Parent folderOpen Confluence

RWS Architecture article

DCIM

Deliver a Datacenter Infrastructure Management system of record for assets, racks, power, IPAM, and automation integrations.

  1. Typeworkpackage
  2. Statusplanned
  3. Domainnetwork
On this page
  1. WP-02 DCIM
  2. Summary
  3. Scope
  4. Architecture Context
  5. Decision Context
  6. Dependencies
  7. Acceptance Criteria

WP-02 DCIM

Summary

Deliver a Datacenter Infrastructure Management system of record for assets, racks, power, IPAM, and automation integrations.

Scope

  • Establish authoritative inventory records for racks, devices, interfaces, cables, VLANs, and IP allocations used by DC3.0 automation.
  • Define and enforce a minimum NetBox data contract for in-scope spine/leaf/border devices.
  • Implement API-driven allocation workflows for management IPs, loopbacks, and point-to-point links.
  • Integrate NetBox-backed dynamic inventory into Cisco NX-OS generation and deployment workflows.
  • Provide migration exception handling and reconciliation controls for assets that cannot be normalized in the first wave.

Architecture Context

Decision Context

Dependencies

Acceptance Criteria

  • 100% of in-scope Location B spine/leaf/border devices exist in NetBox with required role/platform/site/ASN metadata.
  • 100% of in-scope uplinks, peer links, and management interfaces are modeled with interface and cabling records.
  • Address allocations for management, loopback, and underlay point-to-point links are executed through API-driven workflows with zero allocation collisions.
  • Dynamic inventory generation from NetBox returns all in-scope devices in correct role groups before each production deployment window.
  • Render/deploy pipeline blocks when required NetBox fields are missing, inconsistent, or outside policy constraints.
  • Brownfield exceptions are documented with owner and expiry date, and are reduced sprint over sprint.