Milestone to Milestone Dependency
Intermediate milestones in a process component has a dependency on the completion of the intermediate milestones in another process components.
The following figure shows the milestone to milestone dependency:
ProductComprisedOf Sequence and Intermediate Milestone Dependency
Sequencing is an indication of the order in which the plan items are executed. If there is not an intermediate milestones dependency set, a default START-END dependency is created. When using the ProductComprisedOf sequence and intermediate milestones at the same time, the intermediate milestone dependencies takes a precedence over the conventional End-->Start dependencies.
The following figure shows a START-->END dependency with an intermediate milestone dependency:
- The plan for an order is generated in the usual manner. There are no intermediate milestone dependencies yet. The following is the plan based on the sequences:
Start_Plan1_End --> Start_Plan2_End --> Start_NO_RECIPROCAL_ACTION _End.
- The generated plan is evaluated against the intermediate milestone dependencies defined in the product model so as to rearrange the dependencies. In this step as per the product model, the milestone 'Milestone_Dependency_2' of Plan2 will depend on the milestone_M1 of Plan1.
Start_Plan1End ---> Milestone DependencyPlan2_End
- There is a check for whether to add the existing dependencies or not. If the intermediate milestone dependency in a plan item is on the same plan fragment as the one in existing dependency, it ignores the existing dependency on that plan fragment, for example, the start of Plan2 will not depend on the end of Plan1 anymore.
The following is the final plan:
Start_Plan1_End ---> Start_Milestone DependencyPlan2_End ---> StartNO_RECIPROCAL_ACTION_End
The intermediate milestone dependencies take a precedence over the conventional End-->Start of dependencies.
