SOW.pdf

RFP #

STATEMENT OF WORK

Security for Sonic Boom Field Measurements

Program Office

National Aeronautics and Space Administration Armstrong Flight Research Center Edwards, California

Table of Contents

1.0 Background

2.0 Objectives

3.0 Requirements

4.0 Deliverables

5.0 Period of Performance

6.0 Travel

7.0 Other Special Requirements and Considerations

RFP/Contract No. Sonic Boom Field Security 05 June 2026

1.0 Background

The NASA Quesst mission has built an aircraft capable of flying at supersonic speeds without making a loud sonic boom on the ground. This aircraft, the NASA X-59, will be used to conduct tests at Armstrong Flight Research Center (AFRC) and at select cities across the continental USA. These tests require that the X-59 aircraft’s sonic boom be measured using NASA ground recording systems (GRS). Up to 125 GRS will be deployed for each test. In addition to the GRS, the team will deploy weather stations, trailers, and various other sonic boom flight research field systems.

All equipment and personnel will be deployed in remote, unattended locations for extended periods in support of the Quesst mission. The locations are public land with considerable human and wildlife activity. A security system is required to protect all resources and assets.

2.0 Objectives

Provide temporary, rapidly deployable field security services to protect NASA-owned sonic boom monitoring equipment, support trailers, and associated assets deployed in remote locations in support of the Quesst mission. The contractor shall provide continuous surveillance, intrusion detection, remote monitoring capabilities, and incident notification capabilities sufficient to deter theft, vandalism, and unauthorized access while minimizing impacts to ongoing field operations and mission data collection activities.

The systems will be monitored by NASA.

3.0 Requirements

The contractor shall provide two (2) self-contained, rapidly deployable security units capable of continuous operation at remote field locations without reliance on permanent site infrastructure.

The units shall provide video surveillance, remote monitoring, wireless communications, intrusion detection, and real-time notification capabilities for Government personnel. The contractor shall provide all equipment, installation, activation, monitoring services, maintenance, and technical support necessary to maintain operational security coverage throughout the deployment period.

4.0 Deliverables

Mobile Security Units (MSU), (2 count) o Management and operation of MSUs

Shipping of MSUs Setup of MSUs

5.0 Period of Performance

1 year after contract award

RFP/Contract No. SOW Title Date or Version #

6.0 Travel

Round-trip to set-up and retrieve MSUs, included with quote and services

7.0 Other Special Requirements and Considerations

N/A

REVISIONS

Revision Number Date Brief Summary of Changes

Base 06/05/26 Original SOW

This section tracks changes made to the SOW so that the history of the SOW can be viewed easily. A summary of the change for the revision should be entered along with the date of the change.

SOW Language Tips:

A variety of people with different perspectives and life experiences will read your SOW. Readers typically include Government and industry contracting personnel, managers, technical experts, accountants and lawyers. All these readers need to understand the SOW in a clear and concise manner;

therefore, language selection is very important.

Below are tips that you should consider when reviewing the SOW:

Use simple words, phrases, and sentences whenever practical.

Be concise, precise, and consistent. Keep sentences short and to the point. Normally the longer the sentence, the harder it is to understand.

Use verbs in the active voice. A verb is in the active voice when it expresses an action performed by its subject. For example, “The Contractor shall report contract progress quarterly.”

Conversely, avoid using verbs in the passive voice. A verb is in the passive voice when it expresses an action performed upon its subject or when the subject is the result of the action. For example, “Contract progress shall be reported quarterly by the Contractor.”

Use “shall” or “must” when writing a requirement binding on the Contractor. Avoid “should” or “may” because they leave the decision on appropriate action up to the Contractor.

Use “will” to indicate actions by the Government.

Be consistent when using terminology. Use the same word to mean the same thing throughout your SOW. Avoid using different words to indicate the same type of action.

Avoid redundancy. At best, requiring the Contractor to do the same thing in different parts of the SOW will add needless words to the SOW. At worst, there may be subtle differences in the requirements that may lead to a dispute during contract performance.

Avoid vague or inexact phrases and generalizations.

Avoid catchall and open-ended phrases, such as, “is common practice in the industry,” “as directed,” or “subject to approval.” If you want to give the Contractor an opportunity to use their standard commercial practices, require each offeror to identify its commercial practices in a proposal and then include that proposal as part of the order/contract.

Define technical terms.

Avoid using Government jargon. Assure that it is clearly defined whenever jargon must be used.

Only use “any,” “either,” “and/or,” “etc.” when allowing the Contractor to select an alternative.

Use abbreviations or acronyms only after spelling them out the first time they are used (e.g., National Aeronautics and Space Administration (NASA)). Spell them out even if they are commonly used by NASA because a commercial Contractor may not be familiar with them.

Identify the date or version of any document referenced in your SOW.

Advise readers from industry where they can obtain referenced documents.