NS1-SMBA-CDRL-0001C_01152026.pdf

Effective Date: January 15, 2026 Expiration Date: January 15, 2031

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

NS1-SMBA-CDRL-0001, Revision C Near Earth Orbit Network Series-1 Project, Code 473

Near Earth Orbit Network Series-1 Project

Sounder for Microwave-Based Applications

Contract Data Requirements List

NOAA/NASA

Goddard Space Flight Center Greenbelt, Maryland

GSFC NEON Series-1 CMO

RELEASED

NS1 SMBA CDRL NS1-SMBA-CDRL-0001, Revision C ii Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Near Earth Orbit Network Project Series-1 Sounder for Microwave-Based Applications

Contract Data Requirements List Review/Signature/Approval Page

Prepared By:

Jessica Knizhnik SMBA Instrument Manager NASA Goddard Space Flight Center

Approved By:

Jessica Knizhnik SMBA Instrument Manager NASA Goddard Space Flight Center

Risha George NEON Series-1 Project Manager NASA Goddard Space Flight Center

Electronic Approval available on-line at: https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm iii Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Preface

This document is under NEON Series-1 (NS1) Project configuration control. Once this document is approved, NS1 approved changes are handled in accordance with Class I and Class II change control requirements as described in the Low Earth Orbit (LEO) Programs Division (LPD) Programs and Projects Configuration Management Procedure (CMP), and changes to this document shall be made by complete revision.

Any questions should be addressed to:

LEO/NEON Configuration Management Office

NASA/GSFC

Code 473 Greenbelt, MD 20771 iv Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Change History Log

Revision Effective Date Description of Changes

Revision – December 20, 2024 This version incorporates 470-CCR-24-0404 which was approved by the SMBA ERB on March 26, 2024, and incorporates NS1-CCR-0004 by the NS1 SMBA CCB on the effective date shown.

Revision A April 1, 2025 This version incorporates NS1-CCR-0007 which was approved by the NS1 SMBA CCB on the effective date shown.

Removed duplicate language for UAR. Changed delivery date for MA-1.

Revision B August 19, 2025 This version incorporates NS1-CCR-0014 which was approved by the NS1 SMBA CCB on the effective date shown.

Revision C January 15, 2026 This version incorporates NS1-CCR-0017 which was approved by the NS1 SMBA CCB on the effective date shown.

v Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Table of Contents

1 INTRODUCTION

1.1 Scope

1.2 Export Control Limitations

1.3 Proprietary Data

1.4 Prior Submission Deliveries

1.5 Due Dates – Related Definitions

1.6 Media – Related Definitions

1.7 Category – Related Definitions

1.8 Applicability

1.9 Updates

1.10 Documentation Change Procedures

1.11 Delivery Instructions

2 DATA ITEM DESCRIPTIONS

2.1 Project Management Data Items

2.2 Review Data Items

2.3 Systems Engineering Data Items

2.4 Software Data Items

2.5 Integration and Test Data Items

2.6 Mission Assurance Data Items

2.7 Calibration/Validation Data Items

2.8 On-Orbit Data Items

APPENDIX A: ABBREVIATIONS AND ACRONYMS

List of Figures

Figure 1. Noise Power Spectral Density Curves

List of Tables

Table 1. Contract Deliverable Items List

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

1 INTRODUCTION

This contract data requirements list (CDRL) document defines the requirements for deliverable documentation to be provided by the Sounder for Microwave-Based Applications (SMBA) Contractor. Section 1 includes definitions and instructions for distribution. Table 1 presents the CDRL item by item, with due dates, quantity, and media format. Section 2 contains the data item descriptions (DID), descriptions of each item which provide the use for the deliverables and the required preparation information. Except where specifically indicated to the contrary, the formats and drawing standards used shall be those normally used by the Contractor and by its subcontractors.

1.1 Scope

The CDRLs within this document include those required for the development phase as well as the production phase, as indicated in Table 1. Though this document has been created for the Near Earth Orbit Network (NEON) Series-1 (NS1) project, the CDRLs, particularly those associated with the production phase, are applicable to subsequent projects within the NEON program.

1.2 Export Control Limitations

For Export Control limitations reference the Export License clause in the Contract.

1.3 Proprietary Data

For Proprietary Data requirements reference the Rights in Data clause in the Contract.

1.4 Prior Submission Deliveries

If new hardware, software, or documentation is developed, procured, designed, fabricated, tested, or processed in a different manner from that of the first SMBA flight Instrument effort (obsolescence, corrective actions, modifications, errors, etc.), the Contractor shall deliver the data item as required with the necessary updates for Government approval, reference, or information, as defined for each impacted deliverable herein.

1.5 Due Dates – Related Definitions

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

DUE DATE:

o CDR, PER, etc.: Critical Design Review (CDR), Pre-Environmental Review (PER), Pre-Ship Review (PSR), etc. (all Top-Level Instrument Reviews).

Electronic distribution to be delivered to the Government five working days prior to review, unless otherwise stated.

o Monthly: Submitted on monthly basis o L: Launch Date (Actual Launch Date) o DACA/(D): (Calendar) Days After Contract Award/(Definitization)

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

o ORR: Mission-Level Operational Readiness Review o PLAR: Post-Launch Assessment Review (at the completion of on-orbit commissioning)

MATURITY:

o Initial: The first submission of an item which is anticipated to be revised and resubmitted at a later date.

