Attachment C - CDRL.pdf

Effective Date: BD

Expiration Date: TBD

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

SOLAR-XRIS-REQ-0031, Revision -

Space Weather Observations at L1 (SOLAR) Series, Code 493

Space Weather Observations at L1 to

Advance Readiness (SOLAR) Project

X-Ray Irradiance Sensor (XRIS)

Contract Deliverables Requirements List

(CDRL)

U.S. Department of Commerce (DOC)

National Oceanic and Atmospheric Administration (NOAA)

NOAA Satellite and Information Service (NESDIS)

National Aeronautics and Space Administration (NASA)

GSFC SOLAR Project

CMO

January 13, 2026

DRAFT

DRAFT

https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List http://www.noaa.gov/ https://www.commerce.gov/

SOLAR Project XRIS CDRL SOLAR-XRIS-REQ-0031, Revision -

Effective Date: TBD ii

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

Space weather Observations at L1 (SOLAR) Project X-Ray

Irradiance Sensor (XRIS)

Contract Deliverables Requirements List (CDRL)

Signature/Approval Page

Approved By:

Original signed by:

E. Matt Glanfield

SW Next SOLAR XRIS Instrument Engineer

NASA Goddard Space Flight Center

C. Hudson DeLee

SW Next SOLAR Instrument Systems Manager

James Morrissey

Project Manager, SW Next SOLAR https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List iii

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

Preface

This document is under SOLAR Program configuration control. Once this document is approved, SOLAR approved changes are handled in accordance with Class I and Class II change control requirements as described in the SOLAR Configuration Management Procedure, and changes to this document shall be made by complete revision.

In this plan, all mandatory actions (i.e., requirements) are denoted by statements containing the term “shall.” The terms “may” or “can” denote discretionary privilege or permission; “should” denotes a good practice and is recommended but not required; “will” denotes expected outcome;

and “are/is” denotes descriptive material.

Any questions should be addressed to:

SOLAR Configuration Management Office

Mail Stop: 493

Goddard Space Flight Center

Greenbelt, MD 20771 https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List iv

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

Change History Log

Revision Effective Date Description of Changes

(Reference the CCR & CCB/ERB Approval Date)

Revision -https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List v

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

Table of Contents

INTRODUCTION

1.1 DEFINITION OF DUE DATES/MATURITY, DEFINITION OF CATEGORIES, AND

DELIVERY INSTRUCTIONS

1.1.1 Due Date

1.1.2 Maturity

1.1.3 NASA Acceptance Code

1.2 XRIS CONTRACT DELIVERABLES REQUIREMENTS LIST (CDRL)

1.3 DATA ITEM DESCRIPTION (DID) OVERVIEW

1.4 DELIVERY INSTRUCTIONS

1.5 CDRL ITEMS OVERVIEW

PROGRAM DATA ITEM DESCRIPTIONS

PM-1 PROGRAM MANAGEMENT PLAN

PM-4 ENGINEERING CHANGE PROPOSALS, DEVIATIONS, AND WAIVERS

PM-5 PROGRAM MANAGEMENT STATUS REVIEW DATA PACKAGE

RESOURCE MANAGEMENT

RM-3 DETAILED SCHEDULES

REVIEW DATA ITEM DESCRIPTIONS

RVW-1 FORMAL REVIEW DATA PACKAGE

SYSTEMS ENGINEERING DATA ITEM DESCRIPTIONS

SE-3 XRIS SYSTEM SPECIFICATION

SE-4 DETAILED DESIGN SPECIFICATIONS

SE-5 THERMAL MATH MODEL AND REPORTS

SE-6 STRUCTURAL MATH MODEL AND REPORTS

SE-7 SOLID MATH MODEL

SE-9 SYSTEM PERFORMANCE VERIFICATION PLAN

SE-10 SYSTEM PERFORMANCE VERIFICATION REPORT

SE-11 PERFORMANCE VERIFICATION PROCEDURES

SE-12 ENVIRONMENTAL VERIFICATION SPECIFICATION

SE-13 ENVIRONMENTAL VERIFICATION REPORTS

SE-14 DIGITAL IMAGE AND VIDEO RECORDS

SE-15 INDIVIDUAL TEST PLANS

SE-16 MAGNETIC CONTROL PLAN

SE-18 EMC/EMI COMPATIBILITY PLAN

SE-19 MAINTENANCE, TEST, AND OPERATIONS MANUAL FOR THE XRIS

EMULATOR

SE-20 REQUEST FOR USE OF MULTI-MISSION OR PREVIOUSLY DESIGNED,

FABRICATED, OR FLOWN HARDWARE

MISSION ASSURANCE AND SAFETY DATA ITEM DESCRIPTIONS

MA 1-1 MISSION ASSURANCE REQUIREMENTS COMPLIANCE MATRIX

MA 2-1 INPUT TO ORBITAL DEBRIS ASSESSMENT REPORT and End of Mission Plan

(EOMP)

MA 3-1 SYSTEM SAFETY PLAN (SSP)

MA 3-2 SAFETY REQUIREMENTS COMPLIANCE CHECKLIST

https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List vi

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

MA 3-4 INSTRUMENT SAFETY ASSESSMENT REPORT

MA 4-2 FAILURE MODE, EFFECTS, AND CRITICALITY ANALYSIS, AND

CRITICALITY ITEMS LIST

MA 4-5 LIMITED LIFE ITEMS LIST

MA 4-6 PARTS STRESS ANALYSIS

MA 4-7 WORST-CASE ANALYSES

MA 5-1 SOFTWARE ASSURANCE PLAN

MA 7-1 EEE PARTS CONTROL PLAN

MA 7-2 MASTER EEE PARTS LIST

