[insert project name] - nm doit fast id/dps... · web viewproject sponsors sign the project charter...

FASTID

PROJECT CHARTER FOR CERTIFICATION

EXECUTIVE SPONSOR – SECRETARY GREGORY J. FOURATT

BUSINESS OWNER – PETE N KASSETAS, CHIEF DPS

PROJECT MANAGER – CESARIO ALVILLAR

ORIGINAL PLAN DATE: AUGUST 08, 2014

REVISION DATE:

REVISION: 1.0

i

ABOUT THIS PROJECT CHARTER DOCUMENT

PERMISSION TO PLAN THE PROJECT AND SETTING THE GOVERNANCE STRUCTURE

The Project Charter provides the project manager and project team with permission to proceed with the work of the project, within the scope delineated in this document. The Project Charter should be the outcome of a number of documents that went into the pre-planning for the project, and in many cases the agency IT Plan, Business Case for appropriations, Federal funding requests and the like.

Project sponsors sign the Project Charter signifying that they have agreed to the governance structure for guiding the direction for the further planning of the project, discovery and defining the requirements, acquiring necessary resources, and within that context the statement of work for any related contracts including a contract for the Independent Validation and Verification.

The Project Charter is also the foundation for the creation of the project management plan, and much of the thinking and writing for this charter will be immediately usable for that project management plan.

ii

TABLE OF CONTENTSABOUT THIS PROJECT CHARTER DOCUMENT....................................................................................................... II

TABLE OF CONTENTS.......................................................................................................................................... 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.........................................................11.3 PROJECT CERTIFICATION REQUIREMENTS....................................................................................................................2

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

2.1 AGENCY JUSTIFICATION...........................................................................................................................................32.2 BUSINESS OBJECTIVES.............................................................................................................................................32.3 TECHNICAL OBJECTIVES...........................................................................................................................................32.4 IMPACT ON ORGANIZATION......................................................................................................................................3

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

3.1 DELIVERABLES.......................................................................................................................................................53.1.1 Project Deliverables...................................................................................................................................53.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)..............................................................................................................................................95.2. BUDGET BY MAJOR DELIVERABLE OR TYPE OF EXPENSE –.............................................................................................95.3 BUDGET BY PROJECT PHASE OR CERTIFICATION PHASE..................................................................................................9

6.0 PROJECT AUTHORITY AND ORGANIZATIONAL STRUCTURE...........................................................................10

6.2 PROJECT GOVERNANCE PLAN.........................................................................................................................116.3 PROJECT MANAGER.........................................................................................................................................12

6.3.1 PROJECT MANAGER CONTACT INFORMATION........................................................................................126.3.2 PROJECT MANAGER BACKGROUND.........................................................................................................12

6.4 PROJECT TEAM ROLES AND RESPONSIBILITIES................................................................................................136.5 PROJECT MANAGEMENT METHODOLOGY..................................................................................................................17

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

13.0 PROJECT CHARTER AGENCY APPROVAL SIGNATURES.................................................................................21

iii

14.0 PROJECT CHARTER CERTIFICATION APPROVAL SIGNATURE........................................................................21

iv

Revision History

REVISION NUMBER DATE COMMENT

1.0 August 08, 2014 1st draft

v

PROJECT CHARTER NEW MEXICO LAW ENFORCEMENT TELECOMMUNICATIONS (NMLETS) UPGRADE 1

1. PROJECT BACKGROUND

1.1 EXECUTIVE SUMMARY -RATIONALE FOR THE PROJECT

The Department of Public Safety State Police will deploy a mobile fingerprinting device to NMDPS law enforcement officers throughout the state of NM. This is an expansion of the Automated Fingerprint Identification System (AFIS) system. The mobile devices capture individual’s fingerprints and submit to the AFIS for identification. Results are returned to the mobile applications screen for notification and positive identification, if available.

1.2 SUMMARY OF THE FOUNDATION PLANNING AND DOCUMENTATION FOR THE PROJECT

Technical and user documentation will be provided by the vendor.

PAGE 1


1.3 PROJECT CERTIFICATION REQUIREMENTS

CRITERIA YES/NO EXPLANATION

Project is mission critical to the agency? Yes Officer Safety

Project cost is equal to or in excess of Yes Project is estimated to cost $160,000

Project impacts customer on-line access No

Project is one deemed appropriate by the Secretary of the DoIT

Unknown

Will an IT Architecture Review be required? No Waived

PAGE 2


2.0 JUSTIFICATION, OBJECTIVES AND IMPACTS

2.1 AGENCY JUSTIFICATION

NUMBER DESCRIPTION

AGENCY-1 Officer safety

AGENCY- Quickly identify persons of interest in the FBI RISC database

2.2 BUSINESS OBJECTIVES

NUMBER DESCRIPTION

BO-01 identify persons of interest listed in the NM AFIS database

BO-02 identify persons of interest listed in the FBI RISC database

2.3 TECHNICAL OBJECTIVES

