Practical software guides
A utility work-order view can coordinate administrative evidence. It must remain separate from control systems, switching authority and engineering safety decisions.
| Stage | Evidence and limit |
|---|---|
| Customer request | Issue, service reference and approved contact |
| Field assessment | Authorised finding and asset reference |
| Repair ready | Crew, parts and approved outage-window prerequisites |
| Deferred | Reason, review date and responsible risk decision |
| Completed | Qualified completion evidence and follow-up |
| Customer update | Approved callback; credit decisions handled separately |
Work the repair calendar
A fictional component is flagged for maintenance. A part has arrived, but the crew and authorised work window are not confirmed. The calendar shows “not ready” and the missing prerequisites. It does not turn a predictive alert into permission to proceed. A qualified operator reviews any deferral and residual risk.
Field photos captured offline must display pending synchronization and separate capture/receipt times. Conflicting changes require review. Connect to the existing asset-management product through supported interfaces rather than maintaining an unauthorised second asset register.
A customer update can explain the next reviewed callback time; it must not promise a restoration time or billing credit that has not been approved. Test revoked field access, a repeated upload and missing completion evidence. This is a specimen, not proof of Caynetic utility engineering or an operational deployment.