Torek Heavy equipment maintenance software
Updated
An in-house heavy equipment workshop means your own bay and your own mechanics looking after the company’s excavators, loaders, trucks and everything else. Its real enemy is not breakdowns but disorder: faults nobody wrote down, jobs that got lost, and a history that exists only in people’s heads.
Torek is a CMMS built for exactly that internal workshop: faults are recorded on a phone from site, jobs are handed to mechanics, and the history of every unit accumulates on its own.
Most workshop software is written for garages repairing customers’ vehicles: its core is intake, customer estimates and invoicing. An internal workshop needs none of that. It needs answers about its own equipment:
That set of needs has an international name — CMMS, a computerised maintenance management system. How Torek compares with the international products in that category is set out in the side-by-side comparison.
A practical note: the biggest cause of downtime in an internal workshop is not a slow repair but a fault noticed late. The shorter the path from “the operator saw it” to “the mechanic knows”, the less equipment stands idle.
What an idle machine costs only becomes an argument once the idle hours are counted. When a repair job is raised, it can be marked that the machine cannot work: downtime starts automatically and closes when the repair is completed. Downtime without a repair is entered by hand with a reason — waiting for parts, an accident, an inspection or other.
The result is a plain answer to “how many machines are standing right now”, and every unit gets its own downtime history in hours. Administrators and the managers responsible for that machine are told when it stops and when it is working again, with the hours and the reason, and every morning they get a summary of the equipment that has been standing for more than a day. The same hours appear in the monthly repair report, next to parts, labour and outside-garage invoices.
Heavy equipment work happens in gloves, in a yard, often nowhere near a desk, so the tools have to match:
| Where | What is used | What it is for |
|---|---|---|
| On site | The Android app, working offline | Reporting a fault with a photo; syncs when back in range |
| In the workshop | A shared screen with PIN sign-in | Each mechanic sees their own queue, no shared password |
| In the office | The browser | Planning, parts, history and reports |
A recorded fault becomes an entry in the defect log, then a job in the work order system, and finally a line of asset history with its parts and hours (see repair tracking). Nothing is entered twice along the way.
The tipping point is usually not the number of machines but the cost of downtime. Once a day of an idle excavator or loader costs more than a day of a mechanic, waiting in someone else’s queue becomes the most expensive line in the estimate.
Most fleets do both: daily and emergency work in-house, engine and hydraulic overhauls with specialists.
Intervals are counted in engine hours rather than kilometres; parts cost more and take longer to arrive; the machines work on sites far from the workshop.
So reporting faults from the field on a phone and planning work in advance matter far more here — an unplanned stop on site costs incomparably more than a scheduled repair.
With two things: reporting faults on a phone and a queue of work orders. Those two steps alone remove the pile of notes on the desk and start building a history.
Stock, preventive maintenance and reports are worth adding as a second stage, once the crew is used to recording things daily.
Yes. Only the maintenance measures differ: kilometres for trucks, engine hours for self-propelled machinery. A system that supports both lets the whole fleet sit in one place.
From the repair itself. When a job is raised for a machine that cannot work, downtime starts automatically and ends when the repair is completed. A stop without a repair — waiting for parts, an accident, an inspection or another reason — is entered by hand with that reason.
Each machine then has its downtime history in hours, and the monthly repair report shows downtime hours alongside repair costs. Downtime tracking is a module the company switches on when it needs it.
It stays. Every defect, job, part and reading is kept on the asset record, so the service history can be shown to a buyer instead of reconstructed from invoices.
A walkthrough: from a fault on site to a closed job in the workshop.
Get in touch