GXI Instrument Draft SOW.pdf

GeoXO Imager (GXI) Statement of Work (SOW) RFI Draft April 12, 2022

Contents Tables

1 Program Scope and Management

1.1 Period of Contract Coverage

1.2 Documents

1.2.1 Applicable Documents

1.2.2 Reference Documents

1.3 Project Management

1.3.1 Key Personnel

1.3.2 Action Item Tracking

1.3.3 Document Retention

1.3.4 Weekly Status Reporting

1.3.5 Government Insight

1.3.6 Contractor Access to Government-Controlled and Spacecraft-Controlled Facilities and Data

1.3.7 Subcontract Management

1.3.8 Deliverable Documentation

1.4 Resource Management

1.4.1 Work Breakdown Structure (WBS)

1.4.2 Earned Value Management System (EVMS)

1.4.3 Performance Measurement Baseline (PMB)

1.4.4 Integrated Master Schedule (IMS)

1.5 Risk Management

1.6 Configuration and Information Management

1.6.1 Participation in Government and Spacecraft CCBs

1.6.2 Knowledge Capture / Lessons Learned

1.7 Special Task Activities

1.8 Reviews and Meetings

1.8.1 Kick-off Meeting

1.8.2 Requirements Walkthrough

1.8.3 Project Management Status Reviews

1.8.4 Integrated Baseline Review (IBR)

1.8.5 Contractor-Led Meetings and Reviews

1.8.6 Government Chaired Instrument Reviews

1.8.7 Observatory-level Reviews

1.8.8 Program-level Reviews

1.8.9 Operations Reviews - Each Flight Model

1.8.10 Participation in Observatory Level Working Groups

2 Systems Engineering

2.1 Systems Management and Engineering

2.2 Use of DOORS Tool

2.3 Spacecraft Interface and Accommodation

2.4 System Analysis and Allocations

2.5 Contamination Control and Analysis

2.6 Trending

3 Mission Assurance

4 Design and Analysis

4.1 Instrument Design

4.2 Software

4.2.1 Management and Maintenance

4.2.2 Flight Software Development Environment (FSDE)

4.2.3 Flight Software Design

4.2.4 Ground Test Software Development

4.2.5 Ground Processing Algorithms (GPA)

4.3 Electrical Design

4.3.1 Field Programmable Gate Array (FPGA) Design and Development

4.3.2 Electromagnetic Compatibility (EMC) and Electromagnetic Interference (EMI)

4.3.3 Electrostatic Discharge (ESD)

4.3.4 Radiation

4.3.5 Mechanisms

4.4 Structural Design

4.5 Thermal Design

4.6 Optical Design

4.7 Structural, Thermal, and Optical Performance (STOP) Model

4.8 Image Navigation and Registration (INR)

4.9 Fabrication & Test Requirements

5 Parts and Spares Procurement

5.1 Spares

5.1.1 Testing of Spare Hardware

5.1.2 "One-shot" items

6 Engineering Development Program

6.1 Engineeing Development Activities

6.2 EDM Functional and Performance Testing

7 Flight Model-1 (FM-1)

7.1 Integration and Test

7.1.1 Integration

7.1.2 Performance Verification and Design Qualification

7.1.3 Functional and Performance Testing

7.1.4 Structural and Mechanical Testing

7.1.5 Electromagnetic Compatibility Testing

7.1.6 Thermal Testing

7.1.7 Calibration

7.2 Logistics

7.2.1 Transportation and Handling

7.2.2 Storage

7.3 Post-shipment Support

7.3.1 Contractor On-Site Team at Spacecraft Facility

7.3.2 Instrument and GSE Checkout

7.3.3 Observatory-level Instrument Integration and Test Support

8 Operations Support

8.1 Launch Operations Support

8.2 Mission Operations Support

8.2.1 Pre-Launch Support

8.2.2 End-to-End Test Support

8.2.3 Post-Launch Test (PLT) Support

8.2.4 On-orbit Anomaly Support

9 Ground Support Equipment (GSE)

9.1 Electrical Ground Support Equipment (EGSE)

9.1.1 Electrical System Test Equipment (ESTE)

9.1.2 Connectors and Connector Savers

9.1.3 Other Electrical Ground Support Equipment (EGSE)

9.2 Mechanical and Optical Ground Support Equipment

9.3 Ground Processing Demonstration System (GPDS)

9.4 Instrument Hardware Simulator (IHS)

9.5 Instrument Software Simulator (ISS)

10 Flight Model-2 (FM-2)

10.1 Deliverable Documentation

10.2 Spares

10.3 Integration and Test

10.4 Logistics

10.5 Post-Shipment Support

11 Flight Model-3 (FM-3)

11.1 Deliverable Documentation

11.2 Spares

11.3 Integration and Test

11.4 Logistics

11.5 Post-Shipment Support

12 Flight Model-4 (FM-4)

12.1 Deliverable Documentation

12.2 Spares

12.3 Integration and Test

12.4 Logistics

12.5 Post-Shipment Support

13 Flight Model-5 (FM-5)

13.1 Deliverable Documentation

13.2 Materials & Parts Procurement

13.3 Spares

13.4 Integration and Test

13.5 Logistics

13.6 Post-Shipment Support

14 Acronyms

Tables Table 1. Applicable Documents

Table 2. Reference Documents

Instrument SOW

