Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Hardware Security”

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.

141 records · Page 8

Mars Sample Return Using Commercial Capabilities: Mission Architecture Overview

Mars Sample Return (MSR) is the highest priority science mission for the next decade as recommended by the recent Decadal Survey of Planetary Science. This paper presents an overview of a feasibility study for an MSR mission. The objective of the study was to determine whether emerging commercial capabilities can be used to reduce the number of mission systems and launches required to return the samples, with the goal of reducing mission cost. We report the feasibility of a complete and closed MSR mission design using the following scenario that covers three synodic launch opportunities, beginning with the 2022 opportunity: A Falcon Heavy injects a SpaceX Red Dragon capsule and trunk onto a Trans Mars Injection (TMI) trajectory. The capsule is modified to carry all the hardware needed to return samples collected on Mars including a Mars Ascent Vehicle (MAV), an Earth Return Vehicle (ERV), and hardware to transfer a sample collected in a previously landed rover mission to the ERV. The Red Dragon descends to land on the surface of Mars using Super Sonic Retro Propulsion (SSRP). After previously collected samples are transferred to the ERV, the single-stage MAV launches the ERV from the surface of Mars. The MAV uses a storable liquid bi-propellant propulsion system to deliver the ERV to a Mars phasing orbit. After a brief phasing period, the ERV, which also uses a storable bi-propellant system, performs a Trans Earth Injection (TEI) burn. Upon arrival at Earth, the ERV performs Earth and lunar swing-bys and is placed into a lunar trailing circular orbit - an Earth orbit, at lunar distance. A later mission, using Dragon and launched by a Falcon Heavy, performs a rendezvous with the ERV in the lunar trailing orbit, retrieves the sample container and breaks the chain of contact with Mars by transferring the sample into a sterile and secure container. With the sample contained, the retrieving spacecraft makes a controlled Earth re-entry preventing any unintended release of pristine martian materials into the Earth's biosphere. The analysis methods employed standard and specialized aerospace engineering tools. Mission system elements were analyzed with either direct techniques or by using parametric mass estimating relationships (MERs). The architecture was iterated until overall mission convergence was achieved on at least one path. Subsystems analyzed in this study include support structures, power system, nose fairing, thermal insulation, actuation devices, MAV exhaust venting, and GN&C. Best practice application of loads, mass growth contingencies, and resource margins were used. For Falcon Heavy capabilities and Dragon subsystems we utilized publically available data from SpaceX, published analyses from other sources, as well as our own engineering and aerodynamic estimates. Earth Launch mass is under 11 mt, which is within the estimated capability of a Falcon Heavy, with margin. Total entry masses between 7 and 10 mt were considered with closure occurring between 9 and 10 mt. Propellant mass fractions for each major phase of the EDL - Entry, Terminal Descent, and Hazard Avoidance - have been derived. An assessment of the effect of the entry conditions on the thermal protection system (TPS), currently in use for Dragon missions, shows no significant stressors. A useful payload mass of 2.0 mt is provided and includes mass growth allowances for the MAV, the ERV, and mission unique equipment. We also report options for the MAV and ERV, including propulsion systems, crewed versus robotic retrieval mission, as well as direct Earth entry. International planetary protection policies as well as verifiable means of compliance will have a large impact on any MSR mission design. We identify areas within our architecture where such impacts occur. We also describe preliminary compliance measures that will be the subject of future work. This work shows that emerging commercial capabilities as well as new methodologies can be used to efficiently support an important planetary science objective. The work also has applications for human exploration missions that use propulsive EDL techniques

Red Dragon↗

Emergency Flight Control of a Twin-Jet Commercial Aircraft using Manual Throttle Manipulation

