Search NASA⌕ Search

SEARCH · Search NASA

Results for “Design Information Verification”

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 37 records · Page 2
All sourcesNASA NTRSDOE OSTI
DOE OSTI2023

Verification of a Modeling Toolkit for the Design of Building Electrical Distribution Systems

DC electrical distribution systems offer many potential advantages over their AC counterparts. They can facilitate easier integration with distributed energy resources, improve system energy efficiency by eliminating AC/DC converters at end-use devices (e.g., laptop chargers), and reduce installation material, time, and cost. However, DC electrical distribution systems present additional design considerations, largely resulting from potentially greater magnitude and variation in cable losses. Modeling and simulation are rarely used to design such systems. However, the greater dependency of DC system energy efficiency on design choices such as distribution voltages, architecture, and integration of PV and BESS suggests that modeling and simulation may be required. Such system performance analysis is currently not a standard practice, in part due to limited availability and validation of capable software tools. This paper characterizes the accuracy of a Modelica-based Building Electrical Efficiency Analysis Model (BEEAM) toolkit, as a precursor for validating its use to perform system performance analysis and inform design decisions. The study builds upon previous verification research by characterizing complete systems comprised of commercially available equipment, and providing a more detailed analysis of simulation results. Five lighting systems with varying electrical distribution architectures were designed using market-available equipment, installed in a laboratory environment, modeled using BEEAM, and simulated using three Modelica integrated development environments (IDEs). Simulated and measured results were compared to characterize toolkit accuracy. Initial results revealed that simulated performance was mostly within ±5% of measured system-level and device-level performance. While simulation results were not found to be dependent on the IDE, some Modelica compiler interoperability issues were identified. Although the BEEAM toolkit showed promise for the targeted use case, further work is needed to determine whether the demonstrated 5% accuracy is sufficient for making real-world design decisions, and for BEEAM to advance from an interesting research tool to one that can impact real-world building projects.

24 POWER TRANSMISSION AND DISTRIBUTION↗
NASA NTRS2010

Constellation Ground Systems Launch Availability Analysis: Enhancing Highly Reliable Launch Systems Design

Success of the Constellation Program's lunar architecture requires successfully launching two vehicles, Ares I/Orion and Ares V/Altair, in a very limited time period. The reliability and maintainability of flight vehicles and ground systems must deliver a high probability of successfully launching the second vehicle in order to avoid wasting the on-orbit asset launched by the first vehicle. The Ground Operations Project determined which ground subsystems had the potential to affect the probability of the second launch and allocated quantitative availability requirements to these subsystems. The Ground Operations Project also developed a methodology to estimate subsystem reliability, availability and maintainability to ensure that ground subsystems complied with allocated launch availability and maintainability requirements. The verification analysis developed quantitative estimates of subsystem availability based on design documentation; testing results, and other information. Where appropriate, actual performance history was used for legacy subsystems or comparative components that will support Constellation. The results of the verification analysis will be used to verify compliance with requirements and to highlight design or performance shortcomings for further decision-making. This case study will discuss the subsystem requirements allocation process, describe the ground systems methodology for completing quantitative reliability, availability and maintainability analysis, and present findings and observation based on analysis leading to the Ground Systems Preliminary Design Review milestone.

Gernand, Jeffrey L.↗
NASA NTRS2010

Constellation Ground Systems Launch Availability Analysis: Enhancing Highly Reliable Launch Systems Design

Success of the Constellation Program's lunar architecture requires successfully launching two vehicles, Ares I/Orion and Ares V/Altair, within a very limited time period. The reliability and maintainability of flight vehicles and ground systems must deliver a high probability of successfully launching the second vehicle in order to avoid wasting the on-orbit asset launched by the first vehicle. The Ground Operations Project determined which ground subsystems had the potential to affect the probability of the second launch and allocated quantitative availability requirements to these subsystems. The Ground Operations Project also developed a methodology to estimate subsystem reliability, availability, and maintainability to ensure that ground subsystems complied with allocated launch availability and maintainability requirements. The verification analysis developed quantitative estimates of subsystem availability based on design documentation, testing results, and other information. Where appropriate, actual performance history was used to calculate failure rates for legacy subsystems or comparative components that will support Constellation. The results of the verification analysis will be used to assess compliance with requirements and to highlight design or performance shortcomings for further decision making. This case study will discuss the subsystem requirements allocation process, describe the ground systems methodology for completing quantitative reliability, availability, and maintainability analysis, and present findings and observation based on analysis leading to the Ground Operations Project Preliminary Design Review milestone.

