Search NASA⌕ Search

SEARCH · Search NASA

Results for “NASA requirements”

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 NTRS2001

A Stream lined Approach for the Payload Customer in Identifying Payload Design Requirements

NASA payload developers from across various disciplines were asked to identify areas where process changes would simplify their task of developing and flying flight hardware. Responses to this query included a central location for consistent hardware design requirements for middeck payloads. The multidisciplinary team assigned to review the numerous payload interface design documents is assessing the Space Shuttle middeck, the SPACEHAB Inc. locker, as well as the MultiPurpose Logistics Module (MPLM) and EXpedite the PRocessing of Experiments to Space Station (EXPRESS) rack design requirements for the payloads. They are comparing the multiple carriers and platform requirements and developing a matrix which illustrates the individual requirements, and where possible, the envelope that encompasses all of the possibilities. The matrix will be expanded to form an overall envelope that the payload developers will have the option to utilize when designing their payload's hardware. This will optimize the flexibility for payload hardware and ancillary items to be manifested on multiple carriers and platforms with minimal impact to the payload developer.

Miller, Ladonna J.↗
NASA NTRS2007

Exploration Launch Projects RS-68B Engine Requirements for NASA's Heavy Lift Ares V

NASA's Vision for Exploration requires a safe, efficient, reliable, and versatile launch vehicle capable of placing large payloads into Earth orbit for transfer to the Moon and destinations beyond. The Ares V Cargo Launch Vehicle (CaLV) will provide this heavy lift capability. The Ares V launch concept is shown in Fig. 1. When it stands on the launch pad at Kennedy Space Center late in the next decade, the Ares V stack will be almost 360 feet tall. As currently envisioned, it will lift 133,000 to 144,000 pounds to trans-lunar injection, depending on the length of loiter time on Earth orbit. This presentation will provide an overview of the Constellation architecture, the Ares launch vehicles, and, specifically, the latest developments in the RS-68B engine for the Ares V.

Sumrall, John P.↗
NASA NTRS1990

Compatibility of the Space Station Freedom life sciences research centrifuge with microgravity requirements

NASA is developing a Life Sciences Centrifuge Facility for Space Station Freedom. In includes a 2.5-meter artificial gravity Bioresearch Centrifuge (BC), which is perhaps the most critical single element in the life sciences space research program. It rotates continuously at precise selectable rates, and utilizes advanced reliable technologies to reduce vibrations. Three disturbance types are analyzed using a current Space Station Freedom dynamic model in the 0.0 to 5.0 Hz range: sinusoidal, random, and transient. Results show that with proper selection of proven design techniques, BC vibrations are compatible with requirements.

Hasha, Martin D.↗
NASA NTRS2015

Mars2020 Entry, Descent, and Landing Instrumentation (MEDLI2): Science Objectives and Instrument Requirements

NASAs exploration and technology roadmaps call for capability advancements in Mars entry, descent, and landing (EDL) systems to enable increased landed mass, a higher landing precision, and a wider planetary access. It is also recognized that these ambitious EDL performance goals must be met while maintaining a low mission risk in order to pave the way for future human missions. As NASA is engaged in developing new EDL systems and technologies via testing at Earth, instrumentation of existing Mars missions is providing valuable engineering data for performance improvement, risk reduction, and an improved definition of entry loads and environment. The most notable recent example is the Mars Entry, Descent and Landing Instrument (MEDLI) suite hosted by Mars Science Laboratory for its entry in Aug 2012. The MEDLI suite provided a comprehensive dataset for Mars entry aerodynamics, aerothermodynamics and thermal protection system (TPS) performance. MEDLI data has since been used for unprecedented reconstruction of aerodynamic drag, vehicle attitude, in-situ atmospheric density, aerothermal heating, and transition to turbulence, in-depth TPS performance and TPS ablation. [1,2] In addition to validating predictive models, MEDLI data has demonstrated extra margin available in the MSL forebody TPS, which can potentially be used to reduce vehicle parasitic mass. The presentation will introduce a follow-on MEDLI instrumentation suite (called MEDLI2) that is being developed for Mars-2020 mission. MEDLI2 has an enhanced scope that includes backshell instrumentation, a wider forebody coverage, and instruments that specifically target supersonic aerodynamics. Similar to MEDLI, MEDLI2 uses thermal plugs with embedded thermocouples and ports through the TPS to measure surface pressure. MEDLI2, however, also includes heat flux sensors in the backshell and a low range pressure transducer to measure afterbody pressure.

Aerothermodynamics↗
NASA NTRS1981

User requirements for NASA data base management systems. Part 1: Oceanographic discipline

