Hardware refresh waves.
Out-of-policy devices are identified and refreshed in waves through the lockers.
Tools you may already run, plus the one that hands the device over.
From the first signal to a device in hand.
Tanium or Intune finds devices out of policy or at end of life.
Hardware Asset Management plans refresh waves, and devices are built in batches.
Users swap through the lockers, wave by wave.
The full sequence
- Tanium or Intune data shows devices out of policy or at end of life.
- Hardware Asset Management groups them into waves by site and model.
- Replacement devices are built in batches for each wave.
- Smart Collect® reserves cells, and users in the wave are invited to collect.
- Users swap devices and return the old ones in the same cell.
- Returned devices are routed for wipe, reuse or disposal.
What you need in place
- Tanium or Microsoft Intune reporting device age and compliance
- ServiceNow Hardware Asset Management
- Smart Lockers with capacity for refresh waves
How the pieces connect
- Tanium or Intune
- Feed device data into ServiceNow, for example through the Service Graph Connector for Tanium or the Intune spoke.
- ServiceNow HAM
- Identifies devices due for refresh and plans the waves.
- Smart Collect®
- Reserves cells for each wave and records every swap.
The physical steps stay the same, whichever system makes the decision.
Run this recipe from a standard ServiceNow workflow today, and let AI take the decision later. Nothing on the physical side changes.
One record of what was decided, and what physically happened.
A reference design for your technical team.
The Blueprint shows how this recipe would work in your ServiceNow instance and what a build would involve. It is a design, not a step-by-step installation guide.
- What you need in place. Tanium or Microsoft Intune reporting device age and compliance · ServiceNow Hardware Asset Management · Smart Lockers with capacity for refresh waves
- How the pieces connect. The role of Tanium, Microsoft Intune and Hardware Asset Management and Smart Collect®, and what stays in your instance
- Step by step. All 6 steps, from the first signal to the returned device
- Approval and policy. Size waves to locker capacity at each site.
- Handover rules and exceptions. Reservations, codes, expiry, returns, and what happens when stock runs out or nobody collects
- What to measure. Devices refreshed per week · Queue time at the tech bar during refresh · Old devices recovered per wave
- What a build involves. The questions to settle first, the roles involved, and how we would scope a six to eight week pilot
Request the Blueprint
A four-page reference design for your technical team. Tell us who you are and the Blueprint downloads straight away.
Before you ask
How many devices can a wave handle?
As many as the lockers hold. Waves are sized to locker capacity at each site, and refilled as users collect.
Is this an off-the-shelf integration?
No. It is a recipe concept that shows what becomes possible when these tools are combined with Smart Collect®. We build it with you, and where needed with the vendor, when it fits your estate.
Where does the data live?
In your own ServiceNow instance. Smart Collect® does not keep a separate database of your users or devices.
Do we need AI for this?
No. A standard ServiceNow workflow can run every step today. Otto or Flow can take over the decision later without changing anything on the physical side.