AALLLL R ROADOAD N NETWORKETWORK OFOF L LINEARINEAR RREFERENCEDEFERENCED D DATAATA (ARNOLD) P (ARNOLD) PHASEHASE 2 2 DDATAATA M MIGRATIONIGRATION ANDAND ESRI R ESRI ROADSOADS & &

HHIGHWAYSIGHWAYS IMPLEMENTATIONIMPLEMENTATION

PPROJECTROJECT C CHARTERHARTER F FOROR C CERTIFICATIONERTIFICATION

EXECUTIVE SPONSOR – TOM CHURCH, CABINET SECRETARY

BUSINESS OWNER – YOLANDA DURAN, CHIEF DATA MANAGEMENT BUREAU AND MEL HERRERA, GIS MANAGER

IT PROJECT MANAGER – JOANN GIRARD BUSINESS SUPPORT – INFORMATION TECHNOLOGY

BUSINESS OWNER PROJECT MANAGER – JACK YATES STAFF MANAGER ROADWAY INVENTORY PROGRAM

ORIGINAL PLAN DATE: NOVEMBER 16, 2015

REVISION DATE: N/A

REVISION:

TABLE OF CONTENTSTABLE OF CONTENTSTABLE OF CONTENTS............................................................................................................................................ I

REVISION HISTORY............................................................................................................................................. III

1. PROJECT BACKGROUND............................................................................................................................. 1

1.1 EXECUTIVE SUMMARY - RATIONALE FOR THE PROJECT................................................................................................11.2 SUMMARY OF THE FOUNDATION PLANNING AND DOCUMENTATION FOR THE PROJECT......................................................21.3 PROJECT CERTIFICATION REQUIREMENTS....................................................................................................................3

2.0 JUSTIFICATION, OBJECTIVES AND IMPACTS....................................................................................................3

2.1 AGENCY JUSTIFICATION...........................................................................................................................................32.2 BUSINESS OBJECTIVES.............................................................................................................................................42.3 TECHNICAL OBJECTIVES...........................................................................................................................................42.4 IMPACT ON ORGANIZATION......................................................................................................................................52.5 TRANSITION TO OPERATIONS....................................................................................................................................5

3.0 PROJECT/PRODUCT SCOPE OF WORK............................................................................................................ 6

3.1 DELIVERABLES.......................................................................................................................................................63.1.1 Project Deliverables...................................................................................................................................63.1.2 Product Deliverables..................................................................................................................................7

3.2 SUCCESS AND QUALITY METRICS...............................................................................................................................8

4.0 SCHEDULE ESTIMATE..................................................................................................................................... 8

5.0 BUDGET ESTIMATE...................................................................................................................................... 10

5.1 FUNDING SOURCE(S)............................................................................................................................................105.2. BUDGET BY MAJOR DELIVERABLE OR TYPE OF EXPENSE -............................................................................................105.3 BUDGET BY PROJECT PHASE OR CERTIFICATION PHASE................................................................................................11

6.0 PROJECT AUTHORITY AND ORGANIZATIONAL STRUCTURE...........................................................................11

6.1 STAKEHOLDERS...............................................................................................................................................116.2 PROJECT GOVERNANCE PLAN.........................................................................................................................136.3 PROJECT MANAGER.........................................................................................................................................14

6.3.1 PROJECT MANAGER CONTACT INFORMATION........................................................................................146.4 PROJECT TEAM ROLES AND RESPONSIBILITIES................................................................................................146.5 PROJECT MANAGEMENT METHODOLOGY..................................................................................................................16

7.0 CONSTRAINTS............................................................................................................................................. 17

8.0 DEPENDENCIES............................................................................................................................................ 17

9.0 ASSUMPTIONS............................................................................................................................................ 18

10.0 SIGNIFICANT RISKS AND MITIGATION STRATEGY........................................................................................18

11.0 COMMUNICATION PLAN FOR EXECUTIVE REPORTING................................................................................19

12.0 INDEPENDENT VERIFICATION AND VALIDATION - IV&V..............................................................................19

13.0 PROJECT CHARTER AGENCY APPROVAL SIGNATURES.................................................................................20

i

14.0 PROJECT CHARTER CERTIFICATION APPROVAL SIGNATURE........................................................................20

ii

REVISION HISTORYREVISION HISTORY

REVISION NUMBER DATE COMMENT

1.0 November 2, 2015 Original

