Emergency and Muster Management

The Emergency Command Center is the most critical page in the NISC Mustering System. It provides real-time accountability of all personnel during an active emergency, enables multi-channel mass notifications, and maintains a full audit trail of every event for compliance and after-action review.

Navigate to: Emergency (main navigation)

---

Contents

1. Permission Requirements
2. Page Overview
3. Emergency Trigger and Resolve Workflow
4. Tab 1 — Communications Hub
5. Tab 2 — Personnel Muster
6. Tab 3 — Event History
7. Tab 4 — Contacts
8. Tab 5 — Automation Rules
9. Tab 6 — Analytics
10. Tab 7 — Provider Health
11. Tab 8 — After-Action Report
12. Real-Time Updates
13. Mobile Access

---

1. Permission Requirements

Access to different functions on this page is controlled by your assigned role. The system checks permissions before displaying controls.

Action	Required Permission
View emergency information and muster list	emergency: read
Trigger a new emergency	emergency: trigger
Resolve an active emergency	emergency: resolve

If you open the Emergency page and see the message "You do not have permission to view emergency information," contact your system administrator to request the appropriate role.

Note: All users who are logged in and have at least emergency: read can view the live muster status during an active emergency. Only designated safety officers or administrators will have trigger and resolve permissions.

---

2. Page Overview

When you open the Emergency page, the screen is divided into three areas:

Command Header — A persistent header showing the page title. During a normal (non-emergency) state, a red "Trigger Emergency" button appears in the upper right. During an active emergency, this is replaced by a green "Resolve Emergency" button.

Active Emergency Banner — When an emergency is active, a pulsing red banner appears below the header displaying the scenario type (FIRE, MEDICAL, etc.) and the time the emergency was triggered.

Summary Statistics — Five tiles display real-time counts:

• Total Personnel — All personnel tracked in the system.
• In Building — Personnel whose BLE beacon was last detected inside the facility.
• Not Detected — Personnel with no recent beacon signal (location unknown).
• Accounted Safe — Personnel who have been confirmed safe (manually or by self-confirmation).
• Special Needs — Personnel flagged as requiring additional assistance.

Navigation Tabs — Eight tabs provide access to different sections. The tabs are described in sections 4 through 11 below.

Screenshot placeholder: Command header with active emergency banner and five summary tiles.

---

3. Emergency Trigger and Resolve Workflow

Triggering an Emergency

Important: Only users with the emergency: trigger permission will see an active "Trigger Emergency" button. If the button is greyed out, you do not have this permission.

1. Click the Trigger Emergency button in the upper-right corner of the page. A confirmation dialog opens.

2. Select the Scenario that best describes the emergency:

   • Fire Emergency
   • Medical Emergency
   • Security Threat
   • Severe Weather
   • Other Emergency

   Each scenario automatically determines which notification channels are used and how quickly escalations activate:

   Scenario	Channels	Repeat Interval
   Fire Emergency	SMS, Voice, Email — all immediately	Every 2 minutes
   Medical Emergency	SMS, Email — voice escalates after 3 minutes	On escalation
   Security Threat	SMS, Voice, Email — all immediately	None
   Severe Weather	SMS, Voice, Email — all immediately	Every 5 minutes
   Other Emergency	SMS, Email — escalates after 5 minutes	On escalation

3. Enter an optional Description providing additional detail (for example, "Fire reported in Building B, Floor 3 server room").

4. The Notify All toggle is on by default. Leave it on to immediately send notifications to all registered emergency contacts.

5. Click Trigger Emergency to confirm. The system activates the emergency, sends the first wave of notifications, and the page immediately updates: the header button changes to "Resolve Emergency," the active emergency banner appears, and the muster list begins tracking personnel.

Note: The triggering user's identity is automatically recorded (by email or display name). This appears in the event history and after-action report.

Resolving an Emergency

Important: Only users with the emergency: resolve permission will see an active "Resolve Emergency" button.

1. Once the situation is under control and all personnel are accounted for, click the Resolve Emergency button in the upper-right corner.

2. A confirmation dialog opens. Enter Resolution Notes describing what happened and how the emergency was resolved. These notes become part of the permanent event record and the after-action report.

3. Click Resolve Emergency to confirm. The system archives the event, the active emergency banner disappears, the summary statistics reset, and the "Trigger Emergency" button returns to the header.

