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 721 records · Page 40

An Interoperability Concept for Detect and Avoid and Collision Avoidance Systems: Results from a Human-In-The-Loop Simulation

The integration of Unmanned Aircraft Systems (UAS) into the National Airspace System (NAS) poses a variety of technical challenges to UAS developers and aviation regulators. In response to growing demand for access to civil airspace in the United States, the Federal Aviation Administration (FAA) has produced a roadmap identifying key areas requiring further research and development. One such technical challenge is the development of a "detect and avoid" system (DAA) capable of providing a means of compliance with the "see and avoid" requirement in manned aviation. The purpose of the DAA system is to support the pilot, situated at a ground control station (GCS), in maintaining "DAA well clear" of nearby aircraft through the use of GCS displays and alerts. In addition to its primary function of aiding the pilot in maintaining DAA well clear, the DAA system must also safely interoperate with existing NAS systems and operations, such as the airspace management procedures of air traffic controllers (ATC) and Collision Avoidance (CA) systems currently in use by manned aircraft, namely the Traffic Alert and Collision Avoidance System (TCAS II). It is anticipated that many UAS architectures will integrate both a DAA system and a TCAS II. It is therefore necessary to explicitly study the integration of DAA and TCAS II alerting structures and maneuver guidance formats to ensure that pilots understand the appropriate type and urgency of their response to the various alerts. This paper presents a concept of interoperability for the two systems. The concept was developed with the goal of avoiding any negative impact on the performance level of TCAS II while retaining a DAA system that still effectively enables pilots to maintain DAA well clear. The interoperability concept described in the paper focuses primarily on facilitating the transition from a late-stage DAA encounter (where a loss of DAA well clear is imminent) to a TCAS II Corrective Resolution Advisory (RA), which requires pilot compliance within five seconds of its issuance. The interoperability concept was presented to 10 participants (6 active UAS pilots and 4 active commercial pilots) in a medium-fidelity, human-in-the-loop simulation designed to stress different aspects of the DAA and TCAS II systems. Pilots' ability to maintain separation, their rate of compliance and response times using the interoperability concept are reported. Results indicated that pilots exhibited comprehension of, and appropriate prioritization within, the DAA-TCAS II combined alert structure. Pilots demonstrated a high rate of compliance with TCAS II RAs and were also seen to respond to corrective RAs within the five second requirement established for manned aircraft. The DAA system presented under test was also shown to be effective in supporting pilots' ability to maintain DAA well clear in the overwhelming majority of cases in which pilots had sufficient time to respond.

Rorie, R. Conrad↗

Autonomous Satellite Command and Control through the World Wide Web: Phase 3

NASA's New Millenium Program (NMP) has identified a variety of revolutionary technologies that will support orders of magnitude improvements in the capabilities of spacecraft missions. This program's Autonomy team has focused on science and engineering automation technologies. In doing so, it has established a clear development roadmap specifying the experiments and demonstrations required to mature these technologies. The primary developmental thrusts of this roadmap are in the areas of remote agents, PI/operator interface, planning/scheduling fault management, and smart execution architectures. Phases 1 and 2 of the ASSET Project (previously known as the WebSat project) have focused on establishing World Wide Web-based commanding and telemetry services as an advanced means of interfacing a spacecraft system with the PI and operators. Current automated capabilities include Web-based command submission, limited contact scheduling, command list generation and transfer to the ground station, spacecraft support for demonstrations experiments, data transfer from the ground station back to the ASSET system, data archiving, and Web-based telemetry distribution. Phase 2 was finished in December 1996. During January-December 1997 work was commenced on Phase 3 of the ASSET Project. Phase 3 is the subject of this report. This phase permitted SSDL and its project partners to expand the ASSET system in a variety of ways. These added capabilities included the advancement of ground station capabilities, the adaptation of spacecraft on-board software, and the expansion of capabilities of the ASSET management algorithms. Specific goals of Phase 3 were: (1) Extend Web-based goal-level commanding for both the payload PI and the spacecraft engineer; (2) Support prioritized handling of multiple PIs as well as associated payload experimenters; (3) Expand the number and types of experiments supported by the ASSET system and its associated spacecraft; (4) Implement more advanced resource management, modeling and fault management capabilities that integrate the space and ground segments of the space system hardware; (5) Implement a beacon monitoring test; (6) Implement an experimental blackboard controller for space system management; (7) Further define typical ground station developments required for Internet-based remote control and for full system automation of the PI-to-spacecraft link. Each of those goals is examined in the next section. Significant sections of this report were also published as a conference paper.

