DATE - New Mexico Department of Information Technology

advertisement
Change Request for Certification and Release of Funds Form
ALL CERTIFIED PROJECTS MUST FOLLOW NM STATE POLICIES AND PROCUREMENT CODE
Phase
CHANGE TYPE:
Scope
Budget
Schedule
PROJECT GOVERNANCE
PROJECT NAME
DoIT/SHARE New Architecture, Hardware, and Disaster Recovery System
PROJECT PHASE
Planning
DATE
3/22/12
LEAD AGENCY
Department of Information Technology (DoIT)
OTHER AGENCIES
EXECUTIVE SPONSOR
Darryl Ackley, DoIT Cabinet Secretary
AGENCY HEAD
Darryl Ackley, DoIT Cabinet Secretary
AGENCY CIO/IT LEAD
David Holmes, SHARE System Manager
PROJECT MANAGER
John Prihoda
PROJECT ABSTRACT (PROVIDE A BRIEF DESCRIPTION AND PURPOSE FOR THIS PROJECT)
The purpose of this project is to establish a Disaster Recovery system for the SHARE environment. Due to the
age of the current hardware environment and the advancements in system clustering and grid control technologies,
the SHARE architecture team worked toward developing an architecture that addressed many identified needs and
goals. Through recent system assessment, planning, and design activities we have identified many challenges and
areas of needed improvement. Through the new system architecture we will meet the identified goals listed below
and address areas of concern and needed improvement.
Goals of the project
 System portability (to meet disaster recovery requirements)
 High availability
 Fault tolerance
 Redundant
 Highly secure
 Adequate bandwidth
 Processes supporting design and deployment
 Flexible – scalable
 Expandable
 Documented
Revision: 9/1/10
Page 11
Change Request for Certification and Release of Funds Form
ALL CERTIFIED PROJECTS MUST FOLLOW NM STATE POLICIES AND PROCUREMENT CODE




Reduce complexity
Improve network management administration
New network design
System management tools to manage the environment
September 2009
Start Date
Planned End Date
To Be Determined
JUSTIFICATION FOR CHANGE IN CERTIFICATION (INCLUDE BUDGET ADJUSTMENT REQUEST; BUSINESS VALUE AND/OR
PROGRAM RESULTS)
The project was put ‘on hold’ while a storage solution was being developed by the DoIT. It had been on hold for
an extended period of time, and the department desires to re-launch the project to obtain the goals listed above and
to utilize the investment that has been made. The project wishes to change the phase of this project back to the
planning stage to allow new management the time to reassess the present status of the previously performed
activities, develop a go-forward strategy, determine possible additional procurements, and identify appropriate
funding sources if needed.
Amount Requested this Certification
$ 0.00
Amount Previously Certified
$ 2,100,000
Amount Spent-to-date
$ 2,031,809
Remaining Appropriation not Certified
$ 0.00
Total Appropriated Amount (include any new funds)
$ 2,100,000
CERTIFICATION HISTORY (INCLUDE ANY PREVIOUS PROJECT OR PHASE CERTIFICATIONS)
Date
Amount
4/13/2009
$ 2,100,000
8/12/2009
$0
Revision: 9/1/10
Funding Source(s) (use specific citations to laws, grants, etc.)
Laws 2009, Chapter 125, Section 27(3) ($1,700,000)
Laws 2009, Chapter 124, Section 4 (Share Operating Budget)
($400,00)
Page 21
Change Request for Certification and Release of Funds Form
ALL CERTIFIED PROJECTS MUST FOLLOW NM STATE POLICIES AND PROCUREMENT CODE
APPROPRIATION HISTORY (INCLUDE ALL FUNDING SOURCES, E.G. FEDERAL, STATE, COUNTY, MUNICIPAL LAWS OR GRANTS)
Fiscal Year
Amount
FY09
$ 2,100,000
Funding Source
Laws 2009, Chapter 125, Section 27(3) ($1,700,000)
Laws 2009, Chapter 124, Section 4 (Share Operating Budget)
($400,000)
MAJOR DELIVERABLE SCHEDULE AND PERFORMANCE MEASURES
Budget
Due Date
Planning efforts to review present hardware design and
implemented configuration
$ 0.00
4/20/12
Planning
Develop go-forward plan for hardware design and
configuration changes
$ 0.00
4/20/12
Planning
Certification of go-forward plan with associated budget
and funding
$ 0.00
4/20/12
Planning
Major Project Deliverable and Performance
Measure
Revision: 9/1/10
Project Phase
Page 31
Change Request for Certification and Release of Funds Form
ALL CERTIFIED PROJECTS MUST FOLLOW NM STATE POLICIES AND PROCUREMENT CODE
BUDGET
Comments:
Description
FY09 & Prior
Staff Internal
$ 0.00
Servers
$ 300,000
Network, LB,
and Firewall
hardware
OEM Grid
Control
Software
Consulting
Services
IV&V
$ 185,000
TOTAL
Revision: 9/1/10
FY10
FY11
FY12
FY13&After
TBD
TBD
$ 1,059,000
$ 562,000
$ 10,000
$ 2,116,000
Page 41
Change Request for Certification and Release of Funds Form
ALL CERTIFIED PROJECTS MUST FOLLOW NM STATE POLICIES AND PROCUREMENT CODE
INDEPENDENT VERIFICATION & VALIDATION (INCLUDE SUMMARY OF THE LATEST IV & V REPORT)
From the IV&V report issued 9/27/2010:
“This report assesses a YELLOW status for the project based upon project uncertainty combined with the nature
of that uncertainty. The PM continues to openly manage issues and keep his line management apprised of
concerns. IV&V expresses concern throughout this document that the project team’s overall workload may be in
need of, at least, workload leveling to ensure that current and upcoming competing tasks do not dilute focused
attention for the SHARE/DR project. In addition to other Agency responsibilities, the team faces less than 90
days until the 12/15/10 projected project completion date. Planning and execution of plans is still pending for
testing, data migration and deployment. The project faces risk in attempting to go live by the 12/15/10 scheduled
date with a limited number of long weekends available for deployment. The PM continues to demonstrate
control/coordination of project scope, planning for contingencies, diligence for acceptance of deliverables, and
resolution of issues.”
IMPACT OF CHANGE (MAY INCLUDE SIGNIFICANT RISKS & MITIGATION STRATEGY; SECURITY, CONSOLIDATION & MAINTENANCE
STRATEGIES; RECORDS RETENTION; & BUSINESS PERFORMANCE MEASURES)
Without this change in project phase to planning, the state risks:



not being able to implement and activate the hardware, and software previously procured on the project,
not put SHARE on a more current, stable production environment, and
not provide the redundant disaster recovery environment required in the 2008 legislation.
Revision: 9/1/10
Page 51
Download