Project Management

Requirements Unique to Data

Warehousing

By Alan Schlukbier

1
Introduction
 Project Managers are not using the
flexibility of PMBOK
 Most PM’s are unprepared for the fast
ramp-up at Mandate and unfamiliar with
the requirements needed before execution.
 The components are different and require
more analysis before mandate and project
commencement.

2
Project Management Issues:
 Project Mandate
 The Business Purpose
 SCOPE, SCOPE, SCOPE
 The Project Timeline
 High Resource Commitment

3
Overview of Data Warehouse
Repositor Model
y BI

ET Backup Recover Purge Archive

L y

Collaborativ
e

Review 4
Vocabulary
 Ontology = Model of knowledge for a bounded
region of interest expressed as concepts,
relationships, rules about their properties, and
rules that govern how concepts participate in
associations
 Data Warehouse = A repository for data. Many
experts define the data warehouse as a
centralized data store that feeds data into a series
of subject specific data stores called data marts
(Inmon). Others accept a broader definition of
the data warehouse as a collection of integrated
data marts (Kimball) with conformed dimensions
 Star Schema = Spreadsheet functionality using a
traditional relational database
5
Roles & Responsibilities
 Data Architect = Responsible for overall logical / physical design of data
warehouse

 Data Modeler = Logically & physically models the business/scientific

requirements of a subject area

 ETL Programmer = Responsible for the extraction, translation, and loading

of data into loosely-coupled relational data structures

 BI Analyst/Programmer = Responsible for implementing analytical

requirements using tools in a particular subject area

 Data Steward = Person responsible for maintaining a data element in a data

