Methodology
A written method, with your numbers in it.
BarrierLedger applies a versioned method profile for each well type, built on the two-barrier philosophy. Your integrity policy sets the limits, bands and cadences; the platform applies them consistently and records the basis of every result.
Reference set
Built on the standards integrity engineers use.
The first method profile adopts these references, in this order of precedence: your own integrity policy first, then the standards.
- 01
Your integrity policy
Takes precedence
- 02
NORSOK D-010
Well barrier philosophy
- 03
ISO 16530-2
Operational phase
- 04
BSEE 30 CFR 250
US OCS casing pressure
The method profile
A profile is a document the platform follows.
One profile covers one well type. It defines the rules end to end, so an assessment can be explained without reading the code that produced it.
Governing limit
Which operator-supplied MAWOP/MAP value governs each monitored annulus, where it came from and how competing limits are resolved.
Assessment rules
How a reading is compared with the governing limit, which inputs each rule requires, and the outcome each rule can produce.
Outcome precedence
The distinct statuses and the precedence used to derive an overall well result from the applicable annulus outcomes.
Trend and SCP handling
The signed rules for sustained pressure rises and sustained casing pressure (SCP), including the required inputs and the diagnostic flags the engine records.
Stale, missing and test inputs
The reading windows, grace periods and required fields that determine whether the rules can run without guessing.
Worked examples and versioning
Worked examples exercise boundary conditions, and every assessment stores the profile and tenant-settings versions it used.
The well register
Barrier structure stays attached to the well.
Strings, annuli and barrier elements live in the register, and the schematic and barrier envelopes are drawn from those recorded fields for every trajectory type.
What the envelope model carries
- Barrier elements are recorded against the relevant well and wellbore.
- Monitored annuli and readings remain associated with their well hierarchy.
- The trajectory is computed from the deviation survey by minimum curvature.
- The schematic is rendered from registered strings, cement tops, packers and completion equipment.
- Primary and secondary envelopes are overlaid in the NORSOK D-010 colour convention.
- Missing schematic inputs are shown as gaps rather than filled with assumed values.
Status, and where it comes from
One annulus, start to finish
Six steps, and none of them skip the record.
This is the path a single annulus takes through an assessment. Every step contributes something a reviewer can point at.
- 01
The governing limit
The annulus’s MAWOP/MAP value is read as master data, with its source, its date and the reference behind it. Where several limits apply, the assessment compares against the governing limit and records which one governed and where each came from.
- 02
The profile’s rule applied
The reading is assessed against the rule the profile sets for that well type, held as data rather than as a constant in the engine. The profile records what the rule is, where it came from, and which version applied.
- 03
A sustained rise
A sustained rise across the profile’s configured window produces its defined outcome and diagnostic flags, distinct from a single reading. The trigger and required inputs come from the signed method and tenant settings.
- 04
One outcome, with its effect
One outcome is recorded for each assessed annulus, with its flag and effect on the well-level result.
- 05
Roll-up to the well
Applicable annulus outcomes roll up to the well through the profile’s defined precedence; a profile is never applied to a different well type.
- 06
Provenance
The run keeps its input and source-file hashes, method-profile and tenant-settings versions, engine build and schema version.
The engine uses explicit inputs and the applicable profile/settings versions. A saved assessment run retains its own input and version metadata; a later run does not rewrite those inputs.
Where the numbers come from
Values are sourced and versioned.
The method has documented defaults; operator-supplied limits and approved tenant-policy changes are preserved with their provenance.
Your limits, with their provenance
Each MAWOP/MAP is imported or entered as master data with its source, date and reference, and every assessment records which limit governed.
Your policy, on signed defaults
Bands, cadences, grace periods and tolerances are tenant settings with documented defaults. Changes go through request and approval and create a new settings version.
Gaps are named, never filled
If a required input is missing, the platform reports the gap as a data-quality flag rather than deriving an engineering value to fill it.
A profile for each well type
A method profile is specific to its stated well type, and a result is never carried across types. The operator decides which regime applies to each well.
What the method does not do
Worked examples before engine code
Versioning
An assessment keeps the versions it used.
Each run records its method-profile and tenant-settings versions. An approved tenant-policy change does not rewrite the basis of a prior run.
A settings version, not a silent edit
Approved tenant-policy changes create a new settings version. Earlier assessments keep the version they used and are not reinterpreted when policy changes.
Assessments keep their version
A completed assessment records the profile version it used and is not silently reinterpreted when the profile moves on. Comparing two versions is an explicit act, not a side effect.
The profile is the authority
The engine implements the profile version it was given; it does not improvise around a gap in it.
Reconciliation, in the same discipline
The method you can read
Read the method summary.
This page describes what a method profile defines. The method summary sets out the barrier model, what an assessment reads, the outcomes and their precedence, SCP handling and provenance for platform producer wells, in plain language, so your integrity engineer can check the logic before any data is shared. It does not publish numerical thresholds or bands: those are set in the tenant’s policy.
The PDF is sent through the enquiry form. We reply by e-mail within one business day.
Methodology FAQ
Questions about the method.
“Our wells are unusual.”
The method for each well type is written down and versioned, and your integrity policy sets the bands, cadences and tolerances within it. Every assessment records the profile and settings versions it used, so unusual wells are a configuration conversation, not a code change.
Which well types can be assessed?
Each well type — producer, injector or disposal well — is assessed against a method profile written for that type, and one profile never serves another, so a result is never carried across types.
Where does the MAWOP or MAP value come from?
Each monitored annulus carries its own MAWOP/MAP value as master data with its source, date and reference, imported with your register or entered directly. Readings are assessed against that value and the bands in your method profile.
What happens when a well cannot be bled to zero?
Sustained casing pressure has its own exception path in the method. The platform records the applicable flag and outcome against the annulus, using the criteria set in your tenant policy, and the case stays visible in the monthly review until it is resolved.
“What about regulators?”
BarrierLedger keeps the operator’s register, test records, reviews and assessment history, and produces in-house integrity reports from them. It does not file anything with a regulator or certify compliance; submissions and official well records remain the operator’s responsibility. The regulations page summarises what each regime asks, with its public sources.
Let's talk
Bring us the policy behind your limits.
Send the register and the document your MAWOP/MAP values come from. We will walk through how your policy maps onto the method profile and where your data needs attention.