Fire Alarm and Egress Interface: The Test Plan a Buyer Should Demand
This fire alarm and egress interface test plan is a bidder-return document, not a generic inspection checklist. It defines the signals that cross each boundary, the state expected when one is absent, the owner of the clock and correction, and the evidence required to close each test. Issue it with the bid package, require deviations to be listed, and make witnessed execution part of acceptance.
Direct answer. The one-line answer — fire alarm and egress interface test plan is the working record for fire alarm and egress interface test plan. fire alarm and egress interface test plan is worthless until fire-alarm-and-egress-interface is attached to it as evidence. A fire alarm and egress interface test plan traces one integration from lock to reader to record. fire alarm and egress interface test plan marks the handover point. fire alarm and egress interface test plan cannot be improvised there.
Throughout, fire alarm and egress interface test plan means what fire alarm and egress interface test plan sets out. It is a working definition of fire alarm and egress interface test plan drawn from the evidence below. It is valid for the specific market and product, not as a general claim.
Issue-for-Bid Status and Required Bidder Response
Use this sheet as a signed contract return. The selected bidder must complete it before acceptance testing begins. A general proposal, product description, or meeting note does not close a scheduled item. The build options sit in the smart door locks.
The bidder shall apply these response rules:
- TS-01.1: Mark every clause as Compliant, Exception, Alternative, Not Applicable, or Deferred by Written Agreement.
- TS-01.2: Identify each exception against the clause number, the affected door or interface, the proposed correction, and the evidence needed for closure.
- TS-01.3: Name the party responsible for diagnosis, correction, witness attendance, and record production at each interface boundary.
- TS-01.4: Submit a proposed test sequence and a separate list of assumptions that require client or authority approval.
- TS-01.5: Do not mark a field result as passed without the evidence listed in this sheet.
| Return item | Required bidder entry | Acceptance rule |
|---|---|---|
| Compliance schedule | Status and clause reference for every row | No blank status |
| Exception schedule | Affected door, deviation, proposed correction, evidence required | Each exception is separately priced or contractually dispositioned by the client |
| Responsibility schedule | Named role for each test and witness | No generic team name without an accountable role |
| Evidence index | Artifact, test reference, custodian, and storage location | Every passed test must point to retained evidence |
| Proposed test sequence | Order, prerequisites, isolation method, and rollback step | The sequence must fit the approved door schedule |
Blank cells are not compliant responses. “As required,” “standard,” and “per code” are not acceptable substitutes for a documented interface value, test method, or named responsibility.
Scope Boundary and Controlled Vocabulary
The scope includes each selected smart lock or electromechanical locking device, its controller, the exit device, door position contact, power supply, access-control platform, fire-alarm endpoint, network path, and monitoring or audit service. The bidder must identify where its responsibility ends and where the next supplier begins.
The control boundary must be explicit. The fire-alarm side reports an approved event or indication; the designated controller applies the approved sequence; the approved door hardware executes the resulting state. Release is not assigned as a discretionary fire decision to the smart lock. The lock reports the state; the system decides what the state means.
For every proposed SKU, confirm on the dated product page for the specific SKU whether the relevant electrical interface, contact arrangement, local control behavior, and required accessory are available. If the dated page does not settle the point, the bidder must identify it as unverified and obtain written manufacturer confirmation before acceptance. This sheet grants no product capability.
| Term | Working definition for this test plan |
|---|---|
| Fire indication | An approved event or signal received from the fire-alarm side and mapped to a defined action |
| Release command | An output that authorizes or causes a door to reach its project-approved released state |
| Request to exit | A signal reporting operation of the exit device from the escape side; it is not a release command |
| Fail-safe | The project-approved state when a defined power or system condition is removed |
| Fail-secure | The project-approved state when a defined power or system condition is removed |
| Controller | The device that holds door state and applies the approved decision logic |
| Audit log | A retained record containing a time, source, event, and outcome |
| Event memory | A device-held buffer used when the central service cannot be reached |
CONFIRM-WITH-LOCAL-FIRE-AUTHORITY: The approving authority, fire-alarm service contractor, and egress reviewer must confirm the project-specific cause-and-effect matrix, reset sequence, release scope, and witnessed test method in writing.
Pre-Bid Door and Interface Schedules
A test cannot be written against an unidentified boundary. Before finalizing its response, each bidder must return a door-by-door schedule, an interface register, and a deviation schedule. The schedules must reconcile rather than repeat one another.
The door schedule shall identify the opening, controlled side, escape side, exit device, locking device, controller, door position contact, electrical source, assigned fire indication, normal state, required fail state, RTE monitoring point, and approved reset behavior. The interface register shall identify the two endpoints, signal direction, normal condition, active condition, supervision, loss-of-signal response, and evidence source.
Where opening or power conditions remain unresolved, request a scoped Smart Lock Retrofit Site Survey or Office Smart Lock Site Survey rather than treating a generic product sheet as site evidence. The Fire Alarm and Egress Interface Requirements Document Template can serve as the source schedule, but the bidder must return it completed.
| Schedule | Minimum fields | Required stage |
|---|---|---|
| Door schedule | Door identifier, sides, hardware, controller, power, contacts, normal state, fail state | Before technical review |
| Interface register | Endpoints, direction, signal meaning, supervision, timeout, loss behavior | Before test scripting |
| Cause-and-effect matrix | Trigger, affected doors, excluded doors, order, reset, logging | Before witnessed testing |
| Responsibility schedule | Diagnose, correct, witness, approve, retain evidence | Before contract award |
| Deviation register | Clause, affected door, proposed alternative, closure evidence | Updated after every design change |
The bidder must also state which document controls when drawings, manufacturer instructions, controller configuration, and the cause-and-effect matrix differ. Unresolved conflicts are exceptions, not field decisions.
Signal Contract, Decision Ownership, and Evidence
The following is a logical test path, not a mandate for a particular panel topology. The bidder must replace the generic roles with the components named in the approved design.
flowchart LR
A[Approved fire indication] --> B[Named interface endpoint]
B --> C[Controller state update]
C --> D[Approved release decision]
D --> E[Door hardware response]
E --> F[State and event evidence]
C --> G[Fault and audit records]
During access control integration testing, the buyer proves that the fire alarm system interface carries an agreed event, rather than merely showing that a wire is present. Each script must define what the sender asserts, how the receiver identifies it, what remains true while the signal is absent, and which component logs the result.
| Decision | Fire-alarm side | Access-control and lock side | Required evidence | Bidder response |
|---|---|---|---|---|
| Recognize the event | Identifies the source and mapped point | Accepts only the defined indication | Panel or test-tool output | State whether recognition is proven |
| Apply the action | Supplies the approved trigger | Applies the cause-and-effect matrix | Configuration export | State the decision owner |
| Execute at the door | No direct execution assumed | Drives the approved release path | Door position before, during, and after | State the controlled output |
| Handle signal loss | Reports or supervises the condition as designed | Applies the approved loss behavior | Fault record and door state | State whether loss is distinguishable |
| Reset or clear | Sends the approved reset event | Applies the approved re-lock sequence | Ordered event log | State the reset owner |
| Preserve evidence | Identifies its clock source | Retains state, event, and sequence data | Export with source timestamps | State custody and access |
The contract should identify the exact component that owns the release decision, rather than saying that the “system” handles it. The Who Owns Fire Alarm and Egress Interface: Supplier, Integrator or Client allocation should be reduced to named roles for diagnosis, configuration, correction, and record production.
Every signal row shall also state whether its meaning is edge-triggered, level-held, latched, or time-bound. Continuity without agreed semantics is not an accepted interface.
Test Governance, Clock Ownership, and Readiness
The bidder must nominate one test authority and one record authority. Different firms may perform the work, but the witness must know who may change a cause-and-effect setting, who may return a door to service, and who may approve a retest.
| Role | Accountable contribution |
|---|---|
| Client or project authority | Approves the project matrix, witnesses results, and decides unresolved deviations |
| Fire-alarm service contractor | Provides the approved stimulus, explains point mapping, and supplies panel evidence |
| Access-control integrator | Configures the controller, demonstrates its logic, and exports relevant records |
| Lock or door supplier | Explains local behavior, wiring, accessories, and the selected SKU evidence |
| Security or operations representative | Confirms receipt, notification, and operational workflow expectations |
| Named test witness | Executes the script, records observations, and signs each result |
The bidder must nominate one authoritative event clock and an administrator responsible for it. At test start, record the clock source, time representation, synchronization method, and observed offset for the controller, server, fire-alarm endpoint, and test tool. Use a sequence identifier to order events that share a timestamp. The owner of the clock also owns the procedure for correcting drift and reconciling events after a failed or interrupted test.
Site testing may begin only after the following prerequisites are evidenced:
- Current approved drawings and door schedule.
- Approved cause-and-effect and reset matrices.
- A written and safe stimulus method for each fire test.
- Named witnesses and communication channel.
- Test credentials and rollback credentials.
- A documented controller test mode.
- Isolation and restoration steps.
- Temporary door and room identification.
- Access to relevant event logs and exports.
- A procedure for stopping the test safely.
CONFIRM-WITH-LOCAL-FIRE-AUTHORITY: The client and named witness must approve the test method, isolation boundary, restoration sequence, and authority to return each door to service before test execution.
Fire-Indication Test Cases
For fire alarm interface testing, the bidder shall use a controlled stimulus selected by the fire-alarm service contractor and accepted by the named witness. The method must state how the event is generated, how it is mapped, how it is removed, and how the installation is returned to normal.
| Test | Controlled stimulus | Expected observation | Evidence to retain | Accountable role |
|---|---|---|---|---|
| FIR-01 | No fire indication | Doors remain in their scheduled normal state | Door states and absence of release events | Access-control integrator |
| FIR-02 | Approved remote or group indication | Only doors listed in the approved matrix reach their approved released state | Ordered events and before, during, and after door states | Fire-alarm contractor |
| FIR-03 | Approved local initiating event | The correct point mapping and resulting door group are demonstrated | Point-to-door trace | Fire-alarm contractor |
| FIR-04 | Fire indication and credential request overlap | The approved priority and event order are reproducible | Both request records, release result, and timestamps | Named witness |
| FIR-05 | Fire-interface signal removed or supervised as faulty | The condition is not silently converted into an alarm; the approved loss behavior occurs | Fault record, door state, and controller output | Access-control integrator |
| FIR-06 | Approved reset or clear event | Re-lock or re-arm occurs only at the defined point in the sequence | Complete ordered event history | Client or project authority |
| FIR-07 | Controller or central service unavailable during the indication | The approved degraded behavior applies and remains identifiable | Local state, fault record, and restoration action | System owner |
| FIR-08 | Supply interruption and restoration | The approved power state and recovery sequence are demonstrated | Power event, door state, controller state, and recovery log | Facilities and system owner |
| FIR-09 | Sustained or repeated indication | The input is handled according to its defined latching or hold behavior | Raw event sequence and final state | Controller integrator |
A test passes only when the stimulus, mapped point, affected doors, event order, resulting state, and record evidence agree with the approved matrix. A door outside the matrix must not change unless the schedule contains a specific, approved exception. The bidder must not infer that the intended sequence occurred merely because a release was observed.
For every failed case, capture the input state, controller output, door position, event records, clock readings, and operator actions. Use the Fire Alarm and Egress Interface Failure Patterns and How to Recover to classify the fault boundary, but retain the project’s own evidence and approved recovery sequence.
Egress and Request-to-Exit Test Cases
Egress release verification separates physical escape from signal reporting. Request-to-exit signal testing confirms that an RTE event reports operation of the exit device; the RTE signal is not used as the release command. Release on the escape side is the default behavior of the exit device.
| Test | Action | Expected observation | Evidence to retain |
|---|---|---|---|
| EGR-01 | Operate the exit device from the escape side | The door reaches the approved released state and the RTE event is observed | Door sequence and corresponding RTE record |
| EGR-02 | Operate the exit device while the central service is unavailable | Local behavior follows the approved exit-device and controller schedule | Local controller state and any stored event |
| EGR-03 | Remove the defined supply under an approved test method | The door reaches the fail-safe or fail-secure state named for that opening | Supply state, lock state, and fault indication |
| EGR-04 | Do not operate the exit device | No RTE event is generated by the test | Controller event history over the test window |
| EGR-05 | Combine an RTE operation with a fire indication | The combined sequence follows the approved matrix without an unrecorded state change | Ordered events, both inputs, and door state |
| EGR-06 | Hold the door open after operating the exit device | The door-position transition is recorded separately from the RTE operation | RTE event and subsequent door-position event |
| EGR-07 | Return the door to normal service | The lock, controller, and exit-device states return to the approved condition | Final configuration and position evidence |
The expected result must come from the approved door schedule, not from a general statement that a door “fails open” or “fails locked.” The bidder must document whether a local release, remote release, or independently operating exit device was tested and where the evidence was taken.
CONFIRM-WITH-LOCAL-FIRE-AUTHORITY: The egress reviewer and fire-alarm service contractor must approve the exact RTE, door-position, power-loss, and combined-event tests for each door class before execution.
Degraded-Mode and Power-State Testing
Fail-safe door testing means checking the state named in the project matrix; it does not turn a product label into an acceptance result. Every unavailable component needs an expected state, a detectable condition, a recovery path, and an accountable owner.
| Test | Condition introduced | Expected result to be proven | Required evidence |
|---|---|---|---|
| DEG-01 | Network partition between controller and service | The approved local behavior continues and any loss indication is recorded | Local state, network status, and event memory |
| DEG-02 | Central server unavailable | The door does not inherit an undocumented server state | Door state, controller log, and local decision trace |
| DEG-03 | Access controller unavailable or isolated | The project-approved door state and access to the door are demonstrated | Power and controller status, door position, and witness record |
| DEG-04 | Fire-alarm interface link lost | Loss is distinguished from an approved alarm indication and handled as specified | Supervision output, fault record, and resulting state |
| DEG-05 | Primary building supply removed | The approved transition occurs without an undocumented release | Supply trace, lock state, controller state, and records |
| DEG-06 | Backup supply transition or restoration | The door remains within the approved state sequence until recovery completes | Supply events and final controller state |
| DEG-07 | Lock battery low or depleted under the approved method | The warning or resulting state is demonstrated as a distinct condition | Device indication, local door behavior, and event record |
| DEG-08 | Door-position contact open, closed, or disconnected | The controller reports the observed state and handles it according to the schedule | Raw contact state, reported state, and event |
| DEG-09 | RTE monitoring path interrupted | The interruption is distinguishable from an actual exit operation | Circuit or interface diagnostic and event history |
The offline case is the design, not the exception. A bare answer such as “fails locked” is an approval question, not an engineering conclusion. The bidder must distinguish building-power loss, low lock battery, controller loss, server loss, and communication loss because they can produce different observable states.
For each condition, record when the disturbance was introduced, how the system detected it, the door state during the disturbance, the records available locally and centrally, the restoration action, and the final stable state.
Records, Event History, and Personal Data
The buyer must be able to answer what was written down, where it lives, and who can read it. The audit log and event memory serve different purposes. The audit log is the retained event record; event memory is the buffer used when a device cannot reach the central service. Acceptance must prove both paths where event continuity is required.
Each relevant record should identify the event time and source, the door and event type, the trigger or cause, the resulting state, the configuration version, and a sequence value that preserves order. When an operator action causes the event, the record must distinguish that action from the original fire indication or RTE operation. A later database entry must not replace the original event history.
The bidder must demonstrate an export or readback after the network, server, controller, and test tool have each carried a transaction. The export must retain source timestamps, ordering information, and the distinction between live, buffered, delayed, and restored records.
Personal data requires a separate decision. The bid must state who may view individual door-use records, which roles may export them, and how operational fire testing is separated from routine access reporting. Do not use a fire test to collect unnecessary identity data.
CONFIRM-WITH-LOCAL-PRIVACY-REVIEWER: The client must confirm the permitted event fields, retention period, reader roles, export controls, and any personal-data treatment associated with door events for the installed system.
Acceptance Gates, Deviations, and Retesting
A passed test closes one defined interface behavior. It does not establish acceptance for the whole building or every door. The bidder and witness must sign each result separately, and any design or firmware change that can alter behavior requires impact review and targeted regression testing.
| Acceptance gate | Pass condition | Fail condition |
|---|---|---|
| Trigger | The scripted stimulus reaches the named endpoint with the correct mapping | The source, point, or mapping cannot be demonstrated |
| Decision | The approved matrix produces the expected action | The action depends on an undocumented assumption |
| Door response | The controlled door set reaches the expected state | The wrong door changes or the required door does not |
| Event history | The source event, action, and outcome remain identifiable and ordered | Records are missing, duplicated beyond the approved design, or ambiguous |
| Degraded behavior | The defined unavailable state and recovery are reproduced | The result varies without explanation |
| Evidence | The required export, images, logs, and witness record are complete | A verbal assurance is the only support |
The bidder must classify deviations without using a defect category to imply regulatory acceptance. Any deviation that leaves the expected release, egress, or restoration behavior unverified remains open. A documentation discrepancy with no observed behavior change is handled separately from a functional mismatch.
For a failed test, freeze the evidence, identify the suspect boundary, correct the cause, and repeat the original script. Then run every connected test whose shared input, configuration, output, or record path may have changed. A correction that passes only one retest does not close the shared cause-and-effect matrix.
Fix Ownership and Escalation
Which side owns the fix? The answer must be attached to the interface boundary, not left to a general telephone call. A role may investigate more than one boundary, but the schedule must identify who may change the configuration or hardware and who verifies the correction.
| Boundary | Diagnosis owner | Correction owner | Evidence owner |
|---|---|---|---|
| Fire-alarm point or event source | Fire-alarm service contractor | Fire-alarm service contractor | Named test witness |
| Fire-to-access interface mapping | Joint review between the two integrators | Controller configuration owner | Access-control integrator |
| Controller decision logic | Access-control integrator | Access-control integrator | Access-control integrator |
| Lock, exit device, or door hardware | Relevant supplier or installer | Relevant supplier or installer | Named test witness |
| Power and network availability | Facilities or network owner | Facilities or network owner | Operations representative |
| Event storage and export | Platform or service owner | Platform or service owner | Client record custodian |
The bidder must state the escalation path for a fault found during factory testing, installation, commissioning, and normal operation. Each escalation record should contain the test reference, affected boundary, observed state, event sequence, suspected owner, agreed corrective action, retest scope, and final evidence. Responsibility for investigating a symptom does not transfer responsibility for fixing the underlying cause.
The practical counterpart to this point is the smart lock event management. That is the same question fire alarm and egress interface test plan has to answer here.
Handover Package and Award Condition
The handover package must let a reviewer reconstruct the approved interface without relying on the memory of the commissioning team. It must also show which observations came from the selected SKU evidence and which came from the installed system.
| Handover artifact | Required content |
|---|---|
| Approved interface schedule | Final endpoint, signal meaning, loss behavior, and owner |
| Door and cause-and-effect schedule | Final door states, fire actions, RTE points, and reset sequence |
| Executed test scripts | Stimulus, steps, expected result, actual result, and witness sign-off |
| Event exports | Source timestamps, ordering, source identity, and restoration records |
| Clock record | Clock source, administrator, synchronization method, and drift check |
| Product evidence register | Dated product-page captures and written confirmations relied upon |
| Deviation and retest record | Open status, correction, retest scope, and closure evidence |
| Operational ownership matrix | Escalation route, record custodian, and maintenance responsibility |
Make the completed door release test plan, witnessed results, and unresolved exceptions a condition of acceptance. Issue the same controlled sheet to every bidder, require each bidder to return the schedules with its offer, and require the selected bidder to close every exception before the installation is accepted. A clean panel display or a successful credential test is not evidence that the fire alarm and egress interface has been proven.
Put the answer on paper and request a quote against that document.

