E/SP3: JW December 27, 2005

MEMMORANDUM FOR: GOES Data Collection System (DCS) Users

FROM: Kay Metcalf GOES DCS Program Manager

SUBJECT: Minutes of the 104^th^ GOES DCS Technical Working

Group Meeting, November 9, 2005.

**[I. Opening Remarks -- Kay Metcalf, DCS Program Manager
(NESDIS/DSD).]{.underline}**

Kay opened the 104^th^ meeting of the DCS Technical Working Group with a
welcome to all and made mention of the large turnout for the Baltimore
meeting. She next introduced the NOAA support people: Letecia Reeves, Al
Mcmath, Phil Whaley, herself, and Jim Wydick. The TWG agenda was
reviewed and accepted as is. The current STIWG Chairman, Stan Brua of
the Army Corps of Engineers was introduced to the audience.

**[II. Satellite Telemetry Interagency Working Group (STIWG) Report --
Stan Brua (USACE).]{.underline}**

Stan Brua next presented the report for the previous days STIWG Meeting.
Charles Kazamir will be the 2006 STIWG Chairman. DOMSAT funding is in
place through September 2008, and the OFCM has paid the current DAMSAT
bills. He previewed the Emergency Data Distribution Network (EDDN)
development with further details following. He introduced Mark Bushnell
as the contact person that is leading the DCPI effort that will result
in new standards to ensure the continuity of the availability of the
DCPI/RF band. He mentioned that the STIWG is concerned that NESDIS has
no formal mandates covering the DCS service. Therefore the STIWG is to
elevate their concerns to the parent committee, the Subcommittee on
Hydrology. He came back to the EDDN and introduced Ernest Dreyer of the
USGS who gave an historical review of the backup project. Ernest
explained how Charles Kazamir of the BLM Fire Center had an idea for
networking existing DCS DRGS units to serve as an emergency backup to
the Wallops CDA since a backup system did not exist. Also the results of
NOAA's backup study resulted in a very costly system concept and a
location that was considered to close to the existing Wallops site.
Additionally, it called for only Wallops personnel to man the backup
site. The USGS decided to purchase some DRGS units to provide emergency
data processing at the Sioux Falls EROS Data Center. The USGS then
talked to NOAA who decided to work with the USGS to implement a basic
emergency backup site at Sioux Falls. A NOAA criterion for support is
that data are to be made available to other DCS users. An EDDN proposal
was being generated and is almost complete. Off the shelf (COTS)
components will be used with the DRGS standard of DDS. The initial
system is to be just what is needed to receive and distribute DCS data
but it will permit future expansion and development Stan Brua referenced
Rich Engstoms system in Rock Island that is a currently running system
much like what is proposed for the EDDN.

.

Mark Bushnell next presented a review of how the DCPI system band was
intended to function along with the inherent system limits. The NTIA
limitations that are placed on the DCS were also briefly mentioned and
how these limitations restrain the system somewhat. There are plans to
write a proposal for a Small Business Innovative Research (SBIR) grant
for DCPI development. It is hoped that up to \$75,000 could be awarded
for a Phase 1 initial study followed by \$300,000 that would support the
Phase 2 development of prototype hardware. The SBIR proposals are due in
early 2006 with the awards to follow in June. The Phase 1 study is
expected to last for 6 months. There were plans for a DCPI
teleconference that would be scheduled for the following week with many
DCS users planning to participate. Paul Tippett was to contact
additional users to get everyone involved.

Larry Cedrone's SHEF Code work was reference from yesterday's meeting. A
wealth of SHEF Code information can be found at
[Weather.gov/os/whfs/shef.shtml]{.underline}.

The STIWG plans to have the next meeting in the spring in Ashville, NC
or Sioux Falls, SD to be followed by one in the fall.

**[III. NESDIS Management Report- Kay Metcalf, DCS Program Manager
(NESDIS/DSD).]{.underline}**

