SWO-MOS-CDRL-0001_02-27-2025.pdf

Effective Date: February 26, 2025

Expiration Date: February 26, 2030

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

SWGS-MOS-CDRL-0001, Revision -

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

02/27/2025

Released

DRAFT

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

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

Space Weather Observations

Mission Operations Services

(SWO-MOS)

Contract Data Requirements List (CDRL)

Review/Signature/Approval Page

Prepared by:

David Nguyen

Reviewed by:

Ava Afghahi

Susan Jacobs

Fiza Chaudry

Scott Schnee

Laura Dunlap

Maria Amaro

David Donovan

Brian Frey

Kenneth Jensen

Andrew Royale

Katherine Spotz

Approved by:

Jill Taylor ii

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:

SWO Configuration Management Office

NASA/GSFC

Code 492.0

Greenbelt, MD 20771 iv

Table of TBDs/TBRs/TBSs

Action Item

No.

Location Summary Individual/

Organization

Actionee v

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 Factory IT System Security and Contingency Plan [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]

vi

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 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 Design Modification Review (DMRs) Packages [RE-03]

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

5.35 Factory Test Readiness Review Packages [RE-13]

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

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

5.38 Test Readiness Review (TRR) Packages [RE-18]

5.39 Acceptance Data Package [RE-21]

5.40 General Review Packages [RE-24]

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

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

5.43 Software Test Plans and Procedures [SW-03]

5.44 Software Test Reports [SW-04]

5.45 Software Delivery Packages [SW-06]

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

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

5.48 Post-Test Data Package [IT-03]

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

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

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

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

5.53 SWO-MOS Maintenance Records [TO-09]

5.54 SWO-MOS Training Plans [TO-10]

5.55 SWO-MOS Training Materials [TO-11]

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

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

5.58 SWO-MOS Mission Assurance Implementation Plan (MAIP) [MA-02]

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

5.60 SWO-MOS Preliminary Hazard Analysis Report [MA-04]

5.61 SWO-MOS Reliability, Maintainability, and Availability (RMA) Program Plan [MA-05]

5.62 SWO-MOS Analysis of Design Report [MA-06]

5.63 SWO-MOS Software Assurance Plan [MA-07]

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

5.65 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 applicable to all task orders under SWO-MOS Base IDIQ contract as 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

These CDRLs apply to all SWO-MOS IDIQ Task Orders as provided in Appendix A, Applicability Matrix.

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

Reference (A&R) Documents List, SWGS-MS-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 any other dictionary, the SWO terminology will take precedence. In the event of any unresolved conflict, the Contractor must request conflict resolution by the Contracting Officer.

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.

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 entire SWO-MOS inclusive of the Base PWS requirements and all subsequent task orders shall be reviewed and updated at the start of each new task order. 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 SOW requirements will be achieved (include a description of planned activities for identifiable SOW requirements).

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

The SWO-MOS PMP shall detail the project’s agile methodology, including:

a) Implementation of the Agile process.

b) Agile procedures for managing administrative and engineering changes.

c) Cadence and synchronization of agile ceremonies.

d) Use of agile artifacts, information radiators, and metrics.

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] DRAFT

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 both agile and 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 delineate the agile framework implementation by:

a) Showing the cadence and synchronization points for Program Increments (PIs), iterations, and other Agile events and ceremonies.

b) Maintaining vertical traceability to the portfolio backlog, program backlog, and team backlogs throughout the entire contract performance.

c) Establishing clear milestones or checkpoints at the end of each PI to align with the overall project schedule.

The SWO-MOS IMS shall include a revision process to accommodate changes and refinements throughout the project lifecycle, in line with the Agile framework’s emphasis on continuous planning and adaptation.

The SWO-MOS IMS shall be accompanied by:

a) A schedule narrative describing the overall schedule status, PI 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. Each task order will provide a PMSR.

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, tailored to align with the

Agile framework:

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

b) PI and iteration progress, including PI 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) Risks, issues, and dependencies related to agile work packages.

f) Continuous Improvement initiatives and results from Inspect & Adapt workshops.

g) Performance based metrics.

h) Planned activities for next reporting period.

The PMSR data package shall be delivered at the conclusion of each PI planning event, summarizing status from the prior PI.

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 relevant Agile ceremonies and events, including PI 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 plan applies to all task orders.

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) Incorporates PPIL(s) provided, coordinated with the Government, by GFP/GFI vendors for those subsystems.

e) 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

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. Each task order will provide a CPR.

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 integrate with the project’s agile framework by:

