Search NASA⌕ Search

SEARCH · Search NASA

Results for “Maintenance Risk 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 19 records

Risk Management of Jettisoned Objects in LEO

The construction and maintenance of the International Space Station (ISS) has led to the release of many objects into its orbital plane, usually during the course of an extra-vehicular activity (EVA). Such releases are often unintentional, but in a growing number of cases, the jettison has been intentional, conducted after a careful assessment of the net risk to the partnership and to other objects in space. Since its launch in 1998 the ISS has contributed on average at least one additional debris object that is simultaneously in orbit with the station, although the number varies widely from zero to eight at any one moment. All of these objects present potential risks to other objects in orbit. Whether it comes from known and tracked orbiting objects or from unknown or untrackable objects, collision with orbital debris can have disastrous consequences. Objects greater than 10cm are generally well documented and tracked, allowing orbiting spacecraft or satellites opportunities to perform evasive maneuvers (commonly known as Debris Avoidance Maneuvers, or DAMs) in the event that imminent collision is predicted. The issue with smaller debris; however, is that it is too numerous to be tracked effectively and yet still poses disastrous consequences if it intercepts a larger object. Due to the immense kinetic energy of any item in orbit, collision with debris as small as 1cm can have catastrophic consequences for many orbiting satellites or spacecraft. Faced with the growing orbital debris threat and the potentially catastrophic consequences of a collision-generated debris shower originating in an orbit crossing the ISS altitude band, in 2007 the ISS program manger asked program specialists to coordinate a multilateral jettison policy amongst the ISS partners. This policy would define the acceptable risk trade rationale for intentional release of a debris object, and other mandatory constraints on such jettisons to minimize the residual risks whenever a jettison was accepted. Although ISS-related debris often presents untenable risks to the EVA crew, IVA crew, or to a departing cargo vehicle for a controlled disposal, such released objects also present a ballistic nuisance to the visiting vehicle traffic, and a potential fragmentation threat to the hundreds of other functional and debris objects whose perigees lie below the ISS orbital altitude. Thus, every such jettison decision is a conscious risk trade.

Bacon, John B.↗

Data systems and computer science: Software Engineering Program

An external review of the Integrated Technology Plan for the Civil Space Program is presented. This review is specifically concerned with the Software Engineering Program. The goals of the Software Engineering Program are as follows: (1) improve NASA's ability to manage development, operation, and maintenance of complex software systems; (2) decrease NASA's cost and risk in engineering complex software systems; and (3) provide technology to assure safety and reliability of software in mission critical applications.

Zygielbaum, Arthur I.↗

NASA's post-Challenger safety program - Themes and thrusts

The range of managerial, technical, and procedural initiatives implemented by NASA's post-Challenger safety program is reviewed. The recommendations made by the Rogers Commission, the NASA post-Challenger review of Shuttle design, the Congressional investigation of the accident, the National Research Council, the Aerospace Safety Advisory Panel, and NASA internal advisory panels and studies are summarized. NASA safety initiatives regarding improved organizational accountability for safety, upgraded analytical techniques and methodologies for risk assessment and management, procedural initiatives in problem reporting and corrective-action tracking, ground processing, maintenance documentation, and improved technologies are discussed. Safety issues relevant to the planned Space Station are examined.

Rodney, G. A.↗

Mission management aircraft operations manual

This manual prescribes the NASA mission management aircraft program and provides policies and criteria for the safe and economical operation, maintenance, and inspection of NASA mission management aircraft. The operation of NASA mission management aircraft is based on the concept that safety has the highest priority. Operations involving unwarranted risks will not be tolerated. NASA mission management aircraft will be designated by the Associate Administrator for Management Systems and Facilities. NASA mission management aircraft are public aircraft as defined by the Federal Aviation Act of 1958. Maintenance standards, as a minimum, will meet those required for retention of Federal Aviation Administration (FAA) airworthiness certification. Federal Aviation Regulation Part 91, Subparts A and B, will apply except when requirements of this manual are more restrictive.

Source record↗

NASA’s EGS Program Technology Demonstrations and Risk Reduction for Sustainable Surface Operations

This paper discusses NASA’s Exploration Ground Systems (EGS) Program Technology Infusion Strategy and the results from EGS technology demonstration projects, including Integrated Health Management capabilities for Condition Based and Predictive Maintenance, conservation of cryogenic fluids, and logistics management/commonality of maintenance equipment, tools, and consumables. The paper also discusses how technologies and capabilities implemented for ground systems (i.e. automated/autonomous operations and maintenance) can be leveraged to help reduce risk for sustainable lunar surface operations.