The Department of Homeland Security (DHS) created the PCAR (Propulsion-Controlled Aircraft Recovery) project in 2005 to mitigate the ManPADS (man-portable air defense systems) threat to the commercial aircraft fleet with near-term, low-cost proven technology. Such an attack could potentially cause a major FCS (flight control system) malfunction or other critical system failure onboard the aircraft, despite the extreme reliability of current systems. For the situations in which nominal flight controls are lost or degraded, engine thrust may be the only remaining means for emergency flight control [ref 1]. A computer-controlled thrust system, known as propulsion-controlled aircraft (PCA), was developed in the mid 1990s with NASA, McDonnell Douglas and Honeywell. PCA's major accomplishment was a demonstration of an automatic landing capability using only engine thrust [ref 11. Despite these promising results, no production aircraft have been equipped with a PCA system, due primarily to the modifications required for implementation. A minimally invasive option is TOC (throttles-only control), which uses the same control principles as PCA, but requires absolutely no hardware, software or other aircraft modifications. TOC is pure piloting technique, and has historically been utilized several times by flight crews, both military and civilian, in emergency situations stemming from a loss of conventional control. Since the 1990s, engineers at NASA Dryden Flight Research Center (DFRC) have studied TOC, in both simulation and flight, for emergency flight control with test pilots in numerous configurations. In general, it was shown that TOC was effective on certain aircraft for making a survivable landing. DHS sponsored both NASA Dryden Flight Research Center (Edwards, CA) and United Airlines (Denver, Colorado) to conduct a flight and simulation study of the TOC characteristics of a twin-jet commercial transport, and assess the ability of a crew to control an aircraft down to a survivable runway landing using TOC. The PCAR project objective was a set of pilot procedures for operation of a specific aircraft without hydraulics that (a) have been validated in both simulation and flight by relevant personnel, and (b) mesh well with existing commercial operations, maintenance, and training at a minimum cost. As a result of this study, a procedure has been developed to assist a crew in making a survivable landing using TOC. In a simulation environment, line pilots with little or no previous TOC experience performed survivable runway landings after a few practice TOC approaches. In-flight evaluations put line pilots in a simulated emergency situation where TOC was used to recover the aircraft, maneuver to a landing site, and perform an approach down to 200 feet AGL. The results of this research, including pilot observations, procedure comments, recommendations, future work and lessons learned, will he discussed. Flight data and video footage of TOC approaches may also be shown.

Cole, Jennifer H.↗

An Efficient Approach for Mars Sample Return Using Emerging Commercial Capabilities

Mars Sample Return is the highest priority science mission for the next decade as recommended by the 2011 Decadal Survey of Planetary Science. This article presents the results of a feasibility study for a Mars Sample Return mission that efficiently uses emerging commercial capabilities expected to be available in the near future. The motivation of our study was the recognition that emerging commercial capabilities might be used to perform Mars Sample Return with an Earth-direct architecture, and that this may offer a desirable simpler and lower cost approach. The objective of the study was to determine whether these capabilities can be used to optimize the number of mission systems and launches required to return the samples, with the goal of achieving the desired simplicity. All of the major element required for the Mars Sample Return mission are described. Mission system elements were analyzed with either direct techniques or by using parametric mass estimating relationships. The analysis shows the feasibility of a complete and closed Mars Sample Return mission design based on the following scenario: A SpaceX Falcon Heavy launch vehicle places a modified version of a SpaceX Dragon capsule, referred to as "Red Dragon", onto a Trans Mars Injection trajectory. The capsule carries all the hardware needed to return to Earth Orbit samples collected by a prior mission, such as the planned NASA Mars 2020 sample collection rover. The payload includes a fully fueled Mars Ascent Vehicle; a fueled Earth Return Vehicle, support equipment, and a mechanism to transfer samples from the sample cache system onboard the rover to the Earth Return Vehicle. The Red Dragon descends to land on the surface of Mars using Supersonic Retropropulsion. After collected samples are transferred to the Earth Return Vehicle, the single-stage Mars Ascent Vehicle launches the Earth Return Vehicle from the surface of Mars to a Mars phasing orbit. After a brief phasing period, the Earth Return Vehicle performs a Trans Earth Injection burn. Once near Earth, the Earth Return Vehicle performs Earth and lunar swing-bys and is placed into a Lunar Trailing Orbit - an Earth orbit, at lunar distance. A retrieval mission then performs a rendezvous with the Earth Return Vehicle, retrieves the sample container, and breaks the chain of contact with Mars by transferring the sample into a sterile and secure container. With the sample contained, the retrieving spacecraft makes a controlled Earth re-entry preventing any unintended release of Martian materials into the Earth's biosphere. The mission can start in any one of three Earth to Mars launch opportunities, beginning in 2022.

Commercial↗

The Planning and Implementation of Test Facility Improvements

As engineering programs develop, and product testing begins, ideas for process improvement soon become obvious. Engineers envision new holding and handling fixtures. Additional custom-made support equipment may be needed. Perhaps modifications to the building or modifications to facility hardware are the order of the day. This is where a flexible creative test organization is needed. We need not be content with the status quo. All of these desired test innovations can make the difficult easy and improve the work flow. At times, implementing these new ideas demands more time or specialized expertise than test team members have. Through the coordinated use of labor resources, the needed improvements can still be made and in a timely fashion that supports program schedules. This presentation provides practical advice and a method whereby test personnel can creatively develop facility improvements and manage them from start to finish. You can control just how much time you invest and what part of your concepts you will personally design. By wisely defining the requirements and presenting them to the appropriate help sources (vendors, contractors, coworkers, and support departments), you can get the help you need to bring the improvements you have conceived, into fruition. Aspects of this presentation include defining requirements for test facility improvements, choosing labor resources, writing a statement of work, determining cost and benefits, securing department approval, coordinating procurement, managing the project, and training the end users. The process of successfully implementing test facility improvements is thoroughly explained. It has been tried, proven and improved over nearly 25 years of use. Whether considering a $50 improvement or a $50 million dollar improvement, this discussion will provide helpful pointers. Examples of improvements made through this process and their illustration will be included.

