Attachment C - CDRL - L1 Series MAG 01-11-2024.pdf

Effective Date: January 11, 2024 Expiration Date: January 11, 2029

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

L1SERIES-MAG-REQ-0025 Revision A Space Weather Next L1 Series Project, Code 493

Space Weather Next (SW Next) Program

Lagrange (L1) Series Project Magnetometer (MAG)

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 SW Next L1 Series CMO

January 12, 2024

Released

L1 Series Project MAG CDRL L1SERIES-MAG-REQ-0025, Revision A ii Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

L1 Series Project Magnetometer Contract Deliverables Requirements List (CDRL)

Signature/Approval Page

Prepared by:

Originally signed on 1/12/2024 by:

Alejandra Constante SW Next L1 Series Magnetometer Instrument Engineer NASA Goddard Space Flight Center

Reviewed by:

Originally signed on 1/12/2024 by:

Hudson DeLee SW Next L1 Series Instrument Systems Manager

Approved by:

Originally signed 1/12/2024 by:

Brennan Nowak Deputy Project Manager, SW Next L1 Series

Originally signed 1/12/2024 by:

J. Timothy Van Sant Project Manager, SW Next L1 Series iii Check the L1 Series 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 L1 Series Program configuration control. Once this document is approved, L1 Series approved changes are handled in accordance with Class I and Class II change control requirements as described in the L1 Series 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:

L1 Series Configuration Management Office

NASA/GSFC

Code 493 Greenbelt, MD 20771 iv Check the L1 Series 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 - December 1, 2023 This was CCR L1SERIES-CCR-0023 to baseline the document and was approved on December 1, 2023.

Rev – Chg 01 December 20, 2023 This was CCR L1SERIES-CCR-0046 to review the changes to document and was approved on December 20, 2023.

Revision A January 12, 2024 This was CCR L1SERIES-CCR-0053 to review the changes to the document and was approved on January 11, 2024 v Check the L1 Series CM tool Server at https://ipdtdms.gsfc nasa.gov/ to verify that this is the correct version prior to use.

Table of Contents

1 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 MAG CONTRACT DELIVERABLES REQUIREMENTS LIST (CDRL)

1.3 DATA ITEM DESCRIPTION (DID) OVERVIEW

1.4 DELIVERY INSTRUCTIONS

1.5 CDRL ITEMS OVEVIEW

2 PROGRAM DATA ITEM DESCRIPTIONS

PM-1 PROGRAM MANAGEMENT PLAN

PM-2 WEEKLY STATUS REPORTS AND TELECON MINUTES

PM-3 CONFIGURATION MANAGEMENT PLAN

PM-4 CONFIGURATION CHANGE REQUESTS (CCR) CLASS I

PM-5 PROGRAM MANAGEMENT STATUS REVIEW DATA PACKAGE

PM-6 RISK MANAGEMENT PLAN

PM-7 NASA PROPERTY IN THE CUSTODY OF THE CONTRACTORS

PM-8 CONTRACTOR TASK PLAN

PM-9 DOCUMENT TREE

3 RESOURCE MANAGEMENT

RM-1 MONTHLY AND QUARTERLY FINANCIAL REPORT

RM-2 CONTRACTOR’S WBS DIAGRAM AND DICTIONARY

RM-3 DETAILED SCHEDULES

4 REVIEW DATA ITEM DESCRIPTIONS

RVW-1 SYSTEM DEFINITION REVIEW (SDR) DATA PACKAGE

RVW-2 PRELIMINARY DESIGN REVIEW (PDR) DATA PACKAGE

RVW-3 CRITICAL DESIGN REVIEW (CDR) DATA PACKAGE

RVW-4 PRE-ENVIRONMENTAL REVIEW (PER) DATA PACKAGE

RVW-5 PRE-STORAGE/PRE-SHIP REVIEW (PSR) DATA PACKAGE

RVW-6 SUBSYSTEM REVIEW MINUTES AND ACTION ITEMS

RVW-7 RESPONSES TO REQUEST FOR ACTIONS

RVW-8 SUBCONTRACT AND SUBSYSTEM REVIEW DATA PACKAGES

5 SYSTEMS ENGINEERING DATA ITEM DESCRIPTIONS

SE-1 SYSTEMS ENGINEERING MANAGEMENT PLAN

SE-2 ENGINEERING ANALYSES REPORTS

SE-3 MAG 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-8 INSTRUMENT BLOCK DIAGRAMS, AND APPROVED OR CONTROLLED

DRAWINGS

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

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-17 COMPONENT AND SUBASSEMBLY TEST REPORTS FOR ALL

SUBCONTRACTED ITEMS

SE-18 EMC/EMI COMPATIBILITY PLAN

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

EMULATOR

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

FABRICATED, OR FLOWN HARDWARE

6 MISSION ASSURANCE AND SAFETY DATA ITEM DESCRIPTIONS

MA 1-1 MISSION ASSURANCE REQUIREMENTS COMPLIANCE MATRIX

MA 1-2 SUPPLIER LIST

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

(EOMP)

MA 2-2 NON-CONFORMANCE REPORT ............................ Error! Bookmark not defined.

MA 3-1 SYSTEM SAFETY PLAN (SSP)

MA 3-2 SAFETY REQUIREMENTS COMPLIANCE CHECKLIST

MA 3-3 OPERATIONS HAZARD ANALYSIS AND HAZARD VERIFICATiON

TRACKING LOG

MA 3-4 INSTRUMENT SAFETY ASSESSMENT REPORT

MA 3-5 HAZARDOUS PROCEDURES FOR PAYLOAD I&T AND PRELAUNCH

PROCESSING

MA 3-6 PRE-MISHAP PLAN

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

CRITICALITY ITEMS LIST

MA 4-3 FAULT TREE ANALYSIS

MA 4-4 RELIABILITY PREDICTIONS

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 6-1 ELECTROSTATIC DISCHARGE CONTROL (ESD)PLAN

MA 6-2 PRINTED CIRCUIT BOARD (PCB) PROCUREMENT PLAN

MA 6-5 LEAD-FREE CONTROL PLAN (LFCP)

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 8-1 MATERIALS & PROCESSES SELECTION, CONTROL, AND

IMPLEMENTATION PLAN

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

MA 8-2 MATERIALS USAGE AGREEMENT

MA 8-3 MATERIALS IDENTIFICATION AND USAGE LIST

MA 8-4 LIFE TEST PLAN AND FINAL REPORT FOR LUBRICATED MECHANISMS . 75

MA 8-5 ADDITIVE MANUFACTURING CONTROL PLAN (AMCP)

MA 8-6 AM PRODUCTION PLAN (PPP)

MA 9-1 CONTAMINATION CONTROL PLAN

MA 9-2 FOREIGN OBJECT DEBRIS PROGRAM

MA 11-1 GIDEP ALERTS/NASA ADVISORY DISPOSITIONS

MA 11-2 INITIATING GIDEP ALERTS

MA 12-1 END ITEM ACCEPTANCE DATA PACKAGE

7 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-7 TREND ANALYSIS PLAN AND DATA REPORTS

OPS-8 ON-SITE DATA ANALYSIS REPORTS

OPS-9 MASS PROPERTIES AND POWER REPORT

OPS-10 MAG PACKETIZED DATA

OPS-11 INSTRUMENT OPERATIONS CONFIGURABLE ITEMS

8 SOFTWARE DATA ITEM DESCRIPTIONS

SW-1 SOFTWARE MANAGEMENT PLAN

SW-2 SOFTWARE DELIVERY PACKAGES

9 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

10 FPGA DATA ITEM DELIVERABLE

FW-1 FPGA DEVELOPMENT PLAN

FW-2 FPGA DESIGN DATA PACKAGE

11 MAG HARDWARE/SOFTWARE DELIVERABLE ITEMS

APPENDIX A ABBREVIATIONS AND ACRONYMS

APPENDIX B RECCOMMENDED OPERATING PROCEDURES (ROPS) TEMPLATE

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

1 INTRODUCTION

This Space Weather Next (SW Next) Lagrange 1 (L1) Series (L1 Series) Instrument Contract Deliverables Requirements List (CDRL) document defines the requirements for deliverable items to be provided by the L1 Series Magnetometer (MAG) 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 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. If the Government disapproves, the requirement for resubmission by the Contractor shall be as specified by the Government Contracting Officer. 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, the Contractor may proceed with the associated work after notifying the Government of the intention to proceed.

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

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 MAG 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 MAG 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 L1 Series specified web portal unless otherwise noted in the MAG 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

