The Repeat Repairs frame allows you to configure system-component repair codes to be identified as a repair that was previously performed within a recent time frame. The time frame can be defined in terms of days or usage. This allows you to monitor its recurrence rate to determine if there is a cause to be concerned due to an abnormal frequency rate.
For instance, if the brake pads have to be replaced after 10,000 miles when they should last 20,000 you might suspect a problem with the calipers or suspension or some other systemic issue.
When a Work Order is opened for a unit with a job code that is configured as a repeat repair, a warning message will appear showing detailed information such as the last work order number where the job was performed, elapsed days since the last repair and the elapsed usage. The warning will also appear if the job has been added on the fly using Labor Wedge or if the job originated as a work request.
The job code hyperlink will be RED to clearly notify the user that the job is a repeat. Selecting the link will display the repeat repair history in the Work Order Job detail.
This screen allows you to query by System, Component, MCC and Tech Spec. When you click on Find, the bottom portion of the screen displays the existing job codes configured as Repeat Repairs. If you click on Find without specifying any of the four you will see all the current Repeat Repairs.
You may also configure additional job codes on this table. Go to the last empty row and add the Sys-Comp code. The description will appear. Next add the MCC and Tech Spec codes.
Then enter the Time Back Days and Usage Back to create the range that will qualify it as a Repeat period. Next enter the Max Repeats to indicate how many times the job must be performed to become a Repeat Repair.
There might be an occasion where the action taken should not be considered a repeat repair. There is a field on the Work Accomplished Codes frame that allows you to set specific WAC codes so that they are not flagged as a Repeat Repair.
There is a Repeat Repairs Batch Process (Repeat Work) you can run that will clear all repeat flags in the specified date range and reset them based on the current parameters configured in the repeat work parameters table.
System Flag 5212 identifies the source for this table. When you first configure all your Repeat Repair codes you can run this to setup all the Sys-Comp code parameters. After the initial run it should not be necessary to run the batch program again. However, it can be run at your discretion if the Repeat Repair parameters are changed. The batch program can be launched using the Batch Process Manager frame.
System Flags
5212 - Use enhanced Repeat Repair system? (Y/N) - Set to 'Y', enhanced Repeat Repair System will be used. Setting to 'Y' allows access to the Repeat Repairs frame. Default is N which will preserve existing functionality (batch mode only using System code configuration settings and standard reports).
5359 - Use "Ignored" WACs when Evaluating Job History for Repeat Repair? (Y/N) - When a job is entered, default behavior is to check previous job occurrences whether or not the previous jobs have a WAC with the Ignore Repeat Repairs flag set to Y. Also, when clicking on a previously flagged job to see its history, jobs will appear in the history whether or not the WAC is set to Ignore. The only function of the Ignore flag is that a job with an Ignored WAC will not itself be flagged as a Repeat Repair. However, if you set this flag to N, jobs with WACs that have the Ignore flag set will not be considered at all and will not appear in the Repeat Repair job history. This flag is only used when System Flag 5212 is set to Y.
Last Updated: 03/27/2017
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.