The Maintenance Manager: Meet Mike
Mike is a Maintenance Manager at a mid-sized discrete manufacturer producing automotive components.
His facility runs three production shifts across 14 production cells — stamping, robotic welding, machining, and final assembly.
He manages a team of six technicians.
His performance is measured against three metrics: unplanned downtime frequency, PM compliance rate, and the plant's weekly OEE score.
He has been in this role for four years.
He is good at his job.
He spends a significant portion of every day managing information gaps rather than managing maintenance.
That is what this article is about.
6:00 AM — The Shift Handover
Before: Starting Blind
Mike arrives at the facility at 6:00 AM.
The night shift maintenance technician has left a handover note on the supervisor's desk.
It reads: "Line 7 had issues around 3 AM. Fixed it. Also the hydraulic press on Cell 4 is making a noise. Might want to check it."
Mike reads it.
He does not know what "issues" on Line 7 means.
He does not know whether the fix was a proper corrective repair or a temporary workaround.
He does not know how long the line was down.
He does not know what parts were used.
He does not know whether the hydraulic press noise started at the beginning of the shift or developed during it.
He sends a WhatsApp message to the night shift technician asking for more detail.
He waits.
He starts his morning with incomplete information about the condition of his production floor.
After: Starting With Context
Mike opens Fabrico on his phone before he reaches the car park.
The shift handover dashboard shows him everything the night shift captured.
Line 7 experienced an unplanned stop at 02:47 — a film drive motor alarm, classified as an electrical fault.
The corrective work order shows it was resolved at 03:31.
Total downtime: 44 minutes.
The technician logged the corrective action — replaced the motor start capacitor, part number confirmed, stock level updated.
The hydraulic press on Cell 4 generated three micro-stop events between 04:10 and 05:45 — each lasting between 90 seconds and four minutes.
The OEE system classified these as Minor Stoppages in the Six Big Losses framework.
The performance trend on Cell 4 shows the press has been running at 94% of target cycle time for the last six shifts.
A condition-based alert was generated at 05:50 — recommending a hydraulic system inspection based on the performance degradation pattern.
The work order is already in the queue.
Mike's day starts with a complete picture of his floor's overnight condition.
He knows what happened, what was done about it, and what still needs attention.
He has not sent a single message.
7:15 AM — The Production Meeting
Before: The Defensive Update
The 7:15 AM production meeting involves Mike, the production manager, and the plant manager.
The production manager opens with the weekly OEE report — which shows the facility at 67% OEE against a 75% target.
The production manager attributes 8 points of loss to maintenance-related downtime.
Mike disagrees.
Three of those downtime events were caused by a material supply interruption — not an equipment failure.
One was a planned maintenance window that the production schedule did not account for.
He knows this because he was there.
But he cannot prove it in the meeting because his maintenance records are in a CMMS that does not talk to the OEE system.
The meeting ends with an action item for Mike to produce a detailed downtime attribution report by end of week.
That report will take three hours to produce manually from two separate systems.
After: The Data-Backed Update
The 7:15 AM production meeting begins with the plant manager pulling up the Fabrico dashboard on the meeting room screen.
OEE for the week: 67% against a 75% target.
The Six Big Losses breakdown shows the loss categories automatically.
Unplanned downtime: 4.2% — of which 1.8% is attributable to equipment failures and 2.4% is attributable to material supply interruptions logged by operators at the point of occurrence.
Planned maintenance: 1.1% — including the PM window that ran 23 minutes over schedule on Wednesday because the replacement bearing was a non-standard size.
Setup and Adjustment losses: 3.7% — primarily from the format changeover on Cell 9 that took 47 minutes against a 28-minute target.
The attribution is clear, structured, and agreed upon before the meeting starts.
The discussion moves immediately to what to do about each loss category rather than arguing about what caused them.
Mike does not need to produce a manual report.
The data is already there.
8:30 AM — The Unplanned Breakdown
Before: The Reactive Scramble
At 8:30 AM, the production supervisor calls Mike.
The rotary filling machine on Line 3 has stopped.
Mike walks to Line 3.
The machine is displaying an alarm code he does not immediately recognise.
He asks the operator what happened.
The operator says it started slowing down about 20 minutes ago and then stopped.
Mike tries to recall whether this machine has had a similar fault before.
He thinks it might have — about eight months ago — but he cannot remember what caused it or how it was fixed.
He goes back to his office to search the CMMS for historical records.
He finds two work orders that might be relevant.
One has a meaningful failure code. One says "repaired" with no further detail.
He calls his most experienced technician, explains the situation over the phone, and asks him to come to Line 3.
The technician arrives 18 minutes after the initial call — with general tools but not the specific components that the fault is most likely to require.
Diagnosis takes another 25 minutes because the failure history is incomplete.
The technician needs to go to the storeroom for parts.
The part is in stock — but in a different location from where the inventory system says it should be.
Total time from fault to machine restarting: 87 minutes.
After: The Structured Response
At 8:30 AM, Fabrico detects the rotary filling machine on Line 3 slowing below its target cycle rate.
At 8:31 AM, the machine stops and generates an alarm code.
Fabrico automatically creates a priority work order — classified as an unplanned corrective, linked to the asset's complete maintenance history, pre-populated with the three most common causes of this specific alarm code on this machine type.
The work order reaches Mike's technician's mobile phone at 8:31 AM.
It shows the alarm code, its most likely causes, the machine's last five work orders for context, and the parts list for the most probable repair.
It shows that the specific bearing assembly most commonly associated with this fault is in stock — location Bay C, Shelf 4.
The technician is at the storeroom at 8:34 AM.
He is at the machine at 8:39 AM — nine minutes after the fault occurred, with the right part and the right information.
Diagnosis confirms the bearing assembly.
Total time from fault to machine restarting: 34 minutes.
53 minutes recovered compared to the "before" scenario.
On a line generating $380 per hour in production value, that 53 minutes represents $335 in recovered output from a single incident.
Across 40 incidents per month, the MTTR improvement alone generates over $13,000 per month in recoverable production value.
10:45 AM — The Spare Parts Hunt
Before: The Storeroom Lottery
Mike receives a call from a technician working on a planned PM on the hydraulic press in Cell 4.
The PM checklist requires replacing the hydraulic filter.
The technician cannot find the filter in the storeroom.
The inventory system shows 3 in stock.
After 20 minutes of searching, the technician finds two filters in a different location from where the system says they should be.
They are a different specification from what the PM requires.
Mike calls the maintenance coordinator to raise an emergency purchase order.
The coordinator is in a meeting.
Mike emails the purchase request.
The PM is put on hold while they wait for the part.
The planned maintenance window expires.
The PM is rescheduled.
The hydraulic press returns to production with the filter not replaced.
After: The Pre-Staged Repair
The PM work order for Cell 4's hydraulic press was generated three days ago — because the press crossed its run-hour threshold for scheduled maintenance.
When the work order was generated, Fabrico automatically checked the spare parts required against current inventory levels.
The hydraulic filter required for this PM was at its minimum stock level.
An automatic replenishment alert was sent to the purchasing coordinator three days ago.
The filter was ordered and received yesterday.
It is in the storeroom at the correct location, clearly labeled with the asset it belongs to.
The technician completes the PM in the scheduled window.
The work order is closed at the machine from the mobile app.
The inventory record updates automatically — parts consumed, remaining stock level adjusted, next reorder threshold evaluated.
The PM compliance record is complete.
No phone calls.
No hunting.
No deferred maintenance.
1:00 PM — The Management Report Request
Before: The Two-Hour Spreadsheet
At 1:00 PM, Mike receives an email from the plant manager.
The operations director is visiting next week and wants a summary of maintenance performance for Q3 — MTTR trend, PM compliance rate, top 5 assets by downtime frequency, and maintenance cost per production unit.
Mike opens his CMMS.
He can pull PM compliance and work order counts.
He cannot pull MTTR accurately because the "time to repair" field is inconsistently filled out.
He cannot pull maintenance cost per unit because cost data is in the CMMS and production output is in a separate OEE system.
He exports two spreadsheets.
He spends 90 minutes cross-referencing them, building a pivot table, and producing a formatted summary.
The data is for Q3.
It is now mid-Q4.
The report describes a production reality that is three months old.
After: The Real-Time Dashboard
At 1:00 PM, Mike receives the same email.
He opens Fabrico on his laptop.
He navigates to the Analytics dashboard and sets the date range to Q3.
MTTR by asset class: automatically calculated from work order open and close timestamps.
PM compliance rate by site and by team: automatically aggregated from completed work orders.
Top assets by unplanned downtime frequency: automatically ranked from the Six Big Losses categorization.
Maintenance cost per production unit: automatically calculated because maintenance cost data and production output data exist in the same platform.
He exports the dashboard as a PDF.
Total time: four minutes.
He sends the report to the plant manager with a note flagging the three specific trends that warrant discussion during the operations director's visit.
He has time to think about what the data means rather than time to produce the data.
3:30 PM — The Compliance Question
Before: The Document Search
At 3:30 PM, the quality manager stops by Mike's office.
A customer audit is scheduled for next Thursday.
The customer requires documentation that the injection molding press on Line 9 has been maintained according to the documented PM program for the last 12 months — specifically that calibration checks were completed, that the correct consumables were used, and that a qualified technician signed off on each maintenance event.
Mike goes to the CMMS.
He finds 14 PM work orders for Line 9's press over the last 12 months.
Three are missing technician sign-off.
Two have incomplete parts records — the consumables field is blank.
One was completed four days outside the scheduled window with no documentation of why.
Mike spends two hours reconstructing the missing records from paper logbooks, technician recollection, and cross-referencing with purchasing records for parts evidence.
He produces a documentation package that is complete on paper but has visible gaps in digital integrity.
He is not confident it will satisfy a thorough customer audit.
After: The On-Demand Audit Report
At 3:30 PM, the quality manager sends Mike the same request.
Mike navigates to the Asset record for Line 9's injection molding press in Fabrico.
He selects "Compliance Report" and sets the date range to the last 12 months.
The report generates in 11 seconds.
It shows every PM work order — date completed, technician name, parts consumed with batch numbers, SOP version followed, digital sign-off timestamp.
Every work order has a complete record because the mobile app made completion easier than leaving fields blank.
Every technician sign-off is a timestamped digital signature captured at the machine.
Every parts record is automatically populated from the inventory management module when the technician scanned the parts out of the storeroom.
Mike sends the report to the quality manager.
The documentation package is complete, consistent, and digitally unalterable.
No reconstruction required.
5:15 PM — Planning Tomorrow
Before: The Calendar Guessing Game
At 5:15 PM, Mike sits down to plan tomorrow's maintenance schedule.
He has three PMs due this week — one that was already deferred from last week because of the spare parts issue.
He does not know which production cells are scheduled for which jobs tomorrow.
The production schedule is managed in a separate system by the production planning team.
He sends a message to the production planner asking which lines will be running light tomorrow morning — so he can schedule the deferred PM without creating a production conflict.
The planner responds at 5:45 PM.
Line 7 is available for three hours from 7:00 AM.
Mike schedules the PM for 7:00 AM and assigns it to his most experienced technician.
He does not know whether that technician has other work orders already scheduled for the morning.
He will find out tomorrow.
After: The Integrated Schedule
At 5:15 PM, Mike opens Fabrico's planning board.
He can see tomorrow's production schedule alongside the maintenance schedule in a single view.
Line 7 has a production run starting at 10:00 AM.
The 3-hour window from 7:00 AM to 10:00 AM is available — and the planning board shows this window as available for maintenance scheduling.
Mike drags the deferred PM onto the Line 7 timeline at 7:00 AM.
The system confirms the window is conflict-free.
It shows him which of his technicians have available capacity tomorrow morning.
It shows him that the required parts for the PM are in stock at the correct location.
He assigns the work order to his available technician.
The technician receives a notification on their mobile phone at 5:16 PM — with the work order details, the asset history, the required parts list, and the location of those parts in the storeroom.
Tomorrow morning's PM will start on time, with the right technician, the right parts, and the right information.
Mike leaves the facility at 5:30 PM.
He will not receive a call about a parts shortage at 7:15 AM.
He knows this because the platform already checked.
The Numbers: What One Day of Difference Adds Up To
The scenarios above are not edge cases.
They are the routine operational differences between a maintenance manager operating with disconnected tools and one operating with a unified OEE and CMMS platform.
Run the numbers across a year.
MTTR reduction on the filling machine fault:
53 minutes recovered per incident.
At an estimated 40 similar incidents per year across the facility.
At $380 per production hour.
Annual value: $13,400.
Eliminated manual reporting time:
Approximately 3 hours per week of manual report production replaced by on-demand dashboard export.
At a maintenance manager's fully-loaded cost of $45 per hour.
Annual value: $7,020 in recovered management time — redirected toward planning and improvement rather than data assembly.
Deferred PM prevention:
One deferred PM per month — resolved by pre-staging parts automatically rather than discovering the stockout during the maintenance window.
At an estimated $800 per deferred PM event in extended downtime and emergency procurement cost.
Annual value: $9,600.
Shift handover quality:
The 20 minutes Mike spent waiting for WhatsApp clarification at 6:00 AM, multiplied by 250 working days per year.
At his fully-loaded cost of $45 per hour.
Annual value: $3,750 in recovered management time.
Conservative annual total from one maintenance manager's daily experience: $33,770.
This calculation uses a single facility, a single maintenance manager, and four specific daily scenarios.
It does not include OEE improvement from condition-based PM preventing the next major failure.
It does not include compliance audit cost avoidance.
It does not include the compounding effect of a cleaner maintenance history enabling better predictive analysis over time.
The numbers from a single operational day, multiplied across a year, make the investment case without requiring a complex financial model.
What Stays the Same
This article has presented a deliberately optimistic "after" scenario — and it is worth being honest about what does not automatically change when a new platform is implemented.
Maintenance problems do not disappear.
Equipment still fails. Wear still accumulates. Operators still cause accidental damage. Supply chain disruptions still create parts shortages.
A platform does not prevent these events.
It changes how quickly and how effectively the maintenance team responds to them — and whether the team has enough advance warning to prevent some of them before they occur.
Adoption requires effort.
The 96% adoption rate that Fabrico achieves within the first month of go-live reflects a structured training and onboarding process — not an assumption that technicians will automatically migrate their behavior.
Role-specific training, clear communication about what the platform does for each individual technician's daily workflow, and management consistency in using the platform's data rather than requesting parallel manual reports — all of these are necessary for the "after" scenario in this article to materialize.
Data quality improves over time — not immediately.
The condition-based PM triggers and predictive analysis capabilities in the "after" scenarios are more powerful after 6-12 months of clean machine-connected data than they are in week one.
The platform generates value from day one — but it generates more value as the historical dataset grows.
Frequently Asked Questions
Is the "before" scenario in this article representative of most manufacturing facilities?
The scenarios described reflect the operational reality of mid-sized manufacturing facilities running disconnected maintenance and OEE systems — which represents the majority of mid-market manufacturers globally.
Specific details will vary — the exact platforms, the specific assets, the precise failure modes — but the structural problems are consistent: incomplete shift handovers, reactive fault response with delayed dispatch, spare parts uncertainty at the maintenance window, manual cross-system reporting, and compliance documentation gaps.
Does Fabrico replace the need for a dedicated OEE monitoring tool alongside it?
Yes. Fabrico's native OEE monitoring — Availability, Performance, and Quality tracked in real time from machine signals, aligned with the Six Big Losses framework — eliminates the need for a separate OEE platform.
The production meeting scenario in this article, where OEE data and maintenance data are in the same environment, is only achievable when both capabilities exist on the same platform rather than requiring integration between separate systems.
How quickly does the "after" scenario materialize after implementation?
The shift handover improvement and mobile work order dispatch improvements are visible from day one of go-live.
MTTR reduction from faster dispatch and better information at the machine is typically measurable within the first 30 days.
Condition-based PM trigger value — where the platform begins preventing failures rather than just responding to them faster — develops as the historical dataset builds over the first 3-6 months.
What does the maintenance manager's role look like after implementation?
Less reactive coordination. More proactive analysis.
The time recovered from manual reporting, shift handover reconstruction, and parts hunting is redirected toward the reliability improvement work that most maintenance managers were hired to do but rarely have capacity for — Bad Actor asset analysis, PM schedule optimization, and continuous improvement initiatives.
Can a small maintenance team realistically implement and manage a unified OEE and CMMS platform?
Yes. The implementation is supported by a dedicated automation engineer and account manager throughout the deployment — so the internal team's time investment during implementation is structured and bounded rather than open-ended.
The ongoing management of the platform — work order assignment, PM schedule management, reporting — is less time-intensive than the manual processes it replaces, rather than more.
The scenarios in this article are based on operational patterns observed across manufacturing environments. If your daily experience as a maintenance manager resembles the "before" scenarios more than the "after" scenarios, a 30-day pilot on a representative selection of your assets will produce measurable before-and-after data from your own facility — before any full investment is required.
Login
Blog
