Post on 27-Dec-2015
11
GOES-R User Requirements Change Process
Barbara PfarrBill Mazur
Monica Todirita
GOES-R Program Systems Engineering
2
GOES-R Requirements Evolution
Key Decision Points (KDP): Launch Readiness
1999 2005 2007 2014
REQUIREMENTS
B C/D
System Architecture Government and Industry Studies Phase
Program Definition &
Risk Reduction (PDRR) Phase
Acquisition and Operations (A&O) Phase
2008
NWS ORD1999
GUCMay 2001
GUCOct 2002
GUCMay 2004
GUCMay 2006
GUCJan 2008
MRD 2’2005
MRD 32007
LIRD 2007
RequirementsDocuments
GOES Users Conferences
GPRD2004
CORL
MCP2007
NASA/MOU
7120.5D
Project Plans
Level I
Level II
Level IIa
Level III / Level IIIa
Project Interface Documents & Specifications
Update TBD
UpdateTBD
ACRONYMS
CORL Consolidated Observational Requirements List MOU Memorandum of Understanding
GPRD GOES Program Requirements Document MRD Mission Requirements Document
GUC GOES Users Conference ORD Operational Requirements Document
LIRD Level I Requirements Document NWS National Weather Service
MRD 12003
3
NWS Operational Requirements Document (ORD) circa. 1999
• Top Priorities Operation of sensors through eclipse and “keep-out-zones.” Resolution of imaging conflict among climatic, synoptic,
and mesoscale requirements. Improved time and space resolution for the imager sensor.
X Improved spatial coverage of the sounder sensor.
4
Oth
er U
sers
National Weather Service (NWS)
Oceanic & Atmospheric Research (OAR)
National Ocean Service (NOS)
National Marine Fisheries Service (NMFS)
NOAA Marine & Aviation Operations (NMAO)
Program Planning & Integration (PPI)
NOAA Users
National Environmental Satellite, Data & Information Service (NESDIS)
Eco
syst
ems,
Wea
ther
& W
ater
, C
lim
ate,
C
om
mer
ce &
Tra
nsp
ort
atio
n
L1RD
Aerosols
PrecipitationAtmospheri
c Profiles
Ocean
Space & Solar
Clouds
Land
Requirements
Atmospheric RadianceAtmospheri
c Winds
Coastal Waters & Estuaries
Mapping Requirements To GOES-R Approved System Solutions
Spacecraft
Up
com
ing
P
rocu
re-m
ents
Instru
men
ts
Ground Segment
MRD
MRD
Instruments
Advanced Baseline Imager
(ABI)
EUVS / XRS Irradiance Sensor
(EXIS)
Solar Ultra Violet Imager (SUVI)
Space Environment In-
Situ Suite (SEISS)
Geostationary Lightning Mapper
(GLM)
5
GOES-R Requirements Process During Acquisition and
Operations
• Stability and clarity of requirements critical to successful implementation;
• As costs and implementation difficulties become apparent requirement updates may be necessary;
• Challenges for the Acquisition & Operations Phase:
– As products and services become available to the current series, these “Legacy” products must be integrated into the to-be-delivered GOES-R system.
– As technologies mature and funding is made available, additional new products and services may be added.
– As National priorities change, requirements will be reviewed and updated.
6
GOES-R Requirements Documents Hierarchy
Requirement Level
Baseline DocumentDocument Custodian
& Control ProcessReviewing Body Approving Body
NOAA Observing Systems
Architecture (NOSA)
Consolidated Observational
Requirements List (CORL)
NOAA Observing Systems Council (NOSC)
NOAA Observing
Systems Council (NOSC)
NOAA Executive Council (NEC)
Level IGOES-R Level I
Requirements DocumentsGOES-R Program Office
(GPO)
NOSC,NOAA PMC,
NESDIS AA/DAANOAA DUS
Level IIGOES-R
Management Control Plan
GPONESDIS AA/DAANASA/GSFC PMC
NESDIS AA, NASA/GSFC Center Director
Level IIaMission Requirements
DocumentGPO
GOES-R Operational
Requirements
Working Group (GORWG)
GPO
GOES-R SPD
Level IIIGOES-R
Project Plans GOES-R Projects GPO GOES-R SPD
Level IIIaProject Level Interface
Documents and Functional Specifications
GOES-R Projects GPO GOES-R Project Managers
7
User Request forChange Process
User Request
CORL
Implement Request
Non- Level 1 and funding available
Level 1 and / or funding required
CORL Consolidated Observational Requirements List
ECRB Engineering Change Review Board
GORWG GOES-R Operational Requirements Working Group
GPO GOES-R Program Office
PMC Program Management Council
TAP Technical Advisory Panel
GORWGReview / Analysis ECRB
Review(GPO)
Scientific Analysis(TAP)
CCBDisposition /
Approval (GPO)
PMCApproval
Validation
8
Example of a User Requirements Change Currently Under
Consideration
Desired Growth in the capacity for the EMWIN and LRIT Communication Services
The Government's firm requirement will be defined in the draft solicitation
and subsequent final solicitation
9
Command and Data Acquisition StationWallops, VA
NOAASatellite Operations Facility
Suitland, MD(LRIT Source)
EMWIN CC Silver Spring, MD(EMWIN Source)
GOES NOP SeriesGOES-R Series
Combination of Emergency Managers Weather Information Network (EMWIN) and Low Rate Information Transmission (LRIT) Services
Combination of Emergency Managers Weather Information Network (EMWIN) and Low Rate Information Transmission (LRIT) Services
Separate EMWIN/LRITCombined EMWIN/LRIT
EMWIN User
EMWINUser
LRIT User
LRIT User
The Government's firm requirement will be defined in the draft solicitation
and subsequent final solicitation
10
EMWIN and LRIT Characteristics
• Currently the two services have separate broadcasts through each GOES satellite (East and West):– EMWIN:
• 9.6Kbps FM signal, 1690.725 MHz (GOES I-M series)• 19.2 Kbps OQPSK CCSDS packetized signal, 1692.7 MHz (GOES
NOP series)• Users utilize ~1 meter antenna
– LRIT:• 128 Kbps BPSK CCSDS packetized signal, 1691.0 MHz • Users utilize ~1.2 meter antenna
• Both User communities desire greater capacity for more products
The Government's firm requirement will be defined in the draft solicitation
and subsequent final solicitation
11
EMWIN and LRIT Concerns and Proposed Solution
• Concern about impact to cost, complexity and transition difficulties to higher data rate service
– Bandwidth available for the entire GOES-R communications requirement is limited
– Impact to Users terminals-- particularly for EMWIN• Must be very portable• Users have limited budget/resources
• Candidate GOES-R solution:– EMWIN and LRIT combined with a data rate greater than both
current services– Design the satellite to transmit sufficient power that Users can still
utilize ~1 meter antennas – Separate Virtual channels for each service--allow users to receive
the content of either or both services– With software-based receiver technology, user terminals can be
designed to receive all past and future formats with no hardware changes
LRIT I, LRIT N
EMWIN I EMWIN N
EMWIN IEMWIN NLRIT I/NEMWIN/LRIT
The Government's firm requirement will be defined in the draft solicitation
and subsequent final solicitation
12
PROs and CONs
• BENEFITS:– Allows desired increase in throughput capacity for both services.– Allows commonality of user receive systems.– Reduces cost/complexity of Spacecraft.– Both Services retain the ability to use the same relatively small antennas with the
new higher data rate.– Reduces spectrum requirements:
• Added benefit--allows critical S/C telemetry signal to be included in the GOES frequency band.
• CHALLENGES:– Another change for the current users. However:
• New frequencies are necessary, but the GRB broadcast requirement (31 Mbps) forces a reallocation of the L-band frequencies anyway.
• New data rates are required to satisfy User-stated growth needs.
– Transition Concerns between legacy GOES and GOES-R
The Government's firm requirement will be defined in the draft solicitation
and subsequent final solicitation
13
User Concern Mitigation:Prototyping the
solution• The GOES-R Program plans to demonstrate a prototype very low cost
EMWIN/LRIT receiver based on “Software Defined Radio” techniques which will:– Receive both services in any GOES I-M, N-P or –R+ frequencies, data rates and
modulation types.– Receiver signal processing to be performed by a simple USB interface board in
conjunction with a standard PC. Design for a prototype interface to be provided to the User community
– Utilize GOES-R developed software--source code which would be available to the User communities.
– Anticipate demonstration of a prototype in mid-2008.
Ettus Universal Software Radio Peripheral (USRP)early prototype
clock
A/D chip
USB connectorEthernet
USB chip
FPGA
The Government's firm requirement will be defined in the draft solicitation
and subsequent final solicitation
14
Impacts to Requirements Documentation
• The proposed solution still supports the EMWIN and LRIT services.– Therefore the Level 1 Requirements are unaffected
• The MRD defines the unique properties of EMWIN and LRIT through unique Spacecraft-to-Ground Interface Requirements Documents (IRDs).– Existing separate IRDs for EMWIN and LRIT (417-R-IRD-0004 &
417-R-IRD-0003) to be merged– A new IRD, for the combined service, is being created and will be
referenced for both service requirements
• No cost impacts are required for implementation. – Savings on the satellite communication system will fund the
development of the demonstration prototype.The Government's firm requirement will be defined in the draft solicitation
and subsequent final solicitation
15
Impacts to Requirements Documentation (cont.)
EMWINMRD Req ID 463
EMWINMRD Req ID 463
LRITMRD Req ID 467
LRITMRD Req ID 467
Flight Project F&PS IDs
XXX
Flight Project F&PS IDs
XXX
Ground Project F&PS
IDs XXX
Ground Project F&PS
IDs XXX
CombinedLRIT/EMWIN
IRD
End results: one spacecraft transponder, one common receive system
OldLRITIRD
OldEMWIN
IRD
OldReference
OldReference
New Reference
The Government's firm requirement will be defined in the draft solicitation
and subsequent final solicitation
16
Upcoming NOAA-sponsored Direct Read-out User
Conference
December 8-12, 2008 Miami, Florida