SEARCH · Search NASA

Results for “Distribution Operations”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 73 records · Page 4

All sources NASA NTRS DOE OSTI

NASA NTRS1989

Mars Observer Mission Operations

Mars Observer, planned for launch in September 1992, will be the first deep space planetary mission to fully utilize a distributed operations concept for science instrument control. In addition, several of the other concepts proposed by the Mission Operations and Information Systems Subcommittee of the Solar System Exploration Committee have been adopted for the purpose of improving the efficiency and reducing the costs of Deep Space Mission Operations.

Mckinley, Edward L.↗

NASA NTRS2015

Effectiveness of Advanced Collaboration Tools on Crew Communication in Reduced Crew Operations

The present research examines operational performance and verbal communication in airline flight crews under reduced crew operations (RCO). Eighteen two-pilot crews flew six scenarios under three conditions; one condition involved current-day operations while two involved RCO. In RCO flights, the Captain initially operated the simulated aircraft alone but could request remote crewmember support as off-nominal events occurred and workload was expected to increase. In one of the two RCO conditions, crewmembers were provided with advanced prototype collaboration tools designed to alleviate difficulties in crew coordination. Crews successfully solved all challenging events without accident and analyses of operational performance did not reveal any differences among the three conditions. In RCO flights, crew communication increased when tools were available relative to flights in which they were not; specifically, there were more acknowledgements and decision-making communications. These results suggest the collaboration tools enable higher degrees of crewmember awareness andor coordination during distributed operations.

crew resource management↗

NASA NTRS1986

Independent Orbiter Assessment (IOA): Analysis of the instrumentation subsystem

The results of the Independent Orbiter Assessment (IOA) of the Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) are presented. The IOA approach features a top-down analysis of the hardware to determine failure modes, criticality, and potential critical items. To preserve independence, this analysis was accomplished without reliance upon the results contained within the NASA FMEA/CIL documentation. The independent analysis results for the Instrumentation Subsystem are documented. The Instrumentation Subsystem (SS) consists of transducers, signal conditioning equipment, pulse code modulation (PCM) encoding equipment, tape recorders, frequency division multiplexers, and timing equipment. For this analysis, the SS is broken into two major groupings: Operational Instrumentation (OI) equipment and Modular Auxiliary Data System (MADS) equipment. The OI equipment is required to acquire, condition, scale, digitize, interleave/multiplex, format, and distribute operational Orbiter and payload data and voice for display, recording, telemetry, and checkout. It also must provide accurate timing for time critical functions for crew and payload specialist use. The MADS provides additional instrumentation to measure and record selected pressure, temperature, strain, vibration, and event data for post-flight playback and analysis. MADS data is used to assess vehicle responses to the flight environment and to permit correlation of such data from flight to flight. The IOA analysis utilized available SS hardware drawings and schematics for identifying hardware assemblies and components and their interfaces. Criticality for each item was assigned on the basis of the worst-case effect of the failure modes identified.

Howard, B. S.↗

NASA NTRS1992

The changing nature of spacecraft operations: From the Vikings of the 1970's to the great observatories of the 1990's and beyond

Four trends in spacecraft flight operations are discussed which will reduce overall program costs. These trends are the use of high-speed, highly reliable data communications systems for distributing operations functions to more convenient and cost-effective sites; the improved capability for remote operation of sensors; a continued rapid increase in memory and processing speed of flight qualified computer chips; and increasingly capable ground-based hardware and software systems, notably those augmented by artificial intelligence functions. Changes reflected by these trends are reviewed starting from the NASA Viking missions of the early 70s, when mission control was conducted at one location using expensive and cumbersome mainframe computers and communications equipment. In the 1980s, powerful desktop computers and modems enabled the Magellan project team to operate the spacecraft remotely. In the 1990s, the Hubble Space Telescope project uses multiple color screens and automated sequencing software on small computers. Given a projection of current capabilities, future control centers will be even more cost-effective.

Ledbetter, Kenneth W.↗

NASA NTRS1974

Modal Interfaces in Hawaii

Hawaii, an archipelago where transportation distances are short but the interfaces are many, seeks elimination of modal changes by totally-submerged hydrofoil craft operating at the water surface directly between tourist resort destinations, by dual mode rapid transit vehicles operating directly between the deplaning bridges at Honolulu International Airport and hotel porte-cochere at Waikiki, by demand responsive vehicles for collection and distribution operating on fixed guideways for line haul, and by roll-on/roll-off inter-island ferries for all models of manually operated ground vehicles. The paper also describes facilitation of unavoidable interfaces by innovative sub-systems.

