WEBVTT

00:00:00.020 --> 00:00:03.410
Hey everybody, and welcome back to the Operational ITAM podcast.

00:00:03.890 --> 00:00:08.000
I'm Bill Van Nort, and I'm super excited about episode two for this series.

00:00:08.590 --> 00:00:12.460
If you joined me for the first episode, welcome back. I'm glad you're here.

00:00:12.970 --> 00:00:16.489
If you are new to the series, I suggest listening to the first episode,

00:00:16.489 --> 00:00:18.640
and then come back to episode two.

00:00:19.390 --> 00:00:23.600
Good morning, good afternoon, or good evening, wherever you happen to be listening from.

00:00:24.080 --> 00:00:28.730
This is the Operational ITAM podcast, the show where we take the unglamorous

00:00:28.730 --> 00:00:31.960
machinery of enterprise technology and make it make sense.

00:00:32.729 --> 00:00:37.210
I'm your host, Bill, and today's episode is a deep dive of the hardware asset

00:00:37.210 --> 00:00:40.700
management topic we briefly touched upon in the first episode.

00:00:41.280 --> 00:00:45.220
Welcome in. Grab your coffee, grab your headphones, and let's get into it.

00:00:45.930 --> 00:00:49.390
Last time, I told you the hardware lifecycle has seven stages,

00:00:49.650 --> 00:00:53.280
and I promised we'd go deeper. Today, we keep that promise.

00:00:54.390 --> 00:00:59.580
Quick recap because good teaching repeats itself on purpose Hardware Asset Management,

00:00:59.760 --> 00:01:04.310
or HAM is the discipline of managing physical technology assets across their

00:01:04.310 --> 00:01:07.810
entire life cycle Request, Procure,

00:01:08.360 --> 00:01:10.190
Receive, Deploy,

00:01:10.800 --> 00:01:18.450
Maintain, Recover, and Dispose 7 Stages Every device passes through all 7,

00:01:18.640 --> 00:01:20.000
whether you're watching or not.

00:01:21.200 --> 00:01:26.230
Today, we walk the life cycle gate by gate, and at each gate I'll tell you three things.

00:01:26.840 --> 00:01:31.050
What the stage is, what data must be captured, and how it fails.

00:01:31.760 --> 00:01:36.290
Because every stage fails the same way in every organization I've ever seen.

00:01:37.070 --> 00:01:40.560
The failure modes are practically franchised. Gate 1.

00:01:40.950 --> 00:01:45.900
The Request The request stage is where a business need becomes a demand for equipment.

00:01:46.530 --> 00:01:50.520
Someone is hired. Someone's machine dies. A project spins up.

00:01:50.960 --> 00:01:54.230
Simple, right? Here's what must be captured at this gate.

00:01:54.950 --> 00:01:59.570
Who is asking? What are they asking for? What standards it maps to?

00:02:00.000 --> 00:02:03.000
Who approved it? And what cost center is paying for it?

00:02:03.560 --> 00:02:05.780
Five facts. That's the whole toll.

00:02:06.480 --> 00:02:10.030
And here's how it fails. The request happens outside the process.

00:02:10.449 --> 00:02:14.169
A manager emails a friend in IT. A department buys its own gear on a credit

00:02:14.169 --> 00:02:16.810
card. An executive's assistant just handles it.

00:02:17.340 --> 00:02:20.720
Every one of those transactions creates an asset that will haunt your inventory

00:02:20.720 --> 00:02:24.870
for years. Because an asset born without a record is a ghost from day one.

00:02:25.430 --> 00:02:29.300
We'll talk about ghosts properly in part two. They deserve their own segment.

00:02:29.830 --> 00:02:33.820
The control at this gate is a service catalog with standard configurations.

00:02:34.310 --> 00:02:37.699
Standards matter more than people think, and not just for cost.

00:02:38.210 --> 00:02:42.199
Every deviation from standard is a snowflake. Unique to support,

00:02:42.500 --> 00:02:45.190
unique to secure, unique to dispose of.

00:02:45.560 --> 00:02:48.540
A fleet of snowflakes isn't a fleet. It's a blizzard.

00:02:49.270 --> 00:02:54.669
Gate 2. Procure. Procurement converts the approved request into a purchase,

00:02:55.160 --> 00:02:57.370
and this is where the asset record should be born.

