Amendment 0002 - Attachment J.3 Contract Data Requirements List (CDRL).pdf

Effective Date: May 30, 2025TBD

Expiration Date: May 30, 2030TBD

Check https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

SWGS-MOS-CDRL-0001, Revision AB Draft

Space Weather Ground Services, Code 492.0

Space Weather Observations

Mission Operations Services

(SWO-MOS)

Contract Data Requirements List (CDRL)

U.S. Department of Commerce (DOC)

National Oceanic and Atmospheric Administration (NOAA)

National Environmental Satellite, Data, and Information Service (NESDIS)

National Aeronautics and Space Administration (NASA)

SWO Reviewed – Not Subject to Export Control

GSFC SWGS CMO

06/02/2025TBD

ReleasedDraft https://ipdtdms.gsfc.nasa.gov/

SWO-MOS CDRL SWGS-MOS-CDRL-0001, Revision AB Draft i

Preface

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

Any questions should be addressed to:

SWGS Configuration Management Office

NASA/GSFC

Code 492.0

Greenbelt, MD 20771 ii

Change History Log

Revision Effective

Date

Description of Changes

(Reference the CCR & CCB/ERB Approval Date)

Revision - 02/26/2025 Baseline Release following the approval of SWGS-CCR-0006

Revision A 05/30/2025 Updated following the approval of SWGS-CCR-0025

Updated MA-## deliverables and associated DIDs

Updated CDRL Summary table and adjusted the CDRL submission timelines

Updated CDRL table and applicability table for inclusion of additional CDRLs required for TO-03

Revision B Draft Update CDRL Summary List to better differentiate between

TO-01 and TO-03 reviews iii

Table of TBDs/TBRs/TBSs

Action Item

No.

Location Summary Individual/

Organization

Actionee iv

Table of Contents

1 INTRODUCTION

1.1 Scope

1.2 Purpose

2 RELATED DOCUMENTATION

3 IDENTIFICATION, REFERENCE, DELIVERY, AND ACCEPTANCE

3.1 Identification

3.2 Title

3.3 Contract Submission

3.4 Electronic Submission

3.5 Transmittal Notification

3.6 Hardcopy Deliverables

3.7 Alternative Delivery Methods

3.8 Delivery Formats

3.9 Contract Acceptance Code

3.10 Documentation Change Procedures

3.11 Document Markings

4 CONTRACT DATA REQUIREMENTS LIST

4.1 SWO-MOS CDRL Summary List

5 DATA ITEM DESCRIPTIONS

5.1 SWO-MOS Project Management Plan [PM-01]

5.2 SWO-MOS Integrated Master Schedule [PM-03]

5.3 Project Management Status Review Data Package [PM-04]

5.4 Meeting Minutes [PM-07]

5.5 SWO-MOS Property Management Plan [PM-09]

5.6 Contract Performance Report (CPR) [PM-10]

5.7 SWO-MOS Earned Value Management System (EVMS) Plan [PM-11]

5.8 Integrated Baseline Review (IBR) Data Package [PM-12]

5.9 SWO-MOS Contract Work Breakdown Structure [PM-13]

5.10 Financial Reports [FM-01]

5.11 SWO-MOS Configuration Management Plan [CM-01]

5.12 SWO-MOS Document Tree [CM-02]

5.13 SWO-MOS Drawing Tree [CM-03]

5.14 SWO-MOS Configuration Item Identification List [CM-05]

5.15 SWO-MOS Configuration Control Board (CCB) Documentation [CM-06]

5.16 SWO-MOS Configuration Change Requests (CCRs) [CM-07]

5.17 SWO-MOS Risk Management Plan (RMP) [RM-01]

5.18 Risk List [RM-02]

5.19 IT System Security and Contingency Document [IS-01]

5.20 SWO-MOS Systems Engineering Management Plan (SEMP) [SE-01]

5.21 SWO-MOS Operations Concept [SE-02]

5.22 SWO-MOS Requirements Document [SE-03]

v

5.23 SWO-MOS External Interface Requirements Specification [SE-04]

5.24 SWO-MOS Element and Infrastructure Requirements Specifications [SE-05]

5.25 SWO-MOS Internal Interface Requirements Specification [SE-06]

5.26 SWO-MOS Design Descriptions [SE-07]

5.27 SWO-MOS External Interface Control Documents [SE-08]

5.28 SWO-MOS Internal Interface Control Documents [SE-10]

5.29 SWO-MOS Software Requirements Specifications [SE-11]

5.30 SWO-MOS Software Design Descriptions [SE-12]

5.31 SWO-MOS Database Design Descriptions [SE-13]

5.32 Mission Unique Change Review (MUCR) Packages [RE-01]

5.33 System Requirements Review/System Definition Review (SRR/SDR) Package [RE-02]

5.34 Design Modification Review (DMR) Package [RE-03]

5.35 Critical Design Review (CDR) [RE-04]

5.36 Preliminary Design Review (PDR) Package [RE-05]

5.37 Test Readiness Review Packages [RE-13]

5.38 Segment Integration Review (SIR) Package [RE-14]

5.39 Release Pre-Ship Review (PSR) Packages [RE-15]

5.40 Release Readiness Review (RRR) Packages [RE-17]

5.41 Operations Test Readiness Review (OTRR) Packages [RE-18]

5.42 Acceptance Data Package [RE-21]

5.43 General Review Packages [RE-24]

5.44 SWO-MOS Software Management and Development Plan (SMDP) [SW-01]

5.45 SWO-MOS Software Verification and Validation Plans [SW-02]

5.46 Software Test Plans and Procedures [SW-03]

5.47 Software Test Reports [SW-04]

5.48 Software Delivery Packages [SW-06]

5.49 SWO-MOS Integration, Test and Verification Plan [IT-01]

5.50 Detailed Test Plan(s) and Procedures [IT-02]

5.51 Post-Test Data Package [IT-03]

5.52 SWO-MOS Transition and Operations Support Plan [TO-01]

5.53 Mission Operations Plan [TO-02]

5.54 SWO-MOS Operations and Maintenance Manuals [TO-03]

5.55 SWO-MOS Ground Operations Procedures [TO-07]

5.56 SWO-MOS Maintenance, Logistics, and Sparing Plan [TO-08]