MA 7-3 RADIATION EFFECTS MITIGATION

MA 7-4 RADIATION SHIELDING AND DOSE ANALYSIS REPORT

MA 7-5 SINGLE EVENT FAULT MANAGEMENT PLAN

MA 8-2 MATERIALS USAGE AGREEMENT

MA 8-3 MATERIALS IDENTIFICATION AND USAGE LIST

MA 11-1 GIDEP ALERTS/NASA ADVISORY DISPOSITIONS

MA 11-2 INITIATING GIDEP ALERTS

MA 12-1 END ITEM ACCEPTANCE DATA PACKAGE

OPERATIONS DATA ITEM DESCRIPTIONS

OPS-1 FLIGHT TELEMETRY AND COMMAND DATABASE

OPS-2 FLIGHT TELEMETRY AND COMMAND HANDBOOK

OPS-3 OPERATIONS HANDBOOK

OPS-4 GROUND PROCESSING ALGORITHMS TEST AND VALIDATION PLAN

OPS-5 GROUND PROCESSING ALGORITHM DOCUMENT

OPS-6 GROUND SOFTWARE ACCEPTANCE PLAN INPUT

OPS-9 MASS PROPERTIES AND POWER REPORT

OPS-10 XRIS PACKETIZED DATA

OPS-11 INSTRUMENT OPERATIONS CONFIGURABLE ITEMS

SOFTWARE DATA ITEM DESCRIPTIONS

SW-1 SOFTWARE MANAGEMENT PLAN

SW-2 SOFTWARE DELIVERY PACKAGES

INTEGRATION AND TEST DATA ITEM DESCRIPTIONS

I&T-1 TRANSPORTATION, HANDLING PLAN AND PROCEDURES

I&T-2 POST LAUNCH TEST REPORTS

I&T-3 OBSERVATORY LEVEL TEST PROCEDURES

I&T-4 OBSERVATORY LEVEL TEST REPORT

I&T-5 CALIBRATION PROGRAM PLAN

I&T-6 CALIBRATION DATA BOOKS

FPGA DATA ITEM DELIVERABLE

FW-1 FPGA DEVELOPMENT PLAN

FW-2 FPGA DESIGN DATA PACKAGE

XRIS HARDWARE/SOFTWARE DELIVERABLE ITEMS

APPENDIX A ABBREVIATIONS AND ACRONYMS

APPENDIX B RECOMMENDED OPERATING PROCEDURES (ROPS) TEMPLATE . 76

https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List vii

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

INTRODUCTION

This Space Weather Next (SW Next) Space weather Observation at L1 to Advance Readiness

(SOLAR) Instrument Contract Deliverables Requirements List (CDRL) document defines the requirements for deliverable items to be provided by the SOLAR X-Ray Irradiance Sensor

(XRIS) contractor. All data shall be prepared, maintained/updated, and delivered to the

Government in accordance with the requirements specified in the governing contract, delivery order, Statement of Work (SOW), Mission Assurance Requirements (MAR), and this CDRL and its associated Data Item Descriptions (DIDs).

1.1 DEFINITION OF DUE DATES/MATURITY, DEFINITION OF CATEGORIES,

AND DELIVERY INSTRUCTIONS

The following definitions apply to the "Delivery" column in Table 2 below.Error! Reference source not found.

1.1.1 Due Date

a. Proposal: Items that are provided with the proposal.

b. CDR, PER, etc.: Critical Design Review, Pre-Environmental Review, Pre-Ship Review, etc.

c. As Generated: After each initial edition, revision, addition, etc. Monthly: Monthly by the 15th of each month or as required or as modified by CO

d. Weekly: Weekly status reports by Tuesday close of business or as modified by

Contracting Officer (CO)

e. L: Launch Date

f. DACA: Days after contract award

g. MACA: Months after contract award

Unless otherwise noted, the data in the due date column titled "days" are to be interpreted as calendar days.

1.1.2 Maturity

a. Preliminary: The initial submission of an item. To be completed with available information as of the time of preparation for the due date.

b. Update: The best up-to-date information available at the time.

c. Final: The complete thorough submission of an item for approval, review, or information. This does not preclude updating later.

1.1.3 NASA Acceptance Code

A Approval: Documents in this category require approval by the Goddard Space

Flight Center (GSFC) Contracting Officer’s Representative (COR) prior to use by the contractor. Starting when the Government receives the document, the Government

Contracting Officer may provide written (electronic) comments within 21 calendar days.

When the Government identifies a deficiency, the Contractor shall re-submit within 30 calendar days of receiving Government comments (3 days for Spacecraft-level test and calibration/validation procedures) or provide a plan within 7 calendar days (1 day for test https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

calibration/ validation procedures), as specified by the Government Contracting Officer, for approval by the Government to close the deficiency. Normally, the requirement for resubmission will be within 30 days of receiving the Government’s comments. If the

Government does not provide comments in the prescribed time (21 calendar days), the

Contractor may proceed with the associated work after notifying the Government of the intention to proceed.

R Review: Documents in this category require delivery to the Government prior to use and within the time period specified in the "Due Date" column of this document.

They are subject to evaluation by the Government or its designated representatives to determine Contractor effectiveness in meeting contract objectives. Following submission, the Contractor may proceed with the associated work. Starting when the

Government receives the document, the Government Contracting Officer may provide written (electronic) comments within 21 calendar days. When the Government identifies a deficiency, the Contractor shall re-submit within 30 calendar days of receiving

Government comments (3 days for Spacecraft-level test and calibration/validation procedures) or provide a plan within 7 calendar days (1 day for test calibration/ validation procedures), as specified by the Government Contracting Officer, for approval by the

