Results for “engineered systems” — Page 57

NASA NTRS1975

Space-based solar power conversion and delivery systems (study), engineering analysis

A systems analysis of synchronous, orbit-based power generation and relay systems that could be operational in the 1990's is described along with a comparison with earth-based systems to be operational in the same time frame. Operational and economic requirements for the orbiting systems and near term research activities which will be required to assure feasibility, development, launch and operational capabilities of such systems in the post- 1990 time frame are examined.

Nathan, C. A.↗

NASA NTRSDate not supplied

Establishing Trust in NASA’s Artemis Campaign Computer-Human Interface (CHI) Implementation

The NASA Artemis program will return humans to the Moon. This time, with the help of commercial and international partners, the program's objective is a permanent moon base. The moon base infrastructure, including an orbiting moon station and moon surface assets, will be developed for astronauts to stay for the long haul to learn to live and work on another planet in preparation for an eventual Humans-to-Mars mission. As the roundtrip communication delays increase in deep space exploration, the crew will need more onboard systems autonomy and functionality to maintain and control the vehicle or habitat. These mission constraints will change the current Earth-based spacecraft to ground control support approach that will demand more safe, efficient, and effective Computer-Human Interface (CHI) control. For Artemis, CHI is defined as the elements that the crew interfaces with: audio, video, lighting, and crew controls subsystems. Understanding how CHI will need to evolve to support deep space missions will be critical for the Artemis program--especially crew controls, which is the focus of this paper. How does NASA ensure crew controls are reliable enough to control complex systems and prevent a catastrophic event due to human error--especially when the astronauts could be physiologically and/or psychologically impaired? NASA's approach to mitigating catastrophic hazards in human spaceflight system development such as crew controls, is through a holistic system engineering and Human System Integration methodology that focuses on incorporating NASA's Human-Rating Requirements-that ensures human performance characteristics to control/safely recover the crew from hazardous situations within the human interface design are considered. This paper discusses, at a high level, CHI for the Artemis program. Next, a discussion of what it means to human-rate a space system crew controls and how trust in the human-computer interface begins with the NASA human rating requirements. Finally, a discussion on how systems engineering and the human system integration process ensures that crew control implementation incorporates the NASA human-rating requirements.

artemis↗

NASA NTRSDate not supplied

Establishing Trust in NASA’s Artemis Campaign Computer-Human Interface (CHI) Implementation

The NASA Artemis program will return humans to the Moon. This time, with the help of commercial and international partners, the program's objective is a permanent moon base. The moon base infrastructure, including an orbiting moon station and moon surface assets, will be developed for astronauts to stay for the long haul to learn to live and work on another planet in preparation for an eventual Humans-to-Mars mission. As the roundtrip communication delays increase in deep space exploration, the crew will need more onboard systems autonomy and functionality to maintain and control the vehicle or habitat. These mission constraints will change the current Earth-based spacecraft to ground control support approach that will demand more safe, efficient, and effective Computer-Human Interface (CHI) control. For Artemis, CHI is defined as the elements that the crew interfaces with: audio, video, lighting, and crew controls subsystems. Understanding how CHI will need to evolve to support deep space missions will be critical for the Artemis program--especially crew controls, which is the focus of this paper. How does NASA ensure crew controls are reliable enough to control complex systems and prevent a catastrophic event due to human error--especially when the astronauts could be physiologically and/or psychologically impaired? NASA's approach to mitigating catastrophic hazards in human spaceflight system development such as crew controls, is through a holistic system engineering and Human System Integration methodology that focuses on incorporating NASA's Human-Rating Requirements-that ensures human performance characteristics to control/safely recover the crew from hazardous situations within the human interface design are considered. This paper discusses, at a high level, CHI for the Artemis program. Next, a discussion of what it means to human-rate a space system crew controls and how trust in the human-computer interface begins with the NASA human rating requirements. Finally, a discussion on how systems engineering and the human system integration process ensures that crew control implementation incorporates the NASA human-rating requirements.

artemis↗

NASA NTRS2011

Software Users Manual (SUM): Extended Testability Analysis (ETA) Tool

