Data filtering in the metric mapping load based on configuration

Maximo Asset Management for Energy Optimization 7.1.0 fix pack 1 provides improved support for data filtering in the metric mapping load by using configuration. Currently, the mapping of meter and metric data through the two cron tasks of Maximo Asset Management for Energy Optimization does not provide a way to "skip" rows of data from ITMfEM based on configuration. In the current cron processing, there is hardcoded logic to bypass data mapping of rows when the values of the meter reading from ITMfEM is 0.0 or -0.1. With this fix, there will no longer be hardcoded mappings to skip data, because the updated metermapping.xml file will have these conditions implemented.

With the updated metermapping.xml file, you can implement a mapping that will 'skip' rows based on the configuration within the file. The mapping file supports the ability to 'exclude' (skip) or 'include' data within the mapping file. For example, if you exclude (skip) the mapping of a row of data when there is a value of 0.0 or -0.1 in the Ambient_temp_Value attribute, the mapping file is as follows:

<MAP>
<SOURCEMETER>Ambient_Temp_Avg</SOURCEMETER>
<SOURCEFILTER type="exclude" filter="-0.1">Ambient_Temp_Avg</SOURCEFILTER>
<SOURCEFILTER type="exclude" filter="0.0">Ambient_Temp_Avg</SOURCEFILTER>
<TARGETMETER1>TEMP_C</TARGETMETER1>
</MAP>

The <SOURCEFILTER> tag identifies the filter type by using the tag attribute type. The valid values are either include or exclude. The tag attribute 'filter' identifies the value to use for the filter, and the tag value identifies the tag from the input (ITMfEM) xml to which the filtering is applied.

You can specify the filter values for both include and exclude as Java Regular Expressions. In the following example filtering, the value of Sensor Type begins with ‘Temp’.

<SOURCEFILTER type='include' filter="Temp.*">Sensor_Type</SOURCEMETER>

For details about Java Regular Expression, see http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html.

When multiple 'exclude' filters are provided, only one of the filter criteria needs to be met for the mapping to be skipped. When multiple 'include' filters are provided, all the include filter criteria need to be met for the mapping to be included (not skipped).