Oberlander, Larry↗

JANNAF "Test and Evaluation Guidelines for Liquid Rocket Engines": Status and Application

For many decades, the U.S. rocket propulsion industrial base has performed remarkably in developing complex liquid rocket engines that can propel critical payloads into service for the nation, as well as transport people and hardware for missions that open the frontiers of space exploration for humanity. This has been possible only at considerable expense given the lack of detailed guidance that captures the essence of successful practices and knowledge accumulated over five decades of liquid rocket engine development. In an effort to provide benchmarks and guidance for the next generation of rocket engineers, the Joint Army Navy NASA Air Force (JANNAF) Interagency Propulsion Committee published a liquid rocket engine (LRE) test and evaluation (T&E) guideline document in 2012 focusing on the development challenges and test verification considerations for liquid rocket engine systems. This document has been well received and applied by many current LRE developers as a benchmark and guidance tool, both for government-driven applications as well as for fully commercial ventures. The USAF Space and Missile Systems Center (SMC) has taken an additional near-term step and is directing activity to adapt and augment the content from the JANNAF LRE T&E guideline into a standard for potential application to future USAF requests for proposals for LRE development initiatives and launch vehicles for national security missions. A draft of this standard was already sent out for review and comment, and is intended to be formally approved and released towards the end of 2017. The acceptance and use of the LRE T&E guideline is possible through broad government and industry participation in the JANNAF liquid propulsion committee and associated panels. The sponsoring JANNAF community is expanding upon this initial baseline version and delving into further critical development aspects of liquid rocket propulsion testing at the integrated stage level as well as engine component level, in order to advance the state of the practice. The full participation of the entire U.S. rocket propulsion industrial base is invited and expected at this opportune moment in the continuing advancement of spaceflight technology.

Parkinson, Douglas↗

Internet-Based System for Voice Communication With the ISS

The Internet Voice Distribution System (IVoDS) is a voice-communication system that comprises mainly computer hardware and software. The IVoDS was developed to supplement and eventually replace the Enhanced Voice Distribution System (EVoDS), which, heretofore, has constituted the terrestrial subsystem of a system for voice communications among crewmembers of the International Space Station (ISS), workers at the Payloads Operations Center at Marshall Space Flight Center, principal investigators at diverse locations who are responsible for specific payloads, and others. The IVoDS utilizes a communication infrastructure of NASA and NASArelated intranets in addition to, as its name suggests, the Internet. Whereas the EVoDS utilizes traditional circuitswitched telephony, the IVoDS is a packet-data system that utilizes a voice over Internet protocol (VOIP). Relative to the EVoDS, the IVoDS offers advantages of greater flexibility and lower cost for expansion and reconfiguration. The IVoDS is an extended version of a commercial Internet-based voice conferencing system that enables each user to participate in only one conference at a time. In the IVoDS, a user can receive audio from as many as eight conferences simultaneously while sending audio to one of them. The IVoDS also incorporates administrative controls, beyond those of the commercial system, that provide greater security and control of the capabilities and authorizations for talking and listening afforded to each user.

Chamberlain, James↗

Affordable Development and Demonstration of a Small Nuclear Thermal Rocket (NTR) Engine and Stage: How Small Is Big Enough?

