Search NASA⌕ Search

SEARCH · Search NASA

Results for “MAINTENANCE 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 325 records · Page 18
All sourcesNASA NTRSDOE OSTI
NASA NTRS2013

Web Application Software for Ground Operations Planning Database (GOPDb) Management

A Web application facilitates collaborative development of the ground operations planning document. This will reduce costs and development time for new programs by incorporating the data governance, access control, and revision tracking of the ground operations planning data. Ground Operations Planning requires the creation and maintenance of detailed timelines and documentation. The GOPDb Web application was created using state-of-the-art Web 2.0 technologies, and was deployed as SaaS (Software as a Service), with an emphasis on data governance and security needs. Application access is managed using two-factor authentication, with data write permissions tied to user roles and responsibilities. Multiple instances of the application can be deployed on a Web server to meet the robust needs for multiple, future programs with minimal additional cost. This innovation features high availability and scalability, with no additional software that needs to be bought or installed. For data governance and security (data quality, management, business process management, and risk management for data handling), the software uses NAMS. No local copy/cloning of data is permitted. Data change log/tracking is addressed, as well as collaboration, work flow, and process standardization. The software provides on-line documentation and detailed Web-based help. There are multiple ways that this software can be deployed on a Web server to meet ground operations planning needs for future programs. The software could be used to support commercial crew ground operations planning, as well as commercial payload/satellite ground operations planning. The application source code and database schema are owned by NASA.

Lanham, Clifton↗
NASA NTRS2002

Crew Factors in Flight Operations XIV: Alertness Management in Regional Flight Operations Education Module

Regional operations encompass a broad range of pilots and equipment. This module is intended to help all those involved in regional aviation, including pilots, schedulers, dispatchers, maintenance technicians, policy makers, and others, to understand the physiological factors underlying fatigue, how flight operations affect fatigue, and what can be done to counteract fatigue and maximize alertness and performance in their operations. The overall purpose of this module is to promote aviation safety, performance, and productivity. It is intended to meet three specific objectives: (1) to explain the current state of knowledge about the physiological mechanisms underlying fatigue; (2) to demonstrate how this knowledge can be applied to improving flight crew sleep, performance, and alertness; and (3) to offer strategies for alertness management. Aviation Safety Reporting System (ASRS) and National Transportation Safety Board (NISH) reports are used throughout this module to demonstrate that fatigue is a safety issue in the regional operations community. The appendices at the end of this module include the ASRS reports used for the examples contained in this publication, brief introductions to sleep disorders and relaxation techniques, summaries of relevant NASA publications, and a list of general readings on sleep, sleep disorders, and circadian rhythms.

Rosekind, Mark R.↗
NASA NTRS1999

Spacecraft Software Maintenance: An Effective Approach to Reducing Costs and Increasing Science Return

Flight software is a mission critical element of spacecraft functionality and performance. When ground operations personnel interface to a spacecraft, they are typically dealing almost entirely with the capabilities of onboard software. This software, even more than critical ground/flight communications systems, is expected to perform perfectly during all phases of spacecraft life. Due to the fact that it can be reprogrammed on-orbit to accommodate degradations or failures in flight hardware, new insights into spacecraft characteristics, new control options which permit enhanced science options, etc., the on- orbit flight software maintenance team is usually significantly responsible for the long term success of a science mission. Failure of flight software to perform as needed can result in very expensive operations work-around costs and lost science opportunities. There are three basic approaches to maintaining spacecraft software--namely using the original developers, using the mission operations personnel, or assembling a center of excellence for multi-spacecraft software maintenance. Not planning properly for flight software maintenance can lead to unnecessarily high on-orbit costs and/or unacceptably long delays, or errors, in patch installations. A common approach for flight software maintenance is to access the original development staff. The argument for utilizing the development staff is that the people who developed the software will be the best people to modify the software on-orbit. However, it can quickly becomes a challenge to obtain the services of these key people. They may no longer be available to the organization. They may have a more urgent job to perform, quite likely on another project under different project management. If they havn't worked on the software for a long time, they may need precious time for refamiliarization to the software, testbeds and tools. Further, a lack of insight into issues related to flight software in its on-orbit environment, may find the developer unprepared for the challenges. The second approach is to train a member of the flight operations team to maintain the spacecraft software. This can prove to be a costly and inflexible solution. The person assigned to this duty may not have enough work to do during a problem free period and may have too much to do when a problem arises. If the person is a talented software engineer, he/she may not enjoy the limited software opportunities available in this position; and may eventually leave for newer technology computer science opportunities. Training replacement flight software personnel can be a difficult and lengthy process. The third approach is to assemble a center of excellence for on-orbit spacecraft software maintenance. Personnel in this specialty center can be managed to support flight software of multiple missions at once. The variety of challenges among a set of on-orbit missions, can result in a dedicated, talented staff which is fully trained and available to support each mission's needs. Such staff are not software developers but are rather spacecraft software systems engineers. The cost to any one mission is extremely low because the software staff works and charges, minimally on missions with no current operations issues; and their professional insight into on-orbit software troubleshooting and maintenance methods ensures low risk, effective and minimal-cost solutions to on-orbit issues.

