OEE Summary

in short oee multiplies availability, performance, and quality into one score for how productively your equipment runs mantsu feeds all three factors automatically from registered downtimes, confirmations, and scrap overall equipment effectiveness (oee) is the manufacturing industry standard for measuring how productively a machine or production line is being used an oee score of 100% means you are producing only good parts, as fast as possible, with no unplanned stops oee is not a single number it is the product of three factors, each measuring a different type of loss oee as the product of the availability, performance, and quality factors mantsu captures all the data needed to calculate oee directly from operator interactions on the shop floor the time model to understand oee, it helps to think in terms of time every loss "eats into" the available production time, layer by layer oee time model waterfall from total available time down to fully productive time each row shows how much productive time remains after each layer of loss is removed time block what it represents all time every minute of every day (24/7) planned prod time the time your equipment is scheduled to run (shifts, calendars) run time planned time minus downtime events; the machine was actually running net run time run time minus performance losses; the machine ran at its ideal speed fully productive time net run time minus quality losses; only good parts were produced the goal of oee is to maximise fully productive time availability availability measures how much of your planned production time the equipment was actually running availability = run time / planned production time any event that stops production for a meaningful period counts as an availability loss loss type examples in mantsu unplanned stops machine breakdown, material shortage registered with a dedicated reason code in the downtimes manager & via the order cockpit for the operator planned stops changeover, scheduled maintenance, cleaning scheduling in mantsu, every downtime event has a start time , stop time , and reason code drawn from the configured reason tree this makes it possible to see exactly which stop types are hurting your availability and where to focus improvement 100% availability means no stops occurred during planned production time performance performance measures whether the equipment ran at its maximum theoretical speed during the time it was running the maximum theoretical speed needs to be set correctly in master data & can vary per product, or this factor can exceed 100%, which does not provide a correct total oee performance = net run time / run time or equivalently performance = actual output / theoretical output performance loss captures two subtleties that are easy to miss loss type description in mantsu short stops brief interruptions too short to log as a downtime event automatically captured below the short stop threshold in the downtimes manager reduced speed machine running, but slower than the ideal cycle time derived from confirmed quantities vs the expected rate for the order the order cockpit records confirmations (actual output) against production orders that carry a planned quantity and planned time window the gap between what was produced and what could have been produced at full speed is your performance loss 100% performance means that the process ran at its theoretical maximum speed whenever it was running quality quality measures what fraction of the output was good on the first pass no rework, no scrap quality = good output / total output quality loss is straightforward but costly because you already spent availability and performance time producing parts that cannot be shipped loss type description in mantsu scrap parts that must be discarded entirely registered per order in the order cockpit with a scrap reason code rework / rejects parts that fail inspection and need re processing captured through failed inspection lots in the qm module because scrap is logged with a reason code and linked to a material and order, mantsu gives you the traceability to understand why quality losses occur, not just how many 100% quality means every confirmed part is produced first time right and passed inspection with no scrap and no rework how do you calculate oee? a simple example with real numbers example oee calculation combining the availability, performance, and quality factors even when each individual factor looks reasonable, the combined oee reveals a significant amount of lost capacity world class oee is generally considered to be around 85% most manufacturing operations start between 40% and 60%, which highlights how much untapped capacity typically exists how does mantsu support oee? mantsu does not calculate oee automatically out of the box, but it captures all the raw data needed to do so oee factor data source in mantsu availability downtime events with reason codes (downtimes manager) performance confirmed quantities vs planned quantities per order (order cockpit) quality scrap registrations with reason codes + inspection results (order cockpit + qm) planned time shift and calendar definitions (core shift & calendar management) this data can be exposed through the insights module or via an external reporting layer to calculate and visualize oee per equipment, shift, or time period why does oee matter? oee turns shop floor activity into a single, comparable score more importantly, the three underlying factors tell you where your losses are coming from a low availability score points to your downtimes manager data which reason codes appear most? a low performance score points to short stops and speed losses are operators clearing micro jams that never get logged? a low quality score points to scrap and inspection data which materials or operations produce the most rejects? by connecting oee analysis to the structured, operator captured data in mantsu, you move from a lagging indicator to an actionable improvement loop frequently asked questions what is a good oee score? an oee of around 85% is commonly cited as world class for discrete manufacturing, but the most valuable use of oee is tracking your own trend over time and comparing like with like where does mantsu get the oee data? from normal operator interactions downtime registrations feed availability, confirmations and machine counters feed performance, and scrap registrations feed quality no separate data entry is needed what is the difference between a downtime loss and a performance loss? a downtime loss is a registered stop with a reason code a performance loss is time lost while the machine keeps running, such as reduced speed or short stops below the threshold