Making AssetManager an AASHTOWare Product

1
Making AssetManageran AASHTOWare Product

• Presented to
• AASHTO Subcommittee on Asset Management
• Presented by
• Jan Edwards, Project Director
• AASHTO
• January 11, 2005

2
Presentation Overview

• AASHTOWare Background
• NCHRP 20-57 Results
• Transition from research to implementation -
  things to consider
• Whats Needed
• Next Steps

3
What is AASHTOWare?

• A technical service program that allows
  member agencies to pool resources to develop,
  support and maintain software, at substantially
  lower costs than custom development.
• Applicable throughout software lifecycle
• Geared to DOT production environments
• Based on AASHTO Standards
• Managed at all levels by DOT personnel.

4
AASHTOWareFundamental Principles
Flexibility
Common Needs

• 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
5
How is the AASHTOWare Process Managed?

• DOT subject matter experts and IT professionals
  guide software development performed by
  contractors
• Decisions by consensus majority rules.
• All expenses, including task force travel, paid
  out of license revenue
• Special Committee on Joint Development provides
  oversight
• Full-time AASHTO Staff project management

6
Management Organization
7
Who Uses AASHTOWare?

• 50 State DOTs, plus District of Columbia, Puerto
  Rico and FHWA
• 2 Canadian Provinces and several foreign
  countries
• Numerous counties, cities, universities, and
  consulting firms

8
Revenue

• Over the last 15 years, AASHTOWare revenue has
  grown from 2 Million to more than 20 Million
  annually.

9
Application Areas

• Construction Project Lifecycle Management
• Trnsport - 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
• Safety
• TSIMS Transportation Safety Information
  Management
• Asset Management
• AssetManager NT Network analysis tool
• AssetManager PT Program analysis tool
• AssetManager XT possible series toolkit
• Maintenance/Asset Management System new effort
  with SOM

10
NCHRP 20-57 Analytic Tools for Asset Management
-Results
Network Tool (AssetManager NT)
Program Tool (AssetManager PT)
Long-Term (up to 20 years) Analysis based on
Aggregate Performance Results from Management
Systems Supports Resource Allocation Tradeoffs
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
NCHRP 20-57 Analytic Tools for Asset Management

• AssetManager NT stand-alone desktop application
• AssetManager PT functional prototype (based on
  an Excel spreadsheet)
• Both
• Rely on data from existing DOT management
  systems robots developed for Pontis HERS-ST
• Highly configurable based on specific DOT
  parameters and practices

12
Transition from Research to Practice
Considerations

• NCHRP will distribute tools to all state DOTs
• Without on-going support mechanism, what will
  happen to 20-57 tools?
• Maximum impact possible if tools are bundled with
  implementation assistance and support.
• Continued funding needed for architectural and
  functional improvements
• AASHTOWare program offers proven mechanism for
  cost-effective long-term support, maintenance and
  enhancement

13
AssetManager as an AASHTOWare Product Whats
Needed?

• Commitment from Subcommittee to champion
  AssetManager implementation and sponsor the
  proposed AASHTOWare project
• Project proposal for tool implementation
• 5 volunteers - to serve on Steering Committee to
  guide pre-solicitation activities
• A successful project solicitation with a minimum
  of 10 DOT participants

14
Whats Needed?Suggested Project Approach

• Phase I
• Goal Form community of early adopters.
• Actions Implementation and Support
• Timeframe - 12 months
• Phase II
• Goal Architectural Functional Enhancement
• Actions On-going support and maintenance, select
  database for PT, port both tools to .NET, add
  functional improvements prioritized by users
• Timeframe 12 to 15 months
• Initially, solicit funds for Phase I only
• Define Phase II as part of first phase work plan,
  and then solicit

15
Whats Needed?Suggested Phase I Work Plan

• Develop AssetManager Tutorial
• Develop Technical Manual
• 2 On-site Visits by Cambridge Systematics to each
  participating DOT, including a CEO Workshop
• Telephone support
• Maintenance fix critical errors log routine
  errors for second phase correction
• Optional Service Units
• Develop additional robots
• Survey participants and establish prioritized
  enhancement list
• Develop work plan for Phase II

16
Next Steps AASHTOWare Project Initiation

• Develop Phase 1 project proposal and solicitation
  package
• Review and approval by the Special Committee on
  Joint Development
• Send to AASHTO membership and other potential
  project sponsors
• If solicitation is successful, proceed with
  project
• Appoint AssetManager Project Task Force
• Start work!

17
Next Steps

• Endorsement of proposed project by Asset
  Management Subcommittee
• 5 volunteers
• Finalize work plan and submit for SCOJD approval
• Reauthorization
• Mail solicitation to all AASHTO members target
  June 2005

18
Questions?