Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Agile Development”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 91 records · Page 5

An investigation of fighter aircraft agility

This report attempts to unify in a single document the results of a series of studies on fighter aircraft agility funded by the NASA Ames Research Center, Dryden Flight Research Facility and conducted at the University of Kansas Flight Research Laboratory during the period January 1989 through December 1993. New metrics proposed by pilots and the research community to assess fighter aircraft agility are collected and analyzed. The report develops a framework for understanding the context into which the various proposed fighter agility metrics fit in terms of application and testing. Since new metrics continue to be proposed, this report does not claim to contain every proposed fighter agility metric. Flight test procedures, test constraints, and related criteria are developed. Instrumentation required to quantify agility via flight test is considered, as is the sensitivity of the candidate metrics to deviations from nominal pilot command inputs, which is studied in detail. Instead of supplying specific, detailed conclusions about the relevance or utility of one candidate metric versus another, the authors have attempted to provide sufficient data and analyses for readers to formulate their own conclusions. Readers are therefore ultimately responsible for judging exactly which metrics are 'best' for their particular needs. Additionally, it is not the intent of the authors to suggest combat tactics or other actual operational uses of the results and data in this report. This has been left up to the user community. Twenty of the candidate agility metrics were selected for evaluation with high fidelity, nonlinear, non real-time flight simulation computer programs of the F-5A Freedom Fighter, F-16A Fighting Falcon, F-18A Hornet, and X-29A. The information and data presented on the 20 candidate metrics which were evaluated will assist interested readers in conducting their own extensive investigations. The report provides a definition and analysis of each metric; details of how to test and measure the metric, including any special data reduction requirements; typical values for the metric obtained using one or more aircraft types; and a sensitivity analysis if applicable. The report is organized as follows. The first chapter in the report presents a historical review of air combat trends which demonstrate the need for agility metrics in assessing the combat performance of fighter aircraft in a modern, all-aspect missile environment. The second chapter presents a framework for classifying each candidate metric according to time scale (transient, functional, instantaneous), further subdivided by axis (pitch, lateral, axial). The report is then broadly divided into two parts, with the transient agility metrics (pitch lateral, axial) covered in chapters three, four, and five, and the functional agility metrics covered in chapter six. Conclusions, recommendations, and an extensive reference list and biography are also included. Five appendices contain a comprehensive list of the definitions of all the candidate metrics; a description of the aircraft models and flight simulation programs used for testing the metrics; several relations and concepts which are fundamental to the study of lateral agility; an in-depth analysis of the axial agility metrics; and a derivation of the relations for the instantaneous agility and their approximations.

Valasek, John↗

Precision slew/settle technologies for flexible spacecraft

Many spacecraft missions in the next decade will require both a high degree of agility and precision pointing. Agility includes both rotational maneuvering for retargeting and translational motion for orbit adjustment and threat avoidance. The major challenge associated with such missions is the need for control over a wide range of amplitudes and frequencies, ranging from tens of degrees at less than 1 Hz to a few micron radians at hundreds of Hz. TRW's internally funded Precision Control of Agile Spacecraft (PCAS) project is concerned with developing and validating in hardware the tools necessary to successfully complete the combined agile maneuvering/precision pointing missions. Development has been undertaken on a number of fronts for quietly slewing flexible structures. Various methods for designing slew torque profiles have been investigated. Prime candidates for slew/settle scenarios include Inverse Dynamics and Parameterized Function Space. Joint work with Processor Bayo at the University of California, Santa Barbara and Professor Flashner at the University of Southern California has led to promising torque profile design methods. Active and passive vibration suppression techniques also play a key role for rapid slew/settle mission scenarios. Active members with local control loops and passive members with high loss factor viscoelastic material have been selected for hardware verification. Progress in each of these areas produces large gains in the quiet slewing of flexible spacecraft. The main thrust of the effort to date has been the development of a modular testbed for hardware validation of the precision control concepts. The testbed is a slewing eighteen foot long flexible truss. Active and passive members can be interchanged with the baseline aluminum members to augment the inherent damping in the system. For precision control the active members utilize control laws running on a high speed digital structural control processor. Tip and midspan motions of the truss are determined using optical sensors while accelerometers can be used to monitor the motions of other points of interest. Preliminary results indicate that a mix of technologies produces the greatest benefit. For example, shaping the torque profile produces large improvements in slew/settle performance, but without added damping settling times may still be excessive. With the introduction of moderate amounts of damping, slew/settle performance is vastly improved. On the other hand, introducing damping without shaping the torque profile may not yield the desired level of performance.

