Refine Your Search

Search Results

Viewing 1 to 6 of 6
Technical Paper

A Status Report of NASA's On-line Project Information System (OPIS), a Tool for Analysis-Focused Data

The On-line Project Information System (OPIS) is a web-based database developed at NASA Ames Research Center (ARC) to improve information transfer and data availability for Exploration Life Support (ELS) projects. The tool enables users to investigate NASA technology development efforts, connect with knowledgeable experts, and to communicate important information. Within OPIS, Principal Investigators (PI's) post technical, administrative, and project participant information for other users to access through browse and search mechanisms. PI's are given technical data reporting requirements in the form of annual report templates, to assure that the information reported satisfies the most critical data needs of various ELS user groups. OPIS fulfills data and functionality needs of key user groups in the ELS Community through data solicitation, centralization, and distribution. The tool also circumvents data loss with ELS participant turnover.
Technical Paper

NASA's On-line Project Information System (OPIS) Attributes and Implementation

The On-line Project Information System (OPIS) is a LAMP-based (Linux, Apache, MySQL, PHP) system being developed at NASA Ames Research Center to improve Agency information transfer and data availability, largely for improvement of system analysis and engineering. The tool will enable users to investigate NASA technology development efforts, connect with experts, and access technology development data. OPIS is currently being developed for NASA's Exploration Life Support (ELS) Project. Within OPIS, NASA ELS Managers assign projects to Principal Investigators (PI), track responsible individuals and institutions, and designate reporting assignments. Each PI populates a “Project Page” with a project overview, team member information, files, citations, and images. PI's may also delegate on-line report viewing and editing privileges to specific team members. Users can browse or search for project and member information.
Technical Paper

Updating the Tools Used to Estimate Space Radiation Exposures for Operations: Codes, Models, and Interfaces

In order to estimate the exposure to a crew in space, there are three essential steps to be performed: first, the ambient radiation environment at the vehicle must be characterized; second, the mass distribution properties of the vehicle, including the crewmembers themselves must be developed, and third a model of the interactions of space radiations with matter must be employed in order to characterize the radiation field at the dose point of interest. The Space Radiation Analysis Group (SRAG) at the NASA, Johnson Space Center carries the primary responsibility for the operational radiation protection support function associated with manned space flight. In order to provide support during the various planning, execution, and analysis/recording phase activities associated with a given mission, tools have been developed to allow rapid, repeatable calculations of exposure on orbit.
Technical Paper

Delivery of Servicing & Performance Checkout Equipment to the International Space Station Joint Airlock to Support Extravehicular Activity

In July 2001, during Space Shuttle Flight 7A, the Joint Airlock was added to the International Space Station (ISS) and utilized in performing the first extravehicular activity (EVA) from the ISS. Unlike previous airlock designs built by the United States or Russia, the Joint Airlock provides the ISS with the unique capability for performing EVAs utilizing either U.S. or Russian spacesuits. This EVA capability is made possible by the use of U.S.- and Russian- manufactured hardware items referred to as Servicing and Performance Checkout Equipment (SPCE) located in both the Joint Airlock's Equipment and Crew Locks. This paper provides a description for each SPCE item along with a summary of the requirements and capabilities provided in support of EVA events from the ISS Joint Airlock.
Technical Paper

Immobilized Microbe Microgravity Water Processing System (IMMWPS) Flight Experiment Integrated Ground Test Program

This paper provides an overview of the IMMWPS Integrated Ground Test Program, completed at the NASA Johnson Space Center (JSC) during October and November 2001. The JSC Crew and Thermal Systems Division (CTSD) has developed the IMMWPS orbital flight experiment to test the feasibility of a microbe-based water purifier for use in zero-gravity conditions. The IMMWPS design utilizes a Microbial Processor Assembly (MPA) inoculated with facultative anaerobes to convert organic contaminants in wastewater to carbon dioxide and biomass. The primary purpose of the ground test program was to verify functional operations and procedures. A secondary objective was to provide initial ground data for later comparison to on-orbit performance. This paper provides a description of the overall test program, including the test article hardware and the test sequence performed to simulate the anticipated space flight test program. In addition, a summary of significant results from the testing is provided.
Technical Paper

ISS ECLS System Analysis Software Tools - An Overview and Assessment

There have been many software programs that have provided simulations for the performance and operation of the Environmental Control and Life Support Subsystems (ECLSS) in the International Space Station (ISS) and in the Space Shuttle. These programs have been applied for purposes in system analysis, flight analysis, and ECLSS studies. Flight and system analysis tasks are deemed important. Therefore, more manpower and resources added for such work is considered beneficial. System analysis covers design and trouble-shooting, the validation of Flight Rules, and the contingency analysis. During the engineering design phase, ECLSS modelers predict the performance and interaction of units in a process train. Simulation results can be useful in estimating equipment sizes and costs. This article has also used two examples to illustrate that many Flight Rules need to be validated using properly selected integrated programs.