20250227 SWO-MOS CDRL.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

Space Weather O servati ns

Mission Operations Se vices

(SWO-MOS)

Contract Data Re uir ments Li t (CDRL)

U.S. D rtm of Commerce (DOC)

National nic and Atmospheric Administration (NOAA)

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

National Aeronautics and Space Administration (NASA)

SWO eviewed – Not ject 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 i pproved, changes are handled in accordance with Class I and Class II change control re ements as described in the SWGS Configuration Management Procedures, and chang is 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 Indivi ual/

Org zation ctionee v

Table of Contents

1 INTRODUCTION

1.1 Scope

1.2 Purpose

2 RELATED DOCUMENTATION

3 IDENTIFICATION, REFERENCE, DELIVERY, AND ACCEPT NCE

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 Procedur

3.11 Document Markings

4 CONTRACT DATA REQUIREMENT LIST

4.1 SWO-MOS CDRL Summary List

5 DATA ITEM DESCRIPTIONS

5.1 SWO-MOS Proj ement Plan [ 01]

5.2 SWO-MOS I grated Ma r Schedule [ M-03]

5.3 Project Ma gement Statu Review Data P kage [PM-04]

5.4 Meetin Minutes [PM-07

5.5 SWO-M Property M Plan [PM-09]

5.6 Contract P rman Report (CPR) [ 10]

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

5 8 rated Basel Review (IBR) Data Package [PM-12]

SWO OS Contra Work Breakdown Structure [PM-13]

5.10 Financial ports [FM ]

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

5.12 SWO-MOS D ument Tree [CM-02]

5.13 SWO-MOS D wing Tree [CM-03]

5 14 SWO-MOS C figuration Item Identification List [CM-05]

5 SWO-MOS nfiguration Control Board (CCB) Documentation [CM-06]

5.1 WO-MO Configuration Change Requests (CCRs) [CM-07]

5.17 S O-M S Risk Management Plan (RMP) [RM-01]

5.18 Ris st [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-1

5.37 Release Readiness Review (RRR) Packages [R 7]

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 Managemen and Development Plan MDP) [SW-01]

5.42 SWO-MOS Software Verificatio an lidation Plans [SW ]

5.43 Software Test Plans and Procedur [SW-0

5.44 Software Test Reports [SW-04]

5.45 Software Delivery Packages [SW-06

5.46 SWO-MOS Integration, Test and Veri atio lan [IT-01]

5.47 Detailed Test Pla Procedures [I ]

5.48 Post-Test Data ackage [ 03]

5.49 SWO-MOS ansition and perations Su ort Plan [TO-01]

5.50 SWO-M Operations an Maintenance M uals [TO-03]

5.51 SWO-M S Ground Op io Procedures [TO-07]

5.52 SWO-MO Mainten e, Logist paring Plan [TO-08]

5.53 SWO-MOS nt ance Records [TO-09]

5.54 SWO-MOS Tra g Plans [TO-10]

SW OS Traini Materials [TO-11]

5.56 SWO-M Facility R uirements Implementation Plans [TO-15]

5.57 SWO-MOS ission Ass nce Implementation Plan (MAIP) [MA-01]

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

5.59 SWO-MOS S em Safety Program Plan [MA-03]

5.60 SWO-MOS P minary Hazard Analysis Report [MA-04]

61 SWO-MOS R iability, Maintainability, and Availability (RMA) Program Plan [MA-05]

5.62 WO-M S Analysis of Design Report [MA-06]

5.63 SW 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 delive les applicable to all task orders under SWO-MOS Base IDIQ contract as defined in Appendi A, Table 2.

1.2 Purpose

The purpose of this document is to provide a comprehensive list and d criptions of data items the Contractor shall deliver under this contract. The Govern ent may provide m l artifacts for many of these data items as Government-furnished perty (GFP) or Govern nt-furnished information (GFI). The Contractor may use provid GFP/GFI to inform their own development of CDRLs. Additionally, the Contractor may quest Government approval to use existing Contractor practice for format, processes, or t to meet the CD L delivery requirements. Government approval for changes may on be granted 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) Applica and

Reference (A&R) Documents List, SWGS-MS-LIST-0003, provides the list pplicable and reference documents for the CDRLs with their sources. In the event of any n lved conflict, the Contractor must request conflict resolution by the Contracting Offic n adva of work performed.

The SWO Program Acronym and Glossary List, SWO-MGMT ST-0001, defines termin gy as used in this document and throughout the SWOPD. In the ent of conflict between terminology in this document and any other dictionary, th WO terminology will take precedence. In the event of any unresolved conflict, th ontractor must quest 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 o ages containing such materials.

Documents containing Contractor proprietary materials or information, as de mined by the

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

Documents shall not be unnecessarily or unjustifiably marked with re ctive or lim g 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 requirem ts and all subsequent task orders shall be reviewed and updated at the start of each new k order. Any required information that is specific to a particular task order shall be clea seg ated 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) describe w the SWO-MOS project is organized and managed inclusive of all subsequent task ers. It provide the management structure, its system of operation, and responsible line communicati . In addition, it provides task order specific project management informa as nee .

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

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

b) Organizational structure, inc ding in lationships of te ical, business, and subcontract management.

