Industry · Construction

Less downtime. More billable hours.

Grivara OPS runs your heavy-equipment fleet, from the yard to the work front.

Request a demo See how it's modeled

For contractors and heavy-equipment fleets, excavators, dump trucks, loaders, generators.

What follows

Four things your operation already has, and nobody measures.

We don't sell modules. Below are the three leaks the machine-hour drains through, and the real screens of a loaded operation where they get closed.

The machine: What it earns per operating hour and costs per idle hour.
The hour: The hour meter, the only honest witness to what it actually ran.
The part: The one that wasn't on the shelf — nearly the whole cost of a breakdown.
The front: Where each machine is, and which crew stops if it doesn't show up.

Your year is decided in the machine-hour. It leaks in three places.

A contractor doesn't sell machines, it sells hours of machine on a work front. Every unit is worth one figure per operating hour and costs another per idle hour, and the whole business lives in that gap.

Leak 01

A stopped machine drags the whole front with it

Unplanned downtime doesn't cost you the machine alone. The crew stops with it, so do the trucks waiting to be loaded, and so does the work queued behind them.

400 h × $380/h on a single articulated dump truck = $152,000 a year — at the low end of the published range, on one unit.

Caterpillar research: unplanned downtime generates between 400 and 800 non-productive hours per machine per year in typical construction operations.

Leak 02

Fixing it in an emergency costs several times more than scheduling it

Nobody pays a mechanic more in an emergency. You pay for the part that wasn't there, brought in the way you didn't plan, plus the secondary damage the failure caused on its way down.

In the reference operation a corrective job averages $2,135 against $264 for preventive — 8.1×. And on work order WO-00147, $2,998 of the $3,208 total (93.5%) was a single part.

Reactive repairs cost 3 to 9 times the same work performed as scheduled maintenance, from expedited parts, overtime labour and secondary damage.

Leak 03

Hours the machine worked that nobody counted

The hour meter is the only honest witness to what a machine did, and it gets read by hand whenever someone passes through the yard. Between two readings the hours belong to no front, no ticket and no maintenance plan.

In the reference operation the two heavy-use machines carry 6,420 h and 9,985 h, captured by hand roughly every eleven days. Everything in between is an estimate.

Komatsu, across telematics from about 75,000 machines in North America: 38% average idle time. Construction fleets average 55–65% utilization against an optimal band of 70–85%.

The fleet

The equipment list, arranged the way you arrange the work.

It isn't a fixed table. Every arrangement your fleet office actually uses — by front, by what's down, by what's sleeping in the yard — is saved as a tab the whole team sees.

Saved views per work front: Ruta 32 Limón, Liberia–Cañas, and whichever ones you create.
"Down" gathers what can't produce today; "In the yard" gathers what's being paid for and producing nothing.
Each view carries its own columns, so the fleet office prunes what it doesn't use.
Category, manufacturer, model and location are objects rather than free text, so they actually filter.

The job site doesn't wait for the part to turn up.

Every stopped machine has a halted work front behind it. Knowing which one, where it is and what it needs is the difference between moving a crew and losing the day.

The machine

Every unit with a file and a rate.

The excavator isn't a row in a spreadsheet. It's an object carrying what it cost, what it has consumed in maintenance, who is certified to run it, and what every idle hour costs you.

Purchase cost, accumulated maintenance spend and the ratio between them, in the operation's own currency.
Required skills with levels: who can get on this machine and who can't.
Service history, documentation, rental and reliability in the same file.
Value per operating hour and cost per idle hour — what turns a stoppage into a number.

The cost

When a breakdown opens, the part is nearly all of it.

A closed work order doesn't just say what it cost. It says what the cost was made of. And a corrective job always has the same shape — which is exactly what meter-driven preventive avoids.

Labour $210 across 9 logged hours, at $23.33/h.
Parts $2,998 — 93.5% of the $3,208 total.
Hours are logged against the order, not estimated at month end.
The SLA inherited from the priority flags the breach on the order itself, not in a month-end report.

One real order

A hydraulic leak on the Ruta 32 Limón front.

This is a complete order in the reference operation, from whoever reported it through to the reconciled cost. Nothing invented: it's work order WO-00147.

01The yard reports itMaría Jiménez opens the order as a corrective repair, high priority, on the Ruta 32 Limón front.
02It goes to the mechanicJuan Castro picks it up. The SLA policy inherited from the priority starts two clocks: response and resolution.
03Both clocks are missedResponse breached by 20 h, resolution by 4 days — visible on the order, not discovered at month end.
04It closes with the cost broken out$3,208: nine hours of labour at $210, and one part at $2,998.
05The lesson is on the recordThe cost was the part. And the part is exactly what a meter-driven preventive job would have had on the shelf.

