PDIS- Technical Design Document

Director IT Business
Solutions:
IT Programs Manager:
IT Business Solutions
Manager:
Domain Architect:

Business Area:
Created By:
Creation Date:
Last Updated:
Version:

AMI Controller ETL High Level Design Information Management 1 CONFIDENTIALITY/SECURITY WARNING 2 DOCUMENT INFORMATION AND REVISION HISTORY Version Date Author(s) Revision Notes 0.2 2 Last Updated 11/15/2010 .2 FPL Confidential AMI Controller ETL High Level Design Version: 0.1 Initial Draft 0.

...................................9 5..................................3.............................................................................4 Run Frequency and Time ...........1.............................................................3.............................................................5 4.................................................................................................................................................................AMI Controller ETL High Level Design Information Management Table of Contents 1 CONFIDENTIALITY/SECURITY WARNING ......................................................................................................................................1............................................................................................................................................................3 Systems Overview: ..........................1 DESIGN CONSIDERATION ....................................................5 4 INBOUND SYNCHRONICATION APPROACH ...................................................................................................................................1 DESIGN CONSIDERATION ........1................................................ 10 8 CODE QUALITY AND TESTING ........................................................................................2 Base/Enrichment Table .................................................................2 DATA MODEL ..............................7 4.................................................3 Volumetric Analysis .......................................................................................................9 5..........................2 SIGN-OFF SHEET............2 2 DOCUMENT INFORMATION AND REVISION HISTORY ...3........................................3 ETL STRATEGY ...................................................................................................................................5 4...............................................................4 3...............................4 3.................................................................3 GLOSSARY .......................................4 3......................................................................................................................................................................9 5.........2.............................................5 4...........9 5.................9 6 SCHEDULING ..............................................................................2 Out Bound Data: .........2 3 Last Updated 11/15/2010 ...............................................6 4.4 3.............................................................. 10 8.........................................1 Master Tables .........................................................................6 4.......2 PURPOSE ...2 Source System Analysis......................................8 5 OUTBOUND SYNCHRONICATION APPROACH ........................1 Initial Load Strategy ................................. 11 APPENDIX .......................................................................................................................................2..4 3.......................1...2..................................3.....................................................................................................8 4....................................................................................................................3 Staging Area ......................................................................................1...........................................................................9 5.......................1 Data Requirements .................................................................2............................................... 10 7 CODING GUIDELINES .................1....2..............................................................8 4.................6 4........................................................................................................................................................................................................................................1 8....................................1.............6 4.....1 Data Requirements ..............................................6 4.....2 Source System Analysis – Data Model..........1 Inbound Data:.............................................................................................................................5 4........................................................................................2...4 Exception Handling .............................5 4...................1 OVERVIEW ............................................................................................................2 ETL STRATEGY ......3 Auditing Requirements.... 11 FPL Confidential AMI Controller ETL High Level Design Version: 0........................................4 3..............................................7 4...............................................................................................................................3 Run Frequency and Time .................................................................2 Incremental Load Strategy .2 3 INTRODUCTION ............

3 Systems Overview: Tiers / Layers ETL Platform Data Integration Tool Data Integration Tool Platform Data Base Platform Database Database Client Scheduling Utility Scheduler Testing Tools Test Management Technology / Tool Informatica PowerCenter 9.1 Inbound Data: 3.2 Purpose 3.2.AMI Controller ETL High Level Design Information Management 3 INTRODUCTION 3.1 Overview The purpose of the PDIS is to… Current Process: Purpose of the Project and Benefits: Scope of the Project: The scope of the project is broadly classified into following functionalities: System Objectives: 3.2.2 4 Last Updated 11/15/2010 .2.2 Out Bound Data: 3.1 UNIX Teradata 13.5.10 with Bitemporal Capability HP Data Quality Management FPL Confidential AMI Controller ETL High Level Design Version: 0.

