DRAFT_SMO_SOW_4_26_16v1_R1.pdf

DRAFT STATEMENT OF WORK

SOFIA SCIENCE AND MISSION OPERATIONS CONTRACT

NNA16579196R

VERIFY THAT THIS IS THE CORRECT REVISION BEFORE USE

NASA

Ames Research Center, JA:M/S 241-1, Moffett Field, CA 94035-0001

For

NNA1679196R

REVISION #:

DATE:

CHANGE/REVISION LOG

Rev. No. Rev. Date Rev. Summary

TABLE OF CONTENTS

1.0 Introduction

1.1 SOFIA Goals and Objectives

1.2 Contract Objectives

1.3 SOW Structure

2.0 General Requirements

2.1 Training

2.2 Travel

2.3 Work Schedules

2.4 Government Installation Furnished Facilities & Property

2.5 Purchasing

2.6 Foreign National Access and Export Control

2.7 Fatigue Management

3.0 Technical Requirements

3.1 WBS 1.01 Program Management

3.1.1 General

3.1.2 Integrated Master Schedule

3.1.3 Technical, Performance, & Metrics Reporting

3.1.4 Financial Reporting

3.1.5 Audit, Reviews, and Assessment Support

3.1.6 Contract Management

3.1.7 Public Engagement

3.2 WBS 1.02 Systems Engineering & Integration

3.2.1 Systems Engineering

3.2.2 Requirements Management

3.2.3 Configuration Management

3.2.4 Data Management

3.3 WBS 1.03 Safety & Mission Assurance

3.3.1 General

3.3.2 System Safety

3.3.3 Environmental, Safety, & Health (ES&H)

3.3.4 Mission Assurance

3.3.5 Software Assurance

3.3.6 Airworthiness

3.4 WBS 1.04 Science & Technology

3.4.1 General Science & Technology

3.4.2 Grant and Contract Administration

3.4.3 Call for Proposals

3.4.4 Science Optimized Observation Cycle Flight Schedule

3.4.5 SOFIA Users Group

3.4.6 Data and Software

3.4.7 Science Paper Development Management

3.5 WBS 1.05 Science Instruments

3.6 WBS 1.06 Aircraft/Observatory Systems

3.7 WBS 1.07 Science Mission Operations

3.7.1 General

3.7.2 Mission Planning & Readiness

3.7.3 Science Instrument Support

3.7.4 Flight Operations Support

3.7.5 Flight Operations Facilities and Equipment

3.8 WBS 1.08 Reserved

3.9 WBS 1.09 Ground Systems

3.9.1 IT Security

3.9.2 Sustain Application Software

3.10 WBS 1.10 System Integration & Test

3.10.1 Integration

3.10.2 Test, Verification, and Validation

4.0 Contract Deliverable Requirements List (CDRL) summary

5.0 Appendix A – Applicable and Reference Documents

5.1 A.1 Applicable Documents

5.2 A.2 Reference Documents

6.0 Appendix B - Acronyms

7.0 Appendix C - Glossary

1.0 Introduction

The SOFIA science and mission operations contract provides NASA with an infrared science guest observer program that delivers quality science to NASA in the form of astronomical data and quality refereed science papers. NASA and the German Aerospace Center, Deutsches

Zentrum für Luft-und Raumfahrt (DLR), make available the observatory platform that this contract uses to achieve the infrared science guest observer program and the science deliverables.

SOFIA is an airborne astronomical observatory consisting of a 2.5-meter aperture telescope permanently installed in a specially modified Boeing 747SP aircraft. The observatory, with its open port telescope provided through a partnership with DLR, provides routine access to nearly all of the visible, infrared, far infrared, and sub-millimeter parts of the electromagnetic spectrum.

SOFIA's primary mission is to conduct high-quality, high-impact, cutting-edge research in astronomy, astrophysics, and planetary astronomy in a safe and cost effective manner. The observatory is able to directly incorporate new or upgraded instruments over its lifetime.

The SOFIA Program is executed jointly at two NASA centers. Flight operations and maintenance of the SOFIA aircraft are managed at the Armstrong Flight Research Center

(AFRC) Building 703 located in Palmdale, California. Program and science operations are managed at the Ames Research Center (ARC) at Moffett Field, California. The work defined by the requirements in this SOW will be performed principally at AFRC and ARC. Mission

Operations personnel typical duty stations are located in Palmdale CA.

The SOFIA Program consists of both the observatory and mission support systems. The observatory includes the Airborne System and the Science Instruments (‘Facility Instruments’ operated and maintained by the program, as well as ‘Principal Investigator’ Instruments operated and maintained by a Principal Investigator). The Airborne System consists of the Aircraft, Telescope Assembly, and Mission Command and Control System. The ground-based mission support systems include the SOFIA Science Center (SSC) at Ames, and the SOFIA Operations

Center (SOC) located at the Armstrong Flight Research Center Bld. 703 in Palmdale. The SOC provides aircraft housing and maintenance capabilities for the observatory (including the mirror coating chamber) along with science instrument preparation and checkout facilities.

SOFIA conducts approximately 100 to 120 science flights and produces nominally 800 research hours annually. This translates to nominally eight or more hours of science per 10-hour overnight flight. The flight rate is nominally three flights per week with an additional contingency flight every third week and a capability to support four flights/week planned for ~25% of the weeks in a year including deployments that require ground and flight operations during weekends. Several weeks per year are dedicated to aircraft maintenance, typically three weeks three times a year roughly evenly spaced through the year with one maintenance period in December.

