Shared Information Data (SID) Model

(1)

Shared Information/Data

(SID) Model

Addendum 3 - Product Business Entity Definitions

GB922 Addendum- 3

Member Evaluation Version 3.1

NGOSS Release 3.5

July 2003

(2)

(3)

Notice

The TeleManagement Forum (“TM Forum”) has made every effort to ensure that the contents of this document are accurate. However, no liability is accepted for any errors or omissions or for consequences of any use made of this document. This document is a draft working document of TM Forum and is provided to its members solely for formal comments and evaluation. It is not a Forum Approved Document and is solely circulated for the purposes of assisting TM Forum in the preparation of a final document in furtherance of the aims and mission of TM Forum. Any use of this document by the recipient is at its own risk. Under no circumstances will TM Forum be liable for direct or indirect damages or any costs or losses resulting from the use of this document by the recipient.

Members of TM Forum are granted limited copyright waiver to distribute this document within their companies. They may not make paper or electronic copies for distribution outside their companies. The only purpose of the provision of this draft document to members is for making formal comments thereon to TM Forum.

This document may involve a claim of patent rights by one or more TM Forum members, pursuant to the agreement on Intellectual Property Rights between TM Forum and its members, and by non-members of TM Forum.

Direct inquiries to the TM Forum office: 89 Headquarters Plaza North

Suite 350

Morristown, NJ 07960-6628 USA Tel No: +1.973.292.1901

Fax No: +1.973.993.3131

(4)

Acknowledgments

This document was prepared by the members of the TeleManagement Forum SID team:

The Shared Information/Data Model is a genuinely collaborative effort. The TM Forum would like to thank the following people for contributing their time and expertise to the production of this document. It is just not possible to recognize all the organizations and individuals that have contributed or influenced the introduction. We apologize to any person or organization we inadvertently missed in these acknowledgments.

Key individuals that reviewed, provided input, managed, and determined how to utilize inputs coming from all over the world, and really made this document happen were:

Name Affiliation

Cliff Faurer TeleManagement Forum

Chris Hartley Telstra

Helen Hepburn British Telecom

John Reilly MetaSolv Software

Wayne Sigley Telstra

John Strassner Intelliden

Johan Lindblahd Ki Consulting

(5)

About TeleManagement Forum

TeleManagement Forum is an international consortium of communications service providers and their suppliers. Its mission is to help service providers and network operators automate their business processes in a cost- and time-effective way. Specifically, the work of the TM Forum includes:

Establishing operational guidance on the shape of business processes. Agreeing on information that needs to flow from one process activity to another.

Identifying a realistic systems environment to support the interconnection of operational support systems.

Enabling the development of a market and real products for integrating and automating telecom operations processes.

The members of TM Forum include service providers, network operators and suppliers of equipment and software to the communications industry. With that combination of buyers and suppliers of operational support systems, TM Forum is able to achieve results in a pragmatic way that leads to product offerings (from member companies) as well as paper specifications.

(6)

About this document

This is a TM Forum Guidebook. The guidebook format is used when:

The document lays out a ‘core’ part of TM Forum’s approach to automating business processes. Such guidebooks would include the Telecom Operations Map and the Technology Integration Map, but not the detailed specifications that are developed in support of the approach. Information about TM Forum policy, or goals or programs is provided, such as the Strategic Plan or Operating Plan.

Information about the marketplace is provided, as in the report on the size of the OSS market.

Document Life Cycle

This document is being issued for Member Evaluation. The purpose of an Evaluation Version is to encourage input based on experience of members and the public as they begin to use the document. Following the Evaluation Period, documents that are seen to deliver value are candidates for formal approval by the TM Forum. All documents approved by the TM Forum undergo a formal review and approval process.

This document will continue under formal change control. Supporting work will be issued as companions to this document. A document of this type is a “living document,” capturing and communicating current knowledge and practices. Further inputs will be made because of detailed work ongoing in the TM Forum and the industry.

Document History

Version Date Purpose

0.1 Jan 2002 GB915 Addendum Template created from TMF407

v1.1 Guidebook template

Feb 2002 TAW - updated diagrams & minor changes

0.5 May 2002 Change to Product Offering and Product (Instance) agreed on team calls. General changes resulting from Telstra comments including Version.

(7)

Version Date Purpose

1.1 Sept 2002 Phase II updates.

1.2 Sept 2002 Updates based on team review.

3.0 May 2003 Added Product Pricing, updated association and attribute names.

3.1 July 2003 Formatted for Member Review with NGOSS R3.5

Time Stamp

This version of this document can be considered valid until December 2003, by which time it will be updated or reissued.

How to obtain a copy

An electronic copy of this document can be downloaded at the TM Forum Web Site (www.tmforum.org) at Publications or through a link to Publications from a specific team’s public project area.

If the document version has only been released to members for review and comment, the document can only be downloaded from the TM Forum Web Site in the Members Only Area. Depending upon the document, it could be accessible from New Items, Evaluation Versions, or a team’s Members Only project area. If you would like a paper version of this document, please order via the TM Forum Web Site or contact the TM Forum office. If you are not a member, please contact the TM Forum office on +1.973.292.1901.

How to comment on the document

Comments must be in written form and addressed to the SID team leaders and TMF staff sponsor for review with the project team. Please send your comments to the contacts shown below:

John Reilly [email protected] +1 972-403-8408

John Strassner [email protected] +1 719-785-0648

Cliff Faurer [email protected] +1 303-367-1443

(8)

(9)

Table of Figures

Figure Pr.1 – Primary Product Domain Business Entities 2 Figure Pr.2 – Product, Service, Resource Domain Relationships 3

Figure Pr.3 - Product Specification – Basic Entities 5

Figure Pr.4 - Product Specification - Characteristics and Versions 7

Figure Pr.5 - Product Offering - Basic Entities 9

Figure Pr.6 Product Offering Terms 11

Figure Pr.7 - Product Entities 13

Figure Pr.8 – Product Offering Price 15

Figure Pr.9 – Product Offering Price’s Associations With Other Business Entities 16

Figure Pr.10 – Product Offering Price Components 17

