1 / 35

Emergency Data Distribution Network

Proposal to add an independent GOES DCS Reception and Distribution System to complement the NESDIS Wallops Island Facility Presented by Ernest Dreyer, USGS/WRD June 12, 2007. Emergency Data Distribution Network. Overview. Review EDDN project Provide a current status

vida
Download Presentation

Emergency Data Distribution Network

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. Proposal to add an independent GOES DCS Reception and Distribution System to complement the NESDIS Wallops Island Facility Presented by Ernest Dreyer, USGS/WRD June 12, 2007 Emergency Data Distribution Network

  2. Overview • Review EDDN project • Provide a current status • Describe backup capabilities • Review User access

  3. Review of EDDN Project

  4. EDDN Project GOALS • Receive data from all DCPs transmitting in the GOES DCS independently of Wallops Island. • Locate facility at a site sufficiently distant from Wallops Island to achieve event independence. • Implement additional pilot signal at a location other than Wallops Island. • Distribute data independently of Wallops Island.

  5. STIWG/NESDIS Proposal • Locate the emergency distribution system at the USGS EROS Data Center in Sioux Falls, South Dakota. • USGS and NOAA/NESDIS will share the costs for procurement of the Direct Readout Ground Station system. • System will be primarily operated by USGS with support from NESDIS. • Operational costs will be shared among users who agree to participate and NESDIS.

  6. Limitations • Contains no system to • Make new assignments • Data will be acquired from any transmitting DCP and so an internal schedule will not be necessary. • Generate abnormal platform response messages • Messages will not be checked for abnormal conditions – at least not initially.

  7. Limitations (cont.) • Distribution will initially be over the Internet using the DDS protocol. • No DOMSAT transmissions • No direct land-lines • Depends on the existence of a usable pilot signal.

  8. Basic EDDN System • DRGS system with 2 antennas for GOES East and West ( at least 7M ) • DOMSAT system for data from Wallops Island • LRGS systems for acquiring and distributing data. • Web Server for reporting system status.

  9. Some Features required of theEDDN GOES Receive System • Receive both 100 and 300 baud messages on the same channel. • Support a backup pilot signal and be able to switch to the backup if the primary signal fails.

  10. Diagram of Proposed System

  11. System Monitoring • Use Big Brother system monitoring • Write Big Brother clients for montioring • DRGSs via the DAMS NT event socket • LRGSs via system logs • Other events significant to the operations of system • Big Brother can • Display current status on web site • Send notifications to email groups • Page users

  12. System Control • After initial setup, system should operate with a minimum of operator intervention. • System will be remotely managed using a remote system console assisted by on-site support.

  13. Recurring Costs • EROS Support • Includes • 24/7 on-call network and emergency support • General SA support during regular hours. • SA will be familiar with DRGS systems and can assist in trouble shooting, making repairs, etc. • Does not include • Routine administration.

  14. Recurring Costs (cont.) • Maintenance • Optional maintenance support for the system after the warranty period. This includes • Yearly routine maintenance and inspection • On-call service.

  15. Current Status of EDDN

  16. Status of DRGS Procurement • RFP issued Early February • Site Visit at EROS February 17,2007 • Proposals Received Late March • Evaluations/Review Active • Contract Awarded June, 2007 • System Installed 6 months after award

  17. Status of LRGS Upgrades to support EDDN • LRGS Software • Work completed and ready for testing for the following enhancements: • DDS Security • DDS Configuration • DDS Backup Message Recovery • DDS Data filtering • New version is 6.0 and will be the base configuration used by EDDN

  18. Basic Backup Capabilities

  19. Some EDDN Features EDDN was designed with these principles • Would integrate easily into the current data distribution system. • Would be active all the time, not needing to be “turned on.” • Would provide a secondary source of data that could be used for data recovery for “problem” transmissions.

  20. Role of LRGS in GOES DCS

  21. EDDN and LRGS • EDDN takes advantage of the backup capabilities developed for Version 6.0 of the LRGS system • The LRGS is a store-and-forward system that can be configured with a • primary data feed and • one or more secondary feeds. • The LRGS can automatically use secondary feeds for backup and data recovery.

  22. EDDN and LRGS • Version 6.0 of the LRGS supports these backup/recovery/filtering scenarios: • Failure of primary data feed. • DDS • DOMSAT • DRGS ( DAMS-NT connection ) • Other • Missing messages. • Reception of “bad” message. • Messages with parity errors • Messages with missing EOT • Reception of duplicate messages.

  23. Examples that Illustrate Backup Scenarios

  24. LRGS BackupDOMSAT Only Primary LRGS with 1 Peer Backup

  25. LRGS BackupDOMSAT Only Primary LRGS with 2 Peer Backups

  26. LRGS BackupDOMSAT and DRGS LRGS with DOMSAT feed backed up by LRGS with DRGS feed

  27. LRGS BackupDRGS and DOMSAT LRGS with DRGS feed backed up by LRGS with DOMSAT feed

  28. Scenario for EDDN/LRGS BackupLRGS with Primary DOMSAT feed DOMSAT GOES East GOES West Wallops EROS EDDN Wallops LRGS EROS LRGS 1st Backup (DDS Feed) USER LRGS 2nd Backup?? (DDS Feed) DDS Client USER

  29. Scenario for EDDN/LRGS BackupLRGS with Primary DRGS feed DOMSAT GOES East GOES West Wallops EROS EDDN Wallops LRGS EROS LRGS 1st Backup (DDS Feed) USER LRGS 2nd Backup?? (DDS Feed) DDS Client USER

  30. Scenario for EDDN/LRGS BackupLRGS with Primary Network DDS feed DOMSAT GOES East GOES West EROS EDDN Wallops EROS LRGS Wallops LRGS 1st Backup (DDS Feed) USER LRGS Primary ( DDS Feed ) DDS Client USER

  31. EDDN and User Access

  32. EDDN and User Access • How will users get data from EDDN • Interactively • DDS client, either a GUI message broswer of command-line command • Real-time • Another LRGS using DDS connection • DDS command-line command in real-time script • Other DDS clients

  33. Some examples of available DDS clients Interactive • LRGS Message Browser • DDS command-line command (Both are included with basic LRGS packages and can also be acquired as stand-alone software) Real-time • Another LRGS using DDS connection to another system • DDS command-line command in real-time script • DECODES • USGS Satin • National Interagency Fire Center “ASCADS” Program

  34. EDDN and User Access • How will users keep their network up-to-data? • LRGSs in EDDN system will synchronize user information, including networks, from PDTS. • How will users monitor the operational status? • Big Brother Web display

  35. EDDN and User Access • What documentation will be available? • Setup guide that explains • Features • Hardware and software Requirements • Registration procedure • Connection options

More Related