Shell, Elaine M.↗
NASA NTRS1971

Utilization of available skills and materials in fire prevention

Procedures for installing fire protection systems in large buildings are discussed. Factors considered in the safety management are: (1) distribution of water supply, (2) design and location of exits, (3) emergency power system, and (4) maintenance procedures.

Martin, H. W.↗
NASA NTRS1983

Software-Engineering Data-Base System

Software Engineering Laboratory Data Base Maintenance System (SEL/DBAM) collects and maintains data base for evaluating software-development methodologies. SEL/DBAM provides interactive facilities for management of data collected by Software Engineering Laboratory at Goddard Space Flight Center.

Card, D. N.↗
NASA NTRS1982

Space Operations Center System Analysis: Requirements for a Space Operations Center, revision A

The system and program requirements for a space operations center as defined by systems analysis studies are presented as a guide for future study and systems definition. Topics covered include general requirements for safety, maintainability, and reliability, service and habitat modules, the health maintenance facility; logistics modules; the docking tunnel; and subsystem requirements (structures, electrical power, environmental control/life support; extravehicular activity; data management; communications and tracking; docking/berthing; flight control/propulsion; and crew support). Facilities for flight support, construction, satellite and mission servicing, and fluid storage are included as well as general purpose support equipment.

Woodcock, G. R.↗
NASA NTRS1982

Automation of the longwall mining system

Cost effective, safe, and technologically sound applications of automation technology to underground coal mining were identified. The longwall analysis commenced with a general search for government and industry experience of mining automation technology. A brief industry survey was conducted to identify longwall operational, safety, and design problems. The prime automation candidates resulting from the industry experience and survey were: (1) the shearer operation, (2) shield and conveyor pan line advance, (3) a management information system to allow improved mine logistics support, and (4) component fault isolation and diagnostics to reduce untimely maintenance delays. A system network analysis indicated that a 40% improvement in productivity was feasible if system delays associated with all of the above four areas were removed. A technology assessment and conceptual system design of each of the four automation candidate areas showed that state of the art digital computer, servomechanism, and actuator technologies could be applied to automate the longwall system.

Zimmerman, W.↗
NASA NTRS1983

Recommended approach to sofware development

A set of guideline for an organized, disciplined approach to software development, based on data collected and studied for 46 flight dynamics software development projects. Methods and practices for each phase of a software development life cycle that starts with requirements analysis and ends with acceptance testing are described; maintenance and operation is not addressed. For each defined life cycle phase, guidelines for the development process and its management, and the products produced and their reviews are presented.

Mcgarry, F. E.↗
NASA NTRS1993

Solar dynamic power system development for Space Station Freedom

The development of a solar dynamic electric power generation system as part of the Space Station Freedom Program is documented. The solar dynamic power system includes a solar concentrator, which collects sunlight; a receiver, which accepts and stores the concentrated solar energy and transfers this energy to a gas; a Brayton turbine, alternator, and compressor unit, which generates electric power; and a radiator, which rejects waste heat. Solar dynamic systems have greater efficiency and lower maintenance costs than photovoltaic systems and are being considered for future growth of Space Station Freedom. Solar dynamic development managed by the NASA Lewis Research Center from 1986 to Feb. 1991 is covered. It summarizes technology and hardware development, describes 'lessons learned', and, through an extensive bibliography, serves as a source list of documents that provide details of the design and analytic results achieved. It was prepared by the staff of the Solar Dynamic Power System Branch at the NASA Lewis Research Center in Cleveland, Ohio. The report includes results from the prime contractor as well as from in-house efforts, university grants, and other contracts. Also included are the writers' opinions on the best way to proceed technically and programmatically with solar dynamic efforts in the future, on the basis of their experiences in this program.

Source record↗
NASA NTRS2009

Protocol for Communication Networking for Formation Flying

