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 Fred Branski Office of the Chief Information Officer NOAA’s National Weather Service 8th APSDEU Meeting Oct 10-12, 2007

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

“Taking the pulse of the planet” NWSTG/RTH Functional 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 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

“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

“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

“Taking the pulse of the planet” 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)  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)

NWSTG NOAAnet Transition Current Customer Connectivity

NWSTG NOAAnet Transition No Direct Connect RTG Customers

NWSTG NOAAnet Transition End State for Customer Connectivity

“Taking the pulse of the planet” 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 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 February)  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/BTG Performance - RUC13 4.5Gb/day 67K products per day Avg Internal Delay: 1.31sec Avg Total Delay : 6.91sec

RTG/BTG Performance - RUC13 4.5Gb/day 67K products per day Avg Internal Delay: 1.31sec Avg Total Delay : 6.91sec

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Products from CWTO CMC – RTH Washington Text Link Monday Oct 08, # Products by size

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

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

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

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

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

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

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

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

“Taking the pulse of the planet” 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?  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?

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

“Taking the pulse of the planet” KWBC Operational Support KWBC Communication Control Center (CCC) - Tech Control Point of contact 24 hours every day Phone: Fax : Data Management Staff: Walter Smith - Team Lead, Data Management ext 139 Julie Hayes - Family of Services Manager ext 120 Richard Robinson - Data Manager ext 179 Cynthia Cromwell – Data Manager ext 143 Fred Branski, Branch Chief – Ops Support, Perf Monitoring & Data Mgmt ext 121

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