Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “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
NASA NTRS1973

Study of data collection platform concepts: Data collection system user requirements

The overall purpose of the survey was to provide real world data on user requirements. The intent was to assess data collection system user requirements by questioning actual potential users rather than speculating on requirements. The end results of the survey are baseline requirements models for both a data collection platform and a data collection system. These models were derived from the survey results. The real value of these models lies in the fact that they are based on actual user requirements as delineated in the survey questionnaires. Some users desire data collection platforms of small size and light weight. These sizes and weights are beyond the present state of the art. Also, the survey provided a wealth of information on the nature and constituency of the data collection user community as well as information on user applications for data collection systems. Finally, the data sheds light on the generalized platform concept. That is, the diversity of user requirements shown in the data indicates the difficulty that can be anticipated in attempting to implement such a concept.

Source record↗
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 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↗
DOE OSTI2026

DOE EV Data Collection - Maintenance Data

Maintenance data includes information on maintenance performed on the electric vehicles, including preventive maintenance, service calls, and availability of the vehicles. The parameters collected, and their definitions, will vary due to the differences in maintenance tracking systems that exist between fleets. Parameter definitions are detailed in the data dictionary, and specific vehicle information is available in the vehicle attributes table. Vehicle ID can be used as a key between maintenance 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 OSTI2026

DOE EV Data Collection - Facility Data

Facility data includes information on electricity consumption by larger-scale infrastructure, including buildings, solar arrays, and energy storage systems. Parameter definitions can be found in the data dictionary. If a connection between specific vehicle information and facility data exists, it will be available in the vehicle attributes table. 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↗
NASA NTRS1988

Wide band data collection system

The Incorporated Research Institutes for Seismology (IRIS) approached NASA Headquarters in 1986 about the need to collect data daily from seismic stations around the world as part of the Earth Observing System (EOS) mission. A typical IRIS Seismic Station generates 16 Megabytes of data per day when there is seismic activity. The Preliminary Design Parameters of the Wide Band Data Collection System are summarized.

Turkiewicz, J. M.↗
DOE OSTI2024

Identifying Controlling Variables for Mercury Vapors in Alpha-4 at Y-12: Two Year Data Collection Update

Multiple sensor packages were deployed at Alpha-4 by SRNL, in collaboration with United Cleanup Oak Ridge LLC (UCOR), to monitor mercury vapor concentrations and meteorological parameters. These sensors collected data, inside and outside of the legacy-use facility, for approximately two years. Though data gaps still exist, particularly in colder months, several controlling variables were identified that govern mercury vapor concentrations within Alpha-4. Temperature, barometric pressure gradients, humidity, and wind speed have been identified as controlling variables. A strong positive correlation was seen between mercury vapor concentrations and temperature which generally followed diurnal fluctuations. Temperatures below approximately 10 degrees Celsius did not show any spikes above the PEL, indicating more work can be performed at any time during the winter months – more data should be collected to confirm consistency in this finding. Additionally, spikes in mercury vapor concentrations above that of the permissible exposure limit (PEL; 100 µg/m 3 ) occurred primarily in late afternoon or evening/overnight hours (between 3 PM and 6 AM), which suggests D&D operations might be best scheduled during morning or daytime hours prior to the late afternoon. However, a limited number of spikes did occur outside of the identified window, although this may be attributed to disturbances in air flow and mercury vapor release from work activities performed inside of the Alpha-4 building. The analysis conducted allows for a strong predictive capability for estimating mercury vapor concentrations based upon accurate meteorological parameters. Still, additional data collection, particularly in the winter months, could help to strengthen the predictive power and validate the identified data trends. Further, increased temporal resolution could also help to better characterize the incipient stages of the increases and decreases in the mercury vapor concentration. Continued monitoring support by SRNL at Y-12 is underway at Alpha-4 to further close remaining data gaps and support deactivation and decommissioning work. Within a collaborative effort with UCOR, the SRNL team is collecting mercury vapor data to study the efficacy of a novel mercury suppressant, FerroBlack® which was recently deployed at Alpha-4. In addition, modifications to the current monitoring setup to increase measurement resolution is also being investigated.

54 ENVIRONMENTAL SCIENCES↗
NASA NTRS1993

Use of infrared telemetry as part of a nonintrusive inflight data collection system to collect human factors data

The objective of this paper is to present a methodology and rationale for development of a Nonintrusive Inflight Data Collection System (NIDCS) to collect Human Factors (HF) data during a space mission. These data will enable the research team to identify and resolve issues. This paper will present the background and history of the NIDCS, the methodology and techniques employed versus those in current use on Earth, initial results of the effort--including a brief description of the equipment, and, finally, a discussion of the scientific importance and possible future applications of this system elsewhere. The schema for the NIDCS includes a collection of three types of data: behavioral, physiological, and biomechanical. These will be collected using videotape of crew members' activities, bioelectric signal measurement, and measurement of kinematics and kinetics, respectively. This paper will focus on the second type of data, physiological activity as determined by changes in bioelectric potentials as crew members perform daily assignments.

