> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/integrations/elevators/otis.md). # Otis Understand Otis Compass compatibility, credential support, licensing, and network requirements. {% hint style="info" %} For networking, see [Configure Otis Compass networking](/knowledge-hub/products/integrations/elevators/otis/configure-otis-compass-networking.md). For operational issues, see [Otis Compass HLI connection issues](/knowledge-hub/products/integrations/elevators/otis/otis-troubleshooting.md). {% endhint %} ## Overview | Attribute | Value | | ---------------- | -------------------------------------------------------------------------------------------------------- | | Integration name | **Otis Compass HLI** | | Protocol | ICD2 and ICD3 (Plus) | | Architecture | Ethernet. CC server communicates with the Otis Compass Destination Management System via a dedicated NIC | | Controller | **Controller 6000 only**. The Controller 6000 RS232 serial slot is used for the Elevator HLI assignment | | Licensing | Licensed, `[Features] OtisCompassHLI=1` | | Max floors | **255** | | Multi-server | Not tested in a CC multi-server environment | > **This integration is compatible with the Gallagher Controller 6000 only.** No additional door licences are required. ## Protocol support ### ICD2 Not all ICD2 messages are supported. Refer to the "Limitations" section of the release note for details. Implemented per the *Compass Security Integration Software Requirements Specification Overview* document `D125_SRS_CSI_Overview Revision 3 (2011-08-01)`. ### ICD3 (Plus) The following ICD3 interactive command is supported per `D125_SRS_CSIGeneric_GallagherGroupLtd_86_Rev16.pdf` (provided by Otis to Gallagher): | Field | Value | | ----------- | ---------------------------------------------------------------------------------------------- | | Type ID | `0x40` | | Name | DEC Security Credential Data | | Source | DES/DER, N/A (Port 45308) | | Destination | SS Port 46308 | | Description | Sent from a DES/DER to the SS when a credential is swiped on a card reader attached to the DEC | Maximum number of bits supported: **255**. ## Reader support ### Gallagher readers Gallagher Readers read Gallagher data from the card. To configure a Gallagher Reader to read the CSN from a Mifare card, see "Creating Readers" in the Configuration Client Online Help. A Gallagher reader assigned to an Elevator Car HLI supports: * Triggered overrides * Double card override * Card trace * Lockdown * Entry allowed during lockdown ### Otis terminal readers Tested using the Otis Terminal **Elatec TWN4 Mifare NFC**, controlled by the Otis Compass Destination Management System. > **The Otis Terminal cannot read Gallagher data from the card.** It reads only the card's serial number. Supported card technologies for Otis Terminals: | Technology | Read mode | | ------------------------------------------------------------------------- | ------------------------------ | | Mifare Classic 1K/4K (4-byte UID) | Mifare Card Serial Number only | | Mifare DESFire EV1 (7-byte UID) | Mifare Card Serial Number only | | HID iClass formats (26/8 Wiegand or other Wiegand Universal Card Formats) | Per CC-supported formats | | HID Encoded 125KHz (26/8, 36/14 Wiegand or other UC Formats) | Per CC-supported formats | | Mifare Plus S 4K | Mifare Card Serial Number only | ## Compass HLI vs Otis Serial HLI Two separate HLI types exist for Otis systems. They **cannot both be deployed concurrently** with the same Otis Elevator Management System: | HLI type | Purpose | Notes | | -------------------- | -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | | **Otis Compass HLI** | Destination-based floor access via the Compass DMS | This document | | **Otis Serial HLI** | Connects a separate Otis Elevator Management System using T-Series readers (for service/maintenance access inside elevator cars) | Separately licensed; refer to the T-Series reader datasheet for supported card technologies | ## Licensing ``` [Features] OtisCompassHLI=1 ``` ![Otis Compass HLI licence configuration - showing the Features section with OtisCompassHLI=1 in the licence file and the Configuration Client licence view](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-5a07da8f94f6b5ea7e9ef9c73dbaf403e78b99c1%2FSECHUB-otis-integration-05-license-config-screenshot.png?alt=media) ### Related content * [Configure Otis Compass networking](/knowledge-hub/products/integrations/elevators/otis/configure-otis-compass-networking.md) * [Otis Compass HLI connection issues](/knowledge-hub/products/integrations/elevators/otis/otis-troubleshooting.md) * [Elevator integration interfaces and limits](/knowledge-hub/products/integrations/elevators/hli-reference.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.security.gallagher.com/knowledge-hub/products/integrations/elevators/otis.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.