The Nuclear Thermal Rocket (NTR) derives its energy from fission of uranium-235 atoms contained within fuel elements that comprise the engine's reactor core. It generates high thrust and has a specific impulse potential of approximately 900 specific impulse - a 100 percent increase over today's best chemical rockets. The Nuclear Thermal Propulsion (NTP) project, funded by NASA's Advanced Exploration Systems (AES) program, includes five key task activities: (1) Recapture, demonstration, and validation of heritage graphite composite (GC) fuel (selected as the Lead Fuel option); (2) Engine Conceptual Design; (3) Operating Requirements Definition; (4) Identification of Affordable Options for Ground Testing; and (5) Formulation of an Affordable Development Strategy. During fiscal year (FY) 2014, a preliminary Design Development Test and Evaluation (DDT&E) plan and schedule for NTP development was outlined by the NASA Glenn Research Center (GRC), Department of Energy (DOE) and industry that involved significant system-level demonstration projects that included Ground Technology Demonstration (GTD) tests at the Nevada National Security Site (NNSS), followed by a Flight Technology Demonstration (FTD) mission. To reduce cost for the GTD tests and FTD mission, small NTR engines, in either the 7.5 or 16.5 kilopound-force thrust class, were considered. Both engine options used GC fuel and a common fuel element (FE) design. The small approximately 7.5 kilopound-force criticality-limited engine produces approximately157 thermal megawatts and its core is configured with parallel rows of hexagonal-shaped FEs and tie tubes (TTs) with a FE to TT ratio of approximately 1:1. The larger approximately 16.5 kilopound-force Small Nuclear Rocket Engine (SNRE), developed by Los Alamos National Laboratory (LANL) at the end of the Rover program, produces approximately 367 thermal megawatts and has a FE to TT ratio of approximately 2:1. Although both engines use a common 35-inch (approximately 89-centimeters) -long FE, the SNRE's larger diameter core contains approximately 300 more FEs needed to produce an additional 210 thermal megawatts of power. To reduce the cost of the FTD mission, a simple one-burn lunar flyby mission was considered to reduce the liquid hydrogen (LH2) propellant loading, the stage size and complexity. Use of existing and flight proven liquid rocket and stage hardware (e.g., from the RL10B-2 engine and Delta Cryogenic Second Stage) was also maximized to further aid affordability. This paper examines the pros and cons of using these two small engine options, including their potential to support future human exploration missions to the Moon, near Earth asteroids (NEA), and Mars, and recommends a preferred size. It also provides a preliminary assessment of the key activities, development options, and schedule required to affordably build, ground test and fly a small NTR engine and stage within a 10-year timeframe.

Spacecraft design↗

"Glitch Logic" and Applications to Computing and Information Security

This paper introduces a new method of information processing in digital systems, and discusses its potential benefits to computing and information security. The new method exploits glitches caused by delays in logic circuits for carrying and processing information. Glitch processing is hidden to conventional logic analyses and undetectable by traditional reverse engineering techniques. It enables the creation of new logic design methods that allow for an additional controllable "glitch logic" processing layer embedded into a conventional synchronous digital circuits as a hidden/covert information flow channel. The combination of synchronous logic with specific glitch logic design acting as an additional computing channel reduces the number of equivalent logic designs resulting from synthesis, thus implicitly reducing the possibility of modification and/or tampering with the design. The hidden information channel produced by the glitch logic can be used: 1) for covert computing/communication, 2) to prevent reverse engineering, tampering, and alteration of design, and 3) to act as a channel for information infiltration/exfiltration and propagation of viruses/spyware/Trojan horses.

hardware vulnerabilities↗

Spaceflight Holography Investigation in a Virtual Apparatus (SHIVA) Ground Experiments and Concepts for Flight Design

This paper discusses the development and design of an experimental test cell for ground-based testing to provide requirements for the Spaceflight Holography Investigation in a Virtual Apparatus (SHIVA) experiment. Ground-based testing of a hardware breadboard set-up is being conducted at Marshall Space Flight Center in Huntsville, Alabama. SHIVA objectives are to test and validate new solutions of the general equation of motion of a particle in a fluid, including particle-particle interaction, wall effects, motion at higher Reynolds Number, and a motion and dissolution of a crystal moving in a fluid. These objectives will be achieved by recording a large number of holograms of particle motion in the International Space Station (ISS) glove box under controlled conditions, extracting the precise three- dimensional position of all the particles as a function of time, and examining the effects of all parameters on the motion of the particles. This paper will describe the mechanistic approach to enabling the SHIVA experiment to be performed in a ISS glove box in microgravity. Because the particles are very small, surface tension becomes a major consideration in designing the mechanical method to meet the experiments objectives in microgravity, To keep a particle or particles in the center of the test cell long enough to perform and record the experiment and to preclude contribution to particle motion, requires avoiding any initial velocity in particle placement. A Particle Injection Mechanism (PIM) designed for microgravity has been devised and tested to enable SHIVA imaging. Also, a test cell capture mechanism, to secure the test cell during vibration on a specially designed shaker table for the SHIVA experiment will be described. Concepts for flight design are also presented.

Miernik, Janie H.↗

Curating NASA's Past, Present, and Future Extraterrestrial Sample Collections

