FAQ
What the model needs, what it returns, and what it takes to get started.
Fracta serves water utilities and the engineering firms that support them. We help you find leaks faster with Fracta Leak Zones, prioritize which mains to inspect, maintain or replace with our risk assessment (Likelihood of Failure, Cost of Failure and Total Risk), and turn legacy drawings into GIS-ready data with As-Built Digitization.
Likelihood of Failure (LOF) estimates a pipe’s probability of failure over a defined period. Cost of Failure (COF) estimates the financial impact, including repair and disruption, using specified cost assumptions. Total Risk combines the two to help compare priorities across the network.
No. Our risk assessment uses your existing asset and break records plus environmental and geographic data Fracta maintains. Fracta Leak Zones adds an optional SCADA export, never new hardware or a live connection. Both tell your crews where to focus field work; they do not measure a pipe’s physical condition.
An AI-driven service that ranks the areas of your network most likely to contain leaks, so crews know where to start. It combines Fracta’s Likelihood of Failure model with your operating data.
A survey sweeps miles of pipe with no clear starting point. Fracta Leak Zones tells you which areas to survey first, so crew hours go where leaks are most likely. Your survey team or partner still confirms each leak in the field.
Only a GIS pipe inventory (pipe ID, install date, material, diameter) and break history are required. For the sharpest targeting, we recommend a SCADA export of hourly flows, tank levels and pressures, plus GIS of pressure zones and facilities.
No. We only need a CSV or Excel export 1 to 4 times a year, matching your package. It is recommended, not required.
Yes. Send what you have and flag what is missing. We will tell you up front how gaps affect scope.
No. Fracta Leak Zones is a standalone service and does not require a prior Fracta risk assessment.
Once, twice, three or four times a year (Bronze, Silver, Gold or Platinum), so your team has time to investigate and act on each set before the next one arrives.
Your crews confirm leaks in the field. If you prefer, Fracta can include on-site pinpointing through a leak detection partner as an optional add-on.
Pricing is based on the miles of main analyzed and how many deliveries you receive each year. Optional on-site pinpointing is quoted separately. Contact us for a quote.
Start with your pipe-network GIS data, including unique pipe IDs, material, diameter and installation year, plus dated break or repair records. Breaks need a pipe ID or a usable location. Fracta reviews the files and identifies gaps before scoping the assessment. Fracta Leak Zones needs the same two datasets to start. A SCADA export and zone/facility GIS are recommended, not required.
Missing pipe attributes do not automatically rule out an assessment. Some values can be estimated or recovered from supporting records. We also need to review whether the available break history and asset locations are usable. Estimated attributes should not be treated as field-verified facts.
Yes. Our As-Built Digitization service converts scanned drawings and legacy maps into georeferenced features and structured attributes for GIS use. We review the source records and agree on the required layers, attributes and output format. Digitization represents what the records show; it is not a field survey.
For a risk assessment, your team reviews pipe-level results on an interactive map, examines contributing factors, and uses reports and data exports. For Fracta Leak Zones, you receive a map of priority areas for leak investigation, refreshed 1 to 4 times a year. For As-Built Digitization, you receive GIS data in the agreed structure and format. The exact analyses depend on the agreed scope.
Yes. Assessment data can be exported in formats such as CSV, GeoJSON and Shapefile for use in existing GIS and analysis workflows. File export is different from a live integration; specific connections or automated data exchange should be confirmed during scoping.
Fracta evaluates predictive performance using historical break records held out of model training. Ask to review the validation approach and results relevant to your assessment. Outputs express probabilities, not guaranteed failure dates, and should be used alongside engineering judgment and field evidence.
Yes. Risk results help compare replacement priorities. Long-term projections can explore how different renewal rates affect expected breaks. These outputs support planning decisions; they are not construction designs, and projections depend on the data and assumptions used.
We start by understanding your goals and reviewing your available data or drawings. We then agree on the scope, prepare and check the data, carry out the analysis, leak prioritization or digitization, and review the deliverables with your team. Your local knowledge helps resolve gaps and interpret the results.
Timing and pricing depend on the work requested and the condition and volume of the source data. For risk assessments, network size helps define scope; for digitization, the record set does. We review those inputs before confirming a quote and delivery schedule. For Fracta Leak Zones, scope is set by network size and how many deliveries you receive each year.
Your team can use the in-app user guide for operating instructions and contact Fracta for assistance. For risk assessments, new break records, asset changes and model updates can affect results. Confirm the support arrangements, platform access and reassessment schedule included in your agreement. With Fracta Leak Zones, updated priority areas arrive on your package schedule, so your team can act on each set before the next one lands.
Fracta scores every pipe segment in your distribution network for how likely it is to fail and what that failure will cost, so your next capital dollar replaces the segment carrying the most risk. It uses machine learning on the records you already have. No new sensors, no field work.
| Score | Question it answers | Unit |
|---|---|---|
| Likelihood of Failure (LOF) | Which pipes are most likely to break? | Probability (%) at 1, 2, 3 and 5 years |
| Cost of Failure (COF) | What happens, in dollars, when they do? | $ per segment (direct + indirect) |
| Total Risk (TR) | Where should the next capital dollar go? | $ at risk per segment (LOF × COF) |
Primarily potable water mains. Reclaimed water, transmission lines and others can be included by agreement.
Age, material and break history are three of the many variables that decide whether a pipe fails. On their own they send crews to the oldest pipe, not the weakest one, and they say nothing about what a break costs. Fracta weights 120+ variables learned from 560,000+ recorded breaks, instead of weights assigned by hand.
Topeka, KS (three engineers, $6.5M in annual waterline replacement) saw 54% of pipe failures fall in the highest-risk tier in year one and 65% in year two, with an average $18K direct savings per capital project and $80K to $100K in annual savings. Fracta is trusted by over 100 utilities across North America and has analyzed 200,000+ miles of pipe.
| Topeka, KS | Result |
|---|---|
| Failures caught in the highest-risk tier, year one | 54% |
| Failures caught in the highest-risk tier, year two | 65% |
| Average direct savings per capital project | $18K |
| Annual savings | $80K to $100K |
A machine learning score of each pipe segment’s probability of failure at 1, 2, 3 and 5 years, plus its percentile rank across your system and the five variables contributing most to that score.
Both. It is trained on 560,000+ recorded breaks across 200,000+ miles of pipe, then calibrated against your own system’s failure record.
For each segment, the five factors contributing most toward a higher predicted LOF. The order is learned from data, not set by a fixed rule like “age always comes first,” so it differs pipe to pipe.
No. It means soil-related inputs contribute more to that pipe’s predicted LOF than age does, given the other inputs. A driver explains the prediction; it does not prove the physical cause or measure present condition. Drivers are relative influence, not percentages of failure probability.
Fracta evaluates predictive performance on historical break records held out of model training. At Topeka, 54% of failures landed in the top-risk tier in year one and 65% in year two. Outputs are probabilities, not guaranteed failure dates.
Yes. Accuracy improves as your break data accumulates. With a Fracta Monitor subscription, your network is re-scored annually as your data changes.
The dollar cost of a break on each segment, split into direct cost (repair and restoration) and indirect cost (the consequences of the break). It is location aware: a break under a quiet side street and one on an arterial outside a hospital are not the same event.
| Direct cost | Indirect and consequential cost |
|---|---|
| Excavation, repair and pipe replacement | Service interruption to downstream customers |
| Pavement and surface restoration | Traffic disruption and detour duration |
| Emergency crew mobilization and overtime | Impact on hospitals, schools, emergency services |
| Intense repair (HDD, jack and bore) near rail and major routes | Water lost, environmental exposure, property and third-party damage |
Direct costs come from AWWA handbooks, Water Research Foundation findings, public bid results from small, medium and large cities, and academic cost studies. Indirect defaults use public bid documents for traffic control, environmental fine records and WRF technical reports. Defaults are refined over time with anonymized values entered by other Fracta customers.
Yes, and we recommend it. Every input can be edited, and a custom COF field lets you add your own rule by diameter, material or install year range. Property damage and critical facility costs have no defaults, because public data is too thin, so your team supplies those.
Three methods, from simplest to most precise:
A geospatial buffer around each pipe counts hospitals, schools, fire and police stations, streams and water bodies from Fracta’s in-house database. Each counted feature adds its input cost. You can view these features in the COF map view.
Named sets of cost assumptions you create in the platform (Scenarios tab) and switch between, so you can compare, for example, a conservative and an aggressive cost view. COF and Total Risk update with the selected scenario.
Likelihood of Failure multiplied by Cost of Failure: the expected dollars at risk on each segment. It is one objective criticality score, comparable across the whole system and readable by anyone who approves a budget.
Because a likely break can be cheap and an unlikely one can be expensive. In this example, condition alone sends crews to Segment A first; Total Risk moves Segment B 35 places earlier.
| Segment A (residential side street) | Segment B (arterial near hospital) | |
|---|---|---|
| LOF, 5-year | 82% | 31% |
| Cost of Failure | $9,000 | $75,000 |
| Total Risk | $7,380 | $23,250 |
| CIP rank | #41 | #6 |
Building a CIP ranked in dollars, sizing budgets by how much risk each funding level buys down, and supporting master plans, rate cases and grant applications with an auditable figure per segment.
Total Risk in dollars for every segment, a system-wide ranking, a map layer symbolized by Total Risk, an exportable ranked asset list for the CIP, COF scenario comparison, and Job Planner grouping for project bundling.
Long-term projections can explore how different renewal rates affect expected breaks. They support planning decisions; they are not construction designs.
| Dataset | Required? | Key fields |
|---|---|---|
| Pipe assets | Yes | Unique ID, install date or year, material (with code legend), diameter; status optional |
| Break history | Yes | Break date on every record; pipe ID, geometry, lat/lon or address |
| Supplementary layers | Optional | Pressure, parcels (year built), valves, hydrants, reservoirs/plants, joints |
Most utilities already have 90% of this in their GIS.
Take the six-question Data Readiness Check (about 15 minutes). Most utilities clear five of six from their GIS alone.
Yes. Blank values are workable; missing columns are not. Gaps in install year, material or diameter can be recovered from connecting pipes and supplementary layers. Estimated attributes should not be treated as field-verified facts.
Undated breaks are removed from the model. Breaks without a pipe ID are matched to the nearest pipe. Addresses are geocoded; incomplete or erroneous addresses may be dropped.
Shapefile, GeoPackage, File Geodatabase or GeoJSON; breaks can also come as Excel or CSV with locations. Imperial or metric, any projection or national grid, local-language field names. Tell us the units and CRS; no need to rename, translate or clean anything.
Export the layers, send them via the secure link your Fracta contact provides or your utility’s SFTP, and Fracta returns a written completeness summary flagging missing fields and anomalies before scoping.
Yes, through As-Built Digitization, which converts record drawings into GIS data first. See the As-Built Digitization questions below.
A web map of your network with Assets and Risk Analysis views: LOF, COF, Total Risk, length and population layers (depending on subscription), plus Population and Critical Infrastructure context layers. Filter by any property or a drawn area, click any pipe for details, and manage COF scenarios.
Per mile of main, banded by system size: larger systems pay less per mile. Every quote is built from a verified mile count. The package is a one-time baseline assessment of the whole network with year one of platform access included.
From month 13, a Fracta Monitor subscription keeps platform access and re-scores your network annually as your data changes. A three-year term is recommended; one- and five-year terms are available.
Yes, cooperative purchasing vehicles are supported where a utility buys that way.
Timing is confirmed after we review your data. Historically, assessments have taken about four to eight weeks; data quality and follow-up requests can affect the schedule.
Data can be transferred through the secure link provided by your Fracta contact or your utility’s SFTP. Before transfer, confirm the hosting and access arrangements, retention and deletion terms, and any utility-specific security requirements with Fracta.
An in-app user manual, your Fracta representative and contact@fracta.ai.
It converts as-designed and as-built drawings (scanned record sets, mylars, vector PDFs and CAD files) into GIS data that is georeferenced to a coordinate system, connected at junctions and attributed to your schema. The service is patent pending.
Most utilities do, but the authoritative record of what is actually in the ground often still lives in drawings, not the GIS. Digitization closes that gap so your GIS reflects your records, not just what someone had time to draw in.
Water distribution, wastewater collection, stormwater, gas distribution and transmission, liquids pipelines, electric distribution, and telecom and fiber outside plant.
GIS managers and analysts, records and asset managers, distribution or collection system managers, engineering PMs at capital project closeout, city engineers and county surveyors, gas integrity leads, outside plant engineering teams, and GIS leads at engineering firms.
| Sector | Requirement | Date |
|---|---|---|
| Drinking water | Lead and Copper Rule Improvements service line inventories | Nov 1, 2027 |
| Gas transmission | PHMSA TVC records and MAOP reconfirmation (49 CFR 192.624) | Jul 3, 2028 |
| Wastewater / storm | MS4 outfall mapping; consent decree deliverables | Per permit |
| Electric / public works | Esri Utility Network migration after ArcMap retirement | Ongoing |
| Telecom / broadband | FCC Broadband Data Collection; BEAD as-built reporting | Per program |
| Engineering / SUE | ASCE 38-22 records research | Per project |
Dates reflect federal rules as published; confirm state-level variation with your regulator.
No. As-Built Digitization is sold and priced entirely on its own. It is also the natural first step if you later want Likelihood and Cost of Failure scoring, which requires the network in GIS.
Yes. Our workflow starts with digital files, so paper and mylar need to be scanned first. Contact Fracta before arranging scanning to confirm file requirements for your drawings.
We use file-based exchange through a sharing method agreed with your team, including your organization’s existing file-sharing service. Contact Fracta to arrange the transfer. No connection to your live GIS is required.
There is one deliverable quality level: human-verified and GIS-ready.
Every delivery includes a QA report with residual error at control points, so positional accuracy is measured, not asserted.
No. Digitization represents what the records show. If the original drawing is wrong, the GIS will faithfully reflect that error. It is a strong basis for records research, not a substitute for field verification.
Yes. A small sample can be digitized at no charge so you can review the output before a larger engagement. Agree on the sample size and scope with Fracta first.
From one municipal storm drainage set (vector PDF), the delivered layers included:
| Layer | Features delivered |
|---|---|
| Storm drain structures | 52 |
| Storm pipe segments | 49 |
| Sanitary manhole covers | 17 |
| Water valve boxes | 10 |
| Control points carried for QA | 5 |
Per sheet, banded by volume: more sheets, lower cost per sheet. Every quote is built from a verified sheet count, never a number guessed on a call. A one-time service, with no required Fracta subscription for the delivered GIS files.
You retain rights to your source drawings and the GIS datasets derived from them.
Ask us directly, or see the model run on your own network.
Live webinar · Tue, Dec 8 · 9:00 AM PT / 12:00 PM ET
How West Slope Water District uses Fracta AI to act like a larger utility.
Save my seat