Search NASA⌕ Search

SEARCH · Search NASA

Results for “design and process 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 505 records · Page 28
All sourcesNASA NTRSDOE OSTI
NASA NTRS1988

Space station functional relationships analysis

A systems engineering process is developed to assist Space Station designers to understand the underlying operational system of the facility so that it can be physically arranged and configured to support crew productivity. The study analyzes the operational system proposed for the Space Station in terms of mission functions, crew activities, and functional relationships in order to develop a quantitative model for evaluation of interior layouts, configuration, and traffic analysis for any Station configuration. Development of the model involved identification of crew functions, required support equipment, criteria of assessing functional relationships, and tools for analyzing functional relationship matrices, as well as analyses of crew transition frequency, sequential dependencies, support equipment requirements, potential for noise interference, need for privacy, and overall compatability of functions. The model can be used for analyzing crew functions for the Initial Operating Capability of the Station and for detecting relationships among these functions. Note: This process (FRA) was used during Phase B design studies to test optional layouts of the Space Station habitat module. The process is now being automated as a computer model for use in layout testing of the Space Station laboratory modules during Phase C.

Tullis, Thomas S.↗
NASA NTRS2016

Evaluation of Novel Liner Concepts for Fan and Airframe Noise Reduction

This paper presents a review of four novel liner concepts: soft vanes, over-the-rotor liners, external liners, and flap side-edge liners. A number of similarities in the design and evaluation of these concepts emerged during these investigations. Since these were the first attempts to study these particular liner concepts, there was limited information to guide the design process. In all cases, the target frequencies (or frequency range) were known, but the optimum acoustic impedance and optimum liner placement were typically not known. For these cases, the maximum available surface was used and a c-impedance was targeted based on the assumption the sound field impinges on the surface at normal incidence. This choice proved fruitful for every application. An impedance prediction model was used to design variable-depth liner configurations, and a graphical design code (ILIAD) was developed to aid in this process. The ability to build increasingly complex liner configurations via additive manufacturing was key, such that multiple designs could quickly be tested in a normal incidence impedance tube. The Two-Thickness Method was used to evaluate available bulk materials, such that bulk liners could also be considered for each application. These novel liner concepts provide sufficient noise reduction to warrant further investigations.

Jones, M. G.↗
NASA NTRS2022

22” ADP Fan Rig Liners Design Report

