For years, we have grown comfortable with a convenient division. Fire protection deals with saving lives and evacuation. Physical security handles asset protection, zone separation and resilience against misuse. Each discipline has its own regulations, its own standards, its own specialists and its own language.
Fire protection and physical security — two worlds that need to meet.
The problem is that a building is not divided into disciplinary silos. There is one set of doors. One set of corridors. One set of passages. One set of procedures. And a real incident does not ask whether it has just entered the “fire” zone or the “security” zone. It simply exploits whatever turns out to be the weakest, the least coordinated, or designed solely from the perspective of a single speciality. This is exactly where a problem begins that can no longer be solved by thinking in terms of separate disciplines.
The interface is not theoretical
The easiest place to see this is at the point shared by both worlds: doors, passages and their operational logic. What fire automation treats as an element of evacuation assurance, physical security often regards as a critical tool for zone separation, access restriction and asset protection. We are talking about the same piece of infrastructure, but read through two entirely different lenses.
In a typical office building, such a conflict may be merely organisational. It ends with a discussion, a scenario adjustment, perhaps a change in a few assumptions. In sensitive facilities, the situation is different. There, poorly designed door or passage logic does not just mean user inconvenience. It can mean a genuine security vulnerability. And this is where the comfortable story of two separate worlds comes to an end.
Evacuation is not always just evacuation
In the fire industry, we naturally assume that an alarm means danger and that the building should support the fastest and safest possible exit from the zone. That is the right instinct. But physical security practice has long taught caution about oversimplification.
False triggers, provocations, actions testing the security response, or attempts to exploit procedures are not exotic phenomena. In many types of facilities, they must be treated as part of the normal risk landscape rather than an unlikely exception.
That is why it is worth asking: does the logic of my design, in alarm mode, inadvertently create the easiest path to zones that should remain protected under normal conditions?
This is not a question against evacuation. It is a question about the quality of design thinking. If an alarm triggers the mass unlocking of passages, changes the relationships between zones and removes safeguards from circulation routes — while no well-considered zoning logic, oversight or security procedures accompany it — then the building may start operating correctly in one sense, yet dangerously in another. It is precisely at moments like these that silos begin to produce risk.
Compliance is the foundation. But it is not always enough
There is no doubt that in the world of fire automation, compliance with regulations and technical requirements remains the foundation. The problem starts when compliance becomes the only horizon of thinking.
Modern facilities are more complex than they were even a dozen years ago. We have more integrations, more dependencies between systems, greater operational pressure and more scenarios in which someone might try to exploit building behaviour. This means that the question “have we met the requirements?” is no longer sufficient on its own. Increasingly, we also need to ask: what happens if the alarm turns out to be false? Are there scenarios for misuse? Could a fire alarm unnecessarily open access to critical areas? How will security staff respond when passage states change? Are the control logic and security procedures truly aligned? These are not questions about a single system — they are questions about security as a process.
Holism does not mean shifting responsibility
The point is not for a fire automation designer to replace a physical security specialist. Just as a security specialist cannot replace a fire protection designer. The point is something simpler and at the same time harder: acknowledging that there is a shared area of responsibility that must not be left until the end of a project.
Doors on evacuation routes, passages between zones, control integrations, response scenarios, system behaviour after an alarm is triggered, the impact of automation on security procedures — these are not topics that should be developed separately and then “stitched together” during commissioning or under deadline pressure. Because what typically emerges then is not a well-considered solution. It is a forced compromise.
One facility demands unified thinking
In practice, the best solutions do not come from one discipline dominating another. They come from conversations held early enough. That is when there is still time to distribute functions, build conditional logic, anticipate exceptions, describe procedures and avoid situations where one decision automatically weakens another area of security.
This is the direction worth strengthening today: less installation-focused thinking, more scenario-based thinking. Not just “how should the system work?” but also “what will that operation do to the facility as a whole?” This is especially important where the stakes go beyond user comfort — where continuity of operations, information protection, safeguarding valuable assets and resilience against deliberate misuse are all on the line.
This is not a trend. It is a necessity
Two silos were convenient. They simplified responsibilities, organised the market and allowed specialists to operate within well-known boundaries. But convenience does not always mean effectiveness.
There is one facility. One user. One incident — even when it affects multiple systems at once. In the coming years, the question will less and less be about who is right from a disciplinary standpoint, and more and more about whether the facility as a whole will behave properly when reality refuses to respect our disciplinary boundaries.
And that is precisely why fire protection must talk to physical security. Not because someone wants to expand their competences by force. But because today, there is no other way to design security responsibly.
Because if security systems are truly meant to protect a facility, they cannot be a collection of parallel islands. They must form a single, coherent operational logic — because the facility is one.