On an SPM, the cycle is set by the slowest station.

Machine-level timing says the machine got slower. Station-level timing says which station did — usually the difference between a week of investigation and an afternoon.

A special-purpose machine is, by definition, unlike any other machine on the floor, which makes generic monitoring assumptions unusually likely to be wrong. What an SPM does have is a PLC that already knows a great deal — cycle state, station status, counts, faults — because it had to in order to run the machine at all.

Monitoring an SPM is therefore rarely an acquisition problem. It is an agreement problem: deciding which of the PLC's existing signals represent the things you want to measure.

Station-level versus machine-level

MACHINE VIEWCycle runningThe SPM reports a cycle. Useful, and it hides where the time inside the cycle went.
STATION VIEWPer-station timingWhich station takes longest, and whether that changes over a shift.
THE FINDOne slow stationOn a multi-station SPM, cycle time is set by the slowest station. Everything else waits.
THE FIXBalance or interveneA station-level view turns a vague 'the SPM is slow' into a specific, addressable finding.

This is the single highest-value configuration decision on an SPM. Machine-level cycle timing tells you the machine got slower; station-level timing tells you which station did, which is usually the difference between a week of investigation and an afternoon.

What to agree during commissioning

AGREE

What one cycle produces

Multi-station and multi-cavity SPMs frequently produce several components per cycle. Establish this before any count is reported.

AGREE

Which faults stop production

An SPM annunciates many conditions. Only some stop output, and treating all of them equally makes the Pareto meaningless.

AGREE

Station boundaries

Where one station's time ends and the next begins, as the PLC sees it — not as the mechanical layout suggests.

AGREE

Idle versus starved

An SPM waiting for input material is a supply problem, not a machine problem. Distinguish them or the wrong team gets the action.

What the PLC gives you

Almost everything you need, usually. Cycle running, station states, counters and fault bits are typically already in the program because the machine needs them. Acquisition is configured by the MachineWise engineering team, read-only, with nothing written to the PLC.

The work is mapping — deciding which tag means what, with its data type, scaling and edge behaviour recorded — and it is a conversation involving your maintenance team, your production team and ours. On a bespoke machine there is no shortcut and no library to look it up in, which is why the method matters. It is set out in PLC signal mapping for machine monitoring.

Connect your machines today

Two special-purpose machines on a live dashboard this week.

Bring the SPM whose cycle time everyone argues about. Station-level timing usually ends the argument within a fortnight.

Book a free 2-machine pilot WhatsApp us
Questions

Straight answers.

How are special-purpose machines monitored?
Through the PLC that already runs them. Cycle state, station status, counters and fault bits are usually already in the program, so the work is mapping rather than acquisition.
Why measure at station level?
Because on a multi-station SPM the cycle time is set by the slowest station and everything else waits. Machine-level timing tells you the machine got slower; station-level tells you which station did.
How many parts does one SPM cycle produce?
It varies, and multi-station or multi-cavity machines frequently produce several. This must be established before any count is reported, or output will be wrong by a consistent multiplier.
Should every fault be treated as downtime?
No. An SPM annunciates many conditions and only some stop production. Treating them all equally makes the Pareto meaningless.
How do we tell an idle SPM from a starved one?
By mapping them as different states. A machine waiting for input material is a supply problem, not a machine problem, and conflating them sends the action to the wrong team.
Is there a shortcut for mapping a bespoke machine?
No. The tags exist only in your program and there is no library to look them up in, which is exactly why the mapping method and its documentation matter.
FREE 2-MACHINE PILOT
Live OEE on two of your machines — this week. ₹0 to start.
Software-first setup in under an hour each · your data stays on-premises · plant-specific ROI model included.