Virginia Department of Transportation

1. Virginia Department of Transportation Inventory and Condition Assessment System First Step towards Asset Management

2. Maintenance Business Process ReEngineering - 1995 • Did not have a complete picture of our infrastructure and its condition • Unsure we were making the best possible investments • Unable to evaluate the results of strategies and investment • Unable to advocate for ourselves

3. Maintenance Business Process ReEngineering - 1995 • Comprehensive inventory • Make best investment strategies • Consider asset life cycle • Optimize over all assets and asset life cycle • Consistent service delivery statewide • Quantify infrastructure

4. Inventory and Condition Assessment System • Comprehensive inventory – all assets (pavements, bridges, drainage, roadside, traffic) • How many, where, what condition • Provide data for business decision system to follow • Basis for Asset Management

5. Integrating the Maintenance Business of VDOT • Start with the infrastructure inventory • Enable Asset based data recording • Enable resource incensement to be attributed to assets – financial, equipment, human • Support work planning • Support work implementation • Support evaluation of results

6. Integrating the Enterprise Business of VDOT • Managing the Asset through its Life Cycle • Planning and alternative evaluation • Design • Construction • Maintenance • Retirement • Managing the Use of the Asset – • land use permits, hauling permits, routing • traffic flow, capacity, impact, trip and travel analysis

7. Integrating the Business of Transportation • Intermodal • Buses, trains, bikes, pedestrians, airports and spaceports • Interagency • Emergency services, State Police, Environmental Quality • Inter-Jurisdictional • Cities and town, municipal planning organizations, other states

8. Integrating the Business of Transportation through Asset Management Maintenance Enterprise Commonwealth

9. Integrating the Data of Transportation through Asset Management Location Connection Time Are central issues for the integration of asset management data in a transportation agency

10. Integrating the Data of Transportation • Location in space and on the network • Connectivity of assets to the network, of parts of the network to itself • Time is an important dimension to support from planning evaluation of investment results Four Dimensional Data

11. Integrating Transportation Data through Location • Data integration across different application areas is a long-standing need of DOT’s • The concept of location can serve as an integrative concept across a wide variety of data; geographic and other • Location is central to all core business functions of a DOT • Source NCHRP 359, 1993

12. Integrating the Business and Data of Transportation The linear “network” or datum is central to all core transportation businesses • Manage the Assets – plan, design, construct, maintain • Use the Assets - permit, route, capacity, traffic, emergency • Manage Transportation - to effectively move goods and people

13. Model of a Roadway Network in an Asset Management System Network sections are uniquely numbered 201 100 102 101 Sections 100,101,102, in order make up one route Sections 200,101,201, in order, make another route This arrangement allows the network to represent Routes and alternate routes 200 Node – where sections join, every section has one node at each end Network Section or Link – represents section of network between two nodes; spatially correct, curvilinear distance correct Asset Distance from the node, and the offset from the link This distance, plus the offset, plus network section number uniquely place the asset ON THE NETWORK. Although displaying these things in ArcView can “look” like this, the software must create and manage the actual connection of the asset to the network – and be able to re-create these measures if something changes. The distance and offset can be expressed in any unit, Including addresses. THIS IS LOCATION REFERENCING.

14. Location and Connection • Location of an asset in relationship to the datum matters - through the datum all linear referencing systems can be used • Topology is more than a display, it is part of the data and describes the spatial relationship of the asset to the linear datum; • Location is a native descriptor used by DOT personnel; location on a linear referencing system is the real world situation • Fundamental characteristic of a transportation system is connectedness

15. Time Matters • Temporal operators and temporal consistency: • Enable analysis of asset history • Enable analysis of deterioration • Enable evaluation of results of investments over time • Enable analysis of network status over time • Enable time-based routing, capacity, and other traffic analysis

16. Transportation data integrate through the expression of connectivity to the network in the data model and in the data.

17. Location, connectivity and time and must be addressed in the data model

18. Highways by exor • Datum construction • Anchor points • Anchor sections • Linear network • These form the datum, the backbone of all the linear referencing systems

19. Exor functionality Supports multiple Linear Referencing Systems • County/route/milepoint • Milepost • Addresses • Link/node/offset (link into VDOT legacy highway records system) • Meterpost • Can generate LRM • Expandable • Can accommodate multiple routes

20. NCHRP 20-27 • Exor supports 20-27 data model • Maximizes the use of legacy data • Enables enterprise integration using the datum as the backbone • Separates linear events from the datum • Expandable

21. Integration via “Off the Shelf” Software • Purchased ready-to-market functionality • Forced additional requirement analysis • Forced issues around standardization of data • Off the Shelf solution is manageable and upgradeable, supported by vendor • Software is configurable and flexible • Can support some in-house development

22. Integration via “Off the Shelf” Software • Paradigm shift/organizational issues • Management of future functionality through a user’s group • Become part of larger user community – access to best industry practices • Assume that we can learn from business practice encoded • VDOT procurement model of ownership

23. Integration via “Off the Shelf” Software • Manages risks and controls costs of initial implementation • Manages risks around requirements • May not get what you thought you wanted • In this rapidly developing asset management environment, that can be a good thing

24. Lessons Learned • Conceptually, a model of integration with location, connectivity and time as central components is far more different that you think it is • Communicate this concept early and often

25. Lessons Learned • Choose the software based on the data model • Understand the data model • Define business requirements and rules in relationship to the data model • Start with smallest possible asset data sets • Then, actually prototype business requirements and push them through the system

26. Lessons Learned • Communicate concepts of Asset Management – direct relationship to the data • Don’t underestimate organizational and human issues

27. Lessons Learned Begin with intermodal, interagency, enterprise-wide asset management in mind and Start Small