FAQs & Requirements

This topic provides a comprehensive list of requirements needed to integrate the ASSA DSR and POE/IP LOCKS with System Galaxy. The Assa locks will connect directly with ASSA DSR database, which will communicate directly with System Galaxy database.

 

IMPORTANT: You must be an authorized, certified ASSA Installer to perform the ASSA Lock installation and configuration. You must also be an authorized, certified Galaxy Installer to perform the Galaxy installation and configuration.

 

 

Features in this topic

Components of the DSR Solution

Important Requirements

 

---

 

 

Components of the DSR Solution

The following components are required to integrate the Assa DSR Solution with System Galaxy.

Galaxy hardware is not needed for the DSR Lock control. ASSA IP and WiFi Locks do not physically connect to Galaxy hardware panels. ASSA IP and WiFi Locks connect via TCP/IP using POE, or via WiFi to the DSR Server.

IMPORTANT: The DSR Server should not be installed on same computer that is running/hosting the GCS Services (or SG Comm Server). Install the DSR Server app on a separate computer.

 

1. DSR PC/Server - computer hosting the DSR Software, Database, Services and Tools listed below.

   1. DSR Installer v7.0.8 (installs the DSR Server, DSR Support Tool, Assa Abloy Service and PostgreSQL database)

   2. DSR Support Tool (installed by the DSR Installer)

   3. USB COM Cable (supplied with locks) - used with the LCT Tool to configure each lock.

   4. LCT Toolv4.0.25 - (separate installer) installed where it can physically connect to locks using the Serial USB Port.

   5. ASSA Locks (WIFI or IP-enabled (POE)) - All locks connect directly to the DSR Server. Galaxy hardware is not involved.

    

2. System Galaxy Communication Server enterprise access control system.

   1. System Galaxy (v10.5.1 or higher) - for enrolling cards/users and assigning authorizations

   2. SG-DSR Manager App - used to importing readers and configuring the reader schedules and authorizations.

   3. GCS.Web.API.Service - performs the transfer of between SG and the DSR Database.

   4. GCS Core Services - must be running - (GCS ClientGW, DBWriter, Comm Service & Event Service* )

       

      NOTICE: Some GCS services will be running that are not required for DSR integration, or that are required for other integrations also being used at that System Galaxy.

       

 

 

 

 

IMPORTANT REQUIREMENTS

 

CONFIGURING LOCKS

1. You must use the LCT Tool and USB COM Cable to configure ASSA Locks (i.e. network settings, server IP connection settings, POE or WIFI Router security settings, reader type /card technology and lock alarm modes).
   1. You must configure a Lock Profile for the lock, before you add the lock, This includes reader type/card technology, alarm settings, etc.
   2. When you add (connect) the lock, you must assign the profile and provide a man-readable name, as well as program the network settings for the Lock, DSR Server, WIFI Router or POE Security settings.
   3. You must click the [configure] button to send all the configurations to the lock.

    

   INSTALLING DSR SERVER

2. You must install the DSR Server on a separate PC from System Galaxy Comm Server.
   1. The DSR Server has its own PostgreSQL database
   2. During the DSR Installation, you must set the Lock Auto-confirm option to "FALSE" .
   3. During the DSR Installation, you must set the WS Security option as appropriate for the job site. If using WS Security, you must also perform the appropriate security configurations, such as SSL Certs, etc.
3. The Assa Abloy Service must be running on the DSR Server.
4. You must create connection exceptions for the DSR Ports (2571 / 8080) in the Server firewall and anti-virus/malware shields.
5. You should verify Locks are visibly connected to the DSR Server using the DSR Support Tool before launching SG-DSR Manager. You cannot confirm locks in the DSR Support Tool.

 

 

 

SYSTEM GALAXY COMMUNICATION SERVER

 

The SG-DSR Manager App and the Web API Service are automatically installed when the System Galaxy Comm Server is installed. SG Comm Server Installation should already be done. Galaxy Install is not covered in this section.

 

IMPORTANT: ASSA-DSR appSettings keys for must be manually enabled in the Galaxy appSettings config file after System Galaxy software Part-3 is finished installing. (AssaDsrEnabled and AssaDsrCallbackServiceEnabled keys value = "true"). See topic

 

1. The GCS.Web.API.Service must be configured to "start automatically" - it might be advisable to set it to Automatic Delayed.

2. The GCS.Web.API.Service must be running on the SG Communication Server to support SG-DSR Manager.

3. Locks must be connected (online status) to the DSR Server before they can be confirmed in the SG-DSR Manager

4. You must "confirm" locks in the SG-DSR Manager App before you can configure schedules, authorizations, access point modes, lock groups, etc.
   

5. The Lock status must be "online" in order to [confirm] them into the SG-DSR Manager App .

   • If the lock is not online it will still appear in the lock list in both the DSR Tool and SG Manager App. You may need to wake up the lock to get it to confirm.

   • You can wake up WiFi Locks by invoking the wake-up command, or using a wake-up card.

   • Locks are saved / inserted into the SG database and the DSR Server's database at the time they are confirmed.