This software user manual describes the implementation and use the Extended Testability Analysis (ETA) Tool. The ETA Tool is a software program that augments the analysis and reporting capabilities of a commercial-off-the-shelf (COTS) testability analysis software package called the Testability Engineering And Maintenance System (TEAMS) Designer. An initial diagnostic assessment is performed by the TEAMS Designer software using a qualitative, directed-graph model of the system being analyzed. The ETA Tool utilizes system design information captured within the diagnostic model and testability analysis output from the TEAMS Designer software to create a series of six reports for various system engineering needs. The ETA Tool allows the user to perform additional studies on the testability analysis results by determining the detection sensitivity to the loss of certain sensors or tests. The ETA Tool was developed to support design and development of the NASA Ares I Crew Launch Vehicle. The diagnostic analysis provided by the ETA Tool was proven to be valuable system engineering output that provided consistency in the verification of system engineering requirements. This software user manual provides a description of each output report generated by the ETA Tool. The manual also describes the example diagnostic model and supporting documentation - also provided with the ETA Tool software release package - that were used to generate the reports presented in the manual

Maul, William A.↗

NASA NTRS2005

HPT Clearance Control: Intelligent Engine Systems-Phase 1

The following work has been completed to satisfy the Phase I Deliverables for the "HPT Clearance Control" project under NASA GRC's "Intelligent Engine Systems" program: (1) Need for the development of an advanced HPT ACC system has been very clearly laid out, (2) Several existing and potential clearance control systems have been reviewed, (3) A scorecard has been developed to document the system, performance (fuel burn, range, payload, etc.), thermal, and mechanical characteristics of the existing clearance control systems, (4) Engine size and flight cycle selection for the advanced HPT ACC system has been reviewed with "large engine"/"long range mission" combination showing the most benefit, (5) A scoring criteria has been developed to tie together performance parameters for an objective, data driven comparison of competing systems, and (6) The existing HPT ACC systems have been scored based on this scoring system.

Source record↗

NASA NTRS1981

F100 engine diagnostic system status to date

An engine diagnostic system, proposed for the F100 engine, was tested in five specially modified Tactical Air Command F-15 aircraft during a 16-month flight evaluation. After more than 3300 engine operating hours encompassing almost 900 flights during the flight evaluation, these aircraft provided a data base, still being analyzed, that has shown successful demonstration of the original functional characteristics. Four general design requirements, recording engine operating time/low cycle fatigue event detection, engine trim, and trend and performance data collection were demonstrated. Also, validation of maintenance actions taken and indicated needed maintenance were successfully demonstrated.

Boyless, J. A.↗

NASA NTRSDate not supplied

MBSE Applications for the MSR SRC Mars Ascent Vehicle

The objective of the NASA Mars Sample Return (MSR) Campaign is to collect samples from the surface of Mars and return them to Earth for scientific research. The Mars Ascent Vehicle (MAV) will be integrated into a larger Mars Sample Retrieval Lander (SRL) for transit to and storage on Mars. After all Martian samples have been collected and loaded into the MAV payload assembly, MAV will deliver the samples from the Martian surface to Mars orbit. A separate spacecraft, the Earth Return Orbiter (ERO) will retrieve the samples from Mars orbit and return them to Earth. To address common systems engineering challenges associated with using traditional systems engineering practices on complex projects, the MAV systems engineering team has explored implementation of Model-Based Systems Engineering (MBSE) tools and languages. This paper describes the current state of implementation and development of the MAV MBSE model with the Systems Modeling Language (SysML) within the scope of the MAV Systems Requirement Cycle (SRC) systems engineering workflow. The MAV MBSE model has been developed within Magic Draw – a SysML editor commonly used to implement MBSE. The MAV MBSE model has been used to develop mission phase functional flow diagrams for the Concept of Operations, decompose mission to vehicle subsystem functions, develop a functional decomposition, derive functional requirements, trace requirements up to customer-imposed requirements, trace requirements within MAV requirement space, identify requirements trace gaps, define and map the physical design space architecture, allocate requirements to subsystems, develop validation items, define assembly, integration, and test (AI&T) operations, and trace these items across driving goals to develop an integrated digital thread of systems engineering information used to drive design specifications, decision making, and ultimately design verification and validation. Findings and results associated with implementing MBSE in these ways, alongside traditional methods will be discussed.

MBSE↗

NASA NTRSDate not supplied

MBSE Applications for the MSR SRC Mars Ascent Vehicle

