Voyager spacecraft phase B, task D. Volume 11 - Engineering study task - Photo imaging system Final report
Systems engineering analysis of photoimaging systems for optimum photographic coverage of Mars during 1973 Voyager mission
SEARCH · Engineering Papers
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.
Systems engineering analysis of photoimaging systems for optimum photographic coverage of Mars during 1973 Voyager mission
The National Aeronautics and Space Administration's (NASA) Airspace Systems Program is contributing air traffic management research in support of the 2025 Next Generation Air Transportation System (NextGen). Contributions support research and development needs provided by the interagency Joint Planning and Development Office (JPDO). These needs generally call for integrated technical solutions that improve system-level performance and work effectively across multiple domains and planning time horizons. In response, the Airspace Systems Program is pursuing an integrated research approach and has adapted systems engineering best practices for application in a research environment. Systems engineering methods aim to enable researchers to methodically compare different technical approaches, consider system-level performance, and develop compatible solutions. Systems engineering activities are performed iteratively as the research matures. Products of this approach include a demand and needs analysis, system-level descriptions focusing on NASA research contributions, system assessment and design studies, and common systemlevel metrics, scenarios, and assumptions. Results from the first systems engineering iteration include a preliminary demand and needs analysis; a functional modeling tool; and initial system-level metrics, scenario characteristics, and assumptions. Demand and needs analysis results suggest that several advanced concepts can mitigate demand/capacity imbalances for NextGen, but fall short of enabling three-times current-day capacity at the nation s busiest airports and airspace. Current activities are focusing on standardizing metrics, scenarios, and assumptions, conducting system-level performance assessments of integrated research solutions, and exploring key system design interfaces.
Results of the flight demonstration of the adaptive engine control system (ADECS), an integrated flight and propulsion control system, are reported. The ADECS system provides additional engine thrust by increasing engine pressure ratio (EPR) at intermediate and afterburning power, with the amount of EPR uptrim modulated in accordance with the maneuver requirements, flight conditions, and engine information. As a result of EPR uptrimming, engine thrust has increased by as much as 10.5 percent, rate of climb has increased by 10 percent, and the time to climb from 10,000 to 40,000 ft has been reduced by 12.5 percent. Increases in acceleration of 9.3 and 13 percent have been obtained at intermediate and maximum power, respectively. No engine anomalies have been detected for EPR increases up to 12 percent.
Engineering feasibility and economics of reusable launch vehicle systems
Low speed inducers for rocket engine feed system
Engineering constraints in designing optimal and suboptimal feedback systems
Apollo service propulsion system rocket engine bipropellant valve improvement program - valve design guide and oxygen-hydrogen technology
A systematic approach to developing an engine monitoring system (EMS) is outlined. An extensive shopping list of EMS capabilities and benefits are included. A team approach to developing an EMS is emphasized with a description of the responsibilities of each team member.
An efficient diagnosis engine - a combination of mathematical models and algorithms - has been developed for identifying faulty components in a possibly complex engineering system. This model-based diagnosis engine embodies a twofold approach to reducing, relative to prior model-based diagnosis engines, the amount of computation needed to perform a thorough, accurate diagnosis. The first part of the approach involves a reconstruction of the general diagnostic engine to reduce the complexity of the mathematical-model calculations and of the software needed to perform them. The second part of the approach involves algorithms for computing a minimal diagnosis (the term "minimal diagnosis" is defined below). A somewhat lengthy background discussion is prerequisite to a meaningful summary of the innovative aspects of the present efficient model-based diagnosis engine. In model-based diagnosis, the function of each component and the relationships among all the components of the engineering system to be diagnosed are represented as a logical system denoted the system description (SD). Hence, the expected normal behavior of the engineering system is the set of logical consequences of the SD. Faulty components lead to inconsistencies between the observed behaviors of the system and the SD (see figure). Diagnosis - the task of finding faulty components - is reduced to finding those components, the abnormalities of which could explain all the inconsistencies. The solution of the diagnosis problem should be a minimal diagnosis, which is a minimal set of faulty components. A minimal diagnosis stands in contradistinction to the trivial solution, in which all components are deemed to be faulty, and which, therefore, always explains all inconsistencies.
The NASA/SP-2015-3709, Human Systems Integration (HSI) Practitioner's Guide, also known as the "HSIPG," provides a tool for implementing HSI activities within the NASA systems engineering framework. The HSIPG is written to aid the HSI practitioner engaged in a program or project (P/P), and serves as a knowledge base to allow the practitioner to step into an HSI lead or team member role for NASA missions. Additionally, this HSIPG is written to address the role of HSI in the P/P management and systems engineering communities and aid their understanding of the value added by incorporating good HSI practices into their programs and projects. Through helping to build a community of knowledgeable HSI practitioners, this document also hopes to build advocacy across the Agency for establishing strong, consistent HSI policies and practices. Human Systems Integration (HSI) has been successfully adopted (and adapted) by several federal agencies-most notably the U.S. Department of Defense (DoD) and the Nuclear Regulatory Commission (NRC)-as a methodology for reducing system life cycle costs (LCCs). These cost savings manifest themselves due to reductions in required numbers of personnel, the practice of human-centered design, decreased reliance on specialized skills for operations, shortened training time, efficient logistics and maintenance, and fewer safety-related risks and mishaps due to unintended human/system interactions. The HSI process for NASA establishes how cost savings and mission success can be realized through systems engineering. Every program or project has unique attributes. This HSIPG is not intended to provide one-size-fits-all recommendations for HSI implementation. Rather, HSI processes should be tailored to the size, scope, and goals of individual situations. The instructions and processes identified here are best used as a starting point for implementing human-centered system concepts and designs across programs and projects of varying types, including manned and unmanned, human spaceflight, aviation, robotics, and environmental science missions. The practitioner using this guide should have expertise in Systems Engineering or other disciplines involved in producing systems with anticipated human interactions. (See section 1.6 of this guide for further discussion on HSI discipline domains.) The HSIPG provides an "HSI layer" to the NASA Systems Engineering Engine (SEE), detailed in NASA Procedural Requirement (NPR) 7123.1B, NASA Systems Engineering Processes and Requirements, and further explained in NASA/SP-2007-6105, Systems Engineering Handbook (see HSIPG Table 2.2-1, NASA Documents with HSI Content, for specific references and document versions).
An Energy Efficient Engine (E3) program was established to develop technology for improving the energy efficiency of future commercial transport aircraft engines. As part of this program, General Electric designed and tested a new engine. The design, fabrication, bench and engine testing of the Full Authority Digital Electronic Control (FADEC) system used for controlling the E3 Demonstrator Engine is described. The system design was based on many of the proven concepts and component designs used on the General Electric family of engines. One significant difference is the use of the FADEC in place of hydromechanical computation currently used.
This document is a summary of the R&D activities associated with the Engineered Barrier Systems Work Package. Multiple facets of Engineered Barrier Systems (EBS) research were examined in the course of FY19 activities. This report is focused on delivering an update on the status and progress of modelling tools and experimental methods, both of which are essential to understanding and predicting long-term repository performance as part of the safety case. Specifically, the work described herein aims to improve understanding of EBS component evolution and interactions. Ultimately, the EBS Work Package is working towards producing process models for distinct processes that can either be incorporated into performance assessment (PA), or provide critical information for implementing better constraints on barrier performance. The main objective of this work is that the models being developed and refined will either be implemented directly into the Geologic Disposal Safety Assessment (GDSA) platform, or can otherwise be indirectly linked to the performance assessment by providing improved bounding conditions. In either the case, the expectation is that validated modelling tools will be developed that provide critical input to the safety case.
A six-segment management model is presented, each segment of which represents a major area in a new product development program. The first segment of the model covers integration of specialist engineers into 'systems requirement definition' or the system engineering documentation process. The second covers preparation of five basic types of 'development program plans.' The third segment covers integration of system requirements, scheduling, and funding of specialist engineering activities into 'work breakdown structures,' 'cost accounts,' and 'work packages.' The fourth covers 'requirement communication' by line organizations. The fifth covers 'performance measurement' based on work package data. The sixth covers 'baseline requirements achievement tracking.'
Designing engineering objects requires many engineers' knowledge from different domains. There needs to be cooperative work among engineering designers to complete a design. Revisions of a design are time consuming, especially if designers work at a distance and with different design description formats. In order to reduce the design cycle, there needs to be a sharable design describing the engineering community, which can be electronically transportable. Design is a process of integrating that is not easy to define definitively. This paper presents Design Script which is a generic engineering design knowledge representation scheme that can be applied in any engineering domain. The Design Script is developed through encapsulation of common design activities and basic design components based on problem decomposition. It is implemented using CLIPS with a Windows NT graphical user interface. The physical relationships between engineering objects and their subparts can be constructed in a hierarchical manner. The same design process is repeatedly applied at each given level of hierarchy and recursively into lower levels of the hierarchy. Each class of the structure can be represented using the Design Script.
A consistent engine system data base was generated for defining advantages and disadvantages, system performance and operating limits, engine parametric data, and technology requirements for candidate high pressure LO2/HC engine systems. Optimum LO2/HC engine power cycles were synthetized and representative conceptual engine design generated for a specified advanced surface to orbit transportation system.
The Human Research Program (HRP) Exploration Medical Capability (ExMC) Element has developed a Medical System Foundation for Level of Care IV, as defined by NASA’s space flight human-system standards, for long-duration lunar orbit and surface operation missions by employing a systems engineering approach using model-based systems engineering tools. This Foundation model includes a concept of operations; functional decomposition; clinical content (medical conditions, capabilities, and resources); associated functional, interface and non-functional technical requirements; and traces to the current versions of NASA standards documents and parent-level (Program- and Vehicle habitat system level) requirements. Collectively, these components constitute a foundation that serves as a starting point for a medical system that meets the Level of Care IV requirement. The Foundation was developed by a multidisciplinary team consisting of systems engineers, scientists, and clinicians across NASA, and information is presented in an easily accessible format that is understandable across disciplines. Stakeholders can use the Foundation to analyze the traces between medical capabilities, medical conditions, medical resources, and requirements and to identify medical system interfaces with other vehicle systems/subsystems. It can also be used as a basis for performing trades on risks vs. medical system mass and volume allocation. This discussion will focus on the processes through which the Medical System Foundation was developed, how the Foundation builds a bridge between the medical and engineering domains and facilitates communication between these communities, and how these processes can be applied more broadly to a crew health and performance system and other system domains. The presentation also discusses Foundation modifications based on the recently updated versions of the NASA 3001 Standards.
The basic requirements and guidelines for the preparation of System Safety Engineering Analysis are presented. The philosophy of System Safety and the various analytic methods available to the engineering profession are discussed. A text-book description of each of the methods is included.
A performance measurement system which provides both a means of monitoring performance and a resource to support management decision making is described. The process of performance indicator development is discussed and typical indicators are described. The paper concludes with a summary of some of the lessons learned in applying productivity measurements to engineering services tasks and in automating data collection, evaluation and interpretation.