SEARCH · Search NASA
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.
A series of functional flow charts are considered that were developed to properly identify and record the degree of participation of the disciplines considered in this feasibility study and the type of data required in the design process.
Alternate processing methods have been investigated as a means of improving the mechanical properties of injection-molded SiC. Various mixing processes (dry, high-sheer, and fluid) were evaluated along with the morphology and particle size of the starting beta-SiC powder. Statistically-designed experiments were used to determine significant effects and interactions of variables in the mixing, injection molding, and binder removal process steps. Improvements in mechanical strength can be correlated with the reduction in flaw size observed in the injection molded green bodies obtained with improved processing methods.
This paper presents a case study of the knowledge engineering process employed to support the Link Monitor and Control Operator Assistant (LMCOA). The LMCOA is a prototype system which automates the configuration, calibration, test, and operation (referred to as precalibration) of the communications, data processing, metric data, antenna, and other equipment used to support space-ground communications with deep space spacecraft in NASA's Deep Space Network (DSN). The primary knowledge base in the LMCOA is the Temporal Dependency Network (TDN), a directed graph which provides a procedural representation of the precalibration operation. The TDN incorporates precedence, temporal, and state constraints and uses several supporting knowledge bases and data bases. The paper provides a brief background on the DSN, and describes the evolution of the TDN and supporting knowledge bases, the process used for knowledge engineering, and an analysis of the successes and problems of the knowledge engineering effort.
A bibliography is provided of materials presentations and publications resulting from NAGW-810.
This presentation reports on the NASA project to develop a prototype for RS-83 engine designed for use on reusable launch vehicles (RLV). Topics covered include: program objectives, overview schedule, organizational chart, integrated systems engineering processes, requirement analysis, catastrophic engine loss, maintainability analysis tools, and prototype design analysis.
For the last two years, NASA's Jet Propulsion Laboratory has been engaged in the process of re-engineering the way in which it does business. a signigicant portion of this effort is devoted toward improving engineering processes such as the building of advanced spacecraft and the design of scientific missions to investigate the solar system and beyond.
Summary of how KSC implements the characterization and cleanup of Remediation sites.
No abstract available
This poster illustrates my major and minor projects worked on during my entire time interning at KSC in the Materials Science Branch. My major projects consist of three Failure Analyses, a research project on Magnesium Alloys, and the manufacturing and mechanical testing of the Advanced Plant Habitat. My three Failure Analyses are Umbilical Testing Ground Plates, Lithium Ion Battery Locking Spring Blade, and a Liquid Oxygen Poppet.
Exploration-class missions to the moon, Mars and beyond will require a significant change in medical capability from today's low earth orbit centric paradigm. Significant increases in autonomy will be required due to differences in duration, distance and orbital mechanics. Aerospace medicine and systems engineering teams are working together within ExMC to meet these challenges. Identifying exploration medical system needs requires accounting for planned and unplanned medical care as defined in the concept of operations. In 2017, the ExMC Clinicians group identified medical capabilities to feed into the Systems Engineering process, including: determining what and how to address planned and preventive medical care; defining an Accepted Medical Condition List (AMCL) of conditions that may occur and a subset of those that can be treated effectively within the exploration environment; and listing the medical capabilities needed to treat those conditions in the AMCL. This presentation will discuss the team's approach to addressing these issues, as well as how the outputs of the clinical process impact the systems engineering effort.
This paper presents a case study of the knowledge engineering process employed to support the Link Monitor & Control Operator Assistant (LMCOA). The LMCOA is a prototype system which automates equipment used to support space-ground communication with deep space spacecraft in NASA's Deep Space Network (DSN). The primary knowledge base in the LMCOA is the Temporal Dependency Network (TDN). The paper provides a brief background on the DSN, and describes the evolution of the TDN and supporting knowledge bases, the process used for knowledge engineering, and an analysis of the successes--and problems--of the knowledge engineering effort.
The purpose of this handbook is to provide guidance for implementing the Risk Management (RM) requirements of NASA Procedural Requirements (NPR) document NPR 8000.4A, Agency Risk Management Procedural Requirements [1], with a specific focus on programs and projects, and applying to each level of the NASA organizational hierarchy as requirements flow down. This handbook supports RM application within the NASA systems engineering process, and is a complement to the guidance contained in NASA/SP-2007-6105, NASA Systems Engineering Handbook [2]. Specifically, this handbook provides guidance that is applicable to the common technical processes of Technical Risk Management and Decision Analysis established by NPR 7123.1A, NASA Systems Engineering Process and Requirements [3]. These processes are part of the \Systems Engineering Engine. (Figure 1) that is used to drive the development of the system and associated work products to satisfy stakeholder expectations in all mission execution domains, including safety, technical, cost, and schedule. Like NPR 7123.1A, NPR 8000.4A is a discipline-oriented NPR that intersects with product-oriented NPRs such as NPR 7120.5D, NASA Space Flight Program and Project Management Requirements [4]; NPR 7120.7, NASA Information Technology and Institutional Infrastructure Program and Project Management Requirements [5]; and NPR 7120.8, NASA Research and Technology Program and Project Management Requirements [6]. In much the same way that the NASA Systems Engineering Handbook is intended to provide guidance on the implementation of NPR 7123.1A, this handbook is intended to provide guidance on the implementation of NPR 8000.4A. 1.2 Scope and Depth This handbook provides guidance for conducting RM in the context of NASA program and project life cycles, which produce derived requirements in accordance with existing systems engineering practices that flow down through the NASA organizational hierarchy. The guidance in this handbook is not meant to be prescriptive. Instead, it is meant to be general enough, and contain a sufficient diversity of examples, to enable the reader to adapt the methods as needed to the particular risk management issues that he or she faces. The handbook highlights major issues to consider when managing programs and projects in the presence of potentially significant uncertainty, so that the user is better able to recognize and avoid pitfalls that might otherwise be experienced.
This paper explores the application of established roadmapping approaches in standards planning and roadmap development to support mission assurance objectives. Mission assurance requires proactive planning across multiple domains including technical, schedule, cost, organizational, and policy. The intersection of these domains happens at the enterprise level, and enterprise systems engineering processes can systematically guide mission assurance activities, including development of standards roadmaps. Standards planning and development is a critical contributor to an effective mission assurance strategy, although standards are often developed and adopted reactively. Technology and standards planning is a key Enterprise Process Management activity, as identified by the Systems Engineering Body of Knowledge, and technology and standards roadmaps are strategic tools used to enable that process. Technology roadmapping has proven effective in guiding enterprise architecture and concept design, and standards planning supports enterprise requirements definition and management. However, there are limited methodologies to guide such standards planning activities. The application of technology roadmapping principles to standards planning formalizes the process and establishes a repeatable framework for standards development and integration. The framework development described in this paper fills a methodological gap by adapting proven roadmapping techniques to standards planning. Through a comparison of roadmapping methodologies and a case study analysis, this approach outlines a systematic process for anticipating and planning standards needs. In the case of developing a standards integration roadmap for NASA’s Office of Safety and Mission Assurance (OSMA), technology roadmapping principles were adapted to develop a roadmap framework to allow NASA and OSMA to define an agency-wide standards integration plan for commercial and industry safety and mission assurance standards. The outcome highlights key adaptations required for roadmapping in a standards context and describes the process steps to formalize a standards planning activity. The roadmapping framework adapted for standards development and integration enables more strategic, forward-looking standards planning and allows for better alignment between evolving capabilities and mission assurance requirements. Beyond its application to mission assurance, this methodology can be transferred to other domains requiring standards development, providing a systematic approach that integrates systems engineering principles into policy strategy and decision-making processes.
NASA’s Model-Based Systems Engineering (MBSE) Infusion and Modernization Initiative (MIAMI) chartered a strategy group comprising early to mid-career NASA subject matter experts with diverse experiences to look into the future of systems engineering at NASA. The purpose of the group was to provide a vision for the future state of systems engineering practices and to develop a strategic plan to enable the evolution of the art up to 20 years in the future. The group used a design thinking approach to gather ideas and obtained insight into current engineering processes and domain outlook by interviewing engineers of varying expertise and experiences who had worked on teams of different sizes for missions large and small. The group built a roadmap to highlight future needs, projected capabilities, and technology and competency gaps and developed a strategic plan to ensure the expedient introduction of these capabilities. The resulting strategic plan recommends capability development and workforce strategies and provides guidance for Agency-wide SE policy. Artifacts, details, and raw data from the strategy team’s work are contained in NASA/TM-20205002911/SUPPL, Strategic Perspectives on the Future of Systems Engineering at NASA: Supplemental Information: Appendixes A to K.
Long duration Lunar and Martian missions will change the way NASA currently practices medicine. The missions will require more autonomous capability compared to current low Earth orbit operations. For the medical system, lack of consumable resupply, evacuation opportunities, and real-time ground support are key drivers toward greater autonomy. Recognition of the limited mission and vehicle resources available to carry out exploration missions motivates the Exploration Medical Capability (ExMC) Element’s approach to enabling the necessary autonomy. This element promotes human health and performance in space by advancing medical systems design and risk-informed decision-making for long-duration deep-space exploration missions (LDEMs). ExMC is using system engineering processes and Model-Based System Engineering (MBSE) tools to identify the user needs and requirements of LDEM medical systems. The MBSE approach to medical system design offers a paradigm shift toward greater integration between the vehicle and the medical system, and directly supports the transition of Earth-reliant International Space Station operations to the Earth-independent operations envisioned for LDEMs. This talk will provide a high-level overview of what the ExMC SE team has accomplished since the last IWS, an introduction to upcoming SE talks, and the ongoing systems engineering work.
Engineering data management, incorporating concepts of optimization with data representation, is receiving increasing attention as the amount and complexity of information necessary for performing engineering operations increases and the need to coordinate its representation and use increases. Research in this area promises advantages for a wide variety of engineering applications, particularly those which seek to use data in innovative ways in the engineering process. This paper presents a framework for a comprehensive, relational database management system that combines a knowledge base of design constraints with a database of engineering data items in order to achieve a 'generative database' - one which automatically generates new engineering design data according to the design constraints stored in the knowledge base. The representation requires a database that is able to store all of the data normally associated with engineering design and to accurately represent the interactions between constraints and the stored data while guaranteeing its integrity. The representation also requires a knowledge base that is able to store all the constraints imposed upon the engineering design process.
Process-based cost estimation plays a key role in effecting cultural change that integrates distributed science, technology and engineering teams to rapidly create innovative and affordable products. Working together, NASA Glenn Research Center and Boeing Canoga Park have developed a methodology of process-based cost estimation bridging the methodologies of high-level parametric models and detailed bottoms-up estimation. The NASA GRC/Boeing CP process-based cost model provides a probabilistic structure of layered cost drivers. High-level inputs characterize mission requirements, system performance, and relevant economic factors. Design alternatives are extracted from a standard, product-specific work breakdown structure to pre-load lower-level cost driver inputs and generate the cost-risk analysis. As product design progresses and matures the lower level more detailed cost drivers can be re-accessed and the projected variation of input values narrowed, thereby generating a progressively more accurate estimate of cost-risk. Incorporated into the process-based cost model are techniques for decision analysis, specifically, the analytic hierarchy process (AHP) and functional utility analysis. Design alternatives may then be evaluated not just on cost-risk, but also user defined performance and schedule criteria. This implementation of full-trade study support contributes significantly to the realization of the integrated development environment. The process-based cost estimation model generates development and manufacturing cost estimates. The development team plans to expand the manufacturing process base from approximately 80 manufacturing processes to over 250 processes. Operation and support cost modeling is also envisioned. Process-based estimation considers the materials, resources, and processes in establishing cost-risk and rather depending on weight as an input, actually estimates weight along with cost and schedule.
Design of large, complex space systems depends on significant model-based support for exploration of the design space. Integrated models predict system performance in mission-relevant terms given design descriptions and multiple physics-based numerical models. Both the design activities and the modeling activities warrant explicit process definitions and active process management to protect the project from excessive risk. Software and systems engineering processes have been formalized and similar formal process activities are under development for design engineering and integrated modeling. JPL is establishing a modeling process to define development and application of such system-level models.