Search NASA⌕ Search

SEARCH · Search NASA

Results for “distribution management system”

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 415 records · Page 23
All sourcesNASA NTRSDOE OSTI
NASA NTRS2008

PrismTech Data Distribution Service Java API Evaluation

My internship duties with Launch Control Systems required me to start performance testing of an Object Management Group's (OMG) Data Distribution Service (DDS) specification implementation by PrismTech Limited through the Java programming language application programming interface (API). DDS is a networking middleware for Real-Time Data Distribution. The performance testing involves latency, redundant publishers, extended duration, redundant failover, and read performance. Time constraints allowed only for a data throughput test. I have designed the testing applications to perform all performance tests when time is allowed. Performance evaluation data such as megabits per second and central processing unit (CPU) time consumption were not easily attainable through the Java programming language; they required new methods and classes created in the test applications. Evaluation of this product showed the rate that data can be sent across the network. Performance rates are better on Linux platforms than AIX and Sun platforms. Compared to previous C++ programming language API, the performance evaluation also shows the language differences for the implementation. The Java API of the DDS has a lower throughput performance than the C++ API.

Riggs, Cortney↗
NASA NTRS1990

Tools for distributed application management

Distributed application management consists of monitoring and controlling an application as it executes in a distributed environment. It encompasses such activities as configuration, initialization, performance monitoring, resource scheduling, and failure response. The Meta system is described: a collection of tools for constructing distributed application management software. Meta provides the mechanism, while the programmer specifies the policy for application management. The policy is manifested as a control program which is a soft real time reactive program. The underlying application is instrumented with a variety of built-in and user defined sensors and actuators. These define the interface between the control program and the application. The control program also has access to a database describing the structure of the application and the characteristics of its environment. Some of the more difficult problems for application management occur when pre-existing, nondistributed programs are integrated into a distributed application for which they may not have been intended. Meta allows management functions to be retrofitted to such programs with a minimum of effort.

Marzullo, Keith↗
NASA NTRS1999

NASA Occupational Health Program FY98 Self-Assessment

The NASA Functional Management Review process requires that each NASA Center conduct self-assessments of each functional area. Self-Assessments were completed in June 1998 and results were presented during this conference session. During FY 97 NASA Occupational Health Assessment Team activities, a decision was made to refine the NASA Self-Assessment Process. NASA Centers were involved in the ISO registration process at that time and wanted to use the management systems approach to evaluate their occupational health programs. This approach appeared to be more consistent with NASA's management philosophy and would likely confer status needed by Senior Agency Management for the program. During FY 98 the Agency Occupational Health Program Office developed a revised self-assessment methodology based on the Occupational Health and Safety Management System developed by the American Industrial Hygiene Association. This process was distributed to NASA Centers in March 1998 and completed in June 1998. The Center Self Assessment data will provide an essential baseline on the status of OHP management processes at NASA Centers. That baseline will be presented to Enterprise Associate Administrators and DASHO on September 22, 1998 and used as a basis for discussion during FY 99 visits to NASA Centers. The process surfaced several key management system elements warranting further support from the Lead Center. Input and feedback from NASA Centers will be essential to defining and refining future self assessment efforts.

Brisbin, Steven G.↗
NASA NTRSDate not supplied

Risk-Reduction Autonomy Implementation to Enable NASA Artemis Missions

