Skip Headers
Oracle® Communications Data Model Reference
Release 11.3.2

E28440-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 Logical Data Model Foundation

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:

Major Subject Areas and Related Entities

The following describes the main entities related to some major or typical subject areas in Oracle Communications Data Model:

Note:

The entity-relationship figures of the major reference entities in those subject areas are available with the Oracle Communications Data Model IP Patch. The IP Patch includes additional documentation. To obtain the IP Patch and for the latest information about Oracle Communications Data Model patch sets, go to My Oracle Support at https://support.oracle.com.

Subject Area: Customer

Table 2-8 lists the entities associated with the subject area Customer.

Table 2-8 Entities of Subject Area: Customer

Customer Entity List

ACCOUNT

ACCOUNT PAYMENT

ADDRESS LOCATION

AGREEMENT

ARPU BAND

BARING REASON

BLACK LIST HISTORY

CALENDAR MONTH

CREDIT SCORE PROVIDER

CUSTOMER

CUSTOMER ACCOUNT

CUSTOMER ADDRESS

CUSTOMER AFFILIATION

CUSTOMER CLASS

CUSTOMER CLASS ASSIGNMENT

CUSTOMER CLUSTER

CUSTOMER CLUSTER TYPE

CUSTOMER COMMUNITY

CUSTOMER COST

CUSTOMER DOCUMENT

CUSTOMER FACING SERVICE

CUSTOMER FACING SERVICE ROLE

CUSTOMER FACING SERVICE SPECIFICATION

CUSTOMER FACING SERVICE SPECIFICATION ATOMIC

CUSTOMER FACING SERVICE SPECIFICATION COMPOSITE

CUSTOMER FACING SERVICE SPECIFICATION ROLE

CUSTOMER FACING SERVICE SPECIFICATION VERSION

CUSTOMER FIELD SERVICE ACTIVITY

CUSTOMER FIELD SERVICE DETAIL

CUSTOMER GROUP

CUSTOMER GROUP ASSIGNMENT

CUSTOMER GROUP ITEM

CUSTOMER INDIVIDUAL

CUSTOMER OCCASION

CUSTOMER OCCASION TYPE

CUSTOMER ORDER

CUSTOMER ORDER DOCUMENT

CUSTOMER ORDER LINE ITEM

CUSTOMER ORDER LINE ITEM STATE ASSIGN

CUSTOMER ORDER PAYMENT

CUSTOMER ORDER PRIORITY TYPE

CUSTOMER ORDER STATE ASSIGNMENT

CUSTOMER ORDER STATE CHANGE REASON

CUSTOMER ORGANIZATION

CUSTOMER PREFERENCE

CUSTOMER RELATIONSHIP

CUSTOMER RELATIONSHIP TYPE

CUSTOMER RESTRICTED INFO

CUSTOMER REVENUE BAND

CUSTOMER REVENUE BAND ASSIGNMENT

CUSTOMER REVENUE TYPE

CUSTOMER SCORE

CUSTOMER SEGMENT

CUSTOMER SEGMENTATION MODEL

CUSTOMER SIC ASSIGNMENT

CUSTOMER SOURCE

CUSTOMER STATUS REASON

CUSTOMER TYPE

DERIVED VALUE

EDUCATION

EVENT PARTY INTERACTION

EXTERNAL CREDIT PROFILE

EXTERNAL CREDIT PROFILE ASSIGNMENT

EXTERNAL ORGANIZATION TYPE

GENDER

HOUSEHOLD

INITIATIVE RESULT TYPE

INITIATIVE TYPE

INVOICE

JOB

LANGUAGE

MARITAL STATUS

PARTY

PARTY PROMOTION RESPONSE

PARTY STATUS HISTORY

PROMOTION

PROSPECT

SEGMENT CRITERIA

SOC JOB

SOC JOB CATEGORY

SOC JOB GROUP

UNIT OF MEASURE

VALUE TYPE


Subject Area: Prepaid-Balance and Voucher

Table 2-10 lists the entities associated with the subject area Prepaid Balance and Voucher.

Subject Area: Product Offering and Product Subscription

Table 2-22 lists the entities associated with the subject area Product Offering and Product Subscription.

Table 2-22 Entities of Subject Area: Product Offering and Product Subscription

Product Offer and Product Subscription Entity List

PRODUCT OFFERING

PRODUCT OFFERING ASSIGNMENT TYPE

PRODUCT OFFERING AVAILABILITY

PRODUCT OFFERING COST

PRODUCT OFFERING DOCUMENT REQUIREMENT

PRODUCT OFFERING GEOGRAPHY ASSIGNMENT

PRODUCT OFFERING GROUP

PRODUCT OFFERING GROUP ASSIGNMENT

PRODUCT OFFERING GROUP TYPE

PRODUCT OFFERING MANAGEMENT

PRODUCT OFFERING MARKET SEGMENT AVAILABILITY

PRODUCT OFFERING ORGANIZATION AVAILABILITY

PRODUCT OFFERING PRICE

PRODUCT OFFERING PRICE COMPONENT

PRODUCT OFFERING PRICE COMPOSITE

PRODUCT OFFERING PRICE POLICY ACTION

PRODUCT OFFERING PRICE POLICY CONDITION

PRODUCT OFFERING PRICE POLICY VALUE

PRODUCT OFFERING PRICE POLICY VARIABLE

PRODUCT OFFERING PRICE RECURRING

PRODUCT OFFERING PRICE RELATIONSHIP

PRODUCT OFFERING PRICE TYPE

PRODUCT OFFERING PRODUCT ASSIGNMENT

PRODUCT OFFERING PRODUCT OFFERING PRICE ASSIGNMENT

PRODUCT OFFERING RATING PLAN

PRODUCT OFFERING RATING PLAN DETAIL

PRODUCT OFFERING RELATIONSHIP

PRODUCT OFFERING RELATIONSHIP TYPE

PRODUCT OFFERING SUBSTITUTE BY DOC

PRODUCT OFFERING TERM

PRODUCT SPEC CHAR RESOURCE SPEC CHAR ASSIGNMENT

PRODUCT SPEC CHAR VAL RESOURCE SPEC CHAR VAL ASSIGNMENT

PRODUCT SPECIFICATION GROUP

PRODUCT SPECIFICATION GROUP TYPE

PRODUCT SPECIFICATION

PRODUCT SPECIFICATION ADDITIONAL TEXT

PRODUCT SPECIFICATION ASSIGNMENT REASON

PRODUCT SPECIFICATION CATEGORY

PRODUCT SPECIFICATION CHARACTERISTIC

PRODUCT SPECIFICATION CHARACTERISTIC CONFIGURABLE ASSIGNMENT

PRODUCT SPECIFICATION CHARACTERISTIC RELATIONSHIP

PRODUCT SPECIFICATION CHARACTERISTIC USE

PRODUCT SPECIFICATION CHARACTERISTIC VALUE

PRODUCT SPECIFICATION CHARACTERISTIC VALUE RELATIONSHIP

PRODUCT SPECIFICATION CHARACTERISTIC VALUE USE

PRODUCT SPECIFICATION COLUMN

PRODUCT SPECIFICATION COST

PRODUCT SPECIFICATION COVERAGE AREA TYPE

PRODUCT SPECIFICATION COVERAGE GEO DETAIL

PRODUCT SPECIFICATION GROUP ASSIGNMENT

PRODUCT SPECIFICATION HISTORY

PRODUCT SPECIFICATION MANAGEMENT HISTORY

PRODUCT SPECIFICATION MANAGEMENT REASON

PRODUCT SPECIFICATION MANAGEMENT ROLE

PRODUCT SPECIFICATION NETWORK ASSIGNMENT

PRODUCT SPECIFICATION RELATIONSHIP

PRODUCT SPECIFICATION STATUS HISTORY

PRODUCT SPECIFICATION STATUS TYPE

PRODUCT SPECIFICATION TYPE

PRODUCT SPECIFICATION VERSION


Subject Area: Product and Product Specification

Table 2-10 lists the entities associated with the subject area Product and Product Specification.

Table 2-24 Entities of Subject Area: Product and Product Specification

Product and Product Specification Entity List

ACCESSORIES

ADDITIONAL TEXT

BRAND

BROADBAND RATING PLAN

COMMUNICATION SERVICE

COMPOSITE PRODUCT SPECIFICATION

COMPOSITE PRODUCT SPECIFICATION ASSIGNMENT

COMPOSITE PRODUCT SPECIFICATION CHARGE TYPE

CONTENT

CURRENCY

CUSTOMER ORDER

DOCUMENT CONDITION TYPE

DOCUMENT TYPE

EQUIPMENT

EQUIPMENT FUNCTIONALITY

EQUIPMENT FUNCTIONALITY ASSIGNMENT

EQUIPMENT INSTANCE

EXTERNAL OPERATOR

FIXED LINE RATING PLAN

GEOGRAPHY ENTITY

HANDSET MODEL

INVENTORY ITEM STATE

ITEM SPECIFICATION

LANGUAGE

MARKET SEGMENT

NETWORK TOUCHPOINT

ORGANIZATION BUSINESS UNIT

ORGANIZATION ITEM SELLING PRICE

ORGANIZATION WAREHOUSE

PARTY

POLICY

POLICY RULE

POLICY SET

PREPAID VOUCHER

PREPAID VOUCHER SPECIFICATION

PRICE DERIVATION RULE

PRICE TYPE

PRICE TYPE RELATION REASON

PRICE TYPE RELATIONSHIP

PRODUCT

PRODUCT BRAND

PRODUCT CATALOG

PRODUCT CATALOG GEOGRAPHY ASSIGNMENT

PRODUCT CATALOG PRESENTATION TYPE

PRODUCT CATALOG PRODUCT OFFERING ASSIGNMENT

PRODUCT CATALOG SALES CHANNEL ASSIGNMENT

PRODUCT CATALOG TYPE

PRODUCT COVERAGE AREA

PRODUCT FUNCTIONALITY DEPENDENCY

PRODUCT LINE

PRODUCT OFFERING

PRODUCT OFFERING ASSIGNMENT TYPE

PRODUCT OFFERING AVAILABILITY

PRODUCT OFFERING DOCUMENT REQUIREMENT

PRODUCT OFFERING GEOGRAPHY ASSIGNMENT

PRODUCT OFFERING GROUP

PRODUCT OFFERING GROUP ASSIGNMENT

PRODUCT OFFERING GROUP TYPE

PRODUCT OFFERING MARKET SEGMENT AVAILABILITY

PRODUCT OFFERING ORGANIZATION AVAILABILITY

PRODUCT OFFERING PRICE

PRODUCT OFFERING PRICE TYPE

PRODUCT OFFERING PRODUCT ASSIGNMENT

PRODUCT OFFERING PRODUCT SPECIFICATION ASSIGNMENT

PRODUCT OFFERING RELATIONSHIP

PRODUCT OFFERING RELATIONSHIP TYPE

PRODUCT OFFERING SUBSTITUTE BY DOC

PRODUCT OFFERING TERM

PRODUCT OFFERING TYPE

PRODUCT SPECIFICATION GROUP

PRODUCT SPECIFICATION GROUP TYPE

PRODUCT SPECIFICATION

PRODUCT SPECIFICATION ADDITIONAL TEXT

PRODUCT SPECIFICATION ASSIGNMENT REASON

PRODUCT SPECIFICATION CATEGORY

PRODUCT SPECIFICATION CHARACTERISTIC

PRODUCT SPECIFICATION CHARACTERISTIC RELATIONSHIP

PRODUCT SPECIFICATION CHARACTERISTIC USE

PRODUCT SPECIFICATION CHARACTERISTIC VALUE

PRODUCT SPECIFICATION CHARACTERISTIC VALUE RELATIONSHIP

PRODUCT SPECIFICATION CHARACTERISTIC VALUE USE

PRODUCT SPECIFICATION COVERAGE AREA TYPE

PRODUCT SPECIFICATION COVERAGE GEO DETAIL

PRODUCT SPECIFICATION GROUP ASSIGNMENT

PRODUCT SPECIFICATION MANAGEMENT HISTORY

PRODUCT SPECIFICATION MANAGEMENT REASON

PRODUCT SPECIFICATION MANAGEMENT ROLE

PRODUCT SPECIFICATION NETWORK ASSIGNMENT

PRODUCT SPECIFICATION RELATIONSHIP

PRODUCT SPECIFICATION STATUS HISTORY

PRODUCT SPECIFICATION STATUS TYPE

PRODUCT SPECIFICATION TYPE

PRODUCT SPECIFICATION VERSION

PRODUCT STATUS HISTORY

PRODUCT STATUS TYPE

RATING METHOD TYPE

SALES CHANNEL

SERVICE SPECIFICATION

SET TOP BOX MODEL

SSIM CARD

SIM CARD HANDSET ASSIGNMENT

SMS RATING PLAN

TV CHANNEL

VALUE ADDED SERVICE

VENDOR

WIRELESS RATING PLAN


Subject Area: Promotion and Campaign

Table 2-10 lists the entities associated with the subject area Promotion and Campaign.

Table 2-25 Entities of Subject Area: Promotion and Campaign

Promotion and Campaign Entity List

CAMPAIGN

CAMPAIGN CHANNEL

CAMPAIGN CHANNEL ASSIGNMENT

CAMPAIGN CHANNEL TYPE

CAMPAIGN CHARACTERISTIC

CAMPAIGN CHARACTERISTIC VALUE

CAMPAIGN MANAGEMENT HISTORY

CAMPAIGN MESSAGE

CAMPAIGN MESSAGE CREATIVE

CAMPAIGN MESSAGE DEPICTION

CAMPAIGN RELATIONSHIP

CAMPAIGN STATUS

CAMPAIGN TERM VALUE

CAMPAIGN TYPE

CONTACT LIST

CONTACT LIST CHANGE REASON

CONTACT LIST RECURRENCE TYPE

CUSTOMER SEGMENT

EVENT PARTY INTERACTION

GEOGRAPHY ENTITY

INITIATIVE TYPE

MARKET AREA

MARKET SEGMENT

MARKET SEGMENT INCLUSION

MEDIA OBJECT

MEDIA OBJECT ASSIGNMENT

MEDIA OBJECT TYPE

ORGANIZATION BUSINESS UNIT

PARTNER PROMOTION PROGRAM

PARTY

PARTY CONTACT LIST PARTICIPATION

PARTY CONTACT LIST ROLE

PARTY MANAGEMENT ROLE

PARTY MARKET SEGMENT ASSIGNMENT

PARTY PROMOTION RESPONSE

PRODUCT

PROMOTION

PROMOTION CLUSTER USAGE

PROMOTION CONTACT LIST UTILIZATION

PROMOTION MANAGEMENT HISTORY

PROMOTION MESSAGE RENDERING

PROMOTION PRODUCT CATALOG ASSIGNMENT

PROMOTION PRODUCT OFFERING ASSIGNMENT

PROMOTION RELATIONSHIP

PROMOTION RESULT TYPE

PROMOTION SALES CHANNEL ASSIGNMENT

PROMOTION TERM TYPE

PROMOTION TERM VALUE

PROMOTION TYPE

PROPOSAL

PROPOSAL RELATIONSHIP

PROSPECT

PROSPECT PRIORITY TYPE

PROSPECT QUALITY SCORE TYPE

PROSPECT QUALITY SCORE VALUE

PROSPECT REJECT REASON

PUBLICATION

SALES CHANNEL

SOURCE SYSTEM

SOURCE SYSTEM TYPE

SURVEY

TARGET ACCESS METHOD

TARGET ACCOUNT

TARGET AGREEMENT

TARGET GEOGRAPHY AREA

TARGET MARKET SEGMENT

TARGET TYPE


Subject Area: Resource

Table 2-10 lists the entities associated with the subject area Resource.

Table 2-27 Entities of Subject Area: Resource

Resource Entity List

ACCESS METHOD

ADDRESS LOCATION

CABLE

CAPACITY

CARD

CELL SITE

CELL SITE TYPE

CIRCUIT CATEGORY

CIRCUIT COMPONENT

CIRCUIT RENTAL

CIRCUIT RENTAL EVENT TYPE

CIRCUIT TRAFFIC

CIRCUIT TYPE

COMPOUND RESOURCE

COMPOUND RESOURCE SPEC

CONNECTION

DEVICE INTERFACE

EMPLOYEE

EQUIPMENT CENTER

EQUIPMENT HOLDER

EVENT CIRCUIT RENTAL

EXTERNAL OPERATOR

FIXED LINE PORT

HARDWARE

IN PLATFORM

IN ROUTING DEVICE

LOCAL ADDRESS LOCATION

LOGICAL DEVICE

LOGICAL RESOURCE

LOGICAL RESOURCE PHYSICAL SUPPORT

MANAGED HARDWARE

MANAGED TRANSMISSION ENTITY

MOBILE SWITCHING CENTER

NETWORK

NETWORK ADDRESS

NETWORK ASSIGNMENT

NETWORK ASSIGNMENT TYPE

NETWORK CAPACITY

NETWORK ROUTE

NETWORK ROUTE POINT

NETWORK ROUTE POINT ASSIGNMENT

NETWORK SERVICE COVERAGE ASSIGNMENT

NETWORK SERVICE COVERAGE ASSIGNMENT

NETWORK TOUCHPOINT

NETWORK TOUCHPOINT CLASS

NETWORK TOUCHPOINT TYPE

NETWORK TYPE

OPERATING SYSTEM

PARTY

PHYSICAL COMPONENT

PHYSICAL CONNECTOR

PHYSICAL CONTAINER

PHYSICAL DEVICE

PHYSICAL EQUIPMENT

PHYSICAL LINK

PHYSICAL PORT

PHYSICAL RESOURCE

PHYSICAL RESOURCE SPECIFICATION

PIPE

PRODUCT SPECIFICATION

PROTOCOL

RESOURCE

RESOURCE PARTY ASSOCIATION

RESOURCE PARTY MANAGEMENT

RESOURCE RELATIONSHIP

RESOURCE RELATIONSHIP TYPE

RESOURCE ROLE

RESOURCE ROLE SPECIFICATION

RESOURCE SPECIFICATION CATEGORY

RESOURCE SPECIFICATION

RESOURCE STATE HISTORY

RESOURCE STATE REASON

RESOURCE STATE TYPE

ROUTER

SERVICE COVERAGE AREA

SERVICE COVERAGE AREA TYPE

SERVICE COVERAGE GEO DETAIL

SERVICE EQUIPMENT ASSIGNMENT

SITE

SITE TYPE

SOFTWARE

SPECTRUM COVERAGE AREA

SWITCH

SWITCH CAPABILITY

SWITCH CAPABILITY TYPE

SWITCH ROUTING DEVICE ASSIGNMENT

SWITCH TYPE

TECHNOLOGY

TECHNOLOGY TYPE

TERMINATION POINT

TRAIL

VENDOR

WIRELESS SPECTRUM


Subject Area: Service and Service Specification

Table 2-10 lists the entities associated with the subject area Service and Service Specification.

Table 2-28 Entities of Subject Area: Service and Service Specification

Service and Service Specification Entity List

ACCESS METHOD SERVICE ASSIGNMENT

ACCOUNT

ADDRESS LOCATION

BROADBAND SERVICE

BUSINESS INTERACTION

BUSINESS INTERACTION ITEM

COMPOSITE SERVICE

COMPOSITE SERVICE INCLUSION

COMPOSITE SERVICE TYPE INCLUSION

COST

CUSTOMER FACING SERVICE

CUSTOMER FACING SERVICE ROLE

CUSTOMER FACING SERVICE SPECIFICATION

CUSTOMER FACING SERVICE SPECIFICATION ATOMIC

CUSTOMER FACING SERVICE SPECIFICATION COMPOSITE

CUSTOMER FACING SERVICE SPECIFICATION ROLE

CUSTOMER FACING SERVICE SPECIFICATION VERSION

EMAIL SERVICE

FDA

FIXED LINE SERVICE

FSAM

GEOGRAPHY CITY

GPRS SERVICE

MMS SERVICE

NETWORK SITE

PARTY

PARTY SERVICE ASSIGNMENT

PARTY SERVICE ASSIGNMENT REASON

PARTY SERVICE ASSIGNMENT ROLE

PAY TV SERVICE

PRODUCT

PRODUCT SUBSCRIPTION

QOS SERVICE

QOS SERVICE SPEC TYPE

RESOURCE

RESOURCE FACING SERVICE

RESOURCE FACING SERVICE ROLE

RESOURCE FACING SERVICE SPEC VERSION

RESOURCE FACING SERVICE SPECIFICATION

RESOURCE FACING SERVICE SPECIFICATION ATOMIC

RESOURCE FACING SERVICE SPECIFICATION COMPOSITE

RESOURCE FACING SERVICE SPECIFICATION ROLE

RESOURCE SPECIFICATION

SERVICE

SERVICE BUNDLE

SERVICE BUNDLE SPECIFICATION

SERVICE BUNDLE SPECIFICATION ATOMIC

SERVICE BUNDLE SPECIFICATION COMPOSITE

SERVICE COVERAGE AREA

SERVICE COVERAGE AREA TYPE

SERVICE COVERAGE GEO DETAIL

SERVICE DEPENDENCY

SERVICE LR DEPENDENCY

SERVICE ORDER

SERVICE ORDER LINE ITEM

SERVICE PACKAGE

SERVICE PACKAGE SPECIFICATION

SERVICE PACKAGE SPECIFICATION ATOMIC

SERVICE PACKAGE SPECIFICATION COMPOSITE

SERVICE PR DEPENDENCY

SERVICE RESOURCE ASSIGNMENT

SERVICE ROLE

SERVICE SPECIFICATION

SERVICE SPECIFICATION ATOMIC

SERVICE SPECIFICATION CHARACTERISTIC

SERVICE SPECIFICATION CHARACTERISTIC VALUE

SERVICE SPECIFICATION COMPOSITE

SERVICE SPECIFICATION PRODUCT SPECIFICATION RELATIONSHIP

SERVICE SPECIFICATION RESOURCE SPEC RELATIONSHIP

SERVICE SPECIFICATION ROLE

SERVICE SPECIFICATION VERSION

SERVICE STATUS

SERVICE STATUS CATEGORY

SERVICE STATUS HISTORY

SERVICE STATUS REASON

SIM CARD

SMS SERVICE

UDR EVENT

VOICE MESSAGE SERVICE

VPN SERVICE

WIRELESS SERVICE


Subject Area: UDR Event

Table 2-10 lists the entities associated with the subject area UDR Event.

Logical Entities for Business Areas

These business areas lists contain the logical entities in the data model grouped by business area.

Note:

The notion of a business area is not strict. That is, some business areas are overlapping. Thus, a logical entity can belong to, or be needed in, several business areas. Some logical entities are not explicitly listed because they either only represent a relationship between tables, are not critically important to any business area, or are simply lookup entities. For more information, see About Business Areas and Subject Areas in Oracle Communications Data Model.

The following are the business area logical data model entities:

Note:

The business area figures showing complete diagrams with attributes and entities are available with the Oracle Communications Data Model IP Patch. The IP Patch includes additional documentation. To obtain the IP Patch and for the latest information about Oracle Communications Data Model patch sets, go to My Oracle Support at https://support.oracle.com.

Business Area: Cost

Table 2-30 lists the logical entities for Cost.

Business Area: Customer Management

Table 2-31 lists the logical entities for Customer Management.

Table 2-31 Customer Management Business Area Logical Entities

Customer Management Entity List

ACCESS METHOD ACCOUNT ASSIGNMENT

ACCESS METHOD ASSIGNMENT

ACCESS METHOD ELEMENT

ACCESS METHOD EQUIPMENT ASSIGNMENT

ACCESS METHOD GEOGRAPHY ASSIGNMENT

ACCESS METHOD PARTY ASSIGNMENT

ACCESS METHOD POOL

ACCESS METHOD PRODUCT SUBSCRIPTION ASSIGNMENT

ACCESS METHOD SEGMENT

ACCESS METHOD SEGMENT PROD CAPABILITY RL

ACCESS METHOD STATUS HISTORY

ACCESS METHOD TYPE

ACCOUNT ADJUSTMENT REASON

ACCOUNT AGREEMENT RELATIONSHIP

ACCOUNT ASSIGNMENT

ACCOUNT ASSIGNMENT REASON

ACCOUNT BALANCE ADJUSTMENT TYPE

ACCOUNT BALANCE TYPE

ACCOUNT BILLING CYCLE HISTORY

ACCOUNT BILLING FREQUENCY HISTORY

ACCOUNT BILLING PERIOD HISTORY

ACCOUNT CREDIT LIMIT

ACCOUNT EVENT TYPE

ACCOUNT MANAGEMENT HISTORY

ACCOUNT PARTY PRODUCT OFFERING RELATIONSHIP

ACCOUNT PAYMENT METHOD STATUS

ACCOUNT PAYMENT METHOD STATUS REASON

ACCOUNT PAYMENT METHOD STATUS TYPE

ACCOUNT PREFERRED INVOICE DELIVERY

ACCOUNT PRODUCT OFFERING PARTICIPATION HISTORY

ACCOUNT PRODUCT SUBSCRIPTION ASSIGNMENT

ACCOUNT PRODUCT SUBSCRIPTION ASSIGNMENT REASON

ACCOUNT PROFILE

ACCOUNT REFUND REASON

ACCOUNT SEGMENT

ACCOUNT SEGMENT ASSIGNMENT HISTORY

ACCOUNT SEGMENTATION MODEL

ACCOUNT STATUS HISTORY

ACCOUNT STATUS REASON

ACCOUNT STATUS TYPE

ACCOUNT TYPE

ACCOUNTING CYCLE

ACCOUNTING ITEM CATEGORY

ADDRESS LOCATION

ADDRESS RELATED

ADDRESS STATUS

AGE BAND

AGE ON NET BAND

AGREEMENT

AGREEMENT APPROVAL

AGREEMENT ASSIGNMENT

AGREEMENT ASSIGNMENT REASON

AGREEMENT ASSIGNMENT TYPE

AGREEMENT CHANGE INITIATOR TYPE

AGREEMENT CHANGE TYPE

AGREEMENT DOCUMENT

AGREEMENT STATUS

AGREEMENT STATUS TYPE

AGREEMENT TERM TYPE

ARPU BAND

AWARD LEVEL

BANK

BANK DIRECT DEBIT CHANNEL

BARING REASON

BILLING CYCLE

BILLING FREQUENCY

BILLING PERIOD

BILLING STATUS CATEGORY

BILLING STATUS TYPE

BLACK LIST HISTORY

BUSINESS HALF MONTH

BUSINESS HALF YEAR

BUSINESS MONTH

BUSINESS QUARTER

BUSINESS UNIT JOB ROLE

BUSINESS UNIT SHIFT

BUSINESS WEEK

BUSINESS YEAR

CALENDAR HALF MONTH

CALENDAR HALF YEAR

CALENDAR MONTH

CALENDAR QUARTER

CALENDAR WEEK

CALENDAR YEAR

CALL CENTER AGENT

CALL CENTER AGENT TYPE

CALL CENTER CASE SUB TYPE

CALL CENTER CASE TITLE

CALL CENTER CASE TYPE

CALL CENTER SERVICE CAPABILITY

CHANGE PROPOSED BY TYPE

COMPOSITE PRODUCT SPECIFICATION

CREDIT CATEGORY

CURRENCY GEOGRAPHY ENTITY ASSIGNMENT

CUSTOMER

CUSTOMER CLASS

CUSTOMER CLASS ASSIGNMENT

CUSTOMER COST

CUSTOMER FIELD SERVICE ACTIVITY

CUSTOMER FIELD SERVICE DETAIL

CUSTOMER INDIVIDUAL

CUSTOMER OCCASION

CUSTOMER OCCASION TYPE

CUSTOMER ORDER

CUSTOMER ORDER LINE ITEM

CUSTOMER ORDER LINE ITEM STATE ASSIGN

CUSTOMER ORDER PAYMENT

CUSTOMER ORDER STATE ASSIGNMENT

CUSTOMER ORGANIZATION

CUSTOMER RESTRICTED INFO

CUSTOMER REVENUE BAND

CUSTOMER REVENUE BAND ASSIGNMENT

CUSTOMER REVENUE TYPE

CUSTOMER SCORE

CUSTOMER SEGMENT

CUSTOMER SEGMENTATION MODEL

CUSTOMER SIC ASSIGNMENT

CUSTOMER SOURCE

CUSTOMER TYPE

DATA SERVICE EVENT

DAY

DAY ACTUAL CONDITION

DAY TODATE TRANSFORMATION

DAY TRANSFORMATION

DEBT AGING BAND

DERIVED VALUE

EDUCATION

EMPLOYEE

EMPLOYEE DESIGNATION

EMPLOYEE DESIGNATION

EMPLOYEE DISCOUNT GROUP ASSIGNMENT

EMPLOYEE JOB ROLE ASSIGNMENT

EMPLOYEE JOB ROLE TYPE

EMPLOYEE RESTRICTED INFO

EMPLOYEE SCHEDULE

EMPLOYEE TRAINING RECORD

EMPLOYEE TYPE

EQUIPMENT

EQUIPMENT RENTING AGREEMENT

EVENT ACCOUNT

EVENT GEOGRAPHY

EVENT LOCATION

EVENT PARTY INTERACTION

EVENT PARTY PROFILE

EVENT PARTY ROLE

EVENT RESOLUTION

EXTERNAL INFORMATION SOURCE

EXTERNAL ORGANIZATION TYPE

FACTOR COMPANY

FISCAL HALF MONTH

FISCAL HALF YEAR

FISCAL MONTH

FISCAL QUARTER

FISCAL WEEK

FISCAL YEAR

FRAUD PROFILE CLASS

GENDER

GEOGRAPHY CITY

GEOGRAPHY COUNTRY

GEOGRAPHY COUNTY

GEOGRAPHY DEMOGRAPHIC GROUP

GEOGRAPHY DEMOGRAPHY ATTRIBUTE

GEOGRAPHY DEMOGRAPHY VALUE

GEOGRAPHY ENTITY

GEOGRAPHY ENTITY ASSIGNMENT

GEOGRAPHY ENTITY HIER LEVEL ASSIGNMENT

GEOGRAPHY HIERARCHY

GEOGRAPHY HIERARCHY LEVEL

GEOGRAPHY HIERARCHY LEVEL ASSIGNMENT

GEOGRAPHY LEVEL

GEOGRAPHY LEVEL ATTRIBUTE

GEOGRAPHY LEVEL ATTRIBUTE VALUE

GEOGRAPHY REGION

GEOGRAPHY STATE

GEOGRAPHY SUB REGION

GEOGRAPHY WORLD

GPRS SERVICE

HALF HOUR

HALF MONTH TODATE TRANSFORMATION

HALF MONTH TRANSFORMATION

HALF YEAR TODATE TRANSFORMATION

HALF YEAR TRANSFORMATION

HOUR

HOUSEHOLD

INITIATIVE RESULT TYPE

INITIATIVE TYPE

INTERACTION ANSWER CHOICE

INTERACTION CHANNEL

INTERACTION DIRECTION

INTERACTION QUESTION RESPONSE

INTERACTION REASON

INTERACTION RESULT TYPE

INTERACTION STATUS

INTERACTION TYPE

INVOICE

IP ADDRESS POOL

JOB

JOB ROLE

LANGUAGE

LEGAL PROCESS STATUS TYPE

LETTER TYPE

MAILBOX

MANAGE ACTION TYPE

MARITAL STATUS

MEDIA OBJECT

MUSIC DOWNLOAD

NAICS INDUSTRY SUBSECTOR

NATIONALITY

NP MOBILE MSISDN

NP REQUEST HEADER

NP REQUEST LINE ITEM

NP REQUEST LINE ITEM STATE HISTORY

NP REQUEST LINE ITEM STATE TYPE

NP REQUEST STATE HISTORY

NP REQUEST STATE TYPE

NP REQUEST TYPE

NP STEP

NUMBER AREA

NUMBER COUNTRY

ORDER LINE ITEM STATE

ORDER LINE ITEM STATE

ORDER TYPE

ORGANIZATION AREA

ORGANIZATION BANNER

ORGANIZATION BUSINESS UNIT

ORGANIZATION CHAIN

ORGANIZATION COMPANY

ORGANIZATION CORPORATE

ORGANIZATION DISTRICT

ORGANIZATION DIVISION

ORGANIZATION REGION

OTHER INDIVIDUAL

PARTY ACCOUNT ASSIGNMENT

PARTY ACCOUNT ASSIGNMENT TYPE

PARTY ADDRESS LOCATION ASSIGNMENT

PARTY AGREEMENT ASSIGNMENT

PARTY AGREEMENT ASSIGNMENT ROLE

PARTY AGREEMENT ASSIGNMENT TYPE

PARTY ASSIGNMENT

PARTY CONTACT INFORMATION

PARTY CONTACT LIST ROLE

PARTY EVENT TYPE

PARTY GEOGRAPHY ENTITY ASSIGNMENT

PARTY IDENTIFICATION

PARTY IDENTIFICATION TYPE

PARTY ORDER ASSIGNMENT TYPE

PARTY PRODUCT SUBSCRIPTION ASSIGNMENT

PARTY PROMOTION RESPONSE

PARTY ROLE ASSIGNMENT

PARTY ROLE STATUS

PARTY SEGMENTATION METHOD

PARTY SIM CARD ASSIGNMENT

PARTY STATUS CHANGE REASON

PARTY STATUS HISTORY

PAYMENT CHANNEL

PERIOD TO DATE TRANSFORMATION

PERIOD TRANSFORMATION

POSTAL SERVICE TYPE

POSTCODE

PRICE DERIVATION RULE

PRODUCT SPECIFICATION

PRODUCT SPECIFICATION TYPE

PROMOTION

PROMOTION RESULT TYPE

PROMOTION TERM TYPE

PROSPECT

PROSPECT INDIVIDUAL

PROSPECT ORGANIZATION

PTV FULL CHANNEL ACTIVATION

PUBLICATION TYPE

QUARTER HOUR

QUARTER TO DATE TRANSFORMATION

QUARTER TRANSFORMATION

