1. Department of Information Technology SHARE New Architecture, Hardware, Disaster Recovery, and System Upgrade Project Update SHARE Service Manager – David Holmes Project Manager – John Prihoda March 28, 2012

2. DR Project Scope The purpose of this project is to establish a Disaster Recovery system for the SHARE environment. The goals include:  Move SHARE to newer hardware and commodity technology  Provide for a Highly Available, Redundant & Fault Tolerant System  Increase Agility – Expandable, Flexible & Scalable  Reduce Complexity & Increase Manageability  Establish a Disaster Recovery system easily moved to a remote Disaster Recovery Datacenter. 2

3. Current Status This project has been on hold and is being restarted and pushed to completion  The new SHARE Service Manager is now in place and is making resuming this project a priority.  Hardware was implemented and software installed over a year ago, and is now out of date.  The DR system originally used the end-of-life Hitachi storage. The DR system is lacking a permanent storage solution which will need to be resolved before moving forward. 3

4. Budget Status – 12/15/10 FundAllocatedSpentRemain Appropriations$1,700,000$1,679,745$20,255 ERF$333,219$341,995($2,776) Operational$0$31,650$0 Total$2,039,219$2,053,390$17,479 Note: The Project was certified for $2,100,000. Project financials are under review. 4

5. High Level Plan Restart the project to accomplish: 1)Re-platform current SHARE systems from the aging IBM systems and Hitachi storage to the “new” SHARE hardware platform ASAP 2)Establish DR system as a stand alone clone of SHARE Production 3)Move DR system to remote site when ready 5

6. Affect on Budget Contingent on the outcome of the review and new planning. The project may incur costs associated with:  Selecting and procuring a SHARE storage solution  Procuring other server and network hardware to complete the fully independent DR system  Utilizing professional services as required to complete the project 6

7. Affect on Schedule Currently we estimate new platform implementation is achievable by late August 2012 at the earliest  April to review and plan  May – July to rebuild and test hardware and technical design  July - August to perform the full set of functionality testing with Agencies prior to a Go-Live Exact dates will result from the April planning efforts and is subject to change 7

8. Next Steps: Review Current State Develop Future State – Redesign as necessary Validate Architecture with vendors Determine gaps & solidify final design Prepare a new Plan and Budget to complete the project 8

9. 9 Q&A Thank you