preventive maintenance wp

Enterprise Asset Management(eAM) – Preventive Maintenance

An Oracle White Paper December 2005

ii

eAM – Preventive Maintenance

EXECUTIVE SUMMARY ................................................................................................ 1 INTRODUCTION.............................................................................................................. 1 DESCRIPTION OF THE INITIAL SETUP ................................................................ 2 SET NAME........................................................................................................................... 2 METER .................................................................................................................................. 3 LAST SERVICE INFORMATION................................................................................. 4 PREVENTIVE MAINTENACE SCHEDULE............................................................ 5 Day Interval Rules............................................................................................................ 6 Scheduling Options.......................................................................................................... 6 Start to Start .................................................................................................................. 6 Forecast Work Order ............................................................................................. 6

Start to End................................................................................................................... 8 End to Start................................................................................................................... 8 Lead Time In Days ................................................................................................. 9

End to End ................................................................................................................. 10 Reschedule Manual Work Orders ...................................................................... 10

Runtime Rules................................................................................................................. 12 No Meter Readings.................................................................................................... 14 Usage Rate Not Recalculated................................................................................... 14 Usage Rate Recalculated ........................................................................................... 15 Work Order Completion – Change in Last service Information ...................... 17 Meter Reading Reset.................................................................................................. 18 “Schedule Based On”................................................................................................ 19

List Dates......................................................................................................................... 21 Generate Preventive Maintenance Work Orders program................................. 21

SUPPRESSION.................................................................................................................. 22 Tolerance In Days .......................................................................................................... 25

PREVENTIVE MAINTENANCE TEMPLATE....................................................... 26 CONCLUSION.................................................................................................................. 26 APPENDIX A: LOG FILE CREATED BY THE “GENERATE PREVENTIVE MAINTENACE WORK ORDER” CONCURRENT REQUEST ........................ 27

1 –eAM – Preventive Maintenance

eAM – Preventive Maintenance

EXECUTIVE SUMMARY

Maintenance activities are carried out on the assets in an organization, the details of

which are captured through work orders. The work orders can be generated either

manually or automatically. Maintenance activities can be scheduled periodically

based on time interval or based on the readings of meters associated to the asset or

based on predefined calendar dates. Enterprise Asset Management makes periodic

scheduling possible through Preventive Maintenance.

INTRODUCTION

Enterprise Asset Management (eAM) enables users to optimally plan and schedule

maintenance activities with minimal disruption to an organization’s operations or

production. By effectively monitoring an asset’s operating condition, effective

preventive maintenance strategies can be implemented. Preventive maintenance

activities reduce the probability of failure or degradation of the assets’ physical

conditions. Preventive maintenance helps to establish a maintenance strategy that

ensures minimal downtime.

It is possible to forecast the frequency at which preventive maintenance should be

performed. The frequency is decided based on meter readings, runtime intervals or

calendar dates. Meters are entered to measure any maintained number that needs to

be measured and periodically serviced, based on the measurement.

Preventive Maintenance Schedules(PM schedules) are defined for asset -activity

combinations. Multiple schedules can be defined for experimenting with different

maintenance strategies (simulation and what-if scenarios) but it is the default

schedule which is used for generating work orders. The work orders are generated

from the PM schedules either by running the ‘Generate Preventive Maintenance

Work Orders’ concurrent program or from the ‘Forecast Work Orders’ form.

This paper covers the basic setup and functionality of preventive maintenance.

Runtime Rules, Day Interval rules and List dates are covered in this paper .

Readers with an understanding of basic concepts of enterprise Asset management would be in a position to appreciate the entire gamut of this paper.

Note: The paper has been written with Oracle Application Release 11.5.9 in mind

The screen shots indicated pertain to 11.5.9 only.


DESCRIPTION OF THE INITIAL SETUP

The maintenance organization used in this paper is EM1. “Cabs” is the Asset group

defined. The Asset numbers under this asset group are CAB001 to CAB006. There

are two maintenance activities carried out on each of the above mentioned assets :

• Cab Maintenance – this activity involves all the maintenance activities

carried out on the cab

• Cab Engine Overhaul – this activity is carried out only on the cab’s engine.

The routing for both the activities are the same. The first operation involves

department “Contract”. This department has one resource “OSP Res” and the

usage defined for this resource is 12 hours . The second operation is done in “F-

Maint” department and uses resource “Cab-Mech” for 12 hours. The total

duration for completing the activity is 24 hours.