As codified in NASA Policy Directive 7100.10F, the Astromaterials Acquisition and Curation Office at NASA Johnson Space Center (hereafter JSC Curation) is charged with curation of all extraterrestrial material under NASA control, including future NASA missions. JSC Curation curates all or part of nine astromaterial collections in seven clean room suites: (1) Apollo Samples (1969; ISO 6-7), (2) Luna Samples (from USSR; 1972; ISO 7), (3) Antarctic Meteorites (1976; ISO 7), (4) Cosmic Dust (1981; ISO 5), (5) Microparticle Impact Collection (formerly called Space Exposed Hardware; 1985; ISO 5), (6) Genesis Solar Wind Atoms (2004; ISO 4); (7) Stardust Comet Particles (2006; ISO 5), (8) Stardust Interstellar Particles (2006; ISO 5), (9) Hayabusa Asteroid Particles (from JAXA; 2010; ISO 5). In addition to the labs that house the samples, we have installed and maintained a wide variety of facilities and infrastructure required to support the clean-rooms: more than 10 different HEPA-filtered air-handling systems, ultrapure dry gaseous nitrogen systems, an ultrapure water system (UPW) and cleaning facilities to provide clean tools and equipment for the labs. We also have sample preparation facilities for making thin sections, microtome sections, and even focused ion-beam (FIB) sections to meet the research requirements of scientists. To ensure that we are keeping the samples as pristine as possible, we routinely monitor the cleanliness of our clean rooms and infrastructure systems. This monitoring includes: daily monitoring of the quality of our UPW, weekly airborne particle counts in the labs, monthly monitoring of the stable isotope composition of the gaseous N2 system, and annual measurements of inorganic or organic contamination in processing cabinets. We track within our databases the current and ever-changing characteristics of more than 250,000 individual samples across our various collections (including the 19,141 samples on loan to 433 Principal Investigators in 24 countries). The next sample return missions that NASA will participate in are Hayabusa2 and OSIRIS-REx (Origins Spectral Interpretation Resource Identification Security - Regolith Explorer). The designs for a new state-of-the-art suite of clean rooms to house these samples at JSC have been finalized. This includes separate ISO class 5 clean rooms to house each collection, a common ISO class 7 area for general use, an ISO class 7 microtome laboratory, and a separate thin section lab. Additionally, a new cleaning facility is being designed and procedures developed that will allow for enhanced cleaning of cabinets and tools in an inorganically, organically, and biologically clean manner. We are also designing a large multi-purpose Advanced Curation laboratory that will allow us to develop the techniques necessary to fully support the Hayabusa2 and OSIRIS-REx missions, as well as future possible sample return missions (e.g., Lunar Polar Volatiles, Mars, Comet Surface). A micro-CT (micro Computed Tomography) laboratory dedicated to the study of astromaterials has come online within JSC Curation, and we plan to add additional facilities that will enable non-destructive (or minimally-destructive) analyses of astromaterials in the near future (e.g., micro-XRF (micro X-Ray Fluorescence), confocal imaging Raman Spectroscopy). These facilities will be available to: (1) develop sample handling and storage techniques for future sample return missions, (2) be utilized by PET (Positron Emission Tomography) for future sample return missions, (3) for retroactive PET-style analyses of our existing collections, and (4) for periodic assessments of the existing sample collections.

Zeigler, Ryan A.↗

NASA Tech Briefs, January 2012

