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 361 records · Page 20

Progress on Advancing the Robotic Air-slot Volumetric Inspection System (RAVIS) for Hanford Under-tank Inspection - 20519

The 27 in-service double-shell tank (DST) systems at Hanford provide interim storage for nearly 56 million gallons of nuclear and hazardous chemical legacy waste. The safe and reliable storage of the waste is critical to the site's extended cleanup mission. While in service, the leak integrity of the DSTs must be demonstrated to satisfy the Washington Administrative Code, inform decisions on tank management, and gauge fitness for continued service beyond originally intended design lives. The carbon steel plates and welds that comprise DST primary tank sidewalls and lower knuckles are routinely 'sampled' for volumetric non-destructive testing using ultrasonic inspection technology to determine whether corrosion pitting, cracking, or general corrosion are occurring that could compromise tank leak integrity. However, the carbon steel plates and welds that comprise the bottoms of primary tanks have not been thoroughly inspected since the DSTs were constructed (i.e., since 1968-1986) due to limited physical access to the exterior tank bottoms. The Robotic Air-slot Volumetric Inspection System, or 'RAVIS,' is being engineered to overcome the challenge of tank bottom in-service inspection. The system will be deployed under primary tanks within the small cooling channels/air-slots in the refractory pads upon which the tanks rest and will use ultrasonic guided wave inspection technology to volumetrically inspect physically inaccessible regions that make up ∼90% of a tank bottom, as well as regions that are physically accessible from the air-slots but comprise only ∼10% of a tank bottom. This paper describes the air-slot sensor and robotic deployment system and focuses on the testing approach and methods that are being applied to support (1) design feedback and performance acceptance (requirement verification) and (2) performance repeatability/reliability assessments (qualification) to ensure the RAVIS is prepared for successful inservice inspections of primary tank bottoms. Test progress made against the test plan, the results of 2019 testing, and the future outlook are included. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

STK Integrated Message Production List Editor (SIMPLE) for CEO Operations

Late in fiscal year 2011, the Crew Earth Observations (CEO) team was tasked to upgrade and replace its mission planning and mission operations software systems, which were developed in the Space Shuttle era of the 1980s and 1990s. The impetuses for this change were the planned transition of all workstations to the Windows 7 64-bit operating system and the desire for more efficient and effective use of Satellite Tool Kit (STK) software required for reliable International Space Station (ISS) Earth location tracking. An additional requirement of this new system was the use of the same SQL database of CEO science sites from the SMMS, which was also being developed. STK Integrated Message Production List Editor (SIMPLE) is the essential, all-in-one tool now used by CEO staff to perform daily ISS mission planning to meet its requirement to acquire astronaut photography of specific sites on Earth. The sites are part of a managed, long-term database that has been defined and developed for scientific, educational, and public interest. SIMPLE's end product is a set of basic time and location data computed for an operator-selected set of targets that the ISS crew will be asked to photograph (photography is typically planned 12 to 36 hours out). The CEO operator uses SIMPLE to (a) specify a payload operations planning period; (b) acquire and validate the best available ephemeris data (vectors) for the ISS during the planning period; (c) ingest and display mission-specific site information from the CEO database; (d) identify and display potential current dynamic event targets as map features; (e) compute and display time and location information for each target; (f) screen and select targets based on known crew availability constraints, obliquity constraints, and real-time evaluated constraints to target visibility due to illumination (sun elevation) and atmospheric conditions (weather); and finally (g) incorporate basic, computed time and location information for each selected target into the daily CEO Target List product (message) for submission to ISS payload planning and integration teams for their review and approval prior to uplink. SIMPLE requires and uses the following resources: an ISS mission planning period Greenwich Mean Time start date/time and end date/time), the best available ISS mission ephemeris data (vectors) for that planning period, the STK software package configured for the ISS, and an ISS mission-specific subset of the CEO sites database. The primary advantages realized by the development and implementation of SIMPLE into the CEO payload operations support activity are a smooth transition to the Windows 7 operating system upon scheduled workstation refresh; streamlining of the input and verification of the current ISS ephemeris (vector data); seamless incorporation of selected contents of the SQL database of science sites; the ability to tag and display potential dynamic event opportunities on orbit track maps; simplification of the display and selection of encountered sites based on crew availability, illumination, obliquity, and weather constraints; the incorporation of high-quality mapping of the Earth with various satellite-based datasets for use in describing targets; and the ability to encapsulate and export the essential selected target elements in XML format for use by onboard Earth-location systems, such as Worldmap. SIMPLE is a carefully designed and crafted in-house software package that includes detailed help files for the user and meticulous internal documentation for future modifications. It was delivered in February 2012 for test and evaluation. Following acceptance, it was implemented for CEO mission operations support in May 2012.

Trenchard, Mike↗

Flexible Microsensor Array for the Monitoring and Control of Plant Growth System

Testing for plant experiments in space has begun to explore active nutrient delivery concepts in which water and nutrients are replenished on a continuous basis for long-term growth. The goal of this study is to develop a novel microsensor array to provide information on the dissolved oxygen environment in the plant root zone for the optimum control of hydroponics and solid substrate plant cultivation systems in the space environment. Miniaturized polarographic dissolved oxygen sensors have been designed and fabricated on a flexible Kapton (trademark) (polyimide) substrate. Two capabilities of the new microsensor array were explored. First, measurements of dissolved oxygen in the plant root zone in hydroponics and solid substrate culture systems were made. The microsensor array was fabricated on a flexible substrate, and then cut out into a mesh type to make a suspended array that could be placed either in a hydroponics system or in a solid substrate cultivation system to measure the oxygen environments. Second, the in situ self-diagnostic and self-calibration capability (two-point for oxygen) was adopted by dynamically controlling the microenvironment in close proximity to the microsensors. With a built-in generating electrode that surrounds the microsensor, two kinds of microenvironments (oxygen-saturated and oxygen-depleted phases) could be established by water electrolysis depending on the polarity of the generating electrode. The unique features of the new microsensor array (small size, multiple sensors, flexibility and self-diagnosis) can have exceptional benefits for the study and optimization of plant cultivation systems in both terrestrial and microgravity environments. The in situ self-diagnostic and self-calibration features of the microsensor array will also enable continuous verification of the operability during entire plant growth cycles. This concept of automated control of a novel chemical monitoring system will minimize crew time required for maintenance, as well as reduce volume, mass, and power consumption by eliminating bulky diagnosis systems including calibrant (fluid and gas) reservoir and flow system hardware.

Kim, Chang-Soo↗

The Role and Quality of Software Safety in the NASA Constellation Program

In this study, we examine software safety risk in the early design phase of the NASA Constellation spaceflight program. Obtaining an accurate, program-wide picture of software safety risk is difficult across multiple, independently-developing systems. We leverage one source of safety information, hazard analysis, to provide NASA quality assurance managers with information regarding the ongoing state of software safety across the program. The goal of this research is two-fold: 1) to quantify the relative importance of software with respect to system safety; and 2) to quantify the level of risk presented by software in the hazard analysis. We examined 154 hazard reports created during the preliminary design phase of three major flight hardware systems within the Constellation program. To quantify the importance of software, we collected metrics based on the number of software-related causes and controls of hazardous conditions. To quantify the level of risk presented by software, we created a metric scheme to measure the specificity of these software causes. We found that from 49-70% of hazardous conditions in the three systems could be caused by software or software was involved in the prevention of the hazardous condition. We also found that 12-17% of the 2013 hazard causes involved software, and that 23-29% of all causes had a software control. Furthermore, 10-12% of all controls were software-based. There is potential for inaccuracy in these counts, however, as software causes are not consistently scoped, and the presence of software in a cause or control is not always clear. The application of our software specificity metrics also identified risks in the hazard reporting process. In particular, we found a number of traceability risks in the hazard reports may impede verification of software and system safety.

Layman, Lucas↗

Enabling Assurance in the MBSE Environment

A number of specific benefits that fit within the hallmarks of effective development are realized with implementation of model-based approaches to systems and assurance. Model Based Systems Engineering (MBSE) enabled by standardized modeling languages (e.g., SysML®) is at the core. These benefits in the context of spaceflight system challenges can include [1]: • Improved management of complex development • Reduced risk in the development process • Improved cost management • Improved design decisions With appropriate modeling techniques the assurance community also can improve early oversight and insight into project development. NASA has shown the basic constructs of SysML in an MBSE environment offer several key advantages, within a Model Based Mission Assurance (MBMA) initiative [2, 3]. These include the following: • Model viewpoints that promote rapid and systematic assessment of requirements coverage, hazard tagging and risk management • Embedded safety assessments for launch vehicles • Deployment of model assisted development of reliability products - Failure Modes and Effects Analyses (FMEAs) and Fault Trees • Test Planning • Validation and Verification of complex functions • Support of Assurance Case development for complex systems In addition, while there are benefits to be harvested, there is a realization that these do not come without effort and cost. Enabling model-based approaches requires structure, not only in an organizational context, but in a modeling context as well. There can be a steep learning curve and costs associated to train skilled modelers. But, on the other hand, not all of the assurance community need to be modelers. Models themselves must conform to ontologies that enable assurance. This places constraints upon the models and modelers. Optimums have yet to be developed where resources and constraints on modeling must be traded off in the organization and modeling efforts for projects. A number of barriers need to be overcome, as well, which pose challenges to the developers of the software that supports MBSE/MBMA. Information and data must be made to flow seamlessly through the life cycle. Because there is a wide variety of tools used in the community, to avoid the problems of the past of silos, delays, and diverging interests, information should flow among these tools to support the “single source of truth” paradigm of MBSE. This will greatly facilitate MBMA and advancement of assurance functions.

