Search NASA⌕ Search

SEARCH · Search NASA

Results for “configuration 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

System architecture and method of processing data therein

A system architecture encoded on a non-transitory computer readable medium, the system architecture includes a first protocol. The first protocol is configured to receive a plurality of outputs from an ICS used in controlling an industrial system. The first protocol is configured to receive a plurality of inputs from a physical module. The physical module includes at least one of a component, a sensor, or the ICS. Additionally, the system architecture includes a second protocol, wherein the second protocol is configured to validate the plurality of inputs from the first protocol. Moreover, the system architectures includes a third protocol, wherein the third protocol is configured to validate the plurality of outputs from the first protocol. Further, the system architecture includes a fourth protocol, wherein the fourth protocol is configured to manage the ICS based on the second protocol and the third protocol.

Abdel-Khalik, Hany S.↗

Configuring a Graphical User Interface for Managing Local HYSPLIT Model Runs Through AWIPS

Responding to incidents involving the release of harmful airborne pollutants is a continual challenge for Weather Forecast Offices in the National Weather Service. When such incidents occur, current protocol recommends forecaster-initiated requests of NOAA's Hybrid Single-Particle Lagrangian Integrated Trajectory (HYSPLIT) model output through the National Centers of Environmental Prediction to obtain critical dispersion guidance. Individual requests are submitted manually through a secured web site, with desired multiple requests submitted in sequence, for the purpose of obtaining useful trajectory and concentration forecasts associated with the significant release of harmful chemical gases, radiation, wildfire smoke, etc., into local the atmosphere. To help manage the local HYSPLIT for both routine and emergency use, a graphical user interface was designed for operational efficiency. The interface allows forecasters to quickly determine the current HYSPLIT configuration for the list of predefined sites (e.g., fixed sites and floating sites), and to make any necessary adjustments to key parameters such as Input Model. Number of Forecast Hours, etc. When using the interface, forecasters will obtain desired output more confidently and without the danger of corrupting essential configuration files.

Wheeler, mark M.↗

Land-mobile satellite communication system

A satellite communications system includes an orbiting communications satellite for relaying communications to and from a plurality of ground stations, and a network management center for making connections via the satellite between the ground stations in response to connection requests received via the satellite from the ground stations, the network management center being configured to provide both open-end service and closed-end service. The network management center of one embodiment is configured to provides both types of service according to a predefined channel access protocol that enables the ground stations to request the type of service desired. The channel access protocol may be configured to adaptively allocate channels to open-end service and closed-end service according to changes in the traffic pattern and include a free-access tree algorithm that coordinates collision resolution among the ground stations.

Yan, Tsun-Yee↗

Systems and methods for managing energy storage operations

An energy storage device (ESD) manager determines charge conditions that result in charge-related aging of an energy storage device (ESD), such as a battery, cell, or the like. The ESD manager may determine charge-related costs for charge operations, which may quantify charge-related aging imposed by subjecting ESD to specified charge conditions. The ESD manager may evaluate and/or modify charge operations to reduce charge-related aging. The ESD manager may be further configured to model charge-related aging behavior over time and/or under variable charge conditions. The ESD manager may configure charge operations to ensure that charge-related performance loss remains below a threshold for a specified usage duration.

Gering, Kevin L.↗

pyam: Python Implementation of YaM

pyam is a software development framework with tools for facilitating the rapid development of software in a concurrent software development environment. pyam provides solutions for development challenges associated with software reuse, managing multiple software configurations, developing software product lines, and multiple platform development and build management. pyam uses release-early, release-often development cycles to allow developers to integrate their changes incrementally into the system on a continual basis. It facilitates the creation and merging of branches to support the isolated development of immature software to avoid impacting the stability of the development effort. It uses modules and packages to organize and share software across multiple software products, and uses the concepts of link and work modules to reduce sandbox setup times even when the code-base is large. One sidebenefit is the enforcement of a strong module-level encapsulation of a module s functionality and interface. This increases design transparency, system stability, and software reuse. pyam is written in Python and is organized as a set of utilities on top of the open source SVN software version control package. All development software is organized into a collection of modules. pyam packages are defined as sub-collections of the available modules. Developers can set up private sandboxes for module/package development. All module/package development takes place on private SVN branches. High-level pyam commands support the setup, update, and release of modules and packages. Released and pre-built versions of modules are available to developers. Developers can tailor the source/link module mix for their sandboxes so that new sandboxes (even large ones) can be built up easily and quickly by pointing to pre-existing module releases. All inter-module interfaces are publicly exported via links. A minimal, but uniform, convention is used for building modules.

Myint, Steven↗

Subsonic Aerodynamic Assessment of Vortex Flow Management Devices on a High-Speed Civil Transport Configuration

