Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “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.

At least 1,045 records · Page 58

Equipment management user's handbook for property custodians

The NASA Equipment Management User's Handbook for Property Custodians is issued as an instructional guide for personnel designated as property custodians and technical personnel involved in the acquisition, management, and use of NASA-owned equipment. This handbook provides general information and basic operational procedures for processing equipment transactions through the agency-wide NASA Equipment Management System (NEMS). Each NASA installation must prepare supplementary instructions for local requirements beyond the scope of NASA-wide policies and procedures contained herein, or as specified for local implementation in NHB 4200.1, 'NASA Equipment Management Manual.' NHB 4200.1 sets forth policy, uniform performance standards, and procedural guidance to NASA personnel for the acquisition, management, and use of NASA-owned equipment. This handbook is a controlled document, issued in loose-leaf form and revised by page changes. Additional copies for internal use may be obtained through normal distribution.

Source record↗

An engineering code to analyze hypersonic thermal management systems

Thermal loads on current and future aircraft are increasing and as a result are stressing the energy collection, control, and dissipation capabilities of current thermal management systems and technology. The thermal loads for hypersonic vehicles will be no exception. In fact, with their projected high heat loads and fluxes, hypersonic vehicles are a prime example of systems that will require thermal management systems (TMS) that have been optimized and integrated with the entire vehicle to the maximum extent possible during the initial design stages. This will not only be to meet operational requirements, but also to fulfill weight and performance constraints in order for the vehicle to takeoff and complete its mission successfully. To meet this challenge, the TMS can no longer be two or more entirely independent systems, nor can thermal management be an after thought in the design process, the typical pervasive approach in the past. Instead, a TMS that was integrated throughout the entire vehicle and subsequently optimized will be required. To accomplish this, a method that iteratively optimizes the TMS throughout the vehicle will not only be highly desirable, but advantageous in order to reduce the manhours normally required to conduct the necessary tradeoff studies and comparisons. A thermal management engineering computer code that is under development and being managed at Wright Laboratory, Wright-Patterson AFB, is discussed. The primary goal of the code is to aid in the development of a hypersonic vehicle TMS that has been optimized and integrated on a total vehicle basis.

Vangriethuysen, Valerie J.↗

Software Management Environment (SME) concepts and architecture, revision 1

This document presents the concepts and architecture of the Software Management Environment (SME), developed for the Software Engineering Branch of the Flight Dynamic Division (FDD) of GSFC. The SME provides an integrated set of experience-based management tools that can assist software development managers in managing and planning flight dynamics software development projects. This document provides a high-level description of the types of information required to implement such an automated management tool.

Hendrick, Robert↗

Software Management Environment (SME): Components and algorithms

This document presents the components and algorithms of the Software Management Environment (SME), a management tool developed for the Software Engineering Branch (Code 552) of the Flight Dynamics Division (FDD) of the Goddard Space Flight Center (GSFC). The SME provides an integrated set of visually oriented experienced-based tools that can assist software development managers in managing and planning software development projects. This document describes and illustrates the analysis functions that underlie the SME's project monitoring, estimation, and planning tools. 'SME Components and Algorithms' is a companion reference to 'SME Concepts and Architecture' and 'Software Engineering Laboratory (SEL) Relationships, Models, and Management Rules.'

Hendrick, Robert↗

Re-engineering Nascom's network management architecture

The development of Nascom systems for ground communications began in 1958 with Project Vanguard. The low-speed systems (rates less than 9.6 Kbs) were developed following existing standards; but, there were no comparable standards for high-speed systems. As a result, these systems were developed using custom protocols and custom hardware. Technology has made enormous strides since the ground support systems were implemented. Standards for computer equipment, software, and high-speed communications exist and the performance of current workstations exceeds that of the mainframes used in the development of the ground systems. Nascom is in the process of upgrading its ground support systems and providing additional services. The Message Switching System (MSS), Communications Address Processor (CAP), and Multiplexer/Demultiplexer (MDM) Automated Control System (MACS) are all examples of Nascom systems developed using standards such as, X-windows, Motif, and Simple Network Management Protocol (SNMP). Also, the Earth Observing System (EOS) Communications (Ecom) project is stressing standards as an integral part of its network. The move towards standards has produced a reduction in development, maintenance, and interoperability costs, while providing operational quality improvement. The Facility and Resource Manager (FARM) project has been established to integrate the Nascom networks and systems into a common network management architecture. The maximization of standards and implementation of computer automation in the architecture will lead to continued cost reductions and increased operational efficiency. The first step has been to derive overall Nascom requirements and identify the functionality common to all the current management systems. The identification of these common functions will enable the reuse of processes in the management architecture and promote increased use of automation throughout the Nascom network. The MSS, CAP, MACS, and Ecom projects have indicated the potential value of commercial-off-the-shelf (COTS) and standards through reduced cost and high quality. The FARM will allow the application of the lessons learned from these projects to all future Nascom systems.

