Search NASA⌕ Search

SEARCH · Search NASA

Results for “SERVICE”

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 109 records · Page 6

Analysis of exhaustive limited service for token ring networks

Token ring operation is well-understood in the cases of exhaustive, gated, gated limited, and ordinary cyclic service. There is no current data, however, on queueing models for the exhaustive limited service type. This service type differs from the others in that there is a preset maximum (omega) on the number of packets which may be transmitted per token reception, and packets which arrive after token reception may still be transmitted if the preset packet limit has not been reached. Exhaustive limited service is important since it closely approximates a timed token service discipline (the approximation becomes exact if packet lengths are constant). A method for deriving the z-transforms of the distributions of the number of packets present at both token departure and token arrival for a system using exhaustive limited service is presented. This allows for the derivation of a formula for mean queueing delay and queue lengths. The method is theoretically applicable to any omega. Fortunately, as the value of omega becomes large (typically values on the order of omega = 8 are considered large), the exhaustive limited service discipline closely approximates an exhaustive service discipline.

Peden, Jeffery H.↗

Robotic servicing of EOS instruments

This paper addresses robotic servicing of the Earth Observing Satellite (EOS) instruments. The goals of implementing a robotic servicing system on EOS would be to maintain the instruments throughout the required mission life and minimize life-cycle costs. To address robot servicing, an initial design concept has been developed which will be applied to a representative EOS instrument. This instrument will be used as a model for determining the most practical level of servicing of its parts, and how to design these parts for robot servicing. Using this representative EOS instrument as a model, a generic design scheme will be developed that can be applied to all EOS instruments. The first task is to determine how to identify which parts must be designed for robot servicing. Next, the requirements imposed on the instruments and the servicing robot when designing for robot serviceability must be examined.

Razzaghi, Andrea I.↗

Service equipment for use in hostile environments

Service equipment for use in hostile environments includes a detachable service unit secured to a stationary service unit. The detachable service unit includes a housing with an exterior plate, a power control interface for connection to an exterior power source, locating pins located in said exterior plate, an electrical connector in the exterior plate electrically coupled to said power control interface, and a pair of clamping receptacles formed in the exterior plate and located on adjacent opposite edges of the exterior plate. The stationary unit includes an electrical connector for connection to the electrical connector of the detachable service unit, a clamping apparatus for clamping and unclamping the detachable service unit from the stationary unit, a base clamp assembly for mounting the clamping apparatus onto the stationary unit, and locating pin holes for receiving the locating pins and aligning the detachable service unit onto the stationary unit. The detachable service unit and stationary unit have mating scalloped faces which aid in alignment and provide a mechanism for heat dissipation.

Dolce, James L.↗

Astronomical Software Directory Service

With the support of NASA's Astrophysics Data Program (NRA 92-OSSA-15), we have developed the Astronomical Software Directory Service (ASDS): a distributed, searchable, WWW-based database of software packages and their related documentation. ASDS provides integrated access to 56 astronomical software packages, with more than 16,000 URLs indexed for full-text searching. Users are performing about 400 searches per month. A new aspect of our service is the inclusion of telescope and instrumentation manuals, which prompted us to change the name to the Astronomical Software and Documentation Service. ASDS was originally conceived to serve two purposes: to provide a useful Internet service in an area of expertise of the investigators (astronomical software), and as a research project to investigate various architectures for searching through a set of documents distributed across the Internet. Two of the co-investigators were then installing and maintaining astronomical software as their primary job responsibility. We felt that a service which incorporated our experience in this area would be more useful than a straightforward listing of software packages. The original concept was for a service based on the client/server model, which would function as a directory/referral service rather than as an archive. For performing the searches, we began our investigation with a decision to evaluate the Isite software from the Center for Networked Information Discovery and Retrieval (CNIDR). This software was intended as a replacement for Wide-Area Information Service (WAIS), a client/server technology for performing full-text searches through a set of documents. Isite had some additional features that we considered attractive, and we enjoyed the cooperation of the Isite developers, who were happy to have ASDS as a demonstration project. We ended up staying with the software throughout the project, making modifications to take advantage of new features as they came along, as well as influencing the software development. The Web interface to the search engine is provided by a gateway program written in C++ by a consultant to the project (A. Warnock).