REDEMPTION TYPE

RINGTONE

ROLES HIERARCHY

SCRIPT

SCRIPT QUESTION

SCRIPT QUESTION TYPE

SEASON

SECOND

SEGMENT CRITERIA

SEGMENT TYPE

SERVICE REQUEST

SIC ASSIGNMENT

SIC DIVISION

SIC INDUSTRY GROUP

SIM CARD PRODUCT SUBSCRIPTION ASSIGNMENT

SOC JOB

SOC JOB CATEGORY

SOC JOB GROUP

SOC JOB MAJOR GROUP

SOURCE SYSTEM

SOURCE SYSTEM KEY MAPPING

SUBSCRIBER ACTIVATION REASON

TAX EXEMPT

TIME SLOT

TIME STANDARD BY DAY

TIME STANDARD BY WEEK

USER

VALUE TYPE

VENDOR FACTOR COMPANY ASSIGNMENT

VIRTUAL TEAM

WEATHER CONDITION

WEEK TODATE TRANSFORMATION

WEEK TRANSFORMATION

YEAR TRANSFORMATION


Business Area: Marketing

Table 2-32 lists the logical entities for Marketing.

Table 2-32 Marketing Business Area Logical Entity

Marketing Entity List

ACCOUNT PRODUCT OFFERING PARTICIPATION HISTORY

ADVERTISING PERIOD

ADVERTISING QUARTER

ADVERTISING WEEK

ADVERTISING YEAR

AWARD LEVEL

BUSINESS HALF MONTH

BUSINESS HALF YEAR

BUSINESS MONTH

BUSINESS QUARTER

BUSINESS WEEK

BUSINESS YEAR

CALENDAR HALF MONTH

CALENDAR HALF YEAR

CALENDAR MONTH

CALENDAR QUARTER

CALENDAR WEEK

CALENDAR YEAR

CAMPAIGN

CAMPAIGN CHANNEL

CAMPAIGN CHANNEL TYPE

CAMPAIGN MANAGEMENT HISTORY

CAMPAIGN MESSAGE

CAMPAIGN MESSAGE CREATIVE

CAMPAIGN MESSAGE DEPICTION

CAMPAIGN PURPOSE TYPE

CAMPAIGN STATUS

CAMPAIGN TYPE

CONTACT LIST

CONTACT LIST CHANGE REASON

CONTACT LIST RECURRENCE TYPE

COST

DAY

DEMOGRAPHY ATTRIBUTE

DEMOGRAPHY GROUP

DSL MODEM

EMPLOYEE DESIGNATION

EMPLOYEE JOB ROLE TYPE

EMPLOYEE TYPE

EQUIPMENT

EVENT LOCATION

EVENT RESPONSE REASON

FISCAL HALF MONTH

FISCAL HALF YEAR

FISCAL MONTH

FISCAL QUARTER

FISCAL WEEK

FISCAL YEAR

GEOGRAPHY LEVEL ATTRIBUTE

INDIVIDUAL DEMOGRAPHY PROFILE

INDIVIDUAL DEMOGRAPHY VALUE

INITIATIVE TYPE

INTERACTION DIRECTION

INTERACTION REASON

INTERACTION RESULT TYPE

INTERACTION STATUS

INTERACTION TYPE

LETTER TYPE

MANAGE ACTION TYPE

MARKET AREA

MARKET AREA LEVEL

PRODUCT OFFERING TERM

MEDIA OBJECT

MEDIA OBJECT ASSIGNMENT

ORGANIZATION AREA

ORGANIZATION BANNER

ORGANIZATION BUSINESS UNIT

ORGANIZATION CHAIN

ORGANIZATION COMPANY

ORGANIZATION CORPORATE

ORGANIZATION DISTRICT

ORGANIZATION DIVISION

ORGANIZATION REGION

PARTNER PROMOTION PROGRAM

PARTY CONTACT LIST PARTICIPATION

PARTY CONTACT LIST ROLE

PARTY GEOGRAPHY ENTITY ASSIGNMENT

PARTY MANAGEMENT ROLE

PRODUCT SPECIFICATION

PRODUCT OFFERING

COMPOSITE PRODUCT SPECIFICATION

PRODUCT SPECIFICATION TYPE

PROMOTION

PROMOTION CLUSTER USAGE

PROMOTION CONTACT LIST UTILIZATION

PROMOTION MANAGEMENT HISTORY

PROMOTION RESULT TYPE

PROMOTION TERM VALUE

PUBLICATION

PUBLICATION TYPE

RETAIL STORE

SCRIPT QUESTION TYPE

SEASON

SELLING LOCATION

SOURCE SYSTEM TYPE

TARGET ACCESS METHOD

TARGET ACCOUNT

TARGET AGREEMENT

TARGET GEOGRAPHY AREA

TARGET TYPE

TIME SLOT

TIME STANDARD BY DAY

TIME STANDARD BY WEEK

WEATHER CONDITION

WEEK TODATE TRANSFORMATION

WEEK TRANSFORMATION

WEEKDAY

YEAR TRANSFORMATION


Business Area: Network

Table 2-33 lists the logical entities for Network.

Table 2-33 Network Business Area Logical Entity

Network Entity List

ADDRESS LOCATION

ANZSIC CLASSIFICATION

BASE STATION CONTROLLER

BASE TRANSCEIVER STATION

BER FER TYPE

BROADBAND SERVICE

BROADBAND RATING PLAN

BROADBAND USAGE EVENT

BUSINESS HALF MONTH

BUSINESS HALF YEAR

BUSINESS MONTH

BUSINESS QUARTER

BUSINESS WEEK

BUSINESS YEAR

CALENDAR HALF MONTH

CALENDAR HALF YEAR

CALENDAR MONTH

CALENDAR QUARTER

CALENDAR WEEK

CALENDAR YEAR

CALL DIRECTION

CALL FORWARD

CALL OTHER TYPE

CALL RECYCLED REASON

CALL SUCCESS FAILURE TYPE

CALL SURCHARGE

CALL TERMINATION REASON

CELL

CELL OUTAGE REASON

CELL SITE

CELL SITE TYPE

CELL TYPE

CIRCUIT CATEGORY

CIRCUIT COMPONENT

CIRCUIT RENTAL

CIRCUIT RENTAL EVENT TYPE

CIRCUIT TRAFFIC

CIRCUIT TYPE

CONTENT DELIVERY EVENT

DAY

DESTINATION TYPE

DISTANCE BAND

DIVERT RETRIEVE REASON

DIVERT RETRIEVE TYPE

EQUIPMENT CENTER

EVENT

EVENT ACCESS METHOD ACTIVITY

EVENT ASSIGNMENT

EVENT ASSIGNMENT REASON

EVENT ASSIGNMENT TYPE

EVENT CATEGORY

EVENT CIRCUIT RENTAL

EVENT CLASS

EVENT COMPOSITE PRODUCT SPECIFICATION

EVENT GEOGRAPHY

EVENT PREPAID MOBILE

EVENT PRODUCT SUBSCRIPTION WIRELESS

EVENT STATUS

EVENT SUBSCRIPTION CHANGE

EXTERNAL OPERATOR

FAULT RESOLUTION TYPE

FAULT TYPE

FISCAL HALF MONTH

FISCAL HALF YEAR

FISCAL MONTH

FISCAL QUARTER

FISCAL WEEK

FISCAL YEAR

FIXED LINE CALL EVENT

FIXED LINE PORT

GEOGRAPHY CITY

GEOGRAPHY COUNTRY

GEOGRAPHY REGION

GEOGRAPHY STATE

GEOGRAPHY SUB REGION

GEOGRAPHY WORLD

IDD CALL EVENT

IN PLATFORM

INTERACTION DIRECTION

INTERACTION REASON

INTERACTION RESULT TYPE

INTERACTION STATUS

INTERACTION TYPE

INTERNET ACCESS EVENT

LETTER TYPE

LOYALTY PROGRAM

MEDIATED CALL EVENT

MMS EVENT

MOBILE SWITCHING CENTER

MONTH TODATE TRANSFORMATION

MONTH TRANSFORMATION

NETWORK

NETWORK SERVICE COVERAGE ASSIGNMENT

NETWORK TOUCHPOINT

NETWORK TOUCHPOINT CLASS

NETWORK TOUCHPOINT STATUS

NETWORK TOUCHPOINT TYPE

NETWORK TYPE

NOTIFICATION TYPE

NUMBER NETWORK TYPE

ON OFF NET TYPE

PARTY

PACKET CONTROL UNIT OUTAGE REASON

PEAK OFFPEAK TIME

PREPAID MOBILE EVENT TYPE

PROMOTION RESULT TYPE

PROMOTION TERM TYPE

PTV QPI SERVICE EVENT

PUBLICATION TYPE

RESOURCE

RETAIL STORE

RF CARRIER

ROUTING DEVICE

SCRIPT QUESTION TYPE

SEASON

SERVICE CLASS

SERVICE CLASS TYPE

SERVICE COVERAGE AREA

SERVICE COVERAGE AREA TYPE

SERVICE COVERAGE GEO DETAIL

SERVICE EQUIPMENT ASSIGNMENT

SERVICE REQUEST

SMS EVENT

SWITCH

SWITCH CAPABILITY

SWITCH CAPABILITY TYPE

SWITCH COMMAND

SWITCH ROUTING DEVICE ASSIGNMENT

SWITCH TYPE

TCH TYPE

TECHNOLOGY

TECHNOLOGY TYPE

TIME BAND

TIME SLOT

TIME STANDARD BY DAY

TIME STANDARD BY WEEK

UDR EVENT

UDR EVENT STATUS

UDR EVENT TYPE

UMS ACCESS TYPE

UMS EVENT

VAS SUBSCRIPTION

VOIP CALL EVENT

VOLUME BAND

WIRELESS CALL EVENT

WIRELESS CONTENT DOWNLOADING EVENT

YEAR TRANSFORMATION


Business Area: Product Management

Table 2-35 lists the logical entities for Product Management.

Table 2-35 Product Management Business Area Logical Entity

Product Management Entity List

ACCESSORIES

ADDITIONAL TEXT

BRAND

BROADBAND RATING PLAN

BUSINESS HALF MONTH

BUSINESS HALF YEAR

BUSINESS MONTH

BUSINESS QUARTER

CABLE MODEM

CALENDAR HALF MONTH

CALENDAR HALF YEAR

CALENDAR MONTH

CALENDAR QUARTER

CALENDAR WEEK

CALENDAR YEAR

CALLER ID

CELL

CELL SECTOR

CELL SITE

CHANGE PROPOSED BY TYPE

CHANNEL

CHANNEL TYPE

COMPOSITE PRODUCT SPECIFICATION

COMPOSITE PRODUCT SPECIFICATION ASSIGNMENT

COMPOSITE PRODUCT SPECIFICATION CHARGE TYPE

CONFIGURABLE PRODUCT SPECIFICATION CHARACTERISTIC

CONTENT

DISCOUNT GROUP

DOCUMENT CONDITION TYPE

DOCUMENT TYPE

EQUIPMENT

EQUIPMENT FUNCTIONALITY

EQUIPMENT FUNCTIONALITY ASSIGNMENT

EQUIPMENT INSTANCE

EQUIPMENT INSTANCE STATUS TYPE

EVENT COMPOSITE PRODUCT SPECIFICATION

EVENT SIM CARD

FISCAL HALF MONTH

FISCAL HALF YEAR

FISCAL MONTH

FISCAL QUARTER

FISCAL WEEK

FISCAL YEAR

FIXED LINE SERVICE

FIXED LINE RATING PLAN

GIVE AWAY TYPE

HANDSET INSTANCE

HANDSET MODEL

IDD

ITEM SPECIFICATION

LANGUAGE

PRODUCT OFFERING TERM

MINUTE

MMS SERVICE

MODEL TYPE

NAICS CLASSIFICATION

NAICS INDUSTRY

NAICS INDUSTRY GROUP

NAICS INDUSTRY SECTOR

NAICS INDUSTRY SUBSECTOR

NETWORK TOUCHPOINT

ORGANIZATION BUSINESS UNIT

ORGANIZATION ITEM SELLING PRICE

ORGANIZATION WAREHOUSE

PARTY

PAY TV SERVICE

PPA CATEGORY

PPA DEDUCTION TYPE

PREPAID VOUCHER

PRODUCT

PRODUCT SPECIFICATION ADDITIONAL TEXT

PRODUCT SPECIFICATION ASSIGNMENT REASON

PRODUCT CAPABILITY

PRODUCT CAPABILITY TYPE

PRODUCT CAPABILITY VALUE

PRICE TYPE

PRICE TYPE RELATIONSHIP

PRICE TYPE RELATION REASON

CONFIGURABLE PRODSPECCHAR PRODSPEC ASSIGNMENT

PRODUCT FUNCTIONALITY DEPENDENCY

PRODUCT SPECIFICATION MANAGEMENT HISTORY

PRODUCT SPECIFICATION MANAGEMENT REASON

PRODUCT SPECIFICATION MANAGEMENT ROLE

PRODUCT OFFERING

PRODUCT OFFERING ASSIGNMENT TYPE

PRODUCT OFFERING GEOGRAPHY ASSIGNMENT

PRODUCT OFFERING GROUP

PRODUCT OFFERING GROUP ASSIGNMENT

PRODUCT OFFERING GROUP TYPE

PRODUCT OFFERING PRODUCT SPECIFICATION ASSIGNMENT

PRODUCT OFFERING TYPE

PRODUCT SPECIFICATION

PRODUCT SPECIFICATION NETWORK ASSIGNMENT

PRODUCT SPECIFICATION RELATIONSHIP

PRODUCT SPECIFICATION STATUS HISTORY

PRODUCT SPECIFICATION TYPE

PRODUCT SPECIFICATION VERSION

PRODUCT SPECIFICATION STATUS TYPE

RATING METHOD TYPE

SECURITY REQUIRED TYPE

SERVICE

SERVICE CLASS

SERVICE CLASS TYPE

SET TOP BOX

SET TOP BOX MODEL

SIM CARD

SIM CARD ACCESS METHOD ASSIGNMENT

SIM CARD HANDSET ASSIGNMENT

SIM CARD PRODUCT SUBSCRIPTION ASSIGNMENT

SMS RATING PLAN

TIME BAND

TIME SLOT

TIME STANDARD BY WEEK

TV CHANNEL

VALUE ADDED SERVICE

WIRELESS RATING PLAN

YEAR TRANSFORMATION


Business Area: Provisioning and Service

Table 2-36 lists the logical entities for Provisioning and Service.

Table 2-36 Provisioning and Service Business Area Logical Entity

Provisioning and Service Entity List

ACCESS METHOD

ACCESS METHOD ASSIGNMENT TYPE

ACCESS METHOD ELEMENT TYPE

ACCESS METHOD PARTY ASSIGNMENT

ACCESS METHOD STATUS REASON

ACCESS METHOD STATUS TYPE

ACCESS METHOD TYPE

ACCOUNT

ADDRESS LOCATION

AGREEMENT

AGREEMENT TERM

APPOINTMENT CALENDAR

BLACK LIST HISTORY

BUSINESS HALF MONTH

BUSINESS HALF YEAR

BUSINESS MONTH

BUSINESS QUARTER

BUSINESS WEEK

BUSINESS YEAR

CALENDAR HALF MONTH

CALENDAR HALF MONTH

CALENDAR HALF YEAR

CALENDAR QUARTER

CALENDAR WEEK

CALENDAR YEAR

CALL CATEGORY

CALL CENTER

CALL CENTER AGENT TYPE

CALL CENTER CASE SUB TYPE

CALL CENTER CASE TITLE

CALL CENTER CASE TYPE

CALL FORWARD

CALL ROUTING TYPE

CALL SOURCE DESTINATION

CALL TYPE

CHANGE PROPOSED BY TYPE

COMPOSITE PRODUCT SPECIFICATION

COURIER

COURIER COST

CUSTOMER

CUSTOMER CLASS

CUSTOMER CLASS ASSIGNMENT

CUSTOMER ORDER

CUSTOMER SCORE

CUSTOMER SEGMENT

CUSTOMER SOURCE

CUSTOMER TYPE

DAY

EQUIPMENT

EVENT ASSIGNMENT REASON

EVENT ASSIGNMENT TYPE

EVENT CATEGORY

EVENT GEOGRAPHY

EVENT RESPONSE REASON

FIELD ACTIVITY RESULT TYPE

FIELD ACTIVITY TYPE

FISCAL HALF MONTH

FISCAL HALF YEAR

FISCAL MONTH

FISCAL QUARTER

FISCAL WEEK

FISCAL YEAR

GEOGRAPHY CITY

GEOGRAPHY COUNTY

GEOGRAPHY REGION

GEOGRAPHY STATE

GEOGRAPHY SUB REGION

GEOGRAPHY WORLD

INTERACTION DIRECTION

INTERACTION REASON

INTERACTION RESULT TYPE

INTERACTION STATUS

INTERACTION TYPE

ISP USAGE EVENT

ITEM SPECIFICATION

LETTER TYPE

MANAGE ACTION TYPE

PRODUCT OFFERING TERM

UDR EVENT

NP REQUEST LINE ITEM STATE HISTORY

NP REQUEST STATE TYPE

NP REQUEST TYPE

NP STEP

ORDER TYPE

ORGANIZATION AREA

ORGANIZATION BANNER

ORGANIZATION BUSINESS UNIT

ORGANIZATION CHAIN

ORGANIZATION COMPANY

ORGANIZATION CORPORATE

ORGANIZATION DISTRICT

ORGANIZATION DIVISION

ORGANIZATION REGION

OTHER INDIVIDUAL

PARTY AM PRODUCT OFFERING ASSIGNMENT HISTORY

PARTY CONTACT LIST ROLE

PARTY SIM CARD ROLE

PREPAID VOUCHER

PRODUCT OFFERING

PRODUCT OFFERING GEOGRAPHY ASSIGNMENT

PRODUCT OFFERING ORGANIZATION AVAILABILITY

PRODUCT OFFERING PRODUCT SPECIFICATION ASSIGNMENT

PRODUCT OFFERING PRICE

PRODUCT SPECIFICATION

PRODUCT SPECIFICATION TYPE

PROMOTION RESULT TYPE

PROMOTION TERM TYPE

PTV USAGE EVENT

PUBLICATION TYPE

SCRIPT QUESTION TYPE

SEASON

SERVICE

SERVICE CLASS

SERVICE CLASS TYPE

SERVICE REQUEST

SIM CARD ACCESS METHOD REASON

SIM CARD ACTIVATION REASON

SIM CARD ACTIVATION TYPE

SIM CARD PRODUCT SUBSCRIPTION ASSIGNMENT

SIM CARD TYPE

SUBSCRIBER ACTIVATION REASON

PRODUCT SUBSCRIPTION

TIME SLOT

TIME STANDARD BY DAY

TIME STANDARD BY WEEK

UMS ACCESS TYPE

VOICE MESSAGE SERVICE

YEAR TRANSFORMATION


Business Area: Revenue

Table 2-37 lists the logical entities for Revenue.

Table 2-37 Revenue Business Area Logical Entities

Revenue Entity List

ACCESS METHOD

ACCESS METHOD TYPE

ACCOUNT ACCOUNTING CYCLE HISTORY

ACCOUNT PAYMENT

ACCOUNT PAYMENT METHOD

ADDRESS LOCATION

AGREEMENT

BUSINESS HALF MONTH

BUSINESS HALF YEAR

BUSINESS MONTH

BUSINESS QUARTER

BUSINESS WEEK

BUSINESS YEAR

CALENDAR HALF MONTH

CALENDAR HALF YEAR

CALENDAR MONTH

CALENDAR QUARTER

CALENDAR WEEK

CALENDAR YEAR

CAMPAIGN

CAMPAIGN TYPE

CELL

CELL SITE

COLLECTION AGENCY

COMMISSION TYPE

COMPOSITE PRODUCT SPECIFICATION

CURRENCY EXCHANGE RATE

CUSTOMER

CUSTOMER CLASS

CUSTOMER CLASS ASSIGNMENT

CUSTOMER SCORE

CUSTOMER SEGMENT

CUSTOMER SOURCE

CUSTOMER TYPE

DAY

DEBT AGING BAND

DIRECT DEBIT STATUS REASON

EQUIPMENT

EVENT FINANCIAL

EVENT LOYALTY PROGRAM

FACTOR COMPANY

FISCAL HALF MONTH

FISCAL HALF YEAR

FISCAL MONTH

FISCAL QUARTER

FISCAL WEEK

FISCAL YEAR

FRAUD PROFILE CLASS

GEOGRAPHY CITY

GEOGRAPHY COUNTRY

GEOGRAPHY COUNTY

GEOGRAPHY REGION

GEOGRAPHY STATE

GEOGRAPHY SUB REGION

GEOGRAPHY WORLD

GL REFERENCE

INVOICE

INVOICE ADJUSTMENT

INVOICE ADJUSTMENT QUOTA

INVOICE ADJUSTMENT REASON

INVOICE ADJUSTMENT TYPE

INVOICE DELIVERY TYPE

INVOICE DISCOUNT

INVOICE DISCOUNT REASON

INVOICE DISCOUNT TYPE

INVOICE ITEM

INVOICE ITEM DETAIL

INVOICE ITEM DETAIL TYPE

INVOICE ITEM TYPE

INVOICE PAYMENT TERM

INVOICE PAYMENT TERM TYPE

INVOICE TYPE

IP ADDRESS POOL

LANGUAGE

NETWORK

RESOURCE

NETWORK TYPE

ORGANIZATION AREA

ORGANIZATION BANNER

ORGANIZATION BUSINESS ENTITY

ORGANIZATION BUSINESS UNIT

ORGANIZATION BUSINESS UNIT TYPE

ORGANIZATION CHAIN

ORGANIZATION COMPANY

ORGANIZATION CORPORATE

ORGANIZATION DISTRICT

ORGANIZATION DIVISION

ORGANIZATION HIERARCHY

ORGANIZATION HIERARCHY LEVEL

ORGANIZATION HIERARCHY LEVEL ASSIGNMENT

ORGANIZATION HIERARCHY VERSION

ORGANIZATION ITEM SELLING PRICE

ORGANIZATION LEVEL

ORGANIZATION LEVEL ATTRIBUTE VALUE

ORGANIZATION LEVEL ATTRIBUTES

ORGANIZATION MARKET DATA

ORGANIZATION REGION

ORGANIZATION SERVICE WEBSITE

ORGANIZATIONAL DEMOGRAPHY VALUE

PAYMENT METHOD TYPE

PAYMENT TRANSACTION TYPE

PREPAID RECHARGE

PRICE TYPE

PRODUCT OFFERING PRICE

PRODUCT SPECIFICATION

PRODUCT SPECIFICATION TYPE

PRODUCT SUBSCRIPTION

PRODUCT SUBSCRIPTION ASSIGNMENT

PRODUCT SUBSCRIPTION STATUS CATEGORY

PRODUCT SUBSCRIPTION STATUS HISTORY

PRODUCT SUBSCRIPTION STATUS REASON

PRODUCT SUBSCRIPTION TERM TYPE

PRODUCT SUBSCRIPTION TYPE

PROMOTION

PROMOTION TYPE

RECHARGE REVENUE SLAB

SALES CHANNEL

SALES CHANNEL REPRESENTATIVE

SALES COMMISSION DETAIL

SALES COMMISSION PAYROLL

SALES COMMISSION PLAN

SALES COMMISSION PLAN DETAIL

PRODUCT SUBSCRIPTION ASSIGNMENT TYPE

PRODUCT SUBSCRIPTION EVENT TYPE

SUBSCRIPTION SERVICE CLASS ASSIGNMENT

PRODUCT SUBSCRIPTION STATUS

SUBSCRIPTION TERM VALUE

TAX EXEMPT

TIME SLOT

TIME STANDARD BY DAY

TIME STANDARD BY WEEK

YEAR TRANSFORMATION


Logical Data Model Entity Dictionary

Table 2-38, Table 2-39, Table 2-40, Table 2-41, Table 2-42, Table 2-43, and Table 2-44 list the logical data model entities, in alphabetical order.

Table 2-38 A to C Entity Descriptions

Entity Name Type Description

802 SERVICE

Reference

Semantics that define how traffic is forwarded based on the value of the priority field in the 802.1P header.

ACCESS METHOD

Reference

Methods that a customer accesses or uses as a service. For example:

  • Fixed Line telephone numbers

  • Wireless telephone numbers

  • xDSL account

  • IDD Calling card number

ACCESS METHOD ACCOUNT ASSIGNMENT

Reference

Assigns ACCESS METHODs to an account.

ACCESS METHOD ASSIGNMENT TYPE

Lookup

Type of relationship between two ACCESS METHODs. For example:

  • Replace

  • Bind together

ACCESS METHOD ASSIGNMENT

Reference

Assignment of an ACCESS METHOD to a related ACCESS METHOD.

ACCESS METHOD ELEMENT

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:

  • Country code

  • Area code

  • Local number

ACCESS METHOD ELEMENT TYPE

Lookup

Lookup for type of ACCESS METHOD ELEMENT. For example:

  • Country code of phone number

  • Area code of phone number

ACCESS METHOD EQUIPMENT ASSIGNMENT

Reference

How the access method binds to an equipment instance. For example:

  • Cell phone number binds onto a cell phone

  • Login code binds to a modem

ACCESS METHOD GEOGRAPHY ASSIGNMENT

Reference

Assigns the access method to a geographic region.

ACCESS METHOD PARTY ASSIGNMENT

Reference

Assigns access method to a party.

ACCESS METHOD PARTY ASSIGNMENT TYPE

Lookup

Lookup for type of relationship between ACCESS METHOD and PARTY. For example:

  • Management

  • Owned by

The management type of access method party relationship specifies that an employee may be responsible for the maintenance of a group of access methods.

ACCESS METHOD POOL

Reference

The logical network resources. For example:

  • Telephone number

  • IP address

ACCESS METHOD PORTING HISTORY

Base

The history of access methods that the customer brought to the operator from another telecom operator, according to the number porting scheme.

ACCESS METHOD PRODUCT SUBSCRIPTION ASSIGNMENT

Reference

Assigns ACCESS METHOD(s) to a PRODUCT SUBSCRIPTION.

ACCESS METHOD SEGMENT

Reference

Segments of ACCESS METHODs defined for usage tracking. For example:

  • Phone number may have the segments: Country_Code + Area_Code + Local_Number

  • IP address may have the segments: Type A, B, C, D, E subnetwork

ACCESS METHOD SEGMENT PROD CAPABILITY RL

Reference

The relationship between ACCESS METHOD SEGMENT and PRODUCT CAPABILITY to define which product capabilities require which access method segment.

ACCESS METHOD SERVICE ASSIGNMENT

Reference

Defines the relationship between a SERVICE and an ACCESS METHOD. For example, which service (gsm voice) is using which mobile number.

ACCESS METHOD STATUS HISTORY

Base

The status of an ACCESS METHOD. Defines both current status and historical status. For example:

  • Active

  • Suspended

  • Deactivated

ACCESS METHOD STATUS REASON

Lookup

Lookup for available reasons an ACCESS METHOD may have a change in status.

For example:

  • Customer relocation

  • Suspension due to late-payment

ACCESS METHOD STATUS TYPE

Lookup

Lookup for available ACCESS METHOD status types and descriptions. For example:

  • Active

  • Inactive

  • Suspended

  • Future Activated

ACCESS METHOD TYPE

Lookup

Lookup for ACCESS METHOD type: Defines the types of methods by which a customer may use or access services or products. For example:

  • Fixed Line telephone numbers

  • Wireless telephone numbers

  • xDSL account

  • IDD Calling card number

ACCESSORIES

Reference

The accessories that may be purchased from the service provider in addition to the item, product, or service. For example:

  • Handset chains

  • Starter kit

  • Headset (earphones)

  • USB Cable

ACCESSORIES INSTANCE

Reference

A physical instance of ACCESSORIES which customer has got as part of an option or add-on. An instance can be a specific Handset cover or headset (with Serial Number), loudspeakers, and so on.

ACCOUNT

Reference

The account is generated by a agreement 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 website or from a Service Provider terminal. In this case the account is normally protected by a password.

ACCOUNT ACCOUNTING CYCLE HISTORY

Base

Billing cycle status history for ACCOUNTs.

ACCOUNT ADJUSTMENT REASON

Lookup

Lookup of all the reasons for adjustments. For example:

  • Goodwill

  • Agreement after complaint

ACCOUNT AGREEMENT RELATIONSHIP

Reference

Assignment of ACCOUNT to a AGREEMENT.

ACCOUNT ASSIGNMENT

Reference

Relationship assignments between ACCOUNTs. For example, parent and child accounts.

ACCOUNT ASSIGNMENT REASON

Lookup

Lookup for available reasons ACCOUNTs may be related.

ACCOUNT ASSIGNMENT TYPE

Reference

The type of relationship between two ACCOUNTs. For example, a corporate account has several affiliated accounts.

ACCOUNT BALANCE

Base

This entity keeps a snapshots of ACCOUNT BALANCEs, at different period of time and for different ACCOUNT BALANCE TYPE.

ACCOUNT BALANCE ADJUSTMENT TYPE

Lookup

Lookup of all the types of adjustments. For example:

  • Free Monthly Fee

  • Free Service

  • Direct credit amount

ACCOUNT BALANCE GROUP

Reference

The balance group concept allows one account to have multiple balance groups, which applies to different groups of services. For example, some special discounts, or monetary balance, can be given for wireless calls, but not for fixed line service.

ACCOUNT BALANCE IMPACT

Base

The account balance change details, because of a specific event. For example:

  • Account payment

  • Rated UDR event

ACCOUNT BALANCE MONTH DRVD

Derived

Daily aggregate of free minutes allowance (PPA) for ACCOUNT and PRODUCT OFFERING.

ACCOUNT BALANCE TYPE

Lookup

Type of account balance. For example:

  • Broadband

  • PTV

  • Wireless free call allowance

ACCOUNT BILLING CYCLE HISTORY

Reference

Billing cycle status history for ACCOUNTs.

ACCOUNT BILLING FREQUENCY HISTORY

Reference

Billing frequency history for ACCOUNTs.

ACCOUNT BILLING OCCURRENCE

Reference

Specifies each billing occurrence for an ACCOUNT. A billing occurrence may be triggered by a predefined billing cycle or some other event such as account termination. In a single account billing occurrence there may be multiple invoices generated.

ACCOUNT BILLING PERIOD HISTORY

Reference

Billing period history for ACCOUNTs.

ACCOUNT BUSINESS INTERACTION ROLE

Reference

The business interaction role which can be assigned by a CUSTOMER ACCOUNT.

ACCOUNT COST

Base

Subtype of COST, which associates a specific incurred cost to an ACCOUNT (through an EMPLOYEE).

ACCOUNT CREDIT LIMIT

Base

Credit limit assigned to an account, subscription, or agreement.

ACCOUNT DEBT

Base

Information about the ACCOUNT and debt collection process, as soon as an ACCOUNT is tagged as being in debt until the day it is resolved (included).

ACCOUNT DEBT HISTORY

Base

History tracking of the evolution of the debt process per individual ACCOUNT.

ACCOUNT DEBT MONTH AGGR

Aggregate

The summarized monthly debt status for each CUSTOMER TYPE.

ACCOUNT DEBT MONTH DERIVED

Derived

Summery of payment and collection by internal collector.

ACCOUNT EVENT TYPE

Lookup

Lookup for account event types.

ACCOUNT FIRST ACTIVITY DERIVED

Derived

Collects first usage and payment per account. This entity should be filled once and updated maximal twice per account (one for payment, one per incoming and outgoing usage). It is then never touched.

ACCOUNT LAST ACTIVITY DERIVED

Derived

Collects last usage and payment per account. This entity should be filled at least every day per account until full account deactivation.

ACCOUNT MANAGEMENT HISTORY

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.

ACCOUNT PARTY PRODUCT OFFERING RELATIONSHIP

Reference

Assigns accounts and parties to PRODUCT OFFERING.

ACCOUNT PAYMENT

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.

ACCOUNT PAYMENT DAY DRVD

Derived

Daily aggregation of payments made by all customers.

ACCOUNT PAYMENT METHOD

Reference

Contains preferred payment methods for the account.

ACCOUNT PAYMENT METHOD STATUS

Base

Status history of each account preferred payment method. For example:

  • Active

  • Inactive

  • Invalid

ACCOUNT PAYMENT METHOD STATUS HIST DRVD

Derived

Collects the changes on payment method status.

ACCOUNT PAYMENT METHOD STATUS REASON

Lookup

Lookup for specific status of the account payment method. For example:

  • Activated

  • Deactivated

  • Disabled

ACCOUNT PAYMENT METHOD STATUS TYPE

Lookup

Lookup for types of ACCOUNT PAYMENT METHOD STATUS. For example:

  • Active

  • Inactive

  • Payment Rejected

ACCOUNT PAYMENT MONTH AGGR

Aggregate

Monthly summary of payments made by all customers.

ACCOUNT PAYMENT PAYMENT PLAN ASSIGNMENT

Base

Association of an ACCOUNT PAYMENT to a specific PAYMENT PLAN (after agreement). This association is critical to control whether the PAYMENT PLAN is fulfilled on time or not.

ACCOUNT PAYMENT PLAN ASSIGNMENT

Reference

Association of a PAYMENT PLAN to an ACCOUNT.

ACCOUNT PREFERRED INVOICE DELIVERY

Reference

The preferred invoice delivery type history for ACCOUNT.

ACCOUNT PRODUCT OFFERING PARTICIPATION HISTORY

Base

Defines the history of how account uses the PRODUCT OFFERING.

ACCOUNT PRODUCT SUBSCRIPTION ASSIGNMENT

Reference

History of subscriptions by an ACCOUNT.

ACCOUNT PRODUCT SUBSCRIPTION ASSIGNMENT REASON

Lookup

Each account to subscription relationship may have a reason associated with it. For example:

  • Warrant account

  • Payment account

ACCOUNT PROFILE

Reference

Records more details about the ACCOUNT.

