Returning to the Moon: Building the Systems Engineering Base for Successful Science Missions

NASA Astrophysics Data System (ADS)

Eppler, D.; Young, K.; Bleacher, J.; Klaus, K.; Barker, D.; Evans, C.; Tewksbury, B.; Schmitt, H.; Hurtado, J.; Deans, M.; Yingst, A.; Spudis, P.; Bell, E.; Skinner, J.; Cohen, B.; Head, J.

2018-04-01

Enabling science return on future lunar missions will require coordination between the science community, design engineers, and mission operators. Our chapter is based on developing science-based systems engineering and operations requirements.

Computer-assisted engineering data base

NASA Technical Reports Server (NTRS)

Dube, R. P.; Johnson, H. R.

1983-01-01

General capabilities of data base management technology are described. Information requirements posed by the space station life cycle are discussed, and it is asserted that data base management technology supporting engineering/manufacturing in a heterogeneous hardware/data base management system environment should be applied to meeting these requirements. Today's commercial systems do not satisfy all of these requirements. The features of an R&D data base management system being developed to investigate data base management in the engineering/manufacturing environment are discussed. Features of this system represent only a partial solution to space station requirements. Areas where this system should be extended to meet full space station information management requirements are discussed.

Tailoring Systems Engineering Processes in a Conceptual Design Environment: A Case Study at NASA Marshall Spaceflight Center's ACO

NASA Technical Reports Server (NTRS)

Mulqueen, John; Maples, C. Dauphne; Fabisinski, Leo, III

2012-01-01

This paper provides an overview of Systems Engineering as it is applied in a conceptual design space systems department at the National Aeronautics and Space Administration (NASA) Marshall Spaceflight Center (MSFC) Advanced Concepts Office (ACO). Engineering work performed in the NASA MFSC's ACO is targeted toward the Exploratory Research and Concepts Development life cycle stages, as defined in the International Council on Systems Engineering (INCOSE) System Engineering Handbook. This paper addresses three ACO Systems Engineering tools that correspond to three INCOSE Technical Processes: Stakeholder Requirements Definition, Requirements Analysis, and Integration, as well as one Project Process Risk Management. These processes are used to facilitate, streamline, and manage systems engineering processes tailored for the earliest two life cycle stages, which is the environment in which ACO engineers work. The role of systems engineers and systems engineering as performed in ACO is explored in this paper. The need for tailoring Systems Engineering processes, tools, and products in the ever-changing engineering services ACO provides to its customers is addressed.

Integrating system safety into the basic systems engineering process

NASA Technical Reports Server (NTRS)

Griswold, J. W.

1971-01-01

The basic elements of a systems engineering process are given along with a detailed description of what the safety system requires from the systems engineering process. Also discussed is the safety that the system provides to other subfunctions of systems engineering.

Parametric Cost Analysis: A Design Function

NASA Technical Reports Server (NTRS)

Dean, Edwin B.

1989-01-01

Parametric cost analysis uses equations to map measurable system attributes into cost. The measures of the system attributes are called metrics. The equations are called cost estimating relationships (CER's), and are obtained by the analysis of cost and technical metric data of products analogous to those to be estimated. Examples of system metrics include mass, power, failure_rate, mean_time_to_repair, energy _consumed, payload_to_orbit, pointing_accuracy, manufacturing_complexity, number_of_fasteners, and percent_of_electronics_weight. The basic assumption is that a measurable relationship exists between system attributes and the cost of the system. If a function exists, the attributes are cost drivers. Candidates for metrics include system requirement metrics and engineering process metrics. Requirements are constraints on the engineering process. From optimization theory we know that any active constraint generates cost by not permitting full optimization of the objective. Thus, requirements are cost drivers. Engineering processes reflect a projection of the requirements onto the corporate culture, engineering technology, and system technology. Engineering processes are an indirect measure of the requirements and, hence, are cost drivers.

40 CFR 91.307 - Engine cooling system.

Code of Federal Regulations, 2014 CFR

2014-07-01

... 40 Protection of Environment 20 2014-07-01 2013-07-01 true Engine cooling system. 91.307 Section...) CONTROL OF EMISSIONS FROM MARINE SPARK-IGNITION ENGINES Emission Test Equipment Provisions § 91.307 Engine cooling system. An engine cooling system is required with sufficient capacity to maintain the engine at...

40 CFR 91.307 - Engine cooling system.

Code of Federal Regulations, 2013 CFR

2013-07-01

... 40 Protection of Environment 21 2013-07-01 2013-07-01 false Engine cooling system. 91.307 Section...) CONTROL OF EMISSIONS FROM MARINE SPARK-IGNITION ENGINES Emission Test Equipment Provisions § 91.307 Engine cooling system. An engine cooling system is required with sufficient capacity to maintain the engine at...

Requirements management: keeping your technology acquisition project under control.

PubMed

Carr, J J

2000-03-01

Whether you are acquiring clinical or business information systems, patient monitoring systems, or therapeutic and diagnostic systems, the odds are good that the project will be delivered late, will cost far more than predicted, and will not provide all the features promised. The principal reason for project failure is improper management of the requirements of the system. Requirements engineering and management is a skill from the systems engineering profession that can be learned by nearly any professional who is managing a technology acquisition project. The author discusses what requirements engineering and management is and how it is done.

46 CFR 46.15-5 - Engineering requirements.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 46 Shipping 2 2012-10-01 2012-10-01 false Engineering requirements. 46.15-5 Section 46.15-5... Lakes Voyages § 46.15-5 Engineering requirements. (a) Bilge and ballast systems, piping, inlets and... subchapter F (Marine Engineering) of this chapter. ...

46 CFR 46.15-5 - Engineering requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 2 2010-10-01 2010-10-01 false Engineering requirements. 46.15-5 Section 46.15-5... Lakes Voyages § 46.15-5 Engineering requirements. (a) Bilge and ballast systems, piping, inlets and... subchapter F (Marine Engineering) of this chapter. ...

46 CFR 46.15-5 - Engineering requirements.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 46 Shipping 2 2014-10-01 2014-10-01 false Engineering requirements. 46.15-5 Section 46.15-5... Lakes Voyages § 46.15-5 Engineering requirements. (a) Bilge and ballast systems, piping, inlets and... subchapter F (Marine Engineering) of this chapter. ...

46 CFR 46.15-5 - Engineering requirements.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 46 Shipping 2 2013-10-01 2013-10-01 false Engineering requirements. 46.15-5 Section 46.15-5... Lakes Voyages § 46.15-5 Engineering requirements. (a) Bilge and ballast systems, piping, inlets and... subchapter F (Marine Engineering) of this chapter. ...

46 CFR 46.15-5 - Engineering requirements.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 46 Shipping 2 2011-10-01 2011-10-01 false Engineering requirements. 46.15-5 Section 46.15-5... Lakes Voyages § 46.15-5 Engineering requirements. (a) Bilge and ballast systems, piping, inlets and... subchapter F (Marine Engineering) of this chapter. ...

Technology Challenges for Deep-Throttle Cryogenic Engines for Space Exploration

NASA Technical Reports Server (NTRS)

Brown, Kendall K.; Nelson, Karl W.

2005-01-01

Historically, cryogenic rocket engines have not been used for in-space applications due to their additional complexity, the mission need for high reliability, and the challenges of propellant boil-off. While the mission and vehicle architectures are not yet defined for the lunar and Martian robotic and human exploration objectives, cryogenic rocket engines offer the potential for higher performance and greater architecture/mission flexibility. In-situ cryogenic propellant production could enable a more robust exploration program by significantly reducing the propellant mass delivered to low earth orbit, thus warranting the evaluation of cryogenic rocket engines versus the hypergolic bi-propellant engines used in the Apollo program. A multi-use engine. one which can provide the functionality that separate engines provided in the Apollo mission architecture, is desirable for lunar and Mars exploration missions because it increases overall architecture effectiveness through commonality and modularity. The engine requirement derivation process must address each unique mission application and each unique phase within each mission. The resulting requirements, such as thrust level, performance, packaging, bum duration, number of operations; required impulses for each trajectory phase; operation after extended space or surface exposure; availability for inspection and maintenance; throttle range for planetary descent, ascent, acceleration limits and many more must be addressed. Within engine system studies, the system and component technology, capability, and risks must be evaluated and a balance between the appropriate amount of technology-push and technology-pull must be addressed. This paper will summarize many of the key technology challenges associated with using high-performance cryogenic liquid propellant rocket engine systems and components in the exploration program architectures. The paper is divided into two areas. The first area describes how the mission requirements affect the engine system requirements and create system level technology challenges. An engine system architecture for multiple applications or a family of engines based upon a set of core technologies, design, and fabrication approaches may reduce overall programmatic cost and risk. The engine system discussion will also address the characterization of engine cycle figures of merit, configurations, and design approaches for some in-space vehicle alternatives under consideration. The second area evaluates the component-level technology challenges induced from the system requirements. Component technology issues are discussed addressing injector, thrust chamber, ignition system, turbopump assembly, and valve design for the challenging requirements of high reliability, robustness, fault tolerance, deep throttling, reasonable performance (with respect to weight and specific impulse).

Technology Challenges for Deep-Throttle Cryogenic Engines for Space Exploration

NASA Astrophysics Data System (ADS)

Brown, Kendall K.; Nelson, Karl W.

2005-02-01

Historically, cryogenic rocket engines have not been used for in-space applications due to their additional complexity, the mission need for high reliability, and the challenges of propellant boil-off. While the mission and vehicle architectures are not yet defined for the lunar and Martian robotic and human exploration objectives, cryogenic rocket engines offer the potential for higher performance and greater architecture/mission flexibility. In-situ cryogenic propellant production could enable a more robust exploration program by significantly reducing the propellant mass delivered to low earth orbit, thus warranting the evaluation of cryogenic rocket engines versus the hypergolic bipropellant engines used in the Apollo program. A multi-use engine, one which can provide the functionality that separate engines provided in the Apollo mission architecture, is desirable for lunar and Mars exploration missions because it increases overall architecture effectiveness through commonality and modularity. The engine requirement derivation process must address each unique mission application and each unique phase within each mission. The resulting requirements, such as thrust level, performance, packaging, burn duration, number of operations; required impulses for each trajectory phase; operation after extended space or surface exposure; availability for inspection and maintenance; throttle range for planetary descent, ascent, acceleration limits and many more must be addressed. Within engine system studies, the system and component technology, capability, and risks must be evaluated and a balance between the appropriate amount of technology-push and technology-pull must be addressed. This paper will summarize many of the key technology challenges associated with using high-performance cryogenic liquid propellant rocket engine systems and components in the exploration program architectures. The paper is divided into two areas. The first area describes how the mission requirements affect the engine system requirements and create system level technology challenges. An engine system architecture for multiple applications or a family of engines based upon a set of core technologies, design, and fabrication approaches may reduce overall programmatic cost and risk. The engine system discussion will also address the characterization of engine cycle figures of merit, configurations, and design approaches for some in-space vehicle alternatives under consideration. The second area evaluates the component-level technology challenges induced from the system requirements. Component technology issues are discussed addressing injector, thrust chamber, ignition system, turbopump assembly, and valve design for the challenging requirements of high reliability, robustness, fault tolerance, deep throttling, reasonable performance (with respect to weight and specific impulse).

Applying Early Systems Engineering: Injecting Knowledge into the Capability Development Process

DTIC Science & Technology

2012-10-01

involves early use of systems engi- neering and technical analyses to supplement the existing operational analysis techniques currently used in...complexity, and costs of systems now being developed require tight coupling between operational requirements stated in the CDD, system requirements...Fleischer » Keywords: Capability Development, Competitive Prototyping, Knowledge Points, Early Systems Engineering Applying Early Systems

Mars Reconnaissance Orbiter Mission: Systems Engineering Challenges on the Mars Reconnaissance Orbiter Mission

NASA Technical Reports Server (NTRS)

Havens, Glen G.

2007-01-01

MRO project is a system of systems requiring system engineering team to architect, design, integrate, test, and operate these systems at each level of the project. The challenge of system engineering mission objectives into a single mission architecture that can be integrated tested, launched, and operated. Systems engineering must translate high-level requirements into integrated mission design. Systems engineering challenges were overcome utilizing a combination by creative designs built into MRO's flight and ground systems: a) Design of sophisticated spacecraft targeting and data management capabilities b) Establishment of a strong operations team organization; c) Implementation of robust operational processes; and d) Development of strategic ground tools. The MRO system has met the challenge of its driving requirements: a) MRO began its two-year primary science phase on November 7, 2006, and by July 2007, met it minimum requirement to collect 15 Tbits of data after only eight months of operations. Currently we have collected 22 Tbits. b) Based on current performance, mission data return could return 70 Tbits of data by the end of the primary science phase in 2008.

Integration of safety engineering into a cost optimized development program.

NASA Technical Reports Server (NTRS)

Ball, L. W.

1972-01-01

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.'

An Online Graduate Requirements Engineering Course

ERIC Educational Resources Information Center

Kilicay-Ergin, N.; Laplante, P. A.

2013-01-01

Requirements engineering is one of the fundamental knowledge areas in software and systems engineering graduate curricula. Recent changes in educational delivery and student demographics have created new challenges for requirements engineering education. In particular, there is an increasing demand for online education for working professionals.…

System Engineering of Autonomous Space Vehicles

NASA Technical Reports Server (NTRS)

Watson, Michael D.; Johnson, Stephen B.; Trevino, Luis

2014-01-01

Human exploration of the solar system requires fully autonomous systems when travelling more than 5 light minutes from Earth. This autonomy is necessary to manage a large, complex spacecraft with limited crew members and skills available. The communication latency requires the vehicle to deal with events with only limited crew interaction in most cases. The engineering of these systems requires an extensive knowledge of the spacecraft systems, information theory, and autonomous algorithm characteristics. The characteristics of the spacecraft systems must be matched with the autonomous algorithm characteristics to reliably monitor and control the system. This presents a large system engineering problem. Recent work on product-focused, elegant system engineering will be applied to this application, looking at the full autonomy stack, the matching of autonomous systems to spacecraft systems, and the integration of different types of algorithms. Each of these areas will be outlined and a general approach defined for system engineering to provide the optimal solution to the given application context.

NASA's Robotics Mining Competition Provides Undergraduates Full Life Cycle Systems Engineering Experience

NASA Technical Reports Server (NTRS)

Stecklein, Jonette

2017-01-01

NASA has held an annual robotic mining competition for teams of university/college students since 2010. This competition is yearlong, suitable for a senior university engineering capstone project. It encompasses the full project life cycle from ideation of a robot design to actual tele-operation of the robot in simulated Mars conditions mining and collecting simulated regolith. A major required element for this competition is a Systems Engineering Paper in which each team describes the systems engineering approaches used on their project. The score for the Systems Engineering Paper contributes 25% towards the team's score for the competition's grand prize. The required use of systems engineering on the project by this competition introduces the students to an intense practical application of systems engineering throughout a full project life cycle.

Helping System Engineers Bridge the Peaks

NASA Technical Reports Server (NTRS)

Rungta, Neha; Tkachuk, Oksana; Person, Suzette; Biatek, Jason; Whalen, Michael W.; Castle, Joseph; Castle, JosephGundy-Burlet, Karen

2014-01-01

In our experience at NASA, system engineers generally follow the Twin Peaks approach when developing safety-critical systems. However, iterations between the peaks require considerable manual, and in some cases duplicate, effort. A significant part of the manual effort stems from the fact that requirements are written in English natural language rather than a formal notation. In this work, we propose an approach that enables system engineers to leverage formal requirements and automated test generation to streamline iterations, effectively "bridging the peaks". The key to the approach is a formal language notation that a) system engineers are comfortable with, b) is supported by a family of automated V&V tools, and c) is semantically rich enough to describe the requirements of interest. We believe the combination of formalizing requirements and providing tool support to automate the iterations will lead to a more efficient Twin Peaks implementation at NASA.

SAGA: A project to automate the management of software production systems

NASA Technical Reports Server (NTRS)

Campbell, Roy H.; Beckman-Davies, C. S.; Benzinger, L.; Beshers, G.; Laliberte, D.; Render, H.; Sum, R.; Smith, W.; Terwilliger, R.

1986-01-01

Research into software development is required to reduce its production cost and to improve its quality. Modern software systems, such as the embedded software required for NASA's space station initiative, stretch current software engineering techniques. The requirements to build large, reliable, and maintainable software systems increases with time. Much theoretical and practical research is in progress to improve software engineering techniques. One such technique is to build a software system or environment which directly supports the software engineering process, i.e., the SAGA project, comprising the research necessary to design and build a software development which automates the software engineering process. Progress under SAGA is described.

Control system and method for a power delivery system having a continuously variable ratio transmission

DOEpatents

Frank, Andrew A.

1984-01-01

A control system and method for a power delivery system, such as in an automotive vehicle, having an engine coupled to a continuously variable ratio transmission (CVT). Totally independent control of engine and transmission enable the engine to precisely follow a desired operating characteristic, such as the ideal operating line for minimum fuel consumption. CVT ratio is controlled as a function of commanded power or torque and measured load, while engine fuel requirements (e.g., throttle position) are strictly a function of measured engine speed. Fuel requirements are therefore precisely adjusted in accordance with the ideal characteristic for any load placed on the engine.

NASA's Robotic Mining Competition Provides Undergraduates Full Life Cycle Systems Engineering Experience

NASA Technical Reports Server (NTRS)

Stecklein, Jonette

2017-01-01

NASA has held an annual robotic mining competition for teams of university/college students since 2010. This competition is yearlong, suitable for a senior university engineering capstone project. It encompasses the full project life cycle from ideation of a robot design, through tele-operation of the robot collecting regolith in simulated Mars conditions, to disposal of the robot systems after the competition. A major required element for this competition is a Systems Engineering Paper in which each team describes the systems engineering approaches used on their project. The score for the Systems Engineering Paper contributes 25% towards the team’s score for the competition’s grand prize. The required use of systems engineering on the project by this competition introduces the students to an intense practical application of systems engineering throughout a full project life cycle.

Enhancing requirements engineering for patient registry software systems with evidence-based components.

PubMed

Lindoerfer, Doris; Mansmann, Ulrich

2017-07-01

Patient registries are instrumental for medical research. Often their structures are complex and their implementations use composite software systems to meet the wide spectrum of challenges. Commercial and open-source systems are available for registry implementation, but many research groups develop their own systems. Methodological approaches in the selection of software as well as the construction of proprietary systems are needed. We propose an evidence-based checklist, summarizing essential items for patient registry software systems (CIPROS), to accelerate the requirements engineering process. Requirements engineering activities for software systems follow traditional software requirements elicitation methods, general software requirements specification (SRS) templates, and standards. We performed a multistep procedure to develop a specific evidence-based CIPROS checklist: (1) A systematic literature review to build a comprehensive collection of technical concepts, (2) a qualitative content analysis to define a catalogue of relevant criteria, and (3) a checklist to construct a minimal appraisal standard. CIPROS is based on 64 publications and covers twelve sections with a total of 72 items. CIPROS also defines software requirements. Comparing CIPROS with traditional software requirements elicitation methods, SRS templates and standards show a broad consensus but differences in issues regarding registry-specific aspects. Using an evidence-based approach to requirements engineering for registry software adds aspects to the traditional methods and accelerates the software engineering process for registry software. The method we used to construct CIPROS serves as a potential template for creating evidence-based checklists in other fields. The CIPROS list supports developers in assessing requirements for existing systems and formulating requirements for their own systems, while strengthening the reporting of patient registry software system descriptions. It may be a first step to create standards for patient registry software system assessments. Copyright © 2017 Elsevier Inc. All rights reserved.

40 CFR 90.307 - Engine cooling system.

Code of Federal Regulations, 2012 CFR

2012-07-01

... 40 Protection of Environment 21 2012-07-01 2012-07-01 false Engine cooling system. 90.307 Section...) CONTROL OF EMISSIONS FROM NONROAD SPARK-IGNITION ENGINES AT OR BELOW 19 KILOWATTS Emission Test Equipment Provisions § 90.307 Engine cooling system. An engine cooling system is required with sufficient capacity to...

40 CFR 90.307 - Engine cooling system.

Code of Federal Regulations, 2014 CFR

2014-07-01

... 40 Protection of Environment 20 2014-07-01 2013-07-01 true Engine cooling system. 90.307 Section...) CONTROL OF EMISSIONS FROM NONROAD SPARK-IGNITION ENGINES AT OR BELOW 19 KILOWATTS Emission Test Equipment Provisions § 90.307 Engine cooling system. An engine cooling system is required with sufficient capacity to...

40 CFR 89.329 - Engine cooling system.

Code of Federal Regulations, 2012 CFR

2012-07-01

... 40 Protection of Environment 21 2012-07-01 2012-07-01 false Engine cooling system. 89.329 Section...) CONTROL OF EMISSIONS FROM NEW AND IN-USE NONROAD COMPRESSION-IGNITION ENGINES Emission Test Equipment Provisions § 89.329 Engine cooling system. An engine cooling system is required with sufficient capacity to...

40 CFR 89.329 - Engine cooling system.

Code of Federal Regulations, 2013 CFR

2013-07-01

... 40 Protection of Environment 21 2013-07-01 2013-07-01 false Engine cooling system. 89.329 Section...) CONTROL OF EMISSIONS FROM NEW AND IN-USE NONROAD COMPRESSION-IGNITION ENGINES Emission Test Equipment Provisions § 89.329 Engine cooling system. An engine cooling system is required with sufficient capacity to...

40 CFR 89.329 - Engine cooling system.

Code of Federal Regulations, 2014 CFR

2014-07-01

... 40 Protection of Environment 20 2014-07-01 2013-07-01 true Engine cooling system. 89.329 Section...) CONTROL OF EMISSIONS FROM NEW AND IN-USE NONROAD COMPRESSION-IGNITION ENGINES Emission Test Equipment Provisions § 89.329 Engine cooling system. An engine cooling system is required with sufficient capacity to...

40 CFR 90.307 - Engine cooling system.

Code of Federal Regulations, 2013 CFR

2013-07-01

... 40 Protection of Environment 21 2013-07-01 2013-07-01 false Engine cooling system. 90.307 Section...) CONTROL OF EMISSIONS FROM NONROAD SPARK-IGNITION ENGINES AT OR BELOW 19 KILOWATTS Emission Test Equipment Provisions § 90.307 Engine cooling system. An engine cooling system is required with sufficient capacity to...

40 CFR 89.329 - Engine cooling system.

Code of Federal Regulations, 2011 CFR

2011-07-01

... 40 Protection of Environment 20 2011-07-01 2011-07-01 false Engine cooling system. 89.329 Section...) CONTROL OF EMISSIONS FROM NEW AND IN-USE NONROAD COMPRESSION-IGNITION ENGINES Emission Test Equipment Provisions § 89.329 Engine cooling system. An engine cooling system is required with sufficient capacity to...

Analysis of high load dampers

NASA Technical Reports Server (NTRS)

Bhat, S. T.; Buono, D. F.; Hibner, D. H.

1981-01-01

High load damping requirements for modern jet engines are discussed. The design of damping systems which could satisfy these requirements is also discusseed. In order to evaluate high load damping requirements, engines in three major classes were studied; large transport engines, small general aviation engines, and military engines. Four damper concepts applicable to these engines were evaluated; multi-ring, cartridge, curved beam, and viscous/friction. The most promising damper concept was selected for each engine and performance was assessed relative to conventional dampers and in light of projected damping requirements for advanced jet engines.

Cleared for Launch - Lessons Learned from the OSIRIS-REx System Requirements Verification Program

NASA Technical Reports Server (NTRS)

Stevens, Craig; Adams, Angela; Williams, Bradley; Goodloe, Colby

2017-01-01

Requirements verification of a large flight system is a challenge. It is especially challenging for engineers taking on their first role in space systems engineering. This paper describes our approach to verification of the Origins, Spectral Interpretation, Resource Identification, Security-Regolith Explorer (OSIRIS-REx) system requirements. It also captures lessons learned along the way from developing systems engineers embroiled in this process. We begin with an overview of the mission and science objectives as well as the project requirements verification program strategy. A description of the requirements flow down is presented including our implementation for managing the thousands of program and element level requirements and associated verification data. We discuss both successes and methods to improve the managing of this data across multiple organizational interfaces. Our approach to verifying system requirements at multiple levels of assembly is presented using examples from our work at instrument, spacecraft, and ground segment levels. We include a discussion of system end-to-end testing limitations and their impacts to the verification program. Finally, we describe lessons learned that are applicable to all emerging space systems engineers using our unique perspectives across multiple organizations of a large NASA program.

Towards Requirements in Systems Engineering for Aerospace IVHM Design

NASA Technical Reports Server (NTRS)

Saxena, Abhinav; Roychoudhury, Indranil; Lin, Wei; Goebel, Kai

2013-01-01

Health management (HM) technologies have been employed for safety critical system for decades, but a coherent systematic process to integrate HM into the system design is not yet clear. Consequently, in most cases, health management resorts to be an after-thought or 'band-aid' solution. Moreover, limited guidance exists for carrying out systems engineering (SE) on the subject of writing requirements for designs with integrated vehicle health management (IVHM). It is well accepted that requirements are key to developing a successful IVHM system right from the concept stage to development, verification, utilization, and support. However, writing requirements for systems with IVHM capability have unique challenges that require the designers to look beyond their own domains and consider the constraints and specifications of other interlinked systems. In this paper we look at various stages in the SE process and identify activities specific to IVHM design and development. More importantly, several relevant questions are posed that system engineers must address at various design and development stages. Addressing these questions should provide some guidance to systems engineers towards writing IVHM related requirements to ensure that appropriate IVHM functions are built into the system design.

737/CFM56-7 Aircraft Engine Systems

NASA Technical Reports Server (NTRS)

Wright, Steve; Shiosaki, Justin

2006-01-01

The configuration of the propulsion system engine externals must meet many airplane requirements such as cost, thrust, weight, range and systems power extraction. On the 737-700 several program requirements also played a major role in the development of the engine externals. These program goals were increased range, same cost as a 1994 737-300, 15% reduction in maintenance costs from the 737-300, and a propulsion package that appeared as if it was designed by one company. This presentation will show how these requirements shaped the design of the engine externals for the 737-700/CFM56-7B.

Investigation of the current requirements engineering practices among software developers at the Universiti Utara Malaysia Information Technology (UUMIT) centre

NASA Astrophysics Data System (ADS)

Hussain, Azham; Mkpojiogu, Emmanuel O. C.; Abdullah, Inam

2016-08-01

Requirements Engineering (RE) is a systemic and integrated process of eliciting, elaborating, negotiating, validating and managing of the requirements of a system in a software development project. UUM has been supported by various systems developed and maintained by the UUM Information Technology (UUMIT) Centre. The aim of this study was to assess the current requirements engineering practices at UUMIT. The main problem that prompted this research is the lack of studies that support software development activities at the UUMIT. The study is geared at helping UUMIT produce quality but time and cost saving software products by implementing cutting edge and state of the art requirements engineering practices. Also, the study contributes to UUM by identifying the activities needed for software development so that the management will be able to allocate budget to provide adequate and precise training for the software developers. Three variables were investigated: Requirement Description, Requirements Development (comprising: Requirements Elicitation, Requirements Analysis and Negotiation, Requirements Validation), and Requirement Management. The results from the study showed that the current practice of requirement engineering in UUMIT is encouraging, but still need further development and improvement because a few RE practices were seldom practiced.

Rocket Engine Health Management: Early Definition of Critical Flight Measurements

NASA Technical Reports Server (NTRS)

Christenson, Rick L.; Nelson, Michael A.; Butas, John P.

2003-01-01

The NASA led Space Launch Initiative (SLI) program has established key requirements related to safety, reliability, launch availability and operations cost to be met by the next generation of reusable launch vehicles. Key to meeting these requirements will be an integrated vehicle health management ( M) system that includes sensors, harnesses, software, memory, and processors. Such a system must be integrated across all the vehicle subsystems and meet component, subsystem, and system requirements relative to fault detection, fault isolation, and false alarm rate. The purpose of this activity is to evolve techniques for defining critical flight engine system measurements-early within the definition of an engine health management system (EHMS). Two approaches, performance-based and failure mode-based, are integrated to provide a proposed set of measurements to be collected. This integrated approach is applied to MSFC s MC-1 engine. Early identification of measurements supports early identification of candidate sensor systems whose design and impacts to the engine components must be considered in engine design.

46 CFR 189.55-5 - Plans and specifications required for new construction.

Code of Federal Regulations, 2011 CFR

2011-10-01

...) OCEANOGRAPHIC RESEARCH VESSELS INSPECTION AND CERTIFICATION Plan Approval § 189.55-5 Plans and specifications..., carbon dioxide, foam and sprinkling systems. (e) Marine engineering. For plans required for marine engineering equipment and systems. See Subchapter F (Marine Engineering) of this chapter. (f) Electrical...

46 CFR 189.55-5 - Plans and specifications required for new construction.

Code of Federal Regulations, 2010 CFR

2010-10-01

...) OCEANOGRAPHIC RESEARCH VESSELS INSPECTION AND CERTIFICATION Plan Approval § 189.55-5 Plans and specifications..., carbon dioxide, foam and sprinkling systems. (e) Marine engineering. For plans required for marine engineering equipment and systems. See Subchapter F (Marine Engineering) of this chapter. (f) Electrical...

Tracing And Control Of Engineering Requirements

NASA Technical Reports Server (NTRS)

Turner, Philip R.; Stoller, Richard L.; Neville, Ted; Boyle, Karen A.

1991-01-01

TRACER (Tracing and Control of Engineering Requirements) is data-base/word-processing software system created to document and maintain order of both requirements and descriptions associated with engineering project. Implemented on IBM PC under PC-DOS. Written with CLIPPER.

Systems engineering in the Large Synoptic Survey Telescope project: an application of model based systems engineering

NASA Astrophysics Data System (ADS)

Claver, C. F.; Selvy, Brian M.; Angeli, George; Delgado, Francisco; Dubois-Felsmann, Gregory; Hascall, Patrick; Lotz, Paul; Marshall, Stuart; Schumacher, German; Sebag, Jacques

2014-08-01

The Large Synoptic Survey Telescope project was an early adopter of SysML and Model Based Systems Engineering practices. The LSST project began using MBSE for requirements engineering beginning in 2006 shortly after the initial release of the first SysML standard. Out of this early work the LSST's MBSE effort has grown to include system requirements, operational use cases, physical system definition, interfaces, and system states along with behavior sequences and activities. In this paper we describe our approach and methodology for cross-linking these system elements over the three classical systems engineering domains - requirement, functional and physical - into the LSST System Architecture model. We also show how this model is used as the central element to the overall project systems engineering effort. More recently we have begun to use the cross-linked modeled system architecture to develop and plan the system verification and test process. In presenting this work we also describe "lessons learned" from several missteps the project has had with MBSE. Lastly, we conclude by summarizing the overall status of the LSST's System Architecture model and our plans for the future as the LSST heads toward construction.

The systems engineering overview and process (from the Systems Engineering Management Guide, 1990)

NASA Technical Reports Server (NTRS)

1993-01-01

The past several decades have seen the rise of large, highly interactive systems that are on the forward edge of technology. As a result of this growth and the increased usage of digital systems (computers and software), the concept of systems engineering has gained increasing attention. Some of this attention is no doubt due to large program failures which possibly could have been avoided, or at least mitigated, through the use of systems engineering principles. The complexity of modern day weapon systems requires conscious application of systems engineering concepts to ensure producible, operable and supportable systems that satisfy mission requirements. Although many authors have traced the roots of systems engineering to earlier dates, the initial formalization of the systems engineering process for military development began to surface in the mid-1950s on the ballistic missile programs. These early ballistic missile development programs marked the emergence of engineering discipline 'specialists' which has since continued to grow. Each of these specialties not only has a need to take data from the overall development process, but also to supply data, in the form of requirements and analysis results, to the process. A number of technical instructions, military standards and specifications, and manuals were developed as a result of these development programs. In particular, MILSTD-499 was issued in 1969 to assist both government and contractor personnel in defining the systems engineering effort in support of defense acquisition programs. This standard was updated to MIL-STD499A in 1974, and formed the foundation for current application of systems engineering principles to military development programs.

The systems engineering overview and process (from the Systems Engineering Management Guide, 1990)

NASA Astrophysics Data System (ADS)

The past several decades have seen the rise of large, highly interactive systems that are on the forward edge of technology. As a result of this growth and the increased usage of digital systems (computers and software), the concept of systems engineering has gained increasing attention. Some of this attention is no doubt due to large program failures which possibly could have been avoided, or at least mitigated, through the use of systems engineering principles. The complexity of modern day weapon systems requires conscious application of systems engineering concepts to ensure producible, operable and supportable systems that satisfy mission requirements. Although many authors have traced the roots of systems engineering to earlier dates, the initial formalization of the systems engineering process for military development began to surface in the mid-1950s on the ballistic missile programs. These early ballistic missile development programs marked the emergence of engineering discipline 'specialists' which has since continued to grow. Each of these specialties not only has a need to take data from the overall development process, but also to supply data, in the form of requirements and analysis results, to the process. A number of technical instructions, military standards and specifications, and manuals were developed as a result of these development programs. In particular, MILSTD-499 was issued in 1969 to assist both government and contractor personnel in defining the systems engineering effort in support of defense acquisition programs. This standard was updated to MIL-STD499A in 1974, and formed the foundation for current application of systems engineering principles to military development programs.

System Engineering of Photonic Systems for Space Application

NASA Technical Reports Server (NTRS)

Watson, Michael D.; Pryor, Jonathan E.

2014-01-01

The application of photonics in space systems requires tight integration with the spacecraft systems to ensure accurate operation. This requires some detailed and specific system engineering to properly incorporate the photonics into the spacecraft architecture and to guide the spacecraft architecture in supporting the photonics devices. Recent research in product focused, elegant system engineering has led to a system approach which provides a robust approach to this integration. Focusing on the mission application and the integration of the spacecraft system physics incorporation of the photonics can be efficiently and effectively accomplished. This requires a clear understanding of the driving physics properties of the photonics device to ensure proper integration with no unintended consequences. The driving physics considerations in terms of optical performance will be identified for their use in system integration. Keywords: System Engineering, Optical Transfer Function, Optical Physics, Photonics, Image Jitter, Launch Vehicle, System Integration, Organizational Interaction

Man-machine interface and control of the shuttle digital flight system

NASA Technical Reports Server (NTRS)

Burghduff, R. D.; Lewis, J. L., Jr.

1985-01-01

The space shuttle main engine (SSME) presented new requirements in the design of controls for large pump fed liquid rocket engine systems. These requirements were the need for built in full mission support capability, and complexity and flexibility of function not previously needed in this type of application. An engine mounted programmable digital control system was developed to meet these requirements. The engine system and controller and their function are described. Design challenges encountered during the course of development included accommodation for a very severe engine environment, the implementation of redundancy and redundancy management to provide fail operational/fail safe capability, removal of heat from the package, and significant constraints on computer memory size and processing time. The flexibility offered by programmable control reshaped the approach to engine design and development and set the pattern for future controls development in these types of applications.

NASA's Systems Engineering Approaches for Addressing Public Health Surveillance Requirements

NASA Technical Reports Server (NTRS)

Vann, Timi

2003-01-01

NASA's systems engineering has its heritage in space mission analysis and design, including the end-to-end approach to managing every facet of the extreme engineering required for successful space missions. NASA sensor technology, understanding of remote sensing, and knowledge of Earth system science, can be powerful new tools for improved disease surveillance and environmental public health tracking. NASA's systems engineering framework facilitates the match between facilitates the match between partner needs and decision support requirements in the areas of 1) Science/Data; 2) Technology; 3) Integration. Partnerships between NASA and other Federal agencies are diagrammed in this viewgraph presentation. NASA's role in these partnerships is to provide systemic and sustainable solutions that contribute to the measurable enhancement of a partner agency's disease surveillance efforts.

Control system and method for a power delivery system having a continuously variable ratio transmission

DOEpatents

Frank, A.A.

1984-07-10

A control system and method for a power delivery system, such as in an automotive vehicle, having an engine coupled to a continuously variable ratio transmission (CVT). Totally independent control of engine and transmission enable the engine to precisely follow a desired operating characteristic, such as the ideal operating line for minimum fuel consumption. CVT ratio is controlled as a function of commanded power or torque and measured load, while engine fuel requirements (e.g., throttle position) are strictly a function of measured engine speed. Fuel requirements are therefore precisely adjusted in accordance with the ideal characteristic for any load placed on the engine. 4 figs.

Directed evolution and synthetic biology applications to microbial systems.

PubMed

Bassalo, Marcelo C; Liu, Rongming; Gill, Ryan T

2016-06-01

Biotechnology applications require engineering complex multi-genic traits. The lack of knowledge on the genetic basis of complex phenotypes restricts our ability to rationally engineer them. However, complex phenotypes can be engineered at the systems level, utilizing directed evolution strategies that drive whole biological systems toward desired phenotypes without requiring prior knowledge of the genetic basis of the targeted trait. Recent developments in the synthetic biology field accelerates the directed evolution cycle, facilitating engineering of increasingly complex traits in biological systems. In this review, we summarize some of the most recent advances in directed evolution and synthetic biology that allows engineering of complex traits in microbial systems. Then, we discuss applications that can be achieved through engineering at the systems level. Copyright © 2016 Elsevier Ltd. All rights reserved.

A design study of a reaction control system for a V/STOL fighter/attack aircraft

NASA Technical Reports Server (NTRS)

Beard, B. B.; Foley, W. H.

1983-01-01

Attention is given to a short takeoff vertical landing (STOVL) aircraft reaction control system (RCS) design study. The STOVL fighter/attack aircraft employs an existing turbofan engine, and its hover requirement places a premium on weight reduction, which eliminates prospective nonairbreathing RCSs. A simple engine compressor bleed RCS degrades overall performance to an unacceptable degree, and the supersonic requirement precludes the large volume alternatives of thermal or ejector thrust augmentation systems as well as the ducting of engine exhaust gases and the use of a dedicated turbojet. The only system which addressed performance criteria without requiring major engine modifications was a dedicated load compressor driven by an auxilliary power unit.

From Science To Design: Systems Engineering For The Lsst

NASA Astrophysics Data System (ADS)

Claver, Chuck F.; Axelrod, T.; Fouts, K.; Kantor, J.; Nordby, M.; Sebag, J.; LSST Collaboration

2009-01-01

The LSST is a universal-purpose survey telescope that will address scores of scientific missions. To assist the technical teams to convergence to a specific engineering design, the LSST Science Requirements Document (SRD) selects four stressing principle scientific missions: 1) Constraining Dark Matter and Dark Energy; 2) taking an Inventory of the Solar System; 3) Exploring the Transient Optical Sky; and 4) mapping the Milky Way. From these 4 missions the SRD specifies the needed requirements for single images and the full 10 year survey that enables a wide range of science beyond the 4 principle missions. Through optical design and analysis, operations simulation, and throughput modeling the systems engineering effort in the LSST has largely focused on taking the SRD specifications and deriving system functional requirements that define the system design. A Model Based Systems Engineering approach with SysML is used to manage the flow down of requirements from science to system function to sub-system. The rigor of requirements flow and management assists the LSST in keeping the overall scope, hence budget and schedule, under control.

Requirement Assurance: A Verification Process

NASA Technical Reports Server (NTRS)

Alexander, Michael G.

2011-01-01

Requirement Assurance is an act of requirement verification which assures the stakeholder or customer that a product requirement has produced its "as realized product" and has been verified with conclusive evidence. Product requirement verification answers the question, "did the product meet the stated specification, performance, or design documentation?". In order to ensure the system was built correctly, the practicing system engineer must verify each product requirement using verification methods of inspection, analysis, demonstration, or test. The products of these methods are the "verification artifacts" or "closure artifacts" which are the objective evidence needed to prove the product requirements meet the verification success criteria. Institutional direction is given to the System Engineer in NPR 7123.1A NASA Systems Engineering Processes and Requirements with regards to the requirement verification process. In response, the verification methodology offered in this report meets both the institutional process and requirement verification best practices.

2.0 AEDL Systems Engineering

NASA Technical Reports Server (NTRS)

Graves, Claude

2005-01-01

Some engineering topics: Some Initial Thoughts. Capability Description. Capability State-of-the-Art. Capability Requirements. Systems Engineering. Capability Roadmap. Capability Maturity. Candidate Technologies. Metrics.

46 CFR 169.693 - Engine order telegraph systems.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 7 2010-10-01 2010-10-01 false Engine order telegraph systems. 169.693 Section 169.693... Machinery and Electrical Electrical Installations on Vessels of 100 Gross Tons and Over § 169.693 Engine order telegraph systems. An engine order telegraph system is not required. ...

46 CFR 169.693 - Engine order telegraph systems.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 46 Shipping 7 2013-10-01 2013-10-01 false Engine order telegraph systems. 169.693 Section 169.693... Machinery and Electrical Electrical Installations on Vessels of 100 Gross Tons and Over § 169.693 Engine order telegraph systems. An engine order telegraph system is not required. ...

46 CFR 169.693 - Engine order telegraph systems.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 46 Shipping 7 2012-10-01 2012-10-01 false Engine order telegraph systems. 169.693 Section 169.693... Machinery and Electrical Electrical Installations on Vessels of 100 Gross Tons and Over § 169.693 Engine order telegraph systems. An engine order telegraph system is not required. ...

46 CFR 169.693 - Engine order telegraph systems.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 46 Shipping 7 2011-10-01 2011-10-01 false Engine order telegraph systems. 169.693 Section 169.693... Machinery and Electrical Electrical Installations on Vessels of 100 Gross Tons and Over § 169.693 Engine order telegraph systems. An engine order telegraph system is not required. ...

46 CFR 169.693 - Engine order telegraph systems.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 46 Shipping 7 2014-10-01 2014-10-01 false Engine order telegraph systems. 169.693 Section 169.693... Machinery and Electrical Electrical Installations on Vessels of 100 Gross Tons and Over § 169.693 Engine order telegraph systems. An engine order telegraph system is not required. ...

76 FR 72087 - Special Conditions: Diamond Aircraft Industries, Model DA-40NG; Electronic Engine Control (EEC...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-11-22

... engine design certification, and the certification requirements for engine control systems are driven by... following novel or unusual design features: Electronic engine control system. Discussion As discussed above...; Electronic Engine Control (EEC) System AGENCY: Federal Aviation Administration (FAA), DOT. ACTION: Final...

Systems Engineering in NASA's R&TD Programs

NASA Technical Reports Server (NTRS)

Jones, Harry

2005-01-01

Systems engineering is largely the analysis and planning that support the design, development, and operation of systems. The most common application of systems engineering is in guiding systems development projects that use a phased process of requirements, specifications, design, and development. This paper investigates how systems engineering techniques should be applied in research and technology development programs for advanced space systems. These programs should include anticipatory engineering of future space flight systems and a project portfolio selection process, as well as systems engineering for multiple development projects.

Capturing Requirements for Autonomous Spacecraft with Autonomy Requirements Engineering

NASA Astrophysics Data System (ADS)

Vassev, Emil; Hinchey, Mike

2014-08-01

The Autonomy Requirements Engineering (ARE) approach has been developed by Lero - the Irish Software Engineering Research Center within the mandate of a joint project with ESA, the European Space Agency. The approach is intended to help engineers develop missions for unmanned exploration, often with limited or no human control. Such robotics space missions rely on the most recent advances in automation and robotic technologies where autonomy and autonomic computing principles drive the design and implementation of unmanned spacecraft [1]. To tackle the integration and promotion of autonomy in software-intensive systems, ARE combines generic autonomy requirements (GAR) with goal-oriented requirements engineering (GORE). Using this approach, software engineers can determine what autonomic features to develop for a particular system (e.g., a space mission) as well as what artifacts that process might generate (e.g., goals models, requirements specification, etc.). The inputs required by this approach are the mission goals and the domain-specific GAR reflecting specifics of the mission class (e.g., interplanetary missions).

Formal Verification of Complex Systems based on SysML Functional Requirements

DTIC Science & Technology

2014-12-23

Formal Verification of Complex Systems based on SysML Functional Requirements Hoda Mehrpouyan1, Irem Y. Tumer2, Chris Hoyle2, Dimitra Giannakopoulou3...requirements for design of complex engineered systems. The proposed ap- proach combines a SysML modeling approach to document and structure safety requirements...methods and tools to support the integration of safety into the design solution. 2.1. SysML for Complex Engineered Systems Traditional methods and tools

Orbit Transfer Vehicle (OTV) engine phase A study

NASA Technical Reports Server (NTRS)

Mellish, J. A.

1978-01-01

Requirements for the orbit transfer vehicle engine were examined. Engine performance/weight sensitivities, the effect of a service life of 300 start/shutdown cycles between overalls on the maximum engine operating pressure, and the sensitivity of the engine design point (i.e., thrust chamber pressure and nozzle area ratio) to the performance requirements specified are among the factors studied. Preliminary engine systems analyses were conducted on the stage combustion, expander, and gas generator engine cycles. Hydrogen and oxygen pump discharge pressure requirements are shown for various engine cycles. Performance of the engine cycles is compared.

Developing Data System Engineers

NASA Astrophysics Data System (ADS)

Behnke, J.; Byrnes, J. B.; Kobler, B.

2011-12-01

In the early days of general computer systems for science data processing, staff members working on NASA's data systems would most often be hired as mathematicians. Computer engineering was very often filled by those with electrical engineering degrees. Today, the Goddard Space Flight Center has special position descriptions for data scientists or as they are more commonly called: data systems engineers. These staff members are required to have very diverse skills, hence the need for a generalized position description. There is always a need for data systems engineers to develop, maintain and operate the complex data systems for Earth and space science missions. Today's data systems engineers however are not just mathematicians, they are computer programmers, GIS experts, software engineers, visualization experts, etc... They represent many different degree fields. To put together distributed systems like the NASA Earth Observing Data and Information System (EOSDIS), staff are required from many different fields. Sometimes, the skilled professional is not available and must be developed in-house. This paper will address the various skills and jobs for data systems engineers at NASA. Further it explores how to develop staff to become data scientists.

30 CFR 36.25 - Engine exhaust system.

Code of Federal Regulations, 2014 CFR

2014-07-01

... 30 Mineral Resources 1 2014-07-01 2014-07-01 false Engine exhaust system. 36.25 Section 36.25... EQUIPMENT Construction and Design Requirements § 36.25 Engine exhaust system. (a) Construction. The exhaust system of the engine shall be designed to withstand an internal pressure equal to 4 times the maximum...

The development of a post-test diagnostic system for rocket engines

NASA Technical Reports Server (NTRS)

Zakrajsek, June F.

1991-01-01

An effort was undertaken by NASA to develop an automated post-test, post-flight diagnostic system for rocket engines. The automated system is designed to be generic and to automate the rocket engine data review process. A modular, distributed architecture with a generic software core was chosen to meet the design requirements. The diagnostic system is initially being applied to the Space Shuttle Main Engine data review process. The system modules currently under development are the session/message manager, and portions of the applications section, the component analysis section, and the intelligent knowledge server. An overview is presented of a rocket engine data review process, the design requirements and guidelines, the architecture and modules, and the projected benefits of the automated diagnostic system.

System verification and validation: a fundamental systems engineering task

NASA Astrophysics Data System (ADS)

Ansorge, Wolfgang R.

2004-09-01

Systems Engineering (SE) is the discipline in a project management team, which transfers the user's operational needs and justifications for an Extremely Large Telescope (ELT) -or any other telescope-- into a set of validated required system performance characteristics. Subsequently transferring these validated required system performance characteris-tics into a validated system configuration, and eventually into the assembled, integrated telescope system with verified performance characteristics and provided it with "objective evidence that the particular requirements for the specified intended use are fulfilled". The latter is the ISO Standard 8402 definition for "Validation". This presentation describes the verification and validation processes of an ELT Project and outlines the key role System Engineering plays in these processes throughout all project phases. If these processes are implemented correctly into the project execution and are started at the proper time, namely at the very beginning of the project, and if all capabilities of experienced system engineers are used, the project costs and the life-cycle costs of the telescope system can be reduced between 25 and 50 %. The intention of this article is, to motivate and encourage project managers of astronomical telescopes and scientific instruments to involve the entire spectrum of Systems Engineering capabilities performed by trained and experienced SYSTEM engineers for the benefit of the project by explaining them the importance of Systems Engineering in the AIV and validation processes.

Increasing the reliability of labor of railroad engineers

NASA Technical Reports Server (NTRS)

Genes, V. S.; Madiyevskiy, Y. M.

1975-01-01

It has been shown that the group of problems related to temporary overloads still require serious development with respect to further automating the basic control operation - programmed selection of speed and braking. The problem of systems for warning the engineer about the condition of the unseen track segments remains a very serious one. Systems of hygenic support of the engineer also require constructive development. The problems of ensuring the reliability of work of engineers in periods of low information load, requiring motor acts, can basically be considered theoretically solved.

Requirements for guidelines systems: implementation challenges and lessons from existing software-engineering efforts.

PubMed

Shah, Hemant; Allard, Raymond D; Enberg, Robert; Krishnan, Ganesh; Williams, Patricia; Nadkarni, Prakash M

2012-03-09

A large body of work in the clinical guidelines field has identified requirements for guideline systems, but there are formidable challenges in translating such requirements into production-quality systems that can be used in routine patient care. Detailed analysis of requirements from an implementation perspective can be useful in helping define sub-requirements to the point where they are implementable. Further, additional requirements emerge as a result of such analysis. During such an analysis, study of examples of existing, software-engineering efforts in non-biomedical fields can provide useful signposts to the implementer of a clinical guideline system. In addition to requirements described by guideline-system authors, comparative reviews of such systems, and publications discussing information needs for guideline systems and clinical decision support systems in general, we have incorporated additional requirements related to production-system robustness and functionality from publications in the business workflow domain, in addition to drawing on our own experience in the development of the Proteus guideline system (http://proteme.org). The sub-requirements are discussed by conveniently grouping them into the categories used by the review of Isern and Moreno 2008. We cite previous work under each category and then provide sub-requirements under each category, and provide example of similar work in software-engineering efforts that have addressed a similar problem in a non-biomedical context. When analyzing requirements from the implementation viewpoint, knowledge of successes and failures in related software-engineering efforts can guide implementers in the choice of effective design and development strategies.

Requirements for guidelines systems: implementation challenges and lessons from existing software-engineering efforts

PubMed Central

2012-01-01

Background A large body of work in the clinical guidelines field has identified requirements for guideline systems, but there are formidable challenges in translating such requirements into production-quality systems that can be used in routine patient care. Detailed analysis of requirements from an implementation perspective can be useful in helping define sub-requirements to the point where they are implementable. Further, additional requirements emerge as a result of such analysis. During such an analysis, study of examples of existing, software-engineering efforts in non-biomedical fields can provide useful signposts to the implementer of a clinical guideline system. Methods In addition to requirements described by guideline-system authors, comparative reviews of such systems, and publications discussing information needs for guideline systems and clinical decision support systems in general, we have incorporated additional requirements related to production-system robustness and functionality from publications in the business workflow domain, in addition to drawing on our own experience in the development of the Proteus guideline system (http://proteme.org). Results The sub-requirements are discussed by conveniently grouping them into the categories used by the review of Isern and Moreno 2008. We cite previous work under each category and then provide sub-requirements under each category, and provide example of similar work in software-engineering efforts that have addressed a similar problem in a non-biomedical context. Conclusions When analyzing requirements from the implementation viewpoint, knowledge of successes and failures in related software-engineering efforts can guide implementers in the choice of effective design and development strategies. PMID:22405400

Fusing Quantitative Requirements Analysis with Model-based Systems Engineering

NASA Technical Reports Server (NTRS)

Cornford, Steven L.; Feather, Martin S.; Heron, Vance A.; Jenkins, J. Steven

2006-01-01

A vision is presented for fusing quantitative requirements analysis with model-based systems engineering. This vision draws upon and combines emergent themes in the engineering milieu. "Requirements engineering" provides means to explicitly represent requirements (both functional and non-functional) as constraints and preferences on acceptable solutions, and emphasizes early-lifecycle review, analysis and verification of design and development plans. "Design by shopping" emphasizes revealing the space of options available from which to choose (without presuming that all selection criteria have previously been elicited), and provides means to make understandable the range of choices and their ramifications. "Model-based engineering" emphasizes the goal of utilizing a formal representation of all aspects of system design, from development through operations, and provides powerful tool suites that support the practical application of these principles. A first step prototype towards this vision is described, embodying the key capabilities. Illustrations, implications, further challenges and opportunities are outlined.

Aerojet advanced engine concept

NASA Technical Reports Server (NTRS)

Schoenman, L.

1984-01-01

The future orbit transfer vehicle (OTV) requirements which dictate the need for a highly versatile, highly reliable, reusable propulsion module are discussed. To attain maximum operational economy, space-basing is essential. This requires a reusable, maintenance free engine. The design features of this space based engine are defined. A new engine cycle and its advantages allow all the maintenance goals to be attained. Rubbing contact and interpropellant seals and purges are eliminated when GO2 is used to drive the LO2 pump. The TPA design has only one moving part. The use of both GH2 and GO2 to drive the turbines lowers the turbine temperatures in addition lower GH2 temperatures and pressures improve chamber cooling and longer life. The use of GO2 as a turbine drive fluid is addressed. Space based engines require an integrated control and health monitoring system to improve system reliability and eliminate all scheduled maintenance. It is concluded that all OTV propulsion requirements can be fulfilled with a single engine. The technological developments required to demonstrate that engine are outlined.

Evaluation of advanced propulsion options for the next manned transportation system: Propulsion evolution study

NASA Technical Reports Server (NTRS)

Spears, L. T.; Kramer, R. D.

1990-01-01

The objectives were to examine launch vehicle applications and propulsion requirements for potential future manned space transportation systems and to support planning toward the evolution of Space Shuttle Main Engine (SSME) and Space Transportation Main Engine (STME) engines beyond their current or initial launch vehicle applications. As a basis for examinations of potential future manned launch vehicle applications, we used three classes of manned space transportation concepts currently under study: Space Transportation System Evolution, Personal Launch System (PLS), and Advanced Manned Launch System (AMLS). Tasks included studies of launch vehicle applications and requirements for hydrogen-oxygen rocket engines; the development of suggestions for STME engine evolution beyond the mid-1990's; the development of suggestions for STME evolution beyond the Advanced Launch System (ALS) application; the study of booster propulsion options, including LOX-Hydrocarbon options; the analysis of the prospects and requirements for utilization of a single engine configuration over the full range of vehicle applications, including manned vehicles plus ALS and Shuttle C; and a brief review of on-going and planned LOX-Hydrogen propulsion technology activities.

Closing the gap in systems engineering education for the space industry

NASA Technical Reports Server (NTRS)

Carlisle, R.

1986-01-01

The education of system engineers with emphasis on designing systems for space applications is discussed. System engineers determine the functional requirements, performance needs, and implementation procedures for proposed systems and their education is based on aeronautics and mathematics. Recommendations from industry for improving the curriculum of system engineers at the undergraduate and graduate levels are provided. The assistance provided by companies to the education of system engineers is examined.

An airline study of advanced technology requirements for advanced high speed commercial transport engines. 2: Engine preliminary design assessment

NASA Technical Reports Server (NTRS)

Sallee, G. P.

1973-01-01

The advanced technology requirements for an advanced high speed commercial transport engine are presented. The results of the phase 2 study effort cover the following areas: (1) general review of preliminary engine designs suggested for a future aircraft, (2) presentation of a long range view of airline propulsion system objectives and the research programs in noise, pollution, and design which must be undertaken to achieve the goals presented, (3) review of the impact of propulsion system unreliability and unscheduled maintenance on cost of operation, (4) discussion of the reliability and maintainability requirements and guarantees for future engines.

Non-Toxic Orbital Maneuvering System Engine Development

NASA Technical Reports Server (NTRS)

Green, Christopher; Claflin, Scott; Maeding, Chris; Butas, John

1999-01-01

Recent results using the Aestus engine operated with LOx/ethanol propellant are presented. An experimental program at Rocketdyne Propulsion and Power is underway to adapt this engine for the Boeing Reusable Space Systems Division non-toxic Orbital Maneuvering System/Reaction control System (OMS/RCS) system. Daimler-Chrysler Aerospace designed the Aestus as an nitrogen tetroxide/monomethyl hydrazine (NTO/MMH) upper-stage engine for the Ariane 5. The non-toxic OMS/RCS system's preliminary design requires a LOx/ethanol (O2/C2H5OH) engine that operates with a mixture ratio of 1.8, a specific impulse of 323 seconds, and fits within the original OMS design envelope. This paper describes current efforts to meet these requirements including, investigating engine performance using LOx/ethanol, developing the en-ine system sizing package, and meeting the vehicle operation parameters. Data from hot-fire testing are also presented and discussed.

48 CFR 2936.209 - Construction contracts with architect-engineer firms.

Code of Federal Regulations, 2013 CFR

2013-10-01

... architect-engineer firms. 2936.209 Section 2936.209 Federal Acquisition Regulations System DEPARTMENT OF LABOR GENERAL CONTRACTING REQUIREMENTS CONSTRUCTION AND ARCHITECT-ENGINEER CONTRACTS Special Aspects of Contracting for Construction 2936.209 Construction contracts with architect-engineer firms. As required by FAR...

ISO 9000 and/or Systems Engineering Capability Maturity Model?

NASA Technical Reports Server (NTRS)

Gholston, Sampson E.

2002-01-01

For businesses and organizations to remain competitive today they must have processes and systems in place that will allow them to first identify customer needs and then develop products/processes that will meet or exceed the customers needs and expectations. Customer needs, once identified, are normally stated as requirements. Designers can then develop products/processes that will meet these requirements. Several functions, such as quality management and systems engineering management are used to assist product development teams in the development process. Both functions exist in all organizations and both have a similar objective, which is to ensure that developed processes will meet customer requirements. Are efforts in these organizations being duplicated? Are both functions needed by organizations? What are the similarities and differences between the functions listed above? ISO 9000 is an international standard of goods and services. It sets broad requirements for the assurance of quality and for management's involvement. It requires organizations to document the processes and to follow these documented processes. ISO 9000 gives customers assurance that the suppliers have control of the process for product development. Systems engineering can broadly be defined as a discipline that seeks to ensure that all requirements for a system are satisfied throughout the life of the system by preserving their interrelationship. The key activities of systems engineering include requirements analysis, functional analysis/allocation, design synthesis and verification, and system analysis and control. The systems engineering process, when followed properly, will lead to higher quality products, lower cost products, and shorter development cycles. The System Engineering Capability Maturity Model (SE-CMM) will allow companies to measure their system engineering capability and continuously improve those capabilities. ISO 9000 and SE-CMM seem to have a similar objective, which is to document the organization's processes and certify to potential customers the capability of a supplier to control the processes that determine the quality of the product or services being produced. The remaining sections of this report examine the differences and similarities between ISO 9000 and SE-CMM and make recommendations for implementation.

Clustered engine study

NASA Technical Reports Server (NTRS)

Shepard, Kyle; Sager, Paul; Kusunoki, Sid; Porter, John; Campion, AL; Mouritzan, Gunnar; Glunt, George; Vegter, George; Koontz, Rob

1993-01-01

Several topics are presented in viewgraph form which together encompass the preliminary assessment of nuclear thermal rocket engine clustering. The study objectives, schedule, flow, and groundrules are covered. This is followed by the NASA groundrules mission and our interpretation of the associated operational scenario. The NASA reference vehicle is illustrated, then the four propulsion system options are examined. Each propulsion system's preliminary design, fluid systems, operating characteristics, thrust structure, dimensions, and mass properties are detailed as well as the associated key propulsion system/vehicle interfaces. A brief series of systems analysis is also covered including: thrust vector control requirements, engine out possibilities, propulsion system failure modes, surviving system requirements, and technology requirements. An assessment of vehicle/propulsion system impacts due to the lessons learned are presented.

A segmented ion engine design for solar electric propulsion systems

NASA Technical Reports Server (NTRS)

Brophy, John R.

1992-01-01

A new ion engine design, called a segmented ion engine, is described which is capable of reducing the required ion source life time for small body rendezvous missions from 18,000 h to about 8,000 h. The use of SAND ion optics for the engine accelerator system makes it possible to substantially reduce the cost of demonstrating the required engine endurance. It is concluded that a flight test of a 5-kW xenon ion propulsion system on the ELITE spacecraft would enormously reduce the cost and risk of using ion propulsion on a planetary vehicle by addressing systems level issues associated with flying a spacecraft radically different from conventional planetary vehicles.

Improved Stirling engine performance using jet impingement

NASA Technical Reports Server (NTRS)

Johnson, D. C.; Britt, E. J.; Thieme, L. G.

1982-01-01

Of the many factors influencing the performance of a Stirling engine, that of transferring the combustion gas heat into the working fluid is crucial. By utilizing the high heat transfer rates obtainable with a jet impingement heat transfer system, it is possible to reduce the flame temperature required for engine operation. Also, the required amount of heater tube surface area may be reduced, resulting in a decrease in the engine nonswept volume and a related increase in engine efficiency. A jet impingement heat transfer system was designed by Rasor Associates, Inc., and tested in the GPU-3 Stirling engine at the NASA Lewis Research Center. For a small penalty in pumping power (less than 0.5% of engine output) the jet impingement heat transfer system provided a higher combustion-gas-side heat transfer coefficient and a smoothing of heater temperature profiles resulting in lower combustion system temperatures and a 5 to 8% increase in engine power output and efficiency.

Designing, Implementing and Maintaining a First Year Project Course in Electrical Engineering

ERIC Educational Resources Information Center

Lillieskold, J.; Ostlund, S.

2008-01-01

Being a modern electrical engineer does not only require state of the art skills in areas such as transfer and processing of information, electronics, systems engineering, and biomedical electrical engineering; it also requires generic engineering skills such as oral and written communication, team building, interpersonal skills, and the ability…

A Software Tool for Integrated Optical Design Analysis

NASA Technical Reports Server (NTRS)

Moore, Jim; Troy, Ed; DePlachett, Charles; Montgomery, Edward (Technical Monitor)

2001-01-01

Design of large precision optical systems requires multi-disciplinary analysis, modeling, and design. Thermal, structural and optical characteristics of the hardware must be accurately understood in order to design a system capable of accomplishing the performance requirements. The interactions between each of the disciplines become stronger as systems are designed lighter weight for space applications. This coupling dictates a concurrent engineering design approach. In the past, integrated modeling tools have been developed that attempt to integrate all of the complex analysis within the framework of a single model. This often results in modeling simplifications and it requires engineering specialist to learn new applications. The software described in this presentation addresses the concurrent engineering task using a different approach. The software tool, Integrated Optical Design Analysis (IODA), uses data fusion technology to enable a cross discipline team of engineering experts to concurrently design an optical system using their standard validated engineering design tools.

Controls, health assessment, and conditional monitoring for large, reusable, liquid rocket engines

NASA Technical Reports Server (NTRS)

Cikanek, H. A., III

1986-01-01

Past and future progress in the performance of control systems for large, liquid rocket engines typified such as current state-of-the-art, the Shuttle Main Engine (SSME), is discussed. Details of the first decade of efforts, which culminates in the F-1 and J-2 Saturn engines control systems, are traced, noting problem modes and improvements which were implemented to realize the SSME. Future control system designs, to accommodate the requirements of operation of engines for a heavy lift launch vehicle, an orbital transfer vehicle and the aerospace plane, are summarized. Generic design upgrades needed include an expanded range of fault detection, maintenance as-needed instead of as-scheduled, reduced human involvement in engine operations, and increased control of internal engine states. Current NASA technology development programs aimed at meeting the future control system requirements are described.

DOE Office of Scientific and Technical Information (OSTI.GOV)

Not Available

The Office of Civilian Radioactive Waste Management Systems Engineering Management Plan (OCRWM SEMP) specifies the technical management approach for the development of the waste management system, and specifies the approach for the development of each of the system elements -- the waste acceptance system, the transportation system, the Monitored Retrievable Storage (MRS) facility, and the mined geologic disposal system, which includes site characterization activity. The SEMP also delineates how systems engineering will be used by OCRWM to describe the system development process; it identifies responsibilities for its implementation, and specifies the minimum requirements for systems engineering. It also identifies themore » close interrelationship of system engineering and licensing processes. This SEMP, which is a combined OCRWM and M&O SEMP, is part of the top-level program documentation and is prepared in accordance with the direction provided in the Program Management System Manual (PMSM). The relationship of this document to other top level documents in the CRWMS document hierarchy is defined in the PMSM. A systems engineering management plan for each project, which specifies the actions to be taken in implementing systems engineering at the project level, shall be prepared by the respective project managers. [``Program`` refers to the CRWMS-wide activity and ``project`` refers to that level responsible for accomplishing the specific activities of that segment of the program.] The requirements for the project level SEMPs are addressed in Section 4.2.2.2. They represent the minimum set of requirements, and do not preclude the broadening of systems engineering activities to meet the specific needs of each project.« less

46 CFR 27.205 - What are the requirements for internal communication systems on towing vessels?

Code of Federal Regulations, 2010 CFR

2010-10-01

... systems on towing vessels? 27.205 Section 27.205 Shipping COAST GUARD, DEPARTMENT OF HOMELAND SECURITY... fitted with a communication system between the engine room and the operating station that— (1) Consists... required to have internal communication systems. (c) When the operating-station's engine controls and the...

Quiet Clean Short-haul Experimental Engine (QCSEE) preliminary under the wing flight propulsion system analysis report

NASA Technical Reports Server (NTRS)

Howard, D. F.

1976-01-01

The preliminary design and installation of high bypass, geared turbofan engine with a composite nacelle forming the propulsion system for a short haul passenger aircraft are described. The technology required for externally blown flap aircraft with under the wing (UTW) propulsion system installations for introduction into passenger service in the mid 1980's is included. The design, fabrication, and testing of this UTW experimental engine containing the required technology items for low noise, fuel economy, with composite structure for reduced weight and digital engine control are provided.

Software Safety Risk in Legacy Safety-Critical Computer Systems

NASA Technical Reports Server (NTRS)

Hill, Janice; Baggs, Rhoda

2007-01-01

Safety-critical computer systems must be engineered to meet system and software safety requirements. For legacy safety-critical computer systems, software safety requirements may not have been formally specified during development. When process-oriented software safety requirements are levied on a legacy system after the fact, where software development artifacts don't exist or are incomplete, the question becomes 'how can this be done?' The risks associated with only meeting certain software safety requirements in a legacy safety-critical computer system must be addressed should such systems be selected as candidates for reuse. This paper proposes a method for ascertaining formally, a software safety risk assessment, that provides measurements for software safety for legacy systems which may or may not have a suite of software engineering documentation that is now normally required. It relies upon the NASA Software Safety Standard, risk assessment methods based upon the Taxonomy-Based Questionnaire, and the application of reverse engineering CASE tools to produce original design documents for legacy systems.

Education of biomedical engineering in Taiwan.

PubMed

Lin, Kang-Ping; Kao, Tsair; Wang, Jia-Jung; Chen, Mei-Jung; Su, Fong-Chin

2014-01-01

Biomedical Engineers (BME) play an important role in medical and healthcare society. Well educational programs are important to support the healthcare systems including hospitals, long term care organizations, manufacture industries of medical devices/instrumentations/systems, and sales/services companies of medical devices/instrumentations/system. In past 30 more years, biomedical engineering society has accumulated thousands people hold a biomedical engineering degree, and work as a biomedical engineer in Taiwan. Most of BME students can be trained in biomedical engineering departments with at least one of specialties in bioelectronics, bio-information, biomaterials or biomechanics. Students are required to have internship trainings in related institutions out of campus for 320 hours before graduating. Almost all the biomedical engineering departments are certified by IEET (Institute of Engineering Education Taiwan), and met the IEET requirement in which required mathematics and fundamental engineering courses. For BMEs after graduation, Taiwanese Society of Biomedical Engineering (TSBME) provides many continue-learning programs and certificates for all members who expect to hold the certification as a professional credit in his working place. In current status, many engineering departments in university are continuously asked to provide joint programs with BME department to train much better quality students. BME is one of growing fields in Taiwan.

30 CFR 36.23 - Engine intake system.

Code of Federal Regulations, 2014 CFR

2014-07-01

... 30 Mineral Resources 1 2014-07-01 2014-07-01 false Engine intake system. 36.23 Section 36.23... EQUIPMENT Construction and Design Requirements § 36.23 Engine intake system. (a) Construction. The intake... operator's compartment, to shut off the air supply to the engine. This valve shall be constructed to permit...

30 CFR 36.23 - Engine intake system.

Code of Federal Regulations, 2012 CFR

2012-07-01

... 30 Mineral Resources 1 2012-07-01 2012-07-01 false Engine intake system. 36.23 Section 36.23... EQUIPMENT Construction and Design Requirements § 36.23 Engine intake system. (a) Construction. The intake... operator's compartment, to shut off the air supply to the engine. This valve shall be constructed to permit...

A systems engineering management approach to resource management applications

NASA Technical Reports Server (NTRS)

Hornstein, Rhoda Shaller

1989-01-01

The author presents a program management response to the following question: How can the traditional practice of systems engineering management, including requirements specification, be adapted, enhanced, or modified to build future planning and scheduling systems for effective operations? The systems engineering management process, as traditionally practiced, is examined. Extensible resource management systems are discussed. It is concluded that extensible systems are a partial solution to problems presented by requirements that are incomplete, partially immeasurable, and often dynamic. There are positive indications that resource management systems have been characterized and modeled sufficiently to allow their implementation as extensible systems.

What is the Final Verification of Engineering Requirements?

NASA Technical Reports Server (NTRS)

Poole, Eric

2010-01-01

This slide presentation reviews the process of development through the final verification of engineering requirements. The definition of the requirements is driven by basic needs, and should be reviewed by both the supplier and the customer. All involved need to agree upon a formal requirements including changes to the original requirements document. After the requirements have ben developed, the engineering team begins to design the system. The final design is reviewed by other organizations. The final operational system must satisfy the original requirements, though many verifications should be performed during the process. The verification methods that are used are test, inspection, analysis and demonstration. The plan for verification should be created once the system requirements are documented. The plan should include assurances that every requirement is formally verified, that the methods and the responsible organizations are specified, and that the plan is reviewed by all parties. The options of having the engineering team involved in all phases of the development as opposed to having some other organization continue the process once the design has been complete is discussed.

Suppression of Thermal Emission from Exhaust Components Using an Integrated Approach

DTIC Science & Technology

2002-08-01

design model must, as a minimum, include an accurate estimate of space required for the exhaust , backpressure to the engine , system weight, gas species...hot flovw testing. The virtual design model provides an estimate of space required for: tih exhaust , backiressure to the engine ., svsie:. weigar. gas...either be the engine for the exhaust system or is capable of providing more than the required mass flow rate and enough gas temperature margins so that

Development of the Functional Flow Block Diagram for the J-2X Rocket Engine System

NASA Technical Reports Server (NTRS)

White, Thomas; Stoller, Sandra L.; Greene, WIlliam D.; Christenson, Rick L.; Bowen, Barry C.

2007-01-01

The J-2X program calls for the upgrade of the Apollo-era Rocketdyne J-2 engine to higher power levels, using new materials and manufacturing techniques, and with more restrictive safety and reliability requirements than prior human-rated engines in NASA history. Such requirements demand a comprehensive systems engineering effort to ensure success. Pratt & Whitney Rocketdyne system engineers performed a functional analysis of the engine to establish the functional architecture. J-2X functions were captured in six major operational blocks. Each block was divided into sub-blocks or states. In each sub-block, functions necessary to perform each state were determined. A functional engine schematic consistent with the fidelity of the system model was defined for this analysis. The blocks, sub-blocks, and functions were sequentially numbered to differentiate the states in which the function were performed and to indicate the sequence of events. The Engine System was functionally partitioned, to provide separate and unique functional operators. Establishing unique functional operators as work output of the System Architecture process is novel in Liquid Propulsion Engine design. Each functional operator was described such that its unique functionality was identified. The decomposed functions were then allocated to the functional operators both of which were the inputs to the subsystem or component performance specifications. PWR also used a novel approach to identify and map the engine functional requirements to customer-specified functions. The final result was a comprehensive Functional Flow Block Diagram (FFBD) for the J-2X Engine System, decomposed to the component level and mapped to all functional requirements. This FFBD greatly facilitates component specification development, providing a well-defined trade space for functional trades at the subsystem and component level. It also provides a framework for function-based failure modes and effects analysis (FMEA), and a rigorous baseline for the functional architecture.

Requirements Flowdown for Prognostics and Health Management

NASA Technical Reports Server (NTRS)

Goebel, Kai; Saxena, Abhinav; Roychoudhury, Indranil; Celaya, Jose R.; Saha, Bhaskar; Saha, Sankalita

2012-01-01

Prognostics and Health Management (PHM) principles have considerable promise to change the game of lifecycle cost of engineering systems at high safety levels by providing a reliable estimate of future system states. This estimate is a key for planning and decision making in an operational setting. While technology solutions have made considerable advances, the tie-in into the systems engineering process is lagging behind, which delays fielding of PHM-enabled systems. The derivation of specifications from high level requirements for algorithm performance to ensure quality predictions is not well developed. From an engineering perspective some key parameters driving the requirements for prognostics performance include: (1) maximum allowable Probability of Failure (PoF) of the prognostic system to bound the risk of losing an asset, (2) tolerable limits on proactive maintenance to minimize missed opportunity of asset usage, (3) lead time to specify the amount of advanced warning needed for actionable decisions, and (4) required confidence to specify when prognosis is sufficiently good to be used. This paper takes a systems engineering view towards the requirements specification process and presents a method for the flowdown process. A case study based on an electric Unmanned Aerial Vehicle (e-UAV) scenario demonstrates how top level requirements for performance, cost, and safety flow down to the health management level and specify quantitative requirements for prognostic algorithm performance.

Software Engineering Improvement Plan

NASA Technical Reports Server (NTRS)

2006-01-01

In performance of this task order, bd Systems personnel provided support to the Flight Software Branch and the Software Working Group through multiple tasks related to software engineering improvement and to activities of the independent Technical Authority (iTA) Discipline Technical Warrant Holder (DTWH) for software engineering. To ensure that the products, comments, and recommendations complied with customer requirements and the statement of work, bd Systems personnel maintained close coordination with the customer. These personnel performed work in areas such as update of agency requirements and directives database, software effort estimation, software problem reports, a web-based process asset library, miscellaneous documentation review, software system requirements, issue tracking software survey, systems engineering NPR, and project-related reviews. This report contains a summary of the work performed and the accomplishments in each of these areas.

SU-E-T-785: Using Systems Engineering to Design HDR Skin Treatment Operation for Small Lesions to Enhance Patient Safety

DOE Office of Scientific and Technical Information (OSTI.GOV)

Saw, C; Baikadi, M; Peters, C

2015-06-15

Purpose: Using systems engineering to design HDR skin treatment operation for small lesions using shielded applicators to enhance patient safety. Methods: Systems engineering is an interdisciplinary field that offers formal methodologies to study, design, implement, and manage complex engineering systems as a whole over their life-cycles. The methodologies deal with human work-processes, coordination of different team, optimization, and risk management. The V-model of systems engineering emphasize two streams, the specification and the testing streams. The specification stream consists of user requirements, functional requirements, and design specifications while the testing on installation, operational, and performance specifications. In implementing system engineering tomore » this project, the user and functional requirements are (a) HDR unit parameters be downloaded from the treatment planning system, (b) dwell times and positions be generated by treatment planning system, (c) source decay be computer calculated, (d) a double-check system of treatment parameters to comply with the NRC regulation. These requirements are intended to reduce human intervention to improve patient safety. Results: A formal investigation indicated that the user requirements can be satisfied. The treatment operation consists of using the treatment planning system to generate a pseudo plan that is adjusted for different shielded applicators to compute the dwell times. The dwell positions, channel numbers, and the dwell times are verified by the medical physicist and downloaded into the HDR unit. The decayed source strength is transferred to a spreadsheet that computes the dwell times based on the type of applicators and prescribed dose used. Prior to treatment, the source strength, dwell times, dwell positions, and channel numbers are double-checked by the radiation oncologist. No dosimetric parameters are manually calculated. Conclusion: Systems engineering provides methodologies to effectively design the HDR treatment operation that minimize human intervention and improve patient safety.« less

Framework for Architecture Trade Study Using MBSE and Performance Simulation

NASA Technical Reports Server (NTRS)

Ryan, Jessica; Sarkani, Shahram; Mazzuchim, Thomas

2012-01-01

Increasing complexity in modern systems as well as cost and schedule constraints require a new paradigm of system engineering to fulfill stakeholder needs. Challenges facing efficient trade studies include poor tool interoperability, lack of simulation coordination (design parameters) and requirements flowdown. A recent trend toward Model Based System Engineering (MBSE) includes flexible architecture definition, program documentation, requirements traceability and system engineering reuse. As a new domain MBSE still lacks governing standards and commonly accepted frameworks. This paper proposes a framework for efficient architecture definition using MBSE in conjunction with Domain Specific simulation to evaluate trade studies. A general framework is provided followed with a specific example including a method for designing a trade study, defining candidate architectures, planning simulations to fulfill requirements and finally a weighted decision analysis to optimize system objectives.

Advanced oxygen-hydrocarbon rocket engine study

NASA Technical Reports Server (NTRS)

Obrien, C. J.; Salkeld, R.

1980-01-01

The advantages and disadvantages, system performance and operating limits, engine parametric data, and technology requirements for candidate high pressure LO2/Hydrocarbon engine systems are summarized. These summaries of parametric analysis and design provide a consistent engine system data base. Power balance data were generated for the eleven engine cycles. Engine cycle rating parameters were established and the desired condition and the effect of the parameter on the engine and/or vehicle are described.

A system management methodology for building successful resource management systems

NASA Technical Reports Server (NTRS)

Hornstein, Rhoda Shaller; Willoughby, John K.

1989-01-01

This paper presents a system management methodology for building successful resource management systems that possess lifecycle effectiveness. This methodology is based on an analysis of the traditional practice of Systems Engineering Management as it applies to the development of resource management systems. The analysis produced fifteen significant findings presented as recommended adaptations to the traditional practice of Systems Engineering Management to accommodate system development when the requirements are incomplete, unquantifiable, ambiguous and dynamic. Ten recommended adaptations to achieve operational effectiveness when requirements are incomplete, unquantifiable or ambiguous are presented and discussed. Five recommended adaptations to achieve system extensibility when requirements are dynamic are also presented and discussed. The authors conclude that the recommended adaptations to the traditional practice of Systems Engineering Management should be implemented for future resource management systems and that the technology exists to build these systems extensibly.

46 CFR 77.05-1 - Installation and details.

Code of Federal Regulations, 2014 CFR

2014-10-01

... MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communication Systems § 77.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or interior... accordance with the requirements of subchapter J (Electrical Engineering) of this chapter. Systems of this...

46 CFR 77.05-1 - Installation and details.

Code of Federal Regulations, 2012 CFR

2012-10-01

... MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communication Systems § 77.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or interior... accordance with the requirements of subchapter J (Electrical Engineering) of this chapter. Systems of this...

46 CFR 77.05-1 - Installation and details.

Code of Federal Regulations, 2010 CFR

2010-10-01

... MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communication Systems § 77.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or interior... accordance with the requirements of subchapter J (Electrical Engineering) of this chapter. Systems of this...

46 CFR 77.05-1 - Installation and details.

Code of Federal Regulations, 2011 CFR

2011-10-01

... MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communication Systems § 77.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or interior... accordance with the requirements of subchapter J (Electrical Engineering) of this chapter. Systems of this...

46 CFR 77.05-1 - Installation and details.

Code of Federal Regulations, 2013 CFR

2013-10-01

... MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communication Systems § 77.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or interior... accordance with the requirements of subchapter J (Electrical Engineering) of this chapter. Systems of this...

7 CFR 1730.26 - Certification.

Code of Federal Regulations, 2010 CFR

2010-01-01

... ELECTRIC SYSTEM OPERATIONS AND MAINTENANCE Operations and Maintenance Requirements § 1730.26 Certification. (a) Engineer's certification. Where provided for in the borrower's loan documents, RUS may require the borrower to provide an “Engineer's Certification” as to the condition of the borrower's system...

7 CFR 1730.26 - Certification.

Code of Federal Regulations, 2011 CFR

2011-01-01

... ELECTRIC SYSTEM OPERATIONS AND MAINTENANCE Operations and Maintenance Requirements § 1730.26 Certification. (a) Engineer's certification. Where provided for in the borrower's loan documents, RUS may require the borrower to provide an “Engineer's Certification” as to the condition of the borrower's system...

7 CFR 1730.26 - Certification.

Code of Federal Regulations, 2012 CFR

2012-01-01

... ELECTRIC SYSTEM OPERATIONS AND MAINTENANCE Operations and Maintenance Requirements § 1730.26 Certification. (a) Engineer's certification. Where provided for in the borrower's loan documents, RUS may require the borrower to provide an “Engineer's Certification” as to the condition of the borrower's system...

7 CFR 1730.26 - Certification.

Code of Federal Regulations, 2014 CFR

2014-01-01

... ELECTRIC SYSTEM OPERATIONS AND MAINTENANCE Operations and Maintenance Requirements § 1730.26 Certification. (a) Engineer's certification. Where provided for in the borrower's loan documents, RUS may require the borrower to provide an “Engineer's Certification” as to the condition of the borrower's system...

7 CFR 1730.26 - Certification.

Code of Federal Regulations, 2013 CFR

2013-01-01

... ELECTRIC SYSTEM OPERATIONS AND MAINTENANCE Operations and Maintenance Requirements § 1730.26 Certification. (a) Engineer's certification. Where provided for in the borrower's loan documents, RUS may require the borrower to provide an “Engineer's Certification” as to the condition of the borrower's system...

Automotive Stirling Engine Mod 1 Design Review, volume 2

NASA Technical Reports Server (NTRS)

1982-01-01

The auxiliaries and the control system for the ASE MOD I: (1) provide the required fuel and air flows for a well controlled combustion process, generating heat to the Stirling cycle; (2) provide a driver acceptable method for controlling the power output of the engine; (3) provide adequate lubrication and cooling water circulation; (4) generate the electric energy required for engine and vehicle operation; (5) provide a driver acceptable method for starting, stopping and monitoring the engine; and (6) provide a guard system, that protects the engine at component or system malfunction. The control principles and the way the different components and sub-systems interact are described as well as the different auxiliaries, the air fuel system, the power control systems and the electronics. The arrangement and location of auxiliaries and other major components are also examined.

14 CFR 23.934 - Turbojet and turbofan engine thrust reverser systems tests.

Code of Federal Regulations, 2010 CFR

2010-01-01

... 14 Aeronautics and Space 1 2010-01-01 2010-01-01 false Turbojet and turbofan engine thrust... CATEGORY AIRPLANES Powerplant General § 23.934 Turbojet and turbofan engine thrust reverser systems tests. Thrust reverser systems of turbojet or turbofan engines must meet the requirements of § 33.97 of this...

System safety engineering analysis handbook

NASA Technical Reports Server (NTRS)

Ijams, T. E.

1972-01-01

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.

Goals Analysis Procedure Guidelines for Applying the Goals Analysis Process

NASA Technical Reports Server (NTRS)

Motley, Albert E., III

2000-01-01

One of the key elements to successful project management is the establishment of the "right set of requirements", requirements that reflect the true customer needs and are consistent with the strategic goals and objectives of the participating organizations. A viable set of requirements implies that each individual requirement is a necessary element in satisfying the stated goals and that the entire set of requirements, taken as a whole, is sufficient to satisfy the stated goals. Unfortunately, it is the author's experience that during project formulation phases' many of the Systems Engineering customers do not conduct a rigorous analysis of the goals and objectives that drive the system requirements. As a result, the Systems Engineer is often provided with requirements that are vague, incomplete, and internally inconsistent. To complicate matters, most systems development methodologies assume that the customer provides unambiguous, comprehensive and concise requirements. This paper describes the specific steps of a Goals Analysis process applied by Systems Engineers at the NASA Langley Research Center during the formulation of requirements for research projects. The objective of Goals Analysis is to identify and explore all of the influencing factors that ultimately drive the system's requirements.

Questioning the Role of Requirements Engineering in the Causes of Safety-Critical Software Failures

NASA Technical Reports Server (NTRS)

Johnson, C. W.; Holloway, C. M.

2006-01-01

Many software failures stem from inadequate requirements engineering. This view has been supported both by detailed accident investigations and by a number of empirical studies; however, such investigations can be misleading. It is often difficult to distinguish between failures in requirements engineering and problems elsewhere in the software development lifecycle. Further pitfalls arise from the assumption that inadequate requirements engineering is a cause of all software related accidents for which the system fails to meet its requirements. This paper identifies some of the problems that have arisen from an undue focus on the role of requirements engineering in the causes of major accidents. The intention is to provoke further debate within the emerging field of forensic software engineering.

Operational Issues in the Development of a Cost-Effective Reusable LOX/LH2 Engine

NASA Technical Reports Server (NTRS)

Ballard, Richard O.

2003-01-01

The NASA Space Launch Initiative (SLI) was initiated in early 2001 to conduct technology development and to reduce the business and technical risk associated with developing the next-generation reusable launch system. In the field of main propulsion, two LOXLH2 rocket engine systems, the Pratt & Whitney / Aerojet Joint Venture (JV) COBRA and the Rocketdyne RS-83, were funded to develop a safe, economical, and reusable propulsion system. Given that a large-thrust reusable rocket engine program had not been started in the U.S. since 1971, with the Space Shuttle Main Engine (SSME), this provided an opportunity to build on the experience developed on the SSME system, while exploiting advances in technology that had occurred in the intervening 30 years. One facet of engine development that was identified as being especially vital in order to produce an optimal system was in the areas of operability and maintainability. In order to achieve the high levels of performance required by the Space Shuttle, the SSME system is highly complex with very tight tolerances and detailed requirements. Over the lifetime of the SSME program, the engine has required a high level of manpower to support the performance of inspections, maintenance (scheduled and unscheduled) and operations (prelaunch and post-flight). As a consequence, the labor- intensive needs of the SSME provide a significant impact to the overall cost efficiency of the Space Transportation System (STS). One of the strategic goals of the SLI is to reduce cost by requiring the engine(s) to be easier (Le. less expensive) to operate and maintain. The most effective means of accomplishing this goal is to infuse the operability and maintainability features into the engine design from the start. This paper discusses some of the operational issues relevant to a reusable LOx/LH2 main engine, and the means by which their impact is mitigated in the design phase.

Shuttle avionics software trials, tribulations and success

NASA Technical Reports Server (NTRS)

Henderson, O. L.

1985-01-01

The early problems and the solutions developed to provide the required quality software needed to support the space shuttle engine development program are described. The decision to use a programmable digital control system on the space shuttle engine was primarily based upon the need for a flexible control system capable of supporting the total engine mission on a large complex pump fed engine. The mission definition included all control phases from ground checkout through post shutdown propellant dumping. The flexibility of the controller through reprogrammable software allowed the system to respond to the technical challenges and innovation required to develop both the engine and controller hardware. This same flexibility, however, placed a severe strain on the capability of the software development and verification organization. The overall development program required that the software facility accommodate significant growth in both the software requirements and the number of software packages delivered. This challenge was met by reorganization and evolution in the process of developing and verifying software.

Split radiator design for heat rejection optimization for a waste heat recovery system

DOEpatents

Ernst, Timothy C.; Nelson, Christopher R.

2016-10-18

A cooling system provides improved heat recovery by providing a split core radiator for both engine cooling and condenser cooling for a Rankine cycle (RC). The cooling system includes a radiator having a first cooling core portion and a second cooling core portion. An engine cooling loop is fluidly connected the second cooling core portion. A condenser of an RC has a cooling loop fluidly connected to the first cooling core portion. A valve is provided between the engine cooling loop and the condenser cooling loop adjustably control the flow of coolant in the condenser cooling loop into the engine cooling loop. The cooling system includes a controller communicatively coupled to the valve and adapted to determine a load requirement for the internal combustion engine and adjust the valve in accordance with the engine load requirement.

Status of the advanced Stirling conversion system project for 25 kW dish Stirling applications

NASA Technical Reports Server (NTRS)

Shaltens, Richard K.; Schreiber, Jeffrey G.

1991-01-01

Heat engines were evaluated for terrestrial Solar Distributed Heat Receivers. The Stirling engine was identified as one of the most promising heat engines for terrestrial applications. Technology development is also conducted for Stirling convertors directed toward a dynamic power source for space applications. Space power requirements include high reliability with very long life, low vibration, and high system efficiency. The free-piston Stirling engine has the potential for future high power space conversion systems, either nuclear or solar powered. Although both applications appear to be quite different, their requirements complement each other.

Deep Borehole Field Test Requirements and Controlled Assumptions.

DOE Office of Scientific and Technical Information (OSTI.GOV)

Hardin, Ernest

2015-07-01

This document presents design requirements and controlled assumptions intended for use in the engineering development and testing of: 1) prototype packages for radioactive waste disposal in deep boreholes; 2) a waste package surface handling system; and 3) a subsurface system for emplacing and retrieving packages in deep boreholes. Engineering development and testing is being performed as part of the Deep Borehole Field Test (DBFT; SNL 2014a). This document presents parallel sets of requirements for a waste disposal system and for the DBFT, showing the close relationship. In addition to design, it will also inform planning for drilling, construction, and scientificmore » characterization activities for the DBFT. The information presented here follows typical preparations for engineering design. It includes functional and operating requirements for handling and emplacement/retrieval equipment, waste package design and emplacement requirements, borehole construction requirements, sealing requirements, and performance criteria. Assumptions are included where they could impact engineering design. Design solutions are avoided in the requirements discussion. Deep Borehole Field Test Requirements and Controlled Assumptions July 21, 2015 iv ACKNOWLEDGEMENTS This set of requirements and assumptions has benefited greatly from reviews by Gordon Appel, Geoff Freeze, Kris Kuhlman, Bob MacKinnon, Steve Pye, David Sassani, Dave Sevougian, and Jiann Su.« less

The First Development of Human Factors Engineering Requirements for Application to Ground Task Design for a NASA Flight Program

NASA Technical Reports Server (NTRS)

Dischinger, H. Charles, Jr.; Stambolian, Damon B.; Miller, Darcy H.

2008-01-01

The National Aeronautics and Space Administration has long applied standards-derived human engineering requirements to the development of hardware and software for use by astronauts while in flight. The most important source of these requirements has been NASA-STD-3000. While there have been several ground systems human engineering requirements documents, none has been applicable to the flight system as handled at NASA's launch facility at Kennedy Space Center. At the time of the development of previous human launch systems, there were other considerations that were deemed more important than developing worksites for ground crews; e.g., hardware development schedule and vehicle performance. However, experience with these systems has shown that failure to design for ground tasks has resulted in launch schedule delays, ground operations that are more costly than they might be, and threats to flight safety. As the Agency begins the development of new systems to return humans to the moon, the new Constellation Program is addressing this issue with a new set of human engineering requirements. Among these requirements is a subset that will apply to the design of the flight components and that is intended to assure ground crew success in vehicle assembly and maintenance tasks. These requirements address worksite design for usability and for ground crew safety.

Thrust Vector Control for Nuclear Thermal Rockets

NASA Technical Reports Server (NTRS)

Ensworth, Clinton B. F.

2013-01-01

Future space missions may use Nuclear Thermal Rocket (NTR) stages for human and cargo missions to Mars and other destinations. The vehicles are likely to require engine thrust vector control (TVC) to maintain desired flight trajectories. This paper explores requirements and concepts for TVC systems for representative NTR missions. Requirements for TVC systems were derived using 6 degree-of-freedom models of NTR vehicles. Various flight scenarios were evaluated to determine vehicle attitude control needs and to determine the applicability of TVC. Outputs from the models yielded key characteristics including engine gimbal angles, gimbal rates and gimbal actuator power. Additional factors such as engine thrust variability and engine thrust alignment errors were examined for impacts to gimbal requirements. Various technologies are surveyed for TVC systems for the NTR applications. A key factor in technology selection is the unique radiation environment present in NTR stages. Other considerations including mission duration and thermal environments influence the selection of optimal TVC technologies. Candidate technologies are compared to see which technologies, or combinations of technologies best fit the requirements for selected NTR missions. Representative TVC systems are proposed and key properties such as mass and power requirements are defined. The outputs from this effort can be used to refine NTR system sizing models, providing higher fidelity definition for TVC systems for future studies.

Optimization in the systems engineering process

NASA Technical Reports Server (NTRS)

Lemmerman, Loren A.

1993-01-01

The essential elements of the design process consist of the mission definition phase that provides the system requirements, the conceptual design, the preliminary design and finally the detailed design. Mission definition is performed largely by operations analysts in conjunction with the customer. The result of their study is handed off to the systems engineers for documentation as the systems requirements. The document that provides these requirements is the basis for the further design work of the design engineers at the Lockheed-Georgia Company. The design phase actually begins with conceptual design, which is generally conducted by a small group of engineers using multidisciplinary design programs. Because of the complexity of the design problem, the analyses are relatively simple and generally dependent on parametric analyses of the configuration. The result of this phase is a baseline configuration from which preliminary design may be initiated.

Automotive Stirling reference engine design report

NASA Technical Reports Server (NTRS)

1981-01-01

The reference Stirling engine system is described which provides the best possible fuel economy while meeting or exceeding all other program objectives. The system was designed to meet the requirements of a 1984 Pontiac Phoenix (X-body). This design utilizes all new technology that can reasonably be expected to be developed by 1984 and that is judged to provide significant improvement, relative to development risk and cost. Topics covered include: (1) external heat system; (2) hot engine system; (3) cold engine system; (4) engine drive system; (5) power control system and auxiliaries; (6) engine instalation; (7) optimization and vehicle simulation; (8) engine materials; and (9) production cost analysis.

Semantic Modeling of Requirements: Leveraging Ontologies in Systems Engineering

ERIC Educational Resources Information Center

Mir, Masood Saleem

2012-01-01

The interdisciplinary nature of "Systems Engineering" (SE), having "stakeholders" from diverse domains with orthogonal facets, and need to consider all stages of "lifecycle" of system during conception, can benefit tremendously by employing "Knowledge Engineering" (KE) to achieve semantic agreement among all…

30 CFR 36.23 - Engine intake system.

Code of Federal Regulations, 2013 CFR

2013-07-01

... 30 Mineral Resources 1 2013-07-01 2013-07-01 false Engine intake system. 36.23 Section 36.23... EQUIPMENT Construction and Design Requirements § 36.23 Engine intake system. (a) Construction. The intake... intake system without permanent deformation and shall prevent the propagation of flame through the joint...

Systems Engineering

NASA Technical Reports Server (NTRS)

Pellerano, Fernando

2015-01-01

This short course provides information on what systems engineering is and how the systems engineer guides requirements, interfaces with the discipline leads, and resolves technical issues. There are many system-wide issues that either impact or are impacted by the thermal subsystem. This course will introduce these issues and illustrate them with real life examples.

COBRA System Engineering Processes to Achieve SLI Strategic Goals

NASA Technical Reports Server (NTRS)

Ballard, Richard O.

2003-01-01

The COBRA Prototype Main Engine Development Project was an endeavor conducted as a joint venture between Pratt & Whitney and Aerojet to conduct risk reduction in LOX/LH2 main engine technology for the NASA Space Launch Initiative (SLI). During the seventeen months of the project (April 2001 to September 2002), approximately seventy reviews were conducted, beginning with the Engine Systems Requirements Review (SRR) and ending with the Engine Systems Interim Design Review (IDR). This paper discusses some of the system engineering practices used to support the reviews and the overall engine development effort.

Advanced supersonic propulsion study, phase 2. [propulsion system performance, design analysis and technology assessment

NASA Technical Reports Server (NTRS)

Howlett, R. A.

1975-01-01

A continuation of the NASA/P and WA study to evaluate various types of propulsion systems for advanced commercial supersonic transports has resulted in the identification of two very promising engine concepts. They are the Variable Stream Control Engine which provides independent temperature and velocity control for two coannular exhaust streams, and a derivative of this engine, a Variable Cycle Engine that employs a rear flow-inverter valve to vary the bypass ratio of the cycle. Both concepts are based on advanced engine technology and have the potential for significant improvements in jet noise, exhaust emissions and economic characteristics relative to current technology supersonic engines. Extensive research and technology programs are required in several critical areas that are unique to these supersonic Variable Cycle Engines to realize these potential improvements. Parametric cycle and integration studies of conventional and Variable Cycle Engines are reviewed, features of the two most promising engine concepts are described, and critical technology requirements and required programs are summarized.

Design description of a microprocessor based Engine Monitoring and Control unit (EMAC) for small turboshaft

NASA Technical Reports Server (NTRS)

Baez, A. N.

1985-01-01

Research programs have demonstrated that digital electronic controls are more suitable for advanced aircraft/rotorcraft turbine engine systems than hydromechanical controls. Commercially available microprocessors are believed to have the speed and computational capability required for implementing advanced digital control algorithms. Thus, it is desirable to demonstrate that off-the-shelf microprocessors are indeed capable of performing real time control of advanced gas turbine engines. The engine monitoring and control (EMAC) unit was designed and fabricated specifically to meet the requirements of an advanced gas turbine engine control system. The EMAC unit is fully operational in the Army/NASA small turboshaft engine digital research program.

Systems Security Engineering

DTIC Science & Technology

2010-08-22

Commission (IEC). “Information technology — Security techniques — Code of practice for information security management ( ISO /IEC 27002 ...Information technology — Security techniques — Information security management systems —Requirements ( ISO /IEC 27002 ),”, “Information technology — Security...was a draft ISO standard on Systems and software engineering, Systems and software assurance [18]. Created by systems engineers for systems

Systems Engineering Model for ART Energy Conversion

DOE Office of Scientific and Technical Information (OSTI.GOV)

Mendez Cruz, Carmen Margarita; Rochau, Gary E.; Wilson, Mollye C.

The near-term objective of the EC team is to establish an operating, commercially scalable Recompression Closed Brayton Cycle (RCBC) to be constructed for the NE - STEP demonstration system (demo) with the lowest risk possible. A systems engineering approach is recommended to ensure adequate requirements gathering, documentation, and mode ling that supports technology development relevant to advanced reactors while supporting crosscut interests in potential applications. A holistic systems engineering model was designed for the ART Energy Conversion program by leveraging Concurrent Engineering, Balance Model, Simplified V Model, and Project Management principles. The resulting model supports the identification and validation ofmore » lifecycle Brayton systems requirements, and allows designers to detail system-specific components relevant to the current stage in the lifecycle, while maintaining a holistic view of all system elements.« less

Engine system assessment study using Martian propellants

NASA Technical Reports Server (NTRS)

Pelaccio, Dennis; Jacobs, Mark; Scheil, Christine; Collins, John

1992-01-01

A top-level feasibility study was conducted that identified and characterized promising chemical propulsion system designs which use two or more of the following propellant combinations: LOX/H2, LOX/CH4, and LOX/CO. The engine systems examined emphasized the usage of common subsystem/component hardware where possible. In support of this study, numerous mission scenarios were characterized that used various combinations of Earth, lunar, and Mars propellants to establish engine system requirements to assess the promising engine system design concept examined, and to determine overall exploration leverage of such systems compared to state-of-the-art cryogenic (LOX/H2) propulsion systems. Initially in the study, critical propulsion system technologies were assessed. Candidate expander and gas generator cycle LOX/H2/CO, LOX/H2/CH4, and LOX/CO/CH4 engine system designs were parametrically evaluated. From this evaluation baseline, tripropellant Mars Transfer Vehicle (MTV) LOX cooled and bipropellant Lunar Excursion Vehicle (LEV) and Mars Excursion Vehicle (MEV) engine systems were identified. Representative tankage designs for a MTV were also investigated. Re-evaluation of the missions using the baseline engine design showed that in general the slightly lower performance, smaller, lower weight gas generator cycle-based engines required less overall mission Mars and in situ propellant production (ISPP) infrastructure support compared to the larger, heavier, higher performing expander cycle engine systems.

Advanced rocket propulsion

NASA Technical Reports Server (NTRS)

Obrien, Charles J.

1993-01-01

Existing NASA research contracts are supporting development of advanced reinforced polymer and metal matrix composites for use in liquid rocket engines of the future. Advanced rocket propulsion concepts, such as modular platelet engines, dual-fuel dual-expander engines, and variable mixture ratio engines, require advanced materials and structures to reduce overall vehicle weight as well as address specific propulsion system problems related to elevated operating temperatures, new engine components, and unique operating processes. High performance propulsion systems with improved manufacturability and maintainability are needed for single stage to orbit vehicles and other high performance mission applications. One way to satisfy these needs is to develop a small engine which can be clustered in modules to provide required levels of total thrust. This approach should reduce development schedule and cost requirements by lowering hardware lead times and permitting the use of existing test facilities. Modular engines should also reduce operational costs associated with maintenance and parts inventories.

Systems engineering and the user: Incorporation of user requirements into the SE process

NASA Technical Reports Server (NTRS)

Naugle, John E.

1993-01-01

This paper is organized into four parts. In the Gestation Phase, I describe the process of starting a new mission and establishing its rough boundaries. Next I show how the scientific experiments are selected. Then we enter the Preliminary Design Phase, where we incorporate the scientist's instruments into the systems engineering process. Finally, I show how the Preliminary Design Review (PDR) assures NASA management and the scientists that the scientific requirements have been incorporated into the systems engineering process to everyone's satisfaction.

Connecting Requirements to Architecture and Analysis via Model-Based Systems Engineering

NASA Technical Reports Server (NTRS)

Cole, Bjorn F.; Jenkins, J. Steven

2015-01-01

In traditional systems engineering practice, architecture, concept development, and requirements development are related but still separate activities. Concepts for operation, key technical approaches, and related proofs of concept are developed. These inform the formulation of an architecture at multiple levels, starting with the overall system composition and functionality and progressing into more detail. As this formulation is done, a parallel activity develops a set of English statements that constrain solutions. These requirements are often called "shall statements" since they are formulated to use "shall." The separation of requirements from design is exacerbated by well-meaning tools like the Dynamic Object-Oriented Requirements System (DOORS) that remained separated from engineering design tools. With the Europa Clipper project, efforts are being taken to change the requirements development approach from a separate activity to one intimately embedded in formulation effort. This paper presents a modeling approach and related tooling to generate English requirement statements from constraints embedded in architecture definition.

46 CFR 96.05-1 - Installation and details.

Code of Federal Regulations, 2013 CFR

2013-10-01

... CONTROL AND MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communications Systems § 96.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or... be in accordance with the requirements of subchapter J (Electrical Engineering) of this chapter...

46 CFR 96.05-1 - Installation and details.

Code of Federal Regulations, 2012 CFR

2012-10-01

... CONTROL AND MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communications Systems § 96.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or... be in accordance with the requirements of subchapter J (Electrical Engineering) of this chapter...

46 CFR 96.05-1 - Installation and details.

Code of Federal Regulations, 2014 CFR

2014-10-01

... CONTROL AND MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communications Systems § 96.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or... be in accordance with the requirements of subchapter J (Electrical Engineering) of this chapter...

46 CFR 96.05-1 - Installation and details.

Code of Federal Regulations, 2011 CFR

2011-10-01

... CONTROL AND MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communications Systems § 96.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or... be in accordance with the requirements of subchapter J (Electrical Engineering) of this chapter...

46 CFR 96.05-1 - Installation and details.

Code of Federal Regulations, 2010 CFR

2010-10-01

... CONTROL AND MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communications Systems § 96.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or... be in accordance with the requirements of subchapter J (Electrical Engineering) of this chapter...

Creating system engineering products with executable models in a model-based engineering environment

NASA Astrophysics Data System (ADS)

Karban, Robert; Dekens, Frank G.; Herzig, Sebastian; Elaasar, Maged; Jankevičius, Nerijus

2016-08-01

Applying systems engineering across the life-cycle results in a number of products built from interdependent sources of information using different kinds of system level analysis. This paper focuses on leveraging the Executable System Engineering Method (ESEM) [1] [2], which automates requirements verification (e.g. power and mass budget margins and duration analysis of operational modes) using executable SysML [3] models. The particular value proposition is to integrate requirements, and executable behavior and performance models for certain types of system level analysis. The models are created with modeling patterns that involve structural, behavioral and parametric diagrams, and are managed by an open source Model Based Engineering Environment (named OpenMBEE [4]). This paper demonstrates how the ESEM is applied in conjunction with OpenMBEE to create key engineering products (e.g. operational concept document) for the Alignment and Phasing System (APS) within the Thirty Meter Telescope (TMT) project [5], which is under development by the TMT International Observatory (TIO) [5].

Engine design considerations for 2nd generation supersonic transports

NASA Technical Reports Server (NTRS)

Howlett, R. A.

1975-01-01

The environmental and economic goals projected for advanced supersonic transports will require revolutionary improvements in propulsion systems. Variable cycle engine concepts that incorporate unique components and advanced technologies show promise in meeting these goals. Pratt & Whitney Aircraft is conducting conceptual design studies of variable cycle engine concepts under NASA sponsorship. This paper reviews some of the design considerations for these engine concepts. Emphasis is placed on jet noise abatement, reduction of emissions, performance improvements, installation considerations, hot-section characteristics and control system requirements. Two representative variable cycle engine concepts that incorporate these basic design considerations are described.

DYGABCD: A program for calculating linear A, B, C, and D matrices from a nonlinear dynamic engine simulation

NASA Technical Reports Server (NTRS)

Geyser, L. C.

1978-01-01

A digital computer program, DYGABCD, was developed that generates linearized, dynamic models of simulated turbofan and turbojet engines. DYGABCD is based on an earlier computer program, DYNGEN, that is capable of calculating simulated nonlinear steady-state and transient performance of one- and two-spool turbojet engines or two- and three-spool turbofan engines. Most control design techniques require linear system descriptions. For multiple-input/multiple-output systems such as turbine engines, state space matrix descriptions of the system are often desirable. DYGABCD computes the state space matrices commonly referred to as the A, B, C, and D matrices required for a linear system description. The report discusses the analytical approach and provides a users manual, FORTRAN listings, and a sample case.

Control Design for an Advanced Geared Turbofan Engine

NASA Technical Reports Server (NTRS)

Chapman, Jeffryes W.; Litt, Jonathan S.

2017-01-01

This paper describes the design process for the control system of an advanced geared turbofan engine. This process is applied to a simulation that is representative of a 30,000 lbf thrust class concept engine with two main spools, ultra-high bypass ratio, and a variable area fan nozzle. Control system requirements constrain the non-linear engine model as it operates throughout its flight envelope of sea level to 40,000 ft and from 0 to 0.8 Mach. The control architecture selected for this project was developed from literature and reflects a configuration that utilizes a proportional integral controller integrated with sets of limiters that enable the engine to operate safely throughout its flight envelope. Simulation results show the overall system meets performance requirements without exceeding system operational limits.

Requirements, Verification, and Compliance (RVC) Database Tool

NASA Technical Reports Server (NTRS)

Rainwater, Neil E., II; McDuffee, Patrick B.; Thomas, L. Dale

2001-01-01

This paper describes the development, design, and implementation of the Requirements, Verification, and Compliance (RVC) database used on the International Space Welding Experiment (ISWE) project managed at Marshall Space Flight Center. The RVC is a systems engineer's tool for automating and managing the following information: requirements; requirements traceability; verification requirements; verification planning; verification success criteria; and compliance status. This information normally contained within documents (e.g. specifications, plans) is contained in an electronic database that allows the project team members to access, query, and status the requirements, verification, and compliance information from their individual desktop computers. Using commercial-off-the-shelf (COTS) database software that contains networking capabilities, the RVC was developed not only with cost savings in mind but primarily for the purpose of providing a more efficient and effective automated method of maintaining and distributing the systems engineering information. In addition, the RVC approach provides the systems engineer the capability to develop and tailor various reports containing the requirements, verification, and compliance information that meets the needs of the project team members. The automated approach of the RVC for capturing and distributing the information improves the productivity of the systems engineer by allowing that person to concentrate more on the job of developing good requirements and verification programs and not on the effort of being a "document developer".

NASA Risk Management Handbook. Version 1.0

NASA Technical Reports Server (NTRS)

Dezfuli, Homayoon; Benjamin, Allan; Everett, Christopher; Maggio, Gaspare; Stamatelatos, Michael; Youngblood, Robert; Guarro, Sergio; Rutledge, Peter; Sherrard, James; Smith, Curtis;

The next generation rocket engines

NASA Astrophysics Data System (ADS)

Beichel, Rudi; O'Brien, Charles J.; Taylor, James P.

This paper examines propulsion system technologies for earth-to-orbit vehicles, and describes several propulsion system concepts which could support the recommendations of the Commission for Space Development for the year 2000. The hallmark of that system must and will be reliability. Reliability will be obtained through a very structured design approach, coupled with a rational, cost effective, development and qualification program. To improve the next generation space transportation propulsion systems we need to select the very best of alternative power and performance cycles and engine physical concepts with a rigid requirement to achieve a robust, dependable, affordable propulsion system. For example, engine concepts using either propellants or non-propellant fluids for cooling and/or power drive offer the potential to provide smooth, controlled engine starts, low turbine temperatures, etc. as required for long life turbomachinery. Concepts examined are LOX/LH 2, |LOX/LH 2 + hydrocarbon, and LOX/LH 2 + hydrocarbon + Al dual expander engines, separate LOX/LH 2 and LOX/hydrocarbon engines, and variable mixture ratio engines. A fully reusable propulsion system that is perceived to be very low risk and low in operation cost is described.

Visit from JAXA to NASA MSFC: The Engines Element & Ideas for Collaboration

NASA Technical Reports Server (NTRS)

Greene, William D.

2013-01-01

System Design, Development, and Fabrication: Design, develop, and fabricate or procure MB-60 component hardware compliant with the imposed technical requirements and in sufficient quantities to fulfill the overall MB-60 development effort. System Development, Assembly, and Test: Manage the scope of the development, assembly, and test-related activities for MB-60 development. This scope includes engine-level development planning, engine assembly and disassembly, test planning, engine testing, inspection, anomaly resolution, and development of necessary ground support equipment and special test equipment. System Integration: Provide coordinated integration in the realms of engineering, safety, quality, and manufacturing disciplines across the scope of the MB-60 design and associated products development Safety and Mission Assurance, structural design, fracture control, materials and processes, thermal analysis. Systems Engineering and Analysis: Manage and perform Systems Engineering and Analysis to provide rigor and structure to the overall design and development effort for the MB-60. Milestone reviews, requirements management, system analysis, program management support Program Management: Manage, plan, and coordinate the activities across all portions of the MB-60 work scope by providing direction for program administration, business management, and supplier management.

Solar-Powered Electric Propulsion Systems: Engineering and Applications

NASA Technical Reports Server (NTRS)

Stearns, J. W.; Kerrisk, D. J.

1966-01-01

Lightweight, multikilowatt solar power arrays in conjunction with electric propulsion offer potential improvements to space exploration, extending the usefulness of existing launch vehicles to higher-energy missions. Characteristics of solar-powered electric propulsion missions are outlined, and preliminary performance estimates are shown. Spacecraft system engineering is discussed with respect to parametric trade-offs in power and propulsion system design. Relationships between mission performance and propulsion system performance are illustrated. The present state of the art of electric propulsion systems is reviewed and related to the mission requirements identified earlier. The propulsion system design and test requirements for a mission spacecraft are identified and discussed. Although only ion engine systems are currently available, certain plasma propulsion systems offer some advantages in over-all system design. These are identified, and goals are set for plasma-thrustor systems to make them competitive with ion-engine systems for mission applications.

Requirements Analysis and Course Improvements for EO3502 Telecommunications Systems Engineering

DTIC Science & Technology

2005-03-01

California, Berkeley, School of Information Management and Systems The University of California, Berkeley (Cal) is a public, coeducational university...NAVAL POSTGRADUATE SCHOOL MONTEREY, CALIFORNIA THESIS REQUIREMENTS ANALYSIS AND COURSE IMPROVEMENTS FOR E03502 TELECOMMUNICATIONS SYSTEMS ENGINEERING...Postgraduate School ORGANIZATION REPORT Monterey, CA 93943-5000 NUMBER 9. SPONSORING /MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSORING

A Knowledge-Based and Model-Driven Requirements Engineering Approach to Conceptual Satellite Design

NASA Astrophysics Data System (ADS)

Dos Santos, Walter A.; Leonor, Bruno B. F.; Stephany, Stephan

Satellite systems are becoming even more complex, making technical issues a significant cost driver. The increasing complexity of these systems makes requirements engineering activities both more important and difficult. Additionally, today's competitive pressures and other market forces drive manufacturing companies to improve the efficiency with which they design and manufacture space products and systems. This imposes a heavy burden on systems-of-systems engineering skills and particularly on requirements engineering which is an important phase in a system's life cycle. When this is poorly performed, various problems may occur, such as failures, cost overruns and delays. One solution is to underpin the preliminary conceptual satellite design with computer-based information reuse and integration to deal with the interdisciplinary nature of this problem domain. This can be attained by taking a model-driven engineering approach (MDE), in which models are the main artifacts during system development. MDE is an emergent approach that tries to address system complexity by the intense use of models. This work outlines the use of SysML (Systems Modeling Language) and a novel knowledge-based software tool, named SatBudgets, to deal with these and other challenges confronted during the conceptual phase of a university satellite system, called ITASAT, currently being developed by INPE and some Brazilian universities.

Design study of RL10 derivatives. Volume 2: Engine design characteristics, appendices. [development of rocket engine for application to space tug propulsion system

NASA Technical Reports Server (NTRS)

1973-01-01

Calculations, curves, and substantiating data which support the engine design characteristics of the RL-10 engines are presented. A description of the RL-10 ignition system is provided. The performance calculations of the RL-10 derivative engines and the performance results obtained are reported. The computer simulations used to establish the control system requirements and to define the engine transient characteristics are included.

SHARP's systems engineering challenge: rectifying integrated product team requirements with performance issues in an evolutionary spiral development acquisition

NASA Astrophysics Data System (ADS)

Kuehl, C. Stephen

2003-08-01

Completing its final development and early deployment on the Navy's multi-role aircraft, the F/A-18 E/F Super Hornet, the SHAred Reconnaissance Pod (SHARP) provides the war fighter with the latest digital tactical reconnaissance (TAC Recce) Electro-Optical/Infrared (EO/IR) sensor system. The SHARP program is an evolutionary acquisition that used a spiral development process across a prototype development phase tightly coupled into overlapping Engineering and Manufacturing Development (EMD) and Low Rate Initial Production (LRIP) phases. Under a tight budget environment with a highly compressed schedule, SHARP challenged traditional acquisition strategies and systems engineering (SE) processes. Adopting tailored state-of-the-art systems engineering process models allowd the SHARP program to overcome the technical knowledge transition challenges imposed by a compressed program schedule. The program's original goal was the deployment of digital TAC Recce mission capabilities to the fleet customer by summer of 2003. Hardware and software integration technical challenges resulted from requirements definition and analysis activities performed across a government-industry led Integrated Product Team (IPT) involving Navy engineering and test sites, Boeing, and RTSC-EPS (with its subcontracted hardware and government furnished equipment vendors). Requirements development from a bottoms-up approach was adopted using an electronic requirements capture environment to clarify and establish the SHARP EMD product baseline specifications as relevant technical data became available. Applying Earned-Value Management (EVM) against an Integrated Master Schedule (IMS) resulted in efficiently managing SE task assignments and product deliveries in a dynamically evolving customer requirements environment. Application of Six Sigma improvement methodologies resulted in the uncovering of root causes of errors in wiring interconnectivity drawings, pod manufacturing processes, and avionics requirements specifications. Utilizing the draft NAVAIR SE guideline handbook and the ANSI/EIA-632 standard: Processes for Engineering a System, a systems engineering tailored process approach was adopted for the accelerated SHARP EMD prgram. Tailoring SE processes in this accelerated product delivery environment provided unique opportunities to be technically creative in the establishment of a product performance baseline. This paper provides an historical overview of the systems engineering activities spanning the prototype phase through the EMD SHARP program phase, the performance requirement capture activities and refinement process challenges, and what SE process improvements can be applied to future SHARP-like programs adopting a compressed, evolutionary spiral development acquisition paradigm.

Energy efficient engine. Core engine bearings, drives and configuration: Detailed design report

NASA Technical Reports Server (NTRS)

Broman, C. L.

1981-01-01

The detailed design of the forward and aft sumps, the accessory drive system, the lubrication system, and the piping/manifold configuration to be employed in the core engine test of the Energy Efficient Engine is addressed. The design goals for the above components were established based on the requirements of the test cell engine.

NEXT Single String Integration Test Results

NASA Technical Reports Server (NTRS)

Soulas, George C.; Patterson, Michael J.; Pinero, Luis; Herman, Daniel A.; Snyder, Steven John

2010-01-01

As a critical part of NASA's Evolutionary Xenon Thruster (NEXT) test validation process, a single string integration test was performed on the NEXT ion propulsion system. The objectives of this test were to verify that an integrated system of major NEXT ion propulsion system elements meets project requirements, to demonstrate that the integrated system is functional across the entire power processor and xenon propellant management system input ranges, and to demonstrate to potential users that the NEXT propulsion system is ready for transition to flight. Propulsion system elements included in this system integration test were an engineering model ion thruster, an engineering model propellant management system, an engineering model power processor unit, and a digital control interface unit simulator that acted as a test console. Project requirements that were verified during this system integration test included individual element requirements ; integrated system requirements, and fault handling. This paper will present the results of these tests, which include: integrated ion propulsion system demonstrations of performance, functionality and fault handling; a thruster re-performance acceptance test to establish baseline performance: a risk-reduction PMS-thruster integration test: and propellant management system calibration checks.

A Project-Based Cooperative Approach to Teaching Sustainable Energy Systems

ERIC Educational Resources Information Center

Verbic, Gregor; Keerthisinghe, Chanaka; Chapman, Archie C.

2017-01-01

Engineering education is undergoing a restructuring driven by the needs of an increasingly multidisciplinary engineering profession. At the same time, power systems are transitioning toward future smart grids that will require power engineers with skills outside of the core power engineering domain. Since including new topics in the existing…

Achieving Maximum Integration Utilizing Requirements Flow Down

NASA Technical Reports Server (NTRS)

Archiable, Wes; Askins, Bruce

2011-01-01

A robust and experienced systems engineering team is essential for a successful program. It is often a challenge to build a core systems engineering team early enough in a program to maximize integration and assure a common path for all supporting teams in a project. Ares I was no exception. During the planning of IVGVT, the team had many challenges including lack of: early identification of stakeholders, team training in NASA s system engineering practices, solid requirements flow down and a top down documentation strategy. The IVGVT team started test planning early in the program before the systems engineering framework had been matured due to an aggressive schedule. Therefore the IVGVT team increased their involvement in the Constellation systems engineering effort. Program level requirements were established that flowed down to IVGVT aligning all stakeholders to a common set of goals. The IVGVT team utilized the APPEL REQ Development Management course providing the team a NASA focused model to follow. The IVGVT team engaged directly with the model verification and validation process to assure that a solid set of requirements drove the need for the test event. The IVGVT team looked at the initial planning state, analyzed the current state and then produced recommendations for the ideal future state of a wide range of systems engineering functions and processes. Based on this analysis, the IVGVT team was able to produce a set of lessons learned and to provide suggestions for future programs or tests to use in their initial planning phase.

Energy Efficient Engine (E3) combustion system component technology performance report

NASA Technical Reports Server (NTRS)

Burrus, D. L.; Chahrour, C. A.; Foltz, H. L.; Sabla, P. E.; Seto, S. P.; Taylor, J. R.

1984-01-01

The Energy Efficient Engine (E3) combustor effort was conducted as part of the overall NASA/GE E3 Program. This effort included the selection of an advanced double-annular combustion system design. The primary intent of this effort was to evolve a design that meets the stringent emissions and life goals of the E3, as well as all of the usual performance requirements of combustion systems for modern turbofan engines. Numerous detailed design studies were conducted to define the features of the combustion system design. Development test hardware was fabricated, and an extensive testing effort was undertaken to evaluate the combustion system subcomponents in order to verify and refine the design. Technology derived from this effort was incorporated into the engine combustion hardware design. The advanced engine combustion system was then evaluated in component testing to verify the design intent. What evolved from this effort was an advanced combustion system capable of satisfying all of the combustion system design objectives and requirements of the E3.

Conversion from Tree to Graph Representation of Requirements

NASA Technical Reports Server (NTRS)

Mayank, Vimal; Everett, David Frank; Shmunis, Natalya; Austin, Mark

2009-01-01

A procedure and software to implement the procedure have been devised to enable conversion from a tree representation to a graph representation of the requirements governing the development and design of an engineering system. The need for this procedure and software and for other requirements-management tools arises as follows: In systems-engineering circles, it is well known that requirements- management capability improves the likelihood of success in the team-based development of complex systems involving multiple technological disciplines. It is especially desirable to be able to visualize (in order to identify and manage) requirements early in the system- design process, when errors can be corrected most easily and inexpensively.

IDC Re-Engineering Phase 2 System Specification Document Version 1.5

DOE Office of Scientific and Technical Information (OSTI.GOV)

Satpathi, Meara Allena; Burns, John F.; Harris, James M.

This document contains the system specifications derived to satisfy the system requirements found in the IDC System Requirements Document for the IDC Re-Engineering Phase 2 project. This System Specification Document (SSD) defines waveform data processing requirements for the International Data Centre (IDC) of the Comprehensive Nuclear Test Ban Treaty Organization (CTBTO). The routine processing includes characterization of events with the objective of screening out events considered to be consistent with natural phenomena or non-nuclear, man-made phenomena. This document does not address requirements concerning acquisition, processing and analysis of radionuclide data but does include requirements for the dissemination of radionuclide datamore » and products.« less

Engineering Ethics in the Subject of Engineering History

NASA Astrophysics Data System (ADS)

Isohata, Hiroshi

Engineering ethics has been focused in the field of engineering education since the introduction of accreditation system of engineering education. In this paper, contents of the subject of engineering history are examined and discussed from the viewpoints of education of engineering ethics through a practical case of civil engineering history in a college. For the first step, codes of engineering ethics regulated in various engineering organizations are analyzed and the common contents are extracted to set the requirements for the education of engineering ethics. Then contents of the subject of engineering history are examined according to the requirements. Finally, conditions of engineering history for engineering ethics are discussed.

Space shuttle main engine controller

NASA Technical Reports Server (NTRS)

Mattox, R. M.; White, J. B.

1981-01-01

A technical description of the space shuttle main engine controller, which provides engine checkout prior to launch, engine control and monitoring during launch, and engine safety and monitoring in orbit, is presented. Each of the major controller subassemblies, the central processing unit, the computer interface electronics, the input electronics, the output electronics, and the power supplies are described and discussed in detail along with engine and orbiter interfaces and operational requirements. The controller represents a unique application of digital concepts, techniques, and technology in monitoring, managing, and controlling a high performance rocket engine propulsion system. The operational requirements placed on the controller, the extremely harsh operating environment to which it is exposed, and the reliability demanded, result in the most complex and rugged digital system ever designed, fabricated, and flown.

Control Design for an Advanced Geared Turbofan Engine

NASA Technical Reports Server (NTRS)

Chapman, Jeffryes W.; Litt, Jonathan S.

2017-01-01

This paper describes the design process for the control system of an advanced geared turbofan engine. This process is applied to a simulation that is representative of a 30,000 pound-force thrust class concept engine with two main spools, ultra-high bypass ratio, and a variable area fan nozzle. Control system requirements constrain the non-linear engine model as it operates throughout its flight envelope of sea level to 40,000 feet and from 0 to 0.8 Mach. The purpose of this paper is to review the engine control design process for an advanced turbofan engine configuration. The control architecture selected for this project was developed from literature and reflects a configuration that utilizes a proportional integral controller with sets of limiters that enable the engine to operate safely throughout its flight envelope. Simulation results show the overall system meets performance requirements without exceeding operational limits.

46 CFR 107.231 - Inspection for certification.

Code of Federal Regulations, 2010 CFR

2010-10-01

... chapter, Electrical Engineering; 1 1 Requirements for industrial systems and components are in Subpart 111.94 of this chapter. (3) Subchapter F of this chapter, Marine Engineering; 2 2 Requirements for industrial systems and components are in Subpart 58.60 of this chapter. (4) Subchapter E of this chapter...

46 CFR 107.231 - Inspection for certification.

Code of Federal Regulations, 2014 CFR

2014-10-01

... chapter, Electrical Engineering; 1 1 Requirements for industrial systems and components are in Subpart 111.94 of this chapter. (3) Subchapter F of this chapter, Marine Engineering; 2 2 Requirements for industrial systems and components are in Subpart 58.60 of this chapter. (4) Subchapter E of this chapter...

46 CFR 107.231 - Inspection for certification.

Code of Federal Regulations, 2013 CFR

2013-10-01

... chapter, Electrical Engineering; 1 1 Requirements for industrial systems and components are in Subpart 111.94 of this chapter. (3) Subchapter F of this chapter, Marine Engineering; 2 2 Requirements for industrial systems and components are in Subpart 58.60 of this chapter. (4) Subchapter E of this chapter...

46 CFR 107.231 - Inspection for certification.

Code of Federal Regulations, 2011 CFR

2011-10-01

... chapter, Electrical Engineering; 1 1 Requirements for industrial systems and components are in Subpart 111.94 of this chapter. (3) Subchapter F of this chapter, Marine Engineering; 2 2 Requirements for industrial systems and components are in Subpart 58.60 of this chapter. (4) Subchapter E of this chapter...

46 CFR 107.231 - Inspection for certification.

Code of Federal Regulations, 2012 CFR

2012-10-01

... chapter, Electrical Engineering; 1 1 Requirements for industrial systems and components are in Subpart 111.94 of this chapter. (3) Subchapter F of this chapter, Marine Engineering; 2 2 Requirements for industrial systems and components are in Subpart 58.60 of this chapter. (4) Subchapter E of this chapter...

User-centered requirements engineering in health information systems: a study in the hemophilia field.

PubMed

Teixeira, Leonor; Ferreira, Carlos; Santos, Beatriz Sousa

2012-06-01

The use of sophisticated information and communication technologies (ICTs) in the health care domain is a way to improve the quality of services. However, there are also hazards associated with the introduction of ICTs in this domain and a great number of projects have failed due to the lack of systematic consideration of human and other non-technology issues throughout the design or implementation process, particularly in the requirements engineering process. This paper presents the methodological approach followed in the design process of a web-based information system (WbIS) for managing the clinical information in hemophilia care, which integrates the values and practices of user-centered design (UCD) activities into the principles of software engineering, particularly in the phase of requirements engineering (RE). This process followed a paradigm that combines a grounded theory for data collection with an evolutionary design based on constant development and refinement of the generic domain model using three well-known methodological approaches: (a) object-oriented system analysis; (b) task analysis; and, (c) prototyping, in a triangulation work. This approach seems to be a good solution for the requirements engineering process in this particular case of the health care domain, since the inherent weaknesses of individual methods are reduced, and emergent requirements are easier to elicit. Moreover, the requirements triangulation matrix gives the opportunity to look across the results of all used methods and decide what requirements are critical for the system success. Copyright © 2010 Elsevier Ireland Ltd. All rights reserved.

Specialty and Systems Engineering Supplement to IEEE 15288.1

DTIC Science & Technology

2017-08-28

requirements with a space-specific recommended practice. (8) Added Section 3.2.21, Systems Engineering Data Item Descriptions (DIDs...Systems Engineering Data Item Descriptions ........................................................ 17 4. Applicable Documents...and life cycle cost analyses. d. Alternative designs and capabilities of manufacturing are evaluated . e. Long-lead-time items, material source

An Object-Oriented Graphical User Interface for a Reusable Rocket Engine Intelligent Control System

NASA Technical Reports Server (NTRS)

Litt, Jonathan S.; Musgrave, Jeffrey L.; Guo, Ten-Huei; Paxson, Daniel E.; Wong, Edmond; Saus, Joseph R.; Merrill, Walter C.

1994-01-01

An intelligent control system for reusable rocket engines under development at NASA Lewis Research Center requires a graphical user interface to allow observation of the closed-loop system in operation. The simulation testbed consists of a real-time engine simulation computer, a controls computer, and several auxiliary computers for diagnostics and coordination. The system is set up so that the simulation computer could be replaced by the real engine and the change would be transparent to the control system. Because of the hard real-time requirement of the control computer, putting a graphical user interface on it was not an option. Thus, a separate computer used strictly for the graphical user interface was warranted. An object-oriented LISP-based graphical user interface has been developed on a Texas Instruments Explorer 2+ to indicate the condition of the engine to the observer through plots, animation, interactive graphics, and text.

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

NASA Technical Reports Server (NTRS)

Culley, Dennis E.

2011-01-01

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.

Propulsion system tests on a full scale Centaur vehicle to investigate 3-burn mission capability of the D-lT configuration

NASA Technical Reports Server (NTRS)

Groesbeck, W. A.; Baud, K. M.; Lacovic, R. F.; Tabata, W. K.; Szabo, S. V., Jr.

1974-01-01

Propulsion system tests were conducted on a full scale Centaur vehicle to investigate system capability of the proposed D-lT configuration for a three-burn mission. This particular mission profile requires that the engines be capable of restarting and firing for a final maneuver after a 5-1/2-hour coast to synchronous orbit. The thermal conditioning requirements of the engine and propellant feed system components for engine start under these conditions were investigated. Performance data were also obtained on the D-lT type computer controlled propellant tank pressurization system. The test results demonstrated that the RL-10 engines on the Centaur vehicle could be started and run reliably after being thermally conditioned to predicted engine start conditions for a one, two and three burn mission. Investigation of the thermal margins also indicated that engine starts could be accomplished at the maximum predicted component temperature conditions with prestart durations less than planned for flight.

A Mathematical Model of Marine Diesel Engine Speed Control System

NASA Astrophysics Data System (ADS)

Sinha, Rajendra Prasad; Balaji, Rajoo

2018-02-01

Diesel engine is inherently an unstable machine and requires a reliable control system to regulate its speed for safe and efficient operation. Also, the diesel engine may operate at fixed or variable speeds depending upon user's needs and accordingly the speed control system should have essential features to fulfil these requirements. This paper proposes a mathematical model of a marine diesel engine speed control system with droop governing function. The mathematical model includes static and dynamic characteristics of the control loop components. Model of static characteristic of the rotating fly weights speed sensing element provides an insight into the speed droop features of the speed controller. Because of big size and large time delay, the turbo charged diesel engine is represented as a first order system or sometimes even simplified to a pure integrator with constant gain which is considered acceptable in control literature. The proposed model is mathematically less complex and quick to use for preliminary analysis of the diesel engine speed controller performance.

A Theory of Information Quality and a Framework for its Implementation in the Requirements Engineering Process

NASA Astrophysics Data System (ADS)

Grenn, Michael W.

This dissertation introduces a theory of information quality to explain macroscopic behavior observed in the systems engineering process. The theory extends principles of Shannon's mathematical theory of communication [1948] and statistical mechanics to information development processes concerned with the flow, transformation, and meaning of information. The meaning of requirements information in the systems engineering context is estimated or measured in terms of the cumulative requirements quality Q which corresponds to the distribution of the requirements among the available quality levels. The requirements entropy framework (REF) implements the theory to address the requirements engineering problem. The REF defines the relationship between requirements changes, requirements volatility, requirements quality, requirements entropy and uncertainty, and engineering effort. The REF is evaluated via simulation experiments to assess its practical utility as a new method for measuring, monitoring and predicting requirements trends and engineering effort at any given time in the process. The REF treats the requirements engineering process as an open system in which the requirements are discrete information entities that transition from initial states of high entropy, disorder and uncertainty toward the desired state of minimum entropy as engineering effort is input and requirements increase in quality. The distribution of the total number of requirements R among the N discrete quality levels is determined by the number of defined quality attributes accumulated by R at any given time. Quantum statistics are used to estimate the number of possibilities P for arranging R among the available quality levels. The requirements entropy H R is estimated using R, N and P by extending principles of information theory and statistical mechanics to the requirements engineering process. The information I increases as HR and uncertainty decrease, and the change in information AI needed to reach the desired state of quality is estimated from the perspective of the receiver. The HR may increase, decrease or remain steady depending on the degree to which additions, deletions and revisions impact the distribution of R among the quality levels. Current requirements trend metrics generally treat additions, deletions and revisions the same and simply measure the quantity of these changes over time. The REF evaluates the quantity of requirements changes over time, distinguishes between their positive and negative effects by calculating their impact on HR, Q, and AI, and forecasts when the desired state will be reached, enabling more accurate assessment of the status and progress of the requirements engineering effort. Results from random variable simulations suggest the REF is an improved leading indicator of requirements trends that can be readily combined with current methods. The increase in I, or decrease in H R and uncertainty, is proportional to the engineering effort E input into the requirements engineering process. The REF estimates the AE needed to transition R from their current state of quality to the desired end state or some other interim state of interest. Simulation results are compared with measured engineering effort data for Department of Defense programs published in the SE literature, and the results suggest the REF is a promising new method for estimation of AE.

AMTD: Update of Engineering Specifications Derived from Science Requirements for Future UVOIR Space Telescopes

NASA Technical Reports Server (NTRS)

Stahl, H. Philip

2014-01-01

AMTD is using a Science Driven Systems Engineering approach to develop Engineering Specifications based on Science Measurement Requirements and Implementation Constraints. Science requirements meet the needs of both Exoplanet and General Astrophysics science. Engineering Specifications are guiding our effort to mature to TRL-6 the critical technologies needed to produce 4-m or larger flight-qualified UVOIR mirrors by 2018 so that a viable mission can be considered by the 2020 Decadal Review.

Decision Support System Requirements Definition for Human Extravehicular Activity Based on Cognitive Work Analysis

PubMed Central

Miller, Matthew James; McGuire, Kerry M.; Feigh, Karen M.

2016-01-01

The design and adoption of decision support systems within complex work domains is a challenge for cognitive systems engineering (CSE) practitioners, particularly at the onset of project development. This article presents an example of applying CSE techniques to derive design requirements compatible with traditional systems engineering to guide decision support system development. Specifically, it demonstrates the requirements derivation process based on cognitive work analysis for a subset of human spaceflight operations known as extravehicular activity. The results are presented in two phases. First, a work domain analysis revealed a comprehensive set of work functions and constraints that exist in the extravehicular activity work domain. Second, a control task analysis was performed on a subset of the work functions identified by the work domain analysis to articulate the translation of subject matter states of knowledge to high-level decision support system requirements. This work emphasizes an incremental requirements specification process as a critical component of CSE analyses to better situate CSE perspectives within the early phases of traditional systems engineering design. PMID:28491008

Decision Support System Requirements Definition for Human Extravehicular Activity Based on Cognitive Work Analysis.

PubMed

Miller, Matthew James; McGuire, Kerry M; Feigh, Karen M

2017-06-01

The design and adoption of decision support systems within complex work domains is a challenge for cognitive systems engineering (CSE) practitioners, particularly at the onset of project development. This article presents an example of applying CSE techniques to derive design requirements compatible with traditional systems engineering to guide decision support system development. Specifically, it demonstrates the requirements derivation process based on cognitive work analysis for a subset of human spaceflight operations known as extravehicular activity . The results are presented in two phases. First, a work domain analysis revealed a comprehensive set of work functions and constraints that exist in the extravehicular activity work domain. Second, a control task analysis was performed on a subset of the work functions identified by the work domain analysis to articulate the translation of subject matter states of knowledge to high-level decision support system requirements. This work emphasizes an incremental requirements specification process as a critical component of CSE analyses to better situate CSE perspectives within the early phases of traditional systems engineering design.

Engineering Education's Contribution to the Space Program.

ERIC Educational Resources Information Center

Stever, H. Guyford

1988-01-01

States that an expanding future in space requires new technology. Stresses that from engineering education, space requires people with a fundamental knowledge of modern science instruments, all engineering sciences, an appreciation and capability for detail and systems design, and an understanding of costs and competitiveness, machines, materials,…

The effect of requirements prioritization on avionics system conceptual design

NASA Astrophysics Data System (ADS)

Lorentz, John

This dissertation will provide a detailed approach and analysis of a new collaborative requirements prioritization methodology that has been used successfully on four Coast Guard avionics acquisition and development programs valued at $400M+. A statistical representation of participant study results will be discussed and analyzed in detail. Many technically compliant projects fail to deliver levels of performance and capability that the customer desires. Some of these systems completely meet "threshold" levels of performance; however, the distribution of resources in the process devoted to the development and management of the requirements does not always represent the voice of the customer. This is especially true for technically complex projects such as modern avionics systems. A simplified facilitated process for prioritization of system requirements will be described. The collaborative prioritization process, and resulting artifacts, aids the systems engineer during early conceptual design. All requirements are not the same in terms of customer priority. While there is a tendency to have many thresholds inside of a system design, there is usually a subset of requirements and system performance that is of the utmost importance to the design. These critical capabilities and critical levels of performance typically represent the reason the system is being built. The systems engineer needs processes to identify these critical capabilities, the associated desired levels of performance, and the risks associated with the specific requirements that define the critical capability. The facilitated prioritization exercise is designed to collaboratively draw out these critical capabilities and levels of performance so they can be emphasized in system design. Developing the purpose, scheduling and process for prioritization events are key elements of systems engineering and modern project management. The benefits of early collaborative prioritization flow throughout the project schedule, resulting in greater success during system deployment and operational testing. This dissertation will discuss the data and findings from participant studies, present a literature review of systems engineering and design processes, and test the hypothesis that the prioritization process had no effect on stakeholder sentiment related to the conceptual design. In addition, the "Requirements Rationalization" process will be discussed in detail. Avionics, like many other systems, has transitioned from a discrete electronics engineering, hard engineering discipline to incorporate software engineering as a core process of the technology development cycle. As with other software-based systems, avionics now has significant soft system attributes that must be considered in the design process. The boundless opportunities that exist in software design demand prioritization to focus effort onto the critical functions that the software must provide. This has been a well documented and understood phenomenon in the software development community for many years. This dissertation will attempt to link the effect of software integrated avionics to the benefits of prioritization of requirements in the problem space and demonstrate the sociological and technical benefits of early prioritization practices.

Free-piston Stirling hydraulic engine and drive system for automobiles

NASA Technical Reports Server (NTRS)

Beremand, D. G.; Slaby, J. G.; Nussle, R. C.; Miao, D.

1982-01-01

The calculated fuel economy for an automotive free piston Stirling hydraulic engine and drive system using a pneumatic accumulator with the fuel economy of both a conventional 1980 spark ignition engine in an X body class vehicle and the estimated fuel economy of a 1984 spark ignition vehicle system are compared. The results show that the free piston Stirling hydraulic system with a two speed transmission has a combined fuel economy nearly twice that of the 1980 spark ignition engine - 21.5 versus 10.9 km/liter (50.7 versus 25.6 mpg) under comparable conditions. The fuel economy improvement over the 1984 spark ignition engine was 81 percent. The fuel economy sensitivity of the Stirling hydraulic system to system weight, number of transmission shifts, accumulator pressure ratio and maximum pressure, auxiliary power requirements, braking energy recovery, and varying vehicle performance requirements are considered. An important finding is that a multispeed transmission is not required. The penalty for a single speed versus a two speed transmission is about a 12 percent drop in combined fuel economy to 19.0 km/liter (44.7 mpg). This is still a 60 percent improvement in combined fuel economy over the projected 1984 spark ignition vehicle.

Improved Traceability of a Small Satellite Mission Concept to Requirements Using Model Based System Engineering

NASA Technical Reports Server (NTRS)

Reil, Robin L.

2014-01-01

Model Based Systems Engineering (MBSE) has recently been gaining significant support as a means to improve the "traditional" document-based systems engineering (DBSE) approach to engineering complex systems. In the spacecraft design domain, there are many perceived and propose benefits of an MBSE approach, but little analysis has been presented to determine the tangible benefits of such an approach (e.g. time and cost saved, increased product quality). This paper presents direct examples of how developing a small satellite system model can improve traceability of the mission concept to its requirements. A comparison of the processes and approaches for MBSE and DBSE is made using the NASA Ames Research Center SporeSat CubeSat mission as a case study. A model of the SporeSat mission is built using the Systems Modeling Language standard and No Magic's MagicDraw modeling tool. The model incorporates mission concept and requirement information from the mission's original DBSE design efforts. Active dependency relationships are modeled to demonstrate the completeness and consistency of the requirements to the mission concept. Anecdotal information and process-duration metrics are presented for both the MBSE and original DBSE design efforts of SporeSat.

Improved Traceability of Mission Concept to Requirements Using Model Based Systems Engineering

NASA Technical Reports Server (NTRS)

Reil, Robin

2014-01-01

Model Based Systems Engineering (MBSE) has recently been gaining significant support as a means to improve the traditional document-based systems engineering (DBSE) approach to engineering complex systems. In the spacecraft design domain, there are many perceived and propose benefits of an MBSE approach, but little analysis has been presented to determine the tangible benefits of such an approach (e.g. time and cost saved, increased product quality). This thesis presents direct examples of how developing a small satellite system model can improve traceability of the mission concept to its requirements. A comparison of the processes and approaches for MBSE and DBSE is made using the NASA Ames Research Center SporeSat CubeSat mission as a case study. A model of the SporeSat mission is built using the Systems Modeling Language standard and No Magics MagicDraw modeling tool. The model incorporates mission concept and requirement information from the missions original DBSE design efforts. Active dependency relationships are modeled to analyze the completeness and consistency of the requirements to the mission concept. Overall experience and methodology are presented for both the MBSE and original DBSE design efforts of SporeSat.

State Analysis Database Tool

NASA Technical Reports Server (NTRS)

Rasmussen, Robert; Bennett, Matthew

2006-01-01

The State Analysis Database Tool software establishes a productive environment for collaboration among software and system engineers engaged in the development of complex interacting systems. The tool embodies State Analysis, a model-based system engineering methodology founded on a state-based control architecture (see figure). A state represents a momentary condition of an evolving system, and a model may describe how a state evolves and is affected by other states. The State Analysis methodology is a process for capturing system and software requirements in the form of explicit models and states, and defining goal-based operational plans consistent with the models. Requirements, models, and operational concerns have traditionally been documented in a variety of system engineering artifacts that address different aspects of a mission s lifecycle. In State Analysis, requirements, models, and operations information are State Analysis artifacts that are consistent and stored in a State Analysis Database. The tool includes a back-end database, a multi-platform front-end client, and Web-based administrative functions. The tool is structured to prompt an engineer to follow the State Analysis methodology, to encourage state discovery and model description, and to make software requirements and operations plans consistent with model descriptions.

An Assessment Methodology to Evaluate In-Flight Engine Health Management Effectiveness

NASA Astrophysics Data System (ADS)

Maggio, Gaspare; Belyeu, Rebecca; Pelaccio, Dennis G.

2002-01-01

flight effectiveness of candidate engine health management system concepts. A next generation engine health management system will be required to be both reliable and robust in terms of anomaly detection capability. The system must be able to operate successfully in the hostile, high-stress engine system environment. This implies that its system components, such as the instrumentation, process and control, and vehicle interface and support subsystems, must be highly reliable. Additionally, the system must be able to address a vast range of possible engine operation anomalies through a host of different types of measurements supported by a fast algorithm/architecture processing capability that can identify "true" (real) engine operation anomalies. False anomaly condition reports for such a system must be essentially eliminated. The accuracy of identifying only real anomaly conditions has been an issue with the Space Shuttle Main Engine (SSME) in the past. Much improvement in many of the technologies to address these areas is required. The objectives of this study were to identify and demonstrate a consistent assessment methodology that can evaluate the capability of next generation engine health management system concepts to respond in a correct, timely manner to alleviate an operational engine anomaly condition during flight. Science Applications International Corporation (SAIC), with support from NASA Marshall Space Flight Center, identified a probabilistic modeling approach to assess engine health management system concept effectiveness using a deterministic anomaly-time event assessment modeling approach that can be applied in the engine preliminary design stage of development to assess engine health management system concept effectiveness. Much discussion in this paper focuses on the formulation and application approach in performing this assessment. This includes detailed discussion of key modeling assumptions, the overall assessment methodology approach identified, and the identification of key supporting engine health management system concept design/operation and fault mode information required to utilize this methodology. At the paper's conclusion, discussion focuses on a demonstration benchmark study that applied this methodology to the current SSME health management system. A summary of study results and lessons learned are provided. Recommendations for future work in this area are also identified at the conclusion of the paper. * Please direct all correspondence/communication pertaining to this paper to Dennis G. Pelaccio, Science

Combination solar photovoltaic heat engine energy converter

NASA Technical Reports Server (NTRS)

Chubb, Donald L.

1987-01-01

A combination solar photovoltaic heat engine converter is proposed. Such a system is suitable for either terrestrial or space power applications. The combination system has a higher efficiency than either the photovoltaic array or the heat engine alone can attain. Advantages in concentrator and radiator area and receiver mass of the photovoltaic heat engine system over a heat-engine-only system are estimated. A mass and area comparison between the proposed space station organic Rankine power system and a combination PV-heat engine system is made. The critical problem for the proposed converter is the necessity for high temperature photovoltaic array operation. Estimates of the required photovoltaic temperature are presented.

Can IR scene projectors reduce total system cost?

NASA Astrophysics Data System (ADS)

Ginn, Robert; Solomon, Steven

2006-05-01

There is an incredible amount of system engineering involved in turning the typical infrared system needs of probability of detection, probability of identification, and probability of false alarm into focal plane array (FPA) requirements of noise equivalent irradiance (NEI), modulation transfer function (MTF), fixed pattern noise (FPN), and defective pixels. Unfortunately, there are no analytic solutions to this problem so many approximations and plenty of "seat of the pants" engineering is employed. This leads to conservative specifications, which needlessly drive up system costs by increasing system engineering costs, reducing FPA yields, increasing test costs, increasing rework and the never ending renegotiation of requirements in an effort to rein in costs. These issues do not include the added complexity to the FPA factory manager of trying to meet varied, and changing, requirements for similar products because different customers have made different approximations and flown down different specifications. Scene generation technology may well be mature and cost effective enough to generate considerable overall savings for FPA based systems. We will compare the costs and capabilities of various existing scene generation systems and estimate the potential savings if implemented at several locations in the IR system fabrication cycle. The costs of implementing this new testing methodology will be compared to the probable savings in systems engineering, test, rework, yield improvement and others. The diverse requirements and techniques required for testing missile warning systems, missile seekers, and FLIRs will be defined. Last, we will discuss both the hardware and software requirements necessary to meet the new test paradigm and discuss additional cost improvements related to the incorporation of these technologies.

Resilient Propulsion Control Research for the NASA Integrated Resilient Aircraft Control (IRAC) Project

NASA Technical Reports Server (NTRS)

Guo, Ten-Huei; Litt, Jonathan S.

2007-01-01

Gas turbine engines are designed to provide sufficient safety margins to guarantee robust operation with an exceptionally long life. However, engine performance requirements may be drastically altered during abnormal flight conditions or emergency maneuvers. In some situations, the conservative design of the engine control system may not be in the best interest of overall aircraft safety; it may be advantageous to "sacrifice" the engine to "save" the aircraft. Motivated by this opportunity, the NASA Aviation Safety Program is conducting resilient propulsion research aimed at developing adaptive engine control methodologies to operate the engine beyond the normal domain for emergency operations to maximize the possibility of safely landing the damaged aircraft. Previous research studies and field incident reports show that the propulsion system can be an effective tool to help control and eventually land a damaged aircraft. Building upon the flight-proven Propulsion Controlled Aircraft (PCA) experience, this area of research will focus on how engine control systems can improve aircraft safe-landing probabilities under adverse conditions. This paper describes the proposed research topics in Engine System Requirements, Engine Modeling and Simulation, Engine Enhancement Research, Operational Risk Analysis and Modeling, and Integrated Flight and Propulsion Controller Designs that support the overall goal.

40 CFR 92.124 - Test sequence; general requirements.

Code of Federal Regulations, 2012 CFR

2012-07-01

.... (e) Pre-test engine measurements (e.g., idle and throttle notch speeds, fuel flows, etc.), pre-test engine performance checks (e.g., verification of engine power, etc.) and pre-test system calibrations (e... 40 Protection of Environment 21 2012-07-01 2012-07-01 false Test sequence; general requirements...

40 CFR 92.124 - Test sequence; general requirements.

Code of Federal Regulations, 2014 CFR

2014-07-01

.... (e) Pre-test engine measurements (e.g., idle and throttle notch speeds, fuel flows, etc.), pre-test engine performance checks (e.g., verification of engine power, etc.) and pre-test system calibrations (e... 40 Protection of Environment 20 2014-07-01 2013-07-01 true Test sequence; general requirements. 92...

40 CFR 92.124 - Test sequence; general requirements.

Code of Federal Regulations, 2010 CFR

2010-07-01

.... (e) Pre-test engine measurements (e.g., idle and throttle notch speeds, fuel flows, etc.), pre-test engine performance checks (e.g., verification of engine power, etc.) and pre-test system calibrations (e... 40 Protection of Environment 20 2010-07-01 2010-07-01 false Test sequence; general requirements...

40 CFR 92.124 - Test sequence; general requirements.

Code of Federal Regulations, 2013 CFR

2013-07-01

.... (e) Pre-test engine measurements (e.g., idle and throttle notch speeds, fuel flows, etc.), pre-test engine performance checks (e.g., verification of engine power, etc.) and pre-test system calibrations (e... 40 Protection of Environment 21 2013-07-01 2013-07-01 false Test sequence; general requirements...

40 CFR 92.124 - Test sequence; general requirements.

Code of Federal Regulations, 2011 CFR

2011-07-01

.... (e) Pre-test engine measurements (e.g., idle and throttle notch speeds, fuel flows, etc.), pre-test engine performance checks (e.g., verification of engine power, etc.) and pre-test system calibrations (e... 40 Protection of Environment 20 2011-07-01 2011-07-01 false Test sequence; general requirements...

The Ion Propulsion System on NASA's Space Technology 4/Champollion Comet Rendezvous Mission

NASA Technical Reports Server (NTRS)

Brophy, John R.; Garner, Charles E.; Weiss, Jeffery M.

1999-01-01

The ST4/Champollion mission is designed to rendezvous with and land on the comet Tempel 1 and return data from the first-ever sampling of a comet surface. Ion propulsion is an enabling technology for this mission. The ion propulsion system on ST4 consists of three ion engines each essentially identical to the single engine that flew on the DS1 spacecraft. The ST4 propulsion system will operate at a maximum input power of 7.5 kW (3.4 times greater than that demonstrated on DS1), will produce a maximum thrust of 276 mN, and will provide a total (Delta)V of 11.4 km/s. To accomplish this the propulsion system will carry 385 kg of xenon. All three engines will be operated simultaneously for the first 168 days of the mission. The nominal mission requires that each engine be capable of processing 118 kg. If one engine fails after 168 days, the remaining two engines can perform the mission, but must be capable of processing 160 kg of xenon, or twice the original thruster design requirement. Detailed analyses of the thruster wear-out failure modes coupled with experience from long-duration engine tests indicate that the thrusters have a high probability of meeting the 160-kg throughput requirement.

Knowledge-based environment for optical system design

NASA Astrophysics Data System (ADS)

Johnson, R. Barry

1991-01-01

Optical systems are extensively utilized by industry government and military organizations. The conceptual design engineering design fabrication and testing of these systems presently requires significant time typically on the order of 3-5 years. The Knowledge-Based Environment for Optical System Design (KB-OSD) Program has as its principal objectives the development of a methodology and tool(s) that will make a notable reduction in the development time of optical system projects reduce technical risk and overall cost. KB-OSD can be considered as a computer-based optical design associate for system engineers and design engineers. By utilizing artificial intelligence technology coupled with extensive design/evaluation computer application programs and knowledge bases the KB-OSD will provide the user with assistance and guidance to accomplish such activities as (i) develop system level and hardware level requirements from mission requirements (ii) formulate conceptual designs (iii) construct a statement of work for an RFP (iv) develop engineering level designs (v) evaluate an existing design and (vi) explore the sensitivity of a system to changing scenarios. The KB-OSD comprises a variety of computer platforms including a Stardent Titan supercomputer numerous design programs (lens design coating design thermal materials structural atmospherics etc. ) data bases and heuristic knowledge bases. An important element of the KB-OSD Program is the inclusion of the knowledge of individual experts in various areas of optics and optical system engineering. This knowledge is obtained by KB-OSD knowledge engineers performing

Thermal and Environmental Barrier Coatings for Advanced Propulsion Engine Systems

NASA Technical Reports Server (NTRS)

Zhu, Dong-Ming; Miller, Robert A.

2004-01-01

Ceramic thermal and environmental barrier coatings (TEBCs) are used in gas turbine engines to protect engine hot-section components in the harsh combustion environments, and extend component lifetimes. For future high performance engines, the development of advanced ceramic barrier coating systems will allow these coatings to be used to simultaneously increase engine operating temperature and reduce cooling requirements, thereby leading to significant improvements in engine power density and efficiency. In order to meet future engine performance and reliability requirements, the coating systems must be designed with increased high temperature stability, lower thermal conductivity, and improved thermal stress and erosion resistance. In this paper, ceramic coating design and testing considerations will be described for high temperature and high-heat-flux engine applications in hot corrosion and oxidation, erosion, and combustion water vapor environments. Further coating performance and life improvements will be expected by utilizing advanced coating architecture design, composition optimization, and improved processing techniques, in conjunction with modeling and design tools.

Energy efficient engine preliminary design and integration study

NASA Technical Reports Server (NTRS)

Gray, D. E.

1978-01-01

The technology and configurational requirements of an all new 1990's energy efficient turbofan engine having a twin spool arrangement with a directly coupled fan and low-pressure turbine, a mixed exhaust nacelle, and a high 38.6:1 overall pressure ratio were studied. Major advanced technology design features required to provide the overall benefits were a high pressure ratio compression system, a thermally actuated advanced clearance control system, lightweight shroudless fan blades, a low maintenance cost one-stage high pressure turbine, a short efficient mixer and structurally integrated engine and nacelle. A conceptual design analysis was followed by integration and performance analyses of geared and direct-drive fan engines with separate or mixed exhaust nacelles to refine previously designed engine cycles. Preliminary design and more detailed engine-aircraft integration analysis were then conducted on the more promising configurations. Engine and aircraft sizing, fuel burned, and airframe noise studies on projected 1990's domestic and international aircraft produced sufficient definition of configurational and advanced technology requirements to allow immediate initiation of component technology development.

Thermal/structural Tailoring of Engine Blades (T/STAEBL) User's Manual

NASA Technical Reports Server (NTRS)

Brown, K. W.; Clevenger, W. B.; Arel, J. D.

1994-01-01

The Thermal/Structural Tailoring of Engine Blades (T/STAEBL) system is a family of computer programs executed by a control program. The T/STAEBL system performs design optimizations of cooled, hollow turbine blades and vanes. This manual contains an overview of the system, fundamentals of the data block structure, and detailed descriptions of the inputs required by the optimizer. Additionally, the thermal analysis input requirements are described as well as the inputs required to perform a finite element blade vibrations analysis.

Committee on Earth Observation Satellites (CEOS) Systems Engineering Office (SEO). Ocean Surface Topography (OST) Workshop, Ruedesheim an Rhein, Germany. [CEOS SEO Status Report

NASA Technical Reports Server (NTRS)

Killough, Brian D., Jr.

2008-01-01

The CEOS Systems Engineering Office will present a 2007 status report of the CEOS constellation process, present a new systems engineering framework, and analysis results from the GEO Societal Benefit Area (SBA) assessment and the OST constellation requirements assessment.

IDEF3 Formalization Report

DTIC Science & Technology

1991-10-01

SUBJECT TERMS 15. NUMBER OF PAGES engineering management information systems method formalization 60 information engineering process modeling 16 PRICE...CODE information systems requirements definition methods knowlede acquisition methods systems engineering 17. SECURITY CLASSIFICATION ji. SECURITY... Management , Inc., Santa Monica, California. CORYNEN, G. C., 1975, A Mathematical Theory of Modeling and Simula- tion. Ph.D. Dissertation, Department

78 FR 36369 - Heavy-Duty Engine and Vehicle, and Nonroad Technical Amendments

Federal Register 2010, 2011, 2012, 2013, 2014

2013-06-17

... reference to post-transmissions systems in the hybrid engine test requirements in 40 CFR part 1036 and 49... requirements for testing post-transmission hybrids using a vehicle test. The agencies anticipate that there... out in the regulation specify how to test post-transmission systems. Specifically, 40 CFR 1037.525, 40...

ESCORT: A Pratt & Whitney nuclear thermal propulsion and power system for manned mars missions

NASA Astrophysics Data System (ADS)

Feller, Gerald J.; Joyner, Russell

1999-01-01

The purpose of this paper is to describe the conceptual design of an upgrade to the Pratt & Whitney ESCORT nuclear thermal rocket engine. The ESCORT is a bimodal engine capable of supporting a wide range of vehicle propulsive and electrical power requirements. The ESCORT engine is powered by a fast-spectrum beryllium-reflected CERMET-fueled nuclear reactor. In propulsive mode, the reactor is used to heat hot hydrogen to approximately 2700 K which is expanded through a converging/diverging nozzle to generate thrust. Heat pickup in the nozzle and the radial beryllium reflectors is used to drive the turbomachinery in the ESCORT expander cycle. In electrical mode, the reactor is used to heat a mixture of helium and xenon to drive a closed-loop Brayton cycle in order to generate electrical energy. This closed loop system has the additional function of a decay heat removal system after the propulsive mode operation is discontinued. The original ESCORT design was capable of delivering 4448.2 N (1000 lbf) of thrust at a vacuum impulse level of approximately 900 s. Design Reference Mission requirements (DRM) from NASA Johnson Space Center and NASA Lewis Research Center studies in 1997 and 1998 have detailed upgraded requirements for potential manned Mars missions. The current NASA DRM requires a nuclear thermal propulsion system capable of delivering total mission requirements of 200170 N (45000 lbf) thrust and 50 kWe of spacecraft electrical power. This is met assuming three engines capable of each delivering 66723 N (15000 lbf) of vacuum thrust and 25 kWe of electrical power. The individual engine requirements were developed assuming three out of three engine reliability for propulsion and two out of three engine reliability for spacecraft electrical power. The approximate target vacuum impulse is 925 s. The Pratt & Whitney ESCORT concept was upgraded to meet these requirements. The hexagonal prismatic fuel elements were modified to address the uprated power requirements while maintaining the peak fuel temperature below the 2880 K limit for W-UO2 CERMET fuels. A system integrated performance methodology was developed to assess the sensitivity to weight, thrust and impulse to the DRM requirements. Propellant tanks, shielding, and Brayton cycle power conversion unit requirements were included in this evaluation.

48 CFR 2936.602 - Selection of firms for architect-engineer contracts.

Code of Federal Regulations, 2011 CFR

2011-10-01

... architect-engineer contracts. 2936.602 Section 2936.602 Federal Acquisition Regulations System DEPARTMENT OF LABOR GENERAL CONTRACTING REQUIREMENTS CONSTRUCTION AND ARCHITECT-ENGINEER CONTRACTS Architect-Engineer Services 2936.602 Selection of firms for architect-engineer contracts. ...

48 CFR 2936.602 - Selection of firms for architect-engineer contracts.

Code of Federal Regulations, 2014 CFR

2014-10-01

... architect-engineer contracts. 2936.602 Section 2936.602 Federal Acquisition Regulations System DEPARTMENT OF LABOR GENERAL CONTRACTING REQUIREMENTS CONSTRUCTION AND ARCHITECT-ENGINEER CONTRACTS Architect-Engineer Services 2936.602 Selection of firms for architect-engineer contracts. ...

48 CFR 2936.602 - Selection of firms for architect-engineer contracts.

Code of Federal Regulations, 2010 CFR

2010-10-01

... architect-engineer contracts. 2936.602 Section 2936.602 Federal Acquisition Regulations System DEPARTMENT OF LABOR GENERAL CONTRACTING REQUIREMENTS CONSTRUCTION AND ARCHITECT-ENGINEER CONTRACTS Architect-Engineer Services 2936.602 Selection of firms for architect-engineer contracts. ...

48 CFR 2936.602 - Selection of firms for architect-engineer contracts.

Code of Federal Regulations, 2013 CFR

2013-10-01

... architect-engineer contracts. 2936.602 Section 2936.602 Federal Acquisition Regulations System DEPARTMENT OF LABOR GENERAL CONTRACTING REQUIREMENTS CONSTRUCTION AND ARCHITECT-ENGINEER CONTRACTS Architect-Engineer Services 2936.602 Selection of firms for architect-engineer contracts. ...

48 CFR 2936.602 - Selection of firms for architect-engineer contracts.

Code of Federal Regulations, 2012 CFR

2012-10-01

... architect-engineer contracts. 2936.602 Section 2936.602 Federal Acquisition Regulations System DEPARTMENT OF LABOR GENERAL CONTRACTING REQUIREMENTS CONSTRUCTION AND ARCHITECT-ENGINEER CONTRACTS Architect-Engineer Services 2936.602 Selection of firms for architect-engineer contracts. ...

Oil cooling system for a gas turbine engine

NASA Technical Reports Server (NTRS)

Coffinberry, G. A.; Kast, H. B. (Inventor)

1977-01-01

A gas turbine engine fuel delivery and control system is provided with means to recirculate all fuel in excess of fuel control requirements back to aircraft fuel tank, thereby increasing the fuel pump heat sink and decreasing the pump temperature rise without the addition of valving other than that normally employed. A fuel/oil heat exchanger and associated circuitry is provided to maintain the hot engine oil in heat exchange relationship with the cool engine fuel. Where anti-icing of the fuel filter is required, means are provided to maintain the fuel temperature entering the filter at or above a minimum level to prevent freezing thereof. Fluid circuitry is provided to route hot engine oil through a plurality of heat exchangers disposed within the system to provide for selective cooling of the oil.

Space Station engineering and technology development

NASA Technical Reports Server (NTRS)

1985-01-01

Historical background, costs, organizational assignments, technology development, user requirements, mission evolution, systems analyses and design, systems engineering and integration, contracting, and policies of the space station are discussed.

Early Engagement of Safety and Mission Assurance Expertise Using Systems Engineering Tools: A Risk-Based Approach to Early Identification of Safety and Assurance Requirements

NASA Technical Reports Server (NTRS)

Darpel, Scott; Beckman, Sean

2016-01-01

Decades of systems engineering practice have demonstrated that the earlier the identification of requirements occurs, the lower the chance that costly redesigns will needed later in the project life cycle. A better understanding of all requirements can also improve the likelihood of a design's success. Significant effort has been put into developing tools and practices that facilitate requirements determination, including those that are part of the model-based systems engineering (MBSE) paradigm. These efforts have yielded improvements in requirements definition, but have thus far focused on a design's performance needs. The identification of safety & mission assurance (S&MA) related requirements, in comparison, can occur after preliminary designs are already established, yielding forced redesigns. Engaging S&MA expertise at an earlier stage, facilitated by the use of MBSE tools, and focused on actual project risk, can yield the same type of design life cycle improvements that have been realized in technical and performance requirements.

Complex Adaptive Systems of Systems (CASoS) engineering and foundations for global design.

DOE Office of Scientific and Technical Information (OSTI.GOV)

Brodsky, Nancy S.; Finley, Patrick D.; Beyeler, Walter Eugene

2012-01-01

Complex Adaptive Systems of Systems, or CASoS, are vastly complex ecological, sociological, economic and/or technical systems which must be recognized and reckoned with to design a secure future for the nation and the world. Design within CASoS requires the fostering of a new discipline, CASoS Engineering, and the building of capability to support it. Towards this primary objective, we created the Phoenix Pilot as a crucible from which systemization of the new discipline could emerge. Using a wide range of applications, Phoenix has begun building both theoretical foundations and capability for: the integration of Applications to continuously build common understandingmore » and capability; a Framework for defining problems, designing and testing solutions, and actualizing these solutions within the CASoS of interest; and an engineering Environment required for 'the doing' of CASoS Engineering. In a secondary objective, we applied CASoS Engineering principles to begin to build a foundation for design in context of Global CASoS« less

Systems Engineering of Electric and Hybrid Vehicles

NASA Technical Reports Server (NTRS)

Kurtz, D. W.; Levin, R. R.

1986-01-01

Technical paper notes systems engineering principles applied to development of electric and hybrid vehicles such that system performance requirements support overall program goal of reduced petroleum consumption. Paper discusses iterative design approach dictated by systems analyses. In addition to obvious peformance parameters of range, acceleration rate, and energy consumption, systems engineering also considers such major factors as cost, safety, reliability, comfort, necessary supporting infrastructure, and availability of materials.

14 CFR 23.1195 - Fire extinguishing systems.

Code of Federal Regulations, 2013 CFR

2013-01-01

..., and the discharge distribution must be adequate to extinguish fires. An individual “one shot” system may be used, except for engine(s) embedded in the fuselage, where a “two shot” system is required. (3...

14 CFR 23.1195 - Fire extinguishing systems.

Code of Federal Regulations, 2014 CFR

2014-01-01

..., and the discharge distribution must be adequate to extinguish fires. An individual “one shot” system may be used, except for engine(s) embedded in the fuselage, where a “two shot” system is required. (3...

Computer-Aided Software Engineering - An approach to real-time software development

NASA Technical Reports Server (NTRS)

Walker, Carrie K.; Turkovich, John J.

1989-01-01

A new software engineering discipline is Computer-Aided Software Engineering (CASE), a technology aimed at automating the software development process. This paper explores the development of CASE technology, particularly in the area of real-time/scientific/engineering software, and a history of CASE is given. The proposed software development environment for the Advanced Launch System (ALS CASE) is described as an example of an advanced software development system for real-time/scientific/engineering (RT/SE) software. The Automated Programming Subsystem of ALS CASE automatically generates executable code and corresponding documentation from a suitably formatted specification of the software requirements. Software requirements are interactively specified in the form of engineering block diagrams. Several demonstrations of the Automated Programming Subsystem are discussed.

Rotorcraft convertible engine study

NASA Technical Reports Server (NTRS)

Gill, J. C.; Earle, R. V.; Mar, H. M.

1982-01-01

The objective of the Rotorcraft Convertible Engine Study was to define future research and technology effort required for commercial development by 1988 of convertible fan/shaft gas turbine engines for unconventional rotorcraft transports. Two rotorcraft and their respective missions were defined: a Fold Tilt Rotor aircraft and an Advancing Blade Concept (ABC) rotorcraft. Sensitivity studies were conducted with these rotorcraft to determine parametrically the influence of propulsion characteristics on aircraft size, mission fuel requirements, and direct operating costs (DOC). The two rotorcraft were flown with conventional propulsion systems (separate lift/cruise engines) and with convertible propulsion systems to determine the benefits to be derived from convertible engines. Trade-off studies were conducted to determine the optimum engine cycle and staging arrangement for a convertible engine. Advanced technology options applicable to convertible engines were studied. Research and technology programs were identified which would ensure technology readiness for commercial development of convertible engines by 1988.

Gas Turbine Characteristics for a Large Civil Tilt-Rotor (LCTR)

NASA Technical Reports Server (NTRS)

Snyder, Christopher A.; Thurman, Douglas R.

2010-01-01

In support of the Fundamental Aeronautics Program, Subsonic Rotary Wing Project; an engine system study has been undertaken to help define and understand some of the major gas turbine engine parameters required to meet performance and weight requirements as defined by earlier vehicle system studies. These previous vehicle studies will be reviewed to help define gas turbine performance goals. Assumptions and analysis methods used will be described. Performance and weight estimates for a few conceptual gas turbine engines meeting these requirements will be given and discussed. Estimated performance for these conceptual engines over a wide speed variation (down to 50 percent power turbine rpm at high torque) will be presented. Finally, areas needing further effort will be suggested and discussed.

Requirements analysis notebook for the flight data systems definition in the Real-Time Systems Engineering Laboratory (RSEL)

NASA Astrophysics Data System (ADS)

Wray, Richard B.

1991-12-01

A hybrid requirements analysis methodology was developed, based on the practices actually used in developing a Space Generic Open Avionics Architecture. During the development of this avionics architecture, a method of analysis able to effectively define the requirements for this space avionics architecture was developed. In this methodology, external interfaces and relationships are defined, a static analysis resulting in a static avionics model was developed, operating concepts for simulating the requirements were put together, and a dynamic analysis of the execution needs for the dynamic model operation was planned. The systems engineering approach was used to perform a top down modified structured analysis of a generic space avionics system and to convert actual program results into generic requirements. CASE tools were used to model the analyzed system and automatically generate specifications describing the model's requirements. Lessons learned in the use of CASE tools, the architecture, and the design of the Space Generic Avionics model were established, and a methodology notebook was prepared for NASA. The weaknesses of standard real-time methodologies for practicing systems engineering, such as Structured Analysis and Object Oriented Analysis, were identified.

Requirements analysis notebook for the flight data systems definition in the Real-Time Systems Engineering Laboratory (RSEL)

NASA Technical Reports Server (NTRS)

Wray, Richard B.

1991-01-01

A hybrid requirements analysis methodology was developed, based on the practices actually used in developing a Space Generic Open Avionics Architecture. During the development of this avionics architecture, a method of analysis able to effectively define the requirements for this space avionics architecture was developed. In this methodology, external interfaces and relationships are defined, a static analysis resulting in a static avionics model was developed, operating concepts for simulating the requirements were put together, and a dynamic analysis of the execution needs for the dynamic model operation was planned. The systems engineering approach was used to perform a top down modified structured analysis of a generic space avionics system and to convert actual program results into generic requirements. CASE tools were used to model the analyzed system and automatically generate specifications describing the model's requirements. Lessons learned in the use of CASE tools, the architecture, and the design of the Space Generic Avionics model were established, and a methodology notebook was prepared for NASA. The weaknesses of standard real-time methodologies for practicing systems engineering, such as Structured Analysis and Object Oriented Analysis, were identified.

TARGET's role in knowledge acquisition, engineering, validation, and documentation

NASA Technical Reports Server (NTRS)

Levi, Keith R.

1994-01-01

We investigate the use of the TARGET task analysis tool for use in the development of rule-based expert systems. We found TARGET to be very helpful in the knowledge acquisition process. It enabled us to perform knowledge acquisition with one knowledge engineer rather than two. In addition, it improved communication between the domain expert and knowledge engineer. We also found it to be useful for both the rule development and refinement phases of the knowledge engineering process. Using the network in these phases required us to develop guidelines that enabled us to easily translate the network into production rules. A significant requirement for TARGET remaining useful throughout the knowledge engineering process was the need to carefully maintain consistency between the network and the rule representations. Maintaining consistency not only benefited the knowledge engineering process, but also has significant payoffs in the areas of validation of the expert system and documentation of the knowledge in the system.

Combined Heat and Power Systems Technology Development and Demonstration 370 kW High Efficiency Microturbine

DOE Office of Scientific and Technical Information (OSTI.GOV)

none,

The C370 Program was awarded in October 2010 with the ambitious goal of designing and testing the most electrically efficient recuperated microturbine engine at a rated power of less than 500 kW. The aggressive targets for electrical efficiency, emission regulatory compliance, and the estimated price point make the system state-of-the-art for microturbine engine systems. These goals will be met by designing a two stage microturbine engine identified as the low pressure spool and high pressure spool that are based on derivative hardware of Capstone’s current commercially available engines. The development and testing of the engine occurred in two phases. Phasemore » I focused on developing a higher power and more efficient engine, that would become the low pressure spool which is based on Capstone’s C200 (200kW) engine architecture. Phase II integrated the low pressure spool created in Phase I with the high pressure spool, which is based on Capstone’s C65 (65 kW) commercially available engine. Integration of the engines, based on preliminary research, would allow the dual spool engine to provide electrical power in excess of 370 kW, with electrical efficiency approaching 42%. If both of these targets were met coupled with the overall CHP target of 85% total combined heating and electrical efficiency California Air Resources Board (CARB) level emissions, and a price target of $600 per kW, the system would represent a step change in the currently available commercial generation technology. Phase I of the C370 program required the development of the C370 low pressure spool. The goal was to increase the C200 engine power by a minimum of 25% — 250 kW — and efficiency from 32% to 37%. These increases in the C200 engine output were imperative to meet the power requirements of the engine when both spools were integrated. An additional benefit of designing and testing the C370 low pressure spool was the possibility of developing a stand-alone product for possible commercialization. The low pressure spool design activity focused on an aeropath derivative of the current C200 engine. The aeropath derivative included changes to the compressor section —compressor and inducer — and to the turbine nozzle. The increased power also necessitated a larger, more powerful generator and generator controller to support the increased power requirements. These two major design changes were completed by utilizing both advanced 3D modeling and computational fluid dynamics modelling. After design, modeling, and analysis, the decision was made to acquire and integrate the components for testing. The second task of Phase I was to integrate and test the components of the low pressure spool to validate power and efficiency. Acquisition of the components for the low pressure spool was completed utilizing Capstone’s current supplier base. Utilization of Capstone’s supply base for integration of the test article would allow — if the decision was made —expedited commercialization of the product. After integration of the engine components, the engine was tested and evaluated for performance and emissions. Test data analysis confirmed that the engine met all power and efficiency requirements and did so while maintaining CARB level emissions. The emissions were met without the use of any post processing or catalyst. After testing was completed, the DOE authorized — via a milestone review — proceeding to Phase II: the development of the integrated C370 engine. The C370 high pressure spool design activity required significant changes to the C65 engine architecture. The engine required a high power density generator, completely redesigned compressor stage, turbine section, recuperator, controls architecture, and intercooler stage asThe two most critical design challenges were the turbine section (the nozzle and turbine) and the controls architecture. The design and analysis of all of the components was completed and integrated into a system model. The system model — after numerous iterations — indicated that, once integrated, the engine will meet or exceed all system requirements. Unfortunately, the turbine section’s life requirements remain a technical challenge and will require continued refinement of the bi-metallic turbine wheel design and manufacturing approach to meet the life requirement at theses high temperatures. The current controls architecture requires substantial effort to develop a system capable of handling the high-speed, near real-time controls requirement, but it was determined not to be a technical roadblock for the project. The C370 Program has been a significant effort with state-of-the-art technical targets. The targets have pushed Capstone’s designers to the limits of current technology. The program has been fortunate to see many successes: the successful testing of the low pressure spool (C250), the development of new material processes, and the implementation of new design practices. The technology and practices learned during the program will be utilized in Capstone’s current product lines and future products. The C370 Program has been a resounding success on many fronts for the DOE and for Capstone.« less

Lightweight two-stroke cycle aircraft diesel engine technology enablement program, volume 1

NASA Technical Reports Server (NTRS)

Freen, P. D.; Berenyi, S. G.; Brouwers, A. P.; Moynihan, M. E.

1985-01-01

An experimental Single Cylinder Test Engine Program is conducted to confirm the analytically projected performance of a two-stroke cycle diesel engine for aircraft applications. The test engine delivered 78kW indicated power from 1007cc displacement, operating at 3500 RPM on Schnuerle loop scavenged two-stroke cycle. Testing confirms the ability of a proposed 4-cylinder version of such an engine to reach the target power at altitude, in a highly turbocharged configuration. The experimental program defines all necessary parameters to permit design of a multicylinder engine for eventual flight applications; including injection system requirement, turbocharging, heat rejection, breathing, scavenging, and structural requirements. The multicylinder engine concept is configured to operate with an augmented turbocharger, but with no primary scavenge blower. The test program is oriented to provide a balanced turbocharger compressor to turbine power balance without an auxiliary scavenging system. Engine cylinder heat rejection to the ambient air has been significantly reduced and the minimum overall turbocharger efficiency required is within the range of commercially available turbochargers. Analytical studies and finite element modeling is made of insulated configurations of the engines - including both ceramic and metallic versions. A second generation test engine is designed based on current test results.

Preface to RIGiM 2009

NASA Astrophysics Data System (ADS)

Rolland, Colette; Yu, Eric; Salinesi, Camille; Castro, Jaelson

The use of intentional concepts, the notion of "goal" in particular, has been prominent in recent approaches to requirement engineering (RE). Goal-oriented frameworks and methods for requirements engineering (GORE) have been keynote topics in requirements engineering, conceptual modelling, and more generally in software engineering. What are the conceptual modelling foundations in these approaches? RIGiM (Requirements Intentions and Goals in Conceptual Modelling) aims to provide a forum for discussing the interplay between requirements engineering and conceptual modelling, and in particular, to investigate how goal- and intention-driven approaches help in conceptualising purposeful systems. What are the fundamental objectives and premises of requirements engineering and conceptual modelling respectively, and how can they complement each other? What are the demands on conceptual modelling from the standpoint of requirements engineering? What conceptual modelling techniques can be further taken advantage of in requirements engineering? What are the upcoming modelling challenges and issues in GORE? What are the unresolved open questions? What lessons are there to be learnt from industrial experiences? What empirical data are there to support the cost-benefit analysis when adopting GORE methods? Are there application domains or types of project settings for which goals and intentional approaches are particularly suitable or not suitable? What degree of formalization and automation, or interactivity is feasible and appropriate for what types of participants during requirements engineering?

Orbital transfer rocket engine technology 7.5K-LB thrust rocket engine preliminary design

NASA Technical Reports Server (NTRS)

Harmon, T. J.; Roschak, E.

1993-01-01

A preliminary design of an advanced LOX/LH2 expander cycle rocket engine producing 7,500 lbf thrust for Orbital Transfer vehicle missions was completed. Engine system, component and turbomachinery analysis at both on design and off design conditions were completed. The preliminary design analysis results showed engine requirements and performance goals were met. Computer models are described and model outputs are presented. Engine system assembly layouts, component layouts and valve and control system analysis are presented. Major design technologies were identified and remaining issues and concerns were listed.

Progress toward an advanced condition monitoring system for reusable rocket engines

NASA Technical Reports Server (NTRS)

Maram, J.; Barkhoudarian, S.

1987-01-01

A new generation of advanced sensor technologies will allow the direct measurement of critical/degradable rocket engine components' health and the detection of degraded conditions before component deterioration affects engine performance, leading to substantial improvements in reusable engines' operation and maintenance. When combined with a computer-based engine condition-monitoring system, these sensors can furnish a continuously updated data base for the prediction of engine availability and advanced warning of emergent maintenance requirements. Attention is given to the case of a practical turbopump and combustion device diagnostic/prognostic health-monitoring system.

Systems engineering for very large systems

NASA Technical Reports Server (NTRS)

Lewkowicz, Paul E.

1993-01-01

Very large integrated systems have always posed special problems for engineers. Whether they are power generation systems, computer networks or space vehicles, whenever there are multiple interfaces, complex technologies or just demanding customers, the challenges are unique. 'Systems engineering' has evolved as a discipline in order to meet these challenges by providing a structured, top-down design and development methodology for the engineer. This paper attempts to define the general class of problems requiring the complete systems engineering treatment and to show how systems engineering can be utilized to improve customer satisfaction and profit ability. Specifically, this work will focus on a design methodology for the largest of systems, not necessarily in terms of physical size, but in terms of complexity and interconnectivity.

Systems engineering for very large systems

NASA Astrophysics Data System (ADS)

Lewkowicz, Paul E.

Very large integrated systems have always posed special problems for engineers. Whether they are power generation systems, computer networks or space vehicles, whenever there are multiple interfaces, complex technologies or just demanding customers, the challenges are unique. 'Systems engineering' has evolved as a discipline in order to meet these challenges by providing a structured, top-down design and development methodology for the engineer. This paper attempts to define the general class of problems requiring the complete systems engineering treatment and to show how systems engineering can be utilized to improve customer satisfaction and profit ability. Specifically, this work will focus on a design methodology for the largest of systems, not necessarily in terms of physical size, but in terms of complexity and interconnectivity.

40 CFR 1045.120 - What emission-related warranty requirements apply to me?

Code of Federal Regulations, 2014 CFR

2014-07-01

... (CONTINUED) AIR POLLUTION CONTROLS CONTROL OF EMISSIONS FROM SPARK-IGNITION PROPULSION MARINE ENGINES AND... purchaser that the new engine, including all parts of its emission control system, meets two conditions: (1... generous than we require. The emission-related warranty for an engine may not be shorter than any published...

Magnetohydrodynamics (MHD) Engineering Test Facility (ETF) 200 MWe power plant. Design Requirements Document (DRD)

NASA Technical Reports Server (NTRS)

Rigo, H. S.; Bercaw, R. W.; Burkhart, J. A.; Mroz, T. S.; Bents, D. J.; Hatch, A. M.

1981-01-01

A description and the design requirements for the 200 MWe (nominal) net output MHD Engineering Test Facility (ETF) Conceptual Design, are presented. Performance requirements for the plant are identified and process conditions are indicated at interface stations between the major systems comprising the plant. Also included are the description, functions, interfaces and requirements for each of these major systems. The lastest information (1980-1981) from the MHD technology program are integrated with elements of a conventional steam electric power generating plant.

Performance characteristics of a combination solar photovoltaic heat engine energy converter

NASA Technical Reports Server (NTRS)

Chubb, Donald L.

1987-01-01

A combination solar photovoltaic heat engine converter is proposed. Such a system is suitable for either terrestrial or space power applications. The combination system has a higher efficiency than either the photovoltaic array or the heat engine alone can attain. Advantages in concentrator and radiator area and receiver mass of the photovoltaic heat engine system over a heat-engine-only system are estimated. A mass and area comparison between the proposed space station organic Rankine power system and a combination PV-heat engine system is made. The critical problem for the proposed converter is the necessity for high temperature photovoltaic array operation. Estimates of the required photovoltaic temperature are presented.

Energy Efficient Engine combustor test hardware detailed design report

NASA Technical Reports Server (NTRS)

Burrus, D. L.; Chahrour, C. A.; Foltz, H. L.; Sabla, P. E.; Seto, S. P.; Taylor, J. R.

1984-01-01

The Energy Efficient Engine (E3) Combustor Development effort was conducted as part of the overall NASA/GE E3 Program. This effort included the selection of an advanced double-annular combustion system design. The primary intent was to evolve a design which meets the stringent emissions and life goals of the E3 as well as all of the usual performance requirements of combustion systems for modern turbofan engines. Numerous detailed design studies were conducted to define the features of the combustion system design. Development test hardware was fabricated, and an extensive testing effort was undertaken to evaluate the combustion system subcomponents in order to verify and refine the design. Technology derived from this development effort will be incorporated into the engine combustion system hardware design. This advanced engine combustion system will then be evaluated in component testing to verify the design intent. What is evolving from this development effort is an advanced combustion system capable of satisfying all of the combustion system design objectives and requirements of the E3. Fuel nozzle, diffuser, starting, and emissions design studies are discussed.

SysML: A Language for Space System Engineering

NASA Astrophysics Data System (ADS)

Mazzini, S.; Strangapede, A.

2008-08-01

This paper presents the results of an ESA/ESTEC internal study, performed with the support of INTECS, about modeling languages to support Space System Engineering activities and processes, with special emphasis on system requirements identification and analysis. The study was focused on the assessment of dedicated UML profiles, their positioning alongside the system and software life cycles and associated methodologies. Requirements for a Space System Requirements Language were identified considering the ECSS-E-10 and ECSS-E_40 processes. The study has identified SysML as a very promising language, having as theoretical background the reference system processes defined by the ISO15288, as well as industrial practices.

Energy Efficient Engine: Control system preliminary definition report

NASA Technical Reports Server (NTRS)

Howe, David C.

1986-01-01

The object of the Control Preliminary Definition Program was to define a preliminary control system concept as a part of the Energy Efficient Engine program. The program was limited to a conceptual definition of a full authority digital electronic control system. System requirements were determined and a control system was conceptually defined to these requirements. Areas requiring technological development were identified and a plan was established for implementing the identified technological features, including a control technology demonstration. A significant element of this program was a study of the potential benefits of closed-loop active clearance control, along with laboratory tests of candidate clearance sensor elements for a closed loop system.

Integrating MBSE into Ongoing Projects: Requirements Validation and Test Planning for the ISS SAFER

NASA Technical Reports Server (NTRS)

Anderson, Herbert A.; Williams, Antony; Pierce, Gregory

2016-01-01

The International Space Station (ISS) Simplified Aid for Extra Vehicular Activity (EVA) Rescue (SAFER) is the spacewalking astronaut's final safety measure against separating from the ISS and being unable to return safely. Since the late 1990s, the SAFER has been a standard element of the spacewalking astronaut's equipment. The ISS SAFER project was chartered to develop a new block of SAFER units using a highly similar design to the legacy SAFER (known as the USA SAFER). An on-orbit test module was also included in the project to enable periodic maintenance/propulsion system checkout on the ISS SAFER. On the ISS SAFER project, model-based systems engineering (MBSE) was not the initial systems engineering (SE) approach, given the volume of heritage systems engineering and integration (SE&I) products. The initial emphasis was ensuring traceability to ISS program standards as well as to legacy USA SAFER requirements. The requirements management capabilities of the Cradle systems engineering tool were to be utilized to that end. During development, however, MBSE approaches were applied selectively to address specific challenges in requirements validation and test and verification (T&V) planning, which provided measurable efficiencies to the project. From an MBSE perspective, ISS SAFER development presented a challenge and an opportunity. Addressing the challenge first, the project was tasked to use the original USA SAFER operational and design requirements baseline, with a number of additional ISS program requirements to address evolving certification expectations for systems operating on the ISS. Additionally, a need to redesign the ISS SAFER avionics architecture resulted in a set of changes to the design requirements baseline. Finally, the project added an entirely new functionality for on-orbit maintenance. After initial requirements integration, the system requirements count was approaching 1000, which represented a growth of 4x over the original USA SAFER system. This presented the challenge - How to confirm that this new set of requirements set would result in the creation of the desired capability.

Combustion performance and heat transfer characterization of LOX/hydrocarbon type propellants. Task 3: Data dump

NASA Technical Reports Server (NTRS)

Hart, S. W.

1982-01-01

A preliminary characterization of Orbital Maneuvering System (OMS) and Reaction Control System (RCS) engine point designs over a range of thrust and chamber pressure for several hydrocarbon fuels is reported. OMS and RCS engine point designs were established in two phases comprising baseline and parametric designs. Interface pressures, performance and operating parameters, combustion chamber cooling and turboprop requirements, component weights and envelopes, and propellant conditioning requirements for liquid to vapor phase engine operation are defined.

Expanded Guidance for NASA Systems Engineering. Volume 1: Systems Engineering Practices

NASA Technical Reports Server (NTRS)

Hirshorn, Steven R.

2016-01-01

This document is intended to provide general guidance and information on systems engineering that will be useful to the NASA community. It provides a generic description of Systems Engineering (SE) as it should be applied throughout NASA. A goal of the expanded guidance is to increase awareness and consistency across the Agency and advance the practice of SE. This guidance provides perspectives relevant to NASA and data particular to NASA. This expanded guidance should be used as a companion for implementing NPR 7123.1, Systems Engineering Processes and Requirements, the Rev 2 version of SP-6105, and the Center-specific handbooks and directives developed for implementing systems engineering at NASA. It provides a companion reference book for the various systems engineering-related training being offered under NASA's auspices.

System engineering of the Atacama Large Millimeter/submillimeter Array

NASA Astrophysics Data System (ADS)

Bhatia, Ravinder; Marti, Javier; Sugimoto, Masahiro; Sramek, Richard; Miccolis, Maurizio; Morita, Koh-Ichiro; Arancibia, Demián.; Araya, Andrea; Asayama, Shin'ichiro; Barkats, Denis; Brito, Rodrigo; Brundage, William; Grammer, Wes; Haupt, Christoph; Kurlandczyk, Herve; Mizuno, Norikazu; Napier, Peter; Pizarro, Eduardo; Saini, Kamaljeet; Stahlman, Gretchen; Verzichelli, Gianluca; Whyborn, Nick; Yagoubov, Pavel

2012-09-01

The Atacama Large Millimeter/submillimeter Array (ALMA) will be composed of 66 high precision antennae located at 5000 meters altitude in northern Chile. This paper will present the methodology, tools and processes adopted to system engineer a project of high technical complexity, by system engineering teams that are remotely located and from different cultures, and in accordance with a demanding schedule and within tight financial constraints. The technical and organizational complexity of ALMA requires a disciplined approach to the definition, implementation and verification of the ALMA requirements. During the development phase, System Engineering chairs all technical reviews and facilitates the resolution of technical conflicts. We have developed analysis tools to analyze the system performance, incorporating key parameters that contribute to the ultimate performance, and are modeled using best estimates and/or measured values obtained during test campaigns. Strict tracking and control of the technical budgets ensures that the different parts of the system can operate together as a whole within ALMA boundary conditions. System Engineering is responsible for acceptances of the thousands of hardware items delivered to Chile, and also supports the software acceptance process. In addition, System Engineering leads the troubleshooting efforts during testing phases of the construction project. Finally, the team is conducting System level verification and diagnostics activities to assess the overall performance of the observatory. This paper will also share lessons learned from these system engineering and verification approaches.

Advanced Propulsion System Studies for General Aviation Aircraft

NASA Technical Reports Server (NTRS)

Eisenberg, Joseph D. (Technical Monitor); German, Jon

2003-01-01

This final report addresses the following topics: Market Impact Analysis (1) assessment of general aviation, including commuter/regional, aircraft market impact due to incorporation of advanced technology propulsion system on acquisition and operating costs, job creation and/or manpower demand, and future fleet size; (2) selecting an aircraft and engine for the study by focusing on the next generation 19-passenger commuter and the Williams International FJ44 turbofan engine growth. Propulsion System Analysis Conducted mission analysis studies and engine cycle analysis to define a new commuter mission and required engine performance, define acquisition and operating costs and, select engine configuration and initiated preliminary design for hardware modifications required. Propulsion System Benefits (1) assessed and defined engine emissions improvements, (2) assessed and defined noise reduction potential and, (3) conducted a cost analysis impact study. Review of Relevant NASA Programs Conducted literature searches using NERAC and NASA RECON services for related technology in the emissions and acoustics area. Preliminary Technology Development Plans Defined plan to incorporate technology improvements for an FJ44-2 growth engine in performance, emissions, and noise suppression.

30 CFR 36.48 - Tests of surface temperature of engine and components of the cooling system.

Code of Federal Regulations, 2011 CFR

2011-07-01

... with the engine operated as prescribed by MSHA. All parts of the engine, cooling system, and other... components of the cooling system. 36.48 Section 36.48 Mineral Resources MINE SAFETY AND HEALTH ADMINISTRATION... PERMISSIBLE MOBILE DIESEL-POWERED TRANSPORTATION EQUIPMENT Test Requirements § 36.48 Tests of surface...

30 CFR 36.48 - Tests of surface temperature of engine and components of the cooling system.

Code of Federal Regulations, 2010 CFR

2010-07-01

... with the engine operated as prescribed by MSHA. All parts of the engine, cooling system, and other... components of the cooling system. 36.48 Section 36.48 Mineral Resources MINE SAFETY AND HEALTH ADMINISTRATION... PERMISSIBLE MOBILE DIESEL-POWERED TRANSPORTATION EQUIPMENT Test Requirements § 36.48 Tests of surface...

Physiological Investigation of Localized Temperature Effects on Vigilance Performance

DTIC Science & Technology

2014-03-27

Department of Systems Engineering Graduate School of Engineering and Management Air Force Institute of Technology Air University Air Education and...Training Command In Partial Fulfillment of the Requirements for the Degree of Master of Science in Systems Engineering Justine D. Jeroski, BS...electrodes (right). ...................................................... 14 Figure A 3. BIOPAC © hardware system showing placement of ECG

Materials, Processes and Manufacturing in Ares 1 Upper Stage: Integration with Systems Design and Development

NASA Technical Reports Server (NTRS)

Bhat, Biliyar N.

2008-01-01

Ares I Crew Launch Vehicle Upper Stage is designed and developed based on sound systems engineering principles. Systems Engineering starts with Concept of Operations and Mission requirements, which in turn determine the launch system architecture and its performance requirements. The Ares I-Upper Stage is designed and developed to meet these requirements. Designers depend on the support from materials, processes and manufacturing during the design, development and verification of subsystems and components. The requirements relative to reliability, safety, operability and availability are also dependent on materials availability, characterization, process maturation and vendor support. This paper discusses the roles and responsibilities of materials and manufacturing engineering during the various phases of Ares IUS development, including design and analysis, hardware development, test and verification. Emphasis is placed how materials, processes and manufacturing support is integrated over the Upper Stage Project, both horizontally and vertically. In addition, the paper describes the approach used to ensure compliance with materials, processes, and manufacturing requirements during the project cycle, with focus on hardware systems design and development.

44 CFR 65.10 - Mapping of areas protected by levee systems.

Code of Federal Regulations, 2010 CFR

2010-10-01

... requirement described in paragraph (b)(1)(i) of this section, may be approved. Appropriate engineering... paragraph (b)(1)(iii) of this section, may be approved. Appropriate engineering analyses demonstrating... are structural parts of the system during operation and design according to sound engineering practice...

Systems Engineering Case Studies: Synopsis of the Learning Principles

DTIC Science & Technology

2010-05-17

Engineering Case Study HST refers to the Hubble Space Telescope Systems Engineering Case Study TBMCS refers to the Theater Battle Management Core System...going to orbit undetected in spite of substantial evidence that could have been used to prevent this occurrence. TBMCS /1 Requirements Definition...baseline was volatile up to system acceptance, which took place after TBMCS passed operational test and evaluation. TBMCS /2 System Architecture The

Engineered Barrier System performance requirements systems study report. Revision 02

DOE Office of Scientific and Technical Information (OSTI.GOV)

Balady, M.A.

This study evaluates the current design concept for the Engineered Barrier System (EBS), in concert with the current understanding of the geologic setting to assess whether enhancements to the required performance of the EBS are necessary. The performance assessment calculations are performed by coupling the EBS with the geologic setting based on the models (some of which were updated for this study) and assumptions used for the 1995 Total System Performance Assessment (TSPA). The need for enhancements is determined by comparing the performance assessment results against the EBS related performance requirements. Subsystem quantitative performance requirements related to the EBS includemore » the requirement to allow no more than 1% of the waste packages (WPs) to fail before 1,000 years after permanent closure of the repository, as well as a requirement to control the release rate of radionuclides from the EBS. The EBS performance enhancements considered included additional engineered components as well as evaluating additional performance available from existing design features but for which no performance credit is currently being taken.« less

14 CFR 23.1195 - Fire extinguishing systems.

Code of Federal Regulations, 2012 CFR

2012-01-01

..., and the discharge distribution must be adequate to extinguish fires. An individual “one shot” system... to extinguish fires. An individual “one shot” system may be used, except for engine(s) embedded in the fuselage, where a “two shot” system is required. ...

A Systems Engineering Process Supporting the Development of Operational Requirements Driven Federations

DTIC Science & Technology

2008-12-01

A SYSTEMS ENGINEERING PROCESS SUPPORTING THE DEVELOPMENT OF OPERATIONAL REQUIREMENTS DRIVEN FEDERATIONS Andreas Tolk & Thomas G. Litwin ...c. THIS PAGE unclassified Standard Form 298 (Rev. 8-98) Prescribed by ANSI Std Z39-18 Tolk, Litwin and Kewley Executive Office (PEO...capabilities and their relative changes 1297 Tolk, Litwin and Kewley based on the system to be evaluated as well, in particular when it comes to

Reducing acquisition risk through integrated systems of systems engineering

NASA Astrophysics Data System (ADS)

Gross, Andrew; Hobson, Brian; Bouwens, Christina

2016-05-01

In the fall of 2015, the Joint Staff J7 (JS J7) sponsored the Bold Quest (BQ) 15.2 event and conducted planning and coordination to combine this event into a joint event with the Army Warfighting Assessment (AWA) 16.1 sponsored by the U.S. Army. This multipurpose event combined a Joint/Coalition exercise (JS J7) with components of testing, training, and experimentation required by the Army. In support of Assistant Secretary of the Army for Acquisition, Logistics, and Technology (ASA(ALT)) System of Systems Engineering and Integration (SoSE&I), Always On-On Demand (AO-OD) used a system of systems (SoS) engineering approach to develop a live, virtual, constructive distributed environment (LVC-DE) to support risk mitigation utilizing this complex and challenging exercise environment for a system preparing to enter limited user test (LUT). AO-OD executed a requirements-based SoS engineering process starting with user needs and objectives from Army Integrated Air and Missile Defense (AIAMD), Patriot units, Coalition Intelligence, Surveillance and Reconnaissance (CISR), Focused End State 4 (FES4) Mission Command (MC) Interoperability with Unified Action Partners (UAP), and Mission Partner Environment (MPE) Integration and Training, Tactics and Procedures (TTP) assessment. The SoS engineering process decomposed the common operational, analytical, and technical requirements, while utilizing the Institute of Electrical and Electronics Engineers (IEEE) Distributed Simulation Engineering and Execution Process (DSEEP) to provide structured accountability for the integration and execution of the AO-OD LVC-DE. As a result of this process implementation, AO-OD successfully planned for, prepared, and executed a distributed simulation support environment that responsively satisfied user needs and objectives, demonstrating the viability of an LVC-DE environment to support multiple user objectives and support risk mitigation activities for systems in the acquisition process.

Orbit Transfer Rocket Engine Technology Program: Advanced engine study, task D.1/D.3

NASA Technical Reports Server (NTRS)

Martinez, A.; Erickson, C.; Hines, B.

1986-01-01

Concepts for space maintainability of OTV engines were examined. An engine design was developed which was driven by space maintenance requirements and by a failure mode and effects (FME) analysis. Modularity within the engine was shown to offer cost benefits and improved space maintenance capabilities. Space operable disconnects were conceptualized for both engine change-out and for module replacement. Through FME mitigation the modules were conceptualized to contain the least reliable and most often replaced engine components. A preliminary space maintenance plan was developed around a controls and condition monitoring system using advanced sensors, controls, and condition monitoring concepts. A complete engine layout was prepared satisfying current vehicle requirements and utilizing projected component advanced technologies. A technology plan for developing the required technology was assembled.

Space shuttle engineering and operations support. Avionics system engineering

NASA Technical Reports Server (NTRS)

Broome, P. A.; Neubaur, R. J.; Welsh, R. T.

1976-01-01

The shuttle avionics integration laboratory (SAIL) requirements for supporting the Spacelab/orbiter avionics verification process are defined. The principal topics are a Spacelab avionics hardware assessment, test operations center/electronic systems test laboratory (TOC/ESL) data processing requirements definition, SAIL (Building 16) payload accommodations study, and projected funding and test scheduling. Because of the complex nature of the Spacelab/orbiter computer systems, the PCM data link, and the high rate digital data system hardware/software relationships, early avionics interface verification is required. The SAIL is a prime candidate test location to accomplish this early avionics verification.

The ICARE Method

NASA Technical Reports Server (NTRS)

Henke, Luke

2010-01-01

The ICARE method is a flexible, widely applicable method for systems engineers to solve problems and resolve issues in a complete and comprehensive manner. The method can be tailored by diverse users for direct application to their function (e.g. system integrators, design engineers, technical discipline leads, analysts, etc.). The clever acronym, ICARE, instills the attitude of accountability, safety, technical rigor and engagement in the problem resolution: Identify, Communicate, Assess, Report, Execute (ICARE). This method was developed through observation of Space Shuttle Propulsion Systems Engineering and Integration (PSE&I) office personnel approach in an attempt to succinctly describe the actions of an effective systems engineer. Additionally it evolved from an effort to make a broadly-defined checklist for a PSE&I worker to perform their responsibilities in an iterative and recursive manner. The National Aeronautics and Space Administration (NASA) Systems Engineering Handbook states, engineering of NASA systems requires a systematic and disciplined set of processes that are applied recursively and iteratively for the design, development, operation, maintenance, and closeout of systems throughout the life cycle of the programs and projects. ICARE is a method that can be applied within the boundaries and requirements of NASA s systems engineering set of processes to provide an elevated sense of duty and responsibility to crew and vehicle safety. The importance of a disciplined set of processes and a safety-conscious mindset increases with the complexity of the system. Moreover, the larger the system and the larger the workforce, the more important it is to encourage the usage of the ICARE method as widely as possible. According to the NASA Systems Engineering Handbook, elements of a system can include people, hardware, software, facilities, policies and documents; all things required to produce system-level results, qualities, properties, characteristics, functions, behavior and performance. The ICARE method can be used to improve all elements of a system and, consequently, the system-level functional, physical and operational performance. Even though ICARE was specifically designed for a systems engineer, any person whose job is to examine another person, product, or process can use the ICARE method to improve effectiveness, implementation, usefulness, value, capability, efficiency, integration, design, and/or marketability. This paper provides the details of the ICARE method, emphasizing the method s application to systems engineering. In addition, a sample of other, non-systems engineering applications are briefly discussed to demonstrate how ICARE can be tailored to a variety of diverse jobs (from project management to parenting).

14 CFR 33.28 - Engine control systems.

Code of Federal Regulations, 2010 CFR

2010-01-01

...) Applicability. These requirements are applicable to any system or device that is part of engine type design...) Aircraft-supplied data. Single failures leading to loss, interruption or corruption of aircraft-supplied...

14 CFR 33.28 - Engine control systems.

Code of Federal Regulations, 2012 CFR

2012-01-01

...) Applicability. These requirements are applicable to any system or device that is part of engine type design...) Aircraft-supplied data. Single failures leading to loss, interruption or corruption of aircraft-supplied...

14 CFR 33.28 - Engine control systems.

Code of Federal Regulations, 2011 CFR

2011-01-01

...) Applicability. These requirements are applicable to any system or device that is part of engine type design...) Aircraft-supplied data. Single failures leading to loss, interruption or corruption of aircraft-supplied...

14 CFR 33.28 - Engine control systems.

Code of Federal Regulations, 2013 CFR

2013-01-01

...) Applicability. These requirements are applicable to any system or device that is part of engine type design...) Aircraft-supplied data. Single failures leading to loss, interruption or corruption of aircraft-supplied...

14 CFR 33.28 - Engine control systems.

Code of Federal Regulations, 2014 CFR

2014-01-01

...) Applicability. These requirements are applicable to any system or device that is part of engine type design...) Aircraft-supplied data. Single failures leading to loss, interruption or corruption of aircraft-supplied...

The NASA Space Launch System Program Systems Engineering Approach for Affordability

NASA Technical Reports Server (NTRS)

Hutt, John J.; Whitehead, Josh; Hanson, John

2017-01-01

The National Aeronautics and Space Administration is currently developing the Space Launch System to provide the United States with a capability to launch large Payloads into Low Earth orbit and deep space. One of the development tenets of the SLS Program is affordability. One initiative to enhance affordability is the SLS approach to requirements definition, verification and system certification. The key aspects of this initiative include: 1) Minimizing the number of requirements, 2) Elimination of explicit verification requirements, 3) Use of certified models of subsystem capability in lieu of requirements when appropriate and 4) Certification of capability beyond minimum required capability. Implementation of each aspect is described and compared to a "typical" systems engineering implementation, including a discussion of relative risk. Examples of each implementation within the SLS Program are provided.

Nuclear Engine System Simulation (NESS) version 2.0

NASA Technical Reports Server (NTRS)

Pelaccio, Dennis G.; Scheil, Christine M.; Petrosky, Lyman J.

1993-01-01

The topics are presented in viewgraph form and include the following; nuclear thermal propulsion (NTP) engine system analysis program development; nuclear thermal propulsion engine analysis capability requirements; team resources used to support NESS development; expanded liquid engine simulations (ELES) computer model; ELES verification examples; NESS program development evolution; past NTP ELES analysis code modifications and verifications; general NTP engine system features modeled by NESS; representative NTP expander, gas generator, and bleed engine system cycles modeled by NESS; NESS program overview; NESS program flow logic; enabler (NERVA type) nuclear thermal rocket engine; prismatic fuel elements and supports; reactor fuel and support element parameters; reactor parameters as a function of thrust level; internal shield sizing; and reactor thermal model.

Airbreathing engine selection criteria for SSTO propulsion system

NASA Astrophysics Data System (ADS)

Ohkami, Yoshiaki; Maita, Masataka

1995-02-01

This paper presents airbreathing engine selection criteria to be applied to the propulsion system of a Single Stage To Orbit (SSTO). To establish the criteria, a relation among three major parameters, i.e., delta-V capability, weight penalty, and effective specific impulse of the engine subsystem, is derived as compared to these parameters of the LH2/LOX rocket engine. The effective specific impulse is a function of the engine I(sub sp) and vehicle thrust-to-drag ratio which is approximated by a function of the vehicle velocity. The weight penalty includes the engine dry weight, cooling subsystem weight. The delta-V capability is defined by the velocity region starting from the minimum operating velocity up to the maximum velocity. The vehicle feasibility is investigated in terms of the structural and propellant weights, which requires an iteration process adjusting the system parameters. The system parameters are computed by iteration based on the Newton-Raphson method. It has been concluded that performance in the higher velocity region is extremely important so that the airbreathing engines are required to operate beyond the velocity equivalent to the rocket engine exhaust velocity (approximately 4500 m/s).

Virtual Collaborative Environments for System of Systems Engineering and Applications for ISAT

NASA Technical Reports Server (NTRS)

Dryer, David A.

2002-01-01

This paper describes an system of systems or metasystems approach and models developed to help prepare engineering organizations for distributed engineering environments. These changes in engineering enterprises include competition in increasingly global environments; new partnering opportunities caused by advances in information and communication technologies, and virtual collaboration issues associated with dispersed teams. To help address challenges and needs in this environment, a framework is proposed that can be customized and adapted for NASA to assist in improved engineering activities conducted in distributed, enhanced engineering environments. The approach is designed to prepare engineers for such distributed collaborative environments by learning and applying e-engineering methods and tools to a real-world engineering development scenario. The approach consists of two phases: an e-engineering basics phase and e-engineering application phase. The e-engineering basics phase addresses skills required for e-engineering. The e-engineering application phase applies these skills in a distributed collaborative environment to system development projects.

77 FR 488 - Control of Emissions From New Highway Vehicles and Engines; Approval of New Scheduled Maintenance...

Federal Register 2010, 2011, 2012, 2013, 2014

2012-01-05

... and engine manufacturers began planning to meet those requirements by optimizing engine designs for low emissions and adding high-efficiency aftertreatment systems. Manufacturers examined the use of... recirculation, and selective catalytic reduction (SCR). SCR systems use a nitrogen-containing reducing agent...

Ada Software Engineering Education and Training Requirements Within the U.S. Army

DTIC Science & Technology

1988-12-01

Services and DoD. DoD Directive 3405.1 requires the use of Ada in all applications and DoD Directive 3405.2 establishes the policy of using Ada in...covers DoD structure and procedures, Army policies , and all aspects of software engineering theory, systems engineering, and software development and...acquisition policy , concept development, workload requirements, contracting, and maintenance. The second course covers many of the same areas

7 CFR 1753.17 - Engineering services.

Code of Federal Regulations, 2014 CFR

2014-01-01

... 7 Agriculture 11 2014-01-01 2014-01-01 false Engineering services. 1753.17 Section 1753.17... AGRICULTURE TELECOMMUNICATIONS SYSTEM CONSTRUCTION POLICIES AND PROCEDURES Engineering Services § 1753.17 Engineering services. (a)(1) All engineering services required by a borrower to support its application for a...

7 CFR 1753.17 - Engineering services.

Code of Federal Regulations, 2010 CFR

2010-01-01

... 7 Agriculture 11 2010-01-01 2010-01-01 false Engineering services. 1753.17 Section 1753.17... AGRICULTURE TELECOMMUNICATIONS SYSTEM CONSTRUCTION POLICIES AND PROCEDURES Engineering Services § 1753.17 Engineering services. (a)(1) All engineering services required by a borrower to support its application for a...

7 CFR 1753.17 - Engineering services.

Code of Federal Regulations, 2011 CFR

2011-01-01

... 7 Agriculture 11 2011-01-01 2011-01-01 false Engineering services. 1753.17 Section 1753.17... AGRICULTURE TELECOMMUNICATIONS SYSTEM CONSTRUCTION POLICIES AND PROCEDURES Engineering Services § 1753.17 Engineering services. (a)(1) All engineering services required by a borrower to support its application for a...

7 CFR 1753.17 - Engineering services.

Code of Federal Regulations, 2013 CFR

2013-01-01

... 7 Agriculture 11 2013-01-01 2013-01-01 false Engineering services. 1753.17 Section 1753.17... AGRICULTURE TELECOMMUNICATIONS SYSTEM CONSTRUCTION POLICIES AND PROCEDURES Engineering Services § 1753.17 Engineering services. (a)(1) All engineering services required by a borrower to support its application for a...

7 CFR 1753.17 - Engineering services.

Code of Federal Regulations, 2012 CFR

2012-01-01

... 7 Agriculture 11 2012-01-01 2012-01-01 false Engineering services. 1753.17 Section 1753.17... AGRICULTURE TELECOMMUNICATIONS SYSTEM CONSTRUCTION POLICIES AND PROCEDURES Engineering Services § 1753.17 Engineering services. (a)(1) All engineering services required by a borrower to support its application for a...

NASA's Space Launch System: Systems Engineering Approach for Affordability and Mission Success

NASA Technical Reports Server (NTRS)

Hutt, John J.; Whitehead, Josh; Hanson, John

2017-01-01

NASA is working toward the first launch of the Space Launch System, a new, unmatched capability for deep space exploration with launch readiness planned for 2019. Since program start in 2011, SLS has passed several major formal design milestones, and every major element of the vehicle has produced test and flight hardware. The SLS approach to systems engineering has been key to the program's success. Key aspects of the SLS SE&I approach include: 1) minimizing the number of requirements, 2) elimination of explicit verification requirements, 3) use of certified models of subsystem capability in lieu of requirements when appropriate and 4) certification of capability beyond minimum required capability.

Engineering Safety- and Security-Related Requirements for Software-Intensive Systems

DTIC Science & Technology

2010-04-27

Requirements Negative (shall not) Requirements Hardware Requirements equ remen s System / Documentation Requirements eve oper Requirements Operational ...Validation Actual / Proposed Defensibility C li Operational Vulnerability Analysis VulnerabilityVulnerability Safety Vulnerability performs System ...including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson

Failure Modes Effects and Criticality Analysis, an Underutilized Safety, Reliability, Project Management and Systems Engineering Tool

NASA Astrophysics Data System (ADS)

Mullin, Daniel Richard

2013-09-01

The majority of space programs whether manned or unmanned for science or exploration require that a Failure Modes Effects and Criticality Analysis (FMECA) be performed as part of their safety and reliability activities. This comes as no surprise given that FMECAs have been an integral part of the reliability engineer's toolkit since the 1950s. The reasons for performing a FMECA are well known including fleshing out system single point failures, system hazards and critical components and functions. However, in the author's ten years' experience as a space systems safety and reliability engineer, findings demonstrate that the FMECA is often performed as an afterthought, simply to meet contract deliverable requirements and is often started long after the system requirements allocation and preliminary design have been completed. There are also important qualitative and quantitative components often missing which can provide useful data to all of project stakeholders. These include; probability of occurrence, probability of detection, time to effect and time to detect and, finally, the Risk Priority Number. This is unfortunate as the FMECA is a powerful system design tool that when used effectively, can help optimize system function while minimizing the risk of failure. When performed as early as possible in conjunction with writing the top level system requirements, the FMECA can provide instant feedback on the viability of the requirements while providing a valuable sanity check early in the design process. It can indicate which areas of the system will require redundancy and which areas are inherently the most risky from the onset. Based on historical and practical examples, it is this author's contention that FMECAs are an immense source of important information for all involved stakeholders in a given project and can provide several benefits including, efficient project management with respect to cost and schedule, system engineering and requirements management, assembly integration and test (AI&T) and operations if applied early, performed to completion and updated along with system design.

Configuration management program plan for Hanford site systems engineering

DOE Office of Scientific and Technical Information (OSTI.GOV)

Kellie, C.L.

This plan establishes the integrated management program for the evolving technical baseline developed through the systems engineering process. This configuration management program aligns with the criteria identified in the DOE Standard, DOE-STD-1073-93. Included are specific requirements for control of the systems engineering RDD-100 database, and electronic data incorporated in the database that establishes the Hanford Site Technical Baseline.

Large space telescope engineering scale model optical design

NASA Technical Reports Server (NTRS)

Facey, T. A.

1973-01-01

The objective is to develop the detailed design and tolerance data for the LST engineering scale model optical system. This will enable MSFC to move forward to the optical element procurement phase and also to evaluate tolerances, manufacturing requirements, assembly/checkout procedures, reliability, operational complexity, stability requirements of the structure and thermal system, and the flexibility to change and grow.

Perspectives on knowledge in engineering design

NASA Technical Reports Server (NTRS)

Rasdorf, W. J.

1985-01-01

Various perspectives are given of the knowledge currently used in engineering design, specifically dealing with knowledge-based expert systems (KBES). Constructing an expert system often reveals inconsistencies in domain knowledge while formalizing it. The types of domain knowledge (facts, procedures, judgments, and control) differ from the classes of that knowledge (creative, innovative, and routine). The feasible tasks for expert systems can be determined based on these types and classes of knowledge. Interpretive tasks require reasoning about a task in light of the knowledge available, where generative tasks create potential solutions to be tested against constraints. Only after classifying the domain by type and level can the engineer select a knowledge-engineering tool for the domain being considered. The critical features to be weighed after classification are knowledge representation techniques, control strategies, interface requirements, compatibility with traditional systems, and economic considerations.

Engine starting and stopping

NASA Astrophysics Data System (ADS)

Curnock, Barry

Different starter systems for jet engines are discussed: electric, cartridge, iso-propyl-nitrate, air, gas turbine, and hydraulic. The fuel system, ignition system, air flow control system, and actual starting mechanism of an air starter motor system are considered. The variation of engine parameters throughout a typical starting sequence are described, with reference to examples for an RB211-535 engine. Physical constraints on engine starting are considered: rotating stall, light up, the window between hang and stall, hang, compressor stall, and the effects of ambient conditions. The following are also discussed: contractual and airworthiness requirements; windmilling; inflight relighting; afterburning light up; combustion stability; and broken shafts. Graphics illustrating the above are presented.

Second Generation RLV Space Vehicle Concept

NASA Astrophysics Data System (ADS)

Bailey, M. D.; Daniel, C. C.

2002-01-01

NASA has a long history of conducting development programs and projects in a consistant 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 I, 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 respect Project Offices. This template is intended to provide systems engineering as an integrated function at the Program Level. . Undoubtedly, the program management of SLI and the NIAT 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.

Second Generation RLV Space Vehicle Concept

NASA Technical Reports Server (NTRS)

Bailey, Michelle; Daniel, Charles; Throckmorton, David A. (Technical Monitor)

2002-01-01

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.

40 CFR 1068.120 - What requirements must I follow to rebuild engines?

Code of Federal Regulations, 2011 CFR

2011-07-01

... (CONTINUED) AIR POLLUTION CONTROLS GENERAL COMPLIANCE PROVISIONS FOR ENGINE PROGRAMS Prohibited Actions and... rebuilding an engine's turbocharger or aftercooler or the engine's systems for fuel metering or electronic control so that it significantly increases the service life of the engine. For these provisions...

A Model-Based Approach to Engineering Behavior of Complex Aerospace Systems

NASA Technical Reports Server (NTRS)

Ingham, Michel; Day, John; Donahue, Kenneth; Kadesch, Alex; Kennedy, Andrew; Khan, Mohammed Omair; Post, Ethan; Standley, Shaun

2012-01-01

One of the most challenging yet poorly defined aspects of engineering a complex aerospace system is behavior engineering, including definition, specification, design, implementation, and verification and validation of the system's behaviors. This is especially true for behaviors of highly autonomous and intelligent systems. Behavior engineering is more of an art than a science. As a process it is generally ad-hoc, poorly specified, and inconsistently applied from one project to the next. It uses largely informal representations, and results in system behavior being documented in a wide variety of disparate documents. To address this problem, JPL has undertaken a pilot project to apply its institutional capabilities in Model-Based Systems Engineering to the challenge of specifying complex spacecraft system behavior. This paper describes the results of the work in progress on this project. In particular, we discuss our approach to modeling spacecraft behavior including 1) requirements and design flowdown from system-level to subsystem-level, 2) patterns for behavior decomposition, 3) allocation of behaviors to physical elements in the system, and 4) patterns for capturing V&V activities associated with behavioral requirements. We provide examples of interesting behavior specification patterns, and discuss findings from the pilot project.

System Engineering for J-2X Development: The Simpler, the Better

NASA Technical Reports Server (NTRS)

Kelly, William M.; Greasley, Paul; Greene, William D.; Ackerman, Peter

2008-01-01

The Ares I and Ares V Vehicles will utilize the J-2X rocket engine developed for NASA by the Pratt and Whitney Rocketdyne Company (PWR) as the upper stage engine (USE). The J-2X is an improved higher power version of the original J-2 engine used for Apollo. System Engineering (SE) facilitates direct and open discussions of issues and problems. This simple idea is often overlooked in large, complex engineering development programs. Definition and distribution of requirements from the engine level to the component level is controlled by Allocation Reports which breaks down numerical design objectives (weight, reliability, etc.) into quanta goals for each component area. Linked databases of design and verification requirements help eliminate redundancy and potential mistakes inherent in separated systems. Another tool, the Architecture Design Description (ADD), is used to control J-2X system architecture and effectively communicate configuration changes to those involved in the design process. But the proof of an effective process is in successful program accomplishment. SE is the methodology being used to meet the challenge of completing J-2X engine certification 2 years ahead of any engine program ever developed at PWR. This paper describes the simple, better SE tools and techniques used to achieve this success.

Combining System Safety and Reliability to Ensure NASA CoNNeCT's Success

NASA Technical Reports Server (NTRS)

Havenhill, Maria; Fernandez, Rene; Zampino, Edward

2012-01-01

Hazard Analysis, Failure Modes and Effects Analysis (FMEA), the Limited-Life Items List (LLIL), and the Single Point Failure (SPF) List were applied by System Safety and Reliability engineers on NASA's Communications, Navigation, and Networking reConfigurable Testbed (CoNNeCT) Project. The integrated approach involving cross reviews of these reports by System Safety, Reliability, and Design engineers resulted in the mitigation of all identified hazards. The outcome was that the system met all the safety requirements it was required to meet.

Software For Graphical Representation Of A Network

NASA Technical Reports Server (NTRS)

Mcallister, R. William; Mclellan, James P.

1993-01-01

System Visualization Tool (SVT) computer program developed to provide systems engineers with means of graphically representing networks. Generates diagrams illustrating structures and states of networks defined by users. Provides systems engineers powerful tool simplifing analysis of requirements and testing and maintenance of complex software-controlled systems. Employs visual models supporting analysis of chronological sequences of requirements, simulation data, and related software functions. Applied to pneumatic, hydraulic, and propellant-distribution networks. Used to define and view arbitrary configurations of such major hardware components of system as propellant tanks, valves, propellant lines, and engines. Also graphically displays status of each component. Advantage of SVT: utilizes visual cues to represent configuration of each component within network. Written in Turbo Pascal(R), version 5.0.

46 CFR 169.609 - Exhaust systems.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 46 Shipping 7 2014-10-01 2014-10-01 false Exhaust systems. 169.609 Section 169.609 Shipping COAST... Electrical Internal Combustion Engine Installations § 169.609 Exhaust systems. Engine exhaust installations and associated cooling systems must be built in accordance with the requirements of American Boat and...

Sensemaking in a Value Based Context for Large Scale Complex Engineered Systems

NASA Astrophysics Data System (ADS)

Sikkandar Basha, Nazareen

The design and the development of Large-Scale Complex Engineered Systems (LSCES) requires the involvement of multiple teams and numerous levels of the organization and interactions with large numbers of people and interdisciplinary departments. Traditionally, requirements-driven Systems Engineering (SE) is used in the design and development of these LSCES. The requirements are used to capture the preferences of the stakeholder for the LSCES. Due to the complexity of the system, multiple levels of interactions are required to elicit the requirements of the system within the organization. Since LSCES involves people and interactions between the teams and interdisciplinary departments, it should be socio-technical in nature. The elicitation of the requirements of most large-scale system projects are subjected to creep in time and cost due to the uncertainty and ambiguity of requirements during the design and development. In an organization structure, the cost and time overrun can occur at any level and iterate back and forth thus increasing the cost and time. To avoid such creep past researches have shown that rigorous approaches such as value based designing can be used to control it. But before the rigorous approaches can be used, the decision maker should have a proper understanding of requirements creep and the state of the system when the creep occurs. Sensemaking is used to understand the state of system when the creep occurs and provide a guidance to decision maker. This research proposes the use of the Cynefin framework, sensemaking framework which can be used in the design and development of LSCES. It can aide in understanding the system and decision making to minimize the value gap due to requirements creep by eliminating ambiguity which occurs during design and development. A sample hierarchical organization is used to demonstrate the state of the system at the occurrence of requirements creep in terms of cost and time using the Cynefin framework. These trials are continued for different requirements and at different sub-system level. The results obtained show that the Cynefin framework can be used to improve the value of the system and can be used for predictive analysis. The decision makers can use these findings and use rigorous approaches and improve the design of Large Scale Complex Engineered Systems.

40 CFR 90.327 - Sampling system requirements.

Code of Federal Regulations, 2011 CFR

2011-07-01

... 40 Protection of Environment 20 2011-07-01 2011-07-01 false Sampling system requirements. 90.327... Equipment Provisions § 90.327 Sampling system requirements. (a) Sample component surface temperature. For sampling systems which use heated components, use engineering judgment to locate the coolest portion of...

40 CFR 90.327 - Sampling system requirements.

Code of Federal Regulations, 2010 CFR

2010-07-01

... 40 Protection of Environment 20 2010-07-01 2010-07-01 false Sampling system requirements. 90.327... Equipment Provisions § 90.327 Sampling system requirements. (a) Sample component surface temperature. For sampling systems which use heated components, use engineering judgment to locate the coolest portion of...

Concept Design of the Payload Handling Manipulator System. [space shuttle orbiters

NASA Technical Reports Server (NTRS)

1975-01-01

The design, requirements, and interface definition of a remote manipulator system developed to handle orbiter payloads are presented. End effector design, control system concepts, and man-machine engineering are considered along with crew station requirements and closed circuit television system performance requirements.

48 CFR 2936.209 - Construction contracts with architect-engineer firms.

Code of Federal Regulations, 2014 CFR

2014-10-01

... with architect-engineer firms. 2936.209 Section 2936.209 Federal Acquisition Regulations System DEPARTMENT OF LABOR GENERAL CONTRACTING REQUIREMENTS CONSTRUCTION AND ARCHITECT-ENGINEER CONTRACTS Special Aspects of Contracting for Construction 2936.209 Construction contracts with architect-engineer firms. As...

48 CFR 2936.209 - Construction contracts with architect-engineer firms.

Code of Federal Regulations, 2011 CFR

2011-10-01

... with architect-engineer firms. 2936.209 Section 2936.209 Federal Acquisition Regulations System DEPARTMENT OF LABOR GENERAL CONTRACTING REQUIREMENTS CONSTRUCTION AND ARCHITECT-ENGINEER CONTRACTS Special Aspects of Contracting for Construction 2936.209 Construction contracts with architect-engineer firms. As...

48 CFR 2936.209 - Construction contracts with architect-engineer firms.

Code of Federal Regulations, 2010 CFR

2010-10-01

... with architect-engineer firms. 2936.209 Section 2936.209 Federal Acquisition Regulations System DEPARTMENT OF LABOR GENERAL CONTRACTING REQUIREMENTS CONSTRUCTION AND ARCHITECT-ENGINEER CONTRACTS Special Aspects of Contracting for Construction 2936.209 Construction contracts with architect-engineer firms. As...

48 CFR 2936.209 - Construction contracts with architect-engineer firms.

Code of Federal Regulations, 2012 CFR

2012-10-01

... with architect-engineer firms. 2936.209 Section 2936.209 Federal Acquisition Regulations System DEPARTMENT OF LABOR GENERAL CONTRACTING REQUIREMENTS CONSTRUCTION AND ARCHITECT-ENGINEER CONTRACTS Special Aspects of Contracting for Construction 2936.209 Construction contracts with architect-engineer firms. As...

Systems engineering principles for the design of biomedical signal processing systems.

PubMed

Faust, Oliver; Acharya U, Rajendra; Sputh, Bernhard H C; Min, Lim Choo

2011-06-01

Systems engineering aims to produce reliable systems which function according to specification. In this paper we follow a systems engineering approach to design a biomedical signal processing system. We discuss requirements capturing, specification definition, implementation and testing of a classification system. These steps are executed as formal as possible. The requirements, which motivate the system design, are based on diabetes research. The main requirement for the classification system is to be a reliable component of a machine which controls diabetes. Reliability is very important, because uncontrolled diabetes may lead to hyperglycaemia (raised blood sugar) and over a period of time may cause serious damage to many of the body systems, especially the nerves and blood vessels. In a second step, these requirements are refined into a formal CSP‖ B model. The formal model expresses the system functionality in a clear and semantically strong way. Subsequently, the proven system model was translated into an implementation. This implementation was tested with use cases and failure cases. Formal modeling and automated model checking gave us deep insight in the system functionality. This insight enabled us to create a reliable and trustworthy implementation. With extensive tests we established trust in the reliability of the implementation. Copyright © 2010 Elsevier Ireland Ltd. All rights reserved.

Nuclear Thermal Propulsion Mars Mission Systems Analysis and Requirements Definition

NASA Technical Reports Server (NTRS)

Mulqueen, Jack; Chiroux, Robert C.; Thomas, Dan; Crane, Tracie

2007-01-01

This paper describes the Mars transportation vehicle design concepts developed by the Marshall Space Flight Center (MSFC) Advanced Concepts Office. These vehicle design concepts provide an indication of the most demanding and least demanding potential requirements for nuclear thermal propulsion systems for human Mars exploration missions from years 2025 to 2035. Vehicle concept options vary from large "all-up" vehicle configurations that would transport all of the elements for a Mars mission on one vehicle. to "split" mission vehicle configurations that would consist of separate smaller vehicles that would transport cargo elements and human crew elements to Mars separately. Parametric trades and sensitivity studies show NTP stage and engine design options that provide the best balanced set of metrics based on safety, reliability, performance, cost and mission objectives. Trade studies include the sensitivity of vehicle performance to nuclear engine characteristics such as thrust, specific impulse and nuclear reactor type. Tbe associated system requirements are aligned with the NASA Exploration Systems Mission Directorate (ESMD) Reference Mars mission as described in the Explorations Systems Architecture Study (ESAS) report. The focused trade studies include a detailed analysis of nuclear engine radiation shield requirements for human missions and analysis of nuclear thermal engine design options for the ESAS reference mission.

Study of solid rocket motor for space shuttle booster, volume 2, book 1

NASA Technical Reports Server (NTRS)

1972-01-01

The technical requirements for the solid propellant rocket engine to be used with the space shuttle orbiter are presented. The subjects discussed are: (1) propulsion system definition, (2) solid rocket engine stage design, (3) solid rocket engine stage recovery, (4) environmental effects, (5) manrating of the solid rocket engine stage, (6) system safety analysis, and (7) ground support equipment.

Development of advanced high temperature in-cylinder components and tribological systems for low heat rejection diesel engines, phase 1

NASA Astrophysics Data System (ADS)

Kroeger, C. A.; Larson, H. J.

1992-03-01

Analysis and concept design work completed in Phase 1 have identified a low heat rejection engine configuration with the potential to meet the Heavy Duty Transport Technology program specific fuel consumption goal of 152 g/kW-hr. The proposed engine configuration incorporates low heat rejection, in-cylinder components designed for operation at 24 MPa peak cylinder pressure. Water cooling is eliminated by selective oil cooling of the components. A high temperature lubricant will be required due to increased in-cylinder operating temperatures. A two-stage turbocharger air system with intercooling and aftercooling was selected to meet engine boost and BMEP requirements. A turbocompound turbine stage is incorporated for exhaust energy recovery. The concept engine cost was estimated to be 43 percent higher compared to a Caterpillar 3176 engine. The higher initial engine cost is predicted to be offset by reduced operating costs due the lower fuel consumption.

Development of advanced high temperature in-cylinder components and tribological systems for low heat rejection diesel engines, phase 1

NASA Technical Reports Server (NTRS)

Kroeger, C. A.; Larson, H. J.

1992-01-01

Analysis and concept design work completed in Phase 1 have identified a low heat rejection engine configuration with the potential to meet the Heavy Duty Transport Technology program specific fuel consumption goal of 152 g/kW-hr. The proposed engine configuration incorporates low heat rejection, in-cylinder components designed for operation at 24 MPa peak cylinder pressure. Water cooling is eliminated by selective oil cooling of the components. A high temperature lubricant will be required due to increased in-cylinder operating temperatures. A two-stage turbocharger air system with intercooling and aftercooling was selected to meet engine boost and BMEP requirements. A turbocompound turbine stage is incorporated for exhaust energy recovery. The concept engine cost was estimated to be 43 percent higher compared to a Caterpillar 3176 engine. The higher initial engine cost is predicted to be offset by reduced operating costs due the lower fuel consumption.

Collaborative engineering and design management for the Hobby-Eberly Telescope tracker upgrade

NASA Astrophysics Data System (ADS)

Mollison, Nicholas T.; Hayes, Richard J.; Good, John M.; Booth, John A.; Savage, Richard D.; Jackson, John R.; Rafal, Marc D.; Beno, Joseph H.

2010-07-01

The engineering and design of systems as complex as the Hobby-Eberly Telescope's* new tracker require that multiple tasks be executed in parallel and overlapping efforts. When the design of individual subsystems is distributed among multiple organizations, teams, and individuals, challenges can arise with respect to managing design productivity and coordinating successful collaborative exchanges. This paper focuses on design management issues and current practices for the tracker design portion of the Hobby-Eberly Telescope Wide Field Upgrade project. The scope of the tracker upgrade requires engineering contributions and input from numerous fields including optics, instrumentation, electromechanics, software controls engineering, and site-operations. Successful system-level integration of tracker subsystems and interfaces is critical to the telescope's ultimate performance in astronomical observation. Software and process controls for design information and workflow management have been implemented to assist the collaborative transfer of tracker design data. The tracker system architecture and selection of subsystem interfaces has also proven to be a determining factor in design task formulation and team communication needs. Interface controls and requirements change controls will be discussed, and critical team interactions are recounted (a group-participation Failure Modes and Effects Analysis [FMEA] is one of special interest). This paper will be of interest to engineers, designers, and managers engaging in multi-disciplinary and parallel engineering projects that require coordination among multiple individuals, teams, and organizations.

Update - Concept of Operations for Integrated Model-Centric Engineering at JPL

NASA Technical Reports Server (NTRS)

Bayer, Todd J.; Bennett, Matthew; Delp, Christopher L.; Dvorak, Daniel; Jenkins, Steven J.; Mandutianu, Sanda

2011-01-01

The increasingly ambitious requirements levied on JPL's space science missions, and the development pace of such missions, challenge our current engineering practices. All the engineering disciplines face this growth in complexity to some degree, but the challenges are greatest in systems engineering where numerous competing interests must be reconciled and where complex system level interactions must be identified and managed. Undesired system-level interactions are increasingly a major risk factor that cannot be reliably exposed by testing, and natural-language single-viewpoint specifications areinadequate to capture and expose system level interactions and characteristics. Systems engineering practices must improve to meet these challenges, and the most promising approach today is the movement toward a more integrated and model-centric approach to mission conception, design, implementation and operations. This approach elevates engineering models to a principal role in systems engineering, gradually replacing traditional document centric engineering practices.

76 FR 35424 - Information Collection Requirements; Defense Federal Acquisition Regulation Supplement...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-06-17

... DEPARTMENT OF DEFENSE Defense Acquisition Regulations System Information Collection Requirements; Defense Federal Acquisition Regulation Supplement; Construction and Architect-Engineer Contracts AGENCY..., Construction and Architect-Engineer Contracts, and Related Clauses at DFARS 252.236; OMB Control Number 0704...

Digital controls for gas turbine engines

DOE Office of Scientific and Technical Information (OSTI.GOV)

Robinson, K.

1987-01-01

This paper begins by first describing the simplistic requirements of a gas turbine engine; how these requirements are best satisfied, frequently with the aid of electronic control systems; what the trade-off between integrity and reliability means; and finally, but forming a major section, this paper describes in qualitative detail a few of the current programmes for Full Authority Digital Engine Controls (FADEC).

40 CFR 1068.120 - What requirements must I follow to rebuild engines?

Code of Federal Regulations, 2012 CFR

2012-07-01

... systems for fuel metering or electronic control so that it significantly increases the service life of the... must have a reasonable technical basis for knowing that the rebuilt engine's emission control system... believe that the engine with those parts will control emissions of all pollutants at least to the same...

40 CFR 1068.120 - What requirements must I follow to rebuild engines?

Code of Federal Regulations, 2014 CFR

2014-07-01

... systems for fuel metering or electronic control so that it significantly increases the service life of the... must have a reasonable technical basis for knowing that the rebuilt engine's emission control system... believe that the engine with those parts will control emissions of all pollutants at least to the same...

40 CFR 1068.120 - What requirements must I follow to rebuild engines?

Code of Federal Regulations, 2013 CFR

2013-07-01

... systems for fuel metering or electronic control so that it significantly increases the service life of the... must have a reasonable technical basis for knowing that the rebuilt engine's emission control system... believe that the engine with those parts will control emissions of all pollutants at least to the same...

D-21B RBCC Modification Feasibility Study

NASA Technical Reports Server (NTRS)

1999-01-01

This report presents a feasibility study on the modifications required to re-engine the Lockheed D-21 Drone for use as a NASA RBCC engine. An introduction, background information, engine configuration and performance, propulsion system integration, loads/thermal analysis, avionics/systems, flight test results, costs and work schedule, and some conclusions are presented.

40 CFR 63.9306 - What are my continuous parameter monitoring system (CPMS) installation, operation, and...

Code of Federal Regulations, 2014 CFR

2014-07-01

... Standards for Hazardous Air Pollutants for Engine Test Cells/Stands General Compliane Requirements § 63.9306... at all times that an engine test cell/stand is operating, except during monitoring malfunctions... engine test cell/stand is operating. You must inspect the automatic shutdown system at least once every...

40 CFR 63.9306 - What are my continuous parameter monitoring system (CPMS) installation, operation, and...

Code of Federal Regulations, 2013 CFR

2013-07-01

... Standards for Hazardous Air Pollutants for Engine Test Cells/Stands General Compliane Requirements § 63.9306... at all times that an engine test cell/stand is operating, except during monitoring malfunctions... engine test cell/stand is operating. You must inspect the automatic shutdown system at least once every...

Definition, technology readiness, and development cost of the orbit transfer vehicle engine integrated control and health monitoring system elements

NASA Technical Reports Server (NTRS)

Cannon, I.; Balcer, S.; Cochran, M.; Klop, J.; Peterson, S.

1991-01-01

An Integrated Control and Health Monitoring (ICHM) system was conceived for use on a 20 Klb thrust baseline Orbit Transfer Vehicle (OTV) engine. Considered for space used, the ICHM was defined for reusability requirements for an OTV engine service free life of 20 missions, with 100 starts and a total engine operational time of 4 hours. Functions were derived by flowing down requirements from NASA guidelines, previous OTV engine or ICHM documents, and related contracts. The elements of an ICHM were identified and listed, and these elements were described in sufficient detail to allow estimation of their technology readiness levels. These elements were assessed in terms of technology readiness level, and supporting rationale for these assessments presented. The remaining cost for development of a minimal ICHM system to technology readiness level 6 was estimated. The estimates are within an accuracy range of minus/plus 20 percent. The cost estimates cover what is needed to prepare an ICHM system for use on a focussed testbed for an expander cycle engine, excluding support to the actual test firings.

Metal- and intermetallic-matrix composites for aerospace propulsion and power systems

NASA Astrophysics Data System (ADS)

Doychak, J.

1992-06-01

Successful development and deployment of metal-matrix composites and intermetallic- matrix composites are critical to reaching the goals of many advanced aerospace propulsion and power development programs. The material requirements are based on the aerospace propulsion and power system requirements, economics, and other factors. Advanced military and civilian aircraft engines will require higher specific strength materials that operate at higher temperatures, and the civilian engines will also require long lifetimes. The specific space propulsion and power applications require hightemperature, high-thermal-conductivity, and high-strength materials. Metal-matrix composites and intermetallic-matrix composites either fulfill or have the potential of fulfilling these requirements.

Specialized data analysis for the Space Shuttle Main Engine and diagnostic evaluation of advanced propulsion system components

NASA Technical Reports Server (NTRS)

1993-01-01

The Marshall Space Flight Center is responsible for the development and management of advanced launch vehicle propulsion systems, including the Space Shuttle Main Engine (SSME), which is presently operational, and the Space Transportation Main Engine (STME) under development. The SSME's provide high performance within stringent constraints on size, weight, and reliability. Based on operational experience, continuous design improvement is in progress to enhance system durability and reliability. Specialized data analysis and interpretation is required in support of SSME and advanced propulsion system diagnostic evaluations. Comprehensive evaluation of the dynamic measurements obtained from test and flight operations is necessary to provide timely assessment of the vibrational characteristics indicating the operational status of turbomachinery and other critical engine components. Efficient performance of this effort is critical due to the significant impact of dynamic evaluation results on ground test and launch schedules, and requires direct familiarity with SSME and derivative systems, test data acquisition, and diagnostic software. Detailed analysis and evaluation of dynamic measurements obtained during SSME and advanced system ground test and flight operations was performed including analytical/statistical assessment of component dynamic behavior, and the development and implementation of analytical/statistical models to efficiently define nominal component dynamic characteristics, detect anomalous behavior, and assess machinery operational condition. In addition, the SSME and J-2 data will be applied to develop vibroacoustic environments for advanced propulsion system components, as required. This study will provide timely assessment of engine component operational status, identify probable causes of malfunction, and indicate feasible engineering solutions. This contract will be performed through accomplishment of negotiated task orders.

14 CFR 33.69 - Ignitions system.

Code of Federal Regulations, 2013 CFR

2013-01-01

... STANDARDS: AIRCRAFT ENGINES Design and Construction; Turbine Aircraft Engines § 33.69 Ignitions system. Each..., except that only one igniter is required for fuel burning augmentation systems. [Amdt. 33-6, 39 FR 35466... 14 Aeronautics and Space 1 2013-01-01 2013-01-01 false Ignitions system. 33.69 Section 33.69...

14 CFR 33.69 - Ignitions system.

Code of Federal Regulations, 2014 CFR

2014-01-01

... STANDARDS: AIRCRAFT ENGINES Design and Construction; Turbine Aircraft Engines § 33.69 Ignitions system. Each..., except that only one igniter is required for fuel burning augmentation systems. [Amdt. 33-6, 39 FR 35466... 14 Aeronautics and Space 1 2014-01-01 2014-01-01 false Ignitions system. 33.69 Section 33.69...

14 CFR 33.69 - Ignitions system.

Code of Federal Regulations, 2012 CFR

2012-01-01

... STANDARDS: AIRCRAFT ENGINES Design and Construction; Turbine Aircraft Engines § 33.69 Ignitions system. Each..., except that only one igniter is required for fuel burning augmentation systems. [Amdt. 33-6, 39 FR 35466... 14 Aeronautics and Space 1 2012-01-01 2012-01-01 false Ignitions system. 33.69 Section 33.69...

14 CFR 125.181 - Induction system ice prevention.

Code of Federal Regulations, 2013 CFR

2013-01-01

... 14 Aeronautics and Space 3 2013-01-01 2013-01-01 false Induction system ice prevention. 125.181... Requirements § 125.181 Induction system ice prevention. A means for preventing the malfunctioning of each engine due to ice accumulation in the engine air induction system must be provided for each airplane. ...

14 CFR 125.181 - Induction system ice prevention.

Code of Federal Regulations, 2011 CFR

2011-01-01

... 14 Aeronautics and Space 3 2011-01-01 2011-01-01 false Induction system ice prevention. 125.181... Requirements § 125.181 Induction system ice prevention. A means for preventing the malfunctioning of each engine due to ice accumulation in the engine air induction system must be provided for each airplane. ...

14 CFR 125.181 - Induction system ice prevention.

Code of Federal Regulations, 2012 CFR

2012-01-01

... 14 Aeronautics and Space 3 2012-01-01 2012-01-01 false Induction system ice prevention. 125.181... Requirements § 125.181 Induction system ice prevention. A means for preventing the malfunctioning of each engine due to ice accumulation in the engine air induction system must be provided for each airplane. ...

14 CFR 125.181 - Induction system ice prevention.

Code of Federal Regulations, 2010 CFR

2010-01-01

... 14 Aeronautics and Space 3 2010-01-01 2010-01-01 false Induction system ice prevention. 125.181... Requirements § 125.181 Induction system ice prevention. A means for preventing the malfunctioning of each engine due to ice accumulation in the engine air induction system must be provided for each airplane. ...

14 CFR 125.181 - Induction system ice prevention.

Code of Federal Regulations, 2014 CFR

2014-01-01

... 14 Aeronautics and Space 3 2014-01-01 2014-01-01 false Induction system ice prevention. 125.181... Requirements § 125.181 Induction system ice prevention. A means for preventing the malfunctioning of each engine due to ice accumulation in the engine air induction system must be provided for each airplane. ...

Systems Engineering and Integration for Advanced Life Support System and HST

NASA Technical Reports Server (NTRS)

Kamarani, Ali K.

2005-01-01

Systems engineering (SE) discipline has revolutionized the way engineers and managers think about solving issues related to design of complex systems: With continued development of state-of-the-art technologies, systems are becoming more complex and therefore, a systematic approach is essential to control and manage their integrated design and development. This complexity is driven from integration issues. In this case, subsystems must interact with one another in order to achieve integration objectives, and also achieve the overall system's required performance. Systems engineering process addresses these issues at multiple levels. It is a technology and management process dedicated to controlling all aspects of system life cycle to assure integration at all levels. The Advanced Integration Matrix (AIM) project serves as the systems engineering and integration function for the Human Support Technology (HST) program. AIM provides means for integrated test facilities and personnel for performance trade studies, analyses, integrated models, test results, and validated requirements of the integration of HST. The goal of AIM is to address systems-level integration issues for exploration missions. It will use an incremental systems integration approach to yield technologies, baselines for further development, and possible breakthrough concepts in the areas of technological and organizational interfaces, total information flow, system wide controls, technical synergism, mission operations protocols and procedures, and human-machine interfaces.

System safety in Stirling engine development

NASA Technical Reports Server (NTRS)

Bankaitis, H.

1981-01-01

The DOE/NASA Stirling Engine Project Office has required that contractors make safety considerations an integral part of all phases of the Stirling engine development program. As an integral part of each engine design subtask, analyses are evolved to determine possible modes of failure. The accepted system safety analysis techniques (Fault Tree, FMEA, Hazards Analysis, etc.) are applied in various degrees of extent at the system, subsystem and component levels. The primary objectives are to identify critical failure areas, to enable removal of susceptibility to such failures or their effects from the system and to minimize risk.

Computer tools for systems engineering at LaRC

NASA Technical Reports Server (NTRS)

Walters, J. Milam

1994-01-01

The Systems Engineering Office (SEO) has been established to provide life cycle systems engineering support to Langley research Center projects. over the last two years, the computing market has been reviewed for tools which could enhance the effectiveness and efficiency of activities directed towards this mission. A group of interrelated applications have been procured, or are under development including a requirements management tool, a system design and simulation tool, and project and engineering data base. This paper will review the current configuration of these tools and provide information on future milestones and directions.

Configuration management program plan for Hanford site systems engineering

DOE Office of Scientific and Technical Information (OSTI.GOV)

Hoffman, A.G.

This plan establishes the integrated configuration management program for the evolving technical baseline developed through the systems engineering process. This configuration management program aligns with the criteria identified in the DOE Standard, DOE-STD-1073-93. Included are specific requirements for control of the systems engineering RDD-100 database, and electronic data incorporated in the database that establishes the Hanford site technical baseline.

Analysis of variation in oil pressure in lubricating system

NASA Astrophysics Data System (ADS)

Sharma, Sumit; Upreti, Mritunjay; Sharma, Bharat; Poddar, Keshav

2018-05-01

Automotive Maintenance for an engine contributes to its reliability, energy efficiency and repair cost reduction. Modeling of engine performance and fault detection require large amount of data, which are usually obtained on test benches. This report presents a methodical study on analysis of variation in lubrication system of various medium speed engines. Further this study is limited to the influence of Engine Oil Pressure on frictional losses, Torque analysis for various Oil Pressures and an analytical analysis of engine Lubrication System. The data collected from various Engines under diagnostics is represented graphically. Finally the illustrated results were used as a viable source for detection and troubleshooting of faults in Lubrication System of regular passenger vehicle.

Systems Engineering and Management Applications of ISO 9001:2015 for Government

NASA Technical Reports Server (NTRS)

Shepherd, Christena C.

2016-01-01

The manufacturing segment of the business world is busy assessing the impact of ISO 9001:2015, and updating their management systems to meet the required compliance date. What does the new revision mean for government agencies that deliver large engineering projects rather than mass production? In fact, the standard, especially the new revision, can be used quite readily for government agencies, or applied to specific projects, once it is understood in terms of the similarities with systems engineering and project management. From there it can be extrapolated to "mission realization" systems, and a Quality Management System (QMS) is a logical result that can bring order to processes and systems that likely already exist in some fashion. ISO 9001:2015 is less product-oriented than previous versions. It can be more broadly applied to public organizations as well as private; and to services (missions) as well as products. The emphasis on risk management in the revised standard provides the needed balance for weighing decisions with respect to cost, schedule, technical, safety, and regulatory compliance; so if this is not part of agency governance already, this is a good place to start, especially for large engineering projects. The Systems Engineering standard used for this analysis is from NASA's NPR 7123.1 NASA Systems Engineering Processes and Requirements; however, those who are more familiar with ISO/IEC 26702 Systems Engineering-application and management of the systems engineering process, or SAE/EIA 632 Processes for Engineering a System will also recognize the similarities. In reality, the QMS outlined by ISO 9001 reinforces the systems engineering processes, and serves to ensure that they are adequately implemented, although most of the ISO 9001 literature emphasizes the production and process aspects of the standard. Rather than beginning with ISO 9001and getting lost in the vocabulary, it is useful to begin with the systems engineering lifecycle. Identification of stakeholder expectations, identifying solutions, creating specific product or service designs, production of the product or service, delivery to the public, and the associated management, planning, and control processes, are a familiar place to begin thinking of the overall system of identifying, designing, and competing a project or mission. Lining up this lifecycle with the ISO requirements (see Figure 1) illustrates how a quality management system is concerned with the same processes, and provides a governance and assurance function. If implemented properly, there are cost savings resulting from less rework, repair, reprocessing, failures, misplaced documents, and similar types of deficiencies1. Starting with an organization's systems engineering processes allows the organization to use their own terminology for a QMS plan, and tailor the plan to their own project or organization, so that it is more easily developed, understood, and implemented.

Expert system prototype developments for NASA-KSC business and engineering applications

NASA Technical Reports Server (NTRS)

Ragusa, James M.; Gonzalez, Avelino J.

1988-01-01

Prototype expert systems developed for a variety of NASA projects in the business/management and engineering domains are discussed. Business-related problems addressed include an assistant for simulating launch vehicle processing, a plan advisor for the acquisition of automated data processing equipment, and an expert system for the identification of customer requirements. Engineering problems treated include an expert system for detecting potential ignition sources in LOX and gaseous-oxygen transportation systems and an expert system for hazardous-gas detection.

Design control for clinical translation of 3D printed modular scaffolds.

PubMed

Hollister, Scott J; Flanagan, Colleen L; Zopf, David A; Morrison, Robert J; Nasser, Hassan; Patel, Janki J; Ebramzadeh, Edward; Sangiorgio, Sophia N; Wheeler, Matthew B; Green, Glenn E

2015-03-01

The primary thrust of tissue engineering is the clinical translation of scaffolds and/or biologics to reconstruct tissue defects. Despite this thrust, clinical translation of tissue engineering therapies from academic research has been minimal in the 27 year history of tissue engineering. Academic research by its nature focuses on, and rewards, initial discovery of new phenomena and technologies in the basic research model, with a view towards generality. Translation, however, by its nature must be directed at specific clinical targets, also denoted as indications, with associated regulatory requirements. These regulatory requirements, especially design control, require that the clinical indication be precisely defined a priori, unlike most academic basic tissue engineering research where the research target is typically open-ended, and furthermore requires that the tissue engineering therapy be constructed according to design inputs that ensure it treats or mitigates the clinical indication. Finally, regulatory approval dictates that the constructed system be verified, i.e., proven that it meets the design inputs, and validated, i.e., that by meeting the design inputs the therapy will address the clinical indication. Satisfying design control requires (1) a system of integrated technologies (scaffolds, materials, biologics), ideally based on a fundamental platform, as compared to focus on a single technology, (2) testing of design hypotheses to validate system performance as opposed to mechanistic hypotheses of natural phenomena, and (3) sequential testing using in vitro, in vivo, large preclinical and eventually clinical tests against competing therapies, as compared to single experiments to test new technologies or test mechanistic hypotheses. Our goal in this paper is to illustrate how design control may be implemented in academic translation of scaffold based tissue engineering therapies. Specifically, we propose to (1) demonstrate a modular platform approach founded on 3D printing for developing tissue engineering therapies and (2) illustrate the design control process for modular implementation of two scaffold based tissue engineering therapies: airway reconstruction and bone tissue engineering based spine fusion.

Design Control for Clinical Translation of 3D Printed Modular Scaffolds

PubMed Central

Hollister, Scott J.; Flanagan, Colleen L.; Zopf, David A.; Morrison, Robert J.; Nasser, Hassan; Patel, Janki J.; Ebramzadeh, Edward; Sangiorgio, Sophia N.; Wheeler, Matthew B.; Green, Glenn E.

2015-01-01

The primary thrust of tissue engineering is the clinical translation of scaffolds and/or biologics to reconstruct tissue defects. Despite this thrust, clinical translation of tissue engineering therapies from academic research has been minimal in the 27 year history of tissue engineering. Academic research by its nature focuses on, and rewards, initial discovery of new phenomena and technologies in the basic research model, with a view towards generality. Translation, however, by its nature must be directed at specific clinical targets, also denoted as indications, with associated regulatory requirements. These regulatory requirements, especially design control, require that the clinical indication be precisely defined a priori, unlike most academic basic tissue engineering research where the research target is typically open-ended, and furthermore requires that the tissue engineering therapy be constructed according to design inputs that ensure it treats or mitigates the clinical indication. Finally, regulatory approval dictates that the constructed system be verified, i.e., proven that it meets the design inputs, and validated, i.e., that by meeting the design inputs the therapy will address the clinical indication. Satisfying design control requires (1) a system of integrated technologies (scaffolds, materials, biologics), ideally based on a fundamental platform, as compared to focus on a single technology, (2) testing of design hypotheses to validate system performance as opposed to mechanistic hypotheses of natural phenomena, and (3) sequential testing using in vitro, in vivo, large preclinical and eventually clinical tests against competing therapies, as compared to single experiments to test new technologies or test mechanistic hypotheses. Our goal in this paper is to illustrate how design control may be implemented in academic translation of scaffold based tissue engineering therapies. Specifically, we propose to (1) demonstrate a modular platform approach founded on 3D printing for developing tissue engineering therapies and (2) illustrate the design control process for modular implementation of two scaffold based tissue engineering therapies: airway reconstruction and bone tissue engineering based spine fusion. PMID:25666115

Concepts, requirements, and design approaches for building successful planning and scheduling systems

NASA Technical Reports Server (NTRS)

Hornstein, Rhoda Shaller; Willoughby, John K.

1991-01-01

Traditional practice of systems engineering management assumes requirements can be precisely determined and unambiguously defined prior to system design and implementation; practice further assumes requirements are held static during implementation. Human-computer decision support systems for service planning and scheduling applications do not conform well to these assumptions. Adaptation to the traditional practice of systems engineering management are required. Basic technology exists to support these adaptations. Additional innovations must be encouraged and nutured. Continued partnership between the programmatic and technical perspective assures proper balance of the impossible with the possible. Past problems have the following origins: not recognizing the unusual and perverse nature of the requirements for planning and scheduling; not recognizing the best starting point assumptions for the design; not understanding the type of system that being built; and not understanding the design consequences of the operations concept selected.

NASA Systems Engineering Handbook

NASA Technical Reports Server (NTRS)

2007-01-01

This handbook is intended to provide general guidance and information on systems engineering that will be useful to the NASA community. It provides a generic description of Systems Engineering (SE) as it should be applied throughout NASA. A goal of the handbook is to increase awareness and consistency across the Agency and advance the practice of SE. This handbook provides perspectives relevant to NASA and data particular to NASA. The coverage in this handbook is limited to general concepts and generic descriptions of processes, tools, and techniques. It provides information on systems engineering best practices and pitfalls to avoid. There are many Center-specific handbooks and directives as well as textbooks that can be consulted for in-depth tutorials. This handbook describes systems engineering as it should be applied to the development and implementation of large and small NASA programs and projects. NASA has defined different life cycles that specifically address the major project categories, or product lines, which are: Flight Systems and Ground Support (FS&GS), Research and Technology (R&T), Construction of Facilities (CoF), and Environmental Compliance and Restoration (ECR). The technical content of the handbook provides systems engineering best practices that should be incorporated into all NASA product lines. (Check the NASA On-Line Directives Information System (NODIS) electronic document library for applicable NASA directives on topics such as product lines.) For simplicity this handbook uses the FS&GS product line as an example. The specifics of FS&GS can be seen in the description of the life cycle and the details of the milestone reviews. Each product line will vary in these two areas; therefore, the reader should refer to the applicable NASA procedural requirements for the specific requirements for their life cycle and reviews. The engineering of NASA systems requires a systematic and disciplined set of processes that are applied recursively and iteratively for the design, development, operation, maintenance, and closeout of systems throughout the life cycle of the programs and projects.

24 CFR 200.934 - User fee system for the technical suitability of products program.

Code of Federal Regulations, 2012 CFR

2012-04-01

... section establishes fee requirements for the issuance of Structural Engineering Bulletins (SEBs), Mechanical Engineering Bulletins (MEBs), Truss Connector Bulletins (TCBs), Area Letters of Acceptance (ALAs... Department. (i) With respect to Mechanical Engineering Bulletins (MEBs), Structural Engineering Bulletins...

24 CFR 200.934 - User fee system for the technical suitability of products program.

Code of Federal Regulations, 2013 CFR

2013-04-01

... section establishes fee requirements for the issuance of Structural Engineering Bulletins (SEBs), Mechanical Engineering Bulletins (MEBs), Truss Connector Bulletins (TCBs), Area Letters of Acceptance (ALAs... Department. (i) With respect to Mechanical Engineering Bulletins (MEBs), Structural Engineering Bulletins...

24 CFR 200.934 - User fee system for the technical suitability of products program.

Code of Federal Regulations, 2014 CFR

2014-04-01

... section establishes fee requirements for the issuance of Structural Engineering Bulletins (SEBs), Mechanical Engineering Bulletins (MEBs), Truss Connector Bulletins (TCBs), Area Letters of Acceptance (ALAs... Department. (i) With respect to Mechanical Engineering Bulletins (MEBs), Structural Engineering Bulletins...

24 CFR 200.934 - User fee system for the technical suitability of products program.

Code of Federal Regulations, 2011 CFR

2011-04-01

... section establishes fee requirements for the issuance of Structural Engineering Bulletins (SEBs), Mechanical Engineering Bulletins (MEBs), Truss Connector Bulletins (TCBs), Area Letters of Acceptance (ALAs... Department. (i) With respect to Mechanical Engineering Bulletins (MEBs), Structural Engineering Bulletins...

From scenarios to domain models: processes and representations

NASA Astrophysics Data System (ADS)

Haddock, Gail; Harbison, Karan

1994-03-01

The domain specific software architectures (DSSA) community has defined a philosophy for the development of complex systems. This philosophy improves productivity and efficiency by increasing the user's role in the definition of requirements, increasing the systems engineer's role in the reuse of components, and decreasing the software engineer's role to the development of new components and component modifications only. The scenario-based engineering process (SEP), the first instantiation of the DSSA philosophy, has been adopted by the next generation controller project. It is also the chosen methodology of the trauma care information management system project, and the surrogate semi-autonomous vehicle project. SEP uses scenarios from the user to create domain models and define the system's requirements. Domain knowledge is obtained from a variety of sources including experts, documents, and videos. This knowledge is analyzed using three techniques: scenario analysis, task analysis, and object-oriented analysis. Scenario analysis results in formal representations of selected scenarios. Task analysis of the scenario representations results in descriptions of tasks necessary for object-oriented analysis and also subtasks necessary for functional system analysis. Object-oriented analysis of task descriptions produces domain models and system requirements. This paper examines the representations that support the DSSA philosophy, including reference requirements, reference architectures, and domain models. The processes used to create and use the representations are explained through use of the scenario-based engineering process. Selected examples are taken from the next generation controller project.

From Earth to Orbit: An assessment of transportation options

NASA Technical Reports Server (NTRS)

Gavin, Joseph G., Jr.; Blond, Edmund; Brill, Yvonne C.; Budiansky, Bernard; Cooper, Robert S.; Demisch, Wolfgang H.; Hawk, Clark W.; Kerrebrock, Jack L.; Lichtenberg, Byron K.; Mager, Artur

1992-01-01

The report assesses the requirements, benefits, technological feasibility, and roles of Earth-to-Orbit transportation systems and options that could be developed in support of future national space programs. Transportation requirements, including those for Mission-to-Planet Earth, Space Station Freedom assembly and operation, human exploration of space, space science missions, and other major civil space missions are examined. These requirements are compared with existing, planned, and potential launch capabilities, including expendable launch vehicles (ELV's), the Space Shuttle, the National Launch System (NLS), and new launch options. In addition, the report examines propulsion systems in the context of various launch vehicles. These include the Advanced Solid Rocket Motor (ASRM), the Redesigned Solid Rocket Motor (RSRM), the Solid Rocket Motor Upgrade (SRMU), the Space Shuttle Main Engine (SSME), the Space Transportation Main Engine (STME), existing expendable launch vehicle engines, and liquid-oxygen/hydrocarbon engines. Consideration is given to systems that have been proposed to accomplish the national interests in relatively cost effective ways, with the recognition that safety and reliability contribute to cost-effectiveness. Related resources, including technology, propulsion test facilities, and manufacturing capabilities are also discussed.

Engineering Aerothermal Analysis for X-34 Thermal Protection System Design

NASA Technical Reports Server (NTRS)

Wurster, Kathryn E.; Riley, Christopher J.; Zoby, E. Vincent

1998-01-01

Design of the thermal protection system for any hypersonic flight vehicle requires determination of both the peak temperatures over the surface and the heating-rate history along the flight profile. In this paper, the process used to generate the aerothermal environments required for the X-34 Testbed Technology Demonstrator thermal protection system design is described as it has evolved from a relatively simplistic approach based on engineering methods applied to critical areas to one of detailed analyses over the entire vehicle. A brief description of the trajectory development leading to the selection of the thermal protection system design trajectory is included. Comparisons of engineering heating predictions with wind-tunnel test data and with results obtained using a Navier-Stokes flowfield code and an inviscid/boundary layer method are shown. Good agreement is demonstrated among all these methods for both the ground-test condition and the peak heating flight condition. Finally, the detailed analysis using engineering methods to interpolate the surface-heating-rate results from the inviscid/boundary layer method to predict the required thermal environments is described and results presented.

Engineering Aerothermal Analysis for X-34 Thermal Protection System Design

NASA Technical Reports Server (NTRS)

Wurster, Kathryn E.; Riley, Christopher J.; Zoby, E. Vincent

1998-01-01

Design of the thermal protection system for any hypersonic flight vehicle requires determination of both the peak temperatures over the surface and the heating-rate history along the flight profile. In this paper, the process used to generate the aerothermal environments required for the X-34 Testbed Technology Demonstrator thermal protection system design is described as it has evolved from a relatively simplistic approach based on engineering methods applied to critical areas to one of detailed analyses over the entire vehicle. A brief description of the trajectory development leading to the selection of the thermal protection system design trajectory is included. Comparisons of engineering heating predictions with wind-tunnel test data and with results obtained using a Navier- Stokes flowfield code and an inviscid/boundary layer method are shown. Good agreement is demonstrated among all these methods for both the ground-test condition and the peak heating flight condition. Finally, the detailed analysis using engineering methods to interpolate the surface-heating-rate results from the inviscid/boundary layer method to predict the required thermal environments is described and results presented.

23 CFR 940.11 - Project implementation.

Code of Federal Regulations, 2011 CFR

2011-04-01

... projects funded with highway trust funds shall be based on a systems engineering analysis. (b) The analysis should be on a scale commensurate with the project scope. (c) The systems engineering analysis shall... definitions; (4) Analysis of alternative system configurations and technology options to meet requirements; (5...

23 CFR 940.11 - Project implementation.

Code of Federal Regulations, 2014 CFR

2014-04-01

... projects funded with highway trust funds shall be based on a systems engineering analysis. (b) The analysis should be on a scale commensurate with the project scope. (c) The systems engineering analysis shall... definitions; (4) Analysis of alternative system configurations and technology options to meet requirements; (5...

23 CFR 940.11 - Project implementation.

Code of Federal Regulations, 2012 CFR

2012-04-01

... projects funded with highway trust funds shall be based on a systems engineering analysis. (b) The analysis should be on a scale commensurate with the project scope. (c) The systems engineering analysis shall... definitions; (4) Analysis of alternative system configurations and technology options to meet requirements; (5...

23 CFR 940.11 - Project implementation.

Code of Federal Regulations, 2013 CFR

2013-04-01

... projects funded with highway trust funds shall be based on a systems engineering analysis. (b) The analysis should be on a scale commensurate with the project scope. (c) The systems engineering analysis shall... definitions; (4) Analysis of alternative system configurations and technology options to meet requirements; (5...

23 CFR 940.11 - Project implementation.

Code of Federal Regulations, 2010 CFR

2010-04-01

... projects funded with highway trust funds shall be based on a systems engineering analysis. (b) The analysis should be on a scale commensurate with the project scope. (c) The systems engineering analysis shall... definitions; (4) Analysis of alternative system configurations and technology options to meet requirements; (5...

System controls challenges of hypersonic combined-cycle engine powered vehicles

NASA Technical Reports Server (NTRS)

Morrison, Russell H.; Ianculescu, George D.

1992-01-01

Hypersonic aircraft with air-breathing engines have been described as the most complex and challenging air/space vehicle designs ever attempted. This is particularly true for aircraft designed to accelerate to orbital velocities. The propulsion system for the National Aerospace Plane will be an active factor in maintaining the aircraft on course. Typically addressed are the difficulties with the aerodynamic vehicle design and development, materials limitations and propulsion performance. The propulsion control system requires equal materials limitations and propulsion performance. The propulsion control system requires equal concern. Far more important than merely a subset of propulsion performance, the propulsion control system resides at the crossroads of trajectory optimization, engine static performance, and vehicle-engine configuration optimization. To date, solutions at these crossroads are multidisciplinary and generally lag behind the broader performance issues. Just how daunting these demands will be is suggested. A somewhat simplified treatment of the behavioral characteristics of hypersonic aircraft and the issues associated with their air-breathing propulsion control system design are presented.

Development and experimental validation of computational methods to simulate abnormal thermal and structural environments

NASA Astrophysics Data System (ADS)

Moya, J. L.; Skocypec, R. D.; Thomas, R. K.

1993-09-01

Over the past 40 years, Sandia National Laboratories (SNL) has been actively engaged in research to improve the ability to accurately predict the response of engineered systems to abnormal thermal and structural environments. These engineered systems contain very hazardous materials. Assessing the degree of safety/risk afforded the public and environment by these engineered systems, therefore, is of upmost importance. The ability to accurately predict the response of these systems to accidents (to abnormal environments) is required to assess the degree of safety. Before the effect of the abnormal environment on these systems can be determined, it is necessary to ascertain the nature of the environment. Ascertaining the nature of the environment, in turn, requires the ability to physically characterize and numerically simulate the abnormal environment. Historically, SNL has demonstrated the level of safety provided by these engineered systems by either of two approaches: a purely regulatory approach, or by a probabilistic risk assessment (PRA). This paper will address the latter of the two approaches.

Model based systems engineering for astronomical projects

NASA Astrophysics Data System (ADS)

Karban, R.; Andolfato, L.; Bristow, P.; Chiozzi, G.; Esselborn, M.; Schilling, M.; Schmid, C.; Sommer, H.; Zamparelli, M.

2014-08-01

Model Based Systems Engineering (MBSE) is an emerging field of systems engineering for which the System Modeling Language (SysML) is a key enabler for descriptive, prescriptive and predictive models. This paper surveys some of the capabilities, expectations and peculiarities of tools-assisted MBSE experienced in real-life astronomical projects. The examples range in depth and scope across a wide spectrum of applications (for example documentation, requirements, analysis, trade studies) and purposes (addressing a particular development need, or accompanying a project throughout many - if not all - its lifecycle phases, fostering reuse and minimizing ambiguity). From the beginnings of the Active Phasing Experiment, through VLT instrumentation, VLTI infrastructure, Telescope Control System for the E-ELT, until Wavefront Control for the E-ELT, we show how stepwise refinements of tools, processes and methods have provided tangible benefits to customary system engineering activities like requirement flow-down, design trade studies, interfaces definition, and validation, by means of a variety of approaches (like Model Checking, Simulation, Model Transformation) and methodologies (like OOSEM, State Analysis)

Working on the Boundaries: Philosophies and Practices of the Design Process

NASA Technical Reports Server (NTRS)

Ryan, R.; Blair, J.; Townsend, J.; Verderaime, V.

1996-01-01

While systems engineering process is a program formal management technique and contractually binding, the design process is the informal practice of achieving the design project requirements throughout all design phases of the systems engineering process. The design process and organization are systems and component dependent. Informal reviews include technical information meetings and concurrent engineering sessions, and formal technical discipline reviews are conducted through the systems engineering process. This paper discusses and references major philosophical principles in the design process, identifies its role in interacting systems and disciplines analyses and integrations, and illustrates the process application in experienced aerostructural designs.

30 CFR 250.1629 - Additional production and fuel gas system requirements.

Code of Federal Regulations, 2012 CFR

2012-07-01

... operating range. (2) Engine exhaust. You must equip engine exhausts to comply with the insulation and... structure. (4) Fire- and gas-detection system. (i) Fire (flame, heat, or smoke) sensors shall be installed...

An inference engine for embedded diagnostic systems

NASA Technical Reports Server (NTRS)

Fox, Barry R.; Brewster, Larry T.

1987-01-01

The implementation of an inference engine for embedded diagnostic systems is described. The system consists of two distinct parts. The first is an off-line compiler which accepts a propositional logical statement of the relationship between facts and conclusions and produces data structures required by the on-line inference engine. The second part consists of the inference engine and interface routines which accept assertions of fact and return the conclusions which necessarily follow. Given a set of assertions, it will generate exactly the conclusions which logically follow. At the same time, it will detect any inconsistencies which may propagate from an inconsistent set of assertions or a poorly formulated set of rules. The memory requirements are fixed and the worst case execution times are bounded at compile time. The data structures and inference algorithms are very simple and well understood. The data structures and algorithms are described in detail. The system has been implemented on Lisp, Pascal, and Modula-2.

Space Launch System Base Heating Test: Sub-Scale Rocket Engine/Motor Design, Development & Performance Analysis

NASA Technical Reports Server (NTRS)

Mehta, Manish; Seaford, Mark; Kovarik, Brian; Dufrene, Aaron; Solly, Nathan

2014-01-01

ATA-002 Technical Team has successfully designed, developed, tested and assessed the SLS Pathfinder propulsion systems for the Main Base Heating Test Program. Major Outcomes of the Pathfinder Test Program: Reach 90% of full-scale chamber pressure Achieved all engine/motor design parameter requirements Reach steady plume flow behavior in less than 35 msec Steady chamber pressure for 60 to 100 msec during engine/motor operation Similar model engine/motor performance to full-scale SLS system Mitigated nozzle throat and combustor thermal erosion Test data shows good agreement with numerical prediction codes Next phase of the ATA-002 Test Program Design & development of the SLS OML for the Main Base Heating Test Tweak BSRM design to optimize performance Tweak CS-REM design to increase robustness MSFC Aerosciences and CUBRC have the capability to develop sub-scale propulsion systems to meet desired performance requirements for short-duration testing.

The Development of Environmental Barrier Coatings for SiCSiC Ceramic Matrix Composites: Challenges and Opportunities

NASA Technical Reports Server (NTRS)

Zhu, Dongming

2014-01-01

Environmental barrier coatings (EBCs) and SiC/SiC ceramic matrix composites (CMCs) systems will play a crucial role in future turbine engines for hot-section component applications because of their ability to significantly increase engine operating temperatures, reduce engine weight and cooling requirements. The development of prime-reliant environmental barrier coatings is a key to enable the applications of the envisioned CMC components to help achieve next generation engine performance and durability goals. This paper will primarily address the performance requirements and design considerations of environmental barrier coatings for turbine engine applications. The emphasis is placed on current candidate environmental barrier coating systems for SiCSiC CMCs, their performance benefits and design limitations in long-term operation and combustion environments. Major technical barriers in developing advanced environmental barrier coating systems, the coating integrations with next generation CMC turbine components having improved environmental stability, cyclic durability and system performance will be described. The development trends for turbine environmental barrier coating systems by utilizing improved compositions, state-of-the-art processing methods, and simulated environment testing and durability modeling will be discussed.

Site systems engineering fiscal year 1999 multi-year work plan (MYWP) update for WBS 1.8.2.2

DOE Office of Scientific and Technical Information (OSTI.GOV)

GRYGIEL, M.L.

1998-10-08

Manage the Site Systems Engineering process to provide a traceable integrated requirements-driven, and technically defensible baseline. Through the Site Integration Group(SIG), Systems Engineering ensures integration of technical activities across all site projects. Systems Engineering's primary interfaces are with the RL Project Managers, the Project Direction Office and with the Project Major Subcontractors, as well as with the Site Planning organization. Systems Implementation: (1) Develops, maintains, and controls the site integrated technical baseline, ensures the Systems Engineering interfaces between projects are documented, and maintain the Site Environmental Management Specification. (2) Develops and uses dynamic simulation models for verification of the baselinemore » and analysis of alternatives. (3) Performs and documents fictional and requirements analyses. (4) Works with projects, technology management, and the SIG to identify and resolve technical issues. (5) Supports technical baseline information for the planning and budgeting of the Accelerated Cleanup Plan, Multi-Year Work Plans, Project Baseline Summaries as well as performance measure reporting. (6) Works with projects to ensure the quality of data in the technical baseline. (7) Develops, maintains and implements the site configuration management system.« less

JPL Counterfeit Parts Avoidance

NASA Technical Reports Server (NTRS)

Risse, Lori

2012-01-01

SPACE ARCHITECTURE / ENGINEERING: It brings an extreme test bed for both technologies/concepts as well as procedures/processes. Design and construction (engineering) always go together, especially with complex systems. Requirements (objectives) are crucial. More important than the answers are the questions/Requirements/Tools-Techniques/Processes. Different environments force architects and engineering to think out of the box. For instance there might not be gravity forces. Architectural complex problems have common roots: in Space and on Earth. Let us bring Space down on Earth so we can keep sending Mankind to the stars from a better world. Have fun being architects and engineers...!!! This time is amazing and historical. We are changing the way we inhabit the solar systems!

322-R2U2 Engineering Assessment - August 2015

DOE Office of Scientific and Technical Information (OSTI.GOV)

Abri, M.; Griffin, D.

This Engineering Assessment and Certification of Integrity of retention tank system 322-R2 has been prepared for tank systems that store and neutralizes hazardous waste and have secondary containment. The regulations require that this assessment be completed periodically and certified by an independent, qualified, California-registered professional engineer. Abri Environmental Engineering performed an inspection of the 322-R2 Tank system at the Lawrence Livermore National Laboratory (LLNL) in Livermore, CA. Mr. William W. Moore, P.E., conducted this inspection on March 16, 2015. Mr. Moore is a California Registered Civil Engineer, with extensive experience in civil engineering, and hazardous waste management.

Fluid design studies of integrated modular engine system

NASA Technical Reports Server (NTRS)

Frankenfield, Bruce; Carek, Jerry

1993-01-01

A study was performed to develop a fluid system design and show the feasibility of constructing an integrated modular engine (IME) configuration, using an expander cycle engine. The primary design goal of the IME configuration was to improve the propulsion system reliability. The IME fluid system was designed as a single fault tolerant system, while minimizing the required fluid components. This study addresses the design of the high pressure manifolds, turbopumps and thrust chambers for the IME configuration. A physical layout drawing was made, which located each of the fluid system components, manifolds and thrust chambers. Finally, a comparison was made between the fluid system designs of an IME system and a non-network (clustered) engine system.

76 FR 77854 - Notice of Intent To Seek Approval To Establish an Information Collection

Federal Register 2010, 2011, 2012, 2013, 2014

2011-12-14

... Reporting Requirements for the Engineering Research Centers (ERCs). OMB Number: 3145-NEW. Expiration Date of.... Abstract Proposed Project The Engineering Research Centers (ERC) program supports an integrated, interdisciplinary research environment to advance fundamental engineering knowledge and engineered systems; educate...

Systems engineering: A formal approach. Part 1: System concepts

NASA Astrophysics Data System (ADS)

Vanhee, K. M.

1993-03-01

Engineering is the scientific discipline focused on the creation of new artifacts that are supposed to be of some use to our society. Different types of artifacts require different engineering approaches. However, in all these disciplines the development of a new artifact is divided into stages. Three stages can always be recognized: Analysis, Design, and Realization. The book considers only the first two stages of the development process. It focuses on a specific type of artifacts, called discrete dynamic systems. These systems consist of active components of actors that consume and produce passive components or tokens. Three subtypes are studied in more detail: business systems (like a factory or restaurant), information systems (whether automated or not), and automated systems (systems that are controlled by an automated information system). The first subtype is studied by industrial engineers, the last by software engineers and electrical engineers, whereas the second is a battlefield for all three disciplines. The union of these disciplines is called systems engineering.

Customer requirements process

NASA Technical Reports Server (NTRS)

Russell, Yvonne; Falsetti, Christine M.

1991-01-01

Customer requirements are presented through three viewgraphs. One graph presents the range of services, which include requirements management, network engineering, operations, and applications support. Another viewgraph presents the project planning process. The third viewgraph presents the programs and/or projects actively supported including life sciences, earth science and applications, solar system exploration, shuttle flight engineering, microgravity science, space physics, and astrophysics.

System Engineering on the Use for Ares I,V - the Simpler, the Better

NASA Technical Reports Server (NTRS)

Kelly, William; Greene, William D.; Greasley, Paul; Ackerman, Peter C.

2008-01-01

The Ares I and Ares V Vehicles will utilize the J-2X rocket engine developed for NASA by the Pratt & Whitney Rocketdyne Company. The J-2X is an improved higher power version of the original J-2 engine used during the Apollo program. With higher power and updated requirements for safety and performance, the J-2X becomes a new engine using state-of-the-art design methodology, materials and manufacturing processes. The implementation of Systems Engineering (SE) principles enables the rapid J-2X development program to remain aligned with the ARES I and V vehicle programs, Meeting the aggressive development schedule is a challenge. Coordinating the best expertise thai NASA and PWR have to offer requires effectively utilizing resources at multiple sites. This presents formidable communication challenges. SE allows honest and open discussions of issues and problems. This simple idea is often overlooked in large and complex SE programs. Regular and effective meetings linking SE objectives to component designs are used to voice differences of opinions with customer and contractor in attendance so that the best mutual decisions can be made on the shortest possible schedule. Regular technical interchange meetings on secure program wide computer networks and CM processes are effective,in the "Controlled Change" process that exemplifies good SE. Good communication is a key effective SE implementation. The System of Systems approach is the vision of the Orion program which facilitates the establishment of dynamic SE processes at all levels including the engine. SE enables requirements evolution by facilitating organizational and process agility. Flow down and distribution of requirements is controlled by Allocation Reports which breakdown numerical design objectives (weight, reliability, etc.) into quanta goals for each component area. Linked databases of design and verification requirements helps eliminate redundancy and potential mistakes inherent m separated systems. Another tool, the Architecture Design Description, is being used to control J-2X system architecture and effectively communicate configuration changes to those involved in the design process. But the proof is in successful program accomplishment. The SE is the methodology being used to meet the challenge of completing J-2X engine certification 2 years ahead of any engine program ever developed at PWR. The Ares I SE system of systems has delivered according to expectations thus far. All major design reviews (SRR. PDR, CDR) have been successfully conducted to satisfy overall program objectives using SE as the basis for accomplishment. The paper describes SE tools and techniques utilized to achieve this success.

Commercialization of dish-Stirling solar terrestrial systems

NASA Technical Reports Server (NTRS)

Ross, Brad; Penswick, Barry; White, Maury; Cooper, Martin; Farbman, Gerald

1990-01-01

The requirements for dish-Stirling commercialization are described. The requirements for practical terrestrial power systems, both technical and economic, are described. Solar energy availability, with seasonal and regional variations, is discussed. The advantages and disadvantages of hybrid operation are listed. The two systems described use either a 25-kW free-piston Stirling hydraulic engine or a 5-kW kinematic Stirling engine. Both engines feature long-life characteristics that result from the use of welded metal bellows as hermetic seals between the working gas and the crankcase fluid. The advantages of the systems, the state of the technology, and the challenges that remain are discussed. Technology transfer between solar terrestrial Stirling applications and other Stirling applications is predicted to be important and synergistic.

F-15/nonaxisymmetric nozzle system integration study support program

NASA Technical Reports Server (NTRS)

Stevens, H. L.

1978-01-01

Nozzle and cooling methods were defined and analyzed to provide a viable system for demonstration 2-D nozzle technology on the F-15 aircraft. Two candidate cooling systems applied to each nozzle were evaluated. The F-100 engine mount and case modifications requirements were analyzed and the actuation and control system requirements for two dimensional nozzles were defined. Nozzle performance changes relative to the axisymmetric baseline nozzle were evaluated and performance and weight characteristics for axisymmetric reference configurations were estimated. The infrared radiation characteristics of these nozzles installed on the F-100 engine were predicted. A full scale development plan with associated costs to carry the F100 engine/two-dimensional (2-D) nozzle through flight tests was defined.

Engineering performance metrics

NASA Astrophysics Data System (ADS)

Delozier, R.; Snyder, N.

1993-03-01

Implementation of a Total Quality Management (TQM) approach to engineering work required the development of a system of metrics which would serve as a meaningful management tool for evaluating effectiveness in accomplishing project objectives and in achieving improved customer satisfaction. A team effort was chartered with the goal of developing a system of engineering performance metrics which would measure customer satisfaction, quality, cost effectiveness, and timeliness. The approach to developing this system involved normal systems design phases including, conceptual design, detailed design, implementation, and integration. The lessons teamed from this effort will be explored in this paper. These lessons learned may provide a starting point for other large engineering organizations seeking to institute a performance measurement system accomplishing project objectives and in achieving improved customer satisfaction. To facilitate this effort, a team was chartered to assist in the development of the metrics system. This team, consisting of customers and Engineering staff members, was utilized to ensure that the needs and views of the customers were considered in the development of performance measurements. The development of a system of metrics is no different than the development of any type of system. It includes the steps of defining performance measurement requirements, measurement process conceptual design, performance measurement and reporting system detailed design, and system implementation and integration.

Systems integrated human engineering on the Navy's rapid acquisition of manufactured parts/test and integration facility

NASA Technical Reports Server (NTRS)

Gallaway, Glen R.

1987-01-01

Human Engineering in many projects is at best a limited support function. In this Navy project the Human Engineering function is an integral component of the systems design and development process. Human Engineering is a member of the systems design organization. This ensures that people considerations are: (1) identified early in the project; (2) accounted for in the specifications; (3) incorporated into the design; and (4) the tested product meets the needs and expectations of the people while meeting the overall systems requirements. The project exemplifies achievements that can be made by the symbiosis between systems designers, engineers and Human Engineering. This approach increases Human Engineering's effectiveness and value to a project because it becomes an accepted, contributing team member. It is an approach to doing Human Engineering that should be considered for most projects. The functional and organizational issues giving this approach strength are described.

Key Reliability Drivers of Liquid Propulsion Engines and A Reliability Model for Sensitivity Analysis

NASA Technical Reports Server (NTRS)

Huang, Zhao-Feng; Fint, Jeffry A.; Kuck, Frederick M.

2005-01-01

This paper is to address the in-flight reliability of a liquid propulsion engine system for a launch vehicle. We first establish a comprehensive list of system and sub-system reliability drivers for any liquid propulsion engine system. We then build a reliability model to parametrically analyze the impact of some reliability parameters. We present sensitivity analysis results for a selected subset of the key reliability drivers using the model. Reliability drivers identified include: number of engines for the liquid propulsion stage, single engine total reliability, engine operation duration, engine thrust size, reusability, engine de-rating or up-rating, engine-out design (including engine-out switching reliability, catastrophic fraction, preventable failure fraction, unnecessary shutdown fraction), propellant specific hazards, engine start and cutoff transient hazards, engine combustion cycles, vehicle and engine interface and interaction hazards, engine health management system, engine modification, engine ground start hold down with launch commit criteria, engine altitude start (1 in. start), Multiple altitude restart (less than 1 restart), component, subsystem and system design, manufacturing/ground operation support/pre and post flight check outs and inspection, extensiveness of the development program. We present some sensitivity analysis results for the following subset of the drivers: number of engines for the propulsion stage, single engine total reliability, engine operation duration, engine de-rating or up-rating requirements, engine-out design, catastrophic fraction, preventable failure fraction, unnecessary shutdown fraction, and engine health management system implementation (basic redlines and more advanced health management systems).

Study of an engine flow diverter system for a large scale ejector powered aircraft model

NASA Technical Reports Server (NTRS)

Springer, R. J.; Langley, B.; Plant, T.; Hunter, L.; Brock, O.

1981-01-01

Requirements were established for a conceptual design study to analyze and design an engine flow diverter system and to include accommodations for an ejector system in an existing 3/4 scale fighter model equipped with YJ-79 engines. Model constraints were identified and cost-effective limited modification was proposed to accept the ejectors, ducting and flow diverter valves. Complete system performance was calculated and a versatile computer program capable of analyzing any ejector system was developed.

14 CFR Appendix K to Part 25 - Extended Operations (ETOPS)

Code of Federal Regulations, 2014 CFR

2014-01-01

... that is time-limited. K25.1.4Propulsion systems. (a) Fuel system design. Fuel necessary to complete an... does not apply to airplanes with a required flight engineer. (b) APU design. If an APU is needed to..., whichever is lower, and run for the remainder of any flight . (c) Engine oil tank design. The engine oil...

14 CFR Appendix K to Part 25 - Extended Operations (ETOPS)

Code of Federal Regulations, 2010 CFR

2010-01-01

... that is time-limited. K25.1.4Propulsion systems. (a) Fuel system design. Fuel necessary to complete an... does not apply to airplanes with a required flight engineer. (b) APU design. If an APU is needed to..., whichever is lower, and run for the remainder of any flight . (c) Engine oil tank design. The engine oil...

14 CFR Appendix K to Part 25 - Extended Operations (ETOPS)

Code of Federal Regulations, 2013 CFR

2013-01-01

... that is time-limited. K25.1.4Propulsion systems. (a) Fuel system design. Fuel necessary to complete an... does not apply to airplanes with a required flight engineer. (b) APU design. If an APU is needed to..., whichever is lower, and run for the remainder of any flight . (c) Engine oil tank design. The engine oil...

14 CFR Appendix K to Part 25 - Extended Operations (ETOPS)

Code of Federal Regulations, 2012 CFR

2012-01-01

... that is time-limited. K25.1.4Propulsion systems. (a) Fuel system design. Fuel necessary to complete an... does not apply to airplanes with a required flight engineer. (b) APU design. If an APU is needed to..., whichever is lower, and run for the remainder of any flight . (c) Engine oil tank design. The engine oil...

Information Integration for Concurrent Engineering (IICE) IDEF3 Process Description Capture Method Report

DTIC Science & Technology

1992-05-01

methodology, knowledge acquisition, 140 requirements definition, information systems, information engineering, 16. PRICE CODE systems engineering...and knowledge resources. Like manpower, materials, and machines, information and knowledge assets are recognized as vital resources that can be...evolve towards an information -integrated enterprise. These technologies are designed to leverage information and knowledge resources as the key

Orbit Transfer Vehicle (OTV) advanced expander cycle engine point design study. Volume 1: Executive summary

NASA Technical Reports Server (NTRS)

1981-01-01

The objective of the study was to generate the system design of a performance-optimized, advanced LOX/hydrogen expander cycle space engine. The engine requirements are summarized, and the development and operational experience with the expander cycle RL10 engine were reviewed. The engine development program is outlined.

46 CFR 58.10-10 - Diesel engine installations.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 46 Shipping 2 2011-10-01 2011-10-01 false Diesel engine installations. 58.10-10 Section 58.10-10... MACHINERY AND RELATED SYSTEMS Internal Combustion Engine Installations § 58.10-10 Diesel engine installations. (a) The requirements of § 58.10-5 (a), (c), and (d) shall apply to diesel engine installations...

46 CFR 58.10-10 - Diesel engine installations.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 2 2010-10-01 2010-10-01 false Diesel engine installations. 58.10-10 Section 58.10-10... MACHINERY AND RELATED SYSTEMS Internal Combustion Engine Installations § 58.10-10 Diesel engine installations. (a) The requirements of § 58.10-5 (a), (c), and (d) shall apply to diesel engine installations...

46 CFR 58.10-10 - Diesel engine installations.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 46 Shipping 2 2014-10-01 2014-10-01 false Diesel engine installations. 58.10-10 Section 58.10-10... MACHINERY AND RELATED SYSTEMS Internal Combustion Engine Installations § 58.10-10 Diesel engine installations. (a) The requirements of § 58.10-5 (a), (c), and (d) shall apply to diesel engine installations...

46 CFR 58.10-10 - Diesel engine installations.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 46 Shipping 2 2012-10-01 2012-10-01 false Diesel engine installations. 58.10-10 Section 58.10-10... MACHINERY AND RELATED SYSTEMS Internal Combustion Engine Installations § 58.10-10 Diesel engine installations. (a) The requirements of § 58.10-5 (a), (c), and (d) shall apply to diesel engine installations...

Study of advanced rotary combustion engines for commuter aircraft

NASA Technical Reports Server (NTRS)

Berkowitz, M.; Jones, C.; Myers, D.

1983-01-01

Performance, weight, size, and maintenance data for advanced rotary aircraft engines suitable for comparative commuter aircraft system evaluation studies of alternate engine candidates are provided. These are turbocharged, turbocompounded, direct injected, stratified charge rotary engines. Hypothetical engines were defined (an RC4-74 at 895 kW and an RC6-87 at 1490 kW) based on the technologies and design approaches used in the highly advanced engine of a study of advanced general aviation rotary engines. The data covers the size range of shaft power from 597 kW (800 hp) to 1865 kW (2500 hp) and is in the form of drawings, tables, curves and written text. These include data on internal geometry and configuration, installation information, turbocharging and turbocompounding arrangements, design features and technologies, engine cooling, fuels, scaling for weight size BSFC and heat rejection for varying horsepower, engine operating and performance data, and TBO and maintenance requirements. The basic combustion system was developed and demonstrated; however the projected power densities and performance efficiencies require increases in engine internal pressures, thermal loading, and rotative speed.

78 FR 58153 - Prevailing Rate Systems; North American Industry Classification System Based Federal Wage System...

Federal Register 2010, 2011, 2012, 2013, 2014

2013-09-23

... engine and engine parts manufacturing,'' ``Motor vehicle electrical and electronic equipment... manufacturing,'' ``Other motor vehicle electrical and electronic equipment manufacturing,'' and ``All other motor vehicle parts manufacturing'' in the second column from the list of required NAICS codes for the...

Prototype design of a collision protection system for cab car engineers.

DOT National Transportation Integrated Search

2013-03-01

The objective of this project was to develop and analyze a passive system to protect a cab car engineer from secondary impact injuries that might be experienced due to impact with the cab console. The primary requirement for the system was the abilit...

Evaluation of a staged fuel combustor for turboprop engines

NASA Technical Reports Server (NTRS)

Verdouw, A. J.

1976-01-01

Proposed EPA emission regulations require emission reduction by 1979 for various gas turbine engine classes. Extensive combustion technology advancements are required to meet the proposed regulations. The T56 turboprop engine requires CO, UHC, and smoke reduction. A staged fuel combustor design was tested on a combustion rig to evaluate emission reduction potential in turboprop engines from fuel zoning. The can-type combustor has separately fueled-pilot and main combustion zones in series. The main zone fueling system was arranged for potential incorporation into the T56 with minor or no modifications to the basic engine. Three combustor variable geometry systems were incorporated to evaluate various airflow distributions. Emission results with fixed geometry operation met all proposed EPA regulations over the EPA LTO cycle. CO reduction was 82 percent, UHC reduction was 96 percent, and smoke reduction was 84 percent. NOx increased 14 percent over the LTO cycle. At high power, NOx reduction was 40 to 55 percent. This NOx reduction has potential application to stationary gas turbine powerplants which have different EPA regulations.

Engine health monitoring: An advanced system

NASA Technical Reports Server (NTRS)

Dyson, R. J. E.

1981-01-01

The advanced propulsion monitoring system is described. The system was developed in order to fulfill a growing need for effective engine health monitoring. This need is generated by military requirements for increased performance and efficiency in more complex propulsion systems, while maintaining or improving the cost to operate. This program represents a vital technological step in the advancement of the state of the art for monitoring systems in terms of reliability, flexibility, accuracy, and provision of user oriented results. It draws heavily on the technology and control theory developed for modern, complex, electronically controlled engines and utilizes engine information which is a by-product of such a system.

U.S. Air Force Engineering and Services Hardware Requirements

DOT National Transportation Integrated Search

1991-04-01

This document proposes a path to meet the communications-computer systems (CSC) requirements of Air Force Engineering and Services (E and S) in the mid-to-late 1990s. It reflects the philosophies that guide E and S upper- level management as it carri...

Kerosene-base fuels in small gasoline engines. Final report

DOE Office of Scientific and Technical Information (OSTI.GOV)

Failla, C.C.; Pouring, A.A.

1991-01-01

This document presents the results of an engineering study to demonstrate the technology for converting small gasoline spark-ignited engines, to burn kerosene type fuels to power small generators (0.5 to 3.0 kw). Commercially available (plus those in the developmental stage), reciprocating, two-stroke, four stroke and rotary engines were evaluated for their conversion potential. Unique combustion systems were identified and trade-off studies conducted on engine type, combustion systems, and modification required to burn kerosene type fuels, with special emphasis given to minimizing life cycle cost. Recommendations for the most feasible system are given.

Transition in Gas Turbine Control System Architecture: Modular, Distributed, and Embedded

NASA Technical Reports Server (NTRS)

Culley, Dennis

2010-01-01

Controls systems are an increasingly important component of turbine-engine system technology. However, as engines become more capable, the control system itself becomes ever more constrained by the inherent environmental conditions of the engine; a relationship forced by the continued reliance on commercial electronics technology. A revolutionary change in the architecture of turbine-engine control systems will change this paradigm and result in fully distributed engine control systems. Initially, the revolution will begin with the physical decoupling of the control law processor from the hostile engine environment using a digital communications network and engine-mounted high temperature electronics requiring little or no thermal control. The vision for the evolution of distributed control capability from this initial implementation to fully distributed and embedded control is described in a roadmap and implementation plan. The development of this plan is the result of discussions with government and industry stakeholders

Applicability of a Crack-Detection System for Use in Rotor Disk Spin Test Experiments Being Evaluated

NASA Technical Reports Server (NTRS)

Abdul-Aziz, Ali; Baaklini, George Y.; Roth, Don J.

2004-01-01

Engine makers and aviation safety government institutions continue to have a strong interest in monitoring the health of rotating components in aircraft engines to improve safety and to lower maintenance costs. To prevent catastrophic failure (burst) of the engine, they use nondestructive evaluation (NDE) and major overhauls for periodic inspections to discover any cracks that might have formed. The lowest cost fluorescent penetrant inspection NDE technique can fail to disclose cracks that are tightly closed during rest or that are below the surface. The NDE eddy current system is more effective at detecting both crack types, but it requires careful setup and operation and only a small portion of the disk can be practically inspected. So that sensor systems can sustain normal function in a severe environment, health-monitoring systems require the sensor system to transmit a signal if a crack detected in the component is above a predetermined length (but below the length that would lead to failure) and lastly to act neutrally upon the overall performance of the engine system and not interfere with engine maintenance operations. Therefore, more reliable diagnostic tools and high-level techniques for detecting damage and monitoring the health of rotating components are very essential in maintaining engine safety and reliability and in assessing life.

Engineering Antifragile Systems: A Change In Design Philosophy

NASA Technical Reports Server (NTRS)

Jones, Kennie H.

2014-01-01

While technology has made astounding advances in the last century, problems are confronting the engineering community that must be solved. Cost and schedule of producing large systems are increasing at an unsustainable rate and these systems often do not perform as intended. New systems are required that may not be achieved by current methods. To solve these problems, NASA is working to infuse concepts from Complexity Science into the engineering process. Some of these problems may be solved by a change in design philosophy. Instead of designing systems to meet known requirements that will always lead to fragile systems at some degree, systems should be designed wherever possible to be antifragile: designing cognitive cyberphysical systems that can learn from their experience, adapt to unforeseen events they face in their environment, and grow stronger in the face of adversity. Several examples are presented of on ongoing research efforts to employ this philosophy.

The Large Synoptic Survey Telescope OCS and TCS models

NASA Astrophysics Data System (ADS)

Schumacher, German; Delgado, Francisco

2010-07-01

The Large Synoptic Survey Telescope (LSST) is a project envisioned as a system of systems with demanding science, technical, and operational requirements, that must perform as a fully integrated unit. The design and implementation of such a system poses big engineering challenges when performing requirements analysis, detailed interface definitions, operational modes and control strategy studies. The OMG System Modeling Language (SysML) has been selected as the framework for the systems engineering analysis and documentation for the LSST. Models for the overall system architecture and different observatory subsystems have been built describing requirements, structure, interfaces and behavior. In this paper we show the models for the Observatory Control System (OCS) and the Telescope Control System (TCS), and how this methodology has helped in the clarification of the design and requirements. In one common language, the relationships of the OCS, TCS, Camera and Data management subsystems are captured with models of the structure, behavior, requirements and the traceability between them.

Big system: Interactive graphics for the engineer

NASA Technical Reports Server (NTRS)

Quenneville, C. E.

1975-01-01

The BCS Interactive Graphics System (BIG System) approach to graphics was presented, along with several significant engineering applications. The BIG System precompiler, the graphics support library, and the function requirements of graphics applications are discussed. It was concluded that graphics standardization and a device independent code can be developed to assure maximum graphic terminal transferability.

Design of automatic startup and shutdown logic for a Brayton-cycle 2- to 15-kilowatt engine

NASA Technical Reports Server (NTRS)

Vrancik, J. E.; Bainbridge, R. C.

1975-01-01

The NASA Lewis Research Center is conducting a closed-Brayton-cycle power conversion system technology program in which a complete power system (engine) has been designed and demonstrated. This report discusses the design of automatic startup and shutdown logic circuits as a modification to the control system presently used in this demonstration engine. This modification was primarily intended to make starting the engine as simple and safe as possible and to allow the engine to be run unattended. In the modified configuration the engine is started by turning the control console power on and pushing the start button after preheating the gas loop. No other operator action is required to effect a complete startup. Shutdown, if one is required, is also effected by a simple stop button. The automatic startup and shutdown of the engine have been successfully and purposefully demonstrated more than 50 times at the Lewis Research Center during 10,000 hours of unattended operation. The net effect of this modification is an engine that can be safely started and stopped by relatively untrained personnel. The approach lends itself directly to remote unattended operation.

Acquisition Cycle Time: Defining the Problem

DTIC Science & Technology

2016-04-01

oversight and prescribe a more laissez - faire approach to acquisition. Others diagnose unaffordable ambitions and unnecessarily demanding requirements, and...treated as a subsystem. Systems engineering organizations need to engineer the software/avionics system – a change in leadership technical background

The significance of requirements engineering for the medical domain.

PubMed

Kossmann, Mario

2014-07-01

This paper aims to raise awareness of the importance of Requirements Engineering (RE) for the successful and efficient development of high-quality systems and products for the medical domain. It does so by providing an introduction to RE from the viewpoints of project and programme management and systems engineering in general and by illustrating the usefulness of a sound RE approach to the development of a local healthcare system in a deprived region in central Africa. The paper concludes that RE is just as crucial for the development of systems and products in the medical domain, as it is for the development of systems in the aerospace industry or software systems in the consumer electronics industry; while the degree of detail and formality of how RE is used has to be tailored to fit the context in question.

Knowledge-based requirements analysis for automating software development

NASA Technical Reports Server (NTRS)

Markosian, Lawrence Z.

1988-01-01

We present a new software development paradigm that automates the derivation of implementations from requirements. In this paradigm, informally-stated requirements are expressed in a domain-specific requirements specification language. This language is machine-understable and requirements expressed in it are captured in a knowledge base. Once the requirements are captured, more detailed specifications and eventually implementations are derived by the system using transformational synthesis. A key characteristic of the process is that the required human intervention is in the form of providing problem- and domain-specific engineering knowledge, not in writing detailed implementations. We describe a prototype system that applies the paradigm in the realm of communication engineering: the prototype automatically generates implementations of buffers following analysis of the requirements on each buffer.

Engineering computer graphics in gas turbine engine design, analysis and manufacture

NASA Technical Reports Server (NTRS)

Lopatka, R. S.

1975-01-01

A time-sharing and computer graphics facility designed to provide effective interactive tools to a large number of engineering users with varied requirements was described. The application of computer graphics displays at several levels of hardware complexity and capability is discussed, with examples of graphics systems tracing gas turbine product development, beginning with preliminary design through manufacture. Highlights of an operating system stylized for interactive engineering graphics is described.

14 CFR 27.955 - Fuel flow.

Code of Federal Regulations, 2013 CFR

2013-01-01

... STANDARDS: NORMAL CATEGORY ROTORCRAFT Powerplant Fuel System § 27.955 Fuel flow. (a) General. The fuel system for each engine must be shown to provide the engine with at least 100 percent of the fuel required... to rotorcraft flight attitudes. (4) The critical fuel pump (for pump-fed systems) is installed to...

14 CFR 27.955 - Fuel flow.

Code of Federal Regulations, 2014 CFR

2014-01-01

... STANDARDS: NORMAL CATEGORY ROTORCRAFT Powerplant Fuel System § 27.955 Fuel flow. (a) General. The fuel system for each engine must be shown to provide the engine with at least 100 percent of the fuel required... to rotorcraft flight attitudes. (4) The critical fuel pump (for pump-fed systems) is installed to...

14 CFR 29.955 - Fuel flow.

Code of Federal Regulations, 2014 CFR

2014-01-01

... STANDARDS: TRANSPORT CATEGORY ROTORCRAFT Powerplant Fuel System § 29.955 Fuel flow. (a) General. The fuel system for each engine must provide the engine with at least 100 percent of the fuel required under all... flow transmitter, if installed, and the critical fuel pump (for pump-fed systems) must be installed to...

14 CFR 27.955 - Fuel flow.

Code of Federal Regulations, 2011 CFR

2011-01-01

... STANDARDS: NORMAL CATEGORY ROTORCRAFT Powerplant Fuel System § 27.955 Fuel flow. (a) General. The fuel system for each engine must be shown to provide the engine with at least 100 percent of the fuel required... to rotorcraft flight attitudes. (4) The critical fuel pump (for pump-fed systems) is installed to...

14 CFR 27.955 - Fuel flow.

Code of Federal Regulations, 2010 CFR

2010-01-01

... STANDARDS: NORMAL CATEGORY ROTORCRAFT Powerplant Fuel System § 27.955 Fuel flow. (a) General. The fuel system for each engine must be shown to provide the engine with at least 100 percent of the fuel required... to rotorcraft flight attitudes. (4) The critical fuel pump (for pump-fed systems) is installed to...

14 CFR 29.955 - Fuel flow.

Code of Federal Regulations, 2013 CFR

2013-01-01

... STANDARDS: TRANSPORT CATEGORY ROTORCRAFT Powerplant Fuel System § 29.955 Fuel flow. (a) General. The fuel system for each engine must provide the engine with at least 100 percent of the fuel required under all... flow transmitter, if installed, and the critical fuel pump (for pump-fed systems) must be installed to...

14 CFR 29.955 - Fuel flow.

Code of Federal Regulations, 2012 CFR

2012-01-01

... STANDARDS: TRANSPORT CATEGORY ROTORCRAFT Powerplant Fuel System § 29.955 Fuel flow. (a) General. The fuel system for each engine must provide the engine with at least 100 percent of the fuel required under all... flow transmitter, if installed, and the critical fuel pump (for pump-fed systems) must be installed to...

14 CFR 29.955 - Fuel flow.

Code of Federal Regulations, 2010 CFR

2010-01-01

... STANDARDS: TRANSPORT CATEGORY ROTORCRAFT Powerplant Fuel System § 29.955 Fuel flow. (a) General. The fuel system for each engine must provide the engine with at least 100 percent of the fuel required under all... flow transmitter, if installed, and the critical fuel pump (for pump-fed systems) must be installed to...

14 CFR 27.955 - Fuel flow.

Code of Federal Regulations, 2012 CFR

2012-01-01

... STANDARDS: NORMAL CATEGORY ROTORCRAFT Powerplant Fuel System § 27.955 Fuel flow. (a) General. The fuel system for each engine must be shown to provide the engine with at least 100 percent of the fuel required... to rotorcraft flight attitudes. (4) The critical fuel pump (for pump-fed systems) is installed to...

14 CFR 29.955 - Fuel flow.

Code of Federal Regulations, 2011 CFR

2011-01-01

... STANDARDS: TRANSPORT CATEGORY ROTORCRAFT Powerplant Fuel System § 29.955 Fuel flow. (a) General. The fuel system for each engine must provide the engine with at least 100 percent of the fuel required under all... flow transmitter, if installed, and the critical fuel pump (for pump-fed systems) must be installed to...

An airline study of advanced technology requirements for advanced high speed commercial transport engines. 1: Engine design study assessment

NASA Technical Reports Server (NTRS)

Sallee, G. P.

1973-01-01

The advanced technology requirements for an advanced high speed commercial tranport engine are presented. The results of the phase 1 study effort cover the following areas: (1) statement of an airline's major objectives for future transport engines, (2) airline's method of evaluating engine proposals, (3) description of an optimum engine for a long range subsonic commercial transport including installation and critical design features, (4) discussion of engine performance problems and experience with performance degradation, (5) trends in engine and pod prices with increasing technology and objectives for the future, (6) discussion of the research objectives for composites, reversers, advanced components, engine control systems, and devices to reduce the impact of engine stall, and (7) discussion of the airline objectives for noise and pollution reduction.

The common engine concept for ALS application - A cost reduction approach

NASA Technical Reports Server (NTRS)

Bair, E. K.; Schindler, C. M.

1989-01-01

Future launch systems require the application of propulsion systems which have been designed and developed to meet mission model needs while providing high degrees of reliability and cost effectiveness. Vehicle configurations which utilize different propellant combinations for booster and core stages can benefit from a common engine approach where a single engine design can be configured to operate on either set of propellants and thus serve as either a booster or core engine. Engine design concepts and mission application for a vehicle employing a common engine are discussed. Engine program cost estimates were made and cost savings, over the design and development of two unique engines, estimated.

46 CFR 111.10-9 - Ship's service supply transformers; two required.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 46 Shipping 4 2014-10-01 2014-10-01 false Ship's service supply transformers; two required. 111.10... ENGINEERING ELECTRIC SYSTEMS-GENERAL REQUIREMENTS Power Supply § 111.10-9 Ship's service supply transformers; two required. If transformers are used to supply the ship's service distribution system required by...

46 CFR 111.10-9 - Ship's service supply transformers; two required.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 46 Shipping 4 2012-10-01 2012-10-01 false Ship's service supply transformers; two required. 111.10... ENGINEERING ELECTRIC SYSTEMS-GENERAL REQUIREMENTS Power Supply § 111.10-9 Ship's service supply transformers; two required. If transformers are used to supply the ship's service distribution system required by...

46 CFR 111.10-9 - Ship's service supply transformers; two required.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 46 Shipping 4 2011-10-01 2011-10-01 false Ship's service supply transformers; two required. 111.10... ENGINEERING ELECTRIC SYSTEMS-GENERAL REQUIREMENTS Power Supply § 111.10-9 Ship's service supply transformers; two required. If transformers are used to supply the ship's service distribution system required by...

46 CFR 111.10-9 - Ship's service supply transformers; two required.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 4 2010-10-01 2010-10-01 false Ship's service supply transformers; two required. 111.10... ENGINEERING ELECTRIC SYSTEMS-GENERAL REQUIREMENTS Power Supply § 111.10-9 Ship's service supply transformers; two required. If transformers are used to supply the ship's service distribution system required by...

46 CFR 111.10-9 - Ship's service supply transformers; two required.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 46 Shipping 4 2013-10-01 2013-10-01 false Ship's service supply transformers; two required. 111.10... ENGINEERING ELECTRIC SYSTEMS-GENERAL REQUIREMENTS Power Supply § 111.10-9 Ship's service supply transformers; two required. If transformers are used to supply the ship's service distribution system required by...

Requirements Engineering in Building Climate Science Software

ERIC Educational Resources Information Center

Batcheller, Archer L.

2011-01-01

Software has an important role in supporting scientific work. This dissertation studies teams that build scientific software, focusing on the way that they determine what the software should do. These requirements engineering processes are investigated through three case studies of climate science software projects. The Earth System Modeling…

Boiler and Pressure Balls Monopropellant Thermal Rocket Engine

NASA Technical Reports Server (NTRS)

Greene, William D. (Inventor)

2009-01-01

The proposed technology is a rocket engine cycle utilizing as the propulsive fluid a low molecular weight, cryogenic fluid, typically liquid hydrogen, pressure driven, heated, and expelled through a nozzle to generate high velocity and high specific impulse discharge gas. The proposed technology feeds the propellant through the engine cycle without the use of a separate pressurization fluid and without the use of turbomachinery. Advantages of the proposed technology are found in those elements of state-of-the-art systems that it avoids. It does not require a separate pressurization fluid or a thick-walled primary propellant tank as is typically required for a classical pressure-fed system. Further, it does not require the acceptance of intrinsic reliability risks associated with the use of turbomachinery

SOFIA Program SE and I Lessons Learned

NASA Technical Reports Server (NTRS)

Ray, Ronald J.; Fobel, Laura J.; Brignola, Michael P.

2011-01-01

Once a "Troubled Project" threatened with cancellation, the Stratospheric Observatory for Infrared Astronomy (SOFIA) Program has overcome many difficult challenges and recently achieved its first light images. To achieve success, SOFIA had to overcome significant deficiencies in fundamental Systems Engineering identified during a major Program restructuring. This presentation will summarize the lessons learn in Systems Engineering on the SOFIA Program. After the Program was reformulated, an initial assessment of Systems Engineering established the scope of the problem and helped to set a list of priorities that needed to be work. A revised Systems Engineering Management Plan (SEMP) was written to address the new Program structure and requirements established in the approved NPR7123.1A. An important result of the "Technical Planning" effort was the decision by the Program and Technical Leadership team to re-phasing the lifecycle into increments. The reformed SOFIA Program Office had to quickly develop and establish several new System Engineering core processes including; Requirements Management, Risk Management, Configuration Management and Data Management. Implementing these processes had to consider the physical and cultural diversity of the SOFIA Program team which includes two Projects spanning two NASA Centers, a major German partnership, and sub-contractors located across the United States and Europe. The SOFIA Program experience represents a creative approach to doing "System Engineering in the middle" while a Program is well established. Many challenges were identified and overcome. The SOFIA example demonstrates it is never too late to benefit from fixing deficiencies in the System Engineering processes.

Large liquid rocket engine transient performance simulation system

NASA Technical Reports Server (NTRS)

Mason, J. R.; Southwick, R. D.

1989-01-01

Phase 1 of the Rocket Engine Transient Simulation (ROCETS) program consists of seven technical tasks: architecture; system requirements; component and submodel requirements; submodel implementation; component implementation; submodel testing and verification; and subsystem testing and verification. These tasks were completed. Phase 2 of ROCETS consists of two technical tasks: Technology Test Bed Engine (TTBE) model data generation; and system testing verification. During this period specific coding of the system processors was begun and the engineering representations of Phase 1 were expanded to produce a simple model of the TTBE. As the code was completed, some minor modifications to the system architecture centering on the global variable common, GLOBVAR, were necessary to increase processor efficiency. The engineering modules completed during Phase 2 are listed: INJTOO - main injector; MCHBOO - main chamber; NOZLOO - nozzle thrust calculations; PBRNOO - preburner; PIPE02 - compressible flow without inertia; PUMPOO - polytropic pump; ROTROO - rotor torque balance/speed derivative; and TURBOO - turbine. Detailed documentation of these modules is in the Appendix. In addition to the engineering modules, several submodules were also completed. These submodules include combustion properties, component performance characteristics (maps), and specific utilities. Specific coding was begun on the system configuration processor. All functions necessary for multiple module operation were completed but the SOLVER implementation is still under development. This system, the Verification Checkout Facility (VCF) allows interactive comparison of module results to store data as well as provides an intermediate checkout of the processor code. After validation using the VCF, the engineering modules and submodules were used to build a simple TTBE.

A Model-Based Approach to Developing Your Mission Operations System

NASA Technical Reports Server (NTRS)

Smith, Robert R.; Schimmels, Kathryn A.; Lock, Patricia D; Valerio, Charlene P.

2014-01-01

Model-Based System Engineering (MBSE) is an increasingly popular methodology for designing complex engineering systems. As the use of MBSE has grown, it has begun to be applied to systems that are less hardware-based and more people- and process-based. We describe our approach to incorporating MBSE as a way to streamline development, and how to build a model consisting of core resources, such as requirements and interfaces, that can be adapted and used by new and upcoming projects. By comparing traditional Mission Operations System (MOS) system engineering with an MOS designed via a model, we will demonstrate the benefits to be obtained by incorporating MBSE in system engineering design processes.

The HAL 9000 Space Operating System Real-Time Planning Engine Design and Operations Requirements

NASA Technical Reports Server (NTRS)

Stetson, Howard; Watson, Michael D.; Shaughnessy, Ray

2012-01-01

In support of future deep space manned missions, an autonomous/automated vehicle, providing crew autonomy and an autonomous response planning system, will be required due to the light time delays in communication. Vehicle capabilities as a whole must provide for tactical response to vehicle system failures and space environmental effects induced failures, for risk mitigation of permanent loss of communication with Earth, and for assured crew return capabilities. The complexity of human rated space systems and the limited crew sizes and crew skills mix drive the need for a robust autonomous capability on-board the vehicle. The HAL 9000 Space Operating System[2] designed for such missions and space craft includes the first distributed real-time planning / re-planning system. This paper will detail the software architecture of the multiple planning engine system, and the interface design for plan changes, approval and implementation that is performed autonomously. Operations scenarios will be defined for analysis of the planning engines operations and its requirements for nominal / off nominal activities. An assessment of the distributed realtime re-planning system, in the defined operations environment, will be provided as well as findings as it pertains to the vehicle, crew, and mission control requirements needed for implementation.

Patient safety - the role of human factors and systems engineering.

PubMed

Carayon, Pascale; Wood, Kenneth E

2010-01-01

Patient safety is a global challenge that requires knowledge and skills in multiple areas, including human factors and systems engineering. In this chapter, numerous conceptual approaches and methods for analyzing, preventing and mitigating medical errors are described. Given the complexity of healthcare work systems and processes, we emphasize the need for increasing partnerships between the health sciences and human factors and systems engineering to improve patient safety. Those partnerships will be able to develop and implement the system redesigns that are necessary to improve healthcare work systems and processes for patient safety.

14 CFR 29.571 - Fatigue evaluation of structure.

Code of Federal Regulations, 2012 CFR

2012-01-01

..., but are not limited to, rotors, rotor drive systems between the engines and rotor hubs, controls... drive systems between the engines and rotor hubs, controls, fuselage, fixed and movable control surfaces... AIRCRAFT AIRWORTHINESS STANDARDS: TRANSPORT CATEGORY ROTORCRAFT Strength Requirements Fatigue Evaluation...

46 CFR 58.30-50 - Requirements for miscellaneous fluid power and control systems.

Code of Federal Regulations, 2010 CFR

2010-10-01

...) MARINE ENGINEERING MAIN AND AUXILIARY MACHINERY AND RELATED SYSTEMS Fluid Power and Control Systems § 58.30-50 Requirements for miscellaneous fluid power and control systems. (a) All fluid power and control... 46 Shipping 2 2010-10-01 2010-10-01 false Requirements for miscellaneous fluid power and control...

46 CFR 58.30-50 - Requirements for miscellaneous fluid power and control systems.

Code of Federal Regulations, 2014 CFR

2014-10-01

...) MARINE ENGINEERING MAIN AND AUXILIARY MACHINERY AND RELATED SYSTEMS Fluid Power and Control Systems § 58.30-50 Requirements for miscellaneous fluid power and control systems. (a) All fluid power and control... 46 Shipping 2 2014-10-01 2014-10-01 false Requirements for miscellaneous fluid power and control...

46 CFR 58.30-50 - Requirements for miscellaneous fluid power and control systems.

Code of Federal Regulations, 2013 CFR

2013-10-01

...) MARINE ENGINEERING MAIN AND AUXILIARY MACHINERY AND RELATED SYSTEMS Fluid Power and Control Systems § 58.30-50 Requirements for miscellaneous fluid power and control systems. (a) All fluid power and control... 46 Shipping 2 2013-10-01 2013-10-01 false Requirements for miscellaneous fluid power and control...

46 CFR 58.30-50 - Requirements for miscellaneous fluid power and control systems.

Code of Federal Regulations, 2011 CFR

2011-10-01

...) MARINE ENGINEERING MAIN AND AUXILIARY MACHINERY AND RELATED SYSTEMS Fluid Power and Control Systems § 58.30-50 Requirements for miscellaneous fluid power and control systems. (a) All fluid power and control... 46 Shipping 2 2011-10-01 2011-10-01 false Requirements for miscellaneous fluid power and control...

46 CFR 58.30-50 - Requirements for miscellaneous fluid power and control systems.

Code of Federal Regulations, 2012 CFR

2012-10-01

...) MARINE ENGINEERING MAIN AND AUXILIARY MACHINERY AND RELATED SYSTEMS Fluid Power and Control Systems § 58.30-50 Requirements for miscellaneous fluid power and control systems. (a) All fluid power and control... 46 Shipping 2 2012-10-01 2012-10-01 false Requirements for miscellaneous fluid power and control...

Postures and Motions Library Development for Verification of Ground Crew Human Factors Requirements

NASA Technical Reports Server (NTRS)

Stambolian, Damon; Henderson, Gena; Jackson, Mariea Dunn; Dischinger, Charles

2013-01-01

Spacecraft and launch vehicle ground processing activities require a variety of unique human activities. These activities are being documented in a primitive motion capture library. The library will be used by human factors engineering analysts to infuse real to life human activities into the CAD models to verify ground systems human factors requirements. As the primitive models are being developed for the library, the project has selected several current human factors issues to be addressed for the Space Launch System (SLS) and Orion launch systems. This paper explains how the motion capture of unique ground systems activities is being used to verify the human factors engineering requirements for ground systems used to process the SLS and Orion vehicles, and how the primitive models will be applied to future spacecraft and launch vehicle processing.

System engineering and management in a large and diverse multinational consortium

NASA Astrophysics Data System (ADS)

Wright, David; O'Sullivan, Brian; Thatcher, John; Renouf, Ian; Wright, Gillian; Wells, Martyn; Glasse, Alistair; Grozinger, Ulrich; Sykes, Jon; Smith, Dave; Eccleston, Paul; Shaughnessy, Bryan

2008-07-01

This paper elaborates the system engineering methods that are being successfully employed within the European Consortium (EC) to deliver the Optical System of the Mid Infa-Red Instrument (MIRI) to the James Webb Space Telescope (JWST). The EC is a Consortium of 21 institutes located in 10 European countries and, at instrument level, it works in a 50/50 partnership with JPL who are providing the instrument cooler, software and detector systems. The paper will describe how the system engineering approach has been based upon proven principles used in the space industry but applied in a tailored way that best accommodates the differences in international practices and standards with a primary aim of ensuring a cost-effective solution which supports all science requirements for the mission. The paper will recall how the system engineering has been managed from the definition of the system requirements in early phase B, through the successful Critical Design Review at the end of phase C and up to the test and flight build activities that are presently in progress. Communication and coordination approaches will also be discussed.

Protein design in systems metabolic engineering for industrial strain development.

PubMed

Chen, Zhen; Zeng, An-Ping

2013-05-01

Accelerating the process of industrial bacterial host strain development, aimed at increasing productivity, generating new bio-products or utilizing alternative feedstocks, requires the integration of complementary approaches to manipulate cellular metabolism and regulatory networks. Systems metabolic engineering extends the concept of classical metabolic engineering to the systems level by incorporating the techniques used in systems biology and synthetic biology, and offers a framework for the development of the next generation of industrial strains. As one of the most useful tools of systems metabolic engineering, protein design allows us to design and optimize cellular metabolism at a molecular level. Here, we review the current strategies of protein design for engineering cellular synthetic pathways, metabolic control systems and signaling pathways, and highlight the challenges of this subfield within the context of systems metabolic engineering. Copyright © 2013 WILEY-VCH Verlag GmbH & Co. KGaA, Weinheim.

Main Engine Prototype Development for 2nd Generation RLV RS-83

NASA Technical Reports Server (NTRS)

Vilja, John; Fisher, Mark; Lyles, Garry M. (Technical Monitor)

2002-01-01

This presentation reports on the NASA project to develop a prototype for RS-83 engine designed for use on reusable launch vehicles (RLV). Topics covered include: program objectives, overview schedule, organizational chart, integrated systems engineering processes, requirement analysis, catastrophic engine loss, maintainability analysis tools, and prototype design analysis.

A Novel Approach to Physiology Education for Biomedical Engineering Students

ERIC Educational Resources Information Center

DiCecco, J.; Wu, J.; Kuwasawa, K.; Sun, Y.

2007-01-01

It is challenging for biomedical engineering programs to incorporate an indepth study of the systemic interdependence of cells, tissues, and organs into the rigorous mathematical curriculum that is the cornerstone of engineering education. To be sure, many biomedical engineering programs require their students to enroll in anatomy and physiology…

76 FR 39763 - Special Conditions: Boeing Model 787-8 Airplane; Interaction of Systems and Structures...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-07-07

...) Protection, Limit Engine Torque Loads for Sudden Engine Stoppage, and Design Roll Maneuver Requirement AGENCY... design features when compared to the state of technology envisioned in the airworthiness standards for transport category airplanes. These design features include limit engine torque loads for sudden engine...

AMTD: update of engineering specifications derived from science requirements for future UVOIR space telescopes

NASA Astrophysics Data System (ADS)

Stahl, H. Philip; Postman, Marc; Mosier, Gary; Smith, W. Scott; Blaurock, Carl; Ha, Kong; Stark, Christopher C.

2014-08-01

The Advance Mirror Technology Development (AMTD) project is in Phase 2 of a multiyear effort, initiated in FY12, to mature by at least a half TRL step six critical technologies required to enable 4 meter or larger UVOIR space telescope primary mirror assemblies for both general astrophysics and ultra-high contrast observations of exoplanets. AMTD uses a science-driven systems engineering approach. We mature technologies required to enable the highest priority science AND provide a high-performance low-cost low-risk system. To give the science community options, we are pursuing multiple technology paths. A key task is deriving engineering specifications for advanced normal-incidence monolithic and segmented mirror systems needed to enable both general astrophysics and ultra-high contrast observations of exoplanets missions as a function of potential launch vehicles and their mass and volume constraints. A key finding of this effort is that the science requires an 8 meter or larger aperture telescope.

AMTD: Update of Engineering Specifications Derived from Science Requirements for Future UVOIR Space Telescopes

NASA Technical Reports Server (NTRS)

Stahl, H. Philip; Postman, Marc; Mosier, Gary; Smith, W. Scott; Blaurock, Carl; Ha, Kong; Stark, Christopher C.

2014-01-01

The Advance Mirror Technology Development (AMTD) project is in Phase 2 of a multiyear effort, initiated in FY12, to mature by at least a half TRL step six critical technologies required to enable 4 meter or larger UVOIR space telescope primary mirror assemblies for both general astrophysics and ultra-high contrast observations of exoplanets. AMTD uses a science-driven systems engineering approach. We mature technologies required to enable the highest priority science AND provide a high-performance low-cost low-risk system. To give the science community options, we are pursuing multiple technology paths. A key task is deriving engineering specifications for advanced normal-incidence monolithic and segmented mirror systems needed to enable both general astrophysics and ultra-high contrast observations of exoplanets missions as a function of potential launch vehicles and their mass and volume constraints. A key finding of this effort is that the science requires an 8 meter or larger aperture telescope

Reusability aspects for space transportation rocket engines: programmatic status and outlook

NASA Astrophysics Data System (ADS)

Preclik, D.; Strunz, R.; Hagemann, G.; Langel, G.

2011-09-01

Rocket propulsion systems belong to the most critical subsystems of a space launch vehicle, being illustrated in this paper by comparing different types of transportation systems. The aspect of reusability is firstly discussed for the space shuttle main engine, the only rocket engine in the world that has demonstrated multiple reuses. Initial projections are contrasted against final reusability achievements summarizing three decades of operating the space shuttle main engine. The discussion is then extended to engines employed on expendable launch vehicles with an operational life requirement typically specifying structural integrities up to 20 cycles (start-ups) and an accumulated burning time of about 6,000 s (Vulcain engine family). Today, this life potential substantially exceeds the duty cycle of an expendable engine. It is actually exploited only during the development and qualification phase of an engine when system reliability is demonstrated on ground test facilities with a reduced number of hardware sets that are subjected to an extended number of test cycles and operation time. The paper will finally evaluate the logic and effort necessary to qualify a reusable engine for a required reliability and put this result in context of possible cost savings realized from reuse operations over a time span of 25 years.

Engineered containment and control systems: nurturing nature.

PubMed

Clarke, James H; MacDonell, Margaret M; Smith, Ellen D; Dunn, R Jeffrey; Waugh, W Jody

2004-06-01

The development of engineered containment and control systems for contaminated sites must consider the environmental setting of each site. The behaviors of both contaminated materials and engineered systems are affected by environmental conditions that will continue to evolve over time as a result of such natural processes as climate change, ecological succession, pedogenesis, and landform changes. Understanding these processes is crucial to designing, implementing, and maintaining effective systems for sustained health and environmental protection. Traditional engineered systems such as landfill liners and caps are designed to resist natural processes rather than working with them. These systems cannot be expected to provide long-term isolation without continued maintenance. In some cases, full-scale replacement and remediation may be required within 50 years, at an effort and cost much higher than for the original cleanup. Approaches are being developed to define smarter containment and control systems for stewardship sites, considering lessons learned from implementing prescriptive waste disposal regulations enacted since the 1970s. These approaches more effectively involve integrating natural and engineered systems; enhancing sensors and predictive tools for evaluating performance; and incorporating information on failure events, including precursors and consequences, into system design and maintenance. An important feature is using natural analogs to predict environmental conditions and system responses over the long term, to accommodate environmental change in the design process, and, as possible, to engineer containment systems that mimic favorable natural systems. The key emphasis is harmony with the environment, so systems will work with and rely on natural processes rather than resisting them. Implementing these new integrated systems will reduce current requirements for active management, which are resource-intensive and expensive.

33 CFR 149.409 - How many fire extinguishers are needed?

Code of Federal Regulations, 2010 CFR

2010-07-01

... turbine engines B-II One for each engine. 2 (6) Open electric motors and generators C-II One for each of... fixed system is installed. 2 If the engine is installed on a weather deck or is open to the atmosphere... fans, are exempt. 4 Not required if a fixed foam system is installed in accordance with 46 CFR 108.489. ...

33 CFR 149.409 - How many fire extinguishers are needed?

Code of Federal Regulations, 2013 CFR

2013-07-01

... turbine engines B-II One for each engine. 2 (6) Open electric motors and generators C-II One for each of... fixed system is installed. 2 If the engine is installed on a weather deck or is open to the atmosphere... fans, are exempt. 4 Not required if a fixed foam system is installed in accordance with 46 CFR 108.489...

33 CFR 149.409 - How many fire extinguishers are needed?

Code of Federal Regulations, 2012 CFR

2012-07-01

... turbine engines B-II One for each engine. 2 (6) Open electric motors and generators C-II One for each of... fixed system is installed. 2 If the engine is installed on a weather deck or is open to the atmosphere... fans, are exempt. 4 Not required if a fixed foam system is installed in accordance with 46 CFR 108.489. ...

33 CFR 149.409 - How many fire extinguishers are needed?

Code of Federal Regulations, 2014 CFR

2014-07-01

... turbine engines B-II One for each engine. 2 (6) Open electric motors and generators C-II One for each of... fixed system is installed. 2 If the engine is installed on a weather deck or is open to the atmosphere... fans, are exempt. 4 Not required if a fixed foam system is installed in accordance with 46 CFR 108.489...

33 CFR 149.409 - How many fire extinguishers are needed?

Code of Federal Regulations, 2011 CFR

2011-07-01

... turbine engines B-II One for each engine. 2 (6) Open electric motors and generators C-II One for each of... fixed system is installed. 2 If the engine is installed on a weather deck or is open to the atmosphere... fans, are exempt. 4 Not required if a fixed foam system is installed in accordance with 46 CFR 108.489. ...

Preliminary designs for 25 kWe advanced Stirling conversion systems for dish electric applications

NASA Technical Reports Server (NTRS)

Shaltens, Richard K.; Schreiber, Jeffrey G.

1990-01-01

Under the Department of Energy's (DOE) Solar Thermal Technology Program, Sandia National Laboratories is evaluating heat engines for terrestrial Solar Distributed Heat Receivers. The Stirling engine has been identified by Sandia as one of the most promising engines for terrestrial applications. The Stirling engine also has the potential to meet DOE's performance and cost goals. The NASA Lewis Research Center is conducting Stirling engine technology development activities directed toward a dynamic power source for space applications. Space power systems requirements include high reliability, very long life, low vibration and high efficiency. The free-piston Stirling engine has the potential for future high power space conversion systems, either nuclear or solar powered. Although both applications appear to be quite different, their requirements complement each other. Preliminary designs feature a free-piston Stirling engine, a liquid metal heat transport system, and a means to provide nominally 25 kW electric power to a utility grid while meeting DOE's performance and long term cost goals. The Cummins design incorporates a linear alternator to provide the electrical output, while the STC design generates electrical power indirectly through a hydraulic pump/motor coupled to an induction generator. Both designs for the ASCS's will use technology which can reasonably be expected to be available in the early 1990's.

Preliminary designs for 25 kWe advanced Stirling conversion systems for dish electric applications

NASA Astrophysics Data System (ADS)

Shaltens, Richard K.; Schreiber, Jeffrey G.

Under the Department of Energy's (DOE) Solar Thermal Technology Program, Sandia National Laboratories is evaluating heat engines for terrestrial Solar Distributed Heat Receivers. The Stirling engine has been identified by Sandia as one of the most promising engines for terrestrial applications. The Stirling engine also has the potential to meet DOE's performance and cost goals. The NASA Lewis Research Center is conducting Stirling engine technology development activities directed toward a dynamic power source for space applications. Space power systems requirements include high reliability, very long life, low vibration and high efficiency. The free-piston Stirling engine has the potential for future high power space conversion systems, either nuclear or solar powered. Although both applications appear to be quite different, their requirements complement each other. Preliminary designs feature a free-piston Stirling engine, a liquid metal heat transport system, and a means to provide nominally 25 kW electric power to a utility grid while meeting DOE's performance and long term cost goals. The Cummins design incorporates a linear alternator to provide the electrical output, while the STC design generates electrical power indirectly through a hydraulic pump/motor coupled to an induction generator. Both designs for the ASCS's will use technology which can reasonably be expected to be available in the early 1990's.

Preliminary designs for 25 kWe advanced Stirling conversion systems for dish electric applications

NASA Technical Reports Server (NTRS)

Shaltens, Richard K.; Schreiber, Jeffrey G.

1990-01-01

Under the Department of Energy's (DOE) Solar Thermal Technology Program, Sandia National Laboratories is evaluating heat engines for terrestrial Solar Distributed Heat Receivers. The Stirling engine has been identified by Sandia as one of the most promising engines for terrestrial applications. The Stirling engine also has the potential to meet DOE's performance and cost goals. The NASA Lewis Research Center is conducting Stirling engine technology development activities directed toward a dynamic power source for space applications. Space power systems requirements include high reliability, very long life, low vibration and high efficiency. The free-piston Stirling engine has the potential for future high power space conversion systems, either nuclear or solar powered. Although both applications appear to be quite different, their requirements complement each other. Preliminary designs feature a free-piston Stirling engine, a liquid metal heat transport system, and a means to provide nominally 25 kW electric power to a utility grid while meeting DOE's performance and long term cost goals. The Cummins design incorporates a linear alternator to provide the electrical output, while the STC design generates electrical power indirectly through a hydraulic pump/motor coupled to an induction generator. Both designs for the ASCS's will use technology which can reasonably be expected to be available in the early 1990's

New Technology Sparks Smoother Engines and Cleaner Air

NASA Technical Reports Server (NTRS)

2001-01-01

Automotive Resources, Inc. (ARI) has developed a new device for igniting fuel in engines-the SmartPlug.TM SmartPlug is a self-contained ignition system that may be retrofitted to existing spark-ignition and compression-ignition engines. The SmartPlug needs as little as six watts of power for warm-up, and requires no electricity at all when the engine is running. Unlike traditional spark plugs, once the SmartPlug ignites the engine, and the engine heats up, the power supply for the plug is no longer necessary. In the utility industry, SmartPlugs can be used in tractors, portable generators, compressors, and pumps. In addition to general-purpose applications, such as lawn mowers and chainsaws, SmartPlugs can also be used in the recreational, marine, aviation, and automotive industries. Unlike traditional ignition systems, the SmartPlug system requires no distributor, coil points, or moving parts. SmartPlugs are non-fouling, with a faster and cleaner burn than traditional spark plugs. They prevent detonation and are not sensitive to moisture, allowing them to be used on a variety of engines. Other advantages include no electrical noise, no high voltage, exceptionally high altitude capabilities, and better cold-start statistics than those of standard spark ignition systems. Future applications for the SmartPlug are being evaluated by manufacturers in the snowmobile industry.

Applying Model Based Systems Engineering to NASA's Space Communications Networks

NASA Technical Reports Server (NTRS)

Bhasin, Kul; Barnes, Patrick; Reinert, Jessica; Golden, Bert

2013-01-01

System engineering practices for complex systems and networks now require that requirement, architecture, and concept of operations product development teams, simultaneously harmonize their activities to provide timely, useful and cost-effective products. When dealing with complex systems of systems, traditional systems engineering methodology quickly falls short of achieving project objectives. This approach is encumbered by the use of a number of disparate hardware and software tools, spreadsheets and documents to grasp the concept of the network design and operation. In case of NASA's space communication networks, since the networks are geographically distributed, and so are its subject matter experts, the team is challenged to create a common language and tools to produce its products. Using Model Based Systems Engineering methods and tools allows for a unified representation of the system in a model that enables a highly related level of detail. To date, Program System Engineering (PSE) team has been able to model each network from their top-level operational activities and system functions down to the atomic level through relational modeling decomposition. These models allow for a better understanding of the relationships between NASA's stakeholders, internal organizations, and impacts to all related entities due to integration and sustainment of existing systems. Understanding the existing systems is essential to accurate and detailed study of integration options being considered. In this paper, we identify the challenges the PSE team faced in its quest to unify complex legacy space communications networks and their operational processes. We describe the initial approaches undertaken and the evolution toward model based system engineering applied to produce Space Communication and Navigation (SCaN) PSE products. We will demonstrate the practice of Model Based System Engineering applied to integrating space communication networks and the summary of its results and impact. We will highlight the insights gained by applying the Model Based System Engineering and provide recommendations for its applications and improvements.

Doing Systems Engineering Without Thinking About It at NASA Dryden Flight Research Center

NASA Technical Reports Server (NTRS)

Bohn-Meyer, Marta; Kilp, Stephen; Chun, Peggy; Mizukami, Masashi

2004-01-01

When asked about his processes in designing a new airplane, Burt Rutan responded: ...there is always a performance requirement. So I start with the basic physics of an airplane that can get those requirements, and that pretty much sizes an airplane... Then I look at the functionality... And then I try a lot of different configurations to meet that, and then justify one at a time, throwing them out... Typically I'll have several different configurations... But I like to experiment, certainly. I like to see if there are other ways to provide the utility. This kind of thinking engineering as a total systems engineering approach is what is being instilled in all engineers at the NASA Dryden Flight Research Center.

Fall 2012 Graduate Engineering Internship Summary

NASA Technical Reports Server (NTRS)

Ehrlich, Joshua

2013-01-01

In the fall of 2012, I participated in the National Aeronautics and Space Administration (NASA) Pathways Intern Employment Program at the Kennedy Space Center (KSC) in Florida. This was my second internship opportunity with NASA, a consecutive extension from a summer 2012 internship. During my four-month tenure, I gained valuable knowledge and extensive hands-on experience with payload design and testing as well as composite fabrication for repair design on future space vehicle structures. As a systems engineer, I supported the systems engineering and integration team with the testing of scientific payloads such as the Vegetable Production System (Veggie). Verification and validation (V&V) of the Veggie was carried out prior to qualification testing of the payload, which incorporated a lengthy process of confirming design requirements that were integrated through one or more validatjon methods: inspection, analysis, demonstration, and testing. Additionally, I provided assistance in verifying design requirements outlined in the V&V plan with the requirements outlined by the scientists in the Science Requirements Envelope Document (SRED). The purpose of the SRED was to define experiment requirements intended for the payload to meet and carry out.

77 FR 497 - Control of Emissions From New Nonroad Compression-Ignition Engines: Approval of New Scheduled...

Federal Register 2010, 2011, 2012, 2013, 2014

2012-01-05

... replenishment of the nitrogen-containing reducing agent for selective catalytic reduction (SCR) technologies... NO X reduction requirements for their diesel engines. SCR systems use a nitrogen-containing reducing... balance between the dictates of operating nonroad equipment (which requires DEF tanks of small enough...

46 CFR 25.35-1 - Requirements.

Code of Federal Regulations, 2014 CFR

2014-10-01

... Requirements. (a) Every gasoline engine installed in a motorboat or motor vessel after April 25, 1940, except outboard motors, shall be equipped with an acceptable means of backfire flame control. (b) Installations... Approval Nos. 162.015 or 162.041 or engine air and fuel induction systems bearing basic Approval Nos. 162...

46 CFR 25.35-1 - Requirements.

Code of Federal Regulations, 2013 CFR

2013-10-01

... Requirements. (a) Every gasoline engine installed in a motorboat or motor vessel after April 25, 1940, except outboard motors, shall be equipped with an acceptable means of backfire flame control. (b) Installations... Approval Nos. 162.015 or 162.041 or engine air and fuel induction systems bearing basic Approval Nos. 162...

46 CFR 27.203 - What are the requirements for fire detection on towing vessels?

Code of Federal Regulations, 2010 CFR

2010-10-01

... detection on towing vessels? You must have a fire-detection system installed on your vessel to detect engine... use an existing engine-room-monitoring system (with fire-detection capability) instead of a fire-detection system, if the monitoring system is operable and complies with this section. You must ensure that...

46 CFR 111.97-3 - General requirements.

Code of Federal Regulations, 2011 CFR

2011-10-01

... COAST GUARD, DEPARTMENT OF HOMELAND SECURITY (CONTINUED) ELECTRICAL ENGINEERING ELECTRIC SYSTEMS-GENERAL REQUIREMENTS Electric Power-Operated Watertight Door Systems § 111.97-3 General requirements. Each watertight door operating system must meet Subpart H, § 170.270 of this chapter. [CGD 74-125A, 47 FR 15236, Apr. 8...

46 CFR 111.97-3 - General requirements.

Code of Federal Regulations, 2012 CFR

2012-10-01

... COAST GUARD, DEPARTMENT OF HOMELAND SECURITY (CONTINUED) ELECTRICAL ENGINEERING ELECTRIC SYSTEMS-GENERAL REQUIREMENTS Electric Power-Operated Watertight Door Systems § 111.97-3 General requirements. Each watertight door operating system must meet Subpart H, § 170.270 of this chapter. [CGD 74-125A, 47 FR 15236, Apr. 8...

46 CFR 111.97-3 - General requirements.

Code of Federal Regulations, 2013 CFR

2013-10-01

... COAST GUARD, DEPARTMENT OF HOMELAND SECURITY (CONTINUED) ELECTRICAL ENGINEERING ELECTRIC SYSTEMS-GENERAL REQUIREMENTS Electric Power-Operated Watertight Door Systems § 111.97-3 General requirements. Each watertight door operating system must meet Subpart H, § 170.270 of this chapter. [CGD 74-125A, 47 FR 15236, Apr. 8...

46 CFR 111.97-3 - General requirements.

Code of Federal Regulations, 2014 CFR

2014-10-01

... COAST GUARD, DEPARTMENT OF HOMELAND SECURITY (CONTINUED) ELECTRICAL ENGINEERING ELECTRIC SYSTEMS-GENERAL REQUIREMENTS Electric Power-Operated Watertight Door Systems § 111.97-3 General requirements. Each watertight door operating system must meet Subpart H, § 170.270 of this chapter. [CGD 74-125A, 47 FR 15236, Apr. 8...

46 CFR 111.97-3 - General requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... COAST GUARD, DEPARTMENT OF HOMELAND SECURITY (CONTINUED) ELECTRICAL ENGINEERING ELECTRIC SYSTEMS-GENERAL REQUIREMENTS Electric Power-Operated Watertight Door Systems § 111.97-3 General requirements. Each watertight door operating system must meet Subpart H, § 170.270 of this chapter. [CGD 74-125A, 47 FR 15236, Apr. 8...

The MSFC Collaborative Engineering Process for Preliminary Design and Concept Definition Studies

NASA Technical Reports Server (NTRS)

Mulqueen, Jack; Jones, David; Hopkins, Randy

2011-01-01

This paper describes a collaborative engineering process developed by the Marshall Space Flight Center's Advanced Concepts Office for performing rapid preliminary design and mission concept definition studies for potential future NASA missions. The process has been developed and demonstrated for a broad range of mission studies including human space exploration missions, space transportation system studies and in-space science missions. The paper will describe the design team structure and specialized analytical tools that have been developed to enable a unique rapid design process. The collaborative engineering process consists of integrated analysis approach for mission definition, vehicle definition and system engineering. The relevance of the collaborative process elements to the standard NASA NPR 7120.1 system engineering process will be demonstrated. The study definition process flow for each study discipline will be will be outlined beginning with the study planning process, followed by definition of ground rules and assumptions, definition of study trades, mission analysis and subsystem analyses leading to a standardized set of mission concept study products. The flexibility of the collaborative engineering design process to accommodate a wide range of study objectives from technology definition and requirements definition to preliminary design studies will be addressed. The paper will also describe the applicability of the collaborative engineering process to include an integrated systems analysis approach for evaluating the functional requirements of evolving system technologies and capabilities needed to meet the needs of future NASA programs.

Cost/Effort Drivers and Decision Analysis

NASA Technical Reports Server (NTRS)

Seidel, Jonathan

2010-01-01

Engineering trade study analyses demand consideration of performance, cost and schedule impacts across the spectrum of alternative concepts and in direct reference to product requirements. Prior to detailed design, requirements are too often ill-defined (only goals ) and prone to creep, extending well beyond the Systems Requirements Review. Though lack of engineering design and definitive requirements inhibit the ability to perform detailed cost analyses, affordability trades still comprise the foundation of these future product decisions and must evolve in concert. This presentation excerpts results of the recent NASA subsonic Engine Concept Study for an Advanced Single Aisle Transport to demonstrate an affordability evaluation of performance characteristics and the subsequent impacts on engine architecture decisions. Applying the Process Based Economic Analysis Tool (PBEAT), development cost, production cost, as well as operation and support costs were considered in a traditional weighted ranking of the following system-level figures of merit: mission fuel burn, take-off noise, NOx emissions, and cruise speed. Weighting factors were varied to ascertain the architecture ranking sensitivities to these performance figures of merit with companion cost considerations. A more detailed examination of supersonic variable cycle engine cost is also briefly presented, with observations and recommendations for further refinements.

An expert system for spectroscopic analysis of rocket engine plumes

NASA Technical Reports Server (NTRS)

Reese, Greg; Valenti, Elizabeth; Alphonso, Keith; Holladay, Wendy

1991-01-01

The expert system described in this paper analyzes spectral emissions of rocket engine exhaust plumes and shows major promise for use in engine health diagnostics. Plume emission spectroscopy is an important tool for diagnosing engine anomalies, but it is time-consuming and requires highly skilled personnel. The expert system was created to alleviate such problems. The system accepts a spectral plot in the form of wavelength vs intensity pairs and finds the emission peaks in the spectrum, lists the elemental emitters present in the data and deduces the emitter that produced each peak. The system consists of a conventional language component and a commercially available inference engine that runs on an Apple Macintosh computer. The expert system has undergone limited preliminary testing. It detects elements well and significantly decreases analysis time.

Automated Test Environment for a Real-Time Control System

NASA Technical Reports Server (NTRS)

Hall, Ronald O.

1994-01-01

An automated environment with hardware-in-the-loop has been developed by Rocketdyne Huntsville for test of a real-time control system. The target system of application is the man-rated real-time system which controls the Space Shuttle Main Engines (SSME). The primary use of the environment is software verification and validation, but it is also useful for evaluation and analysis of SSME avionics hardware and mathematical engine models. It provides a test bed for the integration of software and hardware. The principles and skills upon which it operates may be applied to other target systems, such as those requiring hardware-in-the-loop simulation and control system development. Potential applications are in problem domains demanding highly reliable software systems requiring testing to formal requirements and verifying successful transition to/from off-nominal system states.

Implementation of a Goal-Based Systems Engineering Process Using the Systems Modeling Language (SysML)

NASA Technical Reports Server (NTRS)

Patterson, Jonathan D.; Breckenridge, Jonathan T.; Johnson, Stephen B.

2013-01-01

Building upon the purpose, theoretical approach, and use of a Goal-Function Tree (GFT) being presented by Dr. Stephen B. Johnson, described in a related Infotech 2013 ISHM abstract titled "Goal-Function Tree Modeling for Systems Engineering and Fault Management", this paper will describe the core framework used to implement the GFTbased systems engineering process using the Systems Modeling Language (SysML). These two papers are ideally accepted and presented together in the same Infotech session. Statement of problem: SysML, as a tool, is currently not capable of implementing the theoretical approach described within the "Goal-Function Tree Modeling for Systems Engineering and Fault Management" paper cited above. More generally, SysML's current capabilities to model functional decompositions in the rigorous manner required in the GFT approach are limited. The GFT is a new Model-Based Systems Engineering (MBSE) approach to the development of goals and requirements, functions, and its linkage to design. As a growing standard for systems engineering, it is important to develop methods to implement GFT in SysML. Proposed Method of Solution: Many of the central concepts of the SysML language are needed to implement a GFT for large complex systems. In the implementation of those central concepts, the following will be described in detail: changes to the nominal SysML process, model view definitions and examples, diagram definitions and examples, and detailed SysML construct and stereotype definitions.

Satellite-instrument system engineering best practices and lessons

NASA Astrophysics Data System (ADS)

Schueler, Carl F.

2009-08-01

This paper focuses on system engineering development issues driving satellite remote sensing instrumentation cost and schedule. A key best practice is early assessment of mission and instrumentation requirements priorities driving performance trades among major instrumentation measurements: Radiometry, spatial field of view and image quality, and spectral performance. Key lessons include attention to technology availability and applicability to prioritized requirements, care in applying heritage, approaching fixed-price and cost-plus contracts with appropriate attention to risk, and assessing design options with attention to customer preference as well as design performance, and development cost and schedule. A key element of success either in contract competition or execution is team experience. Perhaps the most crucial aspect of success, however, is thorough requirements analysis and flowdown to specifications driving design performance with sufficient parameter margin to allow for mistakes or oversights - the province of system engineering from design inception to development, test and delivery.

Preliminary flight results of an adaptive engine control system of an F-15 airplane

NASA Technical Reports Server (NTRS)

Myers, Lawrence P.; Walsh, Kevin R.

1987-01-01

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.

Effective Software Engineering Leadership for Development Programs

ERIC Educational Resources Information Center

Cagle West, Marsha

2010-01-01

Software is a critical component of systems ranging from simple consumer appliances to complex health, nuclear, and flight control systems. The development of quality, reliable, and effective software solutions requires the incorporation of effective software engineering processes and leadership. Processes, approaches, and methodologies for…

46 CFR 112.25-1 - General.

Code of Federal Regulations, 2013 CFR

2013-10-01

..., DEPARTMENT OF HOMELAND SECURITY (CONTINUED) ELECTRICAL ENGINEERING EMERGENCY LIGHTING AND POWER SYSTEMS Emergency Systems Having an Automatic Starting Diesel Engine or Gas Turbine Driven Emergency Power Source as the Sole Emergency Power Source § 112.25-1 General. This subpart contains requirements applicable to...

46 CFR 112.25-1 - General.

Code of Federal Regulations, 2014 CFR

2014-10-01

..., DEPARTMENT OF HOMELAND SECURITY (CONTINUED) ELECTRICAL ENGINEERING EMERGENCY LIGHTING AND POWER SYSTEMS Emergency Systems Having an Automatic Starting Diesel Engine or Gas Turbine Driven Emergency Power Source as the Sole Emergency Power Source § 112.25-1 General. This subpart contains requirements applicable to...

46 CFR 112.25-1 - General.

Code of Federal Regulations, 2010 CFR

2010-10-01

..., DEPARTMENT OF HOMELAND SECURITY (CONTINUED) ELECTRICAL ENGINEERING EMERGENCY LIGHTING AND POWER SYSTEMS Emergency Systems Having an Automatic Starting Diesel Engine or Gas Turbine Driven Emergency Power Source as the Sole Emergency Power Source § 112.25-1 General. This subpart contains requirements applicable to...

46 CFR 112.25-1 - General.

Code of Federal Regulations, 2011 CFR

2011-10-01

..., DEPARTMENT OF HOMELAND SECURITY (CONTINUED) ELECTRICAL ENGINEERING EMERGENCY LIGHTING AND POWER SYSTEMS Emergency Systems Having an Automatic Starting Diesel Engine or Gas Turbine Driven Emergency Power Source as the Sole Emergency Power Source § 112.25-1 General. This subpart contains requirements applicable to...

46 CFR 112.25-1 - General.

Code of Federal Regulations, 2012 CFR

2012-10-01

..., DEPARTMENT OF HOMELAND SECURITY (CONTINUED) ELECTRICAL ENGINEERING EMERGENCY LIGHTING AND POWER SYSTEMS Emergency Systems Having an Automatic Starting Diesel Engine or Gas Turbine Driven Emergency Power Source as the Sole Emergency Power Source § 112.25-1 General. This subpart contains requirements applicable to...

Nuclear thermal propulsion engine system design analysis code development

NASA Astrophysics Data System (ADS)

Pelaccio, Dennis G.; Scheil, Christine M.; Petrosky, Lyman J.; Ivanenok, Joseph F.

1992-01-01

A Nuclear Thermal Propulsion (NTP) Engine System Design Analyis Code has recently been developed to characterize key NTP engine system design features. Such a versatile, standalone NTP system performance and engine design code is required to support ongoing and future engine system and vehicle design efforts associated with proposed Space Exploration Initiative (SEI) missions of interest. Key areas of interest in the engine system modeling effort were the reactor, shielding, and inclusion of an engine multi-redundant propellant pump feed system design option. A solid-core nuclear thermal reactor and internal shielding code model was developed to estimate the reactor's thermal-hydraulic and physical parameters based on a prescribed thermal output which was integrated into a state-of-the-art engine system design model. The reactor code module has the capability to model graphite, composite, or carbide fuels. Key output from the model consists of reactor parameters such as thermal power, pressure drop, thermal profile, and heat generation in cooled structures (reflector, shield, and core supports), as well as the engine system parameters such as weight, dimensions, pressures, temperatures, mass flows, and performance. The model's overall analysis methodology and its key assumptions and capabilities are summarized in this paper.

Thermal energy storage for a space solar dynamic power system

NASA Technical Reports Server (NTRS)

Faget, N. M.; Fraser, W. M., Jr.; Simon, W. E.

1985-01-01

In the past, NASA has employed solar photovoltaic devices for long-duration missions. Thus, the Skylab system has operated with a silicon photovoltaic array and a nickel-cadmium electrochemical system energy storage system. Difficulties regarding the employment of such a system for the larger power requirements of the Space Station are related to a low orbit system efficiency and the large weight of the battery. For this reason the employment of a solar dynamic power system (SDPS) has been considered. The primary components of an SDPS include a concentrating mirror, a heat receiver, a thermal energy storage (TES) system, a thermodynamic heat engine, an alternator, and a heat rejection system. The heat-engine types under consideration are a Brayton cycle engine, an organic Rankine cycle engine, and a free-piston/linear-alternator Stirling cycle engine. Attention is given to a system description, TES integration concepts, and a TES technology assessment.

Research requirements for emergency power to permit hover-one-engine-inoperative helicopter operation

NASA Technical Reports Server (NTRS)

Yost, J. H.

1976-01-01

The research and technology demonstration requirements to achieve emergency-power capability for a civil helicopter are documented. The goal for emergency power is the ability to hover with one engine inoperative, transition to minimum-power forward flight, and continue to a safe landing where emergency power may or may not be required. The best method to obtain emergency power is to augment the basic engine power by increasing the engine's speed and turbine-inlet temperature, combined with water-alcohol injection at the engine inlet. Other methods, including turbine boost power and flywheel energy, offer potential for obtaining emergency power for minimum time durations. Costs and schedules are estimated for a research and development program to bring emergency power through a hardware-demonstration test. Interaction of engine emergency-power capability with other helicopter systems is examined.

2005 8th Annual Systems Engineering Conference. Volume 2, Wednesday Presentations

DTIC Science & Technology

2005-10-27

Acquisition Programs: An OSD Perspective, Col Warren Anderson, OUSD (AT&L) Defense Systems Implementation of Policy Requiring Systems Engineering Plans...Technical Excellence, Col Warren Anderson, OUSD (AT&L) Defense Systems Applying CMMI to System Safety, Mr. Tom Pfitzer, APT Research, Inc. System...to following pages for Tutorials Schedule) Buffett Lunch Tutorial Tracks (Please refer to following pages for Tutorials Schedule) Reception in

40 CFR 1048.605 - What provisions apply to engines certified under the motor vehicle program?

Code of Federal Regulations, 2014 CFR

2014-07-01

... engine cooling system so that temperatures or heat rejection rates are outside the original engine... submission. We may require you to send us emission test data on any applicable nonroad duty cycles. (g...

40 CFR 1048.605 - What provisions apply to engines certified under the motor vehicle program?

Code of Federal Regulations, 2013 CFR

2013-07-01

... engine cooling system so that temperatures or heat rejection rates are outside the original engine... submission. We may require you to send us emission test data on any applicable nonroad duty cycles. (g...

40 CFR 1048.605 - What provisions apply to engines certified under the motor vehicle program?

Code of Federal Regulations, 2012 CFR

2012-07-01

... engine cooling system so that temperatures or heat rejection rates are outside the original engine... submission. We may require you to send us emission test data on any applicable nonroad duty cycles. (g...

40 CFR 1048.605 - What provisions apply to engines certified under the motor vehicle program?

Code of Federal Regulations, 2011 CFR

2011-07-01

... engine cooling system so that temperatures or heat rejection rates are outside the original engine... submission. We may require you to send us emission test data on any applicable nonroad duty cycles. (g...

46 CFR 162.060-20 - Design and construction requirements.

Code of Federal Regulations, 2014 CFR

2014-10-01

..., AND MATERIALS: SPECIFICATIONS AND APPROVAL ENGINEERING EQUIPMENT Ballast Water Management Systems... service; (4) Meets recognized national or international standards for all related marine engineering and electrical engineering applications; and (5) Operates when the vessel is upright, inclined under static...

46 CFR 162.060-20 - Design and construction requirements.

Code of Federal Regulations, 2013 CFR

2013-10-01

..., AND MATERIALS: SPECIFICATIONS AND APPROVAL ENGINEERING EQUIPMENT Ballast Water Management Systems... service; (4) Meets recognized national or international standards for all related marine engineering and electrical engineering applications; and (5) Operates when the vessel is upright, inclined under static...

46 CFR 162.060-20 - Design and construction requirements.

Code of Federal Regulations, 2012 CFR

2012-10-01

..., AND MATERIALS: SPECIFICATIONS AND APPROVAL ENGINEERING EQUIPMENT Ballast Water Management Systems... service; (4) Meets recognized national or international standards for all related marine engineering and electrical engineering applications; and (5) Operates when the vessel is upright, inclined under static...

Assessing students' performance in software requirements engineering education using scoring rubrics

NASA Astrophysics Data System (ADS)

Mkpojiogu, Emmanuel O. C.; Hussain, Azham

2017-10-01

The study investigates how helpful the use of scoring rubrics is, in the performance assessment of software requirements engineering students and whether its use can lead to students' performance improvement in the development of software requirements artifacts and models. Scoring rubrics were used by two instructors to assess the cognitive performance of a student in the design and development of software requirements artifacts. The study results indicate that the use of scoring rubrics is very helpful in objectively assessing the performance of software requirements or software engineering students. Furthermore, the results revealed that the use of scoring rubrics can also produce a good achievement assessments direction showing whether a student is either improving or not in a repeated or iterative assessment. In a nutshell, its use leads to the performance improvement of students. The results provided some insights for further investigation and will be beneficial to researchers, requirements engineers, system designers, developers and project managers.

Comparison of two total energy systems for a diesel power generation plant. [deep space network

NASA Technical Reports Server (NTRS)

Chai, V. W.

1979-01-01

The capabilities and limitations, as well as the associated costs for two total energy systems for a diesel power generation plant are compared. Both systems utilize waste heat from engine cooling water and waste heat from exhaust gases. Pressurized water heat recovery system is simple in nature and requires no engine modifications, but operates at lower temperature ranges. On the other hand, a two-phase ebullient system operates the engine at constant temperature, provides higher temperature water or steam to the load, but is more expensive.

A Chemical Engineer's Perspective on Health and Disease

PubMed Central

Androulakis, Ioannis P.

2014-01-01

Chemical process systems engineering considers complex supply chains which are coupled networks of dynamically interacting systems. The quest to optimize the supply chain while meeting robustness and flexibility constraints in the face of ever changing environments necessitated the development of theoretical and computational tools for the analysis, synthesis and design of such complex engineered architectures. However, it was realized early on that optimality is a complex characteristic required to achieve proper balance between multiple, often competing, objectives. As we begin to unravel life's intricate complexities, we realize that that living systems share similar structural and dynamic characteristics; hence much can be learned about biological complexity from engineered systems. In this article, we draw analogies between concepts in process systems engineering and conceptual models of health and disease; establish connections between these concepts and physiologic modeling; and describe how these mirror onto the physiological counterparts of engineered systems. PMID:25506103