The automation pyramid

ALearning Material

Industrial automation organises a factory's control and information systems into layers, the automation pyramid. Each layer talks mainly to the ones directly above and below it, with slower, more "business" timescales as you go up.

‍​‌‌​​‌‌​​‌‌‌​​‌​​‌‌​​‌​‌​‌‌​​‌​‌​​‌​‌‌​‌​‌‌‌​​‌‌​‌‌​​​​‌​‌‌​‌‌​‌​‌‌‌​​​​​‌‌​‌‌​​​‌‌​​‌​‌‍A factory isn't one system but a stack of them, and the automation pyramid is the map of how they relate. Each layer talks mostly to its immediate neighbours, and the timescale stretches as you climb: milliseconds of real-time control at the bottom, seconds of supervision above that, and hours-to-weeks of operations and business planning at the top. Seeing a plant as these layers is what lets you place any device, protocol, or requirement in context.

The principle that makes the pyramid more than a diagram is that time and trust decrease as you go up. The bottom must react instantly and must never fail; the top plans at leisure. So the architecture deliberately decouples them. A hiccup in the business network at the top must never be able to stall a motor at the bottom. That separation isn't just tidy organisation; it is a safety and security boundary, and it's the lens for the whole automation topic.

        ┌─────────────────────┐
   L4   │  ERP (business)     │   days/weeks: orders, inventory, planning
        ├─────────────────────┤
   L3   │  MES (operations)   │   hours/shifts: scheduling, quality, tracking
        ├─────────────────────┤
   L2   │  SCADA / HMI        │   seconds: supervise, visualise, alarms
        ├─────────────────────┤
   L1   │  PLC / DCS (control)│   milliseconds: real-time control logic
        ├─────────────────────┤
   L0   │  Field devices      │   physical: sensors & actuators
        └─────────────────────┘

• ‍​‌‌​​‌‌​​‌‌‌​​‌​​‌‌​​‌​‌​‌‌​​‌​‌​​‌​‌‌​‌​‌‌‌​​‌‌​‌‌​​​​‌​‌‌​‌‌​‌​‌‌‌​​​​​‌‌​‌‌​​​‌‌​​‌​‌‍L0 Field: sensors (measure) and actuators (act): the physical edge.
• L1 Control: PLCs/DCS executing real-time logic (the scan cycle you learned).
• L2 Supervisory: SCADA/HMI: screens operators watch, set setpoints, see alarms and trends. Supervises, doesn't do the fast control itself.
• L3 MES (Manufacturing Execution System): turns production orders into work, tracks what was actually made, quality, downtime.
• L4 ERP (Enterprise Resource Planning): business: orders, inventory, finance.

Key principle: time and trust decrease as you go up. The bottom reacts in milliseconds and must never fail; the top plans in days. A network glitch at L4 shouldn't stop a motor at L1. This separation is also a safety and security boundary.

SCADA vs HMI: - HMI (Human-Machine Interface): the local screen/panel on a machine. - SCADA (Supervisory Control And Data Acquisition): the wider system that collects data from many PLCs/sites, displays it centrally, logs history, and raises alarms.

‍​‌‌​​‌‌​​‌‌‌​​‌​​‌‌​​‌​‌​‌‌​​‌​‌​​‌​‌‌​‌​‌‌‌​​‌‌​‌‌​​​​‌​‌‌​‌‌​‌​‌‌‌​​​​​‌‌​‌‌​​​‌‌​​‌​‌‍Why it exists. A factory has thousands of devices and decisions spanning milliseconds to weeks; without a clear structure it becomes an unmanageable, unsafe tangle. The automation pyramid is the map (which layer does what, how fast, and who talks to whom) so control, supervision, and business each stay in their lane.

Mental model. A restaurant. L0 = ingredients and the stove. L1 = the line cooks following recipes precisely and fast. L2 = the head chef watching all stations. L3 = the shift manager scheduling orders. L4 = the owner deciding what's on the menu and ordering supplies. Each layer trusts the one below to execute.

