How To Reduce DCIM Deployment Cost And Complexity

How To Reduce DCIM Deployment Cost And Complexity

The key is device level functionality.

By Darin Wymer
Article Link: http://bit.ly/1mCIhIx

The ROI associated with core DCIM capabilities like real-time monitoring, intelligent alerting, and asset management is very legitimate. As a result, data center operators are deploying DCIM solutions across their facilities to both reduce downtime and drive significant CapEx/ OpEx cost savings. Yet according to the Uptime Institute’s 2013 Data Center Industry Survey, 60% of advanced owners and operators cite cost as the primary barrier to DCIM adoption. This disconnect is a common one with enterprise software deployments. And while there are no silver bullets when it comes to rolling out DCIM, deploying devices with greater functionality including multi protocol support, data logging, and an onboard web interface can greatly reduce the TCO of the overall solution.

Multi-Protocol Support

One of the immediate value propositions several DCIM vendors speak to is the ability to pull several disparate applications into a “single pane of glass”. Logic dictates that application consolidation is a big part of the long term ROI for facilities managers. But this may not be possible if the facility is loaded with devices supporting just single, legacy or proprietary protocols. And while middleware vendors providing jaces that sit between the device and the DCIM front end will tout the benefits of protocol conversion, it is far more efficient for devices to speak directly to the DCIM system. Direct communication can minimize total device counts in the facility, reduce single points of failure, and help eliminate multiple license fees for monitoring the same points.

Onboard Data Logging/Backup

Protocol conversion isn’t the only reason jaces are deployed in the critical facility. Managing all the data generated by rapid polling becomes a big issue as device counts increase, and middleware is commonly used to aggregate data between the device and the DCIM solution. This isn’t necessary for devices with onboard data logging and backup, as they can handle the workload associated with measuring continuous data over frequent intervals without the need of additional hardware and software. The net result is the ability to scale your device infrastructure much more efficiently and effectively.

Web Interface

As the device count scales, managing adds, moves, and changes to the infrastructure becomes increasingly challenging as well. One way to mitigate the complexity is to deploy devices with an onboard web interface. This allows the device data to be read remotely from the network as opposed to requiring a direct connection.Validating DCIM data becomes much simpler, and any adds, moves, and changes in the device configuration can be managed through the DCiM interface which helps maintain the “single pane of glass” paradigm. Like any enterprise software application, implementing a DCIM solution isn’t a discrete event for facility and IT professionals. Instead, it is a continuous process of deployment and maintenance, constantly evolving over time. The key to maximizing ROI is to streamline those programs as much as possible. As such, utilizing devices with a high level of functionality can do a lot to reduce the time, cost, and complexity over the lifecycle of the project.

Add Comment

Leave a Reply

%d bloggers like this: