Preventive Maintenance Setup

eAM can generate Work Orders automatically based on meter readings, runtime and/or
calendar days. An example of meter-based preventive maintenance is your car's oil
changes. Most car manufacturers recommend that you change your engine oil every
3,000 miles or six months, whichever comes first.

To set up the above scenario, you would first define your car's odometer as a meter.
Next, you would associate that meter to an asset (your car), using the Asset Meter
Association window. After you have associated the meter to the asset, you can
associate the Maintenance Activity (oil change) that should occur, based on the meters
you have defined. This is done via Preventive Maintenance Scheduling.

This section includes the following topics:

 Project and Task Setup

 Defining Meter Templates
 Defining Meters
 Defining Set Names
 Defining a Preventive Maintenance Template
 Entering Preventive Maintenance Schedule Definitions

Project and Task Setup

Work Orders can associate with a Project, Task or Seiban number, at the time of
implementing PM suggestions to work orders. The Forecast Work Order window is
customizable.

Defining Meter Templates

There are two ways to create meters. You can create them within the Meter window, or
create them first using the Meter Template window, and then next instantiating them
when defining an asset. If you create Meters using the Meter window (See: Defining
Meters), associate that meter definition with individual Asset Numbers manually. If you
utilize the Meter Template definition functionality, you can associate that Meter
Template with Asset Groups. After the association is created, when an Asset Number
(Asset Numbers or Serialized Rebuilds) is created within that Asset Group (Asset Group
or Rebuildable Item), the system automatically creates a new instance of the meter,
associated with the specific Asset Number. This enables you to streamline your meter
setup. However, the meters are not created retroactively; it applies to Asset Numbers
created after the Meter Template was created.

Defining Meter Templates

To define Meter Templates

1. Navigate to the Meter Template window.

Meter Template

2. Enter a unique meter template Name.

3. Enter the template's Description.
4. Select the meter Type.

When entering meter readings for the current meter, if the meter is an Absolute
type, the Value field is enabled. If the meter is a Change type, the Change field
is enabled.

5. Select a unit of measure (UOM). After the meter is created, this field is disabled.
6. Select whether the meter readings is Ascending, Descending, or Fluctuating. A
fluctuating meter reading is one that can go up and down, for example, a
temperature gauge. As production units pass through meters, meter readings
increment. Another example of an ascending meter is a car odometer. Some
liquid dispensers start full and record decreasing readings as material is used.

Note: If the meter is fluctuating, it is not used in Preventive Maintenance

scheduling.

7. Optionally enter an Initial Reading. This is automatically used as the first meter
reading entered, or each new instance of the meter that is created and
associated with an Asset Number (or Serialized Rebuild) via the Meter Template.
8. If you select the Used in Scheduling check box, the meter is used in Preventive
Maintenance Scheduling. If there are any scheduling rules associated with this
meter, you cannot clear this check box. If this is a fluctuating meter, this check
 box is disabled. If the Used in Scheduling check box is selected, the Usage Rate
(per day) and Number of Past Reading fields are mandatory.
9. Optionally select the Required check box to indicate whether readings for the
meter are required during work order completion, regardless of whether a work
order was generated from Preventive Maintenance or if it was created manually.

You can select or clear this check mark at any time; it impacts only future meter
readings. However, if the meter is a Primary Failure Meter for any current
asset/meter association, you cannot clear the check box.

10.Enter a usage Rate (per day). This field works in conjunction with the Number of
Past Readings field to provide daily meter usage estimates, based on historical
readings. It supplies the system benchmark data that is used to set the
occurrence of scheduled PMs. Rate per day is referred to in the absence of a
sufficient value in the Number of Past Readings field.

This field is mandatory if you have selected the Used in Scheduling check box.

11.Enter a value for the Number of Past Readings. This value designates how many
readings prior the scheduler should go to for calculating the usage rate. If there
is an insufficient number of readings (for example four, instead of the required
five), the system continues the calculation based on the usage Rate per day.

This field is mandatory if you have selected the Used in Scheduling check box.

Note: If you enter a value of 1, the system perpetually calculates at the usage
Rate per day.

12.Select the meter template effective dates. If left blank, the meter is effective all
of the time. You can disable a meter effective on a specific date by selecting a To
date.
13.Save your work.

To associate Meter Templates with Asset Groups

If you utilize the Meter Template definition functionality (See: Defining Meter

Templates), you can associate that Meter Template with Asset Groups, within the same
Meter Template window. After you create the association, when a new Asset Number
(Asset Numbers or Rebuildable Serial Numbers) is created within that Asset Group
(Asset Group or Rebuildable Item) a new instance of the corresponding meter is
automatically created. This enables you to streamline your Meter setup.

1. Select an Item Type. Valid values are Capital or Rebuildable.

 2. Select an Asset Group. If you previously selected Capital, Asset Groups are
available for selection. If you previously selected Rebuildable, Rebuildable Items
are available for selection.
3. Save your work. After saving, every Asset Number defined as part of the current
Asset Group automatically associates with the Meter Template; you do not need
to create this association manually.

Defining Meters

Alternatively, you can create Meters using the Meter window. Manually associate the
meter definition with individual Asset Numbers. If you utilize the Meter Template
definition functionality, you can associate that Meter Template with Asset Groups
(See: Defining Meter Templates).

Defining Meters

To define a meter within the Meter window

1. Navigate to the Meter window.

Meter

2. Enter a unique meter Name.

3. Enter a Description for this meter.
4. Optionally select a Source Meter from the list of values. As the Source Meter's
readings are updated, the associated target meter (current meter) is updated
automatically. Companies can associate a Source Meter to an Asset
Number/Meter association. The Source Meter reading subsequently feeds
corresponding meters that are associated with assets within the Meter Hierarchy.
 For example, some companies must track units, using a Meter, to a parent asset
