From the meter to the customer. Connected systems. Smarter decisions.
ADMX sits on top of the AMI, billing and ERP systems you already run. It catches exceptions 30 days before the bill read, protects the life of your meters, and helps you keep the return you planned for.
You bought smart meters, but you didn't get a smart system. Municipalities invest in AMI to find leaks, track non-revenue water and justify the loans behind their capital projects. But most AMI systems are built around the meter, not the operator. Why water is different.
You have 24/7 reads, but you still wait a month to learn the health of your system.
Problems surface when the bill read runs, so the corrected bill goes out four to five days late.
Even a few percent of uncaught anomalies can skew billing estimates, so customers end up over- or undercharged.
You can see one meter at a time. You can't see your whole system.
Manufacturers kept your operational data behind an upsell. It's your data, and you already paid for it.
A 15-year system can fail in five when it's configured wrong or changed by its manufacturer.
Source: WRF Smart Metering Playbook, Survey Data (Project 5261). See what it means for your system.
Most billing departments pull meter reads once a month, one billing route at a time. ADMX uses the 24/7 data in between, so your team can check a whole route before the bill read ever runs.
Illustration of one billing cycle. Timing shown is typical, not a specific utility.
From the first AMI alarm to the final management report, the same unique ID follows the meter through GIS, CIS, work orders, inventory, the field and billing.
“I might be able to have a lunch and make it home for dinner with my wife.”
An operator, when Jane Story asked what a daily exception report would do for himLook up any of 2,706 Texas water systems. See apparent and real losses since 2015, and how you compare with similar-size systems.
Open the explorer Integration builderPick your system types and software. Get a saved list of every integration and public data source to plan for, with links to each.
Build your listSecure, read-only connections move the data so nobody has to re-key it.
One master record links every system's own ID for the same meter, customer, place or asset.
Together they let your stakeholders connect their systems, work more efficiently, reduce costs and serve customers better: bills on time, fewer truck rolls and asset history that is never lost.
ADMX employees onboard our proprietary platform onto your existing AMI infrastructure, creating one cohesive view of the systems you already run.
Data scientists and a designated change-management account manager ensure data integrity, from the meter to the bill, as your people and processes change.
A fixed-fee activation, then a monthly subscription per meter, per month, for the deployment and continued operation of the live system.
ADMX helps your team prove read rates and acceptance, trace every failure to its source, and leave the owner supported after handover. Explore published AMI contracts and open pursuits in the Opportunity Atlas.
We run three years of your meter data against local weather to see whether your system follows its environment. If anomalous data has crept in, the skew shows, and we show you how to correct your billing estimates.
ADMX sits on top of your IT and OT environment. Your cybersecurity stays in place and your data stays where it lives. ADMX pulls only what each system-wide analysis needs. It keeps its own cases, evidence and analysis, not a copy of your systems.
Your departments run separate systems that don't talk to each other. ADMX connects them through APIs and unique identifiers, and turns them into one operational picture.
Your core systems carry water usage to revenue. Your enterprise systems keep the utility running around them. ADMX connects both and adds the insight layer on top.
Turn data into actionable information.
The meter-to-cash chain, working together through secure APIs and integrations.
Each core system links to the enterprise systems named on its card, below.
Shared across the utility to improve efficiency, service and asset life.
Two ideas make a connected utility work. APIs move the information between systems. Unique identifiers make sure every system is talking about the same meter, customer, location or asset.
API = how systems communicate.
UID = how systems know exactly which thing they're talking about.
Each system keeps its own terms. ADMX links them through master IDs, so every record traces back to where it lives.
EP 51207 · 64021877MTR-64021877 / CH130-11872 · SP 7730418WM-0418A-MTR-20931ADMX-0418One crosswalk links each system's own ID. Nobody re-keys anything, and every system keeps the IDs it already uses.
Example records for illustration.
Account UID 847291Account UID 552118Same name, different customers. The UID keeps each record separate, so the right person gets the right bill and the right crew visit.
History of 123 Main St.: lostHistory of 123 Main St.: keptFor years the industry habit was to replace the meter ID at every change-out. Linking by premise and service point keeps years of usage history intact.
Follow a single failed meter through every system it touches. ADMX carries the same record from the first alarm to the verified outcome. ADMX brings the evidence to each step; your people make every decision.
The head-end reports missing reads and a possible leak flag for endpoint EP 51207.
The source system defines what the event means. A missing read alone is not proof of a leak.
Example records for illustration.
ADMX is in active development. Capabilities describe the product as designed, and items marked Roadmap come later. We confirm exactly what is available for your systems during the free assessment.
Watches 24/7 reads between bill cycles, so exceptions get fixed before the bill read instead of after it.
A morning list of communication-infrastructure exceptions that could cause a bill-read problem in 30 days.
Plans crew work by route ahead of the bill cycle, so crews spend less time on emergencies.
Looks forward across the system, not just back at history, to find leaks and losses earlier.
Uses pressure, flow and consumption data most water systems haven't touched yet. Shows leaks across the system and the impact of large users.
Compares consumption with local weather over time to expose skewed data and wrong peak months.
Stops improper reads from reaching billing. Correct bills go out on time.
Manages the handoff from meter to head-end to billing, so one clean data chain runs from the field to the invoice.
Groups customers by usage pattern once a year of data is in, for better conservation targeting and service.
Tracks battery drain, read frequency and endpoint health, so a 15-year system lasts 15 years.
Keeps a premise's history through every meter, register, brass and endpoint change.
Uses system-wide data to set capital improvement priorities, so spending goes where the data shows need.
Six more modules connect your data to the Texas public record. See Public Data & Funding.
Everything happening in a water system should track local conditions. ADMX leads with weather: its own purpose-built API pulls National Weather Service data for any service area, wherever ADMX runs, and builds the local record over time. Put meter data next to the weather, and anomalous data that is overstating or understating what's really happening shows up fast.
Reading local conditions is standard practice in the oil industry, where Jane Story learned to read the “microeconomics” of an area. ADMX brings that discipline to water, with weather normalization built in from day one.
A Texas city's rate study put its peak month in April. Anyone who has lived in Texas knows the peak is July through September. Skewed data had crept in over time. That is the kind of skew a three-year run against weather data is built to show.
Changing out a meter, register or endpoint can create an odd reading. If those exceptions aren't managed, improper reads flow straight into billing. Early AMI adopters learned this the hard way. ADMX verifies the whole chain.
Including read frequency and battery settings that protect design life.
Endpoints and collectors checked so signals actually arrive.
The handoff that most deployments never verify.
Which natural events need an exception, and how each ties into billing.
For years the industry standard was to replace the meter ID with the new meter's serial number at every change-out. That one habit wipes out the history of the premise. ADMX helps your team set up unique identifiers (UIDs) and component tracking so history survives every work order.
The meter's casing. On some meters you can change the register and keep the brass in place.
The dial or face that shows the numbers and the reading. Sometimes built as one unit with the meter.
The communication point that sends the meter's information through the network.
Operators have been told for years that the data is too technical for them. That isn't true. Most reports are built for distributors or technologists. ADMX reports are built for the people who run the system.
Operators know their system. Show one a meter ID and they'll say, “That's the milk factory.” A technologist sees only a number. ADMX puts that field knowledge at the center, and sets up every report around the decisions operators make each day.
Our proof-of-concept work started simply. We gave operators reports of their own data, set up the way they read them. Their reaction: “This is game changing.” The playbook reports the same lesson from Moulton Niguel Water District in California: experienced field crews interpreting data anomalies made resolution faster (Final Report, p. 81).
“If it was configured for you, I have no doubt you'd be able to figure it out.”
Jane Story, co-founderEvery morning, ADMX lists the communication and meter exceptions that could cause a problem at the next bill read. Your team has 30 days to fix them, a route at a time.
| Meter / endpoint | Exception | Status |
|---|---|---|
| EP 51207 | Endpoint battery draining fast | Schedule |
| R14-1130 | No reads for 3 days | Inspect |
| R15-0417 | Register swapped, history not linked | Fix UID |
| Collector C-06 | Signals sent, data not arriving | Inspect |
| R17-0093 | Continuous flow overnight | Crew assigned |
We've seen half of an AMI system go down within days. We've seen batteries set to read so often that a 15-year system died in five. And we've seen manufacturer “enhancements” wipe out features a utility or municipality had already paid for. ADMX stands on the owner's side.
Settings that protect the full design life of every endpoint. Battery life was the top meter specification in the WRF Smart Metering Playbook survey, named by 43 of 55 utilities, and the Final Report calls it the top hardware-related concern.
Configured so meter signals actually reach you, without buying extra hardware.
Checked for lost functionality before they cost you the back half of your investment.
What gets installed is verified against what was specified, all the way through to billing.
Where ADMX fits: battery life typically defines the overall asset life of a smart meter, and frequent transmissions cut it to 8–12 years. The playbook advises utilities to monitor actual battery performance rather than rely on vendor assurances, and to run a warranty monitoring and enforcement program. ADMX watches read frequency and battery drain on every endpoint, and documents the evidence a warranty claim needs.
Expected battery life ranges. Source: WRF Smart Metering Playbook, Final Report (Project 5261, 2026), p. 41; see also pp. 40, 42.
Texas water and wastewater systems operate under TCEQ rules in Title 30 of the Texas Administrative Code. Retail public utilities file water loss audits with TWDB, every year for those with more than 3,300 connections or TWDB financial assistance and every five years for the rest (31 TAC §358.6). The state publishes a great deal of this record. ADMX lines that public record up with your own operational data. You can explain changes in your numbers, find reporting gaps, and reuse your evidence in funding applications.
| Module | What it does | What you get | Guardrail |
|---|---|---|---|
| Wholesale-flow & boundary reconciliation | Uses TWDB buyer/seller, water-use and service-boundary data to flag when an apparent change in water loss may line up with wholesale purchases or sales, boundary changes, connection counts or population changes. | Know whether a loss trend is real or a product of how it was reported. | Flags possible explanations for review. Doesn't conclude. |
| Regulatory & operational evidence correlation | Links public water system compliance and monitoring context to your own incident and work timeline. | One timeline of what happened in the field and what showed up in the compliance record. | Correlation is never treated as proof that an asset caused a violation. |
| Funding evidence reuse | Maps your line material and age, break and repair work orders, estimated water savings, outage and pressure evidence, and asset-management status to TWDB application fields. | Traceable evidence packets, ready for funding applications. | Evidence packets only. ADMX never scores or predicts awards. |
| Environmental covariates | Tests whether rainfall, drought, source water, aquifer and geology, or land cover actually improve a specific model. | Outside data used only where it measurably helps. | Checks missing data, scale, confounding and out-of-sample accuracy first. No causal claims from map overlays. |
| Public/utility identifier reconciliation | Maps PWS IDs, TWDB entity and water-user-group identifiers, districts and service areas to your own GIS, service and asset IDs. | One crosswalk between the state's identifiers and yours. | Human review, a match-confidence score, effective dates and the source of every match. |
| Data-quality learning | Compares the event counts you track yourself with your TWDB water-loss audit summaries. | Finds where definitions, periods, boundaries or data handling don't line up. | Separates true discrepancies from acceptable differences in method. |
ADMX organizes systems, records and evidence by the Title 30 Texas Administrative Code (30 TAC) chapter that governs them, from public drinking water under Chapter 290 to domestic wastewater under Chapter 217. Your staff, auditors and engineers see the same structure they already work in.
| System type | Program | Governing 30 TAC rules |
|---|---|---|
| Drinking water: sources & wells | Public drinking water | §290.41 Water Sources §288.2 Water Conservation Plans for Municipal Uses by Public Water Suppliers Ch. 30, Subch. K Public Water System Operators and Operations Companies |
| Drinking water: treatment plant | Public drinking water | §290.42 Water Treatment §290.111 Surface Water Treatment Ch. 290, Subch. F Drinking Water Standards Governing Drinking Water Quality and Reporting Requirements for Public Water Systems Ch. 30, Subch. K Public Water System Operators and Operations Companies |
| Drinking water: storage tanks | Public drinking water | §290.43 Water Storage §290.46 Minimum Acceptable Operating Practices for Public Drinking Water Systems Ch. 30, Subch. K Public Water System Operators and Operations Companies |
| Drinking water: distribution | Public drinking water | §290.44 Water Distribution §290.46 Minimum Acceptable Operating Practices for Public Drinking Water Systems §290.117 Regulation of Lead and Copper Ch. 290, Subch. H Consumer Confidence Reports §288.2 Water Conservation Plans for Municipal Uses by Public Water Suppliers Ch. 288, Subch. B Drought Contingency Plans Ch. 30, Subch. K Public Water System Operators and Operations Companies |
| Wastewater collection (sewer) | Domestic wastewater | Ch. 217, Subch. C Conventional Collection Systems Ch. 217, Subch. D Alternative Collection Systems Ch. 319, Subch. C Public Notice of Spills or Accidental Discharges from Wastewater Facilities Owned or Operated by Local Governments Ch. 30, Subch. J Wastewater Operators and Operations Companies |
| Wastewater treatment plant | Domestic wastewater | Ch. 217, Subch. B Treatment Facility Design Requirements Ch. 217 Design Criteria for Domestic Wastewater Systems Ch. 309 Domestic Wastewater Effluent Limitation and Plant Siting §319.1 Monitoring and Reporting Requirements Ch. 305 Consolidated Permits Ch. 312 Sludge Use, Disposal, and Transportation Ch. 30, Subch. J Wastewater Operators and Operations Companies |
| On-site sewage facilities | Domestic wastewater | Ch. 285 On-Site Sewage Facilities |
| Reclaimed water | Reuse | Ch. 210 Use of Reclaimed Water |
| Industrial water & pretreatment | Industrial | Ch. 315 Pretreatment Regulations for Existing and New Sources of Pollution §288.3 Water Conservation Plans for Industrial or Mining Use Ch. 210, Subch. E Special Requirements for Use of Industrial Reclaimed Water Ch. 305 Consolidated Permits |
| Wholesale supply & transmission | Supply | §288.5 Water Conservation Plans for Wholesale Water Suppliers Ch. 291, Subch. I Wholesale Water Petitions Ch. 297, Subch. I Conveying Stored Water Ch. 297, Subch. J Water Supply Contracts and Amendments §290.44 Water Distribution |
| Reservoirs, dams & raw water | Supply | Ch. 299 Dams and Reservoirs Ch. 297 Water Rights, Substantive Ch. 307 Texas Surface Water Quality Standards |
| Irrigation (agricultural & landscape) | Irrigation | §288.4 Water Conservation Plans for Agricultural Use Ch. 297 Water Rights, Substantive Ch. 344 Landscape Irrigation Ch. 30, Subch. D Landscape Irrigators, Irrigation Technicians, and Irrigation Inspectors |
| Retail, wholesale & irrigation suppliers | Conservation & drought | Ch. 288, Subch. B Drought Contingency Plans |
| Water districts | Districts | Ch. 293 Water Districts |
Chapter and section titles as published in the TCEQ rules index and checked against the rule text on 12 October 2026. Links open the Cornell Legal Information Institute copy of the rule. Citations help organize records; they are not legal or compliance advice, and the utility remains responsible for compliance.
Every value ADMX shows from a public source carries its source, the agency's own as-of date, its review status and any caveats the agency attached.
| Source | Publisher | Access | What ADMX uses it for | Known limits |
|---|---|---|---|---|
| Water Loss Dashboard & audit data | Texas Water Development Board | Dashboard, Excel downloads | Loss trends, audit reconciliation | Annual, system-level audits; no leak locations |
| Water Service Boundary Viewer | Texas Water Development Board | Map viewer, CSV and Shapefile | Service areas, boundary changes | Boundaries are informational; edits need a utility sign-in |
| SARA report catalog | Texas Water Development Board | Report catalog (some reports require login) | Water use, population and demand projections | Some reports need a utility login |
| Mapping data services | Texas Water Development Board | ArcGIS services, Shapefiles | Aquifer and planning layers | Planning layers, not distribution-asset inventories |
| Texas Drinking Water Viewer | Texas Commission on Environmental Quality | Search by water system ID | Compliance and monitoring context | No bulk download; may be stale or incomplete |
| Raw datasets | Texas Commission on Environmental Quality | Excel, ASCII and Shapefile downloads | Facility and compliance records | Update cadence varies by file |
| Service Line Inventory | U.S. EPA (SDWIS) | Dashboard with data dictionary | Lead, galvanized, non-lead and unknown service lines | Aggregated counts, not addresses |
| Public weather API | NOAA National Weather Service | REST API | Local weather for normalized analysis | Observations can be delayed by quality control |
| Climate Data Online | NOAA NCEI | REST API (token) | Historical climate for the 3-year assessment | Token required; rate limits and station gaps |
| Storm Events Database | NOAA NCEI | Search and bulk CSV | Storm context for unusual readings | Reporting thresholds vary by event type |
| National Risk Index | FEMA | Interactive map, documentation | Hazard context for capital planning | Community-scale, not asset-level |
| Earthquake catalogs | TexNet (UT Bureau of Economic Geology), USGS | ArcGIS service, FDSN REST API | Seismic covariates, tested before use | Preliminary and reviewed events carry different certainty |
| Recalls API | U.S. Consumer Product Safety Commission | REST API, weekly CSV | Flags installed or stocked products named in a recall | Consumer products only; matches need human review |
| NSF/ANSI 61 listings | NSF (private certifier) | Search listings | Certification status of drinking-water components | A certification reference, not a recall feed |
Public data adds context and corroboration. It never replaces your own records, and a match in time or place is a reason to review, not proof of cause. ADMX is not affiliated with or endorsed by these agencies. Agency caveats, such as undercount warnings or preliminary status, are carried through unchanged.
ADMX is a software product. Many vendors hand over software and leave: you can watch your data flow, but nobody helps you act on it. Forward-deployed engineers onboard ADMX's proprietary platform onto your existing AMI infrastructure, creating one cohesive view. Data scientists and a designated change-management account manager keep your data right and your team ready, long after go-live.
In our experience, most AMI rollouts are delivered by meter distributors. They install the new meter and they're done. Nobody walks through how billing and operations will change once 24/7 data starts flowing. We do.
The first year protects the return you planned when you bought the meters. After about a year of data, system-wide patterns become visible, and that's where the next level of return comes from.
Your data against local weather, to find skew and estimate errors.
Forward-deployed engineers onboard ADMX onto your head-end, MDMS, billing and ERP, creating one cohesive view. Your data stays where it is.
ADMX data scientists set up UIDs and component tracking, and check the meter-to-bill chain and exception rules.
Your designated change-management account manager moves the team from “check the meter once a month” to working with 24/7 data.
Configuration, billing accuracy and asset life protected.
Water loss, customer archetypes, conservation, predictive maintenance and capital planning.
An ongoing relationship, not a project that ends at handoff.
The Water Research Foundation's playbook advises utilities to consider a dedicated change management and communications manager on every AMR or AMI project, and partners who can carry data management and integration. ADMX builds both into the subscription.
ADMX employees who work inside your environment. They onboard our proprietary platform onto your head-end, MDMS, CIS, GIS, work management and ERP, map every ID, and stay until the live system runs and your data is trusted.
They own the crosswalks, validation and exception rules, and weather normalization. They check that what is installed flows correctly from meter to head-end to billing, and that each exception is caught before it reaches a bill.
Your designated point of contact. They keep stakeholders aligned, run training and feedback, and make sure data integrity holds as people, processes and vendors change.
Define scope and objectives, interview stakeholders and staff, gauge readiness, and plan the transition of every workflow that changes.
Train staff and users, engage champions, and gather feedback during onboarding so roadblocks are cleared early.
Correct remaining gaps, review outcomes against objectives, document lessons learned and recognize the team's wins.
Phases follow the change management framework in the WRF Smart Metering Playbook, Final Report (Section 2.8, pp. 88–89).
A report-and-leave model studies your systems, writes recommendations and walks away. ADMX forward-deployed engineers are ADMX employees. They work inside your environment, onboarding and deploying the software until it is running and your data is trusted.
Reading the Water Research Foundation's Smart Metering Playbook, co-founder Forrest Hester wrote down three questions every AMI owner should be able to answer about the platform they choose. These are ADMX's answers.
“Every direct and most indirect variables that are developed can be measured, managed, and reported on.”
Forrest Hester, co-founder
Can it trace an AMI failure to its source, identify the responsible party, and produce evidence that enforces contractual service commitments?
Yes. An AMI system has many failure points: the meter and register, the endpoint, the collector network, the head-end, the MDMS and the hand-off to billing. Each needs its own root-cause tactic. ADMX carries one record across all of them, with the same unique ID from the first alarm to the verified outcome, so the failure point, the responsible party and the timeline are documented in a form a service-level or warranty claim can stand on. Your team decides whether to enforce it.
Can it follow a detected issue through correction, revised billing, refunds or collection, and prove the financial benefit without double-counting?
Yes, and that is the point. It can be done, but it is rarely, if ever, truly done: AMI business cases lean on assumptions nobody tracks or reports against. ADMX follows each case from detection to the corrected bill, refund or collection, counts each dollar once, and attributes it only under the measurement plan agreed up front. Indirect benefits get the same discipline: fewer truck rolls is a direct, measurable benefit, and the emissions avoided are measured with it.
Can it preserve the data, mappings and rules you need to change meter, head-end or billing vendors, and show that billing survives the move?
Yes, by starting from documentation. No configuration transition between AMI systems is seamless: the operational parameters built into one head-end vendor's workflows don't migrate cleanly into another's. So ADMX documents those parameters from day one, keeps datasets structured to best practice, and records business processes, ID mappings and exception rules outside any single vendor's system. A vendor change starts from a documented baseline, and ADMX compares reads and bills across the cutover so continuity is measured, not assumed.
Before a pilot reports any benefit, ADMX and your stakeholders agree on a measurement plan and record it in the software. Results are reported against that plan, with measured and estimated figures kept apart. This is the footing a water-savings performance contract needs.
Baseline and comparison periods, the boundary, and which meters and accounts are included.
How results are compared, what is excluded, and how known data gaps are handled.
Intervention costs and the rules for what ADMX can and can't take credit for.
Customer, operational, physical water loss, billing and financial effects, each reported on its own.
An agreed reviewer checks the results before anyone calls them savings.
ADMX is priced the way municipalities already buy software as a service: a fixed-fee activation, then a subscription per meter, per month. The WRF playbook describes the same per-meter, per-month structure for service-based metering models (Final Report, p. 70).
A fixed fee for onboarding and deployment by forward-deployed engineers, creating one cohesive view of your existing AMI infrastructure.
A monthly subscription for each meter, covering deployment and the continued operation of the live system, including your data scientists and change-management account manager.
Exception rules, crosswalks and weather normalization maintained as your system changes, so the cohesive view stays accurate.
Pricing depends on meter count and scope. Ask for a quote.
Public water systems, domestic wastewater systems, water districts and authorities in Texas, whether they have deployed AMI or are deploying it now.
| You are | Your question | How ADMX helps |
|---|---|---|
| Utility director or city manager | Will our AMI investment pay off? | We protect the return you planned for and give you evidence to justify the capital and loans behind it. |
| Operations and field crews | How do we stay ahead of problems? | Work routes 30 days ahead with a daily exception report built for you. |
| Billing and customer service | Why are bills late or wrong? | Exceptions are caught and handled before they ever reach a bill. |
| Finance and IT | Will this slow our systems or put our data at risk? | Data stays at the source, security stays in place, and reports stay fast. |
| Early AMI adopters | Did years of 24/7 data skew our billing? | Your data is still there. A 3-year weather analysis shows the skew and how to correct it. |
| Grant, funding and compliance staff | Can we prove our need and explain our numbers to the state? | Traceable evidence packets mapped to TWDB application fields, and loss trends reconciled before you report. |
| Department system owners | Will ADMX override my system? | No. You stay the owner and authority for your system and its data. ADMX connects it so others can act on it. |
| Municipalities mid-deployment | Is our rollout being installed right? | Forward-deployed engineers checking every meter through to billing. |
This is the record ADMX produces for every deployment: the scale, the connected systems, what failed and why, the corrective workflow, the measured results and the stakeholders' sign-off.
TX-DEPLOY-01Names are removed and every figure is an example. The scenario is built from field conditions ADMX's co-founders have documented; this record is replaced with a Texas customer's own results once that customer approves publication.
Asset: the Daily Exception Report flagged endpoints on three routes losing battery faster than design. The head-end confirmed the cause: read frequency set higher than specified at deployment, putting 15-year endpoints on track for about five.
Billing: the same endpoints were dropping reads. Left alone, those accounts would have hit the next bill read without actual reads, producing estimated bills and four-to-five-day corrections.
Step through the same workflow, system by system: From alarm to resolution.
| Measure | Before | After | Measured from |
|---|---|---|---|
| Affected accounts reaching the bill read without actual reads | 1,240Example | 0Example | CIS read type at bill read |
| Days to correct a bill-day exception on those routes | 4–5 | 0, fixed before the bill readExample | Billing cycle records |
| Projected endpoint battery life | About 5 years | 15-year design lifeExample | Head-end battery telemetry |
| Unplanned truck rolls on affected routes, per cycle | 37Example | 6Example | CMMS work orders |
| Endpoints returned under warranty | — | 212Example | RMA records |
Measured and estimated figures are reported separately, under the measurement plan agreed before work began. How we measure value.
A project team was analyzing a water system through its ERP and financial data and kept finding anomalous readings. Jane Story was brought in as a subcontractor for her operational-data specialty, wrote code to analyze the reads, and showed they weren't created in the financial system at all. They were being fed from the operational system.
Endpoints were set to read too often during deployment. Batteries drained early, and half of one AMI system went down.
A manufacturer's “enhancement” wiped out functionality the utility had paid for, cutting short a 15- to 20-year investment.
Some water systems wait 24 hours to run a simple report because their architecture pushes granular operational data into systems built for transactions.
A city installed a new BI publisher system and, a year later, asked why it was running so slowly. It had been porting all of its operational data into it.
Misconfigured collector units left meters transmitting but no data coming in, and the utility kept buying more hardware.
Some early AMI adopters let a small share of anomalous reads, say 3%, into billing. Estimates shifted without anyone knowing, and customers ended up over- or undercharged.
For years, water has been the overlooked municipal utility. Everyone assumed clean drinking water would always be there, so water never got the standards and efficiencies that electric and gas built up.
Many water operations teams have no warehouse and no meter shop. They meet at the tailgate each morning and carry their inventory in their trucks. Then AMI arrived and started pouring 24/7 data into operations that were never set up to receive it.
“We've got folks that aren't used to doing digital transformation, and now we've got to step in and help these cities and utilities transfer into the systems they've purchased.”
Jane Story, co-founderFor years, manufacturers across the operational world, including meter, pressure and decision-support systems, locked operators out of their own data. Access became an upsell, and the official reason was security. But the data in your system belongs to you, and your contracts increasingly say so.
Depending on how the network is deployed, operational data can be read every minute or every five minutes. ERPs and business systems are built for financial transactions. Pour one into the other and reports crawl, and cloud bills grow to store data you'll never use.
Source: WRF Smart Metering Playbook, Final Report (Project 5261, 2026), p. 32–33, Figure 1-8.
For the Smart Metering Playbook (WRF Project 5261, with SWAN Forum), 55 utilities in 22 countries described their drivers, risks and plans in April 2024. Riverbend Water Resources District in New Boston, Texas was among them. Their answers point to the same gaps ADMX is built to close.
Number of the 55 responding utilities. Source: WRF Smart Metering Playbook, Survey Data (Project 5261, March 2025), Figure 13.
Where ADMX fits: billing, meter maintenance, IT and asset management are the four teams ADMX connects through one record per meter, account and asset.
Number of the 55 responding utilities. Source: WRF Smart Metering Playbook, Survey Data (Project 5261, March 2025), Figure 15.
Where ADMX fits: IT and OT integration is the second-ranked risk. ADMX keeps OT in OT, reads only what each decision needs, and puts forward-deployed engineers where skilled resources run short.
Number of the 55 responding utilities. Source: WRF Smart Metering Playbook, Survey Data (Project 5261, March 2025), Figure 7.
Where ADMX fits: data integration ties for first. Device and battery life follows, and ADMX watches read frequency and battery drain so a 15-year system lasts 15 years.
Number of the 55 responding utilities. Source: WRF Smart Metering Playbook, Survey Data (Project 5261, March 2025), Figure 17.
Where ADMX fits: leak detection and pressure monitoring lead. ADMX uses pressure, flow and consumption together to show leaks across the system, not just at one meter.
The Final Report sorts utilities into four stages and points each to different work. ADMX is built for every stage, and fits best once AMI is in the ground.
Considering smart metering. Playbook focus: drivers, technologies and a compelling business case.
With ADMX: a free 3-year assessment puts your own data behind the business case.
Business case in hand. Playbook focus: procurement, project management, roles and responsibilities.
With ADMX: an integration list by system type, and one connected record written into scope.
Scaling to full deployment, or deciding to retrofit, upgrade or replace. Playbook focus: seamless integration and deeper value from the data.
With ADMX: forward-deployed engineers onboard one cohesive view, and data scientists check every meter through to billing.
Deployed and experienced. Playbook focus: optimize, benchmark and extend beyond the meter.
With ADMX: daily exceptions, verified outcomes against your business case, and TWDB benchmarks.
Stages from the WRF Smart Metering Playbook, Final Report (Section 1.2.1, pp. 2–4).
Recommended reading for every stakeholder: the Smart Metering Playbook and related resources.
Primes, engineering firms, cities, districts and utilities register once, under a shared organizational email. Build a cart of the opportunities you want to pursue, answer a short questionnaire, and exchange project files with ADMX, all kept in your account.
Checking your sign-in…
ADMX never asks for or stores a password on this page. Registrations are reviewed by ADMX before an account is activated. Once active, files can be PDF, images, CSV, JSON, Markdown or plain text, up to 20 MB each.
Explore public water and utility projects alongside reported system conditions. ADMX curates these records to identify where independent data review, AMI integration, water-loss measurement or project verification may be relevant.
Published contract, award and program values from public records, deduplicated.
Values are amounts stated in the public record: not-to-exceed ceilings, awards and published program values, not spend to date. Only records that state a total value are counted; per-meter, annual-only, savings, grant and budget figures are excluded. Counts reflect the records ADMX has collected, not the whole market. See the records.
Installing meters is the visible half of an AMI contract. The other half is whether every meter's data reaches the head-end, the MDMS and the bill, and whether the owner can prove it. ADMX gives your team that half: forward-deployed engineers, data scientists and a change-management account manager who make the data right, document it, and stay with the owner after your crews demobilize.
Owners and auditors now publish what goes wrong after install. The installer's name is on the project; the evidence that it worked should be too.
Findings as published by each owner, auditor or news outlet. Listed to show the risk, not to fault any vendor or installer.
The evaluation weights and contract terms owners publish reward the team that can prove data performance, not only the lowest installed price.
City of Alamo Heights weighted its AMI evaluation lifecycle cost 35, support 35, compliance 20, risk 5, network 5, with payment tied to a System Acceptance Testing milestone. Source ↗
Miami-Dade WASD scored technical 5,000 points against price 1,000 on its $273.6M AMI award; the winning team was not the lowest price. Source ↗
Louisville Water's contract set 99% one-day and 99.5% three-day read rates by project end. Port Arthur's RFP requires 98% within 72 hours. Louisville ↗ · Port Arthur ↗
Miami-Dade procured an AMI owner's representative separately from the installer. Denton bought $6.5M of monitoring and analytics alongside its $26M AMI award. Miami-Dade ↗ · Denton ↗
ADMX is manufacturer-agnostic and works alongside the meter, network and head-end your team proposes. We price as a fixed-fee activation inside your bid, then continue with the owner on a per-meter, per-month subscription.
Forward-deployed engineers are ADMX employees, backed by data scientists and a designated change-management account manager.
ADMX reads from the owner's systems and writes back only through approved interfaces, so it adds no risk to your installed system.
A fixed-fee activation fits your bid. The per-meter subscription continues with the owner, so no support tail stays with you.
Register your company to build an opportunity cart, answer our teaming questionnaire and exchange documents with ADMX.
Send the opportunity. We'll return a project-specific capability package your team can consider for the bid. Submitting does not create a teaming agreement.
A listed opportunity is a research lead. It is not an endorsement, a bid invitation, a confirmed project scope, or a claim that ADMX participation will secure an award. Every record links to its source; check the official record before acting. Draft: these records are pending ADMX editorial review of source, location, metric definition and wording before public release.
Each layer is a different kind of record. Markers group records by county in Texas and by state elsewhere; select one to see the records behind it.
Records behind each marker appear here. Locations are approximate: county or state centroids, never a site address.
The list uses the same filters as the map. Each card shows the record's stage, its source and the date it was checked, and ADMX's potential fit, which is our analysis rather than a finding by the owner.
These records are drawn from Texas Water Development Board water-loss audit data for audit year 2024. A reported total water-loss percentage is not the same as a measured leak rate. Loss may include both physical leakage and apparent losses such as meter or billing-data inaccuracies. Review each system's source record and validation information before drawing conclusions.
TWDB defines total water loss as the difference between system input and authorized consumption, split into real losses (physical losses such as leakage and overflows) and apparent losses (meter inaccuracy, unauthorized consumption and billing-data errors). For financial-assistance thresholds TWDB uses real and apparent loss in gallons per connection per day, not a percentage.
A system is flagged if either screen applies to its 2024 audit:
Sources: TWDB Water Loss Dashboard and audit data · TWDB water loss thresholds
Counts reflect the records ADMX has collected, not the complete market. There is no "worst systems" ranking: audit quality and system differences make a filterable distribution with its source more defensible.
All layers, current filters ignored.
Evidence level as recorded for each source.
Top 12. Collected records only.
TWDB audit year 2024. A system can meet both screens.
Tell us about the opportunity and what you'd like from ADMX. We'll review the request and reply with what fits.
Submitting this form does not establish a teaming agreement, and it does not commit either party to a pursuit.
How the Atlas grows: Texas public data first; then further opportunity records after column mapping and editorial review; then other states and countries as reliable sources and update practices are in place.
Look up any Texas water system's reported water loss, then build the list of integrations you need. Both use public sources, linked exactly to where the data lives.
Every audit a Texas utility files with TWDB splits water loss into apparent losses, from meter inaccuracy, data handling and unauthorized use, and real losses, from leaks and breaks. In every year from 2015 to 2024, the statewide median real loss was between 5 and 7.5 times the median apparent loss.
Source: TWDB Historical Water Loss Audit Data, as of 28 February 2026, from the TWDB Water Loss Dashboard. Medians of audits TWDB includes in its historical reports. The number of audits varies by year; 2015 and 2020 include most systems' five-year audits. Values as reported by utilities and quality-reviewed by TWDB staff.
Choose the systems you operate, organized by TCEQ rule chapter, and the software you run. You get a list of every integration and public data source to plan for, with links to each source. Sign in to save it and share it with the ADMX team.
Organized the way TCEQ regulates them under Title 30 of the Texas Administrative Code. Choose all that apply.
Rule text links open the Cornell Legal Information Institute copy; the official reference is the TCEQ rules index. Citations are for orientation, not legal or compliance advice.
Systems marked Common are typical for the types you chose. Pick what you run, or choose Other and type its name.
Suggested from the system types you chose, based on what each source covers. Add or remove any.
ADMX reads from the systems you depend on. That makes how we connect, isolate and handle your data as important as what we show you. In the WRF Smart Metering Playbook survey, 20 of 55 utilities ranked privacy and security among their top three AMI project risks.
These are design commitments for the ADMX platform. Each is confirmed through security review before any customer data is connected.
Connectors read from your systems. Any write-back runs only through an interface you approve, is reconciled against your system, and can never change a meter or device setting.
Operational data reaches ADMX through a historian or DMZ export your team controls. There is no path back into SCADA.
Each customer's data is kept separate at every layer, and every request is checked against the customer it belongs to.
ADMX APIs are described in the OpenAPI format and versioned, so your IT team can review exactly what is exchanged.
Questionable readings are flagged and the original values retained, the data-integrity best practice in EPA's Online Water Quality Monitoring in Distribution Systems (EPA 817-B-18-001, §6.1).
Each value links back to its source system, record and retrieval time. Your data can be exported back to you at any time, and at the end of a subscription your crosswalks, rules and case records are handed back in open formats. The playbook asks for exactly this: exit and data-handover terms, because metering data belongs to the utility.
Security is built into every phase of development, from planning through retirement, following the NIST system development life cycle, and aligned to the NIST Cybersecurity Framework functions (Identify, Protect, Detect, Respond, Recover) and AWWA G430, the frameworks the WRF playbook recommends for vetting AMI vendors.
ADMX is built so your stakeholders can trust what it shows and stay in control of what happens next.
We prepare responses to the requirement, terms, proposal contents and evaluation factors your solicitation defines.
ADMX grew out of years spent on the owner's side of AMI deployments. We saw the same pattern again and again: meters installed, data flowing, and nobody checking whether it was right or what it meant. ADMX closes that gap with software, and with forward-deployed engineers who stay until your data is trusted.
Specialist in operational data for water systems and municipalities. She was first brought in as a subcontractor to explain anomalous reads that a financial-data analysis couldn't, and traced them to the operational system. She spent five years on the owner's side of AMI deployments, focused on deployment quality, change management and capturing the return owners planned for. From the oil industry she brought the habit of reading an area's “microeconomics,” the root of ADMX's weather-normalized analysis.
Brings an operator's and owner's view of utility infrastructure, with a background in gas distribution. Focused on outcomes that protect stakeholders, employees and the customers they serve.
Forward-deployed engineers onboard the platform and create one cohesive view of your existing AMI infrastructure. Data scientists and designated change-management account managers ensure data integrity for every customer. How the team works.
Every number links to its source system, record and time. Measured results, estimates and predictions are always labeled apart.
Your systems stay the source of record. Anything written back goes only through an interface you approve.
ADMX never diagnoses a leak, changes a bill, dispatches a crew or approves a warranty on its own. It brings the evidence.
We protect the design life of what you bought and the return you planned, through configuration, vendor and system changes.
Forward-deployed engineers are ADMX employees. Data scientists and your change-management account manager stay with you.
Systems and evidence organized by TCEQ 30 TAC chapter and reconciled with TWDB public data, before expanding to other states.
Start with a three-year assessment of your meter data against National Weather Service records.
Start with the industry's own playbook, then the questions stakeholders ask us and the terms we use.
We recommend every stakeholder, from council members to meter technicians, read the Water Research Foundation's Smart Metering Playbook. It is the broadest current look at how utilities plan, buy and run AMI.
Findings from the Final Report and survey, matched to what ADMX does.
| Playbook finding | What ADMX does about it | Read more |
|---|---|---|
| Customer service and billing is the business unit most affected (53 of 55) | Exceptions are caught 30 days before the bill read, so bills go out on time and on actual reads. | Daily Exception Report |
| IT and OT integration is a top-three project risk (31 of 55) | OT stays in OT. ADMX reads only what each decision needs and keeps its own case and evidence records. | OT stays OT |
| Data integration ties for the top procurement consideration (35 of 55) | APIs move the data; unique identifiers link every system's record for the same meter, account and asset. | APIs and UIDs |
| Battery life is the top meter specification (43 of 55) | Read frequency and battery drain are watched so endpoints reach their design life. | Owner advocacy |
| Multiple vendors and contractors is a named risk (13 of 55) | One record from alarm to outcome documents the failure point and the responsible party. | Three questions |
| Skilled resources are short (15 of 55) | Forward-deployed engineers, ADMX employees, work inside your environment and train operators on their own reports. | Forward-deployed engineers |
| Leak detection (50) and pressure monitoring (41) are the offerings most wanted | Pressure, flow and consumption are analyzed together, system-wide. | Capabilities |
| Data analysis (41) and digital twin (23) are on utilities' minds | ADMX is the digital twin of your asset data: every meter, account and service point reconciled across your systems. | Digital twin |
| Running the data management layer through a vendor risks limited access, lock-in and data loss if the vendor fails (Final Report, pp. 17–18) | ADMX is read-only; your systems stay the source of record, and crosswalks, rules and case records are handed back in open formats. | Trust & security |
| Monitor actual battery performance and enforce warranties; real-world life is 10–15 years, 8–12 with frequent transmissions (pp. 40–42) | Read frequency and battery drain watched on every endpoint, with warranty evidence documented. | Battery life chart |
| Only reads and cut-cable alarms usually pass between vendors, which can lock utilities in for 15–20 years (p. 41) | Parameters, mappings and rules documented outside any single vendor's system, so a vendor change starts from a baseline. | Operational portability |
| Validate AMI data before billing; Moulton Niguel's QC scripts and weekly reviews catch issues before billing cycles complete (pp. 81–82) | The Daily Exception Report flags issues 30 days before the bill read. | Daily Exception Report |
| A benefits realization plan needs governance, metrics, targets and accountability per benefit (p. 77) | A measurement plan agreed before any benefit is claimed, with independent sign-off. | How we measure value |
| Consider a dedicated change management and communications manager (p. 89) | Every subscription includes a designated change-management account manager. | Your ADMX team |
| Service models are priced per meter, per month (p. 70) | Fixed-fee activation, then a subscription per meter, per month. | Subscription model |
| Future outlook: API-based collaboration between technology partners (p. 93) | APIs move the data; UIDs keep every system talking about the same meter. | APIs and UIDs |
| Treating AMI as a hardware upgrade is a common mistake (Water Online) | Smart meters aren't a construction project; operator readiness is part of activation. | How we work |
Page numbers refer to the WRF Smart Metering Playbook, Final Report. Counts are from the Survey Data figures. ADMX is not affiliated with or endorsed by the Water Research Foundation or SWAN Forum.
ADMX stands for Asset Data Management eXtraction. It's a platform that sits on top of your IT and OT systems, keeps your cybersecurity in place, and pulls only the data needed for system-wide analysis.
No. ADMX works on top of what you have and helps protect it.
Most AMI systems are meter-focused. They analyze one meter at a time and can't show how the whole system affects finances, water loss or conservation.
Most AMI projects are delivered by meter distributors as construction projects. Nobody redesigned how billing and operations would use 24/7 data.
No, the data is still there. A 3-year weather analysis can show whether anomalous data skewed your system, and how to correct your estimates.
Yes. ADMX traces a failure to its source across meter, endpoint, network, head-end, MDMS and billing, and documents the responsible party and timeline in a form a service-level or warranty claim can stand on. Read all three questions.
No configuration transition is seamless, so ADMX documents your parameters, mappings and exception rules from day one, outside any single vendor's system. A vendor change starts from that baseline, and reads and bills are compared across the cutover.
No. Every system keeps its own IDs. ADMX keeps a crosswalk that links them into one master record.
ADMX links the new meter to the same premise and service point, so years of usage history carry over instead of being lost.
Yes. ADMX reads by default. Nothing goes back into your systems without an approved interface and your sign-off, and nothing changes how a meter behaves.
No. Operational data overloads business systems and runs up storage costs. ADMX keeps source data where it lives and stores only its own case, evidence and analysis records.
Forward-deployed engineers onboard the platform. Data scientists and your designated change-management account manager ensure data integrity and lead the change with your team. Meet the team.
ADMX is a software company. Our forward-deployed engineers are ADMX employees who handle activation, onboarding and deploying the software in your environment, and support your team, but what you buy is a software subscription.
A fixed-fee activation, then a monthly subscription per meter, per month, for the deployment and continued operation of the live system. Pricing depends on meter count and scope.
It's designed as a continuing relationship. The biggest gains come after about a year of data.
ADMX organizes systems and records by the 30 TAC chapter that governs them: Chapter 290 for public drinking water, Chapter 217 for domestic wastewater, Chapter 285 for on-site sewage, Chapter 210 for reclaimed water, Chapter 315 for pretreatment, Chapters 297 and 299 for water rights and dams, Chapter 344 for landscape irrigation and Chapter 288 for conservation and drought plans. The citations organize evidence; compliance stays with the utility. See the full framework.
No. ADMX assembles traceable evidence packets mapped to TWDB application fields. It never scores or predicts awards.
It might be. It might also line up with wholesale purchases or sales, a boundary change, or new connection or population counts. ADMX flags those possibilities so you can check them before you report.
Tell us a little about your system. We'll run three years of your meter data against local weather to see whether your system follows its environment, show where skew has crept in, and what to change in your billing estimates.
Effective date: [set at launch]. This notice covers this website and the forms, registration and document exchange on it.
Information you enter in our forms: your name, organization, work email, phone, meter count, systems you run and any notes. For company and city accounts, the organization’s details, its shared master email, individual users’ names and emails, questionnaire answers, the opportunities saved to its cart, and files exchanged with ADMX.
Basic technical information our hosting provider records to deliver and protect the site, such as IP address, browser type and request times.
Your opportunity cart and form drafts are stored in your own browser until you send them.
To respond to requests, prepare assessments and capability packages, review and activate accounts, exchange documents you send us, and keep the site secure. We do not sell personal information, and we do not use it for advertising.
Service providers that run this site for us, such as our hosting, email and storage providers, under terms that limit their use of it. We may disclose information when the law requires it. Utility data you share for an assessment is used only for that assessment unless we agree otherwise in writing.
Inquiries are kept for as long as we are in contact and for a reasonable period after. Account records and exchanged files are kept while the account is active; at the end of a subscription your crosswalks, rules and case records are returned to you in open formats on request, as described on our Trust & Security page.
You can ask to see, correct or delete the personal information you sent us by emailing [email protected]. Public agencies should note that records they send us may also be subject to their own public-information obligations.
We use encrypted connections, access controls and limited retention. No system is perfectly secure; tell us right away if you believe your account has been misused.
ADMX, Asset Data Management eXtraction · [email protected]
Effective date: [set at launch]. By using this site you agree to these terms.
Content on this site, including the Opportunity Atlas, the water-loss lookup, the integration list builder and references to TCEQ and TWDB rules, is provided for general information. It is not legal, engineering, compliance or financial advice, and the utility remains responsible for its own compliance.
Opportunity and water-loss records are drawn from public sources and linked to them. They may be incomplete, out of date or later revised by the agency or owner. Check the official record before acting on it. A listed opportunity is a research lead, not an endorsement, bid invitation or confirmed scope.
Submitting an inquiry, registering an organization or adding an opportunity to a cart does not create a teaming agreement, subscription or other contract. Any engagement is made only in a separate written agreement.
Each organization registers under a shared organizational master email, with individual users linked beneath it. You are responsible for keeping your organization’s users current and for activity under your account. ADMX may decline, suspend or deactivate an account.
You confirm you have the right to share any file you upload, and you allow ADMX to store and process it to provide the service you requested. Do not upload information you are not permitted to share.
Do not attempt to access other organizations’ accounts or data, disrupt the site, scrape it in bulk, or submit unlawful or malicious content.
The site’s text, design and software belong to ADMX or its licensors. Public data remains subject to its publisher’s terms. Third-party names are used only to identify their products and do not imply endorsement.
The site is provided as is. To the extent the law allows, ADMX is not liable for indirect or consequential losses arising from use of the site or reliance on its content.
These terms are governed by the laws of the State of Texas. [Venue and any additional terms to be confirmed by counsel.]
How to read the information on this website, including statements about ADMX’s plans and strategy.
This is background information about ADMX Optimization Inc.’s (“ADMX”, “Company”) activities and strategy current as of the date of the website. This information is given in summary form and does not purport to be complete. It is based on information that is already in the public domain including information from third-party sources. While the company believes the information from the third-party sources to be reasonable, the company cannot guarantee its accuracy. Readers should verify such information for themselves.
ADMX’s public record should be consulted for a more complete understanding of the company’s status. Nothing in this website should be considered an invitation, advice, or a recommendation to investors or potential investors to hold, purchase, or sell securities. Before acting on any information, you should consider your particular situation and seek independent financial advice from a qualified registered professional.
Certain information contained herein may constitute “forward-looking information”. Generally, forward-looking information can be identified by the use of forward-looking terminology such as, “will”, “anticipated”, “if”, “projected”, or variations of such words and phrases or statements that certain actions, events, or results “will” occur. Forward-looking statements regarding the company’s strategy or position are based on the company’s estimates and are subject to known and unknown risks, uncertainties and other factors that may cause the actual results, level of activity, performance or achievements of the company to be materially different from those expressed or implied by such forward-looking statements or forward-looking information.
There can be no assurance that such statements will prove to be accurate, as actual results and future events could differ materially from those anticipated in such statements. Accordingly, readers should not place undue reliance on forward-looking statements and forward-looking information. The Company will not update any forward-looking statements or forward-looking information contained herein, except as required by applicable securities laws.