NUMBER DESCRIPTION

TO-01 Expand fingerprint identification technology to the DPS State Police in the field

2.4 IMPACT ON ORGANIZATION

AREA DESCRIPTION

STATE POLICE OFFICERS

Officers can scan a suspect’s fingerprints and launch a search of NM AFIS and the FBI’s RISC database.

BUSINESS PROCESSES

Training of officers in proper use of hardware and software

IT OPERATIONS AND STAFFING

No impact on IT operations and current staffing

OTHER NA

PAGE 3


AREA DESCRIPTION

PAGE 4


2.5 Transition to Operations

AREA DESCRIPTION

PRELIMINARY OPERATIONS LOCATION AND STAFFING PLANS

The system is hosted at DPS and maintained by Morphotrak.

DATA SECURITY, BUSINESS CONTINUITY

No change

MAINTENANCE STRATEGY

Morphotrak has the maintenance contract and DPS is in the process of requesting additional years of maintenance.

INTEROPERABILITY The system will integrate with New Mexico AFIS and the FBI’s RISC database.

RECORD RETENTION No records generated, data retrieval only

CONSOLIDATION STRATEGY

No consolidation. System is a module of the AFIS system

PAGE 5


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 . “Project management plan” is 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. plan.”

IT Service Contracts The Department of Information Technology (DoIT) and the State Purchasing Division of General Services have established a template for all IT related contracts.

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

PAGE 6


Monthly Project Status Reports to DoIT

Project status reports. 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 This is the Template used to request that the project be officially closed. Note that project closure is the last phase of the certification process

3.1.2 PRODUCT DELIVERABLES

Systems Architecture Waived

System and Acceptance Testing

DPS will perform the Acceptance Testing

Operations requirements Support and Maintenance contract to be approved

PAGE 7


3.2 SUCCESS AND QUALITY METRICS

No. Quality Standard Tracking Tool or Measure

1

Certification to proceed to implementation 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

5 Verification and Validation • N/A waived

6 Project completed within budget, schedule, and scope • Project Management Plan• Manage to contract• Steering Committee

Meeting Decisions

PAGE 8


4.0 SCHEDULE ESTIMATE

New Mexico Commercial Vehicle OS/OW Permitting and Routing System Project Schedule

No. Task Name Duration Start - Days after NTP

End - Days after NTP

Pred Resource

1 Purchase Order request

8 weeks Sonia Abeyta

2 Order equipment 2 weeks Sonia Abeyta

3 Identify end users 1 day Major Lovato and Major Soland

4 Training 2 days Morphotrak, Sonia Abeyta

5 Installation 12 weeks Morphotrak, DPS

6 Follow up training 1 week Morphotrak, Sonia Abeyta, Jonathan Borrego

PAGE 9


5.0 BUDGET ESTIMATE

Identifier PSDC Permitting and Routing System Cost

PB-01 Order Equipment and training $160,000

PB-11 Total fees $160,000

5.1 FUNDING SOURCE(S)

SOURCE AMOUNT ASSOCIATED RESTRICTIONS

APPROVERS

C2, LAWS 2014 CHAPTER 63, SECTION 7, ITEM 19

$160,000 RON BURTON, DPS CIO

5.2. BUDGET BY MAJOR DELIVERABLE OR TYPE OF EXPENSE –

ITEM COST ESTIMATEOrder Equipment and training $160,000Total expended: $160,000

5.3 BUDGET BY PROJECT PHASE OR CERTIFICATION PHASE

Proposed Certification Schedule for Current Fiscal Year

Phases Amount Requested

Major Deliverable(s) Due Dates

Planning/Implementation $160,000 Morpho IDent equipment June 30, 2015

PAGE 10


6.0 PROJECT AUTHORITY AND ORGANIZATIONAL STRUCTURE

PAGE 11


6.1 STAKEHOLDERS

Name Stake in Project Organization Title Phone email

Gregory J. Fouratt

Executive sponsor

Department of Public Safety

Cabinet Secretary [email protected]

Pete N Kassetas Sponsor DPS Chief [email protected]

Ron BurtonSponsor - DPS Resources

DPS IT CIO [email protected]

Darrell GrahamDPS Resources

DPS ITITD/TSB Bureau Chief

[email protected]

Cesario AlvillarProject Manager

DPS IT Project Manager [email protected]

Elizabeth (Karana) Haring

Contracts SMEPurchasing Agent-Advanced

505-827-9626mailto:[email protected]

Sonia AbetyaBusiness process manager

DPS LERBLERB CCH Manager,

[email protected]

Regina Chacon Manager DPS LERBLERB Bureau Chief,

[email protected]

Jonathan Borrego

FastId Support DPS LERB AFIS Support Tech 505-827-3428

[email protected]

PAGE 12

mailto:[email protected]





6.2 PROJECT GOVERNANCE PLAN

6.3 PROJECT MANAGER

6.3.1 PROJECT MANAGER CONTACT INFORMATION

NAME ORGANIZATION PHONE #(S) EMAIL