Launch Processing↗

NASA’s Exploration Ground Systems Program: Technology Demonstrations and Risk Reduction for Sustainable Surface Operations

This presentation discusses NASA’s Exploration Ground Systems (EGS) Program Technology Infusion Strategy and the results from EGS technology demonstration projects, including Integrated Health Management capabilities for Condition Based and Predictive Maintenance, conservation of cryogenic fluids, and logistics management/commonality of maintenance equipment, tools, and consumables. The presentation also discusses how technologies and capabilities implemented for ground systems (i.e. automated/ autonomous operations and maintenance) can be leveraged to help reduce risk for sustainable lunar surface operations.

Technology Infusion↗

How Much Testing is Needed to Manage Supportability Risks for Beyond-LEO Missions?

Supportability will be a significantly greater driver of cost and risk for future deep-space crewed missions than it has been in the past. Spares requirements and maintenance risk mitigation in particular present an unprecedented challenge for missions beyond Low Earth Orbit (LEO), since, for the first time in human spaceflight history, crews will be weeks or months away from resupply or a safe return to Earth in the event of an abort. Under these conditions, failure rates are a critical parameter that must be well-understood in order to manage logistics and risk effectively. However, failure rates cannot be measured directly, and can only be estimated based on past experience and test results. Previous research has shown that International Space Station (ISS) operational experience has provided significant benefits to future missions by reducing uncertainty and improving accuracy in failure rate estimates, resulting in significant reductions in mass and risk for beyond-LEO missions. This paper updates and expands on that research and quantifies the potential value of continued testing for future mission supportability. Frequentist and Bayesian models for evaluating, validating, and updating failure rate estimates are described, and are combined with supportability models to examine potential impacts of additional operating experience for future missions in terms of logistics mass reduction. The implications of these results for technology development, system design, and program planning are discussed along with lessons learned and recommendations for future system development. In the end, there is no simple answer to the question of how much testing is required, but the models described in this paper provide a way to evaluate the potential impacts of testing in order to inform test planning.

Andrew C Owens↗

Operations Analysis of the 2nd Generation Reusable Launch Vehicle

The Space Launch Initiative (SLI) program is developing a second-generation reusable launch vehicle. The program goals include lowering the risk of loss of crew to 1 in 10,000 and reducing annual operations cost to one third of the cost of the Space Shuttle. The SLI missions include NASA, military and commercial satellite launches and crew and cargo launches to the space station. The SLI operations analyses provide an assessment of the operational support and infrastructure needed to operate candidate system architectures. Measures of the operability are estimated (i.e. system dependability, responsiveness, and efficiency). Operations analysis is used to determine the impact of specific technologies on operations. A conceptual path to reducing annual operations costs by two thirds is based on key design characteristics, such as reusability, and improved processes lowering labor costs. New operations risks can be expected to emerge. They can be mitigated with effective risk management with careful identification, assignment, tracking, and closure. SLI design characteristics such as nearly full reusability, high reliability, advanced automation, and lowered maintenance and servicing coupled with improved processes are contributors to operability and large operating cost reductions.

Noneman, Steven R.↗

Space station data system analysis/architecture study. Task 2: Options development, DR-5. Volume 3: Programmatic options

Task 2 in the Space Station Data System (SSDS) Analysis/Architecture Study is the development of an information base that will support the conduct of trade studies and provide sufficient data to make design/programmatic decisions. This volume identifies the preferred options in the programmatic category and characterizes these options with respect to performance attributes, constraints, costs, and risks. The programmatic category includes methods used to administrate/manage the development, operation and maintenance of the SSDS. The specific areas discussed include standardization/commonality; systems management; and systems development, including hardware procurement, software development and system integration, test and verification.

Source record↗

Managing Ada development

The Ada programming language was developed under the sponsorship of the Department of Defense to address the soaring costs associated with software development and maintenance. Ada is powerful, and yet to take full advantage of its power, it is sufficiently complex and different from current programming approaches that there is considerable risk associated with committing a program to be done in Ada. There are also few programs of any substantial size that have been implemented using Ada that may be studied to determine those management methods that resulted in a successful Ada project. The items presented are the author's opinions which have been formed as a result of going through an experience software development. The difficulties faced, risks assumed, management methods applied, and lessons learned, and most importantly, the techniques that were successful are all valuable sources of management information for those managers ready to assume major Ada developments projects.

Green, James R.↗

Earth Independent Medical Operations (EIMO) Datascope: Challenges and Potential Solutions

