Evaluate device management over the whole life of a fleet, not only on the day it goes live. A sound evaluation pilots real workflows on your own devices, makes clear who owns and supports each function, and plans how devices move in and out. Otukan runs that evaluation with you. Acceptance criteria are agreed before the pilot, ownership and partner scope are written down, and migration and exit are planned per platform. The pages in this collection help you prepare each part, for Android and Apple phones and tablets.
Fleet scope
Pilot devices should represent the fleet: each model, OS version and ownership mode you run, on Android and on Apple devices alike. A pilot limited to the newest phones hides the problems older hardware brings. Otukan chooses the pilot set with you and agrees the acceptance criteria for each device group before the first enrolment.
Operating model
Before signing, you should know who holds policy authority, who builds each function, who supports it and who you call when a device fails. Otukan puts this in writing: the functions it builds and supports, the ones a partner delivers and how each connects to your directory and existing tools.
| Page | What it helps you prepare |
|---|---|
| Ownership and partner scope | Who builds, operates and supports each function |
| Support and lifecycle | How support runs and how the service is maintained |
| MDM migration | How devices move from your current service |
| MDM requirements checklist | The questions to answer before you decide |
Lifecycle
Evaluation continues after go-live. Otukan reviews new OS releases, platform credential renewals and device end-of-support dates with you, and keeps the exit plan agreed at the start current as the fleet changes.