Meters in Eam - Webcast

ATTENTION AUDIO Options
Option 1: Voice Streaming Audio Broadcast
Option 2: Teleconference (Dial In)
No need to dial in on a telephone

Questions can be asked in the WebEx Chat panel
Details
Requires telephone to dial in

Questions can be asked over the phone or in the
WebEx Chat
Details
Conference ID: Complete your ID here
International dial in: +1-706-758-7972
US Free call: 1-866-627-3315
List with national toll free numbers is available
in Doc ID: 1148600.1
View anytime during the conference using
Communicate > Teleconference > Join
Teleconference from your WebEx menu
Upcoming: How to Use Meters In Enterprise Asses Management

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |
Upcoming Advisor Webcast Schedule
Check out Note ID : 740966.1

Select your Product Area
E-Business Suite Manufacturing
Scan through the list of Current Topics
Register for the session(s) of your interest
Upcoming: How to Use Meters In Enterprise Asses Management

Safe Harbor Statement

The following is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracles products remains at the sole discretion of Oracle.
Oracle Advisor Webcast

How to Use Meters In Enterprise Asset
Management
Zahoor Ahmed
Senior Principal Technical Support Engineer
October 16, 2014
Objectives
Understand what meters are
Consider setups required
Look at some example uses
Brief look at tables/apis
Agenda
1
Introduction
Basic Setups
Some examples of using Meters
Tables/APIs used for meters
Q&A
INTRODUCTION
What are meters?
Meters are defined and associated with asset numbers to measure the assets or
rebuildable items usage.
Example : odometer, counter.
Meters are used in Preventative Maintenance Scheduling to schedule and

generate work orders.
Meter Readings are entered at Work Order Completion
Meter Readings can be mandatory or non-mandatory at this stage
Meter Readings are mandatory for work orders generated by PM Scheduling.
SETUPS 1
The following setups are required to use Meters:
Create an asset
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.
Create the meter
Associate the meter to the asset(s)
Now define the PM Schedules which will generate the work orders for the
designated activities based on the meter rules.
SETUPS 2
Lets now look at the setups in more detail before exploring some examples:
We have an asset DTF3000. Here is an activity :
10
SETUPS 3
Here is the Maintenance BOM created for the activity :
11
SETUPS 4
Here is the Maintenance Routing created for the activity :
12
SETUPS 5
Now lets look at how this activity is associated to an asset :
13
SETUPS 6
There are 2 ways to create a meter :
Create a Meter Template and then instantiate them when creating an
asset
Create a Meter manually and then associate it to one or more assets.
Meter Readings can be mandatory or non-mandatory at this stage
Meter Readings are mandatory for work orders generated by PM Scheduling.
Lets now look at how the meter is created :
14
SETUPS 7
Here is the meter used for the previous activity and asset : (other values not
shown : type = absolute ; UOM = Ml ; value change= ascending ; initial
reading = 120000 ; rate per day = 200 ; no of past readings = 600)
15
SETUPS 8
Explanations of Key fields :
Meter Type :
- Absolute = (actual readings used and value field enabled when entering
readings).
- Change incremental changes are measured. Change field enabled for
meter readings).
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.
16
SETUPS 9
Value Change: Controls direction allowed for meter readings:
- Ascending = Readings can only go up (e.g car odometer)
- Descending = Readings can only go down (e.g a liquid dispenser which
starts full and then the liquid starts to get used and is reduced)
- Fluctuating = Can go up or down (e.g a temperature gauge)
Used in Scheduling Checkbox : Meter used in PM Scheduling
Required Checkbox : meter readings are required when the work order is
completed for the associated asset.
Initial Reading : Automatically used as the first meter reading entered.
17
SETUPS 10
Rate : Works in conjunction with no of past readings to calculate daily
meter usage estimates based on historical readings.
No of Past Readings : Dictates the number of readings prior the schedular
should go to calculate the usage rate.
Primary Failure Meter (PFM) : This is the default meter used for Failure
Analysis (optional). Failure Analysis not a part of this webcast separate
topic.
The PFM is used to calculate meter based MTBF and MTTR
MTBF = Mean Time before Failure
MTTR = Mean Time to Repair
18
SETUPS 11
The other method of creating meters is to use a meter template.
Steps are :
- Create meter template
- Assign it to an asset group.
- Create a new asset for that asset group
- A new meter instance will be automatically created for that asset
number.
- Ideal for fleet management for example.
19
SETUPS 12
20
SETUPS 13
Next - the PM Schedule is created for the asset/activity/meter
21
SETUPS 14
This shows the last service date information:
22
SETUPS 15
Explanation of some Key fields in PM Setup for Meters:
Base Meter: Enter meter and interval. PM Engine then ignores actual and
scheduled dates for calculations.
Base Interval : Time or Meter Reading : Example : perform the activity
every 90 days (time) or every 10000 miles (meter reading).
Cycle = Complete round of maintenance activities. Can specify number of
intervals in the cycle.
Last Service Reading : Optional. Will update when meter reading is
entered on work order completion.
23
SETUPS: 16
Before I look at some examples I will highlight some points about usage
rate and no of past readings :
Lets say you specify no of past readings on meter definition as 10 and
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, system will use the historical readings to calculate the usage
rate which is stored on the PM Schedule.
24
SETUPS 17
- A Tip : If you do not want 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 :
Formula Used By Workbench To Forecast Work Orders (Doc ID 812166.1)
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.
25
EXAMPLES OF METER USAGE : 1

