1 / 45

NOAA’s NWS Telecommunication Gateway RTH Washington

NOAA’s NWS Telecommunication Gateway RTH Washington. Fred Branski Office of the Chief Information Officer NOAA’s National Weather Service 8th APSDEU Meeting Oct 10-12, 2007. NWSTG/RTH Functional Overview. The NWSTG/RTH is the central communication facility of the NWS;

xiang
Download Presentation

NOAA’s NWS Telecommunication Gateway RTH Washington

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NOAA’sNWS Telecommunication GatewayRTH Washington • Fred Branski • Office of the Chief Information Officer • NOAA’s National Weather Service • 8th APSDEU Meeting • Oct 10-12, 2007

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

  3. NWSTG/RTHFunctional Overview The NWSTG includes • WMO Regional Telecommunication Hub (RTH) Washington • ICAO OPMET Databank (KWBCYMYX) • the ASOS Operations and Monitoring Center (AOMC) • Operational oversight of U.S. federal automated surface observing systems • the AWIPS Network Control Facility (NCF) • AWIPS is the main NWS’ system which supports the NWS forecast and warning mission requirement • The NCF is the central communications hub and technical support center for AWIPS

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

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

  6. NOAAnet Transition • NOAAnet: RTG OC-12 / BTG OC-3 (OC-12 in progress) • Customer transitions to NOAAnet: December 2006 to September 2008 • Internal underway, NWS regions done, NCF, NESDIS soon • External – direct to NOAAnet or through an Access Point • 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. NWSTG NOAAnet TransitionCurrent Customer Connectivity

  8. NWSTG NOAAnet TransitionNo Direct Connect RTG Customers

  9. NWSTG NOAAnet TransitionEnd State for Customer Connectivity

  10. RTG/BTG Status &Performance • 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 February) • Performance Category Threshold Actual • System Availability 99.90% 100% • Warning Message Latency 10 seconds < 1 second • Routine Message Latency 60 seconds < 1 second • Daily Traffic Volume 1.2TB 1.1TB

  11. RTG/BTG Performance - RUC134.5Gb/day 67K products per day Avg Internal Delay: 1.31sec Avg Total Delay    : 6.91sec

  12. RTG/BTG Performance - RUC134.5Gb/day 67K products per day Avg Internal Delay: 1.31sec Avg Total Delay    : 6.91sec

  13. RTH Washington Thruput Times

  14. RTH Tokyo – RTH Washington Text Link Monday Oct 08, 2007 Bytes from RJTD 150 Kb 100 Kb 50 Kb Min, Avg & Max input delay 15 Seconds 5 Seconds

  15. RTH Tokyo – RTH Washington Text Link Monday Oct 08, 2007 Products from RJTD 150 100 50 # Products by size 150 100 50

  16. RTH Tokyo – RTH Washington Binary Link Monday Oct 08, 2007 Bytes from RJTD 3 Mb 1 Mb Min, Avg & Max input delay 15 Seconds 5 Seconds

  17. RTH Tokyo – RTH Washington Binary Link Monday Oct 08, 2007 Products from RJTD 1000 500 # Products by size 1000 500

  18. RTH Tokyo – RTH Washington Pictorial Link Monday Oct 08, 2007 Bytes from RJTD 200 Kb 150 Kb Min, Avg & Max input delay 4 Seconds 1 Seconds

  19. RTH Tokyo – RTH Washington Pictorial Link Monday Oct 08, 2007 Products from RJTD 3 # Products by size 3

  20. RTH Melbourne – RTH Washington Text Link Monday Oct 08, 2007 Bytes from AMMC 80 Kb 40 Kb 20 Kb Min, Avg & Max input delay 15 Seconds 5 Seconds

  21. RTH Melbourne – RTH Washington Text Link Monday Oct 08, 2007 Products from AMMC 150 100 50 # Products by size 150 100 50

  22. RTH Melbourne – RTH Washington Binary Link Monday Oct 08, 2007 Bytes from AMMC 15 Kb 5 Kb Min, Avg & Max input delay 15 Seconds 5 Seconds

  23. RTH Melbourne – RTH Washington Binary Link Monday Oct 08, 2007 Products from AMMC 20 10 5 # Products by size 20 10 5

  24. RTH Melbourne – RTH Washington Text Link Monday Oct 08, 2007 Transmission Delay Internal Delay Total Delay Avg Thruput to AMMC 250 Seconds 150 Seconds 50 Seconds

  25. RTH Melbourne – RTH Washington Text Link Monday Oct 08, 2007 Transmission Delay Internal Delay Total Delay Max Thruput to AMMC 400 Seconds (6.67 Min) 250 Seconds (4.167 Min) 100 Seconds 50 Seconds

  26. RTH Melbourne – RTH Washington Text Link Monday Oct 08, 2007 Bltns Thruput to AMMC 1600 Bltns 1000 Bltns 600 Bltns

  27. RTH Melbourne – RTH Washington Binary Link Monday Oct 08, 2007 Transmission Delay Internal Delay Total Delay Avg Thruput to AMMC 1600 Seconds (26.67 Min) 800 Seconds (13.33 Min) 200 Seconds (3.33 Min)

  28. RTH Melbourne – RTH Washington Binary Link Monday Oct 08, 2007 Transmission Delay Internal Delay Total Delay Max Thruput to AMMC 2000 Seconds (33.33 Min) 1500 Seconds (25 Min) 500 Seconds (8.33 Min)

  29. RTH Melbourne – RTH Washington Binary Link Monday Oct 08, 2007 Bltns Thruput to AMMC 3000 Bltns 2000 Bltns 500 Bltns

  30. RTH Melbourne – RTH Washington Binary Link Monday Oct 08, 2007 Bits/Sec Thruput to AMMC 120 Kbps 80 Kbps 20 Kbps

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

  32. CMC – RTH Washington Text Link Monday Oct 08, 2007 Bytes from CWTO 150 Kb 50 Kb Min, Avg & Max input delay 10 Seconds 10 Seconds 5 Seconds

  33. CMC – RTH Washington Text Link Monday Oct 08, 2007 Products from CWTO 800 200 # Products by size 800 200

  34. CMC – RTH Washington Binary Link Monday Oct 08, 2007 Bytes from CWTO 800 Kb 200 Kb Min, Avg & Max input delay 10 Seconds 5 Seconds

  35. CMC – RTH Washington Binary Link Monday Oct 08, 2007 Products from CWTO 400 100 # Products by size 400 100

  36. RTH Washington All products Monday Oct 08, 2007 Bytes to KWBC 800 Mb 400 Mb 200 Mb Min, Avg & Max input delay 150 Seconds 50 Seconds

  37. RTH Washington All products Monday Oct 08, 2007 Products to KWBC 40 K 10 K # Products by size 40 K 10 K

  38. RTH Washington All products Monday Oct 08, 2007 Transmission Delay Internal Delay Total Delay Avg Inter-System Thruput 160 Seconds 20 Seconds

  39. RTH Washington All products Monday Oct 08, 2007 Transmission Delay Internal Delay Total Delay Max Inter-System Thruput 800 Seconds (13.33 Min) 500 Seconds (8.33 Min) 100 Seconds

  40. RTH Washington All products Monday Oct 08, 2007 All Bltns Thruput 11,500 Bltns 9,500 Bltns 8,000 Bltns

  41. RTH Washington All products Monday Oct 08, 2007 Bits/Sec Thruput 1.8 Mbps 1.4 Mbps 800 Kbps 200 Kbps

  42. Issues • MTN Cloud 1 Expiry • Contract end - Dec 2007 • BT interested in 1 year extension • WMO coordination meeting November 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?

  43. 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)? • Washington GISC interaction with Asia & Euro GISCs? • Metadata catalogue coordination? • Communication requirements? • When to address this - next meeting?

  44. KWBC Operational Support KWBC Communication Control Center (CCC) - Tech Control Point of contact 24 hours every day Toc.Nwstg@noaa.gov Phone: +1 301 713-0902 Fax: +1 301 587-177 • Data Management Staff:Walter Smith - Team Lead, Data Management • walter.smith@noaa.gov +1 301 713-0864 ext 139 • Julie Hayes - Family of Services Manager julie.hayes@noaa.gov +1 301 713-0864 ext 120 • Richard Robinson - Data Manager • richard.robinson@noaa.gov +1 301 713-0864 ext 179 • Cynthia Cromwell – Data Manager • cynthia.cromwell@noaa.gov +1 301 713-0864 ext 143 • Fred Branski, Branch Chief – Ops Support, Perf Monitoring & Data Mgmt • fred.branski@noaa.gov +1 301 713-0864 ext 121

  45. Thank You! Additional Questions???

More Related