Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “vehicle data collection”

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 19 records
All sourcesNASA NTRSDOE OSTI
DOE OSTI2026

DOE EV Data Collection - Vehicle Data

Vehicle data consist of electric vehicle performance data collected directly from the vehicle during standard operations. Data were collected using onboard data loggers that were either installed by the project team or preinstalled by the original equipment manufacturer. Data recorded by the data loggers were made accessible via an online web portal or an application programming interface. Different data loggers were used (HEM, ViriCiti, and Geotab), and the method for each vehicle is defined in the vehicle attributes file. Some systems collected data on a “trip-level” basis, in which each row of a table represents a single trip (the period between a key-on and key-off event), whereas other data were collected on a per-day basis, in which each row represents a single day of operation. Data were collected over a range of data collection periods, depending on the project. Data have been anonymized by removing information or decreasing information resolution as necessary so that fleets are not identifiable. Due to the wide range of vehicle types represented and variation in data collection, data parameters and frequencies differ between vehicles and fleets The **Performance Data Daily/Trip Data Dictionaries** contain definitions for each available parameter associated with a vehicle’s operations, aggregated at either a daily or trip level. The parameters available will vary from vehicle to vehicle, but every possible parameter will be defined. The **Vehicle Attributes Data Dictionary** contains definitions for each available parameter associated with a vehicle’s physical and functional attributes and fleet context. The **Vehicle Attributes** table contains specific vehicle characteristics, coded to an anonymous Vehicle ID. This Vehicle ID can be used as a key between vehicle data and vehicle attribute tables. The **Vehicle Data** tables contain the data from each vehicle’s operations, aggregated at either a daily or trip level, coded to an anonymous Vehicle ID. This Vehicle ID can be used as a key between vehicle data and vehicle attribute tables. Data is being uploaded quarterly through 2023 and subject to change until the conclusion of the project.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗
DOE OSTI2021

Libpanda: A High Performance Library for Vehicle Data Collection

Cyber-Physical Systems (CPS) generally involve time-critical components due to physical dynamics, therefore necessitating high-performance subsystems. This is also true in data collection scenarios to infer physical phenomena. This paper covers Libpanda as an example of a component that has been designed to address performance issues in CPS implementations. Libpanda is a C++ library that interfaces software with a Comma.ai Panda device. Pandas are used for installation in modern vehicles to read the vehicle CAN bus, providing rich sensor data and limited vehicle control through message injection. The motivation to design lib-panda stems from the lack of performance in Python-based code that runs on inexpensive hardware like a Raspberry Pi. In such situations, Python code would result in utilizing 92% CPU while also dropping around 40% of the CAN packet due to bottlenecks. Without using different tools, inconsistent data collection means a loss of time-based vehicle state interpretation. Libpanda addresses these issues through implementation in a different language and implementation of different design paradigms involving asynchronous calls and multithreading. The Panda also features a GPS module that allows multiple instances to synchronize clocks for large-scale data collection scenarios. Libpanda has been designed with time-synchronization in mind to aid in the measurement of inter-vehicle dynamics. The performance improvements of libpanda have resulted in it becoming an important component in automotive dynamics research that requires a higher technical performance in large-scale experiments.

Bunting, Matthew↗
DOE OSTI2020

FAST: Continuing the Focus on Data Quality

This presentation provides an overview of fiscal year 2019 federal motor vehicle fleet data, collected at the individual vehicle level during the fall of 2019, how the the collecting project has reviewed that information for potential quality issues, how the quality of this year's data submission compare to the prior year, and recommendations for federal agencies in their efforts to continue to improve the quality of their submissions. This presentation will be given at the January 2020 FedFleet training event, hosted by the US General Services Administration in Washington, DC. The information is collected through the Federal Automotive Statistical Tool (FAST) project. FAST is a Web-based information system managed by the US Department of Energy, the US General Services Administration, and the Energy Information Administration. FAST is used to collect information about the fleet of motor vehicles used and managed by the Federal government. FAST is developed and maintained by DOE's Idaho National Laboratory (INL).

99 GENERAL AND MISCELLANEOUS↗
DOE OSTI2021

FedFleet 2021: Federal Automotive Statistical Tool - Federal Vehicle Fleet Data Collection

