NetDMR doesn’t understand “Effluent Flow” or “BOD 5-day” as text. It uses numeric codes: 50050 for flow, 00310 for BOD. Electronic reporting codes in Operator10 translate your plant’s data into the state’s required format. Enter codes correctly, and uploads succeed. Enter wrong codes, and the state system rejects your submission.
Why codes matter
States use electronic reporting codes to standardize data across thousands of facilities. Every wastewater plant in the state reports BOD using code 00310, not “BOD,” “BOD5,” or “Biochemical Oxygen Demand.” This standardization allows automated processing, compliance tracking, and data aggregation. When you submit via NetDMR, the state system validates every code against your permit. Wrong codes mean rejection—the system doesn’t guess what you meant. Operator10 must use exact codes from your NetDMR copy of record.
Parameter store codes
Parameter store codes identify which pollutant or operational parameter you’re reporting. Common codes: 50050 (effluent flow), 00310 (BOD 5-day), 00530 (total suspended solids), 00400 (pH), 00610 (ammonia nitrogen), 00665 (phosphorus), 31616 (fecal coliform). Your NetDMR copy of record lists every parameter code for your permit. Enter these codes in Operator10’s Electronic Reporting section when setting up each location parameter on the NetDMR report.
Monitoring location codes
Monitoring location codes indicate where samples were collected. Code 1 typically means effluent (final discharge point), Code 2 might be influent (incoming wastewater), Code 3 could be an intermediate process point or secondary treatment. Your permit defines which monitoring locations exist at your facility and which code corresponds to each. Enter the monitoring location code in Operator10 for each parameter. If you report effluent BOD, use parameter code 00310 with monitoring location code 1.
Unit codes
Unit codes specify measurement units. Code 03 = million gallons per day (MGD), 19 = milligrams per liter (mg/L), 26 = pounds per day (lbs/day), 24 = kilograms per day (kg/day). NetDMR requires numeric unit codes, not text abbreviations. When setting up parameters in Operator10, select units from the dropdown menu—Operator10 displays both the unit name and code (e.g., “19 – mg/L”). The system automatically includes the correct unit code in the exported NetDMR file.
Frequency codes
Frequency codes indicate how often you sample. Code 999 = continuous (for flow meters or inline sensors), 3 = three times per week, 7 = daily, 1 = once per month, 4 = quarterly. Your permit specifies sampling frequency for each parameter. Enter the frequency code in Operator10. If you sample BOD three times per week, enter code 3. If the state changes your permit to require daily BOD sampling, update the frequency code to 7.
Sample type codes
Sample type codes specify how samples were collected. CP = composite (24-hour composite sample), GR = grab (single instant sample), TM = totalizer (cumulative reading like flow meters), ES = estimated (calculated or modeled value). Match sample type codes to your actual sampling methods. If you collect 24-hour composites for BOD, use CP. If you take grab samples for pH (since pH can’t be composited), use GR.
Season codes (when applicable)
Some permits have season codes for parameters with seasonal limits. If ammonia limits change in summer vs winter, the state assigns season code 1 for winter limits and season code 2 for summer limits (or similar—varies by state). Operator10 can handle seasonal limits if you set them up per the NetDMR copy of record. Some facilities create separate NetDMR reports for each season with corresponding season codes. Others adjust limits within one report based on month. Consult your copy of record to determine if season codes apply.
Notify codes (rarely used)
Notify codes are special flags for parameters you no longer monitor or discharge. If your permit once required chlorine residual reporting but you switched to UV disinfection, you might use a notify code to tell the state “this parameter no longer applies.” Most facilities don’t need notify codes, but they exist for edge cases. If your NetDMR copy of record shows a notify code, replicate it in Operator10 to prevent the state system from expecting data for inactive parameters.
Where to enter codes in Operator10
When setting up a NetDMR report in Operator10, open each location parameter (LP) definition. In the Electronic Reporting section, you’ll see fields for: Parameter Store Code (e.g., 00310), Monitoring Location Code (e.g., 1), Season Code (if applicable), Notify Code (if applicable). For columns (monthly average, daily max, etc.), select Unit Code from the dropdown (e.g., 19 for mg/L). For frequencies and sample types, enter the appropriate codes (e.g., 3/week = code 3, Composite = CP). Every code must match your NetDMR copy of record exactly.
Common code entry errors
Wrong parameter code: Entering 5005 instead of 50050 for flow. Solution: Copy-paste codes from NetDMR copy of record into Operator10.
Missing monitoring location: Forgetting to enter monitoring location code 1. Solution: Check every LP has a monitoring location code.
Incorrect units: Using code 19 (mg/L) when the permit requires 26 (lbs/day). Solution: Verify unit codes against copy of record, especially for loading limits.
Frequency mismatch: Setting continuous (999) when permit requires 3/week (3). Solution: Match frequency codes to permit requirements, not actual practice (if you sample daily but permit requires 3/week, use permit code).
Validate codes before going live
After entering all electronic reporting codes in Operator10, generate a test NetDMR file. Contact your state’s NetDMR coordinator and request a test account or temporary facility code for validation testing. Upload the test file to the NetDMR system. If codes are correct, the upload succeeds. If codes are wrong, the system returns specific error messages identifying which codes failed. Fix errors in Operator10, regenerate the file, and retest until uploads succeed without errors.
Why precision matters
Electronic systems don’t tolerate ambiguity. Electronic reporting codes are the language NetDMR speaks. Master the codes, and electronic reporting becomes routine. Ignore them, and you’ll fight upload failures every month.
Next Steps: Configure Operator10 NetDMR codes correctly →