Contents of this issue are: (1) Energy-Based Tetrahedron Sensor for High-Temperature, High-Pressure Environments (2) Handheld Universal Diagnostic Sensor (3) Large-Area Vacuum Ultraviolet Sensors (4) Fiber Bragg Grating Sensor System for Monitoring Smart Composite Aerospace Structures (5) Health-Enabled Smart Sensor Fusion Technology (6) Extended-Range Passive RFID and Sensor Tags (7) Hybrid Collaborative Learning for Classification and Clustering in Sensor Networks (8) Self-Healing, Inflatable, Rigidizable Shelter (9) Improvements in Cold-Plate Fabrication (10) Technique for Radiometer and Antenna Array Calibration - TRAAC (11) Real-Time Cognitive Computing Architecture for Data Fusion in a Dynamic Environment (12) Programmable Digital Controller (13) Use of CCSDS Packets Over SpaceWire to Control Hardware (14) Key Decision Record Creation and Approval Module (15) Enhanced Graphics for Extended Scale Range (16) Debris Examination Using Ballistic and Radar Integrated Software (17) Data Distribution System (DDS) and Solar Dynamic Observatory Ground Station (SDOGS) (18) Integration Manager (19) Eclipse-Free-Time Assessment Tool for IRIS (20) Automated and Manual Rocket Crater Measurement Software (21) MATLAB Stability and Control Toolbox Trim and Static Stability Module (22) Patched Conic Trajectory Code (23) Ring Image Analyzer (24) SureTrak Probability of Impact Display (25) Implementation of a Non-Metallic Barrier in an Electric Motor (26) Multi-Mission Radioisotope Thermoelectric Generator Heat Exchangers for the Mars Science Laboratory Rover (27) Uniform Dust Distributor for Testing Radiative Emittance of Dust-Coated Surfaces (28) MicroProbe Small Unmanned Aerial System (29) Highly Stable and Active Catalyst for Sabatier Reactions (30) Better Proton-Conducting Polymers for Fuel-Cell Membranes (31) CCD Camera Lens Interface for Real-Time Theodolite Alignment (32) Peregrine 100-km Sounding Rocket Project (33) SOFIA Closed- and Open-Door Aerodynamic Analyses (34) Sonic Thermometer for High-Altitude Balloons (35) Near-Infrared Photon-Counting Camera for High-Sensitivity Observations (36) Integrated Optics Achromatic Nuller for Stellar Interferometry (37) High-Speed Digital Interferometry (38) Ultra-Miniature Lidar Scanner for Launch Range Data Collection (39) Shape and Color Features for Object Recognition Search (40) Explanation Capabilities for Behavior-Based Robot Control (41) A DNA-Inspired Encryption Methodology for Secure, Mobile Ad Hoc Networks (42) Quality Control Method for a Micro-Nano-Channel Microfabricated Device (43) Corner-Cube Retroreflector Instrument for Advanced Lunar Laser Ranging (44) Electrospray Collection of Lunar Dust (45) Fabrication of a Kilopixel Array of Superconducting Microcalorimeters with Microstripline Wiring Spacecraft Attitude Tracking and Maneuver Using Combined Magnetic Actuators (46) Coherent Detector for Near-Angle Scattering and Polarization Characterization of Telescope Mirror Coatings

Source record↗

Compiling a Comprehensive EVA Training Dataset for NASA Astronauts

Training for a spacewalk or extravehicular activity (EVA) is considered a hazardous duty for NASA astronauts. This places astronauts at risk for decompression sickness as well as various musculoskeletal disorders from working in the spacesuit. As a result, the operational and research communities over the years have requested access to EVA training data to supplement their studies. The purpose of this paper is to document the comprehensive EVA training data set that was compiled from multiple sources by the Lifetime Surveillance of Astronaut Health (LSAH) epidemiologists to investigate musculoskeletal injuries. The EVA training dataset does not contain any medical data, rather it only documents when EVA training was performed, by whom and other details about the session. The first activities practicing EVA maneuvers in water were performed at the Neutral Buoyancy Simulator (NBS) at the Marshall Spaceflight Center in Huntsville, Alabama. This facility opened in 1967 and was used for EVA training until the early Space Shuttle program days. Although several photographs show astronauts performing EVA training in the NBS, records detailing who performed the training and the frequency of training are unavailable. Paper training records were stored within the NBS after it was designated as a National Historic Landmark in 1985 and closed in 1997, but significant resources would be needed to identify and secure these records, and at this time LSAH has not pursued acquisition of these early training records. Training in the NBS decreased when the Johnson Space Center in Houston, Texas, opened the Weightless Environment Training Facility (WETF) in 1980. Early training records from the WETF consist of 11 hand-written dive logbooks compiled by individual workers that were digitized at the request of LSAH. The WETF was integral in the training for Space Shuttle EVAs until its closure in 1998. The Neutral Buoyancy Laboratory (NBL) at the Sonny Carter Training Facility near JSC opened in March 1997 and is the current site for US EVA training. Other space agencies also have used water to simulate weightlessness and train for EVAs. Russia has a training facility similar to the NBL named the Hydro Lab. The Hydro Lab began operations at the Gagarin Cosmonaut Training Center (GCTC) in 1980 and has been used extensively to the present. Although a majority of training in the Hydro Lab uses the Russian Orlan suit, a small number of sessions have been conducted using a NASA suit. The Japanese Weightlessness Environment Test System (WETS) went into service at the Tsukuba Space Center in 1997 but was closed in 2011 due to extensive earthquake damage. Several sessions were performed using a NASA suit, but these sessions were short and considered "development" runs. LSAH has assembled records from the WETF, NBL and Hydro Lab. Recording of the EVA training data has changed considerably from 1967 to present. The goal of early record keeping was to track use of hardware components, and the person involved was treated as a suited operator, not as a focus of interest. Records from the past two decades are fairly precise with the person, date, suit type and size noted. On occasion the length of the session was listed, but this data is not included on all records. Records were merged from data sources and extensive cleaning of the records was required since the multiple sources frequently overlapped and duplicated records. To date the LSAH EVA training dataset includes over 12,500 EVA training sessions performed by NASA astronauts since 1981. The following variables are included for most records: Name, Sex, Event date, Event name, HUT type, HUT size, Facility, and Estimated run time. For a smaller subset of records, the following variables are available: Actual run time, Time inverted, and the suit components Waist bearing type, Shoulder harness, Shoulder pads, and Teflon inserts. The LSAH dataset is currently the most complete resource for data regarding EVA training sessions performed by NASA astronauts. However, it is not 100 percent complete since the WETS (Japan) and NBS (Marshall) training facility data were not included. This dataset has been compiled by LSAH to study the relationship of EVA training to musculoskeletal injuries but has many other non-medical applications. This dataset can be provided to other groups in order to respond to program and research questions with appropriate board approvals.

