End-to-end workflows

How work moves through Maintenance from start to finish, who does each step and what the system does in response.

On this page (10)

Breakdown: request to closed job with parts, labour and downtime

Who: Requester R (request.create), Manager M (role Maintenance manager), Technician T (role Maintenance technician, linked employee)

#What the person doesWhat the system does
1R: Report Issue on asset CHL-001, type Breakdown, priority UrgentRequest MR-... New; asset status Breakdown; Assets Down +1
2M: open the request, Review, ApproveStatus Approved; decided by M
3M: Create Work Order, technician TWO-... Draft with T; T's bell shows 'WO-... assigned to you'; request Work Order Created
4T: My Work > Start WorkIn Progress; labour timer for T; asset Under Maintenance; the breakdown's running downtime (or a new unplanned one) linked to the job
5M (or T with parts.issue): Parts tab: Add Part 2 x V-belt, IssueInventory transfer done, stock -2, part cost in ledger, journal Dr 5200 / Cr 1200
6T: Complete with failure code MECH, cause, signatureCompleted; labour and downtime closed and costed; asset Active
7M: CloseClosed; request MR-... Closed automatically; costs final (Add Cost refused)

Request turned down

Who: Requester R, Approver M

#What the person doesWhat the system does
1R: Report Issue with no assetRequest New
2M: ApproveRefused 'Say which asset it is about before approving it.'
3M: Reject with reason 'Duplicate'Status Rejected; decision note kept
4M: CloseStatus Closed; no work order exists
5R: try to edit the request (API PUT)Refused 'A request is changed only before it is decided.'

Calendar preventive plan generates, runs and moves on

Who: Planner P (plan.edit, workorder.create), Technician T

#What the person doesWhat the system does
1P: New Plan 'Quarterly chiller service', every 3 Months, First Due = today + 5 days, lead 7, default technician T, checklist 3 lines, 2 assetsPlan MP-...; both assets due in 5 days; Preventive Due tile counts them
2P: Preventive Maintenance > Generate Due Work OrdersTwo WOs Assigned to T, planned start on the due date 08:00, 3 tasks each, plan snapshot
3P: Generate again'Nothing is due.' - no duplicates
4T: Start one job, tick the 3 tasks Done, CompleteCompleted; asset last done = today; next due = today + 3 months
5P: open the plan > Assets tabCompleted asset shows the new next due and no open job; the other still has its open job
6P: edit the plan checklist (API) and open the first jobThe job keeps its original checklist and plan revision

Meter-based preventive maintenance

Who: Planner P, Technician T

#What the person doesWhat the system does
1P: Add Meter Operating Hours on GEN-001; Log Reading 12000Meter at 12000 h
2P: New Plan, trigger Runtime, meter Operating Hours, every 500, asset GEN-001Next due meter 12500
3T: Log Reading 12400Nothing generated; Due list shows 12400 / 12500 h (within 90 %)
4T: Log Reading 12510A work order is generated at once with due meter 12500
5T: Start and Complete it with Meter Reading at Completion 12520Reading recorded (source Work Order); next due meter 13020
6T: Log Reading 12000 without resetRefused 'This counter was at 12520 h. A smaller reading is recorded as a meter reset.'

Failed inspection raises a request that becomes a job

Who: Inspector I (maintenance.edit), Manager M

#What the person doesWhat the system does
1I: New Inspection, template Safety Inspection, asset CHL-001INS-... planned with 3 checks
2I: answer Pass, Fail ('guard missing'), Pass; Complete InspectionResult FAIL; one request 'Failed inspection INS-...' priority high, source Inspection
3M: open the request from the Request smart button; Approve; Create Work OrderWO-... linked to the request
4M: Complete and Close the jobRequest Closed
5Admin: switch off 'A failed inspection raises a maintenance request'; repeat with another failureResult FAIL but no request is raised

Condition monitoring: sensor reading to request

Who: Configurator C (configure), Integration (maintenance.edit API user), Manager M

#What the person doesWhat the system does
1C: Add Meter Temperature on CHL-001; Alert Rule 'Temperature > 45', raise request, urgentRule active
2C: IoT Sensors > New TS-CHL-01 on CHL-001 linked to the Temperature meterSensor active
3Integration: POST sensors/ingest {sensor: 'TS-CHL-01', value: 47} three timesThree readings (source IoT); one open alert; one request 'Condition alert: ...' priority urgent, source IoT
4M: Meters > Acknowledge the alertAlert acknowledged
5Integration: send 48A new alert and a new request (the previous alert is no longer open)

Parts shortage to purchase and back to work

Who: Technician T, Storekeeper / Manager M, Buyer B

#What the person doesWhat the system does
1M: on an In Progress job Add Part 5 x filter with only 3 freeReserved 3, short 2
2M: Request Shortage, vendor VDraft purchase document (RFQ) for 2 filters, VAT 5 %; job Waiting Parts; labour stopped
3B: confirm and receive the purchase in Purchase / InventoryStock +2 (Inventory's own flow)
4T: Resume; M: Reserve, then Issue all 5Issued 5 at stock cost; journal Dr 5200 / Cr 1200
5T: Complete; M: Return Unused 1Reverse transfer at the issue unit cost; part cost reduced
6M: Close; try Return Unused again (API)Refused 'A closed work order's parts are final. Reopen it first.'

Outside vendor: purchase order, AMC visit and warranty claim

Who: Manager M (configure, cost.view)

#What the person doesWhat the system does
1M: New Contract AMC with vendor V, 2026-01-01..2026-12-31, 4 visits, asset CHL-001AMC-...; visits 0 / 4
2M: on a job Create Purchase Order to V, 'Rewind motor' 1 x 1200Purchase order in Purchase; job Waiting Vendor
3M: Vendors > Record Visit with the contract, Done, cost 800, asset CHL-001Within Contract; no cost booked; visits 1 / 4
4M: Record Visit without contract, Done, cost 800800.00 AED vendor cost on the asset
5M: Asset 360 > Add Warranty (valid); Create Warranty Claim 2400 linked to the job (API work_order_id)WCL-... Draft; job shows the claim; asset Warranty card shows the reference

Calibration fails and is redone

Who: Quality user Q (maintenance.calibration)

#What the person doesWhat the system does
1Q: Asset 360 > More > Record Calibration, Fail, measured 0.09 mm vs ±0.05CAL-...; register Failed; next calibration = today; request 'Calibration failed CAL-...' high
2Q: Calibration register filter FailedAsset listed
3Q: Record Calibration again, Pass, interval 180Register Valid; next = today + 180 days
4Q: open the calendar 6 months ahead'Calibration due <code>' event on the next date

Two-person control: approval, completion and close

Who: Planner A (workorder.create), Approver B (request.approve), Technician T, Manager C (workorder.close)

#What the person doesWhat the system does
1Admin: Maintenance Settings > Work orders need approval ONSaved
2A: New Work Order (Draft); try Start / ScheduleRefused 'Approve the work order before starting it.' / '...scheduling it.'
3B: ApproveApproved
4A or B: Assign T; T: Start, CompleteCompleted by T
5T: try CloseNot offered; API 'You do not have permission for this action.' (technician has no workorder.close)
6C: CloseClosed by C