1 Program Scope and Management This Statement of Work (SOW) defines the minimum set of tasks and deliverables necessary to design, analyze, develop, fabricate, integrate, test, verify, evaluate, and support launch of the Geostationary Extended Observations Imager (GXI, hereupon called Instrument), to supply and maintain the instrument Ground Support Equipment (GSE), and to support the Mission Operations at the NOAA Satellite Operational Facility (NSOF) in accordance with the Contract, this SOW, and the Contractual documents listed in the Applicable Documents Section within cost and schedule commitments.

The Instrument has a risk classification of Class B, consistent with NPR 8705.4A. The Instrument Requirements and Statement of Work are consistent with this Risk Classification. The Instrument shall be a primary instrument as described in the Instrument Mission Assurance Requirements, henceforth referred to as the IMAR.

The Contractor shall provide the personnel, subject matter expertise, materials, equipment, facilities and all other necessary resources to accomplish the work specified in the Contract, this SOW, and the Contractual documents listed in the Applicable Documents to design, develop, deliver (if applicable) and support under the basic contract:

a) Agreed-to component and subsystem Engineering Development Unit (EDUs), Prototype Units, and an Instrument Engineering Development Model (EDM)

b) One Instrument Flight Model (PFM) designated Flight Model-1 (FM-1)

c) One Instrument Flight Model (PFM) designated Flight Model-2 (FM-2)

d) Parts and materials for two additional flight Instruments

e) Spare parts/components to enable the timely repair of the flight models

f) Three sets of the Electrical System Test Equipment (ESTE)

g) Four Instrument Hardware Simulators (IHS)

h) One Instrument Software Simulators (ISS)

i) Two Flight Software Development Environments (FSDEs)

j) One Ground Processing Demonstration System (GPDS)

k) All Instrument Mechanical, Electrical, and Optical Ground Support Equipment (MGSE, EGSE, and

OGSE, respectively)

In addition, there will be three options for additional models to be exercised at the Government’s discretion:

l) Option 1 for an additional Flight Model (FM-3)

m) Option 2 for an additional Flight Model (FM-4)

n) Option 3 for an additional Flight Model (FM-5), including all necessary parts and materials

The Contractor shall provide personnel, materials, equipment, and facilities necessary to store GXI instrument units and associated equipment in accordance with the requirements of this contract.

The Contractor shall submit deliverables per the GXI Contract Data Requirements List (CDRL) (418-XO- GXICDRL-0055), referred to as the CDRL from this point forward. Reference Section, “Deliverable Documentation” for a more detailed explanation of the deliverable documentation requirements.

The following sections, along with the Data Item Descriptions (DID) in the CDRL describe the specific work to be accomplished by the Contractor.

1.1 Period of Contract Coverage

The period of contract coverage is from contract award through the life of the mission, including successful launch, post-launch evaluation, mission operations, and on-orbit anomaly investigations until all the instruments reach end-of-life or end of defined mission, whichever comes first.

1.2 Documents

1.2.1 Applicable Documents

The documents listed in this section apply directly to the performance of the Instrument contract.

These documents establish detailed specifications, requirements, and interface information necessary for the performance of the contract.

The current revision numbers and dates will be maintained in an Attachment to the Contract. Attachment 1 to the GXI contract, Applicable and Reference Documentation, provides the current issue revision, issue date, approved CCR, and approving modification for all applicable documents listed below. That contract attachment shall be the governing document for the items listed below.

Table 1. Applicable Documents

No. Document No. Document Name 1 418-XO-GXICDRL-0055 GeoXO GXI Contract Data Requirements List (CDRL) 2 418-XO-IMAR-0026 GeoXO Instrument Mission Assurance Requirements (IMAR) 3 418-XO-GXIPORD-0024 GXI Performance and Operational Requirements Document

(PORD)

4 418-XO-GXIUIID-0023 GXI Unique Instrument Interface Document (UIID) 5 418-XO-GXIGIRD-0041 GeoXO General Interface Requirements Document (GIRD) 6 418-XO-SIM-00TBD Geostationary Extended Observations (GeoXO) Instrument

Simulator Requirements Specification 7 418-00TBD GeoXO GXI Simulator IRCD 8 GSFC-STD-1001A Criteria for Flight Program Critical Milestone Reviews 9 NPR 7150.2C NASA Software Engineering Requirements 10 GPR 8700.6C Engineering Peer Reviews 11 GPR7120.4D Risk Management

12 418-00TBD Geostationary Extended Observations (GeoXO) Flight Software (FSW) Table Schema

13 418-00TBD Geostationary Extended Observations (GeoXO) Application Packet Schema

14 418-00TBD Geostationary Extended Observations (GeoXO) Command & Telemetry Database (CTDB) Schema

15 TBD GRDDP

16 CCSDS 660.2-G-2 CCSDS XML Telemetric and Command Exchange (XTCE)

1.2.1.1 Precedence of Applicable Documents

In case of conflict between applicable documents, the precedence shall be as follows:

1. Contract

2. SOW

3. UIID

4. GIRD

5. PORD

6. ICD

7. IMAR

8. Other Applicable Documents

The Contractor shall notify the Contracting Officer of any inconsistency in the contract, including all attachments and Applicable Documents.

1.2.2 Reference Documents

The documents in Error! Reference source not found. are referenced herein and amplify or clarify the information presented in this document. These documents are not binding on the content of this document.

Table 2. Reference Documents

No. Document No. Document Name 1 NPD 2820.1C NASA Software Policy 2 500-PG-8700.2.7 Design of Space Flight Field Programmable Gate Arrays 3 NASA-GB-8719.13 NASA Software Safety Guidebook 4 NASA-STD-8739.8A NASA Software Assurance and Software Safety Standard 5 NPR 8705.4A Risk Classification for NASA Payloads 6 410-XO-PLN-0006 GeoXO Risk Management Plan - RMP

