PF2_-_RFP_-_Attachment_1-Statement_of_Work_(SOW).pdf

i

US AIR FORCE SPACE AND MISSILE SYSTEMS CENTER (SMC)

MILITARY SATELLITE COMMUNICATIONS (MILSATCOM)

SYSTEMS DIRECTORATE

Attachment 1

COMMERCIAL SATELLITE

COMMUNICATIONS (COMSATCOM)

Pathfinder #2

STATEMENT OF WORK

FA8808-17-R-0004

DATE: 23 JUNE 2017

Issued By Air Force Space and Missile Systems Center

MILSATCOM

483 N. Aviation Blvd

El Segundo, CA 90254 ii

Table of Contents

1 OVERVIEW

1.1 Terminology

1.2 Classification

1.3 Period of Performance

2 GENERAL DESCRIPTION

2.1 USG Transponder(s)

2.2 User Description

2.3 Coverage Area

2.4 Communication Connectivity

3 STATEMENT OF WORK (SOW)

3.1 USG Transponder(s)

3.2 Cybersecurity Requirement

3.3 Spectrum/Frequency Policy Compliance

3.4 Incidental Support (Contract Line Item Number (CLIN) 0003 and CLIN 0004)

3.4.1 Network Operations Center and Personnel Staffing

3.4.2 Transmission Plans

3.4.3 Disposal Plan

3.4.4 Host Nation Agreements (HNAs) and Approvals

3.4.5 Reporting

3.5 Guarantee of Capability

3.6 System Safety

3.7 Security for Government Financing

3.8 Deliverables

4 AEROSPACE FFRDC ENABLING REQUIREMENT

Appendix 1

TAB 1: Pathfinder EMI/RFI Reporting Checklist

1 OVERVIEW

This Statement of Work (SOW) establishes the requirements for the Pathfinder #2 (PF2) Ku-Band

Commercial Satellite Communications (COMSATCOM) procurement.

The Space and Missile Systems Center (SMC), Military Satellite Communications

(MILSATCOM) Systems Directorate, Los Angeles Air Force Base, California is acquiring pre-launch commercial transponder(s). The intent is to demonstrate the process of procuring pre-launch transponder(s) as part of a series of risk mitigation steps towards a future innovative, affordable procurement of long term COMSATCOM services.

The United States Air Force’s goal is to leverage new methods to buy COMSATCOM services to satisfy warfighter requirements while providing significant cost savings when compared to the prevailing leasing methods used today. SMC has devised a series of COMSATCOM pathfinders to address a number of risks as the Air Force learns how to buy and contract for more affordable, higher performing and more mission assured/flexible COMSATCOM services. The pathfinders are sequential and flexible to allow for inclusion of lessons learned from previously executed pathfinders or new information not previously known or available.

In 2014, a previous pathfinder named Pathfinder #1 (PF1), demonstrated how to buy and contract for on-orbit transponder(s) supporting a specific Combatant Command (COCOM). PF1 demonstrated investment based affordability, resolving commercial radio spectrum risks, while highlighting need for better coverage flexibility. For PF2 the primary objective is to demonstrate how to acquire a number of pre-launch transponder(s). This will demonstrate additional investment based affordability techniques while demonstrating minor design influence. The satellite operator will continue to own and operate the satellite hosting the United States Government (USG) transponder(s) in accordance with any required International Telecommunication Union (ITU), Federal Communications Commission (FCC), national and foreign regulations.

1.1 Terminology

Requirements are identified by a numbered Requirements Identifier (REQID). The REQID appears at the beginning of each requirements statement within [brackets] and in boldface [SOW

-xx].

1.2 Classification

This acquisition and associated solicitation documents are unclassified.

1.3 Period of Performance

Unless otherwise stated, all requirements apply for the duration of the period of performance (PoP) of the contract. The PoP for this contract begins upon contract award and expires fifteen (15) years following completion of in-orbit test (IOT) for the space vehicle on which the United States

Government (USG) Transponder(s) reside. If IOT is never completed, then the period of performance expires fifteen (15) years after the scheduled IOT date in accordance with paragraph

3.4.5 below.

2 GENERAL DESCRIPTION

A general description of the system, including the users, required coverage area, and communication connectivity, are summarized below.

2.1 USG Transponder(s)

The Government intends to procure Ku-band Fixed Satellite Services (FSS) commercial pre-launch transponder(s) for access to COMSATCOM services. The USG Transponder(s) shall provide service over the contiguous United States. The USG shall own the transponder(s) for the lifetime of the satellite on which they are carried. The contractor shall operate and maintain the satellite, to include all support for the hosted USG Transponder(s).

2.2 User Description

The USG transponder(s) shall be available for use by any USG entity as directed by the USG entity that will request COMSATCOM services over said transponders.

2.3 Coverage Area

The USG Transponder(s) shall provide coverage to all points within the contiguous United States.

2.4 Communication Connectivity

