Search NASA⌕ Search

SEARCH · Search NASA

Results for “Mission Data 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 253 records · Page 14
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

NASA Development of Hardware for Life Support Systems in Cis Lunar and Surface Habitats

Sustained human presence requires the ability to survive with a minimal Earth supply chain and minimal communications from Earth. NASA is working on mission platforms to aggregate ECLS functions into a cis lunar and lunar surface architectures to demonstrate Mars forward capabilities and reduce the risk for human missions to Mars. This means the Environmental Control and Life Support (ECLS) technologies in the vehicle architecture will need to recover air and water from human and consumable waste products to support humans for short and long duration missions. NASA is developing ECLS technologies for Air Revitalization, Water Recovery and Management, Waste Management and Environmental Monitoring. Implementation of these technologies on microgravity and partial gravity platforms will collect component and system data on manned missions to increase the reliability needed for mission beyond Low Earth Orbit.

Imelda C. Stambaugh↗
NASA NTRS1976

Distributed microprocessors for spacecraft control and data handling

The Unified Data System (UDS) group at JPL is attempting to reduce total mission costs by designing a spacecraft data system which takes advantage of the natural and historical partitioning of a spacecraft into subsystems. Each subsystem is assigned a microprocessor which needs just enough capability to control the sensors and actuators of that subsystem, collect its data and maintain time synchronization with the rest of the spacecraft. The resulting distributed system avoids many of the overhead costs of a single centralized multi-processing system. To minimize complexity and therefore minimize total mission costs, a variety of standards and restrictions are imposed on the design of hardware, software, and communications. Articulation of these standards and restrictions is a major benefit deriving from the UDS program.

Lesh, F.↗
NASA NTRS2000

Autonomous Agents and Intelligent Assistants for Exploration Operations

Human exploration of space will involve remote autonomous crew and systems in long missions. Data to earth will be delayed and limited. Earth control centers will not receive continuous real-time telemetry data, and there will be communication round trips of up to one hour. There will be reduced human monitoring on the planet and earth. When crews are present on the planet, they will be occupied with other activities, and system management will be a low priority task. Earth control centers will use multi-tasking "night shift" and on-call specialists. A new project at Johnson Space Center is developing software to support teamwork between distributed human and software agents in future interplanetary work environments. The Engineering and Mission Operations Directorates at Johnson Space Center (JSC) are combining laboratories and expertise to carry out this project, by establishing a testbed for hWl1an centered design, development and evaluation of intelligent autonomous and assistant systems. Intelligent autonomous systems for managing systems on planetary bases will commuicate their knowledge to support distributed multi-agent mixed-initiative operations. Intelligent assistant agents will respond to events by developing briefings and responses according to instructions from human agents on earth and in space.

Malin, Jane T.↗
NASA NTRS1972

Guidance system operations plan for manned LM earth orbital and lunar missions using program luminary 1E. Section 2: Data links

Data links for the guidance system of manned lunar module orbital and lunar missions are presented. Subjects discussed are: (1) digital uplink to lunar module, (2) lunar module liftoff time increment, (3) lunar module contiguous block update, (4) lunar module scatter update, (5) lunar module digital downlink, and (6) absolute addresses for update program.

Hamilton, M. H.↗
NASA NTRS2012

Using Quality Attributes to Bridge Systems Engineering Gaps : A Juno Ground Data Systems Case Study

The Juno Mission to Jupiter is the second mission selected by the NASA New Frontiers Program. Juno launched August 2011 and will reach Jupiter July 2016. Juno's payload system is composed of nine instruments plus a gravity science experiment. One of the primary functions of the Juno Ground Data System (GDS) is the assembly and distribution of the CFDP (CCSDS File Delivery Protocol) product telemetry, also referred to as raw science data, for eight out of the nine instruments. The GDS accomplishes this with the Instrument Data Pipeline (IDP). During payload integration, the first attempt to exercise the IDP in a flight like manner revealed that although the functional requirements were well understood, the system was unable to meet latency requirements with the as-is heritage design. A systems engineering gap emerged between Juno instrument data delivery requirements and the assumptions behind the heritage flight-ground interactions. This paper describes the use of quality attributes to measure and overcome this gap by introducing a new systems engineering activity, and a new monitoring service architecture that successfully delivered the performance metrics needed to validate Juno IDP.

Ground Data Systems (GDS)↗
NASA NTRS1996

Aeronautics and Space Report of the President: Fiscal Year 1996 Activities

Topics considered include: (1) Space launch activities: space shuttle missions; expendable launch vehicles. (2) Space science: astronomy and space physics; solar system exploration. (3) Space flight and technology: life and microgravity sciences; space shuttle technology; reuseable launch vehicles; international space station; energy; safety and mission assurance; commercial development and regulation of space; surveillance. (4) Space communications: communications satellites; space network; ground networks; mission control and data systems. (5) Aeronautical activities: technology developments; air traffic control and navigation; weather-related aeronautical activities; flight safety and security; aviation medicine and human factors. (6) Studies of the planet earth: terrestrial studies and applications: atmospheric studies: oceanographic studies; international aeronautical and space activities; and appendices.