1.3 Project Management

The objective of the Contractor Project team shall be to develop and deliver all hardware, software, documentation, and data that meet performance and contract requirements within cost and schedule commitments. Effective Project Management techniques, including but not limited to team leadership, technical development approach management, cost and schedule planning, monitoring, and adjustment, risk management, potential future problem identification and resolution, and promotion of teamwork, including with the Government team, will be employed to achieve this objective. The Contractor shall establish a Project Management Office (PMO) responsible for the leadership and overall direction of all phases of the work specified in this SOW. The Contractor shall appoint a dedicated Project Manager to lead, direct and manage this project. The Contractor’s Project Manager shall have responsibility for the overall technical performance, resource management, and schedule management of the contractual effort and all subcontracts. The Contractor’s designated Project Manager shall report to a level of company management appropriate to ensure prompt resolution of all problems.

The Contractor shall develop and implement a Project Management Plan that describes the methodology and processes that will be employed to achieve the objectives of this contract and manage the Instrument Project from contract award through operational support of the last instrument delivered under this contract, in accordance with CDRL PM-01.

The Contractor shall establish effective communication with the Government Project Office through the Government Representative that includes, but is not limited to, e-mail and telephone contact as necessary, weekly telecons with the Government Instrument team, and one-on-one contact between National Aeronautics and Space Administration (NASA) and Contractor discipline engineers, to be coordinated by the Contracting Officer Representative (COR).

1.3.1 Key Personnel

The Contractor shall notify the Government of any changes of key personnel (Project Manager, Chief Engineer, etc.) at least 2 work weeks ahead of the change, if possible, and coordinate with the Government on a transition plan to capture and transfer knowledge and to minimize disruption.

1.3.2 Action Item Tracking

The Contractor shall develop and maintain a Master Action Item Database (MAID) - a spreadsheet listing all Request for Actions (RFAs) or Action Items from all reviews and technical meetings.

The Contractor shall preserve all historic actions in the MAID.

1.3.3 Document Retention

The Contractor shall retain all documents and test data for the life of the contract.

1.3.4 Weekly Status Reporting

In order to provide regular written communication of the status of the Project, the Contractor shall submit a Weekly Status Report to the Government in accordance with CDRL PM-02. This written report is not a substitute for any weekly meeting agreed upon with the Government.

1.3.5 Government Insight

The objective of the Government team is to enable the success of the Contractor team. This is to be accomplished through effective teamwork, efficient problem resolution, and by ensuring that the efforts under this contract are aligned with project objectives. This necessitates appropriate levels of insight by the Government team in to the Contractor team’s activities.

The Contractor shall open to Government attendance all Contractor and subcontractor internal data, reviews, audits, meetings and other activities within the scope of the contract. For access and insight activity, “Government” includes Government personnel and Government contractor personnel. The Contractor shall allow and enable the use of Non-Disclosure Agreements (NDA) with Government contractors where appropriate. The Contractor shall notify the Contracting Officer, the Government Resident Office and the Contracting Officer’s Representative (COR) of meetings, reviews or tests in sufficient time (nominally five working days unless otherwise specified) to permit meaningful Government participation.

1.3.5.1 Accomodation of Government Team

The Contractor shall accommodate five Government in-plant representatives. This accommodation shall include lockable offices, including furniture, printer(s), copier(s), phones, and high-speed internet access. At least one of the offices shall be private. The Contractor shall provide the in-plant representatives with badging that allows for unescorted and off-hours access to the facilities involved in instrument development. The badged Government in-plant representatives shall be allowed to escort other Government visitors.

The Contractor shall coordinate with the Government regarding badging (including level of access) for Government personnel other than the in-plant representatives.

The Contractor shall provide additional office space for up to ten people for use by Government representatives during reviews or other functions that will temporarily increase the number of on-site Government representatives.

The Contractor shall provide office space, furniture, copier(s), printer, phones, and high-speed internet access for up to ten visiting Government representatives during instrument integration and testing, in the vicinity of the activity. The Contractor shall provide badging that allows for unescorted and off-hours access to the facilities involved in instrument testing.

All accommodations shall be coordinated and agreed to with the Government.

1.3.6 Contractor Access to Government-Controlled and Spacecraft-Controlled Facilities and Data

In order to access Government-controlled facilities, such as the control center and launch site, and Spacecraft-controlled facilities, such as the Satellite Integration and Test facilities, the Contractor shall apply for all required authorizations and take any necessary training in a timely manner. The Contractor shall meet all requirements necessary to maintain access without interruption. Access may require the Contractor to obtain Non-Disclosure Agreements, participation in training, and travel to a Government or Spacecraft facility to physically get a badge.

In order to access Government-controlled computer systems, folders, or data such as the Portal, or Spacecraft-controlled computer systems, folders, or data, the Contractor shall apply for all required authorizations, take any necessary training, and meet any operating system and/or software requirements in a timely manner. The Contractor shall meet all requirements necessary to maintain access without interruption. Access may require the Contractor to obtain Non-Disclosure Agreements, participation in training, and/or installation of software on a Contractor computer. If the Contractors’ internal requirements are not compatible with the Government or Spacecraft Contractor’s requirements, the Contractor shall coordinate with the Government or Spacecraft Contractor to achieve a mutually acceptable arrangement.

1.3.7 Subcontract Management

The Contractor shall actively manage its subcontractors. This management shall include mission- and quality-assurance focused oversight and technical insight that verifies compliance with the requirements of the contract. The Contractor shall flow all applicable requirements and controls to its subcontractors.

