SOW_2020-09-23.pdf

For Official Use Only

Federal Aviation Administration

Unmanned Aircraft Systems (UAS) Technologies For Airports

Statement Of Work - DRAFT

September 23, 2020

Description of Work: The Federal Aviation Administration’s (FAA) Office of Airports’ Airport

Technology Research and Development Branch (ATRD) supports the FAA’s mission by conducting the necessary research and development required to enhance the safety of operations at our nation’s airports and to ensure the adequacy of engineering specifications and standards in all areas of the airport systems, and, where necessary, develop data to support new standards. The research conducted by ATRD is highly visible and has a high impact to airport safety.

The contractor will be responsible for conducting and supporting a wide variety of research efforts comprising of tests, evaluations, and studies that support an efficient, productive, and cost-effective National Airspace System (NAS). These efforts will include activities related testing and evaluating UAS technologies for airports.

This Statement of Work (SOW) includes the following task areas:

Task Area 1: UAS Detection and Mitigation Technologies/Systems (RE&D/AIP Funded)

Task Area 2: UAS Airport Applications (AIP Funded)

Additional task areas, within the general scope of this SOW, may be added by the FAA during the period of performance (POP) of this contract as the technology and industry matures.

1. TASK AREA BACKGROUND

1.1. Task Area 1: UAS Detection and Mitigation Technologies/Systems

The FAA Reauthorization Act of 2018, Section 383, AIRPORT SAFETY AND

AIRSPACE HAZARD MITIGATION AND ENFORCEMENT, directs the FAA to work with the Department of Defense (DoD) and Department of Homeland Security (DHS) and the heads of other relevant Federal departments and agencies for the purpose of ensuring that technologies or systems that are developed, tested, or deployed by Federal departments and agencies to detect and mitigate potential risks posed by errant or hostile UAS operations do not adversely impact or interfere with safe airport operations, navigation, air traffic services, or the safe and efficient operation of the National Airspace System (NAS).

In addition, it also directs the FAA to develop a plan for the certification, permitting, authorizing, or allowing of the deployment of detection and mitigation technology or systems in the airport environment. It further requires the FAA to test UAS detection and mitigation technologies/systems at five airports. For the purposes of this effort, ATRD will conduct research primarily at the Atlantic City International Airport (ACY) colocated next to the FAA’s William J. Hughes Technical Center, at four additional airports to-be-determined (TBD), and other possible test ranges that have yet to be determined. The bulk of the detection and mitigation technologies/systems testing and data collection will take place in the controlled setting of the ACY test area where environmental impacts, electronic interference, and other factors can be closely monitored and accounted for in the performance analysis.

The FAA recognizes the fast rate of change in the UAS detection and mitigation ecosystem and is poised to conduct a series of operational evaluations to derive a performance-based standard. ATRD intends to test and evaluate several different unmanned aircraft system

(UAS) detection and/or mitigation technologies/systems under this research effort. It is uncertain how many of the detection technologies/systems will be radar, radio frequency

(RF), electro optical/infrared, acoustic, cellular, or a combination of these technologies.

Specifics about the program will continue to develop as the program matures.

An initial DRAFT technical performance standard will be generated from the data collected on each of the technologies evaluated in the tightly controlled setting of ACY. Installing and evaluating each technology/system at ACY will provide baseline conditions. After completing a thorough evaluation at ACY, a technology/system will be deployed to one of four (or more) added airports for validation and to collect additional data. In addition, during UAS detection and mitigation technology/system validation at the four additional airports, the FAA and airport stakeholders may assess UAS usability requirements and responses around airports.

Ultimately, this effort will culminate in performance standards and best practices for the selection and deployment of UAS detection and mitigation technologies/systems in the airport environment. In addition, this effort will also help inform airports and Federal and

State agencies of technical, operational, and safety considerations associated with selecting and deploying UAS detection and mitigation technologies/systems, and possibility define usability requirements and responses within the vicinity of an airport.

1.2. Task Area 2: UAS Airport Applications

The continuous evolution of UAS has stimulated interest among airport operators for various airfield applications. Today’s UAS are autonomous to execute complex flight patterns with minimal input from remote pilots and boast safety features including automatic return functionality, collision-avoidance, etc. High-resolution cameras and other advanced sensors provide real-time data at heights, distances, and angles never before possible.

Historically, airfield activities such as obstruction analysis, pavement inspection, wildlife hazard management, perimeter security inspections, and emergency response, and other airport safety related applications have primarily been conducted on the ground. However, aerial observations and measurements offer opportunities to increase the efficiency of routine assessments, as well as an unprecedented viewpoint during emergencies. The gradual integration of UAS into the airport environment could supplement or even replace the need for many ground-based procedures.

In cooperation with the FAA’s Office of Airports, ATRD is working to enable the safe, reliable, and effective integration of UAS into the airport environment. Chief among outcomes of this effort is conducting research, testing, and evaluations to identify suitable technologies and processes and procedures for each unique UAS airport application. The outcome of this research will assist with creating/updating FAA guidance documentation for UAS integration at our nation’s airports.

The FAA’s Office of Airports and ATRD have identified six-core applications for UAS in the airport environment, listed in order of priority:

1. Obstruction Analysis – Identifying obstructions that are penetrating an airports imaginary surface(s).

2. Airfield Pavement Inspections – Collecting data to supplement traditional (visual) airport pavement inspections.

