BlueWave Security has developed a feature that will send a Lockdown command to certain doors  (“Receiving door(s)”) in response to a Lockdown AUX event occuring at a door (“Triggering door”). The  Lockdown AUX can be set up to trigger when a physical button is pushed at the location of the sending  door. The Lockdown command locks the door and prevents any credentials from gaining admittance,  other than a card programmed to have Master Card functionality. 

The success of the Lockdown Forwarding feature depends on many factors relating to the server  software, network connectivity between the controllers and the server, and proper functioning of the door  hardware. It should ONLY be used as part of a comprehensive Lockdown protocol that includes physical  confirmation that doors are secured after the Lockdown command has been issued. 


This document assumes that BlueView 17.0-5 (or higher) has been installed and configured on the  machine used as the BlueView server. Bluelink Network Services must be running and both the  Triggering and Receiving doors must be online and communicating with the service for this feature to be  active. 

 1. Enable the Lockdown Forwarding feature. The Lockdown Forwarding feature will be available  only on systems that are licensed for it, in the form of a valid activation code that includes this  

feature. When BlueView is properly licensed, “Lockdown Forwarding” will appear under Modules  on the License Information portion of the Help → About screen.

 a) To turn on Lockdown Forwarding, in BlueView, go to File → Preferences, and click on the  Lockdown Forwarding tab. Put a check in the box next to Enable Lockdown Forwarding.  

 b) Determine whether you will organize your Receiving doors by Site or by Area, and make the  appropriate selection from the drop-down box. 


c) If necessary, make adjustments to the “Number of Times to Retry on Failure” setting. This  setting determines how many times the Lockdown Forwarding mechanism will attempt to retry sending a Lockdown command to doors that have not yet been locked down because they are disabled, have no network route to the controller, are not connected, are in the middle of a  permissions activation, or are in “Controller Failed” mode. BlueWave recommends keeping  the retry number below 10. This is because a higher number of retries could result in the  service being tied up unnecessarily long. In turn, this could delay other system tasks,  including pending Lockdown Forwarding requests. In most cases, 5 retries should be  sufficient to reconnect to any controllers that may have been momentarily offline at the time  the Lockdown AUX signal was detected. 

 d) Click Save Settings to commit the changes. Click OK to confirm that the settings have been  saved, then Close to exit the Preferences screen.

 2. Organize Triggering door(s) and Receiving door(s) into the same BlueView Area or Site, based on the setting you chose in step 1 above. In BlueView, go to Configure → Door.  


a) If Lockdown Forwarding by Area is selected: Select a Door, then change its Area by making a selection from the Area drop-down. Then click “Apply” to save the change. When a Lockdown AUX event occurs at any of the doors in an Area, the other doors in the same Area as the  triggering door will be sent the Lockdown command. 


b) If Lockdown Forwarding by Site is selected: Select a Door, then change its Site by making a  selection from the Site drop-down. Then click “Apply” to save the change. When a Lockdown  AUX event occurs at any of the doors in a Site, the other doors in the same Site as the  triggering door will be sent the Lockdown command. 

 3. Install the Lockdown button. Wire the Lockdown button into the NetGen controller at the  Triggering door according to the diagram below, which will work for most buttons. Check the  instructions for your button to be sure.

 4. Configure the Triggering door in BlueView. 

 a) Triggering doors (the door controllers that have a physical button wired into them) need to be  set up to generate a Lockdown event on AUX input. In BlueView, go to Configuration →  Doors. Select the triggering door. Click on the Advanced Configuration button. In the  Advanced Configuration screen, under AUX Input, confirm that LockDown is selected. Click  Close to save the settings. 


b) Triggering doors also need to be set as “Event Priority” doors. On the Door Configuration  screen, select the Triggering door. Click the box next to Event Priority to put a check in it, then click Apply.  

This setting means that these doors will be checked more frequently for events, so the system will receive and respond the Lockdown AUX event in a more timely way. It is important that  ONLY Triggering doors are marked as “Event Priority” doors, because the more doors that  have this setting turned on, the less effective it will be.


5. While in the Configure → Door screen, confirm the firmware version for both Triggering and  Receiving doorsBlueWave recommends that all doors included in a Lockdown protocol be running firmware version 7.02 or higher. Use the Firmware Updater tool to update the  firmware on any doors running earlier versions of firmware. 


To recap, Lockdown Forwarding will ONLY work in the following circumstances: 

• The Lockdown Forwarding feature is appropriately licensed and has been enabled in the software • Bluelink Network Services is running on the BlueView server 

• The Triggering door has power and is online and communicating with Bluelink Network Services  • The Triggering door has been configured as an “Event Priority” door  

• The Receiving doors have power and are online and communicating with Bluelink Network  Services  

• The Receiving doors are configured in BlueView to be in the same Area or Site as the triggering  door. (Choose either Area or Site as described in step 1b above.) 

• Both Triggering and Receiving doors are running firmware 7.02 or higher  

• Each door must have locking hardware in good working condition. Lockdown may not occur if the door is propped open, or if something else is physically hindering the locking mechanism from  securing the door. This kind of failure can NOT be detected or reported in the software – it must  be confirmed by visual inspection. 

The Receiving doors will NOT instantly go into Lockdown. There will be a delay as Bluelink Network Service relays the Lockdown signal to each door. The length of the delay is dependent on many factors,  including but not limited to the amount of event traffic the server is processing at the time that the  Lockdown AUX event occurs, the speed and reliability of the network connection between the controllers  and their server, the performance of the BlueView server, the number of doors in the Area, etc. Similarly,  once the doors have received the forwarded Lockdown commands, there may be an additional delay  before the Lockdown events and door statuses are reported back to the server and updated in the  BlueView software and web interface. 

BlueWave recommends periodic “live” testing of the Lockdown Forwarding feature, to ensure that staff  are familiar with the way the feature works and to help ensure that all door controllers, network  connections, and door hardware are in working order. 

Lockdown Forwarding should ONLY be used as part of a comprehensive Lockdown protocol that  includes physical confirmation that doors are secured after the Lockdown commands have been issued.