Skip to main content

service.mes_scada()

MES, MOM & SCADA

operating context

When MES, MOM and SCADA overlap without direction

MES/MOM/SCADA design is needed when platforms and responsibilities overlap, and the plant no longer knows what runs where, who owns it and how to evolve it.

01

Overlapping layers

Issue

Process logic spread across PLC, HMI, MES and spreadsheets.

Solution

Defines what stays at machine level, what moves to coordination, what enters supervision.

02

Operational data model

Issue

Orders, states, recipes and alarms are modeled inconsistently across platforms.

Solution

Brings orders, states, recipes and quality into a shared ISA-95 model.

03

Cross-line reuse

Issue

Each line evolves independently, reuse is limited to copied screens.

Solution

Defines replicable patterns without losing necessary local specifics.

operating method

How we work: 4 phases in sequence

01

Process mapping

Analysis of the production flow: stages, stations, critical parameters, data collection points.

ISA-95L0–L4roles
02

MES/SCADA architecture

Design of the supervision and production management system. Data model definition and integrations.

ordersstatesrecipes
03

Implementation

Configuration, HMI interface development, PLC connection and staging environment testing.

alarmsqualitytraceability
04

Rollout and tuning

Progressive deployment per line, alarm calibration and operator training.

rolloutreuseownership
expected output

How we structure MES, MOM and SCADA

We do not start from platform naming, but from the split of responsibilities across layers, users and process decisions.

What remains at machine level, what moves into coordination and what belongs in central supervision.

tech spec

Technical spec

explorer
architecture/ 2
operations/ 2
layer-decomposition.md
// mom.layers

Layer decomposition

analisi: Split across PLC, HMI, MES, MOM, SCADA and business systems.
criticità: Duplicated logic, confused roles, messy integrations.
output: Functional layer map with ownership.
ISA-95L0–L4roles
// mom.process

Process model

analisi: Orders, states, recipes, events, alarms, quality and traceability.
criticità: Inconsistent models across platforms, non-aggregable data.
output: Shared operational model aligned with ISA-95.
ordersstatesISA-95
// mom.supervision

Supervision and exceptions

analisi: Shift cockpit, alarm management, escalation and deviations.
criticità: Scattered information, ad-hoc reaction.
output: Supervision view coherent with roles.
cockpitalarmsescalation
// mom.rollout

Rollout template

analisi: Replicable patterns across lines, managed local variations.
criticità: Copy-paste rollout, untracked divergences.
output: Governed template with extension points.
rolloutreusevariants
architecture/layer-decomposition.md Markdown
next_step.initialize

Design your MES/MOM layer

Execution, orchestration and supervision with clear roles and responsibilities.