Manning, R. A.↗

Introduction of an Agile Systems Engineering Process to the NASA Armstrong Flight Research Center

This paper will provide background on the National Aeronautics and Space Administration (NASA) Aeronautics Research Mission Directorate (ARMD) ARMD Test Data Portal (ATDP) effort along with the rationale that motivated the ATDP team to consider implementing an agile systems engineering (SE) process. The primary motivation for using this new SE process was based on the desire to mitigate a major risk to project success. Since the agile SE process had never been used before at the NASA Armstrong Flight Research Center (AFRC), utilizing this new SE process required a trailblazing effort to introduce it to NASA AFRC leadership. As a result, the ATDP team chose to adhere to the agile SE process in addition to the trusted classical waterfall SE process on ATDP. Through successful execution of this hybrid SE process during Phase I, along with demonstrating the value and rigor of the agile SE process, NASA AFRC leadership ultimately permitted the ATDP project to solely use the agile SE process for developments beyond Phase I. While it is the opinion of the authors that the classical SE process is more effective for most projects at NASA AFRC, some projects may deem that the agile SE process is more advantageous. Although this paper is focused on introducing the agile SE process to NASA AFRC, lessons learned will be valuable to other organizations as well. Details of how the ATDP team implemented the agile SE process during Phase I will be summarized, along with how the team met all required classical SE milestones. Lessons learned throughout Phase I of this effort will also be highlighted.

Daniel S. Jones↗

Agile manufacturing: The factory of the future

The factory of the future will require an operating methodology which effectively utilizes all of the elements of product design, manufacturing and delivery. The process must respond rapidly to changes in product demand, product mix, design changes or changes in the raw materials. To achieve agility in a manufacturing operation, the design and development of the manufacturing processes must focus on customer satisfaction. Achieving greatest results requires that the manufacturing process be considered from product concept through sales. This provides the best opportunity to build a quality product for the customer at a reasonable rate. The primary elements of a manufacturing system include people, equipment, materials, methods and the environment. The most significant and most agile element in any process is the human resource. Only with a highly trained, knowledgeable work force can the proper methods be applied to efficiently process materials with machinery which is predictable, reliable and flexible. This paper discusses the affect of each element on the development of agile manufacturing systems.

Loibl, Joseph M.↗

Automation of Flight Software Regression Testing

NASA is developing the Space Launch System (SLS) to be a heavy lift launch vehicle supporting human and scientific exploration beyond earth orbit. SLS will have a common core stage, an upper stage, and different permutations of boosters and fairings to perform various crewed or cargo missions. Marshall Space Flight Center (MSFC) is writing the Flight Software (FSW) that will operate the SLS launch vehicle. The FSW is developed in an incremental manner based on "Agile" software techniques. As the FSW is incrementally developed, testing the functionality of the code needs to be performed continually to ensure that the integrity of the software is maintained. Manually testing the functionality on an ever-growing set of requirements and features is not an efficient solution and therefore needs to be done automatically to ensure testing is comprehensive. To support test automation, a framework for a regression test harness has been developed and used on SLS FSW. The test harness provides a modular design approach that can compile or read in the required information specified by the developer of the test. The modularity provides independence between groups of tests and the ability to add and remove tests without disturbing others. This provides the SLS FSW team a time saving feature that is essential to meeting SLS Program technical and programmatic requirements. During development of SLS FSW, this technique has proved to be a useful tool to ensure all requirements have been tested, and that desired functionality is maintained, as changes occur. It also provides a mechanism for developers to check functionality of the code that they have developed. With this system, automation of regression testing is accomplished through a scheduling tool and/or commit hooks. Key advantages of this test harness capability includes execution support for multiple independent test cases, the ability for developers to specify precisely what they are testing and how, the ability to add automation, and the ability of the harness and cases to be executed continually. This test concept is an approach that can be adapted to support other projects.