registry

 Data Governor = Responsible for the overall management (availability,

usability, integrity, and security of data employed in an enterprise

6
 Topic One – Mandate Purpose
 A data mart designed to analyze customers
 A data mart designed to analyze product sales
 A data mart designed to analyze product costs
 A data mart designed to analyze product
profitability

7
Sales Data Mart

8
Topic Two - Business Objective
 We need accurate daily sales from stores
 We need to compare monthly profitability
between products
 We need accurate sales trends over 5-year
periods

9
Topic Three - Scope
 We need a centralized data store for all
corporate financial reporting
 We need a centralized regulatory model to
satisfy all external privacy requirements
 We need more details on medical results
(medical lab)
 We need accurate shipping / ordering /
inventory details
10
Inmon ODS

11
 Underlying ERD Models
Prod uct T ype Qualifier Type
Produc t Type Code
Produc t Type Nam e Bus Qual Code
Produc t Type Description
Pro duct Hierarchy
identifies attribute Qualifier
Product Hierarchy ID
Business Qualifier referenced in / Bus Qual Code (FK)
Hierarchy Nam e Qualifier Table is used to Qualifer Set ID (FK)
ma y c hara c te rize Status Code
one or more / Status Date
may c onsist of Pro du ct Lin k
Qualifier Column constrain
must be c ha rac t erize d
by exac t ly o ne
Open Date
Hierarchy Source Name
o ne o r mo re / P roduc t Hierarc hy ID (FK) based on Qualifier Text
must be inc o rporat ed Child Product ID (FK )
in exac t ly one
P arent Product ID (F K)

P ro duct
Qualifer Set groups a set of
may represent c hild in
P roduct ID Qualifer Set ID
P roduct Type Code (FK )
one or more /
mus t inc lude Product
exac tly one (c hild)
P roduct S ource Name
Qualifier Set Name identifies the
Product ID
may re present parent in
o ne or more /
Qualifer Set Description applicability of
Analytical Term
must inc lude
e xac tly o ne (parent )
Product Type Code (FK) Analytical Term
Product Source Name Economic Term Code (FK)
P rod uct Type Code

Product ID (FK)
Qualifer Set ID (FK)
has Product Economic Term is valued in
Economic Term Code (FK) Value Number
Pro du ct D etail
Product ID (FK)
Pro du ct Su mmary P oin t Product ID (FK)
Product ID (FK)
Product Number (AK1.1)
Short Nam e
Product Sum mary Point ID (AK1.1) Economic Term Type Qualifiers Count
Short Nam e
Long Nam e
Desc ription
Long Nam e
Description
Economic Term Code characterizes
Open Date Open Date
Start Date
Status Code
Status Code Economic Term Name
Status Date
Status Date Economic Term Description

Party Type Equifax Summary Report E quifax Generic DAS Segment Equifax Trade Type may characteriz e
Equifax Trade S egment Equifax Custom Generic DAS Party Role
Party Type Code Credit Bureau Report ID (FK) may include Credit Bureau Report ID (FK ) Trade Ty pe Code one or more / Credit Bureau Report ID (FK) Credit Bureau Report ID (FK) Party ID (FK)
ex actly one / must be c haracteriz ed Trade Ty pe Code (FK) Trade Type Code (FK) Role Type Code (FK)
Cus tomer Reference Number Last 3 Months Inquiries Count may be augmented
Party Type Name mus t be reported Trade Ty pe Name by exactly one
Birth Year Last 6 Months Inquiries Count Open Trades Count by exactly one / may authorize
Party Type Desc ription
City Name for exactly one Last 12 Months Inquiries Count
Trade Ty pe Desc ript ion
Open Trades Total B alance Amount must augment
All Open Trades Count Agree me nt Event
exac tly one All Open Trades Total Balance Amount one or more / Relationship ID (FK )
Province Last Inquiry Age Open Trades Total High Credit A mount All Open Trades Total High Credit Amount
Pos tal Code Derogatory Public Records Count Open Trades Ut ilization Perc entage may be authorized
All Open Trades Utilization P ercentage may represent 3rd party E vent Datetime
Acc ount Number Last Derogatory P ublic Record Age Newes t Trade Age by exactly one
All Open Trades Pos it ive B alance Count in one or more / E vent Ty pe Code (FK)
Bankruptc y On File Indicator Oldest Trade Age
must involve
Third Party Re lationship
Subject Age Trades E ver 30 Days Count
may c harac t erize
Trades E ver 60 Days Count
Re lationship exactly one (3rd party) Relationship ID (FK) P art y ID (FK )
one or more / Relat ions hip ID Third Party ID (FK) Role Type Code (FK )
Trades E ver 90-120 Days Count
must be c harac terized may include Trades E ver Bad Debt Count
First Part y ID (FK ) Third Party Role Type Code (FK )
by e xac tly one one or more / Trades E ver Over 30 Day s Count may repres ent 2nd party
mus t be reported Trades Current P ast Due Count First Part y Role Type Code (FK )
for exact ly one Trades Currently 30 Days Count in one or m ore / S econd P arty ID (FK )
Trades Currently 60 Days Count mus t involve
Party Trades Currently 90-120 Day s Count exactly one (2nd party )
S econd P arty Role Type Code (FK)
P arty ID Trades Currently Bad Debt Count Relat ions hip Type Code (FK )
may participate in
Trades Currently Over 30 Days Count
P arty Type Code (FK ) Last 12 Months Trades 30 Days Count one or more /
Equifax Custom DAS Inquiry Type may represent 1s t party mus t involve
Equifax Custom DAS Inquiry Last 12 Months Trades 60 Days Count
in one or more /
Custom DAS Inquiry Code may define Last 12 Months Trades 90-120 Days Count exac tly one
Credit Bureau Report ID (FK) Last 12 Months Trades Bad Debt Count must i nvove
one or more / Cust om DAS Inquiry Code (FK)
Custom DAS Inquiry Name Last 12 Months Trades Over 30 Day s Count ex actl y one (1st party )
Party Type Code Custom DAS Inquiry Description must be defined
Last 24 Months Trades Satisfact ory Count
by ex ac tly one Inquiry Date
Ins titution Name Last 24 Months Trades 30 Days Count
Security Pled ge
may make Relations hip ID (FK)
Industry Code Last 24 Months Trades 60 Days Count Credit Facility Agre ement one or more /
Last 24 Months Trades 90-120 Days Count Third Party Role Type Code (FK )
Last 24 Months Trades Bad Debt Count Agreement ID (FK ) mus t be made
Personal Party may include may inc lude Third Party ID (FK )
Part y ID (FK) exac tly one /
Equifax Custom DAS Segment
one or more /
Last 24 Months Trades Over 30 Day s Count
Agreement Type Code (FK ) Agreement Clause Type by exac tly one Claus e Number (FK)
Credit Bureau Report ID (FK ) Last 3 Mont hs Trades Opened Count Agree men t Claus e Ty pe Cod e
must be reported mus t be inc luded Last 6 Mont hs Trades Opened Count Market ing Source Code (FK)
CIF Number for ex act ly one Las t 12 Months Inquiries Count in exact ly one may characteriz e
Close to CIF Number Last 12 Months Trades Opened Count Agree men t Claus eTy pe Name
Close Dat e Open Trades Positive Balance Count Agree men t Claus e Ty pe Des crip tion one or more / Agree me nt Clause
Marital Status Lifet ime Worst Rating Value must be characterized
Relationship ID (FK )
Dependents Count by exactly one Clause Number
may artic ulat e
Bank Direct or Indicat or
Gender Code one or more / Agreement Cla use Type Code (FK)
Language Code must be artic ulat ed
CIF Cus tomer Type Code Rela tionship Type Code Security Agree me nt
for exactly one
Spouse CIF Number Equifax Beacon Reject Type Equifax Beacon Segment Equifax Beacon Reason Type Relationship
Agre em ent Cla use Type Code ID (FK ) may consis t of
First Service Date
Equifax Beacon Reason
B eacon Reject Code Credit Bureau Report ID (FK) Beacon Reason Code Clause Number (FK ) one or more /
Customer P rivacy Option Code may clarify Credit Bureau Report ID (FK)
may explain Beacon Reason Code (FK) Secured Amount must be made
Privac y Disclosure Notice Indicat or B eacon Reject Name Class ification Indicator Beacon Reason Name one or more
one or more / for exactly one
Senior Indic at or B eacon Reject Alphabetic Code Beacon S core Value Beacon Reason Desc ription Full Liability Indicator
may be explained
Bankruptcy Dat e B eacon Reject Des cription by exac tly one Beacon Reject Code (FK) Security Type Security Support Indicator
Ever Bankrupt Indic at or may characterize
Sec urity Ty pe Code Legal Advice Indicator
Previous Loan Ex perience Indic ator may include may be clarified one or more /
Birth Year by one or more Sec urity Ty pe Name Security Type Code (FK)
exactly one / must have
Deceased Indicat or must be report ed
Privac y Option Code (FK) Sec urity Ty pe Description may initiate
for exactly one may journalize
exac tly one
one or m ore / Ag re ement Status
mus t be journalizedSmall Business Agree ment Relationship ID (FK )
may terminate
Equifax B NI Reject Type may explain Equifax BNI S egment E quifax B NI Reason Ty pe may c larify Equifax BNI R eason for exac tly one Relationship ID (FK )
exactly one Start Event Datetim e (FK)
one or more
BNI Rejec t Code one or more / Credit Bureau Report ID (FK) BNI Reason Code Credit Bureau Report ID (FK) CLASS Num Eve nt Type may charact eriz e Start Event Type Code (FK)
BNI Rejec t Name may be ex plained Classification Indic ator BNI Reason Name BNI Reason Code (FK) one or more /
by exact ly one Liability Number Event Type Code End Event Type Code (FK )
Credit Bureau Report Type BNI Rejec t Alphabetic Code BNI Sc ore Value BNI Reason Description must be charact eriz ed
Transit Event Type Name End Event Datetime (FK)
Credit Bureau Report Code
BNI Rejec t Descript ion BNI Reject Code (FK ) Marketing Source Type may offer Agre ement Marketing Fe ature Requested Amount by ex act ly one
Status Type Code (FK )
Marketing S ource Code Event Type Description
Credit Bureau Report Name may be evaluated may include may be clarified one or more Relationship ID (FK) A pproved A mount
Credit Bureau Report Desc ription by one or more / exact ly one / by one or more can be assigned to one or m ore / Marketing Feature Type Code (FK) A ccepted Amount
Marketing S ource Type Name Status Type may charac teri ze
mus t evaluate must be report ed has a
Marketing S ource Type Description may characterize A pplication Date one or more /
ex actly one for ex act ly one Offer B y S tatus Ty pe Code
Marketing Feature Type one or more
Offer Date
Credit Offer Amt mus t be charac teri zed
Marketi ng Feat ure Type Code Credit Offer Expiry Dt S tatus Ty pe Name by exac tly one
may c haract eriz e Pri mary Indicator
S ales Revenue S tatus Ty pe Des cription
one or more /
must be c haracterized
Agreement Type Marketi ng Feat ure Type Name Net Inc After Tax
by exact ly one A greement Type Code Marketi ng Feat ure Type Desc ripti on
Equifax Data Capture Segment may c haracterize Cash and Near Cas h
may include
one or more / Credit Bureau Report ID (FK) A greement Type Name one or more / B ank Depos it
must be reported Segment Number A greement Type Description must be c haracterized Non CIB C Debt
Credit Bureau Report for ex actly one
Account Number by exactly one W atch List Code
Credit Bureau Report ID Inst itution Name Classific ation Code
Party ID (FK ) (A K1.1) Reported Dat e Agreem ent Type Code Risk Rating
Credit Bureau Report Date (AK1.2) Equifax Pers onal Identifiers Credit Limit A mount Certificate Number
mus t be des cribed Opened Date
Credit Bureau Report Code (FK) by exactly one / Credit Bureau Report ID (FK) Cashflow Coverage
Estimated Balance A mount
mus t describe Last Name Estimated Past Due Amount PLC A greement Cashflow Coverage Date
ex actly one First Name Las t Activit y Date Relationship ID (FK ) Credit Score Ex ception Code
Middle Name Account Designator Code P ost Number ID
Credit Bureau Report Code Member Number Liability Number
S uffix
Trade Type Code Transit S end_3rd_P arty
S pouse Name
S ocial Insuranc e Number S end 3rd P arty Date
P os t Number ID
B irth Date CLA SS Number Update By
P ostal Code Update Date
P roc ess ing Region Code
P urpo se Type P urpose Description B LLI Insurance Num
Purpose Code may characterize B LLI Transit Num
A greement Staff Indicator
one or more / A ss et S ecurity Type B LLI Request Number
Purpose Code Name B LLI Coverage Amt
must be characterized A uthoriz ed Limit Amount
Purpose Code Des cription B ehaviour Score
by exactly one Open Date
B ehaviour Score Date
Created Date
Equifax Personal Identifiers SB Credit S core Value Decision Request Count
Credit B ureau Report ID (FK ) Decision Request Date
Credit S core Date
Loa n Category Type Renegotiate Increase or decrease
House Number Street Name Credit B ureau S core Value
Loan Category Code Last Renegotiate Date
may define one or more Credit B ureau S core Date
Equifax Summary Extension SB Loan Category Type Name Credit B ureau Code Last Renegotiate S tatus
Credit Bureau Report ID (FK) Last Renegotiate Reason
TDS R V alue
Archive Date
Equifax Personal Identifiers R etail TDS R Date Marketing Code
Flag 1, 2 Credit Bureau Report ID (FK) Original Risk Rating
P urpose Code (FK)
Hous e Number Loan Category Code (FK) Original Pos t Number ID
S treet Name S ecurity for Adjudic ation

12
Topic Four – Project Timeline
 Upfront analysis for DW projects is
substantial
 Depending on Scope, a complete ontology
is usually required before Mandate
 Enterprise Level Data Warehouse projects
may exist for years to do Data Quality,
Stewardship, and Governance before
project commencement to iteratively load
data warehouse

13
Time Line

14
Topic Five - Resources
 If tools are not in place, fully configured,
and personnel trained, do not start project
 Issues of purging, backup, recovery, and
archiving must be addressed at mandate
time
 Rules of availability of Operational
Resources, ETL programmers, and SME’s
must be addressed at Mandate time

15
Summary
 Much more preliminary analysis is
required to insure all tools, data quality,
stewardship, governance is in place and
capable to define a complete ontology
 PM’s must question and explore business
objectives in much more detail
 Mandates are vital
 Timelines will be skewed to analysis
 Resources must be heavily automated for
sustainable projects
16
Where to Get More Information
Books:
1. Berry, Michael J.A. and Linoff, Gordon S., Mastering Data Mining: The Art
and Science of Customer Relationship Management
2. Cook, Melissa A., Building Enterprise Information Architectures,
Reengineering Information Systems
3. English, Larry P., Improving Data Warehouse and Business Information
Quality
4. Inmon, W.H., Building the Data Warehouse, Data Architecture, the
Information Paradigm
5. Kimball, Ralph the Data Warehouse Toolkit, the Data Warehouse Lifecycle
Toolkit
6. Schlukbier, Alan C., Implementing Enterprise Data Warehousing: A Guide
for Executives
7. Simsion, Graeme, Data Modeling Essentials: Analysis, Design, and
Innovation
8. Zachman, John A., A Framework for Information Systems Architecture

17
 Where to Get More Information
(continued)
Magazines:
1. DMReview published and online

Consulting services:
1. Data Management Association, DAMA
2. The Data Warehouse Institute, TDWI
3. The Data Governance Institute
4. Schlukbier Consulting, www.schlukbier.com

18