Open topic with navigation

TIBCO® Product and Service Catalog powered by TIBCO EBX® 1.2.0

# TIBCO® Product and Service Catalog powered by TIBCO EBX® Master Repositories

TIBCO Product and Service Catalog powered by TIBCO EBX models and manages its SID-based objects in the following separate repositories:

Repository Name | Description
--- | ---
Allowance | Allowance information that can modify Price (for example, 250 minutes free, then the normal 10 cents per minute thereafter).
Catalog | List of subset of offerings to allow for management of multiple catalogs of ProductOfferings.
Category | Category
Characteristic | Characteristics or Usages that a Product or Price may relate to. A record can be both a characteristic and a usage at the same time (for example, a handset has an "SMS" characteristic. "SMS" is also be defined as a type of "Usage" that can be charged for. Characteristics often contain values that describe the amount of the Characteristic. Such values may be defined once (500 Free Minutes), user or system input at time of order (MSISDN = ?), or may be "Instanced" and vary per Product Offering (Sales Package has the "Free Minutes" Characteristic. The value of Free Minutes for the Sales Package = 1000).
CharacteristicDataType | Additional information for Characteristic.
Discount | Discount information that can modify Price (for example, 25% off from 10 - 14 February, 50 Euros off the cost of installation)
Migration | Migration
Milestone | Representation of the start and end of part of an executing plan item.
Party | List of Party Entities that may be used to further define compatibility of Products, Prices, or Policies with specific Parties. Parties may be defined as Organizations, Roles or People. Organizations may be individual Corporations, or Corporations and their subsidiaries (Corporate Hierarchies). A Role represents a group of people (for example, IT Staffǰ Administrator, Senior Management). People represent actual named, individuals (for example, John Smith).
PartyExtension | Additional information associated with Parties.
PlanFragment | It provides configuration information for a Process Component/Plan Fragment of BPM Engines. It has information for SLA.
PolicyRule | Rule definitions that may be applied to Products to further specify unique qualification rules or events for a ProductOffering (for example, "this product can only be sold to the females", "after one year get something free").
Price | The data repository used to maintain price and price matrices, as well as usage charge information for products that have associated fixedǰ usage, recurring, simple, or one-time charges.
Product | Each record in the Product repository represents a Component. Components comprise other Components, which may include other Components. Depending on the complexity of the data there is no limit to the level of componentization you wish to model. From a SID perspective, a top-level Component is called a Product. Sub-components are known as Composite Products (if made of a distinct group of components) or simply Components. In turn, TIBCO Product and Service Catalog also allows the user to classify their components into logical types (Device, Tariffsǰ Services, Options, and so on).
ProjectTag | It provides a central repository to manage the Project Tag Names. These tag names are later used across other repositories.
RequiresProduct | Requires Product
Rule | Rule
RuleCondition | Rule Condition
RuleParameter | Rule Parameter
SalesChannel | A repository defined to create all the possible channels or modes, through which the Offers can be sold to the end user (For example, Online Marketplace, Retail stores, Door-to-Door).
KeyValue | Key value
Segment | Contains a list of other reference entities that may impact the definition of Products (for example, Product may be available only to Corporate customers, or Pricing may differ based on Customer Risk).

Copyright © 2021-2022. Cloud Software Group, Inc. All Rights Reserved.