For a proper usage and collaboration between BMS, DCIM, CMDB, etc. the usage of an architectural framework is recommended.
A datacenter is basically a value stack. A supply chain of stack elements where each element is a service component (People, Process and Technology that adds up to an service). For each element in the stack the IT organization has to assure the quality as agreed on. In essence these quality attributes were performance/capacity, availability/continuity, confidentiality/integrity, and compliance. And nowadays also sustainability. One of the greatest challenges for the IT organization was and is to coherently manage these quality attributes for the complete service stack or supply chain.
Currently a mixture of management systems is used to manage the datacenter service stack: BMS, DCIM, CMDB, and System & Network Management Systems.
GETTING RID OF THE SILOES
As explained in “Datacenters: blending BIM, DCIM, CMDB, etc.” we are still talking about working in silos where each of the participants that is involved in the life cycle of the Datacenter is using its own information sets and systems. To achieve real general improvements (instead of local optimizing successes) a better collaboration and information exchange between the different participants is needed.
To steer and control the datacenter usage successfully a monitoring system should be in place to get this done. Accepting the fact that the participants are using different systems we have to find a way to improve the collaboration and information exchange between the systems. There for we need some kind of reference, an architectural framework.
For designing an efficient monitoring framework, it is important to assemble a coherent system of functional building blocks or service components. Loose coupling and strong cohesion, encapsulation and the use of Facade and Model–View–Controller (MVC) patterns is strongly wanted because of the many proprietary solutions that are involved.
Based on an earlier blog about energy monitoring a short description of the most common building blocks will be given:
- Most vendors have their own proprietary API’s to interface with the metering devices. Because metering differ within and between data centers these differences should be encapsulated in standard ‘Facility usage services‘. Services for the primary, secondary and tertiary power supply and usage, the cooling, the air handling.
- For the IT infrastructure (servers, storage and network components) usage we got the same kind of issues. So the same receipt, encapsulation of proprietary API’s in standard ‘IT usage services‘, must be used.
- Environmental conditions outside the data center, the weather, has its influences on the the data center so proper information about this must be available by a dedicated Outdoor service component.
- For a specific data center a DC Usage Service Bus must be available to have a common interface for exchanging usage information with reporting systems.
- The DC Data Store is a repository (Operational Data Store or Dataware House) for datacenter usage data across data centers.
- The Configuration management database(s) (CMDB) is a repository with the system configuration information of the Facility Infrastructure and the IT infrastructure of the data centers.
- The Manufactures specification databases stores specifications/claims of components as provided by the manufactures.
- The IT capacity database stores the available capacity (processing power and storage) size that is available for a certain time frame.
- The IT workload database stores the workload (processing power and storage) size that must be processed in a certain time frame.
- The DC Policy Base is a repository with all the policies, rules, targets and thresholds about the datacenter usage.
- The Enterprise DC Usage Service Bus must be available to have a common interface for exchanging policies, workload capacity, CMDB, manufacturer’s and usage information of the involved data centers, with reporting systems.
- The Composite services deliver different views and reports of the energy usage by assembling information from the different basic services by means of the Enterprise Bus.
- The DC Usage Portal is the presentation layer for the different stakeholders that want to know something about the usage of the Datacenter.
Usage of an architectural framework (reference architecture) is a must to get a monitoring environment working. The modular approach focussed on standard interfaces gives the opportunity of “rip and replace” of components. It also gives the possibility to extend the framework with other service components. The service bus provides a standard exchange of data (based on messages) between the applications and prevents the making of dedicated, proprietary point to point communication channels. Also to get this framework working a standard data model is mandatory.