To achieve NASA’s Artemis program mission objectives a high level of autonomy and ubiquitous autonomy throughout the systems that are being developed will be necessary. The autonomous systems of Artemis will require a distributed autonomy capability, with autonomous systems organized functionally in a hierarchical architecture, where systems at higher levels of the hierarchy have authority over systems at lower levels. The challenge of developing autonomy technologies and concepts of operations for Artemis has been undertaken by the NASA Gateway Working Group. This group has developed requirements, architectures, concepts of operations, and interface control documents, in the context of a hierarchical distributed architecture that includes the following: a Vehicle System Manager (VSM) that autonomously manages the entire Gateway; Module System Managers (MSMs) that autonomously manage each module; and System Managers (SMs) that autonomously manage systems within a module(i.e. ECLSS).A substantially high level of autonomy needs to be achieved by each element of the hierarchy (VSM, MSM, SM)to meet requirements for uncrewed operations; this includes conditions that will have minimal and/or delayed ground intervention (i.e. requirements for sustainability for months of operation without crew or ground support). To advance an implementation of this autonomy design (Gateway Autonomy Design –GAD), a collaboration was established between the Autonomous Systems Laboratory (ASL) at NASA Stennis Space Center and Lockheed Martin. The objectives of this partnership were the following: (1)to implement autonomy at the VSM, MSM, and SM levels;(2) to implement communications among a VSM, 2 MSMs, ORION (a visiting vehicle somewhat equivalent to a module) and 1 SM (a power system), and (3) test autonomous operations with representative use cases. A SM backed by a high-fidelity simulation was created to facilitate demonstrations of use cases that originated in a system of a module. Communication between the VSM and MSMs was implemented according to Concepts of Operations and Interface Control Documents (ICDs). Demonstrations were conducted to address nominal and off-nominal operations and multi-module interactions with VSM. Additionally, user interfaces were created to provide awareness about ongoing processes and results while enhancing the demonstration. Demonstrations included the following use cases: (1)Orion as visiting vehicle registers with VSM;(2) VSM reschedules a module’s timelines when another module’s MSM task fails; and (3) a module’s Power System Manager (PSM) standalone demonstration that included component failure diagnostics, tracing component failure to effected components, which in turn, reports failure information up to the VSM for acknowledgement and display. This paper will describe the detailed technology and autonomous systems developed, and the integrated multi-module demonstrations conducted. Also, challenges that must be met to fully implement the GAD defined by Gateway will be addressed.

Autonomous Systems↗
NASA NTRS2008

Spaceborne Processor Array

A Spaceborne Processor Array in Multifunctional Structure (SPAMS) can lower the total mass of the electronic and structural overhead of spacecraft, resulting in reduced launch costs, while increasing the science return through dynamic onboard computing. SPAMS integrates the multifunctional structure (MFS) and the Gilgamesh Memory, Intelligence, and Network Device (MIND) multi-core in-memory computer architecture into a single-system super-architecture. This transforms every inch of a spacecraft into a sharable, interconnected, smart computing element to increase computing performance while simultaneously reducing mass. The MIND in-memory architecture provides a foundation for high-performance, low-power, and fault-tolerant computing. The MIND chip has an internal structure that includes memory, processing, and communication functionality. The Gilgamesh is a scalable system comprising multiple MIND chips interconnected to operate as a single, tightly coupled, parallel computer. The array of MIND components shares a global, virtual name space for program variables and tasks that are allocated at run time to the distributed physical memory and processing resources. Individual processor- memory nodes can be activated or powered down at run time to provide active power management and to configure around faults. A SPAMS system is comprised of a distributed Gilgamesh array built into MFS, interfaces into instrument and communication subsystems, a mass storage interface, and a radiation-hardened flight computer.

Chow, Edward T.↗
NASA NTRS1990

Environmental Control and Life Support System

Viewgraphs on the Environmental Control and Life Support System (ECLSS) for the space station are presented. The ECLSS is divided into six subsystems: temperature and humidity control (THC), atmosphere control and supply (ACS), atmosphere revitalization (AR), fire detection and suppression (FDS), water recovery management (WRM), and waste management (WM). Topics covered include: ECLSS subsystem functions; ECLSS distributed system; ECLSS functional distribution; CO2 removal; CO2 reduction; oxygen generation; urine processor; and potable water recovery.

Ray, Charles↗
NASA NTRS1985

Space power systems - 'Spacecraft 2000'

The program 'Spacecraft 2000' has the objective to identify critical, high-payoff, potential spacecraft technologies, taking into account the formulation, advocation, and the management of the requisite technology development programs. This program represents a joint NASA-industry program. The technology areas addressed by 'Spacecraft 2000' are related to spacecraft power/energy storage, thermal control/thermal management, power management and distribution, autonomous operation-control, on-board system integration, spacecraft environmental interactions, secondary propulsion, communications technologies, a total system response approach, and system-subsystem technology verification. The expected benefits of a development of advanced technologies include decreased spacecraft bus system weights, decreased mission costs, increased reliability/lifetimes, and increased operational flexibility.

