Green IT scenario for Asset Management
This chapter provides a detailed overview about the configuration of Green IT based Asset Management provided by IBM products.
IBM Maximo Asset Management for Energy Optimization helps you monitor the data center environment to identify ways to optimize energy consumption. You can view the layout and a heat map of your data center. Then, you can use the provided service management functions to address related issues, reducing energy costs, and eliminating associated risks.
The chapter guides you through the steps to configure Maximo Asset Management for Energy Optimization and IBM Tivoli Monitoring for Energy Management to obtain asset and sensor information. This information is used to build graphical views of the data center layout and heat map. You use these views to monitor the conditions in your data center and to identify potential problems. Click an asset on the layout view to retrieve a list of related assets (such as servers mounted on a rack), view meter readings, or create a work order for the asset.
This chapter contains the following topics:
5.1 Scenario overview
The scenario has been designed to enable proper maintenance of your building facilities and the components included. This way helps to ensure optimal performance of your assets by optimizing the lifetime, reduction of energy waste, and in general a reduced carbon footprint by using less energy. Figure 5-1 shows you several modern Asset Management practices implemented in enterprises.
Figure 5-1 Asset Management today
We show how to track your assets and how to automate the maintenance for your components.
5.2 Products involved
The products and product components involved in this scenario are as follows:
•IBM Maximo Asset Management for Energy Optimization V 7.1.0.0
•IBM Tivoli Integration Composer V7.2.0.0
•IBM Tivoli Asset Management for IT V 7.2.0.0
•IBM Tivoli Naming Reconciliation Services 1.0.0
•Common PMP 7.1.1.5
In addition, the following products have been installed to support the products:
•IBM WebSphere Application Server 6.1
•Windows Server 2003 5.2 Service Pack 2
A detailed list of software and hardware requirements for IBM Maximo Asset Management for Energy Optimization is published on the IBM website at:
5.3 Benefits
IBM Maximo Asset Management for Energy Optimization performs a regular scheduled maintenance on building facilities and components. This scheduling ensures maintenance is performed as required to optimize the energy usage. The end-to-end service process tracks and schedules maintenance requests, hosted all in one system. This way optimizes your site travel requirements and provides instant access to your status and history data.
The benefits of this scenario are as follows:
•Reduce energy costs and eliminate service outages by identifying and eliminating energy inefficiencies.
•Visualize energy and environmental metrics to identify temperature hot-spots in a simple map overview.
•Remediate energy issues by generating service requests to take action on energy issues
•Link energy metrics with asset information to manage energy as a part of asset management processes, such as condition monitoring and maintenance.
•Ability to create “what if” scenarios. Real-time energy, thermal, and IT dashboards can be used by the IT and operations staff to conduct what-if scenarios on environmental and energy impact and analyze how altering the physical layout and cooling set-points affect the thermal map of the data center. This technique helps organizations determine the most energy-efficient data center layout and facilities equipment settings.
Figure 5-2 shows the Asset Management process improvements over the years.
Figure 5-2 Asset Management improvements
A detailed description is at the following address:
5.4 High-level implementation steps
This chapter guides you through the high-level steps that are required to accomplish the scenario in your environment.
This chapter does not give you a detailed installation instructions but does outline the main steps and highlight the steps that differ from a standard installation without integration. Figure 5-3 shows a simplified integration diagram for this scenario.
Figure 5-3 Simplified integration diagram
Based on the system requirements, we assume that you have the products in place and configured according to the product guidelines. See 5.2, “Products involved” on page 104.
5.5 Implementing Tivoli Monitoring for Energy Management into Maximo Asset Management for Energy Optimization
The Tivoli Monitoring for Energy Management provides the data from a variety of devices or assets hosted in your facility. The IBM Tivoli Integration Composer integration adapter is used to map the monitoring data to the asset information in Maximo Asset Management for Energy Optimization.
This section describes how to configure the integration.
5.5.1 Configuring IBM Tivoli Integration Composer for data connection
Define the data source connections that connects Integration Composer to Tivoli Monitoring for Energy Management and Maximo Asset Management for Energy Optimization.
The Tivoli Integration Composer uses a JDBC driver to connect to data sources. Maximo Asset Management for Energy Optimization provides two data sources:
•The ITM61 data source is used for connection to the source, which is in our scenario the Tivoli Monitoring for Energy Management database.
•The MEO71 data source is used for connection to the target system, which is the Maximo Asset Management for Energy Optimization database.
To define the mapping, you must create the connections for both data sources as shown in Figure 5-4.
Figure 5-4 Tivoli Integration Composer
You must have database administrative rights to access the user interface. Integration Composer stores each database user ID that you enter when defining connectivity to the source and target data sources, but it does not store the passwords. After you define your data source connections, the only parameter that the Integration Composer user interface requests from you in real time is the password for the data source (that is, the database password for database users).
Source data connection procedure
The source data connection procedure is as follows (see and Figure 5-6 on page 108:
1. Sign in to Integration Composer using the Maximo database user ID and password.
|
Tip: The default database name is MAXDB71 and the default user is MAXIMO.
|
2. Under Data Source, select Define New Data Source.
3. In the Define a New Data Source window, select Tivoli Monitoring 6.1, and then click Next. Type ITM61 as the data source name, click Next, and then confirm that you want to overwrite the data source.
4. In Connection Method, select IBM Tivoli Monitoring. Specify the parameters for connecting to Tivoli Monitoring for Energy Management. Click Test Connection to verify the connection.
5. Click Finish.
Figure 5-5 shows how to define a new data source.
Figure 5-5 Tivoli Integration Composer: Define a new data source
Figure 5-6 shows how to select the data source.
Figure 5-6 Tivoli Integration Composer: Define source data
Target data connection procedure
The source data connection procedure is as follows (see Figure 5-7 on page 109):
1. In the Integration Composer window, select Define New Data Source.
2. In the Define a New Data Source window, select Deployed Asset 7.2, and then click Next. Type MEO71 as the data source name, click Next, and then, confirm that you want to overwrite the data source.
3. In Connection Method, select the option for the database in which Maximo Asset Management for Energy Optimization is running. Specify the parameters for connecting to the Maximo Asset Management for Energy Optimization database. Click Test Connection to verify the connection.
4. Click Finish.
Figure 5-7 shows the options to select the target.
Figure 5-7 Tivoli Integration Composer: Define target data
5.5.2 Configuring the mapping in Tivoli Monitoring for Energy
The integration adapter requires a mapping to load data from Tivoli Monitoring for Energy Management to Maximo Asset Management for Energy Optimization.
Connection between source and target database
The mapping connects the source and the target database. The mapping information about the mapping expressions is stored in a mapping file and must be imported.
The mapping procedure is as follows:
1. Sign in to Integration Composer using a valid user ID and password.
2. Select Create New Mapping.
3. In the Source list, select the data source that you defined for Tivoli Monitoring for Energy Management, for example, ITM61.
4. In the Target list, select the data source that you defined for Maximo Asset Management for Energy Optimization.
5. Type a name for the new mapping, and then click OK. If necessary, enter the password for the connection to the source and target database, if requested.
6. In the Mapping window, select the Import action.
7. Select the ITM61toDPA72.fsn file, and then click Open.
8. After the file is imported, click Save, and then click Close.
Figure 5-8 Tivoli Integration Composer: Mapping process
5.5.3 Configuring Tivoli Maximo Asset Management for Energy Optimization
With the given setup you can run the integration adapter mapping to load asset data from Tivoli Monitoring for Energy Management into Maximo Asset Management for Energy Optimization.
Mapping configuration
To execute the data mapping, run the integration adapter mapping to load data from Tivoli Monitoring for Energy Management into the Deployed Assets tables in Maximo Asset Management for Energy Optimization. You can use several options to set up the mapping execution to fit to your daily needs.
One-time mapping execution
You must create a mapping in Tivoli Integration Composer between Tivoli Monitoring for Energy Management and Maximo Asset Management for Energy Optimization.
Run the mapping command once to load the asset data to the Maximo Asset Management for Energy Optimization Deployed Assets tables.
Use any scheduling method to run this command periodically to keep your database updated. Perform the following steps:
1. On the computer where Tivoli Integration Composer is installed, open a command prompt and go to the bin subdirectory of the Tivoli Integration Composer installation directory.
2. Enter the following command, depending on the OS:
– For Windows:
commandLine.bat <mapping name> <Integration Composer database userid> <Integration Composer database password> <Tivoli Monitoring userid> <Tivoli Monitoring password> <Maximo for Energy Optimization database userid> <Maximo for Energy Optimization database password>
The execution is shown Example 5-1.
Example 5-1 Tivoli Integration Composer: Windows command line execution
C:Integration ComposercomandLine.bat ITMfEM-MEO7.1 maximo db2admin test test maximo db2admin
– For UNIX:
commandLine.sh <mapping name> <Integration Composer database userid> <Integration Composer database password> <Tivoli Monitoring userid> <Tivoli Monitoring password> <Maximo for Energy Optimization database userid> <Maximo for Energy Optimization database password>
3. Follow the standard reconciliation and promotion process shown in Figure 5-9 to promote the deployed assets that were loaded to authorized assets.
Figure 5-9 Maximo: Reconciliation and promotion process
Further information is in the Maximo online help.
Scheduled data load
Configure and run the cron task to load meter information from Tivoli Monitoring for Energy Management into Maximo Asset Management for Energy Optimization.
The PLUSEITMMETERS cron task obtains meter data from Tivoli Monitoring for Energy Management and sets the corresponding meters for the Maximo Asset Management for Energy Optimization assets.
Configure the integration endpoint and external system for communication with Tivoli Monitoring for Energy Management:
1. In the End Points application, select the PLUSEITMEP endpoint.
2. On the End Point tab, specify the values for the URL, user name, and password for your Tivoli Monitoring for Energy Management system.
3. In the External Systems application, select the PLUSEITMES system.
4. On the System tab, specify the values for the URL, user name, and password for your Tivoli Monitoring for Energy Management system.
5. In the Cron Task Setup application, select the PLUSEITMMETERS cron task. An instance of the cron task is provided, as shown in Figure 5-10 on page 112.
6. Click Set Schedule and select the interval for running the cron task to load the meters, and then click Save Cron Task Definition.
Figure 5-10 Maximo: Cron Task configuration
5.5.4 Loading meter information from Tivoli Monitoring for Energy Management into Maximo Asset Management for Energy Optimization
Maximo Asset Management for Energy Optimization obtains meter data from Tivoli Monitoring for Energy Management metrics.
Tivoli Monitoring for Energy Management does not have the “concept” of a meter name that relates to the individual metrics that are captured for a device. Meter information is obtained from the following types of Tivoli Monitoring for Energy Management objects:
•KE9_RACK_SERVER_POWER_DATA
•KE9_BLADECENTER_POWER_DATA
•KE9_PDU_POWER_DATA
•KE9_ALL_SENSOR_DATA
Metrics information from Tivoli Monitoring for Energy Management is mapped to the corresponding Maximo Asset Management for Energy Optimization meter name. For example, suppose the following information is pulled from Tivoli Monitoring for Energy Management for a KE9 Rack Server:
<Ambient_Temp_Avg dt="number">21.0</Ambient_Temp_Avg>
<Ambient_Temp_Max dt="number">21.0</Ambient_Temp_Max>
<Ambient_Temp_Min dt="number">21.0</Ambient_Temp_Min>
The metric to be recorded is Ambient_Temp_Avg. Therefore, the meter name that is created in Maximo Asset Management for Energy Optimization for that server is AMB_AVG_C.
The following types of meters are defined for Tivoli Monitoring for Energy Management:
AMB_AVG_C Ambient Average Temperature (Celsius)
AMB_AVG_F Ambient Average Temperature (Fahrenheit)
EXH_AVG_C Exhaust Average Temperature (Celsius)
EXH_AVG_F Exhaust Average Temperature (Fahrenheit)
AVG_PWR_AC Average Power AC
AVG_PWR_DC Average Power DC
HUMIDITY_R Relative Humidity
5.5.5 Loading temperature metrics data from Tivoli Monitoring for Energy Management into Maximo Asset Management for Energy Optimization
You must load the metrics data into Maximo Asset Management for Energy Optimization. Configure and run the cron task to load temperature metrics data from Tivoli Monitoring for Energy Management into Maximo Asset Management for Energy Optimization.
Make sure that your assets exists and linked to the meters to which the metrics refer.
The PLUSEITMMETRICS cron task obtains metrics data from Tivoli Monitoring for Energy Management. Metrics information is obtained from the following types of Tivoli Monitoring for Energy Management objects:
•KE9_RACK_SERVER_POWER_DATA
•KE9_BLADECENTER_POWER_DATA
•KE9_PDU_POWER_DATA
•KE9_ALL_SENSOR_DATA
Configuring metrics data integration
Verify the configuration of the integration endpoint and external system for communication with Tivoli Monitoring for Energy Management:
1. In the End Points application, select the PLUSEITMEP endpoint.
2. On the End Point tab, ensure that the values for the URL, user name, and password correspond to your Tivoli Monitoring for Energy Management system.
3. In the External Systems application, select the PLUSEITMES system.
4. On the System tab, ensure that the values for the URL, user name, and password correspond to your Tivoli Monitoring for Energy Management system.
5. In the Cron Task Setup application, select the PLUSEITMMETRICS cron task, as shown in Figure 5-11
6. Click Set Schedule and select the interval for running the cron task to load the metrics, and then, click Save Cron Task Definition.
Figure 5-11 Maximo: Cron task configuration for metric data
5.5.6 Configuring data centers
Before you can use Maximo Asset Management for Energy Optimization, you must configure a data center location and its assets.
Configuring data center locations
To display the data center views, configure the data center location by setting its dimensions in the Locations application.
When you configure the dimension attributes for a location, Maximo Asset Management for Energy Optimization identifies that location as a data center. Perform the following steps:
1. In the Locations application, create a location or select the location that you want to set as a data center location.
2. Select the Modify Data Center Properties action.
3. In the Modify Data Center Properties window, select the unit of measure for the data center dimensions in the Layout Unit of Measure field. Ensure that the unit of measure that you selected has a conversion to the FEET unit (ft) of measure configured.
4. In the Meters application, select Select Action → Unit of Measure and Conversion → Add/Modify Conversions.
If a conversion to FEET is not configured, create one by clicking New Row.
5. Specify the data center dimensions in the Length, Width, and Height fields. Regardless of the unit of measure that you select, the resolution for the length and width on the data center views is 1 foot (30.48 cm). The resolution for height is 0.5 foot (15.24 cm).
6. Select the unit of measure for the temperature sensors in the Sensor Unit of Measure field. This unit of measure is used only for manual temperature sensors
7. Click Save Location.
|
Optional: The Absolute Color Scale check box enables you to set the upper and lower temperature boundaries of the heat map. By default, the colors are relative to the maximum and minimum temperature readings in the data center. If this check box is selected, the mxe.meo.maxtemp and mxe.meo.mintemp system properties specify the maximum and minimum temperatures.
|
Configuring data center assets
Before you can display assets in the data center view, you must assign the assets to a data center location. You must also set the attributes that describe the dimensions and the position of the asset in the data center.
|
Note: The location of the asset that you want to configure must be a data center location.
|
The configuration of a data center involves two main steps:
Surveying the data center
Surveying the data center involves the following tasks:
1. A template worksheet is provided to help with the physical collection of data center asset information that needs to be entered into Asset Management for Energy Optimization (MEO). You can find this worksheet in the following location:
meo_install_dir oolsmaximoenxcenterData center Layout Worksheet.xls.
2. Pulling device information from IBM Tivoli Monitoring for Energy Management using the provided Tivoli Integration Composer adapter.
3. Promotion and reconciliation of the devices from Tivoli Monitoring for Energy Management to Maximo Assets.
Besides IT assets, you can use the provided asset types to configure other elements in your data center. You can configure walls, furniture, and perforated floor tiles, and assets that are not monitored by software, such as racks and air conditioners. The unit of measure for the coordinates and dimensions is the same that is defined for the data center location.
|
Note: If you try to change the coordinates or dimensions of an asset while the meter readings for that asset are being updated, an “update by another user” message is indicated. To minimize this problem, stop the PLUSEMETRICS cron task instances during data center setup.
|
To proceed with this step, select the asset that you want to configure in the Assets application, or create an asset:
1. In the Data Center Details section of the Asset tab, select a data center type for the asset. Data center types define the colors and shapes of the assets in the layout view.
2. Specify the coordinates of the position of the asset in the X, Y, and Z fields. The origin for the coordinates is the lower left corner of the layout view.
3. Specify the dimensions of the asset in the Width, Length, and Height fields.
4. Select the direction of the front of the asset in the view.
5. For rack-mounted assets, enter the slot position of the asset. Optionally, select the group to which the asset belongs.
6. Click Save Asset.
Configuring asset hierarchies
Configure assets in the data center that are related, such as a rack and the servers installed in that rack, in a single operation.
Maximo Asset Management for Energy Optimization identifies asset hierarchies by the X and Y coordinates of the assets. The data center layout view does not recognize any parent-child relationships that are configured for the assets. Therefore, you can configure assets that are physically located one above the other but that do not share a parent asset. For example, you can configure servers that are installed on shelves.
When you configure racks and the servers that are mounted on those racks, enter the same X and Y coordinates for the rack and all the servers.
You can set the coordinates and dimensions of multiple data center assets by using the Modify Data Center Assets action:
1. In the Locations application, select the data center location for which you want to set the asset attributes, and then select the Modify Data Center Assets action.
2. In the Modify Data Center Assets window, perform the following steps:
a. Select the assets that you want to modify.
b. In the fields at the bottom of the window, specify the values for the coordinates and any other attributes that you want to set.
c. Click Apply New Values. Attributes that are blank are not changed.
d. Repeat the steps for other groups of assets for which you want to set common attributes.
3. Click Save.
5.5.7 Using data center graphical views
You can monitor your data center and resolve energy issues from the Data Center tab in the Assets and Locations applications. When you select a data center location in the Locations application, or when you select an asset that is assigned to a data center location in the Assets application, the Data Center tab is added to the application window. It has the following information:
•The top part of the Data Center tab shows the data center location name, description, and site. You can change the description by clicking the icon next to it.
•The middle part shows the data center views. The layout view is shown by default. To display the heat view, select Heat on the drop-down list above the views.
When both views, Layout and Heat, are selected, they are shown superimposed. The actions that are available when you click anywhere inside the view depend on which view is in the foreground. You can switch the views by clicking the view.
|
Note: To remove any of the views, select it in the list, and then click it.
|
The graphical views always show the measures in feet. If you select a different unit of measure for your data center, this unit of measure is converted to feet for display.
Layout view
The Layout view shows the data center layout with all the assets that are assigned to the data center location and that have their coordinate and dimension attributes set.
All X and Y coordinate values that are entered for assets and locations are converted to feet and displayed on a grid of tiles that are fixed at two feet by two feet. All asset size values (width, length, and height) are also converted to feet.
The colors and shapes of the assets depend on their data center types. If you select Legend in the left list on the bottom area, a list of all data center types opens. By selecting or clearing the check boxes in the visible column, you can choose which types of assets are shown in the layout view.
If you select an asset type in the center list and then select Elements in the left list on the bottom area, a list opens of all assets of that type that are configured in this data center.
If you click an asset in the layout view, a list of all assets with the same type of the selected asset opens, with the asset that you selected highlighted.
If the point where you click has a rack and its servers configured, the rack is highlighted. To view all assets in the selected point, select Retrieve Assets for Selected Map Location in the right-most list at the bottom part of the tab, then click Go. A window opens showing all assets at the point selected. Click the arrow next to an asset in the list to switch to the Assets application with that asset selected.
With an asset selected on the layout view, you can also choose the following actions on the right-most list:
•Show Meter Readings, to view the meter reading for the asset
•Create work order for selected asset, to create a work order pre-filled with the asset name and location, and with the following description: Generated for Meter Readings (Click Long Description).
•Go to → Deployed Assets, to switch to the appropriate Deployed Assets application (Computer or Network Device, depending on the type of asset), with that asset selected.
Heat view
This view shows a heat map of the data center which is an interpolation of the most recent temperature sensor readings.
The heat map update period, in minutes, is specified by the mex.meo.heatrefresh system property. You can also update the map manually by clicking. The sensor readings are obtained fromTivoli Monitoring for Energy Management by a cron task. The heat map changes only if the cron task was executed since the last time the map was updated. Set the mex.meo.heatrefresh property to a value synchronized to that of the frequency of the metrics load cron task.
The colors in the map can be relative to a fixed range of temperatures, or to the last minimum and maximum temperature readings. This behavior is determined by the setting of the Absolute Color Scale check box in the data center location properties.
You can view the heat map for various heights by selecting the height in the list above the map.
When the heat view is in focus, the bottom part of the Data Center tab shows a vertical heat slice view. This view consists of the following elements:
•A vertical section of the heat map of the data center, taken along the X (width) axis
Select the Y (length) coordinate for the cut by dragging the horizontal cross-hair line on the top heat map view.
•A vertical line showing the temperature readings at the selected X coordinate
Select the coordinate by dragging the vertical cross-hair line on the top heat map view.
•A solid line showing the temperature graphic for the height selected
•A dotted line showing the height selected
|
Note: To prevent displaying temperature readings that have not been updated for a long time, set the mxe.com.heattime system property. This property defines the maximum time, in minutes, that meter readings are used for building the heat map. Any readings taken more than mxe.com.heattime minutes ago are not considered for building the heat map.
|
Configuring manual temperature sensors
To improve the accuracy of the heat map view, you can configure external sensors and enter their readings to be displayed in the heat view.
Consider providing manual sensor readings in locations where there are not enough sensor readings (such as data center perimeters). Providing manual sensors improves the overall appearance of the heat map.
Perform the following steps:
1. In the Locations application, select the location for which you want to include sensor information, and then select the Modify Data Center Properties action.
2. Select the sensor for which you want to add or change information, or add a new sensor, and then enter the coordinates of the location of the sensor. The origin of the coordinates is the lower left corner of the data center view.
3. Enter the temperature reading for the sensor. The unit of measure for all sensors is that set for the data center location.
4. Click OK.
For more product-related help information, go to the following web address:
5.6 Architectural diagram of integration
Figure 5-12 shows the products used and gives the architectural overview of the components.
Figure 5-12 Data Center product overview
Figure 5-13 explains the components that are used in the specified products to configure the described scenario.
Figure 5-13 Component overview: Maximo for Energy Optimization
5.7 Scenario walk-through
Increasingly efficient, high-density computers provide an opportunity to get more value from every square foot of space in your data center.
The scenario walk-through has several examples of how you can achieve your goal with a focus on energy efficiency in an overall Green IT context. Figure 5-14 shows the visualization of the temperature as a main instrument for visualization.
Figure 5-14 Maximo heat map: data center overview
For the walk-through, we assume that products (listed in 5.2, “Products involved” on page 104) are in place and are configured (as described in 5.4, “High-level implementation steps” on page 106).
5.7.1 New assets from strategy to ready
Daily, you receive new requests for new service, new servers, and new assets to be placed in your data center. The Maximo heat map can help you in several ways:
•Where to place your assets
The heat map visualizes the heat in your data center. With this information, you can balance the temperature by selecting the right place for your new assets.
•Where to move your assets
Because you have several servers and further assets in your heat map, you can identify warmer and colder areas of your data center. The heat map visualizes this information, helping you to move your assets accordingly.
These two typical scenarios are used to explain the required implementation steps from an end-to-end perspective.
Because you have the products installed and configured, you get all your requests (install, move, change, delete) for new assets through the Maximo service order. According to your service, several service work orders are created to cover your job plans for installing new assets and updating asset information in your data center. To find the correct place for the new servers, the job plan includes a task to select the appropriate location from the heat map of Maximo Asset Management for Energy Optimization. This technique ensures that the server is placed into the correct area, from an energy perspective. See Figure 5-15.
Figure 5-15 Maximo Asset Management for Energy Optimization: heat map
The same heat map can be used to relocate your assets within the data center. The process starts, based on your heat monitoring, and the heat map can help you to identify heat bottlenecks. Figure 5-16 shows a bottleneck identified. Warm area (red color) is the bottleneck.
Figure 5-16 Asset relocation
The process for moving the asset is applied through a service order to create the required service work orders, and runs similar to the described process for placing.
To apply the scenario to a virtualized environment, the Maximo Asset Management for Energy Optimization heat visualization can help to place your virtual instances according to the needed power and cooling data. The heat map supports you to start the placing process and to give you the daily data to balance your heat production in comparison with the cooling capacity.
5.7.2 Event Management based on Energy Management
Fast reaction and event management is crucial to your environment’s health index to deliver your service, fulfilling the needed service level. Energy and especially heat data measured with sensors in your data center can help you to have short reaction time between asset related interruptions and starting your solution process.
Combine heat and asset information
If you discover an unexpected increase of temperature in the heat map, you may select the appropriate area, and the assets location are shown. Condition monitoring of assets notifies you when conditions go outside the defined metric levels. Figure 5-17 shows the drill-down options from heat to asset.
Figure 5-17 Maximo heat map drill down
Because the information has been processed in your event and incident processes, the process chain starts, for example to schedule a technician visit or a maintenace plan.
Use of historical data
Because the thermal data is linked to the asset data, reports can be created to present several areas. Figure 5-18 on page 123 shows a BIRT report about asset power consumption.
Figure 5-18 BIRT report: power demand by asset
5.8 Summary
Figure 5-19 shows the quick summary of the solution.
Figure 5-19 Quick summary
In this chapter, we described how you can configure Maximo Asset Management for Energy Optimization and IBM Tivoli Monitoring for Energy Management to obtain asset and sensor information from your data center. This information is used to build graphical views of the data center layout and heat map. You can use these views to monitor the conditions in your data center and to identify potential problems.
In the scenario walk-through section, we showed you two common use cases of this graphical view:
•Where to place your assets: Choosing the right place for your new assets to balance your temperature.
•Where to move your assets: Relocating your assets inside the data center taking into consideration warmer and colder areas of your data center.
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.