Figure Pr.11 – Types of Product Offering Price Charges 19 Figure Pr.12 – Types of Product Offering Price Adjustments 21

(12)

Business Entities

PRODUCT Domain

Introduction

In looking at ‘Product’ for the SID model, the modelers used SIM Product domain as the basis. The key concepts that were looked at were the detailed specification of products (product specifications); the way in which they are offered into the market (product offerings); and the way in which they are maintained and perform while in use (products). The SID model reflects product entities from a business-oriented point-of-view and uses the best of standard modeling patterns for this area.

Overview of ‘Product’

This section outlines the approach taken to distinct parts of the SID model. An overview of how the main product domain business entities are related is shown in the figure below. This model is developed as we work through this document.

(13)

ProductSpecification

(from Product Specifi catio n A BE)

0..n 0..n

0..n

ProdSpecReferences

0..n

ProductOffering

(from Product Offering ABE)

1 0..n 1 0..n ProdSpecMadeAvailableAs Product

(from Product ABE)

1 0..1 1 0..1 ProdOfferDescribes 0..n 0..n 0..n ProductReferences 0..n

Figure Pr.1 – Primary Product Domain Business Entities

The Product domain is essential to the overall SID model. Customers need to be able to express their needs in plain English in order to determine which product offerings can support their requirements and Service Providers need to be able to match these requirements to technical specifications to realize the product offering. Product offering represents what is externally presented to the market for the market’s use. Product offerings are assembled from reusable product specifications (sometimes referred to as a product spec). For example, an email specification may be used in a number of different product offerings. A single product offering, such as home-based internet service, may represent the aggregation of internet connection, email service, and web hosting product specifications. A product represents the subscription of a product offering by a party. For example, Helen H. subscription to an internet product offering.

(14)

Business entities in the Product domain have a close relationship with business entities in the Service and Resource domains. While Product business entities represent what the market sees of a provider’s offerings, service and resource business entities represent the realization of the offerings from a provider’s perspective. The figure below depicts the relationship among Product, Service, and Resource domain business entities.

ServiceUtilizes CustomerFacingService Product 0..n 0..n 0..n ProductReferences 0..n 0..1 0..n 0..1 0..n ProductHasCustomerFacingServices ResourceFacingService 0..n 1..n 0..n 1..n CFServiceRequiresRFServices ServiceSpecification 0..n 0..n 0..n InvolvedServiceSpecs 0..n Service 1 0..n 1 0..n SpecifiesService ProductOffering 1 0..n 1 0..n ProdOfferDescribes CustomerFacing ServiceSpec 1 0..n 1 0..n SpecifiesCustomerFacingService PhysicalResourceSpec ProductSpecification 0..n 0..n 0..n 0..n ProdSpecReferences 1 0..n 1 0..n ProdSpecMadeAvailableAs 0..n 0..n 0..n 0..n ProductSpecDefinesCFSSpecs 0..n 0..n 0..n 0..n ProductSpecDefinesPRSpecs Resource 0..n 0..n 0..n 0..n ResourceSpecification 0..n 0..n 0..n 0..n InvolvedResourceSpecs 1 0..n 1 0..n SpecifiesResource ResourceFacing ServiceSpec 1 0..n 1 0..n SpecifiesResourceFacingService 0..n 1..n 0..n 1..n RequiresResourceFacingServiceSpec 1 1..n 1 1..n RFServiceSpecHasResourceSpecs

Figure Pr.2 – Product, Service, Resource Domain Relationships

Business entities within the Product domain are also involved in business interactions (see Business Interaction Addendum 1BI).

(15)

Product/Product Specification

Products are things (tangible or intangible) which enterprises, such as service providers, market, sell or lease to customers to create profit. In a changing world, monopoly telcos with a custom-built portfolio have been replaced by a value network [eTOM] of Suppliers and Service Providers offering complex communications-based Products. The way in which those Products have to be specified is not as simple as it used to be.

A product specification may be simple or a composition of simple product Specifications [Fowler-Specification]. A product specification may represent a tangible object or something intangible provided to customers, realized as a ‘service’ but not to be confused with a network service here. The SID modeling of a composite product specification covers both the physical build of more than one product specification and one or more product specifications supplied together in a collection. In addition, a composite product specification may consist of other product specifications that are sold separately in their own right, or of simple product specifications that are only for sale as part of the aforementioned product specification. Product specifications may also exist within groupings, i.e. product categories or product lines or product types.

Enterprises may assemble products themselves or they may buy them in from other suppliers (through contractual agreements where the enterprise takes the role of customer - see SID Agreement addendum 1A); or they may do a combination of these things.

Product Specification Example - The "3G Mobile super saver pack"

This is sold via intermediaries ("Dog-n-Bones-R-Us" phone shops) as a "BigTelephone" branded product. Nokia supply the phones and give a 2-year guarantee. The "BigTelephone" network is used for voice and they supply a phone number and a SIM card. The SMS function is provided by "Best Messaging”, as "BigTelephone" doesn't have an SMS function. The customer signs the contract with "BigTelephone" for 2 years with minimum monthly calls and BT bill the customer direct. BT has a separate contract with “Best Messaging” to cover the use of their SMS function. In looking at the detail of Product

Specification , the following concepts are modeled by the structure in Fig. 2 below:

Relationships between different product specifications for bundling or composite specifications;

• • • •

Different attributes for different types of product specification, e.g. some products the customer can take home with them, others they experience as a service, e.g. one delivered across a network;

Simple product specifications which cannot be broken down further.

Composite product specifications which comprise a number of other product specifications, any of which may provide more than one instance per composite product specification.

(16)

ProductSpecification Relationship type : Integer validFor : TimePeriod AtomicProductSpecification ProductSpecificationType type description ProductSpecificationCost cos tToBusiness : Money validFor : TimePeriod CompositeProductSpecific ation ProductSpecification name : String description : String productNumber : String brand : String validFor : TimePeriod lifecycleStatus : Integer 1 0... 1 0... ProdSpecTypeCategorizes 0..n 0..n 0..n ProdSpecReferences 0..n 1 0..n 1 0..n ProdSpecDevelopmentIncurs 0..n 0..n 0..n 0..n ProdSpecCompositeComprisedOf

