1

COPC/CSAB JAG-CCMStatus Updates and Recommendations

April 7, 2010

JAG-CCM Teamversion 4.0-20100331

2

Outline

• CCM Team Membership• Status Updates and Recommendations

– COPC Enterprise Network Requirements (Reconciliation, sizing, and budget estimates)

– COPC Enterprise Network TOC Linkage– NAEFS Latency– Development of the Next Generation COPC

Enterprise Network– Requirements gathering across the COPC partners– Pentagon and Silver Spring Connection During

Lockdown– OPCs Communications Backup Procedure

3

CCM TeamMember Organization

Charles Abel Air Force/AFWA/A6

Ken Barnett OFCM

Luis Cano NOAA/NWS/NCEP/NCO (CCM-Chair)

Seyed Hosseini NOAA/NESDIS/OSDPD/IPD

Tracy LePire Navy/NAVO

Jackie Lord NOAA/NWS/TOC

Sherryl Panek Navy/FNMOC

Charleston Simms Navy/CNMOC/N6

Technical Advisor/SME/Alternate Organization

Jami Casamento NOAA/NWS/OST

Derek Eddington Navy/FNMOC

Patrick Gregory NOAA/NESDIS/OCIO

Tom Harrison Air Force/AFWA/A6

Craig Hegemann NOAA/NWS/OCIO

Bruce Kenison DISA Field Office USSTRATCOM

Ben Kyger NOAA/NWS/NCEP/NCO

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

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

COPC Enterprise NetworkTOC Linkage

COPC Action Item 2009-2.2COPC 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

COPC Enterprise NetworkTOC 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

NAEFS Latency COPC Action Item 2009-2.8

• COPC Action Item 2009-2.8: JAG/OCM and JAG/CCM shall coordinate to develop an FY2010 schedule (Action Plan) for operational incorporation of the FNMOC NOGAPS into NAEFS, including actions necessary at both OPCs and TOC with a focus on addressing data latency issues in all organizations.

• Priority: (H)• Advocate: JAG/OCM, JAG/CCM• Suspense: 30 November 2009

9

NAEFS Latency COPC Action Item 2009-2.8

• Recommendation: close action item for CCM

• 2/3/2010: COPC DATMS network upgrade completed as planned– Reduced message throughput latency

between FNMOC and TOC– Ongoing activities with NAEFS group, e.g.,

intermittent product delay issues and new data requirements

10

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).

11

Development of the Next Generation COPC Enterprise Network

COPC Action Item 2008-2.11

• Recommendation: keep action item open

• Risk (high probability/high Impact):– funding to deploy enterprise network has not

been fully identified for NOAA

• Mitigation:– develop a common NOAA budget request

approach by coordinating with NWS and NESDIS stakeholders

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

Development of the Next Generation COPC Enterprise Network

COPC Action Item 2008-2.11

13

COPC FY12 FY13 FY14AWFA $292 $100 $100

FNMOC $292 $100 $100 NAVO $292 $100 $100 NCEP $1,722 $1,980 $1,980

NESDIS $1,722 $1,980 $1,980 TOC $875 $974 $974 Total $5,195 $5,233 $5,233

COPC Cost Estimates and Proposed Allocation ($1K)2013 COPC Weather Enterprise Network

•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

Development of the Next Generation COPC Enterprise Network

COPC Action Item 2008-2.11

• 1/13/2009: NOAA COPC Principles and NWS CIO provided direction to CCM to develop a common NOAA budget approach for the FY12-13 COPC Weather Enterprise

• 1/25/2009: NWS OCIO and NWS OST/SEC briefed and discussed common NWS budget approach

15

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)

• 4/12/2010: NWS and NESDIS meeting scheduled to discuss common NOAA budget approach for the FY12-13 COPC Weather Enterprise

16

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

17

Development of the Next Generation COPC Enterprise Network

COPC Action Item 2008-2.11

18

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

Schedule Summary

Date Milestones Assigned to Status Comments

Aug 24, 2009

Send network requirements to OFCM

COPC CIOs Complete •Received 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

Complete •Increased the bandwidth between AFWA, FNMOC, NAVO and NOAA•Removed end-of-life ATM hardware•Better routing paths

3rd QTR FY2010

Engage FY12 budget request process

COPC Partners

On Track •12/23/2009: CCM provided estimated budget for the 2013 COPC Weather Enterprise Network to COPC Principles•3/28/2010: Common NWS budget approach achieved

FY2011 Approve DoD-NOAA enterprise network design and budget

DISA, COPC CIOs & CFOs

None

FY2012 Initiate enterprise network build

DISA, CCM None •Contingent on funding in FY12

FY2013 Make enterprise network operational

CCM,

DISA

None •Contingent on funding in FY12

19

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).

20

Requirements Gathering Across COPC Partners COPC Action Item 2008-2.12

• Request CSAB assistance to complete action item– COPC and CNMOC network requirements gathering and analysis

successfully completed April-December 2009

– Assumption is COPC will gather network requirements annually

• Alternative #1– COPC open/close new action item each year for OFCM to issue data

call to COPC and CNMOC CIOs/TDs similar to 2009 OFCM data call

• Alternative #2– Leverage the DAPE to formalize network requirements gathering

process to include CNMOC

• Alternative #3– Develop separate agreement amongst COPC and CNMOC to gather

network requirements annually

21

Pentagon and Silver Spring CSAB Action Item 2010-1.1

CSAB Action Item 2010-1.1: The JAG/CCM shall confirm that the Pentagon to Silver Spring connection [IP address] be provisioned to continue communicating in the case of a DISA lockdown of all external connections during a significant National security event.

22

Pentagon and Silver Spring CSAB Action Item 2010-1.1

• Recommendation: close action item

• 2/9/2010: According to DATMS Service Manager and DISA CONUS ATM Circuit implementation POC, DISA will not terminate the DATMS circuit between Pentagon and Silver Spring during a significant National security event. In addition, DISA maintains Telecommunications Service Priority (TSP) on circuit to provide priority restoral in case of outage during a National critical event.

23

OPCs Communications Backup CSAB Action Item 2008-10.3

CSAB Action Item 2008-10.3: JAG/CCM will develop formal documentation which consolidates the procedures for implementing NIPRNet/Internet backup communications when DATMS-U goes down at each OPC. Additionally, CCM needs to consolidate and establish an agreed upon schedule to test/exercise these procedures. CSAB will document these procedures as a reference document for the P-14.

• Advocate: Mr. Luis Cano, JAG/CCM and CSAB• Suspense: Spring 2009 CSAB.

24

OPCs Communications Backup CSAB Action Item 2008-10.3

• Recommendation: keep action item open

• CCM focusing on DoD network between AFWA, FNMOC, NAVO and TOC

• Issues and questions– Legal for NWS to use Internet for operational backup?– Legal for DoD to use NIPERNET and DREN for operational backup?– Assuming using Internet, NIPERNET and DREN is allowed, what are

the C&A implications?– Presently NESDIS uses Internet routinely to deliver operational data

and products.– No formal agreement with SLA-type parameters, i.e., how long to wait to

invoke backups procedures between Centers