Tashakkor, Scott B.↗

An Expanded Role for Python in Expediting System Simulation Development

The Python programming language has traditionally been used as a “scripting” language and is not generally recognized as a language for building system simulations, where C++, Java, and other compiled languages are typically used. While very powerful and gaining favor for a large set of programming tasks, Python is generally regarded as not having the speed to directly do the extensive numeric computations required in large-scale simulation. This paper aims to present an approach, supported by case studies, to re-think this assertion. Directly using Python in this new role has the potential to expedite an agile, spiral cycle of development of design-test-modify for systems simulation.

programming language↗

In-Space Manufacturing: Pioneering a Sustainable Path to Mars

In order to provide meaningful impacts to exploration technology needs, the In-Space Manufacturing (ISM) Initiative must influence exploration systems design now. In-space manufacturing offers: dramatic paradigm shift in the development and creation of space architectures; efficiency gain and risk reduction for low Earth orbit and deep space exploration; and "pioneering" approach to maintenance, repair, and logistics leading to sustainable, affordable supply chain model. In order to develop application-based capabilities in time to support NASA budget and schedule, ISM must be able to leverage the significant commercial developments, which requires innovative, agile collaborative mechanisms (contracts, challenges, SBIR's, etc.); and NASA-unique investments to focus primarily on adapting the technologies and processes to the microgravity environment. We must do the foundational work - it is the critical path for taking these technologies from lab curiosities to institutionalized capabilities: characterize, certify, institutionalize, design for Additive Manufacturing (AM). Ideally, International Space Station (ISS) U.S. lab rack or partial rack space should be identified for in-space manufacturing utilization in order to continue technology development of a suite of capabilities required for exploration missions, as well as commercialization on ISS.

Werkheiser, Niki↗

Situation assessment in the Paladin tactical decision generation system

Paladin is a real-time tactical decision generator for air combat engagements. Paladin uses specialized knowledge-based systems and other Artificial Intelligence (AI) programming techniques to address the modern air combat environment and agile aircraft in a clear and concise manner. Paladin is designed to provide insight into both the tactical benefits and the costs of enhanced agility. The system was developed using the Lisp programming language on a specialized AI workstation. Paladin utilizes a set of air combat rules, an active throttle controller, and a situation assessment module that have been implemented as a set of highly specialized knowledge-based systems. The situation assessment module was developed to determine the tactical mode of operation (aggressive, defensive, neutral, evasive, or disengagement) used by Paladin at each decision point in the air combat engagement. Paladin uses the situation assessment module; the situationally dependent modes of operation to more accurately represent the complex decision-making process of human pilots. This allows Paladin to adapt its tactics to the current situation and improves system performance. Discussed here are the details of Paladin's situation assessment and modes of operation. The results of simulation testing showing the error introduced into the situation assessment module due to estimation errors in positional and geometric data for the opponent aircraft are presented. Implementation issues for real-time performance are discussed and several solutions are presented, including Paladin's use of an inference engine designed for real-time execution.

Mcmanus, John W.↗

Comparative study of x ray and microwave emissions during solar flares

The work supported by the grant consisted of two projects. The first project involved making detailed case studies of two flares using SMM data in conjunction with ground based observations. The first flare occurred at 1454 UT on June 20, 1989 and involved the eruption of a prominence near the limb. In the study we used data from many wavelength regimes including the radio, H-alpha, hard X-rays, and soft X-rays. We used a full gyrosynchrotron code to model the apparent presence of a 1.4 GHz source early in the flare that was in the form of a large coronal loop. The model results lead us to conclude that the initial acceleration occurs in small, dense loops which also produced the flare's hard X-ray emission. We also found evidence that a source at 1.4 GHz later in the event was due to second harmonic plasma emission. This source was adjacent to a leg of the prominence and comes from a dense column of material in the magnetic structure supporting the prominence. Finally, we investigated a source of microwaves and soft X-rays, occurring approximately 10 min after the hard X-ray peak, and calculate a lower limit for the density of the source. The second flare that was studied occurred at 2156 UT on June 20, 1989 and was observed with the VLA and the Owens Valley Radio Observatory (OVRO) Frequency Agile Array. We have developed a gyrosynchrotron model of the sources at flare peak using a new gyrosynchrotron approximation which is valid at very low harmonics of the gyrofrequency. We found that the accelerated particle densities of the sources decreased much more with radius from the source center than had been supposed in previous work, while the magnetic field varied less. We also used the available data to analyze a highly polarized source which appeared late in the flare. The second project involved compiling a statistical base for the relative timing of the hard X-ray peak, the turbulent and blue-shift velocities inferred from soft X-ray line emissions observed by SMM and the microwave peak as determined from ground-based observations. This timing was then used to aid the testing of newly developed global models for flares that incorporate the global magnetic topology as well as the electron dynamics that are responsible for the hard X-rays and microwaves.

Winglee, Robert M.↗

A scientific assessment of a new technology orbital telescope

As part of a program designed to test the Alpha chemical laser weapons system in space, the Ballistic Missile Defense Organization (BMDO) developed components of an agile, lightweight, 4-meter telescope, equipped with an advanced active-optics system. BMDO had proposed to make space available in the telescope's focal plane for instrumentation optimized for scientific applications in astrophysics and planetary astronomy for a potential flight mission. Such a flight mission could be undertaken if new or additional sponsorship can be found. Despite this uncertainty, BMDO requested assistance in defining the instrumentation and other design aspects necessary to enhance the scientific value of a pointing and tracking mission. In response to this request, the Space Studies Board established the Task Group on BMDO New Technology Orbital Observatory (TGBNTOO) and charged it to: (1) provide instrumentation, data management, and science-operations advice to BMDO to optimize the scientific value of a 4-meter mission; and (2) support a space studies board assessment of the relative scientific merit of the program. This report deals with the first of these tasks, assisting the Advanced Technology Demonstrator's (ATD's) program scientific potential. Given the potential scientific aspects of the 4-meter telescope, this project is referred to as the New Technology Orbital Telescope (NTOT), or as the ATD/NTOT, to emphasize its dual-use character. The task group's basic conclusion is that the ATD/NTOT mission does have the potential for contributing in a major way to astronomical goals.

Source record↗

Utilization of an agility assessment module in analysis and optimization of preliminary fighter configuration

A study has been conducted to develop and to analyze a FORTRAN computer code for performing agility analysis on fighter aircraft configurations. This program is one of the modules of the NASA Ames ACSYNT (AirCraft SYNThesis) design code. The background of the agility research in the aircraft industry and a survey of a few agility metrics are discussed. The methodology, techniques, and models developed for the code are presented. The validity of the existing code was evaluated by comparing with existing flight test data. A FORTRAN program was developed for a specific metric, PM (Pointing Margin), as part of the agility module. Example trade studies using the agility module along with ACSYNT were conducted using a McDonnell Douglas F/A-18 Hornet aircraft model. Tile sensitivity of thrust loading, wing loading, and thrust vectoring on agility criteria were investigated. The module can compare the agility potential between different configurations and has capability to optimize agility performance in the preliminary design process. This research provides a new and useful design tool for analyzing fighter performance during air combat engagements in the preliminary design.

Ngan, Angelen↗

The Ejectable Data Recorder: A Lean, Risk-Informed Approach for Hardware Development

NASA is developing the Orion spacecraft to transport crew from the Earth to the Moon as part of the Artemis series of missions. To provide a crew escape capability from pre-launch through ascent, the Orion vehicle is equipped with a Launch Abort System (LAS), built by Lockheed Martin, which pulls the capsule away from the launch vehicle in the event of an abort scenario. The Ascent Abort 2 (AA-2) test flight occurred on July 2, 2019,and tested a production version of the LAS to ensure that it can operate as intended, and to collect a large data set from hundreds of sensors on the vehicle to support Orion flight certification. In the original AA-2 architecture, a single-string set of communications antennas on the LAS would downlink all of the in-flight test data to ground stations. However, that communications architecture was predicted to have data dropouts during abort and jettison of the LAS, and would not support data transmission at all after LAS jettison. As a result, a comprehensive trade study was completed, yielding the addition of antennas on the crew module (CM), a buffer/rebroadcast capability for key portions of the flight, and an ejectable data recorder (EDR) subsystem. This EDR subsystem would serve as a backup to the radio frequency (RF) communications system, and would be non-flight critical, providing a unique capability that enabled management to take a different approach with the hardware and software development. The Crew Module and Separation Ring were developed as “Class 1”Flight Hardware, albeit with some tailoring approaches to enable efficiencies. The Class 1 designation requires full rigor for flight hardware and software, documenting everything that happens to a piece of hardware from procurement through disposal, requiring a full spectrum of acceptance tests, and the highest rigor of quality assurance processes. At the other end of the spectrum, Class 3hardware is controlled, but not intended for flight, and leaves the level of rigor up to the project manager. This classification is often used for research and development projects. Similarly,Class-1E has been recently defined at NASA for ISS payloads and technology development projects that are not flight critical and do not need the full rigor of Class 1 to be successful. The EDR subsystem was challenged at commencement to adopt a skunkworks and agile-like approach to hardware development, allowing for a different risk posture than the rest of the AA-2 hardware. After initially pursuing Class 1 processes, the EDR subsystem design evolved to incorporating numerous commercial components, leading to re-designation as a Class-1E subsystem. The resulting EDR subsystem was fully successful in meeting all flight system requirements, and achieved 100% retrieval of flight test data. This paper will discuss the risk posture of the EDR subsystem and the subsequent tailoring that was enacted as part of its Class-1E status.

EDR↗

Principles from Two Small SRM-Based Launcher Design/Developments

Two solid rocket motor based launch vehicles are in design and development at MSFC, a 4-stage Earth-to-Orbit vehicle cube-satellite launcher, and the 2-stage Mars Ascent Vehicle for the Mars sample return mission. Trade studies that refined these designs have benefited from developments in understanding sensitivities and approximate modeling. The development and practice of that has demonstrated 3 principles: PRINCIPLE I: Identify mission-specific key design drivers — particularly interactions (and focus knowledge-development on those). PRINCIPLE II: Agility — don’t lock down your derived requirements early — keep trading, and characterizing sensitivities. PRINCIPLE III: Use multi-fidelity tools to improve “understanding value generated per modeling effort cost.” The designer should expect different design solution techniques to derive from different mission needs. This paper shows how two launch vehicle designs developed and adapted to those needs.

Kibbey, Timothy P.↗

Control structural interaction testbed: A model for multiple flexible body verification

Conventional end-to-end ground tests for verification of control system performance become increasingly complicated with the development of large, multiple flexible body spacecraft structures. The expense of accurately reproducing the on-orbit dynamic environment and the attendant difficulties in reducing and accounting for ground test effects limits the value of these tests. TRW has developed a building block approach whereby a combination of analysis, simulation, and test has replaced end-to-end performance verification by ground test. Tests are performed at the component, subsystem, and system level on engineering testbeds. These tests are aimed at authenticating models to be used in end-to-end performance verification simulations: component and subassembly engineering tests and analyses establish models and critical parameters, unit level engineering and acceptance tests refine models, and subsystem level tests confirm the models' overall behavior. The Precision Control of Agile Spacecraft (PCAS) project has developed a control structural interaction testbed with a multibody flexible structure to investigate new methods of precision control. This testbed is a model for TRW's approach to verifying control system performance. This approach has several advantages: (1) no allocation for test measurement errors is required, increasing flight hardware design allocations; (2) the approach permits greater latitude in investigating off-nominal conditions and parametric sensitivities; and (3) the simulation approach is cost effective, because the investment is in understanding the root behavior of the flight hardware and not in the ground test equipment and environment.

Chory, M. A.↗

Study of aerodynamic technology for VSTOL fighter attack aircraft

Vertical short takeoff aircraft capability, supersonic dash capability, and transonic agility were investigated for the development of Fighter/attack aircraft to be accommodated on ships smaller than present aircraft carriers. Topics covered include: (1) description of viable V/STOL fighter/attack configuration (a high wing, close-coupled canard, twin-engine, control configured aircraft) which meets or exceeds specified levels of vehicle performance; (2) estimates of vehicle aerodynamic characteristics and the methodology utilized to generate them; (3) description of propulsion system characteristics and vehicle mass properties; (4) identification of areas of aerodynamic uncertainty; and (5) a test program to investigate the areas of aerodynamic uncertainty in the conventional flight mode.

Burhans, W., Jr.↗

Investigation into the impact of agility on conceptual fighter design

The Agility Design Study was performed by the Boeing Defense and Space Group for the NASA Langley Research Center. The objective of the study was to assess the impact of agility requirements on new fighter configurations. Global trade issues investigated were the level of agility, the mission role of the aircraft (air-to-ground, multi-role, or air-to-air), and whether the customer is Air force, Navy, or joint service. Mission profiles and design objectives were supplied by NASA. An extensive technology assessment was conducted to establish the available technologies to industry for the aircraft. Conceptual level methodology is presented to assess the five NASA-supplied agility metrics. Twelve configurations were developed to address the global trade issues. Three-view drawings, inboard profiles, and performance estimates were made and are included in the report. A critical assessment and lessons learned from the study are also presented.

Engelbeck, R. M.↗

Non-Maximally Decimated Filter Banks Enable Adaptive Frequency Hopping for Unmanned Aircraft Vehicles

In the last few years, radio technologies for unmanned aircraft vehicle (UAV) have advanced very rapidly. The increasing need to fly unmanned aircraft systems (UAS) in the national airspace system (NAS) to perform missions of vital importance to national security, defense, and science has pushed ahead the design and implementation of new radio platforms. However, a lot still has to be done to improve those radios in terms of performance and capabilities. In addition, an important aspect to account for is hardware cost and the feasibility to implement these radios using commercial off-the-shelf (COTS) components. UAV radios come with numerous technical challenges and their development involves contributions at different levels of the design. Cognitive algorithms need to be developed in order to perform agile communications using appropriate frequency allocation while maintaining safe and efficient operations in the NAS and, digital reconfigurable architectures have to be designed in order to ensure a prompt response to environmental changes. Command and control (C2) communications have to be preserved during "standard" operations while crew operations have to be minimized. It is clear that UAV radios have to be software-defined systems, where size, weight and power consumption (SWaP) are critical parameters. This paper provides preliminary results of the efforts performed to design a fully digital radio architecture as part of a NASA Phase I STTR. In this paper, we will explain the basic idea and technical principles behind our dynamic/adaptive frequency hopping radio for UAVs. We will present our Simulink model of the dynamic FH radio transmitter design for UAV communications and show simulation results and FPGA system analysis.

UAV↗

Major Design Choices and Challenges that Enabled the Success of the Ejectable Data Recorder System

The Ejectable Data Recorder (EDR) subsystem was added to the Crew Module (CM) of the Ascent Abort 2 (AA-2) test flight due to a risk that the communications architecture would be insufficient to downlink all the data to the ground during the test flight. Since the EDR subsystem was a secondary system for data collection, AA-2 management enabled the team to take a different approach to hardware development that was more agile-like. This paper discusses key design decisions, technical challenges, and lessons learned that enabled the success of the EDR system during its flight on July 2, 2019.

Jeff Hagen↗