ATTEST: A Tool-kit for Rotorcraft Regime Recognition Codes Validation
Navy SBIR FY2015.2


Sol No.: Navy SBIR FY2015.2
Topic No.: N152-094
Topic Title: ATTEST: A Tool-kit for Rotorcraft Regime Recognition Codes Validation
Proposal No.: N152-094-0680
Firm: Intelligent Automation, Inc.
15400 Calhoun Drive
Suite 190
Rockville, Maryland 20855
Contact: Peter Chen
Phone: (301) 795-4463
Web Site: http://www.i-a-i.com
Abstract: IAI and its collaborators (the team) propose to develop ATTEST, a tool-kit for automatic validation of rotorcraft regime recognition codes. The tool-kit will leverage existing rotorcraft simulation platforms, which provide state-of-the-art methodologies and have been validated for a range flight conditions and rotor configurations. The codes will be used to simulate the rotorcraft and provide “truth data” that can be compared to the predictions from RR codes. Combined with the team’s expertise in design of experiments, applied to both testing as well as aircraft design; the proposed approach seeks to fill in the Navy’s need for a stand-alone tool to validate proprietary rotorcraft regime recognition codes. The team will also leverage on its access to actual flight card data and sophisticated RR codes to improve the fidelity of the proposed tool, simultaneously minimizing the risk involved in validating the tool.
Benefits: The proposed tool has a low developmental risk due to the use of sophisticated rotorcraft simulation platforms and RR codes. Furthermore, the simulation platforms take advantage of latest advances in parallel and high-performance computing, thereby reducing computation costs. The modular nature of the proposed tool makes its very flexible in design in order when interfacing with existing HUMS software. Since the proposed tool is physics-based, it is devoid of any inherent biases present in typical pattern recognition algorithms, thus reducing “noise” in its output. Lastly, the stand-alone nature of the tool makes it extremely agile and can be easily integrated with other RR codes, and thereby establish performance criteria to develop more robust RR codes in the future.

Return