6. After the lock is confirmed, you should set the lock alarm priorities in the SG-DSR Manager app. Also set any other options you desire and save that it in the Manager Tool - this will put it in the queue to be loaded to the lock(s).

   • POE Locks usually pick up their changes quickly. You may need to wake up WiFi locks.

7. You must create the Schedules you need before you can assign them to door modes and authorizations (access privileges).

8. You must create the Authorizations before you can assign them to the Cards in the System Galaxy Cardholders screen.

9. You must indicate whether a Lock Group can be used to lock and or unlock and assign desired locks

   • This must be done before the operator can use the LOCK, UNLOCK, OR PULSE buttons to command locks.

   • this is not recommended for WiFi Readers since the are not continually online.

10. You must enroll cards/users in System Galaxy Cardholder screen

    • you must assign the appropriate DSR Authorization (access privileges) to a card before it can work at the reader.

    • when cardholder is saved the user and permissions are sent to the appropriate locks by the GCS.Web.API.Service.

    • users can be seen in the SG-DSR Manager App

11. All cards, schedules, authorizations and modes are sent to the appropriate reader by the GCS.Web.API.Service.

12. The operator/admin can force load the changes to any reader from the SG-DSR Manager tool if they do not want to wait on the Web Service to push the updates.

13. If you need to delete locks, you cab delete them from the Access Points screen at the SG-DSR Manager. This removes the lock from SG database and the DSR Server database. If the lock connects again, it will come in as a new unconfirmed lock.

 

 

ASSA - LOCKS ( WIFI Readers / IP-Enabled Readers )

See the manufacturer’s documentation to determine which locks or readers are compatible with the DSR Sever 7.0.7.

IMPORTANT: WIFI Locks only wake up once a day (configurable).
1) You must manually trigger a wake-up at WIFI Locks in order to complete Lock Confirmation.
2) For security reasons, you should manually trigger wake-ups at all WIFI Locks to force updates to lock configuration or whenever changes are made to schedules, authorizations, users, access privileges, and reader modes. FAILURE TO FORCE UPDATES COULD RESULT IN A SECURITY ISSUE.
3) WIFI Locks eventually get their changes whenever the connection timer elapses, which could be up to 24 hrs (configurable).
4) To FORCE UPDATES, trigger a wake-up by entering wake command #323232 at the lock keypad, or by pressing the COMM button inside the reader head, or by presenting a wake-up card at the WIFI Lock. ALWAYS TEST YOUR CHANGES to ensure the compliance.

 

1. Technician must use the Assa LCT Tool to configure Locks to get them to connect to the DSR Server. Locks must connect to the DSR Server and be confirmed into the DSR Database.

   • use the USB Cable to connect the LCT Tool (computer) to each lock to perform the network configurations.

   • set up each lock with the correct IP/Network settings and Security settings to connect to DSR Server

   • Locks will initiate a connection to the DSR Server after they are configured.

 

ASSA - DSR SERVER INSTALLATION

1. You must install the DSR Server software on a separate PC/Server (i.e. not on the Galaxy Comm Server).

   1. The DSR installer lays down the DSR Support Tool, which is used to verify lock connections and make further changes to lock settings.

   2. During installation, you must set the Lock Auto-confirm option to "false".

   3. During installation, set the WS Security option as appropriate for your system.

   4. During installation, set up the appropriate login and password parameters. Do not loose these they are needed to sign into the DSR Support Tool.

2. After the DSR Server is installed, the Technician can launch the DSR Support Tool and see the locks coming online.
   1. POE Locks (IP-Enabled) will come on fairly quickly and should remain connected.
   2. WiFi Locks must be forced to connect using #323232 from keypad, or pressing COMM button inside the reader head. or a wake-up card. (WiFi readers do not have to remain connected to get them into the DSR Database).
      
   3. Locks will come on as "unconfirmed" to Lock List in the DSR Support Tool. Confirming locks will add them to the DSR database. Optionally, you can wait and confirm them later in the SG-DSR Manager App.
3. Use the DSR Support Tool to perform additional post-install configuration, such as setting alarms, security settings, and other options.
   1. POE Locks (IP-Enabled) will pick up their changes automatically.
   2. WiFi Locks require a forced wake-up -- use the wake command #323232, COMM button, or a wake card to trigger the updates.

   TIP: To see how many users are in a Lock, you can select the lock in the LOCK LIST in the DSR Tool and select the Lock Details tab at the bottom half of the screen. At installation the lock should have no users.

 

 

 

SYSTEM GALAXY & SG ASSA MANAGEMENT APP

IMPORTANT: System Galaxy Communication Server and SG Database must be installed before you can use the SG DSR Manager App.

 