Hanisch, Robert J.↗

NASA Alternate Access to Station Service Concept

The evolving nature of the NASA space enterprise compels the agency to develop new and innovative space systems concepts. NASA, working with increasingly strained budgets and a declining manpower base, is attempting to transform from operational activities to procurement of commercial services. NASA's current generation reusable launch vehicle, the Shuttle, is in transition from a government owned and operated entity to a commercial venture to reduce the civil servant necessities for that program. NASA foresees its second generation launch vehicles being designed and operated by industry for commercial and government services. The "service" concept is a pioneering effort by NASA. The purpose the "service" is not only to reduce the civil servant overhead but will free up government resources for further research - and enable industry to develop a space business case so that industry can sustain itself beyond government programs. In addition, NASA desires a decreased responsibility thereby decreasing liability. The Second Generation Reusable Launch Vehicle (RLV) program is implementing NASA's Space Launch Initiative (SLI) to enable industry to develop the launch vehicles of the future. The Alternate Access to Station (AAS) project office within this program is chartered with enabling industry to demonstrate an alternate access capability for the International Space Station (ISS). The project will not accomplish this by traditional government procurement methods, not by integrating the space system within the project office, or by providing the only source of business for the new capability. The project funds will ultimately be used to purchase a service to take re-supply cargo to the ISS, much the same as any business might purchase a service from FedEx to deliver a package to its customer. In the near term, the project will fund risk mitigation efforts for enabling technologies. AAS is in some ways a precursor to the 2nd Generation RLV. By accomplishing ISS resupply with existing technologies, not only will a new category of autonomous vehicles deliver cargo, but a commercial business base will be incubated that will improve the likelihood of commercial convergence with the next generation of RLVs. Traditional paradigms in government management and acquisition philosophy are being challenged in order to bring about the objective of the AAS project. The phased procurement approach is proving to be the most questionable aspect to date. This work addresses the fresh approach AAS is adopting in management and procurement through a study of the AAS history, current solutions, key technologies, procurement complications, and an incremental forward plan leading to the purchase of a service to deliver goods to ISS. Included in this work is a discussion of the Commercial Space Act of 1998 and how it affects government purchase of space launch and space vehicle services. Industry should find these topics pertinent to their current state of business.

Bailey, Michelle D.↗

Servicing Capability for the Evolutionary Space Station

User servicing for Space Station Freedom (SSF) will span an evolutionary period paralleling that of the station's growth plan. This will include a baseline servicing configuration followed by a final growth phase in which all user servicing requirements are satisfied. Although the basic requirements for user servicing are not station configuration dependent, the emphasis placed on different aspects of servicing may change with the eventual SSF growth objectives. This paper will discuss the servicing requirements and how they will be satisfied by Freedom baseline and growth capabilities. The accomodation of the growth servicing elements will be addressed, including the required hooks and scars to implement these growth servicing capabilities.

Alcorn, George↗

Capability 9.4 Servicing

This paper presents viewgraphs on capability structure 9.4 servicing. The topics include: 1) Servicing Description; 2) Benefits of Servicing; 3) Drivers & Assumptions for Servicing; 4) Capability Breakdown Structure 9.4 Servicing; 5) Roadmap for Servicing; 6) 9.4 Servicing Critical Gaps; 7) Capability 9.4 Servicing; 8) Capability 9.4.1 Inspection; 9) State-of-the-Art /Maturity Level /Capabilities for 9.4.1 Inspection; 10) Capability 9.4.2 Diagnostics; 11) State-of-the-Art/Maturity Level /Capabilities for 9.4.2 Diagnostics; 12) Capability 9.4.3 Perform Planned Maintenance; 13) State-of-the-Art /Maturity Level /Capabilities for 9.4.3 Perform Planned Maintenance; 14) Capability 9.4.4 Perform Unplanned Repair; 15) State-of-the-Art /Maturity Level /Capabilities for 9.4.4 Perform Unplanned Repair; 16) Capability 9.4.5 Install Upgrade; 17) Capability 9.4.5 Install Upgrade; 18) State-of-the-Art /Maturity Level /Capabilities for 9.4.5 Install Upgrade; 19) Capability 9.4.6 Planning, Logistics, Training; and 20) State-of-the-Art /Maturity Level /Capabilities for 9.4.6 Planning, Logistics, & Training;

