Feature updates
Latest update
Productivity per worker hour
November
2026
Staffing in your analysis
As an optional feature, oee.ai now brings staffing into your analysis. The number of people on the line comes from the production order as a stored value or is entered on the tablet. oee.ai calculates worker hours from it and relates them to the quantity produced. This adds a whole new area of analysis, and we'd love to tell you more!
Notified even without a loss reason
A new notification type now reports when a loss exceeds a set duration and is still unanswered. Shift leads learn about a long downtime or speed loss even if nobody at the line has entered a reason yet. While the loss is still running, the right reason can be clarified and a comment can add more context.
Security & refinements
In September, we again successfully passed the external audit for our ISO 27001 re-certification, and we're proud of it. Our approach to data security remains independently confirmed.
Past feature updates
We are also constantly improving.
Calculate with your own formula, directly in oee.ai
October
2026
Define a metric, track it live
A new widget calculates with a formula of your own. You combine existing values into a metric that oee.ai doesn't calculate out of the box. One example is technical availability: it counts only technical downtime and leaves out organisational causes such as missing material. The widget works in reports and on the Andon Board, so the figure is visible in real time on the line and in meetings.
Fix typos right away
After a manual unit entry, the tablet shows a card like the one you know from reject entries. For five minutes you can use it to correct or undo the value; after that, the card disappears. A mistyped digit no longer stays in your figures for good.
Clear which loss is meant
When the tablet asks for a loss reason, it now shows whether the loss is still ongoing or has already ended. For an ended loss, the end time is shown as well. Operators on the line can see which loss event still needs an answer.
One event, several reasons
September
2026
Split a loss event afterwards
A standstill can have several causes in a row: cleaning, then a break, then changeover, until production starts again. Without a switch along the way, the whole period carries just one reason. You can now split such a loss event directly in the interface, into as many sections as it needs, each with its own loss reason and comment. The total duration stays the same and reports follow automatically.
No typos in your figures
You can now set an upper limit for manual unit and reject entries. Anything above it is not saved and the operator gets a clear message on the tablet. One digit too many no longer distorts your figures.
Short stops no longer slip through
The widgets “Current loss” and “Current machine status” now also show microstops. Before, they reported no standstill as long as the threshold for an availability loss had not been reached.
Faster input, freer analysis
August
2026
Set a loss reason without the wait
You can now preselect a loss reason in the tablet attributes. Operators assign the reason right away instead of waiting out the minimum loss detection time. That way the reason is recorded while the cause is still fresh.
Expert mode in the table widget
The table widget now has an expert mode for partitioning. In it, partitions can be configured freely, including combinations that were not available before. If you need a view the predefined combinations cannot produce, you can build it yourself instead of taking the detour through an export.
Stability & maintenance
The tablet interface runs on a new version addressing earlier pitfalls in continuous operation. We have also made the API connection more robust.
Shift planning, refined
July
2026
Shift planning without misunderstandings
A small but helpful refinement: shifts that are already running or lie in the past are no longer shown as editable in shift planning. This was never actually possible – the interface now simply makes it clear. Fewer questions, cleaner shift management.
From practice, for practice
This refinement goes back to a hint from a customer – that's exactly how many of our improvements come about. Notice something that could be clearer, faster or simpler?
Let us know, we're listening.