About program triggering

1. When there is a PM/unit calendar entry, the PM will trigger based on the first date found in the calendar that is after the last completion date. The PM calendar overrides everything.
2. When there is no calendar entry available to use, Enrich will fall back to using the PM rule Elapsed PM Calc Date.
   1. When option 1 is used, the calculations will be based on last completion.
   2. Option 2 is based on previous due date, but only when done on time or late; if done early, the system reverts to option 1.
   3. Option 3 is based on previous due date, regardless of being done on time, late, or early.
      • If option 2 or 3 is in effect but there was no previous completion, Enrich will revert back to option 1.
      • If using option 2 or 3 causes the calculated next due date to be prior to the last completion, Enrich will revert back to option 1.
      • When option 2 or 3 is used, the next due date will be calculated by taking the previous due date + the interval. The % due calculation is divided by the interval value. The # of days calculation will use previous due instead of last completion.

Scheduled (Nightly) PM Check

Following are the steps involved in the nightly PM check:

1. Clear the PM status file. The results of PM evaluation go into a PM status file. The first step in the nightly PM check is to clear this of all data.
2. Determine the equipment and PMs to include. Equipment is included if in a status of A (active) or I (in garage) or blank. PMs attached to the unit are included as long as they have a type of Inspection or Maintenance. The program start/end dates must be valid based on the job date. As well, the unit PM start date is checked. If revenue start date logic is turned on or if the unit has a specific start date for PMs, that may impact the inclusion of the unit/PM.
3. Unit/PM calculations.
   • If the unit/PM is found on an open roster (i.e. the PM is currently triggered), no further calculations are performed. A record is written into the PM status file with the trigger information and the record is flagged as not requiring further evaluation or triggering. If this triggered PM has a pattern, the description written to the status file will be the pattern description and not the general program description.
   • If the unit/PM is not on an open roster entry, the unit/PM calendars are checked. If calendars don't exist, rule 014 is checked. A record is written into the PM status file, flagged to trigger or not based on the results of these checks. The next due date as determined by the checks is written to the status file as well. If the PM has a pattern, Enrich will determine the next sequence that should be triggered and load that into the status file along with the pattern description.
4. Apply sliding. After the calculations have been performed, sliding is applied for those PMs where the rules say that sliding is possible. For each PM on the unit, Enrich compares the next due date to the due dates of all other PMs for the unit whose rule for Can PM's Slide To Me is Yes. If the difference in the dates meets the criteria for sliding (i.e. sliding early only, late only, or both) and the difference is within the allowed number of days for sliding, the original PM will be allowed to slide to this PM. If there are multiple PMs to which the original PM could potentially slide, the one chosen will be the one that is closest in days. The triggering flag on the original PM will be changed to that of the PM to which it is going to slide.
5. Trigger PMs. After sliding has been applied, Enrich runs through the PM status file for the unit and triggers any PM that is marked as being ready to trigger. Sub-programs will be handled as usual, which means that the activities from the sub-program will either appear on the roster or not, depending on the business parameter Auto Close Sub-programs. If the PM being triggered is one defined with a pattern, the description of the work roster will be changed to the description found on the pattern sequence being triggered. As well, the activities placed on the roster will come from the triggered pattern sequence.

Interactive Entry of a Metric Triggering a PM

This will call the identical function as is used in the nightly PM check, for the single unit only. The calculations are performed, the sliding is applied, and triggering is performed, if necessary. All PMs will be considered, even those that are purely date-driven.

Implementing Patterns

The rules for sliding can be added to any existing PM at any time and will come into play the next time triggering is being looked at for a unit/PM. If multiple existing PMs are going to be combined into a single new maintenance PM with a pattern, the following must occur:

1. Create the new PM with its pattern, giving each sequence its own description.
2. Set up the sliding rules on the PM.
3. Attach equipment and intervals to the PM as usual.
4. Attach activities to each pattern sequence.
5. Attach document links to each pattern sequence, if applicable.
6. Determine the last completion date for each unit as well as the pattern sequence last completed.
7. Enter PM history for each unit, which will update the date and pattern sequence for the last completion.
8. Put an end date on the PMs that are being replaced to prevent them from triggering again. This will ensure that the history for the original PMs will be kept intact.

Back to PMs