> 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/configuring-a-live-reporting-external-system.md).

# Configuring a Live Reporting External System

### Introduction

This topic describes how to create an External System (Live Reporting Interface) that will enable Command Centre to build an audit trail for lift access events. This External System is used to interface with the Logging Task Interface in Schindler.

**Note:** Operators require the "Edit Site" operator privilege to be able to add, modify, and delete External Systems.

***

### Before you begin

* Create the Logging Task Interface in Schindler.
* Request Schindler integrators to create a Logging Task Interface in Schindler, and provide the TCP/IP Port Number shown on the Logging Task Interface. This TCP/IP Port is required later in this procedure.

***

### Configuration

To configure a Live Reporting External System, perform the following procedures in Gallagher Configuration Client:

1. Click **Configure** from the menu bar, then **External Systems**.

   The **External Systems** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. **Right click** and select **New\...External System**.

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click the **Event Response** tab, and configure as required.

   For further detail see [Event Response tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/event-response-tab.md).
5. Click the **Alarm Instructions** tab, and configure as required.

   For further detail see [Alarm Instructions tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/alarm-instructions-tab.md).
6. Click each tab in turn to configure a Live Reporting External System:

<details>

<summary>API Setup tab</summary>

1. Click the **API Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-7061035b514a556e6fdadde2bab20d0cac58a537%2Fschindlerlivereportinginterface.png?alt=media)
2. Select the appropriate **Controller** from the drop-down list.

   **Note:** Only standard Gallagher Controllers will work, (i.e. Gallagher UltraSec Controllers will not work).
3. Select the appropriate External System server from the **Server** drop-down list.
4. Click the **Unique** radio button in the 'Identity' section of this screen and type in a unique identity string. This field is limited to a maximum of 64 characters.

</details>

<details>

<summary>Configuration tab</summary>

1. Click the **Configuration** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9c280785df55c0bafde652ae3c764ddd2d8f7617%2Fschindler_lifereporting2.png?alt=media)
2. Select the **SchindlerID Life Reporting** middleware plug-in from the **System Type** drop-down list.

   The 'Configuration' section this tab becomes populated accordingly.
3. Enter the Schindler server IP address in the **IP Address** field.
4. Enter the TCP/IP Port Number of the Schindler Logging Task Interface in the **Port** field. Range 0-65535.

   To enable Live reporting ensure the Logging of Personal Data is set to **Always** and the Live Reporting **Active** checkbox is ticked.

   **Note:** Schindler advises that storing the personal data may violate local laws. However, if the local laws are fulfilled and you want to log the personal data using the Live Reporting Interface, you need to select the option **Always** for Logging of Personal Data in the Logging Task Interface.

</details>

7. Click the **Icons** tab if you want to change the Icon Set for this external system.

   For further details regarding the **Icons** tab, see [Icons](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/icons.md).
8. Click the **Notes** tab if you want to add a note(s) about this external system.

   For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
9. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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/configuring-a-live-reporting-external-system.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.