5.57 SWO-MOS Maintenance Records [TO-09]

5.58 SWO-MOS Training Plans [TO-10]

5.59 SWO-MOS Training Materials [TO-11]

5.60 SWO-MOS Facility Requirements Implementation Plans [TO-15]

5.61 SWO-MOS Mission Assurance Implementation Plan (MAIP) [MA-01]

5.62 SWO-MOS System Safety Program Plan [MA-03]

5.63 SWO-MOS Preliminary Hazard Analysis Report [MA-05]

5.64 SWO-MOS Electrostatic Discharge (ESD) Control Plan [MA-07]

5.65 SWO-MOS Failure Mode, Effects, & Criticality Analysis (FMECA) [MA-08]

5.66 SWO-MOS Reliability, Maintainability, and Availability (RMA) Program Plan [MA-09] vi

5.67 SWO-MOS Reliability, Maintainability, & Availability (RMA) Predictions Report [MA-

10]

5.68 SWO-MOS Software Assurance Plan [MA-17]

5.69 SWO-MOS Trend Analysis Report [MA-18]

5.70 Special Study Reports [SS-01]

APPENDIX A. CDRL APPLICABILITY MATRIX

1 INTRODUCTION

1.1 Scope

This CDRL document includes data item descriptions (DIDs) for the data deliverables under

SWO-MOS Base IDIQ contract. The applicability of individual CDRL DIDs to individual task orders is defined in Appendix A, Table 2.

1.2 Purpose

The purpose of this document is to provide a comprehensive list and descriptions of the data items the Contractor shall deliver under this contract. The Government may provide model artifacts for many of these data items as Government-furnished property (GFP) or Government-furnished information (GFI). The Contractor may use provided GFP/GFI to inform their own development of CDRLs. Additionally, the Contractor may request Government approval to use existing Contractor practice for format, processes, or tools to meet the CDRL delivery requirements. Government approval for changes may only be granted by the CO.

2 RELATED DOCUMENTATION

Space Weather Observations Mission Operations Services (SWO-MOS) Applicable and

Reference (A&R) Documents List, SWGS-MOS-LIST-0003, provides the list of applicable and reference documents for the CDRLs with their sources. In the event of any unresolved conflict, the Contractor must request conflict resolution by the Contracting Officer in advance of work performed.

The SWO Program Acronym and Glossary List, SWO-MGMT-LIST-0001, defines terminology as used in this document and throughout the SWOPD. In the event of conflict between terminology in this document and the SWO Acronym and Glossary, the SWO terminology will take precedence. In the event of any unresolved conflict, the Contractor must request conflict resolution by the Contracting Officer.

3 IDENTIFICATION, REFERENCE, DELIVERY, AND ACCEPTANCE

3.1 Identification

The ID column identifies the Data Item by functional category and a sequential number within that category. The data item prefixes, and the associated functional categories, are listed below.

Table 1 Data Item Prefixes and Associated Functional Categories

Data Item Prefix Functional Category

PM Program Management

FM Financial Management

CM Configuration Management

RM Risk Management

IS Information Security

SE Systems Engineering

RE Review Packages

SW Software

IT Integration and Test

TO Transition to Operations

MA Safety and Mission Assurance

SS Special Studies

3.2 Title

The CDRL Title describes the required data, or document that is traceable to specific elements of the functional category breakdown structure.

3.3 Contract Submission

Initial: The initial submission of an item for approval, review, or information. To be completed with available information as of the time of preparation for the due date.

Update: The best up-to-date information available at the time. Data item updates will require the same "approval/review" process as was required for the previous submissions.

Final: The complete thorough submission that meets all CDRL requirements, as written or negotiated, of an item for approval, review, or information.

Other Definitions

Term Definition

Shall Indicates a mandatory requirement.

Will Denotes an expected outcome or statement of fact, not a requirement

Are/Is Used for descriptive material, not requirements.

TBS

“to be supplied”, identifies missing or incomplete information, values, or data needed to fulfill a requirement.

TBD

“to be determined”, indicated requirement has not been decided or is not yet known.

TBR

“to be refined/reviewed”, indicates a requirement is subject to review for appropriateness and subject to revision.

SW Next

The total scope of the SW Next architecture and functionality identified in the Space Weather Next requirements document and interface requirements documents.

Software Refers to both software and firmware.

Task Order The number or frequency of these events or deliveries will be specified in the individual Task Order Statements of Work (SOWs)

Iteration A new version of a piece of computer software.

Monthly Submissions due by the 15th of each month, or as modified by the CO.

Bi-weekly Submissions due by close of business every other Tuesday, or as modified by the CO.

Weekly Submissions due by close of business every Friday, or as modified by the CO.

Days Business days, unless otherwise indicated.

POP Period of Performance, referring to contract POP

As Generated Items after each initial edition, revision, and addition that are critical to schedule, performance, or interface shall be transmitted to the

Government within 48 hours of generation.

As Required Items updated and delivered at the direction of the CO or as specified in the data item requirements.

Build Version at the factory or otherwise not delivered for use.

Release Version delivered to site or to operations environment for use.

3.4 Electronic Submission

The primary method of submission for all deliverables is through the Government-specified web portal. This includes all data items, reports, and other documentation required by the contract.

3.5 Transmittal Notification

Upon submission of any deliverable, the Contractor shall send a transmittal notification via email to the Contracting Officer (CO) and Contracting Officer’s Representative (COR). The email should include the following:

• Title/identification of the submitted deliverable.

• The date of submission.

• Context for the submission.

CO: Maryann Orellana (maryann.orellana@noaa.gov)

COR: Gustave Comeyne (Gustave.Comeyne@noaa.gov)

3.6 Hardcopy Deliverables

In rare instances, the Government may request hardcopy versions of specific deliverables. A hardcopy includes data that is typed, drawn, or printed on paper by common conventional practices. Hardcopy deliverables shall be delivered according to Contract requirements.

3.7 Alternative Delivery Methods

Any deviations from the standard electronic submission process must be approved, in writing, by the CO or COR.

3.8 Delivery Formats

Unless otherwise specified in the data item description or approved by the CO, electronic deliverables shall be provided in the following formats:

