Sample records for requirements engineering process

  1. 7 Processes that Enable NASA Software Engineering Technologies: Value-Added Process Engineering

    NASA Technical Reports Server (NTRS)

    Housch, Helen; Godfrey, Sally

    2011-01-01

    The presentation reviews Agency process requirements and the purpose, benefits, and experiences or seven software engineering processes. The processes include: product integration, configuration management, verification, software assurance, measurement and analysis, requirements management, and planning and monitoring.

  2. Aspects of the BPRIM Language for Risk Driven Process Engineering

    NASA Astrophysics Data System (ADS)

    Sienou, Amadou; Lamine, Elyes; Pingaud, Hervé; Karduck, Achim

    Nowadays organizations are exposed to frequent changes in business environment requiring continuous alignment of business processes on business strategies. This agility requires methods promoted in enterprise engineering approaches. Risk consideration in enterprise engineering is getting important since the business environment is becoming more and more competitive and unpredictable. Business processes are subject to the same quality requirements as material and human resources. Thus, process management is supposed to tackle value creation challenges but also the ones related to value preservation. Our research considers risk driven business process design as an integral part of enterprise engineering. A graphical modelling language for risk driven business process engineering was introduced in former research. This paper extends the language and handles questions related to modelling risk in organisational context.

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

  4. The Systems Engineering Process for Human Support Technology Development

    NASA Technical Reports Server (NTRS)

    Jones, Harry

    2005-01-01

    Systems engineering is designing and optimizing systems. This paper reviews the systems engineering process and indicates how it can be applied in the development of advanced human support systems. Systems engineering develops the performance requirements, subsystem specifications, and detailed designs needed to construct a desired system. Systems design is difficult, requiring both art and science and balancing human and technical considerations. The essential systems engineering activity is trading off and compromising between competing objectives such as performance and cost, schedule and risk. Systems engineering is not a complete independent process. It usually supports a system development project. This review emphasizes the NASA project management process as described in NASA Procedural Requirement (NPR) 7120.5B. The process is a top down phased approach that includes the most fundamental activities of systems engineering - requirements definition, systems analysis, and design. NPR 7120.5B also requires projects to perform the engineering analyses needed to ensure that the system will operate correctly with regard to reliability, safety, risk, cost, and human factors. We review the system development project process, the standard systems engineering design methodology, and some of the specialized systems analysis techniques. We will discuss how they could apply to advanced human support systems development. The purpose of advanced systems development is not directly to supply human space flight hardware, but rather to provide superior candidate systems that will be selected for implementation by future missions. The most direct application of systems engineering is in guiding the development of prototype and flight experiment hardware. However, anticipatory systems engineering of possible future flight systems would be useful in identifying the most promising development projects.

  5. Requirements for company-wide management

    NASA Technical Reports Server (NTRS)

    Southall, J. W.

    1980-01-01

    Computing system requirements were developed for company-wide management of information and computer programs in an engineering data processing environment. The requirements are essential to the successful implementation of a computer-based engineering data management system; they exceed the capabilities provided by the commercially available data base management systems. These requirements were derived from a study entitled The Design Process, which was prepared by design engineers experienced in development of aerospace products.

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

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

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

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

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

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

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

  13. 78 FR 4038 - Critical Parts for Airplane Propellers

    Federal Register 2010, 2011, 2012, 2013, 2014

    2013-01-18

    ... requiring a system of processes to identify and manage these parts throughout their service life. This rule... engineering process, a manufacturing process, and a service management process for propeller critical parts... engineering process, to how the part is manufactured and to how the part is maintained in service. Engineering...

  14. Building a Narrative Based Requirements Engineering Mediation Model

    NASA Astrophysics Data System (ADS)

    Ma, Nan; Hall, Tracy; Barker, Trevor

    This paper presents a narrative-based Requirements Engineering (RE) mediation model to help RE practitioners to effectively identify, define, and resolve conflicts of interest, goals, and requirements. Within the SPI community, there is a common belief that social, human, and organizational issues significantly impact on the effectiveness of software process improvement in general and the requirements engineering process in particularl. Conflicts among different stakeholders are an important human and social issue that need more research attention in the SPI and RE community. By drawing on the conflict resolution literature and IS literature, we argue that conflict resolution in RE is a mediated process, in which a requirements engineer can act as a mediator among different stakeholders. To address socio-psychological aspects of conflict in RE and SPI, Winslade and Monk (2000)'s narrative mediation model is introduced, justified, and translated into the context of RE.

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

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

  17. 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…

  18. Configuration evaluation and criteria plan. Volume 2: Evaluation critera plan (preliminary). Space Transportation Main Engine (STME) configuration study

    NASA Technical Reports Server (NTRS)

    Bair, E. K.

    1986-01-01

    The unbiased selection of the Space Transportation Main Engine (STME) configuration requires that the candidate engines be evaluated against a predetermined set of criteria which must be properly weighted to emphasize critical requirements defined prior to the actual evaluation. The evaluation and selection process involves the following functions: (1) determining if a configuration can satisfy basic STME requirements (yes/no); (2) defining the evaluation criteria; (3) selecting the criteria relative importance or weighting; (4) determining the weighting sensitivities; and (5) establishing a baseline for engine evaluation. The criteria weighting and sensitivities are cost related and are based on mission models and vehicle requirements. The evaluation process is used as a coarse screen to determine the candidate engines for the parametric studies and as a fine screen to determine concept(s) for conceptual design. The criteria used for the coarse and fine screen evaluation process is shown. The coarse screen process involves verifying that the candidate engines can meet the yes/no screening requirements and a semi-subjective quantitative evaluation. The fine screen engines have to meet all of the yes/no screening gates and are then subjected to a detailed evaluation or assessment using the quantitative cost evaluation processes. The option exists for re-cycling a concept through the quantitative portion of the screening and allows for some degree of optimization. The basic vehicle is a two stage LOX/HC, LOX/LH2 parallel burn vehicle capable of placing 150,000 lbs in low Earth orbit (LEO).

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

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

  1. Multidisciplinary and Active/Collaborative Approaches in Teaching Requirements Engineering

    ERIC Educational Resources Information Center

    Rosca, Daniela

    2005-01-01

    The requirements engineering course is a core component of the curriculum for the Master's in Software Engineering programme, at Monmouth University (MU). It covers the process, methods and tools specific to this area, together with the corresponding software quality issues. The need to produce software engineers with strong teamwork and…

  2. A Framework for Automating Cost Estimates in Assembly Processes

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

    Calton, T.L.; Peters, R.R.

    1998-12-09

    When a product concept emerges, the manufacturing engineer is asked to sketch out a production strategy and estimate its cost. The engineer is given an initial product design, along with a schedule of expected production volumes. The engineer then determines the best approach to manufacturing the product, comparing a variey of alternative production strategies. The engineer must consider capital cost, operating cost, lead-time, and other issues in an attempt to maximize pro$ts. After making these basic choices and sketching the design of overall production, the engineer produces estimates of the required capital, operating costs, and production capacity. 177is process maymore » iterate as the product design is refined in order to improve its pe~ormance or manufacturability. The focus of this paper is on the development of computer tools to aid manufacturing engineers in their decision-making processes. This computer sof~are tool provides aj?amework in which accurate cost estimates can be seamlessly derivedfiom design requirements at the start of any engineering project. Z+e result is faster cycle times through first-pass success; lower ll~e cycie cost due to requirements-driven design and accurate cost estimates derived early in the process.« less

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

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

  5. 48 CFR 48.102 - Policies.

    Code of Federal Regulations, 2012 CFR

    2012-10-01

    ... cost-effective value engineering procedures and processes. Agencies shall provide contractors a... services must require a mandatory value engineering program to reduce total ownership cost in accordance... VALUE ENGINEERING Policies and Procedures 48.102 Policies. (a) As required by Section 36 of the Office...

  6. 48 CFR 48.102 - Policies.

    Code of Federal Regulations, 2013 CFR

    2013-10-01

    ... cost-effective value engineering procedures and processes. Agencies shall provide contractors a... services must require a mandatory value engineering program to reduce total ownership cost in accordance... VALUE ENGINEERING Policies and Procedures 48.102 Policies. (a) As required by Section 36 of the Office...

  7. 40 CFR 63.11925 - What are my initial and continuous compliance requirements for process vents?

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... accepted chemical engineering principles, measurable process parameters, or physical or chemical laws or... scale. (iv) Engineering assessment including, but not limited to, the following: (A) Previous test..., and procedures used in the engineering assessment shall be documented. (3) For miscellaneous process...

  8. 40 CFR 63.11925 - What are my initial and continuous compliance requirements for process vents?

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... accepted chemical engineering principles, measurable process parameters, or physical or chemical laws or... scale. (iv) Engineering assessment including, but not limited to, the following: (A) Previous test..., and procedures used in the engineering assessment shall be documented. (3) For miscellaneous process...

  9. 40 CFR 63.11925 - What are my initial and continuous compliance requirements for process vents?

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... accepted chemical engineering principles, measurable process parameters, or physical or chemical laws or... scale. (iv) Engineering assessment including, but not limited to, the following: (A) Previous test..., and procedures used in the engineering assessment shall be documented. (3) For miscellaneous process...

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

  11. Rapid Development: A Content Analysis Comparison of Literature and Purposive Sampling of AFRL Rapid Reaction Projects

    DTIC Science & Technology

    2011-12-01

    systems engineering technical and technical management processes. Technical Planning, Stakeholders Requirements Development, and Architecture Design were...Stakeholder Requirements Definition, Architecture Design and Technical Planning. A purposive sampling of AFRL rapid development program managers and engineers...emphasize one process over another however Architecture Design , Implementation scored higher among Technical Processes. Decision Analysis, Technical

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

  13. Clinical image processing engine

    NASA Astrophysics Data System (ADS)

    Han, Wei; Yao, Jianhua; Chen, Jeremy; Summers, Ronald

    2009-02-01

    Our group provides clinical image processing services to various institutes at NIH. We develop or adapt image processing programs for a variety of applications. However, each program requires a human operator to select a specific set of images and execute the program, as well as store the results appropriately for later use. To improve efficiency, we design a parallelized clinical image processing engine (CIPE) to streamline and parallelize our service. The engine takes DICOM images from a PACS server, sorts and distributes the images to different applications, multithreads the execution of applications, and collects results from the applications. The engine consists of four modules: a listener, a router, a job manager and a data manager. A template filter in XML format is defined to specify the image specification for each application. A MySQL database is created to store and manage the incoming DICOM images and application results. The engine achieves two important goals: reduce the amount of time and manpower required to process medical images, and reduce the turnaround time for responding. We tested our engine on three different applications with 12 datasets and demonstrated that the engine improved the efficiency dramatically.

  14. Payload crew training complex simulation engineer's handbook

    NASA Technical Reports Server (NTRS)

    Shipman, D. L.

    1984-01-01

    The Simulation Engineer's Handbook is a guide for new engineers assigned to Experiment Simulation and a reference for engineers previously assigned. The experiment simulation process, development of experiment simulator requirements, development of experiment simulator hardware and software, and the verification of experiment simulators are discussed. The training required for experiment simulation is extensive and is only referenced in the handbook.

  15. Putting ROSE to Work: A Proposed Application of a Request-Oriented Scheduling Engine for Space Station Operations

    NASA Technical Reports Server (NTRS)

    Jaap, John; Muery, Kim

    2000-01-01

    Scheduling engines are found at the core of software systems that plan and schedule activities and resources. A Request-Oriented Scheduling Engine (ROSE) is one that processes a single request (adding a task to a timeline) and then waits for another request. For the International Space Station, a robust ROSE-based system would support multiple, simultaneous users, each formulating requests (defining scheduling requirements), submitting these requests via the internet to a single scheduling engine operating on a single timeline, and immediately viewing the resulting timeline. ROSE is significantly different from the engine currently used to schedule Space Station operations. The current engine supports essentially one person at a time, with a pre-defined set of requirements from many payloads, working in either a "batch" scheduling mode or an interactive/manual scheduling mode. A planning and scheduling process that takes advantage of the features of ROSE could produce greater customer satisfaction at reduced cost and reduced flow time. This paper describes a possible ROSE-based scheduling process and identifies the additional software component required to support it. Resulting changes to the management and control of the process are also discussed.

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

  17. Information use skills in the engineering programme accreditation criteria of four countries

    NASA Astrophysics Data System (ADS)

    Bradley, Cara

    2014-01-01

    The need for twenty-first century information skills in engineering practice, combined with the importance for engineering programmes to meet accreditation requirements, suggests that it may be worthwhile to explore the potential for closer alignment between librarians and their work with information literacy competencies to assist in meeting accreditation standards and graduating students with high-level information skills. This article explores whether and how information use skills are reflected in engineering programme accreditation standards of four countries: Canada, the USA, the UK, and Australia. Results indicate that there is significant overlap between the information use skills required of students by engineering accreditation processes and librarians' efforts to develop information literacy competencies in students, despite differences in terms used to describe these skills. Increased collaboration between engineering faculty and librarians has the potential to raise student information literacy levels and fulfil the information use-related requirements of accreditation processes.

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

  19. 40 CFR 63.1412 - Continuous process vent applicability assessment procedures and methods.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... engineering principles, measurable process parameters, or physical or chemical laws or properties. Examples of... values, and engineering assessment control applicability assessment requirements are to be determined... by using the engineering assessment procedures in paragraph (k) of this section. (f) Volumetric flow...

  20. 40 CFR 63.1412 - Continuous process vent applicability assessment procedures and methods.

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... engineering principles, measurable process parameters, or physical or chemical laws or properties. Examples of... values, and engineering assessment control applicability assessment requirements are to be determined... by using the engineering assessment procedures in paragraph (k) of this section. (f) Volumetric flow...

  1. 40 CFR 63.1412 - Continuous process vent applicability assessment procedures and methods.

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... engineering principles, measurable process parameters, or physical or chemical laws or properties. Examples of... values, and engineering assessment control applicability assessment requirements are to be determined... by using the engineering assessment procedures in paragraph (k) of this section. (f) Volumetric flow...

  2. 40 CFR 63.1412 - Continuous process vent applicability assessment procedures and methods.

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... engineering principles, measurable process parameters, or physical or chemical laws or properties. Examples of... values, and engineering assessment control applicability assessment requirements are to be determined... by using the engineering assessment procedures in paragraph (k) of this section. (f) Volumetric flow...

  3. 40 CFR 63.1412 - Continuous process vent applicability assessment procedures and methods.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    ... engineering principles, measurable process parameters, or physical or chemical laws or properties. Examples of... values, and engineering assessment control applicability assessment requirements are to be determined... by using the engineering assessment procedures in paragraph (k) of this section. (f) Volumetric flow...

  4. A Hydrogen Containment Process for Nuclear Thermal Engine Ground testing

    NASA Technical Reports Server (NTRS)

    Wang, Ten-See; Stewart, Eric; Canabal, Francisco

    2016-01-01

    The objective of this study is to propose a new total hydrogen containment process to enable the testing required for NTP engine development. This H2 removal process comprises of two unit operations: an oxygen-rich burner and a shell-and-tube type of heat exchanger. This new process is demonstrated by simulation of the steady state operation of the engine firing at nominal conditions.

  5. Security Requirements Management in Software Product Line Engineering

    NASA Astrophysics Data System (ADS)

    Mellado, Daniel; Fernández-Medina, Eduardo; Piattini, Mario

    Security requirements engineering is both a central task and a critical success factor in product line development due to the complexity and extensive nature of product lines. However, most of the current product line practices in requirements engineering do not adequately address security requirements engineering. Therefore, in this chapter we will propose a security requirements engineering process (SREPPLine) driven by security standards and based on a security requirements decision model along with a security variability model to manage the variability of the artefacts related to security requirements. The aim of this approach is to deal with security requirements from the early stages of the product line development in a systematic way, in order to facilitate conformance with the most relevant security standards with regard to the management of security requirements, such as ISO/IEC 27001 and ISO/IEC 15408.

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

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

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

  9. Multi-Center Implementation of NPR 7123.1A: A Collaborative Effort

    NASA Technical Reports Server (NTRS)

    Hall, Phillip B.; McNelis, Nancy B.

    2011-01-01

    Collaboration efforts between MSFC and GRC Engineering Directorates to implement the NASA Systems Engineering (SE) Engine have expanded over the past year to include other NASA Centers. Sharing information on designing, developing, and deploying SE processes has sparked further interest based on the realization that there is relative consistency in implementing SE processes at the institutional level. This presentation will provide a status on the ongoing multi-center collaboration and provide insight into how these NPR 7123.1A SE-aligned directives are being implemented and managed to better support the needs of NASA programs and projects. NPR 7123.1A, NASA Systems Engineering Processes and Requirements, was released on March 26, 2007 to clearly articulate and establish the requirements on the implementing organization for performing, supporting, and evaluating SE activities. In early 2009, MSFC and GRC Engineering Directorates undertook a collaborative opportunity to share their research and work associated with developing, updating and revising their SE process policy to comply and align with NPR 7123.1A. The goal is to develop instructions, checklists, templates, and procedures for each of the 17 SE process requirements so that systems engineers will be a position to define work that is process-driven. Greater efficiency and more effective technical management will be achieved due to consistency and repeatability of SE process implementation across and throughout each of the NASA centers. An added benefit will be to encourage NASA centers to pursue and collaborate on joint projects as a result of using common or similar processes, methods, tools, and techniques.

  10. The JSC Engineering Directorate Product Peer Review Process

    NASA Technical Reports Server (NTRS)

    Jenks, Kenneth C.

    2009-01-01

    The JSC Engineering Directorate has developed a Product Peer Review process in support of NASA policies for project management and systems engineering. The process complies with the requirements of NPR 7120.5, NPR 7123.1 and NPR 7150.2 and follows the guidance in NASA/SP-2007-6105. This presentation will give an overview of the process followed by a brief demonstration of an actual peer review, with audience participation.

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

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

  13. Using Life-Cycle Human Factors Engineering to Avoid $2.4 Million in Costs: Lessons Learned from NASA's Requirements Verification Process for Space Payloads

    NASA Technical Reports Server (NTRS)

    Carr, Daniel; Ellenberger, Rich

    2008-01-01

    The Human Factors Implementation Team (HFIT) process has been used to verify human factors requirements for NASA International Space Station (ISS) payloads since 2003, resulting in $2.4 million in avoided costs. This cost benefit has been realized by greatly reducing the need to process time-consuming formal waivers (exceptions) for individual requirements violations. The HFIT team, which includes astronauts and their technical staff, acts as the single source for human factors requirements integration of payloads. HFIT has the authority to provide inputs during early design phases, thus eliminating many potential requirements violations in a cost-effective manner. In those instances where it is not economically or technically feasible to meet the precise metric of a given requirement, HFIT can work with the payload engineers to develop common sense solutions and formally document that the resulting payload design does not materially affect the astronaut s ability to operate and interact with the payload. The HFIT process is fully ISO 9000 compliant and works concurrently with NASA s formal systems engineering work flow. Due to its success with payloads, the HFIT process is being adapted and extended to ISS systems hardware. Key aspects of this process are also being considered for NASA's Space Shuttle replacement, the Crew Exploration Vehicle.

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

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

  16. The MSFC Systems Engineering Guide: An Overview and Plan

    NASA Technical Reports Server (NTRS)

    Shelby, Jerry A.; Thomas, L. Dale

    2007-01-01

    As systems and subsystems requirements become more complex in the pursuit of the exploration of space, advanced technology will demand and require an integrated approach to the design and development of safe and successful space vehicles and there products. System engineers play a vital and key role in transforming mission needs into vehicle requirements that can be verified and validated. This will result in a safe and cost effective design that will satisfy the mission schedule. A key to successful vehicle design within systems engineering is communication. Communication, through a systems engineering infrastructure, will not only ensure that customers and stakeholders are satisfied but will also assist in identifying vehicle requirements; i.e. identification, integration and management. This vehicle design will produce a system that is verifiable, traceable, and effectively satisfies cost, schedule, performance, and risk throughout the life-cycle of the product. A communication infrastructure will bring about the integration of different engineering disciplines within vehicle design. A system utilizing these aspects will enhance system engineering performance and improve upon required activities such as Development of Requirements, Requirements Management, Functional Analysis, Test, Synthesis, Trade Studies, Documentation, and Lessons Learned to produce a successful final product. This paper will describe the guiding vision, progress to date and the plan forward for development of the Marshall Space Flight Center (MSFC) Systems Engineering Guide (SEG), a virtual systems engineering handbook and archive that will describe the system engineering processes that are used by MSFC in the development of complex systems such as the Ares launch vehicle. It is the intent of this website to be a "One Stop Shop" for our systems engineers that will provide tutorial information, an overview of processes and procedures and links to assist system engineering with guidance and references, and provide an archive of systems engineering artifacts produced by the many NASA projects developed and managed by MSFC over the years.

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

  18. 48 CFR 48.102 - Policies.

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... VALUE ENGINEERING Policies and Procedures 48.102 Policies. (a) As required by Section 36 of the Office... cost-effective value engineering procedures and processes. Agencies shall provide contractors a... engineering provisions in appropriate supply, service, architect-engineer and construction contracts as...

  19. Security Quality Requirements Engineering (SQUARE): Case Study Phase III

    DTIC Science & Technology

    2006-05-01

    Security Quality Requirements Engineering (SQUARE): Case Study Phase III Lydia Chung Frank Hung Eric Hough Don Ojoko-Adams Advisor...Engineering (SQUARE): Case Study Phase III CMU/SEI-2006-SR-003 Lydia Chung Frank Hung Eric Hough Don Ojoko-Adams Advisor Nancy R. Mead...1 1.1 The SQUARE Process ............................................................................... 1 1.2 Case Study Clients

  20. Requirements Development for the NASA Advanced Engineering Environment (AEE)

    NASA Technical Reports Server (NTRS)

    Rogers, Eric; Hale, Joseph P.; Zook, Keith; Gowda, Sanjay; Salas, Andrea O.

    2003-01-01

    The requirements development process for the Advanced Engineering Environment (AEE) is presented. This environment has been developed to allow NASA to perform independent analysis and design of space transportation architectures and technologies. Given the highly collaborative and distributed nature of AEE, a variety of organizations are involved in the development, operations and management of the system. Furthermore, there are additional organizations involved representing external customers and stakeholders. Thorough coordination and effective communication is essential to translate desired expectations of the system into requirements. Functional, verifiable requirements for this (and indeed any) system are necessary to fulfill several roles. Requirements serve as a contractual tool, configuration management tool, and as an engineering tool, sometimes simultaneously. The role of requirements as an engineering tool is particularly important because a stable set of requirements for a system provides a common framework of system scope and characterization among team members. Furthermore, the requirements provide the basis for checking completion of system elements and form the basis for system verification. Requirements are at the core of systems engineering. The AEE Project has undertaken a thorough process to translate the desires and expectations of external customers and stakeholders into functional system-level requirements that are captured with sufficient rigor to allow development planning, resource allocation and system-level design, development, implementation and verification. These requirements are maintained in an integrated, relational database that provides traceability to governing Program requirements and also to verification methods and subsystem-level requirements.

  1. Mission Engineering of a Rapid Cycle Spacecraft Logistics Fleet

    NASA Technical Reports Server (NTRS)

    Holladay, Jon; McClendon, Randy (Technical Monitor)

    2002-01-01

    The requirement for logistics re-supply of the International Space Station has provided a unique opportunity for engineering the implementation of NASA's first dedicated pressurized logistics carrier fleet. The NASA fleet is comprised of three Multi-Purpose Logistics Modules (MPLM) provided to NASA by the Italian Space Agency in return for operations time aboard the International Space Station. Marshall Space Flight Center was responsible for oversight of the hardware development from preliminary design through acceptance of the third flight unit, and currently manages the flight hardware sustaining engineering and mission engineering activities. The actual MPLM Mission began prior to NASA acceptance of the first flight unit in 1999 and will continue until the de-commission of the International Space Station that is planned for 20xx. Mission engineering of the MPLM program requires a broad focus on three distinct yet inter-related operations processes: pre-flight, flight operations, and post-flight turn-around. Within each primary area exist several complex subsets of distinct and inter-related activities. Pre-flight processing includes the evaluation of carrier hardware readiness for space flight. This includes integration of payload into the carrier, integration of the carrier into the launch vehicle, and integration of the carrier onto the orbital platform. Flight operations include the actual carrier operations during flight and any required real-time ground support. Post-flight processing includes de-integration of the carrier hardware from the launch vehicle, de-integration of the payload, and preparation for returning the carrier to pre-flight staging. Typical space operations are engineered around the requirements and objectives of a dedicated mission on a dedicated operational platform (i.e. Launch or Orbiting Vehicle). The MPLM, however, has expanded this envelope by requiring operations with both vehicles during flight as well as pre-launch and post-landing operations. These unique requirements combined with a success-oriented schedule of four flights within a ten-month period have provided numerous opportunities for understanding and improving operations processes. Furthermore, it has increased the knowledge base of future Payload Carrier and Launch Vehicle hardware and requirement developments. Discussion of the process flows and target areas for process improvement are provided in the subject paper. Special emphasis is also placed on supplying guidelines for hardware development. The combination of process knowledge and hardware development knowledge will provide a comprehensive overview for future vehicle developments as related to integration and transportation of payloads.

  2. CIM's bridge from CADD to CAM: Data management requirements for manufacturing engineering

    NASA Technical Reports Server (NTRS)

    Ford, S. J.

    1984-01-01

    Manufacturing engineering represents the crossroads of technical data management in a Computer Integrated Manufacturing (CIM) environment. Process planning, numerical control programming and tool design are the key functions which translate information from as engineered to as assembled. In order to transition data from engineering to manufacturing, it is necessary to introduce a series of product interpretations which contain an interim introduction of technical parameters. The current automation of the product definition and the production process places manufacturing engineering in the center of CAD/CAM with the responsibility of communicating design data to the factory floor via a manufacturing model of the data. A close look at data management requirements for manufacturing engineering is necessary in order to establish the overall specifications for CADD output, CAM input, and CIM integration. The functions and issues associated with the orderly evolution of computer aided engineering and manufacturing are examined.

  3. 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).

  4. System Engineering Processes at Kennedy Space Center for Development of SLS and Orion Launch Systems

    NASA Technical Reports Server (NTRS)

    Schafer, Eric; Stambolian, Damon; Henderson, Gena

    2013-01-01

    There are over 40 subsystems being developed for the future SLS and Orion Launch Systems at Kennedy Space Center. These subsystems are developed at the Kennedy Space Center Engineering Directorate. The Engineering Directorate at Kennedy Space Center follows a comprehensive design process which requires several different product deliverables during each phase of each of the subsystems. This Presentation describes this process with examples of where the process has been applied.

  5. Spacecraft systems engineering: An introduction to the process at GSFC

    NASA Technical Reports Server (NTRS)

    Fragomeni, Tony; Ryschkewitsch, Michael G.

    1993-01-01

    The main objective in systems engineering is to devise a coherent total system design capable of achieving the stated requirements. Requirements should be rigid. However, they should be continuously challenged, rechallenged and/or validated. The systems engineer must specify every requirement in order to design, document, implement and conduct the mission. Each and every requirement must be logically considered, traceable and evaluated through various analysis and trade studies in a total systems design. Margins must be determined to be realistic as well as adequate. The systems engineer must also continuously close the loop and verify system performance against the requirements. The fundamental role of the systems engineer, however, is to engineer, not manage. Yet, in large, complex missions, where more than one systems engineer is required, someone needs to manage the systems engineers, and we call them 'systems managers.' Systems engineering management is an overview function which plans, guides, monitors and controls the technical execution of a project as implemented by the systems engineers. As the project moves on through Phases A and B into Phase C/D, the systems engineering tasks become a small portion of the total effort. The systems management role increases since discipline subsystem engineers are conducting analyses and reviewing test data for final review and acceptance by the systems managers.

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

  7. Engineers: Designers--No Alibis.

    ERIC Educational Resources Information Center

    Stevens, Susan A. R.; Wilkins, Linda C.

    Engineering is the science, art, and business of designing and getting things done; engineers are required to make things happen through interpersonal relationships. At Monash University (Australia), a new course, Management for Engineers, was set up in 1990 to encourage a more holistic approach to the process of engineering. The course included…

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

  9. A Decision Analysis Tool for the Source Selection Process

    DTIC Science & Technology

    2006-03-01

    THE SOURCE SELECTION PROCESS THESIS Presented to the Faculty Department of Systems and Engineering Management 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 Engineering Management John R. Trumm, BS Captain, USAF March 2006

  10. 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; hide

    2011-01-01

    The purpose of this handbook is to provide guidance for implementing the Risk Management (RM) requirements of NASA Procedural Requirements (NPR) document NPR 8000.4A, Agency Risk Management Procedural Requirements [1], with a specific focus on programs and projects, and applying to each level of the NASA organizational hierarchy as requirements flow down. This handbook supports RM application within the NASA systems engineering process, and is a complement to the guidance contained in NASA/SP-2007-6105, NASA Systems Engineering Handbook [2]. Specifically, this handbook provides guidance that is applicable to the common technical processes of Technical Risk Management and Decision Analysis established by NPR 7123.1A, NASA Systems Engineering Process and Requirements [3]. These processes are part of the \\Systems Engineering Engine. (Figure 1) that is used to drive the development of the system and associated work products to satisfy stakeholder expectations in all mission execution domains, including safety, technical, cost, and schedule. Like NPR 7123.1A, NPR 8000.4A is a discipline-oriented NPR that intersects with product-oriented NPRs such as NPR 7120.5D, NASA Space Flight Program and Project Management Requirements [4]; NPR 7120.7, NASA Information Technology and Institutional Infrastructure Program and Project Management Requirements [5]; and NPR 7120.8, NASA Research and Technology Program and Project Management Requirements [6]. In much the same way that the NASA Systems Engineering Handbook is intended to provide guidance on the implementation of NPR 7123.1A, this handbook is intended to provide guidance on the implementation of NPR 8000.4A. 1.2 Scope and Depth This handbook provides guidance for conducting RM in the context of NASA program and project life cycles, which produce derived requirements in accordance with existing systems engineering practices that flow down through the NASA organizational hierarchy. The guidance in this handbook is not meant to be prescriptive. Instead, it is meant to be general enough, and contain a sufficient diversity of examples, to enable the reader to adapt the methods as needed to the particular risk management issues that he or she faces. The handbook highlights major issues to consider when managing programs and projects in the presence of potentially significant uncertainty, so that the user is better able to recognize and avoid pitfalls that might otherwise be experienced.

  11. 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!

  12. A multi-scale controlled tissue engineering scaffold prepared by 3D printing and NFES technology

    NASA Astrophysics Data System (ADS)

    Yan, Feifei; Liu, Yuanyuan; Chen, Haiping; Zhang, Fuhua; Zheng, Lulu; Hu, Qingxi

    2014-03-01

    The current focus in the field of life science is the use of tissue engineering scaffolds to repair human organs, which has shown great potential in clinical applications. Extracellular matrix morphology and the performance and internal structure of natural organs are required to meet certain requirements. Therefore, integrating multiple processes can effectively overcome the limitations of the individual processes and can take into account the needs of scaffolds for the material, structure, mechanical properties and many other aspects. This study combined the biological 3D printing technology and the near-field electro-spinning (NFES) process to prepare a multi-scale controlled tissue engineering scaffold. While using 3D printing technology to directly prepare the macro-scaffold, the compositing NFES process to build tissue micro-morphology ultimately formed a tissue engineering scaffold which has the specific extracellular matrix structure. This scaffold not only takes into account the material, structure, performance and many other requirements, but also focuses on resolving the controllability problems in macro- and micro-forming which further aim to induce cell directed differentiation, reproduction and, ultimately, the formation of target tissue organs. It has in-depth immeasurable significance to build ideal scaffolds and further promote the application of tissue engineering.

  13. Engineering Change Management Method Framework in Mechanical Engineering

    NASA Astrophysics Data System (ADS)

    Stekolschik, Alexander

    2016-11-01

    Engineering changes make an impact on different process chains in and outside the company, and lead to most error costs and time shifts. In fact, 30 to 50 per cent of development costs result from technical changes. Controlling engineering change processes can help us to avoid errors and risks, and contribute to cost optimization and a shorter time to market. This paper presents a method framework for controlling engineering changes at mechanical engineering companies. The developed classification of engineering changes and accordingly process requirements build the basis for the method framework. The developed method framework comprises two main areas: special data objects managed in different engineering IT tools and process framework. Objects from both areas are building blocks that can be selected to the overall business process based on the engineering process type and change classification. The process framework contains steps for the creation of change objects (both for overall change and for parts), change implementation, and release. Companies can select singleprocess building blocks from the framework, depending on the product development process and change impact. The developed change framework has been implemented at a division (10,000 employees) of a big German mechanical engineering company.

  14. Pahoa geothermal industrial park. Engineering and economic analysis for direct applications of geothermal energy in an industrial park at Pahoa, Hawaii

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

    Moreau, J.W.

    1980-12-01

    This engineering and economic study evaluated the potential for developing a geothermal industrial park in the Puna District near Pahoa on the Island of Hawaii. Direct heat industrial applications were analyzed from a marketing, engineering, economic, environmental, and sociological standpoint to determine the most viable industries for the park. An extensive literature search produced 31 existing processes currently using geothermal heat. An additional list was compiled indicating industrial processes that require heat that could be provided by geothermal energy. From this information, 17 possible processes were selected for consideration. Careful scrutiny and analysis of these 17 processes revealed three thatmore » justified detailed economic workups. The three processes chosen for detailed analysis were: an ethanol plant using bagasse and wood as feedstock; a cattle feed mill using sugar cane leaf trash as feedstock; and a papaya processing facility providing both fresh and processed fruit. In addition, a research facility to assess and develop other processes was treated as a concept. Consideration was given to the impediments to development, the engineering process requirements and the governmental support for each process. The study describes the geothermal well site chosen, the pipeline to transmit the hydrothermal fluid, and the infrastructure required for the industrial park. A conceptual development plan for the ethanol plant, the feedmill and the papaya processing facility was prepared. The study concluded that a direct heat industrial park in Pahoa, Hawaii, involves considerable risks.« less

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

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

  17. Requirements and test results for the qualification of thermal control coatings

    NASA Technical Reports Server (NTRS)

    Brzuskiewicz, J. E.; Zerlaut, G. A.; Lauder, K.; Miller, G. M.

    1988-01-01

    Paint type coatings are often used as engineering materials in critical satellite temperature control applications. The functional features of coatings used for temperature control purposes must remain stable throughout the satellite manufacturing process and the satellite mission. The selection of a particular coating depends on matching coating characteristics to mission requirements. The use of paint coatings on satellites, although having an extensive history, requires that the paint be qualified to each application on an individual basis. Thus, the qualification process through testing serves to ensure that paint coatings as engineering materials will fulfill design requirements.

  18. Requirements: Towards an understanding on why software projects fail

    NASA Astrophysics Data System (ADS)

    Hussain, Azham; Mkpojiogu, Emmanuel O. C.

    2016-08-01

    Requirement engineering is at the foundation of every successful software project. There are many reasons for software project failures; however, poorly engineered requirements process contributes immensely to the reason why software projects fail. Software project failure is usually costly and risky and could also be life threatening. Projects that undermine requirements engineering suffer or are likely to suffer from failures, challenges and other attending risks. The cost of project failures and overruns when estimated is very huge. Furthermore, software project failures or overruns pose a challenge in today's competitive market environment. It affects the company's image, goodwill, and revenue drive and decreases the perceived satisfaction of customers and clients. In this paper, requirements engineering was discussed. Its role in software projects success was elaborated. The place of software requirements process in relation to software project failure was explored and examined. Also, project success and failure factors were also discussed with emphasis placed on requirements factors as they play a major role in software projects' challenges, successes and failures. The paper relied on secondary data and empirical statistics to explore and examine factors responsible for the successes, challenges and failures of software projects in large, medium and small scaled software companies.

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

  20. Dynamic Environmental Qualification Techniques.

    DTIC Science & Technology

    1981-12-01

    environments peculiar to military operations and requirements. numerous dynamic qualification test methods have been established. It was the purpose...requires the achievement of the highest practicable degree in the standard- ization of items, materials and engineering practices within the...standard is described as "A document that established engineering and technical requirements for processes, pro’cedures, practices and methods that have

  1. Implementation of NASA Materials and Processes Requirements at the Goddard Space Flight Center

    NASA Technical Reports Server (NTRS)

    Powers, Charles E.

    2009-01-01

    This slide presentation reviews the history and current practices of the Materials Engineering Branch (MEB) at the Goddard Space Flight Center. Included in the presentation is a review of the general Materials and Processes (M&P) requirements in the NASA-STD-6016. The work that the Materials Engineering Branch does to support GSFC Projects is also reviewed. The Materials Engineering Branch capabilities are listed, the expertise that is available to GSFC projects is also listed. Included in the backup slides are forms that the MEB uses to identify the materials in the spacecraft under development.

  2. Advances in multi-scale modeling of solidification and casting processes

    NASA Astrophysics Data System (ADS)

    Liu, Baicheng; Xu, Qingyan; Jing, Tao; Shen, Houfa; Han, Zhiqiang

    2011-04-01

    The development of the aviation, energy and automobile industries requires an advanced integrated product/process R&D systems which could optimize the product and the process design as well. Integrated computational materials engineering (ICME) is a promising approach to fulfill this requirement and make the product and process development efficient, economic, and environmentally friendly. Advances in multi-scale modeling of solidification and casting processes, including mathematical models as well as engineering applications are presented in the paper. Dendrite morphology of magnesium and aluminum alloy of solidification process by using phase field and cellular automaton methods, mathematical models of segregation of large steel ingot, and microstructure models of unidirectionally solidified turbine blade casting are studied and discussed. In addition, some engineering case studies, including microstructure simulation of aluminum casting for automobile industry, segregation of large steel ingot for energy industry, and microstructure simulation of unidirectionally solidified turbine blade castings for aviation industry are discussed.

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

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

  5. Astrobiobound! Search for Life in the Solar System: Scientists and Engineers Bringing their Challenges to K-12 Students

    NASA Astrophysics Data System (ADS)

    Klug Boonstra, S. L.; Swann, J.; Manfredi, L.; Zippay, A.; Boonstra, D.

    2014-12-01

    The Next Generation Science Standards (NGSS) brought many dynamic opportunities and capabilities to the K-12 science classroom - especially with the inclusion of engineering. Using science as a context to help students engage in the engineering practices and engineering disciplinary core ideas is an essential step to students' understanding of how science drives engineering and how engineering enables science. Real world examples and applications are critical for students to see how these disciplines are integrated. Furthermore, the interface of science and engineering raise the level of science understanding, and facilitate higher order thinking skills through relevant experiences. Astrobiobound! is designed for the NGSS (Next Generation Science Standards) and CCSS (Common Core State Standards). Students also practice and build 21st Century Skills. Astrobiobound! help students see how science and systems engineering are integrated to achieve a focused scientific goal. Students engage in the engineering design process to design a space mission which requires them to balance the return of their science data with engineering limitations such as power, mass and budget. Risk factors also play a role during this simulation and adds to the excitement and authenticity. Astrobiobound! presents the authentic first stages of NASA mission design process. This simulation mirrors the NASA process in which the science goals, type of mission, and instruments to return required data to meet mission goals are proposed within mission budget before any of the construction part of engineering can begin. NASA scientists and engineers were consulted in the development of this activity as an authentic simulation of their mission proposal process.

  6. A Theory of Information Quality and a Framework for Its Implementation in the Requirements Engineering Process

    ERIC Educational Resources Information Center

    Grenn, Michael W.

    2013-01-01

    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…

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

  8. Application of laser anemometry in turbine engine research

    NASA Technical Reports Server (NTRS)

    Seasholtz, R. G.

    1983-01-01

    The application of laser anemometry to the study of flow fields in turbine engine components is reviewed. Included are discussions of optical configurations, seeding requirements, electronic signal processing, and data processing. Some typical results are presented along with a discussion of ongoing work.

  9. Application of laser anemometry in turbine engine research

    NASA Technical Reports Server (NTRS)

    Seasholtz, R. G.

    1982-01-01

    The application of laser anemometry to the study of flow fields in turbine engine components is reviewed. Included are discussions of optical configurations, seeding requirements, electronic signal processing, and data processing. Some typical results are presented along with a discussion of ongoing work.

  10. Stratified charge rotary aircraft engine technology enablement program

    NASA Technical Reports Server (NTRS)

    Badgley, P. R.; Irion, C. E.; Myers, D. M.

    1985-01-01

    The multifuel stratified charge rotary engine is discussed. A single rotor, 0.7L/40 cu in displacement, research rig engine was tested. The research rig engine was designed for operation at high speeds and pressures, combustion chamber peak pressure providing margin for speed and load excursions above the design requirement for a high is advanced aircraft engine. It is indicated that the single rotor research rig engine is capable of meeting the established design requirements of 120 kW, 8,000 RPM, 1,379 KPA BMEP. The research rig engine, when fully developed, will be a valuable tool for investigating, advanced and highly advanced technology components, and provide an understanding of the stratified charge rotary engine combustion process.

  11. CANISTER HANDLING FACILITY DESCRIPTION DOCUMENT

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

    J.F. Beesley

    The purpose of this facility description document (FDD) is to establish requirements and associated bases that drive the design of the Canister Handling Facility (CHF), which will allow the design effort to proceed to license application. This FDD will be revised at strategic points as the design matures. This FDD identifies the requirements and describes the facility design, as it currently exists, with emphasis on attributes of the design provided to meet the requirements. This FDD is an engineering tool for design control; accordingly, the primary audience and users are design engineers. This FDD is part of an iterative designmore » process. It leads the design process with regard to the flowdown of upper tier requirements onto the facility. Knowledge of these requirements is essential in performing the design process. The FDD follows the design with regard to the description of the facility. The description provided in this FDD reflects the current results of the design process.« less

  12. Space sensors for global change

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

    Canavan, G.H.

    1994-02-15

    Satellite measurements should contribute to a fuller understanding of the physical processes behind the radiation budget, exchange processes, and global change. Climate engineering requires global observation for early indications of predicted effects, which puts a premium on affordable, distributed constellations of satellites with effective, affordable sensors. Defense has a requirement for continuous global surveillance for warning of aggression, which could evolve from advanced sensors and satellites in development. Many climate engineering needs match those of defense technologies.

  13. 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…

  14. Engineering Complex Embedded Systems with State Analysis and the Mission Data System

    NASA Technical Reports Server (NTRS)

    Ingham, Michel D.; Rasmussen, Robert D.; Bennett, Matthew B.; Moncada, Alex C.

    2004-01-01

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

  15. 40 CFR 63.526 - Monitoring requirements.

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... vent. (D) Design analysis based on accepted chemical engineering principles, measurable process.... (i) For the purpose of determining de minimis status for emission points, engineering assessment may... operating conditions expected to yield the highest flow rate and concentration. Engineering assessment...

  16. 40 CFR 63.526 - Monitoring requirements.

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... vent. (D) Design analysis based on accepted chemical engineering principles, measurable process.... (i) For the purpose of determining de minimis status for emission points, engineering assessment may... operating conditions expected to yield the highest flow rate and concentration. Engineering assessment...

  17. 40 CFR 63.526 - Monitoring requirements.

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... vent. (D) Design analysis based on accepted chemical engineering principles, measurable process.... (i) For the purpose of determining de minimis status for emission points, engineering assessment may... operating conditions expected to yield the highest flow rate and concentration. Engineering assessment...

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

  19. The European Engineer: A British Civil Engineering Viewpoint.

    ERIC Educational Resources Information Center

    Fleming, George

    1988-01-01

    Confronts the problems of defining the European Engineer in terms of educational and practical training. Analyzes the supply and demand requirements of engineering management and practice. Compares these analyses with conditions in the United States. Gives details of the educational process in a number of European countries. (CW)

  20. Improvement of Selected Logistics Processes Using Quality Engineering Tools

    NASA Astrophysics Data System (ADS)

    Zasadzień, Michał; Žarnovský, Jozef

    2018-03-01

    Increase in the number of orders, the increasing quality requirements and the speed of order preparation require implementation of new solutions and improvement of logistics processes. Any disruption that occurs during execution of an order often leads to customer dissatisfaction, as well as loss of his/her confidence. The article presents a case study of the use of quality engineering methods and tools to improve the e-commerce logistic process. This made it possible to identify and prioritize key issues, identify their causes, and formulate improvement and prevention measures.

  1. The Institute for Software Engineering.

    ERIC Educational Resources Information Center

    Inselbert, Armond

    1982-01-01

    The Institute for Software Engineering, a data processing education, publishing and consulting organization with offices and members worldwide, is described. The goal of the Institute is to assist data processing management and staff in providing the service levels required to support an organization's business needs. (Author/MLW)

  2. Procurement engineering - the productivity factor

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

    Bargerstock, S.B.

    1993-01-01

    The industry is several years on the road to implementation of the Nuclear Management and Resources Council (NUMARC) initiatives on commercial-grade item dedication and procurement. Utilities have taken several approaches to involve engineering in the procurement process. A common result for the approaches is the additional operations and maintenance (O M) cost imposed by the added resource requirements. Procurement engineering productivity is a key element in controlling this business area. Experience shows that 400 to 500% improvements in productivity are possible with a 2-yr period. Improving the productivity of the procurement engineering function is important in today's competitive utility environment.more » Procurement engineering typically involves four distinct technical evaluation responsibilities along with several administrative areas. Technical evaluations include the functionally based safety classification of replacement components and parts (lacking a master parts list), the determination of dedication requirements for safety-related commercial-grade items, the preparation of a procurement specification to maintain the licensed design bases, and the equivalency evaluation of alternate items not requiring the design-change process. Administrative duties include obtaining technical review of vendor-supplied documentation, identifying obsolete parts and components, resolving material nonconformances, initiating the design-change process for replacement items (as needed), and providing technical support to O M. Although most utilities may not perform or require all the noted activities, a large percentage will apply to each utility station.« less

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

  4. Requirements model for an e-Health awareness portal

    NASA Astrophysics Data System (ADS)

    Hussain, Azham; Mkpojiogu, Emmanuel O. C.; Nawi, Mohd Nasrun M.

    2016-08-01

    Requirements engineering is at the heart and foundation of software engineering process. Poor quality requirements inevitably lead to poor quality software solutions. Also, poor requirement modeling is tantamount to designing a poor quality product. So, quality assured requirements development collaborates fine with usable products in giving the software product the needed quality it demands. In the light of the foregoing, the requirements for an e-Ebola Awareness Portal were modeled with a good attention given to these software engineering concerns. The requirements for the e-Health Awareness Portal are modeled as a contribution to the fight against Ebola and helps in the fulfillment of the United Nation's Millennium Development Goal No. 6. In this study requirements were modeled using UML 2.0 modeling technique.

  5. 49 CFR 240.231 - Requirements for locomotive engineers unfamiliar with physical characteristics in other than...

    Code of Federal Regulations, 2011 CFR

    2011-10-01

    ... with physical characteristics in other than joint operations. 240.231 Section 240.231 Transportation... Process § 240.231 Requirements for locomotive engineers unfamiliar with physical characteristics in other... characteristics of the territory pursuant to the railroad's certification program. (b) Except as provided in...

  6. 49 CFR 240.231 - Requirements for locomotive engineers unfamiliar with physical characteristics in other than...

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... with physical characteristics in other than joint operations. 240.231 Section 240.231 Transportation... Process § 240.231 Requirements for locomotive engineers unfamiliar with physical characteristics in other... characteristics of the territory pursuant to the railroad's certification program. (b) Except as provided in...

  7. 40 CFR 63.526 - Monitoring requirements.

    Code of Federal Regulations, 2011 CFR

    2011-07-01

    .... (D) Design analysis based on accepted chemical engineering principles, measurable process parameters... purpose of determining de minimis status for emission points, engineering assessment may be used to... expected to yield the highest flow rate and concentration. Engineering assessment includes, but is not...

  8. 40 CFR 63.526 - Monitoring requirements.

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    .... (D) Design analysis based on accepted chemical engineering principles, measurable process parameters... purpose of determining de minimis status for emission points, engineering assessment may be used to... expected to yield the highest flow rate and concentration. Engineering assessment includes, but is not...

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

  10. An Exploratory Study of Cost Engineering in Axiomatic Design: Creation of the Cost Model Based on an FR-DP Map

    NASA Technical Reports Server (NTRS)

    Lee, Taesik; Jeziorek, Peter

    2004-01-01

    Large complex projects cost large sums of money throughout their life cycle for a variety of reasons and causes. For such large programs, the credible estimation of the project cost, a quick assessment of the cost of making changes, and the management of the project budget with effective cost reduction determine the viability of the project. Cost engineering that deals with these issues requires a rigorous method and systematic processes. This paper introduces a logical framework to a&e effective cost engineering. The framework is built upon Axiomatic Design process. The structure in the Axiomatic Design process provides a good foundation to closely tie engineering design and cost information together. The cost framework presented in this paper is a systematic link between the functional domain (FRs), physical domain (DPs), cost domain (CUs), and a task/process-based model. The FR-DP map relates a system s functional requirements to design solutions across all levels and branches of the decomposition hierarchy. DPs are mapped into CUs, which provides a means to estimate the cost of design solutions - DPs - from the cost of the physical entities in the system - CUs. The task/process model describes the iterative process ot-developing each of the CUs, and is used to estimate the cost of CUs. By linking the four domains, this framework provides a superior traceability from requirements to cost information.

  11. Re-engineering: a prescription for hospitals.

    PubMed

    Bolton, C; Gordon, J R

    1994-01-01

    Previously applied mostly in large, private sector corporations, "re-engineering" is fast becoming a tool that hospitals can use to break away from the old to find a new and better way of doing things. Re-engineering, however, first requires strong leadership which is committed to employee involvement and re-inventing the process design to meet the needs of the customers. Once the transition has been completed, the processes and the organization must continue to be managed differently. This article reviews the processes involved in re-engineering, and discusses the implementation of the initiative at the Sunnybrook Health Science Centre in Toronto.

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

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

  14. Determining the compactive effort required to model pavement voids using the Corps of Engineers gyratory testing machine.

    DOT National Transportation Integrated Search

    1997-11-01

    Various agencies have used the Corps of Engineers gyratory testing machine (GTM) to design and test asphalt mixes. Materials properties such as shear strength and strain are measured during the compaction process. However, a compaction process duplic...

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

  16. QFD emphasis of IME design

    NASA Astrophysics Data System (ADS)

    Erickson, C. M.; Martinez, A.

    1993-06-01

    The 1992 Integrated Modular Engine (IME) design concept, proposed to the Air Force Space Systems Division as a candidate for a National Launch System (NLS) upper stage, emphasized a detailed Quality Functional Deployment (QFD) procedure which set the basis for its final selection. With a list of engine requirements defined and prioritized by the customer, a QFD procedure was implemented where the characteristics of a number of engine and component configurations were assessed for degree of requirement satisfaction. The QFD process emphasized operability, cost, reliability and performance, with relative importance specified by the customer. Existing technology and near-term advanced technology were surveyed to achieve the required design strategies. In the process, advanced nozzles, advanced turbomachinery, valves, controls, and operational procedures were evaluated. The integrated arrangement of three conventional bell nozzle thrust chambers with two advanced turbopump sets selected as the configuration meeting all requirements was rated significantly ahead of the other candidates, including the Aerospike and horizontal flow nozzle configurations.

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

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

  19. Engineering knowledge requirements for sand and dust on Mars

    NASA Technical Reports Server (NTRS)

    Kaplan, D. I.

    1991-01-01

    The successful landing of human beings on Mars and the establishment of a permanent outpost there will require an understanding of the Martian environment by the engineers. A key feature of the Martian environment is the nearly ubiquitous presence of sand and dust. The process which the engineering community will undertake to determine the sensitivities of their designs to the current level of knowledge about Mars sand and dust is emphasized. The interaction of the engineering community with the space exploration initiative (SEI) mission planners and management is described.

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

  1. Integration Framework of Process Planning based on Resource Independent Operation Summary to Support Collaborative Manufacturing

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

    Kulvatunyou, Boonserm; Wysk, Richard A.; Cho, Hyunbo

    2004-06-01

    In today's global manufacturing environment, manufacturing functions are distributed as never before. Design, engineering, fabrication, and assembly of new products are done routinely in many different enterprises scattered around the world. Successful business transactions require the sharing of design and engineering data on an unprecedented scale. This paper describes a framework that facilitates the collaboration of engineering tasks, particularly process planning and analysis, to support such globalized manufacturing activities. The information models of data and the software components that integrate those information models are described. The integration framework uses an Integrated Product and Process Data (IPPD) representation called a Resourcemore » Independent Operation Summary (RIOS) to facilitate the communication of business and manufacturing requirements. Hierarchical process modeling, process planning decomposition and an augmented AND/OR directed graph are used in this representation. The Resource Specific Process Planning (RSPP) module assigns required equipment and tools, selects process parameters, and determines manufacturing costs based on two-level hierarchical RIOS data. The shop floor knowledge (resource and process knowledge) and a hybrid approach (heuristic and linear programming) to linearize the AND/OR graph provide the basis for the planning. Finally, a prototype system is developed and demonstrated with an exemplary part. Java and XML (Extensible Markup Language) are used to ensure software and information portability.« less

  2. Silicon production process evaluations

    NASA Technical Reports Server (NTRS)

    1981-01-01

    Chemical engineering analysis of the HSC process (Hemlock Semiconductor Corporation) for producing silicon from dichlorosilane in a 1,000 MT/yr plant was continued. Progress and status for the chemical engineering analysis of the HSC process are reported for the primary process design engineering activities: base case conditions (85%), reaction chemistry (85%), process flow diagram (60%), material balance (60%), energy balance (30%), property data (30%), equipment design (20%) and major equipment list (10%). Engineering design of the initial distillation column (D-01, stripper column) in the process was initiated. The function of the distillation column is to remove volatile gases (such as hydrogen and nitrogen) which are dissolved in liquid chlorosilanes. Initial specifications and results for the distillation column design are reported including the variation of tray requirements (equilibrium stages) with reflux ratio for the distillation.

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

  4. The Algorithm Theoretical Basis Document for Level 1A Processing

    NASA Technical Reports Server (NTRS)

    Jester, Peggy L.; Hancock, David W., III

    2012-01-01

    The first process of the Geoscience Laser Altimeter System (GLAS) Science Algorithm Software converts the Level 0 data into the Level 1A Data Products. The Level 1A Data Products are the time ordered instrument data converted from counts to engineering units. This document defines the equations that convert the raw instrument data into engineering units. Required scale factors, bias values, and coefficients are defined in this document. Additionally, required quality assurance and browse products are defined in this document.

  5. A Knowledge Engineering Approach to Analysis and Evaluation of Construction Schedules

    DTIC Science & Technology

    1990-02-01

    software engineering discipline focusing on constructing KBSs. It is an incremental and cyclical process that requires the interaction of a domain expert(s...the U.S. Army Coips of Engineers ; and (3) the project management software developer, represented by Pinnell Engineering , Inc. Since the primary...the programming skills necessary to convert the raw knowledge intn a form a computer can understand. knowledge engineering : The software engineering

  6. ACUTE BEHAVORIAL EFFECTS FROM EXPOSURE TO TWO-STROKE ENGINE EXHAUST

    EPA Science Inventory

    Benefits of changing from two-stroke to four-stroke engines (and other remedial requirements) can be evaluated (monetized) from the standpoint of acute behavioral effects of human exposure to exhaust from these engines. The monetization process depends upon estimates of the magn...

  7. Virtual aluminum castings: An industrial application of ICME

    NASA Astrophysics Data System (ADS)

    Allison, John; Li, Mei; Wolverton, C.; Su, Xuming

    2006-11-01

    The automotive product design and manufacturing community is continually besieged by Hercule an engineering, timing, and cost challenges. Nowhere is this more evident than in the development of designs and manufacturing processes for cast aluminum engine blocks and cylinder heads. Increasing engine performance requirements coupled with stringent weight and packaging constraints are pushing aluminum alloys to the limits of their capabilities. To provide high-quality blocks and heads at the lowest possible cost, manufacturing process engineers are required to find increasingly innovative ways to cast and heat treat components. Additionally, to remain competitive, products and manufacturing methods must be developed and implemented in record time. To bridge the gaps between program needs and engineering reality, the use of robust computational models in up-front analysis will take on an increasingly important role. This article describes just such a computational approach, the Virtual Aluminum Castings methodology, which was developed and implemented at Ford Motor Company and demonstrates the feasibility and benefits of integrated computational materials engineering.

  8. In the soft-to-hard technical spectrum: Where is software engineering?

    NASA Technical Reports Server (NTRS)

    Leibfried, Theodore F.; Macdonald, Robert B.

    1992-01-01

    In the computer journals and tabloids, there have been a plethora of articles written about the software engineering field. But while advocates of the need for an engineering approach to software development, it is impressive how many authors have treated the subject of software engineering without adequately addressing the fundamentals of what engineering as a discipline consists of. A discussion is presented of the various related facets of this issue in a logical framework to advance the thesis that the software development process is necessarily an engineering process. The purpose is to examine more of the details of the issue of whether or not the design and development of software for digital computer processing systems should be both viewed and treated as a legitimate field of professional engineering. Also, the type of academic and professional level education programs that would be required to support a software engineering discipline is examined.

  9. Recent developments in turbomachinery component materials and manufacturing challenges for aero engine applications

    NASA Astrophysics Data System (ADS)

    Srinivas, G.; Raghunandana, K.; Satish Shenoy, B.

    2018-02-01

    In the recent years the development of turbomachinery materials performance enhancement plays a vital role especially in aircraft air breathing engines like turbojet engine, turboprop engine, turboshaft engine and turbofan engines. Especially the transonic flow engines required highly sophisticated materials where it can sustain the entire thrust which can create by the engine. The main objective of this paper is to give an overview of the present cost-effective and technological capabilities process for turbomachinery component materials. Especially the main focus is given to study the Electro physical, Photonic additive removal process and Electro chemical process for turbomachinery parts manufacture. The aeronautical propulsion based technologies are reviewed thoroughly where in surface reliability, geometrical precession, and material removal and highly strengthened composite material deposition rates usually difficult to cut dedicated steels, Titanium and Nickel based alloys. In this paper the past aeronautical and propulsion mechanical based manufacturing technologies, current sophisticated technologies and also future challenging material processing techniques are covered. The paper also focuses on the brief description of turbomachinery components of shaping process and coating in aeromechanical applications.

  10. Design of a high-speed digital processing element for parallel simulation

    NASA Technical Reports Server (NTRS)

    Milner, E. J.; Cwynar, D. S.

    1983-01-01

    A prototype of a custom designed computer to be used as a processing element in a multiprocessor based jet engine simulator is described. The purpose of the custom design was to give the computer the speed and versatility required to simulate a jet engine in real time. Real time simulations are needed for closed loop testing of digital electronic engine controls. The prototype computer has a microcycle time of 133 nanoseconds. This speed was achieved by: prefetching the next instruction while the current one is executing, transporting data using high speed data busses, and using state of the art components such as a very large scale integration (VLSI) multiplier. Included are discussions of processing element requirements, design philosophy, the architecture of the custom designed processing element, the comprehensive instruction set, the diagnostic support software, and the development status of the custom design.

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

  12. A Scenario-Based Process for Requirements Development: Application to Mission Operations Systems

    NASA Technical Reports Server (NTRS)

    Bindschadler, Duane L.; Boyles, Carole A.

    2008-01-01

    The notion of using operational scenarios as part of requirements development during mission formulation (Phases A & B) is widely accepted as good system engineering practice. In the context of developing a Mission Operations System (MOS), there are numerous practical challenges to translating that notion into the cost-effective development of a useful set of requirements. These challenges can include such issues as a lack of Project-level focus on operations issues, insufficient or improper flowdown of requirements, flowdown of immature or poor-quality requirements from Project level, and MOS resource constraints (personnel expertise and/or dollars). System engineering theory must be translated into a practice that provides enough structure and standards to serve as guidance, but that retains sufficient flexibility to be tailored to the needs and constraints of a particular MOS or Project. We describe a detailed, scenario-based process for requirements development. Identifying a set of attributes for high quality requirements, we show how the portions of the process address many of those attributes. We also find that the basic process steps are robust, and can be effective even in challenging Project environments.

  13. Aircraft Flight Modeling During the Optimization of Gas Turbine Engine Working Process

    NASA Astrophysics Data System (ADS)

    Tkachenko, A. Yu; Kuz'michev, V. S.; Krupenich, I. N.

    2018-01-01

    The article describes a method for simulating the flight of the aircraft along a predetermined path, establishing a functional connection between the parameters of the working process of gas turbine engine and the efficiency criteria of the aircraft. This connection is necessary for solving the optimization tasks of the conceptual design stage of the engine according to the systems approach. Engine thrust level, in turn, influences the operation of aircraft, thus making accurate simulation of the aircraft behavior during flight necessary for obtaining the correct solution. The described mathematical model of aircraft flight provides the functional connection between the airframe characteristics, working process of gas turbine engines (propulsion system), ambient and flight conditions and flight profile features. This model provides accurate results of flight simulation and the resulting aircraft efficiency criteria, required for optimization of working process and control function of a gas turbine engine.

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

  15. Integrating International Engineering Organizations For Successful ISS Operations

    NASA Technical Reports Server (NTRS)

    Blome, Elizabeth; Duggan, Matt; Patten, L.; Pieterek, Hhtrud

    2006-01-01

    The International Space Station (ISS) is a multinational orbiting space laboratory that is built in cooperation with 16 nations. The design and sustaining engineering expertise is spread worldwide. As the number of Partners with orbiting elements on the ISS grows, the challenge NASA is facing as the ISS integrator is to ensure that engineering expertise and data are accessible in a timely fashion to ensure ongoing operations and mission success. Integrating international engineering teams requires definition and agreement on common processes and responsibilities, joint training and the emergence of a unique engineering team culture. ISS engineers face daunting logistical and political challenges regarding data sharing requirements. To assure systematic information sharing and anomaly resolution of integrated anomalies, the ISS Partners are developing multi-lateral engineering interface procedures. Data sharing and individual responsibility are key aspects of this plan. This paper describes several examples of successful multilateral anomaly resolution. These successes were used to form the framework of the Partner to Partner engineering interface procedures, and this paper describes those currently documented multilateral engineering processes. Furthermore, it addresses the challenges experienced to date, and the forward work expected in establishing a successful working relationship with Partners as their hardware is launched.

  16. The Application of V&V within Reuse-Based Software Engineering

    NASA Technical Reports Server (NTRS)

    Addy, Edward

    1996-01-01

    Verification and Validation (V&V) is performed during application development for many systems, especially safety-critical and mission-critical systems. The V&V process is intended to discover errors as early as possible during the development process. Early discovery is important in order to minimize the cost and other impacts of correcting these errors. In reuse-based software engineering, decisions on the requirements, design and even implementation of domain assets can can be made prior to beginning development of a specific system. in order to bring the effectiveness of V&V to bear within reuse-based software engineering. V&V must be incorporated within the domain engineering process.

  17. The prospect of using large eddy and detached eddy simulations in engineering design, and the research required to get there

    PubMed Central

    Larsson, Johan; Wang, Qiqi

    2014-01-01

    In this paper, we try to look into the future to envision how large eddy and detached eddy simulations will be used in the engineering design process about 20–30 years from now. Some key challenges specific to the engineering design process are identified, and some of the critical outstanding problems and promising research directions are discussed. PMID:25024421

  18. 48 CFR 48.102 - Policies.

    Code of Federal Regulations, 2014 CFR

    2014-10-01

    ... VALUE ENGINEERING Policies and Procedures 48.102 Policies. (a) As required by 41 U.S.C. 1711, agencies shall establish and maintain cost-effective value engineering procedures and processes. Agencies shall... cost in accordance with 48.101(b)(2). However, there must be no sharing of value engineering savings in...

  19. Using Written-Answer Questions To Complement Numerical Problems. Case Study: A Separation Processes Course.

    ERIC Educational Resources Information Center

    Iveson, Simon M.

    2002-01-01

    Describes the process and outcome of including in assignments and examinations some questions requiring written answers along with traditional questions requiring only numerical calculations. Lists questions used in a chemical engineering course on separation processes along with sample responses from students. Student feedback indicates a…

  20. DREAMS and IMAGE: A Model and Computer Implementation for Concurrent, Life-Cycle Design of Complex Systems

    NASA Technical Reports Server (NTRS)

    Hale, Mark A.; Craig, James I.; Mistree, Farrokh; Schrage, Daniel P.

    1995-01-01

    Computing architectures are being assembled that extend concurrent engineering practices by providing more efficient execution and collaboration on distributed, heterogeneous computing networks. Built on the successes of initial architectures, requirements for a next-generation design computing infrastructure can be developed. These requirements concentrate on those needed by a designer in decision-making processes from product conception to recycling and can be categorized in two areas: design process and design information management. A designer both designs and executes design processes throughout design time to achieve better product and process capabilities while expanding fewer resources. In order to accomplish this, information, or more appropriately design knowledge, needs to be adequately managed during product and process decomposition as well as recomposition. A foundation has been laid that captures these requirements in a design architecture called DREAMS (Developing Robust Engineering Analysis Models and Specifications). In addition, a computing infrastructure, called IMAGE (Intelligent Multidisciplinary Aircraft Generation Environment), is being developed that satisfies design requirements defined in DREAMS and incorporates enabling computational technologies.

  1. An Approach to Help Departments Meet the New ABET Process Safety Requirements

    ERIC Educational Resources Information Center

    Vaughen, Bruce K.

    2012-01-01

    The proposed program criteria changes by the Accreditation Board for Engineering and Technology, Inc. (ABET), for chemical, biochemical, biomolecular, and similarly named programs includes a fundamental awareness expectation of the hazards involved in chemical processing for a graduating chemical engineer. As of July 2010, these four new words…

  2. Biocatalysis in the Pharmaceutical Industry: The Need for Speed

    PubMed Central

    2017-01-01

    The use of biocatalysis in the pharmaceutical industry continues to expand as a result of increased access to enzymes and the ability to engineer those enzymes to meet the demands of industrial processes. However, we are still just scratching the surface of potential biocatalytic applications. The time pressures present in pharmaceutical process development are incompatible with the long lead times required for engineering a suitable biocatalyst. Dramatic increases in the speed of protein engineering are needed to deliver on the ever increasing opportunities for industrial biocatalytic processes. PMID:28523096

  3. Biocatalysis in the Pharmaceutical Industry: The Need for Speed.

    PubMed

    Truppo, Matthew D

    2017-05-11

    The use of biocatalysis in the pharmaceutical industry continues to expand as a result of increased access to enzymes and the ability to engineer those enzymes to meet the demands of industrial processes. However, we are still just scratching the surface of potential biocatalytic applications. The time pressures present in pharmaceutical process development are incompatible with the long lead times required for engineering a suitable biocatalyst. Dramatic increases in the speed of protein engineering are needed to deliver on the ever increasing opportunities for industrial biocatalytic processes.

  4. Silicon production process evaluations

    NASA Technical Reports Server (NTRS)

    1982-01-01

    Chemical engineering analyses involving the preliminary process design of a plant (1,000 metric tons/year capacity) to produce silicon via the technology under consideration were accomplished. Major activities in the chemical engineering analyses included base case conditions, reaction chemistry, process flowsheet, material balance, energy balance, property data, equipment design, major equipment list, production labor and forward for economic analysis. The process design package provided detailed data for raw materials, utilities, major process equipment and production labor requirements necessary for polysilicon production in each process.

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

  6. The Requirement for Vocational Skills in the Engineering Industry in the Areas of Modena and Vienna. Synthesis Report.

    ERIC Educational Resources Information Center

    Gatti, Mario; Mereu, Maria Grazia; Tagliaferro, Claudio; Markowitsch, Jorg; Neuberger, Robert

    Requirements for vocational skills in the engineering industry in Modena, Italy, and Vienna, Austria, were studied. In Modena, employees of a representative sample of 90 small, medium, and large firms in the mechanical processing, agricultural machinery, and sports car manufacturing sectors were interviewed. In Vienna, data were collected through…

  7. A Strategic Plan of Academic Management System as Preparation for EAC Accreditation Visit--From UKM Perspective

    ERIC Educational Resources Information Center

    Ab-Rahman, Mohammad Syuhaimi; Yusoff, Abdul Rahman Mohd; Abdul, Nasrul Amir; Hipni, Afiq

    2015-01-01

    Development of a robust platform is important to ensure that the engineering accreditation process can run smoothly, completely and the most important is to fulfill the criteria requirements. In case of Malaysia, the preparation for EAC (Engineering Accreditation Committee) assessment required a good strategic plan of academic management system…

  8. High-performance wavelet engine

    NASA Astrophysics Data System (ADS)

    Taylor, Fred J.; Mellot, Jonathon D.; Strom, Erik; Koren, Iztok; Lewis, Michael P.

    1993-11-01

    Wavelet processing has shown great promise for a variety of image and signal processing applications. Wavelets are also among the most computationally expensive techniques in signal processing. It is demonstrated that a wavelet engine constructed with residue number system arithmetic elements offers significant advantages over commercially available wavelet accelerators based upon conventional arithmetic elements. Analysis is presented predicting the dynamic range requirements of the reported residue number system based wavelet accelerator.

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

  10. System Engineering Processes at Kennedy Space Center for Development of the SLS and Orion Launch Systems

    NASA Technical Reports Server (NTRS)

    Schafer, Eric J.

    2012-01-01

    There are over 40 subsystems being developed for the future SLS and Orion Launch Systems at Kennedy Space Center. These subsystems developed at the Kennedy Space Center Engineering Directorate follow a comprehensive design process which requires several different product deliverables during each phase of each of the subsystems. This Paper describes this process and gives an example of where the process has been applied.

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

  12. Embedding Sustainable Development at Cambridge University Engineering Department

    ERIC Educational Resources Information Center

    Fenner, Richard A.; Ainger, Charles M.; Cruickshank, Heather J.; Guthrie, Peter M.

    2005-01-01

    Purpose--The paper seeks to examine the latest stage in a process of change aimed at introducing concepts of sustainable development into the activities of the Department of Engineering at Cambridge University, UK. Design/methodology/approach--The rationale behind defining the skills which future engineers require is discussed and vehicles for…

  13. Teaching Process Engineering Principles Using an Ice Cream Maker

    ERIC Educational Resources Information Center

    Kaletunc, Gonul; Duemmel, Kevin; Gecik, Christopher

    2007-01-01

    The ice cream laboratory experiment is designed to illustrate and promote discussion of several engineering and science topics including material and energy balances, heat transfer, freezing, mass transfer, mixing, viscosity, and freezing point depression in a sophomore level engineering class. A pre-lab assignment requires the students to develop…

  14. Frontiers in Chemical Engineering. Research Needs and Opportunities.

    ERIC Educational Resources Information Center

    National Academy of Sciences - National Research Council, Washington, DC. Commission on Physical Sciences, Mathematics, and Resources.

    Chemical engineers play a key role in industries such as petroleum, food, artificial fibers, petrochemicals, plastics and many others. They are needed to tailor manufacturing technology to the requirements of products and to integrate product and process design. This report discusses how chemical engineers are continuing to address technological…

  15. Generalized Information Architecture for Managing Requirements in IBM?s Rational DOORS(r) Application.

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

    Aragon, Kathryn M.; Eaton, Shelley M.; McCornack, Marjorie Turner

    When a requirements engineering effort fails to meet expectations, often times the requirements management tool is blamed. Working with numerous project teams at Sandia National Laboratories over the last fifteen years has shown us that the tool is rarely the culprit; usually it is the lack of a viable information architecture with well- designed processes to support requirements engineering. This document illustrates design concepts with rationale, as well as a proven information architecture to structure and manage information in support of requirements engineering activities for any size or type of project. This generalized information architecture is specific to IBM's Rationalmore » DOORS (Dynamic Object Oriented Requirements System) software application, which is the requirements management tool in Sandia's CEE (Common Engineering Environment). This generalized information architecture can be used as presented or as a foundation for designing a tailored information architecture for project-specific needs. It may also be tailored for another software tool. Version 1.0 4 November 201« less

  16. The Scenario-Based Engineering Process (SEP): a user-centered approach for the development of health care systems.

    PubMed

    Harbison, K; Kelly, J; Burnell, L; Silva, J

    1995-01-01

    The Scenario-based Engineering Process (SEP) is a user-focused methodology for large and complex system design. This process supports new application development from requirements analysis with domain models to component selection, design and modification, implementation, integration, and archival placement. It is built upon object-oriented methodologies, domain modeling strategies, and scenario-based techniques to provide an analysis process for mapping application requirements to available components. We are using SEP in the health care applications that we are developing. The process has already achieved success in the manufacturing and military domains and is being adopted by many organizations. SEP should prove viable in any domain containing scenarios that can be decomposed into tasks.

  17. Engine-start Control Strategy of P2 Parallel Hybrid Electric Vehicle

    NASA Astrophysics Data System (ADS)

    Xiangyang, Xu; Siqi, Zhao; Peng, Dong

    2017-12-01

    A smooth and fast engine-start process is important to parallel hybrid electric vehicles with an electric motor mounted in front of the transmission. However, there are some challenges during the engine-start control. Firstly, the electric motor must simultaneously provide a stable driving torque to ensure the drivability and a compensative torque to drag the engine before ignition. Secondly, engine-start time is a trade-off control objective because both fast start and smooth start have to be considered. To solve these problems, this paper first analyzed the resistance of the engine start process, and established a physic model in MATLAB/Simulink. Then a model-based coordinated control strategy among engine, motor and clutch was developed. Two basic control strategy during fast start and smooth start process were studied. Simulation results showed that the control objectives were realized by applying given control strategies, which can meet different requirement from the driver.

  18. Engineering education in 21st century

    NASA Astrophysics Data System (ADS)

    Alam, Firoz; Sarkar, Rashid; La Brooy, Roger; Chowdhury, Harun

    2016-07-01

    The internationalization of engineering curricula and engineering practices has begun in Europe, Anglosphere (English speaking) nations and Asian emerging economies through the Bologna Process and International Engineering Alliance (Washington Accord). Both the Bologna Process and the Washington Accord have introduced standardized outcome based engineering competencies and frameworks for the attainment of these competencies by restructuring existing and undertaking some new measures for an intelligent adaptation of the engineering curriculum and pedagogy. Thus graduates with such standardized outcome based curriculum can move freely as professional engineers with mutual recognition within member nations. Despite having similar or near similar curriculum, Bangladeshi engineering graduates currently cannot get mutual recognition in nations of Washington Accord and the Bologna Process due to the non-compliance of outcome based curriculum and pedagogy. This paper emphasizes the steps that are required to undertake by the engineering educational institutions and the professional body in Bangladesh to make the engineering competencies, curriculum and pedagogy compliant to the global engineering alliance. Achieving such compliance will usher in a new era for the global mobility and global engagement by Bangladesh trained engineering graduates.

  19. Computer Design Technology of the Small Thrust Rocket Engines Using CAE / CAD Systems

    NASA Astrophysics Data System (ADS)

    Ryzhkov, V.; Lapshin, E.

    2018-01-01

    The paper presents an algorithm for designing liquid small thrust rocket engine, the process of which consists of five aggregated stages with feedback. Three stages of the algorithm provide engineering support for design, and two stages - the actual engine design. A distinctive feature of the proposed approach is a deep study of the main technical solutions at the stage of engineering analysis and interaction with the created knowledge (data) base, which accelerates the process and provides enhanced design quality. The using multifunctional graphic package Siemens NX allows to obtain the final product -rocket engine and a set of design documentation in a fairly short time; the engine design does not require a long experimental development.

  20. Engineering English and the High-Tech Industry: A Case Study of an English Needs Analysis of Process Integration Engineers at a Semiconductor Manufacturing Company in Taiwan

    ERIC Educational Resources Information Center

    Spence, Paul; Liu, Gi-Zen

    2013-01-01

    The global high-tech industry is characterized by extreme competitiveness, innovation, and widespread use of English. Consequently, Taiwanese high-tech companies require engineers that are talented in both their engineering and English abilities. In response to the lack of knowledge regarding the English skills needed by engineers in Taiwan's…

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

  2. Low Cost Process for Manufacture of Oxide Dispersion Strengthened (ODS) Turbine Nozzle Components.

    DTIC Science & Technology

    1979-12-01

    SWTTPROCESS FORJIANUFACTURE OF9OXIDE)ISPERSIONSTRENGTHENED (ODS) O0 TURBINE !IJOZZLE COMPONENTS, -- , General Electric Company Aircraft Engine Group...machining processes for low pressure turbine (LPT) vanes , high pressure turbine (HPT) vanes , and HPT band segments for the F101 engine . The primary intent...for aircraft turbine nozzle components. These processes were shown capable of maintaining required microstructures and properties for the vane and

  3. Teaching ethics to engineers: ethical decision making parallels the engineering design process.

    PubMed

    Bero, Bridget; Kuhlman, Alana

    2011-09-01

    In order to fulfill ABET requirements, Northern Arizona University's Civil and Environmental engineering programs incorporate professional ethics in several of its engineering courses. This paper discusses an ethics module in a 3rd year engineering design course that focuses on the design process and technical writing. Engineering students early in their student careers generally possess good black/white critical thinking skills on technical issues. Engineering design is the first time students are exposed to "grey" or multiple possible solution technical problems. To identify and solve these problems, the engineering design process is used. Ethical problems are also "grey" problems and present similar challenges to students. Students need a practical tool for solving these ethical problems. The step-wise engineering design process was used as a model to demonstrate a similar process for ethical situations. The ethical decision making process of Martin and Schinzinger was adapted for parallelism to the design process and presented to students as a step-wise technique for identification of the pertinent ethical issues, relevant moral theories, possible outcomes and a final decision. Students had greatest difficulty identifying the broader, global issues presented in an ethical situation, but by the end of the module, were better able to not only identify the broader issues, but also to more comprehensively assess specific issues, generate solutions and a desired response to the issue.

  4. PVD thermal barrier coating applications and process development for aircraft engines

    NASA Astrophysics Data System (ADS)

    Rigney, D. V.; Viguie, R.; Wortman, D. J.; Skelly, D. W.

    1997-06-01

    Thermal barrier coatings (TBCs) have been developed for application to aircraft engine components to improve service life in an increasingly hostile thermal environment. The choice of TBC type is related to the component, intended use, and economics. Selection of electron beam physical vapor deposition proc-essing for turbine blade is due in part to part size, surface finish requirements, thickness control needs, and hole closure issues. Process development of PVD TBCs has been carried out at several different sites, including GE Aircraft Engines (GEAE). The influence of processing variables on microstructure is dis-cussed, along with the GEAE development coater and initial experiences of pilot line operation.

  5. Modeling a distributed environment for a petroleum reservoir engineering application with software product line

    NASA Astrophysics Data System (ADS)

    de Faria Scheidt, Rafael; Vilain, Patrícia; Dantas, M. A. R.

    2014-10-01

    Petroleum reservoir engineering is a complex and interesting field that requires large amount of computational facilities to achieve successful results. Usually, software environments for this field are developed without taking care out of possible interactions and extensibilities required by reservoir engineers. In this paper, we present a research work which it is characterized by the design and implementation based on a software product line model for a real distributed reservoir engineering environment. Experimental results indicate successfully the utilization of this approach for the design of distributed software architecture. In addition, all components from the proposal provided greater visibility of the organization and processes for the reservoir engineers.

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

  7. Introducing the CERT (Trademark) Resiliency Engineering Framework: Improving the Security and Sustainability Processes

    DTIC Science & Technology

    2007-05-01

    Organizational Structure 40 6.1.3 Funding Model 40 6.1.4 Role of Information Technology 40 6.2 Considering Process Improvement 41 6.2.1 Dimensions of...to the process definition for resiliency engineering. 6.1.3 Funding Model Just as organizational structures tend to align across security and...responsibility. Adopting an enter- prise view of operational resiliency and a process improvement approach requires that the funding model evolve to one

  8. Power processing and control requirements of dispersed solar thermal electric generation systems

    NASA Technical Reports Server (NTRS)

    Das, R. L.

    1980-01-01

    Power Processing and Control requirements of Dispersed Receiver Solar Thermal Electric Generation Systems are presented. Kinematic Stirling Engines, Brayton Engines and Rankine Engines are considered as prime movers. Various types of generators are considered for ac and dc link generations. It is found that ac-ac Power Conversion is not suitable for implementation at this time. It is also found that ac-dc-ac Power Conversion with a large central inverter is more efficient than ac-dc-ac Power Conversion using small dispersed inverters. Ac-link solar thermal electric plants face potential stability and synchronization problems. Research and development efforts are needed in improving component performance characteristics and generation efficiency to make Solar Thermal Electric Generation economically attractive.

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

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

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

  12. Problem-Based Learning in Engineering Ethics Courses

    ERIC Educational Resources Information Center

    Kirkman, Robert

    2016-01-01

    I describe the first stages of a process of design research in which I employ problem-based learning in a course in engineering ethics, which fulfills a requirement for students in engineering degree programs. The aim of the course is to foster development of particular cognitive skills contributing to moral imagination, a capacity to notice,…

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

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

  15. An Interdisciplinary Approach for Understanding Information Utilization in Engineering and Product Design

    ERIC Educational Resources Information Center

    Bi, Youyi

    2017-01-01

    Human-centered design requires thorough understanding of people (e.g. customers, designers, engineers) in order to better satisfy the needs and expectations of all stakeholders in the design process. Designers are able to create better products by incorporating customers' subjective evaluations on products. Engineers can also build better tools…

  16. Experimental Replication of an Aeroengine Combustion Instability

    NASA Technical Reports Server (NTRS)

    Cohen, J. M.; Hibshman, J. R.; Proscia, W.; Rosfjord, T. J.; Wake, B. E.; McVey, J. B.; Lovett, J.; Ondas, M.; DeLaat, J.; Breisacher, K.

    2000-01-01

    Combustion instabilities in gas turbine engines are most frequently encountered during the late phases of engine development, at which point they are difficult and expensive to fix. The ability to replicate an engine-traceable combustion instability in a laboratory-scale experiment offers the opportunity to economically diagnose the problem (to determine the root cause), and to investigate solutions to the problem, such as active control. The development and validation of active combustion instability control requires that the causal dynamic processes be reproduced in experimental test facilities which can be used as a test bed for control system evaluation. This paper discusses the process through which a laboratory-scale experiment was designed to replicate an instability observed in a developmental engine. The scaling process used physically-based analyses to preserve the relevant geometric, acoustic and thermo-fluid features. The process increases the probability that results achieved in the single-nozzle experiment will be scalable to the engine.

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

  18. Building Safer Systems With SpecTRM

    NASA Technical Reports Server (NTRS)

    2003-01-01

    System safety, an integral component in software development, often poses a challenge to engineers designing computer-based systems. While the relaxed constraints on software design allow for increased power and flexibility, this flexibility introduces more possibilities for error. As a result, system engineers must identify the design constraints necessary to maintain safety and ensure that the system and software design enforces them. Safeware Engineering Corporation, of Seattle, Washington, provides the information, tools, and techniques to accomplish this task with its Specification Tools and Requirements Methodology (SpecTRM). NASA assisted in developing this engineering toolset by awarding the company several Small Business Innovation Research (SBIR) contracts with Ames Research Center and Langley Research Center. The technology benefits NASA through its applications for Space Station rendezvous and docking. SpecTRM aids system and software engineers in developing specifications for large, complex safety critical systems. The product enables engineers to find errors early in development so that they can be fixed with the lowest cost and impact on the system design. SpecTRM traces both the requirements and design rationale (including safety constraints) throughout the system design and documentation, allowing engineers to build required system properties into the design from the beginning, rather than emphasizing assessment at the end of the development process when changes are limited and costly.System safety, an integral component in software development, often poses a challenge to engineers designing computer-based systems. While the relaxed constraints on software design allow for increased power and flexibility, this flexibility introduces more possibilities for error. As a result, system engineers must identify the design constraints necessary to maintain safety and ensure that the system and software design enforces them. Safeware Engineering Corporation, of Seattle, Washington, provides the information, tools, and techniques to accomplish this task with its Specification Tools and Requirements Methodology (SpecTRM). NASA assisted in developing this engineering toolset by awarding the company several Small Business Innovation Research (SBIR) contracts with Ames Research Center and Langley Research Center. The technology benefits NASA through its applications for Space Station rendezvous and docking. SpecTRM aids system and software engineers in developing specifications for large, complex safety critical systems. The product enables engineers to find errors early in development so that they can be fixed with the lowest cost and impact on the system design. SpecTRM traces both the requirements and design rationale (including safety constraints) throughout the system design and documentation, allowing engineers to build required system properties into the design from the beginning, rather than emphasizing assessment at the end of the development process when changes are limited and costly.

  19. 15 CFR 801.9 - Reports required.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ...); industrial engineering services; industrial-type maintenance, installation, alteration, and training services... services; educational and training services; engineering, architectural, and surveying services; financial... assets covered by the BE-125 survey are rights related to: Industrial processes and products; books...

  20. 15 CFR 801.9 - Reports required.

    Code of Federal Regulations, 2010 CFR

    2010-01-01

    ...); industrial engineering services; industrial-type maintenance, installation, alteration, and training services... services; educational and training services; engineering, architectural, and surveying services; financial... assets covered by the BE-125 survey are rights related to: Industrial processes and products; books...

  1. 15 CFR 801.9 - Reports required.

    Code of Federal Regulations, 2012 CFR

    2012-01-01

    ...); industrial engineering services; industrial-type maintenance, installation, alteration, and training services... services; educational and training services; engineering, architectural, and surveying services; financial... assets covered by the BE-125 survey are rights related to: Industrial processes and products; books...

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

  3. Introducing new technologies into Space Station subsystems

    NASA Technical Reports Server (NTRS)

    Wiskerchen, Michael J.; Mollakarimi, Cindy L.

    1989-01-01

    A new systems engineering technology has been developed and applied to Shuttle processing. The new engineering approach emphasizes the identification, quantitative assessment, and management of system performance and risk related to the dynamic nature of requirements, technology, and operational concepts. The Space Shuttle Tile Automation System is described as an example of the first application of the new engineering technology. Lessons learned from the Shuttle processing experience are examined, and concepts are presented which are applicable to the design and development of the Space Station Freedom.

  4. Durability Evaluation of the Effects of Hydro-processed Renewable Jet (HRJ) Blended at 50% with Petroleum JP-8 on a Navistar Maxxforce D10 9.3L Engine

    DTIC Science & Technology

    2012-05-01

    Effects of Hydro-processed Renewable Jet (HRJ) blended at 50% with petroleum JP-8 on a Navistar Maxxforce D10 9.3L Engine 5a. CONTRACT NUMBER...report will be used to assess the effect of the HRJP-8 fuel on engine performance and durability as compared to JP-8. This evaluation requires that two...Hour Durability). Modifications to this procedure are primarily increases to the operating temperatures of the engine coolant, combustion air and

  5. Design of an embedded inverse-feedforward biomolecular tracking controller for enzymatic reaction processes.

    PubMed

    Foo, Mathias; Kim, Jongrae; Sawlekar, Rucha; Bates, Declan G

    2017-04-06

    Feedback control is widely used in chemical engineering to improve the performance and robustness of chemical processes. Feedback controllers require a 'subtractor' that is able to compute the error between the process output and the reference signal. In the case of embedded biomolecular control circuits, subtractors designed using standard chemical reaction network theory can only realise one-sided subtraction, rendering standard controller design approaches inadequate. Here, we show how a biomolecular controller that allows tracking of required changes in the outputs of enzymatic reaction processes can be designed and implemented within the framework of chemical reaction network theory. The controller architecture employs an inversion-based feedforward controller that compensates for the limitations of the one-sided subtractor that generates the error signals for a feedback controller. The proposed approach requires significantly fewer chemical reactions to implement than alternative designs, and should have wide applicability throughout the fields of synthetic biology and biological engineering.

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

  7. Compute as Fast as the Engineers Can Think! ULTRAFAST COMPUTING TEAM FINAL REPORT

    NASA Technical Reports Server (NTRS)

    Biedron, R. T.; Mehrotra, P.; Nelson, M. L.; Preston, M. L.; Rehder, J. J.; Rogersm J. L.; Rudy, D. H.; Sobieski, J.; Storaasli, O. O.

    1999-01-01

    This report documents findings and recommendations by the Ultrafast Computing Team (UCT). In the period 10-12/98, UCT reviewed design case scenarios for a supersonic transport and a reusable launch vehicle to derive computing requirements necessary for support of a design process with efficiency so radically improved that human thought rather than the computer paces the process. Assessment of the present computing capability against the above requirements indicated a need for further improvement in computing speed by several orders of magnitude to reduce time to solution from tens of hours to seconds in major applications. Evaluation of the trends in computer technology revealed a potential to attain the postulated improvement by further increases of single processor performance combined with massively parallel processing in a heterogeneous environment. However, utilization of massively parallel processing to its full capability will require redevelopment of the engineering analysis and optimization methods, including invention of new paradigms. To that end UCT recommends initiation of a new activity at LaRC called Computational Engineering for development of new methods and tools geared to the new computer architectures in disciplines, their coordination, and validation and benefit demonstration through applications.

  8. Naval Systems Engineering Guide

    DTIC Science & Technology

    2004-10-01

    Decision Critical Design Review System Integration Activities IOC FRP Decision Review Production & Deployment Sustainment IOT & FOC Sustainmen...reentered when things change significantly, such as funding, requirements, or schedule. This process must start at the very beginning of a Major...outputs through sub-processes will reveal a number of things : a. Determine the level of process applicability and tailoring required. b. Additional

  9. Enhancing healthcare process design with human factors engineering and reliability science, part 1: setting the context.

    PubMed

    Boston-Fleischhauer, Carol

    2008-01-01

    The design and implementation of efficient, effective, and safe processes are never-ending challenges in healthcare. Less than optimal performance levels and rising concerns about patient safety suggest that traditional process design methods are insufficient to meet design requirements. In this 2-part series, the author presents human factors engineering and reliability science as important knowledge to enhance existing operational and clinical process design methods in healthcare. An examination of these theories, application approaches, and examples are presented.

  10. Algae to Bio-Crude in Less Than 60 Minutes

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

    Elliott, Doug

    Engineers have created a chemical process that produces useful crude oil just minutes after engineers pour in harvested algae -- a verdant green paste with the consistency of pea soup. The PNNL team combined several chemical steps into one continuous process that starts with an algae slurry that contains as much as 80 to 90 percent water. Most current processes require the algae to be dried -- an expensive process that takes a lot of energy. The research has been licensed by Genifuel Corp.

  11. Algae to Bio-Crude in Less Than 60 Minutes

    ScienceCinema

    Elliott, Doug

    2018-01-16

    Engineers have created a chemical process that produces useful crude oil just minutes after engineers pour in harvested algae -- a verdant green paste with the consistency of pea soup. The PNNL team combined several chemical steps into one continuous process that starts with an algae slurry that contains as much as 80 to 90 percent water. Most current processes require the algae to be dried -- an expensive process that takes a lot of energy. The research has been licensed by Genifuel Corp.

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

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

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

  15. A Systems Engineering Approach to Quality Assurance for Aerospace Testing

    NASA Technical Reports Server (NTRS)

    Shepherd, Christena C.

    2014-01-01

    On the surface, it appears that AS9100 has little to say about how to apply a Quality Management System (QMS) to major aerospace test programs (or even smaller ones). It also appears that there is little in the quality engineering Body of Knowledge (BOK) that applies to testing, unless it is nondestructive examination (NDE), or some type of lab or bench testing associated with the manufacturing process. However, if one examines: a) how the systems engineering (SE) processes are implemented throughout a test program; and b) how these SE processes can be mapped to the requirements of AS9100, a number of areas for involvement of the quality professional are revealed. What often happens is that quality assurance during a test program is limited to inspections of the test article; what could be considered a manufacturing al fresco approach. This limits the quality professional and is a disservice to the programs and projects, since there are a number of ways that quality can enhance critical processes, and support efforts to improve risk reduction, efficiency and effectiveness. The Systems Engineering (SE) discipline is widely used in aerospace to ensure the progress from Stakeholder Expectations (the President, Congress, the taxpayers) to a successful, delivered product or service. Although this is well known, what is not well known is that these same SE processes are implemented in varying complexity, to prepare for and implement test projects that support research, development, verification and validation, qualification, and acceptance test projects. Although the test organization's terminology may vary from the SE terminology, and from one test service provider to another, the basic process is followed by successful, reliable testing organizations. For this analysis, NASA Procedural Requirements (NPR) 7123.1, NASA Systems Engineering Processes and Requirements is used to illustrate the SE processes that are used for major aerospace testing. Many of these processes are also implemented for smaller test projects, and this set of processes will also look familiar to those who have participated in launch site activation and flight demonstrations.

  16. Reference Model for Project Support Environments Version 1.0

    DTIC Science & Technology

    1993-02-28

    relationship with the framework’s Process Support services and with the Lifecycle Process Engineering services. Examples: "* ORCA (Object-based...Design services. Examples: "* ORCA (Object-based Requirements Capture and Analysis). "* RETRAC (REquirements TRACeability). 4.3 Life-Cycle Process...34traditional" computer tools. Operations: Examples of audio and video processing operations include: "* Create, modify, and delete sound and video data

  17. Requirements management and control

    NASA Technical Reports Server (NTRS)

    Robbins, Red

    1993-01-01

    The systems engineering process for thermal nuclear propulsion requirements and configuration definition is described in outline and graphic form. Functional analysis and mission attributes for a Mars exploration mission are also addressed.

  18. A Study of Emotions in Requirements Engineering

    NASA Astrophysics Data System (ADS)

    Colomo-Palacios, Ricardo; Hernández-López, Adrián; García-Crespo, Ángel; Soto-Acosta, Pedro

    Requirements engineering (RE) is a crucial activity in software development projects. This phase in the software development cycle is knowledge intensive, and thus, human capital intensive. From the human point of view, emotions play an important role in behavior and can even act as behavioral motivators. Thus, if we consider that RE represents a set of knowledge-intensive tasks, which include acceptance and negotiation activities, then the emotional factor represents a key element in these issues. However, the emotional factor in RE has not received the attention it deserves. This paper aims to integrate the stakeholder's emotions into the requirement process, proposing to catalogue them like any other factor in the process such as clarity or stability. Results show that high arousal and low pleasure levels are predictors of high versioning requirements.

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

  20. Using task analysis to improve the requirements elicitation in health information system.

    PubMed

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

    2007-01-01

    This paper describes the application of task analysis within the design process of a Web-based information system for managing clinical information in hemophilia care, in order to improve the requirements elicitation and, consequently, to validate the domain model obtained in a previous phase of the design process (system analysis). The use of task analysis in this case proved to be a practical and efficient way to improve the requirements engineering process by involving users in the design process.

  1. Precision manufacturing for clinical-quality regenerative medicines.

    PubMed

    Williams, David J; Thomas, Robert J; Hourd, Paul C; Chandra, Amit; Ratcliffe, Elizabeth; Liu, Yang; Rayment, Erin A; Archer, J Richard

    2012-08-28

    Innovations in engineering applied to healthcare make a significant difference to people's lives. Market growth is guaranteed by demographics. Regulation and requirements for good manufacturing practice-extreme levels of repeatability and reliability-demand high-precision process and measurement solutions. Emerging technologies using living biological materials add complexity. This paper presents some results of work demonstrating the precision automated manufacture of living materials, particularly the expansion of populations of human stem cells for therapeutic use as regenerative medicines. The paper also describes quality engineering techniques for precision process design and improvement, and identifies the requirements for manufacturing technology and measurement systems evolution for such therapies.

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

  3. Reverse engineering physical models employing a sensor integration between 3D stereo detection and contact digitization

    NASA Astrophysics Data System (ADS)

    Chen, Liang-Chia; Lin, Grier C. I.

    1997-12-01

    A vision-drive automatic digitization process for free-form surface reconstruction has been developed, with a coordinate measurement machine (CMM) equipped with a touch-triggered probe and a CCD camera, in reverse engineering physical models. The process integrates 3D stereo detection, data filtering, Delaunay triangulation, adaptive surface digitization into a single process of surface reconstruction. By using this innovative approach, surface reconstruction can be implemented automatically and accurately. Least-squares B- spline surface models with the controlled accuracy of digitization can be generated for further application in product design and manufacturing processes. One industrial application indicates that this approach is feasible, and the processing time required in reverse engineering process can be significantly reduced up to more than 85%.

  4. Vascularization strategies for tissue engineers.

    PubMed

    Dew, Lindsey; MacNeil, Sheila; Chong, Chuh Khiun

    2015-01-01

    All tissue-engineered substitutes (with the exception of cornea and cartilage) require a vascular network to provide the nutrient and oxygen supply needed for their survival in vivo. Unfortunately the process of vascular ingrowth into an engineered tissue can take weeks to occur naturally and during this time the tissues become starved of essential nutrients, leading to tissue death. This review initially gives a brief overview of the processes and factors involved in the formation of new vasculature. It then summarizes the different approaches that are being applied or developed to overcome the issue of slow neovascularization in a range of tissue-engineered substitutes. Some potential future strategies are then discussed.

  5. Delta Clipper vehicle design for supportability

    NASA Astrophysics Data System (ADS)

    Smiljanic, Ray R.; Klevatt, Paul L.; Steinmeyer, Donald A.

    1993-02-01

    The paper describes the Single Stage Rocket Technology (SSRT) Delta Clipper vehicle design. As a means of reducing vehicle processing and turnaround times, the SSRT Delta Clipper design, contrary to past practices, incorporates support ability engineering features into its initial set of design requirements. The engineering process used to 'design-in' supportability into the Delta Clipper vehicle is described in detail and is illustrated using diagrams.

  6. Computerized systems analysis and optimization of aircraft engine performance, weight, and life cycle costs

    NASA Technical Reports Server (NTRS)

    Fishbach, L. H.

    1979-01-01

    The paper describes the computational techniques employed in determining the optimal propulsion systems for future aircraft applications and to identify system tradeoffs and technology requirements. The computer programs used to perform calculations for all the factors that enter into the selection process of determining the optimum combinations of airplanes and engines are examined. Attention is given to the description of the computer codes including NNEP, WATE, LIFCYC, INSTAL, and POD DRG. A process is illustrated by which turbine engines can be evaluated as to fuel consumption, engine weight, cost and installation effects. Examples are shown as to the benefits of variable geometry and of the tradeoff between fuel burned and engine weights. Future plans for further improvements in the analytical modeling of engine systems are also described.

  7. TRACER - TRACING AND CONTROL OF ENGINEERING REQUIREMENTS

    NASA Technical Reports Server (NTRS)

    Turner, P. R.

    1994-01-01

    TRACER (Tracing and Control of Engineering Requirements) is a database/word processing system created to document and maintain the order of both requirements and descriptive material associated with an engineering project. A set of hierarchical documents are normally generated for a project whereby the requirements of the higher level documents levy requirements on the same level or lower level documents. Traditionally, the requirements are handled almost entirely by manual paper methods. The problem with a typical paper system, however, is that requirements written and changed continuously in different areas lead to misunderstandings and noncompliance. The purpose of TRACER is to automate the capture, tracing, reviewing, and managing of requirements for an engineering project. The engineering project still requires communications, negotiations, interactions, and iterations among people and organizations, but TRACER promotes succinct and precise identification and treatment of real requirements separate from the descriptive prose in a document. TRACER permits the documentation of an engineering project's requirements and progress in a logical, controllable, traceable manner. TRACER's attributes include the presentation of current requirements and status from any linked computer terminal and the ability to differentiate headers and descriptive material from the requirements. Related requirements can be linked and traced. The program also enables portions of documents to be printed, individual approval and release of requirements, and the tracing of requirements down into the equipment specification. Requirement "links" can be made "pending" and invisible to others until the pending link is made "binding". Individuals affected by linked requirements can be notified of significant changes with acknowledgement of the changes required. An unlimited number of documents can be created for a project and an ASCII import feature permits existing documents to be incorporated. TRACER can automatically renumber section headers when inserting or deleting sections of a document and generate sign-off forms for any approval process as well as a table of contents. TRACER was implemented on an IBM PC under PC-DOS. The program requires 640K RAM, a hard disk, and PC-DOS version 3.3 or higher. It was written in CLIPPER (Summer '87). TRACER is available on two 5.25 inch 1.2Mb MS-DOS format diskettes. The executable program is also provided with the distribution. TRACER is a copyrighted work with all copyright vested in the National Aeronautics and Space Administration. IBM PC and PC-DOS are registered trademarks of International Business Machines. CLIPPER is a trademark of Nantucket Corporation.

  8. Auxiliary engine digital interface unit (DIU)

    NASA Technical Reports Server (NTRS)

    1972-01-01

    This auxiliary propulsion engine digital unit controls both the valving of the fuel and oxidizer to the engine combustion chamber and the ignition spark required for timely and efficient engine burns. In addition to this basic function, the unit is designed to manage it's own redundancy such that it is still operational after two hard circuit failures. It communicates to the data bus system several selected information points relating to the operational status of the electronics as well as the engine fuel and burning processes.

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

  10. Product Lifecycle Management and the Quest for Sustainable Space Exploration Solutions

    NASA Technical Reports Server (NTRS)

    Caruso, Pamela W.; Dumbacher, Daniel L.; Grieves, Michael

    2011-01-01

    Product Lifecycle Management (PLM) is an outcome of lean thinking to eliminate waste and increase productivity. PLM is inextricably tied to the systems engineering business philosophy, coupled with a methodology by which personnel, processes and practices, and information technology combine to form an architecture platform for product design, development, manufacturing, operations, and decommissioning. In this model, which is being implemented by the Marshall Space Flight Center (MSFC) Engineering Directorate, total lifecycle costs are important variables for critical decision-making. With the ultimate goal to deliver quality products that meet or exceed requirements on time and within budget, PLM is a powerful concept to shape everything from engineering trade studies and testing goals, to integrated vehicle operations and retirement scenarios. This briefing will demonstrate how the MSFC Engineering Directorate is implementing PLM as part of an overall strategy to deliver safe, reliable, and affordable space exploration solutions and how that strategy aligns with the Agency and Center systems engineering policies and processes. Sustainable space exploration solutions demand that all lifecycle phases be optimized, and engineering the next generation space transportation system requires a paradigm shift such that digital tools and knowledge management, which are central elements of PLM, are used consistently to maximum effect. Adopting PLM, which has been used by the aerospace and automotive industry for many years, for spacecraft applications provides a foundation for strong, disciplined systems engineering and accountable return on investment. PLM enables better solutions using fewer resources by making lifecycle considerations in an integrative decision-making process.

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

  12. Product Lifecycle Management and the Quest for Sustainable Space Explorations

    NASA Technical Reports Server (NTRS)

    Caruso, Pamela W.; Dumbacher, Daniel L.

    2010-01-01

    Product Lifecycle Management (PLM) is an outcome of lean thinking to eliminate waste and increase productivity. PLM is inextricably tied to the systems engineering business philosophy, coupled with a methodology by which personnel, processes and practices, and information technology combine to form an architecture platform for product design, development, manufacturing, operations, and decommissioning. In this model, which is being implemented by the Engineering Directorate at the National Aeronautics and Space Administration's (NASA's) Marshall Space Flight Center, total lifecycle costs are important variables for critical decision-making. With the ultimate goal to deliver quality products that meet or exceed requirements on time and within budget, PLM is a powerful concept to shape everything from engineering trade studies and testing goals, to integrated vehicle operations and retirement scenarios. This paper will demonstrate how the Engineering Directorate is implementing PLM as part of an overall strategy to deliver safe, reliable, and affordable space exploration solutions. It has been 30 years since the United States fielded the Space Shuttle. The next generation space transportation system requires a paradigm shift such that digital tools and knowledge management, which are central elements of PLM, are used consistently to maximum effect. The outcome is a better use of scarce resources, along with more focus on stakeholder and customer requirements, as a new portfolio of enabling tools becomes second nature to the workforce. This paper will use the design and manufacturing processes, which have transitioned to digital-based activities, to show how PLM supports the comprehensive systems engineering and integration function. It also will go through a launch countdown scenario where an anomaly is detected to show how the virtual vehicle created from paperless processes will help solve technical challenges and improve the likelihood of launching on schedule, with less hands-on labor needed for processing and troubleshooting.

  13. Engineering the Future: Cell 6

    NASA Technical Reports Server (NTRS)

    Stahl, P. H.

    2010-01-01

    This slide presentation reviews the development of the James Webb Space Telescope (JWST), explaining the development using a systems engineering methodology. Included are slides showing the organizational chart, the JWST Science Goals, the size of the primary mirror, and full scale mockups of the JSWT. Also included is a review of the JWST Optical Telescope Requirements, a review of the preliminary design and analysis, the technology development required to create the JWST, with particular interest in the specific mirror technology that was required, and views of the mirror manufacturing process. Several slides review the process of verification and validation by testing and analysis, including a diagram of the Cryogenic Test Facility at Marshall, and views of the primary mirror while being tested in the cryogenic facility.

  14. Current Challenges for HTCMC Aero-Propulsion Components

    NASA Technical Reports Server (NTRS)

    DiCarlo, James A.; Bansal, Narottam P.

    2007-01-01

    In comparison to the best metallic materials, HTCMC aero-propulsion engine components offer the opportunity of reduced weight and higher temperature operation, with corresponding improvements in engine cooling requirements, emissions, thrust, and specific fuel consumption. Although much progress has been made in the development of advanced HTCMC constituent materials and processes, major challenges still remain for their implementation into these components. The objectives of this presentation are to briefly review (1) potential HTCMC aero-propulsion components and their generic material performance requirements, (2) recent progress at NASA and elsewhere concerning advanced constituents and processes for meeting these requirements, (3) key HTCMC component implementation challenges that are currently being encountered, and (4) on-going activities within the new NASA Fundamental Aeronautics Program that are addressing these challenges.

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

  16. Project Interface Requirements Process Including Shuttle Lessons Learned

    NASA Technical Reports Server (NTRS)

    Bauch, Garland T.

    2010-01-01

    Most failures occur at interfaces between organizations and hardware. Processing interface requirements at the start of a project life cycle will reduce the likelihood of costly interface changes/failures later. This can be done by adding Interface Control Documents (ICDs) to the Project top level drawing tree, providing technical direction to the Projects for interface requirements, and by funding the interface requirements function directly from the Project Manager's office. The interface requirements function within the Project Systems Engineering and Integration (SE&I) Office would work in-line with the project element design engineers early in the life cycle to enhance communications and negotiate technical issues between the elements. This function would work as the technical arm of the Project Manager to help ensure that the Project cost, schedule, and risk objectives can be met during the Life Cycle. Some ICD Lessons Learned during the Space Shuttle Program (SSP) Life Cycle will include the use of hardware interface photos in the ICD, progressive life cycle design certification by analysis, test, & operations experience, assigning interface design engineers to Element Interface (EI) and Project technical panels, and linking interface design drawings with project build drawings

  17. Defining Medical Capabilities for Exploration Missions

    NASA Technical Reports Server (NTRS)

    Hailey, M.; Antonsen, E.; Blue, R.; Reyes, D.; Mulcahy, R.; Kerstman, E.; Bayuse, T.

    2018-01-01

    Exploration-class missions to the moon, Mars and beyond will require a significant change in medical capability from today's low earth orbit centric paradigm. Significant increases in autonomy will be required due to differences in duration, distance and orbital mechanics. Aerospace medicine and systems engineering teams are working together within ExMC to meet these challenges. Identifying exploration medical system needs requires accounting for planned and unplanned medical care as defined in the concept of operations. In 2017, the ExMC Clinicians group identified medical capabilities to feed into the Systems Engineering process, including: determining what and how to address planned and preventive medical care; defining an Accepted Medical Condition List (AMCL) of conditions that may occur and a subset of those that can be treated effectively within the exploration environment; and listing the medical capabilities needed to treat those conditions in the AMCL. This presentation will discuss the team's approach to addressing these issues, as well as how the outputs of the clinical process impact the systems engineering effort.

  18. Influence of Thrust Level on the Architecture and Optimal Working Process Parameters of a Small-scale Turbojet for UAV

    NASA Astrophysics Data System (ADS)

    Kuz`michev, V. S.; Filinov, E. P.; Ostapyuk, Ya A.

    2018-01-01

    This article describes how the thrust level influences the turbojet architecture (types of turbomachines that provide the maximum efficiency) and its working process parameters (turbine inlet temperature (TIT) and overall pressure ratio (OPR)). Functional gasdynamic and strength constraints were included, total mass of fuel and the engine required for mission and the specific fuel consumption (SFC) were considered optimization criteria. Radial and axial turbines and compressors were considered. The results show that as the engine thrust decreases, optimal values of working process parameters decrease too, and the regions of compromise shrink. Optimal engine architecture and values of working process parameters are suggested for turbojets with thrust varying from 100N to 100kN. The results show that for the thrust below 25kN the engine scale factor should be taken into the account, as the low flow rates begin to influence the efficiency of engine elements substantially.

  19. Progress toward an optimized hydrogen series hybrid engine

    NASA Astrophysics Data System (ADS)

    Smith, J. Ray; Aceves, Salvador M.; Johnson, Norman L.; Amsden, Anthony A.

    1995-06-01

    The design considerations and computational fluid dynamics (CFD) modeling of a high efficiency, low emissions, hydrogen-fueled engine for use as the prime mover of a series hybrid automobile is described. The series hybrid automobile uses the engine to generate electrical energy via a lightweight generator, the electrical energy is stored in a power peaking device (like a flywheel or ultracapacitor) and used as required to meet the tractive drive requirements (plus accessory loads) through an electrical motor. The engine/generator is stopped whenever the energy storage device is fully charged. Engine power output required was determined with a vehicle simulation code to be 15 to 20 kW steady state with peak output of 40 to 45 kW for hill climb. Combustion chamber and engine geometry were determined from a critical review of the hydrogen engine experiments in the literature combined with a simplified global engine model. Two different engine models are employed to guide engine design. The models are a simplified global engine performance model that relies strongly on correlations with literature data for heat transfer and friction losses, and a state-of-the-art CFD combustion model, KIVA-3, to elucidate fluid mechanics and combustion details through full three-dimensional modeling. Both intake and exhaust processes as well as hydrogen combustion chemistry and thermal NO(sub x) production are simulated. Ultimately, a comparison between the simulation and experimental results will lead to improved modeling and will give guidance to changes required in the next generation engine to achieve the goal of 45% brake thermal efficiency.

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

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

  2. Space flight requirements for fiber optic components: qualification testing and lessons learned

    NASA Astrophysics Data System (ADS)

    Ott, Melanie N.; Jin, Xiaodan Linda; Chuska, Richard; Friedberg, Patricia; Malenab, Mary; Matuszeski, Adam

    2006-04-01

    "Qualification" of fiber optic components holds a very different meaning than it did ten years ago. In the past, qualification meant extensive prolonged testing and screening that led to a programmatic method of reliability assurance. For space flight programs today, the combination of using higher performance commercial technology, with shorter development schedules and tighter mission budgets makes long term testing and reliability characterization unfeasible. In many cases space flight missions will be using technology within years of its development and an example of this is fiber laser technology. Although the technology itself is not a new product the components that comprise a fiber laser system change frequently as processes and packaging changes occur. Once a process or the materials for manufacturing a component change, even the data that existed on its predecessor can no longer provide assurance on the newer version. In order to assure reliability during a space flight mission, the component engineer must understand the requirements of the space flight environment as well as the physics of failure of the components themselves. This can be incorporated into an efficient and effective testing plan that "qualifies" a component to specific criteria defined by the program given the mission requirements and the component limitations. This requires interaction at the very initial stages of design between the system design engineer, mechanical engineer, subsystem engineer and the component hardware engineer. Although this is the desired interaction what typically occurs is that the subsystem engineer asks the components or development engineers to meet difficult requirements without knowledge of the current industry situation or the lack of qualification data. This is then passed on to the vendor who can provide little help with such a harsh set of requirements due to high cost of testing for space flight environments. This presentation is designed to guide the engineers of design, development and components, and vendors of commercial components with how to make an efficient and effective qualification test plan with some basic generic information about many space flight requirements. Issues related to the physics of failure, acceptance criteria and lessons learned will also be discussed to assist with understanding how to approach a space flight mission in an ever changing commercial photonics industry.

  3. Space Flight Requirements for Fiber Optic Components; Qualification Testing and Lessons Learned

    NASA Technical Reports Server (NTRS)

    Ott, Melanie N.; Jin, Xiaodan Linda; Chuska, Richard; Friedberg, Patricia; Malenab, Mary; Matuszeski, Adam

    2007-01-01

    "Qualification" of fiber optic components holds a very different meaning than it did ten years ago. In the past, qualification meant extensive prolonged testing and screening that led to a programmatic method of reliability assurance. For space flight programs today, the combination of using higher performance commercial technology, with shorter development schedules and tighter mission budgets makes long term testing and reliability characterization unfeasible. In many cases space flight missions will be using technology within years of its development and an example of this is fiber laser technology. Although the technology itself is not a new product the components that comprise a fiber laser system change frequently as processes and packaging changes occur. Once a process or the materials for manufacturing a component change, even the data that existed on its predecessor can no longer provide assurance on the newer version. In order to assure reliability during a space flight mission, the component engineer must understand the requirements of the space flight environment as well as the physics of failure of the components themselves. This can be incorporated into an efficient and effective testing plan that "qualifies" a component to specific criteria defined by the program given the mission requirements and the component limitations. This requires interaction at the very initial stages of design between the system design engineer, mechanical engineer, subsystem engineer and the component hardware engineer. Although this is the desired interaction what typically occurs is that the subsystem engineer asks the components or development engineers to meet difficult requirements without knowledge of the current industry situation or the lack of qualification data. This is then passed on to the vendor who can provide little help with such a harsh set of requirements due to high cost of testing for space flight environments. This presentation is designed to guide the engineers of design, development and components, and vendors of commercial components with how to make an efficient and effective qualification test plan with some basic generic information about many space flight requirements. Issues related to the physics of failure, acceptance criteria and lessons learned will also be discussed to assist with understanding how to approach a space flight mission in an ever changing commercial photonics industry.

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

  5. Update on Risk Reduction Activities for a Liquid Advanced Booster for NASA's Space Launch System

    NASA Technical Reports Server (NTRS)

    Crocker, Andrew M.; Greene, William D.

    2017-01-01

    The stated goals of NASA's Research Announcement for the Space Launch System (SLS) Advanced Booster Engineering Demonstration and/or Risk Reduction (ABEDRR) are to reduce risks leading to an affordable Advanced Booster that meets the evolved capabilities of SLS and enable competition by mitigating targeted Advanced Booster risks to enhance SLS affordability. Dynetics, Inc. and Aerojet Rocketdyne (AR) formed a team to offer a wide-ranging set of risk reduction activities and full-scale, system-level demonstrations that support NASA's ABEDRR goals. During the ABEDRR effort, the Dynetics Team has modified flight-proven Apollo-Saturn F-1 engine components and subsystems to improve affordability and reliability (e.g., reduce parts counts, touch labor, or use lower cost manufacturing processes and materials). The team has built hardware to validate production costs and completed tests to demonstrate it can meet performance requirements. State-of-the-art manufacturing and processing techniques have been applied to the heritage F-1, resulting in a low recurring cost engine while retaining the benefits of Apollo-era experience. NASA test facilities have been used to perform low-cost risk-reduction engine testing. In early 2014, NASA and the Dynetics Team agreed to move additional large liquid oxygen/kerosene engine work under Dynetics' ABEDRR contract. Also led by AR, the objectives of this work are to demonstrate combustion stability and measure performance of a 500,000 lbf class Oxidizer-Rich Staged Combustion (ORSC) cycle main injector. A trade study was completed to investigate the feasibility, cost effectiveness, and technical maturity of a domestically-produced engine that could potentially both replace the RD-180 on Atlas V and satisfy NASA SLS payload-to-orbit requirements via an advanced booster application. Engine physical dimensions and performance parameters resulting from this study provide the system level requirements for the ORSC risk reduction test article. The test article is scheduled to complete fabrication and assembly soon and continue testing through late 2019. Dynetics has also designed, developed, and built innovative tank and structure assemblies using friction stir welding to leverage recent NASA investments in manufacturing tools, facilities, and processes, significantly reducing development and recurring costs. The full-scale cryotank assembly was used to verify the structural design and prove affordable processes. Dynetics performed hydrostatic and cryothermal proof tests on the assembly to verify the assembly meets performance requirements..

  6. 10 CFR 35.51 - Training for an authorized medical physicist.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ... on the NRC's Web page.) To have its certification process recognized, a specialty board shall require... physics, other physical science, engineering, or applied mathematics from an accredited college or... physical science, engineering, or applied mathematics from an accredited college or university; and has...

  7. Framework Support For Knowledge-Based Software Development

    NASA Astrophysics Data System (ADS)

    Huseth, Steve

    1988-03-01

    The advent of personal engineering workstations has brought substantial information processing power to the individual programmer. Advanced tools and environment capabilities supporting the software lifecycle are just beginning to become generally available. However, many of these tools are addressing only part of the software development problem by focusing on rapid construction of self-contained programs by a small group of talented engineers. Additional capabilities are required to support the development of large programming systems where a high degree of coordination and communication is required among large numbers of software engineers, hardware engineers, and managers. A major player in realizing these capabilities is the framework supporting the software development environment. In this paper we discuss our research toward a Knowledge-Based Software Assistant (KBSA) framework. We propose the development of an advanced framework containing a distributed knowledge base that can support the data representation needs of tools, provide environmental support for the formalization and control of the software development process, and offer a highly interactive and consistent user interface.

  8. Biomaterials-based 3D cell printing for next-generation therapeutics and diagnostics.

    PubMed

    Jang, Jinah; Park, Ju Young; Gao, Ge; Cho, Dong-Woo

    2018-02-01

    Building human tissues via 3D cell printing technology has received particular attention due to its process flexibility and versatility. This technology enables the recapitulation of unique features of human tissues and the all-in-one manufacturing process through the design of smart and advanced biomaterials and proper polymerization techniques. For the optimal engineering of tissues, a higher-order assembly of physiological components, including cells, biomaterials, and biomolecules, should meet the critical requirements for tissue morphogenesis and vascularization. The convergence of 3D cell printing with a microfluidic approach has led to a significant leap in the vascularization of engineering tissues. In addition, recent cutting-edge technology in stem cells and genetic engineering can potentially be adapted to the 3D tissue fabrication technique, and it has great potential to shift the paradigm of disease modeling and the study of unknown disease mechanisms required for precision medicine. This review gives an overview of recent developments in 3D cell printing and bioinks and provides technical requirements for engineering human tissues. Finally, we propose suggestions on the development of next-generation therapeutics and diagnostics. Copyright © 2017 Elsevier Ltd. All rights reserved.

  9. E-ELT requirements flow down

    NASA Astrophysics Data System (ADS)

    Gonzalez, J. C.; Kurlandczyk, H.; Schmid, C.; Schneller, D.

    2016-08-01

    One of the critical activities in the systems engineering scope of work is managing requirements. In line with this, E-ELT devotes a significant effort to this activity, which follows a well-established process. This involves optimally deriving requirements from the user (Top-Level Requirements) through the system Level 1 Requirements and from here down to subsystems procurement specifications. This paper describes the process, which is illustrated with some practical examples, including in particular the role of technical budgets to derive requirements on subsystems. Also, the provisions taken for the requirements verification are discussed.

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

  11. Monsanto may bypass NIH in microbe test.

    PubMed

    Sun, Marjorie

    1985-01-11

    The Monsanto Company is planning to ask the Environmental Protection Agency for clearance to field test a genetically engineered microbial pesticide, bypassing the traditional approval process of the National Institutes of Health. Although only federally funded institutions are required to obtain NIH approval for genetic engineering tests, Monsanto is the first company to bypass the NIH regulatory process, which has become mired in a lawsuit brought by Jeremy Rifkin.

  12. Creative brains: designing in the real world†

    PubMed Central

    Goel, Vinod

    2014-01-01

    The process of designing artifacts is a creative activity. It is proposed that, at the cognitive level, one key to understanding design creativity is to understand the array of symbol systems designers utilize. These symbol systems range from being vague, imprecise, abstract, ambiguous, and indeterminate (like conceptual sketches), to being very precise, concrete, unambiguous, and determinate (like contract documents). The former types of symbol systems support associative processes that facilitate lateral (or divergent) transformations that broaden the problem space, while the latter types of symbol systems support inference processes facilitating vertical (or convergent) transformations that deepen of the problem space. The process of artifact design requires the judicious application of both lateral and vertical transformations. This leads to a dual mechanism model of design problem-solving comprising of an associative engine and an inference engine. It is further claimed that this dual mechanism model is supported by an interesting hemispheric dissociation in human prefrontal cortex. The associative engine and neural structures that support imprecise, ambiguous, abstract, indeterminate representations are lateralized in the right prefrontal cortex, while the inference engine and neural structures that support precise, unambiguous, determinant representations are lateralized in the left prefrontal cortex. At the brain level, successful design of artifacts requires a delicate balance between the two hemispheres of prefrontal cortex. PMID:24817846

  13. The Flow Engine Framework: A Cognitive Model of Optimal Human Experience

    PubMed Central

    Šimleša, Milija; Guegan, Jérôme; Blanchard, Edouard; Tarpin-Bernard, Franck; Buisine, Stéphanie

    2018-01-01

    Flow is a well-known concept in the fields of positive and applied psychology. Examination of a large body of flow literature suggests there is a need for a conceptual model rooted in a cognitive approach to explain how this psychological phenomenon works. In this paper, we propose the Flow Engine Framework, a theoretical model explaining dynamic interactions between rearranged flow components and fundamental cognitive processes. Using an IPO framework (Inputs – Processes – Outputs) including a feedback process, we organize flow characteristics into three logically related categories: inputs (requirements for flow), mediating and moderating cognitive processes (attentional and motivational mechanisms) and outputs (subjective and objective outcomes), describing the process of the flow. Comparing flow with an engine, inputs are depicted as flow-fuel, core processes cylinder strokes and outputs as power created to provide motion. PMID:29899807

  14. Process and apparatus for afterburning of combustible pollutants from an internal combustion engine

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

    Laurent, P.A.

    1978-07-04

    In a process for the afterburning of the combustible pollutants from an internal combustion engine, in order to automatically reduce the secondary induction rate when power increases without using a controlling valve actuatd by the carburetor venturi depression, there is provided a volumetric efficiency of the secondary air pump linked to and activated by the engine and a volumetric efficiency which decreases when the ratio between its back pressure and suction pressure increases, this reduction being achieved through the proper selection of the pump volumetric compression ratio r: between 0.6 c and 1.3 c when a steeply decreasing trend ismore » required, and above 1.3 c if a slower and slower decreasing trend is required. To perform this process an afterburner apparatus has a nitrogen oxide reducing catalyst placed inside the afterburner reactor on the gas stream immediately at the outlet of a torus, in which the gases are homogenized and their reaction with preinjection air is terminated.« less

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

  16. Status on the Verification of Combustion Stability for the J-2X Engine Thrust Chamber Assembly

    NASA Technical Reports Server (NTRS)

    Casiano, Matthew; Hinerman, Tim; Kenny, R. Jeremy; Hulka, Jim; Barnett, Greg; Dodd, Fred; Martin, Tom

    2013-01-01

    Development is underway of the J -2X engine, a liquid oxygen/liquid hydrogen rocket engine for use on the Space Launch System. The Engine E10001 began hot fire testing in June 2011 and testing will continue with subsequent engines. The J -2X engine main combustion chamber contains both acoustic cavities and baffles. These stability aids are intended to dampen the acoustics in the main combustion chamber. Verification of the engine thrust chamber stability is determined primarily by examining experimental data using a dynamic stability rating technique; however, additional requirements were included to guard against any spontaneous instability or rough combustion. Startup and shutdown chug oscillations are also characterized for this engine. This paper details the stability requirements and verification including low and high frequency dynamics, a discussion on sensor selection and sensor port dynamics, and the process developed to assess combustion stability. A status on the stability results is also provided and discussed.

  17. 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).

  18. Requirements engineering for cross-sectional information chain models

    PubMed Central

    Hübner, U; Cruel, E; Gök, M; Garthaus, M; Zimansky, M; Remmers, H; Rienhoff, O

    2012-01-01

    Despite the wealth of literature on requirements engineering, little is known about engineering very generic, innovative and emerging requirements, such as those for cross-sectional information chains. The IKM health project aims at building information chain reference models for the care of patients with chronic wounds, cancer-related pain and back pain. Our question therefore was how to appropriately capture information and process requirements that are both generally applicable and practically useful. To this end, we started with recommendations from clinical guidelines and put them up for discussion in Delphi surveys and expert interviews. Despite the heterogeneity we encountered in all three methods, it was possible to obtain requirements suitable for building reference models. We evaluated three modelling languages and then chose to write the models in UML (class and activity diagrams). On the basis of the current project results, the pros and cons of our approach are discussed. PMID:24199080

  19. Seven Processes that Enable NASA Software Engineering Technologies

    NASA Technical Reports Server (NTRS)

    Housch, Helen; Godfrey, Sally

    2011-01-01

    This slide presentation reviews seven processes that NASA uses to ensure that software is developed, acquired and maintained as specified in the NPR 7150.2A requirement. The requirement is to ensure that all software be appraised for the Capability Maturity Model Integration (CMMI). The enumerated processes are: (7) Product Integration, (6) Configuration Management, (5) Verification, (4) Software Assurance, (3) Measurement and Analysis, (2) Requirements Management and (1) Planning & Monitoring. Each of these is described and the group(s) that are responsible is described.

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

  1. 40 CFR 63.11498 - What are the standards and compliance requirements for wastewater systems?

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... Chemical Manufacturing Area Sources Standards and Compliance Requirements § 63.11498 What are the standards... each wastewater stream using process knowledge, engineering assessment, or test data. Also, you must...

  2. 40 CFR 63.11498 - What are the standards and compliance requirements for wastewater systems?

    Code of Federal Regulations, 2012 CFR

    2012-07-01

    ... Chemical Manufacturing Area Sources Standards and Compliance Requirements § 63.11498 What are the standards... each wastewater stream using process knowledge, engineering assessment, or test data. Also, you must...

  3. Biocatalysts: application and engineering for industrial purposes.

    PubMed

    Jemli, Sonia; Ayadi-Zouari, Dorra; Hlima, Hajer Ben; Bejar, Samir

    2016-01-01

    Enzymes are widely applied in various industrial applications and processes, including the food and beverage, animal feed, textile, detergent and medical industries. Enzymes screened from natural origins are often engineered before entering the market place because their native forms do not meet the requirements for industrial application. Protein engineering is concerned with the design and construction of novel enzymes with tailored functional properties, including stability, catalytic activity, reaction product inhibition and substrate specificity. Two broad approaches have been used for enzyme engineering, namely, rational design and directed evolution. The powerful and revolutionary techniques so far developed for protein engineering provide excellent opportunities for the design of industrial enzymes with specific properties and production of high-value products at lower production costs. The present review seeks to highlight the major fields of enzyme application and to provide an updated overview on previous protein engineering studies wherein natural enzymes were modified to meet the operational conditions required for industrial application.

  4. Role of strategic planning in engineering management

    NASA Technical Reports Server (NTRS)

    Krishen, Kumar

    1993-01-01

    Today, more than ever before, engineers are faced with uncertain and sometimes chaotic environments in which to function. The traditional roles of an engineer to design, develop, and streamline a manufacturing process for a product are still valued and relevant. However, the need for an engineer to participate in the process of identifying the product to be developed, the schedule and resources required, and the goal of satisfying the customer, has become paramount to achieving the success of the enterprise. When we include these endeavors in the functions of an engineer, management of 'engineering' takes on a new dimension. In this paper, the ramifications of the changing and increased functions of an engineer and consequent impacts on engineering management are explored. The basic principles which should be invoked in order to embrace the new environment for engineering management are outlined. The ultimate finding of this study is that the enterprise strategic plan should be developed in such a way as to allow engineering management to encompass the full spectrum of the responsibilities of engineers. A consequence of this is that the fundamental elements of the strategic process can best be implemented through a project team or group approach. The paper thus concentrates on three areas: evolving environment, strategic plan, and ways to achieve enterprise success.

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

  6. Design of the Curriculum for a Second-Cycle Course in Civil Engineering in the Context of the Bologna Framework

    ERIC Educational Resources Information Center

    Gavin, K. G.

    2010-01-01

    This paper describes the design of the curriculum for a Master of Engineering programme in civil engineering at University College Dublin. The revised programme was established to meet the requirements of the Bologna process and this paper specifically considers the design of a new, second-cycle master's component of the programme. In addition to…

  7. Implementation of Insight Responsibilities in Process Engineering

    NASA Technical Reports Server (NTRS)

    Osborne, Deborah M.

    1997-01-01

    This report describes an approach for evaluating flight readiness (COFR) and contractor performance evaluation (award fee) as part of the insight role of NASA Process Engineering at Kennedy Space Center. Several evaluation methods are presented, including systems engineering evaluations and use of systems performance data. The transition from an oversight function to the insight function is described. The types of analytical tools appropriate for achieving the flight readiness and contractor performance evaluation goals are described and examples are provided. Special emphasis is placed upon short and small run statistical quality control techniques. Training requirements for system engineers are delineated. The approach described herein would be equally appropriate in other directorates at Kennedy Space Center.

  8. Engineering evidence for carbon monoxide toxicity cases.

    PubMed

    Galatsis, Kosmas

    2016-07-01

    Unintentional carbon monoxide poisonings and fatalities lead to many toxicity cases. Given the unusual physical properties of carbon monoxide-in that the gas is odorless and invisible-unorganized and erroneous methods in obtaining engineering evidence as required during the discovery process often occurs. Such evidence gathering spans domains that include building construction, appliance installation, industrial hygiene, mechanical engineering, combustion and physics. In this paper, we attempt to place a systematic framework that is relevant to key aspects in engineering evidence gathering for unintentional carbon monoxide poisoning cases. Such a framework aims to increase awareness of this process and relevant issues to help guide legal counsel and expert witnesses. © The Author(s) 2015.

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

  10. Inertial Fusion Power Plant Concept of Operations and Maintenance

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

    Anklam, T.; Knutson, B.; Dunne, A. M.

    2015-01-15

    Parsons and LLNL scientists and engineers performed design and engineering work for power plant pre-conceptual designs based on the anticipated laser fusion demonstrations at the National Ignition Facility (NIF). Work included identifying concepts of operations and maintenance (O&M) and associated requirements relevant to fusion power plant systems analysis. A laser fusion power plant would incorporate a large process and power conversion facility with a laser system and fusion engine serving as the heat source, based in part on some of the systems and technologies advanced at NIF. Process operations would be similar in scope to those used in chemical, oilmore » refinery, and nuclear waste processing facilities, while power conversion operations would be similar to those used in commercial thermal power plants. While some aspects of the tritium fuel cycle can be based on existing technologies, many aspects of a laser fusion power plant presents several important and unique O&M requirements that demand new solutions. For example, onsite recovery of tritium; unique remote material handling systems for use in areas with high radiation, radioactive materials, or high temperatures; a five-year fusion engine target chamber replacement cycle with other annual and multi-year cycles anticipated for major maintenance of other systems, structures, and components (SSC); and unique SSC for fusion target waste recycling streams. This paper describes fusion power plant O&M concepts and requirements, how O&M requirements could be met in design, and how basic organizational and planning issues can be addressed for a safe, reliable, economic, and feasible fusion power plant.« less

  11. Inertial fusion power plant concept of operations and maintenance

    NASA Astrophysics Data System (ADS)

    Knutson, Brad; Dunne, Mike; Kasper, Jack; Sheehan, Timothy; Lang, Dwight; Anklam, Tom; Roberts, Valerie; Mau, Derek

    2015-02-01

    Parsons and LLNL scientists and engineers performed design and engineering work for power plant pre-conceptual designs based on the anticipated laser fusion demonstrations at the National Ignition Facility (NIF). Work included identifying concepts of operations and maintenance (O&M) and associated requirements relevant to fusion power plant systems analysis. A laser fusion power plant would incorporate a large process and power conversion facility with a laser system and fusion engine serving as the heat source, based in part on some of the systems and technologies advanced at NIF. Process operations would be similar in scope to those used in chemical, oil refinery, and nuclear waste processing facilities, while power conversion operations would be similar to those used in commercial thermal power plants. While some aspects of the tritium fuel cycle can be based on existing technologies, many aspects of a laser fusion power plant presents several important and unique O&M requirements that demand new solutions. For example, onsite recovery of tritium; unique remote material handling systems for use in areas with high radiation, radioactive materials, or high temperatures; a five-year fusion engine target chamber replacement cycle with other annual and multi-year cycles anticipated for major maintenance of other systems, structures, and components (SSC); and unique SSC for fusion target waste recycling streams. This paper describes fusion power plant O&M concepts and requirements, how O&M requirements could be met in design, and how basic organizational and planning issues can be addressed for a safe, reliable, economic, and feasible fusion power plant.

  12. 10 CFR 725.15 - Requirements for approval of applications.

    Code of Federal Regulations, 2011 CFR

    2011-01-01

    ... engaged in a substantial effort to develop, design, build or operate a chemical processing plant or other... (b)(2)(i) of this section, substantial scientific, engineering or other professional services to be... the paragraph (b)(3)(i) of this section substantial scientific, engineering, or other professional...

  13. A Study of Technical Engineering Peer Reviews at NASA

    NASA Technical Reports Server (NTRS)

    Chao, Lawrence P.; Tumer, Irem Y.; Bell, David G.

    2003-01-01

    This report describes the state of practices of design reviews at NASA and research into what can be done to improve peer review practices. There are many types of reviews at NASA: required and not, formalized and informal, programmatic and technical. Standing project formal reviews such as the Preliminary Design Review and Critical Design Review are a required part of every project and mission development. However, the technical, engineering peer reviews that support teams' work on such projects are informal, some times ad hoc, and inconsistent across the organization. The goal of this work is to identify best practices and lessons learned from NASA's experience, supported by academic research and methodologies to ultimately improve the process. This research has determined that the organization, composition, scope, and approach of the reviews impact their success. Failure Modes and Effects Analysis (FMEA) can identify key areas of concern before or in the reviews. Product definition tools like the Project Priority Matrix, engineering-focused Customer Value Chain Analysis (CVCA), and project or system-based Quality Function Deployment (QFD) help prioritize resources in reviews. The use of information technology and structured design methodologies can strengthen the engineering peer review process to help NASA work towards error-proofing the design process.

  14. A Co-modeling Method Based on Component Features for Mechatronic Devices in Aero-engines

    NASA Astrophysics Data System (ADS)

    Wang, Bin; Zhao, Haocen; Ye, Zhifeng

    2017-08-01

    Data-fused and user-friendly design of aero-engine accessories is required because of their structural complexity and stringent reliability. This paper gives an overview of a typical aero-engine control system and the development process of key mechatronic devices used. Several essential aspects of modeling and simulation in the process are investigated. Considering the limitations of a single theoretic model, feature-based co-modeling methodology is suggested to satisfy the design requirements and compensate for diversity of component sub-models for these devices. As an example, a stepper motor controlled Fuel Metering Unit (FMU) is modeled in view of the component physical features using two different software tools. An interface is suggested to integrate the single discipline models into the synthesized one. Performance simulation of this device using the co-model and parameter optimization for its key components are discussed. Comparison between delivery testing and the simulation shows that the co-model for the FMU has a high accuracy and the absolute superiority over a single model. Together with its compatible interface with the engine mathematical model, the feature-based co-modeling methodology is proven to be an effective technical measure in the development process of the device.

  15. A Matrix Approach to Software Process Definition

    NASA Technical Reports Server (NTRS)

    Schultz, David; Bachman, Judith; Landis, Linda; Stark, Mike; Godfrey, Sally; Morisio, Maurizio; Powers, Edward I. (Technical Monitor)

    2000-01-01

    The Software Engineering Laboratory (SEL) is currently engaged in a Methodology and Metrics program for the Information Systems Center (ISC) at Goddard Space Flight Center (GSFC). This paper addresses the Methodology portion of the program. The purpose of the Methodology effort is to assist a software team lead in selecting and tailoring a software development or maintenance process for a specific GSFC project. It is intended that this process will also be compliant with both ISO 9001 and the Software Engineering Institute's Capability Maturity Model (CMM). Under the Methodology program, we have defined four standard ISO-compliant software processes for the ISC, and three tailoring criteria that team leads can use to categorize their projects. The team lead would select a process and appropriate tailoring factors, from which a software process tailored to the specific project could be generated. Our objective in the Methodology program is to present software process information in a structured fashion, to make it easy for a team lead to characterize the type of software engineering to be performed, and to apply tailoring parameters to search for an appropriate software process description. This will enable the team lead to follow a proven, effective software process and also satisfy NASA's requirement for compliance with ISO 9001 and the anticipated requirement for CMM assessment. This work is also intended to support the deployment of sound software processes across the ISC.

  16. Dynamic Systems Analysis for Turbine Based Aero Propulsion Systems

    NASA Technical Reports Server (NTRS)

    Csank, Jeffrey T.

    2016-01-01

    The aircraft engine design process seeks to optimize the overall system-level performance, weight, and cost for a given concept. Steady-state simulations and data are used to identify trade-offs that should be balanced to optimize the system in a process known as systems analysis. These systems analysis simulations and data may not adequately capture the true performance trade-offs that exist during transient operation. Dynamic systems analysis provides the capability for assessing the dynamic tradeoffs at an earlier stage of the engine design process. The dynamic systems analysis concept, developed tools, and potential benefit are presented in this paper. To provide this capability, the Tool for Turbine Engine Closed-loop Transient Analysis (TTECTrA) was developed to provide the user with an estimate of the closed-loop performance (response time) and operability (high pressure compressor surge margin) for a given engine design and set of control design requirements. TTECTrA along with engine deterioration information, can be used to develop a more generic relationship between performance and operability that can impact the engine design constraints and potentially lead to a more efficient engine.

  17. Issues in nanocomposite ceramic engineering: focus on processing and properties of alumina-based composites.

    PubMed

    Palmero, Paola; Kern, Frank; Sommer, Frank; Lombardi, Mariangela; Gadow, Rainer; Montanaro, Laura

    2014-12-30

    Ceramic nanocomposites, containing at least one phase in the nanometric dimension, have received special interest in recent years. They have, in fact, demonstrated increased performance, reliability and lifetime with respect to monolithic ceramics. However, a successful approach to the production of tailored composite nanostructures requires the development of innovative concepts at each step of manufacturing, from the synthesis of composite nanopowders, to their processing and sintering.This review aims to deepen understanding of some of the critical issues associated with the manufacturing of nanocomposite ceramics, focusing on alumina-based composite systems. Two case studies are presented and briefly discussed. The former illustrates the benefits, in terms of sintered microstructure and related mechanical properties, resulting from the application of an engineering approach to a laboratory-scale protocol for the elaboration of nanocomposites in the system alumina-ZrO2-YAG (yttrium aluminium garnet). The latter illustrates the manufacturing of alumina-based composites for large-scale applications such as cutting tools, carried out by an injection molding process. The need for an engineering approach to be applied in all processing steps is demonstrated also in this second case study, where a tailored manufacturing process is required to obtain the desired results.

  18. A knowledge-based approach to configuration layout, justification, and documentation

    NASA Technical Reports Server (NTRS)

    Craig, F. G.; Cutts, D. E.; Fennel, T. R.; Case, C.; Palmer, J. R.

    1990-01-01

    The design, development, and implementation is described of a prototype expert system which could aid designers and system engineers in the placement of racks aboard modules on Space Station Freedom. This type of problem is relevant to any program with multiple constraints and requirements demanding solutions which minimize usage of limited resources. This process is generally performed by a single, highly experienced engineer who integrates all the diverse mission requirements and limitations, and develops an overall technical solution which meets program and system requirements with minimal cost, weight, volume, power, etc. This system architect performs an intellectual integration process in which the underlying design rationale is often not fully documented. This is a situation which lends itself to an expert system solution for enhanced consistency, thoroughness, documentation, and change assessment capabilities.

  19. A Knowledge-Based Approach to Configuration Layout, Justification, and Documentation

    NASA Technical Reports Server (NTRS)

    Craig, F. G.; Cutts, D. E.; Fennel, T. R.; Case, C. M.; Palmer, J. R.

    1991-01-01

    The design, development, and implementation of a prototype expert system which could aid designers and system engineers in the placement of racks aboard modules on the Space Station Freedom are described. This type of problem is relevant to any program with multiple constraints and requirements demanding solutions which minimize usage of limited resources. This process is generally performed by a single, highly experienced engineer who integrates all the diverse mission requirements and limitations, and develops an overall technical solution which meets program and system requirements with minimal cost, weight, volume, power, etc. This system architect performs an intellectual integration process in which the underlying design rationale is often not fully documented. This is a situation which lends itself to an expert system solution for enhanced consistency, thoroughness, documentation, and change assessment capabilities.

  20. Stochastic processes, estimation theory and image enhancement

    NASA Technical Reports Server (NTRS)

    Assefi, T.

    1978-01-01

    An introductory account of stochastic processes, estimation theory, and image enhancement is presented. The book is primarily intended for first-year graduate students and practicing engineers and scientists whose work requires an acquaintance with the theory. Fundamental concepts of probability were reviewed that are required to support the main topics. The appendices discuss the remaining mathematical background.

  1. Capturing security requirements for software systems.

    PubMed

    El-Hadary, Hassan; El-Kassas, Sherif

    2014-07-01

    Security is often an afterthought during software development. Realizing security early, especially in the requirement phase, is important so that security problems can be tackled early enough before going further in the process and avoid rework. A more effective approach for security requirement engineering is needed to provide a more systematic way for eliciting adequate security requirements. This paper proposes a methodology for security requirement elicitation based on problem frames. The methodology aims at early integration of security with software development. The main goal of the methodology is to assist developers elicit adequate security requirements in a more systematic way during the requirement engineering process. A security catalog, based on the problem frames, is constructed in order to help identifying security requirements with the aid of previous security knowledge. Abuse frames are used to model threats while security problem frames are used to model security requirements. We have made use of evaluation criteria to evaluate the resulting security requirements concentrating on conflicts identification among requirements. We have shown that more complete security requirements can be elicited by such methodology in addition to the assistance offered to developers to elicit security requirements in a more systematic way.

  2. Capturing security requirements for software systems

    PubMed Central

    El-Hadary, Hassan; El-Kassas, Sherif

    2014-01-01

    Security is often an afterthought during software development. Realizing security early, especially in the requirement phase, is important so that security problems can be tackled early enough before going further in the process and avoid rework. A more effective approach for security requirement engineering is needed to provide a more systematic way for eliciting adequate security requirements. This paper proposes a methodology for security requirement elicitation based on problem frames. The methodology aims at early integration of security with software development. The main goal of the methodology is to assist developers elicit adequate security requirements in a more systematic way during the requirement engineering process. A security catalog, based on the problem frames, is constructed in order to help identifying security requirements with the aid of previous security knowledge. Abuse frames are used to model threats while security problem frames are used to model security requirements. We have made use of evaluation criteria to evaluate the resulting security requirements concentrating on conflicts identification among requirements. We have shown that more complete security requirements can be elicited by such methodology in addition to the assistance offered to developers to elicit security requirements in a more systematic way. PMID:25685514

  3. Patient Safety: The Role of Human Factors and Systems Engineering

    PubMed Central

    Carayon, Pascale; Wood, Kenneth E.

    2011-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. PMID:20543237

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

  5. Shuttle mission simulator requirement report, volume 2, revision A

    NASA Technical Reports Server (NTRS)

    Burke, J. F.

    1973-01-01

    The training requirements of all mission phases for crews and ground support personnel are presented. The specifications are given for the design and development of the simulator, data processing systems, engine control, software, and systems integration.

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

  7. A general engineering scenario for concurrent engineering environments

    NASA Astrophysics Data System (ADS)

    Mucino, V. H.; Pavelic, V.

    The paper describes an engineering method scenario which categorizes the various activities and tasks into blocks seen as subjects which consume and produce data and information. These methods, tools, and associated utilities interact with other engineering tools by exchanging information in such a way that a relationship between customers and suppliers of engineering data is established clearly, while data exchange consistency is maintained throughout the design process. The events and data transactions are presented in the form of flowcharts in which data transactions represent the connection between the various bricks, which in turn represent the engineering activities developed for the particular task required in the concurrent engineering environment.

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

  9. Understanding One Institutions' Process in Preparing Civil Engineering Students to Be Globally Competent

    ERIC Educational Resources Information Center

    Mavroudhis, Vasiliki Goudanas

    2017-01-01

    Civil engineering is an increasingly dynamic and global industry experiencing expansion cross borders, resulting in new required competencies sought out by employers and reflected in updated undergraduate program outcomes. These new competencies include attributes that result in global competence. Institutions of higher learning need to…

  10. Using a Didactic Manipulator in Mechatronics and Industrial Engineering Courses

    ERIC Educational Resources Information Center

    Stankovski, Stevan; Tarjan, Laslo; Skrinjar, Dragana; Ostojic, Gordana; Senk, Ivana

    2010-01-01

    One of the most difficult and most important engineering tasks is the integration of a robot-manipulator into material handling, assembly, and production processes, offering the possibility of supervision and control. The knowledge and skills required for these kinds of tasks are purely mechatronic and, thus, multidisciplinary. This paper…

  11. High School Student Information Access and Engineering Design Performance

    ERIC Educational Resources Information Center

    Mentzer, Nathan

    2014-01-01

    Developing solutions to engineering design problems requires access to information. Research has shown that appropriately accessing and using information in the design process improves solution quality. This quasi-experimental study provides two groups of high school students with a design problem in a three hour design experience. One group has…

  12. Mathematical modeling and characteristic analysis for over-under turbine based combined cycle engine

    NASA Astrophysics Data System (ADS)

    Ma, Jingxue; Chang, Juntao; Ma, Jicheng; Bao, Wen; Yu, Daren

    2018-07-01

    The turbine based combined cycle engine has become the most promising hypersonic airbreathing propulsion system for its superiority of ground self-starting, wide flight envelop and reusability. The simulation model of the turbine based combined cycle engine plays an important role in the research of performance analysis and control system design. In this paper, a turbine based combined cycle engine mathematical model is built on the Simulink platform, including a dual-channel air intake system, a turbojet engine and a ramjet. It should be noted that the model of the air intake system is built based on computational fluid dynamics calculation, which provides valuable raw data for modeling of the turbine based combined cycle engine. The aerodynamic characteristics of turbine based combined cycle engine in turbojet mode, ramjet mode and mode transition process are studied by the mathematical model, and the influence of dominant variables on performance and safety of the turbine based combined cycle engine is analyzed. According to the stability requirement of thrust output and the safety in the working process of turbine based combined cycle engine, a control law is proposed that could guarantee the steady output of thrust by controlling the control variables of the turbine based combined cycle engine in the whole working process.

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

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

  15. Future fundamental combustion research for aeropropulsion systems

    NASA Technical Reports Server (NTRS)

    Mularz, E. J.

    1985-01-01

    Physical fluid mechanics, heat transfer, and chemical kinetic processes which occur in the combustion chamber of aeropropulsion systems were investigated. With the component requirements becoming more severe for future engines, the current design methodology needs the new tools to obtain the optimum configuration in a reasonable design and development cycle. Research efforts in the last few years were encouraging but to achieve these benefits research is required into the fundamental aerothermodynamic processes of combustion. It is recommended that research continues in the areas of flame stabilization, combustor aerodynamics, heat transfer, multiphase flow and atomization, turbulent reacting flows, and chemical kinetics. Associated with each of these engineering sciences is the need for research into computational methods to accurately describe and predict these complex physical processes. Research needs in each of these areas are highlighted.

  16. A Quality Management Evaluation of the Graduate Education Process for Ocean Engineers in the Civil Engineer Corps

    DTIC Science & Technology

    1993-12-01

    graduate education required for Ocean Facilities Program (OFP) officers in the Civil Engineer Corps (CEC) of the United States Navy. For the purpose...determined by distributing questionnaires to all officers in the OFP. Statistical analyses of numerical data and judgmental3 analysis of professional...45 B. Ocean Facility Program Officer Graduate Education Questionnaire ....... 47 C. Summary of Questionnaire Responses

  17. NASA Fastrac Engine Gas Generator Component Test Program and Results

    NASA Technical Reports Server (NTRS)

    Dennis, Henry J., Jr.; Sanders, T.

    2000-01-01

    Low cost access to space has been a long-time goal of the National Aeronautics and Space Administration (NASA). The Fastrac engine program was begun at NASA's Marshall Space Flight Center to develop a 60,000-pound (60K) thrust, liquid oxygen/hydrocarbon (LOX/RP), gas generator-cycle booster engine for a fraction of the cost of similar engines in existence. To achieve this goal, off-the-shelf components and readily available materials and processes would have to be used. This paper will present the Fastrac gas generator (GG) design and the component level hot-fire test program and results. The Fastrac GG is a simple, 4-piece design that uses well-defined materials and processes for fabrication. Thirty-seven component level hot-fire tests were conducted at MSFC's component test stand #116 (TS116) during 1997 and 1998. The GG was operated at all expected operating ranges of the Fastrac engine. Some minor design changes were required to successfully complete the test program as development issues arose during the testing. The test program data results and conclusions determined that the Fastrac GG design was well on the way to meeting the requirements of NASA's X-34 Pathfinder Program that chose the Fastrac engine as its main propulsion system.

  18. Advanced general aviation comparative engine/airframe integration study

    NASA Technical Reports Server (NTRS)

    Huggins, G. L.; Ellis, D. R.

    1981-01-01

    The NASA Advanced Aviation Comparative Engine/Airframe Integration Study was initiated to help determine which of four promising concepts for new general aviation engines for the 1990's should be considered for further research funding. The engine concepts included rotary, diesel, spark ignition, and turboprop powerplants; a conventional state-of-the-art piston engine was used as a baseline for the comparison. Computer simulations of the performance of single and twin engine pressurized aircraft designs were used to determine how the various characteristics of each engine interacted in the design process. Comparisons were made of how each engine performed relative to the others when integrated into an airframe and required to fly a transportation mission.

  19. A Study of Experience Credit for Professional Engineering Licensure

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

    Martin, M.A.

    2003-08-11

    Oak Ridge National Laboratory performed a study of experience credit for professional engineering licensure for the Department of Energy's Industrial Assessment Center (IAC) Program. One of the study's goals was to determine how state licensure boards grant experience credit for engineering licensure, particularly in regards to IAC experience and experience prior to graduation. Another goal involved passing IAC information to state licensure boards to allow the boards to become familiar with the program and determine if they would grant credit to IAC graduates. The National Council of Examiners for Engineers and Surveyors (NCEES) has adopted a document, the ''Model Law''.more » This document empowers states to create state engineering boards and oversee engineering licensure. The board can also interpret and adopt rules and regulations. The Model Law also gives a general ''process'' for engineering licensure, the ''Model Law Engineer''. The Model Law Engineer requires that an applicant for professional licensure, or professional engineering (PE) licensure, obtain a combination of formal education and professional experience and successfully complete the fundamentals of engineering (FE) and PE exams. The Model Law states that a PE applicant must obtain four years of ''acceptable'' engineering experience after graduation to be allowed to sit for the PE exam. Although the Model Law defines ''acceptable experience,'' it is somewhat open to interpretation, and state boards decide whether applicants have accumulated the necessary amount of experience. The Model Law also allows applicants one year of credit for postgraduate degrees as well as experience credit for teaching courses in engineering. The Model Law grants states the power to adopt and amend the bylaws and rules of the Model Law licensure process. It allows state boards the freedom to modify the experience requirements for professional licensure. This power has created variety in experience requirements, and licensure requirements can differ from state to state. Before this study began, six questions were developed to help document how state boards grant experience credit. Many of the questions were formulated to determine how states deal with teaching experience, postgraduate credit, experience prior to graduation, PE and FE waivers, and the licensure process in general. Data were collected from engineering licensure boards for each of the fifty states and the District of Columbia. Telephone interviews were the primary method of data collection, while email correspondence was also used to a lesser degree. Prior to contacting each board, the researchers attempted to review each state's licensure web site. Based on the data collected, several trends and patterns were identified. For example, there is a general trend away from offering credit for experience prior to graduation. The issue becomes a problem when a PE from one state attempts to gain a license in another state by comity or endorsement. Tennessee and Kansas have recently stopped offering this credit and Mississippi cautions applicants that it could be difficult to obtain licensure in other states.« less

  20. ISPE: A knowledge-based system for fluidization studies

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

    Reddy, S.

    1991-01-01

    Chemical engineers use mathematical simulators to design, model, optimize and refine various engineering plants/processes. This procedure requires the following steps: (1) preparation of an input data file according to the format required by the target simulator; (2) excecuting the simulation; and (3) analyzing the results of the simulation to determine if all specified goals'' are satisfied. If the goals are not met, the input data file must be modified and the simulation repeated. This multistep process is continued until satisfactory results are obtained. This research was undertaken to develop a knowledge based system, IPSE (Intelligent Process Simulation Environment), that canmore » enhance the productivity of chemical engineers/modelers by serving as an intelligent assistant to perform a variety tasks related to process simulation. ASPEN, a widely used simulator by the US Department of Energy (DOE) at Morgantown Energy Technology Center (METC) was selected as the target process simulator in the project. IPSE, written in the C language, was developed using a number of knowledge-based programming paradigms: object-oriented knowledge representation that uses inheritance and methods, rulebased inferencing (includes processing and propagation of probabilistic information) and data-driven programming using demons. It was implemented using the knowledge based environment LASER. The relationship of IPSE with the user, ASPEN, LASER and the C language is shown in Figure 1.« less

  1. Integrated Logistics Support approach: concept for the new big projects: E-ELT, SKA, CTA

    NASA Astrophysics Data System (ADS)

    Marchiori, G.; Rampini, F.; Formentin, F.

    2014-08-01

    The Integrated Logistic Support is a process supporting strategies and optimizing activities for a correct project management and system engineering development. From the design & engineering of complex technical systems, to the erection on site, acceptance and after-sales service, EIE GROUP covers all aspects of the Integrated Logistics Support (ILS) process that includes: costing process centered around the life cycle cost and Level of Repair Analyses; engineering process which influences the design via means of reliability, modularization, etc.; technical publishing process based on international specifications; ordering administration process for supply support. Through the ILS, EIE GROUP plans and directs the identification and development of logistics support and system requirements for its products, with the goal of creating systems that last longer and require less support, thereby reducing costs and increasing return on investments. ILS therefore, addresses these aspects of supportability not only during acquisition, but also throughout the operational life cycle of the system. The impact of the ILS is often measured in terms of metrics such as reliability, availability, maintainability and testability (RAMT), and System Safety (RAMS). Example of the criteria and approach adopted by EIE GROUP during the design, manufacturing and test of the ALMA European Antennas and during the design phase of the E-ELT telescope and Dome are presented.

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

  3. A Sociotechnical Framework for Governing Climate Engineering

    PubMed Central

    2015-01-01

    Proposed ways of governing climate engineering have most often been supported by narrowly framed and unreflexive appraisals and processes. This article explores the governance implications of a Deliberative Mapping project that, unlike other governance principles, have emerged from an extensive process of reflection and reflexivity. In turn, the project has made significant advances in addressing the current deficit of responsibly defined criteria for shaping governance propositions. Three such propositions argue that (1) reflexive foresight of the imagined futures in which climate engineering proposals might reside is required; (2) the performance and acceptance of climate engineering proposals should be decided in terms of robustness, not optimality; and (3) climate engineering proposals should be satisfactorily opened up before they can be considered legitimate objects of governance. Taken together, these propositions offer a sociotechnical framework not simply for governing climate engineering but for governing responses to climate change at large. PMID:26973363

  4. 1-G Human Factors for Optimal Processing and Operability of Ground Systems Up to CxP GOP PDR

    NASA Technical Reports Server (NTRS)

    Stambolian, Damon B.; Henderson, Gena; Miller, Darcy; Prevost, Gary; Tran, Donald; Barth, Tim

    2011-01-01

    This slide presentation reviews the development and use of a process and tool for developing these requirements and improve the design for ground operations. A Human Factors Engineering Analysis (HFEA) Tool was developed to create a dedicated subset of requirements from the FAA requirements for each subsystem. As an example the use of the human interface with an actuator motor is considered.

  5. NASA Supportability Engineering Implementation Utilizing DoD Practices and Processes

    NASA Technical Reports Server (NTRS)

    Smith, David A.; Smith, John V.

    2010-01-01

    The Ares I design and development program made the determination early in the System Design Review Phase to utilize DoD ILS and LSA approach for supportability engineering as an integral part of the system engineering process. This paper is to provide a review of the overall approach to design Ares-I with an emphasis on a more affordable, supportable, and sustainable launch vehicle. Discussions will include the requirements development, design influence, support concept alternatives, ILS and LSA planning, Logistics support analyses/trades performed, LSA tailoring for NASA Ares Program, support system infrastructure identification, ILS Design Review documentation, Working Group coordination, and overall ILS implementation. At the outset, the Ares I Project initiated the development of the Integrated Logistics Support Plan (ILSP) and a Logistics Support Analysis process to provide a path forward for the management of the Ares-I ILS program and supportability analysis activities. The ILSP provide the initial planning and coordination between the Ares-I Project Elements and Ground Operation Project. The LSA process provided a system engineering approach in the development of the Ares-I supportability requirements; influence the design for supportability and development of alternative support concepts that satisfies the program operability requirements. The LSA planning and analysis results are documented in the Logistics Support Analysis Report. This document was required during the Ares-I System Design Review (SDR) and Preliminary Design Review (PDR) review cycles. To help coordinate the LSA process across the Ares-I project and between programs, the LSA Report is updated and released quarterly. A System Requirement Analysis was performed to determine the supportability requirements and technical performance measurements (TPMs). Two working groups were established to provide support in the management and implement the Ares-I ILS program, the Integrated Logistics Support Working Group (ILSWG) and the Logistics Support Analysis Record Working Group (LSARWG). The Ares I ILSWG is established to assess the requirements and conduct, evaluate analyses and trade studies associated with acquisition logistic and supportability processes and to resolve Ares I integrated logistics and supportability issues. It established a strategic collaborative alliance for coordination of Logistics Support Analysis activates in support of the integrated Ares I vehicle design and development of logistics support infrastructure. A Joint Ares I - Orion LSAR Working Group was established to: 1) Guide the development of Ares-I and Orion LSAR data and serve as a model for future Constellation programs, 2) Develop rules and assumptions that will apply across the Constellation program with regards to the program's LSAR development, and 3) Maintain the Constellation LSAR Style Guide.

  6. Jupiter Europa Orbiter Architecture Definition Process

    NASA Technical Reports Server (NTRS)

    Rasmussen, Robert; Shishko, Robert

    2011-01-01

    The proposed Jupiter Europa Orbiter mission, planned for launch in 2020, is using a new architectural process and framework tool to drive its model-based systems engineering effort. The process focuses on getting the architecture right before writing requirements and developing a point design. A new architecture framework tool provides for the structured entry and retrieval of architecture artifacts based on an emerging architecture meta-model. This paper describes the relationships among these artifacts and how they are used in the systems engineering effort. Some early lessons learned are discussed.

  7. Adapting Rational Unified Process (RUP) approach in designing a secure e-Tendering model

    NASA Astrophysics Data System (ADS)

    Mohd, Haslina; Robie, Muhammad Afdhal Muhammad; Baharom, Fauziah; Darus, Norida Muhd; Saip, Mohamed Ali; Yasin, Azman

    2016-08-01

    e-Tendering is an electronic processing of the tender document via internet and allow tenderer to publish, communicate, access, receive and submit all tender related information and documentation via internet. This study aims to design the e-Tendering system using Rational Unified Process approach. RUP provides a disciplined approach on how to assign tasks and responsibilities within the software development process. RUP has four phases that can assist researchers to adjust the requirements of various projects with different scope, problem and the size of projects. RUP is characterized as a use case driven, architecture centered, iterative and incremental process model. However the scope of this study only focusing on Inception and Elaboration phases as step to develop the model and perform only three of nine workflows (business modeling, requirements, analysis and design). RUP has a strong focus on documents and the activities in the inception and elaboration phases mainly concern the creation of diagrams and writing of textual descriptions. The UML notation and the software program, Star UML are used to support the design of e-Tendering. The e-Tendering design based on the RUP approach can contribute to e-Tendering developers and researchers in e-Tendering domain. In addition, this study also shows that the RUP is one of the best system development methodology that can be used as one of the research methodology in Software Engineering domain related to secured design of any observed application. This methodology has been tested in various studies in certain domains, such as in Simulation-based Decision Support, Security Requirement Engineering, Business Modeling and Secure System Requirement, and so forth. As a conclusion, these studies showed that the RUP one of a good research methodology that can be adapted in any Software Engineering (SE) research domain that required a few artifacts to be generated such as use case modeling, misuse case modeling, activity diagram, and initial class diagram from a list of requirements as identified earlier by the SE researchers

  8. Systems engineering in practice: can rigour and creativity co-exist?

    NASA Astrophysics Data System (ADS)

    Schnetler, Hermine; Rees, Philip; Egan, Ian

    2006-06-01

    Systems engineering as a discipline has been established for many years, being utilised to good effect most notably, in the defence industry. Its introduction in a formalised way to the UK ATC is relatively recent. Although a good start has been made in embedding the process within the lifecycle model, much work is still required to refine the systems engineering elements to cope with the complex (internationally collaborative) business model, the need to nurture creativity in the design process and the translation into a highly challenging cost-driven technology domain. This paper explores the current status of systems engineering at the UK ATC, shows where further work is needed, and how improvements can be made to meet the challenges of next generation telescopes and instrumentation. It is shown why the discipline is necessary, especially given that projects often comprise diverse global teams (both small and large), and it indicates the pitfalls of a tendency in the early stages of a project to focus on solutions rather than robust requirements capture. Finally, despite the obvious value and yet often ill-understood rigours of system engineering, it is shown how innovation and creativity can be promoted rather than stifled.

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

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

  11. NTP comparison process

    NASA Technical Reports Server (NTRS)

    Corban, Robert

    1993-01-01

    The systems engineering process for the concept definition phase of the program involves requirements definition, system definition, and consistent concept definition. The requirements definition process involves obtaining a complete understanding of the system requirements based on customer needs, mission scenarios, and nuclear thermal propulsion (NTP) operating characteristics. A system functional analysis is performed to provide a comprehensive traceability and verification of top-level requirements down to detailed system specifications and provides significant insight into the measures of system effectiveness to be utilized in system evaluation. The second key element in the process is the definition of system concepts to meet the requirements. This part of the process involves engine system and reactor contractor teams to develop alternative NTP system concepts that can be evaluated against specific attributes, as well as a reference configuration against which to compare system benefits and merits. Quality function deployment (QFD), as an excellent tool within Total Quality Management (TQM) techniques, can provide the required structure and provide a link to the voice of the customer in establishing critical system qualities and their relationships. The third element of the process is the consistent performance comparison. The comparison process involves validating developed concept data and quantifying system merits through analysis, computer modeling, simulation, and rapid prototyping of the proposed high risk NTP subsystems. The maximum amount possible of quantitative data will be developed and/or validated to be utilized in the QFD evaluation matrix. If upon evaluation of a new concept or its associated subsystems determine to have substantial merit, those features will be incorporated into the reference configuration for subsequent system definition and comparison efforts.

  12. Model-Driven Useware Engineering

    NASA Astrophysics Data System (ADS)

    Meixner, Gerrit; Seissler, Marc; Breiner, Kai

    User-oriented hardware and software development relies on a systematic development process based on a comprehensive analysis focusing on the users' requirements and preferences. Such a development process calls for the integration of numerous disciplines, from psychology and ergonomics to computer sciences and mechanical engineering. Hence, a correspondingly interdisciplinary team must be equipped with suitable software tools to allow it to handle the complexity of a multimodal and multi-device user interface development approach. An abstract, model-based development approach seems to be adequate for handling this complexity. This approach comprises different levels of abstraction requiring adequate tool support. Thus, in this chapter, we present the current state of our model-based software tool chain. We introduce the use model as the core model of our model-based process, transformation processes, and a model-based architecture, and we present different software tools that provide support for creating and maintaining the models or performing the necessary model transformations.

  13. The Effect of Gravity on the Combustion Synthesis of Porous Biomaterials

    NASA Technical Reports Server (NTRS)

    Castillo, M.; Zhang, X.; Moore, J. J.; Schowengerdt, F. D.; Ayers, R. A.

    2003-01-01

    Production of highly porous composite materials by traditional materials processing is limited by difficult processing techniques. This work investigates the use of self propagating high temperature (combustion) synthesis (SHS) to create porous tricalcium phosphate (Ca3(PO4)2), TiB-Ti, and NiTi in low and microgravity. Combustion synthesis provides the ability to use set processing parameters to engineer the required porous structure suitable for bone repair or replacement. The processing parameters include green density, particle size, gasifying agents, composition, and gravity. The advantage of the TiB-Ti system is the high level of porosity achieved together with a modulus that can be controlled by both composition (TiB-Ti) and porosity. At the same time, NiTi exhibits shape memory properties. SHS of biomaterials allows the engineering of required porosity coupled with resorbtion properties and specific mechanical properties into the composite materials to allow for a better biomaterial.

  14. Implications of multiplane-multispeed balancing for future turbine engine design and cost

    NASA Technical Reports Server (NTRS)

    Badgley, R. H.

    1974-01-01

    This paper describes several alternative approaches, provided by multiplane-multispeed balancing, to traditional gas turbine engine manufacture and assembly procedures. These alternatives, which range from addition of trim-balancing at the end of the traditional assembly process to modular design of the rotating system for assembly and balancing external to the engine, require attention by the engine designer as an integral part of the design process. Since multiplane-multispeed balancing may be incorporated at one or more of several points during manufacture-assembly, its deliberate use is expected to provide significant cost and performance (reduced vibration) benefits. Moreover, its availability provides the designer with a firm base from which he may advance, with reasonable assurance of success, into the flexible rotor dynamic regime.

  15. Developing a new industrial engineering curriculum using a systems engineering approach

    NASA Astrophysics Data System (ADS)

    Buyurgan, Nebil; Kiassat, Corey

    2017-11-01

    This paper reports on the development of an engineering curriculum for a new industrial engineering programme at a medium-sized private university in the northeast United States. A systems engineering process has been followed to design and develop the new curriculum. Considering the programme curriculum as a system, first the stakeholders have been identified, and some preliminary analysis on their needs and requirements has been conducted. Following that, the phases of conceptual design, preliminary design, and detailed design have been pursued during which different levels of validation, assessment, and evaluation processes have been utilised. In addition, a curriculum assessment and continuous improvement process have been developed to assess the curriculum and the courses frequently. The resulting curriculum is flexible, allowing the pursuit of accelerated graduate programmes, a second major, various minor options, and study-abroad; relevant, tailored to the needs of industry partners in the vicinity; and practical, providing hands-on education, resulting in employment-ready graduates.

  16. Prospects of microbial cell factories developed through systems metabolic engineering.

    PubMed

    Gustavsson, Martin; Lee, Sang Yup

    2016-09-01

    While academic-level studies on metabolic engineering of microorganisms for production of chemicals and fuels are ever growing, a significantly lower number of such production processes have reached commercial-scale. In this work, we review the challenges associated with moving from laboratory-scale demonstration of microbial chemical or fuel production to actual commercialization, focusing on key requirements on the production organism that need to be considered during the metabolic engineering process. Metabolic engineering strategies should take into account techno-economic factors such as the choice of feedstock, the product yield, productivity and titre, and the cost effectiveness of midstream and downstream processes. Also, it is important to develop an industrial strain through metabolic engineering for pathway construction and flux optimization together with increasing tolerance to products and inhibitors present in the feedstock, and ensuring genetic stability and strain robustness under actual fermentation conditions. © 2016 The Authors. Microbial Biotechnology published by John Wiley & Sons Ltd and Society for Applied Microbiology.

  17. Product Lifecycle Management and the Quest for Sustainable Space Exploration Solutions

    NASA Technical Reports Server (NTRS)

    Caruso, Pamela W.; Dumbacher, Daniel L.

    2010-01-01

    Product Lifecycle Management (PLM) is an outcome of lean thinking to eliminate waste and increase productivity. PLM is inextricably tied to the systems engineering business philosophy, coupled with a methodology by which personnel, processes and practices, and information technology combine to form an architecture platform for product design, development, manufacturing, operations, and decommissioning. In this model, which is being implemented by the Engineering Directorate at the National Aeronautics and Space Administration's (NASA's) Marshall Space Flight Center, total lifecycle costs are important variables for critical decisionmaking. With the ultimate goal to deliver quality products that meet or exceed requirements on time and within budget, PLM is a powerful tool to shape everything from engineering trade studies and testing goals, to integrated vehicle operations and retirement scenarios. This paper will demonstrate how the Engineering Directorate is implementing PLM as part of an overall strategy to deliver safe, reliable, and affordable space exploration solutions. It has been 30 years since the United States fielded the Space Shuttle. The next generation space transportation system requires a paradigm shift such that digital tools and knowledge management, which are central elements of PLM, are used consistently to maximum effect. The outcome is a better use of scarce resources, along with more focus on stakeholder and customer requirements, as a new portfolio of enabling tools becomes second nature to the workforce. This paper will use the design and manufacturing processes, which have transitioned to digital-based activities, to show how PLM supports the comprehensive systems engineering and integration function. It also will go through a launch countdown scenario where an anomaly is detected to show how the virtual vehicle created from paperless processes will help solve technical challenges and improve the likelihood of launching on schedule, with less hands-on labor needed for processing and troubleshooting. Sustainable space exploration solutions demand that all lifecycle phases be optimized. Adopting PLM, which has been used by the automotive industry for many years, for aerospace applications provides a foundation for strong, disciplined systems engineering and accountable return on investment by making lifecycle considerations variables in an iterative decision-making process. This paper combines the perspectives of the founding father of PLM, along with the experience of Engineering leaders who are implementing these processes and practices real-time. As the nation moves from an industrial-based society to one where information is a valued commodity, future NASA programs and projects will benefit from the experience being gained today for the exploration missions of tomorrow.

  18. Creating Learning Environment Connecting Engineering Design and 3D Printing

    NASA Astrophysics Data System (ADS)

    Pikkarainen, Ari; Salminen, Antti; Piili, Heidi

    Engineering education in modern days require continuous development in didactics, pedagogics and used practical methods. 3D printing provides excellent opportunity to connect different engineering areas into practice and produce learning by doing applications. The 3D-printing technology used in this study is FDM (Fused deposition modeling). FDM is the most used 3D-printing technology by commercial numbers at the moment and the qualities of the technology makes it popular especially in academic environments. For achieving the best result possible, students will incorporate the principles of DFAM (Design for additive manufacturing) into their engineering design studies together with 3D printing. This paper presents a plan for creating learning environment for mechanical engineering students combining the aspects of engineering design, 3D-CAD learning and AM (additive manufacturing). As a result, process charts for carrying out the 3D printing process from technological point of view and design process for AM from engineering design point of view were created. These charts are used in engineering design education. The learning environment is developed to work also as a platform for Bachelor theses, work-training environment for students, prototyping service centre for cooperation partners and source of information for mechanical engineering education in Lapland University of Applied Sciences.

  19. BPELPower—A BPEL execution engine for geospatial web services

    NASA Astrophysics Data System (ADS)

    Yu, Genong (Eugene); Zhao, Peisheng; Di, Liping; Chen, Aijun; Deng, Meixia; Bai, Yuqi

    2012-10-01

    The Business Process Execution Language (BPEL) has become a popular choice for orchestrating and executing workflows in the Web environment. As one special kind of scientific workflow, geospatial Web processing workflows are data-intensive, deal with complex structures in data and geographic features, and execute automatically with limited human intervention. To enable the proper execution and coordination of geospatial workflows, a specially enhanced BPEL execution engine is required. BPELPower was designed, developed, and implemented as a generic BPEL execution engine with enhancements for executing geospatial workflows. The enhancements are especially in its capabilities in handling Geography Markup Language (GML) and standard geospatial Web services, such as the Web Processing Service (WPS) and the Web Feature Service (WFS). BPELPower has been used in several demonstrations over the decade. Two scenarios were discussed in detail to demonstrate the capabilities of BPELPower. That study showed a standard-compliant, Web-based approach for properly supporting geospatial processing, with the only enhancement at the implementation level. Pattern-based evaluation and performance improvement of the engine are discussed: BPELPower directly supports 22 workflow control patterns and 17 workflow data patterns. In the future, the engine will be enhanced with high performance parallel processing and broad Web paradigms.

  20. Analysis of the Magneto-Hydrodynamic (MHD) Energy Bypass Engine for High-Speed Air-Breathing Propulsion

    NASA Technical Reports Server (NTRS)

    Riggins, David W.

    2002-01-01

    The performance of the MHD energy bypass air-breathing engine for high-speed propulsion is analyzed in this investigation. This engine is a specific type of the general class of inverse cycle engines. In this paper, the general relationship between engine performance (specific impulse and specific thrust) and the overall total pressure ratio through an engine (from inlet plane to exit plane) is first developed and illustrated. Engines with large total pressure decreases, regardless of cause or source, are seen to have exponentially decreasing performance. The ideal inverse cycle engine (of which the MHD engine is a sub-set) is then demonstrated to have a significant total pressure decrease across the engine; this total pressure decrease is cycle-driven, degrades rapidly with energy bypass ratio, and is independent of any irreversibility. The ideal MHD engine (inverse cycle engine with no irreversibility other than that inherent in the MHD work interaction processes) is next examined and is seen to have an additional large total pressure decrease due to MHD-generated irreversibility in the decelerator and the accelerator. This irreversibility mainly occurs in the deceleration process. Both inherent total pressure losses (inverse cycle and MHD irreversibility) result in a significant narrowing of the performance capability of the MHD bypass engine. The fundamental characteristics of MHD flow acceleration and flow deceleration from the standpoint of irreversibility and second-law constraints are next examined in order to clarify issues regarding flow losses and parameter selection in the MM modules. Severe constraints are seen to exist in the decelerator in terms of allowable deceleration Mach numbers and volumetric (length) required for meaningful energy bypass (work interaction). Considerable difficulties are also encountered and discussed due to thermal/work choking phenomena associated with the deceleration process. Lastly, full engine simulations utilizing inlet shock systems, finite-rate chemistry, wall cooling with thermally balanced engine (fuel heat sink), fuel injection and mixing, friction, etc. are shown and discussed for both the MHD engine and the conventional scramjet. The MHD bypass engine has significantly lower performance in all categories across the Mach number range (8 to 12.2). The lower performance is attributed to the combined effects of 1) additional irreversibility and cooling requirements associated with the MHD components and 2) the total pressure decrease associated with the inverse cycle itself.

  1. Towards Integrated Pulse Detonation Propulsion and MHD Power

    NASA Technical Reports Server (NTRS)

    Litchford, Ron J.; Thompson, Bryan R.; Lineberry, John T.

    1999-01-01

    The interest in pulse detonation engines (PDE) arises primarily from the advantages that accrue from the significant combustion pressure rise that is developed in the detonation process. Conventional rocket engines, for example, must obtain all of their compression from the turbopumps, while the PDE provides additional compression in the combustor. Thus PDE's are expected to achieve higher I(sub sp) than conventional rocket engines and to require smaller turbopumps. The increase in I(sub sp) and the decrease in turbopump capacity must be traded off against each other. Additional advantages include the ability to vary thrust level by adjusting the firing rate rather than throttling the flow through injector elements. The common conclusion derived from these aggregated performance attributes is that PDEs should result in engines which are smaller, lower in cost, and lighter in weight than conventional engines. Unfortunately, the analysis of PDEs is highly complex due to their unsteady operation and non-ideal processes. Although the feasibility of the basic PDE concept has been proven in several experimental and theoretical efforts, the implied performance improvements have yet to be convincingly demonstrated. Also, there are certain developmental issues affecting the practical application of pulse detonation propulsion systems which are yet to be fully resolved. Practical detonation combustion engines, for example, require a repetitive cycle of charge induction, mixing, initiation/propagation of the detonation wave, and expulsion/scavenging of the combustion product gases. Clearly, the performance and power density of such a device depends upon the maximum rate at which this cycle can be successfully implemented. In addition, the electrical energy required for direct detonation initiation can be significant, and a means for direct electrical power production is needed to achieve self-sustained engine operation. This work addresses the technological issues associated with PDEs for integrated aerospace propulsion and MHD power. An effort is made to estimate the energy requirements for direct detonation initiation of potential fuel/oxidizer mixtures and to determine the electrical power requirements. This requirement is evaluated in terms of the possibility for MHD power generation using the combustion detonation wave. Small scale laboratory experiments were conducted using stoichiometric mixtures of acetylene and oxygen with an atomized spray of cesium hydroxide dissolved in alcohol as an ionization seed in the active MHD region. Time resolved thrust and MHD power generation measurements were performed. These results show that PDEs yield higher I(sub sp) levels than a comparable rocket engine and that MHD power generation is viable candidate for achieving self-excited engine operation.

  2. System Guidelines for EMC Safety-Critical Circuits: Design, Selection, and Margin Demonstration

    NASA Technical Reports Server (NTRS)

    Lawton, R. M.

    1996-01-01

    Demonstration of required safety margins on critical electrical/electronic circuits in large complex systems has become an implementation and cost problem. These margins are the difference between the activation level of the circuit and the electrical noise on the circuit in the actual operating environment. This document discusses the origin of the requirement and gives a detailed process flow for the identification of the system electromagnetic compatibility (EMC) critical circuit list. The process flow discusses the roles of engineering disciplines such as systems engineering, safety, and EMC. Design and analysis guidelines are provided to assist the designer in assuring the system design has a high probability of meeting the margin requirements. Examples of approaches used on actual programs (Skylab and Space Shuttle Solid Rocket Booster) are provided to show how variations of the approach can be used successfully.

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

  4. Data management for Computer-Aided Engineering (CAE)

    NASA Technical Reports Server (NTRS)

    Bryant, W. A.; Smith, M. R.

    1984-01-01

    Analysis of data flow through the design and manufacturing processes has established specific information management requirements and identified unique problems. The application of data management technology to the engineering/manufacturing environment addresses these problems. An overview of the IPAD prototype data base management system, representing a partial solution to these problems, is presented here.

  5. Skill Sets Required for Environmental Engineering and Where They Are Learned

    ERIC Educational Resources Information Center

    Reed, Kathaleen

    2010-01-01

    The purpose of this study was to investigate the knowledge, skills, abilities and traits environmental engineers need. Two questions were asked: what skills are considered important, and where are they learned? Dreyfus and Dreyfus' novice-to-expert model, which describes a progressive, five-step process of skill development that occurs over time…

  6. NERVA-Derived Nuclear Thermal Propulsion Dual Mode Operation

    NASA Astrophysics Data System (ADS)

    Zweig, Herbert R.; Hundal, Rolv

    1994-07-01

    Generation of electrical power using the nuclear heat source of a NERVA-derived nuclear thermal rocket engine is presented. A 111,200 N thrust engine defined in a study for NASA-LeRC in FY92 is the reference engine for a three-engine vehicle for which a 50 kWe capacity is required. Processes are described for energy extraction from the reactor and for converting the energy to electricity. The tie tubes which support the reactor fuel elements are the source of thermal energy. The study focuses on process systems using Stirling cycle energy conversion operating at 980 K and an alternate potassium-Rankine system operating at 1,140 K. Considerations are given of the effect of the power production on turbopump operation, ZrH moderator dissociation, creep strain in the tie tubes, hydrogen permeation through the containment materials, requirements for a backup battery system, and the effects of potential design changes on reactor size and criticality. Nuclear considerations include changing tie tube materials to TZM, changing the moderator to low vapor-pressure yttrium hydride, and changing the fuel form from graphite matrix to a carbon-carbide composite.

  7. A summary of computational experience at GE Aircraft Engines for complex turbulent flows in gas turbines

    NASA Astrophysics Data System (ADS)

    Zerkle, Ronald D.; Prakash, Chander

    1995-03-01

    This viewgraph presentation summarizes some CFD experience at GE Aircraft Engines for flows in the primary gaspath of a gas turbine engine and in turbine blade cooling passages. It is concluded that application of the standard k-epsilon turbulence model with wall functions is not adequate for accurate CFD simulation of aerodynamic performance and heat transfer in the primary gas path of a gas turbine engine. New models are required in the near-wall region which include more physics than wall functions. The two-layer modeling approach appears attractive because of its computational complexity. In addition, improved CFD simulation of film cooling and turbine blade internal cooling passages will require anisotropic turbulence models. New turbulence models must be practical in order to have a significant impact on the engine design process. A coordinated turbulence modeling effort between NASA centers would be beneficial to the gas turbine industry.

  8. A summary of computational experience at GE Aircraft Engines for complex turbulent flows in gas turbines

    NASA Technical Reports Server (NTRS)

    Zerkle, Ronald D.; Prakash, Chander

    1995-01-01

    This viewgraph presentation summarizes some CFD experience at GE Aircraft Engines for flows in the primary gaspath of a gas turbine engine and in turbine blade cooling passages. It is concluded that application of the standard k-epsilon turbulence model with wall functions is not adequate for accurate CFD simulation of aerodynamic performance and heat transfer in the primary gas path of a gas turbine engine. New models are required in the near-wall region which include more physics than wall functions. The two-layer modeling approach appears attractive because of its computational complexity. In addition, improved CFD simulation of film cooling and turbine blade internal cooling passages will require anisotropic turbulence models. New turbulence models must be practical in order to have a significant impact on the engine design process. A coordinated turbulence modeling effort between NASA centers would be beneficial to the gas turbine industry.

  9. DART system analysis.

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

    Boggs, Paul T.; Althsuler, Alan; Larzelere, Alex R.

    2005-08-01

    The Design-through-Analysis Realization Team (DART) is chartered with reducing the time Sandia analysts require to complete the engineering analysis process. The DART system analysis team studied the engineering analysis processes employed by analysts in Centers 9100 and 8700 at Sandia to identify opportunities for reducing overall design-through-analysis process time. The team created and implemented a rigorous analysis methodology based on a generic process flow model parameterized by information obtained from analysts. They also collected data from analysis department managers to quantify the problem type and complexity distribution throughout Sandia's analyst community. They then used this information to develop a communitymore » model, which enables a simple characterization of processes that span the analyst community. The results indicate that equal opportunity for reducing analysis process time is available both by reducing the ''once-through'' time required to complete a process step and by reducing the probability of backward iteration. In addition, reducing the rework fraction (i.e., improving the engineering efficiency of subsequent iterations) offers approximately 40% to 80% of the benefit of reducing the ''once-through'' time or iteration probability, depending upon the process step being considered. Further, the results indicate that geometry manipulation and meshing is the largest portion of an analyst's effort, especially for structural problems, and offers significant opportunity for overall time reduction. Iteration loops initiated late in the process are more costly than others because they increase ''inner loop'' iterations. Identifying and correcting problems as early as possible in the process offers significant opportunity for time savings.« less

  10. Strategies for Maximizing Successful Drug Substance Technology Transfer Using Engineering, Shake-Down, and Wet Test Runs.

    PubMed

    Abraham, Sushil; Bain, David; Bowers, John; Larivee, Victor; Leira, Francisco; Xie, Jasmina

    2015-01-01

    The technology transfer of biological products is a complex process requiring control of multiple unit operations and parameters to ensure product quality and process performance. To achieve product commercialization, the technology transfer sending unit must successfully transfer knowledge about both the product and the process to the receiving unit. A key strategy for maximizing successful scale-up and transfer efforts is the effective use of engineering and shake-down runs to confirm operational performance and product quality prior to embarking on good manufacturing practice runs such as process performance qualification runs. We consider key factors to consider in making the decision to perform shake-down or engineering runs. We also present industry benchmarking results of how engineering runs are used in drug substance technology transfers alongside the main themes and best practices that have emerged. Our goal is to provide companies with a framework for ensuring the "right first time" technology transfers with effective deployment of resources within increasingly aggressive timeline constraints. © PDA, Inc. 2015.

  11. A Multidisciplinary Approach to Mixer-Ejector Analysis and Design

    NASA Technical Reports Server (NTRS)

    Hendricks, Eric, S.; Seidel, Jonathan, A.

    2012-01-01

    The design of an engine for a civil supersonic aircraft presents a difficult multidisciplinary problem to propulsion system engineers. There are numerous competing requirements for the engine, such as to be efficient during cruise while yet quiet enough at takeoff to meet airport noise regulations. The use of mixer-ejector nozzles presents one possible solution to this challenge. However, designing a mixer-ejector which will successfully address both of these concerns is a difficult proposition. Presented in this paper is an integrated multidisciplinary approach to the analysis and design of these systems. A process that uses several low-fidelity tools to evaluate both the performance and acoustics of mixer-ejectors nozzles is described. This process is further expanded to include system-level modeling of engines and aircraft to determine the effects on mission performance and noise near airports. The overall process is developed in the OpenMDAO framework currently being developed by NASA. From the developed process, sample results are given for a notional mixer-ejector design, thereby demonstrating the capabilities of the method.

  12. Applications of Ecological Engineering Remedies for Uranium Processing Sites, USA

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

    Waugh, William

    The U.S. Department of Energy (USDOE) is responsible for remediation of environmental contamination and long-term stewardship of sites associated with the legacy of nuclear weapons production during the Cold War in the United States. Protection of human health and the environment will be required for hundreds or even thousands of years at many legacy sites. USDOE continually evaluates and applies advances in science and technology to improve the effectiveness and sustainability of surface and groundwater remedies (USDOE 2011). This paper is a synopsis of ecological engineering applications that USDOE is evaluating to assess the effectiveness of remedies at former uraniummore » processing sites in the southwestern United States. Ecological engineering remedies are predicated on the concept that natural ecological processes at legacy sites, once understood, can be beneficially enhanced or manipulated. Advances in tools for characterizing key processes and for monitoring remedy performance are demonstrating potential. We present test cases for four ecological engineering remedies that may be candidates for international applications.« less

  13. IDC Re-Engineering Phase 2 System Requirements Document Version 1.4

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

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

    This System Requirements Document (SRD) defines waveform data processing requirements for the International Data Centre (IDC) of the Comprehensive Nuclear Test Ban Treaty Organization (CTBTO). The IDC applies, on a routine basis, automatic processing methods and interactive analysis to raw International Monitoring System (IMS) data in order to produce, archive, and distribute standard IDC products on behalf of all States Parties. 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,more » but includes requirements for the dissemination of radionuclide data and products.« less

  14. IDC Re-Engineering Phase 2 System Requirements Document V1.3.

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

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

    2015-12-01

    This System Requirements Document (SRD) defines waveform data processing requirements for the International Data Centre (IDC) of the Comprehensive Nuclear Test Ban Treaty Organization (CTBTO). The IDC applies, on a routine basis, automatic processing methods and interactive analysis to raw International Monitoring System (IMS) data in order to produce, archive, and distribute standard IDC products on behalf of all States Parties. 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 datamore » but includes requirements for the dissemination of radionuclide data and products.« less

  15. Closed Loop Requirements and Analysis Management

    NASA Technical Reports Server (NTRS)

    Lamoreaux, Michael; Verhoef, Brett

    2015-01-01

    Effective systems engineering involves the use of analysis in the derivation of requirements and verification of designs against those requirements. The initial development of requirements often depends on analysis for the technical definition of specific aspects of a product. Following the allocation of system-level requirements to a product's components, the closure of those requirements often involves analytical approaches to verify that the requirement criteria have been satisfied. Meanwhile, changes that occur in between these two processes need to be managed in order to achieve a closed-loop requirement derivation/verification process. Herein are presented concepts for employing emerging Team center capabilities to jointly manage requirements and analysis data such that analytical techniques are utilized to effectively derive and allocate requirements, analyses are consulted and updated during the change evaluation processes, and analyses are leveraged during the design verification process. Recommendations on concept validation case studies are also discussed.

  16. Cost-engineering modeling to support rapid concept development of an advanced infrared satellite system

    NASA Astrophysics Data System (ADS)

    Bell, Kevin D.; Dafesh, Philip A.; Hsu, L. A.; Tsuda, A. S.

    1995-12-01

    Current architectural and design trade techniques often carry unaffordable alternatives late into the decision process. Early decisions made during the concept exploration and development (CE&D) phase will drive the cost of a program more than any other phase of development; thus, designers must be able to assess both the performance and cost impacts of their early choices. The Space Based Infrared System (SBIRS) cost engineering model (CEM) described in this paper is an end-to-end process integrating engineering and cost expertise through commonly available spreadsheet software, allowing for concurrent design engineering and cost estimation to identify and balance system drives to reduce acquisition costs. The automated interconnectivity between subsystem models using spreadsheet software allows for the quick and consistent assessment of the system design impacts and relative cost impacts due to requirement changes. It is different from most CEM efforts attempted in the past as it incorporates more detailed spacecraft and sensor payload models, and has been applied to determine the cost drivers for an advanced infrared satellite system acquisition. The CEM is comprised of integrated detailed engineering and cost estimating relationships describing performance, design, and cost parameters. Detailed models have been developed to evaluate design parameters for the spacecraft bus and sensor; both step-starer and scanner sensor types incorporate models of focal plane array, optics, processing, thermal, communications, and mission performance. The current CEM effort has provided visibility to requirements, design, and cost drivers for system architects and decision makers to determine the configuration of an infrared satellite architecture that meets essential requirements cost effectively. In general, the methodology described in this paper consists of process building blocks that can be tailored to the needs of many applications. Descriptions of the spacecraft and payload subsystem models provide insight into The Aerospace Corporation expertise and scope of the SBIRS concept development effort.

  17. Propellant injection systems and processes

    NASA Technical Reports Server (NTRS)

    Ito, Jackson I.

    1995-01-01

    The previous 'Art of Injector Design' is maturing and merging with the more systematic 'Science of Combustion Device Analysis.' This technology can be based upon observation, correlation, experimentation and ultimately analytical modeling based upon basic engineering principles. This methodology is more systematic and far superior to the historical injector design process of 'Trial and Error' or blindly 'Copying Past Successes.' The benefit of such an approach is to be able to rank candidate design concepts for relative probability of success or technical risk in all the important combustion device design requirements and combustion process development risk categories before committing to an engine development program. Even if a single analytical design concept cannot be developed to predict satisfying all requirements simultaneously, a series of risk mitigation key enabling technologies can be identified for early resolution. Lower cost subscale or laboratory experimentation to demonstrate proof of principle, critical instrumentation requirements, and design discriminating test plans can be developed based on the physical insight provided by these analyses.

  18. Improved Concrete Cutting and Excavation Capabilities for Crater Repair, Phase 1

    DTIC Science & Technology

    2014-04-01

    manageable pieces, it is not recommended for the ADR process because of the requirement for additional supporting equipment - the air compressor ... Air Force Civil Engineer Center Tyndall Air Force Base, FL 32403-5319 ERDC/GSL TR-14-8 ii Abstract The US Army Engineer Research and...Development Center was tasked by the US Air Force Civil Engineer Center to improve the saw cutting and excavation production rates of crater repairs in thick

  19. Overview of thermal barrier coatings in diesel engines

    NASA Technical Reports Server (NTRS)

    Yonushonis, T. M.

    1995-01-01

    An understanding of delamination mechanisms in thermal barrier coatings has been developed for diesel applications through nondestructive evaluation, structural analysis modeling and engine evaluation of various thermal barrier coatings. This knowledge has resulted in improved thermal barrier coatings which survive abusive cyclic fatigue tests in high output diesel engines. Significant efforts are still required to improve the plasma spray processing capability and the economics for complex geometry diesel engine components. Data obtained from advanced diesel engines on the effect of thermal barrier coatings on engine fuel economy and emission has not been encouraging. Although the underlying metal component temperatures have been reduced through the use of thermal barrier coating, engine efficiency and emission trends have not been promising.

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

  1. Engineering of biotin-prototrophy in Pichia pastoris for robust production processes.

    PubMed

    Gasser, Brigitte; Dragosits, Martin; Mattanovich, Diethard

    2010-11-01

    Biotin plays an essential role as cofactor for biotin-dependent carboxylases involved in essential metabolic pathways. The cultivation of Pichia pastoris, a methylotrophic yeast that is successfully used as host for the production of recombinant proteins, requires addition of high dosage of biotin. As biotin is the only non-salt media component used during P. pastoris fermentation (apart from the carbon source), nonconformities during protein production processes are usually attributed to poor quality of the added biotin. In order to avoid dismissed production runs due to biotin quality issues, we engineered the biotin-requiring yeast P. pastoris to become a biotin-prototrophic yeast. Integration of four genes involved in the biotin biosynthesis from brewing yeast into the P. pastoris genome rendered P. pastoris biotin-prototrophic. The engineered strain has successfully been used as production host for both intracellular and secreted heterologous proteins in fed-batch processes, employing mineral media without vitamins. Another field of application for these truly prototrophic hosts is the production of biochemicals and small metabolites, where defined mineral media leads to easier purification procedures. Copyright © 2010 Elsevier Inc. All rights reserved.

  2. Expert systems for superalloy studies

    NASA Technical Reports Server (NTRS)

    Workman, Gary L.; Kaukler, William F.

    1990-01-01

    There are many areas in science and engineering which require knowledge of an extremely complex foundation of experimental results in order to design methodologies for developing new materials or products. Superalloys are an area which fit well into this discussion in the sense that they are complex combinations of elements which exhibit certain characteristics. Obviously the use of superalloys in high performance, high temperature systems such as the Space Shuttle Main Engine is of interest to NASA. The superalloy manufacturing process is complex and the implementation of an expert system within the design process requires some thought as to how and where it should be implemented. A major motivation is to develop a methodology to assist metallurgists in the design of superalloy materials using current expert systems technology. Hydrogen embrittlement is disasterous to rocket engines and the heuristics can be very complex. Attacking this problem as one module in the overall design process represents a significant step forward. In order to describe the objectives of the first phase implementation, the expert system was designated Hydrogen Environment Embrittlement Expert System (HEEES).

  3. A Framework for Performing V&V within Reuse-Based Software Engineering

    NASA Technical Reports Server (NTRS)

    Addy, Edward A.

    1996-01-01

    Verification and validation (V&V) is performed during application development for many systems, especially safety-critical and mission-critical systems. The V&V process is intended to discover errors, especially errors related to critical processing, as early as possible during the development process. Early discovery is important in order to minimize the cost and other impacts of correcting these errors. In order to provide early detection of errors, V&V is conducted in parallel with system development, often beginning with the concept phase. In reuse-based software engineering, however, decisions on the requirements, design and even implementation of domain assets can be made prior to beginning development of a specific system. In this case, V&V must be performed during domain engineering in order to have an impact on system development. This paper describes a framework for performing V&V within architecture-centric, reuse-based software engineering. This framework includes the activities of traditional application-level V&V, and extends these activities into domain engineering and into the transition between domain engineering and application engineering. The framework includes descriptions of the types of activities to be performed during each of the life-cycle phases, and provides motivation for the activities.

  4. Design and analysis of siloxanes removal by adsorption from landfill gas for waste-to-energy processes.

    PubMed

    Elwell, Anthony C; Elsayed, Nada H; Kuhn, John N; Joseph, Babu

    2018-03-01

    Separation of volatile methyl siloxanes from landfill gas using fixed adsorption beds was modeled with the objective of identifying appropriate technology and the economics associated with this purification step. A general adsorption model assuming plug flow and radial symmetry was developed and used to conduct a parametric sweep of 162 unique cases. The varied parameters were adsorbent type (activated carbon and silica gel), bed height (3.05-9.15 m/10-30 ft), inlet siloxane concentration (5-15 mg/m 3 ), moisture content (0-100% relative humidity at STP or RH), and siloxane tolerance limit (0.094-9.4 mg/m 3 ) that correlated to three distinct energy conversion technologies (electricity production using engines or fuels cells or catalytic conversion to liquid hydrocarbon fuels). Due to the detrimental effect of RH on siloxane absorption, the maximum allowable moisture content of LFG before purification is 50% RH and moisture removal processes are also required. The design calculations using a selected case study show that the adsorption bed height required needed for 6 months minimum breakthrough time for catalytic fuel production is twice that for engine applications. Fuel cell applications require 3 times the bed height compared to engine applications. However, the purification costs amounted to 94%, 16% and 52% of recovered product value for engine, liquefaction, and fuel cell applications, respectively indicating the need for a high value product to justify purification costs. The approaches and conclusions can be extended to specific process conditions for landfill gas purification and to other processes that use biogas produced from waste as a feedstock. Copyright © 2017 Elsevier Ltd. All rights reserved.

  5. 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).

  6. 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).

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

  8. Current state of nuclear fuel cycles in nuclear engineering and trends in their development according to the environmental safety requirements

    NASA Astrophysics Data System (ADS)

    Vislov, I. S.; Pischulin, V. P.; Kladiev, S. N.; Slobodyan, S. M.

    2016-08-01

    The state and trends in the development of nuclear fuel cycles in nuclear engineering, taking into account the ecological aspects of using nuclear power plants, are considered. An analysis of advantages and disadvantages of nuclear engineering, compared with thermal engineering based on organic fuel types, was carried out. Spent nuclear fuel (SNF) reprocessing is an important task in the nuclear industry, since fuel unloaded from modern reactors of any type contains a large amount of radioactive elements that are harmful to the environment. On the other hand, the newly generated isotopes of uranium and plutonium should be reused to fabricate new nuclear fuel. The spent nuclear fuel also includes other types of fission products. Conditions for SNF handling are determined by ecological and economic factors. When choosing a certain handling method, one should assess these factors at all stages of its implementation. There are two main methods of SNF handling: open nuclear fuel cycle, with spent nuclear fuel assemblies (NFAs) that are held in storage facilities with their consequent disposal, and closed nuclear fuel cycle, with separation of uranium and plutonium, their purification from fission products, and use for producing new fuel batches. The development of effective closed fuel cycles using mixed uranium-plutonium fuel can provide a successful development of the nuclear industry only under the conditions of implementation of novel effective technological treatment processes that meet strict requirements of environmental safety and reliability of process equipment being applied. The diversity of technological processes is determined by different types of NFA devices and construction materials being used, as well as by the composition that depends on nuclear fuel components and operational conditions for assemblies in the nuclear power reactor. This work provides an overview of technological processes of SNF treatment and methods of handling of nuclear fuel assemblies. Based on analysis of modern engineering solutions on SNF regeneration, it has been concluded that new reprocessing technologies should meet the ecological safety requirements, provide a more extensive use of the resource base of nuclear engineering, allow the production of valuable and trace elements on an industrial scale, and decrease radioactive waste release.

  9. Enhancing the Human Factors Engineering Role in an Austere Fiscal Environment

    NASA Technical Reports Server (NTRS)

    Stokes, Jack W.

    2003-01-01

    An austere fiscal environment in the aerospace community creates pressures to reduce program costs, often minimizing or sometimes even deleting the human interface requirements from the design process. With an assumption that the flight crew can recover real time from a poorly human factored space vehicle design, the classical crew interface requirements have been either not included in the design or not properly funded, though carried as requirements. Cost cuts have also affected quality of retained human factors engineering personnel. In response to this concern, planning is ongoing to correct the acting issues. Herein are techniques for ensuring that human interface requirements are integrated into a flight design, from proposal through verification and launch activation. This includes human factors requirements refinement and consolidation across flight programs; keyword phrases in the proposals; closer ties with systems engineering and other classical disciplines; early planning for crew-interface verification; and an Agency integrated human factors verification program, under the One NASA theme. Importance is given to communication within the aerospace human factors discipline, and utilizing the strengths of all government, industry, and academic human factors organizations in an unified research and engineering approach. A list of recommendations and concerns are provided in closing.

  10. Spacelab user implementation assessment study. (Software requirements analysis). Volume 2: Technical report

    NASA Technical Reports Server (NTRS)

    1976-01-01

    The engineering analyses and evaluation studies conducted for the Software Requirements Analysis are discussed. Included are the development of the study data base, synthesis of implementation approaches for software required by both mandatory onboard computer services and command/control functions, and identification and implementation of software for ground processing activities.

  11. Sustainable and responsible design from a Christian worldview.

    PubMed

    Eisenbarth, Steven R; Van Treuren, Kenneth W

    2004-04-01

    Many aspects of design require engineers to make choices based on non-quantifiable personal perspectives. These decisions touch issues in aesthetics, ethics, social impact, and responsibility and sustainability. Part of Baylor University's mission is to provide a learning community in which Christian life values and worldviews might be integrated into academic disciplines. In view of this institutional commitment, members of the Engineering faculty are investigating how Christian worldviews might interact with elements of engineering design in such a way as to produce uniquely Christian insights and inform the non-quantifiable aspects of the engineering process.

  12. Requirements Analysis for Large Ada Programs: Lessons Learned on CCPDS- R

    DTIC Science & Technology

    1989-12-01

    when the design had matured and This approach was not optimal from the formal the SRS role was to be the tester’s contract, implemen- testing and...on the software development CPU processing load. These constraints primar- process is the necessity to include sufficient testing ily affect algorithm...allocations and timing requirements are by-products of the software design process when multiple CSCls are a P R StrR eSOFTWARE ENGINEERING executed within

  13. Characterization of the Temperature Capabilities of Advanced Disk Alloy ME3

    NASA Technical Reports Server (NTRS)

    Gabb, Timothy P.; Telesman, Jack; Kantzos, Peter T.; OConnor, Kenneth

    2002-01-01

    The successful development of an advanced powder metallurgy disk alloy, ME3, was initiated in the NASA High Speed Research/Enabling Propulsion Materials (HSR/EPM) Compressor/Turbine Disk program in cooperation with General Electric Engine Company and Pratt & Whitney Aircraft Engines. This alloy was designed using statistical screening and optimization of composition and processing variables to have extended durability at 1200 F in large disks. Disks of this alloy were produced at the conclusion of the program using a realistic scaled-up disk shape and processing to enable demonstration of these properties. The objective of the Ultra-Efficient Engine Technologies disk program was to assess the mechanical properties of these ME3 disks as functions of temperature in order to estimate the maximum temperature capabilities of this advanced alloy. These disks were sectioned, machined into specimens, and extensively tested. Additional sub-scale disks and blanks were processed and selectively tested to explore the effects of several processing variations on mechanical properties. Results indicate the baseline ME3 alloy and process can produce 1300 to 1350 F temperature capabilities, dependent on detailed disk and engine design property requirements.

  14. Silicon production process evaluations

    NASA Technical Reports Server (NTRS)

    1982-01-01

    Chemical engineering analysis was continued for the HSC process (Hemlock Semiconductor Corporation) in which solar cell silicon is produced in a 1,000 MT/yr plant. Progress and status are reported for the primary engineering activities involved in the preliminary process engineering design of the plant base case conditions (96%), reaction chemistry (96%), process flow diagram (85%), material balance (85%), energy balance (60%), property data (60%), equipment design (40%), major equipment list (30%) and labor requirements (10%). Engineering design of the second distillation column (D-02, TCS column) in the process was completed. The design is based on a 97% recovery of the light key (TCS, trichlorosilane) in the distillate and a 97% recovery of the heavy key (TET, silicon tetrachloride) in the bottoms. At a reflux ratio of 2, the specified recovery of TCS and TET is achieved with 20 trays (equilibrium stages, N=20). Respective feed tray locations are 9, 12 and 15 (NF sub 1 = 9, NF sub 2 = 12,, and NF sub 3 = 15). A total condenser is used for the distillation which is conducted at a pressure of 90 psia.

  15. Using Visualization and Computation in the Analysis of Separation Processes

    ERIC Educational Resources Information Center

    Joo, Yong Lak; Choudhary, Devashish

    2006-01-01

    For decades, every chemical engineer has been asked to have a background in separations. The required separations course can, however, be uninspiring and superficial because understanding many separation processes involves conventional graphical methods and commercial process simulators. We utilize simple, user-­friendly mathematical software,…

  16. EmptyHeaded: A Relational Engine for Graph Processing

    PubMed Central

    Aberger, Christopher R.; Tu, Susan; Olukotun, Kunle; Ré, Christopher

    2016-01-01

    There are two types of high-performance graph processing engines: low- and high-level engines. Low-level engines (Galois, PowerGraph, Snap) provide optimized data structures and computation models but require users to write low-level imperative code, hence ensuring that efficiency is the burden of the user. In high-level engines, users write in query languages like datalog (SociaLite) or SQL (Grail). High-level engines are easier to use but are orders of magnitude slower than the low-level graph engines. We present EmptyHeaded, a high-level engine that supports a rich datalog-like query language and achieves performance comparable to that of low-level engines. At the core of EmptyHeaded’s design is a new class of join algorithms that satisfy strong theoretical guarantees but have thus far not achieved performance comparable to that of specialized graph processing engines. To achieve high performance, EmptyHeaded introduces a new join engine architecture, including a novel query optimizer and data layouts that leverage single-instruction multiple data (SIMD) parallelism. With this architecture, EmptyHeaded outperforms high-level approaches by up to three orders of magnitude on graph pattern queries, PageRank, and Single-Source Shortest Paths (SSSP) and is an order of magnitude faster than many low-level baselines. We validate that EmptyHeaded competes with the best-of-breed low-level engine (Galois), achieving comparable performance on PageRank and at most 3× worse performance on SSSP. PMID:28077912

  17. Case Study of 'Engineering Peer Meetings' in JPL's ST-6 Project

    NASA Technical Reports Server (NTRS)

    Chao, Lawrence P.; Tumer, Irem

    2004-01-01

    This design process error-proofing case study describes a design review practice implemented by a project manager at NASA Jet Propulsion Laboratory. There are many types of reviews at NASA: required and not, formalized and informal, programmatic and technical. Standing project formal reviews such as the Preliminary Design Review (PDR) and Critical Design Review (CDR) are a required part of every project and mission development. However, the engineering peer reviews that support teams technical work on such projects are often informal, ad hoc, and inconsistent across the organization. This case study discusses issues and innovations identified by a project manager at JPL and implemented in 'engineering peer meetings' for his group.

  18. Case Study of "Engineering Peer Meetings" in JPL's ST-6 Project

    NASA Technical Reports Server (NTRS)

    Tumer, Irem Y.; Chao, Lawrence P.

    2003-01-01

    This design process error-proofing case study describes a design review practice implemented by a project manager at NASA Jet Propulsion Laboratory. There are many types of reviews at NASA: required and not, formalized and informal, programmatic and technical. Standing project formal reviews such as the Preliminary Design Review (PDR) and Critical Design Review (CDR) are a required part of every project and mission development. However, the engineering peer reviews that support teams technical work on such projects are often informal, ad hoc, and inconsistent across the organization. This case study discusses issues and innovations identified by a project manager at JPL and implemented in "engineering peer meetings" for his group.

  19. Handbook of Industrial Engineering Equations, Formulas, and Calculations

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

    Badiru, Adedeji B; Omitaomu, Olufemi A

    The first handbook to focus exclusively on industrial engineering calculations with a correlation to applications, Handbook of Industrial Engineering Equations, Formulas, and Calculations contains a general collection of the mathematical equations often used in the practice of industrial engineering. Many books cover individual areas of engineering and some cover all areas, but none covers industrial engineering specifically, nor do they highlight topics such as project management, materials, and systems engineering from an integrated viewpoint. Written by acclaimed researchers and authors, this concise reference marries theory and practice, making it a versatile and flexible resource. Succinctly formatted for functionality, the bookmore » presents: Basic Math Calculations; Engineering Math Calculations; Production Engineering Calculations; Engineering Economics Calculations; Ergonomics Calculations; Facility Layout Calculations; Production Sequencing and Scheduling Calculations; Systems Engineering Calculations; Data Engineering Calculations; Project Engineering Calculations; and Simulation and Statistical Equations. It has been said that engineers make things while industrial engineers make things better. To make something better requires an understanding of its basic characteristics and the underlying equations and calculations that facilitate that understanding. To do this, however, you do not have to be computational experts; you just have to know where to get the computational resources that are needed. This book elucidates the underlying equations that facilitate the understanding required to improve design processes, continuously improving the answer to the age-old question: What is the best way to do a job?« less

  20. Coal gasification systems engineering and analysis. Appendix B: Medium B+U gas design

    NASA Technical Reports Server (NTRS)

    1980-01-01

    A four module, 20,000 TPD, based on KT coal gasification technology was designed. The plant processes Kentucky No. 9 coal with provisions for up to five percent North Alabama coal. Medium BTU gas with heat content of 305 BTU/SCF and not more than 200 ppm sulfur is the primary plant product. Sulfur is recovered for scale as prilled sulfur. Ash disposal is on site. The plant is designed for zero water discharge. Trade studies provided the basis for not using boiler produced steam to drive prime movers. Thus process derived steam in excess of process requirements in superheated for power use in prime movers. Electricity from the TVA grid is used to supply the balance of the plant prime mover power requirements. A study of the effect of mine mouth coal cleaning showed that coal cleaning is not an economically preferred route. The design procedure involved defining available processes to meet the requirements of each system, technical/economic trade studies to select the preferred processes, and engineering design and flow sheet development for each module. Cost studies assumed a staggered construction schedule for the four modules beginning spring 1981 and a 90% on stream factor.

  1. Automated process planning system

    NASA Technical Reports Server (NTRS)

    Mann, W.

    1978-01-01

    Program helps process engineers set up manufacturing plans for machined parts. System allows one to develop and store library of similar parts characteristics, as related to particular facility. Information is then used in interactive system to help develop manufacturing plans that meet required standards.

  2. 40 CFR 63.2465 - What requirements must I meet for process vents that emit hydrogen halide and halogen HAP or HAP...

    Code of Federal Regulations, 2010 CFR

    2010-07-01

    ... Pollutants: Miscellaneous Organic Chemical Manufacturing Emission Limits, Work Practice Standards, and... the mass emission rate of HAP metals based on process knowledge, engineering assessment, or test data...

  3. Multi-surface topography targeted plateau honing for the processing of cylinder liner surfaces of automotive engines

    NASA Astrophysics Data System (ADS)

    Lawrence, K. Deepak; Ramamoorthy, B.

    2016-03-01

    Cylinder bores of automotive engines are 'engineered' surfaces that are processed using multi-stage honing process to generate multiple layers of micro geometry for meeting the different functional requirements of the piston assembly system. The final processed surfaces should comply with several surface topographic specifications that are relevant for the good tribological performance of the engine. Selection of the process parameters in three stages of honing to obtain multiple surface topographic characteristics simultaneously within the specification tolerance is an important module of the process planning and is often posed as a challenging task for the process engineers. This paper presents a strategy by combining the robust process design and gray-relational analysis to evolve the operating levels of honing process parameters in rough, finish and plateau honing stages targeting to meet multiple surface topographic specifications on the final running surface of the cylinder bores. Honing experiments were conducted in three stages namely rough, finish and plateau honing on cast iron cylinder liners by varying four honing process parameters such as rotational speed, oscillatory speed, pressure and honing time. Abbott-Firestone curve based functional parameters (Rk, Rpk, Rvk, Mr1 and Mr2) coupled with mean roughness depth (Rz, DIN/ISO) and honing angle were measured and identified as the surface quality performance targets to be achieved. The experimental results have shown that the proposed approach is effective to generate cylinder liner surface that would simultaneously meet the explicit surface topographic specifications currently practiced by the industry.

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

  5. Inspection planning development: An evolutionary approach using reliability engineering as a tool

    NASA Technical Reports Server (NTRS)

    Graf, David A.; Huang, Zhaofeng

    1994-01-01

    This paper proposes an evolutionary approach for inspection planning which introduces various reliability engineering tools into the process and assess system trade-offs among reliability, engineering requirement, manufacturing capability and inspection cost to establish an optimal inspection plan. The examples presented in the paper illustrate some advantages and benefits of the new approach. Through the analysis, reliability and engineering impacts due to manufacturing process capability and inspection uncertainty are clearly understood; the most cost effective and efficient inspection plan can be established and associated risks are well controlled; some inspection reductions and relaxations are well justified; and design feedbacks and changes may be initiated from the analysis conclusion to further enhance reliability and reduce cost. The approach is particularly promising as global competitions and customer quality improvement expectations are rapidly increasing.

  6. Collaborative engineering-design support system

    NASA Technical Reports Server (NTRS)

    Lee, Dong HO; Decker, D. Richard

    1994-01-01

    Designing engineering objects requires many engineers' knowledge from different domains. There needs to be cooperative work among engineering designers to complete a design. Revisions of a design are time consuming, especially if designers work at a distance and with different design description formats. In order to reduce the design cycle, there needs to be a sharable design describing the engineering community, which can be electronically transportable. Design is a process of integrating that is not easy to define definitively. This paper presents Design Script which is a generic engineering design knowledge representation scheme that can be applied in any engineering domain. The Design Script is developed through encapsulation of common design activities and basic design components based on problem decomposition. It is implemented using CLIPS with a Windows NT graphical user interface. The physical relationships between engineering objects and their subparts can be constructed in a hierarchical manner. The same design process is repeatedly applied at each given level of hierarchy and recursively into lower levels of the hierarchy. Each class of the structure can be represented using the Design Script.

  7. Modeling of materials supply, demand and prices

    NASA Technical Reports Server (NTRS)

    1982-01-01

    The societal, economic, and policy tradeoffs associated with materials processing and utilization, are discussed. The materials system provides the materials engineer with the system analysis required for formulate sound materials processing, utilization, and resource development policies and strategies. Materials system simulation and modeling research program including assessments of materials substitution dynamics, public policy implications, and materials process economics was expanded. This effort includes several collaborative programs with materials engineers, economists, and policy analysts. The technical and socioeconomic issues of materials recycling, input-output analysis, and technological change and productivity are examined. The major thrust areas in materials systems research are outlined.

  8. Control Design for a Generic Commercial Aircraft Engine

    NASA Technical Reports Server (NTRS)

    Csank, Jeffrey; May, Ryan D.

    2010-01-01

    This paper describes the control algorithms and control design process for a generic commercial aircraft engine simulation of a 40,000 lb thrust class, two spool, high bypass ratio turbofan engine. The aircraft engine is a complex nonlinear system designed to operate over an extreme range of environmental conditions, at temperatures from approximately -60 to 120+ F, and at altitudes from below sea level to 40,000 ft, posing multiple control design constraints. The objective of this paper is to provide the reader an overview of the control design process, design considerations, and justifications as to why the particular architecture and limits have been chosen. The controller architecture contains a gain-scheduled Proportional Integral controller along with logic to protect the aircraft engine from exceeding any limits. Simulation results illustrate that the closed loop system meets the Federal Aviation Administration s thrust response requirements

  9. Future heavy duty trucking engine requirements

    NASA Technical Reports Server (NTRS)

    Strawhorn, L. W.; Suski, V. A.

    1985-01-01

    Developers of advanced heavy duty diesel engines are engaged in probing the opportunities presented by new materials and techniques. This process is technology driven, but there is neither assurance that the eventual users of the engines so developed will be comfortable with them nor, indeed, that those consumers will continue to exist in either the same form, or numbers as they do today. To ensure maximum payoff of research dollars, the equipment development process must consider user needs. This study defines motor carrier concerns, cost tolerances, and the engine parameters which match the future projected industry needs. The approach taken to do that is to be explained and the results presented. The material to be given comes basically from a survey of motor carrier fleets. It provides indications of the role of heavy duty vehicles in the 1998 period and their desired maintenance and engine performance parameters.

  10. Development Status and Performance Comparisons of Environmental Barrier Coating Systems for SiCSiC Ceramic Matrix Composites

    NASA Technical Reports Server (NTRS)

    Zhu, Dongming; Harder, Bryan

    2016-01-01

    Environmental barrier coatings (EBC) and SiCSiC ceramic matrix composites (CMCs) will play a crucial role in future aircraft turbine engine systems, because of their ability to significantly increase engine operating temperatures, reduce engine weight and cooling requirements. This paper presents current NASA EBC-CMC development emphases including: the coating composition and processing improvements, laser high heat flux-thermal gradient thermo-mechanical fatigue - environmental testing methodology development, and property evaluations for next generation EBC-CMC systems. EBCs processed with various deposition techniques including Plasma Spray, Electron Beam - Physical Vapor Deposition, and Plasma Spray Physical Vapor Deposition (PS-PVD) will be particularly discussed. The testing results and demonstrations of advanced EBCs-CMCs in complex simulated engine thermal gradient cyclic fatigue, oxidizing-steam and CMAS environments will help provide insights into the coating development strategies to meet long-term engine component durability goals.

  11. Propulsion and Energetics Panel Working Group 13 on Alternative Jet Engine Fuels. Volume 2. Main Report

    DTIC Science & Technology

    1982-07-01

    twenty years the only economically available fuels for aircraft gas turbine engines will be those from the processing of conventional crude petroleum...alternative fuels in new aircraft engines. i.e. problems ir, combustors. turbines . and afterburners. and methods for their solution. - Fuel system...required expertise assigned to each task group. The three areas were. Supply and demand scenarios for aviation turbine fuels in the NATO Nations for the

  12. Plastics disassembly versus bulk recycling: engineering design for end-of-life electronics resource recovery.

    PubMed

    Rios, Pedro; Stuart, Julie Ann; Grant, Ed

    2003-12-01

    Annual plastic flows through the business and consumer electronics manufacturing supply chain include nearly 3 billion lb of high-value engineering plastics derived from petroleum. The recovery of resource value from this stream presents critical challenges in areas of materials identification and recycling process design that demand new green engineering technologies applied together with life cycle assessment and ecological supply chain analysis to create viable plastics-to-plastics supply cycles. The sustainable recovery of potentially high-value engineering plastics streams requires that recyclers either avoid mixing plastic parts or purify later by separating smaller plastic pieces created in volume reduction (shredding) steps. Identification and separation constitute significant barriers in the plastics-to-plastics recycling value proposition. In the present work, we develop a model that accepts randomly arriving electronic products to study scenarios by which a recycler might identify and separate high-value engineering plastics as well as metals. Using discrete eventsimulation,we compare current mixed plastics recovery with spectrochemical plastic resin identification and subsequent sorting. Our results show that limited disassembly with whole-part identification can produce substantial yields in separated streams of recovered engineering thermoplastics. We find that disassembly with identification does not constitute a bottleneck, but rather, with relatively few workers, can be configured to pull the process and thus decrease maximum staging space requirements.

  13. Reflection for Meaning and Action as an Engine for Professional Development across Multiple Early Childhood Teacher Education Contexts

    ERIC Educational Resources Information Center

    Isik-Ercan, Zeynep; Perkins, Kelley

    2017-01-01

    Drawing from sociocultural theories of learning and literature on reflection in educational contexts, this article describes reflective practices as a meaning-making and action engine to support early childhood education practitioners' professional knowledge, skills, and dispositions. We argue that the process of reflection requires a differential…

  14. Process Inquiry: Analysis of Oral Problem-Solving Skills in Mathematics of Engineering Students

    ERIC Educational Resources Information Center

    Trance, Naci John C.

    2013-01-01

    This paper presents another effort in determining the difficulty of engineering students in terms of solving word problems. Students were presented with word problems in algebra. Then, they were asked to solve the word problems orally; that is, before they presented their written solutions, they were required to explain how they understood the…

  15. Conducting requirements analyses for research using routinely collected health data: a model driven approach.

    PubMed

    de Lusignan, Simon; Cashman, Josephine; Poh, Norman; Michalakidis, Georgios; Mason, Aaron; Desombre, Terry; Krause, Paul

    2012-01-01

    Medical research increasingly requires the linkage of data from different sources. Conducting a requirements analysis for a new application is an established part of software engineering, but rarely reported in the biomedical literature; and no generic approaches have been published as to how to link heterogeneous health data. Literature review, followed by a consensus process to define how requirements for research, using, multiple data sources might be modeled. We have developed a requirements analysis: i-ScheDULEs - The first components of the modeling process are indexing and create a rich picture of the research study. Secondly, we developed a series of reference models of progressive complexity: Data flow diagrams (DFD) to define data requirements; unified modeling language (UML) use case diagrams to capture study specific and governance requirements; and finally, business process models, using business process modeling notation (BPMN). These requirements and their associated models should become part of research study protocols.

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

  17. ISPE: A knowledge-based system for fluidization studies. 1990 Annual report

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

    Reddy, S.

    1991-01-01

    Chemical engineers use mathematical simulators to design, model, optimize and refine various engineering plants/processes. This procedure requires the following steps: (1) preparation of an input data file according to the format required by the target simulator; (2) excecuting the simulation; and (3) analyzing the results of the simulation to determine if all ``specified goals`` are satisfied. If the goals are not met, the input data file must be modified and the simulation repeated. This multistep process is continued until satisfactory results are obtained. This research was undertaken to develop a knowledge based system, IPSE (Intelligent Process Simulation Environment), that canmore » enhance the productivity of chemical engineers/modelers by serving as an intelligent assistant to perform a variety tasks related to process simulation. ASPEN, a widely used simulator by the US Department of Energy (DOE) at Morgantown Energy Technology Center (METC) was selected as the target process simulator in the project. IPSE, written in the C language, was developed using a number of knowledge-based programming paradigms: object-oriented knowledge representation that uses inheritance and methods, rulebased inferencing (includes processing and propagation of probabilistic information) and data-driven programming using demons. It was implemented using the knowledge based environment LASER. The relationship of IPSE with the user, ASPEN, LASER and the C language is shown in Figure 1.« less

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

  19. Software Engineering Laboratory (SEL) compendium of tools, revision 1

    NASA Technical Reports Server (NTRS)

    1982-01-01

    A set of programs used to aid software product development is listed. Known as software tools, such programs include requirements analyzers, design languages, precompilers, code auditors, code analyzers, and software librarians. Abstracts, resource requirements, documentation, processing summaries, and availability are indicated for most tools.

  20. Integrating Safety and Mission Assurance into Systems Engineering Modeling Practices

    NASA Technical Reports Server (NTRS)

    Beckman, Sean; Darpel, Scott

    2015-01-01

    During the early development of products, flight, or experimental hardware, emphasis is often given to the identification of technical requirements, utilizing such tools as use case and activity diagrams. Designers and project teams focus on understanding physical and performance demands and challenges. It is typically only later, during the evaluation of preliminary designs that a first pass, if performed, is made to determine the process, safety, and mission quality assurance requirements. Evaluation early in the life cycle, though, can yield requirements that force a fundamental change in design. This paper discusses an alternate paradigm for using the concepts of use case or activity diagrams to identify safety hazard and mission quality assurance risks and concerns using the same systems engineering modeling tools being used to identify technical requirements. It contains two examples of how this process might be used in the development of a space flight experiment, and the design of a Human Powered Pizza Delivery Vehicle, along with the potential benefits to decrease development time, and provide stronger budget estimates.

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

    Lingenfelter, A. C., LLNL

    Materials for gas turbine engines are required to meet a wide range of temperature and stress application requirements. These alloys exhibit a combination of creep resistance, creep rupture strength, yield and tensile strength over a wide temperature range, resistance to environmental attack (including oxidation, nitridation, sulphidation and carburization), fatigue and thermal fatigue resistance, metallurgical stability and useful thermal expansion characteristics. These properties are exhibited by a series of solid-solution-strengthened and precipitation-hardened nickel, iron and cobalt alloys. The properties needed to meet the turbine engine requirements have been achieved by specific alloy additions, by heat treatment and by thermal mechanical processing.more » A thorough understanding of the metallurgy and metallurgical processing of these materials is imperative in order to successfully fusion weld them. This same basic understanding is required for repair of a component with the added dimension of the potential effects of thermal cycling and environmental exposure the component will have endured in service. This article will explore the potential problems in joining and repair welding these materials.« less

  2. NLS propulsion - Government view

    NASA Technical Reports Server (NTRS)

    Smelser, Jerry W.

    1992-01-01

    The paper discusses the technology development for the Space Transportation Main Engine (STME). The STME is a liquid oxygen/liquid hydrogen engine with 650,000 pounds of thrust, which may be flown in single-engine or multiple-engine configurations, depending upon the payload and mission requirements. The technological developments completed so far include a vacuum plasma spray process, the liquid interface diffusion bonding, and a thin membrane platelet technology for the combustion chamber fabrication; baseline designs for the hydrogen turbopump and the oxygen pump; and the engine control system. The family of spacecraft for which this engine is being developed includes a 20,000 pound payload to LEO and a 150,000 pound to LEO vehicle.

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

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

  5. Overview of Plant Incorporated Protectants

    EPA Pesticide Factsheets

    When assessing the potential risks of genetically engineered plant-incorporated protectants, EPA requires extensive studies examining numerous factors. Learn more about the history and process for regulating PIPs.

  6. Digital Image Processing in Private Industry.

    ERIC Educational Resources Information Center

    Moore, Connie

    1986-01-01

    Examines various types of private industry optical disk installations in terms of business requirements for digital image systems in five areas: records management; transaction processing; engineering/manufacturing; information distribution; and office automation. Approaches for implementing image systems are addressed as well as key success…

  7. 19 CFR 10.710 - Value-content requirement.

    Code of Federal Regulations, 2011 CFR

    2011-04-01

    ... allocable to the specific goods; (iii) Research, development, design, engineering, and blueprint costs... or value of the materials produced in Jordan, plus the direct costs of processing operations... disposal. (d) Direct costs of processing operations—(1) Items included. For purposes of paragraph (a) of...

  8. Legal basis of the Advanced Therapies Regulation.

    PubMed

    Jekerle, V; Schröder, C; Pedone, E

    2010-01-01

    Advanced therapy medicinal products consist of gene therapy, somatic cell therapy and tissue engineered products. Due to their specific manufacturing process and mode of action these products require specially tailored legislation. With Regulation (EC) No. 1394/2007, these needs have been met. Definitions of gene therapy, somatic cell therapy and tissue engineered products were laid down. A new committee, the Committee for Advanced Therapies, was founded, special procedures such as the certification procedure for small- and medium-sized enterprises were established and the technical requirements for Marketing Authorisation Applications (quality, non-clinical and clinical) were revised.

  9. Breadboard RL10-11B low thrust operating mode

    NASA Technical Reports Server (NTRS)

    Kmiec, Thomas D.; Galler, Donald E.

    1987-01-01

    Cryogenic space engines require a cooling process to condition engine hardware to operating temperature before start. This can be accomplished most efficiently by burning propellants that would otherwise be dumped overboard after cooling the engine. The resultant low thrust operating modes are called Tank Head Idle and Pumped Idle. During February 1984, Pratt & Whitney conducted a series of tests demonstrating operation of the RL10 rocket engines at low thrust levels using a previously untried hydrogen/oxygen heat exchanger. The initial testing of the RL10-11B Breadboard Low Thrust Engine is described. The testing demonstrated operation at both tank head idle and pumped idle modes.

  10. Virtual and flexible digital signal processing system based on software PnP and component works

    NASA Astrophysics Data System (ADS)

    He, Tao; Wu, Qinghua; Zhong, Fei; Li, Wei

    2005-05-01

    An idea about software PnP (Plug & Play) is put forward according to the hardware PnP. And base on this idea, a virtual flexible digital signal processing system (FVDSPS) is carried out. FVDSPS is composed of a main control center, many sub-function modules and other hardware I/O modules. Main control center sends out commands to sub-function modules, and manages running orders, parameters and results of sub-functions. The software kernel of FVDSPS is DSP (Digital Signal Processing) module, which communicates with the main control center through some protocols, accept commands or send requirements. The data sharing and exchanging between the main control center and the DSP modules are carried out and managed by the files system of the Windows Operation System through the effective communication. FVDSPS real orients objects, orients engineers and orients engineering problems. With FVDSPS, users can freely plug and play, and fast reconfigure a signal process system according to engineering problems without programming. What you see is what you get. Thus, an engineer can orient engineering problems directly, pay more attention to engineering problems, and promote the flexibility, reliability and veracity of testing system. Because FVDSPS orients TCP/IP protocol, through Internet, testing engineers, technology experts can be connected freely without space. Engineering problems can be resolved fast and effectively. FVDSPS can be used in many fields such as instruments and meter, fault diagnosis, device maintenance and quality control.

  11. SE Requirements Development Tool User Guide

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

    Benson, Faith Ann

    2016-05-13

    The LANL Systems Engineering Requirements Development Tool (SERDT) is a data collection tool created in InfoPath for use with the Los Alamos National Laboratory’s (LANL) SharePoint sites. Projects can fail if a clear definition of the final product requirements is not performed. For projects to be successful requirements must be defined early in the project and those requirements must be tracked during execution of the project to ensure the goals of the project are met. Therefore, the focus of this tool is requirements definition. The content of this form is based on International Council on Systems Engineering (INCOSE) and Departmentmore » of Defense (DoD) process standards and allows for single or collaborative input. The “Scoping” section is where project information is entered by the project team prior to requirements development, and includes definitions and examples to assist the user in completing the forms. The data entered will be used to define the requirements and once the form is filled out, a “Requirements List” is automatically generated and a Word document is created and saved to a SharePoint document library. SharePoint also includes the ability to download the requirements data defined in the InfoPath from into an Excel spreadsheet. This User Guide will assist you in navigating through the data entry process.« less

  12. Coal gasification systems engineering and analysis. Appendix A: Coal gasification catalog

    NASA Technical Reports Server (NTRS)

    1980-01-01

    The scope of work in preparing the Coal Gasification Data Catalog included the following subtasks: (1) candidate system subsystem definition, (2) raw materials analysis, (3) market analysis for by-products, (4) alternate products analysis, (5) preliminary integrated facility requirements. Definition of candidate systems/subsystems includes the identity of and alternates for each process unit, raw material requirements, and the cost and design drivers for each process design.

  13. Human Systems Integration (HSI) Practitioner's Guide

    NASA Technical Reports Server (NTRS)

    Zumbado, Jennifer Rochlis

    2015-01-01

    The NASA/SP-2015-3709, Human Systems Integration (HSI) Practitioner's Guide, also known as the "HSIPG," provides a tool for implementing HSI activities within the NASA systems engineering framework. The HSIPG is written to aid the HSI practitioner engaged in a program or project (P/P), and serves as a knowledge base to allow the practitioner to step into an HSI lead or team member role for NASA missions. Additionally, this HSIPG is written to address the role of HSI in the P/P management and systems engineering communities and aid their understanding of the value added by incorporating good HSI practices into their programs and projects. Through helping to build a community of knowledgeable HSI practitioners, this document also hopes to build advocacy across the Agency for establishing strong, consistent HSI policies and practices. Human Systems Integration (HSI) has been successfully adopted (and adapted) by several federal agencies-most notably the U.S. Department of Defense (DoD) and the Nuclear Regulatory Commission (NRC)-as a methodology for reducing system life cycle costs (LCCs). These cost savings manifest themselves due to reductions in required numbers of personnel, the practice of human-centered design, decreased reliance on specialized skills for operations, shortened training time, efficient logistics and maintenance, and fewer safety-related risks and mishaps due to unintended human/system interactions. The HSI process for NASA establishes how cost savings and mission success can be realized through systems engineering. Every program or project has unique attributes. This HSIPG is not intended to provide one-size-fits-all recommendations for HSI implementation. Rather, HSI processes should be tailored to the size, scope, and goals of individual situations. The instructions and processes identified here are best used as a starting point for implementing human-centered system concepts and designs across programs and projects of varying types, including manned and unmanned, human spaceflight, aviation, robotics, and environmental science missions. The practitioner using this guide should have expertise in Systems Engineering or other disciplines involved in producing systems with anticipated human interactions. (See section 1.6 of this guide for further discussion on HSI discipline domains.) The HSIPG provides an "HSI layer" to the NASA Systems Engineering Engine (SEE), detailed in NASA Procedural Requirement (NPR) 7123.1B, NASA Systems Engineering Processes and Requirements, and further explained in NASA/SP-2007-6105, Systems Engineering Handbook (see HSIPG Table 2.2-1, NASA Documents with HSI Content, for specific references and document versions).

  14. Evaluation of scavenging in two-stroke-cycle engines

    NASA Technical Reports Server (NTRS)

    Venediger, Herbert J

    1934-01-01

    The viewpoints are discussed, according to which the scavenging of two-stroke-cycle engines can be evaluated, and the relations between scavenging pressure and the quantity of the scavenging medium required, as also between the scavenging pressure and the revolution speed, are developed. It is further shown that the power increase is limited by the scavenging process, so that further researches are desirable for qualitative improvement. These results lead to several conclusions regarding the propulsion of motor vehicles by the two-stroke-cycle engines. Lastly, attention is called to the fundamental defect of the two-dimensional treatment of the scavenging process and to the consequent distinction between the two-dimensional and three-dimensional scavenging-type efficiency.

  15. University of Colorado CubeSat Student Projects as Successful Model for Teaching Students about Engineering Practices

    NASA Astrophysics Data System (ADS)

    Palo, S. E.; Li, X.; Woods, T. N.; Kohnert, R.

    2014-12-01

    There is a long history of cooperation between students at the University of Colorado, Boulder and professional engineers and scientists at LASP, which has led to many successful space missions with direct student involvement. The recent student-led missions include the Student Nitric Oxide Explorer (SNOE, 1998 - 2002), the Student Dust Counter (SDC) on New Horizons (2006 - present), the Colorado Student Space Weather Experiment (CSSWE), being a very successful NSF CubeSat that launched in September 2012, and the NASA Miniature X-ray Solar Spectrometer (MinXSS) CubeSat (launch will be in early 2015). Students are involved in all aspects of the design, and they experience the full scope of the mission process from concept, to fabrication and test, and mission operations. A significant part of the student involvement in the CubeSat projects is gained by using the CubeSat development as a focal point for an existing two-semester course sequence in CU's Aerospace Engineering Sciences (AES) Department: the Space Hardware Design section of Graduate Projects I & II (ASEN 5018 & ASEN 6028). The goal of these courses is to teach graduate students how to design and build systems using a requirement-based approach and fundamental systems engineering practices. The two-semester sequence takes teams of about 15 students from requirements definition and preliminary design through manufacturing, integration, and testing. In addition to the design process, students learn key professional skills such as working effectively in groups, finding solutions to open-ended problems, and actually building a system to their own set of specifications. The partnership between AES and LASP allows us to include engineering professionals in the mix, thus more effectively training science and engineering students for future roles in the civilian or commercial space industry. The mentoring process with LASP engineers helps to mitigate risk of the inexperience of the students and ensures consistent system engineer oversight for the multi-year CubeSat programs.

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

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

  18. Closing the Gap Between Process Control Theory and Practice

    ERIC Educational Resources Information Center

    Velazquez, Carlos; Cardona-Martinez, Nelson; Velazquez, Edwin

    2010-01-01

    The pressure on world-wide manufacturing industries to meet tougher demands and regulations has forced companies to focus on improving manufacturing using tools like process automation. This focus requires better-prepared students. The process control course of the Department of Chemical Engineering at the University of Puerto Rico at Mayaguez has…

  19. A national collaboration process: Finnish engineering education for the benefit of people and environment.

    PubMed

    Takala, A; Korhonen-Yrjänheikki, K

    2013-12-01

    The key stakeholders of the Finnish engineering education collaborated during 2006-09 to reform the system of education, to face the challenges of the changing business environment and to create a national strategy for the Finnish engineering education. The work process was carried out using participatory work methods. Impacts of sustainable development (SD) on engineering education were analysed in one of the subprojects. In addition to participatory workshops, the core part of the work on SD consisted of a research with more than 60 interviews and an extensive literature survey. This paper discusses the results of the research and the work process of the Collaboration Group in the subproject of SD. It is suggested that enhancing systematic dialogue among key stakeholders using participatory work methods is crucial in increasing motivation and commitment in incorporating SD in engineering education. Development of the context of learning is essential for improving skills of engineering graduates in some of the key abilities related to SD: systemic- and life-cycle thinking, ethical understanding, collaborative learning and critical reflection skills. This requires changing of the educational paradigm from teacher-centred to learner-centred applying problem- and project-oriented active learning methods.

  20. Develop Advanced Nonlinear Signal Analysis Topographical Mapping System

    NASA Technical Reports Server (NTRS)

    Jong, Jen-Yi

    1997-01-01

    During the development of the SSME, a hierarchy of advanced signal analysis techniques for mechanical signature analysis has been developed by NASA and AI Signal Research Inc. (ASRI) to improve the safety and reliability for Space Shuttle operations. These techniques can process and identify intelligent information hidden in a measured signal which is often unidentifiable using conventional signal analysis methods. Currently, due to the highly interactive processing requirements and the volume of dynamic data involved, detailed diagnostic analysis is being performed manually which requires immense man-hours with extensive human interface. To overcome this manual process, NASA implemented this program to develop an Advanced nonlinear signal Analysis Topographical Mapping System (ATMS) to provide automatic/unsupervised engine diagnostic capabilities. The ATMS will utilize a rule-based Clips expert system to supervise a hierarchy of diagnostic signature analysis techniques in the Advanced Signal Analysis Library (ASAL). ASAL will perform automatic signal processing, archiving, and anomaly detection/identification tasks in order to provide an intelligent and fully automated engine diagnostic capability. The ATMS has been successfully developed under this contract. In summary, the program objectives to design, develop, test and conduct performance evaluation for an automated engine diagnostic system have been successfully achieved. Software implementation of the entire ATMS system on MSFC's OISPS computer has been completed. The significance of the ATMS developed under this program is attributed to the fully automated coherence analysis capability for anomaly detection and identification which can greatly enhance the power and reliability of engine diagnostic evaluation. The results have demonstrated that ATMS can significantly save time and man-hours in performing engine test/flight data analysis and performance evaluation of large volumes of dynamic test data.

  1. Re-engineering the Federal planning process: A total Federal planning strategy, integrating NEPA with modern management tools

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

    Eccleston, C.H.

    1997-09-05

    The National Environmental Policy Act (NEPA) of 1969 was established by Congress more than a quarter of a century ago, yet there is a surprising lack of specific tools, techniques, and methodologies for effectively implementing these regulatory requirements. Lack of professionally accepted techniques is a principal factor responsible for many inefficiencies. Often, decision makers do not fully appreciate or capitalize on the true potential which NEPA provides as a platform for planning future actions. New approaches and modem management tools must be adopted to fully achieve NEPA`s mandate. A new strategy, referred to as Total Federal Planning, is proposed formore » unifying large-scale federal planning efforts under a single, systematic, structured, and holistic process. Under this approach, the NEPA planning process provides a unifying framework for integrating all early environmental and nonenvironmental decision-making factors into a single comprehensive planning process. To promote effectiveness and efficiency, modem tools and principles from the disciplines of Value Engineering, Systems Engineering, and Total Quality Management are incorporated. Properly integrated and implemented, these planning tools provide the rigorous, structured, and disciplined framework essential in achieving effective planning. Ultimately, the goal of a Total Federal Planning strategy is to construct a unified and interdisciplinary framework that substantially improves decision-making, while reducing the time, cost, redundancy, and effort necessary to comply with environmental and other planning requirements. At a time when Congress is striving to re-engineer the governmental framework, apparatus, and process, a Total Federal Planning philosophy offers a systematic approach for uniting the disjointed and often convoluted planning process currently used by most federal agencies. Potentially this approach has widespread implications in the way federal planning is approached.« less

  2. 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).

  3. The Effect of Ethanol Addition to Gasoline on Low- and Intermediate-Temperature Heat Release under Boosted Conditions in Kinetically Controlled Engines

    NASA Astrophysics Data System (ADS)

    Vuilleumier, David Malcolm

    The detailed study of chemical kinetics in engines has become required to further advance engine efficiency while simultaneously lowering engine emissions. This push for higher efficiency engines is not caused by a lack of oil, but by efforts to reduce anthropogenic carbon dioxide emissions, that cause global warming. To operate in more efficient manners while reducing traditional pollutant emissions, modern internal combustion piston engines are forced to operate in regimes in which combustion is no longer fully transport limited, and instead is at least partially governed by chemical kinetics of combusting mixtures. Kinetically-controlled combustion allows the operation of piston engines at high compression ratios, with partially-premixed dilute charges; these operating conditions simultaneously provide high thermodynamic efficiency and low pollutant formation. The investigations presented in this dissertation study the effect of ethanol addition on the low-temperature chemistry of gasoline type fuels in engines. These investigations are carried out both in a simplified, fundamental engine experiment, named Homogeneous Charge Compression Ignition, as well as in more applied engine systems, named Gasoline Compression Ignition engines and Partial Fuel Stratification engines. These experimental investigations, and the accompanying modeling work, show that ethanol is an effective scavenger of radicals at low temperatures, and this inhibits the low temperature pathways of gasoline oxidation. Further, the investigations measure the sensitivity of gasoline auto-ignition to system pressure at conditions that are relevant to modern engines. It is shown that at pressures above 40 bar and temperatures below 850 Kelvin, gasoline begins to exhibit Low-Temperature Heat Release. However, the addition of 20% ethanol raises the pressure requirement to 60 bar, while the temperature requirement remains unchanged. These findings have major implications for a range of modern engines. Low-Temperature Heat Release significantly enhances the auto-ignition process, which limits the conditions under which advanced combustion strategies may operate. As these advanced combustion strategies are required to meet emissions and fuel-economy regulations, the findings of this dissertation may benefit and be incorporated into future engine design toolkits, such as detailed chemical kinetic mechanisms.

  4. Specialty Engineering Supplement to IEEE-15288.1

    DTIC Science & Technology

    2015-05-15

    receiver required to work in a dense EMI environment. (15) Any RF receiver with a burnout level of less than 30 dBm (1 mW). b. A summary of all...Context 2.1 ISO-IEC-IEEE-15288: 2015, Systems and Software Engineering — System life cycle processes ISO-IEC-IEEE 15288 is the DOD-adopted standard for...to ISO-15288 for application of systems engineering on defense programs that was developed by a joint services working group under the auspices of the

  5. Military engine computational structures technology

    NASA Technical Reports Server (NTRS)

    Thomson, Daniel E.

    1992-01-01

    Integrated High Performance Turbine Engine Technology Initiative (IHPTET) goals require a strong analytical base. Effective analysis of composite materials is critical to life analysis and structural optimization. Accurate life prediction for all material systems is critical. User friendly systems are also desirable. Post processing of results is very important. The IHPTET goal is to double turbine engine propulsion capability by the year 2003. Fifty percent of the goal will come from advanced materials and structures, the other 50 percent will come from increasing performance. Computer programs are listed.

  6. Corrosion Issues for Ceramics in Gas Turbines

    NASA Technical Reports Server (NTRS)

    Jacobson, Nathan S.; Fox, Dennis S.; Smialek, James L.; Opila, Elizabeth J.; Tortorelli, Peter F.; More, Karren L.; Nickel, Klaus G.; Hirata, Takehiko; Yoshida, Makoto; Yuri, Isao

    2000-01-01

    The requirements for hot-gas-path materials in gas turbine engines are demanding. These materials must maintain high strength and creep resistance in a particularly aggressive environment. A typical gas turbine environment involves high temperatures, rapid gas flow rates, high pressures, and a complex mixture of aggressive gases. Figure 26.1 illustrates the requirements for components of an aircraft engine and critical issues [1]. Currently, heat engines are constructed of metal alloys, which meet these requirements within strict temperature limits. In order to extend these temperature limits, ceramic materials have been considered as potential engine materials, due to their high melting points and stability at high temperatures. These materials include oxides, carbides, borides, and nitrides. Interest in using these materials in engines appears to have begun in the 1940s with BeO-based porcelains [2]. During the 1950s, the efforts shifted to cermets. These were carbide-based materials intended to exploit the best properties of metals and ceramics. During the 1960s and 1970s, the silicon-based ceramics silicon carbide (SiC) and silicon nitride (Si3N4) were extensively developed. Although the desirable high-temperature properties of SiC and Si3N4 had long been known, consolidation of powders into component-sized bodies required the development of a series of specialized processing routes [3]. For SiC, the major consolidation routes are reaction bonding, hot-pressing, and sintering. The use of boron and carbon as additives which enable sintering was a particularly noteworthy advance [4]. For Si3N4 the major consolidation routes are reaction bonding and hot pressing [5]. Reaction-bonding involves nitridation of silicon powder. Hot pressing involves addition of various refractory oxides, such as magnesia (MgO), alumina (Al2O3), and yttria (y2O3). Variations on these processes include a number of routes including Hot Isostatic Pressing (HIP), gas-pressure sintering, sinter-HIPing, and Encapsulation-HIPing. It is important to note that each process involves the addition of secondary elements, which later were shown to dramatically influence oxidation and corrosion behavior. As dense bodies of silicon-based ceramics became more readily available, their desirable high temperature properties were confirmed. These materials retained strength to very high temperatures (i.e. 1300-1400 C). Further, they were lightweight and made from abundant materials. SiC and Si3N4 therefore emerged as leading ceramic candidates for components in heat engines, designed to operate at higher temperatures for better performance and fuel efficiency. The first US programs for ceramics in heat engines have been reviewed [6]. Selected programs on ceramic engine parts are summarized here in regard to their contributions to understanding the corrosion behavior of a heat engine environment.

  7. Gaining the Competitive Edge: Design for Manufacturing

    NASA Technical Reports Server (NTRS)

    Batill, Stephen M.; Pinkelman, Jim; Sellar, Richard

    1993-01-01

    The successful design of a commercial aircraft which is intended to be in direct competition with existing aircraft requires a market analysis to establish design requirements, the development of a concept to achieve those goals. and the ability to economically manufacture the aircraft. It is often the case that an engineer designs system components with only the perspective of a particular discipline. The relationship of that component to the entire system is often a minor consideration. In an effort to highlight the interaction that is necessary during the design process, the students were organized into design/build teams and required to integrate aspects of market analysis, engineering design, production and economics into their concepts. In order to facilitate this process a hypothetical "Aeroworld" was established. Having been furnished relevant demographic and economic data for "Aeroworld". students were given the task of designing and building an aircraft for a specific market while achieving an economically competitive design. Involvement of the team in the evolution of the design from market definition to technical development to manufacturing allowed the students to identify critical issues in the design process and to encounter many of the conflicting requirements which arise in an aerospace systems design.

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

  9. The Power of Imaging.

    ERIC Educational Resources Information Center

    Haapaniemi, Peter

    1990-01-01

    Describes imaging technology, which allows huge numbers of words and illustrations to be reduced to tiny fraction of space required by originals and discusses current applications. Highlights include image processing system at National Archives; use by banks for high-speed check processing; engineering document management systems (EDMS); folder…

  10. The FoReVer Methodology: A MBSE Framework for Formal Verification

    NASA Astrophysics Data System (ADS)

    Baracchi, Laura; Mazzini, Silvia; Cimatti, Alessandro; Tonetta, Stefano; Garcia, Gerald

    2013-08-01

    The need for high level of confidence and operational integrity in critical space (software) systems is well recognized in the Space industry and has been addressed so far through rigorous System and Software Development Processes and stringent Verification and Validation regimes. The Model Based Space System Engineering process (MBSSE) derived in the System and Software Functional Requirement Techniques study (SSFRT) focused on the application of model based engineering technologies to support the space system and software development processes, from mission level requirements to software implementation through model refinements and translations. In this paper we report on our work in the ESA-funded FoReVer project where we aim at developing methodological, theoretical and technological support for a systematic approach to the space avionics system development, in phases 0/A/B/C. FoReVer enriches the MBSSE process with contract-based formal verification of properties, at different stages from system to software, through a step-wise refinement approach, with the support for a Software Reference Architecture.

  11. Ceramic technology for advanced heat engines project. Semiannual progress report, October 1985-March 1986

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

    Not Available

    1986-08-01

    Significant accomplishments in fabricating cermaic components for the Department of Energy (DOE), National Aeronautics and Space Administration (NASA), and Department of Defense (DOD) advanced heat engine programs have provided evidence that the operation of ceramic parts in high-temperature engine environments is feasible. However, additional research is needed in materials and processing development, design methodology, and data base and life prediction. An assessment of needs was completed, and a five-year project plan was developed with extensive input from private industry. The objective of the project is to develop the industrial technology base required for reliable ceramics for application in advanced automotivemore » heat engines. The project approach includes determining the mechanisms controlling reliability, improving processes for fabricating existing ceramics, developing new materials with increased reliability, and testing these materials in simulated engine environments to confirm reliability. although this is a generic materials project, the focus is on structural ceramics for advanced gas turbine and diesel engines, ceramic bearings and attachments, and ceramic coatings for thermal barrier and wear applications in these engines.« less

  12. A Simple Interactive Introduction to Teaching Genetic Engineering

    ERIC Educational Resources Information Center

    Child, Paula

    2013-01-01

    In the UK, at key stage 4, students aged 14-15 studying GCSE Core Science or Unit 1 of the GCSE Biology course are required to be able to describe the process of genetic engineering to produce bacteria that can produce insulin. The simple interactive introduction described in this article allows students to consider the problem, devise a model and…

  13. Supporting Educational Games in Higher Education: The Creation and Implementation of Custom Game Engine for a University

    ERIC Educational Resources Information Center

    Choi, Gi Woong; Pursel, Barton K.; Stubbs, Chris

    2017-01-01

    Interest towards implementing educational gaming into courses within higher education continues to increase, but it requires extensive amounts of resources to create individual games for each course. This paper is a description of a university's effort to create a custom educational game engine to streamline the game development process within the…

  14. Employability of Graduates--A Search through the Educational Processes of Indian Engineering Institutions

    ERIC Educational Resources Information Center

    Viswanadhan, K. G.

    2008-01-01

    There is a big boom in manpower requirements in IT industries in India in recent years. Presently India is aiming at becoming the major source of manpower in IT and other technical fields in the global scenario. To achieve this target, enhancement of employability of graduates coming out of engineering colleges are very important. A study has been…

  15. 640 x 480 PtSi infrared engine

    NASA Astrophysics Data System (ADS)

    Lang, Frank B.; Coyle, Peter J.; Stabile, Paul J.; Tower, John R.; Zubalsky, I.; Ornstein, Itzhak

    1996-06-01

    The design and performance of a compact, light-weight, low power infrared engine is presented. The 3 - 5 micron MWIR imaging subsystem consists of a Stirling-cooled, 640 (H) by 480 (V) staring PtSi infrared focal plane array (IRFPA) with associated drive and analog video processing electronics. The IR engine provides user-selectable integration time control. This infrared imaging subsystem is designed to be gimbal-mounted, and has been qualified to be operated in minus 10 Celsius to plus 50 Celsius environments. The infrared engine is also designed to meet the requirements of demanding shock and vibration environments.

  16. V&V Plan for FPGA-based ESF-CCS Using System Engineering Approach.

    NASA Astrophysics Data System (ADS)

    Maerani, Restu; Mayaka, Joyce; El Akrat, Mohamed; Cheon, Jung Jae

    2018-02-01

    Instrumentation and Control (I&C) systems play an important role in maintaining the safety of Nuclear Power Plant (NPP) operation. However, most current I&C safety systems are based on Programmable Logic Controller (PLC) hardware, which is difficult to verify and validate, and is susceptible to software common cause failure. Therefore, a plan for the replacement of the PLC-based safety systems, such as the Engineered Safety Feature - Component Control System (ESF-CCS), with Field Programmable Gate Arrays (FPGA) is needed. By using a systems engineering approach, which ensures traceability in every phase of the life cycle, from system requirements, design implementation to verification and validation, the system development is guaranteed to be in line with the regulatory requirements. The Verification process will ensure that the customer and stakeholder’s needs are satisfied in a high quality, trustworthy, cost efficient and schedule compliant manner throughout a system’s entire life cycle. The benefit of the V&V plan is to ensure that the FPGA based ESF-CCS is correctly built, and to ensure that the measurement of performance indicators has positive feedback that “do we do the right thing” during the re-engineering process of the FPGA based ESF-CCS.

  17. A Tailored Concept of Operations for NASA LSP Integrated Operations

    NASA Technical Reports Server (NTRS)

    Owens, Clark V.

    2016-01-01

    An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this project is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services.

  18. A Global Assessment of Stem Cell Engineering

    PubMed Central

    Loring, Jeanne F.; McDevitt, Todd C.; Palecek, Sean P.; Schaffer, David V.; Zandstra, Peter W.

    2014-01-01

    Over the last 2 years a global assessment of stem cell engineering (SCE) was conducted with the sponsorship of the National Science Foundation, the National Cancer Institute at the National Institutes of Health, and the National Institute of Standards and Technology. The purpose was to gather information on the worldwide status and trends in SCE, that is, the involvement of engineers and engineering approaches in the stem cell field, both in basic research and in the translation of research into clinical applications and commercial products. The study was facilitated and managed by the World Technology Evaluation Center. The process involved site visits in both Asia and Europe, and it also included several different workshops. From this assessment, the panel concluded that there needs to be an increased role for engineers and the engineering approach. This will provide a foundation for the generation of new markets and future economic growth. To do this will require an increased investment in engineering, applied research, and commercialization as it relates to stem cell research and technology. It also will require programs that support interdisciplinary teams, new innovative mechanisms for academic–industry partnerships, and unique translational models. In addition, the global community would benefit from forming strategic partnerships between countries that can leverage existing and emerging strengths in different institutions. To implement such partnerships will require multinational grant programs with appropriate review mechanisms. PMID:24428577

  19. A global assessment of stem cell engineering.

    PubMed

    Loring, Jeanne F; McDevitt, Todd C; Palecek, Sean P; Schaffer, David V; Zandstra, Peter W; Nerem, Robert M

    2014-10-01

    Over the last 2 years a global assessment of stem cell engineering (SCE) was conducted with the sponsorship of the National Science Foundation, the National Cancer Institute at the National Institutes of Health, and the National Institute of Standards and Technology. The purpose was to gather information on the worldwide status and trends in SCE, that is, the involvement of engineers and engineering approaches in the stem cell field, both in basic research and in the translation of research into clinical applications and commercial products. The study was facilitated and managed by the World Technology Evaluation Center. The process involved site visits in both Asia and Europe, and it also included several different workshops. From this assessment, the panel concluded that there needs to be an increased role for engineers and the engineering approach. This will provide a foundation for the generation of new markets and future economic growth. To do this will require an increased investment in engineering, applied research, and commercialization as it relates to stem cell research and technology. It also will require programs that support interdisciplinary teams, new innovative mechanisms for academic-industry partnerships, and unique translational models. In addition, the global community would benefit from forming strategic partnerships between countries that can leverage existing and emerging strengths in different institutions. To implement such partnerships will require multinational grant programs with appropriate review mechanisms.

  20. Design and analysis of lifting tool assemblies to lift different engine block

    NASA Astrophysics Data System (ADS)

    Sawant, Arpana; Deshmukh, Nilaj N.; Chauhan, Santosh; Dabhadkar, Mandar; Deore, Rupali

    2017-07-01

    Engines block are required to be lifted from one place to another while they are being processed. The human effort required for this purpose is more and also the engine block may get damaged if it is not handled properly. There is a need for designing a proper lifting tool which will be able to conveniently lift the engine block and place it at the desired position without any accident and damage to the engine block. In the present study lifting tool assemblies are designed and analyzed in such way that it may lift different categories of engine blocks. The lifting tool assembly consists of lifting plate, lifting ring, cap screws and washers. A parametric model and assembly of Lifting tool is done in 3D modelling software CREO 2.0 and analysis is carried out in ANSYS Workbench 16.0. A test block of weight equivalent to that of an engine block is considered for the purpose of analysis. In the preliminary study, without washer the stresses obtained on the lifting tool were more than the safety margin. In the present design, washers were used with appropriate dimensions which helps to bring down the stresses on the lifting tool within the safety margin. Analysis is carried out to verify that tool design meets the ASME BTH-1 required safety margin.

  1. Space Shuttle Main Engine - The Relentless Pursuit of Improvement

    NASA Technical Reports Server (NTRS)

    VanHooser, Katherine P.; Bradley, Douglas P.

    2011-01-01

    The Space Shuttle Main Engine (SSME) is the only reusable large liquid rocket engine ever developed. The specific impulse delivered by the staged combustion cycle, substantially higher than previous rocket engines, minimized volume and weight for the integrated vehicle. The dual pre-burner configuration permitted precise mixture ratio and thrust control while the fully redundant controller and avionics provided a very high degree of system reliability and health diagnosis. The main engine controller design was the first rocket engine application to incorporate digital processing. The engine was required to operate at a high chamber pressure to minimize engine volume and weight. Power level throttling was required to minimize structural loads on the vehicle early in flight and acceleration levels on the crew late in ascent. Fatigue capability, strength, ease of assembly and disassembly, inspectability, and materials compatibility were all major considerations in achieving a fully reusable design. During the multi-decade program the design evolved substantially using a series of block upgrades. A number of materials and manufacturing challenges were encountered throughout SSME s history. Significant development was required for the final configuration of the high pressure turbopumps. Fracture control was implemented to assess life limits of critical materials and components. Survival in the hydrogen environment required assessment of hydrogen embrittlement. Instrumentation systems were a challenge due to the harsh thermal and dynamic environments within the engine. Extensive inspection procedures were developed to assess the engine components between flights. The Space Shuttle Main Engine achieved a remarkable flight performance record. All flights were successful with only one mission requiring an ascent abort condition, which still resulted in an acceptable orbit and mission. This was achieved in large part via extensive ground testing to fully characterize performance and to establish acceptable life limits. During the program over a million seconds of accumulated test and flight time was achieved. Post flight inspection and assessment was a key part of assuring proper performance of the flight hardware. By the end of the program the predicted reliability had improved by a factor of four. These unique challenges, evolution of the design, and the resulting reliability will be discussed in this paper.

  2. Update on Risk Reduction Activities for a Liquid Advanced Booster for NASA's Space Launch System

    NASA Technical Reports Server (NTRS)

    Crocker, Andrew M.; Doering, Kimberly B; Meadows, Robert G.; Lariviere, Brian W.; Graham, Jerry B.

    2015-01-01

    The stated goals of NASA's Research Announcement for the Space Launch System (SLS) Advanced Booster Engineering Demonstration and/or Risk Reduction (ABEDRR) are to reduce risks leading to an affordable Advanced Booster that meets the evolved capabilities of SLS; and enable competition by mitigating targeted Advanced Booster risks to enhance SLS affordability. Dynetics, Inc. and Aerojet Rocketdyne (AR) formed a team to offer a wide-ranging set of risk reduction activities and full-scale, system-level demonstrations that support NASA's ABEDRR goals. For NASA's SLS ABEDRR procurement, Dynetics and AR formed a team to offer a series of full-scale risk mitigation hardware demonstrations for an affordable booster approach that meets the evolved capabilities of the SLS. To establish a basis for the risk reduction activities, the Dynetics Team developed a booster design that takes advantage of the flight-proven Apollo-Saturn F-1. Using NASA's vehicle assumptions for the SLS Block 2, a two-engine, F-1-based booster design delivers 150 mT (331 klbm) payload to LEO, 20 mT (44 klbm) above NASA's requirements. This enables a low-cost, robust approach to structural design. During the ABEDRR effort, the Dynetics Team has modified proven Apollo-Saturn components and subsystems to improve affordability and reliability (e.g., reduce parts counts, touch labor, or use lower cost manufacturing processes and materials). The team has built hardware to validate production costs and completed tests to demonstrate it can meet performance requirements. State-of-the-art manufacturing and processing techniques have been applied to the heritage F-1, resulting in a low recurring cost engine while retaining the benefits of Apollo-era experience. NASA test facilities have been used to perform low-cost risk-reduction engine testing. In early 2014, NASA and the Dynetics Team agreed to move additional large liquid oxygen/kerosene engine work under Dynetics' ABEDRR contract. Also led by AR, the objectives of this work are to demonstrate combustion stability and measure performance of a 500,000 lbf class Oxidizer-Rich Staged Combustion (ORSC) cycle main injector. A trade study was completed to investigate the feasibility, cost effectiveness, and technical maturity of a domestically produced Atlas V engine that could also potentially satisfy NASA SLS payload-to-orbit requirements via an advanced booster application. Engine physical dimensions and performance parameters resulting from this study provide the system level requirements for the ORSC risk reduction test article. The test article is scheduled to complete critical design review this fall and begin testing in 2017. Dynetics has also designed, developed, and built innovative tank and structure assemblies using friction stir welding to leverage recent NASA investments in manufacturing tools, facilities, and processes, significantly reducing development and recurring costs. The full-scale cryotank assembly was used to verify the structural design and prove affordable processes. Dynetics performed hydrostatic and cryothermal proof tests on the assembly to verify the assembly meets performance requirements. This paper will discuss the ABEDRR engine task and structures task achievements to date and the remaining effort through the end of the contract.

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

  4. Ranking protective coatings: Laboratory vs. field experience

    NASA Astrophysics Data System (ADS)

    Conner, Jeffrey A.; Connor, William B.

    1994-12-01

    Environmentally protective coatings are used on a wide range of gas turbine components for survival in the harsh operating conditions of engines. A host of coatings are commercially available to protect hot-section components, ranging from simple aluminides to designer metallic overlays and ceramic thermal barrier coatings. A variety of coating-application processes are available, and they range from simple pack cementation processing to complex physical vapor deposition, which requires multimillion dollar facilities. Detailed databases are available for most coatings and coating/process combinations for a range of laboratory tests. Still, the analysis of components actually used in engines often yields surprises when compared against predicted coating behavior from laboratory testing. This paper highlights recent work to develop new laboratory tests that better simulate engine environments. Comparison of in-flight coating performance as well as industrial and factory engine testing on a range of hardware is presented along with laboratory predictions from standard testing and from recently developed cyclic burner-rig testing.

  5. Effects of process parameters in plastic, metal, and ceramic injection molding processes

    NASA Astrophysics Data System (ADS)

    Lee, Shi W.; Ahn, Seokyoung; Whang, Chul Jin; Park, Seong Jin; Atre, Sundar V.; Kim, Jookwon; German, Randall M.

    2011-09-01

    Plastic injection molding has been widely used in the past and is a dominant forming approach today. As the customer demands require materials with better engineering properties that were not feasible with polymers, powder injection molding with metal and ceramic powders has received considerable attention in recent decades. To better understand the differences in the plastic injection molding, metal injection molding, and ceramic injection molding, the effects of the core process parameters on the process performances has been studied using the state-of-the-art computer-aided engineering (CAE) design tool, PIMSolver® The design of experiments has been conducted using the Taguchi method to obtain the relative contributions of various process parameters onto the successful operations.

  6. Software Safety Risk in Legacy Safety-Critical Computer Systems

    NASA Technical Reports Server (NTRS)

    Hill, Janice L.; Baggs, Rhoda

    2007-01-01

    Safety Standards contain technical and process-oriented safety requirements. Technical requirements are those such as "must work" and "must not work" functions in the system. Process-Oriented requirements are software engineering and safety management process requirements. Address the system perspective and some cover just software in the system > NASA-STD-8719.13B Software Safety Standard is the current standard of interest. NASA programs/projects will have their own set of safety requirements derived from the standard. Safety Cases: a) Documented demonstration that a system complies with the specified safety requirements. b) Evidence is gathered on the integrity of the system and put forward as an argued case. [Gardener (ed.)] c) Problems occur when trying to meet safety standards, and thus make retrospective safety cases, in legacy safety-critical computer systems.

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

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

  9. Applying formal methods and object-oriented analysis to existing flight software

    NASA Technical Reports Server (NTRS)

    Cheng, Betty H. C.; Auernheimer, Brent

    1993-01-01

    Correctness is paramount for safety-critical software control systems. Critical software failures in medical radiation treatment, communications, and defense are familiar to the public. The significant quantity of software malfunctions regularly reported to the software engineering community, the laws concerning liability, and a recent NRC Aeronautics and Space Engineering Board report additionally motivate the use of error-reducing and defect detection software development techniques. The benefits of formal methods in requirements driven software development ('forward engineering') is well documented. One advantage of rigorously engineering software is that formal notations are precise, verifiable, and facilitate automated processing. This paper describes the application of formal methods to reverse engineering, where formal specifications are developed for a portion of the shuttle on-orbit digital autopilot (DAP). Three objectives of the project were to: demonstrate the use of formal methods on a shuttle application, facilitate the incorporation and validation of new requirements for the system, and verify the safety-critical properties to be exhibited by the software.

  10. Numerical Propulsion System Simulation: An Overview

    NASA Technical Reports Server (NTRS)

    Lytle, John K.

    2000-01-01

    The cost of implementing new technology in aerospace propulsion systems is becoming prohibitively expensive and time consuming. One of the main contributors to the high cost and lengthy time is the need to perform many large-scale hardware tests and the inability to integrate all appropriate subsystems early in the design process. The NASA Glenn Research Center is developing the technologies required to enable simulations of full aerospace propulsion systems in sufficient detail to resolve critical design issues early in the design process before hardware is built. This concept, called the Numerical Propulsion System Simulation (NPSS), is focused on the integration of multiple disciplines such as aerodynamics, structures and heat transfer with computing and communication technologies to capture complex physical processes in a timely and cost-effective manner. The vision for NPSS, as illustrated, is to be a "numerical test cell" that enables full engine simulation overnight on cost-effective computing platforms. There are several key elements within NPSS that are required to achieve this capability: 1) clear data interfaces through the development and/or use of data exchange standards, 2) modular and flexible program construction through the use of object-oriented programming, 3) integrated multiple fidelity analysis (zooming) techniques that capture the appropriate physics at the appropriate fidelity for the engine systems, 4) multidisciplinary coupling techniques and finally 5) high performance parallel and distributed computing. The current state of development in these five area focuses on air breathing gas turbine engines and is reported in this paper. However, many of the technologies are generic and can be readily applied to rocket based systems and combined cycles currently being considered for low-cost access-to-space applications. Recent accomplishments include: (1) the development of an industry-standard engine cycle analysis program and plug 'n play architecture, called NPSS Version 1, (2) A full engine simulation that combines a 3D low-pressure subsystem with a 0D high pressure core simulation. This demonstrates the ability to integrate analyses at different levels of detail and to aerodynamically couple components, the fan/booster and low-pressure turbine, through a 3D computational fluid dynamics simulation. (3) Simulation of all of the turbomachinery in a modern turbofan engine on parallel computing platform for rapid and cost-effective execution. This capability can also be used to generate full compressor map, requiring both design and off-design simulation. (4) Three levels of coupling characterize the multidisciplinary analysis under NPSS: loosely coupled, process coupled and tightly coupled. The loosely coupled and process coupled approaches require a common geometry definition to link CAD to analysis tools. The tightly coupled approach is currently validating the use of arbitrary Lagrangian/Eulerian formulation for rotating turbomachinery. The validation includes both centrifugal and axial compression systems. The results of the validation will be reported in the paper. (5) The demonstration of significant computing cost/performance reduction for turbine engine applications using PC clusters. The NPSS Project is supported under the NASA High Performance Computing and Communications Program.

  11. The Vehicle Integrated Performance Analysis Experience: Reconnecting With Technical Integration

    NASA Technical Reports Server (NTRS)

    McGhee, D. S.

    2006-01-01

    Very early in the Space Launch Initiative program, a small team of engineers at MSFC proposed a process for performing system-level assessments of a launch vehicle. Aimed primarily at providing insight and making NASA a smart buyer, the Vehicle Integrated Performance Analysis (VIPA) team was created. The difference between the VIPA effort and previous integration attempts is that VIPA a process using experienced people from various disciplines, which focuses them on a technically integrated assessment. The foundations of VIPA s process are described. The VIPA team also recognized the need to target early detailed analysis toward identifying significant systems issues. This process is driven by the T-model for technical integration. VIPA s approach to performing system-level technical integration is discussed in detail. The VIPA process significantly enhances the development and monitoring of realizable project requirements. VIPA s assessment validates the concept s stated performance, identifies significant issues either with the concept or the requirements, and then reintegrates these issues to determine impacts. This process is discussed along with a description of how it may be integrated into a program s insight and review process. The VIPA process has gained favor with both engineering and project organizations for being responsive and insightful

  12. Medical device development.

    PubMed

    Panescu, Dorin

    2009-01-01

    The development of a successful medical product requires not only engineering design efforts, but also clinical, regulatory, marketing and business expertise. This paper reviews items related to the process of designing medical devices. It discusses the steps required to take a medical product idea from concept, through development, verification and validation, regulatory approvals and market release.

  13. Integrating interface slicing into software engineering processes

    NASA Technical Reports Server (NTRS)

    Beck, Jon

    1993-01-01

    Interface slicing is a tool which was developed to facilitate software engineering. As previously presented, it was described in terms of its techniques and mechanisms. The integration of interface slicing into specific software engineering activities is considered by discussing a number of potential applications of interface slicing. The applications discussed specifically address the problems, issues, or concerns raised in a previous project. Because a complete interface slicer is still under development, these applications must be phrased in future tenses. Nonetheless, the interface slicing techniques which were presented can be implemented using current compiler and static analysis technology. Whether implemented as a standalone tool or as a module in an integrated development or reverse engineering environment, they require analysis no more complex than that required for current system development environments. By contrast, conventional slicing is a methodology which, while showing much promise and intuitive appeal, has yet to be fully implemented in a production language environment despite 12 years of development.

  14. Turbomachinery Course

    NASA Technical Reports Server (NTRS)

    Stinson, Henry; Turner, James (Technical Monitor)

    2002-01-01

    In this viewgraph presentation, information and diagrams are provided on rocket engine turbopumps. These turbomachines are highly complex and have several unique features: (1) They are generally very high power density machines; (2) They experience high fluid dynamic loads; (3) They are exposed to severe thermal shocks in terms of rapid starts and stops and extremely high heat transfer coefficients; (4) They have stringent suction performance requirements to minimize tank weight; (5) Their working fluids significantly impact the design: oxidizers are generally explosive, they afford almost no lubrication for bearings and seals, some fuels can degrade material properties, cryogenics result in severe thermal gradients; (6) Their life requirements are short relative to other turbomachines in that there are hundreds of cycles and a few hours of operation for reusable systems. The design of rocket engine turbomachines is a systems engineering challenge because multiple engineering disciplines must be integrated to deal with issues pertaining to stress, structural dynamics, hydrodynamics, aerodynamics, thermodynamics, and materials and process selection.

  15. Breadboard RL10-2B low-thrust operating mode (second iteration) test report

    NASA Technical Reports Server (NTRS)

    Kanic, Paul G.; Kaldor, Raymond B.; Watkins, Pia M.

    1988-01-01

    Cryogenic rocket engines requiring a cooling process to thermally condition the engine to operating temperature can be made more efficient if cooling propellants can be burned. Tank head idle and pumped idle modes can be used to burn propellants employed for cooling, thereby providing useful thrust. Such idle modes required the use of a heat exchanger to vaporize oxygen prior to injection into the combustion chamber. During December 1988, Pratt and Whitney conducted a series of engine hot firing demonstrating the operation of two new, previously untested oxidizer heat exchanger designs. The program was a second iteration of previous low thrust testing conducted in 1984, during which a first-generation heat exchanger design was used. Although operation was demonstrated at tank head idle and pumped idle, the engine experienced instability when propellants could not be supplied to the heat exchanger at design conditions.

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

  17. Fastrac Nozzle Design, Performance and Development

    NASA Technical Reports Server (NTRS)

    Peters, Warren; Rogers, Pat; Lawrence, Tim; Davis, Darrell; DAgostino, Mark; Brown, Andy

    2000-01-01

    With the goal of lowering the cost of payload to orbit, NASA/MSFC (Marshall Space Flight Center) researched ways to decrease the complexity and cost of an engine system and its components for a small two-stage booster vehicle. The composite nozzle for this Fastrac Engine was designed, built and tested by MSFC with fabrication support and engineering from Thiokol-SEHO (Science and Engineering Huntsville Operation). The Fastrac nozzle uses materials, fabrication processes and design features that are inexpensive, simple and easily manufactured. As the low cost nozzle (and injector) design matured through the subscale tests and into full scale hot fire testing, X-34 chose the Fastrac engine for the propulsion plant for the X-34. Modifications were made to nozzle design in order to meet the new flight requirements. The nozzle design has evolved through subscale testing and manufacturing demonstrations to full CFD (Computational Fluid Dynamics), thermal, thermomechanical and dynamic analysis and the required component and engine system tests to validate the design. The Fastrac nozzle is now in final development hot fire testing and has successfully accumulated 66 hot fire tests and 1804 seconds on 18 different nozzles.

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

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

  20. Adoption of Requirements Engineering Practices in Malaysian Software Development Companies

    NASA Astrophysics Data System (ADS)

    Solemon, Badariah; Sahibuddin, Shamsul; Ghani, Abdul Azim Abd

    This paper presents exploratory survey results on Requirements Engineering (RE) practices of some software development companies in Malaysia. The survey attempted to identify patterns of RE practices the companies are implementing. Information required for the survey was obtained through a survey, mailed self-administered questionnaires distributed to project managers and software developers who are working at software development companies operated across the country. The results showed that the overall adoption of the RE practices in these companies is strong. However, the results also indicated that fewer companies in the survey have use appropriate CASE tools or software to support their RE process and practices, define traceability policies and maintain traceability manual in their projects.

  1. Key issues in the thermal design of spaceborne cryogenic infrared instruments

    NASA Astrophysics Data System (ADS)

    Schember, Helene R.; Rapp, Donald

    1992-12-01

    Thermal design and analysis play an integral role in the development of spaceborne cryogenic infrared (IR) instruments. From conceptual sketches to final testing, both direct and derived thermal requirements place significant constraints on the instrument design. Although in practice these thermal requirements are interdependent, the sources of most thermal constraints may be grouped into six distinct categories. These are: (1) Detector temperatures, (2) Optics temperatures, (3) Pointing or alignment stability, (4) Mission lifetime, (5) Orbit, and (6) Test and Integration. In this paper, we discuss these six sources of thermal requirements with particular regard to development of instrument packages for low background infrared astronomical observatories. In the end, the thermal performance of these instruments must meet a set of thermal requirements. The development of these requirements is typically an ongoing and interactive process, however, and the thermal design must maintain flexibility and robustness throughout the process. The thermal (or cryogenic) engineer must understand the constraints imposed by the science requirements, the specific hardware, the observing environment, the mission design, and the testing program. By balancing these often competing factors, the system-oriented thermal engineer can work together with the experiment team to produce an effective overall design of the instrument.

  2. RT-25: Requirements Management for Net-Centric Enterprises. Phase 1

    DTIC Science & Technology

    2011-04-28

    software systems. These include Business Process Modeling Notation ( BPMN ) (White and Miers 2008) and Business Process Execution Language (BPEL) (Sarang...Engineering with SysML/UML: Modeling, Analysis, Design, Morgan Kaufmann/The OMG Press. White, S. A. and D. Miers (2008). BPMN Modeling and Reference

  3. Environmental Testing of the NEXT PM1R Ion Engine

    NASA Technical Reports Server (NTRS)

    Snyder, John S.; Anderson, John R.; VanNoord, Jonathan L.; Soulas, George C.

    2007-01-01

    The NEXT propulsion system is an advanced ion propulsion system presently under development that is oriented towards robotic exploration of the solar system using solar electric power. The subsystem includes an ion engine, power processing unit, feed system components, and thruster gimbal. The Prototype Model engine PM1 was subjected to qualification-level environmental testing in 2006 to demonstrate compatibility with environments representative of anticipated mission requirements. Although the testing was largely successful, several issues were identified including the fragmentation of potting cement on the discharge and neutralizer cathode heater terminations during vibration which led to abbreviated thermal testing, and generation of particulate contamination from manufacturing processes and engine materials. The engine was reworked to address most of these findings, renamed PM1R, and the environmental test sequence was repeated. Thruster functional testing was performed before and after the vibration and thermal-vacuum tests. Random vibration testing, conducted with the thruster mated to the breadboard gimbal, was executed at 10.0 Grms for 2 min in each of three axes. Thermal-vacuum testing included three thermal cycles from 120 to 215 C with hot engine re-starts. Thruster performance was nominal throughout the test program, with minor variations in a few engine operating parameters likely caused by facility effects. There were no significant changes in engine performance as characterized by engine operating parameters, ion optics performance measurements, and beam current density measurements, indicating no significant changes to the hardware as a result of the environmental testing. The NEXT PM1R engine and the breadboard gimbal were found to be well-designed against environmental requirements based on the results reported herein. The redesigned cathode heater terminations successfully survived the vibration environments. Based on the results of this test program and confidence in the engineering solutions available for the remaining findings of the first test program, specifically the particulate contamination, the hardware environmental qualification program can proceed with confidence

  4. MODIS. Volume 1: MODIS level 1A software baseline requirements

    NASA Technical Reports Server (NTRS)

    Masuoka, Edward; Fleig, Albert; Ardanuy, Philip; Goff, Thomas; Carpenter, Lloyd; Solomon, Carl; Storey, James

    1994-01-01

    This document describes the level 1A software requirements for the moderate resolution imaging spectroradiometer (MODIS) instrument. This includes internal and external requirements. Internal requirements include functional, operational, and data processing as well as performance, quality, safety, and security engineering requirements. External requirements include those imposed by data archive and distribution systems (DADS); scheduling, control, monitoring, and accounting (SCMA); product management (PM) system; MODIS log; and product generation system (PGS). Implementation constraints and requirements for adapting the software to the physical environment are also included.

  5. Facility siting as a decision process at the Savannah River Site

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

    Wike, L.D.

    1995-12-31

    Site selection for new facilities at Savannah River Site (SRS) historically has been a process dependent only upon specific requirements of the facility. While this approach is normally well suited to engineering and operational concerns, it can have serious deficiencies in the modern era of regulatory oversight and compliance requirements. There are many issues related to the site selection for a facility that are not directly related to engineering or operational requirements; such environmental concerns can cause large schedule delays and budget impact,s thereby slowing or stopping the progress of a project. Some of the many concerns in locating amore » facility include: waste site avoidance, National Environmental Policy Act requirements, Clean Water Act, Clean Air Act, wetlands conservation, US Army Corps of Engineers considerations, US Fish and Wildlife Service statutes including threatened and endangered species issues, and State of South Carolina regulations, especially those of the Department of Health and Environmental Control. In addition, there are SRS restrictions on research areas set aside for National Environmental Research Park (NERP), Savannah River Ecology Laboratory, Savannah River Forest Station, University of South Carolina Institute of Archaeology and Anthropology, Southeastern Forest Experimental Station, and Savannah River Technology Center (SRTC) programs. As with facility operational needs, all of these siting considerations do not have equal importance. The purpose of this document is to review recent site selection exercises conducted for a variety of proposed facilities, develop the logic and basis for the methods employed, and standardize the process and terminology for future site selection efforts.« less

  6. A History of Welding on the Space Shuttle Main Engine (1975 to 2010)

    NASA Technical Reports Server (NTRS)

    Zimmerman, Frank R.; Russell, Carolyn K.

    2010-01-01

    The Space Shuttle Main Engine (SSME) is a high performance, throttleable, liquid hydrogen fueled rocket engine. High thrust and specific impulse (Isp) are achieved through a staged combustion engine cycle, combined with high combustion pressure (approx.3000psi) generated by the two-stage pump and combustion process. The SSME is continuously throttleable from 67% to 109% of design thrust level. The design criteria for this engine maximize performance and weight, resulting in a 7,800 pound rocket engine that produces over a half million pounds of thrust in vacuum with a specific impulse of 452/sec. It is the most reliable rocket engine in the world, accumulating over one million seconds of hot-fire time and achieving 100% flight success in the Space Shuttle program. A rocket engine with the unique combination of high reliability, performance, and reusability comes at the expense of manufacturing simplicity. Several innovative design features and fabrication techniques are unique to this engine. This is as true for welding as any other manufacturing process. For many of the weld joints it seemed mean cheating physics and metallurgy to meet the requirements. This paper will present a history of the welding used to produce the world s highest performance throttleable rocket engine.

  7. 40 CFR 63.1427 - Process vent requirements for processes using extended cookout as an epoxide emission reduction...

    Code of Federal Regulations, 2014 CFR

    2014-07-01

    ... = Concentration of epoxide in the reactor liquid at the beginning of the time period, weight percent. k = Reaction rate constant, 1/hr. t = Time, hours. Note: This equation assumes a first order reaction with respect... process knowledge, reaction kinetics, and engineering knowledge, in accordance with paragraph (a)(2)(i) of...

  8. 40 CFR 63.1427 - Process vent requirements for processes using extended cookout as an epoxide emission reduction...

    Code of Federal Regulations, 2013 CFR

    2013-07-01

    ... = Concentration of epoxide in the reactor liquid at the beginning of the time period, weight percent. k = Reaction rate constant, 1/hr. t = Time, hours. Note: This equation assumes a first order reaction with respect... process knowledge, reaction kinetics, and engineering knowledge, in accordance with paragraph (a)(2)(i) of...

  9. Conceptual design of modular fixture for frame welding and drilling process integration case study: Student chair in UNS industrial engineering integrated practicum

    NASA Astrophysics Data System (ADS)

    Darmawan, Tofiq Dwiki; Priadythama, Ilham; Herdiman, Lobes

    2018-02-01

    Welding and drilling are main processes of making chair frame from metal material. Commonly, chair frame construction includes many arcs which bring difficulties for its welding and drilling process. In UNS industrial engineering integrated practicum there are welding fixtures which use to fixing frame component position for welding purpose. In order to achieve exact holes position for assembling purpose, manual drilling processes were conducted after the frame was joined. Unfortunately, after it was welded the frame material become hard and increase drilling tools wear rate as well as reduce holes position accuracy. The previous welding fixture was not equipped with clamping system and cannot accommodate drilling process. To solve this problem, our idea is to reorder the drilling process so that it can be execute before welding. Thus, this research aims to propose conceptual design of modular fixture which can integrate welding and drilling process. We used Generic Product Development Process to address the design concept. We collected design requirements from 3 source, jig and fixture theoretical concepts, user requirements, and clamping part standards. From 2 alternatives fixture tables, we propose the first which equipped with mounting slots instead of holes. We test the concept by building a full sized prototype and test its works by conducting welding and drilling of a student chair frame. Result from the welding and drilling trials showed that the holes are on precise position after welding. Based on this result, we conclude that the concept can be a consideration for application in UNS Industrial Engineering Integrated Practicum.

  10. Design optimum frac jobs using virtual intelligence techniques

    NASA Astrophysics Data System (ADS)

    Mohaghegh, Shahab; Popa, Andrei; Ameri, Sam

    2000-10-01

    Designing optimal frac jobs is a complex and time-consuming process. It usually involves the use of a two- or three-dimensional computer model. For the computer models to perform as intended, a wealth of input data is required. The input data includes wellbore configuration and reservoir characteristics such as porosity, permeability, stress and thickness profiles of the pay layers as well as the overburden layers. Among other essential information required for the design process is fracturing fluid type and volume, proppant type and volume, injection rate, proppant concentration and frac job schedule. Some of the parameters such as fluid and proppant types have discrete possible choices. Other parameters such as fluid and proppant volume, on the other hand, assume values from within a range of minimum and maximum values. A potential frac design for a particular pay zone is a combination of all of these parameters. Finding the optimum combination is not a trivial process. It usually requires an experienced engineer and a considerable amount of time to tune the parameters in order to achieve desirable outcome. This paper introduces a new methodology that integrates two virtual intelligence techniques, namely, artificial neural networks and genetic algorithms to automate and simplify the optimum frac job design process. This methodology requires little input from the engineer beyond the reservoir characterizations and wellbore configuration. The software tool that has been developed based on this methodology uses the reservoir characteristics and an optimization criteria indicated by the engineer, for example a certain propped frac length, and provides the detail of the optimum frac design that will result in the specified criteria. An ensemble of neural networks is trained to mimic the two- or three-dimensional frac simulator. Once successfully trained, these networks are capable of providing instantaneous results in response to any set of input parameters. These networks will be used as the fitness function for a genetic algorithm routine that will search for the best combination of the design parameters for the frac job. The genetic algorithm will search through the entire solution space and identify the optimal combination of parameters to be used in the design process. Considering the complexity of this task this methodology converges relatively fast, providing the engineer with several near-optimum scenarios for the frac job design. These scenarios, which can be achieved in just a minute or two, can be valuable initial points for the engineer to start his/her design job and save him/her hours of runs on the simulator.

  11. Ceramic Technology for Advanced Heat Engines Project. Semiannual progress report, October 1984-March 1985

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

    Not Available

    1985-09-01

    A five-year project plan was developed with extensive input from private industry. The objective of the project is to develop the industrial technology base required for reliable ceramics for application in advanced automotive heat engines. The project approach includes determining the mechanisms controlling reliability, improving processes for fabricating existing ceramics, developing new materials with increased reliability, and testing these materials in simulated engine environments to confirm reliability. Although this is a generic materials project, the focus is on structural ceramics for advanced gas turbine and diesel engines, ceramic bearings and attachments, and ceramic coatings for thermal barrier and wear applicationsmore » in these engines.« less

  12. Ceramic technology for advanced heat engines project: Semiannual progress report for April through September 1986

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

    Not Available

    1987-03-01

    An assessment of needs was completed, and a five-year project plan was developed with extensive input from private industry. Objective is to develop the industrial technology base required for reliable ceramics for application in advanced automotive heat engines. The project approach includes determining the mechanisms controlling reliability, improving processes for fabricating existing ceramics, developing new materials with increased reliability, and testing these materials in simulated engine environments to confirm reliability. Although this is a generic materials project, the focus is on structural ceramics for advanced gas turbine and diesel engines, ceramic bearings and attachments, and ceramic coatings for thermal barriermore » and wear applications in these engines.« less

  13. Liquid rocket booster integration study. Volume 1: Executive summary

    NASA Technical Reports Server (NTRS)

    1988-01-01

    The impacts of introducing liquid rocket booster engines (LRB) into the Space Transportation System (STS)/Kennedy Space Center (KSC) launch environment are identified and evaluated. Proposed ground systems configurations are presented along with a launch site requirements summary. Prelaunch processing scenarios are described and the required facility modifications and new facility requirements are analyzed. Flight vehicle design recommendations to enhance launch processing are discussed. Processing approaches to integrate LRB with existing STS launch operations are evaluated. The key features and significance of launch site transition to a new STS configuration in parallel with ongoing launch activities are enumerated. This volume is the executive summary of the five volume series.

  14. Liquid rocket booster integration study. Volume 5, part 1: Appendices

    NASA Technical Reports Server (NTRS)

    1988-01-01

    The impacts of introducing liquid rocket booster engines (LRB) into the Space Transportation System (STS)/Kennedy Space Center (KSC) launch environment are identified and evaluated. Proposed ground systems configurations are presented along with a launch site requirements summary. Prelaunch processing scenarios are described and the required facility modifications and new facility requirements are analyzed. Flight vehicle design recommendations to enhance launch processing are discussed. Processing approaches to integrate LRB with existing STS launch operations are evaluated. The key features and significance of launch site transition to a new STS configuration in parallel with ongoing launch activities are enumerated. This volume is the appendices of the five volume series.

  15. Liquid Rocket Booster Integration Study. Volume 2: Study synopsis

    NASA Technical Reports Server (NTRS)

    1988-01-01

    The impacts of introducing liquid rocket booster engines (LRB) into the Space Transportation System (STS)/Kennedy Space Center (KSC) launch environment are identified and evaluated. Proposed ground systems configurations are presented along with a launch site requirements summary. Prelaunch processing scenarios are described and the required facility modifications and new facility requirements are analyzed. Flight vehicle design recommendations to enhance launch processing are discussed. Processing approaches to integrate LRB with existing STS launch operations are evaluated. The key features and significance of launch site transition to a new STS configuration in parallel with ongoing launch activities are enumerated. This volume is the study summary of the five volume series.

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

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

  18. The Australian Computational Earth Systems Simulator

    NASA Astrophysics Data System (ADS)

    Mora, P.; Muhlhaus, H.; Lister, G.; Dyskin, A.; Place, D.; Appelbe, B.; Nimmervoll, N.; Abramson, D.

    2001-12-01

    Numerical simulation of the physics and dynamics of the entire earth system offers an outstanding opportunity for advancing earth system science and technology but represents a major challenge due to the range of scales and physical processes involved, as well as the magnitude of the software engineering effort required. However, new simulation and computer technologies are bringing this objective within reach. Under a special competitive national funding scheme to establish new Major National Research Facilities (MNRF), the Australian government together with a consortium of Universities and research institutions have funded construction of the Australian Computational Earth Systems Simulator (ACcESS). The Simulator or computational virtual earth will provide the research infrastructure to the Australian earth systems science community required for simulations of dynamical earth processes at scales ranging from microscopic to global. It will consist of thematic supercomputer infrastructure and an earth systems simulation software system. The Simulator models and software will be constructed over a five year period by a multi-disciplinary team of computational scientists, mathematicians, earth scientists, civil engineers and software engineers. The construction team will integrate numerical simulation models (3D discrete elements/lattice solid model, particle-in-cell large deformation finite-element method, stress reconstruction models, multi-scale continuum models etc) with geophysical, geological and tectonic models, through advanced software engineering and visualization technologies. When fully constructed, the Simulator aims to provide the software and hardware infrastructure needed to model solid earth phenomena including global scale dynamics and mineralisation processes, crustal scale processes including plate tectonics, mountain building, interacting fault system dynamics, and micro-scale processes that control the geological, physical and dynamic behaviour of earth systems. ACcESS represents a part of Australia's contribution to the APEC Cooperation for Earthquake Simulation (ACES) international initiative. Together with other national earth systems science initiatives including the Japanese Earth Simulator and US General Earthquake Model projects, ACcESS aims to provide a driver for scientific advancement and technological breakthroughs including: quantum leaps in understanding of earth evolution at global, crustal, regional and microscopic scales; new knowledge of the physics of crustal fault systems required to underpin the grand challenge of earthquake prediction; new understanding and predictive capabilities of geological processes such as tectonics and mineralisation.

  19. Design and Data Management System

    NASA Technical Reports Server (NTRS)

    Messer, Elizabeth; Messer, Brad; Carter, Judy; Singletary, Todd; Albasini, Colby; Smith, Tammy

    2007-01-01

    The Design and Data Management System (DDMS) was developed to automate the NASA Engineering Order (EO) and Engineering Change Request (ECR) processes at the Propulsion Test Facilities at Stennis Space Center for efficient and effective Configuration Management (CM). Prior to the development of DDMS, the CM system was a manual, paper-based system that required an EO or ECR submitter to walk the changes through the acceptance process to obtain necessary approval signatures. This approval process could take up to two weeks, and was subject to a variety of human errors. The process also requires that the CM office make copies and distribute them to the Configuration Control Board members for review prior to meetings. At any point, there was a potential for an error or loss of the change records, meaning the configuration of record was not accurate. The new Web-based DDMS eliminates unnecessary copies, reduces the time needed to distribute the paperwork, reduces time to gain the necessary signatures, and prevents the variety of errors inherent in the previous manual system. After implementation of the DDMS, all EOs and ECRs can be automatically checked prior to submittal to ensure that the documentation is complete and accurate. Much of the configuration information can be documented in the DDMS through pull-down forms to ensure consistent entries by the engineers and technicians in the field. The software also can electronically route the documents through the signature process to obtain the necessary approvals needed for work authorization. The workflow of the system allows for backups and timestamps that determine the correct routing and completion of all required authorizations in a more timely manner, as well as assuring the quality and accuracy of the configuration documents.

  20. Fast Formal Analysis of Requirements via "Topoi Diagrams"

    NASA Technical Reports Server (NTRS)

    Menzies, Tim; Powell, John; Houle, Michael E.; Kelly, John C. (Technical Monitor)

    2001-01-01

    Early testing of requirements can decrease the cost of removing errors in software projects. However, unless done carefully, that testing process can significantly add to the cost of requirements analysis. We show here that requirements expressed as topoi diagrams can be built and tested cheaply using our SP2 algorithm, the formal temporal properties of a large class of topoi can be proven very quickly, in time nearly linear in the number of nodes and edges in the diagram. There are two limitations to our approach. Firstly, topoi diagrams cannot express certain complex concepts such as iteration and sub-routine calls. Hence, our approach is more useful for requirements engineering than for traditional model checking domains. Secondly, out approach is better for exploring the temporal occurrence of properties than the temporal ordering of properties. Within these restrictions, we can express a useful range of concepts currently seen in requirements engineering, and a wide range of interesting temporal properties.

  1. National meeting to review IPAD status and goals. [Integrated Programs for Aerospace-vehicle Design

    NASA Technical Reports Server (NTRS)

    Fulton, R. E.

    1980-01-01

    A joint NASA/industry project called Integrated Programs for Aerospace-vehicle Design (IPAD) is described, which has the goal of raising aerospace-industry productivity through the application of computers to integrate company-wide management of engineering data. Basically a general-purpose interactive computing system developed to support engineering design processes, the IPAD design is composed of three major software components: the executive, data management, and geometry and graphics software. Results of IPAD activities include a comprehensive description of a future representative aerospace vehicle design process and its interface to manufacturing, and requirements and preliminary design of a future IPAD software system to integrate engineering activities of an aerospace company having several products under simultaneous development.

  2. System Engineering Concept Demonstration, Effort Summary. Volume 1

    DTIC Science & Technology

    1992-12-01

    involve only the system software, user frameworks and user tools. U •User Tool....s , Catalyst oExternal 00 Computer Framwork P OSystems • •~ Sysytem...analysis, synthesis, optimization, conceptual design of Catalyst. The paper discusses the definition, design, test, and evaluation; operational concept...This approach will allow system engineering The conceptual requirements for the Process Model practitioners to recognize and tailor the model. This

  3. How to Do Science From an Engineering Organization

    NASA Technical Reports Server (NTRS)

    Suggs, Robert M.

    2003-01-01

    MSFC's Space Environments Team performs engineering support for a number of NASA spaceflight projects by defining the space environment, developing design requirements, supporting the design process, and supporting operations. Examples of this type of support are given including meteoroid environment work for the Jovian Icy Moon Orbiter mission, ionizing radiation support for the Chandra X-Ray Observatory, and astronomicaVgeophysica1 observation planning for International Space Station.

  4. Manufacturing Technology for Shipbuilding

    DTIC Science & Technology

    1983-01-01

    during which time there was an interface of Japanese and American shipbuilding concepts and methodology . Those two years of work resulted in many...lanes is of paramount importance in maintaining a smoothy orderly flow of pre-fabricated steel. Occasionally, the process lanes may fall behind schedule...design methodology . The earlier the start that Engineering has, the better the chance that all required engineering work will be completed at start of

  5. The Systems Test Architect: Enabling The Leap From Testable To Tested

    DTIC Science & Technology

    2016-09-01

    engineering process requires an interdisciplinary approach, involving both technical and managerial disciplines applied to the synthesis and integration...relationship between the technical and managerial aspects of systems engineering. TP-2003-020-01 describes measurement as having the following...it is evident that DOD makes great strides to tackle both the managerial and technical aspects of test and evaluation within the systems

  6. A Mixed Learning Approach to Integrating Digital Signal Processing Laboratory Exercises into a Non-Lab Junior Year DSP Course

    ERIC Educational Resources Information Center

    McPheron, Benjamin D.; Thangaraj, Charles V.; Thomas, Charles R.

    2017-01-01

    Laboratory courses can be difficult to fit into an engineering program at a liberal arts-focused university, which requires students to be exposed to appropriate breadth, as well as sufficient depth in their engineering education. One possible solution to this issue is to integrate laboratory exercises with lecture in a "studio" format,…

  7. Modelling and Simulation for Requirements Engineering and Options Analysis

    DTIC Science & Technology

    2010-05-01

    should be performed to work successfully in the domain; and process-based techniques model the processes that occur in the work domain. There is a crisp ...acad/sed/sedres/ dm /erg/cwa. DRDC Toronto CR 2010-049 39 23. Can the current technique for developing simulation models for assessments

  8. System design from mission definition to flight validation

    NASA Technical Reports Server (NTRS)

    Batill, S. M.

    1992-01-01

    Considerations related to the engineering systems design process and an approach taken to introduce undergraduate students to that process are presented. The paper includes details on a particular capstone design course. This course is a team oriented aircraft design project which requires the students to participate in many phases of the system design process, from mission definition to validation of their design through flight testing. To accomplish this in a single course requires special types of flight vehicles. Relatively small-scale, remotely piloted vehicles have provided the class of aircraft considered in this course.

  9. NOSS Altimeter Detailed Algorithm specifications

    NASA Technical Reports Server (NTRS)

    Hancock, D. W.; Mcmillan, J. D.

    1982-01-01

    The details of the algorithms and data sets required for satellite radar altimeter data processing are documented in a form suitable for (1) development of the benchmark software and (2) coding the operational software. The algorithms reported in detail are those established for altimeter processing. The algorithms which required some additional development before documenting for production were only scoped. The algorithms are divided into two levels of processing. The first level converts the data to engineering units and applies corrections for instrument variations. The second level provides geophysical measurements derived from altimeter parameters for oceanographic users.

  10. Engineering Supply Management System: The Next Generation

    DTIC Science & Technology

    1991-09-01

    010 Partia! receipts 0018 Automatic inventory update 0 048 Discrepant material 0 004 Order processing requirements Transaction reversal capability 0 012...August 1991. 2-5 sys.em’s modules that support the DEH’s needs are the Sales Order Processing , Register Sales, Purchase Order Processing , Inventory...modular system developed by PIC Business Systems, Incorporated. This system possesses Order Processing , Inventory Management, Purchase Orders, and

  11. Processing multilevel secure test and evaluation information

    NASA Astrophysics Data System (ADS)

    Hurlburt, George; Hildreth, Bradley; Acevedo, Teresa

    1994-07-01

    The Test and Evaluation Community Network (TECNET) is building a Multilevel Secure (MLS) system. This system features simultaneous access to classified and unclassified information and easy access through widely available communications channels. It provides the necessary separation of classification levels, assured through the use of trusted system design techniques, security assessments and evaluations. This system enables cleared T&E users to view and manipulate classified and unclassified information resources either using a single terminal interface or multiple windows in a graphical user interface. TECNET is in direct partnership with the National Security Agency (NSA) to develop and field the MLS TECNET capability in the near term. The centerpiece of this partnership is a state-of-the-art Concurrent Systems Security Engineering (CSSE) process. In developing the MLS TECNET capability, TECNET and NSA are providing members, with various expertise and diverse backgrounds, to participate in the CSSE process. The CSSE process is founded on the concepts of both Systems Engineering and Concurrent Engineering. Systems Engineering is an interdisciplinary approach to evolve and verify an integrated and life cycle balanced set of system product and process solutions that satisfy customer needs (ASD/ENS-MIL STD 499B 1992). Concurrent Engineering is design and development using the simultaneous, applied talents of a diverse group of people with the appropriate skills. Harnessing diverse talents to support CSSE requires active participation by team members in an environment that both respects and encourages diversity.

  12. Development of Integrated Programs for Aerospace-vehicle design (IPAD): Integrated information processing requirements

    NASA Technical Reports Server (NTRS)

    Southall, J. W.

    1979-01-01

    The engineering-specified requirements for integrated information processing by means of the Integrated Programs for Aerospace-Vehicle Design (IPAD) system are presented. A data model is described and is based on the design process of a typical aerospace vehicle. General data management requirements are specified for data storage, retrieval, generation, communication, and maintenance. Information management requirements are specified for a two-component data model. In the general portion, data sets are managed as entities, and in the specific portion, data elements and the relationships between elements are managed by the system, allowing user access to individual elements for the purpose of query. Computer program management requirements are specified for support of a computer program library, control of computer programs, and installation of computer programs into IPAD.

  13. Signal Processing Methods for Liquid Rocket Engine Combustion Stability Assessments

    NASA Technical Reports Server (NTRS)

    Kenny, R. Jeremy; Lee, Erik; Hulka, James R.; Casiano, Matthew

    2011-01-01

    The J2X Gas Generator engine design specifications include dynamic, spontaneous, and broadband combustion stability requirements. These requirements are verified empirically based high frequency chamber pressure measurements and analyses. Dynamic stability is determined with the dynamic pressure response due to an artificial perturbation of the combustion chamber pressure (bomb testing), and spontaneous and broadband stability are determined from the dynamic pressure responses during steady operation starting at specified power levels. J2X Workhorse Gas Generator testing included bomb tests with multiple hardware configurations and operating conditions, including a configuration used explicitly for engine verification test series. This work covers signal processing techniques developed at Marshall Space Flight Center (MSFC) to help assess engine design stability requirements. Dynamic stability assessments were performed following both the CPIA 655 guidelines and a MSFC in-house developed statistical-based approach. The statistical approach was developed to better verify when the dynamic pressure amplitudes corresponding to a particular frequency returned back to pre-bomb characteristics. This was accomplished by first determining the statistical characteristics of the pre-bomb dynamic levels. The pre-bomb statistical characterization provided 95% coverage bounds; these bounds were used as a quantitative measure to determine when the post-bomb signal returned to pre-bomb conditions. The time for post-bomb levels to acceptably return to pre-bomb levels was compared to the dominant frequency-dependent time recommended by CPIA 655. Results for multiple test configurations, including stable and unstable configurations, were reviewed. Spontaneous stability was assessed using two processes: 1) characterization of the ratio of the peak response amplitudes to the excited chamber acoustic mode amplitudes and 2) characterization of the variability of the peak response's frequency over the test duration. This characterization process assists in evaluating the discreteness of a signal as well as the stability of the chamber response. Broadband stability was assessed using a running root-mean-square evaluation. These techniques were also employed, in a comparative analysis, on available Fastrac data, and these results are presented here.

  14. Analysis of the production process of optically pure D-lactic acid from raw glycerol using engineered Escherichia coli strains.

    PubMed

    Posada, John A; Cardona, Carlos A; Gonzalez, Ramon

    2012-02-01

    Glycerol has become an ideal feedstock for producing fuels and chemicals. Here, five technological schemes for optically pure D: -lactic acid production from raw glycerol were designed, simulated, and economically assessed based on five fermentative scenarios using engineered Escherichia coli strains. Fermentative scenarios considered different qualities of glycerol (pure, 98 wt.%, and crude, 85 wt.%) with concentrations ranging from 20 to 60 g/l in the fermentation media, and two fermentation stages were also analyzed. Raw glycerol (60 wt.%) was considered as the feedstock feeding the production process in all cases; then a purification process of raw glycerol up to the required quality was required. Simulation processes were carried out using Aspen Plus, while economic assessments were performed using Aspen Icarus Process Evaluator. D: -Lactic acid recovery and purification processes were based on reactive extraction with tri-n-octylamine using dichloromethane as active extractant agent. The use of raw glycerol represents only between 2.4% and 7.8% of the total production costs. Also, the total production costs obtained of D: -lactic acid in all cases were lower than its sale price indicating that these processes are potentially profitable. Thus, the best configuration process requires the use of crude glycerol diluted at 40 g/l with total glycerol consumption and with D: -lactic acid recovering by reactive extraction. The lowest obtained total production cost was 1.015 US$/kg with a sale price/production cost ratio of 1.53.

  15. ViPLab: A Virtual Programming Laboratory for Mathematics and Engineering

    ERIC Educational Resources Information Center

    Richter, Thomas; Rudlof, Stephan; Adjibadji, B.; Bernlohr, Heiko; Gruninger, Christoph; Munz, Claus-Dieter; Stock, Andreas; Rohde, Christian; Helmig, Rainer

    2012-01-01

    Purpose: In the process of the implementation of the eBologna program and the recent change of the university system, curricula at German universities have been redesigned; courses have been condensed and learning content has been re-structured into modules, each of which requires an evaluation. Simultaneously, skills required for working in…

  16. Improving conversion yield of fermentable sugars into fuel ethanol in 1st generation yeast-based production processes.

    PubMed

    Gombert, Andreas K; van Maris, Antonius J A

    2015-06-01

    Current fuel ethanol production using yeasts and starch or sucrose-based feedstocks is referred to as 1st generation (1G) ethanol production. These processes are characterized by the high contribution of sugar prices to the final production costs, by high production volumes, and by low profit margins. In this context, small improvements in the ethanol yield on sugars have a large impact on process economy. Three types of strategies used to achieve this goal are discussed: engineering free-energy conservation, engineering redox-metabolism, and decreasing sugar losses in the process. Whereas the two former strategies lead to decreased biomass and/or glycerol formation, the latter requires increased process and/or yeast robustness. Copyright © 2014 Elsevier Ltd. All rights reserved.

  17. Vers l'elimination des dessins d'ingenierie des processus de modification d'ingenierie en aeronautique

    NASA Astrophysics Data System (ADS)

    Quintana, Virgilio

    For many years, 3D models and 2D drawings have been the main basic elements that together form and carry a product's definition throughout its lifecycle. With the advent of the Digital Product Definition trend, the Aerospace and Automotive industries have been very interested in adopting a Model-based Definition (MBD) approach that promises reduced time-to-market and improved product quality. Its main purpose is to improve and accelerate the design, manufacturing and inspection processes by integrating drawing annotations directly onto a 3D model, thereby minimizing the need to generate engineering drawings. Even though CAD tools and international standards support the MBD concept, its implementation throughout the whole product lifecycle has not yet been fully adopted; traditional engineering drawings still play an essential part in the capture and distribution of non-geometric data (tolerances, notes, etc.), in the long-term storage of product definitions, as well as in the management of engineering changes. This is especially so within the Engineering Change Management (ECM) process, which involves the study, review, annotation, validation, approval and release of engineering drawings. The exploration of alternatives to reengineer the ECM process in the absence of drawings is therefore a necessary step before the MBD approach can be broadly accepted. The objective of this research project was to propose a solution to conduct the ECM process in a drawing-less environment and to quantify its potential gains. Two Canadian aerospace companies participated in this project. First, the main barriers to be overcome in order to fully implement the MBD initiative were identified. Our observations were based on forty-one interviews conducted within the Engineering, Drafting, Configuration Management, Airworthiness, Certification, Manufacturing, Inspection and Knowledge Management departments from the two participating companies. The results indicated that there is a need to define how the Product Definition will be carried in this drawing-less environment while supporting all of the downstream users' specific requirements. Next, a solution to conduct an MBD-driven Engineering Change Management Process (ECM) was developed and evaluated based on the process requirements from both companies. The solution consists of the definition of a dataset composed of the MBD model (generated by the CAD system) and a lightweight distribution file (generated and exploited by the visualization application). The ECM process was then reengineered to support its execution when working with MBD datasets. Finally, the gains from administering the MBD-driven ECM process were determined using empirical and experimental data within a discrete-event simulation approach. Based on a case study conducted in a Canadian aerospace company, our results show that a reduction of about 11% can be achieved in both the average overall processing time and in the average cost.

  18. Quiet Clean Short-haul Experimental Engine (QCSEE). Composite fan frame subsystem test report

    NASA Technical Reports Server (NTRS)

    Stotler, C. L., Jr.; Bowden, J. H.

    1977-01-01

    The element and subcomponent testing conducted to verify the composite fan frame design of two experimental high bypass geared turbofan engines and propulsion systems for short haul passenger aircraft is described. Emphasis is placed on the propulsion technology required for future externally blown flap aircraft with engines located both under the wing and over the wing, including technology in composite structures and digital engine controls. The element tests confirmed that the processes used in the frame design would produce the predicted mechanical properties. The subcomponent tests verified that the detail structural components of the frame had adequate structural integrity.

  19. Adaptation of Combustion Principles to Aircraft Propulsion. Volume I; Basic Considerations in the Combustion of Hydrocarbon Fuels with Air

    NASA Technical Reports Server (NTRS)

    Barnett, Henry C (Editor); Hibbard, Robert R (Editor)

    1955-01-01

    The report summarizes source material on combustion for flight-propulsion engineers. First, several chapters review fundamental processes such as fuel-air mixture preparation, gas flow and mixing, flammability and ignition, flame propagation in both homogenous and heterogenous media, flame stabilization, combustion oscillations, and smoke and carbon formation. The practical significance and the relation of these processes to theory are presented. A second series of chapters describes the observed performance and design problems of engine combustors of the principal types. An attempt is made to interpret performance in terms of the fundamental processes and theories previously reviewed. Third, the design of high-speed combustion systems is discussed. Combustor design principles that can be established from basic considerations and from experience with actual combustors are described. Finally, future requirements for aircraft engine combustion systems are examined.

  20. Metrology: Calibration and measurement processes guidelines

    NASA Technical Reports Server (NTRS)

    Castrup, Howard T.; Eicke, Woodward G.; Hayes, Jerry L.; Mark, Alexander; Martin, Robert E.; Taylor, James L.

    1994-01-01

    The guide is intended as a resource to aid engineers and systems contracts in the design, implementation, and operation of metrology, calibration, and measurement systems, and to assist NASA personnel in the uniform evaluation of such systems supplied or operated by contractors. Methodologies and techniques acceptable in fulfilling metrology quality requirements for NASA programs are outlined. The measurement process is covered from a high level through more detailed discussions of key elements within the process, Emphasis is given to the flowdown of project requirements to measurement system requirements, then through the activities that will provide measurements with defined quality. In addition, innovations and techniques for error analysis, development of statistical measurement process control, optimization of calibration recall systems, and evaluation of measurement uncertainty are presented.

  1. Systems Integration Processes for NASA Ares I Crew Launch Vehicle

    NASA Technical Reports Server (NTRS)

    Taylor, James L.; Reuter, James L.; Sexton, Jeffrey D.

    2006-01-01

    NASA's Exploration Initiative will require development of many new elements to constitute a robust system of systems. New launch vehicles are needed to place cargo and crew in stable Low Earth Orbit (LEO). This paper examines the systems integration processes NASA is utilizing to ensure integration and control of propulsion and nonpropulsion elements within NASA's Crew Launch Vehicle (CLV), now known as the Ares I. The objective of the Ares I is to provide the transportation capabilities to meet the Constellation Program requirements for delivering a Crew Exploration Vehicle (CEV) or other payload to LEO in support of the lunar and Mars missions. The Ares I must successfully provide this capability within cost and schedule, and with an acceptable risk approach. This paper will describe the systems engineering management processes that will be applied to assure Ares I Project success through complete and efficient technical integration. Discussion of technical review and management processes for requirements development and verification, integrated design and analysis, integrated simulation and testing, and the integration of reliability, maintainability and supportability (RMS) into the design will also be included. The Ares I Project is logically divided into elements by the major hardware groupings, and associated management, system engineering, and integration functions. The processes to be described herein are designed to integrate within these Ares I elements and among the other Constellation projects. Also discussed is launch vehicle stack integration (Ares I to CEV, and Ground and Flight Operations integration) throughout the life cycle, including integrated vehicle performance through orbital insertion, recovery of the first stage, and reentry of the upper stage. The processes for decomposing requirements to the elements and ensuring that requirements have been correctly validated, decomposed, and allocated, and that the verification requirements are properly defined to ensure that the system design meets requirements, will be discussed.

  2. NEXT Ion Engine 2000 Hour Wear Test Results

    NASA Technical Reports Server (NTRS)

    Soulas, George C.; Kamhawi, Hani; Patterson, Michael J.; Britton, Melissa A.; Frandina, Michael M.

    2004-01-01

    The results of the NEXT 2000 h wear test are presented. This test was conducted with a 40 cm engineering model ion engine, designated EM1, at a 3.52 A beam current and 1800 V beam power supply voltage. Performance tests, which were conducted over a throttling range of 1.1 to 6.9 kW throughout the wear test, demonstrated that EM1 satisfied all thruster performance requirements. The ion engine accumulated 2038 h of operation at a thruster input power of 6.9 kW, processing 43 kg of xenon. Overall ion engine performance, which includes thrust, thruster input power, specific impulse, and thrust efficiency, was steady with no indications of performance degradation. The ion engine was also inspected following the test. This paper presents these findings.

  3. Uncertainty in Calibration, Detection and Estimation of Metal Concentrations in Engine Plumes Using OPAD

    NASA Technical Reports Server (NTRS)

    Hopkins, Randall C.; Benzing, Daniel A.

    1998-01-01

    Improvements in uncertainties in the values of radiant intensity (I) can be accomplished mainly by improvements in the calibration process and in minimizing the difference between the background and engine plume radiance. For engine tests in which the plume is extremely bright, the difference in luminance between the calibration lamp and the engine plume radiance can be so large as to cause relatively large uncertainties in the values of R. This is due to the small aperture necessary on the receiving optics to avoid saturating the instrument. However, this is not a problem with the SSME engine since the liquid oxygen/hydrogen combustion is not as bright as some other fuels. Applying the instrumentation to other type engine tests may require a much brighter calibration lamp.

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

    DTIC Science & Technology

    1995-09-01

    vital processes of a business. process, IDEF, method, methodology, modeling, knowledge acquisition, requirements definition, information systems... knowledge resources. Like manpower, materials, and machines, information and knowledge assets are recognized as vital resources that can be leveraged to...integrated enterprise. These technologies are designed to leverage information and knowledge resources as the key enablers for high quality systems

  5. A requirements engineering approach for improving the quality of diabetes education websites.

    PubMed

    Shabestari, Omid; Roudsari, Abdul

    2011-01-01

    Diabetes Mellitus is a major chronic disease with multi-organ involvement and high-cost complications. Although it has been proved that structured education can control the risk of developing these complications, there is big room for improvement in the educational services for these patients. e-learning can be a good solution to fill this gap. Most of the current e-learning solutions for diabetes were designed by computer experts and healthcare professionals but the patients, as end-users of these systems, haven't been deeply involved in the design process. Considering the expectations of the patients, this article investigates a requirement engineering process comparing the level of importance given to different attributes of the e-learning by patients and healthcare professionals. The results of this comparison can be used for improving the currently developed online diabetes education systems.

  6. Revisiting software specification and design for large astronomy projects

    NASA Astrophysics Data System (ADS)

    Wiant, Scott; Berukoff, Steven

    2016-07-01

    The separation of science and engineering in the delivery of software systems overlooks the true nature of the problem being solved and the organization that will solve it. Use of a systems engineering approach to managing the requirements flow between these two groups as between a customer and contractor has been used with varying degrees of success by well-known entities such as the U.S. Department of Defense. However, treating science as the customer and engineering as the contractor fosters unfavorable consequences that can be avoided and opportunities that are missed. For example, the "problem" being solved is only partially specified through the requirements generation process since it focuses on detailed specification guiding the parties to a technical solution. Equally important is the portion of the problem that will be solved through the definition of processes and staff interacting through them. This interchange between people and processes is often underrepresented and under appreciated. By concentrating on the full problem and collaborating on a strategy for its solution a science-implementing organization can realize the benefits of driving towards common goals (not just requirements) and a cohesive solution to the entire problem. The initial phase of any project when well executed is often the most difficult yet most critical and thus it is essential to employ a methodology that reinforces collaboration and leverages the full suite of capabilities within the team. This paper describes an integrated approach to specifying the needs induced by a problem and the design of its solution.

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

  8. Expanded Guidance for NASA Systems Engineering. Volume 2: Crosscutting Topics, Special Topics, and Appendices

    NASA Technical Reports Server (NTRS)

    Hirshorn, Steven R.

    2017-01-01

    Historically, most successful NASA projects have depended on effectively blending project management, systems engineering, and technical expertise among NASA, contractors, and third parties. Underlying these successes are a variety of agreements (e.g., contract, memorandum of understanding, grant, cooperative agreement) between NASA organizations or between NASA and other Government agencies, Government organizations, companies, universities, research laboratories, and so on. To simplify the discussions, the term "contract" is used to encompass these agreements. This section focuses on the NASA systems engineering activities pertinent to awarding a contract, managing contract performance, and completing a contract. In particular, NASA systems engineering interfaces to the procurement process are covered, since the NASA engineering technical team plays a key role in the development and evaluation of contract documentation. Contractors and third parties perform activities that supplement (or substitute for) the NASA project technical team accomplishment of the NASA common systems engineering technical process activities and requirements outlined in this guide. Since contractors might be involved in any part of the systems engineering life cycle, the NASA project technical team needs to know how to prepare for, allocate or perform, and implement surveillance of technical activities that are allocated to contractors.

  9. Process quality engineering for bioreactor-driven manufacturing of tissue-engineered constructs for bone regeneration.

    PubMed

    Papantoniou Ir, Ioannis; Chai, Yoke Chin; Luyten, Frank P; Schrooten Ir, Jan

    2013-08-01

    The incorporation of Quality-by-Design (QbD) principles in tissue-engineering bioprocess development toward clinical use will ensure that manufactured constructs possess prerequisite quality characteristics addressing emerging regulatory requirements and ensuring the functional in vivo behavior. In this work, the QbD principles were applied on a manufacturing process step for the in vitro production of osteogenic three-dimensional (3D) hybrid scaffolds that involves cell matrix deposition on a 3D titanium (Ti) alloy scaffold. An osteogenic cell source (human periosteum-derived cells) cultured in a bioinstructive medium was used to functionalize regular Ti scaffolds in a perfusion bioreactor, resulting in an osteogenic hybrid carrier. A two-level three-factor fractional factorial design of experiments was employed to explore a range of production-relevant process conditions by simultaneously changing value levels of the following parameters: flow rate (0.5-2 mL/min), cell culture duration (7-21 days), and cell-seeding density (1.5×10(3)-3×10(3) cells/cm(2)). This approach allowed to evaluate the individual impact of the aforementioned process parameters upon key quality attributes of the produced hybrids, such as collagen production, mineralization level, and cell number. The use of a fractional factorial design approach helped create a design space in which hybrid scaffolds of predefined quality attributes may be robustly manufactured while minimizing the number of required experiments.

  10. Isolator-combustor interaction in a dual-mode scramjet engine

    NASA Technical Reports Server (NTRS)

    Pratt, David T.; Heiser, William H.

    1993-01-01

    A constant-area diffuser, or 'isolator', is required in both the ramjet and scramjet operating regimes of a dual-mode engine configuration in order to prevent unstarts due to pressure feedback from the combustor. Because the nature of the combustor-isolator interaction is different in the two operational modes, however, attention is presently given to the use of thermal vs kinetic energy coordinates for these interaction processes' visualization. The results of the analysis thus conducted indicate that the isolator requires severe flow separation at combustor entry, and that its entropy-generating characteristics are more severe than an equivalent oblique shock. A constant-area diffuser is only marginally able to contain the equivalent normal shock required for subsonic combustor entry.

  11. Energy and Water Conservation Assessment of the Radiochemical Processing Laboratory (RPL) at Pacific Northwest National Laboratory

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

    Johnson, Stephanie R.; Koehler, Theresa M.; Boyd, Brian K.

    2014-05-31

    This report summarizes the results of an energy and water conservation assessment of the Radiochemical Processing Laboratory (RPL) at Pacific Northwest National Laboratory (PNNL). The assessment was performed in October 2013 by engineers from the PNNL Building Performance Team with the support of the dedicated RPL staff and several Facilities and Operations (F&O) department engineers. The assessment was completed for the Facilities and Operations (F&O) department at PNNL in support of the requirements within Section 432 of the Energy Independence and Security Act (EISA) of 2007.

  12. On-line infrared process signature measurements through combustion atmospheres

    NASA Astrophysics Data System (ADS)

    Zweibaum, F. M.; Kozlowski, A. T.; Surette, W. E., Jr.

    1980-01-01

    A number of on-line infrared process signature measurements have been made through combustion atmospheres, including those in jet engines, piston engines, and coal gasification reactors. The difficulties involved include operation in the presence of pressure as high as 1800 psi, temperatures as high as 3200 F, and explosive, corrosive and dust-laden atmospheres. Calibration problems have resulted from the use of purge gases to clear the viewing tubes, and the obscuration of the view ports by combustion products. A review of the solutions employed to counteract the problems is presented, and areas in which better solutions are required are suggested.

  13. Space Station logistics policy - Risk management from the top down

    NASA Technical Reports Server (NTRS)

    Paules, Granville; Graham, James L., Jr.

    1990-01-01

    Considerations are presented in the area of risk management specifically relating to logistics and system supportability. These considerations form a basis for confident application of concurrent engineering principles to a development program, aiming at simultaneous consideration of support and logistics requirements within the engineering process as the system concept and designs develop. It is shown that, by applying such a process, the chances of minimizing program logistics and supportability risk in the long term can be improved. The problem of analyzing and minimizing integrated logistics risk for the Space Station Freedom Program is discussed.

  14. A Human Factors Framework for Payload Display Design

    NASA Technical Reports Server (NTRS)

    Dunn, Mariea C.; Hutchinson, Sonya L.

    1998-01-01

    During missions to space, one charge of the astronaut crew is to conduct research experiments. These experiments, referred to as payloads, typically are controlled by computers. Crewmembers interact with payload computers by using visual interfaces or displays. To enhance the safety, productivity, and efficiency of crewmember interaction with payload displays, particular attention must be paid to the usability of these displays. Enhancing display usability requires adoption of a design process that incorporates human factors engineering principles at each stage. This paper presents a proposed framework for incorporating human factors engineering principles into the payload display design process.

  15. Space Shuttle Main Engine Joint Data List Applying Today's Desktop Technologies to Facilitate Engine Processing

    NASA Technical Reports Server (NTRS)

    Jacobs, Kenneth; Drobnick, John; Krell, Don; Neuhart, Terry; McCool, A. (Technical Monitor)

    2001-01-01

    Boeing-Rocketdyne's Space Shuttle Main Engine (SSME) is the world's first large reusable liquid rocket engine. The space shuttle propulsion system has three SSMEs, each weighing 7,400 lbs and providing 470,000 lbs of thrust at 100% rated power level. To ensure required safety and reliability levels are achieved with the reusable engines, each SSME is partially disassembled, inspected, reassembled, and retested at Kennedy Space Center between each flight. Maintenance processing must be performed very carefully to replace any suspect components, maintain proper engine configuration, and avoid introduction of contaminants that could affect performance and safety. The long service life, and number, complexity, and pedigree of SSME components makes logistics functions extremely critical. One SSME logistics challenge is documenting the assembly and disassembly of the complex joint configurations. This data (joint nomenclature, seal and fastener identification and orientation, assembly sequence, fastener torques, etc.) must be available to technicians and engineers during processing. Various assembly drawings and procedures contain this information, but in this format the required (practical) joint data can be hard to find, due to the continued use of archaic engineering drawings and microfilm for field site use. Additionally, the release system must traverse 2,500 miles between design center and field site, across three time zones, which adds communication challenges and time lags for critical engine configuration data. To aid in information accessibility, a Joint Data List (JDL) was developed that allows efficient access to practical joint data. The published JDL has been a very useful logistics product, providing illustrations and information on the latest SSME configuration. The JDL identifies over 3,350 unique parts across seven fluid systems, over 300 joints, times two distinct engine configurations. The JDL system was recently converted to a web-based, navigable electronic manual that contains all the required data and illustrations in expanded view format using standard PC products (Word, Excel, PDF, Photoshop). The logistics of accurately releasing this information to field personnel was greatly enhanced via the utilization of common office products to produce a more user-friendly format than was originally developed under contract to NASA. This was done without reinventing the system, which would be cost prohibitive on a program of this maturity. The brunt of the joint part tracking is done within the logistics organization and disseminated to all field sites, without duplicating effort at each site. The JDL is easily accessible across the country via the NASA intranet directly at the SSME workstand. The advent of this logistics data product has greatly enhanced the reliability of tracking dynamic changes to the SSME and greatly reduces engineering change turnaround time and potential for errors. Since the inception of the JDL system in 1997, no discrepant parts have propagated to engine assembly operations. This presentation focuses on the challenges overcome and the techniques used to apply today's desktop technologies to an existing logistics data source.

  16. The opto-mechanical design process: from vision to reality

    NASA Astrophysics Data System (ADS)

    Kvamme, E. Todd; Stubbs, David M.; Jacoby, Michael S.

    2017-08-01

    The design process for an opto-mechanical sub-system is discussed from requirements development through test. The process begins with a proper mission understanding and the development of requirements for the system. Preliminary design activities are then discussed with iterative analysis and design work being shared between the design, thermal, and structural engineering personnel. Readiness for preliminary review and the path to a final design review are considered. The value of prototyping and risk mitigation testing is examined with a focus on when it makes sense to execute a prototype test program. System level margin is discussed in general terms, and the practice of trading margin in one area of performance to meet another area is reviewed. Requirements verification and validation is briefly considered. Testing and its relationship to requirements verification concludes the design process.

  17. Predictive Engineering Tools for Injection-Molded Long-Carbon-Fiber Thermoplastic Composites - FY13 Fourth Quarterly Report

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

    Nguyen, Ba Nghiep; Simmons, Kevin L.

    2013-12-02

    This quarterly report summarizes the status of the project planning to obtain all the approvals required for a Cooperative Research and Development Agreement (CRADA) with Autodesk, Inc., Toyota Motor Engineering and Manufacturing North America (Toyota), and Magna Exterior and Interiors Corporation (Magna). The final CRADA documents processed by PNNL’s Legal Services were submitted to all the parties for signatures.

  18. Standard CMMI Appraisal Method for Process Improvement (SCAMPI) A, Version 1.3: Method Definition Document

    DTIC Science & Technology

    2011-03-01

    performance of Federal Government Contract Number FA8721-05- C -0003 with Carnegie Mellon University for the operation of the Software Engineering... C Roles and Responsibilities 195 Appendix D Reporting Requirements and Options 201 Appendix E Managed Discovery 203 Appendix F Scoping and...Upgrade Team (SUT) • Mary Busby , Lockheed Martin • Palma Buttles-Valdez, Software Engineering Institute • Paul Byrnes, Integrated System Diagnostics

  19. Joint Force Quarterly. Issue 77, 2nd Quarter 2015

    DTIC Science & Technology

    2015-04-01

    security required for storing or transfer- ring the data and whether the individual should be informed about potential uses of the data. It is also...decision relevance.7 The often repeated mantra in the social sciences, “correlation does not imply causation,” certainly rings true here. The popular...development of turbine jet engines by innovative scientists and engineers working with military personnel. The process involved nearly continuous insertion

  20. Weapon System Requirements: Detailed Systems Engineering Prior to Product Development Positions Programs for Success

    DTIC Science & Technology

    2016-11-01

    systems engineering had better outcomes. For example, the Small Diameter Bomb Increment I program, which delivered within cost and schedule estimates ...its current portfolio. This portfolio has experienced cost growth of 48 percent since first full estimates and average delays in delivering initial...stable design, building and testing of prototypes, and demonstration of mature production processes. • Realistic cost estimate : Sound cost estimates

  1. Net-Shape HIP Powder Metallurgy Components for Rocket Engines

    NASA Technical Reports Server (NTRS)

    Bampton, Cliff; Goodin, Wes; VanDaam, Tom; Creeger, Gordon; James, Steve

    2005-01-01

    True net shape consolidation of powder metal (PM) by hot isostatic pressing (HIP) provides opportunities for many cost, performance and life benefits over conventional fabrication processes for large rocket engine structures. Various forms of selectively net-shape PM have been around for thirty years or so. However, it is only recently that major applications have been pursued for rocket engine hardware fabricated in the United States. The method employs sacrificial metallic tooling (HIP capsule and shaped inserts), which is removed from the part after HIP consolidation of the powder, by selective acid dissolution. Full exploitation of net-shape PM requires innovative approaches in both component design and materials and processing details. The benefits include: uniform and homogeneous microstructure with no porosity, irrespective of component shape and size; elimination of welds and the associated quality and life limitations; removal of traditional producibility constraints on design freedom, such as forgeability and machinability, and scale-up to very large, monolithic parts, limited only by the size of existing HIP furnaces. Net-shape PM HIP also enables fabrication of complex configurations providing additional, unique functionalities. The progress made in these areas will be described. Then critical aspects of the technology that still require significant further development and maturation will be discussed from the perspective of an engine systems builder and end-user of the technology.

  2. Systems Maintenance Automated Repair Tasks (SMART)

    NASA Technical Reports Server (NTRS)

    Schuh, Joseph; Mitchell, Brent; Locklear, Louis; Belson, Martin A.; Al-Shihabi, Mary Jo Y.; King, Nadean; Norena, Elkin; Hardin, Derek

    2010-01-01

    SMART is a uniform automated discrepancy analysis and repair-authoring platform that improves technical accuracy and timely delivery of repair procedures for a given discrepancy (see figure a). SMART will minimize data errors, create uniform repair processes, and enhance the existing knowledge base of engineering repair processes. This innovation is the first tool developed that links the hardware specification requirements with the actual repair methods, sequences, and required equipment. SMART is flexibly designed to be useable by multiple engineering groups requiring decision analysis, and by any work authorization and disposition platform (see figure b). The organizational logic creates the link between specification requirements of the hardware, and specific procedures required to repair discrepancies. The first segment in the SMART process uses a decision analysis tree to define all the permutations between component/ subcomponent/discrepancy/repair on the hardware. The second segment uses a repair matrix to define what the steps and sequences are for any repair defined in the decision tree. This segment also allows for the selection of specific steps from multivariable steps. SMART will also be able to interface with outside databases and to store information from them to be inserted into the repair-procedure document. Some of the steps will be identified as optional, and would only be used based on the location and the current configuration of the hardware. The output from this analysis would be sent to a work authoring system in the form of a predefined sequence of steps containing required actions, tools, parts, materials, certifications, and specific requirements controlling quality, functional requirements, and limitations.

  3. Business Process Reengineering in the Inventory Management to Improve Aircraft Maintenance Operations in the Indonesian Air Force

    DTIC Science & Technology

    2006-06-01

    research will cover an overview of business process engineering (BPR) and operation management . The focus will be on the basic process of BPR, inventory...management and improvement of the process of business operation management to appropriately provide a basic model for the Indonesian Air Force in...discuss the operation management aspects of inventory management and process improvement, including Economic Order Quantity, Material Requirement

  4. Development of sensor augmented robotic weld systems for aerospace propulsion system fabrication

    NASA Technical Reports Server (NTRS)

    Jones, C. S.; Gangl, K. J.

    1986-01-01

    In order to meet stringent performance goals for power and reuseability, the Space Shuttle Main Engine was designed with many complex, difficult welded joints that provide maximum strength and minimum weight. To this end, the SSME requires 370 meters of welded joints. Automation of some welds has improved welding productivity significantly over manual welding. Application has previously been limited by accessibility constraints, requirements for complex process control, low production volumes, high part variability, and stringent quality requirements. Development of robots for welding in this application requires that a unique set of constraints be addressed. This paper shows how robotic welding can enhance production of aerospace components by addressing their specific requirements. A development program at the Marshall Space Flight Center combining industrial robots with state-of-the-art sensor systems and computer simulation is providing technology for the automation of welds in Space Shuttle Main Engine production.

  5. Institutional profile: the London Centre for Nanotechnology.

    PubMed

    Weston, David; Bontoux, Thierry

    2009-12-01

    Located in the London neighborhoods of Bloomsbury and South Kensington, the London Centre for Nanotechnology is a UK-based multidisciplinary research center that operates at the forefront of science and technology. It is a joint venture between two of the world's leading institutions, UCL and Imperial College London, uniting their strong capabilities in the disciplines that underpin nanotechnology: engineering, the physical sciences and biomedicine. The London Centre for Nanotechnology has a unique operating model that accesses and focuses the combined skills of the Departments of Chemistry, Physics, Materials, Medicine, Electrical and Electronic Engineering, Mechanical Engineering, Chemical Engineering, Biochemical Engineering and Earth Sciences across the two universities. It aims to provide the nanoscience and nanotechnology required to solve major problems in healthcare, information processing, energy and the environment.

  6. Ceramic Technology Project semiannual progress report, April 1992--September 1992

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

    Johnson, D.R.

    1993-07-01

    This project was developed to meet the ceramic technology requirements of the DOE Office of Transportation Systems` automotive technology programs. Significant progress in fabricating ceramic components for DOE, NASA, and DOE advanced heat engine programs show that operation of ceramic parts in high-temperature engines is feasible; however, addition research is needed in materials and processing, design, and data base and life prediction before industry will have a sufficient technology base for producing reliable cost-effective ceramic engine components commercially. A 5-yr project plan was developed, with focus on structural ceramics for advanced gas turbine and diesel engines, ceramic bearings and attachments,more » and ceramic coatings for thermal barrier and wear applications in these engines.« less

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

  8. RNA search engines empower the bacterial intranet.

    PubMed

    Dendooven, Tom; Luisi, Ben F

    2017-08-15

    RNA acts not only as an information bearer in the biogenesis of proteins from genes, but also as a regulator that participates in the control of gene expression. In bacteria, small RNA molecules (sRNAs) play controlling roles in numerous processes and help to orchestrate complex regulatory networks. Such processes include cell growth and development, response to stress and metabolic change, transcription termination, cell-to-cell communication, and the launching of programmes for host invasion. All these processes require recognition of target messenger RNAs by the sRNAs. This review summarizes recent results that have provided insights into how bacterial sRNAs are recruited into effector ribonucleoprotein complexes that can seek out and act upon target transcripts. The results hint at how sRNAs and their protein partners act as pattern-matching search engines that efficaciously regulate gene expression, by performing with specificity and speed while avoiding off-target effects. The requirements for efficient searches of RNA patterns appear to be common to all domains of life. © 2017 The Author(s).

  9. RNA search engines empower the bacterial intranet

    PubMed Central

    Dendooven, Tom

    2017-01-01

    RNA acts not only as an information bearer in the biogenesis of proteins from genes, but also as a regulator that participates in the control of gene expression. In bacteria, small RNA molecules (sRNAs) play controlling roles in numerous processes and help to orchestrate complex regulatory networks. Such processes include cell growth and development, response to stress and metabolic change, transcription termination, cell-to-cell communication, and the launching of programmes for host invasion. All these processes require recognition of target messenger RNAs by the sRNAs. This review summarizes recent results that have provided insights into how bacterial sRNAs are recruited into effector ribonucleoprotein complexes that can seek out and act upon target transcripts. The results hint at how sRNAs and their protein partners act as pattern-matching search engines that efficaciously regulate gene expression, by performing with specificity and speed while avoiding off-target effects. The requirements for efficient searches of RNA patterns appear to be common to all domains of life. PMID:28710287

  10. 46 CFR 11.502 - Additional requirements for engineer endorsements.

    Code of Federal Regulations, 2013 CFR

    2013-10-01

    ... 46 Shipping 1 2013-10-01 2013-10-01 false Additional requirements for engineer endorsements. 11... SEAMEN REQUIREMENTS FOR OFFICER ENDORSEMENTS Professional Requirements for Engineer Officer § 11.502 Additional requirements for engineer endorsements. (a) For all original and raise of grade of engineer...

  11. 46 CFR 11.502 - Additional requirements for engineer endorsements.

    Code of Federal Regulations, 2010 CFR

    2010-10-01

    ... 46 Shipping 1 2010-10-01 2010-10-01 false Additional requirements for engineer endorsements. 11... SEAMEN REQUIREMENTS FOR OFFICER ENDORSEMENTS Professional Requirements for Engineer Officer § 11.502 Additional requirements for engineer endorsements. (a) For all original and raise of grade of engineer...

  12. 46 CFR 11.502 - Additional requirements for engineer endorsements.

    Code of Federal Regulations, 2012 CFR

    2012-10-01

    ... 46 Shipping 1 2012-10-01 2012-10-01 false Additional requirements for engineer endorsements. 11... SEAMEN REQUIREMENTS FOR OFFICER ENDORSEMENTS Professional Requirements for Engineer Officer § 11.502 Additional requirements for engineer endorsements. (a) For all original and raise of grade of engineer...

  13. 46 CFR 11.502 - Additional requirements for engineer endorsements.

    Code of Federal Regulations, 2011 CFR

    2011-10-01

    ... 46 Shipping 1 2011-10-01 2011-10-01 false Additional requirements for engineer endorsements. 11... SEAMEN REQUIREMENTS FOR OFFICER ENDORSEMENTS Professional Requirements for Engineer Officer § 11.502 Additional requirements for engineer endorsements. (a) For all original and raise of grade of engineer...

  14. Turnaround Time Modeling for Conceptual Rocket Engines

    NASA Technical Reports Server (NTRS)

    Nix, Michael; Staton, Eric J.

    2004-01-01

    Recent years have brought about a paradigm shift within NASA and the Space Launch Community regarding the performance of conceptual design. Reliability, maintainability, supportability, and operability are no longer effects of design; they have moved to the forefront and are affecting design. A primary focus of this shift has been a planned decrease in vehicle turnaround time. Potentials for instituting this decrease include attacking the issues of removing, refurbishing, and replacing the engines after each flight. less, it is important to understand the operational affects of an engine on turnaround time, ground support personnel and equipment. One tool for visualizing this relationship involves the creation of a Discrete Event Simulation (DES). A DES model can be used to run a series of trade studies to determine if the engine is meeting its requirements, and, if not, what can be altered to bring it into compliance. Using DES, it is possible to look at the ways in which labor requirements, parallel maintenance versus serial maintenance, and maintenance scheduling affect the overall turnaround time. A detailed DES model of the Space Shuttle Main Engines (SSME) has been developed. Trades may be performed using the SSME Processing Model to see where maintenance bottlenecks occur, what the benefits (if any) are of increasing the numbers of personnel, or the number and location of facilities, in addition to trades previously mentioned, all with the goal of optimizing the operational turnaround time and minimizing operational cost. The SSME Processing Model was developed in such a way that it can easily be used as a foundation for developing DES models of other operational or developmental reusable engines. Performing a DES on a developmental engine during the conceptual phase makes it easier to affect the design and make changes to bring about a decrease in turnaround time and costs.

  15. Liquid rocket booster integration study. Volume 3: Study products. Part 2: Sections 8-19

    NASA Technical Reports Server (NTRS)

    1988-01-01

    The impacts of introducing liquid rocket booster engines (LRB) into the Space Transportation System (STS)/Kennedy Space Center (KSC) launch environment are identified and evaluated. Proposed ground systems configurations are presented along with a launch site requirements summary. Prelaunch processing scenarios are described and the required facility modifications and new facility requirements are analyzed. Flight vehicle design recommendations to enhance launch processing are discussed. Processing approaches to integrate LRB with existing STS launch operations are evaluated. The key features and significance of launch site transition to a new STS configuration in parallel with ongoing launch activities are enumerated. This volume is part two of the study products section of the five volume series.

  16. Liquid rocket booster integration study. Volume 3, part 1: Study products

    NASA Technical Reports Server (NTRS)

    1988-01-01

    The impacts of introducing liquid rocket booster engines (LRB) into the Space Transportation System (STS)/Kennedy Space Center (KSC) launch environment are identified and evaluated. Proposed ground systems configurations are presented along with a launch site requirements summary. Prelaunch processing scenarios are described and the required facility modifications and new facility requirements are analyzed. Flight vehicle design recommendations to enhance launch processing are discussed. Processing approaches to integrate LRB with existing STS launch operations are evaluated. The key features and significance of launch site transition to a new STS configuration in parallel with ongoing launch activities are enumerated. This volume is part one of the study products section of the five volume series.

  17. Feasibility study of an Integrated Program for Aerospace-vehicle Design (IPAD) system. Volume 3: Engineering creative/evaluation processes, phase 1, task 2

    NASA Technical Reports Server (NTRS)

    Garrocq, C. A.; Hosek, J. J.

    1973-01-01

    A series of functional flow charts are considered that were developed to properly identify and record the degree of participation of the disciplines considered in this feasibility study and the type of data required in the design process.

  18. Teacher-Led Design of an Adaptive Learning Environment

    ERIC Educational Resources Information Center

    Mavroudi, Anna; Hadzilacos, Thanasis; Kalles, Dimitris; Gregoriades, Andreas

    2016-01-01

    This paper discusses a requirements engineering process that exemplifies teacher-led design in the case of an envisioned system for adaptive learning. Such a design poses various challenges and still remains an open research issue in the field of adaptive learning. Starting from a scenario-based elicitation method, the whole process was highly…

  19. Engineering and Safety Partnership Enhances Safety of the Space Shuttle Program (SSP)

    NASA Technical Reports Server (NTRS)

    Duarte, Alberto

    2007-01-01

    Project Management must use the risk assessment documents (RADs) as tools to support their decision making process. Therefore, these documents have to be initiated, developed, and evolved parallel to the life of the project. Technical preparation and safety compliance of these documents require a great deal of resources. Updating these documents after-the-fact not only requires substantial increase in resources - Project Cost -, but this task is also not useful and perhaps an unnecessary expense. Hazard Reports (HRs), Failure Modes and Effects Analysis (FMEAs), Critical Item Lists (CILs), Risk Management process are, among others, within this category. A positive action resulting from a strong partnership between interested parties is one way to get these documents and related processes and requirements, released and updated in useful time. The Space Shuttle Program (SSP) at the Marshall Space Flight Center has implemented a process which is having positive results and gaining acceptance within the Agency. A hybrid Panel, with equal interest and responsibilities for the two larger organizations, Safety and Engineering, is the focal point of this process. Called the Marshall Safety and Engineering Review Panel (MSERP), its charter (Space Shuttle Program Directive 110 F, April 15, 2005), and its Operating Control Plan emphasizes the technical and safety responsibilities over the program risk documents: HRs; FMEA/CILs; Engineering Changes; anomalies/problem resolutions and corrective action implementations, and trend analysis. The MSERP has undertaken its responsibilities with objectivity, assertiveness, dedication, has operated with focus, and has shown significant results and promising perspectives. The MSERP has been deeply involved in propulsion systems and integration, real time technical issues and other relevant reviews, since its conception. These activities have transformed the propulsion MSERP in a truly participative and value added panel, making a difference for the safety of the Space Shuttle Vehicle, its crew, and personnel. Because of the MSERP's valuable contribution to the assessment of safety risk for the SSP, this paper also proposes an enhanced Panel concept that takes this successful partnership concept to a higher level of 'true partnership'. The proposed panel is aimed to be responsible for the review and assessment of all risk relative to Safety for new and future aerospace and related programs.

  20. Research and engineering assessment of biological solubilization of phosphate

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

    Rogers, R.D.; McIlwain, M.E.; Losinski, S.J.

    This research and engineering assessment examined a microbial phosphate solubilization process as a method of recovering phosphate from phosphorus containing ore compared to the existing wet acid and electric arc methods. A total of 860 microbial isolates, collected from a range of natural environments were tested for their ability to solubilize phosphate from rock phosphate. A bacterium (Pseudomonas cepacia) was selected for extensive characterization and evaluation of the mechanism of phosphate solubilization and of process engineering parameters necessary to recover phosphate from rock phosphate. These studies found that concentration of hydrogen ion and production of organic acids arising from oxidationmore » of the carbon source facilitated microbial solubilization of both pure chemical insoluble phosphate compounds and phosphate rock. Genetic studies found that phosphate solubilization was linked to an enzyme system (glucose dehydrogenase). Process-related studies found that a critical solids density of 1% by weight (ore to liquid) was necessary for optimal solubilization. An engineering analysis evaluated the cost and energy requirements for a 2 million ton per year sized plant, whose size was selected to be comparable to existing wet acid plants.« less

Some links on this page may take you to non-federal websites. Their policies may differ from this site.
Top