Drake, Brian C.↗

Issues in NASA program and project management

This volume is the eighth in an ongoing series addressing current topics and lessons learned in NASA program and project management. Articles in this volume cover the following topics: (1) power sources for the Galileo and Ulysses Missions; (2) managing requirements; (3) program control of the Tropical Rainfall Measuring Mission; (4) project management method; (5) career development for project managers; and (6) resources for NASA managers.

Hoffman, Edward J.↗

Workload management and geographic disorientation in aviation incidents: A review of the ASRS data base

NASA's Aviation Safety Reporting System (ASRS) incident reports are reviewed in two related areas: pilots' failures to appropriately manage tasks, and breakdowns in geographic orientation. Examination of 51 relevant reports on task management breakdowns revealed that altitude busts and inappropriate runway usee were the most frequently reported consequences. Task management breakdowns appeared to occur at all levels of expertise, and prominent causal factors were related to breakdowns in crew communications, over-involvement with the flight management system and, for small (general aviation) aircraft, preoccupation with weather. Analysis of the 83 cases of geographic disorientation suggested that these too occurred at all levels of pilot experience. With regard to causal factors, a majority was related to poor cockpit resource management, in which inattention led to a loss of geographic awareness. Other leading causes were related to poor weather and poor decision making. The potential of the ASRS database for contributing to research and design issues is addressed.

Williams, Henry P.↗

Management of a coordinated parts program

The organization of the management of a parts program is discussed. The organizational structure faced by the parts manager and the advantages and disadvantages of managing a coordinated parts program are analyzed. The reliable operation of an instrument is the key to the success of the mission, together with the management of the parts program. The analysis led to the conclusion that the setting up of the decision support model will aid the parts manager in the decision making and the process control.

Krishnan, G. S.↗

NASA/DOD Aerospace Knowledge Diffusion Research Project. Paper 67: Maximizing the Results of Federally-Funded Research and Development Through Knowledge Management: A Strategic Imperative for Improving US Competitiveness

Federally-funded research and development (R&D) represents a significant annual investment (approximately $79 billion in fiscal year 1996) on the part of U.S. taxpayers. Based on the results of a 10-year study of knowledge diffusion in U.S. aerospace industry, the authors take the position that U.S. competitiveness will be enhanced if knowledge management strategies, employed within a capability-enhancing U.S. technology policy framework, are applied to diffusing the results of federally-funded R&D. In making their case, the authors stress the importance of knowledge as the source of competitive advantage in today's global economy. Next, they offer a practice-based definition of knowledge management and discuss three current approaches to knowledge management implementation-mechanistic, "the learning organization," and systemic. The authors then examine three weaknesses in existing U.S. public policy and policy implementation-the dominance of knowledge creation, the need for diffusion-oriented technology policy, and the prevalence of a dissemination model- that affect diffusion of the results of federally-funded R&D. To address these shortcomings, they propose the development of a knowledge management framework for diffusing the results of federally-funded R&D. The article closes with a discussion of some issues and challenges associated with implementing a knowledge management framework for diffusing the results of federally-funded R&D.

Pinelli, Thomas E.↗

Continuous Risk Management: A NASA Program Initiative

NPG 7120.5A, "NASA Program and Project Management Processes and Requirements" enacted in April, 1998, requires that "The program or project manager shall apply risk management principles..." The Software Assurance Technology Center (SATC) at NASA GSFC has been tasked with the responsibility for developing and teaching a systems level course for risk management that provides information on how to comply with this edict. The course was developed in conjunction with the Software Engineering Institute at Carnegie Mellon University, then tailored to the NASA systems community. This presentation will briefly discuss the six functions for risk management: (1) Identify the risks in a specific format; (2) Analyze the risk probability, impact/severity, and timeframe; (3) Plan the approach; (4) Track the risk through data compilation and analysis; (5) Control and monitor the risk; (6) Communicate and document the process and decisions.

