2.0 2.1 Name Stake in Project Organization Title Phone email Subscriber Agencies Subscriber Agencies Glen Condon SME DFA / LGD 911 GIS Specialist 505-827-4977 Gar Clarke Central State GIS DOIT NM Geospatial and Broadband Program Manager 505-827-1663 Diana Dejarnette Administrative DPS ASD Deputy Director 505-827-9035 Elizabeth (Karana) Haring Contracts DPS Purchasing 505-827-9626 Elizabeth Trickey General Counsel DPS Deputy General Counsel Fran Dunaway Procurement DPS Chief Procurement Officer 808-827-9018 Gregory J. Fouratt Executive sponsor DPS Cabinet Secretary 505-827-3370 Greg.Fouratt@state.nm.us Regina Chacon DPS DPS Bureau Chief – LERB 505-827-9297 Kimberly Clark Business Owner DPS Bureau DPS Emergency Communications Director 505-841-9256 Kristian Reveles SME DPS Bureau Communications Supervisor 575-622-7200 Perry McPhee SME DPS Bureau Communications Specialist 505-841-9256 Cesario Alvillar Project Manager DPS IT Project Manager 505-827-9538 Darrell Graham DPS Resources, Technical Lead DPS IT ITD/TSB Bureau Chief 505-827-3460 Communication
BO-03 Improving officer safety by tracking unit location using Automatic Vehicle Location (AVL) for officers in the field and providing a secondary means of communication and access to National Crime Information Center (NCIC) access within the application. BO-04 Gathering call response and officer initiated event information for data collection and intelligence gathering purposes. BO-05 Improved reporting of crime data and performance statistics for state and federal grant purposes, operational assessment and unit deployment. 3.1.2 Number Description TO-01 Replace outdated Computer Aided Dispatch System nearing obsolescence. This system is fundamental to DPS Operations. TO-02 Improve mapping capabilities and enhance ability to capture incident data based on GIS information. TO-03 Implement new technologies not available in current system. TO-04 Leverage existing secondary technologies incompatible with current system. TO-05 Enhanced system stability. TO-06 Improved interface capabilities. 3.2 N/A 3.3 QM-01 Formal testing will determine whether the implementation of targeted requirements have been successful or not. Qm-02 Requirements - Team and Stakeholder review and signed Accepted Qm-03 Design - Technical Lead review Requirements Traceability to design and signed Accepted
Qm-04 Test Plan - Formal testing will determine whether the implementation of targeted requirements have been successful or not.- Business owner, and Stakeholders review Requirements Traceability to test results and signed Accepted Qm-05 Production version - Technical Lead review of configuration and signed Accepted Qm-06 Schedule - Milestone dates, status reports Accepted Qm-07 Budget - Budget reports, status Accepted 4.0 4.1 4.1.1 Phase Summary of Phase Key Deliverables Initiation This phase defines overall parameters of the project and established the appropriate project management and quality environment required to complete the project. Project Charter, Initial Risk Assessment, High level schedule, Approval for next phase Planning This phase defines the exact parameters of the project and ensures all the pre-requisites for execution and control are in place. RFP, signed vendor contract, Project Management Plan, Team members identified, Stakeholder list, Functional Requirements, High level WBS, High level Schedule, Budget and Communication Plans, Roles and Responsibilities, Status reports, approval for next phase Implementation The phase configures and deploys the system. Certification Form, updated Project Management Plan, Project Schedule, Configuration Documentation, Testing LIFE CYCLE MANAGEMENT MANAGEMENT
Acceptance criteria Deliverable 4 will be considered complete when the Procuring Agency accepts the Requirements Analysis Document. Deliverable 4: Phase X Launch Deliverable Name Due Date Compensation Phase X Launch XX Days After Contract Execution Not to exceed $$ including Gross Receipts Tax with 100% Retainage per Article 3, Paragraph D. Task Item Sub Tasks Description Phase Launch Sub 1 The Contractor will implement all Phase I functionality as defined in the RFP, selected by the Procuring Agency, and refined in the Requirements Analysis Document. Sub 2 The Contractor will create test scripts for all Phase I functionality and perform testing on all Phase I functionality using these test scripts. The Contractor will correct errors when identified and retest. Sub 3 The Contractor will re-import updated company and permit data. This is the data that will be used for the Phase I launch and will reflect all new accounts and permits since the initial import. This import will have any corrections identified in the testing of the initial data. Sub 4 The Contractor will Sub 5 The Contractor will create user documentation for all Phase I functionality. The Contractor will implement online help for all Phase I functionality. Sub 6 The Contractor will perform Phase I training for all Procuring Agency personnel. Training will be performed XX Sub 7 The Contractor and the Procuring Agency will launch the Phase I functionality on the production environment.
Sub 8 The Contractor will provide weekly status reports including but not limited to status of activities, issues, risks, dependencies and proposed resolutions Sub 9 Deliverables will be reviewed and Accepted by the Procuring Agency Acceptance criteria Deliverable 5 will be considered complete when the Contractor successfully launches Phase I functionality. Deliverable 5: Phase I Completion Deliverable Name Due Date Compensation Phase Completion XX Days After Contract Execution All Retainage for Deliverable #1 through Deliverable #X shall be paid upon Acceptance of this Deliverable, not to exceed $$ including Gross Receipts Tax Task Item Sub Tasks Description Phase Completion Sub 1 The Procuring Agency will perform a phased rollout of Phase I functionality at locations and with users of its choosing. Sub 2 The Contractor will correct errors and implement user-specified modifications in the system. All fixes and modifications will be developed on the development environment, tested on the test environment, and if Accepted by the Procuring Agency, implemented in the production environment using a schedule of the Procurement Agency’s choosing. Sub 3 The Contractor will create a complete suite of Phase I acceptance test scripts that fully test Phase I functionality. Each item in the test scripts will refer to a project requirement and will have a description of how to perform the test, expected correct results, and possible failure methods to look for. The Procuring Agency will be free to add or change tests in its acceptance scripts. The Contractor will insure that the system passes all tests on all Phase I acceptance test scripts before declaring the system ready for the Procuring Agency’s acceptance testing. Sub 4 The Procuring Agency will perform acceptance testing.
Planning P-R07 Maps No maps for dispatchers, a must for CAD Darrel/Marco Work with Gar on his consolidated mapping project 2/4/2014 2/27/2014 Planning P-R11 Moving the contract through the approval process could take longer than wanted. Project delays, loss of funds Kim, Cesario Kim and Karana will move the contracts through the process 2/25/2014 2/25/2014 Planning P-A29 Data Requirements assessment - meet and provide DPS with a template and help with a survey Meet and provide DPS with a template and help with a survey 3/6/2014 3/24/2014 P - Planning A - Action R - Risk I- Issue IM - Implementation Risks are mitigated - mitigated by reducing its probability of happening to zero Risk - an uncertain event that may or may not happen, that will impact your project adversely (positive or negative) affecting the outcome of the project Issues are resolved - taking action Issue - an issue is a matter in question or dispute that is disruptive to the smooth execution of a project as planned. There is no probability attached, it is a certitude. An Issue will happen, is happening now, or has already happened.
6.6.1 Project Area Category Measure Requirements Quality Functional Baseline Team and Stakeholder review and signed Design Quality Allocated Baseline Technical Lead review Requirements Traceability to design and signed Test Plan Quality Testing Business owner, and Stakeholders review Requirements Traceability to test results and signed Production version Quality Production Baseline Technical Lead review of configuration and signed Schedule Project Time Milestones Milestone dates, status reports Budget Project Budget Milestones Budget reports, status 6.7 QUALITY CONTROL 6.7.1 No. Quality Standard Tracking Tool or Measure 1 Certification to proceed to next phase by DoIT Approval from DoIT Project Certification Committee and release of funds 2 Project issues/risks documented, tracked, and worked to resolution Issues/risks Log 3 Project budget Weekly budget review 4 Project Schedule Weekly Schedule update and review