Search NASA⌕ Search

SEARCH · Search NASA

Results for “commonality”

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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

A Crew and Logistics Lander for the Common Habitat Architecture

The Common Habitat Architecture is a conceptual study that explores the use of a large habitat derived from the Space Launch System (SLS) liquid oxygen tank as a core habitation element that can be used for crew missions or training in 0g, 1/6g, 3/8g, and 1g. This is not part of current NASA Artemis mission planning, but instead represents an architecture that could potentially follow after the Artemis missions and initial human Mars landings. This architecture leverages Starship-derived vehicles for crew landing on and ascent from the Moon and Mars in support of long-duration surface missions with pressurized crew transfer baselined as a nominal capability. This is not the Human Landing System variant of Starship but represents a number of modifications to enable long-duration surface missions with an eight-person crew size. A rapid brainstorming study was conducted in February of 2021, using only public data, to identify options to deliver the 90-ton Common Habitat to the surface and emplace it at the intended habitation site. This study compared three lunar lander concepts and three Mars lander concepts before ultimately selecting the SpaceX Starship as the most viable lander. The Common Habitat Architecture assumes that this Starship variant can further be modified for crew and cargo delivery, assuming that the use of a common system will lead to cost benefits. It is assumed that the Starship will expend too much propellant in landing crew and logistics to be able to launch, given the assumed absence of surface propellant production. Consequently, a separable ascent stage is used for crew ascent. The pressurized elements of this modified Starship are discussed: Starship Ascent Module, Airlock, Transfer Tunnel, Pressurized Crew Transfer Module, and Logistics Modules. For each element, a description, dimensions, rough mass estimates, core capabilities, and design features are presented. Key mechanisms and internal structures of the starship are also discussed. This will include flame diverters for the ascend module, the orbital docking hatch, Pressurized Crew Transfer Module Garage door, Starship Ascent Module fairing, flame diverter blow-out panels, Pressurized Crew Transfer Module lift system, logistics module lift system, contingency crew ascent via the logistics module lift system, internal catwalks, and structural interfaces. Concept of Operations will be discussed for both Moon and Mars. This will include in-space crew rendezvous and transfer, crewed landing, shirtsleeve crew transfer, crew departure, contingency surface operations, and final element disposition. Key differences for Mars will be discussed, such as the Martian atmosphere, dust storms, the absence of crew handover, and Deep Space Exploration Vehicle rendezvous. Contingency microgravity maintenance access will also be discussed. This work will demonstrate viable pressurized crew transfer with a Starship-based lander architecture. Forward work includes Garage lighting and camera systems, Starship Ascent Module propulsion system and docking port trades, contingency habitation trades, and mass/power equipment estimation. Finally, forward work includes developing a heavy cargo return system derived from the Crew and Logistics Starship. The goal of this system is the return of at least 10,000 kg payloads from the surfaces of the Moon and Mars.

Lunar Lander↗
NASA NTRS1988

Analyzing Commonality In A System

Cost decreased by use of fewer types of parts. System Commonality Analysis Tool (SCAT) computer program designed to aid managers and engineers in identifying common, potentially common, and unique components of system. Incorporates three major functions: program for creation and maintenance of data base, analysis of commonality, and such system utilities as host-operating-system commands and loading and unloading of data base. Produces reports tabulating maintenance, initial configurations, and expected total costs. Written in FORTRAN 77.

Pacheco, Alfred↗
NASA NTRS1988

Space station commonality analysis

This study was conducted on the basis of a modification to Contract NAS8-36413, Space Station Commonality Analysis, which was initiated in December, 1987 and completed in July, 1988. The objective was to investigate the commonality aspects of subsystems and mission support hardware while technology experiments are accommodated on board the Space Station in the mid-to-late 1990s. Two types of mission are considered: (1) Advanced solar arrays and their storage; and (2) Satellite servicing. The point of departure for definition of the technology development missions was a set of missions described in the Space Station Mission Requirements Data Base. (MRDB): TDMX 2151 Solar Array/Energy Storage Technology; TDMX 2561 Satellite Servicing and Refurbishment; TDMX 2562 Satellite Maintenance and Repair; TDMX 2563 Materials Resupply (to a free-flyer materials processing platform); TDMX 2564 Coatings Maintenance Technology; and TDMX 2565 Thermal Interface Technology. Issues to be addressed according to the Statement of Work included modularity of programs, data base analysis interactions, user interfaces, and commonality. The study was to consider State-of-the-art advances through the 1990s and to select an appropriate scale for the technology experiments, considering hardware commonality, user interfaces, and mission support requirements. The study was to develop evolutionary plans for the technology advancement missions.