Deliverables Accepted Formats

Text Documents Microsoft Word (.docx), Adobe PDF (.pdf)

Presentations Microsoft PowerPoint (.pptx), Adobe PDF (.pdf)

Spreadsheets Microsoft Excel (.xlsx)

Databases ASCII (.txt), XML with schema documentation

Schedules Microsoft Project (.mpp), Adobe PDF (.pdf)

Schematics / Drawings Microsoft Visio (.vsdx), Adobe PDF (.pdf)

Photographs JPEG (.jpg), PNG (.png)

Video MP4 (.mp4), AVI (.avi)

Note: The Contractor may propose alternative formats for any deliverable type, subject to CO approval. The Government reserves the right to request specific formats as needed.

3.9 Contract Acceptance Code

For all CDRLs, the Contractor shall respond to Government feedback within 30 days of receipt.

Code Description

(A) Approval

Documents require submission to the Government within the time specified. Approval documents shall not be implemented until

Government approval. The Government will act on items requiring approval within 30 days of receipt.

(R) Review

Documents shall be submitted to the Government within the time specified and will be subject to evaluation. Review documents shall be implemented upon issuance unless otherwise noted. When evaluation reveals inadequacies, the Contractor shall correct and resubmit the document as specified.

(I) Information

Documents will be used by the Government to determine current project status, progress, and for future planning requirements. These are accepted as long as the content is complete per the CDRL requirements.

3.10 Documentation Change Procedures

The Contractor shall issue Document Change Notices (DCNs) whenever minor changes or updates occur in data items that have been delivered to the Government. DCN reports shall be delivered on a periodic basis (such as monthly or with each increment) as defined in the

Integrated Master Schedule (IMS).

Revisions shall be designated as the latest version letter with a point number designator. For example, Revision A.1, A.2, A.3, etc. After nine revisions, an update shall be required. For minor changes or updates (documents that change by less than 30%), change bars are to be provided only with each CDRL delivery to the Government.

For Updates (major changes (documents that change by more than 30% based on page count)) of documents, formal CDRL deliveries shall be provided as a complete document without redlines or change bars, along with a “difference” version showing changes from the prior formal delivery.

3.11 Document Markings

Documents containing materials or information covered and controlled by International

Trafficking in Arms Regulations (ITAR) or Export Administration Regulation (EAR) regulations, as determined by the Contractor, shall be so marked on the cover and on pages containing such materials.

Documents containing Contractor proprietary materials or information, as determined by the

Contractor, shall be so marked on the cover and on pages containing such materials.

Documents shall not be unnecessarily or unjustifiably marked with restrictive or limiting labels, nor shall such labeling be applied frivolously or indiscriminately.

4 CONTRACT DATA REQUIREMENTS LIST

The table below is the Contract Data Requirements List. See Section 05 for explanation of terms. See Appendix A for applicability matrix by Task Order.

4.1 SWO-MOS CDRL Summary List

ID Title Contract Submission Final

Acceptance

P R O J E C T M A N A G E M E N T

PM-01 SWO-MOS Project Management Plan Final: Post-Award Conference

Updates: as directed A

PM-02 Reserved

PM-03

SWO-MOS Integrated Master

Schedule (IMS)

Final: Contract Award + 60 days

Updates: Monthly 13 business days after close of contractor fiscal period through POP

I

PM-04

Project Management Status Review

(PMSR) Data Package

Initial: Post-Award Conference

Updates: Provide a draft one business day prior to each PMSR meeting, with a formal update no later than one week following the meeting

I

PM-05 Reserved

PM-06 Reserved

PM-07 Meeting Minutes Final: Meeting + 1 week

Updates: as required R

PM-08 Reserved

PM-09

SWO-MOS Property Management

Plan

Final: Contract Award + 120 Days

Updates: Annually or as directed R

PM-10 Contract Performance Report (CPR) Initial: Contract Award + 60 days

Monthly thereafter, or as otherwise directed I

PM-11

SWO-MOS Earned Value

Management System (EVMS) Plan

Initial: Contract Award + 60 days

Update: as required I

Acceptance

PM-12

Integrated Baseline Review (IBR)

Data Package

Initial: per Task Order Award + 60 days

Update: as required I

PM-13

SWO-MOS Contract Work

Breakdown Structure (CWBS)

Final: Contract Award + 60 days

Updates: as directed A

F I N A N C I A L M A N A G E M E N T

FM-01 Financial Reports

Initial: Contract Award + 60 days

Updates: Monthly as described in the DID for this

CDRL

I

FM-02 Reserved

C O N F I G U R A T I O N M A N A G E M E N T

CM-01

SWO-MOS Configuration

Management Plan

Initial: Contract Award + 60 days

Final: Contract Award + 120 days

Updates: as directed

A

CM-02 SWO-MOS Document Tree Initial: per Task Order PDR/DMR – 1 day

Updates: as directed I

CM-03 SWO-MOS Drawing Tree Initial: per Task Order PDR/DMR - 1 day

Updates: as directed I

CM-04 Reserved

CM-05

SWO-MOS Configuration Item

Identification List

Initial: PDR/MUCR

Updates: as directed R

CM-06

SWO-MOS Configuration Control

Board (CCB) Documentation Final: as Generated I

CM-07

SWO-MOS Configuration Change

Requests (CCRs)

Final: as Generated

A, I

R I S K M A N A G E M E N T

RM-01 Risk Management Plan

Initial: Contract Award + 60 days

Final: Contract Award + 120 days

Updates As directed

A

Acceptance

RM-02 Risk List Initial: Contract Award + 120 days

Updates: monthly R

I N F O R M A T I O N S E C U R I T Y

IS-01

IT System Security and Contingency

Document

Initial: per Task Order PDR/DMR - 2 weeks

Final: Annual Reauthorization

Updates: as required by the DID or per Task Order

R

S Y S T E M S E N G I N E E R I N G

SE-01

SWO-MOS Systems Engineering

Management Plan

Initial: Contract Award + 30 days

Final: Contract Award + 60 days

Updates: as directed

R

SE-02 SWO-MOS Operations Concept

Initial: per Task Order SRR/MUCR - 1 week

Update: per Task Order PDRDMR - 1 week

