agentleFS
equinorequinor/neqsim-community-skills/skills/field-development/neqsim-psc-bid-economics-screening/SKILL.md

neqsim-psc-bid-economics-screening

Skill4 starsChanged 5 months agoApache-2.0View on GitHub

Educational PSC exploration-block bid screening: royalty, capped cost oil, profit-oil split, income tax, signature bonus and exploration programme, with EMV and the break-even offered profit-oil share. USE WHEN: judging a bid-round offer, asking how much State profit-oil share a block can bear, or comparing a near-field tie-back with a stand-alone case before any discovery exists.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No per-well productivity, local-content obligations or partner carry.

    line 85
  2. Distinctive:

    Not suitable for a bid decision without qualified commercial and fiscal review.

    line 86

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

PSC Bid Economics Screening

Use this skill to put a number on a Production Sharing Contract bid before there is a discovery. The bid variable is the offered State share of profit oil, so the useful answer is the break-even share at which the expected monetary value (EMV) is zero, and the headroom between that and the offer.

When to Use

  • A bid-round block must be judged on value, not volume.
  • A near-field tie-back and a stand-alone concept need the same fiscal wrapper.
  • An agent needs a quick "can the block bear this offer" answer to scope a deeper study.

Inputs

  • production_mmbbl, capex_musd, opex_musd: yearly development profile starting the year after discovery, at 100%.
  • profit_oil_share_offered: State share of profit oil, the bid variable.
  • chance_of_discovery: probability of a developable discovery.
  • working_interest, signature_bonus_musd, exploration_program_musd, discovery_delay_years.
  • volume_scales and volume_weights: optional P90/P50/P10 outcomes given a discovery, for example scales 0.6/1.0/1.5 with weights 0.3/0.4/0.3.
  • Model terms: oil_price, discount_rate, royalty_rate, cost_oil_cap, tax_rate, depreciation_years, loss_offset_cap, optional price-linked share step.

Outputs

  • emv_musd, pv_development_given_discovery_musd, pv_pre_discovery_cost_musd.
  • break_even_profit_oil_share, share_headroom, government_take.
  • bid_verdict: value_creating, thin_headroom (headroom below 0.05) or negative_emv.
  • assumptions.

Engineering Method

Per development year: royalty on gross revenue; cost oil is the lower of the cap times net revenue and the unrecovered cost pool; profit oil is split by the offered share; contractor income tax applies to contractor revenue less OPEX and straight-line CAPEX depreciation, with losses offset up to a cap. The signature bonus is not cost recoverable. The bonus and exploration programme are paid in every outcome; development only on discovery. EMV equals the pre-discovery cost plus the chance of discovery times the expected development value.

The default terms are generic public placeholders. Replace them with the terms of the actual bid-round contract before reading the numbers as anything but a screen. The model does not represent a contract-compliant calculation, per-well productivity tables, local-content obligations or partner carry.

Python Usage Pattern

from psc_bid_economics_screening import PscBidModel

model = PscBidModel(oil_price=70.0, discount_rate=0.10,
                    price_share_steps=[(60.0, 0.05)])   # optional contract price-band table, from the contract only
result = model.evaluate(
    production, capex, opex,
    profit_oil_share_offered=0.25, chance_of_discovery=0.30,
    working_interest=0.70, signature_bonus_musd=20.0, exploration_program_musd=60.0,
)
print(result.bid_verdict, result.break_even_profit_oil_share)
rows = model.tornado(0.20, production_mmbbl=production, capex_musd=capex, opex_musd=opex,
                     profit_oil_share_offered=0.25, chance_of_discovery=0.30)   # largest swing first

For P10/P50/P90 EMV and the probability of loss use the Java PscBidEconomics.monteCarlo(samples, seed, priceSigma, volumeSigma, capexSigma): price, volume and CAPEX get mean-preserving lognormal factors, the dry outcome is counted in the probability of loss, and a fixed seed gives repeatable results. The Python class and the Java class agree on the deterministic EMV, break-even share and price-band results (pinned in the Java tests).

Validation Checklist

  • Contract terms (royalty, cost-oil cap, tax, price-band table) come from the actual bid-round contract, not the defaults.
  • The development profile starts the year after discovery and is at 100 percent, with working interest applied once.
  • The bonus and exploration programme are counted in every outcome, including the dry one.
  • Break-even share reproduces zero EMV when fed back as the offered share.
  • Python and Java PscBidEconomics give the same deterministic EMV on the same inputs.

Common Mistakes

SymptomCauseFix
EMV looks too highExploration programme or bonus charged only on successCharge both in every outcome
Headroom is negative at a sensible offerDefault placeholder terms used as contract termsReplace with the real contract terms
Volume risk looks symmetricP90/P50/P10 weights do not sum to 1Check volume_weights
Value credited to a tie-back that does not fitHost ullage ignoredRun HostSynergyScreening first

Limitations

  • Generic public placeholder terms; not a contract-compliant calculation.
  • No per-well productivity, local-content obligations or partner carry.
  • Not suitable for a bid decision without qualified commercial and fiscal review.

Related NeqSim Functionality

  • neqsim.process.fielddevelopment.economics.PscBidEconomics — the validated Java class with the same mechanics, plus Monte Carlo and tornado; prefer it inside NeqSim studies.
  • neqsim.process.fielddevelopment.tieback.HostSynergyScreening — host ullage cover and tie-back synergy value, credited only when the demand fits the host.
  • neqsim.process.fielddevelopment.economics.TaxModelRegistry (BR-PSA) and CashFlowEngine — full-life fiscal cash flow once a concept exists.
  • Chain with neqsim-reservoir-model-builder, neqsim-brazil-presalt-analogue-basis, neqsim-asset-value-npv-screening and the frontier-block-bid-agent.

References

  • Johnston, D. (1994), International Petroleum Fiscal Systems and Production Sharing Contracts, PennWell, for the royalty, cost-oil and profit-oil mechanics.
  • The production sharing contract of the bid round being screened (the only authority for the terms).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.