3. Wildlife Hazard Management – Dispersing wildlife and monitoring/surveying wildlife and habitat/attractants on and within the vicinity of an airport.

4. Perimeter Security – Inspecting an airport fence line for anomalies, searching for possible intruders, and responding to emergencies.

5. Aircraft Rescue and Firefighting (ARFF) – Providing incident commanders with live monitoring capabilities for increased situational awareness and to document an accident/incident scene.

6. Other Airport Safety Related Applications / UAS Airport Integration Program Planning

- ATRD is continuously evaluating new and emerging UAS airport applications / programs to include in their research portfolio.

2. GENERAL REQUIREMENTS

The contractor must provide the necessary program management support and technical expertise necessary to support the specific requirements in the Task Areas included in this SOW. The contractor must have the ability to conduct research, testing, and evaluation activities without supervision/direction. All contractor and sub-contractor employees must have and maintain a U.S.

driver’s license and Passport, and must have the ability to obtain and maintain an airport security badge (potentially with driving privileges) for access to the airport movement and non-movement areas of large airports. The contractor and subcontractor(s) will be required to travel frequently to multiple airports, testing/evaluation locations, and for meetings. The contractor and subcontractor(s) will be required to work beyond and outside a normal working schedule at various times to accomplish the Task Areas and their subsequent subtasks in the SOW. The contractor and subcontractor(s) must maintain a program management office to enable essential staff to respond within 30 minutes to work with ATRD at the FAA’s William J. Hughes Technical Center, NJ, their collaborators, and to conduct a testing and evaluations of UAS technologies at ACY.

The contractor must have a Program Manager(s) that will have responsibilities of performing the day-to-day and long-term program/project planning, managing personnel, scheduling, setting up regular meetings, managing subcontracts, conduct administrative duties, and reporting of the work to be performed by the support staff under the requirements of this SOW. The Program Manager(s) must demonstrate previous U.S. Government collaboration and contractual experience.

The contractor support staff must demonstrate experience in project management, engineering, field installations, writing technical documents, and previous work in an airport operations environment. The contract support staff must demonstrate the ability to conduct research, testing, and evaluation activities without supervision/direction. The contract support staff must have experience with managing a diverse, complex, fast-paced, and highly visible program portfolio.

The contract support staff must have knowledge and experience with deploying, monitoring, troubleshooting, and removing complex equipment on an airfield. The contract support staff must have a proficient knowledge and understanding of the National Airspace System (NAS), Title 14

Code of Federal Regulations (CFR) Part 139 - Certification of Airports, FAA Advisory Circulars, FAA Orders, FAA CertAlerts, FAA Engineering Briefs, other FAA Guidance Documents, FAA

Air Traffic Policies and Procedures and the airport operations environment. The contractor support staff must be proficient and knowledgeable in UAS operations, and their designated UAS pilots/flight crew members must hold/maintain a current 14 CFR Part 107 remote pilot airman certificate, for UAS.

It is anticipated that the contractor will require multiple skill sets, areas of discipline, labor force, areas of expertise, and support to fully accomplish the Task Areas and subsequent subtask areas in this SOW. The following are contractor support staff considerations that may be needed to accomplish the subtasks: project manager professionals (PMP), engineers, airport operations analysts, airport emergency responders, logistics, communications, electronics, hardware/software applications, electrical, spectrum analysts, radar specialist, geospatial analysts/engineers, remote sensing specialists, photogrammetrists, pilots, multidiscipline engineering technicians, technical report writers, report editors, and subject matter experts (SME). The specific requirements discussed in this SOW will require multiple teams to test at different locations, simultaneously.

Changes to this Statement of Work will be issued by contract modification. Subtasks within

Section 3 of this Statement of Work will come to completion and may be updated with new subtasks, within the general scope of the SOW, as technology and industry mature and new research requirements are received by the FAA.

2.1. Work Schedule

The Contractor will be required to work beyond and outside a normal working schedule at various times to accomplish the Task Areas in the SOW. Contractor personnel may be required to work and travel some nights and weekends due to off-hour testing. For the purposes of this SOW, a ‘normal working schedule’ is defined as 8am to 5pm, Monday through Friday.

3. SPECIFIC REQUIREMENTS

3.1. Task Area-1: UAS Detection and Mitigation Technologies/Systems. An FAA ATRD research team will be coordinating and conducting the technical evaluation of UAS detection and mitigation systems in two phases. In Phase 1, the FAA will initially be assessing and examining multiple different technology types and systems at the Atlantic

City International Airport (ACY), collocated next to the FAA William J. Hughes Technical

Center and supporting ranges for mitigation. Upon the demonstrated technical performance assessment, the FAA research team will initiate Phase 2, which includes deploying selected technologies/systems to hosting Airport Operators and their airport environment to conduct operations to evaluate the technology and validate/refine performance standards. In Phase 2, in coordination with Airport Operators and stakeholders, the FAA will conduct UAS operations to evaluate the UAS detection and mitigation systems deployed at the airports. The FAA may evaluate usability requirements of the technologies/systems. All of the information and data collected will be used by the

FAA to draft performance standards and guidance language that describes the selection, procurement, deployment, and management of UAS detection and mitigation technologies/systems in an airport environment.

3.1.1. Subtask 1 – Support.

3.1.1.1. The contractor must provide the support described in Section 2

