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 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRS2020

Introduction to ISS Crew Displays

The International Space Station (ISS) began payload operations in earnest in 2000 with the arrival of the Expedition 1. To date, ISS has offered Principal Investigators (PIs) a reliable platform for microgravity research, having hosted thousands of onboard science experiments. Most of this research is supported by experiment hardware and software and many include a crew‐operated Graphical User Interface (GUI). The purpose of this article is to share information with PIs and Payload Developer (PD) teams about the processes, standards, and guidelines applicable to crew GUI design that must be complied with when planning payload software. The goal is not to enumerate all of the ISS display standards, but rather to highlight design guidelines and the ISS Program milestones for verification and approval of onboard crew displays.

Graphical User Interface↗
NASA NTRS2017

Review of a Draft - Avoiding the Impossible: Re-focusing a Non-Feasible Mission 2-Hrs into a 3-Day Engineering Session

Concurrent engineering offers a great many benefits to engineers and mission designers throughout the world of aerospace. The only downside of concurrent engineering, and this is somewhat unavoidable, is that you don’t know the results of a design session until the end when it is completed. Usually, this is not a problem – you wouldn’t start building a spacecraft before the design is finished. However, within mass and cost constrained systems, you may end up with a final design that although technically sound – is not feasible due to mass or cost limits. Employing in-session mass and cost models with flexible inputs that refine their estimates and variance as more detailed information comes in throughout a design session allows major design changes to be made when the probability of breaching a mass or cost cap exceeds a threshold level. This enables mission designers to re-focus the study, and avoid spending 3-days with 15 engineers designing a non-feasible mission. By understanding key correlations and nested relationships within mass or cost, and specifically mass or cost allocations per mission element by mission type, it’s possible to get flexible-input, statistically based mass and cost estimates very early in the design process. Baseline models are seeded using mission characteristics and general parameters (outer planetary orbiter-probe mission, $500M cost cap for example) to provide a rough estimate of the expected mass or cost. As information gets solidified during the session, it gets added to the model and the estimates are updated. Continuing the orbiter-probe mission example, modeling probe heat shield cost as a percent of total probe cost, and probe cost as a percent of total flight system cost, and total flight system cost as a percent of total mission cost allows a design team to roll-up solidified information to estimate the probability of fitting within a mass or cost constraint early in a concurrent design session. When only the heat shield cost is known, the variance of the final estimate is higher, whereas when the full probe gets defined, naturally, the variance of the estimate decreases. A methodology, model, verification and demo implementation for cost limit breach are presented.

Hihn, Jairus M.↗
NASA NTRS2010

Space Weather Models and Their Validation and Verification at the CCMC

The Community Coordinated l\lodeling Center (CCMC) is a US multi-agency activity with a dual mission. With equal emphasis, CCMC strives to provide science support to the international space research community through the execution of advanced space plasma simulations, and it endeavors to support the space weather needs of the CS and partners. Space weather support involves a broad spectrum, from designing robust forecasting systems and transitioning them to forecasters, to providing space weather updates and forecasts to NASA's robotic mission operators. All of these activities have to rely on validation and verification of models and their products, so users and forecasters have the means to assign confidence levels to the space weather information. In this presentation, we provide an overview of space weather models resident at CCMC, as well as of validation and verification activities undertaken at CCMC or through the use of CCMC services.

Hesse, Michael↗
NASA NTRS2022

Flight Software Dictionary Development for the Mars2020 Rover

