The ESDIS Project manages EOSDIS interfaces between system components through the use of interface documentation. These documents include management level documents such as Working Agreements and Inter-Project Agreements and technical documents such as Requirements Documents and Interface Control Documents.
The following diagrams have links to example documents that the ESDIS Project uses to control the interfaces. More than one document may describe an interface. The sample documents presented here draw mostly from the ICESat-I mission.
Click on a link to see an example document that ESDIS uses to control the interface between two system components Print all rollover information
Updated 10/25/2011
Agreements between ESDIS and projects not managed by ESDIS. Generally, the projects involved agree on an exchange of support services and data. From the interface control viewpoint, these agreements identify the need for an interface and the scope of the interface.
Phase:
A
Life Cycle Review:
Pre-SRR
EOSDIS Example
Inter-project Agreement (IPA) between the NASA QuikSCAT Scatterometer Project and the Earth Science Data and Information System (ESDIS) Project for Science Data Archive and Distribution Support, 423-10-38
ICDs are used to record design agreements for the interfaces between participating organizations. ICDs provide a means to evaluate and control all mutually interdependent and/or interacting design parameters of the interface
Phase:
B/C
Life Cycle Review:
PDR/CDR
EOSDIS Example
EOS PM-1 Spacecraft to EOS Ground System Interface Control Document, 422-11-19-03
A W/A outlines the working commitments made between the ESDIS Project and another organization for developing, implementing and/or operating portions of the data system.
Phase:
A
Life Cycle Review
Pre-SRR
EOSDIS Example
Working Agreement between the ESDIS Project and the MOPITT Principal Investigator for Standard Data Production Using the NCAR Science Investigator-lead Processing System (SIPS), 423-10-55
DMRs include Mission-Specific Requirements Documents (MSRDs) and mission requirement documents (e.g., Ground System Requirements Documents (GSRDs), and Mission Operations Requirements Documents (MORDs)). DMRs contain the results of the requirements identification and derivation activities and provide the basis for system design for individual missions.
Phase:
A
Life Cycle Review
SRR
EOSDIS Example
Aura Mission Specific Requirements Document, 423-10-47
ICDs are used to record design agreements for the interfaces between participating organizations. ICDs provide a means to evaluate and control all mutually interdependent and/or interacting design parameters of the interface
Phase:
B
Life Cycle Review
PDR/CDR
EOSDIS Example
Radio Frequency interface Control Document Between the EOS-PM-1 Spacecraft and the Spaceflight Tracking and Data Network, 450-RFICD-EOS PM-1/STDN
An ATBD describes the physical and mathematical description of the algorithms to be used in the generation of data products. It includes a description of variance and uncertainty estimates and considerations of calibration and validation, exception control, and diagnostics. In some cases, internal and external data product flows are required.
Phase:
B
Life Cycle Review
PDR
EOSDIS Example
EOS/AMSR RAINFALL, Algorithm Theoretical Basis Document Thomas Wilheit, Christian Kummerow, Ralph Ferraro May 1999
ICDs are used to record design agreements for the interfaces between participating organizations. ICDs provide a means to evaluate and control all mutually interdependent and/or interacting design parameters of the interface
Phase:
B/C
Life Cycle Review
PDR/CDR
EOSDIS Example
Interface Control Document Between the Earth Observing System (EOS) Data and Operations System (EDOS) and the TDRSS Ground Terminals (TGTs), 428-ICD-EDOS/TGT
ICDs are used to record design agreements for the interfaces between participating organizations. ICDs provide a means to evaluate and control all mutually interdependent and/or interacting design parameters of the interface
Phase:
B/C
Life Cycle Review
PDR/CDR
EOSDIS Example
Interface Control Document Between the Earth Observing System (EOS) Data and Operations System (EDOS) and the EOS Ground System (EGS) Elements, 428-ICD-EDOS/EGS
IRDs define the requirements for data exchanges across an interface between separately managed systems or subsystems. The requirements statements in IRDs are derived directly from project requirements documents.
Phase:
A
Life Cycle Review
MDR
EOSDIS Example
Interface Responsibilities for Standard Product Generation Using Science Investigator-led Processing Systems, 423-42-03
ICDs are used to record design agreements for the interfaces between participating organizations. ICDs provide a means to evaluate and control all mutually interdependent and/or interacting design parameters of the interface
Phase:
B/C
Life Cycle Review
PDR/CDR
EOSDIS Example
Interface Control Document between the Goddard Earth Sciences Data and Information Services Center (GES DISC) Simple, Scalable Script-based Science Processor Archive (S4PA) and the Science System Element (SSE) Interface Mechanisms, 423-44-01
Operations Agreements are even lower level, more detailed interface documents that are created to help define the operations use of the interfaces, including such things as addresses, phone numbers, and names of responsible personnel. These documents are not intended for project-level development and control.
Phase:
D
Life Cycle Review
ORR
EOSDIS Example
Operations Agreement (OA) Between the Goddard Earth Sciences (GES) Data and Information Services Center (DISC) and the Ozone Monitoring Instrument (OMI) Science Investigator-led Processing System (SIPS), 610.2-GDISC-OP-OA.004
ICDs are used to record design agreements for the interfaces between participating organizations. ICDs provide a means to evaluate and control all mutually interdependent and/or interacting design parameters of the interface
Phase:
B/C
Life Cycle Review
PDR/CDR
EOSDIS Example
Interface Control Document Between the Earth Observing System (EOS) Data and Operations System (EDOS) and the EOS Ground System (EGS) Elements, 428-ICD-EDOS/EGS
ICDs are used to record design agreements for the interfaces between participating organizations. ICDs provide a means to evaluate and control all mutually interdependent and/or interacting design parameters of the interface
Phase:
B/C
Life Cycle Review
PDR/CDR
EOSDIS Example
Interface Control Document Between the Earth Observing System (EOS) Networks and the Earth Observing System Data and Information System (EOSDIS) Elements, 423-ICD-002
ICDs are used to record design agreements for the interfaces between participating organizations. ICDs provide a means to evaluate and control all mutually interdependent and/or interacting design parameters of the interface
Phase:
B/C
Life Cycle Review
PDR/CDR
EOSDIS Example
Interface Control Document between the ESDIS Metrics System (EMS) and the Data Providers, 423-47-01
ICDs are used to record design agreements for the interfaces between participating organizations. ICDs provide a means to evaluate and control all mutually interdependent and/or interacting design parameters of the interface
Phase:
B/C
Life Cycle Review
PDR/CDR
EOSDIS Example
Interface Control Document between EOSDIS Core System (ECS) and EOS Clearinghouse (ECHO) for Metadata Inventory and Ordering, 423-45-02
The MRT plan documents the strategy that will be used to verify and ensure that all system components working together meet design specifications and requirements for the mission.
Phase:
D
Life Cycle Review
TRR
EOSDIS Example
Earth Observing System (EOS) Aura Mission Readiness Test Plan (MRTP), ESDIS02760
Click on a link to see an example document that ESDIS uses to control the interface between two system components Print all rollover information
Updated 10/25/2011
EOSDIS Interface Document Acronyms
Type
Name
Purpose
W/A
Working Agreement
A W/A outlines the working commitments made between the ESDIS Project and another organization for developing, implementing and/or operating portions of the data system.
--
Project Plan
The Project Plan contains the technical approaches and management plans to implement the project requirements. It defines, at a high level, the scope of the project, the implementation approach, the environment within which the project operates, and the baseline commitments of the program and project. (from NPR 7120.5D)
DMR
Detailed Mission Requirements (DMRs)
DMRs include Mission-Specific Requirements Documents (MSRDs) and mission requirement documents (e.g., Ground System Requirements Documents (GSRDs), and Mission Operations Requirements Documents (MORDs)). DMRs contain the results of the requirements identification and derivation activities and provide the basis for system design for individual missions.
ATBD
Algorithm Theoretical Basis Document
An ATBD describes the physical and mathematical description of the algorithms to be used in the generation of data products. It includes a description of variance and uncertainty estimates and considerations of calibration and validation, exception control, and diagnostics. In some cases, internal and external data product flows are required.
ADURD
Archiving, Distribution and User Services Requirements in EOSDIS
This document provides generic requirements for data archiving, data distribution and user services for EOSDIS-supported data.
DFCD
Data Format Control Documents
Data Format Control Documents (DFCDs), and other data format documents (e.g., Data Format Requirements Documents (DFRDs)), define the formats of data units that are transferred across an interface and the control codes used in the data formats.
IRD
Interface Requirements Documents
IRDs define the requirements for data exchanges across an interface between separately managed systems or subsystems. The requirements statements in IRDs are derived directly from project requirements documents.
ICD
Interface Control Documents
ICDs are used to record design agreements for the interfaces between participating organizations. ICDs provide a means to evaluate and control all mutually interdependent and/or interacting design parameters of the interface
OA
Operations Agreements
Operations Agreements are even lower level, more detailed interface documents that are created to help define the operations use of the interfaces, including such things as addresses, phone numbers, and names of responsible personnel. These documents are not intended for project-level development and control.
MRT
Mission Readiness Test Plan
The MRT plan documents the strategy that will be used to verify and ensure that all system components working together meet design specifications and requirements for the mission.