00:02:58.400 --> 00:03:02.550
Not at receiving. Not at deployment. At the purchase order.

00:03:03.540 --> 00:03:07.900
The moment money is committed, a record should exist saying this asset is inbound,

00:03:08.020 --> 00:03:12.850
here's what it is, here's what it cost, here's the vendor, here's the contract,

00:03:13.110 --> 00:03:16.250
here's the warranty entitlement. What must be captured?

00:03:16.970 --> 00:03:23.640
Purchase order number, line item detail, unit cost, vendor, warranty terms,

00:03:23.990 --> 00:03:28.720
and, critically, the link between the PO and the eventual serial numbers.

00:03:29.540 --> 00:03:33.910
That link is the thread that ties your financial world to your operational world.

00:03:34.720 --> 00:03:38.900
Cut that thread, and finance and IT are describing two different companies.

00:03:39.530 --> 00:03:43.070
How it fails. Bulk purchases recorded as a single line.

00:03:43.820 --> 00:03:46.710
200 laptops, one line item, one lump sum.

00:03:47.030 --> 00:03:51.040
Now, try answering three years later, which of those 200 serials is still under

00:03:51.040 --> 00:03:55.640
warranty, or what any individual device actually cost for depreciation purposes.

00:03:55.980 --> 00:04:00.270
You can't. The data was never atomic, and you cannot split an atom you never had.

00:04:00.890 --> 00:04:06.440
Gate 3. Receive. Receiving is where the physical world and the record meet for the first time.

00:04:07.010 --> 00:04:09.860
The handshake between the purchase order and the box on the dock.

00:04:10.940 --> 00:04:14.010
This is the single highest leverage moment in the entire life cycle.

00:04:14.940 --> 00:04:20.470
Capture at this gate. Serial number, asset tag applied, model verified against

00:04:20.470 --> 00:04:23.910
the PO, condition confirmed, and location assigned.

00:04:24.589 --> 00:04:27.410
Even if that location is just stock room, shelf 4.

00:04:28.089 --> 00:04:32.450
Let me say that plainly. If you tag and record assets accurately at receiving,

00:04:32.870 --> 00:04:34.730
every downstream stage gets easier.

00:04:35.570 --> 00:04:38.930
If you don't, no amount of downstream heroics fully recovers.

00:04:39.700 --> 00:04:43.570
Receiving is where data quality is cheapest. Every gate after this one,

00:04:43.830 --> 00:04:45.420
the same correction costs more.

00:04:45.980 --> 00:04:50.529
How it fails? Receiving is treated as a shipping function instead of a data function.

00:04:51.300 --> 00:04:55.589
The box gets signed for, stacked, and the record gets created later.

00:04:55.980 --> 00:05:01.240
And later, as we all know, is a mythical time zone where no work has ever actually been performed.

00:05:02.000 --> 00:05:06.980
Gate 4. Deploy. Deployment assigns the asset to a person, a place,

00:05:06.980 --> 00:05:08.770
or a purpose and puts it to work.

00:05:10.180 --> 00:05:15.390
What must be captured, the assignment, who has it, the location,

00:05:15.550 --> 00:05:21.160
the date, what configuration is applied, and the status change from in-stock to in-use.

00:05:21.790 --> 00:05:25.970
In modern estates, deployment is also where the device enrolls in endpoint management,

00:05:26.350 --> 00:05:31.050
joins identity, and inherits security policy, which means deployment is where

00:05:31.050 --> 00:05:33.529
HAM shakes hands with security for the first time.

00:05:34.089 --> 00:05:37.970
It will not be the last handshake. Keep that thought for the end of the episode.

00:05:38.670 --> 00:05:40.730
How it fails. Assignment drift.

00:05:41.670 --> 00:05:45.960
The device was deployed to Alice. Alice moved teams. The machine went to Srini.

00:05:46.330 --> 00:05:49.529
Srini left. His manager kept it in a drawer as a spare.

00:05:50.190 --> 00:05:53.690
The record still says Alice. Three moves. Zero updates.

00:05:54.360 --> 00:05:59.370
Multiply by a thousand devices in five years, and your assignment data becomes historical fiction.

00:05:59.950 --> 00:06:02.920
Well written, internally consistent, and dead wrong.