SEQ Department Resource Assigned units Usage UOM

10 Contract OSP Res 1 12 HR

20 F-Maint Cab-Mech 1 12 HR

The resources “OSP Res” and “Cab-Mech” are available 24 hours. The calendar for

the organization is defined as all seven days in the week as working days and does

not include any exceptions.

SET NAME

"Preventive Maintenance Set Name" gives users the option of creating multiple PM

schedules for one asset-activity association and provides ways of experimenting

with different maintenance strategies. A PM schedule for an Activity and a

Maintained Number or Maintained Group must uniquely belong to a Set Name.

Set names are defined in the "Set Name" window (Navigation : Preventive

Maintenance � Set Name Definition). The set names used in this paper are

“Cab_Main” and “Cab_Simulation”.

Some important points to note :

• “Main” is a seeded set

• PM schedule for the same Maintenance Number and activity combination

can be created across sets

• Each PM schedule will have a ‘set name’ field. It is a mandatory field

• Every PM set has an end date. Every PM schedule that belongs to the set

must have its effective-to date before the end date of the PM set.

• There can only be one default PM schedule per asset-activity association.


Users will be able to set and unset a default PM schedule.

• Default PM schedules will be automatically picked up by the PM engine to

generate work orders.

• Non-default PM schedules will be mainly used for simulation and ‘What-If’

scenarios and they will never generate work orders

In the “Set Name” window, choose “Templates” to view or modify the PM schedule templates or choose “Schedules” to view or modify the PM schedules associated with the set name.

METER

Meters are associated with maintained numbers to measure a variable of the asset

or rebuildable item. Meters are entered to measure any Maintained Number that

needs to be measured and periodically serviced, based on the measurement.

Meters are defined using the meter definition screen.

• Enter a meter name ,description and a unit of measure (UOM) for the

meter. The meter defined here is OMCAB004_01 with a UOM of Hours.

• Choose whether the meter readings are ascending, descending or fluctuating.

• If the meter has to be used in scheduling, then mark the “Used In

Scheduling” check box. As soon as this is check marked, the “Rate (per

day)” and the “Number of Past Readings” fields are enabled.

• Enter the usage rate and the number of past readings (if “Used in

Scheduling” is marked) . The number of past readings designates how many


readings prior the scheduler should go to for calculating the usage rate. If

there are an insufficient number of readings, then the usage rate defined

here is used. A usage rate of 20 and a number of past readings of 5 is

entered for the meter OMCAB004-01

• The initial meter reading and the effective dates are optional. For meter

OMCAB004-01 , an initial reading of 0 was entered on 15th Nov, 2004

The Meter defined can be associated with the asset number (Navigation : Meter �

Meter Association) . Meter OMCAB004-01 is associated with Asset number

CAB004.

Another way to define meters is through the Meter Template . In the Meter

Template definition, meter templates are associated with maintained groups .After

the association, whenever a new asset number is created under the maintained

group, a meter is created and attached to the new asset number automatically.

LAST SERVICE INFORMATION

The last service information captures details of the date and the reading when the

last maintenance activity is done on an asset.

Last service reading captures the meter reading when the activity was performed

most recently on the asset. The last service reading cannot be greater than the last

meter reading (in case of ascending meter) or less than the last meter reading (for

descending meters)

Similarly, last service date captures the date when the activity was performed most

recently on the asset . Last service start date captures the date when the activity

started and last service end date captures the date when the activity ended. Last

service start/end date serves as a starting point for rule based scheduling.

The last service information is usually updated from the work order completion. When a work order is completed, the last service start & end date will be updated with the work order’s actual start & end date and the last service meter readings will be entered. The last service information can be modified from the “Last Service Information” screen (Navigation : Preventive maintenance � Last Service Info)


There is no meter associated with the asset number CAB001 so no meter details are seen in the screenshot provided above

PREVENTIVE MAINTENACE SCHEDULE

Preventive maintenance schedules are defined to create or forecast work orders

based on rules or based on a list of specific date. A preventive maintenance

schedule can be created on asset number –activity or asset route-activity

combination.

The PM schedule is defined in the “Preventive Maintenance (Schedule Definition)”

window ( Navigation : Preventive Maintenance � Schedule definition).

In the PM schedule definition window, enter the following details :

• Enter a unique “Schedule name”

• Choose the “Item type”. You could choose between Asset and rebuildable.

• Enter a valid set name. The set name must be defined in the “Set name”

