Intermediate Milestones Dependencies

The actual fulfillment of a product is done by orchestrating the back-end process components. By default, any process component has two milestones:

  1. START
  2. END

These milestones represent the starting and the end parts of it. There is a direct dependency between the process components due to sequencing of the products in the catalogue. This dependency is of type END-to-START, or once a process component is completely executed, then only the dependent process component can start its execution as shown in the following figure:

END-to-START dependency


The process component EP_DEVICE_PROV can start only when EP_SERVICE_PROV is completed and EP_TARIFF_PROV can start only when EP_DEVICE_PROV is completed.

TIBCO Fulfillment Order Management also supports the following complex types of dependencies between the executing process components:

These dependencies are supported with the implementation of Intermediate Milestones within the process component in addition to the START and END.

The functionality provides a base behavior that permits plan items to be sequenced corresponding to products related by MDO when:

  1. MDO related product instances have no LINKID defined.
  2. MDO related product instances have LINKID defined and have same LINKID value.

This feature can extend the base behavior and sequence additionally plan items corresponding to products related by MDO when:

  1. MDO related parent product instance has LINKID defined and child product instances have no LINKID defined.
  2. MDO related parent product instance has no LINKID and child product instances have a LINKID defined.

An MDO related parent product instance can relate to multiple child product instances using base and extended cases so that following use cases are possible:

  • An MDO related parent product that has a LINKID defined and is related to a child instances that has same LINKID defined shall be also related to MDO related child product instances that have no LINKID defined.
  • An MDO related parent product that has no LINKID defined and is related to a child product instance that has no LINKID defined shall be also related to MDO related child product instances that have a LINKID defined.