Professional Documents
Culture Documents
Sample-Datawarehouse Requirements PDF
Sample-Datawarehouse Requirements PDF
SAMPLE
Requirements Examples
DAVID M WALKER
Version: 0.1
Date: 01/01/2006
http://www.datamgmt.com
Sample - Requirements Examples
Table of Contents
Synopsis
This document has a number of samples of completed sections from the four sets of
requirements (Business, Data, Query and Interface) to aid analysts in completing their own
templates. The requirements are a merger of actual requirements taken from Telcos around
the world. They are not consistent nor should anything be read into any requirements as
coming from any particular operator. There are no examples from the Technical
Requirements as they do not have the same form of template table.
Intended Audience
Reader Recommended Reading
Executive Synopsis through to Background
Business Users Synopsis through to Background
IT Management Entire Document
IT Strategy Entire Document
IT Project Management Entire Document
IT Developers Entire Document
Business Requirements
BUSINESS REQUIREMENT
Business Requirement Number 1
Business Requirement Name Organisations & Individuals (Customers)
Priority High
Currently available in the Data Warehouse Yes
Description
There is a requirement to hold details and build a history of customers activities with Telco,
tracking them through their Telco relationship life cycle, from initial marketing prospect,
through sales, service provisioning, billing, etc.
Organisations and individuals include customers and prospects for Telco products and
services and all others for which information can be obtained. Organisations may also be
OLO (Other Licensed Operators) network customers, third-party dealers, the customers of
third-party dealers, and other organisations such as Telco own business units, OFTEL,
contractors, suppliers, etc.
Note: prospects details are only required for prospects that have become customers or
prospects that form part of the Target Account List.
The information held for organisations and individuals must include name, address,
postcode, etc. and a standardised version the customer name into a common search
format.
A detail of all organisations sites e.g. addresses and service locations of installed
equipment.
The relationships between organisations and individuals must be maintained, e.g. multiple
contacts for customer organisations. This should include the individuals full contact details
and what they do, such as influencers, decision makers, finance/procurement contact, IT
director or contact, telephony contact, billing contact, data network contact, marketing
contact, etc.
These is also a need to hold enhanced profile information about organisations such as:
Telecomm profile - Comms spend (not just with Telco), telecomm products/services
used, equipment used, other suppliers used (and products), PBX supplier.
There is a need to maintain a history of the relationship between a customer and other
associated information. This information includes contracts, orders, products and services,
accounts, usage, non-usage, billing, payments, contacts, faults, sites, telephone numbers,
sales channels, sales account manager, market segmentation, etc.
o Sales channel related hierarchies, i.e. how sales view their customers.
Over time, as history information is accumulated, these hierarchies will allow detailed
analysis of behaviour to be performed by relating the revenue, product, account, orders etc.
together for an organisational structure.
Customer profitability. Initially this will only include interconnect in-payments / out-
payments against products and services delivered. When available, sources of
actual cost information should be included.
Customer details, e.g. monthly numbers and revenue, by customer life cycle status,
customer hierarchy level, SOV (Sales Order Value), product, price package,
discount plan, actual and potential comms spend, installed equipment, geography,
campaign response or marketing activity, market segment, sector.
Number and names of customers lost, their worth and billing trends.
Other patterns in the customer base, e.g. customer lifecycle, customer historic
trends, customer buying cycle, customer revenue, cost profiles, profitable/non-
profitable, customer site moves, etc.
The dealer and reseller relationship, including revenue and payments, by call type,
national, mobile, international, etc. Also, aggregate third party customers into their
respective dealers / suppliers.
Existing resellers and dealers to identify potential reseller and dealer companies.
OLO customer revenue (in-payments and out-payments) and usage patterns and
trends, by routes/points of interconnect, tail costs, time of day, inbound, outbound,
etc.
Dealer: A dealer is a third party organisation that has an existing business base
through which it can sell standard Telco Branded Products. Telco owns the
customer and consequently the Customer benefits from 24hr customer care and
management reports etc. In return for acquiring customers on Telcos behalf the
dealer receives an ongoing 'revenue share this is a proportion the customers
billing.
Reseller: The Reseller purchases Telco products at wholesale rates and 'resells'
them under their own brand. The contractual relationship is between the reseller
and the customer, not Telco. The reseller sets his own retail pricing, bills the
customer, arranges premise routing and provides customer care. Telco will provide
the reseller with a monthly wholesale bill and provide customer care for bill queries
and network faults to the reseller only, contact is not made between Telco and the
reseller's customer.
The reseller can be further subdivided into two groups: those who aggregate carrier
minutes (an Aggregator) and those who merely resell (Direct Reseller) from one or
two carriers.
Aggregator: By using 'smart' MLU technology e.g. black box or via sophisticated
PBX software, customer premise routing is made over a number of carriers
according to price.
Aggregators are able to maximise their buying power to secure the best possible
rate for each route. Aggregators approach customers as an independent telecomm
provider. The offer is to remove the purchase and pricing decision from the
customer by pooling rates from all carriers and therefore always offering the best
possible combination of rates. Effectively they will manage a customers telephony
needs.
The solution should not support lead tracking, contact management - Not all the
information that the sales force will require is likely to be held in the warehouse as
this will not be a suitable repository.
Data Overview
Performance Measures Dimensionality / Ordered By / Described By
Technical Assessment
Other Comments
Data Requirements
Dimensions
DIMENSION
Dimension Number 1
Dimension Name Party
Description
The Party dimension represents individuals, their parent organisations and the higher-level organisation
structure.
Hierarchy Structure
Holding
Company
Customer
Account
Customer
Site
Customer
Line Identity
This dimension is intended to represent individuals and organisations of interest to Telco so,
for instance, this may represent organisations with which Telco have a customer, supplier or
interconnect relationship.
The diagram above depicts one of the specific hierarchies that is required the customer
reporting hierarchy.
Business and trading names of an organisation and all its subsidiaries and parent
companies.
o Sales channel related hierarchies, i.e. how sales view their customers.
Organisations also include third-party dealers, the customers of third-party dealers, OFTEL,
contractors and suppliers. No hierarchical structure within any of these is required.
Data Steward
Status Changes (Slowly Changing Dimensions)
The customer reporting hierarchy is likely to change at a rate between quarterly and annually.
The Telco sales organisation is likely to change at a rate between monthly for small changes
and annually for large changes.
It is important that this information stays as up to date as possible for those organisations with which
Telco carries out transactions. For other organisations, such as prospects, the data refresh requirement
is more lenient.
Implementation Notes
Performance Measures
PERFORMANCE MEASURE
Performance Measure Number 1
Performance Measure Name Vanilla Rated Call Revenue Amount
Measure Type Basic
Definition
The Vanilla Rated Call Revenue is the amount of revenue generated by a call, and is attached to
a Call Detail Record (CDR) by the first pass of the rating engine.
Additional Commentary
As such, this Vanilla Rated Call Revenue Amount is the basic revenue value attached
to the call record, and includes factors such as the time of day the call was made, the
day of the week, the message source code, the charge band and the specific rating
group.
It excludes any subsequent rating changes that are applied by the billing system, which
turn Vanilla Rated Call Revenue into the Re-Rated Call Revenue.
The Vanilla Rated Call Revenue Amount could also loosely be referred to as unbilled
usage revenue, and should therefore have a revenue status type of unbilled usage
revenue.
Data Steward
Dimensionality / Ordered By / Described By
For unbilled usage: Vanilla Rated Call Revenue Amount will be accumulated alongside
the Call Duration on a daily basis by telephone number per bill cycle, and will be zeroed
at the start of each bill production run for that telephone number. A later increment
may load individual unbilled usage revenue at the CDR level for both Vanilla Rated Call
Revenue and Call Duration.
For billed usage: Vanilla Rated Call Revenue Amount will be stored at the individual
CDR level alongside the Call Duration and the Re-Rated Call Revenue Amount.
Individual Call Detail Records are required for a rolling three months, which therefore implies that
Vanilla Rated Call Revenue Amounts will be available for a rolling three months.
The cumulative unbilled usage (Vanilla Rated Call Revenue Amount and Call Duration)
by telephone number by bill cycle will be a daily feed into the system.
At the billed usage level, this information should be loaded into the system once per bill
production run. That is, there are currently estimated to be six bill production runs per
month.
Implementation Notes
PERFORMANCE MEASURE
Performance Measure Number 2
Performance Measure Name Number of Services
Measure Type Count
Definition
Additional Commentary
For example we may wish to know the number of different service codes and their
descriptions by account number and service location, in order to explore service mix.
Data Steward
Dimensionality / Ordered By / Described By
Implementation Notes
PERFORMANCE MEASURE
Performance Measure Number 3
Performance Measure Name Bill Balance Brought Forward Amount
Measure Type Derived
Definition
The Bill Balance Brought Forward Amount is the balance brought forward from the
previous bill cycle's bill
Additional Commentary
The Bill Balance Brought Forward Amount should be the same as the previous bill
cycles Bill Balance Carried Forward Amount.
The Bill Balance Brought Forward Amount will be sourced directly from the source
billing systems.
Data Steward
Dimensionality / Ordered By / Described By
The speed of response will depend on the available level of pre-calculated aggregates.
This information could be made available from the source systems should the Systems
Roadmap point to this being an area of high priority.
Implementation Notes
Query Requirements
Query Requirement
Query Requirement Number 1
Query Requirement Name Credit/aged report
Description
A report that show the outstanding debt by account and credit group
Requested by
Data Overview
Debts by account and how long that debt has been outstanding
Technical Assessment
Other Comments
Frequency Weekly
Type Regular
Interface Requirements
Interface
Interface Number 1
Interface Name Customer Segmentation Groups
Target System Name CRM System
Output Type File
Output Location /BI/ftp/outgoing/CRM
Output File Name csg.csv
Output File Type CSV
Output Format ASCII
Output Character Set US-ASCII
Output Frequency Daily
CSV Specifics
Field Separator Comma (,)
Record Separator Carriage Return Line Feed
Quoting Character Double Quote ()
Escaping Character Double Quote ()
XML Specifics
Validation
Validation Location
Description/Purpose of File
This file is used to update the CRM system with the current market segment group and
score information
Data Definition
Field Name Source Field Name Mandatory?
Customer_id Customer.customer_id Yes
Market_Segment MarSeg.segment_name Yes
Segment_Score Custom_MarSeg_History.score Yes
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
Yes / No
Currently available from the Data Warehouse Yes
Limitations of current availability
Implementation Notes
Copyright
2006 Data Management & Warehousing. All rights reserved. Reproduction not permitted
without written authorisation. References to other companies and their products use
trademarks owned by the respective companies and are for reference purposes only.