EXHIBIT B - GLIMR DRL_DRD.pdf

Contract No. XXXXXXXXX Exhibit B – Data Requirements List/Data Requirements Description (DRL/DRD) (Version 0.1)

XXXXXXXXXX

EXHIBIT B

Data Requirements List (DRL) / Data

Requirements Description (DRD)

For

Geostationary Littoral Imaging and Monitoring Radiometer (GLIMR)

Access to Space (ATS)

Version 0.1

February 18, 2026

Document Change Record

Revision Date Description of Change

0.1 2/18/26 Initial version.

TABLE OF CONTENTS

1.0 INTRODUCTION

2.0 DEFINITIONS

3.0 DATA REQUIREMENTS LIST

4.0 DATA REQUIREMENTS DESCRIPTION (DRD)

4.1 REVIEW DRDS

ATS Requirements Review (ATSRR) GLIMR Spacecraft to GLIMR Payload Integration Review (ATSIR) GLIMR Observatory Test Readiness Review (ATSTRR) GLIMR Mission Operations Readiness Review (ATSORR) GLIMR Mission Post Launch Assessment Review (ASTPLAR) GLIMR Mission Decommissioning Review (ASTDR) GLIMR Payload Pre-Ship Review (PSR) GLIMR Extended Mission Review for Period 1 (EMR1) GLIMR Extended Mission Review for Period 2 (EMR2) GLIMR Mission Key Decision Point (KDP) E GLIMR Mission Key Decision Point (KDP) F

4.2 PROJECT MANAGEMENT DRDS

Monthly Project Status Report (MPSR) Security Requirements for Unclassified IT Resources Financial Reporting of NASA Property in the Custody of Contractors Subcontracting Reports Organizational Conflicts of Interest Plan

4.3 SAFETY AND MISSION ASSURANCE (S&MA) DRDS

ISO 9001 or AS9100 Compliance Documents: Quality Plan and Quality System Manual Reporting of Discrepancies Functional and Interface Failure Modes and Effects Analysis (FMEA)

4.4 TECHNICAL DRDS

Interface Control Documents (ICDs) Verification and Validation (V&V) Plan and Matrix Verification Reports GLIMR Spacecraft Thermal Analysis Report and Thermal Model Coupled Loads Analysis and Dynamics Environment Report GLIMR Payload to GLIMR Spacecraft Integration and Test Plan and Procedures Contamination Control Plan GLIMR Observatory Operations Plan GLIMR Mission Software Integration, Test Plan and Procedures Command and Telemetry Dictionary, Telemetry Calibration and Flight Rules

1.0 INTRODUCTION

This Data Requirements List (DRL) / Data Requirements Description (DRD) document defines the requirements for deliverable documentation to be provided by the Contractor. Section 2.0 includes definitions and instructions for delivery. Section 3.0 presents the DRL item by item, including due dates, quantity, and media format. Section 4.0 provides the DRD for each item listed in the DRL. Each DRD includes use and preparation information.

2.0 DEFINITIONS

Access to Space (ATS)

Contractor services required to integrate the GLIMR Payload onto the GLIMR spacecraft and place the Observatory into the specified GEO orbit and that will allow the Government to acquire the necessary scientific measurements (including transmission of this data to the GSDS) to assess rapidly evolving processes such as phytoplankton physiology and bloom evolution, episodic/seasonal river discharge, dissolved and particulate carbon transformations, and coastal storm damage.

Distributed Active Archive Center (DAAC)

The Government-assigned location(s) where GLIMR data and data products will be delivered by the GLIMR GSDS for public access and permanent archive.

GLIMR Ground Segment Provides the GLIMR Observatory command, control, and communication uplink and downlink, and data transfers from the GLIMR GMOC to the GLIMR GSDS.

GLIMR Ground Station Provides the GLIMR GMOC communications to and from the GLIMR Observatory.

GLIMR Mission

The entire GLIMR science mission performed by the Government and the Contractor. Includes the GLIMR Payload and Access to Space, data product generation, science results, and PI-led science community.

GLIMR Mission Operations Center

(GMOC)

Control center for uploading GLIMR Spacecraft and GLIMR Payload commands to the GLIMR Spacecraft and receiving GLIMR Spacecraft, GLIMR Payload, GLIMR science and housekeeping data from the GLIMR Spacecraft.

GLIMR Observatory The combination of the GLIMR Payload to the GLIMR Spacecraft.

GLIMR Payload

The Government-provided hardware that will be integrated into the GLIMR Spacecraft. The GLIMR Payload is a geostationary hyperspectral ocean color sensor capable of repeat coverage designed for the primary mission focus on ecosystem processes in the Gulf of America Includes all GLIMR Payload intra-connected cables and harnesses between the GLIMR Payload’s subsystems.

Does not include the Contractor-provided cables such as power, data, and communications to the GLIMR Payload-to-GLIMR Spacecraft interface.

GLIMR Science Data Segment

(GSDS)

The facility operated by the Government, located at NASA Goddard Space Flight Center, that receives GLIMR mission raw data (L0) from the GMOC to generate science products and deliver them to the GLIMR DAAC.

GLIMR Spacecraft

The vehicle with mechanical, electrical, and thermal interface for the GLIMR Payload to achieve the GLIMR mission. For the purposes of this effort, the GLIMR Payload may be hosted on a dedicated spacecraft or share the spacecraft with other payloads.

Interface Control Document (ICD)

Defines the interface between two systems (e.g., GLIMR Payload-to-GLIMR Spacecraft Mechanical and Thermal ICD; GLIMR Payload-to-GLIMR Spacecraft Electrical ICD; GLIMR GSDS-to-

GMOC ICD).

Launch Segment A rocket system including all necessary operations for launch to insert GLIMR Observatory from Earth’s surface into orbit.

Shall