definition window. Every Set Name has an end date. Every PM schedule

that belongs to the “Set Name” must have its effective-to date before the

end date of the PM Set Name.

• Select a “Maintained Number” . If the “Item Type” chosen is “Asset”, then

this field refers to the Asset number else it refers to the rebuildable number.

In the case of Non –serialized rebuildable item, then this field is not

required

• The maintained group is populated automatically as soon as a value is

entered for the maintained number field.

• Select the “Activity”. Only the activities associated with the asset number /

rebuildable is available in the list of values.

• Choose the Schedule type. The options available are “Rule Based” and “List

Dates”. The “Day Interval Rules” tab and the “Runtime Rules” tab are

enabled if you choose “Rule Based” schedule type . The “List dates” tab

becomes enabled when the schedule type chosen is “List dates”

• The Effective date defaults from the activity chosen. The “Effective from”

and “Effective To” dates can be updated

• Run to failure items are those whose items costs are cheaper than the

maintenance cost of the item. If the “Run To Failure” check box is selected,

the PM Scheduler will not automatically schedule the maintained number

and Activity association, however manual Work Orders can still be created.

• The “Default” check box, if marked, indicates that the PM schedule is the

default schedule for the maintained number–activity combination. Work

orders will be generated only based on the default PM schedules


Day Interval Rules

The day interval rule specifies the time span in days, between the creation of each

work order . This is based on the last service information.

For information on the “last service start date & end date”, pls refer to the Last

Service Information described above

The above PM schedule will be used to explain the Scheduling options

Scheduling Options

The “Scheduling Options” controls the way the work order dates are calculated by

the PM scheduler. This decided whether forward scheduling or backward

scheduling must be used by the PM Process.

Start to Start

This is a Forward Scheduling Method. The PM scheduler uses the base point as the “Last Service START date” and calculates the START dates for the scheduled work orders.

Forecast Work Order

In the Maintenance Workbench (Navigation : Work Order planning � Maintenance Workbench), choose the Asset number CAB001. In the work order form, Press on the “Forecast Work” button to get the “Forecast Work Order” form. In the “Forecast Work Order” form :

• The Start date would default to current date

• Enter the cutoff date. The Cutoff Date decides the date till which you would

like the Work Orders to be created from the suggested dates.


• The horizon is the difference between the start and cutoff date. If the

horizon is changed, then the cut off date gets recalculated

• Optionally enter a Set name. If a set name is entered then the “Simulate”

button gets enabled and the “Run” and “Implement” button grays out. On

the other hand if no set name is chosen, then the “Simulate” button is

grayed out and the “Run” and “Implement” buttons are enabled. . No PM

schedule will be picked up for the asset/activity association if there is no

simulation PM schedule with the set name existing.

• When ‘Combine with Default’ is checked, the default PM schedules gets

picked up in the cases where no PM schedules with the specified set name

exist. When ‘Combine with Default’ is not checked, only PM schedules with

the set name specified will be picked up by the PM engine.

For the asset CAB001 (schedule attached to this asset number is CAB001_CM), when the “Forecast Work Order” is run from the Maintenance Workbench, the following work orders are suggested .

The last service start date was 24th Nov, 2004. With a day interval of 30, the first

work order’s START date is suggested on 24th Dec, 2004 and the consecutive work

orders are created with a difference of 30 days.

The “Implement” button could be chosen to convert the forecasted schedules into work orders. Implementing the third line in the above schedule, would create work order with the start date as 22-Feb-2005 and completion date as 23-Feb-2005.


Start to End

This is a Backward Scheduling Method. The base point here is the “Last Service

START date” and using the base point, the PM process calculates the END dates

for the scheduled work orders.

For the PM schedule, CAB001_CM, change the Scheduling option to Start to

End.. The screenshot below shows the forecasted schedule for the asset number

CAB001 for the “Start to End” option

The last service START date was 24th Nov, 2004. With a day interval of 30, the first

work order’s END date is suggested on 24th Dec, 2004 and the consecutive work

orders are created with a difference of 30 days.

Implementing the third line in the above schedule, would create work order with

the start date as 21-Feb-2005 and completion date as 22-Feb-2005.

End to Start

This is a forward scheduling method . Here the PM scheduler uses the last service

END date to calculate the START dates for the scheduled work orders.

Changed the Scheduling option to End to Start for the schedule CAB001_CM and

