Presentation is loading. Please wait.

Presentation is loading. Please wait.

NOAA’s NWS Telecommunication Gateway RTH Washington Fred Branski Office of the Chief Information Officer NOAA’s National Weather Service 20 th NamEurDEx.

Similar presentations


Presentation on theme: "NOAA’s NWS Telecommunication Gateway RTH Washington Fred Branski Office of the Chief Information Officer NOAA’s National Weather Service 20 th NamEurDEx."— Presentation transcript:

1 NOAA’s NWS Telecommunication Gateway RTH Washington Fred Branski Office of the Chief Information Officer NOAA’s National Weather Service 20 th NamEurDEx Meeting May 22-24, 2007 Fred Branski Office of the Chief Information Officer NOAA’s National Weather Service 20 th NamEurDEx Meeting May 22-24, 2007

2 “Taking the pulse of the planet” NWSTG/RTH Functional Overview  The NWSTG/RTH is  the central communication facility of the NWS;  the primary acquisition and distribution center for NWS data and products;  the primary acquisition and distribution center for international data and products to meet WMO, ICAO and bi-laterally agreed US requirements;  A major data exchange hub for NOAA and other agency data and products.  Will become Washington Global Information Systems Center (GISC) within the WMO Information System (WIS).  The NWSTG/RTH is  the central communication facility of the NWS;  the primary acquisition and distribution center for NWS data and products;  the primary acquisition and distribution center for international data and products to meet WMO, ICAO and bi-laterally agreed US requirements;  A major data exchange hub for NOAA and other agency data and products.  Will become Washington Global Information Systems Center (GISC) within the WMO Information System (WIS).

3 “Taking the pulse of the planet” Replacement & Backup NWSTG (RTG/BTG)  Full functional replacement of existing capabilities  Expanded capacity and capability  Transition to new technology –Message queuing (MQ) for internal transport –Network centric systems interconnectivity –Relational database central processing engine –NAS/SAN storage solutions  Highly scaleable architecture  Planned Hardware refresh  Full functional replacement of existing capabilities  Expanded capacity and capability  Transition to new technology –Message queuing (MQ) for internal transport –Network centric systems interconnectivity –Relational database central processing engine –NAS/SAN storage solutions  Highly scaleable architecture  Planned Hardware refresh

4 “Taking the pulse of the planet” Government Networking Requirements - NOAANet IP-based networking solution − Any-to-any connectivity − High degree of bandwidth scalability − Optimum redundancy and survivability − IP convergence (i.e., voice, video and data over IP) − High-end performance Network security remains paramount, particularly in light of today’s socio-political threats Segmentation from the public Internet Minimizes risk of security or privacy breaches

5 “Taking the pulse of the planet” RTG/BTG/NOAANet Status  RTG & BTG connections to NOAANet in place  Internal NWS connections underway  External Gateway migrations planned –Began December 01, 2006 –Initially two Access Points for external connectivity –One within the RTG facility but external to the infrastructure (temporary to facilitate transitions) –One in New York City– GTS, AFTN / FAA / Hawaii / Micronesia, others? –Possibly Atlanta, Chicago, Tacoma, ??? (based on need &cost)  RTG & BTG connections to NOAANet in place  Internal NWS connections underway  External Gateway migrations planned –Began December 01, 2006 –Initially two Access Points for external connectivity –One within the RTG facility but external to the infrastructure (temporary to facilitate transitions) –One in New York City– GTS, AFTN / FAA / Hawaii / Micronesia, others? –Possibly Atlanta, Chicago, Tacoma, ??? (based on need &cost)