Figure Pr.3 - Product Specification – Basic Entities

In all combinations of products, there must be clearly defined relationships between the products in order to ensure consistency of service to the customer. Some examples of such product specification relationships would be migration, exclusivity, dependency and substitution, as indicated in Figure Pr.3 above.

There are also costs associated with creating, developing and maintaining a product and the enterprises records these against the product specification. There is an implied link between the product specification cost entity and business information but this has not been explored in this area of the SID model.

(17)

Product Characteristics

Product specifications also have a variety of characteristics, such as a printer’s dimensions, paper capacity, print speed, color, and so forth, and possible values associated with the characteristics. SID uses Product Specification Characteristic Value and Product Characteristic for Product Specification [Fowler-Properties] as shown in Figure Pr.4 on the following page.

Characteristics can be grouped into three different types:

• If a characteristic has a discrete value (e.g. color or business coding), it may be derived from a range of allowable values; • If a characteristic describes the product within a parameter range (e.g. dimension), it may be defined with a ‘high value’

and a ‘low value’ [Fowler-Range] ;

• If a characteristic value is ‘derived’, it will use other parameters in a formula. N.B. There are business rules implied here that require more work in the next phase of the SID Product definition.

As product specifications are upgraded, as the market and technology move on, they are subject to version control. If there is a significant change of capabilities, a new product specification is created; if the existing characteristics are revised in a way that doesn’t affect the product offering, then a new version can be created. A product specification may have a number of different versions that represent minor revisions relating to characteristics, cost and so forth. A description of the revisions is captured as an attribute of product version.

When a product offering is created for a product specification (see Product Offering below), the party may also have the option to choose from a set of properties values, such as color, or may be able to choose one from a number of product properties. Where a product specification characteristic is interchangeable with others in this way, it is modeled as a configurable product specification characteristic.

(18)

ProductSpecificationVersion prodSpecRevisionType prodSpecRevisionNumber description prodSpecRevisionDate validFor ConfigurableProductSpecCharacteristic ProductSpecCharacteristic name description 0..n _0..n 0..n ProdSpecCharacteristicReferences 0..n ProductSpecCharacteristicValue prodSpecCharValueType prodSpecCharValue prodSpecCharValueFrom prodSpecCharValueTo validFor 1 0..n 1 0..n ProdSpecCharacteristicTakesOn ProductSpecification 0..n 0..n 0..n 0..n ProdSpecCharacteristicDescri bes 0..n 0..n 0..n 0..n ProdSpecDescribedBy 1 0..n 1 0..n ProdSpecModificationsRecordedAs

(19)

Product/Product Offering

Product offerings are targeted at one or more market segments based on the appropriate market strategy. Enterprises create product offerings from product specifications that have additional market led details applied over a particular period of time. The product offering may also be defined by the location(s) at which it is available. Locations in the SID model are represented by the Location/Place business entity. The customers do not need to know anything about the detailed product specification as the enterprise tailors the product offering to their needs.

Where a business market strategy dictates, product offerings may be bundled together and re-priced as necessary. In addition, the time period for a bundled product offering will depend upon those for its component offerings.

An enterprise puts product offerings into the marketplace by developing and maintaining a catalog of product offerings across one or more (market) distribution channels, e.g. a catalog on a website and a glossy brochure have different attributes and may also contain different sets of product offerings. The product offerings set out in the product catalog are product specifications with additional details that enable a contract to be struck for their sale/purchase. This includes not only the product characteristics but also other product-dependent details, such as SLA parameters, invoicing and shipping details.

There are typically a number of product offerings associated with a single product specification, for example to reflect offers to the market for different time periods. In cases where a product specification’s value to the business is solely as a component part of a composite product specification, it does not have a product offering associated with it as it is not be sold on its own. Cases where these items are supplied to the customer separately as ‘spares’, e.g. under warranty, are covered under Product below.

When customers select products from the product catalog, it is the product offering details that they are looking at and which are reflected in what they agree to contractually.

(20)

SimpleProductOffering ProductOfferingPrice name description validFor : TimePeriod BundledProductOffering ProductSpecification

(from Product Spe cificati on ABE)

MarketStrategy

(from M arket S trat egy & Pl an ABE) MarketSegment

(f rom Market S egment A BE) DistributionChannel

(from Sales Channel ABE) 0..n0..n ProdCatalogAvailab leVia 0..n0..n ProductCatalog

ProductOffering id name des cription validFor : TimePeriod status 0..n 0..n 0..n 0..n ProdOfferValuedByPrice 0..n 0..n 0..n 0..n BundledProdOfferComprisedOf 1 0..n 1 0..n

ProdSpecMad eAvailab leAs 0..n 0..n 0..n 0..n ProdOfferingProvidedBy 0..n 0..n 0..n 0..n ProdOfferingSupportedBy 0..n 0..n 0..n 0..n ProdOfferingTarge tedTo 0..n 0..n 0..n 0..n ProdOfferingPub licizedIn Place

(f rom Entit ies)

0..n

0..n 0..n

0..n ProdOfferingAvailableIn

Figure Pr.5 - Product Offering - Basic Entities

Product Offering Example

Smooth Telco normally markets a range of mobile phones as individual items. For a limited period around February 14th_{, it}

decides to market one model with a special red cover, boxed in pairs and accompanied by two champagne glasses. As an added attraction, the deal includes a discount for calls made between the telephone numbers allocated to each pair for a set period. It is a huge success and likely to be repeated the following year when a new product offering with the new valid time period will be created. These product offerings exist side by side with the standard product offering for the mobile phone model when the phones are sold individually.

(21)

Product Offering Terms

The product offering is primarily the way to position products in the marketplace to create profit; the amount of profit depends upon both the original pricing of the product and the eventual terms of the sales agreements struck for that product offering. The product offering price is based on both the basic cost to develop and produce products (see Product Specification) and the enterprise’s policy on revenue targets. The pricing policy mechanism is represented in this model by ‘term’. Terms are the conditions under which the product is offered to customers and product finance term is only one of many which may come into play. In addition to a definition of the list price, financial terms may also include acceptable methods of payment for this type of product. As examples of other types of Product term, the SID model also includes product service term and product shipment term.

