Getting setup right saves months of confusion later. The biggest failure mode is simple: people attach logic to the same LP where operators type readings. That overwrites real measurements and makes audits painful. Treat results and inputs as different destinations. Create a clean “results” LP (e.g., “BOD Pounds”) and store the calculation there. When Operator10 formulas live on the correct LPs, raw data stays intact and your KPIs remain trustworthy.
Why placement matters
If a formula writes where humans also type, today’s math can replace yesterday’s lab number. Separate “calculated” LPs from “entered” LPs so you can reconcile any discrepancy quickly. This also helps when training new staff—inputs are where you type; results are where you read.
Build from the LP list
Open the destination LP and use Attach Formula → +. Writing from the LP list auto-attaches the logic to the right place and cuts mistakes. In Remarks, write the intent in plain English (what it does, units, and any rounding) so someone else can maintain it.
Name rules that prevent mistakes
Use clear words (e.g., “Final Effluent — BOD Pounds”). Avoid special characters (#, %, &). Consistent names speed up troubleshooting and help you spot mismatches at a glance.
Insert tokens the safe way
Always insert via the token picker so you get the exact [Location:Parameter] format. Hand-typing “effluent bod” looks fine but won’t resolve. The picker guarantees valid references and eliminates silent failures.
Troubleshoot before rollout
- Missing result? Check that the test date actually has inputs.
- Result appears on second click? Fix calc order so inputs run above dependents.
- Unit feels off? Confirm you referenced the correct parameter and unit.
With these habits, Operator10 formulas become readable, auditable, and reliable—no mystery math, no overwritten entries, and a faster path to clean reports.
Next Steps: Explore Operator10 Wastewater Solutions →
