Connect your rig

Connecting is boring, on purpose: Ultimate QC speaks standard WITSML 1.4.1.1, so whatever already collects your rig data can feed us. Credentials are issued when your access request is approved — one set per operator, never shared.

1Three ways in — pick what you already have

Your aggregator pushes to us. If your rig data lands in Kongsberg SiteCom, Petrolink, Pason, or a rig-site EDR / office WITSML hub, add Ultimate QC as a WITSML destination: endpoint https://uqc.app/witsml, SOAP verbs WMLS_AddToStore / WMLS_UpdateInStore (append-by-MD, idempotent — re-sends are safe), HTTP Basic auth over TLS.
We pull from your WITSML server. Give us the URL, read-only credentials and the uidWell / uidWellbore to watch — our collector polls with standard WMLS_GetFromStore, which every SiteCom / Petrolink / EDR store answers. Set up with you during onboarding; nothing to install on your side.
WITS level 0. Classic serial/TCP record streams connect through our WITS→WITSML bridge — a single small program we supply that runs at the rig site (or wherever the feed is reachable), reads the &&…!! record frames (surveys from record 07, depths from record 01, vendor-specific items via a mapping file we set up with you), and delivers them to /witsml like any aggregator. It dials your feed or listens for it, reconnects on drops, and retries a failed delivery on the next frame. If you can choose, choose WITSML.

2What to send

object	uid	content
well	your uid	name; optionally field / pad / country, CRS + north reference, alarm limits as a JSON block in `commonData/comments`
wellbore	your uid	one per bore; sidetracks carry `parentWellbore` + `mdKickoff` and land in the right place automatically
trajectory	`PLAN`	the design path — enables plan-vs-actual, return-to-plan and projection
trajectory	`ACTUAL`	surveys as drilled: `md`, `incl`, `azi`, `dTimStn` + field references
log	`RAWSURVEY`	raw sensors `MD,GX,GY,GZ,BX,BY,BZ` — enables the per-station QC gates and independent angle re-computation
log	`ABI`	continuous at-bit channel `MD,ABIINC,ABIAZI` (optional)

Minimum to go live: a well and its ACTUAL trajectory. Everything else switches on the moment it arrives — no configuration call needed. A survey station looks like:

<trajectoryStation uid="s2310">
  <dTimStn>2026-08-27T14:03:20Z</dTimStn>
  <md uom="m">2310.0</md>
  <incl uom="dega">88.6</incl>
  <azi uom="dega">357.2</azi>
  <magTotalFieldReference uom="nT">61310</magTotalFieldReference>
  ...
</trajectoryStation>

3What you'll see

Your well appears on the dashboard within seconds of the first delivery, under its field and pad, and every viewer you authorise sees it live — stations land without a refresh.
Every station is verified on arrival: gravity / field / dip gates, two independent position engines cross-checking each other, screening holds shown greyed — never buried, released only with a signed reason.
Plan tracker, distance to plan, return-to-plan steering, anti-collision separation against your offset wells, and the full evidence-graded audit report one click away — built from the data exactly as received.
Anything unclear is refused, not guessed: offsets without a reference-frame assertion are excluded from anti-collision with the reason shown on the page.

4Where your data lives — and how much space it needs

Single-tenant by design. Each operator runs on their own instance — hosted by us, hybrid, or fully on-prem (Docker) — with its own database and its own encrypted backups. Your data never shares a database with another operator, and customer-facing pages make zero third-party calls.
Space is small. A survey station stores in ~0.4 KB — a full well's surveys fit in well under 1 MB. The continuous at-bit channel at one point per 5 s is the only real consumer: ~70 MB per drilling-month per well. A 50-well campaign-year, continuous channels included, stays under 50 GB.
Retention: surveys and the audit trail are the record — kept for the life of the well. Continuous channels keep full rate for the active drilling window and are downsampled after (configured per instance at onboarding).
Every read and write is audited — who saw what, when.

5Try before you connect

Watch our simulator wells drilling live — the exact product your data would land in — or request access and we'll issue sandbox WITSML credentials so your team can push test data end-to-end before a single real well is connected. A sandbox credential is scoped to its own well-uid prefix — your test pushes can't touch (or see) anything else on the instance, and we can revoke it in one click.