Bill Schuman

1
Bill Schuman Don KielJanuary 23, 2007
State DOT Route Logs / Straight Line Diagramming
Applications Cooperative Technology Sharing
Approach
2
What Are Route Logs?(Straight Line Diagrams)

• Used in paper form for years at many state DOTs
• Effective, simple way to view business data for a
  portion of roadway
• Combines straight-line view of road and
  associated business data

3
Automating Route Logs - Advantages

• Streamlines maintenance and updating
• Allows easier sharing of information
• Can take advantage of leading edge technologies
  such as geographic information systems
• Can be enabled for easy viewing and use via the
  Web
• Expandable, customizable for individual business
  needs
• Can be integral part of a Web portal environment

4
VTrans Route Logs History

• Long-time use of paper SLD products
• Lack of maintenance
• Process to automate started in 2000
• V. 1 of Integrated Route Logs (IRA) completed
  2003
• Web and Desktop versions
• SQL Server database
• ASP
• Phase 2 continuing

5
(No Transcript)
6
NHDOT Route Logs History

• SLD plots used especially by Districts
• Lack of maintenance
• Conversion project of VTrans IRA completed in
  2005
• Web version only
• Oracle database
• .Net
• Phase 2 beginning now

7
(No Transcript)
8
VDOT Straight Line Diagram History

• Leverages updated road network model and database
• Part of new Roadway Network System
• Conversion project of VTrans IRA scheduled for
  completion 1Q 2007
• Web version only
• Oracle database
• .Net, C
• Phase 2 requirements identified

9
(No Transcript)
10
Cooperative Approaches

• Coordinated, shareable and reusable code,
  functions, updating, maintenance
• Cost sharing/savings
• Standardization
• Management of customization

11
Groundwork Already Completed

• VTrans developed a code-sharing agreement
  document (NHDOT and VDOT)
• VT-NH-VA Phase 2 Planning and Coordination
• FHWA Involvement

12
NHDOT and VTrans - Proposed EnhancementsVDOT -
Initial Requirements
13
Should There Be A Consortium Approach?

• Pros
• Increasing demand for product
• Code-sharing agreement could be jointly
  sponsored, open to others being added
• Value added functionality each new party
  would commit to sharing
• National coordination technology transfer
  opportunities
• Subscription service with software custodian
  for compatibility and coordination in design,
  development, implementation, and maintenance
• Further leverage the investment of VT, NH, VA,
  and others that participate

14
Should There Be A Consortium Approach?

• Cons
• Administrative overhead
• Contracting inconsistencies
• Pricing questions

15
Questions
?