Read the task
Clear inspection points and checks on the 2.4-inch employee device.
Case study
Field tasks across sites and shifts.
A project for a 10,000-person oil company: a 2.4-inch field device connected to team and site workflows.
Project illustration · Organisational scale does not describe simultaneous connections.
Start with the site.
Define the team, approved work area and existing systems before deciding how the device fits.
The customer and the initial idea
What should each level of the organisation see?
This project involves a Saudi oil company managing an organisation of around 10,000 people across sites, shifts and work teams. Group managers need an overall view; site managers need to understand today’s work; team leaders need to know who can take the next task. Employees need clear instructions and a usable way to record what happened.
The customer is considering a workforce management system, with wrist devices as one employee interface. Site membership, current assignments, completion and responsibility for exceptions need to connect. Buying devices alone would not provide that workflow: the backend and the people managing it are part of the product definition.
TEAM LEADER
Today’s inspectionInspection teamAssigned
Reported issueReview
Assign & follow upInterface concept
Assign and follow up
Team leaders assign work and follow exceptions through the shift.
Keep a clear record
Agree the record needed for the task. This image shows an already-saved photograph.
SITE & GROUP
Task overviewSites & shiftsRoles
Field recordsAccess
Connect existing systemsInterface concept
Connect the existing system
Site and group views bring task status and access rules together.
One workflow. Three levels of use.
Employee · 2.4-inch device
View assigned shift tasks, inspection points and checks. Record results or flag an exception, with a clear indication of whether the record has been submitted.
Team leader · Assign and follow up
Assign work by role and shift, review open tasks and exceptions, arrange handovers and manage shift changes. The management interface and terminal are selected for the project.
Site and group · Summaries and access
Review task status by site and organisation, manage roles and device allocation, and control data access. Interfaces to existing staff, maintenance or operations systems are defined together.
We would work with group, site and team representatives on roles, shifts, permissions and task handovers. Together, we would decide what comes from existing systems, what the backend manages and what employees need on the small screen. Devices, connections and interfaces must be defined together.
Together, we would define employee, team and site/group views. That includes the source of staff and role information, task assignment, device issuing, record submission and access rules. We would assess the T9, site connectivity and existing system interfaces together. The employee screen stays focused; management interfaces handle assignment, summaries and follow-up.
How the task would work
Receive the shift’s tasks
A team leader assigns work; the employee sees the route, next point and required checks.
Complete the check or flag an issue
Review each item on site, record the result and route issues to the agreed responsible person.
Follow up and consolidate
Teams confirm tasks and handovers. Site and group views show authorised summaries, while pending uploads remain clearly identified.
Define suitability before development.
A non-hazardous area still requires site permission. Hazardous-area suitability and approvals need separate assessment; explosion protection or gas detection must not be assumed.
A first team, then further sites
The first step is to confirm site acceptance. A pilot could then start with one team and one inspection route in a non-hazardous area where the selected equipment is permitted. Within the agreed scope, trial terminals, a team interface and system connections would let all three levels try assignment, execution, exception handling and shift handover.
The trial should expose issues with wearing, connectivity, task state and handovers before further teams or sites join. Around 10,000 describes the organisation; active connections, data frequency and peak load require separate definition and validation. Issuing, spares, charging, training and support also need a site-by-site plan.
The first pilot should show whether employees understand their tasks, team leaders can follow up exceptions and the backend receives complete records. Site acceptance, usability and workflow findings come before further teams and facilities.
What the first team pilot needs.
Employee devices for an approved area
Assess the terminal and mount against site acceptance requirements, then try reading, glove use, charging and device issuing through a shift.
A complete task and management workflow
Connect employee, team and backend views within the agreed scope, with clear responsibility for assignments, exceptions and records.
A basis for the next site
Document roles, interfaces, device configuration, training and pilot issues before agreeing further terminals and rollout.
Capacity, records and mounting
Define the capacity requirement
Workforce size, device count and concurrent connections are different requirements. Backend capacity, network coverage and data frequency must be validated for the agreed scope.
Keep people, tasks and records aligned
Agree sites, teams, permissions and device handovers. Offline use, shift changes and reassignment must preserve ownership and the next action.
What does your team need to do on site?
Talk to usFunctions, suitability and delivery scope are defined and validated for each project.