It was reported that NESDIS has been concentrating on the Emergency Data
Distribution Network (EDDN), High Data Rate (HDR) assignments and the
DCP filter study with narrower band transmission characteristics. Kay
introduced Letecia Reeves who was to present a report on the status of
the HDR transition.

**[High Date Rate Transition-Letecia Reeves (NESDIS/DSD)]{.underline}**

It was reported that currently there were 41 High Data Rate (HDR)
operational channels in the DCS. There are 7422 of the HDR DCPs are
operating at 300 bps. It was also reported that some of the recently
purchased HDR demodulators have had to be used as 100 bps demod
replacements. Some of the 300 bps channel demods have been placed
adjacent to 100bps demods but without any interference yet. Kay
explained the rational for doing this in spite of the appearance of
violating transition plan guidelines. Kay reported that all affected
users were notified of the configuration changes. There was some user
anxiety that was expressed about using 300 bps demods next to the 100
bps units. There was also mention of using mixed mode 100bps message
traffic on the same channel as 100 bps traffic. Kay said that she is
using 5 and 10 second windows, and is recommending pseudo binary code as
a type of data compression to save DCS resources. Users should update
the PDTs and were reminded of the latency that exists in the way DAPS
processes message data so they need to allow some time margin within the
message window. Some users mentioned that the latency seemed to be about
2 to 3 seconds. A general discussion focused on the use of 5 second
windows. A vendor recommendation was made to make the standard message
time reference be the time that the message arrives at the satellite.
This presentation is included with the minutes.

**[IV. NESDIS Wallops/CDA Report -- Al Mcmath
(NESDIS/OSO)]{.underline}**

It was reported that LRIT transmission of DCS data is now 100% on both
GOES East and GOES West. This provides possible data reception for those
outside of the DOMSAT footprint. Additionally, Wallops has increased the
reliability of the broadband communications connection between the CDA
and Suitland. All of the DCS data are in the LRIT data stream now.
However, the system is in it early operational stages and lessons are
still being learned. The LRIT system latency has not yet been determined
precisely.

A DCS risk assessment has been completed at the CDA and the plan was
approved in August 2005. Telnet users present problems for the Wallops
DCS firewall because passwords have to go through the DAPS firewall. The
CDA DCS personnel have accepted the fact that the current DAPS will be
here for awhile longer so they are trying to fortify the system. They
also will be testing DCS channel interference and monitoring system that
uses a spectrum analyzer. It was reported that a Booz Allen penetration
test at the CDA was successfully completed.

Wallops is preparing for the addition of a 3^rd^ operational spacecraft.
This is to satisfy South American users who lost some data during their
recent hurricane season. It is expected to have GOES 10 as a central
spacecraft and GOES 11 and 12 for normal U.S. operations. However, when
GOES N is launched, it will present the CDA with some antenna
challenges. There is the upcoming NSOF move that will require movement
of communication lines and presenting significant logistical challenges.
A new backup building is to be constructed at the Wallops CDA for
satellite products such as WEFAX. There have been some Telnet problems
recently along with a firewall failure where there was no backup for the
firewall. This resulted in user log-in problems.

There was a vendor question about any backup pilot tone. It was reported
that the Wallops CDA used a signal generator at the Goddard Spaceflight
Center backup site to demonstrate the concept and the setup worked from
there.

There was a major GOES failure on October 31 due to a faulty power
supply but that only affected imagery data and not DCS service. Al also
clarified the COOP emergency drill misunderstandings that resulted from
the last TWG. Due to the hurricanes this fall, the COOP drill has been
postponed until some later date.

Phil Whaley of the Wallops CDA next gave a brief review of the GOES
spacecraft control backup mechanisms that involve both NOAA and NASA
supporting elements.

**[V. DCS Ecuadorian Channel Interference- Lawrence Crippen/Sandra
Wright (Joint Spectrum Center).]{.underline}**