Final: per Task Order CDR/DMR + 30 60 days

Updates: as directed

A

SE-03 SWO-MOS Requirements Document

Initial: per Task Order SRR/MUCR - 1 week

Update: per Task Order PDR - 1 week

Final: per Task Order CDR/DMR - 3 weeks

Updates: as directed

A

SE-04

SWO-MOS External Interface

Requirements Specifications

Initial: per Task Order SRR/MUCR - 1 week

Update: per Task Order PDR - 1 week

Final: per Task Order CDR/DMR - 3 weeks

Updates: as directed

A

SE-05

SWO-MOS Element and Infrastructure

Requirements Specification

Initial: per Task Order SRR/MUCR – 1 week

Update: per Task Order PDR - 1 week

Final: per Task Order CDR/DMR – 2 weeks

Updates: as directed

R

SE-06

SWO-MOS Internal Interface

Requirements Specification

Initial: per Task Order SRR/MUCR - 1 week

Update: per Task Order PDR - 1 week

Final: per Task Order CDR/DMR - 2 weeks

R

Acceptance

Updates: as directed

SE-07 SWO-MOS Design Descriptions

Initial: per Task Order PDR/DMR - 1 week

Final: per Task Order CDR/DMR + 30 60 days

Updates: as directed

I

SE-08

SWO-MOS External Interface Control

Documents

Initial: per Task Order DMRPDR/DMR - 3 weeks

Final: per Task Order CDR/DMR +30 60 days

Updates: as directed

A

SE-09 Reserved

SE-10

SWO-MOS Internal Interface Control

Documents

Initial: per Task Order PDR/DMR - 2 weeks

Final: per Task Order CDR/DMR + 30 days

Updates: as directed

R

SE-11

SWO-MOS Software Requirements

Specifications

Initial: per Task Order SRR/MUCR - 1 week

Final: per Task Order CDR/DMR - 2 weeks

Updates: per Software release/deployment

R

SE-12

SWO-MOS Software Design

Descriptions

Initial: per Task Order PDR/DMR - 2 weeks

Final: per Task Order CDR/DMR + 60 days

Updates: per Software release/deployment

I

SE-13

SWO-MOS Database Design

Descriptions

Initial: per Task Order PDR/DMR - 2 weeks

Final: per Task Order CDR/DMR + 60 days

Updates: per Software release/deployment

R

R E V I E W P A C K A G E S

RE-01

Mission Unique Change Review

(MUCR) Packages

Initial: per Task Order MUCR - 2 weeks

Final: per Task Order MUCR + 30 days

Initial: R

Final: I

RE-02

System Requirements Review/System

Definition Review (SRR/SDR)

Package

Initial: per Task Order SRR/SDR - 2 weeks

Final: per Task Order SRR/SDR + 30 days

Initial: R

Final: I

RE-03

Design Modification Review (DMR)

Packages

Initial: per Task Order DMR - 2 weeks

Final: per Task Order DMR + 30 days

Initial: R

Final: I

RE-04

Critical Design Review (CDR)

Package

Initial: per Task Order CDR - 2 weeks

Final: per Task Order CDR + 30 days

Initial: R

Final: I

Acceptance

RE-05

Preliminary Design Review (PDR)

Package

Initial: per Task Order PDR - 2 weeks

Final: per Task Order PDR + 30 days

Initial: R

Final: I

RE-06 Reserved

RE-07 Reserved

RE-08 Reserved

RE-09 Reserved

RE-10 Reserved

RE-11 Reserved

RE-12 Reserved

RE-13

Test Readiness Review (TRR)

Packages Final: Test start - 1 week R

RE-14 Segment Integration Review (SIR) Final: SIR – 1 week R

RE-15 Release Pre-ship Reviews (PSR) Final: per Task Order PSR - 1 week I

RE-16 Reserved

RE-17

Release Readiness Review (RRR)

Packages

Initial: per Task Order RRR - 1 week

Final: per Task Order RRR + 30 days

Initial: R

Final: I

RE-18

Operations Test Readiness Review

Packages (OTRR) Final: per Operations TRR - 1 week R

RE-19 Reserved

RE-20 Reserved

RE-21 Acceptance Data Package Final: per Task Order ORR-2 weeks A

RE-22 Reserved

RE-23 Reserved

RE-24 General Review Packages Initial: per Task Order Review - 2 weeks

Final: per Task Order Review + 30 days

Initial: R

Final: I

S O F T W A R E

SW-01

SWO-MOS Software Management and Development Plan

Initial: Contract Award + 60 days

Final: Contract Award + 120 days

Initial: I

Final: R

Acceptance

Updates: as directed.

SW-02

SWO-MOS Software Verification and

Validation Plan

Initial: per Task Order SRR/MUCR – 2 weeks

Final: per Task Order SRR/MUCR + 30 60 days R

SW-03 Software Test Plans and Procedures

Initial: 15 days prior to per Task Order test

Final: per Task Order at PSR

Updates: For each release.

I

SW-04 Software Test Reports Final: per Test Completion + 4 weeks I

SW-05 Reserved

SW-06 Software Delivery Package Final: per Test Completion + 4 weeks R

I N T E G R A T I O N A N D T E S T

IT-01

SWO-MOS Integration, Test, and

Verification Plan

Initial: per Task Order CDR/DMR - 2 weeks

Final: per Task Order CDR/DMR + 45 days

Updates: as directed

Initial: A

Final: A

Update: A

IT-02 Detailed Test Plan(s) and Procedures Final: 15 days prior to test

Updates: For each release.

R

IT-03 Post-Test Data Package Final: per Test Completion + 4 weeks R

T R A N S I T I O N T O O P E R A T I O N S

TO-01

SWO-MOS Transition and Operations

Support Plan

Initial: per Task Order CDR/DMR - 2 weeks

Final: per Task Order CDR/DMR + 60 days

Updates: as directed

Initial: I

Final: A

TO-02 Mission Operations Plan

Initial: CDR/DMR – 30 days

Final: MOR – 30 days

Updates: as directed

Initial: R

Final: A

TO-03

SWO-MOS Operations and

Maintenance Manuals

Initial: first Release Readiness Review – 30 days

Final: last Release Readiness Review + 90 days

Updates: as directed