Moe, Rud↗

Hubble Space Telescope - First Servicing Mission

Space Shuttle mission STS-61 was the first of several planned servicing missions for HST, intended to periodically replace failed components and upgrade scientific instruments with improved versions to keep the telescope viable and productive throughout its planned 15-year lifetime. This First Servicing Mission was also intended to correct several design flaws that were detected shortly after the launch of HST. There were three overall mission objectives for the STS-61 repair mission: 1) To Restore the Planned Scientific Capabilities: One complexity of the First Servicing Mission was the necessity for adding optical elements in the light path to correct the spherical aberration. These corrective optics were required to provide the quantitative science capability to enable key scientific programs to be carried out as originally planned. The addition of the COSTAR and the installation of WFPC2 both contributed to recovering these capabilities. 2) To Restore the Reliability of Vehicle Systems: Failed or degraded components had depleted some of the original subsystem redundancy, which had to be restored to allow continued science operations until the next servicing mission in 1997. Anomalous components that required servicing included the solar arrays, gyroscope sensing units, gyroscope electronics, magnetometers, solar array drive electronics, and electrical fuses. 3) To Validate the On-Orbit Servicing Concept for HST: Validation of the concept of on-orbit servicing as the way to achieve HST's full 15-year life was required to provide a foundation for future servicing missions.

Source record↗

What Do Our Users Want? Perspectives on Understanding and Meeting User Needs for Multi-Mission Data Services

The Sun-Earth Connection Active Archive (SECAA) project of NASA's Space Physics Data Facility operates a range of unique and heavily used multi-mission data services in support of the large-scale science objectives of the Great Observatory, including services such as CDAWeb, the CDAWeb Plus client, SSCWeb, OMNIweb and the CDF data format. In developing and operating these services, we have encountered and continue to struggle with a wide range of issues such as balancing scope and functionality with simplicity and ease of use, understanding the effectiveness of our choices and identifying areas most important for further improvement. In this paper, we will review our key services and then discuss some of our observations and new approaches to understanding and meeting user data service requirements. Some observations are obvious but may still have substantial implications; e.g. functionality without information content is of little user interest, which has led to our recent emphasis on development of web services interfaces, so the content and functionality we already serve is readily and fully available as a building block for new services. Some observations require careful design and tradeoffs; e.g. users will complain when they are offered interfaces with limited options but users are also easily intimidated and become lost when offered extensive options for customization. Some observations remain highly challenging; e.g. a comprehensive multi-mission, multi-source view of all data and services available easily produces a daunting list, but a more selective view can easily lead users to overlook available and relevant data. It is often difficult to obtain and meaningfully interpret measures of true productive usage and overall user satisfaction, even with a variety of techniques including statistics, citations, case studies, user feedback and advisory committees. Most of these issues will apply to and may even be more acute for distributed implementation architectures.

McGuire, Robert E.↗

Solid Propulsion Systems, Subsystems, and Components Service Life Extension

The service life extension of solid propulsion systems, subsystems, and components will be discussed based on the service life extension of the Space Transportation System Reusable Solid Rocket Motor (RSRM) and Booster Separation Motors (BSM). The RSRM is certified for an age life of five years. In the aftermath of the Columbia accident there were a number of motors that were approaching the end of their five year service life certification. The RSRM Project initiated an assessment to determine if the service life of these motors could be extended. With the advent of the Constellation Program, a flight test was proposed that would utilize one of the RSRMs which had been returned from the launch site due to the expiration of its five year service life certification and twelve surplus Chemical Systems Division BSMs which had exceeded their eight year service life. The RSRM age life tracking philosophy which establishes when the clock starts for age life tracking will be described. The role of the following activities in service life extension will be discussed: subscale testing, accelerated aging, dissecting full scale aged hardware, static testing full scale aged motors, data mining industry data, and using the fleet leader approach. The service life certification and extension of the BSMs will also be presented.

