SDC Migration Project Status Report

Loading...

WA State Consolidated Technology Services State Data Center Migration Project Status Report Prepared By:

Consolidated Technology Services – SDC Migration Project

Heidi Brownell/Rick Cook

Current Issues: 7 Open Schedule: Under Development

Period Covered:

Through October 26, 2011

Budget: $60,429,439

Date:

October 28, 2011

Scope: Under Development

SDC Projects Status Project SDC Migration Project

SDC Network Core (NWC)

SDC WAN

SDC Telephony (LTS: PBX, Call Management System and Interactive Voice Response Unit)

9/2/2011

Completed in this Reporting Period

Planned for Next Reporting Period

Began reconciling the projects between the work breakdown structure, SharePoint site and budget sheets. This is approximately 90% complete. Obtained sign-off on project charter. Held the first Steering Committee meeting. Held the first two core team meetings. Updated the Investment plan to align with the project charter and reflect current plans. Refined the work breakdown structure and captured task durations and dependencies in the project plan. The first cut of the overall plan is complete. Refinement of the plan is an ongoing task. Specific timelines are still needed for OB2 Move activities planned after July 2012. These will be captured around second quarter of 2012. Updated the status report template and implemented a repeatable process for Service Owner status reporting.

Continue refinement of the project plan. Focus on critical path items such as ordering the next set of enclosures for Data Hall 1. Continue working the project issues.

Cisco Advanced Services agreements for Installation and Engineering/Testing signed and PO requests have been submitted. Responded to Wright Runstad questions on qualified fiber contractor requirements in the “Structured Cable Installation Requirements”. Submitted cable and pathway requirements to SDC Facilities for SONET timing generator installation requirements. Cisco Network Core equipment delivery is 95% complete. Awaiting the delivery of the Nexus 7018 switches.

Meet with Cisco PM and Engineering manager to set the planning schedule for the equipment installation and engineering testing. Set firm date for fiber contractor SDC walk-thru. Submit timing generator equipment and installation specifications to contract group for quote solicitation. Continue NWC design decision meetings. Complete cabinet elevation drawings for NWC equipment and fiber panels.

Reorganized several projects for improved management and reporting. Started initial planning phase for some of the WAN projects. In Initiation/Planning Phase

Start project initiation/planning phase and determine budget for some of the projects. Continue planning efforts. Continue planning efforts

1

WA Department of Information Services Status Report

Project SDC Facilities

SDC Private Cloud Procurement Project SDC Private Cloud Implementation Project OB2 Move – A la Carte 1 OB2 Move – A la Carte 2 OB2 Move – Vendor Management Mainframe Messaging

CSD Server Migration

Server Virtualization

Security Gateway

Security Infrastructure

9/2/2011

Completed in this Reporting Period

Planned for Next Reporting Period

Phase one enclosure installation is 70% complete (Due 11/01/11). Documentation gathering is taking place for the Data Center Infrastructure Management (DCIM) tool implementation. Physical Security system separation has been approved. Space Management Supervisor position is filled. Completed 3 of the 4 Customer Core Team Requirements Validation Workshops

Complete enclosure installs for phase 1. Continued data and documentation gathering for DCIM configuration and implementation. Continue work on verification and acceptance of the video surveillance system.

N/A

Planning to begin in late 2011

Obtained an inventory of A la Carte customers to begin communication and migration planning. See DSHS Core Redesign status below.

Begin communications with A la Carte customers.

N/A

Planning to begin in late 2011

Refined tasks, timelines, and dependencies within the SDC Migration project plan. Met to refine work breakdown structure and schedule for messaging projects associated with the SDC.

No activity planned for next reporting period. Mainframe moves are targeted for around December 2012. Continue to refine tasks, timelines, and dependencies within the SDC Migration project plan. Initial tasks do not begin until Summer of 2012. Continue to refine tasks, timelines, and dependencies within the SDC Migration project plan

Continued the draft of the overall work breakdown structure and schedule for all server migration projects associated with the SDC. Comarch OSS Servers: Planning virtualization of TSD’s Comarch OSS servers. Agency Technology Services (ATS) Servers: Gathered usage data, prepping for virtualization. Security Servers: Booked Meeting to discuss. PCR approved to change end date of project to July 2012. Completed the initial draft of the overall work breakdown structure and schedule for all security gateway projects associated with the SDC. Released the Security Gateways RFI for 30 day publication on 10/7. Firewall RFP completed and sent to the CTS Office of Legal Services (OLS) for release. Hypervisor firewall resource planning with CSD.