4. The resolved event is immediately available in the Event History tab. If you need to write an after-action report, navigate to Tab 3 (Event History), find the event, and click View Report.

Screenshot placeholder: Trigger Emergency dialog with scenario dropdown and description field.

---

4. Tab 1 — Communications Hub

The Communications Hub is the first tab (index 0) and serves as the primary mass-notification interface. It combines a conversation-style inbox with composing tools for SMS, email, and voice.

Layout

The hub uses a split-panel layout:

• Left panel (Inbox) — Lists all communication threads grouped by contact. Each row shows the contact's name, the channel used (SMS, Email, or Voice), the last message, and whether there are unread replies.
• Right panel (Compose / Thread) — Displays the message thread for the selected contact, or a blank compose screen for a new message.

On mobile, only one panel is visible at a time. Tap a conversation to open it; use the back arrow to return to the inbox.

Sending a New Message

1. Click the New Message button (top-right of the inbox panel).
2. In the compose panel, select a Channel: SMS, Email, or Voice.
3. Enter the recipient (phone number for SMS/Voice, email address for Email) or search the recipient directory.
4. Type your message in the body field.
5. Optionally click Templates to insert a pre-written message (see Message Templates below).
6. Click Send.

Sending to an Existing Contact

1. Click on any conversation row in the inbox.
2. The thread panel loads the full message history with that contact.
3. Type a reply in the compose bar at the bottom and click Send.

Message Templates

Templates allow you to insert standardised emergency messages without typing them from scratch.

1. In the compose panel, click the Templates button.
2. The templates panel opens. Templates are filtered by the currently selected channel (SMS, Email, or Voice).
3. Click a template to insert its body text (and subject line, for email) into the compose fields.
4. Edit the text if needed, then send.

Tip: Templates are managed from within the Communications Hub. Administrators can create, edit, and delete templates. See the template management section for details.

Voice Dialer

For direct voice calls to individual contacts:

1. Click the Voice button in the hub toolbar to open the Voice Manager, which shows available voice recordings.
2. Click the Dialer button to open a keypad interface.
3. Enter or confirm the phone number and click Call.

Incoming Messages (Inbox)

If a contact replies to an SMS notification, their reply appears in the inbox with an unread indicator. Click the thread to view the reply and acknowledge it.

Screenshot placeholder: Communications Hub with inbox list on the left and compose panel on the right.

---

5. Tab 2 — Personnel Muster

The Personnel Muster tab (index 1) is the heart of the mustering operation. It shows the real-time location and safety status of every tracked employee.

Employee Self-Confirmation Banner

When an emergency is active, a self-confirmation card appears at the top of the Muster tab. Logged-in employees can tap I'm Safe or I Need Help to immediately update their muster status. This requires the user's account to be linked to a BLE beacon (set up by an administrator). If the account has no linked beacon, a warning is shown.

Filter Chips

Four filter chips appear above the personnel list. Clicking a chip filters the list to show only that group. The count shown on each chip updates in real time.

Chip	What it shows
All Personnel	Every tracked employee (total count)
In Building	Employees whose beacon is currently detected inside the facility
Not Detected	Employees with no active beacon signal (location unknown)
Special Needs	Employees flagged as requiring assistance

Searching Personnel

A search box in the toolbar allows you to search across name, employee ID, department, floor location, and phone number simultaneously. Results update as you type. To clear the search, click the X inside the search box.

View Modes

Three view modes are available via the toggle buttons to the right of the search box:

• Table View — A sortable, paginated data table with columns for Name, Employee ID, Department, Status, In Building, Special Needs, and Last Seen. Columns can be sorted by clicking the header. The table supports pagination (10, 15, 30, or 50 rows per page).
• Card View — A grid of cards, each showing the employee's name initials, name, department, status badge, and last known location. Cards are colour-coded by status (green = safe, amber = in building, red = special needs, grey = not detected). Pagination controls appear below the grid.
• List View — A compact one-row-per-person list. Pagination controls appear below. This is the default view.

Personnel Status Colours

Each employee is colour-coded to communicate urgency at a glance:

Colour	Meaning
Green	Confirmed safe
Teal / Blue	In building, beacon actively detected
Amber / Orange	Not detected (location unknown)
Red	Special needs flag is set — requires priority attention
Grey	No status information

Clear Filters

Click the Clear Filters button (funnel icon) to reset the search text and all filter chips back to "All Personnel."

Muster Completion

