Search NASA⌕ Search

SEARCH · Search NASA

Results for “knowledge 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 397 records · Page 22
All sourcesNASA NTRSDOE OSTI
NASA NTRS1991

The nutrition advisor expert system

The Nutrition Advisor Expert System (NAES) is an expert system written in the C Language Integrated Production System (CLIPS). NAES provides expert knowledge and guidance into the complex world of nutrition management by capturing the knowledge of an expert and placing it at the user's fingertips. Specifically, NAES enables the user to: (1) obtain precise nutrition information for food items; (2) perform nutritional analysis of meal(s), flagging deficiencies based upon the U.S. Recommended Daily Allowances; (3) predict possible ailments based upon observed nutritional deficiency trends; (4) obtain a top ten listing of food items for a given nutrient; and (5) conveniently upgrade the data base. An explanation facility for the ailment prediction feature is also provided to document the reasoning process.

Huse, Scott M.↗
NASA NTRS2011

DCS: A Case Study of Identification of Knowledge and Disposition Gaps Using Principles of Continuous Risk Management

The Human Research Program (HRP) is formulated around the program architecture of Evidence-Risk-Gap-Task-Deliverable. Review of accumulated evidence forms the basis for identification of high priority risks to human health and performance in space exploration. Gaps in knowledge or disposition are identified for each risk, and a portfolio of research tasks is developed to fill them. Deliverables from the tasks inform the evidence base with the ultimate goal of defining the level of risk and reducing it to an acceptable level. A comprehensive framework for gap identification, focus, and metrics has been developed based on principles of continuous risk management and clinical care. Research towards knowledge gaps improves understanding of the likelihood, consequence or timeframe of the risk. Disposition gaps include development of standards or requirements for risk acceptance, development of countermeasures or technology to mitigate the risk, and yearly technology assessment related to watching developments related to the risk. Standard concepts from clinical care: prevention, diagnosis, treatment, monitoring, rehabilitation, and surveillance, can be used to focus gaps dealing with risk mitigation. The research plan for the new HRP Risk of Decompression Sickness (DCS) used the framework to identify one disposition gap related to establishment of a DCS standard for acceptable risk, two knowledge gaps related to DCS phenomenon and mission attributes, and three mitigation gaps focused on prediction, prevention, and new technology watch. These gaps were organized in this manner primarily based on target for closure and ease of organizing interim metrics so that gap status could be quantified. Additional considerations for the knowledge gaps were that one was highly design reference mission specific and the other gap was focused on DCS phenomenon.

Norcross, Jason↗
NASA NTRS2001

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

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

Post, Todd↗
NASA NTRS2020

Medical Data Architecture Prototype Development - Summary of Recent Work and Proposed Ideas for Upcoming Work

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically-relevant information to support medical operations during exploration missions, and in ExMC Gap Med 10: We do not have the capability to provide computed medical decision support during exploration missions. These gaps recognize the need for a comprehensive medical data management system and the accompanying computational support to provide autonomous medical care during long duration exploration missions. As the MDA matures—including the capability to comprehensively process and discover medically-relevant information to support medical operations during exploration missions—project focus will shift to maturing and extending the MDA platform to enable clinical decision support and real-time guidance. To date, the MDA foundational architecture has recommended exploration medical system Level of Care IV requirements through a series of test bed prototype developments and analog demonstrations. The next stage in the development will focus on more autonomous clinical decision making necessary to address challenges in executing a self-contained medical system that enables health care both with and without assistance from ground support. A thorough understanding of current state of medical decision support systems, advanced machine learning algorithms and vast and varied data sources is required. The development of a clinical decision support for exploration missions (Level of Care V) roadmap is needed: one that assesses of current state of the art of clinical decision support systems (CDSS), interoperability issues, identification of challenges in health and performance monitoring, obtaining and processing information from biosensors, knowledge and data management, data integration and fusion, and advanced algorithm development. This roadmap must also include rapid prototype development in the areas of data processing, advanced analysis and prediction of medical events, and treatment based on medically relevant information processing and evidence-based best practices. In this presentation, an overview of the relevant issues and the beginning framework of a Level of Care V CDSS development roadmap will be provided.

Krihak, M.↗
NASA NTRS1987

SOLON: An autonomous vehicle mission planner