6 “Taking the pulse of the planet” NOAANet Transition  NOAANet: RTG OC-12 / BTG OC-3 (OC-12 in progress)  Customer transitions to NOAANET: Dec 01, 2006 to May 31, 2007  Internal underway, NWS regions done, NCF, NESDIS soon  External – began December 01, 2006 –Initially two Access Points for external connectivity –One within the RTG facility but external to the infrastructure (temporary to facilitate transitions) –One in New York City– GTS, AFTN / FAA / Hawaii / Micronesia, Others? –Possibly Atlanta, Chicago, Tacoma, ??? (based on need &cost)  NOAANet: RTG OC-12 / BTG OC-3 (OC-12 in progress)  Customer transitions to NOAANET: Dec 01, 2006 to May 31, 2007  Internal underway, NWS regions done, NCF, NESDIS soon  External – began December 01, 2006 –Initially two Access Points for external connectivity –One within the RTG facility but external to the infrastructure (temporary to facilitate transitions) –One in New York City– GTS, AFTN / FAA / Hawaii / Micronesia, Others? –Possibly Atlanta, Chicago, Tacoma, ??? (based on need &cost)

7 “Taking the pulse of the planet” RTG/BTG/NOAANet Status  RTG IOC June 26, 2006 / RTG FOC – July 31, 2006  Performance Metric Threshold – System Availability (averaged monthly) 99.90% – Warning Message Latency (averaged monthly) 10 seconds – Routine Message Latency (averaged monthly) 60 seconds – Daily Traffic Volume (averaged monthly) 1.2TB  NWSTG Performance Results (measured Feb 06, 2006)  Performance Category Threshold Actual –System Availability 99.90%100% –Warning Message Latency10 seconds< 1 second –Routine Message Latency60 seconds< 1 second –Daily Traffic Volume1.2TB1.1TB  RTG IOC June 26, 2006 / RTG FOC – July 31, 2006  Performance Metric Threshold – System Availability (averaged monthly) 99.90% – Warning Message Latency (averaged monthly) 10 seconds – Routine Message Latency (averaged monthly) 60 seconds – Daily Traffic Volume (averaged monthly) 1.2TB  NWSTG Performance Results (measured Feb 06, 2006)  Performance Category Threshold Actual –System Availability 99.90%100% –Warning Message Latency10 seconds< 1 second –Routine Message Latency60 seconds< 1 second –Daily Traffic Volume1.2TB1.1TB

8 “Taking the pulse of the planet” RTH Washington Thruput Times

9 Frames (frames/sec) Bytes (bytes/sec) Bandwidth Utilization Total Bandwidth Utilization RTH Exeter – RTH Washington Link Thursday, May 17 2007 Psbl traffic shaping issue To KWBC To EGRR Capped? Bursting No issues with frames

10 RTH Exeter – RTH Washington Text Link Thursday, May 17 2007 Bytes from EGRR 500 Kb Min, Avg & Max input delay 1 Minute 1.5 Mb 20 Seconds

11 RTH Exeter – RTH Washington Text Link Thursday, May 17 2007 Products from EGRR 500 # Products by size 500 1000

12 RTH Exeter – RTH Washington Binary Link Thursday, May 17 2007 Bytes from EGRR 4 Mb Min, Avg & Max input delay 50 Seconds 6 Mb 100 Seconds

13 RTH Exeter – RTH Washington Binary Link Thursday, May 17 2007 Products from EGRR 500 # Products by size 500 1500

14 RTH Exeter – RTH Washington Pictorial Link Thursday, May 17 2007 Bytes from EGRR 50 Kb 10 Seconds Min, Avg & Max input delay 20 Seconds

15 Products from EGRR RTH Exeter – RTH Washington Pictorial Link Thursday, May 17 2007 10 # Products by size 10

16 RTH Exeter – RTH Washington Text Link Thursday, May 17 2007 Avg Thruput to EGRR Transmission Delay Internal Delay Total Delay 100 Minutes 2.78 Hours

17 RTH Exeter – RTH Washington Text Link Thursday, May 17 2007 Max Thruput to EGRR Transmission Delay Internal Delay Total Delay 100 Minutes 200 Minutes 4.44 Hours

18 RTH Exeter – RTH Washington Binary Link Thursday, May 17 2007 Avg Thruput to EGRR Transmission Delay Internal Delay Total Delay 100 Minutes 200 Minutes 3.89 Hours

19 RTH Exeter – RTH Washington Binary Link Thursday, May 17 2007 Max Thruput to EGRR Transmission Delay Internal Delay Total Delay 100 Minutes 200 Minutes 4.44 Hours

