SEARCH · Engineering Papers

Results for “data services”

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 217 records · Page 12

All sources NASA NTRS DOE OSTI

NASA NTRS1999

The Wallops Flight Facility Model for an Integrated Federal/Commercial Launch Range

Historically, the federal government has been the predominant purchaser of space launches in the United States. The government met its needs through purchase of hardware and services. It also provided the infrastructure necessary to conduct launch operations through federal launch ranges, both military and NASA. Under this model, the government had the complete ownership, responsibility, liability, and expense for launch activities. As the commercial space sector grew, there emerged a corresponding growth in demand for launch range services. However, the expense and complexity of activities has thus far deterred a rapid rise in the establishment of purely commercial launch sites. In this context, purely commercial is defined as "without benefit of capabilities provided by the federal government." Consistent with the Commercial Space Launch Act, in recent years NASA and the Air Force have supported commercial launches from government launch ranges on a cost-reimbursable, non-interference basis. In this mode the commercial launch service providers contract with the government to provide services including use of facilities, tracking and data services, and range safety. As the commercial market projections began to show significant opportunities for economic development, several states established spaceports to provide the services necessary to meet these projected commercial needs. In 1997, NASA agreed to the establishment of the Virginia Space Flight Center (VSFC) at the Wallops Flight Facility. Under this arrangement, NASA agreed to allow Virginia Commercial Space Flight Authority (VCSFA) to construct facilities on NASA property and agreed to provide services in accordance with the Space Act of 1958 and the Commercial Space Launch Act of 1984 (as amended) to support VSFC launch customers. The relationship between NASA and VCSFA, however, has evolved beyond a customer supplier relationship. A partnership relationship has emerged which pairs the strengths of the established NASA test range and the state-sponsored, commercial launch facility provider, in an attempt to satisfy the needs for flexible, low-cost access to space. Furthermore, the future of the NASA/Wallops Test Range is closely linked with the success of VCSFA in promoting commercial launches from Wallops. This paper will describe the changing paradigm of the federal launch range and the unique aspects of the NASA/Wallops Facility relationship with VCSFA. Discussion will include institutional cost-sharing, business development and marketing, joint educational programs, and strategic planning.

Underwood, Bruce E.↗

NASA NTRS2020

Introduction to UTM Services & Communication

This presentation provides an overview of NASA's UAS traffic management (UTM) system, defines key concepts, and gives a brief recap of the research done thus far. The UTM system is comprised of four key concepts: UAS Service Suppler (USS), USS Network, UAS Supplemental Data Service Suppliers (SDSP), and the Flight Information Management System (FIMS). Walking through an example UTM operation illustrates the basic contribution of and relationship between each of these components. While this is what a future operation could look like, today we have only started down the road. NASA, and particularly NASA Ames, has spent the last four years on UTM research, of which helped inform both regulation and industry.

Claudatos, Lauren↗

NASA NTRS2019

NASA Global Satellite and Model Data Products and Services for Tropical Cyclone Research

The lack of observations over vast tropical oceans is a major challenge for tropical cyclone research. Satellite observations and model reanalysis data play an important role in filling these- gaps. Established in the mid-1980's, the Goddard Earth Sciences Data and Information Services Center (GES DISC), as one of the 12 NASA data centers, archives and distributes data from several Earth science disciplines such as precipitation, atmospheric dynamics, atmospheric composition, hydrology, including well-known NASA satellite missions (e.g. TRMM, GPM) and model assimilation projects (MERRA-2). Acquiring datasets suitable for tropical cyclone research in a large data archive is a challenge for many, especially for those who are not familiar with satellite or model data. Over the years, the GES DISC has developed user-friendly data services. For example, Giovanni is an online visualization and analysis tool, allowing users to visualize and analyze over 2000 satellite- and model-based variables with a Web browser, without downloading data and software. In this chapter, we will describe data and services at the GES DISC with emphasis on tropical cyclone research. We will also present two case studies and discuss future plans.

Liu, Zhong↗

NASA NTRS2005

Towards the Development of a Unified Distributed Date System for L1 Spacecraft

The purpose of this grant, 'Towards the Development of a Unified Distributed Data System for L1 Spacecraft', is to take the initial steps towards the development of a data distribution mechanism for making in-situ measurements more easily accessible to the scientific community. Our obligations as subcontractors to this grant are to add our Faraday Cup plasma data to this initial study and to contribute to the design of a general data distribution system. The year 1 objectives of the overall project as stated in the GSFC proposal are: 1) Both the rsync and Perl based data exchange tools will be fully developed and tested in our mixed, Unix, VMS, Windows and Mac OS X data service environment. Based on the performance comparisons, one will be selected and fully deployed. Continuous data exchange between all L1 solar wind monitors initiated. 2) Data version metadata will be agreed upon, fully documented, and deployed on our data sites. 3) The first version of the data description rules, encoded in a XML Schema, will be finalized. 4) Preliminary set of library routines will be collected, documentation standards and formats agreed on, and desirable routines that have not been implemented identified and assigned. 5) ViSBARD test site implemented to independently validate data mirroring procedures. The specific MIT tasks over the duration of this project are the following: a) implement mirroring service for WIND plasma data b) participate in XML Schema development c) contribute toward routine library.

