Operator10 generates visual DMR reports for printing and review. But electronic submission requires a different format—a machine-readable file the state’s NetDMR system can ingest and validate. Export NetDMR files from Operator10 creates this file automatically, translating your data into the exact format state systems expect.
Why export instead of print?
NetDMR eliminates manual DMR data entry. Instead of typing values from a printed report into the state’s web portal (slow, error-prone), you upload a file containing all data. The state system reads the file, validates codes and values, and populates the DMR automatically. Export NetDMR files from Operator10 generates this upload file. One click, and your month’s data is ready for electronic submission without retyping a single value.
How to export NetDMR files
After fetching data and generating your monthly NetDMR report in Operator10, click the Export button. Operator10 creates a file with a name like “NetDMR_[PermitNumber][Month][Year].txt” or similar. The file saves automatically to your configured storage path (the folder where Operator10 stores exported files, configured during software setup). Operator10 often provides a link button that opens File Explorer directly to the storage path, so you don’t have to navigate manually.
What’s in the exported file?
Open the exported file in Notepad (it’s plain text), and you’ll see rows of comma-separated or pipe-separated values. It looks cryptic—strings of numbers and codes—but each row represents one parameter on your DMR. The file includes: Permit Number (identifies your facility), Discharge Number (identifies which outfall if you have multiple), Parameter Code (e.g., 00310 for BOD), Monitoring Location Code (e.g., 1 for effluent), Date (month/year being reported), Values (monthly average, daily max, min), Unit Codes (19 for mg/L, 03 for MGD), Frequency and Sample Type Codes (3/week composite, continuous totalizer), and Exceedance Flags (if values exceeded permit limits).
File format matches state specifications
The state’s NetDMR system expects data in a specific format defined by EPA’s NetDMR technical specifications. Operator10’s export NetDMR files function follows these specifications exactly. Field order, delimiters, code formats, date formats—all match what the state expects. This is why entering electronic reporting codes correctly in Operator10 is critical: those codes populate the exported file, and the state system validates every code during upload.
Upload file to state NetDMR portal
Log into your state’s NetDMR portal (the web-based system where you submit DMRs). Navigate to “Create New DMR” or “Upload DMR Data.” The portal provides an Upload File option. Click it, browse to your Operator10 storage path, select the exported NetDMR file, and upload. The state system reads the file, validates codes, populates the DMR form with your data, and displays it for review. If validation passes, you review and submit. If validation fails, error messages identify which codes or values caused failure.
Review uploaded data before final submission
After uploading the file, the NetDMR portal displays your DMR populated with data from the file. Always review before final submission. Check: Do values match what you expect? Is flow 2.5 MGD as shown in Operator10? Is BOD 12 mg/L? Are all parameters present? Did any parameters fail to upload (blank cells in the portal)? If everything looks correct, submit. If errors exist, don’t submit—fix them in Operator10, regenerate and export the file, upload again, and re-review.
Common upload errors
Incorrect parameter code: State system rejects code 5005 because permit specifies 50050. Fix: Update code in Operator10, regenerate, export, re-upload.
Missing monitoring location code: File has blank monitoring location for BOD. Fix: Add monitoring location code 1 in Operator10, export, upload.
Wrong units: File uses mg/L (code 19) for flow instead of MGD (code 03). Fix: Change unit code in Operator10, export, upload.
Date format error: Rare, but if Operator10’s date format doesn’t match state expectations, upload fails. Contact AllMax support—they’ll fix format in a software update.
Save exported files for records
After successful submission, save the exported NetDMR file in a dedicated folder: “2025-01-NetDMR-Exported.txt,” “2025-02-NetDMR-Exported.txt,” etc. These files prove what you submitted and when. During audits or compliance reviews, exported files combined with NetDMR portal download copies provide complete documentation. Some plants keep exported files for 5+ years alongside other DMR records.
Test uploads with temporary credentials
Before submitting your first NetDMR file from Operator10, contact your state’s NetDMR coordinator and request test credentials or a temporary facility code. Upload test files to the test environment. If they validate successfully, you know Operator10 is configured correctly. If they fail, error messages guide corrections without risking real compliance submissions. Once tests pass consistently, switch to production credentials and submit real DMRs.
Automate monthly workflow
With export NetDMR files mastered, your monthly DMR workflow becomes: (1) Verify data in NetDMR data view, (2) Generate NetDMR report in Operator10, (3) Click Export, (4) Navigate to storage path, (5) Upload file to state portal, (6) Review and submit. Total time: 10-15 minutes. Compare to 60-90 minutes for manual data entry. Electronic submission via Operator10 saves hours monthly and eliminates transcription errors.
Why this feature transforms reporting
Before NetDMR integration, DMRs required generating reports, printing them, and manually retyping 50+ values into the state portal. Export NetDMR files eliminates retyping entirely, reducing DMR preparation from an hour to 15 minutes while dramatically improving accuracy. It’s the single biggest reporting efficiency gain in modern wastewater software.
Next Steps: Implement electronic DMR submission with Operator10 →
