Search NASA⌕ Search

SEARCH · Search NASA

Results for “monitoring verification and reporting”

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.

51 records · Page 3

AIPS technology survey report

The results of a technology survey conducted for the NASA/JSC by the CSDL during Phase 1 of the NASA Advanced Information Processing System (AIPS) program at the CSDL are discussed. The purpose of the survey was to ensure that all technology relevant to the configuration, design, development, verification, implementation, and validation of an advanced information processing system, whether existing or under development and soon to be available, would be duly considered in the development of the AIPS. The emphasis in the survey was on technology items which were clearly relevant to the AIPS. Requirements were developed which guided the planning of contacts with the outside sources to be surveyed, and established practical limits on the scope and content of the Technology Survey. Subjects surveyed included architecture, software, hardware, methods for evaluation of reliability and performance, and methods for the verification of the AIPS design and the validation of the AIPS implementation. Survey requirements and survey results in each of these areas are presented, including analyses of the potential effects on the AIPS development process of using or not using the surveyed technology items. Another output of the survey was the identification of technology areas of particular relevance to the AIPS and for which further development, in some cases by the CSDL and in some cases by the NASA, would be fruitful. Appendices are provided in which are presented: (1) reports of some of the actual survey interactions with industrial and other outside information sources; (2) the literature list from the comprehensive literature survey which was conducted; (3) reduced-scale images of an excerpt ('Technology Survey' viewgraphs) from the set of viewgraphs used at the 14 April 1983 Preliminary Requirements Review by the CSDL for the NASA; and (4) reduced-scale images of the set of viewgraphs used in the AIPS Technology Survey Review presentation to the NASA monitors by the CSDL at the NASA Langley Research Center on 28 Sep. 1983.

Ogletree, Glenn↗

Safeguard: Progress and Test Results for a Reliable Independent On-Board Safety Net for UAS

