What’s new

• The answer: the recommended action and the verdict first, then the cost of waiting a year and whether the well is in or near a failing band, the reasons with links to the evidence, the steps to take, and the five options with their expected lifetime cost. Raise a work order or ask Ask IQ about the well from the same card. Where nothing can be forecast the card says why: the well is out of service, it needs two tests, or a baseline is missing and which one.
• One number per fact: where the capacity index corrects the latest reading to the baseline rate, the diagnosis now quotes the same corrected figure and says so, so the card and the sentence beside it agree.
• The well section: the formation, casing, screens, pack and seal at true depth, the water levels from the latest test, and the pump at its setting — bowls per recorded stage, column, discharge head and motor, or the submersible pump and motor — drawn to one scale inside its casing. Sizes on record are drawn solid; anything not on record is drawn dashed at a typical proportion and says so. The column or drop-pipe size can now be entered on Edit well.
• Ask IQ opens on a briefing: the wells that need attention, this month on the utility schedule and the next act-by month, each with “ask about this”; starter questions by role; a “/” menu of commands; every figure in an answer carries its source, and every answer says how sure it is.
• The Budget’s year: each well’s months ahead with the act-by month and its cause, the fleet’s cost month by month and the year’s total with its range, what acting now would change, and a one-page brief for the board that prints on Letter paper.
• On a phone: wide tables and charts scroll inside their card with a swipe hint and the well’s name pinned, and the navigation wraps to two rows instead of cutting off its last item.

How it was proven Fifty-four checks on the answer card and its wording, including the reason given when nothing is forecast; the well-section drawing checked against ten deliberate tamperings on one well and eleven on another; every route replayed against the previous release with only the intended views changed; accessibility checks with no failing node on ninety-four route audits; no sideways page scroll on twenty-four routes at seven widths; the engine’s answers checked against its gate and every released file hashed on the live site against the build.

• Time-of-use, priced like the bill: Southern California Edison’s agricultural and pumping schedules — TOU-PA-2 and TOU-PA-3, Options D and E and their 5-to-8 p.m. variants — rate for rate, facilities and time-related demand included. The cheapest option for each meter from its own load; a meter over 500 kW is flagged, not priced.
• Pump or buy: the cost of each well’s next acre-foot against the water the district would otherwise buy, at its own price or a published default labeled as one, and next year’s budget by well and month from the district’s own metered months, with its range.
• The forecast: each well’s months ahead from a lifecycle model fitted to the district’s own history, and the act-by month — when a declining well no longer fits its budget outside the expensive hours — with its cause.
• Transmissivity on every tested well, from its strongest test, with the method and the range it is sure within; the change in aquifer loss and well loss since the first step test; and the share of flow by screened layer, labeled an indication. It appears on the well page and in the well report.
• Ask IQ: questions about any well answered in plain English by calling the platform’s own tools against the district’s record, every figure cited to the test, record, plan or document it came from, with its date. It is read-only, it answers with the asker’s own access, and every exchange is kept for the district. Included in every membership.

How it was proven Every rate in the tariff engine checked line by line against the text of the utility’s published schedules; the forecast and transmissivity on the demonstration wells equal to the engine’s own run; a forty-two-question acceptance set for Ask IQ — questions, commands and refusals — answered with every figure cited, its misses fixed and asked again; every released file hashed on the live site against the build.

• A closed month: what each well delivered against its own target (met, short or over), the fleet's percentage, the energy the acre-feet took at each well's own kilowatt-hours per acre-foot, and no schedule or "still owed" for a month that is over.
• A month ahead: the target, the acre-feet a day it takes, the weekday and weekend mix, and the schedule that meets it. The month in progress counts only the part of today that has passed.
• Where each well's volume comes from: SCADA first (the flowmeter's totalizer, else flow integrated with gaps booked as estimates), then meter readings logged by hand. A well with neither says so, and a tag map filled in with the district's own wells downloads for the integrator.
• Totalizers in gallons, thousands of gallons, million gallons, hundred cubic feet or acre-feet, and flow in gpm, MGD or cfs, are converted, never guessed; the hours either side of a month's edge are shared by time, so nothing falls between two months.
• A meter reading is withdrawn with a reason, not deleted: it stays on record, struck through, and counts toward nothing.
• Every figure in a sentence matches the figure in the table beside it, a whole-hour schedule no longer pumps a full extra hour for a few seconds of need, and the page prints on Letter paper with both weekday and weekend schedules.

How it was proven Seventy-five checks on the budget arithmetic; sixty-three on the budget tables and the SCADA volume function, including units, month edges and withdrawal; twenty-five in the browser across open, closed and planned months, on a phone and on paper; the database suite with no delete path left on any district record table.