The State-Operator Logic Machine (SOLON) Planner provides an architecture for effective real-time planning and replanning for an autonomous vehicle. The highlights of the system, which distinguish it from other AI-based planners that have been designed previously, are its hybrid application of state-driven control architecture and the use of both schematic representations and logic programming for the management of its knowledge base. SOLON is designed to provide multiple levels of planning for a single autonomous vehicle which is supplied with a skeletal, partially-specified mission plan at the outset of the vehicle's operations. This mission plan consists of a set of objectives, each of which will be decomposable by the planner into tasks. These tasks are themselves comparatively complex sets of actions which are executable by a conventional real-time control system which does not perform planning but which is capable of making adjustments or modifications to the provided tasks according to constraints and tolerances provided by the Planner. The current implementation of the SOLON is in the form of a real-time simulation of the Planner module of an Intelligent Vehicle Controller (IVC) on-board an autonomous underwater vehicle (AUV). The simulation is embedded within a larger simulator environment known as ICDS (Intelligent Controller Development System) operating on a Symbolics 3645/75 computer.

Dudziak, M. J.↗
NASA NTRS1988

Intelligent, autonomous systems in space

The Space Station is expected to be equipped with intelligent, autonomous capabilities; to achieve and incorporate these capabilities, the required technologies need to be identitifed, developed and validated within realistic application scenarios. The critical technologies for the development of intelligent, autonomous systems are discussed in the context of a generalized functional architecture. The present state of this technology implies that it be introduced and applied in an evolutionary process which must start during the Space Station design phase. An approach is proposed to accomplish design information acquisition and management for knowledge-base development.

Lum, H.↗
NASA NTRS2008

Exhaustive Thresholds and Resistance Checkpoints

Once deployed, all intricate systems that operate for a long time (such as an airplane or chemical processing plant) experience degraded performance during operational lifetime. These can result from losses of integrity in subsystems and parts that generally do not materially impact the operation of the vehicle (e.g., the light behind the button that opens the sliding door of the minivan). Or it can result from loss of more critical parts or subsystems. Such losses need to be handled quickly in order to avoid loss of personnel, mission, or part of the system itself. In order to manage degraded systems, knowledge of its potential problem areas and the means by which these problems are detected should be developed during the initial development of the system. Once determined, a web of sensors is employed and their outputs are monitored with other system parameters while the system is in preparation or operation. Just gathering the data is only part of the story. The interpretation of the data itself and the response of the system must be carefully developed as well to avoid a mishap. Typically, systems use a test-threshold-response paradigm to process potential system faults. However, such processing sub-systems can suffer from errors and oversights of a consistent type, causing system aberrant behavior instead of expected system and recovery operations. In our study, we developed a complete checklist for determining the completeness of a fault system and its robustness to common processing and response difficulties.

Easton, Charles↗
NASA NTRS2016

Climate Change Adaptation Activities at the NASA John F. Kennedy Space Center, FL., USA

In 2010, the Office of Strategic Infrastructure and Earth Sciences established the Climate Adaptation Science Investigators (CASI) program to integrate climate change forecasts and knowledge into sustainable management of infrastructure and operations needed for the NASA mission. NASA operates 10 field centers valued at $32 billion dollars, occupies 191,000 acres and employs 58,000 people. CASI climate change and sea-level rise forecasts focus on the 2050 and 2080 time periods. At the 140,000 acre Kennedy Space Center (KSC) data are used to simulate impacts on infrastructure, operations, and unique natural resources. KSC launch and processing facilities represent a valued national asset located in an area with high biodiversity including 33 species of special management concern. Numerical and advanced Bayesian and Monte Carlo statistical modeling is being conducted using LiDAR digital elevation models coupled with relevant GIS layers to assess potential future conditions. Results are provided to the Environmental Management Branch, Master Planning, Construction of Facilities, Engineering Construction Innovation Committee and our regional partners to support Spaceport development, management, and adaptation planning and design. Potential impacts to natural resources include conversion of 50% of the Center to open water, elevation of the surficial aquifer, alterations of rainfall and evapotranspiration patterns, conversion of salt marsh to mangrove forest, reductions in distribution and extent of upland habitats, overwash of the barrier island dune system, increases in heat stress days, and releases of chemicals from legacy contamination sites. CASI has proven successful in bringing climate change planning to KSC including recognition of the need to increase resiliency and development of a green managed shoreline retreat approach to maintain coastal ecosystem services while maximizing life expectancy of Center launch and payload processing resources.