Lazarus, Alan J.↗

NASA NTRS1990

Advanced Communications Technology Satellite (ACTS) and potential system applications

A description of the advanced communications technology satellite (ACTS) system is given with special emphasis on the communication characteristics. Potential satellite communications scenarios, including future operational ACTS-like satellite systems, are discussed. The description of the ACTS system updates previously published ACTS system references. Detailed information on items such as experimental ground stations is presented. The potential services can be generically described as voice, video, and data services. The implementation of these services on future operational ACTS-like systems can lead to unique quality, flexibility, and capacity characteristics at lower service costs. The specific service applications that could be supported range from low to high data rates and include both domestic and international applications.

Wright, David L.↗

NASA NTRS1986

Mature data transport and command management services for the Space Station

The duplex space/ground/space data services for the Space Station are described. The need to separate the uplink data service functions from the command functions is discussed. Command management is a process shared by an operation control center and a command management system and consists of four functions: (1) uplink data communications, (2) management of the on-board computer, (3) flight resource allocation and management, and (4) real command management. The new data service capabilities provided by microprocessors, ground and flight nodes, and closed loop and open loop capabilities are studied. The need for and functions of a flight resource allocation management service are examined. The system is designed so only users can access the system; the problems encountered with open loop uplink access are analyzed. The procedures for delivery of operational, verification, computer, and surveillance and monitoring data directly to users are reviewed.

Carper, R. D.↗

NASA NTRS1983

Comparative analysis of large antenna spacecraft using the ideas system

A Land Mobile Satellite System (LMSS), capable of providing mobile communications for commercial and government applications in nonmetropolitan areas of the continental U.S. and Canada as an augmentation to existing and planned terrestrial systems, is being studied. The satellite system would provide 'narrow band' telecommunications services such as mobile radio, telephone, dispatch, safety, and special radio services, and thin-route fixed telephone and data services in the 806-890 MHz band and continuous emergency beacon monitoring in the 406-406.1 MHz band. A single Shuttle launch with an upper stage orbital transfer system would place the LMSS spacecraft in geosynchronous orbit over the continental U.S. in 1995 with a 10-year lifetime. The present investigation has the objective to evaluate, compare, and rank selected spacecraft concepts, to suggest design improvement to the individual concepts, and to identify technology needs.

Garrett, L. B.↗

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 NTRS2013

Validation of Helicopter Gear Condition Indicators Using Seeded Fault Tests

A "seeded fault test" in support of a rotorcraft condition based maintenance program (CBM), is an experiment in which a component is tested with a known fault while health monitoring data is collected. These tests are performed at operating conditions comparable to operating conditions the component would be exposed to while installed on the aircraft. Performance of seeded fault tests is one method used to provide evidence that a Health Usage Monitoring System (HUMS) can replace current maintenance practices required for aircraft airworthiness. Actual in-service experience of the HUMS detecting a component fault is another validation method. This paper will discuss a hybrid validation approach that combines in service-data with seeded fault tests. For this approach, existing in-service HUMS flight data from a naturally occurring component fault will be used to define a component seeded fault test. An example, using spiral bevel gears as the targeted component, will be presented. Since the U.S. Army has begun to develop standards for using seeded fault tests for HUMS validation, the hybrid approach will be mapped to the steps defined within their Aeronautical Design Standard Handbook for CBM. This paper will step through their defined processes, and identify additional steps that may be required when using component test rig fault tests to demonstrate helicopter CI performance. The discussion within this paper will provide the reader with a better appreciation for the challenges faced when defining a seeded fault test for HUMS validation.

Dempsey, Paula↗

NASA NTRS2005

The Virtual Solar Observatory: Still a Small Box

Two and a half years after a design study began, and a year and a half after development commenced, version 1.0 of the Virtual Solar Observatory (VSO) was released at the 2004 Fall AGU meeting. Although internal elements of the VSO have changed, the basic design has remained the same, reflecting the team's belief in the importance of a simple, robust mechanism for registering data provider holdings, initiating queries at the appropriate provider sites, aggregating the responses, allowing the user to iterate before making a final selection, and enabling the delivery of data directly from the providers. In order to make the VSO transparent, lightweight, and portable, the developers employed XML for the registry, SOAP for communication between a VSO instance and data services, and HTML for the graphic user interface (GUI's). We discuss the internal data model, the API, and user responses to various trial GUI's as typical design issues for any virtual observatory. We also discuss the role of the "small box" of data search, identification, and delivery services provided by the VSO in the larger, Sun-Solar System Connection virtual observatory (VxO) scheme.

