Application guide · Manufacturing, process industry, mining and production performance

MES in Africa with Panorama COOX

Connect machine and operator data to consistent production-performance indicators, while keeping the MES layer interoperable with the wider OT/IT architecture.

Executive summary

Panorama COOX brings Manufacturing Execution System (MES) functions into the Panorama family, with a current emphasis on QPI (Quality and Performance Indicators) and production-performance analysis. It collects equipment and operator information, models the production context and calculates indicators that teams can investigate and act on.

A useful MES does not merely display a high-level KPI. It makes the definitions, source data and causes behind availability, performance and quality losses consistent enough to guide improvement.

See CODRA’s official Panorama COOX MES page and OEE Software: Calculate OEE Without Skewing the Numbers.

The operational gap between machines and enterprise systems

Control systems know what machines are doing in real time. Enterprise systems know orders, customers, inventory and financial commitments. The MES layer connects production execution and performance between them. It must combine automatic machine data with operator context such as stop causes, rejects, shifts and production objectives.

Without that layer, plants often compare spreadsheets built from inconsistent definitions. The same OEE label can conceal different planned-time rules, reject handling or manual assumptions across lines and sites.

What Panorama COOX contributes

  • real-time acquisition from production equipment through interfaces such as OPC Classic, OPC UA and Modbus;
  • a production hierarchy aligned with ISA-88 and ISA-95 concepts;
  • automatic and manual collection of quantities, stops, rejects and operating context;
  • QPI calculations including OEE and related availability, performance, quality, MTBF and MTTR indicators;
  • desktop and web visualisation, event views, dashboards and reporting;
  • exchange with external systems as part of a wider OT/IT architecture.

The exact functional scope must be confirmed against the current Panorama COOX version and licence. Broader COOX Origin modules should not be assumed to be included automatically in a Panorama COOX project.

Comparable KPIs require governed definitions

OEE is the product of availability, performance and quality, but each factor depends on definitions. Planned shutdowns, micro-stops, ideal cycle time, rework and reject attribution must be agreed with production teams. Software can automate the calculation; it cannot decide policy silently.

A sound deployment exposes the cause tree and underlying events so teams can improve the process rather than debate the number. Operators should be able to enter missing context quickly, and managers should be able to compare periods or sites on the same rules.

MES as one application on the OT/IT data platform

Panorama COOX can coexist with SCADA, Historian, BMS, EMS and other operational applications on a shared architecture. The SCADA application retains real-time process control; the Historian preserves operational history; the MES application adds production models, performance context and improvement workflows.

ERP integration should exchange the information each side owns rather than duplicate whole databases. The project should define orders, master data, actual production, quality results and acknowledgement flows with explicit responsibility.

African production contexts

Brownfield plants

Start from heterogeneous equipment

Connect different PLC and machine generations, then normalise production context without requiring a single automation brand.

Multi-site groups

Compare performance on common definitions

Keep line and plant context visible while consolidating approved indicators for regional or group-level decisions.

Manufacturing, food and beverage, materials, mining-related processing and other industrial operations can benefit when the project begins with a concrete loss or decision rather than an abstract dashboard programme.

How to evaluate a MES pilot

  1. Select one representative line or process: include real stops, rejects, changeovers and manual context.
  2. Agree the production model: hierarchy, states, shifts, products, orders and ideal rates.
  3. Govern each indicator: formula, owner, exclusions, source, quality and approval.
  4. Validate operator ergonomics: missing causes and corrections must be quick, controlled and auditable.
  5. Close the improvement loop: prove that teams can identify a loss, investigate it and track the effect of an action.

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 MES and SCADA?

A SCADA application focuses on real-time supervision and control. An MES adds production execution, performance, quality and contextual workflows. They can share data while retaining different responsibilities.

Does MES replace the ERP?

No. The ERP usually owns enterprise planning, commercial and financial information. The MES manages production execution and actual operating context, with controlled exchanges between the two.

Can Panorama COOX connect to existing machines?

Yes, subject to the available protocols and the quality of the machine data. CODRA lists OPC Classic, OPC UA and Modbus among the supported acquisition approaches.

Does Panorama COOX include every COOX Origin MES module?

The precise scope depends on the current product version and licence. A project should confirm which QPI, production-management, traceability or other modules are included rather than assuming the complete COOX Origin range.

What makes an OEE figure trustworthy?

A trustworthy OEE uses governed definitions for planned time, ideal rate, stops, rejects and quality, with traceable source data and consistent application across periods, lines and sites.

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.