plant communities↗
NASA NTRS2019

Short Course on Lithium-Ion Batteries: Fundamental Concepts, Battery Safety, and Modeling Techniques

When developing this course several years back I asked myself, "What do I think the TFAWS community needs to know about lithium-ion batteries and why should they care?" I think the answers to these questions can be boiled down to the following statements: 1. Lithium-ion (Li-ion) battery electrical performance and efficiency are heavily driven by thermal conditions. 2. Li-ion battery assemblies can experience single cell thermal runaway events which can lead to cell-to-cell propagation; these are thermally driven failure events that can be controlled with effective thermal management systems. 3. Knowledge of BOTH Li-ion battery fundamentals AND traditional thermal design principles are required to develop safe battery assemblies that are both gravimetrically and volumetrically optimized.This year the Short Course on Lithium-ion Batteries will be presented in a 2-part series. The first portion, "Fundamentals, Battery Safety, and Thermal Runaway," will focus on educating participants on the fundamental aspects of Li-ion batteries and on battery safety related topics (i.e. thermal runaway, cell-to-cell propagation, safe handling practices, et...). The second portion, "Practical Thermal Simulation Techniques," will provide participants with a real time demonstration of how to use Thermal Desktop to model of Li-ion battery assemblies. This part of the lesson will cover geometry simplification, mesh development, boundary conditions, and heat loads for both nominal operations (charge and discharge) and for thermal runaway events.

Walker, William↗
NASA NTRS2021

FRESCO: A Framework for Spacecraft Systems Autonomy

Achieving the science exploration and defense goals of the following decades will require flight systems capable of operations with limited operator contact, system mode changes and retasking based on sensor data, and complex robotic operations. To support these capabilities, increasingly autonomous flight systems are required that can perform dedicated mission functions, e.g. payload targeting and communications, and system-level functions, e.g. planning and goal monitoring. Architecting an autonomous system requires a well-reasoned, self-consistent framework to avoid \textit{ad hoc} design choices that will introduce complexity and risk. The Framework for Robust Execution and Scheduling of Commands On-Board, FRESCO, is the result of lessons learned in developing a software architecture to enable autonomous solar system exploration. FRESCO generalizes this work to offer a modular, software-agnostic approach to developing verifiable architecture for autonomous space systems. FRESCO specifies guiding principles, functions, interfaces, and interactions from which mission-specific autonomous control architectures can be derived. FRESCO is a principled framework relying on explicit, state-based goal definitions, centralized management of state knowledge, clearly separated control boundaries, and hierarchical reasoning. Using components from FRESCO reference architecture, an autonomous decision-making architecture can be designed for spacecraft which can then be mapped to flight software architecture. FRESCO is flexibly defined to enable autonomous control of flight systems built using extensive software and hardware heritage. Finally, FRESCO-derived architectures support a spectrum of operator/spacecraft interactions, ranging from traditional commanding to goal-driven commanding with the ability to change mission goals autonomously. FRESCO has been used in defining the autonomy architectures for the ASTERIA mission and have been demonstrated in laboratory and software simulation for small body rendezvous and in-space servicing missions.

Kolcio, Ksenia↗
NASA NTRS1989

Hubble Space Telescope Design Engineering Knowledgebase (HSTDEK)

The research covered here pays specific attention to the development of tools to assist knowledge engineers in acquiring knowledge and to assist other technical, engineering, and management personnel in automatically performing knowledge capture as part of their everyday work without adding any extra work to what they already do. Requirements for data products, the knowledge base, and methods for mapping knowledge in the documents onto the knowledge representations are discussed, as are some of the difficulties of capturing in the knowledge base the structure of the design process itself, along with a model of the system designed. The capture of knowledge describing the interactions of different components is also discussed briefly.

Johannes, James D.↗
NASA NTRS2015

ATM Technology Demonstration 1 (ATD-1) Project: Terminal Airspace Technologies for NextGen (Public)