This presentation presents a brief overview of the collection of information about the US government's fleet of motor vehicles using the Federal Automotive Statistical Tool (FAST), discusses the makeup and operation of the vehicle fleet during FY 2020, discusses challenges associated with quality of the submitted data, and touches on future aspects of fleet data collection and reporting. FAST is a web-based information system sponsored by GSA's Office of Government-wide Policy and DOE's Federal Energy Management Program to collect information about the US federal government's fleet of motor vehicles; FAST is developed, maintained, and supported by DOE's Idaho National Laboratory (INL).

99 GENERAL AND MISCELLANEOUS↗
NASA NTRS2023

A Remote Vehicle Operations Center’s Role in Collecting Human Factors Data

The National Aeronautics and Space Administration is supporting research to develop a prototype remote vehicle operations center at Langley Research Center to explore current and future advanced air mobility operations using small unmanned aerial systems vehicles as surrogates for future, larger-scale passenger carrying vehicles. Data collected within the Remote Operations for Autonomous Missions (ROAM) Unmanned Aerial Systems (UAS) Operations Center will be used to explore different roles and responsibilities of remote operators managing multiple autonomous vehicles, with the goal of exploring human-autonomy teaming concepts that enable m:N operations (i.e., m operators managing N vehicles). ROAM has developed into a world-class research, development, and technology (RD&T) environment that can support both the collection of human factors data and the command and control of remote vehicles in beyond visual line of sight conditions. Presented in this paper is an overview of ROAM, with a focus on the design components that support human factors data collection and a review of initial usability results of the facility.

Human factors↗
NASA NTRS2023

A Remote Vehicle Operations Center’s Role in Collecting Human Factors Data

The National Aeronautics and Space Administration is supporting research to develop a prototype remote vehicle operations center at Langley Research Center to explore current and future advanced air mobility operations using small unmanned aerial systems vehicles as surrogates for future, larger-scale passenger carrying vehicles. Data collected within the Remote Operations for Autonomous Missions (ROAM) Unmanned Aerial Systems (UAS) Operations Center will be used to explore different roles and responsibilities of remote operators managing multiple autonomous vehicles, with the goal of exploring human-autonomy teaming concepts that enable m:N operations (i.e., m operators managing N vehicles). ROAM has developed into a world-class research, development, and technology (RD&T) environment that can support both the collection of human factors data and the command and control of remote vehicles in beyond visual line of sight conditions. Presented in this paper is an overview of ROAM, with a focus on the design components that support human factors data collection and a review of initial usability results of the facility.

Human factors↗
DOE OSTI2023

Vehicle Powertrain Simulation Accuracy for Various Drive Cycle Frequencies and Upsampling Techniques

As connected and automated vehicle technologies emerge and proliferate, lower frequency vehicle trajectory data is becoming more widely available. In some cases, entire fleets are streaming position, speed, and telemetry at sample rates of less than 10 seconds. This presents opportunities to apply powertrain simulators such as the National Renewable Energy Laboratory's Future Automotive Systems Technology Simulator to model how advanced powertrain technologies would perform in the real world. However, connected vehicle data tends to be available at lower temporal frequencies than the 1-10 Hz trajectories that have typically been used for powertrain simulation. Higher frequency data, typically used for simulation, is costly to collect and store and therefore is often limited in density and geography. This paper explores the suitability of lower frequency, high availability, connected vehicle data for detailed powertrain simulation. A large data set of 1 Hz trajectories is used to quantify the accuracy loss when simulating energy consumption for conventional, hybrid, and battery electric powertrains using less than 1 Hz data. Techniques to upsample lower frequency drive cycle data in order to increase accuracy are also explored. Median energy consumption errors when simulating energy consumption for a 1/10 Hz trajectory are found to be 3-6% when compared to 1 Hz trajectories. Applying upsampling and interpolation techniques are shown to reduce the simulation errors by roughly 50%. The findings in this work can guide connected vehicle data collection specifications and processing techniques applied when using collected data for powertrain simulation.

ADVANCED PROPULSION SYSTEMS↗
DOE OSTI2020

Impact of transportation network companies on urban congestion: Evidence from large-scale trajectory data

