<< Click to Display Table of Contents >> Navigation:  EQuIS Library > Formats > DMR Format

Format Name: DMR 

File Name: DMR.zip 

Source: EDP Standalone and EQuIS Professional

Export(s): Yes (see section below)

Enumeration File: DMR-enum.xml

 

 

Description: The DMR format is included with EQuIS Professional and is used to import data related to Discharge Monitoring Reports (DMRs). More information on DMRs can be accessed in the Discharge Monitoring Reports article.  

 

Installation Instructions: The DMR format is included in the installation of EDP Standalone and EQuIS Professional in the \Formats\EarthSoft folder. This format is not included with the installation of EQuIS Enterprise, but can be added and configured to be available in the Enterprise EDP EDD Upload widget. If the format should be configured for EQuIS Enterprise, an administrator will need to define the commit type and other EDP Enterprise elements as defined in the Workflow Widget and Add or Modify Enterprise EDP Formats articles.

 

Overview:

 

The DMR format contains the following sections:  

•Report

•Facility_v2 – Populates the DT_FACILITY table detailing the facility associated with the DMR. This section can be used to modify or add information to an existing facility or to create a new facility in the database.

•Field Results

•FieldSamples_v2 – Details field samples associated with the DMR. This section can be used to modify or add information to field samples in the database.  

•FieldResults_v2 – Details field results associated with the DMR’s field samples. This section can be used to modify or add field result information to field samples that exist in the database.

•Permit Information

•Permit_v2 – Populates the DT_PERMIT table detailing the permit associated with the DMR. This section can be used to modify or add information to an existing permit or to create a new permit in the database.

•Monitor_v2 – Details the monitoring location information for the DMR. For locations whose permit location reporting name is different than the name provided as the sys_loc_code, the monitor number (or monitor name) can be populated in this section. For example, sediment basins may be called Outfall 001 in the DMR permit, while the sys_loc_code may follow a different naming scheme.

•MonitorReport_v2 – Populates the DT_DISCHARGE_REPORT and DT_DISCHARGE_REPORT_PARAMETER tables with general information about the DMR including associated permit, sampling, and analysis details.

•Results

•Sample_v2 – This section is for populating information about the DMR samples that have been sent to the lab for analysis.  

•Result_v2 – This section is for populating the lab sample result details for the DMR.

 

A potential workflow could be:

1.Open the DMR format in EDP.

2.Upload a pre-populated EDD with sections containing the DMR information of interest.

a.It is encouraged to populate the EQuIS database via the "Facility_v2” and “Permit_v2” sections of the format prior to collecting field samples or receiving lab results.

 

 

3.Once that data have been processed and committed into EQuIS, the data can be used in the following ways:

a.Export the data using the DMR format’s EDD exports in EDP.

i.The DMR format has three EDD exports: Field Results EDD, Permit EDD, and Lab Results EDD. Each of these exports can be filtered by attributes such as location, permit, and sample delivery group (SDG). Once the data have been selected, the populated sections of the EDD can be exported to Excel for those who may already have an existing template used for DMR submittals.

b.Export the data using EQuIS DMR reports.

i.EarthSoft can work with clients to prepare reports used for DMRs, including a report for NetDMR submittal and custom eDMR’s for select states. State agencies often refer to how they are submitting their DMR’s and what format they are using for submitting DMR data to the USEPA on their websites. Contact EarthSoft Sales to inquire about custom EQuIS DMR reports.

 

 

 

Limitations/Assumptions: The checks and mappings in any EDD format involve assumptions. The following are assumptions and limitations for the DMR format.

•Test Alternate Key (TAK) fields available in the format: SAMPLE_ID, ANALYTIC_METHOD, ANALYSIS_DATE, FRACTION, TEST_TYPE, and COLUMN_NUMBER. The IDENTIFIER field does not exist in the DMR format. If “Identifier” is toggled in the database test-level key fields, an error message will appear for DT_TEST upon the Create step.

•Prior to importing laboratory samples and results, the FieldSamples_v2 section must be used to populate the DT_SAMPLE table prior to importing laboratory samples using the Sample_v2 section. The Sample_v2 section requires sys_sample_code to exist in the DT_SAMPLE table. An error will occur if sys_sample_code does not correlate with an existing SYS_SAMPLE_CODE in the DT_SAMPLE table.

•The Sample_v2 and Result_v2 sections should be imported together as the sys_sample_code in the Result_v2 section references the sys_sample_code in the Sample_v2 section.

•Ensure that the following values are present in their associated tables:  

•Facility_v2

•The state must exist in the RT_STATE table as STATE_CODE.

•FieldSamples_v2

•The sample_matrix_code must exist in the RT_MATRIX table as MATRIX_CODE.

•The sample_type_code must exist in the RT_SAMPLE_TYPE table as SAMPLE_TYPE_CODE.

•The depth_unit must exist in the RT_UNIT table as UNIT_CODE.

•The sampling_method must exist in the RT_SAMPLE_METHOD table as METHOD_CODE.

