Under 43 CFR subpart 3175 each Facility Measurement Point runs four independent clocks — plate pull-and-inspect, transducer verification, meter tube, spot sampling — and every one of them is keyed to the FMP's volume tier. Change the average flow rate and the whole calendar silently shifts. A spreadsheet does not notice. This does: it derives the tier, recalculates all four due dates, and flags the FMPs whose tier just moved.
One-time purchase. No subscription. No account. Works offline.
Enter the FMP's average flow rate in Mcf per day and the § 3175.10 volume tier follows: very-low at 35 or under, low to 200, high to 1,000, very-high above that. The tier appears on the FMP card and drives every interval. Update the rate and all four due dates recalculate on the spot.
A well that fell from high to low just had its plate interval doubled from three months to six. One that climbed the other way just had it halved, and may already be late. The app names every FMP whose tier moved since its last entry, so the shift is a notification instead of a finding.
The headline view is one list across the whole portfolio: overdue in red, due within 30 days in amber, current in green, with a running count of overdue items and an indicative exposure figure at $1,000 per missed inspection under BLM's assessment schedule.
Pick an FMP and a period and get the document: its identifying and primary-device data, every event in the period in full, and the plate-inspection detail § 3175.80(e) requires attached to it. Printable, exportable as CSV, plus a whole-portfolio CSV for the six-year retention.
| Clock | Citation | Very high | High | Low | Very low |
|---|---|---|---|---|---|
| Orifice plate pull-and-inspect | § 3175.80(d) | 1 month | 3 months | 6 months | 12 months |
| Transducer verification — EGM | § 3175.102(b) | 1 month | 3 months | 6 months | 12 months |
| Transducer verification — mechanical recorder | § 3175.92(b) | 1 month | 2 months | 3 months | 6 months |
| Meter tube inspection | § 3175.80(h)-(k) | 2 years | 4 years | 8 years | Exempt |
| Spot sampling | § 3175.110 | 1 month | 3 months | 6 months | 12 months |
| New / re-fractured plate cycle | § 3175.80(c) | 14 days, until an inspection passes API 14.3.2 § 4 | |||
A mechanical chart recorder verifies at double the EGM frequency, and a very-low-volume FMP is exempt from the meter tube clock — two rules that are easy to get backwards on a spreadsheet and impossible to get backwards here.
The routine pull-and-inspect runs at the tier frequency, and § 3175.80(e) sets out what the record must contain: the plate's orientation as found — bevel upstream or downstream — the measured orifice bore diameter, the condition of the plate, and whether it passed or failed against API 14.3.2 § 4. A plate that fails needs a replacement recorded, because the bore in the run has just changed and every volume calculated after it depends on that number.
The app captures all of it on the event, updates the FMP's bore and beta ratio when a plate is replaced, and puts the whole set in the verification report as a table.
A new FMP, or one whose well has been recently re-fractured, inspects its plate every 14 days rather than at the routine tier interval — because that is when solids, scale and frac sand do their damage. The cycle ends when an inspection is recorded that passed API 14.3.2 § 4.
Mark the FMP as new or recently re-fractured and the plate clock switches to 14 days. Log a passing inspection and it reverts to the routine tier frequency by itself, with no calendar to rebuild.
Transducer verification is not a tick in a box. The differential pressure, static pressure and temperature transducers are each read against a certified test device, as found and as left, and the error is what the record turns on. A mechanical chart recorder does this at double the EGM frequency.
The app takes all six readings plus the reference, computes each error in absolute terms and as a percentage, and keeps them with the event so the verification report shows the work rather than the conclusion.
Four intervals per FMP, two of them multi-year, all of them keyed to a tier that moves with production. A tab per year, a formula somebody copied down wrong in 2024, and a meter tube inspection nobody has thought about since the tube went in. Then the flow rate on three FMPs drops below 200 and every interval on them changes without a single cell updating.
This is the same calendar kept where the tier lives: one register, four clocks per FMP, recalculated the moment a rate changes, with the record and the report generated from the events themselves.
Every clock on every FMP sits in exactly one band, so the exposure is on the first screen rather than found the week before an inspection.
FMP name and BLM FMP number, lease or unit/CA, well or battery, measurement type, primary device, meter tube inside diameter, orifice bore, and the derived beta ratio.
Average flow rate in Mcf per day over the averaging period, the § 3175.10 tier it lands in, and a flag when that tier has changed since the last entry.
Date and time, technician and company, prior event date, plate orientation, measured orifice bore, plate condition, and pass or fail against API 14.3.2 § 4 — with a replacement record when it fails.
As-found and as-left readings for the differential pressure, static pressure and temperature transducers against the certified test device, with the error computed for each.
Measured tube inside diameter and inspection result on the multi-year tube clock; method, laboratory, heating value and relative density on each spot sample.
The verification report as a printable page and as CSV, a whole-portfolio event CSV for the six-year retention Onshore Order 5 requires, and full JSON export and re-import between devices.
Built to the same shape as our other field-compliance logs, so if your crew already uses one, this one reads the same on day one.
It does not file anything with the BLM, does not decide which of your measurement points are FMPs, does not certify a device or approve a measurement plan, and does not replace 43 CFR subpart 3175, Onshore Order 5, API 14.3 or your own written procedure. It records what was inspected, by whom, when and what was found, keeps the four clocks from the published frequency table, and prints that record in the shape the verification report asks for. The exposure figure is indicative only, not a penalty calculation.
Everything stays on your device. Nothing is uploaded, no account is created, and the app keeps working when the lease road has no bars.