Map
Map source fields to the project structure and reuse the mapping on refresh.
Meridian · Data & Integrations
Use the project data you already have.Keep the source visible.
Bring existing assumptions, production, cost, schedule, actuals and reference data into Meridian. Inputs are mapped, validated and reconciled before they enter the model.
Inputs
Bring the data in.
Files and structured extracts are read directly — XLSX, CSV and standard system exports. Direct system connections are scoped against the client’s data estate during implementation. The source system remains the system of record.
Subsurface and production
Production forecasts, historical production, reserves and resource positions, and well data from reservoir and production systems.
Cost and finance
Cost estimates, budgets, commitments and actual expenditure from cost systems, ERP and accounting extracts.
Schedule and project controls
Activities, dependencies, milestones, baselines and actual progress from existing scheduling tools.
Market and commercial
Price decks, forward curves, differentials, tariffs, exchange rates and contract terms held as dated records.
Licence and fiscal
Licence terms, work commitments and fiscal regime records, with effective dates retained.
Documents and public disclosures
Candidate assumptions extracted from contracts, licences and technical studies for review, plus public company disclosures.
Import control
Validate it before it enters the model.
Record the mapping, validation result and source reference with the import so calculated outputs remain traceable to the accepted input.
Validate
Check type, unit, range and completeness; report failures as exceptions.
Reconcile
Reconcile imported totals to source and record unresolved differences.
Approve
Accepted data enters the project with its source, extract date and approver.
Outputs and integrations
Send the outputs back. Keep the lineage.
Outputs retain the project, case, version, status and source context needed to reconcile them to the model.
Supported now
Reports and spreadsheets
Report packs and supporting tables, reproducible from the version that issued them.
Structured exports
Period cash flow, fiscal detail, schedule detail and assumption registers in machine-readable form.
By implementation scope
APIs and webhooks
Programmatic access to cases, results and registers, and notifications when approved data changes.
Enterprise systems
Exchange with identity, document, workflow, finance, operations and project-control systems where required.
Implementation
Stood up against the existing estate.
Each step is confirmed with the people who own the data and the numbers before the next begins.
Map
The data estate: sources, owners and formats.
Configure
Modules, calculation conventions and fiscal records for the organisation.
Reconcile
First results against the numbers the business already trusts.
Deploy
Access, identity and environments confirmed with IT.
Maintain
Refreshes, new sources and configuration changes as the estate evolves.
Integration scoping
Name what needs to connect.
Tell us the source, the target and the data that needs to move.