00:06:03.589 --> 00:06:08.490
The control. No moves without a ticket, and no ticket without a corresponding record update.

00:06:09.820 --> 00:06:14.200
In episode one, I called this control adherence, the percentage of lifecycle

00:06:14.200 --> 00:06:17.480
events that pass through the sanction process instead of around it.

00:06:18.190 --> 00:06:21.990
Deployment, and everything after it, is where that metric earns its keep.

00:06:22.670 --> 00:06:27.300
Gate five, maintain. Maintenance is the long middle of the lifecycle.

00:06:27.780 --> 00:06:32.760
Repairs, upgrades, warranty claims, and the quiet accumulation of wear and tear.

00:06:33.660 --> 00:06:38.400
It's the least glamorous stage, and the longest one. A device spends a few days

00:06:38.400 --> 00:06:43.380
in the first four gates, and several years in this one. What's important to capture here?

00:06:44.280 --> 00:06:48.200
Incident and repair history tied to the asset record, warranty status,

00:06:48.330 --> 00:06:50.810
and any changes to configuration or components.

00:06:51.600 --> 00:06:53.910
Why does repair history belong in the asset record?

00:06:54.710 --> 00:06:58.710
Because patterns hide in it. If one model generates triple the tickets of its

00:06:58.710 --> 00:07:02.150
peers, that's not trivia. That's procurement intelligence.

00:07:03.290 --> 00:07:07.380
The maintain stage is where your asset data starts paying you back, if you let it.

00:07:08.070 --> 00:07:11.640
Feed repair patterns into your next purchase decision, and asset management

00:07:11.640 --> 00:07:15.450
stops being a record-keeping function and starts being a forecasting function.

00:07:16.090 --> 00:07:21.370
How it fails. The service desk and the asset register live in different systems that never speak.

00:07:22.460 --> 00:07:25.860
Tickets reference Bob's laptop. Which laptop?

00:07:26.530 --> 00:07:32.180
The record can't say, so the pattern is never seen. So the same lemon gets purchased three more times.

00:07:32.800 --> 00:07:38.490
Gate 6. Recover. Recovery is the retrieval of an asset when its assignment ends.

00:07:38.980 --> 00:07:42.980
The employee departs, the project closes, the refresh replaces it.

00:07:43.740 --> 00:07:47.600
And I'll be blunt, recovery is the most commonly broken stage in the entire

00:07:47.600 --> 00:07:50.230
life cycle, and remote work broke it harder.

00:07:50.960 --> 00:07:56.020
When the workforce went home, the devices went with them, and a meaningful percentage never came back.

00:07:56.900 --> 00:08:02.020
Offboarding without asset recovery is resignation by mail with company property as a parting gift.

00:08:02.540 --> 00:08:05.580
What must be captured? The return itself?

00:08:06.420 --> 00:08:11.410
Condition upon return? The status change to in-stock or pending disposal?

00:08:12.170 --> 00:08:16.720
And, before anything else happens, confirmation that the device is still enrolled,

00:08:16.930 --> 00:08:19.080
still locatable, and still encrypted?

00:08:20.130 --> 00:08:24.510
Key item to capture here, the disposition decision. Redeploy it,

00:08:24.870 --> 00:08:26.850
hold it as a spare, or retire it.

00:08:27.810 --> 00:08:32.309
That decision should be deliberate, recorded, and fast, because a recovered

00:08:32.309 --> 00:08:34.870
asset sitting in limbo is depreciating in the dark.

00:08:35.549 --> 00:08:39.540
The control at this gate is elegant in its simplicity. Tie asset returned to

00:08:39.540 --> 00:08:41.309
offboarding and put teeth in it.

00:08:41.910 --> 00:08:46.410
No return, no ticket closure, and someone's name stays on the exception report

00:08:46.410 --> 00:08:49.130
until the device is in hand or formally written off.

00:08:49.950 --> 00:08:53.790
Remember the daily exception report from volume one? This is what it's for.

00:08:54.640 --> 00:08:59.799
That's six gates. The seventh, disposal, is where security, legality,

00:08:59.799 --> 00:09:03.160
and money all collide, and it deserves the room to breathe.

00:09:03.870 --> 00:09:11.260
Gate seven, dispose. Disposal, or more formally, IT asset disposition,

