Search NASASearch

SEARCH · Search NASA

Results for “engineering process”

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 163 records · Page 9

Cell Libraries

A NASA contract led to the development of faster and more energy efficient semiconductor materials for digital integrated circuits. Gallium arsenide (GaAs) conducts electrons 4-6 times faster than silicon and uses less power at frequencies above 100-150 megahertz. However, the material is expensive, brittle, fragile and has lacked computer automated engineering tools to solve this problem. Systems & Processes Engineering Corporation (SPEC) developed a series of GaAs cell libraries for cell layout, design rule checking, logic synthesis, placement and routing, simulation and chip assembly. The system is marketed by Compare Design Automation.

Source record

The Rapid Response Radiation Survey (R3S) Mission Using the HISat Conformal Satellite Architecture

The Rapid Response Radiation Survey (R3S) experiment, designed as a quick turnaround mission to make radiation measurements in LEO, will fly as a hosted payload in partnership with NovaWurks using their Hyper-integrated Satlet (HiSat) architecture. The need for the mission arises as the Nowcast of Atmospheric Ionization Radiation for Aviation Safety (NAIRAS) model moves from a research effort into an operational radiation assessment tool. The data collected by R3S, in addition to the complementary data from a NASA Langley Research Center (LaRC) atmospheric balloon mission entitled Radiation Dosimetry Experiment (RaDX), will validate exposure prediction capabilities of NAIRAS. This paper discusses the development of the R3S experiment as made possible by use of the HiSat architecture. The system design and operational modes of the experiment are described, as well as the experiment interfaces to the HiSat satellite via the user defined adapter (UDA) provided by NovaWurks. This paper outlines the steps taken by the project to execute the R3S mission in the 4 months of design, build, and test. Finally, description of the engineering process is provided, including the use of facilitated rapid/concurrent engineering sessions, the associated documentation, and the review process employed.

Miller, Nathanael

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

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

Collaborative Systems Thinking: A Response to the Problems Faced by Systems Engineering's 'Middle Tier'

Experienced systems engineers are adept at more than implementing systems engineering processes: they utilize systems thinking to solve complex engineering problems. Within the space industry demographics and economic pressures are reducing the number of experienced systems engineers that will be available in the future. Collaborative systems thinking within systems engineering teams is proposed as a way to integrate systems engineers of various experience levels to handle complex systems engineering challenges. This paper uses the GOES-R Program Systems Engineering team to illustrate the enablers and barriers to team level systems thinking and to identify ways in which performance could be improved. Ways NASA could expand its engineering training to promote team-level systems thinking are proposed.

Phfarr, Barbara B.

A Study of Particle Size Metrics Using Non-Spherical Feedstock for Metal Additive Manufacturing

The goal of this work was to determine which standard particle size metric derived from optical analysis most closely approximates the sieved weight percent of irregularly shaped powder intended to be used for directed energy deposition. In this investigation, equivalent circle diameter, maximum diameter, minimum diameter, and perimeter are used as metrics to “virtually sieve” the particles in samples of irregularly shaped powder into the following particle size bins: <45 µm, 45 µm - 150 µm, and >150 µm. The percentage in the 45 µm - 150 µm bin is then compared to the weight percent of the powder mechanically sieved into this size range. The absolute difference between the virtually sieved percentage and the mechanically sieved percentage was assessed for 81 samples of mechanically-generated stainless steel 316L powder all produced under different processing conditions in an oscillation ball mill. This difference was found to be on average, the least with the minimum diameter assessed as an area percentage, followed by the equivalent diameter assessed as an area percentage, and then the maximum diameter assessed as a percentage of the total number of particles ranked third. These findings may be used by powder production process engineers and quality assurance personnel to assist in process control as more diverse additive manufacturing feedstocks become utilized.

Marcus Jackson

A Collaborative Vision for Deep Space Human Exploration