When a price has been created, it will appear as the list price for product offering in the product catalog. For a simple product offering, this may also be the effective list price but, if product offerings are bundled together, the overall price will not necessarily be the combination of component list prices and pricing policy will be required. The customer will refer to the list price in selecting a product but, depending upon their relationship (e.g. account) with the enterprise offering the product, this price may be further revised through discounting, such as for bulk buying, loyalty and so forth. This is modeled through agreement term.

(22)

AgreementItem

(f rom Agreement ABE)

Agreement

1 0..n 1 0..n AgreementConsistsOf AgreementTermOrCondition

0..n 0..n 0..n 0..n AgreementItemGovernedBy 1 0..n 1 0..n AgreementGovernedBy BusinessInteractionItem

(from Business Interaction ABE)

ProductOfferingTerm 0..n 0..n 0..n 0..n Agreem entTermOrConditionRealizedVia ProductOffering 0..1 0..n 0..1 0..n

BusinssI nteractionItem InvolvesProductOffering

0..n

0..n 0..n

0..n

ProdOfferAgreementRequirementsRepresentedAs

(23)

Product/Product

When the customer makes a selection, they may also have a number of options to select from. These are associated with the Product Offering and modeled in Product Configured (see Figure Pr.6 below), which defines the product delivered to the customer (see Product below). The Product Configured comprises the detail of the Product Configured Properties selected by the customer.

When an enterprise agrees to deliver a product to a customer, there is a significant amount of information that needs to be recorded to implement that product on the provider’s infrastructure or resources and to activate the Service. This is modeled in Product and associated entities below.

(24)

ProductComponent ProductSpecCharac teristicValue

(from Product Specification ABE)

ProductSpecCharacteristic

(from Product Specification ABE)

ProductOffering

(f ro m P rod uct Off erin g A BE)

ProductBundle ProductCharacteristic productCharacteristicValue validFor 0..1 0..n 0..1 0..n ProdSpecCharValueInstantiatedAsProductCharacteristic 0..1 0..n 0..1 0..n

ProdSpecCh arDescrib esProdChara cteristic

ProductInvolvementRole productInvolvementRole validFor Product name description productStatus productSerialNumber validFor : TimePeriod 1 0..n 1 0..n ProdOfferDescrib es 0..1 0..n 0..1 0..n ProductBundleComprisedOf 0..n 0..n 0..n ProductReferences 0..n 0..n 1 0..n ProdCharDefinesTheConfigurationOf 1 0..n0..n ProductOfInterestTo 0..n0..n Place (from Entities) 0..n 0..n 0..n 0..n ProductLocatedVia PartyRoleProductInvolvement

(f rom Product ABE)

PartyRole (f rom Rol es ) 0..n 1 0..n 1 PartyRolePlays ResourceRoleProductInvolvement

(f rom P roduc t ABE )

ResourceRole

(from Resource Entities)

0..n

1 0..n

1

ResourceRolePlays

Figure Pr.7 - Product Entities

Product offerings may be obtained by the customer in a number of ways: some products are equipment obtained directly into the possession of the customer but some are services provided across the provider’s resources and which the customer accesses and uses, rather than owns. In some cases, a provider may give the customer access to a product resident on a third party’s resources. Where a third-party product is involved, it may be branded/badged as coming from another provider or it may be re-branded/badged as the first provider’s product. Whichever of these is applicable, once the customer is using the product, we are talking about a realization of the Product offering that is based on a standard Product Specification. We are also talking about the user/recipient who is entitled to use the product. This is represented by the ProductInvolvementRole business entity and it’s productInvolvementRole attribute. The product that the customer has obtained is not truly realized until it is in use. The user may be the signatory to an agreement, particularly if the customer is an Individual, but they may also be an agent or employee of the customer where that customer is a large organization.

(25)

Product/Product Offering/Product Offering Price

Note: This model has not been validated against requirements of a Billing application. The Product Price Model presented here has been constructed using Order Fulfillment use cases. A future phase of the SID project will incorporate Billing use case support in this model.

The price of a product offering or a bundle may be simple or quite complex. A simple price could be the charge associated with the monthly rental of a cable modem. Or, a price could encompass many different components. A typical introductory wireless offering, for example, will have an activation cost, a monthly cost, a number of free minutes, a cost for extra minutes, and some sort of promotional component. It might also include a corporate discount for business users. Each of these elements must be described in order to paint an accurate picture of the overall price charged for any product offering.

This part of the SID model presents a set of components that can be combined to offer a complete and accurate description of the price charged for an offering. A secondary consideration is to define those components in such a way that they can be readily implemented in a typical billing system.

A product offering may have any number of prices, each of which is made up of a single component or a composite of a number of components. The Product Offering Price model employs the composite/component modeling pattern used throughout the SID to represent simple and complex prices, as illustrated in the figure below.

(26)

ComponentProdOfferPrice priceType quantity : Quantity currencyType CompositeProdOfferPrice ProductOffering

(f rom Product Of f ering ABE)

ProductOfferingPrice name description validFor : TimePeriod 0..n 0..n 0..n 0..n CompositeProdOfferPriceComprisedOf 0..n 0..n 0..n 0..n ProdOfferValuedByPrice PriceEvent 0..n 0..n ComponentProdOfferPriceGovernedBy 0..n 0..n

Figure Pr.8 – Product Offering Price

Figure Pr.P1 also shows an association between ProductOfferingPrice and PriceEvent. The PriceEvent business entity represents an occurrence (happening) or schedule that triggers the creation of a billing charge for a product offering. For example, a price event instance may represent the end of a month when monthly recurring billing charges are created. In some cases, the creation of a charge associated with a ProductOfferingPrice may be triggered by multiple events. For example, a penalty (ProductOfferingPrice) may be triggered by over- or under-usage of a service. Under- and over-usage are represented as two separate PriceEvent entity instances.

(27)

The price paid for a product offering may appear in ProductCatalogs, may be offered via certain DistributionChannels, or in certain GeographicAreas. The figure below depicts the associations a ProductOfferingPrice has with these business entities.

ProdCatalogProdOffer + validFor : Tim ePeriod

Geographic Area

(f rom Geographic Place)

