Goddard research and engineering management exercise /GREMEX/
Computer assisted management simulation exercise for training of personnel as project managers
Baker, R. F.↗
SEARCH · Engineering Papers
Results for “Engineering management”
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.
GREMEX update (Goddard research engineering management exercise)
Management simulation techniques offer training in management problems. Exercise was developed to provide experience in research and development project decision making from management rather than technological perspective. Program and documentation have been revised innumerable times in past. Described report is revised version as it exists to date.
Vaccaro, M. J.↗
Adapting the Goddard research and engineering management exercise (GREMEX) to nonspacecraft environments
A computerized training aid for all levels of research and development managers is presented. The computer model used for NASA training simulates development of a spacecraft. Operation of the model is described together with instructions for changing the input-data cards to alter the nomenclature and response of the model for use in other training environments.
Wales, R. O.↗
The Faster, Better, Cheaper Approach to Space Missions: An Engineering Management Assessment
NASA was chartered as an independent civilian space agency in 1958 following the Soviet Union's dramatic launch of the Sputnik 1 (1957). In his state of the union address in May of 1961, President Kennedy issued to the fledging organization his famous challenge for a manned lunar mission by the end of the decade. The Mercury, Gemini and Apollo programs that followed put the utmost value on high quality, low risk (as low as possible within the context of space flight), quick results, all with little regard for cost. These circumstances essentially melded NASAs culture as an organization capable of great technological achievement but at extremely high cost. The Space Shuttle project, the next major agency endeavor, was put under severe annual budget constraints in the 1970's. NASAs response was to hold to the high quality standards, low risk and annual cost and let schedule suffer. The result was a significant delay in the introduction of the Shuttle as well as overall total cost growth. By the early 1990's, because NASA's budget was declining, the number of projects was also declining. Holding the same cost and schedule productivity levels as before was essentially causing NASA to price itself out of business. In 1992, the helm of NASA was turned over to a new Administrator. Dan Goldin's mantra was "faster, better, cheaper" and his enthusiasm and determination to change the NASA culture was not to be ignored. This research paper documents the various implementations of "faster, better, cheaper" that have been attempted, analyzes their impact and compares the cost performance of these new projects to previous NASA benchmarks. Fundamentally, many elements of "faster, better, cheaper" are found to be working well, especially on smaller projects. Some of the initiatives are found to apply only to smaller or experimental projects however, so that extrapolation to "flagship" projects may be problematic.
Hamaker, Joseph W.↗
Microelectrical Mechanical Systems Flow Control Used to Manage Engine Face Distortion in Compact Inlet Systems
Turbofan engine-face flow distortion is one of the most troublesome and least understood problems for designers of modern engine inlet systems. One concern is that there are numerous sources of flow-field distortion that are ingested by the inlet or generated within the inlet duct itself. Among these are: (1) flow separation at the cowl lip during in-flight maneuvering, (2) flow separation on the compression surfaces due to shock-wave/boundary layer interactions, (3) spillage of the fuselage boundary layer into the inlet duct, (4) ingestion of aircraft vortices and wakes emanating from upstream disturbances, and (5) strong secondary flow gradients and flow separation induced by wall curvature within the inlet duct itself. Most developing aircraft (including the B70, F-111, F-14, Mig-25, Tornado, and Airbus A300) have experienced one or more of these types of problems, particularly at high Mach numbers and/or extreme maneuver conditions when flow distortion at the engine face exceeded the allowable limits of the engine.
Anderson, Bernhard H.↗
Use of the Capability Maturity Model Integration (CMMI Registered Trademark) in Software Engineering Management on NASA Missions
No abstract available
Crumbley, Tim↗
Engineering data management: Experience and projections
Experiences in developing a large engineering data management system are described. Problems which were encountered are presented and projected to future systems. Business applications involving similar types of data bases are described. A data base management system architecture proposed by the business community is described and its applicability to engineering data management is discussed. It is concluded that the most difficult problems faced in engineering and business data management can best be solved by cooperative efforts.
Jefferson, D. K.↗
Forward for the new edition of: “What Every Engineer Should Know About Risk Engineering and Management"
In aerospace and engineering in general, the major metrics are capability, cost, and safety/risk. With the increasingly rapid emergence and utilization of new technologies and systems of increasing complexity, ensuring safety becomes more difficult. The technology and practice/applications of safety/risk technologies require updating in concert with capability and systems technology changes. Hence the new, updated edition of this risk engineering book. Major changes in technology and applications, now and going forward, increasingly involve artificial intelligence (AI)/autonomy and complex systems, which are rapidly developing and moving targets when it comes to risk/safety analysis. These introduce both new risks and safety issues, and they alter more usual ones. The current reality is that often the best AI is when it is “Black Boxed”, developed “independently”, without detailed human understanding of how and by what processes decisions and results are produced. There are ongoing efforts to make the AI processes more understandable by humans, with results to be determined. Also, trusted and true autonomy is free of human intervention, which would require machines to ideate to solve in real time issues that arise due to unknown unknowns and even known unknowns. Machines using generative adversarial network (GANs) and other approaches are beginning to ideate. Overall, the capabilities and practice of AI/autonomy utilization is a work in progress with the rate of progress substantial and the impacts upon system risk/safety major.
Dennis M. Bushnell↗
Software engineering project management - A state-of-the-art report
The management of software engineering projects in the aerospace industry was investigated. The survey assessed such features as contract type, specification preparation techniques, software documentation required by customers, planning and cost-estimating, quality control, the use of advanced program practices, software tools and test procedures, the education levels of project managers, programmers and analysts, work assignment, automatic software monitoring capabilities, design and coding reviews, production times, success rates, and organizational structure of the projects.
Thayer, R. H.↗
Data management in engineering
An introduction to computer based data management is presented with an orientation toward the needs of engineering application. The characteristics and structure of data management systems are discussed. A link to familiar engineering applications of computing is established through a discussion of data structure and data access procedures. An example data management system for a hypothetical engineering application is presented.
Browne, J. C.↗
An Engineering Data Management System for Ipad
An overview of the capabilities and software architecture of the IPAD information processor (IPIP) is presented. IPIP is a state-of-the-art data base management system that satisfies engineering requirements not addressed by present day commercial systems. It also significantly advances a number of capabilities that are offered commercially. IPIP capabilities range from support for multiple schemas and data models to support for distributed processing, configuration control, and data inventory management. IPIP exploits semantic commonality in features offered in various forms at different user interfaces in today's commercial systems. An integrated software architecture supports all user interfaces: programming languages, interactive data manipulation, and schema languages. This approach promotes simplicity and compactness in software and permits features to be offered symmetrically across all appropriate user interfaces.
H R Johnson↗
Systems Integration Processes for NASA's Crew Launch Vehicle
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. This paper examines the systems integration processes NASA is utilizing to ensure integration and control of propulsion and non-propulsion elements within NASA's Crew Launch Vehicle (CLV). The objective of the CLV is to provide the transportation capabilities to meet the Constellation Program requirements for delivering a Crew Exploration Vehicle (CEV) or other payload to Low Earth Orbit (LEO) in support of the lunar and Mars missions. The CLV must successfully provide the capability within cost and schedule with an acceptable risk approach. This paper will describe in detail the systems engineering management processes that will be applied to assure CLV Project success through complete and efficient technical integration. Discussion of specific 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 CLV Project is broken logically 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 CLV elements and among the other Constellation projects. Launch vehicle stack integration (CLV 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 will also be discussed. The processes for decomposing requirements to the Elements and ensuring that requirements have been correctly validated, decomposed, allocated, and that the verification requirements are properly defined to ensure that the system design meets requirements will be discussed.
Reuter, James L.↗
Systems Integration Processes for NASA Ares I Crew Launch Vehicle
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.
Taylor, James L.↗
Achieving Improved Reliability with Failure Analysis
Reliability is the ability of a product to properly function, within specified performance limits, for a specified period of time, under the life cycle application conditions. Failure analysis is a vital tool in the effort to ensure reliability of electronic products and systems throughout their product lifecycle. Today, organizations involved in activities within the electronics supply chain are facing new challenges, not just from complex assembly styles, harsher lifecycle environments, and sophisticated supply chains, but also from customers who are demanding a quicker turn-around. Unfortunately, root cause failure analysis is often performed incompletely, leading to a poor understanding of failure mechanisms and causes and, customer dissatisfaction due to recurring failures. The PDC starts with an introduction to reliability concepts, physics of failure and an overview of failure mechanisms that affect PCBs, PCBAs and components. The PDC then dives into root cause hypothesizing techniques (Pareto, FMEA, fishbone, FTA), non-destructive and destructive analysis and, materials characterization will be discussed. Numerous failure analysis case studies will be used to illustrate the techniques and analysis principles to arrive at the root cause(s) of field failures on printed circuit boards, active components, and assemblies. What Will You Learn: Topics include: Overview of Reliability Concepts Failure mechanisms of electronic products Root cause analysis Failure analysis techniques -Non-destructive techniques (optical, CSAM etc.) -Destructive analysis (DPA, Decap, FIB etc.) -Materials characterization (XRF, EDS, TMA/DSC etc.) Who Will Benefit: Reliability engineers, failure analysis engineers, engineering managers, design engineers, component engineers, quality assurance functions and, personnel involved with reliability activities within their company.
non-destructive techniques↗
Application of Agile for Systems Engineering, Project Management and Modeling and Lessons Learned
The Systems Engineering team within the Human Research Program (HRP) Exploration Medical Capability (ExMC) Element has been transforming its development processes to be more efficient, robust,and responsive to change and to its stakeholders. To these ends, the Systems Engineering team trialed the integration of agile development techniques into existing and new processes. Agile development methods are well understood within the software development community. Outside ofsoftware development, however, how non-software project management (PM) and systems engineering (SE) teams implement agile development techniques is less well understood. In its transformation efforts, the ExMC SE team focused on three main areas: Improving the project communications among subsystem teams and stakeholders by adopting a scrum-like process, Changing the status and reporting mechanisms to improve schedule coordination between the subsystem team, SE leadership, and ExMC Element leadership, and Unifying the model-based SE workflow to improve understanding of Concepts of Operations across projects.This presentation highlights several of these transformations and what the SE team learned while undergoing the transformation.
S Lumpkins↗
Design and utilization of a Flight Test Engineering Database Management System at the NASA Dryden Flight Research Facility
A Flight Test Engineering Database Management System (FTE DBMS) was designed and implemented at the NASA Dryden Flight Research Facility. The X-29 Forward Swept Wing Advanced Technology Demonstrator flight research program was chosen for the initial system development and implementation. The FTE DBMS greatly assisted in planning and 'mass production' card preparation for an accelerated X-29 research program. Improved Test Plan tracking and maneuver management for a high flight-rate program were proven, and flight rates of up to three flights per day, two times per week were maintained.
Knighton, Donna L.↗
Introduction to System Health Engineering and Management in Aerospace
This paper provides a technical overview of Integrated System Health Engineering and Management (ISHEM). We define ISHEM as "the paper provides a techniques, and technologies used to design, analyze, build, verify, and operate a system to prevent faults and/or minimize their effects." This includes design and manufacturing techniques as well operational and managerial methods. ISHEM is not a "purely technical issue" as it also involves and must account for organizational, communicative, and cognitive f&ms of humans as social beings and as individuals. Thus the paper will discuss in more detail why all of these elements, h m the technical to the cognitive and social, are necessary to build dependable human-machine systems. The paper outlines a functional homework and architecture for ISHEM operations, describes the processes needed to implement ISHEM in the system life-cycle, and provides a theoretical framework to understand the relationship between the different aspects of the discipline. It then derives from these and the social and cognitive bases a set of design and operational principles for ISHEM.
Johnson, Stephen B.↗