c) Authority of the project manag relative t ther p ms and support organizations.

d) Interfaces wi Government.

e) How the S W requ ments will b chieved (include a description of planned activiti for identifia SOW requi ments).

f) Indi e critical path ong-lead item d significant milestones down to the lowest l of the WBS.

The SWO-MOS P shall ail the proje gile methodology, including:

a) Implemen n of the Agile process.

gile proce s for managing administrative and engineering changes.

c) C ce and sy ronization of agile ceremonies.

d) Use gile artifa information radiators, and metrics.

The SWO-MOS PM hall describe the mission assurance organization structure, emphasizing:

a) Staffing ns

b) Reportin channels

c) Autho and responsibilities

d) Ma ement visibility supporting iterative development and cross-functional c aboration.

e) ntegration 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 m nagement process.

The SWO-MOS PMP shall include management and tracking of reliabili main ability, 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 ta orders.

The SWO-MOS IMS shall include:

a) The full scope of the project effort, encompassing both agile an -agile work streams.

b) Proper identification, alignment, and synchronization am g all depen cies.

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

The SWO-MOS IMS shall delineate the agile framework im mentation by:

a) Showing the cadence and synchronization nts for Program Increments (PIs), iterations, and other Agile events and cere nies.

b) Maintaining vertical traceability to the portfo backlo program backlog, and team backlogs throughout the entire contract pe nce.

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

The SWO-MOS IMS shall include a revi n pro to accommodate nges and refinements throughout the project lifecycle, in line wi he Agile work’s emphasis on continuous planning and adaptation.

The SWO-MOS IMS shall be accompanied by

a) A schedul rrati escribing th erall schedule status, PI objectives, critical path, sch dule risks, mitigation ns.

b) Chan history identi ng all schedu changes with rationale (task additions, d ons, duration a ustments, chang o logic) to the schedule baseline doc entation.

The SWO-MOS IM li y shall indicate critical paths, slack, and reserve and shall include metrics to measure sch e performance, such as milestone completion rates, task variance an , l path stab and overall project timeline adherence.

he SWO-MOS S shall us application that is compatible to Microsoft Project and that supports data trans and integra on.

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 recomm dations 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 tract.

The PMSR data package shall include at least the following subjects, tail d to n with the

Agile framework:

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

b) PI and iteration progress, including PI objectiv feature completion, and any deviation from the planned scope or schedul

c) Technical issues and concerns.

d) Program and Team backlog status; including y chang ince last review.

e) Risks, issues, and dependencies related to agil rk kages.

f) Continuous Improvement initiatives and results fr nspect & Adapt workshops.

g) Performance based metrics.

h) Planned activities for next r o period.

The PMSR data package shall be delivere t the co ion of each PI p nning 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 ernment.

b) All relevant Agile ceremonies and events, including PI plannin tem demos, iteration planning, retrospectives, and I&A workshops.

