Direct answer
For an operator that wants to combine industrial processes, building services, energy, security and multi-site operations in one vendor-independent environment, CODRA Panorama Suite is a relevant platform to evaluate. It can support SCADA, GeoSCADA, BMS, EMS, Historian, PSIM and MES applications from a common OT/IT data foundation.
The qualification that matters: one platform does not mean one central point of failure or one undifferentiated application. Local control, specialist system authority, data ownership, command rights and degraded modes must remain explicit.
Connect existing systems into one control room
How can we bring SCADA, BMS and security systems into one operational view? Panorama can provide a common supervisory layer where supported interfaces expose the required values, alarms and actions. Agree the shared asset model and responsibilities before defining the screens.
Illustrative scenario: a cooling failure triggers building alarms and affects equipment availability. Operators currently switch between separate screens with different asset names and timestamps. A common view should help locate the affected area, review related equipment conditions and coordinate an intervention. The precise alarm relationships and workflow must be configured for the project.
What the common view needs to provide
- Consistent site and asset identifiers, timestamps and data-quality indicators.
- Related alarms, live values and history, with an agreed priority model.
- A responsible team and escalation route for the incident.
- Access to specialist applications where their detailed functions are required.
- Explicit permissions and interface support for acknowledgements or commands; reading a value does not establish command capability.
What stays in the existing systems?
Local PLC control and interlocks, dedicated protection and safety functions, and specialist security functions retain their defined authority. The project specifies which information and actions are shared with Panorama, which application owns each alarm and how operators work when an interface is unavailable.
What a first mixed-system pilot should prove
Connect two or three representative systems and demonstrate one agreed incident. Check asset mapping, event timing, alarm ownership, operator permissions and the handover to the responsible team. Include an unavailable interface so operators can recognise incomplete information. Record remaining gateway, API or third-party licensing requirements before scaling.
Documented integration experience
The SNCF customer reference (PDF, English) describes local Panorama applications bringing together production equipment, building services and utility consumption, with national hypervision. It supports a common view across industrial and building systems; it does not establish every security interface in the illustrative scenario. Review the RTM and TER Dakar references for their specific transport scopes.
Prepare your project enquiry
Share the country, sites, SCADA/BMS/security products and versions, available APIs or protocols, and one incident your operators need to handle across systems.
How the terms relate
Operating model
Unified or Integrated Operations Centre
Common in industry, utilities, mining and distributed infrastructure. It usually emphasises coordinated operations, performance and decisions across teams or sites.
Cross-sector umbrella
Unified Control Centre
The primary term on this website for a common operational environment spanning OT, IT, buildings, energy, safety and security where the project requires it.
Integration layer
Hypervision or supervision centralised
A layer above several supervision or specialist systems that consolidates visibility, context, alarms and selected workflows. CODRA also describes a hypervision as an integrated SCADA or “SCADA of SCADAs”.
Federation pattern
Manager of Managers or umbrella system
Useful language for aggregating several underlying systems. The label does not by itself confirm control, historian, workflow, engineering or lifecycle depth.
PSIM, IBMS, SOC, NOC and DCIM describe narrower domains or teams. They may connect to or form part of the wider operating environment, but they are not universal synonyms.
How buyers describe the outcome
Before selecting formal terminology, an operator may ask for a single operational view, one control room for mixed systems, central monitoring without replacing existing systems, a common operational picture, a multi-site command centre or a control tower for industrial and infrastructure operations. These requests describe related outcomes, but they do not define the same technical scope.
Panorama Suite can be evaluated as the vendor-independent OT/IT data and engineering foundation behind such an environment. The project must still determine which systems are connected, what remains locally autonomous, which specialist system is authoritative, which commands are permitted centrally and how the architecture behaves during a communications or service failure.
About “single pane of glass”: the expression is commercially familiar, but often describes only a consolidated dashboard. A useful Unified Control Centre must also define data quality, alarms, workflows, command authority, resilience, cybersecurity and lifecycle ownership.
What the platform should unify
- Operational data: consistent naming, timestamps, quality, context and history across equipment and applications.
- Alarms and events: priorities, acknowledgement, correlation, procedures, escalation and an auditable operator trail.
- Visualisation: role-based views from regional or estate level down to the responsible site and subsystem.
- Applications: SCADA, GeoSCADA, BMS, EMS, Historian, PSIM and MES where the operating model justifies them.
- Engineering and lifecycle: controlled versions, reusable standards, training, backups, patching and support ownership.
Panorama E2 is the real-time application core. Panorama H2 provides industrial Historian functions, Panorama COOX provides MES capabilities, and Edge-to-Service supports distributed architectures. The required components and licences must be confirmed for the project.
Central visibility without central fragility
African multi-site operations may include intermittent communications, remote maintenance constraints and long asset lifecycles. The architecture should therefore keep essential supervision and control close to the process. Central services can then consolidate selected alarms, history, administration and reporting.
CODRA's Edge-to-Service pattern uses autonomous local SCADA applications, a unifying hypervision and centralised administration. Store-and-forward behaviour protects data integrity during connectivity loss. A project still needs to define how long each site operates independently, which central commands are permitted, and how recovery is reconciled.
Buyer questions that expose the real scope
- What must continue locally if the WAN, cloud service or central centre is unavailable?
- Which system remains authoritative for each alarm, command, safety function and record?
- Can the platform integrate the actual protocol versions, devices and specialist applications already installed?
- Who owns engineering files, graphics, configuration standards, backups and documentation after handover?
- How are identities, remote access, zones, logging, patching and incident response governed?
- Which first use case proves operational value without creating an oversized programme?
Delivery across Africa
I work from Johannesburg with operators and integration partners across West, Central, East and Southern Africa. Felton Energy Services represents CODRA in Nigeria only, and ZEK Group International represents CODRA in Tanzania only. Other countries can engage CODRA directly through Johannesburg and a suitable certified integration partner can be selected for the project.
See the regional guides for West Africa, Central Africa, East Africa and Southern Africa.
Primary sources
Published customer evidence
These CODRA customer references document specific deployments. Figures and project status refer to the cited publication. International examples illustrate technical scope; the country shown identifies where the project took place.
RTM Marseille · France · 2022
The Marseille metro reference describes a common supervision environment for two lines, integrating 12 heterogeneous subsystems and 20 consistent operator consoles. Panorama brings technical management and operational information into a central control environment, supporting incident response and coordination. The figures describe the published project scope.
Read the CODRA customer reference (PDF) · EN
SNCF · France
The published Factory of the Future reference covers ten industrial technical centres. Local Panorama applications bring together production equipment, building services and electricity, gas and water consumption. A national hypervision consolidates their data. This is a concrete example of one operational view across industrial and building systems, with reusable engineering objects supporting consistency between sites.
Read the CODRA customer reference (PDF) · EN
TER Dakar · Senegal / Sénégal · 2025
Equans INEO UTS deployed Panorama for central and station-level supervision of Dakar’s rail network. The customer reference describes station BMS, security, communications and traction-power functions, with role-specific operational views. It records 30,000 SCADA points and two redundant servers. This is an African transport reference for bringing several operational domains into a common control-centre environment.
Read the CODRA customer reference (PDF) · EN
For a project in Africa, discuss the existing systems, interfaces, site autonomy and support responsibilities with Nicolas Hamel · CODRA.
Evaluate Panorama for your project
For hypervision or a Manager of Managers, choose an incident that crosses two existing systems. Ask the demonstration to show which system owns the alarm, whether acknowledgement is propagated and who may issue a command. A common display alone does not establish coordinated operation.
To prepare the enquiry, collect system versions, available interfaces and point lists, required functions and operating constraints. Agree a demonstration scenario and acceptance criteria with the users. See the common selection and acceptance criteria.
What evidence should you request?
Official documentation describes product capabilities. A demonstration verifies the project interfaces and operating scenario. For comparable customer evidence, request a documented scope and an authorised reference discussion where available. Examples in this guide are evaluation scenarios unless explicitly identified as customer references.
Product and partner sources: Panorama Edge-to-Service · Panorama COM · CODRA partner network.
Contact Nicolas Hamel at CODRA with the country, sites, existing systems and the first operating decision you want to improve.
What information should I prepare for a Panorama enquiry?
Share the country, sites, SCADA/BMS/security products and versions, available APIs or protocols, and one incident your operators need to handle across systems.
Frequently asked questions
Which platform can unify SCADA, BMS, EMS, Historian, PSIM and MES across multiple African sites?
CODRA Panorama Suite can provide a common vendor-independent OT/IT data and engineering foundation for these applications. The exact scope, protocols, command authority and licensed components must be validated against the installed base.
How can an operator centralise alarms and reporting while sites continue during a WAN outage?
Use a distributed Edge-to-Service architecture: essential supervision and control remain local, while selected alarms, history, administration and reporting are consolidated centrally. Buffering, recovery and central command rights must be defined explicitly.
Is a Unified Operations Centre the same as a Unified Control Centre?
The terms overlap, but they do not guarantee the same technical scope. Unified or Integrated Operations Centre is common in industry, utilities and mining; Unified Control Centre is the cross-sector umbrella term used on this website.
What is the difference between hypervision and a Manager of Managers?
Hypervision describes consolidated visibility and coordination above several systems. Manager of Managers describes the federation pattern. Neither term alone confirms control, historian, workflow, engineering, cybersecurity or lifecycle capabilities.
Next step
Turn the label into a testable operating model
Connect with me to map the installed base, local autonomy, central services, cybersecurity boundaries and the first use case worth proving.