forecasted the work orders. The last service end date was 26th Nov, 2004. With a

day interval of 30, the first work order’s START date is suggested on 26-Dec-2004

and the consecutive work orders are created with a difference of 30 days. The

suggested work orders are shown in the next screen shot.


Lead Time In Days

The Preventive Maintenance process suggests work orders to be created or

scheduled in the horizon between the forecast start date to the cut-off date

specified while running the process. Lead Time In Days specifies the work orders

for those extra days beyond the cut-off date mentioned. To illustrate this example,

for the schedule CAB001_CM, a value of 25 is entered against the “Lead Time In

Days” field.

The PM process was run with a cutoff date as 01st May, 2005. The lead time of 25 days was taken into the picture while running the PM process so a work order was also forecasted for 25th May 2005.


End to End

The PM scheduler uses the base point as the “Last Service END date” and

calculates the END dates for the scheduled work orders. This is a Backward

Scheduling Method.

Note : The “Lead Time In Days” is set to zero for the following simulations

Reschedule Manual Work Orders

In the PM schedule, mark the “Reschedule Manual Work Orders” check box. If the

box is checked, the unreleased manual work orders will be taken into account

during PM rescheduling, else not. PM engine will not reschedule firmed or released

work orders.

Another change introduced in the PM schedule, CAM001_CM, is the Multiple

Rules defined for the day interval rule. The interval between the scheduled work

orders is 30 days between 24-Nov- 2004 and 28-Feb-2005 . From 01-Mar-2005 to

15-Aug-2005 , the day interval specified is 45 days.

The details of the 3 work orders already existing for the asset CAB001 is shown

below

Sl Work Order

Number

Scheduled Start date Scheduled

Completion date

Status

1 EM182073 14-Jan-2005 05:31:00 15-Jan-2005 05:31:00 Unreleased

2 EM182074 10-Feb-2005 13:17:00 11-Feb-2005 13:17:00 Unreleased

3 EM181973 23-Jun-2005 00:00:00 24-jun-2005 00:00:00 Released


When the PM engine is run, the schedule shown below is proposed

Line 1, 2 ,4 and 5 in the above forecast corresponds to the interval rule of 30 days.

After 26th Mar, 2005, the interval rule of 45 days is added to get the next effective

date of 10th May ,2005. The next expected schedule must be with the schedule end

date of 24th Jun, 2005 but as there is already a work order on the 24th June, no work

order is suggested by the PM engine.

Also note that for the released work order EM181973, the action column contains

a value of “No Action”. For work order EM182073, the check box is marked

meaning that the work order will be rescheduled to the expected end date. For


work order EM182074, the check box is not marked so the work order will not be

rescheduled.

Implementing the forecasted work orders would provide the following work orders

The work orders forecasted for this schedule is shown below

Runtime Rules

Runtime rules are based on meters. The interval between the work orders is

calculated based on the interval divided by the usage rate.

Ensure that the following setup is complete before defining a runtime PM schedule

• Activity Definition

• Maintained Number or maintained Group - Activity Association

• Meter Definition

• Meter/Asset Association

• Maintained Group (Non-Serialized Rebuildable) or Asset or Maintained

• Number/Activity Association

The Runtime rule will be explained using asset number CAB004. Meter

OMCAB004-01 is defined and attached to the asset CAB004 (refer Meter

definition explained before). Schedule CAB004_CM is defined for the asset

CAB004 as shown in the next screen shot:


The interval defined for the meter OMCAB004-01 in schedule CAB004_CM is 300

KM. Usage rate defined for the meter is 20 KM

The last service information can be entered from the PM Schedule screen by

pressing on the “Last Service Info” button. The service start and end date is on

15th November , 2004 and the last service reading is 0 KM


No Meter Readings

No meter readings are entered. When running the PM engine from the “Forecast

Work Order” screen, the following work orders are forecasted :

The usage rate is 20 KM and the interval is 300 Km so the work orders are

scheduled at a gap of 15 days. The current meter reading date is 15th Nov,2004 so

the first work order is created on 30th Nov, 2004 and thereafter a work order is

created every 15th day.

Usage Rate Not Recalculated

Meter readings are now entered in the meter reading screen(Meters � Meter

Reading). The reading history shows the following :

The number of past readings is 5 whereas only two entries have been made so the usage rate is 20 (defined in the meter definition form). The system uses the Life To Date meter reading to calculate the Usage Rate.


The PM schedule forecasts the following schedules