Faymon, K. A.↗
NASA NTRSDate not supplied

Informing New Concepts for UAS and Autonomous System Safety Management using Disaster Management and First Responder Scenarios

As emerging flight operations become more prevalent and increasingly automated and distributed, the capabilities for managing safety of vehicles and operations will also need to evolve. To address this challenge, the National Academies has envisioned an In-Time Aviation Safety Management System (IASMS) capability for a wide range of aviation operations including current commercial operations as well as new entrants envisioned with advanced air mobility (AAM). The suite of IASMS services, functions, and capabilities (SFCs) would be implemented in a federated approach and would address trends as well as individual operations. Through predictive modeling and data analysis, IASMS is envisioned to identify arising risks so that they can be mitigated, in-time, before a safety incident occurs. IASMS and its requisite set of SFCs must leverage a wide range of information to perform. To better understand these new needs, FSF worked with the aviation and humanitarian communities to develop and validate scenarios that include traditional aviation operations and UAS operations intermingled as they are deployed for disaster management and first responder (DMFR) situations. The three scenarios developed include: • Post Natural disaster response, such as a hurricane, involving multiple parties utilizing traditional aviation and UAS to support rescue operations, surveil damage, and locate survivors needing assistance. • Wildfire fighting in remote locations with traditional aircraft for transport and fire-retardant delivery combined with UAS for surveillance of fire locations as well as to track individual firefighter locations. • Medical Operations and AAM in Urban Environments including passenger-carrying helicopters and AAM vehicles, medical missions (such as transport of radio-pharmaceuticals), and other UAS delivery operations (such as the delivery of defibrillators). Each scenario was developed and validated by representatives with expertise in humanitarian operations, urban and rural emergency response, air traffic management, UAS operations, and traditional flight operations. The scenario definitions address roles and responsibilities of individual actors, the appropriate utilization of UAS, and the actions taken by those actors to appropriately manage risks associated with the mission and environment. The risks to aviation traffic and to people on the ground explored included potential risks arising from incompatibilities in calculating reference altitudes (eg, differing uses of AGL, MSL, barometric, or GPS-derived values), loss of command and control (C2) communications, rapid changes in weather and winds, and physical interference. For each risk, IASMS SFCs were postulated in the context of monitoring services, risk assessment capabilities, and identifying appropriate mitigation strategies. The identified SFC capabilities were envisioned from known services postulated for IASMS and for UTM. For these unique environments, IASMS SFCs are needed to address conditions such as hazardous payloads, micro-climates and urban canyons, and the need to keep uninvolved air traffic out of the area where DMFR operations are being conducted. The second phase of analysis focused on inferring the specific information needs and the SFCs for IASMS, utilizing a structure of 16 information classes to organize requirements. For each of the risks identified in the workshops, it was postulated what data sources would be necessary to monitor critical aspects of the risk (eg, surrounding air traffic, ground population, terrain, etc). to be directly measured as well as data that would be derived, which implies additional SFCs for different actors to understand what information would likely be exchanged between parties. For an IASMS to be effective, additional research is needed to develop the advanced algorithms that can address the increasingly autonomous and complex operations in differing environments and to develop means of identifying unknown risks. Looking at these scenarios highlighted a number of research issues. These include the ability to quickly "cordon off" airspace thru temporary flight restrictions (TFRs) or other means, developing clear definitions to enable automation-based algorithms for prioritizing operations, defining airspace density metrics, standardization of altitude reporting, and establishing a basis for safety data metrics definition and collection. This paper seeks to outline the development of an IASMS in the context of the DMFR scenarios and resulting demonstrations. Utilizing this contextual approach, NASA will generate recommendations for an assured safety framework for AAM operations that enables AAM operations to safely access the NAS.

In Time Aviation Safety Management System↗
NASA NTRS2001

A Software Architecture for Intelligent Synthesis Environments