DistributionChannel

(f rom Sales Channel ABE) ProductOfferingPrice name description validFor : TimePeriod 0..n 0..n 0..n 0..n ProdOfferPriceAvailableIn 0..n 0..n 0..n 0..n ProdOfferPriceMadeAvailableVia 0..n 1 0..n 1 ProdOfferPri ceAdvertisedAs Produ ctCatalog

ProductOffering

(f rom Produc t Of f ering ABE)

0..n 0..n 0..n 0..n ProdOfferValuedByPrice 0..n 0..n 0..n ProdOfferingPublicizedIn 0..n

Figure Pr.9 – Product Offering Price’s Associations With Other Business Entities

Each component of a ProductOfferingPrice can take on one of two forms. A component may represent the amount charged to a party playing a role. For example, a monthly internet connection fee. Or, a component may represent an adjustment

(28)

that will be made to the amount charged. For example, an installation allowance of $49.95 to the first month’s bill, which offsets an installation charge. The figure below depicts the two types of component product offering prices.

CompositeProdOfferPrice

ComponentProdOfferPrice

priceType qua ntity : Quantity cu rrencyType ProductOffering

PriceEvent ProductOfferingPrice name description validFor : TimePeriod 0..n 0..n 0..n 0..n ProdOfferValuedByPrice 0..n 0..n 0..n 0..n CompositeProdOfferPriceComprisedOf 0..n 0..n _0..n 0..n ComponentProdOfferPriceGovernedBy ProdOfferPriceAlteration ProdOfferPri ceCharge _0..n_0..n ProdOfferPriceChargeImpactedBy _0..n_0..n

(29)

Charges incurred for a product offering can take many different forms, such as

• Recurring Charge – A recurring charge is levied repeatedly. It has a period, such as monthly, quarterly, or yearly. An example would be a monthly charge for long distance.

• One Time Charge – A one time charge is levied once. An example is the cost of a cell phone handset. • Fee – A particular type of one time charge, such as an activation fee or installation fee.

• Usage – A charge levied for usage, based on measuring events. This model distinguishes between simple usage and usage where the charge is described by a tariff.

• Simple Usage – Simple usage describes a rate where the charge is the same for all events. A 10 cents a minute for long distance plan is one example.

• Tariff Usage – Tariff usage describes a rate where there are different charges for different types of events. This could include plans, which have different prices for evening minutes and anytime minutes. This usage aggregates a number of simple usages.

• Alternate Price Charge – A price charged in lieu of another price. For example, purchasing two of a single product offering may result in a discounted price for both.

A representative set of these types of charges is shown in the figure below. The set by no means represents the complete set of charges that can be incurred for a product offering. The Product Price Model provides a framework into which other types of charges can easily fit.

(30)

ComponentProdOfferPrice priceType quantity : Quantity currencyType OneTimeChargeProdOfferPriceCharge SimpleUsageProdOfferPriceCharge RecurringChargeProdOfferPriceCharge TariffUsageProdOfferPriceCharge ProdOfferPriceAlte ration AlternateProdOfferPriceCharge ProdOfferPriceCharge 0..n 0..n 0..n 0..n AlternatePriceChargeAppliedInLieuOf

(31)

Similarly, alterations made to charge(s) incurred for a ProductOffering can take many different forms, such as

• Discount – A discount is a reduction in price. It could be a flat fee such as 10 dollars or a percentage, such as 50% off. A discount always applies to, and thus is associated with, one or more other ProdOfferPriceComponents. So a discount would be 10 dollars off the installation fee or 50% off the per-minute rate.

• Allowance – An allowance is a number of something allowed before charging begins. 300 free minutes per month is an example of an allowance. Another example would be a minimum monthly charge, where a ten dollar per month recurring charge would be combined with a ten dollar allowance. The product offer price contains attributes that describe what the allowed unit is (i.e. minutes, dollars), the number of units as well as the period (per month, per call). Note: the unit and number are represented by the composite attribute quantity.

A representative set of these types of allowances is shown in the figure below. The set by no means represents the complete set of allowances for a product offering. The Product Price Model provides a framework into which other types of allowances can, like charges, easily fit.

(32)

ComponentProdOfferPrice priceType quantity : Quantity currencyType ProdOfferPriceCharge ProdOfferPriceAlteration DiscountProdOfferPriceAlteration AllowanceProdOfferiPriceAlteration

Figure Pr.12 – Types of Product Offering Price Adjustments

Putting charges and allowances in a single example provides a complete view of a product offering price. A simple wireless plan includes a 75 dollar phone, a 50 dollar activation fee, a 20 dollar monthly charge, 250 free local minutes per month, 10 cents a minute for additional minutes, and 25 cents a minute long distance. The components are

• A 75 dollar One Time Charge (charge) • A 50 dollar Fee (charge)

• A 20 dollar Recurring Charge per month (charge)

(33)

• An Allowance of 250 minutes (adjustment)

Adding on to the example, suppose Sue is an employee of a company, which has a volume discount agreement with the service provider. The agreement is to waive the installation fee and provide a 20 percent discount on local minutes. This would manifest itself as:

• A composite price that associated the 50 dollar Discount with the 50 dollar Fee

• A composite price that associated the 20 percent Discount with the 10 cent per minute Simple Usage

(34)

ComponentProdOfferPrice priceType quantity : Quantity currencyType DiscountProdOfferPrice Alteration OneTimeChargeProdOfferPriceCharge Recurring Ch argeProdOfferPriceCharge

SimpleUsageProdOfferPriceCharge TariffUsageProdOfferPriceCharge

AllowanceProdOfferiPrice Alteratio n Charge and Adj ustmen t

subclasses shown here are illustrative only and, as such, do not represent al l the p ossib le types of charges and adju stm ents that can exi st.

AlternateProdOfferPriceCharge ProdOfferPriceCharge 0..n 0..n 0..n 0..n

AlternatePriceChargeApplie dInLieuOf 0..n0..n ProdOfferPriceChargeImpactedBy 0..n0..n ProdOfferPriceAlteration

CompositeProdOfferPrice

DistributionChannel

(f rom Sales Channel ABE)

PriceEvent ProdCatalogProdOffer

