OEE+ and the Owner column
OEE+ is Augos's extension of standard OEE. It keeps the standard loss breakdown, OEE factor, loss category and cause, exactly as the standard defines it, and adds one column standard OEE never had: who each lost minute sits with. The owner follows the time account, not the stop reason: planning for the time it allocated, the operator logged in, or the technician who accepted the call. Standard OEE shows the loss. OEE+ shows who owns it.
What OEE+ is
Standard OEE multiplies Availability, Performance and Quality into one score, then sorts the lost time into loss categories and stop reasons. That tells a plant how much time it lost and roughly to what. It does not say whose problem the loss is, or how much of it could be won back. OEE+ answers both. The arithmetic is unchanged, so an OEE+ score of 65% means exactly what a standard OEE of 65% means. The addition is a fourth column in the loss breakdown: for every lost minute, who it sits with, set by the time account it falls in. The root of a stop is found in the reason tree, from the reason to the machine, assembly, component and part, down to the event log. How to calculate OEE sets out the standard arithmetic; this page is about the column.
Source: Augos Factory method, Glossary: OEE+
What the split adds
OEE+ splits a loss in three ways without changing the score: across, by factor, category and cause; by owner, who the time sits with; and inside, where one stop is separated into parts that different people control. Standard OEE shows the total. OEE+ shows its parts.
Across, the standard loss breakdown is kept exactly as the standard defines it, and the owner is the added column. Inside a planned stop, the allocated time is owned by Planning and the overrun by the Operator (Planning Efficiency Loss and Operator Compliance). Inside a stop, Augos Assist, an optional extra, times the response in stages (Stoppage Response Stages). Attributing losses to people is one result of this split. The other is a more granular reading of the same data.
Source: Augos Factory method, this page and the two linked pages
The six big losses
The six big losses are the classic map of where OEE goes. Two sit under each factor.
| Factor | Loss | What it looks like on the floor |
|---|---|---|
| Availability | Breakdowns | The line is down and nobody planned it. |
| Availability | Setup and adjustment | Changeovers, cleaning and planned maintenance, and the time they overrun. |
| Performance | Small stops and idling | The line halts for seconds, restarts, halts again. Too short to log by hand. Augos counts these as interruptions (what standard OEE calls minor stops or micro-stops). |
| Performance | Reduced speed | The line runs, but below its ideal rate. |
| Quality | Process defects | Scrap and rework during steady running. |
| Quality | Reduced yield | Start-up rejects while the process settles after a stop. |
Standard OEE stops here. Each loss has a category and, with a good list of stop reasons, a cause. The next step, the one that turns a report into a task list, is to ask who the time sits with and where its root is.
The Owner column
OEE+ adds one column. It is set by the time account a lost minute falls in, not by the stop reason. The setup workbook has no owner field, and no stop reason belongs to a department.
| Time account | Who it sits with | How |
|---|---|---|
| Planned stop: the allocated time (Planning Efficiency Loss) | Planning | The standard the plant set for the task. Planning is a bucket, not a person: there is no planning module and no planner is named. |
| Planned stop: time over the allocation (Operator Compliance) | The operator logged in | The overrun against the Standard Allowed Time. |
| Unplanned stop: Operator Evaluation and Operator Resolution | The operator logged in | From the stop until the call, and the time spent clearing it alone. |
| Unplanned stop: Technician Response, Active Wrench, Inactive Wrench | The technician who accepted the call | Needs Augos Assist. Without it the whole stop sits with the operator logged in. |
| Interruptions | Their own account, traceable to the operator logged in and the product | Counted by the sensor below the stop threshold; no reason and no response stage. |
| Speed loss and quality loss | Reported, not assigned | By job and product, against the rated speed and the good count. |
A changeover's allocated time sits with planning because the plant chose the standard; the minutes it runs over sit with the operator who ran it (Planning Efficiency Loss and Operator Compliance). A breakdown's response and repair sit with the technician who accepted the call, and the evaluation and any clearing before the call with the operator (Stoppage Response Stages). A wait for raw material is an unplanned stop with no call, so its time sits with the operator logged in; the reason tree is what shows it was a supply problem, not a floor one.
Source: Augos Factory method; owner rule, Tim Stevens, 19 October 2026; terms as defined in the Glossary
Who the time sits with
The platform measures two kinds of people and keeps one bucket for the plan.
| Who | Recovers the time by |
|---|---|
| The operator logged in | Noticing faster, clearing more stops alone, keeping to the changeover standard, running at pace. |
| The technician who accepted the call | Arriving faster, repairing faster, fixing recurring faults for good. Needs Augos Assist. |
| Planning, as a bucket | Scheduling fewer or shorter planned stops, and tightening allocated times the line already beats. |
A department is the roll-up of the people measured: operators to production, technicians to the technical team. Quality, supply and planning problems are found in the reason tree, by drilling from the reason to the machine, assembly, component and part and down to the event log, not by an owner field. Recoverable hours are worked out for the individual, the event, the job and the product, against the line's own best.
Stops nobody has classified yet sit in Pending Inputs, ranked by hours, so the time that still needs a reason stays visible.
A real month, by account
The table below is one anonymised beverage packaging line over one month in 2026, 711.2 paid hours once the 8.8 hours of stops still pending classification (45 events) are excluded, as the Augos platform recorded it. Site, line, products and people are removed; the hours are as measured.
| Loss | Hours | Share of paid time | Account, and who it sits with |
|---|---|---|---|
| Waiting for raw material (5 stops) | 97.8 | 13.8% | Unplanned; the operator logged in, no call |
| Other waits: water, quality, blending, procurement (13 stops) | 4.1 | 0.6% | Unplanned; the operator logged in |
| Breakdowns (417 stops) | 99.2 | 13.9% | Unplanned; the technician who accepted, with Augos Assist, else the operator |
| Planned maintenance logged as unplanned (4 stops) | 4.2 | 0.6% | Unplanned; the technician who accepted |
| Cleaning (36 planned stops) | 78.8 | 11.1% | Planned; planning (allocated) · the operator logged in (overrun) |
| Interruptions (13,260) | 54.6 | 7.7% | Interruptions; their own account, traceable to operator and product |
| Speed loss (net of 0.4 h gain) | 23.2 | 3.3% | Speed; reported by job and product |
| Quality stops and checks | 22.9 | 3.2% | Unplanned; the operator logged in |
| Changeovers (26) | 14.0 | 2.0% | Planned; planning (allocated) · the operator logged in (overrun) |
| People (meetings, breaks over) | 9.3 | 1.3% | Planned; planning (allocated) · the operator logged in (overrun) |
| Quality loss (rejects, as time) | 4.2 | 0.6% | Quality; reported by job and product |
| Net production time | 299.0 | 42.0% |
Read as standard OEE, this line lost 58.0% of its paid time and Availability was the problem. Read by account, two blocks of almost identical size appear with opposite fixes: 98 hours lost to five raw-material waits, which the reason tree shows as a supply problem that will not be solved on the floor; and 99 hours lost to 417 breakdowns averaging fourteen minutes, which sit with the technicians who answered the calls and the operators who cleared most of them. The 55 hours of interruptions, one every minute and a half of running time, are an account of their own, traceable to the operator and product, and were invisible before a sensor counted them. Those are three different conversations, and the account and the reason tree are what start the right one.
Source: Augos platform, Performance Overview and Downtime Report, one anonymised beverage line, a 30-day month in 2026
What changes on Monday
A morning meeting run on standard OEE reports a percentage and a list of reasons, and the room argues about whose fault it was. A meeting run on OEE+ opens the loss breakdown by account: planning sees the hours it allocated, the maintenance lead sees the breakdown hours and each technician's response and repair time, the supervisor sees the overruns, the evaluation and resolution times and the interruptions by operator, and the reason tree shows which waits came from supply. Each leaves with their own number and their own benchmark, the line's own best, so the question is no longer who to blame but how much of yesterday's loss each function can recover this week.
What Augos Assist adds
Standard OEE, the loss breakdown (factor, category, cause) and owner attribution are in the standard fee. Augos Assist, an optional extra, adds the Stoppage Response Stages behind the attribution: operator evaluation and resolution, technician response and wrench time. Without Assist, attribution has no technician owner and the full resolution of a stop sits with the operator.
Source: Augos Factory method, Glossary: one offer
Common questions
Is OEE+ a different formula from OEE?
No. Availability, Performance and Quality are calculated exactly as standard OEE defines them, so the score is comparable with any other plant's. OEE+ adds a column to the loss breakdown, the owner, and does not change the arithmetic.
What are the six big losses?
Breakdowns and setup/adjustment under Availability; small stops and reduced speed under Performance; process defects and reduced yield under Quality. They are the classic map of where OEE goes. OEE+ says who each one's time sits with.
Who does a lost minute go to?
Planning, for the time it allocated to a planned stop; the operator logged in, for overruns and for evaluation and resolution time; the technician who accepted the call, for response and repair time, with Augos Assist. Interruptions are an account of their own, traceable to the operator logged in and the product. The time account decides, not the stop reason, and no stop reason belongs to a department.
Why is "wait for technician" shared?
Because the operator decides when to call and the technician decides how fast to arrive. Neither can shorten the wait alone, so it is timed as its own stage and owned by both.
Does owner attribution blame operators?
It measures what each function controls and benchmarks it against the line's own best, using medians so one bad shift does not define anyone. On the line above the operator-owned losses were roughly a quarter of the total; the rest sat with planning, suppliers and maintenance.