Search NASA⌕ Search

SEARCH · Search NASA

Results for “Management practices”

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 361 records · Page 20

Lessons Learned Study Final Report for the Exploration Systems Mission Directorate

This report is the final product of a 90-day study performed for the Exploration Systems Mission Directorate. The study was to assemble lessons NASA has learned from previous programs that could help the Exploration Systems Mission Directorate pursue the Exploration vision. It focuses on those lessons that should have the greatest significance to the Directorate during the formulation of program and mission plans. The study team reviewed a large number of lessons learned reports and data bases, including the Columbia Accident Investigation Board and Rogers Commission reports on the Shuttle accidents, accident reports from robotic space flight systems, and a number of management reviews by the Defense Sciences Board, Government Accountability Office, and others. The consistency of the lessons, findings, and recommendations validate the adequacy of the data set. In addition to reviewing existing databases, a series of workshops was held at each of the NASA centers and headquarters that included senior managers from the current workforce as well as retirees. The full text of the workshop reports is included in Appendix A. A lessons learned website was opened up to permit current and retired NASA personnel and on-site contractors to input additional lessons as they arise. These new lessons, when of appropriate quality and relevance, will be brought to the attention of managers. The report consists of four parts: Part 1 provides a small set of lessons, called the Executive Lessons Learned, that represent critical lessons that the Exploration Systems Mission Directorate should act on immediately. This set of Executive Lessons and their supporting rationale have been reviewed at length and fully endorsed by a team of distinguished NASA alumni; Part 2 contains a larger set of lessons, called the Selected Lessons Learned, which have been chosen from the lessons database and center workshop reports on the basis of their specific significance and relevance to the near-term work of the Exploration Directorate. These lessons frequently support the Executive lessons but are more general in nature; Part 3 consists of the reports of the center workshops that were conducted as part of this activity. These reports are included in their entirety (approximately 200 pages) in Appendix G and have significance for specific managers; Part 4 consists of the remainder of the lessons that have been selected by this effort and assembled into a database for the use of the Explorations Directorate. The database is archived and hosted in the Lessons Learned Knowledge Network, which provides a flexible search capability using a wide variety of search terms. Finally, a spreadsheet lists databases searched and a bibliography identifies reports that have been reviewed as sources of lessons for this task. NASA has been presented with many learning opportunities. We have conducted numerous programs, some extremely successful and others total failures. Most have been documented with a formal lessons learned activity, but we have not always incorporated these learning opportunities into our normal modes of business. For example, the Robbins Report of 2001 clearly indicates that many project failures of the past two decades were the result of violating well documented best practices, often in direct violation of management instructions and directives. An overarching lesson emerges: that disciplined execution in accordance with proven best practices is the greatest single contributor to a successful program. The Lessons Learned task team offers a sincere hope that the lessons presented herein will be helpful to the Exploration Systems Directorate in charting and executing their course. The success of the Directorate and of NASA in general depends on our collective ability to move forward without having to relearn the lessons of those who have gone before.

Van Laak, Jim↗

Expanding the Use of Time-Based Metering: Multi-Center Traffic Management Advisor

Time-based metering is an efficient air traffic management alternative to the more common practice of distance-based metering (or "miles-in-trail spacing"). Despite having demonstrated significant operational benefit to airspace users and service providers, time-based metering is used in the United States for arrivals to just nine airports and is not used at all for non-arrival traffic flows. The Multi-Center Traffic Management Advisor promises to bring time-based metering into the mainstream of air traffic management techniques. Not constrained to operate solely on arrival traffic, Multi-Center Traffic Management Advisor is flexible enough to work in highly congested or heavily partitioned airspace for any and all traffic flows in a region. This broader and more general application of time-based metering is expected to bring the operational benefits of time-based metering to a much wider pool of beneficiaries than is possible with existing technology. It also promises to facilitate more collaborative traffic management on a regional basis. This paper focuses on the operational concept of the Multi-Center Traffic Management Advisor, touching also on its system architecture, field test results, and prospects for near-term deployment to the United States National Airspace System.

Landry, Steven J.↗

Ranger's Legacy

With its Landsat satellites, development of sensors, and advancement of processing techniques, NASA provided the initial technology base for another Earth-benefit application of image processing, Earth resources survey by means of remote sensing. Since each object has its own unique "signature," it is possible to distinguish among surface features and to generate computer-processed imagery identifying specific features of importance to resource managers. This capability, commercialized by Perceptive Scientific Instruments, Inc., offers practical application in such areas as agricultural crop forecasting, rangeland and forest management, land use planning, mineral and petroleum exploration, map making, water quality evaluation and disaster assessment. Major users of the technology have been federal, state, and local governments, but it is making its way into commercial operations, for example, resource exploration companies looking for oil, gas and mineral sources, and timber production firms seeking more efficient treeland management. Supporting both government and private users is a small industry composed of companies producing the processing hardware software. As is the case in the medical application, many of these companies are direct offspring of NASA's work.

Source record↗

To Meet or Not To Meet Physical vs. Virtual Configuration Control Board

This presentation will define the CCB, discuss its functions and members. We will look into traditional processes of managing change control via the CCB meeting and advanced practices utilizing enhanced product tools and technologies. Well step through a summary of the feedback from the community of CM professionals at NASA Goddard Space Flight Center of best practices as well as pros and cons for facilitating both a physical CCB and managing stakeholder approvals in a virtual environment. Attendees will come away with current industry strategies to determine if process for managing change control and approvals can be streamlined within their local work environments.

tools↗

Communicating Risk to Program Managers

Program Managers (PM) can protect program resources and improve chances of success by anticipating, understanding and managing risks. Understanding the range of potential risks helps one to avoid or manage the risks. A PM must choose which risks to accept to reduce fire fighting, must meet the expectations of stakeholders consistently, and avoid falling into costly "black holes" that may open. A good risk management process provides the PM more confidence to seize opportunities save money, meet schedule, even improve relationships with people important to the program. Evidence of managing risk and sound internal controls can mean better support from superiors for the program by building a trust and reputation from being on top of issues. Risk managers have an obligation to provide the PM with the best information possible to allow the benefits to be realized (Small Business Consortium, 2004). The Institute for Chartered Accountants in England and Wales sees very important benefits for companies in providing better information about what they do to assess and manage key business risks. Such information will: a) provide practical forward-looking information; b) reduce the cost of capital; c) encourage better risk management; and d) improve accountability for stewardship, investor protection and the usefulness of financial reporting. We are particularly convinced that enhanced risk reporting will help listed companies obtain capital at the lowest possible cost (The Institute of Chartered Accountants in England &Wales, June 2002). Risk managers can take a significant role in quantifying the success of their department and communicating those figures to executive (program) management levels while pushing for a broader risk management role. Overall, risk managers must show that risk management work matters in the most crucial place-the bottom line- as they prove risk management can be a profit center (Sullivan, 2004).

Shivers, C. Herbert↗

Managing Space System Faults: Coalescing NASA's Views

Managing faults and their resultant failures is a fundamental and critical part of developing and operating aerospace systems. Yet, recent studies have shown that the engineering "discipline" required to manage faults is not widely recognized nor evenly practiced within the NASA community. Attempts to simply name this discipline in recent years has been fraught with controversy among members of the Integrated Systems Health Management (ISHM), Fault Management (FM), Fault Protection (FP), Hazard Analysis (HA), and Aborts communities. Approaches to managing space system faults typically are unique to each organization, with little commonality in the architectures, processes and practices across the industry.

Muirhead, Brian↗

Shuttle Propulsion System Major Events and the Final 22 Flights

