SWIRE
StateWide Infrastructure Replacement & Enhancement
Project Charter For Certification
Executive Sponsor – Darryl Ackley, Cabinet Secretary-Department of Information Technology
Executive Sponsor – Jacqueline Miller, Deputy Cabinet Secretary-Department of Information Technology
Business Owner - Maynard Salazar, Deputy Services Mgr.-Broadband and Radio-Department of Information Technology
Project Manager – Maynard Salazar, Deputy Services Mgr.-Broadband and Radio-Department of Information Technology
Original Plan Date: July 23, 2014
Revision Date: July 23, 2014
Revision: 1.0
About This Project Charter DOCUMENT
Permission to plan the projec t 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.
Project certification Initial phase documentation
The Project Charter is also used within the State of New Mexico IT Project Certification process as evidence of the project’s worthiness for the Initial Phase certification. The Initial Phase certification is especially critical to many state and agency projects because of its related release of the initial funds required for the project.
Initiation Phase funding is requested by an agency for use in developing project phases, developing Independent Verification and Validation (“IV&V”) plan and contract; address project review issues and/or to develop an overall project management plan. Note: Waiver of the IV&V requirement requires specific written approval by the Secretary of the DoIT.
DoIT “Project Certification” Memorandum July 2, 2007
The Project Charter and the Request for Certification Form are meant to provide a comprehensive picture of the project’s intention and initial planning, that includes the project’s place in the context of the State of New Mexico’s IT Strategic Plan, Enterprise Architecture, and DoIT project oversight process. See “IT Project Oversight Process” Memorandum July 5th 2007 on the OCIO-DoIT web site.
table of contents
About This Project Charter DOCUMENT
table of contents
1. project background
1.1 Executive Summary -rationale for the project
1.2 Summary 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.3.2 PROJECT MANAGER BACKGROUND
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 / Comment1.0 / July 17, 2014 / Initiation of SWIRE Project
1
Project Charter - SWIRE1
1. project background
The project background section is meant to provide the reviewer with a picture of the development of the project from inception to its being submitted for certification.
1.1Executive Summary -rationale for the project
Radio communications infrastructure is in need of replacement and enhancement due to life cycle expiration and growing demand of critical public safety communications statewide.
1.2 Summary of the foundation planning and documentation for the project
1.3 Project Certification Requirements
Does the project fit into the criteria for certification? Which and how?
CRITERIA / YES/NO / EXPLANATIONProject is mission critical to the agency / Yes / Public Safety communications
Project cost is equal to or in excess of $100,000.00 / Yes / Project budget is $5,000,000
Project impacts customer on-line access / No / Replacement and enhancement of radio communications systems for public safety agencies
Project is one deemed appropriate by the Secretary of the DoIT / Yes
Will an IT Architecture Review be required? / No / Replacement and enhancement of existing radio communication systems
2.0 Justification, Objectives and impacts
The justification and objectives section relates the project to the purpose of the lead agency and describes the high level business and technical objectives for the project. The section also includes a high level review of the impact to the organization, and of the concerns for transition to operations.
2.1 Agency Justification
IDENTIFY AGENCY MISSION, PERFORMANCE MEASURE OR STRATEGIC GOALS TO BE ADDRESSED THROUGH THIS PROJECT
Number / DescriptionAgency / continue to provide enterprise level radio communication services to public safety agencies.
2.2 Business Objectives
Use the following table to list measurable business objectives
Number / DescriptionBusiness Objective 1 / fulfill statatory responsibilites to provide public safety agengies the ability to fulfill their missions.
2.3 Technical Objectives
Number / DescriptionTechnical Objective 1 / Replace and enhance mission critical infrastructure in order to provide reliable and resilient radio communications to public safety agencies.
2.4 Impact on Organization
The impacts on the organization are areas that need to be addressed by the project through its planning process. They may not be internal project risks, but they can impact the success of the project’s implementation.
Area / DescriptionEnd user / will enable public safety agencies more reliable and resilient systems.
Business Processes / No impact to the business process will occur as the result of this project. Department currently provides this services to end users.
It Operations and staffing / No change in internal operations will occur as a result of this project. Will continue to utilize established framework to support the service.
2.5 Transition to Operations
The transition to operations areas include items that are asked in the certification form to assure that the project has accounted or will account for these matters in its planning and requirements specifications.
Area / DescriptionPreliminary Operations location and staffing plans / operations will continue to occur at existing locations and no other additional staffing will be required in order to provided services. contractor will be utilized for project management in implementation.
Data Security, Business Continuity / will develop migration strategy from old to new infrastructure as required.
Maintenance Strategy / utilize existing establish procedures currently in place as part of the enterprise service.
Interoperability / system is interoperable with existing network infrastructure .
Record retention / All project documents will be stored and archieved for future reference.
3.0 Project/ProductScope of Work
In its efforts to move from the high level business objectives to the desired end product/service the project team will need to deliver specific documents or work products. The State of New Mexico Project Management Methodology distinguishes between the project and the product.
Project Deliverables relate to how we conduct the business of the project. Product Deliverables relate to how we define what the end result or product will be, and trace our stakeholder requirements through to product acceptance, and trace our end product features and attributes back to our initial requirements
3.1 Deliverables
3.1.1 Project Deliverables
This initial list of project deliverables are those called for by the IT Certification Process and Project Oversight memorandum, but does not exhaust the project deliverable documents
Project Management / Internal resources will be utilized to manage project.Implementation / Will develop implementation strategy to insure project has as little impact as possible to end users.
Monthly Project Status Reports / Will provide DoIT Enterprise Project Management Office monthly reports to ensure compliance with policies and procedures defined.
Project Closeout Report / DoIT Project Manager will provide all reports required for Project Closeout.
4.0 Schedule Estimate
The estimated schedule from initiation to completion is FY15.
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 restrictionsLaws 2014 Chapter 66, Section20(2) / $5,000,000 / Plan, design, acquire, purchase and implement infrastructure for public safety communications statewidefor improved communication equipment affecting all emergency responders.
5.2. Budget By Major Deliverable or Type of expense -
Item / Cost Estimate / .Project management / $200,000
EQUIPMENT PURCHASE AND INSTALLATION / $4,800,000
5.3Budget By Project Phase or Certification Phase
Item / Cost Estimate / .INITIATION / $200,000
PLANNING AND IMPLEMENTATION / $4,800,000
6.0 Project Authority and Organizational Structure
6.1 STAKEHOLDERS
Stakeholders should be a mix of agency management and end users who are impacted positively or negatively by the project.
name / Stake in Project / Organization / TitleDarrly Ackley / Executive sponsor / Doit / Cabinet secretary
jacqueline Miller / executive sponsor / doit / Deputy cabinet secretary
Maynard Salazar / Project Mgr./Business Owner / Doit / Deputy Services Mgr.
external agency / operational user / PUBLIC SAFETY AGENCIES
6.2 PROJECT GOVERNANCE PLAN
6.3 PROJECT MANAGER
6.3.1 PROJECT MANAGER CONTACT INFORMATION
name / Organization / Phone #(s) / EmailMaynard M. Salazar / DoIT / 505-827-2446 /
6.3.2 PROJECT MANAGER BACKGROUND
Deputy Services Mgr.-Department of Information Technology Broadband and Radio Services. Has 30 + years experience in Information Technology. Has served on TARC, C2 evaluation committee. Has been Deputy Director/Deputy Service Manager with the Department of Information Technology for the past 6 years.
6.4 PROJECT TEAM ROLES AND RESPONSIBILITIES
Role / ResponsibilityDARRYL ACKLEY / EXECUTIVE SPONSOR
JACQUELINE MILLER / EXECUTIVE SPONSOR
MAYNARD SALAZAR / PROJECT MANAGER/BUSINESS OWNER
INTERNAL STAFF / PLANNING AND IMPLEMENTATION
6.5 Project management Methodology
This project will follow an implementation plan that will define how project the project will be implemented. This plan will define a budget, resources, schedule and a planned strategy to deploy and install all equipment. The project will utilize contracted project management and internal QA to ensure project meets complies with all requirements and meets all benchmarks and milestones.
7.0 Constraints
Number / Description1 / APPROPRIATION EXPIRATION
8.0 Dependencies
Types include the following and should be associated with each dependency listed.
- 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 / certification of project / M
2 / Procurement of equipment / e
3 / scheduling of resources / d
4 / Accessability to locations and equipment / d
9.0 Assumptions
Number / Description1 / Implementation will be completed by June 30, 2015.
2 / Budget/Funding available.
3 / New/replacement equipment will be acquired by DOIT.
4 / Staff will be available for installations and programming.
5 / Inventory Management will be required including completing asset forms and documentation.
10.0 Significant Risks and Mitigation Strategy
Risk 1
No major risks have been identified. / Probability / ImpactMitigation Strategy
Contingency Plan
11.0 COMMUNICATION PLAN FOR EXECUTIVE REPORTING
DoIT Project Manager will hold weekly status meeting with contracted Project Management vendor and all assigned internal staff to ensure all deadlines and benchmarks are met in accordance with the Project Management Plan (PMP) and will provided the DoIT Project Oversight and Compliance Division monthly reports as required by the Project Certification Committee (PCC).
12.0 INDEPENDENT VERIFICATION AND VALIDATION - IV&V
Requesting waiver to IV&V and requesting to utilize internal QA instead.
13.0 Project Charter Agency Approval Signatures
signature / dateExecutive Sponsor
Business Owner
Project Manager
14.0 Project Charter Certification Approval Signature
signature / dateDoIT / PCC Approval
Page 1