Operational ITAM Podcast

About Operational ITAM Podcast

Thirty years of enterprise IT, distilled into something you can use on Monday morning. Operational ITAM is a podcast about the unglamorous machinery of enterprise technology — hardware and software asset management, licensing, audit defense, SaaS governance, and the money quietly leaking out of all of them. Host Bill Van Nort has led IT asset management, end-user computing, and workplace technology at large organizations across banking, mortgage, and automotive, reclaimed millions in software spend, and survived audits from the biggest publishers on the planet. No vendor pitches disguised as advice. No jargon for its own sake. When something is an opinion, he says so. When the honest answer is "it depends," he tells you what it depends on. New episodes cover the fundamentals that never change: know what you have, know where it is, know what it costs, know when it leaves.

Publisher

Bill Van Nort

Category

business · technology

Language

en

Explicit

No

First episode

29 Jul 2026

Latest episode

8 Oct 2026

Latest episodes

17 episodes in the feed.

1. 

   8 Oct 2026

   The Decision Table: Keep the Result

   The project is finished. The invoice is lower. Six weeks later, someone asks for more licenses. What changed? Bill Van Nort follows a fictional software service after its initial improvement has been verified. This episode separates legitimate growth, an outdated onboarding rule, and overdue temporary-access reviews, then shows how to preserve the result without blocking the service the business needs. IN THIS EPISODE • Keep purchased capacity, assignments and business requirements distinct. • Check the process that creates new assignments as well as the current list. • Set review triggers early enough to leave time for action. • Treat missing evidence as unconfirmed. • Reopen the decision when business needs change. • Describe restored capacity without inventing another savings claim. WATCH, LISTEN AND READ https://www.operationalitam.com/pages/podcast-017-keep-the-result.html PRACTICAL EXERCISE Allow about an hour. Choose one completed technology change using authorized records. Record the verified outcome and date, a condition that could undermine it, the evidence that would reveal the change, its owner, the review trigger and the response deadline. Inspect a recent issue to see whether the cause was corrected and the result checked. If no example exists, mark the control untested. CHAPTERS (00:00) - Keep the Result (00:53) - The Decision Table (02:22) - A fictional software service (02:33) - Verify the starting result (03:28) - Six weeks later (03:53) - Three causes, three responses (05:48) - Hand over the operating conditions (07:22) - Act before capacity runs out (08:41) - Roles and operating cadence (09:30) - Correct the assignment path (10:40) - Restored capacity, not new savings (12:08) - When the decision should change (13:20) - What an alert can see (14:13) - Ownership and authority (15:00) - Keep the review useful (16:03) - Beyond software: spare laptops (17:20) - A management update that supports action (18:51) - Your practical exercise (19:50) - Resources and closing (20:41) - Credits TRANSCRIPT Click here to view the episode transcript. (https://share.transistor.fm/s/df68459e/transcript) SOURCES AND RESOURCES FinOps Foundation — Usage Optimization: https://www.finops.org/framework/capabilities/usage-optimization/ FinOps Foundation — Anomaly Management: https://www.finops.org/framework/capabilities/anomaly-management/ Microsoft Learn — Manage group licenses: https://learn.microsoft.com/en-us/microsoft-365/admin/manage/manage-group-licenses?view=o365-worldwide Amazon Web Services — Cost Anomaly Detection: https://docs.aws.amazon.com/cost-management/latest/userguide/manage-ad.html Roles & Operating Cadence, Bill’s paid resource: https://www.operationalitam.com/store/index.php?page=product&sku=CP-ROLES The exercise requires no purchase. The case quantities and prices are fictional, illustrative USD. Operational ITAM Podcast | Bill Van Nort | An EpicB Media LLC production. https://www.operationalitam.com

