Search NASA⌕ Search

SEARCH · Search NASA

Results for “system engineering program”

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

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

At least 91 records · Page 5
All sourcesNASA NTRSDOE OSTI
NASA NTRS2004

Test Planning Approach and Lessons

As NASA began technology risk reduction activities and planning for the next generation launch vehicle under the Space Launch Initiative (SLI), now the Next Generation Launch Technology (NGLT) Program, a review of past large liquid rocket engine development programs was performed. The intent of the review was to identify any significant lessons from the development testing programs that could be applied to current and future engine development programs. Because the primary prototype engine in design at the time of this study was the Boeing-Rocketdyne RS-84, the study was slightly biased towards LOX/RP-1 liquid propellant engines. However, the significant lessons identified are universal. It is anticipated that these lessons will serve as a reference for test planning in the Engine Systems Group at Marshall Space Flight Center (MSFC). Towards the end of F-1 and J-2 engine development testing, NASA/MSFC asked Rocketdyne to review those test programs. The result was a document titled, Study to Accelerate Development by Test of a Rocket Engine (R-8099). The "intent (of this study) is to apply this thinking and learning to more efficiently develop rocket engines to high reliability with improved cost effectivenes" Additionally, several other engine programs were reviewed - such as SSME, NSTS, STME, MC-1, and RS-83- to support or refute the R-8099. R-8099 revealed two primary lessons for test planning, which were supported by the other engine development programs. First, engine development programs can benefit from arranging the test program for engine system testing as early as feasible. The best test for determining environments is at the system level, the closest to the operational flight environment. Secondly, the component testing, which tends to be elaborate, should instead be geared towards reducing risk to enable system test. Technical risk can be reduced at the component level, but the design can only be truly verified and validated after engine system testing.

Parkinson, Douglas A.↗
NASA NTRSDate not supplied

Methods for Developing Successful Systems Engineers

Systems Engineering (SE) is a complex and challenging field that incorporates the knowledge of systems engineering processes, the ability to synthesize a wide-range of engineering disciplines, and the ability to lead a team of people to successfully accomplish the goals of a project. It requires hard technical skills and soft-skill leadership savvy. As a result, three main development needs are identified: 1) Knowledge of SE processes, the benefits of these processes to a project and their tailored application 2) Knowledge of a wide-range of engineering disciplines, how they interrelate in a system, and the development of sound technical judgement 3) Team leadership to direct and motivate a team of subsystem and discipline experts This paper describes the establishment of a comprehensive training and development program for Systems Engineers at NASA Ames Research Center that addresses in part each of these three areas from the perspective of the implementing manager. A variety of methods have been utilized including the establishment of a SE Community of Practice, a unique and innovative web tool, on-line videos, classroom training in NASA’s 17 Common Technical Processes, guidance on the tailored application of these processes, monthly technical talks, mentoring in both technical judgment and team leadership, and NASA’s Leadership Development Programs. While much of professional SE development must come through project experience, the approaches listed above can accelerate development. The diversity of skills required of Systems Engineering demands a multi-faceted approach to successfully train and develop this critical skill.

development↗
NASA NTRSDate not supplied

Methods for Developing Successful Systems Engineers

Systems Engineering (SE) is a complex and challenging field that incorporates the knowledge of systems engineering processes, the ability to synthesize a wide-range of engineering disciplines, and the ability to lead a team of people to successfully accomplish the goals of a project. It requires hard technical skills and soft-skill leadership savvy. As a result, three main development needs are identified: 1. Knowledge of SE processes, the benefits of these processes to a project and their tailored application 2. Knowledge of a wide-range of engineering disciplines, how they interrelate in a system, and the development of sound technical judgement 3. Team leadership to direct and motivate a team of subsystem and discipline experts This paper describes the establishment of a comprehensive training and development program for Systems Engineers at NASA Ames Research Center that addresses in part each of these three areas from the perspective of the implementing manager. A variety of methods have been utilized including the establishment of a SE Community of Practice, a unique and innovative web tool, on-line videos, classroom training in NASA’s 17 Common Technical Processes, guidance on the tailored application of these processes, monthly technical talks, mentoring in both technical judgment and team leadership, and NASA’s Leadership Development Programs. While much of professional SE development must come through project experience, the approaches listed above can accelerate development. The diversity of skills required of Systems Engineering demands a multi-faceted approach to successfully train and develop this critical skill.

development↗
NASA NTRS2011

Spacecraft Testing Programs: Adding Value to the Systems Engineering Process

Testing has long been recognized as a critical component of spacecraft development activities - yet many major systems failures may have been prevented with more rigorous testing programs. The question is why is more testing not being conducted? Given unlimited resources, more testing would likely be included in a spacecraft development program. Striking the right balance between too much testing and not enough has been a long-term challenge for many industries. The objective of this paper is to discuss some of the barriers, enablers, and best practices for developing and sustaining a strong test program and testing team. This paper will also explore the testing decision factors used by managers; the varying attitudes toward testing; methods to develop strong test engineers; and the influence of behavior, culture and processes on testing programs. KEY WORDS: Risk, Integration and Test, Validation, Verification, Test Program Development

