Scribd
Upload
6 views6 pages

Case Study Slides

Uploaded by

piyush gupta
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
6 views6 pages

Case Study Slides

Uploaded by

piyush gupta
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 6

ETL Case Study

Home Healthcare Products and Services


• Client is America's leading provider of integrated home
healthcare products and services, including oxygen and
respiratory equipment, home-delivered respiratory
medications and a broad range of home infusion therapies
and medical equipment.

• Client has 450 branches and 30 pharmacy locations


nationwide

• Client serves over 1.6 million patients annually throughout


all 50 states.

• Client strategy is to position itself in the marketplace as the


low cost, high quality provider of a broad range of home
healthcare services to managed care and Medicare
customers

• In July 2006, company initiated a major technology


restructuring process. The project was named Symphony. A
part of the project was to implement an enterprise wide
business intelligence solution for all lines of business. This
was to give the company a uniformed and consolidated view
of their data and help the executive team to make better
decision about the business

1
Problem Statement
1. Multiple source systems with different kind of data from different line of business

2. Data extraction from multiple source systems with multiple (23) branch database schemas

3. 23 branches’ data residing in 23 different systems were to be integrated and loaded into Enterprise Data Warehouse

4. Complex rules to process customer dimensional data to eliminate the duplicates

5. Multiple processing rules to address standardization

2
Infosys Understanding

• Infosys understood that a significant amount of data modeling work was already done by the client team. It was our
understanding that Client had already put logical & physical data model in place for the project

• Infosys understood that the data in central repository provided a single “source of truth” of operational reporting
requirements and users could access information on an on-demand basis

• Infosys proposed to execute the project on a Time & Material basis and to execute the engagement in an elapsed
timeframe of sixteen weeks. This was an initial estimate based on our current understanding of the scope and the initial
effort estimation could have varied because of the following reasons:
 Possibility of data model changes and additional scalable data
 Data sources could be different or more than anticipated
 Extensive data quality & data cleansing mechanism (as per the standards laid down by the data architecture group)
 Complexity in ETL design

3
Infosys Approach
Solution Definition Phase Execution Phase

• Understand ETL high level • Define ETL strategy


business requirements • Design and develop extraction, cleansing and
• Understand scope of project loading processes
• Study source systems • ETL Mapping development
• Study DM and POC • Identify and resolve data quality issues
• Identify data quality issues and • Define & execute Test Cases/Test Plans
create a roadmap • SIT/UAT Support
• Create implementation plan for • Define post-execution handover process
next step • Project Management
OBJECTIVES

2-4 Weeks 12 Weeks

• The execution was done in an iterative manner


• During the project, Infosys aligned with the DW methodologies and the processes laid down by client, and worked
in close collaboration with the existing project team

4
Architecture

5
Project Scope
• ETL Solution Definition
• High level source system study
• Review and evaluate existing Data Model
• ETL Requirements Gathering & Analysis
• Design
• Design high-level ETL strategy
• Validate source-target mapping
• Specifications for transformation rules
• Define the loading processes
• Execution
• Development of extraction and loading processes
• Testing for Data Quality issues
• Testing for Performance issues
• Designing of Test Cases, Test Plans
• UAT support

You might also like