Workflow

The purpose of Asset Management workflow is to extract and load assets (Equipment and or Functional Location records) from your EAM System to Predix Essentials. As these records are loaded, they will be related to a superior asset record, if one is identified on the asset. Assets are managed in the EAM system with the data being transferred to Predix Essentials to support analysis.

In the following workflow diagram, the blue text in a shape indicates that a corresponding description has been provided in the sections that follow the diagram.

The purpose of the Event Management Workflow is to extract and load notification and order information from your EAM System to Predix Essentials as work history records. As these records are loaded, they may be related to an equipment and/or functional location record, if they are identified on the records.

In the following workflow diagram, the blue text in a shape indicates that a corresponding description has been provided in the sections that follow the diagram.

The purpose of the Notification Creation Workflow is to create a notification in SAP in reference to a Predix Essentials Recommendation, and then take data from the new notification to populate the data on the recommendation.

In the following workflow diagram, the blue text in a shape indicates that a corresponding description has been provided in the sections that follow the diagram.

Work Management Integration workflows manage the collection of detailed condition assessment data like inspections and calibrations, while accounting for resources and costs on orders in the EAM system. The Task & Confirmation Generation workflow documents the approach where the schedule is managed in SAP. The Work Management Interface program creates task records in Predix Essentials. Each of these will contain information about the EAM maintenance plan, item, task list, work order, and operation from which it was created.

In the following workflow diagram, the blue text in a shape indicates that a corresponding description has been provided in the sections that follow the diagram.

Work Management Integration workflows manage the collection of detailed condition assessment data like inspections and calibrations, while accounting for resources and costs on orders in the EAM system. The Work Order Generation Workflow documents the approach where the schedule is managed in Predix Essentials. The adapter generates work orders in SAP based on Predix Essentials Inspection or Calibration Tasks triggered by the call horizon interval on the Predix Essentials task.

In the following workflow diagram, the blue text in a shape indicates that a corresponding description has been provided in the sections that follow the diagram.

Persona: System Administrator

The Predix Essentials System Administrator will configure the APM Connect Job Conductor to define what jobs will be run, assign the context parameters, and schedule the triggers to execute the job on a scheduled basis. Alternatively, the job can be executed manually from the Job Conductor. Then, you will update the context file that is located on the APM Connect server to apply assigned filters for the extractions.

Persona: Solution Administrator (EAM)

The EAM Solution Administrator is responsible for managing the master data (Location, Equipment & taxonomy structure) as well as the asset hierarchy in the EAM system. The administrator will follow his or her own processes/procedures for loading new data or updating existing master data.

Persona: Predix Essentials

When the job executes, it will extract records that are used to store information about locations in the EAM system, including but not limited to the locations at which the physical pieces of equipment are installed. The job will use the context file parameters as filters to define the data that is extracted.

Persona: System Administrator (APM)

This step is not necessary to complete the data transfer. However, it is a check to ensure that the transfer was executed successfully. The execution log is used to view information about the job execution such as its status, ID, trigger type, and other details. The log also contains information about the errors and warnings that occurred during the execution process. If there are errors, then the Solution Administrator can modify the parameters, and then re-run the job manually.

Persona: System Administrator

The Predix Essentials System Administrator will configure the APM Connect Job Conductor to define what jobs will be run, assign the context parameters and schedule the triggers to kick off the job on a scheduled basis. Alternatively, the job can be kicked of manually from the Job Conductor. Then they will update the context file which is located in the APM Connect server file to apply assigned filters for the extractions.

Persona: System Administrator

The EAM Analyst (Planner/Scheduler) is responsible for creating EAM specific requests for work to be completed. These documents have various names based on the EAM system. In SAP they are called Notifications or Work Orders, and in Maximo Work Orders and Service Requests. They will follow their own processes/procedures for creating the documents, and approval workflows as configured in their own system.

Persona: Analyst

User creates a recommendation manually or from any of the Predix Essentials modules. After all the approval steps are completed, select the box to the left of EAM Notification check box to trigger the Notification job.

