Nicolas Hamel

Building a Unified Control Centre in South Africa with CODRA Panorama Suite

This South Africa guide covers Unified Control Centre architecture and the SCADA applications within it: Edge-to-Service, redundancy, EMS and Historian functions, OT cybersecurity, delivery partners and buyer criteria for energy, water, transport, buildings and data centres. For the broader product view, see Panorama Suite for Africa: an OT/IT Data Management Platform for Unified Control Centres. For the Johannesburg office and regional partner route, read Vendor-independent Unified Control Centres for Southern Africa.

Unified Control Centre buyer’s checklist

Architecture

  • Define control boundaries: what must keep running without WAN?
  • Redundancy where it matters: servers, communications and power.
  • Historian and EMS sizing: tag counts, retention and reporting cadence.
  • Protocols and gateways: Modbus, S7comm, BACnet/IP or SC, SNMP, MQTT, IEC 61850 and others.

Security

  • Zone and conduit design, allow‑list communications and MFA for remote access.
  • Harden PLC/HMI/servers; patching strategy without disrupting ops.
  • Monitoring and logging: Historian and SIEM/SOC integration.

People and process

  • Operator training and SOPs; change management and backups.
  • Measurement and verification for energy and water savings, when included in the EMS scope.
  • Support SLAs: hours, response, spares, escalation.

Video: Building a SCADA application with CODRA Panorama Suite

Prefer reading? See the Unified Control Centre buyer’s checklist and Frequently asked questions below. Also watch Sommet Africa Forward à Nairobi for additional profile and market context. Read the BPI France interview for business context in South Africa.

Key takeaways
  • Keep control local; use Edge‑to‑Service for reporting/analytics.
  • Design redundancy where it matters (servers, comms, power).
  • Right‑size historian/EMS and densify metering for decisions and M&V.
  • Segment OT/IT, enforce MFA for remote access, and allow‑list communications.

Why the platform approach matters in Africa

1) One OT/IT data platform supports multiple operational priorities

Panorama Suite can support SCADA, GeoSCADA, BMS, EMS, Historian, PSIM and MES applications, as well as Unified Control Centres, Edge-to-Service and BIM for operations. In Africa, this matters because projects often expand from one application to another as priorities evolve.

2) Vendor independence protects long-term choice

Many owners want to avoid OEM lock-in and single-integrator dependency. A vendor-independent OT/IT Data Management Platform helps unify mixed assets and applications, preserve long-term choice, and protect investment decisions.

3) Edge-to-Service matches local realities

African operations are often distributed and phased. Edge-to-Service supports resilient hybrid architectures where control stays local and supervision/reporting scales centrally.

4) Unified Control Centres create operational value

Customers are reducing silos: fewer screens, fewer vendors, and one operational view across BMS, security, energy and industrial operations.

5) Local partnerships strengthen delivery and support

Local integration partners strengthen regional engineering, first-line support, knowledge transfer and escalation throughout the project lifecycle.

Market landscape and common use cases

South African SCADA deployments span municipal water and sanitation, energy (generation, distribution, metering and EMS), transport (rail and BMS at stations), and buildings and data centres (HVAC, BMS, power and alarms). Typical goals include operational visibility, alarm management, compliance reporting, energy and water efficiency, and resilient operations during network outages.

Reference architectures

Central control with local autonomy

Local PLC/RTU/HMI keep assets running; a central SCADA provides a unified view, alarms, historian/EMS, and engineering tools. Use redundant servers and communications for critical processes.

Edge‑to‑Service

Securely bridge local sites to value‑added services (dashboards, reporting, analytics, mobile) without putting control in the cloud. Selectively publish data upstream; keep control local.

Protocols and interoperability

Plan for Modbus, S7comm, BACnet/IP or SC, SNMP, MQTT, and IEC 61850. Use tested gateways where needed and document addressing, scaling, and time‑sync.

Historian and EMS

Right‑size tag counts, archiving windows, and report schedules. For EMS, densify metering where decisions are made and retain enough history for M&V.

OT cybersecurity basics

For regulated and high-consequence contexts, see Cybersecurity for nuclear Unified Control Centres and OT/IT Data Management Platforms in Africa for a cybersecurity-first framework aligned to IEC 62443 and ANSSI guidance.

  • Segment networks; define trust boundaries between IT and OT.
  • Harden assets (PLC/HMI/servers), enforce MFA for remote access, and use allow‑listed communications between zones.
  • Collect logs and telemetry; monitor for anomalies; back up configurations and test restores.
  • Adopt a clear change‑management process with approvals and rollback plans.

Integrators and delivery

Choose partners with relevant references, formal quality assurance, certified training and 24/7 support. Ensure transparent documentation handover and that cybersecurity practices are embedded from design through maintenance. For energy and water, include measurement and verification (M&V) in scope to quantify savings.

Frequently asked questions

What does SCADA cost?

Total cost depends on scale, tag count, redundancy, telemetry, interfaces and support. Budget for software licences, integration, infrastructure, communications, training and lifecycle support. A focused pilot helps validate sizing before full rollout.

Should SCADA be on-premises or in the cloud?

Essential control and operator supervision should remain at the level required for autonomous operation. Central or cloud services can add reporting and analytics when the risk assessment supports them. A hybrid architecture is common.

How long does a SCADA pilot take?

A focused pilot often runs for 6 to 12 weeks across a small asset group. It should validate interoperability, alarms, dashboards, history, cybersecurity controls, training and the scale-up plan.

Need help?

I help organisations in South Africa and across Africa use CODRA Panorama Suite as an OT/IT Data Management Platform for SCADA, GeoSCADA, BMS, EMS, Historian, PSIM and MES applications, as well as Unified Control Centres. You can also read IT/OT convergence in Africa: connect the business without weakening operations. Contact me on LinkedIn, read the BPI France interview, or see the CODRA Panorama Suite platform.