Means the imperative. Compliance and formal traceability and verification by the Contractor is mandatory. Any deviations from these contractually imposed mandatory requirements require a formal change implemented through a written contract modification.

Will Designates the intent of NASA or the Government.

May Terms "may" or "can" denote discretionary privilege or permission.

2.1 DUE DATES/MATURITY – RELATED DEFINITIONS

The following definitions apply to the "DUE DATE, MATURITY.” Unless otherwise specified, deadlines are in calendar days.

(a) DUE DATE:

(1) DACA: (Calendar) Days After Contract Award.

(b) MATURITY:

(1) Draft: An early submission of an item. To be completed as is practicable at the time of preparation. Preliminary submittals are based on the best available current information and are resubmitted when required. Major changes are expected.

(2) Final: The submission of an item that, to the best of the Contractor’s knowledge and intention, will not require further revision or updates. However, this does not preclude later updates, if found that any of the contents are no longer accurate.

(3) Update: The item is revised with the best up-to-date information available at the time, as required. Updates require the same "approval/review/information" process as was required for the most recent submission. “Update” applies to all documentation.

2.2 MEDIA - RELATED DEFINITIONS

The following definition applies to the “MEDIA” column in Tables 3-1 through 3-4 of this document. If separate distribution instructions are not specified for separate submission due date/maturity items, then the listed distribution applies to all submissions.

E Electronic: The Contractor shall deliver data items to a Government specified web portal unless otherwise noted. The Contractor shall notify the Contracting Officer (CO) and Contracting Officer’s Representative (COR) of electronic submission of the data item via electronic mail. The Contractor shall provide electronic deliverables in the following standard electronic formats unless otherwise approved by the CO or COR:

• Text Documents: PDF (searchable) or Microsoft Word.

• Presentations: PDF (searchable) or Microsoft PowerPoint.

• Spreadsheets: Microsoft Excel.

• Database: Delimited ASCII (American Standard Code for Information Interchange) text files accompanied with database schema document defining tables and entries or mutually agreed software.

• Schedules: PDF and native scheduling software file format (e.g., Microsoft Project, Primavera, etc.).

• Schematics and Drawings: Design Web Format (DWF) and PDF.

• Photographs: JPEG or current industry standard.

• Video: Any readily available open standard (e.g., AVI, MPEG).

• CAD models: .step files or agreed software platform

• Thermal Analysis Models: Thermal Desktop or agreed software platform

• Structural Analysis Models: Nastran or agreed software platform

• Software: code and/or executable

• Other: mutually agreed upon format

O Other: See DRD for additional distribution instructions.

A Access: The Contractor shall maintain and provide access to data items (including documentation that are produced in the normal business of carrying out the contracted work) in a Government specified web portal, unless otherwise noted in the DRD. Material shall be available for access to a Government representative or delivered for review upon request to the Government utilizing one of the other media selections noted above. NOTE: There is no specific contract requirement or action for delivery of such material and the DRD formats are suggestions for document generation to ensure all required items are addressed.

2.3 CATEGORY - RELATED DEFINITIONS

The following definitions apply to "Submission Category (CAT)" column Tables 3-1 through 3-4. If separate submission instructions are not specified for separate submission due date/maturity items, then the listed submission instruction applies to all submissions.

A Approval: This category requires Government signature approval of the documentation (including approval of any applicable review) before the Contractor begins implementation. If the Contractor has not received approval within 21 calendar days of delivery of a DRD item or the date of any applicable review (whichever is later), the Contractor may proceed as if approved unless otherwise directed by the CO. If the item is rejected (not approved) and returned with comments for revision, the Contractor shall follow the requirements specified by the CO or COR to resolve issues. For most cases the Contractor shall resubmit the document within 14 calendar days of receiving comments from the Government.

R Review: This category requires Government review. The Contractor may implement the document if not notified of corrective actions within 14 calendar days after receipt by the Government. If corrective actions are identified, their resolution will be mutually agreed upon and specified by the CO or COR.

I Information: Documentation items in this category are provided for Government information only.

No formal feedback will be provided. Any issues or questions arising from review of the documentation will be addressed at regular oversight meetings.

3.0 DATA REQUIREMENTS LIST

Tables 3-1 through 3-4 comprise the DRL.

Table 3-1 Review DRL

No. DOCUMENT DUE DATE, MATURITY MEDIA CAT

RE-01 ATS Requirements Review

(ATSRR)

Draft presentation and required data submittals due 30 calendar days prior to the scheduled review.

Final presentation due 7 calendar days prior to the scheduled review.

E

R

A

RE-02

GLIMR Spacecraft to GLIMR Payload Integration Review

(ATSIR)

Draft presentation and required data submittals due 30 calendar days prior to the scheduled review.

Final presentation due 7 calendar days prior to

A

RE-03 GLIMR Observatory Test Readiness Review

(ATSTRR)

Draft presentation and required data submittals due 30 calendar days prior to the scheduled review.

Final presentation due 7 calendar days prior to

RE-04

GLIMR Mission Operations Readiness Review (ATSORR)

Draft presentation and required data submittals due 30 calendar days prior to the scheduled review.

Final presentation due 7 calendar days prior to

RE-05

GLIMR Mission Post Launch Assessment Review (ATSPLAR)

Draft presentation and required data submittals due 30 calendar days prior to the scheduled review.

Final presentation due 7 calendar days prior to the scheduled review.

E

E

R

A

RE-06

GLIMR Mission Decommissioning Review (ATSDR)

Draft presentation and required data submittals due 30 calendar days prior to the scheduled review.

Final presentation due 7 calendar days prior to the scheduled review.

E

E

R

A

RE-07 GLIMR Payload Pre- Ship Review (PSR)

Draft presentation and required data submittals due 30 calendar days prior to the scheduled review.

Final presentation due 7 calendar days prior to the scheduled review.

E