Hundley, Nedra H.↗

Navigation Performance of Global Navigation Satellite Systems in the Space Service Volume

This paper extends the results I reported at this year's ION International Technical Meeting on multi-constellation GNSS coverage by showing how the use of multi-constellation GNSS improves Geometric Dilution of Precision (GDOP). Originally developed to provide position, navigation, and timing for terrestrial users, GPS has found increasing use for in space for precision orbit determination, precise time synchronization, real-time spacecraft navigation, and three-axis attitude control of Earth orbiting satellites. With additional Global Navigation Satellite Systems (GNSS) coming into service (GLONASS, Galileo, and Beidou) and the development of Satellite Based Augmentation Services, it is possible to obtain improved precision by using evolving multi-constellation receiver. The Space Service Volume formally defined as the volume of space between three thousand kilometers altitude and geosynchronous altitude ((is) approximately 36,500 km), with the volume below three thousand kilometers defined as the Terrestrial Service Volume (TSV). The USA has established signal requirements for the Space Service Volume (SSV) as part of the GPS Capability Development Documentation (CDD). Diplomatic efforts are underway to extend Space service Volume commitments to the other Position, Navigation, and Timing (PNT) service providers in an effort to assure that all space users will benefit from the enhanced capabilities of interoperating GNSS services in the space domain.

Force, Dale A.↗

A Unified Level of Service Model for NASA Earth Science Data Stewardship

During the past year, the Interagency Implementation and Concepts Team (IMPACT) reviewed existing service models in use at various NASA data centers in an effort to produce a unified, cohesive, and comprehensive Level of Service Model for all of NASA Distributed Active Archive Centers (DAACs). NASA DAACs are responsible for ensuring NASA Earth Science data are accurately and securely ingested, distributed, supported, and preserved. The term “Service" as used here refers to the spectrum of data management activities and outputs provided by DAACs in support of the data cared fo by each data cente. The unified Level-of- Service (LoS) model described in this presentation utilizes both the NASA-defined data product category and the data processing level to easily identify an appropriate level-of-service to be applied to a data product throughout the full data life cycle. This LoS model is to be used by DAACs when appraising incoming data in order to determine the appropriate and required services to provide. The LoS model utilizes a 3-level system in which services build upon previous levels and thereby require greater commitment and effort both on the part of the DAAC personnel and the data producer at the highest level. The LoS model description also contains examples of ways to communicate with data producers and data users what services can be expected, thereby bringing more consistent user experiences across the enterprise. In this presentation, we will outline the features of the LoS model and describe how it relates to the FAIR data practices and the NOAA Maturity Matrix model.

Smith, Deborah↗

On-demand Command and Control of ASTERIA with Cloud-based Ground Station Services

ASTERIA (Arcsecond Space Telescope Enabling Research in Astrophysics) was a 6-unit CubeSat technology demonstration mission that deployed from the International Space Station on November 20th, 2017. After successfully completing its 90-day primary mission that demonstrated arcsecond-level line-of-sight pointing and focal plane thermal stability for exoplanet detection, it entered an extended mission performing onboard software demonstrations to mature technology both in space and on the ground. One of the technologies was a completely cloud-based ground system leveraging Amazon Web Services (AWS) Ground Station service.Announced in December 2018 and launched in May 2019, AWS Ground Station is a fully managed ground station service that aims to reduce the overhead associated with developing and maintaining ground system infrastructure throughout the mission lifecycle. AWS Ground Station makes available the suite of features required for any ground system in support of low-Earth orbit (LEO) and medium-Earth Orbit (MEO) satellite operations on-demand and without setting up or maintaining long-term contracts. Charges are incurred on a per-minute basis for antenna usage during scheduled tracks. Support is available for S-band uplink and downlink, along with X-band narrowband and wideband downlink. Missions that use the service may reserve tracks with any licensed AWS Ground Station antennas located across each service region and have direct access to any AWS services in support of mission operations.The cloud-based architecture built around the AWS Ground Station service greatly enhanced ASTERIA mission operations by enabling end-to-end pass automation, on-demand contact scheduling and contingency planning, along with more efficient data downlink through station availability and station-to-station handovers. It incorporated open-source software, particularly NASA's AMMOS Instrument Toolkit (AIT) and Open Mission Control Technologies (OpenMCT), along with the AWS application programming interfaces (API) to the Ground Station, Elastic Compute Cloud (EC2) and Simple Storage Service (S3) services. After showcasing operability in August 2019, the team continued using and improving this novel ground system architecture until the end of mission in December 2019. This paper describes the cloud-based ground system, how it was designed, tested, and evaluated with an in-orbit spacecraft, the operational capabilities that it enabled, along with lessons learned and recommendations for future missions.

