Operational problem
Shift production truth arrived late and manually. Cycle time lived in spreadsheets that froze under load. Efficiency numbers could be edited by hand. Supervisors could not see press status during the shift.
Proven Success · Injection · MENA
A short anonymized story: operational pain, what shipped on the floor, how data was collected, and which outcomes we can actually stand behind — without naming the plant or inventing percentages.
Illustrative sceneProven Success · Injection
Roles only. No plant names, no people. No unverified savings percentages.
Shift production truth arrived late and manually. Cycle time lived in spreadsheets that froze under load. Efficiency numbers could be edited by hand. Supervisors could not see press status during the shift.
Prove live cycle counting on injection presses, tie counts to production activities, close activities with scrap, and build an honest path to OEE = Availability × Performance × Quality — without turning the whole platform into a cycle-time-only product.
What shipped
Open a production activity for the shift
Live cycles from the press signal
Official efficiency only after close
What operators and supervisors saw
Cycles from press signals into local storage and a live dashboard. Official efficiency used closed activities — not editable mid-shift theatre. Live views consumed open activities only.
18.4s
Accepted
19.1s
Accepted
—
Idle
21.8s
Over
Visual of the field-validated dashboard pattern — not a live plant feed, and not an OEE uplift claim.
Counts from press signal to dashboard — official efficiency from closed activities only.
| Edge cycle counting | Live in-shift |
|---|---|
| Context | Counts from press signal to dashboard — official efficiency from closed activities only. |
OEE foundation
What was field-validated is the collection path — not an invented OEE uplift %.
From running / stopped press signals during the shift.
From counted cycles vs standard time — not mid-shift manual edits.
From activity close + scrap — official path after close.
Impact and lessons
← All Proven Success · Production Intelligence · Learn: cycle time
Bring one production line, its current data sources, and a priority loss. We will map the measurement, workflow, and proof of value.