(truck). These units should then trickle down to all children components of that
parent asset (transmission, tires, belts). Each child component has different
Meters to track the units and history on the individual components. If the
transmission is replaced, the Rebuild Replacement process enables you to
remove the replaced transmission from the meter hierarchy and add the new
transmission to the hierarchy. From that point, meter readings logged to the
truck should also update the transmission’s child meter with those units. Any
time a reading is logged to the truck, it will update the transmission child Meter
with those units.

5. Select the meter Type.

When entering meter readings for the current meter, if the meter is an Absolute
type, the Value field is enabled. If the meter is a Change type, the Change field
is enabled. A Change type meter is used to measure incremental changes in
meter readings. The incremental amount is added to the current meter reading.
After meter readings are entered for a Change Meter, you cannot change the
type to Absolute.

6. Select a unit of measure (UOM), associated with this meter. After the meter is
created, this field is disabled.
7. Select whether the meter readings are Ascending, Descending, or Fluctuating. A
fluctuating meter reading is one that can go up and down, for example, a
temperature gauge. As production units pass through meters, meter readings
increment. Another example of an ascending meter is a car odometer. Some
liquid dispensers start full and record decreasing readings as material is used.

Note: Fluctuating meters are not used in Preventive Maintenance scheduling.

After the meter is created, this field is disabled.

8. Enter an Initial Reading. This is automatically used as the first meter reading
entered, or each new instance of the meter that is created and associated to a
Asset Number via the Meter Template.
9. If you select the Used in Scheduling check box, the meter is used in Preventive
Maintenance Scheduling. If there are any scheduling rules associated with this
meter, you cannot clear this check box. If this is a fluctuating meter, this check
box is disabled. If the Used in Scheduling check box is selected, the Usage Rate
(per day) and Use Past Reading fields become mandatory.
10.Optionally select the Required check box to indicate whether readings for the
meter are required during work order completion, regardless of whether a work
order was generated from Preventive Maintenance or if it was created manually.
 You can select or clear this check mark at any time; it impacts only future meter
readings. However, if the meter is a Primary Failure Meter for any current
asset/meter association, you cannot clear the check box.

11.Enter a usage Rate (per day). This field works in conjunction with the Number of
Past Readings field to provide daily meter usage estimates, based on historical
readings. It supplies the system benchmark data that is used to set the
occurrence of scheduled PMs. Rate per day is referred to in the absence of a
sufficient value in the Number of Past Readings field.

This field is mandatory if you have selected the Used in Scheduling check box.

12.Enter a value for the Number of Past Readings. This value designates how many
readings prior the scheduler should go to for calculating the usage rate. If there
is an insufficient number of readings (for example four, instead of the required
five), the system continues the calculation based on the usage Rate per day
entered.

This field is mandatory if you have selected the Used in Scheduling check box.

Note: If you enter a value of 1, the system perpetually calculates at the usage
Rate per day.

13.Select the meter Effective Dates. If left blank, the meter is effective all of the
time, after it is created. If you select a future date, the meter is disabled until
that date. You can disable a meter effective on a specific date by selecting a To
date.
14.Save your work.

To associate meters with capital assets and/or serialized rebuilds

Meter Association creates the relationship between the meter definition and the capital
Asset Number and/or Serialized Rebuild.

1. Select an Item Type of Capital, if you are going to associate the current meter
with an Asset Number. Select Rebuildable if you are associating the current
meter with a Serialized Rebuild.
2. Select an Asset Number (or Serialized Rebuild). The Asset Group (or Rebuildable
Item) defaults.
3. Optionally select a Primary Failure Meter to indicate the default meter that is
used for failure analysis. This meter's readings are used to calculate meter-based
MTBF and MTTR. See: Failure Analysis Overview.

You can select a Primary Failure Meter for any meter with the Required check
mark selected. Only one meter can be selected at a time, for an asset.
 4. Save your work.

Defining Set Names

A PM schedule for an Activity and an Asset Number or Asset Group must uniquely
belong to a Set Name. Multiple PM Schedules for the same Asset Number or Asset
Group and Activity combination are created across Sets. However, out of those PM
Schedules, one can be identified as the Default and used for generating Work Orders.
Other PM Schedules in other Sets can be used for simulation purposes. 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 Schedule's Set Name. Before assigning
a Set Name to a PM schedule, you need to define Set Names within the Set Name
Definition window. If you do not want to create Set Names, you can assign PM
schedules to set, MAIN; it already exists.

PM schedules might contain assets that transferred from one organization to another.
The asset's destination organization can update and use the PM schedules that are
assigned to a global PM set. However, you can only view, within the destination
organization, PM schedules that are assigned to the asset's originating organization's
local PM sets.

Defining Set Names

To define Set Names

1. Navigate to the Set Name window.

Set Name
2. Enter the Set Name.
3. Optionally enter 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 Schedule's Set
Name. If you leave this field blank, the current Set Name does not expire.
4. Optionally enter a Description for this Set Name.
5. Optionally select the Global check box to indicate that the set is visible globally.
If this check box is clear, the set is confined to the current organization.

Note: You can change this setting from Global to local, if the set is not used in
an PM schedules of another organization's assets.

6. Optionally choose Templates to add, change, delete, or view Preventive

