20250227 SWO-MOS QASP.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-PLAN-0006, Revision -

Space Weather Ground Services, Code 4 .0

Space Weather Observati ns

Mission Operation Ser ices

(SWO-MOS)

Quality Assurance Surveillance Plan (QASP)

SWO viewed – Not ject to Export Control

GSFC SWGS CMO

02/27/2025

Released

DRAFT

SWO-MOS QASP SWGS-MOS-PLAN-0006, Revision -ii

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)

Quality Assurance Surveillance Plan (QASP)

Signature/Approval Page

Prepared by:

David Nguyen

Reviewed by:

Ava Afghahi

Susan Jacobs

Scott Schnee

Laura Dunlap

Maria Amaro

David Donovan

Brian Frey

Andrew Royale

Katherine Spotz

Ken Jensen

Approved by:

Jill Taylor iii

Preface

This document provides the Quality Assurance Surveillance Plan for the Indefinite Delivery /

Indefinite Quantity (IDIQ) Space Weather Observations Mission Operations Service (SWO-

MOS) contract. It is under SWGS configuration control. Once this document is ap ved, changes are handled in accordance with Class I and Class II change control req ements as described in the SWGS Configuration Management Procedures, and change his document will be made by complete revision.

Any questions should be addressed to:

SWGS Configuration Management Office

NASA/GSFC

Code 492.0

Greenbelt, MD 20771 iv

Change History Log

Revision Effective

Date

Description of Changes

(Reference the CCR & CCB/ERB Approv Date)

Revision - 02/26/2025 Baseline Release following the approval of S GS-CCR-0011 v

Table of Contents

1 INTRODUCTION

1.1 Vision

1.2 Mission

1.3 Purpose

1.4 Authority

2 RELATED DOCUMENTATION

3 ROLES AND RESPONSIBILITIES

3.1 Government Representatives

3.2 Contractor Representatives

4 PERFORMANCE REQUIREMENTS AND METHO OF SURVEILLANCE

4.1 Contract Surveillance

4.2 Surveillance Methodologies

4.2.1 Participation in and Inspection of Contractor-L Agil ctivities

4.2.2 Inspection of Contract Data Requirements List (C ) deliverables

4.2.3 Periodic Informal Reviews

4.2.4 Formal Reviews

4.2.5 Direct Observations

4.2.6 Validated User/Customer Com aints

4.3 Surveillance Matrix

5 PERFORMANCE REPORTING

5.1 Regular Performa rting

5.2 Notification of naccepta Quality

5.3 Record Kee ng

5.4 Issues an Resolution

6 INCENTIV AND REM

6.1 Incentives:

6.2 Remedies:

AP SWO-M SURVEILLANCE MATRIX

1 INTRODUCTION

1.1 Vision

The vision for the SWO-MOS Solution is to develop a scalable, multi-mission missi operations system capable of supporting the National Oceanic and Atmospheric ministration

(NOAA) space weather observation programs, ensuring the continuity and ext ion of critical space weather data collection from various orbital locations. The SWO-MO em will provide health and status monitoring and trending, command and control rbit an ttitude management, mission planning, contingency operations, and anomaly covery capa ities for spacecraft and instruments. The system will evolve from its initial implementation foc d on the Space Weather Follow-On Lagrange 1 (SWFO-L1) mission o a unified, multi-miss architecture that can support multiple space weather observa es, instruments, and partners across different orbits.

1.2 Mission

The mission of the SWO-MOS Solution includes the followin

1. Scalability and Multi-Mission Support

The SWO-MOS Solution will sca m a single-mission s m to a robust, multi-mission platform capable of simu neo upporting multip pace weather observatories. It will integrate futu missions s those at La ange points, geosynchronous orbit (GEO), and a riety of ho ads or observatories in other orbits.

2. Interoperability and Common Opera n atterns Across Missions

The Solution wil a ly interopera system that integrates seamlessly with

