FA8650-18-S-2001-Atch5.pdf

FA8650-18-S-2001

Attachment 5

STATEMENT OF OBJECTIVES (SOO)

TASK ORDER 0001

Design, Analysis, and Testing of Multi-Disciplinary Aerospace System Technologies

1.0 BACKGROUND: It is anticipated that parts of this task order will build on previous research efforts. For example a tailless design project has already developed a design process, so design studies and relevant wind tunnel testing are potential projects that could be proposed under this new task. Design methods for structures with integrated smart material actuation have been studied in the context of energy efficiency, mechanical advantage, and resistance to external loads for basic aerospace structural components, mechanisms, and systems. For example, a biologically-inspired topology optimization scheme has previously been used to create alternative structural layouts for a generic fighter wing concept, as well as for scaled aeroelastic test models utilizing spatial variations in material properties to tailor aeroelastic response parameters. Optimization methods have also been used to address origami-based morphing concepts. Unique sensors and actuators have been applied to dynamic systems to tailor performance and response, and the impact of integration of these devices as compared to conventional systems has been evaluated. This task order will continue work in similar areas through examination of technologies in a design/analyze/build/test context.

2.0 OBJECTIVE: The objectives of this task are to mature multi-disciplinary multi-functional technologies and associated methods and processes that enable revolutionary air vehicles through design, analysis, fabrication, and test activities. The technologies of interest include, but are not limited to, advanced airframe concepts that embed non-structural components within load bearing structure, innovative control effectors for tailless supersonic aircraft, reconfigurable or morphing load-bearing structures, compliant mechanisms, fly-by-feel technologies, development and application of methods to analyze and exploit coupling between disciplines, application of advanced active and passive materials to unique structural configurations, and other multi-disciplinary technologies.

3.0 TECHNICAL REQUIREMENTS:

1) Subtasks:

Subtask 1 – Multi-disciplinary Design: This activity aims to develop the technical basis for selected multi-disciplinary and multi-functional technologies. Studies will investigate fundamental physical interactions between disciplines (e.g.

aero/mechanical/thermal/acoustic/electromagnetic/kinematic/actuation) and develop component, sub-system, and notional system concepts that exploit beneficial aspects of the technologies. Examples could include, but are not limited to, integration of aerodynamics, structures, and controls disciplines to enable elimination of vertical tail surfaces on a supersonic aircraft; integration of antenna design, aerodynamics, and structural design for a multifunctional winglet; simultaneous design of multiple vehicle subsystems to exploit coupling during conceptual and preliminary design stages; applying topological optimization methods for multi-functional structures; integration of aerodynamics, structures, and controls disciplines for application of topological optimization methods for multi-functional structures; integration of innovative sensors and actuators to enable fly-by-feel for improved gust rejection and load quality; exploration of unique reconfiguration concepts based on origami design methods for embedded antennas and acoustic signal rejection; developing sensitivity analysis methods to expand gradient-based optimization in aircraft design;

combine operations analysis with physics based models to achieve effectiveness based design; and other design-based research activities for unique aircraft concepts.

Research and development of parametric associative models for conceptual and preliminary design phases, capable of advancing multi-scale, multi-fidelity, multidisciplinary analysis and optimization with uncertainty quantification of disciplines listed above. The results shall increase the number of multi-fidelity, multi-domain models from single source.

Results shall include reduction of real time for generation of initial models and in situ parametric and topological changes to model.

Develop and assess multidisciplinary design distributed, service-oriented computing frameworks with an open flexible design environment, allowing for universal availability and incorporation of existing data, tools/methods. Results shall enable modeling for design processes, performance of analysis and identification of sensitivities for design processes, processes for design space exploration, processes for verification, validation and accreditation of design, and hardware for services. Results include increasing applicable types of computing resources to include laptops/desktops, computing clusters, and high performance computing and shall result in an increase in number of geographically distributed engineering and business partners within collaborative environment.

Subtask 2 -- Analysis: This activity will explore the development of models and analysis tools not typically considered in component and system design. Analyses are also to be conducted in accordance with the other sub-tasks, as needed. Examples of disciplines could include, but not be limited to, predictive non-linear, anisotropic models of active materials, aeroacoustics, aerodynamics, controls, structures, aeroelasticity, kinematics and multi-body dynamics, electromagnetics, cost, and mass properties in line with conceptualization or realization activities to predict behavior of designs with advanced technologies.Examples of analyses at different scales and fidelity levels include, but are not limited to, multi-disciplinary sensitivity analysis, surrogate modeling, multi-fidelity analysis and multi-scale analysis.