An experimental investigation of the effects of leading-edge vortex management devices on the subsonic performance of a high-speed civil transport (HSCT) configuration was conducted in the Langley 14- by 22-Foot Subsonic Tunnel. Data were obtained over a Mach number range of 0.14 to 0.27, with corresponding chord Reynolds numbers of 3.08 x 10 (sup 6) to 5.47 x 10 (sup 6). The test model was designed for a cruise Mach number of 2.7. During the subsonic high-lift phase of flight, vortical flow dominates the upper surface flow structure, and during vortex breakdown, this flow causes adverse pitch-up and a reduction of usable lift. The experimental results showed that the beneficial effects of small leading-edge vortex management devices located near the model reference center were insufficient to substantially affect the resulting aerodynamic forces and moments. However, devices located at or near the wiring apex region demonstrated potential for pitch control with little effect on overall lift.

Campbell, Bryan A.↗

Management of space networks

NASA has proposed missions to the Moon and Mars that reflect three areas of emphasis: human presence, exploration, and space resource development for the benefit of Earth. A major requirement for such missions is a robust and reliable communications architecture. Network management--the ability to maintain some degree of human and automatic control over the span of the network from the space elements to the end users on Earth--is required to realize such robust and reliable communications. This article addresses several of the architectural issues associated with space network management. Round-trip delays, such as the 5- to 40-min delays in the Mars case, introduce a host of problems that must be solved by delegating significant control authority to remote nodes. Therefore, management hierarchy is one of the important architectural issues. The following article addresses these concerns, and proposes a network management approach based on emerging standards that covers the needs for fault, configuration, and performance management, delegated control authority, and hierarchical reporting of events. A relatively simple approach based on standards was demonstrated in the DSN 2000 Information Systems Laboratory, and the results are described.

Markley, R. W.↗

The Network Configuration of an Object Relational Database Management System

The networking and implementation of the Oracle Database Management System (ODBMS) requires developers to have knowledge of the UNIX operating system as well as all the features of the Oracle Server. The server is an object relational database management system (DBMS). By using distributed processing, processes are split up between the database server and client application programs. The DBMS handles all the responsibilities of the server. The workstations running the database application concentrate on the interpretation and display of data.

Diaz, Philip↗

A Programmable SDN+NFV Architecture for UAV Telemetry Monitoring

With the explosive growth in UAV numbers forecast worldwide, a core concern is how to manage the ad-hoc network configuration required for mobility management. As UAVs migrate among ground control stations, associated network services, routing and operational control must also rapidly migrate to ensure a seamless transition. In this paper, we present a novel, lightweight and modular architecture which supports high mobility, resilience and flexibility through the application of SDN and NFV principles on top of the UAV infrastructure. By combining SDN programmability and Network Function Virtualization we can achieve resilient infrastructure migration of network services, such as network monitoring and anomaly detection, coupled with migrating UAVs to enable high mobility management. Our container-based monitoring and anomaly detection Network Functions (NFs) can be tuned to specific UAV models providing operators better insight during live, high-mobility deployments. We evaluate our architecture against telemetry from over 80flights from a scientific research UAV infrastructure.

Resilience↗

Integrated energy harvesting transceivers and transmitters with dual-antenna architecture for miniaturized implants and electrochemical sensors

Systems and methods for utilizing a small form-factor, wirelessly powered transceiver are disclosed. In one embodiment, a wireless powered transceiver includes a receive antenna configured to receive a receive signal, a transmit antenna configured to transmit a transmit signal, a power harvesting system including a rectifier circuit configured convert radio frequency energy from the receive signal into DC (direct current) voltage, and a power management unit (PMU) configured to set the operating mode and biasing condition of the receive and transmit circuitry blocks and provide DC voltage from the receive circuitry block to the transmit circuitry block to maintain a minimum voltage, a receiver circuitry block configured to provide energy from the receive signal to the power harvesting system, and a transmitter circuitry block including a data modulator circuit, the data modulator circuit configured to generate the transmit signal using DC voltage received from the power management unit.

Babakhani, Aydin↗

Integrated energy harvesting transceivers and transmitters with dual-antenna architecture for miniaturized implants and electrochemical sensors

Systems and methods for utilizing a small form-factor, wirelessly powered transceiver are disclosed. In one embodiment, a wireless powered transceiver includes a receive antenna configured to receive a receive signal, a transmit antenna configured to transmit a transmit signal, a power harvesting system including a rectifier circuit configured convert radio frequency energy from the receive signal into DC (direct current) voltage, and a power management unit (PMU) configured to set the operating mode and biasing condition of the receive and transmit circuitry blocks and provide DC voltage from the receive circuitry block to the transmit circuitry block to maintain a minimum voltage, a receiver circuitry block configured to provide energy from the receive signal to the power harvesting system, and a transmitter circuitry block including a data modulator circuit, the data modulator circuit configured to generate the transmit signal using DC voltage received from the power management unit.