Gernand, Jeffrey L.↗
NASA NTRS1979

Prototype solar-heating system design package

Design package for complete residential solar-heating system is given. Includes documents and drawings describing performance design, verification standards, and analysis of system with sufficient information to assemble working system.

Source record↗
NASA NTRSDate not supplied

NASA’s Developments in Cryogenic Fluid Management Technology

NASA has been pursuing the development and demonstration of enabling and enhancing technologies for Cryogenic Fluid Management (CFM) in collaboration with the US industry. NASA’s vision for current and future space exploration requires high-performance chemical and nuclear propulsion solutions that utilize cryogens. The Agency will use cryogenic fluids for Earth-to-orbit transportation, human missions to the Moon and Mars, planetary exploration, and in-situ resource utilization (ISRU) production. All these architectures will require state-of-the-art long-duration storage on the surface and in-space transfer for refueling. This paper focuses on key CFM technology developments completed or ongoing by the Cryogenic Fluid Management Portfolio Office within NASA’s Space Technology Mission Directorate. The CFM Portfolio Office, partnered with US aerospace industry, has invested in CFM technology ground and flight demonstrations, focused on maturing CFM hardware and operations for Artemis and Moon to Mars activities. These demonstrations additionally provide NASA with data to inform numerical modeling activities for verification and validation of design tools and approaches for future missions. This paper includes discussion on remaining high-priority open CFM technology gaps for Mar-forward architectures and initiatives for closure.

Cryogenic Fluid Management↗
DOE OSTI2025

COnfirmation using Gamma-ray Non-Imaging Zero-knowledge ANti-mask Time-encoding (COGNIZANT) Final Summary Report

In potential future arms reduction treaties in which the numbers of nuclear warheads may approach small numbers, using delivery systems as a proxy for the warheads themselves may be insufficient. Therefore, a technical means of verifying the presence of a nuclear warhead may become necessary. Verifying that a declared item actually is a warhead is technically challenging within a verification regime: providing assurance to the monitoring party that a presented item is a warhead while protecting sensitive information about that warhead may be required. It is generally believed that strong assurance will require the confirmation of key attributes that may reveal closely-guarded critical design information. This provides high confidence to the monitoring party, but presents a risk of information loss to the host. A verification system must overcome this hurdle. Over the last several decades, systems have been developed that balance host and monitoring partner needs by using sensitive information to confirm treaty accountable items (TAI) as warheads while sequestering that information behind an information barrier (1). These are designed to meet the needs of the host but places the onus on the monitor to authenticate the hardware, firmware, and software. Authentication requires that the monitor confirm that all components of the system have not been modified and work as intended. In 2014, Glaser et al. proposed applying the concept of “zero knowledge protocols” (ZKP) from the field of cryptography to the problem of warhead verification (2). In mathematical cryptography, ZKP is accomplished by challenging one party to solve a problem that is only possible if that party possesses the information being authenticated. After repeated challenges, the party provides confidence that it possesses this information without revealing any details about the information itself. Systems have been in development based on this idea at both Princeton and MIT (2) (3) (4). The final measurement results produced by these systems can be viewed by both the host and the monitoring party without the worry of revealing sensitive information. However, in both of these physical implementations, there remains an information barrier within the system. The need for a digital information barrier to protect a measurement result is eliminated, but it has been replaced with the need to sequester physical components of the system, potentially obfuscating the measurement process itself. Both implementations physically insert information into the system that requires protection to prevent undesired disclosure of sensitive information: in the Princeton method, one must physically load the complement of the expected image of a true warhead into the system, and in the MIT technique, one loads a collection of spectator foils whose thicknesses physically encrypt a measured spectrum. This complicates authentication of the hardware and measurement process. The CONFIDANTE/COGNIZANT concept developed in this project do not load sensitive information into the system at any time, and could therefore open the possibility of allowing the inspector to not only view the final data but also the measurement as it is being performed and all associated equipment.

98 NUCLEAR DISARMAMENT, SAFEGUARDS, AND PHYSICAL P↗
NASA NTRS2003

A Novel Data System for Verification of Internal Parameters of Motor Design

Three major obstacles have limited the amount of information that can be obtained from inside an operating solid rocket motor. The first is a safety issue due to the presence of live propellant interacting with classical, electrical instrumentation. The second is a pressure vessel feed through risk arising from bringing a large number of wires through the rocket motor wall safely. The third is an attachment/protection issue associated with connecting gages to live propellant. Thiokol has developed a highly miniaturized, networked, electrically isolated data system that has safely delivered information from classical, electrical instrumentation (even on the burning propellant surface) to the outside world. This system requires only four wires to deliver 80 channels of data at 2300 samples/second/channel. The feed through leak path risk is massively reduced from the current situation where each gage requires at least three pressure vessel wire penetrations. The external electrical isolation of the system is better than that of the propellant itself. This paper describes the new system.