GENERAL REQUIREMENTS of this this SOW to accomplish Task

Area-1 and subsequent Subtasks.

3.1.1.2. The contractor must perform the necessary program/project management tasks/activities to support this Subtask, which includes, but is not limited to:

3.1.1.2.1. Providing necessary and qualified personnel to support this

Subtask.

3.1.1.2.2. Preparing and maintaining project schedules using project management tools.

3.1.1.2.3. Coordinating and collaborating with all parties involved in the research, testing, and evaluations of UAS detection and mitigation technologies/systems.

3.1.1.2.3.1. This may include, but not limited to: various

FAA organizations, airport operators, other support contractors, other stakeholders, federal, state, or local governmental organizations, security/law enforcement, vendors, etc.

3.1.1.2.4.Scheduling meetings and preparing/distributing meeting agendas, meeting minutes, and action items.

3.1.1.2.5.Providing status updates on task area related activities.

3.1.1.2.6.Preparing project plans, test plans, test cards, presentation materials, reports, program/safety related analyses, and other deliverables, requested by the Contracting Officer’s

Representatives (COR).

3.1.1.2.7.Providing and addressing edits/comments to reports, plans, and other documents and deliverables.

3.1.1.2.8.The contractor must archive all information, minutes, notes, plans, data, etc. into a central depository that is available for

ATRD and their collaborators.

3.1.1.3. The contractor must support the FAA ATRD with UAS detection and mitigation technology/system research, testing, and evaluation efforts at

ACY, additional airports TBD, and additional sites TBD.

3.1.1.3.1. The contractor must prepare and execute project plans, test plans, and test cards. Test cards may be repeated several times, as needed.

3.1.1.3.2. The contractor must develop ‘performance specifications’ framework for each type of UAS detection and mitigation technology. With the objective to create draft FAA Advisory

Circulars or other FAA Guidance Documents.

3.1.1.3.3. The contractor must perform planning and coordination efforts in preparation for the deployment, testing, and evaluation of

UAS detection and mitigation technologies/systems at ACY and other airport locations. This includes participating in airport site surveys and determining the necessary authorizations and permits required necessary to deploy, test, and evaluate UAS detection and mitigation technologies/systems, at airport locations.

3.1.1.3.3.1. The contractor must perform/support and

document a hazard/risk analysis/assessment and other safety related analyses/assessment prior to conducting UAS detection and mitigation testing/evaluations.

3.1.1.3.3.2. The contractor must perform/support and

document spectrum interference testing at each airport, prior to the commencement of UAS detection and mitigation testing/evaluations.

3.1.1.3.4. The contractor must develop a methodology and ranking criteria for selecting UAS platforms for testing/evaluating against UAS detection and mitigation technologies/systems.

3.1.1.3.5. The contractor must assist the FAA ATRD and each UAS detection and mitigation technology/system vendor with deploying, operating, maintaining, monitoring, troubleshooting, collecting data, and removing technologies/systems, at each airport location.

3.1.1.3.6. The contractor must test and evaluate the performance capabilities of each UAS detection and mitigation technology/system.

3.1.1.3.6.1. The contractor must review, analyze, and

report on the data collected during the test and evaluation period.

3.1.1.3.6.2. The contractor must develop objective criteria

and metrics for testing/evaluating each of the

UAS detection and technologies tested at ACY and other airport locations.

3.1.1.4. The contractor must fully document all UAS detection and mitigation technology/system testing and evaluations performed under this Task

Area.

3.1.1.5. The contractor must participate in UAS detection and mitigation technology demonstrations (sometimes in short notice), as requested by the COR or authorized federal designee.

3.1.1.6. The contractor may be asked to participate in other agencies UAS detection and mitigation testing and evaluations, demonstrations, and/or operations.

3.1.1.7. The contractor must document all necessary information to support this

Task Area.

3.1.1.8. The FAA may provide Technical Direction for other duties, within the general scope of this Task Area, as needed/assigned by the FAA ATRD in support of this Task Area.

3.1.1.9. The contractor must continually review and analyze the data being collected and prepare draft Engineering Brief/Advisory Circular language, or other guidance document that describes the performance specifications, selection, procurement, deployment, and management of UAS detection and mitigation technologies/systems in the airport environment. It should become clear which factors must be considered when choosing the proper system for a given set of airport conditions and requirements from the field-testing/evaluations. Research efforts should also refine the minimum performance standards for airport UAS detection and mitigation technologies/systems and most certainly will have valuable lessons learned on the process and considerations of installing a system in the location best suited to maximizing system capabilities, and detail any impacts to navigational aids, visual aids, and other airport equipment that is discovered during the test and evaluation efforts. Lastly, through longitudinal operations of multiple technologies/systems at multiple airports, the contractor will prepare guidance for best practices to manage the effective use of UAS detection and mitigation technologies/systems to secure the airport and ensure fundamental principles of safety risk management are followed.

3.1.2. Subtask 2 – Revise Documents/Deliverables. The FAA ATRD often submits documents/deliverables, such as a Presentation, Final Report, Technical Note, or

Draft Document, to FAA Office of Airports or other FAA organizations for review prior to publishing.. It can take several weeks or months before FAA ATRD receives feedback or recommended changes to these documents/deliverables. The purpose of this Subtask is for the contractor to revisit previous documents/deliverables and revise the documents/deliverables based on FAA feedback.

