Search NASA⌕ Search

SEARCH · Search NASA

Results for “Ground Support 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 325 records · Page 18

Identifying Functional Requirements for Flexible Airspace Management Concept Using Human-In-The-Loop Simulations

Flexible Airspace Management (FAM) is a mid- term Next Generation Air Transportation System (NextGen) concept that allows dynamic changes to airspace configurations to meet the changes in the traffic demand. A series of human-in-the-loop (HITL) studies have identified procedures and decision support requirements needed to implement FAM. This paper outlines a suggested FAM procedure and associated decision support functionality based on these HITL studies. A description of both the tools used to support the HITLs and the planned NextGen technologies available in the mid-term are presented and compared. The mid-term implementation of several NextGen capabilities, specifically, upgrades to the Traffic Management Unit (TMU), the initial release of an en route automation system, the deployment of a digital data communication system, a more flexible voice communications network, and the introduction of a tool envisioned to manage and coordinate networked ground systems can support the implementation of the FAM concept. Because of the variability in the overall deployment schedule of the mid-term NextGen capabilities, the dependency of the individual NextGen capabilities are examined to determine their impact on a mid-term implementation of FAM. A cursory review of the different technologies suggests that new functionality slated for the new en route automation system is a critical enabling technology for FAM, as well as the functionality to manage and coordinate networked ground systems. Upgrades to the TMU are less critical but important nonetheless for FAM to be fully realized. Flexible voice communications network and digital data communication system could allow more flexible FAM operations but they are not as essential.

dynamic airspace configuration↗

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↗

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-tostation 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 inorbit spacecraft, the operational capabilities that it enabled, along with lessons learned and recommendations for future missions.

Fesq, Lorraine↗

The J-2X Upper Stage Engine: From Design to Hardware

NASA is well on its way toward developing a new generation of launch vehicles to support of national space policy to retire the Space Shuttle fleet, complete the International Space Station, and return to the Moon as the first step in resuming this nation s exploration of deep space. The Constellation Program is developing the launch vehicles, spacecraft, surface systems, and ground systems to support those plans. Two launch vehicles will support those ambitious plans the Ares I and Ares V. (Figure 1) The J-2X Upper Stage Engine is a critical element of both of these new launchers. This paper will provide an overview of the J-2X design background, progress to date in design, testing, and manufacturing. The Ares I crew launch vehicle will lift the Orion crew exploration vehicle and up to four astronauts into low Earth orbit (LEO) to rendezvous with the space station or the first leg of mission to the Moon. The Ares V cargo launch vehicle is designed to lift a lunar lander into Earth orbit where it will be docked with the Orion spacecraft, and provide the thrust for the trans-lunar journey. While these vehicles bear some visual resemblance to the 1960s-era Saturn vehicles that carried astronauts to the Moon, the Ares vehicles are designed to carry more crew and more cargo to more places to carry out more ambitious tasks than the vehicles they succeed. The government/industry team designing the Ares rockets is mining a rich history of technology and expertise from the Shuttle, Saturn and other programs and seeking commonality where feasible between the Ares crew and cargo rockets as a way to minimize risk, shorten development times, and live within the budget constraints of its original guidance.

Byrd, Thomas↗

Skylab Rescue Space Vehicle OAT No. 1 Plugs in Test

A test is described which demonstrates the compatibility of the Skylab Rescue Space Vehicle systems, the ground support equipment, and off-site support facilities by proceeding through a simulated launch countdown, liftoff, and flight. The functions of propellant loading, umbilical ejection, holddown arm release, service arm retraction, liftoff, and inflight separation are simulated. An external power source supplies transfer power to internal, and instrument unit commands are simulated by the digital command system. The test outline is presented along with a list of references, intercommunications information, radio frequency matrix, and interface control chart.

Jevitt, S. J.↗

Modeling and Performance Considerations for Automated Fault Isolation in Complex Systems

The purpose of this paper is to document the modeling considerations and performance metrics that were examined in the development of a large-scale Fault Detection, Isolation and Recovery (FDIR) system. The FDIR system is envisioned to perform health management functions for both a launch vehicle and the ground systems that support the vehicle during checkout and launch countdown by using suite of complimentary software tools that alert operators to anomalies and failures in real-time. The FDIR team members developed a set of operational requirements for the models that would be used for fault isolation and worked closely with the vendor of the software tools selected for fault isolation to ensure that the software was able to meet the requirements. Once the requirements were established, example models of sufficient complexity were used to test the performance of the software. The results of the performance testing demonstrated the need for enhancements to the software in order to meet the demands of the full-scale ground and vehicle FDIR system. The paper highlights the importance of the development of operational requirements and preliminary performance testing as a strategy for identifying deficiencies in highly scalable systems and rectifying those deficiencies before they imperil the success of the project

