How To Improve Lrs Maintenance

GIS-T Conference 2015

Crossroads in the Heartland

LRS Maintenance and

Asset Management Systems

Phil Hardy – LRS Product Manager

GIS-T Conference 2015

Agenda

• Evolution of LRS Maintenance

• Lessons learned implementing Roads & Highways

1. Periodic vs dynamic updates

2. LRS editing with event updates in mind

3. Include Asset Managers into the QC process

4. Post-processing the LRS Interface

Evolution of LRS & Event Location Maintenance

• Historical Method

– Everybody’s on their own (LRS & Events)

Evolution of LRS & Event Location Maintenance

• Historical Method

– Everybody’s on their own (LRS & Events)

• Current Method in many DOTs

– Integration by memo

– Each group makes its own

Event changes

LRS

Pavement

Single-Source LRS

• Great force multiplier

– 1 LRS edit makes many event edits across all systems

• Double-edged sword

– 1 LRS editing mistake means many event errors

Automated  Updates Automated  Updates Automated  Updates AgileAssets Transmetric

Lessons Learned Implementing Roads & Highways

1. Periodic vs dynamic updates

2. LRS editing with event updates in mind

3. Include Asset Managers into the QC process

4. Post-processing the LRS Interface

1. Periodic vs Dynamic Updates

• Dynamic – The LRS is always the same as the source

system (“internal” events)

• Periodic – Deliberate snapshots from the source system

(“external” events)

When to Use Dynamic Updates

• Roadway Inventory

– Functional classification

– Federal Aid #

– Jurisdiction

– Number of Lanes

– Lane widths

– Shoulder widths

– Median type

– Etc.

When to Use Periodic Updates

• Real Asset Management

– Pavement

– Bridge

– Safety

– Etc.

• Items that involve analytics

– Project package creation

– Scenario evaluation

2. LRS Editing with Event Updates in Mind

Remember you are not just editing the LRS

… you are editing EVERYBODY’s events

Keeping the right perspective on LRS

Keeping the right perspective on LRS

Asset Management

LRS

 Safety

 Congestion

 Pavement

 Bridges

3. Include Asset Managers in QC

• Suggested workflow

LRS  Editing LRS QC Pass LRS  standards? Run Test  Interface Run Full  Interface Acceptable  results? Yes No Yes No

Ro

ad

s 

&

Highw

ay

s

Agile

 

Asset

s

4. Post-processing after LRS Interface

Bridg e P av emen t Sa fe ty Tr affic Main te nance Report of changed events      Automated data update for changed events Report of new route segments      Automated data update for new route segments    Report of retired route segments   Automated data update for retired route segments Report of changed jurisdictions      Automated data update for changed jurisdictions   

4. Post-processing after LRS Interface

Bridg e P av emen t Sa fe ty Tr affic Main te nance Report of changed events      Automated data update for changed events Report of new route segments      Automated data update for new route segments    Report of retired route segments   Automated data update for retired route segments Report of changed jurisdictions     

4. Post-processing after LRS Interface

Bridg e P av emen t Sa fe ty Tr affic Main te nance Report of changed events      Automated data update for changed events Report of new route segments      Automated data update for new route segments    Report of retired route segments   Automated data update for retired route segments Report of changed jurisdictions      Automated data update for changed jurisdictions   

4. Post-processing after LRS Interface

Bridg e P av emen t Sa fe ty Tr affic Main te nance Report of changed events      Automated data update for changed events Report of new route segments      Automated data update for new route segments    Report of retired route segments   Automated data update for retired route segments Report of changed jurisdictions     

Review

• Evolution of LRS Maintenance

• Lessons learned implementing Roads & Highways

1. Periodic vs dynamic updates

2. LRS editing with event updates in mind

3. Include Asset Managers into the QC process

4. Post-processing the LRS Interface

Contact Info:

Phil Hardy - AgileAssets

[email protected]

949-505-3315

LRS Interface Methodology

LRS Gateway

External System

Integration Layer

AgileAssets

Common across the board Custom for each external system Esri Roads & Highways Bentley/Exor Various homegrown systems

Buffer Tables

Allows prior review of changes

LRS Editing with Assets in Mind

• 2 ways to do this edit

– Replace the entire route

– Do 2 realignments

LRS Editing with Assets in Mind

1) Replace the entire route

– Event effect: retire all events

LRS Editing with Assets in Mind

2) Do 2 realignments

– Event effect: retire only affected

events

Involve Asset Managers in LRS QC

Test Mode Option

– Allows business units to preview results

– Can preview changes to both LRS and Events

Old Alignment

New Alignment

Interface to Roads & Highways

LRS Interface Planning

• Make sure the 2 LRSs are in sync

– In terms of data

– In terms of LRM design

• Make sure your event location data is clean (i.e. it fits on

the LRS)

• Make sure the 2 sides of the interface can fully

communicate with each other

Configuration Steps

• Fill in Interface Config window (partially)

• Make connection (ArcCatalog - AgileAssets system)

• Register External Events with Rds & Hwys

• Create Rds & Hwys Export Network web service

• Create Rds & Hwys Relocate Events web services

• Finish filling in Interface Config window

Interface to Roads & Highways

• Simplified Workflow

Request 

Updated LRS

Request 

Updated 

Events

Update AMS 

Tables from 

Buffers

Load LRS 

Buffer Tables

Load Events‐

to‐be‐

Updated 

Table

Load Event 

Buffer Tables

Start

Comparison Views

Comparison Views

Comparison Views

Comparison Views

QC

Roads & Highways

• R&H Analyze

• Data Reviewer

AgileAssets

• Job errors – may have links to ArcGIS errors

• System Logs (provides extra details on Job errors)

• Error messages in Comparison views

Interface to Roads & Highways

Making edits  to LRS v1 Making edits  to LRS v2 v3  v4 Making edits  to LRS v3 LRS v2 is available LRS v3 is available LRS v4 is available v2  v3 v1  v2 R&H Import LRS  v2 Import LRS  v3 Import LRS  v4 v3 v2 v1 Adding events  to LRS v1 Adding events  to LRS v2 Adding events  to LRS v3 AgileAsse ts Run  Interface Run  Interface Run  Interface

Editing Activities

• Create Route • Extend Route • Realign Route • Reassign Route • Retire Route 0 100 0 100 120 0 ₁₀₀ retired 0 100 1‐10 retired 20 80 20 80 20 ₈₀ I‐110 I‐10 I‐10 0 100

Event Measure Behaviors

Before Realignment Stay Put Move Snap Retire

Planning

• Make sure the 2 LRMs are in sync

– In terms of data

– In terms of LRM design

• LRM design needs to be based on lowest common

denominator

– Examples:

• AgileAssets requires a base LRM that covers entire network

• R&H returns a single, concatenated route name for all LRMs

• Make sure the 2 sides of the interface can fully

communicate with each other

• Make sure your event data is clean (i.e. it fits on the

LRS)