Background: The implementation of a Data Center Infrastructure Management (DCIM) software system enables real-time asset management information for computing resources and supporting infrastructure in UI enterprise data centers. Where authorized and security enabled, DCIM data will be available on a read only basis to existing data center tenants, including colocation partners.
We’ve implemented an open source DCIM software tool called openDCIM. For phase one, openDCIM will contain data from existing excel spreadsheets (to be retired), plus additional logical and physical observed data – all of which will be verified by visual and electronic audits to be accurate.
The DCIM change management process is designed to ensure that openDCIM database accuracy is maintained and, in some cases, be the authoritative source of server hosting information.
Change Process: The requirement is to keep openDCIM current with the actual state of data hall physical and logical in-scope inventory. For a full list of fields captured and maintained by openDCIM that are in-scope for this change management process, see Appendix A.
- If the ITS Core IT Facilities team is making the change, then your work is done. That team will ensure that applicable changes get applied to openDCIM.
- If you propose to make a change to a field that is in-scope for openDCIM, the Core IT Facilities group’s preference is to be notified in advance to coordinate (timing and content) the updating of openDCIM.
- Core IT Facilities can be contacted by email to the ITS-CoreITFacilities distribution.
- Confirmation of the change will be returned to the initiator in the form of a report, screen shot, or at minimum, an email that the change has been made.
- This DCIM CM document will be reviewed annually, at a minimum.
- When in doubt whether a change is in-scope for openDCIM, the safe action is to let Core IT Facilities know.
Requirement: In order to maintain accurate and consistent data in the openDCIM database, the authorization to modify openDCIM data is closely held to a limited number of staff in the Core IT Facilities group. For a full list of fields captured by openDCIM that are in-scope for this change management process, see Appendix A.
If you utilize the Core IT Facilities Rack & Stack team for your data center device support needs, then most of the implemented and applicable changes will be kept current in openDCIM by that team. However, there are some changes that don’t require Rack & Stack team interaction that we’ll need to know about. An example would be a change to the primary or secondary systems administrator for server(s)/device(s).
If, however, you are an individual or group that implements systems changes independently, then following this change process is critical to maintaining openDCIM database to maintain an accurate representation of what is hosted in the data halls.
Reasons and objectives:
- Data Center equipment and infrastructure asset tracking
- Intuitive asset tracking with improved accuracy and reliability
- Shared workload to track, audit and provide guide services to colocation partners
- Serves as a guide to quickly and easily find the server’s location, contact, and other useful information.
- Better planning for infrastructure and server deployments
- Capacity planning – space, power and cooling
- Capacity planning – PDU, KVM, and Network ports
- Professional handling of colocation partner assets
- Real-time visibility to floor plans and cabinet deployments
- Ad hoc reports of what our enterprise data centers are hosting for each colocation partner
- Improved decision making based on near real-time information
In Scope: The following are guiding statements of what is considered in-scope for the openDCIM Change Management Process:
- Data centers ITF, LC and EMRB.
- Current data hall layouts (including Bingo grid labels) will be visible and kept current using openDCIM
- The following cabinets in all “in-scope” data centers are in-scope:
- Production, Colocation, Storage, and Research (including research rows at ITF & Argon at LC)
- • transfer switches, UPS, in cabinet PDU and any other device that takes up “U” space
DCIM fields: The follow list of data fields/categories are considered in-scope for maintaining accurate openDCIM records:
- Hardware changes (replacing a server, for example)
- Label, aka server name (the name of the “box”)
- Physical location changes (within a cabinet or between cabinet and/or data centers)
- Serial number
- Asset tag
- IPv4 or IPv6 addresses
- Primary Admin
- Secondary Admin
- Customer contact
- OS changes (From WIN to UNIX for example, not version upgrades from say Win 2012 to Win 2016)
- Operational log notes (DIMM swaps, HDD replacements, other repairs/upgrades)
- Any notes (i.e. what the server is used for, if it is SAN attached, etc.)
Out of Scope: There are a few, very specific categories that are out of scope at this time:
- Virtual Machines (VM). The Physical host servers are in-scope
- Power & Environmental Monitoring/Reporting
- Networking (Only the floor footprint of the following are captured):
- End of Row Cabinet
- Data Hall networking distribution
- Campus network delivery infrastructure within data halls
- Other network distribution not listed in the in-scope section
- ICN at LC14
- Telecom at LC14