E

R

A

RE-08

GLIMR Extended Mission Review for Period 1 (EMR1)

Draft presentation and required data submittals due 30 calendar days prior to the scheduled review.

Final presentation due 7 calendar days prior to the scheduled review.

E

E

R

A

RE-09

GLIMR Extended Mission Review for Period 2 (EMR2)

Draft presentation and required data submittals due 30 calendar days prior to the scheduled review.

Final presentation due 7 calendar days prior to the scheduled review.

E

E

R

A

RE-10 GLIMR Mission Key Decision Point (KDP) E

Draft presentation and required data submittals due 30 calendar days prior to the scheduled review.

Final presentation due 7 calendar days prior

E

E to the scheduled review.

RE-11 GLIMR Mission Key Decision Point (KDP) F

Draft presentation and required data submittals due 30 calendar days prior to the scheduled review.

Final presentation is due 7 calendar days prior to the scheduled review.

E

E

Table 3-2 Project Management DRL

PM-01 Monthly Project Status Report (MPSR) Monthly, no later than the 15th calendar day E I

PM-02 Security Requirements for Unclassified IT Resources See instructions in DRD E A

PM-03

Financial Reporting of NASA Property in the Custody of Contractors

See instructions in DRD E, O I

PM-04 Subcontracting Reports See instructions in DRD E, O I

PM-05 Organizational Conflicts of Interest (OCI) Plan See instructions in DRD E A

Table 3-3 Safety and Mission Assurance DRL

MA-01

ISO 9001 or AS9100 Compliance Documents:

Quality Plan and Quality System Manual

30 DACA Access I

MA-02 Reporting of Discrepancies

For GLIMR Payload interface-related discrepancies: Within 24 hours after discrepancy incident

For all other discrepancies, Monthly, with MPSR

During On-Orbit Checkout and Operations:

Within 24 hours after discrepancy incident

Access

I

MA-03 Functional and Interface Failure Modes and Effects Analysis (FMEA)

Draft due 30 calendar days prior to the PSR

Final due 30 calendar days prior to the ATSIR

E

E

Table 3-4 Technical DRL

TE-01 Interface Control Documents (ICDs)

Draft due 30 calendar days prior to the ATSRR

Draft due 30 calendar days prior to the PSR

Final due 30 calendar days prior to the ATSIR

TE-02

Verification and Validation (V&V) Plan and Matrix

Draft due 30 calendar days prior to the ATSIR

Draft due 30 calendar days prior to the PSR

Final due 30 calendar days prior to the ATSTRR

TE-03 Verification Reports Routine delivery of verification data and reports within 30 calendar days after verification activity completion.

TE-04

GLIMR Spacecraft Thermal Analysis Report and Thermal Model

Draft due 30 calendar days prior to the ATSIR

Final due 30 calendar days prior to the ATSTRR

Update due prior to GLIMR Spacecraft delivery to Launch Vehicle facility.

A

A

TE-05

Coupled Loads Analysis and Dynamics Environment Report

Draft due 30 calendar days prior to the ATSIR

Final due 30 calendar days prior to the ATSTRR

Update due prior to GLIMR Spacecraft delivery to Launch Vehicle facility.

A

A

TE-06

GLIMR Payload to GLIMR Spacecraft Integration and Test Procedures

Draft due 30 calendar days prior to the PSR

Draft due 30 calendar days prior to the ATSIR

Final due 30 calendar days prior to the ATSTRR

TE-07 Contamination Control Plan

Draft due 30 calendar days prior to the PSR

Final due 30 calendar days prior to the ATSIR

TE-08

GLIMR

Observatory Operations Plan

Draft due 30 calendar days prior to the ATSRR

Final due 30 calendar days prior to the ATSTRR

Update due 30 calendar days prior to the

ATSORR

A

A

TE-09

GLIMR Mission Software Integration, Test Plan and Procedures

Draft due 30 calendar days prior to the ATSRR

Draft due 30 calendar days prior to the PSR

Final due 30 calendar days prior to the ATSTRR

Update due 30 calendar days prior to the

TE-10 Host Contribution to LOS Jitter Budget

Draft due 30 calendar days prior to the ATSIR

Final due 30 calendar days prior to the ATSTRR

Update due 30 calendar days prior to the

4.0 DATA REQUIREMENTS DESCRIPTION (DRD)

4.1 REVIEW DRDS

Title:

ATS Requirements Review (ATSRR)

DRD No.:

RE-01

Reference:

SOW 4.2.1

Use:

The ATSRR is a multi-disciplined technical review to ensure that the ATS requirements as defined in the SOW and ATSHSRD are correctly interpreted and allocated to the GLIMR Spacecraft and GLIMR Ground Segment. The Success Criteria of this review is the Contractor’s demonstration of the established GLIMR Spacecraft and GLIMR Ground Segment requirements baseline to be implemented by the Contractor.

Preparation Information:

A. The Contractor shall address all ATS contract requirements, the required ICDs, requirements/design tradeoffs and analyses, and applicable Contractor internal documentation that govern the performance of the GLIMR Spacecraft and GLIMR Ground Segment. Topics shall include:

1. Process and plan for system engineering of interfaces.

2. Preliminary storyboard for GLIMR Payload Integration, Test, Launch, and Operations

(ITLO).

3. Preliminary concept of On-Orbit GLIMR Payload and GLIMR Observatory operations.

4. Overview of GLIMR spacecraft architecture, launch vehicle configuration, and Ground

Segment architecture.

5. Discussion of needed deliverables and receivables between the Contractor and the

Government.

6. Overview of organizational structure and personnel support team for System

Engineering, ITLO, and On-Orbit operations.

7. Plans for hardware configuration management.

8. Software Configuration and Safety Assurance Plans.

9. Plans and processes for satisfying the contract requirements.