Britton, Keith J.↗
NASA NTRS2015

Technology Readiness Level Assessment Process as Applied to NASA Earth Science Missions

Technology assessments of fourteen science instruments were conducted within NASA using the NASA Technology Readiness Level (TRL) Metric. The instruments were part of three NASA Earth Science Decadal Survey missions in pre-formulation. The Earth Systematic Missions Program (ESMP) Systems Engineering Working Group (SEWG), composed of members of three NASA Centers, provided a newly modified electronic workbook to be completed, with instructions. Each instrument development team performed an internal assessment of its technology status, prepared an overview of its instrument, and completed the workbook with the results of its assessment. A team from the ESMP SEWG met with each instrument team and provided feedback. The instrument teams then reported through the Program Scientist for their respective missions to NASA's Earth Science Division (ESD) on technology readiness, taking the SEWG input into account. The instruments were found to have a range of TRL from 4 to 7. Lessons Learned are presented; however, due to the competition-sensitive nature of the assessments, the results for specific missions are not presented. The assessments were generally successful, and produced useful results for the agency. The SEWG team identified a number of potential improvements to the process. Particular focus was on ensuring traceability to guiding NASA documents, including the NASA Systems Engineering Handbook. The TRL Workbook has been substantially modified, and the revised workbook is described.

Systems Engineering↗
NASA NTRS1977

Study of Lyndon B. Johnson Space Center utility systems

The results of an engineering study of potential energy saving utility system modifications for the NASA Lyndon B. Johnson Space Center are presented. The objective of the study was to define and analyze utility options that would provide facility energy savings in addition to the approximately 25 percent already achieved through an energy loads reduction program. A systems engineering approach was used to determine total system energy and cost savings resulting from each of the ten major options investigated. The results reported include detailed cost analyses and cost comparisons of various options. Cost are projected to the year 2000. Also included are a brief description of a mathematical model used for the analysis and the rationale used for a site survey to select buildings suitable for analysis.

Redding, T. E.↗
NASA NTRS2014

Implementation of the Orbital Maneuvering Systems Engine and Thrust Vector Control for the European Service Module

The European Space Agency (ESA) has entered into a partnership with the National Aeronautics and Space Administration (NASA) to develop and provide the Service Module (SM) for the Orion Multipurpose Crew Vehicle (MPCV) Program. The European Service Module (ESM) will provide main engine thrust by utilizing the Space Shuttle Program Orbital Maneuvering System Engine (OMS-E). Thrust Vector Control (TVC) of the OMS-E will be provided by the Orbital Maneuvering System (OMS) TVC, also used during the Space Shuttle Program. NASA will be providing the OMS-E and OMS TVC to ESA as Government Furnished Equipment (GFE) to integrate into the ESM. This presentation will describe the OMS-E and OMS TVC and discuss the implementation of the hardware for the ESM.

Orbital Maneuvering System↗
NASA NTRS1978

Automated process planning system

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.

Mann, W.↗
NASA NTRS2011

SRMS History, Evolution and Lessons Learned

Early in the development of the Space Shuttle, it became clear that NASA needed a method of deploying and retrieving payloads from the payload bay. The Shuttle Remote Manipulator System (SRMS) was developed to fill this need. The 50 foot long robotic arm is an anthropomorphic design consisting of three electromechanical joints, six degrees of freedom, and two boom segments. Its composite boom construction provided a light weight solution needed for space operations. Additionally, a method of capturing payloads with the arm was required and a unique End Effector was developed using an electromechanical snare mechanism. The SRMS is operated using a Displays and Controls Panel and hand controllers located within the aft crew compartment of the shuttle. Although the SRMS was originally conceived to deploy and retrieve payloads, its generic capabilities allowed it to perform many other functions not originally conceived of. Over the years it has been used for deploying and retrieving constrained and free flying payloads, maneuvering and supporting EVA astronauts, satellite repair, International Space Station construction, and as a viewing aid for on-orbit International Space Station operations. After the Columbia accident, a robotically compatible Orbiter Boom Sensor System (OBSS) was developed and used in conjunction with the SRMS to scan the Thermal Protection System (TPS) of the shuttle. These scans ensure there is not a breach of the TPS prior to shuttle re-entry. Ground operations and pre mission simulation, analysis and planning played a major role in the success of the SRMS program. A Systems Engineering Simulator (SES) was developed to provide a utility complimentary to open loop engineering simulations. This system provided a closed-loop real-time pilot-driven simulation giving visual feedback, display and control panel interaction, and integration with other vehicle systems, such as GN&C. It has been useful for many more applications than traditional training. Evolution of the simulations, guided by the Math Model Working Group, showed the utility of input from multiple modeling groups with a structured forum for discussion.There were many unique development challenges in the areas of hardware, software, certification, modeling and simulation. Over the years, upgrades and enhancements were implemented to increase the capability, performance and safety of the SRMS. The history and evolution of the SRMS program provided many lessons learned that can be used for future space robotic systems.

Jorgensen, Glenn↗
NASA NTRS2013

Exploring Mission Concepts with the JPL Innovation Foundry A-Team