NOAA’s exi g operatio practices, l raging common infrastructure and interfaces for teleme tracking, command, and mis n support services. Support for different observa ies and instrum ts will use fami operator and support interfaces and use instance f the same o It will also interface with partner agencies and commercia rvice viders to expa ground station and data processing capabilities.

3. Efficiency st-Effectiveness

Solution wil lance efficiency and cost-effectiveness including long-term sustai nt and ma nance costs without compromising on mission-critical services by optimizin e use of c mon services and reusable components and leveraging NOAA enterprise in structure.

4. Agile and remental Development

The Solution l be developed incrementally using Agile methodologies to ensure flexibility and pid response to changing mission needs. Program Increments (PIs) will continuously eliver functional, tested capabilities aligned with the evolving space eather m ion portfolio.

5 h ed Security and Resilience

The lution will prioritize security, adhering to NOAA, federal, and NIST information security standards. It will be designed with a resilient architecture capable of maintaining operations even in the face of anomalies or cyber threats.

6. Future-Proofing and Innovation

The Solution is intended to evolve alongside advances in NOAA enterprise capabilities and mandates.

1.3 Purpose

This SWO-MOS Quality Assurance Surveillance Plan is a government-develop document used to determine if the Contractor’s performance meets the performance sta ds contained in the contract. The QASP establishes procedures on how this assessment/in c process will be conducted. It provides the detailed process for continuous oversight

● What will be monitored

● How monitoring will take place

● Who will conduct the monitoring

● How monitoring efforts and results will be d umented

The Contractor is responsible for implementing and d ring perform e that meets contract standards using its Mission Assurance Implementation Pl The Q provides the structure for the Government’s surveillance of the Contractor’s perfo n nd their Quality

Assurance/Quality Control (QA/QC) actions to assure they me ontract standards and requirements. It is the Government’s resp nsibility to be objectiv fair and consistent in evaluating Contractor performance.

This QASP is a living document. Flexibili in the QAS uired to allow for an increase or decrease in the level of surveillance necessa based on ontra formance.

The Government will pro py of the QA o the Contractor to facilitate open communication. In ad ion, the SP recogni that unforeseen or uncontrollable circumstances migh ccur that ar utside the co ol of the Contractor. The QASP ensures early identificati and resolution f performance ues to minimize impact on mission performance.

1.4 Authority

Authority for issuance his QASP is provided under Part 46 of the Federal Acquisition

Re pection of vices clauses, which provides for inspection, acceptance and cumentation he servic lled for in the contract or order. This acceptance is to be executed by the C racting Of r or a duly authorized representative.

2 RELATED DOCUMENTATION

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 this QASP with their sources. In the event of any unresolv conflict, the Contractor must request conflict resolution by the Contracting Officer in adv e of work performed.

The SWO Program Acronym and Glossary List, SWO-MGMT-LIST-0 1, define rminology as used in this document and throughout the SWOPD. In the event of conflict betwee terminology in this document and any other dictionary, the SWO minology will take precedence. In the event of any unresolved conflict, the Contr r must request conflict resolution by the Contracting Officer.

3 ROLES AND RESPONSIBILITIES

3.1 Government Representatives

The following personnel will oversee and coordinate Government surveillance activi ies.

SWO-MOS Program Manager (PM) – The SWO-MOS PM provides primary ogram oversight, nominates the Contracting Officer’s Representative (COR), ensur e COR is trained before performing any COR duties and supports the COR’s perfor nce essment activities. While the PM may serve as a direct conduit to provide Gov ment gui ce and feedback to the Contractor on technical matters, they are not empowered to make any tractual commitments or any contract changes on the Government’s behal

Assigned PM: Mr. Ousseini Lankoande

Organization or Agency: NOAA NESDIS SWO

Email: ousseini.lankoande@noaa.gov

Contracting Officer (CO) – The CO will ensure performan f necessary actions for effective contracting, ensure compliance with the contract term nd safeguard the interests of the United States in the contractual relatio hip. The CO will also sure that the Contractor receives impartial, fair, and equitable tre me der this contract.

Assigned CO: Ms. Maryann Orellana

