Module
Events
From the fault report to the checked fix. The photos, the checklist, the parts and the hours stay on the job, so every repair leaves a record and a cost.
What it does
Four-stage workflow
Every job moves through New, Assigned, Completed and Checked, with live counts per stage and assigned work pinned to the top.
Priorities and deadlines
Three priority levels, deadline warnings that turn red past due, and checklists resolved task by task.
Spare parts from the job
Attach warehouse parts to an event. Shortages raise a parts request automatically.
Full job costing
Staff time, spare parts, device downtime and external costs summed per event.
Audit trail and time KPIs
Complete activity history plus repair time, idle time and downtime tracked on every event.
AI repair suggestions
Similar past events analysed for typical repair time and parts used. Printable protocols and QR codes included.
How it works
It starts as a report
Someone scans the device QR code or picks the device from the list, sets type, priority and deadline and attaches photos. Schedules and rules create the same kind of job without anyone typing.
It gets an owner
From New the job is assigned to a person or a group. The checklist, the files and the parts already reserved travel with it, and high priority moves it to the top of the queue.
It gets done
The technician ticks the checklist off task by task, adds the parts used by name, part number or serial number, records external costs and completes with a summary and the files the job requires.
It gets checked
A supervisor checks the event or returns it to New with a comment. Checked is final, with a printable protocol, the full history and what the job cost: labour, parts, downtime and external costs.
See Events running on your own plant.
Ask for a demo with your own devices, parts and jobs.