SEARCH · Search NASA

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

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 577 records · Page 32

All sources NASA NTRS DOE OSTI

NASA NTRS2013

Class D Management Implementation Approach of the First Orbital Mission of the Earth Venture Series

A key element of the National Research Council's Earth Science and Applications Decadal Survey called for the creation of the Venture Class line of low-cost research and application missions within NASA (National Aeronautics and Space Administration). One key component of the architecture chosen by NASA within the Earth Venture line is a series of self-contained stand-alone spaceflight science missions called "EV-Mission". The first mission chosen for this competitively selected, cost and schedule capped, Principal Investigator-led opportunity is the CYclone Global Navigation Satellite System (CYGNSS). As specified in the defining Announcement of Opportunity, the Principal Investigator is held responsible for successfully achieving the science objectives of the selected mission and the management approach that he/she chooses to obtain those results has a significant amount of freedom as long as it meets the intent of key NASA guidance like NPR 7120.5 and 7123. CYGNSS is classified under NPR 7120.5E guidance as a Category 3 (low priority, low cost) mission and carries a Class D risk classification (low priority, high risk) per NPR 8705.4. As defined in the NPR guidance, Class D risk classification allows for a relatively broad range of implementation strategies. The management approach that will be utilized on CYGNSS is a streamlined implementation that starts with a higher risk tolerance posture at NASA and that philosophy flows all the way down to the individual part level.

Wells, James E.↗

NASA NTRS1997

Assessment and Management of the Risks of Debris Hits During Space Station EVAs

The risk of EVAs is critical to the decision of whether or not to automate a large part of the construction of the International Space Station (ISS). Furthermore, the choice of the technologies of the space suit and the life support system will determine (1) the immediate safety of these operations, and (2) the long-run costs and risks of human presence in space, not only in lower orbit (as is the case of the ISS) but also perhaps, outside these orbits, or on the surface of other planets. The problem is therefore both an immediate one and a long-term one. The fundamental question is how and when to shift from the existing EMU system (suit, helmet, gloves and life support system) to another type (e.g. a hard suit), given the potential trade-offs among life-cycle costs, risks to the astronauts, performance of tasks, and uncertainties about new systems' safety inherent to such a shift in technology. A more immediate issue is how to manage the risks of EVAs during the construction and operation of the ISS in order to make the astronauts (in the words of the NASA Administrator) "as safe outside as inside". For the moment (June 1997), the plan is to construct the Space Station using the low-pressure space suits that have been developed for the space shuttle. In the following, we will refer to this suit assembly as EMU (External Maneuvering Unit). It is the product of a long evolution, starting from the U.S. Air Force pilot suits through the various versions and changes that occurred for the purpose of NASA space exploration, in particular during the Gemini and the Apollo programs. The Shuttle EMU is composed of both soft fabrics and hard plates. As an alternative to the shuttle suit, at least two hard suits were developed by NASA: the AX5 and the MRKIII. The problem of producing hard suits for space exploration is very similar to that of producing deep-sea diving suits. There was thus an opportunity to develop a suit that could be manufactured for both purposes with the economies of scale that could be gained from a two-branch manufacturing line (space and deep sea). Of course, the space suit would need to be space qualified. Some of the problems in adopting one of the hard suits were first that the testing had to be completed, and second that it required additional storage space. The decision was made not to develop a hard suit in time for the construction and operation of the ISS. Instead, to improve the safety of the current suit, it was decided to reinforce the soft parts of the shuttle EMU with KEVLAR linings to strengthen it against debris impacts. Test results, however, show that this advanced suit design has little effect on the penetration characteristics.

Pate-Cornell, Elisabeth↗

NASA NTRS2001

An Overview of In-Stu Treatability Studies at Marshall Space Flight Center, Huntsville, Alabama