Numerous lessons have been documented from the Space Shuttle Propulsion elements. Major events include loss of the Solid Rocket Boosters (SRB's) on STS-4 and shutdown of a Space Shuttle Main Engine (SSME) during ascent on STS-51F. On STS-112 only half the pyrotechnics fired during release of the vehicle from the launch pad, a testament for redundancy. STS-91 exhibited freezing of a main combustion chamber pressure measurement and on STS-93 nozzle tube ruptures necessitated a low liquid level oxygen cut off of the main engines. A number of on pad aborts were experienced during the early program resulting in delays. And the two accidents, STS-51L and STS-107, had unique heritage in history from early program decisions and vehicle configuration. Following STS-51L significant resources were invested in developing fundamental physical understanding of solid rocket motor environments and material system behavior. And following STS-107, the risk of ascent debris was better characterized and controlled. Situational awareness during all mission phases improved, and the management team instituted effective risk assessment practices. The last 22 flights of the Space Shuttle, following the Columbia accident, were characterized by remarkable improvement in safety and reliability. Numerous problems were solved in addition to reduction of the ascent debris hazard. The Shuttle system, though not as operable as envisioned in the 1970's, successfully assembled the International Space Station (ISS). By the end of the program, the remarkable Space Shuttle Propulsion system achieved very high performance, was largely reusable, exhibited high reliability, and was a heavy lift earth to orbit propulsion system. During the program a number of project management and engineering processes were implemented and improved. Technical performance, schedule accountability, cost control, and risk management were effectively managed and implemented. Award fee contracting was implemented to provide performance incentives. The Certification of Flight Readiness and Mission Management processes became very effective. A key to the success of the propulsion element projects was related to relationships between the MSFC project office and support organizations with their counterpart contractor organizations. The teams worked diligently to understand and satisfy requirements and achieve mission success.

Owen, James W.↗

Civilian Agency Industry Working Group EVM World Update

Objectives include: Promote the use of standards ]based, objective, and quantitative systems for managing projects and programs in the federal government. Understand how civilian agencies in general, manage their projects and programs. Project management survey expected to go out soon to civilian agencies. Describe how EVM and other best practices can be applied by the government to better manage its project and programs irrespective of whether work is contracted out or the types of contracts employed. Develop model policies aimed at project and program managers that are transportable across the government.

Kerby, Jerald↗

Provider of Services for Urban Air Mobility (PSU) Prototype Simulation (X5) Final Report

Urban Air Mobility (UAM) is a new air transportation service concept to carry passengers or cargo in metropolitan areas, leveraged by innovative aircraft and air traffic automation technologies. NASA has conducted a series of simulations, called the X-series simulation, to evaluate the UAM concept of operations and support the development of airspace procedures and services for UAM operations. The simulation called “X5” was conducted in 2023 to test a Provider of Services for UAM (PSU) prototype developed by NASA for UAM flight planning, strategic conflict management support, and data exchange between UAM operators. In this simulation, two strategic conflict management capabilities, Demand-Capacity Balancing and Sequencing and Scheduling, were further investigated. This document describes the UAM system architecture modeled, the X5 simulation environment to be executed (e.g., traffic scenario and UAM airspace construct), and the strategic conflict management processes developed and evaluated in this study. Then, the simulation results are provided using several system performance metrics, such as the number of operations planned and activated, demand-capacity imbalances detected and resolved, and pre-departure delays. Based on these metrics, the test findings and lessons learned from this simulation are discussed. NASA developed a PSU prototype as part of a reference implementation of UAM system architecture and evolved strategic conflict management capabilities for UAM operations from the previous collaborative simulations with industry partners. Below is the summary of the achievements: - Aligned NASA’s UAM reference architecture with the FAA’s UAM ConOps notional architecture - Extended UAM airspace management capabilities to include 1) Demand-Capacity Balancing (DCB) to ensure operators coordinate planned usage of shared vertiports, and 2) Sequencing and Scheduling (S&S) at UAM corridor entry and exit points to help facilitate an orderly flow of traffic - Defined the PSU information exchange APIs and requirements towards informing industry standards - Developed and tested a NASA PSU prototype as reference implementation to validate the requirements and APIs - Developed a prototype service connecting NASA’s PSU and the FAA system for testing future PSU-ATM interface requirements - Tested NASA-developed assumptions for UAM operations such as airspace design, procedures, vehicle performance, and strategic conflict management methods to inform future Cooperative Operating Practices (COPs) development with industry - Evaluated system performance metrics such as number of simultaneous operations and ground delays that can help define system-level requirements. The simulation results showed that the UAM traffic demand could be managed to minimize the needs of tactical separation provision with ground delays assigned by DCB and S&S. These accomplishments and the lessons learned from the PSU Prototype X5 simulation activities will be valuable inputs for the Air Mobility Pathfinders (AMP) project, which is NASA’s new project to create and evaluate a reference architecture for safe, secure, and scalable UAM operations.