o Preliminary/Prelim: An early submission of an item. To be completed as is practicable at the time of preparation. Preliminary submittals are written with the best available current information and are resubmitted when further information becomes available.

o Final: The complete, thorough submission of an item for approval, review, or information that, to the best of the Contractor’s knowledge and intention, will not require further revision or updates. However, this does not preclude updating if later found to be necessary. Any updates shall require the same "approval/review" process as was required for the original submissions.

o Current: The delivery is written with the best up-to-date information available at the time.

o Update: The delivery is revised with the best up-to-date information available at the time.

Other entries in the "DUE DATE” and “MATURITY" columns are self-explanatory.

1.6 Media – Related Definitions

The following definitions apply to the deliverables in Table 1.

E – Data items shall be delivered in electronic format to a GSFC Low Earth Orbit (LEO) Programs Division (LPD) specified web portal unless otherwise noted in the CDRL DID. The Contracting Officer shall be notified of electronic submission of the deliverable via email.

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

Text Documents: PDF (searchable) or Microsoft Word

Presentations: PDF (searchable) or PowerPoint

Spreadsheets: Microsoft Excel

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

Schedules: PDF and Microsoft Project

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

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

Photographs: JPEG or current industry standard.

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

Measurement Data Delimited ASCII format or other acceptable format

In addition to deliveries in the required formats above, the Contractor may also provide additional copies of the same deliverables is other formats (e.g., .mdzip).

If separate distribution instructions are not specified for separate submission due date/maturity items, then the listed distribution applies to all submissions.

1.7 Category – Related Definitions

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

A Approval: CDRL items in this category require approval by the GSFC COR or Contracting

Officer prior to use by the Contractor. Receipt by the Government shall occur within the time specified in the "Due Date" column of Table 1 of this document. Requirements for resubmission shall be as specified by the Contracting Officer. For most cases the Contractor shall be required to resubmit the document within 14 calendar days of receiving comments from the Government. If the Contractor has not received response from the Government within 30 calendar days of delivery of a CDRL item, the Contractor may proceed as if the document has been approved.

I Information: Data in this category shall be delivered to the Government within the time period specified in the “Due Date” column of Table 1 for the purpose of determining current program status, progress, and future planning requirements.

1.8 Applicability

The "Applicability (APPLIC)" column in Table 1 indicates the Contract Line Item Numbers (CLIN) for which each CDRL is applicable and during which the CDRL is to be delivered. This is done by indicating Development [DEV], Production [PROD], or Task Order [TO] CLINs.

CLINs are associated with Development [DEV], Production [PROD], or Task Order [TO] per the Contract Clause GSFC 52.211-91, SCOPE OF WORK.

1.9 Updates

If the Government or Contractor determines that there is a Contractor-initiated substantive change and an update is needed to properly reflect the information previously delivered, the Contractor shall make the update and redeliver the CDRL independent of the quantity requirements in the CDRL table. The Contractor shall notify the Government of any pending updates and re-deliver the CDRL on a schedule agreed to by the Government. Table 1 does not specify this repetitious requirement; however it is required for each CDRL.

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

1.10 Documentation Change Procedures

Unless otherwise defined in the Statement of Work (SOW) or contract:

When a minor correction/change is needed or has been made to a few parts of a “Final” version of a CDRL item that has already been delivered to the Government, the Contractor shall issue within 30 days a Documentation Change Notice starting with the number 001. Change bars or “change tracking” shall be used to indicate the locations of changes unless the particular file type does not have those features available. If not available, the details of the changes will be described in a text file.

When a major correction/change is needed or has been made to all or multiple parts of a

“Final” version of a CDRL item that has already been delivered to the Government, the Contractor shall deliver within 30 days a complete revision of the CDRL item. A description of all changes incorporated into the new revision shall be included in the new document or otherwise documented. No change bars are used when a document is updated by revision, and the Documentation Change Notice numbers for that document shall be automatically recycled to 001.

1.11 Delivery Instructions

CDRL submissions shall be complete, unabridged, and unredacted. All CDRLs shall comply with the contract rights in data and export control clauses.

External documents referenced within a CDRL submission shall be made available virtually to the Government upon request.

The Contractor shall deliver each CDRL item via the media indicated in accordance with the schedule and any special instructions indicated in Table 1 and/or the corresponding DID, and in accordance with the contract or SOW requirements and provisions.

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 hardcopy upon mutual agreement between the Contractor and the Government.

All CDRL submittals shall be protected by encryption or through the use of other secure means approved by the Government against unauthorized disclosure including interception and decryption by foreign nationals. Prior to delivery, the Contractor shall implement all safeguards necessary to ensure data is protected in accordance with the Export Administration Regulations except when expressly authorized by a Technical Assistance Agreement.

The Contractor shall include a cover letter with the following information:

CDRL #

Title Due Date Flight Model Serial Number Original Submission Date

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Prior Delivery CDRL # Current Submission Revision Current Submission Revision Date

The Contractor may deliver a single letter for multiple submissions as long as the information above is contained in the letter for each deliverable item.

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Table 1. Contract Deliverable Items List

No. MANAGEMENT DUE DATE, MATURITY CAT APPLIC

PM-1 Monthly Project Management Reviews (PMR)

Monthly, 3 days prior to review I DEV, PROD, TO

PM-2 Engineering Peer Review (EPR) Plan

