NEW MEXICO E-CITATION PROJECT P R OJ EC T CHA R TER FOR C ER T IFIC A TION EXECUTIVE SPONSORS: TOM CHURCH, CABINET SECRETARY DESIGNATE KATHRYN BENDER, DEPUTY SECRETARY, PROGRAMS AND INFRASTRUCTURE TAMARA P. HAAS, DIRECTOR, OFFICE OF ASSET MANAGEMENT MICHAEL SANDOVAL, DIRECTOR, PLANNING AND SAFETY DIVISION ERIC ROYBAL, ACTING CHIEF INFORMATION OFFICER BUSINESS OWNER: MICHAEL SANDOVAL, DIRECTOR, PLANNING AND SAFETY DIVISION PROJECT ANALYST: ANTHONY APODACA, PLANNING AND SAFETY DIVISION ORIGINAL PLAN DATE: DECEMBER 4, 2013 REVISION DATE: JANUARY 15 2014 REVISION: 1.1 TABLE OF CONTENTS TABLE OF CONTENTS ............................................................................................................................................ I 1. PROJECT BACKGROUND .............................................................................................................................1 1.1 EXECUTIVE SUMMARY -RATIONALE FOR THE PROJECT ....................................................................................1 1.2 SUMMARY OF THE FOUNDATION PLANNING AND DOCUMENTATION FOR THE PROJECT .....................................1 1.3 PROJECT CERTIFICATION REQUIREMENTS ...........................................................................................................2 2.0 JUSTIFICATION, OBJECTIVES AND IMPACTS ..........................................................................................4 2.1 AGENCY JUSTIFICATION ......................................................................................................................................4 2.2 BUSINESS OBJECTIVES .........................................................................................................................................4 2.3 TECHNICAL OBJECTIVES ......................................................................................................................................4 2.4 IMPACT ON ORGANIZATION .................................................................................................................................5 2.5 TRANSITION TO OPERATIONS ...............................................................................................................................5 3.0 PROJECT/PRODUCT SCOPE OF WORK .......................................................................................................6 3.1 DELIVERABLES ....................................................................................................................................................6 3.1.1 Project Deliverables....................................................................................................................................6 3.1.2 Product Deliverables ..................................................................................................................................6 3.2 SUCCESS AND QUALITY METRICS ........................................................................................................................7 4.0 SCHEDULE ESTIMATE .....................................................................................................................................8 5.0 BUDGET ESTIMATE ..........................................................................................................................................9 5.1 FUNDING SOURCE(S)............................................................................................................................................9 5.2. BUDGET BY MAJOR DELIVERABLE OR TYPE OF EXPENSE – ................................................................................9 5.3 BUDGET BY PROJECT PHASE OR CERTIFICATION PHASE.................................................................................... 10 6.0 PROJECT AUTHORITY AND ORGANIZATIONAL STRUCTURE ......................................................... 11 6.1 STAKEHOLDERS ........................................................................................................................................... 11 6.2 PROJECT GOVERNANCE PLAN .................................................................................................................. 12 6.3 PROJECT MANAGER ..................................................................................................................................... 13 6.3.1 PROJECT MANAGER CONTACT INFORMATION ................................................................................ 13 12.3.2 PROJECT MANAGER BACKGROUND ........................................................................................ 13 6.4 PROJECT TEAM ROLES AND RESPONSIBILITIES ................................................................................... 13 6.5 PROJECT MANAGEMENT METHODOLOGY ........................................................................................................... 15 7.0 CONSTRAINTS .................................................................................................................................................. 15 8.0 DEPENDENCIES ................................................................................................................................................ 16 9.0 ASSUMPTIONS .................................................................................................................................................. 16 10.0 SIGNIFICANT RISKS AND MITIGATION STRATEGY ........................................................................... 17 11.0 COMMUNICATION PLAN FOR EXECUTIVE REPORTING .................................................................. 17 12.0 INDEPENDENT VERIFICATION AND VALIDATION - IV&V ............................................................... 18 13.0 PROJECT CHARTER AGENCY APPROVAL SIGNATURES .................................................................. 19 14.0 PROJECT CHARTER CERTIFICATION APPROVAL SIGNATURE ..................................................... 19 i Revision History REVISION NUMBER DATE COMMENT 1.0 December 4, 2013 Original Document 1.1 January 15, 2014 Revisions for PCC Certification ii PROJECT CHARTER DOT E-CITATIONS PROJECT 1 1. PROJECT BACKGROUND 1.1 EXECUTIVE SUMMARY -RATIONALE FOR THE PROJECT The New Mexico E-Citation project is a multi-phase, multi-year program designed for the purpose of integrating the Traffic and Criminal Software (TraCS), utilized by Law Enforcement Agency (LEA) personnel for issuing electronic citations, with the Odyssey Court Case Management systems utilized by County Magistrate Courts in New Mexico. The proposed project will provide a seamless integration of the electronic citation data, issued from the TraCS software by law enforcement agencies, to the Odyssey Case Management system. The automation will eliminate redundant data entry, currently performed by court personnel, and reduce manual keystroke errors. The E-Citation project will improve the timeliness, completeness, uniformity, and integration of driver and vehicle information needed by the courts in New Mexico. The E-Citation project supports New Mexico’s larger goal of collecting and sharing Traffic Safety Data with internal and external stakeholders, to identify priorities for National, State, Local, and Tribal highway safety programs. The Statewide Traffic Records Executive Oversight Committee (STREOC) members and the Statewide Traffic Records Coordinating Committee (STRCC) members represent many New Mexico agencies that create, share, and report on traffic records data. Since 2002, STREOC has provided oversight and policy direction to the STRCC, and facilitated the establishment of a long-range strategic plan for traffic record system improvements. The STRCC Strategic Plan was developed and adopted by the STREOC and the STRCC in December 2002, with the latest update approved in December 2012. This STRCC Strategic plan includes the concept behind the E-Citation project. 1.2 SUMMARY OF THE FOUNDATION PLANNING AND DOCUMENTATION FOR THE PROJECT In 2003, at the direction of Governor Bill Richardson, a statewide, multi-agency, Strategic Planning Committee was formed to address the issues of Driving While Intoxicated (DWI. The resulting DWI Strategic Plan describes a comprehensive DWI Data System as its top priority. Major components of such a system include: Electronic data entry in the field of DWI-related paperwork by law enforcement agencies (e-citation). Electronic transfer of DWI-related paperwork among law enforcement agencies, courts (District, Metropolitan, Magistrate and Municipal), District Attorneys and the Motor Vehicle Division. Improved data transfer between law enforcement agencies and the Scientific Laboratory Division of the Department of Health (DOH). Sentence compliance tracking with electronic data transfer between the courts and the compliance tracking system, including probation and corrections and eventually evaluation and central data repository. PAGE 1 PROJECT CHARTER DOT E-CITATIONS PROJECT 2 In addition, this project is aligned with the following strategic plans and assessments: Department of Transportation Highway Safety Performance Plan Department of Transportation Comprehensive Transportation Safety Plan NM Statewide Traffic Records Strategic Plan NM Traffic Records Assessment. 1.3 PROJECT CERTIFICATION REQUIREMENTS CRITERIA YES/NO EXPLANATION Project is mission critical to the agencies Yes The E-Citation Project is a multi-agency project providing workflow automation, and data integration of electronic citation information from the DOT TraCS software module to the New Mexico Courts. Odyssey Case Management system. Project cost is equal to or in excess of $100,000.00 Yes Total estimated cost for Federal Fiscal years 14 and 15 is $400,000 Project impacts customer on-line access Yes The E-Citation project will automate the process of generating court cases in the Odyssey Case Management system, with little or no data entry required by the court staff – thereby increasing productivity and efficiency. Project is one deemed appropriate by the Secretary of the DoIT Yes Project meets the State’s Strategic objectives and is supported by DoIT. PAGE 2 PROJECT CHARTER DOT E-CITATIONS PROJECT Will an IT Architecture Review be required? 3 No Phase 1 of this project is to install, configure, and connect the Albuquerque Police Department TraCS software with the Bernalillo Odyssey System to transfer electronic citations directly to the court’s case management system. Activities include: 1. Hardware and Software Acquisition 2. Installation and configuration of hardware and software 3. Network and Security configuration, testing and implementation 4. Development of data mapping and data extraction facilities 5. Conducting User Acceptance Testing 6. Conducting Training for Users and IT Operational Staff Members. PAGE 3 PROJECT CHARTER DOT E-CITATIONS PROJECT 2.0 JUSTIFICATION, OBJECTIVES AND IMPACTS 2.1 AGENCY JUSTIFICATION NUMBER DESCRIPTION 1 The goal of this project is to successfully integrate data between the New Mexico Law Enforcement Agencies TraCS systems and the Magistrate Courts’ Odyssey Case Management System. 2.2 BUSINESS OBJECTIVES NUMBER DESCRIPTION BUSINESS OBJECTIVE 1 Increase efficiency and productivity BUSINESS OBJECTIVE 2 Optimize business processes, decreasing the number of steps, saving time BUSINESS OBJECTIVE 3 Lower the cost of government, provide more effective Electronic Records Administration Management BUSINESS OBJECTIVE 4 Improve service delivery to constituency BUSINESS OBJECTIVE 5 Reduce manual, paper-based Court Case Management processes, which contribute to high costs and overhead expenses. 2.3 TECHNICAL OBJECTIVES NUMBER DESCRIPTION TECHNICAL OBJECTIVE 1 Extract electronic citation information from the New Mexico Law Enforcement Agencies, TraCS-centralized databases for import to corresponding Magistrate Court Odyssey Case Management System. TECHNICAL OBJECTIVE 2 Develop, configure and install network architecture connectivity and security between Law Enforcement Agencies and Magistrate Courts. TECHNICAL OBJECTIVE 3 Develop Reconciliation facilities in order to determine if all records were transmitted successfully, and to also create a process for retransmitting failed Transactions. PAGE 4 4 PROJECT CHARTER DOT E-CITATIONS PROJECT 2.4 IMPACT ON ORGANIZATION AREA DESCRIPTION END USER Proposed automation as a result of the E-Citation project should realize improved efficiencies for court personnel because of the Citation data entry process is to be eliminated. BUSINESS PROCESSES Automation of Data Entry Business Processes will provide staff efficiencies. IT OPERATIONS AND STAFFING Once network connectivity and security is configured, IT Operations Staff members will only be responsible for monitoring the transmittal process and reconciling the transmitted records. OTHER Constituents appearing before the magistrate courts can be assured that the infractions they are facing are free from any data entry errors that may have been introduced via a paper-process methodology. 2.5 TRANSITION TO OPERATIONS AREA DESCRIPTION PRELIMINARY OPERATIONS LOCATION AND STAFFING PLANS Not Applicable DATA SECURITY, BUSINESS CONTINUITY Data will be encrypted as it travels from the LEA central database server to the Odyssey Case Management Systems. MAINTENANCE STRATEGY Software, network and security configuration settings will be documented for each deployment and stored in an Electronic project repository housed at DOT. INTEROPERABILITY The proposed integration is already operational between the Dona Ana County Sheriff’s Department and the Don Ana Magistrate Court. RECORD RETENTION Information is electronic based and records retention schedules for each LEA and Magistrate Jurisdiction will be addressed during the configuration process. CONSOLIDATION STRATEGY In cases where consolidation is viable, LEAs and Courts will be asked to consolidate their computing infrastructures. PAGE 5 5 PROJECT CHARTER DOT E-CITATIONS PROJECT 3.0 PROJECT/PRODUCT SCOPE OF WORK 3.1 DELIVERABLES 3.1.1 PROJECT DELIVERABLES Project Charter Certification Form Project Management Plan IV&V Contract & Reports IT Service Contracts Risk Assessment and Management Project Schedule Monthly Project Status Reports to DoIT Project Closeout Report 3.1.2 PRODUCT DELIVERABLES Requirements Documents The requirements will be defined and documented during the Planning Phase. This will define goals, business processes, critical factors, current environment, sizing requirements, current vendor environment, # of users, work processing requirements, other needs. Design Documents The Vendor will be required to deliver design documents for network configuration, security authentication, transmission reconciliation, and database mapping methodologies. Systems Specifications System specifications are in place for both the TraCS and Odyssey Case Management Software. Systems Architecture The E-Citation project will use the same technical architecture as the TraCS Statewide Rollout project which has been in production since 2009. System and Acceptance Testing The users will test system functionality, performance, reporting accuracy and response times. IT Technical Support Staff will test system operational performance. PAGE 6 6 PROJECT CHARTER DOT E-CITATIONS PROJECT Operations requirements The Vendor will be required to deliver Operations documentation for network configuration, security authentication, transmission reconciliation, and database mapping methodologies. 3.2 SUCCESS AND QUALITY METRICS NUMBER DESCRIPTION QUALITY METRICS 1 The project schedule, assigned tasks, resources and milestones are met. QUALITY METRICS 2 Project does not exceed budget. QUALITY METRICS 3 Electronic citation information is successfully transmitted from Law Enforcement Agency TraCS software to the corresponding Magistrate Court’s Odyssey Case Management system. QUALITY METRICS 4 System integration is secure, operable and stable QUALITY METRICS 5 Data integrity is maintained QUALITY METRICS 5 LEA IT Operational Staff is adequately trained on reconciling data transmission efforts PAGE 7 7 PROJECT CHARTER DOT E-CITATIONS PROJECT 8 4.0 SCHEDULE ESTIMATE Project Phase Start Date Completion Goals Date Initiating 12/1/2013 1/22/2014 Determine budget availability, team members, analyze and determine infrastructure needed, Develop Project Management Plan, develop risk and mitigation plan. Planning 1/22/2014 5/31/2014 Identify and document Albuquerque City and Bernalillo County motor vehicle enforcement ordinances. Document TraCS database requirements for citation infractions. Document Bernalillo County Odyssey Case Management Traffic Citation database requirements. Document Albuquerque Police Department computing network, and security requirements. Document Bernalillo County Magistrate Court computing network and security requirements. Implementing 6/01/2014 5/31/2015 Phase 1 of this project is to install, configure, and connect the Albuquerque Police Department’s Office TraCS software with the Bernalillo Odyssey System to transfer electronic citations directly to the court’s case management system. Activities include: 7. Hardware and Software Acquisition 8. Installation and configuration of PAGE 8 PROJECT CHARTER DOT E-CITATIONS PROJECT 9 hardware and software 9. Network and Security configuration, testing and implementation 10. Development of data mapping and data extraction facilities 11. Conducting User Acceptance Testing 12. Conducting Training for Users and IT Operational Staff Members Closing 6/1/2015 6/30/2015 Phase 1- DoIT Closure Report, Followup Training, and Project Closure. 5.0 BUDGET ESTIMATE 5.1 FUNDING SOURCE(S) SOURCE AMOUNT FFY14 Highway Safety Plan 14-HE-64-P03 TraCS Citation Adjudication Data Transfer ASSOCIATED RESTRICTIONS $ 200,000 Federal oversight and reporting. 5.2. BUDGET BY MAJOR DELIVERABLE OR TYPE OF EXPENSE – IT E M ESTIMATE Integration Strategy $13,600 Data Mapping Configuration and Security Methodology Strategy $13,600 User Acceptance Test Plan $13,600 Configure TraCS Testing Environment $27,000 PAGE 9 PROJECT CHARTER DOT E-CITATIONS PROJECT IT E M 10 ESTIMATE Configure Network and Security Testing Environment $27,000 User Acceptance Testing $27,000 IT Operational Training $27,000 Transition to Production $13,600 Hardware and Software Purchase $36,800 $200,000 TOTAL BUDGET 5.3 BUDGET Description FY 14 & Prior FY 15 Consulting $68,000 $95,200 Hardware $26,800 Software $10,000 TOTAL $104,800 PAGE 10 $95,200 FY 16 PROJECT CHARTER DOT E-CITATIONS PROJECT 11 6.0 PROJECT AUTHORITY AND ORGANIZATIONAL STRUCTURE 6.1 STAKEHOLDERS NAME STAKE IN PROJECT ORGANIZATION TITLE Tom Church OVERALL PROGRAM RESPONSIBILITY NM DOT Cabinet Secretary Designate Kathryn Bender PROGRAM ADMINISTRATION RESPONSIBILITY NM DOT Deputy Secretary Tama P. Hass PROGRAM FINANCIAL RESPONSIBILITY NM DOT Director Office of Asset Management Michael Sandoval PROGRAM ADMINISTRATION NM DOT Director Planning and Safety Division Eric Roybal QUALITY ASSURANCE MANAGEMENT AND IT SYSTEM ADMINISTRATION NM DOT Acting Chief Information Officer Anthony Apodaca PROJECT ANALYST NM DOT Management Analyst Dave Martinez CO-PROJECT ANALYST NM DOT Management Analyst CSW ENTERPRISES PROJECT MANAGEMENT CSW ENTERPRISES VENDOR PAGE 11 PROJECT CHARTER DOT E-CITATIONS PROJECT 6.2 PROJECT GOVERNANCE PLAN PAGE 12 12 PROJECT CHARTER DOT E-CITATIONS PROJECT 13 6.3 PROJECT MANAGER 6.3.1 PROJECT MANAGER CONTACT INFORMATION NAME ORGANIZATION PHONE #(S) NICK SALAZAR CSW ENTERPRISES, LLC (505) 310-3184 JOHN SALAZAR CSW ENTERPRISES, LLC (505) 699-8503 EMAIL 12.3.2 PROJECT MANAGER BACKGROUND John Salazar has extensive experience in implementing successful IT projects. He is very familiar with the State of New Mexico project certification policies and procedures. John has over 28 years’ experience in information technology. Mr. Salazar has served as CIO for the City of Santa Fe, as well as the NM Taxation and Revenue Department (TRD) and the NM Department of Workforce Solutions (DWS). Nick Salazar is a CompTIA Project+ certified professional who has experience managing project life cycles associated with the rollout of software and hardware products. Nick worked for the New Mexico Taxation and Revenue Department where he was responsible for maintaining the hardware and software utilized by the Motor Vehicle Division to operate their more than 90 field offices. Nick has extensive experience with workstation hardware, software and peripheral equipment installation and configuration. 6.4 PROJECT TEAM ROLES AND RESPONSIBILITIES ROLE RESPONSIBILITY Executive Project Sponsor The point person for the project within the highest level of the General Services Department. Responsibilities include: Champion the project. Consider potential changes facing the organization and assess the organizational impact Decide which changes will be instituted, communicate priorities and provide resources to ensure success Responsible for creating an environment that enables changes to be made on time and within budget. Participate in planning sessions Member of Steering Committee Ultimate project responsibility PAGE 13 PROJECT CHARTER DOT E-CITATIONS PROJECT ROLE RESPONSIBILITY Steering Committee Member Is chartered to provide governance over the direction and support of the project. Responsibilities include: Attend and participate in meetings Review and accept deliverables Review and provide comment on presented documentation Balance larger picture versus details of the project Review project funding and expenditures Champion the project Contributes to lessons learned. Business Owner The person within each of the participating Divisions who is responsible for all operations and management of any and all activities occurring within the division. Responsibilities include: Maintain overall project direction and implementation Ensure staff availability Approve expenditure of funds Issue Resolution Empower Project Manager. Project Manager The persons within each of the participating divisions who must make all decisions related to the operation of the system, staffing assignments. Responsibilities include: Ultimate project success. Diagnose potential problems Participate as “change” agents Develop realistic plans to deal with critical issues and execute changes effectively Decision authority regarding system module set-up Reviews work of Consultant Project Team Support Member Assignments Determine System Administration roles Problem Solving Project Planning Project Budgeting Project Schedule Contract Management Training Plans Communicate with Project Team Support Members, Business Owners and Steering Committee Contributes to lessons learned. PAGE 14 14 PROJECT CHARTER DOT E-CITATIONS PROJECT ROLE RESPONSIBILITY Project Team Support Members Staff assigned to the project on an as needed basis. 15 Responsibilities include: Define Business Requirements Module set-up input Functional Testing Scheduling of meetings and space Completion of assigned tasks Budget Tracking Purchasing and Processing Data Gathering Data Input System Administration Provide Resources as needed. 6.5 PROJECT MANAGEMENT METHODOLOGY The project strategy is based on the strategic direction established by the DOT Executive Steering Committee and the participating agencies utilizing the TraCS, E-Citations and Odyssey Case Management Software products. The integration of the software products will utilize a successful methodology recently developed between the Dona Ana Sheriff’s Office and the Dona Ana Magistrate Court. This integration project effort includes: configuration of data variables in both the TraCS and Odyssey software systems; establishing network connectivity between systems; implementing data transfer encryption services; documentation of configurations; conducting user acceptance testing; training for IT operational staff; and transition to production services. 7.0 CONSTRAINTS NUMBER DESCRIPTION 1. Well Documented Dona Ana Methodologies and Strategies 2. Similar Business Rules between Dona Ana and Bernalillo Counties 3. “Buy-In” of Project Strategies and Objectives from all participants. PAGE 15 PROJECT CHARTER DOT E-CITATIONS PROJECT 16 8.0 DEPENDENCIES 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 Albuquerque Police Department Participation E 2 Bernalillo County Magistrate Court Participation E 3 Vendor with past Integration Experience to perform Tasks E 4 DoIT PCC approval of Project M 5 Contract Approval with Albuquerque Police Department to initiate project M 6 Successful data mapping and data integration methodologies utilized by Dona Ana County D 9.0 ASSUMPTIONS NUMBER DESCRIPTION 1. TraCS software can be configured with all Bernalillo County traffic ordinances 2 Successful connectivity between APD and Bernalillo Magistrate Court PAGE 16 PROJECT CHARTER DOT E-CITATIONS PROJECT 17 10.0 SIGNIFICANT RISKS AND MITIGATION STRATEGY Risk 1 Loss of Federal Grant Funds Probability: POSSIBLE Description - Federal Grant funds are needed to continue providing support the project Impact - HIGH Mitigation Strategy: Business Owner is ensuring that the project meets all requirements for Federal Grant funds. DOT – Traffic Safety Bureau is reviewing available grant opportunities on a regular basis. Contingency Plan: The Project Manager will present options for maintaining the project in its capacity at the time of loss of funds. Risk 2 – Staff Turnover Probability: EXPECTED Description Personnel changes can impact the adoption and maintenance of the proposed systems Mitigation Strategy: Where possible, backup staff will be assigned to shadow every lead staff resource to prevent losing system knowledge and incurring delays in the schedule. Contingency Plan: The timeline and possibly the scope of the project will be adjusted based on the available resources. Risk 3 – Delay in approval of contracts for services Probability: LIKELY Description The process for formulating and approving an IT services contract is complex and may take longer than expected Impact - HIGH Impact - MED Mitigation Strategy: DOT will coordinate efforts for approving an IT services contract with DOT Management and DOIT to ensure procedures are in place to expedite approvals. Contingency Plan: The timeline and possibly the scope of the project will be adjusted based on the available resources. 11.0 COMMUNICATION PLAN FOR EXECUTIVE REPORTING Meetings will be conducted with E-Citation Executive Steering Committee on a regularly scheduled basis. Whiteboard sessions outlining project task and resource assignment schedules and agendas are conducted throughout the process and transferred to Microsoft project. Project team meetings are scheduled to coincide with the Vendor Implementation/Design teams for on-site implementation sessions. The frequency and length of meetings remains to be defined. Project status updates reports will be communicated to E-Citation Steering Committee conducted at weekly meetings. DOT management will be kept informed on progress of the project periodically throughout the project life cycle. PAGE 17 PROJECT CHARTER DOT E-CITATIONS PROJECT 18 12.0 INDEPENDENT VERIFICATION AND VALIDATION - IV&V Because of the Project Deliverables and limited software development, DOT will be requesting an IV&V Waiver for the E-Citation Project. Project/Product Area Include – Yes/No Project Management N Quality Management N Training N Requirements Management N Operating Environment N Development Environment N Software Development N System and Acceptance Testing N Data Management N Operations Oversight N Business Process Impact N PAGE 18 PROJECT CHARTER DOT E-CITATIONS PROJECT 19 13.0 PROJECT CHARTER AGENCY APPROVAL SIGNATURES SIGNATURE EXECUTIVE SPONSOR TOM CHURCH BUSINESS OWNER MICHAEL SANDOVAL PROJECT ANALYST ANTHONY APODACA DATE CO-PROJECT ANALYST DAVE MARTINEZ 14.0 PROJECT CHARTER CERTIFICATION APPROVAL SIGNATURE SIGNATURE DOIT / PCC APPROVAL PAGE 19 DATE