It is important for the Government to have visibility into activities for “critical suppliers” (i.e., those subcontractors under a SOW agreement with the Contractor). As such, the Contractor shall routinely verify critical supplier adherence to both Contractor-flowed down and approved Subcontractor processes as called out in the GeoXO IMAR. The Contractor shall develop and maintain a matrix that shows the prime Contractor’s requirements and identifies those requirements which are flowed to each critical supplier. The matrix shall be made available for review upon request.

The Contractor shall maintain a schedule of meetings (both virtual and in-person) with its critical suppliers and any supplier presenting significant risk to the program to be presented at each PMR. This schedule shall include quality assurance surveillance audits and be available for review.

In cases of frequent or significant anomalies, the Contractor shall support Government requests for additional onsite personnel at critical facilities. The Contractor shall invite the Government to Contractor-attended major reviews and acceptance activities at critical suppliers. The Contractor shall notify the Government at least five working days prior to critical supplier tests and ten working days prior to major reviews to permit meaningful Government participation.

1.3.7.1 Incorporation of Critical Supplier Information

The Contractor shall present the following critical supplier information in the PMR:

a) Summary of progress and any problems or issues

b) Target delivery dates and assessment of risk for any critical supplier within 30 days of critical path

The Contractor shall make the following critical supplier information available to the Government on request:

a) Project Status Reviews and/or Reports

b) Problem Reports per the IMAR

c) Meeting or Review presentation materials

Test reports for all subcontracted items shall be provided in accordance with the CDRL SE 4-9.

Critical supplier open risks shall be reported at each major review.

Major actions from critical supplier meetings and reviews shall be captured and tracked in the MAID.

1.3.8 Deliverable Documentation

The Contractor shall prepare and submit deliverables in accordance with the CDRL/DID (418-XO- GXICDRL-0055) and the SOW. The Contractor shall be responsible for delivering all documents as called out in the CDRL whether or not they are referenced in the SOW.

The Government will establish and maintain a secure electronic document repository, called the GeoXO Portal for document delivery and the exchange of information only. An area within the portal will be maintained for the instrument, accessible only by the respective Contractor and selected Government personnel. The Contractor shall submit all deliverable items specified in the CDRL electronically to the GeoXO Portal using processes agreed upon with the Government. For all document submissions, the Contractor shall send an email to the Government Contracting Officer (CO), informing him or her of the document submission. The Contractor shall make revisions to submitted items per Government comments as specified in the CDRL and re-submit the items using processes agreed upon with the Government.

The Government will post in the Instrument section of the GeoXO Portal Government technical and contractual documentation generated in support of the GeoXO Instrument. The Government will notify the Contractor via email of such postings.

The Contractor shall deliver CDRL submissions that are complete, unabridged, and un-redacted. To the extent that proprietary data is employed to support program execution, the Contractor shall appropriately mark and include such data. The Contractor shall not include copyrighted data without specific written consent. If the Contractor Export Control and Compliance organization deems any data is covered by the Export Administration Regulations (EAR) or International Traffic in Arms Regulations (ITAR), the Contractor shall mark it accordingly.

The Contractor shall protect all emails that are sensitive by encryption or through the use of other secure means approved by the Government against unauthorized disclosure including interception and decryption by foreign nationals. Prior to delivery, the Contractor shall implement all safeguards necessary to ensure data is protected in accordance with the contract.

1.4 Resource Management

The Contractor shall manage the project resources, including, but not limited to, financial, schedule, personnel, materials, and equipment effectively and efficiently to complete all activities per the contract, including the delivery of all items that meet requirements, within cost and schedule constraints and commitments.

The Contractor shall deliver Financial Reports in accordance with CDRL RM-02.

The Contractor shall submit Integrated Program Management Reports (IPMR) (CDRL RM-03).

1.4.1 Work Breakdown Structure (WBS)

The Contractor shall develop and maintain a product oriented Contract Work Breakdown Structure (CWBS) and CWBS Dictionary (CDRL RM-04). The Contractor uses the WBS as the primary framework for contract planning, budgeting, and reporting of the cost, schedule, and technical performance status to the Government. The WBS structure shall be established by the Contractor (based on guidelines provided by the Government) and shall be reported to the Government at a minimum of Level 4 decomposition. The Contractor shall maintain a WBS at a minimum one level lower than reporting Level

4. The Contractor shall notify the Government of any WBS changes at Level 4 or higher before implementation.

1.4.2 Earned Value Management System (EVMS)

The Contractor shall use and maintain an EVMS to track and report cost and schedule performance. The Contractor's system shall meet the guidelines and be maintained in accordance with the Contract. The EVMS shall be supported by the Contractor's management processes and systems and in accordance with the Contractor’s Earned Value Management (EVM) Plan (CDRL RM-01). EVM shall not be required during the Commissioning Support and Post Launch Support Task Order periods. EVM shall not be required after delivery of the final instrument.

1.4.3 Performance Measurement Baseline (PMB)

The Contractor shall maintain a single PMB for this contract. The Contractor shall develop a time phased integrated plan to unify technical scope, schedule, and budget into an overall plan in accordance with the Contractor’s EVM Implementation Plan (reference ANSI/EIA748, Industry Guide for Earned Value Management for guidance). The Contractor shall define the GXI work scope, establish a schedule for accomplishing the work and estimate the resources required to accomplish the work. The