The USG transponder(s) shall provide continuous service for twenty four (24) hours per day and seven (7) days per week for the PoP. Operational availability is measured over each thirty (30) day period and shall be no less than 99.97%.

3 STATEMENT OF WORK (SOW)

3.1 USG Transponder(s)

[SOW-01] The Contractor shall provide at least one (1) pre-launch transponder that meets all requirements of the Pathfinder #2 Technical Requirements Document (TRD), Attachment 2. The

Contractor shall provide the frequency plan, in-band responses, Equivalent Isotropically Radiated

Power (EIRP) contours, Gain/Temperature (G/T) contours, saturated flux density (SFD) contours, point-by-point cross-polarization (XPD) contours for the USG Transponder(s) over at least the coverage area specified in the TRD. The contractor shall provide sufficient information to enable

USG Common Network Planning System (CNPS) based Terminal Planning. CDRL [A001]

3.2 Cybersecurity Requirement

[SOW-02] Cybersecurity shall be applicable to the Satellite Access Center(s), Satellites, and

Contractor Enclave(s) where sensitive information or Government data is hosted or stored for all cybersecurity enabled devices (including hardware, software and firmware). The contractor shall document compliance with the cybersecurity requirements in the Cybersecurity Compliance

Matrix (CCM), included as Attachment 5 Appendix 1 TAB T3. If the Government identifies any security controls are non-compliant [In Accordance With (IAW) DoDI 8510.01], the contractor shall include proposed mitigations in the CCM. The contractor shall be subject to Government and/or independent verification of compliance with the CCM following each delivery of CDRL

[A002].

[SOW-03] The contractor shall ensure the Ku-band FSS commercial transponder(s) and associated satellite control elements meet specified cybersecurity requirements including

Department of Defense (DOD) Instruction 8510.01 and the minimum security controls listed in the CCM. The Contractor shall implement Risk Management Framework (RMF) technical controls from the CCM into the component and system engineering processes. The contractor shall provide artifacts to verify compliance during each system review (i.e. Spacecraft

Preliminary Design Review (SPDR), Spacecraft Critical Design Review (SCDR), Integration

Readiness Review (IRR), and Pre-shipment Review (PSR)). CDRL [A002]

[SOW-04] The contractor shall ensure the proposed solution will support continuous monitoring of cybersecurity status with the ability to identify, isolate, eradicate and recover from internal and external threat sources. CDRL [A002]

[SOW-05] U.S. policy and DoD Instructions require the use of National Security Agency

(NSA) approved cryptography to authenticate and encrypt all system commands transmitted over communications links of commercial satellites carrying DOD traffic in support of space missions.

The Contractor shall employ NSA-approved encryption techniques for telemetry and command

(T&C) links for the spacecraft on which the USG Transponder(s) are hosted to obtain full NSA-certified CNSSP-12 compliance. The Contractor shall deliver updates on the progress and status of implementation 5 business days prior to Quarterly Program Review (QPR) meetings and discuss the topic at QPR meetings described in [SOW-39]. For the final submission, the Contractor shall provide a copy of the NSA-issued and signed CNSSP-12 compliance letter no later than 5 business days prior to the spacecraft PSR. CDRL [A003]

[SOW-06] The contractor shall ensure personnel performing functions associated with operations are vetted via background checks with local law enforcement and national authorities.

The contractor shall ensure all personnel in direct contact with sensitive DoD Operations Security

(OPSEC) indicators (the unit, location, and time of operations) have U.S. SECRET or higher personnel security clearances.