We collect vehicle trajectory data from major transportation network companies (TNCs) in New York City (NYC) in 2017 and 2019, and we use the trajectory data to understand how the growth of TNCs has impacted traffic congestion and emission in urban areas. By mining the large-scale trajectory data and conduct the case study in NYC, we confirm that the rise of TNC is the major contributing factor that makes urban traffic congestion worse. From 2017 to 2019, the number of for-hire vehicles (FHV) has increased by over 48% and served 90% more daily trips. These resulted in an average citywide speed reduction of 22.5% on weekdays, and the average speed in Manhattan decreased from 11.76 km/h in April 2017 to 9.56 km/h in March 2019. The heavier traffic congestion may have led to 136% more NOx, 152% more CO and 157% more HC emission per kilometer traveled by the FHV sector. Our results show that the traffic condition is consistently worse across different times of the day and at different locations in NYC. And we build the connection between the number of available FHVs and the reduction in travel speed between the two years of data and explain how the rise of TNC may impact traffic congestion in terms of moving speed and congestion time. Our findings provide valuable insights for different stakeholders and decision-makers in framing regulation and operation policies towards more effective and sustainable urban mobility.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗
NASA NTRS2019

Operations of the Optical Communications Demonstration for the Orion EM-2 Mission

The GSFC implementation of an Optical Communication System to demonstrate an operational optical communication link for Orion EM-2. It will serve as a base for providing an operational optical communications capability for future Orion missions. GSFC plans to maintain a development path for the optical communication flight terminal to allow commercialization and implementation on future Orion missions. The Orion optical module part of the optical communications flight terminal and its control electronics have a common architecture with the ILLUMA-T optical terminal provided by GSFC for use on the ISS. The plan is to flow data from Orion through the Optical Communication Fight Terminal to the Optical Communication Ground Terminal and reverse. NASA's Orion spacecraft is an exploratory vehicle designed for longer-duration flights beyond the Moon. Following Orion's Exploration Mission-1 (EM-1), during which the spacecraft will travel beyond the Moon, enter a distant retrograde orbit around the Moon and return to Earth unmanned, Exploration Mission-2 (EM-2) will see a crewed spacecraft complete a slightly different flight path. First crewed test flight of the Orion spacecraft, currently targeting a June 30, 2022 launch. The mission involves: One revolution in Low Earth Orbit (LEO) parking orbit to verify basic Orion systems functionality and deploy solar arrays. A single 42-hour Highly Elliptical Orbit (HEO) intermediate checkout orbit allows characterization of the Orion vehicle system performance prior to committing to a cis-lunar flight. Trans Lunar Injection (TLI) burn using Orion Service Module (SM) main engine, which sends Orion on a lunar flyby and free return. Skip reentry at lunar return velocities to splashdown off the coast of San Diego. Total mission duration is approximately 10 days. EM-2 is the first crewed mission of the Orion Spacecraft that crew brings more video up/downloads, file transfers, and real-time chats with family back home and high-rate communications enables live HD streaming for Crew conferences, Public Affairs Office (PAO) events, and significant mission events. Also still collecting vehicle data on numerous Orion subsystems via Development Flight Instrumentation (DFI) allows large data volume returns sooner for DFI and future science payloads, as opposed to waiting for end-of-mission. O2O is a demonstration of operational utility system tested as a Developmental Test Objective (DTO) and not required to meet mission requirements/success/ Flight Test Objectives (FTO). EM-2 architecture is as close to future mission operational architecture as possible.Orion subsystems (video, DFI, etc.) expected to generate ~250 GB of data in the first 24 hours of flight. Total data generated over the mission estimated to be more than 400 GBUsing S-Band alone, Orion limited to ~ 6GB of data downlink per day. Because of this limitation, Orion is planning to limit live video downlinks on EM-1 in order to downlink high priority fileswith 1 hour/day of Optical Communication, Orion could downlink ~6x more data per day (~ 36GB/day).The optical communication system is capable of multiple data rates up to at least 80 Mbps downlink for the transfer of Orion data to Earth while Orion is operating in the lunar vicinity.

Optical Communication↗
NASA NTRS1974

Parameter estimation for terrain modeling from gradient data

This paper developes a method for mathematically modeling terrain surfaces for use on an unmanned Martian vehicle. The data collected by the vehicle consists of terrain height and two directional slopes at each data point. The parameters for the mathematical terrain model are stochastically determined by using least square approximations.-

Shen, C. N.↗
NASA NTRSDate not supplied

An Agile-Like Approach to Hardware Development: The Ejectable Data Recorder (EDR) for Orion's Ascent Abort 2 (AA-2) Test Flight

