SEARCH · Engineering Papers

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 1,045 records · Page 58

All sources NASA NTRS DOE OSTI

NASA NTRS2000

Aeronautical Engineering: A Continuing Bibliography with Indexes

This report lists reports, articles and other documents recently announced in the NASA STI Database. The coverage includes documents on the engineering and theoretical aspects of design, construction, evaluation, testing, operation, and performance of aircraft (including aircraft engines) and associated components, equipment and systems. It also includes research and development in aerodynamics, aeronautics, and ground support equipment for aeronautical vehicles.

Source record↗

NASA NTRS2008

Linking and Combining Distributed Operations Facilities using NASA's "GMSEC" Systems Architectures

NASA's Goddard Mission Services Evolution Center (GMSEC) ground system architecture has been in development since late 2001, has successfully supported eight orbiting satellites and is being applied to many of NASA's future missions. GMSEC can be considered an event-driven service-oriented architecture built around a publish/subscribe message bus middleware. This paper briefly discusses the GMSEC technical approaches which have led to significant cost savings and risk reduction for NASA missions operated at the Goddard Space Flight Center (GSFC). The paper then focuses on the development and operational impacts of extending the architecture across multiple mission operations facilities.

Smith, Danford↗

NASA NTRS2009

Spaceflight Systems Training: A Comparison and Contrasting of Techniques for Training Ground Operators and Onboard Crewmembers

When developing techniques and products for instruction on manned spaceflight systems, training organizations are often faced with two very different customers: ground operators and onboard crewmembers. Frequently, instructional development focuses on one of these customers with the assumption that the other s needs will be met by default. Experience teaches us that differing approaches are required when developing training tailored to the specific needs of each customer. As a rule, ground operators require focused instruction on specific areas of expertise. Their knowledge should be of the details of the hardware, software, and operational techniques associated with that system. They often benefit from historical knowledge of how their system has operated over its lifetime. Since several different ground operators may be interfacing with the same system, each individual operator must understand the agreed-to principles by which that system will be run. In contrast, onboard crewmembers require a more broad, hands-on awareness of their operational environment. Their training should be developed with an understanding of the physical environment in which they live and work and the day-to-day tasks they are most likely to perform. Rarely do they require a deep understanding of the details of a system; it is often sufficient to teach them just enough to maintain situational awareness and perform basic tasks associated with maintenance and operation of onboard systems. Crewmembers may also develop unique onboard operational techniques that differ from preceding crews. They should be taught what flexibility they have in systems operations and how their specific habits can be communicated to ground support personnel. This paper will explore the techniques that can be employed when developing training for these unique customers. We will explore the history of International Space Station training development and how past efforts can guide us in creating training for users of future manned spaceflight efforts.

Balmain, Clinton↗

NASA NTRS2014

NASA Space Launch System Operations Outlook

The National Aeronautics and Space Administration's (NASA) Space Launch System (SLS) Program, managed at the Marshall Space Flight Center (MSFC), is working with the Ground Systems Development and Operations (GSDO) Program, based at the Kennedy Space Center (KSC), to deliver a new safe, affordable, and sustainable capability for human and scientific exploration beyond Earth's orbit (BEO). Larger than the Saturn V Moon rocket, SLS will provide 10 percent more thrust at liftoff in its initial 70 metric ton (t) configuration and 20 percent more in its evolved 130-t configuration. The primary mission of the SLS rocket will be to launch astronauts to deep space destinations in the Orion Multi- Purpose Crew Vehicle (MPCV), also in development and managed by the Johnson Space Center. Several high-priority science missions also may benefit from the increased payload volume and reduced trip times offered by this powerful, versatile rocket. Reducing the lifecycle costs for NASA's space transportation flagship will maximize the exploration and scientific discovery returned from the taxpayer's investment. To that end, decisions made during development of SLS and associated systems will impact the nation's space exploration capabilities for decades. This paper will provide an update to the operations strategy presented at SpaceOps 2012. It will focus on: 1) Preparations to streamline the processing flow and infrastructure needed to produce and launch the world's largest rocket (i.e., through incorporation and modification of proven, heritage systems into the vehicle and ground systems); 2) Implementation of a lean approach to reach-back support of hardware manufacturing, green-run testing, and launch site processing and activities; and 3) Partnering between the vehicle design and operations communities on state-of-the-art predictive operations analysis techniques. An example of innovation is testing the integrated vehicle at the processing facility in parallel, rather than sequentially, saving both time and money. These themes are accomplished under the context of a new cross-program integration model that emphasizes peer-to-peer accountability and collaboration towards a common, shared goal. Utilizing the lessons learned through 50 years of human space flight experience, SLS is assigning the right number of people from appropriate backgrounds, providing them the right tools, and exercising the right processes for the job. The result will be a powerful, versatile, and capable heavy-lift, human-rated asset for the future human and scientific exploration of space.

