> 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/configuration-client/site-installation/external-systems/schindlerid.md).

# SchindlerID

The SchindlerID System integrates Command Centre and the SchindlerID individualization and access control system v1.3.369.1

This integration is comprised of three parts:

### 1. The Schindler Cardholder Management Interface

* Synchronises the Schindler user database with the Command Centre Cardholder database.
* Allows one access card to be used for building doors and the lift system.
* Can convert Badge Numbers from decimal to hexadecimal format.
* Allows Cardholder cards to be automatically formatted as hexadecimal Badge Numbers according to their Card Type specification.
* Assigns a Cardholder's MIFARE Card Serial Number (MIFARE CSN) to the Badge Number field of the corresponding Schindler user.
* Reports on access events at a turnstile/barrier.

### 2. The Life Reporting Interface (plugin)

* Builds an audit trail of Schindler access events in Command Centre.
* Enables Command Centre to receive non-badge card events from Schindler.

### 3. The Call Interface (plugin)

* Enables a Gallagher reader to be used at a Schindler terminal to identify the Cardholder to the Schindler system.
* Enables Command Centre to set the status of a floor to 'Secure' or 'Free' via a schedule or operator override.

**Notes:**

* This integration is compatible with the SchindlerID Call Interface protocol as specified in the document J 41900402.
* Card numbers greater than 16,777,215 are not supported.

### Licensing

The following licence entries are required:

<table><thead><tr><th width="322.6666259765625">Licence</th><th>Description</th></tr></thead><tbody><tr><td><p><code>[Limits]</code><br><code>SchindlerID Systems=N</code></p><p>If using SchindlerID plugins the following licence entries are required:</p><p><code>[Plugin]</code><br><code>PluginX=SchindlerID-LifeReporting</code><br><code>PluginX=SchindlerID-CallInterface</code></p></td><td>Where <code>N</code> is the maximum number of SchindlerID Systems that can be created. Once the maximum number has been reached the option to create additional SchindlerID Systems will be disabled.</td></tr></tbody></table>

### Command Centre multi-server support

The following Command Centre multi-server functionality has been tested:

* All Gallagher-Schindler communications (including Cardholder Sync and Life Reporting) occur from server 1.
* Life Reporting events are replicated to server 2.
* Cardholders can be created on either server (assuming Card Types exist on server 1) and are replicated.
* Floor overrides can occur from both servers.

### Compatibility

The following components are compatible with the Schindler interface:

* Third-Party Database Online Interface J41900401:153324 (11-09-01)
* Call Interface to External Security Systems J41900402: 153324 (11-09-01)
* Third Party Life Reporting Interface v2.8: (12-03-26)
* Schindler ID v1.3.369.1

### Deployment architecture

<figure><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8b913e41693ece17c7dbeb88e89a5668c6165090%2F38891.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/configuration-client/site-installation/external-systems/schindlerid.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.
