Field Development Plan — Tiber

Summary

Tiber is part of the sanctioned Tiber-Guadalupe shared-host development; hub totals are not assigned to Tiber alone.

Historical source snapshot, not a current operating-status assertion or a sanctioned engineering design. Missing inputs are preserved as unknown.

Revision history

RevisionDateWhat changed and why
Initial2026-10-19 Documented the reported development concept and evidence gaps to provide a field-level portfolio reference.
12026-10-20Formatted whole-number inputs without decimal padding for readability.

Engineering rationale

The announcement describes a new production hub with Tiber wells and a Guadalupe tieback, reusing Kaskida platform and subsea designs. Design reuse is the reported rationale for delivery efficiencies; no independent cost saving or feasibility calculation is made here.

Field parameters

InputValueSource and scope
Operator at source dateBPS1: Announcement identifies the development as BP operated.
Reported development conceptsemisub_fpsS1: Announcement identifies a floating platform using Kaskida designs; semisubmersible classification is from reports/lower_tertiary/lifecycle/_facts.json, tiber.host_type (repository snapshot).
HostShared Tiber-Guadalupe floating production platformS1: Announcement covers the combined Tiber-Guadalupe hub, not a standalone Tiber facility.
Water depth (m)UnknownRequired input; not established by the cited evidence.
Wells (scope stated below)6S1: Scope states six Tiber wells plus a separate two-well Guadalupe tieback; only Tiber wells enter this field count.
Designed peak capacity (boe/d)UnknownRequired input; not established by the cited evidence.
Reported oil capacity (bbl/d; not a boe/d plateau)80000S1: 80,000 bpd crude capacity belongs to the combined hub; no Tiber boe/d plateau is inferred.
Recoverable resources (MMboe)UnknownRequired input; not established by the cited evidence.
Actual first-oil yearUnknownRequired input; not established by the cited evidence.

Architecture

Tiber wells and the separate Guadalupe tieback feed one floating production platform. The semisubmersible classification follows the committed lifecycle research; the opened announcement establishes a floating platform and reuse of the Kaskida design, not a detailed hull specification.

Well coordinates, manifold counts and interconnection lengths are required inputs for a detailed layout. Layout: NOT_EVALUATED; no assumed geometry is drawn.

Recommended concept shortlist

NOT_EVALUATED. The reported concept is documented above; a comparative ranking requires sourced screening limits and criteria weights.

Economics and execution

NOT_EVALUATED. No cost or investment return is inferred from facility capacity. Required inputs include scope-matched capital cost, operating cost, production profile, prices, discount rate and schedule. Equipment qualification and installation feasibility also require project-specific design evidence.

Known limits and way forward

The reported oil capacity and resource totals cover the combined hub. Only the Tiber well count is mapped to FieldConcept; hub resources and forecast startup remain null in Tiber field inputs. Obtain the host design basis, metric depth and scope-specific production allocation before detailed assessment.

Sources

Input citations refer to the source dates below. Capacity, planned well count and forecast startup are not measured production.