Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Systems Engineering”

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

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

At least 1,585 records · Page 88
All sourcesNASA NTRSDOE OSTI
DOE OSTI2024

Design Basis Model for Hosting Small Modular Reactors

An aggressive transition from fossil fuels to other types of energy implies the need to construct a large number of nuclear power plants in the near future. However, the real and perceived risks of nuclear energy remain a significant impediment to this transition. This paper describes a comprehensive work process that combines the rigor of model-based systems engineering (MBSE) with 1) the Idaho National Laboratory's (INL) decades of experience with small reactors and with 2) modern project delivery processes. The objective is to reduce the risk of building new facilities or converting existing facilities to nuclear power generation.

42 ENGINEERING↗
NASA NTRS2019

In Space Assembled Telescope (ISAT) Study Preliminary Findings

“When is it advantageous to assemble telescopes in space rather than deploying them from launch vehicle fairings”? This question forms the crux of the objectives of a NASA study we have been conducting in collaboration with colleagues from different NASA centers, industry and academia. In this study, we have engaged a broad cross section of experts from the various fields of optics engineering, that is, telescope design and instrument design, structure and thermal engineering, robotics, launch system engineering, orbital mechanics, integration and testing, astrophysics, and NASA programmatics among others. Initial efforts began with a quick review of the current state of art of the component technologies that contribute towards an in-space assembled telescope. Then, leveraging the collective expertise of the diverse group of experts, we formulated a reference telescope design and attempted to develop a baseline approach to modularize the telescope into components amenable for robotic assembly. The group identified different trades associated with modularization and also developed a set of criteria to discern between the different options as revealed by the trades. Based on the modularization of the telescope, we will assess the impact of various launch vehicles, orbits for assembly and operation, robotic systems and operational approaches, and other related variables. From this, a concept to assemble the reference telescope in space from modular components will be developed. Based on this concept, and definition of the modules, we will develop a mission lifecycle plan for an assembled telescope over different phases of preliminary design, detailed design, assembly-test-and-integration, and in space operations. The mission lifecycle plan will be used to evaluate cost and risk implications of in-space assembly toward answering our fundamental question of the advantages, if any, of assembling a telescope in space as compared to self-deployment. In this paper, we summarize the objectives of the study, a review of the status of the underlying component technologies, a description of the methodology, including three different multi-day technical interchange meetings (TIMs), summary of findings from the TIMs and other related activities. In addition, a detailed description of the various factors that impact in-space assembly, their interplay and criteria for discerning among them, a preliminary description of the life cycle plan, including the test and integration plan, and initial observations on cost and risk implications will be included in the paper.

Mukherjee, Rudranarayan↗
NASA NTRS1981

Application of propagation predictions to Earth/space telecommunications system design

The corresponding between a given propagation phenomenon and system performance is considered. Propagation data are related to system performance parameters, allowing the systems engineer to perform the analyses determining how well requirements are met by a given system design, and enabling the systems engineer to modify that design if necessary. The various ways of specifying performance criteria for different kinds of systems are discussed, and a general procedure for system design is presented and demonstrated.

Source record↗
NASA NTRS1991

Capturing flight system test engineering expertise: Lessons learned

Within a few years, JPL will be challenged by the most active mission set in history. Concurrently, flight systems are increasingly more complex. Presently, the knowledge to conduct integration and test of spacecraft and large instruments is held by a few key people, each with many years of experience. JPL is in danger of losing a significant amount of this critical expertise, through retirement, during a period when demand for this expertise is rapidly increasing. The most critical issue at hand is to collect and retain this expertise and develop tools that would ensure the ability to successfully perform the integration and test of future spacecraft and large instruments. The proposed solution was to capture and codity a subset of existing knowledge, and to utilize this captured expertise in knowledge-based systems. First year results and activities planned for the second year of this on-going effort are described. Topics discussed include lessons learned in knowledge acquisition and elicitation techniques, life-cycle paradigms, and rapid prototyping of a knowledge-based advisor (Spacecraft Test Assistant) and a hypermedia browser (Test Engineering Browser). The prototype Spacecraft Test Assistant supports a subset of integration and test activities for flight systems. Browser is a hypermedia tool that allows users easy perusal of spacecraft test topics. A knowledge acquisition tool called ConceptFinder which was developed to search through large volumes of data for related concepts is also described and is modified to semi-automate the process of creating hypertext links.