Smith, Doug↗
NASA NTRS1987

Digital-flight-control-system software written in automated-engineering-design language: A user's guide of verification and validation tools

The user guide of verification and validation (V&V) tools for the Automated Engineering Design (AED) language is specifically written to update the information found in several documents pertaining to the automated verification of flight software tools. The intent is to provide, in one document, all the information necessary to adequately prepare a run to use the AED V&V tools. No attempt is made to discuss the FORTRAN V&V tools since they were not updated and are not currently active. Additionally, the current descriptions of the AED V&V tools are contained and provides information to augment the NASA TM 84276. The AED V&V tools are accessed from the digital flight control systems verification laboratory (DFCSVL) via a PDP-11/60 digital computer. The AED V&V tool interface handlers on the PDP-11/60 generate a Univac run stream which is transmitted to the Univac via a Remote Job Entry (RJE) link. Job execution takes place on the Univac 1100 and the job output is transmitted back to the DFCSVL and stored as a PDP-11/60 printfile.

Saito, Jim↗
NASA NTRS2010

Space Medicine in the Human System Integration Process

This slide presentation reviews the importance of integration of space medicine in the human system of lunar exploration. There is a review of historical precedence in reference to lunar surface operations. The integration process is reviewed in a chart which shows the steps from research to requirements development, requirements integration, design, verification, operations and using the lessons learned, giving more information and items for research. These steps are reviewed in view of specific space medical issues. Some of the testing of the operations are undertaken in an environment that is an analog to the exploration environment. Some of these analog environments are reviewed, and there is some discussion of the benefits of use of an analog environment in testing the processes that are derived.

Scheuring, Richard A.↗
NASA NTRS2018

NASA's Advanced Extra-Vehicular Activity Space Suit Pressure Garment 2018 Status and Development Plan

This paper presents both near-term and long-term NASA Advanced Extra-vehicular Activity (EVA) Pressure Garment development efforts. The near-term plan discusses the development of pressure garment components for the first design iteration of the International Space Station exploration space suit demonstration configuration, termed the xEMU Demo. The xEMU Demo effort is targeting a 2023-2025 flight demonstration timeframe. The Fiscal Year 2018 (FY18) tasks focus on either the initiation or maturation of component design, depending on the state of development of the components, and the assembly of a suit configuration, termed Z-2.5, that will be used to evaluate changes to the upper torso geometry in a Neutral Buoyancy Laboratory (NBL) test series. The geometry changes, which are being driven by the need to reduce the front-to-back dimension of the advanced extravehicular mobility unit, diverge from a proven shape, such as that of the Mark III Space Suit Technology Demonstrator. The 2018 efforts culminate in the Z-2.5 NBL test. The lessons learned from the Z-2.5 NBL test will inform the xEMU Demo design as the effort moves toward design verification testing and preliminary and critical design reviews. The long-term development plan looks to surface exploration and operations. Technology and knowledge gaps exist between the xEMU Demo configuration; a lunar surface capability, xEMU; and Mars surface suit, mEMU. The development plan takes into account both the priority and the anticipated development duration for each particular technology. The long-term development plan will be updated as risks are mitigated and gaps are closed, but its overarching structure will remain intact.

space suit↗
NASA NTRSDate not supplied

MBSE Applications for the MSR SRC Mars Ascent Vehicle

The objective of the NASA Mars Sample Return (MSR) Campaign is to collect samples from the surface of Mars and return them to Earth for scientific research. The Mars Ascent Vehicle (MAV) will be integrated into a larger Mars Sample Retrieval Lander (SRL) for transit to and storage on Mars. After all Martian samples have been collected and loaded into the MAV payload assembly, MAV will deliver the samples from the Martian surface to Mars orbit. A separate spacecraft, the Earth Return Orbiter (ERO) will retrieve the samples from Mars orbit and return them to Earth. To address common systems engineering challenges associated with using traditional systems engineering practices on complex projects, the MAV systems engineering team has explored implementation of Model-Based Systems Engineering (MBSE) tools and languages. This paper describes the current state of implementation and development of the MAV MBSE model with the Systems Modeling Language (SysML) within the scope of the MAV Systems Requirement Cycle (SRC) systems engineering workflow. The MAV MBSE model has been developed within Magic Draw – a SysML editor commonly used to implement MBSE. The MAV MBSE model has been used to develop mission phase functional flow diagrams for the Concept of Operations, decompose mission to vehicle subsystem functions, develop a functional decomposition, derive functional requirements, trace requirements up to customer-imposed requirements, trace requirements within MAV requirement space, identify requirements trace gaps, define and map the physical design space architecture, allocate requirements to subsystems, develop validation items, define assembly, integration, and test (AI&T) operations, and trace these items across driving goals to develop an integrated digital thread of systems engineering information used to drive design specifications, decision making, and ultimately design verification and validation. Findings and results associated with implementing MBSE in these ways, alongside traditional methods will be discussed.