Government to close the deficiency.

I Information: Data in this category require delivery to the Government within the time period specified in the “Due Date” column of the XRIS Contract Deliverables

Requirements List for the purpose of determining current program status, progress, and future planning requirements. The Government Contracting Officer may provide written

(electronic) comments within 21 calendar days to identify errors and omissions, and the

Contractor shall make the corrections and re-submit as specified by the Government

Contracting Officer. The Contractor shall address Government comments in the next version delivered, or in a revised version if it is the final delivery

1.2 XRIS CONTRACT DELIVERABLES REQUIREMENTS LIST (CDRL)

Items with an “As Generated” due date that are critical to schedule, performance, or interface shall be transmitted to GSFC by within 48 hours of generation.

Any updates to items of “Final” maturity shall require the same "approval/review" process as was required for the previous submissions.

All Data items shall be delivered in electronic format to a GSFC SOLAR specified web portal unless otherwise noted in the XRIS Contract Deliverables Requirements List.

Individual CDRL items may be combined with other CDRL items to increase documentation efficiency if the content and requirements of the CDRL items are satisfied.

Electronic deliverables shall be delivered in the following formats unless otherwise approved by the government:

a. Text Documents: PDF (searchable) or MS Word https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

b. Presentations: PDF (searchable) or PowerPoint

c. Spreadsheets: Microsoft Excel

d. Database: Delimited ASCII files accompanied with database schema document defining tables and entries.

e. Schedules: MS Project

f. Schematics and Drawings: PDF

g. Photographs: JPEG or current industry standard.

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

1.3 DATA ITEM DESCRIPTION (DID) OVERVIEW

Each CDRL item is defined by a corresponding DID. The DID includes the title, number, SOW reference, purpose, applicable documents, and required preparation information.

Much of the required information specified in the DIDs may already exist in the Contractor’s documentation. In those cases, existing documents and formats should be used if they meet the intent of the DID requirements. If so, a notation shall be supplied in the deliverable which indicates where in the Contractor’s document the information that satisfies the requirement can be found.

1.4 DELIVERY INSTRUCTIONS

a. The Contractor shall deliver each CDRL item via the media indicated below in accordance with the schedule and any special instructions indicated in Table 2 and/or the corresponding DID, and in accordance with the contract or mission-specific Delivery

Order (DO) requirements and provisions.

b. All CDRL items shall be delivered electronically (one electronic copy for each CDRL item) to an electronic library designated by the Government. If all or a portion of a CDRL item is not well suited for electronic delivery, the item may be delivered via hard copy upon mutual agreement between the Contractor and the Government.

c. Upon submitting each CDRL item, the Contractor shall notify via email the Government

Contracting Officer (CO), the CO Representative, and the Data Management Office.

1.5 CDRL ITEMS OVERVIEW

Table 1 provides a list of CDRL item categories as follows:

a. Item # An alpha-numeric identifier for each CDRL item category and its respective DID.

The alpha descriptor is based on the subject matter of the deliverable:

Table 1 Alpha-numeric identifiers for each CDRL

PM Program Management

RM Resource Management

RVW Reviews

SE Systems Engineering

MA Mission Assurance and Safety https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

OPS Operations

SW Software

I&T Integration and Test

FW FPGA Development Plan

b. Requirements Reference: The reference indicates the section of the SOLAR Instrument

SOW, IMAR, and/or Instrument Requirements Specification (SPEC) where the CDRL item is called out.

c. Title (self-explanatory)

d. Delivery: The contract baseline schedule of delivery for the CDRL item. Many of the dates are referenced to reviews or other milestones. Unless stated otherwise, days are calendar days.

e. Flight Model: This column describes if a deliverable is required for the first flight model

(FM1), the second flight model (FM2), or both flight models.

f. Purpose: The purpose of the CDRL item submission (i.e., The Government’s role following receipt of a CDRL item) is based on the definitions below. The designation for an item applies to all submissions (e.g., preliminary/initial, update, final) of that item unless noted otherwise. UAR indicates Update as Required with the approval letter indicated in the parenthetical. An A, R, or I indicate the delivery is required, with the

Government’s role following a receipt as indicated.

Table 2 SOLAR XRIS Contract Deliverables Requirements List (CDRL)

CDRL No. SOW Title Delivery Flight

Model Purpose

PM-1 4.1 Program Management Plan Preliminary: 30 DACA

Final: PDR+14 days

FM-1 R

PM-4 4.4

Engineering Change

Proposals, Deviations, and

Waivers

As Required Both A (Class-I)

R (Class-II)

PM-5

4.5.6

4.5.9

4.6

Program Management

Status Review Data Package Bi-monthly FM-1 I

RM-3

4.2

4.6 Detailed Schedules

Preliminary: 15 DACA

Monthly Updates by the

15th of each month

Baseline: Submission includes PCM list NLT 90 days after ATP

Both

I

RVW-1

4.5.4.1-

4.5.4.5

Formal Review Data

Package

Preliminary:

Each Review Dry Run –14 days

Update:

Each Review – 7 days

Both I https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

CDRL No. SOW Title Delivery Flight

Model Purpose

RVW-1

(cont.)

Final:

NLT Review – 2 days

SE-3 5 XRIS System Specification

Preliminary: SDR – 14 days

Final: SDR

FM-1

I

R

SE-4

5.1

6.1

6.3

Detailed Design

Specifications

Preliminary: Applicable subsystem PDR

Final: Applicable subsystem CDR

FM-1

R

R

SE-5

5.3

6.3.2.2

Thermal Math Model and

Reports

Preliminary: PDR

Update: CDR, FM1 PER, FM1 PSR, and as generated

Both R

R

SE-6

5.3

