Work order systems
Built for pipes, valves and hydrants. A well becomes one dot on a map with maintenance tickets attached. No casing, no screened interval, no test history, no baseline.
Waterwell IQ holds the whole life of a water well in one record — construction, water levels, efficiency tests, rehabilitations and cost — and reads your paper archive into it. Then it tells you whether the pump is worn, the screen is fouled, or the aquifer is dropping.
The gap
Every asset platform a utility can buy inherits a map-first model where an asset is a point with attributes. A well is not a point. It is a depth-indexed vertical profile with a moving performance curve and a sixty-year event history — and that shape exists in no other product.
Built for pipes, valves and hydrants. A well becomes one dot on a map with maintenance tickets attached. No casing, no screened interval, no test history, no baseline.
They hold the water levels for your regulatory filings and nothing else. No construction record, no rehabilitation cost, no decision about what to do next.
The driller has the construction report. The consultant has the diagnosis. The pump contractor has the start-up sheet. The district that owns the asset has the worst copy of its own record.
The industry already made the distinction. AWWA benchmarking reports planned maintenance three ways — overall, linear, and vertical. Every system on the market was architected for linear assets. Waterwell IQ is the vertical asset system of record, and it computes that vertical ratio natively.
The signature capability
A well delivering less water at a higher energy cost could be a worn pump, a fouled screen, or an aquifer that is simply dropping. Pulling the pump costs tens of thousands. A rehabilitation costs six figures. A replacement well costs millions. Most districts are guessing.
Head deficit against the factory curve at normal amps, with the pumping level unchanged and specific capacity flat.
Check the lateral setting before you budget a rebuild. Semi-open impellers raised just forty thousandths of an inch above ideal can cost ten percent of your flow — and that is a shim, not a pump pull.
The pumping level deepens at the same flow, specific capacity declines, and sand or turbidity often rises with it.
A rising well-loss coefficient across successive step-drawdown tests is the cleanest quantitative evidence of fouling that exists. Waterwell IQ computes it from the tests you already run.
The static level falls, specific capacity stays stable, and the wells around you show the same trend.
This is a twenty-year capital planning question, not a maintenance ticket. Knowing the difference is the difference between a shim and a bond measure.
Why no one else does this. Every pump monitoring platform assumes a fixed system curve. A well pump lifts against a water level that moves seasonally, secularly and as the screen fouls — so its operating point migrates with no mechanical change at all. Point a generic platform at a municipal well and it will raise a false wear alarm every August.
The platform
A physical well outlives the operator who drilled it, the engineer who rehabbed it and probably the software vendor who first recorded it. Waterwell IQ is built on that assumption: append-only, fully exportable, and yours.
Casing, screen, filter pack, seal and lithology held as depth intervals with install and removal dates — so the schematic is generated from the record, and a date slider shows the well as it stood in any year.
Static and pumping levels, specific capacity, step-drawdown coefficients, sand and water quality — every measurement carrying its reference point, method and stated accuracy, because your regulator asks for all three.
Rehabilitate, repair or replace, argued from evidence: baseline-referenced trends, equivalent uniform annual cost, and a remaining-life model you can put in front of a board.
Component-level condition against the operating region the pump is actually running in, with the correct vibration limit applied for that region — not one blanket threshold for every asset.
The wells ranked by dollars per year recoverable, not by how many alarms they set off. The first screen a general manager sees is a priority list with money attached.
Getting the paper in
Nobody buys asset software because of the dashboard. They buy it because somebody finally offered to get the filing cabinet in. So that is what we do first — and for a pilot district, we do it for free.
Drag a folder in, forward an email to your district address, or let your contractor upload straight to the work order. Scanned, photographed or native — it all goes to the same place.
LAS geophysical logs, SCADA exports and CMMS feeds are read by code, not by a model. Exact, free, and incapable of inventing anything.
A 1976 driller’s log typed on a manual typewriter with handwritten margin notes gets read page by page. Every extracted value carries a confidence score and a citation back to the page and the spot on it.
Pumping level below static. Screens inside total depth. Annular seal against your county’s ordinance, not just the state minimum. A water level that jumps forty feet from last year is flagged, never accepted.
The source page sits beside the field, highlighted. Confident, validated values approve as a batch; anything uncertain is shown one at a time; anything that would overwrite an existing value needs a reason that is written to the audit log.
The engine recomputes, snapshots the result with its version stamp, and tells you only when a threshold has actually been crossed — in acre-feet and dollars, not in “anomaly detected”.
One rule we will not bend. The system never invents a measurement. If a value is not printed on the page, it stays empty and appears in your gap report. A record you cannot trace back to a document is not a record — it is a guess with a timestamp.
| Document | Method | What it fills in |
|---|---|---|
| Driller’s log / well completion report | Read | Lithology, casing, screen and seal intervals, licence, filing clock |
| E-log / geophysical survey | Parsed | LAS curve data and screen-siting evidence |
| Pump efficiency test | Read | One row per speed, wire-to-water efficiency, kWh per acre-foot, incentive eligibility |
| Step-drawdown / aquifer test | Read | Aquifer and well-loss coefficients, well efficiency, specific capacity |
| Installation / start-up sheet | Read | Pump and motor identity, lateral setting, checklist, signatures |
| Video and caliper survey | Read | Depth-tagged defects, encrustation, casing wall loss by depth |
| Rehabilitation report | Read | Event with pre and post specific capacity, method, cost, contractor |
| SCADA historian export | Parsed | Continuous operating points and run hours |
SCADA integration
An annual pump test is one photograph of a moving thing. The tags you already historise — flow, discharge pressure, level, motor kilowatts, run hours, starts — turn that photograph into a film, without adding a single sensor.
One-way, outbound, read-only. No exceptions. A small agent runs inside your perimeter and pushes out. Waterwell IQ never opens a connection into your control network and never writes a value to a tag. Water sector guidance requires operational technology connections to be denied by default, so we designed for that first rather than retrofitting it after your risk and resilience assessment asks.
A native adapter for the Ignition tag historian: point it at your well tag folders, map once, and history backfills from the day your historian started. Gateway-side, no new server.
OPC UA, Modbus TCP, MQTT with Sparkplug B, and scheduled CSV or historian export for the districts whose telemetry is a spreadsheet emailed on the first of the month. All of it lands in the same contract.
With continuous data the platform weights efficiency across the load points your pump actually runs at, instead of the one point a test truck happened to catch. A test truck cannot do that.
| Tag role | Units | Interval | What it unlocks |
|---|---|---|---|
| flow | gpm | 1–15 min | Operating point, production totals, region of operation |
| discharge_pressure | psi | 1–15 min | Total dynamic head with the water level |
| water_level | ft bgs | 15–60 min | Drawdown, specific capacity, the static-lift correction |
| motor_kw | kW | 1–15 min | Wire-to-water efficiency and energy intensity |
| run_state | bool | on change | Run hours and start counts for the life model |
| vfd_hz | Hz | 1–15 min | Speed normalisation so trends compare like with like |
| vibration | in/s rms | 1–60 min | Condition against the limit for the current operating region |
Find the money on one well
This is the same wire-to-water arithmetic the platform runs on every test it ingests. Put your worst well in and see what it is quietly costing.
Wire-to-water method. Energy intensity uses the exact constant 1.023 kWh per acre-foot per foot of head at 100% efficiency. This is an indication, not a pump test.
That number is per well, per year, every year. Multiply it by the wells in your fleet you have not tested since the last drought. Deferring one well replacement by five years, because a rehabilitation happened at the right moment, pays for the whole district’s subscription for a decade.
California
The regulatory load in California falls on the agency, not the vendor. So this is not a compliance product that promises to keep you legal — it is a record complete enough that the filings come out of it.
| Due | Filing | What comes out of the platform |
|---|---|---|
| Feb 1 | Probationary basin extraction report | Monthly extraction per well, well capacity, place and purpose of use — monthly granularity is in the schema, not bolted on. |
| Apr 1 | GSP annual report | Extraction by water use sector, measurement method and stated accuracy, storage change by principal aquifer, on the state templates. |
| Apr 1 | Adjudicated basin annual report | The same shape for Chino, Main San Gabriel, Mojave and the rest — plus quarterly production where the watermaster wants it. |
| Apr 1 | Electronic annual report | Source counts and types, standby sources, source metering and level monitoring, water supplied — pre-filled. |
| Oct 1 | Water loss audit | Source volumes with meter accuracy and last calibration alongside them, because a validator will ask for both. |
| Rolling | Well completion report | The sixty-day clock tracked as a deadline, with the contractor licence on the construction event. |
| Rolling | Public records request | A scoped export with a manifest and a logged reason for every redaction. |
Built on the water year. October to September, as a first-class period alongside calendar and fiscal years. It is the most common modelling mistake in groundwater software and it cannot be fixed later.
Your county’s rules, not just the state’s. Every county and water agency had to adopt a well ordinance meeting or exceeding the state standards, and many go stricter. Validation runs against a per-jurisdiction profile, so a Kern County well is checked against Kern County.
Trust
A platform holding well construction, water level and production data is one of the automated systems your risk and resilience assessment has to cover. We publish the package so it drops straight into your appendix.
Every table, every attachment, every audit entry exportable at any time in open formats. No lock-in, no hostage-taking on exit, and no training models on customer data — written into the contract, not just the marketing.
Tenant separation is enforced by the database engine itself, not by application code, so no application bug can cross the boundary. Independently reviewed, with isolation assertions running on every deployment.
Telemetry is a one-way outbound push from an agent inside your perimeter. There is no inbound path, no cloud-to-control-network session, and no ability to change a setpoint.
Write-once storage, cryptographic hashing of every document and an immutable audit trail — the conditions a district needs before a digital copy can lawfully become the record of authority.
Configurable per record class, with holds for pending litigation, claims and records requests that override every deletion rule. Nothing is ever hard-deleted by default.
Built to WCAG 2.1 AA from the first commit — maps navigable by keyboard, charts with data-table equivalents, nothing encoded in colour alone. Public agencies have a deadline and vendor applications get no exemption.
Membership
Your consultant, your driller, your pump contractor, your operators and your board all need to see the record. Charging by the seat is how a system of record ends up half empty — so we do not.
For drillers and pump contractors. File to the districts that invited you and keep a portfolio of your own work.
Banded, so the rate per well falls as the fleet grows. Historical backfill is included for pilot districts.
For engineering firms and energy assessors managing several client districts from one portfolio.
How districts actually buy this. Software is a professional service, not public works — qualifications-based, no low-bid requirement. Where a solicitation is needed, functional fit typically carries five times the weight of price. We will supply draft specification language, a sole-source justification package, and cooperative purchasing paths so your general manager can execute without a six-month procurement.
Start here
Send a driller’s log, an efficiency test and a start-up sheet for one well. We will read them into a live record and show you the score, the trend and the money — on your own data, in your own units, before you commit to anything.
Prefer email? hello@borelogix.com