Contents


Integrate IBM Predictive Maintenance and Quality (PMQ) with ILS deviceWISE to onboard high-value asset data

Identify problem hot spots and their solutions

Comments

Overview

Asset-intensive industries, such as oil and gas, mining, and energy and utilities, use complex equipment, such as compressors, haul trucks, and turbines, in their day-to-day operation. Any unplanned downtime or major unforeseen failure of this equipment has a direct impact on production downtime, which affects the financial performance of the organization.

Potential component and equipment failure, plus machine health of in-service equipment needs to be monitored by identifying early signs of possible downtime. The goal is to maximize the uptime of the component/equipment.

The IBM Predictive Maintenance and Quality (PMQ) solution helps you monitor, analyze, and report on information that is gathered from high-value assets and recommend maintenance activities for them. With this integrated solution, you can:

  • Predict the failure of a monitored asset in order to fix it and avoid costly downtime.
  • Search stored maintenance logs to determine the best repair procedures and cycles.
  • Identify the root causes of asset failure to take corrective actions.

The integration bus layer within PMQ helps to transform external events (received from monitored high-value assets) into the format that is required by the PMQ analytics solution's data model. One way to receive external low-level events, such as the discharge pressure of a compressor or the inlet temperature of compressor, is to use the ILS deviceWISE Machine to Machine (M2M) Application Platform. (For more information about ILS deviceWISE, see Related topics.) This platform helps:

  • Connect assets to applications.
  • Collect and process data from a variant of assets, in various locations.
  • Integrate that data into existing enterprise IT systems or to a custom dashboard to drive better business decisions.
  • Remotely access and manage assets.

This article explains how to onboard data from an OLE for Process Control (OPC) source, which stands for Object Linking and Embedding (OLE) for Process Control, and the step-by-step configuration to onboard data into PMQ to perform analytics on the asset data.

Use case

A typical oil and gas industry involves various rotating equipment, such as turbines, pumps, compressors, generators, and motors. Each gas turbine has an upstream rotating compressor, which generates pipeline data, such as compressor unit suction and discharge pressures, gas temperatures, unit flow, ambient temperature, and more. The data that is received from low-level source systems acts as a data store to perform analytics, like the health monitoring of turbines. The data is captured in the form of events from field-level systems in a real-time mode that uses a protocol and format that is called OLE for Process Control (OPC). OPC event sources are integrated by using an external adapter, ILS deviceWISE, which pushes the data into the Integration Bus layer within PMQ by using the WebSphere® MQ (IBM MQ) transport. After device events are received in a queue, the event-processing component transforms them into the PMQ event format that is required by the solution.

Tags are often used in the process industry and are normally assigned to a piece of information. A tag consists of a name by describing a single point of information, so a process system can consist of hundreds and even thousands of tags.

For demonstration of integration capabilities, this article uses MatrikonOPC Simulator, which provides equipment data connectivity by using these tags, which are an item database for a device. Simulated tags are OPC-timestamped with range and OPC quality. Based on the quality set, a tag can either be "good" or "bad."

In this scenario, each compressor carries about nine tags that indicate different measurements, as shown in Table 1.

Table 1. Compressor tags, with their units of measurement
NameDefinitionEnglish unitMetric unit
CTIMCompressor inlet temperatureFahrenheit (°F)Celsius (°C)
CTDCompressor discharge temperatureFahrenheit (°F)Celsius (°C)
CPRCompressor pressure ratioNoneNone
AFPCSCompressor inlet pressure transducers 96CSin H2Omm H2O
CPDCompressor discharge press max selectpsibar
AFQCompressor inlet air mass flowlb/skg/s
CompEff_MeanMean compressor efficiency%%
AFPAPBarometric pressure transducers 96APinmm
CMHUMSpecific humidityRatioRatio

Solution architecture

Figure 1 shows the integration of ILS deviceWISE with IBM Predictive Maintenance and Quality solution, a packaged, preconfigured cross-industry business analytics solution.

Figure 1. Architecture of the solution when you integrate ILS deviceWISE with PMQ
Diagram of architecture for integrating ILS deviceWISE with PMQ
Diagram of architecture for integrating ILS deviceWISE with PMQ