Case 1: 1 meter - n assets :
Test_Meter1 Assigned to Asset numbers ASSET1, ASSET2, ... Etc.
Readings are done on the meter.
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.
26

CASE 2: 1 meter - 1 asset :
TEST_METER_1 assigned to asset number , Asset1.
TEST_METER_2 assigned to asset number , Asset2, etc
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.
27

CASE 3 : User wants to create a PM definition so that work orders are not
suggested until the meter reading (say 100) has not been exceeded.
Define a Meter with Rate per Day = 1 and Number of Past Reading = 9999
99
Create a PM with Meter rules for every 100 hours as the Interval
In the Scheduling Options: Use: Base Meter or Base Date to suggest Next
Service: Start Date
EAM Parameters: Uncheck the flag 'Implement From Horizon Start Date'.
Run the Forecasted Work from the Maintenance Workbench.
28

CASE 4 : User wants to generate work order based on last service reading.
Setups are as follows:
Meter = Test_meter1. This was defined as base meter on PM Schedule
with initial interval of 1
Usage Rate = 5.249378
Base Interval = 100
Last Service Reading = 900 ; Date = 29-SEP-2010 13:20:35
On 10-Oct-2010 14:20:36, meter reading of 1000 entered.
However : no work order was generated.
29

Solution for case 4:
Base Meter is mentioned with base meter reading as 1, so suggestions are forecasted from base meter reading always - irrespective of last service reading.
Base Meter reading=1, so PM forecasts work orders at following due readings as interval is 100: 101, 201, 301, 401, 501, 601, 701, 801, 901, 1001 and so on
Usage rate=5.249378
Latest Meter reading=1000, latest meter reading date: 10-Oct-2010 14:20:36
User forecasted in horizon: 29-Sep-2010 to 30-Oct-2010
Lets calculate when due reading 901 falls on:
Left days = (Latest Meter reading-due reading)/usage rate
= (1000-901)/5.249378
= 99/5.249378
= 18.859377
Suggestion date = Latest Meter reading date +left days
= 10-Oct-2010 14:20:36 + 18.859377
= 29-OCT-10
Solution : Remove base meter. Just use meter rule in PM with scheduling option : 'Actual Start Date/Actual End Date/Schedule Start Date/Schedule End Date.
30

CASE 5 : User wants to measure fuel usage for 1000 buses.
Possible solution:
You can create a meter for each bus. 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, value type ascending and direction of Fluctuating.
31

CASE 5 :
32

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 multiple rules region, you can specify the value FIRST or LAST to deal
with due dates (first or last due date of all rules).
33

Case 6 : Same activity with 2 rules:
Rule 1: odometer 5000 KM
Rule2 : 240 Hours
Scheduling Based on : first due date
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.
After a period, the PM runs again.
If at 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.
34

CASE 7 :Trucks of a specific Make and Model need to be scheduled for an oil change every 30 days, or every 1000
miles.
Date Rule defined:
- Last Service Start/End : Date December 26, 2001
- Interval In Days: 30
Meter Rule defined:
- Last Service Reading 3000
- Interval 1000
- Latest Meter Reading 3100 (found within meter reading history)
- Latest Meter Reading Date January 1, 2002 (this can be found via meter reading history)
- Usage Rate 25 miles per day
35

CASE 7 : 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 if you selected last due.
36

CASE 8 : 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 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.
37

CASE 9 : Multiple Activity Example:
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
38

Case 9:
39

Case 9:
40

CASE 9 : 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.
41

CASE 10 : Can meters be associated to Asset Routes?
NO there is an ER:
Enhancement Request Bug 13807136
42

CASE 11 : The client wants to create a rule in a mass meter entry or when
completing the Work order, for example, to prevent the users from
entering more than 1000 KM/day or more than 24hours/day
This is not possible. There is an ER for this:
Bug 6402052 : ONDEMAND:EAM HOUR METER ALLOWS YOU ENTER
READINGS WHICH SET USAGE RATE > 24 HOUR
43