•The sys_loc_code must exist in the DT_LOCATION table as SYS_LOC_CODE.

•The sampling_company_code must exist in the RT_COMPANY table as COMPANY_CODE.

•FieldResults_v2

•The data_provider must exist in the RT_COMPANY table as COMPANY_CODE.

•The cas_rn must exist in the RT_ANALYTE table as CAS_RN.

•The result_unit must exist the RT_UNIT table as UNIT_CODE.

•The sample_matrix_code must exist in the RT_MATRIX table as MATRIX_CODE.

•The qualifier must exist in the RT_QUALIFIER table as QUALIFIER.

•The sampling_company_code must exist in the RT_COMPANY table as COMPANY_CODE.

•The sampling_method must exist in the RT_SAMPLE_METHOD table as METHOD_CODE.

•The fraction must exist in the RT_FRACTION table as FRACTION.

•"SUBCONTRACTOR” must exist in the RT_COMPANY table.

•The depth_unit must exist in the RT_UNIT table as UNIT_CODE.

•Permit_v2

•The company_code must exist in the RT_COMPANY table as COMPANY_CODE.

•Monitor_v2

•The data_provider must exist in the RT_COMPANY table as COMPANY_CODE.

•The loc_type must exist in the RT_LOCATION_TYPE table as LOCATION_TYPE_CODE.

•The loc_minor_basin must exist in the RT_BASIN table as BASIN_CODE.

•The flow_parameter must exist in the RT_ANALYTE table as CAS_RN.

•The loc_state_code must exist in the RT_STATE table as STATE_CODE.

•The stream_code must exist in the RT_STREAM table as STREAM_CODE.

•The units must exist in the RT_UNIT table as UNIT_CODE.

•The drilling_subcontractor must exist in the RT_COMPANY table as COMPANY_CODE.

•Theengineer_subcontractor must exist in the RT_COMPANY table as COMPANY_CODE.

•The estab_company_code must exist in the RT_COMPANY table as COMPANY_CODE.

•The excav_company_code must exist in the RT_COMPANY table as COMPANY_CODE.

•The inspect_subcontractor must exist in the RT_COMPANY table as COMPANY_CODE.

•The subfacility_code must exist in the DT_SUBFACILITY table as SUBFACILITY_CODE.

•The permit_number must exist in the DT_PERMIT table as PERMIT_NUMBER.

•MonitorReport_v2

•The cas_rn must exist in the RT_ANALYTE table as CAS_RN.

•The chemical_name must exist in the RT_ANALYTE table as CHEMICAL_NAME.

•The fraction must exist in the RT_FRACTION table as FRACTION.

•The frequency_code must exist in the RT_FREQUENCY table as FREQUENCY_CODE.

•The sample_type_code must exist in the RT_SAMPLE_TYPE tableas SAMPLE_TYPE_CODE.

•The sample_method must exist in the RT_SAMPLE_METHOD table as METHOD_CODE.

•The quantification_unit must exist in the RT_UNIT table as UNIT_CODE.

•The qc_unit must exist in the RT_UNIT table as UNIT_CODE.

•The ql_unit must exist in the RT_UNIT table as UNIT_CODE.

•The permit_number must exist in the DT_DISCHARGE_MONITOR table as PERMIT_NUMBER.

•The monitor_number must exist in the DT_DISCHARGE_MONITOR table as MONITOR_NUMBER.

•Samples_v2

•The sample_type_code must exist in the RT_SAMPLE_TYPE table as SAMPLE_TYPE_CODE.

•The sampling_method must exist in the RT_SAMPLE_METHOD table as METHOD_CODE.

•The matrix_code must exist in the RT_MATRIX table as MATRIX_CODE.

•The task_code must exist in the DT_TASK table as TASK_CODE.

•The sys_loc_code must exist in the DT_LOCATION table as SYS_LOC_CODE.

•Results_v2

•The analytic_method must exist in the RT_ANALYTIC_METHOD table as ANALYTIC_METHOD.

•The cas_rn must exist in the RT_ANALYTE table as CAS_RN.

•The result_qualifier must exist in the RT_QUALIFIER table as QUALIFIER.

•The result_unit must exist the RT_UNIT table as UNIT_CODE.

•The result_type_code must exist in the RT_RESULT_TYPE table as RESULT_TYPE_CODE.

•The detection_limit_unit must exist in the RT_UNIT table as UNIT_CODE.

•The fraction must exist in the RT_FRACTION table as FRACTION.

•The test_type must exist in the RT_TEST_TYPE table as TEST_TYPE.

•The lab_name_code must exist in the RT_COMPANY talbe as COMPANY_CODE.

•The fraction must exist in the RT_FRACTION table as FRACTION.

 

 

EQuIS Table Mappings:

 

 

Exports: The data returned will be automatically filtered by the facility to which the user is connected, as well as by the parameters selected prior to running the report. See the Exports from Professional EDP article for more information about running exports.

 

 

 

 

 

Export Parameters:

 

 

 

 

The Lab Results EDD export may have to be additionally filtered by analyte, task, and/or SDG if field samples have also been populated.