Fire Protection System Automation (FPSA)

Why do “disjointed” fire protection systems pose a greater risk than no fire protection systems?

The fire alarm detected a fire, but the ventilation continued to circulate air, fanning the flames, the valves did not close, the smoke exhaust system did not start, and the doors along the escape route remained blocked. The alarm system fulfilled its function, the equipment was working properly - but no one made sure that all these systems worked as a single whole in the required sequence. This is where the main danger lies that construction companies face when commissioning projects: the systems are designed in separate sections, each according to its own standards, and the logic of interaction between them is not written down anywhere.

FPSA (automation of fire protection systems) is a control level that connects all subsystems of the fire protection complex into a single response scenario. AYU-Project designs FPSA for industrial, commercial and residential applications in strict accordance with SP 484.1311500.2020 (with Change No. 1, effective from 01.09.2025), SP 7.13130.2013, Federal Law No. 123-FZ and current regulatory framework. Our design documentation and working documentation contain a complete control matrix - from the input signal to a specific command to a specific actuator - and are accepted by experts from the first presentation.

What is FPSA and how is it fundamentally different from FAS and EVAC?

FPSA is neither an additional alarm system nor part of the voice-alarm system; it is the control layer for the fire-protection systems of the fire protection complex, which receives a reliable fire signal from the fire protection system and, according to programmed algorithms, generates commands for all engineering systems of the building involved in fire protection. The division of functions looks like this: SPS - detects and classifies the threat; SOUE - informs people and directs evacuation; ASPS - manages engineering, providing a safe environment for evacuation and preventing the spread of fire and smoke.

Without ASPZ, even ideally installed smoke exhaust valves, booster fans and fire arresting valves remain mechanisms that require manual control - in a real fire this is almost impossible. That is why, at capital construction sites, ASPZ is not an optional, but a mandatory component of the fire protection complex.

What controls FPSA: a complete set of engineering functions

FPSA combines into a single response algorithm all the building’s engineering systems that are activated in the event of a fire. The composition of management functions is determined by the composition of engineering systems at a particular facility and is specified in the technical specifications, however, the typical list includes the following.

Ventilation and smoke protection (smoke ventilation):

• turning off general exchange and recirculation ventilation in the fire zone (and adjacent zones according to the scenario) is a mandatory requirement Federal Law No. 123-FZ And SP 7.13130.2013: general ventilation should not operate simultaneously with smoke ventilation in the same volume;
• closing fire-retarding valves (OZK) on air ducts in the fire zone and adjacent areas - prevents the spread of smoke and fire through the ventilation ducts;
• opening smoke exhaust valves (SDU) in the fire zone - starting the removal of smoke-laden air;
• launching smoke removal fans to create a standardized air flow from the smoke zone;
• launching air boost fans into smoke-free staircases, elevator shafts and airlocks to create excess pressure to prevent smoke from penetrating the evacuation route.

Fire fighting (AFS):

• generation of a command to launch a fire extinguishing installation in the protected volume after confirmation of a fire with the necessary delay for the evacuation of people;
• blocking the simultaneous operation of gas, powder or aerosol fire extinguishing with smoke ventilation in the same room is a mandatory requirement Federal Law No. 123-FZ;
• control of water and foam fire extinguishing pump units.

Access control systems and escape routes:

• unlocking electromagnetic and electromechanical locks on emergency exits and doors on escape routes when there is a “Fire” signal;
• control of fire doors with closers and retaining devices.

Elevators:

• transfer of all elevators to the “Fire Danger” mode with the return of the cabins to the main landing floor and subsequent blocking of the doors in the open position;
• control of elevators used for the evacuation of people with limited mobility (people with reduced mobility) at facilities with relevant requirements.

Emergency lighting:

• automatic switching on of evacuation and emergency lighting upon a “Fire” signal in evacuation zones.

How does the “cause-effect” logic work and why can’t you pass the examination without it?

“Cause-effect” logic is a formalized matrix in which for each input signal (signal type, zone FAS control zone, confirmed fire algorithm) an exact list of output control commands with sequence and delays is defined. Without this matrix, the FPSA project is incomplete: the expert cannot check the correctness of the algorithms and the presence of the required interlocks, the installer does not know what exactly should work, and the commissioning engineer cannot conduct acceptance tests using an unambiguous checklist.

Typical errors identified during the examination in the absence of a cause-and-effect matrix: conflict of systems (smoke ventilation and gas extinguishing are started simultaneously), incorrect control zones (the ventilation of the adjacent room, not the burning one, is turned off), lack of a delay before starting the automatic control system (people do not have time to leave the room), incorrect conditions for unlocking the access control system. AYU-Project develops a cause-and-effect matrix as a mandatory part of the DD, which eliminates all of the listed errors even at the documentation approval stage.

FPSA zoning and fault tolerance requirement: what does SP 484 require from 2025?