b. Presentations: PDF (searchable) or PowerPoint

c. Spreadsheets: Microsoft Excel

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

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

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 OVEVIEW

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 OPS Operations SW Software I&T Integration and Test FW FPGA Development Plan

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

b. Requirements Reference: The reference indicates the section of the L1 Series 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 L1 Series MAG Contract Deliverables Requirements List (CDRL)

CRDL No. SOW Title Delivery Flight Model

Purpose

PM-1 4.1. Program Management Plan Preliminary: 30 DACA

Final: PDR+14 days Both R

PM-2 4.1

Weekly Status Reports and

Telecon Minutes Weekly Both I

PM-3 4.4.1

Configuration Management

Plan Preliminary: 15 DACA Final: PDR + 14 days

FM1 A

PM-4 4.4.1

Configuration Change

Requests (CCR) Class I As generated Both A

PM-5

4.1

4.5.9 Program Management

Status Review Data Package Bi-monthly Both I

PM-6

4.1 4.7

Risk Management Plan Preliminary: 30 DACA Final: PDR + 14 days

FM1 R

PM-7 4.2

NASA Property in the

Custody of the Contractors

Per Contract Clause 1852.245-73, Oct. 15, of each contract year for prior year. Final at contract closeout.

Both R

PM-8 1.1 Contractor Task Plan Per the contract ordering mechanism for Special