Larry Crippen presented presentation that summarized the work that was
done in tracing down the DCS channel interference that has plagued the
system for so long. The Joint Spectrum Center started by going to the
Wallops CDA and analyzing channel data to determine just what channels
had interference. In the midst of their investigation they had to
temporarily stop in order to trace down the source of a new GVAR
interferer. They were able to get back to the DCS study during the
summer 2005. They found that DCS channel 266 had a constant interference
signal and that some signals were only 1 Hz wide. They also examined
possible satellite generated RFI. They examined a host of possible
sources of interference such as wind profilers and other terrestrial
sources. They were able to locate a problem transmitter within 150 feet
that was interfering with channel 266.

The Joint Spectrum Center organized a team to go to Ecuador to search
for interference sources that their sensors had identified. The
interfering RF transmitters all seemed to be located near volcanoes. As
it turned out the Ecuadorians have had seismic monitoring transmitters
there for over 25 years monitoring volcanic activity. The transmitters
were only ½ watt power and were the same type as those used by Americans
to monitor Mt. Saint Helens. The Ecuadorians have 71 volcanoes of which
to be aware with some being active and others that are dormant. There
were instances of transmitters that were very difficult to find. The
Ecuadorian government had allocated RF frequencies in a band from 401 to
402 MHz for seismic monitoring. The approach used by Larry Crippen was
to repair a number of defective Ecuadorian transmitters and to set the
frequencies outside the limits of the DCS band. The Ecuadorian
technicians do not think that they can get their data in a timely manner
if they were to use the GOES DCS; therefore they want to continue using
their local system. It was noted that they have very poor Internet
reliability. It also was mentioned that there is the possibility that
the United States will give Ecuador a DRGS facility that would allow
them to migrate to the GOES DCS. This presentation is included with the
minutes.

**[VI. DCS NTIA Matters - Paul Tippet (DOI/USGS/WRD)]{.underline}**

The URL for reaching the NTIA via the Internet was given as:
[www.ntia.doc.gov/osmhome/redbook/redbook.html](http://www.ntia.doc.gov/osmhome/redbook/redbook.html)
. It was reported that most agencies seem to have a frequency manager to
promote the orderly use of their RF bands and that problems should be
reported promptly to that person. Paragraph 8.2.30 of the above document
deals exclusively with interference. Two actions were then recommended:

1\. Report problems or incidences to the agency frequency manager.

2\. And next to report the incident further up the command chain if
necessary to get action.

**[VI. DCS Tsunami Monitoring - Bernard Kilonsky (University of
Hawaii)]{.underline}\
**A presentation was made describing a Tsunami warning project that
utilizes the GOES DCS. In monitoring the Indian Ocean for tsunami
events, on-site personnel as well as automated systems are employed. A
description of the monitoring system components was presented in which a
network of GOES DCS DCP type stations is configured for monitoring any
tsunami activity. Utilization is also made of the GLOSS Program (Global
Sea Level Observing System) for which the URL is
<http://www.pol.ac.uk/psmsl/programmes/gloss.info.html> . The ASCII
format is used along with the GTS for retransmission. Dramatic photos of
an actual tsunami event near Sri Lanka were presented. A graph of a
tsunami event was shown as a function of time showing the first evidence
of the tsunami onset. IOC funding is expected to be forthcoming for
future support of the monitoring activities and NOAA will be funding
some of the gauges. It was mentioned that they would like to have GOES 9
with the international channels to complete the area coverage. The
potential availability of GOES international channels for the network
was the prime reason for today's presentation. (Wallops reported that
the Fairbanks site would only need to have some DCS demodulators in
order to receive that data.) They are employing buoys that have very
sensitive acoustic sensors for detecting tsunamis. Their prediction
models performed well in forecasting the warning area when they had
sufficient source data.

**[VII. User Report Highlights]{.underline}**

**Mark Bushnell** of the NOAA/NOS reported on monitoring tides and
currents. There are 35 tsunami sites deployed and operational. There are
also 37 hydrological stations in operation and a quick response buoy was
recently deployed.

