Engineering Papers⌕ Search

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.

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

At least 1,099 records · Page 61

Making adaptable systems work for mission operations: A case study

The Advanced Multimission Operations System (AMMOS) at NASA's Jet Propulsion Laboratory is based on a highly adaptable multimission ground data system (MGDS) for mission operations. The goal for MGDS is to support current flight project science and engineering personnel and to meet the demands of future missions while reducing associated operations and software development costs. MGDS has become a powerful and flexible mission operations system by using a network of heterogeneous workstations, emerging open system standards, and selecting an adaptable tools-based architecture. Challenges in developing adaptable systems for mission operations and the benefits of this approach are described.

Holder, Barbara E.↗

SIMSAT: An object oriented architecture for real-time satellite simulation

Real-time satellite simulators are vital tools in the support of satellite missions. They are used in the testing of ground control systems, the training of operators, the validation of operational procedures, and the development of contingency plans. The simulators must provide high-fidelity modeling of the satellite, which requires detailed system information, much of which is not available until relatively near launch. The short time-scales and resulting high productivity required of such simulator developments culminates in the need for a reusable infrastructure which can be used as a basis for each simulator. This paper describes a major new simulation infrastructure package, the Software Infrastructure for Modelling Satellites (SIMSAT). It outlines the object oriented design methodology used, describes the resulting design, and discusses the advantages and disadvantages experienced in applying the methodology.

Williams, Adam P.↗

Multi-spacecraft coherent Doppler and ranging for interplanetary-navigation

Future plans for planetary exploration currently include using multiple spacecraft to simultaneously explore one planet. This never before encountered situation places new demands on tracking systems used to support navigation. One possible solution to the problem of heavy ground resource conflicts is the use of multispacecraft coherent radio metric data, also known as, bent-pipe data. Analysis of the information content of these data types show that the information content of multi-spacecraft Doppler is dependent only on the frequency of the final downlink leg and is independent of the frequencies used on other legs. Numerical analysis shows that coherent bent-pipe data can provide significantly better capability to estimate the location of a lander on the surface of Mars than can direct lander to Earth radio metric data. However, this is complicated by difficulties in separating the effect of a lander position error from that of an orbiter position error for single passes of data.

Pollmeier, Vincent M.↗

Geographic Freedom

Kennedy Space Center's need to conduct real-time monitoring of Space Shuttle operations led to the development of Netlander Inc.'s JTouch system. The technology behind JTouch allows engineers to view Space Shuttle and ground support data from any desktop computer using a web browser. Companies can make use of JTouch to better monitor locations scattered around the world, increasing decision-making speed and reducing travel costs for site visits.

Source record↗

Beyond the Prototype: The Design Evolution of a Deployed AI System

Our previous experiences with deployed intelligent control agents for NASA advanced life support systems (Schreckenghost et al., 2002) inspired us to develop the Distributed Collaboration and Interaction (DCI) system to help humans and mostly-autonomous software agents work together. We discovered many unaddressed needs for human interaction with control agents that operate continuously over months to years to monitor and perform process control for regenerative life support systems. These systems recover usable water or air from the waste products created by biological systems over time. Through the DCI project, we have addressed the needs for interaction between humans and autonomous control systems. This paper describes the software engineering aspects of our experiences, first, in designing and developing a prototype of the DCI system, and later, in adjusting the implementation to make the leap from initial prototype to a system ready to be applied under varying circumstances to meet different needs. The details in the paper focus primarily on the second stage of development. The DCI system is currently deployed, operating 24/7, to assist humans to interact with an advanced Water Recovery System (WRS). In addition, we have demonstrated an application of DCI to support ground personnel in mission support roles.

Martin, C.↗

Beyond the Prototype: The Design Evolution of a Deployed AI System