The Mars2020 project, developed and operated by the Jet Propulsion Laboratory (JPL), successfully landed the Perseverance rover and its flying companion Ingenuity on the surface of Mars on February 18th 2021. Perseverance combines heritage and cutting-edge flight software and hardware to accomplish crucial mission requirements related to Martian surface sampling. The design, development, and operation of NASA’s large strategic science missions require the ability to communicate spacecraft capabilities to hundreds of engineers across multiple disciplines. The interaction between flight and ground software development, Verification and Validation (V&V), Assembly, Test, and Launch Operations (ATLO), and management each demand quick understanding of unique slices of information for each discipline. This information includes the current capabilities of the flight system as well as future capabilities and their status as they are developed and tested. Despite the fundamental and critical nature of this information, the flight software dictionaries used to track it are a stumbling block for many projects. These dictionaries provide the cornerstone for the interpretation of data sent from the spacecraft, allowing for quick comprehension by engineers on the ground. During both spacecraft development and operations, flight software dictionary management includes significant challenges due to the large number of interfacing systems and the subtle yet distinct needs of each.The engineering of flight software dictionaries for Mars2020 had numerous challenges, most-notably: parallel dictionary development to support simultaneous separate flight software build campaigns for each mission phase (cruise and surface), managing requests for operations-enabling information without perturbing the heritage interface with the rover, and the introduction of new tools by the dictionary stakeholders that forced the dictionary team to innovate and redesign the heritage tool chain. These challenges generated guiding principles for the dictionary development effort: emphasize coding best practices and unit testing in the dictionary code development tool chain, use institutionally provided COTS (commercial-off-the-shelf) tools whenever possible, and maintain the heritage flight-ground interface all while advancing operations-enabling information via a loosely coupled interface.Throughout development and operations, the Mars2020 dictionary toolchain included IBM DOORS Next Generation, GitHub, Microsoft Excel, Docker, Jenkins, and a significant custom-built Python codebase. Significant interfaces included JPL’s command and control software, heritage flight software team tools and processes, and the many cloud-based ground tools developed for the mission.This paper will discuss the requirements for the Mars2020 dictionary development, the development team’s response to those requirements, lessons learned throughout the process, steps taken towards automated deliveries and continuous integration of stakeholder inputs, potential toolchain improvements for Mars2020, and key takeaways that could be applied to future missions.

Pyrzak, Guy↗
NASA NTRS2004

Lithium-Ion Verification Test Program

In order to assess the capabilities of current aerospace lithium-ion cells to perform long-term NASA missions, low-earth-orbits (LEO) testing to evaluate long-term cycle life was initiated. A flexible program was developed at NASA Glenn Research Center to enable assessment of technology developments as they occur as well as provide information about different cell vendors and cell designs. Following extensive characterization testing, cells are tested using LEO charge and discharge profiles under ten different combinations of test conditions that were statistically chosen to determine the effects of depth-of-discharge, temperature, and end-of-charge voltage on LEO cycle life. Four cells from each vendor are tested at each specific combination of conditions. Conditions included in the test matrix are depth-of-discharges of 20%, 30, 35%, and 40%; temperatures of 20, 30, and 40 C; and end-of-charge voltages of 3.85 V, 3.95 V, and 4.05 V. Cells are randomly assigned to packs and packs are randomly assigned to test conditions. The capacity of the cells to 3.0 V at the conditions of the test is being periodically measured. The results of this testing will be used to model cell performance and degradation as a function of test operating conditions. Cells are being evaluated in 4-cell series strings with charge voltage limits being applied to individual cells by charge control units designed and built at NASA Glenn Research Center. Testing is being performed at the Naval Surface Warfare Center/Crane Division in Crane, IN. Testing was initiated in September 2004 with 40 Ah cells from Saft and 30 Ah cells from Lithion. The test program is being expanded with the addition of cells from MSA and the addition of small cell modules is being considered. Preliminary results showing voltage, temperature, usable capacity per unit mass, and voltage dispersion as their changes over time for the cells at 20 C is presented.

McKissock, Barbara↗
NASA NTRS2018

Tagging Components in the Test Complex Area

Why tag components differently? - Various methods are in place to tag different components, but not every component is tracked; - Variance in method can make it difficult to obtain component information and identify discrepancies; -Time and resources are spent on component localization and verification. Previous work of RA10 interns: - Researching more efficient asset tracking methods; - Investigating cost effective ways to localize components; - Past interns identified using QR (Quick Response) codes as a potential solution. Link QR codes to Windchill (PLM - Product Lifecycle Management system) DDMS (Design and Data Management System) after QR code is printed/etched and physically tagging it as quickly as possible

Gomez, Sarah↗
NASA NTRS2014

ADEPT for Secondary Payloads

