1. 1 COPC/CSAB JAG-CCM Status Updates and Recommendations October 21, 2009 JAG-CCM Team version 1.3-20091016

2. 2 Outline CCM Team Membership Status Updates and Recommendations –Development of the Next Generation COPC Enterprise Network –Requirements gathering across the COPC partners Background Slides

3. 3 CCM Team MemberOrganization Charles AbelAir Force/AFWA/A6 Kenneth BarnettOFCM Luis Cano*NOAA/NWS/NCEP/NCO Patrick GregoryNOAA/NESDIS/OCIO VacantNavy/CNMOC/N6 Craig HegemannNOAA/NWS/OCIO/TOC Seyed HosseiniNOAA/NESDIS/OSDPD/IPD Ben KygerNOAA/NWS/NCEP/NCO Tracy LePireNavy/NAVO Sherryl PanekNavy/FNMOC *JAG-CCM Chair

4. 4 Development of the Next Generation COPC Enterprise Network COPC Action Item 2008-2.11: JAG CCM shall coordinate the development of the next generation COPC shared network infrastructure with DoD and NOAA IT leadership. The JAG CCM shall leverage projects currently underway that are planning a NOAANet-DoD enterprise network capability. [NUOPC related] Priority: (M) Advocate: JAG/CCM – [Luis Cano] Suspense: Spring 2009 CSAB meeting or (April 1, 2009).

5. 5 Development of the Next Generation COPC Enterprise Network

6. Short-term network upgrade –Estimate operational 2 nd Quarter FY2010 –Network upgrade include: AFWA from 14Mb,50Mb to 28Mb,60Mb FNMOC from 6Mb(2),14Mb to 28Mb(3) NAVO from 6Mb(2) to 28Mb(2) NOAA from 6Mb(2),50Mb to 28Mb(2),60Mb 6

7. Development of the Next Generation COPC Enterprise Network Status Summary Short-term COPC network upgrade –Excellent job by network team AFWA, CNMOC, FNMOC, DISA, NAVO, NESDIS, NWS and OFCM –Network team strengthened relationships across technical groups and worked DoD network provision process For years attempts to upgrade COPC network was not successful 7

8. 8 Development of the Next Generation COPC Enterprise Network Schedule Summary DateMilestonesAssigned toStatusComments Aug 24, 2009 Send network requirements to OFCM COPC CIOsComplete8/24/09: Received official response from CNMOC CIO, included network requirements for FNMOC and NAVO Sep 3, 2009 Initiate short-term network upgrade to COPC network CCM, CNMOC, DISA CompleteProvides short-term relief with increase bandwidth Replaces end-of-life ATM network backbone Replaces at-capacity ATM network equipment 2 nd QTR FY2010 Make short-term COPC network upgrade operational CCM, DISA On TrackNew routing strategy and back-out plans DAPE leveraged, may need additional agreement –type documentation 2 nd QTR FY2010 Engage FY12 budget request process COPC Partners None9/3/2003: DATMS-U upgrade process initiated Provides additional bandwidth and aligns with DISA plans FY2011Approve DoD-NOAA enterprise network design and budget DISA, COPC CIOs & CFOs On Track9/11/2009: Network analysis requirements in progress FY2012Initiate enterprise network build DISA, CCMNoneContingent on funding in FY12 FY2013Make enterprise network operational CCM, DISA NoneContingent on funding in FY12

9. 9 Development of the Next Generation COPC Enterprise Network Status and Recommendation Summary Status: –upgrade COPC DISA DATMS-U to OTN on track operational 2 nd quarter FY10 –planning DoD-NOAA Enterprise Network on track operational 1 st quarter FY13 Risk (high probability/high Impact): –funding to deploy enterprise network has not been identified Mitigation: –determine COPC shared network cost estimates –work DoD and NOAA budget request processes Recommendation: –keep action item 2008-2.11 open

10. 10 Requirements Gathering Across COPC Partners COPC Action Item 2008-2.12: JAG CCM will provide an ongoing process to capture and coordinate telecommunication requirements across COPC partners. These requirements would include the size of the data, when the data needs to be transmitted, when the data needs to be received, which COPC partner will send the data, which COPC partner will receive the data, the schedule of when new data will or needs to be enabled, encryption requirements, other data restrictions, and related COPC business functions. As a follow-on action item, this process would be used to validate technical designs and resource estimates for new network infrastructure initiatives. This process would provide COPC continuing value by supporting network capacity management for existing infrastructure and help justify funding requests for future network upgrades. [NUOPC related] Priority: (M) Advocate: JAG/CCM – [Luis Cano (Chair)] Suspense: Spring 2009 CSAB meeting or (April 1, 2009).

