National Weather Service Telecommunication Gateway Legacy Systems Replacement WMO – ISS September 2002

Increasing Traffic Volumes NWP Improvements NEXRAD –Base Data –ORPG/ORDA NCEP currently produces more than 175 GB/day but is able to send less than 50 to the NWSTG

Architecture Changes Current Architecture –Mainframes –IBM VM/ESA Operating System –Message Switch Application, custom database –Specialized Front End Processors (Amdahl and Concurrent) New Architecture –Enterprise Servers –UNIX –COTS Messaging and Queuing middleware, COTS RDBMS, and C Language applications –General purpose servers

Expected Outcomes Meet NWSTG delivery performance requirements –10 second Message Switch transit for Watches and Warnings –Accommodate traffic increases, user increases, and protocol changes without major disruptions New technology (MQSeries) handles 90 million messages daily averaging 4 seconds transit in U.S. Customs system Retain current reliability and maintainability of facility and IT systems at 99.9% availability Reduce dependency on unique skills, software, and systems

NWSTG Data Flow Diagram

NWSTG Data Flow Highlights Data enters through Communication front ends and is placed on Messaging and Queuing (MQ) middleware for movement to Switch Engine Switch Engine: –Uses Switching Directory to determine distribution –Places message in Sybase RDBMS MQ Series Integrator (MQSI) and applications: –Parse messages and data elements –Perform QC –Build new messages and bulletins Data is delivered to users through communication links and servers

Switching System Replacement Data Flow

NWS Web & FTP Services Alaska Western Region Southern Region Central Region Eastern Region Headquarter Pacific Region Hurricane Center Severe Storm Center Aviation Wx Center