Skip to main content

Service Management use case

Device lifecycle management software

Device lifecycle management follows each laptop, tablet or phone from the request through purchase, setup, repair, refresh and recovery, updating Intune or Jamf, the asset record and the service desk at each step. Fairfax County Public Schools used Kinetic to cut device distribution from two weeks to three days.

Book a working session

Fairfax County Public Schools Device distribution went from two weeks to three days across 200+ schools and offices. Read the FCPS case study

One device, from request to recovery

  1. Experience layer

    A portal where employees request, replace or return devices and see where each request stands, and an asset view of who holds what.

  2. Workflow layer

    Standard devices auto-approve and go to procurement. Arrival triggers enrollment and asset updates, refresh dates open replacement requests, and offboarding opens a recovery task that stays open until the device is back and wiped.

  3. Integration layer

    Enrolls devices in Intune, Jamf or SCCM, creates orders in Coupa, and keeps the asset record and the ServiceNow CI updated with owner, serial number and warranty date at every step.

    • Microsoft Intune
    • Jamf
    • Microsoft SCCM
    • ServiceNow
    • Coupa

AI in device lifecycle management

AI sorts repair requests and spots devices due for refresh or still out after a departure. Write-offs and non-standard devices are approved by people.

What AI does

  • Classifies repair and replacement requests
  • Flags devices due for refresh or not yet returned
  • Summarizes fleet status for asset managers

Decided by people, not by AI

  • Non-standard device requests
  • Early replacements
  • Write-offs for lost or unreturned devices

Three systems, three answers

Ask where a particular laptop is and you can get three answers. The asset system lists it under an employee who left in the spring. Intune shows it checked in last week from a different user. The service desk has a CI for it with neither name. Nobody lied; each system was updated by a different team at a different step, and nothing ties the steps together.

That drift is what fails audits, and it is what leaves a device with sensitive data on it unaccounted for.

The lifecycle as one workflow

Request. An employee picks a device from a catalog of approved models for their role. Standard choices go straight through. A non-standard model goes to the manager, and anything over your cost threshold to finance.

Purchase or stock. Kinetic either reserves a device from stock or creates the order in Coupa or your purchasing system, then tells the employee when to expect it.

Setup. When the device is received, the workflow enrolls it in Intune, Jamf or SCCM with the right baseline, writes the serial number, owner and warranty date to the asset record, and links it to the employee in ServiceNow.

Repair and refresh. Break-fix requests come through the same portal and can issue a loaner. As warranty and refresh dates approach, the workflow opens a replacement request on its own.

Recovery. When someone leaves or a device is replaced, a return task opens and stays open until the device is checked in. Then the MDM wipe runs and the asset record is marked for redeployment or disposal. Write-offs for lost devices need a person’s approval.

At each step every record gets the same update, so the three answers become one.

Fairfax County Public Schools

FCPS supports more than 200 schools and facilities. Device distribution used to take up to two weeks, with requests arriving by phone, email or paper depending on the school. Kinetic gave the district one catalog in front of its existing BMC Remedy system and routed approvals automatically. Distribution now takes three days. Read the FCPS case study.

Devices are usually the second thing teams connect after software provisioning, because the request portal and the approval rules are already in place.

Results at Fairfax County Public Schools

Source: Fairfax County Public Schools case study

Device distribution time
2 weeks → 3 days
Schools and facilities served
200+

What you can build next

The device catalog and its approvals are easy to extend to the software that runs on those devices.

Questions about device lifecycle management

Answered by Kinetic Data. Last updated .

  • Do we need a separate asset management system?

    No. Kinetic works with the asset records you already keep, whether that is a dedicated asset tool or the CMDB in your service desk, and updates them as devices move. It does not hold a competing inventory of its own.

  • Can standard devices skip approval?

    Yes. You decide which models and configurations are pre-approved for which roles. Those go straight to procurement or to stock, and anything else routes to the manager and, above a cost threshold, to finance.

  • How does recovery work for remote employees?

    The recovery task can include a prepaid return label or a drop-off location, and it stays open until the device is received. Once it is checked in, the workflow issues the remote wipe through your MDM and marks the asset ready for redeployment or disposal.

  • Which MDM and asset tools does it work with?

    Intune, Jamf and SCCM for enrollment and wipes, and your asset records wherever they live, whether a dedicated tool or the ServiceNow CMDB. Purchasing goes to Coupa or whatever procurement system you use.

Bring one process. Leave with a plan to build it.

Two hours with our team, at no cost. Bring one process that crosses your systems. We map it with you, show what Kinetic would build, and send you a written plan afterward.

Book a working session