Meeting minutes shall capture key discussion points, decisions, and ac on items from ese meetings.

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

Meeting minutes shall be distributed to attendees and r vant stakehold within 24 hours of the meetings conclusion.

Meeting minutes shall be stored in a centralized, accessible r s y for future reference.

Meeting minutes shall use a standard template to ensure consiste 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 proces used to track project property.

The SWO-MOS Property Management Plan shall include the Personal P erty ntory List

(PPIL) that:

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

b) Is provided in an electronic format with search ca ilities.

c) Identifies all mission critical hardware and soft e.

d) Incorporates PPIL(s) provided, coordinated h the Government, by GFP/GFI vendors for those subsystems.

e) And includes, at a minimum, the following rmation each item:

• Equipment or part name

• Description and quantity

• Model number

• Serial number

• Manufacturer informat

• Acquisition date

• Asset value (cost)

• Location and user of the pr ert

• Procu cifications

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

The CPR shall provide a comprehensive view of project performance, includ

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

b) Separation of direct and indirect costs.

c) Identification of cost elements for all direct reporting

d) Earn value performance measurement data changes m the previous report period.

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

a) Reporting down to WBS Level 4, with lower el rep ng for elements classified as technical, schedule, or cost risk areas.

b) Specific focus on medium and high-risk WBS item ntil both Government project management and the Contra agree they no longer resent significant risks.

The CPR shall include Formats 1-5, with

a) Format 1 (DD Form 2734/1) f WBS-orien t data

b) Format 2 (DD Form 2734/2) fo rganizat nal-orie cost data

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

d) Format 4 (D 2734/4) for s g data

e) Format 5 D Form 34/5) for exp nations and problem analyses

The CPR shall ap variance ana is thresholds all level three and other special interest

WBS elements ariance reporti and analysis are quired for:

a) All trol Acc ts and ce at Complete at the total program level.

b) Curren io Cost or Schedule Variances that exceed ± 5% or ± $50,000, whichever ower.

) mulative- ate Cost or Schedule Variances that exceed ± 5% or ± $100,000, wh ver is lo

d) Varia s at Comp that exceed ± 5% or ± $100,000, whichever is lower.

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

The CPR shall integr with the project’s agile framework by:

a) Alignin eporting periods with PIs.

b) Includ g agile metrics such as velocity, burndown/burnup charts, and feature com etion rates.

c) pping 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 emed acceptable to the Project Office.

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

Contractor format may be substituted for CPR formats when they contain all the require data elements at the specified reporting levels in a form su le 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 (EVMIG)

(March 2019)

• American National Standards Institute/Electronic Industries As ciation (AN /EIA)

EIA748C-2013: Earned Value Management Systems

The SWO-MOS EVMS Plan shall demonstrate comprehensiv mplementation of EVMS, including:

a) Use and understanding of the contract’s ov all financial an roject management system regarding EVMS at all levels of ma ement.

b) Identification of policies, methods, procedure d tra ng used.

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

The SWO-MOS EVMS Plan shall addre k anagement process including:

a) Managing technical scope, sc dule, cos d risk.

b) Conducting variance analysis.

c) Developing ongoing and compr ensive imates at mpletion.

d) Flow down of EVMS requiremen to major subcontracts.

The SWO-MOS EVM lan sha nsure integr on with other management systems by:

a) Linki EVM analys esults to the tractor's Risk Management System (as ap able).

b) Co lating EVM lts with cost and/or schedule risk management proce s

The SWO-MOS EVM an shall include provisions for system maintenance and improvement, incl

a) Re n process t the Government's request, for changes in EVM system archit re, or maj contract modifications.

b) For non rtified systems, a projected timeline with milestones to reach final certifica .

c) Evidenc f EVM system certification or, if not certified, the system certification status a outstanding actions for certification.

The SW MO EVMS Plan shall include metrics to assess the effectiveness of the EVMS, such as Cost Pe mance 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 budge d IMS).

Each task order will provide an IBR.

The IBR Data Package shall provide a snapshot of the current project baseli ncluding:

a) Current Work Breakdown Structure (WBS) and its alignme ith roject 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 da