Data flows and storage/retrieval capacity are severely constrained during missions in space and challenges will become even greater during exploration class missions. There is a need for an artificial intelligence (AI)-based clinical decision support system (CDSS) to monitor and analyze data to provide real-time consultative support for crew medical officer (CMO) decision-making. EIMO is defined as the gradual transition of medical care and decision making from terrestrial to space-based assets, enabling support of astronaut health and performance and reducing overall mission risk. While a hallmark of this paradigm shift from low-earth orbit is that on-board care will increasingly become the responsibility of the astronauts for primary management and decision making, terrestrial assets will continue to be paramount in pre-mission screening and planning, as well as prevention, health maintenance and long-term care contingencies. New capabilities and systems that enable progressively more robust and resilient systems and crews will be necessary to reduce risk and increase probability of deep space exploration mission success. An aspiration for EIMO is to develop AI-enhanced solutions for analysis of crew health & performance data and to facilitate clinical decision support for autonomous medical operations. A “system of systems” approach is envisioned whereby EIMO will deploy AI-supported natural language processing and machine learning (ML) techniques to utilize embedded reference databases and real-time data streams [input vectors] from multiple data sources. Constituent input vectors may include environmental controls, countermeasures data, behavioral data, physiologic wearables, point-of-care laboratory tests, personalized medical records, inventory trade space risk assessments, COTS medical databases, and ground support inputs. An ideal AI capability would possess trained fusion algorithms to cross reference input vectors with medical ‘knowledge’ [cultivated database] to stratify relevant data streams for predictive and actionable capabilities. In addition, EIMO will feature mobility, in that it can be accessed and can push/pull data within and between multiple vehicles/habitats. Large amounts and variable sources of data can be leveraged to diagnose, inform treatment strategies, and potentially predict medical events and performance decrements. Inclusion of advanced training tools using extended reality will enable increasingly autonomous medical care to aid a CMO when ground support is unavailable or time-delayed beyond required action window, e.g., emergent medical situations. EIMO CDSS would require very large datasets to train pre-flight and significant amounts of data are needed to support ML via in-flight CDSS operations. An additional challenge will be to find sufficient data to train a model relevant to astronaut demographics. The rapid, accelerating evolution of this field creates a propitious solution space to leverage multi-modal AI through public-private partnership(s). The status of multi-modal AI systems today would preclude their use for long duration missions as they remain unreliable and are subject to “digital hallucinations” and other errors that could pose operational risk. A federated labs structure is being considered to test and optimize data flow from the multiple input vectors leading to field testing in suitable ground/flight analogs. Critical to the success of an EIMO CDSS will be integration and interoperability and success will be defined by a system that can serve as an in-flight medical consult for the CMO providing critical support during medical contingencies. Benefits to terrestrial medicine may be significant as an outflow of the EIMO medical system, particularly for remote areas and communities lacking significant infrastructure, personnel and resources.

J Lemery↗

Earth Independent Medical Operations (EIMO) Datascope: Challenges and Potential Solutions

Data flows and storage/retrieval capacity are severely constrained during missions in space and challenges will become even greater during exploration class missions. There is a need for an artificial intelligence (AI)-based clinical decision support system (CDSS) to monitor and analyze data to provide real-time consultative support for crew medical officer (CMO) decision-making. EIMO is defined as the gradual transition of medical care and decision making from terrestrial to space-based assets, enabling support of astronaut health and performance and reducing overall mission risk. While a hallmark of this paradigm shift from low-earth orbit is that on-board care will increasingly become the responsibility of the astronauts for primary management and decision making, terrestrial assets will continue to be paramount in pre-mission screening and planning, as well as prevention, health maintenance and long-term care contingencies. New capabilities and systems that enable progressively more robust and resilient systems and crews will be necessary to reduce risk and increase probability of deep space exploration mission success. An aspiration for EIMO is to develop AI-enhanced solutions for analysis of crew health & performance data and to facilitate clinical decision support for autonomous medical operations. A “system of systems” approach is envisioned whereby EIMO will deploy AI-supported natural language processing and machine learning (ML) techniques to utilize embedded reference databases and real-time data streams [input vectors] from multiple data sources. Constituent input vectors may include environmental controls, countermeasures data, behavioral data, physiologic wearables, point-of-care laboratory tests, personalized medical records, inventory trade space risk assessments, COTS medical databases, and ground support inputs. An ideal AI capability would possess trained fusion algorithms to cross reference input vectors with medical ‘knowledge’ [cultivated database] to stratify relevant data streams for predictive and actionable capabilities. In addition, EIMO will feature mobility, in that it can be accessed and can push/pull data within and between multiple vehicles/habitats. Large amounts and variable sources of data can be leveraged to diagnose, inform treatment strategies, and potentially predict medical events and performance decrements. Inclusion of advanced training tools using extended reality will enable increasingly autonomous medical care to aid a CMO when ground support is unavailable or time-delayed beyond required action window, e.g., emergent medical situations. EIMO CDSS would require very large datasets to train pre-flight and significant amounts of data are needed to support ML via in-flight CDSS operations. An additional challenge will be to find sufficient data to train a model relevant to astronaut demographics. The rapid, accelerating evolution of this field creates a propitious solution space to leverage multi-modal AI through public-private partnership(s). The status of multi-modal AI systems today would preclude their use for long duration missions as they remain unreliable and are subject to “digital hallucinations” and other errors that could pose operational risk. A federated labs structure is being considered to test and optimize data flow from the multiple input vectors leading to field testing in suitable ground/flight analogs. Critical to the success of an EIMO CDSS will be integration and interoperability and success will be defined by a system that can serve as an in-flight medical consult for the CMO providing critical support during medical contingencies. Benefits to terrestrial medicine may be significant as an outflow of the EIMO medical system, particularly for remote areas and communities lacking significant infrastructure, personnel and resources.