ACCOUNT REFUND REASON

Lookup

Lookup for the reasons why a refund may occur. For example:

  • Invoice Adjustment

  • Tax Refund

ACCOUNT ROLE TYPE

Lookup

The type of ACCOUNT ROLEs, for example, primary account, secondary account, and so on.

ACCOUNT SEGMENT

Reference

The segments identifying distinct groupings of accounts with similar characteristics. The account segments are typically generated from the data mining analysis.

ACCOUNT SEGMENT ASSIGNMENT HISTORY

Reference

Assign account segment to each account.

ACCOUNT SEGMENTATION MODEL

Reference

Used to cluster the account.

ACCOUNT STATISTIC MONTH AGGR

Aggregate

Monthly summary per ACCOUNT for subscriptions, ARPU, Lifespan, and so on.

ACCOUNT STATUS HISTORY

Base

The history of account status change, including activation, suspension, and so on.

ACCOUNT STATUS REASON

Lookup

Lookup for account status reasons, or possible reasons a given account status has been changed.

ACCOUNT STATUS TYPE

Lookup

Lookup for account status types.

ACCOUNT TAX EXEMPT ASSIGNMENT

Reference

Association of TAX EXEMPTs to accounts. There may be several tax exemptions for a given account.

ACCOUNT TYPE

Lookup

Lookup for account type. For example:

  • Prepaid

  • Postpaid

ACCOUNTING CYCLE

Lookup

Internal Billing cycle which is used to calculate the usage amount and update the account balance for accounting GL purpose.

ACCOUNTING ITEM CATEGORY

Lookup

Lookup for categories that can be associated with incurred costs. For example:

  • Operations

  • Staffing

  • Supplies

ACCRUAL EVENT

Base

Any events that lead to an increase in Loyalty Points to any membership account (loyalty). This entity focuses on the origin (type, organization or partner, and so on) of the increase of points (and the amount). The events that could feed Loyalty Program Event as earning points should all come from Billing System, whatever their origin (usage, customer order, payment and so on). Retail Transactions could also feed this entity.

ACTIVITY CATEGORY

Lookup

Helps to categorized activity events. Typically there are four categories:

  • REP ACTVTY: for Sales Representative Activities

  • Contact: for any type of contact with customer or prospect - and when defined, usually related with EVENT PARTY INTERACTION.

  • INTERN: for internal activities not directly related with customers or prospects (such as meetings, intra-calls, and so on).

  • ACW: or "After Call Work" for activities following a contact, while customer or prospect is not on the line or in the shop.

ACTIVITY RELATIONSHIP TYPE

Lookup

Type of relationship between (employee) activities. This entity is not physicalized.

ACTIVITY RESULT TYPE

Lookup

Lookup for available Result Types for EMPLOYEE activities. For example:

1000 - Successful

2000 - Failed

5000 - Pending

ACTIVITY TYPE

Lookup

Type of EMPLOYEE activities, used for grouping and reporting purpose.

ADDITIONAL TEXT

Reference

Additional text can save multiple lingual notes or comments for products, parties, and other information.

ADDRESS LOCATION

Reference

Address details for physical or mailing address.

ADDRESS LOCATION ADMIN AREA ASSIGNMENT

Reference

Association of an ADDRESS LOCATION to a given ADMINISTRATIVE AREA.Since there can be several levels of jurisdictions and administration, there can be several administrative areas associated with the same address location. Normally, in case of clear administrative hierarchy (for example, Local finance administration and country level finance administration), the lowest possible level should only be used.

ADDRESS LOCATION NAME

Reference

Tracks other names used by the same ADDRESS LOCATION.

ADDRESS PHONE

Reference

Phone Numbers given by individuals or organization as contact data (typically from Retail Shops). It should not be used to store the ACCESS METHOD. It is used from a loyalty retail perspective.

ADDRESS RELATED

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.

ADDRESS RELATED REASON

Lookup

Lookup for reasons addresses may be related.

ADDRESS RELATED TYPE

Lookup

Lookup for the type of relationship between two addresses.

ADDRESS STATUS

Base

Current status of an address location. For example:

  • Active

  • Current

  • Changed

  • Old address

ADDRESS STATUS HISTORY

Base

History of the status for any ADDRESS LOCATION. For example:

Active,

Obsolete

ADDRESS STATUS REASON

Lookup

Lookup for the reason for a change to the current ADDRESS STATUS.

ADDRESS TYPE

Lookup

Lookup for address types. For example:

  • Home

  • Office

  • Warehouse

  • Billing

ADDRESS VERIFICATION TYPE

Lookup

Type of verification for the address (automatic, manual, 3rd party, and so on).

ADHOC COLLECTION

Base

Represents the "on demand" or "adhoc" Statistics Collection, that are not part of the standard statistics collection flow or process. It is typically triggered by EMPLOYEE after a network fault, an alarm, or a service problem.

ADJUSTMENT TYPE

Lookup

Type of INVOICE ADJUSTMENT.

ADMINISTRATIVE AREA

Reference

Area defined by an administration; necessarily associated with a jurisdiction of any type. For example:

MUNICIPALITY

CENSUS DISTRICT

ELECTORAL AREA

COUNTY

PARISH

ADVERTISING PERIOD

Reference

Defines an advertising period.

ADVERTISING QUARTER

Reference

Defines a quarter in an advertising calendar.

ADVERTISING WEEK

Reference

Defines a week in an advertising calendar.

ADVERTISING YEAR

Reference

Defines a year in an advertising calendar.

AF SERVICE

Reference

Defines how to forward network traffic by adding specific semantics that characterize the operation of the Assured Forwarding (AF) Service (RFC2597).

AGE BAND

Lookup

Lookup to bin the customer into different groups according age. For example:

  • 0~20 years

  • 20~30 year

  • 40-50 years

  • 50-60 years

AGE GROUP

Lookup

Group of ages for Individual only; should be filled with what Marketing requires.

AGE ON NET BAND

Lookup

Defines subscriber life cycle ranges. For example:

  • 0-1 month

  • 1-2 months

AGENT

Reference

Agent in the software modelling sense. This is not a sales representative.

AGREEMENT

Reference

Legal agreement between a Communications Service Provider and an account.

AGREEMENT ACCOUNT SUBSCRIPTION PRODUCT AGGR

Aggregate

An aggregated view for reporting and linking purposes that keeps track of current relationships between CUSTOMER, ACCOUNT, AGREEMENT and PRODUCT SUBSCRIPTION.

AGREEMENT APPROVAL

Base

Approval for the AGREEMENT from the operator's authorized employee, if the agreement requires higher level approval or review.

AGREEMENT ASSIGNMENT

Reference

Defines relationship(s) between agreements.

AGREEMENT APPROVAL ASSIGNMENT

Base

Agreement Approval Assignment is only to be used when the chain of approvals is not linear. In case of multiple parallel Authorization Requests for Approval, this entity shall be used.

AGREEMENT ASSIGNMENT REASON

Lookup

Lookup for reasons of why two agreements are related. For example:

The reason for one agreement to be replaced by another:

  • CNRT-END: The first agreement was naturally terminated

  • DLT-Delete:

  • CUST-CHNG: Voluntary change by customer

  • OP-INIT: Service Provider, operator, solicited the agreement change, normally to increase the ARPU value

The reason for one agreement to depend on another:

  • Equipment dependency

  • Network dependency

AGREEMENT ASSIGNMENT TYPE

Lookup

Lookup for types of assignment between two agreements. For example:

  • RPLC: a new agreement replaces the original agreement

  • UPGRADE: a new agreement replace original one with upgraded product

  • DEPEND: a agreement depends on existence of another agreement

AGREEMENT CHANGE INITIATOR TYPE

Lookup

Lookup to classify the initiator of the agreement change.

AGREEMENT CHANGE REASON

Lookup

Reasons for a change in AGREEMENT. Typically, it could be CUSTOMER take-over, or simple information update (CUSTOMER or main product offering level) that triggers a change in agreement information or relationship.

AGREEMENT CHANGE TYPE

Lookup

Lookup of all the type of agreement changes. For example:

  • Contract Renew

  • Contract Terminate

AGREEMENT CHANGED DRVD

Derived

Derived information about customer's current or future agreement for analytical purposes. This entity captures only changed agreements, including REPLACE or TERMINATE.

AGREEMENT DOCUMENT

Reference

The document(s) provided by the customer when a agreement was signed. For example:

  • Photocopy image of customer ID

  • The agreement itself

  • Any other documents attached to the agreement

AGREEMENT DRVD

Derived

Derived information about customer's current or future agreement for analytical purposes.

AGREEMENT INTENT

Reference

Goal of any AGREEMENT (intent). It is defined once so that all similar agreements can refer to the same Statement of intent.

AGREEMENT ITEM

Reference

Detail items for the AGREEMENT. Each item may use a different PRODUCT SPECIFICATION.

AGREEMENT PRODUCT SPEC ASSIGNMENT

Reference

This entity is superceded by AGREEMENT ITEM. It is deprecated and should only be used by legacy systems.

AGREEMENT REVENUE DAY DRVD

Derived

Summary of postpaid revenue per AGREEMENT for any given day. All fact fields are sum-able. It is an extension of the REVENUE DAY DRVD from a different point of view.

AGREEMENT SLA RELATIONSHIP

Reference

Association of SERVICE LEVEL AGREEMENT with the main AGREEMENT signed by customers. Normally, only customer specific SERVICE LEVEL AGREEMENT are mentioned, but one could generalize also to add a relationship for and agreement with "tacit" SERVICE LEVEL AGREEMENT.

AGREEMENT STATUS

Base

The status history of the AGREEMENT.

AGREEMENT STATUS REASON

Lookup

Lookup for description of the agreement status change. For example:

  • Customer originated product change

  • Customer originated churn

  • Provider originated: Bad payment (leading to suspension)

  • Customer originated: Debt paid (leading to reactivation)

  • Customer originated: Banqueroute

AGREEMENT STATUS TYPE

Lookup

Lookup for all possible types of AGREEMENT STATUS. For example:

  • Newly created for new account

  • Renewed automatically

  • Naturally expired or terminated

AGREEMENT TERM

Base

The value of terms attached to the AGREEMENT. For example:

  • Monetary amount

  • Period

  • Premium

  • Initial points

The value can vary at different time period of agreement. 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 agreement.

AGREEMENT TERM TYPE

Lookup

Lookup for all possible terms which may be attached to a AGREEMENT. For example:

  • Monetary amount

  • Period

  • Premium

  • Initial points

  • Cancellation policy

  • Subsidy

AGREEMENT TYPE

Lookup

Lookup for agreement types.

AGGREGATION INTERFACE

Reference

Defines a DEVICE INTERFACE that functions as an Aggregation Interface; that is, an interface on the aggregation portion of the network. The objective of this role is to enable the definition of POLICYs such that all Aggregation Interfaces in a particular Domain can receive the same common configuration commands.

ALLOWANCE SBRP PRICE ALTERNATION

Reference

An allowance, a number of something allowed before charging begins, for a PRODUCT SUBSCRIPTION.

AMERICAN PROPERTY ADDRESS

Reference

The Property Address format used in USA.

ANZSIC CLASSIFICATION

Reference

The SIC code used in Australia and New Zealand.

APPOINTMENT

Base

The appointment between two parties to define a future time for conducting businesses. For example:

  • A customer visit appointment, between a sales representative and a customer.

  • A technical support appointment between a customer and an engineer.

APPOINTMENT CALENDAR

Base

Appointments assigning times for vendor or provider to deliver or provide a service.

APPOINTMENT TYPE

Lookup

Lookup for appointment types. For example:

  • Recurring

  • Scheduled

ARPU BAND

Lookup

Average Revenue per Unit Band definitions. For example:

  • $0-100

  • $101-200

ARPU BASE CUSTOMER TYPE AGGR

Aggregate

The monthly summary of revenue values for ARPU calculation on CUSTOMER TYPE level.

ASSET

Reference

Any tangible or intangible economic resource, owned by the operator, which may be of interest to the financial status of the operator. For example, an asset may be a network element, for example routers, switches, or a business asset like land, building, or patent, and so on.

ASSET APPRAISAL HISTORY

Base

The valuation history of the ASSET.

ASSET CONDITION HISTORY

Base

The condition history of an ASSET, as inspected by an internal employee or a contractor. This is important for vehicles or buildings.

ASSET DEPRECIATION HISTORY

Base

The financial depreciation history of a given ASSET.

ASSET PARTY ASSOCIATION

Reference

The relationship between a PARTY and an ASSET.

ASSET SITE ASSIGNMENT

Reference

The history of locations of each ASSET. An ASSET may be moved among different SITEs in its life cycle.

ASSET TYPE

Lookup

The Type of ASSET. For example:

  • Land

  • Building

  • Computer

ATM INTERFACE

Reference

Asynchronous Transfer Mode (ATM), is a network technology based on transferring data in cells of a fixed size. The cell used with ATM is relatively small compared to that used with older technologies. In principle, the small, constant cell size allows ATM equipment to transmit video, audio, and computer data over the same network, and assure that no single type of data can dominate network traffic. ATM creates a fixed route between two points whenever data transfer begins. This differs from TCP/IP, in which messages are divided into packets and each packet can take a different route from source to destination. This difference makes it easier to track and bill data usage across an ATM network, but it makes it less adaptable to sudden surges in network traffic.

AUTHORIZATION METHOD

Lookup

Method used to authorize a payment (PIN, Signature, TAN, TAN SMS, and so on) or an official document like an agreement (Certified Email or PDF, signature, and so on).

AUTONOMOUS SYSTEM

Reference

An Autonomous System (AS) provides a structured view of routing by segregating the system that is using routing. For example:

  • The Internet

  • A corporate intranet

  • Company extranet

This segregates the system into a set of separately administered domains and each has its own independent routing policies. This is defined in RFC1771.

AUXILIARY COMPONENT

Reference

This entity represents managed entities, such as power supplies, fans, and cables, which are required for the proper operation of the Device but have a primary function that is different than the primary end-user function(s) of the Device.

The difference between Auxiliary Components and other subclasses of EQUIPMENT are whether the physical object performs a function intrinsic to the main function of the Device. For example, consider a ROUTER. The routers main function is to route and forward packets. A Power Supply is an Auxiliary Component, because even though it is needed for the proper operation of the ROUTER, it does not directly help in routing and forwarding packets. A Line Card, that provides routing functionality, is a subclass of EQUIPMENT because its purpose is to route and forward packets. Similar examples exist for different types of equipment, where their criteria may be different. For example, instead of whether it routes or forwards packets, the criterion "does it carry signal" may be useful to appropriately classify components.

AWARD LEVEL

Lookup

The level of customer's loyalty, based on the LOYALTY PROGRAM and ability to contribute to the revenue of the carrier. For example:

  • Platinum

  • Gold

  • Silver

  • Bronze

BANK

Reference

Bank information that may be used in transactions.

BANK DIRECT DEBIT CHANNEL

Reference

Subtype of the PAYMENT CHANNEL, which tracks various bank channels where customers can pay by direct debt method.

BARING REASON

Lookup

Lookup defining reasons a customer may be banned from using a service.

BASE DAY

Reference

The abstracted information about a day, which serves as a base for DAY.

BASE STATION CONTROLLER

Reference

Subtype of RESOURCE, 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.

BASE TRANSCEIVER STATION

Reference

Base Transceiver Station (BTS) is the equipment which facilitates the wireless communication between User Equipment (UE) and the network.

BASEBAND UNIT

Reference

The BaseBand Unit (BBU) is part of 3G Node B base station system, which is in charge of base station control.

BER FER ERROR RATIO DAY DRVD

Derived

Daily BER (Bit Error Rate) and FER (Frame Error Rate) statistics about the network elements.

BER FER ERROR RATIO MONTH AGGR

Aggregate

Monthly BER (Bit Error Rate) and FER (Frame Error Rate) statistics about the network elements.

Derived from BER FER ERROR RATIO DAY DRVD.

BER FER TYPE

Lookup

Lookup to indicate the statistics value for BER (Bit Error Rate) or FER (Frame Error Rate).

BILLING CYCLE

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:

  • The first day of month

  • 10th day of month

BILLING FREQUENCY

Lookup

The billing frequency specifies the number of billing periods that comprise the billing cycle.

BILLING OCCURRENCE TYPE

Lookup

Type of billing occurrence which could be classified by the trigger type. For example:

  • Triggered by customer inquiry.

  • Triggered by automatic billing cycle.

BILLING PERIOD

Lookup

The billing period specifies the unit to be used to calculate the billing cycle (such as days or months).

BILLING STATUS CATEGORY

Lookup

Lookup for category of billing status. For example:

  • Successfully Billed

  • Failure to Bill

BILLING STATUS REASON

Lookup

Lookup for reasons why the UDR EVENT is at certain billing status. For example:

  • Wrong format

  • Missing account information

BILLING STATUS TYPE

Lookup

Lookup for the status type of billing result, including the reasons. For example:

  • Incorrect_data_failed

  • Incorrect_user_not_found

  • Successful

BLACK LIST HISTORY

Base

History of all black-listed customers.

BRAND

Lookup

The brands associated with hardware (usually this applies for handsets, but also for ITEM SPECIFICATIONs).

BRIDGING PROTOCOL

Reference

Bridging Protocols operate at the data link layer of the OSI model, and are used to define communications over different types of homogeneous and heterogeneous local area networks.

BROADBAND RATING PLAN

Reference

Subtype of PRODUCT OFFERING PRICE applied to BROADBAND SERVICE.

BROADBAND SERVICE

Reference

Broadband service is subtype of SERVICE, to track the broadband services used by the user.

BROADBAND USAGE EVENT

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.

BROWSER TYPE

Lookup

Lookup for brand of client browser. For example:

  • Internet Explorer

  • Firefox

BROWSER VERSION

Reference

Version of customer browser, such as Internet Explorer 6.0, Firefox 3.6, and so on.

BUSINESS ASSET

Reference

Any business asset that may be of financial interest to the operator. For example:

  • Land

  • Buildings

  • Equipment, such as office computers

Note: the equipment which is part of the network is in the entity: RESOURCE

BUSINESS HALF MONTH

Reference

Defines month-in-half in a business calendar.

BUSINESS HALF YEAR

Reference

Defines half year in a business calendar.

BUSINESS INTERACTION

Reference

Describes an arrangement, agreement, communication, or joint activity between one or more PARTY ROLEs, RESOURCE ROLEs, or CUSTOMER ACCOUNTs. A Business Interaction may consist of one or more BUSINESS INTERACTION ITEMs. A BUSINESS INTERACTION ITEM may refer to a Product, Service, RESOURCE, or one of their specifications. A Business Interaction is further defined by one or more Places. One Business Interaction may reference another Business Interaction and one BUSINESS INTERACTION ITEM may reference another BUSINESS INTERACTION ITEM on the same or different Business Interaction.

There are five types of Business Interactions:

  • Requests

  • Responses

  • Notifications

  • Agreements

  • Instructions

BUSINESS INTERACTION ASSIGNMENT

Reference

Defines the relationship between two BUSINESS INTERACTIONs.

BUSINESS INTERACTION ASSIGNMENT TYPE

Lookup

Interaction type such as subordinate business interaction.

BUSINESS INTERACTION CHARACTERISTIC

Reference

A characteristic quality or distinctive feature of a BUSINESS INTERACTION.

BUSINESS INTERACTION CHARACTERISTIC TYPE

Lookup

Type of BUSINESS INTERACTION CHARACTERISTIC.

BUSINESS INTERACTION CHARACTERISTIC VALUE

Reference

A value of a BUSINESS INTERACTION CHARACTERISTIC.

BUSINESS INTERACTION HISTORY

Base

The temporary status of an interaction, non current, if it was not COMPLETED when it was first loaded.

BUSINESS INTERACTION ITEM

Base

The purpose for the Business Interaction expressed in terms of a Product Type, PRODUCT OFFERING, Service Type, or RESOURCE SPECIFICATION or may refer to a Product, Service, or RESOURCE. The detail items included in the BUSINESS INTERACTION.

BUSINESS INTERACTION ITEM PRICE

Base

This is the actual price charged to the BUSINESS INTERACTION ITEM, despite the original list and discount price from product setting.

An amount associated with a BUSINESS INTERACTION ITEM that is valued by the associated product offering Price

BUSINESS INTERACTION ITEM SPECIFICATION

Reference

Specification of how a given BUSINESS INTERACTION ITEM is supposed to be filled (data, information, and so on). Normally ignored because the content expected is obvious, this entity is present for completeness only.

BUSINESS INTERACTION LOCATION ASSIGNMENT

Reference

The BUSINESS INTERACTION ROLE which can be assigned to an address. For example:

  • Billing address

  • Shipment address

BUSINESS INTERACTION PAYMENT ASSIGNMENT

Base

The association between a payment and BUSINESS INTERACTION. For example, a payment for a agreement or a customer order.

BUSINESS INTERACTION ROLE

Reference

The roles which can be played by PARTY or other business interaction elements like Resource, and so on.

BUSINESS INTERACTION SPECIFICATION

Reference

The invariant characteristics (attributes in the business view, and methods, constraints, relationships, and behavior in the system view) and behavior of a BUSINESS INTERACTION. This is done by optionally defining a set of BUSINESS INTERACTION SPECIFICATION items, each of which aggregates one or more other types of Specifications. This helps to ensure that different BUSINESS INTERACTION have the same basic characteristics and behavior by deriving them from the same BUSINESS INTERACTION SPECIFICATION.

BUSINESS INTERACTION STATUS REASON

Lookup

The reason to explain why a BUSINESS INTERACTION has had a change in status.

BUSINESS INTERACTION VERSION

Reference

Represents the ability to distinguish between different instances of RESOURCE SPECIFICATIONs. It represents a particular form or variety of a RESOURCE SPECIFICATION that is different from others or from the original. The form represents differences in attributes, methods, relationships, or constraints that characterize this particular RESOURCE SPECIFICATION, but which are not enough to warrant creating a new RESOURCE SPECIFICATION.

BUSINESS LEGAL STATUS

Lookup

The legal status of the company. For example, a Public Company, Private, and so on.

BUSINESS MONTH

Reference

Defines month in a business calendar.

BUSINESS QUARTER

Reference

Defines quarter in a business calendar.

BUSINESS UNIT JOB ROLE

Reference

Assigns job roles to a business unit within the organization.

BUSINESS UNIT SHIFT

Reference

Work shift associated with the Business Unit, mapped to the Employee job roles for the allocation for these shifts.

BUSINESS WEEK

Reference

Defines week in a business calendar.

BUSINESS YEAR

Reference

Defines year in a business calendar.

CABLE

Reference

A container of conductors or fibres. At least two connectors are attached to a cable.

CABLE MODEM

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.

CALENDAR HALF MONTH

Reference

Defines month-in-half in a Gregorian or Normal Calendar.

CALENDAR HALF YEAR

Reference

Defines half year in a Gregorian or Normal Calendar.

CALENDAR MONTH

Reference

Defines month in a Gregorian or Normal Calendar.

CALENDAR QUARTER

Reference

Defines quarter in a Gregorian or Normal Calendar.

CALENDAR WEEK

Reference

Defines weeks in a Gregorian or Normal Calendar.

CALENDAR YEAR

Reference

Defines years in a Gregorian or Normal Calendar.

CALL CATEGORY

Lookup

Lookup for call categories. For example: Data, Fax, or Voice.

CALL CENTER

Reference

Defines call centers for a carrier or provider.

CALL CENTER AGENT

Reference

Agents of a call center.

CALL CENTER AGENT TYPE

Lookup

Lookup for call center agent types. For example: Employee or IVR.

CALL CENTER CALL MONTH AGGR

Aggregate

Monthly summary of customer call statistics for the call center.

CALL CENTER CASE MONTH AGGR

Aggregate

Monthly summary of statistics for all the cases initiated or resolved by the call center.

CALL CENTER CASE SUB TYPE

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".

CALL CENTER CASE TITLE

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:

  • Handset Technical Support

  • Product Usage Technical Support

  • Network Fault Technical Support

CALL CENTER CASE TYPE

Lookup

Lookup for type of call center cases. For example:

  • Cmpl: Complaint

  • Inqry: Inquiry

  • Srv: Service Request

CALL CENTER SERVICE CAPABILITY

Reference

Assigns to the CALL CENTER, the languages, products, or geographical areas which the call center can serve.

CALL DIRECTION

Lookup

To indicate incoming call or outgoing call.

CALL FORWARD

Reference

A type of phone service. The calling party can be on hold if receiving party is in a call.

CALL OTHER TYPE

Lookup

This is to record any other characteristics of the call, such as, 3-party call, or any user defined special type of call.

CALL RECYCLED REASON

Lookup

Lookup for reasons why the voice carrying channel is being recycled during the call.

CALL ROUTING TYPE

Lookup

Lookup to define how the call was routed. For example:

  • Calling from external carrier

  • From Wireless to Land Phone

CALL SERVICE TYPE

Lookup

Lookup for service types that could be used in a call. For example:

  • Toll-Free number such as 800/400

  • Emergency Call such as 911, 112, 110

CALL SOURCE DESTINATION

Reference

Entity represents all the possible zones associated with a combination of any sources and destinations. Those call sources or destinations classify the calls into different groups, such as local call, long distance domestic call, or internal call.

Note: it is not the purpose of this entity to reproduce the A-B number mapping (this is a billing operation). This entity only represents the result of such a mapping.

CALL SUCCESS FAILURE TYPE

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.

CALL SURCHARGE

Lookup

Any extra charge on the call in addition to the normal rating.

CALL TERMINATION REASON

Lookup

Lookup for the reasons a call may be terminated. For example:

  • Dropped

  • Successful End

CALL TYPE

Lookup

Lookup to further classify call category into call types. For example:

  • Voice Voice

  • SMS and MMS

  • Data and FAX

  • Information services

  • GPRS services for Data and Fax

CALLER ID

Reference

Subtype of PRODUCT SPECIFICATION, with specific information about CALLER ID service.

CAMPAIGN

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 standalone. A campaign is always associated with a MEDIA OBJECT, such as a television campaign.

CAMPAIGN CHANNEL

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.

CAMPAIGN CHANNEL ASSIGNMENT

Reference

The assignment to define which CAMPAIGN is lunched at which CAMPAIGN CHANNEL.

CAMPAIGN CHANNEL TYPE

Lookup

Lookup for campaign channel type. For example: newspaper, Television, Magazine.

CAMPAIGN CHARACTERISTIC

Reference

A characteristic quality or distinctive feature of a CAMPAIGN. The characteristic can take on a discrete value, such as the number of press releases, can take on a range of values, for example the number of prospects reached is 50,000 - 100,000, or can be derived from a formula, for example, the number of brokerage house pickups = the sum of all brokerage house instance characteristics.

CAMPAIGN COST

Base

Subtype of COST which can apply to a CAMPAIGN.

CAMPAIGN CHARACTERISTIC VALUE

Reference

A number or text that can be assigned to a CAMPAIGN CHARACTERISTIC.

CAMPAIGN DOCUMENT

Reference

The customer documents provided during campaign activities.

CAMPAIGN HISTORY DAY DRVD

Derived

Daily aggregate of campaign results by PROMOTION RESULT TYPE.

CAMPAIGN MANAGEMENT HISTORY

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.

CAMPAIGN MEDIA

Reference

Relationship between a CAMPAIGN and the MEDIA OBJECT chosen to run this campaign (Radio, TV, newspaper, posters, Internet Adds, and so on).

CAMPAIGN MEDIA SELLING ITEM

Reference

Item, resource, associated with the CAMPAIGN and the MEDIA OBJECT used. It could go from specific accessories that one could get with a specific promotion.

CAMPAIGN MESSAGE

Reference

Details regarding message broadcast or sent during a CAMPAIGN.

CAMPAIGN MESSAGE CREATIVE

Base

Information about the creative content of the message.

CAMPAIGN MESSAGE DEPICTION

Reference

Details about how the execution message is depicted for a CAMPAIGN.

CAMPAIGN PURPOSE TYPE

Lookup

Lookup for types of campaign purposes. For example:

  • Acquire new customers

  • Consolidate existing customers

  • Retention existing customers

CAMPAIGN RELATIONSHIP

Reference

Defines the relationship between two CAMPAIGNs. For example:

  • Replace/upgrade

  • Enhance

CAMPAIGN STATUS

Lookup

Status of CAMPAIGN.

CAMPAIGN TERM VALUE

Reference

The term value for a given campaign.

CAMPAIGN TYPE

Lookup

Lookup for type of campaign. For example:

  • A targeted promotion (to specific individuals, account or group of accounts)

  • A mass market promotion (to a massive audience usually through radio, Television and newspaper)

CANNIBALIZATION DETAIL DAY DRVD

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".

CAPACITY

Reference

This is an abstract base entity that is the parent for both the PHYSICAL CAPACITY and the LOGICAL CAPACITY. These entities define the minimum and maximum requirements, limits, or other variable features of another entity.

CARD

Reference

Represents a type of physical container that can be plugged into a SLOT. A card may represent a primary function, for example, a networking card, or an auxiliary function, for example, a memory card, that supports another card. All objects of this type are capable of carrying electrical and optical signals. A card also provides a mounting point for other types of Managed Physical Resources, such as Chips or Cards.

CARD HOLDER VERIFICATION TYPE

Lookup

Verification Method to check a Card Holder self (personal ID, Birthday, extra PIN...), typically for Credit Card but it could be generalized.

CARD RELATIONSHIP

Reference

This association entity represents the semantics of the Card On Card aggregation. The Card Relationship defines an attribute that describes how the CARD is mounted on or plugged into another CARD.

CARD TYPE

Lookup

Lookup for codes denoting which kind of card was accepted. For example:

  • Amex

  • Diners

  • Disc

  • JCB

  • MC

  • Visa

CELL

Reference

The cell in a wireless network such as GSM, which is an area serviced by the BASE TRANSCEIVER STATION (BTS).

CELL OUTAGE REASON

Lookup

Lookup for reasons a cell outage could occur. For example:

  • Power failure

  • Natural disaster

  • Theft

CELL SECTOR

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.

CELL SITE

Reference

This is where the base station radio equipment and their antennas are located. A cell site gives radio coverage to a cell.

CELL SITE COST

Base

Subtype of COST which could apply to a CELL SITE. For example:

  • Expenses for the cell site building

  • Rent

  • Maintenance

CELL SITE TYPE

Lookup

Lookup for type of CELL SITE. For example: the cell site type can be classified by GSM/CDMA/PHS/broadband/Pay TV.

CELL STATISTIC DAY DRVD

Derived

The network parameters and run time statistics captured at the cell level.

CELL STATISTIC MONTH AGGR

Aggregate

The network parameters and run time statistics for all CELL SITEs aggregated at the month and certain geography level.

CELL TYPE

Lookup

Lookup for all possible cell types. For example, Macro, Micro, and Pico:

  • Macro cells are large geographical area where subscriber base is less dense.

  • Micro cells are small cells in side the macro cells to cover high subscriber density and uneven distribution.

  • Pico cells are used in large buildings, where signals from ground towers are poor.

CERTIFICATE TYPE

Lookup

Type of Certificate (Medical, Tax Authority, Government, and so on).

CFS SPEC VERSION DETAIL

Reference

Defines the relationship of the CFS Type aggregation. Specifically, it enables an application to define which set of versions of this CUSTOMER FACING SERVICE Type are appropriate for a given task.

CHANGE PROPOSED BY TYPE

Lookup

Lookup for who proposed the changes for a customer tariff change. For example:

  • By customer

  • By operator

CHANNEL

Reference

Identifies all the channels through which customers interact with the telco provider for sales or services purposes.

CHANNEL COST

Base

Subtype of COST, which collects all costs specifically related to a given sales channel.

CHANNEL TYPE

Lookup

Lookup for types of channels as defined by their functions. For example:

  • Sales channel

  • Payment channel

  • Debt collection channel

  • Loyalty program channel (where to join/change/redeem loyalty program)

CHASSIS

Reference

A Chassis is a type of Secure Holder that encloses other Managed Physical Entities and provides a definable functionality in its own right, such as a desktop or a network device. For example, a router or a switch.

CHASSIS POSITION

Reference

Represents the semantics of the Chassis In Rack aggregation. Defines two attributes: Position and Location, to define where the CHASSIS is located in the RACK.

CHURN SVM FACTOR

Derived

Mining target entity to store churn factors retrieved from SVM mining model.

CHURN SVM ROC

Derived

Mining target entity to store churn ROC details calculated using SVM mining model.

CIRCUIT CATEGORY

Lookup

Lookup for categories to classify the type of circuit. For example:

  • Analogue Voice

  • Digital Data Services (DDS)

  • ATM

CIRCUIT COMPONENT

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:

  1. From the customer site to the exchange/switch

  2. From the switch to another switch

  3. From the second switch to the second customer site

There are two scenarios:

  • The circuit component links two switches.

  • The circuit component links a switch with a customer site

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.

CIRCUIT RENTAL

Base

Business activities of renting some circuits to other operators, in return for a monthly, or fixed, revenue.

CIRCUIT RENTAL EVENT TYPE

Lookup

Lookup for types of rental events. For example:

  • Rental Initial

  • Monthly Charge

  • Maintenance Charge

  • Termination

CIRCUIT TRAFFIC

Base

The traffic volume statistics over certain periods, where periods are implementation dependent but generally hourly, for each CIRCUIT COMPONENT.

CIRCUIT TYPE

Lookup

Lookup for type of detailed circuit types. For example:

For interconnect:

  • T1 or E1, carry 1.5mbps

  • T2 6.312 Mbit/s

  • T3 44Mbit/s

For customer connection ADSL:

  • ADSL 1: Normally 1Mbit/s

  • ADSL 2x

CLASS BASE WEIGHTED FAIR QUEUE SERVICE

Reference

Specifies the algorithm that schedules packets in queues and guarantees a certain transmission rate. If a queue is not in use, the bandwidth is made available to other queues.

CLASSIFIER SERVICE

Reference

Describes the internal component of the forwarding path, used to recognize and distinguish among different packet streams or flows.

CLIENT