Government will conduct an Integrated Baseline Review (IBR) to validate the GXI cost and schedule baselines (reference Section 1.8.4 and CDRL RM-09). Once the PMB has been established and approved by the Government following completion of the IBR, comprehensive Estimates at Completion (EAC) shall be developed by the Contractor as part of the recurring detailed budget and planning process.

1.4.3.1 Baseline Change Control

In order to maintain baseline integrity and assure oversight of the baseline change control process, the Contractor shall use a formalized change control process for all Baseline Change Requests (BCR) via the Configuration Control Board (CCB) process already established by the Contractor. The Contractor shall notify the Government of any BCR over $500K or any BCR that impacts the critical path schedule prior to closure of the CCB and provide a copy of all associated materials upon request. BCRs incorporating rolling wave changes and/or new scope do not require notification to the Government, regardless of value.

1.4.4 Integrated Master Schedule (IMS)

In order to manage the Instrument effort, the Contractor shall develop, maintain, and deliver an IMS in accordance with CDRL RM-05.

The Contractor shall identify all external Giver-Receiver (G-R) items in the IMS.

The IMS reporting requirements for each flight model shall end once the model has been accepted by the government.

1.5 Risk Management

The Contractor shall establish and maintain a comprehensive risk management program to identify and manage all performance, reliability, schedule, cost, and safety risks on the Contractor’s project. The Contractor shall prepare, deliver, and implement a Risk Management Plan (RMP) in accordance with CDRL PM-03 and the requirements specified herein. The Contractor shall develop and implement risk management strategies, actions, and assign tasks and appropriate resources to manage, mitigate, and control the risks. The Contractor shall document all identified risks in the risk management system and report on them in accordance with the RMP. The Contractor shall present open risks at the PMR as well as any risks closed since the prior PMR. The Contractor shall make the full Risk List available on request.

All approved and funded risk mitigation activities shall be integrated into the IMS (CDRL RM-05) and planned budget.

1.6 Configuration and Information Management

The Contractor shall oversee and manage the generation, configuration control, and distribution of all documents required by the contract. The Contractor shall provide and implement a Configuration Management Plan (CMP) in accordance with CDRL PM-04.

In accordance with the approved CMP, the Contractor shall establish, implement, and maintain a Configuration Management System that provides Configuration Management control of configured items including all flight hardware, all GSE hardware, and all controlled documentation developed under this contract, including drawings, procedures, plans, CDRLs, and program review materials.

The Government will post on the Instrument section of the GeoXO Portal Government technical and contractual documentation generated in support of the GeoXO Instrument.

In order to facilitate efficient access to working materials and presentations, the Contractor shall provide the Government COR, IM, and three other Government representatives of the Government’s choosing access to the Contractor’s shared folders or drives as mutually agreed.

The Contractor shall establish a Configuration Control Board to review and approve changes to the flight models, software, GSE, and all controlled documents.

Deviations and Waivers shall be submitted to the Government as CCRs.

The Contractor shall submit Class I changes, as defined in the DID for CDRL PM-05, to the Government for approval before implementation of the change, in accordance with Configuration Change Requests, Deviations and Waivers, CDRL PM-05.

The Contractor shall submit Class II changes to the Government for concurrence with the classification, in accordance with Configuration Change Requests, Deviations and Waivers, CDRL PM-05. If the Government determines that a Class II classification is incorrect, the Contractor shall resubmit the change as a Class I change.

The Contractor shall separately maintain and post each Class I and Class II Configuration Change Request in the GeoXO portal per agreed upon processes.

1.6.1 Participation in Government and Spacecraft CCBs

The Contractor shall support and participate in the Government and Spacecraft Contractor Configuration and Change Control processes as requested for Government and Spacecraft Contractor controlled documents that are applicable to the Contract.

1.6.2 Knowledge Capture / Lessons Learned

The Contractor shall develop a Knowledge Management Plan, to document how the experiential knowledge pertinent to the development, manufacture, and test of the Instrument will be identified, captured, and used by project Contractor and Government personnel in accordance with CDRL PM-06.

The Contractor shall implement a Knowledge Management Program so that the knowledge base developed and lessons learned during design and development of the EDM and all FMs will be available to the Instrument Project personnel through the life of the mission.

1.7 Special Task Activities

The Contractor shall execute Special Task Activities relating to the development, implementation, and operation of the Instrument and ground systems as required and authorized by Contract clause x.y.

Upon request by the Contracting Officer, the Contractor shall submit a Contractor Task Plan for each Special Task Activity.

1.8 Reviews and Meetings

The Contractor shall provide the technical and administrative support for all Project reviews and meetings including, but not limited to, Instrument Design Reviews, Project Status Reviews, Technical Meetings, Data Reviews, Design Modification/Upgrade Reviews, and Subcontract Reviews.

Unless stipulated otherwise by the Government, the Contractor shall hold all Instrument Project Reviews and meetings at the Contractor's facility.

All reviews and meetings shall provide a virtual attendance option.

The Contractor shall record and deliver meeting minutes for Technical Interchange Meetings (TIMs) and reviews.

1.8.1 Kick-off Meeting

The Contractor shall hold a program kickoff meeting approximately 2 weeks after the contract award.

The Kickoff Meeting agenda shall be developed jointly with the Government, but should include:

a) An overview and introduction to the organization and personnel (both vendor and Government Teams)

b) A top-level look at the total program schedule with a more detailed look at the near-term schedule (between kickoff and IBR)

c) A summary of regularly scheduled meetings and a tentative meeting schedule for the first 6 months (PMRs, table top reviews, peer reviews, project milestone reviews, etc)

d) An overview of the instrument design concept

e) An overview of any technology development work

