An overview of AP 233: STEP's systems engineering standard
Explore the source record for details and available documents.
STEP system engineering↗
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.
From determinism to emergence: systems engineering a step change in execution on Mars
This paper discusses the challenges and considerations in systems engineering the first planned autonomous high-level activity planner on Mars.
Kuhn, Stephen↗
STEP-AIRSEDS System Engineering Support
This report summarizes and highlights the activities in support of the Space Transportation using Electrodynamic Propulsion Atmospheric Ionospheric Research Small Expendable Deployer Satellite (STEP-AIRSEDS) Project for the period of May 16, 2000 through September 28, 2001. The Alpha Technology, Inc. was tasked to provide support to the MSFC (Marshall Space Flight Center) in requirements development and in verification activities. Specifically, the Alpha Technology, Inc. task was to: (1) develop and maintain the STEP-AIRSEDS Project System Requirements Database; (2) develop and maintain the STEP-AIRSEDS requirements verification definition and planning support database; (3) perform requirements flow down analysis of STEP-AIRSEDS Project System Requirements to TMTC (The Michigan Technic Corporation) Level IV Requirements; (4) provide system engineering guidance to the Project as needed; (5) provide guidance to TMTC in preparation of Level IV Requirements; and (6) provide support to STEP-AIRSEDS meetings, reviews, and telecons as needed.
Rowell, Tom↗
Oversimplification of Systems Engineering Goals, Processes, and Criteria in NASA Space Life Support
This paper investigates the oversimplification of the inherently complex systems engineering process in space life support. The standard systems engineering process steps are described. The International Space Station (ISS) life support system is explained with its goals and performance criteria. Although it is not usually emphasized, the essential function of developing a hierarchy of systems and subsystems is to simplify the design process. The System Complexity Metric (SCM) shows how this di-vide-and-conquer approach also reduces the system complexity. The complete systems engineering process has many detailed steps. It is often simplified because of the effort required and the human limitations on working memory and decision span. Systems analysis demands slow, logical, and fo-cused thinking but is often bypassed in favor of quick, intuitive, subconscious “gut feel.” A study of 100 system designs found examples of 12 specific mental mistakes, such as ignoring stakeholder needs, and these mistakes are essentially oversimplifications of the systems engineering process. An analysis of space life support goals, options, criteria, and processes found 11 examples of oversimplifications in systems engineering, such as neglecting safety and cost. All these 11 oversimplifications could be traced to one or more of the 12 previously identified mental mistakes or other well-known ones, such as ig-noring sunk costs. Oversimplification of the systems engineering process is rarely noticed but is a common and harmful problem. A study of failures in 50 different space systems found that problems in systems engineering caused failures and often led to errors in design, development, and test that further contributed to failure. It seems that more diligent systems engineering could prevent many project problems and failures, but projects seem to be more guided by “gut feel” based on tradition, authority, and consensus than on the logical, rational systems engineering approach.
Simplified systems engineering↗
Model-Based Systems Engineering Pathfinder: Informing the Next Steps
In 2016, the NASA Engineering and Safety Center established a model-based systems engineering (MBSE) Pathfinder. The primary motivations for establishing the MBSE Pathfinder were to advance the Agency's applications of MBSE and capture lessons-learned to inform the next steps. The MBSE Pathfinder had four teams working in parallel for eight months on different topics of interest to NASA. The teams were encouraged to learn, and use creativity and innovation in their system modeling. The results were captured via reports, webinars, and a knowledge capture meeting. The approach taken for the MBSE Pathfinder was very successful in providing a number of lessons-learned for NASA and for other organizations considering MBSE or pathfinder efforts, and in building a very strong and collaborative user community.
Weiland, Karen J.↗
Assessing Alternatives in the Systems Engineering Process: Case Study of an Earth Observing Satellite Concept
Defining design alternatives constitutes one of the critical initial steps of the systems engineering process. Once these design alternatives have been identified, assessing which alternatives best satisfy the project’s objectives can prove to be challenging when dealing with complex decision frameworks. Complex systems often involve the participation of different interest groups, who have different value systems and are focused on distinct aspects of the project. For example, design alternatives might be assessed predominantly for their technical merit by one group of stakeholders, while a different group might be more inclined to assess the design alternatives primarily based on programmatic values. MESCAL (Monitoring the Evolving State of Clouds and Aerosol Layers) is an ongoing NASA / CNES (Centre National d’Etudes Spatiales) joint study for an active remote sensing Earth observing satellite. Several design alternatives have been identified and the assessment of these alternatives requires consideration of a variety of factors. This paper presents the approach that was used to support a global assessment of the MESCAL design alternatives. A mapping of the interactions between mission, instrument, and science requirements was modeled to support the assessment of the trade space. In addition, a set of metrics was developed to structure the assessment that was conducted. Finally, this paper also discusses the general applicability of these metrics to other science mission concepts in the formulation phase.
Ivanco, Marie L.↗
Control technology for future aircraft propulsion systems
The need for a more sophisticated engine control system is discussed. The improvements in better thrust-to-weight ratios demand the manipulation of more control inputs. New technological solutions to the engine control problem are practiced. The digital electronic engine control (DEEC) system is a step in the evolution to digital electronic engine control. Technology issues are addressed to ensure a growth in confidence in sophisticated electronic controls for aircraft turbine engines. The need of a control system architecture which permits propulsion controls to be functionally integrated with other aircraft systems is established. Areas of technology studied include: (1) control design methodology; (2) improved modeling and simulation methods; and (3) implementation technologies. Objectives, results and future thrusts are summarized.
Zeller, J. R.↗
Athena: Providing Insight into the History of the Universe
The American Institute for Aeronautics and Astronautics has provided a Request for Proposal which calls for a manned mission to a Near-Earth Object. It is the goal of Team COLBERT to respond to their request by providing a reusable system that can be implemented as a solid stepping stone for future manned trips to Mars and beyond. Despite Team COLBERT consisting of only students in Aerospace Engineering, in order to achieve this feat, the team must employ the use of Systems Engineering. Tools and processes from Systems Engineering will provide quantitative and semi-quantitative tools for making design decisions and evaluating items such as budgets and schedules. This paper will provide an in-depth look at some of the Systems Engineering processes employed and will step through the design process of a Human Asteroid Exploration System.
Murphy, Gloria A.↗
Control Implemented on Quantum Computers: Effects of Noise, Non-Determinism, and Entanglement
Quantum computing has advanced in recent years to the point that there are now some quantum computers and quantum simulators available to the public for use. In addition, quantum computing is beginning to receive attention within the process systems engineering community for directions such as machine learning and optimization. A logical next step for its evaluation within process systems engineering is for control, specifically, for computing control actions to be applied to process systems. In this work, we provide some initial studies regarding the implementation of control on quantum computers, including the implementation of a single-input/single-output proportional control law on a quantum simulator with noise, evaluation of potential impacts of non-determinism on theory for advanced control laws, and discussion of consequences of the way that entanglement works for next-generation manufacturing communication objectives.
Kip Nieman↗
A Model-Based Systems Engineering Journey to Developing a Concept of Operations
Starting in 2017, NASA’s Human Research Program (HRP) Exploration Medical Capability (ExMC) element began a systems engineering transition from traditional, document-centric development to model-centric development when defining its foundation medical systems. These foundation medical systems define a Concept of Operations (ConOps) and identify the generic requirements for a medical system based on assumptions about a generic crew and mission environments and guidance from NASA standards (e.g., Medical “Levels of Care”). By making the transition, ExMC intends to improve communication among stakeholders about foundation medical system requirements and content. In addition, this transition will enable ExMC to lower both development and crew treatment risks for future, mission-specific medical systems. ExMC followed a Model Based Systems Engineering (MBSE) paradigm when developing the foundation medical systems. A model-based approach provides several advantages over a traditional, document-centric approach. First, when Systems Engineers (SE) develop diagrams in a model using a standard modeling language, they produce information dense pictures that facilitate understanding much more efficiently with less room for misinterpretation than text. Second, due to the evolving nature of projects, documentation becomes out of date the minute it is published. This can result in people making decisions based on information that is no longer current, especially if they are referencing a locally-stored copy of a document. A model, on the other hand, is always up to date with the latest approved changes and information. It serves as a single point of truth. Third, a model-centric approach centralizes all important information in one place. Rather than having to flip through separate ConOps documents, design specifications, requirements specifications, and the like to coordinate information, a model captures the content in one, integrated spot. This integration makes tracing information from end-to-end easier with greater reliability. The ExMC Systems Engineering Lifecycle follows a well-defined process. ExMC Systems Engineers perform all major steps of the process, regardless of the development methodology. One of the first steps in the process is developing the ConOps that describes the operation of the system from the point of view of the users. It includes a list of the users and their needs, the goals of the medical system, key assumptions about the system, and definitions of the medical system’s operational environments. For this development effort, ExMC chose to replace the traditional text-based ConOps document with a model. While the decision to change the development workflow was not difficult, implementing the structural and organizational workflows were. It required showing ExMC’s users, most of whom are not Systems Engineers, how the information they require would be presented in the model and to gain their acceptance of this approach. This paper documents key lessons learned during the ConOps transformation by focusing on how the model represents information, the agile workflow used by SEs when developing the model and how it integrates into a project plan, how leadership influenced key users to accept the transformation, and how the users interact with the model information.
Jeffrey Robert Cohen↗
Finite element/finite volume approaches with adaptive time stepping strategies for transient thermal problems
An adaptive time stepping strategy for transient thermal analysis of engineering systems is described which computes the time step based on the local truncation error with a good global error control and obtains optimal time steps to be used during the analysis. Combined mesh partitionings involving FEM/FVM meshes based on physical situations to obtain numerically improved physical representations are also proposed. Numerical test cases are described and comparative pros and cons are identified for practical situations.
Mohan, Ram V.↗
MOS 2.0: The Next Generation in Mission Operations Systems
A Mission Operations System (MOS) or Ground System constitutes that portion of an overall space mission Enterprise that resides here on Earth. Over the past two decades, technological innovations in computing and software technologies have allowed an MOS to support ever more complex missions while consuming a decreasing fraction of Project development budgets. Despite (or perhaps, because of) such successes, it is routine to hear concerns about the cost of MOS development. At the same time, demand continues for Ground Systems which will plan more spacecraft activities with fewer commanding errors, provide scientists and engineers with more autonomous functionality, process and manage larger and more complex data more quickly, all while requiring fewer people to develop, deploy, operate and maintain them. One successful approach to such concerns over this period is a multimission approach, based on the reuse of portions (most often software) developed and used in previous missions. The Advanced Multi-Mission Operations System (AMMOS), developed for deep-space science missions, is one successful example of such an approach. Like many computing-intensive systems, it has grown up in a near-organic fashion from a relatively simple set of tools into a complexly interrelated set of capabilities. Such systems, like a city lacking any concept of urban planning, can and will grow in ways that are neither efficient nor particularly easy to sustain. To meet the growing demands and unyielding constraints placed on ground systems, a new approach is necessary. Under the aegis of a multi-year effort to revitalize the AMMOS's multimission operations capabilities, we are utilizing modern practices in systems architecting and model-based engineering to create the next step in Ground Systems: MOS 2.0. In this paper we outline our work (ongoing and planned) to architect and design a multimission MOS 2.0, describe our goals and measureable objectives, and discuss some of the benefits that this top-down, architectural approach holds for creating a more flexible and capable MOS for Missions while holding the line on cost.
ground systems↗
TERSSE. Definition of the total earth resources system for the shuttle era. Volume 10: (TOSS) TERSSE operational system study
Economic benefits studies regarding the application of remote sensing to resource management and the Total Earth Resources for the Shuttle Era (TERSSE) study to outline the structure and development of future systems are used, along with experience from LANDSAT and LACIE, to define the system performance and economics of an operational Earth Resources system. The system is to be based on current (LANDSAT follow-on) technology and its application to high priority resource management missions, such as global crop inventory. The TERSSE Operational System Study (TOSS) investigated system-level design alternatives using economic performance as the evaluation criterion. As such, the TOSS effort represented a significant step forward in the systems engineering and economic analysis of Earth Resources programs. By parametrically relating engineering design parameters, such as sensor performance details, to the economic benefit mechanisms a new level of confidence in the conclusions concerning the implementation of such systems can be reached.
Stow, W. K.↗
Model-Based Engineering Design for Trade Space Exploration throughout the Design Cycle
This paper presents ongoing work to standardize model-based system engineering as a complement to point design development in the conceptual design phase of deep space missions. It summarizes two first steps towards practical application of this capability within the framework of concurrent engineering design teams and their customers. The first step is standard generation of system sensitivities models as the output of concurrent engineering design sessions, representing the local trade space around a point design. A review of the chosen model development process, and the results of three case study examples, demonstrate that a simple update to the concurrent engineering design process can easily capture sensitivities to key requirements. It can serve as a valuable tool to analyze design drivers and uncover breakpoints in the design. The second step is development of rough-order- of-magnitude, broad-range-of-validity design models for rapid exploration of the trade space, before selection of a point design. At least one case study demonstrated the feasibility to generate such models in a concurrent engineering session. The experiment indicated that such a capability could yield valid system-level conclusions for a trade space composed of understood elements. Ongoing efforts are assessing the practicality of developing end-to-end system-level design models for use before even convening the first concurrent engineering session, starting with modeling an end-to-end Mars architecture.
models↗
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↗
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↗
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.↗
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↗