The first Scheduled date is not 30th Nov, 2004 00:00:00 but it is 28th Nov, 2004

15:36:00. This is calculated using the following logic :

Current Meter reading = 67 Current Meter reading Date = 17-Nov-2004

For the PM Schedule,

Last Service Date = 15-Nov-2004 Target Meter Reading = 300

Due date for next service = Current Meter reading date + (target meter reading -

Current reading)/rate

= 17-Nov-2004 + (300 - 67)/20

= 17-Nov-2004 + 11.65 � 28-Nov-2004 15:36:00

The work orders after 28-Nov-2004 15:36:00 are spaced at an interval of 15 days

Usage Rate Recalculated

A few more meter readings are entered as shown below


“The number of past readings” defined for the meter is 5. The number of readings available for the meter OMCAB004-01 is more than the required number so the usage rate is recalculated using the last 4 meter readings. The readings seen in the above screen shot is Life to date reading. The actual readings entered is given below

DATE Actual Value Life to date

15th Nov, 2004 0 0

16th Nov, 2004 35 35

17th Nov, 2004 32 67

18th Nov, 2004 33 100

19th Nov, 2004 30 130

20th Nov, 2004 25 155

The usage rate is calculated as the total of the meter readings value changes,

divided by the total of the meter reading date intervals

= (Total of meter Reading value changes)/ (Total of reading date intervals) = (155-35)/(20th Nov- 16th Nov) = 120/ 4 � 30

The first date is calculated using the logic :


For the PM Schedule, Usage Rate = 30

Last Service Date = 15-Nov-2004 Target Meter Reading = 300



= 20-Nov-2004 + (300 - 155)/30

= 20-Nov-2004 + 4.833 � 24-Nov-2004 20:00:00

The work orders after 20-Nov-2004 20:00:00 are spaced at an interval of 10 days

(interval/usage rate � 300/30). Now when the PM engine is run, the following

work orders are forecasted


Work Order Completion – Change in Last service Information

A work order is created for asset CAB004 for activity cab maintenance. The

scheduled start date is 20-Nov-2004 00:00:00 and completion date is 21-Nov-2004

00:00:00. The work order was completed and the actual start and end dates of the

work orders are the same as the scheduled dates. While completing the work order ,

a meter reading of 179 was entered. The last service information of the CAB004-

cab maintenance is shown below :

One more reading is entered on the 22nd November ,2004. the meter readings

history is shown in the table below :

DATE Actual Value Life to date

15th Nov, 2004 0 0

16th Nov, 2004 35 35

17th Nov, 2004 32 67

18th Nov, 2004 33 100

19th Nov, 2004 30 130

20th Nov, 2004 25 155

21st Nov, 2004 24 179

22nd Nov, 2004 21 200

The usage rate now recalculates to 25 ( (200-100)/4 �25). When the work orders

are forecasted, the following schedule is proposed


The logic behind this :


Usage Rate = 25

For the PM Schedule, Last Service Date = 20-Nov-2004

Target Meter Reading = 479 (last service reading of 179 +interval of 300)



= 22-Nov-2004 + (479 - 200)/25

= 22-Nov-2004 + 11.16 � 03-Dec-2004 03:50:24

The work orders after 03-Dec-2004 03:50:24 are spaced at an interval of 12 days

(interval/usage rate � 300/25)

Meter Reading Reset

The meter OMCAB001-04 is reset to zero on 24th Nov, 2004 00:00:00. The value

before Reset was 200. The forecasted orders are shown below :


The usage rate remains at 25 and the logic of calculation remains the same as

shown under work order completion except that now the last meter reading is on

24th Nov, 2004 (for the work order completion calculation it was 22nd Nov, 2004)

so the first work order is suggested on 05th Dec, 2004 03:50:24.

Disabled meter readings are not considered by the PM schedule.

“Schedule Based On”

PM Schedule CAB005_CM will be used to understand the functionality of the

“schedule based on” option. The screenshot of the schedule definition is posted

below:

The schedule, CAB005_CM, is based on Runtime Rules and has two meters

OMCAB005-01 and OMCAB005-02 attached to it. The usage rate for meter

OMCAB005-01 is 25 KM /day and the interval defined for this meter is 100 KM.

The second meter OMCAB005-02 has a usage rate of 50 KMs and an interval of

250 KM.

Common information about meter OMCAB005-01 and OMCAB005-02 :

Number of past reading is 3. Last service start and end date is 30-Nov-2004 and the

