NM Department of Transportation ( NMDOT) All Roads Network of Linear Referenced Data (ARNOLD)

1. NM Department of Transportation (NMDOT)All Roads Network of Linear Referenced Data(ARNOLD) Executive Sponsor: Tom Church, Cabinet Secretary Business Owners: Yolanda Duran, NMDOT Data Management Bureau Mel Herrera, GIS/Geospatial Team - Supervisor Jack Yates, Roadway Inventory Program Genevieve Grant Business Support IT Project Manager Project Certification for Initiation September 8, 2014

2. Project Goals and Deadline Full Integration and implementation of the Environmental Systems Research Institute (ESRI) Roads and Highways module of ARCGIS. Migration of data from the Transportation Information Management System (TIMS) into NMDOT’s Roads and Highways Database. Data Linkage with Asset data requirements such as Pavement, Bridge, Crash, Traffic Monitoring Data, Roadway Inventory Assets, Maintenance Management System, Fiscal Management Information System (FMIS), and the Highway Safety Improvement Program (HSIP). This Linear Reference System needs to meet the Federal Highway Administration (FHWA) data requirements for the federal “Moving Ahead for Progress in the 21st Century” (MAP-21) act, and meet NMDOT’s performance measures. NMDOT Data Management needs to comply with the All Roads Network of Linear Referenced Data (ARNOLD) deadline of June 15, 2015.

3. Business Problems Current system: • …is cumbersome and not Windows-intuitive, requiring an 18-month learning curve to proficiently utilize the system. • …is relative inaccessible to NMDOT’s staff supporting Geographic Information Systems (GIS) and the Rural Infrastructure Program (RIP). Requests for data exports, summary tabulation must go through NMDOT’s IT Division. • …does not link to other department databases such as pavement and bridge.

4. Business Problems Cont’d Current system: • … requires a complicated process to upload bulk data files. • …must use ArcMap 9.3., a number of versions behind current ArcMap technology and associated functions and analytical tools. • …requires use of Internet Explorer 8 for tabular data editing.

5. Desired Outcomes A Linear Referencing System (LRS) that meets the MAP 21 ARNOLD requirements Data Linkage with Asset data requirements such as Pavement, Bridge, Crash, Traffic Monitoring Data, Roadway Inventory Assets, Maintenance Management System, FMIS, and HSIP A more user-friendly design for database data import, query and reporting Ability to readily transform GPS coordinates to linear reference system mile points and vice-versa.

6. Business Opportunity Meet Map 21 Highway Performance Monitoring System (HPMS) and Highway Safety Improvement Program (HSIP) Requirements Provide an easy means to validate NM-certified mileage Meet the expanded MAP 21 LRS requirement “to cover all public roads including representation of dual carriageways on divided highways” and related highway facilities (e.g., ramps). Opportunity to implement the expanded requirements, based on best practices identified by other State DOTs.

7. Cost Savings • Reduced staff time due to increased efficiency and productivity by utilizing a single, state-wide, well implemented linear reference system • Lower government service costs due to more efficient work flows and more accurate business process tracking, data entry, auditing, and reporting of information • Utilization of a much more familiar, user-friendly software interface will greatly reduce staff training time and costs.

8. Risk of Keeping the Status Quo • Loss of federal funds due to inadequate reporting • Further degradation of the data quality due to inability to stay current with necessary updates • Current system does not meet the Federal Highway Performance Monitoring System (HPMS) nor their Model Inventory of Roadway Elements (MIRE) data requirements, and it uses outdated technology • Many manual processes needed to produce reports required by FHWA • Maintaining multiple LRS systems and databases.

9. Project Phases and Deliverables

10. Total Cost of Ownership

11. Questions?