The Platform / Domains / Device Lifecycle
XOPS is the control plane for Autonomous Device Operations. You declare the outcome. XOPS maintains the Device and Fulfillment Positions, acts, observes the result, and continues until the estate converges.
No new XOPS agent
Uses telemetry already deployed
Keep or evolve
Preserve your system of record or retire the discovery layer
Weeks
To first production Outcome
The category shift
XOPS is not another HAM platform. It is the autonomous control plane that operates the device estate toward declared outcomes.
You declare the outcome. XOPS continuously maintains the Device and Fulfillment Positions and acts until the estate converges.
Declared outcome
Defines the required end state
Every employee has the right device · Redeploy available inventory before buying · Refresh every device at the optimal economic point · Recover every company asset and preserve chain of custody
Technical Position
Health · Performance · Security · Compliance · Warranty
What condition is the device actually in?
Economic Position
Useful life · Repair cost · Replacement cost · Residual value · CapEx exposure
What is the economically correct decision?
Business Position
Owner · Role · Location · Criticality · Employee impact · Business intent
What does the business require from it?
DEVICE POSITION
Determines the gap between current reality and the declared outcome
Required action
Retain · Repair · Refresh · Relocate · Redeploy · Recover · Retire
FULFILLMENT POSITION
Continuously reconciled from inventory and logistics. Determines the best available path.
Autonomous execution
XOPS acts, observes the result, reconciles the new state, and continues until the outcome is achieved or a governed exception requires human action.
1. Asset records describe. A Position decides.
Traditional HAM records ownership, lifecycle status, and location. XOPS reconciles the broader operating context and determines the required action.
2. Schedules generalize. A Position individualizes.
A calendar says every device should be refreshed at the same age. A Device Position determines the optimal lifecycle for each device.
3. Workflows route. Outcomes converge.
A workflow moves a ticket through predefined steps. XOPS continuously recalculates the gap and adapts the required action and fulfillment path until reality matches the declared outcome.
4. Reports explain. A Position acts.
A lifecycle report tells the team what to investigate. XOPS uses the same Device Position to reserve inventory, initiate recovery, choose fulfillment, update the CMDB, coordinate logistics, and file evidence.
XOPS operates autonomously toward declared outcomes. It continuously observes reality, determines the gap, selects the next action, executes across the connected systems, and verifies the result. Policies, constraints, approvals, and available execution paths govern every action. People engage only when judgment, approval, or physical work is genuinely required.
Autonomy is not the absence of governance. It is governance that operates continuously.
Use the telemetry and systems you already own
XOPS does not need to become another endpoint management, inventory, ITSM, or logistics system. It continuously reconciles evidence already collected across DEX, MDM, EDR, HAM, CMDB, HR, OEM, procurement, inventory, logistics, and carrier platforms into the Device Position.
Keep and coordinate
Keep ServiceNow HAM or another asset repository as the system of record. XOPS maintains the broader Device Position, coordinates action across the surrounding systems, and writes the resulting state and evidence back.
Evolve the architecture
Where the enterprise already has sufficient device, inventory, employee, OEM, and logistics telemetry, XOPS becomes the continuously maintained decision and execution layer without requiring another discovery repository.
No new XOPS agent. No forced replacement. No workflow rebuild.
Smart Refresh™
A fixed-age policy assumes every device has the same useful life. XOPS continuously evaluates health, performance, failure risk, repair-versus-replace economics, employee impact, inventory, budget, and business intent to determine the optimal replacement point for each device.
Extend
Useful life extended where performance and economics support it
Pre-empt
At-risk devices refreshed before they disrupt the employee
Defer
Unnecessary CapEx deferred across each refresh cycle
Reduce
Fewer unnecessary replacements and less e-waste
Replace every device at the right time. Not too late. Not too early.
Change the outcome, not the operating model
Finance declares a new outcome: consume pre-purchased inventory before approving net-new devices. XOPS automatically recalculates every affected Device and Fulfillment Position, rebalances refresh and inventory demand, and changes execution immediately. No workflow redesign, routing project, or operator retraining is required.
Change the outcome. The autonomous operating model adapts.
In production today
Customer outcome
Fortune 100 · Technology
At a Fortune 100 technology enterprise, Device Position replaced fixed-age refresh with performance and condition based decisions across 39 countries, right-sizing each refresh decision against the device’s actual performance, utilization, and compliance posture. Eligible devices remain in service one to two years longer where performance, security, utilization, and business need support it. The value appears in three places that matter to leadership: longer useful life, deferred CapEx, and reduced environmental impact.
+1–2 yrs
Average device life extended
CapEx
Deferred per refresh cycle
ESG ↑
Reduced e-waste & embodied carbon
“We used to staff for the seams: the people who knew which laptop went to which stockroom, which contract ended on which Friday, which executive was in which time zone. XOPS holds that context now. We staff for the work, not the coordination.”
Director of Workplace Tech · Fortune 100 Technology
1.4M+
Devices under continuous Device Position
39
Countries deployed
Weeks
Typical time to first production Outcome
Always-current device management views
The Device Position is not another dashboard. It is the continuously maintained evidence base behind every operational, financial, compliance, inventory, and executive view of the device estate. As device reality changes, every report changes with it.
The Device Position is the maintained operating state. These reports are the stakeholder-specific views published from it.
For ITAM & governance
Continuously maintained evidence of ownership, accountability, lifecycle controls, exceptions, remediation, chain of custody, and audit traceability.
For HAM & CMDB teams
Assigned owner, current location, lifecycle state, device health, warranty, compliance, discrepancies, and required correction.
For security & audit
Recovery status, custody handoffs, remote lock, sanitization and disposal evidence, exceptions, remediation history, and audit traceability.
For finance & procurement
Repair-versus-replace decisions, useful-life extension, forecasted refresh demand, CapEx exposure, avoided purchases, residual value, and budget exceptions.
For device ops & logistics
Available pools, profiles, regions, stockrooms, incoming demand, transfers, shortages, carrier status, and optimal fulfillment paths.
For leadership
Estate health, employee risk, refresh exposure, inventory utilization, recoveries, avoided spend, compliance exceptions, and decisions required for the next operating review.
One evidence base. Six management views. Every action and report starts from the same Device Position.
Illustrative enterprise scenario
What happens after a device event
A workforce event updates the Device Position once. XOPS coordinates every consequence across identity, endpoint management, inventory, logistics, ITSM, procurement, the CMDB, and audit evidence.
Declared outcome
Recover every company device, preserve chain of custody, and redeploy available assets before purchasing another device.
$2,300
Replacement purchase avoided
Recovered
Asset, custody intact
Reconciled
CMDB, same event
Complete
Audit evidence
The event changed. The fulfillment path changed.
The declared outcome did not. XOPS continued operating until the estate converged.
Product depth
Procure → Stock → Deploy → Operate → Recover or Retire
Each outcome coordinates the work across every system involved (HRIS, MDM, IDP, supplier, carrier, stockroom) and adapts when reality breaks the script. Every transition follows a governed, auditable path, with rollback where the connected system supports it.
Provisioning
Typically 2–4 days
Pool allocation, zero-touch MDM enrollment, profile push, delivery routing, employee confirmation, first compliance scan.
Provisioning
Typically 3–5 days
Operator-led image, configure, test, quality verification, delivery routing, employee confirmation. Used when zero-touch is not eligible.
Procurement & intake
Typically 7–21 days
Triggered when the pool is empty: supplier evaluation, PO generation, approval routing, vendor fulfillment, intake, registration, then routed to deployment.
Lifecycle renewal
Position-based
Initiated when the Device Position determines refresh is required based on performance, condition, security, economics, employee impact, and business intent. New-device deployment and old-device recovery proceed in parallel, with refurbishment viability assessed.
Recovery & wipe
Emergency response
Emergency remote lock in minutes, recovery logistics, chain of custody, condition assessment, wipe completion, sanitization evidence, refurbishment assessment, or ITAD disposal.
Repair & continuity
Same-day loaner
Hardware fault diagnosis, vendor dispatch, same-day loaner from the nearest pool imaged to standard config, loaner-to-repaired swap on return.
Use a 15-minute working session to select one declared outcome and the systems behind it. Then run it end to end before the next steering meeting.
