Machine data analysis: run time, setup and downtime per machine
How much of the time do your machines really run, and where does the rest go? The answer sits in confirmations and downtime postings, spread across tables that rarely anyone puts together. Onagero puts them together.
- Runs on your server
- Reads only, never writes
- GDPR ready
- First result in weeks
In short
Onagero evaluates the times that your machines and your ERP already post: run time, setup time, downtime with reason, planned and unplanned breaks. The result is a tool that shows, per machine and week, where the time goes. KPIs such as availability are calculated according to a definition that your production team sets.
How your team describes it
Your experts say what they need in their own words. Onagero finds the right data and builds the tool in a test stage; after your release it runs in operation.
„How much of the time do my machines really run? Break the rest down into setup, downtime with reason and breaks, per machine and week.“Evaluate machine times, as a tool in the browser
What the tool takes over
Three steps done by hand today. The tool your team builds with Onagero then does them itself.
Assembling times
Confirmations, downtime postings and shift calendar together give the time balance of a machine. Gaps in which nothing is posted appear as a row of their own.
Defining KPIs
Availability, setup share, utilization: every KPI has a written definition in the tool, released by your production team.
Making comparable
Machines, weeks and item groups side by side, so that a long setup does not disappear in the monthly average.
Typical situations
This is what the value looks like day to day.
Investment question
Do we need another machine, or is the existing one running too little? The time balance shows how much time goes to setup and waiting.
Setup times
Which item changeovers take the longest? How often is a machine changed over per day? The order sequence thus becomes something that can be checked.
Downtime reasons
Many stoppages fall under “Other”. The tool shows when and where, and the shift can post the missing reasons while it still remembers.
Weekly meeting
Production management sees each machine on one page, with the data as-of date, without anyone building slides.
Which data is needed
- Confirmations with start and end time per operation
- Downtime postings with reason, if available
- Shift calendar and planned breaks
- Machine master data: which machine belongs to which line
Only what your IT releases is read. Names are masked in the development stage. How the data path works
What you end up with
A time balance per machine and week in the browser: running, in setup, stopped with reason, unposted. Plus the fixed definitions of your KPIs and a view of the longest setups of the week.
Start with one problem.
Keep the capability.
No AI transformation. One real process, solved on your data in a few weeks. Your team solves the next one itself.
How your price is formed
After the demo you get a fixed offer. Scope, goal and price are set in writing before it starts.
One real problem, the data sources it needs, your Onagero environment on your server, and the first solution, built with your team and measured against the agreed goal.
- Scope, goal and price in writing before the start
- First running solution in a few weeks
- Your data and results stay exportable at any time
Operating the platform on your server: monitoring, reviewed updates, backup and rehearsed recovery, and maintenance of the connections when systems change.
- Begins only once the start has reached its goal
- Your team builds further solutions itself, in the same environment
- Roles, releases and logs included
What you can rely on
The tool reads, computes and shows. These things it never does, and that is in the contract.
- Onagero does not read signals directly from the controller. It works with what is posted or stored in a released database.
- It does not reschedule orders. Sequence planning stays with your work preparation.
- It does not invent downtime reasons. What is unposted remains visible as unposted.
Questions about Evaluate machine times
Does Onagero calculate OEE?
If your data provides availability, performance and quality, yes. We define it together with you, because OEE is calculated slightly differently in every plant. An honest time balance is often more useful than a single percentage figure.
Do we need a machine connection?
No. If one exists and stores to a database, we use it. Otherwise the confirmations from the ERP or BDE are enough.
What about machines without confirmations?
They are missing from the evaluation, and the tool says so. We advise against estimating missing times.
How does the tool distinguish planned and unplanned downtime?
Through your shift calendar and the downtime reasons. Anything that cannot be assigned appears as unposted, not as planned.
Can the tool create maintenance orders?
No. It shows anomalies. Your people create orders in the system intended for that.
Who may see the evaluation?
You define that through roles. Evaluations that allow conclusions about individual persons should be agreed beforehand with the works council.
A direct line
Write two sentences about Evaluate machine times. You get an answer from a person who builds the tool themselves.
Prefer something structured? The fit check asks seven questions and tells you right away whether a pilot fits.
Which problem would
your team solve first?
Show us a real process. We will show you how it could look with Onagero.
Book a demo →