🎓 Lesson 13 D5

Case Review: Automotive Stamping Press Dashboard Latency Incident

Dashboard latency is the delay between when a machine produces data and when that data appears on the operator’s screen.

🎯 Learning Objectives

  • Analyze HMI system architecture to identify latency contributors across OSI layers 1–7
  • Calculate total system latency by summing deterministic and stochastic components (scan, serialization, queuing, rendering)
  • Design an energy-aware HMI update strategy that balances visual fidelity, update rate, and CPU/GPU power consumption
  • Explain how dashboard latency violates IEC 61508 SIL-2 timing constraints for real-time monitoring in press automation

📖 Why This Matters

In automotive stamping, a 200-ms dashboard latency on a 1,500-ton servo-hydraulic press caused operators to misjudge stroke timing—leading to three consecutive die crashes during high-speed production. Unlike batch processes, stamping requires sub-100-ms visibility for manual intervention or adaptive control. This incident reveals how 'invisible' latency degrades human-in-the-loop reliability—and why energy-aware HMI design must prioritize timing predictability over raw throughput.

📘 Core Principles

Latency in HMIs is not monolithic—it emerges from layered subsystems: (1) Field-level acquisition (sensor response + analog/digital conversion), (2) Control-level processing (PLC scan cycle, tag polling, buffering), (3) Network transport (deterministic vs. best-effort protocols, jitter, packetization), (4) HMI runtime execution (data binding, visualization engine, GPU compositing), and (5) Display output (refresh rate, V-sync, frame buffering). Energy-aware design introduces trade-offs: aggressive polling reduces latency but increases CPU load and heat; compressed data transfer saves bandwidth but adds decode latency. ISO/IEC 62443-3-3 mandates timing budgets for safety-related visualization, while ISA-95 defines acceptable latency thresholds for supervisory decision support (<500 ms for Level 3 MES integration).

📐 Total Deterministic Dashboard Latency (TDDL)

TDDL estimates worst-case latency under nominal load by summing dominant deterministic components. It excludes network jitter and garbage-collection pauses—those require statistical modeling—but serves as the foundational baseline for energy-aware tuning.