1.0 Introduction

Doors.NET interfaces directly with the Simons Voss range of wireless locking devices. Communication to the locks is via Wi-Fi using a Gateway Node. The integration provides you with a real-time, online system.

Programming tasks performed in Doors.NET are sent out to the locks automatically (via the Gateway Node). This eliminates the need for a configuration reader and there is also no need to physically visit the locks to perform any manual updates.

The integration allows you to: remotely lock and unlock doors, generate live events in real-time, retrieve hardware status information and notifications (such as low-battery events or locks going offline). New cardholders and cardholder changes are automatically updated at the locks and locks can be configured to automatically lock and unlock (by assigning auto-unlock schedules).

Note:

• Effective from Doors.NET v5.2.0 there is a slight difference in setting up the Gateway Node. Prior to v5.2.0, a gateway node would be added to a controller bus. From v5.2.0 and onwards, the gateway node is added to the hardware tree as a Network Device. This change improves the setup workflow of wireless lock integration with NXT-MSC and Mercury controllers. Although a controller is still required for the integration, this change also allows for all of the controller buses to be used for general access control.
  
  
• The integration only covers the integration setup in Doors.NET and does not cover any of the initial setup using Smart Intego.

2.0 Smart Intego Devices Config File

IMPORTANT NOTE: This setup guide assumes you have an existing, detailed understanding of how to setup and configure the locks using the Simons Voss Smart Intego software. The Smart Intego software is covered in a separate training session. Smart Intego is used to capture the gateway node, capture and configure the locks and pair them with the Gateway Node. Smart Intego is also used to create and export the hardware config file which is required for initially setting up the integration.

Note: If you are using multiple gateways these will all be included in the same config file.

Before adding the Simons Voss hardware to Doors.NET, it must already be setup and configured correctly using Smart Intego.

This guide explains how to quickly and easily add the Gateway Node and the locking devices (cylinders, lock handles, etc) to Doors.NET.

3.0 System Capacities

• The maximum number of locks per gateway is 16
• The maximum number of gateways per controller is 8

4.0 Licensing Requirements

Simons Voss integration is a licensed feature and therefore will need to be enabled on your Doors.NET license. Your Doors.NET license should be enabled for the number of Simons Voss devices you will be adding to the Doors.NET software.

Once the feature has been enabled, perform the following steps:

1. From Windows Start Menu, go to Doors.NET >> License Manager.
2. Right-click License Manager and select 'Run as Administrator'.
3. Select Application Server from the list on the left.
4. Click the License tab.
   
   
   
   
5. Click the ACTIVATE button at the bottom of the window.
6. You should see a registration successful notification. Click OK.
7. Confirm a restart of the application server.
8. Scroll down the list of license capacities and locate Readers - Simons Voss and Readers - Simons Voss per Controller. These should match the number of Simons Voss devices you will be adding.
   
     
   
   
9. The Simons Voss hardware type will also show as enabled.
   
   
   
   
10. Each controller can support a maximum of 8 gateway nodes and each gateway node can support a maximum of 16 locks.

5.0 Export the Hardware Config File

The Smart Intego software gives you the ability to create an exported file of all the lock information (the lock name, chip ID,). This exported file can then be imported into Doors.NET as a very quick and simple method of adding the locks. This also ensures the lock are added to Doors.NET in the correct order. If the Doors.NET software will reside on a different PC/host workstation then you should copy the exported file onto a portable storage device to transfer the config file across.

1. From within the Smart Intego software, ensure you have paired all the locks/devices with the gateway.
2. Click on File >> Export Configuration Data.
3. Save the config file to somewhere on the PC (or onto a storage drive if the host PC will be on another workstation).
   
   
   
   
4. Smart Intego will notify you of how many locks/devices have been exported to the .CSV file.

6.0 Add the Gateway Node to Doors.NET

6.1 Setup Using NXT-MSC Controllers

This section assumes you already have an online NXT Mercury-Powered (MSC) controller.

1. Log into Doors.NET (default username and password are both admin).
2. Go to Setup >> Hardware Setup >> All to display the hardware tree.
   
