|Oracle® Communications Data Model Operations Guide
11g Release 1 (11.2)
Part Number E15883-01
This chapter provides an overview of how you customize Oracle Communications Data Model and provides an example of modifying the logical model. It contains the following topics:
See also:Business use cases in Oracle Communication Data Model Reference.
Perform fit-gap analysis as described in "Performing Fit-Gap Analysis".
In a development environment, install an Oracle Communications Data Model instance.
Working in the copy you created in Step 2 and following the documentation you created when performing your fit-gap analysis, customize Oracle Communications Data Model by making changes to its components. Document all of your changes. Make the changes in the following order:
Logical to physical mappings
Physical model. To determine which changes to make and the order in which to make these changes, determine dependences among objects by using the Metadata Browser.
Intra-ETL. Keep in mind the issues discussed in Chapter 3, "Populating an Oracle Communications Data Model Warehouse".
In a test environment, make a copy of your customized version of Oracle Communications Data Model.
In the test environment, following the documentation you created in Step 3, test the customized version of Oracle Communications Data Model.
Roll the final customized version of Oracle Communications Data Model out into production.
Fit-gap analysis is where you compare your information needs and communication business requirements with the structure that is available "out of the box" with Oracle Communications Data Model. You identify any required functionality that is not included in the default schema, as well as other modifications that are necessary to meet your requirements.
The result of your fit-gap analysis is a customization report which is a brief explanation of the adaptations and adjustments required to customize Oracle Communications Data Model to fit your communication environment.
Note:Fit-gap analysis is a major undertaking, and normally requires a team performing multiple evaluations.
To perform the actual analysis your evaluation team takes the following steps:
If previous evaluations have been performed, review the documentation from the previous phases, and if necessary add team members with the needed business and technical expertise.
Meet to review the data and map it into Oracle Communications Data Model's schema. In other words, perform a comprehensive analysis of all of the source data in your OLTP systems and then compare your business with the Oracle Communications Data Model logical model to see how it maps to the Oracle Communications Data Model base and derived layer.
Produce a list of what people are going to try to do with the system (examples rather than models), and create use cases for appraising the functionality of Oracle Communications Data Model.
Procedures are written based on the use cases. Keep in mind that deviations from the procedure can be useful, provided that functionality is not skipped.
Map your business procedures against Oracle Communications Data Model functions, noting which processes are not available in Oracle Communications Data Model, or work differently in it. Be sure to check security requirements.
Determine the differences between your needs and Oracle Communications Data Model's schema. Answer the following questions:
Which differences can you live with, and which must be reconciled?
What can you do about the differences you can't live with?
Based on the preceding steps, update the business process models, activity flow diagrams, entity object model, and object life cycle models to reflect the customized system.
Write the customization report, detailing what changes will be required to make Oracle Communications Data Model's schema match your business needs. This includes any interfaces to existing systems, and additions and changes to Oracle Communications Data Model.
Based on the customization report, update the Project Plan, and complete a phase section for the Logical Design phase.
To customize the Oracle Communications Data Model model, you need to understand the dependency between each Oracle Communications Data Model component -- especially how the report KPIs are mapped to the physical tables and columns.
Oracle Communications Data Model provided a tool called "Metadata Browser" that helps you discover this. The metadata browser is delivered as one Dashboard in Oracle Business Intelligence Suite Enterprise Edition.
There are four tabs in the Oracle Business Intelligence Suite Enterprise Edition report that is the Oracle Communications Data Model Metadata Browser:
As shown below, on the Measure-Entity tab you can see the business areas (relational, OLAP, mining), the measures description, corresponding formula, responsible entities, and attributes for the measure.
To browse the data, select the business area and measure description that you are interested in.
Using the Entity-Measure tab of the Metadata Browser, you can discover the mappings between entities, attributes, supported measures, and calculations of the measures. You can discover information about particular entities and attributes.
For example, you take the following steps to learn more about COST ORIGINAL MONTH AGGR:
Select the entity COST ORIGINAL MONTH AGGR.
The following information is displayed.
Using the Program-Table tab you can browse for information on the intra-ETL mappings and report information. Take the following steps:
Select prompt program type (that is, Intra-ETL or report) and program name for sowing particular report or intra_ETL information.
For example, if you select a program type of Report for program named 2-Months of service, the following information is displayed.
For example, if you select a Program type of Intra-ETL Mapping for DWD_ACCT_DEBT_DAY__MAP, the following information is displayed.
Table-Program:By default when you go to the Table-Program tab you see all tables used for all the reports.To discover what reports use a particular table, you must move a particular table from the right pane to the left (Selected) pane.
For example, to see the reports that use the DWA_CALL_CENTR_CALL_MO table, take the following steps:
In the right pane of the Table-Program tab, select DWA_CALL_CENTR_CALL_MO.
Move it to the Selected list on the left by clicking on <, and click OK.
The following information is displayed.
Select GO and the reports for DWA_CALL_CENTR_CALLMO table are displayed.
Application stores are the latest battleground for mobile phone companies seeking to differentiate their products in an increasingly crowded and competitive marketplace. Users will be able to find the applications by searching using keywords or by browsing through categories and top downloads - so they can see what everyone else is downloading - in addition to the front page, which will showcase a selection of featured applications. The 'App World' can be accessed directly through the handset, enabling users to download applications and software on the go. Some applications will be free, others will cost a small fee.
Now, as an example, let's take a look how Oracle Communications Data Model supports the application store business, what a sample customer might discover during fit-gap analysis, and how that customer might extend Oracle Communications Data Model to fit the discovered gaps.
See also:Business use cases in Oracle Communication Data Model Reference for other examples.
The supplied entities that support application stores
The entities provided with the logical model of Oracle Communications Data Model that support the Application stores are:
CONTENT PROVIDER: This entity provides the actual content that will ultimately be consumed by the end user. The contents could be video or audio clips or text content. In the case of Quick Time 7, the content provider is Apple.
CONTENT TYPE: This entity will store the type of content. For example, for Quick Time 7, Content Type is an application.
CONTENT: This entity keeps all contents provided by the content provider. For example, Quick Time 7 is Content. In this entity we can store the information about the content; for example, whether the content is still active or not, popularity of the content which will be calculated by the number of downloads, and so on.
CONTENT PRICE: This entity contains the price for downloading/ordering the content. This price is for individual content clip. There might be other contents priced as a flat rate rather than different price for each content. In this case, the pricing information should be in product rating plan. For example, Quick Time 7 Pro is $30
CONTENT PRICING TYPE: This entity is type of content pricing. For example, The charge per downloading, monthly fixed rate, and so on.
CONTENT DELIVERY EVENT: This entity is an event to track downloads of contents. This entity captures the details of the download like the size of the download, duration, date and so on.
The differences discovered during fit-gap analysis
Assume that during the fit-gap analysis, you discover the following needs that are not supported by the logical model delivered with Oracle Communications Data Model:
Your company saves more than two levels of data for content. In other words, you discover that you track not only Content and Content Type as represented in the standard logical model of Oracle Communications Data Model, but also a level under Content Type (that is, a content subtype). For example for the value of Games in Content, you have Content Types of Fun Games, Action, and Racing. For the value of Fun Games in Content Types, you have subtype values of Packman, Mummy, and NFS.
In the Application Store, the operator must maintain a history of Customers who purchased which application so that when customer tries to reinstall, they are not charged again.
Extending the logical model to support the differences
To support the differences, you need to extend the logical model in the following ways:
To store details about type of the game you will need to modify the logical model. The classic way to do this is to add another entity to hold another level of information. For example, you can add an entity named CONTENT SUBTYPE that has a 1:M relationship with the CONTENT entity. The specific steps to perform these actions in Oracle SQL Developer Data Modeler are given in "Steps: Extending the Logical Model to Support Multiple Levels for CONTENT".
To maintain the history of Customers who have purchased an application, you can change the logical model to support this need by creating an entity named APPLICATION SUBSCRIPTION that has a 1:M relationship with
CONTENT. The specific steps to perform these actions in Oracle SQL Developer Data Modeler are given in "Steps: Modifying the Logical Model".
Open the Oracle Communications Data Model in SQL Developer Data Modeler.
CONTENT SUBTYPE entity by taking the following steps:
In the right-hand pane (the main area) of the SQL Developer Data Modeler window, select the Logical tab.
Click the New Entity icon.
Click in the logical model pane and draw an entity box.
The Entity Properties window is displayed.
In the left-hand pane of Entity Properties, select General. For Name, specify,
CONTENT SUBTYPE. (Note the value of
xxx is the number for Long Name and
Single Table for FWD Engineer Strategy.)
In the left-hand pane, select Attributes. Using the Add (+) icon, add the following attributes, one at a time.:
CONTENT SUBTYPE CODE with a data type of
CONTENT SUBTYPE NAME with a data type of
CONTENT SUBTYPE DESC with a data type of
In the left-hand pane, select Unique Identifiers. Using the Add (+) icon, add a unique, primary key to CONTENT SUBTYPE.
key_1 (which represents the unique, primary key), and use Properties icon to add the properties to the key.
In the left-hand pane of Key Properties, select General. For key properties, specify
CST_PK for Name and
Primary Key for State. (Note that the Long Name is
Select Attributes and Relations, and then select the column for the primary key (that is, CONTENT SUBTYPE CODE).
Click Apply. The entity CONTENT SUBTYPE is created.
Add a CONTENT SUBTYPE CODE column to the
CONTENT entity by taking the following steps:
Right click and select Properties.
In the left-hand pane, click Attributes.
Use the Add (+) icon to add an attribute with the Name of
CONTENT SUBTYPE CODE and a Data type of
Add a relationship between
CONTENT and CONTENT SUBTYPE by taking the following steps:
Select the New 1: N Relation icon.
Select the CONTENT SUBTYPE entity.
Drag the CONTENT SUBTYPE entity over to the
CONTENT entity and drop the cursor.
Open Oracle Communications Data Model in SQL Developer Data Modeler.
APPLICATION SUBSCRIPTION entity by taking the following steps:
In the right-hand pane (main area) of the SQL Developer Data Modeler window, select the Logical tab.
Click the New Entity icon.
Click in the logical model pane in the main area; and in the Logical pane press, diagonally drag, and release the mouse button to draw an entity box.
The Entity Properties window is displayed.
In the left-hand pane of Entity Properties, select General. Specify
APPLICATION SUBSCRIPTION for Name, and
SUBSCRIPTION for Super Type. (Note that the value of FWD Engineer Strategy is Single Table.)
In the left-hand pane, select Attributes. Using the Add (+) icon, add the following
Attribute APPLICATION SUBSCRIPTION CODE and datatype is CODE. As
APPLICATION SUBSCRIPTION entity is of SUBSCRIPTION, attributes are inherited from SUBSCRIPTION entity.
In the left-hand pane, select Unique Identifiers. Use the Add (+) icon to add the Primary Key
Select Attributes and Relations, and then select the column for the unique, primary key.
Click Apply. The
APPLICATION SUBSCRIPTION entity will be created.
Add APPLICATION SUBSCRIPTION CODE to CONTENT by taking the following steps:
Select the CONTENT entity. Right click and select Properties.
In the left-hand pane, select Attributes. Use the Add (+) icon to add attributes, one at a time.
Add a relationship to CONTENT with APPLICATION SUBSCRIPTION by taking the following steps:
Select the New 1: N Relation icon.
Select the APPLICATION SUBSCRIPTION entity.
Drag the APPLICATION SUBSCRIPTION entity over to the CONTENT entity and drop the cursor.