3.1.2.1. The FAA ATRD will provide Technical Direction to the contractor to revise the documents/deliverables.

3.1.2.2. The contractor will submit the revised documents/deliverables as a new deliverable.

3.1.3. Subtask 3 – UAS Operations and Maintenance. The contractor must make the following UAS operations and maintenance services available to the FAA ATRD, at any time during this Task Area’s period of performance, to support this Task

Area. The contractor may consider third party suppliers, such as academia, private

UAS service providers, or the FAA’s UAS Test Sites.

3.1.3.1. The contractor must provide certified, current, and proficient UAS pilots on various UAS platforms, from different manufacturers. UAS pilots must be certificated under Title 14 CFR Part 107, Small Unmanned

Aircraft Systems.

3.1.3.1.1. Various types of UAS platforms, examples include, but are not limited to: rotorcraft, fixed wing, hybrid, ornithopter, swarms or other.

3.1.3.2. Numerous different types of UAS platforms, and their proficient UAS pilots, must be made available to the FAA ATRD, according to test plans and upon ATRDs request, to meet the requirements in this Task Area.

This may include UAS listed in 3.1.3.1.1, or other new types of UAS platforms that are developed in the future.

3.1.3.2.1. The contractor must be knowledgeable and up-to-date on new and emerging UAS platforms and payloads that may be tested and evaluated against UAS detection and mitigation technologies/systems.

3.1.3.2.2. The contractor must provide duplicate platforms/payloads, to meet the requirements in the test plans, and upon the request of the FAA ATRD.

3.1.3.2.3. The FAA will not be financially responsible for UAS platforms, payloads, and accessories that are damaged during this Task

Area, except UAS platforms that are specifically damaged during UAS mitigation technology testing with the objective to disable the UAS platform according to the test plans.

3.1.3.2.3.1. Examples of non-replacement: Operator error, mechanical failure, third-party inadvertent interaction, weather, etc.

3.1.3.2.3.2. Examples of replacement: UAS platforms/

payloads/accessories damaged by mitigation technology such as directed energy, physical damage, and/or those technologies outlined in the test plan.

3.1.3.3. UAS pilots must have an in-depth knowledge and experience with airport operations and the NAS.

3.1.3.4. UAS pilots must have knowledge and experience with planning, coordinating, and executing UAS operations on and within the vicinity of an airport and within controlled and uncontrolled airspace.

3.1.3.5. UAS pilots must have knowledge and experience with obtaining the necessary waivers, authorizations, permits, approvals, etc. in-order to conduct UAS operations on and within the vicinity of an airport and within controlled and uncontrolled airspace. The contractor will be responsible for seeking these necessary documents as required to support this SOW.

3.1.3.6. The contractor must maintain and provide the following documents to the

FAA ATRD and their collaborators upon request:

3.1.3.6.1. UAS Safety Plan

3.1.3.6.2. UAS Operator Training Records

3.1.3.6.3. UAS Operator Pilot Certificates

3.1.3.6.4. UAS Maintenance Plan/Records

3.1.3.6.5. UAS Flight Logs

3.1.3.6.6. Other Operational, Maintenance, and Safety Documents

3.1.3.7. The contractor must provide the appropriate number of visual observers as required to operate UAS.

3.1.3.8. The contractor must coordinate with local stakeholders and communities of interest to inform them of operations as to not interfere with operational testing.

3.1.3.9. The contractor must meet the necessary insurance requirements, required by the test airport, to conduct UAS operations on airport and within controlled/uncontrolled airspace

3.1.3.10. Technical direction may be provided for specific requirements not already defined for this Subtask.

3.1.4. Subtask 4 – Communications, Briefings, Messaging. The contractor must be able to develop professional communications products and program support materials in support of FAA ATRD. Final products may be delivered to FAA in electronic, web-based, or traditional / print formats, and may include quick turnaround professional briefings, presentations, diagrams/illustrations, information pamphlets and other media, worksheets, program branding and templates, marketing materials, web-based communications, media outputs, etc., as needed for FAA ATRD. These products are often used for briefing during industry meetings, public outreach, briefing senior management, etc. The contractor must determine the suitability of communications products and program materials for target audiences, update and review materials for consistency, and for format, flow, and structural integrity.. The contractor may consider third party expertise with in depth understanding of FAA

AOC branding guidelines, FAA plain language best practices, FAA AIT standards, and with experience in developing and outputting high quality products within short timeframes.

3.1.4.1. The FAA will provide all necessary materials and sources for the development of such products.

3.1.4.2. The FAA will provide Technical Direction for specific requirements and products as needed to support this Subtask.

3.1.4.3. Other direct costs as needed and pre-approved by the FAA for high volume brochure printing and/or any conference products or materials.

3.1.4.4. Travel costs as needed and preapproved by the FAA.

3.2. Task Area-2: UAS Airport Applications. The contractor must provide project management support, technical/subject matter expertise, and UAS operations and maintenance services to support the FAA ATRD with conducting research to enable the reliable and effective integration of UAS into the airport environment, for improved safety and efficiency. The FAA ATRD has identified six core applications for use of UAS in the airport environment, listed in order of priority: Obstruction Analysis, Airfield Pavement

Inspections, Wildlife Hazard Management, Perimeter Security, Aircraft Rescue and

Firefighting, and Other Related UAS Airport Safety Applications/UAS Airport

Integration Program Planning.