Studies (only required once Both R

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

2 PROGRAM DATA ITEM DESCRIPTIONS

PM-1 PROGRAM MANAGEMENT PLAN

Title:

Program Management Plan

DID for CDRL No.

PM-1

Reference:

MAG 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 Program Management Plan shall address the overall organization, management approach, and structure of the MAG Program plus its interrelationships with the parent company and the subcontractors, and relationship with the Government.

2. The Program Management Plan shall delineate how the requirements of the Statement of Work (SOW) will be achieved and include a description of planned activities for identifiable SOW requirements.

3. The Program Management Plan shall address interfaces with the Government and with any Government Furnished Equipment (GFE) suppliers.

4. The Program Management Plan shall indicate critical paths, long-lead items and significant milestones down to the lowest level of the WBS.

5. The Program Management Plan shall indicate the need for additional definition of spacecraft and mission information, and when this information is required to avoid schedule slippage.

6. The Program Management Plan shall include graphical displays such as flow diagrams, WBS, logic networks, etc., to reduce verbal descriptive material.

7. The Program Management Plan shall provide an organizational chart(s) and sufficient supplemental narrative to describe fully the organization proposed for carrying out the program showing inter- relationships of technical management, business management, and subcontract management, from lower level through intermediate management to top-level management with detailed explanation of:

a. The authority of the MAG Program Manager relative to other ongoing 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.

b. How and by whom interdepartmental work will be monitored and the authority of the program manager over interdepartmental work.

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

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

d. The lead program team members with names, functions, and qualifications

8. The Program Management Plan shall provide contractual procedures proposed for the program to effect administrative and engineering changes, describing any differences from existing procedures.

9. The Program Management Plan shall describe management techniques to be employed in minimizing program costs and schedule impacts, including controls to be exercised over subcontractors and suppliers.

10. The Program Management Plan shall describe how issues will be surfaced in a timely manner and at the proper levels.

11. The Program Management Plan shall describe how supply chain performance will be tracked.

12. The Program Management Plan shall discuss and illustrate the proposed MAG Mission Assurance organizational structure, including staffing plans, reporting channels, authority and responsibilities, and management visibility.

13. The Program Management Plan shall discuss whether the technical, test, manufacturing and system safety/quality assurance/ reliability/ configuration management personnel required for this program (as indicated in your proposed labor hours) are presently on payroll and immediately available for this work.

14. The Program Management Plan shall state the number and kind of persons who would have to be hired and plans to obtain them.

15. The Program Management Plan shall describe how the schedules are developed, maintained and updated.

16. The Program Management Plan shall describe how subcontracts will be managed and reviewed and describe the performance milestones of each.

17. The Program Management Plan shall list and describe the planned subsystem reviews.

PM-2 WEEKLY STATUS REPORTS AND TELECON MINUTES

Title:

WEEKLY STATUS REPORTS AND TELECON MINUTES

DID for CDRL No.

PM-2

Reference:

MAG SOW Section 4.1 Purpose:

Contract status evaluation.

Preparation Information:

1. The Weekly Status Report shall indicate the status of the contract as of close of business the preceding Friday, including a summary of progress made.

2. The Weekly Status Report shall address the work completed during the week against the work planned for the week, and address recovery plans if necessary.

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

3. The Weekly Status Report shall include technical progress, including significant accomplishments and milestones reached.

4. The Weekly Status Report shall include problems encountered and proposed corrective action.

5. The Weekly Status Report shall indicate any actual or anticipated slip in schedule.

6. The Weekly Status Report shall include identification of any Class I or Class II changes.

7. The Weekly Status Report shall detail the work planned for the next week and summarize the work planned for the next month.

8. The Weekly Status Report shall contain Action Item Status for any overdue action items and any action items due in the next two weeks.

9. The Weekly Status Report shall contain status of any open Non-Conformance Reports.

10. The Weekly Status Report shall contain status on any open contract actions, including Special Engineering Analyses.

11. The Weekly Status Report shall contain status on any red risk item.

Note: This weekly report is intended to be timely and informal and should detail the above topics as changes or problems occur.

PM-3 CONFIGURATION MANAGEMENT PLAN

Title:

CONFIGURATION MANAGEMENT PLAN

DID for CDRL No.

PM-3

Reference:

MAG SOW Section 4.4.1 Purpose:

To define the contractor’s configuration management system and provide a means of control for all changes affecting form, fit, or function and any impact on performance, cost, or schedule.

Preparation Information:

1. The Configuration Management Plan shall describe the scope, approach, methods, and procedures of the system used to control changes of requirements, design, and any other configuration managed item.

2. The Configuration Management Plan shall describe the organization of the configuration management program and how it relates to the rest of the MAG program.

3. The Configuration Management Plan shall list all tools used for configuration management.

4. The Configuration Management Plan shall use the following product change classifications:

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

a. A change or request for Deviation/Waiver is classified as Class I when it affects one or more of the following factors:

i. Program baseline documentation

ii. Technical requirements contained in the product configuration identification, including the following:

1. Form, fit, or function

2. Performance

3. Power

4. Reliability outside stated requirements

5. Weight, balance, moment of inertia

6. Interface characteristics

7. Hardware and process qualifications

iii. Non-technical contractual provisions

1. Fee

2. Incentives

3. Cost

4. Schedule

5. Guarantees or deliveries

iv. Other factors

1. Government-furnished property (GFP)

2. Safety

3. Electromagnetic characteristics

4. Deliverable operational, test, or maintenance computer programs

5. Compatibility with support equipment

b. A change is classified as Class II when it does not fall within the definition of a Class I change.

PM-4 CONFIGURATION CHANGE REQUESTS (CCR) CLASS I

CONFIGURATION CHANGE REQUESTS (CCR) CLASS I

DID for CDRL No.

PM-4

Reference:

MAG SOW Section 4.4.1 Purpose:

Class I changes are to be used as a vehicle for orderly processing of change requests to appropriate level of approval authority for disposition.

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

Preparation Information:

Class I Configuration Change Requests shall document proposed changes impacting form, fit, function, cost, schedules, or performance per the Configuration Management Plan or per the Software Configuration Management Plan section of the Software Management Plan.

PM-5 PROGRAM MANAGEMENT STATUS REVIEW DATA PACKAGE

PROGRAM MANAGEMENT STATUS REVIEW DATA PACKAGE

DID for CDRL No.

PM-5

Reference:

MAG SOW Section 4.1 and 4.5.9 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

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. Financial summary including a summary of actuals versus planned manpower

12. Subcontractor status including:

a. Efforts under contract

b. Efforts waiting contract award

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

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 hn ic al

S ch ed ul e

C on 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

16. Any additional data requested by GSFC

PM-6 RISK MANAGEMENT PLAN

Title:

RISK MANAGEMENT PLAN

DID for CDRL No.

PM-6

Reference:

MAG SOW Section 4.1 and 4.7 Purpose:

To describe the methodologies and processes used to identify, analyze, plan, track, control and communicate the contractor’s risks. The identification, characterization, mitigation plan, and mitigation responsibilities associated with specific risks are described and specific risk abatement strategies or contingency planning processes are discussed. “Risk” refers to anything that can prevent a team from meeting the Delivery Order objectives.

Preparation Information:

1. The Risk Management Plan shall document the process the Contractor will follow to manage risk throughout the life cycle of MAG. This includes technical performance, programmatic, cost, and schedule risks.

2. The Risk Management Plan shall provide descriptions of the processes to provide management at all levels with 1) a disciplined system for early identification of

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

