Search NASA⌕ Search

SEARCH · Search NASA

Results for “STEP system engineering”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRS1994

Robotic Processing Of Rocket-Engine Nozzles

Automated manufacturing cell containing computer-controlled robotic processing system developed to implement some important related steps in fabrication of rocket-engine nozzles. Performs several tedious and repetitive fabrication, measurement, adjustment, and inspection processes and subprocesses now performed manually. Offers advantages of reduced processing time, greater consistency, excellent collection of data, objective inspections, greater productivity, and simplified fixturing. Also affords flexibility: by making suitable changes in hardware and software, possible to modify process and subprocesses. Flexibility makes work cell adaptable to fabrication of heat exchangers and other items structured similarly to rocket nozzles.

Gilbert, Jeffrey L.↗
NASA NTRS2000

Goals Analysis Procedure Guidelines for Applying the Goals Analysis Process

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.

Motley, Albert E., III↗
NASA NTRS1997

Ring Buffered Network Bus

This report describes the research effort to demonstrate the integration of a data sharing technology, Ring Buffered Network Bus, in development by Dryden Flight Research Center, with an engine simulation application, the Java Gas Turbine Simulator, in development at the University of Toledo under a grant from the Glenn Research Center. The objective of this task was to examine the application of the RBNB technologies as a key component in the data sharing, health monitoring and system wide modeling elements of the NASA Aviation Safety Program (AVSP) [Golding, 1997]. System-wide monitoring and modeling of aircraft and air safety systems will require access to all data sources which are relative factors when monitoring or modeling the national airspace such as radar, weather, aircraft performance, engine performance, schedule and planning, airport configuration, flight operations, etc. The data sharing portion of the overall AVSP program is responsible for providing the hardware and software architecture to access and distribute data, including real-time flight operations data, among all of the AVSP elements. The integration of an engine code capable of numerically "flying" through recorded flight paths and weather data using a software tool that allows for distributed access of data to this engine code demonstrates initial steps toward building a system capable of monitoring and modeling the National Airspace.

Source record↗
NASA NTRS2006

Selected Systems Engineering Process Deficiencies and Their Consequences

The systems engineering process is well established and well understood. While this statement could be argued in the light of the many systems engineering guidelines and that have been developed, comparative review of these respective descriptions reveal that they differ primarily in the number of discrete steps or other nuances, and are at their core essentially common. Likewise, the systems engineering textbooks differ primarily in the context for application of systems engineering or in the utilization of evolved tools and techniques, not in the basic method. Thus, failures in systems engineering cannot credibly be attributed to implementation of the wrong systems engineering process among alternatives. However, numerous systems failures can be attributed to deficient implementation of the systems engineering process. What may clearly be perceived as a system engineering deficiency in retrospect can appear to be a well considered system engineering efficiency in real time - an efficiency taken to reduce cost or meet a schedule, or more often both. Typically these efficiencies are grounded on apparently solid rationale, such as reuse of heritage hardware or software. Over time, unintended consequences of a systems engineering process deficiency may begin to be realized, and unfortunately often the consequence is system failure. This paper describes several actual cases of system failures that resulted from deficiencies in their systems engineering process implementation, including the Ariane 5 and the Hubble Space Telescope.

Thomas, Lawrence Dale↗
NASA NTRSDate not supplied

Failure Modes and Mitigation Strategies for a Turboelectric Aircraft Concept with Turbine Electrified Energy Management

The electrification of gas turbine engines represents a major step-change in aircraft propulsion systems commonly known as Electrified Aircraft Propulsion (EAP). EAP involves the integration of electric machines potentially functioning as generators for large scale power extraction, as motors providing electrical augmentation of the engine spools, and even as a means of driving propulsors beyond the immediate scope of the engine. It may also include the use of energy storage. These and other characteristics of hybrid electric propulsion systems are relatively new to aircraft propulsion. The expanded propulsion architecture can be leveraged to improve propulsive efficiency and achieve better vehicle aerodynamics and controllability. It can also allow for additional benefits such as those enabled through Turbine Electrified Energy Management (TEEM). As the propulsion system and its functions expand, new failure modes are introduced. Due to the highly coupled nature of the propulsion system, failures could propagate throughout the system in ways that are unique to the new EAP architectures. To build confidence in the safety and practicality of EAP concepts, these failure modes need to be identified, explored, and addressed through mitigation strategies. This paper seeks to evaluate failure modes and failure mitigation strategies for the EAP concept known as the Single aisle Turboelectric AiRCaft with Aft Boundary Layer propulsor (STARC-ABL). The TEEM control concept is applied to improve transient operability. Several failure modes are considered and control based failure mitigation strategies are proposed with the goal of retaining operability and overall thrust. The results demonstrate the ability to maintain operability and a substantial amount of thrust in the event of various types of failures. Some challenges are also identified and discussed.