6.3.2.2

Structural Math Model and

Reports

Preliminary: PDR

Update: CDR, PER, PSR, and as generated

Both R

Updates: I

SE-7

5.3

6.3.2.2 Solid Math Model

Preliminary: PDR

Update: CDR, FM1 PER, FM1 PSR, and as generated

Both R

Updates: I

SE-9

5.1

6.3.2

System Performance

Verification Plan

Preliminary: SRR-14 days

Final: PDR

Update: SDR/SRR

FM-1

R

A

SE-10

5.1

6.3.2

System Performance

Verification Report

Preliminary: PSR – 30 days

Final: PSR

FM-1

I

I

SE-11

5.1

6.3.2

Performance Verification

Procedures 30 Days prior to use FM-1 A

SE-12

5.1

Environmental Verification

Specification

Preliminary: PDR

Final: CDR – 14 days

Update: As Required

SE-13 5.1

Environmental Verification

Reports

Initial assessment:

1 day after test

Preliminary: 5 days after test

Final: 30 days after Test

I

SE-14

6.3

Digital Image and Video

Records

Preliminary: PER

Final: PSR

Update: As Required

FM-1

I

I https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

CDRL No. SOW Title Delivery Flight

Model Purpose

SE-15

6.1

6.3 Individual Test Plans

Preliminary: CDR

Final: 90 days before Test

FM-1 (FM-

2 as applicable)

A

SE-16

5.5

6.3.2.4 Magnetic Control Plan

Preliminary: PDR

Final: CDR

FM-1

I

R

SE-18 6.3.2.3

EMC/EMI Compatibility

Plan

Preliminary: PDR

Final: CDR

FM-1

I

R

SE-19 7.1.2

Maintenance, Test, and

Operations Manual for the

XRIS Emulator

Final: With Delivery of

XRISE

FM-1 R

SE-20

6.1

6.2

Request for Use of Multi-

Mission or Previously

Designed, Fabricated, or

Flown Hardware

Preliminary: 60 DACA

Final: SDR/SRR + 60 days

FM-1

I

R

MA 1-1 8

Mission Assurance

Requirements Compliance

Matrix

Preliminary: With proposal

Final: 15 DACA

FM-1

I

A

MA 2-1 8

Input to Orbital Debris

Assessment Report (ODAR) and End of Mission Plan

(EOMP)

Preliminary ODAR: 15 days prior to mission PDR

Interim ODAR and Draft

EOMP: 60 days prior to mission CDR

Final: 90 days prior to

Instrument PSR

FM-1

I

I

I

MA 3-1 8 System Safety Plan (SSP)

Preliminary: SRR

Final: 45 days prior to PSR

Updates: 30 days prior to implementation

FM-1

I

R

R

MA 3-2 8

Safety Requirements

Compliance Checklist

Preliminary: 45 days prior to PDR

Final: 45 days prior to CDR

Updates: 45 days prior to

Implementation

FM-1

I

I

I

MA 3-4 8

Instrument Safety

Assessment Report (ISAR)

Preliminary: 30 days prior to instrument PDR

Intermediate: 30 days prior to instrument CDR

Final: 30 days prior to instrument PSR

MA 4-2 8

Failure Mode, Effects, and

Criticality Analysis

(FMECA) and Criticality

Items List (CIL)

Preliminary:

30 days prior to PDR

Update:

FM-1

https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

CDRL No. SOW Title Delivery Flight

Model Purpose

30 days prior to CDR and each subsequent milestone review leading to LRR

MA 4-5 8 Limited Life Items List

Draft: 30 days prior to PDR

Preliminary: 30 days prior to CDR

Updates: 30 days of changes

FM-1

I

R

R

MA 4-6

7.1

Parts Stress Analysis

Draft: 30 days prior to PDR

Final: 30 days prior to CDR

Revisions: 30 after identification

FM-1

R

R

R

MA 4-7

7.1

Worst-case Analyses

30 days prior to CDR

Revisions within 30 days after identification

FM-1 R

MA 5-1 8

Software Assurance Plan

Preliminary: 30 days prior to SRR

Final: 15 days prior to PDR

Updates: 30 days prior to implementation

FM-1

I

MA 7-1

7.1

EEE Parts Control Plan 30 DACA FM-1 I

MA 7-2

7.1

Master EEE Parts List

EEE parts to the Parts

Control Board prior to inclusion

Updates prior to inclusion

FM-1 (FM-

2 as applicable)

A

MA 7-3

7.1

Radiation Effects Mitigation 60 DACA FM-1 A

MA 7-4 8

Radiation Shielding and

Dose Analysis Report

Preliminary: PDR

Final: CDR

FM-1 R

MA 7-5

7.1

Single Event Effect Fault

Management Plan

Preliminary: PDR

Final: CDR

FM-1 A

MA 8-3 8

Materials Identification and

Usage List (MIUL)

Preliminary:

30 days prior to PDR

Final:

30 days prior to CDR

Updates within 30 days after identification

As-built MIUL 30 days prior to PSR

FM-1 (FM-

2 as applicable)

R

R

R

R

MA 11-1 8

GIDEP Alerts/NASA

Advisory Dispositions

Disposition of existing

Alerts within 30 days of identification https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

CDRL No. SOW Title Delivery Flight

Model Purpose

Disposition of new Alerts within 30 days of Alert release

MA 11-2 8 Initiating GIDEP Alerts Within 30 days of identification

FM-1 R

MA 12-1 8

End Item Acceptance Data

Package

Preliminary: 30 days prior to PSR

Final: 30 days prior to End

Item delivery

Updates: 30 days after identification

FM-1 (FM-

2 as applicable)

OPS-1 6.5.3

