Work orders and faults
From a fault report to an approved outcome
What it does
Four stops in the service flow
Faults are raised from the field
A technician reports what they see during a reading, with a photo. The report is attached to the meter record, so which project and which unit it belongs to is never in doubt.
- Photo-backed fault report
- Linked to meter and unit
- Reporting user and timestamp
Work orders pass through approval
If a fault turns into a job, a work order is opened. It moves through assigned, started, awaiting approval and approved.
- Assigned → started → awaiting approval → approved
- Responsible user and due date
- Full history of status changes
No approval, no inventory change
Operations that affect the meter identity — a replacement, for example — are written to the meter record only after approval. The inventory is never corrupted by unapproved field work.
- Brand, serial number and first reading date preserved
- Replacement kept in history
- Approval rights tied to role
Connected to reading
If an unread meter is suspected of being faulty, the report is opened from the same screen. On the billing side that unit goes to estimation, so the calculation never stalls.
- Unread → fault report
- Estimation and averaging in billing
- Period close does not wait
Flow
From report to closure
A fault is noticed in the field or in modem monitoring.
A photo-backed fault report is opened and linked to the meter record.
The office reviews it and, if needed, opens a work order and assigns it.
The technician starts the job and submits it for approval when done.
An authorised user approves; any change affecting the meter identity is written at that moment.
The fault is closed and stays traceable in the history.
At a glance
- Fault source
- Field app, panel or modem monitoring
- Work order states
- Assigned · started · awaiting approval · approved
- Evidence
- Photo, timestamp, reporting user
- Inventory effect
- Written to the meter record only after approval