Vimana
‹ All case studies
Industrial Services

A compressor-service business scaled 600+ AMC clients onto need-based maintenance.

A compressor-service company running annual maintenance contracts for 600+ clients wanted to grow without adding technicians in step — so we moved its book from fixed-schedule visits to remote, condition-based maintenance.

Headline outcome
600+

AMC clients moved from fixed-schedule to condition-based service

Company profile
ScaleField-service technician team
Footprint600+ client compressors under AMC
Starting stackAnnual maintenance contractsCalendar-based site visitsReactive complaint responseNo remote visibility
The challenge

Where the business was losing.

The business serviced 600+ clients on annual maintenance contracts — fixed visits on a calendar, regardless of how each compressor was actually running. Growing the client base meant adding technicians in step; healthy machines were serviced on schedule while stressed ones failed between visits; and there was no remote view of any client's machine.

The audit · 2 weeks

What the audit surfaced.

Before building anything, we mapped the operation. These are the findings that shaped what we built.

F01

Maintenance was calendar-based — every client was visited on a fixed cycle regardless of machine condition.

F02

Growth was capped by technician headcount: more clients meant proportionally more scheduled visits.

F03

Compressors that failed between visits became emergency call-outs — costly, unplanned, and bad for client trust.

What we built

The architecture, and the agents in it.

The data foundation, and the AI agents that turn it into decisions and action.

STEP 01

Remote sensing feed

An IoT device on each client compressor streams tank pressure, motor amperage and temperature to a central platform — continuous signal from the whole client base for the AI to read.

STEP 02

Failure-risk scoring agent

An agent correlates pressure-rebuild cycles with amperage to estimate motor ON-time and duty cycle, flags overuse, and scores each machine's burnout risk from abnormal current — so the business knows which client machines actually need attention.

STEP 03

Need-based dispatch agent

An agent ranks the connected fleet by risk and builds the technician visit list by condition rather than calendar, pre-empting failures before they become breakdowns — letting the business serve more clients per technician.

Implementation
Weeks 1–3Sensing devices rolled out across a first cohort of client compressors
Weeks 4–6Condition and burnout-risk scoring across the connected fleet
Weeks 7–10Need-based dispatch + client-facing condition reporting
Results

Before → after.

Measured against the baseline the audit established — before and after, on the metrics that move the P&L.

Maintenance model
Fixed annual scheduleCondition-based / need-basis
Clients per technician
Capped by visit cycleScalable
Failures between visits
Emergency call-outsPre-empted remotely
Client machine visibility
On-site onlyRemote, continuous
The value created
Grow the client book without growing the technician team

Value is the service business's ability to scale contracts and offer a differentiated need-based service — expressed as operating outcomes, not a rupee figure.

Service capacityMore clients per technicianVisits dispatched by machine condition, not a fixed calendar
Emergency call-outsReducedFailures caught remotely before they become breakdowns
Contract valueStickier AMCsCondition-based maintenance offered as a premium, differentiated contract

Illustrative engagement. The client is anonymised and the figures are representative of the outcomes we target in this sector — but the capability described is real and deployed. Named, verified case studies replace these as clients approve publication.

Start here

Could this be your operation?

Start with a Business Transformation Audit — a structured working session where we map where AI changes your P&L, prioritised by impact.

See more case studies