SOW for Vertiport Design Research v3.3 12-15-2023-Draft for SAM.pdf
PDF 194 KB Posted
- Attached to
- Vertiport Design
- Solicitation number
- 692M15-24-Vertiport
About this file
This statement of work outlines requirements for research support related to the development of guidance for vertiport design standards. The contractor will conduct operational testing of electric vertical takeoff and landing aircraft with up to two original equipment manufacturers to support an update to Engineering Brief #105. Additional live aircraft testing and simulator-based testing will be performed with multiple eVTOL OEMs within defined aircraft category types to inform the creation of a new Vertiport Design Advisory Circular. Deliverables include project plans, detailed test plans, memo reports summarizing test findings, and a final report. The period of performance is from February 15, 2024 through February 14, 2026. The selected contractor must have the ability to obtain a Personal Identity Verification card for access to the FAA network.
View the file
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
FEDERAL AVIATION ADMINISTRATION
STATEMENT OF WORK
December 13, 2023
Contract Name: Vertiport Design Research Contract No: TBD Research Program Area (RPA): S1.5 VTOL Task Order No: TBD Task Area: TBD Description of Work: Vertiport Design Research Support
1. BACKGROUND
In September of 2020, the Airport Technology R&D (ATR) Branch initiated a research project under BAA topic number ARAS0001 “Vertiport Design for eVTOL”. The purpose of that effort was to “Study and develop recommendations for vertiport design standards for electrical vertical takeoff and landing (eVTOL) aircraft. That research led to extensive engagement with a limited number of eVTOL original equipment manufacturers (OEM)s that required establishment of individual non-disclosure agreements with each OEM.
Since that time, the eVTOL market has matured and evolved and, in many respects, has become much more well-defined than it was when ATR’s research began. Together with the results of the BAA effort, these changes in the market have influenced the FAA’s Office of Airport Standards (AAS) to expand the scope of ATR’s research to address additional factors affecting vertiport design standards. Some of the considerations within the expanded scope include addition of larger aircraft i.e. > 7500lbs, autonomous operations, propulsion such as hydrogen and electric-hybrid, and short take-off and landing (STOL) electric aircraft.
2. PURPOSE
This SOW describes an effort to support the creation of guidance for public and private vertiports and vertistops, including modification of existing helicopter and airplane landing facilities, and establishment of new sites. This effort is focused on VTOL aircraft performance, vertiport infrastructure, and the collection of validated helicopter data to update Vertiport Design Engineering Brief #105 and to create the draft version of the Vertiport Design Advisory Circular
(AC).
3. OBJECTIVES
3.1. eVTOL Aircraft Operational Testing [See Section 5.2.1]
3.2. eVTOL Aircraft Simulator-based Testing [See Section 5.3]
3.3. Update the Vertiport Design Engineering Brief #105 [See Section 5.4]
3.4. Create the draft version of the Vertiport Design Advisory Circular [See Section 5.5]
4. GENERAL REQUIREMENTS
The contractor must provide the technical expertise to evaluate eVTOL performance characteristics and their impact on Vertiport design. This research will support the definition of minimum standards in the upcoming Vertiport Design AC for different levels of aircraft performance. The Vertiport Design AC is expected to be published by the end of 2025 and therefore data collection activities from operational and simulation testing must be concluded by early 2025 to allow for review and publication processes required. Other activities may continue into 2025. The AC should include the following at a minimum:
4.1. Vertiport Design Geometry
4.2. Taxiway and Taxi-lane Design
4.3. Aprons and Parking
4.4. Marking, Lighting and Visual Aids
4.5. Charging and Electric Infrastructure
4.6. On-Airport Vertiports
4.7. Site Safety Elements
5. SPECIFIC REQUIREMENTS
5.1. Project Plan
5.1.1. A master project plan will be created in Microsoft Project format that details the schedule and tasks required to meet the deliverable milestones listed in Section 6.
5.2. Operational Testing of eVTOL Aircraft
Live testing with OEM aircraft is required for the development of both the updated EB 105 and the creation of a new Vertiport Design Advisory Circular. Testing under this contract will supplement testing that has occurred under previous agreements.
5.2.1. Operational Testing to support EB 105 update
The contractor must conduct operational testing with up to two specific OEMs to support the update to EB 105. These operational tests will include landing precision measurements and hover capabilities. The contractor will deliver a memo report documenting the testing activities including results and findings.
5.2.1.1. Detailed Test Plan - A detailed test plan will be delivered for each OEM test. Test cases, aircraft maneuvers, goals, data to be collected, and method to analyze the data will be included in the test plans for each vendor at a minimum.
5.2.1.2. Memo Reports - A separate memo report will be delivered (1) month after the conclusion of each OEM aircraft test. This memo report will document testing activities and include the data analysis results and findings identified in the detailed test plan at a minimum.
5.2.1.3. EB 105 Update Report – The contractor will deliver a final test report summarizing all findings and recommendations from OEM testing performed to date including testing activities conducted under previous agreements.
5.2.2. Operational Testing to support new Advisory Circular for Vertiport Design
The contractor must conduct live aircraft testing with OEMS to include taxiing procedures and turn radius (with wheeled aircraft), landing precision/scatter, approach and departure profiles, and downwash/outwash (DWOW) measurements. Different vendors may be introduced, and the exclusion of certain vendors may occur at the FAA’s discretion. Testing may be repeated for certain vendors as aircraft designs mature.
Operational testing opportunities are contingent upon the availability of each OEM. The contractor must be able to respond to short lead times (i.e., 3 to 4 weeks) to coordinate, plan, and conduct testing at locations within the entire continental US.
There is the potential that two OEM aircraft may be available at the same time and that simultaneous testing activities would be required at separate locations.
In addition, some international testing may be required to be supported by the contractor.
The lead time and logistics of international trips will be determined on a per case basis.
The current OEM aircraft fall within the following categories. The goal of this part of the research is to evaluate the performance characteristics of these category types at the discretion of the FAA.. Additionally, there may be more than one OEM with in each of the following categories:
• Multicopter/Ultralight propulsion system
• Multicopter propulsion system
• Lift and Cruise propulsion system
• Vectored thrust/autonomy propulsion system
• Vectored thrust propulsion system
• Vectored thrust/Ducted fan propulsion system
• Some STOL aircraft (vendor(s) to be determined)
• Helicopters
5.2.2.1. Detailed Test Plan - A detailed test plan will be delivered for each OEM test. Test cases, aircraft maneuvers, goals, data to be collected, and method to analyze the data will be included in the test plans for each vendor at a minimum.
5.2.2.2. For testing that occurs at an airport, the contractor will submit required documentation and facilitate all communication and coordination necessary to conduct each test with each respective airport.
5.2.2.3. Memo Reports – A separate memo report will be delivered (1) month after the conclusion of each OEM aircraft test. This memo report will document testing activities and include the data analysis results and findings identified in the detailed test plan at a minimum.
5.3. Simulator-based Testing of eVTOL aircraft
5.3.1. This OEM simulator-based aircraft testing will be utilized to evaluate how aircraft operations affect the design of vertiport facilities. Specifically, simulator-based testing will evaluate aircraft performance during emergency scenarios and critical failures, autonomous operations, operations during Instrument Flight Rules (IFR), and simultaneous operations of multiple eVTOL aircraft at a common location.
The following aircraft category types will be tested pending the OEMs’ willingness to participate and the availability of OEM-developed simulators. Different vendors may be introduced, and the exclusion of certain vendors may occur at the FAA’s discretion. Testing may be repeated for certain vendors as aircraft designs mature.
• Multicopter/Ultralight propulsion system
• Multicopter propulsion system
• Lift and Cruise propulsion system
• Vectored thrust/autonomy propulsion system
• Vectored thrust propulsion system
• Vectored thrust/Ducted fan propulsion system
• Some STOL aircraft (vendor(s) to be determined)
5.3.2. Detailed Test Plan - A detailed test plan will be delivered for each OEM test. Test cases, goals, data to be collected, and method to analyze the data will be included in the test plans for each vendor at a minimum.
5.3.3. Memo Reports – A separate memo report will be delivered (1) month after the conclusion of each OEM aircraft simulator tests. This memo report will document testing activities and include the data analysis results and findings identified in the detailed test plan at a minimum.
5.4. Support Update to Vertiport Design Engineering Brief #105
5.4.1. During operational testing that supports the AC (Section 5.2.2), the contractor will support the process of updating EB 105 including adjudication of comments resulting from internal FAA, and industry review periods. This support will occur concurrently during the timeframe that operational testing is being conducted. The contractor will attend meetings, review comments and participate in comment adjudication activities.
5.5. Deliver a final report that informs the creation of the Vertiport Design Advisory Circular
5.5.1. The Vertiport Design Advisory Circular will be created based on updated version of Vertiport Design Engineering Brief #105. The new Advisory Circular should include at a minimum: Vertiport Design Geometry; Taxiway and Taxi-lane Design;
Aprons and Parking; Marking Light, and Visual Aids; Charging and Electrical Infrastructure; On-Airport Vertiports; and Site Safety Elements. It should be noted that hydrogen charging and infrastructure research is currently being conducted by ATR but is not currently planned to be included in this version of the Advisory Circular.
The contractor will support the process of creating the Advisory Circular including adjudication of comments resulting from internal FAA, and industry review periods.
This support will occur after the delivery of the Final Report. The contractor will attend meetings, review comments, and participate in comment adjudication activities.
5.6. Protection of intellectual property
5.6.1. OEM data may be proprietary and or commercially confidential. The Contractor must establish and implement measures that protect OEM intellectual property prior to testing activities, including protection of data that may be or reveal proprietary or commercially confidential information.
6. DELIVERABLES AND SCHEDULE
Task No. Deliverable Date(s) Description
5.1 Contract Award + 10 work days Project Plan
5.2.1.1 10 working days before each live operational test (EB support)
Detailed Test Plan
5.2.1.2 Conclusion of each live
operational test in support of EB
105 + 20 work days
Memo Reports
5.2.1.3 May 10, 2024 EB 105 Update Report
5.2.2.1 10 working days before each live operational test (AC support)
Detailed Test Plan
5.2.2.3 Conclusion of each live
operational test in support of AC
+ 20 work days
Memo Reports
5.3.2 10 working days before each simulation test
Detailed Test Plan
5.3.3 Conclusion of each simulation
test in support of eVTOL
Advisory Circular + 20 work days
Memo Reports
5.5 March 30, 2025 Final Report
7. GENERAL REPORTING REQUIREMENTS
7.1. Biweekly Teleconferences – The Contractor will discuss the current status of the report including interim findings and share interim versions of the report to solicit early feedback from ATR.
7.2. Report Guidance
7.2.1. An Executive “Mini deck” providing an executive summary of the report content will be included with each final report deliverable. This is not required for the memo report deliveries.
7.2.2. Report Template
The FAA will provide the contractor with the most recent version of the previously created EMAS Signage Simulation Report. This version will be used as the starting point for this task.
All updates will be made to this version of the report.
7.2.3. General Guidance
The contractor must be peer reviewed and proofread for content, clarity, organization, spelling, and math; For example, consider the following:
a. Does the report clearly reflect the objectives of the research?
b. Is the report organized well?
c. Are the relevant points of the research addressed?
d. Are the conclusions drawn logical outcomes or recommendations?
e. Are the main points properly explained? Are examples provided?
f. Is the sequence of events correct?
g. Do the figures and tables used in the document provide clarification for the points in the text?
h. Is the report written in plain language? Are the ideas conveyed in a clear, concise, and comprehensible manner?
i. Do the paragraphs and sections transition logically to the next?
j. Is the spelling correct? Is the math correct?
k. Are tradenames used? If so, are they necessary to the report? Are they marked properly?
l. Is cited work properly cited with the proper reference provide, i.e., title, author, date, etc.?
8. PERIOD OF PERFORMANCE
The Period of Performance is from 2/15/2024 to 2/14/2026. [i.e. Award + 2 years]
9. SECURITY
Contractors needing access to the FAA network must be eligible for and obtain a PIV card.
File details come from the government source that posted it. Updated .