1

JPSS Science Data Services for theDirect Readout Community

Gyanesh ChanderDPES Manager

NASA GSFC Code 586

Bob LutzFTS Manager

NASA GSFC Code 581

AGU Fall MeetingDecember 15 19, 2014

https://ntrs.nasa.gov/search.jsp?R=20150000752 2018-06-28T09:39:08+00:00Z

2

• FTS Overview• FTS Requirements and Functions• FTS Logical Architecture• FTS Key Milestones• Progress to Date

Agenda

TDRSTDRS

ANC Data

LaunchServiceLaunchService

Space/Ground Comm. Node

MD Frames

SMD

TT&C

JPSS Ground System High-level Architecture OV-2 (Jul 14, 2014)

SMD

MSD

TT&C

TT&C

TT&C

TT&

C

TT&C

MD – Mission DataSMD – Stored Mission DataMSD – Mission Support data

DMSP DP AFWA,EUMETSAT PPF,

WindSat NRL/FNMOCSCaN POP GSFC

Findings

Alg.Support

MD Frames

HRDPerformance

HRDPerformance

MSD

SvalSat

JPSS Ground System

JPSS Ground System Provider of SMD, TT&C, LRD/HRD/MSD

No Internal Support, Pass-thru Only FVTS Flight Development

OrganizationsCommon Ground

System (CGS) Provider of SMD Only Direct Readout & Field Terminals GRAVITE External

SMD

GCOM-nGCOM-n

MD FramesCoriolis/WindSatMetOp-nDMSP-Fn(NASA)

Coriolis/WindSatMetOp-nDMSP-Fn(NASA)

HRD

TT&C

Management & Operations NodeSupporting

Ops

CLASS

NASA SDS

xDR, IPs

ESPCxDRs, IPs

Security

Ops Sim & Test Systems• Integrate

Element level simulators• Maintain Simulators

Alg, ASF, DRs, Findings

Correlative Data Sources

Data

Data

Alg & Val LCFs

STA

R

Data

SMD APs

Simulation Node

Data Processing Node

TT&C

/ MS

D

JPSS

Gro

und

Net

wor

k N

ode

Alg. Support

xDRs, IPs

Data

Network supports routing of NASA SCaN-supported missions, &

McMurdo NSF data

SMD (J-1+)

SM

D (J

-1+)

CGS Support Node (L3) FNMOC

NAVOCEANO

SMD APs

MSD

Fairbanks CDA

TrollSat

McMurdo

NSOF MMC

Fairmont CBU Alt MMC

NSOF IDPS Fairmont Alt IDPS

FVS FVTS

Flt Dynamics System

Support Nodes

Field TerminalUsers &

S-NPPJPSS-nS-NPPJPSS-n

WSC

LEGEND:Black/White Text – Block 1.2

+Red Text – Block 2.0

Purple Text – Block 3+

MSD

AGS

AGS

NASA CARA

Cal/Val Node

GRAVITE

Alg. Support

AFWAxDRs, IPs(Blk 1.2 only)

Field Terminal Support Node

HRD Monitor

4

Satellite Communication Links

TDRSSGround Link

TDRSSWhite Sands Station

Ground StationSvalbard, McMurdo, Fairbanks, Troll Direct Readout User Terminal

S-BandAntenna

DBAntenna

SMDAntenna

7.812 GHz15 Mbps

8.2125 GHz300 Mbps

TDRS

Direct BroadcastHigh Rate Data (HRD)

Downlink

Direct Broadcast componentsindicated in green

5

• JPSS Level 1 Requirements Document (JPSS L1RD) provides thefundamental requirements and scope of JPSS FTS– JPSS 1 will provide HRD broadcast

– JPSS 2 will provide HRD broadcast

– JPSS 2 will provide Low Rate Data (LRD) broadcasts

– JPSS shall provide the DR community with software, documentation, andperiodic updates to enable them to produce data products from JPSS,using their own hardware to receive the JPSS HRD broadcasts

• The JPSS Program is not responsible for developing, testing, ordeploying any JPSS capable field terminal

• JPSS will not perform encryption of the direct broadcast

FTS Level 1 Requirements

6

• Provide the following functionality:– Hardware Specifications

• Suggested field terminal configurations

– DFCB and RF ICD• Containing specifics on direct broadcast data format

– Software to produce RDRs from packets• Provide and maintain RT STPS

– Algorithms & Software• Used to create data products from direct broadcast

– Updated algorithms & software• Notification when updates are available

– Mission Support Data• Ancillary/auxiliary data

Key Functions of FTS (1 of 2)

7

• Provide the following functionality (cont’d):– Maintain list of registered users

• Condition for NTIA Frequency allocation approval

– Mission status• Users are provided status of the JPSS direct broadcast

– HRD Link status• Users are provided post pass performance information

– On orbit checkout and special tests• Gather feedback from FTS community

– User community prioritization of the HRD link• Provide feedback to the Program

– Promote the use of the JPSS data products from HRD link

Key Functions of FTS (2 of 2)

8

GRAVITE

JPSS Science Team / STAR

CGS

IDPS

Svalbard

HRD Link Status

FTS Distribution Server

DRL/IPOPP UWISC/CSPP

Customer Community

JPSS Ground Project Requirements

ADL

ADL

ADL

Algorithm Development Library (ADL)Centerpiece of FTS Implementation

• JPSS Science Team members heavily relyupon ADL as part of the Algorithm ChangePackage (ACP)

• ADL provide a means for processing RDRsinto SDRs and EDRs

• IPOPP and CSPP currently use ADL in theirHRD processing system

• Most of the direct broadcast users are notfamiliar with using ADL