The number of proposals accepted for Cycle 4, a typical year-long observation cycle, is 80 US proposals and 18 German proposals, ranging in required flight research hours from 1 hours to 80 hours. The flight observations are scheduled onto flights such that the integrated flight plans are optimized. Each flight has several observation legs ranging from 4 to 10 legs where each observation leg observes a different target.

This contract carries out an infrared science program for SOFIA and NASA by conducting a solicitation and a peer review of community-based observing proposals. Additionally, SOFIA guarantees observing time for instrument developers and conducts a limited number of discretionary investigations defined by the SOFIA Science Mission Operations Director, a Key

Person provided by this contract. This contract also plans and operates the observatory and processes all science data providing a calibrated product and support to the guest observers such that quality, impactful, and peer reviewed science products are delivered. SOFIA Guest

Observers are derived from the US call for proposals and the German call for proposals, generally referred to as US Guest Observers and German Guest Observers.

Long-term plans anticipate the observatory could operate through May 2034. SOFIA’s prime mission ends in September 2019 and is expected to enter into the NASA Senior Review process starting no earlier than 2018. It is expected that the senior review process will be repeated biennially (every two years) until the program is concluded or the mission life ends in 2034. If

NASA chooses to end the SOFIA program for any reason it is anticipated that it will take as many as three years to completely close out.

Because the SOFIA program is an international program the flight operations will continue until all international agreements are satisfied. Once the flight operations are concluded it is expected that the contract core requirements will be de-scoped and IDIQ tasks will be put in place to close out the program. It is anticipated that final closeout of the SOFIA program will take as much as two years once flight operations have ended. The contract options occur every two years to match the anticipated Senior Review process.

The SOFIA Program is organized by functions and the SOFIA Science & Mission Operations

(SSMO) Contractor supports several of the functions. The SOFIA organization chart illustrating the functions that this contract supports is shown in Figure 1. The work performed under this contract is labeled as “NASA Contractor Activity” and “Shared or Cross-Cutting Activity”.

Figure 1: SOFIA Organization Chart

The SOFIA program’s primary development activity has concluded and it is currently in the operations phase; therefore, this requirement is primarily for the execution of a science guest observer program and the delivery to NASA of high quality and impactful science. A productive science program initiates with the response to a call for proposals and culminates in the publication and dissemination of unique and impactful science results. The path in between includes, but is not limited to, the availability of relevant scientific instruments, efficient and reliable flight opportunities, prompt delivery of raw data, rapid production of science-ready data from reliable and accurate pipeline software, and sufficient funding to investigators for the analysis of the results that leads to the publication and dissemination of the final result. In addition, short-term studies and limited-development activities to increase or maintain SOFIA science capabilities will also be required.

The SSMO Contract requirements in this SOW for implementing a high-quality SOFIA science program include, but are not limited to, the following activities:

Manage the solicitation, evaluation, award, and administration of science observation proposals

Assignment of Director’s Discretionary Observation Time

Flight planning of science mission operations

Operate and maintain facility science instruments

Operate SOFIA Science and Mission Operations facilities and maintain facility equipment and IT software

Sustain SOFIA Science and Mission Operations application software

Operate the observatory in-flight and execute flight observation plans (Aircraft piloting and maintenance is not within scope of this procurement)

Process all Facility Science Instrument science data to level 3

Conduct science and public engagement

Maintain and operate the SOFIA primary mirror-coating facility

Support NASA Senior Reviews

Additional tasks will be negotiated and awarded under the IDIQ CLIN for requirements such as:.

Support science instrument development, e.g. review operations interfaces, science data pipeline interfaces, and maintenance procedures.

Participate in or conduct special science studies or surveys

Develop science instrument line replaceable spares where parts are no longer available or repair/upgrade of science instruments

Develop specialized hardware to support program requirements

1.1 SOFIA Goals and Objectives

Although the SOFIA program is currently able to meet science and mission objectives with the current system and processes, the SOFIA Program faces a number of challenges.

NASA desires to increase science community participation with SOFIA.

NASA desires to increase the scientific impact of SOFIA science.

NASA desires to increase the production of peer reviewed journal papers using SOFIA data and increase the total number of citations of SOFIA papers.

NASA desires to continuously improve SOFIA capabilities while increasing efficiency.

To meet the above challenges, NASA has defined the following goals and objectives:

Goal 1: Increase the science use of SOFIA o Objective 1: Increase the observing time over-subscription rate

Goal 2: Increase the science productivity of SOFIA o Objective 1: Increase the number of peer reviewed papers published and citations over the previous year

Goal 3: Improve the science production efficiency o Objective 1: Realize a continuous reduction in lost research hours per year o Objective 2: Reduce the cost of science and mission operations

1.2 Contract Objectives

In order to meet the above SOFIA needs, goals, and objectives, NASA is seeking a Contractor to effectively:

1. Manage, plan, and execute an infrared science program and mission operations to meet

SOFIA and NASA mission objectives including:

Perform the annual SOFIA Call for Proposals (CfP) (solicitation, evaluation, award and administration) for each yearly observation cycle, Plan flight missions for each yearly observation cycle, Provide qualified staff for the planning and execution of science mission operations consistent with a nominal and sustained flight rate of approximately 100 to 120 flights per year and nominally 3 flights per week during mission operations. Science missions fly only at night.