technical uncertainties, 2) a disciplined assessment of current program status, and 3) key indicators of mission success.

3. The Risk Management Plan shall describe the basis for taking action to control risk and for measuring the effectiveness of that action.

4. The Risk Management Plan shall be tailored from NPR 8000.4 and cover:

a) Overview of Risk Management Process

b) Process Details

1) Risk identification - The process to determine and define all risks.

2) Risk analysis - The process to convert risk data into decision-making information. This process should include estimating the probability, impact and time frame of the risks, eliminating duplicates and grouping similar risks, and prioritizing them according to consequences.

3) Risk planning - The process to develop mitigation options and decide what to do with the risks.

4) Risk tracking - The process to acquire, compile and report risk status data, including risk indicators and mitigation actions.

Appropriate risk metrics should be identified so that the Government can evaluate the quality of the risk management.

5) Risk control - The process covering decisions to re-plan mitigation, close risks, invoke contingency plans or continue to track risks. The plan should define responsibilities, typical milestones/reviews, and describe the key risk control activities.

6) Communications and documentation - Present in all the above processes, this is the means by which the output of the processes is documented and communicated to all team members.

5. Risk Information Documentation

6. Constraints and De-scope options

7. For the Top Risks, risks having both a high probability and high impact/severity, the plan shall require, the following (see NPR 8000.4):

a) Description of the risk

b) Primary consequence should the undesirable event occur

c) Estimate of probability of occurrence and the fidelity of the estimate

d) Significant cost impacts, given its occurrence

e) Significant schedule impacts, given its occurrence

f) Potential mitigation measure not already taken and the cost to implement them

g) Characterization of the risk as acceptable or unacceptable with rationale

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

PM-7 NASA PROPERTY IN THE CUSTODY OF THE CONTRACTORS

Title:

NASA PROPERTY IN THE CUSTODY OF THE CONTRACTORS

DID for CDRL No.

PM-7

Reference:

MAG SOW Section 4.2 Purpose:

For budget, cost, and property control Preparation Information:

The NASA Property in the Custody of the Contractors report shall consist of NASA Form 1018 in accordance with NFS 1845.505-14, the instructions on the form, subpart 1845.71, and any supplemental instructions for the current reporting period issued by NASA.

PM-8 CONTRACTOR TASK PLAN

CONTRACTOR TASK PLAN

DID for CDRL No.

PM-8

Reference:

MAG SOW Section 1.1 Purpose:

The task plan is the contractor's resources plan for accomplishing the work described in the task order.

Preparation Information:

The Contractor Task Plan shall be prepared in accordance with the contract ordering mechanism for Special Studies.

PM-9 DOCUMENT TREE

DOCUMENT TREE

DID for CDRL No.

PM-9

Reference:

MAG SOW Section 4.1 Purpose:

For ready reference list of all MAG and GSE documents.

Preparation Information:

1. The document tree shall list all documents for the MAG and separately for the GSE.

2. The document trees shall be organized and identified to serve as a ready reference list.

3. The document tree shall identify documents by name and number.

4. The document tree shall include a brief description defining the scope of each document

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

3 RESOURCE MANAGEMENT

RM-1 MONTHLY AND QUARTERLY FINANCIAL REPORT

Title:

MONTHLY AND QUARTERLY FINANCIAL REPORT

DID for CDRL No.

RM-2

Reference:

MAG SOW Section 4.5 Purpose:

For budget and cost control Preparation Information:

1. The Monthly Financial Report shall be prepared in accordance with NFS 1852.242-73 and NPR 9501.2D, NASA Contractor Financial Management Reporting on NASA Form 533M.