00:09:11.470 --> 00:09:15.350
or ITAD, is the controlled retirement of an asset.

00:09:16.100 --> 00:09:21.150
Data sanitized, chain of custody maintained, value recovered where possible,

00:09:21.510 --> 00:09:23.480
and the record closed with evidence.

00:09:24.290 --> 00:09:27.850
In Volume 1, I called Disposal the shredder in the back room,

00:09:28.330 --> 00:09:30.280
and I said the shredder keeps records too.

00:09:31.179 --> 00:09:36.030
Here's why that line matters. Disposal is the only life cycle stage where a

00:09:36.030 --> 00:09:38.540
mistake can put your company on the front page.

00:09:39.370 --> 00:09:43.290
Nobody ever suffered a breaking news segment from a badly recorded deployment.

00:09:43.950 --> 00:09:46.809
Improperly disposed devices with recoverable data?

00:09:47.500 --> 00:09:53.010
That's a breach, a regulatory event, and a brand wound, all in one dumpster.

00:09:53.630 --> 00:09:58.760
So let's get precise about data Sanitization, because precision here is the whole job.

00:09:59.309 --> 00:10:05.420
The reference standard is NIST Special Publication 888, the federal media sanitization

00:10:05.420 --> 00:10:09.000
guideline that the private sector adopted as the de facto benchmark.

00:10:09.620 --> 00:10:11.059
It defines three levels.

00:10:11.830 --> 00:10:16.240
The first level, clear, involves logical techniques, overriding,

00:10:16.240 --> 00:10:18.030
protecting against simple recovery.

00:10:18.850 --> 00:10:23.500
Purge, the second level, offers stronger techniques, cryptographic erase,

00:10:23.670 --> 00:10:29.010
block erase, and sanitize commands, which offers protection against laboratory-grade recovery.

00:10:29.679 --> 00:10:33.250
The third level? Destroy. Physical destruction.

00:10:33.929 --> 00:10:39.160
This level includes shredding, degaussing where applicable. The data dies with the device.

00:10:40.299 --> 00:10:43.770
Which level you choose depends on the sensitivity of the data and where the

00:10:43.770 --> 00:10:46.340
asset is going next, not on the hardware alone.

00:10:47.460 --> 00:10:50.790
A standard-issue laptop might hold the most sensitive data in the company,

00:10:50.790 --> 00:10:52.130
depending on who carried it.

00:10:53.299 --> 00:10:57.690
And note, for the technically inclined, solid-state drives are not hard drives.

00:10:58.120 --> 00:11:01.670
Wear leveling and hidden blocks mean old-school multi-pass overwrites,

00:11:01.910 --> 00:11:06.710
the ancient DoD 7-pass folklore, don't reliably sanitize flash media.

00:11:07.420 --> 00:11:10.860
If a vendor quotes you passes, that's not a service offering,

00:11:10.980 --> 00:11:12.220
that's a museum exhibit.

00:11:13.570 --> 00:11:17.740
Purge-level techniques, cryptographic erase in particular, are the modern answer

00:11:17.740 --> 00:11:22.070
for SSDs, and as a bonus, Purge preserved the hardware for resale,

00:11:22.260 --> 00:11:25.220
which means compliance and residual value are not in conflict.

00:11:26.510 --> 00:11:31.360
Also worth knowing, NIST refreshed the standard. Revision 2 shifts the emphasis

00:11:31.360 --> 00:11:35.460
from device-by-device wipe recipes toward running a sanitization program,

00:11:35.830 --> 00:11:39.890
and points to IEEE 2-883 for technique selection.

00:11:41.040 --> 00:11:45.330
The direction of travel is clear. Regulators want to see a system, not a one-off.

00:11:46.200 --> 00:11:51.280
Now, most organizations don't dispose of assets themselves. They use an ITAD vendor.

00:11:51.960 --> 00:11:57.350
That's great, but hear me. You can outsource the work. You cannot outsource the accountability.

00:11:57.910 --> 00:12:00.720
So audit the credential, not the vendor brochure.

00:12:01.380 --> 00:12:06.620
The certifications that matter, R2v3, Responsible Recycling Version 3,

00:12:06.970 --> 00:12:11.130
covering data security, environmental handling, and downstream accountability.

00:12:11.730 --> 00:12:15.420
E-Stewards, similar territory with a strong environmental emphasis,

