1 / 17

Some Ideas for Network Consolidation

Some Ideas for Network Consolidation. GTRA Conference June 24 th , 2012 Bedford Springs. Legacy Approach to Bandwidth Procurement . This has been GoC bandwidth procurement strategy for the last 20 years Only 2 - sometimes 3 providers can bid Almost all contracts national

finley
Download Presentation

Some Ideas for Network Consolidation

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. Some Ideas for Network Consolidation GTRA Conference June 24th, 2012 Bedford Springs

  2. Legacy Approach to Bandwidth Procurement • This has been GoCbandwidth procurement strategy for the last 20 years • Only 2 - sometimes 3 providers can bid • Almost all contracts national • by department • Telco assets more • regionally based Department A Department B Department C Department D

  3. Limited Competition and Bargaining Power PWGSC MPLS Peering PWGSC Data Ctr.

  4. Enter – The Third Option • More players – but one shared multi-service IP network • National Backbone provides a high speed redundant backbone that interconnects to all service provider networks • Regional price reductions estimates • between 30 – 40% • More competition • Better alignment with • GC policy • Less departmental • procurement disruption

  5. Organic Opportunity-Based Growth • Started in the National Capital Region • 40-50% of the GoCpopulaiton • Highest density • Most data centres • Quickest win • opportunity

  6. Background • Service Objective: • To provide the most competitive shared WAN Service in the GC • Service Components: • Acquire Fibre • Equipment – NESS • People – SM&D • Service Definition: Shared (virtualized) WAN in Ottawa Area • Schedule Milestones: • Contract Award – September 2007 • PoC / Beta Phase (September 2007 – September 2008 • Service Announcement Date – October 2008 • In service: 44 Months

  7. Sample Client Competitive Case

  8. Service Metrics • Current Service Status (44/ mths. from Service Announcement Date) • Monthly Run Rate: $1M • Service Availability: 99.999% - service has not been interrupted since it was installed (one dark-fibre cut on a remote site over 2 years) • Are 4 data centers are dependent on it: PenMod, PayMod etc.. • Average fulfillment period per site: 25 days • On average 10 – 100x more bandwidth for the same cost as outsourced services in the NCA • Current number of sites connected: 130 • Current number of clients: 20 • Big clients missing: DND 60 sites, CRA 25+sites, HRSDC 22 sites. • Limitations: NCA only

  9. Local Area Network – As Is • Many multi-tenant buildings • Redundant LAN infrastructures • VRF – VLAN mapping • Shared LAN Infrastructure • Voice / Video and Data virtualization • Price per port LAN model • LAN Service Levels standards Dept. A Dept. B Dept. C Dept. D Dept. n National Shared MPLS Network

  10. Current State Architecture Department A • Each Department has three • Data Centre Networks: • One connects to the departmental WAN • One connects to SCNet (Internet Access) • One is dedicated for Storage connectivity DCN-A3 (Storage) DCN-A1 (Data) DCN-A2 (Internet) WAN A SCNet Internet

  11. Consolidate DCNs within Each Department Department A • Step 1 in DC Consolidation • - Consolidate & virtualize the • DC Network – • Each DCN that is consolidated with • Save $$ • Annual Savings Estimates: DCN (Data, Storage & Internet) WAN A SCNet Internet

  12. Consolidate DCNs – Auxiliary Services Department A • Firewalls • IDS/IPS • Load Balancers • SRA Services • WiLAN Termination • Encryption Services • Etc.. DCN (Data, Storage & Internet) WAN A SCNet Internet

  13. Current State Architecture Multi-tenant Data Centres Department A Department B Department C Department D DCN-A3 (Storage) DCN-B3 (Storage) DCN-A3 (Storage) DCN-D3 (Storage) DCN-A1 (Data) DCN-B1 (Data) DCN-C1 (Data) DCN-A2 (Internet) DCN-D1 (Data) DCN-B2 (Internet) DCN-C2 (Internet) DCN-D2 (Internet) WAN B WAN C WAN D SCNet SCNet WAN A SCNet SCNet Internet

  14. Intra Data Centre Network Architecture – To Be • One Data Centre Network per Data Center/ All departments • Integrated Storage and Server Networks • Integrated Firewalls / Load Balancing • Virtualized / Logically separate / Security Zones & Domains Multi-tenant Data Centres – To Be Department A Department B Department C Department D Department E Department n Shared Consolidated Data Center Network GCNet Internet

  15. Mezo Plan Level: • GC-Wide ITSM Plan • PMO Assigned Planning & Governance MACROPLAN • Stream Level: • A Series of Related Initiatives • Broken down into small • Micro Initiatives (MIs) • Stream length 4-6 quarters • One MI per quarter per stream • PM per Stream • Quarterly governance/alignment review Mezo-plan 5 Feedback Learning Metrics Change & Risk Mgmt. WBS Etc. ITSM • Micro Initiative (MI) Level: • Agile initiative • Portfolio of initiatives that are small • and transformational • Under $4M in value • Must be able to complete in • 3 month rolling window • PMP refers to this as “Rollling Wave” • X-Function (plan/build/operate/user teams) • Opportunity-based Micro-plans ITSM Stream 1 3 5 2 3 4 5 1 3 4 1 2 4 5 1 2 Stream 2 Stream 3

  16. Planning, Governance & Alignment M A C R O P L A N • High level • 8 Year View • TB Sub • Policy & Standards • Indicative Business Case • Highlights Focus Areas Mezo-plan 1 Mezo-plan 2 Mezo-plan 3 Mezo-plan 4 Facilities Platform Storage Mainframe Micro-plans Facilities Micro-plans - MF Micro-plans Platform Micro-plans Storage Stream 1 Stream 1 Stream 1 Stream 1 2 1 2 3 4 5 1 2 3 3 5 4 5 1 1 2 3 4 5 1 2 3 5 4 3 4 5 4 1 2 1 4 1 2 3 4 5 5 1 2 3 4 3 1 2 2 5 4 5 4 3 2 5 3 1 2 1 3 5 4 Stream 2 Stream 2 Stream 2 Stream 2 Stream 3 Stream 3 Stream 3 Stream 3

  17. Lessons Learned • Start with a competitive analysis • Build an assumptive business case • Validate the business case and service model via production beta implementations • When the assumptions have been validated to to larger volume deployment One Network

More Related