Support the NASA Senior Review Process

2. Provide on-board mission operations personnel:

Science Instrument Operators: Operate facility class instruments to acquire science data per awarded time of selected proposals

Mission Directors: Science/Flight/Observatory Team coordination

Telescope Operators: Science target acquisition, telescope operation

3. Execute science flight missions. Example duties are:

Flight preparation of the science instrument(s)

Pre/post flight check-out of on-board mission systems

Science flight plan development, extract science data and deliver to the SOFIA

Science Center (SSC) data storage server

Post-flight reports

4. Provide qualified staff to:

Plan and execute for contractor staff and science targets an annual six-week southern hemisphere deployments to Christchurch, New Zealand. (NASA is responsible for overall planning for the deployment)

Operate and maintain SOFIA’s suite of facility science instruments, Process and calibrate all facility instrument science data, and deliver to InfraRed

Science Archive (IRSA)_

Sustain pipeline software for facility science instruments

Provide SOFIA Guest Observer support

Maintain reflectivity of the SOFIA Primary mirror (routine cleanings, re-coat if necessary)

Maintain, sustain, and operate all science and mission operations equipment, software, and facilities that are used in performing the SOFIA mission. Examples include: Observatory Simulation Labs,, Mirror Coating Facility, Flight Planning and

Scheduling Tools, Science Instrument Laboratory

Provide NASA with science and mission operations reports that assess performance to requirements

Provide support for observatory improvement testing and observatory check-out

Perform SOFIA science outreach and public engagement functions

1.3 SOW Structure

NASA has overall responsibility for managing the SOFIA Program. The Contractor is responsible for assisting NASA per the requirements in this SOW, as defined in Sections 2 and 3.

This contract is organized based on the Work Breakdown Structure (WBS) shown in Figure 2.

The requirements in this SOW are structured according to that WBS. General requirements are defined in Section 2 and technical requirements are defined in Section 3. Requirements for operation of software and hardware are included in Sections 3.4 and 3.7. Requirements for maintenance of software and hardware are included in Sections 3.6 and 3.9. Due to the unique nature of pipeline software, science data processing software that has both maintenance and operations requirements are located in Section 3.4. Upgrades of software and hardware capabilities or redesign due to obsolescence, or any short-term maintenance requirements, will be typically IDIQ tasks.

In the execution of these requirements, the Contractor will work with the SOFIA Program concerning the overall strategy, planning, and conduct. The contractor is expected to coordinate science and operations activities with NASA, NASA support contractors, DLR, and DLR’s support contractor.

Figure 2: SOFIA Science and Mission Operations Contractor Work Breakdown Structure

SOFIA Program

SOFIA Science and Mission Operations Contractor

Section 2.0 General

Requirements

Mission Assurance

Program

Management

Science

Instruments

Mission

Operations

Ground Systems

Systems

Integration & Test

System

Engineering & Integration

Technology

Aircraft/

Observatory Systems

Reserved

A rationale statement, CDRL list, and a timing metric are included for many of the requirements, in order to better communicate the Government’s intentions, as well as provide additional information the contractor needs to understand and scope effort of the activity or deliverable associated with the requirement. From a contracting standpoint, the information in these statements does not constitute a binding obligation and that language (in italics) will be removed from the contract documents.

2.0 General Requirements

The following general requirements apply to all functions of the contract. These requirements encompass training, travel, work schedules, government furnished equipment, and procurement.

2.1 Training

The following section contains the general training requirements for SOFIA Operations.

2.1.1 The Contractor shall provide and maintain a skilled workforce with expertise and training necessary to meet the requirements in this SOW and document this with an annual Staffing Plan, CDRL 200001.

CDRL: Yes

2.1.2 The Contractor shall train and annually certify mission operations personnel supporting both ground and flight operations per the SOFIA Mission Operations

Training Plan SCI-US-PLA-PM19_200E provided by NASA per CDRL 20002.

CDRL: Yes, Personnel Certification Status Report

2.2 Travel

2.2.1 The Contractor shall manage mission-essential travel of Contractor employees in accordance with the 41 Code of Federal Regulations (CFR) Chapters 300 through 304 and Federal Acquisition Regulation (FAR) 31.205-46.

Rationale: The work defined in this contract is expected be performed principally at the NASA-Armstrong Flight Research Center, Palmdale, California and Ames

Research Center, Moffett Field, California. Mission Operations personnel typical duty stations are located in Palmdale CA. and include activities such as Flight

Personnel, Mirror Coater Operations, Instrument Maintenance, and Observatory

Data Cache Operations. Science planning typical duty stations are located at ARC and include activities such as Scientist Operations, Science Data Pipeline, Mission

Planning, Help Desk, and Solicitation and Evaluation of Science Observation

Proposals. During the life of the contract, Contractor employees will be required to travel to off-site locations to receive approved training and to perform requirements defined in the contract at deployed locations in support of flight operations. The

Contractor is expected to exercise due diligence to avoid unnecessary travel and to reduce costs.

CDRL: No

2.2.2 The Contractor shall submit requests for foreign travel and conference attendance to the Contracting Officer (CO) or Contracting Officer Representative (COR), as directed, for approval per CDRL 20003.

CDRL: Yes, Contractor foreign travel requests

2.3 Work Schedules

2.3.1 The Contractor shall perform the work on this contract in accordance with the NASA

SOFIA (Program Management Board) PMB approved program schedule.

