Search NASA⌕ Search

SEARCH · Search NASA

Results for “AREA 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.

At least 217 records · Page 12

ISS External Microorganisms: A Payload to Close Planetary Protection Knowledge Gaps for Crewed Missions

Before NASA or COSPAR is able to set planetary protection requirements for crewed missions to locations like Mars there are a number of critical knowledge gaps that must be addressed (1). One of the most important knowledge gaps is an understanding of microbial leakage from crewed habitats and space suits. Current ECLSS (Environmental Control and Life Support System) and PLSS (Portable Life Support System) requirements do not include any provisions to control microbes that may escape along with vented or leaked gasses. The current generation of NASA space suits can leak at rates as high as 100 cm2 /min. during nominal operation (2). ISS (International Space Station) intentionally vents atmospheric gases like CO2 to maintain habitable conditions for the crew. Furthermore, every time an airlock is used for EVA (extravehicular activity)there is an accompanying release of internal atmosphere. Since it is not possible to sterilize a crewed mission, it is important that we understand what if any microbes are entrained in these vented and leaked products. It is also important to understand if these microbes can survive on exterior surfaces. Recent sampling of the Russian segments of ISS suggest that bacteria and fungi from inside ISS may be capable of surviving on external surfaces(3). NASA is developing an aseptic sampling tool for use during EVA and plans to collect samples from vents on ISS to build on these results. The results of this work will be used to develop planetary protection requirements for vented and leaked gasses from crewed volumes. NASA has developed and tested a tool kit for collecting microbiological samples during EVA(4). This tool kit contains eight commercially available, 23 mm. diameter, foam swabs that can be used to aseptically collect samples while at vacuum. The swabs are individually housed in aluminum canisters that are equipped with 0.2 μm Teflon filters. These filters allow the canisters to equilibrate to pressure changes while preventing microbiological contamination. The canisters will be cleaned and sterilized before flight. Results from ground-based testing indicate that this tool kit is capable of aseptically collecting microbes while at vacuum without becoming contaminated during pressure changes(5). Based on the results of this ground testing we have modified the tool kit to meet NASA safety requirements and improve the ergonomics. We added additional mounting points to the tool kit to give astronauts more options for securing it during use. We also changed the opening mechanism to improve the precision with which swabs can be extracted from the tool kit. We plan to use this kit on an upcoming EVA to collect samples from non-propulsive vents and areas near the U.S. airlock on ISS. These samples will be frozen at -80 ̊C and stored on station until they can be returned to Earth. We will analyze these returned samples using next generation DNA sequencing to determine the community composition and function of external ISS environments. The results of this study will close planetary protection knowledge gaps for crewed missions and will help NASA determine appropriate planetary protection requirements for life support systems. The tool kit will also be useful for collecting aseptic samples on upcoming crewed or robotic missions and could easily be modified to collect samples with organic contamination control requirements as well.

A B Regberg↗

Fingered bola body, bola with same, and methods of use

The present invention discloses bola bodies, bolas, and a snaring method which makes use such devices. A bola body, according to the present invention, is nonspherical or irregular in shape rather than a smooth sphere or ovoid body. One or more fingers extends from the bola body. These fingers may be relatively straight or they may have crooked or bent portions to enhance entanglement with a bola line or lines or with each other. Two or more of such fingers may be used and may be regularly or irregularly spaced apart on a bola body. A bola with such bodies includes lines which are connected to the other bodies. In one particular embodiment of a bola body, according to the present invention, the body has an irregular shape with a bottom rectangular portion and a top pyramid portion forming a nose. A plurality of fingers is extended from the pyramidal top portion with one finger extended up and away from each of four corners of the top portion. Such a bola body tends to be initially oriented with its nose and fingers against an object being snared since the body is pulled nose first when a bola line is secured at the tip of the pyramidal portion of the bola body. With such a bola, an unwrapping bola body can slip around a target member so that two of the rod-shaped fingers catch a bola line and guide it into an area or crook between the fingers and a side of the top pyramidal portion of the bola body. Tension on the bola line maintains the line in the crook and tends to press the fingers against the unwrapped target member to stabilize the wrapping of the line about the target member. With such a bola, it is difficult for two or more lines unwrapping in different directions to move past one another without being forced together by line tension. Also, the fingers of such bola bodies may hook and hold each other. The fingers may also hook or entangle some object on or portion of the target member. A probable known target member has known dimensions and shapes so that the bola may be sized and configured to reliably snare such a known target. The bolas can be optimally sized, fashioned, and configured to contact and hold a probable target of known size, dimension, and shape.