2. 

   5 Oct 2026

   The Decision Table: Where Did the Saving Go?

   An approved reduction is only the beginning. Bill Van Nort follows a fictional software subscription change from forecast through the signed agreement, implementation, invoices and a delayed credit. See why a $48,000 gross forecast becomes a $27,000 net calendar-year benefit—and how to explain every difference. IN THIS EPISODE • Agree the baseline, scope and reporting period. • Distinguish assigned licenses from purchased commitments. • Explain delayed implementation and retained capacity. • Trace billing corrections to the affected service periods. • Separate forecast, verified result and annualized run rate. • Check that the service still meets the business requirement. All case amounts are illustrative USD. The fictional supplier minimum and credit timing are not Microsoft or AWS terms. Finance determines your organization's recognition and accounting treatment. YOUR NEXT STEP Pick one completed technology change. Trace its estimate, agreed baseline, effective date, implemented quantity, invoices, credits and implementation costs. Explain material differences. State what is verified and what remains unresolved. Use records you are authorized to access and take the result to your finance partner. WATCH, LISTEN & READ https://www.operationalitam.com/pages/podcast-016-where-did-the-saving-go.html Watch on YouTube: https://www.youtube.com/watch?v=WQgC5BoZD9g PRACTICAL RESOURCE F02 — Validate benefits and report business outcomes: https://www.operationalitam.com/store/index.php?page=product&sku=F02 Bill's paid resource includes an editable procedure, flowchart and adoption/evidence checklist. Purchasing supports the show. The homework requires no purchase. CHAPTERS (00:00) - Where did the saving go? (01:43) - The fictional subscription case (02:39) - Agree the baseline (04:53) - What the signed amendment changes (07:36) - Verify implementation (09:58) - Operational ITAM Store: F02 (11:11) - Follow the invoices (12:51) - Keep the credit in the right period (14:06) - The verified annual result (15:38) - Annual result versus run rate (16:16) - Cloud commitments and utilization (18:11) - Keep the evidence traceable (18:43) - Your practical homework (20:12) - Closing TRANSCRIPT Click here to view the episode transcript. (https://share.transistor.fm/s/54bdee04/transcript) SOURCES & FURTHER READING FinOps Foundation — Reporting and Analytics https://www.finops.org/framework/capabilities/reporting-analytics/ FinOps Foundation — Quantify Business Value https://www.finops.org/framework/domains/quantify-business-value/ Microsoft — Buy or remove business subscription licenses https://learn.microsoft.com/en-us/microsoft-365/commerce/licenses/buy-licenses?view=o365-worldwide Microsoft — Understand your MCA invoice https://learn.microsoft.com/en-us/microsoft-365/commerce/billing-and-payments/understand-your-invoice?view=o365-worldwide AWS — Savings Plans utilization metrics https://docs.aws.amazon.com/savingsplans/latest/userguide/ce-sp-pr-metrics.html AWS — Using the utilization report https://docs.aws.amazon.com/savingsplans/latest/userguide/ce-sp-usingPR.html AWS — How Savings Plans apply https://docs.aws.amazon.com/savingsplans/latest/userguide/sp-applying.html PRODUCTION Written and hosted by Bill Van Nort. Voice production: ElevenLabs. Audio finishing: Adobe Audition. Production assistance: OpenAI Codex. Video assembly: FFmpeg. Show theme: Ten Second Pulse, created with Suno. Operational ITAM covers practical IT asset management, software licensing, FinOps and evidence-led decisions. Website and resources: https://www.operationalitam.com/ An EpicB Media LLC production.

3. 

   28 Sept 2026

   The Decision Table: Who Owns the Renewal Decision?

   A renewal can pass through every department and still arrive at its deadline without a decision owner. Bill Van Nort works through a fictional customer-support renewal to show how ITAM, FinOps, procurement, finance, engineering, and the service owner can reach a defensible choice and verify what happens afterward. The episode examines a lower-priced replacement, transition costs, a revised incumbent offer, and a delay scenario that reverses the cost ranking. Azure Hybrid Benefit and AWS Compute Savings Plans illustrate why licensing rights, consumption forecasts, and commercial commitments need a shared discussion. The company, prices, and outcome in the central case are illustrative, not a client case study or savings benchmark. Website and transcripts: https://www.operationalitam.com/ · Operational ITAM Store: https://www.operationalitam.com/store/ · Roles & Operating Cadence: https://www.operationalitam.com/store/index.php?page=product&sku=CP-ROLES The store contains Bill's paid resources. Today's homework requires no purchase. Your homework Choose one renewal. Record the decision, last useful decision date, authorized owner, options, missing evidence and its owners, the condition that would change your recommendation, implementation responsibility, and the post-approval check. Discussion Where does your renewal process stall: evidence, authority, migration readiness, or checking the result? Chapters 00:00 The meeting that cannot decide 01:08 From a better bill to a better decision 02:44 The fictional renewal 04:32 Who comes to the table 06:40 When the evidence disagrees 09:16 A short break 10:24 Two real reasons the disciplines need each other 12:22 The offer changes 15:05 Make the decision executable 16:35 After the signature 18:23 The takeaway and the homework Transcript Click here to view the episode transcript. (https://share.transistor.fm/s/9db65ff5/transcript) Primary references FinOps Framework: https://www.finops.org/framework/ Intersecting Disciplines: https://www.finops.org/framework/capabilities/intersecting-disciplines/ ITAM and FinOps: planning and procurement: https://www.finops.org/wg/finops-itam-practical-scenarios-planning-procurement/ Microsoft SQL Server licensing: https://www.microsoft.com/licensing/guidance/SQL Azure Hybrid Benefit: https://learn.microsoft.com/en-us/azure/azure-sql/azure-hybrid-benefit?view=azuresql AWS Savings Plans FAQ: https://aws.amazon.com/savingsplans/faqs/ AWS Savings Plans returns: https://docs.aws.amazon.com/savingsplans/latest/userguide/return-sp.html An EpicB Media LLC production.

4. 

   25 Sept 2026

   Challenge the Bill Before You Negotiate the Discount

   Twenty percent off sounds like progress. Until the new bill is still twenty percent higher than last year—and nobody has checked whether you need everything on it. In Episode 014 of the Operational ITAM Podcast, Bill Van Nort examines how quantities, licensing rights, product choices, and contract terms shape a renewal bill before the discount conversation begins. Microsoft, Broadcom, and Oracle provide three different tests. Microsoft’s July 2026 pricing changes reach existing customers at renewal. VMware licensing requires a careful look at physical capacity and retained rights. Oracle’s Java subscription demands a precise understanding of the employee metric and the rights attached to specific releases and updates. The question throughout: what can you substantiate, what can you challenge, and what must change operationally before a smaller commitment becomes possible? In this episode Separate rate increases from changes in quantity, packaging, and terms. Check physical-core calculations without confusing fewer virtual machines with fewer licensing obligations. Examine Oracle’s employee-based metric and the planned October 2026 licensing transition for Oracle JDK 21 updates. Distinguish a correction to the bill from a concession you want to negotiate. Compare staying, switching, and bridging on the same cost horizon. Understand why savings against a quote differ from reductions against actual spending. Verify that an agreed concession appears on the first invoice. A fictional renewal example makes the arithmetic concrete. Staying with the incumbent can be the right answer—but that decision deserves a clear owner and an explanation. The principle: scrutiny Before you ask how much the vendor can take off, establish what belongs on the bill. Turn the episode into action The Operational ITAM Store offers Bill’s paid procedures, toolkits, and decision resources to help make this work repeatable. Explore the Operational ITAM Store (https://www.operationalitam.com/store/). For broader coverage, the Software, SaaS & Cloud toolkit (https://www.operationalitam.com/store/index.php?page=product&sku=SAM) includes procedures, publisher playbooks, and tools for licensing, renewals, audit response, and consumption management. For a focused starting point, explore Plan renewals against the notice deadline (https://www.operationalitam.com/store/index.php?page=product&sku=C05), with an editable procedure, flowchart, and adoption checklist. Review the previews and product descriptions to choose the scope that fits your team. Your homework Give it about an hour. Choose one upcoming renewal and gather the quote, current agreement, latest invoice, and quantity evidence. Explain the change in cost on one page. Identify one line you cannot substantiate, then write down the question, the person who must answer it, and the deadline. Track the notice date separately from the renewal date. Next: The Decision Table Episode 015 brings ITAM, FinOps, procurement, finance, and service ownership into a working decision—with shared evidence, clear authority, and an owner for the next action. Selected sources Microsoft 365 pricing and packaging FAQ (https://www.microsoft.com/en-us/licensing/news/2026-M365-Packaging-Pricing-Updates-FAQ) Microsoft Partner Center: August 2026 announcements (https://learn.microsoft.com/en-us/partner-center/announcements/2026-august#csp-software-pricing-update-effective-october-1-2026) Broadcom: counting cores for VCF and VVF (https://knowledge.broadcom.com/external/article/313548) Broadcom: perpetual licenses after support expiration (https://knowledge.broadcom.com/external/article/429208/perpetual-license-functionality-after-su.html) Oracle Java SE Universal Subscription FAQ (https://www.oracle.com/java/technologies/java-se-subscription-faq.html) Oracle: JDK 21 approaches the end of its permissive license (https://blogs.oracle.com/java/jdk-21-approaches-end-of-permissive-license) Microsoft licensing FAQ on Teams (https://www.microsoft.com/licensing/faqs/10) Research checked September 25, 2026. The renewal arithmetic example is fictional. Customer-specific licensing rights depend on the applicable agreements. Visit Operational ITAM (https://www.operationalitam.com/) © 2026 Operational ITAM · A brand of EpicB Media LLC. All Rights Reserved.

5. 

   18 Sept 2026

   The Standards Body: FOCUS Put Our Name on the Door

   The FinOps people wrote the bill down as a standard and invited ITAM in. Here is how to speak FOCUS before your CFO asks. On June fourth the FOCUS Steering Committee ratified version 1.4 of the FinOps Open Cost and Usage Specification: two new datasets, forty-seven new columns, and an Invoice Detail dataset that joins a consumption record to the physical invoice on one identifier. The same month the Linux Foundation announced Tokenomicon, a conference whose front page names tokenomics, FinOps, and ITAM practitioners in the same sentence. The meter readers built themselves a language. Then they walked across the building to our side, and put our name on the door. Bill walks into the second room of the Grid, the standards body, and breaks down what FOCUS means for ITAM: the eight columns out of sixty-five you actually need, the handful of tests any standard has to pass before you bet a program on it, the ISO 19770-3 entitlement tag he has never once received from a publisher, and the five steps that get a SaaS and licensing estate speaking the language, including the one only ITAM can do. Along the way: what the State of FinOps 2026 survey says about who now reports on licensing and the data center, UnitedHealth Group expressing a VMware data center in FOCUS, and the 1904 Baltimore fire that explains why your vendor's billing format is a thread pitch. Plus, a listener question from Angela in Madison: the cloud FinOps team told the CFO that cloud spend is FOCUS-reconciled, and the CFO wants to know why ITAM's SaaS and licensing numbers cannot be. What do you actually say? IN THIS EPISODE FOCUS 1.4 explained for ITAM: the release history, the eight columns that matter, and how last week's effective rate became Effective Cost over Pricing Quantity The provider table as of this week: who ships 1.2, who ships 1.3, nobody ships 1.4, and why "conformant" currently means self-declared ISO 19770 held up against the same tests, and an opinion, clearly labeled: FOCUS will become the language ITAM reports cost in, and what it will never carry Five steps to speak FOCUS: ask which version, learn the columns, put your contract register in the Contract Commitment dataset, run it in parallel, and put the export in the contract What FOCUS 1.5 brings in December, the Great Baltimore Fire of 1904, and the one-hour homework that produces your first invoice in the language CHAPTERS (00:03) - Standards Body Visit (01:27) - The FOCUS Standard (03:56) - Core Columns (07:46) - AI Billing Examples (09:38) - ITAM Workflow (15:01) - Baltimore Hydrant Lesson (17:02) - Trust Is the Standard (18:41) - Next Rate Case TRANSCRIPT Click here to view the episode transcript. (https://share.transistor.fm/s/29de0a37/transcript) SOURCES & FURTHER READING Introducing FOCUS 1.4, FinOps Foundation (June 2026): https://www.finops.org/insights/introducing-focus-1-4/ (https://www.finops.org/insights/introducing-focus-1-4/) What is FOCUS, release history and license: https://focus.finops.org/what-is-focus/ (https://focus.finops.org/what-is-focus/) FOCUS provider support table: https://focus.finops.org/docs/implementation/get-started/get-started-with-focus-datasets/ (https://focus.finops.org/docs/implementation/get-started/get-started-with-focus-datasets/) FOCUS 1.5 release scope: https://focus.finops.org/focus-1-5-release-scope/ (https://focus.finops.org/focus-1-5-release-scope/) FOCUS practitioner stories, UnitedHealth Group and STMicroelectronics: https://focus.finops.org/adoption/finops-practitioners/ (https://focus.finops.org/adoption/finops-practitioners/) Linux Foundation announces Tokenomicon (June 2026): https://www.linuxfoundation.org/press/linux-foundation-announces-tokenomicon-a-new-conference-for-the-economics-of-ai (https://www.linuxfoundation.org/press/linux-foundation-announces-tokenomicon-a-new-conference-for-the-economics-of-ai) State of FinOps 2026, Linux Foundation / FinOps Foundation: https://www.linuxfoundation.org/press/state-of-finops-survey-ai-value-and-skills-top-priorities-as-finops-matures-across-technology-value-98-manage-ai-90-saas-64-licensing-48-data-center-1 (https://www.linuxfoundation.org/press/state-of-finops-survey-ai-value-and-skills-top-priorities-as-finops-matures-across-technology-value-98-manage-ai-90-saas-64-licensing-48-data-center-1) NISTIR 7158, Major U.S. Cities Using National Standard Fire Hydrants, One Century After the Great Baltimore Fire (NIST, 2004): https://tsapps.nist.gov/publication/get_pdf.cfm?pub_id=861321 (https://tsapps.nist.gov/publication/get_pdf.cfm?pub_id=861321) ABOUT THE SHOW Operational ITAM is a podcast about the unglamorous machinery of enterprise technology — hardware and software asset management, licensing, audit defense, SaaS governance, and the money quietly leaking out of all of them. Bill Van Nort has led IT asset management, end-user computing, IT operations, and workplace technology at large organizations across banking, mortgage, and automotive. He has reclaimed millions in software spend and survived audits from the biggest publishers on the planet. Consulting enquiries and listener case files: operationalitam.com The Operational ITAM Podcast is an EpicB Media LLC production.

6. 

   3 Sept 2026

   The Meter Room: Read the Meter Before the Invoice Does

   AI consumption pricing turned software cost into a meter. Here is how to read yours before the bill does. Software used to be priced at the signature. Now it accrues at the meter. Ramp's payments data shows AI token spend up twenty point seven times in thirteen months, and the FinOps Foundation reports ninety-eight percent of practitioners now manage AI spend, up from thirty-one percent two years ago. A seat is a price you approved once. A meter is a price you discover every month. Bill walks into the first room of the Grid, the meter room, and breaks down the four parts of every consumption agreement: the unit, the rate, the commitment, and the true-up. Along the way: why the median business pays two thousand dollars a month while the average pays one hundred forty thousand, how Coinbase cut its AI bill nearly in half while usage grew, the controller who found ten thousand dollars a month in a term he had never heard, and the arithmetic that turns any invoice into a meter reading. Plus, a listener question from Elena in Cincinnati: finance wants next year's AI budget as one fixed number, and consumption pricing makes that feel impossible. What do you actually give them? IN THIS EPISODE The anatomy of a meter: the unit, the rate, the commitment, and the true-up, and why you need all four named for every consumption agreement you own Ramp's April benchmarks: a sixty-times gap between median and average AI spend, and the twenty-times price difference decided by a model default How Coinbase halved AI spend while usage grew: better defaults, routing, and caching, not friction and spend alerts The AngelList controller who learned the phrase "prompt caching" from a spend briefing and recovered ten thousand dollars a month the same day The three numbers to hand finance instead of one fixed budget, and the one-hour homework that produces your first meter reading CHAPTERS (00:15) - Meter Room Opens (01:16) - Reading the New Bill (04:12) - What a Meter Is (07:32) - Real-World Savings (09:31) - How to Read Usage (12:55) - Budgeting the Unknown (14:21) - Utility Lessons (15:48) - Measurement Discipline (16:38) - Homework and Next Steps TRANSCRIPT Click here to view the episode transcript. (https://share.transistor.fm/s/f7ed88d6/transcript) SOURCES & FURTHER READING Ramp, AI token spend controls launch (July 2026): https://www.prnewswire.com/news-releases/ramp-launches-ai-token-spend-controls-302827389.html (https://www.prnewswire.com/news-releases/ramp-launches-ai-token-spend-controls-302827389.html) Ramp, AI token cost benchmarks (April 2026 data): https://ramp.com/blog/ai-token-cost-for-businesses (https://ramp.com/blog/ai-token-cost-for-businesses) State of FinOps 2026, Linux Foundation / FinOps Foundation: https://www.linuxfoundation.org/press/state-of-finops-survey-ai-value-and-skills-top-priorities-as-finops-matures-across-technology-value-98-manage-ai-90-saas-64-licensing-48-data-center-1 (https://www.linuxfoundation.org/press/state-of-finops-survey-ai-value-and-skills-top-priorities-as-finops-matures-across-technology-value-98-manage-ai-90-saas-64-licensing-48-data-center-1) Coinbase CEO Brian Armstrong on cutting AI cost: https://finance.yahoo.com/markets/crypto/articles/coinbase-ceo-halved-ai-costs-130000536.html (https://finance.yahoo.com/markets/crypto/articles/coinbase-ceo-halved-ai-costs-130000536.html) FOCUS 1.4, FinOps Foundation: https://www.finops.org/insights/introducing-focus-1-4/ (https://www.finops.org/insights/introducing-focus-1-4/) ABOUT THE SHOW Operational ITAM is a podcast about the unglamorous machinery of enterprise technology — hardware and software asset management, licensing, audit defense, SaaS governance, and the money quietly leaking out of all of them. Bill Van Nort has led IT asset management, end-user computing, IT operations, and workplace technology at large organizations across banking, mortgage, and automotive. He has reclaimed millions in software spend and survived audits from the biggest publishers on the planet. Consulting enquiries and listener case files: operationalitam.com (https://operationalitam.com) The Operational ITAM Podcast is an EpicB Media LLC production.

7. 

   27 Aug 2026

   The AI Estate: The First Asset Class With a Regulator Attached

   The EU AI Act's Article 50 transparency obligations began to apply on August 2, with penalties up to 15 million euros or 3 percent of worldwide annual turnover, whichever is higher. It is the first time in the history of this discipline that an asset class arrived with a regulator already attached, and most organizations cannot tell you what is in it. Flexera's 2026 State of ITAM Report puts accurate AI visibility at 31 percent, while the FinOps Foundation's State of FinOps 2026 found 98 percent of FinOps teams now manage AI spend and 73 percent blew through their AI cost plans. This episode delivers on the promise made at the end of Episode 10: defining the newest asset class in the estate. Bill lays out the five forms AI takes on its way into your organization: embedded (AI switched on inside software you already own), subscribed (standalone AI SaaS), metered (consumption-priced APIs where spend scales with enthusiasm), hosted (models you run yourself), and hidden (all four, unrecorded). Then the four questions from Episode 1, pointed at the AI estate: what you have across five forms, where your data actually goes, what it costs across five different budget lines, and when it leaves, faster than any asset class ever tracked. Then the regulator in practitioner terms: the four Article 50 situations, the December 2, 2026 marking transition, the honest note on Article 26's deferral to December 2, 2027, and why every transparency obligation presupposes an inventory. Plus a listener question from Priya in Ann Arbor on where a CIO-mandated AI inventory even starts, the library closing with full honors as the show moves into the grid, and a one-hour shadow AI census: expense data, SSO log, asset register, three numbers on one page. Sources cited: EU AI Act Article 50 and European Commission implementation guidelines (July 20, 2026); EU Digital Omnibus; Flexera 2026 State of ITAM Report; FinOps Foundation State of FinOps 2026; IBM Cost of a Data Breach Report 2026; Zylo 2026 SaaS Management Index. Case files wanted. One situation, one page, anonymized: what the constraint was, what you did, what happened. If you are the person who just got handed the AI inventory question, Bill especially wants yours. Details at https://www.operationalitam.com (https://www.operationalitam.com) Next episode: the meter room. Token-based pricing, GPU hours, and reading the meter before the invoice does. Chapters: (00:02) - AI’s Regulator Arrives (01:57) - The Numbers Behind AI Risk (04:06) - Five Forms of AI Assets (07:26) - The Four Questions Applied (10:13) - Article 50 Explained (12:53) - How to Inventory AI (14:45) - From Library to Grid Click here to view the episode transcript. (https://share.transistor.fm/s/189c0ed4/transcript) Operational ITAM Podcast · https://www.operationalitam.com (https://www.operationalitam.com) · Bill Van Nort on LinkedIn: https://www.linkedin.com/in/billvannort/ (https://www.linkedin.com/in/billvannort/)

8. 

   15 Aug 2026

   Do You Actually Need a Tool? The Readiness Test

   Flexera's 2026 State of ITAM Report says complete visibility into the IT estate has dropped to 36 percent, down eleven points across three years, over the same stretch that organizations bought more asset management tooling than at any point in the discipline's history. We bought more and saw less. This episode explains why, and answers the question Mike from Columbus asked back in Episode 001: should we buy a tool, and how would we know? Bill lays out the Readiness Test, five questions to answer honestly before any purchase order: Who owns the data? When two systems disagree, which one wins? Can you produce entitlements as documents? Does a lifecycle event change a record today, without a tool? Can someone write down what the tool is for, in one sentence, with a number in it? Fail any one and a platform makes your problems more expensive instead of more visible. Then the case for tools, made fairly: what platforms genuinely do well according to Gartner's January 2026 Market Guide, the estate where the tool is a license term rather than a maturity choice (IBM sub-capacity and ILMT), the honest cost picture, and the four signals that it is actually time to buy. Plus, a listener question from Dana in Dayton on what to do when the platform is live and nobody trusts it, the catalog room in the library, and a one-hour homework assignment that will save some organizations two years. Sources cited: Flexera 2026 State of ITAM Report; Gartner Market Guide for Software Asset Management Tools (January 2026); IBM Passport Advantage sub-capacity licensing terms; Forrester (2013); EU AI Act Article 50. Case files wanted. One situation, one page, anonymized: what the constraint was, what you did, what happened. Details at https://www.operationalitam.com Next episode: the AI estate, the first asset class to arrive with a regulator attached. Chapters: (00:03) - Tool Question Answered (04:31) - Readiness Test (07:42) - Market Tells On Itself (09:24) - What To Do Instead (11:22) - When Tools Make Sense (13:55) - When To Buy (16:45) - The Library Catalog Lesson (18:10) - Tooling Is Judgment (19:23) - Homework And Next Episode Click here to view the episode transcript. (https://share.transistor.fm/s/1b9edce9/transcript) Operational ITAM Podcast · https://www.operationalitam.com · Bill Van Nort on LinkedIn: https://www.linkedin.com/in/billvannort/

9. 

   4 Aug 2026

   Renewals: The Negotiation You Can Actually Win

   Microsoft gave everyone seven months of warning. Almost nobody had a plan. The gap between the memo and the plan is the whole episode. An audit arrives on somebody else's schedule. A settlement is negotiated from behind. Shadow IT happens whether you sanction it or not. Disposal's best possible outcome is that nothing happens to you. The renewal is different. It is the only recurring event in asset management where the date is known years in advance, where the other side needs something from you, and where you decide when the work begins. And we blow it consistently as a profession. This one is the 18-month clock — four positions, each with exactly one job — and the five traps written into paper you have already signed. The thesis is not subtle: in a renewal, timing beats tactics. The clever negotiator who starts 60 days out loses to the mediocre one who started 18 months out. Every lever in this episode takes months to build and four seconds to deploy. A listener in Indianapolis writes in six weeks from a renewal whose quote just doubled, and gets an honest answer rather than an encouraging one. IN THIS EPISODE - Why 61% of IT leaders cut a project or initiative to pay for unplanned software cost increases — renewals are now cancelling roadmap items, not headcount - Flat application counts and 8% more money: the growth is not sprawl anymore, it is price - The 18-month clock — count, decide, build, ask — and the 60-day cliff most programs are actually standing on - The version of shelfware that survives every audit and fails every business case: deployed, assigned, compliant, and completely idle - Why leverage is a documented, costed, credible answer to "and what if we don't" — and why it never has to be executed - Broadcom/VMware and Oracle Java as live worked examples, including opening quotes that overstated the actual footprint by 20 to 40% - Five traps: the notice window, the uplift clause, the co-term, the discount shell game, and the multi-year commitment - Why you should never negotiate against list price, and the one discipline that catches more money than every other tactic combined - The University of California walking away from Elsevier, and the single reason they could CHAPTERS (00:03) - Renewal Power Plays (03:15) - The 18-Month Clock (05:56) - VMware and Java Leverage (09:22) - Renewal Traps (13:58) - Six Weeks Left (15:46) - The Serials Department TRANSCRIPT Click here to view the episode transcript. (https://share.transistor.fm/s/9c3a4091/transcript) SOURCES & FURTHER READING Microsoft 365 pricing and packaging updates — the official notice. Announced 4 December, effective 1 July 2026, covering Enterprise, Business, Frontline, and Government commercial equivalents. Office 365 E3 moves from $23 to $26 per user per month, Microsoft 365 E5 from $57 to $60, with Frontline plans rising as much as 43%. https://www.microsoft.com/en-us/licensing/news/2026-m365-packaging-pricing-updates Zylo 2026 SaaS Management Index — 305 applications and roughly $55.7M average annual SaaS spend, up about 8% year over year on a flat application count. Also the source for 54% average license utilization, 79% of IT leaders seeing a renewal price increase, 78% hit with unexpected consumption or AI charges, and 61% cutting a project to absorb unplanned software cost. https://zylo.com/2026-saas-management-index VMware distributor Arrow says minimum software subs set to jump from 16 to 72 cores — The Register, 28 March 2025. The primary reporting on the minimum core-count change and the 20% penalty for subscriptions not renewed by the anniversary date. https://www.theregister.com/2025/03/28/arrow_vmware_licensing_change/ VMware Cloud Foundation — current product and licensing information https://www.vmware.com/products/cloud-infrastructure/vmware-cloud-foundation Oracle Java SE Universal Subscription — the per-employee licensing metric introduced in January 2023 https://www.oracle.com/java/java-se-subscription/ Organizations are parting ways with Oracle Java for open-source alternatives — IT Brew, 29 July 2025, reporting on the joint ITAM Forum and Azul survey of 500 IT and software asset management professionals, which found 79% of organizations have migrated away from Oracle Java or plan to. https://www.itbrew.com/stories/2025/07/29/organizations-are-parting-ways-with-oracle-java-for-open-source-alternatives OpenJDK distributions referenced in this episode: Eclipse Adoptium, Amazon Corretto, Azul Zulu, Red Hat build of OpenJDK, and the Microsoft Build of OpenJDK UC terminates subscriptions with the world's largest scientific publisher in push for open access — University of California, 2019. The Elsevier walk-away referenced in the library segment. https://www.universityofcalifornia.edu/press-room/uc-terminates-subscriptions-worlds-largest-scientific-publisher-push-open-access A note on evidence: settlement terms and negotiated pricing are almost universally covered by non-disclosure, so no public dataset of renewal outcomes exists. The advisory-firm figures on VMware settlement ranges and quote overstatement are reported observations rather than published research, and the negotiation guidance in this episode reflects thirty years on the customer side of the table. It is offered as practitioner knowledge, not as study findings. THE COMPANION TOOL The 90-Day Pre-Renewal Readiness Checklist executes what this episode describes — 57 checks across intake, waste signal analysis, business owner validation, and negotiation preparation, with an owner and an evidence artefact named for every item. Free, no email required. https://www.operationalitam.com/pages/resources.html RELATED EPISODES Episode 003 — Software Asset Management: Proving What You Own Episode 004 — Surviving a Software Audit, Part One: The Letter Lands Episode 005 — Surviving a Software Audit, Part Two: The Settlement LISTENER CASE FILES Got a renewal you cannot justify, or a notice window closing faster than your data is coming together? Send it over — anonymized, sanitized, no company names. Just the situation, what you did, and what happened. https://www.operationalitam.com/pages/podcast-ask.html ABOUT THE SHOW Operational ITAM is a podcast about the unglamorous machinery of enterprise technology — hardware and software asset management, licensing, audit defense, SaaS governance, and the money quietly leaking out of all of them. Bill Van Nort has led IT asset management, end-user computing, IT operations, and workplace technology at large organizations across banking, mortgage, and automotive. He has reclaimed millions in software spend and survived audits from the biggest publishers on the planet. Consulting enquiries and listener case files: operationalitam.com

10. 

    2 Aug 2026

    Surviving a Software Audit, Part One: The Letter Lands

    The first seventy-two hours decide the outcome. Five opening moves for the moment the audit notice arrives. Part one of two. The letter arrives — or, increasingly, the friendly invitation to a "SAM engagement" that is an audit wearing a nicer coat. What you do in the first seventy-two hours shapes everything that follows. Bill lays out five opening moves: contain it, read the contract, control the terms, build your own position before you share anything, and control the data. Along the way: which publishers audit most aggressively, why third-party audit firms are paid by the vendor and what that means for you, why unverified script output drives more inflated claims than actual non-compliance does, and the single most expensive instinct in this situation — panic-buying licenses after the notice arrives, which frequently doesn't count toward the findings anyway. Plus a listener question from Sandra in Grand Rapids on the soft-audit trap. Part two picks up when the findings document lands. IN THIS EPISODE - The five opening moves for the first seventy-two hours - Soft audits and "SAM engagement" invitations — the audit wearing a nicer coat - What your contract's audit clause actually permits, and what it doesn't - Why third-party audit firms are paid by the publisher, and what that changes - Building your own license position before you share a single data point - Controlling the data: what you provide, in what format, and what you never send - Why unverified script output drives more inflated claims than real non-compliance - The most expensive instinct in the room: panic-buying licenses after the notice - Which publishers audit most aggressively, and what the current data shows CHAPTERS (00:03) - Audit Defense Begins (02:11) - Audit Reality Check (05:10) - Five Opening Moves (08:00) - Negotiating Audit Terms (09:35) - Build Your Position (11:08) - Control the Data (13:29) - Settlement and Takeaways TRANSCRIPT Click here to view the episode transcript. (https://share.transistor.fm/s/c727725b/transcript) SOURCES & FURTHER READING Flexera 2026 State of ITAM Report — audit activity by publisher https://www.flexera.com/blog/it-asset-management/state-of-itam-2026/ ISO/IEC 19770-1 — IT Asset Management Systems https://www.iso.org/standard/68531.html Audit incidence and publisher behavior in this episode is drawn from licensing advisory practice and from thirty years of firsthand audit response. Where a figure rests on industry survey data rather than primary research, it is stated as such on air. ABOUT THE SHOW Operational ITAM is a podcast about the unglamorous machinery of enterprise technology — hardware and software asset management, licensing, audit defense, SaaS governance, and the money quietly leaking out of all of them. Bill Van Nort has led IT asset management, end-user computing, IT operations, and workplace technology at large organizations across banking, mortgage, and automotive. He has reclaimed millions in software spend and survived audits from the biggest publishers on the planet. Consulting enquiries and listener case files: operationalitam.com

11. 

    2 Aug 2026

    Welcome to Operational ITAM: Know What You Own

    Thirty years in enterprise IT, distilled into four questions every asset program has to answer. The pilot episode. Host Bill Van Nort opens the series with three decades of enterprise IT leadership behind him — banking, mortgage, automotive — and a straightforward thesis: buried inside a boring-sounding phrase are millions of dollars, real career leverage, and some of the best war stories in enterprise technology. This episode establishes the four fundamentals every program must answer: know what you have, know where it is, know what it costs, know when it leaves. Bill explains why asset management is ultimately a trust discipline rather than an inventory discipline, states his biases up front — evidence over enthusiasm, customer over publisher, simple over clever — and previews the season ahead. Plus: a listener question from Mike in Columbus on what to do when leadership says an ITAM tool isn't in the budget. IN THIS EPISODE - Why nobody notices asset management until it's broken - The four fundamentals: know what you have, where it is, what it costs, when it leaves - Why IT asset management is really about trust, not assets - How the same fifteen questions wear two hundred different outfits - Starting an ITAM program with no tool and no budget - What license compliance actually costs when nobody is keeping score - The show's format, biases, and what's coming this season CHAPTERS (00:23) - Podcast Opening (01:15) - Why Asset Counts Matter (02:05) - The Four Fundamentals (02:46) - Invisible Until Broken (03:16) - The Cost of Chaos (04:16) - Human Side of ITAM (05:01) - Show Format Explained (05:29) - Bill’s Background (06:17) - ITAM Is About Trust (06:59) - What’s Coming Next (07:16) - Start Without a Tool (08:04) - Why This Podcast Exists (08:45) - Show Biases and Principles (09:24) - Season Preview (10:09) - Listener Case Files (10:35) - Who This Show Isn’t For (11:01) - New Names, Same Discipline (11:46) - Closing Thanks (12:21) - Final Takeaway TRANSCRIPT Click here to view the episode transcript. (https://share.transistor.fm/s/92a4149a/transcript) FURTHER READING ISO/IEC 19770-1 — IT Asset Management Systems standard https://www.iso.org/standard/68531.html IAITAM — International Association of IT Asset Managers https://www.iaitam.org LISTENER CASE FILES Got a situation you'd like worked on air? Send it over — anonymized, sanitized, no company names. Real constraints, real politics, real budgets. operationalitam.com ABOUT THE SHOW Operational ITAM is a podcast about the unglamorous machinery of enterprise technology — hardware and software asset management, licensing, audit defense, SaaS governance, and the money quietly leaking out of all of them. Bill Van Nort has led IT asset management, end-user computing, IT operations, and workplace technology at large organizations across banking, mortgage, and automotive. He has reclaimed millions in software spend and survived audits from the biggest publishers on the planet. Consulting enquiries and listener case files: operationalitam.com

12. 

    31 Jul 2026

    The Last Mile: Disposal, Data Destruction, and Chain of Custody

    Ninety-five million dollars in penalties, a moving company that shouldn't have been there, and the standard that quietly changed nine months ago. At the end of life, a device stops being an asset and becomes a liability with a serial number. Disposal is the only gate in the lifecycle where getting it wrong doesn't cost you efficiency or budget — it costs you a regulator. This episode covers what actually changed when NIST published SP 800-88 Revision 2 in September 2025 and withdrew Revision 1 the same day: the shift from a device-by-device technical manual to a program-level governance framework, the deferral of technique detail to IEEE 2883, the retirement of degaussing and multi-pass overwriting, and new language on establishing trust in a vendor's implementation. Then the regulatory stack — GLBA, FACTA, HIPAA, PCI DSS, Sarbanes-Oxley, Regulation S-P — and why one device can sit under five frameworks at once. The centerpiece is a public enforcement case. Morgan Stanley paid $95 million across two regulators after handing roughly 4,900 devices to a moving and storage company with no data destruction experience. Devices reached an internet auction site with unencrypted customer information intact. Every control that failed was an asset management control. Plus a listener question from Marcus in Fort Wayne on whether wiping drives in-house before they reach the ITAD vendor is duplicated effort. IN THIS EPISODE - NIST SP 800-88 Revision 2 — published September 2025, Revision 1 withdrawn the same day - Why the media-specific tables were removed and what replaced them - Clear, Purge, Destroy — what survived and what didn't - Why degaussing and multi-pass overwriting are the wrong answer for modern media - Cryptographic erase, and why it's the one technique NIST kept - Should you wipe in-house before the ITAD vendor? A listener question - The Morgan Stanley case: $95 million, 15 million customers, 42 unaccounted servers - The regulatory stack, and why one device sits under five frameworks - R2v3, e-Stewards, and NAID AAA — what each actually verifies - The downstream gap auditors find over and over - What makes a certificate of destruction defensible, and what makes it worthless - Deaccession, the ledger, and why the shredder isn't the point CHAPTERS (00:03) - Disposal’s Hidden Liability (01:31) - NIST 800-88 Changes (05:47) - The $95 Million Failure (10:21) - Rules, Vendors, and Proof (15:50) - The Ledger Matters Most TRANSCRIPT Click here to view the episode transcript. (https://share.transistor.fm/s/732a157c/transcript) SOURCES & FURTHER READING NIST SP 800-88 Rev. 2 — current standard, published 26 September 2025 https://csrc.nist.gov/pubs/sp/800/88/r2/final NIST announcement and summary of changes from Revision 1 https://www.nist.gov/news-events/news/2025/09/guidelines-media-sanitization-nist-publishes-sp-800-88r2 NIST SP 800-88 Revision 1 — withdrawal notice https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-88r1.pdf IEEE 2883 — Standard for Sanitizing Storage https://standards.ieee.org/ieee/2883/10277/ SERI — R2v3 standard and certified facility directory https://sustainableelectronics.org e-Stewards certified recycler directory https://e-stewards.org/find-a-recycler/ i-SIGMA — NAID AAA certification https://isigma.org Note: NIST SP 800-88 Revision 1 (2014) was withdrawn and superseded in September 2025. A great deal of the ITAD guidance still circulating online cites the withdrawn version. LISTENER CASE FILES Got a situation you'd like worked on air? Send it over — anonymized, sanitized, no company names. Real constraints, real politics, real budgets. operationalitam.com ABOUT THE SHOW Operational ITAM is a podcast about the unglamorous machinery of enterprise technology — hardware and software asset management, licensing, audit defense, SaaS governance, and the money quietly leaking out of all of them. Bill Van Nort has led IT asset management, end-user computing, IT operations, and workplace technology at large organizations across banking, mortgage, and automotive. He has reclaimed millions in software spend and survived audits from the biggest publishers on the planet. Consulting enquiries and listener case files: operationalitam.com

13. 

    31 Jul 2026

    Hardware Refresh Cycles: The Great Debate

    Three years, four, or five? Three curves you can measure in your own environment — and why the confident numbers are the least trustworthy. Somebody in your organization decided how long a laptop lives. Ask where that number came from and you'll usually get "it's industry standard," "that's what the lease term was," or a long pause. Meanwhile it quietly determines a seven-figure line item every year. This episode doesn't hand you a number. It hands you a method. The Three Curves — failure, cost, and value — each measurable in your own environment from data you already have, and where they intersect is your refresh cycle rather than a vendor's. Along the way: why the widely quoted refresh statistics don't survive being traced to their sources, what actually fails in a modern laptop and why it's cheaper to fix than you think, the residual value you forfeit by stretching a cycle, and how the Windows 11 hardware requirements turned refresh from a hardware question into a platform runway question. Plus a listener question from Tony in Toledo, whose CFO wants to move from four years to six — and the argument that actually works in that meeting. IN THIS EPISODE - Why most refresh cycles have no documented origin - The provenance problem: tracing the widely quoted statistics back to dated or vendor-funded sources - Curve one — failure: what actually breaks in a modern laptop, and why it's rarely the drive - Curve two — cost: building your own support-cost-by-age curve in an afternoon - Why the cost curve turns upward exactly when the warranty expires - Curve three — value: the residual recovery you forfeit by stretching the cycle - Paying twice, in two different budgets, across an accounting seam - How Windows 11 hardware requirements changed refresh from hardware to platform runway - Buying for supported life rather than unit price - The AI PC question, and whether NPU capability justifies acceleration - Weeding the collection: why librarians never withdraw a book for turning four - Segmenting the fleet — why one cycle is wrong for most of your users CHAPTERS (00:03) - Refresh Debate Begins (02:22) - The Three Curves (04:09) - Failure and Cost (07:01) - Push Back with Data (07:22) - The Value Curve (08:46) - Security Changes the Game (11:01) - The Library Analogy (12:01) - Segment Your Fleet (12:39) - Refresh Is Economics (14:02) - Disposal Next Time TRANSCRIPT Click here to view the episode transcript. (https://share.transistor.fm/s/4495f6ff/transcript) SOURCES & FURTHER READING Microsoft — Windows 10 end of support https://www.microsoft.com/en-us/windows/end-of-support Microsoft — Windows 11 system requirements https://www.microsoft.com/en-us/windows/windows-11-specifications A note on evidence: the refresh statistics circulating in this field are unusually poorly sourced. Figures on failure rates and support costs for aging hardware typically trace back either to studies more than a decade old or to research funded by hardware manufacturers. This episode deliberately avoids quoting them. The Three Curves framework exists so you can measure your own environment instead of borrowing someone else's number. LISTENER CASE FILES Got a situation you'd like worked on air? Send it over — anonymized, sanitized, no company names. Real constraints, real politics, real budgets. operationalitam.com ABOUT THE SHOW Operational ITAM is a podcast about the unglamorous machinery of enterprise technology — hardware and software asset management, licensing, audit defense, SaaS governance, and the money quietly leaking out of all of them. Bill Van Nort has led IT asset management, end-user computing, IT operations, and workplace technology at large organizations across banking, mortgage, and automotive. He has reclaimed millions in software spend and survived audits from the biggest publishers on the planet. Consulting enquiries and listener case files: operationalitam.com

14. 

    31 Jul 2026

    Shadow IT: Reading the Demand Signal

    Unsanctioned software isn't a discipline problem. It's your users telling you what IT failed to deliver. The instinct is to treat shadow IT as rebellion — something to be found, blocked, and punished. That instinct is why it keeps happening. This episode reframes unsanctioned technology as a demand signal. Every credit card SaaS subscription is a documented case of someone needing a capability badly enough to solve it themselves. The security exposure and license liability are real, and this episode does not soften them. But the durable fix isn't enforcement; it's service. Bill covers how to find what's actually running, how to triage it by risk rather than by annoyance, and how to build an intake path fast enough that going around IT stops being the rational choice. The measure of an ITAM program isn't how much it prevents. It's how little anyone needs to go around it. IN THIS EPISODE - Why shadow IT is a demand signal, not a discipline problem - Business units now control the overwhelming majority of SaaS spend — and what that means - Finding what's actually running: expense reports, SSO logs, network data, and their blind spots - Triage by risk, not by annoyance — a practical severity model - The real exposure: data residency, license liability, and orphaned admin accounts - AI-native tools entering through expense reports faster than governance can respond - Building an intake path fast enough that going around IT stops making sense - Why enforcement-first programs generate more shadow IT, not less - Service as the organizing principle — measuring how little anyone needs to route around you CHAPTERS (00:02) - Hunting Shadow IT (03:22) - Shadow IT Costs (06:31) - Shadow AI Rises (09:20) - Finding Hidden Tools (11:30) - What To Do Next (14:20) - Refresh Debate Next TRANSCRIPT Click here to view the episode transcript. (https://share.transistor.fm/s/d0250e3c/transcript) SOURCES & FURTHER READING Zylo 2026 SaaS Management Index https://zylo.com/2026-saas-management-index Findings summary and methodology https://zylo.com/news/2026-saas-management-index Flexera 2026 State of ITAM Report https://www.flexera.com/blog/it-asset-management/state-of-itam-2026/ IBM Cost of a Data Breach Report https://www.ibm.com/reports/data-breach ABOUT THE SHOW Operational ITAM is a podcast about the unglamorous machinery of enterprise technology — hardware and software asset management, licensing, audit defense, SaaS governance, and the money quietly leaking out of all of them. Bill Van Nort has led IT asset management, end-user computing, IT operations, and workplace technology at large organizations across banking, mortgage, and automotive. He has reclaimed millions in software spend and survived audits from the biggest publishers on the planet. Consulting enquiries and listener case files: operationalitam.com

15. 

    30 Jul 2026

    Surviving a Software Audit, Part Two: The Settlement

    The findings document is an opening offer, not a verdict. How claims get inflated, and how settlements actually get made. Part two of two, picking up exactly where the last episode left off: the findings document has landed and the number on it is worse than you expected. That number is a negotiating position. This episode covers how publisher claims get inflated in the first place, why opening claims routinely land several times higher than eventual settlements, what the publisher actually wants out of this — which is rarely the cash figure in front of you — and how zero-cash resolutions get traded into renewal and subscription commitments instead. Audit defense ends in commerce. The practitioners who understand that walk away with a business outcome. The ones who treat it as a compliance verdict write the check. IN THIS EPISODE - Why the findings document is an opening position, not an invoice - How claims get inflated: measurement errors, wrong metrics, and unverified assumptions - Auditing the audit — challenging methodology before you challenge the number - What the publisher actually wants, and why it's rarely the cash figure - Zero-cash resolutions: trading findings into renewal and subscription commitments - Where the leverage sits, and the timing that determines who has it - Back maintenance, penalties, and which line items are genuinely negotiable - Getting it in writing: release language and what a settlement should close - Building the evidence discipline that prevents the next one CHAPTERS (00:02) - Audit Defense Payoff (02:43) - Claim Anatomy Unpacked (04:14) - Rebuild the Count (06:17) - Trading for Settlement (10:39) - Locking the Paper (11:44) - Fix the Leaks (12:27) - Library Fee Lesson (13:12) - Four-Part Audit Game TRANSCRIPT Click here to view the episode transcript. (https://share.transistor.fm/s/0770dc12/transcript) SOURCES & FURTHER READING Flexera 2026 State of ITAM Report https://www.flexera.com/blog/it-asset-management/state-of-itam-2026/ ISO/IEC 19770-1 — IT Asset Management Systems https://www.iso.org/standard/68531.html A note on evidence: software audit settlements are almost universally subject to non-disclosure terms, which means no public dataset of settlement outcomes exists. The negotiation guidance in this episode reflects licensing advisory practice and thirty years of firsthand experience on the customer side of the table. It is presented as practitioner knowledge, not as research. ABOUT THE SHOW Operational ITAM is a podcast about the unglamorous machinery of enterprise technology — hardware and software asset management, licensing, audit defense, SaaS governance, and the money quietly leaking out of all of them. Bill Van Nort has led IT asset management, end-user computing, IT operations, and workplace technology at large organizations across banking, mortgage, and automotive. He has reclaimed millions in software spend and survived audits from the biggest publishers on the planet. Consulting enquiries and listener case files: operationalitam.com

16. 

    30 Jul 2026

    Hardware Asset Management: The Seven Gates

    Request to disposal, gate by gate — what each stage captures, how each one fails, and why custody is the whole game. Hardware asset management is a custody discipline. This episode walks the full lifecycle gate by gate — request, procure, receive, deploy, maintain, recover, dispose — and applies the same three questions at every stage: what is this gate, what data has to be captured here, and how does it typically fail? Part two moves to the end of life, where the risk concentrates: data sanitization under NIST SP 800-88 Revision 2, what R2v3, e-Stewards, and NAID AAA certifications actually mean when you're selecting an ITAD vendor, the real economics behind refresh cycle decisions, and ghost assets — the machines your records insist you still own. If your inventory can't survive a simple question about where a specific laptop is today, this is the episode that fixes it. IN THIS EPISODE - The seven gates of the hardware lifecycle: request, procure, receive, deploy, maintain, recover, dispose - What data has to be captured at each gate, and how each one typically fails - Ghost assets: why your records insist you own machines that left two years ago - Refresh cycle economics, and what the failure-rate data actually supports - Data sanitization under NIST SP 800-88 Revision 2, and why Revision 1 is withdrawn - Choosing an ITAD vendor: what R2v3, e-Stewards, and NAID AAA actually certify - Why degaussing and multi-pass overwriting are the wrong answer for modern flash media - Custody as the organizing principle behind every hardware asset decision CHAPTERS (00:03) - HAM Lifecycle Overview (01:40) - Request and Approval (02:48) - Procurement Records (04:00) - Receiving the Asset (05:01) - Deployment and Assignment (06:22) - Maintenance Insights (07:32) - Asset Recovery (09:03) - Secure Disposal (12:59) - Refresh Strategy (14:26) - Ghost and Zombie Assets (15:36) - Library Analogy (16:19) - Custody Discipline TRANSCRIPT Click here to view the episode transcript. (https://share.transistor.fm/s/e369e4c0/transcript) SOURCES & FURTHER READING NIST SP 800-88 Rev. 2, Guidelines for Media Sanitization (current standard, September 2025) https://csrc.nist.gov/pubs/sp/800/88/r2/final Full text (PDF) https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-88r2.pdf IEEE 2883 — Standard for Sanitizing Storage https://standards.ieee.org/ieee/2883/10277/ SERI — R2v3 standard and certified facility directory https://sustainableelectronics.org e-Stewards certified recycler directory https://e-stewards.org/find-a-recycler/ i-SIGMA — NAID AAA certification https://isigma.org Note: NIST SP 800-88 Revision 1 (2014) was withdrawn and superseded in September 2025. Much of the ITAD guidance circulating online still cites the withdrawn version. ABOUT THE SHOW Operational ITAM is a podcast about the unglamorous machinery of enterprise technology — hardware and software asset management, licensing, audit defense, SaaS governance, and the money quietly leaking out of all of them. Bill Van Nort has led IT asset management, end-user computing, IT operations, and workplace technology at large organizations across banking, mortgage, and automotive. He has reclaimed millions in software spend and survived audits from the biggest publishers on the planet. Consulting enquiries and listener case files: operationalitam.com

17. 

    29 Jul 2026

    Software Asset Management: Proving What You Own

    Installs are not entitlements. Building an Effective License Position, and why the gap between the two is where the money hides. Crossing over to the intangible side of the house. Where hardware asset management is about custody, software asset management is about evidence — and the evidence standard is considerably higher, because the party asking to see it has a financial interest in the answer. This episode covers the discipline of reconciling what's deployed against what you're entitled to deploy: how publisher licensing metrics actually work, why an installation count is not a license position, and how to construct an Effective License Position that holds up when someone external is checking your arithmetic. The homework matters more than usual on this one. The entitlement library you build here is the same document that determines how the next two episodes go for you. IN THIS EPISODE - Why software asset management is an evidence discipline, not an inventory discipline - Entitlements versus installations, and why counting deployments proves nothing - How publisher licensing metrics actually work — per-user, per-device, per-core, per-employee - Building an Effective License Position that survives external scrutiny - Oracle's per-employee Java licensing and what it changed - VMware under Broadcom: subscription-only, per-core, and the sixteen-core minimum - Where the money hides: unused licenses, wrong editions, and unclaimed downgrade rights - The entitlement library — your homework, and the foundation for audit defense CHAPTERS (00:02) - Software Asset Basics (03:26) - Entitlements and Proof (05:30) - Deployment Discovery (08:08) - Audit Threats (13:13) - SaaS Waste (16:04) - Evidence Over Custody TRANSCRIPT Click here to view the episode transcript. (https://share.transistor.fm/s/f38c5c28/transcript) SOURCES & FURTHER READING Oracle Java SE Universal Subscription (per-employee licensing) https://www.oracle.com/java/java-se-subscription/ Broadcom / VMware Cloud Foundation licensing https://www.broadcom.com/products/software/vmware-cloud-foundation Zylo 2026 SaaS Management Index https://zylo.com/2026-saas-management-index Flexera 2026 State of ITAM Report https://www.flexera.com/blog/it-asset-management/state-of-itam-2026/ ISO/IEC 19770-1 — IT Asset Management Systems https://www.iso.org/standard/68531.html ABOUT THE SHOW Operational ITAM is a podcast about the unglamorous machinery of enterprise technology — hardware and software asset management, licensing, audit defense, SaaS governance, and the money quietly leaking out of all of them. Bill Van Nort has led IT asset management, end-user computing, IT operations, and workplace technology at large organizations across banking, mortgage, and automotive. He has reclaimed millions in software spend and survived audits from the biggest publishers on the planet. Consulting enquiries and listener case files: operationalitam.com

Reach and audience

Public platform figures. Ratings count people who left a rating, not total listeners.

Apple Podcasts (US)

5.0 / 5

2 ratings

Spotify

5.0 / 5

1 ratings

Contact Operational ITAM Podcast

Guest appearances

Does not typically book guests

Based on episode analysis; this does not confirm that the show is currently accepting guests.