Hefner, William Keith↗

NASA NTRS2017

Creative Analytics of Mission Ops Event Messages

Historically, tremendous effort has been put into processing and displaying mission health and safety telemetry data; and relatively little attention has been paid to extracting information from missions time-tagged event log messages. Todays missions may log tens of thousands of messages per day and the numbers are expected to dramatically increase as satellite fleets and constellations are launched, as security monitoring continues to evolve, and as the overall complexity of ground system operations increases. The logs may contain information about orbital events, scheduled and actual observations, device status and anomalies, when operators were logged on, when commands were resent, when there were data drop outs or system failures, and much much more. When dealing with distributed space missions or operational fleets, it becomes even more important to systematically analyze this data. Several advanced information systems technologies make it appropriate to now develop analytic capabilities which can increase mission situational awareness, reduce mission risk, enable better event-driven automation and cross-mission collaborations, and lead to improved operations strategies: Industry Standard for Log Messages. The Object Management Group (OMG) Space Domain Task Force (SDTF) standards organization is in the process of creating a formal standard for industry for event log messages. The format is based on work at NASA GSFC. Open System Architectures. The DoD, NASA, and others are moving towards common open system architectures for mission ground data systems based on work at NASA GSFC with the full support of the commercial product industry and major integration contractors. Text Analytics. A specific area of data analytics which applies statistical, linguistic, and structural techniques to extract and classify information from textual sources. This presentation describes work now underway at NASA to increase situational awareness through the collection of non-telemetry mission operations information into a common log format and then providing display and analytics tools to provide in-depth assessment of the log contents. The work includes: Common interface formats for acquiring time-tagged text messages Conversion of common files for schedules, orbital events, and stored commands to the common log format Innovative displays to depict thousands of messages on a single display Structured English text queries against the log message data store, extensible to a more mature natural language query capability Goal of speech-to-text and text-to-speech additions to create a personal mission operations assistant to aid on-console operations. A wide variety of planned uses identified by the mission operations teams will be discussed.

events↗

NASA NTRS2018

Flight Systems Integration & Test: Lessons Learned for Future Success

This paper offers a comprehensive view of flight system integration and test (I&T) lessons learned related to mishaps and close calls, focusing on what can be done to improve the I&T process to avoid recurrence. Specific areas within the realm of I&T that are covered in this paper include: I&T team communication and training; design of flight and ground systems for I&T; planning and scheduling; configuration management and process documentation; ground support equipment and tools; cleanrooms and contamination; mechanical integration, handling, and deployments; electrical integration and electrostatic discharge; functional testing and troubleshooting; environmental testing and facilities; and launch site operations. To illustrate "real-world" lessons learned for I&T, examples from throughout the history of the U.S. space program are presented. Also presented are some best practices for I&T that can help mitigate mishaps and close calls on the ground or during flight.

Integration & Test↗

NASA NTRS1996

