Torek Features
Updated
Torek is a maintenance management system (CMMS) for a company’s own fleet and its workshop. The whole system is laid out as one chain: defect → work order → preventive maintenance → parts → fuel → trip logs → reports. Every link reads from the same asset record, so a reading, a part or a cost is entered once and used in several places.
Below is every module: what it does, where it is used (browser, Android app or the workshop kiosk) and a link to that module’s own page. Torek is not GPS tracking and not accounting software; a workshop that also repairs customers’ vehicles can add an optional module for invoicing them. What Torek deliberately leaves out is listed at the end.
A list of features says little on its own. The value appears when one record travels the whole chain without being retyped:
| Module | What it does | Where it runs | Link |
|---|---|---|---|
| Defects | A fault logged where it was found: description, severity, photos and the specific machine. An entry made by mistake is removed only by the administrator, with a reason — it stays in the removal log and can be restored. | Browser · app · kiosk | Defect log |
| Work orders | Priorities, owner, deadline, a type of repair, a full status lifecycle, comments and an audit trail; a defect becomes a job in one step. | Browser · app · kiosk | Work orders |
| Outside garage | A repair is marked as done by your own workshop or by an outside garage from your vendor list. The garage’s invoices — amounts excluding and including VAT, the VAT rate (21 % by default) and the PDF — go onto the job and into its cost; only managers with approval rights see the amounts. | Browser | Repair tracking |
| Downtime | A repair for a unit that cannot work starts downtime, and completing the repair ends it; other stops are entered with a reason. How many units are standing now, hours per unit, alerts when a unit stops and works again, and a morning summary of anything standing for more than a day. | Browser | Heavy equipment |
| Preventive maintenance | Each rule has one interval — kilometres, engine hours, days or months. Every day the system builds schedules from readings and rules and notifies the people responsible about what is coming up or overdue; a scheduled item becomes a work order in one step. For calendar rules, the date a job was last done can be entered per unit or for all at once, and the next due date follows immediately. | Browser (rules) · app (list and reminders) | Preventive maintenance |
| Service templates | Parts kits planned in advance as a service protocol, plus a checklist that can be made mandatory; the job cannot be closed until the parts are confirmed and a required checklist is signed. | Browser (templates) · app (parts confirmation) | Maintenance checklists |
| Asset record | One record per unit: defects, jobs, maintenance, parts, fuel, photos, document files (registration, insurance, inspection, warranty) and the full history. | Browser (all views) · app (details, history, photos) | Fleet maintenance |
| Engine hours and mileage | Mileage from approved trip logs and the readings entered with fill-ups and services build one meter history per vehicle, and preventive-maintenance due dates are forecast from it. Fuel consumption is calculated from fill-ups only. | Browser · app | Engine hours |
| Parts and stock | Stock across locations, reservations for a specific job, write-off into job cost, purchase requests with approval and back-ordered parts that reserve themselves on arrival. | Browser (management) · app (parts on the job, online) | Parts inventory |
| Fuel | Fills, versioned norms, actual against norm, fuel-card imports (CSV or Excel), an anomaly queue and a monthly write-off report. | Browser (full module) · app (driver fills) | Fuel tracking |
| Trip logs | Drivers keep trip logs on the phone (works offline); managers approve them in the browser. Numbering, submission, approval and return for correction; approved mileage joins the vehicle’s meter history. | App (drivers) · browser (approval) | Trip logs |
| Labour time | Hours recorded against each work order — the part of cost per unit that is usually missing. | Browser (hours) · app (timer or manual entry, hours worked today) | Repair tracking |
| Workshop calendar | Planning by mechanic and machine; a booking that overlaps another one for the same mechanic is refused. | Browser (planning) · app (read-only) | Workshop calendar |
| Workshop kiosk | A shared screen on the shop floor: PIN sign-in, your own job queue, start and finish, and logging a defect. | Kiosk (browser, on a shared screen) | Workshop kiosk |
| Mobile app | An Android app for mechanics and drivers; it works offline and syncs when the connection returns. | App | Mobile app |
| Reports and KPIs | Cost per unit, maintenance punctuality, work-order cycle time, defect ageing, statutory deadlines, and a monthly repair report by unit, repair type or garage with downtime hours; export to CSV, XLSX and PDF. | Browser | Reports |
| AI assistant | Questions about your own fleet in plain language, answered only from your company’s records and only for users the company has granted access. | Browser · app | AI assistant |
About notifications: an assigned job, a new defect and an approaching service are announced in the system itself and by push on the phone; an assigned job also arrives by email. Every user turns the channels and the events on or off for themselves.
Torek is built for a company that maintains its own equipment. For your own fleet there is no customer invoice — there is a cost centre, downtime, and a history that stays with the company (a workshop that also serves outside customers invoices them with the optional workshop module):
| Fleet | Typical situation | Where to start |
|---|---|---|
| Trucks and trailers | Mileage, statutory deadlines and downtime cost the most; drivers are spread across routes. | Fleet upkeep |
| Construction and road machinery | The service clock is engine hours, not kilometres, and the site often has no signal. | Heavy equipment |
| Agricultural machinery | The season does not wait: a breakdown mid-season costs several times what the same repair costs in winter. | Preventive maintenance |
| Company cars | No workshop of your own — external garages do the repairs, but the history and the deadlines must stay in-house. | Company car records |
| A workshop with mechanics | Several mechanics, one shared job queue, parts and hours on every job. | Work orders |
| A workshop without permanent mechanics | Operators handle the small jobs and an external garage the rest; what matters is that a record remains. | Repair tracking |
The asset list is grouped into cars, trucks, trailers, road machinery, tools and other, and stationary objects can be kept alongside them: buildings, machines, warehouses and infrastructure. For a mixed fleet that means one job queue and one history whatever the brand.
Deliberately out of scope: location and route tracking (that is telematics); VAT returns and the general ledger (that is accounting software — invoices received from outside garages are recorded as a repair cost, and the optional workshop module issues sales invoices and their register for export, not the books themselves); direct connections to fuel-station systems — a fuel-card statement is downloaded from the provider’s portal and uploaded as a CSV file.
If you are after an answer rather than a module, start with these pages:
Yes — this is one system, not a bundle of separate tools. A defect, a work order, a maintenance rule, a part, a fuel entry and a trip log all hang off the same asset record, so a reading or a cost is entered once and used in several places.
What an individual sees is decided by their role: a driver sees their own entries, a mechanic their own jobs, a manager the whole fleet.
Yes. Modules are enabled per company — a module that is off is closed to everyone in that company, and the system refuses its requests. Most fleets start with defects and work orders, then add fuel, trip logs or parts later.
The phone (Android) carries what happens next to the machine: a defect with photos, your own job list and statuses, time logged on the job, checklists, a fuel fill, trip logs, maintenance reminders and questions to the assistant.
The browser keeps the office side: maintenance rules and service templates, the calendar, parts management, fuel norms and the review queue, trip-log approval and reports. Drivers keep trip logs on the phone (works offline); managers approve them in the browser.
No. Torek is a CMMS — repairs, maintenance and defects. Location, routes and live telemetry belong to telematics, and in most fleets the two systems are used side by side rather than instead of each other.
Yes, with the outside-garage module switched on. A repair notes whether your own workshop or an outside garage does the work; the garage is chosen from your vendor list, and its invoices — with the VAT rate (21 % by default) and the PDF — are recorded on the job and count towards its cost. Several invoices can sit on one repair, for parts and labour separately.
This records invoices you receive for your own equipment.
Yes, with the downtime module switched on. Downtime starts when a repair is raised for a unit that cannot work and ends when the repair is completed; a stop without a repair is entered with a reason. You see how many units are standing right now and each unit’s downtime hours, and the monthly repair report shows them next to the repair costs.
With the asset list and one habit: every fault gets logged in one place instead of a message or a hallway conversation. Once defects land in one queue, the job list follows, and history and costs follow from that.
Preventive maintenance, parts and fuel are worth adding afterwards — otherwise three processes have to be fixed at once.
A walkthrough with your asset list and a real fault.
Get in touch