Understanding This AppendixThis appendix discusses real-life scenarios for using PeopleSoft Maintenance Management to:
Set up smart tags in a problem tree.
Process linked PM schedules.
Understanding This AppendixThis appendix presents scenarios of how to use some of the features within PeopleSoft Maintenance Management. These real-life examples describe some of the intended uses of these features, enabling you to understand how these features might be applied to your own organization.
The real-life scenarios described within this PeopleBook may not conform to the business rules and procedures within your organization. Do not construe these examples as consulting or implementation advise for your specific industry or your individual organization. You should adapt or disregard the information presented here based on the needs of your organization. Oracle does not guarantee that the information included here will work as intended within your customized environment.
Example: Setting Up Smart Tags in a Problem TreeSome organizations assign a tag number consisting of a series of codes to an asset in PeopleSoft Asset Management to enable users to easily identify the asset. This tag number is subdivided into groups of characters, where each group represents a particular attribute or type of asset. PeopleSoft Maintenance Management refers to these tag numbers as Smart Tags.
For example, smart tag number C4BFGMTR0002. The groups of characters and the values that they represent are:
C4 – Combustion Turbine 4.
BFG – Boiler Flue Gas System.
MTR – Motor.
0002 – sequential equipment number.
Once the assets are set up in PeopleSoft Asset Management, users can set up these codes on successive levels of a problem tree in PeopleSoft Maintenance Management. When users enter a service request, they can narrow the list of eligible service request assets based on the smart code set up in the problem tree. User associate the code with a problem group, problem, service center and work order criteria on the problem tree.
Users set up a problem tree, select a problem group, problem, service center and work order criteria, and set up each level of the problem tree based on the character groups that comprise the smart tag. When users enter a service request, the problem tree setup enables the user to search for an asset based on the character group levels.
These pages demonstrate how to set up the problem tree using smart tags and how a user can enter a service request and narrow their search for an asset using smart tags.
1. Access PeopleSoft Asset Management and make sure that the assets are set up under the Asset Type of Equipment. In our example, these assets are: C4BFGMTR001, C4BFGMTR002, C4BFGMTR003.
2. Access Set Up Financials/Supply Chain, Product Related, Maintenance Management, Problem Cause Resolution Setup, Problem Tree.
3. Set up the top parent node as EQUIPMENT.
Select the following information:
Description: Owned Equipment
Short Description: EQUIPMENT
Problem Group: MECHANICAL
Problem: No Start
Asset Lookup Field: Tag Number
Asset Type: Equipment
Service Center Information:
Roles – SetID: SHARE
Roles – Service Center: US001
Roles – Agent Role: Call Center Agent
Roles – Technician Role: Technical Specialist
Work Order Defaults – Business Unit: US001
Work Order Defaults – Service Group: MAINT (maintenance)
Work Order Defaults – Work Type: CM (corrective maintenance)
Work Order Defaults – Priority: 1
Click Save.
4. Click the Add Child Node button and add TURBINE as the Middle Node.
Notice that EQUIPMENT displays as the Parent Node.
Enter the description: Combustion Turbine 4.
Enter the short description: C4
Enter C 4 in the Smart Tag field and save the page.
5. Click the Add Child Node button and enter BOILER as the Middle Node.
Notice that Turbine is the Parent Node.
Enter Boiler Flue Gas System as the long description and BOILER as the short description.
Enter BFG in the Smart Tag and save the page.
6. Click the Add Child Node button and enter MOTOR as the Bottom Node.
Enter the long and short descriptions as MOTOR.
Enter MTR in the Smart Tag field and save the page.
7. Let's create a service request to repair one of these C4BFGMTR assets. Access Employee Self-Service, Service Request, Service Request Wizard.
8. The Requested By page defaults the information based on the person signed on to the system. Employees and non-employees can create a service request. Click Next to continue.
9. Click the EQUIPMENT radio button as the type of service request and click the Next button. This field displays because we set up EQUIPMENT as the top node of the Problem Tree.
10. Based on the EQUIPMENT problem tree middle node that we set up, C4 displays to narrow down the type of equipment that needs repair. Click the C4 radio button and click the Next button.
11. Based on the EQUIPMENT Problem Tree middle node that we set up, BOILER displays to narrow down the type of C4 equipment that needs repair. Click the BOILER radio button and click the Next button.
12. Based on the EQUIPMENT Problem Tree bottom node that we set up, MOTOR displays to narrow down the type of C4 boilers that need repair.
13. After narrowing our search based on selecting options from the EQUIPMENT problem tree:
Select Service Center: USA-New York.
Select the Required Date for the repair: Current system date is the default value.
Enter a subject (optional): Boiler Motor.
Enter a description (optional): Does not start.
Select the Tag number search icon to search for the tag number of the asset that you repaired.
15. At the top of the Asset Search page, you can enter the asset characteristics to narrow your search for the tag number. In this case we entered C4 for the Tag Number and clicked the Search button. The three assets we set up in PeopleSoft Asset Management display as the results of the search. Select C4BFGMTR003 as the tag number for the asset that needs repair and click the Search button.
16. The Service Request – Fulfillment Detail page displays again with in the Tag Number and Asset Location fields. Click the Next button to continue.
17. The Service Request - Summary page displays. Review this page for accuracy. If there are errors, you can click the Previous button to make changes. If the information is correct, click the Finish button.
18. A page displaying the Service Request ID and check mark indicating that the submission of this service request was successful displays. Click the OK button to complete this service request. This service request will now appear in the My Service Requests component.
See Creating a Service Request.
Examples: Processing Linked PM SchedulesYou can select one of these methods to link secondary schedules to a primary schedule:
Days Tolerance.
Linking by Cycle.
This section presents examples of how each of these methods are processed using the Preventive Maintenance or Projection process.
Examples: Linking PM Schedules Using the Days Tolerance MethodWhen the Preventive Maintenance or Projection process schedules maintenance, and you defined secondary schedules with the days tolerance method, the system compares the calculated due date of the primary schedule due date to due date of each linked secondary schedule and:
Links the scheduled maintenances if the dates are the same.
Links the scheduled maintenances if the difference between the dates is less than or equal to the days tolerance defined on the linked secondary schedule.
Note. The due date of the primary schedule can be a number of days earlier or later than the due date of the secondary schedule as long as the number of days is within the specified days tolerance.
Does not link the maintenances if neither of these scenarios occur.
Example 1
Major service due date: 05/22/2009
Minor service due date: 05/25/2009
Current date: 05/22/2009
Days tolerance: 7 days
Maintenances will be linked.
Example 2
Major service due date: 05/22/2009
Minor service due date: 05/31/2009
Current date: 05/22/2009
Days tolerance: 7 days
Maintenances will NOT be linked.
Example 3
Major service due date: 05/26/2009
Minor service due date: 05/22/2009
Current date: 05/22/2009
Days tolerance: 7 days
Maintenances will be linked.
Example 4
Major service due date: 05/22/2009
Minor service due date: 05/22/2009
Current date: 05/22/2009
Days tolerance: 7 days
Maintenances will be linked.
Examples: Linking PM Schedules Using the Linking by Cycle MethodWhen maintenances are scheduled through the Preventive Maintenance or Projection process, and there are secondary schedules defined using the linking by cycle method, the system will calculate the current occurrence field of the cycle each time a secondary schedule becomes due. The formula is the current occurrence = current occurrence + 1. The process compares the current occurrence to the cycle occurrences. If they are the same, the process will link the maintenances, reset current occurrence, and add 1 to current cycle field. If the cycle occurrences are not the same, the process will not link the maintenances.
Since maintenances can be scheduled for multiple due dates in the future using the Projection process, the process will continue to calculate the current occurrence and compare the current occurrence to the cycle occurrences for each secondary projection.
Example 1
Major service's due date: It doesn't matter.
Minor Service due date: 05/22/2009
Current date: 05/22/2009
Current occurrence: Last occurrence + 1 = 4
Cycle total occurrences: 4
Current cycle: Current cycle +1
Maintenances will be linked.
Example 2
Major service's due date: It doesn't matter.
Minor Service due date: 05/22/2009
Current date: 05/22/2009
Current occurrence: Last occurrence + 1 = 2
Cycle total occurrences: 4
Current cycle remains the same.
Maintenances will NOT be linked.
Example 3
Major service's due date: It doesn't matter.
Minor Service due date: 05/31/2009
Current date: 05/22/2009
Current occurrence remains the same.
Cycle total occurrences: 4
Current cycle remains the same.
Maintenances will NOT be linked.
See Setting Up and Generating Preventive Maintenance Work Orders.