Dzenitis, John M.↗

Emergency Operations Center at Johnson Space Center

In June 1966, at the start of the Gulf Coast hurricane season, the Johnson Space Center (JSC) celebrated the opening of its new 4,000-square foot, state-of-the-art Emergency Operations Center (EOC). The new EOC has been upgraded and enhanced to support a wide spectrum of emergencies affecting JSC and neighboring communities. One of the main features of the EOC is its premier computerized dispatch center. The new system unites many of JSC's critical emergency functions into one integrated network. It automatically monitors fire alarms, security entrances, and external cameras. It contains the JSC inventory of hazardous materials, by building and room, and can call up Material Safety Data Sheets for most of the generic hazardous materials used on-site. The EOC is available for community use during area emergencies such as hurricanes and is a welcome addition to the Clear Lake/Galveston Bay Area communities' emergency response resources.

Caylor, Gary C.↗

Internet technologies and requirements for telemedicine

Internet technologies are briefly introduced and those applicable for telemedicine are reviewed. Multicast internet technologies are described. The National Aeronautics and Space Administration (NASA) 'Telemedicine Space-bridge to Russia' project is described and used to derive requirements for internet telemedicine. Telemedicine privacy and Quality of Service (QoS) requirements are described.

Remote Consultation↗

Distributed Large Data-Object Environments: End-to-End Performance Analysis of High Speed Distributed Storage Systems in Wide Area ATM Networks

We have developed and deployed a distributed-parallel storage system (DPSS) in several high speed asynchronous transfer mode (ATM) wide area networks (WAN) testbeds to support several different types of data-intensive applications. Architecturally, the DPSS is a network striped disk array, but is fairly unique in that its implementation allows applications complete freedom to determine optimal data layout, replication and/or coding redundancy strategy, security policy, and dynamic reconfiguration. In conjunction with the DPSS, we have developed a 'top-to-bottom, end-to-end' performance monitoring and analysis methodology that has allowed us to characterize all aspects of the DPSS operating in high speed ATM networks. In particular, we have run a variety of performance monitoring experiments involving the DPSS in the MAGIC testbed, which is a large scale, high speed, ATM network and we describe our experience using the monitoring methodology to identify and correct problems that limit the performance of high speed distributed applications. Finally, the DPSS is part of an overall architecture for using high speed, WAN's for enabling the routine, location independent use of large data-objects. Since this is part of the motivation for a distributed storage system, we describe this architecture.

Johnston, William↗

Use of Open Networks and Delay-Tolerant Protocol to Decrease WAN Latency of EOS near Real-Time Data

Since 1999, NASA's Earth Observing System Data Operations System (EDOS) project at Goddard Space Flight Center (GSFC) has provided high-rate data capture, level zero processing, and product distribution services for a majority of NASA's EOS (Earth Observing System) high-rate missions, including Terra, Aqua, Aura, ICESat, EO-1, SMAP, and OCO-2. EDOS high-rate science and engineering (150-300 Mbps) data-driven capture systems are deployed at 7 worldwide ground stations which are connected via both private (closed) and public (open) wide area networks (WANs) to the centralized EDOS Level Zero Processing Facility (LZPF) located at GSFC, where the data is processed and Level 0 products are distributed to users worldwide. All data transferred over the open networks to GSFC traverse an IPSec tunnel, providing the same level of security as a VPN connection. EDOS produces both time-based and near real-time products (session-based). Near real-time data products are produced from a single ground station contact; time-based products are produced from multiple ground station contacts. EDOS is the primary supplier of EOS Level 0 data to the NASA near real-time user community known as the Land, Atmosphere Near real-time Capability for EOS (LANCE). For the past few years, EDOS has streamlined its systems to reduce WAN latency for near real-time data delivery, including implementing Quality of Service (QoS), expanding closed network bandwidth, adding open network connections with more bandwidth, and implementing a delay-tolerant protocol to mitigate long round-trip times to remote ground stations.