Evans, John W.↗

Recommendations on Evidence and Process for Certification of Learning-enabled Components in Aerospace Systems

This report primarily identifies a collection of relevant and necessary evidence for assurance of machine learnt components (MLCs)—also known as learning-enabled components—integrated into aircraft systems, and gives preliminary suggestions on the elements of a certification process that invoke the identified evidence. The main focus is on feedforward neural networks that are static and trained offline through supervised learning. A brief background on the generic elements of the lifecycle of an MLC is given to contextualize the assurance considerations and, consequently, the evidence that is relevant and necessary to support certification. At the level of an MLC, those considerations relate to: (i) the consistency and correctness of MLC contributions to system functions in the context of a validated functional intent; and (ii) the absence of MLC contributions to aircraft-level failure conditions. At an ML model level, confidence in model and data properties contribute to assurance of the containing MLC, in particular: (a) generalizability and robustness of models, in the presence of inputs not previously seen during training, disturbances to inputs, and unexpected inputs; and (b) valid data, i.e., data that are at least representative, relevant, complete, and accurate. Evidence for the above span the elements of the ML lifecycle, and includes, at a minimum, lifecycle artifacts that pertain to: (1) properties of requirements capturing functional intent, safety constraints, and aspects of the intended use and operating environment; (2) model performance, model complexity and design, and algorithm choice; (3) achievement of required performance at the levels of a trained model during model development, a trained model after model development is complete, and a trained model that is transformed into an executable equivalent; (4) model implementation aspects necessary for transforming a trained model into the executable equivalent; (5) integration of the executable trained model into the containing MLC, and eventually the larger system; and, (6) lastly, the verification and validation (V&V) of each of the above. Such V&V lifecycle artifacts themselves include: aspects of coverage, e.g., of various levels of requirements by the input space of the model and the data; traceability (where applicable); application of formal methods for property specification, analysis, and checking. Examples of evidence generation methods and tools further ground the discussion on what constitutes evidence, and the contribution to assurance during certification. The identified assurance considerations and supporting evidence is not a comprehensive set. Additionally, neither what should be considered as sufficient evidence relative to the assigned criticality of an MLC, nor how criticality ought to be determined and adjusted, have been considered in this report. However, suggestions are made for potential activities of the ML lifecycle that are aimed at providing confidence that an MLC can be relied upon when integrated into its containing (aircraft) system. Those activities are proposed as candidate elements of a certification process for MLCs. The main purpose of this report to inform regulatory guidance and consensus standards that may be used to meet the safety intent of the applicable regulations.

Aviation safety↗

Technical Reference Suite Addressing Challenges of Providing Assurance for Fault Management Architectural Design

Research into complexities of software systems Fault Management (FM) and how architectural design decisions affect safety, preservation of assets, and maintenance of desired system functionality has coalesced into a technical reference (TR) suite that advances the provision of safety and mission assurance. The NASA Independent Verification and Validation (IV&V) Program, with Software Assurance Research Program support, extracted FM architectures across the IV&V portfolio to evaluate robustness, assess visibility for validation and test, and define software assurance methods applied to the architectures and designs. This investigation spanned IV&V projects with seven different primary developers, a wide range of sizes and complexities, and encompassed Deep Space Robotic, Human Spaceflight, and Earth Orbiter mission FM architectures. The initiative continues with an expansion of the TR suite to include Launch Vehicles, adding the benefit of investigating differences intrinsic to model-based FM architectures and insight into complexities of FM within an Agile software development environment, in order to improve awareness of how nontraditional processes affect FM architectural design and system health management. The identification of particular FM architectures, visibility, and associated IV&V techniques provides a TR suite that enables greater assurance that critical software systems will adequately protect against faults and respond to adverse conditions. Additionally, the role FM has with regard to strengthened security requirements, with potential to advance overall asset protection of flight software systems, is being addressed with the development of an adverse conditions database encompassing flight software vulnerabilities. Capitalizing on the established framework, this TR suite provides assurance capability for a variety of FM architectures and varied development approaches. Research results are being disseminated across NASA, other agencies, and the software community. This paper discusses the findings and TR suite informing the FM domain in best practices for FM architectural design, visibility observations, and methods employed for IV&V and mission assurance.

Fitz, Rhonda↗

Comparative Analysis of Static and Dynamic Probabilistic Risk Assessment

