DCIM Offers Benefits In Legacy Data Centers
August 14, 2012
This is Casey Laughman, managing editor of
Building Operating Management magazine. Today's tip is that Data Center Infrastructure Management offers benefits in legacy data centers.
Where there is an existing plant, a middleware DCIM system is ideal. Configured and placed on the Industrial Ethernet or IT network, the object of the system is to listen on the wire for any pre-defined data or receive traps from legacy management/monitoring systems and report or archive accordingly.
The benefits of this type of installation include using existing BMS/BAS/EPMS (emergency power management system) and network management systems and less installation time since the points at the far end are already connected. However, many drawbacks exist. Those drawbacks include: the risk that custom software will be have to be developed to fit existing systems; incomplete data gathering based on the possibility that the building's legacy 'tool' cannot integrate; the potential that staff may tire of the system prior to full implementation and shelve it; concern that the DCIM will be yet another platform to increase operational expenses; and the probability that something on the raised floor will change during DCIM implementation, rendering Day 1 data out of date.
Don't let the drawbacks weigh too heavy, though. Tying existing systems into a central point of collection wisely capitalizes on the existing investment in management systems and enables cross-system data sharing. But be wary when checking into DCIM or middleware. Ask a lot of questions and provide the vendors with a list of the systems for desired integration.
Questions should include the obvious: Can you integrate with everything on my list? What protocols have you successfully integrated with? What systems have you successfully integrated with? Can I use this to tie not only one, but multiple data centers together?
Be prepared for a lot of "vaporware." Middleware and DCIM at this level of integration is an emerging field and vendors will make promises that the next release will contain everything. Don't expect an out-of-box solution from any of them — there are just too many types of systems. Consider creating a bubble diagram that shows the existing systems by manufacturer name and function and reveals any existing relationship between the two, as well as the desired future relationships. This can go a long way toward illustrating the desired equipment.
Next
Read next on FacilitiesNet
