Skip to main content

Fire Systems Technical Requirements Specification

A Technical Requirements Specification (TRS) turns the fire safety objectives into verifiable requirements for each fire system, set before procurement.

What a fire systems TRS is

A Technical Requirements Specification is the requirements baseline for a fire system or a family of fire systems. It takes the fire safety objectives set in the fire strategy and turns them into requirements a designer can design to, a contractor can price and install to, and the client can verify at testing, commissioning and handover. Each requirement is a single testable statement, traced to its source: legislation, a standard, the client’s own requirements or a project decision.

The TRS is the first document in the fire engineering assurance chain. The Concept Design Statement, the detailed design, the Materials Compliance Register, the inspection and test plans, the commissioning test plans, the cause and effects matrix, the Authority to Use inspection and the operation and maintenance manuals all follow from it. Our fire engineering assurance service tracks that hierarchy from top to bottom.

When you need one

  • Before a fire system is procured. Tenderers price the same requirement, and the design that follows has a fixed baseline to be checked against.
  • From option selection. The TRS is started once an option is chosen and developed through concept design, so the design has a set of requirements to meet.
  • On an upgrade at a station in service. The new system has to work with the existing installation and with station operations, and the TRS records both.
  • Across a portfolio of stations. One specification can set common requirements for the portfolio while each station keeps its own delivery scope.

A TRS written after design has started tends to describe the design rather than bound it. We write it early, from the fire safety objectives, so the requirements lead and the design follows.

What a TRS bounds

  • Scope and boundaries. What the specification covers, what it excludes, and where each system meets another system or discipline.
  • Performance. The functional and performance requirements for each system: coverage, system category, response times, the operating environment and design life.
  • Interfaces. The cause and effects, the interfaces with door release, lift recall, smoke control and ventilation, the interface with any existing system, and the interface with station operations.
  • Standards. The legislation, the codes of practice and, on London Underground premises, the Category 1 standards that apply, with any known departure identified at the start so it can follow the concession route.
  • Acceptance criteria. How each requirement will be verified, by inspection, test, demonstration or analysis, and how the requirements together are validated against the fire safety objectives.
  • Testing and commissioning. Factory and site acceptance testing, commissioning, integrated testing across systems, and validation of the cause and effects.
  • Handover evidence. The operation and maintenance manuals, training, spares, warranties and the asset information the operator needs to maintain the system.
  • Quality and maintainability. Product approval, installer competence, access for maintenance and planned maintenance.

How we write it

  1. Start from the fire strategy. Read the fire safety objectives and the premises designation. Railway stations are designed to BS 9992:2020, the code of practice whose scope covers surface, sub-surface and enclosed stations; on London Underground premises the code of practice is selected by the scope of the works. Our BS 9992 fire strategy page covers that work.
  2. Establish the standards that apply. On London Underground premises, the Category 1 standards S1081 (passive) and S1082 (active) set the requirements for the design, installation, testing, commissioning and handover of fire safety systems, each applying by its own scope. Both require a written specification before a system is designed or modified, for review and acceptance by TfL. A TRS therefore carries the London Underground requirements alongside the British Standards. A planned departure from a London Underground standard is identified in the TRS and routed as an S1641 concession.
  3. Survey the existing installation. On an upgrade, record the existing system and the constraints it places on the new one.
  4. Write the requirements. One testable statement per requirement, each traced to its source. Requirements state performance, not a product: no product is specified as compliant because it was accepted elsewhere.
  5. Fix the interfaces. Record every interface in an interface schedule and set the cause and effects requirements the system must meet.
  6. Define verification. Set the verification method for each requirement, the testing and commissioning sequence, and the handover evidence the contractor must supply.

Where S1085 applies on London Underground premises, the TRS carries its materials requirements, and we then assess each product against it on its own evidence. Our S1085 materials compliance page sets out that work.

We write the specification and review the designs and contractor records against it. We do not install, test or commission directly: the contractor does, and we witness and review the testing and commissioning against the specification.

On TfL’s Jubilee Line Extension equal egressibility and EVC programme across eight sub-surface stations, JWCS authored the Options Development Report and the portfolio-level Technical Requirements Specification. The TRS bounded the EVC, refuge and compartmentation provisioning as a single procurement package, a structure that supports a unified procurement strategy with station-specific delivery packages. The project page sets out the role in full.

The TRS is one of the documents within our fire systems consultancy. We also review Technical Requirements Specifications prepared by others as part of our technical and peer review service.

Typical deliverables

  • Technical Requirements Specification for a single fire system or a portfolio of systems
  • Each requirement traced to its source, with how it is to be verified
  • Interface schedule and cause and effects requirements
  • Known departures from standards identified for the S1641 concession route
  • Review comments on a TRS prepared by others

Governing Framework

BS 9992:2020BS 5839-1:2025BS 5839-9:2021BS EN 12845:2015+A1:2019BS EN 15004-1:2024BS 9990:2015BS 7273-4:2015+A2:2023BS EN 12101 seriesS1081S1082S1641

Lifecycle stages

GRIP 3-7 / Pathway 1-5. Started at option selection, developed through concept design, then maintained under change control as the baseline for verification through to handover.

Related projects

Insights

Part of our Fire Systems Consultancy service.

Discuss this service

Senior-led from the first conversation.

Contact