Artemis will be the first cooperative campaign among nations for crewed planetary exploration. This paradigm shift reflects a collaborative vision for deep space human exploration that embraces the concept that, “If you want to go fast, go alone; If you want to go far, go together.” This paper elaborates on the way the National Aeronautics and Space Administration(NASA)is striving to make its Moon to Mars effort a collaborative endeavor for long-term human exploration of deep space and for the international space community. The agency is making great strides in unifying its workforce, mission directorates, technical authorities, and centers behind shared goals and processes. Enhanced communication and a reinvigoration of systems engineering ideals have been a hallmark of that effort, guided by the Moon to Mars Architecture, which defines what NASA aims to accomplish and how it will execute those goals. This interdisciplinary approach ensures the Artemis campaign supports NASA’s engineering, science, and technology development goals. As of September 2024, over 43 nations have signed the Artemis Accords, which establish a common set of principles for peaceful cooperation in civil space exploration. Building off these efforts, NASA has been engaging in separate and distinct discussions about partner contributions to Artemis. International partnerships for the Artemis campaign include long-standing partners as well as agencies with which NASA has only more recently begun collaborating. The Gateway Program is an early example of both –benefitting from partnerships with Canada, Japan, and Europe forged though decades of cooperation on the International Space Station, as well as a new partnership with the United Arab Emirates. The agency’s Moon to Mars Objectives and Architecture unify the NASA workforce with common goals and shared systems-engineering processes. The architecture offers pathways for broader participation from industry, academia, and international partners. The agency evolves this collaborative approach through its annual Architecture Concept Review cycle, seeking input from the NASA workforce, and through workshops, from industry, academia, and the international space community to refine NASA’s roadmap for exploration. Exploring together, NASA and its partners are setting humanity on the path to long-term presence at the Moon and our eventual journey to Mars

Objective

Marshall Space Flight Center Ground Systems Development and Integration

Ground Systems Development and Integration performs a variety of tasks in support of the Mission Operations Laboratory (MOL) and other Center and Agency projects. These tasks include various systems engineering processes such as performing system requirements development, system architecture design, integration, verification and validation, software development, and sustaining engineering of mission operations systems that has evolved the Huntsville Operations Support Center (HOSC) into a leader in remote operations for current and future NASA space projects. The group is also responsible for developing and managing telemetry and command configuration and calibration databases. Personnel are responsible for maintaining and enhancing their disciplinary skills in the areas of project management, software engineering, software development, software process improvement, telecommunications, networking, and systems management. Domain expertise in the ground systems area is also maintained and includes detailed proficiency in the areas of real-time telemetry systems, command systems, voice, video, data networks, and mission planning systems.

Wade, Gina

The Rapid Response Radiation Survey (R3S) Mission Using the HiSat Conformal Satellite Architecture

