Decades of well logs you cannot search, cannot summarise, cannot share.
Subsurface decisions on new wells, reservoir analysis, and field-redevelopment economics depend on the well-log history of the basin. That history exists — it lives on tape, in proprietary archives, in retired vendor formats, in DLIS files only the original software can render. The bytes are preserved; the institutional knowledge is not accessible.
Talk to a Subsurface solutions engineer · Read the energy microsite · Read the DocuTalk capability brief
"I have decades of well logs in formats only the original software can read."
"I have decades of well logs in formats only the original software can read. I cannot search them, I cannot summarise them, I cannot share them with new geoscientists." — VP Subsurface / Geoscience
The technical reality: well-log formats — DLIS (Digital Log Interchange Standard), LAS (Log ASCII Standard), legacy SEG-Y, vendor proprietary — were designed for the rendering software of their era. Modern subsurface platforms (SLB Techlog, Halliburton DecisionSpace, Emerson Paradigm) read the formats but do not surface them in a search-and-share workflow. AI search (DocuTalk, Glean) cannot index DLIS without a parsing pipeline.
What TeamSync gives the VP Subsurface.
1. Native well-log viewers (DLIS, LAS, SEG-Y).
TeamSync's specialised viewers render petroleum well logs natively in the browser. Geoscientists annotate inline; annotations are stored as metadata against the log; the audit ledger anchors annotation events.
2. Metadata extraction from log headers.
The Metadata Extraction pipeline reads DLIS / LAS headers and indexes the structured fields (well name, basin, formation, log date, log type, vendor) — making the corpus queryable by metadata facets.
3. Semantic search across the log narrative.
Semantic Search indexes the log narrative (formation evaluations, completion reports, end-of-well reports). Queries like "show me every Bakken horizontal well drilled before 2015 with mud-log shows above C5" return ranked results.
4. DocuTalk grounds the institutional-knowledge conversation.
The retired senior geoscientist's tribal knowledge is in the reports they wrote. DocuTalk surfaces it: "what did Smith say about the Bone Spring formation in his 2008 reservoir review?" — answer with citation. New geoscientists ramp on the basin's history in days, not years.
5. The audit ledger preserves provenance.
Original log file (the bytes from the wireline-logging vendor in 1985), every annotation since, every interpretation, every reservoir-model input — all anchored in the Merkle audit ledger. Forensic re-analysis of a producing field's reserve estimate is a query, not a project.
How TeamSync compares for subsurface knowledge access.
| Capability | TeamSync | SLB Techlog | Halliburton Landmark | Emerson Paradigm | Glean overlay |
|---|---|---|---|---|---|
| Native well-log viewers (DLIS, LAS, SEG-Y) | ✅ | ✅ Subsurface-native | ✅ Subsurface-native | ✅ Subsurface-native | – |
| Metadata-extracted log headers | ✅ | Within Techlog | Within Landmark | Within Paradigm | Index only |
| Semantic search across reports | ✅ | Limited (Techlog AI) | Limited | Limited | ✅ Federated |
| AI grounded in DocuTalk with citation | ✅ | Techlog AI | Landmark AI | – | ✅ |
| Audit-anchored provenance for log files | ✅ Merkle | – | – | – | – |
| Per-cluster transparent pricing | ✅ | Per-product | Per-product | Per-product | Per-seat |
Important: TeamSync coexists with SLB Techlog / Halliburton Landmark / Emerson Paradigm — they own subsurface interpretation. TeamSync owns the document-of-record + AI-grounding layer alongside, with cryptographic provenance.
CTAs.
| If you are… | Do this |
|---|---|
| VP Subsurface / Geoscience | Talk to a solutions engineer |
| Reservoir Engineer building basin models | Read the DocuTalk capability brief |
| Knowledge Manager preserving retiring senior staff knowledge | Read the knowledge-worker-productivity use case |
Frequently asked questions.
Does this replace SLB Techlog?
No. Coexistence. Techlog handles subsurface interpretation; TeamSync handles the document-of-record + searchable archive + AI-grounded knowledge surface alongside.
What about legacy tape and microfiche?
The metadata-extraction pipeline supports OCR on scanned legacy logs. Tape-stored DLIS can be ingested via the standard ingest API after a one-time digitisation project.
Can TeamSync compute new attributes from log data?
No — that is what subsurface platforms (Techlog, DecisionSpace, Paradigm) are for. TeamSync is the document-and-knowledge layer, not the interpretation engine.