About
BarrierLedger is a FEEC product.Built by engineers who sign the method.
Front End Engineering Consultancy Limited is an independent engineering consultancy. BarrierLedger is the well integrity product in its software family, built and supported by the same engineers who write and sign the integrity method profiles it applies.
Why we built it
Integrity lives in a spreadsheet, and the reasoning lives in someone’s head.
Operators managing tens to hundreds of wells usually run well integrity out of a register that has grown over years. It works — until the person who maintains it is on leave, or until someone asks how a status was decided and the answer is a memory.
The enterprise alternative is real software, but it is sized and priced for portfolios an order of magnitude larger, with implementation programmes to match. The gap in the middle is where BarrierLedger sits: the discipline of a proper integrity system, on the registers operators already keep, without a two-year programme.
The engineering position is simple. An integrity status that cannot be explained is not much better than a guess, and a threshold that a vendor invented is worse than no threshold at all. So the platform carries your rules, records where they came from, and shows its working.
How we work
Four commitments that shape the product.
The method is written first
No engineering value is invented in code. Bands, trend rules, tolerances and test frequencies come from a written profile sourced from the operator’s own integrity policy, and a profile change creates a new version.
A status has to be explainable
If someone asks why a well is yellow, the answer should be in the record: the reading, the governing limit and its source, the profile version and the rule that fired.
Acceptance is a reconciliation, not a demo
A pilot is accepted when your own register is reproduced within a tolerance agreed in writing, signed off by your integrity engineer — not when the screens look convincing.
The operator stays responsible
BarrierLedger produces in-house integrity reports. Regulatory submissions, official well records and the decision to declare a well safe remain with the operator.
Engineering services
The platform, and the people who wrote the method.
Services stand on their own. An operator who is not ready to subscribe can still have the register assessed properly, and a pilot is the bridge between the two.
Register health check
A fixed-fee assessment of the register you already keep: data quality, the MAWOP/MAP basis behind it, and where it stands against the method. The usual first step.
Full integrity assessment
A complete assessment across the agreed wells, with acceptance criteria agreed in writing first and a signed-off reconciliation against your own figures.
Method profile development
Turning your integrity policy into a versioned method profile for a well type — including the exception policy, test scheduling and tolerances. The profile is signed by its method owner before it is used.
Reconciliation and parallel runs
Running the platform alongside your current process and reporting every difference with its reason, so the change is evidenced rather than asserted.
What FEEC does not claim
The software family
Start with a conversation and a register.
Tell us how integrity is managed today and where the MAWOP figures come from. We will tell you what the platform can assess, what it cannot, and what a pilot would have to reproduce.