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

# KONE

Choose a KONE integration method for elevator access control or cardholder synchronization.

Gallagher integrates with Kone elevator systems through **three distinct methods**. The correct method depends on the site's Kone infrastructure and the Command Centre version in use.

{% hint style="info" %}
**Note:** There are two versions of Kone HLI. Which version applies depends on the Command Centre version. Confirm the CC version before configuring.
{% endhint %}

## Variants

| Variant                                                                                                   | Status                   | Architecture                                                   | Licensing                  | Use case                                                         |
| --------------------------------------------------------------------------------------------------------- | ------------------------ | -------------------------------------------------------------- | -------------------------- | ---------------------------------------------------------------- |
| [**Kone Serial (Standard)**](/knowledge-hub/products/integrations/elevators/kone/kone-serial-standard.md) | Current, legacy / serial | RS232 from C6000 to Kone Controller (Kone Protocol v2.5)       | Non-licensed               | Older Kone systems with Conventional Dispatching                 |
| [**Kone ELI**](/knowledge-hub/products/integrations/elevators/kone/kone-eli.md)                           | Current, IP-based        | TCP/IP per Kone Group Controller Access Control Interface Spec | Licensed                   | Current Ethernet-based integration; supports Destination Control |
| [**Kone Office Flow**](/knowledge-hub/products/integrations/elevators/kone/kone-office-flow.md)           | Current, data sync only  | Service-based sync to KONE Office Flow                         | Licensed (`Kone Access=1`) | Cardholder sync only, NOT for elevator access control            |

### Add-ons / extensions to Kone ELI

| Extension                                                                                                            | Status  | Purpose                                                                                 |
| -------------------------------------------------------------------------------------------------------------------- | ------- | --------------------------------------------------------------------------------------- |
| [**Kone ELI - RCGIF Plugin**](/knowledge-hub/products/integrations/elevators/kone/kone-eli/kone-eli-rcgif-plugin.md) | Current | Automates turnstile-triggered elevator calls; supports multi-controller (KCEGC1) setups |

## At a glance

### Kone Serial (Standard)

Serial-based integration using **Kone Protocol v2.5**, intended for older Kone elevator systems. An RS232 cable runs directly from a **Controller 6000** to the Kone Controller. **Non-licensed.**

* One serial connection per C6000 (single RS232 port).
* Up to 8 Elevator Shafts/Cars per Controller (RS232); 2 per Controller (TCP/IP).
* See [Kone Serial (Standard)](/knowledge-hub/products/integrations/elevators/kone/kone-serial-standard.md) for full details.

### Kone ELI (IP-based)

IP-based integration implemented per Kone's **Group Controller Access Control Interface Specification Rev 1.8**, the current Ethernet-based method.

The Kone ELI integration creates four item types in Command Centre:

![Kone ELI HLI 2 highlighted in the Hardware panel under Controller 7000, visible in the Alarm Viewer - the HLI item sits directly under the controller in the hardware hierarchy](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-c0d9be833dc3562dd4010c0fcc7cc40feef0e750%2FSECHUB-kone-integration-01-eli-hli-hardware-item.png?alt=media)

* **Kone ELI HLI** - Hardware item under the assigned controller. Visible in the Alarm Viewer.
* **Floor Arrangement** - defines which floors a cardholder is permitted to reach; assigned to cardholders or access groups.
* **DOP (Door Operating Panel)** - represents the call panel at each floor landing (outside the elevator car).
* **COP (Car Operating Panel)** - represents the button panel inside the elevator car.

The three remaining item types as they appear in the **Elevator Car** master list (Configuration Client):

![Floor Arrangement 1 highlighted in the Elevator Car master list - the Floor Arrangement item sits alongside the DOP and COP panel items](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-bc5f5bf10aaea01955bb1d15acb03bb89f0fa6f5%2FSECHUB-kone-integration-02-eli-floor-arrangement.png?alt=media)

![Kone DOP in 5th Floor / Panel 1 highlighted in the Elevator Car master list - the Door Operating Panel (landing call panel) item](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-48057e691aaeb41b673d406281ab47023b5bd3a9%2FSECHUB-kone-integration-03-eli-dop.png?alt=media)

![Kone COP Panel 1 highlighted in the Elevator Car master list - the Car Operating Panel (in-car buttons) item](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-24c9f419cb593e29c377860538d119104dd136dc%2FSECHUB-kone-integration-04-eli-cop.png?alt=media)

For deep configuration reference, see [Kone ELI](/knowledge-hub/products/integrations/elevators/kone/kone-eli.md), [Kone ELI Configuration](/knowledge-hub/products/integrations/elevators/kone/kone-eli/kone-eli-configuration.md), and [Kone ELI Troubleshooting](/knowledge-hub/products/integrations/elevators/kone/kone-eli/kone-eli-troubleshooting.md).

For turnstile-triggered calls and multi-controller deployments, see [Kone ELI - RCGIF Plugin](/knowledge-hub/products/integrations/elevators/kone/kone-eli/kone-eli-rcgif-plugin.md).

### Kone Office Flow

**Synchronises Command Centre cardholder records with the KONE Office Flow system on a regular basis.**

* **Not for elevator access control** - data synchronisation only.
* Operates independently of Kone Serial and Kone ELI.
* See [Kone Office Flow](/knowledge-hub/products/integrations/elevators/kone/kone-office-flow.md) for licensing, configuration items (Kone Service, Kone Validity Time, Kone Elevator Access), and release-note reference.

## Choosing between variants

* **Site has older Kone equipment using Conventional Dispatching and Kone Protocol v2.5?** Use [Kone Serial (Standard)](/knowledge-hub/products/integrations/elevators/kone/kone-serial-standard.md).
* **Site has a modern Kone Group Controller (KGC/KCEGC) supporting TCP/IP?** Use [Kone ELI](/knowledge-hub/products/integrations/elevators/kone/kone-eli.md).
* **Site wants turnstile-triggered elevator calls, or has multiple KCEGCs in one Kone Group?** Use [Kone ELI - RCGIF Plugin](/knowledge-hub/products/integrations/elevators/kone/kone-eli/kone-eli-rcgif-plugin.md) (extends Kone ELI).
* **Customer wants to sync cardholders to KONE Office Flow (a separate building/people management system)?** Use [Kone Office Flow](/knowledge-hub/products/integrations/elevators/kone/kone-office-flow.md) (this is data sync, not access control).

Kone Office Flow can run alongside Kone ELI or Kone Serial, because they serve different purposes. Kone Serial and Kone ELI are typically not deployed together at the same elevator system.

***

🔗 **Related**

* [HLI Reference](/knowledge-hub/products/integrations/elevators/hli-reference.md). Cross-vendor interface types and system limits.
* [Schindler](/knowledge-hub/products/integrations/elevators/schindler.md). The other destination-control vendor integration.


---

# 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/kone.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.