(f rom Produc t Off ering Price ABE )

Geographic Area

(f rom Geographic Place)

ProductOfferingPrice

name descrip tion validFor : Time Period 0..n 0..n 0..n 0..n CompositeProdOfferPriceComprisedOf 0..n 0..n 0..n 0..n ProdOfferPriceMadeAvailableVia 0..n 0..n 0..n 0..n ComponentProdOfferPriceGovernedBy 1 0..n 1 0..n ProdOfferPriceAdvertisedAs 0..n 0..n 0..n 0..n ProdOfferPriceAvailab leIn ProductOffering

(f rom P roduc t Off ering AB E)

0..n 0..n 0..n 0..n ProdOfferValuedByPrice ProductCatalog

0..n 0..n

ProdOfferingPublicizedIn

(35)

References

Fowler-AP Analysis Patterns – Reusable Object Models by Martin Fowler ISBN 0-201-89542-0 http://martinfowler.com/articles.html Fowler-Time Patterns for things that change with time

http://martinfowler.com/ap2/timeNarrative.html Fowler-Properties Dealing with Properties by Martin Fowler

http://www.martinfowler.com/apsupp/properties.pdf Fowler-Range Range http://martinfowler.com/ap2/range.html

Fowler-Specification

ACIA Alliance Common Information Architecture (AT&T, BT & Concert) version 3.1, 15 Dec 2000

eTOM GB921 version 2.5

Metasolv Sales & Marketing Business Objects Document for TMF Larman Applying UML and Patterns, Second Edition

ISBN 0-13-095004-1

http://www.craiglarman.com/book_applying_2nd/Applying_2nd.htm Arsanjani Service Provider: A Domain Pattern and its Business Framework

Implementation

http://st-www.cs.uiuc.edu/~plop/plop99/proceedings/Arsanjani/provider3.pdf Hay Advanced Data Model Patterns by David Hay

(36)

Product Specification

Business Entity Definition

Business

Entity Name

ProductSpecification

Description A detailed description of a tangible or intangible object made available externally in the form of a ProductOffering to Customers or other Parties playing a PartyRole. A ProductSpecification may consist of other ProductSpecifications supplied together as a collection. Members of the collection may be offered in their own right. ProductSpecifications may also exist within groupings, such as ProductCategories, ProductLines, and ProductTypes.

Sources ACIA, MetaSolv, Fowler Cross-

References Synonyms / Aliases ProductTemplate, ProductSpec

Related Business Entities groupedBy ProductCatagory bundledInto CompositeProductSpecification involvedWith ProductSpecification incurs ProductSpecCost madeAvailableToTheMarketAs ProductOffering Business Rules

Business Entity Attributes Definition

Business Entity

Name

ProductSpecification

Attribute Name Description Data Type Characteristics

, Permitted Values & Units

Required/

Optional Notes

name The name of the product

specification. Required

description A narrative that explains in detail what the product spec is.

Required

productNumber An identification number assigned

to uniquely identify the specification. Required brand/Badge The manufacturer or trademark of

the specification. Optional validFor The period for which the product

specification is valid. Time Period Required lifeCycleStatus The condition of the product

specification, such as active, inactive, planned.

(37)

Composite Product Specification

Business Entity Definition

Business

Entity Name

CompositeProductSpecification

Description A type of ProductSpecification that is formed by aggregating other ProductSpecifications, which may be Composite or Atomic ProductSpecifications.

Sources ACIA Cross-

References Synonyms / Aliases

Related Business Entities Subclass of ProductSpecification Business Rules

Atomic Product Specification

Business Entity Definition

Business

Entity Name

AtomicProduct Specification

Description A type of ProductSpecification that does not have any subordinate ProductSpecifications, that is, an AtomicProductSpecification is a leaf-level ProductSpecification.

Sources SID team Cross-

References Synonyms / Aliases Related Business Entities Subclass of ProductSpecification Business Rules

(38)

Product Specification Relationship

Business Entity Definition

Business

Entity Name

ProductSpecificationRelationship

Description A migration, substitution, dependency, or exclusivity relationship between/among ProductSpecifications.

Sources ACIA, MetaSolv Cross-

Related Business Entities definesAssociationsBetween ProductSpecification governedBy ProductSpecificationRelationshipPolicy Business Rules

Business Entity Attributes Definition

Business Entity

Name

ProductSpecificationRelationship

Attribute Name Description Data Type Characteristics,

Permitted Values & Units

Required/

type A categorization of the relationship, such as migration, substitution, dependency, exclusivity.

Required

validFor The period for which the relationship is

(39)

Product Specification Cost

Business Entity Definition

Business

Entity Name

ProductSpecificationCost

Description A monetary amount assigned to a ProductSpecification that represents the cost to the business to plan, develop, market, and implement the ProductSpecification.

Related Business Entities assignsCostValueTo ProductSpecification Business Rules

Business Entity Attributes Definition

Business Entity

Name

ProductSpecificationCost

Required/ Optional

Notes

costToBusiness The monetary amount that represents

the cost. Money Required

validFor The period during which the cost is

(40)

Product Specification Type

Business Entity Definition

Business

Entity Name

ProductSpecificationType

Description A classification that groups ProductSpecifications that share common characteristics.

Related Business Entities categorizes ProductSpecification Business Rules

Business Entity Attributes Definition

Business Entity

Name

ProductSpecificationType

Required/

type The name of the product

specification type. String Required description A narrative that explains in detail

(41)

Product Specification Version

Business Entity Definition

Business

Entity Name

ProductSpecificationVersion

Description A particular form or variety of a ProductSpecification that is different from others or from the original. The form

represents differences in properties that characterize a ProductSpecification, that are not enough to warrant creating a new ProductSpecification.

Sources ACIA, Fowler Cross-

Related Business Entities refinesTheDefintionOf ProductSpecification definedBy ProductSpecProperty Business Rules

Business Entity Attributes Definition

Business Entity

Name

ProductSpecificationVersion

Required/

ProdSpecRevision

Type The significance of the revision. String Major, Minor Required prodSpecRevision

Number

A number that represents the occurrence of the version in the sequence of versions.

Required

description A narrative that explains the reason

