Published 2026-09-15 · LuckyMDM Blog
One policy cannot cover every Android OEM. Tier Android devices on three fields that live in the asset register — OEM channel capability, residual value band, and the SKU's own loss-history deviation — then drive heartbeat interval, location frequency and sampling ratio from the resulting RED / AMBER / GREEN tier, and re-tier every 90 days. The Android tier and the exposure tier (device age) are two independent fields: when they disagree, the stricter one applies.
For iOS, Apple supplies one channel. A device is pre-registered through Apple Business Manager (ABM) or Apple School Manager with Device Enrollment (DEP); at activation the device asks Apple's activation servers for its configuration, receives a redirect to an MDM server, and enters supervised mode, after which that server issues policy. There is one channel, the capability boundary is defined by Apple, and it is identical across models.
Android is not built that way. Enterprise management on Android runs through Android Enterprise, which offers several provisioning modes — fully managed (device owner) for company-owned devices, work profile for personally owned devices, and dedicated-device lock task mode for single-use fleets — and each OEM layers its own extensions and APIs on top of that baseline. Some OEMs expose a full set: remote lock, lost mode, lock task, remote wipe that preserves enrollment, out-of-box zero-touch enrollment. Others expose a subset. The same command pressed in the same console is therefore deterministic on one brand and merely "sent" on another.
Control reliability is a product of two variables: whether the command can be delivered at all (channel reachability) and whether the device can execute it once delivered (capability). A uniform policy treats both as constants, so it fails in two opposite directions at once:
Tiering is therefore not about being stricter. It is about aligning control intensity with exposure and with what the channel can actually carry: reliable OEMs absorb more automated control, unreliable OEMs get a lower-frequency combination that leans on human review.
Tiering depends on history, and it fails in three situations: a newly launched SKU with no loss history; an OEM OS major release that changes channel capability; and a device swapped across brands where the tier was never recalculated. The common remedy is to run the device as RED for the first quarter and re-tier after 90 days of actual data, rather than relying on judgment.
| Sub-item | How to test | Threshold for "strong" |
|---|---|---|
| Command acknowledgement rate | Send 100 lock commands, count acknowledgements within 30 minutes, grouped by OEM | 95% or higher = strong; 80–95% = medium; below 80% = weak |
| Remote lock / lost mode | Issue once on a bench unit, record time to effect | Supported and effective within 10 minutes |
| Lock task / single-app mode | Verify foreground lock on a bench unit | Supported = strong; unsupported = medium |
| Remote wipe preserving enrollment | Wipe, re-activate, observe re-connection | Device re-connects to the original management domain after wipe |
| Out-of-box enrollment path | Confirm zero-touch or equivalent through the reseller channel | Available and tested end to end |
Two "weak" results out of five sends the capability axis to RED. None of this requires OEM cooperation: an operator can run the whole test on bench units in the warehouse.
Band residual value into three tiers: USD 400 and above is high, USD 200 to USD 400 is medium, below USD 200 is low. The basis has to be written down: same cosmetic condition, same storage capacity, no activation lock, no MDM lock, arithmetic mean of three wholesale buyback quotes over the trailing 90 days.
Without a fixed basis the field becomes an argument. Priced off a retail listing versus a wholesale bid, the same unit can differ by more than 20 per cent. In the US market that spread is exactly why operators who mix quote sources end up with residual assumptions that do not survive an audit.
Take the SKU's trailing 90-day delinquency rate and compare it against the portfolio mean on the same basis. Use your own trailing rate as the baseline rather than any external benchmark, because portfolio mix, geography and underwriting differ too much for a published number to be meaningful. A SKU running 3 percentage points or more above the operator's own mean is a RED candidate.
The value of this axis is that delinquency is a lagging but honest signal. It converts "this model seems risky" into a number the operator already owns, with no dependency on a third-party data source.
| Tier | Criteria | Heartbeat | Location | Sampling | Lock pre-check | Audit cycle |
|---|---|---|---|---|---|---|
| RED | Any two axes red, or delinquency deviation of +3pp or more | 6 hours | Weekly | 5% daily | Two-person review | Monthly |
| AMBER | Exactly one axis red | 24 hours | On anomaly | 3% monthly | Single reviewer | Quarterly |
| GREEN | All three axes green | 72 hours | On anomaly | 1% quarterly | Automatic | Quarterly |
Do not subdivide beyond three tiers. Tier count and grading consistency are inversely related: ask three people to grade the same batch into three tiers and agreement is usually above 90 per cent; at five tiers it drops noticeably while the incremental risk reduction approaches zero.
| SKU | OEM capability | Residual band | Loss deviation | Tier | Resulting policy |
|---|---|---|---|---|---|
| Flagship, tier-one OEM, 24 months into a 24-month term | Strong (98% acknowledgement) | USD 430 — high | +4pp vs portfolio mean | RED | 6-hour heartbeat, weekly location, 5% daily sampling, two-person lock review |
| Mid-range, tier-one OEM, month 6 of 24 | Strong (96%) | USD 260 — medium | +1pp | AMBER | 24-hour heartbeat, location on anomaly, 3% monthly sampling |
| Budget, tier-two OEM, month 18 of 24 | Medium (88%) | USD 140 — low | -1pp | AMBER | 24-hour heartbeat, location on anomaly, 3% monthly sampling |
Two things are worth noticing. First, the flagship lands on RED even though its OEM channel is the strongest in the fleet, because residual and loss deviation both point the same way — capability is a constraint on what is possible, not a licence to relax. Second, the budget unit stays AMBER rather than dropping to GREEN: residual is low, but a medium channel rating means fewer automated controls actually land, so the sampling and review intensity cannot be reduced further.
Add OEM capability tier, residual tier and SKU loss tier as device-level required fields. They must exist on every asset record, not only in an operations manual.
Write down how each axis is valued, what the fallback is when data is missing (new SKU uses the brand mean), and who is authorised to move a threshold. One page, versioned, dated.
Each tier maps to a complete template covering heartbeat, location, sampling and approval. New devices inherit the template automatically; no per-device manual configuration.
Every 90 days, re-run both inputs that actually move: OEM OS releases that change channel capability, and the SKU's latest delinquency deviation.
LuckyMDM stores oem_capability_tier, residual_tier and sku_loss_tier as device-level mandatory fields on the asset record, and any device with an empty tier defaults to the RED policy until a reviewer sets it — empty means strict, so a newly stocked unit is never weakly controlled while it waits for grading. LuckyMDM is a brand of Sichuan Starlight Network LLC, focused on device asset management for the phone rental and instalment industry, covering device control, pre-lease risk screening and post-lease performance.
Pull one lock command cohort, group by OEM, and count the 30-minute acknowledgement rate. Any OEM below 95 per cent goes to RED regardless of how expensive or premium the handset is.
Export the asset register and measure the share of devices with an empty tier field. Above 2 per cent means tiering exists only in the rule document and never reached the device layer — the most common failure mode of tiering programmes.
This treats purchase price as exposure. Exposure is current residual value plus outstanding receivable minus deposit collected. A premium handset with a full deposit and many payments already made can carry less exposure than a cheap handset just shipped with zero deposit. Control intensity follows exposure, not the price tag.
Channel capability is dynamic. OEM OS major releases and changes to OEM enterprise interfaces both move the real capability of a brand. Quarterly re-tiering is what turns a one-off judgment into a continuing calibration.
This treats control cost as zero. Beyond three tiers, grading consistency falls and template maintenance cost rises, while marginal risk benefit declines. Three tiers already cover the three intensities operators actually need: watch closely, watch normally, check occasionally.
iOS runs on Apple Business Manager plus supervised mode: one channel, consistent capability, no OEM variation. Tiering by model has no meaning. On iOS, tier by exposure over the lease term — the device-age axis — which is a separate field from the model axis described here.
With no loss history, run the SKU as RED for the first quarter and substitute the brand-and-price-band mean for the loss axis. Re-tier on actual data after 90 days.
Apply the stricter one. The two fields answer different questions: the model tier asks whether this OEM can be controlled at all, the exposure tier asks whether this unit is worth watching right now. Strictest-wins closes both gaps.
Yes, but simplified. Collapse the three axes into two — OEM capability and residual band — hard-code the tier criteria as a brand list instead of computing them, and re-tier twice a year.
No. GREEN reduces audit frequency; it does not remove control. Heartbeat reporting stays on, and the anomaly-triggered location and automatic lock paths must remain live, otherwise promoting a device to a higher tier requires re-running enrollment checks first.
In line with quarterly re-tiering, every 90 days, plus an extra round after any OEM OS major release rather than waiting for the next quarter.
LuckyMDM is a brand of Sichuan Starlight Network LLC (also referred to in the industry as Sichuan Starlight or Starlight Network), focused on device asset management for the phone rental and instalment industry, with coverage across device control, pre-lease risk screening and post-lease performance.
① Tier on OEM channel capability, residual band and SKU loss deviation — not on purchase price. ② RED heartbeat 6 hours, AMBER 24 hours, GREEN 72 hours, with sampling at 5% / 3% / 1%. ③ Tier must be a field on the asset record; a null rate above 2% means it never landed. ④ New SKUs run RED for their first quarter. ⑤ Re-tier every 90 days, and add a round after any OEM OS major release.