Woerner, Irene Wong↗
NASA NTRSDate not supplied

Results from NASA Agile Teams Study

In order to meet the demands of the current global economy, a study of agile teams at NASA was conducted by the NASA Engineering and Safety Center (NESC) to explore how the Agency can become more adaptable and flexible due to several influences, including the maturity and availability of digital tools and NASA’s increased reliance on commercial providers. NESC Technical Discipline Teams (TDTs) perform annual studies to understand the needs of their stakeholders, establish a state of the discipline, and inform strategic planning efforts. As part of the 2022 interview series, the Systems Engineering TDT utilized the dissertation work of Dr. Jackelynne Silva-Martinez that focused on NASA agile teams. The Systems Engineering TDT partnered with the Software and Human Factors TDTs on the formulation of interview questions and subsequent solicitation of customer inputs, which helped attract diverse agile teams across the Agency. 34 participants were interviewed, including civil servants and contractors, with open-ended questions related to their teams’ adoption and transition to agile. Participants were also questioned about their perceptions of the implementation of agile approaches across the Agency. Results showed a consistent framing of agile as incremental knowledge growth, a way of showing progress, and as the incorporation of frequent customer feedback. However, participants emphasized a lack of a common understanding of agile across the Agency, which sometimes caused managers and engineers to be reluctant to accept and support them. Results also showed the most successful agile teams had formal training with over five years of agile experience, used retrospectives, and tailored their agile processes for their specific situation and needs. This paper provides details of the interview responses gathered in the study and suggests actions for NASA to become more agile.

NASA↗
NASA NTRS1975

TC-2 post Helios experiment data review

Data are presented from a systems postflight analysis of the Centaur Launch Vehicle and Helios. Also given is a comparison of data from preflight analyses. Topics examined are: (1) propellant behavior; (2) helium usage; (3) propellant tank pressurization; (4) propellant tank thermodynamics; (5) component heating; thermal control; and thermal protection system; (6) main engine system; (7) H2O2 consumption; (8) boost pump post-meco performance; and (9) an overview of other systems.

Source record↗
NASA NTRS1978

Update on the development of the Space Shuttle main engine /as of June 20, 1978/

During the last year, significant progress was made toward the development of the Space Shuttle Main Engine which will provide propulsion for the Space Shuttle Orbiter Vehicle. Component and subsystem testing was conducted at the Rocketdyne Santa Susana Field Laboratory on combustion devices, turbomachinery, and the engine POGO suppression system. Engine testing continued at the National Space Technology Laboratories on both single engines and a three-engine cluster. As a result of these tests, hardware limitations were identified and design modifications were incorporated and evaluated by further testing. Current effort is being directed toward the delivery of the first flight engines and certification of the SSME for manned flight.

Johnson, J. R.↗
NASA NTRS1992

Integration of tools for the Design and Assessment of High-Performance, Highly Reliable Computing Systems (DAHPHRS), phase 1

Systems for Space Defense Initiative (SDI) space applications typically require both high performance and very high reliability. These requirements present the systems engineer evaluating such systems with the extremely difficult problem of conducting performance and reliability trade-offs over large design spaces. A controlled development process supported by appropriate automated tools must be used to assure that the system will meet design objectives. This report describes an investigation of methods, tools, and techniques necessary to support performance and reliability modeling for SDI systems development. Models of the JPL Hypercubes, the Encore Multimax, and the C.S. Draper Lab Fault-Tolerant Parallel Processor (FTPP) parallel-computing architectures using candidate SDI weapons-to-target assignment algorithms as workloads were built and analyzed as a means of identifying the necessary system models, how the models interact, and what experiments and analyses should be performed. As a result of this effort, weaknesses in the existing methods and tools were revealed and capabilities that will be required for both individual tools and an integrated toolset were identified.