Atmospheric Visibility Monitoring (AVM) Program

The objective of the AVM Program is to obtain atmospheric transmission statistics data to support optical communications. The AVM Program is an autonomouse system that measures ground intensity of stars through different filters. The fully autonomouse systems collect atmospheric visibility data from three sites. A database of visibility data is being created to easily extract atmospheric transmission statistics information. This presentation describes the Program, the sites chosen, and the data obtained.

optical↗

NASA NTRS2023

Control and Non-Payload Communications Generation 7 Prototype Radio Flight Test Report

This report presents a description and test results of a seventh-generation prototype radio developed for Control and Non-Payload Communications (CNPC) between a ground-based pilot and an unmanned aircraft. Radios were prepared under a cooperative agreement between the NASA Glenn Research Center and Collins Aerospace (formerly Rockwell Collins, Inc.) and were used to support the development and validation of air-to-ground CNPC radio system standards. The CNPC radios operated in the 5,030- to 5,091-MHz frequency range. This report describes radio waveforms, laboratory testing, flight test systems, and flight test results.

Control and Non-Payload Communications↗

DOE OSTI2015

GLC_Exec v. 1.2.1

Launching a rocket involves a controlled transition of the rocket subsystems from a quiescent state to the launch state (i.e., lift-off). In order to launch safely, with confidence that the rocket will successfully complete its mission, the state-of-health for all rocket subsystems and critical ground support equipment must be closely monitored throughout the launch process. This is accomplished by the ground support engineers using mission-specific ground support equipment. A subset of the GSE, the Remote Electrical Ground Interface System (REGIS), is located nearest the rocket to which it's connected via the Umbilical, a wiring harness providing power, sensor, and control lines. The REGIS also connects via Ethernet to the Ground Launch Computer (GLC).

Kilgore, Roger Martin↗

NASA NTRS2013

Develop a Model Component

During my internship at NASA, I was a model developer for Ground Support Equipment (GSE). The purpose of a model developer is to develop and unit test model component libraries (fluid, electrical, gas, etc.). The models are designed to simulate software for GSE (Ground Special Power, Crew Access Arm, Cryo, Fire and Leak Detection System, Environmental Control System (ECS), etc. ~.) before they are implemented into hardware. These models support verifying local control and remote software for End-Item Software Under Test (SUT). The model simulates the physical behavior (function, state, limits and 110) of each end-item and it's dependencies as defined in the Subsystem Interface Table, Software Requirements & Design Specification (SRDS), Ground Integrated Schematic (GIS), and System Mechanical Schematic.(SMS). The software of each specific model component is simulated through MATLAB's Simulink program. The intensiv~ model development life cycle is a.s follows: Identify source documents; identify model scope; update schedule; preliminary design review; develop model requirements; update model.. scope; update schedule; detailed design review; create/modify library component; implement library components reference; implement subsystem components; develop a test script; run the test script; develop users guide; send model out for peer review; the model is sent out for verific~tionlvalidation; if there is empirical data, a validation data package is generated; if there is not empirical data, a verification package is generated; the test results are then reviewed; and finally, the user. requests accreditation, and a statement of accreditation is prepared. Once each component model is reviewed and approved, they are intertwined together into one integrated model. This integrated model is then tested itself, through a test script and autotest, so that it can be concluded that all models work conjointly, for a single purpose. The component I was assigned, specifically, was a fluid component, a discrete pressure switch. The switch takes a fluid pressure input, and if the pressure is greater than a designated cutoff pressure, the switch would stop fluid flow.

Ensey, Tyler S.↗

NASA NTRS1989

Aeronautical mobile TDMA/MCTDMA system

