Paper bench sheets and mobile forms follow a logical sequence: influent first, then process units, then effluent. Operators read from left to right or top to bottom, recording values in that order. When the Operator10 DataView doesn’t match that sequence, data entry slows down because the operator has to hunt for the right column or row. Matching DataView column order to bench sheets eliminates that friction.
Why sequence matters
When a lab tech or operator enters data, they’re transferring values from one format (paper, clipboard, mobile screen) to another (Operator10 DataView). If the bench sheet lists TSS in the order Influent → Primary → Basins 1–7 → Effluent, but the DataView shows Basins 1–7 → Influent → Effluent → Primary, the operator has to skip around, losing their place and increasing the chance of entering a value in the wrong field. Column order alignment reduces cognitive load and speeds up entry by letting operators work in the same sequence they’re reading.
How to reorder DataView columns
Open your DataView in Operator10. Left-click any column header and hold down the mouse button. Drag the column left or right to the position you want. A vertical line appears as you drag, showing where the column will land when you release the mouse. Drop the column in place. Repeat for each column until the sequence matches your bench sheet. If you’re working with an inverted DataView (parameters as rows, dates as columns), the same drag-and-drop works for row labels—just drag rows up or down instead.
Start with a clear reference
Before you start reordering, grab a copy of your plant’s current bench sheet or mobile form. Lay it next to your monitor. Open the DataView you want to adjust. Compare the sequence on the bench sheet to the sequence in the DataView. Make a list of which columns need to move and where. This prevents you from dragging columns randomly and helps you complete the reorder in one session.
Common bench sheet sequences
Most plants follow predictable patterns. Influent parameters (flow, BOD, TSS, pH) come first because that’s where the process starts. Primary clarifier or headworks data comes next if your plant has those units. Aeration basins or treatment process units follow in numerical order (Basin 1, Basin 2, etc.). Effluent parameters come last. Secondary parameters like chemical feeds, sludge handling, or lab QC data might go at the end or in a separate DataView entirely. Match your DataView to whatever order your operators use in the field or lab.
Example: Lab TSS bench sheet
A lab tech’s TSS bench sheet might read: Influent → Primary Effluent → Aeration Basin 1 → Aeration Basin 2 → Aeration Basin 3 → Secondary Clarifier → Effluent. The default Operator10 DataView might have created location parameters in alphabetical order or grouped them by type, which doesn’t match the bench sheet flow. Reorder the columns to match the bench sheet sequence exactly. Now the tech reads the first value on the bench sheet, enters it in the first column of the DataView, reads the second value, enters it in the second column, and so on—no hunting, no confusion.
Combine with inverted display for best results
If you use inverted DataView display (dates on top, parameters on the side), reordering rows to match bench sheet sequence is even more powerful. The operator enters a date column from top to bottom, hitting Enter after each value. If the row order matches the bench sheet order, they never have to look up from the paper or mobile screen. Read, type, Enter, repeat. This is the fastest possible data entry workflow in Operator10.
Reordering doesn’t affect the database
Dragging columns or rows to rearrange their display order has zero impact on the database, other DataViews, reports, or charts. You’re only changing the visual sequence for this one DataView. The underlying location parameters stay the same. If another DataView or report shows parameters in a different order, that’s fine—each view is independent. Your lab TSS DataView can match the bench sheet while your monthly report DataView groups parameters by treatment stage. Both pull the same data; they just organize it differently on screen.
Test with operators
After reordering, ask the operators or lab techs who use that DataView to test it with real data entry. Watch where they pause or hesitate. If they’re still hunting for columns, adjust the sequence again. The goal is for them to enter data without thinking about the interface, so the DataView order should feel invisible—like they’re just transferring values from one list to an identical list.
Next Steps: Optimize your Operator10 DataViews for your team →