[SOW-07] The contractor shall conduct analysis for any Commercial-Off-The-Shelf (COTS), freeware, free and open source software, and shareware software that is not on the government approved product list (https://aplits.disa.mil/apl) to ensure there are no component or system risks.

The Contractor shall take preventative steps at all levels of the respective supply chain to commit suppliers to providing authentic material and conduct preventative actions to include establishing measures to mitigate counterfeiting risks, managing residual risk throughout the life cycle, and maintaining traceability of parts origination and distribution. The Contractor shall document their access control process to ensure only authorized personnel have access to and use of system design information and software/hardware united to integrate commercial technology.

[SOW-08] The Contractor shall engage key employees in OPSEC-awareness training programs. Cleared contractor personnel shall be trained on operational security procedures for use when engaging with sensitive DoD OPSEC information. Key staff shall engage in initial training https://aplits.disa.mil/apl

(on hire or when tasked with DoD specific responsibilities), and on an ongoing basis as requirements necessitate. Additionally, OPSEC indicators shall only be shared with cleared personnel with a specific need to know.

[SOW-09] The contractor shall have twenty four (24) hours per day, seven (7) days per week access to secure voice communications (e.g. Secure Telephone Unit, Secure Telephone

Equipment), or other mutually agreed upon media or voice communications capability capable of protecting Sensitive but Unclassified data, to support anomaly investigation and resolution.

3.3 Spectrum/Frequency Policy Compliance

The following requirements ensure the contractor meets a minimum spectrum policy compliance level. All references to the Contractor’s satellite shall identify the satellite which hosts the USG

Transponder(s). The contractor shall retain ownership and control of the satellite, thus licensing and spectrum regulatory compliance remains with the Contractor.

For the USG Transponder(s):

[SOW-10] The Contractor shall possess a station license (operating authority) issued by a national administration suitable for the satellite, prior to launch of that satellite, and for the satellite’s operational life.

[SOW-11] The Contractor's satellite shall operate in a manner that adheres to the provisions of the national license and International Telecommunication Union (ITU) Radio Regulations.

[SOW-12] The Contractor shall bring the satellite into use in accordance with the ITU-R Radio

Regulations (http://www.itu.int/pub/R-REG-RR).

[SOW-13] For the duration of the PoP, the Contractor's satellite shall not carry any secondary payload from or be licensed or registered with the ITU through any of the nations listed in the most current year’s National Defense Authorization Act (NDAA) States of Concern list.

[SOW-14] The Contractor shall complete the ITU coordination process with all required administrations that are listed in ITU circular CR/C.

http://www.itu.int/pub/R-REG-RR

[SOW-15] The Contractor shall engage the Government on spectrum issues that affect the

USG Transponder(s) and satellite services over the required coverage area, including but not limited to, bi-lateral adjacent satellite interference and when the authorization to operate with the host nation holding the spectrum filings are at risk.

[SOW-16] Transponder(s) from the satellite providing satellite services to the required coverage area shall comply with all applicable national and international spectrum regulations.

[SOW-17] The Contractor shall provide EMI/RFI identification, characterization, and geo-location capability to support resolution of purposeful and accidental incidents of interference.

3.4 Incidental Support (Contract Line Item Number (CLIN) 0003 and CLIN 0004)

[SOW-18] The Contractor shall provide support to assure commercially-controlled satellite operations and situational awareness services for the USG Transponder(s) for fifteen (15) years following the completion of IOT of the satellite.

[SOW-19] The Contractor shall certify they have key operations staff ("key staff") who can affect satellite payload operations and network operations continuously available for incident response and anomaly resolution. One satellite operations staff member shall be available for contact at all times to support incident resolution. Additionally, a satellite operator staff member with decision-making authority (e.g., Chief Executive Officer, Chief Operating Officer, or Chief

Technology Officer) shall be available to be contacted in the event that incident resolution requires business impacting decisions to be made.

3.4.1 Network Operations Center and Personnel Staffing

[SOW-20] The Contractor shall ensure a twenty four (24) hours per day, seven (7) days per week Network Operations Center with English speaking technicians is available. The center shall serve as the focal point for any problems encountered with the satellite service where technicians shall be able to troubleshoot or escalate to the next tier any problems encountered.

[SOW-21] The Contractor shall respond to calls to the network operations center within five

(5) minutes.

3.4.1.1 Satellite Health and Network Monitoring

[SOW-22] The Contractor shall collect and deliver as needed the near real-time monitoring, fault/incident/outage reporting, and information access to ensure effective and efficient operations, performance, and availability consistent with commercial best practices. The Contractor shall perform network monitoring to address the following metrics at a minimum:

• Satellite anomalies likely to disrupt service – Satellite

• Interference Data – Satellite

• Spectrum Data – Satellite

• Inclination – Satellite

• Power – Satellite

3.4.1.2 EMI/RFI Reporting

[SOW-23] The Contractor shall provide EMI/RFI identification, characterization, best effort geo-location, and notification in accordance with the Pathfinder EMI/RFI Reporting Checklist.

Such services include, but are not limited to, identifying and characterizing interferer EMI/RFI being transmitted in addition to an authorized carrier and geo-locating identifiable sources of

EMI/RFI. The Contractor shall follow the attached Pathfinder EMI/RFI Reporting Checklist

(Appendix 1 TAB 1) when an EMI/RFI event occurs which affects USG Transponders. [CDRL

A005]

[SOW-24] The Contractor shall provide initial acknowledgement of EMI/RFI event to the

Wideband Watch Office (WBWO) Watch Officer by telephone within ten (10) minutes and best effort geo-location of the interfering signal source, spectrum analyzer screenshots, and characterization in accordance with guidance (as described in the Pathfinder EMI/RFI Reporting

Checklist) shall be provided within thirty (30) minutes of contractor EMI/RFI detection or

Government request if events are detected by the Government. The contractor shall provide updates to the Government upon change in status, upon request, or every two (2) hours from initial report until incident resolution. If secure email and/or voice communications are not available, the contractor (and subcontractors) shall use a mutually agreed upon media and voice communications system capable of protecting sensitive but unclassified data. No later than five

(5) calendar days after incident resolution, the Contractor shall provide an EMI/RFI Summary of

Action Report [CDRL A005], summarizing the incident, corrective actions taken, and incident resolution, to WBWO Watch Officer and Contracting Officer Representative.

3.4.1.3 Fault Reporting

[SOW-25] The Contractor shall collect operational data for all services and provide data to the

Government to support:

1) detection, identification, and isolation of faults;

2) initiation, tracking, and completion of corrective actions; and

