Project Management Plan SHARE Upgrade
August 05, 2009 Department of Information Technology
Document Change Information
Version / Rev # / Date / Description0001 / 000 / 08/05/09 / First Draft
0002 / 000 / 08-14-09 / Second Draft
0002 / 001 / 08-18-09 / Small changes
1
Project Management Plan SHARE Upgrade
August 05, 2009 Department of Information Technology
Table of Contents
1 Project Overview 1
1.1 Introduction 1
1.2 Current State 2
1.3 Future State 2
2 Scope 2
2.1 Business Objectives 2
2.2 Technical Objectives 2
2.3 Project Deliverables 2
2.4 Product Deliverables 3
2.5 Work Breakdown Structure 3
3 Strategy 4
3.1 Technical Strategy 4
3.2 Success Factors 4
3.3 Logistics and Resources 5
3.4 Methods, Tools, and Techniques 5
4 Project Organization 5
4.1 Stakeholders and Sponsors 5
4.2 Project Team 6
4.3 Organizational Structure 7
4.4 Organizational Boundaries, Interfaces, and Responsibilities 7
4.5 Schedule 7
4.6 Training 8
4.7 Documentation 8
5 mANAGEMENT AND cONTROLS 8
5.1 Management Objectives and Priorities 8
5.2 Assumptions 8
5.3 Constraints 9
5.4 Dependencies 9
5.5 Project Time Line 10
5.6 Project Libraries 11
5.7 Staff Planning and Acquisition 11
5.8 Product and Process Quality Assurance 11
5.9 Risk Management 12
5.10 Configuration Management 12
5.11 Communications Management 13
5.12 Procurement Management 13
5.13 Budget Management 14
5.14 Budget and Resource Allocation 14
5.15 Measurements 14
6 Closedown 14
1
Project Management Plan SHARE Upgrade
August 05, 2009 Department of Information Technology
Project Management Plan
1 Project Overview
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 Architecture Team worked toward developing an architecture that addressed many identified needs and goals. Through recent system assessment activities we have identified many challenges and areas of 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
· Reduce Complexity
· Improve Network Management Administration
· New Network Design
· System Management tools to manage the environment
1.1 Introduction
This Project Management Plan has been established to set forth the guidelines, deliverables and methods to be used in supporting the customer requirements for upgrading the SHARE system. This plan will be reviewed at completion to insure that the methodologies and procedures are kept current. Version numbering as described later in the document will be followed.
1.2 Current State
While the SHARE system is currently operating in a production and development environment, the hardware is reaching the end of its effective life cycle. Additionally, there is no disaster recovery system available in the current environment.
1.3 Future State
The goal is to upgrade the hardware, operating systems, management software, and upgrade Oracle data base from 10G RAC to 11G RAC including the development of a disaster recovery environment.
2 Scope
This section will outline the justification, objectives, deliverables, and Work Breakdown Structure (WBS) for the SHARE Upgrade project.
2.1 Business Objectives
Number / Description /1. / Meet disaster recovery and business continuity requirements
2. / Provide a system that is highly available.
3. / Replace aging hardware
4. / Improve Network Design and Security
2.2 Technical Objectives
Number / Description /1. / Install new hardware and operating system platform that will support the PeopleSoft Application and data base. Perform all recommended tasks of testing and securing (hardening) the new the hardware and operating system.
2. / Upgrade Oracle Data base from 10G RAC to 11G RAC
3. / Implement Oracle grid control
4. / Implement System clustering using Oracle Enterprise Linux and VM Ware
2.3 Project Deliverables
Project Charter / Defines project authority, governance and lays the foundation for elements to be addressed in the Project Plan.Project Plan / A formal, approved document used to guide both project execution and project control. The primary uses of the project plan are to document planning assumptions and decisions, facilitate communication among stakeholders, and document approved scope, cost, and schedule baselines.
Work Break Down Structure (WBS) / Defines the components of the projects.
Risk Matrix / Risk matrix that defines the risk event, the probability, and an assessment. The risk matrix will also identify any Risk Mitigation, Contingency, and Backout procedures.
Go/No Go Criteria / Criteria that will be established to drive any go/no go decisions that need to be made. All criteria must be addressed to the satisfaction of the Steering Committee.
2.4 Product Deliverables
The following chart outlines the Product Deliverables:
HardwareNew systems hardware architecture platform (servers and network hardware)
Oracle Enterprise Manager (OEM) system management software with Grid Control
Disaster Recovery capabilities with Oracle Data Guard replication software
One 11 node development environment including Disaster Recovery
One 7 node production environment
One two node management environment
New Network design supporting the above identified environments
Testing and Compliance Services
Testing related to the upgrade of system and network hardware, operating system software, management tools and data base upgrades.
Testing related to OEM Grid Control and clustering services
System Documentation
On site training and shadowing in the use of OEM Grid Control Product Suite
2.5 Work Breakdown Structure
See Attachment “A”
3 Strategy
3.1 Technical Strategy
The following table outlines the technical strategy that will be used to accomplish the tasks required.
Number / Description1. / Using best practices, install new hardware and operating system platform that will support the PeopleSoft Application and data base. Perform all recommended tasks of hardening, testing and securing the new hardware and operating system.
2. / Upgrade Oracle Data base from 10G RAC to 11G RAC
3. / Implement Oracle grid control
4. / Implement System clustering using Oracle Enterprise Linux and VM Ware
5. / Install and secure newly designed network to meet the requirements of the new system architecture.
6. / Training; Oracle will provide a 10 day training session for technical staff. Training will include …
3.2 Success Factors
Supportable Model
· Supportable Data Management
o Information Lifecycle Management (ILM)
§ Archiving Data
§ Tiered data
§ Masking of data
· Reduce Complexity
· Improve up-time
· Version Management
· Baseline and metrics
· Ongoing tuning processes
· Oracle 11G
· Tiered Firewall
· N-Tier Architecture
o Development Access
o Production Access
o Management Access
· Monitoring – Alerting – Trending
· Overall improved and enhanced system management
· Cost effective Linux Environments
· Logging, improved system reporting
3.3 Logistics and Resources
Supplies and equipment will be required and funded via normal appropriations. Each organization will supply their staff person with a desk area, phone, voice mail, email, access to the Internet and other equipment needed to perform their work on the project.
The only travel expected is by vendor personnel. The cost of their travel is included in the negotiated contracts.
3.4 Methods, Tools, and Techniques
Members of the project teams will perform their task in the manner prescribed by the documented processes and procedures.
4 Project Organization
This section shows the relationships among the major functions and activities, the structure, boundaries, and delineates responsibilities.
4.1 Stakeholders and Sponsors
The following table shows the stakeholders and sponsors by area and function:
Function/Activity / Position / Individual(s) /Executive Sponsor / DoIT - Cabinet Secretary / Marlin Mackey
SHARE Director / Director – Finance Control / Anthony Armijo
Steering Committee Member / DoIT - Deputy Secretary / Conny Maki
Steering Committee Member / DoIT - Deputy Secretary / Tom McQuillan
Steering Committee Member / DoIT SHARE System Manager / Steve Yore
4.2 Project Team
The following tables show the State team assignments:
Management Team
Team / Labor Category / Name /Project Management / Project Manager / Mike Neitzey
Operations / Operations Lead / George Robinson
Infrastructure / Deputy Director, DoIT Operations / Kelly Mentzer
Applications Support / Team Lead / Bruce Walker
Time/Labor/Payroll Support / Team Lead / Mike Vaisa
Functional Testing / Team Lead / Tobi Andrade
Help Desk Support / DoIT Support Services Manager / Dorenda Morse
Business Continuity / Team Leader / Mary Anaya
Technical Team
Name / Area of Expertise / Organization /Mike Vaisa / Payroll / DFA
George Robinson / Operations / DFA
Jonathan Walker / Security / DFA
Don Gleason / Security / DFA
Karla Fernandez / Security / DFA
Kelly Mentzer / Operations / DoIT
Vin Kelly / Security, Network Administration / DoIT
Fernando Rodriquez / Oracle DB Administration / DoIT
Bryan Emery / Oracle DB Administration / DoIT
Henry Brown / AIX Administration / DoIT
Maureen Howles / AIX Administration / DoIT
Neal Perrone / Windows/Citrix Administration / DoIT
Angela Larranaga / Windows/Citrix Administration / DFA
Infrastructure Team
Name / Area of Expertise / Organization /Henry Brown / AIX and Linux / DoIT
Neil Perrone / Windows / DoIT
Chris Rodriquez / Storage and F5 / DoIT
Bill York / Storage / DoIT
Chris Hancock / F5 / DoIT
Software Support Team
Maritza Snyder / Technical – Time Labor, HR, MISC / DoIT
Ben Bowles / Technical – Benefits, HR, MISC / DoIT
Gary Graves / Technical – Benefits, Interfaces, MISC / DoIT
Lynn Chick / Technical – Reports, Queries, Operations / DoIT
Yvonne Encinias / Functional – Time Labor Lead / DoIT
Jessica Miera / Functional – Time Labor / DoIT
Paul Armijo / Functional – Benefits, HR / DoIT
Time & Labor – Payroll Support Team
Name / Area of Expertise / Organization /Audrey Liddy / Functional Payroll / DFA
Mike Vaisa / Functional Payroll / DFA
Help Desk Team
Name / Area of Expertise / Organization /Dorenda Morse / Enterprise Support Desk Supervisor / DoIT
Business Continuity Team
Name / Area of Expertise / Organization /Mary Anaya / Risks and Issues / Business Continuity
4.3 Organizational Structure
The governance structure of the SHARE Upgrade team can be found at Attachment B.
4.4 Organizational Boundaries, Interfaces, and Responsibilities
The key interface between the organizations is between the Project Manager from the DoIT, the Project Managers from Oracle and the assigned Team Leaders/ managers. The primary methods utilized will be the Status Report/Briefing, adhoc meetings, electronic mail, and phone conversations. Interaction may occur directly between the technical components of all teams. However, overall task direction can only come from the Project Manager. Final decisions will be made at the Steering Committee level.
4.5 Schedule
The Project Schedules will be stored in the Shared/Project Files/New SHARE Architecture Upgrade – Disaster Recovery/Schedule directory. Individual schedules will be updated by their respective owners on an as required basis.
4.6 Training
There will be a vendor hosted training on site for identified technical support staff. The training will be focused on the OEM Grid Control Suite of Tools and what will be required to manage the new environment.
4.7 Documentation
Project documentation falls into one of the following categories:
Documentation as defined in Section 2.4
Test Results Reports
Transmittal information (memos, letters, receipts, etc.)
Project guidance (processes, procedures, etc.)
All of these will be under some level of identified CM control as identified in the next section.
5 mANAGEMENT AND cONTROLS
This section identifies the goals and procedures used by management for the SHARE Upgrade project.
5.1 Management Objectives and Priorities
The overall goal is to provide support services to the SHARE Upgrade project in the five areas defined by the contract. The priority for the project team is to achieve a stable hardware and software environment.
5.2 Assumptions
The following table is a list of assumptions for the SHARE Upgrade project:
Item / Description /1 / Participation from all parties involved.
2 / Controls will be put in place for adequate tracking and reporting.
5.3 Constraints
The following table is a list of constraints for the SHARE Upgrade project:
Item / Description /1 / Deliverables, terms and conditions as described in the contract with Oracle.
2 / Maintain uninterrupted services to all State Agencies.
3 / Project Manager is in question at this time
4
5.4 Dependencies
The following table is a list of dependencies for the SHARE Upgrade project:
Item / Description /1 / Additional funding required for the network/load balancing hardware. Due to system design, we added additional hardware to meet requirements on new architecture.
2 / Location of State Disaster Recovery site is identified
3 / Department of Information Technology’s disaster recovery and business continuity project
1
Project Management Plan SHARE Upgrade
August 05, 2009 Department of Information Technology
5.5 Project Time Line
1
Project Management Plan SHARE Upgrade
August 05, 2009 Department of Information Technology
5.6 Project Libraries
Due to the limits on the network configurations and availability that are a result of a dispersed team, each team will be responsible for establishing a common area for storing project related items.
Project Management items will be stored sub-directories under the following directory:
IT Shared/Project Files/New SHARE Architecture Upgrade – Disaster Recovery
5.7 Staff Planning and Acquisition
Personnel will be assigned by their parent organizations to the project. As additional resource requirements are identified, the Project Manager will work with the Executive Steering Committee and senior agency management to identify individuals with the necessary skills to augment the team.
5.8 Product and Process Quality Assurance
Product and Process Quality Assurance falls into two categories. The first is Quality Control which encompasses the physical quality of the products. This is provided by a series of product checks done by various levels of reviews and test. The level of review will be determined by the level of risk of errors. The second category is Quality Assurance which is monitored and measured by an independent validation that work is being performed according to documented processes and procedures.