Laughlin, M. S.↗

Dual-Doppler Feasibility Study

When two or more Doppler weather radar systems are monitoring the same region, the Doppler velocities can be combined to form a three-dimensional (3-D) wind vector field thus providing for a more intuitive analysis of the wind field. A real-time display of the 3-D winds can assist forecasters in predicting the onset of convection and severe weather. The data can also be used to initialize local numerical weather prediction models. Two operational Doppler Radar systems are in the vicinity of Kennedy Space Center (KSC) and Cape Canaveral Air Force Station (CCAFS); these systems are operated by the 45th Space Wing (45 SW) and the National Weather Service Melbourne, Fla. (NWS MLB). Dual-Doppler applications were considered by the 45 SW in choosing the site for the new radar. Accordingly, the 45th Weather Squadron (45 WS), NWS MLB and the National Aeronautics and Space Administration tasked the Applied Meteorology Unit (AMU) to investigate the feasibility of establishing dual-Doppler capability using the two existing systems. This study investigated technical, hardware, and software requirements necessary to enable the establishment of a dual-Doppler capability. Review of the available literature pertaining to the dual-Doppler technique and consultation with experts revealed that the physical locations and resulting beam crossing angles of the 45 SW and NWS MLB radars make them ideally suited for a dual-Doppler capability. The dual-Doppler equations were derived to facilitate complete understanding of dual-Doppler synthesis; to determine the technical information requirements; and to determine the components of wind velocity from the equation of continuity and radial velocity data collected by the two Doppler radars. Analysis confirmed the suitability of the existing systems to provide the desired capability. In addition, it is possible that both 45 SW radar data and Terminal Doppler Weather Radar data from Orlando International Airport could be used to alleviate any radar geometry issues at the NWS MLB radar, such as the "cone of silence" or beam blockage. In the event of a radar outage at one of the sites, the multi-radar algorithms would provide continuing coverage of the area through use of the data from the remaining operational radar sites. There are several options to collect, edit, synthesize and display dual-Doppler data sets. These options include commercial packages available for purchase and a variety of freeware packages available from the National Center for Atmospheric Research (NCAR) for processing raw radar data. However, evaluation of the freeware packages revealed that they do not have sufficient documentation and configuration control to be certified for 45 SW use. Additionally, a TI data line must be installed/leased from the NWS MLB office and CCAFS to enable the receipt of NWS MLB raw radar data to use in the dual-Doppler synthesis. Integration of the TI data line into the Eastern Range infrastructure that will meet the security requirements necessary for 45 SW use is time-consuming and costly. Overall evaluation indicates that establishment of the dual-Doppler capability using the existing operational radar systems is desirable and feasible with no technical concerns. Installation of such a system represents a significant enhancement to forecasting capabilities at the 45 WS and at NWS MLB. However, data security and cost considerations must be evaluated in light of current budgetary constraints. In any case, gaining the dual-Doppler capability will provide opportunities for better visualization of the wind field and better forecasting of the onset of convection and severe weather events to support space launch operations at KSC and CCAFS.

Huddleston, Lisa L.↗

The NASA Integrated Information Technology Architecture

