Earlier product guidance · version not specified
One order, several systems
One production order may appear in ERP, MES, inspection software and maintenance records. Define which order, batch or work item each record describes and how those objects connect. The general field requirements are in Export requirements.
Order or batch ID
A stable identifier for the object being analysed. If a work order contains several batches, define whether the analysis follows the order or each batch.
Operation and sequence
Activity names with timestamps, and a declared step number or sequence column. Timestamps never substitute for declared order; without it, the events are kept and paths are withheld.
Start and end
Recorded start and end times distinguish step duration from the gaps between steps. A completion-only export supports a narrower set of timing measures.
Optional context
Correctly linked work centres, teams, shift calendars, materials, inspection outcomes and rework reasons allow more detailed comparisons.
Check history and source authority
Use the full operating history.
Request the event history behind each order. A current status such as “Order A: Complete” leaves out the approvals, repeated steps and waiting needed to reconstruct its journey.
Define the source of each measure.
The Engine uses explicit source authority, roles and field mappings. These define where order and duration come from; unavailable measures remain visible as gaps.
Review inputs and formats