State of New MexicoArnold Phase 1
Department of TransportationProject Management Plan
lmVersion 0.3
All Roads Network of Linear-Referenced Data (ARNOLD)Phase 1 - Network Development
PROJECT MANAGEMENT PLAN
(PMP)
Executive Sponsor – Tom Church, Cabinet Secretary
Business Owner – Yolanda Duran, Chief Data Management Bureau and Mel Herrera, GIS manager
Project Manager – Jack Yates, Staff Manager Roadway Inventory Program
IT Project Manager – Jo Girard
Original Plan Date: November 2, 2015
1st Revision: June 17, 2015
2nd Revision: June 18, 2015
3rd Revision: October 30, 2015
Revision: 0.3
Revision History
1.0 Project Overview
1.1 Executive Summary- rationale for the Project
1.2 funding and sources
1.3 constraints
1.4 dependencies
1.5 ASSUMPTIONS
1.6 Initial Project Risks Identified
2.0 Project Authority and Organizational Structure
2.1 Stakeholders
2.2 Project Governance Structure
2.2.1 Organizational Boundaries, interfaces and responsibilities
2.3 Executive Reporting
3.0 SCOPE
3.1 Project Objectives
3.1.1 Business Objectives
3.2 Critical Success Factors
4.1 Project Management Life Cycle
4.1.1 Project Management Deliverables
4.1.2 Deliverable Approval Authority Designations
4.1.3 Deliverable Acceptance Procedure
5.0 Project Work
5.1 Work Breakdown Structure (WBS)
5.2Schedule allocation -Project Timeline
5.3 Project Budget
5.4 Project Team
5.4.1 Project Team Organizational Structure
5.4.2 Project Team Roles and Responsibilities
6.0 Project Management and Controls
6.1 Risk and issue Management
6.1.1 Risk Management Strategy
6.1.2 Project Risk Identification
6.1.3 Project Risk Mitigation Approach
6.1.4 Risk Reporting and Escalation Strategy
6.1.5 Project Risk Tracking Approach
6.1.6 ISSUE MANAGEMENT
6.2 INDEPENDENT Verification And Validation - Iv&V
6.3 Scope Management Plan
6.5 Communication Plan
6.5.1 Communication Matrix
6.5.2 Status Meetings
Project status meetings (calls) will be held on a weekly basis.
6.5.3 Project Status Reports
6.6 PERFORMANCE MEASUREMENT (PROJECT METRICS)
6.7 QUALITY OBJECTIVES AND CONTROL
6.7.1 quality Standards
6.7.2 Project and Product Review AND ASSESSMENTS
6.7.3 Agency/Customer Satisfaction
6.7.4 PRODUCT DELIVERABLE ACCEPTANCE PROCESS
6.8 CONFIGURATION MANAGEMENT
6.8.1 Version Control
6.8.2 Project Repository (Project Library)
7. 0 Project Close
7.1 Administrative Close
7.2 Contract Close
AttachmentS
Revision History
Revision Number / Date / Comment0.1 / June 17, 2015 / CDM/DTS Edits
0.2 / June 18, 2015 / NMDOT Edits
0.3 / October 30, 2015 / NMDOT Edits
State of New MexicoArnold Phase 1
Department of TransportationProject Management Plan
lmVersion 0.3
1.0 Project Overview
The primary objective of the ARNOLD Phase 1 - Development and Implementation Plan is to develop NMDOT’s all-roads network (ARNOLD). The network will be developed using existing sources of information and will be designed to meet existing Federal ARNOLD and HPMS reporting requirements. In addition to developing the initial network geometry and linear referencing system, the study will also provide recommended strategies for the long-term maintenance of the network and LRS and support for routing and address location.
1.1 Executive Summary- rationale for the Project
The Highway Performance Monitoring System (HPMS) Field Manual includes a requirement for States to provide a linear referencing system (LRS) network for all Federal-aid eligible roads as part of their annual HPMS submittal. The LRS network is used to locate and display all HPMS data items on a map for quality control purposes and for subsequent analysis using geospatial and network analysis techniques. FHWA expanded the requirement for the LRS network to include all public roads, including dual carriageways on divided highways. This expanded All Roads Network of Linear-Referenced Data (ARNOLD) addresses specific legislation included in the latest Federal surface transportation reauthorization, “Moving Ahead for Progress in the 21st Century” (MAP-21). This is Phase 1 of the overall project
In an October 7, 2012 memorandum, FHWA expanded the requirement for the LRS network to include all public roads, including dual carriageways on divided highways. This expanded All Roads Network of Linear-Referenced Data (ARNOLD) addresses specific legislation included in the latest Federal surface transportation reauthorization (MAP-21) that the Highway Safety Improvement Program (HSIP) for each State shall establish a safety data system covering all public roads, including non-State-owned public roads and roads on tribal land in the State in a geospatial manner. In other words, State highway agencies will have a geospatially enabled public roadway network or base map that can be used to locate crashes and other relevant highway information (e.g., bridges) that are not on the state maintained highway system (i.e., off-system roads).
The Phase 2 for this project will include the full Integration and implementation of the ESRI Roads and Highways including the migration of data from TIMS into Roads and Highways Database. Phase 3 is the data linkage with Asset data requirements such as Pavement, Bridge, Crash, Traffic Monitoring Data, Roadway Inventory Assets, Maintenance Management System, FMIS, and HSIP. The ESRI Roads and Highways solution supports both desktop and web users. On the desktop, the ESRI Roads and Highways solution provides DOT with an interface for defining routes, registering events (such as road inventory data elements, bridges, crashes, and pavement), and adding event behavior.The web implementation, the Roadway Characteristics Editor (RCE), is focused around leveraging the LRS (Linear Reference System) to maintain certain roadway characteristics event data. RCE provides DOT with a simple interface for updating event data to easily attribute a highway. External database linkages will allow externally stored and maintained asset data to be linked to the Roads and Highways maintained LRS. Event editing functions are provided in the RCE web application to reduce the level of effort required to maintain highway attributes. ESRI Roads and Highways support historical views as well as traceability (who edited what and when). The ESRI roads and Highways solution and the underlying ESRI Roads & Highways Data Model will also address DOT’s reporting requirements (those internal to DOT as well as state and federal government reporting requirements such as the Federal Highway Administration FHWA) Highway Performance Monitoring System (HPMS), annual Certification of Public Mileage, and other reporting requirements). For the HPMS submittal, the R&H COTS data model contains placeholders for the required elements of the HPMS submittal. The application provides tools and configurable workflows to support the maintenance of HPMS data stored and managed in the geodatabase. For other report products R&H provides the means to modify the standard data model with the data elements needed to support those reports and the capability to integrate with other software vendor’s reporting tools to create standard report products as well as ad hoc queries that can be exported as data files that can then be used to create report products that are tailored to a specific user’s needs.
1.2 funding and sources
Source / Amount / Associated restrictions / ApproversNMDOT FHWA Annual Work Plan (AWP) / $30,000.00 / FHWA / Yolanda Duran
And Jack Yates
NMDOT FHWA Annual Work Plan (AWP) / $100,000 / FHWA / Yolanda Duran
And Jack Yates
FHWA Pooled Fund / $100,000 FHWA Funded / FHWA / FHWA
1.3 constraints
Number / DescriptionProject activities must be approved by FHWA and meet ARNOLD PFS objectives
Adequate resources
State requirements for oversight and project delays
delays in processing contracts and purchasing
1.4 dependencies
Types include the following and should be associated with each dependency listed.
- Mandatory dependencies are dependencies that are inherent to the work being done.
- D- Discretionary dependencies are dependencies defined by the project management team. This may also encompass particular approaches because a specific sequence of activities is preferred, but not mandatory in the project life cycle.
- E-External dependencies are dependencies that involve a relationship between project activities and non-project activities such as purchasing/procurement
Number / Description / Type M,D,E
DOIT oversight committee approval / M
Funding for project / M
Design and infrastructure dependencies / M
Data conversions / m
1.5 ASSUMPTIONS
Assumptions are planning factors that, for planning purposes, will be considered true, real, or certain.
Number / DescriptionAdequate budget will be available
Adequate staffing levels
Staff will be trained on the use of data
Vendor will provide training
Data will be easily converted
1.6 Initial Project Risks Identified
RISK 1: Failure to meet Federal Requirements and Deadline
Description – Funds will not be readily available to support the project / Probability Very Low / Impact LowMitigation Strategy: Allocate funding in excess of projected funding needs.
Contingency Plan: If this occurs, NMDOT staff will need to implement solution independently without vendor assistance or guidance.
RISK 2: Suitability of DPS/ProMiles data for ARNOLD
Description – DPS/ProMiles data may not meet the ARNOLD data requirements / Probability Medium / Impact HighMitigation Strategy: Evaluate DPS/ProMiles Data for ARNOLD Suitability
Contingency Plan: Implement an alternate data migration plan for ARNOLD leveraging TIMS data supplemented by DPS/ProMiles data on local roads.
RISK 3: Too many project goals to accomplish by April 2016
Description – Project starting too late to accomplish all ARNOLD goals / Probability Low / Impact LowMitigation Strategy: Determine what project goals are feasible to accomplish by April 2016
Contingency Plan: Initiate a prototype project for migrating an initial set of data from DPS/ProMiles by June 15 while initiating a planning project for the full implementation in parallel.
2.0 Project Authority and Organizational Structure
2.1 Stakeholders
name / Stake in Project / Organization / Title / Contact InformationJoe Hausman / ARNOLD Program Manager, HPMS program review coordinator / FHWA / FHWA ARNOLD Program Manager
Tom Church / Executive Sponsor / NMDOT / Planning & Asset Management Division Director
Tammy Haas / Business Owner / NMDOT / Asset Management and Planning Chief / 505-795-2126
Yolanda Duran / Business Owner / NMDOT / Data Management Bureau Chief / 505‐827‐0961
Mel Herrera / GIS / NMDOT / GIS Manager / 505-827-5453 office
Jack Yates / Project Manager / NMDOT / Roadway Inventory Program Manager / 505-216-8059
Jo Girard / IT Project Manager / NMDOT / IT Project Manager / 505-827-5340
Jeff Woodman / Application Support / NMDOT / Application Support Bureau Chief / 505-827-5289
Ganesh Singh / Application Support / NMDOT / IT Generalist / 505-827-0902
Namobael Frostad / Application Support / NMDOT / IT Application Support / 505-827-2875
Kevin Karns / Application Support / NMDOT / IT DBA / 505-827-5293
2.2 Project Governance Structure
2.2.1 Organizational Boundaries, interfaces and responsibilities
Role / ResponsibilityExecutive Sponsor/ Steering Committee / The point person will be the highest level of NMDOT.
Responsibilities include:
- Champion Project
- Consider changes facing the organization and its impacts
- Responsible for finding budget to complete project
- Participate in planning sessions
- Ultimate project responsibility
Business Owner /
- Tasked with overall direction and support of the project
- Participate in meetings
- Review and accept deliverables
- Review and provide comment on documentation provided by project team.
- Review project funding and its sources
Project Manager(s) / Person responsible to the participating entities that make decisions related to the operation of the project.
- Problem Solving
- Reviews work of Consultants
- Scheduling of meetings
- Participate in changes to project
- Diagnose potential problems on project
- Determine roles of IT personnel
- Ultimate project success
- Budget Planning
- Project Schedule
- Training Plans
- Contract Management
- Ensure communications between vendor and project owner.
Project Team Members / Staff assigned to Project
- Contract Support
- Document Support
- Define Business needs
- System Administration
- Testing
- Data integrity
- Data input
Technical Staff / Staff assigned to defining infrastructure requirements and providing support to project indefinitely.
Duties Include:
- System infrastructure Specifications
- Integration of other NMDOT systems
- Data backups
- Storage requirements
- Security
- Data Migration
- Systems install and updates
- Network connectivity
- Provide test/development environments
- System maintenance
- System reporting
- Database tools (reporting)
- Disaster recovery
- Anti-virus protection
2.3 Executive Reporting
The Project Manager will be responsible for creating periodic internal reports for NMDOT stakeholders and will assist in preparing materials for presentation to DoIT and the PCC. The Project Manager will work in conjunction with the Technical Lead and the vendor to gather data for these reports.
3.0 SCOPE
Task1 - Project Management
2 - ARNOLD Planning and Review
3 - Development of the All Roads Network
4 - ARNOLD Maintenance Strategic Plan
5 – IV/V
3.1 Project Objectives
3.1.1 Business Objectives
Number / DescriptionBus. Objective 1 / All Roads Network Development Planning and Review
Bus. Objective 2 / Development of the All Roads Network
Bus. Objective 3 / Develop ARNOLD Maintenance Strategic Plan
Bus. Objective 4 / Increased efficiency and productivity through a well-managed linear referencing system
Bus. Objective 5 / Optimize business process, decreasing number of steps, saving time
Bus. Objective 6 / Lower the cost of government by having a more efficient work activity process tracking
Bus. Objective 7 / Improve reporting capability to Executive Management & FHWA
3.2 Critical Success Factors
Number / DescriptionQuality Metrics 1 / Project does not exceed budget
Quality Metrics 2 / The project schedule, assigned tasks and milestones are met within project plan
4.0 Project Deliverables and methodology
4.1 Project Management Life Cycle
Phase / Summary of Phase / Key DeliverablesInitiation / Project Status Reports / Project Status Reports
Planning / Project Management Plan / Project Management Plan
Planning / ARNOLD Development Plan / ARNOLD Development Plan
Implementation / Develop All Roads Network centerline file with LRS / All Roads Network file with LRS
Implementation / Pilot submission of All Roads Network to FHWA to verify that it meets requirements / Pilot Submission of Network to FHWA
Implementation / Develop All Roads Network centerline file with LRS / High-Level Plan for Roads & Highways Migration
Closure / Develop the ARNOLD Strategic Maintenance Plan / ARNOLD Strategic Maintenance Plan
4.1.1 Project Management Deliverables
4.1.1.1 Project Status Reports
Description – Project Status Report / Deliverable Acceptance Criteria – N/AStandards for Content and Format – Progress report format contained in Communication Plan in Attachment D
Quality Review – N/A
4.1.1.2Project Management Plan
Description – Project Management Plan / Deliverable Acceptance Criteria – N/AStandards for Content and Format – Project Plan included as Attachment A
Quality Review – N/A
4.1.1.3 ARNOLD Development Plan
Description - (SOW Task 2)ARNOLD Development Plan / Deliverable Acceptance Criteria - NMDOT Approval
Standards for Content and Format - FHWA ARNOLD requirements.
Quality Review - NMDOT staff reviewing the draft deliverable and providing comments and suggested revisions. NMDOT comments will be synthesized and compiled into one document by the NMDOT and provided to CDM who will update the network and provide the updated draft.
4.1.1.4All Roads Network file with LRS
Description - Develop All Roads Network centerline file with LRS / Deliverable Acceptance Criteria – Network contains all required roads, route IDs, and route measures (LRS).Standards for Content and Format – FHWA ARNOLD requirements.
Quality Review - NMDOT staff reviewing the draft deliverable and providing comments and suggested revisions. NMDOT comments will be synthesized and compiled into one document by the NMDOT and provided to CDM who will update the network and provide the updated draft.
4.1.1.5 Pilot Submission of Network to FHWA
Description - Pilot submission of All Roads Network to FHWA to verify that it meets requirements / Deliverable Acceptance Criteria - Approval of pilot submission by FHWA.Standards for Content and Format – FHWA ARNOLD requirements.
Quality Review –FHWA HPMS Data Upload Validation scripts
4.1.1.6 High-Level Plan for Roads & Highways Migration
Description - Develop All Roads Network centerline file with LRS / Deliverable Acceptance Criteria - Approval of pilot submission by FHWA.Standards for Content and Format - Contains all state and local public roads, route measures, dual carriageways where appropriate.
Quality Review –Conducted by both NMDOT and FHWA staff
4.1.1.7 NMDOT ARNOLD Strategic Maintenance Plan
Description –Develop the ARNOLD Strategic Maintenance Plan / Deliverable Acceptance Criteria - Approval of Strategic Maintenance Plan.Standards for Content and Format –FHWA and industry GIS standards of practice.
Quality Review - NMDOT Staff will determine if recommendations can be supported at the NMDOT.
4.1.2 Deliverable Approval Authority Designations
Deliverable Number / Deliverable / Approvers (Who can approve) / Date ApprovedPRJ-DEL-001 / Project Status Reports / Yolanda Duran,
Jack Yates
Joann Girard
PRJ-DEL-002 / Project Management Plan (PMP) / Yolanda Duran,
Jack Yates
Joann Girard / 6/18/2015
PRJ-DEL-003 / ARNOLD Development Plan / Yolanda Duran,
Jack Yates
Joann Girard / 9/8/2015
PRJ-DEL-004 / All Roads Network file with LRS / Yolanda Duran,
Jack Yates
Joann Girard
PRJ-DEL-005 / Pilot Submission of Network to FHWA / Yolanda Duran,
Jack Yates
Joann Girard
PRJ-DEL-006 / High-Level Plan for Roads & Highways Migration / Yolanda Duran,
Jack Yates
Joann Girard / 9/8/2015
PRJ-DEL-007 / ARNOLD Strategic Maintenance Plan / Yolanda Duran,
Jack Yates
Joann Girard
4.1.3 Deliverable Acceptance Procedure
Deliverables will consist of documents and data, not software. Deliverables will be submitted electronically to the NMDOT Project Manager for review and acceptance. A note of acceptance should be issued by the NMDOT Project Manager.
5.0Project Work
5.1 Work Breakdown Structure (WBS)
Identifier / Work Package Description / Definition/Objective / Milestone/DeliverableProject Status Reports / Project Status / Ongoing Progress Calls & Monthly Status Report
Project Management / Project Management / PMP
All Roads Network Development Planning Review / Review existing resources, create plan for developing GIS network / Development plan document
Development of the All Roads Network / Develop all roads network including LRS / All road network
Pilot Submission of Network to FHWA / Data to FHWA / Data submission
High-Level Plan for Roads & Highways Migration / Roads & Highway Implementation / Roads & Highway Implementation Plan
Develop ARNOLD Maintenance Strategic Plan / Develop long-term maintenance plan for network / Maintenance plan document
5.2Schedule allocation -Project Timeline