Day shift enters data in one sequence. Night shift prefers a different order. One operator likes seeing summaries; another finds them distracting. When everyone shares the same DataView layout, someone compromises. Operator-specific DataViews solve this by letting each person save their own customized version of the same data set.
Why personalize DataViews?
Operators have different habits, training, and preferences. Some read bench sheets top to bottom, others left to right. Some operators want to see all treatment stages at once; others prefer focusing on one section at a time. Forcing everyone into a single DataView layout slows down the team members whose workflow doesn’t match the default. Operator-specific DataViews respect individual work styles while keeping everyone in the same database, so data stays consistent even though screens look different.
How to create a personalized DataView
Start with an existing DataView that contains the parameters you need. Open it in Operator10 and customize it: reorder columns, change headers, adjust date range, enable or disable summaries, apply inverted display—whatever fits your workflow. When you’re satisfied, click File > Save As. Give the DataView a unique name that includes your identifier, like “Lab TSS – John” or “Daily Rounds – Night Shift.” Click Save. This creates a new DataView that only you use, leaving the original intact for everyone else.
Example: Two operators, two workflows
Operator A enters influent data first, then works through basins in numerical order, then logs effluent. Operator B prefers to enter all flow data first (influent, basins, effluent), then circle back for all TSS values, then all BOD values. They both need the same location parameters, but the column order should be different. Create two DataViews from the same parameter set: “Daily Entry – Operator A” with columns in process sequence, and “Daily Entry – Operator B” with columns grouped by parameter type. Both operators enter data faster because the screen matches how they think.
Save personalized views for different tasks
One operator might create three operator-specific DataViews for themselves: one for morning rounds with inverted display and no summaries, one for end-of-shift review with summaries enabled and standard display, and one for exporting data to engineers with a custom date range and specific column order. All three views pull from the same database, but each one is optimized for a different task in that operator’s day.
Share shortcuts for fast access
After creating an operator-specific DataView, drag it to the desktop to create a shortcut (see the desktop shortcuts blog post for details). Each operator can have their own folder of shortcuts on their workstation or in a shared folder with their name. When Operator A logs in, they open “Lab TSS – A” from their desktop. When Operator B logs in, they open “Lab TSS – B” from their desktop. Same data, different layouts, zero conflict.
Avoid clutter in the DataView list
If your team creates many operator-specific DataViews, the main DataView list in Operator10 can get long. Use clear, consistent naming conventions: include the operator’s initials or shift name, like “TSS – DayShift” or “Rounds – BJ” so everyone can find their own views quickly. Archive or delete old personalized views that are no longer in use. Some plants designate one or two “official” DataViews for new hires or temporary staff, while experienced operators maintain their own customized versions.
Personalized views don’t fragment data
All operator-specific DataViews point to the same database location parameters. If Operator A enters an influent TSS value of 250 mg/L on December 4, that value appears in every DataView that includes influent TSS, regardless of layout. The data is centralized; only the interface is personalized. This means supervisors can review data using their own DataView, operators can enter data using theirs, and reports pull the same validated values regardless of which view was used for entry.
Encourage experimentation
When operators know they can create and customize operator-specific DataViews without breaking anything or affecting their coworkers, they experiment more. They try inverted display, adjust column widths, remove summaries, add group headers—and they discover layouts that make their work faster. Plants that encourage this kind of personalization see higher adoption of Operator10 and less resistance to data entry tasks, because the software adapts to the operator instead of forcing the operator to adapt to the software.
Bottom line
No two operators work exactly alike. Operator-specific DataViews honor that reality by giving everyone the flexibility to customize their interface while keeping the entire team in the same reliable database. Data stays consistent, workflows get faster, and operators feel ownership over the tool they use every day.
Next Steps: Explore Operator10 DataView customization options →