Flight Telemetry and

Command Database

Baseline: PER of FM1

Final: PSR

FM-1

R

R

OPS-2 6.5.3

Flight Telemetry and

Command Handbook

Preliminary: PDR

Final: PSR

Updates: As required

R

OPS-3 6.5.3 Operations Handbook Preliminary: PER

Final: PSR

FM-1

R

A

OPS-4 6.1.3

Ground Processing

Algorithms Test and

Validation Plan

Preliminary: PDR

Final: PSR - 3 months

Update: CDR

R

R

OPS-5 6.1.3

Ground Processing

Algorithm Document

Preliminary: PDR

Final: PSR -3 months

Update: CDR

R

R

OPS-6 6.1.3

Ground Software

Acceptance Plan Input

Preliminary: CDR

Final: PSR - 6 months

FM-1

R

R

OPS7 6.5.3

Trend Analysis Plan

Trend Analysis Data

Reports

Preliminary: PDR

Final:

CDR as generated

R

OPS-8 6.5.2

On-site Data Analysis

Reports As generated FM-1 R

OPS-9 6.3.2.2

Mass Properties and Power

Report

Monthly NLT 15th of each month

FM-1 I

OPS-10 7 XRIS Packetized Data As generated FM-1 I

OPS-11 6.5.3

Instrument Operations

Configurable Items

Preliminary: 30 days prior to launch

FM-1

R https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

CDRL No. SOW Title Delivery Flight

Model Purpose

Updates: As needed

SW-1 6.1.2 Software Management Plan

Preliminary:

30 DACA

Final:

SW Acceptance Review

Update:

PDR, CDR, TRR

R

R

SW-2 6.5.3.1

Software Delivery

Packages

Preliminary: PER

Final: PSR

Updates: At major revision releases

FM-1

R

R

R

I&T-1 6.4.1 Transportation, Handling

Plan and Procedures

Preliminary: PDR

Final: CDR

FM-1 R

I&T-2 6.5.3

6.5.5 Post Launch Test Reports

Preliminary: 2 weeks after test

Final: 2 months after test

FM-1 R

I&T-3 5.3 Observatory Level Test

Procedures

Preliminary: PER

Final: PSR

FM-1 R

I&T-4 5.3 Observatory Level Test

Report Observatory PSR FM-1 R

I&T-5 6.3.3 Calibration Program Plan

Preliminary: SDR/SRR

Final: CDR

Update: PSR

FM-1

R

R

R

I&T-6 6.3.3 Calibration Data Books Final: PSR of each Model

FM-1 (FM-

2 as applicable)

R

FW-1 6.2.1 FPGA Development Plan Preliminary: SRR/SDR

Final: 30 days before PDR

FM-1

R

R

FW-2 6.2.1

FPGA Design Data Package

(FDDP)

Preliminary:

30 days before PDR

Updates: As generated

Final: 30 days before CDR

FM-1

R https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

PROGRAM DATA ITEM DESCRIPTIONS

PM-1 PROGRAM MANAGEMENT PLAN

Title:

Program Management Plan

DID for CDRL No.

PM-1

Reference:

XRIS SOW Section 4.1

Purpose:

Describes how the program is organized and managed. It provides the management structure, its system of operation, responsible lines of communications, and key personnel assignments

Preparation Information:

1. The Contractor shall prepare and deliver, as prescribed herein, a Program

Management Plan organized as follows:

a. Program Management. Describe the management approach to the implementation of the SOLAR Project Program, including interrelationships of the Contractor’s program office with functional and divisional groups. Use flow diagrams, work breakdown structure, logic networks, etc., as necessary to reduce verbal descriptive material. Address interfaces with the Government and subcontractors.

b. Programmatic Interface with the Government. Describe the process for interfacing with the Government with respect to programmatic and technical status and issues.

c. Organizational Chart. Provide a chart showing the Contractor’s organization for this program, including titles, functions, and lines of authority.

(1) Authority of the Program Manager relative to other on-going programs and applicable support organizations within the company structure. Discuss the

Program Manager’s control over essential resources and functions necessary to accomplish the work.

(2) Process to be followed by the Program Manager in obtaining decisions beyond his/her authority and in resolving conflicts in priority for resources and functions not under the Program Manager’s direct control, such as personnel, finances, and facilities.

d. Implementation approach for the project. Describe in general how the requirements of the program (i.e., Contract, Statement of Work, Mission

Assurance Requirements, XRIS Requirements Document, etc.) will be achieved.

Identify potential problems related to this work and the planned approach to avoiding problems and/or obtaining solutions. Describe controls to be exercised over subcontractors and suppliers.

e. Subcontract management. Describe subcontract management practices, approach to establishing clear subcontract requirements, integration of subcontractor work into the program, management of interfaces, subcontractor reporting, plans for review of subcontractor efforts, integration of reported subcontractor risks and issues into the program, acceptance process, and incorporation of mission assurance requirements into subcontracted efforts. Describe how Government insight into subcontractor activities will be enabled.

f. Management techniques to be employed to minimize risks of violating interface requirements and agreements. Describe how issues will be surfaced in a timely manner and at the proper levels. Identify initial proposed key technical https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

performance metrics the project will use to monitor and report on interface compliance and resource status, including the continuity of knowledge capture of key personnel through the development lifecycle of the two observatories.

g. Technical Working Groups. Describe the process of establishing and implementing technical working groups such as instrument interfaces, pointing/alignment, thermal, contamination control, environmental test planning, special technical topics, etc. Identify each working group separately along with a general description of its function, members, and planned lifetime. Explain how the Contractor will provide Government technical personnel interfaces and how they will function within the technical working groups. Explain how documentation of the Contractor-led meetings will be maintained and distributed to the Government.