The IBR Data Package shall demonstrate how the curren seline aligns with:

a) The processes and methodologies outlined the EVMS P n [PM-11]

b) Agile practices and metrics used in the proje

c) Current Government-approved guidance on Ear V ue Management.

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

a) Prior to each formal IBR

b) After significant project chang or replann rts

c) As requested by the Governmen

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

The SWO-MOS CWBS shall:

a) Define the hierarchical decomposition of the project’s scope, in ng 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 el ent.

b) Map CWBS elements to features and capabili planned for delivery in each PI.

c) Provide traceability between scope, schedul and budget.

d) Map each CWBS element to the correspon g PWS para ph.

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 Dat Pac [PM-12] as approp te.

The SWO-MOS CWBS and CWBS dictio ry shall b d available fo Government review:

a) At the conclusion of each PI.

b) When significant changes occur the ject scope.

c) As requested 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 accor nce with d to 3 of the CWBS [PM-13].

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

Financial reports shall b d after each c uding PI, or as otherwise specified in the contract.

Financial reports all include a n ative explana for variances that exceed plus or minus 5% between:

a) The l Dire abor Hour and subcontractors) shown in the prior report and the u Total Direct Labor Hours shown in the current report.

b) The Total mated Cost amount shown in the prior report and the Actual Total t amount wn in the current report.

Each variance na ive shall e ain:

a) Reason the variance

b) Impact(s n the baseline

c) Specific rective 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 fo wing:

a) Defining and identifying configuration items, baselines, and th ationships.

b) Configuration control; managing changes to items and basel s, in ding change requests, approval authorities, and tracking mechanisms.

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

d) Configuration audits and reviews to verify comp ness, correctness, and consistency of configuration items and baseli

The SWO-MOS CM Plan shall describe how CM pro es will be appl to support agile development practices, including:

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

b) Maintaining traceability between configuration item nd their associated requirements, design artifact nd test cases.

c) Establishing and managing seli f r iterative and in ental deliveries.

d) Integrating CM with continu integra nd continuous livery processes.

The SWO-MOS CM Plan shall identify the ols, system an structure that will be used to support configuration management activities ch as

a) Version con ms for manag software source code, hardware specifica ns, docum ts, database command procedures, and other artifacts.

b) Issue king system or managing ange requests, defects, and other con guration items

c) B and release m a nt tools fo creating, packaging, and deploying software deliv bles.

d) Collabo o latforms for facilitating communication and coordination among team mem

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 resu and change notifications.

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

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

The SWO-MOS CM Plan shall define roles and responsibilities of ind duals and s responsible for management activities, resources, and programmatic and organizationa interfaces.

The SWO-MOS CM Plan shall include metrics for configur n management effectiveness, such as change request processing times, configuration a 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 uments.

c) Incorporate document tree contents provided by GFP/GFI v ors, oordinated 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 h document.

The SWO-MOS Document Tree shall:

a) Be updated according to a defined cadenc

b) Include a change log detailing updates made their onale.

c) Be accessible to all relevant stakeholders throug roject’s chosen collaboration platform.

d) Include measurable metrics f ompleteness and acc y.

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 ve as coordinated with the Government.

c) Be organized to serve as a ready reference list, including ere approp e 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 cadenc

b) Include a change log detailing updates made their onale.

c) Be accessible to all relevant stakeholders throug roject’s chosen collaboration platform.

d) Include measurable metrics f ompleteness and acc y.

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 esting, 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 Com ter S ware

Configuration Items (CSCIs), including hardware, softwa firmware, uments, and databases.

b) Encompass the full scope of the project effort, inclu ng CI/CSCI content fr

GFP/GFI vendors, as coordinated with the Gove ment.

c) Provide metadata for each CI/CSCI including

• Unique Identifier

• Type

• Description / Implementation

• Test Strategy

• Mission / Safety Criticality

• Repository Location

• Owner / Responsible T m

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 t, sponsor, and change control number of items to be reviewed.

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

c) Data packages for each proposed change, containing:

• Precise format and content for board review

• All relevant background material.