Deployable entry vehicles provide an enabling capability for large payloads at destinations across the solar system. The primary advantage of such systems derives from the fundamental limitation of available launch vehicle shroads preventing tried-and-true rigid aeroshell technology from being applied. However, little mission-pull exists for deployable entry vehicle technology for missions where the entry vehicle is the primary payload and can fit within available shrouds. The propensity toward applying rigid aeroshell technology is logical given that deployable concepts are higher risk and provide no marginal scientific benefit for missions where a rigid aeroshell is an option. A movement toward flying smaller spacecraft has emerged in recent years and is revealing novel applications for deployable entry vehicles as secondary payloads. Secondary payloads must minimize interference with the primary payload in order to ease accomodation. Advancements in small spacecraft technology have caught the attention of government entities who are now recognizing the high value proposition of small spacecraft for frequent, incremental technology development and science return rather than the traditional high cost and infrequent big-bang approaches. Worldwide, well over 200 small satellites (mass < 180 kg) have launched in recent years for such purposes as eduation, technology development, science, commerce, and defense. The Adaptable Deployable Entry and Placement Technology (ADEPT), a mechanically-deployable entry vehicle technology, has been under development at NASA since 2011. An Ames Center Innovation Fund (CIF) proposal was recently awarded to study ADEPT for EDL of small payloads. The unique capability of ADEPT for small science payloads comes from its ability to stow within a slender volume and deploy passively to achieve a mass-efficient drag surface with a high heat rate capability. The low ballistic coefficient results in entry heating and mechanical loads that can be met by a revolutionary three-dimensionally woven carbon fabric supported with rib structures. This carbon fabric has test-proven capability as both primary structure and payload thermal protection. This presentation will inform the EDL community of the capability of ADEPT for delivery of small secondary payloads as well as provide status of on-going technology development activities. Results of a mission applications study for secondary payloads to Mars and Venus will be presented. A primary goal of these mission design activities is to integrate high-value verification approaches wherever possible. For example, for some mission applications it is possible to test in NASA arc jet facilities at full-scale. This enables endto- end thermostructural requirement verification with a single test. Another important challenge that needs to be solved is the reliability of the decelerator to achieve the desired shape using simple passive mechanical actuators (such as springs) that do not require power from the primary payload for deployment. A configuration of ADEPT is being prototyped and used to evaluate the functionality and reliability of the deployment mechanism through bench-top testing. The prototype will then be tested in a low speed wind tunnel in late 2014 to evaluate aerodynamic load-carrying capability and deflected shape. Results of the deployment testing and status of wind tunnel test plans will be discussed.

Smith, B.↗
NASA NTRS1986

Analyzing the security of an existing computer system

Most work concerning secure computer systems has dealt with the design, verification, and implementation of provably secure computer systems, or has explored ways of making existing computer systems more secure. The problem of locating security holes in existing systems has received considerably less attention; methods generally rely on thought experiments as a critical step in the procedure. The difficulty is that such experiments require that a large amount of information be available in a format that makes correlating the details of various programs straightforward. This paper describes a method of providing such a basis for the thought experiment by writing a special manual for parts of the operating system, system programs, and library subroutines.

Bishop, M.↗
NASA NTRS2006

Inspection and Verification of Domain Models with PlanWorks and Aver

When developing a domain model, it seems natural to bring the traditional informal tools of inspection and verification, debuggers and automated test suites, to bear upon the problems that will inevitably arise. Debuggers that allow inspection of registers and memory and stepwise execution have been a staple of software development of all sorts from the very beginning. Automated testing has repeatedly proven its considerable worth, to the extent that an entire design philosophy (Test Driven Development) has been developed around the writing of tests. Unfortunately, while not entirely without their uses, the limitations of these tools and the nature of the complexity of models and the underlying planning systems make the diagnosis of certain classes of problems and the verification of their solutions difficult or impossible. Debuggers provide a good local view of executing code, allowing a fine-grained look at algorithms and data. This view is, however, usually only at the level of the current scope in the implementation language, and the data-inspection capabilities of most debuggers usually consist of on-line print statements. More modem graphical debuggers offer a sort of tree view of data structures, but even this is too low-level and is often inappropriate for the kinds of structures created by planning systems. For instance, god or constraint networks are at best awkward when visualized as trees. Any any non-structural link between data structures, as through a lookup table, isn't captured at all. Further, while debuggers have powerful breakpointing facilities that are suitable for finding specific algorithmic errors, they have little use in the diagnosis of modeling errors.

Bedrax-Weiss, Tania↗
NASA NTRS1995

Verification and validation of a reliable multicast protocol

