Goes r user requirements change process
Download
1 / 16

GOES-R User Requirements Change Process - PowerPoint PPT Presentation


  • 131 Views
  • Uploaded on

GOES-R User Requirements Change Process. Barbara Pfarr Bill Mazur Monica Todirita GOES-R Program Systems Engineering. 1. GOES-R Requirements Evolution. REQUIREMENTS. System Architecture Government and Industry Studies Phase. Program Definition & Risk Reduction (PDRR) Phase.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'GOES-R User Requirements Change Process' - fonda


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Goes r user requirements change process

GOES-R User Requirements Change Process

Barbara Pfarr

Bill Mazur

Monica Todirita

GOES-R Program Systems Engineering

1


Goes r requirements evolution
GOES-R Requirements Evolution

REQUIREMENTS

System Architecture

Government and Industry Studies Phase

Program

Definition &

Risk Reduction

(PDRR) Phase

Acquisition and Operations (A&O) Phase

1999

2005

2014

2007

2008

Key Decision

Points (KDP):

C/D

B

Launch Readiness

CORL

Requirements

Documents

GPRD

2004

NWS ORD

1999

Level I

LIRD 2007

Update TBD

NASA/MOU

Level II

7120.5D

MCP

2007

Level IIa

Update

TBD

MRD 3

2007

MRD 2’

2005

MRD 1

2003

Project Plans

Level III / Level IIIa

Project Interface Documents & Specifications

GOES Users

Conferences

GUC

Oct 2002

GUC

May 2004

GUC

May 2006

GUC

Jan 2008

GUC

May 2001


Nws operational requirements document ord circa 1999
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.

    • Improved spatial coverage of the sounder sensor.


Mapping requirements to goes r approved system solutions

Requirements

Aerosols

Clouds

Precipitation

Atmospheric Profiles

Atmospheric Radiance

Atmospheric Winds

Land

Ocean

Coastal Waters & Estuaries

Space & Solar

Mapping Requirements To GOES-R Approved System Solutions

Instruments

NOAA Users

Advanced Baseline Imager (ABI)

Ecosystems, Weather & Water, Climate, Commerce & Transportation

National Weather Service (NWS)

EUVS / XRS Irradiance Sensor (EXIS)

Oceanic & Atmospheric Research (OAR)

Solar Ultra Violet Imager (SUVI)

Instruments

National Ocean Service (NOS)

L1RD

MRD

Other Users

Space Environment In-Situ Suite (SEISS)

National Marine Fisheries Service (NMFS)

Geostationary Lightning Mapper (GLM)

NOAA Marine & Aviation Operations (NMAO)

Program Planning & Integration (PPI)

National Environmental Satellite, Data & Information Service (NESDIS)

Spacecraft

MRD

Upcoming Procure-ments

Ground Segment


Goes r requirements process during acquisition and operations
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.



User request for change process
User Request for OperationsChange Process

CORL

User

Request

Validation

Scientific

Analysis

(TAP)

GORWG

Review /

Analysis

ECRB

Review

(GPO)

CCB

Disposition /

Approval

(GPO)

Level 1 and / or funding required

PMC

Approval

Implement

Request

Non- Level 1 and funding available


Example of a user requirements change currently under consideration

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


Goes r user requirements change process

GOES-R Consideration

Series

GOES NOP Series

Combined EMWIN/LRIT

Separate EMWIN/LRIT

LRIT User

EMWIN CC

Silver Spring, MD

(EMWIN Source)

EMWIN

User

EMWIN User

NOAA

Satellite Operations Facility

Suitland, MD

(LRIT Source)

LRIT User

Combination of

Emergency Managers Weather Information Network (EMWIN)

and Low Rate Information Transmission (LRIT) Services

Command and Data Acquisition Station

Wallops, VA

The Government's firm requirement will be defined in the draft solicitation and subsequent final solicitation


Emwin and lrit characteristics
EMWIN and LRIT Characteristics Consideration

  • 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


Emwin and lrit concerns and proposed solution

EMWIN I Consideration

EMWIN N

LRIT I/N

EMWIN/LRIT

LRIT I, LRIT N

EMWIN I

EMWIN N

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

The Government's firm requirement will be defined in the draft solicitation and subsequent final solicitation


Pros and cons
PROs and CONs Consideration

  • 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


User concern mitigation prototyping the solution
User Concern Mitigation: ConsiderationPrototyping 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

The Government's firm requirement will be defined in the draft solicitation and subsequent final solicitation


Impacts to requirements documentation
Impacts to Requirements Documentation Consideration

  • 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


Impacts to requirements documentation cont
Impacts to Requirements Documentation (cont.) Consideration

LRITMRD Req ID 467

EMWINMRD Req ID 463

New Reference

Old

Reference

Old

Reference

Combined

LRIT/EMWIN IRD

Old

LRITIRD

Old

EMWIN IRD

Flight Project F&PS IDs XXX

Ground Project F&PS IDs XXX

End results: one spacecraft transponder, one common receive system

The Government's firm requirement will be defined in the draft solicitation and subsequent final solicitation


Upcoming noaa sponsored direct read out user conference december 8 12 2008 miami florida
Upcoming NOAA-sponsored Direct Read-out User Conference ConsiderationDecember 8-12, 2008 Miami, Florida