Académique Documents
Professionnel Documents
Culture Documents
Table of Contents
Page
Project Charter......................................................................................................2 Preliminary Charter..........................................................................................................2 Final Charter....................................................................................................................2 What is the purpose (description) of this project?...........................................................2 What are the tangible business benefits?.........................................................................3 What are the intangible benefits?.....................................................................................3 Why should we do this project?.......................................................................................3 Who are the stakeholders? What is the impact to them? What is the impact to our system?.............................................................................................................................4 What is the estimated total budget cost?..........................................................................4 What assumptions have been made?................................................................................5 What does the project include?........................................................................................5 Are there regulatory impacts?..........................................................................................5 What is the plan to procure equipment, third party services or resources?.....................5 What is the proposed business or technical solution?......................................................5 What alternatives were considered? ...............................................................................5 Who will manage the solution once the project is complete?......................................6 What success criteria have been established?..................................................................6 How will an audit for compliance be conducted?............................................................6 In what areas does the project manager have flexibility?................................................6 TEAM COMPOSITION...........................................................................................8 SCOPE FORM WORKSHEET.............................................................................10 SCOPE BOUNDARIES........................................................................................12 DELIVERABLES SCHEDULE INPUT.................................................................13 SCOPE RISK........................................................................................................14 MILESTONE SCHEDULE....................................................................................15 STAFFING & SPENDING ACTUALS MONITORING.........................................16 SPENDING ESTIMATE........................................................................................17 Project Status Report.........................................................................................18 ISSUES LIST........................................................................................................19 LESSONS LEARNED RECOMMENDATIONS...................................................21
Page 1
Project Charter
Project Name: Executive Branch Mainframe Data Center Consolidation
Preliminary Charter
Developed by: Tom Shepherd Approved by Project Sponsor: Reviewed by: Date: November 26, 2001 Date: Date:
Final Charter
Developed by: Approved by Project Sponsor: Reviewed by: Date: Date: Date:
Page 2
What is the plan to complete the work? (High level plan with estimated dates.) February 28, 2002 Develop a capacity plan for mainframe computing by performing an analysis of all mainframe applications review and justification of all mainframe
Page 3
applications and commercial off-the-shelf (COTS) software used to support those applications). April 1, 2002 Assess logical/physical data center designs and staffing needs and implement the new data center management structure.
Who are the stakeholders? What is the impact to them? What is the impact to our system?
Stakeholder Department of Transportation Describe the impact to that stakeholder The department will be affected if their data center is used to recover the capitol complex data center services in the event of a disaster. Conversely, the capitol complex data center services provide a disaster backup for the DOT. IWD will only be responsible for specifying the type and level of services required and will no longer be burdened with the management responsibility for the IWD data center. Operating as a central service bureau for state government, ITD will manage and operate all capitol complex data center services for the benefit of all governmental entities. The CIO has a vested interest (and statutory duty) to take action to foster the compatibility, interoperability, effectiveness, and efficiency of the information technology systems within the executive branch of state government. The result of more effective data center management will be to reduce ongoing operational and maintenance costs and improve overall service.
Public
Page 4
Page 5
IWD and divorcing itself from any involvement with IWD. This is not recommended as it capitulates to ineffective management practices.
Page 6
Network( Network( s) s) Network( Network( s) s) Network( Network( s) s) ITD Managed & Operated Data Center
Network(s) Network(s)
Page 7
Project Leader:
Department Represented
Management
Management liaison, financial To be named management ITD Operations Management To be named IWD IT Management DOT IT Management To be named To be named
Team Representative
To be named To be named To be named To be named To be named
Team Status
Team Representative
Team Status
Page 8
Production job processing, online telecommunications systems, printing, Contingency Planning and Disaster Recovery Capacity Planning
Page 9
Project Leader:
Deliverable
Project management plan
Typ e*
Customer Needs
A plan that represents customer concerns and requirements and provides a path for effectively achieving the project goals.
Customer Requirements
Sufficient time and resources to execute the plan without adversely impacting the delivery of critical mainframe services.
Features/ Functions
Plan must be developed and executed collaboratively and balance the individual agency interests with the greater overall public benefit.
Support for all necessary Assessments to computer applications. determine the justification for continuing to run the applications on a mainframe or recommend other actions (discontinue the application, replace with a COTS application, or discontinue the application). The timely availability Appropriate computing The capacity plan will power to process online of appropriate be based upon input real-time inquiries and computing services. from the current and turnaround batch workloads prospective customer within specified time agencies. frames. Continuity of Contingency and Sufficient capacity, operations recovery plans to be compatible hardware executed in the event of and software, and an event adversely current backups of impacting a mainframe mainframe data center facility. applications must be
Yes
Yes
A data center configuration that meets all customer needs and requirements without unacceptable costly surpluses in unused capacity. Plans and resources that are capable of providing for the continuity of designated critical applications.
Yes
Page 10
Project Leader:
Deliverable
Typ e*
Customer Needs
Customer Requirements
Features/ Functions
Component failure impact analysis of mainframe hardware, software, and network components (new data center configuration)
available in the event of a disaster. Availability of high High availability (99%+) of Support for required speed, high reliability mainframe computing network services, high mainframe computing services. Sufficient availability, data services at the lowest computing power to process backup and archiving online real-time inquiries reasonable unit cost. services, offsite and turnaround batch storage of critical workloads within specified system backups, time frames. support for legacy applications and assessment/migration support to move applications to more appropriate platforms. Continuity of Software and hardware Identify and eliminate operations. redundancies and (or mitigate) single availability of data points of failure and storage to support other vulnerabilities in continuity of operations. the design of the data center.
Yes
Reasonable software and hardware redundancies consistent with efficient data center operations.
Page 11
SCOPE BOUNDARIES Project Name: Executive Branch Mainframe Project Data Center Consolidation Leader: Life Cycle Stages (LCS) Included
Tom Shepherd, Information Technology Department
Why?
Processes Included
Why?
Why?
Processes Affected
Why?
Projects Affected
Why?
Page 12
Project Name:
No.
Project Sponsor:
Delivery Date
May 1, 2002 May 1, 2002 1 1,2 3 3
Duration
4 months 1 month 2 months 2 weeks 2 months
Start Date
January 1, 2002 April 1, 2002 May 1, 2002 July 1, 2002
Predecessors
3, 6
Successors
Person Accountable
ITD, DOT, IWD Technical Representatives ITD, DOT, IWD Technical Representatives ITD, DOT, IWD Management, Technical Representatives ITD, DOT, IWD Management, Technical Representatives ITD, DOT, IWD Technical Representatives ITD disaster recovery planner, ITD, DOT, IWD Technical Representatives
1 2 3 4 5 6 7 8 9 10 11 12 13
June 30, 2002 July 15, 2002 July 1, 2002 August 31, 2002
4, 5, 6 6
3 months
Page 13
Project Leader:
Deliverable
Risk Limit
Risks
Risk Rating
Countermeasures
Person Accountable
Page 14
Project Leader:
Phas e Planning
Milestone
Close Out
Execution
Page 15
Project Sponsor:
Spending Actuals
Time Period
TOTALS:
Page 16
Type of Expense
SUBTOTAL: ACCURACY RATING*: RANGE: EXTERNAL COST SPENDING LIMIT: INTERNAL & EXTERNAL TOTAL: ACCURACY RATING*: RANGE: TOTAL COST SPENDING LIMIT: * Document reasons for each accuracy rating.
Page 17
Project Status Report This is a representative sample of the weekly project status reports that will be issued once the project is started. Project: Executive Branch Mainframe Data Center Consolidation Date:
Planned Work Done this Week Unplanned Work Done this week Planned Work Not Done this week Work Planned for Next Week Upcoming Meetings, Milestones & Deliverables Issues/Barriers
Lessons Learned
Please email any questions, comments of concerns regarding the Executive Branch Mainframe Data Center Consolidation Project to: Tom R. Shepherd at tom.shepherd@itd.state.ia.us
Page 18
Project Leader:
Person Person who Date Date responsibl needs resolution resolve e to resolution needed d resolve
IWD, Dept. of Management ITD, DOT, IWD Management Representatives ITD, DOT, IWD Management Representatives ITD, DOT, IWD Management Representatives
How resolved
1 2 3 4 5
Ownership of the IWD data center Project manager assets Required availability (hours of the Project Manager day, days of the week) of data center services Statutory requirements for service Project Manager delivery. Service level commitments (from service level agreements, funding requirements, contractual obligations) Project Manager
7 8 9
Page 19
10
Page 20
Project Sponsor:
Went Well
Needs to Change
PROJECT PROCESS
Teamwork Project Initiation Project Plan Project Execution Project Close Out Recommendations:
Page 21