RTH Washington

of 17

Please download to get full document.

View again

All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
PDF
17 pages
0 downs
4 views
Share
Description
RTH Washington. Fred Branski, Chief, Performance Monitoring, Support & Data Management Branch Office of the Chief Information Officer NOAA’s National Weather Service OPAG-ISS Meeting Sep 18-22, 2006. NWSTG/RTH Functions. The NWSTG is the central communication facility of the NWS;
Transcript
RTH Washington
  • Fred Branski, Chief, Performance Monitoring,
  • Support & Data Management Branch
  • Office of the Chief Information Officer
  • NOAA’s National Weather Service
  • OPAG-ISS Meeting
  • Sep 18-22, 2006
  • NWSTG/RTH Functions
  • The NWSTG 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.
  • NWSTG Functional OverviewThe 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
  • Data Input to the RTH
  • IP / Sockets / Frame Relay
  • X.25
  • Asynchronous
  • Dial up
  • FTP – http://weather.gov/tg/ftpingest.html
  • Email – http://weather.gov/tg/emailingest.html
  • Web - http://weather.gov/tg/bullguid.html
  • Major Initiatives
  • Replacement Telecommunications Gateway
  • Backup Telecommunications Gateway
  • NOAANet – National MPLS network
  • WIS development planning
  • Code migration
  • Improved Monitoring
  • RMTN upgrade
  • Replacement NWSTG (RTH)
  • 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
  • Hardware refresh
  • Replacement / BackupTG DescriptionNWS users
  • Nat’l Centers for Environ. Prediction
  • NWS Regional Offices
  • Domestic/int’l observation & forecast offices
  • AWIPS
  • Worldwide users
  • WMO/ICAO
  • Family of services
  • Govt. agencies
  • Internet users
  • Foreign countries
  • Emergency mgrs
  • NWS Telecom Gateway
  • Located in Silver Spring
  • New message switching syst.
  • allows future upgrades
  • x 2 upgradeability
  • Much improved response time
  • Redundancy ensures
  • uninterrupted service
  • Full configuration management
  • 120GB/461500 GB85GB/38250 GBGeographically separatedbackup system in northernVirginia90GB/46900 GB950GB/383500 GBDaily Throughput/# of circuitsLegacy over 5 year projection for replacementDaily total message flow:Legacy - 1.245TBRTG/BTG – 6.15TB (2011)Measurements/Projections based on May 2006 WMO message flowNOAANet BackboneSprint Peerless IP Network MapTacomaChicagoNew YorkCheyenneStocktonPennsauken, NJSan JoseRelay, MDKansas CityDCAnaheimAtlantaFortWorthOC48Internet Transport NodeStatus for RTG/BTG NOAANet Status
  • RTG IOC - June 19, 2006
  • RTG FOC – 3Q 2006
  • NOAANet OC-3 connection to BTG – June 2006
  • BTG IOC / OC-12 – 4Q 2006
  • All projects end – May 31, 2007
  • Status for RTG/BTG NOAANet Status
  • NOAANet Transition:
  • Internal underway, NWS regions, NCF, NESDIS soon
  • External – begin December 01, 2006
  • Initially two Access Points
  • One within the RTG facility but external to the infrastructure
  • One at Parsippany New York – GTS, AFTN / FAA / Hawaii / Micronesia, Others???
  • Possibly Atlanta, Chicago, Tacoma, ???
  • RTG Performance Measures:Requirement FOC Actual Variance Threshold FY06 FY06 FY07Message (Watch&Warning)Avg. Transit Time (seconds) 10 6 0 0Message (Routine&Model)Avg. Transit Time (seconds) 60 7 -53 0Avg. Message Traffic (send/receive) (daily) 1.2TB 1.2 TB 0 0 For Watches and Warnings:
  • Avg time (seconds) to queue to outbound FEP: 6.16
  • Max time (seconds) to queue to outbound FEP: 182 (3.03 minutes)
  • Avg time (seconds) to send from outbound FEP: 37.77
  • Max time (seconds) to send from outbound FEP: 3838 (63.96 minutes
  • Note: Not all connections are moved to the RTG infrastructure. Those still moving through legacy systems have the longest delays. We still see occasional spikes in the RTG processing stream which we are investigating with IBM to determine the cause and resolve. For all other data (except Watches and Warnings):
  • Avg time (seconds) to queue to outbound FEP: 6.97
  • Max time (seconds) to queue to outbound FEP: 236 (3.93 minutes)
  • Avg time (seconds) to send from outbound FEP: 17.13
  • Max time (seconds) to send from outbound FEP: 4039 (67.32 minutes)
  • Note: Not all connections are moved to the RTG infrastructure. Those still moving through legacy systems have the longest delays. We still see occasional spikes in the RTG processing stream which we are investigating with IBM to determine the cause and resolve. For Model data:
  • Avg time (seconds) to queue to outbound FEP: 10.25
  • Max time (seconds) to queue to outbound FEP: 189 (3.15 minutes)
  • Avg time (seconds) to send from outbound FEP: 62.71
  • Max time (seconds) to send from outbound FEP: 1910 (31.83 minutes)
  • Note: Not all connections are moved to the RTG infrastructure. Those still moving through legacy systems have the longest delays. We still see occasional spikes in the RTG processing stream which we are investigating with IBM to determine the cause and resolve. Major Initiatives
  • WIS development planning
  • TOC undertaking planning of VGISC development and US WIS plan
  • Basis provide by RTH upgrade and MPLS rollout
  • Will coordinate with Region IV to develop regional plan
  • Code migration
  • Workstations throughout the regional capable of processing TDCF
  • Capability for Upper Air translation exists within RTH.
  • Extension of translation capability will be main enabling method outside of native processing
  • Improved Monitoring
  • New initiative to be further developed within the RTH and Region.
  • Part of Phase two of RTH upgrade.
  • Major Initiatives
  • RMTN upgrade
  • ISCS follow on planning beginning
  • EMWIN expansion
  • Third Border Initiative funding two pilot projects
  • Plan to implement 10 to 15 additional EMWIN site within Region IV - Caribbean, Central American area
  • Enhanced extra regional connections
  • Region III
  • Russia
  • Major Concern
  • Existing GTS Frame relay contract ends Dec 2007
  • BT may be willing to extend for 1 year
  • What will be its replacement ???MPLS ???
    Related Search
    We Need Your Support
    Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

    Thanks to everyone for your continued support.

    No, Thanks