Entering meter Readings
44
APIS :
Import Meter Reading is an interface process used to import meter
readings into eAM.
In addition, the CREATE_METER_READING API creates meter readings and
resets existing meter readings.
Execution Steps for importing meter readings :
1. Populate the interface table with the import information.
The Meter Reading Import process reads information within the
EAM_METER_READING_INTERFACE table, then imports that information
into the eAM production table.
2. Launch the Meter Reading Import process.
45
Relevant tables for investigating meters and rules :
Select counter_id from CSI_COUNTERS_V where counter_name like'&meter_name';--provide EAM meter name stored as counters in CSI table
Select * from csi_counter_readings where
COUNTER_ID = 'enter counter id here';
select * from EAM_PM_SCHEDULINGS
where name like 'enter problematic PM schedule name'
SELECT * FROM EAM_PM_SCHEDULING_RULES
WHERE PM_SCHEDULE_ID = 'Substitute schedule id here'
46
Summary
What we covered today

Explained what meters are
Looked at basic setups
Looked at some examples
Looked at APIs/Tables
47
To ask a question on the phone

line, select *1 on your phone.
Q&A
To ask a question online, use the

Chat area at the top.
Your question will be read aloud in
the order received.
Question can also be asked on the
My Oracle Support Communities
Top Articles and Community Links

EAM Information Center [ID 1411394.2].
Enterprise Asset Management (EAM) Advisor
Webcast Calendar/Archive [ID 1167439.1].
Oracle Advisor Webcast Schedule [ID
740966.1].
Continue the Discussion on the Enterprise
Asset Management My Oracle Support
Community.
What advisor webcast topics do YOU want to
see presented?
Webcast Survey After Todays Session.
THANK YOU
50
Accessing My Oracle Support Community

1.
Via My Oracle Support -> Community Tab
2.
Directly https://communities.oracle.com
Where Can I Get The Slides From This Session?

1. PDF link from Doc ID 740966.1 (within 48 hours)
2. RAC/Scalability Community >Content Tab > Documents (within 24 hours)
Session Related Community Links

The following thread will have a copy
of the presentation and can be used
for additional questions or discussions
on this topic.
https://community.oracle.com/thread/
3570481
Oracle Advisor Webcast Program
Locating Current Schedule & Archived Recordings

From Note ID : 740966.1 drill
down to your area of interest
Select your Product Area
Oracle Advisor Webcast Program
Locating Current Schedule & Archived Recordings For DB
Note:
Click column headings to sort
Hover on Webcast Title for more
information
Recordings available within 48
hours
Advisor Webcast Questions on a
webcast or ask questions via the
Questions? link
To ask a question on the phone

line, select *1 on your phone.
Q&A
To ask a question online, use the

Q&A area at the top.
Your question will be read aloud in
the order received.
Question can also be asked on the
My Oracle Support Communities
THANK YOU
58

Meters in Eam - Webcast

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Meters in Eam - Webcast

Enviado por

Direitos autorais:

Formatos disponíveis

ATTENTION AUDIO Options

Option 1: Voice Streaming Audio Broadcast

Option 2: Teleconference (Dial In)

No need to dial in on a telephone

Requires telephone to dial in

Upcoming: How to Use Meters In Enterprise Asses Management

Upcoming Advisor Webcast Schedule

Check out Note ID : 740966.1

Upcoming: How to Use Meters In Enterprise Asses Management

Safe Harbor Statement

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

Oracle Advisor Webcast

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

Some examples of using Meters

Tables/APIs used for meters

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

Meters are used in Preventative Maintenance Scheduling to schedule and

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

EXAMPLES OF METER USAGE : 1

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

EXAMPLES OF METER USAGE : 2

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

EXAMPLES OF METER USAGE : 3

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

EXAMPLES OF METER USAGE : 4

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

EXAMPLES OF METER USAGE : 5

Latest Meter reading=1000, latest meter reading date: 10-Oct-2010 14:20:36

User forecasted in horizon: 29-Sep-2010 to 30-Oct-2010

Lets calculate when due reading 901 falls on:

Left days = (Latest Meter reading-due reading)/usage rate

Suggestion date = Latest Meter reading date +left days

= 10-Oct-2010 14:20:36 + 18.859377

EXAMPLES OF METER USAGE : 6

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

EXAMPLES OF METER USAGE : 7

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

EXAMPLES OF METER USAGE : 8

EXAMPLES OF METER USAGE : 9

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

EXAMPLES OF METER USAGE : 10

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

EXAMPLES OF METER USAGE : 11

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

EXAMPLES OF METER USAGE : 12

Copyright 2014 Oracle and/or its affiliates. All rights reserved. |

EXAMPLES OF METER USAGE : 13

Inspection every 100 hours of operation