Ontario Ministry of the Environment Wastewater System (MEWS)

MEWS Version 3.5
July 2014

We welcome your feedback

We have used our best efforts to produce a guide that will help you become familiar and comfortable with the MEWS application. Changes will be made periodically to the information contained in this guide and will be incorporated in later editions. In case of discrepancies between the MEWS guide and other guides and checklists, the official documents such as acts and regulations will prevail.

We welcome your comments about this guide, its organization or subject matter. Please send your comments directly to:

Water Wells and MISA Data Reporting Unit
Ministry of the Environment and Climate Change (MOECC)
Environmental Monitoring and Reporting Branch
125 Resources Road
Toronto, Ontario M9P 3V6

WastewaterReporting@ontario.ca

For user account issues and system access issues, please contact the MEWS Program Officer at (807) 475-1570 or toll free (in Ontario) at 1-800-875-7772.

Please direct any other correspondence regarding reporting of data to the District Office of the Ministry of the Environment and Climate Change, Senior Environmental Officer. A listing of Ministry District Offices is viewable from the Ministry website.

MEWS Industrial User Guide
Copyright © 2014 Ontario Ministry of the Environment and Climate Change

Preface (1.0)

The Ontario Ministry of the Environment Wastewater System (MEWS) is a web-based application designed for the monitoring and reporting of wastewater from companies discharging into Ontario waterways.

The Ontario Ministry of the Environment and Climate Change’s Effluent Monitoring and Effluent Limits Regulations (and other legal instruments such as Certificates of Approval / Environmental Compliance Approval) under the Environmental Protection Act of Ontario (the EPA), require designated dischargers of wastewater who discharge directly to water bodies in Ontario to sample their wastewater discharge, analyze the wastewater discharge samples, and report data to the Ministry based on the results of the analysis of the samples, as well as to ensure that the quality and quantity of wastewater discharge comply with the regulation limit.

Pre-approved users are permitted entry to the secure MEWS website and can gain access to their discharge data. Users interact with the MEWS website using Internet browsers and the World Wide Web.

The Ministry uploads a Company Profile File (CPF) to MEWS for each work site. The CPF lists the sample and parameter monitoring and reporting requirements of each work site, reflecting their regulatory obligations. Users may upload data to MEWS by XML file transfer, or they may type in the data to MEWS directly through data entry forms on the web page. Once a discharger is satisfied with the quality of the data uploaded or directly entered to MEWS, they can use MEWS to submit their data to the Ministry electronically and by mail to satisfy their regulatory obligations. Submitted data is transferred to the Ministry’s Sample Results Data Store (SRDS) database, which is the underlying database for the MEWS interface.

This document provides technical information on the XML file structure and the SRDS code mapping, allowing the user to translate codes from their own database into the Ministry code format and upload large quantities of data to MEWS. It is a complement to the MEWS User Guide for Industrial Officers and Staff.

Notes:

  1. References and fieldnames may reflect legacy wastewater data systems, such as the Industrial Monitoring Information System (IMIS) or the Municipal / Industrial Strategy for Abatement Information Data Entry System (MIDES).
  2. References to "sample" are strictly related to the sampling of wastewater discharge, and not to examples.

General (2.0)

2.1. XML Parts and Reserved Characters

There are three main parts to the XML coding: submission, sample and result. The submission part refers to the work site, the sample part refers to the sample details such as control point and date, and the result part refers to details about the parameter and the actual result value.

XML reserves the characters "<" and ">" to open and close the three main parts of the XML coding. These characters should not be used in field result values (i.e. between quotations) in XML files - they will generate XML parser errors. These characters are typically used in field result values as part of a Remark Code - see Section 6.10 for alternative characters.

2.2. Data Records and Frequency

Only those parameters requiring a result are included in any given sample; thus, a parameter with a weekly frequency (rpttime_name = "WEEKLY") is included only once every weekit is not coded for six of the seven days in a week. Similarly, a parameter with a Daily frequency and result_structure = P3 (three times in a day) is coded three times in a day, while a parameter with a Daily frequency and result_structure = SI (single) is coded only once per day.

A parameter with a frequency of "EVENT" is for sample locations which have infrequent flows. A result is expected to be entered only when there are flow events at that sampling location. All other sampling frequencies are expected to have a result value entered when there is flow, and if there is no flow, an appropriate remark code should be entered.

Therefore, a sample can have one or more results, and a submission can have one or more samples. However, at least one parameter must be coded for any given sample, while any given sample may include all parameters.

2.3. Revised XML files and data deletion

Upon the successful upload of an XML file to MEWS, sample records are created and populated with this data in the MEWS database. If a discharger wishes to upload corrected data with an XML file, they should be aware of the following:

  • A sample record for a given date and control point remains in the MEWS database even if all result values, remark codes and comments are deleted (blanked).
  • To delete a sample record, the discharger must use the Delete button on the Industrial Data Entry Search Samples screen (see the MEWS User Guide for industrial officers and staff).
  • If the discharger does not want to delete a sample but simply change the data within a sample, they may upload an XML file for the same date / control point with the revised data, in which case all previously uploaded data for this date / control point will be over-written, even data for a previously uploaded parameter that is no longer included in the revised XML file.

2.4. Result Data

An XML file should contain detailed data (such as concentration result values) and summary data that are not calculated by MEWS (such as monthly DISDAY result values). Once this data is uploaded to MEWS successfully, MEWS will calculate summary data as the reports are generated.

2.5. XML Template

The Company Profile Report page in MEWS displays a button called "XML Template" beside each Company Profile File (CPF) version. Click on the XML Template button to obtain an XML file template for the version of CPF desired. Refer to the MEWS User Guide for Industrial Officers and Staff for more details. The XML file template generated from your CPF Report reflects many of the requirements contained in your CPF. This XML file can be used as a basis for creating a complete XML file, for data upload.

XML File Code Exclusions and Format (3.0)

3.1. Code Exclusions

The Company Profile File contains all codes, limits, etc. to create front end forms for data input for each work site, and to allow for calculations and compliance. The CPF contains codes, abbreviations, etc., that you will need to include in your XML file. However, some codes, abbreviations, etc., are used exclusively for the calculation or derivation of result values, and must not be coded for inclusion in XML files. This section lists and describes those particular codes, abbreviations, etc., that the user should not include in their XML file:

  • Control Point Types
  • Loadings
  • Calculated Results
  • Result Structures
  • selected Reporting-for-time (Frequencies)

3.1.1. Control Point Types

Plant-level control points must not be coded in XML files these control points are "virtual" control points used by MEWS to perform calculations, generate summary values, and store data on a plant level.

Control Point Code versus Name
Control Point Type CodeControl Point Type Name
88PLANT PROCESS EFFLUENT
90PLANT ONCE THROUGH COOLING WATER EFFLUENT
91PLANT OTHER DIRECT WASTEWATER
92PLANT COMBINED EFFLUENT
93PLANT BATCH EFFLUENT
94PLANT BUILDING EFFLUENT
95PLANT EVENT DISCHARGE EFFLUENT

3.1.2. Loadings

Loadings are usually not coded in XML files loadings are typically calculated by MEWS based on pipe-level result values. Loadings are indicated by the unit of measure. The following units of measure must not be coded in an XML file for pipe-level control points:

XML Loading Abbreviations versus Name
Abbreviation (unit_abbrev)Name
G/BATCHGRAMS PER BATCH
G/DGRAMS PER DAY
KG/DKILOGRAMS PER DAY
KG/MOKILOGRAMS PER MONTH
KG/WKKILOGRAMS PER WEEK
KG/AKILOGRAMS PER YEAR
KG/BATCHKILOGRAMS PER BATCH
KG/8HRSKILOGRAMS PER EIGHT HOURS
UG/BATCHMICROGRAMS PER BATCH
MG/DMILLIGRAMS PER DAY
MG/BATCHMILLIGRAMS PER BATCH
T/DTONNES PER DAY

In rare cases, a discharger may have a control point customized for their reporting needs that will allow loading result values to be entered. For instance, the Control Point Type "Production" allows entry of T/D for a plant-level result value.

3.1.3. Calculated Results

Calculated or derived results must not be coded in XML files these results are calculated by MEWS based on non-calculated result values. Results are given as a component of the result structure. The following components are used only for calculated results and must be excluded from the XML file:

XML Component Abbreviation Chart
Component Abbreviation (component_type)Component NameComponent Description
AVAVERAGEAV = SUM(VALUES)/NO
GMGEOMETRIC MEANNth ROOT OF THE PRODUCT OF N NUMBERS OF SAMPLES
MNMINIMUMSMALLEST VALUE
MXMAXIMUMLARGEST VALUE
NONUM. IN AVERAGENUMBER OF VALUES USED IN CALCULATION. OF AVERAGE
NVNUMBER IN VALUENUMBER OF VALUES RELATED TO RESULT

3.1.4. Result Structures

Calculated or derived results must not be coded in XML files these results are calculated by MEWS based on non-calculated result values. Results are given as a component of the result structure. The following Result Structures are used only for calculated results and must be excluded from the XML file:

XML Result Structure Abbreviation versus Name
Result Structure Abbreviation (result_structure)Result Structure Name
AGSIMPLE AVERAGE
ANAVERAGE AND MINIMUM
ARAVERAGE
AXAVERAGE AND MAXIMUM
DRDAILY REPORTING
GRGEOMETRIC MEAN
MNMINIMUM
MRMISA MONTHLY REPORTING
MXMAXIMUM
PIMAXIMUM AND MINIMUM
QTQUARTERLY TOTAL

3.1.5. Selected Reporting-for-time (Frequencies)

Wastewater sample result values must be obtained on a frequency based upon requirements in the regulations. These frequencies are listed in the CPF for each parameter required to be sampled. Some frequencies are associated with calculated or derived result values. The following frequencies must not be coded in XML filesthese frequencies are only used for calculations by MEWS:

XML Frequency Chart
Name (result rpttime_name)Abbreviation (Freq)Description
2 WEEK2WREPORTED OVER 2 CALENDAR WEEKS
2 WEEK ROLLING2WRREPORTED OVER PREVIOUS 2 CALENDAR WEEKS
20 DAY20DREPORTED OVER 20 DAYS
20 DAY ROLLING20DRREPORTED OVER PREVIOUS 20 DAYS
28 DAYS ROLLING28DRREPORTED OVER PREVIOUS 28 DAYS
30 DAYS30DREPORTED OVER 30 DAYS
30 DAYS ROLLING30DRREPORTED OVER PREVIOUS 30 DAYS
4 MONTH ROLLING4MRREPORTED OVER PREVIOUS 4 CALENDAR MONTHS
4 WEEK4WREPORTED OVER 4 CALENDAR WEEKS
4 WEEK ROLLING4WRREPORTED OVER PREVIOUS 4 CALENDAR WEEKS
DAILY SUMMARYDSREPORTING FOR DAILY SUMMARY
MONTHLY SUMMARYMSREPORTING FOR MONTHLY SUMMARY
TWELVE MONTH ROLLING12MRREPORTING OVER 12 CONSECUTIVE MONTHS