R

TO-04 Reserved

TO-05 Reserved

Acceptance

TO-06 Reserved

TO-07

SWO-MOS Ground Operations

Procedures

Initial: per Task Order Initial first Release Readiness

Review - 30 days

Final: Operational Last Release Readiness Review –

30 days

Updates: PLAR - 2 weeks and as required

R

TO-08

SWO-MOS Maintenance, Logistics, and Sparing Plan

Initial: per Task Order CDR/DMR - 2 weeks

Final: per Task Order CDR/DMR + 60 days

Updates: With each release, and every six months thereafter.

R

TO-09 SWO-MOS Maintenance Records

Initial: One month after start of I&T

Updates: Release 2 – 30 days

Final: Release 3

R

TO-10 SWO-MOS Training Plan Initial: per Task Order CDR/DMR - 2 weeks

Final: per Task Order CDR/DMR + 60 days

Updates: as directed

A

TO-11 SWO-MOS Training Materials Per Task Order Release Readiness Review - 1 week

Updates: as directed R

TO-12 Reserved

TO-13 Reserved

TO-14 Reserved

TO-15

SWO-MOS Facility Requirements

Implementation Plans

Initial: per Task Order CDR/DMR - 2 weeks

Final: per Task Order CDR/DMR + 60 days

Updates: as directed

A

S A F E T Y M I S S I O N A S S U R A N C E

MA-01

SWO-MOS Mission Assurance

Implementation Plan

Initial: per Task Order SRR/MUCR - 2 weeks

Final: per Task Order CDR/DMR – 30 days

Update as required

A

Acceptance

MA-03

SWO-MOS System Safety Program

Plan

Initial: per Task Order SRR/MUCR - 2 weeks

Final: per Task Order CDR/DMR - 30 days

Review/update annually

A

MA-05

SWO-MOS Preliminary Hazard

Analysis Report

Initial: per Task Order PDR/DMR - 2 weeks

Final: per Task Order CDR/DMR + 30 days A

MA-07

SWO MOS Electrostatic Discharge

Control (ESD) Plan

Initial: per Task Order PDR/DMR - 2 weeks

Final: per Task Order CDR/DMR + 30 days

Update as required

R

MA-08

SWO-MOS Failure Mode, Effects, &

Criticality Analysis (FMECA)

Initial: per Task Order PDR/DMR - 2 weeks

Final: per Task Order CDR/DMR + 30 days A

MA-09

SWO-MOS Reliability, Maintainability, and Availability

(RMA) Program Plan

Initial: per Task Order PDR/DMR - 2 weeks

Final: per Task Order CDR/DMR + 30 days

Update as required

R

MA-10 SWO-MOS RMA Predictions Report

Initial: per Task Order PDR/DMR - 2 weeks

Final: per Task Order CDR/DMR + 30 days

Update as required

A

MA-17 SWO-MOS Software Assurance Plan

Initial: per Task Order PDR/DMR – 2 weeks

Final: per Task Order CDR/DMR + 30 days

Update as required

R

MA-18 SWO-MOS Trend Analysis Report Final: First RRR + 30 days

Updates: Quarterly or as directed R

S P E C I A L S T U D I E S

SS-01 Special Study Reports Final: as directed

Updates: as directed R

5 DATA ITEM DESCRIPTIONS

The DIDs in this section are listed in the order used for the tables in Section 4 and represent a

NOAA-NASA standard numbering convention for CDRLs.

CDRLs that apply to the Base PWS requirements and all subsequent task orders shall be reviewed and updated at the start of each new task order as directed by the CDRL Applicability

Matrix. Any required information that is specific to a particular task order shall be clearly segregated by section, tab, appendix, etc. within the updated CDRL.

5.1 SWO-MOS Project Management Plan [PM-01]

The SWO-MOS Project Management Plan (PMP) describes how the SWO-MOS project is organized and managed inclusive of all subsequent task orders. It provides the management structure, its system of operation, and responsible lines of communications. In addition, it provides task order specific project management information, as needed.

The SWO-MOS PMP shall describe the overall project organization and management, including:

a) How and where the program will operate during all iterations and increments of the contract.

b) Organizational structure, including interrelationships of technical, business, and subcontract management.

c) Authority of the project manager relative to other programs and support organizations.

d) Interfaces with the Government.

e) How the PWS requirements will be achieved (include a description of planned activities for identifiable PWS requirements).

f) Indicate critical paths, long-lead items and significant milestones down to the lowest level of the WBS.

The SWO-MOS PMP shall describe the mission assurance organization structure, emphasizing:

a) Staffing plans

b) Reporting channels

c) Authority and responsibilities

d) Management visibility supporting iterative development and cross-functional collaboration.

e) Integration with the SWO-MOS Mission Assurance Implementation Plan [MA-01]

The SWO-MOS PMP shall describe the resource management system, including how it will be used to plan, track, and report status of contract scope.

The SWO-MOS PMP shall list the tools used for project planning, execution, collaboration, and product delivery.

The SWO-MOS PMP shall address system safety considerations in the project management process.

The SWO-MOS PMP shall include management and tracking of reliability, maintainability, and availability requirements throughout the project lifecycle.

5.2 SWO-MOS Integrated Master Schedule [PM-03]

The SWO-MOS Integrated Master Schedule (IMS) is used to plan, monitor, communicate status, and control all activities, including pertinent resources and facilities, necessary to accomplish assigned tasks in compliance with the SWO-MOS Base PWS and all subsequent task orders.

The SWO-MOS IMS shall include:

a) The full scope of the project effort, encompassing either agile or non-agile work streams.

b) Proper identification, alignment, and synchronization among all dependencies.

c) Relevant schedule contents from GFP/GFI vendors, external interface developers, and the Government.

The SWO-MOS IMS shall be accompanied by:

a) A schedule narrative describing the overall schedule status, incremental objectives, critical path, schedule risks, and mitigation plans.

b) Change history identifying all schedule changes with rationale (task additions, deletions, duration adjustments, changes to logic) to the schedule baseline documentation.

The SWO-MOS IMS delivery shall indicate critical paths, slack, and reserve and shall include metrics to measure schedule performance, such as milestone completion rates, task variance analysis, critical path stability, and overall project timeline adherence.

