Making AssetManager an AASHTOWare Product

313 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
313
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Here to talk about how we can transition the software tools developed under NCHRP 20-57 to AASHTOWare. These tools were presented to the Subcommittee at the meeting in Philadelphia last September. There appears to be sufficient interest in making these tools AASHTOWare products and this subcommittee is the natural choice for guiding this effort. Presentation is organized to give a little background on the AASHTOWare program and process for those who are less familiar with it, and summarize the results of the NCHRP 20-57 project. Then talk a little bit about the considerations needed to ensure successful transition of the tools from research to practice, and finally outline what we think is needed under “Next Steps”.
  • Challenge of standardizing around best practice; single approach– while still allowing flexibility for unique requirements. Issue of performance measures- Benchmarking standards – AASHTO’s role in standards development
  • The management structure ensures that AASHTOWare: Supports specific DOT business processes Is enhanced in accordance with DOT priorities Product license fees are established by task forces to meet long and short-term product work plan resource requirements Will always be software developed by DOT users for DOT users…
  • The AASHTOWare program operates as a non-profit activity. The revenue collected goes to cover all program expenses. Software development reinvestment = 85-90% (through contracted services) Administrative Expenses = 10-15% (includes staff salary and travel expense reimbursement for task force members) Growth attributed to a combination of new software products developed in the last 15 years and the popularity of “On-site Service” units as a mechanism to access software consulting services through the AASHTO contract.
  • Trns·port modules include: Preconstruction: BAMS/DSS, PES, LAS, CAS, CES, and a new development of a cost estimation tool known as “Tracer”. Construction Management: SiteManager, SitePad, FieldManager, FieldPad, etc… Pontis and Trns·port could be used to leverage the development of additional Asset Management tools.
  • AssetManager NT: Tool to explore impacts of various budgets on network performance over the long term Enables tradeoffs across asset types, geographic areas, and system subnetworks Quick-response what-if tool that integrates and analyzes results from existing management systems Example questions What happens if we move 20% of bridge funds to pavement program? What happens to non-NHS facilities if we focus 75% of resources on the NHS? AssetManager PT: Tool to support short-range (1 to 3 years) program tradeoff decisions Allows users to shift project candidates in/out of programs and view aggregated impacts and costs Proof-of-concept – confirm that data requirements are reasonable, refine functional design and suggest architecture Example questions What happens to pavement condition if a new major capacity project is substituted for resurfacing projects? What happens if we shift funds from pavement preservation into bridge rehabilitation?
  • Both tool are functional, working software tools, however– neither are really true “production oriented” systems. NCHRP has made great progress in focusing on the development of software tools--- still need mechanism for long-term maintenance and support like any other asset. Share in the cost of initial capital outlay associated with new product area. Point: Rely on data from existing DOT management systems The use of robots and the development of additional robots is a consideration as the tools move from research to practice--- it is also addressed in the project proposal outlined later in this presentation. Important Point: Highly configurable based on specific DOT parameters and practices As is often the case, with “flexibility” comes a certain degree of complexity. This is important because it relates directly to the degree of assistance that may be initially required to get the tools “up and running”. This will be addressed in the project proposal outlined later in this presentation. Also Important: AssetManager PT – prototype (based on an Excel spreadsheet) This prototype needs further development – architectural and functional improvement to be considered truly “production” oriented product. The project proposal addresses this need too.
  • At conclusion of 20-57 project, NCHRP will distribute both AssetManager tools to all state DOTs Without on-going software support, maintenance, and enhancement – tools will have limited impact on asset management practice Both tools rely on data from existing management systems. Robots have been developed for Pontis and HERS-ST. Data from other systems will either require robot development or manual interface. In addition, architectural and functional enhancements have been identified and will continue to be identified by users as the systems are introduced and implemented within DOTs. Software will need a mechanism (a permanent “home”) for lifecycle support. While continued funding could be requested from NCHRP for additional specific development objectives, NCHRP is by definition a research program and does not provide a mechanism for software lifecycle support and maintenance. The AASHTOWare program offers proven mechanism (a permanent “home”) for cost-effective long-term support, maintenance and enhancement The AASHTOWare program offers proven mechanism for cost-effective long-term support, maintenance and enhancement that will help these tools connect with existing asset management data and systems , and add value to existing tools, and help fill some of the current gaps in asset management practice.
  • Experience has shown that a “critical mass” of 10-15 states is needed to be successful in the long-run.
  • Based on preliminary draft work plan, the estimated cost per participant based on 10 state DOTs is between $75,000 to $100,000.
  • Making AssetManager an AASHTOWare Product

    1. 1. Making AssetManager an AASHTOWare Product Presented to AASHTO Subcommittee on Asset Management Presented by Jan Edwards, Project Director AASHTO January 11, 2005
    2. 2. <ul><li>AASHTOWare Background </li></ul><ul><li>NCHRP 20-57 Results </li></ul><ul><li>Transition from research to implementation - things to consider… </li></ul><ul><li>What’s Needed </li></ul><ul><li>Next Steps </li></ul>Presentation Overview
    3. 3. What is AASHTOWare? <ul><li>A technical service program that allows member agencies to pool resources to develop, support and maintain software, at substantially lower costs than custom development. </li></ul><ul><ul><ul><li>Applicable throughout software lifecycle; </li></ul></ul></ul><ul><ul><ul><li>Geared to DOT production environments </li></ul></ul></ul><ul><ul><ul><li>Based on AASHTO Standards; </li></ul></ul></ul><ul><ul><ul><li>Managed at all levels by DOT personnel. </li></ul></ul></ul>
    4. 4. <ul><li>Pooling resources to produce significant cost savings </li></ul><ul><li>Software developed “ by users for users” </li></ul><ul><li>Best practices approach </li></ul><ul><li>Focus on universal requirements – meet 90% of common needs </li></ul><ul><li>Build in flexibility – allow software customization to meet unique needs (i.e. the remaining 10%) </li></ul>AASHTOWare Fundamental Principles Customer Satisfaction Flexibility Value Common Needs
    5. 5. <ul><li>DOT subject matter experts and IT professionals guide software development performed by contractors </li></ul><ul><li>Decisions by consensus & majority rules. </li></ul><ul><li>All expenses, including task force travel, paid out of license revenue </li></ul><ul><li>Special Committee on Joint Development provides oversight </li></ul><ul><li>Full-time AASHTO Staff project management </li></ul>How is the AASHTOWare Process Managed?
    6. 6. Management Organization
    7. 7. Who Uses AASHTOWare? <ul><li>50 State DOTs, plus District of Columbia, Puerto Rico and FHWA </li></ul><ul><li>2 Canadian Provinces and several foreign countries </li></ul><ul><li>Numerous counties, cities, universities, and consulting firms </li></ul>
    8. 8. Revenue <ul><li>Over the last 15 years, AASHTOWare revenue has grown from $2 Million to more than $20 Million annually. </li></ul>
    9. 9. Application Areas <ul><li>Construction Project Lifecycle Management </li></ul><ul><ul><ul><li>Trns·port - Modular suite of products </li></ul></ul></ul><ul><li>Bridges </li></ul><ul><ul><ul><li>Pontis - Bridge Management </li></ul></ul></ul><ul><ul><ul><li>Virtis - Bridge Analysis and Load Rating </li></ul></ul></ul><ul><ul><ul><li>Opis - Bridge Design and Analysis </li></ul></ul></ul><ul><li>Roadway </li></ul><ul><ul><ul><li>DARWin - Pavement Design and Analysis </li></ul></ul></ul><ul><ul><ul><li>SDMS - Survey Data Collection and Management </li></ul></ul></ul><ul><li>Safety </li></ul><ul><ul><ul><li>TSIMS – Transportation Safety Information Management </li></ul></ul></ul><ul><li>Asset Management </li></ul><ul><ul><ul><li>AssetManager NT – Network analysis tool </li></ul></ul></ul><ul><ul><ul><li>AssetManager PT – Program analysis tool </li></ul></ul></ul><ul><ul><ul><li>AssetManager “XT” – … possible series “toolkit” </li></ul></ul></ul><ul><ul><ul><li>Maintenance/Asset Management System – new effort with SOM </li></ul></ul></ul>
    10. 10. NCHRP 20-57 Analytic Tools for Asset Management -Results Program Tool (AssetManager PT) Long-Term (up to 20 years) Analysis based on Aggregate Performance Results from Management Systems Supports Resource Allocation Tradeoffs Network Tool (AssetManager NT) Short-Term (1-3 years) Analysis based on Candidate Projects Supports Understanding of Program Adjustment Consequences & Tradeoffs Flexible Definitions of Performance Measures Flexible Ways of Dividing up the System – based on Geographic & Network Classes Both Show Outcomes for Different Investment Levels and Allocations Across Assets and Portions of the System
    11. 11. NCHRP 20-57 Analytic Tools for Asset Management <ul><li>AssetManager NT – stand-alone desktop application </li></ul><ul><li>AssetManager PT – functional prototype (based on an Excel spreadsheet) </li></ul><ul><li>Both: </li></ul><ul><ul><li>Rely on data from existing DOT management systems; robots developed for Pontis & HERS-ST </li></ul></ul><ul><ul><li>Highly configurable based on specific DOT parameters and practices </li></ul></ul>
    12. 12. Transition from Research to Practice: Considerations <ul><li>NCHRP will distribute tools to all state DOTs </li></ul><ul><li>Without on-going support mechanism, what will happen to 20-57 tools? </li></ul><ul><li>Maximum impact possible if tools are bundled with implementation assistance and support. </li></ul><ul><li>Continued funding needed for architectural and functional improvements </li></ul><ul><li>AASHTOWare program offers proven mechanism for cost-effective long-term support, maintenance and enhancement </li></ul>
    13. 13. AssetManager as an AASHTOWare Product – What’s Needed? <ul><li>Commitment from Subcommittee to “champion” AssetManager implementation and sponsor the proposed AASHTOWare project </li></ul><ul><li>Project proposal for tool implementation </li></ul><ul><li>5 volunteers - to serve on Steering Committee to guide pre-solicitation activities </li></ul><ul><li>A successful project solicitation with a minimum of 10 DOT participants </li></ul>
    14. 14. What’s Needed? Suggested Project Approach <ul><li>Phase I: </li></ul><ul><ul><li>Goal: Form community of early adopters. </li></ul></ul><ul><ul><li>Actions: Implementation and Support </li></ul></ul><ul><ul><li>Timeframe - 12 months </li></ul></ul><ul><li>Phase II: </li></ul><ul><ul><li>Goal: Architectural & Functional Enhancement </li></ul></ul><ul><ul><li>Actions: On-going support and maintenance, select database for PT, port both tools to .NET, add functional improvements prioritized by users </li></ul></ul><ul><ul><li>Timeframe – 12 to 15 months </li></ul></ul><ul><li>Initially, solicit funds for Phase I only </li></ul><ul><li>Define Phase II as part of first phase work plan, and then solicit </li></ul>
    15. 15. <ul><li>Develop AssetManager Tutorial </li></ul><ul><li>Develop Technical Manual </li></ul><ul><li>2 On-site Visits by Cambridge Systematics to each participating DOT, including a CEO Workshop </li></ul><ul><li>Telephone support </li></ul><ul><li>Maintenance – fix critical errors; log routine errors for second phase correction </li></ul><ul><li>Optional Service Units </li></ul><ul><ul><li>Develop additional robots </li></ul></ul><ul><li>Survey participants and establish prioritized enhancement list </li></ul><ul><li>Develop work plan for Phase II </li></ul>What’s Needed? Suggested Phase I Work Plan
    16. 16. Next Steps – AASHTOWare Project Initiation <ul><li>Develop Phase 1 project proposal and solicitation package </li></ul><ul><li>Review and approval by the Special Committee on Joint Development </li></ul><ul><li>Send to AASHTO membership and other potential project sponsors </li></ul><ul><li>If solicitation is successful, proceed with project </li></ul><ul><li>Appoint AssetManager Project Task Force </li></ul><ul><li>Start work! </li></ul>
    17. 17. <ul><li>Endorsement of proposed project by Asset Management Subcommittee </li></ul><ul><li>5 volunteers </li></ul><ul><li>Finalize work plan and submit for SCOJD approval </li></ul><ul><li>Reauthorizatio n </li></ul><ul><li>Mail solicitation to all AASHTO members – target June 2005 </li></ul>Next Steps
    18. 18. Questions?

    ×