Process Development for Integrated and Distributed Rotorcraft Design

The German Aerospace Center is currently developing a new design environment for rotorcraft, which combines sizing, simulation and evaluation tasks into one toolbox. The complete environment applies distributed computation on the servers of the various institutes involved. A uniform data model with a collaboration and interface software, developed by DLR and open source, are used for exchange and networking. The tools used apply blade element methods in connection with full six degrees of freedom trim, panel methods for aerodynamic loads, different empirical models for sizing, engine properties and component mass estimation and finite element methods for structural design. A special feature is the integration of a higher fidelity overall simulation tool directly into the sizing loop. The paper describes the use of the several tools for the phases of conceptual and preliminary design. A design study is presented demonstrating the sensitivity of the process for a variation of the input parameters exhibiting a broad range for trade-off studies. The possibility to continue for analyzing and sizing of the structural properties is also demonstrated by applying a finite element approach for specific load cases. These features highlight the core of the new design environment and enable the development of goal-oriented design processes for research especially of new and unconventional rotorcraft configurations. The work presented in this paper was conducted throughout the DLR internal project, namely the Technologies for Rotorcraft in Integrated and Advanced Design (TRIAD). TRIAD is a joint project of the institutes of Flight Systems, the institute of Aerodynamics and Flow Technology, the institute of Structures and Design, the System Architectures in Aeronautics and Institute of Aerospace Medicine and receives basic founding.

Abstract licence: CC BY

27 more references, whose wording the paper’s licence keeps private.

A person counts once a day per paper. We keep no cookie and no address: a reader is a hash that changes every day. Any month under five reads shows no number.