Turbine Electrified Energy Management↗
NASA NTRS2001

I(sup STAR), NASA's Next Step in Air-Breathing Propulsion for Space Access

The United States' National Aeronautics and Space Administration (NASA) has established a strategic plan for future activities in space. A primary goal of this plan is to make drastic improvements in the cost and safety of earth to low-earth-orbit transportation. One approach to achieving this goal is through the development of highly reusable, highly reliable space transportation systems analogous to the commercial airline system. In the year 2000, NASA selected the Rocket Based Combined Cycle (RBCC) engine as the next logical step towards this goal. NASA will develop a complete flight-weight, pump-fed engine system under the Integrated System Test of an Airbreathing Rocket (I(sup STAR)) Project. The objective of this project is develop a reusable engine capable of self-powering a vehicle through the air-augmented rocket, ramjet and scramjet modes required in all RBCC based operational vehicle concepts. The project is currently approved and funded to develop the engine through ground test demonstration. Plans are in place to proceed with flight demonstration pending funding approval. The project is in formulation phase and the Preliminary Requirements Review has been completed. The engine system and vehicle have been selected at the conceptual level. The I(sup STAR) engine concept is based on an air-breathing flowpath downselected from three configurations evaluated in NASA's Advanced Reusable Technology contract. The selected flowpath features rocket thrust chambers integrated into struts separating modular flowpath ducts, a variable geometry inlet, and a thermally choked throat. The engine will be approximately 220 inches long and 79 inches wide and fueled with a hydrocarbon fuel using liquid oxygen as the primary oxidizer candidate. The primary concept for the pump turbine drive is pressure-fed catalyzed hydrogen peroxide. In order to control costs, the flight demonstration vehicle will be launched from a B-52 aircraft. The vehicle concept is based on the Air Breathing Launch Vehicle 4 (ABLV4) lifting body configuration which has design heritage from NASA's NASP Program. The vehicle will be designed to accelerate from Mach 0.8 to Mach 7 and will be equipped with landing gear for horizontal landing. The complete vehicle, including the engine, will be designed for 25 flights and will be approximately 33 feet long with a total vehicle weight of approximately 25000 lbs.

Hutt, John J.↗
NASA NTRS1989

Computer Control For Ion Engines

Computer system controls start-up, steady-state operation, throttling, and shutdown of pair of xenon-ion propulsion engines. Controls direction of thrust of each engine through operation of gimbal stepping motors. Controls valves in propellant-storage and propellant-distribution system. Control software establishes and maintains efficient, stable operation over entire range of operating variables, and throttles engines to any point within range. Computer operates power supplies, valves, and flow controllers of two ion engines, ion-neutralizer subsystem, and other equipment. Designed for use in interplanetary flight, system adaptable to industrial use in ion-beam deposition of thin films.

Brophy, John R.↗
NASA NTRS1999

Numerical System Solver Developed for the National Cycle Program

As part of the National Cycle Program (NCP), a powerful new numerical solver has been developed to support the simulation of aeropropulsion systems. This software uses a hierarchical object-oriented design. It can provide steady-state and time-dependent solutions to nonlinear and even discontinuous problems typically encountered when aircraft and spacecraft propulsion systems are simulated. It also can handle constrained solutions, in which one or more factors may limit the behavior of the engine system. Timedependent simulation capabilities include adaptive time-stepping and synchronization with digital control elements. The NCP solver is playing an important role in making the NCP a flexible, powerful, and reliable simulation package.