2. The Monthly Financial Report shall be submitted within 15 days of the end of the reporting period.

3. The Quarterly Financial Report shall be prepared in accordance with NFS 1852.242-73 and NPR 9501.D, NASA Contractor Financial Management Reporting on NASA Form 533Q. The report is due 2 weeks prior to the period being reported.

4. At a minimum, the reporting structure shall be in accordance with and to Level 1 of the WBS as set forth in Attachment J.

5. The reporting categories shall include as a minimum:

a. Direct labor by labor category

b. Overhead

c. Fringe Benefits

d. Materials

e. Material Overhead

f. Subcontracts

g. Travel

h. Other Direct Costs

i. Facilities Capital Cost of Money

j. Fee

k. Total Cost-Plus Fee

RM-2 CONTRACTOR’S WBS DIAGRAM AND DICTIONARY

Title:

CONTRACTOR’S WORK BREAKDOWN STRUCTURE DIAGRAM AND

DICTIONARY

DID for CDRL No.

RM-3

Reference:

MAG SOW Section 4.2 Purpose:

To facilitate program planning and control and for financial and technical reporting.

Preparation Information:

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

1. The Contractor's Work Breakdown Structure (WBS) Diagram shall document Government accepted changes to the Government WBS with an updated WBS diagram and description of task elements.

2. The Contractor's WBS Diagram shall define all work included in the MAG development life cycle.

3. The Contractor's WBS Diagram shall provide a framework for program work definition to a level of detail consistent with cost, schedule, technical, and risk oversight as desired by contractor's management.

4. The Contractor's WBS Diagram shall contain a companion WBS dictionary that narratively describes the overall structure and content of each individual element of the WBS.

RM-3 DETAILED SCHEDULES

Title:

DETAILED SCHEDULES

DID for CDRL No.

RM-4

Reference:

MAG SOW Section 4.4.1 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 Models (FMs) instruments and their integration to the L1 Series 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.

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

4 REVIEW DATA ITEM DESCRIPTIONS

RVW-1 SYSTEM DEFINITION REVIEW (SDR) DATA PACKAGE

Title:

SYSTEM DEFINITION REVIEW (SDR) DATA PACKAGE

DID for CDRL No.

RVW-1

Reference:

MAG SOW Section 4.5.4.1 Purpose:

To evaluate the requirements, requirements flow-down, and the operational concepts and to validate the realism of the functional and performance requirements and their congruence with the system configuration selected to conduct the mission.

Preparation Information:

1. The SDR Data Package shall discuss contractor system level requirements, rationale, and flow- down plans to lower-level requirements.

2. The SDR Data Package shall cover the MAG System Specification and the traceability matrix to applicable government requirements documents.

3. The SDR Data Package shall cover requirements for the MAG instruments (Flight Models), Ground Support Equipment, flight software, ground test software, and processing algorithm.

4. The SDR Data Package shall show how the current concept meets all government specified requirements including interface requirements.

5. The SDR Data Package shall identify any MAG technologies that are below Test Readiness Level (TRL) 6.

RVW-2 PRELIMINARY DESIGN REVIEW (PDR) DATA PACKAGE

PRELIMINARY DESIGN REVIEW (PDR) DATA PACKAGE

DID for CDRL No.

RVW-2

Reference:

MAG SOW Section 4.5.4.2 Purpose:

To demonstrate the Flight Equipment and GSE designs meet the documented requirements.

Preparation Information:

1. The PDR data package shall include Science/Technical Objectives, Requirements, and General Specification.

2. The PDR data package shall include responses to action items from previous reviews, including subsystem PDRs.

3. The PDR data package shall include changes since the last review.

4. The PDR data package shall address system performance budgets and margins.

5. The PDR data package shall include processor resource utilization estimates.

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

6. The PDR data package shall address mass, power, data rate, commands, Electromagnetic Compatibility (EMC) / Electromagnetic Interference (EMI).

7. The PDR data package shall address interface requirements.

8. The PDR data package shall address mechanical/structural design, analyses, and life tests.

9. The PDR data package shall address electrical, thermal, and sensor design and analyses.

10. The PDR data package shall address software requirements, design, and development environment.

11. The PDR data package shall address Ground Support Equipment design and workflow, and describe how each item will be fabricated, tested and certified when needed.