Zoning FPSA is a division of an object into fire protection zones (fire protection zone), in each of which the FPSA algorithms work independently. Change No. 1 to SP 484.1311500.2020 (effective from 01.09.2025) established a key requirement for fault tolerance: a single failure of any element of the communication line or control equipment FPSA should not impair the functionality of more than one fire protection zone. In practice, this means: the designer is obliged to build the architecture of control and redundancy lines so that one cable break does not “drop” the entire system.

For the developer, the requirement for fault tolerance is critical from a commercial point of view: it determines the architecture of cable networks and the cost of installation. An incorrect topology (for example, all actuators in a building are connected to one controller without redundancy) may require a complete redesign during the review phase. AYU-Project lays out the required architecture from the first release of DD, saving the construction customer from costly iterations.

Integration of ASPS with SPS, SOUE, AUP and BMS: how does it work in a single complex?

Integration is not just connecting systems with a cable: it is a consistent logic of signaling, priorities and interlocks. FAS generates a “Fire” signal in a specific FAS control zone according to a confirmed algorithm (A, B or C) and transmits it to FPSA. FPSA, in accordance with the control matrix, generates commands for smoke ventilation, AFS, ACS, elevators and simultaneously transmits a control signal to EVAC to trigger an alert in the required zones according to the required scenario. All this happens automatically, at standardized time intervals, without the participation of personnel.

For facilities equipped with a dispatch system (BMS), the fire control system is integrated with it at the level “information from fire control system → BMS” with absolute priority of fire algorithms: the BMS displays status and events, but cannot block or change fire commands. This architecture allows the operation service to monitor the status of all fire protection zones from a single workplace, without creating the threat of violating standardized algorithms.

Composition of design documentation and working documentation to FPSA: what we convey to the customer

Documentation is developed in accordance with Government Decree of the Russian Federation No. 87 dated 16.02.2008 No. 87 (as amended on 21.10.2025) “On the composition of sections of project documentation and requirements for their content”, SP 484.1311500.2020 (with Change No. 1 from 01.09.2025), SP 7.13130.2013, SP 485.1311500.2020, SP 486.1311500.2020 And Federal Law No. 123-FZ.

Design documentation stage includes:

• an explanatory note describing the decisions made on automation and the rationale for control algorithms;
• zoning of the object with a description of the composition and boundaries fire protection zone;
• a matrix of cause-and-effect relationships (Cause & Effect) for each PPP;
• block diagram of FPSA with designation of interaction with FAS, EVAC, AFS, smoke ventilation, ACS and elevators;
• calculation of autonomous power supply of control and executive equipment;
• list of controlled and managed points (I/O list).

Working Documentation Stage (WD) contains:

• block diagram of FPSA with a complete set of equipment and interfaces;
• schematic electrical diagrams for controlling each type of actuator (valves OZK, fans smoke ventilation, valves AFS, door drives, elevator controllers, ACS);
• connection diagram of ASPS controllers with designation of addresses and types of inputs/outputs (I/O);
• plans for the placement of ASPS control cabinets and actuators with reference to building axes;
• cable log and control line routing diagrams;
• ASPZ power supply diagram with parameters of backup power supplies and calculation of battery capacity;
• checklist of acceptance tests according to the Cause & Effect matrix (for each fire protection zone - a set of tested scenarios);
• specifications of equipment and materials;
• statement of quantities.

Regulatory design basis FPSA

• SP 484.1311500.2020 with Amendment No. 1 (valid from 01.09.2025) - the basic set of rules for the design of ASPS: zoning, control algorithms, requirements for fault tolerance;
• Federal Law No. 123-FZ “Technical regulations on fire safety requirements” - regarding the composition of fire protection systems and requirements for control algorithms smoke ventilation, AFS, ventilation;
• SP 7.13130.2013 - standards for smoke ventilation: control of valves, fans, standardized parameters of smoke removal and pressurization;
• SP 485.1311500.2020 (with Amendment No. 1, 2, 3, 2025) - regarding algorithms for controlling fire extinguishing and interlocking installations;
• SP 486.1311500.2020 - list of facilities to be equipped with fire protection systems;
• SP 3.13130.2024 - regarding the interaction between FPSA and EVAC;
• SP 1.13130.2020 - regarding the management of evacuation routes and exits through FPSA;
• GOST R 21.1101-2020 - requirements for working documentation (WD) formatting;
• Government Decree of the Russian Federation No. 87 dated 16.02.2008 No. 87 (as amended on 21.10.2025) “On the composition of sections of project documentation and requirements for their content.”

Pricing and how to order

The cost of developing design documentation and working documentation on FPSA is determined by the number of fire protection zone, the composition of managed systems, the number of controlled and managed points (I/O) and the complexity of the scenario matrix. With the simultaneous design of FPSA, FAS, EVAC and AFS under a single contract, the cost is lower than with a separate order - due to the combined development of control matrices and cable routes.

To receive a commercial proposal, leave a request: indicate the type and purpose of the object, its area, number of floors, the composition of engineering systems (ventilation, smoke ventilation, AFS, ACS, elevators) and the presence of requirements for BMS integration. The initial consultation is free, and we work across Russia remotely.