Subtask 3 -- Testing: This activity seeks to develop and execute cost-effective ground and flight test activities for the multi-disciplinary technologies selected and/or for validation of multi-disciplinary design and analysis methods. Development of fabrication and test plans, data collection, and correlation with computational predictions is anticipated. Examples could include, but not be limited to, wind tunnel testing of innovative control effectors for supersonic tailless vehicles; structural, wind tunnel, and electromagnetic testing of a multifunctional winglet; wind tunnel model fabrication and testing with structurally integrated sensors and associated electronics; wind tunnel and flight testing of innovative structurally integrated sensors for fly-by-feel; structural and wind tunnel testing of 3-D printed aeroelastic models;

flight testing of advanced aeroelastic designs incorporating passive damping materials;

structural, acoustic, and/or RF testing of innovative reconfigurable structures; and benchtop feasibility demonstrations of reconfigurable surfaces and structures incorporating active materials; and support of flight testing to demonstrate improvements in aircraft cost and/or performance.

4.0 DELIVERABLES: The Contractor shall generate and provide data in accordance with the following Contract Data Requirements List (CDRL), DD Form 1423-1:

A001 – Scientific and Technical Reports - Final Report

A002 – Funds and Man-Hour Expenditures Report

A003 – Scientific and Technical Reports - Spend Plan

A004 – Contract Funds Status Report (CFSR)

A008 – Status Report

The contractor shall propose additional deliverables for the TO as appropriate. In addition, software and hardware (including source code, firmware, libraries, and executables) developed under this TO should be delivered with unlimited rights. All software developed under this task order shall be delivered in a format acceptable to both parties. The contractor shall identify any restrictions on the type of rights to be provided with software and hardware delivered but not developed under this TO, with full disclosure of any dependencies upon third party software/hardware.

5.0 BASE SUPPORT: It is anticipated that work will primarily be performed at AFRL (Wright-

Patterson AFB), and office space and access to government computer facilities will be provided.

6.0 FOREIGN PARTICIPATION: Foreign participation is not permitted on this task order.

7.0 PERIOD OF PERFORMANCE: The period of performance for this entire task order is anticipated to be 60 months—57 months for the technical performance and 3 months for the

Final Report.

8.0 SECURITY:

8.1 Operations Security. Operations Security (OPSEC) must be an integral part of our daily activities. As we maintain security on our future technologies that are vital to national interest, we must recognize and prepare for the threat poised against our technology.

Department of Defense policies mandate a high degree of security throughout the acquisition process. However, heightened security awareness and threat-based countermeasures are particularly essential during the research and development phase when our technology is most vulnerable to espionage, sabotage, or exploitation. It is the obligation of each employee or persons involved on this contract be constantly aware of and strictly adhere to security requirements designed to protect sensitive unclassified and other information and resources produced by acquisition, research and development, and technological security efforts outlined in this SOO. The contractor shall ensure employees receive training and follow appropriate Operations Security (OPSEC) measures during the performance of the contract.

8.2 Access to classified. All requested personnel for this effort will require at least a Secret clearance (Tier 3).

8.3 Sub-contracting. If the prime contractor sub-contracts work out; the prime contractor must submit a DD Form 254 for all assigned subcontractors within 30 calendar days of establishment of the contract or agreement to the Industrial Security Manager listed on the

DD 254. Once an effort is over the contractor and subcontractors must account for all classified hardware and material given, used or generated during this effort. The contractor will submit an encrypted non-classified list of all materials and/or hardware in their position to the Government Contracting Officer. In the list of items the contractor should outline what items they wish to keep and the justification. The Government Contracting

Officer and the Industrial Security Manager will determine if the material will be destroyed or returned back to the government. However, if there is a follow on effort a final DD form

254 must be issued to the contractor authorizing the contractor to retain the classified material, access, hardware for a specified time period.

8.4 Protecting information. The contractor shall not divulge any information regarding files, data, process activities/functions, user IDs, passwords, or other knowledge that may be gained, to anyone who is not authorized to have access to such information. Contractor personnel shall abide by all Government rules, procedures, and standard of conduct.

Contractors will require access to Government Automated Information Systems (AIS) and shall have background investigations and security awareness training completed prior to the start of contract performance. When the period of performance is complete and/or contractor personnel leave work on this project, they will have three (3) days to terminate all their network user accounts and to return all access cards and base identification badges.

Contractors shall encrypt all emails containing technical data or other critical information for this program. The use of products such as Encryption Wizard and Amrdec Safe are highly encouraged for safe guarding information when transmitting information via email.

Contractors shall comply with DoD 5400.7‑R/Air Force Manual 33‑302, DoD Freedom of

Information Act (FOIA) Program, requirements. Unclassified information not approved for public release on non-DoD Information Systems shall be protected IAW DoDI 8582.01, Security of Unclassified DoD Information on non-DoD Information Systems, Enclosure 3, and the Program’s Security Classification Guide