Our previous experiences with deployed intelligent control agents for NASA advanced life support systems (Schreckenghost et al., 2002) inspired us to develop the Distributed Collaboration and Interaction (DCI) system to help humans and mostly-autonomous software agents work together. We discovered many unaddressed needs for human interaction with control agents that operate continuously over months to years to monitor and perform process control for regenerative life support systems. These systems recover usable water or air from the waste products created by biological systems over time. Through the DCI project, we have addressed the needs for interaction between humans and autonomous control systems. This paper describes the software engineering aspects of our experiences, first, in designing and developing a prototype of the DCI system, and later, in adjusting the implementation to make the leap from initial prototype to a system ready to be applied under varying circumstances to meet different needs. The details in the paper focus primarily on the second stage of development. The DCI system is currently deployed, operating 24/7, to assist humans to interact with an advanced Water Recovery System (WRS). In addition, we have demonstrated an application of DCI to support ground personnel in mission support roles.

Martin, Cheryl↗

NASA's Cryogenic Fluid Management Technology Project

The Cryogenic Fluid Management (CFM) Project's primary objective is to develop storage, transfer, and handling technologies for cryogens that will support the enabling of high performance cryogenic propulsion systems, lunar surface systems and economical ground operations. Such technologies can significantly reduce propellant launch mass and required on-orbit margins, reduce or even eliminate propellant tank fluid boil-off losses for long term missions, and simplify vehicle operations. This paper will present the status of the specific technologies that the CFM Project is developing. The two main areas of concentration are analysis models development and CFM hardware development. The project develops analysis tools and models based on thermodynamics, hydrodynamics, and existing flight/test data. These tools assist in the development of pressure/thermal control devices (such as the Thermodynamic Vent System (TVS), and Multi-layer insulation); with the ultimate goal being to develop a mature set of tools and models that can characterize the performance of the pressure/thermal control devices incorporated in the design of an entire CFM system with minimal cryogen loss. The project does hardware development and testing to verify our understanding of the physical principles involved, and to validate the performance of CFM components, subsystems and systems. This database provides information to anchor our analytical models. This paper describes some of the current activities of the NASA's Cryogenic Fluid Management Project.

Tramel, Terri L.↗

Analysis of Flight Management System Predictions of Idle-Thrust Descents

To enable arriving aircraft to fly optimized descents computed by the flight management system (FMS) in congested airspace, ground automation must accurately predict descent trajectories. To support development of the predictor and its uncertainty models, descents from cruise to the meter fix were executed using vertical navigation in a B737-700 simulator and a B777-200 simulator, both with commercial FMSs. For both aircraft types, the FMS computed the intended descent path for a specified speed profile assuming idle thrust after top of descent (TOD), and then it controlled the avionics without human intervention. The test matrix varied aircraft weight, descent speed, and wind conditions. The first analysis in this paper determined the effect of the test matrix parameters on the FMS computation of TOD location, and it compared the results to those for the current ground predictor in the Efficient Descent Advisor (EDA). The second analysis was similar but considered the time to fly a specified distance to the meter fix. The effects of the test matrix variables together with the accuracy requirements for the predictor will determine the allowable error for the predictor inputs. For the B737, the EDA prediction of meter fix crossing time agreed well with the FMS; but its prediction of TOD location probably was not sufficiently accurate to enable idle-thrust descents in congested airspace, even though the FMS and EDA gave similar shapes for TOD location as a function of the test matrix variables. For the B777, the FMS and EDA gave different shapes for the TOD location function, and the EDA prediction of the TOD location is not accurate enough to fully enable the concept. Furthermore, the differences between the FMS and EDA predictions of meter fix crossing time for the B777 indicated that at least one of them was not sufficiently accurate.

Stell, Laurel↗

Predictability of Top of Descent Location for Operational Idle-Thrust Descents