Cantwell, Brian↗

Evaluation of Grounding Impedance of a Complex Lightning Protective System Using Earth Ground Clamp Measurements and ATP Modeling

A new Lightning Protection System (LPS) was designed and built at Launch Complex 39B (LC39B), at the Kennedy Space Center (KSC), Florida, which consists of a catenary wire system (at a height of about 181 meters above ground level) supported by three insulators installed atop three towers in a triangular configuration. A total of nine downconductors (each about 250 meters long, on average) are connected to the catenary wire system. Each of the nine downconductors is connected to a 7.62-meter radius circular counterpoise conductor with six equally spaced 6-meter long vertical grounding rods. Grounding requirements at LC39B call for all underground and above ground metallic piping, enclosures, raceways, and cable trays, within 7.62 meters of the counterpoise, to be bounded to the counterpoise, which results in a complex interconnected grounding system, given the many metallic piping, raceways, and cable trays that run in multiple direction around LC39B. The complexity of this grounding system makes the fall of potential method, which uses multiple metallic rods or stakes, unsuitable for measuring the grounding impedances of the downconductors. To calculate the downconductors grounding impedance, an Earth Ground Clamp (a stakeless grounding resistance measuring device) and a LPS Alternative Transient Program (ATP) model are used. The Earth Ground Clamp is used to measure the loop impedance plus the grounding impedance of each downconductor and the ATP model is used to calculate the loop impedance of each downconductor circuit. The grounding impedance of the downconductors is then calculated by subtracting the ATP calculated loop impedances from the Earth Ground Clamp measurements.

Mata, Carlos T.↗

Exploration Medical Capability System Engineering Overview

Deep Space Gateway and Transport missions will change the way NASA currently practices medicine. The missions will require more autonomous capability compared to current low Earth orbit operations. For the medical system, lack of consumable resupply, evacuation opportunities, and real-time ground support are key drivers toward greater autonomy. Recognition of the limited mission and vehicle resources available to carry out exploration missions motivates the Exploration Medical Capability (ExMC) Element's approach to enabling the necessary autonomy. The ExMC Systems Engineering team's mission is to "Define, develop, validate, and manage the technical system design needed to implement exploration medical capabilities for Mars and test the design in a progression of proving grounds." The Element's work must integrate with the overall exploration mission and vehicle design efforts to successfully provide exploration medical capabilities. ExMC is using Model-Based System Engineering (MBSE) to accomplish its integrative goals. The MBSE approach to medical system design offers a paradigm shift toward greater integration between vehicle and the medical system, and directly supports the transition of Earth-reliant ISS operations to the Earth-independent operations envisioned for Mars. This talk will discuss how ExMC is using MBSE to define operational needs, decompose requirements and architecture, and identify medical capabilities needed to support human exploration. How MBSE is being used to integrate across disciplines and NASA Centers will also be described. The medical system being discussed in this talk is one system within larger habitat systems. Data generated within the medical system will be inputs to other systems and vice versa. This talk will also describe the next steps in model development that include: modeling the different systems that comprise the larger system and interact with the medical system, understanding how the various systems work together, and developing tools to support trade studies.

Mindock, J.↗

Exploration Medical Cap Ability System Engineering Overview

Deep Space Gateway and Transport missions will change the way NASA currently practices medicine. The missions will require more autonomous capability compared to current low Earth orbit operations. For the medical system, lack of consumable resupply, evacuation opportunities, and real-time ground support are key drivers toward greater autonomy. Recognition of the limited mission and vehicle resources available to carry out exploration missions motivates the Exploration Medical Capability (ExMC) Element's approach to enabling the necessary autonomy. The ExMC Systems Engineering team's mission is to "Define, develop, validate, and manage the technical system design needed to implement exploration medical capabilities for Mars and test the design in a progression of proving grounds." The Element's work must integrate with the overall exploration mission and vehicle design efforts to successfully provide exploration medical capabilities. ExMC is using Model-Based System Engineering (MBSE) to accomplish its integrative goals. The MBSE approach to medical system design offers a paradigm shift toward greater integration between vehicle and the medical system, and directly supports the transition of Earth-reliant ISS operations to the Earth-independent operations envisioned for Mars. This talk will discuss how ExMC is using MBSE to define operational needs, decompose requirements and architecture, and identify medical capabilities needed to support human exploration. How MBSE is being used to integrate across disciplines and NASA Centers will also be described. The medical system being discussed in this talk is one system within larger habitat systems. Data generated within the medical system will be inputs to other systems and vice versa. This talk will also describe the next steps in model development that include: modeling the different systems that comprise the larger system and interact with the medical system, understanding how the various systems work together, and developing tools to support trade studies.

