Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “time 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 595 records · Page 33

Apollo 16 Press Kit

The Apollo 16 spacecraft is scheduled for launch on Apr. 16, 1972 from Complex 39A at the Kennedy Space Center, Florida by the Saturn V launch vehicle. Crewmen are mission commander John W. Young, command module pilot Thomas K. Mattingly II and lunar module pilot Charles M. Duke Jr. Objectives of the mission, to last up to 12 days, as outlined by NASA: to perform selenological inspection, survey and sampling of materials in a preselected region of Descartes using a lunar roving' vehicle; deploy and activate Apollo surface experiments; develop man's capability to work in the lunar environment; obtain photographs of candidate exploration sites; and toconduct inflight experiments and photographic tasks in lunar orbit. Following launch, the spacecraft will reach Earth Parking Orbit and remain in orbit for about two and one-half revolutions prior to Translunar Injection. Next, the Command and Service Module docks with the Lunar Module and the spacecraft "coasts" to the moon. In orbit around the moon, the Command and Service Module/Lunar Module combination will descend to within 50,000 feet of the lunar surface before undocking. The Lunar Module will continue to descend while the Command and Service Module returns to an orbit approximately 60 miles high. Stay time on the lunar surface is scheduled for approximately 73 hours. The ascent stage of the Lunar Module then lifts the astronauts back into lunar orbit where they will dock with the Command/Service Module. The Lunar Module is jettisoned and Transearth Injection follows. Just prior to reentry into the earth's atmosphere, the Service Module is jettisoned, and the astronauts in the Command Module splashdown in the Pacific Ocean. The target point for end-of-mission splashdown is at 05 degrees 0 minutes north latitude and 158 degrees 40 minutes west longitude or approximately 985 nautical miles south of Honolulu, Hawaii. Splashdown is scheduled for Apr. 28, 1972 at 10:30 a.m. Hawaiian Standard Time (2:30 p.m. CST). Recovery forces for Apollo 16, stationed in both the Atlantic and Pacific Oceans, will consist of three ships, nine aircraft and nearly 1,700 personnel. CTF-130 (Manned Spacecraft Recovery Force, Pacific) forces will be stationed south of Hawaii. Three ships, eight helicopters and three Air Force HC-130H aircraft, and nearly 1,100 personnel, will take part. Task Force 140 (Manned Spacecraft Recovery Force, Atlantic), comprising one ship, six HC-130H aircraft, three helicopters and approximately 300 personnel, will be positioned for possible launch abort operations. Two ships in the Atlantic will also be used for acoustical testing. Other forces, primarily aircraft and personnel of the Air Force Aerospace Rescue and Recovery Service will be on alert around the world for contingency recovery support.

Source record↗

A Service Portal for the Integrated SCaN Network

The Space Communication and Navigation (SCaN) program office owns the assets and services provided by the Deep Space Network (DSN), Near Earth Network (NEN), and Space Network (SN). At present, these individual networks are operated by different NASA centers--JPL for DSN--and Goddard Space Flight Center (GSFC) for NEN and SN--with separate commitments offices for each center. In the near future, SCaN's program office would like to deploy an integrated service portal which would merge the two commitments offices with the goal of easing the task of user planning for space missions requiring services of two or more of these networks. Following interviews with subject matter experts in this field, use cases were created to include the services and functionality mission users would like to see in this new integrated service portal. These use cases provide a guideline for a mock-up of the design of the user interface for the portal. The benefit of this work will ease the time required and streamline/standardize the process for planning and scheduling SCAN's services for future space missions.

space communications and navigation (SCaN)↗

New GES DISC Services Shortening the Path in Science Data Discovery

The Current GES DISC available services only allow user to select variables from a single dataset at a time and too many variables from a dataset are displayed, choice is hard. At American Geophysical Union (AGU) 2016 Fall Meeting, Goddard Earth Sciences Data Information Services Center (GES DISC) unveiled a new service: Datalist. A Datalist is a collection of predefined or user-defined data variables from one or more archived datasets. Our science support team curated predefined datalist and provided value to the user community. Imagine some novice user wants to study hurricane and typed in hurricane in the search box. The first item in the search result is GES DISC provided Hurricane Datalist. It contains scientists recommended variables from multiple datasets like TRMM, GPM, MERRA, etc. Datalist uses the same architecture as that of our new website, which also provides one-stop shopping for data, metadata, citation, documentation, visualization and other available services.We implemented Datalist with new GES DISC web architecture, one single web page that unified all user interfaces. From that webpage, users can find data by either type in keyword, or browse by category. It also provides user with a sophisticated integrated data and services package, including metadata, citation, documentation, visualization, and data-specific services, all available from one-stop shopping.