• Complete technical supporting analyse

• Details on replanning or rescoping i pplicable.

The CCB documentation shall be made available to relev stakeho rs 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 bas ) or Class II

(changes within the scope of the baseline).

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

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

Class I CCRs shall:

a) Be submitted for Government review.

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

The CCR process shall be integrated wit oject’s Agile frame k.

The CCR log shall:

a) Identify each CCR as either Cl I or Clas .

b) Track the status and disposition all CC s.

c) Be accessible t levant stakehol rs rough the project’s collaboration platform.

d) Include fiel for c ge descripti impact assessment, approval status, and implem ations stat

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 Ma geme Procedural

Requirements.

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

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

e) Describe integration with other project ma ement, system ngineering, and agile activities.

f) Explain the relationship between the contract Risk anagement Board (RMB) and associated SWO RMB(s) and how risk infor n continuously flows throughout the contractor’s organization.

The SWO-MOS RMP shall specify:

a) The format and data elements or the pr Risk List [RM ] (and/or Risk

Database).

b) Configuration control applicatio and list age/upd rocedures.

c) How team members can access th cur nt list at any time.

The SWO-MOS RMP ll des e:

a) Key in faces betwe the risk man ment process and other business reporting sys ms.

b) M cs for risk m g t effectiveness.

The SWO-MOS R shall clude:

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

) alphabeti 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 a ption 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 Manag ent P [RM-01].

b) Include a description of each risk, including causes, contr utors, and m gation actions.

c) Provide a risk projection or waterfall chart showing ticipated future chang n risk level.

The Risk List shall include for each risk:

a) Primary consequences if the undesired ev ccurs.

b) Estimate of the probability of occurrence and certain

c) Effectiveness of implemented risk mitigation m

d) Additional tracking information (originator, classif ion, owner, timeframe).

The Risk List shall provide:

a) Potential additional risk mitig ion me

b) Cost comparison of risk mitig n versus o e probability.

The Risk List shall:

a) Characterize "acceptable" osed, with rationale and Government concurren .

b) Allow e Governme o inject thei wn risks into the list.

The Risk List s l:

a) Supp metrics rack number of identified risks, mitigation status, and se y nges.

b) Be prepar or the monthly RMB.

lude an up e of risks, as well as risk handling plans and status for all higher-le isks.

d) Be a sible via t ontractor's Risk Management Tool, which may substitute for monthly ocument 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 desired outcome with respect to meeting the security requirements. The plan applies to a ask orders.

The scope and responsibility of the plan includes:

a) For systems within NOAA5050, the Contractor shall provid ecess inputs and updates to support the Government’s maintenance of exis g security documentation and support A&A (Assessment &Authorization) activities

b) All compliance documentation associated with NIS ecurity standards.

The IT System Security and Contingency Document shall in de:

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 cument sh mply with the following NIST

Special Publications:

a) NIST SP 800-18: Guide for Dev pin ecurity Plans for Information Technology

Systems.

b) NIST SP 0-30: Ri Managemen uide for Information Technology Systems

c) NIST 800-34: Co ngency Plann g Guide for Information Technology Systems

d) NIS SP 800-37: Ri Management F mework for Information Systems and

O izations: A S e Life Cycle Approach for Security and Privacy

[Ass ment & thorizatio )]

e) NIST S 00 3: Security and Privacy Controls for Information Systems and

Organizati

f) ST SP 800 A: Guide for Assessing the Security Controls in Federal

Inf ation Sys s

The IT System Sec y and Con ngency Document shall adhere to applicable NOAA and DOC

IT Security Requirem ts, including:

a) NOAA P acy Impact Assessment Template

b) NESDIS A&A Project Plan Template

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

M gement Act and Updated guidance on Quarterly IT Security Reporting.

For system nd 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 b ndary.

• Provided information for security management and cont

c) Contains the full set of A&A documentation, completed an eady fo view no later than 3 months before yearly A&A documentation de dlines are de red to the

Government less than 12 months before GRD.

d) Reflect all changes identified and required by the i pendent Security Testin &

