Government Microelectronics Assessment for Trust (GOMAT)

Berg, Melanie D.; LaBel, Kenneth A.

Home/Archive/NASA NTRS

NASA NTRS · 20180001572

Government Microelectronics Assessment for Trust (GOMAT)

Berg, Melanie D.·LaBel, Kenneth A.

View original source ↗Export metadata ↓

Abstract

NASA Electronic Parts and Packaging (NEPP) is developing a process to be employed in critical applications. The framework assesses levels of trust and assurance in microelectronic systems. The process is being created with participation from a variety of organizations. We present a synopsis of the framework that includes contributions from The Aerospace Corporation.

Explore related subjects

Assurance Field programmable gate array (FPGA)Application specific integrated circuit (ASIC)Trust Security

Keep this discovery

Explore connections, maps & timelines

BibTeX RIS

Berg, Melanie D., LaBel, Kenneth A.. 2018-02-28. Government Microelectronics Assessment for Trust (GOMAT). https://ntrs.nasa.gov/citations/20180001572

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related reports

NASA NTRS2024

Performance of Two Battery Prognostic Applications used by Two Octocopters for Safe Low Altitude Autonomous Flight Operations

This paper addresses the problem of building trust in online predictions of the remaining available flying time for two different electric Unmanned Aerial Vehicles (eUAVs) powered by lithium-ion-polymer batteries. Flight tests for various automation research missions for the two vehicles were monitored using two on-board battery health management applications to make predictions of the remaining flying time (RFT) for each eUAV and to predict the state of the battery. Playback of the voltage, current and temperature profiles of the battery discharge were used to assess the accuracy of the estimation of the voltage and the charge states of the models as well as the estimate of the RFT. The reference ground truth values were the observed landing time and the measured battery pack resting pack voltage 20 minutes after the flight. The predicted RFT, state of charge (SoC), and state of energy (SoE) were compared with the observed results. Noise values of one standard deviation from the mean values of the internal charge states of the battery model during a reference run were used to vary the states during simulation. One application used an equivalent circuit model of the electrical dynamics of the battery pack, and the other application used a reduced-order electrochemistry model. The variation of the model state components was compared to the variation in the estimate of the RFT and the variation in the SoE to estimate a confidence factor. Variation in the estimates caused by factors affecting the off-line laboratory parameter identification experiments is considered. Variation in the estimates due to environmental factors are discussed.

Assurance↗

NASA NTRS2018

Agile Approach to Adding Assurance and Mitigating Overall Mission Risk for Orion Software on EM-1

Human-rated missions like Orion are becoming exceedingly complex in terms of software contribution to achieving mission objectives, and this creates a resource challenge for everyone whose job is to add assurance that the mission is going to fly safely. Orion IV&V has addressed this challenge by providing focused assurance results of critical mission capabilities prioritized by a dynamic assessment of risk level. Prior to this approach, Orion IV&V was evaluating areas of risk in much broader, and more static, terms. Due to the Agile software development cycle that Orion follows, IV&V findings were often reported months out of phase with the developer. As a result of evolving the approach to providing assurance on Orion, IV&V is able to incrementally deliver high-priority assurance data and more impactful issues more in phase with the developer activities, thereby increasing the value of the findings to the project. The agile IV&V approach employed by the Orion IV&V team strives to achieve a cadence of delivery that matches the pace of development. This agile approach provides increased flexibility for the assurance provider to become more efficient in reporting assurance conclusions and issues. This presentation will discuss the principles which drive the design of our approach, results to date, and aspirations for long-term performance.

Assurance↗