A multiple carrier Time Division Multiple Access (TDMA) system capable of supporting voice, stream data, and packet data traffic between aircraft and ground terminals is presented. Demand assignment permits efficient resource sharing for voice and stream data. The bandwidth efficiency of uncoded A Quadrature Phase Shift Keying (AQPSK) is 1 bps/Hz. High time efficiency (approximately equals 83 percent) is achieved through the use of symbol synchronous TDMA. Demodulation is achieved without loop hang-up while requiring only a 16 symbol preamble each burst. A concatenated coding system provides reliable transmission under multipath conditions.

Magill, Thomas↗

NASA NTRS1988

Telescience, an operational approach to science investigation

The NASA Science and Applications Information System, which is based on telescience and must provide remote interaction between information system services in space and on the ground, is discussed. An infrastructure of networked facilities and institutionally provided support services is being developed. The technologies involved with providing telescience capability are examined, including automated data management services, new data acquisition systems, user support environment for system access, and the capability to access heterogeneous data bases and computational facilities from remote locations.

Weiss, James R.↗

NASA NTRS1994

Max 1991 and beyond

Max '91, a coordinated, broad based observational program, was designed to help maximize the scientific return of solar activity studies. Max '91 benefited from the support of the NOAA space environment laboratory. An important source that increases solar ground based support observations is the solar observing optical network (SOON) solar patrol on tape (SOONSPOT) solar image archival system which has started operations. The past means and the future plans for ground based coordination and communications of Max '91 are summarized. The current status and the future developments of SOONSPOT are presented.

Kiplinger, Alan L.↗

NASA NTRS2003

Industry Support

NASA Glenn Research Center (GRC) is responsible for the Advanced Communications for Air Traffic Management (AC/ATM) Project, a sub-element task of the Advanced Air Transportation Technologies (AATT) Project of the NASA Aviation System Capacity Program (ASC). The AC/ATM Project is developing new communications technologies and tools that will improve throughput in the U.S. Air Traffic Control System. The goal of the AC/ATM Project is to enable a communications infrastructure providing the capacity, efficiency, and flexibility necessary to realize benefits of the future mature Free-Flight environment. The capabilities and scope of communications technologies needed to accomplish this goal depend on characteristics of the future Free-Flight environment. There are many operational concepts being proposed for a future ATM system to enable user flexibility and efficiency. GRC s focus is on developing new technologies and techniques to support the digital communication of information involving airborne and ground-based users. However, the technologies and techniques must be integrated with the systems and services that industry and the Federal Aviation Administration (FAA) are developing. Thus, GRC needs to monitor and provide input to the various industry and FAA organizations and committees that are specifying new systems and services. Adoption of technologies by the FAA is partially dependent on acceptance of the technology by the aviation community. The commercial aviation community in particular would like to adopt technologies that can be used throughout the world. As a result, the adoption of common or at least compatible technologies by European countries is a key factor in getting commitments to those technologies by the US aviation community. GRC desires to keep informed of European activities that relate to aviation communication technologies, particularly those that are being supported by Eurocontrol.

Source record↗

NASA NTRS1977

DSN telemetry system, Mark 3-77

A description is given of the DSN Telemetry System, Mark3-77, which is used to support multiple deep space missions. Telemetry functions performed by the Deep Space Stations, Ground Communications Facility, and the Network Operations Control Center are defined. Recent improvements to the system and planned upgrades are described.

Gatz, E. C.↗

NASA NTRS1995

Analyzing rocket plume spectral data with neural networks

The Optical Plume Anomaly Detection (OPAD) system is under development to provide early-warning failure detection in support of ground-level testing of the Space Shuttle Main Engine (SSME). Failure detection is to be achieved through the acquisition of spectrally resolved plume emissions and subsequent identification of abnormal levels indicative of engine corrosion or component failure. Two computer codes (one linear and the other non-linear) are used by the OPAD system to iteratively determine specific element concentrations in the SSME plume, given emission intensity and wavelength information. Since this analysis is extremely labor intensive, a study was initiated to develop neural networks that would model the 'inverse' of these computer codes. Optimally connected feed-forward networks with imperceptible prediction error have been developed for each element modeled by the linear code, SPECTRA4. Radial basis function networks were developed for the non-linear code, SPECTRA5, and predict combustion temperature in addition to element concentrations.