h. Program Facilities. Describe the Contractor facilities to be used for all program activities, including security and Government access to each.

2. Appendix A, Risk Management, shall address risk management as follows:

a. Define a plan for risk management that describes the process for risk identification, risk analysis, risk mitigation, and risk monitoring. Include the

Contractor’s process for tracking and reporting risk status and changes. This section shall clearly describe:

(1) Risk management philosophy

(2) Risk management organization, to include roles and responsibilities

(3) Risk Management Review Board, to include members, frequency of meetings, and processes

(4) Database (use, access, updates, responsibilities, etc.)

b. Address the management and reporting of risks associated with hardware and software (e.g., technical challenges and risks, new technology qualification), commercial off-the-shelf software, system safety, performance, cost, and schedule

(i.e., programmatic risks). Identify which tools, techniques, and attributes (i.e., Likelihood and Consequence) will be used to manage the risks. It is strongly recommended that the Contractor use the Goddard Space Flight Center (GSFC) risk matrix standard scale (5x5) definitions as defined in GPR 7120.4D, Risk

Management.

3. Appendix B, Schedule Management, shall address the following:

a. Describe the scheduling system, including details of management control methods and techniques. Include an approach for obtaining adequate insight into schedules for subcontracted efforts and integrating subcontractors schedule information in the system schedule. Include a description of schedule level detail (i.e., Level 1, Level 2, etc.) and use of each level of detail for management of the program.

b. Describes the process for preparation, delivery, and maintenance of a schedule that meets the requirements of CDRL RM-3, Detailed Schedules and provides the primary and secondary critical paths.

4. Appendix C, Spare Parts Plan, describes sparing strategy and includes a list that identifies spare items by name, quantity, integration level of spare, applicable subsystem, and a qualitative and quantitative description of the schedule risk being mitigated by each spare.

5. Appendix D, Configuration Management Plan, describes the Contractor’s hardware https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

and software Configuration Management (CM) system (including a description of the

Contractor’s CM policies and procedures) that will be implemented for this project.

a. Describe the approach, methodology, and application of CM principles and practices, including the following:

(1) CM activities and procedures for each of the following CM functions:

(a) Configuration planning and management

(b) Configuration identification

(c) Configuration change management

(d) Configuration status accounting

(e) Configuration verification and audit

(f) CM of digital data

(2) Change management, including methods of obtaining customer approvals and the role of the Government resident office

(3) Configuration Item Identification List and the Computer Software

Configuration Items and Hardware Configuration Items

6. Appendix E of the Program Management Plan shall include a Work Breakdown

Structure (WBS) and WBS Dictionary with information provided down to the Level 3

WBS.

a. Depict the WBS as a logical, hierarchical display of the subdivision of all project work to be completed and include the approved element title and element number.

b. Arrange the WBS Dictionary in the same order as the contract WBS. Include in the WBS Dictionary the following for each WBS element:

(1) WBS element title

(2) WBS element code

(3) WBS element code description, including quantities, work content and relevant efforts associated with each element (e.g., design, development, manufacturing), and contract end items where applicable

(4) Specification title and number associated with the WBS element, if applicable

PM-4 ENGINEERING CHANGE PROPOSALS, DEVIATIONS, AND WAIVERS

Title:

CONFIGURATION CHANGE REQUESTS (CCR) CLASS I

DID for

CDRL No.

PM-4

Reference:

XRIS SOW Section 4.4

Purpose:

ECPs, Deviations, and Waivers facilitate the configuration control of system design changes

Preparation Information:

1. The Contractor shall prepare and submit, as prescribed herein, Class I ECPs, waivers, and/or deviations using SAE-EIA-649, Configuration Management Standard, as a guideline.

2. All ECPs shall contain, in addition to the change description, sufficient information in the form of attachments, drawings, test results, etc., to allow the Government to evaluate the total impact of the proposed change.

https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

3. For the purposes of this DID, a Class I ECP is a change that:

a. Affects a contract specification, mission requirement, or interface requirement

b. Affects schedules of end-item deliverables to the Government

c. Impacts Government-furnished equipment

d. Affects configuration to the extent that changes would be required to prior deliverables in order to maintain specified performance

4. The Government may direct the Contractor to prepare ECPs under the “Changes” clause of the contract.

5. The Contractor shall allow the Government access to Class II changes.

6. Requests for Waivers and Deviations shall:

a. Describe the requirements that apply to the item, subsystem, or system needing the waiver or deviation and provide specific information regarding the nature of the noncompliance.

b. Describe the effect of the proposed noncompliance on item, subsystem, and system performance at higher levels of assembly.

c. Describe the cost or schedule impact of non-approval of the waiver or deviation.

Note: Safety-related waivers and deviations are submitted in accordance with CDRL MA3- 2, Safety Requirements Compliance Checklist, MAR section 3.3.7.

Note: Waivers and deviations related to Material Review Board actions are submitted in accordance with the XRIS MAR.

PM-5 PROGRAM MANAGEMENT STATUS REVIEW DATA PACKAGE

PROGRAM MANAGEMENT STATUS REVIEW DATA PACKAGE

DID for CDRL No.

PM-5

Reference:

XRIS SOW Section 4.5.6, 4.5.9, and 4.6

Purpose:

To summarize the progress since the previous Program Management Status Review.

Preparation Information:

The Program Management Status Review Data Package shall include the following items:

1. Accomplishments since last review, including 20 milestone events depicting critical items of program status for the succeeding two months with a report on the previous two months milestone events

2. Schedule

3. Technical issues and concerns, including summaries of technical progress and descriptions of the current technical issues and concerns

4. Business issues and concerns, including personnel changes https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