Source record↗
NASA NTRS1989

Restrictive loads powered by separate or by common electrical sources

In designing a multiple load electrical system, the designer may wish to compare the performance of two setups: a common electrical source powering all loads, or separate electrical sources powering individual loads. Three types of electrical sources: an ideal voltage source, an ideal current source, and solar cell source powering resistive loads were analyzed for their performances in separate and common source systems. A mathematical proof is given, for each case, indicating the merit of the separate or common source system. The main conclusions are: (1) identical resistive loads powered by ideal voltage sources perform the same in both system setups, (2) nonidentical resistive loads powered by ideal voltage sources perform the same in both system setups, (3) nonidentical resistive loads powered by ideal current sources have higher performance in separate source systems, and (4) nonidentical resistive loads powered by solar cells have higher performance in a common source system for a wide range of load resistances.

Appelbaum, J.↗
NASA NTRS1989

Common source cascode amplifiers for integrating IR-FPA applications

Space based astronomical infrared measurements present stringent performance requirements on the infrared detector arrays and their associated readout circuitry. To evaluate the usefulness of commercial CMOS technology for astronomical readout applications a theoretical and experimental evaluation was performed on source follower and common-source cascode integrating amplifiers. Theoretical analysis indicates that for conditions where the input amplifier integration capacitance is limited by the detectors capacitance the input referred rms noise electrons of each amplifier should be equivalent. For conditions of input gate limited capacitance the source follower should provide lower noise. Measurements of test circuits containing both source follower and common source cascode circuits showed substantially lower input referred noise for the common-source cascode input circuits. Noise measurements yielded 4.8 input referred rms noise electrons for an 8.5 minute integration. The signal and noise gain of the common-source cascode amplifier appears to offer substantial advantages in acheiving predicted noise levels.

Woolaway, James T.↗
NASA NTRS1989

Space biology initiative program definition review. Trade study 4: Design modularity and commonality

The relative cost impacts (up or down) of developing Space Biology hardware using design modularity and commonality is studied. Recommendations for how the hardware development should be accomplished to meet optimum design modularity requirements for Life Science investigation hardware will be provided. In addition, the relative cost impacts of implementing commonality of hardware for all Space Biology hardware are defined. Cost analysis and supporting recommendations for levels of modularity and commonality are presented. A mathematical or statistical cost analysis method with the capability to support development of production design modularity and commonality impacts to parametric cost analysis is provided.

Jackson, L. Neal↗
NASA NTRS1993

Comparison of GPS and GLONASS common-view time transfers

It was already shown than even with a simple daily averaging of GLONASS data at each site, continental GLONASS time transfer can be achieved at a level of several tens of nanoseconds. A further step is to carry out observations of GLONASS satellites by the common-view method. A comparison of GPS and GLONASS common-view time transfers between Russia and Western Europe are reported. At each site, a GPS receiver and a GLONASS receiver are connected to the same atomic clock. Both GPS receivers are of NBS type and the GLONASS receivers are of type A-724. As GPS common-view time transfer between Sevres and Mendeleevo is accomplished at a level of a few nanoseconds in precision, it gives an excellent reference with which to evaluate the performance of GLONASS common-view time transfer.

Lewandowski, W.↗
NASA NTRS1995

Implementation of a standard format for GPS common view data

A new format for standardizing common view time transfer data, recommended by the Consultative Committee for the Definition of the Second, is being implemented in receivers commonly used for contributing data for the generation of International Atomic Time. We discuss three aspects of this new format that potentially improve GPS common-view time transfer: (1) the standard specifies the method for treating short term data, (2) it presents data in consistent formats including needed terms not previously available, and (3) the standard includes a header of parameters important for the GPS common-view process. In coordination with the release of firmware conforming to this new format the Bureau International des Poids et Mesures will release future international track schedules consistent with the new standard.

Weiss, Marc A.↗
NASA NTRS2005

The GPM Common Calibrated Brightness Temperature Product

