OEM, dealer, end user. One view, top to bottom.

Three parties have always worked the same machine off three different sets of books. HILOview puts them on one. Service, parts, rental, equipment sales and warranty, with the hours and the dollars attached to every unit, whatever the make.

OEM Dealer End user

Three machines working on a construction pad: a Zoomlion excavator, a Komatsu excavator and a Cat wheel loader. — A real pad. Three makes. One cost basis.

Cost per hour by CC1Mixed fleet · trailing 90 days · 6 units $43.25blended /hr

1 EX-21 PM due Zoomlion ZE210GLC · 2,140 hr $38.90/hr214 dMTBF CC1 F Undercarriage trending ▲ 9%

2 EX-14 Ready Komatsu PC490LC · 6,412 hr $44.10/hr119 dMTBF CC1 G Hydraulic System · 31% of spend

3 WL-30 Down Cat wheel loader · 12,806 hr $49.20/hr74 dMTBF CC1 A Engine · open service issue

The range

OEM: What the field is actually reporting about the product, and the warranty recovery that follows it, before the claim data goes cold.
Dealer: Service, parts, rental, equipment sales and warranty, with the absorption that ties them together.
End user: Every unit owned, all makes side by side, with a cost per hour that survives an audit.
Machine: One unit, its meter, its PM schedule, its whole repair history and what each visit cost.
Work order: Complaint through confirmation, coded to a real vocabulary instead of a free text box.
The hour: The labour minute, the part off the shelf, the rate it billed at. Where the margin actually lives.

The same record, read three ways.

Nobody has to re-key anything, and nobody has to trust a spreadsheet somebody else maintains.

End user

Know what the iron costs

Your fleet in one place, every make, with meters and PM status
Raise an issue and watch it move without picking up the phone
Cost per hour per unit, built from real invoices, not estimates
Run or replace, with the history behind the answer

Dealer

Run the whole department

Dispatch, technician time, parts, quoting and invoicing in one lifecycle
Absorption and applied rate visible while the month is still fixable
Split billing across customer, vendor claim and internal in the same job
Rental, equipment sales and the service that follows both
Warranty claims built from the actual repair, recovery and variance tracked to the dollar

OEM

See the product in the field

What the field is reporting about the product, coded, not paraphrased
Claims built from the actual repair, with proration math per programme
Recovery inside the claim window rather than after it
Parts movement that reflects what really got replaced

The coding library

Every repair lands in the same vocabulary.

Free text cannot be added up. Ten years of repairs coded the same way can. Three levels say what was worked on, and a fourth says why it was replaced.

CC1 System26 codes GHydraulic System
CC2 Group97 groups G-4Cylinders
CC3 Component361 components G-4-4Cylinder Seal Kit
SPF Why it was replaced24 reasons 52Overhaul Unreusable Parts

That is one real path through the library, not an example written for a website. A technician never types a code. He picks the component he worked on, and the code and its default reason come with it, which is why the capture screen has no free-text field to get wrong.

The reason codes are grouped on purpose

10s: Planned replacement. PM items, ground engaging tools, undercarriage.
20: Replaced early on purpose, before it can stop anything.
30s: Machine down. It stopped, and this is what stopped it.
40s: Major components. Engines, transmissions, pumps, cylinders.
50s: Overhaul. Bearings, seals and gaskets consumed during a repair.
60s & 70s: Appearance and durable items. Decals, panels, guards.

The distance between 20 and 31 is the entire inspection argument: the same hose, replaced on a walkaround or replaced at 02:40 on a Tuesday. Because the reason is coded either way, you can count how often you were on the right side of that line, by machine, by site, by year.

Cost per hour

Where the money went, down to the component.

Not a service total. Every dollar lands on the system that failed, then drills to the assembly, the part, and the reason it was replaced.

Cost per hour by CC1 — component, group, part, SPF

The codes are the real coding library: CC1 G Hydraulic System into Cylinders into Cylinder Seal Kit, out to an SPF code that says whether it was planned wear or a breakdown. Figures are illustrative.

Reliability

Which machine is costing you, and how sure we are.

Mean time between failures against the fleet median, the system that keeps coming back, and a grade that is honest about what it does not yet know.