f) An overview of current risk database and risk management approach

g) Overview of configuration management approach

h) Overview of SMA and quality processes

i) Overview of vendor facilities (tour if possible)

The Kickoff will nominally to be held at vendor facility. Assumed duration is 1 day.

1.8.2 Requirements Walkthrough

Between the Kickoff and the first Project Management Status Review, the Contractor shall support a line-by-line review with the Government of the contract schedule and clauses, the SOW, the CDRL, PORD, GIRD, UIID, and IMAR to ensure mutual understanding of all requirements.

The Contractor shall coordinate with the Instrument Manager on the logistics for the meeting, but should nominally plan for a 3-day in-person meeting.

1.8.3 Project Management Status Reviews

The Contractor shall hold monthly Project Management Status Reviews (PMSR) with the Government for the purpose of reviewing the status of the instrument and GSE development, and the overall status of the project.

The PMSRs will be held at the Contractor's facility. The PMSR will nominally be 8 hours until CDR and 4 hours after. Any special topic splinters shall be coordinated with the Instrument Manager.

The Contractor shall prepare, present, and deliver a PMSR Technical (PMSR-T) Data Package in accordance with CDRL PM-07 and a PMSR Businees (PMSR-B) Data Package in accordance with CDRL

RM-08.

1.8.4 Integrated Baseline Review (IBR)

Approximately two months after award the Contractor shall conduct a Project Implementation and Workforce Exercise meeting with the Government in preparation for the IBR, intended to establish a baseline schedule and workflow plan.

Approximately 6 months after contract award, the Contractor shall conduct the IBR.

The Contractor shall include a review of the Contractor's earned value assessment and reporting system in the IBR.

The Contractor shall plan for a three-day IBR.

The IBR shall follow the WBS based schedule in sufficient depth of detail to show the critical path, all linkages to lower tasks to expose missing dependencies, and to ensure a smooth workflow plan through the delivery of contracted units.

The Contractor shall submit an IBR Package in accordance with CDRL RM-09.

1.8.5 Contractor-Led Meetings and Reviews

The Contractor shall implement a thorough technical peer review process of component and subsystem designs, conduct independent technical assessments of instrument activities, and hold formal design reviews. The reviews listed in this section should not be considered a complete set of reviews for the Contractor’s program. Additional reviews that the Contractor deems necessary to successfully execute the program will be conducted at the Contractor’s discretion.

The Contractor shall track actions items assigned by the Government in the MAID. Reviews are not complete until actions are complete or a detailed plan for closure is submitted by the Contractor and approved by the Government.

Mission Assurance reviews and boards are prescribed in the IMAR document.

1.8.5.1 Weekly Meetings

In order to track status, coordinate activities, and resolve issues, the Contractor shall support weekly meetings and telecons with the Government at mutually agreed to times.

1.8.5.2 Engineering Peer Reviews

Engineering Peer Reviews (EPRs) provide focused, in-depth, table-top level technical discussions that support any evolving design and development of a subsystem, including critical documentation or data packages. EPRs are especially useful for new/novel designs or approaches and/or higher-risk areas. The Contractor shall conduct multiple peer reviews, as appropriate, over the lifecycle as designs evolve to identify and resolve concerns as they arise in the design process, prior to formal, system level reviews such as PDR an CDR, and for any significant design changes. The Contractor shall provide an Engineering Peer Review (EPR) Plan as part of the Systems Engineering Management Plan (SEMP) in accordance with

CDRL SE 2-1.

The Contractor shall coordinate with the Government on the proposed EPR objectives, scope, and agenda.

The Contractor shall chair and host EPRs at the Contractor’s facilities with review panels in accordance with the approved EPR Plan (CDRL SE 2-1), NPR-7123.1, NASA Systems Engineering Processes and Requirements, Appendix G and GPR 8700.6, Engineering Peer Reviews, to review any changes in the design.

Unless stipulated otherwise by the Government, the Contractor shall include Government technical experts in the Engineering Peer Reviews.

The Contractor shall include in the Engineering Peer Reviews Government and Contractor's technical experts with significant practical experience relevant to the technology and the requirements for the review.

The Contractor shall notify the Government at least ten working days in advance of each EPR and make available any prepared EPR material at least three working days prior to each EPR. The Contractor shall document, track, and provide status of EPR actions and closures in the MAID and provide a summary at PMRs.

The Contractor shall document the EPRs in accordance with CDRL SR-07, Engineering Peer Review Package.

1.8.5.3 Subcontract, and Subsystem Reviews

The Contractor shall plan and conduct Subcontract and Subsystem reviews per the Project Management Plan, CDRL PM-01.

Unless stipulated otherwise by the Government, the Contractor shall include Government personnel in Subcontract and Subsystem Reviews.

The Contractor shall conduct PDRs and CDRs for all major subsystems whether the subsystems are provided by the Contractor or by a subcontractor.

Whether internal or external, Subcontract and Subsystem reviews shall be conducted by the Contractor and chaired and staffed by independent reviewers for the hardware under review. For all Subsystem reviews, a Government representative is co-chair. The Contractor shall provide ten (10) days prior notification so that Government representatives can be present.

For Subcontractor and Subsystem reviews, the Contractor shall document the minutes. Any action items shall be captured in the MAID.

The Contractor shall submit Subsystem / Subcontract Review Data Packages in accordance with CDRL

SR-07.

1.8.5.4 Engineering Development Model (EDM) Summary Review

The Contractor shall conduct a review to present the summary of EDM activities to the Government, no later than the start of FM-1 integration.