Delay-Tolerant Protocol↗

In-Depth Modeling and Simulation Analysis of Artemis Missions Using the Impact Probabilistic Risk Assessment Tool

BACKGROUND The Artemis campaign is a Moon exploration program with a series of six planned missions, five of which will be crewed. These five crewed missions will contain a single mission segment (space flight), or multiple mission segments involving space flight (Orion), lunar landing (LTV) and/or space habitat (Gateway). Each crewed segment faces the risk of unique medical conditions, necessitating medical sets/kits tailored to those specificities. To support and enable a data-driven and evidence-based decision-making process through out a mission’s life cycle, a software tool called IMPACT was developed. Using probabilistic risk assessment (PRA) methodologies, IMPACT (Informing Mission Planning via Analysis of Complex Tradespaces) is a novel tool built for analyzing the possibility of encountering complex medical risks during space flight, and for identifying the medical resources and capabilities needed to treat those potential at-risk medical conditions. IMPACT achieves this by performing hundreds of thousands of Monte Carlo simulations of missions to build aggregate pictures of medical risk. During an extended simulation modeling phase, IMPACT generated analytical results for medical risks, and the medical resources and capabilities to address those risks, for every segment of every crewed Artemis mission. This presentation will highlight the reliability, consistency and validity of IMPACT’s computational modeling techniques and will showcase the library of analytical outcomes generated for the Artemis missions. OVERVIEW During the early stages of IMPACT’s design, architecture and technical requirements collection, “scenarios” (use cases) - achievement goals required for acceptance testing, were identified by stakeholders. IMPACT successfully completed the scenario testing requirements and undertook an extensive operational run phase utilizing a wide range of input combinations with a goal of delivering a cohesive, trustworthy, reliable, vast, and diverse body of evidence. The intent of these modeling runs was to validate consistency in output, ensure solidity of executable operations and to streamline processes by identifying areas requiring efficiency improvements. Using the many missions of Artemis, IMPACT ran variations of operational runs to assess the output for acceptable, as well as unusual characteristics. This rigorous long-term “shakedown” analysis was implemented to help build a collective body of evidence to aid in securing a high level of confidence, reliability, and validity in the output, whether from the applicational components of IMPACT, or the entirety of the operational process. ANTICIPATED ANALYSIS AND CONCLUSION This presentation will discuss the various categories of input criteria; the comparisons in the application of these input criteria to various Artemis missions; the preparation and collection of the body of evidence, and reliability of the computational modeling techniques. This paper serves as an initial analytical overview of IMPACT’s probabilistic risk assessment (PRA) medical risk outputs covering Artemis missions and is not intended to be deemed the official medical response for the Artemis campaign.

Crew Composition↗

Using Satellite Remote Sensing Data in a Spatially Explicit Price Model

Famine early warning organizations use data from multiple disciplines to assess food insecurity of communities and regions in less-developed parts of the World. In this paper we integrate several indicators that are available to enhance the information for preparation for and responses to food security emergencies. The assessment uses a price model based on the relationship between the suitability of the growing season and market prices for coarse grain. The model is then used to create spatially continuous maps of millet prices. The model is applied to the dry central and northern areas of West Africa, using satellite-derived vegetation indices for the entire region. By coupling the model with vegetation data estimated for one to four months into the future, maps are created of a leading indicator of potential price movements. It is anticipated that these maps can be used to enable early warning of famine and for planning appropriate responses.

Brown, Molly E.↗