The summary statistics at the top of the page automatically calculate accountability progress. A personnel member counts towards completion when their status is "safe" or "evacuated." Monitor the "Accounted Safe" tile to track progress toward full accountability.

Screenshot placeholder: Personnel Muster tab in list view with filter chips and search bar.

---

6. Tab 3 — Event History

The Event History tab (index 2) provides a chronological record of all emergency events: both active and resolved.

Viewing the List

Events are displayed in reverse chronological order (most recent first). Each event shows:

• Event ID
• Scenario type (Fire, Medical, Security, etc.)
• Description
• Status (Active or Resolved)
• Date and time triggered
• Triggered by (user name or email)

Filtering and Searching

• Status filter — Use the status dropdown to show only Active, Resolved, or Drill events.
• Global search — Type in the search box to filter by description, triggered-by name, resolved-by name, or scenario.
• Column filters — In table view, individual column filter inputs are available for precise filtering.

Viewing Event Detail

Click any event row to open the event detail panel. The detail view shows full event information including resolution notes, personnel counts at the time of the event, and notification delivery statistics.

Viewing an After-Action Report

For resolved events, a View Report button is available in the event detail. Clicking it navigates directly to Tab 8 (After-Action Report) and loads the full report for that event.

Retrying Failed Notifications

If some notifications failed to deliver during the event, a Retry Notifications button appears in the event detail. Clicking it sends a fresh notification attempt to any contacts who did not receive the original message.

Screenshot placeholder: Event History tab showing a list of past events with status badges.

---

7. Tab 4 — Contacts

The Contacts tab (index 3) is the emergency contact directory — the list of people who will be notified when an emergency is triggered.

Contact List

Contacts are displayed in a table sorted by priority (Primary first, then Secondary, then Tertiary) and then alphabetically within each priority level. Each contact shows:

• Name
• Role (for example: Safety Officer, Floor Warden, Security Manager)
• Phone number
• Email address
• Priority level badge

Adding a New Contact

1. Click the Add Contact button (top-right of the Contacts tab).
2. A form dialog opens. Fill in:
   • Name (required)
   • Role (for example: Floor Warden)
   • Phone — used for SMS and voice notifications
   • Email — used for email notifications
   • Priority — Primary (1), Secondary (2), or Tertiary (3)
3. Click Save. The new contact appears in the list immediately.

Note: Both phone and email are optional fields, but at least one should be provided so the contact can actually receive notifications. The system validates phone and email format before saving.

Editing an Existing Contact

1. Find the contact in the list.
2. Click the Edit (pencil) icon on the contact's row.
3. The form dialog opens pre-filled with the contact's current details.
4. Make your changes and click Save.

Deleting a Contact

1. Find the contact in the list.
2. Click the Delete (trash) icon on the contact's row.
3. A confirmation prompt appears. Click Confirm to permanently remove the contact.

Warning: Deleting a contact removes them from future notifications. Past event records that reference them are not affected.

Searching Contacts

Use the global search box at the top of the Contacts tab to search across name, role, phone, and email simultaneously.

Screenshot placeholder: Contacts tab showing contact list with priority badges and action buttons.

---

8. Tab 5 — Automation Rules

The Automation Rules tab (index 4) contains the notification rule engine — an IF-THEN workflow builder that determines who gets notified, on which channel, and when, based on conditions you define.

Rules List

The rules list shows all configured rules. Each rule displays:

• Rule name
• A summary of its trigger conditions
• Active / Inactive status toggle
• Number of times the rule has executed

Two counts at the top of the list show how many rules are currently Active vs Inactive.

Enabling and Disabling a Rule

Click the toggle switch on any rule row to activate or deactivate it without deleting it. A confirmation toast message confirms the change.

Creating a New Rule

1. Click the Create Rule button.
2. The visual Workflow Builder opens — a drag-and-drop canvas interface.

Workflow Builder

The Workflow Builder uses a three-panel layout:

• Left — Node Palette: Lists available node types you can drag onto the canvas:

  • Trigger — The event that starts the rule (for example: "Emergency triggered with scenario = Fire")
  • Condition — A filter that must be true for the workflow to proceed (for example: "Time of day is between 08:00 and 18:00")
  • Action — What to do when conditions are met (for example: "Send SMS to all Primary contacts")
  • Delay — Wait a specified number of minutes before the next step
  • Repeat — Repeat an action at a defined interval