for the version’s creation. Optional ProdSpecRevision

Date The date the version was created. Date Required validFor The period during which the version is

applicable.

(42)

Product Specification Characteristic

Business Entity Definition

Business

Entity Name

ProductSpecificationCharacteristic

Description A characteristic quality or distinctive feature of a ProductSpecification. The characteristic can be take on a discrete value, such as color, can take on a range of values, (for example, sensitivity of 100-240 mV), or can be derived from a formula (for example, usage time (hrs) = 30 – talk time *3). Certain characteristics, such as color, may be configured during the

ordering or some other process.

Sources ACIA, MetaSolv, Fowler Cross- References Synonyms / Aliases ProductSpecificationProperty Related Business Entities takesOn ProductSpecCharacteristicValue references ProductSpecificationCharacteristic Business Rules

Business Entity Attributes Definition

Business Entity Name

_{ProductSpecificationCharacteristic}

Attribute Name Description Data

Type Characteristics, Permitted Values & Units

Required/

Name A word, term, or phrase by which the characteristic is known and distinguished from characteristics.

String Required

(43)

Configurable Product Spec Characteristic

Business Entity Definition

Business

Entity Name

ConfigurableProduct

_{SpecCharacteristic}

Description A type of ProductSpecCharacteristic, such as color, whose may be assigned during the ordering or some other process.

References Synonyms / Aliases ConfigurableProductSpec Property Related Business Entities subclass of ProductSpecCharacteristic Business Rules

(44)

Product Spec Characteristic Value

Business Entity Definition

Business

Entity Name

ProductSpecCharacteristic

_Value

Description A number or text that can be assigned to a ProductSpecCharacteristic.

Sources SID Team Cross-

References Synonyms / Aliases ProductSpecPropertyValue Related Business Entities takenOn by ProductSpecCharacteristic describes ProductSpecification assignedTo Product Business Rules

Business Entity Attributes Definition

Business Entity

Name

ProductSpecCharacterisitic

_Value

Required/

prodSpecCharValue Type

A kind of value that the characteristic can take on.

String Discrete, range derived

Required prodSpecCharValue A discrete value that the

characteristic can take on. String Optional Required if the type is discrete prodSpecCharValue

From The low range value that a characteristic can take on. String Optional One of from or to values required if type is range. prodSpecCharValue

To The upper range value that a characteristic can take on. String Optional One of from or to values required if type is range. validFor The period of time for which a value

is applicable.

(45)

Product Offering

Business Entity Definition

Business

Entity Name

ProductOffering

Description The presentation of one or more ProductSpecifications to the marketplace for sale, rental, or lease for a ProductOfferingPrice. A ProductOffering may target one or more MarketSegments, be included in one or more ProductCatalog, presented in

support of one or more ProductStrategies, and made available in one or more Places. ProductOffering may represent a simple offering of a single ProductSpecification or could represent a bundling of one or more other ProductOffering.

Sources ACIA, MetaSolv, Cross-

Related Business Entities makesAvailable ProductSpecification references ProductOffering bundleInto BundledProductOffering soldAt ProductOfferingPrice targets MarketSegment appearsIn ProductCatalog supports marketStrategy availableIn Place offeredVia DistributionChannel Business Rules

Business Entity Attributes Definition

Business Entity

Name

ProductOffering

Required/

id A unique identifier for the

ProductOffering. Required

name The name of the offering. Required description A narrative that explains what the

offering is.

Optional

validFor The period during which the offering

is applicable. Time Period Required status The condition in which the offering

exists, such as planned, obsolete, active.

(46)

Bundled Product Offering

Business Entity Definition

Business

Entity Name

BundledProductOffering

Description A type of ProductOffering that represents a grouping of ProductOfferings made available to the market. The grouping may consist of other BundledProductOffering(s) or SimpleProductOffering(s).

Related Business Entities comprised of ProductOffering Business Rules

Simple Product Offering

Business Entity Definition

Business

Entity Name

SimpleProductOffering

Description A type of ProductOffering that does not have any subordinate ProductOfferings, that is, an SimpleProductOffering is a leaf-level ProductOffering.

Related Business Entities Business Rules

(47)

Product Catalog

Business Entity Definition

Business

Entity Name

ProductCatalog

Description A list of ProductOfferings for sale, with prices and illustrations, for example in book form or on the web.

ProductCatalogs can be used by Customers during a self-care ordering process and may be used across one or more DistributionChannels.

References Synonyms / Aliases Related Business Entities presents ProductOffering offeredVia DistributionChannel Business Rules

Business Entity Attributes Definition

Business Entity

Name

ProductCatalog

Required/

id A unique identifier for an offering in the catalog.

Required type A categorization of an entry in the

catalog, such as web, book. String Required validFor The period during which the catalog

(48)

Product Offering Price

Business Entity Definition

Business

Entity Name

ProductOfferingPrice

Description An amount, usually of money, that is asked for when a ProductOffering is bought, rented, or leased. The price is valid for a defined period of time and may not represent the actual price paid by a customer.

Sources ACIA, MetaSolv Cross-

Related Business Entities values ProductOffering Business Rules

Business Entity Attributes Definition

Business Entity

Name

ProductOfferingPrice

Required/

type A categorization of the price, such

as list, discounted, lowest allowable String Required price The amount asked for the offering. Money Required

validFor The period during which the price is

(49)

Product Offering Term

Business Entity Definition

Business

Entity Name

ProductOfferingTerm

Description A condition under which a ProductOffering is made available to Customers. ProductOfferingTerm include

ProductOfferingFinancialTerm, which includes such things as acceptable methods of payment, ShipmentTerm, and ServiceTerm.

Related Business Entities specifiesConditionsGoverning ProductOffering appearsAs AgreementTermOrCondition Business Rules

(50)

Product

Business Entity Definition

Business

Entity Name

Product

Description A ProductOffering procured by a Customer, or other interested Party playing a PartyRole, appearing as a

BusinessInteractionItem, which could take the form of a Agreement. ProductSpecificationCharacteristic(s) in part define the Product. A Product is realized as one or more Service(s) and/or Resource(s).