Scheper, C.↗
NASA NTRS1989

Petite Amateur Navy Satellite (PANSAT)

The Naval Postgraduate School's (NPS) Space Systems Academic Group (SSAG) is designing and developing a small communications satellite for launch aboard the shuttle as a complex autonomous payload (CAP). The objectives of PANSAT are three-fold. First, PANSAT will provide an ideal educational tool for the officer students at NPS supporting Space Systems Engineering and Space Systems Operations with hands-on hardware development. Second, the satellite will provide digital store-and-forward communications, or packet radio, for the amateur radio community. The third objective is to provide a low-cost, space-based platform for small experiments. PANSAT will be launched from the shuttle at a nominal altitude of 200 n.m. and an inclination of at least 37 degrees. The satellite weight is 150 lbs. Since there is no attitude control, eight dipole whip antennas will be used to provide isotropic ground coverage for communications. FM digital communications will be used with up-link and down-link on a single frequency in the amateur band of 437.25 MHz. A maximum 50 kHz of bandwidth is envisioned for the satellite. The expected lifetime of the satellite is 1 1/2 to 2 years before atmospheric reentry. The PANSAT design consists of the following: communications subsystem (COMM); computer, or data processor and sequencer (DP&S); power subsystem; structure subsystem; and experiment payload.

Sakoda, D.↗
NASA NTRS1992

Teamwork for Oversight of Processes and Systems (TOPS). Implementation guide for TOPS version 2.0, 10 August 1992

As the nation redefines priorities to deal with a rapidly changing world order, both government and industry require new approaches for oversight of management systems, particularly for high technology products. Declining defense budgets will lead to significant reductions in government contract management personnel. Concurrently, defense contractors are reducing administrative and overhead staffing to control costs. These combined pressures require bold approaches for the oversight of management systems. In the Spring of 1991, the DPRO and TRW created a Process Action Team (PAT) to jointly prepare a Performance Based Management (PBM) system titled Teamwork for Oversight of Processes and Systems (TOPS). The primary goal is implementation of a performance based management system based on objective data to review critical TRW processes with an emphasis on continuous improvement. The processes are: Finance and Business Systems, Engineering and Manufacturing Systems, Quality Assurance, and Software Systems. The team established a number of goals: delivery of quality products to contractual terms and conditions; ensure that TRW management systems meet government guidance and good business practices; use of objective data to measure critical processes; elimination of wasteful/duplicative reviews and audits; emphasis on teamwork--all efforts must be perceived to add value by both sides and decisions are made by consensus; and synergy and the creation of a strong working trust between TRW and the DPRO. TOPS permits the adjustment of oversight resources when conditions change or when TRW systems performance indicate either an increase or decrease in surveillance is appropriate. Monthly Contractor Performance Assessments (CPA) are derived from a summary of supporting system level and process-level ratings obtained from objective process-level data. Tiered, objective, data-driven metrics are highly successful in achieving a cooperative and effective method of measuring performance. The teamwork-based culture developed by TOPS proved an unequaled success in removing adversarial relationships and creating an atmosphere of continuous improvement in quality processes at TRW. The new working relationship does not decrease the responsibility or authority of the DPRO to ensure contract compliance and it permits both parties to work more effectively to improve total quality and reduce cost. By emphasizing teamwork in developing a stronger approach to efficient management of the defense industrial base TOPS is a singular success.

Strand, Albert A.↗
NASA NTRS1995

Use of agents to implement an integrated computing environment

Integrated Product and Process Development (IPPD) embodies the simultaneous application to both system and quality engineering methods throughout an iterative design process. The use of IPPD results in the time-conscious, cost-saving development of engineering systems. To implement IPPD, a Decision-Based Design perspective is encapsulated in an approach that focuses on the role of the human designer in product development. The approach has two parts and is outlined in this paper. First, an architecture, called DREAMS, is being developed that facilitates design from a decision-based perspective. Second, a supporting computing infrastructure, called IMAGE, is being designed. Agents are used to implement the overall infrastructure on the computer. Successful agent utilization requires that they be made of three components: the resource, the model, and the wrap. Current work is focused on the development of generalized agent schemes and associated demonstration projects. When in place, the technology independent computing infrastructure will aid the designer in systematically generating knowledge used to facilitate decision-making.