The NASA's Intelligent Synthesis Environment (ISE) program is a grand attempt to develop a system to transform the way complex artifacts are engineered. This paper discusses a "middleware" architecture for enabling the development of ISE. Desirable elements of such an Intelligent Synthesis Architecture (ISA) include remote invocation; plug-and-play applications; scripting of applications; management of design artifacts, tools, and artifact and tool attributes; common system services; system management; and systematic enforcement of policies. This paper argues that the ISA extend conventional distributed object technology (DOT) such as CORBA and Product Data Managers with flexible repositories of product and tool annotations and "plug-and-play" mechanisms for inserting "ility" or orthogonal concerns into the system. I describe the Object Infrastructure Framework, an Aspect Oriented Programming (AOP) environment for developing distributed systems that provides utility insertion and enables consistent annotation maintenance. This technology can be used to enforce policies such as maintaining the annotations of artifacts, particularly the provenance and access control rules of artifacts-, performing automatic datatype transformations between representations; supplying alternative servers of the same service; reporting on the status of jobs and the system; conveying privileges throughout an application; supporting long-lived transactions; maintaining version consistency; and providing software redundancy and mobility.

Filman, Robert E.↗
NASA NTRS2010

Analyzing Distributed Functions in an Integrated Hazard Analysis

Large scale integration of today's aerospace systems is achievable through the use of distributed systems. Validating the safety of distributed systems is significantly more difficult as compared to centralized systems because of the complexity of the interactions between simultaneously active components. Integrated hazard analysis (IHA), a process used to identify unacceptable risks and to provide a means of controlling them, can be applied to either centralized or distributed systems. IHA, though, must be tailored to fit the particular system being analyzed. Distributed systems, for instance, must be analyzed for hazards in terms of the functions that rely on them. This paper will describe systems-oriented IHA techniques (as opposed to traditional failure-event or reliability techniques) that should be employed for distributed systems in aerospace environments. Special considerations will be addressed when dealing with specific distributed systems such as active thermal control, electrical power, command and data handling, and software systems (including the interaction with fault management systems). Because of the significance of second-order effects in large scale distributed systems, the paper will also describe how to analyze secondary functions to secondary functions through the use of channelization.

Morris, A. Terry↗
NASA NTRS2003

A Power Conversion Concept for the Jupiter Icy Moons Orbiter

The Jupiter Icy Moons Orbiter (JIMO) is a bold new mission under development by the Office of Space Science at NASA Headquarters. ITMO is examining the potential of Nuclear Electric Propulsion (NEP) technology to efficiently deliver scientific payloads to three Jovian moons: Callisto, Ganymede, and Europa. A critical element of the NEP vehicle is the reactor power system, consisting of the nuclear reactor, power conversion, heat rejection, and power management and distribution (PMAD). The emphasis of this paper is on the non-nuclear elements of the reactor power system.

Mason, Lee S.↗
NASA NTRS1984

Distributed data base systems with special emphasis toward POREL

In the last few years a number of research and advanced development projects have resulted in distributed data base management prototypes. POREL, developed at the University of Stuttgart, is a multiuser, distributed, relational system developed for wide and local area networks of minicomputers and advanced micros. The general objectives of such data base systems and the architecture of POREL are discussed. In addition a comparison of some of the the existing distributed DMBS is included to provide the reader with information about the current state of the art.

Neuhold, E. J.↗
NASA NTRS1986

Electrical power system for the U.S. space station

The Space Station Electrical Power System presents many interesting challenges. It will be much larger than previous space power systems, and it must be designed for on-orbit maintenance and replacement, along with having a growth capability. The power generation, energy storage, and power management and distribution (PMAD) subsystems comprise the primary elements of the overall system. Each was analyzed by NASA Lewis Research Center and its two contractors -- Rocketdyne and TRW -- in the definition studies of the program to determine the optimum approach to minimize initial costs and life cycle costs. For the PMAD subsystem, a ring bus architecture operating at 440 V, 20 kHz, single phase, was selected. Photovoltaic and solar dynamic power generation subsystems were both studied. Major tradeoffs were made for each subsystem and for the overall system, and a hybrid system (both photovoltaic and solar dynamic) was selected.

Nored, D. L.↗
NASA NTRS1986

Electrical power system for the U.S. Space Station