Generic oceanographic user requirements were collected and analyzed for use in developing a general multipurpose data base management system for future missions of the Office of Space and Terrestrial Applications (OSTA) of NASA. The collection of user requirements involved; studying the state-of-the-art technology in data base management systems; analyzing the results of related studies; formulating a viable and diverse list of scientists to be interviewed; developing a presentation format and materials; and interviewing oceanographic data users. More effective data management systems are needed to handle the increasing influx of data.

Fujimoto, B.↗
NASA NTRS1989

Electrical, Electronic, and Electromechanical (EEE) parts management and control requirements for NASA space flight programs

This document establishes electrical, electronic, and electromechanical (EEE) parts management and control requirements for contractors providing and maintaining space flight and mission-essential or critical ground support equipment for NASA space flight programs. Although the text is worded 'the contractor shall,' the requirements are also to be used by NASA Headquarters and field installations for developing program/project parts management and control requirements for in-house and contracted efforts. This document places increased emphasis on parts programs to ensure that reliability and quality are considered through adequate consideration of the selection, control, and application of parts. It is the intent of this document to identify disciplines that can be implemented to obtain reliable parts which meet mission needs. The parts management and control requirements described in this document are to be selectively applied, based on equipment class and mission needs. Individual equipment needs should be evaluated to determine the extent to which each requirement should be implemented on a procurement. Utilization of this document does not preclude the usage of other documents. The entire process of developing and implementing requirements is referred to as 'tailoring' the program for a specific project. Some factors that should be considered in this tailoring process include program phase, equipment category and criticality, equipment complexity, and mission requirements. Parts management and control requirements advocated by this document directly support the concept of 'reliability by design' and are an integral part of system reliability and maintainability. Achieving the required availability and mission success objectives during operation depends on the attention given reliability and maintainability in the design phase. Consequently, it is intended that the requirements described in this document are consistent with those of NASA publications, 'Reliability Program Requirements for Aeronautical and Space System Contractors,' NHB 5300.4(1A-l); 'Maintainability Program Requirements for Space Systems,' NHB 5300.4(1E); and 'Quality Program Provisions for Aeronautical and Space System Contractors,' NHB 5300.4(1B).

Source record↗
NASA NTRS2023

Towards Streamlining Auditing for Compliance With Requirements in Open-Source Software at NASA

Context: NASA requires all software to meet several requirements (NPR 7150.2) depending on software criticality. The instantiation of these requirements may vary per project; however, once decided upon, projects must undergo audits to evaluate compliance with these requirements. Aim: We propose that audit effort can be reduced when requirements are realized by leveraging commonly used open-source infrastructure for version control, issue tracking and continuous integration, and the generated records are analyzed using a repository mining software tool to quantify process compliance. Method: We perform a case study in the NASA-funded Copilot project, utilizing Kaiaulu, a repository mining software tool. We define four software compliance metrics based on the Copilot’s requirements, and analyze their impact on source code quality. Results: Our work demonstrates how it is possible to leverage existing open source tools and platforms to facilitate software certification and qualification, and to streamline the auditing process required even when stringent requirements must be enforced. Conclusion: Together, both project and tool can be utilized to visualize project compliance, and metrics can be defined to more easily identify process irregularities to minimize auditing efforts. Project Repository: github.com/Copilot-Language/copilot Tool Repository: github.com/sailuh/kaiaulu

code-quality↗
NASA NTRS2017

The Evolution of Planetary Protection Implementation on Mars Landed Missions

NASA has developed requirements dedicated to the prevention of forward and backward contamination during space exploration. Historically, international agreements provided guidelines to prevent contamination of the Moon and other celestial bodies, as well as the Earth (e.g., sample return missions). The UN Outer Space Treaty was established in 1967 and the Committee on Space Research (COSPAR) maintains a planetary protection policy complying with Article IX of this treaty. By avoiding forward contamination, the integrity of scientific exploration is preserved. Planetary Protection mission requirements are levied on missions to control contamination. These requirements are dependent on the science of the mission and on the celestial bodies encountered or targeted along the way. Consequently, categories are assigned to missions, and specific implementation plans are developed to meet the planetary protection requirements. NASA missions have evolved over time with increasingly more demanding scientific objectives and more complex flight systems to achieve those objectives and, thus, planetary protection methods and processes used for implementation have become much more intricate, complicated, and challenging. Here, we will portray the evolution of planetary protection implementation at JPL in several important areas throughout the course of NASA sponsored robotic Mars lander or rover missions, starting from Mars Pathfinder through the beginning of Mars 2020. Highlighted in the discussion will be process changes in planetary protection requirements development and flow down. Development and implementation of new and improved methods used in the reduction of spacecraft bioburden will be discussed as well as approaches and challenges that come along with setting up remote laboratories to perform bioassays. The consequences and forward planning of delays on missions will be highlighted as well as lessons learned on the impact of communication and training in achieving planetary protection requirements. The evolution of methods used for the detection of microbial bioburden on spacecraft hardware will be considered. These methods use standard microbiology as well as the adaptation of advances in biotechnology, molecular biology, and bioinformatics. Technical approaches developed for the prevention of contamination and recontamination of hardware during Assembly, Test, and Launch Operations will be discussed.