3.2. Format

The following is the XML file format for uploading the work site wastewater discharge data. See the following sections for explanations of each component.

<?xml version="1.0" encoding="UTF-8"?> 
<!ELEMENT submission (sample*)> 
<!ATTLIST submission
    imis_company_code CDATA #REQUIRED 
    ws_name CDATA #REQUIRED>
<!ELEMENT sample (result*)> 
<!ATTLIST sample 
    sample_date_time CDATA #REQUIRED 
    imis_cp_ext CDATA #REQUIRED 
    cp_name CDATA #IMPLIED 
    dischg_sample_cd CDATA #IMPLIED 
    sample_comment CDATA #IMPLIED>
<!ELEMENT result EMPTY> 
<!ATTLIST result
    rpttime_name CDATA #REQUIRED 
    sis_imis_code CDATA #REQUIRED 
    parm_name CDATA #IMPLIED 
    unit_abbrev CDATA #REQUIRED 
    rptas_abbrev CDATA #REQUIRED 
    result_structure CDATA #REQUIRED 
    component_type CDATA #REQUIRED 
    result_value CDATA #REQUIRED 
    remark_code_1 CDATA #IMPLIED 
    remark_code_2 CDATA #IMPLIED 
    remark_code_3 CDATA #IMPLIED 
    result_comment CDATA #IMPLIED 
    imis_regulation_code_1 CDATA #REQUIRED 
    imis_regulation_code_2 CDATA #IMPLIED 
    imis_regulation_code_3 CDATA #IMPLIED 
    imis_regulation_code_4 CDATA #IMPLIED 
    imis_regulation_code_5 CDATA #IMPLIED 
    imis_regulation_code_6 CDATA #IMPLIED 
    imis_regulation_code_7 CDATA #IMPLIED 
    imis_regulation_code_8 CDATA #IMPLIED 
    imis_regulation_code_9 CDATA #IMPLIED 
    imis_regulation_code_10 CDATA #IMPLIED>

XML Attribute Definition (4.0)

4.1. Submission Level Attributes

XML Submission Level Attributes Chart
XML AttributeDefinitionExample Data
imis_company_codeCode for Work Site provided by MOECC Environmental Monitoring and Reporting Branch (EMRB).
Type: 10 digits
Mandatory field
See section 5.0 validation rules
Must match one of the SRDS imis_company_code that your MEWS account can access.
Example data: see section 6.1.
ws_nameName of Work Site.
Type: Max. 100 characters
Mandatory field
Not validated
Example data: see section 6.1; this field does not have to match the legal name, but can be edited to fit within the 100 character limitation.

Note: all string comparisons are case insensitive ignoring leading and trailing spaces.

4.2. Sample Level Attributes

XML Sample Level Attributes Chart
XML AttributeDefinitionExample Data
sample_date_timeCode for sample control point.
Type: 8 characters (YYYYMMDD)
Mandatory field
No entry for time is required
See section 5.0 validation rules
'20041201' for December 1, 2004.
imis_cp_extCode for sample control point.
Type: 4 digits
Mandatory field
See section 5.0 validation rules
Must match one of the SRDS imis_cp_ext of the control points that your MEWS account can access.
Example data: see section 6.2.
cp_nameName of sample control points for the control point of the work site.
Type: Max. 50 characters
Mandatory field
Not validated
Example data: see section 6.2.
dischg_sample_cdSample code
Type: Max. 10 characters
Optional field
Not validated
Discharge Sample Code, used by the discharger for internal documentation as required.
sample_commentSample comment
Type: Max. 2000 characters
Optional field
Not validated
 

Note: all string comparisons are case insensitive ignoring leading and trailing spaces.

4.3. Result Level Attributes

XML Result Level Attributes Chart
XML AttributeDefinitionValidation
rpttime_nameDefines the time period for which the result was reported
Type: Max. 35 characters
Mandatory field
See section 5.0 validation rules
Must match one of the SRDS reportfor-time names.
Example data: see section 6.4.
sis_imis_codeCode for parameter. A parameter can be a:
  • chemical element
  • chemical compound
  • physical characteristics
  • count
  • rate
Type: Max. 6 characters
Mandatory field
See section 5.0 validation rules
Must match one of the SRDS sis_imis_code codes.
Example data: see section 6.5.
parm_nameParameter name
Type: Max. 50 characters
Mandatory field
Not validated
Example data: see section 6.5.
unit_abbrevUnit of measure abbreviation
Type: Max. 8 characters
Mandatory field
See section 5.0 validation rules
Must match the SRDS unit abbreviation defined for the parameter.
Example data: see section 6.6.
If none is required, enter "NO DIM" (for No Dimension).
rptas_abbrevContains information on how the result is reported. It is important when the result can be reported in several ways, such as:
  • as Phosphorus
  • as Phosphate
  • as Si
  • as Si O2

Type: Max. 8 characters
Mandatory field
See section 5.0 validation rules
Must match the SRDS "reported as abbreviation" defined for the parameter.
Example data: see section 6.7.
If none is applicable, enter "NOT APPL".
result_structureQualifier of the result as to the structure and number of associated values reported.
Type: 2 characters
Mandatory field
See section 5.0 validation rules
Must match one of the SRDS result structure abbreviation.
Example data: see section 6.8.
component_typeQualifier of the value as to the way it is measured or calculated.
Type: 2 characters
Mandatory field
See section 5.0 validation rules
Must match the SRDS "component type abbreviation" defined for the result structure.
Example data: see section 6.9.
result_valueValue of the analytical test result
Type: Max. 20 characters
Mandatory field
See section 5.0 validation rules
 
remark_code_1Remark code # 1
Type: Max. 3 characters
Optional field
See section 5.0 validation rules
If specified, must match one of the SRDS remark codes.
Example data: see section 6.10.
remark_code_2Remark code # 2
Type: Max. 3 characters
Optional field
See section 5.0 validation rules
If specified, must match one of the SRDS remark codes, and Remark Code 1 must not be null.
Example data: see section 6.10.
remark_code_3Remark code # 3
Type: Max. 3 characters
Optional field
See section 5.0 validation rules
If specified, must match one of the SRDS remark codes, and Remark Code 1 and 2 must not be null.
Example data: see section 6.10.
result_commentresult comment
Type: Max. 2000 characters
Optional field
Not validated
 
Imis_regulation_code_1Regulation for which the result is reported.
Type: 2 characters
Mandatory field
See section 5.0 validation rules
Must match one of the SRDS Regulation Codes.
Example data: see section 6.3.
imis_regulation_code _2Regulation for which the result is reported.
Type: 2 characters
Optional field
See section 5.0 validation rules
If specified, must match one of the SRDS Regulation Codes.
Example data: see section 6.3.
imis_regulation_code _3Regulation for which the result is reported.
Type: 2 characters
Optional field
See section 5.0 validation rules
imis_regulation_code _4Regulation for which the result is reported.
Type: 2 characters
Optional field
See section 5.0 validation rules
imis_regulation_code _5Regulation for which the result is reported.
Type: 2 characters
Optional field
See section 5.0 validation rules
imis_regulation_code _6Regulation for which the result is reported.
Type: 2 characters
Optional field
See section 5.0 validation rules
imis_regulation_code _7Regulation for which the result is reported.
Type: 2 characters
Optional field
See section 5.0 validation rules
imis_regulation_code _8Regulation for which the result is reported.
Type: 2 characters
Optional field
See section 5.0 validation rules
imis_regulation_code _9Regulation for which the result is reported.
Type: 2 characters
Optional field
See section 5.0 validation rules
 
imis_regulation_code _10Regulation for which the result is reported.
Type: 2 characters
Optional field
See section 5.0 validation rules

Validation (5.0)

The following table lists validation rules to keep in mind when creating an XML format file for data upload to MEWS. The error messages shown will appear in the XML upload Error Log.

Important Note: An XML file may contain more than one sample. In such cases, even if the XML file failed one or more validation rules, the samples that did pass the validation up to the failed sample are uploaded.

For example: In one XML file, there are entries for 4 samples. One on Jan 11, 2007, one on Jan 12, 2007, one on Jan 13, 2007, and one on Jan 14, 2007. When the XML file is uploaded, all the validation passed for Jan 11, 2007, Jan 12, 2007, and Jan 14, 2007 samples. There are some validations that failed for Jan 13, 2007 sample. In this case, the sample for Jan 11, 2007 and Jan 12, 2007 are saved in the MEWS database. The XML upload will have a status of FAILED and display the validations that failed for Jan 13, 2007 sample in the file error log. The sample data for Jan 14, 2007 are not saved in the MEWS database.

Multiple XML fields (e.g., imis_regulation_code_1, imis_regulation_code_2, etc.) should be used sequentially.

Note: All string comparisons must be case insensitive ignoring leading and trailing spaces.

XML Field Validation Rules
XML FieldValidation RulesError Messages
N/AIf the file is not a normal file or the file length is not longer than 0 or the file name is not ended by ".XML".Please specify a valid XML file to upload.
AnyIf the file is an XML file but failed the XML parser validation, then the user will see the parser errors.
These errors are generated by the parser directly.
Parsing Error Messages.
For instance:
  • 1.1 Fatal - Invalid document structure. line=1, column=1.
  • 1.2 Fatal - Document must contain root element. line=1, column=44.