Maintenance Schedule Templates, associated with the current Set Name (See:
Preventive Maintenance Schedule Templates).
7. Optionally choose Schedules to create PM Schedule Definitions, associated with
the current Set Name (See: Defining a Preventive Maintenance Template, Oracle
Enterprise Asset Management User's Guide).
8. Optionally choose Set Default to identify all schedules within this set as Default.
PM Schedules identified as Default automatically generates Work Orders, by the
PM Scheduler process. PM schedules that are not identified as Default can
generate Work Order suggestions, by the PM Scheduler process. The generated
suggestions cannot be converted into Work Orders. You can create an unlimited
number of Set Names within this window.
9. Save your work.
Defining a Preventive Maintenance Template

An Activity and Asset Number combination can be associated with Runtime, Day
Interval Rules, or a list of dates, defining when an Activity should be scheduled for an
Asset, Serialized and Non-Serialized Rebuildables, or an Asset Route. Day Interval rules
and List of Dates rules are supported for Non-Serialized Rebuildables and Asset Routes.
The Preventive Maintenance (PM) Scheduler process creates suggested Work Order
dates based on these rules. A planner can then view these forecasted Work Orders, and
generate them as necessary.

There are two ways to create PM schedule definitions for Rebuildable Serial Numbers
and Assets. You can create them individually within the Preventive Maintenance
Schedules window (See: Entering Preventive Maintenance Schedule Definitions, Oracle
Enterprise Asset Management User's Guide), or streamline the process of creating them
using a PM Template. A PM Template is a schedule, defined for an Asset Group (Asset
Group or Rebuildable Item)/Activity association. If you utilize the PM Template
functionality, a new PM Schedule is automatically created for a newly created Asset
Number (asset or rebuildable) for the Asset Group. All PM Template attributes are
copied over to the PM Schedule for the Instance. You can optionally modify the values
of the PM Instances created.

Before a PM Template is created, the following prerequisites must exist:

 Meter Template Definition (See: Defining Meter Templates, Oracle Enterprise

Asset Management User's Guide)

A Meter Template definition is required if the PM Template is based on Runtime

Rule

 Activity Definition (See: Defining Activities, Oracle Enterprise Asset Management

User's Guide)
 Meter Template Association (See: Associating Meter Templates with Asset
Groups, Oracle Enterprise Asset Management User's Guide )

A Meter Template Association is required if the PM Template is based on

Runtime Rules.

 Activity Association Template (See: Activity Association Templates, Oracle

Enterprise Asset Management User's Guide)

Creating Preventive Maintenance (PM) Templates

To create a PM Template
1. Navigate to the Find Preventive Maintenance Schedules window. This window
enables you to enter information to narrow your search for query mode.

Select Yes in the Generate Next WO field if you want the PM Scheduler to be
able to create the next work order only if the previous work order has been
completed for this work order completion date.

To define a new PM Template, select the New button.

Preventive Maintenance (Template Definition)

2. Enter a PM Template name in the Schedule Name field.

3. Enter a Set Name. A PM schedule for an Activity and Asset Group must uniquely
belong to a Set Name (See: Defining Set Names, Oracle Enterprise Asset
Management User's Guide). 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. Before assigning a Set Name to a PM schedule, define
Set Names within the Set Name Definition window. If you do not want to create
Set Names, you can assign PM schedules to set, MAIN; it already exists.
 PM schedules might contain assets that transferred from one organization to
another. The asset's destination organization can update and use the PM
schedules that are assigned to a global PM set. However, you can only view,
within the destination organization, PM schedules that are assigned to the asset's
originating organization's local PM sets. You can copy these PM schedules to a
global, local set or to your organization's local set.

4. Select an Asset Type. Valid values are Capital and Rebuildable Inventory. If
Capital is selected, the Asset Group fields refer to the Asset Group. If you select
Rebuildable Inventory, the Asset Group fields refer to the Rebuildable Item.
5. Select an Asset Group.
6. Select a Schedule Type. Valid values are Rule Based and List Dates. If you select
Rule Based, the Day Interval Rules and Runtime Rules tabs are enabled to enter
information. If you select List Dates, you can define information within the List
Dates tab.
7. The Effective dates default from the current Activity association, if they exist.
Optionally select or update the Effective From and Effective To dates.
8. Optionally enter a Lead Time In Days.

Lead time in a Preventive Maintenance Schedule is different than lead time

associated with Work Order creation. The Preventive Maintenance process
suggests Work Orders to be created or scheduled, starting from the last service
day of the Asset to the cutoff day you specified while running the process. If a
Lead Time In Days is specified, the Preventive Maintenance process predicts
work for those extra days beyond the cutoff date. This provides the maintenance
department advanced visibility for maintenance work that is typically predicted in
the next planning process. The maintenance department can prepare for such
work in the current planning period.

9. Optionally select a Work Order Status that best fits your business process. When
Preventive Maintenance Work Orders are generated, (See: Generating Work
Orders, Oracle Enterprise Asset Management User's Guide ) they are created with
this specified status. You can optionally update this status within the
Maintenance Workbench (See: Using the Maintenance Workbench, Oracle
Enterprise Asset Management User's Guide).
10.Optionally select Yes in the Generate Next WO field if you want to enable the
scheduler to create the next work order only if the previous work order has been
completed for the work order completion date.
11.Optionally select the Default check box to indicate that the current PM schedule
definition generates Work Orders. If this check box is not selected, Work Order
suggestions will not generate. You can have only one Default PM for an Asset
Item/Activity combination.
12.Optionally select the Automatic Instantiation check box. If this check box is
selected, a new instance of the current PM schedule template is created for each
new Asset (Asset Number or Rebuildable Serial Number).
13.Optionally select the Reschedule Manual Work Orders check box. If this check
box is selected, non-firm, unreleased manual work orders are considered during
PM scheduling.
14.If the Run To Failure check box is selected, the Preventive Maintenance
Scheduler does not automatically schedule Asset Numbers within this Asset
Group and Activity association, although you can create manual Work Orders.
This is relevant for Asset Numbers that cost more to maintain than the Asset
Number itself. You might also check this box for forecasting and budgeting
reasons. For example, your asset is a conveyor belt. It is common in
maintenance environments to let this asset wear out completely before replacing
it. You estimated that the life of this asset is 18 months, and have set up a
schedule for a replacement Work Order every 18 months. In reality, you found
that the belts have ended up wearing out every 12 months, affecting your cost
budget.

You may select this check box and clear it later. For example, you might
associate an Asset Number to an Activity, but maybe you cannot currently
maintain or schedule this Asset Number. You may have future plans to maintain
this Asset Number.

If this check box is selected, PMs created as a copy of this PM Template

generate Work Orders for the corresponding asset in the Maintenance
Workbench (See: Using the Maintenance Workbench, Oracle Enterprise Asset
Management User's Guide).

15.In the Scheduling Options region, indicate how the PM Scheduler process
calculates Work Order dates. The Use field works in conjunction with the to
suggest Next Service field. The date field indicates the Last Service date
o Actual Start Date to Start Date : The PM Scheduler process uses the Last
Service Actual Start Date, and calculates scheduled start dates. This is a
forward scheduling method.
o Actual Start Date to End Date: The PM Scheduler process uses the Last
Service Actual Start Date, and calculates the scheduled end dates. This is
a backward scheduling method.
o Actual End Date to Start Date: The PM Scheduler process uses the Last
Service Actual End Date, and calculates the scheduled start dates. This is
a forward scheduling method.
o Actual End Date to End Date: The PM Scheduler process uses the Last
Service Actual End Date, and schedules the scheduled end dates. This is a
backward scheduling method.
 o Scheduled Start Date to Start Date: The PM Scheduler process uses the
Last Service Scheduled Start Date, and calculates scheduled start dates.
This is a forward scheduling method.
o Scheduled Start Date to End Date : The PM Scheduler process uses the
Last Service Scheduled Start Date, and calculates the scheduled end
dates. This is a backward scheduling method.
o Scheduled End Date to Start Date: The PM Scheduler process uses the
Last Service Scheduled End Date, and calculates the scheduled start
dates. This is a forward scheduling method.
o Scheduled End Date to End Date: The PM Scheduler process uses the Last
Service Scheduled End Date, and schedules the scheduled end dates. This
is a backward scheduling method.
o Base Date: You must enter a date as the basis for the PM calculation. As
your intervals change, you might want to update the Base Date so that
your PM work orders are generated at your choice intervals. It is
recommended that you change the Base Date to the Last Service Date if
your scheduling interval changes, to ensure that the new scheduling is
impacted only from that point and forward. Actual and scheduled work
order dates are not considered when you use the Base Date or Base Meter
options.
o Base Meter: You must enter a Meter, as well as the initial interval. The PM
engine uses that initial reading as the anchor for its calculation. Actual and
scheduled work order dates are not considered when you use the Base
Date or Base Meter options.
16.In the Multiple Rules region, indicate how the predicted due dates are
determined for multiple rules.
o First: The due date is set to the first due date of all rules.
o Last: The due date is set to the last due date of all rules.

For example, below is a Runtime Rule that includes two meters, Meter1 and
Meter2.

Schedule Based On Example

Interval Effective From Effective To Meter
100 0 10,000 Meter1
50 0 2,500 Meter2

If you specify First Due Date in the Scheduling Based On region of the PM
Template, between the two meters, the first meter that hits the due reading
triggers the service. In this case, if Meter1's reading reaches the interval of 100
first, the service happens before Meter2's reading reaches its interval of 50.
Conversely, you can choose Last Due Date in the Scheduling Based On region. In
 this case, even if Meter1 reaches its due reading, the service is not scheduled
until Meter2 has also reached its due reading.

This region is disabled if the current PM schedule definition's Scheduling Type

field is populated with List Dates.

17.In the Activity region, select one or multiple activities. Activities associated with
asset groups are eligible for defining a Schedule Template.

A Maintenance Planner can create a single PM schedule for multiple activities on

an Asset Template. You can list multiple activities to perform on an asset that
share a common base interval of either a date, meter, or both. Each
maintenance activity on the schedule generates work orders, based on a multiple
of the base interval occurring. The group of maintenance activities on one PM
schedule represents a cycle of activities. Base Interval refers to the minimum
of a space of time (such as 90 days), or meter reading (such as 7,500 miles)
between when PM activities included in one PM schedule should be performed. It
can be considered a common denominator among the multiple activities included
in one PM Schedule that share a common base interval. A cycle is a complete
round of maintenance activities performed on an asset that share a common
base interval of a meter or time period, or both, or a multiple of the shared
intervals.

After the cycle of activities completes, the cycle restarts. For example, you can
define a PM schedule for two activities that have a common Base Interval of
7,500 miles. The first activity is an oil change, and is scheduled every 7,500
miles. The second activity, a tune-up, is scheduled for every fourth interval or
30,000 miles. The work order for the oil change generates on each occurrence of
the 7,500 mile interval and the work order for the tune-up generates on the
fourth interval occurrence.

When an asset transfers to another organization, the schedule that is associated

with the local PM Set is viewable within the new organization. For example, the
PM Set Name, Local, is created in organization, EM1. A PM schedule is defined in
EM1 for Asset Number, #1554877, and is associated with Local (Set Name).
Asset Number #1554877 is transferred to another eAM-enabled organization,
EM2. A planner in this new organization (EM2) can view the PM schedule that is
associated with the Local PM set. However, it is view-only; it cannot be updated.
The associated Activity appears in blue, to indicate that the activity definition has
not yet been assigned to EM2. In this scenario, to use the PM schedule, the
planner must either assign the schedule's Activity to the current organization,
EM2, or update the schedule's PM Set Name from Local to a global set or a local
PM set that was defined in EM2.
 Note: You can define an unlimited number of activities, however, it is
recommended that you keep it simple.

18.Optionally indicate the Interval Multiple of the Base Interval. This field works
with the Repeat in Cycle field to determine how many intervals for an activity to
repeat.
19.Optionally select the Repeat in Cycle value to determine if the activity interval
repeats in the cycle. If you select Yes, the Interval Multiple field determines how
many times the activity interval repeats. If you select No, the activity is
scheduled once for each cycle.
20.Optionally enter a Tolerance In Days to indicate a minimum interval in days that
suggested Work Orders' dates are spaced from each other.
21.Within the Date Rules tab, optionally enter Effective From and To dates to
specify the rule's expiration.
22.Enter a Base Interval In Days. For example, if you enter the number three, a
Work Order suggestion is created every three days.

You can optionally create variable Date Rules. For example, you would like Work
Order suggestions created every three days in January, and every four days in
February. The window below illustrates this example:

23.Within the Meter Rules tab, optionally select a Meter Name to indicate that
Preventive Maintenance scheduling is based on a Meter Rule. If you have
previously set up a Date Rule, you can base the scheduling on a Runtime Rule,
as well. Meter Templates associated with this Asset Group (See: Associating
Meter Templates with Asset Groups, Oracle Enterprise Asset Management User's
Guide), and with the Used in Scheduling check box selected in the meter
template definition, are available.

For example, trucks of a specific Make and Model need to be scheduled for an oil
change every 30 days, or every 1000 miles.

Date Rule
Field Value
Last Service Start/End Date December 26, 2001
Interval In Days 30
Meter Rule
Field Value
Last 3000
Service
Reading
Interval 1000
 Latest 3100 (found within meter reading history)
Meter
Reading
Latest January 1, 2002 (this can be found via meter reading history)
Meter
Reading
Date
Usage Rate 25 miles per day (calculated, based on Linear Regression's Least Square
formula. In a least-squares model, the best-fitting line for the observed data
is calculated by minimizing the sum of the squares of the vertical
deviations from each data point to the line. For example, if a point lies on
the fitted line exactly, then its vertical deviation is zero.)

If the Meter Rule is taken into account, the next due date is February 6, 2002
(January 1 2002 + [(3000 + 1000 - 3100)/25 = January 1, 2002] +36 days), and
every 40 days after that. This is calculated as the interval (1000 miles) divided by
the usage rate (25 miles per day).

The PM Scheduler process compares the above suggested dates from the
runtime interval rule, to those of the date rule: Base Date of December 26, 2001
+ every 30 days.

The Work Orders ultimately created by the PM Scheduler process are those of
the earliest or latest dates, depending on how the Schedule Based On region is
populated. If you selected First Due, the earliest suggestion is used for Work
Order creation. The opposite is also true.

24.The Interval and UOM fields work together. For example, for every 2000 miles,
this Asset Number needs an oil change.

The UOM defaults from the Meter Template definition of the current Meter
Template.

You can optionally create multiple Runtime Rules. For example, from zero to
10,000 miles, you would like your asset serviced every 3,000 miles. From 10,000
to 50,000 miles, you would like your asset serviced every 2,000 miles.

25.Optionally enter the Last Service Reading in the Last Service Information
window. This field is also automatically updated with the meter reading
information recorded at Work Order completion (See: Work Order
Completion, Oracle Enterprise Asset Management User's Guide ).

Note: The Preventive Maintenance Scheduler (See: Generating Work

Orders, Oracle Enterprise Asset Management User's Guide ) automatically
 calculates the meter usage rate, based on historical data, which is then used to
predict the next meter due date. Refer to the example below.

26.If you populated List Dates within the Schedule Type field, select the List Dates
tab to define the specific due dates that Work Orders should transpire.

For example, you want asset, Car1, serviced on May 1 and November 1 every
year for the next three years. In this case, you would create a List Dates type
schedule definition, and list all the due dates within this tab. The PM Scheduler
process creates suggested Work Order dates on those specified dates.

27.Save your work.

Entering Preventive Maintenance Schedule Definitions

Schedule definitions are implemented to create scheduled Work Orders, based on Day
Interval Rules, and/or Runtime Rules. Schedules can also be based on a list of specific
dates by using List Date rules. List Date rule based PM schedules cannot have Runtime
or Day interval rules. Runtime or Day Interval Rule based PM schedules cannot have
List Date rules. You can create a Preventive Maintenance Schedule Definition on an
Asset Group (Non-serialized Rebuildable)/Activity combination, Asset Number/Activity
combination, or an Asset Route/Activity combination.

If a meter is entered in a runtime interval rule, the following prerequisites must exist
before creating a Preventive Maintenance Schedule:

 Meter Definition (See: Defining Meters, Oracle Enterprise Asset Management

User's Guide)

A Meter definition is required if the PM schedule is based on Runtime Rules.

 Activity Definition (See: Defining Activities, Oracle Enterprise Asset Management

User's Guide)
 Meter/Asset Association (See: Associating Meters with Asset Numbers, Oracle
Enterprise Asset Management User's Guide)

A Meter/Asset Association is required if the PM schedule is based on Runtime

Rules.

 Asset Group (Non-Serialized Rebuildable) or Asset Number/Activity Association

(See: Associating Asset Numbers with Activities, Oracle Enterprise Asset
Management User's Guide)

Defining Preventive Maintenance (PM) Schedules

To define a Preventive Maintenance schedule for an asset number

1. Navigate to the Find Preventive Maintenance Schedules window. This window

enables you to enter information to narrow your search for query mode.

Select Yes in the Generate Next WO field if you want the PM Scheduler to be
able to create the next work order only if the previous work order has been
completed for this work order completion date.

To define a new schedule, click the New button.

Preventive Maintenance (Schedule Definition)

2. Enter a Schedule Name.

Important: If your PM schedule requires more than one activity and if the
activities use different cycles, we recommend that you create separate PM
schedules.

3. Enter a Set Name. A PM schedule for an Activity and an Asset Number or Asset
Group must uniquely belong to a Set Name (See: Defining Set Names, Oracle
Enterprise Asset Management User's Guide). 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. Before assigning a Set Name to a PM
schedule, define Set Names within the Set Name Definition window. If you do
not want to create Set Names, you can assign PM schedules to set, MAIN; it
already exists.

PM schedules might contain assets that transferred from one organization to

another. The asset's destination organization can update and use the PM
schedules that are assigned to a global PM set. However, you can only view,
within the destination organization, PM schedules that are assigned to the asset's
 originating organization's local PM sets. You can copy these PM schedules to a
global, local set or to your organization's local set.

4. Select an Asset Type. Valid values are Capital and Rebuildable Inventory. If
Capital is selected, the Asset Number and Asset Group fields refer to the Asset
Number and Asset Group, respectively. If Rebuildable Inventory is selected, the
Asset Number and Asset Group fields refer to the Rebuildable Serial Number and
Rebuildable Item, respectively. If a Non-Serialized Rebuildable Item is entered in
the Asset Group field, the Asset Number field is not required.
5. Select an Asset Number. Assets that are maintainable and associated with
Activities are available. The Asset Group field populates with the Asset Group
associated with the current Asset Number. If you wish to define a PM Schedule
for a Non-serialized Rebuildable, enter the Asset Group; the Asset Number field
does not apply.

For assets that transferred from one organization to another, PM schedules that
are defined for assets within their originating organizations are also visible within
their destination organizations.

6. Select a Schedule Type. Valid values are Rule Based and List Dates. If you select
Rule Based, the Day Interval Rules and Runtime Rules tabs are enabled to enter
information. If you select List Dates, you can define information within the List
Dates tab.
7. The Effective dates default from the current Asset Activity association, if they
exist. Optionally select or update the Effective From and Effective To dates.
8. Optionally enter a Lead Time In Days.

Lead time in a Preventive Maintenance Schedule is different than lead time

associated with Work Order creation. Lead time within a Preventive Maintenance
Schedule covers the time between the end date of the first execution of the
Preventive Maintenance Schedule process, and the start date (system date) of
the second execution of the Preventive Maintenance Schedule process. For
example, a department executes the Preventive Maintenance Scheduler process
every two months; the end date of each Preventive Maintenance Scheduler
process is the end of every other month. However, due to circumstance, the
meter data is not ready until the middle of the month. Therefore, the Preventive
Maintenance Scheduler process starts in the middle of the month, instead of at
the beginning, creating a lapse between the first and second Preventive
Maintenance Scheduler executions. Lead time is used to cover this lapse.

9. Optionally select Yes in the Generate Next WO field if you want to enable the
scheduler to create the next work order only if the previous work order has been
completed for the work order completion date.
10.Optionally select a Work Order Status that best fits your business process. When
Preventive Maintenance Work Orders are generated, (See: Generating Work
Orders, Oracle Enterprise Asset Management User's Guide ) they are created with
this specified status. You can optionally specify a different status for each PM
schedule. You can also update this status, using the Maintenance Workbench
(See: Using the Maintenance Workbench, Oracle Enterprise Asset Management
User's Guide).
11.Optionally select the Default checkbox to indicate that the current PM schedule
definition generates Work Orders. If this checkbox is not selected, Work Order
suggestions will not generate. You can have only one Default PM for an Asset
Item/Activity combination.
12.Optionally select the Reschedule Manual Work Orders checkbox. If this checkbox
is selected, non-firm, unreleased manual Work Orders are considered during PM
scheduling.
13.If the Run To Failure checkbox is selected, the Preventive Maintenance Scheduler
does not automatically schedule this Asset Number and Activity association,
although you can create manual Work Orders. This is relevant for Asset Numbers
that cost more to maintain than the Asset Number itself. You might also check
this box for forecasting and budgeting reasons. For example, your asset is a
conveyor belt. It is common in maintenance environments to let this asset wear
out completely before replacing it. You estimated that the life of this asset is 18
months, and have set up a schedule for a replacement Work Order every 18
months. In reality, you found that the belts have worn out every 12 months,
affecting your cost budget.

You can select this checkbox and clear it later. For example, you might associate
a non-maintainable asset to an activity, but maybe you cannot currently maintain
or schedule this asset. You might have future plans to maintain this Asset
Number.

If this check box is selected, the work orders for this asset do not appear in the
Maintenance Workbench at the time of PM Scheduling (See: Using the
Maintenance Workbench, Oracle Enterprise Asset Management User's Guide ).

14.For new PM schedule definitions, the default value for the Reviewer is based on
the user login information, and the Review Date field defaults to the current
system date.

If you are updating a PM schedule definition, the Reviewer field indicates the last
reviewer of the PM Schedule, and the Review Date field indicates the date on
which the last review occurred. When updating the schedule definition, the
Reviewed Date can be changed.
15.In the Scheduling Options region, indicate how the PM Scheduler process
calculates work order dates.

The Use field works in conjunction with the to suggest Next Service field. The

date field indicates the Last Service date.

o Actual Start to Start Date: The PM Scheduler process uses the Last Service
Actual Start Date, and calculates scheduled start dates. This is a forward
scheduling method.
o Actual Start Date to End Date: The PM Scheduler process uses the Last
Service Actual Start Date, and calculates the scheduled end dates. This is
a backward scheduling method.
o Actual End Date to Start Date: The PM Scheduler process uses the Last
Service Actual End Date, and calculates the scheduled start dates. This is
a forward scheduling method.
o Actual End Date to End Date: The PM Scheduler process uses the Last
Service Actual End Date, and schedules the scheduled end dates. This is a
backward scheduling method.
o Scheduled Start Date to Start Date : The PM Scheduler process uses the
Last Service Scheduled Start Date, and calculates scheduled start dates.
This is a forward scheduling method.
o Scheduled Start Date to End Date : The PM Scheduler process uses the
Last Service Scheduled Start Date, and calculates the scheduled end
dates. This is a backward scheduling method.
o Scheduled End Date to Start Date: The PM Scheduler process uses the
Last Service Scheduled End Date, and calculates the scheduled start
dates. This is a forward scheduling method.
o Scheduled End Date to End Date: The PM Scheduler process uses the Last
Service Scheduled End Date, and schedules the scheduled end dates. This
is a backward scheduling method.
o Base Date: You must enter a date as the basis for the PM calculation. As
your intervals change, you might want to update the Base Date so that
your PM work orders are generated at your choice intervals. It is
recommended that you change the Base Date to the Last Service Date if
your scheduling interval changes, to ensure that the new scheduling is
impacted only from that point and forward. Actual and scheduled work
order dates are not considered when you use the Base Date or Base Meter
options.
o Base Meter: You must enter a Meter, as well as the initial interval. The PM
engine uses that initial reading as the anchor for its calculation. Actual and
scheduled work order dates are not considered when you use the Base
Date or Base Meter options.
16.In the For Multiple Rules region, indicate how the predicted due dates are
determined for multiple rules.
 o First: The due date is set to the first due date of all rules.
o Last: The due date is set to the last due date of all rules.

For example, below is a Runtime Rule that includes two meters, Meter1 and
Meter2.

Schedule Based On Example

Interval Effective From Effective To Meter
100 0 10,000 Meter1
50 0 2,500 Meter2

If you specify First in the Multiple Rules region of the PM schedule definition,
between the two meters, the first meter that hits the due reading triggers the
service. In this case, if Meter1's reading reaches the interval of 100 first, the
service happens before Meter2's reading reaches its interval of 50. Conversely,
you can choose Last in the Multiple Rules region. In this case, even if Meter1
reaches its due reading, the service is not scheduled until Meter2 has also
reached its due reading.

This region is disabled if the current PM schedule definition's Scheduling Type

field is populated with List Dates.

17.Optionally enter a value for the Intervals Per Cycle field. This field represents
the number of base intervals that comprise the complete cycle. For example, 12
monthly intervals would comprise a 1-year cycle, and four 7,500 miles base
intervals would comprise a 30,000-mile cycle.

The system automatically updates these fields:

o Current Cycle: The current execution cycle of a Preventive Maintenance

cycle for an asset. This field is automatically updated by the system when
preventive maintenance work orders generated out of a given schedule
are completed.
o Current Interval Cycle: The current execution interval within a current
running cycle. This field is automatically updated by the system when
preventive maintenance work orders generated out of a given schedule
are completed. It is advisable not to change the current cycle and current
interval count after initial definition, unless really required to do so. These
fields can be disabled for edit by users through function based menu
exclusions.
18.Within the Activity region, select one or multiple Activities. Activities associated
with Asset Numbers or Non-serialized Rebuilds are eligible for scheduling.
 A Maintenance Planner can create a single PM schedule for multiple activities on
an Asset. You can list multiple activities to perform on an asset that share a
common base interval of either a date, meter, or both. Each maintenance activity
on the schedule generates work orders, based on a multiple of the base interval
occurring. The group of maintenance activities on one PM schedule represents a
cycle of activities. After the cycle of activities completes, the cycle restarts. For
example, you can define a PM schedule for two activities that have a common
Base Interval of 7,500 miles. The first activity is an oil change, and is scheduled
every 7,500 miles. The second activity, a tune-up, is scheduled for every fourth
interval or 30,000 miles. The work order for the oil change generates on each
occurrence of the 7,500 mile interval and the work order for the tune-up
generates on the fourth interval occurrence.

When an asset transfers to another organization, the schedule that is associated

with the local PM Set is viewable within the new organization. For example, the
PM Set Name, Local, is created in organization, EM1. A PM schedule is defined in
EM1 for Asset Number, #1554877, and is associated with Local (Set Name).
Asset Number #1554877 is transferred to another eAM-enabled organization,
EM2. A planner in this new organization (EM2) can view the PM schedule that is
associated with the Local PM set. However, it is view-only; it cannot be updated.
The associated Activity appears in blue, to indicate that the activity definition has
not yet been assigned to EM2. In this scenario, to use the PM schedule, the
planner must either assign the schedule's Activity to the current organization,
EM2, or update the schedule's PM Set Name from Local to a global set or a local
PM set that was defined in EM2.

Note: You can define an unlimited number of activities, however, it is

recommended that you keep it simple.

19.Optionally indicate the Interval Multiple of the Base Interval. This field works
with the Repeat in Cycle field to determine how many intervals for an activity to
repeat.
20.Optionally select the Repeat in Cycle value to determine if the activity interval
repeats in the cycle. If you select Yes, the Interval Multiple field determines how
many times the activity interval repeats. If you select No, the Activity is
scheduled once for each cycle.
21.Optionally enter a Tolerance In Days to indicate a minimum interval in days that
suggested Work Orders' dates are spaced from each other.
22.Optionally choose Last Service Info to enter the last service information for the
current Asset Number/Activity association. Enter Last Service start and end
dates. These dates are used by the Preventive Maintenance Scheduler as a
starting point for calculating the next due date for a suggested Work Order. After
the Preventive Maintenance Scheduler suggests a Work Order, and that Work
Order is completed, this date resets to the completion date. Last service
 information is always regarding the Asset Number/Activity association, and
independent of the association's PM schedule definition.

The Last Service Reading cannot be greater than the last meter (if the meter is
ascending), or less than the last meter reading (if the meter is descending).

Last Service Information

23.Within the Date Rules tab, optionally enter Effective From and To dates to
specify the rule's expiration. This tab is enabled if Rule Based is populated in the
Schedule Type field.
24.Enter a Base Interval In Days. For example, if you enter the number three, a
Work Order suggestion is created every three days.

You can optionally create variable Date Rules. For example, you would like Work
Order suggestions created every three days in January, and every four days in
February.

Date Rules Example

25.Optionally within the Meter Rules tab, select a Meter Name to indicate that
Preventive Maintenance scheduling is based on a Meter Rule. If you have
previously set up a Date Rule, you can base the scheduling on a Meter Rule, as
well. Meters associated with this Asset Number (See: Associating Meters with
Asset Numbers, Oracle Enterprise Asset Management User's Guide ), and with the
Used in Scheduling checkbox selected in the meter definition, are available.

For example, a Truck 01 Asset Number is scheduled for an oil change every 30
days, or every 1000 miles.

Date Rule
Field Value
Last Service Date December 26, 2001
Interval In Days 30
Meter Rule
 Field Value
Last Service 3000
Reading
Interval 1000
Last Service January 1, 2002 (this can be found via meter reading history)
Reading Date
Usage Rate 25 miles per day (calculated as the total of the meter readings value
changes, divided by the total of the meter reading date intervals)

If the Meter Rule is taken into account, the next due date is February 10, 2002
(January 1 2002 + 40 days), and every 40 days after that. This is calculated as
the interval (1000 miles) divided by the usage rate (25 miles per day).

The PM Scheduler process compares the above suggested dates from the meter
rule, to those of the date rule: Base Date of December 26, 2001 + every 30
days.

The Work Orders ultimately created by the PM Scheduler process are those of
the shortest interval and earliest dates: December 26, 2002 + every 30 days.

Note: Meter Rules are not applicable for Non-Serialized Rebuildables.

26.The Interval and UOM fields work together. For example, for every 2000 miles,
this Asset Number needs an oil change.

The UOM defaults from the meter definition of the current meter.

You can optionally create multiple Meter Rules. For example, from zero to 10,000
miles, you would like your asset serviced every 3,000 miles. From 10,000 to
50,000 miles, you would like your asset serviced every 2,000 miles.

27.You cannot enter the Last Service Reading. This field is automatically updated
with the meter reading information recorded at Work Order completion (See:
Work Order Completion, Oracle Enterprise Asset Management User's Guide ).

Note: The Preventive Maintenance Scheduler (See: Generating Work

Orders, Oracle Enterprise Asset Management User's Guide ) automatically
calculates the meter usage rate, based on historical data, which is then used to
predict the next meter due date. Refer to the example below.

28.If you populated List Dates within the Schedule Type field, select the List Dates
tab to define the specific due dates that Work Orders should transpire.
 For example, you want asset, Car1, serviced on May 1 and November 1 every
year for the next three years. In this case, you would create a List Dates type
schedule definition, and list all the due dates within this tab. The PM Scheduler
process creates suggested Work Order dates on those specified dates.

29.Save your work.

Multiple Activity PM Schedule Definition - Fixed Meter Example

Parameters for Conveyor PM Schedule

 Inspection every 100 hours of operation

 Minor PM for every 200 hours of operation
 Major PM for every 400 hours of operation
 Scheduling Option: Base Meter

The following are the steps you will perform:

1. Enter the meter name and define the scheduling starting point to the right of the
meter.

The system will define default values for the following:

o Intervals per Cycle

o Current Cycle
o Current Interval Count
2. Enter the required activities, taking the following into consideration:
o The Activity “Inspection” is scheduled after 100 hours of operation:
(Interval Multiple (1) x Base Interval (100)).
o The Activity “Minor PM” is scheduled after 200 hours of operation.
o The Activity “Major PM” is scheduled after 400 hours of operation.
o Repeat in Cycle determines if an activity can occur multiple times during a
cycle, in this example the Inspection can occur multiple times within the
cycle, the Minor PM will not be planned at the 400 hour interval.
3. Enter the meter name with a base interval of 100.
4. Save your work.
Analysis of Example

The program will update Current Cycle and Current Interval Count when PM work
orders are completed. For example at 210 hours of operation, two Inspection work
orders and one Minor PM work order have been generated and completed. The Current
Interval Count has been updated to (2). The Current Interval Count provides a count
within the Current Cycle, the Current Interval Count is updated to (1) with the start of
each new cycle.

The Current Cycle provides a count of the number of times a PM Set (Inspection, Minor
PM and Major PM) has been completed. In this example, the Current Cycle remains (1),
the Current Cycle will be updated to (2) with the completion of the PM Set and the start
of a new cycle.

When forecasting work orders for the next 30 days, note that the activity “Minor PM” is
not included in the forecast but the Activity “Inspection” is included, the “Repeat in
Cycle” controls if an activity will occur within a Cycle. For the activity “Inspection” the
Repeat in Cycle is “Yes”, for the activity “Minor PM” the Repeat in Cycle is “No”, the
“Minor PM” will be generated once per cycle.
To define a Preventive Maintenance schedule for an asset route

Preventive Maintenance Schedules can be defined based on Asset Routes. See: Setting
Up Asset Routes.

1. Navigate to the Preventive Maintenance Schedules window.

2. Select Asset from the Item Type list of values.
3. Select an Asset Route from the Asset Number list of values.
4. See: Preventive Maintenance Scheduling, Oracle Enterprise Asset Management
User's Guide, for instructions on the remaining fields.

Note: You can define Date Rules and List Dates for Asset Routes. You cannot
define Meter Rules.

To create a suppression activity

You can suppress other Activities with the current Activity in the scheduling definition.
You can enter suppression activities for an Asset Number/Activity combination.

For example, there are two activities associated with a Truck 01 asset: Oil Change (to
be performed every five months), and Major Service (to be performed every 12
months). A major service on a Truck 01 includes an Oil Change. Therefore, a
suppression definition needs to be defined; the Activity, Major Service, suppresses the
child activity, Oil Change.

1. From the Preventive Maintenance Schedules window, choose Suppression.

Suppression

2. Choose a Suppressed Activity. Activities associated with the Asset Numbers are
available.

Note: One Activity association can suppress multiple Activity associations. One

Activity association can be suppressed by one Activity association.

3. Optionally enter a Description for this suppression.

4. Save your work.

Note: Suppression is applicable to an Activity association and can also be

defined from the Activity Workbench and Suppression window.

Related Topics

Entering Meter Readings

Generating Work Orders