Kazarians, Gayane A.↗
NASA NTRS1990

The reactive bed plasma system for contamination control

The contamination control capabilities of the Reactive Bed Plasma (RBP) system is described by delineating the results of toxic chemical composition studies, aerosol filtration work, and other testing. The RBP system has demonstrated its capabilities to decompose toxic materials and process hazardous aerosols. The post-treatment requirements for the reaction products have possible solutions. Although additional work is required to meet NASA requirements, the RBP may be able to meet contamination control problems aboard the Space Station.

Birmingham, Joseph G.↗
NASA NTRS2023

Wildfire-fighting Use Case Requirements to Monitor

In this technical report, we provide requirements for a wildfire-fighting use-case, towards the Safety Demonstrator 1. The use case will incorporate ground and airborne assets operating in a coordinated fashion, and will comprise five activities, from detection to the execution of the initial attack. Depending on the activity and the data involved, the requirements identified may be non-probabilistic or probabilistic. In both cases, we first identify some of the requirements we wish to monitor, and then present a formalization using the language of requirements of the NASA requirements elicitation tool FRET. To formalize probabilistic requirements, we use a novel extension to FRET’s requirements language that incorporates notions of probability, and discuss how requirements can be translated into existing probabilistic temporal logics like PCTL. We exemplify how some of the requirements presented can be monitored using the existing tools Ogma and Copilot. We close with a summary and future directions.

Requirements↗
NASA NTRS1966

Support of NASA quality requirements by defense contract administration services regions

Defense Contract Administration Services Regions (DCASR) quality assurance personnel performing under NASA Letters of Delegation must work closely with the assigned technical representative of the NASA centers. It is realized that technical personnel from the NASA Centers cannot make on-site visits as frequently as they would like to. However, DCASR quality assurance personnel would know the assigned NASA technical representative and should contact him when problems arise. The technical representative is the expert on the hardware and should be consulted on any problem area. It is important that the DCASR quality assurance personnel recommend to the delegating NASA Center any new or improved methods of which they may be aware which would assist in achieving the desired quality and reliability in NASA hardware. NASA expects assignment of competent personnel in the Quality Assurance functional area and is not only buying the individual's technical skill, but also his experience. Suggestions by field personnel can many times up-grade the quality or the hardware.

Farrar, Hiram D.↗
NASA NTRSDate not supplied

Lunar Surface Position Determination using Perceived Signal Strength

The purpose of this project is to evaluate the feasibility of transmitters and receivers on the lunar surface for Position Determination (PD) without any form of lunar Global Positioning System (GPS). The early Artemis program may lack GPS satellites orbiting the Moon, and it is critical that activities with the lander, rover, and crew EVA identify their position on the lunar surface at all times. This project creates a prototype system that trilaterates user position based upon the perceived signal from at least 3 nearby transmission towers, called “Lunar Access Points”. The application of perceived signal strength for surface PD has historically been used in terrestrial systems such as Long Range Navigation (LORAN), which was popular with the maritime industry prior to the Global Positioning System (GPS). The ease of installing such a local system for early Artemis missions provides a critical resource until satellite-based position determination systems are deployed. A surface-based PD can also be used in GPS-denied environments such as deep craters or lava tubes where satellite visibility is compromised. By demonstrating the basic capability of surface PD, this student team has learned about issues with power, distance, thermal, dust, radiation, data processing, and communication problems applicable to the lunar surface. This knowledge can feed into future NASA requirements to improve the capability of a LunaNET implementation for the Artemis program. This project follows 10 years of successful collaboration between NASA JSC/ARES, Texas Space, Technology, Applications and Research (T STAR) and Texas A&M University in a Public, Private, Academic (PPA) Partnership. NASA funds T STAR to mentor undergraduate Capstone teams in the College of Engineering Department to design, built, and test prototypes meeting NASA requirements. TAMU faculty lead the student teams in their academic class, and NASA Subject Matter Experts (SMEs) provide T STAR and students insight on requirements evolution, prior design projects, and future development goals.

Position Determination↗
NASA NTRSDate not supplied

Using Mesh Networking for A Dynamic Lunar Internet of Things (Liot)