Source record↗
NASA NTRS1974

Flight operations and performance of Skylab life support and environmental control systems

The design and performance of the Skylab thermal and environmental control systems is considered. The Orbital Workshop had a combined active and passive thermal control system. The refrigeration system was designed to store food and biomedical samples and to cool drinking water. The atmosphere control system included active humidity control, molecular sieves and charcoal canisters to control carbon dioxide, odor, and contaminants, and the gas supply system. Mission support preparation, including instrumentation, ground data system, system troubleshooting, and training, is surveyed. Major in-flight anomalies occurred with the thermal control system when the meteoroid shield was lost during SL-1 ascent and when the Airlock Module coolant loop malfunctioned during SL-2 manned operations. The atmosphere control system performed without major anomaly throughout the manned missions.

Hopson, G. D.↗
NASA NTRS1993

Making tomorrow's mistakes today: Evolutionary prototyping for risk reduction and shorter development time

In the early days of JPL's solar system exploration, each spacecraft mission required its own dedicated data system with all software applications written in the mainframe's native assembly language. Although these early telemetry processing systems were a triumph of engineering in their day, since that time the computer industry has advanced to the point where it is now advantageous to replace these systems with more modern technology. The Space Flight Operations Center (SFOC) Prototype group was established in 1985 as a workstation and software laboratory. The charter of the lab was to determine if it was possible to construct a multimission telemetry processing system using commercial, off-the-shelf computers that communicated via networks. The staff of the lab mirrored that of a typical skunk works operation -- a small, multi-disciplinary team with a great deal of autonomy that could get complex tasks done quickly. In an effort to determine which approaches would be useful, the prototype group experimented with all types of operating systems, inter-process communication mechanisms, network protocols, packet size parameters. Out of that pioneering work came the confidence that a multi-mission telemetry processing system could be built using high-level languages running in a heterogeneous, networked workstation environment. Experience revealed that the operating systems on all nodes should be similar (i.e., all VMS or all PC-DOS or all UNIX), and that a unique Data Transport Subsystem tool needed to be built to address the incompatibilities of network standards, byte ordering, and socket buffering. The advantages of building a telemetry processing system based on emerging industry standards were numerous: by employing these standards, we would no longer be locked into a single vendor. When new technology came to market which offered ten times the performance at one eighth the cost, it would be possible to attach the new machine to the network, re-compile the application code, and run. In addition, we would no longer be plagued with lack of manufacturer support when we encountered obscure bugs. And maybe, hopefully, the eternal elusive goal of software portability across different vendors' platforms would finally be available. Some highlights of our prototyping efforts are described.

Friedman, Gary↗
NASA NTRS2018

Optical Relay for Future NASA Geosynchronous Orbiting Satellite for High Data Rate Links to NASA User Missions

NASA is exploring options for its Next Generation Relay (NGR) architecture while the current Tracking Data Relay Satellite System (TDRSS) completes its mission. The plan is to start implementation of the NGR beginning around 2025. The new system of proposed relay satellites will greatly increase the data rates between low Earth orbiting (LEO) satellite missions and the NASA TDRSS relay satellites. This increase in data rates will allow an unprecedented increase in data throughput from the LEO satellite missions back to the principal investigators (PI). This can be accomplished at Ka-band frequencies with high order modulation or at optical frequencies using Differential Phase Shift Keying (DPSK). The first satellite in the next set of relay satellites will have to be backward compatible with current technology to support ongoing and planned missions. The new set of satellites will be launched over a 10-year period with design lifetimes of at least 15 years. To meet these requirements, we analyzed various architectures and designed both the communication payloads on the relay satellite and candidate payloads on the user spacecraft by utilizing optical heads already designed. From this analysis, a demonstration optical satellite named “the Next Generation Optical Relay Pathfinder” with Ka-band capabilities was proposed to be built and launched with the purpose of evaluating an integrated high-speed optical and Ka-band communication system. Given a cost limit for the demonstration satellite, various satellite configurations were developed by varying the number of optical communication payloads. The communication payload on the relay satellite consisted of three major sub-systems: 1) Optical communication payload, 2) Ka-band communication payload, 3) Digital processing and routing of signals. The size, mass (weight), and power (SWaP) of the communication payload and other sub-systems of the satellite were obtained. The NASA Glenn Research Center COMPASS team designed the Pathfinder satellite and performed a cost analysis for its build and launch. In this paper, we first describe the needs, drivers, and the associated challenges for the Next Generation Optical Relay Pathfinder to be capable of connecting multiple LEO and GEO satellites at high data rates. Second, we detail the concept of operations (ConOps) and the system architecture, including the satellite configurations considered, their attributes and limitations, and the size of the satellite needed for each configuration. Third, we provide a summary of the Next Generation Optical Relay Pathfinder satellite design trades and its key elements. Finally, we present the path needed for implementation and operations.

