1. 2005 Trnsport Task Force Report Trnsport Users Group Conference November 6, 2005 Daytona Beach, Florida Paul Neumann, Colorado DOT Chair, Trnsport Task Force

2. Presentation Outline Trnsport Task Force Overview Strategic Directions Maintenance and Support Enhancements & New Development Conclusion

3. Trnsport Task Force Overview

4. Trnsport Mission The mission for Trnsport is to serve the operational and executive management information needs of the transportation agency associated with the development and management of construction projects. Trnsport Long Range Work Plan (LRWP) http://www.cloverleaf.net

5. Trnsport Licensees Alaska Hawaii New Brunswick 39 State Agencies, 1 Canadian Province, FHWA Federal Lands Highways, District of Columbia DOT, Pennsylvania Turnpike Trnsport Implementation Status http://www.cloverleaf.net

6. Trnsport Task Force Members Paul Neumann, Colorado, Chair Roger Bierbaum, Iowa, Vice Chair Jim Johnson, Florida Loren Lemmen, Michigan Todd Bergland, Minnesota Denis Glascock, Missouri Tim Lindberg, South Carolina Trnsport Task Force http://www.cloverleaf.net

7. Task Force Meeting Participants Regular participants at our meetings: –Chuck Conley, AASHTO Staff –Shirley Daugherty, Nebraska, SCOJD Liaison –John Morden, Florida, T&AA Liaison –Jim Ferguson, Nebraska, TUG Chair –Tom Rothrock, Info Tech –Margaret Andraka, Info Tech –Teresa Franklin, Info Tech Trnsport Task Force Meeting Minutes http://www.cloverleaf.net

8. Task Force Responsibilities Strategic Direction –Define long term vision –Establish product objectives –Determine annual goals –Develop marketing plan AASHTOWare ® Policies, Guidelines and Procedures http://www.aashtoware.org

9. Task Force Responsibilities Product Management –Prepare 5-year Long Range Work Plan (LRWP) –Establish annual budget –Prepare annual Maintenance, Support and Enhancement (MSE) work plan –Manage/direct contractor’s MSE operations –Determine operating platforms –Evaluate need for new modules AASHTOWare ® Policies, Guidelines and Procedures http://www.aashtoware.org

10. Trnsport Task Force Operations Five meetings each year (plus the TUG) Other meetings as required –Presentations to potential licensees –SCOJD/Task Force Chairs meeting Numerous conference calls Countless e-mails Subgroups Technical Review Teams (TRTs) Trnsport Task Force Operations http://www.cloverleaf.net

11. Trnsport Task Force Positions Seeking individuals who are interested in serving on the Task Force One opening per year, on average Submit resumes anytime Must have approval from agency

12. Strategic Directions

13. Strategic Goals Business Goals –Align with the AASHTOWare ® strategic direction –Eliminate unnecessary boundaries between and within systems –Bring Trnsport’s value to a larger audience Executives, non-DOT personnel, mobile access –Reduce agency Total Cost of Ownership (TCO) Implementation, support, integration

14. Strategic Goals Technical and Architectural Goals –Provide architecture that meets the needs of current and future customers Web-enabled, with loosely coupled tiers –Build a consistent, unified data model –Enable easier integration with other systems

15. Achieving Strategic Goals Web-enabling has been a strategic goal for several years –But simply web-enabling doesn’t go far enough –Even with a web interface, current architecture would be too expensive to enhance and adapt to new technologies –As technology matured, it became clear that a rewrite was necessary

16. Next Generation Trnsport (NGT) More than web enabling Web services architecture (using.NET) Unification of data model, business rules, security administration, look and feel Easier to deploy and support Easier integration with other systems Supported by AASHTOWare ® Strategic Plan and IT survey

17. Maintenance and Support

18. Maintenance and Support Focus Quality of releases –More important than quantity –Improving installation and deployment –Lowest possible number of errors Communications –Posting more information on Cloverleaf –More frequent notifications to users

19. Trnsport Modification Requests (TMRs) Can be either maintenance or enhancement Maintenance TMR priorities are verified by the TTF –Urgent – can’t perform critical business function –Critical – prevents implementation or upgrade –High – major inconvenience –Medium – minor inconvenience –Low – nuisance

20. Maintenance During NGT Development To maximize funds available for NGT: –Only Urgent and Critical maintenance TMRs will automatically be funded for correction –TTF will evaluate high priority maintenance TMRs on a case-by-case basis to determine whether a correction will be provided TMR Policy http://www.cloverleaf.net

21. Maintenance During NGT Development To maximize funds available for NGT: –Medium and low priority maintenance TMRs won’t be corrected unless TTF approves an exception –No formal TMR review this fiscal year TMR Policy http://www.cloverleaf.net

22. Platform and Release Support Challenges –Trnsport must not be either too far ahead or too far behind licensee environments –There is a limited amount of money available for maintenance, support and enhancements –The more platforms and releases we support, the more it costs

23. Client/Server Platform Support Supported July 1, 2005 –Windows Server 2003 Supported July 1, 2006 –Oracle 10g Trnsport Platform Component Status http://www.cloverleaf.net

24. Client/Server Platform Support Support ending on June 30, 2006 –SitePad on Palm OS –Oracle 8i –DB2 7.2 –Pocket PC 2002 Support ending on June 30, 2007 –Sybase Adaptive Server Enterprise –Windows 2000 Trnsport Platform Component Status http://www.cloverleaf.net

25. Release Support Release versions become unsupported 12 months after the next full release becomes available

26. Warranty Provisions Regression failures (things that used to work) –Functionality working in the June 2005 and later releases is warranted in future releases for as long as the release is supported, up to 24 months (except for technology upgrades) Initial release of NGT will have a 300-day warranty

