Production tracking
Easy production tracking and OEE, straight from the machine
Undrd Control works out OEE from what the machine itself reports: when it runs, when it stops and how many parts it makes. Set up each plant's shifts once, and every machine, shift, day and week gets its availability, performance and quality without anyone filling in a sheet. Across every plant, the connected CNC machines and inspection cameras report to the same screen.
OEE needs a controller that reports its run state and a parts counter, so that is the first thing we check on yours. A machine without them is still monitored, and the OEE view says why it has no figure.
OEE per machine, shift, day and week
Availability, performance and quality are calculated against the plant's own calendar, so a break or a holiday is not counted as a loss. The figures add up over any slice of time: one machine on one shift, or a whole plant over a month.
- A weekly shift pattern per plant, with breaks, a time zone and exceptions for holidays or extra shifts
- Performance against an ideal cycle time per program, set by a manager or learned from the machine's own shortest uninterrupted cycles
- Quality from the inspection cameras linked to the machine; without one it is shown as assumed, never filled in silently
- An OEE target per plant, and an alert by email or push notification when a shift ends below it
Every stop, with a reason
A gap in production longer than the plant's stop threshold, inside planned time, becomes a stop that asks for a reason. Operators classify the stops of their current and previous shift from the machine's page, managers can review any of them, and the reasons are your organisation's own.
- A reason tree per organisation, with sub-reasons, planned and unplanned stops
- A stop marked as outside planned hours leaves planned time, so it does not count as a loss
- An alert when a machine has been stopped for 30 minutes with no reason given, by default
- Downtime ranked by reason, and the six big losses, per machine, plant or period
Tracking across the factory floor
Every connected CNC machine and inspection camera, in every plant, reports to one dashboard. Machine state, pass rate and alerts roll up from machine to plant to fleet, and each person sees the plants they are responsible for.
- Parts counted by the controller's own counter where it reports one, not typed in
- Pass rate and defect breakdown from the inspection cameras, per device and per plant
- Machines, plants and organisations scoped by role, from operator to senior manager
- English and Portuguese throughout
Questions
What people ask about this
What does a machine need for OEE?
A controller that reports its run state and a parts counter; whether yours does is the first thing we check. A connection with a run state but no parts counter gets availability only. Other machines are still monitored, and the OEE view names what is missing.
Where does the ideal cycle time come from?
A manager can set one per program. Until then, Undrd Control learns it from the machine: the shortest part-to-part times of the last 90 days, once it has seen enough uninterrupted cycles. Without either, performance is left out rather than guessed.
Does a plant need a shift calendar?
No, but OEE is more useful with one. A plant with no shift pattern is treated as running around the clock, and one with no time zone as UTC, and the dashboard says so on screen instead of applying it silently.
Track production on your own machines
Tell us which controllers you run and we will tell you which of them can report OEE today.