Panorama Suite for Africa: an OT/IT Data Management Platform for Unified Control Centres

Executive summary

Panorama Suite is CODRA's OT/IT Data Management Platform for operational applications and Unified Control Centres. From a common data and engineering foundation, it can support SCADA, GeoSCADA, BMS, EMS, Historian, PSIM and MES applications, as well as multi-site operations. The objective is not to replace every field or control system. It is to create a consistent operational layer across equipment, sites and teams.

CODRA reports that it has developed industrial software since 1986 and reinvests more than 25% of annual turnover in R&D. The company identifies interoperability, cybersecurity and sovereignty as long-term product commitments. These facts are documented on CODRA's official company page.

A vendor-independent platform built to avoid vendor lock-in

Vendor lock-in usually appears gradually: proprietary protocols, project files held by one contractor, licence models tied to hardware, or upgrades that force an equipment decision. A vendor-independent OT/IT data layer gives the asset owner another option. It can standardise data, operator interfaces, alarms, history and reporting while allowing different controllers and subsystems to remain where they are technically and commercially justified.

Independence does not mean that every device connects automatically. A sound project still verifies protocol versions, available drivers, gateway requirements, timestamp behaviour, alarm semantics, redundancy and engineering ownership. The practical benefit is freedom of architecture, not a promise of zero integration effort.

One data platform, multiple operational applications

Panorama Suite is designed to work across industrial, infrastructure, building and security environments. CODRA lists broad protocol support and maintains third-party interoperability credentials, including OPC UA and BACnet BTL, on its certifications and commitments page.

For an African operator, this can support several operational applications:

• a SCADA or GeoSCADA application for water, energy, transport or distributed infrastructure;
• a BMS or EMS application that expands into performance management and unified alarms;
• a Historian or MES application connecting production, quality, maintenance and enterprise workflows;
• a PSIM-based control centre combining operational and physical-security context;
• a vendor-independent Unified Control Centre that brings several of these applications together.

Application guides

• BMS and EMS in Africa
• Industrial Historian in Africa
• PSIM and Unified Control Centres in Africa
• MES in Africa with Panorama COOX
• Unified Operations Centres, hypervision and Manager of Managers in Africa
• Airport Unified Control Centres and APOC in Africa
• Hospital and healthcare Unified Control Centres in Africa
• Agri-food and agricultural value-chain Unified Control Centres in Africa

The design principle is clear: connect systems around an operational model and accountable interfaces. Keep network boundaries controlled even when broader data access is useful.

For the architecture and governance implications, see IT/OT convergence in Africa: connect the business without weakening operations.

Edge-to-Service for geographically distributed operations

Many African operations combine remote assets, uneven communications and limited maintenance windows. CODRA's Edge-to-Service pattern keeps local operational applications autonomous while providing central hypervision, administration, data transfer and controlled command paths. Its published architecture also describes store-and-forward behaviour, an Edge Gateway in a DMZ and central deployment of applications, versions and patches.

This is useful when a group wants one operating model without making every site dependent on a permanent WAN connection. The project must still define what remains local, what may be centralised, how long a site must tolerate disconnection and how commands are authorised after communications recover.

Source: CODRA, Panorama Edge-to-Service.

Cybersecurity-first, backed by ANSSI qualification

Panorama E2 was the first product in ANSSI's SCADA category to obtain CSPN certification and later received ANSSI qualification. CODRA reports continued certification, including a 2026 update. These credentials provide a strong product-security foundation, while overall system security still depends on the deployed architecture and operating practices.

Secure deployment depends on segmentation, identity and access management, hardening, secure remote support, backup and recovery, logging, vulnerability management and lifecycle governance. CODRA describes Panorama Suite as supporting NIS2-aligned programmes and progressing towards IEC 62443 certification.

Sources: CODRA's cybersecurity page and commitments page.

Automatic Fault Detection as an integrated AI capability

CODRA announced AFD in August 2026 as an integrated AI component for Panorama MES, SCADA and Historian environments. It learns historical normal patterns, considers different operating phases and monitors current behaviour for deviations. Alerts are intended to help teams investigate abnormal conditions earlier.

Potential applications include energy and building performance, air systems, critical assets and process quality. AFD provides decision support for earlier diagnosis and predictive-maintenance workflows. Its results depend on instrumentation, data quality, operating context and the organisation's ability to act on alerts.

Source: CODRA, AFD: detect the abnormal before it becomes an incident.

One platform, four regional delivery contexts

How to evaluate the fit

1. Start from operations: identify the processes that must continue locally during network or service loss.
2. Map the installed base: protocols, controller families, historian sources, BMS, meters and third-party applications.
3. Define ownership: who owns graphics, configuration, source files, cyber controls and documentation after handover.
4. Validate cybersecurity: zones, conduits, identities, remote access, logging, backup, patching and incident response.
5. Run a focused pilot: prove interoperability, operator usability, data quality and support processes before scaling.
6. Assess lifecycle value: compare flexibility, upgrade paths, training and dependency risk, not only initial licence cost.

Frequently asked questions