1. 1 COPC JAG-CCM Status Updates and Recommendations May 4, 2010 JAG-CCM Team version 4.2-20100428

2. 2 Outline CCM Team Membership Status Updates and Recommendations –COPC Enterprise Network Requirements (Reconciliation, sizing, and budget estimates) –COPC Enterprise Network TOC Linkage –Development of the Next Generation COPC Enterprise Network –Requirements gathering across the COPC partners

3. 3 CCM Team MemberOrganization Charles AbelAir Force/AFWA/A6 Ken BarnettOFCM Luis CanoNOAA/NWS/NCEP/NCO (CCM-Chair) Seyed HosseiniNOAA/NESDIS/OSDPD/IPD Tracy LePireNavy/NAVO Jackie LordNOAA/NWS/TOC Sherryl PanekNavy/FNMOC Charleston SimmsNavy/CNMOC/N6 Technical Advisor/SME/AlternateOrganization Jami CasamentoNOAA/NWS/OST Derek EddingtonNavy/FNMOC Patrick GregoryNOAA/NESDIS/OCIO Tom HarrisonAir Force/AFWA/A6 Craig HegemannNOAA/NWS/OCIO Bruce KenisonDISA Field Office USSTRATCOM Ben KygerNOAA/NWS/NCEP/NCO

4. 4 COPC Enterprise Network Requirements COPC Action Item 2009-2.1 COPC Action Item 2009-2.1: JAG CCM shall coordinate with COPC partners to reconcile the FY11-FY14 network requirements and assumptions. The requirements shall include COPC related or COPC impacted initiatives such as NUOPC. Using the reconciled FY11-FY14 network requirements and assumptions, the JAG CCM shall coordinate and finalize the COPC FY11-FY14 network sizing estimates. The network sizing estimates and assumptions will be used to create a ROM budget estimate to build and make operational the 2013 COPC Enterprise Network. These ROM estimates can be used by each COPC partner to engage their respective budget request process. Priority: (H) Advocate: JAG/CCM – [Luis Cano] Suspense: November 26, 2009.

5. 5 COPC Enterprise Network Requirements COPC Action Item 2009-2.1 Recommendation: close action item 12/8/2009: 2009 COPC network requirements disparity resolved 12/23/2009:ROM network sizing and budget estimates provided to COPC principles

6. 6 COPC Enterprise Network TOC Linkage COPC Action Item 2009-2.2 COPC Action Item 2009-2.2: JAG CCM shall coordinate with the NWS TOC the linkage of the NWS Backup Telecommunication Gateway (BTG) network architectural design with the 2013 COPC Enterprise Network plans. Priority: (M) Advocate: JAG/CCM – [Luis Cano] Suspense: 2nd QTR FY10.

7. 7 COPC Enterprise Network TOC Linkage COPC Action Item 2009-2.2 Recommendation: close action item 3/18/2010: COPC Enterprise Network integrated with NOAANet into NOAA’s Local Forecasts and Warnings (LFW) Program, Disseminate Critical Information, FY12 Program Change Summary (PCS)

8. 8 Development of the Next Generation COPC Enterprise Network COPC Action Item 2008-2.11 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).

9. 9 Development of the Next Generation COPC Enterprise Network COPC Action Item 2008-2.11

10. 10 Development of the Next Generation COPC Enterprise Network COPC Action Item 2008-2.11 Recommendation: keep action item open Issue (High Impact): –funding to deploy enterprise network has not been fully identified for NOAA Mitigation: –there is NESDIS and NWS agreement to leverage other projects to build parts of the network where possible –engage the NOAA FY13 budget request process

