Search NASA⌕ Search

SEARCH · Search NASA

Results for “Life Cycle Stages”

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
All sourcesNASA NTRSDOE OSTI
NASA NTRS1995

Low Noise Research Fan Stage Design

This report describes the design of a Low Noise ADP Research Fan stage. The fan is a variable pitch design which is designed at the cruise pitch condition. Relative to the cruise setting, the blade is closed at takeoff and opened for reverse thrust operation. The fan stage is a split flow design with fan exit guide vanes and core stators. This fan stage design was combined with a nacelle and engine core duct to form a powered fan/nacelle, subscale model. This model is intended for use in aerodynamic performance, acoustic and structural testing in a wind tunnel. The model has a 22-inch outer fan diameter and a hub-to-top ratio of 0.426 which permits the use of existing NASA fan and cowl force balance designs and rig drive system. The design parameters were selected to permit valid acoustic and aerodynamic comparisons with the PW 17-inch rig previously tested under NASA contract. The fan stage design is described in detail. The results of the design axisymmetric analysis at aerodynamic design condition are included. The structural analysis of the fan rotor and attachment is described including the material selections and stress analysis. The blade and attachment are predicted to have adequate low cycle fatigue life, and an acceptable operating range without resonant stress or flutter. The stage was acoustically designed with airfoil counts in the fan exit guide vane and core stator to minimize noise. A fan-FEGV tone analysis developed separately under NASA contract was used to determine these airfoil counts. The fan stage design was matched to a nacelle design to form a fan/nacelle model for wind tunnel testing. The nacelle design was developed under a separate NASA contract. The nacelle was designed with an axisymmetric inlet, cowl and nozzle for convenience in testing and fabrication. Aerodynamic analysis of the nacelle confirmed the required performance at various aircraft operating conditions.

Hobbs, David E.↗
NASA NTRS1993

Advanced Manned Launch System

Several alternatives exist for the development of the next manned launch system. The Advanced Manned Launch System (AMLS), which represents a clean-sheet replacement for the Space Shuttle, faces competition from concepts such as (1) the Personnel Launch System, which would serve as a personnel transport to complement the Space Shuttle, and (2) an advanced version of the existing Space Shuttle. An AMLS system could begin operations sometime between 2005 and 2020, depending upon the level of national interest and support. It would probably demonstrate a payload capacity less than that of the Space Shuttle, although performance specifications are far from certain. Even the form of the AMLS is still under discussion. Design studies have considered a wide variety of options including all levels of hardware reusability; single-, dual- and multiple-staging; and airbreathing vs. rocket propulsion. An evaluation of the relative cost-effectiveness of these options is impossible without guidance regarding basic mission requirements such as total number of launches over the system's life cycle and the date required. The availability of more advanced technologies will enable single-stage-to-orbit (SSTO) designs that are in general not feasible using current technology.

Talay, Theodore A.↗
NASA NTRS1997

Application of Domain Knowledge to Software Quality Assurance

This work focused on capturing, using, and evolving a qualitative decision support structure across the life cycle of a project. The particular application of this study was towards business process reengineering and the representation of the business process in a set of Business Rules (BR). In this work, we defined a decision model which captured the qualitative decision deliberation process. It represented arguments both for and against proposed alternatives to a problem. It was felt that the subjective nature of many critical business policy decisions required a qualitative modeling approach similar to that of Lee and Mylopoulos. While previous work was limited almost exclusively to the decision capture phase, which occurs early in the project life cycle, we investigated the use of such a model during the later stages as well. One of our significant developments was the use of the decision model during the operational phase of a project. By operational phase, we mean the phase in which the system or set of policies which were earlier decided are deployed and put into practice. By making the decision model available to operational decision makers, they would have access to the arguments pro and con for a variety of actions and can thus make a more informed decision which balances the often conflicting criteria by which the value of action is measured. We also developed the concept of a 'monitored decision' in which metrics of performance were identified during the decision making process and used to evaluate the quality of that decision. It is important to monitor those decision which seem at highest risk of not meeting their stated objectives. Operational decisions are also potentially high risk decisions. Finally, we investigated the use of performance metrics for monitored decisions and audit logs of operational decisions in order to feed an evolutionary phase of the the life cycle. During evolution, decisions are revisisted, assumptions verified or refuted, and possible reassessments resulting in new policy are made. In this regard we implemented a machine learning algorithm which automatically defined business rules based on expert assessment of the quality of operational decisions as recorded during deployment.