last service reading is Zero.


With a start date of 30-Nov-2004 and a cutoff date of 01st Jan, 2005, the work

orders created for meters independently are shown below.

OMCAB005-01

1 04th Dec, 2004

2 08th Dec, 2004

3 12th Dec, 2004

4 16th Dec, 2004

5 20th Dec, 2004

6 24th Dec, 2004

7 28h Dec, 2004

For OMCAB005-01, the work order will be scheduled every fourth day (interval = 100, usage rate =25) and for meter OMCAB005-02, work orders will be scheduled on every fifth day (interval =250, usage rate =50). When the “Schedule Based on” is set to “First Due Date”, then the due date is set to the due date of the first due date of all the rules. The work orders forecasted for CAB005_CM for the First due date option is shown below :

When the schedule based on is the “Last Due date” , then the due date is set to

the last due date of all rules. The scheduled work orders for schedule CAB005_CM

is shown in the next screenshot

OMCAB005-02

1 05h Dec, 2004

2 10th Dec, 2004

3 15th Dec, 2004

4 20th Dec, 2004

5 25th Dec, 2004

6 30th Dec, 2004


List Dates

The list dates provides users the flexibility to define a PM schedule by listing all the

specific due dates on which the work orders should occur, instead of defining rules

in the PM schedule. The PM engine then generates work orders on these list dates.

List dates and day/runtime interval are mutually exclusive.

PM Schedule CAB003_CM is defined for asset CAB003. The Schedule type is List

dates and under the “List Dates” tab , the dates on which the work orders are

required are listed out.

Generate Preventive Maintenance Work Orders program

In the previous simulations, the “Forecast Work order” form was used to forecast

and implement the work orders. The advantage in the “Forecast Work order” form

is the possibility of viewing the scheduled orders before implementing them.

Another way to create work orders using the PM schedule is to launch the

“Generate Preventive Maintenance Work Orders” concurrent program (

Navigation : Preventive Maintenance � Generate Work orders). This program

considers only the Default PM schedule for generating the work orders and does

not consider any other PM schedule.

The mandatory parameter passed to this program is the cutoff date. Area, asset

Category, item type (Asset or Rebuildable), maintained group and Maintained

number are other filters that could be passed here.


After the “Generate Preventive Maintenance Work Orders” concurrent request

completes, the “WIP Mass Load” program is launched to generate the work orders

forecast by the “Generate Preventive Maintenance Work Orders” request.

The work orders generated for the Asset CAB003 is shown below :

SUPPRESSION

Other Activities can be suppressed with the current Activity in the scheduling

definition. You can enter suppression activities for a Maintained Number/Activity

combination.

To illustrate this functionality, asset CAB006 and activities “Cab maintenance” and

“Cab Engine Overhaul” is used. Here the simulation set is “Cab_Simulation” and

the “Default” check box is not marked. The schedule definitions are shown below :


Schedule CAB006_CS is defined for the CAB006- Cab maintenance combination.

The Day interval defined for this schedule is 5 days.

Schedule CAB006_CEO_CS is defined for the CAB006-Cab Engine Overhaul

combination. The Day interval defined for this schedule is 4 days.


CASE I : No Suppression defined

When no suppression is defined, the work orders forecasted for the asset CAB006

are :

Cab maintenance Activity

Schedule Start Date

1 06-DEC-2004

2 11-DEC-2004

3 16-DEC-2004

4 21-DEC-2004

5 26-DEC-2004

CASE II: Suppression Defined

Suppression is defined to suppress “Cab Engine Overhaul” Activity by “Cab

maintenance” activity (Navigation : Preventive Maintenance �Suppression)

When the forecast Work order is run , the following work orders are forecasted:

Cab Engine Overhaul

Activity

Schedule Start Date

1 05-DEC-2004

2 09-DEC-2004

3 13-DEC-2004

4 17-DEC-2004

5 21-DEC-2004

6 25-DEC-2004

7 29-DEC-2004

Cab Engine Overhaul Activity

Schedule Start Date

1 05-DEC-2004

2 10-DEC-2004

3 15-DEC-2004

4 20-DEC-2004

5 25-DEC-2004

6 30-DEC-2004

Cab maintenance Activity

Schedule Start Date

1 06-DEC-2004

2 11-DEC-2004

3 16-DEC-2004

4 21-DEC-2004

5 26-DEC-2004


