Improved mapping support for the KE9_ALL_SENSOR_DATA object

Maximo Asset Management for Energy Optimization 7.1.0 fix pack 1 provides improved mapping support for the KE9_ALL_SENSOR_DATA object. Initial implementations have uncovered that this object supports various sensors, and each sensor requires variations in their mapping. Therefore, the fix pack provides an updated metermapping.xml file to support the known variations in the default mappings. The fix pack also provides some additional mapping flexibility to support other variations that might be found.

The default mapping for this object is as follows:

<OBJECT>
<NAME>KE9_ALL_SENSOR_DATA</NAME>
<ASSETCLASS>NETDEVICE</ASSETCLASS>
<DOMAINNAME>Sensor_Name</DOMAINNAME>
<NODENAME>Node</NODENAME>
<MAP>
<SOURCEMETER>Sensor_Value</SOURCEMETER>
<SOURCEFILTER type="include" filter="Temperature">Sensor_Type</SOURCEFILTER>
<SOURCEFILTER type="exclude" filter="-0.1">Sensor_Value</SOURCEFILTER>
<SOURCEFILTER type="exclude" filter="0.0">Sensor_Value</SOURCEFILTER>
<SOURCEFILTER type="exclude" filter="CRAC.*">Sensor_Name</SOURCEFILTER>
<SOURCEFILTER type="exclude" filter="CDU.*">Sensor_Name</SOURCEFILTER>
<TARGETMETER1>AMB_AVG_C</TARGETMETER1>
</MAP>
<MAP>
<SOURCEMETER>Sensor_Value</SOURCEMETER>
<SOURCEFILTER type="include" filter="Power_Consumption">Sensor_Type</SOURCEFILTER>
<SOURCEFILTER type="exclude" filter="-0.1">Sensor_Value</SOURCEFILTER>
<SOURCEFILTER type="exclude" filter="0.0">Sensor_Value</SOURCEFILTER>
<TARGETMETER1>AVG_PWR_AC</TARGETMETER1>
</MAP>
<MAP>
<SOURCEMETER>Sensor_Value</SOURCEMETER>
<SOURCEFILTER type="include" filter="Humidity">Sensor_Type</SOURCEFILTER>
<SOURCEFILTER type="exclude" filter="-0.1">Sensor_Value</SOURCEFILTER>
<SOURCEFILTER type="exclude" filter="0.0">Sensor_Value</SOURCEFILTER>
<TARGETMETER1>HUMIDITY-R</TARGETMETER1>
</MAP>
</OBJECT>

The primary change in this mapping is that temperature data related to CRACs and CDUs,which are specific to water temperatures, is now excluded. Therefore, CRACs and CDUs are not used as part of the heat map. As with other objects, the default mapping excludes values of 0.0 and -0.1, which were previously hardcoded in the processing programs of the cron tasks.

Additionally, the fix pack introduces more flexibility in the definition of the key value of the incoming message as varying XMLs from ITMfEM can have different key values. Currently ,the NODENAME and DOMAINNAME are used to hold the key values of data from ITMfEM. However, depending on which sensors are being pulled, it might be required to map different values as the 'key' of the corresponding record that is created in Maximo Asset Management even within the same ITMfEM object. Currently, all objects can support only a single pair of values that are used to populate the nodename and domainname. The following examples show how the key mapping varies depending on whether the sensor_name begins with the value 'Probe':

When value does begin with Probe':
<KEY>
<KEYFILTER type="include" filter="Probe.*">Sensor_Name</KEYFILTER>
<DOMAINNAME/>
<NODENAME>Sensor_OID</NODENAME>>
</KEY>

When value does not begin with Probe':
<KEY>
<KEYFILTER type="exclude" filter="Probe.*">Sensor_Name</KEYFILTER>
<DOMAINNAME>Sensor_Name</DOMAINNAME>
<NODENAME>Node</NODENAME>
</KEY>

You can specify the following three tags at both <OBJECT> and <KEY> levels. When provided at both levels, the value at the <KEY> level works as an override to the value specified at the <OBJECT> level. The fields are mapped only if they meet the KEYFILTER criteria.


<ASSETCLASS> </ASSETCLASS>
<DOMAINNAME> </DOMAINNAME>
<NODENAME> </NODENAME>

The use of the <KEY> section is not restricted to the KE9_ALL_SENSOR_DATA object. You can use the <KEY> section on any object that is in the updated metermapping.xml file.