MBSE↗
NASA NTRSDate not supplied

MBSE Applications for the MSR SRC Mars Ascent Vehicle

The objective of the NASA Mars Sample Return (MSR) Campaign is to collect samples from the surface of Mars and return them to Earth for scientific research. The Mars Ascent Vehicle (MAV) will be integrated into a larger Mars Sample Retrieval Lander (SRL) for transit to and storage on Mars. After all Martian samples have been collected and loaded into the MAV payload assembly, MAV will deliver the samples from the Martian surface to Mars orbit. A separate spacecraft, the Earth Return Orbiter (ERO) will retrieve the samples from Mars orbit and return them to Earth. To address common systems engineering challenges associated with using traditional systems engineering practices on complex projects, the MAV systems engineering team has explored implementation of Model-Based Systems Engineering (MBSE) tools and languages. This paper describes the current state of implementation and development of the MAV MBSE model with the Systems Modeling Language (SysML) within the scope of the MAV Systems Requirement Cycle (SRC) systems engineering workflow. The MAV MBSE model has been developed within Magic Draw – a SysML editor commonly used to implement MBSE. The MAV MBSE model has been used to develop mission phase functional flow diagrams for the Concept of Operations, decompose mission to vehicle subsystem functions, develop a functional decomposition, derive functional requirements, trace requirements up to customer-imposed requirements, trace requirements within MAV requirement space, identify requirements trace gaps, define and map the physical design space architecture, allocate requirements to subsystems, develop validation items, define assembly, integration, and test (AI&T) operations, and trace these items across driving goals to develop an integrated digital thread of systems engineering information used to drive design specifications, decision making, and ultimately design verification and validation. Findings and results associated with implementing MBSE in these ways, alongside traditional methods will be discussed.

MBSE↗
DOE OSTI2022

Importance of appropriate genome information for the design of mating type primers in black and yellow morel populations

Abstract Morels are highly prized edible fungi where sexual reproduction is essential for fruiting-body production. As a result, a comprehensive understanding of their sexual reproduction is of great interest. Central to this is the identification of the reproductive strategies used by morels. Sexual reproduction in fungi is controlled by mating-type ( MAT ) genes and morels are thought to be mainly heterothallic with two idiomorphs, MAT1-1 and MAT1-2. Genomic sequencing of black (Elata clade) and yellow (Esculenta clade) morel species has led to the development of PCR primers designed to amplify genes from the two idiomorphs for rapid genotyping of isolates from these two clades. To evaluate the design and theoretical performance of these primers we performed a thorough bioinformatic investigation, including the detection of the MAT region in publicly available Morchella genomes and in-silico PCR analyses. All examined genomes, including those used for primer design, appeared to be heterothallic. This indicates an inherent fault in the original primer design which utilized a single Morchella genome, as the use of two genomes with complementary mating types would be required to design accurate primers for both idiomorphs. Furthermore, potential off-targets were identified for some of the previously published primer sets, but verification was challenging due to lack of adequate genomic information and detailed methodologies for primer design. Examinations of the black morel specific primer pairs (MAT11L/R and MAT22L/R) indicated the MAT22 primers would correctly target and amplify the MAT1-2 idiomorph, but the MAT11 primers appear to be capable of amplifying incorrect off-targets within the genome. The yellow morel primer pairs (EMAT1-1 L/R and EMAT1-2 L/R) appear to have reporting errors, as the published primer sequences are dissimilar with reported amplicon sequences and the EMAT1-2 primers appear to amplify the RNA polymerase II subunit ( RPB2 ) gene. The lack of the reference genome used in primer design and descriptive methodology made it challenging to fully assess the apparent issues with the primers for this clade. In conclusion, additional work is still required for the generation of reliable primers to investigate mating types in morels and to assess their performance on different clades and across multiple geographical regions.