Reference

Client (part of the software application). This is not the customer.

CLIENT HOST

Reference

Host on which the CLIENT runs (from a software application perspective). It is a Resource identification expected.

CLIENT VERSION

Reference

Version of the CLIENT (part of a software application that the end-user is running).

COLLECTION

Reference

This entity represents collections of Managed Entity objects. A Collection enables common attributes, methods, relationships, and other semantics to be applied to different types of Collections of Managed Entity objects. These can then be refined in the subclasses of Collection.

COLLECTION AGENCY

Reference

Subtype of a PARTY, who collects the customer debt on behalf of the operator under a financial agreement. For example:

  • Debt collection

  • Roaming settlement collection

COLLECTION TYPE

Lookup

Type of Statistic Collection (alerts, alarms, network KPIs, and so on).

COMMISSION DRVD

Derived

Statistics of all commissions granted to the sales agents because of the sales of products and services in the given period.

COMMISSION MONTH AGGR

Aggregate

Monthly aggregation of all commissions granted to the sales agents because of the sales of products and services in the given period.

COMMISSION TYPE

Lookup

Lookup for commission types that may be paid to sales representatives. For example:

  • FLAT: flat rate

  • PERCENTAGE: percent of transaction amount

COMMUNICATION SERVICE

Reference

The service type of product, including fixed line phone call, wireless phone call, and so on.

COMP INTEL CHARACTERISTIC

Reference

A characteristic quality or distinctive feature of a COMPETITOR INTELLIGENCE. The characteristic can take on a discrete value, such as number of press releases, can take on a range of values, for example, number customers within a MARKET SEGMENT (50,000 - 100,000), or can be derived from a formula, for example, number of products offered in a MARKET SEGMENT = the number of the COMPETITOR's Products associated to the MARKET SEGMENT.

COMP INTEL CHARACTERISTIC VALUE

Reference

A number or text that can be assigned to a COMP INTEL CHARACTERISTIC.

COMP INTEL MARKET SEGMENT

Reference

A MARKET SEGMENT in which a COMPETITOR makes Product available.

COMP PROD CRRL CHARACTERISTIC

Reference

A characteristic quality or distinctive feature of a COMPETITOR PRODUCT CORRELATION. The characteristic can be take on a discrete value, such as geographic disbursement (central, national, cascading). The characteristic can take on a range of values, (for example, Competitor Product Offering revenue of $500,000 - $1,000,000), or can be derived from a formula (for example, number of MARKET SEGMENTs in correlation = number of MARKET SEGMENTs related to this correlation).

COMP PROD CRRL CHARACTERISTIC ASSIGNMENT

Reference

Assign the COMP PROD CRRL CHARACTERISTIC to the related COMPETITOR INTELLIGENCE characteristic.

COMP PROD CRRL CHARACTERISTIC RELATIONSHIP

Reference

Defines the relationship between two COMP PROD CRRL CHARACTERISTICs.

COMP PROD CRRL CHARACTERISTIC VALUE

Reference

A number or text that can be assigned to a COMP PROD CRRL CHARACTERISTIC.

COMPENSATORY REASON

Lookup

Possible REASONs for being compensated (Standard Sales program, accelerator, or Hardware Defect, and so on).

COMPETITIVE TIER

Reference

A classification of a COMPETITOR, such as by size, product lines offered, and so on.

COMPETITOR

Reference

A PARTY that offers PRODUCT SPECIFICATION similar to the enterprise's PRODUCT SPECIFICATION in a MARKET SEGMENT.

COMPETITOR INTELLIGENCE

Reference

Facts gathered about a COMPETITOR's plans and activities. These facts perform COMPETITOR SWOT analysis to better understand a COMPETITOR.

COMPETITOR INTELLIGENCE PARTY ROLE

Reference

The PARTY who developed the COMPETITOR INTELLIGENCE.

COMPETITOR MARKET SEGMENT ASSIGNMENT

Reference

A MARKET SEGMENT served by a COMPETITOR.

COMPETITOR MARKET SEGMENT SWOT

Reference

Specifies a Strength, Weakness, Opportunity, or Threat in a MARKET SEGMENT served by a COMPETITOR.

COMPETITOR PRODUCT CORRELATION

Reference

A comparison or relationship between an enterprise-s PRODUCT SPECIFICATION with a COMPETITORs' Product. Information about the correlation may include MARKET SEGMENTs, Product Offering life cycle stage, Jurisdiction, or definable COMP PROD CRRL CHARACTERISTICs.

COMPETITOR SWOT

Reference

General (non-MARKET SEGMENT specific) Strength, Weakness, Opportunity, or Threat when compared to a COMPETITOR.

COMPETITOR TIER ASSIGNMENT

Reference

A classification of a COMPETITOR, such as by size, product lines offered, and so forth.

COMPLEX ADDRESS

Reference

Complex Address describes the internal address for a complex (for GEOGRAPHY COMPLEX). For example, the internal road, building number, and so on.

COMPOSITE COMP PROD CRRL CHARACTERISTIC

Reference

A type of COMP INTEL CHARACTERISTIC that is formed by aggregating other COMP INTEL CHARACTERISTIC, which may be Composite or Atomic COMP INTEL CHARACTERISTIC.

COMPOSITE PROD OFFER PRICE COMPONENT ASSIGNMENT

Reference

Association of price component to Composite Product Offering. It allows building complex pricing.

COMPOSITE PRODUCT SPECIFICATION

Reference

Groups of PRODUCT SPECIFICATIONs bundled to serve as basis of a PRODUCT OFFERING. The composite product specification is not customer facing and a customer should subscribe to a composite product specification through the PRODUCT OFFERING. For example:

  • Tariff Liberty 60, Wireless phone, 3 Friends & Family Network Intern Numbers

  • DSL 32Mbit/s + VoIP Phone + TV Entertainment + Pay TV Soccer Championship

COMPOSITE PRODUCT SPECIFICATION ASSIGNMENT

Reference

Assigns PRODUCT SPECIFICATION(s) to a COMPOSITE PRODUCT SPECIFICATION.

COMPOSITE PRODUCT SPECIFICATION CHARGE TYPE

Lookup

Lookup for type codes and descriptions for COMPOSITE PRODUCT SPECIFICATION charge on a PRODUCT SPECIFICATION. For example:

  • One time charge

  • Usage Duration charge

  • Usage per Call charge

  • Usage amount charge (Data transfer)

  • Monthly Cycle Forward Fee

  • Monthly Cycle Arrear Fee

  • Free Unit Charge

  • Free Charge

COMPOSITE PRODUCT SPECIFICATION TYPE

Lookup

Type of COMPOSITE PRODUCT SPECIFICATION. It groups COMPOSITE PRODUCT SPECIFICATIONs that share common characteristics.

COMPOSITE PRODUCT SUBSCRIPTION PRICE

Reference

A PRODUCT PRICE COMPONENT (associated with PRODUCT SUBSCRIPTION) that is made up of parts.

COMPOSITE SERVICE

Reference

A group of services together forming a new service.

COMPOSITE SERVICE INCLUSION

Reference

Defines the relationship between COMPOSITE SERVICE and atomic service. Composite service inclusion defines how the COMPOSITE SERVICE is formed.

COMPOSITE SERVICE TYPE INCLUSION

Reference

Tracks the relationship of which atomic service type each composite service type includes.

COMPOUND CONDITIONING ELEMENT

Reference

Abstract entity that defines "compound" traffic conditioning elements.

COMPOUND RESOURCE

Reference

This is the abstract base entity for all composite entities that are inherently manageable and form a PRODUCT SPECIFICATION.

The key difference between network element and COMPOUND RESOURCE is that network element describes either a Physical or a Logical entity. In contrast, COMPOUND RESOURCE describes managed entities that are collections of other managed entities. A key point is that each managed entity that is part of a COMPOUND RESOURCE can be individually managed as either a PHYSICAL RESOURCE or a LOGICAL RESOURCE.

COMPOUND RESOURCE COLLECTION

Reference

An entity that is individually manageable.

A Compound Element Collection is an aggregate entity consisting of RESOURCE and optionally Compound Element Collection entities. As such, a Compound Element Collection represents a set of PHYSICAL RESOURCEs and LOGICAL RESOURCEs that collectively represent a managed entity. For example, a Network is a subclass of Compound Element Collection. A Network can be made up of other Networks and SubNetworks. Each Network or SubNetwork can be made up of physical and logical components, gathered and represented by an RESOURCE Collection. Each node in the network can be represented by a RESOURCE.

COMPOUND RESOURCE COMPOUND DETAIL ASSIGNMENT

Reference

Defines the semantics of aggregating COMPOUND RESOURCEs using aggregation. It associates the various components. Also see the TMF SID and the DEN-ng system for more details. See also COMPOUND RESOURCE DETAIL.

COMPOUND RESOURCE DETAIL

Reference

Defines the semantics of the COMPOUND RESOURCE aggregation. Compound Element Detail is abstract, because only its subclasses should be instantiated. There are three concrete subclasses of this class, which are used to represent the aggregation of PHYSICAL RESOURCE, LOGICAL RESOURCE, and COMPOUND RESOURCE into this particular COMPOUND RESOURCE.

COMPOUND RESOURCE DETAIL TYPE

Lookup

The various types for a COMPOUND RESOURCE DETAIL. For example:

  • PHA: Physical Aspect

  • LGA: Logical Aspect

  • OTHA: Other Aspect

COMPOUND RESOURCE PHYSICAL DETAIL

Reference

This is a concrete entity that defines the semantics of aggregating PHYSICAL RESOURCE into a COMPOUND RESOURCE.

COMPOUND RESOURCE ROLE

Reference

This entity is a role that is defined by the interaction between PHYSICAL RESOURCE ROLEs and LOGICAL RESOURCE ROLE. There must be at least one or more PHYSICAL RESOURCE ROLEs and one or more LOGICAL RESOURCE ROLE to form a Compound Element Role. However, neither a PHYSICAL RESOURCE ROLE nor a Logical Element Role has to belong to a Compound Resource Role.

COMPOUND RESOURCE ROLE ASSIGNMENT

Reference

Implements the relationship between COMPOUND RESOURCE and network element role.

COMPOUND RESOURCE ROLE SPEC

Reference

Specification of COMPOUND RESOURCE ROLE: it details the common characteristics of a COMPOUND RESOURCE ROLE.

COMPOUND RESOURCE SPEC

Reference

This is the abstract base entity that defines the invariant characteristics and behavior, attributes, methods, constraints, and relationships, of a COMPOUND RESOURCE. The key difference between a Compound Resource Spec and either a PHYSICAL RESOURCE SPECIFICATION and a LOGICAL RESOURCE SPECIFICATION is that a PHYSICAL RESOURCE SPECIFICATION and LOGICAL RESOURCE SPECIFICATION define templates for specifying the invariant characteristics and behavior of PHYSICAL RESOURCEs and LOGICAL RESOURCEs, respectively. In contrast, a Compound Resource Spec describes templates that contain at least one PHYSICAL RESOURCE SPECIFICATION and at least one LOGICAL RESOURCE SPECIFICATION. Optionally, one or more Compound Resource Specs may also be specified. Thus, a Compound Resource Spec is in effect a "shorthand notation" for specifying complementary PHYSICAL RESOURCE SPECIFICATIONs and LOGICAL RESOURCE SPECIFICATIONs.

COMPOUND RESOURCE SPEC ATOMIC

Reference

This entity describes specific attributes, behavior, relationships, constraints, and semantics for building COMPOUND RESOURCE objects. The purpose of this entity is to track specifications of COMPOUND RESOURCEs separately from other types of Resource Specifications. This entity inherits the Modifies Resource Spec aggregation, and therefore can be used with the corresponding COMPOUND RESOURCE entity. The key difference between a COMPOUND RESOURCE SPEC and either a PHYSICAL RESOURCE SPECIFICATION and a Logical Resource Type is that a PHYSICAL RESOURCE SPECIFICATION and Logical Resource Type define templates for specifying the invariant characteristics and behavior of PHYSICAL RESOURCEs and LOGICAL RESOURCEs, respectively. In contrast, a COMPOUND RESOURCE SPEC describes templates that contain at least one PHYSICAL RESOURCE SPECIFICATION and at least one Logical Resource Type. Optionally, one or more COMPOUND RESOURCE SPECs may also be specified. The difference between a Compound Resource Spec Atomic entity and a COMPOUND RESOURCE SPEC COMPOSITE entity is that a Compound Resource Spec Atomic entity is designed to be a standalone entity.

Note that it still aggregates at least one PHYSICAL RESOURCE SPECIFICATION and at least one Logical Resource Type; however, the result is that this Compound Resource Spec Atomic entity can be used by itself.) In contrast, a COMPOUND RESOURCE SPEC COMPOSITE entity is made up of one or more COMPOUND RESOURCE SPECs, one of which must be a Compound Resource Spec Atomic entity.

COMPOUND RESOURCE SPEC COMPOSITE

Reference

This entity describes specific attributes, behavior, relationships, constraints, and semantics for building composite COMPOUND RESOURCE objects. The purpose of this entity is to track specifications of COMPOUND RESOURCEs separately from other types of Resource Specifications.

This entity inherits the modifies Resource Spec aggregation, and therefore can be used with the corresponding COMPOUND RESOURCE entity. The key difference between a COMPOUND RESOURCE SPEC and either a PHYSICAL RESOURCE SPECIFICATION and a Logical Resource Type is that a PHYSICAL RESOURCE SPECIFICATION and Logical Resource Type define templates for specifying the invariant characteristics and behavior of PHYSICAL RESOURCEs and LOGICAL RESOURCEs, respectively. In contrast, a COMPOUND RESOURCE SPEC describes templates that contain at least one PHYSICAL RESOURCE SPECIFICATION and at least one Logical Resource Type. Optionally, one or more COMPOUND RESOURCE SPECs may also be specified. The difference between a COMPOUND RESOURCE SPEC ATOMIC entity and a Compound Resource Spec Composite entity is that a COMPOUND RESOURCE SPEC COMPOSITE entity is designed to be a standalone entity. (Note that it still aggregates at least one PHYSICAL RESOURCE SPECIFICATION and at least one Logical Resource Type; however, the result is that this COMPOUND RESOURCE SPEC ATOMIC entity can be used by itself.) In contrast, a Compound Resource Spec Composite entity is made up of one or more COMPOUND RESOURCE SPECs, one of which must be a COMPOUND RESOURCE SPEC COMPOSITE entity.

COMPOUND RESOURCE TP DETAIL

Reference

Concrete entity that links TERMINATION POINT to COMPOUND RESOURCE. For example, it will describe characteristics and behavior of the TERMINATION POINTs that comprise this particular Resource Port in terms of dependencies and how a TERMINATION POINT interacts with other TERMINATION POINTs.

COMPOUND RESOURCE UNIT

Reference

A Resource Unit is an entity that is individually manageable. The Compound Resource Unit is an aggregate entity consisting of both physical and logical aspects of a managed Resource. For example, a ROUTER is a Resource Unit. Different PHYSICAL RESOURCE objects can model the physical aspects of the ROUTER in detail. For example, its CARDs, the number and type of PHYSICAL PORTs that are on each CARD, and so forth), and different LOGICAL RESOURCE objects can model the logical aspects of the ROUTER in detail (For example, what Software it is running, how many DEVICE INTERFACEs of what type are currently enabled, if there are any outstanding Faults or Alarms, and so forth). Resource aggregates all PHYSICAL RESOURCE and LOGICAL RESOURCE objects, enabling a high-level view of the physical and logical aspects of the Resource to be provided.

CONFIGURABLE PRODSPECCHAR PRODSPEC ASSIGNMENT

Reference

Assigns one or more CONFIGURABLE PRODUCT SPECIFICATION CHARACTERISTICs to a PRODUCT SPECIFICATION. Multiple products may have the same CONFIGURABLE PRODUCT SPECIFICATION CHARACTERISTICs.

CONFIGURABLE PRODUCT SPECIFICATION CHARACTERISTIC

Reference

Available features that may be associated with one or more PRODUCT SPECIFICATIONs. For example, for a handset there are features such as:

  • MP3 indicator

  • MIDIindicator

  • 3G indicator

  • JAVA indicator

  • GSM 1800 indicator

CONNECTION

Reference

This is a class of managed objects responsible for the transparent transfer of information between CONNECTION TERMINATION POINTs. A Connection is a component of a Trail. Several connections can be bundled into a higher rate trail. A sequence of one or more Connections are linked to form a Trail. A Connection may be either uni- or bi-directional.

CONNECTION TERMINATION POINT

Reference

This is an actual or potential end point of a Network connection. For example, this can represent a logical channel or a timeslot on a physical link. All PHYSICAL PORTs connect to at least one type of CTP.

CONSEQUENCE PERFORMANCE NOTIFICATION

Reference

A communication that occurs as part of a PERFORMANCE CONSEQUENCE. A Notification is typically one-sided, in that no Response is expected. For example, an alert be raised as the result of a PERFORMANCE OBJECTIVE being violated.

CONSEQUENCE PERFORMANCE NOTIFICATION SPEC

Reference

The invariant characteristics that define a communication (notification) that occurs as part of a PERFORMANCE CONSEQUENCE. A Notification is typically one-sided, in that no Response is expected. For example, an alarm may be raised as the result of a PERFORMANCE OBJECTIVE being violated.

CONTACT CENTER DAY DERIVED

Derived

Specifies customer contact statistics. The customer contacts are analyzed.

CONTACT LIST

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.

CONTACT LIST CHANGE REASON

Lookup

Lookup for possible reasons for changing the CONTACT LIST.

CONTACT LIST COST

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).

CONTACT LIST RECURRENCE TYPE

Lookup

A categorization of the recurrence of a CONTACT LIST. For example:

  • W = Once a Week

  • M = Once a Month

  • Y = Once a Year

  • MI = Once a Month with Invoice.

CONTACT MEDIUM

Lookup

Medium used to get into Contact with customer or third party in a business interaction. Typically phone, letter, fax, visit, or chat.

CONTACT ROLES

Lookup

Describes the various roles a contact individual may play in the relationship with the operator.

CONTENT

Reference

Keeps all downloadable content provided to the customer through the operator's network. For example:

  • Weather reports

  • Constellation

  • Jokes

CONTENT DELIVERY EVENT

Base

EVENT in which content was downloaded.

CONTENT PRICE

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 OFFERING PRICE.

CONTENT PRICING TYPE

Lookup

Lookup for types of content pricing. For example:

  • Charge per download

  • Monthly fixed rate

CONTENT PROVIDER

Reference

Provider for content that would be consumed by end user. The contents could be video, audio clips, or text content.

CONTENT TYPE

Lookup

Lookup for content types. For example:

  • Constellation

  • Jokes

  • Weather report

CORE INTERFACE

Reference

Defines a DEVICE INTERFACE role that functions as a Core Interface, that is, an interface in the core of the network. The objective of this role is to enable the definition of POLICYs such that all Core Interfaces in a particular Domain can receive the same common configuration commands.

COST

Base

Costs that have been incurred from operations and events at trackable levels. For example:

  • Gift offer expense

  • Employee salary

  • Commission

  • Promotion delivery cost

  • Carrier billing charge (for roaming/LAC/and so on)

COST CENTER

Reference

Cost Center of a COURIER or provider to which costs can be charged.

COST CENTER DERIVED

Derived

Statistics of all expenses by each business unit inside the carrier. It can be used for auditing and budgeting.

COST CENTER BUDGET

Base

The budget of each COST CENTER at a specific financial period.

COST CENTER MONTH AGGR

Aggregate

Summary at month level of COST associated with COST CENTER and ORGANIZATION BUSINESS UNITs.

COST REASON

Lookup

Lookup of all possible reasons why the cost occurred. For example:

  • Natural disaster

  • Operator error

COST SUBTYPE

Lookup

Lookup to further classify COST TYPEs. For example:

  • Acquisition cost

  • Retention cost

  • Salary

  • Damaged

  • New machine

  • Repair fee

COST TYPE

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).

COUNT DAY DRVD

Derived

Critical Aggregation Summary at day level of various measures (counts) at customer, account, agreement, Main Product Subscription, and Product Subscription level as a function of Customer Type, County, Organization Business Unit, Product Offer level and Product Specification Level (full Hierarchies). It collects summable measures (like number of new customers, new subscriptions, churners, and so on) over the day as well as non-summable measures, like number of active accounts (end of day), suspended subscriptions, and so on.

The measures are supposed to be all at the end of the day considered.

COUNT MONTH AGGR

Aggregate

Similar to COUNT DAY DRVD but at month level. The measures are supposed to be all at the end of the month considered (or the last past full day of data available of the current month).

COUPON SCAN

Lookup

Specifies the barcode on a store or manufacturer coupon. The coupon scan code comprises two parts:

  • The first is a fixed 12 character code that contains the manufacturer identification, family code, and coupon value.

  • The second is based on Code 128 and comprises up to 20 characters which specify the manufacturers number system character, the offer code, and end of offer code. The supplementary Code 128 was introduced as a guideline in 1997.

    These codes are included: Primary Label, Secondary Label, Coupon ID.

COUPON TYPE

Lookup

Lookup for type of coupon used.

COURIER

Reference

The party who provides the Courier service for the Telecom Operator.

COURIER COST

Base

Subtype of COST which applies to a COURIER for delivering products or invoices to the customer.

CPE LOGICAL DEVICE ROLE

Reference

Defines required logical features to implement the specific role of a CPE (Customer Premise Edge) device, as used in a PRODUCT SPECIFICATION or SERVICE.

CREDIT CATEGORY

Reference

List of credit categories available that may be assigned to customers. For example:

  • Excellent

  • Good

  • High risk

CREDIT SCORE PROVIDER

Reference

Provides reference financial rating scores for each customers to the service provider. This information is also called the "Credit Rating Agency".

CROSSED THRESHOLD

Reference

Indicates the identifier of the threshold that caused the alarm. It has to be in relation with a RESOURCE ALARM.

CURRENCY

Lookup

Lookup for currencies that may be used in a transaction.

CURRENCY EXCHANGE RATE

Base

Exchange rate against the primary currency, as determined by exchange rate type and value date.

CURRENCY GEOGRAPHY ENTITY ASSIGNMENT

Reference

Assigns currency usage to a geographic area.

CUSTOM QUEUING SERVICE

Reference

Custom Queueing enables the designer to specify a particular number of bytes, packets, or flows to forward from a specific Queue each time the Queue is serviced.

CUSTOMER

Reference

Information pertaining to customers.

CUSTOMER ACCOUNT

Reference

Account associated to a CUSTOMER from a pure Retail shop perspective. It has otherwise the same behavior as ACCOUNT, but is specific to the retail view, to allow the possibility for the same customer to have two accounts: one for Retail, one for standard Telecommunications Provider (Billing and CRM) just in case they are separate and might not be easily conciliable upfront.

CUSTOMER ACQUISITION SUMMARY MONTH AGGR

Aggregate

Monthly summary of newly acquired customers by PRODUCT SPECIFICATION.

CUSTOMER ADDRESS

Reference

Address associated with a customer as given to the Retail Unit in contact with customer.

CUSTOMER AFFILIATION

Reference

Associates a CUSTOMER with a CUSTOMER GROUP.

CUSTOMER CHURN MONTH AGGR

Aggregate

Summary of churners per month by reason.

CUSTOMER CLASS

Lookup

Lookup for Customer Classification codes. For example:

  • HLCU-High Local Call Usage Customers

  • HNCU-High National Call Usage Customers

  • HINCU-High InterNational Call Usage Customers

CUSTOMER CLASS ASSIGNMENT

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.

CUSTOMER CLUSTER

Reference

Identifies the cluster that the CUSTOMER falls into, based on buying behavior.

CUSTOMER CLUSTER TYPE

Lookup

Define types of CUSTOMER CLUSTER.

CUSTOMER COMMENT

Data Mining

Specifies storing concatenated customer comments in last 1 year, customer comments' score, and so on.

CUSTOMER COMMUNITY

Reference

The Customer Communities identified by mining algorithm.

CUSTOMER COST

Base

Subtype of COST which applies to a customer. For example, the cost of a gift that is sent to a customer.

CUSTOMER COST DRVD

Derived

Statistics of various costs incurred to the customer. This information is important from the analysis point of view. For example, subscriber acquisition cost, subscriber retention cost, and so on.

CUSTOMER COST MONTH AGGR

Aggregate

Statistics of various costs incurred to the customer. These details are important for analysis such as:

  • Subscriber retention cost

  • Subscriber acquisition cost

CUSTOMER DEBT COLLECTION MONTH AGGR

Aggregate

Summary of customer in debt per month (status at the end of the month or latest past full day of the current month).

CUSTOMER DECISION TREE NODE

Reference

Mining target entity to store Decision Tree mining model details.

CUSTOMER DNA DRVD

Derived

