If you are a consumer of project information this presentation is directed at you. The Project Control Data Warehouse is an 'open' type project and an instance of the ODWM. Thanks for taking a look!
1. PCDW for Owners
Automated Systems Alliance, Inc
Copyright 2009 by Automated Systems Alliance, Inc
2. PCDW for Owners
You are an Owner if ... Your
organization uses or could use the
content of a data warehouse to help
run its business…
Copyright 2009 by Automated Systems Alliance, Inc
3. PCDW
• What is PCDW?
• What is the PCDW ‘Technology’?
• Why will PCDW be adopted?
• How does the Owner benefit?
• How do you get the Technology?
• What are your Project Control needs?
Copyright 2009 by Automated Systems Alliance, Inc
4. What is PCDW?
Project Control Data Warehouse (PCDW)
• …A container for project information
that is optimized for reporting…
• … A mechanism for improving
transparency on high risk projects…
• ...An ‘Open Source’ like product that
can be shared…in whole or in part…
Copyright 2009 by Automated Systems Alliance, Inc
5. What is PCDW?
…A container for project information that is
optimized for reporting…
Copyright 2009 by Automated Systems Alliance, Inc
6. What is PCDW?
… A mechanism for improving transparency
on high risk projects…
Copyright 2009 by Automated Systems Alliance, Inc
7. What is PCDW?
...An ‘Open Source’ like product that can be
shared…in whole or in part…
Copyright 2009 by Automated Systems Alliance, Inc
8. What is PCDW ‘Technology’?
…It is a lateral shift in thinking about how to
deliver data warehouses in general…
Copyright 2009 by Automated Systems Alliance, Inc
9. What is PCDW ‘Technology’?
…That shift is toward commoditization…
Copyright 2009 by Automated Systems Alliance, Inc
10. What is PCDW ‘Technology’?
…The reason this hasn’t happened yet…The
‘Open’ paradox…
Copyright 2009 by Automated Systems Alliance, Inc
11. Why will PCDW be Adopted?
…New Players…New Markets…New Products
for a vibrant but stagnant DW industry…
Copyright 2009 by Automated Systems Alliance, Inc
12. Why will PCDW be Adopted?
…Automated System Alliance’s Role…The
PCDW is the first system of its kind…
Copyright 2009 by Automated Systems Alliance, Inc
13. How does the Owner Benefit?
…Better Project Visibility…
Copyright 2009 by Automated Systems Alliance, Inc
14. How does the Owner Benefit?
…Lower Cost…There isn’t a cost for the PCDW but there
also isn’t any free lunch…We’ve just changed the
price of the lunch…
Copyright 2009 by Automated Systems Alliance, Inc
15. How does the Owner Benefit?
…Faster Delivery…We’ve reduced the implementation
time and reduced DW project failure risk…
Copyright 2009 by Automated Systems Alliance, Inc
16. How does the Owner Benefit?
…Flexibility…Choose your environment…
Copyright 2009 by Automated Systems Alliance, Inc
17. How does the Owner Benefit?
…Flexibility…High end solutions…
Copyright 2009 by Automated Systems Alliance, Inc
18. How does the Owner Benefit?
…Flexibility…Low end solutions…
Copyright 2009 by Automated Systems Alliance, Inc
19. How does the Owner Benefit?
…Flexibility…Consolidated Reporting…
Copyright 2009 by Automated Systems Alliance, Inc
20. How does the Owner Benefit?
…Flexibility…Acquisitions…
Copyright 2009 by Automated Systems Alliance, Inc
21. How does the Owner Benefit?
…Flexibility…Legacy Systems…
Copyright 2009 by Automated Systems Alliance, Inc
22. How does the Owner Benefit?
Summary
• One Project truth…many points of view
• Overall cost reduction ($$$$ to $)
• Reduced implementation time (12 to 2 months)
• Environment flexibility
• New project tracking opportunities earlier in the
development process
• Reduced time and cost in acquisitions
• End Legacy systems and their costs
Copyright 2009 by Automated Systems Alliance, Inc
23. How do you get the PCDW?
• Go to http://www.asaservices.biz
• Download the model, instructions and license.
• Install … you are done.
• Download other supporting documentation.
There are other resources on the site.
• PCDW will be available before March 1, 2009
• The License…
Copyright 2009 by Automated Systems Alliance, Inc
24. What do you need?
• Does this technology address
some of your project needs?
• What needs aren’t covered?
• What kinds of concerns do you
have about the model, licensing,
availability of other solutions?
Copyright 2009 by Automated Systems Alliance, Inc
25. What do you need?
Project Control Data Warehouse Profile
• DATA WAREHOUSE NAME: PCDW – Project Control Data Warehouse
• PCDW MISSION: Answer the question, “How is the project going?”, from many points of view.
• DISTRIBUTION: Global
• INDUSTRY(s) SERVED: All
• FUCTIONAL AREA: Project Control
• PCDW OS PLATFORMS: Constrained by the database selection
• PCDW DATABASES: Microsoft SQL, Oracle, DB2, Access, MySQL, PHP and other SQL92 Compliant databases.
• PCDW ACCESS: ODBC, OLE, or Native Access drivers.
• PCDW STRUCTUE: Dimensional built using relational tools
• PCDW OLAP SUPPORT: None
• PCDW BI: Not Included. Owner’s choice. May be constrained by the database selection
• ETL: Not Included. Owner’s choice. Dependent on source(s)
• STAGING TABLES: Not Included (assumed to be part of the ETL process).
• PCDW ARCHICTURE: Snowflake
• PCDW TIME PERSPECTIVE: Current Data Summaries
• PCDW UPDATE: Project Shift or Greater
• DATA SOURCE(S): Required: Accounting Systems. Optional: Scheduling, Project Management, Time Keeping.
• DATA RESOURCE: Consider using as an organizational resource for select data (Project List, Standard Cost Codes, Facility List, etc.)
• PCDW GRAIN: Transaction Level in the Fact table
• PCDW SECURITY ISSUES: Payroll and Contract transactions in the fact table
• PCDW SLOWLY CHANGING DIMENSIONS: Rare (see time perspective)
• PCDW HIERARCHIES: Several Ragged and Fixed (Project, Cost Code, WBS, etc.)
• LANGUAGE: English (will add additional languages based on community interest)
• LICENSE: License table identifying ownership (required)
• TABLE NOTATION: General table type code plus full name
• FIELD NOTATION: Bi-Camel verbose with table association prefix and suffix attachments for primary, candidate, and foreign keys.
• DEVELOPMENT and PRODUCTION: Accommodation made for development and production versions of the Warehouse.
• DATA MARTS: Not Included. Can be Developed.
• DATA FEDERATION: Source table included to allow consolidation of data from multiple sites.
• CHANGE CONTROL: Change control model to be determined. Initial version to be identified as 0.0 with changes identified as 0.n until
the first beta release.
• PCDW DATA INDEXES: None
• PCDW DATA STORED PROCEEDURES: None
• PCDW DATA VIEWS: None
• PCDW DATA ALIAS: None Provided
Copyright 2009 by Automated Systems Alliance, Inc
26. What do you need?
Project Control Data Warehouse Select Topical Dimensions
• PROJECT: Project Name, ID, Location, Description, Planned/Actual Start/End
Dates, AFE ref, etc
• SOURCE: Data Source Tracking
• WBS: Work Breakdown Structure Tracking
• COST CODING: Cost partitioning
• PEOPLE: Address book for employees, contractors, others.
• SUPPLIERS: Organizations providing services, materials, or both.
• TAX TABLES: Tables for maintaining taxing jurisdictions and rates.
• CONTRACTS: Purchase Orders, Work Orders, Service Contracts, Blanket
Orders, etc.
• AP/AR: Payables and receivables.
• FACILITIES: Asset tracking
• PAYROLL: Employee and Contractor Timekeeping
• BUDGETING: Project budgeting and allocation
• BANKING: Bank information, check tracking, and cash flow projection
• RECEIVING: Incurred cost for materials and services
• SCHEDULE: Start/End, duration, resource loading, etc.
• CRAFT: Tracking by labor type.
• TIME: All elements tracked over time.
Copyright 2009 by Automated Systems Alliance, Inc
27. ASA
You don’t have to use ASA’s services to use the
PCDW or ODWM models
But..
We would be happy if you would consider us for
implementations, training/workshops, support,
or specialized ETL development…
Contact:
Cliff Brandon (303)601-0648
http://www.asaservices.biz
Copyright 2009 by Automated Systems Alliance, Inc