59 BASIC BIOLOGICAL SCIENCES↗
NASA NTRS1987

Space station System Engineering and Integration (SE and I). Volume 2: Study results

A summary of significant study results that are products of the Phase B conceptual design task are contained. Major elements are addressed. Study results applicable to each major element or area of design are summarized and included where appropriate. Areas addressed include: system engineering and integration; customer accommodations; test and program verification; product assurance; conceptual design; operations and planning; technical and management information system (TMIS); and advanced development.

Source record↗
NASA NTRS1993

Reactive system verification case study: Fault-tolerant transputer communication

A reactive program is one which engages in an ongoing interaction with its environment. A system which is controlled by an embedded reactive program is called a reactive system. Examples of reactive systems are aircraft flight management systems, bank automatic teller machine (ATM) networks, airline reservation systems, and computer operating systems. Reactive systems are often naturally modeled (for logical design purposes) as a composition of autonomous processes which progress concurrently and which communicate to share information and/or to coordinate activities. Formal (i.e., mathematical) frameworks for system verification are tools used to increase the users' confidence that a system design satisfies its specification. A framework for reactive system verification includes formal languages for system modeling and for behavior specification and decision procedures and/or proof-systems for verifying that the system model satisfies the system specifications. Using the Ostroff framework for reactive system verification, an approach to achieving fault-tolerant communication between transputers was shown to be effective. The key components of the design, the decoupler processes, may be viewed as discrete-event-controllers introduced to constrain system behavior such that system specifications are satisfied. The Ostroff framework was also effective. The expressiveness of the modeling language permitted construction of a faithful model of the transputer network. The relevant specifications were readily expressed in the specification language. The set of decision procedures provided was adequate to verify the specifications of interest. The need for improved support for system behavior visualization is emphasized.

Crane, D. Francis↗
NASA NTRS2012

A Design Rationale Capture Tool to Support Design Verification and Re-use

A design rationale tool (DR tool) was developed to capture design knowledge to support design verification and design knowledge re-use. The design rationale tool captures design drivers and requirements, and documents the design solution including: intent (why it is included in the overall design); features (why it is designed the way it is); information about how the design components support design drivers and requirements; and, design alternatives considered but rejected. For design verification purposes, the tool identifies how specific design requirements were met and instantiated within the final design, and which requirements have not been met. To support design re-use, the tool identifies which design decisions are affected when design drivers and requirements are modified. To validate the design tool, the design knowledge from the Taxiway Navigation and Situation Awareness (T-NASA; Foyle et al., 1996) system was captured and the DR tool was exercised to demonstrate its utility for validation and re-use.

design verification↗
NASA NTRS1974

Shuttle active thermal control system development testing. Volume 1: Overall summary

A summary is given of a series of thermal vacuum tests designed to support the development of the orbiter active thermal control system (ATCS) and included testing of a wide heat load range modular radiator system (MRS) configured to the March 1973 orbiter baseline system, a candidate weight reducing radiator/water cooling system, and a smaller radiator system with a high performance radiator coating. The tests verified the performance of the baseline system and obtained detailed design information for application of a wide heat load range modular radiator system to the orbiter. The two candidate ATCS weight reducing designs have undergone extensive concept verification testing and their system operating characteristics have been determined in sufficient detail for application to the orbiter. Design information has been obtained for an integrated radiator/water cooling system that provides for vehicle heat rejection as well as water management of the excess fuel cell water. Processing techniques have been developed and verified for the application of a high performance thermal control coating to large radiator areas subjected to a temperature range of -280 F to +160 F.

Howell, H. R.↗
NASA NTRS1983

ECUT: Energy Conversion and Utilization Technologies program. Heterogeneous catalysis modeling program concept

Insufficient theoretical definition of heterogeneous catalysts is the major difficulty confronting industrial suppliers who seek catalyst systems which are more active, selective, and stable than those currently available. In contrast, progress was made in tailoring homogeneous catalysts to specific reactions because more is known about the reaction intermediates promoted and/or stabilized by these catalysts during the course of reaction. However, modeling heterogeneous catalysts on a microscopic scale requires compiling and verifying complex information on reaction intermediates and pathways. This can be achieved by adapting homogeneous catalyzed reaction intermediate species, applying theoretical quantum chemistry and computer technology, and developing a better understanding of heterogeneous catalyst system environments. Research in microscopic reaction modeling is now at a stage where computer modeling, supported by physical experimental verification, could provide information about the dynamics of the reactions that will lead to designing supported catalysts with improved selectivity and stability.

Voecks, G. E.↗