See the Maintenance History Behind Every Asset
Downtime, PM completion, work orders and parts spend, broken out machine by machine, so the maintenance manager can see which asset to look at first.
The report fills in from the work orders, PM checks and downtime your team already records, with no separate maintenance log to keep.
The press everyone calls a problem has its history in four places
Its work orders are in the maintenance log, its PM sign-offs are on check sheets, its downtime is in production's records and its parts are on the stockroom count. The crew knows it's a problem machine, but showing how much downtime it causes, how often its PM slips and what it costs to keep running means pulling those four records together by hand.
So repair, scheduling and investment decisions get made on partial information, and the machine that costs the most can go unnoticed until it fails badly.
From a closed job to the machine's report
Work is logged against the asset
Every work order, PM check and downtime event carries the machine it was for, recorded when the job is done.
Records roll up by machine
For each asset in the facility, 10in6 groups its work orders, PM results, downtime and parts used for the report period.
The report points to what to review first
Downtime and availability history, PM compliance and other trends sit side by side for every machine, so the ones taking the most maintenance attention go to the top of the review list.
A machine's maintenance record on one report
For any asset, the maintenance manager can pull up:
- Downtime and availability history over time
- PM compliance, including checks completed late
- Every work order and the parts spent on it
- Whether it is among the highest-risk machines in the facility
Reading the flagged row
Weld Station B lost 16.8 hours this month, with PM compliance at 55% and seven work orders. Missed PMs and repeat repairs on the same machine usually point to the PM plan before they point to the repair crew.
MTBF and MTTR: two machines, opposite problems
Mean time between failures (MTBF) tells you how often a machine breaks down. Mean time to repair (MTTR) tells you how long it stays down when it does. Two presses, one month, 320 scheduled hours each. Illustrative numbers.
| Machine | Breakdowns | Repair hours | MTBF | MTTR | What it points to |
|---|---|---|---|---|---|
| Press 4 | 8 | 12.0 h | 308 ÷ 8 = 38.5 h | 12 ÷ 8 = 1.5 h | Fails often, fixed quickly. A reliability problem: root cause, PM content, operating conditions |
| Press 7 | 3 | 9.0 h | 311 ÷ 3 = 103.7 h | 9 ÷ 3 = 3.0 h | Fails rarely, slow to fix. A repair problem: response, parts on hand, skills, documentation |
Both presses lost a similar number of hours, so a downtime total ranks them almost the same. MTBF and MTTR show they need opposite fixes. MTBF = operating hours (scheduled minus repair) ÷ breakdowns. MTTR = repair hours ÷ breakdowns.
When MTBF is short
- Open one issue for the repeat failure instead of closing the same work order again and again
- Check whether the PM tasks actually cover the failure mode
- Look at what changed: product, material, speed, operator, season
When MTTR is long
- Split it: time until someone arrived versus time spent fixing (see MTTA)
- Waiting for parts? Set minimum stock levels for that machine's critical spares
- Only one person knows the machine? That's a cross-training gap
Getting numbers you can trust: count only unplanned failures, measure from stop to restart, and use the same definition on every machine. When stops are captured as events with real start and end times, as 10in6 Downtime Tracking does, MTBF and MTTR come from what happened, not from memory.
The bigger problem this solvesHow to reduce unplanned downtime →Recurring failures are where maintenance and production data meet. See how stops are captured, coded and worked down.Each column on the report comes from another module
Maintenance Reporting — FAQ
- How do you calculate MTBF and MTTR?
- MTBF (mean time between failures) is operating time divided by the number of breakdowns. MTTR (mean time to repair) is total repair time divided by the number of breakdowns. For a press with 320 scheduled hours, 8 breakdowns and 12 hours of repair, MTBF is 308 / 8 = 38.5 hours and MTTR is 12 / 8 = 1.5 hours. Count only unplanned failures and measure from stop to restart.
- What is the difference between MTBF and MTTR?
- MTBF measures reliability: how long a machine runs between breakdowns. MTTR measures maintainability: how long it takes to get it running again. A short MTBF calls for root-cause work and better preventive maintenance; a long MTTR calls for faster response, spare parts on hand and better repair knowledge.
- Does someone have to enter data separately to build equipment reports?
- No. Maintenance Reporting draws on the work orders, PM checks, downtime events and parts consumption your team already records in its daily maintenance work. Each machine's record grows as those tools are used.
- What equipment-level data can we see?
- You can see downtime history, PM completion rates, on-time PM performance, work order history and parts usage, each tied back to the specific machine it belongs to.
- Can we see which machines are costing the most to maintain?
- Yes. Work order history, parts usage, and technician time can be tied to individual assets, making it possible to compare maintenance burden across machines and identify which ones are consuming the most resources.
- How does this help with PM compliance?
- Maintenance Reporting shows PM completion rates and on-time performance by equipment. If a specific machine keeps having late or missed PM checks, the pattern shows in the report, and the team can deal with it before it leads to a breakdown.
- Can this support decisions about equipment replacement?
- Yes. With downtime history, maintenance cost, PM compliance and work order frequency side by side for a specific asset, the conversation about repairing or replacing it starts from that machine's record.
- Is this a separate module or does it come with CMMS?
- Maintenance Reporting is part of the CMMS module set. It reports on the work orders, PM checks, downtime and inventory recorded through the other CMMS workflows, so the reports get more complete as each of those modules is adopted.
Set up around how your plant runs
Standardized platforms expect the plant to change to fit the software. Do-it-yourself platforms leave your team to build and maintain everything. With 10in6, we configure the system around your equipment, codes and reports, and your team runs it day to day.
Your equipment, codes and reports
Andon calls routed by call type to the technicians on your crew, following the escalation each shift uses.
Your team runs it day to day
Operators, downtime and scrap codes, products and targets, shift schedules, checks, alerts, emailed reports and real-time boards are managed by your own people. Everyday changes need no support ticket and no invoice.
A project manager for the bigger things
New machines, new modules and custom reports go through a 10in6 project manager who already knows your deployment, so nothing starts from scratch. If you would rather we made everyday changes too, we can.
Still here years later
The system keeps being refined after go-live, and new capabilities are added without rebuilding it. Some of our customer relationships have run for 12 years, and 97% of customers say they would never go back.
“[Our 10in6 project manager] has been great to work with. He is very responsive, quick to help and provides solutions, whether we have random questions, new requirements or the rare times we have system issues.”
How the 10in6 delivery model works →
See which machines are costing you the most attention
Tell us which assets worry you most. We'll work out the downtime history, PM compliance and call volume you'd see for each one.