All Roads Network of
Linear Referenced Data (ARNOLD)
Project Charter For Certification
Executive Sponsor – Tom Church, Cabinet Secretary
Business Owner – Yolanda Duran, Chief Data Management Bureau and Mel Herrera, GIS manager
IT Project Manager - Genevieve Grant Business Support – Information Technology
Business Owner Project Manager – Jack Yates Staff Manager Roadway Inventory
Original Plan Date: September 8, 2014
Revision Date: SEPTEMBER 12, 2014
Revision: 1.3
table of contents
table of contents
Revision History
1.project background
1.1Executive Summary - rationale for the project
1.2Summary of the foundation planning and documentation for the project
1.3 Project Certification Requirements
2.0 Justification, Objectives and impacts
2.1 Agency Justification
2.2 Business Objectives
2.3 Technical Objectives
2.4 Impact on Organization
2.5 Transition to Operations
3.0 Project/Product Scope of Work
3.1 Deliverables
3.1.1 Project Deliverables
3.1.2 Product Deliverables
3.2 Success and Quality Metrics
4.0 Schedule Estimate
5.0 Budget Estimate
5.1 Funding Source(s)
5.2. Budget By Major Deliverable or Type of expense -
5.3 Budget By Project Phase or Certification Phase
6.0 Project Authority and Organizational Structure
6.1 STAKEHOLDERS
6.2 PROJECT GOVERNANCE PLAN
6.3 PROJECT MANAGER
6.3.1 PROJECT MANAGER CONTACT INFORMATION
6.4 PROJECT TEAM ROLES AND RESPONSIBILITIES
6.5 Project management Methodology
7.0 Constraints
8.0 Dependencies
9.0 Assumptions
10.0 Significant Risks and Mitigation Strategy
11.0 COMMUNICATION PLAN FOR EXECUTIVE REPORTING
12.0 INDEPENDENT VERIFICATION AND VALIDATION - IV&V
13.0 Project Charter Agency Approval Signatures
14.0 Project Charter Certification Approval Signature
Revision History
Revision Number / Date / Commentversion 1.0 / September 8, 2014 / Incorporated internal NMDOT comments.
Version 1.2 / September 11, 2014 / DoIT e-review
version 1.3 / September 12, 2014 / Incorporated DoIT’s comments.
1
Project Charter For All Roads Network of Linear Referenced Data
1.project background
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.
In anOctober 7, 2012 memorandum, the Federal Highway Administration (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). MAP-21 specifies 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).
This process is required by the New Mexico Department of Transportation (NMDOT) to complete development of a roadway centerline/LRS network for all public roads over the next 9 months in time for it to be used as the basis for submittal of both the 2014 Certified Public Road Mileage (CPRM), due June 1, 2015 and the 2014 HPMS, due June 15, 2015.
See Certified Public Road Mileage Data and ARNOLD, on the FHWA HPMS web site.
The latest Federal surface transportation legislation (MAP-21) prescribes that the Highway Safety Improvement Program 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. The FHWA is asking all State highway agencies to submit such network as either part of the HPMS submittal or the certified public road mileage submittal to facilitate FHWA's review and acceptance of the certified road data. The geospatial network will enable FHWA's review and acceptance of the certified public roadway mileage information in a timelier manner and with greater accuracy, efficiency and precision.
1.1Executive Summary -rationale for the project
Full Integration and implementation of the Environmental Systems Research Institute (ESRI) Roads and Highways including the migration of data from the Transportation Information Management System (TIMS) into NMDOT’s Roads and Highways Database. NMDOT Data Management needs to comply with the All Roads Network of Linear Referenced Data (ARNOLD) deadline of June 15, 2015. 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 FHWA MAP 21 Data Requirements and agency performance measures. The ESRI Roads and Highways solution supports both desktop and web users. On the desktop, the ESRI Roads and Highways solution provides NMDOT 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 NMDOT’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). ESRI’s Roads & Highways data model contains placeholders for the required elements of the HPMS submittal ready to use in the Commercial-Off-the-Shelf version. 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.2Summary of the foundation planning and documentation for the project
The First phase of this project would entail anEnterprise LRS and Road Inventory Discovery Workshop and Implementation Planning. This would include identifying the current status of LRS/Data and equipment and IT support requirements including development of System Requirement and Specification and Technical Architecture Review Committee documents. A Joint Application Design session as well as Independent Validation and Verification will also be conducted during this phase.
The Second Phase of this project will entail aggregation and conflation of New Mexico Municipal Planning Organization, City, County, State, Federal and Tribal “All Road” geodatabase data to one master road network geodatabase (the All Roads Network of Linear Referenced Data referred to by the Federal Highway Administration as ARNOLD).
The Third Phase of the project will entail full integration and implementation of the ESRI Roads and Highways module of ArcGIS software including migration of existing data from the NMDOT’s TIMS into the ESRI Roadsand Highways Database. Data Linkagewith Asset data requirements such as Pavement, Bridge, Crash, Traffic Monitoring Data, Roadway Inventory Assets, Maintenance Management System, FMIS, and HSIP. The final tabular and spatial data system needs to meet the FHWA MAP 21 DataRequirements and agencyperformance measures.
1.3 Project Certification Requirements
CRITERIA / YES/NO / EXPLANATIONProject is mission critical to the agency / Yes / Federal Requirement
Project cost is equal to or in excess of $100,000 / Yes / Estimated cost for entire project is $1,400,000
Project impacts customer on-line access / No / N/A
Project is one deemed appropriate by the Secretary of the DoIT / Yes / Meets NM IT Strategic Plan objectives sponsored by DoIT
Will an IT Architecture Review be required? / Yes / Architecture review will be conducted after the project plan is complete
2.0 Justification, Objectives and impacts
2.1 Agency Justification
The NMDOT Data Management Bureau needs to comply with the All Roads Network of Linear Referenced Data (ARNOLD) deadline of June 15, 2015. Data Linkage with Asset data requirements such as Pavement, Bridge, Crash, Traffic Monitoring Data, Roadway Inventory Assets, Maintenance Management System, FMIS, and HSIP. The final tabular and spatial data system needs to meet the FHWA MAP 21 DataRequirements and agencyperformance measures.
Number / DescriptionAgency NMDOT / Development of standardized road centerline that can be usedfor Data Linkage with Asset data requirements such as Pavement, Bridge, Crash, Traffic Monitoring Data, Roadway Inventory Assets, Maintenance Management System, FMIS, and HSIP. The final tabular and spatial data system needs to meet the FHWA MAP 21 DataRequirements and agencyperformance measures.
2.2 Business Objectives
Number / DescriptionBusiness Objective 1 / Increased efficiency and productivity through a well-managed linear referencing system
business objective 2 / Optimize business process, decreasing number of steps, saving staff time and training cost
business objective 3 / Lower government service costs by enacting a more efficient work flow with more accurate business process tracking
business objective 4 / Improve reporting clarity and capability to executive management
business objective 5 / Substantial NMDOT business process improvements are achievable through a system that is integrated with our maintenance management system, pavement management system, bridge and safety data.
business objective 6 / Successful integration and implementation of the all roads network of linear referenced data which meets the FHWA MAP 21 data requirements and agency performance measures.
2.3 Technical Objectives
Number / DescriptionTechnical Objective 1 / Web-based system will be designed to allow NMDOT staff remote access
teCHnical objective 2 / Data will be easily converted and migrated.
teCHNIcal objective 3 / Data linkage with asset data requirements such as pavement, bridge, crash, traffic monitoring data, roadway inventory assets, maintenance management system, FMIS and HSIP.
teCHnical objective 4 / System interface – provide an architecture that will interface with asset management system
technical objective 5 / Security/user roles – system will support a secure front end user system log in and security role level authentication
technical objective 6 / Extensibility – ensure system is designed to easily allow the addition of new features later, using an application programming interface or plug-ins.
technical objective 7 / Redundancy – system will be configured to support system fail over
2.4 Impact on Organization
Area / DescriptionEnd user / Training will be defined and all end-users within NMDOT willundergo training. Tests will be conducted with random end-users to ensure performance and ease of use.
Business Processes / General procedures for handling maintenance and updates to data will change with the implementation of the contract.
It Operations and staffing / Training will be defined and all it operations staff will be thoroughly trained. Tests will be conducted with each key staff member to ensure performance and ease of use.
2.5 Transition to Operations
Area / DescriptionPreliminary Operations location and staffing plans / Project management and scope of workadjustments will ensure the new system is run in parallel with the old system before final system deployment. Status reports will be delivered bi-weekly.
Data Security, Business Continuity / Security parameters for data will be built into system to include any information that is deemed confidential by law. This is an internal system for agency employees.
Maintenance Strategy / Annual software/hardware maintenance agreement from vendor. Specific deliverables will be in a binding contract agreement.
Interoperability / All hardware/software components are industry standard and compatible with NMDOT’s platform and security requirements.
Record retention / Retention policies will be built into new system
3.0 Project/ProductScope of Work
3.1 Deliverables
3.1.1 Project Deliverables
Project Charter / The Project Charter for Certification sets the overall scope for the project, the governance structure, and when signed is considered permission to proceed with the project. The Project Charter for Certification is used to provide the Project Certification Committee with adequate knowledge of the project and its planning to certify the initiation phase of the projectCertification Form / The Request for Certification and Release of Funds form is submitted when a project goes for any of the certification phases. It deals with the financial aspects of the project, as well as other topics that indicate the level of planning that has gone into the project. Many of the questions have been incorporated into the preparation of the project charter
Project Management Plan / A formal document approved by the executive sponsor and the Department and developed in the plan phase used to manage project execution, control, and project close. The primary uses of the project plan are to document planning assumptions and decisions, facilitate communication among stakeholders, and documents approved scope, cost and schedule baselines. A project plan includes at least other plans for issue escalation, change control, communications, deliverable review and acceptance, staff acquisition, and risk management.
IV&V Contract & Reports / “Independent Verification and Validation (IV&V)” means the process of evaluating a project to determine compliance with specified requirements and the process of determining whether the products of a given development phase fulfill the requirements established during the previous stage, both of which are performed by an organization independent of the lead agency. Independent verification and validation assessment reporting. The Department requires all projects subject to oversight to engage an independent verification and validation contractor unless waived by the Department.
IT Service Contracts / The Department of Information Technology and the State Purchasing Division of General Services have established a template for all Professional ServiceContracts related to IT.
Risk Assessment and Management / Prepare a written risk assessment report at the inception of a project and at end of each product development lifecycle phase or more frequently for large high-risk projects. Each risk assessment shall be included as a project activity in project schedule.
Project Schedule / A tool used to indicate the planned dates, dependencies, and assigned resources for performing activities and for meeting milestones. The defacto standard is Microsoft Project.
Monthly Project Status Reports to DoIT / For all projects that require Department oversight, the lead agency project manager shall submit an agency approved project status report on a monthly basis to the Department.
Project Closeout Report / The last phase of the certification process, including lessons learned throughout this project.
3.1.2 Product Deliverables
System Requirement Specification (SRS) / The SRS defines the business, functional, and technical requirements and design of the system. It includes screen mockups, system security level, and network architecture requirements.System and Acceptance Testing / The Test Plan defines the use cases to test the system. The use cases are drawn from the SRS requirements.
Operations and Support Plan / The Operation and Support Plan defines the tier level support of the system.
3.2Success and Quality Metrics
Number / DescriptionQuality Metric 1 / Project does not exceed budget
quality metric 2 / The project schedule, assigned tasks and milestones are met within project plan
quality metric 3 / System can provide reports
quality metric 4 / Successful integration and implementation of ESRI roads and highways data migration
quality metric 5 / System is secure and stable
quality metric 6 / Staff is trained to maintain system and system is operable
quality metric 7 / Data integrity is maintained.
4.0 Schedule Estimate
This project will be undertaken over the next 21 months; however, the NMDOT is under Federal mandate to provide a portion of this project (the ARNOLD “All Road” geodatabase) by June 15, 2015. Creation of this geodatabase is a logical step that has to be undertaken at the beginning of the project and could be completed by June 2015 to meet the Federal deadline. The remainder of the project implementation phase will continue past the June 2015 ARNOLD deadline with project completion estimated in June 2016.
phases / eSTIMATED SCHEDULE DATEInitiation / September 2014
Planning / October - November 2014
Technical Architecture Review (TARC) / December 2014
Implementation / January 2015 – May 2016
Delivery of ARNOLD “All Road” geodatabase to meet Federal reporting submittal deadline. / June 2015
Migration of data from TIMS into RoadsandHighways Database. Data Linkagewith Asset data requirements such as Pavement, Bridge, Crash, Traffic Monitoring Data, Roadway Inventory Assets, Maintenance Management System, FMIS, and HSIP. Full integration and implementation of the ESRI Roads and Highways module of ArcGIS software. / April 2016
Closing / June 2016
5.0 Budget Estimate
Within the Project Charter budgets for the project can only be estimated. Original budgets requested in appropriations or within agency budgets are probably not the numbers being worked with at project time. Funding sources are asked for to help evaluate the realism of project objectives against funding, and the allocation of budget estimates against project deliverables.