Hammer, Theodore F.↗

Summary of Results from the Risk Management Program for the Mars Microrover Flight Experiment

On 4 July 1997, the Mars Pathfinder landed on the surface of Mars carrying the first planetary rover, known as the Sojourner. Formally known as the Microrover Flight Experiment (MFEX), the Sojourner was a low cost, high-risk technology demonstration, in which new risk management techniques were tried. This paper summarizes the activities and results of the effort to conduct a low-cost, yet meaningful risk management program for the MFEX. The specific activities focused on cost, performance, schedule, and operations risks. Just as the systems engineering process was iterative and produced successive refinements of requirements, designs, etc., so was the risk management process. Qualitative risk assessments were performed first to gain some insights for refining the microrover design and operations concept. These then evolved into more quantitative analyses. Risk management lessons from the manager's perspective is presented for other low-cost, high-risk space missions.

Shishko, Robert↗

Strategic Project Management at the NASA Kennedy Space Center

This paper describes Project Management at NASA's Kennedy Space Center (KSC) from a strategic perspective. It develops the historical context of the agency and center's strategic planning process and illustrates how now is the time for KSC to become a center which has excellence in project management. The author describes project management activities at the center and details observations on those efforts. Finally the author describes the Strategic Project Management Process Model as a conceptual model which could assist KSC in defining an appropriate project management process system at the center.

Lavelle, Jerome P.↗

Academy Sharing Knowledge (ASK). The NASA Source for Project Management Magazine

How big is your project world? Is it big enough to contain other cultures, headquarters, hierarchies, and weird harpoon-like guns? Sure it is. The great American poet Walt Whitman said it best, 'I am large/I contain multitudes.' And so must you, Mr. and Ms. Project Manager. In this issue of ASK, we look outside the project box. See how several talented project managers have expanded their definition of project scope to include managing environments outside the systems and subsystems under their care. Here's a sampling of what we've put together for you this issue: In 'Three Screws Missing,' Mike Skidmore tells about his adventures at the Plesetek Cosmodrome in northern Russia. Ray Morgan in his story, 'Our Man in Kauai,' suggests we take a broader view of what's meant by 'the team.' Jenny Baer-Riedhart, the NASA program manager on the same Pathfinder solar-powered airplane, schools us in how to sell a program to Headquarters in 'Know Thyself--But Don't Forget to Learn About the Customer Too.' Scott Cameron of Proctor and Gamble talks about sharpening your hierarchical IQ in 'The Project Manager and the Hour Glass.' Mike Jansen in 'The Lawn Dart' describes how he and the 'voodoo crew' on the Space Shuttle Advanced Solid Rocket Motor program borrowed a harpoon-like gun from the Coast Guard to catch particles inside of a plume. These are just some of the stories you'll find in ASK this issue. We hope they cause you to stop and reflect on your own project's relationship to the world outside. We are also launching a new section this issue, 'There are No Mistakes, Only Lessons.' No stranger to ASK readers, Terry Little inaugurates this new section with his article 'The Don Quixote Complex.'

Post, Todd↗

The Acquisition Process as a Vehicle for Enabling Knowledge Management in the Lifecycle of Complex Federal Systems

This white paper explores how to increase the success and operation of critical, complex, national systems by effectively capturing knowledge management requirements within the federal acquisition process. Although we focus on aerospace flight systems, the principles outlined within may have a general applicability to other critical federal systems as well. Fundamental design deficiencies in federal, mission-critical systems have contributed to recent, highly visible system failures, such as the V-22 Osprey and the Delta rocket family. These failures indicate that the current mechanisms for knowledge management and risk management are inadequate to meet the challenges imposed by the rising complexity of critical systems. Failures of aerospace system operations and vehicles may have been prevented or lessened through utilization of better knowledge management and information management techniques.

Stewart, Helen↗

Knowledge Management