Marshall Space Flight Center (MSFC) is located in Huntsville, Alabama (north-central Alabama), on approximately 1,840 acres near the center of the U.S. Army's Redstone Arsenal (RSA). MSFC is the National Aeronautics and Space Administration's (NASA's) principal propulsion development center. Its scientists, engineers, and support personnel play a major role in the National Space Transportation System by managing space shuttle mission activities, including the microgravity laboratory. In addition, MSFC will be a significant contributor to several of NASA's future programs, including the Reusable Launch Vehicle (X-33), International Space Station, and Advanced X-ray Astrophysics Facility, as well as research on a variety of space science applications. MSFC has been used to develop, test and manufacture space vehicles and components since 1960, when civilian rocketry and missile activities were transferred from RSA to MSFC. In 1994, MSFC was placed on the National Priority List for the management of hazardous waste sites, under the requirements of the Comprehensive Environmental Response, Compensation, and Liability Act (CERCLA). One requirement of the CERCLA program is to evaluate the nature and extent of environmental contamination resulting from identified CERCLA sites, assess the public health and environmental risks associated with the identified contamination, and identify potential remedial actions. A CERCLA remedial investigation (RI) for the groundwater system has identified at least five major plumes of chlorinated volatile organic compounds (CVOCs) in the groundwater beneath the facility. These plumes are believed to be the result of former management practices at 14 main facility locations (termed "source areas") where CVOCs were released to the subsurface. Trichloroethene (TCE) is the predominant CVOC and is common to all the plumes. Perchloroethene (PCE) also exists in two of the plumes. In addition to TCE and PCE, carbon tetrachloride and 1,1,2,2-tetrachloroethane are contained in one of the plumes. The CVOCs are believed to exist as dense non-aqueous phase liquids (DNAPLs) beneath many of the source areas.

McElroy, Bill↗

NASA NTRS2006

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

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), responsible for project management and flight operations; Orbital Sciences Corporation (OSC), spacecraft builder and responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), responsible for science planning and operations. As a cost-capped mission, one of Dawn s implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL s ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL s GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project s commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to an overall systems engineering process and fundamental systems engineering practices: decomposition of the project request into manageable requirements; definition of a structured yet flexible development process; integration of multiple ground disciplines and experts into a focused team effort; in-process risk management; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

systems engineering↗

NASA NTRS2009

CRYOTE (Cryogenic Orbital Testbed) Concept

Demonstrating cryo-fluid management (CFM) technologies in space is critical for advances in long duration space missions. Current space-based cryogenic propulsion is viable for hours, not the weeks to years needed by space exploration and space science. CRYogenic Orbital TEstbed (CRYOTE) provides an affordable low-risk environment to demonstrate a broad array of critical CFM technologies that cannot be tested in Earth's gravity. These technologies include system chilldown, transfer, handling, health management, mixing, pressure control, active cooling, and long-term storage. United Launch Alliance is partnering with Innovative Engineering Solutions, the National Aeronautics and Space Administration, and others to develop CRYOTE to fly as an auxiliary payload between the primary payload and the Centaur upper stage on an Atlas V rocket. Because satellites are expensive, the space industry is largely risk averse to incorporating unproven systems or conducting experiments using flight hardware that is supporting a primary mission. To minimize launch risk, the CRYOTE system will only activate after the primary payload is separated from the rocket. Flying the testbed as an auxiliary payload utilizes Evolved Expendable Launch Vehicle performance excess to cost-effectively demonstrate enhanced CFM.

Gravlee, Mari↗

NASA NTRS2014

Pair-Wise Trajectory Management-Oceanic (PTM-O)

