# Presentation: 340037

## Emergency Data Distribution Network

**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**

## Overview

- Review EDDN project
- Provide a current status
- Describe backup capabilities
- Review User access

## Review of EDDN Project

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

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

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

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

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

## Some Features required of theEDDN 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.

## Diagram of Proposed System

## 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

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

## System Support

- Initial Capital Investment
- USGS/NESDIS
- Operations and Maintenance Costs
- Work out a fair system for each agency that uses the system
- Likely an assessment similar to DOMSAT

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

## Recurring Costs (cont.)

- Maintenance
- Optional maintenance support for the system after the warranty period.  This includes
- Yearly routine maintenance and inspection
- On-call service.

## Current Status of EDDN

## 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

## 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

## Basic Backup Capabilities

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

## Role of LRGS in GOES DCS

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

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

## Examples that Illustrate Backup Scenarios

## LRGS BackupDOMSAT Only

- Primary LRGS with 1 Peer Backup

## LRGS BackupDOMSAT Only

- Primary LRGS with 2 Peer Backups

## LRGS BackupDOMSAT and DRGS

- LRGS with DOMSAT feed backed up by LRGS with DRGS feed

## LRGS BackupDRGS and DOMSAT 

- LRGS with DRGS feed backed up by LRGS with DOMSAT feed

## Scenario for EDDN/LRGS BackupLRGS with Primary DOMSAT feed

- GOES West

- GOES East

- DOMSAT

- EROS LRGS

- USER LRGS

- Wallops LRGS

- 1st Backup
- (DDS Feed)

- 2nd Backup??
- (DDS Feed)

- USER

- DDS Client

- EROS EDDN

- Wallops

**Notes:**
DDS

## Scenario for EDDN/LRGS BackupLRGS with Primary DRGS feed

- GOES West

- GOES East

- DOMSAT

- EROS LRGS

- USER LRGS

- Wallops LRGS

- 1st Backup
- (DDS Feed)

- 2nd Backup??
- (DDS Feed)

- USER

- DDS Client

- EROS EDDN

- Wallops

**Notes:**
DDS

## Scenario for EDDN/LRGS BackupLRGS with Primary Network DDS feed

- GOES West

- GOES East

- DOMSAT

- EROS LRGS

- USER LRGS

- Wallops LRGS

- 1st Backup
- (DDS Feed)

- Primary
- ( DDS Feed )

- USER

- DDS Client

- EROS EDDN

- Wallops

**Notes:**
DDS

## EDDN and User Access

## 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

## 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

## 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

## EDDN and User Access

- What documentation will be available?
- Setup guide that explains
- Features
- Hardware and software Requirements
- Registration procedure
- Connection options