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

# External Systems

### Introduction

Gallagher Command Centre uses the bi-directional Gallagher FTCAPI Middleware Framework to communicate with multiple third party systems concurrently. Third party system examples are: DVR systems, intercom systems, security sub-systems, alarm monitoring systems, key cabinets and elevator systems.

Such integrations require an FTCAPI middleware plug-in to be developed in order to conduct the protocol conversions between Command Centre and the third party system.

***

### Integrations

Gallagher has developed an FTCAPI middleware plug-in for each of the following third party systems:

* ASCII Text Interface
* Incoming ASCII Interface
* Senstar Stellar Interface
* SNMP v1 Interface
* Bosch Security Escort Interface
* DVR DigiOp HLI Interface
* KeySecure System Interface
* Kone RCGIF plug-in
* SchindlerID Interface
* Ademco 685 FTCAPI plug-in

For details on a particular interface and configuration instructions, refer to the appropriate release note in the `‘Utilities\System Interfaces’` folder of the Gallagher Installation files.

**Note:** Each third party system (integration) requires an entry in the \[Plugin] section of your Command Centre license file (Command Centre.lic).

Gallagher has also developed FTCAPI middleware plug-ins for other third party systems, (e.g. DVR integrations). These integrations are provided as licensed customisations of Command Centre. For a list of customisations that use FTCAPI middleware plug-ins, contact Gallagher Security Technical Support.

***

### The FTCAPI Middleware Framework

The FTCAPI allows for the following functionality:

* communication of events and status from external systems to Command Centre;
* command strings triggered by internal or external events to be transmitted from Command Centre to an external system; and
* status change messages from external systems to change the state of outputs.

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5c89d662501e06f7950504ee39380e393ece426b%2Farchitecture_externalsystems_html.png?alt=media)

**Notes:**

* The FTCAPI has the ability for card events (those submitted via logCardEvent API method) to be used for the purpose of access in Command Centre.
* An External System Item or DVR Camera can be assigned anywhere in Command Centre where a reader may be assigned (other than in the **Delay** and **Alarm Warnings** tabs for an Alarm Zone), i.e. on a Door or an Elevator Car. Thus the ESI/DVR Camera takes on the general function of a reader in the system.
* The FTCAPI will not function using Gallagher UltraSec Controllers.


---

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