3) fault reporting.

3.4.1.4 Service Interruptions and Outages

[SOW-26] The Contractor shall notify the WBWO bandwidth allocation manager of planned satellite or ground system maintenance and/or outages that could materially affect the USG

Transponder operations at least twenty four (24) hours prior to the event.

[SOW-27] The Contractor shall provide verbal status reports to WBWO for service outages within ten (10) minutes of the outage detection. The Contractor shall provide verbal updates hourly until service is restored. For outages known to be due to failures in Contractor-provisioned elements, the Contractor shall initiate conference calls between the Contractor’s operation center and WBWO. For outages lasting 120 minutes or more, the Contractor’s Program Manager shall participate in the conference calls. For outages lasting 240 minutes or more the Contractor’s Senior

Management shall participate in the conference calls. In instances of EMI or RFI, the contractor shall report status and support incident resolution. These reports are in addition to all electronic reports and quarterly reports. The reports shall identify the circuits involved, the cause of outage if known and the actions already taken and planned to correct the outage.

3.4.2 Transmission Plans

[SOW-28] The Contractor shall operate the USG Transponder(s) in accordance with the

Contractor submitted Satellite Operator Transmission Plan (SOW TAB 2).

[SOW-29] The Contractor shall provide a copy of Satellite Operator Transmission Plan for the

USG Transponder(s) no later than completion of IOT. The Transmission Plan has two tables:

Transponder Technical Characteristics and the Technical Parameters of the Transmission Plan.

The Transmission Plan shall be provided to U.S. Army Space and Missile Defense Command /

Army Forces Strategic Command in electronic form via the XML Transmission Plan Tool for Joint

SATCOM Management Planning System (JSMPS). The Transmission Plan shall be updated as mission requirements dictate.

3.4.3 Disposal Plan

[SOW-30] At the end of the satellite life, the Contractor shall dispose of the host satellite containing the USG Transponder(s) in accordance with Contractor’s End of Mission Disposal Plan

(EOMDP), consistent with the requirements of the licensing administration. The contractor shall have the authority to make the End of Life decision for the satellite using good engineering judgment, if analysis conducted using proven analytical techniques based on commercial best practices warrants such a decision. If this occurs prior to the fifteen (15) years following the completion of IOT, then the Guarantee of Capability clause will be invoked (In Accordance With

52.212-04 Addendum to Contract Terms and Conditions – Commercial).

3.4.4 Host Nation Agreements (HNAs) and Approvals

[SOW-31] The Contractor shall support Host Nation Agreement (HNA) efforts to operate and deliver the requested service in accordance with the Transmission Plan, including working with end-users to operate in compliance of the existing HNA(s).

3.4.5 Reporting

[SOW-32] For the host spacecraft upon which the USG Transponder(s) reside, the Contractor shall provide analysis and test data showing compliance with the Overdrive Protection specification in the TRD. The Contractor shall submit progress updates five (5) business days prior to each Quarterly Program Review. The final report shall be submitted when implementation and analysis of TRD-07, TRD-08, and TRD-09 are complete. The final report shall be submitted no later than ten (10) business days prior to the PSR. CDRL [A007]

[SOW-33] The Contractor shall provide access for the USG to attend its SPDR, SCDR and

PSR meetings (if not yet transpired) for the spacecraft upon which the USG Transponder(s) reside.

PSR shall be completed prior to December 31, 2022.

[SOW-34] For the spacecraft on which the USG Transponder(s) reside, the Contractor shall provide a letter stating successful completion of the SPDR, and a soft copy of the SPDR presentation. SPDR shall be completed prior to December 31, 2022. CDRL [A008]

[SOW-35] For the spacecraft on which the USG Transponder(s) reside, the Contractor shall provide a letter stating successful completion of the SCDR and a soft copy of the SCDR presentation. SCDR shall be completed prior to December 31, 2022. CDRL [A008]

[SOW-36] For the spacecraft on which the USG Transponder(s) reside, the Contractor shall provide a letter stating successful completion of the Spacecraft Thermal Vacuum Testing (TVAC), and a copy of the test data for the USG Transponder(s). TVAC shall be completed prior to

December 31, 2022. CDRL [A008]

[SOW-37] For the spacecraft on which the USG Transponder(s) reside, the Contractor shall provide a letter stating successful spacecraft separation from the launch vehicle booster and acquisition of spacecraft telemetry including description of any issues or anomalies related to the event. Successful spacecraft launch and vehicle separation shall be completed prior to December

31, 2022. CDRL [A008]

[SOW-38] For the spacecraft on which the USG Transponder(s) reside, the Contractor shall provide a letter stating successful completion of spacecraft IOT, and a copy of the test data for the