CDRL: No

2.4 Government Installation Furnished Facilities & Property

2.4.1 The Contractor shall locate personnel carrying out the requirements in this SOW in office and laboratory space provided by the Government at SOFIA Program facilities located at both ARC and AFRC/Building 703 (Palmdale), or shall provide a justification to the COR for locating contractor staff offsite.

CDRL: No

2.4.2 The Contractor shall comply with the requirements in SOF-DA-PLA-PM21-1086, SOFIA Program Safety and Mission Assurance Plan, section 3.2, which states, "All work on the SOFIA Program, while at the Building 703, shall follow Armstrong industrial safety and occupational health procedures (i.e. DCP-S documents). All work at ARC shall follow Ames industrial safety and occupational health procedures

(i.e. APR documents). If the SOFIA Observatory is deployed, DCP-S documents or equivalent international occupational safety standards (if more stringent) shall apply."

Rationale: This requirement helps ensure the Contractor understands and complies with requirements and limitations associated with the use of government provided facilities.

CDRL: No

2.4.3 The Contractor shall provide mission-essential equipment, tools, and supplies required for conducting the requirements in this SOW, if not supplied by the

Government and subject to requirement 2.5.1.

Rationale: The determination of whether property is mission-essential will be solely at the discretion of the Contracting Officer.

CDRL: No

2.4.4 The Contractor shall provide non-mission-essential equipment, tools, office supplies, and office equipment required for conducting the requirements in this SOW, if not supplied by the government.

Rationale: Some office equipment, such as office furniture, may be available from the government. The determination of whether property is mission-essential or not will be solely at the discretion of the COR.

CDRL: No

2.4.5 The Contractor shall use, when available, Government furnished office equipment and supplies (including, copiers, and normal office supplies) for the Contractor’s onsite administrative and management staff.

Rationale: Program policy. Standard office furniture, telephone instruments, and

LAN connections for the Contractor’s onsite staff will be supplied from the

Government’s office furniture and equipment pool.

CDRL: No

2.4.6 The Contractor shall establish and maintain a Government Furnished Property (GFP) management process and deliver that process to the Government within 90 days of contract award per CDRL 200004.

Rationale: This process is needed to help ensure all GFP is used appropriately and from which the Government can accurately determine the location of every item.

CDRL: Yes, Contractor GFP Management process

Metrics/timing: Within 90 days of contract award

2.4.7 The Contractor shall use compatible email software and meeting scheduling software with the software the SOFIA program is using

Rationale: SOFIA is a highly integrated operational program and requires tight coordination across all members of the program. Compatible Email and meeting scheduling software is essential to this coordination. Currently SOFIA uses

Microsoft Outlook.

CDRL: No

2.4.8 The contractor shall use the Government Local Area Network (LAN) necessary to perform the work defined herein.

CDRL: No

2.5 Purchasing

2.5.1 The Contractor shall submit purchase requests to the Government for approval prior to the purchase of equipment or services over $100,000 value per CDRL 20005.

Rationale: It is expected the Contractor will need to make purchases of goods and services on the behalf of the Government in carrying out the requirements as defined by the requirements in this SOW. This includes mission-essential tools, equipment, or software needed to conduct the requirements in this SOW not already being supplied by the Government. The determination of whether the requested property is mission-essential will be solely at the discretion of the Contracting Officer Representative. As part of their contract oversight function, the Contracting Officer or COR may request copies of the cost estimates and/or quotations for any purchase or subcontract made on the contract regardless of value.

CDRL: Yes, Purchase requests

2.6 Foreign National Access and Export Control

2.6.1 The contractor shall adhere to the SOFIA Program Export Control Plan (SOF-AR-

PLA-PM91-2020), NPR 2190.1 NASA Export Control Program Operations Manual, and other Program, Center, and Agency policies for Export Control.

Rationale: The SOFIA Guest Observer (GO) program and southern hemisphere deployments are routine operations that include foreign national access to facilities and networks. This requirement includes, among other things, control of foreign national access to sensitive technology, data, or facilities, export classification of foreign destination shipments, and periodic export control training of contractor staff.

CDRL: No.

2.6.2 The contractor shall adhere to NPR 1600.1, NASA Security Program Procedural

Requirements, NPR 1600.4, Identity and Credential Management, and program, center, and agency policies for foreign national access for badging, physical and logical access, escort/no escort privileges, and security and access control planning of personnel; including the following:

a) Access of foreign national contractor staff to NASA facilities is subject to approval by NASA,

b) Foreign Nationals from non-designated countries, who are directly supporting the SOFIA program on a long-term basis, can be granted UNESCORTED access during Normal Business Hours upon completion of their background check and approval of their access control plan. Note: Unescorted access at any one facility does not necessarily provide unescorted access to any other facility.

c) All other Foreign Nationals must be ESCORTED while visiting NASA AFRC or ARC.

d) As required, arrangements can be made for NASA civil servant or contractor escort of Foreign Nationals in B-703 outside normal business hours.

e) Unescorted access at any one facility does not necessarily provide unescorted access to any other facility.

Rationale: The SOFIA Guest Observer (GO) program, SOFIA partner, and southern hemisphere deployments are routine operations that include foreign national access to facilities and networks. Access of Foreign National visitors and employees requires special approval. Normal Business Hours (excluding holidays):

AFRC M-F 6:00 am to 6:00 pm