This document defines an Information Technology Architecture for the National Aeronautics and Space Administration (NASA), where Information Technology (IT) refers to the hardware, software, standards, protocols and processes that enable the creation, manipulation, storage, organization and sharing of information. An architecture provides an itemization and definition of these IT structures, a view of the relationship of the structures to each other and, most importantly, an accessible view of the whole. It is a fundamental assumption of this document that a useful, interoperable and affordable IT environment is key to the execution of the core NASA scientific and project competencies and business practices. This Architecture represents the highest level system design and guideline for NASA IT related activities and has been created on the authority of the NASA Chief Information Officer (CIO) and will be maintained under the auspices of that office. It addresses all aspects of general purpose, research, administrative and scientific computing and networking throughout the NASA Agency and is applicable to all NASA administrative offices, projects, field centers and remote sites. Through the establishment of five Objectives and six Principles this Architecture provides a blueprint for all NASA IT service providers: civil service, contractor and outsourcer. The most significant of the Objectives and Principles are the commitment to customer-driven IT implementations and the commitment to a simpler, cost-efficient, standards-based, modular IT infrastructure. In order to ensure that the Architecture is presented and defined in the context of the mission, project and business goals of NASA, this Architecture consists of four layers in which each subsequent layer builds on the previous layer. They are: 1) the Business Architecture: the operational functions of the business, or Enterprise, 2) the Systems Architecture: the specific Enterprise activities within the context of IT systems, 3) the Technical Architecture: a common, vendor-independent framework for design, integration and implementation of IT systems and 4) the Product Architecture: vendor=specific IT solutions. The Systems Architecture is effectively a description of the end-user "requirements". Generalized end-user requirements are discussed and subsequently organized into specific mission and project functions. The Technical Architecture depicts the framework, and relationship, of the specific IT components that enable the end-user functionality as described in the Systems Architecture. The primary components as described in the Technical Architecture are: 1) Applications: Basic Client Component, Object Creation Applications, Collaborative Applications, Object Analysis Applications, 2) Services: Messaging, Information Broker, Collaboration, Distributed Processing, and 3) Infrastructure: Network, Security, Directory, Certificate Management, Enterprise Management and File System. This Architecture also provides specific Implementation Recommendations, the most significant of which is the recognition of IT as core to NASA activities and defines a plan, which is aligned with the NASA strategic planning processes, for keeping the Architecture alive and useful.

Baldridge, Tim↗

Encryption for Remote Control via Internet or Intranet

A data-communication protocol has been devised to enable secure, reliable remote control of processes and equipment via a collision-based network, while using minimal bandwidth and computation. The network could be the Internet or an intranet. Control is made secure by use of both a password and a dynamic key, which is sent transparently to a remote user by the controlled computer (that is, the computer, located at the site of the equipment or process to be controlled, that exerts direct control over the process). The protocol functions in the presence of network latency, overcomes errors caused by missed dynamic keys, and defeats attempts by unauthorized remote users to gain control. The protocol is not suitable for real-time control, but is well suited for applications in which control latencies up to about 0.5 second are acceptable. The encryption scheme involves the use of both a dynamic and a private key, without any additional overhead that would degrade performance. The dynamic key is embedded in the equipment- or process-monitor data packets sent out by the controlled computer: in other words, the dynamic key is a subset of the data in each such data packet. The controlled computer maintains a history of the last 3 to 5 data packets for use in decrypting incoming control commands. In addition, the controlled computer records a private key (password) that is given to the remote computer. The encrypted incoming command is permuted by both the dynamic and private key. A person who records the command data in a given packet for hostile purposes cannot use that packet after the public key expires (typically within 3 seconds). Even a person in possession of an unauthorized copy of the command/remote-display software cannot use that software in the absence of the password. The use of a dynamic key embedded in the outgoing data makes the central-processing unit overhead very small. The use of a National Instruments DataSocket(TradeMark) (or equivalent) protocol or the User Datagram Protocol makes it possible to obtain reasonably short response times: Typical response times in event-driven control, using packets sized .300 bytes, are <0.2 second for commands issued from locations anywhere on Earth. The protocol requires that control commands represent absolute values of controlled parameters (e.g., a specified temperature), as distinguished from changes in values of controlled parameters (e.g., a specified increment of temperature). Each command is issued three or more times to ensure delivery in crowded networks. The use of absolute-value commands prevents additional (redundant) commands from causing trouble. Because a remote controlling computer receives "talkback" in the form of data packets from the controlled computer, typically within a time interval < or =1 s, the controlling computer can re-issue a command if network failure has occurred. The controlled computer, the process or equipment that it controls, and any human operator(s) at the site of the controlled equipment or process should be equipped with safety measures to prevent damage to equipment or injury to humans. These features could be a combination of software, external hardware, and intervention by the human operator(s). The protocol is not fail-safe, but by adopting these safety measures as part of the protocol, one makes the protocol a robust means of controlling remote processes and equipment by use of typical office computers via intranets and/or the Internet.

Lineberger, Lewis↗