iii

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.

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.

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 New Mexico Department of Transportation (NMDOT) was able to work directly with the FHWA and Federally contracted GIS consultants in a “Pooled Fund Study” (where the State of New Mexico DOT contributed $100,000 of the FHWA AWP funding and the FHWA contributed another $100,000) to complete the development of a roadway centerline/LRS network for all public roads. This network is slated for completion December 31, 2015. That phase of the project was designated as ARNOLD Phase 1. The NMDOT has now selected a GIS consultant from the list of DoIT authorized GIS vendors listed on Statewide price agreement to begin work on the ARNOLD Phase 2 Data Migration and ESRI Roads & Highways Implementation Project. This project, The ARNOLD Phase 2 Data Migration and ESRI Roads & Highways Implementation (ARNOLD Phase 2) will entail migration of the ARNOLD which is being built under Phase 1, to ESRI Roads & Highways as well as all associated roadway asset data stored in the current NMDOT TIMS Exor/Bentley database.  Phase 2 will allow the NMDOT to terminate usage and support for the existing Exor/Bentley database and

PAGE 1

utilize ESRI’s Roads & Highways COTS software to accomplish the same functionality with more up-to-date software and LRS editing features.

Following the Phase 2 effort, there will be a Phase 3 portion of the project which will deal with external database connectivity; however, a separate certification process will be conducted for that effort at a later date.

See Certified Public Road Mileage Data and ARNOLD, on the FHWA HPMS web site.

1.1 EXECUTIVE SUMMARY - RATIONALE FOR THE PROJECT

The ARNOLD Phase 2 Project will entail full integration and implementation of ESRI Roads & Highways including the migration of data from NMDOT’s existing Transportation Information Management System (TIMS) into the ESRI Roads & Highways Data model. The data will be referenced to the ARNOLD Linear Reference System constructed under the ARNOLD Phase 1 project and will need to meet the FHWA MAP 21 Data Requirements and agency performance measures. The ESRI Roads & Highways solution supports both desktop and web users. On the desktop, the ESRI Roads & 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 ESRI Roads & 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 & Highways support historical views as well as traceability (who edited what and when). The ESRI Roads & 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.

PAGE 2

1.2 SUMMARY OF THE FOUNDATION PLANNING AND DOCUMENTATION FOR THE PROJECT

Under separate certification, the first phase of this project is underway and entails construction of the All Road Network of Linear Referenced Data utilizing the Federal Highway Pooled Fund Study and an existing Federally managed contract.

This project, the All Road Network of Linear Referenced Data (ARNOLD) Phase 2 Data Migration and Roads & Highways implementation will entail full integration and implementation of the ESRI Roads & Highways module of ArcGIS software including migration of existing data from the NMDOT’s existing Traffic Information Management System Database (TIMS) into the ESRI Roads & Highways Database. Data Linkage with associated asset data systems such as Pavement, Bridge, Crash, Traffic Monitoring Data, Maintenance Management System, FMIS, and HSIP will be addressed under a different project (Phase 3).

1.3 PROJECT CERTIFICATION REQUIREMENTS

CRITERIA YES/NO EXPLANATION

Project is mission critical to the agency Yes Federal Requirement

Project cost is equal to or in excess of $100,000

Yes Estimated cost for this project is $477,052.00

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

PAGE 3

2.1 AGENCY JUSTIFICATION

The NMDOT Data Management Bureau needs to comply with the All Roads Network of Linear Referenced Data (ARNOLD) FHWA mandate. The final tabular and spatial data system needs to meet the FHWA MAP 21 Data Requirements and agency performance measures.

NUMBER DESCRIPTION

AGENCY NMDOT The existing TIMS database data will be migrated to the ARNOLD LRS network in ESRI’s Roads & Highways software system. The final tabular and spatial data system needs to meet the FHWA MAP 21 and Data Requirements and agency performance measures.

2.2 BUSINESS OBJECTIVES

NUMBER DESCRIPTION

BUSINESS 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.

PAGE 4

2.3 TECHNICAL OBJECTIVES

NUMBER DESCRIPTION

TECHNICAL OBJECTIVE 1 Web-based system will be designed to allow NMDOT staff internet access to data.

TECHNICAL OBJECTIVE 2 Data will be easily converted and migrated.

TECHNICAL OBJECTIVE 3 Facilitate a common data structure which will allow later 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 – migrate to a COTS system (ESRI Roads & Highways) that provides an architecture that will allow future interface with other NMDOT asset management system(s)

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 DESCRIPTION

