> 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/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-viewing-the-system-summary.md). # View the System Summary View alarm, zone, input, and fence status counts from a Remote Arming Terminal. The System Summary screen gives you the outstanding alarm count, the armed and shunted counts, and the current date and time, without leaving the keypad. ### Procedure 1. Log on to the Remote Arming Terminal. 2. Press the **More** key on the "Choose Action" screen to reach the "Main Menu". 3. Scroll to **"System Summary"** and press the key. The "System Summary" screen displays. ### System Summary details * Total number of outstanding alarms * Number of Alarm Zones in secure state (armed) * Number of Inputs or Fence Zones not shunted/isolated * Number of Inputs or Fence Zones shunted/isolated * Current Date and Time Press the Back key to return to the "Main Menu" screen. *** 🔗 **Related** * [Keypads - Remote Arming Terminal operation](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-remote-arming-terminal-operati.md). The keys, screens and privileges behind every keypad action. * [Keypads - Viewing and Acknowledging Alarms](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-viewing-and-acknowledging-alar.md). Work through the outstanding alarms this summary counts. * [Keypads - Viewing Alarms Zones and Inputs](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-viewing-alarms-zones-and-input.md). See which zones and inputs are shunted. --- # 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/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-viewing-the-system-summary.md?ask=&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.