On July 2, 2019, the Ascent Abort 2 (AA-2) Flight Test Vehicle was launched from Cape Canaveral, with the goal of demonstrating the performance of Orion’s Launch Abort System (LAS) and collecting data from hundreds of sensors throughout the vehicle. The data collected during this test flight is of paramount importance, as it will be used to certify the Orion vehicle for human spaceflight. Originally, the data was to be downlinked via a single string network of antennas on the LAS, with the associated risk of potential data dropouts, as well as loss of data once the LAS was jettisoned. Thus, additional antennas were added onto the crew module (CM) to support data downlink post-LAS jettison, a buffer rebroadcast capability was added to fill in any gaps in data downlink transmissions, and an ejectable data recorder (EDR) subsystem was added to the CM as a redundant measure to collect all the instrumentation data. The EDR subsystem was added to the project about one year after the project commenced, which significantly reduced the available development time when compared with the other subsystems of the AA-2 Test Flight. The project was further accelerated by six months, around the critical design review gate. Due to the schedule compression challenge and the fact that the EDR subsystem was a backup system and not flight critical, the EDR subsystem was further challenged to find a new and more efficient way to develop hardware. Thus, the EDR subsystem experimented with different management and systems engineering processes, team sizes, communication methods, and tools. Some examples are novel uses of SharePoint as a Data-centric Project Management & Systems Engineering environment, a continuous testing approach through the lifecycle, and a Skunkworks approach to managing the team. The EDR subsystem blended Commercial Off The Shelf (COTS) hardware with in-house developed hardware and software to create a novel data retrieval capability. The capability evolved rapidly through a hardware in the loop simulation environment that enabled incremental component updates for not only the EDR subsystem but across the entire Crew Module. This paper will present an overview of how the EDR subsystem was managed and compare it to an Agile approach to managing projects. The paper will further provide a recommended approach to future Agile-like hardware development that incorporates lessons learned from the EDR experience.

Agile↗
DOE OSTI2023

WiP Abstract: Edge-Based Privacy of Naturalistic Driving Data Collection

Collecting large driving datasets is important for data-driven transportation research and studied in naturalistic driving [3]. Due to the standard implementation of a Controller Area Network (CAN) bus for a vehicle’s inter-module communication, many off-the-shelf devices can easily transform a vehicle into a rich data collection utility [2]. Vehicles with Adaptive Cruise Control (ACC) are an example of a feature resulting in emergent traffic behavior when scaled [4]. While these utilities were designed with particular data use cases, data may be publicly shared to benefit other researchers through online tools like CyVerse [1]. However, such data should only be shared when any private information is removed. This private information may exist as a set of GPS coordinates, since the start and end points of a trip may designate a driver’s place of residence or work. When considering larger continuously-collected data sets with a focus on naturalistic driving, many drivers are needed to make data collection feasible. Removal of private information becomes much more of a challenge since every driver may uniquely define their geographic privacy. This project aims to build upon the foundation of libpanda [2] by adding features of edge-based data privacy enforcement. In it’s current form, libpanda uses a GPS in conjunction with a CAN interface to record data. Libpanda feature s a set of startup and shutdown scripts to perform automatic data collection and upload. With additional support hardware on a Raspberry Pi, the Pi can maintain power on vehicle shutdown to automatically upload data before shutdown.

Bunting, Matt↗
NASA NTRS2016

Aerodynamic Flight-Test Results for the Adaptive Compliant Trailing Edge

The aerodynamic effects of compliant flaps installed onto a modified Gulfstream III airplane were investigated. Analyses were performed prior to flight to predict the aerodynamic effects of the flap installation. Flight tests were conducted to gather both structural and aerodynamic data. The airplane was instrumented to collect vehicle aerodynamic data and wing pressure data. A leading-edge stagnation detection system was also installed. The data from these flights were analyzed and compared with predictions. The predictive tools compared well with flight data for small flap deflections, but differences between predictions and flight estimates were greater at larger deflections. This paper describes the methods used to examine the aerodynamics data from the flight tests and provides a discussion of the flight-test results in the areas of vehicle aerodynamics, wing sectional pressure coefficient profiles, and air data.

aerodynamics↗
DOE OSTI2026

2015-2017 California Vehicle Survey

The 2015-2017 California Vehicle Survey of residential and commercial light-duty vehicle owners in California assessed consumer preferences for vehicles and included a targeted sample of plug-in electric vehicle (PEV) owners. Resource Systems Group conducted the survey on behalf of the California Energy Commission. In addition to economic and demographic data, the survey integrated light-duty vehicle holding and use information with vehicle choice data collected via the stated preferences survey's set of eight vehicle and fuel type choice exercises. The PEV owner survey participants provided additional data on charging behavior, electricity rates, and their main motivations for purchasing PEVs.