Whitaker, Kevin W.↗

NASA NTRS2024

Crew Health and Performance Integrated Data Architecture (CHP-IDA) Project

BACKGROUND: Future Human Exploration missions introduce a new paradigm as crews move further from the resupply and near real-time ground support typical of Low Earth Orbit missions today. Without immediate support from ground-based personnel, exploration crews will be more reliant on inflight data and technology to respond to emergencies and anomalies. A data architecture to support a new generation of technologies, employing advanced analytical and predictive modeling techniques, is needed to enable crew autonomy. OVERVIEW: The Crew Health and Performance Integrated Data Architecture (CHP-IDA) project funded by NASA’s Exploration Medical Integrated Product Team (XMIPT) is laying a foundation for future in-flight informatics by providing a back-end architecture for collecting, storing, and integrating multiple sources of data generated by and around the crew. CHP-IDA provides a platform for common data models and Application Programming Interfaces to access, integrate, process, and display CHP data (e.g., environmental, exercise, medical, sleep, performance, etc.). This will facilitate the increased situation awareness and decision support required by the crew and remote support of exploration missions. This presentation will describe the currently ongoing effort to develop and evaluate a path-to-flight concept of the CHP-IDA software and its core capabilities. Current integrations will be discussed, including analytics for Extravehicular Activity metabolic rate and data ingestion from a multi-functional integrated medical device. The presentation will also provide examples of scenarios used to demonstrate the CHP-IDA through human-in-the-loop test bed activities as well as examples of appropriate system performance metrics. DISCUSSION: Today, in-flight data is often siloed, unsynchronized, and largely inaccessible in real time. Many data sets require manual entry and/or data transfer between vehicles and the ground. These issues contribute to risks in supporting exploration medical capabilities. The CHP-IDA is a back-end data system providing core capabilities needed for timely and meaningful data insights across CHP domains to crew and remote personnel to enable increased crew autonomy. Future work includes collaboration with additional CHP domains, new technology integrations, and further demonstrations of the IDA within different vehicle and communication latency contexts. LEARNING OBJECTIVES 1. The audience will understand that the CHP-IDA is a back-end system, providing a platform to facilitate access, promote decision tools, and provide meaningful insights to crew and to remote stakeholders during exploration missions. 2. The audience will gain insight into human-centered research and activities used to discover CHP domain data needs and pain points and how this information is used to guide development of the IDA.

Exploration↗

NASA NTRSDate not supplied

Human-Autonomy Teaming Assistant to Support Small Uncrewed Aircraft Systems for Wildland Firefighting Operations

An exploratory human-in-the-loop simulation was conducted to investigate and characterize a Human-Autonomy Teaming (HAT) Assistant to support a remote operator of multiple small Uncrewed Aircraft Systems (sUAS) using a ground control station (GCS) in the context of a wildland fire surveillance mission. Operator performance using the GCS with the HAT Assistant (Assisted Mode) was compared to operator performance using the GCS without the HAT Assistant (Unassisted Mode) during two types of contingency-event scenarios (Low and High Complexity). In the Assisted Mode, the HAT Assistant provided updates to the level of risk to the mission along with recommendations for risk mitigation, which were not provided in the Unassisted Mode. No significant differences in objective performance and subjective ratings of workload, situation awareness, and trust in automation between the Assisted and Unassisted Modes were detected, however there were indications that participants preferred the Assisted GCS over the Unassisted GCS and directions for further development were explored. Additional work is necessary to further refine the HAT Assistant and better characterize its effects on remote operator performance while managing multiple sUAS assets. Future work is recommended to optimize the implementation of an assistant to support operator performance during different missions and across vehicle classes

Human-Autonomy Teaming↗