Enclosure 1 - DRAFT LISA OPTICAL TELESCOPE ASSEMBLY (OTA) SOW.pdf

LISA OTA SOW LISA-SOW-XXXX, Revision - Draft Effective Date: April 1, 2023 i

LISA-TELE-SOW-0004, Revision -

Laser Interferometer Space Antenna (LISA) Telescope, Optical Telescope Assembly (OTA) Statement of Work (SOW) ii

Table of Contents

1 INTRODUCTION

1.1 Background

1.2 Scope

1.3 Related Documentation

1.3.1 Applicable Documents

1.3.2 Reference Documents

2 REQUIREMENTS

2.1 Management

2.1.1 Project Management

2.1.2 Government Insight

2.1.3 Reviews and Meetings

2.1.3.1 Major Reviews

2.1.3.1.1 OTA Reviews

2.1.3.1.2 Mission Level Reviews

2.1.3.2 Engineering Peer Reviews

2.1.3.3 Other Reviews and Meetings

2.1.3.3.1 Scheduled Weekly Teleconferences

2.1.3.3.2 Monthly Project Status Reports and Reviews

2.1.3.3.3 Technical Exchange Meetings and Working Groups

2.1.3.3.4 Status and Planning Meetings

2.1.4 Access to Controlled Facilities

2.1.5 Risk Management

2.1.6 Resource Management

2.1.7 Configuration Management

2.1.8 Lessons Learned Reporting

2.2.1 Requirement Analyses, Derivations, and Allocations

2.2.2 Interface Definition, Verification and Control

2.2.3 Design and Performance Verification

2.2.4 Trending

2.2.5 Models

2.2.5.1 Optical Models

2.2.5.2 Mechanical Models

2.2.5.3 Finite Element Models

2.2.5.4 Thermal Model

2.2.5.5 Models - General

2.2.6 Units

2.3 Mission Assurance

3 OTA DEVELOPMENT

3.1 Design Engineering

3.2 Trade Assessments

3.3 OTA Design Updates

3.3.1 OTA Electronics and Electrical Systems Design

3.3.2 OTA Structure Design

iii

3.3.3 OTA Mechanisms Design

3.3.4 OTA Thermal System Design

3.3.5 This item intentionally left blank

3.3.6 OTA Integration and Test Planning

3.4.1 Fabrication, Modification, Assembly, and Test

3.4.2 Integration and Test

3.4.2.1 Integration

3.4.2.2 Environmental and Performance Testing

3.4.2.3 Integration of the OTA and MSS

3.4.3 OTA Simulators

3.5 OTA Operations Support

3.5.1 Operational Procedures and Documentation

3.5.2 Command and Telemetry Database Support

3.5.3 Training Support

3.6 Packaging, Handling, Storage, and Transportation

3.7 Delivery, Checkout, and Acceptance

3.8 Ground Support Equipment

3.8.1 Mechanical Ground Support Equipment

3.8.2 Electrical Ground Support Equipment

3.9 Shipping, Storage, and Purge Equipment

3.10 Spares

3.11 Engineering Development Units

4 POST-DELIVERY SUPPORT

5 CONTRACT DELIVERABLES REQUIREMENTS LIST AND GOVERNMENT

FURNISHED EQUIPMENT

APPENDIX A ABBREVIATIONS AND ACRONYMS

List of Figures

Figure 1. Subsystem Block Diagram with Optical and Mechanical Interfaces

1 INTRODUCTION

1.1 Background

The measurement of gravitational waves will yield a revolutionary new perspective on our universe, which has already been intensely studied using electromagnetic waves in many wavelength bands. Recently, gravitational waves generated by the merger of a pair of ~ 30 solar mass black holes were detected by the ground-based LIGO network, nearly 100 years after Albert Einstein unveiled the General Theory of Relativity. Ground-based observatories have since released a catalog of almost 100 events from the first three observing runs, and more are expected. While the ground-based detectors are sensitive in the audio band, the Laser Interferometer Space Antenna (LISA) will be the first space-based observatory of gravitational waves, listening for signals in the millihertz frequency band. The population of sources in this band is large and diverse, including events such as supermassive black hole mergers, stellar mass black holes orbiting supermassive black holes (known as Extreme Mass Ratio Inspirals, or EMRIs), galactic compact binaries, etc.