3. Double-click the controller that the gateway node will be added to.
4. Select Network Devices (located beneath the controller buses).
   
   
   
   
5. Click Add Network Protocol icon from the ribbon bar.
   
   
   
   
6. Expand the network devices node and you will see a new entry named 'Undefined'. Select this new entry and the properties will be displayed on the right.
7. Use the Protocol (Network) drop-down menu to select Simons Voss.
   
   
   
   
8. Save the network protocol properties.
9. You will be prompted to reset the controller. Click YES to go ahead with the reset.
10. The Simons Voss network protocol will now appear beneath Network Devices.
11. Select the newly added Simons Voss protocol.
12. From the ribbon bar, click on the Add Simons Voss Gateway icon.
    
    
    
    
13. A dialog box will appear, giving you the option of adding multiple gateways, changing the default description and you can also choose to include the controller name in the gateway description. Click the ACCEPT button to go ahead with importing the gateway.
14. The gateway will be added to the hardware tree but if you select the gateway you will see that there is configuration data missing.
    
    
    
    The gateway configuration (for example; the programmed IP address) is contained in a config file, which is imported into Doors.NET - See section 7.0).

6.2 Setup Using Mercury Controllers

Effective from Doors.NET v5.2.0, the Simons Voss integration is also available when using Mercury EP or LP series controllers. This section assumes you already have an EP or LP series controller added to Doors.NET and online.

1. From within Doors.NET, go to Setup >> Hardware Setup >> All.
2. The hardware tree will appear.
3. Select the Mercury controller and in the controller properties, ensure the controller is online.
   
   
   
   
4. Double-click the controller to view the controller attributes.
5. Select Network Devices.
6. Click the ADD NETWORK PROTOCOL icon.
   
   
   
   
7. Expand the network devices node and you will see a new entry named 'Undefined'. Select this new entry and the properties will be displayed on the right.
8. Use the Protocol (Network) drop-down menu to select Simons Voss.
   
   
   
   
9. The other protocol settings can be left at their defaults.
10. Save the network protocol properties.
11. You will be prompted to reset the Mercury controller. Click YES to go ahead with the reset.
    
    
    
    
12. The Simons Voss network protocol will now appear beneath Network Devices.
13. Select the newly added Simons Voss protocol.
14. From the ribbon bar, click on the Add Simons Voss Gateway icon.
    
    
    
    
15. A dialog box will appear, giving you the option of adding multiple gateways, changing the default description and you can also choose to include the controller name in the gateway description. Click the ACCEPT button to go ahead with importing the gateway.
16. The gateway will be added to the hardware tree but if you select the gateway you will see that there is configuration data missing.
    
    

The gateway configuration (for example; the programmed IP address) is contained in a config file, which is imported into Doors.NET - See next section).

7.0 Import the Hardware Config File

To save you having to manually add the locks into Doors.NET, you can import the lock config file which also eliminates the possibility of the locks being added in an incorrect order. The following steps also eliminate the need to configure the gateway communication settings.

Notes:

• The locks will already need to be communicating with the gateway node (configured using the Smart Intego software).
• The hardware config file contains all the gateways and locks for your site (it is not one config file per gateway). However, you do have to manually add each of the gateway nodes into Doors.NET.

The following steps explain how to import the gateway and locks config file.

