A smartphone can bring assignments and information close to the asset and collect outcomes in the same context. Its value depends on the process: working without a network requires preparation, and a record saved on the phone is not yet an outcome available and verified in the office.
Information available on site
Section titled “Information available on site”
A mobile app (opens in a new tab) can reduce the need to copy reports or search for instructions in separate stores. Technicians need to understand the task, asset and relevant references. Photographs and collected data are useful when they remain connected to the correct assignment.
Preparation includes asset identity, readable instructions and responsibility for unexpected situations. A tool cannot repair an ambiguous procedure or make a check safe merely by displaying it on a phone. The relationship between office and field explains which information must pass between the two environments.
Three moments of offline work
Section titled “Three moments of offline work”Prepare. Necessary information and documents need to be available before entering an area without coverage. Not every item is necessarily downloaded and not every action has an offline path. Trial the actual case, including what happens when an assignment changes while the phone is disconnected.
Record. The device retains supported operations. Operators should distinguish performing work from transmitting its records: a remote supervisor may still see the earlier situation. Urgent cases require an organizational alternative when waiting is not possible.
Synchronize and verify. When connectivity returns, local records must be sent and processing outcomes checked. Successful transfer does not automatically demonstrate that every operation was accepted without errors. Before deleting data or changing devices, understand how pending records are handled.
The Asset2Work scope
Section titled “The Asset2Work scope”The Asset2Work app includes data preparation, local saving of supported operations and upload of records. Checklist saving distinguishes online submission from local saving. This does not mean that every function works without a network: information, permissions and the adopted process determine the usable case.
Upload and processing verification are separate stages; errors require attention. Procedures are in Work offline and synchronize, reserved documentation requiring sign-in. This article concerns the organizational principle rather than a sequence of application commands.
Identity and shared devices
Section titled “Identity and shared devices”The device and the person using it are different identities. A shared phone needs clarity about who is active and who owns the recorded outcomes, rather than undifferentiated credentials. The smartphone’s unlock PIN does not replace identification within the application.
Asset2Work has an operator identity with associated permissions; its tag-based login path may also request PIN confirmation. This should not be treated as a universal rule for every login. Actual arrangements need defining and testing for the devices and people included in the project.
An example and the limits to test
Section titled “An example and the limits to test”At the imaginary Aurora centre, a technician prepares the job before entering a basement plant room. On site, the asset is identified and available checks are recorded; back in a covered area, records are uploaded and outcomes checked. If a record fails, the information handover to the supervisor cannot be assumed complete.
Assessment includes battery life, readability, use with gloves, device protection and recovery after interruptions. Indoor positioning is a separate subject: knowing a location demonstrates neither network availability nor completion of an inspection.
Further reading
Section titled “Further reading”Checklists and traceability explores outcome quality. GiPStech introduces the field operations app context (opens in a new tab). An initial project should validate the whole handover from assignment through data verification, including exceptions.