Warner, Joseph H. D.↗
NASA NTRS1994

Customizing the JPL Multimission Ground Data System: Lessons Learned

This paper will describe lessons learned in adapting JPL's Multimission Ground Data System (MGDS) to fly the Voyager, Galileo, and Mars Observer missions. We will explain how powerful, existing ground data systems can be adapted and packaged in a cost effective way for operations of small and large planetary missions. We will also describe how the MGDS was adapted to support operations within the Galileo Spacecraft Testbed. The Galileo testbed provided a unique opportunity to adapt MGDS to support command and control operations for a small autonomous operations team with a handful of engineers flying the Galileo Spacecraft flight system model.

ground↗
NASA NTRS1991

Silvabase: A flexible data file management system

The need for a more flexible and efficient data file management system for mission planning in the Mission Operations Laboratory (EO) at MSFC has spawned the development of Silvabase. Silvabase is a new data file structure based on a B+ tree data structure. This data organization allows for efficient forward and backward sequential reads, random searches, and appends to existing data. It also provides random insertions and deletions with reasonable efficiency, utilization of storage space well but not at the expense of speed, and performance of these functions on a large volume of data. Mission planners required that some data be keyed and manipulated in ways not found in a commercial product. Mission planning software is currently being converted to use Silvabase in the Spacelab and Space Station Mission Planning Systems. Silvabase runs on a Digital Equipment Corporation's popular VAX/VMS computers in VAX Fortran. Silvabase has unique features involving time histories and intervals such as in operations research. Because of its flexibility and unique capabilities, Silvabase could be used in almost any government or commercial application that requires efficient reads, searches, and appends in medium to large amounts of almost any kind of data.

Lambing, Steven J.↗
NASA NTRS1984

Interference problems for nongeostationary satellites

The interference problems faced by nongeostationary satellites may be of major significance. A general discussion indicates the scope of the problems and describes several configurations of importance. Computer programs are described, which are employed by NASA/JPL and the U.S. Air Force Satellite Control Facility to provide interference-free scheduling of commands and data transmission. Satellite system mission planners are not concerned with the precise prediction of interference episodes, but rather with the expected total amount of interference, the mean and maximum duration of events, and the mean spacing between episodes. The procedures in the theory of probability developed by the author which permit calculation of such quantities are described and applied to several real cases. It may be anticipated that the problems will become steadily worse in the future as more and more data transmissions attempt to occupy the same frequency band.

Sollfrey, W.↗
NASA NTRS2017

Security Vulnerability Profiles of Mission Critical Software: Empirical Analysis of Security Related Bug Reports

While some prior research work exists on characteristics of software faults (i.e., bugs) and failures, very little work has been published on analysis of software applications vulnerabilities. This paper aims to contribute towards filling that gap by presenting an empirical investigation of application vulnerabilities. The results are based on data extracted from issue tracking systems of two NASA missions. These data were organized in three datasets: Ground mission IVV issues, Flight mission IVV issues, and Flight mission Developers issues. In each dataset, we identified security related software bugs and classified them in specific vulnerability classes. Then, we created the security vulnerability profiles, i.e., determined where and when the security vulnerabilities were introduced and what were the dominating vulnerabilities classes. Our main findings include: (1) In IVV issues datasets the majority of vulnerabilities were code related and were introduced in the Implementation phase. (2) For all datasets, around 90 of the vulnerabilities were located in two to four subsystems. (3) Out of 21 primary classes, five dominated: Exception Management, Memory Access, Other, Risky Values, and Unused Entities. Together, they contributed from 80 to 90 of vulnerabilities in each dataset.

Goseva-Popstojanova, Katerina↗
NASA NTRS1992

Architectures for mission control at the Jet Propulsion Laboratory

JPL is currently converting to an innovative control center data system which is a distributed, open architecture for telemetry delivery and which is enabling advancement towards improved automation and operability, as well as new technology, in mission operations at JPL. The scope of mission control within mission operations is examined. The concepts of a mission control center and how operability can affect the design of a control center data system are discussed. Examples of JPL's mission control architecture, data system development, and prototype efforts at the JPL Operations Engineering Laboratory are provided. Strategies for the future of mission control architectures are outlined.

Davidson, Reger A.↗
NASA NTRS1990

The 1990 Reference Handbook: Earth Observing System

An overview of the Earth Observing System (EOS) including goals and requirements is given. Its role in the U.S. Global Change Research Program and the International--Biosphere Program is addressed. The EOS mission requirements, science, fellowship program, data and information systems architecture, data policy, space measurement, and mission elements are presented along with the management of EOS. Descriptions of the facility instruments, instrument investigations, and interdisciplinary investigations are also present. The role of the National Oceanic and Atmospheric Administration in the mission is mentioned.

Source record↗