INDUSTRY FIELD GUIDE
Packaging machinery state logs for AI fault review
A stopped machine can be waiting on a command, responding to an upstream condition, or in a fault state.
NAICS 333993 · Packaging Machinery Manufacturing
A stopped machine can be waiting on a command, responding to an upstream condition, or in a fault state. Its current state is only part of the story. The OPC Foundation’s PackML specification describes common concepts for machine modes and states. An equipment maker can provide a simulator trace that tests whether the model understands why production stopped. OPC Foundation PackML concepts · NIST manufacturing monitoring
Create two timelines with the same period of zero throughput. On one trace, record a commanded pause and an expected transition. On the other, add a warning from a related station and a missing acknowledgment. Name which events came from each source and how the clocks were aligned. The expected answer identifies supporting events, the state boundary, and unresolved timing uncertainty. Keep restart instructions outside the test.
Use simulated tags, generic machine IDs, and timestamps shifted away from real operations. Never include controller programs, safety interlock maps, remote access details, or a customer’s plant network.
Describe a machine-state benchmark
Original Fiund exercise
An upstream hold can coexist with a downstream fault label
Fictional event records use plain state names. No machine control instructions appear.
| Record | Source | What it records |
|---|---|---|
| 1 | Upstream log | Commanded hold active 10:00–10:04. |
| 2 | Downstream log | Fault-labeled interval 10:01–10:03; fault reason blank. |
| 3 | Summary rule | Keep each subsystem's state; derive causation only from explicit evidence. |
Question for the model
What should the joined timeline show?
Show the reference answer and checks
The downstream label overlaps the upstream hold for two minutes and is fully nested within it. Keep both states and their source systems under records 1–3. Overlap alone does not prove the upstream command caused the fault label or that either label should overwrite the other.
- Replacing one subsystem's label with the other's
- Inferring fault cause solely from time overlap
Fields to preserve
- subsystem_id
- Preserves state source
- state_interval
- Supports exact overlap calculation
- cause_evidence
- Distinguishes coincidence from documented causal link
Test another case
Give one fault crossing the hold end and report both overlapping and nonoverlapping portions.
No actual packaging-machine operation, line settings, telemetry credentials or troubleshooting instructions.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.