Product Bundling

Products are on-boarded and wrapped as a “service package”. Service packages include definitions on application SLA, service dependencies, virtual server parameters, and more. A single application can be wrapped multiple times in different service packages to address different SLAs. The process of creating a service package out of an application should be done by a technical person with understanding of computing resource impacts on application performance and service dependencies.

After service packages have been created, product managers can turn them into “Products”. Products are a one-to-one mapping between service packages, and include all of the business-related definitions, including parameters such as a Billing-ID, portal-display parameters, associated product-catalog icons, and more. A single service-package can be wrapped as multiple products.

A product also contains other marketing parameters, such as add-on definitions (lists of products which can be “added” to this one for enhanced value) as well as upgrade / downgrade paths. Once the products are created, the product managers can create bundles of products. Bundles can also contain product add-on definitions and upgrade/downgrade paths. Once products and bundles have been created, they can then be assigned to individual customers. A single customer can have multiple products and multiple bundles assigned to them.

NOTE: Reseller and channel partners can participate in all levels of the service-delivery hierarchy, or they can accept product definitions that have been “pushed-down” from their parent.