Task definition types

When you create a task definition, you associate it with the configuration slot of the assembly that is relevant to the work being done, or with the part number of the component on which the work will be done.

Part number-based task definitions eliminate the need to define a task definition on each configuration slot where a component can be installed across all applicable assemblies. You can use part number task definitions for the following tasks:
  • Maintenance requirements for components that are in storage.
  • Modifications to components.
  • Tracking compliance for components.
  • Tracking shop visit maintenance requirements for components.
  • Work that is required on tools, for example calibration.
Note: You cannot link a part number task definition to a configuration slot task definition, and vice versa.

Part number task definitions are very similar to configuration slot definitions in that they can have links, scheduling rules, and so on. Also, when you activate a part number definition, baseline synchronization pushes out the new revision on applicable inventory. When a part number requirement is initialized, Maintenix also initializes the associated job cards. However, there are differences between part number task definitions and configuration slot definitions:

  • You can create part number type definitions for only requirements, job instruction cards, and reference documents.
  • Blocks and Master Panel Cards (MPCs) apply only to assemblies and are therefore created on config slots. You cannot create them for part numbers.
  • Part number task definitions cannot be used in the Long Range Planner (LRP) application.
  • Troubleshooting (CORR) task definitions and replacement (REPL) task definitions cannot be or include part number task definitions.
  • Part number based task definitions will have their applicability and modification restrictions enforced when actual tasks are created using the Create Historical Task workflow (in contrast to tasks created against configuration slots).
  • Part number task definitions on BATCH parts cannot have scheduling rules.

  • The Maintenix compliance report is not available for part number task definitions.

    Note: For configuration slot task definitions, the task definition codes you assign must be unique only on a given configuration slot. For part number task definitions, task definition code must be unique across the Maintenix system.
You should use configuration slot-based task definitions whenever you need to use any of the Maintenix functionality that does not apply to part number task definitions.
Note: It is recommended to use configuration slot requirements rather than part number requirements because IFS Maintenix cannot include part number requirements in the aircraft's maintenance program.