Common misunderstandings.

• "Higher layers control the machines." Higher layers supervise and plan; the fast, must-never-fail control happens at L1. A glitch up at ERP must never stop a motor.
• "SCADA and HMI are the same thing." An HMI is the local panel on one machine; SCADA is the wider system gathering data from many PLCs/sites, logging history and alarms.
• "Every layer reacts in real time." Timescales grow up the pyramid. Milliseconds at the field, days at the top; only the bottom is hard real-time.

‍​‌‌​​‌‌​​‌‌‌​​‌​​‌‌​​‌​‌​‌‌​​‌​‌​​‌​‌‌​‌​‌‌‌​​‌‌​‌‌​​​​‌​‌‌​‌‌​‌​‌‌‌​​​​​‌‌​‌‌​​​‌‌​​‌​‌‍Connections. This layering frames the whole industrial half of the course: the PLC/DCS scan cycle is L1, SCADA/HMI is L2 (and the HMI+PLC+SCADA capstone), and the separation principle becomes the IT/OT security boundary (Turn 2's industrial-networks lesson) and the independence of safety systems (the functional-safety lesson).

BImmediate Active Recall

‍​‌‌​​‌‌​​‌‌‌​​‌​​‌‌​​‌​‌​‌‌​​‌​‌​​‌​‌‌​‌​‌‌‌​​‌‌​‌‌​​​​‌​‌‌​‌‌​‌​‌‌‌​​​​​‌‌​‌‌​​​‌‌​​‌​‌‍CConceptual Questions

Answer each in your own words in the box, then reveal the model answer to compare. These ask why, not how, and your answers are saved.

DPractice Problems

P1 (easy). Which layer does a temperature transmitter belong to? A production schedule?

P2 (medium). An operator changes a tank's target level on a screen and watches a trend graph. Which layer are they at, and which layer actually holds the level?

P3 (harder). Why is it a red flag, security-wise, if the L1 controllers are directly reachable from the L4 business network?

EFeynman Exercise

Explain the automation pyramid to a beginner with the restaurant analogy. Match each kitchen role to a layer and say what timescale it works on. Then explain why "the owner deciding the menu" should never be able to directly burn the food. I.e., why the layers are kept separate.

FError Analysis Framework

• Flattening the layers. Why: convenience. Recognise: business systems wired straight to controllers. Avoid: segment networks; respect the hierarchy.
• ‍​‌‌​​‌‌​​‌‌‌​​‌​​‌‌​​‌​‌​‌‌​​‌​‌​​‌​‌‌​‌​‌‌‌​​‌‌​‌‌​​​​‌​‌‌​‌‌​‌​‌‌‌​​​​​‌‌​‌‌​​​‌‌​​‌​‌‍Confusing SCADA with control. Why: both "control rooms." Recognise: expecting SCADA to do millisecond loops. Avoid: SCADA supervises; PLC/DCS controls.
• HMI vs SCADA mix-up. Why: both are screens. Recognise: scoping a single panel as a plant-wide system. Avoid: HMI = local, SCADA = system-wide.
• Ignoring timescale. Why: treating all data as urgent. Recognise: overloading control networks with reporting traffic. Avoid: match data flow to layer timescale.

GMini Challenge

For a packaging line, place each on the pyramid and name its layer: a proximity sensor, a PLC running the fill sequence, an operator screen showing alarms, and the system that schedules today's production orders. Then say why the bottom must not depend on the top.

Quiz Check

A quick auto-graded check, separate from the recall cards above. Your score is pooled with the recall cards into this module's Mastery score, and completing this lesson requires the quiz submitted with pooled mastery at 80% or above‍​‌‌​​‌‌​​‌‌‌​​‌​​‌‌​​‌​‌​‌‌​​‌​‌​​‌​‌‌​‌​‌‌‌​​‌‌​‌‌​​​​‌​‌‌​‌‌​‌​‌‌‌​​​​​‌‌​‌‌​​​‌‌​​‌​‌‍.