Line patrol and defect logging
Patrol crews describe a defect by voice and get the right code and priority to log.
Energy and utilities · Field crews
Raise a work order
With tools connected, engineers create a work order after confirming details.
- Tablet
- Online for actions
Tablet assistantOn this device · connects to act
Create a work order for transformer T12.
Drafted with location and photos. Approve to send to dispatch.
Set it as urgent.
Priority set to urgent. Approve to send, or edit the description first.
There is no signal here. Will it send?
It is queued on the tablet and will send to dispatch when you reach coverage.
The problem
Raising a work order means filling long forms in the work management system, usually back at the office. Details are forgotten or entered wrong. Repairs start later than they should.
Who uses it
Field engineers and supervisors who raise maintenance and repair work orders.
What you train it on
- Work order templates
- Asset codes
- Job type list
- Work management connection
How it works on the device
- 1
Drafted on the device
The engineer describes the job by voice. The assistant fills the form fields from your templates.
- 2
Asks before it acts
The engineer reviews the draft and approves it.
- 3
Sent when connected
With your work management tool connected, the order goes to dispatch. Offline, it waits in a visible queue.
Why it runs on the device
Orders raised at the asset
Details are captured while the engineer is looking at the problem.
Approval before sending
Nothing is sent until the engineer approves.
Offline queue
Drafts wait safely and send when the connection returns.
Questions
Sending orders does. Drafting and answering questions work offline.
No. Every order waits for the engineer to approve.
Yes. Who drafted, approved and sent each order is logged.
Related use cases
All use casesPut AI where your work happens.
Pick one team and one use case. We’ll have it running on your own devices in weeks.