Asset Management Workflow

The purpose of Asset Management workflow is to extract and load assets (Equipment and or Functional Location records) from your EAM System to APM. 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 APM to support analysis.

In the following workflow diagram, the blue text in a shape indicates that the corresponding description has been provided in the sections that follow the diagram. For more information, refer to the Interpreting the Workflow Diagrams topic in the APM Product Workflows documentation.

Note: For information on the personas associated with a APM module, refer to the APM Product Workflows documentation.

Persona: System Administrator

The APM 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: APM

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.