The D.N.A of the customer at month level collects any information available about the customer (socio-demographic data, products, purchase, payment and recharge behavior, call behavior, interactions with call center and support, issues, complains, and so on, for mining purposes.

CUSTOMER DOCUMENT

Reference

Various types of customer proof documents provided for a CUSTOMER ORDER, AGREEMENT, and so on.

CUSTOMER EQUIPMENT INSTALLATION DAY DRVD

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

CUSTOMER EQUIPMENT INSTALLATION MO AGGR

Aggregate

Monthly summary of customer equipment installation activities. These statistics typically include: modems, routers, or DSL boxes for internet and Television equipment.

CUSTOMER FACING SERVICE

Reference

This is the base entity for defining CUSTOMER FACING SERVICEs. A CUSTOMER FACING SERVICE is an abstraction that defines the characteristics and behavior of a particular SERVICE as seen by the Customer or other appropriate PARTY ROLE. Thus, this PARTY ROLE purchases, leases, uses, and is otherwise directly aware of this type of SERVICE. This is in direct contrast to RESOURCE FACING SERVICEs which support CUSTOMER FACING SERVICEs but are not seen or purchased directly by the Customer. For example, a VPN is an example of a CUSTOMER FACING SERVICE, while the sub-services that perform different types of routing between network devices making up the VPN are examples of RESOURCE FACING SERVICEs.

CUSTOMER FACING SERVICE ROLE

Reference

Defines a SERVICE in terms of a set of SERVICE ROLEs for a CUSTOMER FACING SERVICE. This entity defines SERVICE ROLEs that represent the variable characteristics of a CUSTOMER FACING SERVICE in terms of the roles that this SERVICE plays. This entity enables the CUSTOMER FACING SERVICE to be managed abstractly using SERVICE ROLEs. The Customer Facing Service Role also helps define the SERVICE in terms of the functions that it has or provides.

CUSTOMER FACING SERVICE SPECIFICATION

Reference

Specifies the invariant characteristics and behavior of a particular CUSTOMER FACING SERVICE as seen by the CUSTOMER.

CUSTOMER FACING SERVICE SPECIFICATION ATOMIC

Reference

This entity defines CUSTOMER FACING SERVICE SPECIFICATIONs that do not have any subordinate CUSTOMER FACING SERVICE SPECIFICATIONs. In other words, a Customer Facing Service Spec Atomic is a standalone CUSTOMER FACING SERVICE SPECIFICATION, and does not require any supporting CUSTOMER FACING SERVICE SPECIFICATIONs to define the invariant characteristics (that is, non-changing attributes, methods, relationships, and constraints) of any CUSTOMER FACING SERVICEs that it serves as a template for.

CUSTOMER FACING SERVICE SPECIFICATION COMPOSITE

Reference

This entity defines an integrated set of CUSTOMER FACING SERVICEs that collectively meets the needs of a SERVICE requested by a Customer. For example, the Customer may have requested GoldService, which is a SERVICE PACKAGE that defines a set of SERVICE BUNDLEs, each of which has its own QoS. Each individual CUSTOMER FACING SERVICE that is part of the SERVICE PACKAGE can be derived from a CUSTOMER FACING SERVICE SPECIFICATION. In this case, a Customer Facing Service Spec Composite will aggregate all of the individual CUSTOMER FACING SERVICE SPECIFICATIONs into a single named object. This object is a standalone object. However, it consists of other Customer Facing Service Spec Composite and/or the CUSTOMER FACING SERVICE SPECIFICATION ATOMIC entities. That is the primary difference between this entity and the Customer Facing Service Spec Atomic entity.

CUSTOMER FACING SERVICE SPECIFICATION ROLE

Reference

Defines a Service Specification, in terms of a set of Service Specification Roles, for a CUSTOMER FACING SERVICE. This is the base entity for defining Service Specification Roles that are used to represent the invariant characteristics of a CUSTOMER FACING SERVICE. This entity enables the CUSTOMER FACING SERVICE to be managed abstractly using Service Specification Roles. The Customer Facing Service Spec Role also helps define the Service Specification in terms of the functions that it has or provides.

CUSTOMER FACING SERVICE SPECIFICATION VERSION

Reference

Keeps the historical versions of CUSTOMER FACING SERVICE SPECIFICATION.

CUSTOMER FIELD SERVICE ACTIVITY

Base

On site installation for the customer with particular equipment instance.

CUSTOMER FIELD SERVICE DETAIL

Base

Details regarding customer service.

CUSTOMER GROSS ORDER QUARTERLY

Aggregate

This entity gives order measures (number of orders and total order amount) in same quarters of consecutive years. For example:

  • Order measures of Jan 2012 and Jan 2013

  • Order measures of Dec 2011 and Dec 2012

Provides information on order measures varying year over year.

CUSTOMER GROUP

Lookup

The lookup code for grouping the customers based on criteria defined by the service operator.

CUSTOMER GROUP ASSIGNMENT

Reference

A grouping of the customers based on criteria defined by the service operator.

CUSTOMER GROUP ITEM

Reference

The list of criteria used to group the CUSTOMERs under a specific CUSTOMER GROUP.

CUSTOMER INDIVIDUAL

Reference

Subtype of CUSTOMER (and PARTY), which contains details of individuals as opposed to organizations.

CUSTOMER OCCASION

Reference

Event celebrated or observed by a customer. For example:

  • Birthday

  • Anniversary

  • Company establishment day

CUSTOMER OCCASION TYPE

Lookup

Lookup for occasion type. For example: Wedding Anniversary, Birthday, Company founding anniversary, and so on.

CUSTOMER ORDER

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.

CUSTOMER ORDER DAY DERIVED

Derived

Daily summary of CUSTOMER ORDERs and their status (end of the corresponding day).

CUSTOMER ORDER DOCUMENT

Reference

The document provided while submitted CUSTOMER ORDER.

CUSTOMER ORDER LINE ITEM

Base

Details regarding items in the CUSTOMER ORDER.

CUSTOMER ORDER LINE ITEM DAY DERIVED

Derived

Summary of the details of CUSTOMER ORDER LINE ITEM status, per day. It allows identifying typical or recurrent issues in specific order types on specific items.

CUSTOMER ORDER LINE ITEM STATE ASSIGN

Base

Current state of an order line item.

CUSTOMER ORDER MONTH AGGR

Aggregate

Summarizes orders placed by customers at month level of aggregation. Using this entity, order measures (number of orders and total order amount) across order status, order type, product, product type dimensions can be computed

CUSTOMER ORDER PAYMENT

Base

Payments applied to a CUSTOMER ORDER.

CUSTOMER ORDER PRIORITY TYPE

Lookup

Lookup for possible priorities which can be assigned to a CUSTOMER ORDER.

CUSTOMER ORDER STATE ASSIGNMENT

Base

Current state of a CUSTOMER ORDER.

CUSTOMER ORDER STATE CHANGE REASON

Lookup

All type of reason for customer order state and customer order line item state changes.

CUSTOMER ORGANIZATION

Reference

Subtype of CUSTOMER (and PARTY), which contains details of organizations as opposed to individuals. An organization can also consist of one individual only (for example: independent).

CUSTOMER PRODUCT AFFILIATION

Derived

Mining target entity to store prediction results of target promotion mining model.

CUSTOMER PREFERENCE

Reference

Merchandise preferences of a Key Customer, for classes of items or other general categories.

CUSTOMER RELATIONSHIP

Reference

Association between CUSTOMERs. Information regarding the CUSTOMER or PROSPECT that is restricted to comply with privacy and other laws. This table is encrypted. For example: associating the Husband-Wife relationship.

CUSTOMER RELATIONSHIP TYPE

Lookup

Lookup for types of relationships that may exist between CUSTOMERs. For example:

  • Married

  • Employee-employer

  • Parent-child

CUSTOMER RESTRICTED INFO

Reference

Detail information about a customer that may be deemed private.

CUSTOMER REVENUE BAND

Lookup

Entity contains a customer classification in revenue terms. For example: Customer with charges between $100 to $200.

CUSTOMER REVENUE BAND ASSIGNMENT

Reference

Assigns a revenue band to a customer.

CUSTOMER REVENUE TYPE

Lookup

Lookup for types of revenue a customer may bring to the operator. For example:

  • Recharging

  • Rent fee

  • One time equipment purchase

CUSTOMER RFMP SCORE

Derived

Recency, Frequency, Monetary, and Profitability Value Score of a CUSTOMER, by ORGANIZATION BUSINESS UNIT.

CUSTOMER SCORE

Reference

Scores or Score ranges that may be assigned to a customer based on credit, behavior, or other criteria. For example:

  • 1, 2, 3, 4, 5

  • 1-10, 11-20

CUSTOMER SEGMENT

Reference

Market or customer segments to which customer may be assigned.

CUSTOMER SEGMENT DETAIL

Reference

Specifies details for storing each customer segment derived from segmentation mining model.

CUSTOMER SEGMENTATION MODEL

Reference

The segmentation model used to profile the customers. For example:

  • KMeans by Revenue from Market Department

  • O-Clustering by IT department

CUSTOMER SENTIMENT MANUAL SCORE

Derived

Specifies predefined dictionary to manually score customers' comments.

CUSTOMER SIC ASSIGNMENT

Reference

Assigns SIC/NASIC code to customers.

CUSTOMER SKU SALES RETURN DAY DRVD

Derived

SKU ITEM purchases and returns by CUSTOMER for an ORGANIZATION BUSINESS UNIT.

CUSTOMER SOURCE

Reference

Initial source or contact with customer. For example:

  • Sales campaign

  • Advertisement

  • Call center

  • Dealer

CUSTOMER STATUS REASON

Lookup

List of the possible REASONs for setting a customer in a given status.

CUSTOMER TYPE

Lookup

Lookup for type of customer. For example: Individual or Corporate.


Table 2-39 D to F Entity Descriptions

Entity Name Type Description

DATA SERVICE EVENT

Base

Data Service Events. For example

  • Fixed Line modem dial

  • Broadband access

  • GPRS service

DATA USAGE DAY DRVD

Derived

Daily aggregate of data usage.

DATA USAGE MONTH AGGR

Aggregate

Monthly aggregate of data usage.

DAY

Reference

Defines day, the lowest level of all calendars.

DAY ACTUAL CONDITION

Reference

Weather, external and internal conditions that may have impacted performance on a given day at a given location.

DAY TODATE TRANSFORMATION

Reference

Documents how todate transformation can be implemented at day level.

DAY TRANSFORMATION

Reference

Transformation for 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.

DEAL

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.

DEAL LINE ITEM

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.

DEALER

Reference

The PARTY who resells products from the operator.

DEALER DISCOUNT GROUP ASSIGNMENT

Reference

Assigns DEALER to a discount group(s).

DEBT AGING BAND

Lookup

Ranges of time used to group debt based on the age of the debt. For example:

  • 0-90 days

  • 91-180 days

DEFICIT ROUND ROBIN SCHEDULING SERVICE

Reference

Provide weighted fair distribution of bandwidth for multiple Queues that contain variable-length packets.

DEMOGRAPHIC CHARACTERISTIC

Reference

A feature or quality used to make recognizable or to define somebody or something, such as age, income, education, revenue, and so forth.

DEMOGRAPHIC CHARACTERISTIC VALUE

Reference

A single value or range of values that defines a DEMOGRAPHIC CHARACTERISTIC.

DEMOGRAPHY ATTRIBUTE

Reference

User defined demographic attributes that can be assigned values.

DEMOGRAPHY GROUP

Reference

The domain of classifications used to group profile information about a PARTY. For example:

  • CH - Credit History

  • ED- Education

  • EM - Employment

  • EQ- Equipment

  • HB - Hobbies

  • HH - Household

  • OR - Organization

And other relevant demographics and psychographics.

DERIVED VALUE

Reference

Derived value of the customer based on predetermined criteria.

DESTINATION TYPE

Lookup

Lookup for the types of destination associated with CALL SOURCE DESTINATION. For example:

  • National Fixed

  • National Mobile

  • International Fixed

  • International Mobile

DEVICE INTERFACE

Reference

This is a concrete entity that represents the (logical) interface or sub-interface of a device. This entity is not a transmission entity; rather, DEVICE INTERFACEs are used to program SERVICEs and LOGICAL RESOURCEs on a Device. For example, use a Device Interface to program a logical connection from a device to a network medium. Different types of Device Interfaces exist for the different types of network media. For example IP compared with ATM, that are used in a network to enable such media to be programmed. The combination of a LOGICAL DEVICE and a Device Interface is what a developer programs to define SERVICEs that run on the device.

DEVICE INTERFACE DETAIL

Reference

In general, there are multiple ways to manage a DEVICE INTERFACE. The first distinction lies in what is being managed. the model defines two types of management commands categories: configuration and operational. Configuration commands are used to configure the DEVICE INTERFACE (and also the LOGICAL DEVICE for commands that affect multiple specific DEVICE INTERFACEs). Operational commands are used to monitor and troubleshoot the software, network connectivity, and the Device itself.

DEVICE INTERFACE PHYSICAL PORT ASSIGNMENT

Lookup

Defines which PHYSICAL PORT can support which DEVICE INTERFACE.

DEVICE INTERFACE ROLE

Reference

Represents different types of roles that can be associated with a particular DEVICE INTERFACE.

DEVICE INTERFACE TP ASSIGNMENT

Reference

Defines the relationship between DEVICE INTERFACE and TERMINATION POINT.

DIFFSERV SERVICE

Reference

Semantics that define how traffic is forwarded based on the value of the DSCP (DiffServ Code Point) of a packet.

DIRECT DEBIT STATUS REASON

Lookup

Lookup for the various reasons the current status is direct debit payment. For example:

  • Customer preferred choice: when the customer does not want to use a credit card.

  • Customer imposed: which means the CSP imposes this status after problems with credit card or cash payments.

DISCOUNT GROUP

Reference

Discount groups that employees or partners may be a part of.

DISCOUNT LINE ITEM

Base

Line Item associated with discounts in a retail transaction.

DISCOUNT SBRP PRICE ALTERATION

Reference

A discount, a reduction of price, for a PRODUCT SUBSCRIPTION.

DISPOSITION TYPE

Lookup

Denotes what disposition a returned item was in. For example:

  • Return to vendor

  • Return to stock

  • Write off

DISTANCE BAND

Lookup

Distance ranges to characterize UDR EVENTs by geographical distance.

DIVERT RETRIEVE REASON

Lookup

Lookup for all reasons for diverting a call or retrieving a call from a Mailbox. For example:

  • Line busy (divert)

  • Line off (divert)

  • No answer (divert)

  • Customer originated (divert / retrieve)

  • Mailbox originated (retrieve only)

DIVERT RETRIEVE TYPE

Lookup

Lookup for types for diverting a call or retrieving a call. For example:

  • Divert

  • Retrieve

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.

DOCUMENT CONDITION TYPE

Lookup

Lookup for possible document condition types. For example:

  • Complete

  • Incomplete

  • Unavailable

DOCUMENT TYPE

Lookup

Lookup for document types. For example:

  • Driver license photocopy

  • Address certification

  • Bank card photocopy

DOCUMENT TYPE GROUP

Lookup

The group of DOCUMENT TYPEs of which customer may provide to service provider for identification. For example:

  • Mandatory Document

  • Legal Requirement

  • Income Proof Document

DOCUMENT TYPE GROUP ASSIGNMENT

Reference

Assigns different DOCUMENT TYPEs into different DOCUMENT TYPE GROUPs.

DOMAIN

Reference

Domain from a web portal point of view.

DOMAIN TYPE

Lookup

Type of DOMAIN (web related).

DROPPER SERVICE

Reference

Specifies the dropper service. Droppers are distinguished by the algorithm that they use to drop traffic.

DSL MODEM

Reference

The xDSL modem to implement Broadband on copper wire (router). The DSLAM (Digital Subscriber Line Access Multiplexer) aggregates multiple xDSL users into the core IP network.

EDGE INTERFACE

Reference

Defines a DEVICE INTERFACE role that functions as an Edge Interface; that is, an interface on the edge of the network. The objective of this role is to enable the definition of POLICYs such that all Edge Interfaces in a particular Domain can receive the same common configuration commands.

EDUCATION

Lookup

Demographic education levels that may be assigned to customers.

EF SERVICE

Reference

Specifies the policy to forward network traffic by adding specific semantics that characterize the operation of the Expedited Forwarding (EF) Service (RFC3246 and RFC3247).

EMAIL ADDRESS

Reference

List of email addresses as a generalization of ADDRESS LOCATION. Typically used for Retail shops.

EMAIL SERVICE

Reference

Specifies all the Email mail boxes allocated to CUSTOMER.

EMPLOYEE

Reference

Subtype of individual indicating an employee of the provider.

EMPLOYEE ACTUAL LABOR HOURLY

Base

Worked shifts by hourly employees.

EMPLOYEE ACTUAL LABOR SALARIED

Base

Worked shifts by salaried employees.

EMPLOYEE COST

Base

Subtype of COST, which applies to employee. For example, salary and bonus for employee.

EMPLOYEE DESIGNATION

Lookup

The various designations present in an organization for the employees. For example:

  • Call Center Agent

  • Manager Customer Care

  • Consultant

  • Principal Consultant

EMPLOYEE DISCOUNT GROUP ASSIGNMENT

Reference

Assigns EMPLOYEE to DISCOUNT GROUP(s).

EMPLOYEE EXPENSE REPORT

Base

The expense reports submitted by employees, including contractors, to claim their business expenses. The EMPLOYEE (Party) and PAYMENT CHANNEL (channel) are captured by its super entity EVENT. The expense submit date is the event begin date.

EMPLOYEE EXPENSE REPORT ITEM

Base

The detail line item of each EMPLOYEE EXPENSE REPORT.

EMPLOYEE EXPENSE REPORT STATE

Base

The different state of a given EMPLOYEE EXPENSE REPORT. For example:

  • Submitted

  • Pending Approval

  • Approved

  • Paid

EMPLOYEE JOB ROLE ASSIGNMENT

Reference

Assigns EMPLOYEE to JOB ROLE(s).

EMPLOYEE JOB ROLE TYPE

Lookup

Relevance of job role assignment to employee. For example: Primary, Secondary, and so on.

EMPLOYEE LANGUAGE CAPABILITY

Reference

Specifies the languages the employee can use to serve customers, especially for call center agents and sales representatives.

EMPLOYEE RESTRICTED INFO

Reference

Detail information about the EMPLOYEE that may be deemed private.

EMPLOYEE SCHEDULE

Reference

Planned staffing schedule of location, role, shift, and employees.

EMPLOYEE TRAINING RECORD

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.

EMPLOYEE TYPE

Lookup

Lookup of employee type. For example:

  • Part-Time

  • Contractual

  • Full-Time

ENROLL CHANNEL

Lookup

Channel through which a customer gets enrolled into a LOYALTY PROGRAM.

ENROLL TYPE

Lookup

Type of ENROLL CHANNEL.

ENTITY

Reference

This entity represents entities that cannot be directly managed. For example, a hub.

ENTITY ROLE

Reference

This is an abstract base entity that defines the concept of various types of roles for entities that describe the function of the entities.

ENTITY SPECIFICATION

Reference

This is an abstract base entity that defines the invariant characteristics, attributes, methods, constraints, and relationships, of another entity.

ENTRY METHOD

Lookup

Lookup for method used of entering transaction data. For example:

  • Entry Through Key

  • Entry Through Magnetic Ink Character Recognition

  • Entry Through MSR

  • Entry Through Scanning

  • Entry Through Smart Card

ENVIRONMENT TYPE

Lookup

Defines the temperature, relative humidity, lighting, and other physical or climatic environmental requirements for storing and displaying the item.

EQUIPMENT

Reference

The devices, delivered by COURIER or collected at the DEALER shop, that a CUSTOMER can use to access services. The device might be Cell Phone, Fixed Line Phone, Fax Machine, and so on. The devices might be lent or sold to the customer. The equipment entity is a subtype of PRODUCT SPECIFICATION.

EQUIPMENT CENTER

Reference

Facility housing devices.

EQUIPMENT CENTER COST

Base

Subtype of COST, which collects all costs that are specifically related to a given EQUIPMENT CENTER (facility rent, taxes, and so on).

EQUIPMENT FUNCTIONALITY

Reference

The function of the EQUIPMENT. For example:

  • Make wireless calls

  • Send SMS

  • Send MMS

EQUIPMENT FUNCTIONALITY ASSIGNMENT

Reference

Assigns functionality to EQUIPMENT.

EQUIPMENT HOLDER

Reference

Represents physical objects that are both manageable and able to host, hold, or contain other physical objects. Examples of physical objects that can be represented by instances of this object class are RACKs, CHASSISs, Shelves, and SLOTs. The difference between subclasses of Equipment Holder, such as a SLOT or a CHASSIS, and subclasses of EQUIPMENT that have a Holder role, such as a CARD, is that the subclasses of Equipment Holder are dedicated to holding other Hardware. The subclasses of EQUIPMENT that have a holder role have a holding capability as a secondary capability, usually for expansion. Their primary function, however, is not to hold other objects.

EQUIPMENT INSTANCE

Reference

Implement communications. For example:

  • Handset (with IMEI)

  • Land line phone (with serial number)

  • Set-top box

  • Cable modem

EQUIPMENT INSTANCE STATUS TYPE

Lookup

Lookup for type of specific equipment instance status type. For example:

  • Purchased from vendor

  • In inventory

  • In customer

  • Broken

  • Reserved

EQUIPMENT RENTING AGREEMENT

Reference

Sub-type of AGREEMENT in which customer leases some equipment. Those equipment that still belong to the service provider. When the AGREEMENT terminates, the device should be returned to service provider.

ERRORED MEDIATED CALL EVENT

Base

The errored/recycled mediated event record from billing engine.

ERRORED RATED WIRELESS CALL EVENT

Base

The errored/recycled rated event record from billing engine.

ERRORED RAW WIRELESS CALL EVENT

Base

The errored/recycled/rejected raw event record from the mediation process.

ETHERNET INTERFACE

Reference

Lists of the various Ethernet Device Interfaces.

EVENT

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.

EVENT ACCESS METHOD ACTIVITY

Base

Occurrence of Access Method Usage.

EVENT ACCOUNT

Base

Events occurring on an account. For example:

  • Account create

  • Account suspension/resume

  • Line (account) termination attempted (convinced back by representatives)

  • Line termination

EVENT AGREEMENT

Base

Events related to agreement creation, cancellation, churn, or change, usually triggered after a business interaction.

EVENT ASSIGNMENT

Base

Describes relationship between unique events.

EVENT ASSIGNMENT REASON

Lookup

Lookup for all possible reasons why a relationship exists between two EVENTs. For example:

  • Premise

  • Result in

EVENT ASSIGNMENT TYPE

Lookup

Lookup for all types of relationships between two EVENTs.

EVENT CATEGORY

Lookup

Lookup for EVENT CATEGORY which is further grouped into EVENT TYPE. For example:

  • Loyalty Program Event

  • Access Method Event

EVENT CIRCUIT RENTAL

Base

Subtype of "Non UDR 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:

  • Initial Installation

  • Maintenance Check

  • Termination

EVENT CLASS

Lookup

Lookup for the classification for the types of EVENTs that can occur. For example:

  • IN: involves only Communications Service Provider

  • OUT: involves customer

EVENT COMPOSITE PRODUCT SPECIFICATION

Base

Events associated with an offer or COMPOSITE PRODUCT SPECIFICATION. Subtype of EVENT.

EVENT COST

Base

Subtype of COST, which is specifically related to a given EVENT. This cost is usually for a non-UDR event such as an interaction with a customer. For example, for on-site maintenance after a service issue or a break-down.

EVENT EMIT DETAIL

Reference

The expressions that determine what, if any, constraints are to be applied to this Policy Event Set. This entity also defines additional semantics to help identify the type of this event.

EVENT EMPLOYEE ACTIVITY

Base

Specifies the EMPLOYEE activities (sales, installation, and so on). Subtype of EVENT.

EVENT EMPLOYEE PAYROLL

Base

Event in which payroll payment was made to an employee (excludes sales commission). Subtype of EVENT.

EVENT EQUIPMENT INSTANCE

Base

Events per instance of EQUIPMENT. Subtype of EVENT.

EVENT FINANCIAL

Base

Financial event involving an account or billing statement. Subtype of EVENT.

EVENT GEOGRAPHY

Base

Events affecting a Geographic Area that may have an impact on a provider's business. Subtype of EVENT. For example:

  • Earthquake

  • Power Outage

  • Labor Strike

EVENT LOCATION

Reference

Assigns an address location to the EVENT.

EVENT LOYALTY PROGRAM

Base

Events associated with each event or transaction on a customer loyalty program. For example:

  • Loyalty points earned by the customer

  • Bonus points awarded to the customer

  • Points redeemed by the customer

EVENT PARTY ASSIGNMENT

Base

Many to many relationship assigning a party or multiple parties to event(s).

EVENT PARTY INTERACTION

Base

Interactions or communications with the customer. For example:

  • Faults

  • Inbound and outbound telemarketing

  • Direct mail

  • SMS

  • Email

  • Service calls

  • Complaints

  • Debt collection

EVENT PARTY INTERACTION CHARACTERISTIC VALUE

Reference

A value of a given Party Interaction Characteristic, associated with a full thread of interaction. The first interaction of the thread is the so-called "party interaction code".

EVENT PARTY INTERACTION CHAT DETAIL

Base

Subtype of EVENT PARTY INTERACTION which represents the chat history details between the service representative and the CUSTOMER. Each chat message is saved as one record.

EVENT PARTY INTERACTION ITEM

Base

When multiple threads are discussed in a single EVENT PARTY INTERACTION, this line item lists the involved threads and other information including accounts, subscriptions, and so on.

EVENT PARTY INTERACTION PARTICIPATION

Base

Tracks multiple employees who participate in a same interaction with a customer

EVENT PARTY PROFILE

Base

Event in which party profile information was modified or updated.

EVENT PARTY ROLE

Lookup

Role played by a PARTY in an EVENT. For example:

  • Customer who reported the event

  • Customer affected by event

  • Party who caused the event

EVENT PREPAID MOBILE

Base

Actions involving PREPAID MOBILE EVENT TYPE account. Subtype of EVENT ACCOUNT. For example:

  • Initial activation

  • Recharges

  • Adjustments

  • Deactivation

EVENT PRODUCT SUBSCRIPTION WIRELESS

Base

Events associated with a subscription. Subtype of EVENT. For example:

  • Subscription activation

  • Reimbursement on prepaid account

  • Termination

  • Suspension because of insufficient deposit

EVENT REASON

Lookup

Lookup for event reasons. For example: arrearage.

EVENT REASON CATEGORY

Lookup

Lookup for event reason categories. Categories are further grouped into event reasons.

EVENT RESOLUTION

Reference

The domain of results that may occur in the resolution of an EVENT.

EVENT RESPONSE REASON

Lookup

Lookup for possible response reasons that may be used in an EVENT.

EVENT RESULT

Lookup

Lookup for the description of a result or any events. For example:

  • Successfully processed

  • Escalated

  • Refused by CSP

  • Refused by customer

  • Failed – Impossible

  • Failed – process error

EVENT SIM CARD

Base

Events associated with a SIM CARD. Subtype of EVENT.

EVENT STATUS

Base

Lookup for event status. For example:

  • Completed

  • Pending

  • In-Progress

  • Suspended

  • Cancelled

  • Abandoned

EVENT STATUS REASON

Lookup

Lookup for event status reasons. For example:

  • Insufficient funds

  • Stolen card

EVENT STATUS TYPE

Lookup

Lookup for EVENT STATUS. For example:

  • Complete

  • Pending

  • In-Progress

  • Suspended

  • Cancelled

  • Abandoned

EVENT SUBSCRIPTION CHANGE

Base

Events involving temporal provisioning and relinquishment of products and services to current subscription base.

EVENT TRIGGER DETAIL

Reference

Tracks the execution, evaluation of POLICY RULE on each POLICY EVENT.

EVENT TYPE

Lookup

Lookup for event type. For example:

  • In Loyalty Program Event

    1.1 Points Accumulation

    1.2 Redemption

  • Access Method Event

    2.1 Access Method Login (connect)

    2.2 Access Method Logout (disconnect)

    2.3 Access Method Suspension (because of late payment or other reason)

EXCHANGE LOCATION

Reference

Specifies service area served by the central office.

EXCLUDE PORT DETAIL

Reference

The attribute exclusionFunction is designed to be populated from an external management system, and represents the criteria for excluding one or more Ports. A predefined exclusion function is to limit the role that a Port plays to an edge role. However, this class enables additional functions to be used to exclude Ports.

EXPENSE REPORT PARTY ASSIGNMENT

Base

The involvement of different PARTYs in a given EMPLOYEE EXPENSE REPORT. For example:

  • The employee who claims the expense

  • The employee who approves the expense

  • The customer involved in the expense justification

EXPENSE REPORT STATE TYPE

Lookup

Lookup for the types of STATE which an EMPLOYEE EXPENSE REPORT may be in. For example:

  • Submitted

  • Pending approval

  • Approved

  • Paid

EXPENSE TYPE

Lookup

Lookup for type of expense being claimed. For example:

  • P = expense was pre-paid by the company

  • C = Cash advance

  • E = Actual expense incurred by requestor

EXPIRY BASIS TYPE

Lookup

Type of Basis or REASON for Expiry. It could be time-based (x months, or so) after first activation or after first or last call, or event based (something happened or a specific date like New Year passed so it expires).

EXTERNAL CREDIT PROFILE

Reference

A source of information that helps define the credit worthiness of the customer.

EXTERNAL CREDIT PROFILE ASSIGNMENT

Reference

Indicate which external agency or institute provided the credit profile for the given customer.

EXTERNAL INFORMATION SOURCE

Reference

Source from which the demographic information or customer information is obtained.

EXTERNAL OPERATOR

Reference

All operators the Service Provider does business with, including inland competitors or roaming partners.

EXTERNAL ORGANIZATION TYPE

Lookup

Lookup for types of external organizations.

FACTOR COMPANY

Reference

Stores the information about the factor company, which is the financial instrument holding the receivables.

FAIR QUEUING SERVICE

Reference

Ensure that each Queue receives a fair share of the set of applicable metrics, for example bandwidth, that are divided among the different Queue instances.

FAULT RESOLUTION TYPE

Lookup

Lookup for available types of network fault resolution.

FAULT TYPE

Lookup

Lookup for available types of faults.

FDA

Reference

The FDA is the Fibre Distribution Area. The FDA is an aggregated fiber broadband geographical area served. Each area served is one "Network Site".

FIELD ACTIVITY RESULT TYPE

Lookup

Lookup for available result types for customer field activities that are performed by support engineers. For example:

  • S - Successful

  • F - Failed

FIELD ACTIVITY TYPE

Lookup

Lookup for types of customer field activities that may be performed by support engineers. For example:

  • Installation

  • Troubleshooting

  • Upgrade

FIREWALL ROLE

Reference

Abstracts the different routing capabilities necessary for a LOGICAL DEVICE to have. This helps simplify the modeling of (especially) network devices, which have many different sets of capabilities. For example, most routers can do routing, forwarding, and firewalling of traffic. By modeling these capabilities as three roles, router functionality is both abstracted and categorized, so that the differences between firewalling done by a router and firewalling done by a dedicated firewall device can be differentiated.

FISCAL HALF MONTH

Reference

Defines half-month in a fiscal calendar.

FISCAL HALF YEAR

Reference

Defines half-year in a fiscal calendar.

FISCAL MONTH

Reference

Defines month in a fiscal calendar.

FISCAL QUARTER

Reference

Defines quarter in a fiscal calendar.

FISCAL WEEK

Reference

Defines week in a fiscal calendar.

FISCAL YEAR

Reference

Defines year in a fiscal calendar.

FIXED LINE CALL EVENT

Base

Event involving a call made on a Fixed Line telephone.

FIXED LINE PORT

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.

FIXED LINE RATING PLAN

Reference

Subtype of PRODUCT OFFERING PRICE associated only with Fixed Lines.

FIXED LINE SERVICE

Reference

Subtype of SERVICE for detail information on the fixed line service.

FLEXIBLE CHARACTERISTIC

Reference

An abstracted entity to provide common structure for all types of characteristics. All of the various types of characteristics may be applicable to the subject, including product, service, network element, and so on. This entity provides a flexible way to define additional attributes for those entities with complex features.

FLEXIBLE CHARACTERISTIC ASSIGNMENT

Reference

Assigns the characteristic to the subject.

FLEXIBLE CHARACTERISTIC ASSIGNMENT TYPE

Reference

Lookup of ASSIGNMENT TYPE. For example:

  • Depending on

  • Having feature of

  • Conflict with

FLEXIBLE CHARACTERISTIC RELATIONSHIP

Reference

Relationship between characteristics, for example, one characteristic may conflict with another.

FLEXIBLE CHARACTERISTIC TYPE

Lookup

Lookup of FLEXIBLE CHARACTERISTIC types.

FLEXIBLE CHARACTERISTIC VALUE

Reference

Possible values that a characteristic may take, including predefined choices or free numeric values.

FLEXIBLE CHARACTERISTIC VALUE ASSIGNMENT

Reference

Assigns the characteristic value to the applicable subject.

FLEXIBLE CHARACTERISTIC VALUE RELATIONSHIP

Reference

Relationship between two flexible characteristic values. For example, exclusiveness, same as, and so on.

FRAUD PROFILE CLASS

Lookup

Lookup for all possible classes of fraud profile that customers or dealers may commit.

FSAM

Reference

FSAM (Fibre Serving Area Module) is an aggregation of FDAs. The FSAM is a group of served areas by the operators of the service, mostly FTTH, or Optical Fiber Broadband.

FUEL SALE STATUS

Lookup

Lookup for status codes that may be applied to a fuel sale.


Table 2-40 G to J Entity Descriptions

Entity Name Type Description

GENDER

Lookup

Lookup for gender.

GEOGRAPHY BUILDING

Reference

Building level in GEOGRAPHY HIERARCHY.

GEOGRAPHY CITY

Reference

Cities defined in a GEOGRAPHY HIERARCHY.

GEOGRAPHY COMPLEX

Reference

Specifies the complex level in GEOGRAPHY HIERARCHY. The complex includes the complexes, a few building forming an enclosed area, in a city, at Universities, or industrial parks, and so on.

GEOGRAPHY COUNTRY

Reference

Countries defined in a GEOGRAPHY HIERARCHY.

GEOGRAPHY COUNTY

Reference

Counties defined in a GEOGRAPHY HIERARCHY.

GEOGRAPHY DEMOGRAPHIC GROUP

Reference

User-defined classification for DEMOGRAPHY ATTRIBUTEs.

GEOGRAPHY DEMOGRAPHY ATTRIBUTE

Reference

User defined attributes to describe demographic information for a given Geography.

GEOGRAPHY DEMOGRAPHY VALUE

Reference

User defined values corresponding to the DEMOGRAPHY ATTRIBUTEs.

GEOGRAPHY ENTITY

Reference

User defined geographic units.

GEOGRAPHY ENTITY ASSIGNMENT

Reference

Assignment of GEOGRAPHY ENTITYs to a user defined hierarchy level.

GEOGRAPHY ENTITY HIER LEVEL ASSIGNMENT

Reference

Assigns GEOGRAPHY ENTITYs to GEOGRAPHY HIERARCHY LEVELs.

GEOGRAPHY HIERARCHY

Reference

User defined geographic hierarchies.

GEOGRAPHY HIERARCHY LEVEL

Reference

User defined levels within a geographic hierarchy.

GEOGRAPHY HIERARCHY LEVEL ASSIGNMENT

Reference

Assignment of a GEOGRAPHY HIERARCHY level to a GEOGRAPHY ENTITY.

GEOGRAPHY LEVEL

Reference

User defined name and descriptions for GEOGRAPHY HIERARCHY LEVEL.

GEOGRAPHY LEVEL ATTRIBUTE

Reference

User defined attributes associated with a GEOGRAPHY LEVEL.

GEOGRAPHY LEVEL ATTRIBUTE VALUE

Reference

Values assigned to the GEOGRAPHY LEVEL ATTRIBUTEs.

GEOGRAPHY REGION

Reference

Defines a region in a GEOGRAPHY HIERARCHY.

GEOGRAPHY STATE

Reference

Defines a state in a GEOGRAPHY HIERARCHY.

GEOGRAPHY STREET

Reference

Defines a city in GEOGRAPHY HIERARCHY.

GEOGRAPHY SUB REGION

Reference

Defines a subregion in a GEOGRAPHY HIERARCHY.

GEOGRAPHY WORLD

Reference

Top level of GEOGRAPHY HIERARCHY.

GGSN

Reference

GGSN (Gateway GPRS Support Node) is the key component in GPRS and 3G system, which links the access network data into the IP-Network.

GIVE AWAY ITEM DAY DRVD

Derived

Statistics of all give away items to the customer for promotion or retention purposes.

GIVE AWAY TYPE

Lookup

Lookup for types of give-aways.

GL ACCOUNT

Reference

The GL accounts are defined to track financial status from a specific angle. All GL Journals are posted to various GL Accounts to reflect financial impact of each business transaction. Each account is defined by certain codes and flags, including whether the account is enabled, whether detail posting or detail budgeting is allowed, and others.

GL ACCOUNT ASSIGNMENT

Reference

Defines the relationship between two GL ACCOUNTs to form an Account Hierarchy. It stores lists of the detail accounts associated with each summary account.

GL ACCOUNT SEGMENT

Reference

Defines different types of GL ACCOUNT, including: Cash, Bank, Equipment, and so on.

GL ACCOUNT TYPE

Lookup

Lookup for types of GL ACCOUNTs. For example:

  • Asset

  • Liability

  • Equity

GL BALANCE

Base

Specifies actual, budget, and encumbrance balances for detail and summary accounts.

GL COST CENTER SEGMENT

Reference

Subtype of GL SEGMENT linking GL ACCOUNT to a specific COST CENTER.

GL JOURNAL ENTRY

Base

Specifies journal entries.

GL JOURNAL ENTRY BATCH

Base

Specifies journal entry batches.

GL JOURNAL ENTRY CATEGORY

Lookup

Lookup for journal entry categories. Specifies the category name and description. Each journal entry in the General Ledger is assigned a journal entry category to identify its purpose. For example:

  • Purchase Invoices

  • Receiving

GL JOURNAL ENTRY LINE

Base

Specifies the journal entry lines to track changes to each GL ACCOUNT made by a certain GL JOURNAL ENTRY. There is a one-to-many relationship between GL JOURNAL ENTRYs and journal entry lines.

GL JE LINE SUBLEDGER ASSIGNMENT

Base

Defines the relationship between GL JOURNAL ENTRY LINEs and GL SUBLEDGER JOURNAL ENTRY LINEs. Represents individual transactions from subledgers that have been summarized into General Ledger journal entry lines.

GL LEDGER

Reference

Defines information about the ledgers and the ledger sets defined in the Financial system. A GL Ledger is defined by 4C, chart of accounts (COA), functional currency, accounting calendar, and Accounting method.

GL LEDGER ACCOUNT ASSIGNMENT

Reference

Assigns the GL ACCOUNTs to GL LEDGERs to form the Chart Of Account (COA).

GL ORG BSNS UNIT SEGMENT

Reference

Assigns the GL ACCOUNT to corresponding ORGANIZATION BUSINESS UNIT.

GL PERIOD

Reference

Specifies information about the accounting periods defined with an Accounting Calendar.

GL PRODUCT SPECIFICATION SEGMENT

Reference

Assigns the GL ACCOUNT to corresponding PRODUCT SPECIFICATION.

GL PROJECT SEGMENT

Reference

Assigns the GL ACCOUNT to corresponding PROJECT.

GL REFERENCE

Reference

Groups or Categories referred from General Ledger to classify all revenue related activities.

GL SEGMENT

Reference

Each GL ACCOUNT contains a few independent segments, which are determined by the Financial System setup. For example, telecom operators may setup their GL Account in this format:

<Country, Cost Center, Account, SubAccount>

1 Y3G1 US 1001 2000
2 Y1C1 JP 1001 3000
3 Y2C1 CN 2001 4000

In this example, Country, Cost Center, and so on, are all different GL Segments. Account 1001 may stand for Cash, while 2001 stands for Bank, and 4000 stands for a specific bank account, and so on. Each of the GL ACCOUNTs may be linked (rolled up) to a specific business entity (Concept), such as organization business unit, project, and so on, through the subentities of GL Segment.

Note: Do not confuse Account in this description with ACCOUNT, which is customer account.

GL SEGMENT TYPE

Lookup

Lookup for type of GL SEGMENT. For example:

  • Project

  • Account

  • Project

GL SUBLEDGER

Reference

Specifies the subsidiary ledger, and represents original business transaction information that varies depending on the application.

GL SUBLEDGER JOURNAL ENTRY

Base

Represents subledger journal entries. The subledger Journal Ledger records the transaction at original level, that is each invoice, or each Purchase Order should have one entry in subledger journal entry.

GL SUBLEDGER JOURNAL ENTRY LINE

Base

Represents the subledger journal entry lines. There is a one-to-many relationship between subledger journal entry headers and subledger. The GL Subledger Journal Entry Line breaks down the GL SUBLEDGER JOURNAL ENTRY into different GL ACCOUNTs.

GPRS SERVICE

Reference

Subtype of PRODUCT SPECIFICATION, 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.

GPRS USAGE EVENT

Base

Specifies the GPRS Session Event. This describes most of the fields you find in the GPRS S-CDRs and G-CDRs as defined by ETSI.

HALF HOUR

Reference

Half-hours defined as part of time.

HALF MONTH TODATE TRANSFORMATION

Reference

Todate transformation information at the half-month level.

HALF MONTH TRANSFORMATION

Reference

Transformations with respect to half-month. For example:

  • This half-month last year

  • This year last half-month

HALF YEAR TODATE TRANSFORMATION

Reference

Cumulative time transformations at the half-year level.

HALF YEAR TRANSFORMATION

Reference

Transformations with respect to half-year. For example:

  • This half-year last year

  • This year last half-year

HANDSET INSTANCE

Reference

Instance of a handset.

HANDSET MODEL

Reference

Models of handsets.

HARDWARE

Reference

This entity represents any type of hardware entity that exists as an atomic unit that is not a PHYSICAL LINK or a PHYSICAL CONNECTOR. Hardware is defined as any component that has a distinct physical identity and can be a component of a PHYSICAL DEVICE. An object has a physical identity if it has a physical manifestation that enables it to be held and have a label attached to it. Thus, software, files, protocols, and policies are not physical objects.

HEAD TAIL DROPPER SERVICE

Reference

Specifies the behavior of either a head dropper or tail dropper (for example, a dropper which drops from the head or tail of its queue, respectively). Subtype of DROPPER SERVICE.

HOLDER ATOMIC

Reference

Represents atomic holders of EQUIPMENT that are individually manageable and do not form composite, or nested, Equipment Holders. Each Holder Atomic object can be a FRU.

HOLDER COMPOSITE

Reference

Represents Equipment Holders that are made up of other Equipment Holders (that is, instances of this entity and the Holder Atomic entity). This provides the semantics of collecting a set of components, each of which is individually manageable, and being able to manage the set of objects as a whole. This containment is modeled using the Has Holders aggregation.

HOME SUBSCRIBER SERVER

Reference

The server holding customer account information in Intelligent Network (IN), or Internet Multimedia System (IMS). For example:

  • Home Subscriber Server (HSS) from IMS

  • Service Control Point (SCP)

HOUR

Reference

Hours defined as part of time.

HOUSEHOLD

Reference

Captures household information for the household that the individual customer may belong to.

IDD

Reference

Subtype of PRODUCT SPECIFICATION that provides information about IDD service.

IDD CALL EVENT

Base

Event involving an International Direct Dial (IDD) call.

IMPRESSION

Base

Details collected when a user accesses a web page.

IMPRESSION EVENT TYPE

Lookup

Lookup for types of details collected when a user accesses a web page.

IN PLATFORM

Reference

IN (Intelligent Network) platforms operated by the telecom service provider. The Prepaid mobile or toll-free business normally relies on IN platform.

IN PLATFORM DAY DRVD

Derived

Daily summation of parameters related to the IN PLATFORM functioning and performance on a daily level.

IN PLATFORM MONTH AGGR

Aggregate

Monthly summation of parameters related to the IN PLATFORM functioning and performance on a monthly level.

IN ROUTING DEVICE

Reference

Specifies all the different types of devices, such as VLR, HLR, and SCP servers, which are utilized in a network to decide the call routing in IN Network or Wireless IN Network (IN is Intelligent Network).

INDIVIDUAL DEMOGRAPHY PROFILE

Reference

The demographic values for individual customer and customer household.

INDIVIDUAL DEMOGRAPHY VALUE

Reference

Values assigned to user-defined DEMOGRAPHY ATTRIBUTEs.

INDIVIDUAL NAME

Reference

Records all names used by the individual party along the history.

INITIATIVE RESULT TYPE

Lookup

Lookup for all possible results of initiatives. For example, the result is:

  • Becomes a customer

  • Does not become a customer

INITIATIVE TYPE

Lookup

Lookup for available initiative types.

INSTALLMENT AGREEMENT

Reference

The installment payment scheme for customer bills.

INTERACTION ANSWER CHOICE

Base

Defined answers, choices, corresponding to initiative questions.

INTERACTION CHANNEL

Reference

Channels used for Provider or Customer interactions. For example:

  • Call center

  • Online business system

  • Counter

INTERACTION DIRECTION

Lookup

Lookup for available directions for initiatives. For example:

  • Inbound

  • Outbound

INTERACTION NAVIGATION ASSIGNMENT

Reference

The navigation path between each two navigation items. For example, from Welcome Page to Log in page, or from Hot Offering to a specific PRODUCT OFFERING advertisement page, and so on. The navigation may change over the time, for example, a product may be on the Hot Offering page for only a short period.

INTERACTION NAVIGATION HISTORY

Base

The history of customer navigation path in each interaction call, or web visit. For example, in an IVR call, a customer may go through the following steps:

  1. Welcome

  2. Broadband

  3. Account balance query

These actions are realized as three records in the history.

INTERACTION NAVIGATION ITEM

Reference

Specifies all the possible places where customer may go to in the IVR or Web service context.

INTERACTION NAVIGATION ITEM TYPE

Lookup

Lookup for the type of Interaction Navigation. For example:

  • IVR Main Menu

  • Home Page

  • Account Activation

  • Account Balance Query

  • Network Fault Request

INTERACTION NAVIGATION LEVEL

Lookup

Lookup for the level of Interaction Navigation according to the path depth the item is in.

INTERACTION NAVIGATION TYPE

Lookup

Lookup for the type of INTERACTION NAVIGATION ITEM. For example:

  • IVR

  • Web Page

INTERACTION NAVIGATION TYPE VERSION

Reference

Historical versions of INTERACTION NAVIGATION ITEMs.

INTERACTION PRIORITY TYPE

Lookup

Lookup for the different priorities which can be assigned to each EVENT PARTY INTERACTION.

INTERACTION QUESTION RESPONSE

Base

Responses provided by CUSTOMER to interaction questions.

INTERACTION REASON

Lookup

Lookup for interaction reasons. For example:

  • Debt collection

  • Service call

  • Inbound marketing

  • Outbound marketing

  • Customer complaints

INTERACTION RESULT TYPE

Lookup

Lookup for possible responses to customer interaction. For example:

  • Showed interest without decision

  • Offer accepted

  • Never call again

INTERACTION STATUS

Lookup

Lookup for available interaction status. For example:

  • Planned

  • In-progress

  • Executed

  • Closed

INTERACTION STATUS TYPE

Lookup

Classification of Interaction Status for reporting purpose. Currently used similarly to INTERACTION STATUS.

INTERACTION TRANSFER HISTORY

Base

The history of interaction transfers.

INTERACTION TRANSFER REASON

Lookup

Lookup for reasons that an interaction is transferred from one agent to another one. For example:

  • Wrong routing

  • Another business interaction

  • To supervisor

INTERACTION TYPE

Lookup

Lookup for types of interactions between company and CUSTOMER. For example:

  • Email

  • Call Center Inbound

  • Call Center Outbound

  • Walk-In to the shop

  • Letter

INTERNET ACCESS EVENT

Base

Subtype of UDR EVENT, which captures customer internet surfing history with detailed URL and time information.

INVENTORY ADJUSTMENT DOCUMENT LINE ITEM

Base

The detail line item which applies an increment or decrement to the item's unit on hand and or the financial valuation.

INVENTORY ADJUSTMENT ITEM DAY DRVD

Derived

Inventory adjustment information at the item, ORGANIZATION BUSINESS UNIT, day-reason level.

INVENTORY CONTROL DOCUMENT

Base

A written or printed paper, or digital equivalent, that evidences the movement of merchandise or supply SKU ITEMs.

INVENTORY CONTROL DOCUMENT LINE ITEM

Base

Detail line on an INVENTORY CONTROL DOCUMENT that identifies the SKU ITEM, and unit of measure exchanged, or the freight, charges, taxes, and allowances applicable to a particular inventory control event and action.

INVENTORY ITEM STATE

Base

Specifies a unit record of a particular stock ITEM SPECIFICATION, held in a particular Inventory Location, in a particular Inventory State and controlled or managed by a particular Revenue Center.

INVENTORY LOCATION

Reference

Physical location where the retailer stores merchandise. The inventory location may be colocated at a SITE and does not include containers, ships, and trucks that are in transit.

INVENTORY POSITION DEPARTMENT DAY AGGR

Aggregate

Daily status and value of inventory. For example:

INVENTORY POSITION ITEM DAY DRVD

Derived

Status and value of inventory. For example:

INVENTORY POSITION SUBCLASS MONTH AGGR

Aggregate

Daily status and value of inventory. For example:

INVENTORY RECEIPT ITEM DAY DRVD

Derived

Daily record of inventory receipts by item and ORGANIZATION BUSINESS UNIT.

INVENTORY TRANSFER ITEM DAY DRVD

Derived

Daily summary of transfer in and transfer out document statistics. Provides a daily summary of inventory transfers at the item, to ORGANIZATION BUSINESS UNIT, from ORGANIZATION BUSINESS UNIT, and transfer type.

Daily summary of transfer in and transfer out document statistics summary of transfer in and transfer out document statistics.

INVENTORY UNAVAILABLE ITEM DAY DRVD

Derived

Weekly record of inventory receipts by subclass and ORGANIZATION BUSINESS UNIT.

INVENTORY VENDOR COMPLIANCE DAY DRVD

Derived

Daily summary of Vendors' Inventory Compliance.

INVOICE

Base

Invoices issued to accounts representing request for payment for goods and services for a specified period.

INVOICE ADJUSTMENT

Base

Adjustments made on the INVOICE.

INVOICE ADJUSTMENT MONTH AGGR

Aggregate

Monthly aggregation of calculated measures for all adjustments made on the INVOICEs.

INVOICE ADJUSTMENT QUOTA

Reference

Quota of INVOICE ADJUSTMENTs assigned to EMPLOYEE.

INVOICE ADJUSTMENT REASON

Lookup

Lookup for the possible reasons for an adjustment on a customer's or on a partner's bill. For example:

  • Service Activation Error

  • Billing Error

  • Goodwill

  • VIP, Loyalty Program, Customer

  • Promotion Event

  • Service downgrade/fault compensation

  • Customer complain

INVOICE ADJUSTMENT TYPE

Lookup

Lookup for available adjustment types that may be applied to customer invoices. For example:

  1. Direct Total Amount Adjustment

  2. Discount Total Bill Amount Adjustment

  3. Monthly Fee Adjustment

  4. Recharge Fee Adjustment (Prepaid)

  5. Activation Fee Adjustment

  6. Free-Unit Amount Adjustment

  7. Item Charge Adjustment

  8. Loyalty Points Adjustment

  9. Others

INVOICE AGING DAY DRVD

Derived

Daily Summary of aging of invoices (from the time they are open until they closed) for reporting purposes.

INVOICE DELIVERY FORMAT

Reference

The format specification, including header, font, and so on, of each invoice delivered to the customer.

INVOICE DELIVERY TYPE

Lookup

Lookup for available delivery types of INVOICE to customer. For example:

  • Printed letter

  • Email

  • Duplicate printed letter on request

INVOICE DISCOUNT

Base

Discount applied to INVOICE.

INVOICE DISCOUNT REASON

Lookup

Lookup for available discount reasons.

INVOICE DISCOUNT TYPE

Lookup

Lookup for available discount types that may be applied to customer invoice.

INVOICE DRVD

Derived

Statistics on Invoices for further aggregation.

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.

INVOICE GENERATION PROCESS

Base

Process specific for the generation of the Invoices (Billing process) as a subtype of PROCESS EVENT.

INVOICE ITEM

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:

  • Wireless Call

  • Ringtone Downloading

  • Monthly Fixed Rate

INVOICE ITEM DETAIL

Base

Additional details regarding INVOICE ITEM including Product Usage Level.

INVOICE ITEM DETAIL TYPE

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:

  • Call Date

  • Duration

  • Dialed Digits

  • Units

  • Direction

  • Zone

  • Charge Net

  • VAT

  • Total Charge

INVOICE ITEM RELATIONSHIP

Base

Define the relationship between INVOICE ITEMs.

INVOICE ITEM TYPE

Lookup

Lookup for invoice item types. For example:

  • 1 = Long Distance Minutes of Usage

  • 2 = Access Charge

  • 3 = Monthly Fee

  • 4 = Equipment Charge

  • 5 = Roaming Minutes of Usage

  • 6 = Equipment Rental

  • 7 = Installation Charge

  • 8 = Adjustment or Discount

  • 9 = Call Record Detail

INVOICE MONTH AGGR

Aggregate

Monthly aggregation of all invoices to postpaid customers at customer type level.

INVOICE PAYMENT ASSIGNMENT

Base

Matches the payment to an INVOICE.

INVOICE PAYMENT TERM

Base

Payment terms of each INVOICE. For example:

  • Payment days

INVOICE PAYMENT TERM TYPE

Lookup

Lookup for available types of payment terms.

INVOICE PROCESS ASSIGNMENT

Reference

Describes the successful processes related to invoice generation, issuing and dispatching.

INVOICE STATUS

Lookup

Lookup for possible status of the invoices.

INVOICE STATUS HISTORY

Base

Status history for an INVOICE, for example, the invoice may experience a status change from open to closed, or from open to extended.

INVOICE STATUS TYPE

Lookup

Type of INVOICE status. For example:

  • Open (not paid)

  • Closed (paid)

  • Extended (due date is changed)

INVOICE TAX ITEM

Base

The Tax item applied to the INVOICE.

INVOICE TYPE

Lookup

Lookup for type of INVOICE according to invoice generation process. For example:

  • Summary Invoice for hierarchical account

  • Standard Invoice

  • Trial Billing Invoice

INVOLVEMENT ROLE

Lookup

Information about the role in which a resource, a service, or a product is involved.

IP ADDRESS

Reference

Represents an IP address. The IP Address can be either in v4 or v6 form, and can be formatted as dotted decimal or CIDR. One or more host aliases can also be supplied.

IP ADDRESS POOL

Reference

Subtype of ACCESS METHOD POOL, which lists all IP addresses available to customers.

IP SUBNET

Reference

A portion of a network that shares a common address component. On TCP/IP networks, subnets are defined as all devices whose IP addresses have the same prefix. For example, all devices with IP addresses that start with 100.100.100 would be part of the same subnet.

IPV4 ADDRESS

Reference

Refines the generic IP ADDRESS to add formatting capabilities that are specific to IPv4.

ISP

Reference

Internet Service Provider (ISP).

ISP BUSINESS

Reference

The business that the ISP may provide. For example:

  • Company | Services

  • A $ 45.00 Broadband DSL Access 20Mbps Down, 896Kps Up

  • A $ 25.00 Broadband DSL Access 7Mbps, 896Kps Up

  • A $ 19.99 Broadband DSL Access 1.5Mbps, 896Kps Up

  • A $ x.xx Wireless Broadband or cable modem Access

This only covers ISP specific business (not Application Provider business).

ISP BUSINESS ASSIGNMENT

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.

ISP BUSINESS TYPE

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:

  • Virtual private server

  • Dedicated hosting

  • Colocation center

  • Web hosting

  • Free hosting

  • Shared hosting

  • Clustered hosting

  • Reseller hosting

  • Application-specific

  • Blog hosting

  • Image hosting

  • Video hosting

  • Wiki farms

  • File hosting

  • Remote backup service

  • Game server hosting

  • DNS hosting

  • E-mail hosting

ISP TYPE

Lookup

Lookup for types of ISPs.

ISP USAGE EVENT

Base

Records traffic details of each session the user conducts with the Internet Service Provider ISP. The entity documents the connect and disconnect date and 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.

ISP USER

Reference

Identifies the user names associated with the Internet Service Provider (ISP) subscription.

ITEM CLASS

Reference

Classification of Items (as resource).

ITEM CLUSTER

Reference

Grouping of items based on common characteristics.

ITEM COMPANY

Reference

Top level of the item merchandise hierarchy.

ITEM DEPARTMENT

Reference

Fourth level in item hierarchy below ITEM GROUP. Item department consists of one or more item classes.

ITEM DIVISION

Reference

Second level in item hierarchy below ITEM COMPANY. Item Division consists of one or more ITEM GROUPs.

ITEM GROUP

Reference

Third level in item hierarchy, below ITEM DIVISION. Item Group consists of one or more ITEM DEPARTMENTs

ITEM LOOKUP METHOD

Lookup

Method by which the SKU ITEM selling price was retrieved and entered into the Point of Sale system during a RETAIL SALES RETURN LINE ITEM transaction.

ITEM SUBCLASS

Reference

The sixth level in item hierarchy, below ITEM CLASS. Item Subclass consists of one or more items.

ITEM TYPE

Lookup

Type of Item. It is available for Retail type of grouping (such as Hardware, Accessories, and so on) or any other grouping the Communications Provider prefers.

ITEM SPECIFICATION

Reference

Details describing the item or PRODUCT SPECIFICATION.

IVR INTERACTION NAVIGATION HISTORY

Base

Specifies the IVR interaction navigation history.

IVR MENU CONTENT

Reference

Detailed Content description of the IVR Menu with the different choices, and paths (scripts) available. It should be use as part of a complete IVR navigation description.

IVR MENU ITEM

Lookup

The IVR MENU ITEM, which can be used to construct the whole IVR navigation system. Each IVR MENU ITEM represents a group or a specific business function.

JOB

Reference

The occupation of the customer, which is the principal activity the customer performs to earn money.

JOB ROLE

Reference

Job Roles defined in the company that may be assigned to employees. For example:

  • Sales representative

  • Support

  • Product manager

  • Customer representative

  • Call center agent

JOURNAL ENTRY LINE CUSTOMER ORDER ITEM ASSIGNMENT

Base

Cross-Reference from GL SUBLEDGER JOURNAL ENTRY LINE to CUSTOMER ORDER LINE ITEM.

JOURNAL ENTRY LINE INVOICE ITEM ASSIGNMENT

Base

Cross-Reference from GL SUBLEDGER JOURNAL ENTRY LINE to INVOICE ITEM.

JURISDICTION

Reference

List of areas over which authority extends in relationship with the SKU ITEM Service Provider in a way or another.


Table 2-41 K to N Entity Descriptions

Entity Name Type Description

KEY PERFORMANCE INDICATOR SLS PARM

Reference

A measure of a specific aspect of the performance of a SERVICE (network or non-network) or a group of SERVICEs of the same type.

KEY QUALITY INDICATOR SLS PARM

Reference

A measure of a specific aspect of the performance of a product, subscription, or a service. A Key Quality Indicator (KQI) draws data to compute the measure from several sources, including KPIs.

LAN

Reference

A Local Area Network (LAN) is a computer network covering a specific local area, such as a home, office, or small group of buildings. The LAN provides communication between computers and devices.

LAN PROTOCOL

Reference

LAN Protocols operate at the lowest two levels of the OSI model, that is, physical and data link, and are used to define communications over different types of local area media.

LAND PARCEL ADDRESS

Reference

Subtype of ADDRESS LOCATION.

LAND USE TYPE

Lookup

List of possible operations on land, carried out by humans, with the intention to obtain products and benefits through using land resources.

LANGUAGE

Lookup

Languages spoken or written within the company or in interactions with CUSTOMERs.

LANGUAGE DIALECT

Reference

A special type of speaking or written language dialect.

LAYER NETWORK

Reference

A Layer Network is defined by the complete set of Access Groups of the same type that may be associated for transferring information. The information transferred is characteristic of the layer network and is termed characteristic information. The associations of the trail terminations, that form a trail, in a layer network may be made and broken by a layer network management process thus changing its connectivity. A separate, logically distinct layer network exists for each trail termination type. The topology of a layer network is described by access groups, subnetworks, and the links between them.

LEGAL PROCESS STATUS TYPE

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).

