1 / 18

April 21, 2010 Infrastructure Wave Refresh Planning

April 21, 2010 Infrastructure Wave Refresh Planning. Agenda. Refresh Planning Process Refresh Plan Overview Data Center Consolidation Refresh Plan ANF EEA EOE EOLWD EOPSS EOHED MassDOT Web Consolidation Plan Refresh MassMail Plan Refresh. Wave Refresh Planning Process.

sani
Télécharger la présentation

April 21, 2010 Infrastructure Wave Refresh Planning

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. April 21, 2010 Infrastructure Wave Refresh Planning

  2. Agenda • Refresh Planning Process • Refresh Plan Overview • Data Center Consolidation Refresh Plan • ANF • EEA • EOE • EOLWD • EOPSS • EOHED • MassDOT • Web Consolidation Plan Refresh • MassMail Plan Refresh

  3. Wave Refresh Planning Process • Data Center Refresh Planning - Foundation • Created a planning spreadsheet that tracks • Every application in the Secretariat • Who owns the application and is it agency internal, Secretariat-wide, State government-wide, or public facing • The current platform (servers, storage, prime location, DR location) • The future state (servers, storage, prime location, DR location) • Current wave allocation, new wave allocation, any comments and notes • Overall Plan Refresh Process • Met with ANF, EEA, EOE, EOLWD, EOPSS, and MassDOT to: • Review the tracking spreadsheet to identify additions or changes • Identify additional opportunities to accelerate wave assignments • Review MassMail plans • Review Web Consolidation plans

  4. Detailed Data Center Consolidation Wave Refresh Process

  5. Data Center Consolidation Spreadsheet Application Name (one application per line) Application Owner (by person’s name) Application Type (Local, Secretariat, Enterprise, Commonwealth) Current State (Server type, Storage, Primary Loc, DR Loc) Future State (Server type, Storage, Primary Loc, DR Loc) Transition Cost (estimate) Move Duration (estimate) Sept ‘09 Wave & Timeframe New Wave Assignment

  6. Data Used to Refresh the Data Center Plan • Four sources of application/server data were used to form the basis of the refreshed plan: • Deloitte Task Order 2 Secretariat Infrastructure Roadmaps (Chapter 6, dated 10/2/09) • MITC/DC2 Planning Spreadsheet (dated 7/17/09) • Asset Repository (as of 4/20/10) • Feedback from the Secretariat CIOs during the recent plan refresh meetings • Data Consistency/Quality • ANF provided updates to the tracking spreadsheet during the past month • EEA stated that they need a “couple of months” to put in place a clear and consistent inventory • EOE new SCIO is working with the agencies to create a complete and accurate inventory • EOLWD generally consistent information, asset information not fully populated • EOPSS in process of creating a complete and accurate inventory • MassDOT provided a thorough application and server inventory

  7. Wave Definitions • Wave 1a: EOHHS Pilot – 600 Washington Street data center • Wave 1b: EOHHS Data Centers – Remaining EOHHS data centers Wave 2a: Systems At Risk (Non-HHS) - Identify Secretariat data center equipment at risk (e.g., under desks, in an unsecured location, maintenance soon to expire), the services should be moved to MITC as soon as possible • Wave 2b: Systems Requiring DR (Non-HHS) - Identify Secretariat data center equipment requiring interim DR services at MITC as soon as possible • Wave 3a: Least Inhibitors - Identify data center locations or sub-sets of servers that can move relatively easily within the next year • Wave 3b: Major Inhibitors - Identify data center location or sub-sets of servers that will require significant risk or effort to move, primary at Springfield Data Center

  8. Data Center Consolidation Wave Refresh Plan Overview

  9. ANF Plan Details • Key Considerations • Possibly bringing Comm-Pass in house (currently at Deloitte in Chicago) • Some minor apps (e.g. OMV vehicle audit may be getting decommissioned) • PERAC out of scope per ANF (separate entity) • DOR data center is currently in MITC, managed by DOR Summary Overview(Prior inventories / Asset Repository) • Number of Usage Sites: TBD • Number of Data Center Sites: 3 • Number of Primary Servers: 515/204 • Number of DR Servers: 192/ - • Number of Applications: 57 / 86 • Next Steps • Finalize Wave 2a/2b candidates as part of Wave 2a/2b detailed planning (July – Oct 2010)

  10. EEA Plan Details • Key Considerations • In process of determining extent of all data centers (and closets) • MassGIS is moving to ITD for FY11 (Infrastructure plan being developed in July 2010). Summary Overview(Prior inventories / Asset Repository) • Number of Usage Sites: TBD • Number of Data Center Sites: 6 • Number of Primary Servers: 87 / 57 • Number of DR Servers: TBD • Number of Applications: 68 / 85 • Next Steps • ITD and EEA to work together to revise application/server inventory • EEA to identify any missing applications / data centers • Finalize Wave 2a/2b candidates as part of Wave 2a/2b detailed planning (July – Oct 2010)

  11. EOE Plan Details • Key Considerations • EEC, CTF & Secretariat on MagNet • ESE & DHE not on MagNet • No pressing need for a robust DR solution • Race-to-the-Top will drive considerable changes to the applications within EOE • Impact of Malden data center Summary Overview(Prior inventories / Asset Repository) • Number of Usage Sites: • Number of Data Center Sites: 2 • Number of Primary Servers: 180 / 16 • Number of DR Servers: TBD • Number of Applications: - / 0 • Next Steps • EOE is in process of inventory update • ITD to work with EOE over the next two months to refine plan as data becomes available

  12. EOLWD Plan Details • Key Considerations • DWD has their own Frame Relay Network • DWD has their own Domain Name (DETMA.org) embedded in all their applications • DIA non-MagNet for 7 remote sites (Paetec MPLS) • DIA DR in Fall River (no wave 2b necessary) • DIA 600 Washington St moving to Congress St within next few months Summary Overview(Prior inventories / Asset Repository) • Number of Usage Sites: 37 Career Centers, 20 Satellite Offices, 7 DIA Remote Sites, 4 Call Centers • Number of Data Center Sites: 2 • Number of Primary Servers: 250/80 • Number of DR Servers: 6 • Number of Applications: 12 / 31 • Next Steps • CCTO developing network roadmap that will define timeline for DIA and DWD to migrate to MAIN. Depending on results may change and/or accelerate timelines • ITD to evaluate a process as part of consolidation of interim network consolidation under Magnet for networks such as DIA’s • EOLWD will evaluate if the migration of infrastructure to Congress street may be migrated to MITC in a co-location model

  13. EOPSS Plan Details • Key Considerations • EOPSS (like MassDOT) is consolidating internally (into MITC/CHSB) before planning the ITD consolidation • As part of Wave 3b, ITD and EOPSS need to coordinate/consolidate the management of the two data centers Summary Overview(Prior inventories / Asset Repository) • Number of Usage Sites: • Number of Data Center Sites: • Number of Primary Servers: 280 / 0 • Number of DR Servers: TBD • Number of Applications: 210 / 0 • Next Steps • Will continually adjust the consolidation wave assignment and timeline based on the progress of the internal consolidations

  14. EOHED Plan • EOHED has already co-located to MITC • Will start planning to transition to managed services starting Oct 2012 • Estimated full transition to managed services by Jan 2013

  15. MassDOT Plan Details • Key Considerations • Interested in having DR in Springfield. Would be willing to take out of SunGard and move to MITC • MassDOT provided a very detailed inventory of current state applications, servers, and data centers (part of a Legislative Report) Summary Overview(Prior inventories / Asset Repository) • Number of Usage Sites: 291 • Number of Data Center Sites: 8 • Number of Primary Servers: 361 / 0 • Number of DR Servers: TBD • Number of Applications: 240 / 0 • Next Steps • Work with MassDOT to identify any infrastructure hotelling (2b) needs/opportunities • Need number of DR racks that could potentially move to MITC • Further mainframe discussion

  16. MassMail & Web Consolidation • Web Consolidation • By the end of FY11, all Secretariats will be substantially on the Mass.Gov platform with the exception of MassDOT which plans to migrate to Mass.Gov after re-tooling (FY12) • MassMail • New Wave Definitions • Wave 1: Agencies that have current archive and retention methods they are willing to continue with for the time being • CPF, CHSB • Wave 2: Agencies that will be serviced by short term archive and retention solution • MassDOT, DIA • Wave 3a: Agencies on Exchange and require full archive, retention, and active directory solution in place • MTRB, DOR • Wave 3b: Agencies with unique needs or significant other issues • MSP, DOC: Not on MS Exchange • DHE, DESE: Not on MagNet • DWD: Original wave assignment

  17. MassMail Migration Plan

  18. Next Steps • Continue working with Secretariats to complete the detailed planning spreadsheets • Continue planning for Wave 1b with EOHHS • Revise capacity plan for two active data centers model based upon updated inventories

More Related