Persona: Predix Essentials

The Job will send the information from the work order and/or notification to APM as a Work history record.

APM Connect will use the common filters in the context file to determine the scope of the extraction required by that Job. Common filters include: Maintenance Plant, Notification & Work Order types, Equipment & Functional Location Taxonomy, Create and Change dates, Functional Location, Equipment numbers.

The job to extract new or updated items from the EAM source can be executed automatically based on the schedule parameters. This method ensures synchronization between your SAP database and your Predix Essentials database.

Persona: Solution Administrator

This step is not necessary to complete the data transfer. However, it is a check to ensure that the transfer was executed successfully. The execution log is used to view information about the Job execution such as its status, ID, trigger type, and other details. The log also contains information about the errors and warnings that occurred during the execution process. If there are errors, then the Solution Administrator can modify the parameters, and re-run the job manually.

Persona: Predix Essentials

A notification created in your EAM system that represents the Predix Essentials recommendation.

The notification is created in the EAM system and the Predix Essentials Recommendation is updated, the notification is created in SAP, and the recommendation will be updated with values for:

• Work Request Reference
• Work Request Equipment
• Work Request Functional Location

Persona: Predix Essentials

The job updates the Predix Essentials Recommendation with the EAM notification reference information.

Persona: Analyst

The intended work detailed on the Predix Essentials Recommendation record is completed and closed.

Persona: Solution Administrator (EAM)

This workflow assumes that the required configuration is in place to set tasks to a control key. In SAP, create a maintenance plan that contains a maintenance item, task list, and at least one operation. One of the operations must meet the criteria in the task configuration table.

Persona: Predix Essentials

When the Work Management Job is run, an Inspection Task record is created for each configured operation. This task record now has field values containing identifying information about the maintenance plan, maintenance item, task list, and the operation. The Inspection record must be linked to the Equipment record representing the asset in SAP.

Persona: Solution Administrator (EAM)

Schedule the maintenance plan. Then, the system generates a work order for it, and the work order is released.

Persona: Predix Essentials

When the Work Management job is run, the Inspection Task record is updated with information about the maintenance plan, maintenance item, task list, and operation.

Persona: Technician

An inspection is entered for the equipment and task used in this example. This can be from many of the inspection event families, such as Full Inspection.

Persona: Technician

When actual work hours are entered for the inspection and it is marked closed, a Confirmation record is automatically created in Predix Essentials, and a corresponding time confirmation is automatically entered for the work order in SAP. The work order number is also automatically removed from the Inspection Task record.

Persona: Predix Essentials

A corresponding time confirmation for the work order is created in SAP. The work order number is also automatically removed from the Inspection Task record.

Persona: Technician

In this process flow, the work is managed in Predix Essentials and related to objects in the EAM system. This step creates the Task in Predix Essentials that is linked to the Equipment record.

Persona: Technician

A query is made on the SAP system to return Task Lists that exist in SAP, so that the users can select the required task list that should be linked to the Predix Essentials Task.

Persona: Technician

A call horizon is entered on the Predix Essentials task, which controls the interval at which work orders are generated in SAP.

Persona: Predix Essentials

The job creates a Work Order in SAP based on the associated Task List/Maintenance Plan, and the work order number is copied back to the task in Predix Essentials.

Persona: Technician

This is not a required step in the workflow, but can be used to validate the process. The process can be validated by searching for the Equipment in the Global Search, verifying the relationships, and verifying that the task includes the EAM work order data.

Persona: Solution Administrator

Define process data integration connections. Standard process data integration interfaces offer connection to field device systems such as condition monitoring devices, instrumentation, process historians, etc.

Persona: Solution Administrator

Define parameters for the acquisition of data from the data source. These parameters can include data polling frequency (i.e., how often data will be acquired and aggregated for evaluation), filtering (for example, severity and type of event), data retention (for example, stored readings for process historian tags), etc. Parameters may be stored in Predix Essentials records, or in system configuration files.