In this Task Area, the contractor must conduct research, testing, evaluations, assessments, outreach, literature reviews, etc. to develop standard processes and procedures and sensor technology (payload) performance specifications to consistently conduct safe, reliable, and effective UAS airport applications.

This project will require collaborating with other FAA lines of business, various government agencies, airports, vendors, and other contractors and subject matter experts that will support this project.

3.2.1. Subtask 1 – Support.

3.2.1.1. The contractor must provide the support described in Section 2

GENERAL REQUIREMENTS of this SOW to accomplish this Subtask.

3.2.1.2. The contractor must perform the necessary program/project management tasks/activities to support this Subtask, which includes, but is not limited to:

3.2.1.2.1. Providing the necessary contract support staff to support this

Subtask.

3.2.1.2.2. Preparing and maintaining project schedules using project management tools.

3.2.1.2.3. Coordinating and collaborating with all parties involved in the research, testing, evaluations, assessments, outreach, literature reviews etc. of UAS airport applications.

3.2.1.2.3.1. This may include, but not limited to: various

FAA organizations, airport operators, other support contractors, other stakeholders, federal, state, or local governmental organizations, law enforcement, vendors, etc.

3.2.1.2.4. Scheduling meetings and preparing/distributing meeting agendas, meeting minutes, and action items.

3.2.1.2.5. Providing status updates on task area related activities.

3.2.1.2.6. Preparing project plans, test plans, presentation materials, reports, program/safety related analyses, and other deliverables, requested by the COR.

3.2.1.2.7. Providing and addressing edits/comments to reports, plans, and other documents and deliverables.

3.2.1.2.8. Updating reports and technical documents, as requested by the

COR.

3.2.1.2.9. Processing and analyzing data collected that was collected by the FAA and their collaborators.

3.2.1.2.10. The contractor must archive all information, minutes, notes, plans, data, etc. into a central depository that is available for the FAA ATRD and their collaborators.

3.2.1.3. The contractor must conduct the necessary research, testing, evaluations, assessments, outreach, literature reviews, etc. necessary to develop standard processes and procedures and sensor technology (payload) performance specifications for each of the FAA’s UAS airport applications, listed below:

Obstruction Analysis

Airfield Pavement Inspections** (reference note, below)

Wildlife Hazard Management** (reference note, below)

Perimeter Security

Aircraft Rescue and Firefighting

Other Related UAS Airport Safety Applications** (reference note, below)

/ UAS Airport Integration Program Planning

**Please note the FAA’s collaborators and partners are conducting research on the use of UAS for airfield pavement inspections, wildlife hazard management, and other airport safety related applications. The contractor may be asked to provide project management support and technical/subject matter expertise to assist with these projects. In addition, the contractor may be required to support ATRD with leading research, testing, and evaluations on new/emerging UAS airport safety applications

(i.e. ‘Other Related UAS Airport Safety Applications’). Technical direction will be provided for the specific requirements for these applications.

3.2.1.4. The contractor must prepare and submit project plans on how they plan to execute the research, testing, evaluations, assessments, outreach, literature reviews, etc. for each UAS airport application.

3.2.1.5. The contractor must develop the ‘framework’ for processes and procedures and UAS sensor technology (payload) performance specifications for each

UAS airport application with the objective to create performance standards and FAA guidance language (e.g. Engineering Briefs, CertAlerts, Advisory Circulars, etc.). This document must be updated continuously throughout the research effort.

3.2.1.5.1. The contractor must leverage interim/completed UAS airport applications/related research to create this deliverable.

3.2.1.5.2. The contractor must perform planning and coordination efforts in preparation for UAS airport application testing and evaluations. This includes, but is not limited to, participating in airport site surveys and determining/obtaining the necessary authorizations and permits/waivers required to test and evaluate UAS on and within the vicinity of airports (for UAS airport applications).

3.2.1.5.2.1. The contractor must perform/support and

document a hazard/risk analysis/assessment and other safety related analyses/assessments prior to conducting UAS airport applications testing/evaluations, as required by the

COR/airport.

3.2.1.5.2.2. The contractor must perform/support and

document spectrum interference testing at each airport/test location, as required by the COR.

3.2.1.5.3. The contractor must develop a methodology and ranking criteria for selecting UAS platforms and sensor technologies

(payloads) for testing and evaluating (for each UAS airport application).

3.2.1.5.4. The contractor must submit individual test plans for each UAS airport application, upon acceptance of each project plan.

3.2.1.5.4.1. The contractor must execute test plans for each

application.

3.2.1.5.4.2. The contractor must review, analyze, and

report on the data collected during the test and evaluation period.

3.2.1.5.5. The contractor must work closely with the FAAs collaborators on this subtask.

3.2.1.5.6. The contractor must fully document all UAS airport application research, testing, evaluations, assessments, outreach, literature reviews etc. performed under this Task Area.

3.2.1.5.7. The contractor may be asked to participate in UAS airport application testing and evaluations, demonstrations, and/or, operations (sometimes in short notice).

3.2.1.5.8. The FAA ATRD may provide technical direction for other duties as needed/assigned by the FAA ATRD in support of this

Task Area.

3.2.1.5.9. The FAA ATRD will provide technical direction for the specific requirements not already defined for this subtask.

3.2.1.5.10. The contractor must document all necessary information to support this Task Area.

3.2.1.5.11. The contractor must continually review and analyze the data being collected and prepare draft FAA guidance documents