The Rapid Response Radiation Survey (R3S) experiment, designed as a quick turnaround mission to make radiation measurements in Low Earth Orbit (LEO), will fly as a hosted payload in partnership with NovaWurks using their Hyper-integrated Satlet (HISat) architecture. The need for the mission arises as the Nowcast of Atmospheric Ionization Radiation for Aviation Safety (NAIRAS) model moves from a research effort into an operational radiation assessment tool. Currently, airline professionals are the second largest demographic of radiation workers and to date their radiation exposure is undocumented in the USA. The NAIRAS model seeks to fill this information gap. The data collected by R3S, in addition to the complementary data from a NASA Langley Research Center (LaRC) atmospheric balloon mission entitled Radiation Dosimetry Experiment (RaD-X), will validate exposure prediction capabilities of NAIRAS. The R3S mission collects total dose and radiation spectrum measurements using a Teledyne μDosimeter and a Liulin-6SA2 LED spectrometer. These two radiation sensors provide a cross correlated radiometric measurement in combination with the Honeywell HMR2300 Smart Digital Magnetometer. The magnetometer assesses the Earth's magnetic field in the LEO environment and allows radiation dose to be mapped as a function of the Earth's magnetic shielding. R3S is also unique in that the radiation sensors will be exposed on the outer surface of the spacecraft, possibly making this the first measurements of the LEO radiation environment with bare sensors. Viability of R3S as an extremely fast turnaround mission is due, in part, to the nature of the robust, well-defined interfaces of the conformal satellite HiSat Architecture. The HiSat architecture, which was developed with the support of the Defense Advanced Research Projects Agency's (DARPA's) Phoenix Program, enabled the R3S system to advance from the first concept to delivery of preliminary design review (PDR) level documents in 29 calendar days. The architecture allows for interface complexities between the specific devices and the satellite bus to be resolved in a standardized interface control document (ICD). The ICD provided a readymade framework to interface to the modular satellite bus. This modularity allowed for approximately 90% of the R3S system to be designed and fabricated in two months without constraint of the hosting satellite's development cycle. This paper discusses the development of the R3S experiment as made possible by use of the HiSat architecture. The system design and operational modes of the experiment are described, as well as the experiment interfaces to the HiSat satellite via the user defined adapter (UDA) provided by NovaWurks. This paper outlines the steps taken by the project to execute the R3S mission in the 4 months of design, build, and test. Additionally portrayed is the ground work done at LaRC to posture the organization for a fast response and the process by which the opportunity was identified as aligning with key strategic goals. Finally, a description of the engineering process is provided, including the use of facilitated rapid/concurrent engineering sessions, the associated documentation, and the review process employed.

Miller, Nathanael A.

Materials, Processes, and Environmental Engineering Network

Attention is given to the Materials, Processes, and Environmental Engineering Network (MPEEN), which was developed as a central holding facility for materials testing information generated by the Materials and Processes Laboratory of NASA-Marshall. It contains information from other NASA centers and outside agencies, and also includes the NASA Environmental Information System (NEIS) and Failure Analysis Information System (FAIS) data. The data base is NEIS, which is accessible through MPEEN. Environmental concerns are addressed regarding materials identified by the NASA Operational Environment Team (NOET) to be hazardous to the environment. The data base also contains the usage and performance characteristics of these materials.

White, Margo M.

A case study of the influences of audience and purpose on the composing processes of an engineer

The design and preliminary findings of a study of composing processes (on the job) of engineers, managers, and scientists is presented. The influences of audience and purpose on the composing process of engineers was of concern; specifically, the cognitive processes, physical behaviors, and factors that influence the evoluton of a piece of writing. An overview of the study, related literature, outlines of research design, and preliminary findings from a case study of engineers are given. It is suggested that teaching be adapted to help students learn to represent rhetorical problems to guide composing for effective writing.

Stalnaker, B. J.

Automation of the aircraft design process

The increasing use of the computer to automate the aerospace product development and engineering process is examined with emphasis on structural analysis and design. Examples of systems of computer programs in aerospace and other industries are reviewed and related to the characteristics of aircraft design in its conceptual, preliminary, and detailed phases. Problems with current procedures are identified, and potential improvements from optimum utilization of integrated disciplinary computer programs by a man/computer team are indicated.

Heldenfels, R. R.

Engineering Lessons Learned and Systems Engineering Applications

Systems Engineering is fundamental to good engineering, which in turn depends on the integration and application of engineering lessons learned. Thus, good Systems Engineering also depends on systems engineering lessons learned from within the aerospace industry being documented and applied. About ten percent of the engineering lessons learned documented in the NASA Lessons Learned Information System are directly related to Systems Engineering. A key issue associated with lessons learned datasets is the communication and incorporation of this information into engineering processes. As part of the NASA Technical Standards Program activities, engineering lessons learned datasets have been identified from a number of sources. These are being searched and screened for those having a relation to Technical Standards. This paper will address some of these Systems Engineering Lessons Learned and how they are being related to Technical Standards within the NASA Technical Standards Program, including linking to the Agency's Interactive Engineering Discipline Training Courses and the life cycle for a flight vehicle development program.

Gill, Paul S.

Let's Roll! Rolling Out or Deploying SEPG Assets