Technical summary of the solution workflow

  1. Integration with historians: Equipment tags and online analyzers are configured in DCS, SCADA, and historian systems. ILS deviceWISE is configured to read the values of all the online and offline tags in a real-time mode. Thus, ILS deviceWISE integrates with level 2 systems and historians to fetch sensor, alarm, monitoring, and diagnostic data that is injected from equipments. This integration results in continuous raw event data capture and a near real-time analysis of the captured data.
  2. Real-time data integration: Triggers are created in ILS deviceWISE workbench to put the tag data in the integration bus layer within PMQ by using a message queue. This data is received on the queue in the form of XML.
  3. Onboard operational data store: Event data that is received from historian systems is converted to the format expected by PMQ, which is eventually populated in the analytical data store. This onboarded data is aggregated data and includes key performance indicator (KPI) and profile information.
  4. Predictive model: IBM SPSS® executes pre-built analytical models, resulting in scores. KPIs are analyzed by the system on a continuous basis. In response to the scores and the current KPI values, SPSS generates recommendations by using the pre-configured business rules.
  5. Enterprise Asset Management (EAM) systems: The received recommendation can be used to initiate or modify a work order in EAM (Maximo) systems for maintenance of the compressor. This event also provides an automatic email alert in all such instances.

High-level configuration to integrate IBM PMQ with ILS deviceWISE

Configure MatrikonOPC to simulate tag values for a compressor

Create an alias group in the MatrikonOPC Simulation Server, with the required alias for each parameter, as shown in Figure 2. (For more information about MatrikonOPC, see Related topics.)

  1. Open the Matrikon OPC Server for Simulation.
  2. Right-click on Alias Configuration and select Insert Alias Group from the pop-up menu.
  3. Provide a suitable name for the alias group.
  4. In the Contents of alias group frame for the newly created group, right-click and select Insert New Alias from the pop-up menu.
  5. Provide a suitable name for the alias/parameter.
Figure 2. Alias group and its contents in Matrikon OPC
Screen capture of a list of all parameters (compressor tags) configured as aliases within the alias group in Matrikon OPC
Screen capture of a list of all parameters (compressor tags) configured as aliases within the alias group in Matrikon OPC

Configure ILS deviceWISE

  1. Create a device of type DA CLIENT in ILS deviceWISE and specify the required OPC server URL. (The OPC server URL field differs per your setup. It is not a generic URL to be used by all.)
    Figure 3. Device of type DA Client, pointing to the correct OPC server
    Screen capture of a new device with name 'PAMDACLIENT' and type 'DA Client' created in deviceWISE workbench. The correct OPC server URL is provided in the Configuration section.
    Screen capture of a new device with name 'PAMDACLIENT' and type 'DA Client' created in deviceWISE workbench. The correct OPC server URL is provided in the Configuration section.

    After the device is connected, it displays the items n the Variable tab as in Figure 4.

    Figure 4. DA Client with a list of available alias groups and their aliases that are configured in Matrikon OPC
    Screen capture of a DA Client of name 'PAMDACLIENT,' its alias group 'PAMGRP,' and a list of aliases that were configured in Matrikon OPC. These are visible once the DA Client is started.
    Screen capture of a DA Client of name 'PAMDACLIENT,' its alias group 'PAMGRP,' and a list of aliases that were configured in Matrikon OPC. These are visible once the DA Client is started.
  2. Create a WebSphere MQ transport and provide the required queue manager, queue, channel, and host name.
    Figure 5. WebSphere MQ transport that is created in deviceWISE
    Screen capture of a WebSphere MQ transport 'PAMESBC' created in deviceWISE. The necessary parameters - host, queue manager, port, channel, and queue name - are provided.
    Screen capture of a WebSphere MQ transport 'PAMESBC' created in deviceWISE. The necessary parameters - host, queue manager, port, channel, and queue name - are provided.
  3. Create a transport map for each tag by selecting the previously created IBM MQ transport. Repeat this step for each tag.
    Figure 6. Transport map
    Screen capture of a new transport map created, using the previously created WMQ transport.
    Screen capture of a new transport map created, using the previously created WMQ transport.

    Figure 7 provides a screen capture of the XML message that is generated.

    Figure 7. XML message that is generated after the map is successfully created
    Screen capture of an XML message template that is generated after a transport map is successfully validated and created for a tag.
    Screen capture of an XML message template that is generated after a transport map is successfully validated and created for a tag.
  4. Create a project within the node, as shown in Figure 8.
    1. In the NEW NODE tree in deviceWISE, expand NEW NODE.
    2. Right-click on the projects item, and select New from the menu.
    3. Provide a new project name in the wizard.

      A new project then appears in the Projects tab, as shown in Figure 8.

    Figure 8. A new project that is created under Node section in deviceWISE
    Screen capture of a new project of name 'PAMC_Comp2' created under the Node section in the deviceWISE workbench.
    Screen capture of a new project of name 'PAMC_Comp2' created under the Node section in the deviceWISE workbench.
  5. Create a trigger for each tag within the project by using the Canvas editor.
    Figure 9. Canvas editor, depicting a new trigger for a tag
    Screen capture of a trigger created with mediation for a tag using 'Data' as the trigger event type and the required variable name from the available list.
    Screen capture of a trigger created with mediation for a tag using 'Data' as the trigger event type and the required variable name from the available list.

    After the trigger definition is validated and saved, it appears within the project, along with all the other triggers, as shown in Figure 10.

    Figure 10. Project with a list of all available triggers in deviceWISE workbench
    Screen capture of a project containing a list of all create triggers (for their respective tags).
    Screen capture of a project containing a list of all create triggers (for their respective tags).