McGuire, K.↗

Medical Data Architecture Project Status

The Medical Data Architecture (MDA) project supports the Exploration Medical Capability (ExMC) risk to minimize or reduce the risk of adverse health outcomes and decrements in performance due to in-flight medical capabilities on human exploration missions. To mitigate this risk, the ExMC MDA project addresses the technical limitations identified in ExMC Gap Med 07: We do not have the capability to comprehensively process medically-relevant information to support medical operations during exploration missions. This gap identifies that the current International Space Station (ISS) medical data management includes a combination of data collection and distribution methods that are minimally integrated with on-board medical devices and systems. Furthermore, there are variety of data sources and methods of data collection. For an exploration mission, the seamless management of such data will enable an increasingly autonomous crew than the current ISS paradigm. The MDA will develop capabilities that support automated data collection, and the necessary functionality and challenges in executing a self-contained medical system that approaches crew health care delivery without assistance from ground support. To attain this goal, the first year of the MDA project focused on reducing technical risk, developing documentation and instituting iterative development processes that established the basis for the first version of MDA software (or Test Bed 1). Test Bed 1 is based on a nominal operations scenario authored by the ExMC Element Scientist. This narrative was decomposed into a Concept of Operations that formed the basis for Test Bed 1 requirements. These requirements were successfully vetted through the MDA Test Bed 1 System Requirements Review, which permitted the MDA project to begin software code development and component integration. This paper highlights the MDA objectives, development processes, and accomplishments, and identifies the fiscal year 2017 milestones and deliverables in the upcoming year.

Data management↗

Exploration Medical Capability Systems Engineering Overview and Update

Long duration Lunar and Martian missions will change the way NASA currently practices medicine. The missions will require more autonomous capability compared to current low Earth orbit operations. For the medical system, lack of consumable resupply, evacuation opportunities, and real-time ground support are key drivers toward greater autonomy. Recognition of the limited mission and vehicle resources available to carry out exploration missions motivates the Exploration Medical Capability (ExMC) Element’s approach to enabling the necessary autonomy. The ExMC Systems Engineering (SE) team’s mission is to “Define, develop, validate, and manage the technical system design needed to implement exploration medical capabilities for Mars and test the design in a progression of proving grounds.” The Element’s work must integrate with the overall exploration mission and vehicle design efforts to successfully provide exploration medical capabilities. ExMC is using Model-Based System Engineering (MBSE) to accomplish its integrative goals. The MBSE approach to medical system design offers a paradigm shift toward greater integration between the vehicle and the medical system, and directly supports the transition of Earth-reliant ISS operations to the Earth-independent operations envisioned for Mars. This talk will provide a high-level overview of what the ExMC SE team has accomplished since the last IWS and what they are focusing on for the upcoming year.

Kerry McGuire↗

Advances in Orion's On-Orbit Guidance and Targeting System Architecture

NASA's manned spaceflight programs have a rich history of advancing onboard guidance and targeting technology. In order to support future missions, the guidance and targeting architecture for the Orion Multi-Purpose Crew Vehicle must be able to operate in complete autonomy, without any support from the ground. Orion's guidance and targeting system must be sufficiently flexible to easily adapt to a wide array of undecided future missions, yet also not cause an undue computational burden on the flight computer. This presents a unique design challenge from the perspective of both algorithm development and system architecture construction. The present work shows how Orion's guidance and targeting system addresses these challenges. On the algorithm side, the system advances the state-of-the-art by: (1) steering burns with a simple closed-loop guidance strategy based on Shuttle heritage, and (2) planning maneuvers with a cutting-edge two-level targeting routine. These algorithms are then placed into an architecture designed to leverage the advantages of each and ensure that they function in concert with one another. The resulting system is characterized by modularity and simplicity. As such, it is adaptable to the on-orbit phases of any future mission that Orion may attempt.

