Modeling the MILESTONE and PLANFRAGMENT Repositories in TIBCO PSC
Perform the following steps to model the Products, PlanFragments, or Milestones:
- Procedure
- Create the
Milestone records.
Note: Create separate Milestones with Milestone names as
START
andEND
respectively, in addition to any intermediate milestones for association with a plan fragment. While creating theSTART
milestone, create theEND
milestone using theMilestoneToMilestone
relationship.Caution: There is no fixed nomenclature for Milestone ID but Milestone names must beSTART
andEND
. - Create the
PlanFragment records and associate the Milestones created earlier using the
PlanFragmentHasMilestone
relationship appropriately. - Decide the sequence of milestones in a plan fragment by creating the
MilestoneToMilestone
relationship between the associated milestones in a plan fragment.MilestoneToMilestone
relationship can only be created between the milestones associated with the same plan fragment.Note:The MilestoneToMilestone relationship must be modeled between all possible combinations of milestone pairs that may appear in the plan item in the execution plan generated by AOPD. Although the product model can have any number of milestones defined, the actual plan item may contain only the subset of these milestones due to the dependency modeling and the products being ordered.
Assume that PF_PROVIDE is a plan fragment associated with product P1 for PROVIDE action in the product model. Also, it contains four milestones namely START, M1, M2, and END. Now, based on the dependencies modeled and the products ordered, one of the three milestone combinations given below can come into the plan item generated for the fulfillment of P1.
- START, M1, END
- START, M2, END
- START, M1, M2, END
To support any of the three milestone combinations mentioned above, the MilestoneToMilestone relationships must be modeled for the following milestone pairs to have the corresponding sections in the plan fragment model.
- START->M1
- START-M2
- M1->M2
- M1->END
- M2->END
While processing this plan item in the execution plan reply, Orchestrator finds the required plan fragment sections to sort the milestones in a proper sequence based on the typical duration value. This ensures the correct representation of the plan item on the OMS UI Gantt chart. If any of the required sections are missing in the plan fragment, Orchestrator fails with an exception to process the execution plan.
For example, in the case of the START-M1-M2-END combination, the sequence of M1 and M2 after START is decided based on the typical durations for START->M1 and START->M2. If START->M1 is 2000 ms and START->M2 is 1000 ms, milestone M1 is sequenced after M2. So the sequence is START->M2->M1->END.
- Decide the dependencies between the milestones of two separate plan fragments by creating the
MilestoneDependsOn
relationship between the associated milestones in the plan fragments.MilestoneDependsOn
relationship can only be created between the milestones associated with different plan fragments. - Create the Product record and associate the plan fragments for four actions using four different
ProductHas[*Action*]PlanFragment
relationships. For instance,ProductHasProvidePlanFragment
. - You can also associate the newly created plan fragments with the existing products by using the relationships explained in point 5. However, you must remove the plan fragment attributes specified in the INTERNAL and AFFINITY tabs.