Ferrell, Bob↗

In Situ Measurements of Surface Texture with Virtual Environments Support Science-Driven Human Surface Operations on the Moon and Beyond

Visualization tools enabling real-time scientific analysis are important for supporting future astronaut operations on the lunar surface. Such tools can be built into virtual environments to support scientific investigations, as well as situational awareness, real-time decision making, and efficient communication between astronauts and ground and support systems. Understanding how these tools can be optimized for science is essential for upcoming Artemis missions. In this contribution, we discuss how measurements of surface texture at multiple length scales can greatly enhance in situ science on/of the Moon, and eventually Mars, asteroids, and beyond. Roughness measurements at various wavelengths directly support objectives defined in the Artemis Science Plan, including (O1) “understanding planetary processes,” (O2) “understanding volatile cycles,” and (O3) “interpreting the impact history of the Earth-Moon system” . Key scientific analyses enabled by texture measurements at different length scales include: ● Sub-centimeter scales: Texture measurements can help constrain lava flow crystallinity, lava rheology, emplacement flow dynamics, and cooling histories (O1). Measurements of lacunarity (voids in fractal fill space) can shed light on eruptive volatile content, residence time of migrating volatiles, and near-surface volume available for micro-cold trapping of volatiles (O1, O2). ● Centimeter–meter scales: Texture measurements can be used for the differentiation of individual lava flows, the reconstruction of local stratigraphies and emplacement sequences, characterization of post-emplacement surface modification processes (O1, O3). Derived roughness (polarization) metrics can be used in the detection of water ice and characterization of ice properties (e.g., purity, grade, depth, abundance). ● Hectometer–Kilometer scales: Texture measurements can be used to differentiate major geologic surface units and surface structures (O1), constrain the presence of abundant ground ices (O2), and analyze surface modification and estimate surface age (O3). Real-time measurements of surface texture across these multiple length scales will enable efficient sample identification and scientific investigations by future astronauts. To support these investigations and the objective classification of surface texture, virtual environments employed by astronauts should be able to instantaneously convert raw data into processed data (e.g., digital terrain and elevation models) and derived metrics (e.g., RMS, std, Hurst, CPR) and perform statistical analyses (e.g., PCA, outliers, correlation matrices). Such tools are being developed and tested by the Resource Exploration and Science of our Cosmic Environment (RESOURCE) team, a node of NASA’s Solar System Exploration Research Virtual Institute (SSERVI), and are an excellent example of the powerful synergies of human and robotic ground assets critical in the return of humans to the Moon.

Ariel N. Deutsch↗

Cryogenic Limb Array Etalon Spectrometer (CLAES) S/N001 cryostat test results

The results of a test program designed to verify the operational and thermal performance of the Cryogenic Limb Array Etalon Spectrometer (CLAES) S/N001 Ne/CO2 cryostat, as monitored and serviced by the Data Acquisition System and Ground Support Equipment, are presented. The S/N001 model test assembly consists of the S/N001 configuration coupled with an instrument thermal mass simulator (ITMS) for simulating the thermal behavior of the instrument package. The test data for the cryostat include the rate of temperature decrease of the various parts of the cryostat/ITMS and the final equilibrium temperatures of the shields, thermal links, and tank. The test results showed that system heat rates, operating temperatures, and expected end-of-life temperature predictions all agree with predictions within estimated margins.

Horsley, W. J.↗

Analysis and Optimization of Test Plans for Advanced Exploration Systems Reliability and Supportability

Future crewed exploration missions beyond Low Earth Orbit (LEO) will operate farther from Earth and be logistically isolated for longer than any previous human spaceflight mission. Under these conditions, supportability and reliability willbestronger drivers of mission mass and risk than they have been in the past. Items with high failure rates, or uncertain failure rates, can result in high spares mass requirements and/or high risk on deep space missions. Testing is a critical element of system development which provides the opportunity to identify and resolve design issues, defects, or other failure modes before they cause problems during a mission. Reliability growth programs can reduce failure rates by identifying and remove failure modes via design changes, and long-duration life testing can provide valuable data to reduce failure rate estimate uncertainty and verify (to some level of confidence) that components are as reliable as expected. Testing activities take time and resources, however, and must be incorporated into program plans in order to be fully effective. This paper presents an integrated reliability test plan analysis and optimization methodology, which has been used to inform Advanced Exploration Systems (AES) Life Support Systems (LSS) ground test planning for future missions. The methodology determines the optimal number of test units to purchase and allocation of test time –split between reliability growth and uncertainty reduction testing –across a given set of items in order to minimize spares mass for a given mission under constraints on total test cost and schedule. Model outputs also include expected spares mass after testing and the expected number of modifications or refurbishments during testing, both of which can inform program planning. Discussion of the model, conclusions, and future work are also presented.