To enable arriving aircraft to fly optimized descents computed by the flight management system (FMS) in congested airspace, ground automation must accurately predict descent trajectories. To support development of the trajectory predictor and its uncertainty models, commercial flights executed idle-thrust descents at a specified descent speed, and the recorded data included the specified descent speed profile, aircraft weight, and the winds entered into the FMS as well as the radar data. The FMS computed the intended descent path assuming idle thrust after top of descent (TOD), and the controllers and pilots then endeavored to allow the FMS to fly the descent to the meter fix with minimal human intervention. The horizontal flight path, cruise and meter fix altitudes, and actual TOD location were extracted from the radar data. Using approximately 70 descents each in Boeing 757 and Airbus 319/320 aircraft, multiple regression estimated TOD location as a linear function of the available predictive factors. The cruise and meter fix altitudes, descent speed, and wind clearly improve goodness of fit. The aircraft weight improves fit for the Airbus descents but not for the B757. Except for a few statistical outliers, the residuals have absolute value less than 5 nmi. Thus, these predictive factors adequately explain the TOD location, which indicates the data do not include excessive noise.

Stell, Laurel L.↗

Flight Management System Execution of Idle-Thrust Descents in Operations

To enable arriving aircraft to fly optimized descents computed by the flight management system (FMS) in congested airspace, ground automation must accurately predict descent trajectories. To support development of the trajectory predictor and its error models, commercial flights executed idle-thrust descents, and the recorded data includes the target speed profile and FMS intent trajectories. The FMS computes the intended descent path assuming idle thrust after top of descent (TOD), and any intervention by the controllers that alters the FMS execution of the descent is recorded so that such flights are discarded from the analysis. The horizontal flight path, cruise and meter fix altitudes, and actual TOD location are extracted from the radar data. Using more than 60 descents in Boeing 777 aircraft, the actual speeds are compared to the intended descent speed profile. In addition, three aspects of the accuracy of the FMS intent trajectory are analyzed: the meter fix crossing time, the TOD location, and the altitude at the meter fix. The actual TOD location is within 5 nmi of the intent location for over 95% of the descents. Roughly 90% of the time, the airspeed is within 0.01 of the target Mach number and within 10 KCAS of the target descent CAS, but the meter fix crossing time is only within 50 sec of the time computed by the FMS. Overall, the aircraft seem to be executing the descents as intended by the designers of the onboard automation.

Stell, Laurel L.↗

Analysis of the March 30, 2011 Hail Event at Shuttle Launch Pad 39A

The Kennedy Space Center (KSC) Hail Monitor System, a joint effort of the NASA KSC Physics Lab and the KSC Engineering Services Contract (ESC) Applied Technology Lab, was first deployed for operational testing in the fall of 2006. Volunteers from the Community Collaborative Rain, Hail, and Snow Network (CoCoRaHS) in conjunction with Colorado State University have been instrumental in validation testing using duplicate hail monitor systems at sites in the hail prone high plains of Colorado. The KSC Hail Monitor System (HMS), consisting of three stations positioned approximately 500 ft from the launch pad and forming an approximate equilateral triangle, as shown in Figure 1, was first deployed to Pad 39B for support of STS-115. Two months later, the HMS was deployed to Pad 39A for support of STS-116. During support of STS-117 in late February 2007, an unusually intense (for Florida standards) hail event occurred in the immediate vicinity of the exposed space shuttle and launch pad. Hail data of this event was collected by the HMS and analyzed. Support of STS-118 revealed another important application of the hail monitor system. Ground Instrumentation personnel check the hail monitors daily when a vehicle is on the launch pad, with special attention after any storm suspected of containing hail. If no hail is recorded by the HMS, the vehicle and pad inspection team has no need to conduct a thorough inspection of the vehicle immediately following a storm. On the afternoon of July 13, 2007, hail on the ground was reported by observers at the Vertical Assembly Building (VAB) and Launch Control Center (LCC), about three miles west of Pad 39A, as well as at several other locations at KSC. The HMS showed no impact detections, indicating that the shuttle had not been damaged by any of the numerous hail events which occurred on that day.

Lane, John E.↗

Hail Disrometer Array for Launch Systems Support