The SWO-MOS IMS shall use an application that is compatible to Microsoft Project and that supports data transfer and integration.

5.3 Project Management Status Review Data Package [PM-04]

The Project Management Status Review (PMSR) data packages provide the Government with a means for assessing and monitoring the contract to ensure that the contractor effort is properly controlled. It presents accomplishments compared to planned activities and recommendations on issues or concerns.

The frequency of PMSR meetings shall be monthly, but may evolve to a meeting cadence mutually agreed with the Government.

The PMSR data package shall include all aspects of the effort covered by the contract.

The PMSR data package shall include at least the following subjects:

a) Accomplishments since last review and open action items; highlight values delivered and key milestones achieved.

b) Iteration progress, including incremental objectives, feature completion, and any deviation from the planned scope or schedule.

c) Technical issues and concerns.

d) Program and Team backlog status; including any changes since last review.

e) List of current risks, their status, and the risk’s impact to cost, schedule, and/or technical performance.

f) Performance based metrics.

g) Planned activities for next reporting period.

5.4 Meeting Minutes [PM-07]

Meeting minutes document the attendees, topics discussed, decisions made, and action items identified.

Meeting minutes shall be prepared and delivered for:

a) All reviews, PMSRs, and other activities as coordinated with the Government.

b) All incremental objectives planning, system demos, iteration planning, retrospectives, and I&A workshops.

Meeting minutes shall capture key discussion points, decisions, and action items from these meetings.

Meeting minutes shall be updated and re-posted as necessary to incorporate corrections and clarifications.

Meeting minutes shall be distributed to attendees and relevant stakeholders within 24 hours of the meetings conclusion.

Meeting minutes shall be stored in a centralized, accessible repository for future reference.

Meeting minutes shall use a standard template to ensure consistency across the project.

5.5 SWO-MOS Property Management Plan [PM-09]

The SWO-MOS Property Management Plan outlines the process for managing, tracking, and controlling personal property, documenting a continuous audit trail from receipt of an item until transfer of accountability or disposal.

The SWO-MOS Property Management Plan shall describe the tools and processes used to track project property.

The SWO-MOS Property Management Plan shall include the Personal Property Inventory List

(PPIL) that:

a) Is prepared and maintained throughout the life of the project.

b) Is provided in an electronic format with search capabilities.

c) Identifies all mission critical hardware and software.

d) And includes, at a minimum, the following information for each item:

• Equipment or part name

• Description and quantity

• Model number

• Serial number

• Manufacturer information

• Acquisition date

• Asset value (cost)

• Location and user of the property

• Procurement specifications

For requested or provided GFI/GFP, the PPIL shall incorporate PPIL(s) provided, coordinated with the Government, by GFP/GFI vendors for those subsystems

5.6 Contract Performance Report (CPR) [PM-10]

Provides the monthly status of performance data and estimates at complete, identifies approved changes to the Performance Measurement Baseline (PMB), and reports variances and projected variances at complete including explanatory analysis.

The CPR shall provide a comprehensive view of project performance, including:

a) Data pertaining to all authorized contract work, both priced and un-priced efforts.

b) Separation of direct and indirect costs.

c) Identification of cost elements for all direct reporting.

d) Earn value performance measurement data changes from the previous reporting period.

The CPR shall align with the project’s SWO-MOS Work Breakdown Structure (WBS) and include:

a) Reporting down to WBS Level 4, with lower-level reporting for elements classified as technical, schedule, or cost risk areas.

b) Specific focus on medium and high-risk WBS items until both Government project management and the Contractor agree they no longer represent significant risks.

The CPR shall include Formats 1-5, with:

a) Format 1 (DD Form 2734/1) for WBS-oriented cost data

b) Format 2 (DD Form 2734/2) for organizational-oriented cost data

c) Format 3 (DD Form 2734/3) for baseline data

d) Format 4 (DD Form 2734/4) for staffing data

e) Format 5 (DD Form 2734/5) for explanations and problem analyses

The CPR shall apply variance analysis thresholds for all level three and other special interest

WBS elements. Variance reporting and analysis are required for:

a) All Control Accounts and The Variance at Complete at the total program level.

b) Current period Cost or Schedule Variances that exceed ± 5% or ± $50,000, whichever is lower.

c) Cumulative-to-date Cost or Schedule Variances that exceed ± 5% or ± $100,000, whichever is lower.

d) Variances at Complete that exceed ± 5% or ± $100,000, whichever is lower.

e) Variance at Complete at the total program level greater than or equal to ± 5%.

The CPR shall support an integrated approach to project management by ensuring consonance with:

a) The Integrated Master Schedule (IMS)

b) Risk Management Processes, Plans and Reports.

c) Probabilistic Risk Assessment Processes and Reports (where required).

d) Monthly/Quarterly Contractor Financial Management Reports.

e) Results from Inspect and Adapt (I&A) workshops and other applicable Agile events.

The CPR shall be submitted electronically using an electronic delivery method deemed acceptable to the Project Office.

The CPR shall include metrics to evaluate contract performance, such as cost variance, schedule variance, performance against baseline estimates, or other relevant performance indicators as agreed upon with the Government.

Contractor format may be substituted for CPR formats whenever they contain all the required data elements at the specified reporting levels in a form suitable for Project management use.

5.7 SWO-MOS Earned Value Management System (EVMS) Plan [PM-11]

The SWO-MOS EVMS Plan describes the contractor's implementation of its earned value management system for the purpose of assessing the adequacy and integrity of that system.

The following is a reference guide for the EVMS Plan:

• Department of Defense Earned Value Management Implementation Guide (EVMIG)

(March 2019)

• American National Standards Institute/Electronic Industries Association (ANSI/EIA)

EIA748C-2013: Earned Value Management Systems

The SWO-MOS EVMS Plan shall demonstrate comprehensive implementation of EVMS, including:

a) Use and understanding of the contract’s overall financial and project management system regarding EVMS at all levels of management.

b) Identification of policies, methods, procedures, and training used.

c) Detailed description of the contractor’s earned value management system implementation.

The SWO-MOS EVMS Plan shall address key management processes, including:

a) Managing technical scope, schedule, cost, and risk.

b) Conducting variance analysis.