A liner design study was conducted as part of a cooperative effort between five (5) government/industry teams that together seek to demonstrate the technology for designing and manufacturing acoustic liners that are twenty five percent (25%) more efficient than 1992 technology liners. The study emphasized teaming collaboration. The improved liners were designed by Pratt & Whitney and Boeing Airplane Company and built by Rohr Inc, and will be tested in the NASA/P& W 22-inch ADP fan rig at NASA Lewis Research Center's 9' x 15' wind tunnel. Design guidelines and decisions were made collectively during monthly design review telecons and at the formal final design review. The tools that were used to design the new improved liners were not new, but the process that was developed as part of this study that led into the evaluation and selection of the final and best liner designs is new. Until now, the liner design process as practiced by different industry teams varied greatly. Some procedures were based on empirical liner attenuation databases which could not adequately account for engine-to-engine hardwall fan noise spectral differences, while others were entirely theoretical. And regardless of which method one chose, the major difficulty was still the lack of understanding and knowledge of the actual hardwall fan source noise modal structure and farfield SPL spectra. The NASA-led effort to attempt actual measurements of the fan source noise modal structure by means of the rotating microphone array is expected to contribute significantly to the understanding of the nature of the fan tone noise modes, but the application to broadband noise is still a long way off. The new design process included consideration of the measured fan tone modes, but for the majority of the spectra a separate, systematic process was used. It is a common practice in the engine/nacelle industry that acoustic liners for new products are designed before actual measured hardwall engine far-field noise spectra are available. Target noise spectra are normally derived from existing engine noise databases with some adjustments to absolute SPLs and frequencies. This practice has been acceptable as long as the new engine was a derivative of the base engine. However, in the case of the ADP, the transition from a current engine base is too - great, and the adjustments could not adequately account for the quantum changes in SPL spectral differences. Examples were the 1992 single degree of freedom (SDOF) inlet and aft liners (designed by P&W) that would be used as the baseline liners against which the new improved liners' efficien¬cies would -be measured. As will be shown, these baseline liners have been found to be deeper than the desire optimum depths. The new liner design process begins with the selection of the target hard wall fan noise spectra. These spectra were obtained by scaling up (5.91 scale factor) the measured hardwall fan spectral data from the 22” ADP fan rig. Next, the modal energy contents for each 1/3-octave band center frequency of these hardwall fan noise spectra are estimated. (Within each 1/3-octave band center frequency, the model energy distribution approximation is for both tone and broadband noise). For the inlet noise, P&W uses a derivative of the NASA Lewis (Ed Rice's) method of classifying; and grouping propagating modes by their cutoff ratios. The next step is to assign energy level to each group of modes having the same cutoff ratio. In Ed Rice's model, the modes were grouped according to ten (10) cutoff ratio intervals with center values located at 1.026, 1.085, 1.155, 1.24, 1.35, 1.49, 1.69, 2.0, and 4.47 (with equal number of modes in each interval). The modes were assumed to have equal energy. P&W’s model expands the cutoff ratio-mode grouping into two hundred (200) smaller cutoff ratio intervals with center values located f1".'m 1.003 to 11.5 in 199 increasing incremental intervals. Next, P&W's model uses a "2-parameter" normal distribution as a template to assign energy levels to these 200 pre-determined cutoff ratio values (for each 1/3-octave band center frequency). In the past, P&W had conducted an extensive study to determine what "2-parameter" values are appropriate for fullscale inlet liners, and had developed a set of twenty-four (24) "2-pararneter" values (i.e. one for each 1/3-octave frequency band) that when used in Ed Rice's Inlet Attenuation Prediction Method produced predicted liner attenuations that closely matched measured liner attenuations from several P&W's engines. In the absence of actual measured tone and broadband modal data from the 22" ADP rig, the process will use P&W's proprietary set of "2-parameter" values for this liner design study. For the aft noise, Boeing uses a modal energy approximation that the "transport energy" of each propagating mode is equal. This approximation is almost the same as the equal energy per mode approximation, except for modes that are near cutoff. Boeing's model forces these modes to have lower energy levels. Both P&W and Boeing agreed that the "transport energy" approximation should work well for the ADP aft fan noise which appears to be dominated by broadband noise. The design process then proceeds to calculate the optimum liner impedances for each frequency in both the inlet and the aft. These optimum impedances represent the target impedances that the designed liners should have. Liners with impedances matching the optimum impedances at all frequencies are "ideal" liners. These ideal liners are theoretically the best liners. Unfortunately, it has been showed that it is impossible to design and build such ideal liners. The next best liners are ones that have impedances matching the optimum impedances over some frequency range (not all frequencies as for the ideal). This is accomplished by the use of "frequency weightings". Several of P&W's and Boeing's existing computer decks were used for optimizing and matching the designed liner impedances to the target optimum values (with the various frequency weightings specified). The optimization produces liner candidates with predicted liner impedances and descriptions of their physical liner characteristics. These candidate liner impedances are then used to predict their spectral attenuation characteristics which are then used together with the target hardwall fan noise spectra to determine the resulting treated noise spectra and PNLT values. Further optimization around the selected candidate designs yield final designs that are best in PNLT attenuations. Use of the optimization decks allowed a large number of liner candidates to be screened in a relatively short period of time. This design process is systematic and is efficient. The new inlet SDOF liner design obtained from the improved process was predicted to be 34% more effective (per unit area) than the 1992 baseline inlet liner. This inlet liner design is a 112 rayl wovenwiremesh facesheet over a 0.312-inch deep honeycomb core. The new aft SDOF liner design was predicted to be 52% more efficient than the aft baseline liner. The new aft SDOF liner is "segmented" with a shallower liner on the core cowl (inner duct wall) and a deeper liner on the fan cowl (outer duct wall). The shallower liner is a 70.6 rayl woven-wiremesh facesheet over a 0.141-inch deep honeycomb core. The deeper liner is a 68 rayl woven-wiremesh facesheet over a 0.309-inch deep honeycomb core. All liner dimensions are for the 22-inch model-scale ADP fan rig liners. The selected advanced liners are "segmented" double-layer (DDOF) liners for the inlet and aft locations. Also, for the inlet, a bulk liner with ceramic foam for wider broadband noise absorption was also selected. Triple-layer liner designs were not considered since the model scaled liners ( 1/5. 91) were dimensionally too small to be built correctly, and irrin earlier concept study, Boeing found a triple-layer to have only very small benefits over a double-layer. The inlet DDOF liner was predicted to be 83% more effective than the baseline. The inlet DDOF design is a 78 rayl facesheet over a 0.080 top cavity depth, a 68 rayl septum and a 0.227-inch bottom cavity depth. The inlet bulk liner is a 60 rayl facesheet over a 0.33-inch deep honeycomb filled with high temperature (HTP) ceramic foam with a density of 4.8 lb/cu.ft and a flow resistivity of 167 rayl/cm. The inlet bulk liner was predicted to be 83% more effective than the baseline liner. The aft DDOF liners are segmented with a shallower liner on the core cowl and a deeper liner on the fan cowl. The shallow DDOF liner is a 49.8 rayl facesheet over a 0.093-inch top cavity depth, a septum of 88.2 rayls over a 0.181-inch bottom cavity depth. The deep DDOF liner is a 12.9 rayl facesheet over a 0.140-inch top cavity depth, a septum of 53.1 ray ls over a 0.258-inch botom cavity depth. The segmented aft DDOF liners were predicted to be 86% more efficient than the baseline liner.

turbofan acoustic treatment↗
NASA NTRS2009

Framework for Multidisciplinary Analysis, Design, and Optimization with High-Fidelity Analysis Tools

A plan is presented for the development of a high fidelity multidisciplinary optimization process for rotorcraft. The plan formulates individual disciplinary design problems, identifies practical high-fidelity tools and processes that can be incorporated in an automated optimization environment, and establishes statements of the multidisciplinary design problem including objectives, constraints, design variables, and cross-disciplinary dependencies. Five key disciplinary areas are selected in the development plan. These are rotor aerodynamics, rotor structures and dynamics, fuselage aerodynamics, fuselage structures, and propulsion / drive system. Flying qualities and noise are included as ancillary areas. Consistency across engineering disciplines is maintained with a central geometry engine that supports all multidisciplinary analysis. The multidisciplinary optimization process targets the preliminary design cycle where gross elements of the helicopter have been defined. These might include number of rotors and rotor configuration (tandem, coaxial, etc.). It is at this stage that sufficient configuration information is defined to perform high-fidelity analysis. At the same time there is enough design freedom to influence a design. The rotorcraft multidisciplinary optimization tool is built and substantiated throughout its development cycle in a staged approach by incorporating disciplines sequentially.

Orr, Stanley A.↗
NASA NTRS1994

Quality assurance and risk management: Perspectives on Human Factors Certification of Advanced Aviation Systems

This paper is based on the experience of engineering psychologists advising the U.K. Ministry of Defense (MoD) on the procurement of advanced aviation systems that conform to good human engineering (HE) practice. Traditional approaches to HE in systems procurement focus on the physical nature of the human-machine interface. Advanced aviation systems present increasingly complex design requirements for human functional integration, information processing, and cognitive task performance effectiveness. These developing requirements present new challenges for HE quality assurance (QA) and risk management, requiring focus on design processes as well as on design content or product. A new approach to the application of HE, recently adopted by NATO, provides more systematic ordering and control of HE processes and activities to meet the challenges of advanced aircrew systems design. This systematic approach to HE has been applied by MoD to the procurement of mission systems for the Royal Navy Merlin helicopter. In MoD procurement, certification is a judicial function, essentially independent of the service customer and industry contractor. Certification decisions are based on advice from MoD's appointed Acceptance Agency. Test and evaluation (T&E) conducted by the contractor and by the Acceptance Agency provide evidence for certification. Certification identifies limitations of systems upon release to the service. Evidence of compliance with HE standards traditionally forms the main basis of HE certification and significant non-compliance could restrict release. The systems HE approach shows concern for the quality of processes as well as for the content of the product. Human factors certification should be concerned with the quality of HE processes as well as products. Certification should require proof of process as well as proof of content and performance. QA criteria such as completeness, consistency, timeliness, and compatibility provide generic guidelines for progressive acceptance and certification of HE processes. Threats to the validity of certification arise from problems and assumptions in T&E methods. T&E should seek to reduce the risk of specification non-compliance and certification failure.

Taylor, Robert M.↗
NASA NTRS2016

Dynamic Systems Analysis for Turbine Based Aero Propulsion Systems

The aircraft engine design process seeks to optimize the overall system-level performance, weight, and cost for a given concept. Steady-state simulations and data are used to identify trade-offs that should be balanced to optimize the system in a process known as systems analysis. These systems analysis simulations and data may not adequately capture the true performance trade-offs that exist during transient operation. Dynamic systems analysis provides the capability for assessing the dynamic tradeoffs at an earlier stage of the engine design process. The dynamic systems analysis concept, developed tools, and potential benefit are presented in this paper. To provide this capability, the Tool for Turbine Engine Closed-loop Transient Analysis (TTECTrA) was developed to provide the user with an estimate of the closed-loop performance (response time) and operability (high pressure compressor surge margin) for a given engine design and set of control design requirements. TTECTrA along with engine deterioration information, can be used to develop a more generic relationship between performance and operability that can impact the engine design constraints and potentially lead to a more efficient engine.

dynamic analysis↗
NASA NTRS2013

Integrated Tools for Future Distributed Engine Control Technologies

Turbine engines are highly complex mechanical systems that are becoming increasingly dependent on control technologies to achieve system performance and safety metrics. However, the contribution of controls to these measurable system objectives is difficult to quantify due to a lack of tools capable of informing the decision makers. This shortcoming hinders technology insertion in the engine design process. NASA Glenn Research Center is developing a Hardware-inthe- Loop (HIL) platform and analysis tool set that will serve as a focal point for new control technologies, especially those related to the hardware development and integration of distributed engine control. The HIL platform is intended to enable rapid and detailed evaluation of new engine control applications, from conceptual design through hardware development, in order to quantify their impact on engine systems. This paper discusses the complex interactions of the control system, within the context of the larger engine system, and how new control technologies are changing that paradigm. The conceptual design of the new HIL platform is then described as a primary tool to address those interactions and how it will help feed the insertion of new technologies into future engine systems.

Culley, Dennis↗
NASA NTRS1988

Space Station tethered waste disposal

The Shuttle Transportation System (STS) launches more payload to the Space Station than can be returned creating an accumulation of waste. Several methods of deorbiting the waste are compared including an OMV, solid rocket motors, and a tether system. The use of tethers is shown to offer the unique potential of having a net savings in STS launch requirement. Tether technology is being developed which can satisfy the deorbit requirements but additional effort is required in waste processing, packaging, and container design. The first step in developing this capability is already underway in the Small Expendable Deployer System program. A developmental flight test of a tether initiated recovery system is seen as the second step in the evolution of this capability.

Rupp, Charles C.↗
NASA NTRS1994

VLSI technology for smaller, cheaper, faster return link systems

Very Large Scale Integration (VLSI) Application-specific Integrated Circuit (ASIC) technology has enabled substantially smaller, cheaper, and more capable telemetry data systems. However, the rapid growth in available ASIC fabrication densities has far outpaced the application of this technology to telemetry systems. Available densities have grown by well over an order magnitude since NASA's Goddard Space Flight Center (GSFC) first began developing ASIC's for ground telemetry systems in 1985. To take advantage of these higher integration levels, a new generation of ASIC's for return link telemetry processing is under development. These new submicron devices are designed to further reduce the cost and size of NASA return link processing systems while improving performance. This paper describes these highly integrated processing components.

Nanzetta, Kathy↗
NASA NTRS1999

National Cycle Program (NCP) Common Analysis Tool for Aeropropulsion

Through the NASA/Industry Cooperative Effort (NICE) agreement, NASA Lewis and industry partners are developing a new engine simulation, called the National Cycle Program (NCP), which is the initial framework of NPSS. NCP is the first phase toward achieving the goal of NPSS. This new software supports the aerothermodynamic system simulation process for the full life cycle of an engine. The National Cycle Program (NCP) was written following the Object Oriented Paradigm (C++, CORBA). The software development process used was also based on the Object Oriented paradigm. Software reviews, configuration management, test plans, requirements, design were all apart of the process used in developing NCP. Due to the many contributors to NCP, the stated software process was mandatory for building a common tool intended for use by so many organizations. The U.S. aircraft and airframe companies recognize NCP as the future industry standard for propulsion system modeling.

Follen, G.↗
NASA NTRS2016

Investigating the Simulink Auto-Coding Process

Model based program design is the most clear and direct way to develop algorithms and programs for interfacing with hardware. While coding "by hand" results in a more tailored product, the ever-growing size and complexity of modern-day applications can cause the project work load to quickly become unreasonable for one programmer. This has generally been addressed by splitting the product into separate modules to allow multiple developers to work in parallel on the same project, however this introduces new potentials for errors in the process. The fluidity, reliability and robustness of the code relies on the abilities of the programmers to communicate their methods to one another; furthermore, multiple programmers invites multiple potentially differing coding styles into the same product, which can cause a loss of readability or even module incompatibility. Fortunately, Mathworks has implemented an auto-coding feature that allows programmers to design their algorithms through the use of models and diagrams in the graphical programming environment Simulink, allowing the designer to visually determine what the hardware is to do. From here, the auto-coding feature handles converting the project into another programming language. This type of approach allows the designer to clearly see how the software will be directing the hardware without the need to try and interpret large amounts of code. In addition, it speeds up the programming process, minimizing the amount of man-hours spent on a single project, thus reducing the chance of human error as well as project turnover time. One such project that has benefited from the auto-coding procedure is Ramses, a portion of the GNC flight software on-board Orion that has been implemented primarily in Simulink. Currently, however, auto-coding Ramses into C++ requires 5 hours of code generation time. This causes issues if the tool ever needs to be debugged, as this code generation will need to occur with each edit to any part of the program; additionally, this is lost time that could be spent testing and analyzing the code. This is one of the more prominent issues with the auto-coding process, and while much information is available with regard to optimizing Simulink designs to produce efficient and reliable C++ code, not much research has been made public on how to reduce the code generation time. It is of interest to develop some insight as to what causes code generation times to be so significant, and determine if there are architecture guidelines or a desirable auto-coding configuration set to assist in streamlining this step of the design process for particular applications. To address the issue at hand, the Simulink coder was studied at a foundational level. For each different component type made available by the software, the features, auto-code generation time, and the format of the generated code were analyzed and documented. Tools were developed and documented to expedite these studies, particularly in the area of automating sequential builds to ensure accurate data was obtained. Next, the Ramses model was examined in an attempt to determine the composition and the types of technologies used in the model. This enabled the development of a model that uses similar technologies, but takes a fraction of the time to auto-code to reduce the turnaround time for experimentation. Lastly, the model was used to run a wide array of experiments and collect data to obtain knowledge about where to search for bottlenecks in the Ramses model. The resulting contributions of the overall effort consist of an experimental model for further investigation into the subject, as well as several automation tools to assist in analyzing the model, and a reference document offering insight to the auto-coding process, including documentation of the tools used in the model analysis, data illustrating some potential problem areas in the auto-coding process, and recommendations on areas or practices in the current Ramses model that should be further investigated. Several skills were required to be built up over the course of the internship project. First and foremost, my Simulink skills have improved drastically, as much of my experience had been modeling electronic circuits as opposed to software models. Furthermore, I am now comfortable working with the Simulink Auto-coder, a tool I had never used until this summer; this tool also tested my critical thinking and C++ knowledge as I had to interpret the C++ code it was generating and attempt to understand how the Simulink model affected the generated code. I had come into the internship with a solid understanding of Matlab code, but had done very little in using it to automate tasks, particularly Simulink tasks; along the same lines, I had rarely used shell script to automate and interface with programs, which I gained a fair amount of experience with this summer, including how to use regular expression. Lastly, soft-skills are an area everyone can continuously improve on; having never worked with NASA engineers, which to me seem to be a completely different breed than what I am used to (commercial electronic engineers), I learned to utilize the wealth of knowledge present at JSC. I wish I had come into the internship knowing exactly how helpful everyone in my branch would be, as I would have picked up on this sooner. I hope that having gained such a strong foundation in Simulink over this summer will open the opportunity to return to work on this project, or potentially other opportunities within the division. The idea of leaving a project I devoted ten weeks to is a hard one to cope with, so having the chance to pick up where I left off sounds appealing; alternatively, I am interested to see if there are any opening in the future that would allow me to work on a project that is more in-line with my research in estimation algorithms. Regardless, this summer has been a milestone in my professional career, and I hope this has started a long-term relationship between JSC and myself. I really enjoy the thought of building on my experience here over future summers while I work to complete my PhD at Missouri University of Science and Technology.

Gualdoni, Matthew J.↗
NASA NTRS1981

Earth feature identification for onboard multispectral data editing: Computational experiments

A computational model of the processes involved in multispectral remote sensing and data classification is developed as a tool for designing smart sensors which can process, edit, and classify the data that they acquire. An evaluation of sensor system performance and design tradeoffs involves classification rates and errors as a function of number and location of spectral channels, radiometric sensitivity and calibration accuracy, target discrimination assignments, and accuracy and frequency of compensation for imaging conditions. This model provides a link between the radiometric and statistical properties of the signals to be classified and the performance characteristics of electro-optical sensors and data processing devices. Preliminary computational results are presented which illustrate the editing performance of several remote sensing approaches.

Aherron, R. M.↗
NASA NTRS2022

Run Time Assurance for Electric Vertical Takeoff and Landing Aircraft

NASA is conducting research to demonstrate and evaluate the application of Run Time Assurance (RTA) as a means to assure safety in Electric Vertical Takeoff and Landing (eVTOL) aircraft with highly automated or autonomous flight capability supervised by a single onboard pilot. The work described in this report demonstrates an application of RTA and examines the implications for design and analysis of aircraft functions and systems; aircraft safety hazards; safety assurance; development assurance; and pilot tasks and performance. This research effort also seeks to assess the efficacy of the combined application of traditional Functional Hazard Analysis (FHA) and the more modern System Theoretic Process Analysis (STPA) techniques to perform hazard analyses on aircraft with complex automated and autonomous systems and an onboard pilot. During the research effort we developed architectural designs of two alternate eVTOL aircraft, generally following the process characterized in the SAE standards ARP4754 and ARP4761. The design has focused on the control architectures of these aircraft, which are identical except that one incorporates RTA techniques to reduce the criticality of some key software components. Artifacts of this process include a taxonomy of aircraft-level functions, aircraft-level architecture diagrams, aircraft-level functional hazard assessments (AFHA), function allocations onto aircraft systems and subsystems, functional block diagrams for a select set of control-related functions, and system-level functional hazard assessments (SFHA) for those functions. This project has highlighted the notion that DAL D is something of a sweet spot for low-confidence controllers in an RTA-based design. Among the many activities described in DO-178C, the activities related to requirement verifiability, algorithmic accuracy, and test coverage can be the most challenging for the kinds of advanced control techniques that may be desirable in novel UAM designs, such as adaptive control, machine-learning, artificial intelligence, numerical search, and Monte Carlo based algorithms. Moreover, the standard requires that development teams demonstrate that errors leading to unacceptable failure conditions have been removed from the software. The RTA architecture, which cordons off the low-confidence function, makes it much easier to show this for these kinds of algorithms. With regard to the use of STPA and FHA as complementary hazard analysis techniques, our research effort led us to the conclusion that STPA should be used to derive requirements for hardware and software systems and/or components. Also, STPA is a natural complement to other processes in ARP4754A involving design studies and iteration.

Run-time assurance↗
NASA NTRS2019

A Knowledge-Based Optimization Method for Aerodynamic Design

A new aerodynamic design method, CODISC, has been developed that combines a legacy knowledge-based design method, CDISC, with a simple optimization module known as SOUP. The primary goal of this new design system is to improve the performance gains obtained using CDISC without adding significant computational time. An additional objective of this approach is to reduce the need for a priori knowledge of good initial input variable values, as well as for subsequent manual revisions of those values as the design progresses. Several test cases illustrate the development of the process to date and some of the options available at transonic and supersonic speeds for turbulent flow designs. The test cases generally start from good baseline configurations and, in all cases, were able to improve the performance. Several new guidelines for good initial values for the design variables, as well as new design rules within CDISC itself, were developed from these cases.

SOUP↗
NASA NTRS2003

Analysis and Test Correlation of Proof of Concept Box for Blended Wing Body-Low Speed Vehicle

The Low Speed Vehicle (LSV) is a 14.2% scale remotely piloted vehicle of the revolutionary Blended Wing Body concept. The design of the LSV includes an all composite airframe. Due to internal manufacturing capability restrictions, room temperature layups were necessary. An extensive materials testing and manufacturing process development effort was underwent to establish a process that would achieve the high modulus/low weight properties required to meet the design requirements. The analysis process involved a loads development effort that incorporated aero loads to determine internal forces that could be applied to a traditional FEM of the vehicle and to conduct detailed component analyses. A new tool, Hypersizer, was added to the design process to address various composite failure modes and to optimize the skin panel thickness of the upper and lower skins for the vehicle. The analysis required an iterative approach as material properties were continually changing. As a part of the material characterization effort, test articles, including a proof of concept wing box and a full-scale wing, were fabricated. The proof of concept box was fabricated based on very preliminary material studies and tested in bending, torsion, and shear. The box was then tested to failure under shear. The proof of concept box was also analyzed using Nastran and Hypersizer. The results of both analyses were scaled to determine the predicted failure load. The test results were compared to both the Nastran and Hypersizer analytical predictions. The actual failure occurred at 899 lbs. The failure was predicted at 1167 lbs based on the Nastran analysis. The Hypersizer analysis predicted a lower failure load of 960 lbs. The Nastran analysis alone was not sufficient to predict the failure load because it does not identify local composite failure modes. This analysis has traditionally been done using closed form solutions. Although Hypersizer is typically used as an optimizer for the design process, the failure prediction was used to help gain acceptance and confidence in this new tool. The correlated models and process were to be used to analyze the full BWB-LSV airframe design. The analysis and correlation with test results of the proof of concept box is presented here, including the comparison of the Nastran and Hypersizer results.

Spellman, Regina L.↗
NASA NTRS2012

Designing Mission Operations for the Gravity Recovery and Interior Laboratory Mission

NASA's Gravity Recovery and Interior Laboratory (GRAIL) mission, to understand the internal structure and thermal evolution of the Moon, offered unique challenges to mission operations. From launch through end of mission, the twin GRAIL orbiters had to be operated in parallel. The journey to the Moon and into the low science orbit involved numerous maneuvers, planned on tight timelines, to ultimately place the orbiters into the required formation-flying configuration necessary. The baseline GRAIL mission is short, only 9 months in duration, but progressed quickly through seven very unique mission phases. Compressed into this short mission timeline, operations activities and maneuvers for both orbiters had to be planned and coordinated carefully. To prepare for these challenges, development of the GRAIL Mission Operations System began in 2008. Based on high heritage multi-mission operations developed by NASA's Jet Propulsion Laboratory and Lockheed Martin, the GRAIL mission operations system was adapted to meet the unique challenges posed by the GRAIL mission design. This paper describes GRAIL's system engineering development process for defining GRAIL's operations scenarios and generating requirements, tracing the evolution from operations concept through final design, implementation, and validation.

MOS↗
NASA NTRS2003

Optimizing spacecraft design - optimization engine development : progress and plans

At JPL and NASA, a process has been developed to perform life cycle risk management. This process requires users to identify: goals and objectives to be achieved (and their relative priorities), the various risks to achieving those goals and objectives, and options for risk mitigation (prevention, detection ahead of time, and alleviation). Risks are broadly defined to include the risk of failing to design a system with adequate performance, compatibility and robustness in addition to more traditional implementation and operational risks. The options for mitigating these different kinds of risks can include architectural and design choices, technology plans and technology back-up options, test-bed and simulation options, engineering models and hardware/software development techniques and other more traditional risk reduction techniques.

risk↗
NASA NTRS1985

Processing technology for high efficiency silicon solar cells

Recent advances in silicon solar cell processing have led to attainment of conversion efficiency approaching 20%. The basic cell design is investigated and features of greatest importance to achievement of 20% efficiency are indicated. Experiments to separately optimize high efficiency design features in test structures are discussed. The integration of these features in a high efficiency cell is examined. Ion implantation has been used to achieve optimal concentrations of emitter dopant and junction depth. The optimization reflects the trade-off between high sheet conductivity, necessary for high fill factor, and heavy doping effects, which must be minimized for high open circuit voltage. A second important aspect of the design experiments is the development of a passivation process to minimize front surface recombination velocity. The manner in which a thin SiO2 layer may be used for this purpose is indicated without increasing reflection losses, if the antireflection coating is properly designed. Details are presented of processing intended to reduce recombination at the contact/Si interface. Data on cell performance (including CZ and ribbon) and analysis of loss mechanisms are also presented.

Spitzer, M. B.↗