Post on 08-Jul-2015
description
ODOT District 2’s Asset ManagementPresentation for U.S. DOT Volpe Center
2Ohio Department of Transportation District Two
ODOT District 2 GIS
John PuenteDistrict 1 GIS
Coordinator\ Planning Administrator
3Ohio Department of Transportation District Two
ODOT District 2 Geospatial Assets
District 2• 3,771 Lane Miles• 13 Million Miles Traveled Yearly• 1,236 Bridges• 5,181 Culverts• 35,958 Ground Mounted Signs• 320 Overhead Signs
4Ohio Department of Transportation District Two
Asset Problem
• What Quantity?• Where Is It?• How Old Is It?• How Many Times Have We Performed Maintenance To It?• What Is Its Life Expectancy?
5Ohio Department of Transportation District Two
Asset Collection
Business Requirements• Asset Type
• Safety Related• Guardrail, Signs etc.
• Accuracy• Location On Earth• Collection Quality
• Frequency• How Often Does It Need Updated
• Cost• Restrictions
• Technology Limitations• Right Collection Tech. For The Asset
Technology For Collection• Remote Sensing
• LiDAR, Aerials etc.• GPS
• Mapping, Survey, Cell Phones• Inferential Statistics
• Calculate Base on Sample Sets
• Through Work Orders• Collect when work is performed to it.
• Project Inclusion• Require contractors to collect after a project is completed.
6Ohio Department of Transportation District Two
Asset Collection – Current Practices
• Multiple Data Formats• No Standardizations \ Localized Standards• Log Point As Primary Spatial Reference
•1 mi = 5280 ft Most Locations Carried To .01 = At +/- 52.8’• Average Error In Log Point +/- 300 ft.• Mile Marker Signs Would Be Placed Wrong• Mile Marker Signs Would Not Be Recorded Correctly• Locations Recorded By Multiple Methods
• Landmark, County Log Point, State Log Point And Intersection
7Ohio Department of Transportation District Two
Asset Collection – GPS Devices2nd Most common location referencing method used by ODOT is GPS.Pros
• Accurate Locations• Electronic Upload• Customizable Applications
Cons• Requires Specialized Equipment And Software• Requires Logistical Planning• Compounding Deadhead Times For Complete Coverage• Requires Specialized Training• Subject To Weather Conditions• Increased Safety Risk To Field Crews And Public
8Ohio Department of Transportation District Two
Asset Collection – Remote Sensing Methods
• Satellite Imagery• Some Free• Good Stuff Costs Big $$$• Most does not meet our resolution needs.• Limited By Weather
• LIDAR• OSIP LIDAR Very Accurate• 1 Meter spacing did not meet our resolution needs.• Freely Available
• Oblique Aerial Imagery• Most does not meet our resolution needs.• Expensive
• Orthorectified Aerial Imagery• Most does not meet our resolution needs.• Frequency of coverage is dependant of source.
9Ohio Department of Transportation District Two
Asset Collection – Remote Sensing Methods - ODOT Video Log
•Video Log as a remote sensing method for asset inventories.
• Good Update Frequency• Established Internal Business Process• Cheap To Implement
•ODOT Video Log• Occurs Every 3-6 Years• Process Is In Place• Possible to project coordinates into image.• The van has a GPS.• We did not have software to accomplish our needs.
10Ohio Department of Transportation District Two
Asset Collection – Methods
• Identified Assets• Identified Collection Methods• Prioritized Asset Collection• Identified Update Procedures
11Ohio Department of Transportation District Two
Overall GIS Management Model for Asset Management
AssetCollectionApplications
Asset (Feature &AttributeManagementApplications
InteroperabilityApplication
12
Asset Management Feature\Attribute Applications
Ohio Department of Transportation District Two
13Ohio Department of Transportation District Two
Asset Management Application
14Ohio Department of Transportation District Two
Asset Media And Report Application
• Attach Pictures, Movies and Documents• Print Reports
15
GPS Asset Application
Ohio Department of Transportation District Two
16Ohio Department of Transportation District Two
GPS Application
• Software Works On Any Windows Mobile• For GPS Operations That Require Field Visits• User Friendly Interface• Managed With Same Application As BADCS And Web Map• Managed And Developed With Visual Studio• Currently Performs Inventory and Inspections• In Development - Work Order Operations
17
Web Mapping Application
Ohio Department of Transportation District Two
18Ohio Department of Transportation District Two
Web Mapping
Current Web Mapping Application• View All Assets• Ensure Spatial Accuracy With Aerials• View Historical, Current and Future Projects• Used For Planning And Research• Generate Reports• Export Shape Files and MicroStation DGN files
19Ohio Department of Transportation District Two
Web Mapping - Reports
Critical ConditionID Longitude Latitude CULVERT_FILE_NUMBERDistrict NLF_ID INVENTORIED_BYINSPECTOR_INITIALSREVIEWER_INITIALSENTRY_CLASSROAD_ID MAINTENANCE_RESPONS
1611 -83.7016 41.52251 8.71E+08 SWOOSR00065**CDLH DLH DLH A 0 S1612 -83.6998 41.52461 8.71E+08 SWOOSR00065**CDLH DLH DLH A 0 S
Right of WayId NLF_ID Archno County Route Log_beg Log_end Year Sheets Type Type_1 Index_Type
4470 SWOOSR00065**C WOO 65 13 14 2005 RW R
ConstructionId NLF_ID Archno County Route Log_beg Log_end Year Sheets Type Type_1 Index_Type
1797 SWOOSR00065**C02c8152 Woo 65 11.99 17.22 1923 34 Const C5091 SWOOSR00065**C WOO 65 11.96 17.69 1995 Const C
Ellis ProjectsId PID_NBR DISTRICT_NBRLOCALE_SHORT_NMEPROJECT_NMETERMINI_TXTPROJECT_MGR_NMEPROJECT_TYPE_SHORT_NMELETTING_SHORT_NMERESERVOIR_YRPROJECT_STATUS_CDDOC_TYPE_SHORT_NME
1521 88505 2 WOO WOO SR 65 12.00 ResurfFrom SR-64 (near Waterville) to Perrysburg corp line (near Holly Ln).FAHY, JULIE MLet ODOT Let 1 Exempt
State RoutesPRIMARYINDEX1RI_STATE_BASIC_SEGMENTS_NUMDISTRICT_NBRNLF_ID COUNTY_ABREV3_CDTRANS_ROUTE_CDTRANS_ROUTE_IDTRANS_ID_EXTENSION_CDTRANS_ID_DESCRIPTION_CDTRANS_BI_DIRECTIONAL_CDLOGPOINT_SLM_BEGIN_NBRBACKSTATION_BEGIN_CD
2426 34028 2 SWOOSR00065**CWOO SR 65 * * C 122427 34029 2 SWOOSR00065**CWOO SR 65 * * C 13.61
20
Buckeye Asset Data Collection System (BADCS)
Ohio Department of Transportation District Two
21Ohio Department of Transportation District Two
Video Log Applications - Video Vehicles
22Ohio Department of Transportation District Two
Video Log Applications - Vendor Evaluations
• Evaluated Several Vendors With Video Log Solutions For Asset Extraction• Researched Extensively• Found Vendors At Extremes (Good and Bad)• Hard Part Was Finding Their Actual Capabilities• No one knows our business better than us.• All were too expensive for the district.
23Ohio Department of Transportation District Two
Solution – Build Our Own Asset Capture Software
24Ohio Department of Transportation District Two
Solution – Software Requirements
• Web Based For Scalability• Throughout District Office 1 And 2, And County Garages
• Flexible• We can add delete or change any asset any time.
• Independent From Any Vendor• We will be able to use this with any video vendors’ image.
• User Friendly• Asset collection is accomplished by a few clicks.
25Ohio Department of Transportation District Two
Mobile Video Asset Capturing Application - Image Calibrations
• Issue• We were not sure of the camera configurations for the different video cycles.• We attempted to measure everything our selves and found that we could not be accurate enough.
• Solution • By manipulating Tao’s equations and coming up with a few of our own we were able to develop methods to develop a configuration for each video cycle.• Uses the imagery with known points and measurements to calibrate.
26Ohio Department of Transportation District Two
Mobile Video Asset Capturing Application - Image Calibrations
27Ohio Department of Transportation District Two
Mobile Video Asset Capturing Application (2007)
28Ohio Department of Transportation District Two
Mobile Video Asset Capturing Application (2007)
29Ohio Department of Transportation District Two
Mobile Video Asset Capturing Application (2007)
Goo
d A
ccur
acy
Bad
A
ccur
acy
30Ohio Department of Transportation District Two
Mobile Video Asset Capturing Application
31
Interoperability Application (FME)
Ohio Department of Transportation District Two
32Ohio Department of Transportation District Two
Interoperability
• Current• With advanced interoperability software from Safe Software, ODOT District 2 is able to deal with the ever changing GIS technology.• Conflate different standards.• Retain the enterprise data formats.• Supply our customers with the format they require for their system.• Automate tasks that would have taken much more time to complete.
33Ohio Department of Transportation District Two
Bridge And Culvert Asset Data
• Bridge and culvert data is frequently requested by the other governmental agencies.• Previous workflows consisted of several steps.
• Querying out the info from the database.• Loading it into a GIS platform.• Geocoding coordinates.• Exporting data multiple times for different formats.
• With FME a workspace was created which reads directly from the production databases.• Now the only thing that needs done is a quick command line that runs the workspace.
• Automatically outputs both a shapefile and a excel document.
34Ohio Department of Transportation District Two
Asset Data Conflation
• Sign information collected as part of the LBRS project.
• District operations require different attributes and a different storage format.• Data needed to be conflated into the existing spatial data framework.
• Data will feed the proposed work order management system.• Data is available for MPO’s cities and villages.
“Ohio's Location Based Response System (LBRS) is a County/State partnership that gathers accurate locational information on all roads and addresses in a county.”
35
Current Results
Ohio Department of Transportation District Two
36Ohio Department of Transportation District Two
Current Asset Processes
Culverts• Inventory• Inspection Every 5 Years
Signs• Inventory• Work Order - Development
Overhead Signs• Inventory• Inspection Every 7 Years
Lighting• Inventory• Inspection – Yearly maintenance Contract
ADA Curb Ramps• Inventory
Roadway Weather information System (RWIS)
•Inventory• Work Order - Development
37Ohio Department of Transportation District Two
Sign Asset Collection
Asset Metrics• Collection So Far For D01 And D02
• Total Signs – 42,835• Est. Value – $3.1 Mil• Est. Complete D2 - %98• Est. Total Signs In D2 – 37,000• Average 450 Signs Collected Per Person Per Day
38Ohio Department of Transportation District Two
Asset Collection Results – BADCS (Signs)
• Development Cost for BADCS - $6,500• More Efficient Compared To Other Collection Methods• Consultant and Governmental Requests For Information• Statistical Analysis• Roadway Project Planning• Safety Improvement By Reducing the Need for Field Visits• Reducing Demand On Some Surveying Activities
BADCS
BADCS
39Ohio Department of Transportation District Two
Partnerships - Penta County and OSU Sign Asset Collection
• Training and collection started 4/15/2010• Penta County 2 Year GIS Program
• 18 Students• OSU Lima Campus GIS Majors
• 2 Students from OSU – Lima Campus• Student Benefits
• Real World Experience• Working With Cutting Edge Software
• ODOT Benefits• Capture of our sign assets.• Develop workflows and benchmarks for internal collection.• Developed a method to access potential resources that not only helps ODOT but also helps Ohio’s Future.
40Ohio Department of Transportation District Two
Future Projects – Statewide Culverts and Bridges
Culverts And Bridges• Utilize Existing Investments• Reduce Demand On Programming Resources• Standardize Collection Methods• Flexible Enough To Collect Any Assets• Fix Windows 7 Compatibility Issues• Software Has Been In Production In Dist. 1 & 2
41
Future
Ohio Department of Transportation District Two
42Ohio Department of Transportation District Two
Future
• Combining Applications Into One Web Application
43Ohio Department of Transportation District Two
Future
• Modified Navigational GPS Units• Using the video log as a car Navigational GPS unit.• Assets would be displayed as the vehicle approaches them.
44Ohio Department of Transportation District Two
Future
•Augmented Reality• Using the video camera as a backdrop we can project the assets into the video using the same equations.
45Ohio Department of Transportation District Two
Summary
• We not only achieved our goals but exceeded them.• In-House Programming• Inexpensive• Efficient Intelligent User Interfaces• Thin Client Application• Easy To Customize• Applications Are Standardized• User Friendly• Transparent Backend Processes• The software and processes are growing in demand.
46Ohio Department of Transportation District Two
Contact Information