10. Plans for technical and schedule risk management, including risk matrices and mitigations.

11. Summary review of the DRDs delivered by ATSRR (per Table 3-4).

12. Schedule that includes the GLIMR Payload integration within the GLIMR spacecraft development schedule, including the dates for all DRL/DRD Reviews (i.e., RE-1 through RE-11) and the internal GLIMR Spacecraft reviews.

B. The Contractor shall prepare the following:

1. Collaboration, agreement, and compliance with the terms of reference (ToR).

2. An agenda of the Review.

3. Review Package data submittals that include all DRDs to be delivered at ATSRR that are listed in Table 3-4.

4. Review presentation package.

5. A Review Report including:

a. List of attendees;

b. Updated material as needed;

c. Findings and minutes; and

d. Summary of Review Action Items.

6. Review Action Items to be organized, assigned, and closed out following the review with reports on closure status provided to the COR upon request.

C. Contractor format for the Review is acceptable.

GLIMR Spacecraft to GLIMR Payload Integration Review (ATSIR)

DRD No.:

RE-02

Reference:

SOW 4.2.1

Use:

The ATSIR is a multi-disciplined technical review to demonstrate that the GLIMR Spacecraft and GLIMR Ground Segment meets all requirements with acceptable risk and within the schedule constraints. Establishes the basis for proceeding with GLIMR Payload integration onto the GLIMR Spacecraft, and that the Contractor’s integration facilities, support personnel, and integration plans and procedures are ready to support integration. The ATSIR success criteria is the Contractor’s demonstration that acceptable design options have been selected, interfaces have been identified, verification methods have been described, and GLIMR Spacecraft is assembled and ready for GLIMR payload integration activities.

Preparation Information:

A. The Contractor shall include in this review:

1. Review and resolution of action items from previous reviews.

2. Review and status of the contract requirements and deliverables.

3. ATS design descriptions, including flight system, Ground Segment, software, end-to-end information and data flow, and operations processes and scenarios.

4. Major trade-offs, changes, and accomplishments since ATSRR.

5. Required changes/modifications to the Contractor’s standard Spacecraft and Ground

Segment to host the GLIMR Payload.

6. GLIMR ATS requirements and flow down and traceability to the Contractor.

7. Verification and validation program, including identification of Incompressible Test List

(i.e., minimum set of tests to verify requirements) items, and Test-as-You-Fly exceptions (i.e., testing configurations that are different than it will be when in flight).

8. GLIMR ground support equipment design status for mechanical, electrical, thermal, software, and shipping and handling equipment.

9. Contractor software and Ground Segment development, and planned tests.

10. Progress on Launch vehicle status and interfaces.

11. Performance capabilities (e.g., station-keeping, orbital parameters) and technical resources (e.g., mass, power, data), utilization, and margins.

12. Status of Contractor acquisitions and facilities development (if applicable).

13. Update of technical risks.

14. Schedule status with margins, risks, performance against original plan, trends, and assessment.

15. ATS integration and testing plans, including GLIMR Spacecraft and GLIMR Ground

Segment, handling equipment, ground support equipment, and software.

B. The Contractor shall prepare the following:

1. Collaboration, agreement, and compliance with the ToR.

2. An agenda of the Review.

3. Review Package data submittals that include all DRDs to be delivered at ATSIR that are listed in Tables 3-3 and 3-4.

4. Review presentation package.

5. A Review Report including:

a. List of attendees;

b. Updated material as needed;

c. Findings and minutes; and

d. Summary of Review Action Items.

GLIMR Observatory Test Readiness Review (ATSTRR)

DRD No.:

RE-03

Reference:

SOW 4.2.1

Use:

The GLIMR Observatory TRR evaluates the readiness of the integrated GLIMR Payload and GLIMR Spacecraft to be environmentally, electrically, and functionally tested, and assesses the readiness of the Contractor’s personnel, test procedures, test equipment, and test facilities. The ATSTRR Success Criteria is the Contractor’s demonstration that all plans, procedures, and equipment are ready for GLIMR Observatory testing.

Preparation Information:

A. The Contractor shall include in this review:

1. Review and resolution of action items from previous reviews.

2. Test staffing, roles and responsibilities, and certifications required and status.

3. Test requirements and test criteria.

4. Storyboard of handling and testing flow.

5. Test plans and procedures for all operations.

6. Plan to close remaining open Verification and Validation items.

7. Test facility status.

8. Configuration of and status of the flight system hardware and software including any deviations between planned hardware and software integration and actual hardware and software integration.

9. Status of environmental, mechanical, thermal, and electrical test support equipment required to conduct the test including all protective safety measures (i.e. Electrostatic Discharge (ESD) protection).

10. Safety of the flight articles, including risk-reduction actions taken.

11. Compliance with any applicable Contractor test policies, requirements, practices, and principles.

12. Schedule of testing, including the tests required in SOW Section 6.3.2, System Level

Integration and Testing.

13. Process for handling anomalies during test activities.

14. Contingency plans.

B. The Contractor shall prepare the following:

1. Collaboration, agreement, and compliance with the ToR.

2. An agenda of the Review.

3. Review Package data submittals that include all DRDs to be delivered at ATSTRR that are listed in Table 3-4.

4. Review presentation package.

5. A Review Report including:

a. List of attendees;

b. Updated material as needed;

c. Findings and minutes; and

d. Summary of Review Action Items.

GLIMR Mission Operations Readiness Review (ATSORR)

DRD No.:

RE-04

Reference:

SOW 4.2.1

Use:

The ATSORR evaluates the readiness of the GLIMR Ground Segment to support launch and flight operations. The ATSORR Success Criteria is the Contractor’s demonstration of the readiness of the GLIMR Ground Segment to support launch and flight operations.

Preparation Information:

A. The Contractor shall include in this review:

1. Review and resolution of action items from previous reviews

