Initialization

Initialization turns active task definitions into actual tasks for inventory to which the task definitions apply.

Only the active revision of a task definition can be initialized, unless the task definition is assigned to a maintenance program. Users can only initialize tasks definitions for organizations to which they belong.

Some task definitions are initialized manually by users, and some are initialized automatically by Maintenix when certain conditions are met—for example, when a dependency exists between two tasks and the prerequisite task is complete. When the baseline synchronization process runs in Maintenix, it automatically initializes task definitions that meet a certain criteria—for example, if a change made to a task definition caused the task definition to become applicable to an inventory item it did not apply to earlier.

Task dependencies create chains of task definitions which baseline synchronization initializes according to the dependency relationships. For example, following task definitions aren't initialized until prerequisite tasks are complete. If you have a task definition chain in which two different prerequisite task definitions have CRT dependencies to the same following task (all are on the same configuration slot), both of the prerequisites can be initialized at the same time.

When block definitions are initialized, Maintenix assigns the requirements to the most appropriate block. When requirement definitions that are included in blocks are initialized, Maintenix assigns the requirements to the most appropriate block, and initializes the job cards included in the requirement automatically. Users cannot initialize job cards manually. Initialization of requirements marked as Prevent Manual Initialization is skipped when they are contained in a block that is initialized.

If your Maintenix system includes inventory for several operator organizations, and you initialize a requirement that is included in a maintenance program in Maintenix, you can only create actual tasks for inventory that belongs to operators that have this specific revision of the requirement in their active maintenance programs.

For reference documents, if you want to initialize them in addition to activating them, you initialize them either as historical tasks—which indicate that your organization has already complied with the maintenance needs stated in the reference document by using requirements that were linked to the reference document—or you state that the reference document is not applicable to your fleet. Initializing reference documents is not necessary in the solution IFS proposes for managing Service Bulletins (SB) Airworthiness Directives (AD), and Engineering Orders (EO).