The Vapor Intrusion EDD Group consists of data tables for inventorying buildings and structures, cataloging factors that impact air quality within structures and for the location, sample and chemistry results for soil vapor, indoor air and ambient outdoor air samples collected. The Vapor Intrusion EDD consists of three data tables (Table 3.3): VI_BuildingInspection_v1 VI_TaskParameters_v1 VI_Samples_v1 Table 3.3: General Information on the Vapor Intrusion Group EDD Sections Completed Submission Table Name Description Data Requirements By Frequency Contains data MTDEQ requires the fields listed that below be populated: inventories building_code– For each buildings and building, this building code structures, must be unique and all cataloging Data upper case. factors that Providers Once per building_name– This can VI_BuildingInspection_v1 impact air Vapor building be a more descriptive quality within Intrusion inspection name for the building. structures. Team inspection_date The – Replaced the date the building inspection legacy was conducted. occupied task_code The unique – building identifier for the task. questionnaire. Contains data Anytime specific to the structure MTDEQ requires the fields listed VI Task, for Data sampling below be populated: example Providers data are The unique task_code – VI_TaskParameters_v1 start/end Vapor collected identifier for the task. weather, Intrusion and parameter_code The – start/end Team provided to task parameter. atmospheric MTDEQ pressure, etc. MTDEQ requires the fields listed below be populated: data_provider - The unique identifier of the Contains company or agency sample Anytime submitting the data. information structure Data sys_sample_code - The collected from sampling Providers unique identifier of the Ambient Air, data are VI_Samples_v1 sample. Each sample at a Indoor Air, collected Intrusion facility must have a unique and Subslab and Team including spikes and Soil Vapor provided to duplicates. You have Sampling MTDEQ considerable flexibility in forms the methods used to derive and assign unique sample identifiers, but uniqueness throughout the database is
The Vapor Intrusion EDD Group consists of data tables for inventorying buildings and structures, cataloging factors that impact air quality within structures and for the location, sample and chemistry results for soil vapor, indoor air and ambient outdoor air samples collected. The Vapor Intrusion EDD consists of three data tables (Table 3.3): VI_BuildingInspection_v1 VI_TaskParameters_v1 VI_Samples_v1 Table 3.3: General Information on the Vapor Intrusion Group EDD Sections Table Name Description Completed By Submission Frequency Data Requirements VI_BuildingInspection_v1 Contains data that inventories buildings and structures, cataloging factors that impact air quality within structures. Replaced the legacy occupied building questionnaire. Data Providers Vapor Intrusion Team Once per building inspection MTDEQ requires the fields listed below be populated: building_code– For each building, this building code must be unique and all upper case. building_name– This can be a more descriptive name for the building. inspection_date – The date the building inspection was conducted. task_code – The unique identifier for the task. VI_TaskParameters_v1 Contains data specific to the VI Task, for example start/end weather, start/end atmospheric pressure, etc. Data Providers Vapor Intrusion Team Anytime structure sampling data are collected and provided to MTDEQ MTDEQ requires the fields listed below be populated: task_code – The unique identifier for the task. parameter_code – The task parameter. VI_Samples_v1 Contains sample information collected from Ambient Air, Indoor Air, and Subslab Soil Vapor Sampling forms Data Providers Intrusion Team Anytime structure sampling data are collected and provided to MTDEQ MTDEQ requires the fields listed below be populated: data_provider - The unique identifier of the company or agency submitting the data. sys_sample_code - The unique identifier of the sample. Each sample at a facility must have a unique including spikes and duplicates. You have considerable flexibility in the methods used to derive and assign unique sample identifiers, but uniqueness throughout the database is
e-TREADS_EDD_Manual.docx