> 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/hli-reference.md).

# Elevator integration interfaces and limits

Compare elevator interface types, controller limits, port use, and performance guidance.

Gallagher integrates with four major elevator brands via three distinct interface methods. The interface type drives the wiring, software configuration, and item type used in Command Centre.

Supported brands: **Kone, Otis, Schindler, ThyssenKrupp**.

## Two elevator system types

| Type                              | How it works                                                                                    |
| --------------------------------- | ----------------------------------------------------------------------------------------------- |
| **Conventional dispatching**      | Any available lift serves any request. Passengers select their own floor inside the car.        |
| **Destination-based dispatching** | The system groups passengers by destination floor before they enter and assigns a specific car. |

![Conventional dispatching concept - scatter diagram showing undirected assignment](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-dcd18a9dc15854fd3b625b8a6d3eacac95644646%2FSECHUB-elevator-integrations-01-conventional-dispatch-concept.png?alt=media)

![Conventional dispatching - one lift serves all requests while others sit idle](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-d7ff7c74180e616f7339dfc446c289730e8331be%2FSECHUB-elevator-integrations-02-conventional-dispatch-illustration.png?alt=media)

*Conventional: all passengers compete for the same available lift. Other cars sit idle.*

![Destination-based dispatching concept - scatter diagram showing grouped assignment by colour](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-0c043c5727c5821f36ccceec3bb2bdbd1005bd15%2FSECHUB-elevator-integrations-03-destination-dispatch-concept.png?alt=media)

![Destination-based dispatching - Lift A assigned floors 10-15, Lift C assigned floors 25-35](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-7e97f306a73193734ea1f0c41eda0cabc9d8b0c5%2FSECHUB-elevator-integrations-04-destination-dispatch-floor-assignment.png?alt=media)

*Destination-based: the system pre-assigns lifts by floor group before passengers board.*

## Three interface types

### RS232 - Wired Serial Cable

**Used by:** Kone (standard), Otis, Otis Modbus, Schindler, ThyssenKrupp v7.10+.

A physical serial cable connects the C6000's RS232 port directly to the elevator system panel.

![RS232 architecture - Gallagher server and workstation connected to C6000 via RS232 serial cable, C6000 wired to 3 lifts and Elevator System Group Control](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-ae0ea7dc365e5cd2e308592a096abf2cddb98ec1%2FSECHUB-elevator-integrations-05-arch-rs232-serial.png?alt=media)

**Requirements:**

* RS232 cable wired to the controller hardware port.
* Elevator HLI item configured in Command Centre under Controller > Serial Devices tab.

![C6000 Properties - Serial Devices tab showing Elevator HLI field set to Kone ELI HLI](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-386040b4438ce74d1f6344510a2cf9ff076a9a5c%2FSECHUB-elevator-integrations-06-c6000-serial-devices-config.png?alt=media)

### TCP/IP - Network Connection

**Used by:** Kone ELI, Otis Compass, Schindler system variants.

No physical serial cable. Communication goes over LAN. The controller's Serial Device software slot is still used, but the RS232 hardware port is not.

![TCP/IP architecture - Gallagher server on LAN, C6000 communicating with Elevator System Group Control over network with 3 lifts](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-60c7ce17f29bb9c79db36fe3cca3ff380a2a9890%2FSECHUB-elevator-integrations-07-arch-tcpip.png?alt=media)

> **Note:** Even without a cable, the controller's Serial Device slot is consumed and unavailable for other purposes. The Elevator HLI item is still required for some variants.

> **Schindler note:** Requires a middleware machine, which is unique among all integrations.

![Schindler-specific - External Systems tree in Command Centre showing SchindlerID System, Live Reporting, and Call Manager items](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-d8f6100b541b2181c0accf9b9428f2da498fa105%2FSECHUB-elevator-integrations-08-schindler-external-systems-config.png?alt=media)

### Gallagher Elevator Service - TCP/IP with Service Layer

**Used by:** Kone Office Flow, ThyssenKrupp v8.10-8.30, ThyssenKrupp Insight (v8.40+).

A separate Windows service (GGL Elevator Service) sits between the Gallagher server and the elevator system. This is the most modern integration path.

![GGL Elevator Service architecture - Gallagher server bidirectional with GGL Elevator Service, both on LAN, C6000 connects to 3 lifts and Elevator System Group Control](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-63d77d82d5200d954f01d9fde2a8c73052495c7b%2FSECHUB-elevator-integrations-09-arch-ggl-elevator-service.png?alt=media)

> **Key difference:** Uses the **Elevator System** item type in Command Centre, not Elevator HLI. There is no dependency on the controller's Serial Device slot or RS232 port.

## HLI comparison table

![HLI comparison table - all supported vendors showing interface type, RS232 port usage, Gallagher Elevator Service requirement, and CC item type](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-6d2b893e491ab996c9abd7cd41ace8375fc0cce9%2FSECHUB-elevator-integrations-10-hli-comparison-table.png?alt=media)

**RS232 Port column values:**

| Value       | Meaning                                                                      |
| ----------- | ---------------------------------------------------------------------------- |
| **use**     | Physical serial cable required and connected to the controller port          |
| **consume** | No cable needed but the port is locked and cannot be used for other purposes |
| **unused**  | Port remains free for other purposes                                         |

For the full compatibility matrix including CC version requirements, refer to the CC Compatibility Matrix.

## System limits (C6000)

| Parameter                    | Limit | Notes                                                        |
| ---------------------------- | ----- | ------------------------------------------------------------ |
| Levels per elevator car      | 256   | -                                                            |
| Elevator cars per controller | 8     | Max configuration size per C6000                             |
| Transactions per second      | 2     | Across all access items (doors and lifts) on that controller |

In practice the binding limits are **20 HBUS readers per controller** and **2 events per second per controller**.

## Performance guidelines

* Place the Elevator Car HLI item and its reader on the **same controller**.
* Use **one access group covering all required levels** rather than multiple single-level groups. This reduces transaction overhead significantly.
* Use the "Change to Disarmed state" Alarm Zone privilege sparingly, as it significantly impacts response time. If used, keep the Alarm Zone on the same controller as the elevator car.

***

🔗 **Related**

* [KONE](/knowledge-hub/products/integrations/elevators/kone.md), [Otis](/knowledge-hub/products/integrations/elevators/otis.md), [Schindler](/knowledge-hub/products/integrations/elevators/schindler.md), [ThyssenKrupp](/knowledge-hub/products/integrations/elevators/thyssenkrupp.md). The per-vendor integration detail.
* [Glossary](/knowledge-hub/products/integrations/elevators/glossary.md). Acronyms and product codes used across the vendor notes.


---

# 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/hli-reference.md?ask=<question>&goal=<user_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.