The Global Precipitation Measurement (GPM) project will provide a core satellite carrying the GPM Microwave Imager (GMI) and will use microwave observations from a constellation of other satellites. Each partner with a satellite in the constellation will have a calibration that meets their own requirements and will decide on the format to archive their brightness temperature (Tb) record in GPM. However, GPM multi-sensor precipitation algorithms need to input intercalibrated Tb's in order to avoid differences among sensors introducing artifacts into the longer term climate record of precipitation. The GPM Common Calibrated Brightness Temperature Product is intended to address this problem by providing intercalibrated Tb data, called "Tc" data, where the "c" stands for common. The precipitation algorithms require a Tc file format that is both generic and flexible enough to accommodate the different passive microwave instruments. The format will provide detailed information on the processing history in order to allow future researchers to have a record of what was done. The format will be simple, including the main items of scan time, latitude, longitude, and Tc. It will also provide spacecraft orientation, spacecraft location, orbit, and instrument scan type (cross-track or conical). Another simplification is to store data in real numbers, avoiding the ambiguity of scaled data. Finally, units and descriptions will be provided in the product. The format is built on the concept of a swath, which is a series of scans that have common geolocation and common scan geometry. Scan geometry includes pixels per scan, sensor orientation, scan type, and incidence angles. The Tc algorithm and data format are being tested using the pre-GPM Precipitation Processing System (PPS) software to generate formats and 1/0 routines. In the test, data from SSM/I, TMI, AMSR-E, and WindSat are being processed and written as Tc products.

Stout, John↗
NASA NTRS2005

Common Badging and Access Control System (CBACS)

This slide presentation presents NASA's Common Badging and Access Control System. NASA began a Smart Card implementation in January 2004. Following site surveys, it was determined that NASA's badging and access control systems required upgrades to common infrastructure in order to provide flexibly, usability, and return on investment prior to a smart card implantation. Common Badging and Access Control System (CBACS) provides the common infrastructure from which FIPS-201 compliant processes, systems, and credentials can be developed and used.

Dischinger, Portia↗
NASA NTRS2009

Multi-Mission Suitability of the NASA Ames Modular Common Bus

The obvious advantages of small spacecraft - their lower cost structure and the rapid development schedule - have enabled a large number of missions in the past. However, most of these missions have been focused on Earth observation from low Earth orbits. In 2006, the Small Spacecraft Division at the NASA Ames Research Center began the development of the Modular Common Bus, a spacecraft capable of delivering scientifically and technically useful payloads to a variety of destinations within 0.1 AU around the Earth. The core technologies used in the Common Bus design are a composite structure with body-mounted solar cells, an integrated avionics unit, and a high performance bipropellant propulsion system. Due to its modular approach, the Common Bus can be adapted to fit specific mission needs while still using a standardized and qualified set of components. Additionally a number of low cost launch vehicles are supported, resulting in overall mission costs of around $150M including the launch vehicle but excluding the science payloads. This significant reduction in cost and the shorter development time would enable NASA to conduct more frequent exploration missions within its budget and timeframe constraints, compared to the status quo. In this paper the suitability of the Common Spacecraft Bus for four different exploration scenarios is analyzed. These scenarios include a lunar orbiter, a lunar lander, a mission to a Sun-Earth Libration Point, and a rendezvous mission to a Near Earth Object. For each scenario, a preliminary design reference mission is developed and key design parameters for the spacecraft are determined.

Tietz, Sascha↗
NASA NTRS2010

Common Cause Failure Modeling: Aerospace Versus Nuclear

Aggregate nuclear plant failure data is used to produce generic common-cause factors that are specifically for use in the common-cause failure models of NUREG/CR-5485. Furthermore, the models presented in NUREG/CR-5485 are specifically designed to incorporate two significantly distinct assumptions about the methods of surveillance testing from whence this aggregate failure data came. What are the implications of using these NUREG generic factors to model the common-cause failures of aerospace systems? Herein, the implications of using the NUREG generic factors in the modeling of aerospace systems are investigated in detail and strong recommendations for modeling the common-cause failures of aerospace systems are given.

Stott, James E.↗
NASA NTRS2012

Extensible Adaptable Simulation Systems: Supporting Multiple Fidelity Simulations in a Common Environment

