| Oracle® Communications Data Model Reference 11g Release 2 (11.2) Part Number E15886-02 |
|
|
View PDF |
The logical data model of the Oracle Communications Data Model defines the business entities and their relationships and provides an understanding of the business and data requirements for the Oracle Communications Data Model data warehouse.
This chapter includes the following sections:
The following are the major area reference logical data model entities:
Figure 2-1 shows the Account Simple entity. Table 2-1 lists the Account Simple entities.
Figure 2-1 Account Simple Entity Organization

Figure 2-2 shows the Customer entity. Table 2-2 lists the Customer entities.
Figure 2-3 shows the Dealer entity. Table 2-3 lists the Dealer entities.
Figure 2-4 shows the Geography entity. Table 2-4 lists the Geography entities.
Figure 2-5 shows the Organization Business Unit entity. Table 2-5 lists the Organization Business Unit entities.
Figure 2-5 Organization Business Unit Entity Organization

Figure 2-6 shows the Party entity. Table 2-6 lists the Party entities.
Figure 2-7 shows the Party Subject Area entity. Table 2-7 lists the Party Subject Area entities.
Figure 2-7 Party Subject Entity Organization

Figure 2-8 shows the Product entity. Table 2-8 lists the Product entities.
Figure 2-9 shows the Product Instance entity. Table 2-9 lists the Product Instance entities.
Figure 2-9 Product Instance Entity Organization

Figure 2-10 shows the Service entity. Table 2-10 lists the Service entities.
Figure 2-11 shows the Subscription entity. Table 2-11 lists the Subscription entities.
Note:
Figure 2-11 is a simplified figure and does not show all of the entities listed in Table 2-11.Figure 2-11 Subscription Entity Organization

Figure 2-12 shows the Time Calendar entity. Table 2-12 lists the Time Calendar entities.
Figure 2-12 Time Calendar Reference Entity Organization

Figure 2-13 shows the Vendor entity. Table 2-13 lists the Vendor entities.
Figure 2-13 Vendor Reference Entity Organization

Figure 2-14 shows the Wireless Network entity. Table 2-14 lists the Wireless Network entities.
Note:
Figure 2-14 is a simplified figure and does not show all of the entities listed in Table 2-14.Figure 2-14 Wireless Network Organization

The following are the business area logical data model entities:
Figure 2-15 shows the Cost entity. Table 2-15 lists the Cost entities.
Figure 2-15 Cost Business Area Organization

Figure 2-16 shows the Customer Management entity. Table 2-16 lists the Customer Management entities.
Note:
Figure 2-16 is a simplified figure and does not show all of the entities listed in Table 2-16.Figure 2-16 Customer Management Area Organization

Figure 2-17 shows the Marketing entity. Table 2-17 lists the Marketing entities.
Note:
Figure 2-17 is a simplified figure and does not show all of the entities listed in Table 2-17.Figure 2-18 shows the Network entity. Table 2-18 lists the Network entities.
Note:
Figure 2-18 is a simplified figure and does not show all of the entities listed in Table 2-18.Figure 2-19 shows the Partner Management entity. Table 2-19 lists the Partner Management entities.
Figure 2-19 Partner Management Area Organization

Figure 2-20 shows the Product Management entity. Table 2-20 lists the Product Management entities.
Note:
Figure 2-20 is a simplified figure and does not show all of the entities listed in Table 2-20.Figure 2-20 Product Management Area Organization

Figure 2-21 shows the Provisioning and Service entity. Table 2-21 lists the Provisioning and Service entities.
Note:
Figure 2-21 is a simplified figure and does not show all of the entities listed in Table 2-21.Figure 2-21 Provisioning and Service Area Organization