LISA (https://www.cosmos.esa.int/web/lisa) is an ESA-lead mission which consists of three spacecraft (S/C) that are separated by 2.5 million kilometers in an Earth-trailing orbit. Each S/C houses two freely-falling proof masses, which serve as inertial references. Laser beams are sent back and forth between the different spacecraft to track the distances between pairs of proof masses, and the signals are combined to search for gravitational wave signatures that come from distortions of the spacetime surrounding the constellation.

These signals are extremely small and require a very sensitive instrument to detect. The change in the distance between proof masses is tracked down to ~10 picometers over timescales of ~1000 seconds, a fractional precision of better than one part in 1020 of the arm length. Ultra-stable telescopes are essential for the implementation of this precision strain measurement, in order to transfer enough laser light between S/C, and these telescopes are one of NASA's contributions to the LISA mission. The telescopes must simultaneously receive and transmit the laser light without contributing path-length noise to the inter-S/C distance determination, with an allocation of ~1 pm/√Hz in the mHz band to each telescope. There is one telescope associated with each of the two proof masses on a LISA S/C, giving a total of six flight telescopes in the constellation.

NASA has, as part of an engineering contract, built the following units:

• Structural/Thermal Model

• Engineering Development Unit (EDU) #1

• Engineering Development Unit (EDU) #2 Information gained, particularly the lessons learned, during this development program will be provided to the Contractor as reference material. However, the Contractor should not assume that direct access to, or provision of, these units will be available. This procurement will be for the development and build of the following flight unit optical telescopes:

• 1 Engineering Test Unit (ETU)

• 1 Qualification Unit (QM) (should be capable of becoming a Protoflight Unit)

• 6 Flight Units

• 2 Spares

1.2 Scope

The scope of this OTA Statement of Work (SOW) includes all efforts and responsibilities for the personnel, services, materials, equipment, and facilities necessary to build, refurbish, or modify all OTAs, as required, to meet LISA performance requirements.

The Contractor shall design, fabricate, align, test, verify per approved plan and deliver six flight and two spare telescopes and provide post-delivery support for both the observatory integration and test program for the LISA mission. A design reference concept has been created by the government to demonstrate feasibility (LISA Telescope Reference Design) however, the contractor can define their own design concept that meets LISA telescope requirements. The contractor shall provide design details, models, and analysis to compare against requirements and tolerances for the LISA program. The final selection of a design will be made by no later than the Preliminary Design Review (PDR).

The Contractor shall provide all personnel, facilities, equipment, material and services necessary to produce the flight and spare telescopes to meet LISA performance requirements. Prior to building the first flight unit, the contractor shall demonstrate that all the processes are in place to build all telescopes to meet the LISA telescope requirements. The dimensional stability requirement is planned to be verified in two parts. The Contractor is expected to verify compliance by analysis before shipping. It is planned that either the QM telescope or one of the flight telescopes will undergo detailed performance testing to verify the dimensional stability requirement, but this will be performed at Government facilities post-delivery. It is planned that the ETU telescope will be delivered to ESA for integration and performance testing of an ETU payload. The ETU shall therefore be fully optically representative as well as having flight representative mechanical interfaces. The contractor shall provide a plan for the qualification program of the flight design. This plan shall include a test program for the Qualification Unit to address any issues carried over from the technology development program.

Integration and test of the OTAs to the scientific instrumentation is conducted at the European Space Agency’s Prime Contractor facility. The selection and announcement of that Prime Contractor and facility have not been announced. The Contractor shall support observatory level activities including, but not limited to, alignment integration and test, verification and validation, and calibration conducted by the Prime at their facilities. The Contractor shall support the on-orbit commissioning portion of the mission.

Additionally, the contractor shall develop a plan for flight telescope production and provide a Life Cycle Cost (LCC) estimate. This plan should include all required facilities, personnel, materials, services and equipment to complete the Structural/Thermal model Engineering Test Unit, Qualification Unit, 6 Flight and 2 Flight Spare telescopes within the required delivery schedule. This may require that two or more telescopes be processed in parallel to deliver all telescopes within the required timeframe. This plan shall also include a spares philosophy at the telescope component level, as required.

Additionally, the contractor shall perform an engineering design trade study for the telescope mechanical interface to the payload structure called the MSS [Moving Optical Sub-Assembly

(MOSA) Support Structure]. The contractor shall perform design trades of mechanical interface and bi-pod mount designs to meet flight telescopes requirements.

The Contractor shall review/or deliver drawings, specifications, reports, plans, optical and mechanical models, manuals, and other specified data in accordance with the Contract Data Requirements List (CDRL) as outlined in Attachment (TBD).

The Contractor shall provide documentation and perform other tasks in accordance with the requirements of this SOW and the applicable documentation referenced herein.

This OTA SOW specifies the Contractor requirements for performing all development activities through launch and on-orbit verification, validation, and calibration. In the event of any differences between this document - the OTA SOW, and other contractual documents, including in the OTA Requirements (OTAR, LISA- -TELE-REQ-0012), the OTA SOW will take precedence. The overall hierarchy is (1) OTA SOW, (2) OTAR.

The work described in this SOW is not all of equal importance or weight. The term "shall" designates the most important weighting level; that is, mandatory. Any deviations from these contractually imposed mandatory items require the approval of the Contracting Officer. A lesser term, "should", designates attributes that the Government values, but which are subject to tradeoff decisions. Such attributes may render the deliverable item more valuable to the Government, but the absence of such attributes does not render the item unacceptable.

“shall” statement Must complete, meet, or exceed the task, requirement, or specification.

“will” statements Actions the Government must complete or deliver.

“should” statements Non-mandatory provision or goal subject to tradeoff decisions. No deliverable items and not subject to verification.

This document, the OTA SOW, is specifically for Phase B/C/D including on-orbit commissioning.

The “shall” and “should” statements in this document only, OTA-SOW, are compliance requirements, and not verifiable requirements.

Figure 1. Subsystem Block Diagram with Interfaces

1.3 Related Documentation

The latest versions of all documents below should be used. LISA documents can be obtained from the LISA TDMS System.

1.3.1 Applicable Documents

The following documents are referenced within this document and are directly applicable or contain policies or other directive matters that are binding for the performance of the contract.

These documents establish detailed specifications, requirements, and interface information necessary for the performance of the contract. In the event of conflicting requirements between this SOW and the Applicable Documents, the Contractor shall immediately notify the GSFC Contracting Officer’s Representative (COR) that there is such a conflict and request direction from the Government as to how to proceed.

For traceability, the contractor shall trace down only one level for each Applicable Document:

any applicable documents within the documents listed are considered as applying directly to the performance of the OTA contract. For example, the LISA MAR (LISA-SMA-REQ-0010) lists NASA Procedural Requirements (NPR) 7150.2 as an applicable document. Therefore, NPR

7150.2 is an applicable document with respect to this SOW. However, the documents listed in Section P.4 of NPR 7150.2 are not considered Applicable Documents for the purposes of this

SOW.

Document Number Title LISA-SMA-REQ-0010 LISA Mission Assurance Requirements (MAR) LISA- TELE-SOW-000 OTA Statement of Work (SOW)

LISA- TELE-REQ-0012 OTA Requirements (OTAR) LISA-TELE-SPEC-xxx Math Model Guidelines (MMG)

1.3.2 Reference Documents

The following documents are referenced herein and amplify or clarify the information presented in this document. These documents are not binding on the content of this document.

Document Number Title MIL-HDBK-217 Reliability Prediction of Electronic Equipment NASA-STD-5001B Structural Design and Test Factors of Safety for Spaceflight

Hardware NASA-STD-5005D Standard for the Design and Fabrication of Ground Support

Equipment NASA-STD-5020 Requirements for Threaded Fastening Systems in Spaceflight

Hardware NPD 7120.4 NASA Engineering and Program/Project Management Policy NPR 7120.5 NASA Space Flight Program and Project Management

Requirements GPR 7120.3 Management of Principal Investigator Mode Missions GPR 7120.4 Risk Management GPR 7123.1 Systems Engineering GSFC-STD-1000G Rules for the Design, Development, Verification and Operation of Flight Systems GSFC-STD-1001A Criteria for Flight and Flight Support System Lifecycle Review GSFC-STD-7000A General Environmental Verification Standard (GEVS) for GSFC

Flight Project Programs and Projects 540-PG-8700.2.1.C Design of Dollies, Stands, and Spacecraft Shipping Containers

2 REQUIREMENTS

2.0-A The Contractor shall design, develop, fabricate, modify, assemble, integrate, and test the hardware described in this SOW in compliance with the applicable documents listed in Section 1.3.1.

2.0-B For non-hardware support aspects of this SOW, the Contractor shall provide the following necessary to accomplish the described support:

• systems and discipline engineering

• expert personnel

• travel

• reports and documentation

• software or software changes

• ground support equipment

• operations

2.0-C The Contractor shall deliver to the Government a Structural/Thermal Model

Engineering Test Unit, a Qualification Unit, six flight telescopes and two flight spare telescopes that are fully verified and characterized to be compliant with the requirements of this contract.

2.0-D The contractor shall seek advance written authorization from GSFC in accordance with CDRL No.: SE 1 PM-10 Title: Engineering Change Proposals (ECPs), Deviations, and Waivers Configuration Change Requests, Deviations, and Waivers for deviations from this SOW (including requirements contained in Applicable Documents of Section 1.3.1).

2.0-E The Contractor should utilize industry-standard practices and methodologies for design, fabrication, assembly, integration, and testing when appropriate and applicable with the intent of cost or schedule savings to the Government. In areas where the Contractor proposes to implement an industry-standard practice or methodology that deviates from this SOW, or the supporting applicable documents, the Contractor shall document the pragmatic savings and seek concurrence at the time of the contract award and only act upon when approved by the Government.

2.1 Management

2.1-A The Contractor shall manage all aspects of this contract effort to ensure that the contract requirements, including technical and programmatic, are met or exceeded. In further detail, this includes management of the administrative and technical direction, schedule control and reporting, financial control and reporting, Government property reporting and control, subcontract performance, configuration management and documentation, and other required reporting efforts.

2.1-B The Contractor shall coordinate, schedule, and document the activities of the pertinent engineering groups contributing to the SOW tasks.

2.1-C The Contractor shall be responsible for traceability and reporting of all its subcontractors’ cost, schedule, and technical performance.

2.1-D The Contractor shall analyze the OTA functional, performance, interface, mission assurance, and verification requirements as specified in the OTA Requirements (LISA-TELE-REQ-0012) and referenced documents, in the context of the above assumptions, and define subsystem requirements and design concepts to the degree required to proceed with design, build, test, and delivery of the ETU, QM, Flight and Flight spare telescopes.

2.1-E The verification of requirements shall not invalidate previously verified requirements.

2.1.1 Project Management

2.1.1-A The Contractor shall maintain a project office to manage the technical activities and resources of the project.

2.1.1-B The Contractor shall appoint a Project Manager (PM) to direct and manage the

OTA project. The Contractor’s Project Manager is responsible for the overall technical performance, resource management, and schedule management of the contractual effort and all subcontracts. The Contractor’s designated Project Manager will report to a level of company management appropriate to ensure prompt resolution of all problems. For costing purposes, the duration of Project Management should be until on-orbit checkout and commissioning.

2.1.1-C The Contractor shall prepare a Project Management Plan, and a Final Report in accordance with items CDRL No.: PM-5 Title: Project Management Plan, and CDRL No.: PM-19 Title: Final Report, respectively.

2.1.1-D The Contractor shall prepare a Contract Work Breakdown Structure (CWBS) and

Dictionary in accordance with CDRL No.: PM-18 Title: Contract Work Breakdown Structure (CWBS) and Dictionary in which the Contractor shall define how the Contractor plans to organize, plan, and report on the work being conducted.

2.1.1-E The PM shall be the principal point of contact for GSFC in matters pertaining to the contract effort.

2.1.2 Government Insight

2.1.2-A The Contractor shall open to Government attendance all Contractor and subcontractor internal data, reviews, audits, meetings, fabrication, integration, tests, and other activities within the scope of the contract. For access and insight activity, “Government” includes Government personnel and Government Contractor personnel. The intended duration is nominally short and would tie to single events, yet could span multiple events or an entire phase. The Government intends to provide an on-site representative from Defense Contract Management Agency (DCMA) or other Government quality representatives. The contractor shall provide office space and the necessary support for the Government on-site representatives, as required.

2.1.2-B The Contractor shall notify the Contracting Officer when applicable and the

Contracting Officer’s Representative (COR) of the activities in 2.1.2-A in sufficient time (nominally five working days) to permit meaningful Government participation. The size and attendance of those activities should be proportional to the notification time.

2.1.2-C The Contractor shall allow and enable the use of Non-Disclosure Agreements

(NDA) with Government contractors where appropriate.

2.1.2-D It is the understanding of the Government that a few essential internal documents and procedures are highly proprietary. In some cases, the Contractor can withhold the methodology in an individual step of the design, fabrication, assembly, or test in benign and low risk situations. The withholding of information of a methodology will be handled on a case-by-case basis, which defines the size of an individual step, and access may involve a subset of the individuals listed above as “Government”. The Contractor cannot withhold information related to the output or result of a methodology or procedure. The Contractor cannot withhold methodology or procedural information from a Failure Review Board (FRB).

2.1.2-E The Contractor shall report technical information in compliance with CDRL No.:

SE-2 Title: Contractor-Generated Internal Technical Information.

2.1.3 Reviews and Meetings

The reviews listed in this section should not be considered a comprehensive set of reviews for the Contractor’s program. Additional reviews that the Contractor deems necessary to successfully execute the program may be conducted at the Contractor’s discretion.

2.1.3-A The Contractor shall provide an OTA Review Plan in compliance with CDRL No.:

PM-8 Title: Review Plan

2.1.3-B The Contractor shall notify the Government at least ten working days in advance of lower level Contractor subsystem reviews and Contractor-initiated Technical Exchange Meetings (TEMs) to allow the Government time to attend the review as part of its insight activities.

2.1.3.1 Major Reviews

All major Mission-level reviews will be convened and review boards appointed and chaired by the Government.

2.1.3.1-A At all reviews, including OTA, Payload, and Mission-level, the Contractor shall support and demonstrate compliance with the review as stated in the OTA-CDRL.

The OTA-CDRL references the GSFC success criteria for reviews, Criteria for Project Flight Critical Milestone Reviews (GSFC-STD-1001), as applicable to spaceflight systems, with some tailoring as appropriate.

2.1.3.1-B The Contractor shall respond as required to action items assigned by the Government.

2.1.3.1-C The Contractor shall prepare and present their portion of these reviews, as appropriate, ensuring that content is complete and accurate.

2.1.3.1-D When the Contractor is hosting, the Contractor shall provide space, high-speed data connections to the Internet, and facility services for personnel with-in the scope of the review or meeting.

2.1.3.1.1 OTA Reviews

2.1.3.1.1-A The Contractor shall host, prepare and present the following reviews and provide review packages in accordance with the CDRL and GSFC-STD- 1001A:

OTA - System Requirements Review (OTA-SRR) – CDRL No.: RE-1 Title:

OTA-System Requirements Review (OTA-SRR) Data Package OTA - Preliminary Design Review (OTA-PDR) - CDRL No.: RE-2 Title:

OTA-Preliminary Design Review (OTA-PDR) Data Package OTA - Critical Design Review (OTA-CDR) - CDRL No.: RE-3 Title: OTA-

Critical Design Review (OTA-CDR) Data Package OTA - Pre-Environmental Review (OTA-PER) - CDRL No.: RE-4 Title:

OTA-Pre-Environmental Review (OTA-PER) Data Package OTA - Pre-Shipment Review (OTA-PSR) - CDRL No.: RE-5 Title: OTA-Pre-

Shipment Review (OTA-PSR) Data Package OTA – Manufacturing Readiness Review (OTA-MRR) - (CDRL No.: RE-8

Title: OTA- Test Readiness Review (TRR) and Data Package OTA – Manufacturing Readiness Review (OTA-MRR) - (CDRL No.: RE-9

Title: OTA-Manufacturing Readiness Review (OTA-MRR) and Data Package)

2.1.3.1.1-B The Government will convene and appoint the review board for all major

OTA-level reviews.

2.1.3.1.1-C The Contractor shall invite the Government to all OTA reviews that are chaired by the Contractor.

2.1.3.1.1-D The Contractor shall assume that each OTA review requires three days to complete with roughly 35 people from the Government.

2.1.3.1.1-E The Contractor shall conduct one dry-run of all OTA Reviews with the

Government approximately four weeks in advance of the review to allow for sufficient feedback to the review.

2.1.3.1.1-F The Contractor shall host and work with the Government project and review team for an additional day following all reviews to discuss and address issues raised and actions assigned at the reviews.

2.1.3.1.2 Mission Level Reviews

2.1.3.1.2-A The Contractor shall prepare and present in person material at each of the following Mission Level reviews:

Mission Preliminary Design Review (MPDR) Mission Critical Design Review (MCDR) MOSA Preliminary Design Review MOSA Critical Design Review Mission SIR

2.1.3.1.2-B The Contractor can assume four (4) supporting Mission Level Engineering

Peer Reviews per Mission-Level Review.

2.1.3.1.2-C The Contractor shall prepare their portion of the above Mission Level reviews in accordance with CDRL No.: RE-6 Title: Inputs to Mission Level and NASA LISA Project level Reviews Data Package. The Government leads the Mission Level reviews and presents the majority of the material.

2.1.3.1.2-D The Contractor shall respond to action items as requested by the Government with-in 30 calendar days.

2.1.3.1.2-E The Contractor shall participate in dry runs of all Mission-Level Reviews and supporting Peer Reviews with the Government approximately three weeks in advance of the review(s). The Contractor can assume one dry-run per Mission-Level Review and one dry-run for supporting Peer Reviews. The Contractor can assume that the Mission-level reviews will take four days and that dry-runs will take two days of Contractor support. The Contractor can assume all Mission Level Reviews will take place at ESA or ESA Prime Contractor site. The Contractor may support dry runs in person or by teleconference and electronic web interface for presentation materials, assuming that the Contractor has electronic services compatible with those of the Government. For estimating purposes, the Contractor should assume five people attending each Mission Level review.

2.1.3.2 Engineering Peer Reviews

2.1.3.2-A The Contractor shall define and implement a set of robust and comprehensive

Engineering Peer Reviews (EPRs) for the hardware subsystems of the OTA commensurate with the scope, complexity and acceptable risk of the product, the maturity of the OTA design, and the extent of and risk associated with any differences from the original assembly.

2.1.3.2-B The Contractor shall submit the Engineering Peer Review Plan in accordance with

CDRL No.: PM-9 Title: Engineering Peer Review Plan.

2.1.3.2-C The Contractor shall conduct the peer reviews in accordance of the plan and the

CDRL No.: RE-7 Title: Engineering Peer Reviews and Data Packages. The Contractor should assume this to be on order with the number of engineering disciplines supporting the OTA for each phase.

2.1.3.3 Other Reviews and Meetings

2.1.3.3-A In addition to the established meetings required in this section, the Contractor shall support routine informal meetings and telecons with the Government as necessary and outlined below.

2.1.3.3.1 Scheduled Weekly Report and Teleconferences

2.1.3.3.1-A The Contractor shall provide detailed status, description of issues, and schedule updates for each major element of the contract in a weekly status report, in accordance with CDRL No.: PM-4: OTA Weekly Status Report.

2.1.3.3.1-B The Contractor shall participate in a weekly management telecon with the

LISA Project Office to communicate programmatic and technical progress and plans of the overall contract effort. The Contractor and Government should share meeting minutes, including the action item log, and other documentation as required. The minimum Contractor attendance will consist of the Contractor Project Manager and Systems Manager or the appropriate technical lead managers as required based on the agenda. More

2.1.3.3.2 Monthly Project Status Reports and Reviews

2.1.3.3.2-A The Contractor shall support the Monthly Project Status Reviews (MPSRs), including a presentation package, in accordance with CDRL No.: PM-1: OTA Monthly Project Status Reviews (MPSR) and Monthly Technical Exchange Meetings (MTEM) Presentation Materials.

2.1.3.3.2-B The Contractor shall provide OTA monthly inputs to the LISA Project monthly Status reviews in accordance with CDRL No.: PM-2: Inputs to LISA Monthly Project Status Reviews (LISA-MPSR) Presentation Materials.

2.1.3.3.2-C The Contractor shall support the monthly OTA Schedule meeting including a presentation package in accordance with CDRL No.: PM-3: OTA Schedule Monthly Presentation Materials.

2.1.3.3.2-D The Government will conduct the MPSR and the OTA Schedule Monthly at the Government Project Office, and it can be supported remotely by the Contractor.

2.1.3.3.3 Technical Exchange Meetings and Working Groups

2.1.3.3.3-A The Contractor shall host and participate in an OTA Monthly Technical Exchange Meetings (MTEM) to discuss technical, programmatic, or other OTA work. The MTEM is nominally a two-day face-to-face meeting with the Government Telescope Management Team and other project personnel as needed at the Contractor’s facility and/or the Government facility.

2.1.3.3.3-B The Contractor shall coordinate with the Telescope Management Team to set the agenda.

2.1.3.3.3-C The Contractor shall support the MTEM, including a presentation package, in accordance with CDRL-PM-1: OTA Monthly Project Status Reviews (MPSR) and Monthly Technical Exchange Meetings (MTEM).

2.1.3.3.3-D The Contractor shall participate in Government-led working groups. Planned

Government-led working groups requiring OTA Contractor participation include, but are not limited to, a (1) Calibration and Characterization group,

(2) a systems engineering group, (3) an OTA-to-instruments interface group,

(4) an OTA-to-Spacecraft interface group, (5) an Observatory Integration and Test (I&T) group, (6) a mission operations group, (7) launch and early orbit planning group, (8) integrated mission timeline group, (9) mission readiness test group, (10) simulation/rehearsal group, (11) a safety working group, (12) a reliability working group, and various mission assurance working groups as specified in the MAR. The level of activities of each group would follow the project life cycle with-in their area of the project. The working groups may set up regular or ad hoc Technical Exchange Meetings, at the discretion of each group.

2.1.3.3.3-E The Contractor shall provide presentation materials for TEMs at least 24 hours in advance, whenever feasible.

2.1.3.3.4 Status and Planning Meetings

2.1.3.3.4-A The Contractor shall notify and allow the Government access to Contractor status and planning meetings, including daily stand-ups and tag-ups.

2.1.4 Access to Controlled Facilities

2.1.4-A The Contractor shall obtain all required access authorizations and submit any paperwork required for the Contractor to access Government controlled facilities, and other facilities, which may require the Contractor to obtain necessary NDAs.

2.1.4-B The Contractor shall allow access by the Government, or its representatives, to all

Contractor facilities used by OTA, subject to and in accordance with appropriate security controls. All NASA personnel will be U.S. persons with the understanding that certain facilities are limited to U.S. citizens only.

2.1.5 Risk Management

2.1.5-A The Contractor shall implement a risk management program in support of the OTA.

As per NASA applicable documents.

2.1.5-B As part of the risk management program, the Contractor shall prepare and submit a plan in accordance with CDRL No.: PM-12 Title: Risk Management Plan, for comparison and inclusion in the LISA Risk Management Plan.

2.1.5-C The Contractor shall summarize and present the top OTA risks in accordance with

CDRL No.: PM-1 Title: OTA Monthly Project Status Reviews (MPSR) - Monthly

Technical Exchange Meetings (MTEM) and Presentation Materials, that can be included as part of the Monthly Status Review Presentation.

2.1.6 Resource Management

2.1.6-A The Contractor shall establish, implement, and maintain a comprehensive resource management system for planning, authorizing, and controlling the total resources effort for each task and for providing timely and adequate visibility into manpower and schedule performance.

2.1.6-B The contractor shall adhere to the contractor’s standards for the resource management system in accordance with CDRL No.: PM-17 Title: Integrated Program Management Data and Analysis Report (IPMDAR).

2.1.6-C The Contractor shall implement an Earned Value Measurement System (EVMS).

2.1.6-D The Contractor shall provide an Earned Value System Management Plan in accordance with CDRL No.: PM-16 Title: Earned Value Management System (EVMS) Plan, CDRL No.: PM-15 Title: Financial Reports, and CDRL No.: PM-17 Title: Integrated Program Management Data and Analysis Report (IPMDAR). The EVMS may be implemented in accordance with the Contractor’s standard plans and policies, provided it includes use of the Monthly Contractor Financial Management Report NASA Form (NF533).

2.1.6-E The Contractor shall provide Financial Reports and Integrated Program

Management Data and Analysis Reports (IPMDARs) to the Government in accordance with the CDRL No.: PM-1: Title: OTA Monthly Project Status Reviews (MPSR) - Monthly Technical Exchange Meetings (MTEM), and the Contractor’s standard policies and procedures.

2.1.6-F The Contractor shall conduct an OTA Integrated Baseline Review (IBR) at the

Contractor facility and present data in accordance with CDRL No.: PM-20 Title:

OTA Integrated Baseline Review and Data Package. The review shall occur within the first 180 days after contract award and as needed prior to major contract modification approval for funding or work scope realignment..

2.1.6-G The Contractor shall obtain approval from the Government prior to changing the

EVMS baseline and provide all approved Budget Change Requests (BCRs) and Baseline Control Logs upon request from the GSFC project office.

2.1.6-H This item is intentionally blank.

2.1.6-I The Contractor shall establish, implement, and maintain an integrated scheduling system consistent with their corporate procedures and documented in a schedule management plan. This plan shall explain the schedule reserve strategy and burn down approach.

2.1.6-J The Contractor shall provide and maintain an IMS in accordance with CDRL No.:

PM-6 Title: Integrated Master Schedule (IMS), and CDRL No.: PM-17 Title:

Integrated Program Management Data and Analysis Report (IPMDAR).

2.1.6-K The Contractor shall identify critical procurements of long lead materials and items that must be procured in order to support the OTA schedule in accordance with CDRL No.: PM-22 Title: Long Lead Items List.

2.1.6-L The Contractor shall provide a security plan in accordance with CDRL No.: PM-23 Title: IT Security Plan

2.1.6-M The Contractor shall provide photographs and videos in accordance with CDRL No.: PM-24 Title: Photographs and Videos

2.1.7 Configuration Management

2.1.7-A The Contractor shall perform configuration management (CM) in support of the

OTA project.

2.1.7-B The Contractor shall develop and deliver the Hardware and Software Configuration

Management Plan in accordance with CDRL No.: PM-11 Title: Configuration Management Plan.

2.1.7-C The Contractor shall notify the Government of Configuration Control Board (CCB) meetings and allow Government participation at all CCB meetings.

2.1.7-D The Contractor shall maintain configuration of flight hardware and software throughout all phases of the Contract.

2.1.7-E The Contractor shall perform and document configuration verification as parts and assemblies are incorporated into higher-level assemblies and at major Project milestones.

2.1.7-F The CM system shall have a change classification and impact assessment process that results in Class I and Class II Configuration Change Requests (CCRs) being forwarded to the LISA Project in accordance with CDRL No.: PM-10 Title:

Engineering Change Proposals (ECPs), Deviations, and Waivers and CDRL No.:

SE-16 Title: Configuration Item (CI) Identification List and Computer Software Configuration Items (CSCI).

2.1.7-G For any flight item that is found to be non-compliant with the requirements of the contract, and is not reworked to be compliant, or is not replaced with a compliant item the contractor shall disposition the non-compliant flight item as described in the MAR.

2.1.7-H The Contractor shall prepare and provide, as a minimum, the following documents under configuration control:

1. CCB status shall be reported at the MPSR in accordance with CDRL No.: PM-

11 Title: Configuration Management Plan.

2. Engineering Drawings in accordance with CDRL No.: SE-6 Title: Engineering Drawings.

3. The Configuration Item Identification List (CIIL) and the Computer Software Configuration Items (CSCIs) in accordance with CDRL No.: PM-11 Title:

Configuration Management Plan. For configuration control, computer software includes: files that define firmware (i.e. VHDL), Ground Support Equipment (GSE) software, analysis software or scripts used in hardware verification, and similarly related software.

2.1.7-I The Contractor shall quantify substantive potential cost impacts of requirements changes at the OTA level, and as appropriate, qualify substantive potential cost impacts at the Payload level. The Contractor is encouraged to propose alternative approaches to defining the performance requirements or other requirements modifications at the OTA-IBR or other MTEM meetings preceding OTA- SRR/SDR, CCRs, or sooner to allow the Government time to analyze the proposed requirement modifications and provide feedback at the review.

2.1.8 Lessons Learned Reporting

2.1.8-A The Contractor shall report lessons learned throughout the project life-cycle.

2.1.8-B The Contractor shall report lessons learned at each of the reviews defined in

Section 2.1.3 and consistent with GSFC-STD-1001A or an equivalent system approved by the Government.

2.1.8-C The Contractor shall participate in a 1-hour lessons learned meeting with the

Government within 1 month after each of the following milestone reviews: OTA- CDR, OTA-PER, and OTA-PSR. The purpose of the meetings is to discuss and capture lessons learned since the last meeting, lesson context and driving events/decisions, and recommendations. The Government will facilitate these lessons learned meetings and the Government will compile an interim lessons learned report following each meeting.

2.1.8-D The Contractor shall report lessons learned after each hardware build (ETU, QM, Flight unit #1 through Flight Unit #6, and Flight spares). More details in CDRL No.: SE-14 Acceptance Data Package and Lessons Learned.

2.1.8-E The Contractor shall review and provide comments/edits to the Government-generated lessons learned interim reports.

2.2 Systems Engineering

2.2-A The Contractor shall perform systems engineering to support all OTA-related activities during all stages of development.

2.2-A.1 For costing purposes, the contractor shall consider the duration of Systems

Engineering to be until on-orbit checkout and commissioning, with reduced support after the delivery and acceptance to GSFC.

2.2-B The Systems Engineering effort shall include, but is not limited to, analysis of technical requirements, functional and performance allocation of derived requirements, traceability, definition and maintenance of all interfaces, verification of all defined, allocated, and derived requirements, systems analyses, risk management support, tradeoff analyses and trade studies, hold peer reviews, and management of systems budgets.

2.2-C This effort shall include but not be limited to the following specific activities:

1. Providing technical direction and oversight throughout all phases of the program.

2. Leading and supporting all peer reviews, project milestones, gateway and launch reviews, and program status reviews as defined in Section 2.1.3.

3. Performing all necessary OTA-level trades and risk assessments necessary to ensure the success of any design or manufacturing changes as a result of parts obsolescence, parts or materials aging, Government Industry Data Exchange Program (GIDEP) or other known parts reliability issues, or any other changes made to the original OTA design.

4. Performing all necessary coordination and analyses required to interface the OTA to the MOSA Support Structure (MSS), subject to the Interface Control Document (ICD) documents above, as described in the CDRL No.: SE-4 Title: Inputs for the MOSA Interface Control Document(s).

5. Preparing documentation and providing necessary support for reviews defined in Section 2.1.3.

6. Performing systems engineering and analysis prior to OTA delivery and in support of OTA and instrument tests at the Observatory level, the launch site, and Observatory commissioning.

7. Supporting system level technical exchange meetings as defined in Section 2.1.3.3.3, including technical issue resolution, performance verification plan buy-offs, pending CCRs, CDRL data submission review/approval status, test data review, anomaly resolution activities, and test support planning.

8. Support closing of all Government- and Contractor-assigned actions, nonconformance reports, and problem failure reports.

2.2-D The Contractor shall develop an OTA System Engineering Management Plan, in accordance with CDRL No.: SE-1 Title: System Engineering Management Plan, which describes the Contractor’s systems engineering approach and processes to be used on the LISA OTA project.

2.2.1 Requirement Analyses, Derivations, and Allocations

2.2.1-A The Contractor shall update the OTA definition, allocation, derivation, and traceability of system and subsystem requirements and the OTA verification approach, as necessary to accommodate any changes to the LISA OTA design.

2.2.1-B The Contractor shall update as necessary for the LISA OTA the analyses and simulations performed in support of technical requirements compliance demonstrations to fully establish, define, maintain, and control allocations for all required performance and design parameters.

2.2.1-C The Contractor shall report Current Best Estimates (CBE) to allocations, which include, but are not limited to, mass properties, alignment, wavefront error, line-of-sight pointing, optical throughput, and contamination. Allocations are reported as part of the Key Technical Parameters (KTP) in the CDRL No.: PM-1: OTA Monthly Project Status Reviews (MPSR) - Monthly Technical Exchange Meetings (MTEM), or upon request.

2.2.1-D The Contractor shall measure OTA wavefront error and pupil alignment in both ambient and flight-like conditions. The Wavefront Error (WFE) and changes to WFE need to be well understood and characterized.

2.2.1-E The Contractor shall measure OTA wavefront error across the field of acquisition as defined in LISA- TELE-REQ-0012 in a variety of pupil positions in both ambient and flight-like conditions. WFE and changes to WFE need to be well understood and characterized for optical performance.

2.2.1-F The Contractor shall perform and document requirements analyses and allocation tasks associated with the OTA.

2.2.1-G The Contractor shall report the mass properties per CDRL No.: SE-15 Title: Mass

Properties Report.

2.2.1-H The Contractor shall report potential changes and potential increases beyond the allocations stated in the OTARS (LISA- TELE-REQ-0012) at the same cadence as the CBE.

2.2.2 Interface Definition, Verification and Control

2.2.2-A This item intentionally left blank.

2.2.2-B The Contractor shall define the OTA side of the following interfaces:

• Spacecraft,

• MOSA Support Structure (MSS),

• Optical Bench and deliver the OTA inputs to the applicable LISA Interface Control Documents in accordance with CDRL No.: SE-4 Title: Inputs for the MOSA Interface Control Document(s).

2.2.2-C The Contractor shall deliver a ICD Compliance Matrix for the ICDs and submit them under the CDRL No.: SE-4 Title: Inputs for the MOSA Interface Control Document(s). Each unique ICD shall have a unique ICD Compliance Matrix document.

2.2.2-D Contractor participation for interface definitions shall include, but is not limited to, providing comments on analyses and reports external to the OTA, and providing independent analyses.

2.2.3 Design and Performance Verification

2.2.3-A This item intentionally left blank.

2.2.3-B The Contractor shall plan and execute a verification program to demonstrate that the OTA meets all requirements in accordance with CDRL No.: SE-10 Title:

System Performance Verification Plan and Matrix and CDRL No.: SE-5 Title:

Specification and Drawing Tree.

2.2.3-C This item intentionally left blank.

2.2.3-D The Contractor shall develop and maintain a requirements traceability tool or utilize an existing tool and use that tool to demonstrate that the OTA design meets all requirements.

2.2.3-E The Contractor shall assess the technology readiness for OTA implementation. The technology readiness requirement is that all technologies shall attain Technology Readiness Level (TRL) 6 (i.e., system or sub-system prototype demonstrated in a relevant environment) or higher at the OTA-PDR.

2.2.3-F The Contractor shall address the risks associated with late verification of the design in the risk management plan.

2.2.4 Trending

2.2.4-A The Contractor shall establish a method for trending data during OTA I&T, and Observatory level I&T.

2.2.4-B The Contractor shall coordinate with the Government the selected list of parameters to be trended in accordance with CDRL No.: SE-17 Title: Trend Analysis.

2.2.4-C The Contractor shall provide Trending Reports in accordance with CDRL No.: SE-

17 Title: Trend Analysis.

2.2.5 Models

The terminology used in this section for the description of the models subject to this SOW is defined as follows, consistent with NASA-STD-7009A w/CHANGE 1, "STANDARD FOR

MODELS AND SIMULATIONS", 2016-07-13:

Model Verification: The process of determining the extent to which a model is compliant with its requirements and specifications as detailed in its conceptual models, mathematical models, or other constructs.

Model Validation: The process of determining the degree to which a model or a simulation is an accurate representation of the real world from the perspective of the intended uses of the model.

Model Calibration: The process of adjusting numerical or modeling parameters in the model to improve agreement with a referent. Note: model correlation is understood to be equivalent terminology.

2.2.5-A The Contractor shall perform the following analyses and modeling and report on the results when completed, and in accordance with:

1) CDRL No.: SE-7 Title: Model Validation Plan

2) CDRL No.: SE-8 Title: Validated Models

3) CDRL No.: SE-9 Title: Analyses Reports