1.8.5.5 Design Modification Reviews

The Contractor shall hold a Design Modification Review (DMR) to review any changes to the flight design as a result of the EDU/EDM program. The Contractor shall plan for up to a one-day review, not including resolution of RFAs.

The Contractor shall deliver a DMR Data Package in accordance with CDRL SR-06.

The DMR can be combined with the EDM Summary Review if mutally agreed by the Contractor and Government.

1.8.5.6 Manufacturing Readiness Reviews

The Contractor shall conduct Manufacturing Readiness Reviews (MRRs) prior to the start of manufacturing critical components identified in the Critical Supplier and Subsystem List, PM-TBD.

Unless stipulated otherwise by the Government, the Contractor shall include Government personnel in the MRRs.

The MRRs shall include a review of any design non-conformances, status of drawings, status of build / manufacturing documentation, facility and ground support equipment readiness, mission assurance / process control, and schedule.

The Contractor shall provide five working days advance notification so that Government representatives can be present.

1.8.5.7 Test Readiness Reviews

The Contractor shall conduct Test Readiness Reviews (TRRs) immediately prior to the start of any test of critical sub-assemblies, the instrument, and instrument suite-level tests..

Unless stipulated otherwise by the Government, the Contractor shall include Government personnel in TRRs. The Contractor shall send a test procedure to the Government at least 3 days prior to the review.

1.8.5.8 Test Data Reviews

The Contractor shall conduct Test Data Reviews (TDRs).

Unless stipulated otherwise by the Government, the Contractor shall include Government personnel in TDRs.

The Contractor shall conduct TDRs for data collected from instrument critical sub-assembly, subcontracted subassembly, instrument, and instrument suite-level tests.

The Contractor shall conduct TDRs prior to the shipment of deliverable GSE.

The Contractor shall conduct a TDR of the interim data during the qualification or acceptance test process of the instrument prior to the breakdown of any test setup (e.g., vibration testing, EMI/EMC testing, thermal vacuum testing, etc.) to ensure successful collection of required data, and prior to the PSR, to determine readiness.

1.8.5.9 Software Reviews

The Contractor shall plan and conduct software reviews per the Software Management Plan, CDRL SW- 01.

Unless stipulated otherwise by the Government, the Contractor shall include Government personnel in Software Reviews.

The Contractor shall provide seven working days of advance notice to enable participation by the Government personnel.

The Contractor shall conduct the following software reviews:

a) Software Requirements Specification Review/Walkthrough

b) Software Preliminary Design Review

c) Software Critical Design Review

d) Software Test Readiness Review

e) Software Qualification Review

The Contractor shall provide a Software Preliminary Design Review (SWPDR) Data Package in accordance with CDRL SW-04.

The Contractor shall provide Software Critical Design Review (SWCDR) Data Package in accordance with

CDRL SW-05.

The Contractor shall provide a Software Test Readiness Review (SWTRR) Data Package in accordance with CDRL SW-09.

The Contractor shall submit a Software Acceptance Review (SWAR) Data Package in accordance with

CDRL SW-11.

The Contractor shall conduct software peer reviews.

The Contractor shall document the scope and process for conducting software peer reviews in the Software Management Plan in accordance with CDRL SW-01.

1.8.6 Government Chaired Instrument Reviews

The Contractor shall conduct Government-chaired Instrument Design Reviews. The Government will chair these reviews and will include appropriate subject matter experts to serve on the review board (Goddard System Review Team (GSRT)). The reviews will cover all aspects of flight and ground hardware, software, and operations for which the Contractor has responsibility.

The Contractor shall conduct a dry run of each design review, with the Government Instrument team in attendance, approximately three weeks prior to the review.

After each review, the Contractor shall document all RFAs in the MAID within 1 week of receipt.

Each design review (PDR, CDR, etc.) is not considered complete until approved by the Government. If the Government determines that a delta review is necessary, the Contractor shall conduct such review at a time mutually agreed upon with the Government.

The Contractor shall deliver an outline for the Design Review Package thirty days before each of the contractually-required Instrument Design Reviews.

The Contractor shall deliver the Design Review Package seven days before each of the contractually-required Instrument Design Reviews.

1.8.6.1 System Requirements/Definition Review (SRR/SDR)

The Contractor shall conduct an SRR/SDR after completing requirements definition and flowdown.

The Contractor shall plan for a three-day SRR/SDR, not including resolution of RFAs.

The Contractor shall deliver an SRR/SDR Data Package in accordance with CDRL SR-01.

1.8.6.2 Preliminary Design Review (PDR)

The Contractor shall conduct a PDR at the conclusion of the preliminary design efforts and after testing the breadboard or brassboard models of critical subassemblies/assemblies, unless the Contractor requests and the Government concurs with holding the PDR earlier.

The Contractor shall plan for a three-day PDR, not including resolution of RFAs.

The Contractor shall deliver a PDR Data Package in accordance with CDRL SR-02.

1.8.6.3 Critical Design Review (CDR)

The Contractor shall conduct a CDR prior to the start of manufacture of the PFM hardware unless the Contractor requests and the Government concurs with an earlier start.

The Contractor shall plan for a four-day CDR, not including resolution of RFAs.

The Contractor shall deliver a CDR Data Package in accordance with CDRL SR-03.

1.8.6.4 Pre-Environmental Review (PER) - Each Instrument

The Contractor shall conduct a PER prior to the start of environmental testing of the EDM (if applicable) and each FM instrument to establish the readiness of the system and to evaluate the environmental test plans and procedures.

The Contractor shall plan for a three-day PER, not including resolution of RFAs.

