Search NASA⌕ Search

SEARCH · Search NASA

Results for “STEP system engineering”

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 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Digital Prototyping Methods to Enable Product Development Analysis Cycle Compression in Aerospace Systems

Historically, the product development life cycle (spanning from origination of a systems concept to initial delivery or fielding) for large-scale aerospace systems is 10-25 years. Examples of recent programs exhibiting this timeline are the Space Shuttle (13 years), , International Space Station (18 years), NASA Hubble telescope (16 years), USAF F-35 Strike Fighter (22 years), Missile Defense Agency THAAD (21 years), USAF V-22 Osprey (26 years), USAF B-2 Spirt (19 years), US Army RAH-66 Comanche (22 years, cancelled prior to fielding), James Webb Space Telescope (25 years), Space Launch System (10 years). This list illustrates the challenges of developing and fielding a modern integrated multi-disciplinary aerospace system. These development timelines are often preceded by significant research and development programs and followed by multiple increments, blocks, or spirals to reach planned operational capability. In the modern era of aerospace system acquisition, there is significant pressure to reduce system development timelines to meet system objectives and enable competitiveness in the current industry and landscape. Across the aerospace industry, a range of rapid acquisition and prototyping programs are seeking to achieve system development within timelines considerably less than 10 years. Notably, in September of 2019, NASA issued a solicitation for the development and demonstration of a Human Landing System (HLS) to deliver humans to the lunar surface by 2024 (5 years) and for the development and demonstration of a more sustainable HLS by 2026 (7 years). Lengthy product development cycle timelines are a product of multiple factors ranging from programmatic, sociological, technical, and systems engineering issues. New approaches in systems engineering provide new ways to enable these compressed development timelines. These approaches employ expanded application of advanced systems engineering methods and cross-cutting digital tools to accelerate system development, utilizing digital prototyping to connect maturing sub-system or component technologies into system or system-of-systems hardware prototypes. Approaches such as the use of system integrating physics relationships to reduce the number of design analysis cycle iterations and state analysis modeling to reduce necessary software testing (and improving coverage of system execution scenarios) represent steps forward in reducing the engineering time needed to field new systems. In addition to cost, schedule and performance benefits, expanded digital exploration and demonstration reduce risk in live system test and demonstration. This incremental demonstration approach, where digital prototyping and demonstration leads and informs full system test and demonstration, could be more important for space applications because of the increased difficulty of test and demonstration of space systems and architectures. The Advanced Concepts Office (ACO) at Marshall Space Flight Center merges traditional multi-disciplinary concept definition methods with modern, cross-cutting systems engineering concepts to enable iterative design and analysis of space architectures and systems through coordinated, strategic management of human capital, technical processes, and technology. This paper provides an overview of that approach, including recent examples and a strategic path forward to enabling continued reduction of aerospace system product development life cycles.

Michael D Watson↗
NASA NTRS2016

Interface Management for a NASA Flight Project Using Model-Based Systems Engineering (MBSE)

The goal of interface management is to identify, define, control, and verify interfaces; ensure compatibility; provide an efficient system development; be on time and within budget; while meeting stakeholder requirements. This paper will present a successful seven-step approach to interface management used in several NASA flight projects. The seven-step approach using Model Based Systems Engineering will be illustrated by interface examples from the Materials International Space Station Experiment-X (MISSE-X) project. The MISSE-X was being developed as an International Space Station (ISS) external platform for space environmental studies, designed to advance the technology readiness of materials and devices critical for future space exploration. Emphasis will be given to best practices covering key areas such as interface definition, writing good interface requirements, utilizing interface working groups, developing and controlling interface documents, handling interface agreements, the use of shadow documents, the importance of interface requirement ownership, interface verification, and product transition.

Vipavetz, Kevin↗
NASA NTRS1981

The Watt Count System

The Watt Count System combines aerospace and computer technology, an engineering systems design approach and the environmental control expertise of a group of engineers who worked on Apollo. First step of the system is a computerized energy consumption analysis based on plans for a new home. Company calculates heating and cooling loads and customizes the most energy efficient system for the particular structure analyzed. A quality control engineer assures that insulation and ducting are installed to specifications. Analysis and design techniques are so accurate that company is able to give homeowner a two-year guarantee that the home's energy consumption will not exceed the kilowatt hour level determined by the computer in step one. In an annual energy performance comparison, a Watt Count home used 45 percent less energy than a conventionally equipped home.