Wright, E. Alvey↗

NASA NTRS2006

Built But Not Used, Needed But Not Built: Ground System Guidance Based On Cassini-Huygens Experience

These reflections share insight gleaned from Cassini-Huygens experience in supporting uplink operations tasks with software. Of particular interest are developed applications that were not widely adopted and tasks for which the appropriate application was not planned. After several years of operations, tasks are better understood providing a clearer picture of the mapping of requirements to applications. The impact on system design of the changing user profile due to distributed operations and greater participation of scientists in operations is also explored. Suggestions are made for improving the architecture, requirements, and design of future systems for uplink operations.

telecommunications↗

NASA NTRS2006

Built But Not Used, Needed But Not Built: Ground System Guidance Based On Cassini-Huygens Experience

telecommunications↗

NASA NTRS2000

The MAP Autonomous Mission Control System

The Microwave Anisotropy Probe (MAP) mission is the second mission in NASA's Office of Space Science low-cost, Medium-class Explorers (MIDEX) program. The Explorers Program is designed to accomplish frequent, low cost, high quality space science investigations utilizing innovative, streamlined, efficient management, design and operations approaches. The MAP spacecraft will produce an accurate full-sky map of the cosmic microwave background temperature fluctuations with high sensitivity and angular resolution. The MAP spacecraft is planned for launch in early 2001, and will be staffed by only single-shift operations. During the rest of the time the spacecraft must be operated autonomously, with personnel available only on an on-call basis. Four (4) innovations will work cooperatively to enable a significant reduction in operations costs for the MAP spacecraft. First, the use of a common ground system for Spacecraft Integration and Test (I&T) as well as Operations. Second, the use of Finite State Modeling for intelligent autonomy. Third, the integration of a graphical planning engine to drive the autonomous systems without an intermediate manual step. And fourth, the ability for distributed operations via Web and pager access.

Breed, Juile↗

NASA NTRS1991

Space Station Freedom electric power system evolution analysis status

The ability is examined of the SSF baselined EPS to transition to operate at a greater system capacity beyond the SSF Permanent Manned Capability PMC) milestone. Specifically, a status of a current analysis is discussed concerning additions, modifications, changeout, or combination thereof of baseline EPS hardware and/or software needed to accomplish the power generation, distribution, operation, and use needed to meet evolving SSF mission objectives. This discussion results in several EPS architectural options that facilitate the addition or substitution of new technologies.

Zernic, Michael J.↗

NASA NTRS2013

Service Oriented Robotic Architecture for Space Robotics: Design, Testing, and Lessons Learned

This paper presents the lessons learned from six years of experiments with planetary rover prototypes running the Service Oriented Robotic Architecture (SORA) developed by the Intelligent Robotics Group (IRG) at the NASA Ames Research Center. SORA relies on proven software engineering methods and technologies applied to space robotics. Based on a Service Oriented Architecture and robust middleware, SORA encompasses on-board robot control and a full suite of software tools necessary for remotely operated exploration missions. SORA has been eld tested in numerous scenarios of robotic lunar and planetary exploration. The experiments conducted by IRG with SORA exercise a large set of the constraints encountered in space applications: remote robotic assets, ight relevant science instruments, distributed operations, high network latencies and unreliable or intermittent communication links. In this paper, we present the results of these eld tests in regard to the developed architecture, and discuss its bene ts and limitations.

service oriented architecture↗

NASA NTRS1980

Systems architecture for distributed applications

This paper describes the kernel of a distributed operating system called ADAPT. The system runs on top of existing single host operating systems that are networked together. It's purpose is to transform this network of individual systems into a single system that will be easier for application programmers to use. This single system need not be monolithic; ADAPT facilitates the construction of both integrated and modular distributed systems.

Peebles, R.↗

NASA NTRS1986

Notes on a storage manager for the Clouds kernel

The Clouds project is research directed towards producing a reliable distributed computing system. The initial goal is to produce a kernel which provides a reliable environment with which a distributed operating system can be built. The Clouds kernal consists of a set of replicated subkernels, each of which runs on a machine in the Clouds system. Each subkernel is responsible for the management of resources on its machine; the subkernal components communicate to provide the cooperation necessary to meld the various machines into one kernel. The implementation of a kernel-level storage manager that supports reliability is documented. The storage manager is a part of each subkernel and maintains the secondary storage residing at each machine in the distributed system. In addition to providing the usual data transfer services, the storage manager ensures that data being stored survives machine and system crashes, and that the secondary storage of a failed machine is recovered (made consistent) automatically when the machine is restarted. Since the storage manager is part of the Clouds kernel, efficiency of operation is also a concern.

