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

Medical Data Architecture Project Status

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. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm. The medical system requirements are being developed in parallel with the exploration mission architecture and vehicle design. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products supported by current prototype development will directly inform exploration medical system requirements.

medical data architecture↗
NASA NTRS2018

Medical Data Architecture (MDA) Project Status

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. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm. The medical system requirements are being developed in parallel with the exploration mission architecture and vehicle design. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products supported by current prototype development will directly inform exploration medical system requirements.

medical data architecture↗
NASA NTRS2019

Medical Data Architecture (MDA) Project Status

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. This gap identifies that the current in-flight medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are a variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable a more medically autonomous crew than the current paradigm. The medical system requirements are being developed in parallel with the exploration mission architecture and vehicle design. ExMC has recognized that in order to make informed decisions about a medical data architecture framework, current methods for medical data management must not only be understood, but an architecture must also be identified that provides the crew with actionable insight to medical conditions. This medical data architecture will provide the necessary functionality to address the challenges of executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. Hence, the products supported by current prototype development will directly inform exploration medical system requirements.In fiscal year 2018, the MDA project developed Test Bed 2, the second iteration in a series of prototypes with functionality focused on data security through role-based access control and encryption, integration with One Portal exercise software and ingestion of an ultrasound Digital Imaging and Communications in Medicine (DICOM) file and image display. Test Bed 2 advances the medical data system architecture framework by providing these functionalities in a scalable system that maintained a layered, modular design. The architecture framework uses a data services approach with role-based access to data in a customized medical record system suitable for space exploration. These functionalities were demonstrated as part of the Next Space Technologies for Exploration Partnerships (NextSTEP) ground test demonstrated at the NASA Johnson Space Center Integrated Power, Avionics and Software (iPAS) facility. Interfacing to a Core Flight Software (CFS) system, the MDA system, using Consultative Committee for Space Data Systems (CCSDS) protocol, transferred an exercise file from the simulated flight MDA system to a mirrored MDA system on the ground through the CFS system. The selection of data sources and demonstrations enabled the team to address stakeholder concerns throughout the development process. In the next iteration, the MDA team will work with stakeholders to identify additional relevant functionalities to further advance system data models, standards and principles that will inform the medical system requirements development.

medical data architecture↗
NASA NTRS2009

Space Shuttle Usage of z/OS

This viewgraph presentation gives a detailed description of the avionics associated with the Space Shuttle's data processing system and its usage of z/OS. The contents include: 1) Mission, Products, and Customers; 2) Facility Overview; 3) Shuttle Data Processing System; 4) Languages and Compilers; 5) Application Tools; 6) Shuttle Flight Software Simulator; 7) Software Development and Build Tools; and 8) Fun Facts and Acronyms.

Green, Jan↗
NASA NTRS1991

SEDS1 mission software verification using a signal simulator

The first flight of the Small Expendable Deployer System (SEDS1) is scheduled as the secondary payload of a Delta II in late 1992. The objective of the SEDS1 mission is to collect data to validate the concept of tethered satellite systems and to verify computer simulations used to predict their behavior. A series of tests will be performed to exercise the software modules which make up the Mission Software of the SEDS Data System. These tests will be performed by using a SEDS Signal Simulator to generate signals which will simulate the inputs normally produced by sensors and circuits in the SEDS system. The SEDS Signal Simulator will be used in the debugging and in the formal verification of the SEDS1 Mission Software. The Simulator will not only emulate normal flight conditions but also exercise all modules written to handle anticipated anomalous flight conditions, conditions that would be difficult to reproduce and control with actual SEDS hardware. The simulator will help to expedite software development and to increase the confidence of the users of the Mission Software. With little modification, the Simulator should be useful in the software development of future SEDS flights.

Pierson, William E.↗
NASA NTRSDate not supplied

PTD: Enabling New Space Technologies

