Pangea, Part II
1. Commercial Purpose and Placement
Pangea connects a property, project, producer or Joint Operating Committee requirement with the market. Its commercial purpose is to improve the ability to obtain suitable capabilities and resources on terms that support profitable development and operation.
Price is one part of that assessment. Availability, technical suitability, reliability, delivery timing, installation cost, operating consequences, maintenance support and the supplier’s ability to perform may materially affect the result. Pangea should make these factors available to the responsible decision-makers without imposing a universal purchasing formula.
Business Operations Management supervises the process. Planning establishes or refines the need. Capability Deployment organizes the engagement of suitable capabilities. The Marketplace sub-module manages the commercial interaction and continuity with the domain Marketplace Modules. Accounting Voucher, Work Order, Industrial Command & Control and other responsible functions retain their established responsibilities. S01
A producer may bring an independently authorized requirement into Pangea. A Joint Operating Committee requirement retains the representation and decision rights of its governing arrangements. The interface must not assume that every participant is an employee of a designated operator or that every engagement concerns a Joint Operating Committee.
The market should also accommodate firms from other industries that supply oil & gas participants. Their participation depends on the transaction’s requirements and their approved role. A supplier need not become an oil & gas producer to demonstrate equipment or fulfil an order.
2. People, Representation and Discovery
The individual and the represented party
The starting point is a person acting in a known capacity. Synallagi’s persistent identity connects that person with separately approved assignments, clients and represented parties. An engineer may serve several producers or Joint Operating Committees. The selected assignment determines the information and actions available in the current engagement.
The contracting party, beneficiary, represented party, funding participant and owner of confidential information may differ. Pangea must keep those relationships explicit. An invitation to a virtual meeting establishes participation in that meeting; it does not establish contractual or expenditure authority.
A participant should be able to see the commercial capacity in which another participant is acting, subject to permitted disclosure. A supplier representative’s authority to describe a product can differ from their authority to accept a price or delivery obligation. A field agent’s authority to report an observation can differ from their authority to accept a milestone.
Discovery and useful encounters
Discovery includes deliberate searches and encounters that expose useful alternatives. Participants may browse a supplier’s premises, follow a property requirement, examine a capability listing or be introduced to a specialist. Pangea should support the serendipity and personal understanding described in the earlier marketplace vision. S04
Search should consider the requirements relevant technical and commercial characteristics. A recommendation should explain the factors that made it relevant and distinguish sponsored placement, if introduced, from technical qualification. A published capability is an invitation to investigate; it is not a reservation or commitment.
A requirement may be met through capabilities already contributed under a Pooling arrangement or through an external market engagement. Pangea should connect with Capability Deployment so those alternatives can be considered within their agreed availability, recovery and authority. A producer’s capability information remains in Research & Capabilities; selective publication through Knowledge & Learning to a particular Joint Operating Committee does not authorize public marketplace disclosure. S01
Supplier profiles should connect the appropriate technical, commercial, field and billing contacts. Qualification evidence should identify its issuer, scope, currency and expiry where relevant. The responsible purchaser determines whether the evidence is sufficient for the contemplated engagement.
Private bids, producer costs, geological information, designs and unpublished capabilities must remain within their permitted audiences. Discovery and recommendation must operate within those same boundaries.
3. The Marketplace Interface
Two coordinated screens
The primary Business Operations Management workstation presents two screens that remain available together. The first is the Pangea working environment: the specialist’s domain, a selected client or property, or the shared marketplace. The second presents the financial information for the properties and responsibilities selected in that context.
The financial screen presents actual, factual, standard and objective accounting, with an identifiable reporting period and source. The specialist can investigate profitability, the cost of work, commitments, accruals and emerging variances, and connect those results to the transactions that explain them. Estimates, work-in-progress assessments and proposed outcomes remain visibly distinct from confirmed actuals.
Selecting a property or Synallagi coordinates the two screens. The engineer can move from an adverse financial result to its underlying work and obligations, then configure the appropriate response in Pangea. As the response is performed and accounted for, its results appear in the financial view. A financial variance identifies a matter for investigation; technical diagnosis and field direction remain with the responsible specialists.
Contextual actions and working domains
A right-click on a relevant item, person, obligation or property exposes the actions available in that context. These can include designing or amending the transaction, defining a Work Order, issuing a Job Order through the applicable authority, arranging an inspection, approving a permitted substitution or issuing an authorized payment. The menu identifies the selected client, transaction, subject and consequence of the action.
The specialist’s professional domain provides an overview of permitted assignments and matters requiring attention. A client’s domain provides that client’s working context. The marketplace supports discovery and interaction with the invited or permitted parties. Moving between these domains preserves the appropriate information and authority boundaries; a shared meeting displays the people and information relevant to its purpose.
The same controls support direct, conversational and mobile actions. They should avoid repeatedly asking the specialist to approve work already covered by an effective instruction or delegation. A new decision is required when the applicable authority, material terms or defined conditions require one.
Connected ways of working
Pangea should offer several ways to reach the same authorized transaction:
- A spatial view of a supplier, property, asset or proposed installation.
- Search, lists, maps and comparison views.
- Conversation or voice assistance.
- Direct access from a requirement, AFE, engagement or existing commitment.
- Mobile access for people undertaking physical work.
These views share the transaction’s business meaning. Routine users should be able to reach an offer or pending decision directly. Spatial participation should be available when it improves understanding, inspection of alternatives or personal collaboration.
A shared session should show the current participants, represented parties, relevant object and status of the discussion. Participants must be able to distinguish an informal proposal, a revised offer, a request for approval and an accepted commitment.
What an object represents
Selecting equipment must identify the actual item or product configuration being discussed. Its authoritative record should provide the relevant specifications, drawings, quantities, units, condition, supplier, availability basis and applicable commercial offer.
An illustrative rendering, a scan of an existing item and an engineering model have different evidentiary uses. The interface must identify the source and status of the representation. A visually convincing model does not establish dimensions, compatibility, ownership, condition or availability.
World Labs describes Marble as generating and editing navigable 3D environments from several types of input, including text and images. It also explains that missing details can be invented during generation. That makes this technology a candidate presentation capability; suitability for Pangea’s engineering and commercial uses requires evaluation. S09
Purchase against AFE
The action opens a transaction view containing the selected item, offer, buyer, beneficiary, property or project, relevant AFE and proposed terms. It then identifies the outstanding technical, contractual and funding requirements.
The interface should explain what the next action will accomplish. Preparing a request, submitting it for approval, accepting a commitment and releasing a payment have different consequences. A user’s approval must refer to the specific terms presented.
A change of item, quantity, price, beneficiary or other material term must be visible before the affected decision is taken. The interface should provide a clear path from the negotiated agreement to the underlying documents and responsible people.
4. Designing Transactions
Engineers and geologists design their individual Synallagi through Pangea, configuring the requirements and relationships needed to accomplish their work. Accounting Voucher’s Transaction Design Interface supplies the reusable business and accounting designs developed by accountants and the relevant specialists. Pangea presents those capabilities in the engineer’s or geologist’s working context. The specialist’s transaction design and the accounting design operate on the same Synallagi. S03
The design must establish what is transferred, how the parties identify and measure it, how it is valued, and how compensation occurs. Each specialist domain retains the knowledge required to perform its work; the transaction specifies the information and evidence that must pass between domains.
For a substantial equipment purchase, the design should express the following arrangements:
Pangea should let the specialist assemble a suitable transaction design and inspect its dependencies as it develops. Technical constraints, participants, financial arrangements and alternative paths must be captured as usable requirements, not left only in conversation. An unusual arrangement may require the responsible specialists to develop or amend a reusable design before the affected action advances.
The template has its own version and approval basis. A transaction retains the design version under which it was accepted. Improvements to a template must not silently change existing contracts.
The design coordinates commercial and accounting consequences. Technical instructions for physical work remain with the responsible operational functions.
5. Offers, Negotiation and Purchase Orders
Technical and commercial agreement
Participants should be able to compare compliant offers, record exceptions and request clarification. Technical evaluation and commercial negotiation may proceed together, but the decision record must identify unresolved requirements.
An accepted offer must identify the parties and the precise basis of acceptance. Conversation summaries can help prepare this record. An AI-generated summary or an attendee’s interpretation must not substitute for the acceptance required by the agreed process.
The supplier must confirm the configuration, capacity and delivery obligations it is actually undertaking. Availability displayed during discovery requires revalidation when reservation or commitment occurs.
Purchase Order configuration
The Capability Deployment reference makes Purchase Order functionality discretionary, selected by the producer and excluded from standard Synallagi configuration. This draft selects that functionality for the high-value purchasing scenario requested for Pangea. It does not change the general configuration rule. S01
Before such a transaction can proceed, the applicable organization must have adopted and configured the Purchase Order controls. Where a different transaction class uses another governing agreement, its equivalent contractual and approval requirements must be defined explicitly. The Petroleum Lease and Financial Marketplace Modules will establish their appropriate instruments.
Purchase Order controls remain in the Accounting Voucher environment. Pangea presents and coordinates their use. The Purchase Order number does not replace an AFE, Cost Center or Lease charge code.
Terms to be captured
The Purchase Order and incorporated documents should address:
- Product configuration, quantity, unit of measure, condition and required documentation.
- Agreed price, currency, taxes, freight and other separately identified charges.
- Assembly or manufacturing milestones and required completion dates.
- Inspection arrangements, witnesses, methods, evidence and acceptance authority.
- Delivery location, shipment conditions, responsibility for transport and handling, and agreed treatment of title and risk.
- Installation, commissioning and site access responsibilities were included.
- Prepayments, progress payments, partial payments, holdbacks and final payment conditions.
- Warranty, defects, change control, cancellation and dispute arrangements.
These terms do not guarantee performance merely because they have been recorded. They establish obligations, evidence requirements and the agreed responses when performance differs from the contract.
Accepted changes require an amendment linked to the affected version. The record should make their effects on price, budget, schedule, financing, field assignments and prior acceptance understandable.


