COPC/JAG-CCM Status Updates and Recommendations 16 November 2010

1. COPC/JAG-CCM Status Updates and Recommendations 16 November 2010 Chris Finnigsmier Acting JAG/CCM Chair

2. Outline • CCM TeamMembership • Status Updates and Recommendations • COPC Enterprise Network Requirements • Development of the Next Generation COPC Enterprise Network (aka DISA WENetDesign)

3. CCMTeam * Upcoming Vacancy ** Vacant role/representative*** New to the role or group

4. COPC Enterprise Network RequirementsCOPC Action Item 2010-1.1 COPC Action Item 2010-1.1: Exercise established processes to coordinate and capture telecommunication requirements across COPC partners, including NUOPC and JPSS related requirements. These requirements will identify current and future data flows including source, destinations, volume, latency requirement, schedule of when new data will be or needs to be enabled, encryption requirements, other data restrictions, and related COPC business functions. This information will be used to validate technical designs and resource estimates for new network infrastructure initiatives.

5. COPC Enterprise Network RequirementsCOPC Action Item 2010-1.1 May/June - CCM developed a revised template TDs/JAGs reviewed template’s design Identified correct individuals (modelers, data assimilations experts, etc.) to articulate requirements July – Data Call sent by Deputy Federal Coordinator (Suspense: 31 Aug 10) To CNMOC (John Meyer), AFWA (Michael Howland), TOC (Craig Hegemann), NCEP (Ben Kyger), and NESDIS (CDR Mark Moran) Sept – All data requirements submitted Sept/Oct – Analyzed the responses, reconciled differences between DOD and NOAA, asked for further fidelity

6. COPC Enterprise Network RequirementsCOPC Action Item 2010-1.1 Recommendation: Keep action item open until the requirements have been reconciled and reported

7. Development of Next Generation COPC Enterprise NetworkCOPC 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.

8. Development of Next Generation COPC Enterprise Network COPC Action Item 2008-2.11 • July/Aug 2010: Meetings with DISA to assist in the design of the COPC Weather Enterprise Network (WENet) • AFWA has funded the design effort at DISA • Sept 2010: Use the COPC Data Requirements as baseline for bandwidth, ports, and protocols

9. Development of Next Generation COPC Enterprise Network COPC Action Item 2008-2.11 • DISA Draft Concept of Design: • Future proof on throughput by standardizing on 10 Gig hardware through the WENet gateways • Geographic redundancy with some local redundancy (dual power supplies) • Four routers, two at each gateway • Two firewall/IDP, one at each gateway

10. Network Topology A Combat Support Agency UNCLASSIFIED // FOR OFFICIAL USE ONLY

11. Development of Next Generation COPC Enterprise Network COPC Action Item 2008-2.11 • DISA – Tasks completed: • Validated design by performing lab testing • Determined secondary WENet node location and finalize circuit costs • DISA - Tasks to be completed: • Provide detailed design document to include NOAA and NAVO (Stennis) portion • Propose a complete cost breakdown to include circuit and equipment costs, and who pays for what

12. Development of the Next Generation COPC Enterprise NetworkCOPC Action Item 2008-2.11 • Recommendation: • Close this action item • DISA has provided design and has performed preliminary testing • Open new action item • Each center develop detailed implementation plan to how to achieve the final design • JAG/CCM proposes the cost sharing mechanism (Annex to DAPE)