EPM 303: Data Warehousing and Data Mining EVMS Data

K.C. Norseth

L-3 Communications

Data Warehousing and Data Mining EVMS DataWhile we have great tools for reporting basic EVMS such and wInsight and MPM, there is a need to do more reporting in different ways. This presentation is intended to describe how we warehouse EVMS data from both wInsight, MPM, project, and other systems for reporting data across contracts.

Agenda System Description Import Service Service Logging Problems Encountered Lessons Learned

Key Takeaways Design of a EVMS Data Warehouse

Components Processes Advantages / examples of reporting

Loading EVMS Data Warehouse Automation

L-3 CSW Contract Statistics 300 Programs maintained in EVMS Average > 1000 work packages/ planning packages per program

Platform MS SQL Server 2005, MS SQL Server 2008

All Databases Windows Server 2003

MPM Server MPM Related Services

Share Point User Interface to data Portal layout

Main EVMS ApplicationsCOTS MPM wInsight MS Project

Internal Developed (WEB) Electronic Baseline Planning System (EBPS) ETC Update Portals and dashboards required for program management needs.

Interfaces for other systems to show Earned Value on their work.

Why We Have Data Warehouses

Some typical EVMS types of reporting needs met by a data warehouse Reporting across multiple programs By Organization By business areas By people

IPT Managers VP’s

By time

Data Warehouses provide a method for FAST reporting and analysis across multiple dimensions. Data warehouses are optimized for speed of reporting Data is aggregated by typical reporting levels and combinations

Data Warehouses provide historical data snapshots not normally available on a typical database.

Data Warehouses usually use reporting tools that users can create reports on their own without I.T. intervention.

What We Store in Our Data Warehouses MPM Data wInsight Data Other EVMS data Financial Data

System Diagram

What We Import Into MPM

• Electronic Baseline Planning System• BCWP• Actuals• Charge number status• MS Project

MPM Import / Export Processes

All systems auto-import data into MPM.

Database loading Process

Reported Warehouse Key component of database is a highly de-normalized wInsight database

De-normalized for speed of reporting Ease of building ad-hoc reports.

wInsight data snapshot by period WBS at that point in time is also stored

Snapshot of additional information from MPM and other data not normally stored in wInsight.

Data is loaded into warehouse at time of load to wInsight database Warehouse is updated if key information is changed in wInsight. Customer reported status on each period so users can see if we are done with

the period or still working on the report.

Automated Triggers for wInsight to Update Reported Warehouse

Changes in Period Status Publevel can be used

Program Status Changes Other key markers for program

The ETL (Extract, Transform, Load) process for the reported warehouse is a stored procedure that is called on demand or automatically.

Reported Warehouse Schema(wInsight)

MPM Warehouse

MPM Database is loaded on demand by custom web page. Data is normalized on load

A second MPM database is maintained in a warehouse for speed and indexing requirements

MPM warehouse is loaded nightly or on demand This allows the cost analyst to not interfere with reporting that live

ETL for warehouse checks for the tables to be updated and will shut down if they are being updated by user.

Data is replicated to MPM warehouse nightly if any changes are made to the program. MPM does not have an incremental update capability

MPM Database Schema

ProjectData

GlobalsMPM

Security

WBS OBS

Calendar

EVMS(Work Package)

EVMS(Resource)

Milestones

ReportsMain product used to generate reports in Business Objects Reports are created by users Optimization of reports is done by IT.

Conclusion

Questions

www.twitter.com/deltek

www.facebook.com/deltekinc

www.linkedin.com/company/163414

www.youtube.com/user/deltekinc

Contact InformationK.C. Norseth

Kenyon.c.norseth@l-3com.com