Wild, Christian W.↗
NASA NTRS2007

An Update on the Lithium-Ion Cell Low-Earth-Orbit Verification Test Program

A Lithium-Ion Cell Low-Earth-Orbit Verification Test Program is being conducted by NASA Glenn Research Center to assess the performance of lithium-ion (Li-ion) cells over a wide range of low-Earth-orbit (LEO) conditions. The data generated will be used to build an empirical model for Li-ion batteries. The goal of the modeling will be to develop a tool to predict the performance and cycle life of Li-ion batteries operating at a specified set of mission conditions. Using this tool, mission planners will be able to design operation points of the battery system while factoring in mission requirements and the expected life and performance of the batteries. Test conditions for the program were selected via a statistical design of experiments to span a range of feasible operational conditions for LEO aerospace applications. The variables under evaluation are temperature, depth-of-discharge (DOD), and end-of-charge voltage (EOCV). The baseline matrix was formed by generating combinations from a set of three values for each variable. Temperature values are 10 C, 20 C and 30 C. Depth-of-discharge values are 20%, 30% and 40%. EOCV values are 3.85 V, 3.95 V, and 4.05 V. Test conditions for individual cells may vary slightly from the baseline test matrix depending upon the cell manufacturer s recommended operating conditions. Cells from each vendor are being evaluated at each of ten sets of test conditions. Cells from four cell manufacturers are undergoing life cycle tests. Life cycling on the first sets of cells began in September 2004. These cells consist of Saft 40 ampere-hour (Ah) cells and Lith ion 30 Ah cells. These cells have achieved over 10,000 cycles each, equivalent to about 20 months in LEO. In the past year, the test program has expanded to include the evaluation of Mine Safety Appliances (MSA) 50 Ah cells and ABSL battery modules. The MSA cells will begin life cycling in October 2006. The ABSL battery modules consist of commercial Sony hard carbon 18650 lithium-ion cells configured in series and parallel combinations to create nominal 14.4 volt, 3 Ah packs (4s-2p). These modules have accumulated approximately 3000 cycles. Results on the performance of the cells and modules will be presented in this paper. The life prediction and performance model for Li-ion cells in LEO will be built by analyzing the data statistically and performing regression analysis. Cells are being cycled to failure so that differences in performance trends that occur at different stages in the life of the cell can be observed and accurately modeled. Cell testing is being performed at the Naval Surface Warfare Center in Crane, IN.

Reid, Concha M.↗
NASA NTRS1998

Designing for Change: Minimizing the Impact of Changing Requirements in the Later Stages of a Spaceflight Software Project

In the traditional 'waterfall' model of the software project life cycle, the Requirements Phase ends and flows into the Design Phase, which ends and flows into the Development Phase. Unfortunately, the process rarely, if ever, works so smoothly in practice. Instead, software developers often receive new requirements, or modifications to the original requirements, well after the earlier project phases have been completed. In particular, projects with shorter than ideal schedules are highly susceptible to frequent requirements changes, as the software requirements analysis phase is often forced to begin before the overall system requirements and top-level design are complete. This results in later modifications to the software requirements, even though the software design and development phases may be complete. Requirements changes received in the later stages of a software project inevitably lead to modification of existing developed software. Presented here is a series of software design techniques that can greatly reduce the impact of last-minute requirements changes. These techniques were successfully used to add built-in flexibility to two complex software systems in which the requirements were expected to (and did) change frequently. These large, real-time systems were developed at NASA Langley Research Center (LaRC) to test and control the Lidar In-Space Technology Experiment (LITE) instrument which flew aboard the space shuttle Discovery as the primary payload on the STS-64 mission.