Datalist↗

Improving AIRS NRT Imagery for the Enhancement of Visualization Services in LANCE

The NASA Goddard Earth Sciences Data and Information Services Center (GES DISC) has been the home of processing, archiving, and distribution services for data from the Atmospheric Infrared Sounder (AIRS) mission since its launch in 2002. AIRS provides data enabling global observations of the atmospheric state. The GES DISC provides service to both AIRS standard products and Near Real-time (NRT) products. The AIRS NRT product is one important element in the Land, Atmosphere Near real-time Capability for EOS (LANCE). The LANCE processing of the AIRS NRT product and the generation of the imagery are performed at the GES DISC. The AIRS NRT imagery are generated by mosaicking and mapping the available AIRS 6-minute retrieval granules to a global cylindrical projection. The images are constantly refreshed when new granules are produced. The AIRS NRT Viewer and LANCE Worldview provide visualization services to online users for AIRS NRT imagery. The imagery include atmospheric temperature, humidity, precipitation, Dust Score, CO, and SO2. The AIRS Applications Development Team at NASA JPL developed a new orbit-based algorithm and software to improve the AIRS NRT imagery. The GES DISC is collaborating with the AIRS Applications Development Team for the implementation of the new algorithm and software. The improvements include image quality, new color palettes, and variable changes. In this presentation, we will detail the improvements and demonstrate visualization of the new imagery.

Ding, Feng↗

Zero-Trust Architecture for Autonomous Edge Computing

We are at the apex of an aviation revolution where autonomy will play a central role in enabling complex, multi-agent systems to communicate, interact, and collaborate on a myriad of applications spanning autonomous swarms to wild-fire management. Autonomy is not an absolute but rather a spectrum ranging from a system requiring significant human intervention to one requiring little to none [1]. For example, the extreme, in the case of an autonomous aircraft, is one that operates independently in the airspace interacting with all other elements (air traffic controllers, other pilots) as if it were a human pilot. Critical to this vision is an architecture that enables autonomous agents to interact with minimal latency. Edge computing is an emerging architecture where compute and storage is pushed to the ‘edge’ of the network in order to minimize the round-trip time from agent to resource thereby mitigating the latency associated with cloud-only based approaches. Additionally, services can generate massive amounts of data (e.g., video feeds), which may require analysis in near real-time. Moving this data to the cloud for further processing may not be feasible due to latency, bandwidth, and cost. Privacy, security, and reliability can also be improved by edge computing architectures. However, this geo-distributed and dynamic* architecture complicates the establishment of unambiguous network security boundaries and can lead to vulnerabilities including man in the middle attacks, replay attacks, physical security breaches of edge nodes, signal interception, etc. This motivates the need for zero-trust architectures [2–4] which de-emphasize the notion of static network perimeters and, as the name implies, do not instill any innate trust in any particular agent. It is required that all agents must be authorized and approved in every transaction. In this paper, we present a zero-trust architecture suitable for edge-computing applications that demand significant low-latency, security, privacy, and reliability.

zero trust↗

S-band and Ku-band return service interference between TDRSS users

The Tracking Data Relay Satellite System (TDRSS) return service performance can be degraded by interference from another user when two or more spacecraft communicate with the same Tracking Data Relay Satellite (TDRS) at the same time. This paper describes the S-band and Ku-band return service self interference environment expected in the 1996 - 2010 timeframe and shows the self-interference expected for selected TDRSS users based on Communications Link Analysis and Simulation System (CLASS) Automated Conflict Resolution System (ACRS) and Interference Monitor (IM) tools. The results show: which user links are susceptible to interference from other users, the interference statistics, and whether or not interference can be avoided with appropriate interference mitigation techniques such as scheduling, cross-polarization, or Pseudo random Noise (PN) spreading. The analysis results enable Space Network (SN) managers to determine the impacts of self-interference on the TDRSS service availability. They also enable project offices to determine whether they should select return service communications parameters, such as polarization and PN spreading, to minimize the probability of being impacted by self-interference; try to schedule TDRSS support around other user spacecraft communications schedules; or accept communication outages due to self-interference.

