Track In#
Overview#
Track In records that a Material has started processing at the MES Resource. It can be initiated by the machine or by an operator at a hybrid station. MES remains responsible for validating the Material, Step, Resource, capacity, hold, dispatch, and other configured Track In requirements.
See Track In Material ↗ for the product transaction behavior.
Nodes#
| Relative node | OPC UA type | Direction | Purpose |
|---|---|---|---|
Operation.TrackIn.Material.Name | String | Machine → MES | Exact MES Material name. May be empty only when FIFO is enabled |
Operation.TrackIn.MachineOperationRequest | Boolean | Machine → MES | Starts a machine-initiated Track In |
Operation.TrackIn.MESOperationPerformed | Boolean | MES → Machine | Indicates that MES performed Track In and is waiting for machine confirmation |
Operation.TrackIn.MachineOperationConfirmed | Boolean | Machine → MES | Acknowledges the performed signal and any downloaded recipe |
Preconditions#
- Resource
EnableAutomationScenariosistrue. - The Material is eligible for the normal MES Track In operation.
- The Resource and Step are correct for the Material.
- A Material name is supplied, or
IndEqAutomationOperationAllowFIFOis enabled. - All Track In nodes have the required access rights.
- If recipe download is enabled, recipe context, parameter nodes, and data types are valid.
Communication Flow#
sequenceDiagram
autonumber
actor O as Operator
participant M as Machine / PLC
participant S as OPC UA Server
participant I as Connect IoT
participant E as Critical Manufacturing MES
alt Machine initiated
M->>S: Write Material.Name
M->>S: MachineOperationRequest = true
S->>I: Request and payload change notification
I->>E: Track In resolved Material
else Operator initiated
O->>E: Track In selected Material in MES UI
end
E->>E: Validate and perform Track In within transaction
opt Recipe management enabled
E-->>I: Resolved recipe and parameters
I->>S: Write Recipe nodes
S-->>M: Recipe values available
end
E-->>I: Track In performed, awaiting machine confirmation
I->>S: MESOperationPerformed = true
S-->>M: Performed signal available
alt Confirmation before MachineReplyTimeout
M->>S: MachineOperationConfirmed = true
S-->>I: Confirmation change notification
I-->>E: Machine confirmed
E->>E: Commit Track In
I->>S: MESOperationPerformed = false
M->>S: Machine-owned bits = false
else MachineReplyTimeout expires
I-->>E: Machine confirmation timeout
E->>E: Roll back Track In
I->>S: MESOperationPerformed = false
end Step-by-Step Process#
Machine-Initiated#
- The PLC writes
Material.Name. - The PLC sets
MachineOperationRequest = true, which raises the machine request through Connect IoT. - Connect IoT requests Track In in MES and provides the explicit Material name when available.
- MES resolves the explicit Material or, when FIFO is enabled, the first eligible Material for the Resource and Step.
- MES validates and performs Track In within the current transaction.
- If recipe management is enabled, MES resolves the recipe and Connect IoT writes its parameters.
- Connect IoT sets
MESOperationPerformed = trueand waits forMachineOperationConfirmed = true. - When confirmation arrives before
MachineReplyTimeout, MES commits Track In. - Both sides return their control bits to
false. - If confirmation does not arrive in time, Track In fails and the transaction rolls back.
Operator-Initiated#
- The operator selects the Material and performs Track In in the MES UI;
MachineOperationRequestis not required. - MES validates and performs Track In within the current transaction.
- If required, recipe parameters are resolved and written to the machine.
- Connect IoT sets
MESOperationPerformed = trueand waits for the machine confirmation. - When confirmation arrives before
MachineReplyTimeout, MES commits Track In. - The result and confirmation bits are reset.
- If confirmation does not arrive in time, the operator receives a failure and the transaction rolls back.
Failure Behavior#
- In MES automation controller type must be
IndEqController - In MES resource
EnableAutomationScenariosmust be set totrue - If Material resolution fails or MES rejects Track In, Connect IoT does not set
MESOperationPerformed. - If the Recipe cannot be resolved or written, the complete transaction rolls back and the Material remains ready to be started.
- If the machine does not set
MachineOperationConfirmed = truebeforeMachineReplyTimeoutexpires, Track In is not successful and its transaction rolls back. - After a timeout, reconcile the MES Material state, machine state, and handshake values before retrying.
Validation and Assumptions#
- Explicit Material Track In selects the correct Material.
- Empty Material is rejected when FIFO is disabled.
- FIFO selects only the first eligible Material when enabled.
- Operator-initiated Track In notifies the machine without a machine request when
EnableAutomationScenarios = true. - Recipe values are available before the PLC accepts the performed signal.
- Failure and missing-acknowledgement paths never create duplicate Track In operations.
- Resource is set as
EnableAutomationScenarios = true - MES automation controller type is
IndEqController