Persona: Solution Administrator

Once the data acquisition parameters are defined, test the connection to ensure that data is accessible in Predix Essentials. Note that in some types of source, a Test Connection feature is provided. In others, the administrator will need to confirm that data is flowing at the Preview Tag Data step.

Persona: Solution Administrator

An initial data synchronization is conducted that creates, in Predix Essentials, records representing Tags and other required elements, such as Enterprises (GE) and AMS Asset folders (AMS), depending on the M2M source. A Tag can represent a time series of data for a single monitored parameter, a summarized or calculated result, or a stream of events. Tags are kept in synchronization with changes in the field data systems. If a Tag that is used in Predix Essentials is removed from the source system, the Tag will be highlighted as removed, alerting the administrator and allowing him or her to update health indicators, policies, etc., to use a different Tag.

Persona: Solution Administrator

Preview the data on a Tag to confirm that Tags are delivering the expected data. For OPC Tags, this is facilitated by a link to view the HDA data in a trend chart.

Persona: Solution Administrator

Tags are linked to assets to provide the correct context for data analysis. Settings for individual Tags may be adjusted to ensure that the data required for specific asset management workflows is available (for example, setting up stored readings). This establishes a subscription to retrieve data automatically, if applicable to the data source type.

Data including Alerts, Events, and Reading for all monitored Tags is acquired in a continuous stream from the field device systems.

Monitored data is used in Core Analysis, Asset Health Management, Policies, and Production Loss Accounting processes. See relevant workflows for details.

Persona: Solution Administrator

Define process data integration connections. Standard process data integration interfaces offer connection to field device systems such as condition monitoring devices, instrumentation, process historians, etc.

Persona: Solution Administrator

Define parameters for the acquisition of data from the data source. These parameters can include data polling frequency (i.e., how often data will be acquired and aggregated for evaluation), filtering (for example, severity and type of event), data retention (for example, stored readings for process historian tags), etc. Parameters may be stored in Predix Essentials records, or in system configuration files.

Persona: Solution Administrator

Once the data acquisition parameters are defined, test the connection to ensure that data is accessible in Predix Essentials. Note that in some types of source, a Test Connection feature is provided. In others, the administrator will need to confirm that data is flowing at the Preview Tag Data step.

Persona: Solution Administrator

An initial data synchronization is conducted that creates, in Predix Essentials, records representing Tags and other required elements, such as Enterprises (GE) and AMS Asset folders (AMS), depending on the M2M source. A Tag can represent a time series of data for a single monitored parameter, a summarized or calculated result, or a stream of events. Tags are kept in synchronization with changes in the field data systems. If a Tag that is used in Predix Essentials is removed from the source system, the Tag will be highlighted as removed, alerting the administrator and allowing him or her to update health indicators, policies, etc., to use a different Tag.

Persona: Solution Administrator

Tags are linked to assets to provide the correct context for data analysis. Settings for individual Tags may be adjusted to ensure that the data required for specific asset management workflows is available (for example, setting up stored readings). This establishes a subscription to retrieve data automatically, if applicable to the data source type.

Data including Alerts, Events, and Reading for all monitored Tags is acquired in a continuous stream from the field device systems.

Monitored data is used in Core Analysis, Asset Health Management, Policies, and Production Loss Accounting processes. See relevant workflows for details.

Persona: Various

The tag information that is generated in this workflow is consumed by various Predix Essentials workflows.

• Health Indicators: If appropriate Health Indicator Mappings exist and the AHM service is configured and running, Health Indicator records will be created automatically when tags are linked to assets, and are used by other Predix Essentials processes.

  Go to the Asset Health workflow.

• Alerts, Events, Readings, etc.: Data for all monitored Tags is acquired in a continuous stream from the field device systems, is used by other Predix Essentials processes.

• Various: Monitored data is used in core analysis, Asset Health Management, Policies, and Production Loss Accounting processes.