To evaluate management for dedicated operational devices, start from the workflow, not the device list. Confirm that the devices are owned by the organisation, that each platform uses the enrolment mode built for single-purpose use, that operations and IT hold separate, written authority, and that provisioning, swaps, resets and retirement work without a site visit. Otukan manages company-owned Android devices through Android Enterprise and single-purpose iPads through Apple’s device management framework, each on its own terms. It covers the handhelds, rugged tablets and scanners that crews share across shifts. Personally owned phones are a separate case with separate rules.
Fleet scope
A dedicated operational device serves a task rather than a person. It is bought by the organisation, often shared between workers, and judged by one test: is it ready when the shift starts?
Ownership
Ownership decides what management may do. Because the organisation owns these devices, it can lock them to a task, reset them between users and recover them remotely. Devices that staff own personally cannot carry those powers, so Otukan keeps them out of an operational fleet and manages any work use on them through a separated work area.
Enrolment mode and platform
| Usage pattern | Android (Android Enterprise) | iPadOS (Apple device management) |
|---|---|---|
| Shared by a crew, one task | Dedicated device, locked to an approved app | Supervised iPad with Single App Mode |
| Shared by a crew, several apps | Dedicated device with a short app list | Supervised iPad, or Shared iPad where applicable |
| Assigned to one worker, work only | Fully managed device | Supervised iPad assigned to the worker |
The columns are not equivalents. Each platform sets its own limits on what an administrator can lock, see and reset. Otukan configures each platform separately and confirms behaviour on the models and OS versions your fleet actually runs.
Operating model
Operational fleets fail when nobody knows who may change what. Otukan separates three kinds of authority.
| Authority | Typically held by | Examples |
|---|---|---|
| What the device must do | Operations | Which apps a site needs, shift times, maintenance windows |
| What the device may do | IT and security | Restrictions, sign-in rules, update approval |
| Hands-on service | IT, or a service partner under a limited role | Repairs, swaps, re-provisioning |
Each authority maps to a console role with its own scope, and every change is recorded.
Integrations
Shared devices depend on the organisation’s identity service for worker sign-in and on the operational app’s backend for data. Otukan applies the device policy; sign-in is checked against your identity service; work data stays in the operational backend rather than on the handset. That split keeps work data off the handset, so a lost device carries little of it.
Owned versus partner functions
Otukan runs the management service. Hardware supply, repair depots and connectivity usually come from partners. Otukan records which functions each partner performs and gives repair staff only the rights their task needs, such as moving a returned device back into the spare pool.
Lifecycle
Take a parcel delivery round as the named workflow. Each stage below is confirmed on physical devices during the pilot.
- Provisioning. A new handheld is switched on at the depot, joins management during setup and arrives in its depot’s group with the delivery app and scanner utility.
- Daily use. A driver signs in at shift start. At handover or after inactivity, the session closes and the next driver signs in.
- Change. A new version of the delivery app reaches the depot’s group overnight, inside its maintenance window.
- Recovery. A cracked device is swapped for a spare. The spare is moved into the depot group, receives its policy and apps, and the broken unit goes to repair.
- Offboarding. A device at the end of its service is removed from its group, wiped and released from its enrolment registration before it leaves the organisation.
Every stage leaves a record, so operations can see which devices are in service, which wait in the spare pool and which are at repair on any given day. The same five stages apply to a warehouse scanner or an inspection tablet; only the apps, windows and swap process change.
For the mechanics of task lock, see Android kiosk management. Enrolment paths are covered on MDM device enrollment. Further fleet scenarios are on use cases.