This video highlights the human-in-the-loop (HITL) simulations conducted by the ATD-1 project and features visual elements developed for Traffic Management Advisor - Terminal Metering, Controller Managed Spacing, and Flight Deck Interval Management. The video content is fairly technical and intended for audiences that have some knowledge of air traffic management issues. This includes researchers and management from NASA, FAA, industry partners, and others interested in terminal metering, controller managed spacing, and interval management technologies. Please note that the media release only clears the video for peer audiences such as ATM conferences or as part of presentations to researchers.

Robinson, John E.↗
NASA NTRS2007

Systems Modeling to Implement Integrated System Health Management Capability

ISHM capability includes: detection of anomalies, diagnosis of causes of anomalies, prediction of future anomalies, and user interfaces that enable integrated awareness (past, present, and future) by users. This is achieved by focused management of data, information and knowledge (DIaK) that will likely be distributed across networks. Management of DIaK implies storage, sharing (timely availability), maintaining, evolving, and processing. Processing of DIaK encapsulates strategies, methodologies, algorithms, etc. focused on achieving high ISHM Functional Capability Level (FCL). High FCL means a high degree of success in detecting anomalies, diagnosing causes, predicting future anomalies, and enabling health integrated awareness by the user. A model that enables ISHM capability, and hence, DIaK management, is denominated the ISHM Model of the System (IMS). We describe aspects of the IMS that focus on processing of DIaK. Strategies, methodologies, and algorithms require proper context. We describe an approach to define and use contexts, implementation in an object-oriented software environment (G2), and validation using actual test data from a methane thruster test program at NASA SSC. Context is linked to existence of relationships among elements of a system. For example, the context to use a strategy to detect leak is to identify closed subsystems (e.g. bounded by closed valves and by tanks) that include pressure sensors, and check if the pressure is changing. We call these subsystems Pressurizable Subsystems. If pressure changes are detected, then all members of the closed subsystem become suspect of leakage. In this case, the context is defined by identifying a subsystem that is suitable for applying a strategy. Contexts are defined in many ways. Often, a context is defined by relationships of function (e.g. liquid flow, maintaining pressure, etc.), form (e.g. part of the same component, connected to other components, etc.), or space (e.g. physically close, touching the same common element, etc.). The context might be defined dynamically (if conditions for the context appear and disappear dynamically) or statically. Although this approach is akin to case-based reasoning, we are implementing it using a software environment that embodies tools to define and manage relationships (of any nature) among objects in a very intuitive manner. Context for higher level inferences (that use detected anomalies or events), primarily for diagnosis and prognosis, are related to causal relationships. This is useful to develop root-cause analysis trees showing an event linked to its possible causes and effects. The innovation pertaining to RCA trees encompasses use of previously defined subsystems as well as individual elements in the tree. This approach allows more powerful implementations of RCA capability in object-oriented environments. For example, if a pressurizable subsystem is leaking, its root-cause representation within an RCA tree will show that the cause is that all elements of that subsystem are suspect of leak. Such a tree would apply to all instances of leak-events detected and all elements in all pressurizable subsystems in the system. Example subsystems in our environment to build IMS include: Pressurizable Subsystem, Fluid-Fill Subsystem, Flow-Thru-Valve Subsystem, and Fluid Supply Subsystem. The software environment for IMS is designed to potentially allow definition of any relationship suitable to create a context to achieve ISHM capability.

Figueroa, Jorge F.↗
NASA NTRS2002

Conference Report: Masters Forum IV, February 2002

The purpose of the APPL Masters Forum is to bring together some of the best project managers at NASA, as well as those in industry and other government agencies, for 2 1/2 days of knowledge sharing. The project managers come eager to reflect on their project experiences, to learn new things from one another--and to unlearn a few things, too. This was the fourth Masters Forum, and the first one held outside Washington, DC. Fifty participants from across the country came to Dallas at the American Airlines Conference Center, a wonderful facility that was conveniently located by the airport and yet still seemed isolated from the rest of the world. Masters Forum IV was also the first one held during the winter. Previous Masters Forums have been during the summer. Hot, sticky Washington, D.C. in the summer may sound unpleasant, but frankly the popularity of earlier Forums is what led to this annual event becoming a semiannual one.

Post, Todd↗
NASA NTRS1997

Integrity Constraint Monitoring in Software Development: Proposed Architectures

