The work order life cycle, from qualification to validation.
How a request becomes a ticket, gets a place in a technician's schedule, is documented in the field and is then validated.
Ticket statuses, from qualification to closure.
A request becomes a ticket, which is qualified, scheduled, carried out and then validated. Every status change is kept with its date.
Qualification
The request is reviewed and can move forward.
Scheduling
The work order gets a date and a technician, then is synchronized with the technician's mobile app.
Work
The technician starts, pauses if needed, documents and completes the work.
Validation and closure
The completed work is validated, then the ticket is closed.
Cancellation
A ticket cancelled before it is started involved no work. If it is cancelled after it was started, the work still counts as carried out.
"Completed" and "closed" are two separate steps: the end of the technician's work, then the validation of the ticket.
A schedule that takes existing commitments into account.
When a work order is assigned to a technician, MatxFlow checks their time slots. If the requested time is taken, it looks for the next slot long enough for the whole work order.
No overlaps
A technician cannot be assigned to two active work orders at the same time.
Duration preserved
In case of conflict, the start is moved with a five-minute buffer; the estimated duration is never shortened.
Prior checks
The date cannot be in the past; the technician must be active and, where required, assigned to the relevant workshop.
Traceable changes
Every scheduling change is recorded, with the state of the ticket before and after.
What the technician records during the work.
The technician documents the work from the mobile app, using the form set up for that type of work order.
Dynamic forms
Text, number, choice, date and time, photo, file, signature. An answer can reveal additional fields, for example when an anomaly is found.
Working and break time
A work order started at 10:00, paused from 10:10 to 10:25 and completed at 10:35 counts 20 minutes of work, 15 minutes of break and 35 minutes elapsed.
Consumables
The consumables used and their quantities are recorded on the work order.
Downtime and return to service
Equipment downtime is linked to the ticket, then its return to service is recorded.
See a work order from start to closure.
In the demo: scheduling, recording in the mobile app, the work order form, then validation and closure.