> 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/elevator-cars/high-level-interface-elevator-cars/configuring-a-floor-arrangement.md).

# Configuring a Floor Arrangement

### Introduction

A Floor Arrangement enables you to specify the number of floors and the Access Zone that represents the area outside the elevator on each particular floor.

Once configured, a Floor Arrangement can be assigned to multiple Elevator Car HLIs. While the configuration of a Floor Arrangement is optional (Access Zones for floors can be configured directly within each Elevator Car HLI), it is recommended that you do so.

### Procedure

1. Click **Configure** from the menu bar, then **Elevator Cars**.

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

   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 **Floors** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-88921be1517255f434089c162bbf75c22c96a241%2Ffloorarrangement_1.png?alt=media)
5. Enter or select the **Number of floors** accessed by the elevator group, (range 1-256). This automatically populates the table with the required number of Floors.

   **Notes:**

   * The Floor column refers to the number used by the elevator group controller (and within the HLI protocol) to refer to this floor. It is not the floor number by which the level is commonly known, (i.e. what is embossed on the elevator button in the elevator car). Floor numbers used within the HLI can also differ between elevator groups within the same elevator system.
   * The number of floors supported is protocol dependent.
6. Click on a row (or Floor) to select it. Select the Access Zone that represents the area outside the elevator on this particular floor, from the drop-down list immediately below the table.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a1ca2e98379db9c0f0ca6a7046528357411c2c46%2Ffloorarrangement_2.png?alt=media)
7. Repeat Step 6 until an Access Zone has been selected for each Floor to which access is controlled by Command Centre.

   **Notes:**

   * If you do not select an Access Zone for a Floor, this means the associated floor is in free access mode.
   * To configure rear doors for elevator cars that have front and rear doors that lead to different Access Zones, refer to “Rear doors” later in this topic.
   * Whenever a change to a Cardholder’s access is made, all access for the Cardholder is sent to the Controller. If the access for a large number of Cardholders is changed at one time, (e.g. the Floor Arrangement item is modified), this will result in a large number of messages being sent to the Controller. The messages pending can be viewed on the **Status and Overrides** tab in the Controller properties. It is recommended that a large change to Cardholder access, be done at a time when the Controller is at its least busiest, (i.e. after hours).
8. Click the **Custom Fields** tab if you want to add and assign a custom field value to this Floor Arrangement.

   For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
9. Click the **Notes** tab if you want to add a note(s) about this Floor Arrangement.

   For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
10. 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.

### Result

A Floor Arrangement is configured and can be assigned to an Elevator Car HLI.

### Rear doors

The Otis Compass and Kone ELI elevator system integrations currently support rear doors on elevator cars. If you are not using one of these integrations, ignore the following.

You can manage access to both front and rear elevator doors. In the Floor arrangement, you must create double the amount of floors specified in elevator HLI configuration. For instance, if you have 4 floors, in the Floor Arrangement, you would need to configure 8 floors (4 for front and 4 for rear). In the Floor Arrangement, the fifth floor represents the first floor's rear door and the sixth floor is the second floor's rear door and so on. If you have a floor that only has one door (either a front or rear door), you still need to configure two floors for it (one with access and the other without access). Ten Floors and Access Zones are configured below, to represent five physical floors with front and rear doors:

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

You also need to refer to [Supported elevator systems - Additional Configuration and Troubleshooting](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/elevator-cars/high-level-interface-elevator-cars/supported-elevator-systems-additional-configuration-and-troubleshooting.md) for integration-specific rear door configuration (e.g. configuration specific to Otis Compass).


---

# 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/elevator-cars/high-level-interface-elevator-cars/configuring-a-floor-arrangement.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.