USG Transponder(s). IOT shall be completed prior to December 31, 2022. CDRL [A008]

[SOW-39] Over the PoP, the Contractor shall hold Quarterly Program Reviews, (QPRs), which shall cover at a minimum program schedules, program/transponder progress and status, CDRL status, progress, and updates, satellite anomalies across the Contractor’s fleet relevant to the USG

Transponder(s), technical issues, operational issues, and status of all payments and remaining payments. QPRs shall also present analysis results from any calibration tests and lifetime availability prediction analysis on the USG transponder(s). The program schedule shall include, at a minimum, dates for QPRs, SPDR, SCDR, IRR, TVAC, NSA certification, completion of

Overdrive protection implementation, PSR, launch, and IOT. The first QPR shall be held at SMC no later than forty-five (45) calendar days following contract award. The first QPR package shall be called the Program Management Plan (PMP). Subsequent QPRs shall be held in the first week of February, May, August, and November through the period of performance for all CLINs. The

Contractor shall provide the QPR package CDRL [A009] five (5) business days prior to each QPR meeting. QPRs may be held via teleconference or in person. For in person meetings, the Contractor shall notify SMC of the date and location of the meeting no later than twenty (20) business days prior to the meeting. However, if possible and practical, the SPDR, SCDR, and the PSR meetings should be held with their concurrent QPRs. The date of a review takes precedence over a scheduled

QPR. For example, an SPDR could be held in mid-October and take the place of the November

QPR.

[SOW-40] Reserved.

3.5 Guarantee of Capability

[SOW-41] If the transponder(s) performance does not meet the requirements specified in the

TRD during the fifteen (15) years following the completion of IOT, then Government will invoke the Guarantee of Capability clause (IAW 52.212-04 Addendum to Contract Terms and Conditions

– Commercial). The Contractor shall restore capability which meets TRD REQIDs 01, 10, 11, 12, 13 14, 16, 17, and 19; and SOW paragraphs 3.3, 3.4, 3.5, and 3.7 which comprise bandwidth greater than or equal to offeror’s proposed bandwidth during the fifteen (15) years following IOT.

If the transponder(s) are unable to complete IOT for any reason, including but not limited to: pre-launch or launch damage, destruction, defects, or any other reason, then the Government will invoke the Guarantee of Capability clause (IAW FAR 52.212-04 Addendum to Contract Terms and Conditions – Commercial, paragraph (o)). The Contractor shall provide capability in accordance with the TRD REQIDs 01, 10, 11, 12, 13, 14, 16, 17, and 19; and SOW paragraphs

3.3, 3.4, 3.5, and 3.7 which comprise bandwidth greater than or equal offeror’s proposed bandwidth during the fifteen (15) years following the scheduled date (provided at the most recent

QPR) of IOT.

3.6 System Safety

[SOW-42] The Contractor shall provide a system safety program that satisfies its commercial requirements for all work, accommodations, and new components provided under this contract.

CDRL [A010]. Initial submission shall be five (5) business days prior to Spacecraft Preliminary

Design Review. Updates shall be submitted five (5) business days prior to the Spacecraft Critical

Design Review and the PSR.

[SOW-43] The Contractor is responsible for: all spacecraft mishap prevention, meeting range safety requirements for the applicable launch system, meeting space safety requirements (eg. Title

14 CFP Chapter III – Federal Aviation Administration Commercial Space Transportation

Regulations), safe conduct of payload-spacecraft Integration & Test activities at its facilities and launch operations, and accepts all mishap risks.

[SOW-44] In the event of a mishap, the Contractor shall assist in any potential United States

Air Force Pathfinder #2 mishap reporting processes. CDRL [A011].

3.7 Security for Government Financing

[SOW-45] Security for interim payment financing. Pursuant to FAR Subpart 32.202-4

Security for Government Financing and 10 U.S.C. 2307(f) and 41 U.S.C. 4505, the Government is required to obtain adequate security for Government financing. Adequate security for payments made under this contract shall be required in the form as outlined in FAR Subpart

32.202-4 Security for Government Financing and 10 U.S.C. 2307(f) and 41 U.S.C. 4505. The

Contractor shall submit proposed security to support Government Financing of CLIN 0001 and justify adequacy of this security in accordance with FAR 32.202-4. The contractor shall deliver necessary artifact(s) to support proposed security as CDRL [A012]. In the event the Contractor fails to provide adequate security as required in this contract, no financing payment shall be made under this contract. Upon receipt of adequate security, financing payments shall be made, including all previous payments to which the Contractor is entitled, in accordance with the terms of the contract. If at any time the Contracting Officer determines that the security provided by the Contractor is insufficient, the Contractor shall promptly provide such additional security as the Contracting Officer determines necessary.

3.8 Deliverables

