1 / 15

Presented by Tony Bianchi, Project Manager AASHTO September 21, 2006

AASHTOWare Program Overview to the Safety Data Systems Task Group of the Safety Management Subcommittee. Presented by Tony Bianchi, Project Manager AASHTO September 21, 2006. Overview. Reason for presentation AASHTOWare Background Fundamental principals How is the process managed?

ronan-hood
Download Presentation

Presented by Tony Bianchi, Project Manager AASHTO September 21, 2006

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. AASHTOWareProgram Overview to the Safety Data Systems Task Group of the Safety Management Subcommittee Presented by Tony Bianchi, Project Manager AASHTO September 21, 2006

  2. Overview • Reason for presentation • AASHTOWare Background • Fundamental principals • How is the process managed? • Who uses AASHTOWare • Next Steps

  3. Safety Related Project Potential • $1.4M federal grant under Section 5501 of SAFETEA-LU with dollar for dollar match requirement • TSIMS Status • Potential for Task Force to identify need and work with AASHTOWare staff to apply for federal grant funds and develop project proposal

  4. What is AASHTOWare? A technical service program that allows member agencies to pool resources to develop, support and maintain software, at substantially lowercosts than custom/individual development. • Applicable throughout software lifecycle; • Geared to DOT production environments; • Based on AASHTO Standards; • Managed at all levels by DOT personnel.

  5. AASHTOWareFundamental Principles Common Needs Flexibility • Pooling resources to produce significant cost savings • Software developed “by users for users” • Best practices approach • Focus on universal requirements – meet 90% of common needs • Build in flexibility – allow software customization to meet unique needs (i.e. the remaining 10%) Value Customer Satisfaction

  6. How is the AASHTOWare Process Managed? • Full-time AASHTO Staff project management • DOT volunteer subject matter experts and IT professionals appointed to product task force to guide software developmentperformed by contractors • Task Forces meet with developers 3-5 times per year to oversee activities and monitor development • Decisions by consensus & majority rules. • Task Forces develop annual product work plans and strategic directions • Special Committee on Joint Development (SCOJD) provides sets overall AASHTOWare program policies and strategic direction

  7. How is the AASHTOWare Process Managed? - continued • Project participation fees– typically collected one time, up-front, at beginning of new development effort; • Thereafter, product license fees collected annually – cover all on-going expenses on yearly basis • Operated as not-for-profit activity. All expenses, including task force travel, and staff labor is paid out of license revenue; each product must be self-supporting • On average, 80-90% of license fee is “reinvested” into software product through contracted services • Special Committee on Joint Development provides oversight • Full-time AASHTO Staff project management

  8. AASHTOWare Management Organization

  9. Who Uses AASHTOWare? • 50 State DOTs, plus District of Columbia, Puerto Rico and FHWA license one or more AASHTOWare products • 2 Canadian Provinces and several foreign countries • Numerous counties, cities, universities, and consulting firms

  10. Revenue Over the last 15 years, AASHTOWare revenue has grown from $2 Million to more than $24 Million annually.

  11. Current Application Areas • Construction Project Lifecycle Management • Trns·port - Modular suite of products • Bridges • Pontis - Bridge Management • Virtis - Bridge Analysis and Load Rating • Opis - Bridge Design and Analysis • Roadway • DARWin - Pavement Design and Analysis • SDMS - Survey Data Collection and Management

  12. Future Application Areas • Asset Management • AssetManager NT – Network analysis tool • AssetManager PT – Program analysis tool • AssetManager “XT” – … possible series “toolkit” • Right-of-Way Relocation

  13. Things to Consider • Software requirements could be based on research already completed, presuming agreement among stakeholders • On-going mechanism for support, maintenance and enhancement is necessary to ensure software’s long-term viability • Continued funding needed for architectural and functional improvements • Maximum impact possible if tools are bundled with implementation assistance and support when delivered • Service Unit concept allows purchase through AASHTO of fixed increments of contractor support for agency-specific needs • AASHTOWare program offers proven mechanism for cost-effective long-term support, maintenance and enhancement of software for state DOTs

  14. Safety Related Project Potential • Commitment from Subcommittee to “champion” and sponsor a proposed AASHTOWare “Project” proposal for software tool development and implementation • At least 5 volunteers - to serve on “Steering Committee” to guide development of a project proposal and other pre-solicitation activities • A successful project solicitation with a minimum of 10-12 DOT participants

  15. Need More Information? Contact: Tony Bianchi, Project Manager AASHTO tbianchi@aashto.org 202-624-5821

More Related