Features#
Each feature page contains its business purpose, node contract, communication-flow diagram, step-by-step behavior, failure behavior, assumptions, and validation checks.
| Feature | Direction | Trigger |
|---|---|---|
| Track In | Machine or operator → MES | Operation request or MES UI operation |
| Recipe Download | MES → Machine | Successful recipe resolution during Track In |
| Data Collection | Machine → MES | MachinePostDataRequest |
| Track Out | Machine or operator → MES | Operation request or MES UI operation |
| Abort | Machine or operator → MES | Operation request or MES UI operation |
| State Synchronization | Machine → MES | Machine state value change |
Read Operation Handshake first for the ownership, ordering, missing-acknowledgement, reset, and idempotency rules shared by Track In, Track Out, and Abort.
Use the Node Reference for the fixed node paths, dynamic Parameter patterns, data types, ownership, access, and initial values that support these feature flows.