Source record↗
NASA NTRS1993

A systems engineering initiative for NASA's space communications

In addition to but separate from the Red and Blue Teams commissioned by the NASA Administrator, NASA's Associate Administrator for Space Communications commissioned a Blue Team to review the Office of Space Communications (Code O) Core Program and determine how the program could be conducted faster, better, and cheaper, without compromising safety. Since there was no corresponding Red Team for the Code O Blue Team, the Blue Team assumed a Red Team independent attitude and challenged the status quo. The Blue Team process and results are summarized. The Associate Administrator for Space Communications subsequently convened a special management session to discuss the significance and implications of the Blue Team's report and to lay the groundwork and teamwork for the next steps, including the transition from engineering systems to systems engineering. The methodology and progress toward realizing the Code O Family vision and accomplishing the systems engineering initiative for NASA's space communications are presented.

Hornstein, Rhoda S.↗
NASA NTRS2016

A Process for Capturing the Art of Systems Engineering

There is both an art and a science to systems engineering. The science of systems engineering is effectively captured in processes and procedures, but the art is much more elusive. We propose that there is six step process that can be applied to any systems engineering organization to create an environment from which the "art" of that organization can be captured, be allowed to evolve collaboratively and be shared with all members of the organization. This paper details this process as it was applied to NASA Launch Services Program (LSP) Integration Engineering Branch during a pilot program of Confluence, a Commercial Off The Shelf (COTS) wiki tool.

Commercial Off The Shelf↗
DOE OSTI2020

A hybrid cyt c maturation system enhances the bioelectrical performance of engineered Escherichia coli by improving the rate-limiting step

Bioelectronic devices can use electron flux to enable communication between biotic components and abiotic electrodes. We have modified Escherichia coli to electrically interact with electrodes by expressing the cytochrome c from Shewanella oneidensis MR-1. However, we observe inefficient electrical performance, which we hypothesize is due to the limited compatibility of the E. coli cytochrome c maturation (Ccm) systems with MR-1 cytochrome c. Here we test whether the bioelectronic performance of E. coli can be improved by constructing hybrid Ccm systems containing protein domains from both E. coli and S. oneidensis MR-1. The hybrid CcmH increased cytochrome c expression by increasing the abundance of CymA 60%, while only slightly changing the abundance of the other cytochromes c. Electrochemical measurements showed that the overall current from the hybrid ccm strain increased 121% relative to the wildtype ccm strain, with an electron flux per cell of 12.3 ± 0.3 fA·cell -1 . Additionally, the hybrid ccm strain doubled its electrical response with the addition of exogenous flavin, and quantitative analysis of this demonstrates CymA is the rate-limiting step in this electron conduit. These results demonstrate that this hybrid Ccm system can enhance the bioelectrical performance of the cyt c expressing E. coli, allowing the construction of more efficient bioelectronic devices.

59 BASIC BIOLOGICAL SCIENCES↗
NASA NTRS2002

Second Generation RLV Space Vehicle Concept