[SOW-46] Table 1, the Contract Delivery Requirements List (CDRL), identifies the data requirements for this effort. These are the items that must be delivered to the Government as specified in the applicable REQID. The Government will have ten (10) business days to review deliverables and make comments. The Contractor shall have three (3) business days to make corrections. Upon receipt of all final deliverables, the Government will have five (5) business days to reject the corrected deliverable.

Table 1 - Deliverables

CDRL Number REQID Title

CDRL A001

SOW-01,

SOW-22

Satellite Performance

CDRL A002

SOW-02,

SOW-03,

SOW-04

Cybersecurity Compliance Matrix

CDRL A003 SOW-05 CNSSP-12 Compliance

CDRL A004 Reserved Reserved

CDRL A005

SOW-23

SOW-24

Pathfinder EMI/RFI Summary of Action

Report

CDRL A006 Reserved Reserved

CDRL A007

SOW-32

Overdrive Protection Data

CDRL A008

SOW-34,

SOW-35,

SOW-36,

SOW-37,

SOW-38

See Block 16

CDRL Number REQID Title

CDRL A009 SOW-39 Quarterly Program Review Package

CDRL A010 SOW-42 System Safety Program Plan

CDRL A011

SOW-22,

SOW-25,

SOW-44

Mishap Cause Report

CDRL A012 SOW-45 Security for Government Financing

4 AEROSPACE FFRDC ENABLING REQUIREMENT

a. The Air Force has entered into a contract with The Aerospace Corporation, a California nonprofit corporation operating a Federally Funded Research and Development Center (FFRDC), for the services of a technical group that will support the DoD/U.S. Government program office by performing General Systems Engineering and Integration, Technical Review, and/or Technical

Support including informing the commander or director of the various Department of Defense

(“DoD”) organizations it supports and any U.S. Government program office of product or process defects and other relevant information, which, if not disclosed to the U.S. Government, could have adverse effects on the reliability and mission success of a U.S. Government program.

1. General Systems Engineering and Integration (GSE&I) deals with overall system definition;

integration both within the system and with associated systems; analysis of system segment and subsystem design; design compromises and tradeoffs; definition of interfaces; review of hardware and software, including manufacturing and quality control; observation, review and evaluation of tests and test data; support of launch, flight test, and orbital operations; appraisal of the contractors' technical performance through meetings with contractors and subcontractors, exchange and analysis of information on progress and problems; review of plans for future work; developing solutions to problems; technical alternatives for reduced program risk; providing comments and recommendations in writing to the applicable DoD

System Program Manager and/or Project Officer as an independent technical assessment for consideration for modifying the program or redirecting the contractor's efforts; all to the extent necessary to assure timely and economical accomplishment of program objectives consistent with mission requirements.

2. Technical Review (TR) includes the process of appraising the technical performance of the contractor through meetings, exchanging information on progress and problems, reviewing reports, evaluating presentations, reviewing hardware and software, witnessing and evaluating tests, analyzing plans for future work, evaluating efforts relative to contract technical objectives, and providing comments and recommendations in writing to the applicable Air

Force Program Manager as an independent technical assessment for consideration for modifying the program or redirecting the contractor’s efforts to assure timely and economical accomplishment of program objectives.

3. Technical Support (TS) deals with broad areas of specialized needs of customers for planning, system architecting, research and development, horizontal engineering, or analytical activities for which The Aerospace Corporation is uniquely qualified by virtue of its specially qualified personnel, facilities, or corporate memory. The categories of TS tasks are: Selected

Research, Development, Test and Evaluation; Plans and System Architecture; Multi-Program

Systems Enhancement; International Technology Assessment; and Acquisition Support.

b. In the performance of this contract, the contractor agrees to cooperate with The Aerospace

Corporation by 1) responding to invitations from authorized U. S. Government personnel to attend meetings; 2) by providing access to technical information and research, development planning data such as, but not limited to, design and development analyses, test data and results, equipment and process specifications, test and test equipment specifications and procedures, parts and quality control procedures, records and data, manufacturing and assembly procedures, and schedule and milestone data, all in their original form or reproduced form and including top-level life cycle cost data, where available; 3) by delivering data as specified in the Contract Data Requirements List;

4) by discussing technical matters relating to this program; 5) by providing access to contractor facilities utilized in the performance of this contract; 6) and by allowing observation of technical activities by appropriate technical personnel of The Aerospace Corporation. The Aerospace

Corporation personnel engaged in GSE&I, TR, and/or TS efforts: (i) are authorized access to all such technical information (including proprietary information) pertaining to this contract and may discuss and disclose it to the applicable DoD personnel in a program office; (ii) are authorized to discuss and disclose such technical information (including proprietary information) to the commander or director of the various DoD organizations it supports and any U.S. Government personnel in a program office which, if not disclosed to the U.S. Government, could have adverse effects on the reliability and mission success of a U.S. Government program; and (iii) Aerospace shall make the technical information (including proprietary information) available only to its