Gurman, J. B.↗

NASA NTRS1978

Low cost satellite land mobile service for nationwide applications

A satellite land mobile system using mobile radios in the UHF band, and Ku-band Communications Routing Terminals (earth stations) for a nationwide connection from any mobile location to any fixed or mobile location, and from any fixed location to any mobile location is proposed. The proposed nationwide satellite land mobile service provides: telephone network quality (1 out of 100 blockage) service, complete privacy for all the users, operation similar to the telephone network, alternatives for data services up to 32 Kbps data rates, and a cost effective and practical mobile radio compatible with system sizes ranging from 10,000 to 1,000,000 users. Seven satellite alternatives (ranging from 30 ft diameter dual beam antenna to 210 ft diameter 77 beam antenna) along with mobile radios having a sensitivity figure of merit (G/T) of -15 dB/deg K are considered. Optimized mobile radio user costs are presented as a function of the number of users with the satellite and mobile radio alternatives as system parameters.

Weiss, J. A.↗

NASA NTRS2005

Bandwidth Efficient Modulation and Coding Techniques for NASA's Existing Ku/Ka-Band 225 MHz Wide Service

The National Aeronautics and Space Administration (NASA) has recently established the Tracking and Data Relay Satellite System (TDRSS) K-band Upgrade Project (TKUP), a project intended to enhance the TDRSS Ku-band and Ka-band Single Access Return 225 MHz (Ku/KaSAR-225) data service by adding the capability to process bandwidth efficient signal design and to replace the White Sand Complex (WSC) KSAR high data rate ground equipment and high rate switches which are nearing obsolescence. As a precursor to this project, a modulation and coding study was performed to identify signal structures which maximized the data rate through the Ku/KaSAR-225 channel, minimized the required customer EIRP and ensured acceptable hardware complexity on the customer platform. This paper presents the results and conclusions of the TKUP modulation and coding study.

Gioannini, Bryan↗

NASA NTRS2004

The Wallops Flight Facility Rapid Response Range Operations Initiative

While the dominant focus on short response missions has appropriately centered on the launch vehicle and spacecraft, often overlooked or afterthought phases of these missions have been launch site operations and the activities of launch range organizations. Throughout the history of organized spaceflight, launch ranges have been the bane of flight programs as the source of expense, schedule delays, and seemingly endless requirements. Launch Ranges provide three basic functions: (1) provide an appropriate geographical location to meet orbital other mission trajectory requirements, (2) provide project services such as processing facilities, launch complexes, tracking and data services, and expendable products, and (3) assure safety and property protection to participating personnel and third-parties. The challenge with which launch site authorities continuously struggle, is the inherent conflict arising from projects whose singular concern is execution of their mission, and the range s need to support numerous simultaneous customers. So, while tasks carried out by a launch range committed to a single mission pale in comparison to efforts of a launch vehicle or spacecraft provider and could normally be carried out in a matter of weeks, major launch sites have dozens of active projects separate sponsoring organizations. Accommodating the numerous tasks associated with each mission, when hardware failures, weather, maintenance requirements, and other factors constantly conspire against the range resource schedulers, make the launch range as significant an impediment to responsive missions as launch vehicles and their cargo. The obvious solution to the launch site challenge was implemented years ago when the Department of Defense simply established dedicated infrastructure and personnel to dedicated missions, namely an Inter Continental Ballistic Missile. This however proves to be prohibitively expensive for all but the most urgent of applications. So the challenge becomes how can a launch site provide acceptably responsive mission services to a particular customer without dedicating extensive resources and while continuing to serve other projects? NASA's Wallops Flight Facility (WFF) is pursuing solutions to exactly this challenge. NASA, in partnership with the Virginia Commercial Space Flight Authority, has initiated the Rapid Response Range Operations Initiative (R3Ops). R3Ops is a multi-phased effort to incrementally establish and demonstrate increasingly responsive launch operations, with an ultimate goal of providing ELV-class services in a maximum of 7-10 days from initial notification routinely, and shorter schedules possible with committed resources. This target will be pursued within the reality of simultaneous concurrent programs, and ideally, largely independent of specialized flight system configurations. WFF has recently completed Phase 1 of R3Ops, an in-depth collection (through extensive expert interviews) and software modeling of individual steps by various range disciplines. This modeling is now being used to identify existing inefficiencies in current procedures, to identify bottlenecks, and show interdependencies. Existing practices are being tracked to provide a baseline to benchmark against as new procedures are implemented. This paper will describe in detail the philosophies behind WFF's R3Ops, the data collected and modeled in Phase 1, and strategies for meeting responsive launch requirements in a multi-user range environment planned for subsequent phases of this initiative.

