These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Machine Maintenance (CMMS)
- Features
- Maintenance execution
Maintenance execution
Record the repair, send its evidence for inspection and retain the accepted service outcome.
OverviewRecorded Labor Intervals×
Machine Maintenance (CMMS) · Maintenance execution
New
Recorded Labor Intervals
Work logs
| Id | Work order | Technician | Started at | Ended at | Work performed | |
|---|---|---|---|---|---|---|
| IDD-934 | WO-7366 | 13 Oct | 21 Oct | WP-168 | ||
| IDD-592 | WO-3126 | 05 Oct | 10 Oct | WP-430 | ||
| IDD-698 | WO-8365 | 04 Oct | 11 Oct | WP-512 | ||
| IDD-259 | WO-3316 | 03 Oct | 11 Oct | WP-952 | ||
| IDD-285 | WO-9143 | 15 Oct | 24 Oct | WP-547 |
6 of 6 records
IDD-934Work logs · WL-30586
Work orderWO-7366
Started at13 Oct
Ended at21 Oct
Work performedWP-168
What you can do
Keep the repair and its evidence together
The Technician starts a scheduled work order after the safety permit check passes. As the repair proceeds, labor entries record when work started and ended and what was performed. Part usage links the consumed item and quantity to the same work order. The Maintenance Reviewer can then assess the actual work behind the request.
Inspection is a separate decision. A job marked Inspection is waiting for the Maintenance Reviewer to accept the submitted outcome. Acceptance closes the work order, publishes its service history and returns the linked asset to Active. The Maintenance Manager can follow that result back to the repair and use it when reviewing future maintenance.
How the work is organized
- Work capture. The Technician records labor against the assigned work order, with a start, an end and a useful description. Entries should explain the intervention clearly enough for another person to understand the outcome without reconstructing it from a shift conversation.
- Inspection evidence. Submit the completed work through the execution workflow. The Maintenance Reviewer checks the eligible submitted revision and the supporting labor and parts. Preserve a rejection reason with its evidence so that a correction can address the actual concern.
- Service outcome. Accepted work produces a service record tied to the asset and work order. The next due date uses the workflow’s 30-day default interval. The Maintenance Manager reviews that result against the equipment’s preventive plan before the next cycle.
What to agree during setup
Agree what a satisfactory work description contains and when Technicians enter their labor. Check how an interrupted shift is recorded so that an unfinished interval is not mistaken for a completed duration. Decide how the Maintenance Reviewer receives the inspection queue and who covers the decision when the regular reviewer is unavailable.
Use actual maintenance outcomes to agree the inspection standard. Confirm which evidence the reviewer expects for a belt change, a corrective repair or a preventive inspection. Rehearse the 30-day next-due behavior and decide whether that default suits the pilot equipment before the team depends on it for planning.
Check the handoff on an actual case
The Technician completes a conveyor belt replacement under a valid permit. They record the work interval, describe the replacement and link the belt consumption to the work order. After submission, the job appears in the inspection queue. The Maintenance Reviewer opens the evidence and checks that it belongs to the intended job and submitted revision.
Accept the case, then confirm the work order is Closed, the service history points to the correct conveyor and the asset is Active. Check the next due date with the Maintenance Manager. Rehearse an unsatisfactory outcome as well: the reviewer must retain the concern and supporting evidence without granting the accepted service outcome. Use that result to agree the team’s correction handoff.
What your team sees
- Inspection Queue — Work awaiting review of its submitted maintenance evidence.
- Recorded Labor Intervals — Recorded labor intervals and work descriptions for checking the execution timeline.
- Service History by Asset — Accepted service outcomes and their recorded next due dates.
Follow the work through
Use execution and inspection for the full rehearsal and preventive maintenance for the next planned job.
What it keeps track of
Data model- Work orders
- Maintenance work orders from request through planning, execution, inspection and closure.
- Work logs
- Technician labour entries recorded against a work order.
- Part usage
- Parts consumed against work orders.
- Safety permits
- Permits to work with validity intervals and approval status.
- Service history
- Completed service outcomes per asset with next due date.
- Assets
- Asset register of maintainable machines and equipment with location, warranty and status.
- People
- Maintenance staff and reviewers referenced by work orders, logs and permits.
Who uses it
Permissions- Technician
- , Maintenance Reviewer, Maintenance Manager.
- The Technician records the work, the Maintenance Reviewer accepts the outcome, and the Maintenance Manager reviews the service result for the next operating cycle.
Set up Machine Maintenance (CMMS) your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.