Trustees, officers, employees, contract labor, consultants, and attorneys who have a need to know.

1. Cost data is defined as information associated with the programmatic elements of life cycle

(concept, development, production, operations, and retirement) of the system/program. As defined, cost data differs from “financial” data, which is defined as information associated with the internal workings of a company or contractor that is not specific to a project or program.

c. The contractor further agrees to include in all subcontracts a clause requiring compliance by subcontractor and supplier and succeeding levels of subcontractors and suppliers with the response and access and disclosure provisions of this Enabling requirement, subject to coordination with the contractor, except for subcontracts for commercial items or commercial services. This agreement does not relieve the contractor of its responsibility to manage the subcontracts effectively and efficiently nor is it intended to establish privity of contract between the

Government or The Aerospace Corporation and such subcontractors or suppliers, except as indicated in paragraph (d) below.

d. The Aerospace Corporation shall protect the proprietary information of contractors, subcontractors, and suppliers in accordance with the Master Non-disclosure Agreement The

Aerospace Corporation entered into with the Air Force, a copy of which is available upon request.

This Master Non-disclosure Agreement satisfies the Nondisclosure Agreement requirements set forth in 10 U.S.C. §2320 (f)(2)(B), and provides that such contractors, subcontractors, and suppliers are intended third-party beneficiaries under the Master Non-disclosure Agreement and shall have the full rights to enforce the terms and conditions of the Master Non-disclosure

Agreement directly against The Aerospace Corporation, as if they had been signatory party hereto.

Each such contractor, subcontractor, or supplier hereby waives any requirement for The Aerospace

Corporation to enter into any separate company-to-company confidentiality or other non-disclosure agreements.

e. Aerospace shall make the technical information (including proprietary information) available only to its Trustees, officers, employees, contract labor, consultants, and attorneys who have a need to know, and Aerospace shall maintain between itself and the foregoing binding agreements of general application as may be necessary to fulfill their obligations under the Master Non-disclosure Agreement referred to herein, and Aerospace agrees that it will inform contractors, subcontractors, and suppliers if it plans to use consultants, or contract labor personnel and, upon the request of such contractor, subcontractor, or supplier, to have its consultants and contract labor personnel execute non-disclosure agreements directly therewith.

f. The Aerospace Corporation personnel are not authorized to direct the contractor in any manner.

The contractor agrees to accept technical direction as follows:

1. Technical direction under this contract will be given to the contractor solely by SMC.

2. Whenever it becomes necessary to modify the contract and redirect the effort, a change order signed by the Contracting Officer or a Supplemental Agreement signed by both the

Contracting Officer and the contractor will be issued.

Appendix 1

TAB 1: Pathfinder EMI/RFI Reporting Checklist

Pathfinder EMI/RFI Reporting Checklist

Checklist Number

OPWS-07C (1 Apr 08)

Step Actions

This checklist outlines information personnel report to the Wideband Watch Office (WBWO) Watch Officer upon encountering an Interfering Signal (IS) that affects the User Signal performance. Use this checklist to report EMI on any spectrum; each spectrum will fill out information as applicable.

For commercial upchannel reporting, fill out ALL lines; for upchannel reporting, fill out only the lines with an asterisk (*).

Commercial SATCOM Owner-Operator will IMMEDIATELY and FIRST contact the WBWO Watch Officer to report the collected information.

*** WBWO Watch Officer: 1-855-SATC0M1 ***

EVENT DESCRIPTION RESULT

*4. DOES IT APPEAR THAT THE USER’S

SIGNAL IS THE FOCUS OF THIS EMI? (YES /

NO / UNDER INVESTIGATION)

*5. IS THIS THE FIRST EVENT OF THIS

NATURE AGAINST THE USER’S SIGNAL?

(YES / NO / UNDER INVESTIGATION)

6. IS THE EMI CROSS POLARIZATION

INTERFERENCE? (YES / NO / UNDER

INVESTIGATION )

*7. IS THE EMI ADJACENT SATELLITE

INTERFERENCE? (YES / NO / UNDER

INVESTIGATION)

*8. HAVE THE USERS BEEN ELIMINATED AS

THE INTERFERENCE SOURCE? (YES / NO /

UNDER INVESTIGATION)

*9. START TIME OF EMI EVENT (AS

REPORTED BY DOD ASSET):

10. CONTRACT VEHICLE/MISSION NUMBER

*11. DELIVERY ORDER (DO), TASK ORDER

(TO) NUMBER / MISSION NUMBER :

12. TRANSMISSION PLAN (TP) REVISION:

13. VENDOR:

AFFECTED SATELLITE INFORMATION

*14. AFFECTED SATELLITE (COMMON

NAME):

*15. SATELLITE SCC (SATELLITE SPACE

COMPUTATION CENTER) NUMBER:

*16. SATELLITE LOCATION (LONGITUDE):

17. SATELLITE OWNER/PRIMARY SUPPORT