Simulation↗

Stewardship Best Practices for Improved Discovery and Reuse of Heterogeneous and Cross-Disciplinary Earth System Data

Some of the Earth system data products such as those from NASA airborne and field investigations (a.k.a. campaigns), are highly heterogeneous and cross-disciplinary, making the data extremely challenging to manage. For example, airborne and field campaign measurements tend to be sporadic over a period of time, with large gaps. Data products generated are of various processing levels and utilized for a wide range of inter- and cross-disciplinary research and applications. Data and derived products have been historically stored in a variety of domain-specific standard (and some non-standard) formats and in various locations such as NASA Distributed Active Archive Centers (DAACs), NASA airborne science facilities, field archives, or even individual scientists’ computer hard drives. As a result, airborne and field campaign data products have often been managed and represented differently, making it onerous for data users to find, access, and utilize campaign data. Some difficulties in discovering and accessing the campaign data originate from the incomplete data product and contextual metadata that may contain details relevant to the campaign (e.g. campaign acronym and instrument deployment locations), but tend to lack other significant information needed to understand conditions surrounding the data. Such details can be burdensome to locate after the conclusion of a campaign. Utilizing consistent terminology, essential for improved discovery and reuse, is also challenging due to the variety of involved disciplines. To help address the aforementioned challenges faced by many repositories and data managers handling airborne and field data, this presentation will describe stewardship practices developed by the Airborne Data Management Group (ADMG) within the Interagency Implementation and Advanced Concepts Team (IMPACT) under the NASA’s Earth Science Data systems (ESDS) Program.

best practices↗

Space Transportation Systems, Aeronautics and Space Technology, Space and Terrestrial Applications, and Space Sciences

This report is prepared on an annual basis for the purposes of highlighting the fiscal year research and technology (R&T) activities. Its intent is to better inform the R&T Program Managers of significant accomplishments that promise practical and beneficial program application. The report is not inclusive of all R&T activities. The document is organized into two distinct sections: (1) a general summary of the major R&T activities in each program area, and (2) a description of significant individual completed activities and their results. This document will be updated November 1 of each year.

Source record↗

Research and Technology

This report is prepared on an annual basis for the purposes of highlighting the fiscal year research and technology (R&T) activities. Its intent !s to better inform the R&T Program Managers of significant accomplishments that promise practical and beneficial program application. The report is not inclusive of all R&T activities. This document will be updated in November of each year.

Source record↗

From Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

The Dawn GDS Team met the SC Sim integration challenge in eight months. The GDS System Engineering approach in response to the SC Simintegration challenge, focused on a set of key practices: decomposition of project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; risk management thru management of expectations; and aggregation of intermediate products into a final product. By maintaining a a system-level focus, the overall systems engineering process unified team GDS Team members with a common goal: the success of the ground system as a whole and not just the success of their individual expert contributions. Incorporation of Agile-type development efforts were aligned with a risk strategy based on team-oriented principles and expectations management, thus achieving a more stable baseline solution without compromising the integrity of the GDS design.

Dawn Mission↗

Space Shuttle Propulsion Finishing Strong

