Texas applications system verification and transfer remote sensing information subsystem: Functional design
There are no author-identified significant results in this report.
Brown, M. L., Jr.↗
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.
Panel flutter
Criteria are presented for the prediction of panel flutter, determination of its occurrence, design for its prevention, and evaluation of its severity. Theoretical analyses recommended for the prediction of flutter stability boundaries, vibration amplitudes, and frequencies for several types of panels are described. Vibration tests and wind tunnel tests are recommended for certain panels and environmental flow conditions to provide information for design of verification analysis. Appropriate design margins on flutter stability boundaries are given and general criteria are presented for evaluating the severity of possible short-duration, limited-amplitude panel flutter on nonreusable vehicles.
Dowell, E. H.↗
Texas Natural Resources Inventory and Monitoring System (TNRIMS), Applications System Verification and Transfer (ASVT), Remote Sensing Information Subsystem (RSIS): As built functional design
There are no author-identified significant results in this report.
Brown, M. L.↗
Land surface Verification Toolkit (LVT)
LVT is a framework developed to provide an automated, consolidated environment for systematic land surface model evaluation Includes support for a range of in-situ, remote-sensing and other model and reanalysis products. Supports the analysis of outputs from various LIS subsystems, including LIS-DA, LIS-OPT, LIS-UE. Note: The Land Information System Verification Toolkit (LVT) is a NASA software tool designed to enable the evaluation, analysis and comparison of outputs generated by the Land Information System (LIS). The LVT software is released under the terms and conditions of the NASA Open Source Agreement (NOSA) Version 1.1 or later. Land Information System Verification Toolkit (LVT) NOSA.
surface model↗
Preliminary design package for programmable controller and hydronic energy package
Information necessary to evaluate the preliminary design of the sunkeeper controller is presented as a compilation of the following documents: development plan, verification plan, hazard analysis, drawing list, and other information pertaining to the design of the subsystem.
Source record↗
The use of wind data with an operational wind turbine in a research and development environment
The status of the use of wind information is presented in four areas, namely: operational control, design verification, power performance analysis, and lifetime estimation. Attention is given to some of the identified wind information needs and the steps taken to meet these needs.
Neustadter, H. E.↗
An Integrated Reliability and Physics-Based Risk Modeling Approach for Assessing Human Spaceflight Systems
This paper presents an integrated reliability and physics-based risk modeling approach for assessing human spaceflight systems. The approach is demonstrated using an example, end-to-end risk assessment of a generic-crewed space transportation system during a reference mission to the International Space Station. The behavior of the system is modeled using analysis techniques from multiple disciplines in order to properly capture the dynamic time- and state- dependent consequences of failures encountered in different mission phases. We discuss how to combine traditional reliability analyses with Monte Carlo simulation methods and physics-based engineering models to produce loss-of- mission and loss-of-crew risk estimates supporting risk-based decision-making and requirement verification. This approach facilitates risk-informed design by providing more realistic representation of system failures and interactions; identifying key risk-driving sensitivities, dependencies, and assumptions; and tracking multiple figures of merit within a single, responsive assessment framework that can readily incorporate evolving design information throughout system development.
Risk assessment↗
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.↗
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.↗
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’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↗
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↗
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↗
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'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↗
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↗
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↗
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↗