All Collections
Access Control
For Administrators With Mercury Hardware
Genea Access Control System Integration with OTIS Compass Destination Dispatch System
Genea Access Control System Integration with OTIS Compass Destination Dispatch System

Learn how to integrate your Genea Access Control System with OTIS Compass Destination Dispatch System

Ankita Chakraborty avatar
Written by Ankita Chakraborty
Updated over a week ago

Through the Otis Compass Destination Dispatch integration, you can manage all elevator traffic from your Genea platform.

Traditionally, passengers press the “up” or “down” elevator call buttons to get to where they need. A modern approach to elevator traffic management exists. With destination dispatch, passengers select their floor and the destination management system guides them to an assigned elevator. This increases passenger flow through orderly travel and optimizes your building operations.

Supported controllers with OTIS Destination Dispatch System

Currently, the following controllers are supported with OTIS Destination Dispatch System.

  1. LP - 4502

  2. EP - 4502

Setting Up Your Genea ACS + OTIS destination dispatch system

1) Navigate to the 'Integrations' tab in your global dashboard.

2) Go to 'Elevator' integrations, and click 'Install' under the OTIS.

3) Click the +Add button to include the locations where you want to activate the OTIS integration. Select the locations and save the settings.

Designate the controller for OTIS integration

To add a controller in Genea for OTIS destination dispatch integration, follow the below steps:

1) Navigate to Hardware from your Genea admin dashboard. Click +Add under the controller's section.

2) Enter the name and optional description of the controller. Select the model number of the controller from the dropdown options.

3) Now, enter the service type, MAC ID of the controller, timezone, serial number, and click Save.

Service Types:

Normal: If your controller is to be used for access control only and it is not to be integrated with OTIS.

OTIS Primary: A primary controller directly communicates to the OTIS DDS.

OTIS Secondary: Communication between the OTIS DDS and the Secondary controller will have to go through the Primary controller. Primary and Secondary Controllers exchange messages through an over-watch controller service which must be installed on the Primary controllers.

Once the controller is added, it is now time to add floors to the elevator.

How to add floors to the elevator?

1) To add floors to the elevator, go to Elevators > Floors from your dashboard. Click +Add. Enter the maximum number of floors in a building and click Save.

3) You may also want to define certain floors that should be freely accessed by anyone such as floors comprising of lobby/reception, parking, or cafeterias/restaurants.

In Genea, you can define such floors as Public Floors. To configure any elevator floor as a public floor, click edit, enable Public Floor, select a schedule during which the floor will be having free access. Click Save. Elevator floors that are allowed public‐access will not require an access card to dispatch an elevator car.

Adding kiosks for OTIS Destination Dispatch System

1) Locate Elevators > Elevator Kiosks from your admin dashboard. ​

2) Click +Add to add a destination entry console. Enter DEC name, an optional description, and click Save.​

3) Once the DEC is added, it is now required to attach readers. To do so, click on "Attach Reader".

4) Enter the reader type - it can either be an internal reader of the controller or an external one. Also, enter the IP address of the OTIS DEC unit.

5) Select a Kiosk mode.

Default Floors: This mode will only authorize the default floor accessible to the users. Users will be notified if they have access to the default floor.

Access to Authorized Floors: This mode will allow the users to select a floor if their credentials have active access levels. Users will be notified if the selected floors are accessible or not.

User Entry of Destination: This mode will allow users to select a floor first and then present the credentials to the reader. Users will be notified if the selected floor is found to be authorized for accessing through the credentials.

Default Floor or Entry of Destination: This mode requires the users to present the credentials to the reader first and then select the floor. If the floor is selected before the timeout period set on DEC, the user will be notified of the accessibility of the selected floors, or else the users will be notified of their access to the default floor.

6) Once you have selected the mode, select the kiosk controller from the list and click Save.

Now that the OTIS DD setup is done, go forward and create the elevator access groups.

How to create Elevator Access Groups?

1) To create an access group, go to Elevators > Elevator Access Groups. Click +Add. Enter the EAG name and description. Click Save.

2) Once the access group is created, click edit to add floors and schedule to the group.

3) Click Edit, enable the floor that you wish to add to the access group, attach the schedule for each floor and click Save.

4) Scroll down to the Kiosks section. Edit the DEC to be added to the specific access group and click Save.

How to configure the default floor accessible to the users?

Assigning default floor while creating a user:

1) While creating a user from the dashboard, select the default floor and save the user details.

Assigning default floor to an existing user:

1) Find the 'Locations' section under the user's profile. Click Edit.

2) Select the default floor and Save.

Default floor will ensure users with valid credentials at a specific terminal are always sent to a default floor, rather than needing to select a destination.

If you have any questions about this feature or have any other requests, please reach out to

Did this answer your question?