GOES Data Collection System Status of Version II Transmitter Implementation Information Brief for TWG Kay Metcalf NOAA GOES DCS Program Manager May 12, 2011
May 2011NOAA GOES DCS2 Goal of Version 2 Transmitters Decrease Width of Each Channel –From 1.5 kHz to.75 kHz for 300 baud –From 3.0 kHz to 2.25 kHz for 1200 baud Double Number of Channels Available –From approximately 100 channels per satellite to approximately 200 channels per satellite Increase System Capacity
Nov-2010NOAA GOES DCS3 Loading Capacity Version 1.0 Loading Capacity –Standard Reporting Mode Once per hour, for 10 seconds Allows for 36,000 transmitters for 100 channel spacecraft Only alternate channels used on each spacecraft –Wide beam causes most transmitters to hit both spacecraft 2 satellites allow for 72,000 transmitters –Varying any Parameter Changes Capacity Repeat Cycle of Transmissions Length of Message Allow 15 minute repeat cycle (most users requesting) –18,000 current version fit into system on both satellites –We’ve already exceeded that with the current system Version 2.0 Loading Capacity –Narrow band transmitters allow for 144,000 using standard mode 15 minute repeat cycle allows 36,000 transmitters on both satellites Users with most requirements are oceanographic users, including tsunami warning Most require 5 or 6 minute repeat cycles These requirements even further diminish capacity Requirements are stringently vetted to conserve resources –Most users still constrained to hourly reporting –NOS and the Tsunami Warning Community are the exceptions
Nov-2010NOAA GOES DCS4 Capacity Drivers Known Requirements –NOS already using 6 minute reporting for tide gauges and tsunamis –Tsunami Users around the hemisphere requesting 5 minute assignments –USGS indicates plans to add 10,000 ground well monitoring systems Reporting hourly at NWS request –Historical Climate Network needs 1000 stations Approximately 500 already assigned –National Fire Danger Rating Network Mandated Use of GOES DCS Goal of 15 minute reporting –World Bank Recommends use of GOES DCS for Emergency Warning Data in Latin America (a Quickly Growing Segment) In 2003 system had 9,000 transmitters, 150 users, 100,000 messages Current use 30,000 transmitters, 400 users, 600,000 messages –More than 300% increase from 2003 usage More users, more stations, more frequent observations and more sensors are anticipated in the future based on current growth rate/demand –These factors point to the future need for additional network capacity to sustain a reliable service for DCS users
Nov-2010NOAA GOES DCS5 V.2 Status Certification Standards completed and published Certification test sets completed New filter Defined Ground System Software changes made Version II Test Channel Loaded with New Software New Channel Structure Defined Three manufacturers certified at V.2 One user already has assignments on 2 channels set as v.2 Configuration switch settable by channel or for entire system –All channels will be v.1 and v.2 compatible when configured
May 2011NOAA GOES DCS6
Technical Points All Center Frequencies of Existing Channels Unchanged No existing Transmitters will have to be reprogrammed until channel clearing begins V.1 and V.2 transmitters can coexist on same channels No New assignments needed to replace Existing V.1 transmitter with new V.2 Transmitter Nov-2010NOAA GOES DCS7
Nov-2010NOAA GOES DCS8 Ground System Requirements Short Term Software changes to demodulators done –Redefined Frame Sync Sequence in software –Implemented new firmware on DAMS-NT demodulators Long Term Software Changes to Demodulators –Implement SRRC filter Analysis shows minimal loss by not implementing Will implement as resources become available Short Term DADDS changes done –Flexible channelization (channel structure) Will Investigate additional processing capability for future refresh New Channels Phased In over several years
Nov-2010NOAA GOES DCS9 How Do We Proceed? Run Operational Demonstrations on V.2 Test Channels: done Successful Demonstration Leads to Loading Software Changes on all Channels: done (demods now configurable) Continue Certifying New Equipment: ongoing Work with Manufacturers to assure commercial DRG Systems Version II compatible: ? No known issues Work with users to identify channels in existing system that are eligible for V.2 implementation because DRGS is capable of handling new data stream (or no DRGS in use): No known issues Allow new transmitters to start populating system on existing channels Once population is sufficient begin new channel alignment as channels become available for transition
Nov-2010NOAA GOES DCS10 Programmatic Discussion Points When do we stop allowing new V.1 assignments? When do Manufacturers stop distributing V.1 equipment? When do we Require All v.1 equipment to be removed from System (or upgraded)? How do software upgrades to existing systems get distributed?
Nov-2010NOAA GOES DCS11 Transition Approach Use Existing Channels “as is” –Field V.2 Transmitters onto same channels as V.1 channels New and old transmitters compatible with NOAA demodulators –(Other DRGS manufacturers?) –Allow Population of V.2 transmitters to grow with no additional changes –When population on 2 adjacent channels approaches x % (60%?) begin clearing channels to allow intermediate channel to be implemented Expected to be 3 or 4 years from start date
Nov-2010NOAA GOES DCS12 GOES DCS Contact Information Kay Metcalf –GOES DCS Program Manager – Letecia Reeves –GOES DCS Customer Service Representative – URL –