1Hz data↗
DOE OSTI2026

FleetREDI Insight: Beverage Delivery in New York City

Capturing real-world data is critical to improving efficiency and supporting technology advancements in commercial vehicles. FleetREDI’s insights provide detailed duty cycle information and highlight unique aspects of the given dataset. Each insight delivers a quick look at the collected data by summarizing the operation and identifying key findings of the initial analysis. This FleetREDI insight explores beverage delivery tractors operating in New York City. Last-mile beverage delivery supports local bars and restaurants throughout Manhattan and the broader New York City area. Manhattan Beer Distributors is a beverage delivery company operating in Manhattan and the Bronx. Logging devices were installed in 17 vehicles, and operational data were collected between August and October 2022. Two types of vehicles were included in data collection: 7 tractors and 10 bay trucks. Using NLR’s FleetREDI data platform, this dataset provides a summary of daily operation to help understand duty cycle characteristics. This includes daily distance, fuel use, and estimated engine-produced energy consumption for 17 bay trucks and tractors that operated more than 7,500 miles in slow-speed urban operation. ![FleetREDI beverage delivery](FleetREDI-beverage-delivery-nyc.jpg)

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗
DOE OSTI2020

Evaluating Energy Efficiency Opportunities from Connected and Automated Vehicle Deployments Coupled with Shared Mobility in California

Connected and Automated Vehicles (CAVs) can be considered to be a disruptive transportation technology, with the potential to significantly improve overall transportation system efficiency; however, CAVs may increase induce vehicle miles traveled (VMT) and bring on greater energy consumption. Further, shared mobility is another disruptive transportation event that is reshaping our travel patterns. The primary goal of this project was to extensively collect data from vehicles and associated infrastructure equipped with CAV technologies from both real-world experiments and simulation studies mainly deployed in California, and develop a comprehensive framework for evaluating energy efficiency opportunities from large-scale (e.g., statewide) introduction of CAVs and a wide deployment of shared mobility systems in a variety of scenarios. To quantify the combined impact of CAV and shared mobility on travel behavior, traffic performance, and energy efficiency, a unique mesoscopic simulation-based model was developed for mobility and energy efficiency evaluation considering these disruptive transportation technologies. As a complement to existing studies on nationwide evaluation of CAVs’ energy impacts, this project was focused on data collection efforts and CAV applications under congested traffic environments that are frequently experienced on a massive scale across the major metropolitan areas in California. Extensive real-world data collection supplemented with simulation studies were conducted to cover a variety of CAV and shared mobility scenarios, particularly on scenarios less-explored in the existing research. Another key component of this project was to consider the interaction between different CAV technologies and shared mobility models, and the compound effect on energy efficiency. A comprehensive modeling suite was developed to quantify the impact of new mobility technologies on travel behavior and traffic performance. The developed modeling framework includes an energy intensity module, mode choice module and activity generation module that are integrated into an agent-based BEAM simulation platform to perform impact analysis based on a variety of scenarios. In addition, the RouteE model has been upgraded to incorporate the impact of CAVs on traffic flow, VMT and energy intensity, using micro-simulation data collected from both freeways and urban arterials. A novel fundamental influencing factor (FIF) mode choice model was developed to link CAV and shared mobility components with travel behaviors, and adapted into the BEAM-centered model framework. A statewide energy inventory was constructed under various CAV technology deployment scenarios by incorporating datasets and models for predicting vehicle market share and vehicle usage, which are tightly associated with the penetration of shared mobility systems. Based applying this modeling suite to a calibrated network in Riverside California, it was found that cooperative automated driving in general will improve mobility, but automated vehicles, even when deployed in a shared autonomous fleet, will likely bring an increase of VMT (up to 36%) due to mode shifts and deadheading. Ride-hailing vehicles typically have better energy efficiency and a higher share of electric vehicles, which helps offset the negative impact from VMT increases when estimating the system-level energy consumption. In general, simulation results show a 6% increase in energy consumption for the scenarios with an increasing shift to ride-hailing modes. The statewide analysis based on the National Household Travel Survey (NHTS) sample data is consistent with the findings from the Riverside network and validate the developed clustering-prediction modeling methodology. The outcomes from this project will help close the knowledge gap on recognizing the potential performance and energy impacts of a broad deployment of CAV and shared mobility technologies across a wide range of roadway infrastructure with varying levels of congestion. Results from this project: 1) will support policymakers in steering CAV development and deployment towards an energy favorable direction; 2) reduce uncertainties in estimating energy saving opportunities from new mobility technologies and services; 3) increase the confidence of CAV technology investors both on the infrastructure side (i.e., transportation agencies) and on the vehicle side (i.e., OEMs); and 4) expedite the deployment of energy-efficient CAV and shared mobility applications.