Fleet reliability and the five-axis machine scorecard

A machine is flagged for a replacement conversation on a rule, not a hunch: five or more failures and an MTBF under a third of the fleet median. An axis nobody has graded is drawn as a gap, never a zero — a machine you have not rated is not a bad machine.

From the field

Twelve minutes from a dead zone to the people who decide.

Capture does not wait for a bar of service. The record is written on the device, replays in order when the truck crests the hill, and arrives as coded work on three screens at once.

One failed item, from the machine to the dealer, the owner and the OEM

The old path is on the same plate for comparison: paper sheet, tray, Friday batch, month-end report. Day 24. The machine knew on day zero either way.

Data entry

Scan, shoot, tap, say.

The cleanest data comes from the flow that asks for the least. Machine and meter arrive filled in, the complaint is dictated, and the codes come from the library rather than a text box.

Field capture, and the fully coded record it produces

Zero free-text fields on the record that lands. That is not discipline, it is the only thing the screen lets you do — which is why the coding holds up a year later.

Inspections

Catch it while it is still small.

A seeping hose found on a walkaround costs a hose. The same hose, found by letting go at 02:40 on a Tuesday, costs the shift.

A 500-hour PM, the evidence it requires, and the problem it catches early

The coding library already separates the two: SPF 20 is the part replaced on purpose before it can stop anything, SPF 31 is the part that stopped the machine. The inspection is how you stay on the left of that line.

The platform

Nine departments. One record.

Not modules bolted together. One data model that every department writes to and reads from.

Service

Dispatch board with conflict detection, mobile technician day view, atomic stage transitions, offline capture that survives no signal.

Parts

Catalog, inventory, purchase orders, RMAs, cycle counting and matrix pricing with separate lanes for aftermarket, represented and non-represented lines.

Quoting

A quote is the job, born early. Approve it and the work order is already built, priced and dispatchable.

Invoicing

Built from live labour and parts, not retyped. Every invoice carries an internal profitability view the customer never sees.

Warranty

Claims, coverage, RMAs and proration math per OEM programme, with rework and goodwill costed back to the job that caused them.

Rental

Units on rent, off rent and on the way, with the service history that follows the machine rather than the contract.

Equipment sales

Pipeline, valuation and trade decisions informed by what the fleet actually costs to run.

Fleet portal

Your customers, in their own view, raising issues and correcting their own machine records.

Workforce

Time, certifications, payroll export and the dual clock that keeps payroll overtime and billable overtime honestly separate.

Why it is different

Built by a service department that got tired of guessing.

Four things most systems in this industry do not do, because the people who wrote them never had to close a month.

Coded repair data

A vocabulary, not a text box

Every job moves through four stages and is coded to a real taxonomy of system, assembly and component. That is what turns ten years of repairs into failure data you can actually query.

C1 Complaint→C2 Cause→C3 Correction→C4 Confirmation

Split billing

Three payers on one job

A single work order can bill the customer, claim against the vendor and absorb the rest internally, line by line. Goodwill shows as a credit the customer can see, and the absorbed cost still lands against the job.

CustomerVendor claimHouse

All makes

One make cannot show you the fleet

A system built around one manufacturer connects you to that manufacturer. A mixed fleet needs one that treats every make the same way, with the same coding and the same cost per hour, so the comparison is real.

KomatsuCatVolvoHitachiZoomlion+

The dual clock

Payroll time is not billable time

Overtime past forty hours is a payroll fact. Work outside the shift window is a billing fact. They are independent, a technician can have one without the other, and treating them as the same number is how margin quietly disappears.

Fleet readiness

Status your customer understands at a glance.

Ready, PM due, down. The same three words the yard already uses, driven by real meters and real work orders.

Example fleetillustrative

EX-14Excavator6,412 hrsReady

EX-21Excavator2,140 hrsPM due

WL-22Wheel loader9,140 hrsDown

HT-7Articulated hauler11,908 hrsReady

Built on real work

Not a prototype with sample data.

HILOview was built inside a working heavy equipment service business, against its own history, and pressure tested on live jobs before it was offered to anyone else.

OEMs represented in the repair history behind it

22,500

Service manuals indexed and searchable

All makes

No brand gets special treatment in the data model