3 Glossary Term Definition ETL Extraction Transformation and Loading SIEDW SIM STG 4 4. These points will play a vital role in addressing Data Quality and Data Integration Process Performance.1.1.2 Source System Analysis 4.1 Data Requirements Assumptions: 4.1.1 INBOUND SYNCHRONICATION APPROACH Design Consideration The overall ETL process design has evolved by considering the following points.AMI Controller ETL High Level Design Information Management 3.2 Remarks 5 Last Updated 11/15/2010 .3 Volumetric Analysis The volumetric analysis has been performed for both Initial and Incremental feeds as mentioned below: Table Object1 Object2 Object3 Object4 Object5 Initial FPL Confidential AMI Controller ETL High Level Design Version: 0. 4.

2 Run Frequency and Time Data Model 4.2 Base/Enrichment Table 4.1 Master Tables 4.4 4.1.2.2.2.3 Staging Area FPL Confidential AMI Controller ETL High Level Design Version: 0.AMI Controller ETL High Level Design Information Management 4.2 6 Last Updated 11/15/2010 .

3.2 Source Stage 7 Base Last Updated 11/15/2010 .1 ETL Strategy Initial Load Strategy Dependency: Frequency of Run: Once Expected Volume: Initial load will be performed in the following Steps as mentioned below. Source o Master Extraction Criteria: Source o Source Stage Base Extraction Criteria: Source o Remarks Source Stage Base Extraction Criteria: Source FPL Confidential AMI Controller ETL High Level Design Version: 0.3 4.AMI Controller ETL High Level Design Information Management 4.

Source  Source Stage Base Step3: Track and Retrieve changes to Customer related enrichment attributes.3.3 Auditing Requirements Mention the Audit details.AMI Controller ETL High Level Design Information Management 4. FPL Confidential AMI Controller ETL High Level Design Version: 0... 4.2 Incremental Load Strategy Dependency: Frequency of Run: Daily/Nightly/Weekly Expected Volume: Driver for Delta Extraction: ETL ID 1 2  ETL Name ETL Start DTTM ETL End DTTM Run Status Step1: Track and Retrieve changes. Source Source Stage Base SIEDW_ETL_PRCS_CONTROL  Step2: Track and Retrieve changes.2 8 Last Updated 11/15/2010 . Source Source Stage Base By Object 4.4 Exception Handling Standard ETL related Exception Handling and Notification needs to be followed.3. This will be elaborated more in LLD..3.

1.1.2 Source System Analysis – Data Model .3 5. These points will play a vital role.AMI Controller ETL High Level Design Information Management 5 5. The process control table should look similar to the below mentioned table.1. Parent Table 5. ETL ID ETL Map Source Table # Of Days To Purge # Days to Archive Files 1 2 The following Steps will be followed to achieve the Purging and Archiving: FPL Confidential AMI Controller ETL High Level Design Version: 0.2 9 Last Updated 11/15/2010 . 5.1 OUTBOUND SYNCHRONICATION APPROACH Design Consideration The overall ETL process design has evolved by considering the following points.1 Data Requirements 5.2 Affected Child Table Relationship Run Frequency and Time ETL Strategy The Purging and Archiving process will be driven from a Process Control table.

AMI Controller ETL High Level Design Information Management 6 SCHEDULING 7 CODING GUIDELINES The ETL process will follow the standard coding guidelines followed at MLIT and UST-GLOBAL and brings in any Best Practices as and when required. 8 CODE QUALITY AND TESTING  .2 10 Last Updated 11/15/2010 . FPL Confidential AMI Controller ETL High Level Design Version: 0. A link to the Coding and Code Review check list will be provided.

2 Appendix FPL Confidential AMI Controller ETL High Level Design Version: 0.2 11 Last Updated 11/15/2010 .AMI Controller ETL High Level Design Information Management APPROVALS 8.0 of this document. Project Manager: DATE Architect: DATE DATE Project Team Member: 8.1 Sign-off Sheet Sign-off on the version x.

Sign up to vote on this title
UsefulNot useful