Complete project charter, receive final sign off. Conduct final Customer Requirements Workshops 11/2/11.

See DSHS Core Redesign status below.

Meet to begin high level planning for moving systems to the SDC.

Provide clarification to RFI questions as needed Review & evaluate RFI responses.

Release the firewall RFP. Await RFP vendor responses for Firewall RFP. Begin internal high-level planning with vendors for Authentication and SecMan deployments. Begin design sessions for Authentication and SecMan projects.

2

WA Department of Information Services Status Report

Project Storage Infrastructure

Decommission OB2

Completed in this Reporting Period

Planned for Next Reporting Period

Service owner finalized recommendation for moving forward with an RFQ for an acquisition and installation service in SDC. Service owner finalized recommendation for moving forward with an RFQQ for the planning and implementation of data migration from OB2 storage platforms to SDC.

Review/update Investment Plan, request approval to proceed. Validate Bill of Materials (BOM), Prepare RFQ, submit to Office of Legal Services (OLS) with the Investment Plan for RFQ release. Begin development of a RFQQ for Data Migration Services. Validate existing OB2 fabric switch port/configuration data to assist SO, NWC-Storage Infrastructure, SDC-Cabling projects, SDC-Tape and VTL projects. Planning phase to being in Fall of 2013

N/A

External Project Collaboration External Project

Completed in this Reporting Period

Planned for Next Reporting Period Continue development of the detailed design. Continue efforts to implement the OB2 Nexus network to be used by DSHS. Start planning the migration of the DSHS MPLS network.

Command Center