12. The PDR data package shall address design verification, test flow and calibration/test plans.

13. The PDR data package shall address instrument operations.

14. The PDR data package shall address parts selection, and qualification.

15. The PDR data package shall address preliminary Failure Modes Effects Analysis (FMEA)/Failure Modes, Effects, and Criticality Analysis (FMECA); Fault Tree Analysis; and reliability analysis and results.

16. The PDR data package shall address parts stress analysis.

17. The PDR Data Package shall address the list of long lead items, and of items that may become obsolete prior to completion of all flight instruments, identify those items that must be procured prior to CDR, and provide a plan for procuring these items and all parts.

18. The PDR data package shall address contamination requirements and control plan.

19. The PDR data package shall address safety hazards identified for flight, range, ground hardware and operations.

20. The PDR data package shall delineate the status of each document required at PDR as to its acceptability for use as is.

21. The PDR data package shall address open interface items.

22. The PDR Data Package shall present all program risks and address their mitigation.

23. The PDR Data Package shall provide the status of all subcontracts and discuss the preliminary design status of critical assemblies and sub-assemblies.

24. The PDR Data Package shall present a summary of all breadboard and brassboard testing and present the test results.

25. The PDR Data Package shall present the development status of sub-assembly engineering units, and available test data.

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

26. The PDR Data Package shall address mission assurance to be imposed including parts and materials usage as well and workmanship standards imposed.

27. The PDR Data Package shall address software assurance process.

28. The PDR data package shall contain information to cover the MAG ground algorithm design.

29. The PDR Data Package shall demonstrate that all MAG technologies have achieved a TRL 6 or higher.

RVW-3 CRITICAL DESIGN REVIEW (CDR) DATA PACKAGE

CRITICAL DESIGN REVIEW (CDR) DATA PACKAGE

DID for CDRL No.

RVW-3

Reference:

MAG SOW Section 4.5.4.3 Purpose:

To present the Flight Equipment and GSE design and operation and S/C interface aspects, to demonstrate that all related manufacturing documentation, processes, and fixtures are in place before hardware manufacture begins, and to demonstrate that the design meets all performance requirements.

Preparation Information:

1. The CDR data package shall include responses to action items from previous reviews, including subsystem CDRs.

2. The CDR data package shall include changes since the last design review.

3. The CDR Data Package shall address the procurement status of long lead items and Electrical, Electronic, and Electromechanical (EEE) parts.

4. The CDR Data Package shall address manufacturing flow, and the status of manufacturing and assembly drawings, bill of materials, etc.

5. The CDR Data Package shall address manufacturing procedures.

6. The CDR Data Package shall address mission assurance product checkpoints and evaluation criteria.

7. The CDR data package shall address the MAG ground algorithm design and development.

8. The CDR Data Package shall address standard applicable in-house processes.

9. The CDR Data Package shall address special/unique tooling and fixtures.

10. The CDR Data Package shall address facilities required for manufacturing.

11. The CDR Data Package shall address personnel resources (time phased).

12. The CDR Data Package shall address the delivery schedules for flight instruments and

GSE.

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

13. The CDR Data Package shall provide status of:

a) Performance specification (subsystems and GSE)

b) Block diagram and description of operation (instrument and GSE)

c) Schematic and logic diagrams (including waveforms, and timing)

d) Mechanical configuration drawings

e) Test procedures

f) Calibration procedures

g) GSE development

14. The CDR data package shall address detailed analysis from FMEA/FMECA, fault tree analysis, and reliability analysis.

15. The CDR data package shall address parts stress analysis.

16. The CDR Data Package shall address worst-case analyses of:

a) Electrical circuits

b) Tolerance and tolerance sensitivity analysis (including thermal and mechanical considerations)

17. The CDR Data Package shall address stress analyses using NASTRAN, or compatible tool, with hand stress analysis verification.

18. The CDR Data Package shall address the structural frequency and other dynamic analyses (including shock, sine sweep, and random, at a minimum).

19. The CDR Data Package shall address the thermal analysis.

20. The CDR Data Package shall address end-to-end system performance and margins.

21. The CDR Data Package shall address mass, power, data rate, commands, EMI/EMC.

22. The CDR data package shall include processor resource utilization estimates.

