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 they are verifying 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.
To view or modify an existing Test Suite, enter or select the Test Suite Name. You may modify the description; this field has a limit of 30 alphanumeric characters. You can disable the suite or change any of the Corrective Job Data. To modify an entry sequence select its row.
To delete a sequence, select its row and click on delete. The row will turn red. Click on save to remove the record. To delete the Test Suite, click on Delete. You will be asked to confirm the deletion.
To create a new Test Suite, enter a new Name, up to 30 characters, letters and numbers. Press tab and enter a new Description. Then select the Job code, Reason and Priority. Select Yes or No to Allow the User to override the Job Code. Click on save.
On the first empty row below, enter the first test sequence Entry Label, ID Number (used in DVSA functionality for IM No.) Description, and Data type. Then configure the remaining attributes for Job Code, Info Only, Spawn Job, and Fault Codes. Press tab and add another Entry Sequence if desired. Click on save when you are done.
Once the Test Suites are created, they need to be tied to a Standard Job's Tech Spec. This could be a PM job or any other standard job that the tests would be associated with. Once that standard job is on a work order, then the tests will display on the work order.
Test Suite Results report
The SmartApps Checklist must be Yes for signatures to print on the Test Suite Results report on the Work Order Main frame.
Subsections Tab
The Subsections tab allows you to categorize checklists by subsections so that similar test suites can be grouped together when the SmartApp Checklist flag is enabled.
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.
Once you add all the necessary subsection codes on this tab, you must assign the codes to each entry on the Test tab.
Categories Tab
Users can limit checklists within the application by Category Codes on the Categories tab. A new System Flag - 5365 controls this functionality. You set this flag to Y to use this functionality.
Once the flag is set to Y, you can assign categories to the test suite to have them appear in the SmartApp so that any unit assigned to a category will see the checklist and any unit not assigned will not have access.
System Flags
Flag No. | Description | Notes |
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. |
See also:
Standard Job Technical Specification
Test
Suites Quick Reference Guide
Last Updated : 03/2023
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.