In the development of complex software systems, designers are required to obtain from many sources and manage vast amounts of knowledge of the system being built and communicate this information to personnel with a variety of backgrounds. Knowledge concerning the properties of the system, including the structure of, relationships between and limitations of the data objects in the system, becomes increasingly more vital as the complexity of the system and the number of knowledge sources increases. Ensuring that violations of these properties do not occur becomes steadily more challenging. One approach toward managing the enforcement or system properties, called context monitoring, uses a centralized repository of integrity constraints and a constraint satisfiability mechanism for dynamic verification of property enforcement during program execution. The focus of this paper is to describe possible software architectures that define a mechanism for dynamically checking the satisfiability of a set of constraints on a program. The next section describes the context monitoring approach in general. Section 3 gives an overview of the work currently being done toward the addition of an integrity constraint satisfiability mechanism to a high-level program language, SequenceL, and demonstrates how this model is being examined to develop a general software architecture. Section 4 describes possible architectures for a general constraint satisfiability mechanism, as well as an alternative approach that, uses embedded database queries in lieu of an external monitor. The paper concludes with a brief summary outlining the, current state of the research and future work.

Fernandez, Francisco G.↗
DOE OSTI2024

Survey and Gap Prioritization of U.S. Electric Vehicle Charge Management Deployments

The goal of this study was to survey and characterize the scope of current technical and programmatic knowledge pertaining to EV charge management technologies and practices in the US and relevant international jurisdictions. This characterization of existing field demonstrations and knowledge derived were used to determine gaps in the SCM demonstration landscape. Addressing these gaps through research and demonstration could increase confidence in the U.S. that load management and EV charge control could achieve overarching societal benefits. A survey of charge management deployments and input from stakeholders was completed to determine the state-of-the-art of smart charge management (SCM) where SCM is defined as controlling the amount of power exchanged between chargers and EVs to meet customers' charging needs while also responding to external power demand or pricing signals to provide load management, resilience, or other benefits to the customer and electric grid. The survey was the basis of the gap analysis in this report and determines which areas are well understood, with high confidence, and which areas need further investigation. Existing examples of EV charge management are characterized here to determine aspects that are ready for widespread deployment and have been demonstrated in the field. These include demonstration studies, pilots, programs, and EV-specific tariffs. In all, 110 examples of charge management were characterized. The data sources were public literature and utility filings as well as targeted interviews. In addition, 43 interviews with stakeholders were conducted with a consistent set of questions used in each interview. This study prioritized gaps in demonstrated SCM capabilities based on 1) Urgency of the particular use-case to offset traditional grid assets, 2) Impact, extensibility, and scaling of results across the entire spectrum of 3000+ utility service territories including projected technical and market potential for a given grid service, and 3) Value of federal funding in addressing the gap, including potential to leverage and/or add scope to existing field demonstrations funded by other non-federal funding mechanisms.

33 ADVANCED PROPULSION SYSTEMS↗
NASA NTRS2012

Safety Risk Knowledge Elicitation in Support of Aeronautical R and D Portfolio Management: A Case Study

Aviation is a problem domain characterized by a high level of system complexity and uncertainty. Safety risk analysis in such a domain is especially challenging given the multitude of operations and diverse stakeholders. The Federal Aviation Administration (FAA) projects that by 2025 air traffic will increase by more than 50 percent with 1.1 billion passengers a year and more than 85,000 flights every 24 hours contributing to further delays and congestion in the sky (Circelli, 2011). This increased system complexity necessitates the application of structured safety risk analysis methods to understand and eliminate where possible, reduce, and/or mitigate risk factors. The use of expert judgments for probabilistic safety analysis in such a complex domain is necessary especially when evaluating the projected impact of future technologies, capabilities, and procedures for which current operational data may be scarce. Management of an R&D product portfolio in such a dynamic domain needs a systematic process to elicit these expert judgments, process modeling results, perform sensitivity analyses, and efficiently communicate the modeling results to decision makers. In this paper a case study focusing on the application of an R&D portfolio of aeronautical products intended to mitigate aircraft Loss of Control (LOC) accidents is presented. In particular, the knowledge elicitation process with three subject matter experts who contributed to the safety risk model is emphasized. The application and refinement of a verbal-numerical scale for conditional probability elicitation in a Bayesian Belief Network (BBN) is discussed. The preliminary findings from this initial step of a three-part elicitation are important to project management practitioners as they illustrate the vital contribution of systematic knowledge elicitation in complex domains.

Shih, Ann T.↗