Professional Documents
Culture Documents
Meters r12 PDF
Meters r12 PDF
Management
Using Meters in EAM
1. OVERVIEW .............................................................................................................................................................................................................................. 1
The objectives of this white paper are to provide an overview of what meters
are and how they are used in EAM. The paper will look at the setups required
and look at some examples of using meters. There will also be a brief
discussion of APIs and tables related to meters. The topics covered in the
paper are :
Meters are defined and associated with asset numbers to measure the assets
(or rebuildable items) usage.
Meter Readings are entered at Work Order Completion. Meter Readings can
be mandatory or non-mandatory at this stage. However, Meter Readings are
mandatory for work orders which are generated by PM Scheduling.
Create an asset
Create Activities: Meters are used to measure usage of an asset and the
main reason for doing this is to carry out maintenance work based on the
usage. Hence, one or more activities need to be defined for the work to
be done. BOMS and routings can also be created for the activity.
2
Now define the PM Schedules which will generate the work orders for the
designated activities based on the meter rules.
Lets now look at the setups in more detail before exploring some examples:
3.2 : Next - here is the Maintenance BOM created for the activity :
3
3.3 : Here is the Maintenance Routing created for the activity :
3.4 : Now lets look at how this activity is associated to an asset using the
Activity Association form :
4
3.5 : There are 2 ways to create a meter :
3.5.1 Lets now look at how the meter is created using the manual method :
Here is the meter used for the previous activity and asset : (not all the values
are shown in the screenshot they are as follows: type = absolute ; UOM =
Ml ; value change= ascending ; initial reading = 120000 ; rate per day = 200 ;
no of past readings = 600)
5
Explanations of Key fields used in defining meters :
Source Meter : For example when a parent asset meter is updated, it will
update the child asset meter readings also. Example : A truck meter is
updated. This updates the child transmission meter also.
Required Checkbox : meter readings are required when the work order is
completed for the associated asset.
Primary Failure Meter (PFM) : This is the default meter used for Failure
Analysis (optional). Failure Analysis not a part of this webcast separate topic.
6
3.5.2 The other method of creating meters is to use a meter template.
7
This shows the last service date information:
Before I look at some examples I will highlight some points about usage rate
and number of past readings :
Lets say you specify the number of past readings on the meter definition as
10 and the usage rate as 25 miles a day.
If there are insufficient readings in the system for the meter - (e.g 9 rather then
required 10), the system uses the usage rate/day (25 per day) in the
calculation.
Otherwise, the system will use the historical readings to calculate the usage
rate which is stored on the PM Schedule.
A Tip : If you do not want the system to calculate the usage rate but use the
one you have provided, then use a very high value for no of past readings - eg
999999. After 1000000 readings, the system will recalculate the usage rate.
The new usage rate will be seen on the PM Schedule and will be based on your
latest meter reading and historical readings.
If you want to know the formula used by the PM Engine to forecast work
orders when using meters, refer to the note below :
Another tip : Uncheck the flag 'Implement From Horizon Start Date if you
want the system to include past dates in the calculation and take into account
all potential work orders.
8
4 EXAMPLE USES OF METERS :
CASE 1 :
When entering a value in the Meter Reading , the value becomes the last
value reading for all the assigned asset numbers.
Thus, entering a value for ASSET1 when completing a work order for
ASSET1 , will be seen as the last reading value for ASSET2.
CASE 2:
1 meter - 1 asset :
In this case when you record a reading for Asset1, it will the last reading
value for the TEST_METER_1, thus not interfering with TEST_METER_2.
Each meter will have its own values and last value.
Hence, if you need to track readings by individual asset number, you must
assign the asset number its own specific meter. For example if you want
to track the service of 2 cars using the odometer, you will need a separate
meter for each car you cannot use one meter for both cars.
9
CASE 3
CASE 4 :
The User wants to generate work orders based on last service reading. Setups
are as follows:
Meter = Test_meter1.
This was defined as base meter on PM Schedule with :
Initial Interval = 1
Usage Rate = 5.249378
Base Interval = 100
Last Service Reading = 900 ; Date = 29-SEP-2010 13:20:35
Usage rate=5.249378
Latest Meter reading=1000, latest meter reading date: 10-Oct-2010 14:20:36
10
Lets calculate when due reading 901 falls on:
= (1000-901)/5.249378
= 99/5.249378
= 18.859377
Solution : Remove the base meter. Just use a meter rule in PM with
scheduling option : Actual Start Date/Actual End Date/Schedule Start
Date/Schedule End Date.
CASE 5 :
Possible solution:
You can create a meter for each bus. There is no need to create any work
order just enter meter readings for each bus periodically and then write your
own reports to analyse the data.
Use a change meter, with value type ascending and direction of Fluctuating.
11
CASE 6 :
Can I assign 2 meters or more for 1 asset? For example , one is an odometer
and the other is an hour meter to measure engine hours. Whichever comes
first, the WO should be triggered. (WO to be created at 5000 KM or 2000
hours whichever comes first).
This is possible because you can associate multiple meters to an asset number
AND a PM schedule can have multiple meter rules.
As an aside a PM schedule can have BOTH a date rule and a meter rule and
the one which comes first will trigger the work order.
In the multiple rules region, you can specify the value FIRST or LAST (for
scheduling based on field) to deal with due dates (first or last due date of all
rules).
Lets say the current meter is 4900 and will get to 5000 in 2 days :
PM will generate WOs only for rule 1 as it is due in 2 days. If you suggest a
period longer or shorter, it is not relevant, only rule 1 will apply. WO for
Rule 1 will be generated before rule 2 reaches its target.
12
After a period, the PM runs again.
If at the next run, the 240 Hours rule comes first this time, then only rule 2
will be used for the chosen period.
Conversely, you can choose Last Due Date in the Scheduling Based On
region. In this case, even if rule 1 reaches its due reading, the service is
not scheduled until rule 2 has also reached its due reading.
CASE 7 :
Trucks of a specific Make and Model need to be scheduled for an oil change
every 30 days, or every 1000 miles.
If the Meter Rule is taken into account, the next due date is February 6, 2002
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:
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 if you selected last due.
13
CASE 8 :
Use of 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 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.
CASE 9 :
14
The above screenshot shows the PM schedule for this 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
15
CASE 10 :
CASE 11:
CASE 12:
This is done using the Meter Readings page in Maintenance Super User:
16
5 APIs AND TABLES USED FOR METERS :
In addition, the
CREATE_METER_READING API
creates meter readings and resets
existing meter readings.
SELECT * FROM
EAM_PM_SCHEDULING_RULES
WHERE PM_SCHEDULE_ID =
'Substitute schedule id here'
18
Using Meters in EAM
Nov 104
Author: Zar Ahmed
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
19