EAM Meters

  • View
    53

  • Download
    12

Embed Size (px)

DESCRIPTION

EAM_Meters.pdf

Text of EAM Meters

  • Oracle Enterprise Asset

    Management

    Using Meters in EAM

    An Oracle White Paper

    Nov 2014

  • Table of Contents

    1. OVERVIEW .............................................................................................................................................................................................................................. 1

    2. WHAT ARE METERS ? ............................................................................................................................................................................................................ 1

    3. BASIC SETUPS FOR METERS ................................................................................................................................................................................................ 3

    4. EXAMPLE USES OF METERS ................................................................................................................................................................................................. 7

    5. APIS AND TABLES USED FOR METERS .............................................................................................................................................................................17

  • 2

    1. OVERVIEW

    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 :

    What are meters? Basic Setups Some examples of using Meters Tables/APIs used for meters

    2. 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. However, Meter Readings are mandatory for work orders which are generated by PM Scheduling.

    3. BASIC SETUPS FOR METERS

    The following setups are required to use Meters:

    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.

    Create the meter

    Associate the meter to the asset(s)

  • 3

    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.1 We have an asset DTF3000. Here is an activity :

    3.2 : Next - here is the Maintenance BOM created for the activity :

  • 4

    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 :

  • 5

    3.5 : 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.

    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)

  • 6

    Explanations of Key fields used in defining meters :

    Meter Type : This can be either of the following:

    - Absolute = actual readings used and value field enabled when

    entering readings.

    - Change incremental changes are measured. Change field is

    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.

    Value Change: Controls the 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 = Readings can go up or down (e.g a temperature

    gauge)

    Used in Scheduling Checkbox : Meter is 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.

    Rate : Works in conjunction with the 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

  • 7

    3.5.2 The other method of creating meters is to use a meter template.

    The 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. This is ideal for fleet management for example.

    Next - the PM Schedule is created for the asset/activity/meter

  • 8

    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 :

    Formula Used By Workbench To Forecast Work Orders (Doc ID 812166.1)

    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.

  • 9

    4 EXAMPLE USES OF METERS :

    Now I will consider some example uses of Meters.

    CASE 1 :

    1 meter assigned to multiple assets :

    E.G : 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.

    CASE 2:

    1 meter - 1 asset :

    E.G : TEST_METER_1 is assigned to one asset number , Asset1.

    And TEST_METER_2 assigned to another asset number , Asset2.

    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.

  • 10

    CASE 3 User wants to create a PM definition so that work orders are not

    suggested until the meter reading (say 100) has 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. 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 = 10