Common practice in the development of simulation systems is meeting all user requirements within a single instantiation. The Joint Polar Satellite System (JPSS) presents a unique challenge to establish a simulation environment that meets the needs of a diverse user community while also spanning a multi-mission environment over decades of operation. In response, the JPSS Flight Vehicle Test Suite (FVTS) is architected with an extensible infrastructure that supports the operation of multiple observatory simulations for a single mission and multiple mission within a common system perimeter. For the JPSS-1 satellite, multiple fidelity flight observatory simulations are necessary to support the distinct user communities consisting of the Common Ground System development team, the Common Ground System Integration & Test team, and the Mission Rehearsal Team/Mission Operations Team. These key requirements present several challenges to FVTS development. First, the FVTS must ensure all critical user requirements are satisfied by at least one fidelity instance of the observatory simulation. Second, the FVTS must allow for tailoring of the system instances to function in diverse operational environments from the High-security operations environment at NOAA Satellite Operations Facility (NSOF) to the ground system factory floor. Finally, the FVTS must provide the ability to execute sustaining engineering activities on a subset of the system without impacting system availability to parallel users. The FVTS approach of allowing for multiple fidelity copies of observatory simulations represents a unique concept in simulator capability development and corresponds to the JPSS Ground System goals of establishing a capability that is flexible, extensible, and adaptable.

McLaughlin, Brian J.↗
NASA NTRS2015

Common Cause Failure Modeling

Common Cause Failures (CCFs) are a known and documented phenomenon that defeats system redundancy. CCFS are a set of dependent type of failures that can be caused by: system environments; manufacturing; transportation; storage; maintenance; and assembly, as examples. Since there are many factors that contribute to CCFs, the effects can be reduced, but they are difficult to eliminate entirely. Furthermore, failure databases sometimes fail to differentiate between independent and CCF (dependent) failure and data is limited, especially for launch vehicles. The Probabilistic Risk Assessment (PRA) of NASA's Safety and Mission Assurance Directorate at Marshall Space Flight Center (MFSC) is using generic data from the Nuclear Regulatory Commission's database of common cause failures at nuclear power plants to estimate CCF due to the lack of a more appropriate data source. There remains uncertainty in the actual magnitude of the common cause risk estimates for different systems at this stage of the design. Given the limited data about launch vehicle CCF and that launch vehicles are a highly redundant system by design, it is important to make design decisions to account for a range of values for independent and CCFs. When investigating the design of the one-out-of-two component redundant system for launch vehicles, a response surface was constructed to represent the impact of the independent failure rate versus a common cause beta factor effect on a system's failure probability. This presentation will define a CCF and review estimation calculations. It gives a summary of reduction methodologies and a review of examples of historical CCFs. Finally, it presents the response surface and discusses the results of the different CCFs on the reliability of a one-out-of-two system.

Hark, Frank↗
NASA NTRS2016

Common Cause Failure Modeling

Common Cause Failures (CCFs) are a known and documented phenomenon that defeats system redundancy. CCFS are a set of dependent type of failures that can be caused by: system environments; manufacturing; transportation; storage; maintenance; and assembly, as examples. Since there are many factors that contribute to CCFs, the effects can be reduced, but they are difficult to eliminate entirely. Furthermore, failure databases sometimes fail to differentiate between independent and CCF (dependent) failure and data is limited, especially for launch vehicles. The Probabilistic Risk Assessment (PRA) of NASA's Safety and Mission Assurance Directorate at Marshal Space Flight Center (MFSC) is using generic data from the Nuclear Regulatory Commission's database of common cause failures at nuclear power plants to estimate CCF due to the lack of a more appropriate data source. There remains uncertainty in the actual magnitude of the common cause risk estimates for different systems at this stage of the design. Given the limited data about launch vehicle CCF and that launch vehicles are a highly redundant system by design, it is important to make design decisions to account for a range of values for independent and CCFs. When investigating the design of the one-out-of-two component redundant system for launch vehicles, a response surface was constructed to represent the impact of the independent failure rate versus a common cause beta factor effect on a system's failure probability. This presentation will define a CCF and review estimation calculations. It gives a summary of reduction methodologies and a review of examples of historical CCFs. Finally, it presents the response surface and discusses the results of the different CCFs on the reliability of a one-out-of-two system.

Hark, Frank↗
NASA NTRS2018

Toward a Common Earth Data Publication Framework

Data publication is an essential activity for all data archives. Each of NASA's twelve Distributed Active Archive Centers (DAACs) have established publication workflows which account for the heterogeneous suite of missions, instruments, data providers, and datasets managed within the Earth Observation System Data and Information System (EOSDIS) program. Some aspects of data publication vary across DAACs: workflows range from manual to automatic, terms used to describe publication elements differ, and systems used to publish and manage data vary. Despite these differences, the DAAC data publication processes are generally the same: obtain the data and related information from data providers, describe the data with metadata and documentation, and release the data for access by the user community. In order to improve consistency and reduce the time required to publish data, we have developed a cross-DAAC initiative called the Common Earthdata Publication Framework (Earthdata Pub). Earthdata Pub seeks to: standardize communications and interactions with data providers; identify and standardize common workflows and steps in the data publication process; and design/implement a front-end system with features that include a common web interface, email & status tracking, and common application programming interfaces (APIs) to communicate with various DAAC-specific software components (services and applications) on the back-end. We will present the latest updates on this effort's progress and future plans.

