Skip to content
ATLAS
Capabilities

Six engineering capability families.

Capability families describe how engineering work is organised inside ATLAS. They are engineering domains, not a feature list — depth, configuration and rollout are established with your organisation during an engagement.

01 — Well Planning & Design
Trajectory, casing and wellbore architecture.
02 — Drilling Engineering & Analysis
Loads, torque and drag, drillstring behaviour.
03 — Hydraulics, Mechanics & Optimization
Circulating behaviour and scenario comparison.
04 — Engineering Data & Repository
Governed components, catalogues and project inputs.
05 — Operational Intelligence
Operational and historical context for engineering.
06 — Reporting, Assurance & Traceability
Structured, reviewable engineering records.
01 — Well planning & design

Structured well design, with intent retained.

Well architecture is developed as project structure: trajectory, casing programme, intervals and targets held together with the objectives and constraints they were designed against.
  • Trajectory and wellbore architecture workflows.
  • Casing and interval design as structured project data.
  • Design objectives, constraints and assumptions recorded with the well.
  • Project context retained across the design lifecycle.
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.
02 — Drilling engineering & analysis

Analysis anchored to the design it belongs to.

Mechanical behaviour is examined against the planned well rather than against a detached copy of it, so the analysis and the design cannot quietly diverge.
  • Torque and drag studies across the planned profile.
  • Axial, torsional and mechanical loading considerations.
  • Drillstring and BHA configuration in project context.
  • Inputs traceable back to their source and revision.
DRILL PIPEHWDPBHABITLOAD →DEPTHTORQUEDRAG
Drillstring / BHA · axial load · torque profileDrillstring and bottom-hole assembly schematic beside a qualitative axial load and torque profile against depth.
03 — Hydraulics, mechanics & optimization

Engineering alternatives, compared honestly.

Hydraulics and hole cleaning are treated as engineering constraints on the operating window. Optimisation studies exist so options can be compared under the same stated assumptions.
  • Circulating behaviour across the interval.
  • Hole cleaning considerations tied to the design.
  • Mechanical optimisation studies for comparison, not prescription.
  • Assumption sets stated with each scenario.
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.
04 — Engineering data & repository

Governed engineering information, not shared folders.

Components, catalogues and project inputs are held in a controlled repository where each item carries its origin, revision and status — with company-approved standards and authorised vendor data taking precedence.
  • Component and catalogue information under version control.
  • Sources attached to values, not remembered separately.
  • Project-specific engineering input remains possible and auditable.
  • Repository content supports engineering decisions while company-approved standards, authorised vendor information and engineering judgement retain precedence.
  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.

05 — Operational intelligence

What is happening, read against what was planned.

Operational context and historical information are surfaced alongside engineering work so planning and review are informed by the same basis. Interpretation stays with the team.
  • Operational context presented next to the design basis.
  • Historical wells available as engineering reference.
  • Learning from previous operations retained rather than retold.
  • No autonomous operational 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.
06 — Reporting, assurance & traceability

Engineering records that survive review.

Engineering outputs, assumptions, reviews and approvals are captured as structured records — so a result can be explained months later, by someone who was not there when it was produced.
  • Structured engineering outputs rather than ad-hoc documents.
  • Assumptions recorded as part of the engineering case.
  • Reviews and approvals captured as reviewable records.
  • Auditability of activity on engineering information.
  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

Engagement

Configured around your engineering requirements.

ATLAS capabilities are configured around the engineering workflows, governance requirements and operating environment of each organisation. Scope, configuration and deployment requirements are established during engagement.

Request a DemoHow assurance works