Micocci, Angelo↗
NASA NTRS1992

Data collection procedures for the Software Engineering Laboratory (SEL) database

This document is a guidebook to collecting software engineering data on software development and maintenance efforts, as practiced in the Software Engineering Laboratory (SEL). It supersedes the document entitled Data Collection Procedures for the Rehosted SEL Database, number SEL-87-008 in the SEL series, which was published in October 1987. It presents procedures to be followed on software development and maintenance projects in the Flight Dynamics Division (FDD) of Goddard Space Flight Center (GSFC) for collecting data in support of SEL software engineering research activities. These procedures include detailed instructions for the completion and submission of SEL data collection forms.

Heller, Gerard↗
NASA NTRS1973

Environmental monitoring via the ERTS-1 Data Collection System.

The Data Collection System (DCS) provides users with near real-time environmental data from earth-based sensors relayed via the Earth Resources Technology Satellite (ERTS-1) to Goddard Space Flight Center. Data is received at Goddard at least twice per day from each sensor and distributed to users (who operate the sensors and transmitters) by mail and teletype. Data collection platforms are discussed together with DCS equipment and the ground receiving and processing equipment.

Painter, J. E.↗
NASA NTRS1988

Transmitter data collection using Ada

A data collection system installed on the 400 kilowatt X-band transmitter of the Goldstone Solar System Radar is described. The data collection system is built around the off-the-shelf IEEE 488 instrumentation, linked with fiber optics, controlled by an inexpensive computer, and uses software written in the Ada language. The speed and accuracy of the system is discussed, along with programming techniques used for both data collection and reduction.

Conroy, B. L.↗
NASA NTRS1974

An evaluation of the ERTS data collection system as a potential operational tool

The Earth Resources Technology Satellite Data Collection System has been shown to be, from the users vantage point, a reliable and simple system for collecting data from U.S. Geological Survey operational field instrumentation. It is technically feasible to expand the ERTS system into an operational polar-orbiting data collection system to gather data from the Geological Survey's Hydrologic Data Network. This could permit more efficient internal management of the Network, and could enable the Geological Survey to make data available to cooperating agencies in near-real time. The Geological Survey is conducting an analysis of the costs and benefits of satellite data-relay systems.

Paulson, R. W.↗
NASA NTRS1987

Advanced Data Collection for Inventory Management

Bar-coding, radio-frequency, and voice-operated systems selected. Report discusses study of state-of-the-art in automated collection of data for management of large inventories. Study included comprehensive search of literature on data collection and inventory management, visits to existing automated inventory systems, and tours of selected supply and transportation facilities at Kennedy Space Center. Information collected analyzed in view of needs of conceptual inventory-management systems for Kennedy Space Center and for manned space station and other future space projects.

Opresko, G. A.↗
NASA NTRS1990

Integrating performance data collection, analysis, and visualization

An integrated data collection, analysis, and data visualization environment is described for a specific parallel system - the Intel iPSC/2 hypercube. The data collection components of the environment encompass software event tracing at the operating system with a program level and a hardware-based performance monitoring system used to capture software events. A visualization system based on the X-window environment permits dynamic display and reduction of performance data. A performance data collection, analysis, and visualization environment makes it possible to access the effects of architectural and system software variations.

Malony, Allen D.↗
NASA NTRS1969

Mossbauer-effect data-collection system

Automated data collection system which uses a small, general-purpose digital computer provides data acquisition from, and minor control of, four Mossbauer-effect experiments. This system is economical with no loss of versatility to the experimenter and is useful in handling large volumes of data from research experiments.

Aschenbrenner, R. A.↗
NASA NTRS1975

ERTS-1 data collection system: Status and performance

The Data Collection System flown on the first Earth Resources Technology Satellite (ERTS-1) relays earth resources data from remotely located in-situ sensors to Goddard Space Flight Center. Data is received at Goddard at least twice each day from every sensor installation and is distributed to users (who operate the sensors and transmitters) by mail and teletype. The system consists of a data formatting and transmitting unit, called the Data Collection Platform (DCP), a receiver and a retransmitter aboard ERTS-1; and receiving, demodulating and decoding equipment located at the Goldstone, California and Goddard data acquisition stations. Data is transmitted from the data acquisition stations to the ERTS Control Center at Goddard, then to the NASA (ERTS) Data Processing Facility (NDPF) where it is processed and distributed to users. Experience to date indicates that the design of the ERTS-1 Data Collection System is adequate for operational use for 50% of the users and, with minor modifications, could meet the requirements of 75%. Some users will have to augment the system by other data collection techniques to meet their operational requirements.

Painter, J. E.↗
NASA NTRS1981

Guide to data collection

Guidelines and recommendations are presented for the collection of software development data. Motivation and planning for, and implementation and management of, a data collection effort are discussed. Topics covered include types, sources, and availability of data; methods and costs of data collection; types of analyses supported; and warnings and suggestions based on software engineering laboratory (SEL) experiences. This document is intended as a practical guide for software managers and engineers, abstracted and generalized from 5 years of SEL data collection.

Source record↗