This paper describes the methods used to specify and implement a complex communications protocol that provides reliable delivery of data in multicast-capable, packet-switching telecommunication networks. The protocol, called the Reliable Multicasting Protocol (RMP), was developed incrementally by two complementary teams using a combination of formal and informal techniques in an attempt to ensure the correctness of the protocol implementation. The first team, called the Design team, initially specified protocol requirements using a variant of SCR requirements tables and implemented a prototype solution. The second team, called the V&V team, developed a state model based on the requirements tables and derived test cases from these tables to exercise the implementation. In a series of iterative steps, the Design team added new functionality to the implementation while the V&V team kept the state model in fidelity with the implementation through testing. Test cases derived from state transition paths in the formal model formed the dialogue between teams during development and served as the vehicles for keeping the model and implementation in fidelity with each other. This paper describes our experiences in developing our process model, details of our approach, and some example problems found during the development of RMP.

Callahan, John R.↗
NASA NTRS1980

Future integrated design process

The design process is one of the sources used to produce requirements for a computer system to integrate and manage product design data, program management information, and technical computation and engineering data management activities of the aerospace design process. Design activities were grouped chronologically and explored for activity type, activity interface, data quantity, and data flow. The work was based on analysis of the design process of several typical aerospace products, including both conventional and supersonic airplanes and a hydrofoil design. Activities examined included research, preliminary design, detail design, manufacturing interface, product verification, and product support. The design process was then described in an IPAD environment--the future.

Meyer, D. D.↗
NASA NTRS2011

Space Suit Joint Torque Testing

In 2009 and early 2010, a test was performed to quantify the torque required to manipulate joints in several existing operational and prototype space suits in an effort to develop joint torque requirements appropriate for a new Constellation Program space suit system. The same test method was levied on the Constellation space suit contractors to verify that their suit design meets the requirements. However, because the original test was set up and conducted by a single test operator there was some question as to whether this method was repeatable enough to be considered a standard verification method for Constellation or other future space suits. In order to validate the method itself, a representative subset of the previous test was repeated, using the same information that would be available to space suit contractors, but set up and conducted by someone not familiar with the previous test. The resultant data was compared using graphical and statistical analysis and a variance in torque values for some of the tested joints was apparent. Potential variables that could have affected the data were identified and re-testing was conducted in an attempt to eliminate these variables. The results of the retest will be used to determine if further testing and modification is necessary before the method can be validated.

Valish, Dana J.↗
NASA NTRS2012

Space Suit Joint Torque Measurement Method Validation

In 2009 and early 2010, a test method was developed and performed to quantify the torque required to manipulate joints in several existing operational and prototype space suits. This was done in an effort to develop joint torque requirements appropriate for a new Constellation Program space suit system. The same test method was levied on the Constellation space suit contractors to verify that their suit design met the requirements. However, because the original test was set up and conducted by a single test operator there was some question as to whether this method was repeatable enough to be considered a standard verification method for Constellation or other future development programs. In order to validate the method itself, a representative subset of the previous test was repeated, using the same information that would be available to space suit contractors, but set up and conducted by someone not familiar with the previous test. The resultant data was compared using graphical and statistical analysis; the results indicated a significant variance in values reported for a subset of the re-tested joints. Potential variables that could have affected the data were identified and a third round of testing was conducted in an attempt to eliminate and/or quantify the effects of these variables. The results of the third test effort will be used to determine whether or not the proposed joint torque methodology can be applied to future space suit development contracts.

Valish, Dana↗
NASA NTRS2017

Discovery Deep Space Optical Communications (DSOC) transceiver

NASA’s 22 cm diameter Deep Space Optical Communications (DSOC) Transceiver is designed to provide a bi-directional optical link between a spacecraft in the inner solar system and an Earth-based optical ground station. This design, optimized for operation across a wide range of illumination conditions, is focused on minimizing blinding from stray light, and providing reliable, accurate attitude information to point its narrow communication beam accurately to the future location of the ground terminal. Though our transceiver will transmit in the 1550 nm waveband and receive in the 1064 nm waveband, the system design relies heavily on reflective optical elements, extending flexibility to be modified for use at different wavebands. The design makes use of common path propagation among transmit, receive and pointing verification optical channels to maintain precise alignment among its components, and to naturally correct for element misalignment resulting from launch or thermal element perturbations. This paper presents the results of trade studies showing the evolution of the design, unique operational characteristics of the design, elements that help to maintain minimal stray light contamination, and preliminary results from development and initial testing of a functional aluminum test model.

Roberts, W. Thomas↗
NASA NTRS1985

Observing the earth radiation budget from satellites - Past, present, and a look to the future