Northeast Alaska Climate: Using Earth Observations to Evaluate Snow Variability through a Climatological Analysis to Support Ecological Monitoring in Northeast Alaska

Alaska is experiencing climate change at an unprecedented rate, with temperatures increasing twice as fast as the national average. The resulting changes to the landscape and ecosystems are significant, including shorter winters, declining snow depth, thawing permafrost, and rapidly receding glaciers. These changes are not only exacerbating the negative impacts of oil exploration but also affecting the food security of indigenous communities that rely on hunting as a subsistence food source. With the US Fish and Wildlife Service managing a potential tundra travel season for the first time in its history, adequate data on historic snow variables is essential to protect the unique habitat of the area. This project used NASA satellite and assimilation system data to inform and improve the current understanding of snow patterns in the Arctic National Wildlife Refuge and the National Petroleum Reserve – Alaska. The DEVELOP team used MODIS Normalized Difference Snow Index data to determine snow season duration, snow change frequency, and the first and last days of snow. The team also utilized the 2.1 Global Land Data Assimilation System and Daymet V4 products to study climatological trends in snow depth and snow water equivalent, respectively, across the study areas. The results of this study give users the capacity to visualize maps of multiple snow variables to monitor changes in snow conditions and proactively prepare for the ecological, cultural, and landscape impacts that changes in snow variability will cause in the future.

Remote Sensing↗

Search for supporting methodologies - Or how to support SEI for 35 years

Concepts relevant to the development of an evolvable information management system are examined in terms of support for the Space Exploration Initiative. The issues of interoperability within NASA and industry initiatives are studied including the Open Systems Interconnection standard and the operating system of the Open Software Foundation. The requirements of partitioning functionality into separate areas are determined with attention given to the infrastructure required to ensure system-wide compliance. The need for a decision-making context is a key to the distributed implementation of the program, and this environment is concluded to be next step in developing an evolvable, interoperable, and securable support network.

Handley, Thomas H., Jr.↗

Lunar Utilization Control Area (LUCA): Configurable Mission Control Rooms and the Benefits to Future Spaceflight

Configurable Control Rooms provide the ability to rapidly change capabilities from mission to mission and customer to customer. Future missions will likely not have the 24/7/365 need for a dedicated mission support room, and CCR could easily be adapted for continuous support if needed. CCRs offer physical, centralized locations for teams to support, and the HOSC provides a secure, reliable facility with constant monitoring by network specialists. Institutions and payload teams can cost save by utilizing a CCR at MSFC eliminating the need to assemble an entire custom control room at their location. This new paradigm in flight operations can ease the creation of any mission from a cubesat to a New Frontiers or Flagship program and anything in between.

Configurable Control Rooms↗

Meteorite Sample Section Repair at NASA Johnson Space Center