NASA has a long history of conducting development programs and projects in a consistent fashion. Systems Engineering within those programs and projects has also followed a given method outlined by such documents as the NASA Systems Engineering Handbook. The relatively new NASA Space Launch Initiative (SLI) is taking a new approach to developing a space vehicle, with innovative management methods as well as new Systems Engineering processes. With the program less than a year into its life cycle, the efficacy of these new processes has yet to be proven or disproven. At $776M for phase 1, SLI represents a major portion of the NASA focus; however, the new processes being incorporated are not reflected in the training provided by NASA to its engineers. The NASA Academy of Program and Project Leadership (APPL) offers core classes in program and project management and systems engineering to NASA employees with the purpose of creating a "knowledge community where ideas, skills, and experiences are exchanged to increase each other's capacity for strong leadership". The SLI program is, in one sense, a combination of a conceptual design program and a technology program. The program as a whole doesn't map into the generic systems engineering project cycle as currently, and for some time, taught. For example, the NASA APPL Systems Engineering training course teaches that the "first step in developing an architecture is to define the external boundaries of the system", which will require definition of the interfaces with other systems and the next step will be to "define all the components that make up the next lower level of the system hierarchy" where fundamental requirements are allocated to each component. Whereas, the SLI technology risk reduction approach develops architecture subsystem technologies prior to developing architectures. The higher level architecture requirements are not allowed to fully develop and undergo decomposition and allocation down to the subsystems before the subsystems must develop allocated requirements based on the highest level of requirements. In the vernacular of the project cycles prior to the mid 1990's, the architecture definition portion of the program appears to be at a generic Phase A stage, while the subsystems are operating at Phase B. Even the management structure of the SLI program is innovative in its approach to Systems Engineering and is not reflected in the APPL training modules. The SLI program has established a Systems Engineering office as an office separate from the architecture development or the subsystem technology development, while that office does have representatives within these other offices. The distributed resources of the Systems Engineering Office are co-located with the respective Project Offices. This template is intended to provide systems engineering as an integrated function at the Program Level. the program management of SLI and the MAT agree that "program/project managers and the systems engineering team must work closely together towards the single objective of delivering quality products that meet the customer needs". This paper will explore the differences between the methods being taught by NASA, which represent decades of ideas, and those currently in practice in SLI. Time will tell if the innovation employed by SLI will prove to be the model of the future. For now, it is suggested that the training of the present exercise the flexibility of recognizing the new processes employed by a major new NASA program.

Bailey, Michelle↗
NASA NTRS1986

Development of an expert system prototype for determining software functional requirements for command management activities at NASA Goddard

The development of an expert system prototype for software functional requirement determination for NASA Goddard's Command Management System, as part of its process of transforming general requests into specific near-earth satellite commands, is described. The present knowledge base was formulated through interactions with domain experts, and was then linked to the existing Knowledge Engineering Systems (KES) expert system application generator. Steps in the knowledge-base development include problem-oriented attribute hierarchy development, knowledge management approach determination, and knowledge base encoding. The KES Parser and Inspector, in addition to backcasting and analogical mapping, were used to validate the expert system-derived requirements for one of the major functions of a spacecraft, the solar Maximum Mission. Knowledge refinement, evaluation, and implementation procedures of the expert system were then accomplished.

Liebowitz, J.↗
NASA NTRS2004

Requirements to Design to Code: Towards a Fully Formal Approach to Automatic Code Generation

A general-purpose method to mechanically transform system requirements into a provably equivalent model has yet to appear. Such a method represents a necessary step toward high-dependability system engineering for numerous possible application domains, including sensor networks and autonomous systems. Currently available tools and methods that start with a formal model of a system and mechanically produce a provably equivalent implementation are valuable but not sufficient. The gap that current tools and methods leave unfilled is that their formal models cannot be proven to be equivalent to the system requirements as originated by the customer. For the classes of systems whose behavior can be described as a finite (but significant) set of scenarios, we offer a method for mechanically transforming requirements (expressed in restricted natural language, or in other appropriate graphical notations) into a provably equivalent formal model that can be used as the basis for code generation and other transformations.

Hinchey, Michael G.↗
NASA NTRS2005

Towards an Automated Development Methodology for Dependable Systems with Application to Sensor Networks

A general-purpose method to mechanically transform system requirements into a probably equivalent model has yet to appeal: Such a method represents a necessary step toward high-dependability system engineering for numerous possible application domains, including sensor networks and autonomous systems. Currently available tools and methods that start with a formal model of a system and mechanically produce a probably equivalent implementation are valuable but not su8cient. The "gap" unfilled by such tools and methods is that their. formal models cannot be proven to be equivalent to the system requirements as originated by the customel: For the classes of systems whose behavior can be described as a finite (but significant) set of scenarios, we offer a method for mechanically transforming requirements (expressed in restricted natural language, or in other appropriate graphical notations) into a probably equivalent formal model that can be used as the basis for code generation and other transformations.

Hinchey, Michael G.↗
NASA NTRS2005

A Formal Approach to Requirements-Based Programming