Developed a work plan for renumbering VLANs. Successfully renumbered one of the VLANs as a trial to validate the work plan steps and effort required. This will be used to estimate the effort for the remaining 50+ VLANs that must change. Worked with CTS/TSD on the design of the OB2 Nexus network to be used by DSHS. Nexus routers (7010's) are now production ready! Nexus 5010 and 2000 switches have been installed and configured in the production environment. Nexus 5010's will be migrated over and closely monitored for 1 month prior to adding any new services to the Nexus platform. Currently waiting on results of SDC space planning efforts.

Data Hall 3 and 4 Marketing

OFM is taking the lead on this effort.

OFM is soliciting for a broker to market the data halls.

Agency Data Center Migration

Business plan update must be completed before additional migration planning can be done. Continuing to meet twice a week, currently focusing on financial models and collecting data to inform the migration plan.

Continue working with the OCIO to build the business plan and discuss planning for agency data center migration. Continue weekly meetings to develop the business plan and financial models.

DSHS Core Redesign

Nexus Data Center Deployment (in OB2)

SDC Business Plan Update

Complete project closeout activities.

Provide input to SDC space planning efforts as required.

Major Deliverable Schedule Formal Deliverable

Deliverable Number

Estimated Completion Date

Deliverable Status

Coordinate projects required to build-out and move to the SDC

9/2/2011

3

WA Department of Information Services Status Report

Formal Deliverable

Deliverable Number

Estimated Completion Date

Deliverable Status

1.1 Project Management Plan and Schedule

D1.1

10/30/2011

Work breakdown structure completed. Task durations and dependencies added to create a granular level schedule. Plan and schedule are in refinement and maintenance mode.

1.2 Investment plan

D1.2

10/30/2011

Plan drafted.

1.3 Project management templates and processes for coordinating the subprojects

D1.3

11/30/2011

Implemented status reporting template and repeatable process.

2.1 Procurement to obtain a Quality Assurance Vendor.

D2.1

7/1/2011

Completed

2.2 Procurement to obtain a vendor to physically move equipment out of OB2 and into the SDC.

D2.2

4/30/2012

Future deliverable

2.3 Procurement to obtain a vendor to conduct performance benchmarks to compare system performance in OB2 to system performance in the SDC (before and after the move).

D2.3

3/31/2012

Future deliverable

Objective 2: Procure resources to assist the project in meeting its goals and objectives

Objective 3: Maximize efficiency and quality, while minimizing cost and risk through the use of repeatable processes to orchestrate the OB2 Move to the SDC 3.1 Overall Systems Migration plan

D3.1

5/30/2012

Future deliverable

3.2 Standard strategies and migration plan for moving systems, applications, functions and equipment to the SDC.

D3.2

6/30/2012

Future deliverable

3.3 Standard templates and repeatable processes for moving equipment and systems to the SDC.

D3.3

6/30/2012

Future deliverable

Objective 4: Oversee and facilitate the development of service owner plans to move equipment to the SDC. 4.1 Inventory of equipment, systems and applications located in the OB2 Data Center.

D4.1

5/30/2012

Future deliverable

4.2 Implementation plans for moving systems to the SDC.

D4.2

6/30/2013

Future deliverable

4.3 Benchmark report validating systems migrated successfully

D4.3

11/30/2013

Future deliverable

5.1 Procurement to obtain a private cloud vendor to design and implement a private cloud utility architecture and computing environment.

D5.1

1/31/2012

In progress

5.2 A private cloud computing environment installed and validated.

D5.2

3/1/2012

Future deliverable

5.3 Policies and procedures for operating and managing the SDC private cloud utility environment. 5.4 Tools and procedures for migrating virtual servers to the SDC private cloud utility environment.

D5.3

4/31/2012

Future deliverable

D5.4

4/31/2012

Future deliverable

Objective 5: Establish a private cloud computing environment to support production systems.

Objective 6: Remove obsolete and applicable equipment from the OB2 Data Center

9/2/2011

4

WA Department of Information Services Status Report

Formal Deliverable

Deliverable Number

Estimated Completion Date

Deliverable Status

6.1 OB2 Decommission Plan

D6.1

11/14/2013

Future deliverable

6.2 List of items to remove

D6.2

12/1/2013

Future deliverable

6.3 Completed inventory of items removed, disposition verified with proper surplus forms

D6.3

2/27/2014

Future deliverable

Top 5 Issues * Issue Key: Green = Issue does not require action within 30 days Yellow = Issue requires action within 30 days Red = Issue requires action within 10 days or less

Y

6/1/2011

Network Monitoring: Allowing agencies to monitor TSD network traffic in a shared environment poses security and technical challenges. Without this capability, agencies may incur longer and more frequent system outages. Resource Conflicts: The project’s resource workload is SDC large. Staff required to work on the SDC Migration project also support production operations and other projects. This causes a conflict in priorities that could impact the SDC Migration Project. This applies to CTS and Agencies. Project Manager for Security projects ITD (Security)

Y

9/12/2011

11/30/2011 12/31/2011

Open

Y

9/14/2011

11/30/2011

Open

Y

9/23/2011

11/1/2011

Top-of-Rack Customer Switches will not be allowed in Data Hall 2. These must be Nexus 2000 switches.

Y

10/18/2011 11/30/2011 12/31/2011

1

Private IP addresses have not been well documented or regulated and could have duplicates across multiple agencies. This could cause routing problems when migrated to the SDC share network.

2

3

4

5 *

Status

Target Next Resolution Review Date Date 11/30/2011 12/31/2011

Issue Summary Description #

Assigned Priority (R,Y,G) TSD

TSD

Opened Date/by

Resolution

Open

11/15/2011 A project management resource Closed has been identified to support security projects. Open

New or changed items in bold italics

Change Requests * 9/2/2011

5

WA Department of Information Services Status Report

No.

Description

001

Requestor

Request Date

Assigned

Cost Impact

Schedule Impact

Status

There are no change requests at this time.

Status (Submitted, Proposal, Approved, Opened, Resolved, Verified, Closed) *

New or changed items in bold italics

1

2

Ability to Meet Deadline

Schedule

Likelihood

Risk Description Because customer agency personnel are not always aligned with mandated objectives and outcomes, they may not support the processes or purchase the services. Because the project is large and includes substantial logistical challenges involving multiple agencies, interdependencies will be complex and could be overlooked.

Level of Impact

ID

Risk Category

Top 5 Risks *

Ext

2

R

G

G

Man

1

R

G

G

3

Budget is large but may be insufficient.

Res

1

R

R

R

4

The project is dependent on and influenced by external drivers such as OCIO and the Legislature. This could impact the project’s scope, schedule and budget.

Ext

2

R

G

G

9/2/2011

Risk Mitigation Comment Continue to include agency IT managers in their steering committee and communicate and educate them regarding the process, decisions, and impacts to the agency systems.

Due Date & Action

Assigned To

Ongoing

Program Manager

Apply project management practices to manage the effort. Break the work down into small and logical units. Use tools to track tasks, dependencies, issues, risks, etc. and automate the planning and communications as much as possible. Implement migration approaches that minimize impacts of system dependencies, such as spanning the network between the OB2 and SDC data centers. Use development and test platforms to verify system dependencies. Work with the Budget Office to consider multiple funding options.

Ongoing

Project Manager

11/1/2011

Program Manager

Provide clear, consistent and routine communication about the project to inform legislators and other stakeholders of the approach and project decisions, and to educate them as to why the decisions and actions are in the best interest of the state.

Ongoing

Program Manager

6

Ability to Meet Deadline

Schedule

Likelihood

Level of Impact

Risk Category

WA Department of Information Services Status Report

Due Date & Action Risk Mitigation Comment Assigned To A clearly articulated business model, architecture R G G 5 Man 2 Ongoing Program and infrastructure design needs to be Manager established and communicated to agencies to determine the actual impact. Agencies need sufficient lead-time to plan for changes and acquire the necessary resources. Risk Category = (Res)ources; (Man)agement; (Tec)hnology; (Fun)ctional; (Dev)elopment; (Int)erfaces; (Sec)urity; (Usa)bility; (Ava)ilability; (Per)formance; (Cap)acity; (Sca)lability; (Ext)ernal. ID

*

Risk Description New business processes and work flows in SDC may impact agency technology operations.

New or changed items in bold italics

Level of Impact Key: 1=major impact 2=significant impact 3=minor impact 0=no impact

Likelihood Key: G = Low. Y = Moderate R = High

Schedule Key: G = on schedule Y = Less than 30 days behind schedule (caution) R = More than 30 days behind schedule (warning

Ability to Meet Deadline Key: G = based on current information, it appears manageable Y = there are significant obstacles or areas of uncertainty or concerns R = there are clearly identifiable threats or deterioration of ability to manage and control

Steering Committee Action Items Item # Item Description 1 2

Review project charter and provide comments to Project Manager.

9/2/2011

Assigned

Date Assigned

Date Due

10/21/2011

10/28/2011

7

Loading...

SDC Migration Project Status Report

WA State Consolidated Technology Services State Data Center Migration Project Status Report Prepared By: Consolidated Technology Services – SDC Migra...

394KB Sizes 2 Downloads 9 Views

Recommend Documents

BCS Project Status Report 2015-01-23 - Project Dashboard
Sep 23, 2015 - Project Management Framework Deliverables. 3/1/16 ... BCS Requirements Documents. 3/1/16 ... Deliverable

2015 Situation Report on International Migration Migration
E. Europe as the primary destination for migration flows into, through and from North Africa. F. Mixed migration from th

Data Center Migration Project WBS | Project Management | Project
A Data Center Migration project schedule/wbs for the assessment, design, move and post migration support phases of a hyp

OIT Project Status Report - Office of Information Technology
Sep 10, 2012 - project will implement Shibboleth federations as a production service. Once implemented .... ironing out

FHWA 1585 Monthly Recipient Project Status Report - TxDOT
December 2011, December 2011 PDF. November 2011, November 2011 PDF. October 2011, October 2011 PDF. September 2011, Sept

fleet status report - Seadrill
Aug 25, 2016 - Ultra-deepwater. 2013. 12,000. 40,000. GoM. BP 22. Oct-13. Oct-20. 562,000. West Vela 3. Ultra-deepwater.

gmi status report - NASA
Sep 9, 2010 - Min Chen, Purdue Univ. • Debra Kollonige, UMBC. • Daewon Byun, NOAA. • Doug Allen, NRL. • Ashley J

SDC-888X - Citizen calculator
CITIZEN modelo SDC-888X tem dupla fonte de alimentação de energia (energia solar e bateria de reserva), permitindo ope

SDC – Projects
If a text message is undesirable, the application will simply call the phone number and play a recording that says, "pre

Project Report
Project Report. On. IMPLEMENTATION OF QUALITY MANAGEMENT SYSTEM. IN RAYMOND MADE-TO-MEASURE. A dissertation submitted in