1. After all the Locks are properly configured at the DSR Server, you must import and configure locks in the Galaxy SG-DSR Manager App

   1. you must add the DSR Server to the SG-DSR Manager App before you can import locks

   2. you must import locks form the DSR Server and save them into the SG Database before you can edit lock settings, load schedules / modes/ authorizations or users.

      TIP: you can confirm Locks in the SG-DSR Manager App on the Access Points tab

      NOTE: Confirming locks from the SG-DSR Manager will save them in the SG Database and insert them into the DSR Server as confirmed also. This is a matter of policy how you manage Lock confirmation.

   3. you must configure the lock alarms for each individual lock in the Access Point tab of the SG-DSR Manager .

   4. you must create all appropriate schedules in the Schedules tab of the SG-DSR Manager.

   5. you must create all appropriate authorizations (access groups) in the Authorizations tab of the SG-DSR Manager.

   6. you must create all appropriate access point modes (door schedules) in the Access Point Modes tab of the SG-DSR Manager.

   7. you must create all appropriate command lock groups in the Lock/Unlock tab of the SG-DSR Manager.

2. After all the programming for the schedules, modes, authorizations and lock settings are finished, you can UPLOAD your programming to the locks.

   • IP Locks pick up changes quickly.

   • WIFI Locks require a forced wake-up -- use the wake command to force updates. Check Lock "Synch Status" to confirm the updates .

3.  check the Lock "Synch Status" in the SG-DSR Manager to confirm the updates are received by the lock

   • Locks will show an "out of synch" status when updates are pending.

   • Locks will show an "in synch" status when updates are received.

To see how many users are in a Reader, you must select the appropriate lock from the LOCK LIST in the DSR Tool and select the Lock Details tab at the bottom half of the screen.

SYSTEM GALAXY & SG ASSA MANAGEMENT APP

 

IMPORTANT: even though you create a descriptive name for the schedules, authorizations, doors, modes, etc., the ASSA DSR Server identifies everything by a GUID or a Serial Number. Therefore in the DSR Tool you will need to look for the logical GUID or Serial Number. If you don’t know what that is, you can look it up by finding it in the SG ASSA Management App by the name you gave it. The SG ASSA Management App shows you both the descriptive name and the GUID/Serial Number.

IMPORTANT: The Galaxy SG-DSR Manager App will import and confirm Locks after they have made their initial connection to the DSR Server and the DSR Server network parameters have been added to the SG-DSR Manager App. The act of confirming Locks in the SG-DSR Manager App will also .

IMPORTANT: Galaxy makes no guarantees about Assa Lock compatibility. The SG-DSR Manager should integrate with any Assa Lock that is supported/connected at the DSR Server. Certain Lock settings may need to be configured with the Assa LCT Tool or with DSR Support Tool. Refer to Assa Manufacturer Documentation for lock compatibility with the DSR Server.

IMPORTANT: The Alarms reported from Assa Locks must be enabled (turned on) in the individual Lock settings by using the LCT Tool and DSR Support Tool. This must be done by the Assa-certified Installer or Technician.

 

1. The ASSA DSR Server supports both IP-enabled & WIFI Locks.
2. Locks must also be configured with the ASSA LCT Configuration Tool 4.0.25.0. (other nearby version of the LCT may also be acceptable).
3. The Locks must be able to connect to the DSR Server.
4. Be aware that System Galaxy hardware and enterprise software do NOT connect to the locks when using the Assa DSR Solution.
5. The Assa Abloy DSR Service must be running on the DSR Server.
6. The GCS.Web.API.Service must be running on the Galaxy Comm Server.
7. The locks must connect to the DSR Server using the default IP Port 2571 - or appropriate specified port. This can be configured in the LCT Tool for the Lock, and in the DSR Support Tool for the Server.

 

 

Additional Considerations

There are 5 main things to consider ...

1. Reader Technology / Card Format (for Galaxy Enrollment)
2. Reader Firmware Version (ability to connect to ASSA LCT & DSR Server/database)
3. Reader-specific Features (whether they are supported in the SG-DSR Manager app)
4. Reader Alarms (whether they are supported in the SG-DSR Manager app)
5. DSR Server version (v7.0.7.0 is the released version)

 

Reader Technology & Card Format

This pertains to both IP-enabled & WIFI readers.

For Galaxy, the main consideration is ability to enroll the credentials that are accepted by the ASSA reader(s). Remember when you are using the DSR Server integration, Galaxy is not transmitting the card data.

1. Confirm the Reader Type / Model is supported by the DSR Server v7.0.7.0. It may be possible to extrapolate this info via the lock serial number. Contact the lock manufacturer for information about your lock by serial number.
2. Confirm that Galaxy supports for the type of reader technology being used - such as proximity, mag-stripe, or other contact / contactless reader types.
3. Confirm enrollment support of the card format - such as 26bit Wiegand, Clock&Data(ABA), Card SN, HID iClass, etc.

 

About Reader Firmware

This pertains to both IP-enabled & WIFI readers.

Readers connect directly to the ASSA DSR Server/database. Confirm firmware compatibility through the Lock Manufacturer's documentation.

 

Reader-specific Features

There are two types of features - general features and special features ...

1. General features are supported in the System Galaxy DSR Manager App (i.e. lock, unlock, unlock duration, door forced, door propped open (open too long), etc.)
2. Special features such as privacy mode, etc. are features are supported through the DSR Server, but you may not be able to change or manipulate these features in the System Galaxy DSR Manager App.