Testing↗

Analysis and Optimization of Test Plans for Advanced Exploration Systems Reliability and Supportability

Future crewed exploration missions beyond Low Earth Orbit (LEO) will operate farther from Earth and be logistically isolated for longer than any previous human spaceflight mission. Under these conditions, supportability and reliability willbestronger drivers of mission mass and risk than they have been in the past. Items with high failure rates, or uncertain failure rates, can result in high spares mass requirements and/or high risk on deep space missions. Testing is a critical element of system development which provides the opportunity to identify and resolve design issues, defects, or other failure modes before they cause problems during a mission. Reliability growth programs can reduce failure rates by identifying and remove failure modes via design changes, and long-duration life testing can provide valuable data to reduce failure rate estimate uncertainty and verify (to some level of confidence) that components are as reliable as expected. Testing activities take time and resources, however, and must be incorporated into program plans in order to be fully effective. This paper presents an integrated reliability test plan analysis and optimization methodology, which has been used to inform Advanced Exploration Systems (AES) Life Support Systems (LSS) ground test planning for future missions. The methodology determines the optimal number of test units to purchase and allocation of test time –split between reliability growth and uncertainty reduction testing –across a given set of items in order to minimize spares mass for a given mission under constraints on total test cost and schedule. Model outputs also include expected spares mass after testing and the expected number of modifications or refurbishments during testing, both of which can inform program planning. Discussion of the model, conclusions, and future work are also presented.

Testing↗

Launch Processing System operations with a future look to Operations Analyst (OPERA)

The Launch Processing System architecture and the ground support operations required to provide Shuttle System engineers with the capability to safely process and launch an Orbiter are described. The described ground operations are the culmination of eleven years of experience and redesign. Some of the 'lessons learned' are examined, and problem areas which ground support operations have identified over the years as the Shuttle and Launch Processing Systems continue to grow in complexity are discussed. The Operational Analyst for Distributed Systems (OPERA), a proposed set of expert systems for the Launch Processing System Operational assistance, is discussed along with its extensions to prospective future configurations and components for the Launch Processing System.

Heard, Astrid E.↗

NIMBUS COMMAND SUBSYSTEM

All satellites have one common requirement, known as the command facility. This is usually a real-time direct RF link from a ground transmitter through the satellite receiver and decoder to a relay or controlled circuit. The more sophisticated research and operational satellites require a command facility which will permit storing of commands to activate systems at predetermined future times when the satellite is beyond the range of the command ground station. These satellites require an accurate clock and a source of precision frequencies. In the Nimbus spacecraft, all these functions are performed by an integrated command and clock subsystem, which includes the command clock and clock-receiver modules in the spacecraft, plus the associated command ground station. This paper will describe the functions and features of these various equipment's.

GROUND SUPPORT SYSTEM↗

Role of simulation and emulation in the development of Shuttle-Centaur (STS-Centaur)

To support the task of integrating the Centaur liquid-fueled upper-stage space vehicle into the space shuttle program. A system to simulate and emulate the STS-Centaur avionic flight system and its supporting ground control and checkout equipment was selected and designated the systems integration facility (SIF). Located in San Diego, California, the SIF is composed of integrated simulators that form a composite control system complement to the STS-Centaur airborne and avionic support equipment. An off-line capability to verify the system design of the Centaur airborne support equipment (CASE) and the Centaur avionic flight system is provided as well as a realistic medium for the development and integration of ground checkout and airborne control software programs. Each simulator is composed of prototype hardware, where feasible, to maximize configuration likeness. Where emulated flight or ground hardware is used, it provides physical characteristics (loads, signals, etc.) equivalent to those of the flight hardware. The hardware and software implementation of the SIF are described.

Gordan, A. L.↗

Recommendations on the Use of Commercial-Off-The-Shelf (COTS) Electrical, Electronic, and Electromechanical (EEE) Parts for NASA Missions - Phase II

