Industrial system commands checked at execution time to avoid mistakes

Execution-Time Validation of Context-Carrying Action Intents in Industrial Cyber-Physical Systems

Programming LanguagesCryptography and SecurityDistributed, Parallel, and Cluster Computing

Summary

In factories, machines get instructions that might become outdated if something changes, like an operator pausing the process. The authors study how to make sure commands are still correct right before they happen, to avoid errors. They propose a system that double-checks these commands at the last moment and only lets the machine act if the situation is exactly as expected. Their tests show that some checks earlier in the process miss brief pauses, but checking at execution time closes this gap.

What this means in practice

  • For industrial control teams: Ensure factory controllers only execute commands valid under current operational states to avoid errors from delayed command effects.
  • For embedded systems developers: Implement atomic validation and version-conditional command release in embedded controllers to improve reliability under changing plant conditions.

Authors

Luca D'Agati, Giuseppe Tricomi, Fabio Orazio Mirto, Giovanni Merlino

Abstract

In industrial cells, commands from learned policies, operators and schedulers reach the controller after inference, confirmation and transport, and the plant may have changed meanwhile, for instance by an operator pause. Such a command is released, or takes effect, when it is no longer correct. We call this the execution gap and ask which component should make the last check, and against which version of which state. The Action Intent Schema (AIS) is a contract in which a producer states how long its decision stays valid and what it assumes. The runtime XAIR rechecks each intent before release, can commit its authorization atomically in the context store, and can release it as a version-conditional command, which the controller executes only if its version of the state is unchanged. In controlled ablations with declared ground truth on emulated and physical cells, OpenPLC and ARM and RISC-V boards, a check on a replica always left an unprotected interval: a pause written from a few to over 100ms after submission escaped it. Only a check in the scan of a software controller, either a controller-local interlock or the version-conditional command, closed the interval for the state that controller owns; only the version-conditional command also refused commands after a pause that had been undone. A global version revoked up to every valid command under unrelated updates. Versions scoped to what the intent reads, or to the truth of its predicates, did not; with continuous signals on the variables the intent reads, only the latter avoided false revocations, though it burdens the store as predicates accumulate. On one embedded-board core, XAIR validated 148-168 intents/s.