Enterprise GIS (eGIS) Project Overview

Enterprise GIS (eGIS) Project Overview February 12, 2014 Troy Marsh, GISP Why eGIS? Desired Future State Current Situa=on Pavement Other Systems Bridge HPMS Maximize Budgets Desktop Roadway inventory Performance Management Web Maintenance Mobile Esri Roads and Highways Authorita=ve LRS Safety Traﬃc ArcGIS PlaDorm Traﬃc
HPMS Pavement
Safety
Roadway Inventory
eGIS Project Goals AuthoritaEve Enterprise LRS & GIS Automate HPMS SubmiKal Replace Current Road Inventory System Improve Ability to Maintain and Report Traﬃc Data •  Address Data Silos and Data DuplicaEon •  Address Duplicate Data CollecEon •  Improve Job Based Data Support • 
• 
• 
• 
eGIS EGIS Project O
verview Contains 5 Major Ini1a1ves Roads and Highways LRS Roadway Inventory HPMS Traﬃc Integrated Management System & Dashboard eGIS Project Overview Module 1 – Roads and Highways LRS 1.  Establish AuthoritaEve LRS 2.  Leverage COTS + ConﬁguraEon 3.  Consolidate Centerline Geometry Source 4.  Implement LRS EdiEng Workﬂows 5.  FoundaEon for Road Inventory, HPMS, External System IntegraEon Esri Roads and Highways
A GIS-enabled linear referencing system for DOTs
GIS-enabled LRS Platform
§ LRS management
§ LRS editing & maintenance
§ LRS web services
§ Information model
§ Workflow
§ Quality control
§ Analysis
§ Mapping
§ Geoprocessing
6 New LRS Data Model Extensive Data Model Based on Industry Experience 7 Esri Roads and Highways
Enables platform expansion across the enterprise
HPMS
Roadway
Inventory
Safety Analysis
Planning
Field Data Collection
Executive
Dashboards
Straight Line
Diagrams
Asset
Management
and more…
GIS-enabled LRS Platform
8 eGIS Project Overview Module 2 – Road Inventory 1.  Totally restructure RI database and migrate data 2.  Build applicaEon to maintain, display and report RI data 3.  Tight integraEon with HPMS, Traﬃc and LRS 4.  Recipient of ﬁeld collected data eGIS Project Overview Module 3 -‐ HPMS 1.  Build and structure HPMS database and consolidate data 2.  Build applicaEon to maintain, display and report HPMS data 3.  Tight integraEon with systems that provide HPMS info 4.  Automate the annual HPMS report 5.  Recipient of ﬁeld collected data eGIS Project Overview Module 4 -‐ Traﬃc 1.  Address traﬃc database 2.  Address mechanisms to maintain, display and report traﬃc data 3.  Address integraEon with HPMS eGIS Project Overview Module 5 – IMS and Execu1ve Dashboard 1.  Viewing and analysis tools for EGIS data 2.  Available to enEre ALDOT enterprise 3.  Two applicaEons a.  Integrated Management System b.  Dashboard eGIS Project Overview Addi1onal Components LRS Editors
ALDOT
System Architecture Concept
SDE
Service
R&H
Desktop
Web
Services
HPMS Editors
Public
Web Viewers
Web
Services
RCE
R&H GDB
Server
ArcGIS
Web Server
Web
Services
ArcGIS
Online
Services
RI Editors
R&H
Internal
Web Server
R&H
Geodatabase
Web
Services
RCE
Web
Services
&
Replication
Traffic Editors
Web
Services
Routes
HPMS
RCE
Road Inventory
ArcGIS
API
District Offices
Field Data
Synchronization
Web Viewers
Replicated
Geodatabases
Traffic
Ad-‐Hoc
Viewing
Tools
Field Data
Synchronization
Field Crews (Mobile)
Other Internal Applications
14 General
Users
eGIS Es=mated Schedule Ini=a=ve Timeframe Begin Date End Date Roads and Highways 18 Months 06/2013 12/2014 Road Inventory / HPMS 24 Months 09/2013 09/2015 Road Inventory / HPMS Minimum 18 Months 09/2013 05/2015 Road Inventory / HPMS Complete 24 Months 09/2013 09/2015 Traﬃc 30 Months 09/2013 03/2016 Integrated Management System (IMS) 18 Months 04/2015 10/2016 18 Months 04/2015 10/2016 ExecuEve Dashboard EGIS Project Ac>vi>es
•  2013 Ac=vi=es •  Project Kickoﬀ – June 2013 •  Establishment of EGIS Technical and Steering CommiKees •  LRS •  Legacy Workshops and DocumentaEon •  Deﬁne FuncEonal Requirements •  HPMS, RI, and Traﬃc •  Legacy Workshops •  VideoLog •  ConﬁguraEon and TesEng 16 EGIS Project Ac>vi>es
•  2014 In Progress •  LRS •  Design Workshops •  System Architecture Workshops •  HPMS, RI, and Traﬃc •  Deﬁne and Document Requirements •  VideoLog •  InstallaEon, TesEng, and Deployment •  ProducEon Cutover •  2014 Planned •  LRS •  Data Cleansing and Pilot (Q2-‐Q3) •  Data MigraEon (Q3-‐Q4) •  Workﬂow Design •  Training •  Deploy and Support ProducEon Environment (Q4 2014 – Q1 2015) •  HPMS, RI, and Traﬃc Design and Development (Q3 2014 – 2015) 17 Thank You! Troy Marsh, GISP 678.576.5844 [email protected] www.pmgpro.com

Download Report