As demands increase to use unmanned aircraft systems (UAS) for a broad spectrum of commercial applications, regulatory authorities are examining how to safely integrate them without compromising safety or disrupting traditional airspace operations. For small UAS, several operational rules have been established; e.g., do not operate beyond visual line-of-sight, do not fly within five miles of a commercial airport, do not fly above 400 feet above ground level. Enforcing these rules is challenging for UAS, as evidenced by the number of incident reports received by the Federal Aviation Administration (FAA). This paper reviews the development of an onboard system - Safeguard - designed to monitor and enforce conformance to a set of operational rules defined prior to flight (e.g., geospatial stay-out or stay-in regions, speed limits, and altitude constraints). Unlike typical geofencing or geo-limitation functions, Safeguard operates independently of the off-the-shelf UAS autopilot and is designed in a way that can be realized by a small set of verifiable functions to simplify compliance with existing standards for safety-critical systems (e.g. for spacecraft and manned commercial transportation aircraft systems). A framework is described that decouples the system from any other devices on the UAS as well as introduces complementary positioning source(s) for applications that require integrity and availability beyond what can be provided by the Global Positioning System (GPS). This paper summarizes the progress and test results for Safeguard research and development since presentation of the design concept at the 35th Digital Avionics Systems Conference (DASC '16). Significant accomplishments include completion of software verification and validation in accordance with NASA standards for spacecraft systems (to Class B), development of improved hardware prototypes, development of a simulation platform that allows for hardware-in-the-loop testing and fast-time Monte Carlo evaluations, and flight testing on multiple air vehicles. Integration testing with NASA's UAS Traffic Management (UTM) service-oriented architecture was also demonstrated.

Young, Steven D.↗

Quantitative Measures for Software Independent Verification and Validation

As software is maintained or reused, it undergoes an evolution which tends to increase the overall complexity of the code. To understand the effects of this, we brought in statistics experts and leading researchers in software complexity, reliability, and their interrelationships. These experts' project has resulted in our ability to statistically correlate specific code complexity attributes, in orthogonal domains, to errors found over time in the HAL/S flight software which flies in the Space Shuttle. Although only a prototype-tools experiment, the result of this research appears to be extendable to all other NASA software, given appropriate data similar to that logged for the Shuttle onboard software. Our research has demonstrated that a more complete domain coverage can be mathematically demonstrated with the approach we have applied, thereby ensuring full insight into the cause-and-effects relationship between the complexity of a software system and the fault density of that system. By applying the operational profile we can characterize the dynamic effects of software path complexity under this same approach We now have the ability to measure specific attributes which have been statistically demonstrated to correlate to increased error probability, and to know which actions to take, for each complexity domain. Shuttle software verifiers can now monitor the changes in the software complexity, assess the added or decreased risk of software faults in modified code, and determine necessary corrections. The reports, tool documentation, user's guides, and new approach that have resulted from this research effort represent advances in the state of the art of software quality and reliability assurance. Details describing how to apply this technique to other NASA code are contained in this document.

Lee, Alice↗

Wilson Corners SWMU 001 2014 Annual Long Term Monitoring Report Kennedy Space Center, Florida

This document presents the findings of the 2014 Long Term Monitoring (LTM) that was completed at the Wilson Corners site, located at the National Aeronautics and Space Administration (NASA) John F. Kennedy Space Center (KSC), Florida. The goals of the 2014 annual LTM event were to evaluate the groundwater flow direction and gradient and to monitor the vertical and downgradient horizontal extent of the volatile organic compounds (VOCs) in groundwater at the site. The LTM activities consisted of an annual groundwater sampling event in December 2014, which included the collection of water levels from the LTM wells. During the annual groundwater sampling event, depth to groundwater was measured and VOC samples were collected using passive diffusion bags (PDBs) from 30 monitoring wells. In addition to the LTM sampling, additional assessment sampling was performed at the site using low-flow techniques based on previous LTM results and assessment activities. Assessment of monitoring well MW0052DD was performed by collecting VOC samples using low-flow techniques before and after purging 100 gallons from the well. Monitoring well MW0064 was sampled to supplement shallow VOC data north of Hot Spot 2 and east of Hot Spot 4. Monitoring well MW0089 was sampled due to its proximity to MW0090. MW0090 is screened in a deeper interval and had an unexpected detection of trichloroethene (TCE) during the 2013 LTM, which was corroborated during the March 2014 verification sampling. Monitoring well MW0130 was sampled to provide additional VOC data beneath the semi-confining clay layer in the Hot Spot 2 area.

Monitoring↗

Real-Time Culture-Independent Microbial Profiling Onboard the International Space Station using Nanopore Sequencing

For the past two decades, microbial monitoring of the International Space Station (ISS) has relied on culture-dependent methods that require return to Earth for analysis. This has a number of limitations, with the most significant being bias towards the detection of culturable organisms and the inherent delay between sample collection and ground-based analysis. In recent years, portable and easy-to-use molecular-based tools, such as Oxford Nanopore Technologies’ MinION™ sequencer and miniPCR bio’s miniPCR™ thermal cycler, have been validated onboard the ISS. Here, we report on the development, validation, and implementation of a swab-to-sequencer method that provides a culture-independent solution to real-time microbial profiling onboard the ISS. Method development focused on analysis of swabs collected in a low-biomass environment with limited facility resources and stringent controls on allowed processes and reagents. ISS-optimized procedures included enzymatic DNA extraction from a swab tip, bead-based purifications, altered buffers, and the use of miniPCR and the MinION. Validation was conducted through extensive ground-based assessments comparing current standard culture-dependent and newly developed culture-independent methods. Similar microbial distributions were observed between the two methods; however, as expected, the culture-independent data revealed microbial profiles with greater diversity. Protocol optimization and verification was established during NASA Extreme Environment Mission Operations (NEEMO) analog missions 21 and 22, respectively. Unique microbial profiles obtained from analog testing validated the swab-to-sequencer method in an extreme environment. Finally, four independent swab-to-sequencer experiments were conducted onboard the ISS by two crewmembers. Microorganisms identified from ISS swabs were consistent with historical culture-based data, and primarily consisted of commonly observed human-associated microbes. This simplified method has been streamlined for high ease-of-use for a non-trained crew to complete in an extreme environment, thereby enabling environmental and human health diagnostics in real-time as future missions take us beyond low-Earth orbit.

microbiology↗

Solutions Network Formulation Report. Integration of OMI and TES Aerosol Products into the EPA Regional Planning Organizations' FASTNET Aerosol Tracking and Analysis Tool

Every year, more than 280 million visitors tour our Nation s most treasured parks and wilderness areas. Unfortunately, many visitors are unable to see the spectacular vistas they expect because of white or brown haze in the air. Most of this haze is not natural; it is air pollution, carried by the wind often hundreds of miles from its origin. Some of the pollutants have been linked to serious health problems, such as asthma and other lung disorders, and even premature death. In addition, nitrates and sulfates contribute to acid rain formation, which contaminates rivers and lakes and erodes buildings and historical monuments. The U.S. Environmental Protection Agency RPOs (Regional Planning Organizations) have been tasked with monitoring and determining the nature and origin of haze in Class I scenic areas, and finding ways to reduce haze in order to improve visibility in these areas. The RPOs have developed an Internet-based air quality DST (Decision Support Tool) called FASTNET (Fast Aerosol Sensing Tools for Natural Event Tracking). While FASTNET incorporates a few satellite datasets, most of the data utilized by this DST comes from ground-based instrument networks. The problem is that in many areas the sensors are sparsely located, with long distances between them, causing difficulties in tracking haze over the United States, determining its source, and analyzing its content. Satellite data could help to fill in the data gaps and to supplement and verify ground-recorded air quality data. Although satellite data are now being used for air quality research applications, such data are not routinely used for environmental decision support, in part because of limited resources, difficulties with interdisciplinary data interpretation, and the need for advanced inter-agency partnerships. As a result, the validation and verification of satellite data for air quality operational system applications has been limited This candidate solution evaluates the usefulness of OMI (Ozone Monitoring Instrument) and TES (Tropospheric Emission Spectrometer) air quality data for the RPOs by comparing OMI and TES data with ground-based data that are acquired during identified episodes of air pollution. The air quality data from OMI and TES are of different spectral ranges than data from satellites currently included in FASTNET, giving them potential advantages over the existing satellites. If the OMI and TES data are shown to be useful to the RPOs, they would then be integrated into the FASTNET DST for use on an operational basis.

Knowlton, Kelly↗

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↗

Overview of the NASA LISA Laser System Development

NASA Goddard Space Flight Center (GSFC) is developing the Laser System (LS) for the Laser Interferometer Space Antenna (LISA) mission, led by the European Space Agency (ESA) with a launch date of 2035. The LS under development at NASA GSFC consists of the Laser Head (LH), the Frequency Reference System (FRS), and the Power Monitor (PMON) Detector Assemblies. Since late 2017, we have been developing various models to advance the technology readiness level (TRL) for the LH from prototype (TRL4) to a system model demonstration in a relevant environment (TRL6). For the LH and FRS, the models further breakdown into the optical and electronics modules where the LH is made up of the Laser Optical Module (LOM) and the Laser Electronics Module (LEM) and the FRS consists of the FRS Optical Reference Cavity (FRS-O) and the FRS Electronics (FRS-E). The LS development follows the established NASA process in demonstrating the performance requirements [1] through the TRL4 effort and then advancing the form factor and package design to meet relevant environment requirements and qualifying the TRL6 design through rigorous testing and performance verification for space applications. The LOM for the LH is a main oscillator power amplifier (MOPA) with wavelength of 1064 nm and nominal output power of 2 Watt throughout the mission. The low-power, low-noise main oscillator (MO) is a custom micro non-planar ring oscillator (µNPRO) [2] that is phase modulated then amplified by the forward pumped ytterbium-dope fiber power amplifier (PA) stage to meet the output power requirement. The FRS is baselined on the GRACE Follow-On (GFO) [3] approach with updated FRS-E design to work with the LH-LEM. The PMON is located on the Optical Bench Assembly (OBA) [4] that samples a small portion of the LH output signal and provides the feedback signal to the LH-LEM for relative intensity noise (RIN) control. In this paper, we will report on the latest status of the LH testing and system level tests, explain the other subsystems involved in the test campaigns, and discuss the path to bring each LS subsystem to TRL6. We will also present the NASA GSFC roadmap in advancing the LISA LS to TRL6+ and plans for future system level testing as well as the preparation for space flight development to meet the LISA launch date of 2035.

amplifier↗

The Suomi National Polar-Orbiting Partnership (SNPP): Continuing NASA Research and Applications

The Suomi National Polar-orbiting Partnership (SNPP) satellite was successfully launched into a polar orbit on October 28, 2011 carrying 5 remote sensing instruments designed to provide data to improve weather forecasts and to increase understanding of long-term climate change. SNPP provides operational continuity of satellite-based observations for NOAA's Polar-orbiting Operational Environmental Satellites (POES) and continues the long-term record of climate quality observations established by NASA's Earth Observing System (EOS) satellites. In the 2003 to 2011 pre-launch timeframe, NASA's SNPP Science Team assessed the adequacy of the operational Raw Data Records (RDRs), Sensor Data Records (SDRs), and Environmental Data Records (EDRs) from the SNPP instruments for use in NASA Earth Science research, examined the operational algorithms used to produce those data records, and proposed a path forward for the production of climate quality products from SNPP. In order to perform these tasks, a distributed data system, the NASA Science Data Segment (SDS), ingested RDRs, SDRs, and EDRs from the NOAA Archive and Distribution and Interface Data Processing Segments, ADS and IDPS, respectively. The SDS also obtained operational algorithms for evaluation purposes from the NOAA Government Resource for Algorithm Verification, Independent Testing and Evaluation (GRAVITE). Within the NASA SDS, five Product Evaluation and Test Elements (PEATEs) received, ingested, and stored data and performed NASA's data processing, evaluation, and analysis activities. The distributed nature of this data distribution system was established by physically housing each PEATE within one of five Climate Analysis Research Systems (CARS) located at either at a NASA or a university institution. The CARS were organized around 5 key EDRs directly in support of the following NASA Earth Science focus areas: atmospheric sounding, ocean, land, ozone, and atmospheric composition products. The PEATES provided the system level interface with members of the NASA SNPP Science Team and other science investigators within each CARS. A sixth Earth Radiation Budget CARS was established at NASA Langley Research Center (NASA LaRC) to support instrument performance, data evaluation, and analysis for the SNPP Clouds and the Earth's Radiant Budget Energy System (CERES) instrument. Following the 2011 launch of SNPP, spacecraft commissioning, and instrument activation, the NASA SNPP Science Team evaluated the operational RDRs, SDRs, and EDRs produced by the NOAA ADS and IDPS. A key part in that evaluation was the NASA Science Team's independent processing of operational RDRs and SDRs to EDRs using the latest NASA science algorithms. The NASA science evaluation was completed in the December 2012 to April 2014 timeframe with the release of a series of NASA Science Team Discipline Reports. In summary, these reports indicated that the RDRs produced by the SNPP instruments were of sufficiently high quality to be used to create data products suitable for NASA Earth System science and applications. However, the quality of the SDRs and EDRs were found to vary greatly when considering suitability for NASA science. The need for improvements in operational algorithms, adoption of different algorithmic approaches, greater monitoring of on-orbit instrument calibration, greater attention to data product validation, and data reprocessing were prominent findings in the reports. In response to these findings, NASA, in late 2013, directed the NASA SNPP Science Team to use SNPP instrument data to develop data products of sufficiently high quality to enable the continuation of EOS time series data records and to develop innovative, practical applications of SNPP data. This direction necessitated a transition of the SDS data system from its pre-launch assessment mode to one of full data processing and production. To do this, the PEATES, which served as NASA's data product testing environment during the prelaunch and early on-orbit periods, were transitioned to Science Investigator-led Processing Systems (SIPS). The distributed data architecture was maintained in this new system by locating the SIPS at the same institutions at which the CARS and PEATES were located. The SIPS acquire raw SNPP instrument Level 0 (i.e. RDR) data over the full SNPP mission from the NOAA ADS and IDPS through the NASA SDS Data Distribution and Depository Element (SD3E). The SIPS process those data into NASA Level 1, Level 2, and global, gridded Level 3 standard products using peer-reviewed algorithms provided by members of the NASA Science Team. The SIPS work with the NASA SNPP Science Team in obtaining enhanced, refined, or alternate real-time algorithms to support the capabilities of the Direct Readout Laboratory (DRL). All data products, algorithm source codes, coefficients, and auxiliary data used in product generation are archived in an assigned NASA Distributed Active Archive Center (DAAC).

remote sensing↗

Bringing Together Users and Developers of Forest Biomass Maps

Forests store carbon and thus represent important sinks for atmospheric carbon dioxide. Reducing uncertainty in current estimates of the amount of carbon in standing forests will improve precision of estimates of anthropogenic contributions to carbon dioxide in the atmosphere due to deforestation. Although satellite remote sensing has long been an important tool for mapping land cover, until recently aboveground forest biomass estimates have relied mostly on systematic ground sampling of forests. In alignment with fiscal year 2010 congressional direction, NASA has initiated work toward a carbon monitoring system (CMS) that includes both maps of forest biomass and total carbon flux estimates. A goal of the project is to ensure that the products are useful to a wide community of scientists, managers, and policy makers, as well as to carbon cycle scientists. Understanding the needs and requirements of these data users is helpful not just to the NASA CMS program but also to the entire community working on carbon-related activities. To that end, this meeting brought together a small group of natural resource managers and policy makers who use information on forests in their work with NASA scientists who are working to create aboveground forest biomass maps. These maps, derived from combining remote sensing and ground plots, aim to be more accurate than current inventory approaches when applied at local and regional scales. Meeting participants agreed that users of biomass information will look to the CMS effort not only to provide basic data for carbon or biomass measurements but also to provide data to help serve a broad range of goals, such as forest watershed management for water quality, habitat management for biodiversity and ecosystem services, and potential use for developing payments for ecosystem service projects. Participants also reminded the CMS group that potential users include not only public sector agencies and nongovernmental organizations but also the private sector because much forest acreage in the United States is privately held and needs data for forest management. Additional key outcomes identified by meeting participants include the following: (1) Priority should be given to building into the biomass product ease of use and low costs (including costs of hardware, software, and analysis requirements), (2) CMS products should also be relevant to other biomass measures for forest watershed management, habitat protection for biodiversity, and assessment of markets for ecosystem services, (3) CMS leadership should engage with the Subsidiary Body for Scientific and Technological Advice of the United Nations Framework Convention on Climate Change as they establish measuring, reporting, and verification standards, and (4) CMS leadership should continue to keep sister agencies and other organizations informed as CMS develops, particularly via the agencies active in the U.S. Global Change Research Program Carbon Cycle Interagency Working Group (U.S. Geological Survey, U.S. Department of Agriculture, and National Oceanic and Atmospheric Administration) and nongovernmental organizations.

Forest↗

CropEx Web-Based Agricultural Monitoring and Decision Support

CropEx is a Web-based agricultural Decision Support System (DSS) that monitors changes in crop health over time. It is designed to be used by a wide range of both public and private organizations, including individual producers and regional government offices with a vested interest in tracking vegetation health. The database and data management system automatically retrieve and ingest data for the area of interest. Another stores results of the processing and supports the DSS. The processing engine will allow server-side analysis of imagery with support for image sub-setting and a set of core raster operations for image classification, creation of vegetation indices, and change detection. The system includes the Web-based (CropEx) interface, data ingestion system, server-side processing engine, and a database processing engine. It contains a Web-based interface that has multi-tiered security profiles for multiple users. The interface provides the ability to identify areas of interest to specific users, user profiles, and methods of processing and data types for selected or created areas of interest. A compilation of programs is used to ingest available data into the system, classify that data, profile that data for quality, and make data available for the processing engine immediately upon the data s availability to the system (near real time). The processing engine consists of methods and algorithms used to process the data in a real-time fashion without copying, storing, or moving the raw data. The engine makes results available to the database processing engine for storage and further manipulation. The database processing engine ingests data from the image processing engine, distills those results into numerical indices, and stores each index for an area of interest. This process happens each time new data is ingested and processed for the area of interest, and upon subsequent database entries, the database processing engine qualifies each value for each area of interest and conducts a logical processing of results indicating when and where thresholds are exceeded. Reports are provided at regular, operator-determined intervals that include variances from thresholds and links to view raw data for verification, if necessary. The technology and method of development allow the code base to easily be modified for varied use in the real-time and near-real-time processing environments. In addition, the final product will be demonstrated as a means for rapid draft assessment of imagery.

Harvey. Craig↗

Validation & Verification of Electrical Components B2 Test Facility

The research focus of this project is to assist in the closure of Measurement, Monitoring and Control System (MMCS) and other electrical requirements in support of the B2 Space Launch System (SLS) Core Stage Green Run Test Project. Alongside this goal I am to understand project management tools to analyze and control activities/tasks associated with those items. The project I am working on will assist electrical engineers in developing and or identifying closure rationale for the MMCS and electrical requirements. Also as serving the role of a training project manager, I am to develop and maintain a method for tracking progress with estimate completion dates specifically identifying those items during this performance window. The methods I used in order to perform the research consisted of worddocuments, excel sheets, and pdf documents needed for review. For example, documents consisted of: a SLS Core Stage Green Run Facility Requirement Document (FRD) identifying the SSC MMCS and electrical requirements, a Stage Controller to SSC Interface Control Document (ICD) identifying the SSC requirements, and the B2 SLS Core Stage Green Run Test project System Requirements Document (SRD) which identifies the MMCS and electrical requirements. The files were sent to me by both mentors, Mr. Barry Robinson and Ms. Dawn Davis. Overall, the review process for the word documents and excel spreadsheets proved to be successful. The data for the electrical components were accurate and were consistent with the original recorded data. However, the consistency with the pdf documents did not follow up all the way. Attention to this mistake was made and further revisions were done in order for the data to agree with each other. Furthermore, an itinerary was designed using Microsoft Outlook in order to track progress with estimated completion dates. This project contributes to NASA/Center Missions and Goals through the Waterfall Model. The Waterfall Model is a linear system used for engineering design. In the Waterfall Model, the fourth step is Verification and Validation. This involves installation, testing, and debugging of the B2 SLS Core Stage electrical components. For the SLS Core Stage Green Run Test Project, each requirement contained in this approved requirements set will have at least one Verification Item (VI) assigned to it. During the design phase, VIs will mostly consist of Analysis or Inspection types. Design phase VIs and closure information will be documented in Dynamics Data Management System (DDMS) in the form of analysis reports and design documentation.

Bastian, Tyler↗

Wilson Corners SWMU 001 2015 Annual Long Term Monitoring Report Kennedy Space Center, Florida

This document presents the findings of the 2015 Long Term Monitoring (LTM) that was completed at the Wilson Corners site, located at the National Aeronautics and Space Administration John F. Kennedy Space Center, Florida. The objectives of the 2015 LTM event were to evaluate the groundwater flow direction and gradient, to monitor the vertical and horizontal extent of the volatile organic compounds (VOCs; including the upgradient and sidegradient extents, which are monitored every five years), and to monitor select locations internal to the dissolved groundwater plume. The 2015 LTM event included several upgradient and sidegradient monitoring wells that are not sampled annually to verify the extent of VOCs in this portion of the site. The December 2015 LTM groundwater sampling event included, depth to groundwater measurements, 40 VOC samples collected using passive diffusion bags, and one VOC sample collected using low-flow techniques. Additionally, monitoring well MW0052DD was overdrilled and abandoned using rotasonic drilling techniques. The following conclusions can be made based on the 2015 LTM results: groundwater flow is generally to the west with northwest and southwest flow components from the water table to approximately 55 feet below land surface (ft BLS); peripheral monitoring wells generally delineate VOCs to groundwater cleanup target levels (GCTLs) except for monitoring wells MW0088, MW0090, MW0095, and NPSHMW0039, which had vinyl chloride (VC) concentrations near the GCTL and MW0062, which had trichloroethene (TCE), cis-1,2-dichloroethenen (cDCE), and VC concentrations above natural attenuation default concentrations (NADCs); VOCs in interior downgradient wells generally fluctuate within historic ranges except for monitoring wells in the north-northwest portion of the site, which have increasing VC concentrations indicating potential plume migration and expansion; Historically, the vertical extents of the VOCs were delineated by monitoring wells screened greater than 60 ft BLS (MW0083 through MW0086, and MW0078). The 2015 LTM results indicate that concentrations of daughter product cDCE is greater than the NADC in MW0078 and that cDCE and VC are greater than NADCs in MW0130. TCE was greater than the GCTL in monitoring well MW130 and not detected above method detection limits (9 micrograms per Liter) in monitoring well MW0078. No GCTL exceedances were identified in monitoring wells MW0083 or MW0086; the dissolved plume footprint appears generally stable, though not fully delineated by monitoring well data in the northeast portion of the site; and 2015 LTM results generally support the existing Conceptual Site Model. Geosyntec recommends modifying the LTM program, collecting a verification sample from monitoring well MW0062, and performing a direct push technology instigation in the northnortheastern portion of the site. A cluster of monitoring wells (MW0132 [2 to 12 ft BLS], MW0133 [15 to 25 ft BLS], and MW0134 [29 to 34 ft BLS]) is proposed to delineate impacts in the northnortheast portion of the site. Geosyntec recommends installation of a vertical extent well in the center of the site (Hot Spot 2 area) post-remediation implementation.

groundwater↗

KSC Headquarters Building Area SWMU 104 Soil Interim Measure Report for LOC 2D and LOC 2E Kennedy Space Center, Florida

This Interim Measure (IM) Report for Location of Concern (LOC) 2D and LOC 2E summarizes the activities associated with implementation of an IM to address soil and concrete contamination at the Kennedy Space Center (KSC) Headquarters Building Area (KHQA) located at KSC, Florida. KHQA has been designated Solid Waste Management Unit (SWMU) 104 under KSC’s Resource Conservation and Recovery Act Corrective Action Program. The IM consisted of excavating/removing residual polychlorinated biphenyl (PCB) contamination in soil and concrete from two separate areas, LOC 2D and LOC 2E, which were associated with electrical transformer locations. IM activities were conducted in accordance with the Interim Measure Work Plan (IMWP), Revision 1, for KHQA dated June 2018, which was approved by the Florida Department of Environmental Protection in a correspondence letter dated April 2016 and the United States Environmental Protection Agency in a correspondence letter dated August 2018. The objective of the IM was to remove all remaining contaminated media with total PCB concentrations greater than the State of Florida Residential Soil Cleanup Target Level (RSCTL) (0.5 milligrams per kilogram [mg/kg]). This cleanup goal meets unrestrictive re-use conditions in Florida, and is below federal regulations for PCB Bulk Remediation Waste Cleanup of 1 mg/kg for high occupancy, unrestricted use areas, as outlined in 40 Code of Federal Regulations (CFR) 761.61(a). The timeline of the IM was coordinated with demolition of the former KSC Headquarters Building (demolished in 2021) in order to safely remove contaminated media after electrical equipment was de-energized and removed from the site. Excavation activities were conducted between January 10, 2022, and February 8, 2022, and included two waste streams for off-site disposal: (1) PCB-remediation waste greater than or equal to 50 mg/kg, and (2) PCB-remediation waste less than 50 mg/kg. A total of approximately 347 cubic yards (478 tons) of PCB-contaminated soil and concrete was initially removed from the LOC 2D and LOC 2E areas, as defined in the IMWP. An additional 4.35 tons of soil and concrete were removed based on verification sampling, which was conducted until the cleanup goal was achieved. The total area of excavation from both LOC 2D and LOC 2E was approximately 5,186 square feet (0.12 acres), and excavation depths ranged from 0.5 to 4.0 feet below land surface Excavated soils and concrete were stockpiled based on waste stream and subsequently transported and disposed of at Waste Connections of Osceola County, LLC – JED Landfill in St. Cloud, Florida (PCBs less than 50 mg/kg) or the Chemical Waste Management Landfill in Emelle, Alabama (PCBs greater than or equal to 50 mg/kg). Following excavation, clean backfill was brought to the site and provided to the Demolition Contractor to complete backfill and grading in conjunction with their final site restoration activities from building demolition. Post-IM groundwater sampling was conducted in May 2022 at three monitoring wells installed in April 2022 to confirm that PCBs did not leach into groundwater. These wells were installed where the highest PCB concentrations were detected at LOC 2D, LOC 2E, and from the Building Perimeter IM (previously completed in 2020). All PCB results in groundwater were non-detect. Volatile organic compounds were also analyzed based on potential past use of solvents in transformers with PCB-dielectric fluids and the potential release of dielectric fluids containing volatile organic compounds, and all results were non-detect. Based on completion of a successful IM at LOC 2D and LOC 2E, as well as previous remedial actions that have addressed other contamination at KHQA (SWMU 104), No Further Action without controls will be recommended for SWMU 104. NASA will submit separate Site Rehabilitation Completion Order request documentation for SWMU 104 to support an NFA without controls recommendation.

PCB↗

Workshop on the Role of Design Assurance in System-Wide Safety’s Safety Demonstrator Series

This report summarizes a three-hour hybrid in-person/online workshop on June 7, 2024 on the topic of design assurance and the Safety Demonstrator Series (SDS), which was held at NASA Ames Research Center. The SDS provides an operational demonstration of, and recommendations for, requirements and standards necessary to monitor, assess, and mitigate risks to assure safety in disaster-oriented operations. Over sixty NASA personnel participated in the workshop. Four main topics were discussed: (1) assurance needs for the Safety Demonstrator Series, (2) assurance and the In-Time Aviation Safety Management System (IASMS), (3) in-time assurance: existing efforts and future opportunities, and (4) demonstrating assurance tools in the Safety Demonstrators. Key takeaways are as follows: 1. Design assurance tools can be used to assure an In-Time Aviation Safety Management System, the systems that comprise it, and other systems or missions. Assurance must consider both systems and components and include the interactions between elements in both a systems/aircraft context and a systems-of-systems/airspace context. 2. Design-time assurance activities can support the identification of monitors needed for operational assurance activities (i.e., the “monitor” function in the monitor-assess-mitigate paradigm at the heart of the IASMS concept). 3. A major opportunity for design-time assurance tools to contribute to the IASMS concept is to support rapid re-validation of systems. This will be particularly important for (1) supporting novel operations in the IASMS, where operational data may disprove design-time assumptions (motivating re-analysis of system safety) and (2) adapting technologies (e.g., AI/ML for autonomous operations) to new operational domains, where there may be new or different safety considerations not included in the initial scope of operations. 4. There are several design assurance tools under development in the System-Wide Safety project that can support assurance of Services, Functions, and Capabilities (SFCs) in the Safety Demonstrators. Transitioning these tools from one-off research projects into a functioning part of IASMS assurance will require closer integration between these tools. 5. It is not clear whether the role of design assurance tools is primarily as a part of IASMS architecture or as an external check on IASMS. The workshop consisted of four discussion topics initiated via four lightning talks by System-Wide Safety researchers. Discussions utilized Mural to engage both in-person and online participants in the hybrid format. Polls and surveys were also utilized to gather participant input. The workshop closed with a reflection activity for participants, as well as new ideas for collaboration and coordination of ongoing System-Wide Safety research.

design assurance↗