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

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

Embed Size (px)

Citation preview

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

1

COPC/CSAB JAG-CCMStatus Updates and Recommendations

October 21, 2009

JAG-CCM Teamversion 1.3-20091016

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

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

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

3

CCM Team

Member Organization

Charles Abel Air Force/AFWA/A6

Kenneth Barnett OFCM

Luis Cano* NOAA/NWS/NCEP/NCO

Patrick Gregory NOAA/NESDIS/OCIO

Vacant Navy/CNMOC/N6

Craig Hegemann NOAA/NWS/OCIO/TOC

Seyed Hosseini NOAA/NESDIS/OSDPD/IPD

Ben Kyger NOAA/NWS/NCEP/NCO

Tracy LePire Navy/NAVO

Sherryl Panek Navy/FNMOC

*JAG-CCM Chair

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

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

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

5

Development of the Next Generation COPC Enterprise Network

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

Development of the Next Generation COPC Enterprise Network

• Short-term network upgrade– Estimate operational 2nd 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

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

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

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

8

Development of the Next Generation COPC Enterprise NetworkSchedule Summary

Date Milestones Assigned to Status Comments

Aug 24, 2009

Send network requirements to OFCM

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

Complete •Provides short-term relief with increase bandwidth•Replaces end-of-life ATM network backbone•Replaces at-capacity ATM network equipment

2nd QTR FY2010

Make short-term COPC network upgrade operational

CCM,

DISA

On Track •New routing strategy and back-out plans•DAPE leveraged, may need additional agreement –type documentation

2nd QTR FY2010

Engage FY12 budget request process

COPC Partners

None •9/3/2003: DATMS-U upgrade process initiated•Provides additional bandwidth and aligns with DISA plans

FY2011 Approve DoD-NOAA enterprise network design and budget

DISA, COPC CIOs & CFOs

On Track •9/11/2009: Network analysis requirements in progress

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

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

9

Development of the Next Generation COPC Enterprise Network

Status and Recommendation Summary

• Status:– upgrade COPC DISA DATMS-U to OTN on track

• operational 2nd quarter FY10

– planning DoD-NOAA Enterprise Network on track• operational 1st 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

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

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

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

11

Requirements Gathering Across COPC PartnersDRAFT 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

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

Requirements Gathering Across COPC PartnersDRAFT Network Sizing Estimates

12

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

Requirements Gathering Across COPC PartnersDRAFT Network Sizing Estimates

13

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

Requirements Gathering Across COPC PartnersDRAFT Network Sizing Estimates

14

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

Requirements Gathering Across COPC PartnersDRAFT Network Sizing Estimates Based on Requirements

15

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

Requirements Gathering Across COPC PartnersDRAFT Network Sizing Estimates Based on Requirements

16

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

17

Requirements Gathering Across COPC Partners

Date Milestones Assigned to Status Comments

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 CIOs Complete •4/24/09: Original due date•8/24/09: Received official response from CNMOC CIO, included network requirements for FNMOC and NAVO

Dec 2009 Analyze requirements and review with COPC Partners and DISA

CCM On Track •6/30/09: Original due date •COPC CIOs and DISA use requirements analysis to help plan Next Generation COPC Enterprise Network

Annual Update 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

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

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 1st quarter FY10• reoccurring annual COPC network requirements gathering and analysis process

1st 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

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

Background Slides

• The following slides provide additional information

19

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

DoD-NOAA Enterprise NetworkProject Schedule

20

ID Task Name Start Finish

1 COPC Enterprise Shared Network Infrastructure Thu 2/26/09 Wed 12/19/12

2 COPC Shared Network requirements Thu 2/26/09 Tue 12/15/09

3 Meet with COPC IT Leaders Thu 2/26/09 Thu 2/26/09

4 Complete DATACALL for network requirements Wed 3/11/09 Mon 8/24/09

5 Perform network requirements analysis Fri 9/11/09 Tue 10/13/09

6 Review network requirements analysis Wed 10/14/09 Tue 12/15/09

7 COPC DoD-NOAA Enterprise Network Design + Cost Estimates Wed 12/16/09 Tue 4/12/11

8 Perform initial DoD-NOAA enterprise network analysis & budget estimates Wed 12/16/09 Tue 1/26/10

9 Perform alternative analysis of DoD-NOAA enterprise network & budget estimates Wed 3/31/10 Tue 9/14/10

10 Review alternative analysis of DoD-NOAA enterprise network & budget estimates Wed 9/15/10 Tue 12/7/10

11 Finalize alternative analysis of DoD-NOAA enterprise network & budget estimates Wed 12/8/10 Tue 1/18/11

12 Approve DoD-NOAA enterprise network design and budget estimate Tue 4/12/11 Tue 4/12/11

13 COPC Shared Cost Model & Approved Budget Plan Wed 1/6/10 Tue 12/20/11

14 Engage FY12 budget request process Wed 1/6/10 Tue 5/11/10

15 Define DoD-NOAA cost sharing model Wed 12/8/10 Tue 1/18/11

16 Review DoD-NOAA budget plan & cost sharing model Wed 1/19/11 Tue 4/12/11

17 Approve final budget plan & cost sharing model Tue 7/5/11 Tue 7/5/11

18 Perform DoD & NOAA legal review Wed 7/6/11 Tue 12/20/11

19 Operational COPC Shared Enterprise Network (Contingent on Funding) Thu 3/1/12 Wed 12/19/12

20 Allocate funding Thu 3/1/12 Thu 3/1/12

21 Provision network circuits and equipment Thu 3/1/12 Wed 7/4/12

22 Test networks Thu 7/5/12 Wed 8/15/12

23 Achieve IA Certification Thu 8/16/12 Wed 11/7/12

24 Transition & make operational Thu 11/8/12 Wed 12/19/12

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

DATMS-U

Silver Spring AP 1000

x.x127.32

x.x.249.22

Offutt AP 1000

x.x.129.31

x.x.249.30

MontereyRouter

x.x.249.17

Monterey AP 1000

x.x131.14

x.x249.18

StennisRouter

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

OffuttRouter

x.x249.29

CCSD-73WSCCSD-73W

T

CC

SD-7

3WU

.18

.17

.29

CCSD-73WH

.14

.10

.30Silver Spring

ASX 1000

x.x117.161MontereyASX 1000

x.x.119.27

CCSD -73WJ

StennisASX 1000

x.x118.68

OffuttASX 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 SpringRouter

x.x249.21

6 Mb 6 Mb

6 M

b

50 Mb14 Mb

DS3 CCSD – 6GBF & OC3 CCSD – 6J4D

6TWA

CCSD-73WG

DS3 CCSD – 6HL5

6TWM

OC3 CCSD – 6TNO

6TW6

CCSD -6574

21

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

2010 COPC MIGRATION TO OTN

OTN

Silver Spring ATM

Stennis Routerx.x.249.25

Offutt Router

x.x249.29

73WS-28 Mb

73WT-28 M

b

73W

U-2

8

Mb

PENTAGONATM

MontereyMSPP

StennisATM

OffuttMSPP 73XZ-28 Mb

73XY-60 MbSilver SpringRouter

x.x249.21

ETH10/100

GunterATM

ETH10/100

2xETH10/100

GunterMSPP

3xETH10/100

3xETH10/100

PENTAGONMSPP

Monterey Router

x.x.249.17

ETH 10/100

ETH 10/100

ETH 10/100ETH 10/100

ETH 10/100

22

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

2013 DoD-NOAA Weather Enterprise Network

23