This assessment had two Phases. Phase I captured NASA Centers’ current practices for commercial-off-the-shelf (COTS) Electrical, Electronic, and Electromechanical (EEE) parts 1 used in spaceflight systems and ground support equipment (available at https://ntrs.nasa.gov/citations/20205011579) [ref. 1]. The Phase II report provides guidance for selecting and using COTS parts in NASA missions. The approaches proposed in this report differ from current agency practices. This top-level executive summary touches on these new approaches for using COTS parts but does not provide the detailed information that is critical in understanding the rationale behind these new approaches. Readers will need to read the entire report to gain full understanding and effectively use the recommendations herein. NASA’s historical approach to selecting and applying parts has been to define certain parts, primarily specific classes of military specification (MIL-SPEC) parts, as “standard”, leaving all others, including COTS parts, as nonstandard. Standard parts typically are used without further testing (“use-as-is”). Nonstandard parts are subjected to initial screening and subsequent lot acceptance testing of representative samples from each procured lot per MIL-SPEC or similar requirements. Decades later, top-tier commercial part manufacturers have evolved significant manufacturing, statistical control, and technological improvements that can now provide parts as reliable or more reliable than MIL-SPEC parts, when used within their datasheet limits. Concurrently, the space science and exploration community’s needs demand technological advances unavailable with MIL-SPEC parts. This ongoing change necessitates using COTS parts for space missions. Properly selected COTS parts in appropriate applications can offer performance and supply availability advantages compared to MIL-SPEC parts. Their utility and demonstrated reliability result from large volumes and automated production and testing processes. However, careful review and a thorough understanding of their specifications (i.e., datasheet limitations) is needed, and verifying that manufacturer specifications and reliability meet space hardware application needs are necessary. This report recommends MIL-SPEC screening and non-radiation-related lot acceptance testing be reduced or eliminated in cases where evidence of sufficient quality and reliability exists for COTS parts. The extent of NASA's insight into COTS manufacturers and the amount and nature of the needed evidence will differ by mission and will likely be driven by a mission's resources and associated risk posture. To facilitate this goal, two new terminologies have been defined and described: “Industry Leading Parts Manufacturer (ILPM)” and “Established COTS parts.” An ILPM is a COTS manufacturer that produces high quality and reliable parts. Some parts produced by ILPMs, defined as Established COTS parts, do not need any additional MIL-SPEC or NASA screening and lot acceptance testing to be used in space applications. This report provides guidance for selecting, procuring, and applying COTS parts and for performing part-, board-, and system-level COTS parts verification. The recommendation to select Established COTS parts from ILPMs will assure those COTS parts will have comparable quality to corresponding MIL-SPEC parts. Selecting, applying, and verifying Established COTS parts from ILPMs requires a holistic team approach, engaging parts engineers, circuit designers, quality, reliability, and systems engineers, procurement specialists, radiation specialists, avionics leads, and program/project managers. A mission-specific approach tailored to a project’s Mission, Environment, Applications and Lifetime (MEAL) [ref. 2] requirements should be developed and approved by program/project managers. Any associated risks should be clearly identified, quantified, mitigated, and/or accepted. Different approaches are recommended according to program/project Risk Classes A, B, C, and D [ref. 3] and human-rated missions [ref. 4]: 1. Recommend Classes A and B and human-rated missions consider a “MIL-SPEC parts- based design” approach. ”MIL-SPEC parts-based design” approach is one in which most parts are MIL-SPEC parts and Established COTS parts from ILPMs are used only when an equivalent MIL-SPEC part does not meet functional or size, weight, and power (SWaP) or performance requirements, or is not available. 2. Recommend Classes D and Sub-D missions consider a “System of COTS” approach. “System of COTS” approach is one which most parts are Established COTS parts from ILPMs. 3. Recommend Class C missions determine which approach is the best for their projects; that is, use either a “MIL-SPEC parts-based design” approach, “System of COTS” approach, or a combined approach utilizing elements of both. This report intends to provide guidance in using COTS parts for NASA missions with risk classifications of A through D and human-rated missions; but it does not address the costs of using COTS parts. Costs of using COTS parts in different NASA mission classes can vary significantly even if the same parts are used in different risk postures, due to differing verification levels needed. The guidance does not distinguish between critical or non-critical systems, and a given project will need to apply the appropriate guidance based on their risk posture. The intended audience of this report are NASA personnel and commercial practitioners who support NASA’s spaceflight missions, including spaceflight program or project managers, parts engineers, parts manufacturers, radiation engineers, avionics engineers, system engineers, circuit design engineers, reliability engineers, safety and mission assurance (SMA) personnel, and parts procurement specialists. The NEPP Program will perform a pathfinder study to explore implementing the guidance in this NESC report. An ILPM verification process is not the same as conventional vendor qualification processes performed according to military standards and specifications. This NESC report intends to provide guidance in utilizing available parts data from ILPM manufacturers for parts assurance assessments needed for NASA missions. The report also captured the current practices from DoD and Federal Aviation Administration (FAA) in Section 10. Note each DoD and FAA report was provided by the corresponding agencies regarding their practices, which are independent from the NESC recommendations in the report.

Commercial-Off-The-Shelf↗

Obtaining Data from Space

Ground support of nasa space programs - tracking and command techniques - minitrack, deep space stations, mercury network, data processing centers

DEEP SPACE INSTRUMENTATION FACILITY /DSIF/↗