Introduction: Meteorite thin and thick sections are routinely shipped from NASA Johnson Space Center to fulfill sample allocation requests from principle investigators around the world. Sections are also re-turned to JSC when researchers are finished studying them since, in most cases, they can be reused for other studies. The sections are very fragile unfortunately, and sometimes return to us needing repairs. The fol-lowing should give you an idea of how we repair sections here in the very lab where they were created. NOTE: Please do not attempt to repair ANSMET meteorite sections that are in your possession. We will perform the repairs for you at NASA JSC if you send the section back to us. Section Delamination: The majority of the meteorite sections that we produce here are secured to the glass slide using a high quality, two-part epoxy. Occasionally, we are asked to use superglue if the researcher wishes to dismount the section from the slide. Both epoxy and superglue are excellent adhesives, but they both tend to embrittle with time which results in delamination from the slide. Exposure to vacuum can also degrade the adhesion between the sample section and the glass slide. Repeated handling of the slide edges can accelerate delamination and, as a preventive measure, the outer 1-2 mm of epoxy is trimmed from newly created sections at JSC. If conductive tapes (copper, carbon, etc.) are used on the section during analysis, great care must be taken in removing the tape so that the epoxy is not pulled up with it. If in doubt, the tape can be left on the section when it is returned to JSC. Before we perform any repairs to sample sections, carbon, gold, or other coatings are removed. We accomplish this using a slurry of 0.05 micron alumina and 190 proof ethyl alcohol applied to a felt polishing pad fitted to a rotating lap wheel. Coatings are re-moved in this manner from all sections that are re-turned to JSC. The extent of the delamination determines how we proceed with the section repair. If the meteorite sample area of the section is not disturbed, then we carefully remove the delaminated epoxy. This is done using a binocular microscope with a 6X zoom, cut-proof gloves, and a very sharp, single edged razor blade. We cut the delaminated epoxy with the blade angled away from the sample area and using very light pressure. The trimmed section is then cleaned in an ultrasonic bath of 200 proof ethyl alcohol for no more than 10 seconds and carefully dried using a lint-free clean room wipe. The section is then placed into a lab oven at 110o F in preparation for epoxy. We mix the resin and hardener components of the low viscosity epoxy and very small amounts are applied to the cut edges of the section using a needle probe and the binocular microscope. Warming the epoxy helps secure the existing section by filling any voids between the glass slide and the section. After the new epoxy cures, we give the section a light polish on a lap wheel fitted with cotton polishing paper that is charged with 1 micron diamond paste. If the section has delaminated to the point of sample area being lifted from the glass, then it may be irreparable. We employ the above technique along with clamping the section in a Teflon pad arrangement in order to flatten the sample while the epoxy cures. Otherwise, the sample will tend to curl. This works to some degree, but once the sample area curls, it seldom re-turns to the original flatness without cracking or bending. Canada Balsam and Crystalbond: We repair damaged sections that had originally been prepared using Canada Balsam or Crystalbond adhesives through the gradual application of heat. We take great care with these samples since these bonding materials tend to get brittle with age. The section is heated in gradual steps (40-50o F per hour) to the melting point of the adhesive. We repair the sample while the adhesive is fluid and then the section is cooled in the same gradual manner in which it was heated. Slide Cracks and Breaks: Accidents happen. Especially with something as small and fragile as a thin/thick section. We all know someone who has driven a microscope objective into a section. As bad as the damage may look, the section can be repaired in most instances. NOTE: Please do not try to tape or glue section pieces back together prior to returning the dam-aged section. This practice usually renders the section irreparable. If the glass slide is cracked but the section is still in one piece, we repair it by infilling the crack with the low viscosity epoxy mentioned earlier. If the slide is in pieces, we can reassemble it with epoxy on a new backer slide. This is a tricky task as the pieces need to be in the correct plane with respect to each other, especially if the sample area is split among several pieces.

Meteorite↗

Recommendations for a service framework to access astronomical archives

There are a large number of astronomical archives and catalogs on-line for network access, with many different user interfaces and features. Some systems are moving towards distributed access, supplying users with client software for their home sites which connects to servers at the archive site. Many of the issues involved in defining a standard framework of services that archive/catalog suppliers can use to achieve a basic level of interoperability are described. Such a framework would simplify the development of client and server programs to access the wide variety of astronomical archive systems. The primary services that are supplied by current systems include: catalog browsing, dataset retrieval, name resolution, and data analysis. The following issues (and probably more) need to be considered in establishing a standard set of client/server interfaces and protocols: Archive Access - dataset retrieval, delivery, file formats, data browsing, analysis, etc.; Catalog Access - database management systems, query languages, data formats, synchronous/asynchronous mode of operation, etc.; Interoperability - transaction/message protocols, distributed processing mechanisms (DCE, ONC/SunRPC, etc), networking protocols, etc.; Security - user registration, authorization/authentication mechanisms, etc.; Service Directory - service registration, lookup, port/task mapping, parameters, etc.; Software - public vs proprietary, client/server software, standard interfaces to client/server functions, software distribution, operating system portability, data portability, etc. Several archive/catalog groups, notably the Astrophysics Data System (ADS), are already working in many of these areas. In the process of developing StarView, which is the user interface to the Space Telescope Data Archive and Distribution Service (ST-DADS), these issues and the work of others were analyzed. A framework of standard interfaces for accessing services on any archive system which would benefit archive user and supplier alike is proposed.

