Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “engineered systems”

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,441 records · Page 80

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↗

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↗

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↗

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

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

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

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

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

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↗

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

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↗

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

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↗

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)↗

Agile: From Software to Mission Systems

To maximize efficiency and flexibility in Mission Operations System (MOS) design, we are evolving principles from agile and lean methods for software, to the complete mission system. This allows for reduced operational risk at reduced cost, and achieves a more effective design through early integration of operations into mission system engineering and flight system design. The core principles are assessment of capability through demonstration, risk reduction through targeted experiments, early test and deployment, and maturation of processes and tools through use.

Trimble, Jay↗

Internal combustion engine and piston having stepped combustion bowl with non-axisymmetric profile

An internal combustion engine system includes an engine housing having a combustion cylinder, and a piston movable within the combustion cylinder to increase a pressure therein to an autoignition threshold for injected fuel. The piston includes a piston crown having a combustion face forming a combustion bowl, and varied in profile to form jet-jet interaction limiters at locations offset from fuel spray jet paths from a fuel injector. The jet-jet interaction limiters include a bowl component and a step component protruding, respectively, within the combustion bowl and a step located transitioning between the combustion bowl and a circumferential rim of the piston. Limiting jet-jet interaction limits soot production in exhaust produced by the engine.

Anders, Jonathan William↗

MFANS 2024 - Formally Proving Characteristics of Cyber-Physical Systems

Cyber-physical systems (CPS) are engineered systems that rely on the smooth integration of computational algorithms and physical elements. This integration presents new challenges for verifying that systems will behave as expected. The goal of this presentation is to present current challenges and potential solutions for the formal verification of cyber-physical systems. For cyber systems, formal methods refer to systematically rigorous mathematical techniques employed in the specification, development, analysis, and verification of both software and hardware systems. Recent advancements in computer science have yielded sophisticated tools specifically designed to address challenges associated with formal methods in complex systems. These tools leverage various foundational concepts such as logic, formal languages, program semantics, type systems, type theory, and automata theory. A notable achievement in the application of formal methods is the seL4 microkernel, claimed to be the first general-purpose operating-system kernel to be verified. Its proof implies the absence of bugs and guarantees that the kernel meets specifications. For physical systems, dynamic and control theory has a history of using rigorous analytic techniques to prove functional correctness. Lyapunov, optimal, classical, modern, and robust control theories all provide rigorous mathematical methods both to analyze system performance and to design controller that can be guaranteed to meet certain objectives. Recent computational techniques like level set theory and reachability analysis provide assertions that a system's state will avoid unsafe regions. Even though success has been independently achieved for cyber systems and physical systems, the integration of such systems creates new challenges. In particular, there is an obvious discrepancy between finite-state machines and infinite-state systems, resulting in different approaches for modeling and analyzing these system. While it is possible to simulate hybrid systems, this provides only a demonstration of a performance and not proof. For hybrid systems, current formal methods and system analysis approaches typically require a workarounds to work on hybrid systems like CPS. This paper will outline the state of the art and limits of current practice for formally verifying CPS and will identify possible research directions that require attention.

97 MATHEMATICS AND COMPUTING↗