The Hardware Asset Reality Check

Teaching composite — not a claim about a named organisation or measured outcome. A 350-person engineering company wants an internal assistant that summarises maintenance manuals and drafts work-order notes. The IT team says there is already a virtualisation cluster, a 10 Gb network, identity management, backups and unused rack space. A business sponsor therefore assumes that 'we already have the infrastructure' and asks procurement to buy a GPU.

The infrastructure lead finds a more nuanced picture. Identity, network monitoring and document storage may be reusable, but the candidate server has no suitable accelerator, the rack's power and cooling headroom are unverified, and the backup route was designed for office systems rather than a shared model service. The assistant also needs to handle long manuals during the morning planning peak. The decision is not whether existing assets have value; it is which parts actually meet the proposed service requirement and which create a hidden bottleneck or operating obligation.

The CIO asks for a one-page asset-and-gap view before approving any purchase: user journey, permitted data route, existing components, constraints, incremental additions, recurring operation, and the representative test that would prove the design is adequate.