Fesq, Lorraine↗

NASA's Implementation of Cloud Services for Human Space Flight

Cloud is a tried-and-true technology used throughout United States government agencies, including the National Aeronautics and Space Administration (NASA). With reliable results and infrequent downtimes, cloud allows for secure remote access, customizability, and streamlined monitoring options, creating an environment for better data integrity and availability. As NASA increasingly migrates functions to the cloud, the Space Communications and Navigation Program (SCaN) program has been investigating how this capability can be leveraged to provide communication services to its users and customers. Currently, missions such as NASA-ISRO Synthetic Aperture Radar (NISAR), Plankton, Aerosol, Cloud, ocean Ecosystem (PACE), and Roman Space Telescope (RST) are planned to incorporate cloud into their data delivery architecture. However, SCaN is looking to expand further. This conversion to using cloud services allows for greater availability of mission data for both robotic and human space flight (HSF)missions. The SCaN program and the Near Space Network (NSN) are working to consolidate resources and create a cloud environment suitable for the entirety of the SCaN program network architecture. SCaN is in the process of finalizing its cloud architecture and soon will be implementing cloud services. The new services used will adhere to federal regulations including Federal Risk and Authorization Management Program (FedRAMP), which is built upon National Institute of Standards and Technology (NIST)documentation. While keeping in mind these security requirements, an auxiliary objective of the cloud integration is to ensure the most cost-efficient solution; providing a scalable, robust and resilient system. Using cloud services, NASA will gain access to better centralized monitoring and management features, along with customizable services on a pay-per-use plan. With the ever-growing NASA mission data volume needs, maintaining ample storage space is another major constraint. Processing and storing such large amounts of data, on the order of terabytes a day, requires dynamic processing capability which is inherently a strength of cloud computing. By routing this data from ground stations through the cloud, there will be greater ease of access for both SCaN and the user community. Artificial intelligence and other built-in cloud functions can also enhance efficiency, improving data processing time. Thereby also allowing for better data availability. As we look to the future of cloud services, NASA will continue to leverage capabilities that will benefit NASA’s ability to provide cost-effective communication services. This paper further outlines the evolution of cloud use by SCaN in the context of Human Space Flight.

cloud storage↗

NASA POWER: Providing Present and Future Climate Services Based on NASA Data for the Energy, Agricultural, and Sustainable Buildings Communities