Numerous lessons have been documented from the Space Shuttle Propulsion elements. Major events include loss of the SRB's on STS-4 and shutdown of an SSME during ascent on STS- 51F. On STS-112 only half the pyrotechnics fired to release the vehicle from the launch pad, a testament for redundancy. STS-91 exhibited freezing of a main combustion chamber pressure measurement and on STS-93 nozzle tube ruptures necessitated a low liquid level oxygen cut off of the main engines. A number of on pad aborts were experienced during the early program resulting in delays. And the two accidents, STS-51L and STS-107, had unique heritage in history from early Program decisions and vehicle configuration. Following STS-51L significant resources were invested in developing fundamental physical understanding of solid rocket motor environments and material system behavior. Human rating of solid rocket motors was truly achieved. And following STS-107, the risk of ascent debris was better characterized and controlled. Situational awareness during all mission phases improved, and the management team instituted effective risk assessment practices. These major events and lessons for the future are discussed. The last 22 flights of the Space Shuttle, following the Columbia accident, were characterized by remarkable improvement in safety and reliability. Numerous problems were solved in addition to reduction of the ascent debris hazard. The propulsion system elements evolved to high reliability and heavy lift capability. The Shuttle system, though not a operable as envisioned in the 1970's, successfully assembled the International Space Station (ISS) and provided significant logistics and down mass for ISS operations. By the end of the Program, the remarkable Space Shuttle Propulsion system achieved very high performance, was largely reusable, exhibited high reliability, and is a heavy lift earth to orbit propulsion system. The story of this amazing system is discussed in detail in the paper.

Owen, James W.↗

Goddard Earth Science Data and Information Center (GES DISC)

The GES DIS is one of 12 NASA Earth science data centers. The GES DISC vision is to enable researchers and educators maximize knowledge of the Earth by engaging in understanding their goals, and by leading the advancement of remote sensing information services in response to satisfying their goals. This presentation will describe the GES DISC approach, successes, challenges, and best practices.

data management↗

Technology Readiness Assessment Best Practices Guide

This guide establishes standard definitions and best practices for conducting technology readiness assessments (TRAs) for in flight projects and NASA’s research and technology missions. These best practices originated from a NASA TRA Committee that met weekly in 2014. The team was co-led by the Headquarters (HQ) Office of the Chief Engineer (OCE) and the HQ Office of the Chief Technologist (OCT), and included one to two representatives from each Center.

Technology readiness level↗

A Standard Reference Model for Data Archives

An implementable Data Archive Architecture is being developed for trusted digital repositories based on the Reference Model for an Open Archival Information System (OAIS) – ISO 14721. A set of interoperable protocols and interface specifications are planned that will offer capabilities for accessing, merging, and re-using data, both within and across the operational boundaries of trustworthy digital repositories. The model will also provide support for the fundamental scientific need to verify the reproducibility of results. This standards development task is being performed by the Data Archive Interoperability (DAI) working group within the Consultative Committee for Space Data Systems (CCSDS). The architecture integrates concepts from the OAIS Reference Model, the ISO/IEC 11179 Metadata Registry (MDR) standard, the CCSDS Reference Architecture for Space Information Management (RASIM), the proposed draft recommended practice document, Information Preparation to Enable Long Term Use (IPELTU), and three decades of digital repository development for science research.

Ambacher, Bruce↗

Grapevine Remote Sensing Analysis of Phylloxera Early Stress (GRAPES): Remote Sensing Analysis Summary

High spatial resolution airborne imagery was acquired in California's Napa Valley in 1993 and 1994 as part of the Grapevine Remote sensing Analysis of Phylloxera Early Stress (GRAPES) project. Investigators from NASA, the University of California, the California State University, and Robert Mondavi Winery examined the application of airborne digital imaging technology to vineyard management, with emphasis on detecting the phylloxera infestation in California vineyards. Because the root louse causes vine stress that leads to grapevine death in three to five years, the infested areas must be replanted with resistant rootstock. Early detection of infestation and changing cultural practices can compensate for vine damage. Vineyard managers need improved information to decide where and when to replant fields or sections of fields to minimize crop financial losses. Annual relative changes in leaf area due to phylloxera infestation were determined by using information obtained from computing Normalized Difference Vegetation Index (NDVI) images. Two other methods of monitoring vineyards through imagery were also investigated: optical sensing of the Red Edge Inflection Point (REIP), and thermal sensing. These did not convey the stress patterns as well as the NDVI imagery and require specialized sensor configurations. NDVI-derived products are recommended for monitoring phylloxera infestations.

Lobitz, Brad↗