Landfill Gas Wellfield Software: Why 400 Monthly Readings Still Miss the Correction Clock

What actually happens on a monthly monitoring round

A gas technician starts a route at 6am with a GEM analyser, a bag of wellhead tools and a printed map that is one cell layout behind reality. He pulls methane, oxygen, balance gas, temperature, static and applied pressure at each wellhead, adjusts a valve where the reading calls for it, writes a note about the wet well on the north slope, and moves on. Four hundred wells across a route takes days. Back at the trailer, the analyser gets docked, the readings export to a file, and someone opens last month's workbook to paste them in.

The moment the exceedance matters is the moment the reading is taken, standing at the wellhead. The moment the exceedance is noticed is a week later, in a spreadsheet, by a person who was not there. That gap is the entire problem this software category exists to close, and it is why a compliance calendar built from paste operations keeps producing the same finding at audit.

The operational standards you are measured against are specific and mostly public. Wellheads are expected to hold negative pressure, stay under a temperature limit that has historically sat at 55 degrees Celsius, and meet a nitrogen or oxygen criterion. Surface emission monitoring is walked on a grid pattern across the cover with a methane instrument and a 500 parts per million action level. When a wellhead reading fails, an initial corrective action clock starts and it is measured in calendar days, not business days, and it does not pause because the technician who took the reading is on a different site this week. Your permit and the applicable subpart set the exact numbers, and your consultant is the right person to confirm them, but the shape is always the same: a reading creates an obligation with a deadline attached to it.

Why the spreadsheet fails at exactly the wrong moment

A workbook holds readings. It does not hold obligations. Nothing in a spreadsheet knows that well GW-114 went positive on the 12th, that a valve adjustment on the 15th counts as the initial corrective action, that the recheck on the 19th still failed, and that the well is now on a path toward a system expansion decision with its own timeline. That chain exists in a gas technician's memory and in a folder of field notes.

The second failure is the well identity problem. A landfill wellfield is not stable. Wells are drilled, deepened, abandoned, converted from vertical to horizontal collection, taken offline during filling, and renumbered when a cell is closed. A spreadsheet column named after a well is not the same object as the physical well, so trend history breaks every time a well is reworked. When a regulator asks for two years of readings at a location, you are reconstructing it from tab names.

The third failure is that the tuning logic never gets written down. Every wellfield has a specific personality: leachate seeps in a certain area after rain, one flank goes hot because of old waste, a section of cover was rebuilt and now runs oxygen high. The person who knows all of that has been on site for eleven years. When he retires, the readings survive and the interpretation does not.

Where SCS eTools, LandTec and LoCI stop

These are real products and each is genuinely competent at the slice it owns. Judge them on scope, not on quality.

• QED LandTec sits closest to the instrument. If your field data problem is capturing readings off a GEM series analyser cleanly and getting them into a structured form, that ecosystem does that job well. What it is not is the site's compliance system of record, and it does not naturally hold your corrective action clocks, your SEM route evidence and your gas plant reconciliation in one place.
• SCS eTools is a field data and compliance reporting product that grew out of an engineering services practice. It is a reasonable fit if your monitoring is largely delivered by that practice and your reporting matches the standard forms. It is a weaker fit when you want your own workflow, your own escalation rules, and your own data sitting in your own warehouse where your revenue team can join it to plant output.
• LoCI Controls is hardware led. Automated wellhead control and remote tuning is a real capability and on the right sites it changes the labour model. It is a tuning and optimisation layer on the wells it instruments, not the record that proves your monthly monitoring obligation was met across every well including the ones with no controller on them.

The common gap is the same in all three cases: none of them was designed around your permit as a data structure. Your permit is where the limits, the frequencies, the clocks and the report contents actually live, and it is specific to your site.

What a custom wellfield build has to include

Start with the well as a durable object with a life history. Every wellhead has a location, a construction record, a depth and screened interval, a status timeline that includes offline and abandoned states, and a link to the cell and the waste it draws from. Readings attach to that object forever, so a rework never breaks the trend.

Then make limits configurable rather than coded. Temperature, pressure, oxygen and balance gas criteria, the parameters your permit sets, and any higher operating value approval you hold, all live in a versioned limit set with effective dates. When a rule interpretation changes or your permit is renewed, someone updates a limit set and the historic evaluations stay evaluated under the rules that applied on that date. This one design decision is the difference between a system that survives a permit renewal and a system that gets rebuilt.