This study examines three different methodologies for producing loss-of-mission (LOM) and loss-of-crew (LOC) risks estimates for probabilistic risk assessments (PRA) of crewed spacecraft. The three bottom-up, component-based PRA approaches examined are a traditional static fault tree, a dynamic Monte Carlo simulation, and a fault tree hybrid that incorporates some dynamic elements. These approaches were used to model the reaction control system thruster pod of a generic crewed spacecraft and mission, and a comparative analysis of the methods is presented. The methodologies are assessed in terms of the process of modeling a system, the actionable information produced for the design team, and the overall fidelity of the quantitative risk evaluation generated. The system modeling process is compared in terms of the effort required to generate the initial model, update the model in response to design changes, and support mass-versus-risk trade studies. The results are compared by examining the top-level LOM/LOC estimates and the relative risk driver rankings at the failure mode level. The fidelity of each modeling methodology is discussed in terms of its capability to handle real-world system dynamics such as cold-sparing, changes in mission operations due to loss of redundancy, and common cause failure modes. The paper also discusses the applicability of each methodology to different phases of system development and shows that a single methodology may not be suitable for all of the many purposes of a spacecraft PRA. The fault tree hybrid approach is shown to be best suited to the needs of early assessments during conceptual design phases. As the design begins to mature, the level of detail represented in the risk model must go beyond redundancy and nominal mission operations to include dynamic, time- and state-dependent system responses as well as diverse system capabilities. This is best accomplished using the dynamic simulation approach, since these phenomena are not easily captured by static methods. Ultimately, once the design has been finalized and the goal of the PRA is to provide design validation and requirement verification, more traditional, static fault tree approaches may become as appropriate as the simulation method.

Mattenberger, Christopher J.↗

Operational Modal Analysis of the Space Launch System Mobile Launcher on the Crawler Transporter ISVV-010 Rollout

NASA is developing an expendable heavy lift launch vehicle capability, the Space Launch System, to support lunar and deep space exploration. To support this capability, an updated ground infrastructure is required including modifying an existing Mobile Launcher system. The Mobile Launcher is a very large heavy beam/truss steel structure designed to support the Space Launch System during its buildup and integration in the Vehicle Assembly Building, transportation between the Vehicle Assembly Building and launch pad 39B by the Crawler Transporter, and provides the launch platform at the launch pad. As part of the Verification and Validation of the Mobile Launcher and Crawler Transporter, two rollouts of the Mobile Launcher transported by the Crawler Transporter, Integrated System Verification and Validation (ISVV) 005 and 010, have been performed to demonstrate the Crawler Transporter’s ability to transport the Mobile Launcher. ISVV-005 occurred in September 2018 and ISVV-010 occurred in late June 2019. ISVV-005 and ISVV-010 also provided the opportunity to gather data that can be used identify the Mobile Launcher on the Crawler Transporter rollout modal characteristics and refine the estimates of the Artemis I integrated launch vehicle rollout forcing functions. While the rollout environment has historically produced relatively small launch vehicle structural loads for the Saturn/Apollo and Space Shuttle programs in comparison to launch and ascent loads, these relatively small structural loads are inputs to structural fatigue analyses. The same holds true for the Space Launch System. Because the rollout forces acting on the Mobile Launcher and the Crawler Transporter are not directly measurable, Operational Modal Analysis techniques, instead of traditional Experimental Modal Analysis techniques, provide an empirical means to identify the Mobile Launcher on the Crawler Transporter rollout modal characteristics. The ISVV-010 rollout modal characteristics provide important supplemental modal information, which along with the Mobile Launcher modal test that was performed in June 2019 immediately prior to ISVV-010 rollout, combine to reduce uncertainty in the test correlated Mobile Launcher on the Crawler Transporter finite element model. A well test correlated finite element model will play a key role in the Building Block approach the Space Launch System program has implemented as part of its certification process for the Artemis I flight and in refining the Artemis I rollout forcing functions. At the time of the ISVV-005 rollout in September 2018, the Mobile Launcher was still undergoing construction, and therefore its modal characteristics are not directly comparable to those of the Mobile Launcher during the June 2019 Mobile Launcher modal test and subsequent ISVV-010 rollout. Hence the ISVV-005 rollout modal characteristics will not be looked at in this paper. This paper will briefly describe the Mobile Launcher and Crawler Transporter physical characteristics, ISVV-010 rollout data collection, the challenges in implementing Operational Modal Analysis techniques due in part to the Crawler Transporter harmonics, and how these challenges were overcome to obtain the ISVV-010 Mobile Launcher on the Crawler Transporter rollout modal characteristics.

Apollo↗

Operational Modal Analysis of the Space Launch System Mobile Launcher on the Crawler Transporter ISVV-010 Rollout