Underwood, Bruce E.↗

NASA NTRS1981

ADS pilot methodologies as candidates for ADS standards

Panel presentations and activities aimed at a critical assessment of the completeness and accuracy of a pilot methodology survey for an Applications Data Service are presented. Standards for interconnecting pilot programs for data sharing are outlined. Panel responsibilities and assignments for the session are given.

Giragosian, P.↗

NASA NTRS1981

ADS pilot program Plan

The Applications Data Service (ADS) is a system based on an electronic data communications network which will permit scientists to share the data stored in data bases at universities and at government and private installations. It is designed to allow users to readily locate and access high quality, timely data from multiple sources. The ADS Pilot program objectives and the current plans for accomplishing those objectives are described.

Clauson, J.↗

NASA NTRS1981

Future satellite systems - Market demand assessment

During 1979-80, a market study was performed regarding the future total demand for communications services, and satellite transmission service at the 4/6 GHz, 12/14 GHz, and 20/30 GHz frequencies. Included in the study were a variety of communications traffic characteristics as well as projections of the cost of C and Ku band satellite systems through the year 2000. In connection with the considered study, a total of 15 major study tasks and subtasks were undertaken and were all interrelated in various ways. The telecommunications service forecasts were concerned with a total of 21 data services, 5 voice services, and 5 video services. The traffic volumes within the U.S. for the three basic services were projected for three time periods. It is found that the fixed frequency allocation for domestic satellites combined with potential interference from adjacent satellites means a near term lack of orbital positions above the U.S.

Reiner, P. S.↗

NASA NTRS1986

University participation via UNIDATA, part 2

The University Corporation for Atmospheric Research (UCAR) is presently completing UNIDATA, Phase II, considered to be the design phase of the UNIDATA Project. The four major components of the UNIDATA System are: (1) global services which access is provided, (2) long haul communication for providing that access, (3) local services for providing access and local management of acquired data, and (4) local interactive processing and graphical display. Each component is described in detail with linkages among the components elucidated. Within this framework, access to the PCDS is discussed. It is pointed out that access to the PCDS could occur via general purpose computer-to-computer communications providing remote log on to the system. The UNIDATA System could also be used to transfer information from the PCDS, provided the appropriate software is available to receive the data. Both of these scenarios require agreements on the access protocols and appropriate physical connections. Universities' needs for weather information on a near real-time basis, and UNIDATA has already established a satellite broadcast data service for this purpose.

Fulker, D. W.↗

NASA NTRSDate not supplied

HRP Data Management Plan

The purpose of Human Research Program Data Management Plan (DMP) is to define the processes and activities required for the overall management of the research data collected and managed by HRP throughout their life cycle. New updates to the Data Management Plan in 2023 include 1. CAPABILITIES AND SERVICES Data Repositories. Principal Investigators (PIs) funded by HRP may be asked to submit data to one of several NASA data repositories. HRP archives data in the NASA Life Sciences Portal (NLSP) that it considers to be unique and high value. This includes data from human subjects in space flight (ISS and commercial flights) and ground analogs to spaceflight; spaceflight tech demos involving humans; human omics data including the microbiome; parabolic flight studies; and the NASA Space Radiation Laboratory (NSRL). The Open Science Data Repository (OSDR) includes The Ames Life Sciences Data Archive (ALSDA), used to archive non-human biological data (e.g., animal) generated by the Human Research program, and GeneLab, available to HRP PIs to archive non-human omics data. Catalog for search and retrieval. A catalog of non-human HRP life science experiments, with all associated descriptions (mission, payload, hardware, and personnel related information), and biospecimens is provided on the NLSP public web site for search and retrieval. 2. IRB ROLE IN RETURN OF INDIVIDUAL RESEARCH RESULTS The NASA IRB manages the process for incidental findings and for returning results to subjects for studies for which NASA IRB is the IRB of record. Omics data, especially genomics data, may generate information significant to the health of or risk to a research subject. These data potentially hold the keys to understand lifetime risks of chronic diseases, such as cancer, as well as risks associated with exposures common in space flight. 3. UPDATE OF TERMS – IDENTIFIABLE AND ATTRIBUTABLE DATA HRP now follows Federal and NASA policy by using “identifiable” instead of “attributable” for Personally Identifiable Information (PII). 4. POLICY ABOUT INTERNAL NON-RESEARCH USE OF DATA The HRP Chief Scientist grants access to data from HRP-funded research for non-research internal use that includes program management, customer facilitation, strategic planning, and risk research planning. Typical HRP personnel granted access to HRP research data for internal use include the Element Scientist, Subject Matter Experts (SME), and Data/bioinformatics Scientists. If data accessed for Internal Use is provided to an intramural or extramural scientist for hypothesis driven research, all Federal and NASA regulations (e.g., IRB review) regarding human subject research apply.

Data Management Plan↗