Harrell, Linda↗

Real-Time Multimission Event Notification System for Mars Relay

As the Mars Relay Network is in constant flux (missions and teams going through their daily workflow), it is imperative that users are aware of such state changes. For example, a change by an orbiter team can affect operations on a lander team. This software provides an ambient view of the real-time status of the Mars network. The Mars Relay Operations Service (MaROS) comprises a number of tools to coordinate, plan, and visualize various aspects of the Mars Relay Network. As part of MaROS, a feature set was developed that operates on several levels of the software architecture. These levels include a Web-based user interface, a back-end "ReSTlet" built in Java, and databases that store the data as it is received from the network. The result is a real-time event notification and management system, so mission teams can track and act upon events on a moment-by-moment basis. This software retrieves events from MaROS and displays them to the end user. Updates happen in real time, i.e., messages are pushed to the user while logged into the system, and queued when the user is not online for later viewing. The software does not do away with the email notifications, but augments them with in-line notifications. Further, this software expands the events that can generate a notification, and allows user-generated notifications. Existing software sends a smaller subset of mission-generated notifications via email. A common complaint of users was that the system-generated e-mails often "get lost" with other e-mail that comes in. This software allows for an expanded set (including user-generated) of notifications displayed in-line of the program. By separating notifications, this can improve a user's workflow.

Wallick, Michael N.↗

An investigation of selected on-orbit satellite servicing issues

The results of three separate investigations performed by Science Applications International Corporation (SAIC) between August 1985 and October 1986 as the second phase of the two-phase Satellite Services System Program Plan contract for the Engineering Directorate of the Lyndon B. Johnson Space Center are discussed. The objectives of the first phase of this contract (reported in SAIC-85/1762) were to determine the potential for servicing a diverse range of spacecraft from the Space Shuttle Orbiter and to assess NASA's role as the catalyst in enabling routine on-orbit servicing. The second area of investigation was prompted by the need to understand satellite servicing requirements in the far term (1995 to 2010) and how results from the first phase of this contract could support these requirements. The mission model developed during the first phase was extended using new data and information from studies which address the later time period. The third area of investigation looked at a new servicing mode which had not been studied previously. This mode involves the on-orbit exchange of very large modules with masses greater than approximately 9,000 kilograms and/or lengths greater than approximately nine meters. The viewgraphs used for the final briefing for each of the three investigations, as presented to NASA are given.

Hoffman, Stephen J.↗

Education, Technology, and Media: A Peak into My Summer Internship at NASA Glenn Research Center in Cleveland, Ohio

My name is James Moon and I am a senor at Tennessee State University where my major is Aeronautical and Industrial Technology with a concentration in industrial electronics. I am currently serving my internship in the Engineering and Technical Services Directorate at the Glenn Research Center (GRC). The Engineering and Technical Service Directorate provides the services and infrastructure for the Glenn Research Center to take research concepts to reality. They provide a full range of integrated services including engineering, advanced prototyping and testing, facility management, and information technology for NASA, industry, and academia. Engineering and Technical Services contains the core knowledge in Information Technology (IT). This includes data systems and analysis, inter and intranet based systems design and data security. Including the design and development of embedded real-time sohare applications for flight and supporting ground systems, Engineering and Technical Services provide a wide range of IT services and products specific to the Glenn Research Center research and engineering community.

Moon, James↗

Cloud-Based Time Series Analysis of Extremes: Use Cases and Applications