00:12:15.900 --> 00:12:21.040
and NAIDA, which is specific to data destruction, with unannounced audits.

00:12:21.600 --> 00:12:23.049
A vendor holding these has been

00:12:23.049 --> 00:12:26.230
independently verified against the same standards you're on the hook for.

00:12:26.730 --> 00:12:29.450
A vendor without them is asking you to take their word for it,

00:12:29.770 --> 00:12:31.580
with your data, on their truck.

00:12:32.190 --> 00:12:36.140
And demand the paper, certificates of sanitization or destruction,

00:12:36.380 --> 00:12:39.490
serial by serial, matched back to your asset records.

00:12:40.110 --> 00:12:42.770
Chain of custody from your dock to final disposition.

00:12:43.570 --> 00:12:46.590
When an auditor or regulator asks what happened to a device,

00:12:46.990 --> 00:12:49.290
we send it to a recycler is not an answer.

00:12:49.970 --> 00:12:55.540
Serial number, certificate, date, method, final disposition. That's an answer.

00:12:56.610 --> 00:12:59.660
The shredder keeps records. Make sure yours does.

00:13:00.300 --> 00:13:04.390
Now let's talk about the two economic questions that hover over the whole life cycle.

00:13:04.760 --> 00:13:08.430
When do you refresh, and what is all this neglect actually costing you?

00:13:09.120 --> 00:13:13.170
Refresh first. The industry's center of gravity for laptops is a three to five

00:13:13.170 --> 00:13:17.930
year cycle, with desktops running a bit longer, and power users cycling faster.

00:13:18.490 --> 00:13:21.540
The total cost of ownership research behind the shorter end is real.

00:13:21.910 --> 00:13:27.120
Past year three, out-of-warranty repairs, support burden, and security exposure climb.

00:13:27.710 --> 00:13:32.600
One frequently cited study found four-year-old PCs suffered roughly 50% more

00:13:32.600 --> 00:13:34.210
security incidents than new ones.

00:13:34.810 --> 00:13:38.280
But, and this is the part the OEM's marketing departments won't tell you,

00:13:38.740 --> 00:13:40.950
the calendar is a proxy, not a truth.

00:13:41.620 --> 00:13:45.550
The mature version of refresh is condition-based. Actual device health.

00:13:45.950 --> 00:13:48.970
Actual failure rates from your maintenance and warranty claim data.

00:13:49.410 --> 00:13:51.360
Actual performance against the workload.

00:13:51.970 --> 00:13:55.830
Some devices earn a sixth year. some demand replacement in their third.

00:13:56.490 --> 00:14:00.400
A calendar refresh treats them identically, which means it's simultaneously

00:14:00.400 --> 00:14:03.170
scrapping good machines and babying bad ones.

00:14:03.860 --> 00:14:08.010
If you captured repair history at gate 5, you already own the data to do better.

00:14:08.790 --> 00:14:12.940
This is also very much a current events topic. Operating system end-of-life

00:14:12.940 --> 00:14:16.890
waves and component shortages have been pushing device prices up sharply,

00:14:17.320 --> 00:14:21.320
which makes squeezing honest extra life from healthy assets a genuine financial

00:14:21.320 --> 00:14:26.120
lever, not just a sustainability talking point. And then there are the ghosts.

00:14:26.800 --> 00:14:31.030
A ghost asset is a record without a device. Inventory says it exists,

00:14:31.200 --> 00:14:32.860
but the physical world disagrees.

00:14:33.330 --> 00:14:37.010
Its evil twin, the zombie asset, is a device without a record.

00:14:37.250 --> 00:14:40.380
It's on your network, drawing support and licenses and risk,

00:14:40.520 --> 00:14:42.470
and your system of record has never heard of it.

00:14:43.270 --> 00:14:46.490
Here's the composite picture. And it's typical, not extreme.

00:14:46.960 --> 00:14:49.230
An enterprise buys 1,000 laptops.

00:14:49.840 --> 00:14:53.530
Three years of departures, upgrades, failures, and office moves later,

00:14:53.820 --> 00:14:56.190
the inventory still says 1,000 active.

00:14:56.830 --> 00:15:02.390
A physical audit finds 820. The other 180 are ghosts. And here's the expensive

00:15:02.390 --> 00:15:04.720
part. The company is still paying for them.

