Data Models

TIBCO Fulfillment Order Management requires a variety of data models (catalogs) for its different functionalities.

TIBCO Fulfillment Order Management uses the following data models:

Data Models Description
Product Model It is used by the AOPD component for generating the execution plan for the newly submitted orders, as well as the amendments. It is also used by OCS, which is an optional component, in TIBCO Fulfillment Order Management.
Action Model It is optionally used by the AOPD component while generating the execution plans specifically for the ProductDependsOn feature.
Discount Model It is used by the OPE component for supporting the offering and pricing functionalities.
Price Model It is used by the OPE component for supporting the offering and pricing functionalities.
Plan Fragment Model It is used by the Orchestrator component for executing the plan for a particular order. It is also used by the optional component – JeOMS for supporting the jeopardy management functionalities.
Note: The optional OCS component also uses the Segment Model along with Product Model. However, since it is not used by any other core components such as AOPD or Orchestrator, its specific details are not covered here. For details, refer to the OCS documentation in TIBCO Fulfillment Order Management User's Guide.

The following table summarizes the models required by various components in TIBCO Fulfillment Order Management:

Components Data Models
Product Action Discount Price Plan Fragment Segment
AOPD Required Optional Not Required Not Required Not Required Not Required
Orchestrator Not Required Not Required Not Required Not Required Required Not Required
JeOMS Not Required Not Required Not Required Not Required Required Not Required
OPE Required Not Required Required Required Not Required Not Required
OCS Required Not Required Not Required Not Required Not Required Required