Medical Operations↗

The real world and lunar base activation scenarios

A lunar base or a network of lunar bases may have highly desirable support functions in a national or international program to explore and settle Mars. In addition, He-3 exported from the Moon could be the basis for providing much of the energy needs of humankind in the twenty-first century. Both technical and managerial issues must be addressed when considering the establishment of a lunar base that can serve the needs of human civilization in space. Many of the technical issues become evident in the consideration of hypothetical scenarios for the activation of a network of lunar bases. Specific and realistic assumptions must be made about the conduct of various types of activities in addition to the general assumptions given above. These activities include landings, crew consumables, power production, crew selection, risk management, habitation, science station placement, base planning, science, agriculture, resource evaluation, readaptation, plant activation and test, storage module landings, resource transport module landings, integrated operations, maintenance, Base 2 activation, and management. The development of scenarios for the activation of a lunar base or network of bases will require close attention to the 'real world' of space operations. That world is defined by the natural environment, available technology, realistic objectives, and common sense.

Schmitt, Harrison H.↗

Application of Lightweight Formal Methods to Software Security

Formal specification and verification of security has proven a challenging task. There is no single method that has proven feasible. Instead, an integrated approach which combines several formal techniques can increase the confidence in the verification of software security properties. Such an approach which species security properties in a library that can be reused by 2 instruments and their methodologies developed for the National Aeronautics and Space Administration (NASA) at the Jet Propulsion Laboratory (JPL) are described herein The Flexible Modeling Framework (FMF) is a model based verijkation instrument that uses Promela and the SPIN model checker. The Property Based Tester (PBT) uses TASPEC and a Text Execution Monitor (TEM). They are used to reduce vulnerabilities and unwanted exposures in software during the development and maintenance life cycles.

security↗

Remote Sensing of In-Flight Icing Conditions: Operational, Meteorological, and Technological Considerations

Remote-sensing systems that map aircraft icing conditions in the flight path from airports or aircraft would allow icing to be avoided and exited. Icing remote-sensing system development requires consideration of the operational environment, the meteorological environment, and the technology available. Operationally, pilots need unambiguous cockpit icing displays for risk management decision-making. Human factors, aircraft integration, integration of remotely sensed icing information into the weather system infrastructures, and avoid-and-exit issues need resolution. Cost, maintenance, power, weight, and space concern manufacturers, operators, and regulators. An icing remote-sensing system detects cloud and precipitation liquid water, drop size, and temperature. An algorithm is needed to convert these conditions into icing potential estimates for cockpit display. Specification development requires that magnitudes of cloud microphysical conditions and their spatial and temporal variability be understood at multiple scales. The core of an icing remote-sensing system is the technology that senses icing microphysical conditions. Radar and microwave radiometers penetrate clouds and can estimate liquid water and drop size. Retrieval development is needed; differential attenuation and neural network assessment of multiple-band radar returns are most promising to date. Airport-based radar or radiometers are the most viable near-term technologies. A radiometer that profiles cloud liquid water, and experimental techniques to use radiometers horizontally, are promising. The most critical operational research needs are to assess cockpit and aircraft system integration, develop avoid-and-exit protocols, assess human factors, and integrate remote-sensing information into weather and air traffic control infrastructures. Improved spatial characterization of cloud and precipitation liquid-water content, drop-size spectra, and temperature are needed, as well as an algorithm to convert sensed conditions into a measure of icing potential. Technology development also requires refinement of inversion techniques. These goals can be accomplished with collaboration among federal agencies including NASA, the FAA, the National Center for Atmospheric Research, NOAA, and the Department of Defense. This report reviews operational, meteorological, and technological considerations in developing the capability to remotely map in-flight icing conditions from the ground and from the air.