Initial: Development CLIN Kickoff

Final: 60 DACA

I

A

DEV

PM-3 Integrated Program Management Data and Analysis Report

(IPMDAR)

Initial: Draft Integrated Master Schedule with Proposal

Initial Baseline: 45 DACA

Baseline: 12th working day of the 3rd fiscal month after contract definitization

Monthly financials: by the 12th working day following the close of the prior month accounting period

PM-4 Integrated Master Schedule (IMS) Baseline: Production CLIN Kickoff

Monthly IMS snapshot no later than the 5th working day of the month

Monthly Final: By the 12th working day following the close of the prior month accounting period

PROD, TO

No. REVIEWS DUE DATE, MATURITY CAT APPLIC

RE-1 Kickoff Meeting Data Package Final: 14 DACA of CLIN I DEV, PROD

RE-2 System Requirements Review (SRR)/System Definition Review (SDR) Data Package

Final: 5 days prior to review I DEV

RE-3 Preliminary Design Review (PDR) Final: 5 days prior to review I DEV

NS1 SMBA CDRL NS1-SMBA-CDRL-0001, Revision C

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

RE-4 Critical Design Review (CDR) Final: 5 days prior to review I DEV

RE-5 Pre-Environmental Review

(PER)

Final: 5 days prior to review I DEV, PROD

RE-6 Pre-Ship Review (PSR) Data Package

Final: 5 days prior to review I DEV, PROD

RE-7 Integrated Baseline Review (IBR) Final: 5 days prior to review I DEV

RE-8 Engineering Peer Review Data Packages

Engineering Peer Review (EPR) Meeting Material : EPR -3 days

Final: Electronic or Hard copies at review

RE-9 Manufacturing Readiness Review Package

Final: 5 days prior to review I DEV, PROD

RE-10 Test Readiness Review (TRR) Data Package

Final: 5 days prior to review I DEV, PROD, TO

RE-11 Inputs to Project Level Reviews Final: 30 days prior to review I DEV, PROD, TO

No. SYSTEMS ENGINEERING DUE DATE, MATURITY CAT APPLIC

SE-1 System Performance Verification Plan (SPVP) and Matrix (SPVM)

Initial: SRR - 7 days

Final: CDR - 7 days

Update: PSR

DEV, PROD

SE-2 Trend and TPM Plan/Analysis, Reports, and Operations Log

Plan Initial: PDR

Plan Update: PER

Plan Final: PSR Analysis, Reports, and Logs delivered per the plan.

DEV, PROD,

TO

SE-3 Engineering Drawings Indentured Drawing List: Make Available Virtually at Top-Level Instrument Reviews

N/A DEV

NS1 SMBA CDRL NS1-SMBA-CDRL-0001, Revision C

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

SE-4 Engineering Change Requests Class I: As Generated A

SE-5 Instrument Performance Specification

Initial: SRR -7 days

Update: PDR - 7 days

Final: CDR - 7 days

I

I

I

DEV

SE-6 Structural and Mechanical Analysis and Models

Initial: PDR -30 days

Final: CDR -30 days

Correlated Model: PSR -30 days

SE-7 Thermal Analysis and Models Initial: PDR -30 days

Final: CDR -30 days

Correlated Model: PSR -30 days

SE-8 Contamination Analysis Report Initial: CDR

Final: PER

Update: PSR -30 days

I

I

I

DEV, PROD

SE-9 Electromagnetic Interference (EMI)/Electromagnetic Capability (EMC) Analysis Report

Initial: CDR – 7 days

Final: PSR -30 days

SE-10 Instrument Concept of Operations Document

Initial: SRR – 7 days

Final: PDR – 7 days

I

I

DEV

SE-11 Inputs to the Instrument to spacecraft Interface Control Document (ICD) including the Mechanical ICD

Initial: PDR

Final: CDR

SE-12 Field Programmable Gate Array (FPGA), Application Specific Integrated Circuit (ASIC), and

Initial: PDR -30 days

Final: CDR -45 days

NS1 SMBA CDRL NS1-SMBA-CDRL-0001, Revision C

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Programmable Logic Device (PLD) Circuitware Design Data Package

As generated for each FPGA/ASIC/PLD

SE-13 Mass Properties Report Final: PSR I DEV, PROD

SE-14 Spare Parts Plan and List Final: Development CLIN Kickoff A DEV

SE-15 Engineering Development Plan Initial: Development CLIN Kickoff

Final: SRR- 7 days

No. SOFTWARE DUE DATE, MATURITY CAT APPLIC

SW-1 Instrument Software Development Plan

Final: 30 DACA A DEV

SW-2 Software Detailed Design Document Initial: PDR-90 days

Final: CDR – 90 days

I

I

DEV

SW-3 FSW Version Description Document Final: 30 days after FSW acceptance test completion and with each FSW release/build

SW-4 Instrument Software Maintenance Plan

Final: PSR I DEV

SW-5 Instrument Data Sets Final: PSR I DEV, PROD, No. INTEGRATION AND TEST DUE DATE, MATURITY CAT APPLIC

IT-1 Instrument Integration, Test, and Verification Plan

Initial: PDR -7 days

Final: CDR -7 days

FM2 Update: Updated version prior to FM2 I&T based on lessons learned from the FM1

I

I

I

DEV

IT-2 Test Results/Reports Final: 10 days after test completion I DEV, PROD, NS1 SMBA CDRL NS1-SMBA-CDRL-0001, Revision C

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