4) CDRL No: SE-10 System Performance Verification Plan and Matrix

5) CDRL No.: CC-1 Title: Optical Analytical Model

2.2.5-B The Contractor models shall meet the requirements of the Math Model Guidelines

(LISA-SPEC_XXXX).

2.2.5.1 Optical Models

2.2.5.1-A The Contractor shall develop and deliver optical models, including ray trace and stray light models.

2.2.5.1-B These models shall comply with the LISA Math Models Guideline Document and be useable throughout the OTA Implementation Phase.

2.2.5.1-C It is the intention of the Government to have these models supported and updated by the OTA vendor throughout the implementation phase, and the Contractor shall update these models at the data review of major tests in support of Model Validation and/or Model Calibration.

2.2.5.1-D The Contractor shall incorporate all applicable test results in an as-built model for each individual OTA unit.

2.2.5.1-E The Contractor shall develop and execute an Optical Model Validation Plan with concurrence from the Government.

2.2.5.1-F The Contractor shall develop and deliver the as-built models that are validated and calibrated from test(s), upon delivery of the OTAs.

2.2.5.1-G The Contractor shall develop and deliver optical performance (wavefront error, pupil placement, line-of-sight, transmission) budgets to the level needed to derive the OTA subsystem and critical component driving requirements.

2.2.5.2 Mechanical Models