(e.g. Engineering Brief, CertAlerts, Advisory Circulars, etc.)

language that describes standard processes and procedures and sensor technology (payload) performance specifications (i.e.

performance criteria) for each of the FAA’s UAS airport applications.

3.2.2. Subtask 2 – Revise Documents/Deliverables. The FAA ATRD often submits documents/deliverables to The FAA Office of Airports or other FAA organizations for review prior to publishing such as a Presentation, Final Report, Technical Note, or Draft Document. It can take several weeks or months before FAA ATRD receives feedback or recommended changes to these documents/deliverables. The purpose of this Subtask is for the contractor to revisit a previous document/deliverable and revise the document/deliverable based on FAA feedback

3.2.2.1. The FAA ATRD will provide Technical Direction to the contractor to revise a document/deliverable.

3.2.2.2. The contractor will submit the revised document as a new deliverable.

3.2.3. Subtask 3 – UAS Operations and Maintenance. The contractor must make the following UAS operations and maintenance services available to the FAA ATRD, at any time during this Task Area’s period of performance, to support this Task

Area. The contractor may consider third party suppliers, such as academia, private

UAS service providers, or the FAA’s UAS Test Sites.

3.2.3.1. The contractor must provide certified, current, and proficient UAS pilots on various UAS platforms, from different manufacturers. UAS pilots must be certificated under Title 14 Code of Federal Regulations (CFR) Part 107, Small Unmanned Aircraft Systems.

3.2.3.1.1. Various types of UAS platforms, examples include, but are not limited to: rotorcraft, fixed wing, hybrid, ornithopter, or other.

3.2.3.2. The contractor must provide numerous types of UAS platforms and payloads, as well as proficient UAS pilots on each platform/payload, to meet the requirements in this Task Area and when requested by ATRD.

3.2.3.3. The contractor must provide both tethered and un-tethered UAS, for testing and evaluations.

3.2.3.4. The contractor must be knowledgeable and up-to-date on new and emerging UAS platforms and payloads that may be tested and evaluated for each UAS airport application.

3.2.3.5. The contractor must provide duplicate platforms/payloads, to meet the requirements in the test plans, and upon the request of ATRD.

3.2.3.6. The FAA will not replace UAS platforms/payloads/accessories that are damaged during this Task Area.

3.2.3.6.1. Examples of non-replacement: Operator error, mechanical failure, third-party inadvertent interaction, weather, etc.

3.2.3.7. The contractor must provide UAS pilots that have an in-depth knowledge and experience with airport operations and the NAS.

3.2.3.8. The contractor must provide UAS pilots that have knowledge and experience with planning, coordinating, and executing UAS operations on and within the vicinity of an airport and within controlled and uncontrolled airspace.

3.2.3.9. The contractor must provide UAS pilots that have knowledge and experience with obtaining the necessary waivers, authorizations, permits, approvals, etc. in-order to conduct UAS operations on and within the vicinity of an airport and within controlled and uncontrolled airspace.

3.2.3.10. The contractor must maintain and provide the following documents to the

FAA ATRD and their collaborators upon request:

3.2.3.10.1. UAS Safety Plan

3.2.3.10.2. UAS Operator Training Records

3.2.3.10.3. UAS Operator Pilot Certificates

3.2.3.10.4. UAS Maintenance Plan/Records

3.2.3.10.5. UAS Flight Logs

3.2.3.10.6. Other Operational, Maintenance, and Safety Documents

3.2.3.10.7. The contractor must provide the appropriate number of visual observers as required to operate the UAS.

3.2.3.11. The contractor must coordinate with local stakeholders and communities of interest to inform them of operations as to not interfere with operational testing.

3.2.3.12. The contractor must meet the necessary insurance requirements, required by the test airport, to conduct UAS operations on airport and within controlled/uncontrolled airspace.

3.2.3.13. Technical direction may be provided for specific requirements not already defined for this Subtask.

3.2.4. Subtask 4 - Communications, Briefings, Messaging. The contractor must be able to develop professional communications products and program support materials in support of FAA ATRD. Final products may be delivered to FAA in electronic, web-based, or traditional / print formats, and may include quick turnaround professional briefings, presentations, diagrams/illustrations, information pamphlets and other media, worksheets, program branding and templates, marketing materials, web-based communications, media outputs, etc., as needed for FAA ATRD. These products are often used for briefing during industry meetings, public outreach, briefing senior management, etc. The contractor must determine the suitability of communications products and program materials for target audiences, update and review materials for consistency, and for format, flow, and structural integrity. The objective is to design and develop a highly informative and visually rich product under short turnarounds. The contractor may consider third party expertise with in depth understanding of FAA AOC branding guidelines, FAA plain language best practices, FAA AIT standards, and with experience in developing and outputting high quality products within short timeframes.

3.2.4.1. The FAA will provide all necessary materials and sources for the development of such products.

3.2.4.2. The FAA will provide Technical Direction for specific requirements and products as needed to support this Subtask.

3.2.4.3. Other direct costs as needed and pre-approved by the FAA for high volume brochure printing and/or any conference products or materials.

3.2.4.4. Travel costs as needed and preapproved by the FAA.

4. DELIVERABLES AND SCHEDULE

4.1 Task Area 1: UAS Detection and Mitigation Technologies/Systems

Deliverable

Number Deliverable Name Deliverable Description