The objective of the NASA Mars Sample Return (MSR) Campaign is to collect samples from the surface of Mars and return them to Earth for scientific research. The Mars Ascent Vehicle (MAV) will be integrated into a larger Mars Sample Retrieval Lander (SRL) for transit to and storage on Mars. After all Martian samples have been collected and loaded into the MAV payload assembly, MAV will deliver the samples from the Martian surface to Mars orbit. A separate spacecraft, the Earth Return Orbiter (ERO) will retrieve the samples from Mars orbit and return them to Earth. To address common systems engineering challenges associated with using traditional systems engineering practices on complex projects, the MAV systems engineering team has explored implementation of Model-Based Systems Engineering (MBSE) tools and languages. This paper describes the current state of implementation and development of the MAV MBSE model with the Systems Modeling Language (SysML) within the scope of the MAV Systems Requirement Cycle (SRC) systems engineering workflow. The MAV MBSE model has been developed within Magic Draw – a SysML editor commonly used to implement MBSE. The MAV MBSE model has been used to develop mission phase functional flow diagrams for the Concept of Operations, decompose mission to vehicle subsystem functions, develop a functional decomposition, derive functional requirements, trace requirements up to customer-imposed requirements, trace requirements within MAV requirement space, identify requirements trace gaps, define and map the physical design space architecture, allocate requirements to subsystems, develop validation items, define assembly, integration, and test (AI&T) operations, and trace these items across driving goals to develop an integrated digital thread of systems engineering information used to drive design specifications, decision making, and ultimately design verification and validation. Findings and results associated with implementing MBSE in these ways, alongside traditional methods will be discussed.

MBSE↗

NASA NTRS2001

Use of Soft Computing Technologies for a Qualitative and Reliable Engine Control System for Propulsion Systems

The problem to be addressed in this paper is to explore how the use of Soft Computing Technologies (SCT) could be employed to improve overall vehicle system safety, reliability, and rocket engine performance by development of a qualitative and reliable engine control system (QRECS). Specifically, this will be addressed by enhancing rocket engine control using SCT, innovative data mining tools, and sound software engineering practices used in Marshall's Flight Software Group (FSG). The principle goals for addressing the issue of quality are to improve software management, software development time, software maintenance, processor execution, fault tolerance and mitigation, and nonlinear control in power level transitions. The intent is not to discuss any shortcomings of existing engine control methodologies, but to provide alternative design choices for control, implementation, performance, and sustaining engineering, all relative to addressing the issue of reliability. The approaches outlined in this paper will require knowledge in the fields of rocket engine propulsion (system level), software engineering for embedded flight software systems, and soft computing technologies (i.e., neural networks, fuzzy logic, data mining, and Bayesian belief networks); some of which are briefed in this paper. For this effort, the targeted demonstration rocket engine testbed is the MC-1 engine (formerly FASTRAC) which is simulated with hardware and software in the Marshall Avionics & Software Testbed (MAST) laboratory that currently resides at NASA's Marshall Space Flight Center, building 4476, and is managed by the Avionics Department. A brief plan of action for design, development, implementation, and testing a Phase One effort for QRECS is given, along with expected results. Phase One will focus on development of a Smart Start Engine Module and a Mainstage Engine Module for proper engine start and mainstage engine operations. The overall intent is to demonstrate that by employing soft computing technologies, the quality and reliability of the overall scheme to engine controller development is further improved and vehicle safety is further insured. The final product that this paper proposes is an approach to development of an alternative low cost engine controller that would be capable of performing in unique vision spacecraft vehicles requiring low cost advanced avionics architectures for autonomous operations from engine pre-start to engine shutdown.

Trevino, Luis↗

NASA NTRS1992

Computer aided systems human engineering: A hypermedia tool

The Computer Aided Systems Human Engineering (CASHE) system, Version 1.0, is a multimedia ergonomics database on CD-ROM for the Apple Macintosh II computer, being developed for use by human system designers, educators, and researchers. It will initially be available on CD-ROM and will allow users to access ergonomics data and models stored electronically as text, graphics, and audio. The CASHE CD-ROM, Version 1.0 will contain the Boff and Lincoln (1988) Engineering Data Compendium, MIL-STD-1472D and a unique, interactive simulation capability, the Perception and Performance Prototyper. Its features also include a specialized data retrieval, scaling, and analysis capability and the state of the art in information retrieval, browsing, and navigation.

Boff, Kenneth R.↗

NASA NTRSDate not supplied

Open Innovation for a NASA Architecture Library

