Executive summary
Panorama Suite can provide a shared operational data layer for Building Management System (BMS) and Energy Management System (EMS) applications. A BMS concentrates on the real-time operation of building services. An EMS adds the longer-term measurement, comparison and improvement of energy and utility performance. They overlap, but they are not identical.
The practical objective: connect HVAC, electrical distribution, lighting, water, lifts, meters and selected safety or security information around one operational model, while keeping appropriate local control and specialist subsystems in place.
CODRA describes Panorama as able to collect and analyse information from lighting, water, energy, LV/HV networks, lifts and access control. Its H2 Energy offer adds utility-focused collection, historisation and analysis. See CODRA’s SCADA System in Building sector – BMS/FM and Boost your drive to energy efficiency with H2 Energy.
Compare energy performance across sites without replacing existing systems
Which sites consume unnecessarily outside operating hours, and what should we investigate first? Panorama can bring meter readings, building-system status and operating schedules into a shared view. Validate the interfaces and metering boundaries first, then use the data to prioritise investigation.
Illustrative scenario: an estates manager oversees branches with different meters and BMS installations. One branch has a high overnight baseload. The team needs to establish whether cooling, lighting or another load remains active before deciding on an intervention.
Make site comparisons meaningful
- Check units, scaling, timestamps, collection intervals, missing readings and meter resets.
- Compare equivalent periods and account for opening hours, floor area, occupancy or production activity, and weather where relevant.
- Distinguish electricity consumption, peak demand and cost; apply the relevant tariffs only when reliable tariff data is available.
- Relate a deviation to equipment status and assign investigation to the responsible site team.
What a first energy pilot should prove
Select representative sites, meters and an HVAC installation. Reconcile the collected values with source readings, identify out-of-hours consumption, review its operating context and route an agreed exception to a named team. Record the baseline and subsequent action before claiming savings.
A documented African reference
The CFAO Green Infra reference in Côte d’Ivoire (PDF, French) documents energy monitoring coordinated from Abidjan, with 11 sites installed out of 30 at publication. It describes local supervision, central administration and Store & Forward. The 30% consumption reduction is a target, not a measured result. See the published scope and additional references.
Prepare your project enquiry
Share the country, number and type of buildings, meters and BMS versions, available interfaces, operating schedules and the energy deviation you want to investigate.
Why building and energy operations become fragmented
Large buildings and estates rarely begin with one coherent architecture. They accumulate HVAC controllers, electrical meters, generators, UPS systems, access control, fire panels, lifts, water systems and specialist applications from different generations and manufacturers. Each subsystem may work, while the operating team still has no common view of alarms, consumption or site performance.
The cost of fragmentation appears in daily operations: repeated alarms, manual consolidation, inconsistent naming, slow diagnosis and upgrades that force a decision about one supplier’s wider ecosystem. A vendor-independent platform creates an integration layer above that diversity. It does not require every field system to be replaced.
One platform for BMS and EMS applications
BMS application
Operate the building in real time
Consolidate status, alarms, commands and visualisation for HVAC, electrical services, water, lighting, lifts and other technical systems according to each operator’s role.
EMS application
Understand and improve utility performance
Historise electricity, water, gas, steam or compressed-air data; compare periods and sites; and give energy teams evidence for investigation and improvement.
Panorama Suite supports standard and specialist communications, but every project must validate the exact protocols, device profiles, drivers and gateways required by the installed base. Data quality, metering boundaries and naming conventions matter as much as connectivity.
Multi-site operations without losing local autonomy
Retail portfolios, banks, campuses, hospitals, airports and data-centre groups often need a central view without making every site dependent on a permanent WAN connection. An Edge-to-Service architecture can keep essential BMS operation local while centralising selected alarms, energy data, administration and fleet-level comparisons.
The design should specify what remains available during a network outage, which commands may be issued centrally, how data is buffered and synchronised, and who owns the application after handover. CODRA documents this distributed pattern in Panorama Edge-to-Service.
Operational and energy use cases
- Data centres: correlate cooling, electrical capacity, UPS, generators, environmental conditions and site alarms.
- Commercial and public estates: compare utility performance across branches, offices, schools, hospitals or government buildings.
- Transport and campuses: coordinate distributed technical systems while maintaining site-level operation.
- Industrial facilities: connect building utilities with production context without merging every control responsibility.
Automatic Fault Detection (AFD) can support investigation by learning normal historical behaviour and alerting teams to abnormal patterns. It is decision support, not a substitute for instrumentation, engineering limits or maintenance procedures. See CODRA’s AFD: detect the abnormal before it becomes an incident.
How to evaluate a BMS and EMS project
- Define the operating decisions: identify the alarms, commands, comparisons and reports that teams must act on.
- Map the installed base: controllers, meters, protocols, networks, existing BMS applications and data ownership.
- Set the energy boundaries: utilities, tariff periods, baselines, submeters, production or occupancy context and data-quality rules.
- Design resilience: local autonomy, WAN loss, redundancy, buffering, backup and recovery.
- Prove a representative pilot: include at least one difficult subsystem, a usable operator workflow and an auditable energy use case.
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.
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.
CFAO Green Infra · Côte d’Ivoire · 2026
CFAO Green Infra uses Panorama Edge-to-Service and H2.Cloud for energy monitoring coordinated from Abidjan. The published account records 11 sites installed out of 30, local supervision, central administration and Store & Forward to preserve data during network outages. Site managers receive reports and alerts on energy and environmental conditions. The 30% consumption reduction is a target; extension to Côte d’Ivoire, Senegal and Cameroon is described as a progressive programme, not evidence of completed deployment in all three countries.
Read the CODRA customer reference (PDF) · FR
Hager · France · 2025
At Obernai, Panorama Data Historian supports energy monitoring across ten buildings, with 600 power meters identified in the 2025 account. Teams create and share reports without writing SQL. Hager reports 14 working hours saved each week and energy-report preparation reduced from two days to one hour. These are customer-specific reported outcomes, not a guaranteed saving for another project.
Read the CODRA customer reference (PDF) · EN
Brussels South Charleroi Airport · Belgium / Belgique · 2023
With Equans, Charleroi Airport uses Panorama for airport facilities and building services, baggage-handling supervision and interfaces to other business systems. The 2023 publication records 72,000 m² supervised, 27,000 external variables and 14,000 alarms, and describes the addition of Panorama H2 for energy reporting. This documents technical airport integration, not a complete APOC or air-traffic-control system. The reported parking electricity saving accompanied LED lighting upgrades supported by supervision.
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 BMS and EMS, select a meter and an HVAC installation representative of the estate. Check units, scaling, collection intervals and meter resets before comparing consumption. Ask the pilot to connect an energy deviation to equipment operation; establish a baseline before making any savings claim.
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, number and type of buildings, meters and BMS versions, available interfaces, operating schedules and the energy deviation you want to investigate.
Frequently asked questions
What is the difference between a BMS and an EMS?
A BMS focuses primarily on the real-time operation of building services. An EMS focuses on measuring, analysing and improving energy and utility performance. A shared OT/IT data platform can support both while keeping their responsibilities clear.
Does Panorama Suite replace every building controller?
No. It can integrate and coordinate heterogeneous systems while existing controllers and specialist applications remain where they are appropriate. Each interface still needs to be validated.
Can one BMS and EMS cover multiple sites?
Yes. A distributed architecture can preserve essential local operation while providing central visibility, administration and performance comparison across sites. Connectivity-loss behaviour must be designed explicitly.
Is a BMS application the same as SCADA?
BMS and SCADA overlap in real-time supervision and control, but they describe different application contexts. On this website, both are applications enabled by the broader Panorama Suite OT/IT Data Management Platform.
Can AFD guarantee energy savings?
No. Automatic Fault Detection can identify abnormal behaviour earlier and support investigation. Savings depend on instrumentation, data quality, operating conditions and the organisation’s ability to act on findings.
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.