11. 11 Development of the Next Generation COPC Enterprise Network COPC Action Item 2008-2.11 Schedule Summary DateMilestonesAssigned toStatusComments Aug 24, 2009 Send network requirements to OFCM COPC CIOsCompleteReceived official response from all COPC organizations Sep 3, 2009 Initiate short-term network upgrade to COPC network CCM, CNMOC, DISA Complete Highly coordinated effort from AFWA, CNMOC, DISA, FNMOC, NAVO, and NOAA [NCEP, NESDIS & TOC] Feb 3, 2010 Make short-term COPC network upgrade operational CCM, DISA CompleteIncreased the bandwidth between AFWA, FNMOC, NAVO and NOAA Removed end-of-life ATM hardware 3 rd QTR FY2010 Engage FY12 budget request process COPC Partners Issue12/23/2009: CCM provided estimated budget for the 2013 COPC Weather Enterprise Network to COPC Principles 3/28/2010: FY12 common NWS budget approach achieved 4/12/2010: Fy12 common NESDIS budget approach not achieved FY2011Approve DoD-NOAA enterprise network design and budget DISA, COPC CIOs & CFOs None FY2012Initiate enterprise network build DISA, CCMNoneContingent on funding in FY12 FY2013Make enterprise network operational CCM, DISA NoneContingent on funding in FY12

12. 12 Development of the Next Generation COPC Enterprise Network COPC Action Item 2008-2.11 12/23/2009: COPC Principles provided with network sizing and budget estimates –Funding needed in FY12 to initiate network provisioning process to make operational the COPC Weather Enterprise Network by FY13 –Important for each COPC Center to achieve their portion of the budget allocation to build the end-to- end enterprise network –Leverage other projects to build parts of the network sooner

13. Development of the Next Generation COPC Enterprise Network COPC Action Item 2008-2.11 13 DoD-NOAA GW costs shared across COPC Partners AFWA, FNMOC, NAVO, NCEP and NESDIS NCEP and NESDIS includes integration with NOAANet TOC includes network to one non-AFWA location

14. 14 Development of the Next Generation COPC Enterprise Network COPC Action Item 2008-2.11 1/13/2010: NOAA COPC Principles and NWS CIO provided direction to CCM to develop a common NOAA budget approach for the FY12-13 COPC Weather Enterprise

15. 15 Development of the Next Generation COPC Enterprise Network COPC Action Item 2008-2.11 1/25/2010: NWS OCIO and NWS OST/SEC briefed and discussed common NWS budget approach

16. 16 Development of the Next Generation COPC Enterprise Network COPC Action Item 2008-2.11 3/18/2010: COPC Enterprise Network integrated with NOAANet into NOAA’s Local Forecasts and Warnings (LFW) Program, Disseminate Critical Information, FY12 Program Change Summary (PCS)

17. 17 Development of the Next Generation COPC Enterprise Network COPC Action Item 2008-2.11 4/12/2010: NWS and NESDIS meeting to discuss common NOAA budget approach for the FY12-13 COPC Weather Enterprise 1. NESDIS and NWS agreement for a common NOAA budget approach for the COPC Weather Enterprise Network. Broader network benefits may be realized depending how NOAA network requirements are scoped, gathered and integrated.

18. 18 Development of the Next Generation COPC Enterprise Network COPC Action Item 2008-2.11 4/12/2010: NWS and NESDIS meeting (continued) 2. From NWS perspective, the COPC Enterprise Network is integrated with NOAANet into NOAA’s Local Forecasts and Warnings Program, Disseminate Critical Information, FY12 Program Change Summary.

19. 19 Development of the Next Generation COPC Enterprise Network COPC Action Item 2008-2.11 4/12/2010: NWS and NESDIS meeting (continued) 3. From NESDIS perspective, it is too late to engage NESDIS' FY12 budget activities. The next opportunity to engage the budget request process is FY13. 4. There is NESDIS and NWS agreement to leverage other projects to build parts of the network where possible.

20. 20 Development of the Next Generation COPC Enterprise Network COPC Action Item 2008-2.11 3/23/2010: AFWA CCM member briefed CCM for AFWA to engage DISA to initiate the design of the COPC Enterprise Network Gateway –CCM team concurs with approach

21. 21 Requirements Gathering Across COPC Partners COPC Action Item 2008-2.12 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).

22. 22 Requirements Gathering Across COPC Partners COPC Action Item 2008-2.12 Recommendation: close action item and open new action item COPC and CNMOC network requirements gathering and analysis successfully completed April-December 2009 With CSAB concurrence, request COPC open new action item for OFCM to issue data call to COPC and CNMOC CIOs/TDs similar to 2009 OFCM data call