Hale, Mark A.↗
NASA NTRS2002

Fundamental Boiling and RP-1 Freezing Experiments

The prestart thermal conditioning of the hardware in LOX (liquid oxygen) systems involve heat transfer between LOX and metal where boiling plays a large role. Information is easily found on nucleate boiling, maximum heat flux, minimum heat flux and film boiling for common fluids like water. After looking at these standard correlations it was felt more data was needed for the cool down side transition boiling for the LN2 and LOX. In particular interest is the film boiling values, the temperature at which transition begins and the slope as peak heat flux is approached. The ultimate goal is an array of boiling heat transfer coefficient as a function of surface temperature which can be used in the chilldown model of the feed system, engine and bleed system for X-34. The first experiment consisted of an actual MC-1 LOX Impeller which had been machined backwards, that was instrumented with 17 surface thermocouples and submerged in liquid nitrogen. The thermocouples were installed on metal thicknesses varying from the thin inducer to the thick hub.

Goode, Brian↗
NASA NTRS2005

Rocket Engine Nozzle Side Load Transient Analysis Methodology: A Practical Approach

During the development stage, in order to design/to size the rocket engine components and to reduce the risks, the local dynamic environments as well as dynamic interface loads must be defined. There are two kinds of dynamic environment, i.e. shock transients and steady-state random and sinusoidal vibration environments. Usually, the steady-state random and sinusoidal vibration environments are scalable, but the shock environments are not scalable. In other words, based on similarities only random vibration environments can be defined for a new engine. The methodology covered in this paper provides a way to predict the shock environments and the dynamic loads for new engine systems and new engine components in the early stage of new engine development or engine nozzle modifications.

Shi, John J.↗
NASA NTRS2005

Human Planetary Landing System (HPLS) Capability Roadmap NRC Progress Review

Capability Roadmap Team. Capability Description, Scope and Capability Breakdown Structure. Benefits of the HPLS. Roadmap Process and Approach. Current State-of-the-Art, Assumptions and Key Requirements. Top Level HPLS Roadmap. Capability Presentations by Leads. Mission Drivers Requirements. "AEDL" System Engineering. Communication & Navigation Systems. Hypersonic Systems. Super to Subsonic Decelerator Systems. Terminal Descent and Landing Systems. A Priori In-Situ Mars Observations. AEDL Analysis, Test and Validation Infrastructure. Capability Technical Challenges. Capability Connection Points to other Roadmaps/Crosswalks. Summary of Top Level Capability. Forward Work.

Manning, Rob↗
NASA NTRS2010

Verification and Implementation of Operations Safety Controls for Flight Missions

Approximately eleven years ago, the International Space Station launched the first module from Russia, the Functional Cargo Block (FGB). Safety and Mission Assurance (S&MA) Operations (Ops) Engineers played an integral part in that endeavor by executing strict flight product verification as well as continued staffing of S&MA's console in the Mission Evaluation Room (MER) for that flight mission. How were these engineers able to conduct such a complicated task? They conducted it based on product verification that consisted of ensuring that safety requirements were adequately contained in all flight products that affected crew safety. S&MA Ops engineers apply both systems engineering and project management principles in order to gain a appropriate level of technical knowledge necessary to perform thorough reviews which cover the subsystem(s) affected. They also ensured that mission priorities were carried out with a great detail and success.

Jones, Cheryl L.↗
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 NTRS2012

MBSE in Development: SMAP Pilot Project

Customer-focused objective: Provide value to a flight project using Model-Based Systems Engineering (MBSE) methodology and products. Institution-focused objective: Advance and improve our systems engineering practices, leveraging MBSE where applicable: Streamline our interfaces across JPL Divisions, to provide better cross-organization products; Streamline our interfaces across lifecycle phase boundaries; Update our SE practices to make them more competitive and able to handle systems of ever-increasing complexity.

Soil Moisture Active and Passive (SMAP)↗