c) Developing ongoing and comprehensive estimates at completion.

d) Flow down of EVMS requirements to all major subcontracts.

The SWO-MOS EVMS Plan shall ensure integration with other management systems by:

a) Linking EVM analysis results to the contractor's Risk Management System (as applicable).

b) Correlating EVM analysis results with cost and/or schedule risk management processes.

The SWO-MOS EVMS Plan shall include provisions for system maintenance and improvement, including:

a) Revision processes at the Government's request, for changes in EVM system architecture, or major contract modifications.

b) For non-certified systems, a projected timeline with milestones to reach final certification.

c) Evidence of EVM system certification or, if not certified, the system certification status and outstanding actions for certification.

The SWO-MOS EVMS Plan shall include metrics to assess the effectiveness of the EVMS, such as Cost Performance Index (CPI), Schedule Performance Index (SPI), Forecasted versus actual costs, or other relevant performance indicators as agreed upon with the Government.

The SWO-MOS EVMS Plan shall be available in electronic physical media format upon request.

5.8 Integrated Baseline Review (IBR) Data Package [PM-12]

An IBR is a joint assessment conducted by the Government and the contractor to verify the realism and accuracy of the PMB. This involves verifying the technical content of the baseline and assessing the realism and accuracy of the related resources (performance budget and IMS).

The IBR Data Package shall provide a snapshot of the current project baseline, including:

a) Current Work Breakdown Structure (WBS) and its alignment with the project scope.

b) Up-to-date Integrated Master Schedule (IMS)

c) Current resource allocation and cost estimates

d) Latest risk register and mitigation strategies.

e) Recent performance metrics and earned value data.

The IBR Data Package shall demonstrate how the current baseline aligns with:

a) The processes and methodologies outlined in the EVMS Plan [PM-11]

b) If applicable, agile practices and metrics used in the project.

c) Current Government-approved guidance on Earned Value Management.

The IBR Data Package shall be updated and maintained throughout the project lifecycle, with revisions submitted:

a) Prior to each formal IBR

b) After significant project changes or replanning efforts

c) As requested by the Government

5.9 SWO-MOS Contract Work Breakdown Structure [PM-13]

The SWO-MOS Contract Work Breakdown Structure (CWBS) and CWBS dictionary establish a framework for defining and organizing the total scope of the project. They provide a basis for planning, reporting status, and assigning responsibilities.

The SWO-MOS CWBS shall:

a) Define the hierarchical decomposition of the project’s scope, including hardware, software, services, and facilities.

b) Include a unique identifier and title for each element.

The SWO-MOS CWBS dictionary shall:

a) Describe the scope and content of each CWBS element.

b) Map CWBS elements to features and capabilities planned for delivery in each incremental objective.

c) Provide traceability between scope, schedule, and budget.

d) Map each CWBS element to the corresponding PWS paragraph.

The SWO-MOS CWBS and CWBS dictionary shall:

a) Be consistent with the IMS [PM-03]

b) Align with the EVMS Plan [PM-11]

c) Be reflected in the IBR Data Package [PM-12] as appropriate.

The SWO-MOS CWBS and CWBS dictionary shall be made available for Government review:

a) At the conclusion of each incremental objective.

b) When significant changes occur to the project scope.

c) As requested by the Government.

5.10 Financial Reports [FM-01]

Financial reports provide the Government with the information needed to track the cost performance of the contractor in accomplishing tasks.

Financial reports shall include, at a minimum, the following categories:

a) Total prime and subcontractor direct labor hours

b) Direct labor costs

c) Prime overhead expense

d) Fringe benefits

e) Materials

f) Materials Overhead

g) Subcontractors (list separately)

h) Equipment

i) Travel

j) Other direct costs

k) Facilities capital cost of money

l) General and administrative

m) Total estimated cost

n) Fixed Fee

o) Total cost-plus fixed fee

Financial reports shall be structured in accordance with and to Level 3 of the CWBS [PM-13].

The CO may require reporting at a lower level WBS in specific cases.

Financial reports shall be delivered after each concluding incremental objective, or as otherwise specified in the contract.

Financial reports shall include a narrative explanation for variances that exceed plus or minus 5% between:

a) The Total Direct Labor Hours (prime and subcontractors) shown in the prior report and the Actual Total Direct Labor Hours shown in the current report.

b) The Total Estimated Cost amount shown in the prior report and the Actual Total

Cost amount shown in the current report.

Each variance narrative shall explain:

a) Reason for the variance

b) Impact(s) on the baseline

c) Specific corrective action(s) being taken or to be taken.

5.11 SWO-MOS Configuration Management Plan [CM-01]

The SWO-MOS Configuration Management (CM) Plan describes the contractor’s approach to establishing and maintaining the integrity of work products throughout the project lifecycle.

The SWO-MOS CM Plan shall describe the processes and procedures for the following:

a) Defining and identifying configuration items, baselines, and their relationships.

b) Configuration control; managing changes to items and baselines, including change requests, approval authorities, and tracking mechanisms.

c) Configuration status accounting; recording and reporting the status of items, baselines, and change requests.

d) Configuration audits and reviews to verify completeness, correctness, and consistency of configuration items and baselines.

The SWO-MOS CM Plan shall identify the tools, systems, and infrastructure that will be used to support configuration management activities such as:

a) Version control systems for managing software source code, hardware specifications, documents, databases, command procedures, and other artifacts.

b) Issue tracking systems for managing change requests, defects, and other configuration items.

c) Build and release management tools for creating, packaging, and deploying software deliverables.

d) Collaboration platforms for facilitating communication and coordination among team members.

The SWO-MOS CM Plan shall describe the approach for training team members on configuration management processes, tools, and their responsibilities.

The SWO-MOS CM Plan shall describe how configuration management information will be communicated to stakeholders, including but not limited to status reports, audit results, and change notifications.

The SWO-MOS CM Plan shall describe the process for regularly reviewing and improving the

CM processes based on feedback, retrospectives, and best practices.

The SWO-MOS CM Plan shall define roles and responsibilities of individuals and teams responsible for management activities, resources, and programmatic and organizational interfaces.

The SWO-MOS CM Plan shall include metrics for configuration management effectiveness, such as change request processing times, configuration audit results, baseline stability, traceability, and testing coverage.

