Special-purpose machines · A closer look
A cycle time should tell you where the work went.
Explore SPM cycle visibility through meaningful stage boundaries, waiting, blocked conditions, repeated attempts and the sequence behind a production delay.
The practical question
How do you make an SPM cycle-time review more informative?
Agree the start, finish and intermediate stages that matter to the question. Keep productive activity, waiting, interruption and repeated attempts distinguishable, using the definitions and timing that the equipment actually provides. Then compare equivalent work rather than treating every recorded cycle as the same operation.
Two machine cycles can have the same duration and very different stories. One may spend more time doing the intended work; another may wait for a condition or repeat a stage. A sequence review needs those differences to remain visible without overwhelming the people using it.
Define the start and finish before measuring
Ask the machine owner to identify what begins and ends the recorded cycle. The start may describe a request, the acceptance of a request or the beginning of a physical operation. A later completion event may refer to the machine, the station or a handoff. Write the definition alongside the metric.
Keep the event source and its time basis clear. If records come from several devices, ask whether their ordering is dependable enough for the intended review. Do not infer a short delay or its cause from timestamps that cannot resolve it.
Distinguish a state from its explanation
The PackML reference defines different states for executing, holding, suspending and stopping a machine’s work, among others. These distinctions show why a single stopped label can be too broad. A state tells the reviewer where the sequence is; the reason for entering it may need separate information.
Sources: [1]
Keep the part and job in the comparison
The OPC Foundation’s machine-tool model includes machine monitoring and job information as distinct concerns. For a cycle review, preserve which job or operating task the record describes. A duration should not acquire a meaning independent of the work represented by that job.
Sources: [2]
An illustrative situation
Reconstruct one slow cycle together
Hypothetical example: a rotary assembly machine records occasional long cycles. The review separates the available stage events and identifies repeated waiting before a transfer. An operator’s note describes a component-presentation issue, but the existing machine record does not establish the reason for every wait.
The team preserves that distinction. It can review the observed waits, ask the operator to explain a known occurrence and decide what evidence would test the proposed explanation. The comparison stays at the level the record supports, without transforming a plausible account into a confirmed cause.
Present the exception clearly
A useful sequence view should let a colleague locate the unusual stage and return to the underlying record. Explain the baseline used for comparison and whether the work is equivalent. Give a missing event a visible meaning; otherwise an incomplete record may look like an unusually fast cycle.
For a discussion with VIEOX, select one stage-level question that repeatedly consumes engineering or production time. Agree which available events can answer it and which cannot. A focused result might be a clearer separation of waiting from processing, or a shared account of repeated attempts that the next shift can follow.
Put the question to work
A practical checklist
- Define the measured start, finish and stage boundaries.
- Explain the difference between a recorded state and an attributed cause.
- Preserve the identity of equivalent jobs or operating tasks.
- Show repeated attempts, missing events and uncertain ordering.
- Review one known exception with the people closest to the sequence.
Questions, answered
Is the shortest observed cycle always the right reference?
Choose a reference that represents the intended work under understood circumstances. A short record might reflect a different job, an incomplete sequence or missing events. The responsible production and engineering team should agree what makes a comparison fair.
Should an operator note overwrite the machine’s recorded state?
Keep the two records connected and distinguishable. The machine describes the event it recorded; the operator contributes experience and an account of the circumstances. A later review can determine how those observations relate without erasing either source.