Prior to launch, the space shuttle might be described as a very large thermos bottle containing substantial quantities of cryogenic fuels. Because thermal insulation is a critical design requirement, the external wall of the launch vehicle fuel tank is covered with an insulating foam layer. This foam is fragile and can be damaged by very minor impacts, such as that from small- to medium-size hail, which may go unnoticed. In May 1999, hail damage to the top of the External Tank (ET) of STS-96 required a rollback from the launch pad to the Vehicle Assembly Building (VAB) for repair of the insulating foam. Because of the potential for hail damage to the ET while exposed to the weather, a vigilant hail sentry system using impact transducers was developed as a hail damage warning system and to record and quantify hail events. The Kennedy Space Center (KSC) Hail Monitor System, a joint effort of the NASA and University Affiliated Spaceport Technology Development Contract (USTDC) Physics Labs, was first deployed for operational testing in the fall of 2006. Volunteers from the Community Collaborative Rain. Hail, and Snow Network (CoCoRaHS) in conjunction with Colorado State University were and continue to be active in testing duplicate hail monitor systems at sites in the hail prone high plains of Colorado. The KSC Hail Monitor System (HMS), consisting of three stations positioned approximately 500 ft from the launch pad and forming an approximate equilateral triangle (see Figure 1), was deployed to Pad 39B for support of STS-115. Two months later, the HMS was deployed to Pad 39A for support of STS-116. During support of STS-117 in late February 2007, an unusual hail event occurred in the immediate vicinity of the exposed space shuttle and launch pad. Hail data of this event was collected by the HMS and analyzed. Support of STS-118 revealed another important application of the hail monitor system. Ground Instrumentation personnel check the hail monitors daily when a vehicle is on the launch pad, with special attention after any storm suspected of containing hail. If no hail is recorded by the HMS, the vehicle and pad inspection team has no need to conduct a thorough inspection of the vehicle immediately following a storm. On the afternoon of July 13, 2007, hail on the ground was reported by observers at the VAB, about three miles west of Pad 39A, as well as at several other locations around Kennedy Space Center. The HMS showed no impact detections, indicating that the shuttle had not been damaged by any of the numerous hail events which occurred that day.

Lane, John E.↗

Multi-Spacecraft Coherent Doppler and Ranging for Interplanetary Navigation

Future plans for planetary exploration currently include using multiple spacecraft to simultaneously explore one planet. This never before encountered situation places new demands on tracking systems used to support navigation. One possible solution to the problem of heavy ground resource conflicts is the use of multi-spacecraft coherent radio metric data, also known as bent-pipe data.

multi-spacecraft↗

Recipe for Success: Digital Viewables

The Engineering Services Contract (ESC) and Information Management Communication Support contract (IMCS) at Kennedy Space Center (KSC) provide services to NASA in respect to flight and ground systems design and development. These groups provides the necessary tools, aid, and best practice methodologies required for efficient, optimized design and process development. The team is responsible for configuring and implementing systems, software, along with training, documentation, and administering standards. The team supports over 200 engineers and design specialists with the use of Windchill, Creo Parametric, NX, AutoCAD, and a variety of other design and analysis tools.

design and process development↗

Preparation for an Earth Independent Medical Operations Demonstration using the Tempus ALS™ Medical Device

