The Standard Job Unit/Dept/Component frame allows you to create standard job parameters at the Unit Level (or Department/Component Level) or to view and make modifications to some of the parameters setup on Standard Job MCC for the unit/department/component at the MCC Level. The frame will display both MCC and Unit Level jobs as well as the Next Due Date for each job.
You have the ability to change the last completion date for a job from this frame as well as view crucial Forecaster statistics. Keeping the data on this frame accurate is essential to have the Forecaster program correctly predict preventative maintenance jobs.
Absolute vs. Relative Jobs - What's the Difference?
Absolute Jobs are jobs that must be done on a mandatory schedule that does not vary. For example, State Inspections which are required yearly and must be completed by the same date. Relative Jobs are those that are forecasted by adding the time and usage intervals to the last time the job was completed. M5 will predict the due date for whichever interval comes first based on the date of last completion.
Schedule Tab
You can setup the intervals for the standard job on this tab. Intervals are Time, Primary Meter, Secondary Meter and Fuel Consumption. You can enter just one or a combination of interval values. Next, you can enter the Deviation Percentages (Earliest and Latest).
For jobs already configured at the MCC level, the recurring interval information will display as read-only with the values from the Standard Job MCC frame.
Relative Jobs - the deviation percentage sets the "window" on a work request in calculating when the earliest and the latest date may be for the job. It expresses the window of opportunity in which a WR will be generated for a job to be DON.
Example:
Interval - 90 days
Last Completed Date - January 1
Deviation Percentage - 10%
Earliest Date - March 23
Due Date - April 1
Latest Date - April 10
Absolute Jobs - the deviation percentage calculates whether the unit will be given "credit" for jobs performed earlier or later than the actual due date. The deviation percentage is the percentage of the job interval by which the completed or DON date may deviate and the unit will still receive "credit."
Example:
Interval - 365 days
Original Interval Start Date - April 1
Deviation Percentage - 10%
Earliest Date - February 24 (the following year)
Due Date - April 1 (the following year)
Latest Date - May 8 (the following year)
'First Time Criteria' is an important setup requirement for absolute jobs. If 'First Time Criteria' is not set at either the Standard Job MCC or Standard Job Unit/Dept/Comp level, M5 will use the in-service or acquisition date or meter to determine when the job should be considered done and due next. See System Flags 1180 and 2001 in the System Flags section below for more information.
The MCC code for the unit will display below the Recurring Interval and First Time Criteria sections in read-only mode. If the standard job already exists at the MCC level, you can click on the MCC Schedule hyperlink to launch the Standard Job MCC frame.
Forecaster Tab
Forecaster is a Batch Process that predicts the next due date of scheduled jobs based on previously entered and predictable data to create work request for these jobs. This information will automatically populate in read-only mode with the data from Standard Job MCC if the standard job already exists at that level.
Forecaster Information:
Scheduling Basis - Relative or Absolute. If the job is relative, the next job due is based on the last completion date. If the job is absolute, the next job due is based on a fixed schedule either by the in-service date, the first date indicated at the Unit level, or first date indicated at the MCC level.
Recurring Job - Check this box if M5 should forecast the job continuously and not just one time.
Seasonal Restriction - In MCC Season or Outside MCC Season. You must have Season Codes created and configured on the MCC.
Maintain Intervals in Cycle - The interval difference between each job is held constant. For example, a unit has a PM cycle of A, B, and C, where the A job is due every 10,000 miles, the B job is due every 20,000, and the C job every 40,000. If the A job is done at 10,500 instead of 10,000, the interval is still maintained. So the B job would be due at 20,500 and the C job would be due at 40,500. This applies to relative jobs.
Push Next Occurrence to the End of the Month - If this box is checked, the next due date will be determined as if the job was done at the end of the month in which it was completed. So if a job was done on March 1st and the cycle for the job is 6 months, the next time the job would be due is September 30th and not September 1st. This only applies to relative jobs.
Job Defaults:
Location Code - If you enter a location code at this level (the MCC level), M5 will forecast jobs at the location entreated in this field for all units within the MCC. If you leave the field blank, M5 will use the maintenance location on the unit main record.
Visit Reason - Default visit reason for M5 to assign when forecasting the job.
Priority - You can set priority values from 0-9 with nine being the highest priority.
Calibration - Designed to work with Equipment Focus functionality. If selected and the job is added to a work order, M5 will update the unit's calibration date when the job is marked as DON on the work order.
Prevent Job Reason Changes - Check this box to prevent job reason changes on the work request and work order for the standard job.
MCC Seasons:
MCC Season Code information will display here in read-only format if the information is setup and configured for the specific MCC code associated with the standard job.
FORECASTER STATISTICS
Click on the Forecaster Statistics hyperlink to view the statistics for this Standard Job. The forecaster statistics include the last date of completion for the job, the next due date for the job as wells as fuel consumption, meter readings and any Forecaster Notes. This information is particularly useful when troubleshooting issues with the Forecaster Batch Process.
History Tab
The History Tab gives you the ability to make corrections to ensure the Forecaster is accurately predicting standard jobs. There are two columns for each Reading value: Last Completion of Job (editable) and Current Values on Unit (read-only).
Sub Job Tab
A sub job is another standard job that is performed as a part of this standard job. When the main job is performed, M5 will consider the sub job completed.
Sub Job - Enter the sub job to be included when performing the standard job. Sub job must already exist as a standard job for the MCC.
Description - Job Description will display automatically here.
Elimination % - If the job falls within a certain amount of time of the higher level job, M5 will not forecast the job to prevent the user from seeing two PM's on the schedule at the same time.
Reset Flag - If checked, M5 resets the sub-job start time once the primary job is complete.
System Flags
1180 - Base Forecasts on In-Service Date? (Y/N) - If set to 'Y', the system will use a unit in-service date, rather than its acquisition date, as the basis for establishing work requests. Additionally, if the flag is set to 'N', the forecasting beginning date is set for a unit on the unit level, and that beginning date will be the first date of when the job will be performed.
2001 - Consider a Job Done at First-Time DATE when Forecasting? (Y/N) - If set to 'N', the first occurrence will be due on the unit's acquisition date or in-service date (which depends on flag 1180), or if set on the standard job, the "first time" date. If set to 'Y', the first occurrence will be due on that date plus the standard job's time interval. The default for this is 'Y'. System Flag 5270 performs the same function for usage forecasting.
5270 - Consider a Job Done at First-Time USAGE when Forecasting? (Y/N) - If set to 'N', the first occurrence will be due on the standard job's first-usage. If set to 'Y', the first occurrence will be due on the standard job's first-usage plus its usage interval. The default for this is 'Y' to preserve the behavior that existed before the flag was created.
5339 - Validate Job in the Cycle for Unit? (Y/N) - When set to ‘Y’, any job being added to a work order that is part of a cycle for a unit needs to be validated as the “most due” (based on earliest date) of any job in the cycle, and also the highest job in the sub job configuration. If it is set to ‘Y’ the following rules apply:
Job cannot be added if another job in the cycle has already been added to a work order.
Job cannot be added if no work request is found for any job in the cycle.
The job being added must be the one that is due/overdue (based on earliest date) and is the highest level job in the cycle.
5375 - Exclude sub-job test suites? (Y/N) - When the flag is set to Y, if users add the parent job ONLY, the Test Suites displayed will be only those set up for the specific job added to the work order.
When the flag is set to N, if users add the parent job ONLY, the Test Suites displayed will be those set up for the Parent Job AND all Sub-Jobs (as set up on the Standard Job MCC frame).
Regardless of this flag's setting, if a specific job is added to a work order and it has test suites set up specifically for them, their test suites will be required to be completed, regardless of duplication or parent/sub-job designations.
Example:
Parent Job: 01-01-001, with test suites TEST1, TEST2, TEST3.
Sub-Job: 02-01-001, with test suites TEST2, TEST3, TEST4.
Sub-Job: 03-01-001, with test suites TEST4, TEST5, TEST6.
When set to Y and adding job 01-01-001 ONLY to the work order, users will see test suites TEST1, TEST2, TEST3.
When set to N and adding job 01-01-001 ONLY to the work order, users will see test suites TEST1, TEST2, TEST3, TEST4, TEST5, TEST6.
When set to Y and adding job 01-01-001, 02-01-001, and 03-01-001 to the work order, users will see test suites associated to each job:
1. 01-01-001 associated with test suites TEST1, TEST2, TEST3.
2. 02-01-001 associated with test suites TEST2, TEST3, TEST4.
3. 03-01-001 associated with test suites TEST4, TEST5, TEST6.
When set to N and adding job 01-01-001, 02-01-001, and 03-01-001 to the work order, users will see test suites associated to each job AND all test suites associated to the sub-jobs but attributed to the parent job:
1. 01-01-001 associated with test suites TEST1, TEST2, TEST3, TEST4, TEST5, TEST6.
2. 02-01-001 associated with test suites TEST2, TEST3, TEST4.
3. 03-01-001 associated with test suites TEST4, TEST5, TEST6.
Last Updated: 06/24/2020
NOTE: To view a list of System Flags and Role Privileges that may impact this screen, hover over the screen title in M5 to display the bubble help/tooltip. At the bottom of the bubble help/tool tip, there is a Settings hyperlink. Click that hyperlink to display the list of flags and privileges.
Additional training and technical documents on this subject may be available in the Resource Files area.