Electronic DMR submission requires precision. One wrong parameter code, one mismatched monitoring location, and your upload fails. NetDMR copy of record is your blueprint—the official document from your state showing exactly what codes, parameters, and formats Operator10 must match for successful electronic reporting.
What is a NetDMR copy of record?
After submitting a DMR through your state’s NetDMR system, you can download a copy of record—a detailed PDF or document listing every parameter you reported, every code used, every permit limit, and every monitoring location. This official record shows what the state expects to see in your electronic submissions. When setting up Operator10’s NetDMR feature, this document is your reference guide. Every value in Operator10 must align with this copy of record, or uploads will fail validation.
Download copy of record from NetDMR system
Log into your state’s NetDMR portal (the web-based system where you currently submit DMRs manually). After submitting a DMR, look for “Download Copy of Record,” “View Submission,” or similar options. Download the file and save it. Ideally, download copies for an entire year (12 months) because some permits have seasonal variations—different limits in summer vs winter, quarterly parameters that only appear certain months, or annual metals testing. Reviewing all 12 months reveals these variations upfront.
What the copy of record shows
The NetDMR copy of record includes: Permit Number and Discharge Number (critical identifiers that link your submission to your facility), Parameter Store Codes (unique numeric codes for each parameter like 50050 for flow, 00310 for BOD), Monitoring Location Codes (usually 1, 2, or 3 indicating effluent, influent, or other sample points), Permit Limits (monthly average, daily max, etc.), Units (mg/L, MGD, lbs/day with unit codes like 19 for mg/L, 03 for MGD), Frequency and Sample Type (3/week, continuous, composite, grab), and Season Codes (if limits change by season). This complete picture ensures nothing is missed when building Operator10 reports.
Match Operator10 setup to copy of record
When creating a NetDMR report in Operator10, open the copy of record alongside the software. For each parameter on the copy of record, add the same parameter to Operator10. Enter the Parameter Store Code exactly as shown (50050, not 5005 or 50500). Enter the Monitoring Location Code (usually 1). Set Permit Limits to match monthly average and daily max values from the copy of record. Choose the correct Unit Code from Operator10’s dropdown, matching the numeric code on the copy of record. Enter Frequency (999 for continuous, 3 for 3/week, etc.) and Sample Type(TM for totalizer, CP for composite, GR for grab). Every field matters.
Identify seasonal variations
Compare copies of record from multiple months. If ammonia limits are 5.0 mg/L January–March but 2.5 mg/L April–October, you’ll need to account for this in Operator10. Some plants create separate NetDMR reports for different seasons with different permit limits. Others use Operator10’s date-based limit features. The copy of record reveals these variations that aren’t always obvious from permit documents alone, which might describe limits in regulatory language rather than showing month-by-month reality.
Verify quarterly and annual parameters
Some parameters only appear quarterly or annually: toxicity tests, metals scans, priority pollutants. Check copies of record from those months to see these parameters’ codes, limits, and frequencies. If you only look at monthly copies, you’ll miss them. When setting up Operator10, include these parameters with appropriate notes indicating they’re quarterly or annual, so operators don’t wonder why they’re on the report form.
Compare permit documents to copy of record
Permit documents (the official regulatory permit issued by EPA or state) sometimes differ from the NetDMR copy of record. Permits might have outdated limits if they haven’t been renewed recently, or they might list parameters that aren’t actually reported electronically. The copy of record is gospel—it reflects what the state’s NetDMR system actually expects. If your permit says one thing but the copy of record shows another, follow the copy of record and contact the state to clarify the discrepancy.
Use copy of record for troubleshooting
If Operator10 generates a NetDMR file and the upload to the state system fails, the error message often references codes or values. Open the copy of record and compare to what Operator10 exported. Is the parameter code correct? Is the monitoring location code right? Did you use the wrong unit code? The copy of record is the answer key for troubleshooting. Most upload failures stem from code mismatches, and the copy of record reveals exactly what the state expects.
Update Operator10 when permits change
When your facility receives a new permit or permit modification, download a fresh NetDMR copy of record after your first submission under the new permit. Compare it to your previous copies. Identify new parameters, changed limits, or removed parameters. Update your Operator10 NetDMR report to match. Without checking the copy of record, you might continue reporting old limits or miss new requirements, causing compliance issues or upload failures.
Keep copies for historical reference
Save NetDMR copies of record in a dedicated folder organized by month and year: “2024-01-NetDMR-CopyOfRecord.pdf,” “2024-02-NetDMR-CopyOfRecord.pdf,” etc. These serve as compliance documentation proving what you reported and when. During audits or regulatory reviews, copies of record show the state what they received from you. They’re also useful training materials for new staff learning the NetDMR setup process.
Why this document is essential
Setting up NetDMR in Operator10 without a copy of record is like building furniture without instructions—you might get close, but critical details will be wrong. The copy of record eliminates guesswork, ensures accuracy, and prevents upload failures. It’s the single most important document for successful electronic DMR reporting.
Next Steps: Set up NetDMR reporting in Operator10 →