33 ADVANCED PROPULSION SYSTEMS↗
DOE OSTI2026

DOE EV Data Collection - Charging Data

Charging data are collected from one of three sources, each with varying levels of additional information. These sources, in approximate order from most to least additional information, are: • The electric vehicle supply equipment (charger) • Onboard the vehicle itself • From a utility submeter. Many chargers provide software that allows for the collection and reporting of charging session data. If unavailable, data may be recorded by the charging vehicle’s onboard systems. If neither of these options is available, data can be acquired from utility submeters that simply track the energy flowing to one or more chargers. Data collected directly from the electric vehicle supply equipment (EVSE) are typically the most accurate and highest frequency. However, it is not always possible to discern which exact vehicle is being charged during any one session. EVSE-side data can be identified where a single charger ID but a range of vehicle IDs are present (e.g., CH001, EV001-EV005). Data collected from the vehicle’s onboard systems usually does not provide information on which exact charger is being used. Vehicle-side data can be identified where a single Vehicle ID but a range of Charger IDs are present (e.g., EV001, CH001-CH005). Data collected from utility submeters provide no information on which specific vehicle is charging or which specific charger is in use. Submeter data can be identified where multiple Vehicle IDs and multiple Charger IDs are present, but only a single Fleet ID is present (e.g., EV001-EV005, CH001-CH005, Fleet01). The **Charge Data Daily/Session Dictionaries** contains definitions for each available parameter collected as part of an individual charging session, aggregated at either a daily or session level. The parameters available will vary between vehicles and chargers. The **Charger Attributes** table contains specific charger characteristics, coded to at least one anonymous Charger ID and linked to either a single or a range of Vehicle IDs. Vehicle ID can be used as a key between charging data and vehicle attribute tables. The **Charger Attributes Data Dictionary** contains definitions for each available parameter collected on the physical and operational characteristics of the charging hardware itself. The **Vehicle Attributes Data Dictionary** contains definitions for each available parameter associated with a vehicle’s physical and functional attributes and fleet context. The **Vehicle Attributes** table contains specific vehicle characteristics, coded to an anonymous Vehicle ID. This Vehicle ID can be used as a key between vehicle data and vehicle attribute tables, and in cases where charging data are supplied, links a vehicle with the charger(s) that supplied it power. The **Charging Data** tables contain the data from each charger’s operations, coded to at least one anonymous Charger ID and linked to either a single or a range of Vehicle IDs. Vehicle ID can be used as a key between charging data and vehicle attribute tables. Data is being uploaded quarterly through 2023 and subject to change until the conclusion of the project.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗
NASA NTRSDate not supplied

Continued Environmental Microbiology Monitoring of the International Space Station (ISS) Veggie Unit Used for In-Flight, Crop-Based Food Systems

Crewmembers live and work in a closed environment that is monitored to ensure their health and safety. To ensure occupants’ health and safety during their spaceflight residency, Environmental Health System (EHS) microbial samples including air, surface, and water, are collected, enumerated, and analyzed quarterly to monitor on-board system contamination and potential risks to crew health. Quarterly monitoring of the microorganisms in the ISS environment supports crew safety and contributes to a large set of microbial concentration and diversity data. Based upon data historically collected over the years, in-flight microbial requirements have been established to maintain the health and safety of the spacecraft environment. This study leverages quarterly operational Environmental Health System (EHS) sampling by collecting additional microbial samples from the surface of the station’s Veggie plant production system. Microbial surface samples collected from the Veggie plant production system will yield microbial concentration and diversity that can be compared and analyzed with nominal surface samples from the vehicle. The data collected in this study will aid in the development of requirements for spaceflight-based food production systems. Continued surface sampling of the internal and external surfaces of the Veggie locker, along with collaboration from both Johnson Space Center (JSC) & Kennedy Space Center (KSC) scientists studying the microbiome of the veggie-crop systems, will be implemented as part of the future development of crop-based food system requirements for the ISS and beyond. This presentation will include a review of the study procedures and evaluations of the current results.

Christian Mena↗