Deliverable

Date

4.1.1. Meeting Minutes

Detailed meeting minutes from each meeting

24 hours following each meeting.

4.1.2 Monthly Reports

As defined in Section 5 General

Reporting Requirements

Fifth (5th) business day of each month

4.1.3 Task Area Schedule

Develop and maintain program

& project(s) schedule in Gantt chart format.

Submitted during every

Monthly

Report, and whenever there is a change in schedule

4.1.4 Project Plans

As defined in Section 5 General

Reporting Requirements. The

Project Plans will be used to execute the objectives of the test for each UAS technology/system testing at each airport or designated location.

Issued through

COR Technical

Direction

4.1.5 Test Plans

As defined in Section 5 General

Reporting Requirements. The

Test Plans will be used for each

UAS technology/system testing at each airport or designated location.

Issued through

COR Technical

Direction

4.1.6 Interim Technology

Report - Outlines

Submit an outline/framework of the sections that will be within the Interim Reports.

Five (5) business days after the completion of the test/evaluation at ACY

4.1.7 Interim Reports

As defined in Section 5 General

Reporting Requirements. An

Interim Report of each technology/system at the conclusion of each evaluation at each location.

28 calendar days following each test/evaluation

4.1.8 Phase 1 and 2 - Outlines

Submit an outline/framework of the sections that will be within

Phase 1 Draft Final Report and

Phase 2 Draft Final.

Five (5) business days following the completion of each phase

4.1.9 Phase 1 Draft Final

Report

As defined in Section 5 General

Reporting Requirements.

60 calendar days following the completion of phase 1 test/evaluation

4.1.10 Phase 1 Final Report

As defined in Section 5 General

Reporting Requirements. This final report must incorporate/address FAA’s edits/comments to deliverable

4.1.9.

15 calendar days following receipt of FAA edits/comments

4.1.11 Phase 2 Draft Final

Report

As defined in Section 5 General

Reporting Requirements.

60 calendar days following the completion of phase 2

4.1.12 Phase 2 Final Report

As defined in Section 5 General

Reporting Requirements. This final report must incorporate/address FAA’s edits/comments to deliverable

4.1.11.

15 calendar days following receipt of FAA edits/comments

4.1.13 Summary Report -

Outline

Submit an outline/framework of the sections that will be within the Summary Reports.

Issued through

COR Technical

Direction

4.1.14 Summary Draft Final

Report Reports

As defined in Section 5 General

Reporting Requirements. The

Summary Report is a consolidated and abbreviated report that must include but is not limited to: Phase 1 and Phase

2 overall findings recommendations, lessons learned, considerations, draft performance specifications, operations, and usability requirements and responses within the vicinity of an airport.

The objective of this report is an abbreviated version of a large volume Comprehensive Report.

Issued through

COR Technical

Direction

4.1.15 Summary Final Reports

As defined in Section 5 General

Reporting Requirements. The

Summary Report is a consolidated and abbreviated report that must include but is not limited to: Phase 1 and Phase

2 overall findings recommendations, lessons learned, considerations, draft performance specifications, operations, and usability requirements and responses within the vicinity of an airport.

The objective of this report is an abbreviated version of a large volume comprehensive report.

This final report must incorporate/address FAA’s edits/comments to deliverable

4.1.14.

Issued through

COR Technical

Direction

4.1.16

Comprehensive UAS

Detection and

Mitigation

Technologies/System

Draft Final Report -

Outline

Submit an outline/framework of the sections that will be within the Comprehensive UAS

Detection and Mitigation

Technologies/System Final

Report.

Issued through

COR Technical

Direction

4.1.17

Comprehensive UAS

Detection and

Mitigation

Technologies/System

Draft Final Report

As defined in Section 5 General

Reporting Requirements. The comprehensive final report is a large volume and detailed comprehensive report of the entire FAA research effort in this

Task Area.

Issued through

COR Technical

Direction

4.1.18

Comprehensive UAS

Detection and

Mitigation

Technologies/System

Final Report

As defined in Section 5 General

Reporting Requirements. The comprehensive final report is a large volume and detailed comprehensive report of the entire FAA research effort in this

Task Area. This final report must incorporate/addresses FAA’s edits/comments to deliverable

4.1.17

Issued through

COR Technical

Direction

4.1.19 Draft Guidance

Documents

Provide a written framework and draft of new advisory circulars

Issued through

4.1.20 Revise

Documents/Deliverables

As defined in Section 5 General

Reporting Requirements. See

Task Area 1, Subtask 2.

Issued through

COR Technical

Direction

4.1.21 Presentation Materials

As defined in Section 5 General

Reporting Requirements.

Issued through

COR Technical

Direction

4.1.22 Data Strategy

As defined in Section 5 General

Reporting Requirements.

Issued through

4.2 Task Area 2: UAS Airport Applications

Deliverable

Number Deliverable Name Deliverable Description Deliverable Date

4.2.1 Monthly Report

As defined in Section 5 General

Reporting Requirements

Fifth (5th) business day of each month

4.2.2 UAS Airport

Application Schedule

Develop and maintain program

& project(s) schedule, for each airport application, in Gantt chart format.

Submitted during every Monthly

Report, and whenever there is a change in schedule

4.2.3 Project Plans

As defined in Section 5 General

Reporting Requirements. The

Project Plans will be used to execute the objectives of each

UAS Airport Application.