• JPSS Program will provide the seed moneyfor the development and maintenance ofIPOPP and CSPP

Community SatelliteProcessing Package (CSPP)

International Polar OrbiterProcessing Package (IPOPP)

Customer Community

9

FTS Logical Architecture

FTSDistribution

ServerFTS

Customers

FTSAcquisitionServer

JPSS Field Terminal Support

CGS SupportNode

CGS

JPSS Ground System

44

1. Mission Support Data(MSD)2. Software (ADL) and Documentation3. Intermediate Products4. Software, MSD, Field Terminal Documentation5. Documentation6. HRD

66

11

22

JPSS CM55

GRAVITE33

10

FTS Data Acquisition and Organization

• FTS acquires and organizes data and documentation relevant to HRD processingfrom JPSS managed satellites

• Data is obtained from the CGS, the CGS support node, GRAVITE and JPSS CM, andstored in the Data Acquisition server

• This data includes processing source code (e.g., ADL, algorithm update packages,RT STPS), documentation, ancillary data, intermediate products and auxiliarydata (PCTs, LUTs, Mission Notices, Schedules)

11

FTS Data Distribution

• The FTS mechanism for data distribution is a web portal. Selecteddata stored on the FTS server is made available for distribution by theFTS Distribution Server

• Customers desiring the system building blocks (e.g., ADL, algorithmsor RT STPS) interact with the FTS Distribution Server to downloadsource code distribution packages for these components

• Mission Support Data, updated regularly from the CGS, is similarlymade available to FTS customers

12

FTS Customer Registration and Reporting

• Customer registration for FTS access is a self service capability enabledthrough interaction with the Distribution Server main page

• Customer provided contact information is available to the FTSoperator for reporting purposes (e.g., to support requests forfrequency usage documentation) and notification purposes (to makeFTS customers aware of changes to in system status)

13

FTS System Status and Health

• The FTS internally monitors FTS component health and status, and logs relevantinformation on the FTS server to support FTS troubleshooting and recovery

• The monitoring approach planned for the FTS leverages existing capabilities usedfor monitoring DPES infrastructure. Expected items to monitor may include:

– Hardware Status,– Disk, CPU and Network Utilization– Server Availability– Process Status

14

System Architecture

15

Software Design

16

FTS Block 2.0 TTO Path Forward

• Block 2.0 Changes for FTS– Inputs from CGS changing with Block 2.0:

• CGS Extranet Web Server • CGS Support Node content with Block 2.0

– Internal changes to FTS:» Checksum calculation differences (from

CRC to SHA 384)» Possible directory changes

– Output:• University of Wisconsin and GSFC Direct

Readout Lab (DRL) using FTS Web Portal instead of NPP External Mission Support Data Server (E-MSDS) for accessing Ancillary and Auxiliary Files

17

FTS Key Milestones

2014 2015Q2 Q3 Q4 Q1 Q2 Q3

Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep

10/1/14

CY

FTS SRR/SDR

FTS CDR

FTS SW Build 1 TRR

FTS SW Build 1 Complete

FTS SW Build 2 TRR

FTS SW Build 2 Complete

FTS HW Build for V1 ATRR

FTS HW Build for V1 Complete

FTS SW Build 3 TRR

FTS SW Build 3 Complete

FTS Version 1.0 TRR (HW/SW)

FTS Version 1.0 Operational

18

Progress to Date (1 of 2)

• The new FTS implementation plan was accepted by the Ground, PSE, and NJOmanagement, presented at the JPSS Customer Forum (Nov 2013), anddiscussed with key stake holders (Dec 2013)

• Upgraded HRD link receiver provided by the Svalbard Ground Station• Successfully awarded grants to NASA/DRL and Uwisc/CIMSS• Completed FTS Software and Hardware Design

– During the development of the Design Documents, three Peer Reviews were held (Junethrough August 2014) with Stakeholders

– Reviewers included the Integrators, JPSS Security, Mission Assurance and MSE– Comments received were incorporated into the next Draft of the Documents

• Supporting Documentation Developed (Subset)– FTS OpsCon Updated– FTS Level 3 and 4 Requirements Baselined– FTS Interface Definition Document (IDD) Completed– FTS Software Test Plan Completed

19

Progress to Date (2 of 2)

• The FTS SRR/SDR was successfully held on Apr 21, 2014– The IRT concluded that the artifacts clearly demonstrated that the FTS team has a

reasonable OpsCon, a good set of requirements, and a well thought out system

– Some of the key concerns included the scope of the FTS effort and clarification oncertain FTS requirements

– Received 6 RFAs and 4 ADV: All are closed

• The FTS CDR scheduled for Sep 17, 2014– The CDR was highly successful and the IRT was extremely pleased with the

proposed Software and Hardware Design

– The review panel approved the FTS team to proceed for implementation

– Received 5 RFAs and 2 RFIs: All are closed

20

Summary

• There is a paradigm shift in the FTS implementation– The JPSS Ground Project is no longer providing data processing framework– FTS is providing the necessary building blocks (software, documentation, and mission support

data) on the web portal– The proposed FTS implementation plan leverages ongoing activities to support needs of DB

community and meets all the FTS requirements– The proposed FTS implementation will ensure to meet NASA and NOAA Standards, Software

Engineering Requirements (NPR 7150.2A), IT Security, and Safety Mission Assurance

• The JPSS Program is supporting the development and maintenance of software package(IPOPP/CSPP) to demonstrate the ability to produce ready to use products from theSNPP/JPSS HRD link

• FTS will leverage existing annual workshops to provide a forum for the DB communityto present, discuss, learn, and provide feedback to the JPSS Program