No significant general-purpose method is currently available to mechanically transform system requirements into a provably equivalent model. The widespread use of such a method represents a necessary step toward high-dependability system engineering for numerous application domains. Current tools and methods that start with a formal model of a system and mechanically produce a provably equivalent implementation are valuable but not sufficient. The "gap" unfilled by such tools and methods is that the formal models cannot be proven to be equivalent to the requirements. We offer a method for mechanically transforming requirements into a provably equivalent formal model that can be used as the basis for code generation and other transformations. This method is unique in offering full mathematical tractability while using notations and techniques that are well known and well trusted. Finally, we describe further application areas we are investigating for use of the approach.

Hinchey, Michael G.↗
NASA NTRS2005

Requirements to Design to Code: Towards a Fully Formal Approach to Automatic Code Generation

A general-purpose method to mechanically transform system requirements into a provably equivalent model has yet to appear. Such a method represents a necessary step toward high-dependability system engineering for numerous possible application domains, including distributed software systems, sensor networks, robot operation, complex scripts for spacecraft integration and testing, and autonomous systems. Currently available tools and methods that start with a formal model of a system and mechanically produce a provably equivalent implementation are valuable but not sufficient. The gap that current tools and methods leave unfilled is that their formal models cannot be proven to be equivalent to the system requirements as originated by the customer. For the classes of systems whose behavior can be described as a finite (but significant) set of scenarios, we offer a method for mechanically transforming requirements (expressed in restricted natural language, or in other appropriate graphical notations) into a provably equivalent formal model that can be used as the basis for code generation and other transformations.

Hinchey, Michael G.↗
NASA NTRS2005

Requirements to Design to Code: Towards a Fully Formal Approach to Automatic Code Generation

A general-purpose method to mechanically transform system requirements into a provably equivalent model has yet to appear. Such a method represents a necessary step toward high-dependability system engineering for numerous possible application domains, including distributed software systems, sensor networks, robot operation, complex scripts for spacecraft integration and testing, and autonomous systems. Currently available tools and methods that start with a formal model of a: system and mechanically produce a provably equivalent implementation are valuable but not sufficient. The "gap" that current tools and methods leave unfilled is that their formal models cannot be proven to be equivalent to the system requirements as originated by the customer. For the ciasses of systems whose behavior can be described as a finite (but significant) set of scenarios, we offer a method for mechanically transforming requirements (expressed in restricted natural language, or in other appropriate graphical notations) into a provably equivalent formal model that can be used as the basis for code generation and other transformations.

Hinchey, Michael G.↗
NASA NTRS1985

Cost effective launch operations of the SSME

The Space Shuttle Main Engine (SSME) represents the beginning of reusable rocket engine operations in the space transportation system (STS). Steps taken to reduce the overall cost of flight operations of the SSME by improving turnaround operations, extending the life of the engine, and improving the cost effectiveness of overhaul operations at the Canoga Park home plant are described. Ground certification testing to ensure safe launch operations is described, as well as certification extension testing that leads to a service life equivalent to 40 flights. The proven flight record of the SSME, which has demonstrated the utility of the SSME as a key component of America's space transportation system, is discussed.

Klatt, F. P.↗
DOE OSTI2021

Simplifying and Visualizing the Ontology of Systems Engineering Models

The credibility of an engineering model is of critical importance in large-scale projects. How concerned should an engineer be when reusing someone else's model when they may not know the author or be familiar with the tools that were used to create it? In this report, the authors advance engineers' capabilities for assessing models through examination of the underlying semantic structure of a model--the ontology. This ontology defines the objects in a model, types of objects, and relationships between them. In this study, two advances in ontology simplification and visualization are discussed and are demonstrated on two systems engineering models. These advances are critical steps toward enabling engineering models to interoperate, as well as assessing models for credibility. For example, results of this research show an 80% reduction in file size and representation size, dramatically improving the throughput of graph algorithms applied to the analysis of these models. Finally, four future problems are outlined in ontology research toward establishing credible models--ontology discovery, ontology matching, ontology alignment, and model assessment.

42 ENGINEERING↗
NASA NTRS1990

Database Access Manager for the Software Engineering Laboratory (DAMSEL) user's guide

Operating instructions for the Database Access Manager for the Software Engineering Laboratory (DAMSEL) system are presented. Step-by-step instructions for performing various data entry and report generation activities are included. Sample sessions showing the user interface display screens are also included. Instructions for generating reports are accompanied by sample outputs for each of the reports. The document groups the available software functions by the classes of users that may access them.