The emergence of rapidly expanding technologies for distribution and dissemination of information and knowledge has brought to focus the opportunities for development of knowledge-based networks, knowledge dissemination and knowledge management technologies and their potential applications for enhancing productivity of knowledge work. The challenging and complex problems of the future can be best addressed by developing the knowledge management as a new discipline based on an integrative synthesis of hard and soft sciences. A knowledge management professional society can provide a framework for catalyzing the development of proposed synthesis as well as serve as a focal point for coordination of professional activities in the strategic areas of education, research and technology development. Preliminary concepts for the development of the knowledge management discipline and the professional society are explored. Within this context of knowledge management discipline and the professional society, potential opportunities for application of information technologies for more effectively delivering or transferring information and knowledge (i.e., resulting from the NASA's Mission to Planet Earth) for the development of policy options in critical areas of national and global importance (i.e., policy decisions in economic and environmental areas) can be explored, particularly for those policy areas where a global collaborative knowledge network is likely to be critical to the acceptance of the policies.

Shariq, Syed Z.↗

Controller Strategies for Managing Air Traffic in High Altitude Arrival Sectors

Substantial increases in the volume of air traffic in the National Airspace System (NAS) are forecast for the next decade, with the number of passengers travelling on U.S. airlines expected to increase by as much as 60%. This increased demand on system capacity will be accompanied by increases in traffic complexity as air traffic service providers routinely accommodate user preferred routing requests. Changes to the NAS to meet these new demands are currently underway, including development of new decision support tools to aid controllers in monitoring and managing air traffic, and increased air-to-air and air-to-ground information exchange. Changes in roles and responsibilities of pilots and controllers in flight path management will accompany these changes in traffic patterns and information technology, however the ultimate responsibility for maintaining aircraft separation will remain with the air traffic controller. A thorough understanding of the methods controllers use to manage air traffic will help ensure that changes to the NAS are implemented in a way that maintains the controller's ability to separate aircraft as the system evolves. This presentation describes the strategies controllers use today to manage arrival traffic in its descent from cruise altitude to the Terminal Radar Approach Control (TRACON) boundary. Factors that increase the complexity of this task include the presence of overflight traffic, varying aircraft performance characteristics, winds aloft, ground speed variations with altitude, the need to merge arrival traffic into a single stream, and, when arrival traffic exceeds airport runway capacity, the added task of metering flow into the TRACON. Because of the limited information available to controllers to manage arrival traffic, their strategies are often driven by the need to reduce the task's complexity, which can result in de-optimized flight paths for individual aircraft (e.g., sub-optimal descent or speed profiles). Understanding these strategies and the cognitive demands that drive them will support a safe transition to a NAS that relies on enhanced technologies. In addition, it could enable system developers to identify opportunities for new automation-based procedures or information displays that could reduce the controller's workload and increase operational efficiency.

Smith, Nancy↗

Application of Risk Assessment Tools in the Continuous Risk Management (CRM) Process

Marshall Space Flight Center (MSFC) of the National Aeronautics and Space Administration (NASA) is currently implementing the Continuous Risk Management (CRM) Program developed by the Carnegie Mellon University and recommended by NASA as the Risk Management (RM) implementation approach. The four most frequently used risk assessment tools in the center are: (a) Failure Modes and Effects Analysis (FMEA), Hazard Analysis (HA), Fault Tree Analysis (FTA), and Probabilistic Risk Analysis (PRA). There are some guidelines for selecting the type of risk assessment tools during the project formulation phase of a project, but there is not enough guidance as to how to apply these tools in the Continuous Risk Management process (CRM). But the ways the safety and risk assessment tools are used make a significant difference in the effectiveness in the risk management function. Decisions regarding, what events are to be included in the analysis, to what level of details should the analysis be continued, make significant difference in the effectiveness of risk management program. Tools of risk analysis also depends on the phase of a project e.g. at the initial phase of a project, when not much data are available on hardware, standard FMEA cannot be applied; instead a functional FMEA may be appropriate. This study attempted to provide some directives to alleviate the difficulty in applying FTA, PRA, and FMEA in the CRM process. Hazard Analysis was not included in the scope of the study due to the short duration of the summer research project.

Paul S. Ray↗

The Project Manager's Tool Kit

Project managers are rarely described as being funny. Moreover, a good sense of humor rarely seems to be one of the deciding factors in choosing someone to be a project manager, or something that pops up as a major discussion point at an annual performance review. Perhaps this is because people think you aren't serious about your work if you laugh. I disagree with this assessment, but that's not really my point. As I talk to people either pursuing a career in project management, or broadening their assignment to include project management, I encourage them to consider what tools they need to be successful. I suggest that they consider any strength they have to be part of their Project Management (PM) Tool Kit, and being funny could be one of the tools they need.

Cameron, W. Scott↗