NASA’s Prediction of Worldwide Energy Resource (POWER) project facilitates the use of NASA Earth Science data holdings within the renewable energy, agricultural, and building heating/cooling design industries. POWER packages solar and meteorological data at various temporal levels from several NASA projects in a user friendly GIS-enabled web services system (https://power.larc.nasa.gov). Data users can access these data either through an intuitive data viewer, image services fully integrable with GIS analysis, connections in the cloud through an Amazon Web Services S3 Bucket, or fully customizable access through an API. Data provided by POWER has been successfully used by decision makers to support actions that address climate change. For example, POWER data has been used to remotely monitor solar array fields and integrated in a sizing tool for off-grid solar and storage systems. POWER data has also been coupled with key building decision tools to support design and retrofitting of building energy systems for energy efficiency and reduction of greenhouse gases. POWER is now developing climate services to provide time series of the projected future evolution of key quantities that interest our users, such as heating/cooling degree days, temperature, wind speed, and downwelling solar flux. We demonstrate the potential of the new climate services by presenting here a range of possible future changes in these quantities at different NASA centers across the continental United States. These data services are based on downscaled climate model data from the NASA Earth Exchange Global Daily Downscaled Projections (NEX-GDDP) data set. We highlight the important insights that new climate services can provide. Our climate services will help our user communities quantify the impacts of climate change to support their key decisions in planning for the future, both inside and outside the Federal Government, especially for decisions in renewable energy and in building heating and cooling.

Bradley Hegyi↗

Service Quality Assessment for NASA's Deep Space Network: No Longer a Luxury

When NASA's Deep Space Network (DSN) was established almost a half century ago, the concept of computer-based service delivery was impractical or infeasible due to the state of information technology As a result, the interface the DSN exposes to its customers tends to be equipment-centric, lacking a clear demarcation between the DSN and the mission operation systems (MOS) of its customers. As the number of customers has continued to increase, the need to improve efficiency and minimize costs has grown. This growth has been the impetus for a DSN transformation from an equipment-forrent provider to a provider of standard services. Service orientation naturally leads to requirements for service management, including proactive measurement of service quality and service levels as well as the efficiency of internal processes and the performance of service provisioning systems. DSN System Engineering has surveyed industry offerings to determine if commercial successes in decision support and Business Intelligence (BI) solutions can be applied to the DSN. A pilot project was initiated, and subsequently executed to determine the feasibility of repurposing a commercial Business Intelligence platform for engineering analysis in conjunction with the platform's intended business reporting and analysis functions.

Operations Efficiency↗

Exploring NASA GES DISC Data with Interoperable Services

Overview of NASA GES DISC (NASA Goddard Earth Science Data and Information Services Center) data with interoperable services: Open-standard and Interoperable Services Improve data discoverability, accessibility, and usability with metadata, catalogue and portal standards Achieve data, information and knowledge sharing across applications with standardized interfaces and protocols Open Geospatial Consortium (OGC) Data Services and Specifications Web Coverage Service (WCS) -- data Web Map Service (WMS) -- pictures of data Web Map Tile Service (WMTS) --- pictures of data tiles Styled Layer Descriptors (SLD) --- rendered styles.

Giovanni↗

MERRA-2 Data and Analytic Services at NASA GES DISC for Climate Extremes Study

NASA's climate reanalysis datasets from the Modern Era Retrospective-analysis for Research and Applications, Version 2 (MERRA-2) contains numerous long-term atmosphere, land, and ocean data products from 1980-present. MERRA-2 datasets, such as precipitation, soil moisture, and temperature, have been used widely to study extreme events. The native archived MERRA-2 data files are day-file (hourly time interval) and month-file, containing up to 125 parameters in one file. Due to the large number of data files and volumes, it is challenging for users, especially the applications research community, to handle the original hourly data files for long time periods to analyze extreme events. In this presentation, we review MERRA-2 data for studies of extreme conditions, and demonstrate analytic services at the NASA Goddard Earth Sciences Data and Information Services Center (GES DISC). One of the current operational services, 'subsetter', allows users to download only specific data of interest, i.e. data selected by parameter, region, and time period. New services are under development that will provide more 'on-the-fly' statistical calculations when downloading data; improve efficiency when accessing long time-series data. We will provide additional "How-to" resources that include step-by-step instructions on data access and usage. We have tested restructuring of day-files in an optimized data cube, which has significantly improved system performance for accessing long time-series. Overall performance is associated with cube size and structure, data compression method, and how the data are accessed. The optimized data cube structure will enable better online analytic services for statistical analysis and extreme events mining. To demonstrate the service, we use an extreme drought associated with the anomalous 2016 monsoon over southern Asia. This prototype time-series service may be augmented in the cloud infrastructure in the future.

data access↗