Defining the asset universe at Northbridge Logistics
Northbridge Logistics operates 14 depots, 320 leased trucks fitted with telematics, 2,400 laptops and tablets, 60 handheld warehouse scanners, 35 on-premises servers, 12 conveyor controllers managed by engineering, and 90 SaaS subscriptions discovered by finance. The CFO has committed to a 15% technology cost reduction and wants a single asset register. The CIO wants one source of truth for service and security decisions. Finance pays SaaS invoices but cannot link most subscriptions to an owner or business service. Fleet manages telematics contracts outside IT. Engineering refuses to hand over conveyor controllers, saying they are operational technology, not IT. The service desk cannot tell which laptop is with which user after a depot closure. No scope statement exists for ITAM, and the first steering meeting is in two weeks.
1. Recommend what Northbridge should include in the ITAM scope and what should remain outside but interfaced. Justify the boundary using asset management principles rather than ownership politics.
Read the worked answer
Scope should be set by management accountability, value at risk, and service dependency, not by who currently holds the budget. Include in the register the endpoints, servers, scanners, SaaS subscriptions that create contractual or data risk, and telematics where IT supports the service. For conveyor controllers, include them as CIs in the configuration management system and as asset records only if IT or a shared asset function is accountable for their lifecycle cost, security patching, or replacement. If engineering retains accountability, define an interface: engineering owns engineering data, while ITAM owns the linked CI and the contract and asset identifiers needed for service impact.
Use criteria: an item belongs in scope if it has material cost, contractual or licensing exposure, security or regulatory risk, or a dependency in a service. Exclude purely operational items only by explicit agreement, recorded as an interface. This prevents scope by politics and gives the steering group a defensible boundary. SaaS must be in scope because finance is paying but cannot link owners; unmanaged subscriptions are a classic value leak.
2. How should the ITAM manager demonstrate value to the CFO and CIO in the first 90 days? Give measures and the reasoning behind them.
Read the worked answer
Value should be expressed in decisions enabled and risk reduced, not record counts. Useful measures are: spend under management, meaning the percentage of SaaS and hardware spend linked to an owner and contract; license position, including true-up exposure and utilization; untracked assets, measured as discovery-versus-register variance; lifecycle risk, such as assets past end-of-support; recovery value from reuse, resale, and disposal; and audit findings closed. The reasoning is that the CFO cares about avoidable spend and cash recovery, while the CIO cares about service and security exposure. Report a baseline in week two, then a trend. Do not claim savings before they are realized. A first 90-day win could be cancelling duplicate SaaS and reconciling the depot-closure laptops. That builds credibility for the harder OT boundary debate.
3. Explain how you would distinguish an IT asset record from a configuration item for the conveyor controllers and SaaS subscriptions.
Read the worked answer
An asset record is primarily financial and lifecycle: what it is, what it cost, who owns it, the contract, location, status, and disposal. A CI is a configuration record describing how an item contributes to a service, including relationships and attributes needed for change, incident, and security. For conveyor controllers, the asset record may capture purchase, warranty, and replacement cost; the CI captures firmware, network segment, dependency on the warehouse service, and patch status. If engineering owns the financial record, ITAM still needs a CI link. For SaaS, the subscription is an asset (contract, seats, cost, renewal); the CI might be the tenant, integration, or business-service dependency. One physical or logical thing can have both records, linked by a stable identifier. Forcing one record to serve both purposes causes exactly the data-quality problems Northbridge is already seeing.