data publication↗
NASA NTRS2019

Common Probe Design Study and Follow-On Activities

The Common Probe Study was funded by the NASA's Planetary Science Division in the Science Mission Directorate in 2018 to investigate the feasibility of a common aeroshell design for atmospheric probe missions at Venus, Jupiter, Saturn, Uranus, and Neptune. The study involved 4 NASA Centers: Ames Research Center, Goddard Space Flight Center, Langley Research Center, and the Jet Propulsion Laboratory. The common aeroshell design that was studied was a 400 kg, 1.5 m diameter, 45-degree sphere cone shape with a high density heatshield material (Heatshield for Extreme Entry Environments Technology, or HEEET) and a parachute system to extract the descent vehicle. This size of aeroshell could accommodate a descent vehicle of 0.75 m diameter, which could encompass both Tier 1 and Tier 2 science instruments at each of the 5 destinations. Study methodology: First, a notional payload of instruments for each destination was defined based on the top priority measurements indicated by the Planetary Science Decadal Survey. Steep and shallow entry flight path angles (EFPA) were defined for each planet based on qualification and operational g-load limits for current, state-of-the-art instruments. Interplanetary trajectories were then identified that bounded the EFPA range.Next, 3-DoF simulations for entry trajectories were run using the entry state vectors from the interplanetary trajectories. Conical ribbon parachutes were sized based on heatshield separation dynamics. Aero-heating correlations were used to generate stagnation point convective and radiative heat flux profiles. High fidelity thermal response models for various TPS materials were used to size stagnation point thicknesses, with margins based on previous studies. Backshell TPS masses were assumed based on scaled heat fluxes from the heatshield and also from previous mission concepts.Based on these analyses, we have found that the common design is applicable for atmospheric probe missions for 4 out of the 5 destinations. Because of the unique gravity well for Jupiter, the entry environments are more severe resulting in heat loads an order of magnitude higher than for the other destinations.The next step is to determine what follow-on activities NASA should engage in. A questionnaire for the atmospheric probe community has been developed, with a focus on what size of aeroshell should be further analyzed (smaller or same diameter), and what incentives would make using such an aeroshell, if assembled and available, desirable to mission proposers.Preliminary results from this questionnaire will be presented.

Hwang, Helen H.↗
NASA NTRS2019

Common Habitat for Long Duration Transit and Surface Operations

This concept is based on the Skylab II concept, which proposes using a SLS propellant tank as the primary structure of a habitat. Common Habitat takes this a step further, proposing an interior architecture that is equally viable as a lunar surface hab, transit hab, and Mars surface hab, thus enabling a single development to support all three long duration habitat roles. Common Habitat has been pursued by the PI and co-investigators at MSFC and other centers in a spare time / funding available basis, often with heavy student intern support. Student resources have developed preliminary concepts, but these models must be refined to reflect accurate vehicle subsystems, utilities, stowage, workstations, and other crew systems. This investigation applies NASA civil servant and contractor expertise to correct errors in the most recent student concepts in order to prepare them for future human-in-the-loop evaluations to determine the most viable configuration for a Common Habitat. In prior studies there was never an opportunity to trade both crew size and internal orientation. Prior work has been a series of point designs with inconsistent design constraints, making apples to apples comparisons impossible. The most recent student work produced CAD models of four habitat variants for future use in a trade study, but the student products contain model construction and geometry errors, inaccurate subsystems design and placement, and unrealistic structural elements and outfitting. These must be corrected before the models can be moved into a VR environment for humanin- the-loop testing. Through consultation with SMEs throughout the Agency, the fidelity of these designs will be upgraded to a level of quality sufficient to make a comparative analysis of crew size sensitivity and internal orientation. The product of this activity is four upgraded CAD models, each reflecting a different configuration of the Common Habitat. One is a horizontal configuration using the full length of the SLS LOX tank. One is a vertical configuration using the same tank dimensions. The third is a horizontal configuration using a truncated SLS LOX tank (half the barrel length). The fourth is a vertical configuration of the half-length SLS LOX tank.

Howard, Robert L.↗