Mississippi DOT's Approach to an Enterprise Wide Linear Referencing System

Transcription

1 Mississippi DOT's Approach to an Enterprise Wide Linear Referencing System Michael Cresap, Mississippi Department of Transportation Bruce Aquila, Intergraph Corporation Concurrent Session 3.4, State LRS Systems Tuesday May 7 th, 2013

2 Introduction Background Business Problem Methodology Lessons Learned Benefits Future Conclusion

3 Background MDOT maintained a simplistic LRS LRS in place for many years LRS supported: Asset data management Reporting Analysis

4 Business Problem Current Data Structure Limited Multiple Networks Maintained Planning Pavement/Research Safety No Maintenance Synchronization Event Data Maintenance Difficult Data and LRM Conversion No Temporal Capability

5 Methodology Solution Selection Extensive Research Iowa DOT Model (NCHRP ) NCHRP 460 White Papers Solution Demonstrations Intergraph ESRI Bentley/Exor ERDAS Vendor Decision Intergraph GeoTrans Data Model

6 Methodology Needs Assessment Conducted Comprehensive Needs Assessment Interviewed 19 Stakeholders Inquired about: LRM Requirements Business Rules Operational Systems Data Collection Methods Data Dissemination LRS Maintenance Workflows Data Model Requirements

7 Methodology Needs Assessment Findings Field Personnel Collect the Most Data Multiple Networks Maintained (Not Synchronized) County Route Logmile Most Used LRM Most Required Data: Maintenance Pavement Construction Traffic Functional Class Financial

8 Methodology Implementation Plan Identified Common LRS Requirements: Dual Carriageways Ramps Frontage Roads Roundabouts Concurrency State Cumulative LRM Cross-Overs Defined Software Needs Oracle Spatial Oracle Workspace Manager GeoMedia Professional GeoMedia Transportation / Transaction Manager

9 Methodology Implementation Plan Maintenance Seat GeoMedia Professional GeoMedia Transaction Manager GeoMedia Transportation Manager GeoMedia Fusion Enterprise Database/Server Oracle Client Analyst Seat GeoMedia GeoMedia Transaction Manager GeoMedia Transportation Analyst Oracle Enterprise/ Locator Oracle Workspace Manager Viewer Seat GeoMedia WebMap Professional Internet Explorer Web Browsers

10 Methodology Implementation Plan Phase 1 Training Data Validation Define LRS Model Create LRS Structure Populate LRM s Local Road Incorporation Index Creation Temporally Enable Model Phase 2 Event Table Preparation Event Datum Locations

11 Methodology MLRS Workshop Objectives Understand the MLRS Data Model Establish Business Rules for Deployment Identify Design Issues Hands on Experience Issues Identified Anchor Section Crossing County Boundary Bridges Without Intersections Measurement Begin Location on Ramps Dual to Single Centerline Divided Highway Cul-de-sacs Roundabouts State Cumulative LRM LRS usage beyond Linear Referencing

12 Methodology Maintenance Use Case Definition Design Maintenance Use Cases Realignments Re-inventory Road Change Route Name Add New Routes Validate Changes Delete a Route Training Stage Test Dataset Tested Maintenance Use Cases Routing with LRS

13 Benefits One Source of the Truth Better Locational Stability More Accurate Network Creation of Business Rules Clearly Defined Maintenance Procedures Temporally Enabled Maintenance

14 Lessons Learned Being Deliberate Pays Off Research Needs Study Implementation Plan Workshop Deployment Training is the Key Find a CHAMPION Pilot Test Identifies Issues

15 Future MLRS Web Services MLRS Network Data Model MLRS Event Data Model MLRS Data Validation MLRS Logging

16 Future Architecture

17 MLRS Web Services Utilize Current MLRS Network External Systems can Request Location Methods to Obtain Location: Coordinates to LRS LRS to Coordinates Time (Effective Date) Will return: State Plane Projected Coordinates State Transverse Mercator Coordinates Geographic Coordinates Historical LRS Reference Location Current LRS Reference Location

18 MLRS Network Data Model Augments Current LRM Model Master MLRS Table to Control: LRM s LRS Keys (County vs. State) Minimum/Maximum Measures for LRS Keys Additional Server Side Data Validations Multiple Carriageway Representations for Event Data: Primary and/or Secondary centerline Mapping secondary to primary network elements Multi-lane Representation Jurisdiction Allocation Web interface to configure LRS

19 MLRS Event Data Model Database-Centric Approach to Stabilizing Events Integrated Server-Side Management Event data registered by MLRS Web Service Will support: Multi Key Multi Jurisdiction Multiple LRM s Minimal Data Entry Time Dual to Single Carriageway Modeling Batch Data Loading Improve HPMS Reporting Capabilities System Date Effective/Valid Date

20 MLRS Validation Context Sensitive MLRS Event Data Validation Validation includes: Single Record during Interactive Editing Multiple Record when Network Changes (Realignment) Single Record Validation Jurisdiction Verification Begin and End Measure Extent and Lane Verification Measures Flagged Requiring Adjusting (Tolerance) Geocoding within Tolerance Measures are Locatable on Network Multi Record Validation Begin and End Measure Measures Flagged Requiring Adjusting (Tolerance) Datum Validation upon Route Realignment

21 MLRS Logging Error logging provided Performance Tracking Errors and Warnings Controlled by Database Configuration Logging Levels Include: Error Messages Only Key Function Calls Verbose or Debug Logging Logging Checks User/Session Auditing Historical (System and Effective date)

22 Questions?