Binder, Michael P.↗
NASA NTRS1982

Electronic/electric technology benefits study

The benefits and payoffs of advanced electronic/electric technologies were investigated for three types of aircraft. The technologies, evaluated in each of the three airplanes, included advanced flight controls, advanced secondary power, advanced avionic complements, new cockpit displays, and advanced air traffic control techniques. For the advanced flight controls, the near term considered relaxed static stability (RSS) with mechanical backup. The far term considered an advanced fly by wire system for a longitudinally unstable airplane. In the case of the secondary power systems, trades were made in two steps: in the near term, engine bleed was eliminated; in the far term bleed air, air plus hydraulics were eliminated. Using three commercial aircraft, in the 150, 350, and 700 passenger range, the technology value and pay-offs were quantified, with emphasis on the fiscal benefits. Weight reductions deriving from fuel saving and other system improvements were identified and the weight savings were cycled for their impact on TOGW (takeoff gross weight) and upon the performance of the airframes/engines. Maintenance, reliability, and logistic support were the other criteria.

Howison, W. W.↗
NASA NTRS2018

Validation & Verification of Electrical Components B2 Test Facility

The research focus of this project is to assist in the closure of Measurement, Monitoring and Control System (MMCS) and other electrical requirements in support of the B2 Space Launch System (SLS) Core Stage Green Run Test Project. Alongside this goal I am to understand project management tools to analyze and control activities/tasks associated with those items. The project I am working on will assist electrical engineers in developing and or identifying closure rationale for the MMCS and electrical requirements. Also as serving the role of a training project manager, I am to develop and maintain a method for tracking progress with estimate completion dates specifically identifying those items during this performance window. The methods I used in order to perform the research consisted of worddocuments, excel sheets, and pdf documents needed for review. For example, documents consisted of: a SLS Core Stage Green Run Facility Requirement Document (FRD) identifying the SSC MMCS and electrical requirements, a Stage Controller to SSC Interface Control Document (ICD) identifying the SSC requirements, and the B2 SLS Core Stage Green Run Test project System Requirements Document (SRD) which identifies the MMCS and electrical requirements. The files were sent to me by both mentors, Mr. Barry Robinson and Ms. Dawn Davis. Overall, the review process for the word documents and excel spreadsheets proved to be successful. The data for the electrical components were accurate and were consistent with the original recorded data. However, the consistency with the pdf documents did not follow up all the way. Attention to this mistake was made and further revisions were done in order for the data to agree with each other. Furthermore, an itinerary was designed using Microsoft Outlook in order to track progress with estimated completion dates. This project contributes to NASA/Center Missions and Goals through the Waterfall Model. The Waterfall Model is a linear system used for engineering design. In the Waterfall Model, the fourth step is Verification and Validation. This involves installation, testing, and debugging of the B2 SLS Core Stage electrical components. For the SLS Core Stage Green Run Test Project, each requirement contained in this approved requirements set will have at least one Verification Item (VI) assigned to it. During the design phase, VIs will mostly consist of Analysis or Inspection types. Design phase VIs and closure information will be documented in Dynamics Data Management System (DDMS) in the form of analysis reports and design documentation.

Bastian, Tyler↗
NASA NTRS2000

The MAP Autonomous Mission Control System

The Microwave Anisotropy Probe (MAP) mission is the second mission in NASA's Office of Space Science low-cost, Medium-class Explorers (MIDEX) program. The Explorers Program is designed to accomplish frequent, low cost, high quality space science investigations utilizing innovative, streamlined, efficient management, design and operations approaches. The MAP spacecraft will produce an accurate full-sky map of the cosmic microwave background temperature fluctuations with high sensitivity and angular resolution. The MAP spacecraft is planned for launch in early 2001, and will be staffed by only single-shift operations. During the rest of the time the spacecraft must be operated autonomously, with personnel available only on an on-call basis. Four (4) innovations will work cooperatively to enable a significant reduction in operations costs for the MAP spacecraft. First, the use of a common ground system for Spacecraft Integration and Test (I&T) as well as Operations. Second, the use of Finite State Modeling for intelligent autonomy. Third, the integration of a graphical planning engine to drive the autonomous systems without an intermediate manual step. And fourth, the ability for distributed operations via Web and pager access.