5. Open contract items

6. Open action items

7. Planned effort for next review period

8. Reliability and quality assurance information

9. Mass properties and power summary

10. Software metrics for each Class A, B or C Computer Software Configuration Item

(CSCI) including:

a. Number of software requirements and their change status

b. Number of software change requests and problem reports and their status

c. Resource utilization estimates and measurements of memory, CPU and I/O

Bandwidth

11. Summary of progress towards Payment Milestones

12. Subcontractor status including:

a. Efforts under contract

b. Efforts waiting contract award

c. Changes to first tier and sub-tier contractors

d. Change orders, problems, issues

e. Pending subcontractor consent packages

f. Supply chain performance will be tracked using the table below, updated bi-monthly. This includes items 12. a. through 12. e. for subcontracts.

Part

Description Supplier Leadtime

Original

Date

(on contract)

Delivery

Date

Need date

Slack

(days)

Affected

Constraint T ec h n ic al

S ch ed u le

C o n tr ac t

13. A list of actions requested of GSFC management

14. Update of corporate changes, for example: early warning of

a. Restructuring activities (including internal reorganizations)

b. Indirect/direct rate changes

15. Risk assessment including approach for mitigation https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

16. Any additional data requested by GSFC (For example, a few slides of detailed technical progress or issues) https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

RESOURCE MANAGEMENT

RM-3 DETAILED SCHEDULES

Title:

DETAILED SCHEDULES

DID for

CDRL No.

RM-3

Reference:

XRIS SOW Section 4.2 and 4.6

Purpose:

For understanding and mapping out in detail the most efficient way of melding together all elements necessary for providing the program deliverables by their required delivery times.

Preparation Information:

1. The schedule shall encompass all phases of the program indicating critical path and schedule slack and reserve.

2. The contractor shall establish, implement, and maintain an instrument schedule. Each

Flight Model (FM) development and delivery shall be tracked in the schedule.

3. Phase 1 schedules shall include the instrument and GSE design, the Program

Reviews, fabrication and test of the Engineering Development Unit (EDU) and GSE.

4. Phase 2 schedules shall include the fabrication, test, calibration, and delivery of the

Flight Model (FM) instrument and its integration to the SOLAR spacecraft.

5. Design schedules shall be detailed by task with expected start and completion dates.

6. Procurement schedules shall be detailed by major items, assembly, or definable subassembly.

7. Procurement schedules shall be subdivided into standard electrical parts, integrated circuits, etc.

8. Fabrication schedules shall be detailed to the mechanical subassembly level and to the electronic board level, and show the expected start and completion dates, as well as substantive in-process milestones.

9. Detailed schedules shall indicate critical paths.

10. Detailed schedules shall indicate slack and reserve.

REVIEW DATA ITEM DESCRIPTIONS

RVW-1 FORMAL REVIEW DATA PACKAGE

Title:

FORMAL REVIEW DATA PACKAGE

DID for CDRL No.

RVW-1

Reference:

XRIS SOW Section 4.5.4.1 – 4.5.4.5 https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

To demonstrate the instrument meets the entrance and exit criteria of NPR 7123.1D Appendix

G.

Preparation Information:

Each formal review data package shall provide sufficient information to meet entrance and exit criteria as required by NPR 7123.1D Appendix G.

For reference, GSFC-STD-1001A provides guidelines and criteria in support of planning and implementing the project reviews.

SYSTEMS ENGINEERING DATA ITEM DESCRIPTIONS

SE-3 XRIS SYSTEM SPECIFICATION

XRIS SYSTEM SPECIFICATION

DID for CDRL No.

SE-3

Reference:

XRIS SOW Section 5

Purpose:

The System Specification defines the contractor’s software and hardware requirements for the

Instrument and Ground Support Equipment in order to assure that the contractor is performing in accordance with the XRIS Requirements Specification

Preparation Information:

1. The XRIS System Specification shall include derived requirements from the XRIS

Requirements Specification and if contractor identifies other contractual requirements that should be included.

2. The XRIS System Specification shall be delivered in an Excel formatted file or in the

ReqIF (Requirements Interchange Format).

3. The XRIS System Specification shall include a Requirements Traceability Matrix.

4. The Requirements Traceability Matrix shall include an impacts field identifying all systems and subsystems that may be affected by a proposed change to this requirement.

5. The Requirements Traceability Matrix shall include an interface impacts field identifying all systems and subsystems that may be affected by a proposed change to this requirement due to an interface association.

https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

6. The Requirements Traceability Matrix shall include identification of the parent requirement.

SE-4 DETAILED DESIGN SPECIFICATIONS

Title:

DETAILED DESIGN SPECIFICATIONS

DID for CDRL No.

SE-4

Reference:

XRIS SOW Section 5.1, 6.1, and 6.3

Purpose:

To evaluate the contractor’s flow down of design requirements from the system level to subassembly and CSU level.

Preparation Information:

1. The Detailed Design Specifications shall provide the hardware and software specifications to be used by the contractor to direct the development of the Instrument and ground support equipment.

2. The Detailed Design Specifications shall consist of separate specifications as appropriate.

3. The Detailed Design Specifications shall include engineering requirements down to the subassembly level and as needed to the part level.

4. The Detailed Design Specifications shall include interface requirements internal and external to XRIS. (Separate Interface Requirements Specifications should be used where appropriate.)

5. The Detailed Design Specifications shall include operational parameters and requirements.

6. The Detailed Design Specifications shall include safety and assurance requirements.

7. The Detailed Design Specifications shall include software requirements to the CSU level.

8. The Detailed Design Specifications shall include unique identifiers for each requirement.

9. The Detailed Design Specifications shall include traceability matrices identifying parent requirements and any requirements impacted by a change in the requirement.