<submission>
imis_company_codeCannot be null.Missing value for SubmissionXMLElement. <imis_company_code>.
Must exist in the database.Invalid company code <imis_company_code>.
ws_nameCannot be null.Missing value for SubmissionXMLElement. <ws_name>.
Cannot be over 100 characters.SubmissionXMLElement.ws_name is over 100 characters.
<sample>
sample_date_timeCannot be null.Missing value for SampleXMLElement. <sample_date_time>.
Cannot be within a time period for which data has already been submitted.Invalid Sample Date <sample_date_time>: Cannot create new Sample within a submitted period.
Must be earlier than the current date / time.Invalid Sample Date <sample_date_time>: Must be earlier than the current date / time.
Must be in the format yyyymmdd.Invalid Sample Date <sample_date_time>: Must be in the format yyyymmdd.
imis_cp_extCannot be null.Missing value for SampleXMLElement. <imis_cp_ext>.
Must exist in the database.Invalid imis cp ext <imis_cp_ext>.
cp_nameCannot be null.Missing value for SampleXMLElement. <cp_name></cp_name>
Cannot be over 50 characters.SampleXMLElement.cp_name is over 50 characters.
dischg_sample_cdContent is not validated. 
Limit of 10 characters as a field property.Dischg_sample_cd Value is over 10 characters.
sample_commentContent is not validated. 
Cannot be over 2000 characters.Sample Comment is over 2000 characters.
<result>
rpttime_nameCannot be null.Missing value for ResultXMLElement. <rpttime_name>.
Must exist in the database.Invalid ResultXMLElement.rpttime_name <rpttime_name>.
sis_imis_codeCannot be null.Missing value for ResultXMLElement <sis_imis_code>.
Must exist in the database.Invalid ResultXMLElement.sis_imis_code <sis_imis_code>.
parm_nameCannot be null.Missing value for ResultXMLElement.parm_name.
Content is not validated. 
Cannot be over 50 characters.ResultXMLElement.parm_name is over 50 characters.
unit_abbrevCannot be null.Missing value for ResultXMLElement. <unit_abbrev>.
Must exist in the database.Invalid ResultXMLElement.unit_abbrev <unit_abbrev>.
rptas_abbrevCannot be null.Missing value for ResultXMLElement. <rptas_abbrev>.
Must exist in the database.Invalid ResultXMLElement.unit_abbrev <rptas_abbrev>.
result_structureCannot be null.Missing value for ResultXMLElement. <result_structure>.
Must exist in the database.Invalid ResultXMLElement.result_structure .
component_typeCannot be null.Missing value for ResultXMLElement.component_type .
Must exist in the database.Invalid ResultXMLElement.component_type .
result_valueCannot be null unless one or more remark_code is provided.Result value or Remark Code must be entered.
If the sis_imis_code is 'PH', 'PHAVG', 'PHMAX' or 'PHMIN', the result value must be between 1-14 inclusive.Invalid ValueRemarksRecord.result_value for parameter pH.
If the sis_imis_code is 'DISDAY', the result value must be 1-31 inclusive.
Also, see Note below (*).
Invalid ValueRemarksRecord.result_value for parameter DISDAY.
If the sis_imis_code is other value, the result value must be a valid integer or decimal number. The result value cannot be in scientific notation format.Invalid ValueRemarksRecord.result_value format.
Cannot be over 20 characters.Result Value is over 20 characters.
If the sis_imis_code is not null and the component_type begins with "T", the result value must be in the format 24-hour time format "HH:MM":
Hour (HH) must be between 00 and 23 inclusive.
Minute (MM) must be between 00 and 59 inclusive.
Invalid ValueRemarksRecord.result_value Time format.
If the sis_imis_code is not null and the component_type begins with "T", there must also be a component_type beginning with "V".Corresponding <component_type> value is required for result value.
If the sis_imis_code is not 'FWTEMP', 'FWTINC' or 'ORP', the result value may not be negative.Invalid Result Value. Verify that the value is a positive number.
If the sis_imis_code is 'ACLETR' or 'ACLEDA', acceptable result values are limited to blank, PASS, or FAIL.Invalid Pass/Fail Value. Verify that the value is either "PASS" or "FAIL.
remark_code_1If the value is not null, it must be a valid remark code that exists in the database.Invalid ValueRemarksRecord.remark_code_1 <remark_code_1>.
If the parameter is a Flow with a result value that is positive, the remark code cannot indicate that there is no flow.Positive flow cannot have a <remark_code_1> remark code.
remark_code_2If the value is not null, remark_code_1 must not be null.Remark code 1 cannot be blank when remark code 2 is specified.
Must be a valid remark code that exists in the database.Invalid ValueRemarksRecord.remark_code_2 <remark_code_2>.
If the parameter is a Flow with a result value that is positive, the remark code cannot indicate that there is no flow.Positive flow cannot have a <remark_code_2> remark code.
remark_code_3If the value is not null, both, remark_code_1 and remark_code_2 must not be null.Remark code 1 and 2 cannot be blank when remark code 3 is specified.
Must be a valid remark code that exists in the database.Invalid ValueRemarksRecord.remark_code_3 <remark_code_3>.
If the parameter is a Flow with a result value that is positive, the remark code cannot indicate that there is no flow.Positive flow cannot have a <remark_code_3> remark code.
result_commentContent is not validated. 
Cannot be over 2000 characters.Sample Comment is over 2000 characters.
imis_regulation_code_1Cannot be null. This error message will supersede other imis_regulation_code error messages.Missing value for SampleXMLElement. <imis_regulation_code_1>.
Must exist in the database.Invalid regulation code <imis_regulation_code_1>.
Must be configured in the company profile file (CPF) for the parameter.Regulation code not configured in company profile for parameter.
imis_regulation_code_2If the value is not null, it must exist in the database.Invalid regulation code <imis_regulation_code_2>.
Cannot be the same value as any other regulation code.Duplicated regulation code <imis_regulation_code_2>.
Must be configured in the company profile file (CPF) for the parameter.Regulation code not configured in company profile for parameter.
imis_regulation_code_3If the value is not null, it must exist in the database.Invalid regulation code <imis_regulation_code_3>.
Cannot be the same value as any other regulation code.Duplicated regulation code <imis_regulation_code_3>.
Must be configured in the company profile file (CPF) for parameter.Regulation code not configured in company profile for parameter.
imis_regulation_code_4If the value is not null, it must exist in the database.Invalid regulation code <imis_regulation_code_4>.
Cannot be the same value as any other regulation code.Duplicated regulation code <imis_regulation_code_4>.
Must be configured in the company profile file (CPF) for the parameter.Regulation code not configured in company profile for parameter.
imis_regulation_code_5If the value is not null, it must exist in the database.Invalid regulation code <imis_regulation_code_5>.
Cannot be the same value as any other regulation code.Duplicated regulation code <imis_regulation_code_5>. </imis_regulation_code_5>
Must be configured in the company profile file (CPF) for the parameter.Regulation code not configured in company profile for parameter.
imis_regulation_code_6If the value is not null, it must exist in the database.Invalid regulation code <imis_regulation_code_6>.
Cannot be the same value as any other regulation code.Duplicated regulation code <imis_regulation_code_6>.
Must be configured in the company profile file (CPF) for the parameter.Regulation code not configured in company profile for parameter.
imis_regulation_code_7If the value is not null, it must exist in the database.Invalid regulation code <imis_regulation_code_7>.
Cannot be the same value as any other regulation code.Duplicated regulation code <imis_regulation_code_7>.
Must be configured in the company profile file (CPF) for the parameter.Regulation code not configured in company profile for the parameter.
imis_regulation_code_8If the value is not null, it must exist in the database.Invalid regulation code <imis_regulation_code_8>.
Cannot be the same value as any other regulation code.Duplicated regulation code <imis_regulation_code_8>.
Must be configured in the company profile file (CPF) for the parameter.Regulation code not configured in company profile for the parameter.
imis_regulation_code_9If the value is not null, it must exist in the database.Invalid regulation code <imis_regulation_code_9>.
Cannot be the same value as any other regulation code.Duplicated regulation code <imis_regulation_code_9>.
Must be configured in the company profile file (CPF) for the parameter.Regulation code not configured in company profile for parameter.
imis_regulation_code_10If the value is not null, it must exist in the database.Invalid regulation code <imis_regulation_code_10>.
Cannot be the same value as any other regulation code.Duplicated regulation code <imis_regulation_code_10>.
Must be configured in the company profile file (CPF) for the parameter.Regulation code not configured in company profile for parameter.
N/AIf the results are duplicated identically.Configuration is duplicated for multiple regulations.
If result records are duplicated, with the only difference being the regulation.Configuration is duplicated for multiple regulations.
If result records are duplicated, with the only difference being the result value.Configuration is duplicated for multiple regulations.
Combination of : sis_imis_code
unit_abbrev
rpttime_name rptas_abbrev
result_structure
component_type
Must exist in the company profile file.Invalid Configuration.
Combination of : result_structure
component_type
Must exist in the company profile file.Invalid result_structure and component_type combination.
AllIf any XML Field is duplicated, regardless of value for the Field.Parser Error: Fatal - Attribute "<xml field>" was already specified for element "<element>". [line=<#>, column=<#>] </element>

* Note for the parameter DISDAY: Two sectors of the MISA regulations, Petroleum Sector and Industrial Minerals Sector, are not explicitly required to report the parameter DISDAY at the pipe level. The system currently does not allow DISDAY to be customized at the plant level; therefore, any customization for reporting of DISDAY must be customized at the pipe level. This requires an interpretation of these two regulations to have the same meaning as the other regulations, which require reporting DISDAY at the pipe level.

If there is no flow for a full month, the DISDAY result value should remain blank (do not enter zero). In addition, a remark code is not required if the DISDAY result value is blank.

Example Data (6.0)

The tables in the following subsections show example data for illustration purpose only:

  • Subsection 6.1: Work Site Codes
  • Subsection 6.2: Control Points

The tables in the following subsections show a complete list of codes that are likely to appear in the CPF or that are required for XML mapping. The codes may be revised from time to time. It is important to use only those codes referred to in your work site Company Profile File (CPF).

  • Subsection 6.3: Regulation Codes
  • Subsection 6.4: Report for Time Codes
  • Subsection 6.5: Parameter Codes
  • Subsection 6.6: Unit of Measure Codes
  • Subsection 6.7: Reported As Codes
  • Subsection 6.8: Result Structure Codes
  • Subsection 6.9: Component Codes
  • Subsection 6.10: Remark Codes

All of the tables indicate which columns are applicable for XML mapping and which are seen on the Company Profile File (CPF). The actual field names appearing in the XML mapping and the CPF may be shown in brackets (e.g., "imis_company_code") for greater clarity.

For instance, in the Work Site Codes table, XML mapping will require entry of a value for the fieldname imis_company_code (value "0009990003", in the first column) and for the fieldname ws_name (value "INDUSTRIAL TEST PLANT INC.", in the second column). The CPF for this company / discharger shows the fieldname Company, with a value "INDUSTRIAL TEST PLANT INC.", in the second column.

Columns with no shading are used in XML mapping and/or the CPF, while shaded columns show information for greater clarity for the user.

6.1. Work Site Codes

The following table shows an example of a company work site (discharger) and the associated IMIS Company Code.

XML Work Site Codes
XMLXML and CPF
Company Code (imis_company_code)Work Site Name (ws_name and Company)
0009990003INDUSTRIAL TEST PLANT INC.

6.2. Control Points

The following table shows examples of control points their names and their typical extension "codes". Use the Control Points as provided by the Company Profile File (CPF).

Sorted by Control Point IMIS Extension.

XML Control Points
XMLXML and CPF
Control Point IMIS Extension (imis_cp_ext)Control Point Name (cp_name and Control Point)
0100FINAL EFFLUENT, STATION 1
0200ONCE THROUGH COOLING WATER
0300FRONT STREET COMBINED SEWER
0700BLAST FURNACE RECYCLE BLOWDOWN
1201REGENERATION FILTER DISCHARGE
2700DUAL MILLS COOLING WATER DISCHARGE

6.3. Regulation Codes

The following table lists all "regulations" (or legal instruments) that are likely to apply to the XML mapping and the CPF. Other "regulations" existcontact the Ministry if clarification is required.

Sorted by Regulation Code.

XML Regulation Codes
XMLCPF
Regulation Code (imis_regulation_code_1) footnote 1Regulation Name (Regulation)
CAC. OF A. - CERTIFICATE OF APPROVAL / ECA ENVIRONMENTAL COMPLIANCE APPROVAL
COCONTROL ORDER
FRFEDERAL REQUIREMENTS
MCMISA COMPLIANCE
PGPROVINCIAL GUIDELINES
PRPROVINCIAL REGULATIONS

6.4. Report for Time Codes

These codes are also known as Frequency Codes. They reflect both the monitoring requirements (i.e., sampling frequency, such as Single Result) and the reporting requirements (e.g., monthly summary).

Sorted by Name.

XML Report for Time Codes
XMLCPFDescription
Name (result rpttime_name)Abbreviation (Freq)
2 WEEK2WREPORTED OVER 2 CALENDAR WEEKS
2 WEEK ROLLING2WRREPORTED OVER PREVIOUS 2 CALENDAR WEEKS
2/YEAR2/YRTWO SAMPLES PER CALENDAR YEAR
20 DAY20DREPORTED OVER 20 DAYS
20 DAY ROLLING20DRREPORTED OVER PREVIOUS 20 DAYS
28 DAYS ROLLING28DRREPORTED OVER PREVIOUS 28 DAYS
30 DAYS30DREPORTED OVER 30 DAYS
30 DAYS ROLLING30DRREPORTED OVER PREVIOUS 30 DAYS
4 MONTH ROLLING4MRREPORTED OVER PREVIOUS 4 CALENDAR MONTHS
4 WEEK4WREPORTED OVER 4 CALENDAR WEEKS
4 WEEK ROLLING4WRREPORTED OVER PREVIOUS 4 CALENDAR WEEKS
5/WEEK5/WKFIVE SAMPLES PER CALENDAR WEEK
BATCHBBATCH SAMPLE
BI-MONTHLYBMREPORTED FOR BI-MONTHLY (once every 2 months)
BI-WEEKLYBWREPORTED FOR BI-WEEKLY (once every 2 weeks)
DAILYDREPORTED FOR A DAY
DAILY SUMMARYDSREPORTING FOR DAILY SUMMARY
EVENTEREPORTED FOR EVENT
HOURHRREPORTED OVER A HOUR
INSTANTANEOUSINSINGLE RESULT
MONTHLYMREPORTED FOR A CALENDAR MONTH
MONTHLY SUMMARYMSREPORTING FOR MONTHLY SUMMARY
QUARTERLYQREPORTED FOR QUARTERLY
THRICE WEEKLYTWREPORTED FOR THRICE WEEKLY (3 times a week)
TWELVE MONTH ROLLING12MRREPORTING OVER 12 CONSECUTIVE MONTHS
WEEKLYWREPORTED FOR A CALENDAR WEEK
YEARLYYRREPORTED FOR A CALENDAR YEAR

6.5. Parameter Codes

Use the parameters as provided in the Company Profile File (CPF). Below is a listing of the most commonly used parameters for industrial discharges. Many of these parameters are also available as a scanned parameter, as may be required for a metals scan. Parameters not listed below can be added to CPF's - please contact your local Environmental Officer (EO) for further details.

The parameter codes and names relate to specific parameter testing methods and analysis. Verify with your laboratory to ensure the correct testing method and analysis is being performed for each parameter.

The following table is sorted by Abbreviation.

XML Parameter Codes
XMLCPF
Abbreviation (sis_imis_code)Parameter Full Name (Parm_Name)
ACDTACIDITY, TOTAL
ACLEDAACUTE LETHALITY DAPHNIA MAGNIA
ACLETRACUTE LETHALITY TROUT
AGUTSILVER, UNFILTERED TOTAL
AGUTSSILVER, MISA SCAN, UNFL.TOTAL
ALFTALUMINUM, FILTERED TOTAL
ALKBALKALINITY, BICARBONATE
ALKOHALKALINITY, HYDROXIDE
ALKTALKALINITY, TOTAL
ALUTALUMINIUM, UNFILTERED TOTAL
ALUTSALUMINIUM, MISA SCAN, UNF.TOT
AOXADSORBABLE ORGANIC HALIDE
ASFTARSENIC, FILTERED TOTAL
ASUTARSENIC, UNFILTERED TOTAL
ASUTSARSENIC, MISA SCAN, UNF.TOTAL
AUUTSGOLD, MISA SCAN, UNFLTD.TOTAL
B2BENZBENZENE C6H6
B2EBNZETHYLBENZENE C8H10
B2TOLUTOLUENE C7H8
BATCHNUMBER OF BATCHES DISCHARGED
BAUTBARIUM, UNFILTERED TOTAL
BAUTSBARIUM, MISA SCAN, UNFL.TOTAL
BBUTBORON, UNFILTERED TOTAL
BBUTSBORON, MISA SCAN, UNFLD.TOTAL
BEUTBERYLIUM,UNFILTERED TOTAL
BEUTSBERYLIUM, MISA SCAN, UNF.TOTL
BIUTBISMUTH - UNFILTERED TOTAL
BIUTSBISMUTH, MISA SCAN, UNF.TOTAL
BOD5BIOCHEMICAL OXYGEN DEMAND, 5 DAY, TOTAL DEMAND
CAFTCALCIUM, FILTERED TOTAL
CAUTCALCIUM, UNFILTERED TOTAL
CAUTSCALCIUM, MISA SCAN, UNF.TOTAL
CBOD5CARBONACEOUS BIOCHEMICAL OXYGEN DEMAND 5 DAY
CCNAURCYANIDE, AVAIL, UNFIL.REAC
CCNFURCYANIDE, FREE, UNFIL.REACTIVE; same as WAD CYANIDE: WEAK ACID DISSOCIABLE CYANIDE
CDFTCADMIUM, FILTERED TOTAL
CDUTCADMIUM, UNFILTERED TOTAL
CDUTSCADMIUM, MISA SCAN, UNF.TOTAL
CEUTSCERIUM, MISA SCAN, UNFL.TOTAL
CLFREECHLORINE, FREE UNFIL.REAC
CLIDURCHLORIDE, UNFIL.REAC
CLRESUCHLORINE, RESIDUAL UNFILTERED
CLTRSCHLORINE, TOTAL RESIDUE
CLUTCHLORINE, UNFIL.TOTAL
CNDVTYSPECIFIC CONDUCTANCE, now used instead of COND25 (CONDUCTIVITY, 25C)
CODCHEMICAL OXYGEN DEMAND
COLTRCOLOR (TRUE)
COUTCOBALT, UNFILTERED TOTAL
COUTSCOBALT, MISA SCAN, UNFL.TOTAL
CRUDERCRUDE RATE THIS MONTH
CRUTCHROMIUM, UNFILTERED TOTAL
CRUTSCHROMIUM, MISA SCAN, UNF.TOTL
CSUTSCESIUM, MISA SCAN, UNFL.TOTAL
CUFTCOPPER, FILTERED TOTAL
CUUTCOPPER, UNFILTERED TOTAL
CUUTSCOPPER, MISA SCAN, UNFL.TOTAL
DII3DIESEL IGNITION IMPROVER
DISDAYDISCHARGE DAYS TOTALS
DISDURDISCHARGE DURATION
DODISSOLVED OXYGEN
DOCCARBON, DISSOLVED ORGANIC
DYUTSDYPROSIUM, MISA SCAN, UNF.TOT
ECIMFBESCHERICHIA COLI MFB
ECMFESCHERICHIA COLI MF
ERUTSERBIUM, MISA SCAN, UNFL.TOTAL
EUUTSEUROPIUM, MISA SCAN, UNF.TOTL
FCMFFECAL COLIFORM MF
FEFTIRON, FILTERED TOTAL
FEUTIRON, UNFILTERED TOTAL
FEUTSIRON, MISA SCAN, UNFLTD.TOTAL
FFIDURFLUORIDE, UNFILTERED REACTIVE
FTFLOWFLOW
FTPRODINDUSTRIAL PLANT PRODUCTION
FWPHPH FIELD
FWTEMPTEMPERATURE, WATER
FWTINCTEMPERATURE, RISE
GAUTSGALLIUM, MISA SCAN, UNF.TOTAL
GBGGROSS BETA GAMMA ACTIVITY
GDUTSGADOLINIUM, MISA SCAN, UNF.TL
GEUTSGERMANIUM, MISA SCAN, UNF.TOT
HARDTHARDNESS, TOTAL
HFUTSHAFNIUM, MISA SCAN, UNF.TOTAL
HGUTMERCURY, UNFILTERED TOTAL
HGUTSMERCURY, MISA SCAN, UNF.TOTAL
HH3TRITIUM, (HYDROGEN 3)
HOUTSHOLMIUM, MISA SCAN, UNF.TOTAL
INUTSINDIUM, MISA SCAN, UNFL.TOTAL
IRUTSIRIDIUM, MISA SCAN, UNF.TOTAL
KKUTPOTASSIUM,UNFILTERED TOTAL
KKUTSPOTASSIUM, MISA SCAN, UNF.TOT
LAUTSLANTHANUM, MISA SCAN, UNF.TOT
LIUTLITHIUM, UNFILTERED TOTAL
LIUTSLITHIUM, MISA SCAN, UNF.TOTAL
LUUTSLUTETIUM, MISA SCAN, UNF.TOTL
MGUTMAGNESIUM,UNFILTERED TOTAL
MGUTSMAGNESIUM, MISA SCAN, UNF.TOT
MNUTMANGANESE,UNFILTERED TOTAL
MNUTSMANGANESE, MISA SCAN, UNF.TOT
MOFTMOLYBDENUM,FILTERED TOTAL
MOUTMOLYBDENUM,UNFILTERED TOTAL
MOUTSMOLYBDENUM, MISA SCAN, UNF.TL
N1HYDRHYDRAZINE
N1MORPMORPHOLINE
NAUTSODIUM, UNFILTERED TOTAL
NAUTSSODIUM, MISA SCAN, UNFL.TOTAL
NBUTSNIOBIUM, MISA SCAN, UNF.TOTAL
NDUTSNEODYMIUM, MISA SCAN, UNF.TOT
NIFTNICKEL, FILTERED TOTAL
NIUTNICKEL, UNFILTERED TOTAL
NIUTSNICKEL, MISA SCAN, UNFL.TOTAL
NNH3FRAMMONIA (UN-IONIZED) FILTER.REAC
NNH3URAMMONIA (UN-IONIZED) UNFIL.REAC
NNH4FRAMMONIUM ION FILTER.REAC
NNHTFRAMMONIUM+AMMONIA, TOTAL FILTER.REAC
NNHTURAMMONIUM+AMMONIA, TOTAL UNFIL.REAC
NNO2FRNITRITE, FILTERED REACTIVE
NNO2URNITRITE, UNFILTERED REACTIVE
NNO3URNITRATE, UNFILTERED REACTIVE
NNOTFRNITRATES TOTAL, FILTER.REAC
NNTKURNITROGEN,TOT,KJELDAHL/UNF.REA
NNTKUTNITROGEN,TOT.KJELDAHL UNF.TOT
NOTRTSEWAGE, RAW
OPRDAYOPERATING DAYS THIS MONTH
ORPOXIDATION REDUCTION POTENTIAL
OSUTSOSMIUM, MISA SCAN, UNFL.TOTAL
P1PCBTPCB TOTAL
P4D3782,3,7,8 - T4CDD
P4F3782,3,7,8 - T4CDF
P92378TETRACHLORDIBENZODIOXIN 2378
P94CDDTOT TETACHLORODIBENZO P-DIOXI
P94CDFTOT TETACHLORODIBENZO FURANS
P95CDDTOT PENTACHLORODIBENZO P-DIXO
P95CDFTOT PENTCHLORODIBENZO FURANS
P96CDDTOT HEXCHLORODIBENZO-P-DIOXIN
P96CDFTOTAL HEXACHLORODIBENZO FURAN
P97CDDTOT HEPTACHLORODIBEN-P-DIOXIN
P97CDFTOT HEPTACHLORODIBENZO FURAN
P98CDDOCTCHLORODIBENZPDIOXIN
P98CDFOCTCHLORODIBENZO FURAN
PB3TOTTRI-ALKYL LEAD (TOTAL)
PB4TOTTETRA-ALKYL LEAD (TOTAL)
PBALKTTOTAL ALKYL LEAD
PBFTLEAD, FILTERED TOTAL
PBUTLEAD, UNFILTERED TOTAL
PBUTSLEAD, MISA SCAN, UNFLTD.TOTAL
PDUTSPALLADIUM, MISA SCAN, UNF.TOT
PEDTEQTOTAL TOXIC EQUIVALENT
PHPH (-LOG H+ CONCN)
PHMAXPH, MAXIMUM
PHMINPH, MINIMUM
PHNOLPHENOLICS, UNFILTERED REACTIVE
PM24DT2,4-DINITRO TOLUENE
PM26DT2,6-DINITRO TOLUENE
PMB2IEBIS-2-CHLOROISOPROPYL ETHER
PMDPEDIPHENYL ETHER
PMHYORHYDRAZINE
PMPHENPHENOL
PN1MNA1-METHYLNAPHTHALENE
PN2MNA2-METHYLNAPHTHALENE
PNACNYACENAPHTHYLENE
PNBAPBENZO(A)PYRENE
PNBIPHBIPHENYL
PNFLUOFLUORENE
PNINDLINDOLE
PNNAPHNAPHTHALENE
PNPHENPHENANTHRENE
PPO4UTPHOSPHATE,UNFILTERED TOTAL
PPUTPHOSPHORUS,UNFILTERED TOTAL
PPUTSPHOSPHORUS, MISA SCAN, UNF.TL
PRITRTSEWAGE, PRIMARY
PRUTSPRAESODYMIUM, MISA SCAN, UNFL
PTUTSPLATINUM, MISA SCAN, UNF.TOTL
RA226FRADIUM 226, FILTERED
RBUTSRUBIDIUM, MISA SCAN, UNF.TOTL
REUTSRHENIUM, MISA SCAN, UNF.TOTAL
RFCRRIINITIAL REFERENCE CRUDE RATE
RHUTSRHODIUM, MISA SCAN, UNF.TOTAL
RSFRESIDUE,FILTERED
RSPRESIDUE, PARTICULATE
RSPLOIRESIDUE,PART LOSS ON IGNIT.
RSTRESIDUE,TOTAL
RUUTSRUTHENIUM, MISA SCAN, UNF.TOT
SBFTANTIMONY, FILTERED TOTAL
SBUTANTIMONY, UNFILTERED TOTAL
SBUTSANTIMONY, MISA SCAN, UNF.TOTL
SCNFRTHIOCYANATES FILTERED REACTIV
SCUTSSCANDIUM, MISA SCAN, UNF.TOTL
SDCR2MSTREAM DAY CRUDE RATE 2 MONTH
SELEXOSELEXOL DEHYDRATOR
SEUTSELENIUM, UNFILTERED TOTAL
SEUTSSELENIUM, MISA SCAN, UNF.TOTL
SIUTSSILICON, MISA SCAN, UNF.TOTAL
SMUTSSAMARIUM, MISA SCAN, UNF.TOTL
SNDTRTSEWAGE, SECONDARY
SNUTTIN UNFILTERED TOTAL
SNUTSTIN, MISA SCAN, UNFLTD. TOTAL
SOLEXTSOLVENT EXTRACTABLES
SRUTSTRONTIUM, UNFILTERED TOTAL
SRUTSSTRONTIUM, MISA SCAN, UNF.TOT
SSIDURSULPHIDE, UNFILTERED REACTIVE
SSO4FRSULPHATE, FILTERED REACTIVE
SSO4URSULPHATE, UNFILTERED REACTIVE
SSUTSULPHUR, UNFILTERED TOTAL
SSUTSSULPHUR, MISA SCAN, UNF.TOTAL
TAUTSTANTALUM, MISA SCAN, UNF.TOTL
TBUTSTERBIUM, MISA SCAN, UNF.TOTAL
TCMFCOLIFORM, TOTAL MF
TCMPNCOLIFORM, TOTAL MPN
TEUTSTELLURIUM, MISA SCAN, UNF.TOT
THUTSTHORIUM, MISA SCAN, UNF.TOTAL
TIUTTITANIUM - UNFILTERED TOTAL
TIUTSTITANIUM, MISA SCAN, UNF.TOTL
TLUTTHALLIUM, UNFILTERED TOTAL
TLUTSTHALLIUM, MISA SCAN, UNF.TOTL
TMCNLZTOT.COPPER,NICKEL,LEAD,ZINC
TMUTSTHULIUM, MISA SCAN, UNF.TOTAL
TOCCARBON, TOTAL ORGANIC
TODTOTAL OXYGEN DEMAND
TPEFMETEMPERATURE EFFLUENT MEAN
TROTOTAL RESIDUAL OXIDANTS
TURBTURBIDITY
TXDL5A48 HOUR LC50 DAPHNIA
TXFL5A96 HOUR LC50 FISH
UUUTURANIUM, UNFILTERED TOTAL
UUUTSURANIUM, MISA SCAN, UNF.TOTAL
VOLDISDISCHARGED VOLUME - TOTAL
VVUTVANADIUM, UNFILTERED TOTAL
VVUTSVANADIUM, MISA SCAN, UNF.TOTL
WWUTTUNGSTEN, UNFILTERED TOTAL
WWUTSTUNGSTEN, MISA SCAN, UNF.TOTL
X1112TTRICHLOROETHANE 1,1,2
X111CEDICHLOROETHANE 1,1
X112CEDICHLOROETHANE 1,2
X112CPDICHLOROPROPANE 1,2
X1BDCMBROMODICHLOROMETHANE
X1BMETBROMOMETHANE
X1BROMBROMOFORM
X1CDBMCHLORODIBROMOMETHANE
X1CHLMCHLORO METHANE
X1CHLOCHLOROFORM CHCL3
X1CTETCARBON TETRACHLORIDE
X1DCLMMETHYLENE CHLORIDE
X1HCBDHEXACHLOROBUTADIENE
X1TETRTETRACHLOROETHYLENE
X1TRICTRICHLOROETHYLENE C2HCL3
X1VCLVINYL CHLORIDE C2H3CL
X2124TRICHLOROBENZENE 1,2,4
X21245TETRACHLOROBENZENE 1,2,4,5
X212CBDICHLOROBENZENE 1,2
X2EDBETHYLENE DIBROMIDE
X2HCBHEXACHLOROBENZENE
X2HCEHEXACHLOROETHANE
X2OCSTOCTACHLOROSTYRENE
X2T245TRICHLOROTOLUENE 2,4,5
X2TTHMTRIHALOMETHANES, TOTAL
YBUTSYTTERBIUM, MISA SCAN, UNF.TOT
YYUTYTTRIUM
YYUTSYTTRIUM, MISA SCAN, UNF.TOTAL
ZNFTZINC, FILTERED TOTAL
ZNUTZINC, UNFILTERED TOTAL
ZNUTSZINC, MISA SCAN, UNFLTD.TOTAL
ZRUTZIRCONIUM, UNFILTERED TOTAL
ZRUTSZIRCONIUM, MISA SCAN, UNF.TOT

6.6. Unit of Measure Codes

The following units of measure are associated with parameters. For work sites listed under MISA regulations, please refer to Table 1 of the MISA Sampling Protocol for the required unit of measure. The Company Profile File (CPF) of all work sites will indicate the unit of measure associated with each parameter applicable for the work site. A third column has been added to provide clarification to some of the unit of measure names.

Sorted by Abbreviation.

XML Unit of Measure Codes
XML and CPFNameClarification
Abbreviation (unit_abbrev and Unit)
%PERCENT 
% DRY WT% DRY WEIGHT 
%RECOVER% RECOVERY 
%REMOVAL% REMOVAL 
%SAT% SATURATION 
% VOLUME% VOLUME 
% WET WT% WET WEIGHT 
10(3)M3THOUSAND CUBIC METRES 
10(3)M3DTHOUSAND CUBIC METRES PER DAY 
10(3)YD3THOUSAND CUBIC YARDS 
10(6)FT3MILLION CUBIC FEETPreviously was "10^6CUFT"
BQ/LBECQUERELS PER LITRE 
CI/MTHCURRIES PER MONTH 
CMCENTIMETRE 
COUNTCOUNT 
CT/100MLCOUNT PER 100 MLUsed instead of "CFU" (Colony Forming Units per 100ML)
DDAY 
DAM3/DCUBIC DEKAMETRES PER DAY 
DEG. CDEGREES CELSIUSAcidity milligram per litre
FTUFORMAZIN TURBIDITY UNIT 
G/BATCHGRAMS PER BATCH 
G/DGRAMS PER DAY 
G/LGRAMS PER LITRE 
HHOUR 
KGKILOGRAMS 
KG/8HRSKILOGRAMS PER EIGHT HOURS 
KG/AKILOGRAMS PER YEAR 
KG/BATCHKILOGRAMS PER BATCH 
KG/DKILOGRAMS PER DAY 
KG/MOKILOGRAMS PER MONTH 
KG/TKILOGRAMS PER TONNE 
KG/WKKILOGRAMS PER WEEK 
KMKILOMETRE 
LLITRE 
L/SLITRES PER SECOND 
MMETRE 
M3CUBIC METRE 
M3/8HRSCUBIC METRES PER EIGHT HOURS 
M3/BATCHCUBIC METRES PER BATCH 
M3/DCUBIC METRES PER DAY 
M3/MINCUBIC METRES PER MINUTE 
M3/MOCUBIC METRES PER MONTH 
M3/SCUBIC METRES PER SECOND 
MBARMILLIBAR 
MBQ/LMILLIBECQUERELS PER LITRE 
MFIB/LMILLION FIBRES/LITRE 
MG/BATCHMILLIGRAMS PER BATCH 
MG/DMILLIGRAMS PER DAY 
MG/LMILLIGRAMS PER LITRE 
MIGMILLION IMPERIAL GALLONS 
MLMILLILITRE 
MMMILLIMETRE 
MVMILLIVOLT 
NG/LNANOGRAMS PER LITRE 
NO DIMNO DIMENSIONUsed instead of NA (NOT APPLICABLE) and PH UNIT
PG/G WETPICOGRAMS PER GRAM WET 
PG/LPICOGRAMS PER LITRE 
TMETRIC TON (MEGAGRAM) 
T/DTONNES PER DAY 
TCUTRUE COLOUR UNIT 
UG/BATCHMICROGRAMS PER BATCH 
UG/G DRYMICROGRAMS PER GRAM DRY 
UG/LMICROGRAMS PER LITRE 
USIEM/CMMICRO SIEMENS PER CENTIMETRE 

6.7. Reported As Codes

The following "reported as" codes are associated with parameters. For work sites listed under MISA regulations, please refer to Table 1 of the MISA Sampling Protocol for the required "reported as" code. The Company Profile File (CPF) of all work sites will indicate the Reported As code associated with each parameter applicable for the work site. Most parameters have a Reported As of "NOT APPL".

Sorted by Abbreviation, except the most common at the top (NOT APPL).

XML Reported As Codes
XML and CPFReported As Full Name
Reported As Abbreviation (rpt_as_abbrev and Rpt As)
NOT APPLNOT APPLICABLE
ACETATEAS THE ACETATE
AIR DRYAIR DRIED
AMBIENTAMBIENT
AS HFAS HYDROGEN FLUORIDE
AS AGAS SILVER (ARGENTUM)
AS ALAS ALUMINIUM
AS ASAS ARSENIC
AS AUAS GOLD (AURUM)
AS BAS BORON
AS BAAS BARIUM
AS BEAS BERYLLIUM
AS BIAS BISMUTH
AS BRAS BROMINE
AS CAS CARBON
AS C2H2AS ACETYLENE
AS CAAS CALCIUM
AS CACO3AS CALCIUM CARBONATE
AS CAOAS CALCIUM OXIDE
AS CDAS CADMIUM
AS CEAS CERIUM
AS CH3SHAS METHYL MERCAPTAN
AS CLAS CHLORINE
AS CL-AS CHLORIDE
AS CLO2AS CHLORINE DIOXIDE
AS COAS COBALT
AS CO2AS CARBON DIOXIDE
AS CRAS CHROMIUM
AS CSAS CESIUM
AS CUAS COPPER (CUPRUM)
AS DYAS DYSPROSIUM
AS ERAS ERBIUM
AS EUAS EUROPIUM
AS FAS FLUORINE
AS FEAS IRON (FERRUM)
AS GAAS GALLIUM
AS GDAS GADOLINIUM
AS GEAS GERMANIUM
AS HAS HYDROGEN
AS H2SAS SULPHIDE
AS H2SO4AS SULPHURIC ACID
AS H3PO4AS PHOSPHORIC ACID
AS HCLAS HYDROGEN CHLORIDE
AS HCNAS HYDROGEN CYANIDE
AS HCNSAS HYDROGEN THIOCYANATE
AS HEAS HELIUM
AS HFAS HAFNIUM
AS HGAS MERCURY (HYDRARGYRUM)
AS HNO3AS NITRIC ACID
AS HOAS HOLMIUM
AS HOACAS ACETIC ACID
AS IAS IODINE
AS INAS INDIUM
AS IRAS IRIDIUM
AS KAS POTASSIUM (KALIUM)
AS LAAS LANTHANUM
AS LASAS LINEAR ALKYL SULPHONATE
AS LIAS LITHIUM
AS LIHAS LITHIUM HYDRIDE
AS LUAS LUTETIUM
AS MGAS MAGNESIUM
AS MGOAS MAGNESIUM OXIDE
AS MNAS MANGANESE
AS MOAS MOLYBDENUM
AS NAS NITROGEN
AS NAAS SODIUM
AS NBAS NIOBIUM
AS NDAS NEODYMIUM
AS NEAS NEON
AS NH3AS AMMONIA
AS NIAS NICKEL
AS NO2AS NITRITE/NITROGEN DIOXIDE
AS NO3AS NITRATE/NITROGEN TRIOXIDE
AS OAS OXYGEN
AS OSAS OSMIUM
AS PAS PHOSPHORUS
AS P2O5AS PYROPHOSPHATE
AS PBAS LEAD (PLUMBUM)
AS PDAS PALLADIUM
AS PO4AS PHOSPHATE
AS PRAS PRASEODYMIUM
AS PTAS PLATINUM
AS RAAS RADIUM
AS RBAS RUBIDIUM
AS REAS RHENIUM
AS RHAS RHODIUM
AS RNAS RADON
AS RUAS RUTHENIUM
AS SAS SULPHUR
AS SBAS ANTIMONY (STIBIUM)
AS SCAS SCANDIUM
AS SEAS SELENIUM
AS SIAS SILICON
AS SIO2AS SILICA
AS SMAS SAMARIUM
AS SNAS TIN (STANNUM)
AS SO2AS SULPHITE/SULPHUR DIOXIDE
AS SO3AS SULPHUR TRIOXIDE
AS SO4AS SULPHATE
AS SRAS STRONTIUM
AS TAAS TANTALUM
AS TBAS TERBIUM
AS TEAS TELLURIUM
AS THAS THORIUM
AS TIAS TITANIUM
AS TLAS THALLIUM
AS TMAS THULIUM
AS UAS URANIUM
AS VAS VANADIUM
AS WAS TUNGSTEN (WOLFRAM)
AS YAS YTTRIUM
AS YBAS YTTERBIUM
AS ZNAS ZINC
AS ZRAS ZIRCONIUM
AT 25CAT 25 DEG. C
-CA(OH)2AS CALCIUM HYDROXIDE
PHENOLAS PHENOL

6.8. Result Structure Codes

Sorted by Abbreviation.

XML Result Structure Codes
XML and CPFResult Structure NameComponents contained in the Result Structure
Result Structure Abbreviation (result_structure and Struct)
AGSIMPLE AVERAGEAVERAGE
ANAVERAGE AND MINIMUMAVERAGE MINIMUM
ARAVERAGEAVERAGE NUMBER IN AVERAGE
AXAVERAGE AND MAXIMUMAVERAGE MAXIMUM
GRGEOMETRIC MEANGEOMETRIC MEAN NUMBER IN VALUE
DRDAILY REPORTINGAVERAGE NUMBER IN AVERAGE MAXIMUM MINIMUM
MNMINIMUMMINIMUM
MRMISA MONTHLY REPORTINGAVERAGE NUMBER IN AVERAGE MAXIMUM MINIMUM
MXMAXIMUMMAXIMUM
P2DAILY RESULTS 2VALUE-1 and TIME-1 VALUE-2 and TIME-2
P3DAILY RESULTS 3VALUE-1 and TIME-1 VALUE-2 and TIME-2 VALUE-3 and TIME-3
P6DAILY RESULTS 6VALUE-1 and TIME-1 VALUE-2 and TIME-2 VALUE-3 and TIME-3 VALUE-4 and TIME-4 VALUE-5 and TIME-5 VALUE-6 and TIME-6
PIMAXIMUM AND MINIMUMMAXIMUM MINIMUM
QTQUARTERLY TOTALSINGLE VALUE NUMBER IN VALUE
SISINGLE RESULTSINGLE VALUE
SNSINGLE RESULT AND NUMBER IN VALUESINGLE VALUE NUMBER IN VALUE
SRSINGLE RESULT AND RANGESINGLE VALUE MAXIMUM MINIMUM

6.9. Components Codes

Sorted by Abbreviation.

Components Codes
XML and CPFComponent NameComponent Description
Component Abbreviation (component_type and Type)
AVAVERAGEAV = SUM(VALUES)/NO
GMGEOMETRIC MEANNth ROOT OF THE PRODUCT OF N NUMBERS OF SAMPLES ( n naa a2 …1 )
MNMINIMUMSMALLEST VALUE
MXMAXIMUMLARGEST VALUE
NONUM. IN AVERAGENUMBER OF VALUES USED IN CALCN. OF AVERAGE
NVNUMBER IN VALUENUMBER OF VALUES RELATED TO RESULT
SMSINGLE VALUERESULT OF MEASUREMENT - NO STATISTICS APPLIED
T1TIME-1TIME WHEN SAMPLE-1 WAS TAKEN
T2TIME-2TIME WHEN SAMPLE-2 WAS TAKEN
T3TIME-3TIME WHEN SAMPLE-3 WAS TAKEN
T4TIME-4TIME WHEN SAMPLE-4 WAS TAKEN
T5TIME-5TIME WHEN SAMPLE-5 WAS TAKEN
T6TIME-6TIME WHEN SAMPLE-6 WAS TAKEN
V1SAMPLE-1VALUE OF FIRST SAMPLE FOR PX RESULT STRUCTURE
V2SAMPLE-2VALUE OF SECOND SAMPLE FOR PX RESULT STRUCTURE
V3SAMPLE-3VALUE OF THIRD SAMPLE FOR PX RESULT STRUCTURE
V4SAMPLE-4VALUE OF FOURTH SAMPLE FOR PX RESULT STRUCTURE
V5SAMPLE-5VALUE OF FIFTH SAMPLE FOR PX RESULT STRUCTURE
V6SAMPLE-6VALUE OF SIXTH SAMPLE FOR PX RESULT STRUCTURE

6.10. Remark Codes

Some Remark Codes cannot be used within an XML file format, since the XML file format reserves the characters " " as opening and closing characters for the various parts of the file. Alternative characters are provided in brackets for those Remark Codes.

Sorted by Remark Code.

XML Remark Codes
XMLRemark Code Name
Remark Code (remark_code_[1, 2 or 3])
!NO DATA WILL BE RECORDED: SEE TEXTUAL REPORT
!INNO DATA: INSUFFICIENT VOLUME DUE TO INSPECTION
!NMNO EFFLUENT - NO SAMPLE AVAILABLE
?LATE DATA: DATA NOT YET AVAILABLE : SEE TEXT
<(use "&lt;")ACTUAL RESULT LESS THAN RECORDED
<DL (use "&lt DL")VERY LOW-LEVEL RESULT; RECORDED VALUE =MEASURED AMOUNT <LMDL
<T (use "&lt T")TENTATIVE LOW-LEVEL RESULT; LMDL =< RECORDED VALUE <RMDL
<W (use "&lt W")NO MEASURABLE RESPONSE (ZERO): <RECORDED VALUE
> (use "&gt")ACTUAL AMOUNT PROBABLY GREATER THAN RECORDED
AAPPROXIMATE VALUE
AISAPPROXIMATE VALUE: INSUFFICIENT SAMPLE
ARATTACHED REPORT
BCSBYPASS - CONSTRUCTION/MAINTENANCE
BPOBYPASS - OTHER
DCLDISINFECTED, CHLORINE
DUVDISINFECTED, UV
EFEQUIPMENT FAILURE
IBINTERFERENCE: BACKGROUND
ICINTERFERENCE: COLOUR
IFNINFILTRATION /INFLOW
IMINTERFERENCE: SAMPLE MATRIX
ISINTERFERENCE SUSPECTED
MPMULTIPHASE SAMPLE: RESULT MAY BE SUSPECTED
NLNON-LETHAL - ALL ORGANISMS SURVIVED
OCDOVERCAPACITY - DRY WEATHER
OCWOVERCAPACITY - WET WEATHER
OEOPERATOR ERROR
OLDOLD: SAMPLE EXCEEDS MAXIMUM STORAGE TIME
POBYPASS, POWER OUTAGE
SDSAMPLE DUPLICATES DIFFER IN APPEARANCE
SIDSAMPLE IDENTIFICATION QUESTIONABLE
SIPSAMPLE IMPROPERLY PRESERVED

Example XML Coding for CPF Requirements (7.0)

Following are examples of XML coding that accommodate various commonly customized Company Profile File (CPF) requirements.

7.1. Example 1: Daily Sampling Results

The following example shows XML coding for two different parameters with daily monitoring frequencies one requires three samplings per day (pH) while the other requires a single sampling per day (RSP).

<submission imis_company_code="0009990003" ws_name="INDUSTRIAL TEST PLANT INC">
    <sample sample_date_time="20060607" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT # 
        1" dischg_sample_cd="" sample_comment=""> 
    <result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D"
        rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32101" 
        remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/>
    <result rpttime_name="DAILY" sis_imis_code="PH" parm_name="pH (-log H+ Concn)"
        unit_abbrev="NO DIM" rptas_abbrev="NOT APPL" result_structure="P3" component_type="V1" 
        result_value="7.1" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/>
    <result rpttime_name="DAILY" sis_imis_code="PH" parm_name="pH (-log H+ Concn)"
        unit_abbrev="NO DIM" rptas_abbrev="NOT APPL" result_structure="P3" component_type="T1" 
        result_value="07:00" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/>
    <result rpttime_name="DAILY" sis_imis_code="PH" parm_name="pH (-log H+ Concn)"
        unit_abbrev="NO DIM" rptas_abbrev="NOT APPL" result_structure="P3" component_type="V2" 
        result_value="7.2" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/> 
    <result rpttime_name="DAILY" sis_imis_code="PH" parm_name="pH (-log H+ Concn)" 
        unit_abbrev="NO DIM" rptas_abbrev="NOT APPL" result_structure="P3" component_type="T2" 
        result_value="10:00" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/> 
    <result rpttime_name="DAILY" sis_imis_code="PH" parm_name="pH (-log H+ Concn)"
        unit_abbrev="NO DIM" rptas_abbrev="NOT APPL" result_structure="P3" component_type="V3" 
        result_value="7.3" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/> 
    <result rpttime_name="DAILY" sis_imis_code="PH" parm_name="pH (-log H+ Concn)" 
        unit_abbrev="NO DIM" rptas_abbrev="NOT APPL" result_structure="P3" component_type="T3" 
        result_value="15:45" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/> 
    <result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate" 
        unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
        result_value="3.2" remark_code_1="< T" remark_code_2="" remark_code_3=" 
        result_comment="" imis_regulation_code_1="MC"/>
    </sample>
    <sample sample_date_time="20060608" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT # 
    	1" dischg_sample_cd="" sample_comment="">
    <result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D"
        rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="29876" 
        remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
    	imis_regulation_code_1="MC"/>
    <result rpttime_name="DAILY" sis_imis_code="PH" parm_name="pH (-log H+ Concn)" 
        unit_abbrev="NO DIM" rptas_abbrev="NOT APPL" result_structure="P3" component_type="V1" 
        result_value="7.0" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/>
    <result rpttime_name="DAILY" sis_imis_code="PH" parm_name="pH (-log H+ Concn)"
        unit_abbrev="NO DIM" rptas_abbrev="NOT APPL" result_structure="P3" component_type="T1" 
        result_value="07:00" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/>
    <result rpttime_name="DAILY" sis_imis_code="PH" parm_name="pH (-log H+ Concn)" 
        unit_abbrev="NO DIM" rptas_abbrev="NOT APPL" result_structure="P3" component_type="V2" 
        result_value="7.5" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/>
    <result rpttime_name="DAILY" sis_imis_code="PH" parm_name="pH (-log H+ Concn)"
         unit_abbrev="NO DIM" rptas_abbrev="NOT APPL" result_structure="P3" component_type="T2" 
         result_value="10:00" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
         imis_regulation_code_1="MC"/> 
    <result rpttime_name="DAILY" sis_imis_code="PH" parm_name="pH (-log H+ Concn)"
        unit_abbrev="NO DIM" rptas_abbrev="NOT APPL" result_structure="P3" component_type="V3" 
        result_value="7.1" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/>
    <result rpttime_name="DAILY" sis_imis_code="PH" parm_name="pH (-log H+ Concn)"
        unit_abbrev="NO DIM" rptas_abbrev="NOT APPL" result_structure="P3" component_type="T3" 
        result_value="15:45" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/>
	<result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate"
        unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
        result_value="4.7" remark_code_1="< T" remark_code_2="" remark_code_3="" 
    	result_comment="" imis_regulation_code_1="MC"/>
    </sample>
</submission> 

7.2. Example 2: Daily and Weekly Sampling Results

The following example shows XML coding for two different parameters, one (RSP) with daily sampling frequencies and the other (PBUT) with weekly sampling frequencies.

<submission imis_company_code="0009990003" ws_name="INDUSTRIAL TEST PLANT INC">
    <sample sample_date_time="20060607" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT # 
    	1" dischg_sample_cd="" sample_comment=""> 
    <result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D"
        rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32101" 
        remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/>
    <result rpttime_name="WEEKLY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D" 
        rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32101" 
        remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
    imis_regulation_code_1="MC"/> 
    <result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate"
        unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
        result_value="12" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/> 
    <result rpttime_name="WEEKLY" sis_imis_code="PBUT" parm_name="LEAD, UNFILTERED TOTAL"
    	unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
        result_value="2.9" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/>
    </sample>
    <sample sample_date_time="20060608" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT #
	1" dischg_sample_cd="" sample_comment=""> 
    <result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D"
        rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="30001" 
        remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
    	imis_regulation_code_1="MC"/>
    <result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate"
    	unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
    	result_value="14" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
    	imis_regulation_code_1="MC"/>
    </sample> 
    <sample sample_date_time="20060609" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT #
	1" dischg_sample_cd="" sample_comment=""> 
    <result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D"
        rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32901" 
        remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/> 
    <result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate" 
    	unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
        result_value="9.6" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/> 
    </sample> 
    <sample sample_date_time="20060610" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT # 
	1" dischg_sample_cd="" sample_comment=""> 
    <result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D" 
    	rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="31801" 
        remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	imis_regulation_code_1="MC"/> 
    <result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate"
    	unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
        result_value="36" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/> 
    </sample> 
    <sample sample_date_time="20060611" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT # 
	1" dischg_sample_cd="" sample_comment=""> 
    <result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D" 
    	rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32881" 
        remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	imis_regulation_code_1="MC"/> 
    <result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate" 
    	unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
        result_value="35" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/> 
    </sample> 
    <sample sample_date_time="20060612" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT # 
	1" dischg_sample_cd="" sample_comment=""> 
    <result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D" 
    	rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32007" 
        remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	imis_regulation_code_1="MC"/> 
    <result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate" 
    	unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
        result_value="31" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/> 
    </sample> 
    <sample sample_date_time="20060613" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT # 
	1" dischg_sample_cd="" sample_comment=""> 
    <result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D" 
    	rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="30031" 
        remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	imis_regulation_code_1="MC"/> 
    <result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate" 
    	unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
        result_value="3.4" remark_code_1="< T" remark_code_2="" remark_code_3="" 
	result_comment="" imis_regulation_code_1="MC"/> 
    </sample> 
    <sample sample_date_time="20060614" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT # 
	1" dischg_sample_cd="" sample_comment=""> 
    <result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D" 
    	rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32401" 
        remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	imis_regulation_code_1="MC"/> 
    <result rpttime_name="WEEKLY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D" 
    	rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32401" 
        remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	imis_regulation_code_1="MC"/> 
    <result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate" 
    	unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
        result_value="15" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/> 
    <result rpttime_name="WEEKLY" sis_imis_code="PBUT" parm_name="LEAD, UNFILTERED TOTAL" 
    	unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
        result_value="2.6" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/> 
    </sample> 
</submission> 

7.3. Example 3: Sample Results for Flow

The parameter Flow is required to be coded for each parameter that requires a loading calculation (concentration X flow), as well as if required by a legal instrument. In any given Sample, there may be multiple parameters with different monitoring frequencies. To accommodate this requirement, Flow should be coded for the each of these frequencies (i.e. daily, weekly, quarterly, etc.) for the corresponding day of the sample. Note that a sample that does not include a parameter that requires a loading calculation need not have the parameter Flow coded, unless otherwise required (such as by a Certificate of Approval / Environmental Compliance Approval).

Flow result values do not appear in the Data Entry screen if the only parameter included in an XML sample for that day is Flow, regardless of how many regulations are listed.

Following are examples of various scenarios involving different monitoring frequencies, and one example of no Flow required.

A. 
<submission imis_company_code="0009990003" ws_name="INDUSTRIAL TEST PLANT INC">
    <sample sample_date_time="20060607" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT #
	1" dischg_sample_cd="" sample_comment=""> 
    <result rpttime_name="THRICE WEEKLY" sis_imis_code="FTFLOW" parm_name="Flow" 
        unit_abbrev="M3/D" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
        result_value="32101" remark_code_1="" remark_code_2="" remark_code_3="" 
        result_comment="" imis_regulation_code_1="MC"/> 
    <result rpttime_name="MONTHLY" sis_imis_code="FTFLOW" parm_name="Flow"
        unit_abbrev="M3/D" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
        result_value="32101" remark_code_1="" remark_code_2="" remark_code_3="" 
        result_comment="" imis_regulation_code_1="MC"/>
    <result rpttime_name="WEEKLY" sis_imis_code="PH" parm_name="pH (-log H+ Concn)"
        unit_abbrev="NO DIM" rptas_abbrev="NOT APPL" result_structure="SI" component_type="V1" 
        result_value="7.1" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/>
    <result rpttime_name="THRICE WEEKLY" sis_imis_code="RSP" parm_name="Residue, Particulate" 
        unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
        result_value="3.2" remark_code_1="< T" remark_code_2="" remark_code_3=""
        result_comment="" imis_regulation_code_1="MC"/> 
    <result rpttime_name="MONTHLY" sis_imis_code="PBUT" parm_name="LEAD, UNFILTERED 
        TOTAL" unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" 
        component_type="SM" result_value="3.2" remark_code_1="< T" remark_code_2="" 
        remark_code_3="" result_comment="" imis_regulation_code_1="MC"/>
    </sample>
</submission>

B. 
<submission imis_company_code="0009990003" ws_name="INDUSTRIAL TEST PLANT INC">
    <sample sample_date_time="20060607" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT #
	1" dischg_sample_cd="" sample_comment=""> 
    <result rpttime_name="WEEKLY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D" 
        rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32101" 
        remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/> 
    <result rpttime_name="MONTHLY" sis_imis_code="FTFLOW" parm_name="Flow"
        unit_abbrev="M3/D" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
        result_value="32101" remark_code_1="" remark_code_2="" remark_code_3="" 
        result_comment="" imis_regulation_code_1="MC"/> 
    <result rpttime_name="WEEKLY" sis_imis_code="DOC" parm_name="CARBON, DISSOLVED 
        ORGANIC" unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI"
        component_type="V1" result_value="7.2" remark_code_1="" remark_code_2="" 
        remark_code_3="" result_comment="" imis_regulation_code_1="MC"/>
    <result rpttime_name="MONTHLY" sis_imis_code="ASUT" parm_name="ARSENIC, UNFILTERED
        TOTAL" unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" 
        component_type="SM" result_value="3.8" remark_code_1="< T" remark_code_2="" 
        remark_code_3="" result_comment="" imis_regulation_code_1="MC"/>
    </sample> 
</submission> 

C. 
<submission imis_company_code="0009990003" ws_name="INDUSTRIAL TEST PLANT INC">
    <sample sample_date_time="20060607" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT # 
	1" dischg_sample_cd="" sample_comment=""> 
    <result rpttime_name="MONTHLY" sis_imis_code="FTFLOW" parm_name="Flow"
        unit_abbrev="M3/D" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
        result_value="32101" remark_code_1="" remark_code_2="" remark_code_3="" 
        result_comment="" imis_regulation_code_1="MC"/> 
    <result rpttime_name="MONTHLY" sis_imis_code="ALUT" parm_name="ALUMINIUM, UNFILTERED 
        TOTAL" unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" 
        component_type="SM" result_value="4.8" remark_code_1="< T" remark_code_2="" 
        remark_code_3="" result_comment="" imis_regulation_code_1="MC"/> 
    </sample>
</submission> 

D. 
<submission imis_company_code="0009990003" ws_name="INDUSTRIAL TEST PLANT INC">
    <sample sample_date_time="20060607" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT # 
	1" dischg_sample_cd="" sample_comment=""> 
    <result rpttime_name="WEEKLY" sis_imis_code="PH" parm_name="pH (-log H+ Concn)" 
        unit_abbrev="NO DIM" rptas_abbrev="NOT APPL" result_structure="SI" component_type="V1" 
        result_value="7.1" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
        imis_regulation_code_1="MC"/> 
    </sample> 
</submission> 

7.4. Example 4: Multiple Control Points within a single XML file

A Sample (and its related Results) is an independent module that can be placed anywhere within the XML coding—dates and control points do not have to be in a particular sequence (i.e., chronological, numerical). However, for clarity, it is recommended that Samples are coded in a sequence that is most convenient to the discharger.

<submission imis_company_code="0009990003" ws_name="INDUSTRIAL TEST PLANT INC"> 
    <sample sample_date_time="20060607" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT 
	    # 1" dischg_sample_cd="" sample_comment=""> 
	<result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D" 
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32101" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/> 
	<result rpttime_name="WEEKLY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32101" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
	<result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate"
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="32" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
	<result rpttime_name="WEEKLY" sis_imis_code="PBUT" parm_name="LEAD, UNFILTERED TOTAL"
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="2.9" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/> 
    </sample>
    <sample sample_date_time="20060608" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT # 
	    1" dischg_sample_cd="" sample_comment=""> 
	<result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D" 
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="30001" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
	<result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate" 
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="3.7" remark_code_1="< T" remark_code_2="" remark_code_3="" 
	    result_comment="" imis_regulation_code_1="MC"/> 
    </sample>
    <sample sample_date_time="20060609" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT # 
	    1" dischg_sample_cd="" sample_comment=""> 
	<result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D" 
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32901" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
	<result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate" 
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="3.9" remark_code_1="< T" remark_code_2="" remark_code_3="" 
	    result_comment="" imis_regulation_code_1="MC"/> 
    </sample>
    <sample sample_date_time="20060610" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT # 
	    1" dischg_sample_cd="" sample_comment=""> 
	<result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D"
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="31801" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
	<result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate" 
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="3.6" remark_code_1="< T" remark_code_2="" remark_code_3=""
	    result_comment="" imis_regulation_code_1="MC"/> 
    </sample>
    <sample sample_date_time="20060611" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT # 
	    1" dischg_sample_cd="" sample_comment=""> 
	<result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D" 
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32881" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/> 
	<result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate"
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="3.5" remark_code_1="< T" remark_code_2="" remark_code_3=""
        result_comment="" imis_regulation_code_1="MC"/>
    </sample>
    <sample sample_date_time="20060612" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT #
	    1" dischg_sample_cd="" sample_comment=""> 
	<result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D"
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32007" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
	<result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate"
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="3.1" remark_code_1="< T" remark_code_2="" remark_code_3=""
	    result_comment="" imis_regulation_code_1="MC"/>
    </sample>
    <sample sample_date_time="20060613" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT # 
	    1" dischg_sample_cd="" sample_comment=""> 
	<result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D" 
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="30031" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
	<result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate"
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="34" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
    </sample> 
    <sample sample_date_time="20060614" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT #
	    1" dischg_sample_cd="" sample_comment=""> 
	<result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D" 
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32401" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/> 
	<result rpttime_name="WEEKLY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D"
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32401" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
	<result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate"
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="3.5" remark_code_1="< T" remark_code_2="" remark_code_3=""
	    result_comment="" imis_regulation_code_1="MC"/>
	<result rpttime_name="WEEKLY" sis_imis_code="PBUT" parm_name="LEAD, UNFILTERED TOTAL" 
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="2.6" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
    </sample>
    <sample sample_date_time="20060607" imis_cp_ext="0400" cp_name="WASTE WATER FROM UNIT
	    # 2" dischg_sample_cd="" sample_comment=""> 
	<result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D" 
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32101" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
	<result rpttime_name="WEEKLY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D"
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32101" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/> 
	<result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate"
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="3.2" remark_code_1="< T" remark_code_2="" remark_code_3=""
	    result_comment="" imis_regulation_code_1="MC"/>
	<result rpttime_name="WEEKLY" sis_imis_code="PBUT" parm_name="LEAD, UNFILTERED TOTAL" 
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="2.9" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
    </sample>
    <sample sample_date_time="20060608" imis_cp_ext="0400" cp_name="WASTE WATER FROM UNIT # 
	    2" dischg_sample_cd="" sample_comment=""> 
	<result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D" 
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="30001" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
	<result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate"
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="3.7" remark_code_1="< T" remark_code_2="" remark_code_3=""
	    result_comment="" imis_regulation_code_1="MC"/>
    </sample>
    <sample sample_date_time="20060609" imis_cp_ext="0400" cp_name="WASTE WATER FROM UNIT # 
	    2" dischg_sample_cd="" sample_comment=""> 
	<result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D"
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32901" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
	<result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate"
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="3.9" remark_code_1="< T" remark_code_2="" remark_code_3=""
	    result_comment="" imis_regulation_code_1="MC"/> 
    </sample>
    <sample sample_date_time="20060610" imis_cp_ext="0400" cp_name="WASTE WATER FROM UNIT # 
	    2" dischg_sample_cd="" sample_comment=""> 
	<result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D" 
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="31801" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
    <result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate"
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="3.6" remark_code_1="< T" remark_code_2="" remark_code_3=""
	    result_comment="" imis_regulation_code_1="MC"/> 
    </sample>
    <sample sample_date_time="20060611" imis_cp_ext="0400" cp_name="WASTE WATER FROM UNIT #
	    2" dischg_sample_cd="" sample_comment=""> 
	<result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D" 
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32881"
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/> 
	<result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate"
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="25" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
    </sample>
    <sample sample_date_time="20060612" imis_cp_ext="0400" cp_name="WASTE WATER FROM UNIT #
	    2" dischg_sample_cd="" sample_comment=""> 
	<result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D"
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32007" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
	<result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate"
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="3.1" remark_code_1="< T" remark_code_2="" remark_code_3=""
	    result_comment="" imis_regulation_code_1="MC"/>
    </sample>
    <sample sample_date_time="20060613" imis_cp_ext="0400" cp_name="WASTE WATER FROM UNIT #
	    2" dischg_sample_cd="" sample_comment=""> 
	<result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D"
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="30031" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
	<result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate"
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="34" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
    </sample>
    <sample sample_date_time="20060614" imis_cp_ext="0400" cp_name="WASTE WATER FROM UNIT # 
	    2" dischg_sample_cd="" sample_comment=""> 
	<result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D" 
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32401" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
	<result rpttime_name="WEEKLY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D"
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32401" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
	<result rpttime_name="DAILY" sis_imis_code="RSP" parm_name="Residue, Particulate"
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="35" remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/>
	<result rpttime_name="WEEKLY" sis_imis_code="PBUT" parm_name="LEAD, UNFILTERED TOTAL"
	    unit_abbrev="MG/L" rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" 
	    result_value="2.6" remark_code_1="< T" remark_code_2="" remark_code_3=""
        result_comment="" imis_regulation_code_1="MC"/>
    </sample>
</submission> 

7.5. Example 5: Multiple Regulations within a single Result

The Result may apply to more than one regulation. MEWS coding allows for up to 10 regulations to be assigned to one Result. However, currently MEWS only accepts 6 different types of regulations (see Section 6.3), so in practice up to 6 different regulations may be assigned to a result. A discharger should not code separate Results for different regulations if all other criteria in the Result is the same—duplicates of the same combination of codes (sis_imis_code; unit_abbrev; rpttime_name; rptas_abbrev; result_structure; and component_type) will result in an error.

Valid coding:

<submission imis_company_code="0009990003" ws_name="INDUSTRIAL TEST PLANT INC">
    <sample sample_date_time="20060607" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT #
	    1" dischg_sample_cd="" sample_comment=""> 
	<result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D"
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32101" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC" imis_regulation_code_2="CA"/>
    </sample>
</submission>

Invalid coding:

<submission imis_company_code="0009990003" ws_name="INDUSTRIAL TEST PLANT INC">
    <sample sample_date_time="20060607" imis_cp_ext="0100" cp_name="WASTE WATER FROM UNIT #
	    1" dischg_sample_cd="" sample_comment=""> 
	<result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D"
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32101" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="MC"/> 
	<result rpttime_name="DAILY" sis_imis_code="FTFLOW" parm_name="Flow" unit_abbrev="M3/D"
	    rptas_abbrev="NOT APPL" result_structure="SI" component_type="SM" result_value="32101" 
	    remark_code_1="" remark_code_2="" remark_code_3="" result_comment="" 
	    imis_regulation_code_1="CA"/>
    </sample>
</submission>