LRS & Business Integration@ MnDOT

Jesse Pearson | LRS Integration Portfolio Manager

Minnesota Department of Transportation

GIS-T 2017 conference, session 7.3.3

mndot.gov

How do you eat an elephant?

mndot.gov 2

Goals for session

mndot.gov/ 3

1. Learn options for staying in Sync with R&H data

2. MnDOT’s successes and failures

3. MnDOT’s approach for LRS integration

4. Lessons learned

Successes at MnDOT

mndot.gov/ 4

Speed Limit data

➢ Internal registered event

➢ Edited in separate RCE app.

Transportation Asset Management System (Agile Assets)

➢ Currently integrated with R&H 10.3.1 and Agile Assets 7.1.5.1

➢ Late April – moving to R&H 10.5 with TAMS2 ver.7.2

Failure #1

mndot.gov/ 5

Traffic Data (Segments, Forecast, Count locations)

➢ Internal registered event

➢ Orig. converted with other events

➢ QA process in place to return “changed” roads made by R&H

➢ Defects in R&H product at 10.3.1 became nail-in-coffin

➢ Pulled out of ALRS in Dec. 2016, became a stand-alone FC.

Failure #2

mndot.gov/ 6

Upgrade to R&H 10.4.1

➢ Agile Assets needed the export network GP Tool for integration

➢ Export network GP Tool didn’t work at 10.4.1

➢ Forced MnDOT to skip to 10.5 upgrade

High-level Integration Strategy

System Data analysis

Business Process Design & Strategy

Plan, Identify Resources and Recommend

Steering Commitee Prioritization

Present to Steering Committee

1 2 3

45

What is needed for integration?

8

Effort

System context diagram

Current business process

System Dependencies

Users (#, roles, etc.)

System Data needs

Identify quick wins

9

Construction Planning

Effort

Dependencies:

PUMACHIMES

(Replacing PPMS)

P6(Scheduling)

FMIS(Fed. Auth.)

FFATA

Bridge (BRM)

PUMAPUMAPUMA

Bridge (BRM)

Bridge (BRM)

Project Tracker

(State Aid Projects)

Who gets integrated first?

mndot.gov/ 10

• 12 critical systems were already identified out of 130 systems.

• Dependencies (Federal Funding/Mandates, Internal/External customers)

• Level of Effort

• Quick wins may go ahead of larger efforts

Level of Effort – Initial Analysis

11

Low Med. High

mndot.gov/

RWMMPUMA

MnCMAT

RCA, WOM,MDSS, AVL

Crash

P6 FMIS &FFATA

Bridge

Project Risks

mndot.gov/ 12

➢ Mixing Data (Old/New)

➢ IT Resources (DBAs)

➢ Delivery of products (timeline)

➢ Intersections not clearly defined for MnDOT(Crash Effort)

Options for business systems using LRS data

13

• New systems = must consume new LRS data

• For existing systems that consume the LRS data:

1. Internal registered event (Bridge)

2. External registered event, changes automatically consumed

3. External registered event, business receives notice of a change, not automatically consumed

4. Not a Registered event, business area would need to develop a process to update their data.

mndot.gov/

LRS data conversion process

14

• Convert data to the new LRS measures

• Data is frozen

• Corrections are made

• Re-load new data into Production with new LRS measures

mndot.gov/

0.0001.000

0.000 0.950

View from the side:

View on map:

True Miles

Cartographic Length

Lessons Learned at MnDOT

15

• Communicate!

• Plan for 6+ month learning curve for any new analyst

• A Strategic plan is a must

• Prioritizing is essential

mndot.gov/

Wrap up & Questions?

Jesse Pearson

LRS Integration Portfolio Manager

Jesse.pearson@state.mn.us

651-366-3881

mndot.gov 16