NASA is developing an expendable heavy lift launch vehicle capability, the Space Launch System, to support lunar and deep space exploration. To support this capability, an updated ground infrastructure is required including modifying an existing Mobile Launcher system. The Mobile Launcher is a very large heavy beam/truss steel structure designed to support the Space Launch System during its buildup and integration in the Vehicle Assembly Building, transportation between the Vehicle Assembly Building and launch pad 39B by the Crawler Transporter, and provides the launch platform at the launch pad. As part of the Verification and Validation of the Mobile Launcher and Crawler Transporter, two rollouts of the Mobile Launcher transported by the Crawler Transporter, Integrated System Verification and Validation (ISVV) 005 and 010, have been performed to demonstrate the Crawler Transporter’s ability to transport the Mobile Launcher. ISVV-005 occurred in September 2018 and ISVV-010 occurred in late June 2019. ISVV-005 and ISVV-010 also provided the opportunity to gather data that can be used identify the Mobile Launcher on the Crawler Transporter rollout modal characteristics and refine the estimates of the Artemis I integrated launch vehicle rollout forcing functions. While the rollout environment has historically produced relatively small launch vehicle structural loads for the Saturn/Apollo and Space Shuttle programs in comparison to launch and ascent loads, these relatively small structural loads are inputs to structural fatigue analyses. The same holds true for the Space Launch System. Because the rollout forces acting on the Mobile Launcher and the Crawler Transporter are not directly measurable, Operational Modal Analysis techniques, instead of traditional Experimental Modal Analysis techniques, provide an empirical means to identify the Mobile Launcher on the Crawler Transporter rollout modal characteristics. The ISVV-010 rollout modal characteristics provide important supplemental modal information, which along with the Mobile Launcher modal test that was performed in June 2019 immediately prior to ISVV-010 rollout, combine to reduce uncertainty in the test correlated Mobile Launcher on the Crawler Transporter finite element model. A well test correlated finite element model will play a key role in the Building Block approach the Space Launch System program has implemented as part of its certification process for the Artemis I flight and in refining the Artemis I rollout forcing functions. At the time of the ISVV-005 rollout in September 2018, the Mobile Launcher was still undergoing construction, and therefore its modal characteristics are not directly comparable to those of the Mobile Launcher during the June 2019 Mobile Launcher modal test and subsequent ISVV-010 rollout. Hence the ISVV-005 rollout modal characteristics will not be looked at in this paper. This paper will briefly describe the Mobile Launcher and Crawler Transporter physical characteristics, ISVV-010 rollout data collection, the challenges in implementing Operational Modal Analysis techniques due in part to the Crawler Transporter harmonics, and how these challenges were overcome to obtain the ISVV-010 Mobile Launcher on the Crawler Transporter rollout modal characteristics.

Apollo↗

Use of multiple gauges and microwave attenuation of precipitation for satellite verification

In this paper both a microwave attenuation measurement along a horizontal line and multiple point gauge measurements are analyzed as possible ground-truth designs to validate satellite precipitation retrieval algorithms at the field of view spatial level (typically about 20 km). The design consists of comparing a sequence of pairs of contemporaneous measurements taken from the ground and from space. The authors examine theoretically the variance of expected differences between the two systems. The line average measurement leads to a smaller mean-square error compared to the case of a single point gauge, since some of the small-scale variability of the rain field is smoothed away by the line integration. The multiple point gauge measurements also give smaller mean-square error than that of a single point gauge. The centroid of the line and point gauge configurations are considered to be located randomly inside the field of view for different overpasses. A space-time spectral formalism is used with a noise-forced diffusive rain field to find the mean-square error. By considering instantaneous ground and satellite measurement pairs over about 50 visits when raining, we can reduce the expected error to approximately 10% of the standard deviation of climatological variability. This is considered to be a useful level of tolerance for identifying biases in the retrieval algorithms. It is found that the multiple point gauges (especially two gauges) are the economical ground-truth design compared to the microwave attenuation based on the mean-square error comparison. The major finding of this study is that a significant improvement over the point gauge is obtained by adding a single additional piece of information; adding more gauges or extending the line of attenuation is not an important improvement.

Ha, Eunho↗

Supporting Crew Autonomy in Deep Space Exploration: Preliminary Onboard Capability Requirements and Proposed Research Questions. Technical Report of the Autonomous Crew Operations Technical Interchange Meeting