**Ernest Dreyer** of the USGS reported that the USGS has over 8000 DCPs
in the U.S. and that 30% are HDR now. He requested that a review of the
HDR transition plan be included in the TWG agenda. The USGS systems are
distributed throughout the U.S. Menlo Park, CA and Reston, VA are the
two central sites that serve as backup systems. Katrina served as a good
test for the two sites and Reston performed as expected.

**Tom Ley** of the Colorado Division of Water Resources reported that
they have a network of 720 gauging station but that they also use USGS
data. About 2/3 of the stations are HDR now and they plan to convert 50
more per year until all are HDR. He reported that they are pleased with
the DCS HDR service. Their Alert System provides warning to emergency
managers of an impending event.

**Paul-Emile Bergeran** of Environment Canada reported that they now
have 788 stations, with 146 of them HDR. They emphasize water level
measurements. He expressed the need for a standard protocol between the
DCP transmitter and the data logger.

**Charles Kazimir** of the NIFC/BLM reported on 450 weather stations
that primarily provide fire weather services. Overall, 1850 stations are
maintained for other agencies as well. They have some DCP firmware
problems that are being corrected. Their DRBS has been working well over
the past few months.

**Kolleen Shelly** of the Forest Service reported that her office is in
the middle of an efficiency study. The fire in paradise program is in
its 2^nd^ year. She reported that one 10 watt system had been installed
in Guam and 3 stations in Puerto Rico along with one on Saint Croix.

**Pete Lessing** of the NDBC reported on the maintenance of 145 stations
in their marine assets which includes 95 Buoys. They also are involved
with tsunami support. They are currently testing an HDR transmitter for
buoys and will be trying it operationally in the spring. They are
working with the NOS for buoy conversion. As an aside, he reported that
Cuban immigrants had been living on one of their buoys.

**Debra Braun** represented the Climate Reference Network/NCDC in
Ashville, NC. There are now 80 stations out of total 120 planned. The
purpose is to describe weather variability and will employ redundant
DCPs. There will be an emphasis on temperature and precipitation
measurements.

**Stan Brua** of the Baltimore District of the Army Corps of Engineers
(ACE) reported that management oversight responsibility will be rotating
every 2 years. Stan is overseeing about 3000 DCS sites currently of
which 15% are HDR. They have had problems with DCP timing errors. He
reported that the DCPs seemed to be reporting in the middle of the
window but errors were still occurring. The messages were 1.5 seconds in
length within a 5 second window message from stations that had
previously been working fine. The possibility of the leap second GPS
issue was thought to be a strong possibility. Otherwise the various
districts are converting to HDR at different rates. There are 85 DCPs in
the Baltimore District of which 10 are HDR.

**Mike Barfield** of the Saint Louis District/ACE reported on 10 major
projects involving levees and dams. They use a DRGS that is being
up-graded and they also have an LRGS. There were no major problems to
report. There are 17 HDR DCPs in the field and expect to have 25% of
their DCPs HDR by January 2006 and they are switching out the 100 bps
DCPs in block batches.

**Jim Heil** of the NWS reported that he is working on GOES-R
requirements. The NWS currently has about 400 DCPs and have plans to
grow significantly in the future. They are working to phase out the 100
bps units.

**Larry Cedrone** of the NWS/OHD Introduced Brian Jackson also of the
NWG/OHD who is responsible for the Hydrometeorological Automated Data
System (HADS) software. The HADS program brings in DCS data and puts it
into a standard format for NWS usage. It was mentioned that multiple
agencies and programs use the HADS data. Larry and Ernest Dreyer of the
USGS have developed a system on the HADS site that links to the USGS
site for data sharing. It was reported that the NWS Central Region has
30 platforms for the Great Lakes Observing System (GLOS) for
meteorological data.

Kay next mentioned that some of the 100 bps channels are becoming
sparsely populated. She said that she would like to compress them by
moving users into these channels.

**[Next Meeting]{.underline}**

The next meeting is to coincide with the next STIWG that is to be a West
meeting with Sioux Falls, SD being a strong possibility.