Evaluation activity in the pre-ATO final version

The IT System Security and Contingency Document sha e:

a) Updated once for each yearly A&A proces

b) Updated when a major change is made that affec urity.

c) Reviewed and updated at least every three years aft e 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 acti es events, reviews, and alignment with the Agile framework and its ceremonies.

The SWO-MOS SEMP shall comply with the format and content specified b PR 7123.1

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

The SWO-MOS SEMP shall outline the contractor’s approach for conducting SE ac ies to support the full scope of the Contractor project, including interacti ns with GFP/GFI ve rs, external interfaces, subcontractors, and the Government.

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

a) Requirements management (identification location, tools d full traceability across all levels)

b) Verification and Validation (V&V)

c) Technical risk management (role in risk processe iability analysis)

d) Configuration management of SE work products

e) Baselining and change cont

The SWO-MOS SEMP shall discuss integ tion of ional SE with a engineering practices including:

a) Maintaining requirements tracea ity ac s agile arti cts (epics, features, user stories)

b) Continuou xplor n (CE), Con uous Integration (CI), Continuous Delivery

(CD), a automated d regression sting frameworks

c) Tech al debt mana ment

The SWO-MO EMP shall ou ne the model(s), t ols, and data management approach for SE activities.

The SWO-MOS SEM ll define the communications plan, including recurring meetings, worki ps, reportin nd information sharing mechanisms.

e SWO-MO EMP shal cument SE organizational structure, roles, responsibilities, and required skillsets.

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

SWO-MOS SEM shall include metrics for systems engineering effectiveness, such as req ments trace ity, verification and validation competition rates, and technical perform ce me res.

The SWO S 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 Co Description.

b) Address the full scope of the Solution, including GFP/GFI v dors, ernal interfaces, subcontractors, and the Government.

c) Describe the relationship to existing systems or procedures.

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

The SWO-MOS Operations Concept shall address the m i-program con pt of:

a) Unified Configuration Management

b) Anomaly Reporting & Tracking System

c) Continuous integration and continuous delivery p ces.

The SWO-MOS Operations Concept shall include metrics to mea operational readiness and performance, such as system availability me e between failure 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 cification and

MIL-STD-961 Defense and Program-Unique Specifications rma d Content.

b) Address the total Solution scope, incorporating requirem specifica s provided by GFP vendors as directed by the Government.

c) Include clear and direct traceability to contract and task order requiremen

d) Define the boundaries of the Solution, including marcation points between th

Solution and external interfaces.

The SWO-MOS Requirements Document shall describ

a) The overall approach for identifying, analyzi and de oping requirements.

b) Any prototyping techniques used in requiremen opment.

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

The SWO-MOS Requirements Docume l define:

a) Software and hardware requi ments t re compliance h contractual and

Government Level 3 requirem ts.

b) Appropriate allocated and deriv require nts fro SWO Solution F&PS, IRDs, MAR, and SOW.

The SWO-MOS Requi ents ument shall

a) Alloca specification erformance l ls.

b) Ide y all installati specific and fa ity requirements.

c) D t and control l er level Solution Design Specification and Element-level spec ations.

The SWO-MOS Req nts Document shall maintain bi-directional traceability between requi rtifacts.

e SWO-MO equiremen Document shall include metrics for management, such as requirements stab traceabil coverage, and volatility.

The SWO-MOS Req ements Document shall describe the process for continuous prioritization and refinement of req ements throughout the project lifecycle, aligned with the agile velopment approac The SWO-MOS Requirements Document shall reference SE-04 for ex al interface re rements.

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 R ements

Specification and MIL-STD-961 Defense and Program-Uni Spe ations

Format and Content (contractor equivalent format is acce ble).

b) Define the requirements for external interfaces.

c) Include appropriate allocated and derived requirem s from the MOSRD, IR

MAR, and SOW.

d) Describe the common messaging formats acr all interfaces.

The SWO-MOS External Interface Requirements Spe ation shall in de a Data Transfer

Workload Table that specifies, for each defined data tran r:

a) Data type

b) Source and destination

c) Delivery frequency and laten

