Summary rows in Operator10 DataViews calculate totals, averages, minimums, or maximums for the visible date range. This is useful for reviewing data but distracting for data entry. When a lab tech is entering TSS values from a bench sheet, seeing a row that says “Sum: 1,250 mg/L” or “Avg: 178.5 mg/L” doesn’t help—it just adds visual noise. Removing summaries from data entry DataViews creates a cleaner screen that lets operators focus on entering values accurately.
Why remove summaries for data entry?
Data entry is a different task than data review. Entry requires focus on individual cells: read the bench sheet value, find the correct location parameter and date, type the value, move to the next one. Summary statistics are irrelevant during this process and can even be misleading—if you’re entering values for the current week, the summary updates with each entry, showing incomplete totals that don’t mean anything yet. Removing summaries clears the screen of distractions so operators see only the grid of cells they need to fill.
How to remove summaries from a DataView
Open your DataView in Operator10 and right-click anywhere in the grid to access Properties. Go to Column Properties. Click the first column header in the list, then hold Shift and click the last column header to select all columns at once. In the right panel, uncheck every box under Summary Type: Sum, Average, Min, Max, Count, etc. Click OK. The summary row(s) at the bottom (or side, if using inverted display) disappear. The DataView now shows only the data grid—no calculated summaries.
Summaries stay in other DataViews
Removing summaries from one DataView doesn’t affect other DataViews, reports, or the database. If you have a “Monthly Review” DataView that shows summaries for supervisors to check trends, that one keeps its summaries. If you have a “Lab TSS Entry” DataView with summaries removed, that’s fine—each view is independent. Operators use the clean entry view, supervisors use the summary view, and both pull from the same data.
When to keep summaries enabled
Not all DataViews should have summaries removed. Keep summaries enabled when the DataView is used for review, not entry. Monthly summary DataViews that show totals for each month across a year, chemical usage tracking views that calculate weekly or monthly costs, and flow analysis views that display average daily flow all benefit from summaries. The rule of thumb: if the DataView is for entering values, remove summaries; if it’s for reviewing or reporting values, keep summaries.
Combine with other clean-screen settings
Removing summaries is one of several settings that create a clean data entry interface. Combine it with 7-day period display (so operators see one week, not a full month), inverted display (so parameters run down the side and dates across the top), and custom column headers (so operators see “Basin 1” instead of “Aeration Basin 1 Solids TSS”). Together, these settings transform a cluttered spreadsheet-style DataView into a focused data entry tool that looks more like a digital bench sheet.
Test with operators
After removing summaries, ask the operators or lab techs who use that DataView whether the screen feels cleaner. Some operators like seeing real-time feedback as they enter values—watching the weekly total climb or the average shift. Others find it distracting and prefer a blank slate. If your team is split, create two versions: one with summaries for operators who want feedback, one without for operators who prefer simplicity. Use operator-specific DataViews(see that blog post) to give everyone the layout they like best.
Summaries still calculate behind the scenes
Even with summaries removed from the DataView display, Operator10 still calculates them for reports and charts. If your monthly report form pulls “Total Flow for October,” that value is computed from the database regardless of whether the DataView shows a summary row. Removing summaries only affects what operators see on screen during data entry—it doesn’t change how the database stores or calculates data.
Why this small change matters
Cognitive load increases when operators have to ignore irrelevant information. A data entry screen cluttered with summary statistics forces the operator to visually filter out the summaries and focus only on the empty cells. Removing that clutter eliminates the filtering step, so the operator’s attention goes straight to the task: enter the value, move to the next cell, repeat. Faster entry, fewer errors, less mental fatigue.
Next Steps: Optimize your Operator10 DataViews for data entry →