The second work order forecasted under the “Cab Engine Overhaul” activity is on

10th Dec, 2004 and not on 9th December. This is because when a parent activity

suppresses a child activity, it means that the child activity will be performed when

the parent activity is done, i.e., the “cab Maintenance” activity performed on the

cab also includes “Cab engine Overhaul” activity.

Keeping the above in mind, the “Cab Engine Overhaul” activity is done on the 05th

Dec, 2004 but a “Cab Maintenance” activity is done on 6th Dec, 2004 which also

includes the “Cab Engine Overhaul” activity. The next work order for “Cab Engine

Overhaul” is scheduled 4 days from 06th Dec, 2004 , i.e., 10th Dec, 2004. The same

logic holds good for the other work orders forecasted under the “cab Engine

Overhaul” activity.

Tolerance In Days

“Tolerance In Days” is mentioned in the scheduling window to define the

minimum interval in days that suggested Work Orders’ dates are spaced from each

other.

The tolerance considers suppression.

CASE III: Suppression defined in Case II and a tolerance of 2 days set in CAB006_ CS schedule and null tolerance set in CAB006_CEO_CS schedule

When the work orders are forecasted, the suggested dates is the same as in Case II

CASE IV : Suppression defined as in Case II and a tolerance of null days set in CAB006_ CS schedule and 2 days tolerance set in CAB006_CEO_CS schedule

The work orders forecasted for this case is shown below


Work orders forecasted for “Cab Maintenance” activity are

06 DEC-2004

11-DEC-2004

16-DEC-2004

21-DEC-2004

26-DEC-2004

Work order forecasted for “Cab Engine Overhaul” activity is

30-DEC-2004

No other work order is forecasted for “Cab Engine Overhaul” activity as work

orders exist for the parent activity ,“Cab Maintenance”

The CAB006_CS and the CAB006_CEO_CS schedules were set as default and the

“Generate Preventive Maintenance Work Orders” concurrent request was

submitted. The log file generated by the request is provided in Appendix A

PREVENTIVE MAINTENANCE TEMPLATE

The previous schedules were created individually using the “Preventive

Maintenance (Schedule Definition)” window. The other way to define schedule is

to use the “Preventive Maintenance (Template definition)” window. A PM

Template is a schedule, defined for a Maintained Group (Asset Group or

Rebuildable Item)/Activity association. When the PM template functionality is

used, a new PM Schedule is automatically created for a newly created Maintained

Number (asset or rebuildable) for the Maintained Group. All PM Template

attributes are copied over to the PM Schedule for the Instance.

The steps used to create the PM template are the same as mentioned under the PM

schedule definition.

CONCLUSION

This paper covers the setup and functionality of preventive maintenance using a

hypothetical business scenario and test cases. The work orders were forecasted or

created after ensuring that no work orders exist in the system for the asset-activity

combination for the forecasted period.


APPENDIX A: LOG FILE CREATED BY THE “GENERATE PREVENTIVE

MAINTENACE WORK ORDER” CONCURRENT REQUEST

Parameters passed to “Generate Preventive Maintenance Work Orders” � Cut off

date : 31-Dec-2004, "Item Type" : Asset and "Maintained Number" : CAB006. Log

file generated is posted below:

+---------------------------------------------------------------------------+

Oracle Enterprise Asset Management: Version : 11.5.0 - Development

Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.

EAMPMSDU module: Generate Preventive Maintenance Work Orders

+---------------------------------------------------------------------------+

Current system time is 04-DEC-2004 09:36:44

+---------------------------------------------------------------------------+

**Starts**04-DEC-2004 09:36:45

**Ends**04-DEC-2004 09:36:50

Start of log messages from FND_FILE

+---------------------------------------------------------------------------+

Starting my log at Sat Dec 04 09:36:48 MST 2004

select msn.inventory_item_id, msn.serial_number

from mtl_serial_numbers msn, mtl_system_items msi

where msn.current_organization_id = msi.organization_id

and msn.inventory_item_id = msi.inventory_item_id

and msi.organization_id = ? and msi.eam_item_type = 1 and

msn.current_status != 4

and msn.maintainable_flag = 'Y' and msn.serial_number = ?

found a serial ...

&&&&&&&&&&&&&&&&&&&&&&&&&&&&

Initializing PMSchedule ...

&&&&&&&&&&&&&&&&&&&&&&&&&&&&

* The last service start and end dates are: 2004-12-01 00:00:00.0, 2004-12-