Babakhani, Aydin↗

YAM- A Framework for Rapid Software Development

YAM is a software development framework with tools for facilitating the rapid development and integration of software in a concurrent software development environment. YAM provides solutions for thorny development challenges associated with software reuse, managing multiple software configurations, the development of software product-lines, multiple platform development and build management. YAM uses release-early, release-often development cycles to allow developers to incrementally integrate their changes into the system on a continual basis. YAM facilitates the creation and merging of branches to support the isolated development of immature software to avoid impacting the stability of the development effort. YAM uses modules and packages to organize and share software across multiple software products. It uses the concepts of link and work modules to reduce sandbox setup times even when the code-base is large. One side-benefit is the enforcement of a strong module-level encapsulation of a module s functionality and interface. This increases design transparency, system stability as well as software reuse. YAM is in use by several mid-size software development teams including ones developing mission-critical software.

simulations↗

ATM Technology Demonstration-1 Phase II Boeing Configurable Graphical Display (CGD) Software Design Description

This Software Description Document (SDD) captures the design for developing the Flight Interval Management (FIM) system Configurable Graphics Display (CGD) software. Specifically this SDD describes aspects of the Boeing CGD software and the surrounding context and interfaces. It does not describe the Honeywell components of the CGD system. The SDD provides the system overview, architectural design, and detailed design with all the necessary information to implement the Boeing components of the CGD software and integrate them into the CGD subsystem within the larger FIM system. Overall system and CGD system-level requirements are derived from the CGD SRS (in turn derived from the Boeing System Requirements Design Document (SRDD)). Display and look-and-feel requirements are derived from Human Machine Interface (HMI) design documents and working group recommendations. This Boeing CGD SDD is required to support the upcoming Critical Design Review (CDR).

Wilber, George F.↗

Nickel-cadmium Battery Cell Reversal from Resistive Network Effects

During the individual cell short-down procedures often used for storing or reconditioning nickel-cadmium (Ni-Cd) batteries, it is possible for significant reversal of the lowest capacity cells to occur. The reversal is caused by the finite resistance of the common current-carrying leads in the resistive network that is generally used during short-down. A model is developed to evaluate the extent of such a reversal in any specific battery, and the model is verified by means of data from the short-down of a f-cell, 3.5-Ah battery. Computer simulations of short-down on a variety of battery configurations indicate the desirability of controlling capacity imbalances arising from cell configuration and battery management, limiting variability in the short-down resistors, minimizing lead resistances, and optimizing lead configurations.

Zimmerman, A. H.↗

phenix v. 7.0

SAND2021-6741 O phenix is Sandia's orchestration tool that allows users to quickly deploy, un-deploy, and interact with SCEPTRE ICS environments. phenix is an orchestration tool used for managing the creation, configuration, and deployment of modeling and simulation environments. As an abstraction layer on top of an underlying virtual machine manager called minimega, phenix organizes the network, application, and scenario information for a given deployment. It allows users to create, configure, and deploy experiments in a repeatable and rapid fashion. An application framework provides the flexibility to manipulate an experiment to suit various needs and requirements. phenix also includes a web-based graphical user interface (GUI) where experiments can be created, configured, and interacted with.

Sahakian, Meghan↗

BEE - FY20 P6-2: Support for HPC resource managers 2.3.6.01 – LANL ATDM ST / STNS01-6 P6 Milestone Completion Documentation

BEE uses abstract interfaces between core functionality and specific driver code. An example of this is the worker_interface. The worker_interface is used by the BEETaskManager to communicate with the HPC system-specific resource manager (e.g. Slurm) and container runtime (e.g. Charliecloud). BEE initially only supported the Slurm HPC resource manager. This activity will make HPC resource manager support a configurable option. When this activity is complete BEE will support both the Slurm and LSF resource managers.

97 MATHEMATICS AND COMPUTING↗

Human System Risk Management for Space Flight