Ryerson, Charles C.↗

Social Semantics for an Effective Enterprise

An evolution of the Semantic Web, the Social Semantic Web (s2w), facilitates knowledge sharing with "useful information based on human contributions, which gets better as more people participate." The s2w reaches beyond the search box to move us from a collection of hyperlinked facts, to meaningful, real time context. When focused through the lens of Enterprise Search, the Social Semantic Web facilitates the fluid transition of meaningful business information from the source to the user. It is the confluence of human thought and computer processing structured with the iterative application of taxonomies, folksonomies, ontologies, and metadata schemas. The importance and nuances of human interaction are often deemphasized when focusing on automatic generation of semantic markup, which results in dissatisfied users and unrealized return on investment. Users consistently qualify the value of information sets through the act of selection, making them the de facto stakeholders of the Social Semantic Web. Employers are the ultimate beneficiaries of s2w utilization with a better informed, more decisive workforce; one not achieved with an IT miracle technology, but by improved human-computer interactions. Johnson Space Center Taxonomist Sarah Berndt and Mike Doane, principal owner of Term Management, LLC discuss the planning, development, and maintenance stages for components of a semantic system while emphasizing the necessity of a Social Semantic Web for the Enterprise. Identification of risks and variables associated with layering the successful implementation of a semantic system are also modeled.

Berndt, Sarah↗

Human Systems Integration: Managing Risk in Anesthesia

The practice of anesthesia relies on clinicians’ ability to safely manage increasingly complex equipment. Devices such as ventilators, drug infusion pumps, and physiologic monitors use sophisticated algorithms to deliver care, but most clinicians are only trained to manage automated systems during normal operation. Few if any receive training on how to manage system failures. Although manufacturers are required to consult with human factors engineers as part of the equipment design process, most pieces of equipment are ultimately brought to market without extensive input from clinicians. Systems in the operating room can be as simple as an oxygen tank, or as complex as a multi-institutional healthcare organization. Humans are also a complex system, and play a critical role in the domains of operations, design, fabrication, maintenance, repair, and ultimately, dismantling and closeout. HSI seeks to provide a means for advocating the human side of the system. Human Systems Integration (HSI) is the cross disciplinary process used as part of the Systems Engineering process to reduce risk in systems. HSI professionals consider the human, hardware, and software elements of system design to optimize system performance and improve safety. HSI professionals work in domains of study that include training, management, human factors engineering, safety, and occupational health, among others. This article discusses the role of systems in the practice of anesthesia, and how consideration of the human during all phases of the system life cycle helps manage risks and promote a better patient outcome.

Human Factors↗

Automating Maneuvers: Considerations for Collision Avoidance

As more space operators implement large constellations of spacecraft, automating orbit maintenance maneuvers becomes a key feature of their operations concept to ensure that the workload is manageable. However the practice of performing a maneuver without sharing the plan with other nearby spacecraft causes a risk that two spacecraft will collide, not only destroying the spacecraft involved, but creating debris that will affect all other spacecraft using that orbit regime. In order to share the maneuver plan, a predicted ephemeris file containing the maneuver must be sent to a central authority to screen against predicted trajectories of all other on-orbit objects to determine where and when close approaches may occur that need to be mitigated. Currently the screening authority used by US operators is the 19th Space Defense Squadron. However the conjunction screening process in use by the 19th was developed over 30 years ago and was not designed with automation in mind, so screenings are performed once every 8 hours, meaning that spacecraft using automated maneuvering need to allow 16 hours to share their maneuver plan via the screening process. Many operators assume that automated maneuver planning must be real-time; however this time between planning and execution to allow for screening is possible if planned for during system design. In an effort to speed up the screening process, NASA has developed a prototype system for performing near-real-time screenings. This prototype system was necessitated to support the NASA Starling mission, a constellation of 4 cubesats that planned to fly at the same altitude as the SpaceX Starlink constellation, both performing automated maneuvering. Without screening of the planned maneuvers, the two constellations risked a collision. Once converted from a prototype to an operational system, this capability will greatly help smallsats, for example those that are planning to test propulsive capabilities, by allowing fast turnaround feedback to ensure safety form collision with other objects. This paper describes the existing CA process, the prototype real-time capability, and results from the experiment that tested the prototype.

Matthew Hejduk↗