2
Guiding Principles and Objectives Approaching the Change Under the
Hood Bringing It All Together What’s Next?
Outline
3
relationship between network-level priorities and the projects
entering the development pipeline.
Understand the trade-offs when choosing projects to develop.
Give the governance process a clear communication tool to help
align priorities.
Make data-driven decisions
TAM Principles Asset management is policy driven. Funding decisions
reflect
Iowa DOT’s vision for how the transportation system should look in
the future.
Asset management is performance based. Iowa DOT understands the
condition of its assets, defines performance targets, and makes
decisions that support these targets.
Asset management involves making trade-offs. Iowa DOT has options
for how to allocate transportation funding. It evaluates these
options and makes informed decisions regarding the best path
forward.
Asset management relies on quality information. Iowa DOT uses data
and analytical tools to support its decisions.
Asset management requires transparency and accountability. Iowa DOT
documents how funding decisions are made. It monitors performance,
tracks progress towards performance targets, and reports on
results.
4
the process
Guiding Principles and Objectives
“While it isn’t all about the tools, the right tool in the right
hands can change an entire culture.”
Technology
ProcessPeople
Timeline 2014 – Project Prioritization Underway 2015-2016 – Dynamic
Data Integration 2016 – v1.0 Prioritization Launch 2017 – v2.0
Prioritization Launch 2018 – Project Scoping starts in
earnest
– Scoping Application Launch 2019 – Valuation integration
– Maintenance Launch
Development
Development Develop a Scoring
Development Develop a Scoring
Method & Algorithm Application development
− ArcGIS Enterprise − Roads & Highways − JavaScript API v4.11 −
ArcGIS Online & Portal
Safe Software − FME Desktop − FME Server
Oracle − v12g − Spatial Views − Pluggables
Web Stack − Angular
Under the Hood
Freight 2,719,973 Impact Layers 60
Traffic 65,853 TOTAL 157
Safety Data 75,491
Roadway Location 41,684
INRIX 58,012
Project Priority ATMS Data 160,480
TOTAL 3,759,873
2 On Demand FME workspaces that are triggered through the
app.
32 FME workspaces run nightly on FME Server
2 FME workspaces that run monthly to update ATMS and INRIX
data
12
15
16
17
18
19
20
Automated processing of a priority algorithm on all projects
currently planned or programmed
Calculates performance scores based on many other DOT-managed
business data (bridges, pavement, traffic, etc)
Allows robust filtering and analysis of both project- level and
performance- level metrics
Bringing It All Together
22
23
Builds upon the Prioritization app framework to allow new projects
to be proposed
Input fields vary based on the program funding or work groups that
are specified
Bringing It All Together
25
Project extent is based on DOT LRS routes, ensuring every element
of the project is a valid road segment
Users can edit the start and end of each route so that only what is
being proposed for improvement is included
A link to Transcend’s RoadAnalyzer® and PathWeb are provided for
additional route review
Bringing It All Together
27
28
Associated geometries provide the basis for live impact analysis of
many other GIS layers
Each layer’s impact total is listed in parentheses
Layers can be turned on in the map and each impacted feature can be
viewed for more information
Bringing It All Together
30
When a project is selected, the user can filter and asses all
contributors to the priority score
Users are also able to see the level of complexity of a project,
and how that compares to other, similar projects
A live assessment of project schedule is shown, allowing users to
discover specific events that are contributing to delay
The user submitting a project scope may continue to refine all
project details until satisfied with impacts and priority
scoring
Bringing It All Together
32
Using INRIX data and other DOT sources, a live assessment of
congestion is displayed
Additional information relating to the contributors to the project
estimate can be viewed
Cost & budget information is pulled directly from DOS business
data
Bringing It All Together
But first, self reflection…
Successes Developed and integrated many data flows Beginning to
make data driven decisions Becoming integrated into our business
processes Building trust with our Transportation Commission
Increase coordination between program managers and Districts
Challenges Data Gaps Maintenance overhead Good vs best…explicit
tradeoffs…hard part to say no to a good project Risks Becoming too
tied to any one tool Becoming complacent in our data collection
Keeping a tool from becoming a gate instead of a tool
What’s Next?
Big Next Steps… Utilize for part 667 evaluations….align with
alternative selection Include analysis for Programmatic CE’s Expand
Data Integration….additional assets Including Valuation &
Benefits Snapshots (Concept/Design/Post Construction) Continuous
Evolution of Criteria and Scoring…mobility, freight, and road
classification Utilize for mitigation projection needs based on
scoped projects
What’s Next?
Slide Number 2
Slide Number 3
Slide Number 4
Slide Number 5
Slide Number 6
Slide Number 7
Slide Number 8
Slide Number 9
Slide Number 10
Slide Number 11
Slide Number 12
Slide Number 13
Slide Number 14
Slide Number 15
Slide Number 16
Slide Number 17
Slide Number 18
Slide Number 19
Slide Number 20
Slide Number 21
Slide Number 22
Slide Number 23
Slide Number 24
Slide Number 25
Slide Number 26
Slide Number 27
Slide Number 28
Slide Number 29
Slide Number 30
Slide Number 31
Slide Number 32
Slide Number 33
Slide Number 34
Slide Number 35