Breed, Juile↗
NASA NTRS1994

Implementing Software Safety in the NASA Environment

Until recently, NASA did not consider allowing computers total control of flight systems. Human operators, via hardware, have constituted the ultimate safety control. In an attempt to reduce costs, NASA has come to rely more and more heavily on computers and software to control space missions. (For example. software is now planned to control most of the operational functions of the International Space Station.) Thus the need for systematic software safety programs has become crucial for mission success. Concurrent engineering principles dictate that safety should be designed into software up front, not tested into the software after the fact. 'Cost of Quality' studies have statistics and metrics to prove the value of building quality and safety into the development cycle. Unfortunately, most software engineers are not familiar with designing for safety, and most safety engineers are not software experts. Software written to specifications which have not been safety analyzed is a major source of computer related accidents. Safer software is achieved step by step throughout the system and software life cycle. It is a process that includes requirements definition, hazard analyses, formal software inspections, safety analyses, testing, and maintenance. The greatest emphasis is placed on clearly and completely defining system and software requirements, including safety and reliability requirements. Unfortunately, development and review of requirements are the weakest link in the process. While some of the more academic methods, e.g. mathematical models, may help bring about safer software, this paper proposes the use of currently approved software methodologies, and sound software and assurance practices to show how, to a large degree, safety can be designed into software from the start. NASA's approach today is to first conduct a preliminary system hazard analysis (PHA) during the concept and planning phase of a project. This determines the overall hazard potential of the system to be built. Shortly thereafter, as the system requirements are being defined, the second iteration of hazard analyses takes place, the systems hazard analysis (SHA). During the systems requirements phase, decisions are made as to what functions of the system will be the responsibility of software. This is the most critical time to affect the safety of the software. From this point, software safety analyses as well as software engineering practices are the main focus for assuring safe software. While many of the steps proposed in this paper seem like just sound engineering practices, they are the best technical and most cost effective means to assure safe software within a safe system.

Wetherholt, Martha S.↗
NASA NTRS1998

Mission to the Solar System: Exploration and Discovery. A Mission and Technology Roadmap

Solar System exploration addresses some of humanity's most fundamental questions: How and when did life form on Earth? Does life exist elsewhere in the Solar System or in the Universe? - How did the Solar System form and evolve in time? - What can the other planets teach us about the Earth? This document describes a Mission and Technology Roadmap for addressing these and other fundamental Solar System Questions. A Roadmap Development Team of scientists, engineers, educators, and technologists worked to define the next evolutionary steps in in situ exploration, sample return, and completion of the overall Solar System survey. Guidelines were to "develop aa visionary, but affordable, mission and technology development Roadmap for the exploration of the Solar System in the 2000 to 2012 timeframe." The Roadmap provides a catalog of potential flight missions. (Supporting research and technology, ground-based observations, and laboratory research, which are no less important than flight missions, are not included in this Roadmap.)

Gulkis, S.↗
NASA NTRS1999

Common Analysis Tool Being Developed for Aeropropulsion: The National Cycle Program Within the Numerical Propulsion System Simulation Environment

The NASA Lewis Research Center is developing an environment for analyzing and designing aircraft engines-the Numerical Propulsion System Simulation (NPSS). NPSS will integrate multiple disciplines, such as aerodynamics, structure, and heat transfer, and will make use of numerical "zooming" on component codes. Zooming is the coupling of analyses at various levels of detail. NPSS uses the latest computing and communication technologies to capture complex physical processes in a timely, cost-effective manner. The vision of NPSS is to create a "numerical test cell" enabling full engine simulations overnight on cost-effective computing platforms. Through the NASA/Industry Cooperative Effort agreement, NASA Lewis and industry partners are developing a new engine simulation called the National Cycle Program (NCP). NCP, which is the first step toward NPSS and is its initial framework, supports the aerothermodynamic system simulation process for the full life cycle of an engine. U.S. aircraft and airframe companies recognize NCP as the future industry standard common analysis tool for aeropropulsion system modeling. The estimated potential payoff for NCP is a $50 million/yr savings to industry through improved engineering productivity.