"Extreme weather events, such as hurricanes, tornadoes, floods, droughts, heatwaves, and blizzards, can cause widespread damage, disrupting ecosystems, agricultural production, and economies. The frequency and intensity of these events have been increasing, likely due to climate change, raising concerns and the need for more accurate analysis and predictions. NASA's Goddard Earth Sciences Data and Information Services Center (GES DISC) has migrated its long-term historical datasets, including precipitation data from MERRA-2 reanalysis, GLDAS land data assimilation, and IMERG satellite observations, to the cloud. This cloud-stored data enables scientists and researchers to utilize cloud computing for advanced modeling and forecasting of extreme weather events, eliminating the need to download large datasets. In this presentation, we will provide an overview of the cloud-based data and services managed by GES DISC; demonstrate methods for accessing and analyzing time series data stored in the cloud; and compare results across various datasets to address critical questions related to extreme precipitation. We will present use cases including: 1. Determining the average total precipitation in California during January and February from 2000 to 2024, and identifying anomalous precipitation in 2021. 2. Calculating the 10, 20, 50, and 100-year return periods for maximum daily rainfall based on 25 years of historical precipitation data (2000-2024) for Maryland.

time series↗

Cost Analysis in a Multi-Mission Operations Environment

Spacecraft control centers have evolved from dedicated, single-mission or single mission-type support to multi-mission, service-oriented support for operating a variety of mission types. At the same time, available money for projects is shrinking and competition for new missions is increasing. These factors drive the need for an accurate and flexible model to support estimating service costs for new or extended missions; the cost model in turn drives the need for an accurate and efficient approach to service cost analysis. The National Aeronautics and Space Administration (NASA) Huntsville Operations Support Center (HOSC) at Marshall Space Flight Center (MSFC) provides operations services to a variety of customers around the world. HOSC customers range from launch vehicle test flights; to International Space Station (ISS) payloads; to small, short duration missions; and has included long duration flagship missions. The HOSC recently completed a detailed analysis of service costs as part of the development of a complete service cost model. The cost analysis process required the team to address a number of issues. One of the primary issues involves the difficulty of reverse engineering individual mission costs in a highly efficient multi-mission environment, along with a related issue of the value of detailed metrics or data to the cost model versus the cost of obtaining accurate data. Another concern is the difficulty of balancing costs between missions of different types and size and extrapolating costs to different mission types. The cost analysis also had to address issues relating to providing shared, cloud-like services in a government environment, and then assigning an uncertainty or risk factor to cost estimates that are based on current technology, but will be executed using future technology. Finally the cost analysis needed to consider how to validate the resulting cost models taking into account the non-homogeneous nature of the available cost data and the decreasing flight rate. This paper presents the issues encountered during the HOSC cost analysis process, and the associated lessons learned. These lessons can be used when planning for a new multi-mission operations center or in the transformation from a dedicated control center to multi-center operations, as an aid in defining processes that support future cost analysis and estimation. The lessons can also be used by mature service-oriented, multi-mission control centers to streamline or refine their cost analysis process.

Felton, Larry↗

Cost Analysis In A Multi-Mission Operations Environment

Spacecraft control centers have evolved from dedicated, single-mission or single missiontype support to multi-mission, service-oriented support for operating a variety of mission types. At the same time, available money for projects is shrinking and competition for new missions is increasing. These factors drive the need for an accurate and flexible model to support estimating service costs for new or extended missions; the cost model in turn drives the need for an accurate and efficient approach to service cost analysis. The National Aeronautics and Space Administration (NASA) Huntsville Operations Support Center (HOSC) at Marshall Space Flight Center (MSFC) provides operations services to a variety of customers around the world. HOSC customers range from launch vehicle test flights; to International Space Station (ISS) payloads; to small, short duration missions; and has included long duration flagship missions. The HOSC recently completed a detailed analysis of service costs as part of the development of a complete service cost model. The cost analysis process required the team to address a number of issues. One of the primary issues involves the difficulty of reverse engineering individual mission costs in a highly efficient multimission environment, along with a related issue of the value of detailed metrics or data to the cost model versus the cost of obtaining accurate data. Another concern is the difficulty of balancing costs between missions of different types and size and extrapolating costs to different mission types. The cost analysis also had to address issues relating to providing shared, cloud-like services in a government environment, and then assigning an uncertainty or risk factor to cost estimates that are based on current technology, but will be executed using future technology. Finally the cost analysis needed to consider how to validate the resulting cost models taking into account the non-homogeneous nature of the available cost data and the decreasing flight rate. This paper presents the issues encountered during the HOSC cost analysis process, and the associated lessons learned. These lessons can be used when planning for a new multi-mission operations center or in the transformation from a dedicated control center to multi-center operations, as an aid in defining processes that support future cost analysis and estimation. The lessons can also be used by mature serviceoriented, multi-mission control centers to streamline or refine their cost analysis process.

