Create New (CRT) dependency

In a create new dependency, when the prerequisite task is completed, an instance of the following task is created automatically.

To ensure accurate usage-based deadlines on following tasks, Maintenix enforces rules for this type of dependency. You can define Create New (CRT) dependencies only between two requirement definitions that are associated with the same tracked configuration slot, any two system configuration slots, or any combination of the root configuration slot and a system configuration slot on the assembly.

In the following diagram, Task A is a modification task that fixes a problem on an aircraft, but the fix must be verified once the aircraft has been able to fly with it for a period of time. Task B is an inspection task to be performed 120 flights after Task A is completed. Therefore, Task A must have a following task dependency to create Task B. After Task A is completed, Task B is created, and has a deadline of 120 flights.

Figure: Create New (CRT) dependency



A recurring task definition—one that is repeated at regular intervals—has a create new task dependency to itself. Task A in the figure below has the dependency onto itself. A recurring task definition does not show itself in the Following Tasks or Previous Tasks areas on their Details tab.

Figure: Recurring task definition



Using CRT dependencies, you can create a task definition chain that includes a repair task followed by an inspection task that is scheduled to occur at an initial interval and at a recurring interval. In this scenario, Task Definition A has a CRT dependency to Task Definition B:
  1. When repair Task A is complete, inspection Task B is created.
  2. According to the scheduled initial interval, Task B is completed and the first recurring instance of Task B is created.
  3. According to the scheduled recurring interval, the first recurring instance of Task B is completed and the second recurring instance of Task B is created, and so on.
If you require an inspection (or other) task to be performed at one interval, then at another interval, and then on a recurring basis, you must model the inspection task with different task definitions. For the first required inspection, you have a task definition to create a one-time task. For the second required inspection and the recurring inspections, you have a second task definition to create an initial (in this case it's actually the second) and the recurring tasks. So your task definition chain, including a repair with CRT dependencies to inspections, is as follows:
  1. Task Definition A (repair) is initialized creating Task A.
  2. When Task A is complete, Task Definition B (inspection) is initialized, creating Task B.
  3. When Task B is complete, Task Definition C (inspection) is initialized, creating Task C.
  4. When Task C is complete, Task Definition C is initialized again, creating the first recurring instance of Task C and so on.
In these scenarios, because of the prerequisite and following relationships between the task definitions, only one of these task definitions is initialized at a time on the same configuration slot. If, on the other hand, you have a task 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.