Organization or Agency: NOAA Acquisitio nd Gra Office

Telephone: 301-327-0344

Email: maryann.orellana v

Contracting Offic s Represen ve (COR) – e COR is responsible for providing continuous techn al oversight of e Contractor’s rformance. The COR uses the QASP to conduct the o ght/surveillan process The COR will keep a Quality Assurance file that accurately docum s the Co ctor s f rmance. The purpose is to ensure that the

Contractor meets th rf ance standards contained in the contract. The COR is responsible for reporting early iden ation of performance problems to the CO. The COR is required to pr al Contra erformance Assessment Reporting System (CPARS) to the CO ich will be u in docum ing past performance. The QASP is the primary tool for surveillance of th ntractor s ality program and helps the COR to document Contractor performance. The C is not empowered to make any contractual commitments or to authorize any contractual chang on the Government’s behalf.

A gned COR: Mr stave Comeyne

Org ation or A cy: NOAA NESDIS SWO

Email: s com ne@noaa.gov

3.2 Contractor Representatives

The following employees of the Contractor serve as the Contractor’s leadership team for this contract. (Complete this section after the contract award)

Contractor Project Manager – TBD

Contractor Deputy Project Manager – TBD

Contractor Chief Systems Engineer – TBD

4 PERFORMANCE REQUIREMENTS AND METHODS OF

SURVEILLANCE

4.1 Contract Surveillance

The goal of the QASP is to ensure that Contractor performance is effectively mo ored and documented. The COR’s role is to establish a professional, non-adversarial r ionships with the CO, PM and the Contractor, which enables positive, open and timely c ications.

These relationships are built upon objective, fair, and consistent COR e uations Contractor performance against contract requirements. The COR uses the method contained in s QASP to ensure the Contractor is in compliance with contract requireme s The COR functio responsible for a wide range of surveillance requirements that ctively measure and eva te the Contractor’s performance. Additionally, this QASP is b d on the premise that the

Contractor, not the Government, is responsible for manag ent and QA/QC actions to successfully meet the terms of the contract. The Gove ent performs eillance, using this

QASP, to determine the quality of the Contractor’s perf ance as it ates to the performance element standards.

4.2 Surveillance Methodologies

The primary methods of surveillance incl de, bu not limited to, th llowing.

4.2.1 Participation in and Inspection of C tractor-Led Activities

The Contractor will develop a Solution to th overnm nt’s missio requirements according to the timeliness requirements f project lifecycl mil ones as directed in task orders. The

Government will partici in le events ass ated with the development of the Solution.

The Government and ontractor use these e ts to communicate surveillance findings and any concerns. Exa ples include b are not limite o the following: During PI planning meetings, the G ernment will a ss objective and bjective Agile metrics to evaluate the alignment of pr sed capabil d stories with the Mission Operations Services

Requirements Doc ent (M SRD) and asse he feasibility of planned work against task order milestones as well as e team dynamics. During PI demonstrations and Inspect and Adapt sessi Governmen ill verify the completion of planned work for the increment and a ss the qu and func ality of delivered capabilities. The Government will also inspect nd evaluate oth gile PI an rint artifacts as necessary to assess Contractor performance.

4.2.2 Inspection o ontract Data Requirements List (CDRL) deliverables

CDRL deliverables a defined in the SWO-MOS CDRL (SWGS-MS-CDRL-0001). All CDRL iverables will be r ewed upon receipt. The Government will report any comments and ca rize the comm nts as Critical, Substantive, or Minor/Editorial.

4.2.3 riodic ormal Reviews

The Gover nt and Contractor will conduct periodic reviews such as status reviews, bi-weekly management coordination meetings, and other ad hoc meetings as needed. The Government will use these reviews to keep informed of the Contractor’s progress and planned activities. This allows for immediate feedback on any concerns and issues, and also establishes expectations against which the Contractor’s actual progress/activities can be measured. The Government and

Contractor can use these reviews to communicate surveillance findings and any concerns.

4.2.4 Formal Reviews