Significant advances in the capabilities of small spacecraft over the past 20 years, coupled with improved access to space from a variety of launch platforms have created new opportunities for scientific exploration and commercial application using these high-value (and yet low cost) platforms. Continued development and demonstration of key technologies are improving the performance of the 3U and 6U class CubeSats while expanding the small spacecraft reach into larger platforms, such as 12U and ESPA class missions. The availability and relatively low cost of CubeSat spacecraft allows key technologies to be flight qualified, bridging the TRL 6/7 gap and making truly novel and enabling technologies available to much larger missions in the planning stages at NASA. The key is connecting the technologists with the flight opportunity in a time and cost efficient manner. NASA’s Small Satellite Technology (SST) program is using existing commercial spacecraft to provide a common bus for technology demonstration, taking advantage of their proven platforms and system with proven flight heritage and extensive infrastructure. In this paper we discuss the Pathfinder Technology Demonstrator (PTD) series of four spacecraft and the CubeSat Laser Infrared CrosslinK (CLICK) series of three spacecraft, the approach SST took in facilitating the missions, the successes of those missions as well as lessons learned in the process. NASA’s PTD spacecraft series is demonstrating a variety of new technologies on-orbit, providing proof of the maturity of these significant new technologies, and enhancing the performance of future CubeSats. Each of the four PTD mission consists of one 6-unit (6U) CubeSat weighing approximately 12 kilograms and measuring approximately 30 centimeters x 25 centimeters x 10 centimeters, characterizing its payload within 90 days of orbit insertion. The spacecraft bus, integration and test, and mission operations services are being provided by Terran Orbital. The PTD missions have demonstrated a novel nano-spacecraft compatible propulsion systems (enabling deep space and maneuverable Cubeat missions) and an optical communications system (enabling high data rate collection and communications) already. The CLICK missions are demonstrating compact space-to-space optical communications first with the CLICK A technology demonstrator (already flown) and finally with the CLICK BC dual spacecraft mission. Both projects are part of the SST program within the NASA Space Technology Mission Directorate. SST is chartered to develop and demonstrate technologies to enhance and expand the capabilities of small spacecraft with a particular focus on enabling new mission architectures through the use of small spacecraft, expanding the reach of small spacecraft to new destinations, and augmenting future missions with supporting small spacecraft.

J. Hanson↗
NASA NTRS1991

Earth observing SAR data processing systems at the Jet Propulsion Laboratory - Seasat to EOS SAR

The evolution of SAR digital data processing and management ground systems developed at the JPL for earth science missions is discussed. Attention is given to the SAR ground data system requirements, the early data processing systems, the Seasat SAR system, and the SIR-B data processing system. Special consideration is given to two currently operational SAR data systems: the JPL aircraft SAR processing system that flies on the NASA DC-8 and the Alaska SAR Facility at Fairbanks.

Nichols, David A.↗
NASA NTRSDate not supplied

NASA’s Goddard Space Flight Center’s Distributed Systems Missions Architecture

Space and Earth Science are being transformed by applying a distributed approach to missions, where the fusion of data from components, systems, instruments, models, and observation locations works in concert with timely responses and feedback mechanisms to multiply the knowledge obtained. Additionally, a disaggregated approach allows for a distributed cost and schedule that can be shared across multiple organizations to enable the greater mission. With the advances in reduced size, weight, and power for space-worthy components leading to the revolution in smaller spacecraft, the cost and timeliness proposition for launching multiple space assets has also greatly improved. Thus, the aerospace industry is undergoing a paradigm shift toward a proliferation of small satellites as a networked approach to meet mission objectives. This paper will describe the impetus, goal, and path to provide an openly available framework as a unifying catalyst for broad-ranging Distributed Systems Missions (DSMs) contributors.

Distributed Systems↗
NASA NTRSDate not supplied

NASA’s Goddard Space Flight Center’s Distributed Systems Missions Architecture

Space and Earth Science are being transformed by applying a distributed approach to missions, where the fusion of data from components, systems, instruments, models, and observation locations works in concert with timely responses and feedback mechanisms to multiply the knowledge obtained. Additionally, a disaggregated approach allows for a distributed cost and schedule that can be shared across multiple organizations to enable the greater mission. With the advances in reduced size, weight, and power for space-worthy components leading to the revolution in smaller spacecraft, the cost and timeliness proposition for launching multiple space assets has also greatly improved. Thus, the aerospace industry is undergoing a paradigm shift toward a proliferation of small satellites as a networked approach to meet mission objectives. This paper will describe the impetus, goal, and path to provide an openly available framework as a unifying catalyst for broad-ranging Distributed Systems Missions (DSMs) contributors.

Distributed Systems↗
NASA NTRS1999

Summary Report of Mission Acceleration Measurement for STS-87: Launched November 19, 1997

Two accelerometer systems, the Orbital Acceleration Research Experiment and the Space Acceleration Measurement System, were used to measure and record the microgravity environment of the Orbiter Columbia during the STS-87 mission in November-December 1997. Data from two separate Space Acceleration Measurement System units were telemetered to the ground during the mission and data plots were displayed for investigators of the Fourth United States Microgravity Payload experiments in near real-time using the World Wide Web. Plots generated using Orbital Acceleration Research Experiment data (telemetered to the ground using a tape delay) were provided to the investigators using the World Wide Web approximately twelve hours after data recording. Disturbances in the microgravity environment as recorded by these instruments are grouped by source type: Orbiter systems, on-board activities, payload operations, and unknown sources. The environment related to the Ku-band antenna dither, Orbiter structural modes, attitude deadband collapses, water dump operations, crew sleep, and crew exercise was comparable to the effects of these sources on previous Orbiter missions. Disturbances related to operations of the Isothermal Dendritic Growth Experiment and Space Acceleration Measurement Systems that were not observed on previous missions are detailed. The effects of Orbiter cabin and airlock depressurization and extravehicular activities are also reported for the first time. A set of data plots representing the entire mission is included in the CD-ROM version of this report.