NASA’s exploration-class missions have severe resource constraints, long return trip durations, significant communication delays and limited resupply opportunities. Validation on the International Space Station (ISS) of medical devices that fit within Earth-Independent Medical Operations (EIMO) systems is a necessary preparation step. Key features of an EIMO medical system include: 1) technologies that support the prevention, diagnosis, and treatment of spaceflight medical events; 2) components that meet mass, volume, power and crew time/training constraints; 3) consideration of the medical skill level of the astronaut caregiver; 4) collection, storage and analysis of medical data within a central data architecture; and 5) incorporation of appropriate guidance and support tools that allow crew autonomy. The Human Research Program’s (HRP) Exploration Medical Capability (ExMC) Element and the Exploration Medical Integrated Product Team (XM-IPT) are planning an ISS technology demonstration to determine the feasibility of including a multifunctional medical device into an EIMO medical system. Demonstration Preparations: The Tempus ALS (Remote Diagnostic Technologies, Ltd., Philips Corp., Farnborough, UK) is a commercial-off-the-shelf medical device, with United States Food and Drug Administration clearance and is Conformité Européene marked in Europe. Several thousand units have been sold and are successfully operating in pre-hospital and in remote settings, such as by European Space Agency (ESA) flight surgeons and some of NASA’s commercial partners during post-flight medical operations. The Tempus ALS provides vital sign measurements such as blood pressure, electrocardiograms, heart rate, end tidal CO2, respiration rate, pulse oximetry and temperature. The device has ultrasound imaging and video laryngoscopy capabilities and has automatic or manual defibrillation modes for treating cardiac arrhythmias. It includes procedural guidance capabilities to assist in the collection of the vital sign measurements and it has various data transmission and report generation features. NASA’s HRP ExMC and XM-IPT are partnering with the ESA to demonstrate the Tempus ALS on ISS, with ESA manifesting the Tempus ALS and its accessories. ESA will compare performance of periodic health status exams and medical contingency drills performed nominally and with the Tempus ALS. NASA’s EIMO demonstration will include the use of Tempus ALS to diagnose a complaint of abdominal pain under increasingly independent circumstances. The caregiver must assess the present illness, collect vital sign measurements, and perform an abdominal ultrasound, under one of three communication situations, including real-time, with a several second delay and with a delay on the order of minutes. Expected Outcomes: Information will be gained about the feasibility, benefits, and challenges of using a multifunctional, all-in-one, medical device for medical diagnosis instead of separate devices with singular functionalities. Information will also be collected about performance differences as communication delays increase and available ground support decreases. Gaining this understanding will allow for further development of exploration medical system capabilities which takes the EIMO construct into consideration.

Beth Lewandowski↗

Tracking and data relay satellite system configuration and tradeoff study. Volume 7: Telecommunications system summary, part 1

The baseline Tracking and Data Relay Satellite telecommunication system is described. The configurations of the user spacecraft terminal and the ground based terminal are illustrated. The system service and performance summary is developed to show the link support, modes of operation, and link performance to the low data rate and medium data rate user spacecraft. The link budget calculation is included to show a typical computation for each space-to-space and space-to-ground link with the assumptions used in each calculation.

Hill, T. E.↗

Data storage systems technology for the Space Station era

The paper presents the results of an internal NASA study to determine if economically feasible data storage solutions are likely to be available to support the ground data transport segment of the Space Station mission. An internal NASA effort to prototype a portion of the required ground data processing system is outlined. It is concluded that the requirements for all ground data storage functions can be met with commercial disk and tape drives assuming conservative technology improvements and that, to meet Space Station data rates with commercial technology, the data will have to be distributed over multiple devices operating in parallel and in a sustained maximum throughput mode.

Dalton, John↗

Operation Evaluation of the VEGGIE Food Production System in the Habitat Demonstration Unit

The 2010 Desert Research and Technology Studies (DRATS) of the VEGGIE Food Production System in the Habitat Demonstration Unit (HDU) Pressurized Excursion Module (PEM) was the first operational evaluation of salad crop production technology in a NASA analog test. A systematic evaluation of rooting media and nutrient delivery systems were evaluated for three lettuce cultivars that have shown promise as candidates for a surface based food production system. The VEGGIE nutrient delivery system worked well, was able to be maintained by multiple operators with a minimum of training, and supported excellent lettuce growth for the duration of the test. A Hazard Analysis and Critical Control Point (HACCP) evaluation was performed using ProSantm as sanitation agent prior to consumption was approved, and the crew was allowed to consume the lettuce grown using the VEGGIE light cap and gravity based nutrient delivery system at the completion of the 14-day DRAT field test. The DRAT field test validated the crew operations; Growth of all lettuce cultivars was excellent. The operational DRAT field testing in the HDU identified light quality issues related to morphology and pigment development that will need to be addressed through additional testing. Feedback from the crew, ground support personnel, and human factors leads was uniformly positive on the psychological value of having the crop production system in the excursion module. A number of areas have been identified for future work, to minimize the "footprint" of the Food Production system through creative use of unused wall and floor space in the unit.

Stutte, Gary W.↗