The Government will conduct formal reviews of Contractor plans, processes, desig and readiness to meet key project milestones (e.g., design, factory and site testing, c truction, operational readiness, and system acceptance). The Government and Contra will use these reviews to communicate surveillance findings and any concerns.

4.2.5 Direct Observations

Observation and experience of delivered systems and servic unction and performance may used to assess performance.

4.2.6 Validated User/Customer Complaints

Feedback from users of the systems and services may be us to a s performance.

4.3 Surveillance Matrix

The Surveillance Matrix (see Appendix A s the li erformance obj ives and standards that must be performed by the Contractor. is matrix d he method of surveillance and frequency the COR will use to validate and pect the perfor elements. Inspection of each element will be documented in the COR e. T matrix documents the standards that will be used to evaluate perfo nd Acceptab ality Levels (AQLs), as appropriate.

Performance ctives define th desired outcome Performance Standards define the level of service required der the con lly meet the performance objective. The inspection methodo y d es how, when, and what will be assessed in measuring performance. The Go ment performs surveillance, using this QASP, to determine the quality of th tor’s perfo nce as it relates to the performance element standards. The veillance M x will be d to form the foundation of the COR’s assessment.

5 PERFORMANCE REPORTING

5.1 Regular Performance Reporting

The COR and CO (or designee) will conduct ongoing and continuous surveillance o WO-MOS performance via regularly scheduled tag-ups and project management status revi . This level of surveillance will enable the Government to demonstrate whether the Contra r is meeting the stated objectives and/or performance standards, including cost/technical/sch objectives.

5.2 Notification of Unacceptable Quality

The COR will notify the CO, in writing, of unacceptable quality levels. The CO will p ide written notification to the Contractor of discrepancies on a quart y basis, or immediately the situation significantly affects the well-being of the project.

The Contractor will provide a written response to the cau and the corrective action to prevent recurrence within 10 working days after receipt of CO otification. Th Contractor should cite specific quality assurance program procedures or new pr dures ins ted to prevent recurrence.

If the Contractor has not met the minimum performance require nts, it may be asked to develop a formal Corrective Action Plan AP) demonstrating ho d by what date it intends to bring performance up to the required l els

5.3 Record Keeping

The COR will maintain contract surveillance les as di cted by O. Surveillance files will include, in part, the following documentation thi ontract and all Task Orders:

a. COR designatio nd app ntment letter

b. All correspo nce includ CO notific ns and the Contractor’s responses

c. Notificati of unaccepta quality and c ective action responses

d. Eviden of cost monitor g: invoices certif and tracked against any contract and/or order cei s

e. Project Man men tatus Review (PMSR) data packages

5.4 Issues and Reso on

e COR mus rdinate an ommunicate with the Contractor to resolve performance issues or concerns. The COR an ntractor should jointly formulate and document long-term courses of action. D sions regarding changes to metrics, thresholds, or service levels should be clearly documented a must be approved by the CO and incorporated into the contract via a odification.

If th Contractor di utes a surveillance determination or has concerns over the Government’s perform ce ma gement of the contract in general, they must first attempt to resolve through the progr ce. If, in the Contractor’s opinion, resolution is not possible or there is clearly an impasse at is adversely affecting the contractual relationship and/or performance, they must report their concerns to the CO in a timely fashion. The CO will be responsible for determining or negotiating the resolution approach and timeframe.

6 INCENTIVES AND REMEDIES

6.1 Incentives:

Incentives to the Contractor may be applied for meeting or exceeding AQLs. These entives include:

- Documentation of Contractor performance into CPARS

- Consideration of an option period for applicable task orders, if fund vailable and the need exists

6.2 Remedies:

In the event that the Contractor fails to meet the outlined AQLs delivery standards, suc missing key milestones, failure to deliver planned features, o n-compliance with configuration and security management processes, remedi may be applied. These remedies include:

- Corrective action plan to remedy a deficiency

- Documentation of issues into the CPARS

- Decrement/Reduction of payment/invoice due

SWO-MOS QASP SWGS-MOS-PLAN-0006, Revision -

