Global Business Services

Business Intelligence Practice

Customer Interaction Analysis

Project
Conceptual Data Integration Model
Sample Deliverable
Version 1.0
01/27/2005

Trademarks
Trademarked names may appear throughout this document. Rather than list the names
and entities that own the trademarks or insert a trademark symbol with each mention of
the trademarked name, the names are used only for editorial purposes and to the benefit
of the trademark owner with no intention of infringing upon that trademark.

Revision History
Date
01/27/2006

Version
V 1.0

Revised By
IBM Consultant

Page i

Description
Initial Version

Conceptual Data Integration Model

Table of Contents
1. DOCUMENT OVERVIEW.................................................................................3
1.1. CONTEXT...............................................................................................................3
1.2. DOCUMENT AUDIENCE............................................................................................3
1.3. PROJECT OVERVIEW..............................................................................................4

2. SOURCE SUBJECT AREAS...........................................................................5

2.1. INITIAL VOLUMETRICS BY SOURCE SYSTEM.............................................................5

3. REUSABLE COMPONENTS REVIEW............................................................6

4. DEFINE INITIAL BUSINESS RULES..............................................................7
5. REVIEW EXISTING DATA QUALITY INFORMATION....................................8
6. EXPECTED TARGET STORES.......................................................................9
7. CONCEPTUAL DATA INTEGRATION MODEL.............................................10

Page ii

Conceptual Data Integration Model

1. Document Overview
This document has been developed by the Customer Interaction Analysis Data Integration
Thread project for the Financial Services Client Enterprise Data Warehouse Program.
This deliverable was developed from the IBM Business Intelligence Methodology deliverables,
leveraging the IBM Banking Data Warehouse Model (BDWM), using the Customer Lifetime
Value Application Solution Template.
BDWM Application Solution Templates (ASTs) provide a template of the data requirements
for non-reporting applications for which the BDW is expected to deliver data, for example
Customer Lifetime Value.

1.1. Context
A Conceptual Data Integration Model is a partial implementation-free representation of
the data integration requirements for the proposed system that will serve as a basis for
determining how they are to be satisfied.
At this stage it is only necessary to identify the major conceptual processes in order to
fully understand the ramifications of the users' requirements for data integration in terms
of the feasibility of the project. Steps for this task include reviewing:

The existing data stores should be identified for potential as

sources.
The components in the Data Integration Architecture should
been reviewed for leverage and reuse for the potential project.
Whether the existing Data Quality Control found in the
Metadata Repository for Data Integration Processes should be assessed to
determine whether there are potential reuse opportunities.
Identifying potential target data stores in which data will reside
for a predefined period as necessitated by business rules.

1.2. Document Audience

The primary audience includes:
o
o
o
o
o

Business Analysts
Data Integration Architects
Data Integration Analysts
Data Integration Designers
Metadata Specialists

These are the individuals who have the responsibility for envisioning, modeling, and,
structuring the data integration architecture and processes.

Page 3

Conceptual Data Integration Model

1.3. Project Overview

The major objectives of the Financial Services Client Customer Interaction Analysis
Project include:

Develop a reporting architecture to provide interactive analytics to loan, credit risk, and
finance users leveraging an Analytics Package.
Develop the Customer Interaction Analysis Data Mart database to support the analytic
requirements.
Develop the core Data Warehouse tables to supply the data to the Customer Interaction
Analysis Data Mart database
Develop the Customer Operational Data Store database as a staging area to consolidate
customer information for operational reporting and to populate the Data Warehouse
tables
Develop the data integration processes required to load and update the Customer
Operational Data Store, core Data Warehouse tables, as well as the Customer
Interaction Analysis Data Mart database

Page 4

Conceptual Data Integration Model

2. Source Subject Areas

Definition:

This section details the systems intended to be used for source in

the Data Integration Architecture.

Source System

Potential Subject Areas

Hogan Teller System

Customer Daily Download

Customer Interaction Daily Download
Customer
Customer Interaction

APS Loan Processes

2.1. Initial Volumetrics by Source System

Definition:

This section details the high-level file sizing from the source
system in terms of number of files, volumes, and timing.

System

Description

HOGAN

Hogan Teller System

Number
of Source
Files
4

Number
of
Records

Volume

Frequency

Type

7G

Daily

full

5G

Daily

full

7,000,000
APS

Loan Processing

5
100,000

Total Files
Total Space

Platform
Mainframe Flat
Files
Mainframe IMS

9
12G

Page 5

Conceptual Data Integration Model

3. Reusable Components Review

Definition:

This section reviews the existing Data Integration Repository for

reusable extract/subscribe, data quality, transforms, and/or
load/publish.

In the review of the existing Organizational Data Integration Repository the following
components:
Existing Reusable Components
Data Integration
Component Layer

Component Name

Description

Extract/Subscribe
None Available
Data Quality-Technical
Error Handling
Component

Standard error handling process

Data Quality-Business
None Available
Transform
None Available
Load/Publish
None Available

Page 6

Conceptual Data Integration Model

4. Initial Business Rules

Definition:

This section captures from initial requirements any directional or

transformation business rules.

Known Business Rules

Business Rule

Type (Data Quality /

Transformation)

Description

CUSTOMER and
SEASON Staging Files
are Joined and
Transformed

Transformation

For analysis purposes, season information will be

aggregated into a single table.

Page 7

Conceptual Data Integration Model

5. Review existing Data Quality Information

Definition:

This section reviews from an existing metadata repository or Data

Quality Workbook data quality information useful for the intended
project.

6.

Page 8

Conceptual Data Integration Model

7. Expected Target Stores

Definition:

This section describes the target stores associated with the

application.

Target Stores

Table Name

1 Customer ODS
CUSTOMER
CUSTOMER_INTERACTI
2 Enterprise Data Warehouse
CUSTOMER
GEOGRAPHIC_AREA
MEAS_PERIOD
GEO_AREA_TO_CUST
CHANNEL
SEASON
CUST_INT_HIST
3. CIA Data Mart
CUSTOMER
MEAS_PERIOD
CHANNEL
GEOGRAPHIC_AREA
CUST_INT_ANALYSIS
CUST_PERF_STAT
PRIM_PROD_ARGMT
ARGMT_PRIM_PAY_TYP

Page 9

Conceptual Data Integration Model

8. Conceptual Data Integration Model

Definition:

This section portrays an implementation-free representation

of the data integration requirements for the proposed system
that will serve as a basis for determining how they are to be
satisfied.

Page 10

Conceptual Data Integration Model