Understanding PCR Setup and Tracking

PCR tracking enables PeopleSoft Maintenance Management users to categorize their work order transactions using predefined problem, cause, and resolution codes. These codes are used to record:

• The problem or the nature of the maintenance or repair issue.

• The cause or underlying reason for a specific problem.

• The resolution or solution to the problem as reflected in the work task detail and overall job content of the work order.

You can link PCR codes in a hierarchy going from problem to cause to resolution and organize them under a user-defined problem group that describes the overall nature of the problem, such as mechanical, electrical, or hardware. After you have categorized work order tasks with PCR codes over a period of time, you can subsequently analyze these PCR code combinations to determine if there are repeatable patterns of occurrences. This information enables you to identify equipment prone to failure, as well as problems that occur frequently. Based on the frequency of the problem, you can decide if you want to set up reusable work order job templates, which predefine the resources needed to solve a problem.

The following table displays examples of user-defined problem group setups:

Based on the some of the items in the Problem Group setup above, you can create these work order task and work order job templates:

The implementation of PCR tracking includes:

• Setting up PCR codes.

• Setting up one or more problem groups.

• Optionally associating a resolution code with a work order task and job template to facilitate template lookup.

A problem group consists of three nested scroll levels and is used to establish the logical relationships or links between problems, causes, and resolutions in a series of one-to-many associations. This means that each higher level PCR code can in turn be linked to one or many lower level codes. Specification of a complete chain of problem to cause to resolution codes is optional. If you choose to create a problem group chain:

• You can associate problem codes with a problem group.

• You can specify a lower level code only if you previously entered a corresponding higher level parent code.

  You must enter these values consecutively with no gaps in between them. For example, a cause code must always have a parent problem code, and a resolution code must have a parent cause code.

• You can optionally link a problem code that you specified for a problem group to one or more individual cause codes.

• You can optionally link each cause code that you specified for a problem group to one or more individual resolution codes.

• You can link a problem group definition with one or more asset classification combinations.

  When users identify a target asset for a task line on a work order, the system will use the defined type, subtype, manufacturer, and model information of the asset to determine which problem group or groups and subsequent problem, cause, and resolution data should be made available in the prompt lists for these fields.

  If a problem group definition is not linked to at least one asset classification combination, it is considered a standalone definition. This occurs when you create a work order or a work order task that does not reference an asset as the object of the work being performed. For example, you can create preventive maintenance work orders based on a location, such as a shop, where the work order task is to take the inventory of a shop on a monthly basis. The problem group might be identified as Other to include miscellaneous problems.

PCR Tracking for Work Orders

Users can enter problem, cause, and resolution codes in a work order up to the point that the work order is closed, enabling them to track and analyze similar problems. For example, a planner or clerk might enter a problem group and problem when the work order is created. Later a technician may add the cause and recommend a resolution in the technician's workbench. Users may also use this functionality to search for an appropriate work order task template to resolve a particular maintenance or repair problem. They may optionally link problem group definitions with various asset classification combinations in order to facilitate their reuse or assignment when entering work orders.

Users may associate work order task template and job template definitions with a specific resolution code to streamline the search for templates that are applicable to a particular problem, cause, and resolution chain. When you want to select either a work order task or work order job template to associate with a work order or work order task, you can search for the template based on the problem group and problem, cause, and resolution codes associated with a template. This work order entry lookup capability is only possible if the resolution code referenced on a particular template definition is linked under a problem group definition as part of a complete problem, cause, and resolution chain.

You can select a problem group, and problem, cause, and resolution codes for work order tasks. It is not necessary to select all four values. However, the system does not permit gaps in the chain of codes. Prompt tables for the various codes ensure that specification of a lower-level code in the chain, such as resolution, is only possible if users enter all higher-level codes (problem group, problem, and cause).