IT-3 Test Procedures & As-Run Test Procedures

Pre-Test: 10 days prior to test

As-Run: Conclusion of each test + 7 days

Launch site-specific Test Procedures Initial: L -12 months

Final: L -3 months (i.e., SC PSR)

A for Pre-Test

I for As-Run

TO

IT-4 Instrument Post Delivery Support (PDS) Document

Initial: PSR -120 days

Final: PSR -7 days

No. MISSION ASSURANCE DUE DATE, MATURITY CAT APPLIC

MA-2 Orbital Debris Assessment Report (ODAR) and End of Mission Plan (EOMP)

Initial ODAR inputs: PDR -15 days

Interim ODAR and Draft EOMP inputs: CDR -60 days

Final/updated ODAR and EOMP inputs: PSR -90 days

MA-3 System Safety Plan Initial: SRR – 7 days

Final: PDR -45 days

Updates 30 days prior to implementation

I

I

I

DEV

MA-4 Safety Requirements Compliance Checklist

Initial: SRR -45 days

Final: PDR -45 days

Updates: CDR -45 days

TO

MA-5 Instrument Safety Assessment Report

Initial: PDR -30 days

Intermediate: CDR -30 days

Final (with VTL): PSR -45 days

NS1 SMBA CDRL NS1-SMBA-CDRL-0001, Revision C

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

MA-6 Failure Modes, Effects, and Criticality Analysis (FMECA) and Critical Items List (CIL)

Initial: PDR -30 days

Final: CDR -30 days

I

I

DEV

MA-7 Master EEE Parts List EEE parts to the Parts Control Board prior to inclusion

Updates prior to inclusion

MA-8 Materials Identification and Usage List (MIUL)

Initial: PDR -30 days

Final: CDR -30 days

Updates: 30 days after identification

I

I

I

DEV

MA-9 Life Test Plan and Final Report for Lubricated Mechanisms

Plan: PDR -30 days

Report: 30 days after acceptance test completion

I

I

DEV

MA-10 End Item Acceptance Data Package Component/Subsystem Final: EIDP for Critical Items (as identified in CDRL PM-2, EPR Plan) with delivery of the item

Initial: PSR -30 days

Final: 30 days prior to end item delivery

Updates: 30 days after identification

I (for crit.

comp/subsy)

No. CALIBRATION/VALIDATION DUE DATE, MATURITY CAT APPLIC

CV-1 Calibration/Validation Plan

Initial: PDR -30 days

Final: CDR -30 days

CV-2 Calibration/Validation Procedures Initial: 60 days prior to use

Final: 10 days prior to use

On-orbit Procedures

NS1 SMBA CDRL NS1-SMBA-CDRL-0001, Revision C

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Final: ORR -30 days Update: PLAR

A A

CV-3 Calibration/Validation Results Electronic Data: 3 days post-test

Test Report: 10 days post-test

Analyses: At completion + 10 days, NLT PSR

I

I

I

DEV, PROD

CV-4 Radiometric Math Model (RMM)/Sensor Performance Math Model (SPMM)

Initial: CDR -30 days

CV-5 Calibration Data Book Initial: CDR

Final: PSR

Update: after commissioning

TO

CV-6 Ground Processing Software Initial: CDR -30 days

CV-7 Spectral Response Function (SRF) Measurements

Final: PSR -7 days A DEV, PROD

CV-8 Hyperspectral Capability Test and Analysis

Initial: CDR

Final: PER -30 days

CV-9 Radio Frequency Interference Detection Capability Test and Analysis

Initial: CDR

Final: PER -30 days

No. ON ORBIT DUE DATE, MATURITY CAT APPLIC

OO-1 Instrument On-Orbit Commissioning Plan

Final: PSR -30 days I

OO-2 Instrument User’s Manual Initial: PER

Final: PSR

I

NS1 SMBA CDRL NS1-SMBA-CDRL-0001, Revision C

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

OO-3 Commissioning Report Initial: 10 Days after each test

Test Results: PLAR

Final: PLAR

I

I

I

DEV, PROD,

TO

OO-4 Command and Telemetry Handbook and Command and Telemetry Database (CTDB)

Initial: PER -30 days

Final: PSR -6 months

I

I

DEV, PROD

OO-5 Instrument Launch and On-Orbit Operations and Contingency Procedures

Final: PSR I DEV

OO-6 Instrument Simulator Users Guide Initial: CDR

Final: with shipment of the OpSim

I

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

2 DATA ITEM DESCRIPTIONS

2.1 Project Management Data Items

DATA ITEM DESCRIPTION

1. CDRL No.: 2. Title:

PM-1 MONTHLY PROJECT MANAGEMENT

REVIEWS (PMR)

1. Reference:

2. Use:

Serves as a primary means to enable project team insight into the SMBA contracted efforts and their status. These review packages will be used to both document status and various metrics with updates monthly and provide an opportunity for discussions between the Contractor and the Government regarding project status, plans, trends, risks, and issues.

3. Preparation Information:

The PMR shall include reporting across the full scope of contract effort including subcontractors’/suppliers’ efforts as appropriate to report the information required per this CDRL

DID.

The Monthly PMR shall include the following information in a format and organization defined by the Contractor:

Program Manager’s Assessment and Programmatic Overview (e.g., significant accomplishments, new/open/closed issues, significant upcoming events, significant changes in plans, etc.).