B-703 Palmdale M-F 6:00 am to 12:00 am (midnight) and

Sat 6:00 am to 5:00 pm

ARC M-F 6:00 am to 6:00 pm

CDRL: No

2.6.3 The contractor shall provide export control records for all international destination shipments per the SOFIA Program Export Control Plan (SOF-AR-PLA-PM91-2020) and NPR 2190 as defined in CDRL 200006.

Rationale: The SOFIA program operations involve southern hemisphere deployments that include export classification of foreign destination shipments. The contractor needs to document, provide, and maintain export control records for all international destination shipments per the SOFIA Program Export Control Plan (SOF-AR-PLA-

PM91-2020) and NPR 2190.

CDRL: Export Control Records, including Export Control Classification Number

(ECCNs), for all international destination shipments.

2.7 Fatigue Management

2.7.1 The contractor shall adhere to the requirements documented in the SOFIA Fatigue

Management Policy (DPL-7900.3-002).

Rationale: The SOFIA Fatigue Management Policy is designed to provide a guideline to minimize the impacts of mission operations personnel required to work nights and weekend in support of the flight or test schedules. This requirement applies to all operations personnel.

3.0 Technical Requirements

This section describes requirements that apply to specific WBS elements of the contract, with the numbering for each section corresponding to the applicable WBS nomenclature. Within each section each requirement has a unique number. The second digit of the number corresponds to the applicable WBS, and the third number is assigned sequentially within that WBS.

The primary focus of this contract is delivery of an infrared science guest observer program including the operation of a government observatory. Development of hardware and software requirements are limited and will be assigned and negotiated through the IDIQ task order process.

Requirements for hardware and software development are included in this SOW but may not be applicable if no development activities are assigned.

3.1 WBS 1.01 Program Management

The Contractor is responsible for providing the management and administrative expertise necessary to plan and control the work defined within this Statement of Work. Project management includes the planning, organizing, directing, coordinating, controlling, monitoring and managing in order to accomplish overall Project objectives. This effort also includes resource allocation, cost estimation and budgeting, schedule control; performance measurement;

contract/subcontract and financial management; associate Contractor liaison; organizational and staff management; reporting; and other project management and control functions.

3.1.1 General

3.1.1.1 The Contractor shall manage all work activities consistent with the SOFIA Program organizational structure.

Rationale: The contract activities are integrated across the program and contractor management must interface with NASA management at the appropriate level to provide efficient coordination.

CDRL: No

Metrics/timing: N/A

3.1.1.2 The Contractor shall provide a Management Plan (MP) per CDRL 310100 and update as required.

CDRL: Yes

Metrics/timing: Initial plan submitted with proposal and incorporated into contract at award, updated as required

3.1.2 Integrated Master Schedule

3.1.2.1 The Contractor shall provide inputs to the SOFIA Program concerning contractor schedules, status, and changes to the SOFIA Integrated Master Schedule (IMS) per

CDRL 310101.

Rationale: The SOFIA Science Program Integrated Master Scheduling (IMS) is a major tool used to manage project activities across the program of which this contract is a part. . These task working schedules and milestones support the milestones in the SOFIA IMS. Working schedules include all significant design, submittal, fabrication, procurement, and work activities; plus, any constraints, including constraints outside of this contract which may impact work on the contract.

CDRL: Yes, Contractor inputs to the IMS

Metrics/timing: Monthly or when significant changes occur

3.1.3 Technical, Performance, & Metrics Reporting

3.1.3.1 The Contractor shall deliver and present a monthly report on the technical, schedule, operations status and risks at the Program Monthly Review (PMR) per CDRL

310102.

Rationale: The Contractor participates in the SOFIA Program standard monthly review to present status of contract performance. The Program Monthly report is organized by the Program organizational structure. Contract monthly report content is provided to the organizational leads for inclusion into the monthly reports. For example, monthly reports on contract content supporting Mission Operations activities will be communicated to the Observatory Operations Director for inclusion in that section of the PMR.

CDRL: Yes, PMR Report on the technical, schedule, operations status and risks

Metrics/timing: Monthly

3.1.3.2 The Contractor shall provide assigned performance metrics, as defined in the Program

Metrics Document SOF-AR-PLA-PM17-2079, for input into the program metrics database per CDRL 310103.

Rationale: Program performance Metrics are collected by the program into a single repository. Specific performance data or metrics are assigned to the contractor to be tracked and input into the program metrics database by the contractor. Metrics are used for Program Status, contractor status, and to support programmatic decisions and planning.

CDRL: Yes, Assigned performance metrics

Metrics/timing: As defined in CDRL

3.1.4 Financial Reporting

3.1.4.1 The Contractor shall deliver a Financial Monthly Report (FMR) per CDRL 310104.

Rationale: This contract represents a major portion of the total program budget and requires periodic reporting to the SOFIA Program.

CDRL: Yes, FMR

Metrics/timing: Monthly

3.1.4.2 The Contractor shall present a summary of the FMR at the Program Contract

Financial Review (PCFR) per CDRL 310105.

Rationale: Ensure financial status is clearly communicated to the SOFIA Program in a forum restricted to only Contractor and NASA.

CDRL: Yes, PCFR FMR presentation

Metrics/timing: Monthly

3.1.4.3 The Contractor shall provide an annual update to the SOFIA Program 5-year budget plan per CDRL 310106.

Rationale: This update is needed to NASA’s annual budget formulation cycle (PPBE).

