Executive summary
A Physical Security Information Management (PSIM) platform federates specialist systems and adds cross-system context, workflows and auditability. It does not replace the VMS, access-control system, fire panel, intrusion system, intercom or BMS simply to reproduce their specialist functions.
A PSIM becomes a Unified Control Centre when the operating model extends beyond security: facilities, utilities, transport, industrial or other operational domains can then share a broader data and workflow foundation while retaining clear responsibilities.
CODRA describes a multi-site PSIM across field collection, local integration, the Unified Control Center and role-based presentation. See PSIM Platform Architecture for Multi-Site Security.
What a PSIM platform should federate
- CCTV and video management events, including camera status and verification workflows;
- access control, forced doors, invalid credentials and occupancy context;
- intrusion, perimeter and duress systems;
- fire detection, voice alarm and emergency communications where the approved interfaces permit;
- intercom, public address, BMS and selected technical alarms;
- maps, geospatial context, procedures, escalation and an operator audit trail.
The value lies in correlation and coordinated response. A door alarm, loss of video and adjacent technical event may deserve a different priority together than each alarm receives in isolation.
A four-layer multi-site architecture
- Field systems: retain the specialist equipment and applications that own local safety or security functions.
- Local integration: normalise events, preserve essential autonomy and buffer information during network loss.
- Unified Control Centre: correlate events, apply procedures, coordinate escalation and maintain an audit trail.
- Presentation: provide views appropriate to control-room operators, security managers, field teams and leadership.
The interfaces between these layers must be explicit. A diagram labelled “centralised” is not enough: the design must state what continues locally, how recovery works and which system remains authoritative for each command.
Vendor independence protects the control-room lifecycle
Security estates evolve in stages. Cameras, access systems and fire panels are replaced at different times, and acquired sites may use entirely different brands. A vendor-independent PSIM layer lets the operator standardise the control-room experience without forcing one hardware family across the estate.
Independence is not automatic compatibility. The project still validates native connectors, ONVIF or other standards, event semantics, supported versions, command authority, latency and failure behaviour. The benefit is architectural choice and a managed migration path.
Resilience and cybersecurity must be designed together
A PSIM centralises sensitive information and becomes operationally important. Segmentation, identity, least privilege, secure remote access, logging, backup, recovery, patch governance and incident procedures therefore apply to the platform as well as to the connected subsystems.
Local autonomy and buffering are essential for distributed estates. CODRA’s Panorama Edge-to-Service pattern addresses disconnected operation, while its Cybersecurity and SCADA page documents the Panorama security approach and ANSSI credentials.
Where the approach is particularly relevant
Critical sites
Airports, rail, ports and utilities
Coordinate security and facility events across large or distributed estates where service continuity and clear escalation matter.
Commercial estates
Data centres, banks and corporate campuses
Unify mixed-generation systems, central teams and local responders while keeping site-specific responsibilities visible.
How to evaluate a PSIM or Unified Control Centre
- Start with scenarios: define events that require cross-system correlation and coordinated action.
- Map authority: identify which subsystem owns detection, command, acknowledgement and evidence.
- Test degraded modes: WAN loss, subsystem loss, central-server loss, delayed video and recovery.
- Validate interoperability: versions, connectors, event detail, command scope and upgrade responsibility.
- Measure operator outcomes: prioritisation, verification time, procedural consistency, reporting and auditability.
Delivery across Africa’s four regions
CODRA’s Africa business and technical office in Johannesburg is the direct route for African projects and coordinates suitable certified integrators according to the country. Felton Energy Services represents CODRA in Nigeria only; ZEK Group International represents CODRA in Tanzania only.
See the dedicated pages for Vendor-independent Unified Control Centres for West Africa, Vendor-independent Unified Control Centres for Central Africa, Vendor-independent Unified Control Centres for East Africa and Vendor-independent Unified Control Centres for Southern Africa.
Frequently asked questions
What is the difference between PSIM and a Unified Control Centre?
PSIM focuses on federating physical-security and related safety systems. A Unified Control Centre can include PSIM while extending the shared operational environment to facilities, utilities, transport, industrial or other domains.
Does a PSIM replace the VMS or access-control system?
Normally no. The VMS, access-control and other specialist systems retain their dedicated functions. The PSIM federates events, context, procedures and operator workflows above them.
Can a PSIM be vendor-independent?
Yes, if the architecture supports the required mix of native connectors and standards and the project validates versions, semantics and failure behaviour. Vendor independence does not remove integration work.
What happens if a site loses its link to the central control room?
A resilient design preserves defined local functions, buffers appropriate events and synchronises safely after recovery. The exact degraded mode must be designed and tested for each site.
What should a PSIM pilot include?
A useful pilot includes multiple subsystem brands, at least one correlation scenario, a guided response workflow, a communications-loss test, cybersecurity controls and an auditable operator outcome.
Next step
Evaluate the application against your real installed base
I work with operators and local integrators to define the initial scope, interfaces, cybersecurity requirements and delivery model.