Communication delays are a critical challenge posed by long duration deep space exploration. Space missions historically have relied on an ever-present Mission Control Center (MCC) to direct operations in near real-time. As unanticipated anomalies that defeat fault detection and resolution systems do arise, the lack of real-time communication will significantly weaken what the MCC support represents: a reliable safety net for the flight crew through its deep and diverse areas of expertise and investigative resources. As a consequence, future space vehicles and habitats need to be equipped with capabilities to support the flight crew to operate with little or no ground support. Considerations must be given to vehicle and mission designs that will fortify the traditionally ground-centered safety net and forge new support systems, when communication delays exist. In August 2018, NASA’s Human Research Program, through its Human Factors and Behavioral Performance Element, convened a Technical Interchange Meeting (TIM) on Autonomous Crew Operations at NASA Ames Research Center. The goal of the meeting was to gather input from NASA centers, industry, academia, and branches of the Department of Defense (DoD) to address how intelligent technologies can be applied to augment onboard capabilities to support crew anomaly response. The TIM featured 24 presentations by 29 speakers and hosted a total of 59 attendees, including 43 from 5 NASA centers (Ames, Johnson, Langley, Marshall, and Jet Propulsion Lab) and 4 from the DoD (3 from Army Research Lab and 1 from Naval Postgraduate School), with remaining attendees from academia (e.g., UC Davis, CMU) and industry (e.g., IBM, Siemens). Discussions were centered around three themes: standards and guidelines, lessons learned in analog environments, and technologies. To help provide a framework for discussion, a concept matrix describing anomaly response processes was created prior to the TIM (Figure 1, page 6). The matrix captures the steps involved (monitoring and detection, diagnosis, solution development and evaluation, solution implementation and verification, resolution documentation) as well as the resources and capabilities required to support these steps (data, knowledge, analysis, synthesis, resource management). A wallpaper size printout of the matrix was utilized at the TIM to solicit attendee inputs along the three themes; the activity garnered 108 submissions of ideas. Overall, what emerged from TIM discussions was a picture of mismatch between crew anomaly response needs and support that can be provided by existing intelligent technologies. The needs are broad, spanning multiple steps and processes/resources, with many of which lacking support from existing technologies, such as knowledge management throughout the steps of problem solving (especially in resolution documentation) and manpower management. The solutions provided by existing intelligent technologies are specific to the steps/processes that they are designed to support and constrained to solving only problems similar to those that have occurred before. What is lacking from technologies is typically made up by humans, specifically their complex critical thinking, creative problem solving, and domain expertise. In the end, the TIM highlighted the pressing need to support responses to onboard anomalies during autonomous crew operations, particularly those that have eluded the system tests, inspection, and other assurance processes. Such anomalies can potentially threaten crew and vehicle safety, as well as significantly impact overall operations with additional workload. These fairly rare events are difficult to anticipate and prepare for, given the state-of-the-art in intelligent technologies. This is true even for anomalies that stem from “unknown knowns”—cases in which there is sufficient external information to characterize the problem but the overall pattern fails to be recognized by the problem solver, or in which the internal knowledge needed to solve a problem is held tacitly and potentially accessible by the problem solver but not articulated. It follows that the ability to tackle anomalies lies not only with the availability of relevant information and knowledge but also their accessibility in times of need. To that end, we propose research questions along the following three broad themes: • How intelligent technologies can help make relevant knowledge and information available? • How intelligent technologies can help make relevant knowledge and information accessible? • How intelligent technologies can help support the crew operating as a team in anomaly response processes?

autonomous crew operations↗

Establishing Fault Tolerance for a Class of Systems by Experiment

A long-standing problem in system verification is establishing fault tolerance at the ultra-high level by experiment. It is considered impossible because of system complexity and the enormous number of trials needed. This paper considers the problem for a class of digital systems that use redundancy to achieve reliability. The class is the systems that operate for a period of time without maintenance followed by a maintenance check that replaces components identified as faulty. The paper considers simulating a natural life test where a natural life test observes a number of operating periods. If the system does not fail during the test, it can be said to have a certain reliability at a certain confidence level. The approach in this paper is to make the simulated life test more efficient while maintaining realism by integrating structural arguments, information on fault occurrence, and fault injection in the lab. The major result of this paper is constructing a global fault model using the failure rate of the components and proving theorems about the model that tell how many, what kind, when, and where to inject faults. A simple example illustrates applying the theorems.

design of experiments↗

GHEP WIBT (Guidelines for Home Energy Professionals Weatherization Installer Badges Toolkit) [SWR-20-69]

The National Renewable Energy Laboratory (NREL) and the U.S. Department of Energy's (DOE) Weatherization Assistance Program (WAP) are collaborating with the home energy retrofit industry to support the development of skilled workers. The Installer Badges Toolkit provides a flexible, customizable, and voluntary approach to training and skills recognition for WAP implementers, utility programs, private-sector workers, and contractors. In Fiscal Year 2018, DOE, along with the Crew Leader scheme committee, determined the Retrofit Installer Technician (RIT) Job Task Analysis (JTA) could be eliminated and its tasks inserted in the Crew Leader JTA. The RIT tasks became the basis of the Installer Badges. The Badges Toolkit was updated in 2020 to add licensing and copyright agreements. Users must cite the copyright information when using or distributing copies of the Badges Toolkit in any way. The technical content has remained unchanged from previous versions of the Badges Toolkit. The Toolkit for home retrofits consists of 25 Badges, each representing different energy efficiency tasks that an installer could perform on a home. Each Badge defines the desired outcome, criteria to verify, applicable material requirements, and references to Standard Work Specifications (SWS) or other relevant standards. The Badges provide a consistent approach to training by ensuring that installers in different regions are learning the same skills nationwide. Organizations can also customize the Toolkit by choosing only those Badges that are relevant to their program. The Badges Toolkit includes five pieces: "How to Use the Badges Toolkit" provides a brief overview of how a Grantee, Subgrantee, or training provider may approach using the toolkit. The "Badges Toolkit: Worksheet" includes what to consider when determining whether and how to best incorporate the Badges into a weatherization assistance program. The "Crew Leader Job Task Analysis Spreadsheet" indicates how the Badges align with specific areas of the JTA. The "Installer Badges Passport" features separate pages for each Badge, which include places for the installer and the supervisor/trainer to record the number of times a task has been successfully completed. The "Installer Badges Verification Criteria" includes sample inspection checklists for each Badge. These can be modified as needed based on approved variance requests or more stringent requirements. They also provide a basis for consistent inspections and awarding of Badges. Note: All elements of the Badges Toolkit are designed for use by potential program implementers. They are not off-the-shelf products intended for immediate deployment. Program implementers must review and modify as needed, revise verification criteria to match local requirements, complete worksheets, and otherwise define the parameters of their own badging program.