The update needs to include budget and workforce estimates by FY.

CDRL: Yes, 5-year budget recommended updates – minimum 2 deliveries - draft and final integrating any updated Program guidance.

Metrics/timing: Annually, two iterations

3.1.5 Audit, Reviews, and Assessment Support

3.1.5.1 The Contractor shall provide requested cost, schedule, technical, and risk information to the SOFIA Program needed to inform audits, reviews, and assessments per the

CDRL 310107.

Rationale: SOFIA is a Congressionally reported program in the NASA Science

Mission Directorate (SMD) Portfolio, and as such is generally subject to independent reviews from internal SMD or external Government Accountability Office (GAO) and

NASA Inspector General (IG) sources; the Contractor will need to support these reviews for content in the scope of this SOW. Included in these reviews are NASA

Senior Reviews that may start in 2018 and may reoccur every two years.

CDRL: Yes, Documentation and presentations of requested cost, schedule, and technical information

Metrics/timing: Average of once per year

3.1.6 Contract Management

3.1.6.1 The Contractor shall notify the COR of contract issues that may have impacts to meeting requirements and schedules as soon as they are identified.

Rationale: Contractor scope of work and staff are integrated into the larger programmatic organization – notifications help ensure clear and timely communication with the COR to prevent impacts to completing work and meeting project requirements and schedules. Issues that are beyond the ability of the COR to resolve will be addressed by the Contractor Oversight Board (see next requirement).

CDRL: No

Metrics/timing: As needed

3.1.6.2 The Contractor shall participate as a member of the Contract Oversight Board (COB) meeting quarterly or as requested by either NASA or the Contractor.

Rationale: The COB is a meeting designed to increase communication and government insight relative to contract performance. Particular emphasis will be applied toward resolving issues that are critical for the success of the SOFIA science mission.

CDRL: No

Metrics/timing: Quarterly or as requested by either NASA or the Contractor.

3.1.6.3 The Contractor shall input into the Program risk data base any risks to the ability of the SOFIA Program, including the contractor, to meet Program needs, goals, objectives, and risks to successful science and mission operations or the safety of any personnel regardless whether or not the issue is related to the Contractor's activities.

Rationale: As integrated aspect of overall program operations, the Contractor needs to be involved in identification and management of SOFIA Program risks.

CDRL: No

Metrics/timing: As needed.

3.1.6.4 The Contractor shall submit and present to the Program Management Board (PMB) for review all agreements, Memorandum of Understanding (MOUs), or commitments for providing unplanned support to SOFIA partners, partner subcontractors, or collaborators per CDRL 310108.

Rationale: The Contractor is the primary point of contact for many internal and external customers and program participants, but cannot commit the program without review through the Program Management Board and approval of any required waivers. This ensures NASA management concurs with commitments made on behalf of the program. Therefore, the Contractor needs to provide draft copies of agreements, MOUs, or commitments through the PMB for program review, including rationale for any waivers or deviations. NASA does not sign the MOUs or agreements, the agreements are between the contractor and the partner in the agreement.

CDRL: Yes, PMB Presentation on unplanned support in agreements, MOUs, and commitments

Metrics/timing: As needed.

3.1.7 Public Engagement

3.1.7.1. The Contractor shall develop and provide to the SOFIA Program for approval a

Program Public Engagement Plan per CDRL 310109.

Rationale: This plan addresses how SOFIA can be presented to the public to communicate the unique and inspirational attributes of airborne astronomy. Activities documented in the plan include establishing partnerships with science museums, public events, and other informal outreach specialists, planetaria, and industry. The plan also outlines how social media will be used as part of the Public Engagement program. The plan also needs to address how the Contractor plans to meet all the public outreach requirements in this section.

CDRL: Yes, Public Engagement Program Plan

Metrics/timing: Once within 90 days of contract award and updated annually.

3.1.7.2 The contractor shall chair and convene, every other week, the SOFIA

Communications Working Group (SCWG) made up of representative of the ARC

Public Affairs Office (PAO), AFRC PAO, NASA Headquarters (HQ) PAO, SOFIA

Program and SOFIA German partner PAO.

Rationale: The SCWG is the primary meeting that coordinates all public outreach across ARC, AFRC, HQ, the German partner, and the contractor such that the same message is being communicated with the public. It is also the meeting where reviews of publications are coordinated by the Centers' and HQ PAO offices. This meeting also is used to review potential non-program flight participants such as members of the press.

CDRL: No

Metrics/timing: Every other week

3.1.7.3 The contractor shall prepare and deliver to the SOFIA Program minutes of the monthly SCWG per CDRL 310110.

Rationale: Documentation of the meeting minutes is required to ensure coordination across the participants.

CDRL: Yes, SCWG minutes

Metrics/timing: Every other week, less than three (3) working days after the meeting

3.1.7.4 The contractor shall convene every other week a Public Engagement (PE) status meeting with the ARC PAO, AFRC PAO, HQ PAO and the SOFIA Program.

Rationale: This meeting statuses NASA management on the SOFIA public engagement effort.

CDRL: No

Metrics/timing: Every other week, alternating with the SCWG.

3.1.7.5 The contractor shall maintain the SOFIA Program webserver and website in compliance with NASA standards identified in http://communications.nasa.gov/content/nasa-comm-guidelines, https://www.nasa.gov/accessibility/section508/sec508, and ARC PAO Policy

“NASAInfoReleasePolicy-2015MAR”, per CDRL 310111.

