Offer Eligibility and Validation
TIBCO Offer and Price Engine uses the same offline models schema currently being used by the TIBCO Product and Service Catalog engine. TIBCO Offer and Price Engine uses product models to get offers configured in the product catalog.
In the TIBCO OPE architecture, the top-level product has no auto-provisioned parents associated with it. All such products are considered as a product offering. Using the class and subclass features of the product model, they can be classified into logical types.
Online integration with TIBCO Product and Service Catalog is also possible using the publish catalog method.
TIBCO Offer and Price Engine integrates with offline models that are published with compliant schema without TIBCO Product and Service Catalog.
TIBCO Offer and Price Engine uses product models (optionally
OfferMappingFile to link
OfferIds) to get offers configured.
Relationships
TIBCO Offer and Price Engine makes use of the following relationships for offer generation and validation and price determination:
| Relationship | Description |
|---|---|
| Product Comprised Of | This relationship is used to define the dependencies between the products, which lead to the decomposition of parent and child products. |
| Characteristic | This relationship is used to associate the characteristic entities with a product. In addition to characteristics that are fulfillment related, some internal characteristics are used by the product for internal logic. These are related to error handling. |
| Compatible Product | This relationship defines that two products can exist in an order or customer image. |
| Incompatible Product | This relationship defines that two products cannot exist in an order or customer image. |
| Compatible Segment | This relationship defines that a product is compatible with the segment. A product can either be compatible, incompatible, or not related to the segment. If a product is defined as both compatible and incompatible in the model, it is considered a compatible product. Segments are grouped by segment type. |
| Incompatible Segment | This relationship defines that a product is incompatible with the segment type and name. |
| Class and Subclass | This relationship can be used to classify products into different logical types. |
| Product Required For | This relationship is used to define the prerequisite between two products. With this relationship, you can create offers without defining the sequence or dependency between products. These products are implicitly provisioned with the parent. |
| Category | This relationship defines that a product belongs to a category. A product can belong to no category, one category, or too many categories. |
Record or Relationship Attributes
This engine uses the following record attributes and relationship attributes:
| Attribute | Description |
|---|---|
| RECORD_STATUS |
This record status characteristic indicates whether the record is active or not. |
| Start Date |
This record level attribute indicates whether the product is an eligible product for the requested order date if it is after the start date. |
| End Date |
This record level attribute indicates whether the product is an eligible product for the requested order date if it is before the end date. |
| Link Definitions |
This is a type field in the characteristics that defines the linking attributes, for example, subscriber ID or any other characteristic between two products. The LinkDefinitions are evaluated for the following relationships:
If LinkDefinitions are provided for relationships, these values must match the values for UDFs for the corresponding products in the offer and the order request. |