Allen, B. Danette↗
NASA NTRS1994

A psychologist's view of validating aviation systems

All systems, no matter what they are designed to do, have shortcomings that may make them less productive than was hoped during the initial development. Such shortcomings can arise at any stage of development: from conception to the end of the implementation life cycle. While systems failure and errors of a lesser magnitude can occur as a function of mechanical or software breakdown, the majority of such problems, in aviation are usually laid on the shoulders of the human operator and, to a lesser extent, on human factors. The operator bears the responsibility and blame even though, from a human factors perspective, error may have been designed into the system. Human factors is not a new concept in aviation. The name may be new, but the issues related to operators in the loop date back to the industrial revolution of the nineteenth century and certainly to the aviation build-up for World War I. During this first global confrontation, military services from all sides discovered rather quickly that poor selection and training led to drastically increased personnel losses. While hardware design became an issue later, the early efforts were primarily focused on increased care in pilot selection and on their training. This actually involved early labor-intensive simulation, using such devices as sticks and chairs mounted on rope networks which could be manually moved in response to control input. The use of selection criteria and improved training led to more viable person-machine systems. More pilots survived training and their first ten missions in the air, a rule of thumb arrived at by experience which predicted ultimate survival better than any other. This rule was to hold through World War II. At that time, personnel selection and training became very sophisticated based on previous standards. Also, many psychologists were drafted into Army Air Corps programs which were geared towards refining the human factor. However, despite the talent involved in these programs and the tremendous build-up of aviation during the war, there were still aircraft designs that were man killers (no sexism implied since all combat pilots were men). One classic design error that was identified fifty years ago was the multipointer altimeter, which could easily be misread especially by a pilot under considerable task load. It has led to flying fully operational aircraft into the terrain. The authors of the research which formally identified this problem put 'Human Errors' in quotes to express their dissatisfaction with the traditional approach to accident investigation. It traditionally places the burden of guilt on the operator. Some of these altimeters still exist in older aircraft to this day.

Stein, Earl S.↗
NASA NTRS1993

Space transfer vehicle concepts and requirements. Volume 4: Summary of special studies

Our final report for Phase 1 addressed the future space transportation needs and requirements based on the current assets, at the time, and their evolution through technology/advanced development using a path and schedule that supported the world leadership role of the United States in a responsible and realistic financial forecast. Always, and foremost, the recommendations placed high values on the safety and success of missions both manned and unmanned through a total quality management philosophy at Martin Marietta. The second phase of the STV contract involved the use of Technical Directives (TD) to provide short-term support for specialized tasks as required by the COTR. Three of these tasks were performed in parallel with Phase 1. These tasks were the Liquid Acquisition Experiment (LACE), Liquid Reorientation Experiment (LIRE), and Expert System for Design, Operation, and Technology Studies (ESDOTS). The results of these TD's were reported in conjunction with the Phase 1 Final Report. Cost analysis of existing launch systems has demonstrated a need for a new upper stage that will increase America's competitiveness in the global launch services market. To provide a growth path of future exploration class STV's, near-term low-cost upper stages featuring modularity, portability, scalability, and evolvability must be developed. These recommendations define a program that: leverages ongoing activities to establish a new development environment, develop technologies that benefit the entire life cycle of a system, and result in a scalable hardware platform that provides a growth path to future upper stages.

Source record↗
NASA NTRS2006

Systems Integration Processes for NASA's Crew Launch Vehicle