• The month's line, green or red: each well's acre-feet pumped so far — from SCADA (totalizer, or flow with gaps estimated and labelled) or from meter readings logged by hand — against where the month should be today, not against the whole month on the 3rd.
• What it takes from here: the acre-feet still owed, spread over the days left, as hours a day at the well's own flow, held against the hours it may run. A well that cannot make it says by how many hours.
• When to run: hours placed in the cheapest tiers first as contiguous runs, within each well's limits on hours, rest, starts and shortest run; must-run windows kept. A well that would run into a demand-charged or dearer hour, or past its limit, hands that water to a well with spare cheap hours — and says what it saves.
• The district's tariff as data: periods from a preset (Southern California Edison agricultural and pumping, PG&E agricultural, or flat) or typed in, prices from the district's own bill. The month's scheduled cost is shown against the same hours run flat.
• Targets, run limits, the tariff and meter readings are edited on the tab, each by the people whose titles allow it. The schedule downloads as a file for the integrator; the platform never writes to a controller.
• The well condition report now prints everything the well page shows: critical speed with its verdict, well efficiency from the step test, the water over the bowls and the screen, the five construction checks, and the casing and borehole log with their sources. The two example reports on this site are printed from this release.
• A live specific capacity is withheld for the first hour of a pump run, while the level is still falling; and a banner tells every user when an update is planned, under way, or done.

How it was proven Twenty-eight test suites including fifty checks on the budget arithmetic and the fleet balance; two new database suites (the notice table, and the budget tables with the SCADA volume function); the tab, the report and the banner rendered in a real browser at desktop and phone widths.

• Construction integrity: five checks a hydrogeologist does once at design, run from the record every time the page opens — the part of every screen standing above the pumping level, hatched on the log and totaled; each casing string's collapse margin against the water pressure at its foot while the well is drawn down; the annular seal against DWR Bulletin 74-90; the filter pack against the slot; entrance velocity through the open area. Every tile names its basis and the field that would let it compute.
• The browser carries none of the engineering. The public key may compute for the demonstration district only; a district's data needs a signed-in session; the website's three published simulations run on typed what-if numbers and nothing else.
• Up to five duty points on the pump curve, with the system curve fitted through them and the crossing marked.
• Every well page makes one analysis call and draws every card from it; if the engine cannot be reached, each card says so instead of going blank.

How it was proven Twenty-six test suites and a leak check that refuses to package a bundle carrying any server-side sentence; every file on the live site hashed against the build after upload; the demonstration well, its control room and its board report rendered in a real browser with the engine reachable and with it refused.

• Water over the bowls and over the screen, live, with watch and alarm thresholds and the years to reach them at the static trend — stated as a straight line, never a forecast.
• Live specific capacity and wire-to-water efficiency against the last test, using a rest of four hours or more as the static reference.
• Pumped this week from the totalizer, with gaps estimated and labeled; run hours and starts.
• A control-room view of the card for a second monitor, re-read every minute while an agent is delivering, with the time of the last read printed where an operator glances.
• The casing table cites the document each string was read from, or says plainly that a person typed it; the log's footer says where the lithology came from.
• The efficiency baseline restarts at a pump replacement, so a new pump is never scored as an improvement of an old one; a static-level decline of 10 ft or more since baseline is flagged with its rate.
• The public demonstration district is Valle Verde — invented places and well numbers. Nothing in it is any district's record.

How it was proven Engine 1.4: 140 tests. The live-view arithmetic proven by 49 checks — the static reference, the rest rule, gap accounting, counter resets, projections refused where there is no downward trend.

• Well efficiency (Jacob, s = BQ + CQ²): efficiency when new versus now at the same rate, lost capacity priced as replacement water, and rehabilitation payback — with the specific-capacity diagram and the curve when new dotted beside it.
• The extractor reads a pump curve sheet's printed performance table and a step test's steps as tables, page by page; a confirmed curve replaces the points on record whole and cites its document.
• A pump replacement is recorded as one: the old pump keeps its history, the new one carries its curve, and the event cites the sheet.
• Re-file a document: a document filed on the wrong well moves in one audited act, its readings move with it, and every value it wrote onto the wrong well is put back field by field.
• A well's own power rate: twelve months of bills over twelve months of kWh, with the tariff and period it came from; the district blend remains the default and every dollar figure says which rate applied.

How it was proven Engine 1.3: 137 tests, including published case histories and a replacement-water example; 752 database assertions on the clean rebuild.

• Work orders on the well, with a CMMS-ready button. Connectors to the maintenance systems districts run come later; no maintenance-system credential is ever stored.
• The schematic draws the water column unmistakably from the recorded static level to total depth, each section at its own width, the well bottom capped and labeled.
• Documents open in a new tab, with a real fallback where a browser blocks it; the full-district export includes the document files.

How it was proven Fifty database assertions on work orders; every release verified on the live site file by file.