To
associate meter templates with asset groups: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.
This section includes the following topics:
Work orders can be associated with a Project, Task or Seiban number at the time of implementing PM suggestions to work orders. The Forecast Work Order window can be configured.
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.
Navigate to the Meter Template window.
Enter a unique meter template Name.
Enter the template's Description.
Enter a Value or Change Reading value for new meter readings, depending on the meter type.
Note: If the meter is a Change type, the Value field indicates the difference between the last reading and the current reading. The Change value is used to calculate the Life To Date Reading, within the Latest tabbed region.
Optionally change the Date, if required.
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.
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.
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.
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.
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.
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.
Save your work.
To
associate meter templates with asset groups:If you use 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.
Select an Item Type.
Valid values are Capital or Rebuildable.
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.
Save your work.
After saving, each asset number defined as part of the current asset group is automatically associated with the meter template.
Reapplying a Meter Template
to an Asset Group:You can reapply a meter template to asset group after the asset has been created. Meter templates can be applied to an entire asset group or a range of asset numbers or serialized rebuildables.
Note: You can apply meter templates to only those assets to which a meter template has not been previously (applied) associated.
Navigate to the Reapply Asset Template form (Enterprise Asset Management > Assets > Reapply Asset Template).
Select values for the following required fields:
Asset Type: Select Capital or Rebuildable.
Asset Group: Select the asset group. You can apply the meter template to an entire asset group or to specific asset numbers within an asset group.
Template Type: Select Meter Template.
Optionally select values for these fields:
Asset Status
Meter Template: Select the meter template that you want to reapply to the asset.
Asset Number From: Enter the beginning asset number value if you want to apply the meter template to a range of asset numbers in the asset group.
Asset Number To: Enter the ending asset number value if you want to apply the meter template to a range of asset numbers in the asset group.
If you enter a value in the Asset Number From field but leave the Asset Number To field blank, the concurrent program will apply the meter template to a specific asset number.
Optionally select Yes in the View Only field if you do not want the system to apply the templates; a log is generated but the templates are not reapplied to the assets. The default value is No.
Click the OK button.
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).
Navigate to the Meter page.
Enter a unique meter Name.
Enter a Description for this meter.
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 child 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.
Select the meter Type of Absolute or Change.
Select a unit of measure (UOM), associated with this meter. After the meter is created, this field is disabled.
Select Ascending, Descending, or Fluctuating in the Value Change field.
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.
Enter an Initial Reading.
This value 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.
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.
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.
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.
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.
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.
Save your work.
To associate meters with capital assets or serialized rebuilds:Meter association creates the relationship between the meter definition and the capital asset number or Serialized Rebuild.
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.
Select an Asset Number (or Serialized Rebuild). The Asset Group (or Rebuildable Item) defaults.
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.
Save your work.
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.
Navigate to the Set Name window.
Enter the Set Name.
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.
Optionally enter a Description for this Set Name.
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.
Optionally choose Templates to add, change, delete, or view Preventive Maintenance Schedule Templates, associated with the current Set Name (See: Preventive Maintenance Schedule Templates).
Optionally choose Schedules to create PM Schedule Definitions, associated with the current Set Name (See: Defining a Preventive Maintenance Template).
Optionally choose Set Default to identify all schedules within this set as Default.
Default-identified PM schedules automatically generate work orders during the PM Scheduler process. PM schedules that are not identified as Default can generate work order suggestions during 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.
Save your work.
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), 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)
A Meter Template definition is required if the PM Template is based on Runtime Rule
Activity Definition (See: Defining Activities)
Meter Template Association (See: Associating Meter Templates with Asset Groups)
A Meter Template Association is required if the PM Template is based on Runtime Rules.
Activity Association Template (See: Activity Association Templates)
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 Next WO only 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.
Enter a PM Template name in the Schedule Name field.
Enter a Set Name. A PM schedule for an Activity and Asset Group must uniquely belong to a Set Name (See: Defining Set Names).
Each Set Name has an end date. The 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.
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.
Select an Asset Group.
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.
The Effective dates default from the current Activity association, if they exist. Optionally select or update the Effective From and Effective To dates.
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.
Optionally select a Work Order Status that best fits your business process.
When PM work orders are generated, (See: Generating Work Orders) they are created with this specified status. You can optionally update this status within the Maintenance Workbench (See: Using the Maintenance Workbench).
Optionally select Yes in the Next WO only 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.
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.
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).
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.
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).
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
In the Multiple Rules region, indicate how the predicted due dates are determined for multiple rules.
First: The due date is set to the first due date of all rules.
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.
In the Activity region, select one or multiple activities.
Activities associated with asset groups are eligible for use in a schedule template definition. 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.
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.
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.
Optionally enter a Tolerance In Days to indicate a minimum interval in days that suggested work order dates are spaced from each other.
Within the Date Rules tab, optionally enter Effective From and To dates to specify the rule's expiration.
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:
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), 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 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 (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.
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.
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).
Note: The Preventive Maintenance Scheduler (See: Generating Work Orders) 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.
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.
Save your work.
You can reapply an PM template to an entire asset group or to specific asset numbers or serialized rebuildables within an asset group. If there are any associated suppression templates, they are also reapplied.
Note: The concurrent program applies to asset groups that have an existing activity template applied.
Navigate to the Reapply Asset Template page (Enterprise Asset Management > Assets > Reapply Asset Template).
Select the Asset Type (required). Values are Capital or Rebuildable.
Enter the Asset Group (required).
Select PM Template for the Template Type to be reapplied (required).
(Optional) Enter values in these fields to reapply the PM template to specific assets within the asset group:
Asset Status
Asset Number From: Enter the beginning asset number value if you want to apply the PM template to a specific asset number in the asset group.
Asset Number To: Enter the ending asset number value if you want to apply the PM template to a specific asset number in the asset group.
Optionally select Yes in the View Only field if you not want the system to apply the templates; a log is generated but the templates are not reapplied to the assets. The default value is No.
Click OK to run the concurrent program to reapply the PM template.
Schedule definitions are implemented to create scheduled work orders, based on Day Interval rules, Runtime rules, or Calendar Based schedules. 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 for an asset group (serialized rebuildable and activity combination, asset number/activity combination, or an asset route/activity combination).
Calendar Based Scheduling
This option enables users to define recurring calendar setups that can be defined in PM rules. Calendar based schedule options are Weekly, Monthly and Yearly.
Note: Multiple calendar rules are allowed but cannot overlap in one PM schedule.
Calendar Based Schedules - Setup Information for Weekly Option
| Field | Values/Meaning |
|---|---|
| Interval | Enter the value for the interval such as enter 2 to repeat once every 2 weeks. |
| Day of Week | Sunday to Saturday |
| Day Num | Display only, values of 1 to 7 are displayed based on Day of Week value. For example, Day Num for Sunday is 1; sequence continues to Day Num as 7 for Saturday. |
Weekly Example
| Field | Values/Meaning |
|---|---|
| Interval | 3 |
| Day of Week | Monday |
| Day Num | 2 |
In this example, the activity should occur once every 3 weeks and is always scheduled to run on a Monday.
Calendar Based Schedules - Setup Information for Monthly Option
| Field | Values/Meaning |
|---|---|
| Interval | Enter the value for the interval such as enter 2 to repeat the activity once every 2 months |
| Repeat | First/Second/Third/Fourth/Last/Day of Month |
| Day of Week | Sunday to Saturday and Day option applicable for First and Last Day of the month selection. |
| Day Num | Display only field. Values 1 to 8 are associated with Day of Week value, or values of 1 to 31 are applicable to Repeat option for Day of Month. |
Monthly Example
| Field | Values/Meaning |
|---|---|
| Interval | 2 |
| Repeat | Last |
| Day of Week | Sunday |
| Day Num | 1 |
In this example the activity should occur once every 2 months on the last Sunday of the month.
Calendar Based Schedules - Setup Information for Yearly Option
| Field | Values/Meaning |
|---|---|
| Interval | Enter the value for the interval such as every 2 years. |
| Repeat | First/Second/Third/Fourth/Last/Day of Month |
| Day of Week | Sunday to Saturday and Day option applicable for First and Last Day of the month selection. |
| Month | January to December |
| Day Num | Display only field. Values 1 to 8 are associated with Day of Week value, or values of 1 to 31 are applicable to Repeat option for Day of Month. |
Yearly Example
| Frequency | Values/Meaning |
|---|---|
| Interval | 2 |
| Repeat | Last |
| Day of Week | Day |
| Day Num | 8 |
| Month | December |
In this example, the activity should occur once every two years and is scheduled on the last day of December.
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)
A Meter definition is required if the PM schedule is based on Runtime Rules.
Activity Definition (See: Defining Activities)
Meter/Asset Association (See: Associating Meters with Asset Numbers)
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)
Navigate to the Find Preventive Maintenance Schedules window.
This window enables you to enter information such as a Planner, to narrow your search for query mode.
Select Yes in the Next WO Only 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.
Enter a Schedule Name.
Attention: If your PM schedule requires more than one activity and if the activities use different cycles, we recommend that you create separate PM schedules.
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). 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.
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.
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.
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.
The Effective dates default from the current Asset activity association, if they exist. Optionally select or update the Effective From and Effective To dates.
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.
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.
Optionally select a Work Order Status that best fits your business process.
When Preventive Maintenance work orders are generated, (See: Generating Work Orders) 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).
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 and activity combination.
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.
Optionally select a Planner to assign to this work order.
If the Run To Failure check box 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 check box 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).
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.
In the Scheduling Options region, indicate how the PM Scheduler process calculates work order dates (see PM Scheduling Options).
In the For Multiple Rules region, indicate how the predicted due dates are determined for multiple rules.
First: The due date is set to the first due date of all rules.
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.
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:
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.
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.
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.
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.
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.
Optionally enter a Tolerance In Days to indicate a minimum interval in days that suggested work orders' dates are spaced from each other.
Optionally choose Last Service Info to enter the last service information for the current asset number and 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 and 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).
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.
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.
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), and with the Used in Scheduling check box 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 Reading | 3000 |
| Interval | 1000 |
| Last Service Reading Date | January 1, 2002 (this can be found via meter reading history) |
| 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.
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.
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).
Note: The Preventive Maintenance Scheduler (See: Generating Work Orders) 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.
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.
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:
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:
Intervals per Cycle
Current Cycle
Current Interval Count
Enter the required activities, taking the following into consideration:
The activity "Inspection" is scheduled after 100 hours of operation: (Interval Multiple (1) x Base Interval (100)).
The activity "Minor PM" is scheduled after 200 hours of operation.
The activity "Major PM" is scheduled after 400 hours of operation.
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.
Enter the meter name with a base interval of 100.
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.
Navigate to the Preventive Maintenance Schedules window.
Select Asset from the Item Type list of values.
Select an Asset Route from the Asset Number list of values.
See: Preventive Maintenance Scheduling, 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 and 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.
From the Preventive Maintenance Schedules window, choose Suppression.
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.
Optionally enter a Description for this suppression.
Save your work.
Note: Suppression is applicable to an activity association and can also be defined from the Activity Workbench and Suppression window.
