2. Trns*port Data Model Unification Joe Pugh Virginia Department of Transportation Peggy Leight Info Tech Inc 11/06/05

3. Scope Identify potential data model changes that will help facilitate a unified data model approach VDOT Strategic Objectives –Review current processes and identify redundant data –Identify opportunities for expanding use of Trns*port in the agency –Facilitate meta-data driven and service oriented architecture Data Model Unification

4. Data Management Concepts Key Concepts Conceptual Data Model Metadata Web Services

5. Current Data Structures Database

6. Duplicate Data

7. Data Flow Diagram

8. Future Data Flow

9. “Add Project” Function Today

10. “Add Project” Web Service

11. NGT Conceptual Data Model

12. Conceptual Data Model Implementation To Date

13. Evaluating Entities 100% 75% 50% 25% 100% 66% 33% 100% 50% 25% Entities Fund package Items Projects Most of the work is up front

14. Conceptual Web Services Architecture

15. NGT Services-Oriented Architecture

16. VDOT Trnsport Data Integration Trnsport Financial Management System Project Scheduling Data Warehouse Enterprise Metadata Repository Roadway Network System Environmental System Program Planning Asset Management Project Dashboard

17. VDOT Data Issues/ NGT Potential Solutions Issues: 1.PES Generate Bid Based Prices process to allow different bid history files for estimating. 2.Ability to enter in a quantity on the construction side and have the system generate unit price. Set boundaries for pricing. 3.Ability to generate multiple bid histories for each county, region, cost group, district. Etc. Potential Solution: A single estimation engine which can be run at any point in the workflow from estimation through construction. Estimation would allow for selection of price based on multiple criteria.

18. VDOT Issues and Potential Solutions cont. Issue: The ability to handle generic fields differently as appropriate to various tables. Potential Solution: Allow each agency to add however many generic fields of any type to any base table.

19. VDOT Issues and Potential Solutions cont. Issues: The ability to generate a totally electronic proposal. Improve the interface between PES and Expedite Ability to determine vendors by district based on zip code, address, longitude/ latitude, etc. Potential Solutions: Yet to be determined (tell us what you need)

20. Data Analysis Observations To improve the structure of the unified data model: Entity Unification (alignment based on related business rules) –Functional Data (Project, Item, Attachment, etc.) –Reference Data (Item Master, Fund Master, People/Vendor, etc.) Streamlining (Consolidate data reducing number of tables and/or columns) –Long Text Descriptions –Code Tables –Location Data type attributes –Attribute/Entity Relocation (e.g., Letting Proposal with Proposal)

21. Consistency in Attributes –Length and type –Code Tables Versioning and Status –Snapshots (e.g., improved addendum processing, change history) –Active/Inactive Status (e.g., Code Tables) –Date/Time/UserID Stamp General Data Clean Up and Reduction –Crosswalk Tables –Temporary Tables for client/server environment –Duplicate Data (e.g., SiteManager data in BAMS/DSS) General Organization, Flexibility and Efficiency –Generic Fields and Attributes –Storage of Calculated Attributes Data Analysis Observations

22. Recommendations Expose NGT working data models to end-users and set-up process to accept feedback throughout development Expose current metadata to end users and include the ability for this information to be accessed outside of NGT.

23. Next Steps 1.Expand analysis to other modules 2.Involve other states in the process 3.Propose recommendations for consideration into NGT backlog https://www.cloverleaf.net/support/forum

24. Remember “Virginia is for Lovers”