On a single site, aggregating CCTV, access control, intrusion and fire detection is something most integrators handle well. The jump in complexity comes with multiple sites: dozens of buildings, subsystems that differ by generation and by brand, variable network constraints, 24/7 service continuity requirements. At that scale, stacking business applications is no longer enough. You need a PSIM platform.
This guide sets out the reference architecture of a multi-site PSIM platform (Physical Security Information Management), its technical layers and the structural trade-offs to settle on at the design phase.
Key takeaways
- Safety-Security PSIM aggregates multiple security subsystems into a single unified control center. Multiple security subsystems into a single Unified Control Center.
- A multi-site PSIM architecture rests on four layers: field collection, integration, Unified Control Center, and presentation.
- Multi-vendor interoperability and degraded-mode handling are the two robustness criteria.
- Multi-site deployment requires a distributed architecture with a centralized Unified Control Center and local autonomy.
What a Safety-Security PSIM platform covers
Safety-security SCADA is the function that aggregates, correlates and presents, in a single interface, every event from the security subsystems of a site or an estate. It lets one operator run what used to be split across five or six business applications.
PSIM (Physical Security Information Management) is the software category implementing this function. A PSIM platform does not replace the subsystems (CCTV, access control, intrusion detection, BMS (Building Management System), voice alarm, intercom); it federates them from above, through native connectors or standard protocols.
The distinction matters: a PSIM platform is not a VMS (Video Management System) or an extended access-control application. It is a transverse oversight layer, independent of underlying brands and generations, adding value through event correlation and standardized procedures.
The four layers of a multi-site PSIM architecture
Layer 1: Field collection (per site)
On each site, the existing subsystems (CCTV, access control, intrusion, fire, BMS, intercom) keep running on their own applications. Collection is handled by connectors: native manufacturer protocols, ONVIF for video, OSDP for access control, BACnet or OPC UA for the BMS. This layer must handle multi-vendor diversity without replacing the installed base.
Layer 2: Local integration and site autonomy
A local integration server per site (or cluster of nearby sites) consolidates flows, normalizes event formats, and stays autonomous if the link to the central control room drops. It keeps the site operational even when that link is cut. Events and video are queued and synchronized once the link is restored.
Layer 3: Unified Control Center
The core of the PSIM platform sits here. This layer receives the normalized events from every site, applies correlation rules (intrusion alarm + video loss + forced door = priority scenario), triggers operating procedures (instructions, video alarm verification, escalation to managers, emergency call), and logs every operator action for later audit. This is also where multi-site mapping is managed, with drill-down from an estate to a building to a zone.
Layer 4: Presentation and operation
This layer exposes functions by user profile: a 24/7 operator in the control room, a security manager with a consolidated multi-site view, field teams on mobile, and management with KPI dashboards. A presentation adapts to a profile and context without duplicating data.
The structural trade-offs to settle at design time
Three trade-offs determine the long-term robustness of a multi-site PSIM platform.
The first is multi-vendor interoperability. A PSIM platform worthy of the name must integrate equipment from several generations and manufacturers with no vendor lock-in. The most reliable criterion is the number of native connectors and the ability to build specific ones for legacy equipment. A single-vendor PSIM is not a PSIM; it is an extended manufacturer application.
The second is degraded-mode handling. What happens if the Unified Control Center is unreachable? If a site loses its network? If an integration server fails? The architecture must explicitly plan for failovers, queues, local autonomy, and recovery procedures. A PSIM that only works in nominal conditions is not usable for security.
The third is the cybersecurity of the platform itself. A Safety-Security PSIM platform centralizes sensitive data (site plans, video streams, access rights, alarms) and becomes a prime target. Compliance with the requirements of ANSSI (the French National Cybersecurity Agency) and, for the operators concerned, with the NIS2 directive, is now a prerequisite. CSPN certification of the underlying platform is a strong signal for public buyers and critical sites, alongside international frameworks such as IEC 62443.
A multi-site PSIM platform is never the sum of stacked business applications. It is a four-layer architecture designed to federate the installed base, guarantee local autonomy, centralize correlation, and present information to the right user profile. The quality of a safety-security project is decided in the architecture trade-offs made upstream, not in the choice of a vendor.
To build your project on proven multi-site foundations, explore the Panorama Suite from CODRA and talk to our experts to frame your target architecture.