The purpose of this project is to evaluate the feasibility of an IEEE 802.11 mesh protocol for lunar surface computing. This standard for wireless networking boosts speed, dependability and range of wireless transmissions. The concept is to integrate sensors (such as deployed science instruments) or Astronaut tools (such as a handheld spectrometer) that communicate with a node on a common cell. The nodes can extend the range of the cell and can dynamically reconfigure the data routing in case of another node failure. All of the data in a cell pass through a modem that communicates with a distant base station across a 4G link. The application of mesh networking to a potential lunar surface network increases robustness and fault tolerance over a traditional single-point modem system. By demonstrating the basic capability of a mesh network, the student team has learned about issues with power, distance, thermal, dust, radiation, data processing, and communication problems applicable to the lunar surface. This knowledge can feed into future NASA requirements to improve the capability of a LunaNET implementation for the Artemis program. This project follows 10 years of successful collaboration between NASA ARES, Texas Space, Technology, Applications and Research (T STAR) and Texas A&M University in a Public, Private, Academic (PPA) Partnership. NASA funds T STAR to mentor undergraduate Capstone teams in the College of Engineering Department to design, built, and test prototypes meeting NASA requirements. TAMU faculty lead the student teams in their academic class, and NASA Subject Matter Experts (SMEs) provide T STAR and students insight on requirements evolution, prior design projects, and future development goals.

Lunar Mesh Networking↗
NASA NTRS2020

The New NASA Approach to Reliability and Maintainability

In 2017, after 20 years, NASA issued a major revision of its reliability and maintainability (R&M) policy, NASA-STD- 8729.1A. Formerly NASA required certain specific R&M activities during each succeeding phase of project development. Now NASA requires a project to start by including the initial development of R&M requirements and the devising of strategies to implement and verify them. Rather than resolving all the requirements first and then designing the system, as has been usual in systems design, the design process now is to work top down by layers. It begins by first identifying the top level requirements and suggesting top level design strategies for those, then making these higher strategies the basis for a lower level set of requirements, and so on down to the lowest components. This approach is intended to ensure that R&M is designed in from the beginning rather than added later with difficulty to a completed design concept. The new R&M standard uses an innovative and effective top-down system design approach intended to effectively implement R&M.

Jones, Harry W.↗
NASA NTRS2020

The New NASA Approach to Reliability and Maintainability

In 2017, after 20 years, NASA issued a major revision of its reliability and maintainability (R&M) policy, NASA-STD-8729.1A [1]. Formerly NASA required certain specific R&M activities during each succeeding phase of project development. Now NASA requires a project to start by including the initial development of R&M requirements and the devising of strategies to implement and verify them. Rather than resolving all the requirements first and then designing the system, as has been usual in systems design, the design process now is to work top down by layers. It begins by first identifying the top level requirements and suggesting top level design strategies for those, then making these higher strategies the basis for a lower level set of requirements, and so on down to the lowest components. This approach is intended to ensure that R&M is designed in from the beginning rather than added later with difficulty to a completed design concept. The new R&M standard uses an innovative and effective top-down system design approach intended to effectively implement R&M.

Jones, Harry W.↗
NASA NTRS1995

An overview of NASA testing requirements for alternate cleaning solvents used in liquid and gaseous oxygen environments

The elimination of CFC-containing cleaning solvents for oxygen systems has prompted the development of a number of alternative cleaning solvents that must now be evaluated not only for cleanability, but compatibility as well. NASA Handbook 8060.1(NHB 8060.1) establishes the requirements for evaluation, testing, and selection of materials for use in oxygen rich environments. Materials intended for use in space vehicles, specified test facilities, and ground support equipment must meet the requirements of this document. In addition to the requirements of NHB 8060.1 for oxygen service, alternative cleaning solvents must also be evaluated in other areas (such as corrosivity, non-metals compatibility, non-volatile residue contamination, etc.). This paper will discuss the testing requirements of NHB 8060.1 and present preliminary results from early screening tests performed at Marshall Space Flight Center's Materials Combustion Research Facility.

Strickland, John W.↗
NASA NTRS1990

Nuclear power technology requirements for NASA exploration missions

It is pointed out that future exploration of the moon and Mars will mandate developments in many areas of technology. In particular, major advances will be required in planet surface power systems. Critical nuclear technology challenges that can enable strategic self-sufficiency, acceptable operational costs, and cost-effective space transportation goals for NASA exploration missions have been identified. Critical technologies for surface power systems include stationary and mobile nuclear reactor and radioisotope heat sources coupled to static and dynamic power conversion devices. These technologies can provide dramatic reductions in mass, leading to operational and transportation cost savings. Critical technologies for space transportation systems include nuclear thermal rocket and nuclear electric propulsion options, which present compelling concepts for significantly reducing mass, cost, or travel time required for Earth-Mars transport.

Bloomfield, Harvey S.↗