NASA's Exploration Initiative will require development of many new elements to constitute a robust system of systems. New launch vehicles are needed to place cargo and crew in stable low earth orbit. This paper examines the systems integration processes NASA is utilizing to ensure integration and control of propulsion and non-propulsion elements within NASA's Crew Launch Vehicle (CLV). The objective of the CLV is to provide the transportation capabilities to meet the Constellation Program requirements for delivering a Crew Exploration Vehicle (CEV) or other payload to Low Earth Orbit (LEO) in support of the lunar and Mars missions. The CLV must successfully provide the capability within cost and schedule with an acceptable risk approach. This paper will describe in detail the systems engineering management processes that will be applied to assure CLV Project success through complete and efficient technical integration. Discussion of specific processes for requirements development and verification, integrated design and analysis, integrated simulation and testing and the integration of reliability, maintainability and supportability (RMS) into the design will also be included. The CLV Project is broken logically into elements by the major hardware groupings, and associated management, system engineering, and integration functions. The processes to be described herein are designed to integrate within these CLV elements and among the other Constellation projects. Launch vehicle stack integration (CLV to CEV, and Ground and Flight Operations integration) throughout the life cycle, including integrated vehicle performance through orbital insertion, recovery of the first stage, and reentry of the upper stage will also be discussed. The processes for decomposing requirements to the Elements and ensuring that requirements have been correctly validated, decomposed, allocated, and that the verification requirements are properly defined to ensure that the system design meets requirements will be discussed.

Reuter, James L.↗
NASA NTRS2006

Systems Integration Processes for NASA Ares I Crew Launch Vehicle

NASA's Exploration Initiative will require development of many new elements to constitute a robust system of systems. New launch vehicles are needed to place cargo and crew in stable Low Earth Orbit (LEO). This paper examines the systems integration processes NASA is utilizing to ensure integration and control of propulsion and nonpropulsion elements within NASA's Crew Launch Vehicle (CLV), now known as the Ares I. The objective of the Ares I is to provide the transportation capabilities to meet the Constellation Program requirements for delivering a Crew Exploration Vehicle (CEV) or other payload to LEO in support of the lunar and Mars missions. The Ares I must successfully provide this capability within cost and schedule, and with an acceptable risk approach. This paper will describe the systems engineering management processes that will be applied to assure Ares I Project success through complete and efficient technical integration. Discussion of technical review and management processes for requirements development and verification, integrated design and analysis, integrated simulation and testing, and the integration of reliability, maintainability and supportability (RMS) into the design will also be included. The Ares I Project is logically divided into elements by the major hardware groupings, and associated management, system engineering, and integration functions. The processes to be described herein are designed to integrate within these Ares I elements and among the other Constellation projects. Also discussed is launch vehicle stack integration (Ares I to CEV, and Ground and Flight Operations integration) throughout the life cycle, including integrated vehicle performance through orbital insertion, recovery of the first stage, and reentry of the upper stage. The processes for decomposing requirements to the elements and ensuring that requirements have been correctly validated, decomposed, and allocated, and that the verification requirements are properly defined to ensure that the system design meets requirements, will be discussed.

Taylor, James L.↗
NASA NTRS2009

Synergistic Development, Test, and Qualification Approaches for the Ares I and V Launch Vehicles