a) Aligning reporting periods with PIs.

b) Including agile metrics such as velocity, burndown/burnup charts, and feature completion rates.

c) Mapping traditional earned value concepts to agile artifacts (e.g., relating story points to budget and schedule performance)

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 relevant 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 plan applies to all task orders.

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).

Each task order will provide an IBR.

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) 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 plan applies to all task orders.

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 PI.

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 PI.

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. Each task order will provide financial reports.

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 PI, 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 plan applies to all task orders.

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 describe how CM processes will be applied to support agile development practices, including:

a) Management of configuration items at various levels of granularity.

b) Maintaining traceability between configuration items and their associated requirements, design artifacts, and test cases.

c) Establishing and managing baselines for iterative and incremental deliveries.

d) Integrating CM with continuous integration and continuous delivery processes.

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. SWO-

MOS CCR applies to all task orders.

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 process shall be integrated with the project’s Agile framework.

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 plan applies to all task orders.

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 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. Each task order will provide a risk list.

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 showing anticipated future changes in risk level.

The Risk List shall include for each risk:

a) Primary consequences if the undesired event occurs.

b) Estimate of the probability of occurrence and uncertainty.

c) Effectiveness of implemented risk mitigation measures.

d) Additional tracking information (originator, classification, owner, timeframe).

The Risk List shall provide:

a) Potential additional risk mitigation measures.

b) Cost comparison of risk mitigation versus occurrence probability.

The Risk List shall:

a) Characterize risks as "acceptable" or closed, with rationale and Government concurrence.

b) Allow the Government to inject their own risks into the list.

The Risk List shall:

a) Support metrics for tracking such as number of identified risks, mitigation status, and severity changes.

b) Be prepared for the monthly RMB.

c) Include an update of risks, as well as risk handling plans and status for all higher-level risks.

d) Be accessible via the contractor's Risk Management Tool, which may substitute for monthly document delivery if approved by the Government.

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

Provides a comprehensive assessment of the management, operational, and technical security controls of the project, made in support of security accreditation, to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting the security requirements. The plan applies to all task orders.

The scope and responsibility of the plan includes:

a) For systems within NOAA5050, the Contractor shall provide necessary inputs and updates to support the Government’s maintenance of existing security documentation and support A&A (Assessment &Authorization) activities.

b) All compliance documentation associated with NIST security standards.

The IT System Security and Contingency Document shall include:

a) System Security Plan

b) Risk Assessment

c) Contingency Plan

d) Security Assessment Report

e) Plans of Action and Milestone (POA&M)

f) FIPS 199 Determination

g) Privacy Impact Assessment

The IT System Security and Contingency Document shall comply with the following NIST

Special Publications:

a) NIST SP 800-18: Guide for Developing Security Plans for Information Technology

Systems.

b) NIST SP 800-30: Risk Management Guide for Information Technology Systems

c) NIST SP 800-34: Contingency Planning Guide for Information Technology Systems

d) NIST SP 800-37: Risk Management Framework for Information Systems and

Organizations: A System Life Cycle Approach for Security and Privacy

[Assessment & Authorization (A&A)]

e) NIST SP 800-53: Security and Privacy Controls for Information Systems and

Organizations

f) NIST SP 800-53A: Guide for Assessing the Security Controls in Federal

Information Systems.

The IT System Security and Contingency Document shall adhere to applicable NOAA and DOC

IT Security Requirements, including:

a) NOAA Privacy Impact Assessment Template

b) NESDIS A&A Project Plan Template

c) OMB Memo 03-19: Reporting Instructions for the Federal Information Security

Management Act and Updated guidance on Quarterly IT Security Reporting.

For systems and services outside NOAA5050 boundaries:

a) Any appropriate system documentation shall be developed in separate appendices with specific information for each system or service..

b) These appendices shall include all inputs required for Government-maintained IT

System Security and Contingency Documentss.

The IT System Security and Contingency Document shall:

a) Incorporate relevant A&A inputs provided by GFP vendors for subsystems, as directed by the project.

b) Include a comprehensive hardware/software inventory that:

• Is complete and up-to-date as of 18 months before GRD.

• Details all system components within the defined security boundary.

• Provided information for security management and control.

c) Contains the full set of A&A documentation, completed and ready for review no later than 3 months before yearly A&A documentation deadlines are delivered to the

Government less than 12 months before GRD.

d) Reflect all changes identified and required by the independent Security Testing &