LETTER TYPE

Lookup

Lookup for available types of letters that may be sent to CUSTOMERs. For example:

  • Direct marketing

  • Legal letter

  • Contract confirmation letter (Welcome)

LIFECYCLE TYPE

Lookup

Type of Lifecycle, following the general marketing product lifecycle categorization. It can also be used as a further category to flag the market lifecycle period in which a specific product belong finds itself on the market.

LOCAL ADDRESS LOCATION

Reference

The local place within a given geographical address location to locate a specific object, such as a RESOURCE.

LOGICAL CAPACITY

Reference

This entity represents the minimum and maximum requirements, limits, or other variable features of different types of Managed Entities.

LOGICAL DEVICE

Reference

This entity represents logical concepts and services that can be managed that are associated with the device as a whole. Logical Device represents a convenient aggregation point for combining different aspects of a device (For example, software contained in the device, protocols that the devices runs, the set of services that it offers, and so forth). The Logical Device also enables the device itself to have a single logical manifestation. Conceptually, this represents the "brains" of the Device.

For example, the Logical Device represents the set of entities required for a ROUTER to know how to route packets.

LOGICAL DEVICE ATOMIC

Reference

Entity for representing logical concepts and services that can be managed which are associated with the device as a whole. Represents a convenient aggregation point for combining different aspects of a device (For example, software contained in the device, protocols that the devices runs, the set of services that it offers, and so forth).

The Logical Device Atomic also enables the device itself to have a single logical manifestation. Represents all logical devices that are atomic in nature (For example, not made up of multiple distinct logical devices that can be separately managed).

LOGICAL DEVICE COMPOSITE

Reference

Entity for representing logical concepts and services that can be managed which are associated with the device as a whole. Represents a convenient aggregation point for combining different aspects of a device (For example, software contained in the device, protocols that the devices runs, the set of services that it offers, and so forth).

The Logical Device Composite also enables the device itself to have a single logical manifestation. Represents all logical devices that are composite in nature (For example, made up of multiple distinct logical devices that can be separately managed). The composite pattern enables Logical Device Composite objects to be made up of LOGICAL DEVICE objects (that is, either LOGICAL DEVICE ATOMIC and/or Logical Device Composite objects).

LOGICAL DEVICE OS ASSIGNMENT

Reference

This is an association class, and defines the semantics of the Logical Device Uses OS association. This is a complex class, and consequently only a few simple attributes are shown in this viewpoint in order for the reader to get a flavor of the types of parameters defined in this class.

LOGICAL DEVICE ROLE

Reference

Defines required logical features to implement the different roles played by different LOGICAL DEVICEs that are used in a PRODUCT SPECIFICATION or SERVICE.

LOGICAL DEVICE ROLE SPEC

Reference

Entity for all Logical Device Role Specifications. The Logical Device Role Spec entity enables relationships to be defined between it and other classes in the core model. This helps prevent relationship explosion. The Logical Device Role Spec defines the invariant attributes, methods, relationships, and constraints of various types of roles associated with LOGICAL DEVICEs in the model.

LOGICAL DEVICE SPECIFICATION

Reference

Grouping of Common and invariant characteristics and behavior associated with a type of LOGICAL DEVICE.

LOGICAL INTERFACE

Reference

An abstract entity that serves as the superclass for all virtual interfaces. Logical interfaces are also called virtual interfaces. This is because a logical interface has no hardware associated with it, and a logical interface is not physically connected to a network. A logical interface serves as a convenient aggregation point for running different relationships that affect its subclasses, thereby avoiding having to instantiate multiple relationships that are essentially the same.

LOGICAL RESOURCE

Reference

This entity describes different logical aspects of devices (For example, DEVICE INTERFACEs) that constitute a PRODUCT SPECIFICATION. The Logical Resource has two main purposes.

  1. To collect common attributes and relationships for all logical entities.

  2. To provide a convenient, single point where relationships with other managed objects can be defined.

LOGICAL RESOURCE PHYSICAL SUPPORT

Reference

Defines how the LOGICAL RESOURCE supports certain PHYSICAL RESOURCEs.

LOGICAL RESOURCE ROLE

Reference

This entity defines the concept of various types of roles that can be associated with LOGICAL RESOURCEs.

LOGICAL RESOURCE ROLE ASSIGNMENT

Reference

Implements the semantics of the Roles Describe Logical Resource aggregation.

LOGICAL RESOURCE ROLE SPECIFICATION

Reference

Entity for all LOGICAL RESOURCE ROLE specification subclasses. The Logical Resource Role Spec enables relationships to be defined between it and other classes. This helps prevent relationship explosion. The Logical Resource Role Spec defines the invariant attributes, methods, relationships, and constraints of various types of roles associated with LOGICAL RESOURCEs.

LOGICAL RESOURCE SPEC ATOMIC

Reference

This entity describes specific attributes, behavior, relationships, constraints, and semantics for building LOGICAL RESOURCE objects. The purpose of this entity is to track specifications of LOGICAL RESOURCEs separately from other types of Resource Specifications. This entity inherits the Modifies Resource Spec aggregation, and therefore can be used with the corresponding LOGICAL RESOURCE entity. The difference between this entity and the Logical Resource Type Composite entity is that this entity represents standalone specifications of LOGICAL RESOURCE objects. The Logical Resource Type Composite entity represents a hierarchy of specifications of LOGICAL RESOURCE objects.

LOGICAL RESOURCE SPEC COMPOSITE

Reference

This entity describes specific attributes, behavior, relationships, constraints, and semantics for building LOGICAL RESOURCE objects. The purpose of this entity is to track specifications of LOGICAL RESOURCE separately from other types of Resource Specifications. This entity inherits the Modifies Resource Spec aggregation, and therefore can be used with the corresponding LOGICAL RESOURCE entity. The difference between this entity and the Logical Resource Type Atomic entity is that this entity represents a hierarchy of specifications for LOGICAL RESOURCEs. The Logical Resource Type Atomic entity represents a single standalone specification of a LOGICAL RESOURCE.

LOGICAL RESOURCE SPEC PHYSICAL SUPPORT

Reference

Defines how the LOGICAL RESOURCE support certain PHYSICAL RESOURCEs.

LOGICAL RESOURCE SPEC VERSION

Reference

Tracks changes in individual RESOURCE SPECIFICATION as it evolves with time.

LOGICAL RESOURCE SPECIFICATION

Reference

This entity defines the invariant characteristics and behavior (attributes, methods, constraints, and relationships) of a LOGICAL RESOURCE.

LOGICAL RESOURCE TYPE VERSION

Reference

The purpose of this entity is to track Logical Resource Type specifications separately from other types of Resource Specifications. This entity inherits the modifiesResourceSpec aggregation, and therefore can be used with the corresponding Logical Resource Type specification entity.

LOOKUP

Lookup

Abstract ENTITY for all lookup entities.

LOOPBACK INTERFACE

Reference

A Loopback Interface is a virtual interface. Traffic sent to the Loopback Interface is forwarded to the Device itself for further processing. Subtype of DEVICE INTERFACE.

LOYALTY MEMBER POINT DAY DRVD

Derived

Similar to ACCOUNT BALANCE for Loyalty Points, on a daily basis.

LOYALTY MEMBERSHIP ENROLL

Base

Describes the Loyalty membership enrollment event.

LOYALTY PROGRAM

Reference

Loyalty programs available to which customers may be members of.

LOYALTY PROGRAM MO AGGR

Aggregate

Monthly summary of LOYALTY PROGRAM statistics by PRODUCT SPECIFICATION and SALES CHANNEL.

LOYALTY TIER

Reference

Describes the LOYALTY PROGRAM level of membership or tier (typically bronze, silver, gold, platinum) associated with a given loyalty program.

LOYALTY TIER CHANGE HISTORY

Base

Tracks all migration from one loyalty tier to the other of Membership Accounts with the reason.

LOYALTY TIER CLASS

Reference

Grouping of LOYALTY TIER into "class", as required by the marketing needs.

LR STATUS

Lookup

Logical Resource Status as defined by TMF SID. The default values are:

  • 0: Unknown

  • 1: OK

  • 2: Initializing

  • 3: Starting

  • 4: Paused

  • 5: Stopping

  • 6: Stopped

  • 7: Degraded

  • 8: Stressed

  • 9: Predicted Failure

  • 10: Error - General

  • 11: Error - Non Recoverable

  • 12: Not Installed or Not Present

  • 13: In Maintenance

  • 14: Unable To Contact

  • 15: Lost Communications

MAILBOX

Reference

Mailbox allocated to a CUSTOMER.

MANAGE ACTION TYPE

Lookup

Lookup for type of management action that can be performed on a PRODUCT OFFERING. For example:

  • Marketing Manager

  • Creation

  • Marketing Research

MANAGED ENTITY

Reference

This is an abstract entity that represents entities in a managed environment that have the following semantics in common:

  • An ENTITY owns or is otherwise responsible for them.

  • Management of the ENTITY is critical for providing a service and maintaining the environment.

  • The ENTITY is important from a management point-of-view.

MANAGED HARDWARE

Reference

This entity adds additional semantics to the Hardware base entity. These semantics provide management information on the hardware. For example, attributes defined by this entity can provide the administrative and operational state of the entity, and tell whether it has any alarms.

MANAGED TRANSMISSION ENTITY

Reference

This entity describes different types of logical entities that are or help form connections that transmit and/or receive information. This represents a superclass to various ITU specs (For example, G.805 and M.3100) and the IETF concepts, such as those found in various RFCs, so that it can unite ITU and IETF concepts.

MANAGEMENT DOMAIN

Reference

Represents a special grouping of ENTITYs that has two important properties. First, it is used to partition managed objects into a meaningful logical grouping. Second, it provides a means to show how management functions are distributed and scaled.

MANAGEMENT INFORMATION

Reference

Abstract entity represents entities that represent management information obtained in a managed environment. Specifically, in the process of managing an entity, information of various forms are created.

MANAGEMENT PROTOCOL

Reference

A Management Protocol is an abstract superclass for protocols that are dedicated to exchanging management information between network devices. This type of protocol is an application layer protocol, and is used for configuring, monitoring, and gathering information about devices.

MARITAL STATUS

Lookup

Lookup for marital status that may be assigned to an individual.

MARKER POOL

Reference

Represents a set of markings that can be used by one or more MARKER SERVICEs. For example, different marker pools could be defined for different CUSTOMERs as well as for different technologies.

MARKER SERVICE

Reference

Describes the Marker Service used to mark packets in a flow so that different devices in the network know how to treat the traffic that these packets belong to.

MARKER SERVICE MARKER POOL ASSIGNMENT

Reference

Association of a MARKER POOL to a MARKER SERVICE.

MARKER TYPE

Lookup

List of the most common types of MARKER SERVICE, which sets existing bits in specific fields of a packet or frame:0: ToS1: DSCP2: 802-priority field3: 802-vlan id4: ISL class of service field (3 bits)5: Class of Service (other field)6: MPLS Label7: VC ID8: VC Bundle (set of VC IDs)

MARKET AREA

Reference

A geographic area or region or other connotation for which demographic data are available.

MARKET AREA LEVEL

Reference

Hierarchical levels of market area.

MARKET SEGMENT

Reference

A grouping of Parties, Geographic Areas, Sales Channels, and so forth. MARKET SEGMENTs are the target of Marketing Campaigns, PRODUCT OFFERING, Product Promotions, Product Placements, and Product Programs from both internal and external, COMPETITORs, and other Providers, perspective.

MARKET SEGMENT CHARACTERISTIC

Reference

A characteristic quality or distinctive feature of a MARKET SEGMENT. The characteristic can be take on a discrete value, such as sex, can take on a range of values, (for example, household income of $50,000 - $100,000), or can be derived from a formula (for example, number of households = number of customer party roles).

MARKET SEGMENT CHARACTERISTIC VALUE

Reference

A number or text that can be assigned to a MARKET SEGMENT CHARACTERISTIC.

MARKET SEGMENT INCLUSION

Reference

The inclusion relationship between two MARKET SEGMENTs.

MARKET SHARE AGGR

Aggregate

Defines market information (in particular of competitors), including Sales Revenue by Month, Address, and Business Unit.

MARKET SHARE DRVD

Derived

Defines the market information, including Sales Revenue by Month, Address, and Business Unit.

MARKET STATISTICS

Reference

A categorization of performance measures by MARKET SEGMENT.

MARKET STATISTIC INCLUSION

Reference

Relationship between two market statistics.

MEASUREMENT JOB

Reference

Contains the descriptions of the job for scheduling PM related activities: the collection of performance indicators or the production of performance indicators.

MEDIA INTERFACE

Reference

This entity serves as the superclass for all virtual interfaces. Logical Interfaces are also called virtual interfaces. This is because a Logical Interface has no hardware associated with it, and it is not physically connected to a network. The Media Interface serves as a convenient aggregation point for running different relationships that affect its subclasses, thereby avoiding having to instantiate multiple relationships that are essentially the same.

MEDIA INTERFACE LOGICAL INTERFACE ASSIGNMENT

Reference

Association of a logical interface with a media interface (USB, DVD Player...).

MEDIA INTERFACE TYPE

Lookup

Type of media interface available (USB, SD Card Reader, DVD Player,...).

MEDIA OBJECT

Reference

Any form of media in which a CAMPAIGN MESSAGE may appear. For example:

  • Newspaper page

  • Television time slot

MEDIA OBJECT ASSIGNMENT

Reference

Relation of one MEDIA OBJECT to another MEDIA OBJECT.

MEDIA OBJECT COST

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).

MEDIA OBJECT TYPE

Lookup

Lookup for available types of MEDIA OBJECTs. For example:

  • Newspaper

  • Television

MEDIATED CALL EVENT

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.

MEDIATION STATUS CATEGORY

Lookup

Lookup for category of mediation status, such as successfully mediated or failed.

MEDIATION STATUS REASON

Lookup

Lookup for reasons why the UDR event is at certain mediation status. For example:

  • Corrupted File

  • Missing record

MEDIATION STATUS TYPE

Lookup

Lookup of the mediation status of a given raw UDR event. For example:

  • <Rejected>

  • <Successful>

MEMBERSHIP ACCOUNT

Reference

Loyalty Account or ACCOUNT specifically defined for and associated to LOYALTY PROGRAMs. The same customer may have multiple membership accounts.

MEMBERSHIP ACCOUNT BALANCE HISTORY

Base

Stores the account balance history for MEMBERSHIP ACCOUNT (Loyalty) as counterpart of ACCOUNT BALANCE.

METER PROFILE

Reference

Traffic profile that the METER SERVICE can use to compare traffic against. The Meter Profile defines what levels of traffic pass through the METER SERVICE:

Levels that are unaltered

Levels that get delayed

Levels that get dropped

Levels that get further analyzed

METER SERVICE

Reference

A meter is a basic traffic conditioning building block. A meter determines the level of conformance of each packet or flow with respect to a pre-established traffic profile by monitoring a metric of a packet or flow (for example its arrival time). Subtype of TRAFFIC CONDITIONING SERVICE.

METER SERVICE PROFILE ASSIGNMENT

Reference

Association of a METER SERVICE with a specific Meter or traffic Profile against which the measures (of the packet) are done.

MINING CHURN TYPE

Lookup

Specifies mining churn types.

MINING LIFE TIME SURVIVAL VALUE BAND

Lookup

Specifies customer life time survival value band details.

MINING LIFE TIME VALUE BAND

Lookup

Specifies customer life time value band details; band of customer life time value that is predicted from the data mining model. For example, 0~100 USD, 100~200 USD, and so on.

MINING SENTIMENT CATEGORY

Lookup

Specifies details of mining sentiment category.

MINUTE

Reference

Defines minutes as part of time.

MME

Reference

The MOBILITY MANAGEMENT ENTITY (MME) is a key component in LTE network, which authenticates users, and so on. Subtype of PHYSICAL DEVICE.

MMS EVENT

Base

Subtype of UDR EVENT, which collects all information of calls of type Multimedia Messaging Service (MMS).

MMS SERVICE

Base

Specifies the information relative to all the MMS services that customer is using. Subtype of CUSTOMER FACING SERVICE.

MOBILE SWITCHING CENTER

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.

MODEL TYPE

Lookup

Lookup for the model types of items. There may be different "types" for a given model. For example, for a handset a model may allow "Bluetooth" or not.

MONITORED CLASS CRITERIA

Reference

This entity collects criteria for specifying what monitored objects are referenced by a query, specifying a monitored object class in conjunction with a filter.