END USER Training will be defined and all end-users within NMDOT will undergo 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

PAGE 5

AREA DESCRIPTION

PRELIMINARY OPERATIONS LOCATION AND STAFFING PLANS

Project management and scope of work adjustments 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

PAGE 6

3.0 PROJECT/PRODUCT SCOPE 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 project

Certification 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.

PAGE 7

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 Service Contracts 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 de facto 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.

PAGE 8

PAGE 9

3.2 SUCCESS AND QUALITY METRICS

NUMBER DESCRIPTION

QUALITY 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 & 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 9 months. Creation of the Phase 1 ARNOLD geodatabase is a logical step that was undertaken first and will be completed by January 2016. The remainder of the project implementation phase will continue past January 2016 with Phase 2 project completion estimated in December 2016.

PAGE 10

PHASES ESTIMATED SCHEDULE DATE

Delivery of ARNOLD “All Road” geodatabase. January 2016

Initiation February 2016

Planning March 2016

Technical Architecture Review (TARC) N/A

Implementation

Migration of data from TIMS into ESRI Roads & Highways Database. Full integration and implementation of the ESRI Roads & Highways module of ArcGIS software.

System Architecture Recommendations

Configuration of ESRI Roads & Highways desktop and Roadway Characteristic Editor

On-site system implementation

Training and support

April-December 2016

April-June 2016

April 2016

June-July 2016

September-November 2016

September-December 2016

Closing December 2016

PAGE 11

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.

Please remember to include agency staff time including project managers as costs.

5.1 FUNDING SOURCE(S)

SOURCE AMOUNT ASSOCIATED RESTRICTIONS

FEDERAL FUNDS

FHWA AWP

$477,052.00 Funding needs To comply With federal requirements associated With this project

5.2. BUDGET BY MAJOR DELIVERABLE OR TYPE OF EXPENSE -

ITEM COST ESTIMATE

Project Management $40,800.00

Review of Phase 1 Data and Information $37,621.00

Initial Design of R&H Database $29,301.00

Project Startup Workshop and Kickoff $39,555.00Migration of Existing Route and Event Data into Roads & Highways Database $62,109.00

System Architecture Recommendations $9,670.00

Configuration of R&H Desktop $77,650.00

Configuration of Roadway Characteristic Editor (RCE) $21,850.00

PAGE 12

ITEM COST ESTIMATE

On-Site System Implementation $27,787.00

Training and On-Site Support $95,419.00

PMG QA/QC Toolkit $6,400.00

IV/V $28,890.00

TOTAL PROJECT ESTIMATE $477,052.00

5.3 BUDGET BY PROJECT PHASE OR CERTIFICATION PHASE

PHASES PLANNED CERTIFICATION DATE

Initiation February 2016

Planning March 2016

Technical Architecture Review (TARC) N/A

Implementation June 2016

Closing December 2016

6.0 PROJECT AUTHORITY AND ORGANIZATIONAL STRUCTURE

6.1 STAKEHOLDERS

NAME STAKE IN PROJECT ORGANIZATION TITLE

TOM CHURCH OVERALL PROGRAM NMDOT SECRETARY

TAMARA HAAS PROGRAM ADMINISTRATIVE NMDOT EXECUTIVE MANAGER, STRATEGIC PLANNING

PAGE 13

NAME STAKE IN PROJECT ORGANIZATION TITLE

RESPONISBILTY & ASSET MANAGEMENT

JOANN GIRARD IT PROJECT MANAGER NMDOT BUSINESS SUPPORT INFORMATION TECHNOLOGY

YOLANDA DURAN BUSINESS OWNER NMDOT DATA MANAGEMENT BUREAU CHIEF

MEL HERRERA BUSINESS OWNER NMDOT GIS/GEOSPATIAL TEAM - SUPERVISOR

JACK YATES BUSINESS OWNER PROJECT MANAGER

NMDOT ROADWAY INVENTORY PROGRAM MANAGER

PAGE 14

Project Business OwnerYolanda Duran

Mel Herrera

Project Team MemberRoadway Inventory Program

Business Owner Project ManagerJack Yates

Executive Steering CommitteeTom ChurchTamara Haas

Business Operations Review Team:GIS Team

Traffic Technical SupportAsset Management DivisionData Management Bureau

Pavement ManagementHighway Safety Improvement Program

6.2 PROJECT GOVERNANCE PLAN

PAGE 15

6.3 PROJECT MANAGER

6.3.1 PROJECT MANAGER CONTACT INFORMATION

