> 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/the-live-reporting-interface-plugin.md).

# The Live Reporting Interface (plugin)

### Introduction

The Live Reporting Interface builds an audit trail of Schindler access events in Command Centre, and enables Command Centre to receive non-badge card events from Schindler.

The Live Reporting Interface is an optional licensed plugin of Command Centre. This plugin must be installed on the middleware PC (PC hosting the FTCAPI Middleware Framework).

### Installation

To install the Live Reporting Interface plugin, perform the following procedure:

1. Install the FTCAPI Middleware Framework on the middleware PC (if not already installed). Refer to the topic [Installing the FTCAPI Middleware Framework](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/configuring-an-external-system-server/installing-the-ftcapi-middleware-framework-fmf.md) for instructions.
2. Ensure your Command Centre licence file (CommandCentre.lic) contains the following entry:

   \[Plugin]

   PluginX=SchindlerID-LifeReporting (where X is a number)
3. Run the installation executable **Gallagher Schindler Live Reporting Plugin-Setup 8.xx.xx.msi** on the middleware PC.

   This file can be found with the Command Centre installation files in the folder: Utilities\System Interfaces\Schindler\SchindlerLiveReportingPlugin

   **Note:** The FTCAPI Router Service restarts as part of the install.
4. To ensure that the Live Reporting plugin has installed correctly, select the Windows **Programs and Features** utility from the Windows/Control Panel. The program 'Gallagher Schindler Live Reporting Plug-in' should be listed as currently installed.

### Configuration

To configure the Live Reporting Interface, perform the following procedures:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Configuring an External System Server](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/configuring-an-external-system-server.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Configuring a Live Reporting External System](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/schindlerid/the-live-reporting-interface-plugin/configuring-a-live-reporting-external-system.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Configuring External System Items (Floors)](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/schindlerid/the-live-reporting-interface-plugin/configuring-external-system-items-floors.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/configuration-client/site-installation/external-systems/schindlerid/the-live-reporting-interface-plugin.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.
