YS Infomatics

Insights · 12 September 2026 · 6 min read

Why spreadsheets fail at IP address management — and what to replace them with

How data-centre and critical-infrastructure teams outgrow spreadsheet IPAM, the failure modes that follow, and the design of a purpose-built inventory and IP management platform.

Every network starts in a spreadsheet

IP address management almost always begins as a tab in a workbook: a supernet, a list of subnets, a column of VLAN IDs, a column of owners. It works — until the environment grows past what one person can hold in their head. At that point the spreadsheet stops being a source of truth and becomes a source of incidents.

The failure modes are predictable

  • Duplicate allocations, because two engineers copied the same free range on the same afternoon.
  • Stale entries — decommissioned devices still 'own' addresses nobody dares reuse.
  • No link between the address plan, the physical inventory and the project that requested the change.
  • Zero audit trail: nobody can say who changed what, or why, six months later.
  • Design reviews that depend on a specific person being available to interpret the sheet.

What a purpose-built platform needs to model

Commercial IPAM tools exist, but for large programmes with their own delivery structure they often either do too much or model the wrong things. When we built an inventory and IPAM platform for a critical-infrastructure programme, the requirements that mattered were structural rather than exotic:

  • Hierarchical supernets and subnets with automatic free-space calculation and conflict prevention.
  • Device and interface addressing tied to a physical inventory — rack, site, role, lifecycle state.
  • VLAN and VRF tracking alongside the address plan, not in a separate tab.
  • Project and change visibility: which programme of work requested which allocation.
  • Role-based access, full history, and exports engineers actually want (CSV, API, config-generation inputs).

Software and network expertise in the same room

The hard part of infrastructure tooling is not the code — it is knowing which abstractions match how network engineers really work. A platform designed by people who have run data-centre fabrics avoids the friction that makes teams drift back to the spreadsheet. That combination of application engineering and infrastructure architecture is the core of how we work.

More insights