Rationale: The contractor needs to maintain the SOFIA web site that includes information for public engagement and the science community to inform both groups on SOFIA activities, accomplishments, and ways that the community can become involved in SOFIA's mission. For the science community, the SOFIA web site provides a mechanism for keeping the users informed concerning the SOFIA program and status of the current and upcoming cycle schedule events.

CDRL: Yes, SOFIA Program webserver and website

Metrics/timing: On going

3.1.7.6 The contractor shall create and, after receiving approval from NASA, publish articles, web features, and press releases to inform the public of SOFIA activities, accomplishments, and SOFIA's mission per CDRL 310112.

Rationale: Other mechanisms, such as social media, may also be employed as identified in the contractor Public Outreach Plan. These articles, etc. will be also be included on the web site.

CDRL: Yes, publish articles, web features, and press releases

Metrics/timing: As required

3.1.7.7 The contractor shall coordinate their public outreach activities with the HQ PAO, ARC PAO, AFRC PAO and SOFIA partners prior to public release and publication of articles, web features, and press releases.

Rationale: This requirement helps ensure a coordinated and unified public outreach effort across the SOFIA program.

http://communications.nasa.gov/content/nasa-comm-guidelines

CDRL: No.

Metrics/timing: As needed

3.2 WBS 1.02 Systems Engineering & Integration

The SOFIA Program has a well established Systems Engineering framework and process, and the Contactor is expected to provide the personnel and technical expertise to support the integrated engineering for contractor managed or supported systems. This element includes work to define observatory and ground systems through the integrated planning and control of the technical program, including design engineering, software engineering, specialty engineering, system architecture development, integrated test planning, system requirements writing, configuration control, technical oversight, control and monitoring of the technical program and risk management activities. Documentation products include Mission/System

Requirements Document (MSRD); interface control documents (ICDs); Risk Management

Plan and Verification and Validation (V&V) plan. Excludes any design engineering costs

This section addresses the technical and management efforts the contractor is required to perform in support of the systems engineering and engineering of the SOFIA Program.

3.2.1 Systems Engineering

3.2.1.1 The Contractor shall develop systems in compliance with NPR 7123.1B Systems

Engineering Processes and Requirements.

Rationale: NPR 7123.1B is an Agency level policy that documents processes and requirements based on lessons learned and best practices that the contractor needs to comply with when the SOFIA Program tasks the Contractor to develop a new system or upgrade existing observatory instruments, facilities, or ground support equipment

(GSE).

CDRL: No

Metrics/timing: As part of system development or upgrade as directed by NASA.

3.2.1.2 The Contractor shall maintain existing systems listed in Appendix D of this SOW to be in compliance with NPR 7123.1B Systems Engineering Processes and

Requirements.

Rationale: NPR 7123.1B is an Agency level document that documents processes and requirements based on lessons learned and best practices and applies when changes are made to an existing system as a result of a discrepancy report to repair or maintain an existing system.

CDRL: No

Metrics/timing: On going

3.2.1.3 The Contractor shall develop new software in compliance with the SOFIA Program

Software Management Plan (SMP) SOF-DA-PLA-PM20-2011.

Rationale: The SOFIA Program Software Management Plan implements the requirements contained in NPR 7150.2B NASA Software Engineering Requirements.

The SMP documents processes and requirements based on lessons learned and best practices that the contractor needs to comply with when the SOFIA Program tasks the Contractor to develop or upgrade existing software. Development of any new software will be per a separate task order from NASA (IDIQ).

CDRL: No.

Metrics/timing: As part of software development or upgrade as directed by NASA

3.2.1.4 The Contractor shall sustain existing software listed in Section J in compliance with the SOFIA Program Software Management Plan (SMP) SOF-DA-PLA-PM20-2011.

Rationale: The SOFIA Program Software Management Plan implements the requirements contained in NPR 7150.2B NASA Software Engineering Requirements.

The SMP documents processes and requirements based on lessons learned and best practices that the contractor needs to comply when the Contractor needs to make changes to the existing software as a result of a discrepancy report to repair or maintain the existing software.

CDRL: No

Metrics/timing: On going

3.2.1.5 The Contractor shall deliver documentation that demonstrates compliance with entrance and success criteria, as determined by NASA, for each technical review

(SRR, PDR, CDR, and TRR) prior to scheduling the review and proceeding to the next technical review per CDRL 310202.

Rationale: NPR 7123.1B defines entrance criteria that must be met before scheduling each of these technical reviews as well as success criteria that must be met before successfully completing the review. The SOFIA Program will tailor these criteria depending on the type of product/system being developed and Program needs. This requirement applies to sustainment of existing hardware and software, as well as the development of any new hardware or software, or upgrades or modification to existing hardware or software as directed by NASA per a separate task order (IDIQ).

CDRL: Yes, Documentation for Technical Reviews

Metrics/timing: For each scheduled review

3.2.2 Requirements Management

3.2.2.1 The Contractor shall flow down Program requirements and derive child requirements for any SOFIA Program directed hardware or software development activities for which the contractor is responsible.

Rationale: The SOFIA Program has baselined level 1 requirements for systems and software that will need to be allocated by the contractor to hardware and software systems the government tasks the contractor to develop. The contractor will then need to derive children requirements for the system or software under development for the allocated requirements per the processes defined in NPR 7123.1B and NPR

