1 / 42

TxDOT's AASHTO SiteManager Implementation as of October 2004

TxDOT's AASHTO SiteManager Implementation as of October 2004 . TxDOT AASHTO SiteManager Implementation in a nutshell. We began tracking our efforts in 1997. The initial estimate for full implementation was 1999.

maverick
Download Presentation

TxDOT's AASHTO SiteManager Implementation as of October 2004

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. TxDOT AASHTO SiteManager Implementation in a nutshell. • We began tracking our efforts in 1997. • 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. • So in 1999 we adjusted our project budget and our implementation completion date.

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

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

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

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

  7. TxDOT's AASHTO SiteManager Implementation as of October 2004 • SiteManager wasn’t really designed for Central Lab processing. • 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.

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

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

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

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

  12. EXISTING CONSTRUCTION RELATED APPLICATIONS

  13. THE PROBLEM : INTEGRATE SITEMANAGER INTO EXISTING APPLICATION ARCHITECTURE

  14. The Solution: SiteManager Interface Controller (SMIC) SiteManager Legacy S M I C Relational Hierarchical N E O N Sybase ADABAS

  15. RESULT: Application Integration and Happy Users

  16. Mainframe Payment Report

  17. Customized SM Payment Report

  18. SiteManager Custom Rpt Engine

  19. SiteManager Custom Rpt Engine

  20. Report Engine Monitor

  21. RESULT: Data Integrity and Happy Users

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

  23. Canned Financial Reports

  24. RESULT: Happy Contractors

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

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

More Related