The exceedance engine is the core. A reading arrives, gets evaluated against the limit set that was in force, and if it fails it creates an obligation with a due date, an owner and a required evidence type. The technician sees it on the handheld before he leaves the wellhead, not a week later. A supervisor sees an aging queue with the clock visible. A recheck reading resolves it or escalates it. Nothing sits in a state where the only person who knows about it is on annual leave.

Field capture has to work with no signal, because half a landfill has none. That means an offline first mobile app with route sequencing, the last reading and last adjustment visible at each well so the technician has context, photo capture for wellhead condition, and a sync that reconciles cleanly when two technicians worked the same route. Analyser import is a parsing job against the specific files your instruments produce, and it is worth doing properly because manual entry of five parameters across 400 wells is where the transcription errors come from.

Surface emission monitoring is its own module and it is mostly about evidence. The walk has to be recorded as a GPS track against the required grid spacing so you can show coverage, exceedance points get pinned with a reading and a photo, remonitoring after cover repair is scheduled automatically, and the whole thing exports as the map and table your report needs. Agencies increasingly want to see the track, not a signed statement that the walk happened.

Finally, connect gas to money. Flare and plant meters, methane concentration, flow, and the wellfield readings that explain them belong in the same data set. When the RNG plant sees a nitrogen rise, the operator should be able to look at which wells moved in the last two rounds rather than opening a separate system. If you sell environmental attributes, the reporting behind those revenues depends on the same measurement chain, and it is worth building the chain once.

Cost, timeline and what moves the number

A first release covering the well object model, analyser import, the exceedance engine with corrective action tracking, the offline field app and the monthly monitoring report runs $55,000 to $110,000 over 10 to 14 weeks. That is a working system your technicians use on the next monitoring round, not a pilot. The full platform, adding SEM routes with GPS evidence, condensate and leachate observations, flare and plant reconciliation, Title V style report assembly and dashboards for the gas revenue side, runs $150,000 to $320,000 phased over 6 to 10 months.

What pushes the number up on a landfill build: multiple sites with different permits and different applicable subparts, because each permit is a limit set plus a report format and both need testing. Automated wellhead controllers, because reconciling controller telemetry against manual readings is real integration work. SCADA or historian access at the plant. Any requirement to submit through a state electronic reporting portal. And the honest one, which is data migration: five years of readings across renamed wells in inconsistent workbooks is a week of engineering plus days of your gas manager confirming which GW-114 is which.

What keeps it down: start with one site, the monthly round and the exceedance clock. That is where the violation risk sits and it is the smallest useful system.

When you should not build

Do not build if you run one closed site with a small passive system and no energy project. The compliance load is real but it is a spreadsheet sized problem and a consultant handles the reporting. Do not build if your monitoring is fully outsourced to an engineering firm that carries the compliance obligation contractually and you have no plan to bring it in house, because you would be paying to duplicate their system.

Build when two or more of these are true. You operate more than one wellfield under more than one permit. Your gas feeds an energy or RNG plant where nitrogen and oxygen have revenue consequences and not just compliance ones. You have taken a finding on corrective action documentation or SEM evidence in the last three years. Your wellfield knowledge lives in one person. Or you are being asked for data by a plant partner or an attribute programme and you are assembling it by hand each quarter.

How to choose a developer for this

Ask them to model your permit before they quote. A developer who understands this work will ask which subpart applies, whether you hold a higher operating value approval, what your SEM frequency is, and how many wells changed identity in the last two years. A developer who starts with a screen mockup has not understood that this is a rules and evidence system with a field app attached.

Ask specifically how corrective action clocks are modelled. If the answer is a status field on a reading, they will build something that cannot show a regulator the chain from failed reading to action to recheck. The correct answer involves an obligation object with its own timeline, independent of the reading that created it.

Ask what analyser files they have actually parsed and what happens when a technician takes a reading twice by mistake in the field. The second question tells you whether they have built offline sync before.

Ask who owns the code, the database and the cloud accounts, and get it in writing before kickoff. Your monitoring history is a regulatory record with a retention obligation and it should never sit inside a vendor account you cannot access. At Digital Heroes the client owns the repository from the first commit. The next step is simple: send us one month of raw analyser exports and your current monitoring report, and we will tell you in a week what the exceedance engine has to look like for your site.