Figure 2-22 shows the Revenue entity. Table 2-22 lists the Revenue entities.
Note:
Figure 2-22 is a simplified figure and does not show all of the entities listed in Table 2-22.Table 2-23 through Table 2-29 list the logical data model entities, in alphabetically.
Table 2-23 A to C Entity Descriptions
| Entity Name | Type | Description |
|---|---|---|
|
Reference |
Lookup for methods that a customer accesses or utilizes a service. For example:
|
|
|
Reference |
Assigns ACCESS METHODs to an account. |
|
|
Lookup |
Type of relationship between two ACCESS METHODs. For example:
|
|
|
Reference |
Assignment of an ACCESS METHOD to a related ACCESS METHOD. |
|
|
Reference |
The ACCESS METHOD may be split into multiple elements for better management. Each element is a segment in the ACCESS METHOD, which represents a group of access methods. For example, for the access method for a phone number, where access method elements are:
|
|
|
Lookup |
Lookup for type of ACCESS METHOD ELEMENT. For example:
|
|
|
Reference |
How the access method binds to an equipment instance. For example:
|
|
|
Reference |
Assigns the access method to a geographic region. |
|
|
Reference |
Assigns access method to a party. |
|
|
Lookup |
Lookup for type of relationship between ACCESS METHOD and PARTY. For example:
The management type of access method party relationship specifies that an employee may be responsible for the maintenance of a group of access methods. |
|
|
Reference |
The logical network resources. For example:
|
|
|
Base |
The history of access methods that the customer brought to the operator from another telecom operator, according to the number porting scheme. |
|
|
Reference |
Segments of ACCESS METHODs defined for usage tracking. For example:
|
|
|
Reference |
The relationship between ACCESS METHOD SEGMENT and PRODUCT CAPABILITY to define which product capabilities require which access method segment. |
|
|
Base |
The status of an ACCESS METHOD. Defines both current status and historical status. For example:
|
|
|
Lookup |
Lookup for available reasons an ACCESS METHOD may have a change in status. For example:
|
|
|
Lookup |
Lookup for available ACCESS METHOD status types and descriptions. For example:
|
|
|
Reference |
Assigns ACCESS METHOD(s) to a SUBSCRIPTION. |
|
|
Lookup |
Lookup for ACCESS METHOD type: Defines the types of methods by which a customer may use or access services or products. For example:
|
|
|
Reference |
The accessories that may be purchased from the service provider in addition to the item, product, or service. For example:
|
|
|
Reference |
The account is generated by a contract between service provider and customer. For the service provider hosting different network, including CDMA, GSM, broadband, and others, one customer may have a different account for a different network or can be unified. Once set up, a customer can use account for self service from the Web site or from a Service Provider terminal. In this case the account is normally protected by a password. |
|
|
Base |
Billing cycle status history for accounts. |
|
|
Lookup |
Lookup of all the reasons for adjustments. For example:
|
|
|
Reference |
Relationship assignments between accounts. For example, parent and child accounts. |
|
|
Lookup |
Lookup for available reasons accounts may be related. |
|
|
Base |
Contains the list of all adjustments to any account balance. These are pure adjustments and not just additional payments or costs. An account balance adjustment is usually related to the party interaction thread. |
|
|
Lookup |
Lookup of all the types of adjustments. For example:
|
|
|
Base |
Balance history of account subjected to the primary currency. The balance value was classified by the balance type. For example:
|
|
|
Lookup |
Type of account balance. For example:
|
|
|
Reference |
Billing cycle status history for accounts. |
|
|
Reference |
Billing frequency history for accounts. |
|
|
Reference |
Billing period history for accounts. |
|
|
Reference |
||
|
Base |
Subtype of COST, which associates a specific incurred cost to an ACCOUNT (through an EMPLOYEE). |
|
|
Base |
Credit limit assigned to an account, subscription, or contract. |
|
|
Derived |
The summarized daily debt status for each account. |
|
|
Aggregate |
Derived from ACCOUNT DEBT DAY DRVD. The summarized monthly debt status for each CUSTOMER TYPE. |
|
|
Base |
Lists the debt write-off activities on all accounts. |
|
|
Lookup |
Lookup for account event types. |
|
|
Base |
Subtype of PARTY ACCOUNT ASSIGNMENT. The account management history tracks the management relationship from employee to the accounts, including account creation, through sales channel, and accounts update or termination. |
|
|
Reference |
Assigns accounts and parties to PRODUCT MARKET PLAN. |
|
|
Base |
Allocations of funds from a receipt made by a party to an account. The receipt of a single sum from a party as a credit against an outstanding balance for the provision and supply of products or services. |
|
|
Derived |
Daily aggregation of payments made by all customers. |
|
|
Base |
Status history of each account preferred payment method. For example:
|
|
|
Aggregate |
Collects all changes to the payment method status and the reason of the changes over time. |
|
|
Derived |
Collects the changes on payment method status. |
|
|
Lookup |
Lookup for specific status of the account payment method. For example:
|
|
|
Lookup |
Lookup for types of ACCOUNT PAYMENT METHOD STATUS. For example:
|
|
|
Aggregate |
Monthly summary of payments made by all customers. |
|
|
Base |
Defines the history of how account uses the PRODUCT MARKET PLAN. |
|
|
Reference |
The preferred invoice delivery type history for account. |
|
|
Reference |
Contains preferred payment methods for the account. |
|
|
Reference |
Records more details about the account. |
|
|
Base |
The customer refund is the money transferred back to customer account, which is normally based on an invoice adjustment. |
|
|
Derived |
The daily summary of refund to customers and the impacts to revenue. |
|
|
Aggregate |
The monthly summary of refunds to customers and the impacts to revenue. |
|
|
Lookup |
Lookup for the reasons why a refund may occur. For example:
|
|
|
Reference |
The segments identifying distinct groupings of accounts with similar characteristics. The account segments are typically generated from the data mining analysis. |
|
|
Reference |
Assign account segment to each account. |
|
|
Reference |
Used to cluster the account. |
|
|
Derived |
Account statistics for each account. One account normally has multiple SUBSCRIPTIONs, and CONTRACTs, all values on which are summed into the account level. Any deleted or blocked accounts are also included and are deemed as Churned, regardless of whether the deletion or block was voluntary. |
|
|
Aggregate |
Account statistical information at higher level by CUSTOMER TYPE. |
|
|
Derived |
The status change information about all accounts at every month. |
|
|
Base |
History of line status on the network. Any subscriber number actually is a line/connection on the switch or network. Each line goes through a variety of stages during its lifecycle on the switch. |
|
|
Lookup |
Lookup for account status reasons, or possible reasons a given account status has been changed. |
|
|
Lookup |
Lookup for account status types. |
|
|
Aggregate |
Account statistical information at a higher level by customer type. |
|
|
Reference |
History of subscriptions by an account. |
|
|
Lookup |
Each account to subscription relationship may have a reason associated with it. For example:
|
|
|
Lookup |
Lookup for account type. For example:
|
|
|
Lookup |
Internal Billing cycle which is used to calculate the usage amount and update the account balance for accounting GL purpose. |
|
|
Lookup |
Lookup for categories that can be associated with incurred costs. For example:
|
|
|
Reference |
Additional text can save multiple lingual notes or comments for products, parties, and other information. |
|
|
Reference |
Address details for physical or mailing address. |
|
|
Reference |
Entity associates addresses with other addresses. Addresses can be associated in many ways. For example, one address is an alternate for another address for those locations with multiple addresses. |
|
|
Lookup |
Lookup for reasons addresses may be related. |
|
|
Base |
Current status of an address location. For example:
|
|
|
Lookup |
Lookup for the reason for a change to the current ADDRESS STATUS. |
|
|
Lookup |
Lookup for address types. For example:
|
|
|
Reference |
Defines an advertising period. |
|
|
Reference |
Defines a quarter in an advertising calendar. |
|
|
Reference |
Defines a week in an advertising calendar. |
|
|
Reference |
Defines a year in an advertising calendar. |
|
|
Lookup |
Lookup to bin the customer into different groups according age. For example:
|
|
|
Lookup |
Defines subscriber life cycle ranges. For example:
|
|
|
Reference |
The SIC code used in Australia and New Zealand. |
|
|
Base |
Appointments assigning times for vendor or provider to deliver or provide a service. |
|
|
Lookup |
Lookup for appointment types. For example:
|
|
|
Aggregate |
The monthly summary of revenue values for ARPU calculation on CUSTOMER TYPE level. |
|
|
Derived |
The monthly summary of revenue values and revenue value components along with the subscriber base count; used to calculate the ARPU values. |
|
|
Lookup |
Average Revenue per Unit Band definitions. For example:
|
|
|
Lookup |
The level of customer's loyalty, based on the LOYALTY PROGRAM and ability to contribute to the revenue of the carrier. For example:
|
|
|
Reference |
Bank information that may be used in transactions. |
|
|
Reference |
Subtype of the PAYMENT CHANNEL, which tracks various bank channels where customers can pay by direct debt method. |
|
|
Lookup |
Lookup defining reasons a customer may be banned from using a service. |
|
|
Reference |
Subtype of NETWORK ELEMENT, which lists the Base Station Controller (BSC) of the network. The Base Station Controller provides, classically, the intelligence behind the BASE TRANSCEIVER STATION (BTS)s. Typically a BSC has tens or hundreds of BTSs under its control. The BSC handles allocation of radio channels, receives measurements from the mobile phones, and controls handovers from BTS to BTS. |
|
|
Reference |
Base Transceiver Station (BTS) is the equipment which facilitates the wireless communication between User Equipment (UE) and the network. |
|
|
Derived |
Daily BER (Bit Error Rate) and FER (Frame Error Rate) statistics about the network elements. |
|
|
Aggregate |
Monthly BER (Bit Error Rate) and FER (Frame Error Rate) statistics about the network elements. Derived from BER FER ERROR RATIO DAY DRVD. |
|
|
Lookup |
Lookup to indicate the statistics value for BER (Bit Error Rate) or FER (Frame Error Rate). |
|
|
Lookup |
Documents each billing run/cycle. Typically the billing cycle is per month. Sometimes a customer may be billed at a different date inside the billing cycle. For example:
|
|
|
Lookup |
The billing frequency specifies the number of billing periods that comprise the billing cycle. |
|
|
Lookup |
The billing period specifies the unit to be used to calculate the billing cycle (such as days or months). |
|
|
Lookup |
Lookup for category of billing status. For example:
|
|
|
Lookup |
Lookup for the status type of billing result, including the reasons. For example:
|
|
|
Base |
History of all black-listed customers. |
|
|
Reference |
The brands associated with hardware (usually this applies for handsets, but also for ITEMs). |
|
|
Reference |
Broadband is subtype of PRODUCT service. Describes the characteristics specific to the broadband product. |
|
|
Reference |
Subtype of PRODUCT RATING PLAN applied to BROADBAND product. |
|
|
Base |
The broadband network usage event, normally implemented as a period while customer is connected to the network. This is charged based on time usage. Some internet connection product might charge by data volume. |
|
|
Reference |
Defines month-in-half in a business calendar. |
|
|
Reference |
Defines half year in a business calendar. |
|
|
Lookup |
The legal status of the company. For example, a Public Company, Private, and so on. |
|
|
Reference |
Defines month in a business calendar. |
|
|
Reference |
Defines quarter in a business calendar. |
|
|
Reference |
Assigns job roles to a business unit within the organization. |
|
|
Reference |
Work shift associated with the Business Unit, mapped to the Employee job roles for the allocation for these shifts. |
|
|
Reference |
Defines week in a business calendar. |
|
|
Reference |
Defines year in a business calendar. |
|
|
Reference |
Subtype of EQUIPMENT INSTANCE, which collects all cable modem instances installed at customer's site connecting to the network of the Communications Service Provider. |
|
|
Reference |
Defines month-in-half in a Gregorian or Normal Calendar. |
|
|
Reference |
Defines half year in a Gregorian or Normal Calendar. |
|
|
Reference |
Defines month in a Gregorian or Normal Calendar. |
|
|
Reference |
Defines quarter in a Gregorian or Normal Calendar. |
|
|
Reference |
Defines weeks in a Gregorian or Normal Calendar. |
|
|
Reference |
Defines years in a Gregorian or Normal Calendar. |
|
|
Lookup |
Lookup for call categories. For example: Data, Fax, or Voice. |
|
|
Reference |
Defines call centers for a carrier or provider. RDM: A unit within an organization or a third-party organization that handles telephone sales, services, or both. |
|
|
Reference |
Agents of a call center. |
|
|
Lookup |
Lookup for call center agent types. For example: Employee or IVR. |
|
|
Derived |
The daily aggregate of customer call statistics from the call center. The customer calls are analyzed for the time of the call, duration of the call, subscriber or non-subscriber calling, and the call direction. |
|
|
Aggregate |
Monthly summary of customer call statistics for the call center. |
|
|
Derived |
Statistics for all the cases initiated or resolved by the call center. For example:
|
|
|
Aggregate |
Monthly summary of statistics for all the cases initiated or resolved by the call center. |
|
|
Lookup |
Lookup to further characterizes the type of cases from the call center. The case subtype helps to split a given case type into various subtypes. For example, for the case type, "Srv: Service Request", the subtype could be classified as "Package Upgrade", "Package Downgrade", "Simple Contract Renewal", or "Onsite Support". |
|
|
Lookup |
Further classifies the CALL CENTER CASE SUB TYPE. For example, for call center case type "Service Request", and call center case subtype "Technical Support", the call center case title could be:
|
|
|
Lookup |
Lookup for type of call center cases. For example:
|
|
|
Reference |
Assigns to the CALL CENTER, the languages, products, or geographical areas which the call center can serve. |
|
|
Lookup |
To indicate incoming call or outgoing call. |
|
|
Reference |
A type of phone service. The calling party can be on hold if receiving party is in a call. |
|
|
Lookup |
This is to record any other characteristics of the call, such as, 3-party call, or any user defined special type of call. |
|
|
Lookup |
Lookup for reasons why the voice carrying channel is being recycled during the call. |
|
|
Lookup |
Lookup to define how the call was routed. For example:
|
|
|
Lookup |
Lookup for service types that could be used in a call. For example:
|
|
|
Reference |
All the possible call sources or call destinations. The call sources or call destinations classify the calls into different groups, such as: local call, long distance domestic call, or internal call. |
|
|
Lookup |
Lookup to classify calls into successful calls or unsuccessful due to various reasons or causes. Call success failure, along with the call direction helps in facilitating the required analysis for roaming calls. |
|
|
Lookup |
Any extra charge on the call in addition to the normal rating. |
|
|
Lookup |
Lookup for the reasons a call may be terminated. For example:
|
|
|
Lookup |
Lookup to further classify call category into call types. For example:
|
|
|
Reference |
Subtype of PRODUCT, with specific information about CALLER ID service. |
|
|
Reference |
Campaigns are the entire communication strategy for a specific marketing communications program. The marketing communications program is frequently in support of promotional events and individual promotions but can be stand-alone. A campaign is always associated with a MEDIA OBJECT, such as a television campaign. |
|
|
Reference |
Channel by which a CAMPAIGN is exposed to a customer. For example: News group or media company which issues newspaper, television affiliate, and so on. A piece of newspaper of a block/slot on the paper is a publication/media object. The campaign channel can be categorized by CAMPAIGN CHANNEL TYPE. |
|
|
Lookup |
Lookup for campaign channel type. For example: newspaper, Television, Magazine. |
|
|
Base |
||
|
Reference |
The history of campaign party role about management of a CAMPAIGN. The party here can be not only the sales or marketing employee at TELCO operator, it can also be campaign partner. |
|
|
Reference |
Details regarding message broadcast or sent during a CAMPAIGN. |
|
|
Base |
Information about the creative content of the message. |
|
|
Reference |
Details about how the execution message is depicted for a CAMPAIGN. |
|
|
Lookup |
Lookup for types of campaign purposes. For example:
|
|
|
Lookup |
Status of CAMPAIGN. |
|
|
Lookup |
Lookup for type of campaign. For example:
|
|
|
Derived |
The calculated detail information related to the tariff/package change of customers. For prepaid customers, usually it is impossible to track customer movement between products due to lack of customer identification. For some customers, they may change at the next "beginning of the month". |
|
|
Aggregate |
The calculated tariff or package change summary of all customers at the month level. For prepaid customers, usually it is impossible to track customer movement between products due to lack of customer identification. |
|
|
Reference |
The cell in a wireless network such as GSM, which is an area serviced by the BASE TRANSCEIVER STATION (BTS). |
|
|
Lookup |
Lookup for reasons a cell outage could occur. For example:
|
|
|
Reference |
Most cells are split into sectors or individual areas to make them more efficient and to let them to carry more calls. The cell site equipment provides each sector with its own set of channels. |
|
|
Reference |
This is where the base station radio equipment and their antennas are located. A cell site gives radio coverage to a cell. |
|
|
Base |
Subtype of COST which could apply to a CELL SITE. For example:
|
|
|
Lookup |
Lookup for type of CELL SITE. For example: the cell site type can be classified by GSM/CDMA/PHS/broadband/Pay TV. |
|
|
Derived |
The network parameters and runtime statistics captured at the cell level. |
|
|
Aggregate |
The network parameters and runtime statistics for all CELL SITEs aggregated at the month and certain geography level. |
|
|
Lookup |
Lookup for all possible cell types. For example, Macro, Micro, and Pico:
|
|
|
Lookup |
Lookup for who proposed the changes for a customer tariff change. For example:
|
|
|
Reference |
Identifies all the channels through which customers interact with the telco provider for sales or services purposes. |
|
|
Base |
Subtype of COST, which collects all costs specifically related to a given sales channel. |
|
|
Lookup |
Lookup for types of channels as defined by their functions. For example:
|
|
|
Derived |
Monthly statistics regarding each account, which acts as source material for training the Churn Predict Mining Model. |
|
|
Lookup |
Lookup for reasons an account may churn. |
|
|
Lookup |
Lookup for categories to classify the type of circuit. For example:
|
|
|
Reference |
Describes each component of each circuit. Typically a circuit will include several components. For example, a Digital Data Services circuit linking two customer sites may include three components:
There are two scenarios:
For the first scenario, where two switches are linked, the switch_id and secondary_switch_id attributes will identify the two switches. The site_id attribute will be null. If the circuit component links a switch with a customer site, then the switch_id attribute will identify the switch and the site_id attribute will identify the customer site. The secondary_switch_id attribute will be null. |
|
|
Base |
Business activities of renting some circuits to other operators, in return for a monthly, or fixed, revenue. |
|
|
Lookup |
Lookup for types of rental events. For example:
|
|
|
Base |
The traffic volume statistics over certain periods, where periods are implementation dependent but generally hourly, for each CIRCUIT COMPONENT. |
|
|
Lookup |
Lookup for type of detailed circuit types. For example: For interconnect:
For customer connection ADSL:
|
|
|
Reference |
Subtype of a PARTY, who collects the customer debt on behalf of the operator under a financial agreement. For example:
|
|
|
Derived |
Statistics of all commissions granted to the sales agents because of the sales of products and services in the given period. |
|
|
Aggregate |
Monthly aggregation of all commissions granted to the sales agents because of the sales of products and services in the given period. |
|
|
Lookup |
Lookup for commission types that may be paid to sales representatives. For example:
|
|
|
Derived |
Statistics about all connections and disconnections from each ACCESS METHOD on the network per day. This is related to the network usage or traffic. This entity is not related to counting "subscriptions" to a given service. |
|
|
Aggregate |
Monthly aggregation of all connections and disconnections on the network per day, for network usage or traffic analysis. |
|
|
Reference |
Lists of potential and existing CUSTOMERs for CAMPAIGNs. Contact lists can be created by the TELCO from marketing activity, running certain models, or obtained from another organization. |
|
|
Lookup |
Lookup for possible reasons for changing the CONTACT LIST. |
|
|
Base |
Subtype of COST, which applies to a specified CONTACT LIST (usually this is a cost associated with the purchase and maintenance of a contact list). |
|
|
Lookup |
A categorization of the recurrence of a CONTACT LIST. For example:
|
|
|
Lookup |
Describes the various roles a contact individual may play in the relationship with the operator. |
|
|
Reference |
Keeps all downloadable content provided to the customer through the operator's network. For example:
|
|
|
Base |
EVENT in which content was downloaded. |
|
|
Reference |
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. |
|
|
Lookup |
Lookup for types of content pricing. For example:
|
|
|
Reference |
Provider for content that would be consumed by end user. The contents could be video, audio clips, or text content. |
|
|
Lookup |
Lookup for content types. For example:
|
|
|
Reference |
Legal agreement between a Communications Service Provider and an account. |
|
|
Base |
Approval for the CONTRACT from the operator's authorized employee, if the contract requires higher level approval or review. |
|
|
Reference |
Defines relationship(s) between contracts. |
|
|
Lookup |
Lookup for reasons of why two contracts are related. For example: The reason for one contract to be replaced by another:
The reason for one contract to depend on another:
|
|
|
Lookup |
Lookup for types of assignment between two contracts. For example:
|
|
|
Lookup |
Lookup to classify the initiator of the contract change. |
|
|
Lookup |
Lookup of all the type of contract changes. For example:
|
|
|
Derived |
Derived information about a customer's current/future contract for analytical purpose. This entity captures only changed, current or future, contracts. |
|
|
Reference |
The document(s) provided by the customer when a contract was signed. For example:
|
|
|
Derived |
Derived information about a customer's current/future contract for analytical purpose. The entity only contains changed contract (current or future). |
|
|
Aggregate |
Derived information about a customer's current/future contract for analytical purpose. The entity only contains changed contract (current or future). |
|
|
Reference |
To accommodate special link or additional usage of product in contract. |
|
|
Base |
The status history of the CONTRACT. |
|
|
Lookup |
Lookup for description of the contract status change. For example:
|
|
|
Lookup |
Lookup for all possible types of CONTRACT STATUS. For example:
|
|
|
Lookup |
Lookup for all possible terms which may be attached to a CONTRACT. For example:
|
|
|
Base |
The value of terms attached to the CONTRACT. For example:
The value can vary at different time period of contract. For example, the monthly fee might be 100 for the first six months and 80 for the last six months. A penalty calculation can also be based on the months left in contract. |
|
|
Lookup |
Lookup for contract types. |
|
|
Base |
Costs that have been incurred from operations and events at trackable levels. For example:
|
|
|
Reference |
Cost Center of a COURIER or provider to which costs can be charged. |
|
|
Base |
The budget of each cost center at a specific financial period. |
|
|
Aggregate |
Statistics of various costs incurred to the customer. These details are important for analysis such as:
|
|
|
Derived |
Monthly aggregation of various cost incurred to the customer. These details are important for analysis such as:
|
|
|
|
Aggregate |
Monthly aggregation of all expenses by each business unit inside the carrier. |
|
Derived |
Statistics of all expenses by each business unit inside the carrier. These values can be useful for auditing and budgeting purposes. |
|
|
Lookup |
Lookup of all possible reasons why the cost occurred. For example:
|
|
|
Lookup |
Lookup to further classify COST TYPEs. For example:
|
|
|
Lookup |
Lookup for types of costs. For example, the cost is to the CUSTOMER, CHANNEL, COURIER, or to the EMPLOYEE (Mobile Monthly Claim or Purchase). |
|
|
Reference |
The party who provides the Courier service for the Telecom Operator. |
|
|
Base |
Subtype of COST which applies to a COURIER for delivering products or invoices to the customer. |
|
|
Reference |
Lookup for credit categories that may be assigned to customers. For example:
|
|
|
Aggregate |
Credit category aggregation over all customers at each month. |
|
|
Derived |
Credit category assigned to each customer at each month. The credit categories are defined in the credit category dimension. |
|
|
Lookup |
Lookup for currencies that may be used in a transaction. |
|
|
Base |
Exchange rate against the primary currency, as determined by exchange rate type and value date. |
|
|
Reference |
Assigns currency usage to a geographic area. |
|
|
Reference |
Information pertaining to customers. |
|
|
Derived |
Aggregate daily new customer count by PRODUCT. |
|
|
Aggregate |
Monthly summary of newly acquired customers by PRODUCT. |
|
|
Lookup |
Lookup for Customer Classification codes. For example:
|
|
|
Reference |
Assign customer to a customer class. A customer may belong to different customer classes because of their usage behavior at different times, therefore customer to customer class is a many to many relationship. |
|
|
Base |
Subtype of COST which applies to a customer. For example, the cost of a gift that is sent to a customer. |
|
|
Aggregate |
Statistics on Customer fraud and debt collection. |
|
|
Derived |
Monthly summary of customer fraud and debt collection. |
|
|
Derived |
Statistics related to customer equipment installation activities for each customer. These statistics typically include: modems, routers, or DSL boxes for internet and Television equipment |
|
|
Aggregate |
Monthly summary of customer equipment installation activities. These statistics typically include: modems, routers, or DSL boxes for internet and Television equipment. |
|
|
Base |
The activities to install services at the customer site. For example:
|
|
|
Base |
On site installation for the customer with particular equipment instance. |
|
|
Base |
Details regarding customer service. |
|
|
Base |
The activities of providing on site support to a customer. |
|
|
Reference |
Subtype of CUSTOMER (and PARTY), which contains details of individuals as opposed to organizations. |
|
|
|
TBS |
TBS |
|
Derived |
The result measures from mining analysis, including churn probabilities, Life Time Value (LTV) mining, and other result measures. |
|
|
Reference |
Event celebrated or observed by a customer. For example:
|
|
|
Lookup |
Lookup for occasion type. For example: Wedding Anniversary, Birthday, Company founding anniversary, and so on. |
|
|
Base |
Orders placed by customers. This customer order is currently for service providers shop service, where a customer can place an order for a handset, a broadband installation request, or make some other order. |
|
|
Base |
Details regarding items in the CUSTOMER ORDER. |
|
|
Base |
Current state of an order line item. |
|
|
Base |
Payments applied to a CUSTOMER ORDER. |
|
|
Base |
Current state of a CUSTOMER ORDER. |
|
|
Reference |
Subtype of CUSTOMER (and PARTY), which contains details of organizations as opposed to individuals. Note that an organization can also consist of one individual only (for example: "independent"). |
|
|
Reference |
Detail information about a customer that may be deemed private. |
|
|
Lookup |
Entity contains a customer classification in revenue terms. For example: Customer with charges between $100 to $200. |
|
|
Reference |
Assigns a revenue band to a customer. |
|
|
Lookup |
Lookup for types of revenue a customer may bring to the operator. For example:
|
|
|
Reference |
Scores or Score ranges that may be assigned to a customer based on credit, behavior, or other criteria. For example:
|
|
|
Reference |
Market or customer segments to which customer may be assigned. |
|
|
Reference |
The segmentation model used to profile the customers. For example:
|
|
|
Lookup |
Lookup for the various customer feelings as reported during a party interaction (on the phone, as email, or from simple mail). The value can be used for text mining. For example:
|
|
|
Reference |
Assigns SIC/NASIC code to customers. |
|
|
Reference |
Initial source or contact with customer. For example:
|
|
|
Lookup |
Lookup for type of customer. For example: Individual or Corporate. |
Table 2-24 D to F Entity Descriptions
| Entity Name | Type | Description |
|---|---|---|
|
|
Base |
Data Service Events. For example
|
|
Derived |
Daily aggregate of data usage. |
|
|
Aggregate |
Monthly aggregate of data usage. |
|
|
Reference |
Defines day, the lowest level of all calendars. |
|
|
Reference |
Weather, external and internal conditions that may have impacted performance on a given day at a given location. |
|
|
Reference |
Documents how todate transformation can be implemented at day level. |
|
|
Reference |
Transformation with respect to a day. For example: maps a day last year to a corresponding day this year, or a day last year, to a day last month, and so on. |
|
|
Reference |
A deal refers to a special offer from a supplier to the telecom provider. The deal generally provides allowances, discounts, special favorable terms of payment or other incentives to motivate the service provider to buy more products or services from a supplier. |
|
|
Reference |
Identifies a specific product or service that is offered as part of a deal to the service provider and defines how the deal cost is to be handled. |
|
|
Reference |
The PARTY who resells products from the operator. |
|
|
Reference |
Assigns DEALER to a discount group(s). |
|
|
Lookup |
Ranges of time used to group debt based on the age of the debt. For example:
|
|
|
Base |
A special type of interaction to collect defaulted payment from a customer by the in-house debt collector. |
|
|
Base |
The assignment of a debt collection case to an external debt collection agency. |
|
|
Base |
Grouping of collection assignments sent to collector. |
|
|
Reference |
User defined demographic attributes that can be assigned values. |
|
|
Reference |
The domain of classifications used to group profile information about a PARTY. For example:
And other relevant demographics and psychographics. |
|
|
Reference |
Derived value of the customer based on predetermined criteria. |
|
|
Lookup |
Lookup for the types of call source destinations. For example:
|
|
|
Lookup |
Lookup for the various reasons the current status is direct debit payment. For example:
|
|
|
Reference |
Discount groups that employees or partners may be a part of. |
|
|
Lookup |
Distance ranges to characterize network events by geographical distance. |
|
|
Lookup |
Lookup for all reasons for diverting a call or retrieving a call from a Mailbox. For example:
|
|
|
Lookup |
Lookup for types for diverting a call or retrieving a call. For example:
Subscriber's calls are diverted to voice mail or to a Unified Messaging Service (UMS) mailbox as specified by the subscriber instructions or settings. For example, calls can be diverted when a subscriber is busy on another call, or when the subscriber has switched off the handset, or when a subscriber is not reachable. The subscriber can later retrieve all calls that are stored on the mailbox by accessing the mailbox through specified numbers or using the Internet, in case of UMS. All this traffic generated by diverted calls and retrieved calls is to be analyzed based on the type of call such as diverted or retrieved. The Divert Retrieve type helps in achieving this analysis by organizing calls as diverted or retrieved calls. |
|
|
Lookup |
Lookup for possible document condition types. For example:
|
|
|
Lookup |
Lookup for document types. For example:
|
|
|
Reference |
The xDSL modem to implement Broadband on copper wire (router). |
|
|
Lookup |
Demographic education levels that may be assigned to customers. |
|
|
Reference |
Subtype of individual indicating an employee of the provider. |
|
|
Base |
Worked shifts by hourly employees. |
|
|
Base |
Worked shifts by salaried employees. |
|
|
Base |
Subtype of COST, which applies to employee. For example, salary and bonus for employee. |
|
|
Lookup |
The various designations present in an organization for the employees. For example:
|
|
|
Reference |
Assigns EMPLOYEE to DISCOUNT GROUP(s). |
|
|
Reference |
||
|
Lookup |
Relevance of job role assignment to employee. For example: Primary, Secondary, and so on. |
|
|
Reference |
Specifies the languages the employee can use to serve customers, especially for call center agents and sales representatives. |
|
|
Reference |
Detail information about the EMPLOYEE that may be deemed private. |
|
|
Reference |
Planned staffing schedule of location, role, shift, and employees. |
|
|
Base |
List the trainings an employee has received. The employee training record is normally meant to apply to the call center agent, who is trained on specific products and or services. |
|
|
Lookup |
Lookup of employee type. For example:
|
|
|
Reference |
The devices that a CUSTOMER can use to access services provided by COURIER. The device might be a Cell Phone, a Fixed Line Phone, or a Fax Machine. Devices might be lent or sold to CUSTOMER. The equipment is a subtype of PRODUCT. |
|
|
Reference |
Facility housing devices. |
|
|
Base |
Subtype of COST, which collects all costs that are specifically related to a given EQUIPMENT CENTER (facility rent, taxes, and so on). |
|
|
Reference |
The function of the EQUIPMENT. For example:
|
|
|
Reference |
Assigns functionality to EQUIPMENT. |
|
|
Reference |
Implement communications. For example:
|
|
|
Reference |
Subtype of CONTRACT in which customers lease some EQUIPMENT. This equipment still belongs to the service provider. When a contract terminates the device should be returned to the service provider. For example:
|
|
|
Base |
A history of the status for an EQUIPMENT INSTANCE. For example:
|
|
|
Lookup |
Lookup for type of specific equipment instance status type. For example:
|
|
|
Base |
Describes the interactions with the Communications Service Provider. Event contains only "non-network" events (anything other than a call data record). An event can occur related to a provider. For example, for equipment down or a service disruption. An event can occur related to a CUSTOMER. For example, for a service order or a bill payment. Events store customer behavior to make special campaigns or to analyze the cost of customers. Normally an event incurs some cost and may generate revenue for the operator. The information specific to the type of event, or event interaction, is stored in corresponding event subtypes. |
|
|
Base |
Occurrence of Access Method Usage. |
|
|
Base |
Events occurring on an account. For example:
|
|
|
Base |
Describes relationship between unique events. |
|
|
Lookup |
Lookup for all possible reasons why a relationship exists between two EVENTs. For example:
|
|
|
Lookup |
Lookup for all types of relationships between two EVENTs. |
|
|
Lookup |
Lookup for EVENT CATEGORY which is further grouped into EVENT TYPE. For example:
|
|
|
Base |
Subtype of "Non Network Events", corresponding to the rental of a fixed line (broadband or phone line). The rental normally incurs charges for various type of activities. For example:
|
|
|
Lookup |
Lookup for the classification for the types of EVENTs that can occur. For example:
|
|
|
Base |
Subtype of COST, which is specifically related to a given EVENT. This cost is usually for a non-network event such as an interaction with a customer. For example, for on-site maintenance after a service issue or a break-down. |
|
|
Base |
Event in which payroll payment was made to an employee (excludes sales commission). Subtype of EVENT. |
|
|
Base |
||
|
Base |
Financial event involving an account or billing statement. Subtype of EVENT. |
|
|
Base |
Events affecting a Geographic Area that may have an impact on a provider's business. Subtype of EVENT. For example:
|
|
|
Base |
A gift redemption event occurred for a contract or subscription; normally because of a product market plan promotion. Operators may also give away gift items because of events such as a wrong billing. The redemption does not involve a LOYALTY PROGRAM. |
|
|
Base |
The delivery of invoice to customer. For example:
|
|
|
Reference |
Assigns an address location to the EVENT. |
|
|
Base |
Events associated with each event or transaction on a customer loyalty program. For example:
|
|
|
Base |
Subtype of EVENT LOYALTY PROGRAM, where a customer receives loyalty program points, a credit, based on network usage, a payment, or some other event. |
|
|
Base |
Subtype of EVENT LOYALTY PROGRAM, where a customer uses loyalty program points, a credit, to redeem gift items including cash placed in their account balance or some other redemption gift item such as a toy. |
|
|
Base |
Many to many relationship assigning a party or multiple parties to event(s). |
|
|
Base |
Interactions or communications with the customer. For example:
|
|
|
Base |
Subtype of EVENT PARTY INTERACTION which represents all phone call interactions from the customer with detailed information including:
|
|
|
Base |
Subtype of EVENT PARTY INTERACTION which represents email interaction from customers. |
|
|
Base |
Subtype of EVENT PARTY INTERACTION which represents the interaction with customers through letters. |
|
|
Base |
Visits to a store by a customer. Subtype of EVENT. |
|
|
Base |
Event in which party profile information was modified or updated. |
|
|
Reference |
Role played by a PARTY in an EVENT. For example:
|
|
|
Base |
Actions involving PREPAID MOBILE EVENT TYPE account. Subtype of EVENT ACCOUNT. For example:
|
|
|
Base |
Events associated with an offer or PRODUCT PACKAGE. Subtype of EVENT. |
|
|
Lookup |
Lookup for event reasons. For example: arrearage. |
|
|
Lookup |
Lookup for event reason categories. Categories are further grouped into event reasons. |
|
|
Reference |
Lookup for possible event resolutions. |
|
|
Lookup |
Lookup for possible response reasons that may be used in an EVENT. |
|
|
Lookup |
Lookup for the description of a result or any events. For example:
|
|
|
Base |
||
|
Base |
Lookup for event status. For example:
|
|
|
Lookup |
Lookup for event status reasons. For example:
|
|
|
Lookup |
Lookup for EVENT STATUS. For example:
|
|
|
Base |
Events associated with a subscription. Subtype of EVENT. For example:
|
|
|
Base |
Events involving temporal provisioning and relinquishment of products and services to current subscription base. |
|
|
Lookup |
Lookup for event type. For example:
|
|
|
Base |
The event of a customer registering at Web site to apply for service. |
|
|
Derived |
Daily collections by external collector. |
|
|
Aggregate |
Monthly collections by external collector. |
|
|
Reference |
Source from which the demographic information or customer information is obtained. |
|
|
Reference |
All operators the Service Provider does business with, including inland competitors or roaming partners. |
|
|
Lookup |
Lookup for types of external organizations. |
|
|
Reference |
Stores the information about the factor company, which is the financial instrument holding the receivables. |
|
|
Lookup |
Lookup for available types of network fault resolution. |
|
|
Lookup |
Lookup for available types of faults. |
|
|
Lookup |
Lookup for available result types for customer field activities that are performed by support engineers. For example:
|
|
|
Lookup |
Lookup for types of customer field activities that may be performed by support engineers. For example:
|
|
|
Reference |
Defines half-month in a fiscal calendar. |
|
|
Reference |
Defines half-year in a fiscal calendar. |
|
|
Reference |
Defines month in a fiscal calendar. |
|
|
Reference |
Defines quarter in a fiscal calendar. |
|
|
Reference |
Defines week in a fiscal calendar. |
|
|
Reference |
Defines year in a fiscal calendar. |
|
|
Reference |
Subtype of PRODUCT that provides detailed information on the fixed line service. |
|
|
Base |
Event involving a call made on a Fixed Line telephone. |
|
|
Reference |
The port ID associated with the telephone plug that provides a customer with fixed line service. The Fixed Line Port connects a customer's phone to a SWITCH. |
|
|
Reference |
Subtype of PRODUCT RATING PLAN associated only with Fixed Lines. |
|
|
Lookup |
Lookup for all possible classes of fraud profile that customers or dealers may commit. |
Table 2-25 G to J Entity Descriptions
| Entity Name | Type | Description |
|---|---|---|
|
|
Lookup |
Lookup for gender. |
|
Reference |
Cities defined in a Geography. |
|
|
Reference |
Countries defined in a Geography. |
|
|
Reference |
Counties defined in a Geography. |
|
|
Reference |
User-defined classification for DEMOGRAPHY ATTRIBUTEs. |
|
|
Reference |
User defined attributes to describe demographic information for a given Geography. |
|
|
Reference |
User defined values corresponding to the DEMOGRAPHY ATTRIBUTEs. |
|
|
Reference |
User defined geographic units. |
|
|
Reference |
Assignment of GEOGRAPHY ENTITYs to a user defined hierarchy level. |
|
|
Reference |
Assigns GEOGRAPHY ENTITYs to GEOGRAPHY HIERARCHY LEVELs. |
|
|
Reference |
User defined geographic hierarchies. |
|
|
Reference |
User defined levels within a geographic hierarchy. |
|
|
Reference |
Assignment of a GEOGRAPHY HIERARCHY level to a GEOGRAPHY ENTITY. |
|
|
Reference |
User defined name and descriptions for GEOGRAPHY HIERARCHY LEVEL. |
|
|
Reference |
User defined attributes associated with a GEOGRAPHY LEVEL. |
|
|
Reference |
Values assigned to the GEOGRAPHY LEVEL ATTRIBUTEs. |
|
|
Reference |
Defines a region in a Geography. |
|
|
Reference |
Defines a state in a Geography. |
|
|
Reference |
Defines a subregion in a Geography. |
|
|
Reference |
Top level of Geography. |
|
|
Derived |
Statistics of all give away items to the customer for promotion or retention purposes. |
|
|
Aggregate |
Monthly aggregation of all give away items given to customers for promotion or retention purposes. |
|
|
Lookup |
Lookup for types of give-aways. |
|
|
Reference |
Groups or Categories referred from General Ledger to classify all revenue related activities. |
|
|
Derived |
Statistics on the PCU (Packet Control Unit) for the GPRS (General Packet Radio Service) such as bytes sent, bytes received, the transferred data volume, and so on. |
|
|
Aggregate |
Monthly aggregation of statistical values on PCU (Packet Control Unit) for the GPRS (General Packet Radio Service). For example:
|
|
|
Reference |
Subtype of PRODUCT, with more information about GPRS (General Packet Radio Service). The service provider provides various services such as Internet, WAP to its customers or subscribers over GPRS. The information about the usage of these services is to be analyzed at individual and aggregate level. The GPRS service dimension organizes all GPRS services. |
|
|
Derived |
Daily summation regarding GPRS services provided to subscribers. |
|
|
Aggregate |
Monthly summation regarding GPRS services provided to subscribers. |
|
|
Reference |
Half-hours defined as part of time. |
|
|
Reference |
Todate transformation information at the half-month level. |
|
|
Reference |
Transformations with respect to half-month. For example:
|
|
|
Reference |
Cumulative time transformations at the half-year level. |
|
|
Reference |
Transformations with respect to half-year. For example:
|
|
|
Reference |
Instance of a handset. |
|
|
Reference |
Models of handsets. |
|
|
Derived |
Daily Aggregate of Handset Stock statistics by CUSTOMER, SALES CHANNEL, and SALES CHANNEL REPRESENTATIVE. |
|
|
Aggregate |
Monthly Summary of Handset Stock statistics by SALES CHANNEL and SALES CHANNEL REPRESENTATIVE. |
|
|
Derived |
Daily summation of handset distributions involving gift, discount, or loyalty voucher points. |
|
|
Aggregate |
Monthly summation of handset distributions involving gift, discount, or loyalty voucher points. |
|
|
Reference |
Hours defined as part of time. |
|
|
Reference |
Captures household information for the household that the individual customer may belong to. |
|
|
Reference |
Subtype of PRODUCT that provides information about IDD service. |
|
|
Base |
Event involving an International Direct Dial (IDD) call. |
|
|
Reference |
IN (Intelligent Network) platforms operated by the telecom service provider. The Prepaid mobile or toll-free business normally relies on IN platform. |
|
|
Derived |
Daily summation of parameters related to the IN PLATFORM functioning and performance on a daily level. |
|
|
Aggregate |
Monthly summation of parameters related to the IN PLATFORM functioning and performance on a monthly level. |
|
|
Reference |
The demographic values for individual customer and customer household. |
|
|
Reference |
Values assigned to user-defined DEMOGRAPHY ATTRIBUTEs. |
|
|
Lookup |
Lookup for all possible results of initiatives. For example, the result is:
|
|
|
Lookup |
Lookup for available initiative types. |
|
|
Base |
Defined answers, choices, corresponding to initiative questions. |
|
|
Reference |
Channels used for Provider or Customer interactions. For example:
|
|
|
Lookup |
Lookup for available directions for initiatives. For example:
|
|
|
Base |
Responses provided by CUSTOMER to interaction questions. |
|
|
Lookup |
Lookup for interaction reasons. For example:
|
|
|
Lookup |
Lookup for possible responses to customer interaction. For example:
|
|
|
Lookup |
Lookup for available interaction status. For example:
|
|
|
Lookup |
Lookup for types of interactions between company and CUSTOMER. For example:
|
|
|
Derived |
Daily summary of payment and collection by internal collector. |
|
|
Aggregate |
Monthly summary of payment and collection by internal collector. |
|
|
Base |
Subtype of NETWORK EVENT, which captures customer internet surfing history with detailed URL and time information. |
|
|
Base |
Invoices issued to accounts representing request for payment for goods and services for a specified period. |
|
|
Base |
Adjustments made on the INVOICE. |
|
|
Aggregate |
Monthly aggregation of calculated measures for all adjustments made on the INVOICEs. |
|
|
Derived |
Calculated measures for all adjustments made on the INVOICEs. |
|
|
Reference |
Quota of INVOICE ADJUSTMENTs assigned to EMPLOYEE. |
|
|
Lookup |
Lookup for the possible reasons for an adjustment on a customer's or on a partner's bill. For example:
|
|
|
Lookup |
Lookup for available adjustment types that may be applied to customer invoices. For example:
|
|
|
Aggregate |
Monthly aggregation of all INVOICEs to post paid customers at customer type level. |
|
|
Lookup |
Lookup for available delivery types of INVOICE to customer. For example:
|
|
|
Base |
Discount applied to INVOICE. |
|
|
Lookup |
Lookup for available discount reasons. |
|
|
Lookup |
Lookup for available discount types that may be applied to customer invoice. |
|
|
Derived |
Statistics on Invoices for further aggregation. |
|
|
Base |
Any line that appears on the INVOICE which is specific to the product components a customer has. The invoice item is not necessarily associated with a monetary charge or a credit (but invoice item usually does have an associated monetary charge or credit). The invoice item is usually a billable item to a given account, onto which usage or other events are charged. The unbillable items that could be part of the invoice item are "Loyalty Points", "Free Unit Amount/Rollover", and so on. For example:
|
|
|
Base |
Additional details regarding INVOICE ITEM including Product Usage Level. |
|
|
Lookup |
Lookup for invoice item detail types (item detail is the description of each column of a given item in a bill). The invoice item detail type may be classified in a mobile line. For example:
|
|
|
Lookup |
Lookup for invoice item types. For example:
|
|
|
|
Derived |
Postpaid customers are billed/invoiced for the usage of services on monthly basis, that is, bill for every subscriber based on his package, category, and usage is calculated, printed and sent to the customer account address for payment. |
|
Base |
Matches the payment to an INVOICE. |
|
|
Reference |
Payment terms of each INVOICE. For example:
|
|
|
Lookup |
Lookup for available types of payment terms. |
|
|
Lookup |
Lookup for type of INVOICE according to invoice generation process. For example:
|
|
|
Reference |
Subtype of ACCESS METHOD POOL, which lists all IP addresses available to customers. |
|
|
Reference |
Internet Service Provider (ISP). |
|
|
Reference |
The business that the ISP may provide. For example:
Please note that this only covers ISP specific business (not Application Provider business). |
|
|
Reference |
Relates an ISP to the Communications Service Provider through a "business" relationship. This entity assigns the definition of the relationship, in entity ISP BUSINESS, with the corresponding ISP. |
|
|
Lookup |
Lookup for high level of ISP business type. For example, Cooper Line Internet Connection (may further divided as DSL, ISDN), Colocation, DNS Name, and so on. For example:
|
|
|
Lookup |
Lookup for types of ISPs. |
|
|
Base |
Records traffic details of each session the user conducts with the Internet Service Provider ISP. The entity documents the connect and disconnect date/time and the number of local and international bytes downloaded, and uploaded. There will typically be multiple rows for each long running session. The entity will be implementation dependent, but normally there will be a record generated each hour - all records for the one session will have the same connect and disconnect date times, but the event start/end datetimes will identify the period that the usage (bytes) covers. |
|
|
Reference |
Identifies the user names associated with the Internet Service Provider (ISP) subscription. |
|
|
Reference |
Details describing the item or PRODUCT. |
|
|
Lookup |
Lookup for type of item (PRODUCT). |
|
|
Reference |
The occupation of the customer, which is the principal activity the customer performs to earn money. |
|
|
Reference |
Job Roles defined in the company that may be assigned to employees. For example:
|
Table 2-26 K to N Entity Descriptions
| Entity Name | Type | Description |
|---|---|---|
|
|
Lookup |
Languages spoken or written within the company or in interactions with CUSTOMERs. |
|
Lookup |
Lookup for various states which a legal process could be in, as part of a party interaction (usually after an inability to find an agreement to pay debts). |
|
|
Lookup |
Lookup for available types of letters that may be sent to CUSTOMERs. For example:
|
|
|
Derived |
Statistics for the number of lines activated and terminated every day for each ORGANIZATION BUSINESS UNIT. |
|
|
Aggregate |
Monthly aggregation of numbers of lines activated and terminated for each ORGANIZATION BUSINESS UNIT. |
|
|
Reference |
Loyalty programs available to which customers may be members of. |
|
|
Reference |
Channel through which a customer can join, change, or redeem the loyalty program. For example:
|
|
|
Derived |
Daily aggregate of LOYALTY PROGRAM statistics by CUSTOMER, PRODUCT, SALES CHANNEL, LOYALTY PROGRAM CHANNEL, SALES CHANNEL REPRESENTATIVE, AGE ON NET BAND, CREDIT CATEGORY. |
|
|
Lookup |
Lookup for the types of award updates that can be given to the PARTY. For example:
|
|
|
Lookup |
Lookup for types of LOYALTY PROGRAM events that could be used in a LOYALTY PROGRAM. |
|
|
Aggregate |
Monthly summary of LOYALTY PROGRAM statistics by PRODUCT, SALES CHANNEL, LOYALTY PROGRAM CHANNEL. |
|
|
Lookup |
Lookup for available roles or responsibilities that may be assigned to a PARTY participant of a LOYALTY PROGRAM. For Example:
|
|
|
Base |
Balance points awarded to a PARTY in a LOYALTY PROGRAM. |
|
|
Reference |
Mailbox allocated to a CUSTOMER. |
|
|
Lookup |
Lookup for type of management action that can be performed on a product market plan. For example:
|
|
|
Lookup |
Lookup for marital status that may be assigned to an individual. |
|
|
Reference |
A geographic area or region or other connotation for which demographic data are available. |
|
|
Reference |
Hierarchical levels of market area. |
|
|
Derived |
Monthly porting count between operators. |
|
|
Base |
The management history of market plan by the employee. |
|
|
Reference |
Stores the document that allows the customer to access a market plan specific to a certain category of customers (such as Students, Seniors, or unemployed). These market plans usually require a document that proves the validity of the request (for example, income certification or identification documents) that this entity stores. |
|
|
Reference |
The detail term value according to each term for the market plan, including monthly charge. |
|
|
Aggregate |
Monthly summation of Geographic Market Share for a PRODUCT MARKET PLAN. |
|
|
Derived |
PRODUCT MARKET PLAN Sales Revenue by Month, Address, and Business Unit. |
|
|
Reference |
Any form of media in which a CAMPAIGN MESSAGE may appear. For example:
|
|
|
Reference |
Relation of one MEDIA OBJECT to another MEDIA OBJECT. |
|
|
Base |
Costs incurred in the usage of a MEDIA OBJECT. Subtype of the COST that collects all costs related to a specific media (Newspaper, Television spots, Fliers, and so on). |
|
|
Lookup |
Lookup for available types of MEDIA OBJECTs. For example:
|
|
|
Base |
The mediated call event with original device information, dropped call, and missed call information, which is normally ignored by rating engine. The call event are collected before the calls are rated by rating engine. |
|
|
Reference |
Defines minutes as part of time. |
|
|
Base |
Subtype of Account Balance describing the number of 'Free' or 'Prepaid' minutes allocated to Subscriber in a given month. |
|
|
Reference |
Subtype of VALUE ADDED SERVICE and PRODUCT, which contains the information relative to the Multimedia Messaging Service (MMS). Do not confuse with the MMS EVENT itself. |
|
|
Base |
Subtype of NETWORK EVENT, which collects all information of calls of type Multimedia Messaging Service (MMS). |
|
|
Reference |
The Mobile Switching Center (MSC) is a sophisticated telephone exchange which provides circuit-switched calling, mobility management, and GSM services to the mobile phones roaming within the area that it serves. This includes voice, data and fax services, and SMS and call divert services. |
|
|
Lookup |
Lookup for the model types of items. Note that there may be different "types" for a given model. For example, for a handset a model may allow "Bluetooth" or not. |
|
|
Reference |
Defines related calendar elements for performing to-date time transformations. |
|
|
Reference |
Transformations with respect to a month. For example:
|
|
|
Derived |
Parameters, configurations, and runtime statistics related to the MSC (Mobile Switch Center) functioning and performance. |
|
|
Aggregate |
Monthly aggregation of parameters, configurations, and runtime statistics related to the MSC (Mobile Switch Center) functioning and performance. |
|
|
Reference |
Subtype of VALUE ADDED SERVICE and PRODUCT, which contains the information relative to the music downloading service. |
|
|
Reference |
Lookup for Classifications in the North American Classification System (NAICS). |
|
|
Reference |
Lookup for Industry in the North American Industry Classification System (NAICS). |
|
|
Reference |
Lookup for Classification Groups in the North American Industry Classification System (NAICS). |
|
|
Reference |
Lookup for Industry Sectors in the North American Industry Classification System (NAICS). |
|
|
Reference |
Lookup for Industry Sub-sectors in the North American Industry Classification System (NAICS). |
|
|
Lookup |
Lookup for available nationalities. |
|
|
Reference |
Names and Service Providers for relevant Networks. The full details of a service provider are found in the PARTY and Organizations entities. |
|
|
Derived |
Statistics of network availability measures and all outages that happened to the operator's network. |
|
|
Aggregate |
Monthly aggregation of network availability statistics and all outages that happened to the operator's network. |
|
|
Reference |
All elements belonging to the network (normally, only of the Communications Service Provider) to deliver the communication services. |
|
|
Base |
Subtype of the COST, which associate a specific cost to a given NETWORK ELEMENT (purchase, maintenance, recycling, and so on). |
|
|
Base |
Assignment of a NETWORK FAULT to a SUBSCRIPTION. |
|
|
Base |
Abstracted event for all events that happened to the operator network because of customer usage; network events are usually the basis for customer billing. |
|
|
Lookup |
Lookup for possible status of NETWORK EVENTs. For example:
|
|
|
Lookup |
Lookup for available types of NETWORK EVENTs. |
|
|
Base |
Records each registered fault. |
|
|
Base |
Links a network issue to all subscriptions impacted, which allows you to list the customer and service impacted by a network fault. |
|
|
Reference |
Defines the relationship between NETWORK TOUCHPOINT and SERVICE COVERAGE AREA. |
|
|
Reference |
Point of service site for a subscriber to access a CELL SITE or FIXED LINE PORT. The site is a geographical point instead of area, therefore, it belongs to some geographical entity. For example, a city or a town rather than a type of the GEOGRAPHY ENTITY. For example:
|
|
|
Lookup |
Lookup for available classes of NETWORK TOUCHPOINT. For example:
|
|
|
Aggregate |
Monthly summary of NETWORK TOUCHPOINTs by CUSTOMER, NETWORK, Address, and so on. |
|
|
Derived |
Monthly summary of NETWORK TOUCHPOINTs by NETWORK, County, and so on. |
|
|
Lookup |
Lookup for Available Status codes and descriptions of NETWORK TOUCHPOINT. |
|
|
Lookup |
Lookup for the type of NETWORK TOUCHPOINT. For example:
|
|
|
Lookup |
Lookup for the types of NETWORK. Will include:
|
|
|
Lookup |
Lookup for types of notification a subscriber may receive when a call is received by or diverted to a UMS or VMS mailbox. For example:
The UMS Notification Type dimension helps to organize the notifications data by notification type, along with other dimensions. |
|
|
Reference |
The mobile MSISDN number of ported number. |
|
|
Base |
The Number Porting (NP) Request submitted by a customer (Porting In) or a recipient operator (Porting Out). |
|
|
Base |
Request Line Item within a Number Porting (NP) request. |
|
|
Base |
State history for Number Porting (NP) request line items. |
|
|
Lookup |
Lookup for type of Number Porting (NP) line item state. For example:
|
|
|
Base |
State history for the Number Porting (NP) request. |
|
|
Lookup |
Lookup for type of state for Number Porting (NP) request. For example:
|
|
|
Lookup |
Lookup for type of Number Porting (NP) Request. For example:
|
|
|
Lookup |
Step involved in the Number Porting (NP) request. For example:
|
|
|
Reference |
Defines the codes associated to a given area; these codes are typically used for calls to a fixed line number. For example:
Note that a number area could also be associated to other operators, and not to a geographical area. For example, 9 in France. |
|
|
Reference |
Country number. For example:
|
|
|
Lookup |
Lookup for available classifications for the network technology, used in relation to subscriptions. For example:
|
|
|
Derived |
Aggregation of daily Porting Requests (in/out). |
|
|
Aggregate |
Monthly summary of Porting Requests (in/out). |
Table 2-27 O to R Entity Descriptions
| Entity Name | Type | Description |
|---|---|---|
|
|
Lookup |
Lookup of call classifications:
|
|
Lookup |
Classification group for operators. For example, the group can be classified as:
|
|
|
Lookup |
Lookup for operator type to classify operators. For example:
International operators normally have multiple subsidiaries whose relationship is modeled in the party relationship. |
|
|
Reference |
Lookup for the status that a given order line item, in a command, can be assigned. For example:
|
|
|
Reference |
Lookup for the type of Order State. For example:
|
|
|
Lookup |
Lookup for the type of Order Status. For example:
|
|
|
Lookup |
Lookup for type of CUSTOMER ORDER. For example:
|
|
|
Reference |
An ORGANIZATION HIERARCHY LEVEL within an ORGANIZATION CHAIN. The Organization Area entity is the parent of one or more ORGANIZATION REGIONs. |
|
|
Reference |
The name of Company, Organization, or subsidiary that is recognizable to the consumer or the name of the store as it appears on the catalog, web channel, or brick and mortar store. |
|
|
Reference |
Any logical entity that is recognized as a part of the enterprise for business analysis and transactions. Classification for a business entity can include company, operation unit, store, or warehouse. |
|
|
Reference |
A business unit of the organization that delivers a limited range of specific communications services or merchandise through any sales channel (Web Site, store, partner stands, and so on). For example, for the SuperTelco example, two Business Units could be defined as:
|
|
|
Base |
Sub-table of COST. This entity associates a specific cost to an ORGANIZATION BUSINESS UNIT (for those costs not covered by EMPLOYEE COST). |
|
|
Lookup |
Lookup for type of ORGANIZATION BUSINESS UNIT. For example:
|
|
|
Reference |
An ORGANIZATION HIERARCHY LEVEL within an ORGANIZATION COMPANY. Organization Chain entity is the parent of one or more ORGANIZATION AREAs. |
|
|
Reference |
An ORGANIZATION HIERARCHY LEVEL within an ORGANIZATION CORPORATE. Organization Company entity is the parent of one or more ORGANIZATION CHAINs. |
|
|
Reference |
Highest level of ORGANIZATION HIERARCHY. Organization Corporate entity is the parent of one or more ORGANIZATION COMPANYs. |
|
|
Reference |
An ORGANIZATION HIERARCHY LEVEL within an ORGANIZATION REGION. Organization District entity is the parent of one or more ORGANIZATION BUSINESS UNITs. |
|
|
Reference |
An ORGANIZATION HIERARCHY LEVEL within ORGANIZATION CORPORATE. |
|
|
Reference |
User defined. Master list of all of the hierarchies in an organization. |
|
|
Reference |
The association entity for the hierarchies and levels. |
|
|
Reference |
Assignment of Hierarchy Levels to ORGANIZATION HIERARCHY. |
|
|
Reference |
Version of ORGANIZATION HIERARCHY. |
|
|
Reference |
Associate selling price to the item. Each organization might have different prices for the same item model. |
|
|
Reference |
List of all the business levels within an organization. |
|
|
Reference |
Values for the user defined attributes associated with an ORGANIZATION HIERARCHY LEVEL. |
|
|
Reference |
Attributes assigned to an ORGANIZATION LEVEL. |
|
|
Reference |
Publicly available and statistical information regarding the internal or external parties, such as DUNS number and number of employees. |
|
|
Reference |
An ORGANIZATION HIERARCHY LEVEL within an ORGANIZATION AREA. Organization Region entity is the parent of one or more ORGANIZATION DISTRICTs. |
|
|
Reference |
Subtype of the ORGANIZATION BUSINESS UNIT. This entity collects all information on Web sites managed by the operator. This normally includes only public information. |
|
|
Reference |
Location in which goods or merchandise (routers, handsets, computers, and so on) are stored but not sold, before they are sent to the shops or utilized by CSP. For example:
|
|
|
Reference |
User defined attribute definitions and corresponding values regarding demographic statistics as related to an ORGANIZATION BUSINESS UNIT. |
|
|
Reference |
Individual associated with a PARTY organization, other than those defined such as CUSTOMER or EMPLOYEE. |
|
|
Reference |
Assigns costs of a given PROMOTION to a Partner or PARTY participating in the promotion. |
|
|
Aggregate |
The monthly summary of financial settlement activities that have happened to partners at higher level. |
|
|
Derived |
Financial settlement activities that have happened to each partner within the month. |
|
|
Lookup |
Lookup for valid reason codes for a partner settlement. |
|
|
Reference |
A party is a real person, organization, branch, subsidiary, legal entity, holding company, or some other entity. Any real thing that you would want to put a name to is a party. The attributes of a party are universal. In other words, they are independent of your selling, or ultimately buying relationship with the party. A party is not necessarily a customer. A party can represent prospects and parts of an ORGANIZATION HIERARCHY, including branches, head offices, corporate conglomerates, that may not necessarily have a billing relationship with the company. Any party that has an active account can be considered a customer. Historical information concerning the party is available in the Parties History. |
|
|
Reference |
Assignment of a PARTY to an ACCOUNT. Depending on type of party, the relationship can be:
|
|
|
Lookup |
Lookup for type of relationship between PARTY and ACCOUNT. Depending on type of party, the relationship can be:
|
|
|
Reference |
Associates one or more Addresses with a PARTY. |
|
|
Base |
The assignment history among ACCESS METHOD, PRODUCT MARKET PLAN, and PARTY. |
|
|
Base |
The status history of assignment among PARTY, ACCESS METHOD, and PRODUCT MARKET PLAN. |
|
|
Reference |
Association of a PARTY with one or more other Parties. The relationships may include relationships between customers or between customers and the telecommunications operator. An example of the later type of relationship, are account management portfolios where an account manager will have a relationship with one or more customers. |
|
|
Lookup |
Lookup for valid reasons parties may be associated with each other. For example:
|
|
|
Lookup |
Lookup for the type of the party relationship. For example:
|
|
|
Reference |
Contact information for a party. |
|
|
Lookup |
Lookup for the type of contact information. For example:
|
|
|
Lookup |
Relationship between PARTY and CONTACT LIST. For example, a party belongs to a contact list. |
|
|
Lookup |
The Role of the PARTY in a CONTACT LIST. |
|
|
Reference |
||
|
Lookup |
Lookup for valid Roles that Parties may be assigned in PARTY CONTRACT ASSIGNMENT. |
|
|
Lookup |
Lookup for type of the PARTY CONTRACT ASSIGNMENT. For example:
|
|
|
Base |
Assignment of cost items to a PARTY. One party may incur multiple costs. For example, for a customer acquisition the customer might be given any of the following items that lead to costs:
Cost might be assigned to multiple parties. For example, for operational cost several organizations may share the same expense on a PROMOTION or CAMPAIGN. |
|
|
Lookup |
Lookup for valid EVENT TYPEs that may be assigned to a party profile for the various event types that may be actioned against a party. |
|
|
Reference |
Assigns a PARTY to one or more GEOGRAPHY ENTITYs. |
|
|
Reference |
Identifying information unique to a PARTY. |
|
|
Lookup |
Lookup for valid types of PARTY IDENTIFICATION. For example:
|
|
|
Base |
Grouping of related contact events with a PARTY into a single thread. |
|
|
Lookup |
Lookup for available reason code and description for why a PARTY may be assigned to an address. For example:
|
|
|
Reference |
Identifies the LOYALTY PROGRAMs that each customer is enrolled in. |
|
|
Lookup |
Defines all roles which a party plays in a CAMPAIGN, such as management or potential customer. |
|
|
Base |
Assignment of PARTY to a given Order. For example:
|
|
|
Lookup |
Lookup for available assignment type codes and descriptions pertaining to PARTY ORDER ASSIGNMENT. For example:
|
|
|
Base |
Response of a PARTY to a PROMOTION. Records the customers response result to the initiative. For example, positive responses:
|
|
|
Lookup |
||
|
Reference |
Assigns party roles for the party. PARTY and PARTY ROLE are an X-X relationship. This relationship may change due to a contract change, or for other reasons. |
|
|
Reference |
Status history of each role that a PARTY has taken. |
|
|
Lookup |
Method used to create the segment, such as K-means clustering in Data Mining. |
|
|
Reference |
||
|
Lookup |
||
|
Lookup |
Higher level of Party Status. For example:
|
|
|
Lookup |
Lookup for valid reasons that may be assigned for a Party Status change. For example:
|
|
|
Base |
Defines current PARTY status history regarding what Operator may be interested. Historical information captured for all lifetime of the customer or dealer. This information may be calculated from internal data; for example, from a payment, or this information may be obtained from an external source such as a credit rating agency. |
|
|
Lookup |
Lookup for status type of the PARTY. For example:
Credit Class is used to rank Customer Credit. For example, the entity value can be:
Or the customer may be defined as:
The party's credit is based on the underlying accounts held by the party. |
|
|
Reference |
Defines a PARTY's relationship to a SUBSCRIPTION. For example: a customer owns a subscription. |
|
|
Lookup |
Lookup for valid Roles that may be assigned to PARTY in regards to the SUBSCRIPTION. |
|
|
Lookup |
Lookup for party type that classifies involved parties according to their inherent characteristics and structure. For example:
|
|
|
Lookup |
Lookup for type of pay category on a pay slip. For example:
|
|
|
Reference |
Subtype of PRODUCT. Pay TV is subscription-based product to deliver TV channels to a customer. |
|
|
Lookup |
Lookup for the type of payment made to the employee. For example:
|
|
|
Derived |
Customer Debt aging results for a DAY. Customer Debt is assigned to a predefined AGE BAND. |
|
|
Aggregate |
Monthly summary of customer debt aging. |
|
|
Reference |
Channel by which customer may pay for service. For example:
|
|
|
Lookup |
Lookup for valid methods of payment. For example:
|
|
|
Lookup |
Lookup for type codes and descriptions for transaction types associated with the Account Payment. The payment may be, for example:
|
|
|
Lookup |
Lookup for reasons for a Packet Control Unit (PCU) outage in GPRS technology. For example:
|
|
|
Lookup |
The definition of the time slots is usage dependent, but it is not common for all the products/packages. The time hours (Peak, off-peak, and night) can be different for different packages. The definition also varies for the following:
For the special days defined in the system. |
|
|
Reference |
Cumulative time transformations at the period level. |
|
|
Reference |
Time transformations at the period level. |
|
|
Reference |
Period level in the planning calendar. |
|
|
Reference |
Quarter level in the planning calendar. |
|
|
Reference |
Season level in the planning calendar. |
|
|
Reference |
Week level in the planning calendar. |
|
|
Reference |
Year level in the planning calendar. |
|
|
Reference |
Reference for available PRODUCT MARKET PLAN subscriptions in an ORGANIZATION BUSINESS UNIT (store, outlet, and so on). |
|
|
Lookup |
Lookup for type of postal service type available to the carrier. For example:
|
|
|
Reference |
Postal Code, Zip Code, or similar geographical designation. |
|
|
Reference |
Subtype of PRODUCT for postpaid wireless. |
|
|
Lookup |
Lookup for categorizations of prepaid allowances. For example:
|
|
|
Lookup |
Lookup for valid deduction types as related to prepaid allowances (PPA). |
|
|
Derived |
Monthly aggregation of prepaid account revenue, including: air time, recharge value and so on, by ACCOUNT, SALES CHANNEL, AGE ON NET BAND. |
|
|
Aggregate |
Monthly summary of prepaid account revenue, including: air time, recharge value, and so on, by CUSTOMER SEGMENT, PRODUCT MARKET PLAN. |
|
|
Derived |
Daily aggregate of free minutes allowance (PPA) for ACCOUNT and PRODUCT MARKET PLAN. |
|
|
Aggregate |
Monthly summary of free minutes allowance (PPA) in a PRODUCT MARKET PLAN. |
|
|
Derived |
Daily aggregate of prepaid calls by ACCOUNT, PRODUCT MARKET PLAN, and ACCESS METHOD. |
|
|
Aggregate |
Monthly summary of prepaid call activity by PRODUCT MARKET PLAN, CUSTOMER TYPE. |
|
|
Lookup |
Lookup for the prepaid mobile event types that may be actioned against a prepaid mobile subscription. The specific event types are implementation specific. For example:
|
|
|
Reference |
Represents each prepaid card. The cards are a means of recharging prepaid mobiles. The card can be physically a Plastic Card or a paper slip with account number and pin code. |
|
|
Base |
Type of ACCOUNT PAYMENT in which a PREPAID MOBILE VOUCHER is recharged. |
|
|
Reference |
The voucher a customer can buy to refill their prepaid account, normally in the form of a paper or plastic card. For example:
|
|
|
Reference |
Type of Service Product. Subtype of SERVICE, for Prepaid Wireless service only. |
|
|
Reference |
The specification of a method to be used to transform the current sell unit retail amount to the price charged to account based on a discount group. |
|
|
Reference |
The product provided by the carrier. Product includes PRODUCT PACKAGE information. The composition of a PRODUCT PACKAGE is tracked in the product relationship. |
|
|
Reference |
Additional descriptive text for a given product, that cannot fit in any other existing attributes, or that should be customized for users with different languages. |
|
|
Reference |
Defines a relationship between a PRODUCT and a related product. |
|
|
Lookup |
Lookup for valid reason codes and descriptions for PRODUCT ASSIGNMENT. |
|
|
Reference |
Various product capabilities, or features. For example:
|
|
|
Lookup |
Lookup for type of PRODUCT CAPABILITY. |
|
|
Reference |
Detailed PRODUCT CAPABILITY information. The information would be quantitative by PRODUCT CAPABILITY TYPE. |
|
|
Lookup |
Lookup for type codes and descriptions for PRODUCT PACKAGE charge on a PRODUCT. For example:
|
|
|
Reference |
Assignment of related PRODUCT CHARGE TYPEs. |
|
|
Lookup |
Lookup for available reasons for PRODUCT CHARGE TYPEs to be related to each other. |
|
|
Lookup |
Lookup for available reasons for Product Charge in the PRODUCT RATING PLAN. For example:
|
|
|
Base |
Sub-table of the COST TYPE table, used to associate a specific cost to a given product. |
|
|
Reference |
Available features that may be associated with one or more PRODUCTs. For example, for a handset there are features such as:
|
|
|
Reference |
Assigns one or more PRODUCT FEATUREs to a PRODUCT. Multiple products may have the same PRODUCT FEATUREs. |
|
|
Reference |
Assignment of valid EQUIPMENT FUNCTIONALITY and PRODUCT VERSIONs to a PRODUCT. |
|
|
Reference |
Assigns a PRODUCT to a GEOGRAPHY ENTITY. This is particularly used for products offered only locally or in a limited region. For example: "Broadband Service" in specific cities and ZIP code areas (typically used for City carriers). |
|
|
Lookup |
Categorizations or Groups into which PRODUCTs may be assigned, usually based on similar functionality. Note: this is different and should not be confused with the PRODUCT MARKET PLAN GROUP entity. For example, the customer may group product in categories such as:
|
|
|
Reference |
Defines relationship of PRODUCT and one or more PRODUCT GROUPs. |
|
|
Lookup |
Lookup for codes and descriptions of types of PRODUCT GROUPs. |
|
|
Reference |
The real instance of a given PRODUCT which a customer can purchase or rent (or eventually gets for free as part of a PRODUCT MARKET PLAN). The product instance is linked to the Customer Order Line Item and relates a product to a customer. For example:
|
|
|
Base |
Defines relationship between EMPLOYEE, PRODUCT MANAGEMENT ROLE, and PRODUCT. |
|
|
Lookup |
Lookup for available reasons for a PRODUCT MANAGEMENT HISTORY relationship. |
|
|
Lookup |
Lookup for valid role codes and descriptions an employee may be assigned in PRODUCT MANAGEMENT HISTORY. For example:
|
|
|
Reference |
Defines how a product is brought to the market, including: positioning, pricing, and bundling details. For example:
|
|
|
Reference |
Assigns Products to PRODUCT MARKET PLANs. |
|
|
Lookup |
Lookup for type of product participation (inclusion) in the market plan. For example:
|
|
|
Base |
Sub-table of the COST TYPE table. This entity associates a specific cost to a given PRODUCT MARKET PLAN. Note that the cost should not be related to the CAMPAIGN or to the PROMOTION, but just to the PRODUCT MARKET PLAN. |
|
|
Reference |
Relationship between PRODUCT MARKET PLAN and Geography. Some PRODUCTs may only be sold in a particular area. |
|
|
Reference |
Hierarchy level to group the various PRODUCT MARKET PLANs. For example:
|
|
|
Reference |
Defines relationship of PRODUCT MARKET PLANs to one or more PRODUCT MARKET PLAN GROUPs. |
|
|
Lookup |
Lookup for the type code and description for a PRODUCT MARKET PLAN GROUP. |
|
|
Lookup |
Type of the PRODUCT MARKET PLAN. For example:
|
|
|
Reference |
||
|
Reference |
Groups of PRODUCTs bundled to serve as basis of a PRODUCT MARKET PLAN. The product package is not customer facing and a customer should subscribe to a product package through the PRODUCT MARKET PLAN. For example:
|
|
|
Reference |
Assigns PRODUCT(s) to a PRODUCT PACKAGE. |
|
|
Lookup |
Lookup for type codes and descriptions for PRODUCT PACKAGE charge on a PRODUCT. For example:
|
|
|
Reference |
Grouping mechanism for prices and usage limits associated with a PRODUCT. |
|
|
Reference |
Detail of PRODUCT RATING PLAN, defines prices and usage limits for each PRODUCT CHARGE TYPE. |
|
|
Lookup |
Lookup for the type of PRODUCT RATING PLAN. |
|
|
Base |
Status history of PRODUCT. |
|
|
Lookup |
Lookup for the type of the product status. |
|
|
Lookup |
Lookup for the type of the PRODUCT. For example:
|
|
|
Reference |
Iteration of a PRODUCT created when a minor change is made to the PRODUCT setting that does not require creating a new PRODUCT. |
|
|
Reference |
The promotion reflects the tactics that an operator undertakes to generate increased incremental sales or usage volume for a specific product within a promotional event. Promotions are frequently communicated as part of a marketing campaign to ensure that awareness is generated with the target audience. |
|
|
Base |
Assigns a particular CUSTOMER SEGMENT, cluster, to a given PROMOTION or list of promotions. The customer segments are generated by certain analytic applications, including Oracle Mining, and this assignment tracks the usage of customer segments in the PROMOTION. |
|
|
Base |
Defines the relationship between a CONTACT LIST and a PROMOTION: the contact list has been used for a marketing campaign to which a specific promotion was proposed. |
|
|
Base |
Subtype of the COST, which is used to associate a specific cost uniquely associated to a given promotion. For example, a rent fee for the location where the operator performs the promotion. |
|
|
Base |
A history of campaign party role about management of a campaign EPISODE. |
|
|
Reference |
Associates a market plan to a PROMOTION. Typically, this applies when a given market plan is offered with an additional discount (PROMOTION) during a certain period. |
|
|
Reference |
Details regarding each CAMPAIGN MESSAGE broadcast through a MEDIA OBJECT. |
|
|
Lookup |
Lookup for the prospect reaction to a specific PROMOTION during a sales campaign. For example:
|
|
|
Lookup |
Lookup for valid type codes and descriptions of Promotion Term associated with a PROMOTION TERM VALUE. For example:
|
|
|
Base |
Assigns PROMOTION TERM TYPE to a PROMOTION with a value corresponding to the Term Type. For example:
|
|
|
Lookup |
Lookup for the type of PROMOTION (each for either a limited time or for the contract duration). For example:
|
|
|
Reference |
An individual, collection of individuals, company, or public institution that does not currently purchase merchandise or services, but who may in the future. A prospect may also be a CUSTOMER of one PRODUCT (already purchased) that does not currently purchase another PRODUCT (may purchase). A prospect has no recorded relationship with the provider. |
|
|
Reference |
Attributes of an individual prospect, one who is not an organization. |
|
|
Reference |
Attributes of a prospect organization. |
|
|
Base |
Pay TV full channel activation event. |
|
|
Base |
The detail of QPI service. |
|
|
Base |
Customer usage of PAY TV service. |
|
|
Reference |
Publication to which the MEDIA OBJECT used in CAMPAIGN belongs. |
|
|
Lookup |
Lookup for code and description describing the type of publication. |
|
|
Reference |
Quarter Hour as defined in Time Hierarchy. |
|
|
Reference |
Cumulative time transformations at the quarter level. |
|
|
Reference |
Transformation with respect to a quarter. For example:
|
|
|
Lookup |
Lookup for Rating Method Type code and description. For example:
|
|
|
Lookup |
Lookup for the bands of revenue earned from the sale of recharge coupons, for prepaid, which is called recharge revenue. The recharge revenue is to be analyzed for all currently active prepaid subscribers and for all churned subscribers until the time of termination. For example, the revenue can be banded by creating slabs for recharge revenue of $0-$25, $25-$50, and so on. |
|
|
Derived |
The daily aggregate of loyalty point redemption by CREDIT CATEGORY, LOYALTY PROGRAM CHANNEL, AGE ON NET BAND, and EMPLOYEE. Daily aggregation of LOYALTY PROGRAM redemption statistics by LOYALTY PROGRAM CHANNEL, SALES CHANNEL, AGE ON NET BAND, CREDIT CATEGORY, and EMPLOYEE. |
|
|
Aggregate |
Monthly summary of LOYALTY PROGRAM redemption statistics by LOYALTY PROGRAM CHANNEL |
|
|
Lookup |
Lookup for redemption type that maintains all possible point redemption types and organizes redemption data by redemption type for analysis purposes. |
|
|
Reference |
Subtype of internal organization. This usually lists the shops where the communications service provider presents the products and sells directly to customers. Note that a retail store may contain several SELLING LOCATIONs. |
|
|
Reference |
Reference list of all wireless or Radio Frequency (RF) carriers. |
|
|
Derived |
Daily aggregate of Radio Frequency (RF) Network Capacity utilization statistics. Radio Frequency (RF) interfaces are present at two levels in the network:
|
|
|
Aggregate |
Monthly summary of Radio Frequency (RF) Network Capacity utilization statistics. |
|
|
Reference |
Sub-table of SUPPLEMENTARY SERVICE, by which a customer can download music as a ringtone for the phone. |
|
|
Lookup |
Lookup for the various roaming types to classify the calls. For example:
|
|
|
Reference |
Hierarchy among the job roles within an organization. |
|
|
Reference |
In IN Network or Wireless, many different type of devices such as VLR, HLR, SCP servers are utilized in network to decide the call routing. This entity tracks the device information. |
Table 2-28 S to V Entity Description
| Entity Name | Type | Description |
|---|---|---|
|
|
Derived |
Daily aggregate of campaign results by PROMOTION RESULT TYPE and Sales Campaign Client Code. |
|
Aggregate |
Monthly summary of Sales Campaign results by PRODUCT MARKET PLAN, CAMPAIGN CHANNEL, PROMOTION RESULT TYPE. |
|
|
Reference |
Channel used to communicate with parties for sales purposes. For example:
Sales channels are represented by the channel level, which also becomes the lowest level for the channel dimension. |
|
|
Reference |
The sales representative who sells the product to the customer. For example:
|
|
|
Base |
The sales commission earned by sales agent because of the contract. |
|
|
Base |
The sales commission issued to the sales agent. |
|
|
Reference |
The sales commission plan for particular PRODUCT PACKAGE and sales agent level. |
|
|
Reference |
Details about the SALES COMMISSION PLAN per PRODUCT MARKET PLAN and PROMOTIONs, including sales quota and commission rate. |
|
|
Derived |
Daily aggregate of sales by SALES CHANNEL, PRODUCT MARKET PLAN, business unit, sales representative, CUSTOMER. |
|
|
Aggregate |
Monthly summary of sales by SALES CHANNEL, PRODUCT MARKET PLAN, business unit, sales representative. |
|
|
Derived |
Monthly summary of sales representative performance measured by sales, commission, and so on. |
|
|
Reference |
A list of specific groupings of questions or statements presented to individuals during a survey. |
|
|
Reference |
Initiative questions documents the questions asked of the customer as part of the initiative. |
|
|
Lookup |
The domain of values used to group script items. For example:
|
|
|
Lookup |
Seasons and their attributes. Seasons are arbitrary periods around which some providers organize their buying and selling patterns. Each day should fall within no more than one season. |
|
|
Reference |
Second hierarchy level as defined in Time Hierarchy. |
|
|
Lookup |
Lookup for type and description of security requirements that may be associated with an ITEM. |
|
|
Reference |
Minimum and Maximum scores for each segment associated with an ACCOUNT SEGMENT or CUSTOMER SEGMENT. |
|
|
Lookup |
Lookup for type codes and descriptions used to define ACCOUNT SEGMENTATION MODEL or CUSTOMER SEGMENTATION MODEL. |
|
|
Reference |
Physical location in a RETAIL STORE specifically dedicated to selling or displaying merchandise. |
|
|
Lookup |
Lookup for type code and description used to define a SELLING LOCATION: For example:
|
|
|
Reference |
A subtype of PRODUCT for all types of telecommunications services. |
|
|
Lookup |
The class of the services. For QoS reason, the call can be divided into different classes (Basically might be home line or business line, or others). It can also be divided by other aspect, line utilizing Circuit Line or IP packets, and so on. |
|
|
Lookup |
Lookup for the type or base to define the SERVICE CLASS. |
|
|
Reference |
The geographic area covered by service provider with certain product combination. Service areas are defined so that service providers can determine the demographic / psychographic / population data the geography served by the network. |
|
|
Lookup |
Lookup for type code and description for SERVICE COVERAGE AREA. |
|
|
Reference |
The detail about service coverage on lowest level. For example:
|
|
|
Reference |
Assignments between NETWORK TOUCHPOINT, EQUIPMENT, and SERVICE according to which SERVICE was tied to which NETWORK TOUCHPOINT through which EQUIPMENT INSTANCE. |
|
|
Base |
Subtype of PARTY INTERACTION THREAD, specifically dedicated to a service request that may trigger a customer field service support order. |
|
|
Reference |
Set-top box for Television service. |
|
|
Reference |
Set-top box model specification. |
|
|
Derived |
Daily aggregate of Lines Count by PRODUCT MARKET PLAN. For example:
|
|
|
Aggregate |
Monthly summary of Lines Count by PRODUCT MARKET PLAN. The usage and profitability is analyzed in this entity. For example:
|
|
|
Derived |
Daily aggregate of shop efficiency details including customer and transaction counts, wait times, and so on, by ORGANIZATION BUSINESS UNIT and GEOGRAPHY REGION. |
|
|
Aggregate |
Monthly summary of shop efficiency details including customer and transaction counts, wait times, and so on, by ORGANIZATION BUSINESS UNIT and GEOGRAPHY REGION. |
|
|
Reference |
Assigns one industry to another industry in Standard Industrial Classification (SIC). |
|
|
Lookup |
Lookup for reason codes and descriptions that describe why two industries are assigned in the Standard Industrial Classification (SIC). |
|
|
Lookup |
A classification group for Standard Industrial Classification (SIC). For example: A. Division A: Agriculture, Forestry, And Fishing:
|
|
|
Reference |
The base level of SIC classification. For more information see SIC CLASSIFICATION. |
|
|
Lookup |
The middle level of the industry classification hierarchy. |
|
|
Reference |
A subscriber identity module (SIM) on a removable SIM card securely stores the service-subscriber key (IMSI) used to identify a subscriber on mobile telephony devices (such as a mobile phone). Also used for UIM (User Identity Module) in the CDMA (Code Division Multiple Access) network. |
|
|
Reference |
A history of relationship between ACCESS METHOD and SIM CARD. Many access methods can be assigned to one SIM Card at any given time. |
|
|
Lookup |
Lookup for valid reason codes and descriptions to describe relationship between SIM CARD and ACCESS METHOD. |
|
|
Lookup |
Lookup for valid reason codes and descriptions describing why a SIM CARD has been activated. |
|
|
Lookup |
Usage states that a SIM CARD may be in. For example:
|
|
|
Reference |
A history of relationship between a HANDSET INSTANCE and a SIM CARD. SIM Cards can be swapped between handsets. |
|
|
Reference |
A history of relationship between the SIM CARD and a SUBSCRIPTION. |
|
|
Lookup |
A reason why a SIM CARD is associated with a SUBSCRIPTION. |
|
|
Lookup |
Lookup for the types of SIM CARD. For example:
|
|
|
Reference |
Subtype of VALUE ADDED SERVICE. This entity defines the information relative to the Short Message Service (SMS). Do not confuse this entity with SMS EVENT. |
|
|
Base |
Subtype of NETWORK EVENT, which collects all information of product usage of Short Message Service (SMS). |
|
|
Reference |
Subtype of PRODUCT RATING PLAN, reserved for Short Message Service (SMS), and also Multimedia Messaging Service (MMS), service. |
|
|
Reference |
Entity holds the most detailed level of Standard Occupational Classification (SOC) job classification. For example:
|
|
|
Reference |
Lookups for the categories in the Standard Occupational Classification (SOC) in which each occupation in the SOC is placed. The hierarchy in SOC is typically: NN-MMM0. These job categories correspond to the 449 "broad occupations" or categories. For example:
|
|
|
Reference |
Lookups for the groups in the Standard Occupational Classification (SOC) in which each occupation in the SOC is placed. The hierarchy of SOC is typically: NN-MM00. For example:
|
|
|
Reference |
Lookups from the (23) major groups in the Standard Occupational Classification (SOC) in which each occupation in the SOC is placed. The hierarchy of SOC is typically: NN-0000. For example:
|
|
|
Reference |
System of record from which information was loaded. |
|
|
Reference |
Track Key of the PARTY, customer or employee, in the originating source system. This key can track information back to the source management system. |
|
|
Lookup |
Lookup for type code and description used to describe SOURCE SYSTEM. For example:
|
|
|
Lookup |
Lookup for valid Subscriber activation code and reasons used to describe Subscriber Activation. For example:
|
|
|
Aggregate |
Monthly summary of Subscriber Churn by PRODUCT, PRODUCT MARKET PLAN, CUSTOMER TYPE, GEOGRAPHY ENTITY, ORGANIZATION BUSINESS UNIT. |
|
|
Derived |
Monthly aggregate of Subscriber Churn information by ACCOUNT, PRODUCT MARKET PLAN, SALES CHANNEL, AGE BAND, AGE ON NET BAND, CREDIT CATEGORY, DEBT AGING BAND, CUSTOMER REVENUE BAND, ARPU BAND, CUSTOMER. |
|
|
Reference |
The record of customer using a product or service which may be based on a contract. Customer's subscription to services is the basis of billing and network usage authorization. |
|
|
Reference |
Relational assignment of one SUBSCRIPTION to another SUBSCRIPTION. This is optional. |
|
|
Lookup |
Lookup for type codes and descriptions pertaining to SUBSCRIPTION ASSIGNMENT. |
|
|
Lookup |
Lookup for available type codes and descriptions for Subscription Events. |
|
|
Reference |
The relationship between SUBSCRIPTION and PRODUCT MARKET PLANs. A SUBSCRIPTION may be reassigned to different PRODUCT MARKET PLANs during its lifetime. |
|
|
Reference |
Defines the class of service for a SUBSCRIPTION. |
|
|
Lookup |
Lookup for available code and description for the status of a SUBSCRIPTION. For example:
|
|
|
Lookup |
Lookup for category codes and descriptions used to group or categorize SUBSCRIPTION STATUS. |
|
|
Base |
A history of the status of a SUBSCRIPTION. For example:
The subscription can simultaneously contain multiple status. For example, the subscription could be Active and In_Debt, or amount below threshold. |
|
|
Lookup |
Lookup for available reason codes and descriptions for defining why a SUBSCRIPTION may be assigned a status. |
|
|
Lookup |
Lookup for available type codes and descriptions pertaining to SUBSCRIPTIONs and PRODUCTs to which Values may be assigned. For example:
|
|
|
Base |
Value assignments for Subscription Terms as pertains to a SUBSCRIPTION and PRODUCT. For example:
The value can vary at different time periods. For example, the monthly fee might be 100 for first six months, and 80 for last six months. A penalty calculation can also be assigned based on the months left in a contract. |
|
|
Lookup |
Lookup for available type codes and descriptions for SUBSCRIPTIONs. For example:
|
|
|
Aggregate |
Monthly summation of the amount budgeted for the items to be given on subsidy by PRODUCT MARKET PLAN, and CUSTOMER TYPE, excluding the NVP scheme items and give-away items. |
|
|
Derived |
Monthly aggregation of the amount budgeted for the items to be given on subsidy by PRODUCT MARKET PLAN and CUSTOMER TYPE, excluding the NVP scheme items and give-away items. |
|
|
Lookup |
Lookup for type code and description of a Subsidy. |
|
|
Reference |
Subtype of PRODUCT that may include supplementary services to complement and support existing services such as telephone and data services. For example:
|
|
|
Aggregate |
Monthly summation of Charge and Billing details for SUPPLEMENTARY SERVICE usage by Business Unit, PRODUCT MARKET PLAN, and PRODUCT. |
|
|
Derived |
Monthly aggregation of Charge and Billing details for SUPPLEMENTARY SERVICE usage by Business Unit, Billing Status Type, PRODUCT MARKET PLAN, and PRODUCT. |
|
|
Reference |
Network switches or exchanges. A switch may be a PSTN (wireline) digital or analog, or a GSM Mobile Station controller (wireless). |
|
|
Reference |
Lookup for capabilities that may be assigned to a SWITCH TYPE. |
|
|
Lookup |
Lookup for type codes and descriptions used to categorize SWITCH CAPABILITY. |
|
|
Reference |
Command which is sent to the switch, telling it to take an action. For example, activate a port with specified parameters. |
|
|
Reference |
Assigns a routing device to a switch in any type of network. |
|
|
Lookup |
Classification of Switch Type and Manufacturer. |
|
|
Reference |
The ACCESS METHODs associated with a PROMOTION. |
|
|
Reference |
||
|
Reference |
||
|
Reference |
GEOGRAPHY ENTITYs targeted by a PROMOTION. |
|
|
Lookup |
Lookup for valid Type codes and descriptions as pertain to a PROMOTION. For example:
|
|
|
Lookup |
Lookup for valid tax exempt codes and descriptions as pertains to an ITEM. |
|
|
Lookup |
Lookup for the types of Traffic Channel. For example:
|
|
|
Lookup |
Technology names and descriptions that can define a NETWORK ELEMENT. For example:
|
|
|
Lookup |
Lookup for available type codes and descriptions that can classify or categorize a TECHNOLOGY. For example:
|
|
|
Reference |
The telephone number pool allocated to the TELCO operator. |
|
|
Lookup |
Band of call duration. For example:
|
|
|
Reference |
Reference entity defining the time slot within a DAY in relation to HOURs, HALF HOURs and QUARTER HOURs. This is used in all time derived and aggregation tables. |
|
|
Reference |
Relates the calendar day to a season and to a standard day. Specifies the relationship between a given day and all days of a given season up to that day. |
|
|
Reference |
Relates the calendar week to a season and to a standard week. Specifies the relationship between a given week and all days of a given season up to that week. |
|
|
Lookup |
Lookup for the Geographic time zone as related to the Greenwich Mean Time (GMT +0.00). |
|
|
Reference |
Type of PRODUCT INSTANCE associating a Television Channel with a PTV USAGE EVENT. |
|
|
Lookup |
Lookup for valid type codes and descriptions for Unified Messaging Services (UMS). The UMS access type indicates the way customers are accessing their mailboxes. This is especially applicable to UMS users who can access their mailbox ether using the standard method, with a specified number or by using Internet mail. |
|
|
Base |
Subtype of NETWORK EVENT. In the UMS notification type dimension, Unified Messaging Service (UMS) is an advanced version of Voice Message Service (VMS). As it is possible to notify the subscriber using UMS by either SMS or by internet mail, similarly a subscriber can access a mailbox in different ways, including by calling a standard access number or through the internet. The information related to UMS access is to be analyzed by the type of access. UMS access type dimension will be used to fulfill this requirement. |
|
|
Lookup |
Lookup for the type of UMS events. For example:
|
|
|
Lookup |
Lookup for possible measurement units valid for the data within the system. For example:
|
|
|
Reference |
Associative entity for EMPLOYEE, JOB ROLE, Business Unit; associates a unique ID for every job role that an employee performs at a particular business unit. An employee appears only one time in the EMPLOYEE entity, but in USER entity, the employee appears on time for each job role at each business unit. |
|
|
Reference |
Type of product consisting of supplementary or value added services such as Call Forward, Call barring, CLI, CLIR, UMS, or VMS. |
|
|
Lookup |
Lookup for unit of measure for the value. For example a customer or a profile can be valued in terms of monetary value or time (a customer for next three years). |
|
|
Lookup |
Lookup for available type codes and descriptions pertaining to defining the derived value of a CUSTOMER or PROSPECT. |
|
|
Reference |
Type of Subscription that includes VALUE ADDED SERVICE. |
|
|
Aggregate |
Monthly Summary of VALUE ADDED SERVICE Details by CUSTOMER TYPE. |
|
|
Derived |
Monthly Aggregation of VALUE ADDED SERVICE Details by CUSTOMER and ACCESS METHOD. |
|
|
Derived |
Daily usage statistics for all value added services that are content based (and some others). This includes: M2M, P2P, and SMS, MMS, ringtone, music, video, email, Universal (Voice/Email) message, and others. |
|
|
Aggregate |
Monthly aggregation of VAS usage statistics, from VAS USAGE DAY DRVD. |
|
|
Reference |
Supplier or source of equipment or supplies. |
|
|
Base |
Single or recurring appointment times allocated for VENDOR representative to visit the Provider or Retail Site. |
|
|
Lookup |
Lookup for the classification of Vendors. For example:
|
|
|
Reference |
Time bound agreement with VENDOR. |
|
|
Reference |
Defines the relationship between VENDOR and FACTOR COMPANY. |
|
|
Reference |
Score assigned to VENDOR based on performance criteria. |
|
|
Lookup |
Lookup for type codes and descriptions of VENDOR RATING performance criteria. |
|
|
Reference |
A Site or Location associated with a VENDOR from which VENDOR may do business with Provider. A Vendor site may be an Office, Warehouse, Dispatch Center, and so on. |
|
|
Reference |
Association of VENDOR SITE with COURIER. |
|
|
Lookup |
Lookup for valid type codes and descriptions pertaining to VENDOR SITE. For example:
|
|
|
Reference |
Type of Business Unit formed for a specific purpose. For example:
|
|
|
Reference |
Subtype of SERVICE. |
|
|
Derived |
Daily aggregate of Voice Call statistics by TIME SLOT, Business Unit, County, PRODUCT, CUSTOMER TYPE, Call Source, Call Destination, CALL DIRECTION, Call Success/Failure, Roaming Service. |
|
|
Base |
The subtype of Network event, specialized for Voice Over IP (VOIP) Calls. |
|
|
Aggregate |
Monthly Summary of Voice Call statistics by Business Unit, County, PRODUCT, CUSTOMER TYPE, CALL CATEGORY, CALL DIRECTION, Call Success/Failure. |
|
|
Lookup |
Characterizes network events by volume. The volume characteristic may be in units of bytes, minutes, packets, downloads. The entity is used as part of the rating of calls and other network events. |
Table 2-29 W to Z Entity Descriptions
| Entity Name | Type | Description |
|---|---|---|
|
Reference |
Reference of the various “weather” conditions, in a very general sense, affecting a given day. There is a difference between internal "weather" (a flood in a store, an employee strike, and so on) and external "weather" (storm, flood, snow, and so on). This information is useful in relation to a network failure. |
|
|
Reference |
Cumulative time transformations at the week level. |
|
|
Reference |
Time transformations at the week level. |
|
|
Reference |
Calendar weekdays. |
|
|
Base |
Defines occurrence of wireless call. |
|
|
Base |
Type of network event, to track wireless content downloading such as music, video clips, and so on. |
|
|
Derived |
Derived from NETWORK ELEMENT Hierarchy for analytical purposes. |
|
|
Reference |
Subtype of PRODUCT RATING PLAN, reserved for wireless voice and data services. |
|
|
Reference |
Transformations at the year level. |