Scarritt, Sara K.↗

An Interoperability Concept for Detect and Avoid and Collision Avoidance Systems: Results from a Human-In-The-Loop Simulation

The integration of Unmanned Aircraft Systems (UAS) into the National Airspace System (NAS) poses a variety of technical challenges to UAS developers and aviation regulators. In response to growing demand for access to civil airspace in the United States, the Federal Aviation Administration (FAA) has produced a roadmap identifying key areas requiring further research and development. One such technical challenge is the development of a "detect and avoid" system (DAA) capable of providing a means of compliance with the "see and avoid" requirement in manned aviation. The purpose of the DAA system is to support the pilot, situated at a ground control station (GCS), in maintaining "DAA well clear" of nearby aircraft through the use of GCS displays and alerts. In addition to its primary function of aiding the pilot in maintaining well clear, the DAA system must also safely interoperate with existing NAS systems and operations, such as the airspace management procedures of air traffic controllers (ATC) and Collision Avoidance (CA) systems currently in use by manned aircraft, namely the Traffic alert and Collision Avoidance System (TCAS) II. It is anticipated that many UAS architectures will integrate both a DAA system and a TCAS II. It is therefore necessary to explicitly study the integration of DAA and TCAS II alerting structures and maneuver guidance formats to ensure that pilots understand the appropriate type and urgency of their response to the various alerts. This paper presents a concept of interoperability for the two systems. The concept was developed with the goal of avoiding any negative impact on the performance level of TCAS II while retaining a DAA system that still effectively enables pilots to maintain DAA well clear.

unmanned aircraft systems↗

TES: A modular systems approach to expert system development for real-time space applications

A major goal of the Space Station era is to reduce reliance on support from ground based experts. The development of software programs using expert systems technology is one means of reaching this goal without requiring crew members to become intimately familiar with the many complex spacecraft subsystems. Development of an expert systems program requires a validation of the software with actual flight hardware. By combining accurate hardware and software modelling techniques with a modular systems approach to expert systems development, the validation of these software programs can be successfully completed with minimum risk and effort. The TIMES Expert System (TES) is an application that monitors and evaluates real time data to perform fault detection and fault isolation tasks as they would otherwise be carried out by a knowledgeable designer. The development process and primary features of TES, a modular systems approach, and the lessons learned are discussed.

Cacace, Ralph↗

Master Console System Monitoring and Control Development

The Master Console internship during the spring of 2013 involved the development of firing room displays at the John F. Kennedy Space Center (KSC). This position was with the Master Console Product Group (MCPG) on the Launch Control System (LCS) project. This project is responsible for the System Monitoring and Control (SMC) and Record and Retrieval (R&R) of launch operations data. The Master Console is responsible for: loading the correct software into each of the remaining consoles in the firing room, connecting the proper data paths to and from the launch vehicle and all ground support equipment, and initializing the entire firing room system to begin processing. During my internship, I developed a system health and status display for use by Master Console Operators (MCO) to monitor and verify the integrity of the servers, gateways, network switches, and firewalls used in the firing room.

Brooks, Russell A.↗

Thermal Modeling and Correlation of the Space Environments Complex Vacuum Chamber and Cryoshroud

A thermal model of the Space Environments Complex (SEC) vacuum chamber and cryoshroud has been developed in support of upcoming thermal vacuum/thermal balance testing for Orion EM-1. The model was developed in Thermal Desktop and includes the vacuum chamber itself, a fluid model of the gaseous nitrogen flowing through the cryoshroud and the chamber piping, the Heat Flux System (HFS) within the cryoshroud, and the mechanical ground support equipment (MGSE) that interfaces with the vehicle. It has been correlated with steady state data from three tests. Two tests ran the cryoshroud in hot mode at 170 °F, and one test ran the cryoshroud in cold mode at -263 °F. Correlation was done using an optimization algorithm to find values of unknown contact conductances that minimized the RMS error between the model predictions and the test data. Overall, model quality was very good with a total RMS error of 2.6 °F.

Stalcup, Erik J.↗

Integrated ECLSS Ground Testbed Development and Status for 2025