20 Bandwidth Utilization Bandwidth Utilization Total Bytes (bytes/sec) Frames (frames/sec) CMC – RTH Washington Link Thursday, May 17 2007 To KWBC To CWRO

21 CMC – RTH Washington Text Link Thursday, May 17 2007 Bytes from CWTO 50 Kb 150 Kb Min, Avg & Max input delay 50 Seconds 100 Seconds

22 Products from CWTO CMC – RTH Washington Text Link Thursday, May 17 2007 100 300 # Products by size 100 300

23 CMC – RTH Washington Binary Link Thursday, May 17 2007 Bytes from CWTO 200 Kb 800 Kb Min, Avg & Max input delay 10 Seconds 40 Seconds

24 CMC – RTH Washington Binary Link Thursday, May 17 2007 Products from CWTO 100 500 # Products by size 100 500

25 RTH Washington All products Thursday, May 17 2007 Bytes to KWBC 200 Mb 600 Mb Min, Avg & Max input delay 100 Seconds 200 Seconds

26 RTH Washington All products Thursday, May 17 2007 Products to KWBC 10 K 40 K # Products by size 10 K 40 K

27 RTH Washington All products Thursday, May 17 2007 Avg Inter-System Thruput Transmission Delay Internal Delay Total Delay 60 Seconds 20 Seconds 140 Seconds

28 RTH Washington All products Thursday, May 17 2007 Transmission Delay Internal Delay Total Delay Max Inter-System Thruput 100 Seconds 200 Seconds 600 Seconds

29 “Taking the pulse of the planet” Issues  MTN Cloud 1 Expiry –Contract end - Dec 2007 –BT interested in 1 year extension –WMO coordination underway, meeting late 2007  RTH Exeter – RTH Washington Link –Delays up to 5 hours –Psbl traffic shaping issue –Traffic growth expected –Should we up bandwidth up current link or wait for cloud 1 replacement?  MTN Cloud 1 Expiry –Contract end - Dec 2007 –BT interested in 1 year extension –WMO coordination underway, meeting late 2007  RTH Exeter – RTH Washington Link –Delays up to 5 hours –Psbl traffic shaping issue –Traffic growth expected –Should we up bandwidth up current link or wait for cloud 1 replacement?

30 “Taking the pulse of the planet” Issues  CMC – Washington Link –No problem with existing traffic on link –Plan to move NAEFS data to operational link –Psbl move of RADAR data to link –NWS/OCIO investigating cost of upgrade –Should we look at NESDIS requirement also?  WMO Information System (WIS)? –Euro GISC – Washington GISC interaction & needs? –Metadata catalogue coordination? –Communication requirements? –When to address this - next meeting?  CMC – Washington Link –No problem with existing traffic on link –Plan to move NAEFS data to operational link –Psbl move of RADAR data to link –NWS/OCIO investigating cost of upgrade –Should we look at NESDIS requirement also?  WMO Information System (WIS)? –Euro GISC – Washington GISC interaction & needs? –Metadata catalogue coordination? –Communication requirements? –When to address this - next meeting?

31 “Taking the pulse of the planet” Your Data and Product Advocates Data Management Staff Fred Branski fred.branski@noaa.gov (301) 713-0864 ext 146 Julie Hayes - Family of Services Manager julie.hayes@noaa.gov (301) 713-0864 ext 120 Walter Smith - Team Lead, Data Management walter.smith@noaa.gov (301) 713-0864 ext 139 Richard Robinson - Data Manager richard.robinson@noaa.gov (301) 713-0864 ext 179 Cynthia Cromwell – Data Manager cynthia.cromwell@noaa.gov (301) 713-0864 ext 143 KWBC Communication Control Center (CCC) - Tech Control Point of contact 24 hours every day Toc.Nwstg@noaa.gov Phone: (301) 713-0902 Fax : (301) 587-1773

32 “Taking the pulse of the planet” Thank You! Additional Questions??? Additional Questions???


Download ppt "NOAA’s NWS Telecommunication Gateway RTH Washington Fred Branski Office of the Chief Information Officer NOAA’s National Weather Service 20 th NamEurDEx."

Similar presentations


Ads by Google