Pitts, David V.↗

NASA NTRS2019

Integrated Analysis of Multiple User Metrics - A “Sequel”; and Introducing the Google Analytic

For decades, the Goddard Earth Sciences Data and Information Services Center (GES DISC) has archived and distributed enormous volumes of NASA Earth science data (accompanied with many developed tools and services) to various research/applications communities and the general public. Being “immersed” in the Big Data era, we have inevitably faced the challenges of our continually increasing archived data in both volume and variety, as well as enhanced user needs and demands. In recent years, we have actively analyzed different types of user metrics, such as operational distribution metrics (recording numbers of distinct users and downloaded data files, size of distributed data volume): user publication metrics (mining info from our Giovanni users’ publications): and Bugzilla metrics (collecting info from user questions or feedback from user assistance tickets). Such metrics have helped us achieve a better understanding of user needs, demands, characteristics, and behaviors, which has then helped us improve our user services. Now we will present a “Sequel” of integrated analysis of multiple metrics at the GES DISC by introducing and adding one new kind of metrics acquired via utilizing our recently implemented Google Analytic 360 suite. Several “newer” reports, e.g., “What web site features and links are the most popular (and least)?” and “What are the top 25 dataset Keyword searches?” retrieved from this new metrics set will be presented, along with the aforementioned “traditional” metrics results.

Shie, Chung-Lin↗

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 NTRS1976

Shape optimization of disc-type flywheels

Techniques were developed for presenting an analytical and graphical means for selecting an optimum flywheel system design, based on system requirements, geometric constraints, and weight limitations. The techniques for creating an analytical solution are formulated from energy and structural principals. The resulting flywheel design relates stress and strain pattern distribution, operating speeds, geometry, and specific energy levels. The design techniques incorporate the lowest stressed flywheel for any particular application and achieve the highest specific energy per unit flywheel weight possible. Stress and strain contour mapping and sectional profile plotting reflect the results of the structural behavior manifested under rotating conditions. This approach toward flywheel design is applicable to any metal flywheel, and permits the selection of the flywheel design to be based solely on the criteria of the system requirements that must be met, those that must be optimized, and those system parameters that may be permitted to vary.

Nizza, R. S.↗

NASA NTRS1984

Requirements for migration of NSSD code systems from LTSS to NLTSS

The purpose of this document is to address the requirements necessary for a successful conversion of the Nuclear Design (ND) application code systems to the NLTSS environment. The ND application code system community can be characterized as large-scale scientific computation carried out on supercomputers. NLTSS is a distributed operating system being developed at LLNL to replace the LTSS system currently in use. The implications of change are examined including a description of the computational environment and users in ND. The discussion then turns to requirements, first in a general way, followed by specific requirements, including a proposal for managing the transition.

Pratt, M.↗

NASA NTRS1985

Space station data system analysis/architecture study. Task 3: Trade studies, DR-5, volume 1

The primary objective of Task 3 is to provide additional analysis and insight necessary to support key design/programmatic decision for options quantification and selection for system definition. This includes: (1) the identification of key trade study topics; (2) the definition of a trade study procedure for each topic (issues to be resolved, key inputs, criteria/weighting, methodology); (3) conduct tradeoff and sensitivity analysis; and (4) the review/verification of results within the context of evolving system design and definition. The trade study topics addressed in this volume include space autonomy and function automation, software transportability, system network topology, communications standardization, onboard local area networking, distributed operating system, software configuration management, and the software development environment facility.

Source record↗

NASA NTRS1985

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

The primary objective of Task 2 is the development of an information base that will support the conduct of trade studies and provide sufficient data to make key design/programmatic decisions. This includes: (1) the establishment of option categories that are most likely to influence Space Station Data System (SSDS) definition; (2) the identification of preferred options in each category; and (3) the characterization of these options with respect to performance attributes, constraints, cost and risk. This volume contains the options development for the design category. This category comprises alternative structures, configurations and techniques that can be used to develop designs that are responsive to the SSDS requirements. The specific areas discussed are software, including data base management and distributed operating systems; system architecture, including fault tolerance and system growth/automation/autonomy and system interfaces; time management; and system security/privacy. Also discussed are space communications and local area networking.

Source record↗