1. TxDOT's AASHTO SiteManager Implementation as of October 2004 TxDOT's AASHTO SiteManager Implementation as of October 2004

2. TxDOT AASHTO SiteManager Implementation in a nutshell. TxDOT AASHTO SiteManager Implementation in a nutshell. We began tracking our efforts in 1997. We began tracking our efforts in 1997. The initial estimate for full implementation was 1999. The initial estimate for full implementation was 1999. In 1998 created a project plan but didn’t adjust for the time spent creating the plan. In 1998 created a project plan but didn’t adjust for the time spent creating the plan. So in 1999 we adjusted our project budget and our implementation completion date. So in 1999 we adjusted our project budget and our implementation completion date.

3. TxDOT AASHTO SiteManager Implementation in a nutshell. TxDOT AASHTO SiteManager Implementation in a nutshell. Line Speeds Line Speeds Business Process Issues Business Process Issues Material Issues Material Issues Legacy System Interface Issues Legacy System Interface Issues Training Coordination Issues Training Coordination Issues

5. TxDOT AASHTO SiteManager Implementation in a nutshell. TxDOT AASHTO SiteManager Implementation in a nutshell. In 2000 TxDOT kicked off Texan2000. In 2000 TxDOT kicked off Texan2000. Business issue resolution. Business issue resolution. Materials plugin development. Materials plugin development. Interface design & development. Interface design & development. The initial plan one district a month. The initial plan one district a month. BUT some districts were really BIG. BUT some districts were really BIG. So we made some adjustments. So we made some adjustments.

6. TxDOT AASHTO SiteManager Implementation in a nutshell. TxDOT AASHTO SiteManager Implementation in a nutshell. Three years on the road would be tough. Three years on the road would be tough. In 2001 began training and implementation in the districts. In 2001 began training and implementation in the districts. Then we realized we needed to upgrade. Then we realized we needed to upgrade. So we made more adjustments. So we made more adjustments. Close to the end we sprinted. Close to the end we sprinted. March 2004 we completed the full SiteManager implementation. March 2004 we completed the full SiteManager implementation.

7. TxDOT AASHTO SiteManager Implementation in a nutshell. TxDOT AASHTO SiteManager Implementation in a nutshell. A static system was important during training but we still made a few changes. A static system was important during training but we still made a few changes. 70+ Plugin spreadsheets 70+ Plugin spreadsheets 4 small Plugin applications 4 small Plugin applications 28 Custom Reports 28 Custom Reports Report Server Report Server Plus a few code modifications to keep the lights on. Plus a few code modifications to keep the lights on.

9. TxDOT's AASHTO SiteManager Implementation as of October 2004 TxDOT's AASHTO SiteManager Implementation as of October 2004 SiteManager wasn’t really designed for Central Lab processing. SiteManager wasn’t really designed for Central Lab processing. So we developed a Library Information Management System (LIMS) on the side. So we developed a Library Information Management System (LIMS) on the side. We also realized SiteManager didn’t address all our DBE certification requirements so we started looking. We also realized SiteManager didn’t address all our DBE certification requirements so we started looking.

11. As of October 2004 As of October 2004 Total bid amount for all active contracts is $7,606,144,540.82 Total bid amount for all active contracts is $7,606,144,540.82 Total change orders to those contracts is 202,643,357.28 Total change orders to those contracts is 202,643,357.28 Grand Total of $7,808,787,898.10 Grand Total of $7,808,787,898.10 July payments = $246,073,293.63 July payments = $246,073,293.63 August payments = $316,280,759.58 August payments = $316,280,759.58 September payments= $278,042,204.56 September payments= $278,042,204.56

12. As of October 2004 As of October 2004 1603 active contracts, 1603 active contracts, 159 completed contracts, 159 completed contracts, 146 pending contracts in SiteManager. 146 pending contracts in SiteManager. From August 21 through September 24 we: From August 21 through September 24 we: –processed 936 progress estimates, –43 final payments, –3 supplemental estimates, –produced 19,453 custom reports.

13. As of October 2004 As of October 2004 There are 3197 active SiteManager users There are 3197 active SiteManager users In 25 Districts with In 25 Districts with 120 Area Offices with 120 Area Offices with Countless Field Offices Countless Field Offices

17. Future Plans Microsoft Terminal Server for everyone! Microsoft Terminal Server for everyone! Sybase to Oracle Sybase to Oracle DSS Upgrade DSS Upgrade SitePad / SitePad Materials SitePad / SitePad Materials LIMS Integration LIMS Integration

21. CIS CBSCMCSCTSFIMSMCSSMSSWSUSASDCISUSPSUSFUVD EXISTING CONSTRUCTION RELATED APPLICATIONS

22. THE PROBLEM : INTEGRATE SITEMANAGER INTO EXISTING APPLICATION ARCHITECTURE

23. The Solution: SiteManager Interface Controller (SMIC)

24. RESULT: Application Integration and Happy Users

25. Mainframe Payment Report

26. Customized SM Payment Report

27. SiteManager Custom Rpt Engine

29. Report Engine Monitor

30. RESULT: Data Integrity and Happy Users

31. SiteManager Financial Interface Start with Estfin.txt file Start with Estfin.txt file Add more information from SiteManager Add more information from SiteManager Add more information from legacy applications Add more information from legacy applications Fold, Spindle, and Mutilate Fold, Spindle, and Mutilate Send to State Comptroller and TxDOT accounting systems Send to State Comptroller and TxDOT accounting systems

32. Canned Financial Reports

33. RESULT: Happy Contractors

37. SitePad SiteManager Server Synchronization Allow SitePad to Synchronize with the SiteManager Server. Allow SitePad to Synchronize with the SiteManager Server. Retain the Existing SitePad Synchronization Process. Retain the Existing SitePad Synchronization Process. Retain the Current Standalone/SitePad Functionality Retain the Current Standalone/SitePad Functionality

42. Copy and rename 5 NVOs. Copy and rename 5 NVOs. Alter the Current Transaction (l_sqlca) to the Server Database (sqlca). Alter the Current Transaction (l_sqlca) to the Server Database (sqlca). Copy and Rename the Existing SitePad Synchronization Window. Copy and Rename the Existing SitePad Synchronization Window. Create Node and Window Definitions for the New Server Side Icon. Create Node and Window Definitions for the New Server Side Icon. How To Get There