JPSS-REQ-1003
Joint Polar Satellite System (JPSS)
National Environmental Satellite, Data,
and Information Service (NESDIS)
Environmental Satellite Processing
Center (ESPC)
Requirements Document (JERD)
Volume 1
Version: 3.2
Date Aug 23, 2018
U.S. Department of Commerce (DOC)
National Oceanic and Atmospheric Administration (NOAA)
National Environmental Satellite, Data, and Information Service (NESDIS)
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
ii
Approval
[signature on file] Gregory A. Mandt Director, Joint Polar Satellite System
Date
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
iii
Change History Log
This record of changes will be initiated once this document has been signed. This document and
subsequent versions of this document are maintained under NOAA JPSS Office (NJO)
configuration control. Proposed changes to the body of the document will be presented for
review and approval to the PCB.
Revision Date Sections Changed Changed Author
1.0 6/4/2013 General change changed Free-Flyer to Polar Free Flyer throughout the document
Maria Larsen
1.0 6/4/2013 Figure 1 Updated Figure 1 to show PDA, ADRS, NDE 2.0 and CBU SRDs, and removed the GCOM SRD as this requirements will ultimately be satisfied in NDE 2.0.
Maria Larsen
1.0 6/4/2013 Context Diagram Update the context diagram to depict ESPC in 2 sites (CBU and NSOF)
Maria Larsen
1.0 6/4/2013 1.3.4 JPSS Space Segment
Changed the last sentence for Free Flyer to singular tense since there is only one polar free flyer. “Their design lives” replaced with “The design life.”
Maria Larsen
1.0 6/4/2013 1.3.4 JPSS Space Segment
Deleted references to JPSS-2 hosting CERES and OMPS-Limb instruments. Added language to indicate JPSS 2 will provide accommodations for RBI and OMPS Limb. Added 'RBI' to Acronyms in Appendix B.
Maria Larsen
1.0 6/4/2013 2.1 Applicable Documents
corrected versions and dates for : JPSS-REQ-1001 JPSS Level-1 Requirements Document version 1.7 May 23, 2013 JPSS-REQ-1002 JPSS Level-1 Requirements Document Supplement version 2.8 May 24, 2013 JPSS-PLN-3109 JPSS Program Implementation Document (PID) (JPSS-PLN-3109) version 1.9 May 23, 2013
Maria Larsen
1.0 6/4/2013 2.1 Applicable Documents
Add version dates to: ISO 19115 Metadata Standard for Geographic Information ISO 19115 effective May 1, 2003 ISO 19115-2 Metadata Standard for Geographic Information, Part 2:
Maria Larsen
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
iv
Extensions for Imagery and Gridded Data effective April 7, 2008
1.0 6/4/2013 3.1.1.1 Data Formats JERD-1570
Removed VIIRS Polar Winds Maria Larsen
1.0 6/4/2013 3.1.4 Capacity, Margin and Scalability JERD-548
changed from 'The NESDIS ESPC shall be capable of supporting product output volumes of 40 terabytes of JPSS data, per day.' to 'The NESDIS ESPC shall be capable of supporting product output volumes of 25.9 terabytes of JPSS data per day. ' Previous 40TB per day of JPSS egress data was an initial estimate. The PDA system is sized at its peak to distribute approximately 40TB per day (37TB) but that is across ALL missions, not just JPSS... the PDA is sized for 26TB per day total... This number does not include the AFWA data flow...
Maria Larsen
1.0 6/4/2013 3.1.7 Data Accounting JERD-1758
Deleted JERD-1758 – JERD-1758 The NESDIS ESPC shall monitor the data quality of the output data. It was redundant with JERD-1756
Maria Larsen
1.0 6/4/2013 3.3.1.5 Intermediate Products
Deleted JERD-164 The NESDIS ESPC shall make available the Retained Intermediate Products produced by the JPSS Ground System, as itemized in Table 3.6 of the L1RD Supplement, to ESPC Registered Users. -PCB determined that this was for Real Time use and RIPS are not for Real Time use. RIPS are available from CLASS
Maria Larsen
1.0 6/4/2013 3.3.1.5 Intermediate Products
Deleted header '3.3.1.5 Intermediate Products' since the only requirement in the section was deleted (JERD-164) leaving a blank section.
Maria Larsen
1.0
6/4/2013 3.6 Interface Requirements
Added an interface requirement that addresses interface to registered and adhoc users: JERD-1775 The NESDIS ESPC shall provide an interface between the system's distribution capability (i.e.
Maria Larsen
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
v
PDA) and external data consumers.
1.0 6/4/2013 3.7 Security Added the following text to explain 'See L1RD-F': Any security requirements contained in this section are in addition to those already levied by the L1RD-F. Most of the security requirements are contained in L1RD-F, which is an applicable document, and therefore are not being repeated in this section.
Maria Larsen
1.0 6/4/2013 3.8 Continuity of Operations
Add a requirement similar to the JERD-1596 that flows down the Level 1 requirement for CLASS to archive a minimal set of data products during a COOP scenario. JERD-1776 The NESDIS ESPC shall as part of the CBU capability to fulfill Continuity of Operations (COOP) be capable of distributing the minimum set of data products in accordance with the JERD Appendix A designated for APC distribution.
Maria Larsen
1.0 6/4/2013 3.8 Continuity of Operations
Added ‘Land Surface Emissivity (ATMS)’ under JERD-1596
Maria Larsen
1.0 6/4/2013 4.0 Appendix A JPSS Data Products (referenced in section 3.3)
AMSR-2/3 SST was designated as required from the Alternate Processing Center (APC).
Maria Larsen
1.0 6/4/2013 4.0 Appendix A Added a column in Appendix A to designate the products (which includes any associated reformatting or translations) that are required for distribution from the Alternate Processing Center (APC) during a COOP event.
Maria Larsen
1.0 6/4/2013 5.0 Appendix B Acronyms
Added L1RD-F acronym Added RBI acronym Added APC acronym
Maria Larsen
1.1 9/4/13 1.3.1 JPSS System Description
Changed text from “The JPSS will also provide operational continuity of satellite-based observations and products for NOAA’s Polar-orbiting Operational Environmental Satellites (POES) and the NASA Earth Observing
Markus Sorrells
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
vi
System (EOS) satellites.” To “The JPSS will also provide operational continuity of satellite-based observations and products for NOAA’s Polar-orbiting Operational Environmental Satellites (POES) and the NASA Earth Observing System (EOS) satellites.”
1.1 9/4/13 1.3.4 JPSS Space
Segment
Changed text from “JPSS-2 is scheduled to be launched in 2022. The same instruments currently hosted on JPSS-1 will be hosted on JPSS-2. JPSS-2 will provide accommodations for RBI and OMPS Limb.” To “JPSS-2 is scheduled to be launched in 2021. The same instruments currently hosted on JPSS-1 will be hosted on JPSS-2. JPSS-2 will provide accommodations for RBI and OMPS Limb if agreement is rescheduled with NASA.
Markus Sorrells
1.1 9/4/13 1.3.4 JPSS Space
Segment
Deleted the following text: “Polar Free Flyer is designed to carry three instruments: 1) A-DCS, 2) SARSAT, and 3) TSIS. Polar Free Flyer is planned for launch in early 2017. The design life is 5 years and will launch as a ride share.”
Markus Sorrells
2.0 5/7/14 3.1.1.1 Data Formats,
JERD-1570
Per CCR NJO-2013-032, which was approved Out-of-Board (OOB) by the NJO PCB Chair, the VIIRS Polar Winds (VPM) BUFR format was re-inserted into this section after it was inadvertently removed by the 6/4/2013 NJO PCB. Decision was captured on the 01/13/2014 “Documentation of Program Control Bard Decisions” memo which was disseminated on 2/14/14.
Markus Sorrells
2.0 5/7/14 3.1.1.1 Data Formats,
JERD-88
Per CCR NJO-2014-005, which was approved by the 3/26/14 NJO Program Control Board, the SZIP compression requirement was removed.
Markus Sorrells
2.0 5/7/14 3.1.1.1 Data Formats,
JERD-88
Per CCR NJO-2013-014, which was approved by the 3/26/14 NJO Program Control Board, the MPEG compression
Markus Sorrells
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
vii
requirement was removed.
2.0 5/7/14 3.3.3 Blended Products
Per CCR NJO-2013-027, Rev C, this section was added to the JERD
Markus Sorrells
2.0 5/7/14 Table A. Table of
Ancillary Data
Per CCR NJO-2013-014, which was approved by the 3/26/14 NJO Program Control Board, NWS was removed as a data source from the Table of Ancillary Data since it does not need to identify two sources for Navy Global Environmental Model (NAVGEM), or Navy Aerosol Analysis and Prediction System (NAAPS).
Markus Sorrells
2.0 5/7/14 3.5 System
Performance, JERD-260 Rational
Per CCR NJO-2014-014, which was approved by the 3/26/14 NJO Program Control Board, the rationale wording was updated to clarify data recipients identified in L1RDS Table 2.2. Per CCR NJO-2014-006, Rev A, which was approved by the 3/26/14 NJO Program Control Board, EUMETSAT was added as a data recipient
Markus Sorrells
2.0 5/7/14 Appendix A, JPSS Data
Products
Table was updated per CCR NJO-2014-002
Markus Sorrells
2.0 5/7/14 Note 1 – TBR Table
Per CCR, NJO-2014-001, which was approved Out-of-Board by the NJO PCB Chair Administrative clarifications were included to distinguish that product latency requirements do not apply to end user reformatting requests that arrive at the user interface; i.e. the ESPC PD segment.
Markus Sorrells
2.0 6/18/14 - Section 1, 1st Para, 5th line - Section 3.1.4, JERD-114 Requirement, 2nd line (both instances) - Section 3.1.4, JERD-116 Requirement, 2nd line - Section 5, Appendix B Acronyms, remove Polar Free Flyer satellite acronym
At the request of the JPSS Director, removed seven (7) references to the Polar Free Flyer (PFF) within the document, since the Polar Free-Flyer is no longer part of JPSS space segment. This change is captured by CCR NJO-2014-024.
Markus Sorrells
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
viii
- Section 6, Appendix C Glossary, in the “Primary Mission Sensor” definition - Section 6, Appendix C Glossary, in the “Secondary Mission Sensor” definition
2.0 6/18/14 - Section 5, Appendix B Acronyms, remove TSIS acronym - Section 6, Appendix C Glossary, in the “TSIS” definition
At the request of the JPSS Director, removed two (2) references to the Total and Spectral Solar Irradiance Sensor (TSIS) within the document, since TSIS is no longer part of JPSS space segment. This change is captured by CCR NJO-2014-024.
Markus Sorrells
2.0 6/18/14 Table of TBDs/TBRs Per CCR NJO-2014-023, “Removal of SARSAT and A-DCS Requirements”, was approved at the 7/17/14 PCB, removed the two (2) remaining TBRs within this document.
Markus Sorrells
3.0 11/20/14 Updated Title; Removed "Table of TBDs/TBRs"; Updated Sections 3.3, 3.3.1, 3.3.1.2, 3.3.3, and Table 1 in Appendix A
Per CCR NJO-2014-039 and 10/24/14 ERB Recommendations, the words “Volume 1” was added to the title of this document, the Table of TBDs / TBRs were removed, and the following modifications were captured in this version of the JERD: 1. Delete :
a. Delete: JERD-145 The NESDIC
ESPC products shall meet the data
product performance requirements
as specified in Appendix A
"product attributes" column,
unless an exclusion or degradation
condition occurs.
b. Delete: JERD-149 If a degradation
condition applies, the ESPC shall
produce retrieved values within an
EDR, SDR, or TDR that are
described by Degradation
Conditions as identified in
Appendix A column labeled
Markus Sorrells
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
ix
"applicable conditions, exclusions
or degradation conditions.
c. Delete Header 3.3.1.3 Excluded
Conditions
d. Delete: JERD-158 A quality flag
shall indicate the application and
identity of an exclusion condition
as defined in Appendix A.
e. Delete: JERD-159 The NESDIS
ESPC shall produce a quality flag
to indicate the application and
identity of an Exclusion Condition
to a retrieved value in a data
record.
f. Delete: Header 3.3.3 Blended
Products
g. Delete JERD – 2005
2. Change JERD-155
From:
JERD-155 The NESDIS
ESPC shall produce a quality
flag to indicate the application
and identity of a Degradation
Condition to a retrieved value in
a data record.
To:
JERD-155 The NESDIS
ESPC shall have the capability
to provide quality flags as
generated by algorithms.
Delete the Product Attributes column
and the Applicable Exclusion or
Degradation Conditions Column in
Table 1 “Table of Science Product
Requirements” in Appendix A JPSS
Data Products (referenced in section
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
x
3.3) and delete associated Note 1
“TBR Table”
3.0 11/20/15 CC NJO-2014-015, Split the JPSS ESPC Requirements Document into Two Volumes
JERD WG
3.1 2/19/15 Para 3.3.3 Blended Products
Per CCR NJO-2014-033, Rev A, which was reviewed and approved at the 2/19/15 PCB and CCR was signed
3/17/15, the following Blended Product was added to paragraph 3.3.3 – “Blended Biomass Burning (with VIIRS) (Sup High)
Markus Sorrells
3.1 5/7/15 Table A. Table of Ancillary Data
Per CCR NJO-2013-014, which was approved by the 3/26/14 NJO Program Control Board, NWS was removed as a data source from the Table of Ancillary Data since it does not need to identify two sources for Navy Global Environmental Model (NAVGEM), or Navy Aerosol Analysis and Prediction System (NAAPS). The above change incorrectly removed the NAVGEM and NAAPS rows from this table instead of just removing “NWS” as a data source for these ancillary data. This change puts these two ancillary data types back into Table A, but without citing “NWS” as a data source.
Markus Sorrells
3.1 6/10/15 Added GMASI product to the JERD Vol 1 table of Ancillary Data
Per CCR NJO-2015-003, Rev B. “GMASI data for CGS was approved at the 12/21/16 PCB and signed by the PCB Chair on 3/18/16.
Markus Sorrells
3.1 6/10/15 Modified table in Appendix A JPSS Data Products in Section 3.3 to include the ESPC product generation and discontinue ESPC AF pass-through
Per CCR NJO-2014-025, Rev D “Reallocation of JPSS Active Fires Algorithm”
Markus Sorrells
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
xi
3.1 10/9/15 Removal of Para 3.3.3 Blended Products
Per CCR NJO-2015-022, Rev C “Remove “Blended Product” references from JERD Vol 1 and add Multiplatform Tropical Cyclone Surface Wind Analysis product to JERD Vol 2 (Blended product)”, the entire contents of Para 3.3.3 should be transferred to JERD Vol 2 Appendix D and Para 3.3.3 should be removed. This CCR supersedes CCRs NJO-2013-027, Rev C and NJO-2014-034, Rev A
Markus Sorrells
3.1 4/20/16 Reallocation of all priority 3/4 products to NDE Appendix A
Per CCR NJO-2015-018, Rev C, “Reallocation of all priority 3/4 product to NDE”, Direction Letter
Markus Sorrells
3.1 4/20/16 3.1.1.1 Removed BUFR requirement for AMSR-2 TWP, CLW, and SSW Added BUFR requirement for Sensor Calibrated Data and SST
Per CCR NJO-2015-031 – AMSR-2 Reformatting requirements in JERD Vol 1 – removed BUFR requirement for AMSR-2 TWP, CLW, and SSW and added BUFR requirements for Sensor Calibrated Data and SST
Bonnie Reed
3.2 10/11/16 Section 3.1.1.1, pages 8 and 9; Section 3.1.4, pages 9 and 10; Section 3.1.7.6, page 12; Section 3.8, page 17; Appendix A. page 19;
Per NJO-2015-015, Rev C, “AMSR2 Data
Delivery in Block 2.0 for NDE 2.0
Processing”, Edit the following GCOM-
W1 and AMSR-2 requirements to match
the change for receipt of AMSR2 APID
Sorted Data Files delivered from IDPS:
JERD-1740, JERD-1743, JERD-114, JERD-
115, JERD-116, JERD-1748, and JERD-
1596.
And
Update Appendix A, JPSS Data Products
to match the change for receipt of
AMSR2 ASD Files
Markus Sorrells
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
xii
3.2 10/7/16 Appendix A, pages 19 – 21 and 23 - 24;
Per NJO-2015-033, “Administrative
Table Updates for the Supplement and
JERD Vol. 1 and 2” changes were made
Appendix A JPSS Data Products.
Administratively included proposed
table updates with the Priority ¾
Reallocation CCR to ensure consistency
across the documentation. See the
updated tables as attachments to the
CCR where red changes indicate the
Priority ¾ CCR updates
Markus Sorrells
3.2 6/15/17 List of Tables, page xv; Section 3.4, page 14; Table A, page 15; Appendix B, page 25 and 26;
Per CCR NJO-2017-002, “GTS routing
requirements for select JPSS products –
JERD Vol 1.”
Added new requirement that states JPSS will support a subset of critical products as being GTS ready, Added Table B. Added new acronyms.
Markus Sorrells
3.2 6/15/17 Section 1.3.3, page 3 Per CCR NJO-2017-011, Rev A, “Admin CCR:
Updating JERD Vol 1 and Vol 2 with list of
Key Performance Parameters (KPPs)”
Modified the text in both volumes of the JERD to KPP language reflected in other JPSS L1 documents.
Markus Sorrells
3.2 12/13/17 Appendix A Table, page 22
Per CCR NJO-2016-015, Rev C, “Addition
of OMPS Limb Profiler SDR and EDR
product requirements for S-NPP”
Included the OMPS-L SDR and EDR
product requirements and
specifications for the S-NPP
implementation into Appendix A table
Markus Sorrells
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
xiii
3.2 12/14/17 Appendix A, page 23; Per CCR NJO-2016-018, “Addition of
ATMS Snowfall Rate product
requirements for S-NPP and JPSS”
Added the ATMS Snowfall Rate (SFR)
product to this document
Markus Sorrells
3.2 12/14/17 Appendix A, page 24 Per CCR NJO-2016-021, Rev A, “Removal
of Surface Type EDR Requirement from
GCOM-W1 L1RD”
Removed Surface Type terminology and
products associated with AMSR2
Markus Sorrells
3.2 12/14/17 Appendix A, page 24; Per CCR NJO-2016-030, Rev A, “Moving
NDE Vegetation Products to GVF Grid”
Updates the Vegetation Indices Data
Products
Markus Sorrells
3.2 12/14/17 Appendix A Per CCR NJO-2017-005, “Reconciliation
of JPSS Requirement Documents from
CCR NJO-2015-018”
Clarifies from approved CCR NJO-2015-
018, Rev C, “Reallocation of all Priority
¾ products to NDE” which product
attributes changes were being
requested as well as includes additional
requirement updates that were not
addressed by CCR NJO-2015-018, Rev C
Markus Sorrells
3.2 9/19/18 1, 3, 6, 11, 14, and 16. Updated wording associated with
references to the Level 1 Requirement
Document Supplement (L1RDS)
Markus Sorrells
3.2 9/20/18 3, 6, 7, and 28 Updated language to indicate that JPSS-
1 launched on 11/18/17. Updated the
rev version of several reference
documents in Section 2.2. Deleted the
term “Anomalous System Behavior” in
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
xiv
Appendix C since it is not used in this
document.
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
xv
Table of Deviations/Waivers
Item No. Deviation/Waiver Waiver
Approved Effectivity
1 Extend the time allocated to ESPC for
reformatting the VIIRS SDR into BUFR, currently specified in L1RDS-3127
9L1RDS Table 2.2) and JERD-259
(Appendix A) as 7 minutes, to 100 minutes. The proposed time extension
will allow the NDE 2.0 system to reformat the VIIRS SDR with its
current planned system hardware. Per
NWS, the waiver for the VIIRS BUFR SDR is valid for 4 years, or until August
2018.
NJO-2014-011, Rev H - VIIRS SDR Reformatting Latency Deviation Request, r1.docx
NOSC Concurred
with Waiver on 12/04/14
Per NWS, the waiver for
the VIIRS BUFR SDR is valid for 4 years, or
until August 2018.
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
xvi
Table of Contents
1 Introduction ......................................................................................................................... 1
1.1 Purpose .................................................................................................................................. 1
1.2 Scope ..................................................................................................................................... 1
1.3 System Overview .................................................................................................................. 2
1.3.1 JPSS System Description ........................................................................................ 2
1.3.2 JPSS Context Diagram ............................................................................................ 2
1.3.3 JPSS System Architecture....................................................................................... 3
1.3.4 JPSS Space Segment ............................................................................................... 3
1.3.5 JPSS Ground Segment ............................................................................................ 3
2 Documentation Organization .............................................................................................. 6
2.1 Applicable Documents .......................................................................................................... 6
2.2 Reference Documents ........................................................................................................... 6
3 Requirements ...................................................................................................................... 8
3.1 General Requirements ........................................................................................................... 8
3.1.1 Units, Formats and Standards ................................................................................. 8
3.1.2 Operational Life ...................................................................................................... 9
3.1.3 System Monitoring and Reporting .......................................................................... 9
3.1.4 Capacity, Margin and Scalability ............................................................................ 9
3.1.5 Margin ................................................................................................................... 10
3.1.6 Utilization ............................................................................................................. 10
3.1.7 Data Accounting ................................................................................................... 11
3.2 Ingest ................................................................................................................................... 12
3.3 Product Generation ............................................................................................................. 12
3.3.1 Science Product Performance ............................................................................... 13
3.3.2 Produce Data Sets ................................................................................................. 13
3.4 Distribution ......................................................................................................................... 14
3.5 System Performance ........................................................................................................... 15
3.5.1 Data Latency and Product Recipients ................................................................... 15
3.5.2 Data Availability ................................................................................................... 16
3.5.3 User Services ........................................................................................................ 16
3.5.4 System Availability ............................................................................................... 16
3.5.5 Fault Tolerance ..................................................................................................... 16
3.6 Interface Requirements ....................................................................................................... 17
3.7 Security ............................................................................................................................... 17
3.8 Continuity of Operations..................................................................................................... 17
4 Appendix A JPSS Data Products (referenced in section 3.3) .......................................... 19
5 Appendix B Acronyms .................................................................................................... 25
6 Appendix C Glossary ....................................................................................................... 27
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
xvii
List of Figures
Figure 1 JERD in Sample JPSS Document Hierarchy ............................................................ 1 Figure 2 JPSS Context Diagram ................................................................................................ 2
List of Tables
Table A. Table of Ancillary Data.............................................................................................. 14
Table B. Recommended Minimum Product Suite for GTS Routing Consideration………15
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-1-
1 Introduction
The Joint Polar Satellite System (JPSS) is the National Oceanic and Atmospheric
Administration’s (NOAA) next-generation operational Earth observation program that acquires
and distributes global environmental data primarily from multiple polar-orbiting satellites. The
program plays a critical role to NOAA’s mission. The JPSS provides operational continuity of
satellite-based observations and products for the Suomi National Polar-orbiting Partnership (S-
NPP) satellite, JPSS satellites, and GCOM-W missions.
The JPSS Ground Segment is comprised of the JPSS Ground System (JPSS GS) and the
Environmental Satellite Processing Center (ESPC). The JPSS Ground Segment’s primary
command and control and data processing center will be located at the NOAA Satellite
Operations Facility (NSOF) in Suitland, MD. The JPSS alternate command and control and data
processing site will be located in Vertex Center in Fairmont, WV.
The ESPC provides data processing. The JPSS ESPC Requirements Document (JERD) is
responsive to both the JPSS the Multi-Mission System Specification (MMSS). (For legacy
requirements applicable to S-NPP and NOAA-20, the JERD is responsive to the JPSS L1RD
Supplement.)
This document is a level 2 document which allocates and flows down requirements to the JPSS
ESPC. Figure 1 below provides an example of where this Level 2 document fits within the JPSS
document hierarchy.
Figure 1 JERD in Sample JPSS Document Hierarchy
1.1 Purpose
The purpose of the JPSS ESPC Requirements Document (JERD) is to identify the functional and
performance requirements allocated to the ESPC in support of the JPSS mission.
1.2 Scope
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-2-
This document contains the top level set of requirements that define functional and performance
capabilities for the ESPC to meet the JPSS mission. These include but are not limited to
identification of system interfaces, and mandate system compliance with applicable regulations.
This document will also serve as a focal point for traceability of all JPSS lower level
requirements contained in project specific documentation.
1.3 System Overview
1.3.1 JPSS System Description
The JPSS Program, which constitutes the next series of US civilian polar orbiting environmental
sensing satellites, and sensor types that have been flown historically on polar satellites, will
implement NOAA’s requirements for collection of global multi-spectral radiometry and other
specialized meteorological, oceanographic, and solar-geophysical data via remote sensing of
land, sea, and atmospheric data. These data will support NOAA’s mission for continuous
observation of the Earth’s environment necessary to understand and predict changes in weather,
climate, oceans and coasts, and the space environment which support the Nation’s economy, and
protect lives and property. The JPSS will also provide operational continuity of satellite-based
observations and products for NOAA’s Polar-orbiting Operational Environmental Satellites
(POES) and the NASA Earth Observing System (EOS) satellites.
1.3.2 JPSS Context Diagram
Figure 2 JPSS Context Diagram
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-3-
1.3.3 JPSS System Architecture
The Joint Polar Satellite System is comprised of the JPSS missions and other missions that
support the fulfillment of the requirements in the JPSS Level 1 Requirements Document (L1RD)
Supported Missions. The basic architecture and many of the instruments and subsystems of the
JPSS Program were developed under the previous National Polar-orbiting Operational
Environmental Satellite System (NPOESS) and Suomi NPP programs. The JPSS missions
utilize the JPSS Space Segment (SS), JPSS Launch Support Segment (LSS) and the JPSS
Ground System (GS). These assets are procured by the JPSS Program and support one or more
of the program missions at various levels.
JPSS will provide a variety of environmental observations from the 1330 Local Time of the
Ascending Node (LTAN) orbit. The users will depend on the European Organisation for the
Exploitation of Meteorological Satellites (EUMETSAT)’s Metop satellites to provide data in the
2130 LTAN orbit (0930 Descending Node). Additionally, the JPSS will acquire and process
data from the Japanese Aerospace Exploration Agency (JAXA)’s Global Change Observation
Missions (GCOM). Collectively, these missions are designed to fulfill the Environmental Data
Record (EDR) requirements specified in the JPSS MMSS. (For legacy requirements applicable
to S-NPP and NOAA-20, the parent EDR requirements are specified in the JPSS L1RD and the
JPSS L1RD Supplement.) KPPs are system attributes that represent those minimum capabilities
or characteristics considered most essential to achieve an effective system. Failure to meet a
KPP attribute threshold may result in a reevaluation of the program. The JPSS KPPs are:
ATMS Temperature Data Records (TDRs)
CrIS Sensor Data Records (SDRs)
For latitudes greater than 60oN in the Alaskan region, VIIRS Imagery EDRs at 0.64 µm
(I1), 1.61 µm (I3), 3.74 µm (I4), 11.45 µm (I5), 8.55 µm (M14), 10.763 µm (M15),
12.03 µm (M16), and the 0.7 µm Near-Constant Contrast (NCC) EDR
87 minute data latency for the ATMS and CrIS SDRs and the VIIRS Imagery EDR
channels specified above
1.3.4 JPSS Space Segment
JPSS-1 launched in November 18, 2017. Capitalizing on the success of Suomi National Polar-
orbiting Partnership (SNPP), the JPSS-1 spacecraft hosts the five instruments currently
manifested on S-NPP: Visible Infrared Imaging Radiometer Suite (VIIRS); Cross-track Infrared
Sounder (CrIS); Advanced Technology Microwave Sounder (ATMS); Ozone Mapper and
Profiler Suite-Nadir (OMPS) and the Clouds and Earth's Radiant Energy System (CERES).
JPSS-1 will take advantage of the successful technologies developed through the Suomi NPP
satellite. JPSS-1’s design life is seven years, and it is scheduled to launch aboard a Delta-II
Launch Vehicle. JPSS-2 is scheduled to be launched in 2021. The same instruments currently
hosted on JPSS-1 will be hosted on JPSS-2. JPSS-2 will provide accommodations for RBI and
OMPS Limb if agreement is reached with NASA.
1.3.5 JPSS Ground Segment
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-4-
The JPSS Ground Segment is a shared ground infrastructure consisting of multiple subsystems
that support a heterogeneous constellation of polar-orbiting satellites, both JPSS Missions and
JPSS Supported Missions, through a comprehensive set of services.
1.3.5.1 JPSS Ground System
The services provided by the JPSS Ground System include Enterprise Management and Ground
Operations (EM&GO), Flight Operations (FO), Data Acquisition (DA), Data Routing (DR), Data
Product Generation (DPG), Data Product Calibration and Validation (DP C/V), and Direct
Readout Support (DRS). Traditional NOAA systems and facilities which form a part of the JPSS
Ground Segment include the NOAA Satellite Operations Facility (NSOF), the Consolidated
Back Up (CBU) facility, and the Environmental Satellite Processing Center (ESPC). The NOAA
Comprehensive Large Array-data Stewardship System (CLASS) is not a part of the JPSS Ground
Segment.
1.3.5.2 Environmental Satellite Processing Center (ESPC)
The Environmental Satellite Processing Center (ESPC) is NOAA's primary data-processing
system for the Nation's environmental satellite data; the ESPC is located at the NOAA Satellite
Operations Facility (NSOF) in Suitland, MD. The ESPC ingests, processes, and distributes
environmental data and information received from all of NOAA's satellites, several foreign
countries' satellites and the Department of Defense's satellites. The ESPC includes the
operational satellite data distribution network which provides NESDIS' customers access to real-
time/near real-time environmental data and information on a continuous (24 hours per day/7 days
per week) basis. The primary product applications are near real-time imagery, interactive
products, and automated products.
The ESPC consists of four primary segments: Ingest (ING), Product Generation (PG), Product
Distribution (PD), and Infrastructure (INF).
Ingest Segment
The Ingest Segment receives (ingests) satellite data from the NOAA geostationary and polar
satellites, selected NASA and DoD satellites, and foreign government environmental
satellites by a variety of methods ranging from direct receipt via an antenna on the roof of
NSOF to file transfers from other organizations. The ESPC system will receive data
products from the JPSS Ground System and ancillary/auxiliary data from external, non-ESPC
sources. Ancillary data is critical to the processing and generation of many ESPC products.
This data includes but is not limited to Numerical Weather Prediction (NWP) models
produced by the National Weather Service, surface observations from the Automated Surface
Observing System (ASOS) network, observations from upper-air soundings from
radiosondes, and in situ observations from ships, buoys, and aircraft.
Product Generation Segment
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-5-
The Product Generation Segment processes and packages mission data to meet user
requirements. The ESPC will process JPSS and Global Change Observation Mission
(GCOM) mission data into sensor and environmental data products, repackage sensor and
environmental data products received from the JPSS Ground System, and provide data
compression services to meet user requirements.
Product Distribution Segment
The Product Distribution Segment exchanges data between ESPC internal processing
systems and external users mission data, data products, and ancillary and auxiliary data. It
includes a user service function that provides an automated interface enabling users to search
and request data products (subscription and ad hoc) and provides status on the request. The
ESPC provides a “push/pull” data transfer capability to provide xDRs and data to users.
Infrastructure Segment
The Infrastructure Segment provides functionality to communicate between all ground
segment and external entities. It consists of communication servers (e.g., POP servers,
routers), distributed Local Area Networks (LANs), Wide-Area Network (WAN), point-to-
point fiber connections, and network security systems (e.g., firewalls). The ESPC provides
some of these capabilities. Additional capabilities are provided as a part of the facility (e.g.,
NSOF), or by other users.
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-6-
2 Documentation Organization
Section 1 provides information regarding the scope, purpose, background and organization of
this document.
Section 2 lists applicable and reference documents that were used as sources of information for
this document or that provide additional background information to aid understanding of the
requirements. Applicable documents are documents from which this document was derived.
Reference documents are documents that amplify or clarify the information contained in this
document.
Section 3 contains the NESDIS ESPC functional and performance requirements that apply to the
Joint Polar Satellite System (JPSS) only. This section identifies the JPSS Requirements,
including JPSS data product performance requirements from the JPSS Level 1 Requirements
Document (L1RD) Supplement that are allocated to the ESPC.
Appendices contain Acronym Lists and Definitions.
2.1 Applicable Documents
The ESPC must be compliant with the following documents:
JPSS-REQ-1001 JPSS Level-1 Requirements Document (S-NPP and NOAA-20 only)
JPSS-REQ-1002 JPSS Level-1 Requirements Document Supplement (S-NPP and NOAA-20
only)
JPSS-REQ-1005 JPSS Multi-Mission System Specification (JPSS-2+)
JPSS-PLN-3109 JPSS Program Implementation Document (PID)
Joint Polar Satellite System (JPSS) Ground System to National Environmental Satellite, Data,
and Information Service (NESDIS) Environmental Satellite Processing Center (ESPC) Interface
Requirements Document (474-00303)
Joint Polar Satellite System (JPSS) Common Ground System to National Environmental
Satellite, Data and Information Service (NESDIS) Environmental Satellite Processing Center
(ESPC) Interface Control Document (474-00411)
ISO 19115 Metadata Standard for Geographic Information ISO 19115 effective May 1, 2003
ISO 19115-2 Metadata Standard for Geographic Information, Part 2: Extensions for Imagery and
Gridded Data effective April 7, 2008
2.2 Reference Documents
The following documents provide additional information:
474-01548 Joint Polar Satellite System (JPSS) Ground System Security Requirements Document
Rev C 02/22/2018
470-00019 Joint Polar Satellite System (JPSS)-1 Mission System Specification Rev- April 12,
2012
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-7-
470-REF-00033 Memorandum of Understanding (MOU) Between National Oceanic and
Atmospheric Administration (NOAA) and Japanese Aerospace Exploration Agency (JAXA) in
Relation to the Cooperation for the GCOM-W1 Rev- 7/18/11
474-00306 JPSS Ground System to NOAA Space Operations Facility (NSOF) Facilities
Interface Requirements Document (IRD) Rev G 9/22/16
474-00310 JPSS Ground System (GS) to National Environmental Satellite, Data, and
Information Service (NESDIS) Consolidated Backup (CBU) Facilities Interface Requirements
Document (IRD) Rev F 9/22/16
JPSS Common Data Format Control Book (CDFCB) Volumes I through VI (474-00001-01 Rev
C, 6/21/12, 474-00001-02 Rev D, 6/21/12, 474-00001-03 Rev C, 6/21/12, 474-00001-04 This
has many parts. Part 01 is Rev A, 11/30/11, 474-00001-05 Rev C, 6/21/12, 474-00001-06 Rev
B, 6/21/12) (Note: Only CDFCB Vols I and VI exist for Block 2 and beyond).
Environmental Satellite Processing and Distribution System (ESPDS) Development Global
Change Observation Mission – Water (GCOM-W1) System Requirements Document Rev- 30
April 2012 (included in Project Plan)
Department of Commerce IT Security Program Policy and Minimum Implementation Standards
The Memorandum of Agreement for Data Acquisition, Processing and Exchange (DAPE) Rev-
24 Sep 2008
Initial Joint Polar System (IJPS) Memorandum of Agreement (MOA)
MOA between NOAA and EUMETSAT for Joint Transition Activities (JTA).
ESPDS-DAP-WA2-DOC-1.0, Standards for Algorithm Delivery and 254 Integration Using
Delivered Algorithm Packages (DAPs)
IETF RFC 2460 Standards for Internet Protocol routing as defined in accordance with IETF RFC
2460 - Internet Protocol. IPv6 compatibility is required in accordance with US Executive Order
893, effective June 2010
474-00109 JPSS Ground System to Kongsberg Satellite Services (KSAT) Interface
Requirements Document (IRD) Effective Date: February 9, 2018
474-REF-00151 Global Change Observation Mission Water (GCOM-W1) AMSR2 Level 1
Product (A, B, and R) Format Specification for the GCOM-W1 Rev- 10/8/2011
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-8-
3 Requirements
This document contains the ESPC functional and performance requirements that apply only to
the Joint Polar Satellite System (JPSS) and not to other missions which the ESPC supports.
3.1 General Requirements
3.1.1 Units, Formats and Standards
JERD-77 The NESDIS ESPC shall be capable of IPv6, per IETF RFC 2460.
JERD-1739 The NESDIS ESPC shall make available metadata with delivered data products
that are compatible with the ISO 19115 and 19115-2 metadata standards, with
extensions as necessary to support NOAA user needs.
3.1.1.1 Data Formats
Note: Appendix contains detailed information regarding specific products that require tailoring
and translating.
JERD-79 The NESDIS ESPC shall provide functionality to translate xDR products from HDF5,
to the following file formats:
Georeferenced Tagged Image File Format (GeoTIFF)
GRIdded Binary Format 2 (GRIB2)
Network Common Data Format 4 (NetCDF4)
JERD-1570 The NESDIS ESPC shall provide functionality to translate the following xDR
products from HDF5, to BUFR:
ATMS radiances (SDR/TDR)
CrIS Radiances (SDR)
VIIRS Radiances (SDR)
VIIRS Polar Winds
Sea Surface Temperature
Total Column Ozone
Nadir Profile Ozone
Aerosol Optical Thickness
JERD-1740 The NESDIS ESPC shall provide functionality to translate the following xDR and
ASD products from NetCDF, to BUFR:
AMSR-2 Sea Surface Temperature
AMSR-2 Sensor Calibrated Data
JERD-84 The NESDIS ESPC shall provide functionality to tailor xDR products that can be
tailored to the following projections: Plate carrée, Mercator, Polar Stereographic.
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-9-
JERD-88 The NESDIS ESPC shall provide functionality to compress data, including in the
following formats: GZIP, ZIP, ZLIB, JPEG.
JERD-1743 The NESDIS ESPC shall be capable of converting ASD files into raw APID files.
JERD-1755 The NESDIS ESPC shall be capable of applying WMO headers to any JPSS
product as requested by the user.
Rationale: NWS requires use of WMO headers.
3.1.2 Operational Life
JERD-95 The NESDIS ESPC new components supporting JPSS functions shall have a
design life through at least FY2025.
3.1.3 System Monitoring and Reporting
3.1.3.1 System Status Reporting
JERD-104 The NESDIS ESPC shall make all system status information including detected
hardware and software anomaly information accessible to the designated authority
for queries and report generation.
3.1.3.2 Performance Reporting
JERD-110 The NESDIS ESPC shall make performance measurements accessible to the
designated authority for queries and report generation.
JERD-545 The ESPC shall monitor performance, for all systems providing JPSS
functionality, including but not limited to: data availability, data integrity,
resource utilization, storage system I/O operations, communications, data latency.
JERD-547 The ESPC shall make data integrity status available to operators.
Rationale: Users must know system functioning status (up or down ) and what
mode system is operating in (open or restricted). Data integrity provides a
measure of data received against the data that was stored and delivered.
3.1.3.3 Data Reporting
JERD-112 The NESDIS ESPC shall make JPSS data availability and JPSS latency
information accessible to the designated authority for queries and report
generation.
3.1.4 Capacity, Margin and Scalability
JERD-114 The NESDIS ESPC shall have sufficient capacity to ingest either S-NPP, JPSS-1,
and GCOM-W or JPSS-1, JPSS-2, and GCOM-W missions data streams (as
specified in Appendix A).
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-10-
JERD-115 The NESDIS ESPC shall have sufficient capacity for data product generation of
two JPSS missions (S-NPP and JPSS-1, or JPSS-1 and JPSS-2), and GCOM-W
missions data (as specified in Appendix A).
JERD-116 The NESDIS ESPC shall have sufficient capacity for product distribution of two
JPSS missions (S-NPP and JPSS-1, or JPSS-1 and JPSS-2), and GCOM-W
missions data streams (as specified in Appendix A).
JERD-548 The NESDIS ESPC shall be sized to support product output volumes of 25.9
terabytes of JPSS data per day.
JERD-549 The NESDIS ESPC shall be capable of supporting ingress volumes of 6 terabytes
of JPSS data per day.
JERD-550 The NESDIS ESPC shall be capable of supporting 100 JPSS concurrent ad-hoc
transfers.
JERD-551 The NESDIS ESPC shall be capable of supporting 200 JPSS concurrent transfers.
JERD-552 The NESDIS ESPC shall be sized to support a maximum ingress bit rate of 3.5
Gbps of JPSS data.
JERD-555 The NESDIS ESPC shall be sized to support an egress bit-rate of 22.9 Gbps of
JPSS data.
Rationale: PDA CDR design allocates 22.9 Gbps for JPSS data.
JERD-556 The NESDIS ESPC shall support a JPSS to ESPC ingress peak file access rate of
40 JPSS files/second.
3.1.5 Margin
JERD-559 The NESDIS ESPC architecture shall be flexible enough to accommodate 100%
CPU and memory growth without necessitating a redesign of the system for any
new functionality added to ESPC in support of JPSS.
Rationale: This applies to new acquisitions in support of JPSS.
3.1.6 Utilization
3.1.6.1 Computer Processing
JERD-119 The NESDIS ESPC shall have sufficient computer processing such that Central
Processing Unit utilization does not exceed 70%, averaged daily.
3.1.6.2 Computer Memory
JERD-121 The NESDIS ESPC shall have sufficient computer memory such that the
computer memory utilization does not exceed 50%, averaged daily.
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-11-
Rationale: The ESPC functionality supports legacy POES and GOES operations
and will support future GOES-R and JPSS missions. This requirement is limited
to the functionality supporting JPSS.
3.1.6.3 Reserve Capacity
JERD-123 The NESDIS ESPC shall provide 50% margin on all system resources, including
processing, storage, and throughput, under peak loading conditions.
3.1.7 Data Accounting
JERD-1745 The NESDIS ESPC shall be capable of receiving SMD accounting data from the
JPSS Ground System.
Rationale: Required by MMSS-433 (L1RDS-2282 for S-NPP and NOAA-20).
ESPC must read reconciliation reports.
JERD-1756 The NESDIS ESPC shall monitor the quality of the ESPC generated Products.
Rationale: Must monitor the quality of the NUPS.
JERD-1757 The NESDIS ESPC shall monitor the integrity of the input data it receives.
Rationale: NDE input data monitoring
3.1.7.1 Data Receipt Records
JERD-126 The NESDIS ESPC shall retain a listing of data received for no less than 30
consecutive calendar days.
3.1.7.2 Data Distribution Records
JERD-128 The NESDIS ESPC shall retain a listing of data distributed for no less than 90
consecutive calendar days.
3.1.7.3 Data Requests Records
JERD-130 The NESDIS ESPC shall retain a listing of data requested by users for no less
than 90 consecutive calendar days.
3.1.7.4 Data Storage
JERD-132 The NESDIS ESPC shall store all data products received from the JPSS Ground
System for a minimum of 4 days.
3.1.7.5 Independent Operations and Test and Integration Capability
JERD-1616 The NESDIS ESPC shall support software updates while satisfying all functional
and performance requirements.
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-12-
JERD-1584 The NESDIS ESPC shall prevent delivery of test data to the operational
environment.
Rationale: ESPC must Segregate test data from operational data
JERD-1585 The NESDIS ESPC shall provide the functionality to perform integration and
testing or maintenance without any impact to ongoing operations.
Rationale: The NESDIS ESPC is required to operate until 2025. Development
and integration and test activities cannot interrupt operations. Consequently
those activities, which are required for system evolution and maintenance, must
be performed during non-operational periods or on independent functional
capabilities isolated from the operational systems. This also applies to algorithm
development and maintenance.
3.1.7.6 Manage System Resources
JERD-1747 The NESDIS ESPC shall provide the capability for a designated authority to
manage system resources.
Rationale: The designated authority must be able to approve/disapprove
subscription requests and manage CPU throughput and margin.
JERD-1748 The NESDIS ESPC shall provide the capability to restrict access to data.
Rationale: The designated authority must be able to restrict access to data to
certain users not authorized to receive the data (i.e. GCOM data restriction must
comply with the NOAA / JAXA MOU agreements.
3.2 Ingest
JERD-1749 The NESDIS ESPC shall ingest data from the JPSS Ground System in
compressed format as documented in JPSS GS to NESDIS ESPC IRD.
Rationale: The compression format to be used is still TBD. However, NDE must
be able to ingest the data in compressed format.
3.3 Product Generation
Data Products and their Performance Attributes
JERD-1750 The NESDIS ESPC shall be capable of processing data from the JPSS Ground
System received in compressed format as documented in JPSS GS to NESDIS
ESPC IRD.
Rationale: The compression format to be used is still TBD. However, NDE must
be able to ingest the data in compressed format and manipulate the data.
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-13-
JERD-144 The NESDIS ESPC shall generate JPSS data products in accordance with
Appendix A only for those products annotated as "ESPC Product Generation."
Rationale: ESPC is only required to generate the products annotated as "ESPC
Product Generation."
3.3.1 Science Product Performance
3.3.1.1 Normal Conditions
JERD-148 All raw and sensor data available from the JPSS Ground System shall be made
available by ESPC regardless of whether or not EDR Degradation and Exclusion
Conditions apply.
3.3.1.2 Degraded Conditions
A useful product can be achieved under other conditions that are not specified in the L1RD, but
needs to be part of the calibration and validation process.
JERD-155 The NESDIS ESPC shall have the capability to provide quality flags as generated
by algorithms.
3.3.1.3 Ancillary Data
JERD-162 The NESDIS ESPC shall make available to the JPSS Ground System (GS)
ancillary data as specified in Table A.
3.3.2 Produce Data Sets
Note:
S-NPP and J-n will comprise a constellation in 1330 LTAN with minimum orbital separation
between satellites. For JPSS managed satellites (S-NPP, J-1 or J-2), when the same sensors are
flying on multiple satellites in the same orbit, one set of sensors are identified to be the primary
mission sensors; the other sensors are designated secondary mission sensors. The primary
mission sensors can reside on different spacecraft. In the case of the failure of a sensor, the
sensor does not get turned off if it is at least marginally operational. The sensors from which the
operational EDRs are produced are referred to as primary sensors. There is only one set of
operational EDRs to which the data availability and latency requirements apply. OSPO is
responsible for identifying the operational EDR set based on Cal/Val recommendations.
JERD-169 The ESPC shall make available one complete set (primary set) of data products
identified in Appendix A from the science data acquired from the JPSS GS.
Rationale: The JPSS GS will produce one complete set from primary mission
sensors and additional data sets from additional mission sensors are produced
and delivered by JPSS GS on a best effort basis.
The ESPC must generate one complete set to which the latency requirements apply. The ESPC
is also required to pass through, or reformat the additional secondary set.
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-14-
JERD-172 The ESPC shall make available any additional product sets as specified in
Appendix A, that originated from secondary mission sensors to ESPC Registered
Users.
3.4 Distribution
JERD-174 The NESDIS ESPC shall make available ancillary data in accordance with Table
A to JPSS service delivery points at the primary (NSOF) and alternate
(Consolidated Back Up (CBU)) processing centers.
JERD-176 The NESDIS ESPC shall make available all products identified in Appendix A as
"ESPC Product Generation" to CLASS.
JERD-180 The NESDIS ESPC shall deliver to NWS the data products identified in JERD
Appendix A that are designated to go to NWS (S-NPP and NOAA-20 legacy
parent requirements designating NWS receipt are contained in the L1RD
Supplement Tables 2.2 and 2.3.)
JERD-2542 The NESDIS ESPC shall provide the capability to make select JPSS products
ready for GTS dissemination.
[GTS ready means insertion/pre-pending of an approved WMO header and
additional routing information to an existing product; NWS manages the U.S.
GTS interface and they have the primary responsibility of disseminating products
onto GTS circuits since the NWS is designated as a Regional Telecommunications
Hub (RTH) as accorded by the WMO governing body. Capability to handle
incrementing of the WMO headers may be necessary to ensure each file is
uniquely identified since the date-time group portion of the WMO header is
DDHHMM to ensure many file received/processed at the same time are clearly
delineated]
Table A. Table of Ancillary Data
Ancillary Data Source Destination Frequency Size Format Fields NCEP Global
Forecast system
(GFS)
NCEP IDPS Every 6
hours ~33MB/~18MB -
~66MB grib1/grib2 3-hr and 6-hr
forecasts
Polar Wander USNO IDPS Weekly 2 MB ASCII Earth Orientation
Finals2000A.all Navy Global
Environmental
Model
(NAVGEM)
FNMOC IDPS Every 6
hours 12 MB GRIB2 3, 6, 9, 12, 15, 18,
21, and 24-hr
forecasts
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-15-
Navy Aerosol
Analysis And
Prediction System
(NAAPS)
FNMOC IDPS Every 6
hours 425 KB GRIB2 3, 6, 9, 12, 15, 18,
21, and 24-hr
forecasts
Leap Second
Updates USNO IDPS Daily 2.1 KB ASCII Available very
infrequently, but
pull daily Daily Solar Data
(DSD) indices SWPC IDPS/SOC Daily 6.5 KB ASCII Space Weather
Predictions Daily
Geomagnetic Data
(DGD) indices
SWPC IDPS/SOC Daily 6.5 KB ASCII Space Weather
Predictions
45-Day AP and
F10.7cm Flux
Forecast
SWPC IDPS/SOC Daily 6.5 KB ASCII Space Weather
Predictions
Global
Multisensor
Automated
Snow/Ice
(GMASI) Product
OSPO IDPS Daily ~19.3 MB each
(Structure stored
within HDF5)
Binary 0-3, 20,21, 200, as
follows: 0: Open water, no
ice 1: Land (no snow)
2: Snow (over
land) 3: Ice (over water)
20: Open water
(no-ice
masked
region) 21: Land (no-ice
masked
region) 200: Fill
Table B. Recommended Minimum Product Suite for GTS Routing Consideration
Products for GTS
ATMS TDRs/SDRs (all channels) - BUFR
CrIS SDRs (channel subset optimized for NWP) - BUFR
VIIRS Polar Winds (NHEMI & SHEMI) EDRs - BUFR
3.5 System Performance
3.5.1 Data Latency and Product Recipients
JERD-259 The NESDIS ESPC shall meet ESPC pass through, Product Generation,
reformatting times as specified in Appendix A. (See Waiver on page xv)
JERD-260 The NESDIS ESPC shall either deliver or make available the products identified
in Appendix A to ESPC Registered Users. (S-NPP and NOAA-20 legacy parent
requirements on data product recipients are contained in the JPSS L1RD
Supplement Tables 2.2 and 2.3.)
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-16-
Rationale: Required by MMSS-284, MMSS-476, MMSS-475, MMSS-562, and
MMSS-563; and MMSS Tables A-8 and A-9. For requirements verification
purposes, ESPC Registered Users include, at a minimum, the National
Environmental Satellite, Data, and Information Service (NESDIS), the National
Marine Fisherues Service (NMFS), the National Ocean Service (NOS), the
National Weather Service (NWS), the Air Force Weather Agency (AFWA), and
the European Organisation for the Exploitation of Meteorological Satellites
(EUMETSAT). This requirement applies to only the primary and secondary
product sets at the NSOF; it applies to only the primary and secondary product
set at the APC. For ESPC, a Registered User has a formal agreement with the
NESDIS Office of Satellite and Product Operations (OSPO), via the ESPC Data
Access form, for the acquisition of data products.
3.5.2 Data Availability
Reserved
3.5.3 User Services
JERD-264 The NESDIS ESPC shall provide a user interface that supports search, order, and
subscription management services.
JERD-265 The NESDIS ESPC shall allow users to subscribe to a subset of JPSS products as
identified in Appendix A and Table A.
Rationale: Users need the option to request a subset of the products. A "subset"
means the user selected products they want ( i.e. manual requests configured by
the user.) Each user must be granted access to data IAW NESDIS policies and
data restrictions (i.e. MOU with JAXA restricts data rights to JAXA products).
JERD-266 The NESDIS ESPC shall be capable of fulfilling user data subscriptions and ad-
hoc orders.
Rationale: "Fulfilling" subscriptions and ad-hoc orders means the ESPC
responds to the data request and can get it to the ESPC system boundary. Fulfill
does not guarantee delivery due to Networks outside of ESPC control.
JERD-1595 The NESDIS ESPC shall be capable of notifying users of the status of their
orders.
3.5.4 System Availability
JERD-270 The NESDIS ESPC outages in support of JPSS functions shall be less than 5
hours over a 30day period.
3.5.5 Fault Tolerance
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-17-
JERD-274 The system shall have no single point of failure for ingest, product generation and
product distribution functionality.
Rationale: The intent is to meet this requirement by providing redundancy. This
redundancy will be implemented by adding COOP capabilities at CBU location.
The assumption is that ESPC as a high availability system, meeting it's
availability requirements combined with the COOP redundancy satisfies this
requirement.
3.6 Interface Requirements
JERD-1775 The NESDIS ESPC shall provide an interface between the system's distribution
capability (i.e. PDA) and external data consumers.
JERD-278 The NESDIS ESPC shall interface with the JPSS Ground System in accordance
with the Joint Polar Satellite System (JPSS) Ground System (GS) to National
Environmental Satellite, Data, and Information Service (NESDIS) Environmental
Satellite Processing Center (ESPC) Interface Requirements Document (IRD)
(document number 474-00303).
JERD-279 The NESDIS ESPC shall interface with the NOAA CLASS.
JERD-283 The NESDIS ESPC shall interface with the National Weather Service (NWS).
3.7 Security
See JPSS L1RD-F
Any security requirements contained in this section are in addition to those already levied by the
L1RD-F. Most of the security requirements are contained in L1RD-F, which is an applicable
document, and therefore are not being repeated in this section.
JERD-1751 The NEDSIS ESPC shall ensure that system status is available only to those
authorized to have access.
Rationale: There are two types of system status: 1. System status for registered
users and 2. System status for designated authorities. A user cannot have access
nor receive what is authorized for designated authorities only.
3.8 Continuity of Operations
Continuity of Operations (COOP) requires designated national assets to remain
operational in the event of regional conditions that can impact primary resources (e.g.,
natural disasters, infrastructure outages, etc.). NOAA COOP plans ensure the continuance
of mission essential functions at an alternate facility in the event of a COOP incident.
NOAA has chosen Fairmont, WV as the JPSS COOP site.
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-18-
JERD-1596 The NESDIS ESPC shall deploy an alternate Data Processing Center as part of
the CBU capability to fulfill Continuity of Operations (COOP) that at a minimum
produces the following products:
AMSR-2/3 Calibrated Sensor Data
Green Vegetation Fraction (VIIRS)
Ocean Color (VIIRS)
Polar Winds (VIIRS)
AMSR-2/3 SST
VIIRS SST
Land Surface Emissivity (ATMS)
JERD-1776 The NESDIS ESPC shall as part of the CBU capability to fulfill Continuity of
Operations (COOP) be capable of distributing the minimum set of data products
in accordance with the JERD Appendix A designated for APC distribution.
JERD-293 The NESDIS ESPC alternate distribution center shall deliver data to the CLASS
Point of Presence (PoP) at the Consolidated Back Up (CBU).
JERD-294 The ESPC shall transition full operations between the COOP and primary
facilities in less than 12 hours.
Rationale: The system must be able to switch to the COOP location and back to
Primary for operations within the specified time period (12 hours). This implies
the system is fully synchronized prior to the transition between locations.
JERD-295 The NESDIS ESPC shall support operations out of the COOP facility for at least
30 consecutive days during each COOP event.
Rationale: The 30-day definition of a long term deployment is consistent with
National-level guidance requiring a 30-day operational capability at remote
backup sites.
JERD-1602 The NESDIS ESPC alternate processing center shall be capable of being remotely
configurable from the primary data processing center at NSOF.
JERD-1603 The NESDIS ESPC alternate processing center shall be capable of being
remotely-operable from the primary data processing center at NSOF.
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-19-
4 Appendix A JPSS Data Products (referenced in section 3.3)
Product/Parameter Products designated for APC
distribution Latency Allocated To ESPC
(Threshold)
AMSR-2/3 Instrument AMSR-2/3 ASD X
ESPC Pass-through 3 minutes
AMSR-2/3 Calibrated Sensor Data X ESPC Product Generation 16 minutes
ESPC Reformatting 7 minutes
ATMS Instrument
ATMS SDR X ESPC Pass-through 3 minutes
ESPC Reformatting 7 minutes
ATMS TDR X ESPC Pass-through 3 minutes
ESPC Reformatting 7 minutes
CERES Instrument
CERES RDR X ESPC Pass-through 3 minutes
CrIS Instrument CrIS SDR X
ESPC Pass-through 3 minutes
ESPC Reformatting 7 minutes
OMPS Instruments OMPS-N SDR X
ESPC Pass-through 3 minutes
VIIRS Instrument SDR X
ESPC Pass-through 3 minutes ESPC Reformatting 7 minutes
Active Fires (VIIRS) ESPC Product Generation 16 minutes
Aerosol Detection (VIIRS) ESPC Product Generation 16 minutes
Aerosol Optical Depth (VIIRS)
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-20-
ESPC Product Generation 16 minutes
Aerosol Particle Size (VIIRS)
ESPC Product Generation 16 minutes
Albedo (Surface) (VIIRS) ESPC Product Generation 16 minutes
Annual Surface Type (VIIRS)
ESPC Product Generation 16 minutes
Atmospheric Vertical Moisture Profile
(CrIS/ATMS)
ESPC Product Generation 16 minutes
Atmospheric Vertical Temperature Profile
(CrIS/ATMS)
ESPC Product Generation 16 minutes
ESPC Pass-through
Carbon Monoxide (CO)(CrIS) ESPC Product Generation 16 minutes
Carbon Dioxide (CO2)(CrIS)
ESPC Product Generation 16 minutes
Cloud Cover/Layers (VIIRS)
ESPC Product Generation 16 minutes
Cloud Height (Top and Base)(VIIRS)
ESPC Product Generation 16 minutes
Cloud Particle Size (VIIRS) ESPC Product Generation 16 minutes
Cloud Liquid Water (AMSR-2/3)
ESPC Product Generation 16 minutes
Cloud Liquid Water (ATMS)
ESPC Product Generation 16 minutes
ESPC Reformatting 7 minutes
Cloud Mask (VIIRS)
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-21-
ESPC Product Generation 16 minutes
Cloud Optical Depth (VIIRS)
ESPC Product Generation 16 minutes
Cloud Phase (VIIRS)
ESPC Product Generation 16 minutes
Cloud Top Pressure (VIIRS)
ESPC Product Generation 16 minutes
Cloud Top Temperature (VIIRS)
ESPC Product Generation 16 minutes
Green Vegetation Fraction (VIIRS) X
ESPC Product Generation 24 hours
ESPC Reformatting 7 minutes
Ice Age/Thickness (VIIRS)
ESPC Product Generation 16 minutes
Ice Concentration (VIIRS) ESPC Product Generation 16 minutes
Ice Surface Temperature (VIIRS) ESPC Product Generation 16 minutes
Imagery (AMSR-2/3) ESPC Product Generation 16 minutes
Imagery (ATMS) ESPC Product Generation 16 minutes
Imagery (VIIRS) X ESPC Pass-through 3 minutes
ESPC Reformatting 7 minutes
Infrared Ozone Profile (CrIS)
ESPC Product Generation 16 minutes
Land Surface Emissivity (ATMS) X
ESPC Product Generation 16 minutes
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-22-
Land Surface Temperature (ATMS) ESPC Product Generation 16 minutes
Land Surface Temperature (VIIRS)
ESPC Product Generation 16 minutes
Methane (CH4)(CrIS)
ESPC Product Generation 16 minutes
Moisture Profile (ATMS)
ESPC Product Generation 16 minutes
Ocean Color/Chlorophyll (VIIRS) X
ESPC Product Generation 31 minutes
OMPS Instruments
OMPS-L SDR
ESPC Product Generation 16 minutes
ESPC Reformatting 7 minutes
OMPS Limb Profile (OMPS-L)
ESPC Product Generation 16 minutes
ESPC Reformatting 7 minutes
Outgoing Longwave Radiation (CrIS)
ESPC Product Generation 16 minutes
Ozone Nadir Profile (OMPS-N) X
ESPC Product Generation 16 minutes
ESPC Reformatting 7 minutes
Ozone Total Column (OMPS-N) X
ESPC Product Generation 16 minutes
ESPC Reformatting 7 minutes
Polar Winds (VIIRS) X
ESPC Product Generation 117 minutes
ESPC Reformatting 7 minutes
Precipitation (Type/Rate) (AMSR-2/3) ESPC Product Generation 16 minutes
Rainfall Rate (ATMS)
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-23-
ESPC Product Generation 16 minutes
Sea Ice Characterization (AMSR-2/3)
ESPC Product Generation 16 minutes
Sea Ice Concentration (ATMS)
ESPC Product Generation 16 minutes
Sea Surface Temperature (AMSR-2/3) X
ESPC Product Generation 16 minutes
ESPC Reformatting 7 minutes
Sea Surface Temperature (VIIRS) X
ESPC Product Generation 16 minutes
ESPC Reformatting 7 minutes
Sea Surface Wind Speed (AMSR-2/3)
ESPC Product Generation 16 minutes
Snow Cover/Depth (AMSR-2/3) ESPC Product Generation 16 minutes
Snow Cover (ATMS)
ESPC Product Generation 16 minutes
Snow Cover (VIIRS)
ESPC Product Generation 16 minutes
Snowfall Rate (ATMS)
ESPC Product Generation 16 minutes
Snow Water Equivalent (ATMS)
ESPC Product Generation 16 minutes
ESPC Reformatting 7 minutes
Snow Water Equivalent (AMSR-2/3)
ESPC Product Generation 16 minutes
Soil Moisture (AMSR-2/3)
ESPC Product Generation 16 minutes
Surface Reflectance (VIIRS)
ESPC Product Generation 16 minutes
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-24-
Temperature Profile (ATMS)
ESPC Product Generation 16 minutes
Total Precipitable Water (AMSR-2/3)
ESPC Product Generation 16 minutes
Total Precipitable Water (ATMS) ESPC Product Generation 16 minutes
ESPC Reformatting 7 minutes
Vegetation Indices – Daily (VIIRS)
ESPC Product Generation 24 hrs
ESPC Reformatting 7 minutes
Vegetation Indices – Weekly (VIIRS)
ESPC Product Generation 24 hrs
ESPC Reformatting 7 minutes
Vegetation Indices – Bi-Weekly (VIIRS)
ESPC Product Generation 24 hrs
ESPC Reformatting 7 minutes
Vegetation Health Index Suite (VIIRS)
ESPC Product Generation 174 hr (1 week+ 6 hr)
Volcanic Ash Detection and Height
(VIIRS)
ESPC Product Generation 16 minutes
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-25-
5 Appendix B Acronyms
AFWA Air Force Weather Agency AMSR Advanced Microwave Scanning Radiometer APC Alternate Processing Center ASD AMSR2 APID Sorted Data
ATMS Advanced Technology Microwave Sounder C3 Command, Control and Communications
CCB Configuration Control Board CERES Clouds and the Earth’s Radiant Energy System
CDR Climate Data Record CLASS Comprehensive Large Array-Data Stewardship System CORL Consolidated Observing Requirements List
CrIMSS Cross-track Infrared and Microwave Sounder Suite CrIS Cross-track Infrared Sounder DOC U.S. Department of Commerce DoD Department of Defense
DUS/O Deputy Under Secretary of Commerce for Oceans and Atmosphere for Operations EDR Environmental Data Record EOS NASA Earth Observing System
ESPC Environmental Satellite Processing Center FNMOC Fleet Numerical Meteorology and Oceanography Center
FT Field Terminal GCOM Global Change Observation Mission
GCOM-W GCOM-Water GTS Global Telecommunications System
HSPD Homeland Security Presidential Directive JAXA Japanese Aerospace Exploration Agency JPSS Joint Polar Satellite System KPP Key Performance Parameter
L1RD Level 1 Requirements Document L1RD-F Level 1 Requirements Document - Final
LEO Low-Earth orbiting or orbit MOU Memorandum of Understanding NAO NOAA Administrative Order
NASA National Aeronautics and Space Administration NAVO Naval Oceanographic Office
NESDIS NOAA Satellite and Information Service NIST National Institute of Standards and Technology NJO NOAA JPSS Office
NOAA National Oceanic and Atmospheric Administration NPD NASA Policy Directive NPP National Polar-orbiting Partnership NPR NASA Procedural Requirement
NSOF NOAA Satellite Operations Facility NSPD National Security Presidential Directive NWS National Weather Service
OMPS Ozone Mapping and Profiler Suite PID Program Implementation Document
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-26-
RBI Radiation Budget Instrument RDR Raw Data Record SDR Sensor Data Record SDS Science Data Segment SN NASA Space Network
S-NPP Suomi NPP SS Space System
STAR NOAA’s Center for Satellite Applications and Research TDR Temperature Data Record
TDRSS Tracking and Data Relay Satellite System USAF United States Air Force VIIRS Visible Infrared Imager/ Radiometer Suite WMO World Meteorological Organization
xDR Data Record
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-27-
6 Appendix C Glossary
Ad Hoc Orders: One-time user request for data. Can also be thought of as a subscription order
with a very short subscription period
Application Packet (AP): The unit of data created by a spacecraft or a spacecraft sensor
according to CCSDS standards. An Application Packet contains a primary header and an
optional secondary header.
ATMS and CrIS: The Cross-track Infrared Sounder (CrIS) combined with the Advanced
Technology Microwave Sounder (ATMS) globally produces atmospheric temperature, moisture
and pressure profiles from space. The combined ATMS/CrIS sensor suite is called the Cross-
track Infrared and Microwave Sounder Suite (CrIMSS).
CERES and CERES Follow-on: The Clouds and the Earth's Radiant Energy System. Part of
NASA's EOS, CERES products include both solar-reflected and Earth-emitted radiation from the
top of the atmosphere to the Earth's surface. Cloud properties are determined using simultaneous
measurements by other EOS instruments such as the Moderate Resolution Imaging
Spectroradiometer (MODIS).
Comprehensive Large Array-data Stewardship System (CLASS): CLASS is an IT system
that supports the NOAA Data Center's mission to archive data and other artifacts from its polar
and geostationary satellites and from in situ sources.
Climate Data Record (CDR): A CDR is a time series of measurements (e.g., sea surface
temperature) of sufficient length, consistency, and continuity to determine climate variability and
change [National Research Council, 2004]. In practice, NOAA will use JPSS data together with
heritage and other data sets to provide climate records typically covering multiple decades in
time.
Data: A discrete set of logical records containing information in a digital format that includes,
but is not limited to, Level 1b, Level 2 and higher Level products created by operational systems,
subsets and aggregates of operational products, as well as ancillary data, instrument calibration
data and spacecraft navigation data.
Data Aggregation: The stitching together of granules into a single file.
Data Availability: Data Availability is the percentage of data collected by operational sensors
on each JPSS satellite that is delivered to the JPSS distribution system. Data availability is
calculated on a 30 day basis.
Data Catalog: A listing of all the data, and any associated attributes, in the system at any given
time.
Data Integrity: refers to the protection of information from revision, to ensure that the
information is not compromised through corruption. A measure of data received against the data
that was stored and delivered. Good data integrity ensures that no software, hardware, network
problem or human intervention compromised the data.
Data Inventory: A listing of all data items and any associated attributes, in the system at any
given time.
Data Item: An instance of data that is independently managed (described, inventoried, and
retrieved).
Data Latency: ESPC Generation latency is defined as the period of time starting when the ESPC
receives the input data and ending with delivery to the user interface, including the ESPC
processing time and making the data available to the end user interface. Latency times are for
granule generation. The latency times to generate regional, orbital and global products will be
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-28-
longer. Latency times do not include distribution time to users who retrieve their products from
CLASS.
Data Quality: The accuracy and correctness of the content and meaning of the data.
Data Receipt: Last bit of incoming data has been received at the system receive point, and for
data that arrives directly at PDA from a source outside of ESPC security boundaries, a virus scan
has completed.
Data Server: Source of data that is to be distributed.
Data Set: A logical grouping of data sharing a common attribute, such as data source or data
type.
Data Type: A specific category of data with common characteristics.
Delivery Timeliness: A threshold of time specified within a subscription that defines how
recently the data needs to have been created in order to be delivered to the user. Delivery
Timeliness is meant to prevent the transfer of data that is not useful to a user due to the age of the
data.
Designated Authority: Persons responsible for the overall status and operation of the system.
Development: The creation of a new system, or the system modifications necessary to add
completely new functionality to an existing baseline system to comply with mission
requirements. It includes the testing, fielding, and verification of these new capabilities (with
support from the receiving organization at the installation site.)
Environmental Data: Environmental data as used in this document is also termed mission data
and refers to all data (atmospheric, oceanographic, terrestrial, space environmental and climatic)
being sensed and collected by the spacecraft.
Environmental Data Record (EDR): Data record produced when an algorithm is used to
convert Sensor or Temperature Data Records (SDRs, TDRs) to geolocated geophysical
parameters (including ancillary parameters, e.g., cloud cleared radiation, etc.).
Registered User: Authorized users who have a formal agreement with OSPO, via the ESPC
Data Access form, for acquisition of data products.
Ingest History: Record of data received by the system.
Interface Data Processing System (IDPS): The IDPS is a subsystem of the NESDIS ESPC
that receives raw data the polar satellites and processes these data into RDRs, SDRs, TDRs and
EDRs and makes these products available to the user community.
Imagery: Two-dimensional array of numbers, in digital format, each representing the brightness
of a small elemental area.
Key Mission Sensor: A Primary Mission Sensor which provides data to meet JPSS mission
success criteria, e.g., ATMS, CrIS or VIIRS.
Key Performance Parameter: A parameter so significant to the user community that all
designated requirements must be met to achieve minimal mission success.
Mission Sensors: Any sensor on the spacecraft directly used to satisfy any of the environmental
data requirements.
Objective: Objectives represent an improved performance level above and beyond the threshold
requirements that would better meet user needs and which are realistically achievable with
current technology.
OMPS: Ozone Mapping and Profiler Suite collects data to permit the calculation of the vertical
and horizontal distribution of ozone in the Earth's atmosphere. OMPS consists of separate nadir
and limb sensors. The OMPS Nadir sensor consists of Mapper and Profiler components.
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-29-
Operational Availability (Ao): The measure of the probability that a system is operationally
capable (ready for tasking) of performing an assigned mission (e.g., delivering a KPP) at any
given time. Once on orbit, the JPSS satellites are assumed to operate 24/7, 365 days per year for
the mission lifetime. The availability criteria include system reliability (besides the satellite
reliability which is specified separately), redundancy, and planned outages (downtime for
spacecraft maneuvers and calibration and ground system sustainment).
Operational Satellite: A spacecraft containing an operational sensor/instrument that is
providing useful data to meet or supplement one or more of the JPSS observational data or
service requirements.
Operations: The staff necessary to operate a system and the recurring costs necessary to keep
the operation active (for example, facilities, networks, utilities, software licensing, and hardware
maintenance).
Payload: Mission sensors and on-board processor.
Peak loading: Peak loading includes data flows for ingress and egress data, as well as all intra-
system flows that move data from the NAS to the various services (integrity check, metadata
parse, virus scan, deflation, tailoring, etc.) and includes processing required for product
generation in a worst-case simultaneous data arrival.
Primary Mission Sensor: A sensor on any of the NPP, or JPSS operational satellites which is
used as the primary source of essential data needed to satisfy a specific set of environmental data
requirements. Normally this is the most capable sensor of its type in the constellation.
Probability of Success (Ps): The probability that an outcome is in fact the expected or desired
outcome. For example, if a trial must result in any of (s+f) equally likely ways, where s is the
number of successful ways and f is the number of failing ways, then the probability of success is
Ps = s/(s+f).
Raw Data Record (RDR): Full resolution digital sensor data, time referenced and earth located,
with absolute radiometric and geometric calibration coefficients available, but not applied, to the
data. Aggregates (sums or weighted averages) of detector samples are considered to be full
resolution data if the aggregation is normally performed to meet resolution and other
requirements. Sensor data must be unprocessed with the following exceptions: time delay and
integration, detector array non-uniformity correction (i.e., offset and responsivity equalization),
and data compression are allowed. Lossy data compression is allowed only if the total
measurement error is dominated by error sources other than the data compression algorithm. All
calibration data will be retained and communicated to the ground without lossy compression.
Refresh: Refresh is the time interval between successive collections of measurements of the
same parameter from the same geographical point on, or above, the surface of the earth.
SARSAT: The Search and Rescue Satellite Aided Tracking system (SARSAT) uses NOAA
satellites in low-Earth and geostationary orbits to detect and locate aviators, mariners, and land-
based users in distress. The satellites relay distress signals from emergency beacons to a network
of ground stations and ultimately to the U.S. Mission Control Center (USMCC) in Suitland,
Maryland as well as foreign MCCs. The MCCs process the data and distribute alerts the
appropriate search and rescue authorities.
Scalability: The ability of a hardware or software system to continue to function according to
original specifications when it is enlarged (e.g., in terms of processing, storage, or throughput
capacity) and to take performance advantage of the increase.
Secondary Mission Sensor: A sensor on any of the NPP, or JPSS operational satellites which is
still functioning but is not used as the primary source of data to satisfy a specific set of
JPSS NESDIS ESPC Requirements Document JPSS-REQ-1003
Effective Date Aug 23, 2018
Version –3.2
-30-
environmental data requirements. Normally this sensor has some degraded capability but some
data from the sensor will be processed on the ground on a best effort basis to supplement the
primary source to increase temporal or spatial coverage.
Sensor Data Record (SDR): Data record produced when an algorithm is used to convert Raw
Data Records (RDRs) to geolocated calibrated brightness temperatures, radiances, or reflectances
with associated ephemeris data.
Service Delivery Point: The functional location or locations where the JPSS must provide data
or services.
Space System: The spacecraft including its associated sensors, subsystems, equipment, and
processors.
State of Health: A summary status point for an entire device and/or defined group of devices.
Sustainment: The work required to keep a baseline system architecture functioning as
technology and security requirements evolve, and the effort necessary to fix problems identified
in the system during operations. System refresh as required.
System Status for Designated Authorities - refers to system performance (e.g., resource
utilization, storage system I/O operations), communications, data availability, data integrity,
product latencies, and hardware and software anomaly information.
System Status for Registered Users – refers to up-down status of system functionality and
mode of operation.
Threshold: Threshold requirements represent the minimally acceptable level of performance
that must be achieved.
Temperature Data Records (TDRs): Data records that are geolocated antenna temperatures
with all relevant calibration data counts and ephemeris data to revert from T-sub-a into counts.
The existence of the SDRs provides reversible data tracking back from the EDRs to the Raw
data.
User Interface: The system/subsystem within the ESPC with which the end user interacts to
acquire data.
VIIRS: The Visible Infrared Imager/Radiometer Suite collects visible and infrared radiometric
data of the Earth's atmosphere, ocean, and land surfaces. Data types include atmospheric
parameters, clouds, Earth radiation budget, land/water and sea surface temperature, ocean color,
and low light imagery.