NAME ORGANIZATION PHONE #(S)

EMAIL

JOANN GIRARD NMDOT IT PROJECT MANAGER

(505) 827-5340 JOANN.GIRARD@STATE.NM.US

JACK YATES NMDOT DATA MANAGEMENT BUREAU ROADWAY INVENTORY PROGRAM

(505) 216-8059 JACK.YATES@STATE.NM.US

6.4 PROJECT TEAM ROLES AND RESPONSIBILITIES

ROLE RESPONSIBILITY

Executive Project Sponsor

The point person will be at 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

Steering Committee 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

Business Owner Person responsible to the participating entities, and who will make decisions related to the operation of the project.

Problem Solving Reviews work of Consultants Participate in changes to project Diagnose potential problems on project

PAGE 16

ROLE RESPONSIBILITY

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. Define Business needs Scheduling of meetings System Administration Testing Purchasing and processing Data integrity Data input

Technical Staff Staff assigned to defining infrastructure requirements and providing ongoing project support.

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

PAGE 17

ROLE RESPONSIBILITY

Database tools (reporting) Disaster recovery Anti-virus protection Provide OEM liaison

6.5 PROJECT MANAGEMENT METHODOLOGY

Phase Summary of Phase Key Deliverables

Initiate During initiate, the project manager of the delivery team will kick-off the project, validate the scope, facilitate the logistics and initiate the project plan.

Communication Plan

Escalation Plan

Project Management Plan

Timeline Schedule

Analysis/JAD The delivery team will conduct the analysis of DOT’s requirements and define the architecture and design of the solution. The requirements include business, technical, and functional requirements.

Onsite Kick-off Project Meeting

Project Documentation

System Requirement Specification

Build & Configuration In Build, the delivery team will configure the proposed system. It includes the installation, development and configuration and testing of components and sub-systems comprising the proposed

Software Configuration

PAGE 18

solution.

Train In this phase, the delivery team will train the Project Managers and select TSD staff for the end user training. Project Managers will train grantees

Administrative Training Manual

Onsite Administrative Training

Agency Training Manual

Deploy In this phase, the delivery team ports the system from a Test environment to Production environment and conduct the system roll out for successfully “Go-Live”

System Go-Live

Close In this phase, the delivery team ensures that every detail of the project has been addressed and proper closure is attained.

Project Closure

Project Review Meeting

Project Archival Activities

Follow-up Activities

7.0 CONSTRAINTS

NUMBER DESCRIPTION

1. Adequate resources

2. State requirements for oversight and project delays

3. Delays in processing contracts and purchasing.

8.0 DEPENDENCIES

PAGE 19

M- 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

1. DoIT oversight committee approval M

2. Contract approvals and purchases E

3. Funding for software and maintenance M

4. Design and infrastructure dependencies M

5. Data conversions M

6. Application and server installs M

7. Software management. M

9.0 ASSUMPTIONS

NUMBER DESCRIPTION

1. Adequate budget will be available

2. Adequate staffing levels

3. Staff will be trained on the use of software

4. Vendor will provide updates

5. Data will be easily converted

6. Software will integrate with other system software.

PAGE 20

NUMBER DESCRIPTION

10.0 SIGNIFICANT RISKS AND MITIGATION STRATEGY

Risk 1

Description -

Funds will not be readily available to support the project

Probability Low Impact Low

Mitigation 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

11.0 COMMUNICATION PLAN FOR 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.

12.0 INDEPENDENT VERIFICATION AND VALIDATION - IV&V

The following check list provides a high level of the type of IV&V accountability the project envisions:

Project/Product Area Include –Yes/N

PAGE 21

o

Project Management Yes

Quality Management Yes

Training Yes

Requirements Management Yes

Operating Environment Yes

Development Environment Yes

Software Development Yes

System and Acceptance Testing Yes

Data Management Yes

Operations Oversight Yes

Business Process Impact Yes

PAGE 22

13.0 PROJECT CHARTER AGENCY APPROVAL SIGNATURES

SIGNATURESIGNATURE DATEDATE

EXECUTIVE SPONSOREXECUTIVE SPONSOR

BUSINESS OWNERBUSINESS OWNER

PROJECT MANAGERPROJECT MANAGER

14.0 PROJECT CHARTER CERTIFICATION APPROVAL SIGNATURE

SIGNATURESIGNATURE DATEDATE

DOIT / PCC APPROVALDOIT / PCC APPROVAL

PAGE 23