Source record↗
NASA NTRSDate not supplied

A Scenario-Based Approach to Assess Continuity Gaps in Earth Observations

Decision analysis processes outlined in systems engineering references, such as the Systems Engineering Body of Knowledge [1] or the NASA Systems Engineering Handbook [2], recommend following a series of steps to support decision-making for engineering applications. These steps are consistent across the literature and typically involve defining objectives, defining relevant criteria against which candidate alternatives can be assessed, selecting an evaluation method, assessing alternatives, and making a recommendation based on this assessment. These approaches are well-suited to assess systems for which sets of common objectives and constraints can be identified. A vast body of literature describes their application to numerous engineering problems, and many methods have been developed since the middle of the 20th century to support the assessment of candidate alternatives for such systems [3, 4, 5, 6]. These approaches, however, show some limitations when decisions pertain to systems of systems. These collections of individual systems typically do not share a common set of objectives and constraints, tend to be highly complex, and the definition of assessable, high-value candidate alternatives poses a challenge due to interdependencies. The formulation, development, operation, and funding of Earth observing missions are such that gaps may occur between missions, therefore impacting the continuity of measurements. These Earth observing mission architectures constitute systems of systems for which a common set of objectives and constraints can be challenging to define. When tasked with assessing gaps that may occur for a series of spaceborne missions that address similar science parameters, the authors therefore proposed to depart from the traditional objective- and criteria-based approach and instead adopted a scenario-based approach. This approach does not require a prioritized set of common objectives; rather, it assesses the impact of possible decisions on the system-of-systems and characterizes its possible future states. It also offers the flexibility to adjust assumptions, update inputs, and refine supporting models over time, while enabling the rapid, early identification of challenges and key decision points. By simulating the impact of potential decisions on the entirety of the system-of-systems, the approach enables the synchronization of multiple decisions that typically occur at the level of the individual system. This paper provides an overview of the approach that was developed to assess continuity gaps for a series of operational and planned spaceborne Earth observing missions, a description of its application to the problem at hand, and a discussion of currently known limitations.

scenario earth observations continuity gaps↗
NASA NTRSDate not supplied

A Scenario-Based Approach to Assess Continuity Gaps in Earth Observations

Decision analysis processes outlined in systems engineering references, such as the Systems Engineering Body of Knowledge [1] or the NASA Systems Engineering Handbook [2], recommend following a series of steps to support decision-making for engineering applications. These steps are consistent across the literature and typically involve defining objectives, defining relevant criteria against which candidate alternatives can be assessed, selecting an evaluation method, assessing alternatives, and making a recommendation based on this assessment. These approaches are well-suited to assess systems for which sets of common objectives and constraints can be identified. A vast body of literature describes their application to numerous engineering problems, and many methods have been developed since the middle of the 20th century to support the assessment of candidate alternatives for such systems [3, 4, 5, 6]. These approaches, however, show some limitations when decisions pertain to systems of systems. These collections of individual systems typically do not share a common set of objectives and constraints, tend to be highly complex, and the definition of assessable, high-value candidate alternatives poses a challenge due to interdependencies. The formulation, development, operation, and funding of Earth observing missions are such that gaps may occur between missions, therefore impacting the continuity of measurements. These Earth observing mission architectures constitute systems of systems for which a common set of objectives and constraints can be challenging to define. When tasked with assessing gaps that may occur for a series of spaceborne missions that address similar science parameters, the authors therefore proposed to depart from the traditional objective- and criteria-based approach and instead adopted a scenario-based approach. This approach does not require a prioritized set of common objectives; rather, it assesses the impact of possible decisions on the system-of-systems and characterizes its possible future states. It also offers the flexibility to adjust assumptions, update inputs, and refine supporting models over time, while enabling the rapid, early identification of challenges and key decision points. By simulating the impact of potential decisions on the entirety of the system-of-systems, the approach enables the synchronization of multiple decisions that typically occur at the level of the individual system. This paper provides an overview of the approach that was developed to assess continuity gaps for a series of operational and planned spaceborne Earth observing missions, a description of its application to the problem at hand, and a discussion of currently known limitations.

scenario earth observations continuity gaps↗