Configure IBM PMQ

Master data is the type of resource that you want to manage, such as people, parts, assets, pieces of equipment, and processes. Master data is normally loaded by using one of the supplied connectors or the Flat File API. The connectors and the Flat File API use IBM Integration Bus flows to transform the data into the required form and to update the data in the IBM Predictive Maintenance and Quality database.

Explore master data and other concepts in the PMQ solution guide (see Related topics).

The following master data files must be loaded in PMQ data store to populate the master tables:

  • location_upsert.csv
  • measurement_type_upsert.csv
  • profile_variable_upsert.csv
  • resource_upsert.csv
  • source_system_upsert.csv

The resource master data sheet contains a list of all compressors and their attributes, as shown in Figure 11.

Figure 11. Sample master data sheet for a resource in IBM PMQ
Screen capture of a sample master data sheet required for populating the master resource table in IBM PMQ. Some of the required entries are a list of all compressors - their name, type, and sub type.
Screen capture of a sample master data sheet required for populating the master resource table in IBM PMQ. Some of the required entries are a list of all compressors - their name, type, and sub type.

Test the solution

Start the trigger that is created in ILS deviceWISE.

  1. Right-click on the trigger present in a project under 'Node' in deviceWISE.
  2. Select Start to start the trigger.
Figure 12. Starting trigger in ILS deviceWISE workbench
Screen capture of a right click on a trigger created in ILS deviceWISE to start it.

Starting the trigger sends a message into the queue that was defined in the transport section. The message is of the format defined in the transport map definition. Data that is pushed from ILS is received in XML in a WebSphere message queue.

You can browse for the XML message received from ILS.

Figure 13. List of messages that are received in WebSphere MQ
Screen capture of a list of all XML messages received in a queue defined in WebSphere MQ.
Screen capture of a list of all XML messages received in a queue defined in WebSphere MQ.

You can double-click any one of the XML messages to see a detailed view of the data present in the XML, as shown in Figure 14.

Figure 14. Detailed view of XML message
Screen capture of a detailed view of one of the XML messages received in the WebSphere queue in MQ, including message data and message data bytes.
Screen capture of a detailed view of one of the XML messages received in the WebSphere queue in MQ, including message data and message data bytes.

The event data that is received from historian systems is converted to the format expected by PMQ, which is eventually populated in the analytical data store. This onboarded data is aggregated data and includes KPI and profile information.

You can see a screen capture of the event observation table in PMQ data store, as shown in Figure 15.

Figure 15. Data onboarded in the PMQ data store
This image shows a screen capture of the data that has been onboarded in the PMQ datastore. Columns include Resource ID, Serial No, Model No, Language ID, Location ID, Tenant ID, Measurement Type, Period Max, and Profile Date.
This image shows a screen capture of the data that has been onboarded in the PMQ datastore. Columns include Resource ID, Serial No, Model No, Language ID, Location ID, Tenant ID, Measurement Type, Period Max, and Profile Date.

Conclusion

The IBM Predictive Maintenance and Quality solution helps you monitor, analyze, and report on information that is gathered from devices and other assets and recommend maintenance activities. PMQ uses ILS deviceWISE to integrate seamlessly with level 2 systems and historians to perform predictive and business analytics on the operational data. This analysis provides the hot spot identification of a problem and the corresponding resolution to avoid a forced outage.


Downloadable resources


Related topics


Comments

Sign in or register to add and subscribe to comments.

static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Data and analytics
ArticleID=988443
ArticleTitle=Integrate IBM Predictive Maintenance and Quality (PMQ) with ILS deviceWISE to onboard high-value asset data
publish-date=11062014