01 00:00:00.0

ruleType == PMConstants.DAY_INTERVAL_RULE

---- putting in the node: pm with id: 542---

&&&&&&&&&&&&&&&&&&&&&&&&&&&&

Initializing PMSchedule ...


* The last service start and end dates are: 2004-12-01 00:00:00.0, 2004-12-

01 00:00:00.0

ruleType == PMConstants.DAY_INTERVAL_RULE

---- putting in the node: pm with id: 463---

--- This PM's parentPM's Suggestions: ---

* The Day interval is: 5.0

************************

* The dueDate is :2004-12-06 00:00:00.0


************************

* The dueDate is :2004-12-11 00:00:00.0


************************

* The dueDate is :2004-12-16 00:00:00.0


************************

* The dueDate is :2004-12-21 00:00:00.0


************************

* The dueDate is :2004-12-26 00:00:00.0


************************

* The dueDate is :2004-12-31 00:00:00.0

******** PM Schedule Details ******************

PM: 463 association ID : 2636

leadTime : 0.0 reschedulingPoint : 1

nonScheduled : falseDay Interval Rule: Every [5.0]

********** Work Order Suggestions for PM 463**********

associationID: 2636

Create new work order

The timestamp is: 2004-12-06 00:00:00.0

associationID: 2636


The timestamp is: 2004-12-11 00:00:00.0


associationID: 2636


The timestamp is: 2004-12-16 00:00:00.0

associationID: 2636


The timestamp is: 2004-12-21 00:00:00.0

associationID: 2636


The timestamp is: 2004-12-26 00:00:00.0

--- This PM's parentPM's Suggestions: ---

associationID: 2636


The timestamp is: 2004-12-06 00:00:00.0

associationID: 2636


The timestamp is: 2004-12-11 00:00:00.0

associationID: 2636


The timestamp is: 2004-12-16 00:00:00.0

associationID: 2636


The timestamp is: 2004-12-21 00:00:00.0

associationID: 2636


The timestamp is: 2004-12-26 00:00:00.0

--------------------------


************************


* The dueDate is :2004-12-05 00:00:00.0


************************

* The dueDate is :2004-12-10 00:00:00.0


************************

* The dueDate is :2004-12-15 00:00:00.0


************************

* The dueDate is :2004-12-20 00:00:00.0


************************

* The dueDate is :2004-12-25 00:00:00.0


************************

* The dueDate is :2004-12-30 00:00:00.0


************************

* The dueDate is :2005-01-03 00:00:00.0

******** PM Schedule Details ******************

PM: 542 association ID : 2635

leadTime : 0.0 reschedulingPoint : 1

nonScheduled : false Day Interval Rule: Every [4.0]

********** Work Order Suggestions for PM 542**********

PARENT's suggestion...

associationID: 2635


The timestamp is: 2004-12-06 00:00:00.0


associationID: 2635


The timestamp is: 2004-12-11 00:00:00.0



associationID: 2635


The timestamp is: 2004-12-16 00:00:00.0


associationID: 2635


The timestamp is: 2004-12-21 00:00:00.0


associationID: 2635


The timestamp is: 2004-12-26 00:00:00.0

associationID: 2635


The timestamp is: 2004-12-30 00:00:00.0

Begin to try to reschedule existing work orders for PM 463

End of trying to reschedule existing work orders for PM 463

Begin to try to reschedule existing work orders for PM 542

End of trying to reschedule existing work orders for PM 542

+---------------------------------------------------------------------------+

End of log messages from FND_FILE

+---------------------------------------------------------------------------+

Executing request completion options...

Printing output file.

Request ID : 2540122

Number of copies : 0

Printer : noprint

Finished executing request completion options.

+---------------------------------------------------------------------------+

Concurrent request completed successfully

Current system time is 04-DEC-2004 09:36:50

+---------------------------------------------------------------------------+

Enterprise Asset Management (eAM) – Preventive Maintenance December 2005 Author: Arockiaraj Irudayasamy, Karthikeyan Balasubramaniam Co-Author : Vinay Srinath Contributing Authors: N/A Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200 www.oracle.com Oracle Corporation provides the software that powers the Internet. Oracle is a registered trademark of Oracle Corporation. Various product and service names referenced herein may be trademarks of Oracle Corporation. All other product and service names mentioned may be trademarks of their respective owners. Copyright © 2002 Oracle Corporation All rights reserved.

preventive maintenance wp

Documents