The JPL Innovation Foundry has established a new approach for exploring, developing, and evaluating early concepts called the A-Team. The A-Team combines innovative collaborative methods with subject matter expertise and analysis tools to help mature mission concepts. Science, implementation, and programmatic elements are all considered during an A-Team study. Methods are grouped by Concept Maturity Level (CML), from 1 through 3, including idea generation and capture (CML 1), initial feasibility assessment (CML 2), and trade space exploration (CML 3). Methods used for each CML are presented, and the key team roles are described from two points of view: innovative methods and technical expertise. A-Team roles for providing innovative methods include the facilitator, study lead, and assistant study lead. A-Team roles for providing technical expertise include the architect, lead systems engineer, and integration engineer. In addition to these key roles, each A-Team study is uniquely staffed to match the study topic and scope including subject matter experts, scientists, technologists, flight and instrument systems engineers, and program managers as needed. Advanced analysis and collaborative engineering tools (e.g. cost, science traceability, mission design, knowledge capture, study and analysis support infrastructure) are also under development for use in A-Team studies and will be discussed briefly. The A-Team facilities provide a constructive environment for innovative ideas from all aspects of mission formulation to eliminate isolated studies and come together early in the development cycle when they can provide the biggest impact. This paper provides an overview of the A-Team, its study processes, roles, methods, tools and facilities.

Team Eureka↗
NASA NTRS2017

Space Launch System, Core Stage, Structural Test Design and Implementation

As part of the National Aeronautics and Space Administration's (NASA) Space Launch System (SLS) Program, engineers at NASA's Marshall Space Flight Center (MSFC) in Huntsville, Alabama are working to design, develop and implement the SLS Core Stage structural testing. The SLS will have the capability to return humans to the Moon and beyond and its first launch is scheduled for December of 2017. The SLS Core Stage consist of five major elements; Forward Skirt, Liquid Oxygen (LOX) tank, Intertank (IT), Liquid Hydrogen (LH2) tank and the Engine Section (ES). Structural Test Articles (STA) for each of these elements are being designed and produced by Boeing at Michoud Assembly Facility located in New Orleans, La. The structural test for the Core Stage STAs (LH2, LOX, IT and ES) are to be conducted by the MSFC Test Laboratory. Additionally, the MSFC Test Laboratory manages the Structural Test Equipment (STE) design and development to support the STAs. It was decided early (April 2012) in the project life that the LH2 and LOX tank STAs would require new test stands and the Engine Section and Intertank would be tested in existing facilities. This decision impacted schedules immediately because the new facilities would require Construction of Facilities (C of F) funds that require congressional approval and long lead times. The Engine Section and Intertank structural test are to be conducted in existing facilities which will limit lead times required to support the first launch of SLS. With a SLS launch date of December, 2017 Boeing had a need date for testing to be complete by September of 2017 to support flight certification requirements. The test facilities were required to be ready by October of 2016 to support test article delivery. The race was on to get the stands ready before Test Article delivery and meet the test complete date of September 2017. This paper documents the past and current design and development phases and the supporting processes, tools, and methodology for supporting the SLS Core Stage STA test stands and related STE. The paper will address key requirements, system development activities and project challenges. Additionally, the interrelationships as well as interdependencies within the SLS project will be discussed.

Shaughnessy, Ray↗
NASA NTRS1975

Building a computer-aided design capability using a standard time share operating system

The paper describes how an integrated system of engineering computer programs can be built using a standard commercially available operating system. The discussion opens with an outline of the auxiliary functions that an operating system can perform for a team of engineers involved in a large and complex task. An example of a specific integrated system is provided to explain how the standard operating system features can be used to organize the programs into a simple and inexpensive but effective system. Applications to an aircraft structural design study are discussed to illustrate the use of an integrated system as a flexible and efficient engineering tool. The discussion concludes with an engineer's assessment of an operating system's capabilities and desirable improvements.

Sobieszczanski, J.↗
DOE OSTI2021

W-8 Production Liaison brochure [Slides]

W-8 is part of the Weapon Systems (W) Engineering Division. W Division provides the system engineering and program management necessary to sustain the safety, reliability, and security of Los Alamos National Laboratory’s assets in the active United States nuclear stockpile: the B61, W76, W78, and W88.

42 ENGINEERING↗
DOE OSTI2022

An Introduction to Los Alamos National Laboratory [Slides]

The Weapon Systems Engineering Division (W) provides the system engineering and program management necessary to sustain the safety, reliability, and security of the Los Alamos National Laboratory’s assets in the active United States nuclear stockpile - the B61, W76, W78 and W88. The Division generates key certification data for Annual Assessment supporting the Laboratory Director's letter to the President on the health of those warheads. This role demands ongoing surveillance of the active stockpile and evaluation of the potential impact of any issues through design, engineering, fabrication, testing using state-of-the-art computational simulation tools and engineering test facilities. The Division works in close liaison with the several production facilities across the nuclear security complex as well as with the customers in the US Navy and Air Force.

98 NUCLEAR DISARMAMENT, SAFEGUARDS, AND PHYSICAL P↗