The Space Station Electrical Power System presents many interesting challenges. It will be much larger than previous space power systems, and it must be designed for on-orbit maintenance and replacement, along with having a growth capability. The power generation, energy storage, and power management and distribution (PMAD) subsystems comprise the primary elements of the overall system. Each was analyzed by NASA Lewis Research Center and its two contractors Rocketdyne and TRW - in the definition studies of the program to determine the optimum approach to minimize initial costs and life cycle costs. For the PMAD subsystem, a ring bus architecture operating at 440 V, 20 kHz, single phase, was selected. Photovoltaic and solar dynamic power generation subsystems were both studied. Major tradeoffs were made for each subsystem and for the overall system, and a hybrid system (both photovoltaic and solar dynamic) was selected.

Nored, D. L.↗
NASA NTRS1990

Information Security and Integrity Systems

Viewgraphs from the Information Security and Integrity Systems seminar held at the University of Houston-Clear Lake on May 15-16, 1990 are presented. A tutorial on computer security is presented. The goals of this tutorial are the following: to review security requirements imposed by government and by common sense; to examine risk analysis methods to help keep sight of forest while in trees; to discuss the current hot topic of viruses (which will stay hot); to examine network security, now and in the next year to 30 years; to give a brief overview of encryption; to review protection methods in operating systems; to review database security problems; to review the Trusted Computer System Evaluation Criteria (Orange Book); to comment on formal verification methods; to consider new approaches (like intrusion detection and biometrics); to review the old, low tech, and still good solutions; and to give pointers to the literature and to where to get help. Other topics covered include security in software applications and development; risk management; trust: formal methods and associated techniques; secure distributed operating system and verification; trusted Ada; a conceptual model for supporting a B3+ dynamic multilevel security and integrity in the Ada runtime environment; and information intelligence sciences.

Source record↗
NASA NTRSDate not supplied

Advanced eLectrical Bus (ALBus) CubeSat: From Build to Flight

The Advanced eLectrical Bus (ALBus) CubeSat project is a technology demonstration mission of a 3-U CubeSat with an advanced, digitally controlled electrical power system capability and novel use of Shape Memory Alloy (SMA) technology for reliable deployable solar array mechanisms. The objective of the project was to advance the state of power management and distribution (PMAD) capabilities to enable future missions requiring flexible and reliable power systems with higher output power capabilities. The goals of the mission were to demonstrate 100W distribution to a target electrical load, respond to continuous and fast transient power requirements, and show reliable deployment of solar arrays and antennas utilizing re-settable SMA mechanisms. The power distribution function of the ALBus PMAD system is unique in the total power to target load capability. Power is distributed from batteries to provide 100W of power directly to a resistive load. The deployable solar arrays utilize NASA Glenn Research Center’s Nickel-Titanium-Palladium-Platinum high-temperature SMAs for the retention and release mechanism, and a super-elastic binary NiTi alloy for the hinge component. The deployable solar array hinge design features the utilization of SMA material properties for a dual purpose. First, the hinge uses the super-elastic SMA properties to provide the spring force to deploy the arrays. Second, the electrical conductivity properties of the SMA enables the design to provide clean conduits for power transfer from the deployable arrays to the power management system. This eliminates the need for electrical harnesses between the arrays and the PMAD system in the ALBus system design. The uniqueness of the SMA retention and release mechanism design is the ability to reset the mechanism and reuse the same hardware. This allow functional tests of the mechanisms before flight with no degradation of performance and flying the hardware that is tested. The project launched as part of the CubeSat Launch Initiative Educational Launch of Nanosatellites (ELaNa) XIX mission on Rocket Lab’s Electron in December 2018. This paper summarizes the final launched design of ALBus and lessons learned from the technology and overall project from development through flight.

Deboshri Sadhukhan↗
NASA NTRS1986

Space station data management system assessment methodology

A computer-aided modeling tool and methodology was developed and is currently being used to assess candidate designs for the Space Station Data Management System (DMS). The DMS will be a complex distributed computer system including processors, storage devices, local area networks, and software that will support all processing functions on board the Space Station. The methodology produces assessments of the performance, reliability, cost, and physical attributes of the candidate designs. This paper describes the architecture and design of the modeling tool and presents the modeling methodology.

Jones, W. R.↗