Parent folderOpen Confluence

RWS Architecture article

Datacenter Infrastructure Management

Datacenter Infrastructure Management is the product-neutral architecture building block for inventory, topology, and infrastructure source-of-truth management. It states what DC 3.

  1. Typeabb
  2. Statuscandidate
  3. Domainnetwork
On this page
  1. ABB Datacenter Infrastructure Management
  2. Summary
  3. Capabilities
  4. Constraints
  5. Service Description
  6. Roadmaps
  7. Landing Zones
  8. Interfaces
  9. Dependencies
  10. EIRA Alignment
  11. Available SBB's

ABB Datacenter Infrastructure Management

Summary

Datacenter Infrastructure Management is the product-neutral architecture building block for inventory, topology, and infrastructure source-of-truth management. It states what DC 3.0 needs from this capability before a concrete SBB, product, or operating model is selected.

Capabilities

  • Provides inventory, topology, and infrastructure source-of-truth management.
  • Defines the functional, technical, security, and quality expectations that SBBs must satisfy.
  • Keeps service ownership, interfaces, and consumption boundaries visible before product selection.
  • Enables traceability from architecture intent to implementation, operational evidence, and consuming services.

Constraints

  • The resulting SBB must fit the datacenters ownership model and document the support, lifecycle, and service-management boundary.
  • Security, privacy, logging, evidence, and compliance controls must be explicit enough to assess BIO2-aligned implementation where applicable.
  • Authoritative inventory data must be maintained through controlled workflows and not duplicated in unmanaged spreadsheets.
  • SBBs must expose APIs that automation and validation tooling can consume.

Service Description

This ABB offers a DCIM service that records infrastructure assets, topology, addressing context, and operational ownership for DC 3.0. It is consumed by solution architects, platform teams, and service owners as the capability contract for selecting and shaping SBBs.

The service description remains implementation-neutral: product selection, hosting pattern, detailed runbooks, and service levels belong in the mapped SBB and related ADRs.

Roadmaps

  • Baseline: confirm scope, service ownership, constraints, and acceptance criteria for Datacenter Infrastructure Management.
  • MVP: validate the mapped SBB implementation and record the selected support and lifecycle model.
  • Next: add measurable service levels, evidence requirements, and roadmap dependencies once the SBB is selected.

Landing Zones

  • Private cloud and central DC 3.0 landing zone for core infrastructure and platform services.
  • Government cloud or external cloud landing zones only when the SBB documents the required control set, connectivity model, and data classification fit.

Interfaces

  • Inventory and topology APIs.
  • IPAM and network source-of-truth interfaces.
  • Automation, reporting, and audit exports.

Dependencies

  • Depends on dns-dhcp-ipam for a supporting capability or integration boundary.
  • Depends on dc-network-structure for a supporting capability or integration boundary.
  • Depends on automation for a supporting capability or integration boundary.
  • Implemented by netbox as currently mapped SBB traceability.
  • Consuming ABB and SBB dependencies must be recorded as links when solution design identifies concrete upstream or downstream use.

EIRA Alignment

Available SBB's