00:15:05.260 --> 00:15:10.100
Maintenance contracts. Endpoint security licenses. Software provisioned per

00:15:10.100 --> 00:15:12.200
device. Support capacity.

00:15:12.790 --> 00:15:15.760
Ghosts don't just distort your data, they draw a salary.

00:15:16.510 --> 00:15:20.850
Every ghost was created at a gate. A purchase never atomized.

00:15:21.190 --> 00:15:22.730
A receipt never recorded.

00:15:23.290 --> 00:15:27.020
A move never ticketed. A departure never recovered.

00:15:27.820 --> 00:15:32.630
Which is the entire thesis of this episode. You don't fix ghosts with an annual seance.

00:15:33.050 --> 00:15:36.620
You fix them by controlling the gates. So ghosts stop being born.

00:15:37.410 --> 00:15:41.090
Let me extend the library one more time since it served us well in Volume 1.

00:15:41.670 --> 00:15:45.830
If the estate is a library, then hardware asset management is circulation.

00:15:46.410 --> 00:15:51.600
Request is the patron at the desk. Procurement is acquisitions placing the order.

00:15:52.140 --> 00:15:54.380
Receiving is cataloging. And

00:15:54.380 --> 00:15:58.040
a book shelled without a catalog card is lost the moment you let go of it.

00:15:58.790 --> 00:16:04.190
Deployment is checkout. Maintenance is rebinding the ones that get read too many times.

00:16:04.810 --> 00:16:10.770
Recovery is the return slot. And every library learns that returns need a due date and a consequence.

00:16:11.000 --> 00:16:13.280
Or the shelves empty one borrower at a time.

00:16:13.980 --> 00:16:19.230
And disposal is the shredder in the back, with a log, a certificate, and a clean conscience.

00:16:20.190 --> 00:16:24.020
One closing principle, in the spirit of the one that closed volume one.

00:16:24.760 --> 00:16:29.120
Hardware asset management is a custody discipline. At every moment of an asset's

00:16:29.120 --> 00:16:32.820
life, one accountable party holds it, and the record says so.

00:16:33.670 --> 00:16:37.880
Every failure we walk through today, the rogue purchase, the lump sum PO,

00:16:38.110 --> 00:16:42.100
the unrecorded receipt, the drifted assignment, the unreturned laptop,

00:16:42.370 --> 00:16:46.900
and the undocumented disposal, is the same failure, wearing six costumes.

00:16:47.660 --> 00:16:49.840
Custody changed, and the record didn't.

00:16:50.710 --> 00:16:55.770
Guard the gates, and the record follows the asset. That's the whole discipline in one sentence.

00:16:56.260 --> 00:16:59.720
Next episode, we cross over to the intangible side of the house.

00:17:00.120 --> 00:17:01.700
Software asset management.

00:17:02.240 --> 00:17:07.170
Licenses, entitlements, audits, and the publishers who profit from your confusion.

00:17:07.880 --> 00:17:09.940
Bring your skepticism. You'll need it.

00:17:10.650 --> 00:17:15.820
Class dismissed. homework. And this one is intended to make this real for everyone.

00:17:16.599 --> 00:17:20.240
Pick your last completed employee offboarding and trace the device.

00:17:21.030 --> 00:17:23.220
Not the record, the device.

00:17:24.230 --> 00:17:28.560
Where is it, physically, right now, and does the record agree?

00:17:29.540 --> 00:17:33.640
If you can answer in under five minutes, congratulations, your gates are holding.

00:17:34.480 --> 00:17:39.320
If you can't, well, now you know which episode to listen to again.

00:17:39.869 --> 00:17:42.220
That's today's episode. Congratulations.

00:17:42.410 --> 00:17:45.140
You now know the full spectrum of hardware asset management.

00:17:45.700 --> 00:17:49.480
Not all the details, but enough to get you started in a very meaningful way.

00:17:50.090 --> 00:17:54.500
And of course, I'll be here next week to provide more relevant ITAM content

00:17:54.630 --> 00:17:56.230
for all of you practitioners out there.

00:17:56.770 --> 00:18:00.470
I'm Bill Van Nort, and this is the Operational ITAM Podcast.

00:18:01.180 --> 00:18:04.310
I look forward to talking more with you next week. Take care.