The topics covered in this slide presentation are: the general approach to software quality improvement (SQI) at Jet Propulsion Institute, the SQI deployment process, and lessons learned in regard to SQI. The Software Engineering Process Group (SEPG) is the group charged with SQI. The initial focus of the Software Quality Improvement (SQI) Project is on mission-critical software for flight projects, their spacecraft and instrument systems, and their ground systems.

process improvements

Lessons Learned in Engineering

This Contractor Report (CR) is a compilation of Lessons Learned in approximately 55 years of engineering experience by each James C. Blair, Robert S. Ryan, and Luke A. Schutzenhofer. The lessons are the basis of a course on Lessons Learned that has been taught at Marshall Space Flight Center. The lessons are drawn from NASA space projects and are characterized in terms of generic lessons learned from the project experience, which are further distilled into overarching principles that can be applied to future projects. Included are discussions of the overarching principles followed by a listing of the lessons associated with that principle. The lesson with sub-lessons are stated along with a listing of the project problems the lesson is drawn from, then each problem is illustrated and discussed, with conclusions drawn in terms of Lessons Learned. The purpose of this CR is to provide principles learned from past aerospace experience to help achieve greater success in future programs, and identify application of these principles to space systems design. The problems experienced provide insight into the engineering process and are examples of the subtleties one experiences performing engineering design, manufacturing, and operations.

Blair, J. C.

Lessons Learned in Engineering

This Contractor Report (CR) is a compilation of Lessons Learned in approximately 55 years of engineering experience by each James C. Blair, Robert S. Ryan, and Luke A. Schutzenhofer. The lessons are the basis of a course on Lessons Learned that has been taught at Marshall Space Flight Center. The lessons are drawn from NASA space projects and are characterized in terms of generic lessons learned from the project experience, which are further distilled into overarching principles that can be applied to future projects. Included are discussions of the overarching principles followed by a listing of the lessons associated with that principle. The lesson with sub-lessons are stated along with a listing of the project problems the lesson is drawn from, then each problem is illustrated and discussed, with conclusions drawn in terms of Lessons Learned. The purpose of this CR is to provide principles learned from past aerospace experience to help achieve greater success in future programs, and identify application of these principles to space systems design. The problems experienced provide insight into the engineering process and are examples of the subtleties one experiences performing engineering design, manufacturing, and operations. The supplemental CD contains accompanying PowerPoint presentations.

Blair, James C.

Design Thinking, Lean Startup, and High-Technology Marketing for Human-Centered Systems Engineering

The use of design thinking, lean startup, and high-technology marketing in systems engineering are presented as a case study. All were used and evaluated for their potential to improve systems engineering processes and design, address the challenges of culture change, increase the adoption rate of new technology, and engage with potential users and sponsors more effectively. Multiple examples of training and use on a model-based systems engineering initiative at a large government agency showcase how these approaches were tailored and used successfully for significant benefits such as enhanced collaboration and better problem definition and design solutions. Challenges remain for use by quiet thinkers and with virtual teams. These new ways of thinking are well aligned with creating and using new technologies and are suitable for situations involving innovation, uncertainty, and change within organizations. This case study intends to familiarize systems engineers with the application of these human-centered approaches, to interest systems engineers in incorporating these approaches into their work processes ,and to inspire the systems engineering research community to investigate further.

Karen J. Weiland

Use of graphics in the design office at the Military Aircraft Division of the British Aircraft Corporation

The CAD/CAM interactive computer graphics system was described; uses to which it has been put were shown, and current developments of the system were outlined. The system supports batch, time sharing, and fully interactive graphic processing. Engineers using the system may switch between these methods of data processing and problem solving to make the best use of the available resources. It is concluded that the introduction of on-line computing in the form of teletypes, storage tubes, and fully interactive graphics has resulted in large increases in productivity and reduced timescales in the geometric computing, numerical lofting and part programming areas, together with a greater utilization of the system in the technical departments.

Coles, W. A.