At the start of 2023, a 1.2-million-tonne-per-year EAF mini-mill in South Asia was running on a maintenance model that had not changed in a decade: paper work orders collected at the end of each shift, a whiteboard PM schedule in the maintenance supervisor's office, and a spare parts room managed by a storekeeper who knew the inventory from memory but had nothing written down. The plant ran three electric arc furnaces, a ladle metallurgy station, a continuous billet caster, and a high-speed bar rolling mill — 340 assets registered in a spreadsheet that no one had updated in 18 months. Mean time to repair on the EAF electrode column assembly was 6.2 hours. The maintenance manager knew this because he had counted it himself from the shift handover logs. He did not know the MTTR for any other asset class because the data was not captured. What he did know was that in Q4 2022, unplanned stoppages had cost the plant 14 production shifts, and that 9 of those 14 stoppages were on assets that had missed their scheduled PM because the technician had been pulled to an emergency on something else and the paper PM record showed nothing. The decision to implement Oxmaint was not driven by a digital transformation strategy. It was driven by a maintenance manager who could not answer when his general manager asked why the same electrode arm had broken down three times in six weeks. Sign up for Oxmaint to begin your own transformation today.
The Plant: 1.2 Mtpa EAF Mini-Mill — South Asia
What Reactive Paper-Based Maintenance Was Costing the Plant — Before the Numbers Were Counted
The plant's maintenance problems in Q4 2022 were not hidden — they were just not measured. The maintenance manager knew intuitively that the team was spending more time responding to breakdowns than preventing them. What he did not know was the specific pattern, the specific assets, and the specific maintenance failures that were driving each unplanned stoppage. Without a CMMS, this knowledge was impossible to accumulate systematically.
How the 90-Day Oxmaint Deployment Unfolded — Week by Week
The maintenance manager's constraint was clear: the deployment could not disrupt production. There was no window to take assets offline for sensor installation, no IT department to manage infrastructure, and no budget for a multi-year transformation programme. Oxmaint deployed in phases within the production schedule — with the first measurable improvement visible within 30 days. Sign up for Oxmaint to begin your own 90-day deployment.
The Oxmaint implementation team worked with the maintenance manager to audit the asset register — identifying the 72 assets missing from the spreadsheet, verifying specifications for each EAF and associated auxiliary equipment, and configuring the Oxmaint asset hierarchy to match the plant's actual structure. The three EAFs, ladle metallurgy furnace, billet caster, and rolling mill were established as the primary asset groups. PM schedules for the 28 highest-criticality assets were configured first, using the plant's existing interval requirements where documented and industry-standard intervals where not.
All 28 maintenance technicians received a 2-hour Oxmaint mobile training session focused entirely on practical tasks: receiving a work order, completing the steps, recording observations, and closing the work order on mobile. From Day 15, all corrective work orders were created and closed digitally. Within 3 weeks, paper usage had stopped voluntarily. The real-time work order dashboard went live for the maintenance manager and supervisor for the first time — showing every open and completed work order across all 28 technicians. Book a demo to see the real-time dashboard.
In week 6, the Oxmaint PM escalation generated an overdue alert for the EAF-2 electrode arm hydraulic system inspection — the same inspection that had been skipped on paper in the weeks before the three-times-recurring breakdown. The maintenance supervisor received the alert on his mobile phone at 6:15am, assigned the PM to the morning shift technician before the shift started, and the inspection was completed before 9am. The inspection found a developing leak in the hydraulic cylinder seal. The cylinder seal was replaced during a planned 2-hour maintenance window that evening. The breakdown did not occur. The maintenance manager's case for the system was made that morning to the general manager.
With 8 weeks of digital work order history accumulated, the maintenance manager used Oxmaint's MTTR analytics for the first time. The EAF electrode column repair time data showed a clear pattern: the 6.2-hour average MTTR was driven by a consistent 2.5-hour delay between the breakdown alarm and the first technician arrival — because the on-call technician, working from a paper schedule, was not reliably reachable. Oxmaint's mobile dispatch sent the breakdown work order directly to the correct technician's phone the moment the work order was created. Average technician response time dropped from 2.5 hours to 18 minutes. Sign up for Oxmaint to activate mobile dispatch.
In month 4, the spare parts inventory was configured in Oxmaint — linking each part to the assets that consumed it and setting reorder points from the previous year's consumption data. The first auto-generated reorder alert in week 18 prevented an electrode tip stockout. In month 6, PM schedules extended to all 412 assets. By Q4 2023 — the 12-month measurement milestone — the plant recorded 3 unplanned production shift losses versus 14 in the same quarter the previous year. Payback on the Oxmaint deployment cost was achieved in month 4, from downtime reduction alone. Book a demo to begin your own deployment.
Every Metric That Changed — Q4 2022 vs Q4 2023
The improvement across all performance metrics stems from three operational changes: mobile dispatch eliminates technician response delay; PM escalation prevents missed inspections; and digital work order history makes recurring failure patterns visible. Sign up for Oxmaint to start building your measurable maintenance record.
| Performance Metric | Q4 2022 Baseline | Q4 2023 Result | Improvement |
|---|---|---|---|
| EAF electrode column MTTR | 6.2 hours average | 3.7 hours average | ↓ 40% |
| Technician response time (breakdown) | 2.5 hours average | 18 minutes average | ↓ 88% |
| Unplanned production shift losses | 14 per quarter | 3 per quarter | ↓ 79% |
| PM completion rate | ~51% (estimated, unverifiable) | 88% (tracked and confirmed) | +37 percentage points |
| Critical spare parts stockouts | 3 in previous 6 months | 0 in Q3–Q4 2023 | 100% eliminated |
| Work order close-out time | End of shift (4–12 hrs after work) | At point of completion (minutes) | Real-time record |
| Asset register completeness | 340 assets (72 missing) | 412 assets with full history | 21% more assets tracked |
| MTTR tracking coverage | 1 asset class (manual count) | All 412 assets (automatic) | Full fleet visibility |
| Deployment payback period | — | 4 months | From downtime reduction only |
Swipe to view full table
Three Operational Changes Behind Every Metric Improvement
The 2.5-hour average technician response delay was not caused by technician unavailability — it was the communication gap between the supervisor creating a paper work order and the on-call technician receiving it. Mobile dispatch eliminated this entirely: the work order appears on the technician's phone the moment it is created, with asset location, fault description, and repair history attached. Response time dropped from 2.5 hours to 18 minutes — producing more than half of the entire MTTR improvement from this single operational change. Sign up for Oxmaint to activate mobile dispatch at your plant.
The paper PM schedule failed silently. When a technician was pulled from a scheduled PM to an emergency breakdown, the PM was simply not done — the whiteboard showed it as pending but there was no escalation, no alert, no record of the skip. Oxmaint's PM escalation generates an overdue alert to the supervisor when any PM exceeds its scheduled date by the configured tolerance — 24 hours for critical assets, 72 hours for secondary. The PM is never silently missed. Book a demo to see PM escalation configured.
The EAF electrode column had broken down three times in six weeks before Oxmaint was deployed. Each time, a different technician filed a paper work order. No one had looked at the three together, compared the failure description, and identified that each breakdown had the same hydraulic cylinder seal failure preceded by the same skipped inspection. Oxmaint's asset history displayed all three work orders in the same view — same fault code, same component, same preceding missed PM. Pattern visible in 30 seconds. Root cause corrected. Zero recurrences in the following 18 weeks. Sign up for Oxmaint to start building your asset history.
Maintenance Manager's Assessment — 12 Months After Go-Live
Before Oxmaint, I could tell you that the EAF had broken down three times in six weeks. I could not tell you why each time was the same hydraulic seal, or that the inspection that would have caught it had been skipped three times because the technician was on something else. With Oxmaint, I can see that pattern in 30 seconds — for every asset, every breakdown, every recurring failure. The 40% MTTR reduction is real and it is documented. But the bigger change is that I can now answer when someone asks why a particular asset keeps failing — because I have the data. Before, I was guessing. Now I know.
Your Plant Has the Same Recurring Breakdowns. The Difference Is Whether You Have the Data to See the Pattern.
Every EAF mini-mill running paper work orders has maintenance patterns that are invisible — recurring failures on the same component, PM gaps before the same breakdown, parts stockouts for the same part. Oxmaint makes these patterns visible within the first 60 days of deployment.
Questions About This Case Study and Oxmaint for EAF Operations
The entire 40% MTTR reduction in this case study was achieved without a single IoT sensor. The improvement came from three purely operational changes: mobile dispatch that eliminated the 2.5-hour technician response delay, PM escalation that prevented the missed inspections causing recurring breakdowns, and asset history that made the recurring failure pattern visible for root cause correction. IoT sensors add a further layer of predictive capability — but this case study demonstrates that the mobile CMMS layer alone delivers substantial and measurable MTTR reduction at a plant starting from a paper-based baseline. Sign up for Oxmaint to begin with the operational improvements first.
Full voluntary adoption — no paper work orders alongside digital ones — was achieved within 3 weeks of go-live. The training was 2 hours per technician, focused on 4 actions they would perform most often: receiving a work order, completing the checklist, recording observations, and closing. Adoption was faster than expected because the mobile system reduced the technicians' own administrative burden: no more hand-writing forms at end of shift, carrying paper through a dusty EAF environment, or waiting for the supervisor to receive an update. The system reduced their friction as much as the supervisor's. Book a demo to discuss deployment approach for your team size.
Yes — plants migrating from a legacy CMMS to Oxmaint frequently see comparable improvements, because legacy system adoption rates are typically 50–65% (work orders created in the system but often completed on paper first and then transferred). The mobile-first design, at-equipment completion capability, and real-time supervisor visibility are not present in most legacy deployments from more than 5 years ago. The improvement potential comes from whether your maintenance team is actually completing work orders in the system at point of work — not from whether a system technically exists. Sign up for Oxmaint to assess the improvement opportunity at your plant.
Start Your 90-Day Oxmaint Deployment. The First Prevented Breakdown Typically Arrives in Week 6.
Every day a paper work order is collected at shift end instead of closed at the asset is a day without the maintenance data that makes patterns visible, root causes identifiable, and recurring breakdowns preventable. Oxmaint deploys in 90 days, pays back in months, and builds the maintenance record that transforms reactive teams into predictive ones.
