Skip to content
ATLAS
ATLAS platform

An integrated environment for drilling engineering.

ATLAS is not a set of calculators bolted together. It is one environment in which a well is planned, engineered, analysed, optimised, supported through execution and reviewed afterwards — with the engineering information behind that work governed throughout.

  • Spreadsheets
  • Specialist applications
  • Vendor / manufacturer information
  • Engineering reports
  • Historical well data
  • Company procedures
  • Individual engineering workflows
  • Operational information

Integrated environment

One governed engineering context

ATLAS is designed so engineering inputs, analysis, assumptions and evidence sit in the same place, with their origin intact.

Platform structure

Four layers, one engineering context.

Each layer exists so the layer above it can be trusted: the workflow relies on governed information, and governed information relies on an organisational platform that controls it.

  1. Engineering workflow

    The sequence engineers actually work through — planning, design, analysis, optimisation, execution support and review.

  2. Engineering intelligence layer

    Governed information, engineering models, operational context and historical learning available to every stage of that workflow.

  3. Governance and assurance

    Sources, versions, assumptions, reviews and approvals retained as structured records rather than as file conventions.

  4. Organisational platform

    Workspaces, roles, repositories and auditability so the environment fits an operating structure, not a single desk.

Each layer supports the layer above it

Engineering workflow

A continuous path, not a series of handovers.

The workflow is deliberately linear in intent — each stage inherits the context established before it, so engineering work is not restarted at every boundary.

  1. 01

    Plan

    Objectives, constraints and design basis stated once, in one place.

  2. 02

    Engineer

    Design work carried out with engineering methods and project context.

  3. 03

    Analyze

    Loads, hydraulics and mechanical behaviour tested against that design.

  4. 04

    Optimize

    Scenarios compared so a choice can be justified, not assumed.

  5. 05

    Execute

    Engineering intent carried into the operation with its context intact.

  6. 06

    Learn

    Outcomes captured as evidence for the next well.

Plan & design

Well architecture engineered with its design basis attached.

Trajectory, casing architecture and target geometry are developed inside a structured design environment. Objectives, constraints and assumptions stay attached to the well, so what the design is trying to achieve remains legible to whoever picks it up next.
  • Trajectory and wellbore architecture developed against stated objectives.
  • Casing and interval design held as project structure, not scattered files.
  • Design changes visible as changes, not as replacement documents.
TARGETSURFACE CASINGINTERMEDIATEKOP / BUILDSURFACE LOCATION
Trajectory · casing architecture · target geometrySchematic well trajectory showing surface location, kick-off point, build section and a geological target with casing shoe depths.
Engineering analysis

Mechanical behaviour examined against the current design.

Torque and drag, axial loading and drillstring behaviour are studied against the planned well and the assumptions recorded with it. The point is not a number in isolation — it is a result whose inputs and basis can be inspected.
  • Drillstring and BHA configurations analysed in project context.
  • Load and torque behaviour reviewed across the planned interval.
  • Inputs traceable to the source they came from.
DRILL PIPEHWDPBHABITLOAD →DEPTHTORQUEDRAG
Drillstring / BHA · axial load · torque profileDrillstring and bottom-hole assembly schematic beside a qualitative axial load and torque profile against depth.
Hydraulics & optimisation

Scenario comparison before decisions are committed.

Hydraulics, hole cleaning and mechanical optimisation studies let engineering alternatives be examined side by side within the operating window the well actually has, so a recommendation can be reasoned about rather than defended after the fact.
  • Circulating behaviour considered across the interval.
  • Hole cleaning treated as an engineering constraint, not an afterthought.
  • Alternatives compared under the same assumptions.
DEPTHPRESSURE →LOWER CONSTRAINTUPPER CONSTRAINTOPERATING WINDOWCIRCULATINGHOLE CLEANING CONSIDERED ACROSS THE INTERVAL
Operating window · circulating pressure · depthQualitative hydraulics operating window bounded by a lower and an upper operating constraint, with a circulating pressure profile between them.
Operational intelligence

Engineering context available during operations.

Operational information and historical results are surfaced next to the engineering basis, so activity on the well can be read against what was planned. Interpretation and action remain with the engineering and operations teams.
  • Design basis and assumptions visible alongside operational activity.
  • Historical wells available as engineering reference.
  • Context presented to people — no autonomous monitoring or action.
PLANNEDIN PROGRESSREVIEWEDCAPTUREDOPERATIONAL SIGNALDESIGN BASISASSUMPTIONSHISTORICAL WELLSCONTEXT PRESENTED TO THE ENGINEER — NOT AUTONOMOUS ACTION
Well state · operational context · engineering awarenessOperational context schematic: a well-state timeline with engineering context surfaced alongside operational activity.
Governed information

The engineering intelligence layer.

Everything above depends on information you can stand behind. In ATLAS, engineering inputs carry their origin, their revision and their status — and the chain from source to decision is retained.

  1. 01

    Source

    Where the value originates

  2. 02

    Evidence

    What supports it

  3. 03

    Version

    Which revision applies

  4. 04

    Decision

    What the engineer concluded

Lineage is retained so a reviewer can reconstruct how an engineering conclusion was reached.

  1. 01

    Engineering output

    Calculated, documented result

  2. 02

    Review

    Examined by a competent engineer

  3. 03

    Approval

    Accepted under company process

  4. 04

    Auditable record

    Retained, versioned, retrievable

Request a DemoSee the capability families