Significant or impactful problems encountered during the reporting period, and anticipated approaches for resolution (including, as appropriate, technical issues including hardware, software, and Ground Support Equipment (GSE) issues, manpower and staffing, and supplier and subcontractor issues, etc.); status of open issues and problems from prior reporting periods.

Risk status for top 10 risks (and all red risks) with mitigations plans and opportunities for each.

CDRL status for each document delivered in accordance with the CDRL or overdue from previous reporting periods and status of documents planned for delivery during the next reporting period.

NS1 SMBA CDRL NS1-SMBA-CDRL-0001, Revision C

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Key personnel changes.

Status of action items.

Summary of Integrated Master Schedule o Schedule and schedule performance status for the contracted effort that includes detail for each subsystem/subassembly o The Primary, Secondary, and Tertiary critical paths with any potential mitigation opportunities that are being considered to maintain the schedule o Critical Path and subsystems schedule reserve/slack trend metrics as jointly defined by the Contractor and Government

Control Milestone Trend Report – The Contractor shall provide a control milestone trend chart that consists of the baselined list of control milestones (determined by the Contractor and agreed to by the project office) and their baselined and projected or actual completion dates. The report will also contain a list of the control milestones expected to complete during the reporting period, their baselined and projected completion dates, and their current status. Note that changes to the control milestones shall be submitted as part of the monthly report for review and concurrence by the Project Office.

Status of Giver/Receiver items (e.g., item, giver or receiver, need date, forecast availability, etc.).

For Cost Plus CLINs, a summary explanation of key Earned Value Management (EVM) parameters performance and trends; summary of financial status and cost performance;

status of management reserve, liens, or other unfunded risk mitigations including estimated cost.

For Fixed Price CLINs, summary of Milestone Payments paid, unpaid/open and status, and a 12-month forecast of upcoming milestones.

For Cost Plus CLINs, headcount metrics with variance explanations reported at the Integrated Product Team (IPT) and Total Project levels that summarize Baseline, Forecast, and Actual headcounts where a “head” equals one equivalent work-month of effort.

Technical status, risks, and issues of the total contracted effort that includes significant/higher risk/near critical path subcontracts o Including a list of suppliers (e.g., significant suppliers/subs who provide higher risk items, items of significant value, or items near/on the critical path), description of product being supplied, and status

Technical Performance Metrics (TPM) (reference CDRL SE-2) that show the Current Best Estimated (CBE), margin/contingency (adjusted for maturity) to the specification indicating calculated, and/or measured values, their accuracy, and units with trends for each including software metrics (reference CDRL SW-1).

Integration and test (I&T) planning summary, test flow/schedules, reviews, procedure release status, readiness, significant completed\open work, risks, issues, concerns, significant lessons learned, and Verification and Validation status (e.g., burn down metrics) when available.

Backup Material:

Spare parts status Configuration Control Board (CCB) Status: List of upcoming, in process, and approved

Class I changes; list of approved Class II changes

NS1 SMBA CDRL NS1-SMBA-CDRL-0001, Revision C

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

Mission Assurance Program Status o Summary of Material Review Board (MRB) actions and status o Summary of Failure/Anomaly Review Board (FRB/ARB) actions and status o Summary of Failure investigations and corrective actions o Company/program quality metrics relevant to processing and program o Manufacturing quality statistics for higher risk/higher impact subcontractors:

First pass yields; Supplier defect rates, etc.

Prohibited Materials Compliance Status (as available) o SMBA Product Alert evaluation status o Production Readiness issues (as available)

Complete risk list from database with risk statements, LxC, and status (open/closed/accepted)

Project security status

NS1 SMBA CDRL NS1-SMBA-CDRL-0001, Revision C

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

DATA ITEM DESCRIPTION

PM-2 ENGINEERING PEER REVIEW (EPR) PLAN

3. Reference:

GPR 8700.6A, Engineering Peer Reviews

4. Use:

To communicate the EPR design review plan to the Government for early planning, discussion, and streamlined execution. It is also a means to convey which elements of the contracted effort are of higher criticality allowing early discussion and understanding. Lastly, it provides an early means to ensure the review approach will be focused on the engineering, streamlined, and not planned with inefficient overhead in chart development and unnecessary presentations.

5. Preparation Information:

The EPR Plan shall:

Identify major/critical subsystems to be reviewed. Critical subsystems are those components, subassemblies, subsystems, and software that are higher risk/complexity items, items of significant dollar/schedule value, or items near/on the critical path.

Critical suppliers are those suppliers delivering critical subsystems.

o Critical subsystems and suppliers identified in the EPR plan are referred to elsewhere in the SOW and CDRL where there is additional attention required for these items (ex. peer reviews, additional deliverables)

Identify the processes, plans, components, subassemblies, subsystems, software elements, etc., that will be peer reviewed.

Provide a schedule tied to major reviews/milestones for the planned EPRs.

Identify components and subsystems that will not be peer reviewed and state the rationale.

Describe the methodology used to determine the scope of the EPR process.

Describe the planned peer review process, including notional review personnel, any plans for internal independent reviewers, nominal agenda, and action item management.

NS1 SMBA CDRL NS1-SMBA-CDRL-0001, Revision C

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

DATA ITEM DESCRIPTION

1. CDRL No.: 2. Title:

PM-3 INTEGRATED PROGRAM MANAGEMENT

DATA AND ANALYSIS REPORT (IPMDAR)

Integrated Program Management Data Analysis Report (IPMDAR) Implementation & Tailoring Guide, 24 August 2021 (https://www.acq.osd.mil/asda/ae/ada/ipm/docs/IPMDAR%20Implementation%20and%20Tailor ing%20Guide_Stamped.pdf), Data Item Description for Integrated Program Management Data and Analysis Report (IPMDAR) DI-MGMT-81861C (this document is to be used as guidance in the preparation of the IPMDAR) ASSIST-QuickSearch Document Details (dla.mil) Contract Performance Dataset (CPD) validator tool EVM-CR Resources (osd.mil) Schedule Performance Dataset (SPD) validator tool EVM-CR Resources (osd.mil) CPD FFS 20200312 Contract Performance Dataset - FFS.pdf (osd.mil) SPD FFS 20200312 Schedule Performance Dataset - FFS.pdf (ssitools.com) SP-2010-403, NASA Schedule Management Handbook NASA IPMDAR Tailoring Supplement (NITS)

For Cost Plus CLINs, to provide information for: (1) integrating cost and schedule performance data with technical performance measures; (2) assessing the magnitude and impact of actual and potential problem areas causing significant cost and schedule variances; and (3) providing valid, timely project status information to higher management.

To ensure an integrated approach to project management, the data provided by this IPMDAR Data Requirements Document (DRD) shall be in consonance with the work breakdown structure (WBS), organizational breakdown structure (OBS), risk management processes, integrated master schedule (IMS), plans and reports (where required), probabilistic risk assessment processes and reports (where required), the cost analysis data requirement (CADRe) (when required), and the monthly/quarterly Contractor financial management reports (NASA 533M/Q).

The Contractor must be able to reconcile between the NASA 533M/Q and the IPMDAR. This reconciliation should be included within the required IPMDAR performance narrative report.

IPMDAR contains data for measuring Contractor cost and schedule performance at NASA. The primary purpose is to reflect current performance status and the forecast of future performance.

NS1 SMBA CDRL NS1-SMBA-CDRL-0001, Revision C

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

The IPMDAR consists of the following components:

Contract Performance Dataset (CPD) – Provides performance/execution data from Contractor existing management systems.

Schedule (comprised of both Microsoft Project or Native Schedule File and the Schedule Performance Dataset (SPD) – Provides data from the consolidated Contractor IMS. At a minimum, subcontractor effort must be incorporated into the IMS at an intermediate level with key milestones and be distinguishable from the Contractor’s and subcontractor’s efforts.

Performance Narrative Report (Comprised of both the Executive Summary and Detailed Analysis Report) – Provides narrative analysis of data provided in the CPD and the SPD.

The IPMDAR CPD and SPD files shall be validated prior to submittal.

The CPD and SPD formats will be JavaScript Object Notation (JSON) format as defined by the IPMDAR file format specifications (FFS) and the IMS in Microsoft Project file or native schedule format. The IMS data dictionary and performance narrative report will be in Microsoft Word/Excel or native format.

CPD, Schedule (Microsoft Project or Native Schedule File and SPD) and Performance Narrative Report (Executive Summary and Detailed Analysis) Instructions:

5.1 CPD Instructions: Contractor will meet the requirements set forth in NASA IPMDAR Tailoring Supplement (NITS)

The CPD shall be submitted in dollars and hours as part of the original JSON submission.

Contractors with IPMDAR flow-down shall submit dollars and hours as part of the original Prime submission and provide a separate JSON file with dollars or hours directly to the Government to protect data sensitivities related to rates.

Data Repository-Electronic Submission and File Formats: Data in accordance with the applicable approved CPD FFS and Data Exchange Instructions is to include all structures and units to at least the control account/work package level

Subcontractor Integration: Data for Subcontractors with an IPMDAR DRD flow-down requirement shall be integrated with the Prime’s IPMDAR CDRL delivery.

5.2 SPD: Contractor will meet the requirements set forth in NASA IPMDAR Tailoring Supplement (NITS).

The Contractor shall use Microsoft Project as their scheduling tool for integration with GSFC schedules.

Contractors with IPMDAR flow-down may submit dollars and hours as part of the original Prime submission and provide a separate JSON file with both dollars and hours directly to the Government to protect data sensitivities related to rates.

NS1 SMBA CDRL NS1-SMBA-CDRL-0001, Revision C

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

IMS Data Dictionary for Microsoft Project or Native IMS Schedule File: The first monthly analysis narrative submission for the Schedule shall include the ‘Schedule Assumptions’ and ‘Data Dictionary.’ Any change, post-first submission, to the ‘Schedule Assumptions’ or ‘Data Dictionary’ requires re-submittal of the information with the affected IPMDAR deliverable.

Schedule Risk Assessment (SRA) – Reporting Frequency: An SRA can be performed, at the request of the Government, particularly when the schedule is a significant issue for the Government due to operational requirements, funding limitations, or when scheduling is considered a major risk element to the acquisition effort.

The IMS shall contain the contract milestones, accomplishments, criteria, discrete tasks/activities, work packages and planning packages, as applicable, from contract start to contract completion. The IMS is an integrated, logically driven, network-based schedule that is vertically and horizontally traceable. The IMS has traceability to, the project EVM WBS, project OBS, Contractor control accounts (CA), and Contractor work packages, if applicable to provide transparency for execution. The WBS and other SPD fields in the IMS are consistent with the CPD. The IMS contains all calendars that define working and non-working time periods or other information that may impact the schedule. Each event (e.g., milestone, activity, summary, etc.) identified in the IMS has a unique identifier that is consistent period to period.

All CCB authorized and funded risk burn-down (mitigation) activities shall be integrated into the

IMS.

The Schedule consists of horizontally and vertically integrated discrete tasks/activities, consistent with all authorized work, and relationships necessary for successful contract completion. The Schedule is a single integrated network that also contains significant external interfaces, subcontractor discrete work, Government furnished equipment/information/property, and relationship dependencies for the entire contractual effort.

The Schedule shall contain all calendars that define working and nonworking time periods.

The Schedule shall reflect accurate remaining durations, start dates, and finish dates for all tasks/activities and milestones in respect to the status date.

5.2.1 If a SOW or Integrated Master Plan are used for vertical schedule integration, those references shall be provided in both the SPD and native schedule.

5.2.2 Milestones – Provide zero duration schedule events marking the due date for accomplishment of a specified work scope or objective. Milestone may mark the start, an interim step, or the end of one or more activities.

5.2.3 Tasks/Activities – Provide elements of work with duration and logical relationships/dependencies. Task/activity names shall be concise and unique in respect to other names within the Schedule. The name of each task/activity shall clearly reflect the scope, output

NS1 SMBA CDRL NS1-SMBA-CDRL-0001, Revision C

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

(e.g., deliverable), and place within the Schedule architecture so that the content can be understood without the subproject task structure, if applicable.

5.2.4 Duration – Provide the length of time estimated, realized, and/or remaining to accomplish a task/activity. Discrete tasks are preferred to be 42 workdays or less.

5.2.5 Baseline Dates and Information – For all tasks within the performance measurement baseline (PMB), baseline dates in the SPD and Native Schedule files shall be consistent with the start and finish of the cost baseline in the CPD at the control account (or work package) level.

The baseline is typically set equal to the current schedule early dates at the time of the baseline establishment when change control is initiated.

5.2.6 Control Account/Work Package Identification – Tasks in the schedule must be tagged with a control account and work package as appropriate. This is accomplished by using the corresponding ControlAccountID and WorkPackageID fields in the Task table of the SPD. The SPD must be consistent with the CA and WP definitions within the CPD. As a minimum, the ControlAccountID values must be consistent with the ID tags as defined in the ControlAccount table and the Task table of the SPD must be consistent with the work package definitions.

5.2.7 Level of Effort (LOE) – LOE activities may be included or excluded in the network, as appropriate. This determination should be made based on standard procedures. LOE activities shall not impact discrete work or the calculation of the critical and driving paths and never drive paths. When LOE activities are included within the IMS, they are clearly identified as such and defined in the Data Dictionary.

5.2.8 Schedule Percent Complete – The calculated schedule percent complete is a time-based status calculated by the schedule tool without regard to task/activity scope accomplishment. This is not used to status budgeted cost of work performed (BCWP) (i.e., depicts the “time” percent complete based on the forecast completion date, not earned value percent complete based on work accomplished). Earned Value percent complete, when used, will be in the physical percent complete field.

5.1.2.9 Earned Value Technique – The Earned Value Technique (EVT) used for planning and statusing the Earned Value Tool can, as needed, be identified with the SPD. The EVT for each task is identified within the SPD and if LOE tasks are included withing the schedule then they must be identified using the appropriate EVT tag.

5.2.10 Total Float/Slack – Provide the amount of time a task/activity or milestone forecast finish date can slip before delaying contract completion or constraint date.

5.2.11 Free Float/Free Slack – Provide the amount of time a task/activity or milestone can slip before it delays any of its successor tasks/activities or milestones.

5.2.12 Driving Path – The driving path is the longest continuous sequence chain of incomplete discrete tasks/activities/milestones and, if present, parallel chains in the schedule network that

NS1 SMBA CDRL NS1-SMBA-CDRL-0001, Revision C

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

drive the forecast dates of the agreed to discrete task/activity or milestone. A driving path may or may not be on the IMS critical path.

5.2.13 Critical Path – A sequence of discrete work packages and planning packages (or lower level tasks/activities) in the IMS that has the longest total duration with the least amount of total float/slack through an end point.

5.2.14 Subcontractor Tasks – Identify the tasks that are unique to the scope of a major subcontractor, if any. The subcontractor discrete work will be incorporated as tasks within the Contractor IMS at a level necessary for a realistic critical path.

5.2.15 Risk Mitigation Tasks – Both the Native Schedule and the SPD delivery shall identify items that came from the Risk/Opportunity Management System and include authorized risk mitigation activities, as applicable.

5.2.16 Schedule Visibility Tasks (SVT) – SVTs are tasks/activities or milestones in the IMS that increase management visibility and functionality of the schedule for non-PMB related items.

SVTs shall not be used to represent any scope within the PMB. Resources cannot be assigned to SVTs, nor shall they be used to assess earned value performance.

5.2.17 Lead/Lag – Provide the durations of leads or lags between predecessor and successor tasks. Justification for each lead/lag shall be included in both the Native Schedule and the SPD.

5.2.18 Constraints – Identify the constraints applied to tasks. Justification for each constraint shall be included in the Native Schedule and SPD submissions.

5.2.19 Schedule Margin – A management method for accommodating schedule contingencies. It is a designated risk mitigation placeholder within the schedule and does not have assigned resources.

5.2.20 Data Dictionary for Native Schedule File – Provide a list of all Contractor defined fields, definitions, and code structures used within the Native Schedule File. The Data Dictionary shall be delivered with the initial submission of the Native Schedule File, and resubmitted with subsequent submissions if changes occur to the Data Dictionary, or upon request.

5.2.21 SRA – The intent of the SRA is to evaluate whether or not the baseline is executable based on the identifiable risks. An SRA is the process which uses statistical techniques to identify technical, programmatic, and schedule risks in a program and quantifies the impact of those risks on the program’s schedule.

5.2.22 Custom/User-Defined Fields – Custom/user-defined fields may be required for specific information not otherwise included in the Schedule and included in the data dictionary.

5.2.22.1 Givers/Receivers – Deliverable and receivable products from one organizational element to another organization element must be identified with zero duration milestone tasks in the IMS and finish-to-start dependencies (for example, the deliverable of a subsystem, the

NS1 SMBA CDRL NS1-SMBA-CDRL-0001, Revision C

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

“giver,” to system I&T, the “receiver,” must each be a milestone task with zero-day duration linked with a finish-to-start dependency from the giver milestone to the receiver milestone).

Giver and receiver milestones must be flagged or coded in the IMS.

5.2.22.2 Government Furnished Item Need Dates – Need dates for Government furnished equipment, material, property, information, facilities, or data must be identified in the IMS with milestone tasks and predecessor and successor logic.

5.2.23 Status Date – Schedule status date must reconcile with the financial and EVM calendar period end dates.

5.3 Performance Narrative Report – Detailed Analysis – Variance Analysis:

Variance Analysis Selection: Variance analysis shall be presented using dollars as the basis.

General: If there are no changes to the reportable element problem analysis, expected impacts, or corrective action status, the Contractor may specify “no changes since the last reported analysis” and reference the IPMDAR date when the narrative was reported.

Government Specified Variance Analysis Thresholds. Control account variances that exceed the category thresholds identified below are selected and reported:

Pool of Reportable Variances are determined by the following thresholds:

Current cost variances exceeding +/- $100K or +/- 10% Current schedule variances exceeding +/- $100K or +/- 10% Cumulative cost variances exceeding +/- $250K and +/- 10% Cumulative schedule variances exceeding +/- $250K and +/- 10% Variances at completion exceeding +/- $500K and +/- 10% Percentages determined using reporting level budgeted cost of work scheduled and

BCWP as the base (denominator)

Variance thresholds shall be reviewed periodically to ensure the threshold levels are commensurate with the changing program risks and may be adjusted by contract modification with no change in contract price.

Performance Narrative Report – Detailed Analysis

Detailed Analysis Required Elements: Provide explanations in the Performance Narrative Report Detailed Analysis in accordance with NASA IPMDAR Guide with the additional following definitions:

Contract summary Baseline Changes: Ensure that the following are covered in the Performance Narrative

Report Detailed Analysis for baseline changes:

o Significant PMB differences (absolute values exceeding +/- 1% ) as compared to the previous IPMDAR reported PMB shall be explained in the Performance Narrative Report Detailed Analysis.

NS1 SMBA CDRL NS1-SMBA-CDRL-0001, Revision C

Check the NS1 TDMS Server at https://ipdtdms.gsfc.nasa.gov/frontmenu_dsp.cfm to verify that this is the correct version prior to use.

o Significant Authorized Baseline Changes shall be explained in the Performance Narrative Report Detailed Analysis. “Significant Authorized Baseline Changes” are defined as the largest baseline changes occurring during the reporting period that in total represent at least 5% (dollar value) of the reporting month’s approved change requests to the PMB.

Estimate at completion analysis Undistributed budget analysis Management reserve analysis Cost and schedule variance analysis Supplemental discussions Reconciliation with 533 data Staffing Changes: ‘Major changes’ to staffing are defined as a change of +/- 5% or greater in the reported organizational level staffing as compared to the previous IPMDAR submittal

The contract IMS shall be reported through delivery of the following information included in the performance narrative report but may be combined at the Contractor’s discretion with the approval of NASA’s project scheduling office. All schedule reporting shall be derived from, and traceable to, the Contractor’s IMS based on the Contractor’s accounting month to include the following:

Summary Master Schedule: A one page, top level, Gantt-type schedule chart in Contractor format that summarizes the contract effort including period of performance and major milestones, critical path, schedule margin, schedule baseline, and current forecast-to-complete.

IMS File/Database: An automated logic network file/database consisting of schedule data for all Contract Work Breakdown Structure (CWBS) elements including subcontractor effort. The entire scope of work must be decomposed into schedule tasks and milestones at a level of detail that supports discrete progress measurement and visibility into the overall design, development, fabrication, integration, assembly, test, and delivery phase of deliverables including flight hardware and software, engineering test and development units, support equipment, etc. Additionally, all schedule tasks must be integrated with dependencies that provide a total end-to-end logic network that includes a system I&T sequence at a level of detail sufficient to identify deliverable need dates. This database must contain dates for all contractual deliverables including end item delivery dates such as flight and ground system hardware and software.

Government furnished equipment, material, property, information, facilities, or data need dates must be identified in the IMS.