27. Enhancements & New Development

28. Enhancement & New Development Process Input –Trnsport Users Group ballot –Strategic direction –Licensee funding Managed by Task Force –TRT appointed whenever practical

29. Delivered Since Last Conference Delivered December 2004 –Trnsport Test Suite 1.0a –BAMS/DSS Edit Database –LAS, BAMS/DSS SiteXchange Interfaces –LAS – New Data Validations for LASINIT –LAS – Attach Proposals to a Letting –Integrate Object Store 2 into CES, PES, LAS, CAS, BAMS/DSS

30. Delivered Since Last Conference Delivered December 2004 –CAS – SITETIME Record Will Not Accept a Negative Value –Rewrite RTF User Guide –Add RTF to PDF Output in CES, PES, LAS, CAS, SiteManager Delivered March 2005 –Expedite x.509 Certificate Authority Enhancement –Expedite PGP Toolkit upgrade

31. Delivered Since Last Conference Delivered March 2005 –SRS for Reference File Sharing (ties into Next Generation Trnsport data model unification) Delivered June 2005 –FieldNet 2.0 –Projects Should Be Locked in PES When Proposal Checked Out –PES/LAS Add Tabbed Folder Functionality

32. Delivered Since Last Conference Delivered June 2005 –CES Enhancement Bundle Display web-based scatter plot and price basis for bid histories Copy tasks at the item level, including copying to an existing item Add bridge ID and other bridge information

33. Delivered Since Last Conference Delivered June 2005 –9 BAMS/DSS HREG TMRs Documentation on how regressions and averages are generated for CES Documentation on bid history files for CES and Estimator Option to use date work began, rather than letting date, for bid history calculations

34. Delivered Since Last Conference Delivered June 2005 –9 BAMS/DSS HREG TMRs New report to identify items/models with positive quantity coefficients. Include information on why reverse curve is generated. New report to compare average and regression prices to ensure that they’re consistent with each other Provide more control of how date is used in the HREG model

35. Delivered Since Last Conference Delivered June 2005 –9 BAMS/DSS HREG TMRs Provide options for both averages and regressions to control the exclusion of outliers from the bid history calculations Add an option for the period of time for the regression model to be different (longer) than that for the averages Create an model profile that contains a FREEPROP select on the CNDISTR field

36. Delivered Since Last Conference Delivered June 2005 –Add Generic Fields Item List, Vendor, Vendor Address tables –Estimator Enhancements Undo/Redo function requirements and design Build Projects in Item Number Order Add Filter to Bid History Catalog

37. Delivered Since Last Conference Delivered June 2005 –FieldManager Enhancements Assign Items to Subcontractors FieldManager – Contract Display –Modifications to LAS Pass to SiteManager process

38. Delivered Since Last Conference Delivered July 2005 –Next Generation Trnsport Mobilization Effort Project Methodology Document Technical Standards and Tools Document Test Driven Approach Document User Input Planning Document

39. Delivered Since Last Conference Delivered August 2005 –SiteManager 3.6a Sample Information (Big 15) Sample Information Window Access Lock Superpave Mix Design Enhancement Search Window - Item code to display with line item number Integrate new GetTemplate SMSI Lock Sample, Generic Field Func., & Attachments

40. Delivered Since Last Conference Delivered September 2005 –Expedite 5.6a Sub Folders and Conditional Bid Withdrawal Add Generics to print sequences Add support for radio buttons

41. Enhancements During NGT Development To maximize funds available for NGT: –TTF will not fund enhancements to the AASHTO-owned modules during NGT development, unless TTF determines an exception is warranted for the benefit of the Trnsport community Ballot is still very important –TTF will use as an indicator of priorities for NGT development Agencies may still fund TMRs

42. Current Enhancement Efforts TRACER, Phase 1 –New module – Cost-based parametric estimation –Nearly ready for delivery Estimator –6836 – ‘Undo/Redo’ function

43. Current Enhancement Efforts FieldManager –6299 – Add Report Customization Functionality in FieldManager –8776 – Enable Site Time tracking in FieldBook IDRs SiteManager –8135 – Enhancements to Stockpile Materials (allow update of conversion factor)

44. Current New Development Effort Next Generation Trnsport, Phase 1 –Development began in July 2005 –Functionality equivalent to client/server PES/LAS –Build necessary architecture –Begin reengineering data model –Agile development methodology –Continuous oversight by TTF –Agency migration impact assessment

45. Next Generation Trnsport Roadmap AASHTO Fiscal Year PhaseIncrement05-0606-0707-0808-0909-10 1Proposal, Letting and Award 2Bid Analysis 3Materials Management 3Construction and Materials Field Reporting 4Contract Monitoring and Reporting 5Construction Management 6Cost-based and Parametric Estimation This plan is tentative, and is subject to change due to factors such as funding availability.

46. Pending New Development Civil Rights and Labor Management System (CRLMS) –To be built as a new module using NGT architecture NGT Materials preliminary work TRACER, Phase 2

47. Conclusion

48. We’re Making Progress Trnsport continues to grow, adding new functionality and progressing with new technologies Remains a robust suite of software modules Current licensees adding modules Other states and countries are looking at Trnsport to meet their needs Next Generation Trnsport development underway

49. How You Can Help Stay informed –Information on Cloverleaf –Task Force meeting minutes Keep the Task Force informed –Cloverleaf NGT Message Board –Keep agency status reports accurate –Complete surveys distributed by TTF Keep up with current releases

50. It’s All About Cooperation By continuing to work together, we can insure that Trnsport will fulfill its mission –Trnsport Users Group –Users Group Board of Directors –Trnsport Task Force –AASHTO Staff –Trnsport Contractor

51. 2005 Trnsport Task Force Report For further information, contact any Trnsport Task Force member