SE-5 THERMAL MATH MODEL AND REPORTS

Title:

THERMAL MATH MODELS AND REPORTS

DID for CDRL No.

SE-5

Reference:

XRIS SOW Section 5.3 and 6.3.2.5

Purpose:

Establish the thermal analytical model of the XRIS for the SOLAR mission, to provide review of these analytical tools which form the basis and analytical validation of the thermal design, https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

and which constitute an accurate representation of the instrument thermal performance in orbit. Reduced thermal analytical models are required for integrated mission thermal analyses.

A report will be created to evaluate the adequacy of the thermal design to meet requirements, both explicit and derived, under worst-case hot and cold environments for all mission phases and operating modes

Preparation Information:

1. The Thermal Math Model shall include:

a. A Detailed Thermal Model of the instruments and options

b. A Reduced Thermal Model of the instrument

2. Both the Detail Thermal Model and the Reduced Thermal Model shall include geometric math models (GMM), which calculate radiation couplings and environmental heat fluxes, and a thermal math models (TMM), or nodal models which calculate the heat transfer and resultant temperatures.

3. The Detailed and Reduced GMM shall be in Thermal Desktop format.

4. The Detailed and Reduced TMMs shall be in The Systems Improved Numerical

Differencing Analyzer 85 (SINDA85) format.

5. Thermal Math Models shall support both steady-state and transient solutions.

6. Thermal Math Models shall represent all flight environments and mission modes from pre- launch through the entire mission life, as well as model the environments of the thermal balance and thermal vacuum tests.

7. Thermal Math Models Report shall include the files and description of any special analytical routines or techniques, e.g., for representing heater or other temperature control features.

8. Any nodes or surfaces using adiabatic surfaces or arithmetic nodes (zero mass nodes) shall be noted.

9. Thermal Math Models Report shall include figures showing at least the overall layout of the instrument with dimensions, and with significant features of the thermal control system identified (e.g., radiators, insulation, apertures).

10. Thermal Math Models Report shall include figures or sketches showing how nodes and surfaces correspond to instrument components.

11. Thermal Math Models Report shall include results of sample run (of the hot case, EOL).

12.

SE-6 STRUCTURAL MATH MODEL AND REPORTS

STRUCTURAL MATH MODEL AND REPORTS

DID for CDRL No.

SE-6

Reference:

https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

XRIS SOW Section 5.3 and 6.3.2.2

Purpose:

To provide instrument interface information for coupled loads analysis by spacecraft contractor for both launch loads and on orbit jitter.

Preparation Information:

1. The structural math model shall include a full order structural math model.

2. The full order structural math model shall be MSC/NASTRAN compatible.

3. The structural math models shall provide models of the instrument in launch configuration.

4. The Structural Math Model Reports shall document the math models with the following information:

a. Configuration version

b. Identification of the documents and drawings used to generate the model

c. Model mass properties

d. Boundary conditions

e. Figures showing the components modeled

f. References used for mechanical properties

g. A summary of output results including modal frequencies, deflections and critical stresses.

h. Undeformed and deformed plots of the FEM https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

SE-7 SOLID MATH MODEL

SOLID MATH MODEL

DID for CDRL No.

SE-7

Reference:

XRIS SOW Section 5.3 and 6.3.2.2

Purpose:

Used by the spacecraft contractor to check envelope and field-of-view constraints.

Government will use for independent verification of constraints.

Preparation Information:

1. Solid math model shall be delivered in its native and Standard for the Exchange of

Product (STEP) format.

SE-9 SYSTEM PERFORMANCE VERIFICATION PLAN

Title:

SYSTEM PERFORMANCE VERIFICATION PLAN

DID for CDRL No.

SE-9

Reference:

XRIS SOW Section 5.1 and 6.3.2

Purpose:

Provides a description of the XRIS performance and verification test program and describes the specific tests and/or analysis that will collectively demonstrate that the hardware/software complies with the performance and environmental requirements.

Preparation Information:

1. The Performance Verification Plan shall describe the approach (test, analysis, etc.)

that will be used to verify the hardware/software complies with requirements.

2. The Performance Verification Plan shall address the environmental verification program either as a separate section or as a separate stand-alone document.

3. The environmental verification section of the Performance Verification Plan shall describe the contractor's approach for qualification and acceptance testing. It is intended to provide general test philosophy and an overview of the system-level environmental testing to be performed to demonstrate adequacy of the instrument for flight (e.g., vibration, shock, thermal vacuum, etc.).

4. If performance or environmental verification is performed at level of assembly other than instrument, the Performance Verification plan shall describe the relationship of the test and analysis to instrument level verification.

5. The Performance Verification Plan shall address any limitations in the ability to verify any performance or environmental requirement along with a risk assessment of the inability to verify the requirement.

6. Where requirements are verified by analysis, the Performance Verification Plan shall include objectives, a description of the mathematical model, assumptions on which https://ipdtdms.gsfc.nasa.gov/documentation/?id=237425&type=1&doc=L1SERIES-MAG-REQ-0013-MAG-Contract-Data-Requirements-List

Check the SOLAR CM tool Server at https://ipdtdms.gsfc.nasa.gov/ to verify that this is the correct version prior to use.

the models will be based, required output, criteria for assessing the acceptability of the results, the interaction with related test activity, if any, and requirements for reports.

7. The Performance Verification Plan shall contain detailed test flow sequence charts showing sequence of development and instrument level testing, including integration and qualification/acceptance test activities for the instrument and instrument assemblies.

8. The Performance Verification shall indicate in the test flows where Comprehensive and Limited Performance Tests will be conducted.

9. The Performance Verification…