Rogers, Melissa J. B.↗
NASA NTRS1999

Summary Report of Mission Acceleration Measurement for STS-87, Launched November 19, 1997

Two accelerometer systems, the Orbital Acceleration Research Experiment and the Space Acceleration Measurement System, were used to measure and record the microgravity environment of the Orbiter Columbia during the STS-87 mission in November-December 1997. Data from two separate Space Acceleration Measurement System units were telemetered to the ground during the mission and data plots were displayed for investigators of the Fourth United States Microgravity Payload experiments in near real-time using the World Wide Web. Plots generated using Orbital Acceleration Research Experiment data (telemetered to the ground using a tape delay) were provided to the investigators using the World Wide Web approximately twelve hours after data recording. Disturbances in the microgravity environment as recorded by these instruments are grouped by source type: Orbiter systems, on-board activities, payload operations, and unknown sources. The environment related to the Ku-band antenna dither, Orbiter structural modes, attitude deadband collapses, water dump operations, crew sleep, and crew exercise was comparable to the effects of these sources on previous Orbiter missions. Disturbances related to operations of the Isothermal Dendritic Growth Experiment and Space Acceleration Measurement Systems that were not observed on previous missions are detailed. The effects of Orbiter cabin and airlock depressurization and extravehicular activities are also reported for the first time. A set of data plots representing the entire mission is included in the CD-ROM version of this report.

Rogers, Melissa J. B.↗
NASA NTRS1994

The NASA Mission Operations and Control Architecture Program

The conflict between increases in space mission complexity and rapidly declining space mission budgets has created strong pressures to radically reduce the costs of designing and operating spacecraft. A key approach to achieving such reductions is through reducing the development and operations costs of the supporting mission operations systems. One of the efforts which the Communications and Data Systems Division at NASA Headquarters is using to meet this challenge is the Mission Operations Control Architecture (MOCA) project. Technical direction of this effort has been delegated to the Mission Operations Division (MOD) of the Goddard Space Flight Center (GSFC). MOCA is to develop a mission control and data acquisition architecture, and supporting standards, to guide the development of future spacecraft and mission control facilities at GSFC. The architecture will reduce the need for around-the-clock operations staffing, obtain a high level of reuse of flight and ground software elements from mission to mission, and increase overall system flexibility by enabling the migration of appropriate functions from the ground to the spacecraft. The end results are to be an established way of designing the spacecraft-ground system interface for GSFC's in-house developed spacecraft, and a specification of the end to end spacecraft control process, including data structures, interfaces, and protocols, suitable for inclusion in solicitation documents for future flight spacecraft. A flight software kernel may be developed and maintained in a condition that it can be offered as Government Furnished Equipment in solicitations. This paper describes the MOCA project, its current status, and the results to date.

Ondrus, Paul J.↗
NASA NTRS1989

Validation of satellite solar occultation measurements 1975-1988

The Stratospheric Aerosol and Gas Experiment (SAGE II) is discussed. SAGE II was launched from the Space Shuttle in October, 1984 as part of the Earth Radiation Budget satellite and uses the solar occultation technique to measure the extinction of solar radiation caused by the earth's atmosphere. The solar radiance data are compared with data from ground-based systems, airborne missions, balloonborne in situ measurements, ancillary measurements, and other satellite systems. The SAGE II instrument, data processing methods, and correlative measurements program are examined.

Maddrea, G. L., Jr.↗
NASA NTRS1989

Ground data systems resource allocation process

The Ground Data Systems Resource Allocation Process at the Jet Propulsion Laboratory provides medium- and long-range planning for the use of Deep Space Network and Mission Control and Computing Center resources in support of NASA's deep space missions and Earth-based science. Resources consist of radio antenna complexes and associated data processing and control computer networks. A semi-automated system was developed that allows operations personnel to interactively generate, edit, and revise allocation plans spanning periods of up to ten years (as opposed to only two or three weeks under the manual system) based on the relative merit of mission events. It also enhances scientific data return. A software system known as the Resource Allocation and Planning Helper (RALPH) merges the conventional methods of operations research, rule-based knowledge engineering, and advanced data base structures. RALPH employs a generic, highly modular architecture capable of solving a wide variety of scheduling and resource sequencing problems. The rule-based RALPH system has saved significant labor in resource allocation. Its successful use affirms the importance of establishing and applying event priorities based on scientific merit, and the benefit of continuity in planning provided by knowledge-based engineering. The RALPH system exhibits a strong potential for minimizing development cycles of resource and payload planning systems throughout NASA and the private sector.

Berner, Carol A.↗