The Test Suite Maintenance frame allows you to create and maintain the troubleshooting and performance verification tests for your fleet vehicles. These tests can be grouped together according to the system or component being verified and are associated with Standard Jobs and Tech Specs.
The Test Suite functionality is designed to provide a structure to capture and respond to test results. If the test results indicate a failure, a work request is automatically created for corrective action. Common examples of test suites are emission inspections, brake tests or mandatory safety checks.
Create a new Test Suite
Enter a new Test Suite Name, limited to 30 characters. The Action Required window displays.
Select Create to create the new test suite. Limited to 50 characters.
Press Tab and enter a description.
Within If any test item fails, Corrective Job data is as follows, unless overridden, enter a job Code, Reason and Priority.
Select Yes or No for Allow user to override JobCode, SmartApps Checklist, Enforce Signature, Available on Direct Test Suite Entry, Show on Vehicle Safety Query, Add WR to Current Work Order, or Send Fail Notification.
Select SAVE.
Within the Tests i-frame:
On the first empty row, enter the first test sequence Entry Label, ID Number (used in DVSA functionality for IM No.), Entry Description, and select an EntryData type.
Configure the attributes for Corrective Job Code, Info Only, Spawn Job, Fault Code, and other attributes, as applicable.
Press tab to add another entry sequence, as applicable.
Select SAVE.
After the test suites are created, they need to be associated to a Standard Job's Tech Spec. This could be a PM job or any other standard job that the tests are associated with. After the standard job is on a work order, then the tests will display on the work order.
View or Modify an Existing Test Suite
Enter or select the Test Suite Name. The description automatically displays.
Modify the description as applicable. Limited to 50 characters.
Select No from the Enabled dropdown to disable the suite.
Modify the Corrective Job data, as applicable.
Modify the Yes or No flags, as applicable.
Within the Tests i-frame, select the Entry Seq row to modify an entry sequence.
Select SAVE.
Delete a Sequence or Test Suite
To delete a sequence, select the Entry Seq row and select DELETE. The row highlights red. Select SAVE to remove the record.
To delete the Test Suite, select DELETE. The Action Required window displays, select Delete to confirm the deletion.
The Send Fail Notification indicator controls when the WR CREATED FROM TEST SUITE FAILURE notification is sent from Notification Manager.
You can select the In-Range Only checkbox when the Minimum Value and Maximum Value is entered.
If you select In-Range Only for the ENTRY OF DATE RANGE data type and the minimum and maximum values are entered, you can enter a date that is + (plus) or - (minus) the number of days from the date the job was entered on the work order.
For example:
Minimum Value is 7, Maximum Value is 21, date of job added to the work order is 03/14/2024 - you can enter any date from 03/21/2024 to 04/04/2024.
Minimum Value is -21, Maximum Value is -7, date of job added to the work order is 03/14/2024 - you can enter any date from 02/22/2024 to 03/07/2024.
All entries are considered a Pass.
If you do not select In-Range Only and enter minimum and maximum values, you can enter any date value.
Dates within the minimum and maximum range based on the date the job is added to the work order is a Pass.
Dates outside the minimum and maximum range based on the date the job is added to the work order is a Fail and generates a work request, as set up. The date the job is added is the job's due date. On the Direct Test Suite Result Entry frame, the date is the Test Date.
For example:
Minimum Value is 7, Maximum Value is 21, date of job added to the work order is 03/14/2024 - you can enter any date. Dates entered from 03/21/2024 to 04/04/2024 are a Pass. Any other date entered is a Fail.
Minimum Value is -21, Maximum Value is -7, date of job added to the work order is 03/14/2024 - you can enter any date. Dates from 02/22/2024 to 03/07/2024 are a Pass. Any other date entered is a Fail.
If you do not enter a minimum or maximum value, you are unable to select the In-Range Only checkbox. You can enter any date. All date entries are a Pass.
Within the Tests i-frame, you can select the Note Req or Fail Note Req checkbox to require notes for test suites or test suite failures.
If the Note Req or Fail Note Req checkbox is selected and notes are not entered, a message displays a list of the test suites missing notes. The test suite will not complete.
If the Note Req or Fail Note Req checkbox is blank, the test suite completes with a Status of Complete and a Result of Failed.
Note: You can add or remove the selection from the Note Req or Fail Note Req checkbox to modify an existing test suite.
The SmartApps Checklist must be Yes for signatures to print on the Test Suite Results report on the Work Order Main frame.
The Subsections tab allows you to categorize checklists by subsections for similar test suites to be grouped together when the SmartApp Checklist flag is Yes.
Before subsections are available for use on this tab, you must first set them up on the Subsection Codes frame. Then you can add those codes to the subsection tab and list them in the order in which they must appear in the application.
After you add all the necessary subsection codes on this tab, you must assign the codes to each entry on the Test tab.
The User Instructions tab allows you to enter general information regarding the test suite. This information displays on the Direct Test Suite Entry, Labor Wedge Test Suite Entry, and Work Order Test Suite Entry.
Users can limit checklists within the application by Category Codes on the Categories tab. This tab only displays when System Flag 5365 is set to Y.
After System Flag 5365 is set to Y, you can assign categories to the test suite to have them appear in SmartApps so that any unit assigned to a category will see the checklist and any unit not assigned will not have access.
5001 - Adopting 3-char SYSTEM code/10-char JOB code? - This flag allows the user to define how they wish their job codes to display. If "Y", a 3-char system code is needed with the job code like 02-013-001. If "N" (the default), M5 utilizes the standard job code like 02-13-001.
5010 - Client Prefix Code - This system flag sets the Client Prefix Code, usually set by AssetWorks.
5365 - Show and Enforce Categories in Test Suite Maintenance for SmartApps (Y/N) - If the flag is set to "Y" the category tab on Test Suite Maintenance will be visible. In addition, available Test Suites will be restricted by category for SmartApps. If the flag is set to "N" the category tab will be hidden, and categories will not be enforced.
5479 - Entry Description on Test Suite Maintenance is required? (Y/N) - The default value will be Y to preserve the existing functionality. When set to N, the Entry Description field on Test Suite Maintenance is not required.
5517 - Add Test Suite Results to Current Work Order? (Y/N) - When this flag is set to Y, the Test Suite Maintenance frame will display a checkbox in the header. When this checkbox is populated, any failures on the Test Suite entry (from Work Orders only) that create work requests will have all created work requests added to the current work order. Note: Jobs cannot be duplicated. If a resultant job is already on the work order, the work request will be created, but will not be added to the work order.
Standard Job Technical Specification
Notification Manager Quick Reference Guide
Test
Suites Quick Reference Guide
Last Updated : 03/2023, 07/2024
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.