DOWNLINK (RECEIVE) TERMINAL INFORMATION

18. DOWNLINK TERMINAL LOCATION (LAT

/ LONG):

*19. ANTENNA TERMINAL TYPE / RADIO

TYPE :

20. ANTENNA SIZE (METERS):

21. G/T (dB/K):

DOWNLINK (RECEIVE) INFORMATION

*22. DOWNLINK TRANSPONDER

NAME/CHANNEL :

*23. DOWNLINK (RECEIVE) CENTER

FREQUENCY/DOWNLINK FREQ :

24. DOWNLINK (RECEIVE) POLARITY:

25. DOWNLINK BEAM (SHORT NAME):

UPLINK (TRANSMIT) TERMINAL INFORMATION

26. UPLINK TERMINAL LOCATION (LAT /

LONG):

27. ANTENNA TERMINAL TYPE/MODEL:

28. ANTENNA SIZE:

29. EIRP (dB/W):

UPLINK (TRANSMIT) INFORMATION

30. UPLINK (TRANSMIT) TRANSPONDER

NAME/CHANNEL:

*31. UPLINK (TRANMIT) CENTER

FREQUENCY/UPLINK FREQ :

32. UPLINK TRANSPONDER POLARITY:

33. UPLINK BEAM (SHORT NAME):

OTHER INFORMATION

*34. ALLOCATED BANDWIDTH (MHZ/KHZ):

*35. MODULATION:

36. AFFECTED USER’S SIGNAL (DIGITAL OR

ANALOG):

37. (IF DIGITAL) BIT ERROR RATE (BER)

BEFORE EVENT:

38. (IF DIGITAL) BIT ERROR RATE (BER)

DURING EVENT:

*39. TRANSLATION FREQUENCY

(MHZ/KHZ):

INTERFERING SIGNAL DESCRIPTION

*40. FREQUENCY OF INTERFERING SIGNAL

APPEARS: (STEADY (OR) VARYING)

*41. (IF STEADY) CENTER FREQUENCY OF

INTERFERING SIGNAL (MHZ/KHZ):

*42. (IF VARYING) DRIFTING (OR)

SWEEPING (OR) ERRATIC:

*43. (IF DRIFTING OR SWEEPING) CENTER

OF LIMITS OF SWEEP/DRIFT (MHZ/KHZ):

*44. (IF DRIFTING OR SWEEPING)

BANDWIDTH WITHIN LIMITS OF

SWEEP/DRIFT (MHZ/KHZ):

*45. (IF ERRATIC): DESCRIBE (OPEN TEXT)

*46. INTERFERING SIGNAL APPEARS:

(MODULATED / CONTINUOUS WAVE)

47. (IF MODULATED) HALF-POWER

BANDWIDTH OF INTERFERING SIGNAL

(MHZ:

48. POWER/AMPLITUDE OF INTERFERING

SIGNAL APPEARS: (STEADY (OR) VARYING )

49. (IF STEADY) SIGNAL-TO-NOISE RATIO

(DB):

50. (IF VARYING) PULSING (OR) SLOW

INCREASE (OR) SLOW DECREASE:

51. (IF VARYING) MAXIMUM SIGNAL-TO-

NOISE RATIO (DB):

Watch Officer will be sure to get the caller’s name, organization/company, and telephone #.

Watch Officer will ask the caller for mission impact as reported by the user. If the caller does not have this info, the WO will ask the caller to get the info and call back the WBWO.

Acronym List

CCM Cybersecurity Compliance Matrix CDR Critical Design Review CLIN Contract Line Item CNPS Common Network Planning System

CNSSP-12

Committee on National Security Systems Policy 12

COCOM Combatant Command COMSATCOM Commercial Satellite Communications COTS Commercial Off The Shelf DOD Department of Defense EIRP Equivalent Isotropically Radiated Power EMI Electromagnetic Interference FAA Federal Aviation Administration FCC Federal Communications Commission

FFRDC

Federally Funded Research and Development Center

FSS Fixed Satellite Services G/T Gain/Temperature HNA Host Nation Agreement IAW In Accordance With IOT In-Orbit Test IRR Integration Readiness Review ITU International Communications Union

JSMPS

Joint Satellite Communications Management Planning System

NDAA National Defense Authorization Act NSA National Security Administration OPSEC Operational Security PF1 Pathfinder #1 PF2 Pathfinder 2 POP Period of Performance PSR Pre-ship Review QPR Quarterly Program Review REQID Requirements Identifier

RMF Risk Management Framework SATCOM Satellite Communications SCDR Spacecraft Critical Design Review SMC Space and Missile Systems Center SOW Statement of Work SPDR Spacecraft Preliminary Design Review T&C Telemetry and Command TRD Technical Requirements Document TR Technical Review TS Technical Support TVAC Thermal Vacuum Testing USG United States Government WBWO Wideband Watch Office XPD Point-by-Point Cross-Polarization