
The client
The client is a large manufacturing company in India with production units in several industrial regions, machining and pressing metal components.
Its output depends on CNC machining centers and hydraulic presses running through every shift. Maintenance is planned by a central team, while each plant’s own technicians do the work on the shop floor.
The challenge
With no central maintenance system, each plant kept its own service calendar. Routine servicing slipped whenever production was busy, and wear was found only after a machine stopped mid-shift.
- Lubrication, filter and spindle services were missed at busy plants.
- Wear showed up as a breakdown instead of at a planned check.
- Unplanned stops pushed back production schedules.
- Service records were kept differently at each plant.
- The central team could not see which machines were overdue.
What they set up in Asset Infinity
The company set every CNC machine and press on preventive plans in Asset Infinity, timed by calendar or running hours, with each plant working its own queue.
Plans on running hours
Running hours recorded for each machine drive meter-based plans, so a heavily used machining center is serviced sooner than one that ran less. (Maintenance)
Service checklists by machine type
Each plan carries the checklist for that machine type, from way lube and hydraulic oil to spindle and clamp checks, with readings and photos. (Maintenance)
A queue for each plant
Each plant’s jobs go to its own technicians under its own workflow, with reminders when planned work sits unstarted. (Work)
Overdue servicing across plants
The central team sees planned, overdue and completed servicing by plant and machine type on one dashboard. (Insight)
How it works day to day
A machining center’s service cycle now runs like this.
- Production supervisor: logs running hours. At the end of each shift, the running hours for each machine are entered against its meter in the app.
- System: raises the service when due. When the machine reaches the hours set in its plan, a work order is created with the service checklist attached.
- Plant maintenance lead: books it into a changeover. The lead schedules the job into the next planned changeover and assigns a technician, who is notified on the mobile app.
- Technician: services the machine. Oil and filter changes, lube levels and spindle checks are ticked off with readings and photos. A failed check raises corrective work.
- Machine operator: flags a problem between services. Unusual noise or a hydraulic leak is reported by scanning the machine’s QR label, so it reaches maintenance straight away.
- System: chases late work. A planned job left unstarted sends reminders and escalates to the plant maintenance lead.
- Central maintenance team: compares plants. Dashboards show overdue servicing and breakdowns by plant and machine type, so intervals can be adjusted where machines still fail.
Before and after
| Before | With Asset Infinity | |
|---|---|---|
| Maintenance system | None central | One system across plants |
| Service timing | Timelines frequently missed | Raised by date or running hours |
| Issue visibility | Delayed | Reported by QR scan, seen at once |
| Records | Legacy, kept per plant | Migrated onto each machine |
| Machine uptime | Lost to unplanned stops | Improved by 32% |
How it rolled out
- Machines and history loaded. Machines were registered plant by plant, and legacy maintenance records were moved onto each one.
- Intervals agreed. Maintenance categories and schedule rules were set per machine type, with plant-wise workflows for each service function.
- Plant teams trained. Technicians and production staff were trained on the mobile app, with ongoing reviews after go-live.
The results
- 32% improvement in machine uptime
- Planned servicing timed by how hard each machine actually runs
- Wear caught at scheduled checks instead of in a breakdown
- One view of overdue servicing across all plants
- Steadier production schedules with fewer unplanned stops
Why it worked
Servicing follows use
Plans driven by running hours match each service to the work a machine has done, instead of the calendar alone.
Each plant runs its own floor
Plant teams keep their own queues and workflows, while the central team sees every plant at once.
Small problems reported early
Scanning the machine label is quicker than finding a supervisor, so operators report faults before they become stoppages.
Looking ahead
By servicing its CNC machines and presses on plans tied to running hours, the company catches wear at planned checks and has improved machine uptime by 32%.
The service history building on every machine now lets the central team refine intervals by machine type and plant.