An application-layer protocol and a network architecture have been proposed for data communications among multiple autonomous spacecraft that are required to fly in a precise formation in order to perform scientific observations. The protocol could also be applied to other autonomous vehicles operating in formation, including robotic aircraft, robotic land vehicles, and robotic underwater vehicles. A group of spacecraft or other vehicles to which the protocol applies could be characterized as a precision-formation- flying (PFF) network, and each vehicle could be characterized as a node in the PFF network. In order to support precise formation flying, it would be necessary to establish a corresponding communication network, through which the vehicles could exchange position and orientation data and formation-control commands. The communication network must enable communication during early phases of a mission, when little positional knowledge is available. Particularly during early mission phases, the distances among vehicles may be so large that communication could be achieved only by relaying across multiple links. The large distances and need for omnidirectional coverage would limit communication links to operation at low bandwidth during these mission phases. Once the vehicles were in formation and distances were shorter, the communication network would be required to provide high-bandwidth, low-jitter service to support tight formation-control loops. The proposed protocol and architecture, intended to satisfy the aforementioned and other requirements, are based on a standard layered-reference-model concept. The proposed application protocol would be used in conjunction with conventional network, data-link, and physical-layer protocols. The proposed protocol includes the ubiquitous Institute of Electrical and Electronics Engineers (IEEE) 802.11 medium access control (MAC) protocol to be used in the datalink layer. In addition to its widespread and proven use in diverse local-area networks, this protocol offers both (1) a random- access mode needed for the early PFF deployment phase and (2) a time-bounded-services mode needed during PFF-maintenance operations. Switching between these two modes could be controlled by upper-layer entities using standard link-management mechanisms. Because the early deployment phase of a PFF mission can be expected to involve multihop relaying to achieve network connectivity (see figure), the proposed protocol includes the open shortest path first (OSPF) network protocol that is commonly used in the Internet. Each spacecraft in a PFF network would be in one of seven distinct states as the mission evolved from initial deployment, through coarse formation, and into precise formation. Reconfiguration of the formation to perform different scientific observations would also cause state changes among the network nodes. The application protocol provides for recognition and tracking of the seven states for each node and for protocol changes under specified conditions to adapt the network and satisfy communication requirements associated with the current PFF mission phase. Except during early deployment, when peer-to-peer random access discovery methods would be used, the application protocol provides for operation in a centralized manner.

Jennings, Esther↗
NASA NTRS2003

Resource Management for Real-Time Adaptive Agents

Increased autonomy and automation in onboard flight systems offer numerous potential benefits, including cost reduction and greater flexibility. The existence of generic mechanisms for automation is critical for handling unanticipated science events and anomalies where limitations in traditional control software with fixed, predetermined algorithms can mean loss of science data and missed opportunities for observing important terrestrial events. We have developed such a mechanism by adding a Hierarchical Agent-based ReaLTime technology (HART) extension to our Dynamic Resource Management (DRM) middleware. Traditional DRM provides mechanisms to monitor the realtime performance of distributed applications and to move applications among processors to improve real-time performance. In the HART project we have designed and implemented a performance adaptation mechanism to improve reaktime performance. To use this mechanism, applications are developed that can run at various levels of quality. The DRM can choose a setting for the quality level of an application dynamically at run-time in order to manage satellite resource usage more effectively. A groundbased prototype of a satellite system that captures and processes images has also been developed as part of this project to be used as a benchmark for evaluating the resource management framework A significant enhancement of this generic mission-independent framework allows scientists to specify the utility, or "scientific benefit," of science observations under various conditions like cloud cover and compression method. The resource manager then uses these benefit tables to determine in redtime how to set the quality levels for applications to maximize overall system utility as defined by the scientists running the mission. We also show how maintenance functions llke health and safety data can be integrated into the utility framework. Once thls framework has been certified for missions and successfully flight tested it can be reused with little development overhead for other missions. In contrast, current space missions llke Swift manage similar types of resource trade -off completely with the scientific application code itself, and such code must be re-certified and tested for each mission even if a large portion of the code base is shared. This final report discusses some of the major issues motivating this research effort, provides a literature review of the related work, discusses the resource management framework and ground-based satellite system prototype that has been developed, indicates what work is yet to be performed, and provides a list of publications resulting from this work.

Welch, Lonnie↗
NASA NTRS1981

Science and applications space platform

The concept for the Platform/Power System combination (supported by Shuttle visits) is presented from the NASA-sponsored Phase A study. The combination will cost-effectively free-fly small groups of unmanned low-earth payloads which have common accommodation needs. A manned support module and power system can provide elemental and growth capability for 3-6 month missions. The configuration and payload accommodations of the combination systems are reviewed and schematized in detail. Flight operations for the payload science management will include the conduct of science operations, the monitoring of instrument performance, verification of the science data and the maintenance of the science mission plan.