The reliability of Spacecraft Life Support systems and the associated mass needed to support human spaceflight is one of the largest risks for missions beyond Low Earth Orbit. The reliability of these systems directly corresponds to the number of spares needed to support the mission. Performance improvements for these systems can reduce the consumables needed for long-duration missions. The only integrated spacecraft regenerative Life Support System exists in Low Earth Orbit. It is not practical to use the ISS system to fully understand the reliability of the technology as these systems are currently maintaining a livable environment and crew’s lives are dependent on the availability of these systems. To achieve advancement on reliability and mass, NASA has initiated the development of an Integrated ECLSS ground Testbed. This paper will provide a status on the testbed development, hardware development and areas for investigation. This paper will also cover planned testbed integration and support for Earth Independent Operations (EIO). This paper will be relevant to sessions: 205, 300, 301, 404, 406, 500, 50, 506, and 511.

Christopher Brown↗

DIGITAL COMMAND SYSTEM FOR SATELLITES

New coding system capable of transmitting almost 8,000 commands for a single tone and compatible with both tone- and digital-controlled satellites

SATELLITE CONTROL↗

Mars Reconnaissance Orbiter, Ground Data System, Receivables and Deliverables (REC/DELs)

This paper presents one JPL element manager's approach to describe a complex Ground Data System (GDS) with its receivables and deliverables (REC/DEL). The Mars Reconnaissance Orbiter (MRO) Ground Data System is the integrated set of ground software, hardware, facilities and networks that support mission operation. REC/DEL is a powerful tool for specifying hierarchy of commitments among systems and teams. Receivable of a system is a deliverable of another system. Focusing on tangible products enables the manager to objectively measure progress in a schedule. Jet Propulsion Laboratory mandates the use of REC/DEL for flight projects. Tutorial and training is provided for managers to create integrated REC/DEL database using automated systems. Project schedules are based on REC/DELs. This paper is not focusing on the mechanics of REC/DEL database creation, but it provides a guideline how one systematically creates categories of deliverables and receivables for ground data system components.

guidelines↗

Full Fuel-Cycle Comparison of Forklift Propulsion Systems

Hydrogen has received considerable attention as an alternative to fossil fuels. The U.S. Department of Energy (DOE) investigates the technical and economic feasibility of promising new technologies, such as hydrogen fuel cells. A recent report for DOE identified three near-term markets for fuel cells: 1. Emergency power for state and local emergency response agencies, 2. Forklifts in warehousing and distribution centers, and 3. Airport ground support equipment markets. This report examines forklift propulsion systems and addresses the potential energy and environmental implications of substituting fuel-cell propulsion for existing technologies based on batteries and fossil fuels. Industry data and the Argonne Greenhouse Gases, Regulated Emissions, and Energy Use in Transportation (GREET) model are used to estimate full fuel-cycle emissions and use of primary energy sources, back to the primary feedstocks for fuel production. Also considered are other environmental concerns at work locations. The benefits derived from using fuel-cell propulsion are determined by the sources of electricity and hydrogen. In particular, fuel-cell forklifts using hydrogen made from the reforming of natural gas had lower impacts than those using hydrogen from electrolysis.

08 HYDROGEN↗

Full fuel-cycle comparison of forklift propulsion systems.

Hydrogen has received considerable attention as an alternative to fossil fuels. The U.S. Department of Energy (DOE) investigates the technical and economic feasibility of promising new technologies, such as hydrogen fuel cells. A recent report for DOE identified three near-term markets for fuel cells: (1) Emergency power for state and local emergency response agencies, (2) Forklifts in warehousing and distribution centers, and (3) Airport ground support equipment markets. This report examines forklift propulsion systems and addresses the potential energy and environmental implications of substituting fuel-cell propulsion for existing technologies based on batteries and fossil fuels. Industry data and the Argonne Greenhouse Gases, Regulated Emissions, and Energy Use in Transportation (GREET) model are used to estimate full fuel-cycle emissions and use of primary energy sources, back to the primary feedstocks for fuel production. Also considered are other environmental concerns at work locations. The benefits derived from using fuel-cell propulsion are determined by the sources of electricity and hydrogen. In particular, fuel-cell forklifts using hydrogen made from the reforming of natural gas had lower impacts than those using hydrogen from electrolysis.

03 NATURAL GAS↗