5.12 SWO-MOS Document Tree [CM-02]

The SWO-MOS Document Tree serves as a central hub for accessing all project documentation.

The document tree is inclusive of all task orders.

The SWO-MOS Document Tree shall:

a) Include project related documentation.

b) Show relationships, delivery phasing, and maturation phasing of documents.

c) Incorporate document tree contents provided by GFP/GFI vendors, as coordinated with the Government.

d) Be organized to serve as a ready reference list.

e) Identify documents by name, number, and version.

f) Include a brief description defining the scope of each document.

The SWO-MOS Document Tree shall:

a) Be updated according to a defined cadence.

b) Include a change log detailing updates made and their rationale.

c) Be accessible to all relevant stakeholders through the project’s chosen collaboration platform.

d) Include measurable metrics for completeness and accuracy.

5.13 SWO-MOS Drawing Tree [CM-03]

The SWO-MOS Drawing Tree serves as a central hub for accessing all project drawings and diagrams. The drawing tree is inclusive of all task orders.

The SWO-MOS Drawing Tree shall:

a) Include all project related drawings.

b) Incorporate drawing tree information provided by GFP/GFI vendors, as coordinated with the Government.

c) Be organized to serve as a ready reference list, including where appropriate a pointer or link to the drawing location.

d) Identify drawings by name, number, and version.

e) Include a brief description of each drawing.

The SWO-MOS Drawing Tree shall:

a) Be updated according to a defined cadence.

b) Include a change log detailing updates made and their rationale.

c) Be accessible to all relevant stakeholders through the project’s chosen collaboration platform.

d) Include measurable metrics for completeness and accuracy.

5.14 SWO-MOS Configuration Item Identification List [CM-05]

The SWO-MOS Configuration Item Identification List identifies and describes the project’s configuration Items (CIs) and Computer Software Configuration Items (CSCIs) which are entities that are used to correlate those CIs/CSCIs to their requirements specification, testing, verification, and validation documents. The list is inclusive of all task orders.

The SWO-MOS Configuration Item Identification List shall:

a) Identify all project-level Configuration Items (CIs) and Computer Software

Configuration Items (CSCIs), including hardware, software, firmware, documents, and databases.

b) Encompass the full scope of the project effort, including CI/CSCI content from

GFP/GFI vendors, as coordinated with the Government.

c) Provide metadata for each CI/CSCI including:

• Unique Identifier

• Type

• Description / Implementation

• Test Strategy

• Mission / Safety Criticality

• Repository Location

• Owner / Responsible Team

5.15 SWO-MOS Configuration Control Board (CCB) Documentation [CM-06]

The Configuration Control Board (CCB) documentation provides a record of the CCB’s activities, decisions, and actions related to the management of the project’s configuration items.

The CCB documentation is inclusive of all task orders.

The CCB documentation shall include:

a) Agendas for each CCB meeting, detailing date, time, location, subject, sponsor, and change control number of items to be reviewed.

b) Minutes of CCB meetings, documenting decisions and action items.

c) Data packages for each proposed change, containing:

• Precise format and content for board review.

• All relevant background material.

• Complete technical supporting analyses.

• Details on replanning or rescoping, if applicable.

The CCB documentation shall be made available to relevant stakeholders through the project’s collaboration platform.

5.16 SWO-MOS Configuration Change Requests (CCRs) [CM-07]

Facilitates the orderly processing of engineering change requests to contractor specifications and requirements, changes to plans and procedures, specification deviations, and waivers, to achieve the appropriate level of review, classification, and approval authority for disposition.

The CCR shall:

a) Be classified as either Class I (changes beyond the scope of the baseline) or Class II

(changes within the scope of the baseline).

b) Include sufficient information (attachments, drawings, test results, etc.) to allow thorough impact assessment.

c) Be prepared in accordance with the SWO-MOS CM Plan [CM-01] and as directed by the Contracting Officer under the “Changes” clause of the contract.

Class I CCRs shall:

a) Be submitted for Government review.

b) Contain detail information on the proposed change, including rationale, impact assessment, and implementation approach.

The CCR log shall:

a) Identify each CCR as either Class I or Class II.

b) Track the status and disposition of all CCRs.

c) Be accessible to relevant stakeholders through the project’s collaboration platform.

d) Include fields for change description, impact assessment, approval status, and implementations status.

5.17 SWO-MOS Risk Management Plan (RMP) [RM-01]

Defines the continuous risk management process by which the contractor identifies, evaluates and minimizes the risks associated with program, project, and mission goals.

The SWO-MOS Risk Management Plan (RMP) shall:

a) Be a configuration-controlled document.

b) Comply with requirements of NPR 8000.4 Agency Risk Management Procedural

Requirements.

c) Include an overview of the program/project risk objectives, policy, purpose, scope, assumptions, constraints, and key ground rules.

d) Provide an overview of the continuous risk management process, including methodologies, procedures, tools, and metrics.

e) Describe integration with other project management, systems engineering, and if applicable, agile activities.

f) Explain the relationship between the contractor’s Risk Management Board (RMB) and associated SWO RMB(s) and how risk information continuously flows throughout the contractor’s organization.

The SWO-MOS RMP shall specify:

a) The format and data elements for the project Risk List [RM-02] (and/or Risk

Database).

b) Configuration control application and list usage/update procedures.

c) How team members can access the current list at any time.

The SWO-MOS RMP shall describe:

a) Key interfaces between the risk management process and other business reporting systems.

b) Metrics for risk management effectiveness.

The SWO-MOS RMP shall include:

a) Appendix(es) for detailed or sensitive material, placed under configuration control.

b) An alphabetized list of definitions for abbreviations, acronyms, and special terms.

5.18 Risk List [RM-02]

Provides information on performance, cost, and schedule risks to definition, development, integration, test, transition to operations, and operations and sustainment. Contractor may request

Government approval to use and existing Contractor practice processes or tools as an option for this CDRL delivery.

The Risk List shall:

a) Be prepared in accordance with the contractor's Risk Management Plan [RM-01].

b) Include a description of each risk, including causes, contributors, and mitigation actions.

c) Provide a risk projection or waterfall chart…