Newhouse, M.↗

Apollo Command and Service Module Propulsion Systems Overview

An overview of the Apollo Command and Service Module (CSM) propulsion systems is provided. The systems for CSM propulsion and control are defined, the times during the mission when each system is used are listed, and, the basic components and operation of the service propulsion system, SM reaction control system and CM reaction control system are described.

Interbartolo, Michael A.↗

The 1973 NASA payload model: Space opportunities 1973 - 1991

The tables of schedules and descriptions which portray the 1973 NASA Payload Model are presented. The schedules cover all NASA programs and the anticipated requirements of the user community, not including the Department of Defense, for the 1973 to 1991 period. The descriptions give an indication of what the payload is expected to accomplish, its characteristics, and where it is going. The payload flight schedules shown for each of the discipline areas indicate the time frame in which individual payloads will be launched, serviced, or retrieved. These do not necessarily constitute shuttle flights, however, since more than one payload can be flown on a single shuttle flight depending on size, weight, orbital destination, and the suitability of combining them. The weight, dimension, and destination data represent approximations of the payload characteristics as estimated by the Program Offices. Payload codes are provided for easy correlation between the schedules and descriptions of the Payload Model and subsequent documentation which may reference this model.

Source record↗

Shuttle mission plans

Shuttle mission plans recently developed by NASA for the time period 1980-1991 are presented. Standard and optional services, which will be available to users of the Space Transportation System (STS) when it becomes operational in the 1980's, are described. Pricing policies established by NASA to encourage use of the STS by commercial, foreign and other U.S. Government users are explained. The small Self-Contained Payload Program, which will make space flight opportunities available to private citizens and individual experimenters who wish to use the Space Shuttle for investigative research, is discussed.

Visentine, J. T.↗

Renewing solar science: The solar maximum repair mission

The purpose of the Solar Maximum Repair Mission is to restore the operational capacity of the satellite by replacing the attitude control system module and servicing two of the scientific instruments on board. The mission will demonstrate the satellite servicing capacity of the Space Shuttle for the first time.

Neal, V.↗

Plasma interactions monitoring system

The plasma environment around the space station is expected to be different from that environment which occurs naturally at these altitudes because of the unprecedented size of the space station, its orbital motion, and its high power distribution system. Although there are models which predict the environment around the station, they do not take into account changes in configuration, changes in the natural and induced environments, nor interactions between the different environments. There will be unique perturbations associated with the space station, which will vary as the space station is being developed. Even after the developed space station has been completed environmental conditions will change as the payloads are changed and as the station systems and materials undergo degradation and modification. Because the space station will be a point of many varied activities the environment will continually undergo perturbations from effluents resulting from operations of the reboost module, EVA, airlock operations, and vacuum venting. The use of the Mobile Service Center will cause disturbances which cannot, at this time, be predicted. Also, the natural environment will be affected by solar flares. In addition, the operations of attached payloads, (e.g., ASTROMAG) themselves will undoubtedly cause perturbations to the ambient environment. Finally, the natural environment will change as a result of natural perturbations such as solar flares and geomagnetic storms.

Roberts, William T.↗

Enhancing orbital servicing operations: Providing positive and effective management of spare and installed hardware - A case study of the Hubble Space Telescope

The Satellite Resources Management and Tracking System was developed specifically for the Hubble Space Telescope (HST) program, and now, NASA has the ability to immediately access the necessary data for planning successful orbital satellite servicing operations. This system is an online, real-time data base system that contains a plethora of data on each item identified to support the HST throughout its planned 15 year life. Some of the information provided includes the current status, location, quantity, and history of each asset, a separate record for each discrete serial numbered item, procurement lead times on items sensitive to technology obsolescence, and the maintenance and repair history of each asset. Finally, details are provided on organizational, operational and logistics requirements.

Randolph, Joseph L.↗