The U.S. National Aeronautics and Space Administration is designing and developing the Ares I and Ares V launch vehicles for access to the International Space Station (ISS) and human exploration of the Moon. The Ares I consists of a first stage reusable five-segment solid rocket booster, a upper stage using a J-2X engine derived from heritage experience (Saturn and Space Shuttle External Tank programs), and the Orion crew exploration vehicle (CEV). The Ares V is designed to minimize the development and overall life-cycle costs by leveraging off of the Ares I design. The Ares V consists of two boosters, a core stage, an earth departure stage (EDS), and a shroud. The core stage and EDS use LH2/LO2 propellants, metallic propellant tanks, and composite dry structures. The core stage has six RS-68B upgraded Delta IV engines while the EDS uses a J-2X engine for second stage ascent and trans-lunar injection (TLI) burn. System and propulsion tests and qualification approaches for Ares V elements are being considered as follow-on extensions of the Ares I development program. Following Ares I IOC, testing will be conducted to verify the J-2X engine's orbital restart and TLI burn capability. The Ares I upper stage operation will be demonstrated through integrated stage development and acceptance testing. The EDS will undergo similar development and acceptance testing with additional testing to verify aspects of cryogenic propellant management, operation of sub-systems in a space simulation environment, and orbital re-start of the main propulsion system. RS-68B certification testing will be conducted along with integrated core stage development and acceptance testing. Structural testing of the Ares V EDS and core stage propellant tanks will be conducted similar to the Ares I upper stage. The structural qualification testing may be accomplished with separate propellant tank test articles. Structural development and qualification testing of the dry structure will be pursued as part of the design and development process. Especially critical is the development test program for the composite structures. The Ares V payload shroud will undergo acoustic, vibration, structural qualification, and deployment testing in a space simulation environment. Similar to Ares I, requirements for full-scale structural dynamic testing are being studied. Both Ares I and Ares V include validation flight testing as part of the qualification programs.

Cockrell, Charles E.↗
NASA NTRS1972

The development of hurricane Inez, 1966, as shown by satellite nighttime radiometric and daytime television coverage

A complete documentation of Numbus 2 High Resolution infrared Radiometer data and ESSA-1 and 3 television photographs is presented for the life-time of Hurricane Inez, 1966. Ten computer produced radiation charts were analyzed in order to delineate the three dimensional cloud structure during the formative, mature and dissipating stages of this tropical cyclone. Time sections were drawn throughout the storm's life cycle to relate the warm core development and upper level outflow of the storm with their respective cloud canopies, as shown by the radiation data. Aerial reconnaissance weather reports, radar photographs and conventional weather analyses were used to complement the satellite data. A computer program was utilized to accept Nimbus 2 HRIR equivalent blackbody temperatures within historical maximum and minimum sea surface temperature limits over the tropical Atlantic Ocean.

Allison, L. J.↗
NASA NTRS1989

Hybrid Propulsion Technology Program, phase 1. Volume 1: Executive summary

The study program was contracted to evaluate concepts of hybrid propulsion, select the most optimum, and prepare a conceptual design package. Further, this study required preparation of a technology definition package to identify hybrid propulsion enabling technologies and planning to acquire that technology in Phase 2 and demonstrate that technology in Phase 3. Researchers evaluated two design philosophies for Hybrid Rocket Booster (HRB) selection. The first is an ASRM modified hybrid wherein as many components/designs as possible were used from the present Advanced Solid Rocket Motor (ASRM) design. The second was an entirely new hybrid optimized booster using ASRM criteria as a point of departure, i.e., diameter, thrust time curve, launch facilities, and external tank attach points. Researchers selected the new design based on the logic of optimizing a hybrid booster to provide NASA with a next generation vehicle in lieu of an interim advancement over the ASRM. The enabling technologies for hybrid propulsion are applicable to either and vehicle design may be selected at a downstream point (Phase 3) at NASA's discretion. The completion of these studies resulted in ranking the various concepts of boosters from the RSRM to a turbopump fed (TF) hybrid. The scoring resulting from the Figure of Merit (FOM) scoring system clearly shows a natural growth path where the turbopump fed solid liquid staged combustion hybrid provides maximized payload and the highest safety, reliability, and low life cycle costing.

Source record↗
NASA NTRS2007

Adapting Project Management Practices to Research-Based Projects