Sources Cross- References Synonyms / Aliases Related Business Entities createdUsing ProductOffering involves BusinessParticipant appearsAs BusinessInteractionItem definedBy ProductCharacteristic realizedAs Service realizedAs Resource Business Rules

Business Entity Attributes Definition

Business Entity

Name

Product

Attribute Name Description Data Type Characteristics

Required/

Name A word, term, or phrase by which the product is known and distinguished from other products.

String Optional

Description An explanation of what the product is. String Optional productSerialNumber _{A set of identifying characters and/or}

numbers assigned to, and usually marked on, each of a series of identical products.

String Optional

productStatus The condition of the product, such as planned, designed, activated,

disconnected.

String Required

validFor The period during which the product is applicable.

Time Period

(51)

Product Bundle

Business Entity Definition

Business

Entity Name

ProductBundle

Description A type of Product that is comprised of other Product(s). The other Product(s) may be ProductBundle(s) or ProductComponent(s).

Related Business Entities comprisedOf Product Business Rules

Product Component

Business Entity Definition

Business

Entity Name

ProductComponent

Description A type of Product that has no subordinate Product(s), that is, a Product Component is a leaf level Product.

References Synonyms / Aliases Related Business Entities Business Rules

(52)

Product Characteristic

Business Entity Definition

Business

Entity Name

ProductCharacteristic

Description A value of a ProductSpecCharacteristic chosen for a Product that further defines what the Product is.

Related Business Entities chosenFor Product describedBy ProductSpecCharacteristic instantiationOf ProductSpecCharacteristicValue Business Rules

Business Entity Attributes Definition

Business Entity

Name

ProductCharacteristic

Required/

productCharacteristic

Value A fact that describes a Product. String Optional Required if the association there is an association with

ProductSpecCharacteristic only.

validFor The period for which the

(53)

Product Involvement Role

Business Entity Definition

Business

Entity Name

ProductInvolementRole

Description A role a Party or Resource plays in the relationship with a Product, such as a user, subscriber, owner, and so forth.

Sources SID team Cross-

Related Business Entities representsTheInvolvementOf BusinessParticipant involves Product Business Rules

Business Entity Attributes Definition

_{ProductInvolvementRole}

Type

Characteristics, Permitted Values & Units

Required/ Optional

Notes

productInvolvementRole A part a Party or Resource plays in its

involvement with a product. String Required validFor The period of time during with the

business participant is involved with the product.

Time

(54)

Party Role Product Involvement

Business Entity Definition

Business

Entity Name

ProductRoleProductInvolvement

Description A PartyRole involved with a Product. The involvement may be a subscriber, lessor, owner, and so forth.

Sources Cross-

Related Business Entities ProductRoleProductInvolvement: PlayedByPartyRole Business Rules

Resource Role Product Involvement

Business Entity Definition

Business

Entity Name

ResourceRoleProductInvolvement

Description A ResourceRole involved with a Product. The involvement may be a subscriber, lessor, and so forth.

Related Business Entities ResourceRoleProductInvolvment: PlayedByResourceRole Business Rules

(55)

Business Entity Definition

Business

Entity Name

ProductOfferingPrice

Description An amount, usually of money, that is asked for or allowed when a ProductOffering is bought, rented, or leased. The price is valid for a defined period of time and may not represent the actual price paid by a customer.

Sources Joule Software model

MetaSolv Software model Cross-References Synonyms / Aliases Related Business Entities ProductOfferingPrice: AppliesTo ProductOffering Advertise As ProdCatalogProdOffer Governed By PriceEvent

Made Available Via DistributionChannel Available In Geographic Area

Business Rules

Business Entity Attributes Definition

Business Entity

Name

ProductOfferingPrice

Required/

name A short descriptive name such as

“affinity discount”. Required description A narrative that explains in detail

the semantics of this component. Optional validFor The period for which the price is

valid.

(56)

Composite Product Offer Price

Business Entity Definition

Business

Entity Name

CompositeProdOfferPrice

Description A ProductOfferingPrice that is made up of parts. The parts may be other CompositeProdOfferPrices or ComponentProdOfferPrices.

MetaSolv model Cross- References Synonyms / Aliases Related Business Entities CompositeProdOfferPrice: Composed Of ProductOfferingPrice Business Rules

(57)

Component Product Offer Price

Business Entity Definition

Business

Entity Name

ComponentProdOfferPrice

Description Part of a ProductOfferingPrice representing a single element of the price. Subclasses further define these elements.

Sources Joule Software model Cross-

Related Business Entities ProdOfferPriceComponent: Defines ProductOfferingPrice Business Rules

Business Entity Attributes Definition

_{ComponentProdOfferPrice}

Type Characteristics, Permitted Values & Units Required/ Optional Notes

PriceType A category that describes the price, such as recurring, discount, allowance, penalty, and so forth.

Required

Quantity A number representing the value of this component and units (such as each) of the price. Its meaning depends on the

priceType. It could be a price, a rate, or a discount.

Quantity Required

(58)

Product Offer Charge

Business Entity Definition

Business

Entity Name

ProdOfferCharge

Description An amount, usually of money, that is asked for when a ProductOffering is bought, rented, or leased.

MetaSolv Software model Cross- References Synonyms / Aliases Related Business Entities ProdOfferCharge: Impacted By ProdOfferAlteration Replaced By AlternateProdOfferCharge Business Rules

Product Offer Price Alteration

Business Entity Definition

Business

Entity Name

ProdOfferPriceAlteration

Description An amount, usually of money, that modifies a price charged for a ProductOffering.

MetaSolv Software model Cross- References Synonyms / Aliases Related Business Entities ProdOfferPriceAlteration: Impacts ProdOfferPriceCharge Business Rules

(59)

Product Catalog Product Offer

Business Entity Definition

Business

Entity Name

ProdCatalogProdOffer

Description The appearance of a ProductOffering in a ProductCatalog.

Related Business Entities

ProductCatalogProductOffer:

PublicationOf ProductOffering in ProductCatalog

Business Rules

Business Entity Attributes Definition

Business Entity

Name

ProdCatalogProdOffer

Required/

validFor The period during which the ProductOffering appears in the ProductCatalog.

Shared Information Data (SID) Model