Questions operators raise first.
Direct answers on validation, integration, security and commercial terms.
How is this different from threshold alarms?
Single-channel alarms fire when a parameter crosses a fixed limit. Vogter classifies the developing multi-channel pattern earlier, identifies the mechanism, and attaches the supporting evidence, so the call is defensible in technical review rather than adding alarm noise.
What does integration require on the rig?
Nothing on the rig. We're cloud-based, and we connect to your existing rig-data hub with a one-way pull (WITSML server, Pason DAS, NOV TOTCO, WellData, or your historian) over the network at roughly 50 kbps outbound per well, VSAT-friendly. No edge device, no new sensors, no crew change.
How is our data secured?
TLS 1.3 in transit, AES-256 at rest, per-well/per-role RBAC, tamper-evident hash-chained logs, and customer-selectable data residency (UK-South by default, or US-East / EU-West).
Is the model a black box?
No. It's physics-informed AI: physics constraints anchor what the model can conclude, and every call carries a structured “why this call” trace: the contributing channels and the reasoning behind it.
What if the evaluation doesn't hit its targets?
Success metrics are agreed during the data review, with no conversion obligation if targets are missed.
What are the commercial terms?
We share commercial terms during the evaluation, once your wells and objectives are scoped.
Still have a question?
Evaluation enquiries, commercial discussions and technical diligence all begin at the same address.