WorkSync DataHub · the supporting data foundation under WellOPS
Every system you run. One number everyone trusts.
Available on its own or with WellOPS and FlowSync
Integration that actually works
Your data stops living in a decade of disconnected systems.
The same well reads three different production numbers in SCADA, allocation, and accounting.
With DataHubOne reconciled number, traceable from the SCADA tag to the revenue line.
Nightly exports and brittle API projects that break the week after you build them.
With DataHubPre-built connectors that stay current automatically. No exports, no custom pipelines to maintain.
Analysis waits while someone re-keys numbers into a spreadsheet.
With DataHubEvergreen data, ready for the tools you already use: Power BI, Spotfire, Tableau.
By the numbers
Pre-built connectors. Not custom middleware.

What you can do with DataHub
Five things the backbone makes possible. Once your systems finally agree.
Regulatory Reporting
Automate state, federal, and severance filings from one source of truth.
FP&A Workflows
Close the books on one dataset that accounting, operations, and engineering all trust.
Well Economic Review · SI / RTP
Automated shut-in candidate detection and return-to-production economics, per well.
Production Allocation & Volume Reconciliation
Lineage from SCADA measurement to revenue and royalty, with the audit trail SOX needs.
Methane & Emissions Reporting
Subpart W, OGMP 2.0, methane intensity, and SEC climate disclosure on the same backbone as production.
The integration atlas
One backbone. Every system you already run.
- Enverus
- Quorum
- Enertia
- Maximo
- SAP PM
- IFS
- Oracle EAM
- AVEVA PI System
- Cygnet
- Ignition
- AVEVA System Platform / InTouch
- AVEVA
- Siemens
- AutoCAD
- Bentley OpenPlant
- SharePoint
- OpenText
- Hexagon SDx
- Intelex
- Sphera
- Enablon
- Esri
- FME
Connectors, plus the people behind them
Pre-built where we can. Hand-built where you need it.
39 pre-built connectors
Your ERP, SCADA, production accounting, and historian, and the rest. The systems every operator runs, live in days, not a custom project.
Any API. Any database.
Not in the catalog? Our engineers have spent years inside oilfield APIs and databases. If a system exposes data through REST, SOAP, ODBC, or a nightly export, we connect it and keep it current.
We make the data agree
The real work is reconciliation. One system flags oil with a run code of 3, another with 1; wells match across systems on API10. We encode those rules so every number downstream means the same thing.
Reconciliation · one rule set, every source
Raw · what your systems send
- vendor A · OilWaterRunFlag = 3
- vendor B · RUN_TYPE = "1"
- scada · PRD_OIL_RT (bbl/d)
- well keys · UWI, API10, pumper alias
One model · what everything downstream reads
- oil_bbl · normalized from every run code
- oil_rate · bbl/d, units reconciled
- well · one identity, matched on API10
- lineage · source tagged on every value
How it works
Read-first by default. Write back with permission.
- Step 01
Read from systems of record
Pre-built connectors pull from your ERP, SCADA, production accounting, and historian, 39 systems in all. Read-only by default. Your data stays your data; your stack stays your stack.
- Step 02
Unify into the semantic model
Records, time-series, documents, and geometry land in one canonical asset model. Entity resolution, unit normalization, and quality flags run continuously. Nothing duplicated. Nothing lost.
- Step 03
Serve to products. Write back with permission.
WellOPS, FlowSync, and Willie / Taylor read from the unified model. Write-back to source systems is opt-in per system and per target. Closed work orders flow back to your CMMS only when you say so.
Evaluating this for your IT or OT team? The full technical walkthrough, protocols, data movement, reconciliation, and deployment topologies, is ungated at How WorkSync connects: architecture and data flow. No form.
Rollout
SCADA, production accounting, EAM. Live on pre-built connectors.
IT issues read-only credentials. Network handshake established.
Time-series flowing. AVEVA PI System or Cygnet first; others follow same pattern.
Production accounting and CMMS work orders unified into one model.
Three integrations running. Hub feeding the products. Backbone ready for the rest of the named connector library on the same pattern.
The standard connection sequence, not a measured figure. The pace depends on how quickly your IT team issues credentials.
We pre-integrate the systems you already run.So you stop pretending the spreadsheet is integration.
WorkSync field notes · 2026
Security
OT-grade security. From day one.
OT-grade security from day one
Built for the operators who cannot use the public cloud.
Secure by design. Industrial-OT security framework. Air-gapped on-prem inference option. Read-only by default, write-back opt-in per system and per target. Your data stays your data; your stack stays your stack.
Why this is the moat
Five things competitors will not redo.
Oilfield-native connector library
Thirty-nine pre-built connectors to the systems O&G actually runs: your production accounting, SCADA, historian, and asset systems, not the generic enterprise EAM list. Years of integration work no competitor wants to redo.
OT-aware by design
Built for the operators who cannot use the public cloud. Secure by design, IEC 62443-aligned, on-prem LLM option. Read-only default. The integration layer your CISO will actually approve.
Read-first integration pattern
We pull from systems of record without changing them. Write-back is opt-in per system and per target. Your stack stays your stack. No rip-and-replace. No surprise schema changes downstream.
Available on its own or with WellOPS and FlowSync
WellOPS, FlowSync, both, or none: the DataHub is the same backbone. The commercial layer is the products that ride on it, under the Impact Guarantee: license fees only when the metrics move. Aligns our incentive with yours.
Two-year head start
Time-to-replicate is not a quarter, it is a roadmap. Anyone trying to enter has to rebuild the connector library, ship the OT framework and pass a security audit. The connectors and the OT framework are built and running in production, secure by design.
Check your stack
Will it work with what you run? Tick it and see the read path.
Tick the systems you run and get the read path for each one, as the connections are built: read-only in, and write-back only where you switch it on.
Nothing you tick leaves this page: no form, no email, no submission.
Your read paths
Tick a category and its read path appears here, with what happens on the way back.
Not on the list? If it exposes an API or a database connection, the extraction agents can connect to it.
More detail
Your systems stay. Intelligence plugs in.
Agents connect straight to your SCADA, historians, ERP, production accounting, CMMS, and engineering tools, reconciling vendor-specific data and feeding decisions back in. You keep every system that works. We add the loop that makes them work together.
- Read-only on credentials your team issues
- SSO via SAML / OIDC
- Stays clear of your control network
How the connections are secured →
- 39 Systems of Record
- 15 Industrial Protocols
- 13 Azure Services
- Read-only, on credentials you issue
What does integrating SCADA, an ERP and a historian actually mean?
In plain terms
Integration in oil and gas operations is the work of making the systems that already hold an operator’s data agree on what a well is, so one record of that well can be read across all of them. It works by mapping each system’s own identifier for the same physical asset to a single reference, reading on a schedule or on a change event through the interface each system already supports, and resolving disagreements with a stated rule about which system is authoritative for which field. Nothing is replaced: the systems of record keep their data and keep writing it the way they already do.
39 systems of record, every one named below
From wellhead sensors to executive dashboards. Extraction agents connect to each system in the list, and the list is the whole list. Counted, not rounded.
| Category | Systems of record |
|---|---|
| SCADA & Control Systems · Real-time well and pipeline monitoring | AVEVA, Emerson, Honeywell, Schneider Electric, Siemens, ABB, Yokogawa, Rockwell Automation |
| Data Historians · Time-series operational data at scale | AVEVA PI System, Proficy Historian, Aspen InfoPlus.21 (AspenTech, an Emerson business) |
| ERP & Financial Systems · Accounting, procurement, and financial close | SAP, Oracle, Microsoft Dynamics 365, Infor, Enertia, WolfePak |
| Production Accounting & Forecasting · Volume tracking, revenue, and decline curve analysis | Enverus, ComboCurve, Quorum, Halliburton (ARIES) |
| CMMS & Maintenance · Work orders, PM schedules, and asset history | IBM Maximo Application Suite, eMaint, MaintainX |
| Production Surveillance · Well performance monitoring and decline analysis | SLB (OFM), Peloton WellView Allez |
| Artificial Lift Optimization · Rod pump, ESP, gas lift, and plunger lift controllers | ChampionX, XSPOC |
| Engineering & Simulation · Pipeline and process hydraulics, process simulation, and pipe-stress analysis | Aspen HYSYS (AspenTech, an Emerson business), Honeywell UniSim Design, DNV Synergi, CAESAR II (Hexagon), pipe stress |
| GIS & Mapping · Asset locations, pipeline routes, and spatial analysis | Esri ArcGIS |
| Fleet & Telematics · Vehicle tracking, crew locations, and drive time optimization | Samsara, Geotab |
| Cloud & Data Platforms · Lakehouses, warehouses, and streaming infrastructure | Snowflake, Databricks, AWS, Apache Kafka |
Deep integration with the Microsoft data stack
From wellhead sensor to executive dashboard: one data path through Microsoft Fabric
- Microsoft Fabric · Unified analytics platform
- IoT Hub · Device telemetry ingestion at scale
- Event Hubs · High-throughput streaming pipeline
- ADLS Gen2 · Scalable data lake storage
- Synapse Analytics · Enterprise analytics warehouse
- Data Factory · ETL orchestration and scheduling
- Data Explorer · Real-time time-series analytics
- Digital Twins · Live asset topology models
- Stream Analytics · Real-time event processing
- Power BI · Interactive dashboards and reports
- Power Automate · Workflow automation and triggers
- Dataverse · Low-code data platform
- Dynamics 365 · ERP, CRM, and field service
Native support for 15 industrial protocols
Speaking the protocol natively means faster deployments and fewer middleware headaches.
Real-Time & Field Data
- OPC-UA
- MQTT
- REST API
- Modbus TCP/RTU
- DNP3
- Kafka
- AMQP
- IEC 61850
Enterprise & Industry Standards
- ODBC/JDBC
- OData
- WITSML
- PRODML
- OSDU
- PPDM
- gRPC
How the agents connect your systems
WorkSync does not use fragile ETL pipelines or CSV imports. Specialized agents handle every step from extraction to decision, running continuously.
Extraction Agents
Connect directly to your data lakehouse and pull every table your operation touches. SCADA, production, tanks, work orders, completions. Native to Fabric, Databricks, and Snowflake.
Refinement Agents
Handle vendor-specific data quirks. Different schemas, conventions, and API formats from Enverus, WolfePak, Quorum, AVEVA PI System, and every other system named above get normalized into one operational data model.
Decision Agents
Evaluate every asset against configurable rules, generate flags, score by economic impact, and package route-optimized work orders. The plan is ready before 6 AM.
How the data actually moves: the ungated architecture walkthrough →
The screen your control room already has.
What the agents read
An example compressor station screen: the process values, the measurement panel the day’s volumes are settled on, the trends and the active alarms. The extraction agents read the tags under a screen like this one, through the protocols above, and nobody re-keys any of it.
Example screen, WorkSync render
Don’t see your system?
Our extraction agents can connect to any system that exposes an API or database. We will map your technology stack and build a custom integration plan in days, not months.
How WorkSync connects: architecture and data flow.
For data engineers and OT/IT leads · no form, no gate
The short version: WorkSync reads from the systems of record you already run, over OPC-UA, MQTT, REST, OData, and ODBC, reconciles what it reads into one golden record per well, and serves that record to the products. Write-back is opt-in per system and never goes to a control system. The platform runs single-tenant, in your VPC, or on-prem. Nothing gets replaced.
You should not have to sit through a sales call to find out how a vendor touches your SCADA. This page is the technical walkthrough we give evaluation teams: what we read and over which protocols, how data moves and reconciles, what write-back actually means, and where the platform can run. Everything here is self-serve. The NDA-gated depth (pen-test summary, threat model) is one request away on /security.
- read-first by default
- write-back opt-in per system
- single-tenant · VPC · on-prem
- no rip-and-replace
Read-first. Everything else follows from that.
01 · The integration model
WorkSync pulls from your systems of record without changing them. Four kinds of data come in: records (wells, work orders, tickets), time-series (tags, rates, pressures), documents (P&IDs, datasheets, as-builts), and geometry (GIS layers, routes). The pattern below is enforced on every connector, not negotiated per project.
Polling, streaming, and an honest word about freshness.
02 · How data moves
Different sources move differently, and pretending otherwise is how integration projects earn their reputation. Here is the actual posture per source class.
| Source class | How it connects | Posture |
|---|---|---|
| SCADA & historians | OPC-UA or MQTT subscription, or the historian’s native API (AVEVA PI System, Cygnet, Ignition) | Streaming or short-interval polling. Time-series lands near-real-time, at the cadence your historian already publishes. We do not resample your tags into something faster than the source. |
| Production accounting, ERP, EAM | ODBC/JDBC, OData, or vendor REST APIs (Enverus, Quorum, Maximo, SAP) | Scheduled pulls, typically several times a day, set with your IT team. Transactional systems change on transactional cadence; polling them harder does not make the data fresher. |
| Documents, GIS, engineering files | REST APIs and file connectors (SharePoint, Esri, FME, CAD/P&ID parsers) | Event-driven where the source supports webhooks, scheduled sweeps where it does not. Parsed content is versioned so a re-issued drawing never silently overwrites lineage. |
The freshness rule
We will not quote you a blanket latency number on a marketing page, because the honest answer is: freshness is a property of the source. Time-series arrives near-real-time from your historian’s cadence. Transactional data arrives on the schedule your systems actually change on. During integration we agree the cadence per source with your IT team, and the platform surfaces data age on every value, so a stale number looks stale instead of confident.
One well, three systems, one record: the API10/UWI walk.
03 · Reconciliation
The hard part of integration was never the pipe. It is making a decade of vendor data agree. One production system flags oil with a run code of 3, another with 1, and the same well answers to a UWI, an API10, and whatever the pumper has always called it. We encode those rules once, so every number downstream means the same thing.
Entity resolution
UWI, API10, and field aliases resolve to one well identity. Facilities, meters, and routes get the same treatment. Ambiguous matches are queued for a human, not guessed.
Normalization & quality flags
Units, run codes, and timestamps normalize continuously. Values that fail range or consistency checks carry a quality flag downstream instead of being silently dropped or silently trusted.
Lineage on every value
Every number in the unified model is tagged with its source system and retrieval time. When accounting asks why a volume changed, the answer is a click, not an investigation.
Opt-in, per system, per target. Never to control systems.
04 · Write-back
What write-back is
Business-system updates you explicitly turn on: closed work orders flowing back to Maximo, completed field tickets posting to the system of record. Each write target is enabled individually, scoped to specific record types, approved by a human where you want one in the loop, and logged in a full audit trail.
What write-back is not
It is never OT. WorkSync does not write setpoints, does not touch PLC logic, and has no pushbutton-equivalent path to field equipment. SCADA integration is unidirectional by architecture. If nobody enables a write target, the platform stays read-only forever, and that is a fully supported way to run it.
Three topologies. Your security team picks.
05 · Where it runs
Single-tenant cloud
Dedicated tenant on AWS or Azure in a region you choose (US-East, US-West, EU). Customer-managed KMS keys (BYOK/HYOK) for data at rest, TLS 1.3 in transit. No shared infrastructure with other customers.
Fit: most operators. Fastest stand-up.
Your VPC
The agent and inference layer deploys into your own cloud tenant, including LLM inference on open-source models you host. Your data and your model calls never leave your environment.
Fit: teams with an established cloud footprint and strict egress rules.
On-prem edge
An on-prem edge connector runs the integration and agent layer entirely inside your network, with egress limited to the web UI and customer-initiated sync. Zone-and-conduit segmentation between IT and OT, allowlisted endpoints, IEC 62443-3-3-aligned controls.
Fit: air-gap requirements. The default pattern for the strictest OT environments.
Security posture across all three: secure by design. IEC 62443-3-3-aligned OT controls, annual third-party penetration testing, SSO via SAML/OIDC, RBAC, and audit logs on every access. The full control list lives on /security.
What WorkSync does not do.
06 · The negative space
Half of a technical evaluation is ruling things out. Save yourself the discovery calls.
No rip-and-replace
Your SCADA, ERP, CMMS, accounting, and GIS stay exactly where they are. WorkSync reads from them; it does not migrate, replatform, or sunset them.
No data-lake prerequisite
You do not need a lakehouse, a UNS, or a finished master-data project first. The connectors and the reconciliation layer are the product. If you already run Fabric, Databricks, or Snowflake, we connect to it; if you do not, nothing is blocked.
No control-system writes
WorkSync cannot write setpoints, modify PLC logic, or issue pushbutton-equivalent commands. The OT boundary is enforced in the integration layer, not by policy.
No cross-tenant model training
Single-tenant architecture. Your operational data never trains a model another customer sees. Default LLM inference is open-source models in a dedicated US-region pool or your own tenant, with no third-party API calls unless you explicitly enable them.
Walk our architecture with your data lead.
Go deeper
Bring your data engineer or OT lead and we will walk this page against your actual stack: your historian, your accounting system, your network boundaries. A working session, not a pitch. And if you would rather keep reading first, everything below is ungated too.
Data Lake vs Data Hub vs Unified Namespace.
The three operating-data architectures oil and gas operators evaluate in 2026, compared side by side on build time, integration cost, query economics, governance burden, AI readiness, and which operator profile each one actually fits.
The short version: the data lake is a 2017 idea built for supermajor scale; the unified namespace is the right OT backbone for control-grade event throughput; the WorkSync DataHub is the read-only integration layer that turns the systems an independent already owns into ranked field decisions inside thirty days. The three are not in conflict for most operators; the question is which one is the right starting point.
What is a unified namespace in oil and gas?
In plain terms
A unified namespace in oil and gas is a single live hierarchical address space in which every piece of operational data has one name and one current value, usually published over a message broker so any system can subscribe to it. It works by having each source publish its data once into the shared hierarchy, after which consumers read from the namespace rather than from each source directly. It differs from a data lake, which stores history in bulk for analysis later, and from a data hub, which reconciles identities between systems and serves a governed record to applications.
Side-by-side: 18 dimensions that actually matter.
The dimensions below are the ones that surface in operator AI-readiness reviews: build time, capex, query economics, governance burden, real-time fitness, AI-agent compatibility, and lock-in posture. Everything else (visualization tooling, dashboard layer, BI integration) sits above this layer and is interchangeable across all three.
| Dimension | Data Lake | Unified Namespace (UNS) | WorkSync DataHub |
|---|---|---|---|
| Core pattern | Copy data into a parallel storage tier; analytics run on the copy | Hierarchical, real-time message bus on top of MQTT or Kafka; data stays in source systems | Read-only integration layer; data stays in the operator existing systems of record |
| Where the data lives | Object storage (S3, ADLS, GCS) plus a curated semantic layer above it | In-flight; the broker is the integration plane, not a storage tier | Production accounting, SCADA, EAM, GIS, HSE, engineering drawings, lease accounting (left in place) |
| Integration model | ETL / ELT pipelines from each source system into the lake | Edge brokers and gateways publish source-system data into a topic hierarchy | Pre-built connectors to P2, Quorum, Enverus, Inertia, Maximo, SAP PM, IFS, AVEVA PI System, Cygnet, Ignition, AVEVA, Esri, SharePoint, OpenText, Intelex, Sphera |
| Build time (typical mid-tier operator) | 18 to 36 months for an integrated lake plus governance program | 3 to 9 months for a real-time backbone across SCADA / historian / control | Under one week to first three integrations; full stack typically inside 90 days |
| Up-front capex / professional services | Seven to eight figures including platform, professional services, and headcount | Mid six to low seven figures for brokers, edge gateways, and integration work | Included with any WellOPS or FlowSync module; scoped with our implementation team |
| Ongoing storage cost | Recurring storage on every duplicate of the source data, indexed and re-indexed | Low storage cost; the broker is transit, not durable storage | None; no parallel storage tier |
| Query / inference economics | Cheap per-query at scale; only after the lake is fully loaded and curated | Cheap and fast for live values; weak for historical analytics without a separate store | Cheap per query because the underlying inference cost dropped ~280x (Stanford 2025 AI Index) |
| Governance burden | Heavy. Catalog, lineage, quality, access, and master data programs are standard scope | Moderate. Topic-naming governance is the main discipline; less catalog overhead than the lake | Light. The operator existing systems remain authoritative; no parallel governance program |
| Master data project required | Yes. The lake economics depend on a coherent canonical model across sources | Lighter than the lake. The hierarchy is the contract; not a full master data project | No. The systems of record stay authoritative; canonical model is built by the connectors |
| Real-time fitness | Batch by default. Streaming bolt-ons are common but add complexity | Excellent for OT. Sub-second event delivery is the design point | Sufficient for ranked field decisions. Streams batched on the cadence the decision actually needs |
| Engineering / SCADA event throughput | Good for analytics but poor for OT-grade event rates without separate streaming infra | Excellent. Built for OT-grade telemetry from SCADA / historian / control | Good. SCADA tag streams are first-class; not OT control-grade event speed (UNS still wins there) |
| AI / ML readiness out of the box | High once curated, but the gating step is the multi-year curation | Good for streaming inference; weaker for AI agents that need cross-system context | High. WellOPS and FlowSync ride on top by default; ranked plans inside 30 days |
| Vertical AI agent compatibility | Indirect. Requires extracting data back out of the lake to feed a vertical agent | Partial. Vertical agents can subscribe but most still need a queryable historical layer beside the bus | Direct. Willie (field agent) and Taylor (engineer agent) are built on the DataHub |
| Vendor lock-in posture | Medium to high. Hyperscaler-coupled architecture, exit cost is non-trivial | Low to medium. MQTT and Kafka are open; broker vendors are interchangeable | Low. Read-only by default; data stays your data; stack stays your stack |
| Sweet-spot operator profile | Supermajors and large IOCs with multi-year horizons and existing data orgs | IIoT-forward operators with strong control-system culture (refining, large midstream, advanced upstream) | Independents at 200 to 2,000 wells and gas utilities at the planning-team level |
| Failure mode | Lake-fills-up-while-decisions-do-not-change. Becomes a memorial to a planning exercise | Topic taxonomy churn and weak historical analytics without bolt-on storage | Underbuilt field workflow that does not consume the ranked decisions the Hub produces |
| Maturity in upstream / midstream | Mature at supermajor scale (2017 to 2022 build wave). Limited adoption at mid-tier | Growing fast in process industries and refining; emerging in oil and gas | |
| Time to first ranked field decision | 18 to 36 months from project start; longer if the curation layer is also being built | 3 to 9 months for the live-data backbone; field-decision layer is a separate build | Under 30 days from first integration to ranked daily plan in the truck cab |
When each one is the right call.
No architecture is universally correct. The right answer depends on operator scale, OT maturity, and how fast the field needs ranked decisions.
The Data Lake is the right call when
- You operate at supermajor or large IOC scale and run analytics workloads that need pooled cross-asset data.
- You already have a multi-year platform horizon, a data-engineering organization, and a curation budget that can absorb the up-front cost.
- Your dominant query pattern is large historical aggregates that justify a parallel curated tier.
For a 200 to 2,000-well independent in 2026 these conditions usually do not hold. The lake-first sequence is a five-year detour without the operator scale to amortize it.
The Unified Namespace is the right call when
- You run OT-grade event throughput that needs sub-second delivery across the control layer (advanced refining, large midstream control rooms, integrated facility automation).
- Your priority is the live operating picture across SCADA, historian, and control, not historical cross-system analytics.
- You have the control-system maturity to govern a topic hierarchy.
Operators who already run a UNS should keep it. The DataHub reads from the UNS the same way it reads from SCADA or a historian.
The WorkSync DataHub is the right call when
- You operate as an independent at 200 to 2,000 wells or as a gas utility planning team that needs ranked field decisions inside 30 days, not inside three fiscal years.
- You want to leave your existing systems of record authoritative (P2, Quorum, Enverus, Maximo, SAP PM, IFS, AVEVA PI System, Cygnet, AVEVA, Esri, SharePoint, Intelex) and add an integration layer on top.
- You want vertical AI agents (Willie for the field operator workflow, Taylor for the engineering workflow) built into the architecture, not bolted onto a separate data layer later.
The 4-week Impact Guarantee pilot is in writing: license fees only when the metrics move.
The three architectures are not in conflict.
The most common operator situation in 2026 is not a one-of-three choice. It is a sequencing question. An independent that already runs a strong SCADA stack and a production accounting system can stand up the DataHub in under a week and have ranked field decisions in thirty days. The same operator can add a unified namespace later for OT-grade event throughput on a specific facility or pad without disturbing the DataHub above it. The data lake, if it is justified at all by the operator scale, comes last; the lake reads from the same systems the DataHub already connects to, and the lake’s analytics workload sits beside the DataHub’s ranked-decision workload rather than replacing it.
The supermajor sequence (lake first, decisions later) is a function of the supermajor’s analytics-org budget and multi-year horizon. The independent sequence is the inverse: ranked decisions first, lake later only if the math justifies it. The DataHub is built for that inverse sequence.
For operators evaluating any of these patterns right now, the practical recommendation is to start with the integration layer that produces decisions inside the current fiscal year. That is the DataHub. Add the UNS where OT-grade event throughput requires it. Add the lake only if the operator scale and analytics budget make the math work.
The lake-first sequence is what the supermajors paid for between 2017 and 2022. An operator does not need to pay tuition on someone else’s experiment. What the field needs is ranked decisions in the truck cab by 6 AM, not a five-year platform program.
Why WorkSync runs hub-first · the position behind the architecture
Skip the five-year detour.
The DataHub reads your existing stack in under a week. Ranked field decisions inside thirty days. Plan your pilot with our implementation team. The 4-week Impact Guarantee is in writing: license fees only when the metrics move.
For the full argument behind why an independent should not start with a lake in 2026, read The Data Lake Is a 2017 Idea.
Where the DataHub gets used
The backbone for ranked work, modeling, and M&A integration.
What plugs into the DataHub
Modules that ride on it
- WellOPSField operations: Work Engine, Route Optimizer, FDC, FWM
- FlowSyncEngineering: Model Builder, Flow Sim, Process Sim
- Work EngineRanked plan in the truck cab by 6 AM
- Route Optimizer35% fewer miles driven, value-density routing
- M&A integration playbookUnify acquired SCADA + accounting in days
- SCADA-driven work executionHow the DataHub closes the SCADA → CMMS gap
LOE reduction playbooks
Pre-built integrations + comparisons
Compare to your stack
- Full integration catalogYour ERP, SCADA, production accounting, and historian
- Data Lake vs Data Hub vs UNSArchitecture comparison: build time, query economics, AI readiness
- How WorkSync comparesvs legacy CMMS, SCADA dashboards, generic FSM, and spreadsheets
- 3-basin case studyHow the DataHub unified 3 SCADA stacks on one backbone
- The Data Lake Is a 2017 IdeaWhy independents run AI without one
- Your Asset Hierarchy Lives in 14 SystemsThe pre-deployment data burn, solved
Frequently asked
What integration teams ask about the DataHub.
What does it actually integrate to?
Why is it included?
Read-only or read/write?
How long until the integrations are live?
What does integrating SCADA, an ERP and a historian actually involve?
How long does a typical integration take?
Do we need to replace our existing systems?
What if our system is not listed here?
How does WorkSync handle data from multiple vendors?
What is a unified namespace in oil and gas?
What is the practical difference between a data lake, a unified namespace, and a data hub?
Does an independent operator need a data lake before running AI?
Is the DataHub the same thing as a unified namespace?
When does a data lake still make sense?
When does a UNS still make sense even if you have a DataHub?
How long does the DataHub take to deploy?
How is the DataHub priced?
What about the OT-IT boundary and cybersecurity exposure?
Where to begin
Start with the backbone. Add the modules when you’re ready.
The DataHub is available on its own or with WellOPS and FlowSync, so operators who want a clean operations data layer first can start there. Same backbone, same connectors, no rework when you add a product.
Available on its own or with WellOPS and FlowSync · reply within 1 business day
Or see the full integration catalog