Project Planning
Any system implementation requires planning, but careful preparation and understanding of the “moving parts” is especially critical when installing a client/server-based application. A sample Project Plan is shown below; this should serve as a starting point and guide for planning your Data Mart implementation and is not meant to be complete.
Sample Project Plan
| Task # | Task Description | Duration |
|---|---|---|
| 0 | Installation Prerequisites | 4d |
| Establish Initial Environment | ||
| Set Up DBMS | ||
| Other (See Attached List) | ||
| 1 | Project Management | 8w |
| 2 | Assemble Client Project Team | 1d |
| Team Leader, Application Administrator, System/Network Administrator, Database Administrator, Report Designer, Trainers, Source System Experts, Performance Specialist | ||
| 3 | Initial Product Delivery & Installation | 1d |
| Install Data Mart sample reports and sample database | ||
| Establish 3-5 Users & Test Accounts | ||
| 4 | Conduct Acceptance Test on sample data | 2d |
| 5 | Training | 1w |
| Admin. & Technical Training (3 Days) | ||
| User Training | ||
| Other (As Required), e.g., Data Mart Advanced Reports, Oracle DBMS, Data Mart Data Steward, Data Mart Uploaders. | ||
| 6 | ETL Design & analysis | 3w |
| Investment data requirement analysis | 3d | |
| Data mapping from 1 accounting system to Data Mart | 3d | |
| Data transformation | 2d | |
| Performance Data Requirements Analysis | 2d | |
| Data Conversion Requirement Analysis | 2d | |
| Detailed Specification | 3d | |
| Development | 4d | |
| 7 | ETL Programming & Testing | 2w |
| Portfolios | 1d | |
| Security Master | 2d | |
| Positions | 1d | |
| Lots | 2d | |
| Cash Activities | 1d | |
| Transactions | 1d | |
| Portfolio Composites | 1d | |
| Develop Ops Procedures & Unit Test | 1d | |
| Low Volume Test | 2d | |
| Full Volume Test | 2d | |
| 8 | Reports & Queries | 3w |
| Analysis, Design & Development; e.g., Management Reports, Account Folder Set up, Start-up Folder Definitions, etc. | ||
| RDL report design | 0.5d per report | |
| Proclarity Data Analytics Report | 1d per report | |
| Client report assembly | 1w | |
| 9 | Create Live Production Environment | 2d |
| Network Configuration & Set Up | ||
| Data Mart "Server" Configuration & Set Up | ||
| Data Mart Database Setup | ||
| 10 | Integrated Production Test | 2d |
| Low Volume Integrated Test | ||
| Volume Production Test | ||
| 11 | Conversion | 3d |
| Extract data from older system | 2d | |
| Extract data from older system | 1d |
Data Mapping
A key element of the installation process is the “mapping” of data from the source system(s) to Data Mart table formats. Data Mart provides a large number of user-definable fields in addition to those explicitly defined in the database.
Prior to beginning the data mapping exercise, it is necessary for your installation team to study and become familiar with the data models of source data systems.
The data mapping team should consist of the Team Leader, Application Administrator, a business-line participant, and at least one Source System Expert. Once they become familiar with the Data Model, they should compare the structure and contents of the Data Model against the model in Data Mart by using the data mapping spreadsheet. These spreadsheets contain the names and formats of the target tables which will be filled via interface with the source systems.
The Data Mart Environments
One of the tasks during the planning phase for the installation is deciding how many versions or copies of the Data Mart database to install and at what times. In a typical installation, three separate databases are installed at the client site:
- Test (Initial Test)
- Pilot (Production Test)
- Production
Moving meta-data between Data Mart environments is a complex process. Data Agent has developed our own custom stored procedure to move meta-data for Data Mart loaders, Data Mart report components, business calendars and custom data fields from one Data Mart environment to another.