Satellite measurements of the radiative exchange between the planet earth and space have been the objective of many experiments since the beginning of the space age in the late 1950's. The on-going mission of the Earth Radiation Budget (ERB) experiments has been and will be to consider flight hardware, data handling and scientific analysis methods in a single design strategy. Research and development on observational data has produced an analysis model of errors associated with ERB measurement systems on polar satellites. Results show that the variability of reflected solar radiation from changing meteorology dominates measurement uncertainties. As an application, model calculations demonstrate that measurement requirements for the verification of climate models may be satisfied with observations from one polar satellite, provided there is information on diurnal variations of the radiation budget from the ERBE mission.

House, F. B.↗
NASA NTRS1999

Solar Array Verification Analysis Tool (SAVANT) Developed

Modeling solar cell performance for a specific radiation environment to obtain the end-of-life photovoltaic array performance has become both increasingly important and, with the rapid advent of new types of cell technology, more difficult. For large constellations of satellites, a few percent difference in the lifetime prediction can have an enormous economic impact. The tool described here automates the assessment of solar array on-orbit end-of-life performance and assists in the development and design of ground test protocols for different solar cell designs. Once established, these protocols can be used to calculate on-orbit end-of-life performance from ground test results. The Solar Array Verification Analysis Tool (SAVANT) utilizes the radiation environment from the Environment Work Bench (EWB) model developed by the NASA Lewis Research Center s Photovoltaic and Space Environmental Effects Branch in conjunction with Maxwell Technologies. It then modifies and combines this information with the displacement damage model proposed by Summers et al. (ref. 1) of the Naval Research Laboratory to determine solar cell performance during the course of a given mission. The resulting predictions can then be compared with flight data. The Environment WorkBench (ref. 2) uses the NASA AE8 (electron) and AP8 (proton) models of the radiation belts to calculate the trapped radiation flux. These fluxes are integrated over the defined spacecraft orbit for the duration of the mission to obtain the total omnidirectional fluence spectra. Components such as the solar cell coverglass, adhesive, and antireflective coatings can slow and attenuate the particle fluence reaching the solar cell. In SAVANT, a continuous slowing down approximation is used to model this effect.

Bailey, Sheila G.↗
NASA NTRS1992

Overview and evolution of the LeRC PMAD DC Testbed

Since the beginning of the Space Station Freedom Program (SSFP), the Lewis Research Center (LeRC) has been developed electrical power system test beds to support the overall design effort. Through this time, the SSFP has changed the design baseline numerous times, however, the test bed effort has endeavored to track these changes. Beginning in August 1989 with the baseline and an all DC system, a test bed was developed to support the design baseline. The LeRC power measurement and distribution (PMAD) DC test bed and the changes in the restructure are described. The changes includeed the size reduction of primary power channel and various power processing elements. A substantial reduction was also made in the amount of flight software with the subsequent migration of these functions to ground control centers. The impact of these changes on the design of the power hardware, the controller algorithms, the control software, and a description of their current status is presented. An overview of the testing using the test bed is described, which includes investigation of stability and source impedance, primary and secondary fault protection, and performance of a rotary utility transfer device. Finally, information is presented on the evolution of the test bed to support the verification and operational phases of the SSFP in light of these restructure scrubs.

Soeder, James F.↗
NASA NTRS1992

Overview and evolution of the LeRC PMAD DC test bed

Since the beginning of the Space Station Freedom Program (SSFP), the Lewis Research Center (LeRC) has been developed electrical power system test beds to support the overall design effort. Through this time, the SSFP has changed the design baseline numerous times, however, the test bed effort has endeavored to track these changes. Beginning in August 1989 with the baseline and an all DC system, a test bed was developed to support the design baseline. The LeRC power measurement and distribution (PMAD) DC test bed and the changes in the restructure are described. The changes included the size reduction of primary power channel and various power processing elements. A substantial reduction was also made in the amount of flight software with the subsequent migration of these functions to ground control centers. The impact of these changes on the design of the power hardware, the controller algorithms, the control software, and a description of their current status is presented. An overview of the testing using the test bed is described, which includes investigation of stability and source impedance, primary and secondary fault protection, and performance of a rotary utility transfer device. Finally, information is presented on the evolution of the test bed to support the verification and operational phases of the SSFP in light of these restructure scrubs.

Soeder, James F.↗