Issued through

COR Technical

Direction

4.2.4

Test Plans

As defined in Section 5 General

Reporting Requirements. The

Test Plans will be used for each

UAS Airport application.

Issued through

COR Technical

Direction

4.2.5 UAS Airport

Application

Specifications

Framework for each UAS

Airport Applications Processes and Procedures and Technology

Performance Specifications

Issued through

COR Technical

Direction

4.2.6 Interim Report -

Outlines

Submit an outline/framework of the sections that will be within the Interim Reports.

Issued through

COR Technical

Direction

4.2.7

Draft Interim Reports

As defined in Section 5 General

Reporting Requirements. An

Interim Report of each UAS airport application research.

Issued through

COR Technical

Direction

4.2.8

Final Draft Report

Outlines

Submit an outline/framework of the sections that will be within

Draft Final Report.

Five (5) business days after the completion of a test/evaluation

4.2.9

Draft Final Report

As defined in Section 5 General

Reporting Requirements. Draft

Final Reports are required for each UAS Airport Application.

90 calendar days following the final

UAS airport application test

4.2.10

Final Reports

As defined in Section 5 General

Reporting Requirements. Final

Reports are required for each

UAS Airport Application. This final report must incorporate/address FAA’s edits/comments to deliverable

4.2.9.

15 calendar days following receipt of FAA edits/comments

4.2.11 Summary Final Report

Outline

Submit an outline/framework of the sections that will be within

Summary Final Report.

Issued through

COR Technical

Direction

4.2.12

Draft Summary Final

Reports

As defined in Section 5 General

Reporting Requirements. The

Summary Report is a consolidated and abbreviated final report.

Issued through

COR Technical

Direction

4.2.13

Final Summary Reports

As defined in Section 5 General

Reporting Requirements. The

Final Summary Report is a consolidated and abbreviated final report and must incorporate/address FAA’s edits/comments to deliverable

4.1.12

Issued through

COR Technical

Direction

4.2.14

Summary Final Reports

As defined in Section 5 General

Reporting Requirements. The

Summary Report is a consolidated and abbreviated final report.

Issued through

COR Technical

Direction

4.2.15 Draft Guidance

Documents

Provide a written framework and draft of new guidance documents.

Issued through

COR Technical

Direction

4.2.16 Revise

Documents/Deliverables

As defined in Section 5 General

Reporting Requirements. See

Task Area 2, Subtask 2.

Issued through

COR Technical

Direction

4.2.17

Presentation Materials As defined in Section 5 General

Reporting Requirements.

Issued through

5. GENERAL REPORTING REQUIREMENTS

5.1. All deliverables must be submitted by email to the COR(s) as outlined in Section 4, Deliverables and Schedule. Secured large file transfer sites may be used for downloads.

FAA servers are limited to a total of a 10 MB email size. All written deliverables must be delivered in electronic format in Microsoft Office applications or later, or other method approved by the COR. Preparation of the reports must be in accordance with, FAA Order

CT 1710.2B, “Preparation & Issuance of Formal Reports, Technical Notes, & Other

Documentation” (effective 2/01/1990). The FAA will provide report templates for the contractor. The contractor must, when requested by the FAA COR, provide the FAA with the necessary documentation or presentation materials to support any of the UAS activity within this SOW.

5.1.1. Monthly Reports - The contractor must submit a monthly summary progress report.

Monthly reports must summarize the project status and must include the following information:

Project status (significant milestones/activities, current status, next steps)

Technical accomplishments, including interim test results

Planned activities

Schedule changes

Meetings and travel*

Figures, images, photographs, etc.

Aggregate data summary of testing (Examples: number of tests, operations, detections, etc.)

Problems that need to be discussed with the COR.

*For travel that occurred during the reporting period, the contractor must submit a detailed trip report (with monthly report) summarizing the trip.

5.1.2 Project Plans – The contractor must submit a Project Plans that will be used to guide both project execution and project control of each UAS technology/system and airport application testing at each airport or designated location.

5.1.3 Test Plans – The contractor must submit a Test Plans detailing the following but not limited to: objectives, resources, processes, procedures, test cards, operations, responsibilities, workflow, personnel, graphs etc.

5.1.4 Interim Reports – The contractor must submit an Interim Report at the conclusion of each UAS technology/system and airport application test at each airport or designated location. The Interim Report must report, but is not limited to: overall summary, aggregate data, finding/results, conclusions, and recommendations.

5.1.5 Draft Final & Final Reports – The contractor must provide a complete Draft Final

Report as outlined in Section 4. The Government will provide a thorough review of each report with electronic review comments/changes within sixty (60) calendar days of delivery. The contractor must then incorporate the FAA review comments/changes prior to submitting a Final Report. An electronic copy of the

Final Report must then be delivered within fifteen (15) calendar days of receipt of the Government review.

5.1.6 Summary Reports – The Summary Report is a consolidated and abbreviated version of a Draft/Final Report.

5.1.7 Draft Guidance Documents – It is expected that the contractor will develop multiple draft FAA Guidance Documents based upon the research efforts under this SOW.

The contractor must use the current FAA formats.

5.1.7.1 Task Area 1: UAS Detection and Mitigation Systems

Technologies/Systems - The purpose of the Guidance Documents is to inform airport operators of the performance standards and best practices for the selection and deployment of UAS detection and mitigation technologies/systems in the airport environment.