2. Operations overview including description of organizational roles and responsibilities, (i.e.

Operator staffing roles and responsibilities, certifications required, and status).

3. Operations concept description including plans for GLIMR Observatory On-Orbit

Checkout, calibration, characterization, uplink/commanding, downlink, data flows, telemetry monitoring, and planning.

4. Description of hardware, facilities, testbeds, and simulators available to support On- Orbit operations.

5. Ground Segment requirements and verification status with plan to complete open V&V items.

6. Ground Segment schedule.

7. Assessment of readiness of procedures, tools, software, and facilities for GLIMR

Observatory operations, science, and ancillary data processing.

8. Plans for data management and archival.

9. Overview of process for problem reporting and tracking.

10. GLIMR Spacecraft anomaly responses that impact the GLIMR Payload.

11. Mishap and contingency plans.

12. Support for GLIMR Mission End of Mission plans.

13. Technical and programmatic risk assessment.

14. Status of Launch vehicle.

15. Status of appropriate commercial licenses to launch and operate at desired orbital slot.

B. The Contractor shall prepare the following:

1. Collaboration, agreement, and compliance with the ToR.

2. An agenda of the Review.

3. Review Package data submittals that include all DRDs to be delivered at ATSORR that are listed in Table 3-4.

4. Review presentation package.

5. A Review Report including:

a. List of attendees;

b. Updated material as needed;

c. Findings and minutes; and

d. Summary of Review Action Items.

6. Review Action Items to be organized, assigned, and closed out following the review with

GLIMR Mission Post Launch Assessment Review (ATSPLAR)

DRD No.:

RE-05

Reference:

SOW 4.2.1

Use:

The ATSPLAR evaluates the readiness of the GLIMR observatory to proceed with full, routine operations after post-launch deployment. The ATSPLAR also evaluates the status of the project plans and the capability to conduct the mission with emphasis on near-term operations and mission-critical events. The ATSLPAR Success Criteria is the Contractor’s demonstration of GLIMR Observatory operational readiness.

Preparation Information:

A. The Contractor shall include in this review:

1. Review and resolution of action items from previous reviews

2. Launch vehicle performance assessment and mission implications, including launch sequence assessment and launch operations.

3. GLIMR Observatory operations performance, including (when appropriate) the early propulsive maneuver results.

4. GLIMR Payload performance, including ongoing calibration plans and status.

5. Ground operations performance, including status of staffing, facilities, tools, and mission software.

6. Command and telemetry summary, including Forward Error Correction (FEC), link and end-to- end data protection and accountability, data drop recovery, and resynchronization/recovery.

7. In-flight anomalies and responsive actions taken, including any autonomous fault protection actions taken, any unexplained telemetry, or any alarms.

8. Significant changes to the system (e.g., hardware, software, or interfaces), support systems, operations (e.g., schedules, processes and procedures), and staffing.

9. Lessons Learned and recommendations for future hosting services.

10. Technical and programmatic risk assessment.

11. Status of appropriate commercial licenses to continue to operate at desired orbital slot.

B. The Contractor shall prepare the following:

1. Collaboration, agreement, and compliance with the ToR.

2. An agenda of the Review.

3. Review Package data submittals that include all DRDs to be delivered at ATSPLAR that are listed in Table 3-2.

4. Review presentation package.

5. A Review Report including:

a. List of attendees;

b. Updated material as needed;

c. Findings and minutes; and

d. Summary of Review Action Items.

6. Review Action Items to be organized, assigned, and closed out following the review with

GLIMR Mission Decommissioning Review (ATSDR)

DRD No.:

RE-06

Reference:

SOW 4.2.1

Use:

The ATSDR confirms the decision to terminate or decommission the GLIMR Observatory and assesses the readiness of the GLIMR Observatory for the safe decommissioning and disposal of its assets. The ATSDR Success Criteria is the Contractor’s demonstration of GLIMR Observatory decommissioning readiness.

Preparation Information:

A. The Contractor shall include in this review:

1. Review and resolution of action items from previous reviews

2. GLIMR Observatory operations performance, including propulsive maneuver results.

3. GLIMR Payload performance and status.

4. Ground operations performance, including status of staffing, facilities, tools, and mission software.

5. In-flight anomalies and responsive actions taken, including any autonomous fault protection actions taken, any unexplained telemetry, or any alarms.

6. Significant changes to the system (e.g., hardware, software, or interfaces), support systems, operations (e.g., schedules, processes and procedures), and staffing.

7. Technical and programmatic risk assessment.

8. Plan for decommissioning and disposal of the GLIMR Payload

a. Transfer of operations from NASA to commercial.

9. Status of appropriate commercial licenses no longer continue to operate at desired orbital slot.

B. The Contractor shall prepare the following:

1. Collaboration, agreement, and compliance with the ToR.

2. An agenda of the Review.

3. Review Package data submittals that includes all DRDs to be delivered at ATSPLAR that are listed in Table 3-2.

4. Review presentation package.

5. A Review Report including:

a. List of attendees;

b. Updated material as needed;

c. Findings and minutes; and

d. Summary of Review Action Items.

6. Review Action Items to be organized, assigned, and closed out following the review with

GLIMR Payload Pre-Ship Review (PSR)

DRD No.:

RE-07

Reference:

SOW 4.2.2

Use:

The GLIMR Payload PSR is a Government-led review that shall be supported by the Contractor.

The Contractor shall provide content needed to assess readiness to receive the GLIMR Payload at the Contractor facilities.

Preparation Information:

The Contractor shall:

A. Prepare for this review a summary of the plans and status of preparations for integration and testing of the GLIMR Payload at the Contractor facilities, including:

1. Demonstration of facility readiness for receiving the GLIMR Payload and associated Ground Support Equipment (GSE), including control of ESD, cleanliness, environmental control, and safety processes.

B. Prepare the following:

1. Data Submittals of all DRDs to be delivered at PSR that are listed in Tables 3-3 and 3-4.

C. Review and comment on the GLIMR Payload PSR documentation within 14 calendar days of receipt from the Government.

GLIMR Extended Mission Review for Period 1 (EMR1)

DRD No.:

RE-08

Reference:

SOW 4.2.2

Use:

The GLIMR EMR1 is a Government-led review that shall be supported by the Contractor. The Contractor shall provide content needed to assess readiness to extend GLIMR Mission.

Preparation Information:

The Contractor shall:

A. Provide input and presentations covering the following:

1. Ground operations performance, including status of staffing, facilities, tools, and mission software

2. In-flight anomalies and responsive actions taken, including any autonomous fault protection actions taken, or any unexplained telemetry, and or any alarms

3. Significant changes to the system (e.g., hardware, software, or interfaces), support systems, operations (e.g., schedules, processes and procedures), and staffing.

4. Technical and programmatic risk assessments

5. Status of appropriate commercial licenses to operate at desired orbital slot.

B. Review and comment on the GLIMR EMR1 documentation within 14 calendar days of receipt from the Government.

GLIMR Extended Mission Review for Period 2 (EMR2)

DRD No.:

RE-09

Reference:

SOW 4.2.2

Use:

The GLIMR EMR2 is a Government-led review that shall be supported by the Contractor. The Contractor shall provide content needed to assess readiness to extend GLIMR Mission.

Preparation Information:

The Contractor shall:

A. Provide input and presentations covering the following:

1. Ground operations performance, including status of staffing, facilities, tools, and mission software

2. In-flight anomalies and responsive actions taken, including any autonomous fault protection actions taken, or any unexplained telemetry, and or any alarms

3. Significant changes to the system (e.g., hardware, software, or interfaces), support systems, operations (e.g., schedules, processes and procedures), and staffing.

4. Technical and programmatic risk assessments

5. Status of appropriate commercial licenses to operate at desired orbital slot.

B. Review and comment on the GLIMR EMR2 documentation within 14 calendar days of receipt

GLIMR Mission Key Decision Point (KDP) E

DRD No.:

RE-10

Reference:

SOW 4.2.2

Use:

The GLIMR KDP-E is a Government-led review that shall be supported by the Contractor. The Contractor shall provide content needed to demonstrate readiness of GLIMR ATS for launch and operations of the GLIMR Observatory and GLIMR Ground Segment.

Preparation Information:

The Contractor shall:

A. Provide input and presentations covering the following:

1. GLIMR Spacecraft Status

2. GLIMR Ground Segment Status

3. Launch Vehicle Status

4. ATS technical and programmatic risks

5. Status of appropriate commercial licenses to launch and operate at desired orbital slot.

B. Review and comment on the GLIMR KDP E documentation within 14 calendar days of receipt

GLIMR Mission Key Decision Point (KDP) F

DRD No.:

RE-11

Reference:

SOW 4.2.2

Use:

The GLIMR KDP-F is a Government-led review that shall be supported by the Contractor. The Contractor shall provide content needed to demonstrate readiness of GLIMR ATS for closeout of the GLIMR Mission.

Preparation Information:

The Contractor shall:

A. Provide input and presentations covering the following:

1. GLIMR Spacecraft Status

2. GLIMR Ground Segment Status

3. Status of appropriate commercial licenses to operate at desired orbital slot.

B. Review and comment on the GLIMR KDP F documentation within 14 calendar days of receipt

4.2 PROJECT MANAGEMENT DRDS

Monthly Project Status Report (MPSR)

DRD No.:

PM-01

Reference:

SOW 4.1; 4.2.4; 6.4

Use:

These reports will be used to provide an opportunity for monthly discussions between the Contractor and the Government regarding schedule, plans, and issues and to evaluate contract status.

Preparation Information:

The Contractor shall provide the MPSR in Microsoft PowerPoint and shall contain the following minimum information:

A. Overall programmatic status summary (technical, schedule) as it relates to the ATS, including, but not limited to: progress of the GLIMR Spacecraft development; interface definition;

integration and test; launch vehicle planning; and summary of programmatic or technical risks related to the GLIMR Payload-to-GLIMR Spacecraft interface design elements that may impact the GLIMR Mission.

B. Summary report on current and planned schedule activities across the span of the mission including, at a minimum:

1. Key milestones and technical status of systems and subsystems impacted by the GLIMR Payload interface requirements; and

2. A top level Gantt-type summary arranged by activity that summarizes the contract effort including, but not limited to, period of performance and major milestones/reviews; critical path; high level linkage of tasks; schedule margin; major mission phases (e.g., design, fabrication, integration, assembly); end item deliveries; schedule risks; and current forecast-to-complete.

C. Reporting of discrepancies.

D. DRL/DRD products status.

E. Key management and development metrics and trends including, but not limited to, a summary of open anomaly reports related to the ATS and any tracked technical resource budgets related to the ATS.

F. Technical and programmatic risks, issues, anticipated approaches for resolution, and all updates from previous reports.

G. Status of open issues/action items and problems from prior reporting periods.

H. Problems encountered during the reporting period, and anticipated approaches for resolution.

I. Significant plans, activities, meetings, and reviews for the next reporting period.

J. Any ATS changes that affect/impact the GLIMR Payload integration or launch.

K. GLIMR Spacecraft and GLIMR Ground Segment status reports during In-Orbit checkout and

On-Orbit operations (Reference SOW 6.4, Launch and GLIMR Observatory In-Orbit Checkout and On-Orbit Operations).

1. DRD Title: Security Requirements for Unclassified IT Resources

2. DRD No.: PM-02 3. Data Type: 1 4. OPR: OCIO

5. Solicitation No.: (Insert solicitation number)

6. Contract No./TO Number: (Insert contract number)