From dealing with the inherent uncertainties in outcomes of scientific research to the lack of applicability of current NASA Procedural Requirements guidance documentation, research-based projects present challenges that require unique application of classical project management techniques. If additionally challenged by the creation of a new program transitioning from basic to applied research in a technical environment often unfamiliar with the cost and schedule constraints addressed by project management practices, such projects can find themselves struggling throughout their life cycles. Finally, supplying deliverables to a prime vehicle customer, also in the formative stage, adds further complexity to the development and management of research-based projects. The Biomedical Research and Countermeasures Projects Branch at NASA Johnson Space Center encompasses several diverse applied research-based or research-enabling projects within the newly-formed Human Research Program. This presentation will provide a brief overview of the organizational structure and environment in which these projects operate and how the projects coordinate to address and manage technical requirements. We will identify several of the challenges (cost, technical, schedule, and personnel) encountered by projects across the Branch, present case reports of actions taken and techniques implemented to deal with these challenges, and then close the session with an open forum discussion of remaining challenges and potential mitigations.

Bahr, P.↗
NASA NTRS1998

Isothermal Fatigue, Damage Accumulation, and Life Prediction of a Woven PMC

This dissertation focuses on the characterization of the fully reversed fatigue behavior exhibited by a carbon fiber/polyimide resin, woven laminate at room and elevated temperatures. Nondestructive video edge view microscopy and destructive sectioning techniques were used to study the microscopic damage mechanisms that evolved. The residual elastic stiffness was monitored and recorded throughout the fatigue life of the coupon. In addition, residual compressive strength tests were conducted on fatigue coupons with various degrees of damage as quantified by stiffness reduction. Experimental results indicated that the monotonic tensile properties were only minimally influenced by temperature, while the monotonic compressive and fully reversed fatigue properties displayed noticeable reductions due to the elevated temperature. The stiffness degradation, as a function of cycles, consisted of three stages; a short-lived high degradation period, a constant degradation rate segment composing the majority of the life, and a final stage demonstrating an increasing rate of degradation up to failure. Concerning the residual compressive strength tests at room and elevated temperatures, the elevated temperature coupons appeared much more sensitive to damage. At elevated temperatures, coupons experienced a much larger loss in compressive strength when compared to room temperature coupons with equivalent damage. The fatigue damage accumulation law proposed for the model incorporates a scalar representation for damage, but admits a multiaxial, anisotropic evolutionary law. The model predicts the current damage (as quantified by residual stiffness) and remnant life of a composite that has undergone a known load at temperature. The damage/life model is dependent on the applied multiaxial stress state as well as temperature. Comparisons between the model and data showed good predictive capabilities concerning stiffness degradation and cycles to failure.

Gyekenyesi, Andrew L.↗
NASA NTRS2016

Early Engagement of Safety and Mission Assurance Expertise Using Systems Engineering Tools: A Risk-Based Approach to Early Identification of Safety and Assurance Requirements

Decades of systems engineering practice have demonstrated that the earlier the identification of requirements occurs, the lower the chance that costly redesigns will needed later in the project life cycle. A better understanding of all requirements can also improve the likelihood of a design's success. Significant effort has been put into developing tools and practices that facilitate requirements determination, including those that are part of the model-based systems engineering (MBSE) paradigm. These efforts have yielded improvements in requirements definition, but have thus far focused on a design's performance needs. The identification of safety & mission assurance (S&MA) related requirements, in comparison, can occur after preliminary designs are already established, yielding forced redesigns. Engaging S&MA expertise at an earlier stage, facilitated by the use of MBSE tools, and focused on actual project risk, can yield the same type of design life cycle improvements that have been realized in technical and performance requirements.

Requirement↗
NASA NTRS1989

Advanced Manned Launch Systems

Advanced Manned Launch Systems (AMLS) studies underway at the NASA Langley Research Center are part of a broader effort examining options for the next U.S. manned space transportation system. AMLS study phases have focused on investigating mission needs and identifying technologies and technology levels, concepts, systems, operational requirements, and life-cycle costs. For near-term technologies and an operations-oriented approach, two-stage vertical-takeoff rocket vehicles with significant levels of reusability are shown to be cost-effective for moderate to high flight rates. All-hydrogen fuel vehicles are also preferred over methane boosted systems from both operational and cost considerations.

Talay, Theodore A.↗
NASA NTRS2016