11. 11 Requirements Gathering Across COPC Partners DRAFT Network Sizing Estimates Based on Requirements Draft network sizing estimates –Based on network requirements provided by COPC IT Leadership –Will be reviewed and adjusted through coordination across COPC partners Assumptions –Network size estimates based on best practices to accommodate latency for bursty data and sufficient bandwidth to recover from network outages (+50%) plus overhead (+10%). –Requirements for AFWA/FNMOC/NAVO to/from NCEP/NESDIS create TOC requirements. The rationale is DoD partners will send/receive data with NCEP/NESDIS via the TOC's network and data flow services. –Requirements from NESDIS to NCEP moved to the TOC in 2013. Consistent with NWS OST/Booz Allen study, a proposed NOAA Consolidated Server Environment (CSE) would provide NCEP/NESDIS centralized data flow services from the TOC. Analysis does not consider computer/storage sizing, performance or latency, it focuses solely on estimating size of wide area network

12. Requirements Gathering Across COPC Partners DRAFT Network Sizing Estimates 12

13. Requirements Gathering Across COPC Partners DRAFT Network Sizing Estimates 13

14. Requirements Gathering Across COPC Partners DRAFT Network Sizing Estimates 14

15. Requirements Gathering Across COPC Partners DRAFT Network Sizing Estimates Based on Requirements 15

16. Requirements Gathering Across COPC Partners DRAFT Network Sizing Estimates Based on Requirements 16

17. 17 Requirements Gathering Across COPC Partners DateMilestonesAssigned toStatusComments Mar 14, 2009 Send shared network requirements data- call to COPC CIOs CCM and OFCM Complete CCM coordinated design of requirements template with DISA Template design captures annual requirements for 5- years into future Aug 24, 2009 Send network requirements to OFCM COPC CIOsComplete4/24/09: Original due date 8/24/09: Received official response from CNMOC CIO, included network requirements for FNMOC and NAVO Dec 2009Analyze requirements and review with COPC Partners and DISA CCMOn Track6/30/09: Original due date COPC CIOs and DISA use requirements analysis to help plan Next Generation COPC Enterprise Network AnnualUpdate COPC shared network requirements using annual data-call process CCM, OFCM and COPC CIOs None Annually update 5-year projection of COPC shared network requirements and share with COPC CIOs and DISA

18. 18 Requirements Gathering Across COPC Partners Status and Recommendation Summary Status: –gather and analyze COPC network requirements on track FY11-FY14 COPC network requirements analysis 1 st quarter FY10 reoccurring annual COPC network requirements gathering and analysis process 1 st quarter FY10 Risk (high probability/high Impact): –network reaching capacity prior to DoD-NOAA enterprise network creation planned for FY13 Mitigation: –verify network requirements across COPC partners –accelerate DoD-NOAA enterprise network build-out contingent on funding –COPC Principles make decisions on what not to support Recommendation: –keep action item 2008-2.12 open

19. Background Slides The following slides provide additional information 19

20. DoD-NOAA Enterprise Network Project Schedule 20

21. DATMS-U Silver Spring AP 1000 x.x127.32 x.x.249.22 Offutt AP 1000 x.x.129.31 x.x.249.30 Monterey Router x.x.249.17 Monterey AP 1000 x.x131.14 x.x249.18 Stennis Router x.x.249.25 Stennis AP 1000 x.x129.29 x.x249.26 Current DISA ATM System – Unclass (DATMS-U) for COPC.9.6 13.5 Offutt Router x.x249.29 CCSD-73WS CCSD-73WT CCSD-73WU.18.17.29 CCSD-73WH.14.10.30 Silver Spring ASX 1000 x.x117.161 Monterey ASX 1000 x.x.119.27 CCSD -73WJ Stennis ASX 1000 x.x118.68 Offutt ASX 1000 x.x118.31 OC3 CCSD – 6ARB 6TWB CCSD-73XZ CCSD-73XY DISN ATM Help Desk (800) 554-3476 DISN ATM NOC Alternate # (703) 735-3570/ 8351 DATMS-U NAVAF PM Terry Warren (703) 735-3520 As Of: Aug 2008 Silver Spring Router x.x249.21 6 Mb 50 Mb 14 Mb DS3 CCSD – 6GBF & OC3 CCSD – 6J4D 6TWA CCSD-73WG DS3 CCSD – 6HL5 6TWM OC3 CCSD – 6TNO 6TW6 CCSD -6574 21

22. 2010 COPC MIGRATION TO OTN OTN Silver Spring ATM Stennis Router x.x.249.25 Offutt Router x.x249.29 73WS-28 Mb 73WT-28 Mb 73WU-28 Mb PENTAGON ATM Monterey MSPP Stenni s ATM Offutt MSPP 73XZ-28 Mb 73XY-60 Mb Silver Spring Router x.x249.21 ETH 10/100 Gunter ATM ETH 10/100 2xETH 10/100 Gunter MSPP 3xETH 10/100 3xETH 10/100 PENTAGON MSPP Monterey Router x.x.249.17 ETH 10/100 22

23. 2013 DoD-NOAA Weather Enterprise Network 23