Travisano, J. J.↗

A tensor approach to modeling of nonhomogeneous nonlinear systems

Model following control methodology plays a key role in numerous application areas. Cases in point include flight control systems and gas turbine engine control systems. Typical uses of such a design strategy involve the determination of nonlinear models which generate requested control and response trajectories for various commands. Linear multivariable techniques provide trim about these motions; and protection logic is added to secure the hardware from excursions beyond the specification range. This paper reports upon experience in developing a general class of such nonlinear models based upon the idea of the algebraic tensor product.

Yurkovich, S.↗

Technical Basis Related to the Posture of NASA’s Office of Safety and Mission Assurance for the Launch of Radioactive Material Other than Space Nuclear Systems: Volume 1–Overview of Analysis and Results

NASA has launched and reentered payloads containing radioactive material for over 50 years. The isotopes, their quantity, and their form have varied significantly. The handling of this material prior to its integration into the spacecraft at the launch Center (and after its return to Earth after flight, if applicable) falls under the purview of the Office of the Chief Health and Medical Officer, while after the radioactive material is integrated into the spacecraft at the launch Center, it falls under the purview of the Office of Safety and Mission Assurance’s (OSMA) Nuclear Flight Safety Program. Historically, OSMA concurrence was required for any launch or reentry involving radioactive material. However, OSMA recently revisited this posture due to changes in the Federal policy in this area, and the significant accrued experience. The current report represents the more quantitative study envisioned in the recent change in posture. More specifically, this document addresses the potential risks and other considerations associated with launching small quantities of radioactive material (below the level requiring the Federally-mandated process in National Security Presidential Memorandum- (NSPM-) 20, “Presidential Memorandum on Launch of Spacecraft Containing Space Nuclear Systems” (USG, 2019) to provide the technical basis for when such activities require OSMA concurrence versus notification, as it relates to nuclear flight safety.

Don Helton↗

Scalable Asset Discovery, Vulnerability Scanning, and Penetration Testing for Remote Sites and Wireless Spectrums Utilizing an Embedded Linux Plug - PwniPlug and the Raspberry Pi B+ as a Sample Pen Test

All devices attached to the NASA KSC network are subject to security vulnerability scanning and/or penetration testing. In today's changing environment, vulnerable and/or unprotected systems can easily be overlooked. Systems that are not properly managed can become a potential threat to the operational integrity of our systems and networks. This includes all NASA (internal and external) information systems within NASA KSC Internet Protocol (IP) address space, and NASA KSC facilities. The Office of the Chief Information Officer (OCIO) recommends that all NASA Centers and information systems be subject to penetration testing on a regular interval in accordance with the guidelines identified by the National Institute of Standards and Technology (NIST). (ITS-HBK-2810.04-02A) Protecting information and equipment at NASA is an area of increasing concern. In addition to the CPU's on the network; Supervisory, Control and Data Acquisition (SCADA) systems are especially vulnerable because these systems have lacked standards, use embedded controllers with little computational power and informal software, are connected to physical processes, have few operators, and are increasingly also being connected to corporate networks. The scope of work is comprised of several individual components which together build upon previous work by Drew Branch, NASA KSC Intern. The Pwn Plug is the selected COTS (Commercial-Off-The-Shelf) device chosen to test simplification of mandatory IT Security tasks. The device will be utilized to provide services to NASA KSC and enable an assessment of infrastructure soundness and regulatory compliance in an efficient, economical, and business responsive manner. The Pwn Plug is designed as a pen testing appliance which provides a hardware platform that can support commercial penetration testing efforts at significantly reduced costs. The expected outcomes are: 1) External Penetration Testing, 2) Social Engineering, 3) Procedural Documentation, 4) Recommended Remediation Action Plan, 5) System Retest & Remediation Attestation and 6) Final Reports, out briefing and Presentation. Due to physical and material constraints beyond intern and mentor control, the project was redefined as a working pen-test scenario. Limitations of lab availability and tools dictated an academic exercise. This report was developed within the scenario guidelines suggested by the project mentor. The guidelines were to be creative in developing a Pen Test program for a client.