Desai, Jal↗

Mangrove Carbon Stocks in Pongara National Park, Gabon

Mangroves are recognized for their valued ecosystem services to coastal areas, and the functional linkages between those services and ecosystem carbon stocks have been established. However, spatially explicit inventories are necessary to facilitate management and protection of mangroves, as well as providing a foundation for payment for ecosystem service programs such as REDD+. We conducted an inventory of carbon stocks in mangroves within Pongara National Park (PNP), Gabon using a stratified random sampling design based on forest canopy height derived from TanDEM-X remote sensing data. Ecosystem carbon pools, including aboveground and belowground biomass and necromass, and soil carbon to a depth of 2 m were assessed using measurements and samples from plots distributed among three canopy height classes within the park. There were two mangrove species within the inventory area in PNP, Rhizophora racemosa and R. harrisonii. R. harrisonii was predominant in the sparse, low-stature stands that dominated the west side of the park. In the east side of the park, both species occurred in tall-stature stands, with tree height often exceeding 30 m. Canopy height was an effective means to stratify the inventory area, as biomass was significantly different among the height classes. Despite those differences in aboveground biomass, the soil carbon density was not significantly different among height classes. Soils were the main component of the ecosystem carbon stock, accounting for over 84% of the total. The ecosystem carbon density ranged from 644 to 943 Mg C ha−1 among the three height classes. The ecosystem carbon stock within PNP is estimated to be 40,588 Gg C. The combination of pre-inventory information about stand conditions and their spatial distribution within the assessment area obtained from remote sensing data and a spatial decision support system were fundamental to implementing this relatively large-scale field inventory. This work exemplifies how mangrove carbon stocks can be quantified to augment national C reporting statistics, provide a baseline for projects involving monitoring, reporting and verification (i.e., MRV), and provide data on the forest composition and structure for sustainable management and conservation practices.

Carl C Trettin↗

The OpenSE Cookbook: A Practical, Recipe Based Collection of Patterns, Procedures, and Best Practices for Executable Systems Engineering for the Thirty Meter Telescope

The OpenSE Cookbook is an open-sourced collection of patterns, procedures, and best practices targeted for systems engineers who seek guidance on applying model-based and executable systems engineering (MBSE) using SysML. Its content has emerged from the system level modeling effort on the European Framework Program 6 (FP6) and the Thirty Meter Telescope (TMT). The TMT MBSE approach applied the Executable Systems Engineering Method (ESEM) and the open-source Engineering Environment (OpenMBEE) to specify, analyze, and verify requirements of TMT’s Alignment and Phasing System (APS) and the Narrow Field Infrared Adaptive Optics System (NFIRAOS). In these applications, implicit dependencies are made explicit in a formal model through the use of ESEM, OpenMBEE, and SysML modeling constructs. The value proposition for applying this MBSE approach was to establish precise requirements and fine-grained traceability to system designs, and to verify key requirements beginning early in development. The integration of ESEM and the OpenMBEE tooling infrastructure (providing linked-data and web-operability) is a significant added value for the MBSE approach. The APS is responsible for the overall pre-adaptive optics wavefront quality, using starlight to measure wavefront errors and align the TMT optics. In the formally integrated and executable SysML model, simulations are performed to analyze the impact of changed requirements and verify specified constraints for various operational scenarios. The APS team used several modeling patterns to capture information such as the requirements, the operational scenarios, involved subsystems and their interaction points, the estimated or required time durations, and the mass and power consumption. Adaptive optics systems are designed to sense real-time atmospheric turbulence and correct the telescope’s optical beam to remove its effect. The system model for the adaptive optics operational modes was developed to capture sequence behaviors and operational scenarios to run Monte-Carlo simulations for verifying acquisition time, observing efficiency, and operational behavior requirements. The model is particularly useful for investigating the effect of parallelization, identifying interface issues, and re-ordering sequence acquisition tasks. A former version of the Cookbook (which is now updated to MBSE challenges, goals, and lessons learned) included modeling guidelines and conventions for all system aspects, hierarchy levels, and views, which were developed during for the Active Phasing Experiment (APE), an opto-mechatronical system technology demonstrator for the Extremely Large Telescope (ELT). The Cookbook utilizes the above mentioned system models as real-world case-studies to demonstrate and document the applications of the recipes, providing also instructional examples and addressing the available tooling support. The Cookbook is accompanied by a number of SysML models and aodel libraries which facilitate model authoring and maintenance. The Cookbook covers the different aspects of Systems Engineering such as management of Requirements, Design (behavior and structure), Interfaces, Interdisciplinary Integration, Analysis, Trade Studies, and Technical Resources. This paper presents the background, motivation, architecture, and highlights some key content of the Cookbook. For example, interface management, error budget management, requirements verification, Monte Carlo driven analysis, and timing analysis of operational scenarios. The paper discusses how the capabilities of OpenMBEE contributed significantly to the adoption of executable systems engineering.

