Torek Preventive maintenance software
Updated
Preventive maintenance in Torek is described with rules. A rule says what has to be done and what counts the interval — kilometres, engine hours, days or months. From the rule and the asset’s meter history the system works out the next due date and creates a schedule for it.
From there the schedule runs on its own: it changes state as the date approaches and passes, and appears once a day in a summary for the people who can act on it. A scheduled item becomes a work order in one step, and the schedule closes with a meter reading that immediately feeds the next forecast.
A rule has a name, a description, an interval type with a value, and an optional asset-type filter. Left empty, the filter means the rule applies to every active asset; filled in, only to that type. Five ready-made presets — oil change, filter change, brake check, tyre rotation and technical inspection — prefill the name, description and a suggested interval, which you then edit to whatever the manufacturer and the actual duty cycle require.
| Interval type | What it suits | Example |
|---|---|---|
| Kilometres | Tractor units, trucks, cars, vans | Oil change every 10,000 km |
| Engine hours | Self-propelled and stationary machinery: excavators, loaders, generators | Service every 500 engine hours |
| Days | Jobs whose frequency is set by time, not by load | Brake check every 180 days |
| Months | Calendar and statutory work | Technical inspection every 12 months |
For date-based intervals the arithmetic is trivial: days or months added to the last completion date. Meter-based intervals run on reading history instead:
Readings are the foundation of all of this. They do not only arrive by hand: a reading is captured when fuel is filled, when a trip log is approved, when a repair is created, raised from a defect or completed, when protocol parts are checked off, and when a planned job is closed. So a car repaired at outside garages, with no trip logs, can still have its mileage recorded at each garage visit; a reading lower than the last one is rejected. The more often a meter is recorded, the better the forecast — and the reverse holds just as firmly.
Calendar rules — every 12 months, every 6 months — need a starting point. For each asset the date the job was last done can be entered, or one date for all of them at once, and the next due date is worked out straight away. The system also shows how many assets still have no date entered, so a gap in the plan does not stay hidden.
This is how equipment with no odometer and no engine-hour meter is planned: semi-trailers and trailers, tachograph checks, annual inspections. The rule is tied to the asset type, and once the job is done, the following due dates run from the actual completion date.
A background sweep runs once a day. It updates the state of every schedule, generates the ones that are missing, and tells the people who can act.
| State | Meaning |
|---|---|
| Scheduled | Due date still ahead |
| Due | The date has arrived, the job is not done |
| Overdue | More than seven days past the date |
| Completed / Cancelled | Closed; a completed one carries a date and a reading |
The result is a maintenance plan that keeps itself current. Every due date and completed job stays on the asset record next to mileage, engine hours and repairs, so a unit’s service history is one list. Planned maintenance also appears in the workshop calendar as read-only entries, so the calendar and the maintenance module always show the same date.
What the module does not do: it does not raise work orders behind your back — that is a deliberate action; it does not read meters from telematics or GPS hardware; and it does not order parts. Parts for a specific job are planned through a service protocol, against warehouse stock.
On four interval types: kilometres, engine hours, days and months. A rule carries one type and one value — 10,000 km, or 500 engine hours, or 12 months.
A rule can be narrowed to a single asset type or left to apply to the whole fleet. Deactivating a rule stops it generating new schedules; the schedules it already produced stay where they are.
From reading history. The readings of the last 90 days give an average daily usage rate, and the next threshold — the meter value at the last schedule plus the rule's interval — divided by that rate gives the predicted date.
It needs at least two readings taken at least a day apart. Until they exist, a meter-based due date is not calculated at all; date-based intervals (days, months) need no readings and run from the last completion date.
Not necessarily. One rule with an empty asset-type filter covers the whole fleet, which is usually right for something like an annual inspection.
Mixed fleets are the case for narrower rules: a rule tied to kilometres says nothing useful about a loader that drives a few hundred metres a day and works for eight hours. That asset's maintenance clock is engine hours.
With a date-based rule — every 6 or 12 months, for example — applied to the trailer's asset type. Enter the date each unit was last serviced or inspected, or one date for all of them, and the next due date is calculated immediately. No odometer or engine-hour readings are needed.
The same approach suits tachograph checks and annual inspections. The system shows how many assets still have no last-done date, so none is left out of the plan by accident.
One a day. The daily sweep counts what is late and what falls due within three days, and sends a single summary — “3 planned jobs overdue, 2 due soon” — rather than one notification per schedule.
It arrives in the app and, when the user has push enabled, on their phone. It does not repeat within the same calendar day.
Yes: by a week, two weeks, a month, or to a specific date, with a reason. The count is capped at three postponements per schedule, and the remaining count is shown before you use the last one.
The cap is deliberate. Unlimited postponement is, in practice, the absence of a maintenance plan.
A read-only “planned jobs” screen with two lists — what is overdue and what falls in the next 30 days — plus a card on the home screen.
Postponing, completing and raising a work order from a schedule stay in the browser, because those are manager actions.
A walkthrough with your asset list and your real intervals.
Get in touch