Who decides

Five roles, five different questions.

One person doesn't sign for this. Each role arrives with a question of its own, and the platform has to answer it in their language.

Equipment manager

"What did idle time cost me this month, by machine and by front?"

Downtime cost per unit and per job
Utilization against what the machine should have been producing
Exports for the board

Shop foreman

"Will it tell me which part to stock before the machine goes down?"

Preventive triggered by hour meter, not just the calendar
Parts reserved against the order
Full history per machine

Site engineer

"I need the machine on Tuesday. Does this tell me whether it's coming?"

What's assigned to their front, in a view of their own
Transfers with origin, destination and in-transit status
What's down, and why

Cost control

"Does this reconcile with the ERP, or is it another sheet nobody fills in?"

Labour and parts broken out per order
Budget per machine and per front
Audit trail on every change

Safety lead

"Is the inspection on record, with a date, an owner and evidence?"

Inspections with due dates and owners
Photos and signatures attached to the record
Operator certifications with expiry warnings

And if your org chart looks nothing like this

Roles, permissions and views are defined per resource and per action. Each front and each subcontractor sees only what's theirs.

ViewCreateApproveExport

Objections

What gets asked before the demo.

We run everything on spreadsheets and WhatsApp today. Why change?: Because the spreadsheet has no hourly rate and doesn't know which machine is down right now, and WhatsApp leaves no record. Neither can tell you what downtime cost you last month. We're not asking you to abandon them on day one — only that the fleet, the orders and the hour meter live in one place.
The yard hand writes the hour meter in a notebook. Does that work here?: It works, and it stays a manual reading: captured against the machine, with a date and whoever took it. The difference is that the platform schedules preventive work against that reading rather than the calendar alone, and tells you when the machine has hit the hours.
We already have an accounting ERP. Does this replace it?: No. The ERP knows what the machine cost to buy and what the repair invoice said. It doesn't know which hour it stood still or why. This lives on the operations side and hands the ERP a cost already broken out by order, machine and front.
We work in dollars and colones, and with subcontractors. Is that handled?: Yes. Costs are kept in the currency each front operates in and consolidated at the exchange rate. Permissions are defined per resource and action, so a subcontractor sees their front and nothing else.
How long before it's loaded with our machines?: The initial load is the fleet, the fronts and the crews. Those three objects are enough to open orders and start accumulating hours and cost; the rest — certifications, budgets, documents — loads in without stopping the operation.

Everything the platform gives your construction operation.

Under every screen is the full platform, with the security, governance and scale of your entire operation.

Multi-front, multi-country registry: Every machine, front and project in one source of truth, with costs in the currencies you operate in.
Operator certifications with expiry: Who can operate which equipment, with level and expiries flagged before they lapse.
Automatic alerts and escalation: Preventive coming due, extended downtime and overdue safety inspections; subscribers escalate what's critical.
Parts and warehouse stock: Reserve the part for the repair and draw it down on use, with source and conflicts controlled.
Mobilization and transfers: Move equipment between fronts with origin, destination and in-transit status, without overlaps.
Live GPS fleet tracking: Position and movement state for machines and crews where you connect it, with geofences per front.
Analytics and exports: Utilization, downtime cost, MTTR and cost per front, with exports for boards and audits.
Complete audit trail: Who changed what and when, on every order, every record and every approval.
Fine-grained roles and permissions: Who sees, does and approves is defined per resource and action; each front and contractor sees only their own.
Documents and evidence: Certificates, manuals, photos and signatures attached to and retained with the machine.
Threshold approvals: Spend or repairs above the threshold you set require approval before they proceed.
Consolidated multi-currency: Costs and profitability in your currencies, consolidated at the exchange rate.

Modeled 1:1

Your job-site reality as it is, not a CRM with modules bolted on.

Every word you use in the yard has an object in Grivara OPS. We don't force your operation into a generic CRM — we model it as it is.

Excavator, dump truck, compactor: Equipment, with its history, its hourly value and its downtime cost.
Work front, yard, warehouse: Location, with the machine assigned to it and its availability.
Crew: Team, with its technicians and their skills.
Hour meter: Meter reading, which triggers preventive work by hours.
Transfer between fronts: Order shipment, with origin, stops and a manifest.
Machine downtime: State interval, with its duration and its cost.
Part used: Part usage, drawn from the warehouse against the order.
Safety inspection: Compliance record with due date and evidence.

The demo

So no machine sits broken, or idle.

We show you your own fleet inside the platform: your machines, your fronts and your hourly rates, so you see the downtime cost in your numbers rather than ours.

We load part of your real fleet before the call.
You leave with the downtime cost of your machines, calculated at your rates.
No purchase commitment and nothing to install.

Book the demo

We reply the same business day.