APPENDIX A: SWO-MOS SURVEILLANCE MATRIX

Statements Standards/AQLs Methods

A. TECHNICAL AND SCHEDULE PERFORMANCE

A.1: Develop the Solution to meet task order requirements.

95% of PI epics completed as pla ed

98% of allocated release requi ments verified prior to delivery of capability

100% of interface requir ents verified b eed date ess at Agile events, mo ly reviews, and design, integr tion, test, and acceptance reviews

A.2: Support project lifecycle reviews for the SWO-MOS.

95% Solution compliance h lifecycl aturity standards including supportin ate s and CDRLs in accordance with:

NASA Procedural Requirements (N ) 7123.1: NASA

Systems E i ing Processes and R irements

GSFC-STD 001A ria for Flight an Flight

Support Rev ws

Assess upon package delivery to project lifecycle reviews

A.3 Deliver a working Solution that meets mission needs.

95% success i meeting s keho tisfaction with

Solution Capab y an eatures

99% system a i ility for delivered system in op ion

Assess at Site Acceptance

Reviews

Review of Stakeholder

Feedback

Review of System Monitoring artifacts

A.4: Achieve planned schedule estones for key events defined in task orde

10 % of site deliverie successfully complete gr d Checkout (ITCO) by deadlines

95% of planned features delivered per PI

Assess during periodic and ongoing schedule coordination activities.

Review of site ITCO artifacts and results.

A.5: Deliver CD s and Delive le items 8% on-time delivery of CDRL data items

1 % on-time delivery of Deliverable Items list

100% approval of CDRLs by the Government

Review of deliverables in accordance with criteria.

SWO-MOS QASP SWGS-MOS-PLAN-0006, Revision -

Statements Standards/AQLs Methods

B. BUSINESS MANAGEMENT

B.1 Complete contract administration including timely and accurate submission of report, invoices, and proposals; adherence to contract requirements; and cooperation with the Government in negotiating changes to the contract.

100% compliance with contract reporting requirement Assess during periodic and ngoing coordination activities.

B.2 Subcontract management, including subcontract cost and performance reporting and integration of major subcontractors into timely and accurate technical, management, and cost reporting.

Compliance with Contrac Governm t-approved

Project Management Plan (C L PM 01)

Assess during periodic and ongoing coordination activities.

B.3 Provision of appropriate level and skill mix of staff to execute the requirements of the contract, including timely addition of staff to maintain key project milestones and meet overall project objectives.

Complianc with C tor’s Governm approved

Project Man ment Plan RL PM-01)

B.4 Execution of risk management processes, including timely identifica n, prioritization, development of miti ion approach, and reporting.

C liance with ntractor’s Government approved

Risk Management n (RM-01)

Assess during periodic and ongoing coordination activities.

B.5. Management of Government ned and Contractor-acquired property.

% ith contract, Agency, and Federal reporting and property management requirements.

Assess during periodic and ongoing coordination activities.

B.6 Compliance with Government secur requirements. This i sical and

Information Tech logy security

Zero security breaches.

100% compliance with security audits, 00% compliance with contract, Agency, and Federal r irements.

Assess during periodic and ongoing coordination activities.

B.7 Provisi of a safe work environm t and complian with Government safe requirements.

100% compliance with contract, Agency, and Federal requirements.

Statements Standards/AQLs Methods DRAFT

SWO-MOS QASP SWGS-MOS-PLAN-0006, Revision -

C. COST MANAGEMENT

C.1 Successful management and control of costs and financial resources, based on current, cumulative, and estimated-to-complete (ETC) costs, when compared to the contract value.

At Government WBS Level: CUM to dat

Cost/Schedule variance thresholds of +/ % or +/-

$50,000, whichever is lower; Total E timated Cost variance thresholds of +/- 5% or $ ,000, whichever is lower.

Request for approval of i eriod baseline ange requests within 24 hours o ontractor roval.

Notification of out-of-period ba e change requests within 5 working days.

Review of Monthly financial reports.

ess during periodic and ong g coordination activities.