Follen, Gregory J.↗
NASA NTRS2002

Space Solar Power Demonstrations: Challenges and Progress

The prospects of using electrical power beamed from space are coming closer to reality with the continued pursuit and improvements in the supporting space solar research and technology. Space Solar Power (SSP) has been explored off and on for approximately three decades as a viable alternative and clean energy source. Results produced through the more recent Space Solar Power Exploratory Research and Technology (SERT) program involving extensive participation by industry, universities, and government has provided a sound technical basis for believing that technology can be improved to the extent that SSP systems can be built, economically feasible, and successfully deployed in space. Considerable advancements have been made in conceptual designs and supporting technologies including solar power generation, wireless power transmission, power management distribution, thermal management and materials, and the integrated systems engineering assessments. Basic technologies have progressed to the point were the next logical step is to formulate and conduct sophisticated demonstrations involving prototype hardware as final proof of concepts and identify high end technology readiness levels in preparation for full scale SSP systems designs. In addition to continued technical development issues, environmental and safety issues must be addressed and appropriate actions taken to reassure the public and prepare them for the future use of this alternative renewable energy resource. Accomplishing these objectives will allow informed future decisions regarding further SSP and related R&D investments by both NASA management and prospective external partners. In particular, accomplishing these objectives will also guide further definition of SSP and related technology roadmaps including performance objectives, resources and schedules; including 'multi-purpose' applications (terrestrial markets, science, commercial development of space, and other government missions).

Howell, Joe T.↗
NASA NTRS2015

Systems Engineering Management Plan NASA Traffic Aware Planner Integration Into P-180 Airborne Test-Bed

NASA's Traffic Aware Planner (TAP) is a cockpit decision support tool that provides aircrew with vertical and lateral flight-path optimizations with the intent of achieving significant fuel and time savings, while automatically avoiding traffic, weather, and restricted airspace conflicts. A key step towards the maturation and deployment of TAP concerned its operational evaluation in a representative flight environment. This Systems Engineering Management Plan (SEMP) addresses the test-vehicle design, systems integration, and flight-test planning for the first TAP operational flight evaluations, which were successfully completed in November 2013. The trial outcomes are documented in the Traffic Aware Planner (TAP) flight evaluation paper presented at the 14th AIAA Aviation Technology, Integration, and Operations Conference, Atlanta, GA. (AIAA-2014-2166, Maris, J. M., Haynes, M. A., Wing, D. J., Burke, K. A., Henderson, J., & Woods, S. E., 2014).

Maris, John↗
NASA NTRS1976

The ABC's required for establishing a practical computerized plant engineering management data base system

A system's approach is outlined in the paper to assist facility and Plant Engineers improve their organization's data management system. The six basic steps identified may appear somewhat simple; however, adequate planning, proper resources, and the involvement of management will determine the success of a computerized facility management data base. Helpful suggestions are noted throughout the paper to insure the development of a practical computerized data management system.

Maiocco, F. R.↗
NASA NTRS1986

An expert system prototype for aiding in the development of software functional requirements for NASA Goddard's command management system: A case study and lessons learned

At NASA Goddard, the role of the command management system (CMS) is to transform general requests for spacecraft opeerations into detailed operational plans to be uplinked to the spacecraft. The CMS is part of the NASA Data System which entails the downlink of science and engineering data from NASA near-earth satellites to the user, and the uplink of command and control data to the spacecraft. Presently, it takes one to three years, with meetings once or twice a week, to determine functional requirements for CMS software design. As an alternative approach to the present technique of developing CMS software functional requirements, an expert system prototype was developed to aid in this function. Specifically, the knowledge base was formulated through interactions with domain experts, and was then linked to an existing expert system application generator called 'Knowledge Engineering System (Version 1.3).' Knowledge base development focused on four major steps: (1) develop the problem-oriented attribute hierachy; (2) determine the knowledge management approach; (3) encode the knowledge base; and (4) validate, test, certify, and evaluate the knowledge base and the expert system prototype as a whole. Backcasting was accomplished for validating and testing the expert system prototype. Knowledge refinement, evaluation, and implementation procedures of the expert system prototype were then transacted.

Liebowitz, Jay↗