7. Date Issued: TBD 8. Date Revised: TBD 9. DRD Category:

Technical ☒ Administrative☐

S&MA ☐

10. Description/Use: To ensure that IT security reporting requirements, including Cyber Supply Chain Risk Management (C-SCRM), are met for all IT systems utilized during work associated with this contract and necessary training requirements are fulfilled.

11. Distribution: All deliverables required by this DRD, except for the C-SCRM plan, shall be submitted electronically to the CO, COR, ACOR, and NASA Organization’s Information System Security Officer (ISSO) (i.e., Security Officer). Approval will be provided by the ISSO. If the organization does not have an ISSO, approval will be provided by the NASA Information Owner. C-SCRM plans shall be submitted to and approved by the ICT/C-SCRM Service Element Lead at agency-dl-ocio-cys-cp-scrm@mail.nasa.gov.

Initial Submission:

Information System Security and C-SCRM Plan(s): For contractor-owned systems, due at the start of phase-in. Initial submission not required for existing, approved plans for Government-owned and Contractor-managed systems. For new Federal Information Systems, due with the delivery of the system.

Non-Federal System Certification: Prior to any transfer of NASA non-public information to the contractor, the contractor shall provide documentation of the certification of the non-federal system to the security officer of the NASA organization that owns the information (typically the organization responsible for the contract).

If the organization does not have an ISSO, the attestation shall be provided to the NASA Information

Owner. Information on Employees in Sensitive Positions/Assignments Report: At the start of phase-in

IT Security Point of Contact: At the start of phase-in

IT Security Awareness Training: Training required prior to access to NASA information and systems.

IT Security Role Based Training: Foundational training is provided prior to performance of assigned role.

Initial evidence showing completion due at the end of phase-in.

Submission Frequency:

Information System Security Plan(s) and C-SCRM Plan: As

Required Non-Federal System Certification: Annually

Information on Employees in Sensitive Positions/Assignments Report: Annually mailto:agency-dl-ocio-cys-cp-scrm@mail.nasa.gov mailto:agency-dl-ocio-cys-cp-scrm@mail.nasa.gov

IT Security Point of Contact: As Required

IT Security Awareness Training: Annually on anniversary date of initial training

Financial Reporting of NASA Property in the Custody of Contractors

DRD No.:

PM-03

Reference:

NFS 1852.245-73, Financial Reporting of NASA Property in the Custody of Contractors Use:

To annually report any NASA owned/Contractor held property that has been furnished or that has been acquired by the Contractor under the terms of this contract.

Preparation Information:

A. The Contractor shall submit annually a NF 1018, NASA Property in the Custody of Contractors, in accordance with NFS 1852.245-73. The Contractor shall comply with the instructions on the Form and NFS 1845.71 and any supplemental instructions for the current reporting period issued by NASA.

B. Subcontractor use of NF 1018 is not required by this clause; however, the Contractor shall include data on property in the possession of subcontractors in the annual NF 1018.

C. The Contractor shall submit the NF 1018 no later than October 15th of each year for the period October 1 through September 30.

D. The Contractor shall submit a final report within 30 calendar days after disposition of all property when contract performance is complete.

Subcontracting Reports

DRD No.:

PM-04

Reference:

FAR 52.219-9, Small Business Subcontracting Plan; NFS 1852.219-75, Individual Subcontracting Reports Use:

The Government uses Subcontracting Reports for collection of subcontract data from Federal contractors, which are required to establish plans for subcontracting with small and small disadvantaged business concerns.

Preparation Information:

A. The Contractor shall submit all subcontracting reports in accordance with FAR 52.219-9 and

NFS 1852.219-75 using the Electronic Subcontract Reporting System (eSRS). Access to eSRS can be found at: http://www.esrs.gov/

B. The Contractor shall notify the Contracting Officer in writing within 5 business days of its eSRS submission.

http://www.esrs.gov/

1. DRD Title: Organizational Conflicts of Interest (OCI) Plan

2. DRD No.: PM-05 3. Data Type: 1 4.OPR: OP

5. Solicitation No.: (Insert solicitation number)

6. Contract No.: (Insert contract number)

7. Date Issued: TBD

8. Date Revised: TBD 9. DRD Category:

Technical ☐ Administrative ☒

S&MA ☐

10. Description/Use: The Plan will communicate the contractor’s approach to identify and resolve OCIs. The contractor will be held accountable for identifying, dispositioning, and reporting OCIs during contract performance.

11. Distribution: Distribution shall be as instructed by the contracting officer.

Initial Submission: Plan shall be submitted with the initial proposal.

Submission Frequency: As needed.

Format: Contractor’s format is acceptable. The electronic format shall be compatible with Microsoft Office.

Interrelationship: NASA Federal Acquisition Regulation (FAR) Supplement (NFS) 1852.209-71, Limitation of Future Contracting, NFS 1852.237-72, Access to Sensitive Information, NFS 1852.237-73, Release of Sensitive Information.

Applicable Documents: FAR Subpart 9.5, Organizational and Consultant Conflicts of Interest, NFS 1809.5, Organizational and Consultant Conflicts of Interest, NASA Guide on Organizational Conflicts of Interest.

Scope: The OCI Plan describes the contractor’s comprehensive approach to identify, avoid, mitigate, neutralize, and report potential OCI issues, including conflicts described in the solicitation and those discovered during contract performance.

Contents: The OCI Plan shall meet the requirements of FAR 9.5 and include the following:

1. Point of contact for OCI issues and reports.

2. Demonstrate an understanding of (1) OCI principles and (2) the full breadth of OCI issues and the types of harm that can result. The Plan at a minimum addresses the three primary types of OCIs (i.e., biased ground rules, unequal access to information, and impaired objectivity).