7150.2B. This requirement applies to the development of any new hardware or software, or upgrades or modification to existing hardware or software as directed by

NASA per a separate task order (IDIQ).

CDRL: No

Metrics/timing: For each system the contractor is tasked to develop

3.2.2.2 The Contractor shall develop and deliver to the SOFIA Program (for approval and baseline) all requirements generated and derived as part of a system or software development upgrade, or modification task per CDRL 310201.

Rationale: NASA is the approving authority for all system and software developed as part of this contract. As such, they need to approve for baseline all requirements prior to the system being built or the software being coded. Currently, there are no

SOW requirements for the contractor to develop any new systems or software. This requirement applies to the development of any new hardware or software, or upgrades or modification to existing hardware or software as directed by NASA per a separate task order (IDIQ).

CDRL: Yes, New system and software requirements (IDIQ)

Metrics/timing: As needed as part of any system or software development effort.

3.2.2.3 The Contractor shall manage technical requirements for SOFIA hardware and software systems that they are responsible for, including those in Appendix D.

Rationale: The Contractor needs to ensure all technical hardware and software requirements managed within the SOFIA Program are accurate (correct) and trace to a parent or source. When changes are approved, the contractor needs to update the baselined set of requirements to ensure they are always kept current. This requirement is intended to ensure accuracy, traceability, and currency of requirements the contractors is responsible.

CDRL: No

Metrics/timing: On going

3.2.3 Configuration Management

3.2.3.1 The Contractor shall maintain all baselined products and deliverables in compliance with the SOFIA Program Configuration Management Plan (CMP), SOF-DF-PLA-

PM03-1054. Any changes to the baselined products must be submitted to the appropriate NASA control board for approval per the process in the CMP.

CDRL: No

Metrics/timing: On going

3.2.3.2 The Contractor shall document and resolve discrepancies in accordance with the

SOFIA CMP, SOF-DF-PLA-PM03-1054.

Rationale: The SOFIA CMP defines the process the contractor must follow to document discrepancies in a Discrepancy Report (DR) and resolve these discrepancies. Resolving discrepancies includes troubleshooting, identifying the problem, recommending a resolution to the discrepancy, implementing the approved resolution, and closing out the DR.

CDRL: No.

Metrics/timing: As needed

3.2.4 Data Management

3.2.4.1 The Contractor shall store all technical and configuration controlled SOFIA Program related documentation in the SOFIA Program-specified data repository.

CDRL: No

Metrics/timing: On going

3.2.4.2 The Contractor shall comply with the SOFIA Data File Numbering Schema (DFNS) document SOF-AR-DEF-PM91-2023.

Rationale: The SOFIA Data File Numbering Schema defines the process for requesting document numbers and templates for how the numbers will be appear on documents.

Metrics/timing: On going

3.3 WBS 1.03 Safety & Mission Assurance

Safety & Mission Assurance includes the technical and management efforts of directing and controlling the safety and mission assurance elements of the program. This element includes design development, safety assessment, review and verification of practices and procedures, and relevant mission success criteria intended to assure the delivered systems meet performance requirements and function for their intended lifetimes. The Contractor will perform Safety & Mission Assurance (S&MA) functions per the requirements in this section.

3.3.1 General

3.3.1.1 The Contractor shall develop and deliver to the SOFIA Program, for approval, a

S&MA Plan (PM21) per CDRL 310301 that documents how the Contractor will comply with the safety, quality, and software assurance requirements defined in:

SOF-DA-PLA-PM21-1086, SOFIA Program Safety and Mission Assurance Plan

SOF-NASA-PLA-PM21-2089, SOFIA Safety Plan (SSP)

SOF-NASA-PLA-PM21-2090, SOFIA Quality Plan (SQP)

SOF-NASA-PLA-PM21-2091, SOFIA Software Assurance Plan (SSAP).

Rationale: The intent is not for the contractor to copy and paste the NASA requirements in their plan, but rather document the contractors approach for meeting the NASA requirements. The contractor may divide their Plan into smaller documents as long as all NASA safety and mission assurance requirements in the listed Program plans are covered.

CDRL: Yes, Contractor S&MA Plan (PM21)

Metrics/timing: Once within 90 days of contract award.

3.3.1.2 The Contractor shall provide emergency response to a safety incidents, as required, involving personnel within a facility managed and operated by the contractor per the

SOFIA Mishap Plan SOF-DF-PLA-OP05-2000.

CDRL: No

Metrics/timing: As needed

3.3.1.3 The Contractor shall provide requested access, and technical and risk information to

NASA as needed for audits, reviews, inspections, and assessments.

Rationale: NASA’s safety and mission assurance organization is required to perform surveillance of this contract concerning contractor activities in any NASA furnished facility. As an example NASA may develop a Quality Assurance Surveillance Plan

(QASP) to document the activities of this function, e.g. Contractor QASP for SOFIA instrument laboratories/ facilities and procedures for work that is performed on instruments and equipment that will be installed on the aircraft and removed from the aircraft. This requirement ensures the Contractor will support the NASA surveillance activities associated with any requirement in the scope of this SOW.

CDRL: No

Metrics/timing: As needed

3.3.1.4 The Contractor shall allow the government access, when requested, to contractor or subcontractor facilities in support of government inspection of procurement, production, and manufacturing of products the contractor is tasked to provide.

Rationale: NASA’s safety and mission assurance organization may be required to perform inspections during the production or manufacturing of products to be delivered to the…