Applications & Use Cases · Study deck
Real-Time ISA-95: Timing Foundations
A factory message can be correct and still arrive too late for control.
Blueprint Bina is your guide for this deck.
After studying this chapter
Learning objectives
You will be able to:
- Explain: Hard real-time describes a deadline for which lateness is failure, not merely inconvenience.: Jitter is cycle-to-cycle timing variation; in synchronized motion, bounded jitter can matter more than average latency.
- Explain: A servo drive, PLC task, HMI alarm, MES work order, and ERP purchase plan all matter, but they live on different time scales and carry different consequences when they arrive late.
- Explain: IoT designs fail when they move Level 0 or Level 1 control decisions into cloud services, dashboards, or business systems that were never built for deterministic deadlines.
Major section
Start With the Story
A filling line must close a valve before a bottle overflows.
- The line controller can act in a fraction of a second.
- A production system can count finished bottles over minutes, while business planning may work across days.
- Sending the fast decision upward through every layer would add delay and mix duties that need different owners.
Major section
Start With the Story (continued)
The layers are not fixed brands or a promise that every factory is arranged alike.
- The deeper sections name the formal levels, timing classes, control loops, production records, and evidence needed when information moves between fast operations and slower planning.
- A machine state may rise to planning.
- A plan may set an approved target.
Major section
Phoebe's Field Notes: Sizing the Anti-Alias Filter for a 1 kHz Motor Loop
The mathematical gist.: A 4–20 mA loop across 250 ohms becomes 1.00–5.00 V, a 4.00 V ADC span.
- At the chapter's 1 ms sample period, 1 kHz sampling sets a 500 Hz Nyquist limit.
Major section
ISA-95 Timing Boundaries
A servo drive, PLC task, HMI alarm, MES work order, and ERP purchase plan all matter, but they live on different time scales and carry different consequences when they arrive late.
- The lower levels are close to the physical process.
- Level 1 controllers run machine logic.
- The useful pattern is to separate control authority from information visibility.
Major section
ISA-95 Timing Boundaries (continued)
IoT designs fail when they move Level 0 or Level 1 control decisions into cloud services, dashboards, or business systems that were never built for deterministic deadlines.
- A cloud dashboard may show a motor-current trend, but it should not close a 1 ms torque loop.
- MES may issue a production order, but it should not bypass a PLC interlock.
- ERP may plan inventory, but it should not decide whether a robot can enter a safety zone.
Major section
ISA-95 Timing Boundaries (continued)
Hard real-time:: Missing the deadline is a system failure, even if the answer eventually arrives.
- Each level can exchange data with the others, but the deadline and safety owner must stay attached to the function.
- That separation also keeps industrial IoT projects honest.
- Soft real-time:: Delay degrades usefulness, but the system can usually continue safely.
Major section
ISA-95 Timing Boundaries (continued)
A machine event may need a local trip, a SCADA alarm, a historian sample, an MES quality hold, and an ERP maintenance cost update.
- The lower levels need deterministic response and fail-safe behavior; the upper levels need context, timestamps, ordering, reconciliation, and business meaning.
- Best effort:: Correctness depends more on completeness, ordering, and reconciliation than on millisecond delivery.
- That visual pairing grounds timing boundary: each layer has a different owner, deadline, failure mode, and acceptable integration technology in named evidence.
- Together those labels make timing boundary: each layer has a different owner, deadline, failure mode, and acceptable integration technology testable.
Major section
Put Decisions at the Lowest Level
As timing relaxes, the architecture can move upward.
- A practical ISA-95 design starts with the fastest unsafe or economically damaging event.
- Emergency stop, light curtain, torque limit, burner management, and motion synchronization belong near certified safety controllers, drives, PLCs, or dedicated real-time hardware.
- SCADA and HMI systems can supervise lines and alarms.
Major section
Put Decisions at the Lowest Level (continued)
None of those bridges should silently become the only place where a local stop, interlock, or critical fallback is decided.
- A dashboard can display their state, but it should not be the path that makes them safe.
- Historians can sample process values for trends.
- ERP can plan demand, inventory, purchasing, and finance.
Major section
Deadlines Beyond Network Speed
A real-time guarantee includes sensing delay, input filtering, PLC scan time, task priority, network scheduling, controller execution, output update, actuator response, and mechanical settling.
- A fast Ethernet link does not fix a slow scan cycle, overloaded gateway, nondeterministic task scheduler, or cloud round trip.
- Higher levels have their own correctness rules.
- ERP integrations need reconciliation and retry.
Major section
Deadlines Beyond Network Speed (continued)
Safety functions may rely on certified PLCs, safety relays, safety-rated drives, PROFIsafe, CIP Safety, or IEC 61508/IEC 61511 engineering practices rather than ordinary application code.
- MES transactions need sequence, genealogy, batch state, operator action, and quality disposition.
- Historians need timestamp source, compression, exception/deviation rules, and data quality.
- These concerns are different from sub-millisecond determinism, but they are still part of a reliable industrial IoT architecture.
Major section
Key Concepts
Hard real-time describes a deadline for which lateness is failure, not merely inconvenience.: Jitter is cycle-to-cycle timing variation; in synchronized motion, bounded jitter can matter more than average latency.
- Those diagram labels establish the scope of isa-95 separates physical process, control, supervisory, operations, and business-planning responsibilities so timing and authority are not collapsed.
Deck summary
Key takeaways
A filling line must close a valve before a bottle overflows.
- The layers are not fixed brands or a promise that every factory is arranged alike.
- The mathematical gist.: A 4–20 mA loop across 250 ohms becomes 1.00–5.00 V, a 4.00 V ADC span.
- A servo drive, PLC task, HMI alarm, MES work order, and ERP purchase plan all matter, but they live on different time scales and carry different consequences when they arrive late.
- IoT designs fail when they move Level 0 or Level 1 control decisions into cloud services, dashboards, or business systems that were never built for deterministic deadlines.
Retrieval practice
Recall check
Blueprint Bina says: answer from memory, then check your reasoning.
Q1A cloud dashboard displays motor-current trends. Where should the fast torque control decision remain?
Show answer
Answer: C The chapter separates upper-level visibility from deterministic machine control authority.
Q2A motor-control path has fast Ethernet but a slow PLC scan. What should the team measure to review its deadline?
Show answer
Answer: B The timing budget includes sensing, scheduling, execution, output, and mechanical response.
Print reference
Answers
Answer key.
- C · The chapter separates upper-level visibility from deterministic machine control authority.
- B · The timing budget includes sensing, scheduling, execution, output, and mechanical response.