3. Define company roles, responsibilities, and procedures for (1) screening (i.e., identifying/recognizing, analyzing/evaluating, resolving, and reporting) existing and new business opportunities for actual/potential OCIs and (2) monitoring and reporting all potential/actual OCIs that arise, resolving conflicts, and reporting previously unidentified OCIs or potential OCIs to the Government.

4. Describe how employees are notified of the Plan’s requirements and how this notification will be documented. Establish and require entrance training for new employees, refresher training for existing employees, and exit training for departing employees. Describe how completion of this training will be documented, including a copy of any training certification template that the contractor will use to document that its employees have completed training.

5. Describe how the contractor will report breaches of the protective measures in the Plan to the contracting officer. Describe what processes the contractor will implement following any breach and indicate that final resolution of the corrective action must be approved by the contracting officer.

6. Identify any affiliated companies/entities (e.g., a parent company or a wholly owned subsidiary) and procedures for coordinating OCIs with such affiliated companies/entities.

7. Address the process for reporting all potential/actual OCIs that arise during performance of the contract. An OCI report shall include (1) a description of the conflict, (2) the plan for resolving the conflict, and (3) the benefits/risks to contract performance associated with plan approval/acceptance. Specific resolution strategies shall be appended to the Plan upon approval by the Government.

8. Explain how the contractor will flow down the provisions of this Plan to any subcontractor that may have a conflict with regard to performing the requirements of this contract. Discuss affected subcontractors’ OCI program as it relates to this contract and specifically explain how affected subcontractors will identify, resolve, and report actual/potential OCIs associated with this contract.

9. Define organizational and employee sanctions for violations of established OCI procedures/requirements/guidelines.

10. Include an assertion from the offeror that to the best of its knowledge no OCIs exist currently, if applicable. Provide a list of all the prime’s and proposed subcontractor(s)’s NASA contracts and subcontracts currently being performed and contracts performed within the last five years of the release of this solicitation, in order to provide the CO a better understanding of other NASA work performed by the offeror that may give rise to an actual or potential conflict. For each prime contract and subcontract listed, the offeror shall: (1) identify the contract number; (2) describe the scope of work in sufficient detail to ascertain the likelihood of a conflict with performance of this contract; and (3) discuss any conflicts that may arise from performance of the listed contracts and award of this contract.

11. The offeror shall also list any non-NASA Federal contracts and subcontracts that it or its proposed subcontractors are currently performing or have performed in the five years preceding the release of the solicitation that may give rise to an OCI. For each and subcontract listed, the offeror shall: (1) identify the contract by number and name; (2) identify the name, address and contact information of the customer(s); (3) describe the scope of work in sufficient detail to ascertain the likelihood of a conflict with performance of this contract; and (4) discuss any conflicts that may arise from performance of the listed contracts and award of this contract.

12. For financial or other interests or relationships beyond Federal contracts or subcontracts that may give rise to an OCI, the offeror shall (1) address the nature and extent of the interest(s) or relationship(s); (2) list any entity or entities involved in the interest(s) or relationship(s) and award of this contract.

13. The offeror shall address how it will avoid, neutralize, or mitigate each potential OCI listed above.

Sufficient information must be provided to allow a meaningful evaluation of the potential effect of the interest on the performance of the statement of work.

14. Include a requirement to update this plan as necessary to address specific OCIs. All updates to the plan must be approved by the contracting officer and the updates/changes must be incorporated in the contract to be effective.

15. Require periodic self-audits to ensure compliance with established OCI procedures/requirements/guidelines.

16. Define records related to the OCI plan (e.g., training and audit records) that will be made available to the Government upon request. Note: The OCI Plan as outlined in paragraphs 1 through 12 above is not for the purpose of addressing other very important contractual obligations such as (1) the contractor’s obligation to protect sensitive information in accordance with NFS 1852.237-72, Access to Sensitive Information, (2) the contractor’s obligation to conduct business in an ethical manner in accordance with FAR 52.203-13, contractor’s Code of Business Ethics and Conduct, and (3) the contractor’s obligation to prevent personal conflicts of interest in accordance with FAR 52.203-16, Preventing Personal Conflicts of Interest.

17. In an appendix to the OCI Plan identify the strategy (e.g., mitigation, limitation on future contracting) for resolving each OCI that is either identified in the solicitation or created by the requirements of the solicitation/contract and explain the effect of such strategy on performance of the contract. If using a firewall, explain how these actions will operate to successfully address the conflict without adversely affecting performance of the contract. (Note: Specific plans to limit future competition are reflected in the clause at NFS 1852.209-71, Limitation of Future Contracting.)

Remarks: None

Maintenance: The contractor shall review the OCI Plan on an annual basis or as directed by the contracting officer to revise the OCI Plan if necessary. Revisions are subject to contracting officer approval and shall be incorporated by change page or complete reissue.

4.3 SAFETY AND MISSION ASSURANCE (S&MA) DRDS

1. DRD Title: ISO 9001 or AS9100 Compliance Documents: Quality Plan and Quality System Manual

2. DRD No.: MA-01 3. Data Type: 1 4. OPR: Safety & Mission Assurance Office (SMAO)

5. Solicitation No.: (Insert solicitation number)

6. Contract No.: (Insert contract number)

7. Date Issued: TBD 8. Date Revised: TBD 9. DRD Category:

Technical ☐

Administrative ☒

S&MA ☐

10. Description/Use: The Contractor's quality system shall be in compliance with the current International Standard ISO 9001

11. Distribution: Contract Specialist; Contracting Officer’s Representative; Safety and Mission Assurance Office, Mission Assurance Branch, gugu.n.rutherford@nasa.gov

Initial Submission: Within thirty calendar days after the contract award date, the Contractor shall submit a copy of its Quality Plan and its Quality System Manual.

Submission Frequency: The Contractor's quality system shall remain compliance to the ISO 9001 or AS9100 standard during the term of the contract.