MONITORED INSTANCES CRITERIA

Reference

This entity collects criteria for specifying what monitored objects are referenced by a query, specifying a list of monitored object instances.

MONITORED OBJECTS CRITERIA

Reference

The entity collects the criteria for specifying what monitored objects are referenced by a query, both scheduled or ad-hoc.

MONTH TODATE TRANSFORMATION

Reference

Defines related calendar elements for performing to-date time transformations.

MONTH TRANSFORMATION

Reference

Transformations with respect to a month. For example:

  • This month last year

  • This year last month

MSC SERVER

Reference

Subtype of PHYSICAL DEVICE.

MSC TRAFFIC DAY DRVD

Derived

Parameters, configurations, and run time statistics related to the MSC (Mobile Switch Center) functioning and performance.

MSC TRAFFIC MONTH AGGR

Aggregate

Monthly aggregation of parameters, configurations, and run time statistics related to the MSC (Mobile Switch Center) functioning and performance.

MUSIC DOWNLOAD

Reference

Subtype of VALUE ADDED SERVICE and PRODUCT SPECIFICATION, which contains the information relative to the music downloading service.

NAICS CLASSIFICATION

Reference

Specifies classifications in the North American Classification System (NAICS).

NAICS INDUSTRY

Reference

Lowest level classification for Industry in the North American Industry Classification System (NAICS).

NAICS INDUSTRY GROUP

Reference

Lookup for Classification Groups in the North American Industry Classification System (NAICS).

NAICS INDUSTRY SECTOR

Reference

Lookup for Industry Sectors in the North American Industry Classification System (NAICS).

NAICS INDUSTRY SUBSECTOR

Reference

Lookup for Industry Sub-sectors in the North American Industry Classification System (NAICS).

NATIONALITY

Lookup

Lookup for available nationalities.

NEGOTIATED SERVICE LEVEL SPEC

Reference

The negotiated service level spec, compared to predefined SLA spec.

NETWORK

Reference

Names and Service Providers for relevant Networks. The full details of a service provider are found in the PARTY and Organizations entities.

A Network is a managed object that represents an aggregation of interconnected telecommunications and management objects capable of exchanging information. The reason that a Network is subclassed from Resource Collection is that it is important that a Network represents physical and logical characteristics and behavior of this collection of telecommunications and management objects. A Network has the additional semantics of having one or more common characteristics and/or behavior. For example, a network may be owned by a single customer or provider, or be associated with the delivery of a specific set of services. A network may be nested within another (larger) network, thereby forming a containment relationship. An example of a network that is contained in another network is a transmission sub-network. The Network is owned by a single Administration and can only perform transmission functions.

NETWORK ADDRESS

Reference

Represents the generic concept of a network address. The Network Address subclasses define different types of addresses of different technologies, such as an IP ADDRESS or an IPXAddress. The use of a Network Address lies in its ability to serve as a convenient point for sourcing and terminating relationships. This eliminates undue duplication of relationships that interact with the subclasses of NETWORK ADDRESS.

NETWORK ADDRESS INTERFACE BINDING

Reference

Defines the semantics of how this NETWORK ADDRESS is contained in this particular DEVICE INTERFACE.

NETWORK ADDRESS TYPE

Lookup

Lookup for the type of network addresses, that is, the invariant characteristics that define a NETWORK ADDRESS. For example, IPv4, IPv6, IPX, and so on.

NETWORK ASSIGNMENT

Reference

Defines the relationship between NETWORKs. For example:

  • One network relies on another network to function.

  • One network belongs to another network.

NETWORK ASSIGNMENT TYPE

Lookup

Lookup for type of network relationship. For example:

  • Composition (one network include another one)

  • RELY (one network relies on another one)

NETWORK ATOMIC

Reference

Represents a standalone Network. Network Atomics may be combined into larger Networks by aggregating them into an appropriate Network Composite object.

NETWORK AVAILABILITY DAY DRVD

Derived

Statistics of network availability measures and all outages that happened to the operator's network.

NETWORK AVAILABILITY MONTH AGGR

Aggregate

Monthly aggregation of network availability statistics and all outages that happened to the operator's network.

NETWORK CAPACITY

Reference

The network capacity of a given network route, trail, or connections.

NETWORK COMPOSITE

Reference

Represents an aggregation of Network Atomic and possibly Network Composite objects. Each Network Atomic object represents a standalone Network; these can be combined to build larger Networks by choosing the appropriate type of Network Composite object to aggregate Network Atomic objects. A Network Composite object can also aggregate Network Composite objects.

NETWORK DOMAIN

Reference

A Network Domain represents a set of Managed Physical Entities that share a common set of administrative and operational characteristics. Primary among these is the use of a common naming methodology. A Network Domain partitions Managed Entity instances into logical groupings. For example, operational and/or administrative groups, that are controlled by one or more common managers. Network Domains provide one way to administer and control the operational characteristics of a set of Managed Entities.

NETWORK DOMAIN ASSIGNMENT

Reference

Assigns RESOURCE into NETWORK DOMAIN.

NETWORK FORWARDING SERVICE

Reference

Subtype of RESOURCE FACING SERVICE

NETWORK ROUTE

Reference

Defines a series of locations a network route may pass.

NETWORK ROUTE POINT

Reference

The points a NETWORK ROUTE may pass through.

NETWORK ROUTE POINT ASSIGNMENT

Reference

Assignment of NETWORK ROUTE POINTs to their NETWORK ROUTE. Multiple NETWORK ROUTEs may share the same NETWORK ROUTE POINT.

NETWORK ROUTE SECTION

Reference

Continuous Section of NETWORK ROUTE,that can be easily and unambiguously defined (for example a linear section from a repeater to the next).

NETWORK SERVICE COVERAGE ASSIGNMENT

Reference

Defines the relationship between NETWORK TOUCHPOINT and SERVICE COVERAGE AREA.

NETWORK SITE

Reference

Specifies a place where RESOURCEs are located or installed.

NETWORK TOUCHPOINT

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:

  • BTS in GSM network

  • Customer installation site in ADSL broadband

NETWORK TOUCHPOINT CLASS

Lookup

Lookup for available classes of NETWORK TOUCHPOINT. For example:

  • Public

  • Private

NETWORK TOUCHPOINT MONTH AGGR

Aggregate

Monthly summary of NETWORK TOUCHPOINTs by CUSTOMER, NETWORK, Address, and so on.

NETWORK TOUCHPOINT DRVD

Derived

Monthly summary of NETWORK TOUCHPOINTs by NETWORK, County, and so on.

NETWORK TOUCHPOINT STATUS

Lookup

Lookup for Available Status codes and descriptions of NETWORK TOUCHPOINT.

NETWORK TOUCHPOINT TYPE

Lookup