Augmenting Parametric Optimal Ascent Trajectory Modeling with Graph Theory

It has been well documented that decisions made in the early stages of Conceptual and Pre-Conceptual design commit up to 80% of total Life-Cycle Cost (LCC) while engineers know the least about the product they are designing [1]. Once within Preliminary and Detailed design however, making changes to the design becomes far more difficult to enact in both cost and schedule. Primarily this has been due to a lack of detailed data usually uncovered later during the Preliminary and Detailed design phases. In our current budget-constrained environment, making decisions within Conceptual and Pre-Conceptual design which minimize LCC while meeting requirements is paramount to a program's success. Within the arena of launch vehicle design, optimizing the ascent trajectory is critical for minimizing the costs present within such concerns as propellant, aerodynamic, aeroheating, and acceleration loads while meeting requirements such as payload delivered to a desired orbit. In order to optimize the vehicle design its constraints and requirements must be known, however as the design cycle proceeds it is all but inevitable that the conditions will change. Upon that change, the previously optimized trajectory may no longer be optimal, or meet design requirements. The current paradigm for adjusting to these updates is generating point solutions for every change in the design's requirements [2]. This can be a tedious, time-consuming task as changes in virtually any piece of a launch vehicle's design can have a disproportionately large effect on the ascent trajectory, as the solution space of the trajectory optimization problem is both non-linear and multimodal [3]. In addition, an industry standard tool, Program to Optimize Simulated Trajectories (POST), requires an expert analyst to produce simulated trajectories that are feasible and optimal [4]. In a previous publication the authors presented a method for combatting these challenges [5]. In order to bring more detailed information into Conceptual and Pre-Conceptual design, knowledge of the effects originating from changes to the vehicle must be calculated. In order to do this, a model capable of quantitatively describing any vehicle within the entire design space under consideration must be constructed. This model must be based upon analysis of acceptable fidelity, which in this work comes from POST. Design space interrogation can be achieved with surrogate modeling, a parametric, polynomial equation representing a tool. A surrogate model must be informed by data from the tool with enough points to represent the solution space for the chosen number of variables with an acceptable level of error. Therefore, Design Of Experiments (DOE) is used to select points within the design space to maximize information gained on the design space while minimizing number of data points required. To represent a design space with a non-trivial number of variable parameters the number of points required still represent an amount of work which would take an inordinate amount of time via the current paradigm of manual analysis, and so an automated method was developed. The best practices of expert trajectory analysts working within NASA Marshall's Advanced Concepts Office (ACO) were implemented within a tool called multiPOST. These practices include how to use the output data from a previous run of POST to inform the next, determining whether a trajectory solution is feasible from a real-world perspective, and how to handle program execution errors. The tool was then augmented with multiprocessing capability to enable analysis on multiple trajectories simultaneously, allowing throughput to scale with available computational resources. In this update to the previous work the authors discuss issues with the method and solutions.

Patrick D Dees↗
NASA NTRS2010

Model Based Definition

In September 2007, the Engineering Directorate at the Marshall Space Flight Center (MSFC) created the Design System Focus Team (DSFT). MSFC was responsible for the in-house design and development of the Ares 1 Upper Stage and the Engineering Directorate was preparing to deploy a new electronic Configuration Management and Data Management System with the Design Data Management System (DDMS) based upon a Commercial Off The Shelf (COTS) Product Data Management (PDM) System. The DSFT was to establish standardized CAD practices and a new data life cycle for design data. Of special interest here, the design teams were to implement Model Based Definition (MBD) in support of the Upper Stage manufacturing contract. It is noted that this MBD does use partially dimensioned drawings for auxiliary information to the model. The design data lifecycle implemented several new release states to be used prior to formal release that allowed the models to move through a flow of progressive maturity. The DSFT identified some 17 Lessons Learned as outcomes of the standards development, pathfinder deployments and initial application to the Upper Stage design completion. Some of the high value examples are reviewed.

Rowe, Sidney E.↗