SCADA and telemetry
Production signals, tank levels, meter readings, alarms, and field-device data from operating assets.
CygNetIgnitionIronIQOther SCADA sources
OTS Platform
One platform for connected oilfield operations.
Start with the app you need today. Connect more workflows as the operation grows.
Oilfield Tracking Services builds software for oilfield water hauling, oil hauling, dispatch coordination, field requests, compliance records, integrations, and operational reporting. The OTS platform lets each module solve a specific job while giving teams a path toward one operating record across water, oil, optional dispatch, field work, rates, invoices, compliance, and reporting. WaterGo and OilGo can operate without dispatched jobs, while DispatchGo is available when teams want a dedicated planning and coordination layer.
Composable ratesInvoice-readyOffline-firstCustomer supportShared records
How the platform works
Start with one application. Connect more when the operation is ready.
Each OTS application can stand on its own for a focused workflow. The platform becomes more valuable as teams connect modules, because shared records reduce duplicate entry and give field, dispatch, compliance, and office users the same operating picture, even when mobile work starts in low-connectivity field conditions. DispatchGo can add planning and coordination, but WaterGo and OilGo do not require dispatched jobs to capture tickets, track work, or support invoicing.
Independent module
One workflow, fast rollout.
Select an application to see how a single module can deliver value on its own before additional workflows are connected.
Water hauling, disposal tickets, and freight records.
Create or import water work
Capture tickets offline first
Sync reports back to office
Focused workflow, independent value.
Connected platform
Multiple modules, one operating record.
Add more applications as operations grow. Shared platform services keep users, jobs, tickets, sites, approvals, optional dispatch context, offline sync patterns, support requests, and reporting aligned across teams.
WaterGo
Water hauling, disposal tickets, and freight records.
OilGo
Oil hauling orders, tickets, and delivery visibility.
DispatchGo
Dispatch boards, routes, vendors, and load status.
FieldGo
Mobile requests, task updates, and field activity.
Users and roles
Sites and assets
Tickets and loads
Offline capture and sync
Reports and exports
Customer support
Shared foundation
The platform keeps the common pieces together.
The more workflows a team connects, the more important the shared foundation becomes. Instead of rebuilding users, locations, reports, and ticket context in every tool, the platform gives OTS modules a common structure to work from. That foundation also supports composable rate structures, invoice creation, offline-first field capture patterns, and a customer support relationship that can evolve with the operation.
User roles and permissions
Sites, vendors, routes, and assets
Load, ticket, and field activity records
Composable rates and invoice creation
Compliance documentation and review exports
Operational reporting for office and leadership teams
Integration paths for accounting and business systems
Offline-first mobile capture and sync patterns
Customer support and implementation guidance
Industry integrations
Connect the platform to the systems oilfield teams already use.
OTS supports both incoming operational data and outgoing business records, so field activity can move from source systems into dispatch, tickets, reconciliation, reporting, compliance, and invoicing without another layer of manual entry.
Incoming
Orders, telemetry, locations, files
Outgoing
Tickets, invoices, reports, exports
Incoming data
Dispatch and load requests
Orders, work requests, route context, pickup details, destinations, and vendor assignments.
EDI, API, and webhooks
Common logistics exchanges, REST endpoints, event callbacks, JSON payloads, cloud APIs, and partner system events.
REST APIsWebhooksS3AzureDatabricks
File, cloud, and SFTP drops
Structured imports for legacy systems, customer files, accounting exports, cloud storage, lakehouse workflows, and scheduled data handoffs.
CSVExcelSFTPAmazon S3Azure StorageDatabricks
GIS and location systems
Lease, facility, yard, well, disposal, route, and geofence context for field and dispatch workflows.
ArcGISFacility listsRoute data
Wastewater disposals
Disposal facility tickets, receipts, manifests, disposal status, and handoff files for water hauling and compliance workflows.
Disposal ticketsReceiptsManifestsFacility files
Identity and permissions
SSO-ready patterns for customer identity providers, role controls, and operational access boundaries.
Outgoing data
Accounting and ERP
Invoice-ready records, customer charges, vendor payables, billing codes, taxes, and GL-friendly exports.
OpenInvoiceOpenTicketSupplierLinkAribaSAPEnertiaQuickBooks
Invoice and ticket packages
Tickets, manifests, disposal records, signatures, attachments, and invoice support documents.
Compliance exports
Review-ready PDF, CSV, and structured data sets for waste, mileage, manifest, disposal, and wastewater facility workflows.
Business intelligence
Operational reporting feeds for dashboards, cost analysis, utilization, route performance, lakehouse workflows, and leadership review.
Power BIDatabricksS3AzureData warehouses
Customer and vendor portals
Shared status, proof-of-work records, load history, and reconciliation details for external stakeholders.
Two-way system sync
Bidirectional updates where status, corrections, approvals, and source-system identifiers need to stay aligned.
ProdViewProCountPeloton WellViewPeloton SiteView
Integration target families
SCADA
CygNet, Ignition, IronIQ, and more
Production Accounting
ProdView, ProCount, and more
Accounting
OpenInvoice, OpenTicket, SupplierLink, Ariba, SAP, Enertia, QuickBooks, and more
Operations
Peloton Product Suite, wastewater disposal facilities, WellView, SiteView, and related operational systems
Cloud and Data Platforms
Amazon S3, Azure storage and APIs, Databricks, cloud file drops, and lakehouse handoffs
Independent applications
Use WaterGo, OilGo, DispatchGo, or FieldGo on its own when a team needs one focused workflow solved first. Dispatch is optional, not a dependency for WaterGo or OilGo.
Shared operating record
Connect modules through the platform so loads, tickets, sites, mileage, approvals, and reports stay aligned.
Rates and invoicing
Use robust, composable rate structures to support invoice-ready records across customers, vendors, routes, jobs, tickets, and operating rules.
Offline-first field support
Mobile workflows are designed for field conditions, helping users capture work when connectivity is limited and sync when service is available.
Customer support
OTS pairs the platform with customer support, rollout help, and product feedback loops from a team close to the software.