The Contractor shall deliver a PER Data Package in accordance with CDRL SR-04.

1.8.6.5 Pre-Shipment Review (PSR) - Each Instrument

The Contractor shall conduct a pre-ship review (PSR) at the conclusion of the integration and test effort prior to shipment and/or storage of each instrument. If the instrument is stored for a period greater than six months prior to shipment, the Contractor shall prepare an abbreviated (half-day) delta-PSR immediately prior to shipment to review logistical shipping details as well as any additional work or testing performed on the instrument since the PSR.

The Contractor shall plan for a three-day PSR, not including resolution of RFAs.

The Contractor shall deliver a PSR Data Package, in accordance with CDRL SR-05.

1.8.7 Observatory-level Reviews

The Contractor shall provide technical support to all Observatory-level reviews, including Observatory integration and test reviews, conducted at the Spacecraft Contractor's facility.

The Contractor shall support the Observatory-level reviews by presentations and/or documentation; for example, by providing and/or presenting instrument overview or design summary, test and data evaluation summaries, etc., in accordance with CDRL SR-10, “Inputs to Higher Level Reviews”.

The Contractor shall attend all Observatory-level Reviews including but not necessarily limited to:

a) Instrument Receiving Review (IRR) (1 day for each FM)

b) Observatory Pre-environmental Review (3 days for each FM)

c) Observatory Pre-storage Review (3 days for each FM)

d) Observatory Pre-ship Review (3 days for each FM)

1.8.8 Program-level Reviews

The Contractor shall support the Program-level Reviews by presentations and/or documentation; for example, an instrument overview or design summary, test and data evaluation summaries, etc.

The Contractor shall support the following Program-level Reviews:

a) Mission System Definition Review (MSDR) (3 days)

b) Mission Preliminary Design Review (MPDR) (3 days)

c) Mission Critical Design Review (MCDR) (3 days)

d) System Integration Review (SIR) (3 days for each FM)

Any inputs shall be provided in accordance with CDRL SR-10, “Inputs to Higher Level Reviews”.

1.8.9 Operations Reviews - Each Flight Model

The Contractor shall support the Operations Reviews for each FM by presentations and documentation;

for example, by providing and/or presenting instrument overview or design summary, test and data evaluation summaries, etc., in accordance with CDRL SR-10, “Inputs to Higher Level Reviews”.

The Contractor shall support the following Operations Reviews for each FM at NSOF:

a) Mission Operations Review (MOR) (3 days)

b) Flight Operations Review (FOR) (3 days)

c) Operational Readiness Review (ORR) (3 days)

d) Post Launch Assessment Review (PLAR) (2 days)

1.8.10 Participation in Observatory Level Working Groups

The Contractor shall support Government-led and Spacecraft-led Working Groups. This will include Working Groups for Observatory I&T: General I&T Planning and Procedure Development, Preperation for Vibration Testing, EMI/EMC, Thermal Vacuum Testing, Mission Rehearsals, Operations Planning, etc.

The Contractor shall attend the meetings in person when requested to do so by the Government.

2 Systems Engineering The Contractor shall establish and maintain a Systems Engineering Program for directing, specifying, and overseeing the design and technical development of the Instrument, GSE, and ground algorithms.

The Contractor shall prepare, deliver, and implement a Systems Engineering Management Plan in accordance with CDRL SE 2-1.

The Contractor shall provide verification reports for all the requirements in the contractual documents.

2.1 Systems Management and Engineering

The Contractor shall perform all system studies, trades, and risk assessments necessary to develop an instrument system design that meets the Instrument performance, operational, and interface requirements.

The Contractor shall flow down the Instrument performance, operational, and interface requirements into engineering functional requirements, detailed equipment requirements, and end item design requirements.

The Contractor shall ensure that all subsystems, both individually and in combination, meet the design and performance specifications and that the design specifications are sufficient to meet the mission life and reliability requirements as defined in the PORD and IMAR.

The Contractor shall develop and maintain the Instrument Systems Specification in accordance with CDRL SE 1-1. The Contractor shall deliver the Instrument Systems Specification in DOORS.

The Contractor shall prepare, deliver, and maintain a Drawing Tree(s) in accordance with CDRL SE 1-6.

The Contractor shall prepare, deliver, and maintain a Document Tree(s) that includes all instrument and GSE design documentation in accordance with CDRL PM-10.

The Contractor shall verify that the GSE meets all design and interface requirements prior to integration with flight hardware.

The Contractor shall establish and maintain a System Performance and Environmental Verification Program to demonstrate that the FMs meet all mandated and derived performance requirements.

The Contractor shall prepare, deliver, and implement a System Performance Verification Plan (SPVP) and Compliance, including a Systems Performance Verification Matrix that documents the System Performance Verification Program at assembly, subsystem, and instrument level of assembly, in accordance with CDRL SE 2-2.

The System Performance Verification Plan (SPVP) shall address how the EDM serves FM performance verification.

The Contractor shall provide System Performance Verification Reports in accordance with CDRL SE 4-10.

2.2 Use of DOORS Tool

The Contractor shall utilize Telelogic Dynamic Object Oriented Requirements System (DOORS®) as the Requirements Management tool.

The Contactor shall provide monthly drops of DOORS dpa modules for Level 4 through Level 6 requirements.

The Government will provide DOORS modules for the PORD, UIID, GIRD, and IMAR. The Contractor shall utilize the Government delivered DOORS modules in their database.

The Contractor shall use standard attributes that will be supplied and agreed to by the Governement, to include (but not limited…