Brower, Eric↗

The Goddard High Resolution Spectrograph Scientific Support Contract

In 1988, Computer Sciences Corporation (CSC) was selected as the Goddard High Resolution Spectrograph (GHRS) Scientific Support Contractor (SSC). This was to have been a few months before the launch of NASA's first Great Observatory, the Hubble Space Telescope (HST). As one of five scientific instruments on HST, the GHRS was designed to obtain spectra in the 1050-3300 A ultraviolet wavelength region with a resolving power, lambda/Delta(lambda) , of up to 100,000 and relative photometric accuracy to 1%. It was built by Ball AeroSpace Systems Group under the guidance of the GHRS Investigation Definition Team (IDT), comprised of 16 scientists from the US and Canada. After launch, the IDT was to perform the initial instrument calibration and execute a broad scientific program during a five-year Guaranteed Time Observation (GTO) period. After a year's delay, the launch of HST occurred in April 1990, and CSC participated in the in-orbit calibration and first four years of GTO observations with the IDT. The HST primary mirror suffered from spherical aberration, which reduced the spatial and spectral resolution of Large Science Aperture (LSA) observations and decreased the throughput of the Small Science Aperture (SSA) by a factor of two. Periodic problems with the Side 1 carrousel electronics and anomalies with the low-voltage power supply finally resulted in a suspension of the use of Side 1 less than two years after launch. At the outset, the GHRS SSC task involved work in four areas: 1) to manage and operate the GHRS Data Analysis Facility (DAF); 2) to support the second Servicing Mission Observatory Verification (SMOV) program, as well as perform system engineering analysis of the GHRS as nesessary; 3) to assist the GHRS IDT with their scientific research programs, particularly the GSFC members of the team, and 4) to provide administrative and logistic support for GHRS public information and educational activities.

Source record↗

Advancements in Dual-Pump Broadband CARS for Supersonic Combustion Measurements

Space- and time-resolved measurements of temperature and species mole fractions of nitrogen, oxygen, and hydrogen were obtained with a dual-pump coherent anti-Stokes Raman spectroscopy (CARS) system in hydrogen-fueled supersonic combustion free jet flows. These measurements were taken to provide time-resolved fluid properties of turbulent supersonic combustion for use in the creation and verification of computational fluid dynamic (CFD) models. CFD models of turbulent supersonic combustion flow currently facilitate the design of air-breathing supersonic combustion ramjet (scramjet) engines. Measurements were made in supersonic axi-symmetric free jets of two scales. First, the measurement system was tested in a laboratory environment using a laboratory-scale burner (approx.10 mm at nozzle exit). The flow structures of the laboratory-burner were too small to be resolved with the CARS measurements volume, but the composition and temperature of the jet allowed the performance of the system to be evaluated. Subsequently, the system was tested in a burner that was approximately 6 times larger, whose length scales are better resolved by the CARS measurement volume. During both these measurements, weaknesses of the CARS system, such as sensitivity to vibrations and beam steering and inability to measure temperature or species concentrations in hydrogen fuel injection regions were indentified. Solutions were then implemented in improved CARS systems. One of these improved systems is a dual-pump broadband CARS technique called, Width Increased Dual-pump Enhanced CARS (WIDECARS). The two lowest rotational energy levels of hydrogen detectable by WIDECARS are H2 S(3) and H2 S(4). The detection of these lines gives the system the capability to measure temperature and species concentrations in regions of the flow containing pure hydrogen fuel at room temperature. WIDECARS is also designed for measurements of all the major species (except water) in supersonic combustion flows fueled with hydrogen and hydrogen/ethylene mixtures (N2, O2, H2, C2H4, CO, and CO2). This instrument can characterize supersonic combustion fueled with surrogate fuel mixtures of hydrogen and ethylene. This information can lead to a better understanding of the chemistry and performance of supersonic combustion fueled with cracked jet propulsion (JP)-type fuel.

Tedder, Sarah Augusta Umberger↗