1. From within Doors.NET, open the hardware tree (Setup >> Hardware Setup >> All).
2. Select the Simons Voss gateway node (added in the previous section).
   
   
   
   
3. The Smart Intego Import wizard will appear. Click NEXT to proceed.
4. Click the IMPORT button.
   
   
   
   
5. Navigate to the location on the PC where the config file is located.
6. Select the config file and click OPEN.
7. Click the PROCESS button and a list will appear of all the devices in the config file.
   
   
   
   
8. Place a check mark in the Selected Hardware option - this will allow you to make multiple hardware selections.
9. Select a gateway node (node type is GN_ER), then use the CTRL keyboard button to select the locks that have been added to that selected gateway (you will know which locks are added to the gateway because they will be displaying the same IP address in the connection details field.
   
   
   
   
10. Click the ANALYSE button.
11. A summary of the lock information will be displayed. If everything appears to be correct, click on the PROCESS CHANGES button. If PROCESS CHANGES is grayed-out then it is likely you are attempting to import an unsupported device. In which case you would need to click BACK and then de-select the unsupported device.
    
    
    
    
12. The detected number of locks will be displayed in a dialog box and the locks will then be added to the hardware tree.
    
    
    
    
13. Click okay and close the config file import wizard.
    
14. The gateway will now be configured and the locks will be located beneath the gateway in the hardware tree.
    
    
    
    
15. If you select the gateway node, in the gateway properties, you should see that it is online.
    
    
    
    
16. In live events you should also see events that have been generated from the locks.
    
    
17. After a few seconds each of the locks that are paired with the gateway, will come online.

8.0 Add a New Cylinder Lock or Smart Handle

Important Note: When adding additional locks to the system, you must first add the lock to the gateway using the Smart Intego software and then export a new (.csv) config file (which will be imported into Doors.NET).

1. From within Doors.NET go to the hardware tree (Setup >> Hardware Setup >> All).
2. Select the Simons Voss Gateway Node.
   
   
   
   
3. Click the Smart Intego Import icon from the ribbon bar.
   
   
   
   
4. The config import wizard will appear.
5. Click NEXT.
6. Click the IMPORT button.
7. Select the updated config file.
   
   
   
   
8. Click OPEN.
9. Click PROCESS and all devices in the config file will be displayed.
10. Again, ensure there is a checkmark in the Selected Hardware option.
11. Use the keyboard CTRL button to select the existing gateway and then select the new lock which has been added to the gateway (or multiple additional locks).
    
    
    
    
12. Click the ANALYSE button and you will see a summary of the lock(s) that will be added.
    
    
    
    
13. Click the PROCESS CHANGES button.
14. Close the lock added notification and close the import wizard.
15. The new lock will now appear on the hardware tree.
16. A few seconds later you will see events from the new lock being displayed in live events.
    
    
    

9.0 Edit Lock Settings in Doors.NET

When you select a lock in the Doors.NET software, the lock properties will display on the right.

Note: Any setting which is grayed-out is non-editable.

• Description - Allows you to change the name of the lock.
• Enabled - Allows you to manually enable and disable the lock.
• Door Type - Allows you to set a specific door type to the lock (used for reporting purposes).
• Door Class - Allows you to set a specific door class to the lock (used for reporting purposes).
• CHIP ID - Displays the programmed CHIP ID for the lock.
• Auto Unlock Schedule - Allows you to select a schedule to determine when the lock will automatically lock and unlock during the day.
• Enable Door Contact - Enable and disable the door contact input (only available on the Smart Handle DM) lockset.
• Strike Timing - Minimum - Allows you to adjust the minimum strike time for the lock (unlock time following a valid card read.
• Strike Timing - Maximum - Allows you to adjust the maximum strike time for the lock (unlock time following a valid card read).
• Anti Passback Mode - Allows you to enable Antipassback on the lockset.
• Filter Door Change of State Transactions - Filters out the diagnostic messages from the door contact.
• Enrollment Reader - Allows you to configure the reader as an enrollment reader.
• Enable Office Mode - Enables Office Mode for the lockset.
• Enable Office Mode - Enable Offline Access List for the lockset.

10.0 Lock and Unlock from Doors.NET

The locks can be instantly controlled from the Doors.NET software - either from the doors grid or from the hardware tree.

• Right-click the lock and select Mode >> then select one of the lock/unlock modes (or you can click Temp Unlock).
  
  
  
  
• If you have the reader selected in the hardware tree, you will also see unlock icons in the ribbon bar that you can use.
  
  

Note: The locks can also be put into 'Lockout' mode (which prevents all cards from gaining access).

11.0 Offline Access List (Whitelist)

The offline access list allows for up to 25 designated cardholders to be able to gain access through the lock (even if the controller is offline to the Doors.NET system). So even if there is a power-outage or controller failure, some cardholders will still be able to gain access at the lock. The Offline Access List can be enabled on a per-lock basis - allowing you to only select the locks that you wish to participate.

11.1 Enable Offline Access List at the Lock

1. Select the lock in the hardware tree.
2. In the lockset properties on the right, locate the Options.
3. Set Enable Offline Access List to Yes.
4. Save the Lock Settings.

Note: this will only enable the feature, the next steps explain how the feature is activated.

11.2 Enable Offline Access List in the Cardholder Record

1. In Doors.NET go to the Home tab >> Cardholders. When the system is licensed for Simons Voss you will see an additional Simons Voss tab on each cardholder record.
2. Open an existing cardholder record or enroll a new cardholder.
3. Click on the Simons Voss tab.
   
   
   
   
4. On the right-side of the screen you will see a list of all locks that have the Offline Access List enabled.
5. For a new system you should highlight each lock and then click on the REMOVE ALL button to clear any existing user records (including any construction credentials) - See next section.
   
   
   
   
6. With the lock selected (or multiple locks selected) ensure the cardholder's credential number is selected on the left.
7. From the Offline Type drop-down list, select one of the two available options:
   
   - Check with the controller - When a valid card is presented, the lock then does a check that the controller is offline - this will incur approximately a 3-second delay before access is granted.
   
   - Emergency - There is no check if the controller is offline and so access is granted immediately (for example; for emergency services personnel). The credential will be immediately granted access locally at the lock.
   
   
8. Click the UPDATE button and the credential will be updated in the database and will automatically be sent out to the access control network.

Note: The ACTIVATE OAL and DEACTIVATE OAL buttons can be used to immediately enable and disable the offline access list at the selected reader.

12.0 Remove the Construction List From a Lock

The construction list is a list of cardholders that are enrolled into the lock using the Smart Intego software. Typically these cardholders would be enrolled into the lock during the construction phase of a building and it allows you to bring the system fully online in stages. These credentials would typically be removed from the lock once the lock has been added to Doors.NET. The following steps explain how to remove the construction list.

1. In Doors.NET, open a cardholder record.
2. Click on the Simons Voss tab.
3. On the right-side of the screen you will see a list of all locks that have the Offline Access List enabled.
4. Select the lock that has the construction list in memory.
5. Click the REMOVE CONSTRUCTION button.
   
   

Note: You can also use the REMOVE ALL button to remove all credentials (Whitelist and Construction credential types).

13.0 Low Battery Events

If a lock has a low battery you will see regular low battery events displayed in live events:

• Low battery events - will start to appear 30 days before the battery is completely flat.
• Critical battery events - will start to appear 20 days before the battery is completely flat.

Note: These low batteries events can be used in the Global Linkage menu - so you can configure the system to immediately send you an e-mail message when the battery level is low or critical.

14.0 Office Mode

Doors.NET also gives you the ability to enable office mode on any of the Simons Voss locksets. Office mode allows one or more cardholders to permanently or temporarily unlock a reader with 2 or more valid card presentations within a 3 second time period. This feature is useful if you need to allow non-cardholders access to a room (such as a teacher unlocking a training room for the duration of a lesson). A single card read will grant access as normal but 2 valid card reads within 3 seconds will keep the lock unlocked.

1. Go to the hardware tree in Doors.NET (Setup >> Hardware Setup >> All).
2. Double-click to expand the controller.
3. Select the lockset that you wish to configure.
4. Locate Options in the lock settings.
5. Set Enable Office Mode to Yes.
   
   
   
   
6. Save the settings and the lock will be immediately updated.

Notes:

• To re-lock the door again, perform another 2-card presentation at the reader and then physically close the door. When re-locking, you will need to hold the credential against the reader for 2-3 seconds.
• This feature requires the use of a door contact as so is therefore only supported on the Smart Handle DM lockset.

15.0 Using a Simons Voss Keypad

The integration gives you the ability to utilize a Simons Voss keypad for PIN or Card + PIN access. The keypad has a 1-to-1 association with an individual lock and is paired using the Doors.NET software.

The following steps explain how to pair a keypad with a lock. Please refer to the Doors.NET help file for instructions about setting up Card + PIN and PIN only access.

1. In Doors.NET, go to Setup >> Hardware Setup >> All.
2. Expand the hardware tree and select the lock you wish to associate with a keypad.
3. In the reader properties on the right, locate the Alternate Reader option, set this to Yes.
4. For the Alternate Reader Type, select Simons Voss keypad.
5. From the Paired Keypad selection, select the available keypad (which is also communicating to the same gateway node).
   
   
   
   
6. Save the reader settings.

Note:

• When using a Simons Voss keypad it is not possible to activate Card + PIN with a schedule. Instead the reader mode (i.e Card + PIN mode) is set via a right-click in the Doors.NET software.
• The number of PIN digits for the keypad is setup in the Smart Intego software (the default value is 4).