23. The CDR Data Package shall address test plans (including all environmental and calibration tests).

24. The CDR Data Package shall address manufacturing considerations.

25. The CDR Data Package shall address maintainability considerations.

26. The CDR Data Package shall address materials and processes lists.

27. The CDR Data Package shall provide a summary of deviations/waivers.

28. The CDR Data Package shall address contamination control and monitoring considerations.

29. The CDR Data Package shall address spares program.

30. The CDR Data Package shall address system safety hazards analyses.

a) Hazards identification matrix

b) Single point failure summaries

c) Risk assessment rationale

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

31. The CDR data package shall address open interface items and the status of the IDD.

32. The CDR Data Package shall present any additional test results from breadboard and brassboard testing.

33. The CDR Data Package shall present the test data from any engineering model.

34. The CDR Data Package shall address the status of all program risks and their mitigation.

35. The CDR Data Package shall address the status of all subcontract design activity and schedule for delivery of flight hardware and demonstrate that designs are complete and have been adequately reviewed.

RVW-4 PRE-ENVIRONMENTAL REVIEW (PER) DATA PACKAGE

Title:

PRE-ENVIRONMENTAL REVIEW (PER) DATA PACKAGE

DID for CDRL No.

RVW-4

Reference:

MAG SOW Section 4.5.4.4 Purpose:

Presents the description and results of the Pre-Environmental Test program and demonstrates readiness for environmental testing.

Preparation Information:

1. The PER Data Package shall include status of action items generated at prior reviews.

2. The PER Data Package shall include analyses and reports required at the review.

3. The PER Data Package shall include test and integration program descriptions and results.

4. The PER Data Package shall include Non-Conformance report summaries including status of actions and rationales for closure.

5. The PER Data Package shall include as-built documentation summary.

6. The PER Data Package shall include results of the functional and interface tests.

7. The PER Data Package shall include malfunctions and corrective actions.

8. The PER Data Package shall include comparison of measured performance with requirements and discussion of the effect of any variance and waivers.

9. The PER Data Package shall include mission operation constraints.

10. The PER Data Package shall include contamination avoidance requirements.

11. The PER Data Package shall include safety requirements.

12. The PER Data Package shall include list of spares for flight equipment and GSE.

13. The PER Data Package shall include review of instrument handling procedures.

14. The PER Data Package shall include interface concerns, problems and solutions.

15. The PER Data Package shall include orbital operations plans.

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

16. The PER Data Package shall include end-item data packages up to this point of the program (submit a summary of the content prior to review and have package available for inspection at review).

a) As-built configuration list

b) Hardware parts lists

c) Hardware materials and processes lists

d) Test Log Book (including total operating time and cycle records)

e) Open item lists (including reasons for being open)

f) Safety compliance data package

g) Limited life items listings and status

h) Critical parameters trend data

i) Final comprehensive performance test results (pre-environmental test results)

17. The PER Data Package shall discuss the compatibility of instrument with observatory flight support equipment, ground support equipment and operational ground equipment.

18. The PER Data Package shall include a description of the planned environmental testing.

19. The PER Data Package shall address the availability and readiness of facilities and GSE required for environmental testing.

20. The PER Data Package shall address the readiness of environmental test plans and procedures.

RVW-5 PRE-STORAGE/PRE-SHIP REVIEW (PSR) DATA PACKAGE

Title:

PRE-STORAGE/PRE-SHIP REVIEW (PSR) DATA PACKAGE

DID for CDRL No.

RVW-5

Reference:

MAG SOW Section 4.5.4.5 Purpose:

To evaluate system performance during qualification or acceptance testing and evaluate readiness to ship from contractor.

Preparation Information:

1. The Pre-Storage Review Data Package shall address responses to action items generated at prior reviews.

2. The Pre-Storage Review Data Package shall address the solutions to all problems encountered during the environmental test and validation program and the solution rationale.

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

3. The Pre-Storage Review Data Package shall address any rework/replacement of hardware, regression testing, or test plan changes should be highlighted during the test flow discussions.

4. The Pre-Storage Review Data Package shall address compliance with the test verification matrix.

5. The Pre-Storage Review Data Package shall address measured test margins versus design estimates.

6. The Pre-Storage Review Data Package…