Nein, M.↗
NASA NTRS1993

System For Retrieving Reusable Software

Encyclopedia of Software Components (ESC) is information-retrieval system of computer hardware and software providing access to generic reusable software tools and parts. Core of ESC is central tool base, which is repository of reusable software. It receives queries and submissions from user through local browser subsystem and receives authorized updates from maintenance subsystem. Sends retrievals to local browser subsystem and user's submissions to maintenance subsystem. Future versions will provide for advanced media, including voice and video, and will link system to database-management system. Programmers will not only retrieve software, but also modify, execute, and cross-link with other software.

Van Warren, Lloyd↗
NASA NTRS1990

OMS event evaluator and scheduler

An Operations Management System (OMS) is being designed for Space Station Freedom to improve productivity, reliability, and safety while reducing operations and maintenance costs. Central to the concept is a short term plan containing mixes of man-readable and machine-executable procedures used in an environment of distributed processing and execution. An OMS event evaluator to check upcoming short-term plan events for validity of execution is under development. The first version checks time and resource constraints against operational conditions for current or expected stations. In work are the handling of environmental and other operational constraints, as well as detailed modeling of resources and station operational states. The Ada Program also has the ability to reschedule all or part of the events.

Eckelkamp, Richard E.↗
NASA NTRS2000

Analysis of Regulatory Guidance for Health Monitoring

The purpose of this study was to assess the connection between current FAA regulations and the incorporation of Health Management (HM) systems into commercial aircraft. To address the overall objectives ARINC: (1) investigated FAA regulatory guidance, (2) investigated airline maintenance practices, (3) systematically identified regulations and practices that would be affected or could act as barriers to the introduction of HM technology, and (4) assessed regulatory and operational tradeoffs that should be considered for implementation. The assessment procedure was validated on a postulated structural HM capability for the B757 horizontal stabilizer.

Munns, Thomas E.↗
NASA NTRS2023

2021-2022 Long-Term Groundwater Monitoring Report Industrial Area Kennedy Space Center, Florida

This report presents the groundwater sampling results from the National Aeronautics and Space Administration (NASA) Industrial Area (IA) 2021-2022 Long-Term Monitoring (LTM) activities and results of the 2023 DPT activities at three of the sites. The NASA IA LTM Program includes the following 14 sites: - Ransom Road Landfill (RRLF) – Solid Waste Management Unit (SWMU) 003 - Orsino Storage Yard (ORSY) – SWMU 004 - Building M7-0505 Treatment Tank Area (M505) – SWMU 039 - Hypergol Maintenance Facility Hazardous Waste South Staging Area (HMF South) – SWMU 070 - Operations and Checkout Building (O&C) – SWMU 076 - Vertical Processing Facility (VPF) – SWMU 077 - Environmental Health Facility (EHF) – SWMU 079 - Kennedy Athletic, Recreation, and Social Park 1 (KARS Park 1) – SWMU 084 - Engineering Development Laboratory (EDL) – SWMU 085 - Launch Equipment Test Facility (LETF) – SWMU 091 - Mobil Service Station (MOBIL) – SWMU 093 - General Services Administration Seized Property (GSSP) – SWMU 095 - Space Station Processing Facility (SSPF) – SWMU 098 - Fuel Storage Area #1 Underground Storage Tank (UST) [Building 1044] (FSA1) – Potential Release Location (PRL) 157 Groundwater levels were gauged at each site during the 2021 and 2022 LTM field activities. Sampling events for the IA LTM Program are conducted seasonally during the dry and wet seasons, which occur in May and November, respectively. The sites in the NASA IA LTM Program are sampled on annual, biennial, or 5-year sampling frequencies based on historical trends. Due to contract transitions and monitoring well installations, 2021 dry season activities were conducted during September 2021, while dry season activities for 2022 resumed in May 2022.

groundwater↗
NASA NTRS1989

Utilization and Maintenance of the Federal Catalog System (FCS)

The Federal Catalog System (FCS) was established and substantiated by law to aid the national economy and promote greater efficiency in supply management operations throughout the Federal Government. This Handbook establishes policies and procedures to be followed by NASA installations and certain contractors in cataloging items of supply in the Federal Catalog System and prescribes use of the system in supply management operations. This Handbook is not intended to duplicate the Federal Cataloging Manuals or Federal Cataloging Handbooks. For the most part, it describes actions that are peculiar to NASA.

Source record↗