Evaluation activity in the pre-ATO final version.

The IT System Security and Contingency Document shall be:

a) Updated once for each yearly A&A process

b) Updated when a major change is made that affects security.

c) Reviewed and updated at least every three years after the most recent ATO.

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

Documents the contractor's planned method of identifying and conducting all Systems

Engineering (SE) related activities under this contract. The plan applies to all task orders.

The SWO-MOS SEMP shall describe the overall lifecycle including the major activities events, reviews, and alignment with the Agile framework and its ceremonies.

The SWO-MOS SEMP shall comply with the format and content specified by NPR 7123.1

Appendix D and guidance provided by SP-2016-6105 NASA SE Handbook.

The SWO-MOS SEMP shall outline the contractor’s approach for conducting SE activities to support the full scope of the Contractor project, including interactions with GFP/GFI vendors, external interfaces, subcontractors, and the Government.

The SWO-MOS SEMP shall describe processes and mechanisms for but not limited to:

a) Requirements management (identification, allocation, tools, and full traceability across all levels)

b) Verification and Validation (V&V)

c) Technical risk management (role in risk processes, reliability analysis)

d) Configuration management of SE work products

e) Baselining and change control.

The SWO-MOS SEMP shall discuss integration of traditional SE with agile engineering practices including:

a) Maintaining requirements traceability across agile artifacts (epics, features, user stories)

b) Continuous Exploration (CE), Continuous Integration (CI), Continuous Delivery

(CD), and automated and regression testing frameworks

c) Technical debt management

The SWO-MOS SEMP shall outline the model(s), tools, and data management approach for SE activities.

The SWO-MOS SEMP shall define the communications plan, including recurring meetings, working groups, reporting, and information sharing mechanisms.

The SWO-MOS SEMP shall document SE organizational structure, roles, responsibilities, and required skillsets.

The SWO-MOS SEMP shall include a top-level schedule outlining major SE events/milestones aligned to the Project’s PI cadence.

The SWO-MOS SEMP shall include metrics for systems engineering effectiveness, such as requirements traceability, verification and validation competition rates, and technical performance measures.

The SWO-MOS SEMP shall define the process for regular review and assessment of compliance with its provisions, including the responsible parties for conducting and approaching such assessments.

5.21 SWO-MOS Operations Concept [SE-02]

Describes the proposed system in terms of the operator and user needs it will fulfill, its relationship to existing systems or procedures, the satellite operational needs, and the external operational interfaces. The operations concept applies to all task orders.

The SWO-MOS Operations Concept shall:

a) Include content as specified in DI-IPSC-81430 Operational Concept Description.

b) Address the full scope of the Solution, including GFP/GFI vendors, external interfaces, subcontractors, and the Government.

c) Describe the relationship to existing systems or procedures.

The SWO-MOS Operations Concept shall describe the incremental delivery of capabilities aligned with PI planning within the Agile framework.

The SWO-MOS Operations Concept shall address the multi-program concept of:

a) Unified Configuration Management

b) Anomaly Reporting & Tracking System

c) Continuous integration and continuous delivery practices.

The SWO-MOS Operations Concept shall include metrics to measure operational readiness and performance, such as system availability, mean time between failures (MTFB), and mean time to repair (MTTR).

5.22 SWO-MOS Requirements Document [SE-03]

Specifies the requirements for the Solution provided in the MOSRD and requirements sub-allocated to lower levels or to infrastructure. It also specifies methods or tests to be used to ensure that each requirement has been met. The document applies to all task orders.

The SWO-MOS Requirements Document shall:

a) Contain content specified in DI-IPSC-81431 System/Subsystem Specification and

MIL-STD-961 Defense and Program-Unique Specifications Format and Content.

b) Address the total Solution scope, incorporating requirements specifications provided by GFP vendors as directed by the Government.

c) Include clear and direct traceability to contract and/or task order requirements.

d) Define the boundaries of the Solution, including demarcation points between the

Solution and external interfaces.

The SWO-MOS Requirements Document shall describe:

a) The overall approach for identifying, analyzing, and developing requirements.

b) Any prototyping techniques used in requirements development.

c) Trade studies used to analyze requirements, including references to these studies.

The SWO-MOS Requirements Document shall define:

a) Software and hardware requirements to ensure compliance with contractual and

Government Level 3 requirements.

b) Appropriate allocated and derived requirements from the SWO Solution F&PS, IRDs, MAR, and SOW.

The SWO-MOS Requirements Document shall:

a) Allocate specification performance levels.

b) Identify all installation-specific and facility requirements.

c) Direct and control lower-level Solution Design Specification and Element-level specifications.

The SWO-MOS Requirements Document shall maintain bi-directional traceability between requirement artifacts.

The SWO-MOS Requirements Document shall include metrics for management, such as requirements stability, traceability, coverage, and volatility.

The SWO-MOS Requirements Document shall describe the process for continuous prioritization and refinement of requirements throughout the project lifecycle, aligned with the agile development approach. The SWO-MOS Requirements Document shall reference SE-04 for external interface requirements.

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

SWO-MOS External Interface Requirements Specifications specify the requirements necessary to support the external interfaces and the methods to be used to ensure that each requirement has been met. The specification applies to all task orders.

The SWO-MOS External Interface Requirements Specification shall:

a) Contain the content specified in the DI-IPSC-81434 Interface Requirements

Specification and MIL-STD-961 Defense and Program-Unique Specifications

Format and Content (contractor equivalent format is acceptable).

b) Define the requirements for external interfaces.

c) Include appropriate allocated and derived requirements from the MOSRD, IRDs, MAR, and SOW.

d) Describe the common messaging formats across all interfaces.

The SWO-MOS External Interface Requirements Specification shall include a Data Transfer

Workload Table that specifies, for each defined data transfer:

a) Data type

b) Source and destination

c) Delivery frequency and latency

d) File Size

The SWO-MOS External Interface Requirements Specification shall be delivered in an archived database that:

a) Includes modules of the specifications and associated link modules.

b) Incorporate modules of the higher- and lower-level specifications to which the specification traces directly.

c) Uses the Government-provided modules for traceability to documents provided by the Government in database module format.

The Contractor shall:

a) Replace Government database modules with new modules as received from the

Government following CCR approvals.

b) Update link traceability as necessary.

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

Specifies the requirements for the Solution Elements and Infrastructure, the requirements allocation to the Element and Infrastructure subsystems and end items, and the methods to be used to ensure that each requirement has been met. The specification applies to all task orders.

The SWO-MOS Element and Infrastructure Requirements Specification shall:

a) Contain the contents specified in DI-IPSC-81431 and MIL-STD-961. Contractor equivalent format is acceptable.

b) Define the boundaries of the Solution elements and infrastructure including demarcation points between the element/infrastructure and external interfaces.

c) Define the requirements for the specific Solution Element and Infrastructure, incorporating requirements specifications provided by GFP vendors.

d) Address the total Solution scope.

e) Address the element and infrastructure scope incorporating requirements specifications provided by GFP vendors.

The SWO-MOS Element and Infrastructure Requirements Specification shall identify and allocate the appropriate requirements to capability-based builds (CBBs).

The SWO-MOS Element and Infrastructure Requirements Document shall maintain bi-directional traceability between requirement artifacts.

The SWO-MOS Element and Infrastructure Requirements Document shall include metrics for management, such as requirements stability, traceability, coverage, and volatility.

The SWO-MOS Element and Infrastructure Requirements Document shall describe the process for continuous prioritization and refinement of requirements throughout the project lifecycle, aligned with the agile development approach.

The SWO-MOS Element and Infrastructure Requirements Specification shall be captured in SE-

06 Internal Interface Requirements Specification.

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

SWO-MOS Internal Interface Requirements Specification specify the requirements necessary to support the interfaces external to a particular element and infrastructure. The specification applies to all task orders.

The SWO-MOS Internal Interface Requirements Specification shall:

a) Contain the content specified in DI-IPSC-81434 Interface Requirements

Specification and MIL-STD-961 Defense and Program-Unique Specifications

Format and Content (contractor equivalent format is acceptable).

b) Define the requirements for the Element and Infrastructure external interfaces to other Elements and Infrastructure, including the interfaces to GFP end-items.

c) Describe the common messaging formats across all interfaces.

The SWO-MOS Internal Interface Requirements Specification shall include a Data Transfer

Workload Table that specifies, for each defined data transfer:

a) Data type

b) Source and destination

c) Delivery frequency and latency

d) File Size

For external interfaces that are the same for an Element and Infrastructure as for an External

Interface, the requirements shall be captured in the higher-order Specification and cited in the lower one.

The SWO-MOS Internal Interface Requirements Specification shall:

a) Be delivered using the contractor’s proposed requirements management toolset and format.

b) Include each requirement specification, its attributed, and rationale.

c) Provide complete traceability across all levels, with…