This document describes the Pair-wise Trajectory Management-Oceanic (PTM-O) Concept of Operations (ConOps). Pair-wise Trajectory Management (PTM) is a concept that includes airborne and ground-based capabilities designed to enable and to benefit from, airborne pair-wise distance-monitoring capability. PTM includes the capabilities needed for the controller to issue a PTM clearance that resolves a conflict for a specific pair of aircraft. PTM avionics include the capabilities needed for the flight crew to manage their trajectory relative to specific designated aircraft. Pair-wise Trajectory Management PTM-Oceanic (PTM-O) is a regional specific application of the PTM concept. PTM is sponsored by the National Aeronautics and Space Administration (NASA) Concept and Technology Development Project (part of NASA's Airspace Systems Program). The goal of PTM is to use enhanced and distributed communications and surveillance along with airborne tools to permit reduced separation standards for given aircraft pairs, thereby increasing the capacity and efficiency of aircraft operations at a given altitude or volume of airspace.

Jones, Kenneth M.↗

NASA NTRS2014

Identification of Vehicle Health Assurance Related Trends

Trend analysis in aviation as related to vehicle health management (VHM) was performed by reviewing the most current statistical and prognostics data available from the National Transportation Safety Board (NTSB) accident, the Federal Aviation Administration (FAA) incident, and the NASA Aviation Safety Reporting System (ASRS) incident datasets. In addition, future directions in aviation technology related to VHM research areas were assessed through the Commercial Aviation Safety Team (CAST) Safety Enhancements Reserved for Future Implementations (SERFIs), the National Transportation Safety Board (NTSB) Most-Wanted List and recent open safety recommendations, the National Research Council (NRC) Decadal Survey of Civil Aeronautics, and the Future Aviation Safety Team (FAST) areas of change. Future research direction in the VHM research areas is evidently strong as seen from recent research solicitations from the Naval Air Systems Command (NAVAIR), and VHM-related technologies actively being developed by aviation industry leaders, including GE, Boeing, Airbus, and UTC Aerospace Systems. Given the highly complex VHM systems, modifications can be made in the future so that the Vehicle Systems Safety Technology Project (VSST) technical challenges address inadequate maintenance crew's trainings and skills, and the certification methods of such systems as recommended by the NTSB, NRC, and FAST areas of change.

Phojanamongkolkij, Nipa↗

NASA NTRS2024

Per- and Polyfluoroalkyl Substances Confirmatory Sampling Report, South Repeater Building (SWMU 121), Kennedy Space Center, Florida

This Per- and Polyfluoroalkyl Substances (PFAS) Confirmatory Sampling (CS) Report was prepared by AECOM Technical Services, Inc. (AECOM) for the National Aeronautics and Space Administration (NASA) under Contract 80KSC019D0010, Task Order 80KSC021F0096. The purpose of this report is to document CS activities at the South Repeater Building, Solid Waste Management Unit (SWMU) 121, formerly known as the Area 3 Repeater Building (A3RB). A Phase I SWMU Assessment and Confirmatory Sampling Report (NASA 2019) and a Phase II and III SWMU Assessment and Confirmatory Sampling Report (NASA 2022b) were previously submitted detailing Center-Wide assessment activities performed at the John F. Kennedy Space Center (KSC) in Florida that identified 33 locations of concern and 19 areas of potential concern at KSC associated with the storage, use, or release of materials containing PFAS. A review of the analytical results from investigation derived waste samples collected in 2020 from the South Repeater Building area indicated concentrations of perfluorooctanesulfonic acid (PFOS) were above Florida Department of Environmental Protection (FDEP) provisional Groundwater Cleanup Target Levels of 70 nanograms per liter (ng/L) at a concentration of 1,750 ng/L. Following this review, the KSC Fire Chief was contacted; the Chief recalled fighting a brush fire in 1998 in the area, during which an unknown volume of aqueous film-forming foam was used to extinguish the fire. The Phase II and Phase III SWMU Assessment Report recommended this area proceed to CS. Historical results in this area are provided in Appendix A . PFAS CS activities were contracted at the South Repeater Building. Initial CS activities were conducted in accordance with the PFAS Assessment and Mitigation Work Plan (AECOM 2022), which was submitted to the NASA Remediation Project Management team and accepted by the team on November 1 and 8, 2021. The objectives of the PFAS CS were to: - - Confirm and begin to assess the extent of PFAS affected media in the South Repeater Building area. - - Identify locations for groundwater, soil, surface water, and soil core sampling. - - Qualitatively characterize the migration potential of released PFAS to environmental media (soil, groundwater, and surface water). The following activities were completed to meet the PFAS CS objectives: - - Installation of monitoring wells via direct push technology (DPT) and rotosonic techniques - - Groundwater, soil, and surface water sampling - - Collection of soil cores to evaluate site lithology - - Development of initial PFAS plume characterization

PFAS↗

NASA NTRS1992

The Many Dimensions of Program Management

For the purposes of this paper, program refers to a collection of activities or projects which must be performed according to a plan or schedule. The Space Exploration Initiative within the National Aeronautics and Space Administration (NASA) is an example. Dimensionality refers to both the various perspectives of a program and to the components within that perspective. It is, thus, appropriate to think of dimensions of dimensionality. For example, one dimension or perspective of a program is the projects which perform the program. Within the project dimension, the individual projects are the components of that dimensionality. The number of projects defines the spatial dimensionality of the project dimension. Thus, each perspective or dimension has a dimensionality of its own. The structure and associated values of all the various perspectives of a program define the program. A project refers to the collection of activities required to conceive, sell, design, develop, evaluate, produce, operate, support, evolve, and retire a given system. A project thus effects the life cycle of given system. A project is, thus, the system to conceive, sell, design, develop, evaluate, produce, operate, support, evolve, and retire a system. A program, thus, effects the life cycle of the collection of projects required to effect the collection of systems required to implement the program.

Dean, Edwin B.↗

NASA NTRS1989

AdaNET prototype library administration manual

The functions of the AdaNET Prototype Library of Reusable Software Parts is described. Adopted from the Navy Research Laboratory's Reusability Guidebook (V.5.0), this is a working document, customized for use the the AdaNET Project. Within this document, the term part is used to denote the smallest unit controlled by a library and retrievable from it. A part may have several constituents, which may not be individually tracked. Presented are the types of parts which may be stored in the library and the relationships among those parts; a concept of trust indicators which provide measures of confidence that a user of a previously developed part may reasonably apply to a part for a new application; search and retrieval, configuration management, and communications among those who interact with the AdaNET Prototype Library; and the AdaNET Prototype, described from the perspective of its three major users: the part reuser and retriever, the part submitter, and the librarian and/or administrator.

Hanley, Lionel↗

NASA NTRS2000

The NASA Aviation Safety Program: Overview

In 1997, the United States set a national goal to reduce the fatal accident rate for aviation by 80% within ten years based on the recommendations by the Presidential Commission on Aviation Safety and Security. Achieving this goal will require the combined efforts of government, industry, and academia in the areas of technology research and development, implementation, and operations. To respond to the national goal, the National Aeronautics and Space Administration (NASA) has developed a program that will focus resources over a five year period on performing research and developing technologies that will enable improvements in many areas of aviation safety. The NASA Aviation Safety Program (AvSP) is organized into six research areas: Aviation System Modeling and Monitoring, System Wide Accident Prevention, Single Aircraft Accident Prevention, Weather Accident Prevention, Accident Mitigation, and Synthetic Vision. Specific project areas include Turbulence Detection and Mitigation, Aviation Weather Information, Weather Information Communications, Propulsion Systems Health Management, Control Upset Management, Human Error Modeling, Maintenance Human Factors, Fire Prevention, and Synthetic Vision Systems for Commercial, Business, and General Aviation aircraft. Research will be performed at all four NASA aeronautics centers and will be closely coordinated with Federal Aviation Administration (FAA) and other government agencies, industry, academia, as well as the aviation user community. This paper provides an overview of the NASA Aviation Safety Program goals, structure, and integration with the rest of the aviation community.

Shin, Jaiwon↗

NASA NTRS1994

Intellectual Property Rights at the National Aeronautics and Space Administration, Lewis Research Center

At a fundamental level, intellectual property is the core work product of a technical organization. The National Aeronautics and Space Administration (NASA), produces a variety of intellectual property including: patents, trademarks, data rights, copyright and rights associated with National Security. For a scientific organization to properly manage its work product it has to manage its intellectual property. This paper endeavors to describe how the intellectual property rights are generated and allocated at NASA. The author then goes on to discuss how the intellectual property might be managed to meet the objectives of program implementation, technology transfer and security.

Williams, Vernon E.↗

NASA NTRS1994

Design and implementation of two two-week Teacher Enhancement Institutes

During this summer, I have been part of a four team effort that planned and executed two two-week Teacher Enhancement Institutes (TEI) for 40 K-8 teachers from this area. The TEI was designed to enhance teachers' background in aeronautics and technology so that they would be better equipped to encourage and to train students in the mathematics, science, and technology fields. The teachers were given a stipend and three graduate credits from Christopher Newport University for their participation in this program. The four ASEE fellows worked together to develop objectives and a schedule of activities for each two-week session based on the program outline given in the grants that were funding this effort. We divided the responsibilities in coordinating and implementing each part of the TEI based on the specific strengths and background of each ASEE fellow. My specific responsibilities were: (1) to develop the course syllabus and generally handle all matters involved with the graduate course; (2) coordinate the follow-up sessions; and (3) design and manage half of the technology sessions that we had scheduled (approximately 30% of the TEI was devoted to technology). Because the first two responsibilities were primarily administrative in nature, I will address only the last. The technology sessions were divided into computer-only and other technologies (e.g., television and digital technology including scanning, digital photography and CD-ROM). I had responsibility for the computer-only technology sessions. The emphasis of these sessions was on use of the Internet specifically to locate and use educational resources. To maximize learning, these sessions were hands-on with two teachers at each computer. Each teacher received instruction in, and actually used, the most popular tools available on the Internet: email (they were given temporary accounts at NASA LaRC), anonymous ftp and archie, gopher and veronica, mosaic, and telnet. Teachers participated in hands-on workshops to learn about these programs, but were also given time during the two-week session to explore on their own and to find resources on the Net that specifically met their needs. In order to ensure that Internet access continues after their return to the classroom, aIl teachers who did not have them also applied for Learning Link accounts (from WHRO, the local public television station) and Virginia Pen accounts (from the Department of Education of Virginia), both of which allow textbased access to Internet. In addition to getting exposure to and practice with Internet tools, teachers were aIso given a hands-on seminar (and also given practice time) on ClarisWorks, an integrated word processing, spreadsheet, database, and paint package. The technology sessions (and TEI as a whole) were enthusiastically received by both new and more experienced teachers as extremely helpful in improving their ability to use technology in developing lesson pIans.

Lambert, Lynn↗

NASA NTRS2005

ASK Talks with Bill Townsend

Recently retiring from his position as Deputy Director of NASA's Goddard Space Flight Center in Greenbelt, Maryland, Bill Townsend is now the Vice President and General Manager of Civil Space Systems of Ball Aerospace and Technologies Corporation. Prior to his assignment to Goddard in 1998, Mr.Townsend had served as the Deputy Associate Administrator (Programs) for the Office of Earth Science since 1993. For a 20 month period beginning June 1996, he was also the acting Associate Administrator for the Enterprise.

Townsend, Bill↗

NASA NTRS2021

High-Density Automated Vertiport Concept of Operations

The National Aeronautics and Space Administration (NASA) vision for Advanced Air Mobility (AAM) includes Urban Air Mobility (UAM) – a concept involving vertical takeoff and landing (VTOL) aircraft, decentralized (or federated) traffic management, and new infrastructure to support urban, suburban, and rural flight operations. High-density performance-based routes or corridors enable prompt transportation of people and goods from node to node, where each node represents a vertiport, defined as an identifiable ground or elevated area used for the takeoff and landing of VTOL aircraft. In the presence of uncertainty surrounding aircraft turnaround time on the ground, vertiports are the critical end points in scheduling, sequencing, and spacing (SSS) of aircraft in dense metropolitan environments. This Concept of Operations (ConOps) includes vertiports of varying sizes, configurations, service offerings, and locations. UAM air vehicles include conventional rotorcraft, unmanned VTOL aircraft, and novel piloted VTOL aircraft. This ConOps focuses on operations at a high-density vertiport, supported by a Vertiport Automation System (VAS) with high-throughput operation capabilities under conditions defined as NASA’s Urban Air Mobility Maturity Level Four (UML-4).

UAM↗

NASA NTRS2021

High-Density Automated Vertiport Concept of Operations

Urban Air Mobility↗

NASA NTRS1994

The design and implementation of EPL: An event pattern language for active databases

The growing demand for intelligent information systems requires closer coupling of rule-based reasoning engines, such as CLIPS, with advanced data base management systems (DBMS). For instance, several commercial DBMS now support the notion of triggers that monitor events and transactions occurring in the database and fire induced actions, which perform a variety of critical functions, including safeguarding the integrity of data, monitoring access, and recording volatile information needed by administrators, analysts, and expert systems to perform assorted tasks; examples of these tasks include security enforcement, market studies, knowledge discovery, and link analysis. At UCLA, we designed and implemented the event pattern language (EPL) which is capable of detecting and acting upon complex patterns of events which are temporally related to each other. For instance, a plant manager should be notified when a certain pattern of overheating repeats itself over time in a chemical process; likewise, proper notification is required when a suspicious sequence of bank transactions is executed within a certain time limit. The EPL prototype is built in CLIPS to operate on top of Sybase, a commercial relational DBMS, where actions can be triggered by events such as simple database updates, insertions, and deletions. The rule-based syntax of EPL allows the sequences of goals in rules to be interpreted as sequences of temporal events; each goal can correspond to either (1) a simple event, or (2) a (possibly negated) event/condition predicate, or (3) a complex event defined as the disjunction and repetition of other events. Various extensions have been added to CLIPS in order to tailor the interface with Sybase and its open client/server architecture.

Giuffrida, G.↗

NASA NTRS2020

Analysis of Pilot Monitoring Skills and a Review of Training Effectiveness

The commercial aviation industry world-wide has identified a need for improved pilot monitoring and awareness (e.g., FAA, 2013, ICAO, 2016). More specifically, aviation safety data indicate that failures in pilots’ flight path management (FPM) monitoring and awareness have contributed to a range of undesired outcomes: accidents, major upsets, and non-compliance with air traffic control (ATC) guidance. The Federal Aviation Administration (FAA) has further stated that these types of FPM failures are likely to worsen with the increasingly complex air traffic control systems and FPM concepts proposed for NextGen (https://www.faa. gov/nextgen/what_is_nextgen/) operations (e.g., see Hah et al., 2017). Adding to this complexity is the introduction of increasingly automated aircraft systems that can increase monitoring burdens. One potential mitigation for this situation is to enhance pilot training for effective monitoring. NASA Ames Research Center was asked to identify and evaluate training approaches that have the potential to enhance pilots’ ability to effectively monitor for FPM (with the result of improved awareness). The focus of this work is to identify, develop or validate training guidance to improve pilot monitoring/awareness regarding FPM and mitigate the recent trend of accidents and incidents, especially loss of control (LOC) events. The result of this work should be input for improved industry standards and FAA guidance to reduce the risk of incidents and accidents due to inadequate pilot monitoring/awareness. This is the first of three reports that were developed for this project.

aviation human factors↗