Industrial systems have strict timing requirements that vary by automation level. A motor control loop that misses its 1ms deadline can cause equipment damage, while an enterprise report delivered a few seconds late has no operational impact. Understanding these timing requirements is fundamental to designing effective industrial IoT systems.
Minimum Viable Understanding: Real-Time & ISA-95
Core Concept: The ISA-95 standard defines a five-level automation pyramid that maps industrial systems from field devices (sub-millisecond response) up to enterprise planning (hours-to-days). Each level has distinct timing requirements, and choosing the wrong technology for a given level can cause equipment damage, safety incidents, or wasted resources.
Why It Matters: A missed 1ms deadline in a servo motor control loop can shatter a grinding wheel or crash a robot arm into a workpiece – costing $10,000-$500,000 per incident. Conversely, using expensive hard real-time hardware for enterprise reporting wastes budget. ISA-95 gives engineers a systematic framework to match timing requirements to technology choices, ensuring safety-critical functions get guaranteed response times while business functions use cost-effective IT infrastructure.
Key Takeaway: Always design from the bottom up – identify the hardest real-time constraint first (usually Level 0-1 safety or motion control), select deterministic protocols and RTOS platforms for those functions, then relax requirements as you move up the pyramid toward enterprise integration. Never attempt to use cloud or IT technologies for hard real-time control.
Sensor Squad: Sammy Learns About Factory Speed Limits!
Hey there, young engineer! Sammy the Sensor has discovered that factories have speed limits – just like roads!
The Factory Speed Pyramid: Imagine a factory is like a tall building with 5 floors:
Basement (Level 0): This is where the actual machines live – robot arms, conveyor belts, temperature sensors. They need to react SUPER fast – like catching a ball that is thrown at you! (Less than 1 millisecond – that is 1/1000th of a second!)
Floor 1 (Level 1): The “brain boxes” (PLCs) that tell machines what to do. They need to be fast too – like a goalkeeper saving a penalty! (1-10 milliseconds)
Floor 2 (Level 2): The big screens where humans watch everything happening. Humans are slower than machines, so updates every second are fine – like checking the scoreboard during a game!
Floor 3 (Level 3): The factory managers planning what to make next. They work in minutes and hours – like a coach planning the next play.
Floor 4 (Level 4): The big bosses deciding what products to build next month. They work in days and weeks – like planning what sport to play next season!
Why Speed Matters: Imagine if the brain box (PLC) told a robot arm to STOP, but the message took 5 whole seconds to arrive. The robot would have already crashed into something! That is why faster floors need special “express delivery” networks, while the upper floors can use regular internet – just like how an ambulance needs a siren to go fast, but a mail truck can take the regular road.
Sensor Squad Memory Trick:
Level 0-1 = Lightning fast (machines talking to machines)
Level 2 = Human speed (people watching screens)
Level 3-4 = Planning speed (thinking and deciding)
Hard real-time = MUST arrive on time, or something breaks!
Soft real-time = Should be fast, but a tiny delay is OK
54.4 ISA-95 Automation Pyramid
Time: ~10 min | Difficulty: Intermediate | Unit: P03.C06.U05
Key Concepts
IoT Architecture: Layered model comprising perception, network, and application tiers defining how sensors, gateways, and cloud services interact.
Edge Computing: Processing data close to the sensor source to reduce latency, bandwidth costs, and cloud dependency.
Telemetry: Time-stamped sensor readings transmitted from a device to a cloud or edge platform for storage, analysis, and visualisation.
Protocol Stack: Set of communication protocols layered from physical radio to application message format that devices must implement to interoperate.
Device Lifecycle: Stages from manufacture through provisioning, operation, maintenance, and decommissioning that IoT management platforms must support.
Security Hardening: Process of reducing attack surface by disabling unused services, applying least-privilege access, and enabling encrypted communications.
Scalability: System property ensuring performance and cost remain acceptable as the number of connected devices grows from prototype to mass deployment.
The ISA-95 standard (also known as IEC 62264) defines the interface between enterprise and control systems:
ISA-95 Automation Pyramid
Figure 54.1: ISA-95 automation pyramid showing five levels with timing requirements from enterprise planning (hours-days) down to field devices (sub-millisecond).
54.5 Timing Requirements by Level
54.5.1 Level 0: Field Devices (Sub-millisecond)
The physical interface with the manufacturing process:
Try it: Adjust the system type and number of devices to see how timing requirements and bandwidth change across ISA-95 levels. Notice how motion control requires orders of magnitude faster response times than enterprise planning.
54.7 Determinism vs. Throughput
Industrial systems distinguish between different real-time guarantees:
54.7.1 Hard Real-Time (Deterministic)
Definition: Must respond within guaranteed time; missing deadline is system failure.
Characteristics:
Worst-case execution time (WCET) must be bounded
Jitter must be minimal (<1μs for synchronized motion)
Try it: Adjust the actual jitter value to see how different applications tolerate timing variation. Notice that printing presses and semiconductor handling require sub-microsecond precision, while simple I/O can tolerate milliseconds of jitter.
Knowledge Check: Real-Time Requirements
Question 1: A printing press requires a cycle time of 125 microseconds with maximum jitter of 1 microsecond. Which type of real-time guarantee does this require?
Best effort
Soft real-time
Hard real-time
Near real-time
Answer
c) Hard real-time – A printing press with a 125 microsecond cycle time and 1 microsecond maximum jitter tolerance is a classic hard real-time application. Missing a deadline would cause visible print defects (color misregistration, smearing). Hard real-time requires guaranteed worst-case execution time (WCET) and minimal jitter, typically implemented with specialized hardware like EtherCAT with distributed clocks.
Question 2: At which ISA-95 level would you place a SCADA system that displays alarm conditions to plant operators?
Level 0 – Field Devices
Level 1 – Basic Control
Level 2 – Supervisory
Level 3 – Operations
Answer
c) Level 2 – Supervisory – SCADA (Supervisory Control and Data Acquisition) systems operate at ISA-95 Level 2, which handles monitoring and supervision of production processes. Level 2 includes HMI displays, alarm management, historical data logging, and recipe management. The timing requirement is soft real-time (100ms-1s), which is appropriate for human-operator interfaces.
Question 3: Why is jitter often more critical than absolute latency for synchronized motion control?
Jitter is easier to measure than latency
Coordinated axes need to arrive at positions at exactly the same time, so timing consistency matters more than speed
Jitter only affects wireless networks
Lower jitter always means lower latency
Answer
b) Coordinated axes need to arrive at positions at exactly the same time, so timing consistency matters more than speed – In a multi-axis robot, all servo motors must receive their position commands at precisely the same instant. If one axis is consistently 5ms late but all axes have the same 5ms delay, the motion is perfectly coordinated. But if one axis varies randomly between 1ms and 9ms (high jitter), the axes become unsynchronized, causing mechanical stress, poor surface finish, or collisions.
54.10 Technology Mapping
The following diagram shows how protocols, platforms, and network architectures align with ISA-95 levels:
Try it: Adjust the response time requirement and safety criticality to see how the recommended ISA-95 level changes. The tool applies the decision framework to match your requirements to the appropriate automation level.
Knowledge Check: Technology Mapping
Question 4: An engineer needs to connect 100 PLCs to a Manufacturing Execution System (MES) for production scheduling. Which protocol and ISA-95 level boundary does this cross?
EtherCAT at Level 0-1 boundary
OPC-UA at Level 2-3 boundary
PROFINET IRT at Level 1-2 boundary
MQTT at Level 3-4 boundary
Answer
b) OPC-UA at Level 2-3 boundary – Connecting PLCs (Level 1-2) to an MES (Level 3) crosses the Level 2-3 boundary, which is exactly where OPC-UA excels. OPC-UA provides the semantic data modeling needed for MES integration (production orders, quality data, genealogy), built-in security for the IT/OT boundary, and platform-independent communication.
Question 5: A factory floor network uses air-gapped segmentation. Which ISA-95 level does this practice primarily protect?
Level 4 – Enterprise systems need air gaps from the internet
Level 0-1 – Critical control networks must be physically isolated from IT networks
Level 3 – MES systems require air gaps from SCADA
All levels equally use air-gapped segmentation
Answer
b) Level 0-1 – Critical control networks must be physically isolated from IT networks – Air-gapped segmentation is primarily used at Level 0-1, where dedicated industrial networks (EtherCAT, PROFINET IRT) carry safety-critical and hard real-time control traffic. These networks must be physically isolated from IT networks to prevent cyberattacks from reaching PLCs, safety controllers, and field devices. A compromised Level 0-1 network could cause physical damage, equipment destruction, or endanger human life.
54.12 Case Study: Automotive Assembly Line Design
You are designing the control system for an automotive assembly line with:
100 robotic arms: Each with 6 axes (600 servo motors total)
1,000 quality inspection sensors: Vision systems, force sensors, laser scanners
50 AGVs: Automated guided vehicles delivering parts
10 operator stations: HMIs for monitoring and manual intervention
Requirements:
All robots must be synchronized within 1ms
Quality data must be logged for 10-year traceability
AGVs must avoid collisions with <100ms response time
Operators need real-time production status
Enterprise ERP system needs hourly production counts
Predictive maintenance for all critical assets
54.12.1 Solution: Latency Requirements
Robotic motion control: <1ms hard real-time, <1μs jitter for synchronization
Try it: Adjust the number of motors, signals per motor, and sampling rate to see how bandwidth requirements scale. Notice how edge processing dramatically reduces cloud costs - a 4,000x reduction makes the difference between $5,589/month and $1.40/month.
Key architectural decisions:
Edge processing: FFT and feature extraction at Level 2 reduces cloud bandwidth by 10,000x
Time-series database: Dedicated historian (OSIsoft PI, Ignition) handles 50K data points/second
OPC-UA server: Provides unified namespace for all 51,000 data points
Data lake: Raw data retained for 10 years in cloud object storage
Security: Network segmentation, OPC-UA encryption, VLANs separate control and IT networks
After edge processing: 1 Hz features = 6 KB/second to cloud
Reduction factor: 4,000×
Putting Numbers to It
An automotive assembly line with 600 servo motors, each reporting 10 signals (position, velocity, current, temperature, etc.) at 1ms intervals generates massive data volumes:
The 4,000× reduction (\(24 \text{ MB/sec} \to 6 \text{ KB/sec}\)) makes cloud analytics economically viable: AWS data transfer at $0.09/GB would cost \(\$5,589/month\) for raw data vs \(\$1.40/month\) for processed features.
For Beginners: Real-Time Systems Simplified
What is “real-time”? It means the system must respond within a specific time limit. Think of it like a deadline:
Hard real-time: Like a goalkeeper – you MUST save the ball in time, or it is a goal. Missing the deadline is a failure (e.g., emergency stop must activate within 10ms).
Soft real-time: Like a bus schedule – being 2 minutes late is annoying but acceptable. Missing the deadline degrades quality but does not cause failure.
Best effort: Like postal mail – it arrives when it arrives, with no guaranteed delivery time.
What is ISA-95? It is a standard that organizes a factory into 5 floors (levels), each with different speed requirements. The bottom floors need lightning-fast responses (controlling machines), while the top floors handle slow business decisions (planning what to build next month).
The key rule: Always use the right tool for the right floor. You would not use a racing car to deliver furniture (too expensive), and you would not use a delivery truck to race in Formula 1 (too slow). Similarly, do not use cloud computing to control a robot arm, and do not use a PLC to run your ERP system.
Decision Framework: Matching Technology to ISA-95 Levels
When designing industrial IoT systems, the biggest mistake is using the wrong technology for the wrong level. This decision framework helps you match computing platforms, protocols, and architectures to automation levels.
Level
Timing
Example Application
Right Technology
Wrong Technology (Why)
0-1
<1ms
Servo motor control
PLC + EtherCAT
Cloud API (200ms latency – motor crashes before alert)
1-2
1-10ms
Discrete I/O, safety
PLC + PROFINET
Wi-Fi + MQTT (packet loss breaks safety)
2
100ms-1s
HMI displays
Industrial PC + SCADA
Consumer laptop (not rated for factory floor)
3
Seconds
MES batch tracking
On-prem server + OPC-UA
Edge gateway (insufficient compute for MES)
4
Minutes-hours
ERP planning
Enterprise cloud
PLC (PLCs don’t run SAP)
Decision Tree:
Q1: Does a missed deadline cause physical damage or safety risk?
Yes → Hard real-time (Levels 0-1) → Use PLC/PAC with deterministic network (EtherCAT, PROFINET IRT)
No → Proceed to Q2
Q2: Is response time under 100ms required?
Yes → Soft real-time (Level 1-2) → Use PLC with standard industrial Ethernet (PROFINET IO, EtherNet/IP)
No → Proceed to Q3
Q3: Does it involve human interaction or visualization?
Yes → Level 2 (SCADA/HMI) → Industrial PC with SCADA software (Ignition, WinCC)
No → Proceed to Q4
Q4: Does it coordinate production workflows or track quality?
Yes → Level 3 (MES) → Server-grade hardware with MES software (Siemens Opcenter, Rockwell FactoryTalk)
No → Proceed to Q5
Q5: Is it business planning, finance, or supply chain?
Yes → Level 4 (ERP) → Enterprise cloud or data center (SAP, Oracle)
Real Example – Assembly Line Robot:
Level 0-1: Servo drives (EtherCAT, <100μs cycle) – controls arm position
Level 3: MES server (OPC-UA, 10s) – tracks which product variant is running
Level 4: ERP cloud (REST API, 1 hour) – orders more parts when inventory low
Key Principle: Never use higher-level (slower) tech for lower-level (faster) requirements. The opposite is OK but wasteful – using EtherCAT for HMI updates works but costs 10× more than needed.
Concept Relationships: Real-Time & ISA-95
Concept
Relates To
Relationship
Hard Real-Time
EtherCAT/PROFINET IRT
Deterministic protocols guarantee sub-millisecond response for Level 0-1 safety and motion control
ISA-95 Levels
Technology Selection
Each level has distinct timing requirements: Field (μs), Control (ms), Supervisory (100ms), Operations (seconds), Enterprise (hours)
Jitter
Multi-Axis Synchronization
Timing variation between coordinated axes more critical than absolute latency for precision motion
OPC-UA
Level 2-3 Boundary
Bridges real-time control (PLCs) to business systems (MES/ERP) with semantic data models and security
Cross-module connection: Industrial Protocols explains how EtherCAT achieves <100μs cycle times with <1μs jitter using time-triggered communication and distributed clocks for Level 0-1 hard real-time control.
Interactive Quiz: Match ISA-95 Concepts
Interactive Quiz: Sequence ISA-95 System Design
Common Pitfalls
1. Over-Engineering the Initial Prototype
Adding too many features before validating core user needs wastes weeks of effort on a direction that user testing reveals is wrong. IoT projects frequently discover that users want simpler interactions than engineers assumed. Define and test a minimum viable version first, then add complexity only in response to validated user requirements.
2. Neglecting Security During Development
Treating security as a phase-2 concern results in architectures (hardcoded credentials, unencrypted channels, no firmware signing) that are expensive to remediate after deployment. Include security requirements in the initial design review, even for prototypes, because prototype patterns become production patterns.
3. Ignoring Failure Modes and Recovery Paths
Designing only for the happy path leaves a system that cannot recover gracefully from sensor failures, connectivity outages, or cloud unavailability. Explicitly design and test the behaviour for each failure mode and ensure devices fall back to a safe, locally functional state during outages.
Label the Diagram
💻 Code Challenge
54.14 Summary
Real-time requirements and ISA-95 levels provide a systematic framework for industrial system design:
ISA-95 pyramid: Five levels from field devices (sub-millisecond) to enterprise (hours-days) with distinct timing requirements and technologies appropriate to each level. The standard (IEC 62264) provides the definitive interface model between enterprise and control systems.
Determinism matters: Hard real-time systems require guaranteed worst-case timing with bounded jitter; soft real-time tolerates occasional delays with statistical QoS; best-effort has no timing guarantees. Choosing the wrong class can cause safety incidents (under-specifying) or wasted budget (over-specifying).
Jitter vs latency: For synchronized motion control, consistent timing (low jitter) is often more critical than absolute speed. IEEE 1588 PTP and EtherCAT distributed clocks provide sub-microsecond synchronization for multi-axis coordination.
Technology mapping: Protocol, computing platform, and network architecture choices must align with the timing requirements of each ISA-95 level. Use EtherCAT/PROFINET IRT for Level 0-1, PROFINET/EtherNet/IP for Level 1-2, OPC-UA for Level 2-3 bridging, and REST/MQTT for Level 3-4 cloud integration.
Design principle: Never use higher-level (slower) technologies for lower-level (faster) requirements. Cloud cannot control motors; PLCs should not run ERP. Design from the bottom up – secure the hardest real-time constraint first, then relax requirements as you ascend the pyramid.
54.15 See Also
Industrial Protocols — Comparison of EtherCAT, PROFINET IRT, EtherNet/IP with latency and jitter specifications for each ISA-95 level
Real-Time Operating Systems — VxWorks, QNX, RTAI architecture for guaranteed worst-case execution time (WCET) at Level 0-1
Time-Sensitive Networking — IEEE 802.1 TSN extensions for deterministic Ethernet suitable for industrial control
OPC-UA Standard — Level 2-3 integration protocol that bridges real-time control to business systems with semantic data models
In 60 Seconds
This chapter covers real-time & isa-95, explaining the core concepts, practical design decisions, and common pitfalls that IoT practitioners need to build effective, reliable connected systems.