Penetration Testing↗

Meeting the challenges of installing a mobile robotic system

The challenges of integrating a mobile robotic system into an application environment are many. Most problems inherent to installing the mobile robotic system fall into one of three categories: (1) the physical environment - location(s) where, and conditions under which, the mobile robotic system will work; (2) the technological environment - external equipment with which the mobile robotic system will interact; and (3) the human environment - personnel who will operate and interact with the mobile robotic system. The successful integration of a mobile robotic system into these three types of application environment requires more than a good pair of pliers. The tools for this job include: careful planning, accurate measurement data (as-built drawings), complete technical data of systems to be interfaced, sufficient time and attention of key personnel for training on how to operate and program the robot, on-site access during installation, and a thorough understanding and appreciation - by all concerned - of the mobile robotic system's role in the security mission at the site, as well as the machine's capabilities and limitations. Patience, luck, and a sense of humor are also useful tools to keep handy during a mobile robotic system installation. This paper will discuss some specific examples of problems in each of three categories, and explore approaches to solving these problems. The discussion will draw from the author's experience with on-site installations of mobile robotic systems in various applications. Most of the information discussed in this paper has come directly from knowledge learned during installations of Cybermotion's SR2 security robots. A large part of the discussion will apply to any vehicle with a drive system, collision avoidance, and navigation sensors, which is, of course, what makes a vehicle autonomous. And it is with these sensors and a drive system that the installer must become familiar in order to foresee potential trouble areas in the physical, technical, and human environment.

Decorte, Celeste↗

A Three-fold Outlook of the Ultra-Efficient Engine Technology Program Office (UEET)

The Ultra-Efficient Engine Technology (UEET) Office at NASA Glenn Research Center is a part of the Aeronautics Directorate. Its vision is to develop and hand off revolutionary turbine engine propulsion technologies that will enable future generation vehicles over a wide range of flight speeds. There are seven different technology area projects of UEET. During my tenure at NASA Glenn Research Center, my assignment was to assist three different areas of UEET, simultaneously. I worked with Kathy Zona in Education Outreach, Lynn Boukalik in Knowledge Management, and Denise Busch with Financial Management. All of my tasks were related to the business side of UEET. As an intern with Education Outreach I created a word search to partner with an exhibit of a Turbine Engine developed out of the UEET office. This exhibit is a portable model that is presented to students of varying ages. The word search complies with National Standards for Education which are part of every science, engineering, and technology teachers curriculum. I also updated a Conference Planning/Workshop Excel Spreadsheet for the UEET Office. I collected and inputted facility overviews from various venues, both on and off site to determine where to hold upcoming conferences. I then documented which facilities were compliant with the Federal Emergency Management Agency's (FEMA) Hotel and Motel Fire Safety Act of 1990. The second area in which I worked was Knowledge Management. a large knowledge management system online which has extensive documentation that continually needs reviewing, updating, and archiving. Knowledge management is the ability to bring individual or team knowledge to an organizational level so that the information can be stored, shared, reviewed, archived. Livelink and a secure server are the Knowledge Management systems that UEET utilizes, Through these systems, I was able to obtain the documents needed for archiving. My assignment was to obtain intellectual property including reports, presentations, or any other documents related to the project. My next task was to document the author, date of creation, and all other properties of each document. To archive these documents I worked extensively with Microsoft Excel. different financial systems of accounting such as the SAP business accounting system. I also learned the best ways to present financial data and shadowed my mentor as she presented financial data to both UEET's project management and the Resources Analysis and Management Office (RAMO). I analyzed the June 2004 financial data of UEET and used Microsoft Excel to input the results of the data. This process made it easier to present the full cost of the project in the month of June. In addition I assisted in the End of the Year 2003 Reconciliation of Purchases of UEET.

Graham, La Quilia E.↗