Cesario Alvillar DPS IT Office: 505 827-9538

Cell: 505 467-9307

[email protected]

6.3.2 PROJECT MANAGER BACKGROUND

30 + years IT professional experience. 10 years managing IT projects

PAGE 13




6.4 PROJECT TEAM ROLES AND RESPONSIBILITIES

Project Artifacts(with Roles and Responsibilities)

Project Phase ArtifactProject

ManagerBusiness Analyst Sponsor

Business Lead

QA Lead Architecture

Tech Lead

s†Procurement

LeadVendor

Initiation Initiation Certification Request A,R C C C I I I I

Initiation Project Charter A, R C C C C I C I

Planning Planning Certification Request A,R C C C I I CProject Management Plan A,R C C C I C C CRisk & Issues Log A, R C C C C I C I IStakeholder list A R C C I C I C

Business Requirements A R C C C I C I C

Business Requirements Review A R I C C I C I C

*Communications Plan A, R C C C C C C I I

* Process Models A R I C C I C I C

* Request for X (Info, A R C C C I C C I

PAGE 14


Proposal, Quote)

*Requirements Fit/Gap Analysis A R I C C I C I C

* IV&V Contract A R I C C C C C C Project Schedule A,R C C C C C C C C

Budget (Spend Plan) A,R C C C C I C C

Project Test Plan A C C C R C C I C* Training Strategy A C C R I I C I C

Implementation Certification Request A,R C I I I C C C

*Architectural Solution Package A C I C I C R C Architecture Technical Review Presentation A R C C C C C C Architecture Technical Architecture Review Request Form A R I I I I I Architecture Business Continuity A R I C I C C C Architecture Operations and Support Plan A R I C I C C C Architecture System Design Document A C I C I C R C

PAGE 15


Architecture Hosting Exception Request Form A C C C I C R C Architecture NM DoIT Security Questionnaire A C I C C R C

Implementation & Closeout

Change Management Request A C C C C C R C C

* Contracts A R C C I C C R C Status Reports A R I C C I C I C

Invoice Processing & Accruals A C I C I I I R I

Lessons Learned A, R C C C C C C C Project Acceptance A, R R C C C C C C I

*Project Change Control A, R C C C C C C C C

Project Closure A, R C I I C C C C C

*

Purchase Requisitions and/or Orders A, R C I I I I I R C

QA User Acceptance Test Sign-off A,R I C C R I C C C

Sponsor Status Reports A, R C I C C C

Team Meetings & Reports A, R C C C C C C I C

Test Coverage A C C C R C C C

PAGE 16


Matrix

Test Results and Defect Reports A C I C R C C

* Training Plan A, R C I R C C C C

R = Responsible A = Accountable C = Consulted I = Informed * If applicable to the project scope

ROLE RESPONSIBILITY NAME FUNCTIONAL AREA

Project Manager/Business Analyst

See RACI Above Cesario Alvillar DPS IT

Sponsor See RACI Above Gregory J. Fouratt DPS

Business Lead/QA Lead See RACI Above Major Lovato and Major Soland

DPS- SP

Architecture See RACI Above DoIT DoIT

Technical Lead See RACI Above Jonathan Borrego DPS IT

Procurement lead See RACI Above Sonia Abeyta DPS

Vendor See RACI Above MorphoTrak Vendor

PAGE 17

† Includes Integration, Application, Infrastructure, and Info Security Leads


6.5 PROJECT MANAGEMENT METHODOLOGY

Procurement, Contract Award, Implementation, Production Transition and Closeout.

7.0 CONSTRAINTS

NUMBER DESCRIPTION

C-01 None

8.0 DEPENDENCIES

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

D-01 INTERNET CONECTIVITY M

PAGE 18


9.0 ASSUMPTIONS

NUMBER DESCRIPTION

A1 Officers in the field will accept the system and use it

10.0 SIGNIFICANT RISKS AND MITIGATION STRATEGY

System

Description –

VPN issues

Probability Low

Impact HIGH

Mitigation Strategy - Coordinate with DPS ITContingency PlanEscalate to sponsors

PAGE 19


11.0 COMMUNICATION PLAN FOR EXECUTIVE REPORTING

Current status of this project will be reported to DPS executive management on a monthly basis or as requested. Weekly status report to project team.

Signatures from the Executive Sponsors are required for some project documents.

PAGE 20


12.0 INDEPENDENT VERIFICATION AND VALIDATION - IV&V

IV&V has been waived.

PAGE 21


13.0 PROJECT CHARTER AGENCY APPROVAL SIGNATURES

SIGNATURE DATE

EXECUTIVE SPONSOR

BUSINESS OWNER

PROJECT MANAGER

14.0 PROJECT CHARTER CERTIFICATION APPROVAL SIGNATURE

SIGNATURE DATE

DOIT / PCC APPROVAL

PAGE 22

[insert project name] - nm doit fast id/dps... · web viewproject sponsors sign the project charter...

Documents