2.2.5.2-A The Contractor shall develop and deliver a mechanical Computer Aided Design

(CAD) model(s).

2.2.5.2-B This model shall comply with the LISA Math Models Guideline Document and be useable throughout the OTA Implementation Phase.

2.2.5.2-C It is the intention of the Government to have this model supported and updated by the OTA vendor throughout the implementation phase, and the Contractor shall update the model at the data review of major tests in support of Model Validation and/or Model Calibration.

2.2.5.2-D The Contractor shall incorporate all applicable test results in an as-built model for

2.2.5.2-E The Contractor shall develop and execute a CAD Model Validation Plan with concurrence from the Government.

2.2.5.2-F The Contractor shall develop and deliver the as-built models that is validated and calibrated from test(s), upon delivery of the OTAs.

2.2.5.3 Finite Element Models

2.2.5.3-A The Contractor shall develop and deliver a mechanical Finite Element Model

(FEM).

2.2.5.3-B This model shall comply with the LISA Math Models Guideline Document and be useable throughout the OTA Implementation Phase.

2.2.5.3-C It is the intention of the Government to have these models supported and updated by the OTA vendor throughout the implementation phase, and the Contractor shall update the models at the data review of major tests in support of Model Validation and/or Model Calibration.

2.2.5.3-D The Contractor shall incorporate all applicable test results in an as-built model for

2.2.5.3-E The Contractor shall develop and execute a FEM Model Validation Plan with concurrence from the Government.

2.2.5.3-F The Contractor shall develop and deliver the as-built models that are validated and calibrated from test(s), upon delivery of the OTAs.

2.2.5.4 Thermal Model

2.2.5.4-A The Contractor shall develop a thermal model(s).

2.2.5.4-B This model shall comply with the LISA Math Models Guideline Document and be useable throughout the OTA Implementation Phase.

2.2.5.4-C It is the intention of the Government to have this model supported and updated by the OTA vendor throughout the implementation phase, and the Contractor shall update the model at the data review of major tests in support of Model Validation and/or Model Calibration.

2.2.5.4-D The Contractor shall incorporate all applicable test results in an as-built model for

2.2.5.4-E The Contractor shall develop and execute a Thermal Model Validation Plan, with concurrence from the Government.

2.2.5.4-F The Contractor shall develop and deliver the as-built model that is validated and calibrated from test(s), upon delivery of the OTAs.

2.2.5.5 Models - General

2.2.5.5-A The Contractor shall deliver the documentation, annotated object and…