Lookup for the type of NETWORK TOUCHPOINT. For example:

  • Cell Site (Wireless)

  • International Switch (roaming partners)

  • Ethernet Socket at Customer site (last mile included - wireline/broadband

  • Switch (wireline - exclusive last mile - wireline/broadband)

NETWORK TYPE

Lookup

Lookup for the types of NETWORK. Will include:

  • PSTN

  • GSM

  • CDMA

NOTIFICATION TYPE

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:

  • SMS

  • Internet mail

The UMS Notification Type dimension helps to organize the notifications data by notification type, along with other dimensions.

NP MOBILE MSISDN

Reference

The mobile MSISDN number of ported number.

NP REQUEST HEADER

Base

The Number Porting (NP) Request submitted by a customer (Porting In) or a recipient operator (Porting Out).

NP REQUEST LINE ITEM

Base

Request Line Item within a Number Porting (NP) request.

NP REQUEST LINE ITEM STATE HISTORY

Base

State history for Number Porting (NP) request line items.

NP REQUEST LINE ITEM STATE TYPE

Lookup

Lookup for type of Number Porting (NP) line item state. For example:

  • Passed

  • Pending

NP REQUEST STATE HISTORY

Base

State history for the Number Porting (NP) request.

NP REQUEST STATE REASON

Lookup

Lists the possible reasons why a Number Portability Request is in a specific state. Such as 'Fraud','Lack of Document'.

NP REQUEST STATE TYPE

Lookup

Lookup for type of state for Number Porting (NP) request. For example:

  • Pre-application

  • Application

  • Document check

NP REQUEST TYPE

Lookup

Lookup for type of Number Porting (NP) Request. For example:

  • Porting In

  • Porting Out

NP STEP

Lookup

Step involved in the Number Porting (NP) request. For example:

  • Application

  • Document check

  • Notify NPAC

NUMBER AREA

Reference

Defines the codes associated to a given area; these codes are typically used for calls to a fixed line number. For example:

  • 1 for Paris (in France)

  • 89 for Munich (in Germany)

A number area could also be associated to other operators, and not to a geographical area. For example, 9 in France.

NUMBER COUNTRY

Reference

Country number. For example:

  • US-01

  • China-86

NUMBER NETWORK TYPE

Lookup

Lookup for available classifications for the network technology, used in relation to subscriptions. For example:

  • in MICA-GCM: CDMA

  • in Flexcab - NTWK, NNSA, WRBL, and so on

NUMBER PORT DAY DRVD

Derived

Aggregation of daily Porting Requests (in/out).

NUMBER PORT MONTH AGGR

Aggregate

Monthly summary of Porting Requests (in/out).


Table 2-42 O to R Entity Descriptions

Entity Name Type Description

ON OFF NET TYPE

Lookup

Lookup of call classifications:

  • On net

  • Off net

OPERATING SYSTEM

Reference

An Operating System is a concrete entity that represents either software and/or firmware that runs the LOGICAL RESOURCE. This entity implements and manages the Resources, tasks, file systems, security, and data available on the LOGICAL RESOURCE. An Operating System is distinct from software applications that are run on the Resource. All applications and software must communicate with the Operating System for all operations that they need.

OPERATOR GROUP

Lookup

Classification group for operators. For example, the group can be classified as:

  • Global Direct Competing

  • Local Competitor

  • Allied by Stock Share

OPERATOR TYPE

Lookup

Lookup for operator type to classify operators. For example:

  • International

  • Local

International operators normally have multiple subsidiaries whose relationship is modeled in the party relationship.

ORACLE GEOMETRY

Reference

Provides geometry information.

ORDER LINE ITEM STATE

Reference

Lookup for the status that a given order line item, in a command, can be assigned. For example:

  • Pending

  • Waiting for Customer feedback

  • Closed

  • Started

  • Error

ORDER LINE ITEM STATE TYPE

Lookup

Lookup for the status that a given order line item can be at. For example:“Pending”

“Waiting for Customer feedback”

“Closed”

“Started”

“Error”

ORDER STATE

Lookup

Lookup for the type of Order State. For example:

  • Open / Processing

  • Pending / Waiting for Customer Feedback

  • Pending / Waiting for Internal Feedback

  • Pending / Waiting for Third Party Feedback

  • Error

  • Closed

  • Cancelled

ORDER STATE TYPE

Lookup

Type of ORDER STATE, used for grouping or summary purpose.

ORDER TYPE

Lookup

Lookup for type of CUSTOMER ORDER. For example:

  • Order for Pickup

  • Order for Delivery

  • Order for Activation

ORGANIZATION

Reference

A sub-type of PARTY that is related to the Communications Service Provider, usually from a Retail perspective. It is not part of the Communications Service Provider. It could have a role as customer upon which it the information should be repeated in CUSTOMER ORGANIZATION.

ORGANIZATION AREA

Reference

An ORGANIZATION HIERARCHY LEVEL within an ORGANIZATION CHAIN. The Organization Area entity is the parent of one or more ORGANIZATION REGIONs.

ORGANIZATION BANNER

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.

ORGANIZATION BUSINESS ENTITY

Reference

Any logical entity that is a part of the enterprise for business analysis and transactions. Classification for a business entity can include company, operation unit, store, or warehouse.

ORGANIZATION BUSINESS UNIT

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:

  • SuperTelco Communications (Mobile)

  • SuperData (Broadband)

ORGANIZATION BUSINESS UNIT COST

Base

Sub-table of COST. This entity associates a specific cost to an ORGANIZATION BUSINESS UNIT (for those costs not covered by EMPLOYEE COST).

ORGANIZATION BUSINESS UNIT HOURS DAY DRVD

Derived

Simple daily summary at ORGANIZATION BUSINESS UNIT level of working, Opening and closing times. It should be limited to any units that may receive public (Retail Shops).

ORGANIZATION BUSINESS UNIT TYPE

Lookup

Lookup for type of ORGANIZATION BUSINESS UNIT. For example:

  • Call Center

  • Branch Office

  • Warehouse

ORGANIZATION CHAIN

Reference

An ORGANIZATION HIERARCHY LEVEL within an ORGANIZATION COMPANY. Organization Chain entity is the parent of one or more ORGANIZATION AREAs.

ORGANIZATION COMPANY

Reference

An ORGANIZATION HIERARCHY LEVEL within an ORGANIZATION CORPORATE. Organization Company entity is the parent of one or more ORGANIZATION CHAINs.

ORGANIZATION CORPORATE

Reference

Highest level of ORGANIZATION HIERARCHY. Organization Corporate entity is the parent of one or more ORGANIZATION COMPANYs.

ORGANIZATION DISTRICT

Reference

An ORGANIZATION HIERARCHY LEVEL within an ORGANIZATION REGION. Organization District entity is the parent of one or more ORGANIZATION BUSINESS UNITs.

ORGANIZATION DIVISION

Reference

An ORGANIZATION HIERARCHY LEVEL within ORGANIZATION CORPORATE.

ORGANIZATION HIERARCHY

Reference

User defined. Master list of all of the hierarchies in an organization.

ORGANIZATION HIERARCHY LEVEL

Reference

The association entity for the hierarchies and levels.

ORGANIZATION HIERARCHY LEVEL ASSIGNMENT

Reference

Assignment of Hierarchy Levels to ORGANIZATION HIERARCHY.

ORGANIZATION HIERARCHY VERSION

Reference

Version of ORGANIZATION HIERARCHY.

ORGANIZATION ITEM SELLING PRICE

Reference

Associate selling price to the item. Each organization might have different prices for the same item model.

ORGANIZATION LEVEL

Reference

List of all the business levels within an organization.

ORGANIZATION LEVEL ATTRIBUTE VALUE

Reference

Values for the user defined attributes associated with an ORGANIZATION HIERARCHY LEVEL.

ORGANIZATION LEVEL ATTRIBUTES

Reference

Attributes assigned to an ORGANIZATION LEVEL.

ORGANIZATION MARKET DATA

Reference

Publicly available and statistical information regarding the internal or external parties, such as DUNS number and number of employees.

ORGANIZATION NAME

Reference

Different types of organization names represent the associated business legal status of their organization.

ORGANIZATION REGION

Reference

An ORGANIZATION HIERARCHY LEVEL within an ORGANIZATION AREA. Organization Region entity is the parent of one or more ORGANIZATION DISTRICTs.

ORGANIZATION SERVICE WEBSITE

Reference

Subtype of the ORGANIZATION BUSINESS UNIT. This entity collects all information on websites managed by the operator. This normally includes only public information.

ORGANIZATION TYPE

Lookup

Type of ORGANIZATION. The category is similar to ORGANIZATION BUSINESS UNIT TYPE but they can be different.

ORGANIZATION WAREHOUSE

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:

  • Chairs

  • Telephone poles

  • Network equipment

  • Auto transmissions

  • Handsets

ORGANIZATIONAL DEMOGRAPHY VALUE

Reference

User defined attribute definitions and corresponding values regarding demographic statistics as related to an ORGANIZATION BUSINESS UNIT.

OS LICENSE ASSIGNMENT

Reference

Defines the semantics of the Party Role Licenses OS association. The OS License Assignment attributes help specify the licensing details for this particular OPERATING SYSTEM instance.

OTHER INDIVIDUAL

Reference

Individual associated with a PARTY organization, other than those defined such as CUSTOMER or EMPLOYEE.

P LOGICAL DEVICE ROLE

Reference

Defines required logical features to implement the specific role of a P (Provider Core) device, as used in a PRODUCT SPECIFICATION or SERVICE.

PACKET CONTROL UNIT OUTAGE REASON

Lookup

Lookup for reasons for a Packet Control Unit (PCU) outage in GPRS technology. For example:

  • Link Down

  • Bit Error Rate

PAGE

Reference

Web Page Description as part of a complete website navigation build-up and tracking.

PARTNER PAYMENT

Base

The payment made to the partners, such as vendors, dealers, and so on. The partners may also have accounts in the source system such as Oracle BRM, therefore, this payment may refer to that account.

PARTNER PAYMENT TYPE

Lookup

Lookup for types of partner payment transactions. For example:

  • Dealer commission

  • Purchase order Payment

PARTNER PROMOTION PROGRAM

Reference

Assigns costs of a given PROMOTION to a Partner or PARTY participating in the promotion.

PARTNER SETTLEMENT MONTH AGGR

Aggregate

The monthly summary of financial settlement activities that have happened to partners at higher level.

PARTNER SETTLEMENT DRVD

Derived

Financial settlement activities that have happened to each partner within the month.

PARTNER SETTLEMENT REASON

Lookup

Lookup for valid reason codes for a partner settlement.

PARTY

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.

PARTY ACCOUNT ASSIGNMENT

Reference

Assignment of a PARTY to an ACCOUNT. Depending on type of party, the relationship can be:

  • Customer owns the ACCOUNT (typically for individual customers: there is one customer and one account)

  • Multiple Customers may share the same account:

    This type of assignment is typical when several ORGANIZATION BUSINESS UNITs or individuals, association or employees, have, for example, a shared balance of free minutes to use on top of their own package (with their own ACCOUNT).

PARTY ACCOUNT ASSIGNMENT TYPE

Lookup

Lookup for type of relationship between PARTY and ACCOUNT. Depending on type of party, the relationship can be:

  • Customer owns the account

  • Multiple customers may share the same account

PARTY ADDRESS LOCATION ASSIGNMENT

Reference

Associates one or more ADDRESS LOCATIONs with a PARTY.

PARTY AGREEMENT ASSIGNMENT

Reference

Assignment of a PARTY to an AGREEMENT, in general, or a contract.

PARTY AGREEMENT ASSIGNMENT ROLE

Lookup

Lookup for valid Roles that Parties may be assigned in PARTY AGREEMENT ASSIGNMENT.

PARTY AGREEMENT ASSIGNMENT TYPE

Lookup

Lookup for type of the PARTY AGREEMENT ASSIGNMENTs. For example:

  • Customer agreement

  • Managing employee

PARTY AM PRODUCT OFFERING ASSIGNMENT HISTORY

Base

The status history of assignment among PARTY, ACCESS METHOD, and PRODUCT OFFERING. The assignment history among ACCESS METHOD, PRODUCT OFFERING, and PARTY.

PARTY AM PRODUCT OFFERING ASSIGNMENT STATUS

Base

The current status and relationship between ACCESS METHOD, PRODUCT OFFERING and PARTY, before being moved to PARTY AM PRODUCT OFFERING ASSIGNMENT HISTORY once changed.

PARTY ASSIGNMENT

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.

PARTY ASSIGNMENT REASON

Lookup

Lookup for valid reasons parties may be associated with each other. For example:

  • Cooptation (customer brings in a new customer)

  • Financial Responsibility

  • Hierarchical relationship in the organization

  • Contractual agreement

PARTY ASSIGNMENT TYPE

Lookup

Lookup for the type of the party relationship. For example:

  • Father and son

  • Organizational hierarchy, subsidiary

  • Customer referral

PARTY BUSINESS INTERACTION ROLE

Reference

The business interaction role which can be assigned by a PARTY.

PARTY CONTACT INFORMATION

Reference

Contact information for a party.

PARTY CONTACT INFORMATION TYPE

Lookup

Lookup for the type of contact information. For example:

  • Email

  • Home telephone number

  • Office telephone number

  • Cell phone number

  • Pager number

PARTY CONTACT LIST PARTICIPATION

Lookup

Relationship between PARTY and CONTACT LIST. For example, a party belongs to a contact list.

PARTY CONTACT LIST ROLE

Lookup

The Role of the PARTY in a CONTACT LIST.

PARTY COST ASSIGNMENT

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:

  • Handset

  • Network Device

  • Gifts

Cost might be assigned to multiple parties. For example, for operational cost several organizations may share the same expense on a PROMOTION or CAMPAIGN.

PARTY DEMOGRAPHIC

Reference

A demographic profile for a PARTY.

PARTY DEMOGRAPHIC VALUE

Reference

Defines individual and organization demography value for a given party demographic profile.

PARTY EVENT TYPE

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.

PARTY GEOGRAPHY ENTITY ASSIGNMENT

Reference

Assigns a PARTY to one or more GEOGRAPHY ENTITYs.

PARTY IDENTIFICATION

Reference

Identifying information unique to a PARTY.

PARTY IDENTIFICATION TYPE

Lookup

Lookup for valid types of PARTY IDENTIFICATION. For example:

  • Driver's License

  • DUNS Number

PARTY LANGUAGE CAPABILITY

Reference

Keeps the language capability score for each party.

PARTY LOCATION REASON

Lookup

Lookup for available reason code and description for why a PARTY may be assigned to an address. For example:

  • Billing address

  • Shipping address

PARTY LOCATION TYPE

Lookup

The type of relationship between the PARTY and the address. For example:

  • Office location

  • Primary Living location

  • Product Installation Address

PARTY MANAGEMENT ROLE

Lookup

Defines all roles which a party plays in a CAMPAIGN, such as management or potential customer.

PARTY MARKET SEGMENT ASSIGNMENT

Reference

Assigns a PARTY to the market segment it belongs to.

PARTY NAME

Reference

Lists any other known names from the life history of a given party.

PARTY ORDER ASSIGNMENT

Base

Assignment of PARTY to a given Order. For example:

  • Sales Agent gets a sales commission because of a customer order.

  • A customer refers another customer to the operator network. The customer may receive incentives.

PARTY ORDER ASSIGNMENT TYPE

Lookup

Lookup for available assignment type codes and descriptions pertaining to PARTY ORDER ASSIGNMENT. For example:

  • Customer of agreement

  • Sales agent for the order

  • Vendor selling the order

PARTY PRODUCT SUBSCRIPTION ASSIGNMENT

Reference

Defines a PARTY's relationship to a PRODUCT SUBSCRIPTION. For example: a customer owns a subscription.

PARTY PRODUCT SUBSCRIPTION ROLE

Lookup

Lookup for valid Roles that may be assigned to PARTY in regards to the PRODUCT SUBSCRIPTION.

PARTY PROFILE

Reference

A match between a PARTY and a PARTY PROFILE TYPE. It is based on matching PARTY characteristics, such as use of a product, with the characteristics of a PARTY PROFILE TYPE.

PARTY PROFILE CHAR ASSIGNMENT

Reference

Association of (Profile specific) Characteristics to a given PARTY PROFILE.

PARTY PROFILE TYPE

Lookup

List of possible types of PARTY PROFILE. For example:

  • Party Preference for Marketing actions

  • Party Interests (Music, Sports, and so on)

PARTY PROFILE TYPE CHARACTERISTIC

Reference

The characteristic a party profile may take. For example, age, education, and so on.

PARTY PROFILE TYPE CHARACTERISTIC VALUE

Reference

The actual value for each PARTY PROFILE TYPE CHARACTERISTIC on the party profile.

PARTY PROJECT PARTICIPATION

Reference

Describe the roles of each party in the project.

PARTY PROMOTION RESPONSE

Base

Response of a PARTY to a PROMOTION.

Records the customers response result to the initiative. For example, positive responses:

  • The customer accepted the offer.

  • The customer increased or modified their usage.

  • The customer changed a specified behavior (for example moved from payment by check to an electronic payment option).

PARTY ROLE

Lookup

Lookup for Roles a PARTY may be assigned in an EVENT.

PARTY ROLE ASSIGNMENT

Reference

Assigns party roles for the party. PARTY and PARTY ROLE are an X-X relationship. This relationship may change due to a agreement change, or for other reasons.

PARTY ROLE CATEGORY

Reference

Specifies a simple grouping or categorization of PARTY ROLEs.

PARTY ROLE CATEGORY ASSIGNMENT

Reference

Shows the association between PARTY ROLE and various PARTY ROLE CATEGORYs

PARTY ROLE OS PROCESS ASSIGNMENT

Reference

Defines the semantics of the Party Role Uses Processes association. Since different PARTY ROLEs have different privileges for working on and running the OPERATING SYSTEM, an association class is needed to accurately model these details.

PARTY ROLE PROFILE ASSIGNMENT

Reference

Association of a given party ROLE (Customer, Provider, and so on) to a profile. Some profiles are only to be defined for specific roles while others can be defined for any.

PARTY ROLE STATUS

Lookup

Status history of each role that a PARTY has taken.

PARTY ROLE TYPE

Lookup

Type of PARTY ROLE, a general grouping for reporting purpose.

PARTY SEGMENTATION METHOD

Lookup

Method used to create the segment, such as K-means clustering in Data Mining.

PARTY SERVICE ASSIGNMENT

Reference

Defines the relationship between PARTY and SERVICE.

PARTY SERVICE ASSIGNMENT REASON

Lookup

Lookup for available reasons for a PARTY and SERVICE relationship.

PARTY SERVICE ASSIGNMENT ROLE

Lookup

Lookup for valid roles and descriptions a PARTY may be assigned for a SERVICE. For example:

  • Service Creation role

  • Service consumer by customer

PARTY SIM CARD ASSIGNMENT

Reference

The relationship between SIM CARD and PARTY.

PARTY SIM CARD ROLE

Lookup

The role which PARTY add in regards to the SIM CARD.

PARTY SKILL

Reference

Defines skills with a score and skill level to each PARTY.

PARTY STATUS CATEGORY

Lookup

Higher level of Party Status. For example:

  • Financial Status

  • Credit Status

  • Payment Status

  • Personal Status

  • Legal Status

PARTY STATUS CHANGE REASON

Lookup

Lookup for valid reasons that may be assigned for a Party Status change. For example:

  • Hire

  • Transfer

  • New customer

PARTY STATUS HISTORY

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.

PARTY STATUS TYPE

Lookup

Lookup for status type of the PARTY. For example:

  • Active

  • Inactive

  • Defaulted

  • New customer

  • VIP, Loyalty Program, customer

  • Black listed

Credit Class is used to rank Customer Credit. For example, the entity value can be:

  • Good

  • Fair

  • Bad

Or the customer may be defined as:

  • Gold

  • Silver

  • Bronze

The party's credit is based on the underlying accounts held by the party.

PARTY TYPE

Lookup

Lookup for party type that classifies involved parties according to their inherent characteristics and structure. For example:

  • Person

  • Organization

  • Organization Unit

PASSPORT

Reference

The passport as a type of PARTY IDENTIFICATION.

PAY CATEGORY

Lookup

Lookup for type of pay category on a pay slip. For example:

  • Salary

  • Deductions

  • Contributions

  • Taxes

PAY TV SERVICE

Reference

Subtype of PRODUCT SPECIFICATION. Pay TV is subscription-based product to deliver TV channels to a customer.

PAY TYPE

Lookup

Lookup for the type of payment made to the employee. For example:

  • Bonus

  • Basic wages

PAYMENT AGING CLASS

Lookup

The classification of accounts according to payment delay history. For example:

  • 0-10 days

  • 11-20 days

PAYMENT CHANNEL

Reference

Channel by which customer may pay for service. For example:

  • Bank (automatic payment)

  • Store (Check, cash)

  • Call Center (Credit Card)

  • Web (Credit Card)

PAYMENT METHOD TYPE

Lookup

Lookup for valid methods of payment. For example:

  • Cash

  • Check

  • Credit Card

  • Debit Card

PAYMENT PLAN

Reference

List of plans for payment (typically for Credit purpose but not only).

PAYMENT TRANSACTION TYPE

Lookup

Lookup for type codes and descriptions for transaction types associated with the ACCOUNT PAYMENT. The payment may be, for example:

  • Periodically Invoice

  • Installation Fee

  • Pre-deposit to the account

  • Late Pay Penalty Payment

  • Regular Monthly

  • Refund / Void

PE LOGICAL DEVICE ROLE

Reference

Defines required logical features to implement the specific role of a PE (Provider Edge) device, as used in a PRODUCT SPECIFICATION or SERVICE.

PEAK OFFPEAK TIME

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:

  • Normal Day

  • Holiday

  • Friday

  • Sunday

For the special days defined in the system.

PERFORMANCE

Base

A measure of the manner in which a SERVICE or RESOURCE is functioning.

PERFORMANCE APPLICABILITY

Reference

The time of day or days during which a PERFORMANCE SPECIFICATION is measured or not measured.

PERFORMANCE CAT CHARACTERISTIC VALUE

Reference

A value of a Characteristic Specification provided for PERFORMANCE CATEGORY that further defines what the PERFORMANCE CATEGORY is.

PERFORMANCE CAT SPEC RELATIONSHIP

Reference

A specification for an association that can be established between two instances of PERFORMANCE CATEGORYs.

PERFORMANCE CAT SPECIFICATION

Reference

The invariant characteristics that define a group or set of performance qualities that are classified together because of common characteristics.

PERFORMANCE CATEGORY

Reference

A group or set of performance qualities that are classified together because of common characteristics.

PERFORMANCE CATEGORY RELATIONSHIP

Reference

An association between two instances of PERFORMANCE CATEGORYs.

PERFORMANCE CHARACTERISTIC VALUE

Reference

A value of a characteristic provided for PERFORMANCE that further defines what the PERFORMANCE is.

PERFORMANCE CONSEQUENCE

Reference

An action taken if a PERFORMANCE OBJECTIVE is not met.

PERFORMANCE INDICATOR

Reference

A numeric value or text determined for a PERFORMANCE INDICATOR SPECIFICATION. For example, a value of .005 ms that represents average packet delay.

PERFORMANCE INDICATOR GROUP

Lookup

Defines a grouping of PERFORMANCE INDICATORs coming together (normally as a group of performance measurements).

PERFORMANCE INDICATOR GROUP SPEC

Lookup

A group of indicators, usually reported in the same message by the equipment.

PERFORMANCE INDICATOR RELATIONSHIP

Reference

An association between two PERFORMANCE INDICATORs, such as one indicator derived from another.

PERFORMANCE INDICATOR SPEC RELATIONSHIP

Reference

An association between two PERFORMANCE INDICATOR SPECIFICATIONs, such as one indicator derived from another.

PERFORMANCE INDICATOR SPECIFICATION

Reference

A measure of a specific aspect of the performance of an entity, such as a lost packets or average jitter, defined for a PERFORMANCE SPECIFICATION that may trigger the creation of a PERFORMANCE CONSEQUENCE.

PERFORMANCE IP ADDRESS

Reference

A Performance-related extension to an IP ADDRESS.

PERFORMANCE MOBILE ADDRESS

Reference

A network address that identifies mobile Resource Resources, such as cell sites and base station controllers.

PERFORMANCE NETWORK ADDRESS

Reference

A Performance-related extension to a NETWORK ADDRESS. A NETWORK ADDRESS defines different ways to identify where an Resource is, such as an IP ADDRESS, or an IPXAddress, or a Point Code.

PERFORMANCE NOTIFICATION

Reference

A communication that occurs as part of measuring performance. A Notification is typically one-sided, that is, no Response is expected.

PERFORMANCE NOTIFICATION SPECIFICATION

Reference

The invariant characteristics that define a communication (notification) that occurs as part of performance measurement. A Notification is typically one-sided, that is, no Response is expected.

PERFORMANCE OBJECTIVE

Reference

A goal for a PERFORMANCE INDICATOR defined in terms of metrics, thresholds, and tolerances.

PERFORMANCE OBJECTIVE APPLICABILITY

Reference

The time of day or days during which a PERFORMANCE OBJECTIVE is evaluated or not evaluated.

PERFORMANCE OBJECTIVE APPLICABILITY CONSEQUENCE

Reference

The time of day or days during which a Performance Objective Consequence applies or not to the violation of a PERFORMANCE OBJECTIVE.

PERFORMANCE POINT CODE

Reference

The performance gathered on a POINT CODE (subtype of NETWORK ADDRESS).

PERFORMANCE SPEC INTERVAL CONVERSION

Reference

The conversion factor that defines how many instances of one PERFORMANCE SPECIFICATION INTERVALs are contained in the related PERFORMANCE SPECIFICATION INTERVAL.

PERFORMANCE SPECIFICATION

Reference

The invariant characteristics that define a measure that determines how a SERVICE and/or Resource is functioning.

PERFORMANCE SPECIFICATION INTERVAL

Reference

The interval of time for represented by the PERFORMANCE SPECIFICATION.

PERIOD TO DATE TRANSFORMATION

Reference

Cumulative time transformations at the period level.

PERIOD TRANSFORMATION

Reference

Time transformations at the period level.

PERSONAL ID REQUIRED TYPE

Lookup

Possible Types of Identification (document) required for a person (Driving license, Personal ID, passport).

PHASE

Reference

Not used.

PHONE NUMBER

Reference

The phone number as a subtype of access method.

PHONE NUMBER POOL

Reference

The telephone number pool allocated to the TELCO operator.

PHYSICAL CAPACITY

Reference

This entity represents the minimum and maximum requirements, limits, or other variable features of a Managed Device or MANAGED HARDWARE object.

PHYSICAL CAPACITY DETAIL

Reference

Represents the semantics of the Has PHYSICAL CAPACITY association. The Physical Capacity Detail provides additional semantics describing the different types of PHYSICAL CAPACITYs that this Managed Component contains, and provides methods to tell how many PHYSICAL CAPACITYs are associated with this particular Managed Component instance.

PHYSICAL COMPONENT

Reference

This is the base entity for different types of Physical Components that can reside either in an EQUIPMENT or an Equipment Holder object. They cannot be used as a standalone object. From a management point-of-view, this object either cannot or does not need to be split into its constituent parts. For example, an ASIC (or Chip) cannot, and a tape for data storage does not need to be split up into their constituent parts. Any piece of hardware that is not a PHYSICAL LINK, PHYSICAL CONNECTOR, EQUIPMENT, or Equipment Holder, is a subclass of this class.

PHYSICAL CONNECTOR

Reference

This is a concrete entity that represents any type of hardware unit that connects to other hardware units and transmit signals and/or power between them.

PHYSICAL CONTAINER

Reference

This entity adds additional semantics to the MANAGED HARDWARE entity. The associated attributes define whether a MANAGED HARDWARE object can be removed and/or replaced, and whether this action requires power to be removed or not when the action is performed.

PHYSICAL COUNT DOCUMENT

Base

Document associated with the manual Inventory (typically done once a year) in retail shops.

PHYSICAL COUNT DOCUMENT LINE ITEM

Base

Describes the line items in the documents associated with a manual Inventory in retail shops.

PHYSICAL DEVICE

Reference

This entity represents hardware devices that can be managed. Represents a convenient aggregation point for combining different aspects of a device (for example, the cables, connectors, cards, power supplies, and other objects that together comprise the device). Thus, it enables the device itself to have a physical manifestation (for example, the "Internet Gateway Router" can be identified as a PHYSICAL DEVICE). Examples of this entity include routers and switches, computers, and other end-devices that are managed.

PHYSICAL DEVICE ATOMIC

Reference

Entity for representing hardware devices that can be managed that contains no sub-ordinate devices. In other words, this physical device is a standalone physical device. Represents a convenient aggregation point for combining different aspects of a device (for example, its physical composition and the set of services that it offers). The Physical Device Atomic also enables the device itself to have a physical manifestation. Examples of this entity include routers and switches, computers, and other end-devices that are managed.

PHYSICAL DEVICE COMPOSITE

Reference

Entity for representing hardware devices that can be managed that contains one or more sub-ordinate devices. In other words, this physical device is not a standalone physical device; rather, it represents an aggregation of physical devices. Each physical device in this aggregation can be managed. Represents a convenient aggregation point for combining different aspects of a device (for example, its physical composition and the set of services that it offers). The Physical Device Composite also enables the device itself to have a physical manifestation. Examples of this entity include routers and switches, computers, and other end-devices that are managed.

PHYSICAL DEVICE ROLE SPEC

Reference

Entity for all Physical Device Role Specification subclasses. The Physical Device Role Spec enables relationships to be defined between itself and other entities in the core model. This helps prevent relationship explosion. The Physical Device Role Spec entity defines the invariant attributes, methods, relationships, and constraints of various types of roles associated with PHYSICAL DEVICEs in the model.

PHYSICAL DEVICE ROLE SPEC DETAIL

Reference

Captures the semantics of the Specifies Physical Device Roles aggregation.

PHYSICAL DEVICE SPEC

Reference

This entity describes specific attributes, behavior, relationships, constraints, and semantics for building PHYSICAL DEVICE objects.

PHYSICAL EQUIPMENT

Reference

Represents physical components of a managed device, including replaceable components. An instance of this object class must be present in only a single geographic location. An Equipment object may be nested within another Equipment object, thereby creating a containment relationship. The Equipment type shall be identified by sub-classing this object class. Either the name of the sub-class or an attribute may be used for identifying the equipment type.

PHYSICAL LINK

Reference

This is a concrete entity that represents the connecting or cabling together of hardware entities. This entity enables both wireless and connector-based communication to be modeled.

PHYSICAL PORT

Reference

Represents an actual or potential end point of a topological (physical) link, and corresponds directly to a physical port on a topology map. Physical Ports are always contained by another physical object - they cannot exist by themselves. The two most common examples are Physical Ports on a CARD and on a CHASSIS.

PHYSICAL PORT RESOURCE PORT ASSIGNMENT

Reference

This entity is a concrete entity that defines the semantics of the PHYSICAL PORTs In Resource Port aggregation. For example, it will describe characteristics and behavior of the PHYSICAL PORTs that comprise this particular Resource Port in terms of dependencies and how a PHYSICAL PORT interacts with other PHYSICAL PORTs.

PHYSICAL RESOURCE

Reference

This entity describes different types of hardware that constitute a PRODUCT SPECIFICATION. The Physical Resource has two main purposes:

  1. To collect common attributes and relationships for all hardware.

  2. To provide a convenient, single point where relationships with other managed objects can be defined.

PHYSICAL RESOURCE ADDRESS

Reference

Not used.

PHYSICAL RESOURCE CHARACTERISTIC

Reference

This is a concrete base class for defining the characteristic features and behavior of a Physical Element Specification. Every Physical Element Specification has a variety of important attributes, methods, constraints, and relationships which distinguish that Physical Element Specification from other Physical Element Specifications. We call these Physical Element SpecCharacteristics. Each of these characteristics is used at the business level to characterize a Physical Element Specification.

PHYSICAL RESOURCE PRODUCT SUBSCRIPTION

Reference

A subtype of PRODUCT SUBSCRIPTION to track tangible device usage by the customer.

PHYSICAL RESOURCE ROLE

Reference

This is a physical role that a device has. The Physical Resource Role enables the correlation of physical components that route traffic with the logical capability of routing traffic.

PHYSICAL RESOURCE ROLE ASSIGNMENT

Reference

This class implements the semantics of the RolesDescribePhysical Element aggregation.

PHYSICAL RESOURCE ROLE SPECIFICATION

Reference

Entity for all Physical Resource Role Specification subclasses. The Physical Resource Role Spec enables relationships to be defined between it and other classes in the model. This helps prevent relationship explosion. The Physical Resource Role Spec defines the invariant attributes, methods, relationships, and constraints of various types of roles associated with Physical Resources, whether they are subclasses of PHYSICAL DEVICE or Hardware, in the model.

Specifies relationships to be defined between it and other classes in the model. This helps prevent relationship explosion.

PHYSICAL RESOURCE ROLE SPECIFICATION DETAIL

Reference

Captures the semantics of the PHYSICAL RESOURCE ROLEs aggregation.

PHYSICAL RESOURCE SPECIFICATION

Reference

This entity defines the invariant characteristics and behavior, attributes, methods, constraints, and relationships, of a PHYSICAL RESOURCE.

PHYSICAL RESOURCE SPECIFICATION ATOMIC

Reference

Describes specific attributes, behavior, relationships, constraints, and semantics for building PHYSICAL RESOURCE objects. The purpose of this entity is to track Physical Resource Specifications separately from other types of Resource Specifications. This entity inherits the Specifies Resource aggregation, and therefore can be used with the corresponding PHYSICAL RESOURCE entity. The difference between this entity and the PHYSICAL RESOURCE SPECIFICATION COMPOSITE entity is that this entity represents standalone Physical Resource Specifications. The PHYSICAL RESOURCE SPECIFICATION COMPOSITE entity represents a specification that is in reality made up of a set (usually a hierarchy) of Physical Resource Specifications.

PHYSICAL RESOURCE SPECIFICATION COMPOSITE

Reference

This entity describes specific attributes, behavior, relationships, constraints, and semantics for building Physical Resource objects. The purpose of this entity is to track Physical Resource Specifications separately from other types of Resource Specifications.

This entity inherits the modifiesResourceSpec aggregation, and therefore can be used with the corresponding PHYSICAL RESOURCE SPECIFICATION entity. The difference between this entity and the PHYSICAL RESOURCE SPECIFICATION ATOMIC entity is that this entity represents a hierarchy of Physical Resource Specifications. The PHYSICAL RESOURCE SPECIFICATION ATOMIC entity represents a single standalone Physical Resource Specification.

PIPE

Reference

Pipe is an abstracted Link between two network resources (which are also abstracted as TERMINATION POINTs).

PIT CHARACTERISTIC

Reference

Not used.

PIT CHARACTERISTIC TYPE

Lookup

Not used.

PLANNING PERIOD

Reference

Period level in the planning calendar.

PLANNING QUARTER

Reference

Quarter level in the planning calendar.

PLANNING SEASON

Reference

Season level in the planning calendar.

PLANNING WEEK

Reference

Week level in the planning calendar.

PLANNING YEAR

Reference

Year level in the planning calendar.

PLATFORM

Reference

Platform (from a Software or Applications perspective) on which an application or a software runs.

POINT BLOCK

Reference

ISUP Signaling OPC and DPC attributes. It is associated with "block point".

POINT CODE

Reference

ISUP Signaling OPC and DPC attributes that map to Region, Subregion, Node Type, and Node Name.

POINT OF SALE DEPARTMENT

Reference

Point of Sale (POS) grouping of items with similar point of sale control and processing attributes. The entity type may also be used to control sales that are not properly identified at the item level.

POINT OF SALE IDENTITY TYPE

Lookup

Lookup for type of identifier used in POS identity.

POINT OF SALE TENDER FLOW DRVD

Derived

Point of Sale (POS) Tender transactions by minute and tender type for a workstation in an ORGANIZATION BUSINESS UNIT.

POINT OF SALE TYPE

Lookup

Type of Point of Sale (POS) transactions.

POINTS EXPIRY BASIS

Reference

List the various periods (or basis) on which points will expire.

POLICIER SERVICE

Reference

Specifies limits for traffic flow to a configured bit rate with limited bursting capability. For example, a standard policer service has no buffering, meaning that packets that cannot be transmitted are simply dropped.

POLICY

Reference

This entity is the root of the POLICY model. As such, it defines common attributes, methods and relationships that all policy subclasses use and take part in.

POLICY ACTION

Reference

This entity represents how to form the action clause of a POLICY RULE. This consists of a single occurrence of a POLICY STATEMENT, which is of the form: {variable, operator, value} Policy actions have the semantics of "SET variable to value". There are two types of actions: - pass actions are invoked if the condition clause was TRUE - fail actions are invoked if the condition clause was FALSE.

POLICY ACTION ASSIGNMENT

Reference

This entity specifies the semantics needed for the contained Policy Actions aggregation.

POLICY ACTION ATOMIC

Reference

This is the base entity for all simple POLICY ACTIONs. A simple POLICY ACTION consists of a single Boolean clause, which performs a single action. This consists of a single occurrence of a POLICY STATEMENT, which is of the form: {SET | CLEAR} POLICY VARIABLE to POLICY VALUE. This is distinctly different from the Policy Action Vendor, which does not use a POLICY STATEMENT. Policy Action Atomic objects can also be used to form more complex action structures. A Policy Action Composite object contains a group of Policy Action Atomic objects; this grouping enables multiple Policy Action Atomic objects to be executed as a group. Alternatively, a Policy Action Atomic object can contain one or more Policy Action Atomic objects (and also Policy Action Composite groups if desired) to provide the semantics of a compound Policy Action. In either case, the aggregation is done using the contained Policy Actions aggregation.

POLICY ACTION COMPOSITE

Reference

Serves as a generic container in which to place Policy Action Atomic, Policy Action Vendor, or Policy Action Composite entities. The first two provide actions that this container groups, while the latter establishes a hierarchy in which to order the execution of POLICY ACTIONs. Both simple and complex POLICY ACTIONs can be placed in this container. Each Policy Action Atomic and Policy Action Vendor object is linked to this object using the containedPolicy Actions association.

POLICY ACTION RULE ASSIGNMENT

Reference

This entity specifies the semantics needed for the Policy Action In Policy Rule aggregation. This aggregation defines the set of POLICY ACTIONs that are contained in this POLICY RULE.

POLICY ACTION VENDOR

Reference

Provides a general extension mechanism for representing POLICY ACTIONs that have not been modeled with the attributes specified in this model. This entity uses two of its properties (Constraint and Constraint Encoding) for defining the content and format of a vendor-specific condition. Its third property (actionResponse) to provide a standard result, so that this object can be placed with other POLICY ACTION objects in a POLICY RULE object. Standardized extensions are not expected to use this entity.

POLICY APPLICATION ASSIGNMENT

Reference

This is an association class that explicitly defines which Managed Entities in a Policy Domain this Policy information applies to.

POLICY CONDITION

Reference

This entity represents how to form the condition clause of a POLICY RULE. This entity represents rule-specific or reusable policy conditions. Policy conditions are of the form: {variable, operator, value} where the operator is usually the MATCH operator, but could be another type (for example, compare) of operator. This gives the semantics of "IF the condition is TRUE (or FALSE)". The subclasses of POLICY CONDITION, along with its recursive aggregation, enable simple and compound (for example, nested) POLICY CONDITIONs to be supported by the same structure.

POLICY CONDITION ASSIGNMENT

Reference

This entity specifies the semantics needed for the Policy Condition In Policy Condition aggregation. This aggregation defines the set of POLICY CONDITIONs that are contained in this POLICY CONDITION. The POLICY CONDITION Contained Policy Condition Details entity and the Policy Condition Rule Details entity have conceptually the same attributes. This is because they both provide semantics to form a condition expression. The difference lies in their placement relative to the POLICY RULE entity. That is, the Contained Policy Condition Details entity combines individual expressions within a condition clause, whereas the Policy Condition Rule Details entity describes how the completed condition clause appears to the POLICY RULE.

POLICY CONDITION ATOMIC

Reference

This is the base entity for all simple policy conditions. A simple policy condition consists of a single Boolean clause, which tests a single condition. This consists of a single occurrence of a POLICY STATEMENT, which is of the form: {variable, operator, value} This design relies on the POLICY STATEMENT to supply the actual terms to form the condition clause. Thus, since everything is normalized to a condition clause, no subclasses of Policy Condition Atomic are needed. Instead, subclasses of the appropriate POLICY STATEMENT classes are provided. A compound POLICY CONDITION consists of one or more POLICY CONDITIONs contained inside a higher-level POLICY CONDITION. These can optionally be grouped by a POLICY CONDITION COMPOSITE object if desired.

POLICY CONDITION COMPOSITE

Reference

The POLICY CONDITION COMPOSITE entity is the base entity for all complex policy conditions. A complex policy condition consists of an aggregation of POLICY CONDITION ATOMIC and POLICY CONDITION COMPOSITE objects, which in turn form a complex Boolean statement. Such an object still evaluates to a single Boolean TRUE or FALSE value.

Conceptually, this is a standalone object that consists of one POLICY CONDITION that provides an overall context for either a nested or a group of subordinate POLICY CONDITIONs to be evaluated.

POLICY CONDITION RULE ASSIGNMENT

Reference

This entity specifies the semantics needed for the Policy Condition In Policy Rule aggregation. This aggregation defines the set of Policy Conditions that are contained in this POLICY RULE. The Contained Policy Condition Details entity and the Policy Condition Rule Details entity have conceptually the same attributes. This is because they both provide semantics to form a condition expression. The difference lies in their placement relative to the POLICY RULE entity. That is, the Contained Policy Condition Details entity combines individual expressions within a condition clause, whereas the Policy Condition Rule Details entity describes how the completed condition clause appears to the POLICY RULE.

POLICY CONDITION TIME PERIOD

Reference

Lists the various Time Period with POLICY CONDITION. It gives the "capability of enabling or disabling a POLICY CONDITION according to a pre-determined time schedule".

POLICY CONDITION VENDOR

Reference

General extension mechanism for representing POLICY CONDITIONs that have not yet been modeled with the attributes specified in this model.

POLICY EVENT

Base

Represents an aggregation of Policy Events, constrained according to the eventConstraint attribute of the Event Details aggregation entity. This set of Policy Events is then presented to one or more POLICY RULEs to trigger the evaluation of their condition clauses. This entity enables an external application, such as a Policy Server, to dynamically adjust the set of events that are being used to trigger the evaluation of a POLICY RULE.

POLICY EVENT ATOMIC

Base

Represents the occurrence of a single atomic event, which triggers the evaluation of the condition clause of a POLICY RULE.

POLICY EVENT COMPOSITE

Base

Represents the occurrence of a composite event. A composite event is an event that is made up of a set of Policy Event Atomic and/or Policy Event Composite entities. Like a Policy Event Atomic, a Policy Event Composite can also be used to trigger the evaluation of the condition clause of a POLICY RULE.

POLICY GROUP

Reference

This entity is a generalized aggregation container. A Policy Group enables POLICY RULEs and POLICY GROUPs to be aggregated in a single container. Note that loops, including the degenerate case of a POLICY GROUP that contains itself, are not allowed when POLICY GROUPs contain other POLICY GROUPs.

POLICY GROUP EXECUTION DETAIL

Reference

This is an association entity that defines the semantics associated with a Policy Event Set being applied to a POLICY GROUP. Specifically, it controls through its Execution Filter attribute which components in the POLICY GROUP this Policy Event Set will be passed to, so it can be evaluated.

POLICY OPERATOR

Reference

This is a concrete entity for modeling different types of operators in a POLICY STATEMENT. By restricting the type of operator used in a POLICY STATEMENT, one can effectively restrict the semantics of that POLICY STATEMENT.

POLICY OPERATOR VARIABLE ASSIGNMENT

Reference

Defines the relationship between POLICY OPERATOR and POLICY VARIABLE.

POLICY ROLE

Reference

This entity defines the concept of various types of roles for different policies that are used.

POLICY RULE

Reference

Entity for realizing the "event-condition-passaction-failaction" semantics that form a the model policy rule. The semantics of this rule are that the rule is evaluated when an event occurs. If the condition clause is satisfied, then the pass-action clause will be executed (otherwise, the fail-action clause will be executed). POLICY RULEs may be nested within POLICY RULEs. This is often needed in networking (for example, bandwidth allocation).

POLICY SET

Reference

This entity defines two types of collections. POLICY RULE collects Policy Events, POLICY CONDITIONs, and POLICY ACTIONs, while POLICY GROUP collects POLICY RULEs and POLICY GROUPs. Two important and powerful features of this arrangement are that a POLICY SET defines a common decision strategy and a common set of POLICY ROLEs to be used by the POLICY GROUPs and the POLICY RULEs that inherit from it.

POLICY SET ASSIGNMENT

Reference

Defines relationship between POLICY SETs.

POLICY STATEMENT

Reference

This entity models the triplet {variable, operator, value} that is used by both the POLICY CONDITION and POLICY ACTION entities. The semantics are reflected in the types of operators that are allowed to be used in each case. For conditions, users want the semantics of "variable relates to value", where "relates to" is usually the match operator, but could also be other applicable operators (for example, a comparison operator). For actions, users want the semantics of "set variable to value". Here, the only operator allowed is the set operator.

POLICY VALUE

Reference

An abstract base entity for modeling different types of values that occur in a POLICY STATEMENT. The POLICY VALUE specifies an attribute that should either be set or cleared (if used in a POLICY ACTION) or matched or compared to a value of the POLICY VARIABLE in a POLICY CONDITION.

POLICY VARIABLE

Reference

This entity models different types of variables that form a POLICY STATEMENT. The variable specifies an attribute or concept that should either be matched or compared to a value when the condition is evaluated.

POLICY VARIABLE VALUE ASSIGNMENT

Reference

This is an association class that contains the OCL expression that will be used to define the particular semantics of how this Value is constrained by this Variable. This includes constraints such as upper and lower bounds of the value that a POLICY VALUE object can take.

POSTAL SERVICE TYPE

Lookup

Lookup for type of postal service type available to the carrier. For example:

  • First-Class Mail

  • Registered Mail

  • Regular Mail

  • Postal Card

POSTCODE

Reference

Postal Code, Zip Code, or similar geographical designation.

PPA CATEGORY

Lookup

Lookup for categorizations of prepaid allowances. For example:

  • Local Call Allowance

  • Long Distance Call Allowance

  • Bonus Free Minutes

  • Internal (Inside Operators network) Call Allowance

PPA DEDUCTION TYPE

Lookup

Lookup for valid deduction types as related to prepaid allowances (PPA).

PREAMBLE MARKER SERVICE

Reference

Subtype of MARKER SERVICE.

PREAMBLE MARKING DETAILS ASSIGNMENT

Reference

Details the TRAFFIC CONDITIONING SERVICE linked to the PREAMBLE MARKER SERVICE.

PREFERENCE TYPE

Lookup

The type of preference relevant to consumers or customers (for example, color preference).

PREPAID ACCOUNT STATISTIC DRVD

Derived

Monthly aggregation of prepaid account revenue, including: air time, recharge value and so on, by ACCOUNT, SALES CHANNEL, AGE ON NET BAND.

PREPAID ALLOWANCE DAY DRVD

Derived

The summary of daily prepaid voucher recharge.

PREPAID ALLOWANCE MONTH AGGR

Aggregate

Monthly summary of free minutes allowance (PPA) in a PRODUCT OFFERING.

PREPAID MOBILE EVENT 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:

  • Initial activation

  • Recharges

  • Adjustments

  • Deactivations

PREPAID RECHARGE

Base

Type of ACCOUNT PAYMENT in which a PREPAID VOUCHER is recharged.

PREPAID VOUCHER

Reference

The voucher a customer can buy to refill their prepaid account, normally in the form of a paper or plastic card. For example:

  • Prepaid Mobile Recharge Voucher

  • Prepaid Calling Card

PREPAID VOUCHER BATCH

Reference

Each voucher instance generation batch may produce thousands vouchers.

PREPAID VOUCHER RECHARGE OPTION

Reference

The recharge options for a type of PREPAID VOUCHER. A voucher can be configured with different perceived value to the customer and they may choose to redeem any one of them. For example a voucher may have the following recharge options:

  • $10 cash

  • $5 and 400 SMS

  • 20Mb data

PREPAID VOUCHER SPECIFICATION

Reference

Specification associated with (an instance of) a Voucher. The voucher customer can buy to refill their prepaid account, normally in form of a paper or plastic card. For example:

  • Prepaid Mobile Recharge Voucher with face value $50

  • Prepaid Calling Card

It is subtype to ITEM SPECIFICATION.

PRICE DERIVATION RULE

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.

PRICE EVENT

Reference

Type of event which may trigger a billing process, for example, event of customer using a product over its quota.

PRICE REASON

Lookup

Possible REASONs for setting a given price. This is informative only.

PRICE TYPE

Lookup

Lookup for type codes and descriptions for COMPOSITE PRODUCT SPECIFICATION charge on a PRODUCT SPECIFICATION. For example:

  • One time charge

  • Usage duration charge

  • Usage per call charge

  • Usage amount charge (data transfer)

  • Monthly cycle forward fee

  • Monthly cycle arrear fee

  • Free unit charge

  • Free charge

  • Factorization (call charge* a factor)

PRICE TYPE RELATION REASON

Lookup

Lookup for available reasons for PRICE TYPEs to be related to each other.

PRICE TYPE RELATIONSHIP

Reference

Assignment of related PRICE TYPEs.

PRIORITY QUEUING SERVICE

Reference

Entity to monitor queues and ensure that they are used properly. Subtype of QUEUE SERVICE.

PROBLEM

Base

Defines any type of problems in general. Specifies details that are always applicable when dealing with problems as part of a process.

PROBLEM COMMENTS

Base

Any comments or additional text associated with a PROBLEM. It is a separate entity to allow several comments to a given PROBLEM depending on who is dealing with it.

PROBLEM ESCALATION LEVEL

Lookup

The different levels of priority which can be assigned to any PROBLEM (and concretely to SERVICE PROBLEM).

PROBLEM LOCATION ASSIGNMENT

Base

Association of one or more ADDRESS LOCATIONs to a given PROBLEM. Typically, it would be the location of the source of the problem. But it could also be the address of main alarm or whatever fits the problem description.

PROBLEM RELATIONSHIP

Base

Describes Relationships between problems, in particular if they are causally related.

PROBLEM RESOURCE ASSIGNMENT

Base

Describes the resources involved in the root cause of the PROBLEM.

PROBLEM SERVICE ASSIGNMENT

Base

Describes the services that are associated with the root cause of the PROBLEM.

PROBLEM STATUS HISTORY

Base

Defines the history of status of any PROBLEMs: for example, from opened to solved pending confirmation to solved.

PROBLEM TRACKING RECORD ASSIGNMENT

Base

Associates TRACKING RECORDs to PROBLEMs.

PROBLEM TROUBLE TICKET ASSIGNMENT

Reference

Association of TROUBLE TICKETs to specific (service) PROBLEMs.

PROCESS

Reference

Defines the various possible processes as defined by the Communications Service Provider. It should normally fits within eTOM but could be generalized to any type of processes at any place (within a software or from an organization perspective). It is the general description of a potentially recurring series of events with various complexity (parallelism, sequentially related or not, and so on). This entity is required to track any process events in Oracle Communications Data Model.

PROCESS COST

Base

Tracks the costs associated with a specific PROCESS EVENT, from any point of view (labor cost, effective cost like ink, paper and stamps, and so on).

PROCESS EVENT

Base

The effective run of a given process from start to end. Although not explicitly required, a process event is usually expected to be an atomic event (no sub-process event). But nothing in Oracle Communications Data Model prevents a building up of complex process and process event structure. Process event is not a sub-type of EVENT.

PROCESS EVENT ASSIGNMENT

Reference

Describes the effective or actual sequential relationship between PROCESS EVENTs.

PROCESS EVENT PARAMETER VALUE OPERATOR ASSIGNMENT

Base

Assignment for a specific PROCESS EVENT of Operators (logical or mathematical in general) to some of its parameters and values.

PROCESS EVENT PRODUCT OFFER PRICE ASSIGNMENT

Reference

Association of process events with a specific PRODUCT OFFERING PRICE (or rate plan). This is usually used at rating or Billing time to deal with specific offering or customers (or partners like for interconnection settlement) following particular processes or calculations.

PROCESS INVOICE DAY DRVD

Derived

Daily summary of the end-to-end invoice processing (Billing, issuing, dispatching), observed from the end process (that is, Successful Dispatching).This entity is critical for the computation of some TMF KPIs.

PROCESS INVOICE DISPATCHING EVENT

Base

Defines any INVOICE dispatching process (from upload to the web to standard mailing to the customers) with some specific statistics related.The process event is considered ended once the letter or email is sent or when the invoice is available for download to the customer. It does not wait to get confirmation of receipt.

PROCESS INVOICE GENERATION EVENT

Base

Lists and describes any INVOICE GENERATION PROCESS (also called Billing Process itself, from invoice item collections to final invoice set-up ready for printing or publishing) with some specific statistics related. All the bill content shall be present in an electronic form, ready to be sent as-is to either the printing process or to the web publishing or formatting process (for example that turns it into a PDF if it is not already the case).

PROCESS INVOICE ISSUING EVENT

Base

Describes statistics for the process of issuing a bill. For example, printing, preparing for customer online display, creating pdf file for download, and so on.

PROCESS PARAMETER

Reference

List the parameter expected and their definition to be filled to allow given PROCESSes to run.

PROCESS PARAMETER ASSIGNMENT

Reference

Association of the standard Parameter(s) expected to the PROCESSes to be able to run.

PROCESS PARAMETER OPERATOR

Lookup

List of Operators (logical or mathematical in general) available to be associated with Parameters from specific processes.

PROCESS PARAMETER VALUE

Reference

Lists of effective Parameter values used per process event.

PROCESS RELATIONSHIP

Reference

Defines the standard sequential or causal relationships between processes. These are not necessarily the effectively used ones but default should be at least defined.

PROCESS RELATIONSHIP TYPE

Lookup

Type of relationship between processes. Typically, it is "SEQUENTIAL" (FROM then TO) or "PARENT" (FROM includes TO). But other relationships could be imagined.

PROCESS SPECIFICATION

Reference

Lists the specifications (that is, invariant characteristics) of a given PROCESS.

PROCESS SPECIFICATION RELATIONSHIP

Reference

Relationships between PROCESS SPECIFICATIONs, where required.

PROCESS STATUS

Lookup

Lists the possible status of a process event. The first Word of the "NAME" can be used for grouping purpose.

PROCESS TYPE

Lookup

Lists the types of PROCESSes one deals with. It should correspond to the eTOM processes a priori, but there are none pre-defined.

PRODUCT

Reference

The real instance of a given PRODUCT SPECIFICATION which a customer can purchase or rent (or eventually gets for free as part of a PRODUCT OFFERING). The product is linked to the Customer Order Line Item and relates a product to a customer. For example:

  • Song specified as "You are not alone": Corresponding to Product MUSIC DOWNLOAD

  • TV channel specified as "Discovery" - Corresponding to Product PAY TV SERVICE

PRODUCT BRAND

Lookup

Brand of the PRODUCT SPECIFICATION or PRODUCT OFFERING. The operators can provide the same product under different brands for different segments of customers. For example, some operators may have brand such as Business, High End, Economical, for the same gsm wireless product.

PRODUCT CAPABILITY

Reference

Various product capabilities, or features. For example:

  • Number of lines for a phone

  • Storage size for Email

  • Number of "Friends&Family" numbers

PRODUCT CAPABILITY TYPE

Lookup

Lookup for type of PRODUCT CAPABILITY.

PRODUCT CAPABILITY VALUE

Reference

Detailed PRODUCT CAPABILITY information. The information would be quantitative by PRODUCT CAPABILITY TYPE.

PRODUCT CATALOG

Reference

A list of PRODUCT OFFERING for sale, with prices and illustrations, for example in book form or on the web. Product Catalogs can be used by Customers during a self-care ordering process and may be used across one or more Distribution Channels.

PRODUCT CATALOG CHARACTERISTIC

Reference

A characteristic quality or distinctive feature of a Product Catalog Specification.

PRODUCT CATALOG CHARACTERISTIC ASSIGNMENT

Reference

A use of the Product Catalog Spec Characteristic by an Entity Specification to which additional properties (attributes) apply or override the properties of similar properties contained in Product Catalog Spec Characteristic.

PRODUCT CATALOG CHARACTERISTIC RELATIONSHIP

Reference

A aggregation, migration, substitution, dependency, or exclusivity relationship between/among Characteristic Specifications.

PRODUCT CATALOG CHARACTERISTIC VALUE

Reference

A value associated with a Product Catalog Characteristic.

PRODUCT CATALOG CHARACTERISTIC VALUE ASSIGNMENT

Reference

A use of the Product Catalog Spec Characteristic Value by an Product Catalog Specification to which additional properties (attributes) apply or override the properties of similar properties contained in Product Catalog Spec Characteristic Value.

PRODUCT CATALOG CHARACTERISTIC VALUE RELATIONSHIP

Reference

A aggregation, migration, substitution, dependency, or exclusivity relationship between/among Characteristic Spec Values.

PRODUCT CATALOG GEOGRAPHY ASSIGNMENT

Reference

Defines which PRODUCT CATALOG is available in which geographical area.

PRODUCT CATALOG PRESENTATION TYPE

Reference

The PRODUCT CATALOG presentation type. For example:

  • Brochure

  • Web pages

  • Video

PRODUCT CATALOG PRODUCT OFFERING ASSIGNMENT

Reference

Defines the relationship between a PRODUCT CATALOG and the PRODUCT OFFERINGs that appeared on the PRODUCT CATALOG.

PRODUCT CATALOG SALES CHANNEL ASSIGNMENT

Reference

Defines where the PRODUCT CATALOGs are made available to the end user.

PRODUCT CATALOG TYPE

Lookup

Lookup for types that define the invariant characteristics of a PRODUCT CATALOG.

PRODUCT CHARACTERISTIC TYPE

Lookup

List the possible types of PRODUCT characteristics (features, look, and so on).

PRODUCT CHARACTERISTIC VALUE

Reference

Lists the possible values a given PRODUCT characteristic can take, ordered by type.

PRODUCT COVERAGE AREA

Reference

Coverage of a product over geographical area.

PRODUCT COVERAGE GEOGRAPHY DETAIL

Reference

Details the area covered by a given PRODUCT or SERVICE COVERAGE AREA. It relies on third party marketing data associated with given ADDRESS LOCATION Code within a given SERVICE COVERAGE AREA.

PRODUCT FUNCTIONALITY DEPENDENCY

Reference

Assignment of valid EQUIPMENT FUNCTIONALITY and PRODUCT SPECIFICATION VERSIONs to a PRODUCT SPECIFICATION.

PRODUCT GEOGRAPHY ASSIGNMENT

Reference

Association of PRODUCT SPECIFICATION to certain geography or region, usually as available for sales or delivery (for example, Fiber-to-home network is usually only available in big cities in the first phase of development).

PRODUCT LINE

Lookup

Lookup for the ways to classify products according business organization. For example: Wireless, Fixed Line, and so on.

PRODUCT OFFERING

Reference

Defines how a product is brought to the market, including: positioning, pricing, and bundling details. For example:

  • Tariff Liberty 60, with 60 Free National Minutes, 3 Friends & Family Network Intern Numbers

  • DSL 32Mbit/s + VoIP Phone + TV Entertainment + Pay TV Soccer Championship one year promotion

PRODUCT OFFERING ASSIGNMENT TYPE

Lookup

Lookup for type of product participation (inclusion) in the market plan. For example:

  • Use as gift

  • Main product

  • Revenue generation service

  • Base on

PRODUCT OFFERING AVAILABILITY

Reference

Reference for Available PRODUCT OFFERING in different area or organization business unit.

PRODUCT OFFERING COST

Base

Sub-table of the COST TYPE table. This entity associates a specific cost to a given PRODUCT OFFERING. The cost should not be related to the CAMPAIGN or to the PROMOTION, but just to the PRODUCT OFFERING.

PRODUCT OFFERING DOCUMENT REQUIREMENT

Reference

Defines the customer document requirements of each PRODUCT OFFERING.

PRODUCT OFFERING GEOGRAPHY ASSIGNMENT

Reference

Relationship between PRODUCT OFFERING and Geography. Some PRODUCT SPECIFICATIONs may only be sold in a particular area.

PRODUCT OFFERING GROUP

Reference

Hierarchy level to group the various PRODUCT OFFERINGs. For example:

  • Postpaid "Family"

  • Broadband "Business Unlimited"

  • Prepaid "Freedom"

PRODUCT OFFERING GROUP ASSIGNMENT

Reference

Defines relationship of PRODUCT OFFERINGs to one or more PRODUCT OFFERING GROUPs.

PRODUCT OFFERING GROUP TYPE

Lookup

Lookup for the type code and description for a PRODUCT OFFERING GROUP.

PRODUCT OFFERING MANAGEMENT

Base

The management history of PRODUCT OFFERING by the employee.

PRODUCT OFFERING MARKET SEGMENT AVAILABILITY