Back | Forward

We recommend that you first define two- or three-digit repair groups and then define repair tasks associated with the repair groups. To number repair tasks, start with the repair group followed by up to eight characters to define the task. The Options tab of the Data -> Shop Activity -> Setup -> Options screen specifies, in the Repair group task IDs are _ digits field, how many digits comprise repair groups.

For example, you want to define a repair group 01 for engine and a repair task of 01-222 to inspect for leaks in the engine (222 is the task ID for inspecting leaks). Many organizations use standard codes published by the American Public Works Association (APWA) or the American Trucking Association’s (ATA's) Vehicle Maintenance Reporting Standards (VMRS). You can use these codes to benchmark fleet management criteria against other organizations.

Repair groups and tasks are defined on the Basic Info tab of the Data -> Shop Activity ->Setup -> Tasks screen.

You can define as many repair tasks as you want. When you do, consider the following:

• Level of Detail: The higher the number of repair tasks, the more detailed reports become. But increasing the level of detail may reduce their usefulness.

• Ease of Use: The more repair tasks you define, the more choices users must select from to correctly describe repair work.

• Standards: The system supports cost and labor standards for each repair task, repair group, and PM service for each standards equipment class. If you use standards, you must define and maintain them for each repair task you perform on equipment units assigned to each standards equipment class. To learn how to define and maintain cost and labor standards, see the FASuite Setup Guide.

Reports contain an acceptable level of detail if you limit the number of repair tasks in typical repair groups to between five and seven. This approach does not apply to PM tasks, which must be detailed enough to enable you to build lists of tasks to perform on PM work orders.