d) File Size

The SWO-MOS External Interface Requir ents Spec n shall be d livered in an archived database that:

a) Includes modules of the specific ns d associated link modules.

b) Incorporate of the higher lower-level specifications to which the specifica n traces d ctly.

c) Uses t Governmen ovided mod s for traceability to documents provided by the vernment in d base module f at.

The Contractor ll:

a) Replac v ment database modules with new modules as received from the

Governme ollowing CCR approvals.

) date link t ability 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 t k orders.

The SWO-MOS Element and Infrastructure Requirements Specification shall

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

b) Define the boundaries of the Solution elements and infrastructure including de cation points between the element/infrastructure and external in faces.

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

d) Address the total Solution scope.

e) Address the element and infrastructure scope in orating req ements specifications provided by GFP vendors.

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

The SWO-MOS Element and Infrastruct e R ments Document ll maintain bi-directional traceability between requireme artifact

The SWO-MOS Element and Infrastructure equireme Do t shall include metrics for management, such as requirements stability, ceabil , coverage, and volatility.

The SWO-MOS Element structure Re ements Document shall describe the process for continuous prioriti tion and nement of r irements throughout the project lifecycle, aligned with the ag developmen pproach.

The SWO-MO Element and In structure Requir ents Specification shall be captured in SE-

06 Internal Inter e Requirem i n

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 Req ents

Specification and MIL-STD-961 Defense and Program-Uni Spe ations

Format and Content (contractor equivalent format is acce ble).

b) Define the requirements for the Element and Infrastructure external interf s to other Elements and Infrastructure, including the int aces to GFP end-items

c) Describe the common messaging formats across interfaces.

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

Workload Table that specifies, for each defined data t fer:

a) Data type

b) Source and destination

c) Delivery frequency and latency

d) File Size

For external interfaces that are the same f an E t and Infrastruc as for an External

Interface, the requirements shall be captur in the high der Specification and cited in the lower one.

The SWO-MOS Internal Interface Requireme Sp fication shall:

a) Be deliver sing contractor’s oposed requirements management toolset and format

b) Inclu each requirem nt specificatio its attributed, and rationale.

c) P de complete tr eability across al vels, with requirements traceability flo g from high fi ations down to lower-level specifications.

The SWO-MOS Int l I rface Requirements Specification shall align with and support the project's overall enterp management strategy, ensuring consistency and interoperability ac nt system d interfaces.

5.26 SWO-MOS Design Descriptions [SE-07]

Describes the architecture and design and establishes the top-level design and interface description(s). The design description applies to all task orders.

The SWO-MOS Design Descriptions shall:

a) Contain the content specified in DI-IPSC-81432 System/Subsyste Design

Description (contractor-equivalent format is acceptable).

b) Incorporate design descriptions provided by the GFP vendo or re nt subsystems, as directed by the Government.

c) Consist of separate descriptions as appropriate.

The SWO-MOS Design Descriptions shall include:

a) Engineering requirements down to the Elemen vel.

b) Operational parameters and requirements

c) Safety and assurance requirements

d) Software requirements to the Element level

The SWO-MOS Design Descriptions shall use unique identifi ligned with the contractor’s requirements management approach.

The SWO-MOS Design Descriptions sh pr a clear and comp nsive overview of the system architecture, including:

a) High-level system components d their int ac

b) Key design decisions and their r onale

c) Architectural p rns and styles pl ed.

The SWO-MOS Desi Descrip s shall addr how the design supports:

a) Scala ity and flexib y for future e ancements

b) In ration with exi ng systems and i astructure

c) Co liance with d rds and regulations.

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

Describes Interface architectures and designs. The ICDs apply to all task orders.

SWO-MOS Interface Control Documents shall:

a) Contain the content specified in DI-IPSC-81436 Interface Design D iption

(contractor-equivalent format is acceptable).

b) Include any additional information necessary to meet the uniqu racteristics of each external interface, as negotiated with external organiza ns.

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

Each describes the Internal Interface architecture and design for a defined interface between elements, infrastructure, and the Government-furnished end-items.