NASA’s Center of Excellence for Collaborative Innovation (CoECI) uses open innovation, or “crowdsourcing”, to access the global public to find ideas, concepts, designs, or solutions that meet a previously unmet need possibly resulting in significant advances in performance. The Center of Excellence for Collaborative Innovation was launched at the request of the White House Office of Science and Technology Policy. This is both a non-traditional method of innovation and a non-traditional method of outreach to the public to involve them in space technologies and programs. It has been used often for software development and new hardware technology. In this case we applied it to innovate with systems engineering tools for creating space architectures. The challenge was sponsored by NASA Engineering and Safety Center Systems Engineering Technical Fellow as part of a program for NASA’s adoption of MBSE. It was a trial to see if there would be as much participation or quality submissions with this more specialized topic and skill. The challenge sought space architecture representations and decompositions to create a library of modeled parts in a system modeling language (SysML). Mission architects mostly start from scratch to build model elements representing the functional and physical architecture of a system in SysML. There are a few beginning libraries, but these are also local to a program or group. A common library will save system engineers a large amount of time, will allow project stakeholders to recognize common graphics and quickly understand the architecture options. The challenge was promoted internationally, especially through professional organizations and universities with a systems engineering focus. It was open for 4 months, purposefully over the winter holiday break time to allow participants extra time outside of work or school. The challenge was designed so that expertise in space hardware was not necessary but getting to play with models of space architecture could provide motivation to participate. We did not receive as many entries as other broader outreach challenges, but the ones we received were extremely thorough and high quality. Solutions came from individuals and teams, students and professional consultants from the United States and Europe. We learned a few lessons about how to engage with the public and what characteristics of a problem result in good crowdsourcing results. The outreach challenge produced several useful ideas and modeled space elements, and the group will be engaging the winners to learn more about their new approaches.

innovation↗

NASA NTRSDate not supplied

Establishing Trust in NASA’s Artemis Program Computer-Human Interface (CHI) Implementation

The NASA Artemis program will return humans to the moon. This time, with the help of commercial and international partners, the program’s objective is a permanent moon base. The moon base infrastructure, including an orbiting moon station and moon surface assets, will be developed for astronauts to stay for the long haul to learn to live and work on another planet in preparation for an eventual Humans-to-Mars mission. As the roundtrip communication delays increase in deep space exploration, more onboard systems autonomy and functionality will be needed to maintain and control the vehicle or habitat. These mission constraints will change the current Earth-based spacecraft ground control support approach that will demand more safe, efficient, and effective Computer-Human Interface (CHI) control. For Artemis, CHI is defined as the elements that the crew interfaces with-audio, video, lighting, and crew controls. Understanding how CHI will need to evolve to support deep space missions will be critical for the Artemis program-especially crew controls which is the focus of this paper. How does NASA ensure crew controls are reliable to control complex systems and prevent a catastrophic event due to human error-especially when the astronauts could be physiologically and/or psychologically impaired? NASA’s approach to mitigating catastrophic hazards in human spaceflight system development such as crew controls is through a holistic system engineering and Human System Integration methodology that embraces NASA’s Human-Rating Requirements-ensuring human performance characteristics to control/safely recover the crew from hazardous situations within the human interface design are considered. This paper discusses, at a high level, CHI for the Artemis program. Next, a discussion of what it means to human-rate a space system crew controls and how trust in the human-computer interface begins with the NASA human rating requirements. Finally, a discussion on how systems engineering, and the human system integration process ensures that crew control implementation incorporates the NASA human-rating requirements.

Human-Rating↗

NASA NTRS1965

Apollo spacecraft control systems

Engine and attitude control systems for Apollo spacecraft

APOLLO SPACECRAFT↗

NASA NTRS2011

A Plan for Revolutionary Change in Gas Turbine Engine Control System Architecture

The implementation of Distributed Engine Control technology on the gas turbine engine has been a vexing challenge for the controls community. A successful implementation requires the resolution of multiple technical issues in areas such as network communications, power distribution, and system integration, but especially in the area of high temperature electronics. Impeding the achievement has been the lack of a clearly articulated message about the importance of the distributed control technology to future turbine engine system goals and objectives. To resolve these issues and bring the technology to fruition has, and will continue to require, a broad coalition of resources from government, industry, and academia. This presentation will describe the broad challenges facing the next generation of advanced control systems and the plan which is being put into action to successfully implement the technology on the next generation of gas turbine engine systems.

Culley, Dennis E.↗

DOE OSTI2022

