Data Center CMMS

Data Center Asset Register: From Commissioning to CMMS

Move assets from construction and commissioning into the CMMS with a validated structure, then reuse that structure across data halls, buildings and campuses.

What the register needs before handover to operations

A data center asset register is ready for handover when operations can plan and carry out maintenance from it without going back to the construction files. For each maintainable asset, it needs:

  • A unique tag that matches the labels on site and the as-built drawings
  • A place in an agreed data center asset hierarchy, with position and physical unit kept distinct
  • An equipment class and the attributes required for that class
  • Manufacturer, model, serial number, installation date and warranty end date
  • A criticality rating based on what the asset supports
  • Links to its documents, commissioning records and spare parts
  • Maintenance tasks ready to load as PM plans in the CMMS

The same discipline applies whether you call the facility a data center or a data centre: the register has to be complete and consistent before the contractor's team moves on.

Handover data from construction and commissioning

Data handed over to operations commonly arrives in many formats from many contractors. Typical inputs are:

  • Equipment schedules and contractor asset lists
  • As-built drawings and single-line diagrams
  • Operation and maintenance manuals, including manufacturer maintenance recommendations
  • Commissioning and test records
  • Warranty terms, spare parts lists and supplier contacts

The usual problem is that these sources disagree. The same unit can carry one tag in the design model, another in the contractor's list and a third on the commissioning sheet. Agree one tagging convention and reconcile every source to it before anything is loaded.

Worked example: one UPS system

This is an illustrative example of how one UPS system could be structured. The site, tags and values are fictional, and every project should confirm them against its own design and manufacturer data.

Practical hierarchy

Campus 1
 └── Building A
      └── Electrical Distribution, Path A
           └── UPS-1A (UPS system)
                ├── UPS-1A-M1 (UPS module 1)
                ├── UPS-1A-M2 (UPS module 2)
                ├── UPS-1A-SBS (Static bypass)
                ├── UPS-1A-BAT1 (Battery string 1)
                └── UPS-1A-BAT2 (Battery string 2)

Key equipment attributes

GroupAttributes to capture
IdentityTag UPS-1A, manufacturer, model, serial number
RatingRated capacity in kVA and kW, input and output voltage
ConfigurationTopology, number of modules, redundancy arrangement
BatteriesChemistry, number of strings, design autonomy
ConnectionsUpstream switchboard, downstream distribution, associated path
HandoverInstallation date, warranty end date, commissioning record reference

Criticality

UPS-1A protects the critical load on Path A, so it would normally rate high on consequence of failure. Redundancy may lower the immediate consequence of a single failure, but it also means a fault can go unnoticed, which makes hidden failures important to the assessment. The rating should follow your own criticality matrix.

Example PM task groupings

Set intervals from manufacturer recommendations and your own operating context.

Task groupScope
Routine inspectionVisual condition, alarm and event log review, environmental checks
Battery conditionString inspection, condition testing and trend review
Thermal and electricalThermal survey of connections, measurements against commissioning baseline
Life-limited componentsPlanned condition review or replacement of fans and capacitors
Functional testingBypass and transfer tests in a controlled maintenance window
Specialist serviceManufacturer service visits and firmware review

How the UPS example could map to Maximo and SAP PM

These are possible patterns for a data center CMMS, not fixed rules.

UPS exampleMaximoSAP PM
Campus and buildingSite and top-level locationsPlant and upper functional locations
Electrical pathLocation, within a systemFunctional location
UPS-1A positionLocationFunctional location
UPS-1A physical unitAsset installed at the locationEquipment installed at the functional location
UPS modulesChild assetsSub-equipment
Battery stringsChild assetsSub-equipment
Fans and capacitorsItems on the spare parts listMaterials on the equipment BOM
PM task groupsJob plans and PMsTask lists and maintenance plans

One validated template across halls, buildings and campuses

Repeat builds are where a validated structure pays back. Prove the hierarchy, class attributes and tagging convention on one data hall, and treat that as the standard for the next hall, building or campus. Each new phase then only has to supply its own tags, serial numbers and commissioning records.

AssetStage is a data staging workspace for this work. You can bring in spreadsheets, vendor documents and CMMS exports, build the hierarchy visually, and validate it for duplicates, missing fields and hierarchy violations before export. For maintenance, link assets to a template strategy and change it once. The change reaches every asset that shares it, with a diff to preview and a rollback if it is wrong.

Using criticality, FMEA and RCM outputs to inform PM plans

Criticality shows where to focus the analysis. AssetStage supports FMEA with ISO 14224 coding, an equipment-class failure-mode library and a governed decision tree for selecting tasks. Accepted tasks can then be promoted into import-ready Maximo and SAP PM job plans and PMs, each traceable to its decision.

For equipment that is less critical or well understood, you may not need a full study. AssetStage can also standardise PMs across identical assets. See the RCM workflow.

Set up equipment classes for your register

The free ISO 14224 for Non-Oil & Gas Industries guide includes a section on applying equipment classes to data center plant.

Download the Guide

Planning a handover? Talk to us about your data.