• Centre — Canvas: A visual flowchart where you connect nodes. Drag a node type from the palette onto the canvas, then draw connections between nodes by clicking and dragging from a node's output port to another node's input port.

• Right — Properties Editor: When you click a node on the canvas, its configuration panel opens on the right. Set the specific values for that node (for example, which channel to use, which recipient group, how many minutes to delay).

Saving a Rule

1. Enter a Rule Name at the top of the builder panel.
2. Build your workflow on the canvas.
3. Click Save Rule. The rule is saved and you are returned to the rules list.

Editing an Existing Rule

1. Click the Edit (pencil) icon on the rule's row in the rules list.
2. The Workflow Builder opens pre-loaded with the existing rule's nodes and connections.
3. Make your changes and click Save Rule.

Deleting a Rule

1. Click the Delete (trash) icon on the rule's row.
2. Confirm the deletion in the prompt. The rule is permanently removed.

Execution History

Click the Execution History button to see a log of the last 10 times rules were evaluated and executed. Each entry shows which rule ran, when it ran, and whether it succeeded.

Tip: Use the Delay node to build escalation chains — for example, "Send SMS immediately, then wait 5 minutes, then send a voice call if no confirmation received."

Screenshot placeholder: Automation Rules tab with the Workflow Builder open showing a three-node workflow.

---

9. Tab 6 — Analytics

The Analytics tab (index 5) provides charts and statistics showing how emergency events have performed over time. This view is for trend analysis and planning rather than live incident management.

Date Range

Select a date range from the dropdown at the top of the tab:

• Last 7 Days
• Last 30 Days (default)
• Last 90 Days

The charts update automatically when you change the range.

Metrics Displayed

• Total Events — The number of emergency events in the selected date range.
• Average Time to Confirmation — How long it took, on average, for the first personnel confirmation to be received after an emergency was triggered (in seconds).
• Confirmation Rate by Channel — The percentage of recipients who confirmed receipt via SMS, Email, and Voice respectively.
• Events Over Time — A bar chart showing the number of emergency events per day across the selected date range, with the average confirmation time overlaid.

Note: If the analytics data endpoint is not yet configured on your installation, the tab will display a "Data not available" message. Contact your system administrator if you require this data.

Screenshot placeholder: Analytics tab with bar chart showing events over time.

---

10. Tab 7 — Provider Health

The Provider Health tab (index 6) displays the operational status of the external services used to send SMS, email, and voice notifications. Facility managers and IT administrators use this tab to quickly identify if a notification channel has a problem.

Provider List

Each configured provider is shown as a card or row containing:

• Provider Name — For example: Azure Communication Services, Twilio SMS, Twilio Voice.
• Status — One of three states:
  • Healthy (green) — The provider is responding normally.
  • Degraded (amber) — The provider is responding but slower or less reliably than expected.
  • Down (red) — The provider is not responding.
• Response Time — The time in milliseconds for the last health check.
• Success Rate — The percentage of recent requests that succeeded.
• Circuit Breaker State:
  • Closed (Normal) — The provider is operating normally; all requests are sent through.
  • Half-Open (Testing) — The provider recently failed; the system is sending test requests to check recovery.
  • Open (Blocked) — The provider has failed repeatedly; requests to this provider are temporarily blocked to prevent further errors.
• Last Checked — The timestamp of the most recent health check.
• Error Count / Total Requests — Running counters for monitoring trends.

Testing a Provider Connection

1. Find the provider you want to test.
2. Click the Test Connection button on that provider's card.
3. The system sends a test request and reports the result with a toast notification.

Note: The page automatically refreshes provider health data every 30 seconds. You do not need to manually refresh.

Tip: If a critical provider (SMS or Voice) shows a "Down" or "Open (Blocked)" status before an expected drill or high-risk period, contact your IT team immediately. Notifications will not be delivered through that channel until the provider recovers.

Screenshot placeholder: Provider Health tab showing three provider cards with status indicators.

---

11. Tab 8 — After-Action Report

The After-Action Report tab (index 7) is only visible when a specific resolved event has been selected for review. It provides a structured post-event analysis of what happened, how quickly the system responded, and what can be improved.

Accessing an After-Action Report

The After-Action Report tab only appears in the navigation bar after you select a resolved event for reporting. There are two ways to access it:

• From Event History: Navigate to Tab 3 (Event History), click a resolved event to open its detail, then click View Report. The page automatically opens Tab 8 loaded with that event's data.
• Direct navigation: If you have already opened a report in the current session, Tab 8 remains visible and you can click it directly.

Report Sections

Event Summary

At the top of the report, the key event details are shown:

• Scenario type and description
• Status (Resolved)
• Date and time triggered
• Date and time resolved
• Triggered by / Resolved by

Timeline

A visual timeline shows the sequence of key moments during the event:

1. Emergency Triggered
2. First Notification Sent (time from trigger to first outbound message)
3. First Confirmation Received (time from trigger to first personnel acknowledgement)
4. Emergency Resolved

Tip: Gaps between timeline events highlight areas for improvement. A long gap between "Emergency Triggered" and "First Notification Sent" may indicate a slow notification provider or misconfigured automation rules.

Response Metrics

Four key performance indicators are displayed:

• Time to First Notification — How many seconds elapsed between the emergency being triggered and the first notification leaving the system.
• Time to First Confirmation — How many seconds elapsed before the first personnel member confirmed safe status.
• Time to Full Accountability — How many seconds elapsed before all personnel were accounted for (either confirmed safe, evacuated, or confirmed unreachable).
• Total Duration — The total time in seconds from trigger to resolution.

Personnel Accountability

A summary of personnel outcomes:

Metric	Description
Total	Total number of tracked personnel at the time of the event
Confirmed	Personnel who confirmed their status during the event
Unreachable	Personnel who could not be contacted
Failed	Personnel whose confirmation attempts encountered system errors

Notification Delivery Statistics

A breakdown per channel (SMS, Email, Voice) showing:

• Messages Sent
• Messages Delivered (confirmed receipt)
• Messages Failed

Escalations

If any automatic escalation rules activated during the event, each escalation is listed with:

• Escalation level number
• The time it triggered
• The reason (for example, "No confirmation received after 5 minutes")
• The channel used for the escalation

Lessons Learned

A free-text field where the report author can document observations, problems, and recommendations for improving future response. This field is editable.

1. Click in the Lessons Learned text area.
2. Type your observations.
3. Click Save Lessons Learned to persist the notes to the event record.

Generating a Report Document

Click the Generate Report button to produce a downloadable document version of the after-action report. A download link opens in a new browser tab.

Screenshot placeholder: After-Action Report tab showing the event timeline and response metrics.

---

12. Real-Time Updates

The Emergency page subscribes to the real-time BLE event stream as soon as it loads. This means:

• The In Building count and the personnel muster list update automatically as BLE beacons are detected or lost — no manual refresh required.
• The Not Detected count rises if a beacon signal is lost (the person may have left the building or their badge battery is depleted).
• The Accounted Safe count increments as personnel confirm their status via self-confirmation.

Real-time updates run for as long as the Emergency page is open. If you navigate away and return, the page reconnects to the event stream and reloads current data.

Note: Real-time updates depend on an active connection to the backend. If the connection is interrupted, the page will continue to display the last known data until connectivity is restored.

---

13. Mobile Access

The Emergency page is fully functional on mobile devices (phones and tablets). The mobile layout differs from desktop in the following ways:

• Summary Statistics — Displayed as a horizontal scrollable row of four tiles: Total, Safe, In Building, and Unaccounted.
• Trigger / Resolve — The trigger and resolve actions appear as buttons within the mobile view, respecting the same permission checks as desktop.
• Personnel Muster — The muster list is rendered as a compact mobile-optimised list. Search and filter controls are accessible via a filter panel.
• Communications Hub — Uses a master-detail navigation pattern: the inbox list fills the screen, and tapping a conversation slides to the thread view. A back arrow returns to the list.

Tip: On mobile, if you need to perform multiple tasks quickly (for example, checking the muster list and sending a notification), use the tab navigation at the bottom of the screen to switch between sections without leaving the page.

---

Quick Reference: Tab Index

Tab Number	Tab Name	Primary Use
0	Communications Hub	Send SMS, email, and voice notifications; manage message templates
1	Personnel Muster	Live personnel tracking, search, filter, and self-confirmation
2	Event History	Review past and active emergency events
3	Contacts	Manage emergency contact directory
4	Automation Rules	Configure IF-THEN notification workflows
5	Analytics	Review response-time trends and confirmation rates
6	Provider Health	Monitor SMS, email, and voice provider status
7	After-Action Report	Post-event analysis (visible after selecting a resolved event)