Multilayered Network Models for Security: Enhancing System Security Engineering with Orchestration

Security engineering approaches can often focus on a particular domain—physical security, cyber security, or personnel security, for example. Yet, security systems engineering consistently faces challenges requiring socio-technical solutions to address evolving and dynamic complexity. While some drivers of this complexity stem from complex risk environments, innovative adversaries, and disruptive technologies, other drivers are endogenous and emerge from the interactions across security engineering approaches. In response, INCOSE's Systems Security Working Group identified the need to better coordinate “disparate security solutions [that] operate independently” as one of eleven key concepts in their IS21 FuSE Security Roadmap. From this perspective, this need for “security orchestration” aligns with the perspective that security is a property that emerges from interactions within complex systems. Current efforts at Sandia National Laboratories are developing a systems security engineering approach that describes high consequence facility (HCF) security as a multidomain set of interacting layers. The result is a multilayered network (MLN)-based approach that captures the interactions between infrastructure, physical components, digital components, and humans in nuclear security systems. This article will summarize the MLN-based approach to HCF security and describe two preliminary results demonstrating potential benefits from incorporating interactions across disparate security solutions. Here, leveraging the logical structure of networks, this MLN model-based approach provides an example of how security orchestration provides enhanced systems security engineering solutions.

42 ENGINEERING↗

NASA NTRS1989

Considerations for a design and operations knowledge support system for Space Station Freedom

Engineering and operations of modern engineered systems depend critically upon detailed design and operations knowledge that is accurate and authoritative. A design and operations knowledge support system (DOKSS) is a modern computer-based information system providing knowledge about the creation, evolution, and growth of an engineered system. The purpose of a DOKSS is to provide convenient and effective access to this multifaceted information. The complexity of Space Station Freedom's (SSF's) systems, elements, interfaces, and organizations makes convenient access to design knowledge especially important, when compared to simpler systems. The life cycle length, being 30 or more years, adds a new dimension to space operations, maintenance, and evolution. Provided here is a review and discussion of design knowledge support systems to be delivered and operated as a critical part of the engineered system. A concept of a DOKSS for Space Station Freedom (SSF) is presented. This is followed by a detailed discussion of a DOKSS for the Lyndon B. Johnson Space Center and Work Package-2 portions of SSF.

Erickson, Jon D.↗

NASA NTRS2004

State analysis requirements database for engineering complex embedded systems

It has become clear that spacecraft system complexity is reaching a threshold where customary methods of control are no longer affordable or sufficiently reliable. At the heart of this problem are the conventional approaches to systems and software engineering based on subsystem-level functional decomposition, which fail to scale in the tangled web of interactions typically encountered in complex spacecraft designs. Furthermore, there is a fundamental gap between the requirements on software specified by systems engineers and the implementation of these requirements by software engineers. Software engineers must perform the translation of requirements into software code, hoping to accurately capture the systems engineer's understanding of the system behavior, which is not always explicitly specified. This gap opens up the possibility for misinterpretation of the systems engineer's intent, potentially leading to software errors. This problem is addressed by a systems engineering tool called the State Analysis Database, which provides a tool for capturing system and software requirements in the form of explicit models. This paper describes how requirements for complex aerospace systems can be developed using the State Analysis Database.

model base engineering↗

DOE OSTI2020

Optical Engine Lockout System Design and Operation

Engine run days in the Diesel Combustion and Fuel Effects Lab are hectic. The long mental lists that must be kept by engine operators, paired with the tight time constraints between experiments, can cause operational issues that may be dangerous to personnel and/or cause damage to test equipment. Until now, a paper sign has been used to warn operators not to motor the engine when a foreign object has been placed inside of it. Unfortunately, this simple administrative control has failed in the past, motivating this effort to develop an improved system. The lockout system described in this document introduces an engineering control that, when activated, actually prevents the engine from being motored. The new system consists of a primary and a secondary control panel. Prior to an operator placing a foreign object into the cylinder, they press a button on the secondary control panel near the engine. This breaks the interlock circuit for the engine dynamometer and activates LEDs on both control panels to notify operators that a foreign object is present within the engine cylinder. Once the work is done and all foreign objects have been removed from the combustion chamber, two operators must be present to disable the system by simultaneously pressing the buttons on the primary and secondary control panels. Requiring a second operator to disable the system increases accountability and reduces the likelihood of potentially costly mistakes.

42 ENGINEERING↗