This brief abstract reviews the development of the current day approach to human system risk management for space flight and the development of the critical components of this process over the past few years. The human system risk management process now provides a comprehensive assessment of each human system risk by design reference mission (DRM) and is evaluated not only for mission success but also for long‐term health impacts for the astronauts. The discipline of bioastronautics is the study of the biological and medical effects of space flight on humans. In 1997, the Space Life Sciences Directorate (SLSD) initiated the Bioastronautics Roadmap (Roadmap) as the "Critical Path Roadmap", and in 1998 participation in the roadmap was expanded to include the National Space Biomedical Research Institute (NSBRI) and the external community. A total of 55 risks and 250 questions were identified and prioritized and in 2000, the Roadmap was base-lined and put under configuration control. The Roadmap took into account several major advisory committee reviews including the Institute of Medicine (IOM) "Safe Passage: Astronaut care for Exploration Missions", 2001. Subsequently, three collaborating organizations at NASA HQ (Chief Health and Medical Officer, Office of Space Flight and Office of Biological & Physical Research), published the Bioastronautics Strategy in 2003, that identified the human as a "critical subsystem of space flight" and noted that "tolerance limits and safe operating bands must be established" to enable human space flight. These offices also requested a review by the IOM of the Roadmap and that review was published in October 2005 as "A Risk Reduction Strategy for Human Exploration of Space: A Review of NASA's Bioastronautics Roadmap", that noted several strengths and weaknesses of the Roadmap and made several recommendations. In parallel with the development of the Roadmap, the Office of the Chief Health and Medical Officer (OCHMO) began a process in 2004 of evaluating the tolerance limits and safe operating bands called for in the Bioastronautics Strategy. Over the next several years, the concept of the "operating bands" were turned into Space Flight Human System Standards (SFHSS), developed by the technical resources of the SLSD at the NASA Johnson Space Center (JSC). These standards were developed and reviewed at the SLSD and then presented to the OCHMO for acceptance. The first set of standards was published in 2007 as the NASA‐STD‐3001, Volume 1, Crew Health that elaborated standards for several physiological areas such as cardiovascular, musculoskeletal, radiation exposure and nutrition. Volume 2, Human Factors, Habitability and Human Health was published in 2011, along with development guidance in the Human Integration Design Handbook (HIDH). Taken together, the SFHSS Volumes 1 and 2, and the HIDH replaced the NASA‐STD‐3000 with new standards and revisions of the older document. Three other changes were also taking place that facilitated the development of the human system risk management approach. In 2005, the life sciences research and development portfolio underwent a comprehensive review through the Exploration Systems Architecture Study (ESAS) that resulted in the reformulation of the Bioastronautics Program into Human Research Program (HRP) that was focused on appropriate mitigation results for high priority human health risks. The baseline HRP budget was established in August 2005. In addition, the OCHMO formulated the Health and Medical Technical Authority (HMTA) in 2006 that established the position of the Chief Medical Officer (CMO) at the NASA JSC along with other key technical disciplines, and the OCHMO became the responsible office for the SFHSS as noted above. The final change was the establishment in 2008 of the Human System Risk Board (HSRB), chaired by the CMO with representation from the HRP, SLSD management and technical experts. The HSRB then began to review all human system risks, established a comprehensive risk management and configuration management plan and data sharing policy. These major developments of standards, the HRP, the HMTA and a forum for review of human system risks (HSRB) facilitated the integration of human research, medical operations, systems engineering and many other disciplines in the comprehensive review of human system risks. The HSRB began a comprehensive review of all potential inflight medical conditions and events and over the course of several reviews consolidated the number of human system risks to 30 where the greatest emphasis is placed for investing program dollars for risk mitigation. The HSRB considers all available evidence from human research, medical operations and occupational surveillance in assessing the risks for appropriate mitigation and future work. All applicable DRMs (low earth orbit 6 and 12 months, deep space sortie for 30 days and 1 year, a one year lunar mission, and a planetary mission for 3 years) are considered as human system risks are modified by the hazards associated with space flight such as microgravity, exposure to radiation, distance from the earth, isolation and a closed environment. Each risk has a summary assessment representing the state of knowledge/evidence base for that risk, the available risk mitigations, traceability to the SFHSS and program requirements, and future work required. These data then can drive coordinated budgets across the HRP, the International Space Station, Crew Health and Safety and Advanced Exploration System budgets. These risk assessments were completed for 6 DRMs in December of 2014 and serve as the baseline for which subsequent research and technology development and crew health care portfolios can be assessed. The HSRB will review each risk at least annually and especially when new information is available that must be considered for effective risk mitigation. The current status of each risk can be reported to program management for operations, budget reviews and general oversight of the human system risk management program.

Davis, Jeffrey↗

Attitude control/momentum management of the Space Station Freedom for large angle torque-equilibrium-attitude configurations

An attitude-control and momentum-management (ACMM) system for the Space Station in a large-angle torque-equilibrium-attitude (TEA) configuration is developed analytically and demonstrated by means of numerical simulations. The equations of motion for a rigid-body Space Station model are outlined; linearized equations for an arbitrary TEA (resulting from misalignment of control and body axes) are derived; the general requirements for an ACMM are summarized; and a pole-placement linear-quadratic regulator solution based on scheduled gains is proposed. Results are presented in graphs for (1) simulations based on configuration MB3 (showing the importance of accounting for the cross-inertia terms in the TEA estimate) and (2) simulations of a stepwise change from configuration MB3 to the 'assembly complete' stage over 130 orbits (indicating that the present ACCM scheme maintains sufficient control over slowly varying Space Station dynamics).

Parlos, Alexander G.↗