Design the rig to keep essential acquisition, alarms, control functions and approved local decisions running when the WAN or satellite link fails. Store records locally with a tested secondary copy, preserve each source timestamp, mark outage intervals, and reconcile local and central records after service returns. A dashboard that reconnects is not proof that the record is complete.
What a connectivity loss actually changes
A remote drilling operation has at least two distinct systems: the processes physically running at the rig and the services that move, store or visualize data elsewhere. Losing the network may stop a remote dashboard without stopping local acquisition. It may also interrupt alarms, remote supervisory decisions, reporting feeds or synchronization services while drilling continues under the site’s approved procedures.
As an Amazon Associate I earn from qualifying purchases.
“No new data received” is therefore not the same as “no operation” or “no event.” Every outage record should identify the start time, affected systems, affected data streams and operating mode. The site must also identify which decisions require live remote oversight and who has authority when that oversight is unavailable. No generic rule permits every drilling activity to continue offline; safety-critical authority remains defined by the approved well and emergency procedures.
Build an offline-first data path before mobilization
Inventory what must remain available locally
- Acquisition channels, historian functions and downhole or surface measurements.
- Alarm annunciation and interlocks that are required for safe operation.
- Approved local control functions and displays.
- Inputs needed for daily reports, tour sheets, mud reports and regulatory records.
- Critical communications, including the fallback method used when the primary link fails.
- Local logs showing operator actions, mode changes, alarms and manual entries.
For each item, write down whether it must continue during a WAN outage, may operate in a degraded mode, or must stop pending authorization. Assign a local owner and an escalation route. This converts “the remote center is unavailable” from an improvised decision into a runbook.
#1 Best Overall
- NEARLY 2X FASTER THAN OUR PREVIOUS GENERATION(8) – move 1,000 high-res photos in under 60 seconds(6) with up to 2000MB/s transfer speeds(2).
- IP65 RATING AND UP TO 3M DROP PROTECTION(3) – protects against spills and drops.
- POCKET-SIZED – fits easily in pockets and small bags.
- SPACE TO OWN YOUR AI CONTENT – speed and capacity to download your high-res clips and photo edits.
- 256-BIT AES ENCRYPTION(4) – helps keep private files secure with password protection.
Map every stream to an owner and a destination
Build a register that includes operator, drilling contractor and service-company systems rather than only the operator’s central platform. For each stream, record:
| Register field | What to capture |
|---|---|
| Source | Instrument, controller, application or manual log that creates the record. |
| Owner | Party responsible for data quality, access and retention. |
| Format and interface | Protocol, schema, file type or message interface used for transfer. |
| Timestamp origin | The clock that assigns the event time; distinguish source time from receipt time. |
| Local retention | Where the primary copy and secondary copy reside, and how long they are retained. |
| Synchronization | Time source, fallback source and monitoring method. |
| Destination | Remote operations center, enterprise historian, service-company system or regulator submission. |
| Recovery owner | Person or team responsible for checking gaps and approving reconciliation. |
Wellsite data commonly crosses several vendors and formats. The Wellsite Information Transfer Specification (WITS) describes the basic wellsite-to-central transfer problem, while a Bureau of Safety and Environmental Enforcement assessment discusses governance and standards such as WITSML and PRODML. Verify the current revision and contractual obligations for the systems actually installed; the WITS site is legacy material and should not be treated as current standards stewardship.
Retain locally with redundancy
Use local storage as the authoritative buffer during an outage and provide a second copy appropriate to the system. A March 17, 2026 field article from Premier Drilling Equipment recommends redundant local storage for unreliable connectivity, but that recommendation is not an independently validated hardware standard. Select equipment only after checking temperature and shock ratings, ingress protection, encryption, access control, retention capacity and compatibility with the acquisition software.
Free tools Windows power users keep installed
One-click scans. No signup required.
Define what happens when the primary local store reaches capacity. The runbook should state whether the system stops, rolls to a protected archive, deletes only data beyond the approved retention period, or requires an operator intervention. Never allow an undocumented overwrite policy to erase the interval you later need to reconstruct.
Use an explicit time design
The SPE Drilling & Completion paper “Clock Synchronization and Timestamping of Data on Acquisition at the Wellsite: Guidelines and Recommendations,” published online June 8, 2023, treats clock alignment as a data-integrity issue. Its recommendations include one rigsite master clock tied to a global reference, local time servers for periods when that reference is unreachable, primary and secondary time servers, monitoring, UTC storage and a startup procedure after a rig move.
Rank #2
- Get NVMe solid state performance with up to 1050MB/s read and 1000MB/s write speeds in a portable, high-capacity drive(1) (Based on internal testing; performance may be lower depending on host device & other factors. 1MB=1,000,000 bytes.)
- Up to 3-meter drop protection and IP65 water and dust resistance mean this tough drive can take a beating(3) (Previously rated for 2-meter drop protection and IP55 rating. Now qualified for the higher, stated specs.)
- Use the handy carabiner loop to secure it to your belt loop or backpack for extra peace of mind.
- Help keep private content private with the included password protection featuring 256‐bit AES hardware encryption.(3)
- Easily manage files and automatically free up space with the SanDisk Memory Zone app.(5). Non-Operating Temperature -20°C to 85°C
Document which clock each system uses and whether it stores UTC, local time or an offset. Keep the original source timestamp with every record; receipt time can be stored separately for latency analysis. A rig that has moved or remained disconnected may have a materially incorrect local clock, even if the network appears healthy when it returns.
Test failover before remote work starts
Run a controlled test that disconnects the primary WAN or satellite path and verifies local acquisition, alarms, retention, operator displays, fallback communications and restoration. Baker Hughes describes risk assessment, escalation procedures, pre-switch testing, VPN extension, encryption and round-the-clock support in its oil-and-gas infrastructure offering. Those are vendor-described practices, not independent performance measurements, so adapt the test to the actual site.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute- Confirm that records continue to be written locally and that the secondary copy is receiving data.
- Verify that an outage marker is visible to rig and office personnel.
- Exercise the alternate voice or messaging channel.
- Measure how operators identify the last acknowledged remote record.
- Reconnect and check whether late records arrive without duplication or reordering.
Operate safely while the link is down
Declare and bound the outage
At detection, log the outage start using the rig’s designated time source, name the failed path and list affected streams. Record whether the rig is in normal local mode, a degraded mode or a hold pending authorization. Use the agreed escalation tree rather than inventing a universal time threshold; acceptable thresholds depend on the well, geography, safety case and communications design.
Keep collection and local decisions running where approved
Continue local acquisition and approved control functions if the system and procedures permit it. Keep alarms and interlocks local. The driller, toolpusher, company representative and other named roles should know who can authorize a change when the remote center cannot be reached. If a decision requires remote expertise, use the fallback communication method or suspend that activity under the site procedure.
Make missing telemetry visible
Show the outage state in local and remote interfaces when possible. Preserve the last valid record, the time of the break and the first time service resumes. Do not fill a gap with a flat line or a copied value that could be mistaken for a measurement. If someone estimates or manually reconstructs a value, label it as estimated or reconstructed and retain the supporting note.
Rank #3
- NEARLY 2X FASTER THAN OUR PREVIOUS GENERATION(8) – move 1,000 high-res photos in under 60 seconds(6) with up to 2000MB/s transfer speeds(2).
- IP65 RATING AND UP TO 3M DROP PROTECTION(3) – protects against spills and drops.
- POCKET-SIZED – fits easily in pockets and small bags.
- SPACE TO OWN YOUR AI CONTENT – speed and capacity to download your high-res clips and photo edits.
- 256-BIT AES ENCRYPTION(4) – helps keep private files secure with password protection.
Protect source records
Do not silently overwrite local files when a central system sends a retransmission request. Write-protect or otherwise preserve the original source data, event sequence and operator logs. A delayed record must remain distinguishable from a record acquired at the time it is received.
Reconcile records after service returns
Reconnection restores a path; it does not prove that the central record is complete. Reconciliation should be a documented control with an owner and an approval point.
- Record restoration by system. Log when the network, historian, acquisition gateway and each individual stream regained service. A link can be up while one application remains stalled.
- Define the expected interval. Use the outage start, restoration time and each stream’s sampling schedule to identify the time ranges that should exist.
- Compare local and central evidence. Check local files, sequence numbers, event counts and central receipt logs. Mark intervals as received, delayed, missing or not applicable.
- Check retransmissions. Look for duplicate records, changed ordering and repeated blocks after a queue is replayed. Preserve both source time and receipt time so late arrival is explainable.
- Resolve exceptions by source owner. The owner of the instrument or application should determine whether a gap is a true non-event, a failed sensor, a storage failure or a transfer failure.
- Document any correction. Keep the original record, the reason for a manual correction, who approved it and when it was applied. Never make a corrected value appear to be a directly acquired value.
- Recheck clocks. Confirm synchronization before cross-system calculations, especially after a rig move or a long disconnection. If clocks disagree, correct the time basis before correlating depth, pressure, torque or events.
- Approve closure. A named data owner should sign off that required streams were reconciled, residual gaps are explained and downstream users were notified.
Distinguish four kinds of “missing” data
- Transmission gap: the source has a record, but the central system does not.
- Acquisition gap: the instrument or local application did not create a record.
- Clock error: a record exists but appears in the wrong interval because its source clock was wrong.
- True non-event: the operation produced no value or event, which must be supported by the local log rather than inferred from silence.
Keep rig and office clocks aligned
Independent clocks at the rig, service companies and remote center can make the same event appear to occur at different times. High latency makes receipt time especially misleading. Use a rigsite master clock synchronized to a global reference when available, local time servers during loss of access, and primary and secondary time sources. Monitor offset and alarm on loss of synchronization.
Store timestamps in UTC where the system supports it, retain the source timestamp during aggregation and store local display time only as a presentation choice. After a rig move, run the documented startup procedure before relying on cross-system analysis. A clock that is several minutes wrong can misalign depth, pressure, mud-pump and alarm records even when every individual record looks plausible.
Choose architecture by recovery behavior, not dashboard appearance
Centralized, edge and cloud designs can all be valid. Compare them on the controls that matter during and after an outage.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #4
- Note: Magsafe is not available in this version
- High-speed Data Transfer: Lexar external SSD ES3 supports USB 3.2 Gen 2 up to 1050MB/s read and 1000MB/s write to transfer files fast for more efficient work. (Performance may be lower if not supporting USB 3.2 Gen 2 on Mac and other systems)
- Wide Compatibility: Lexar Portable SSD ES3 compatibility with iPhone 17 series (Not supported on iPhone 14 and older models), Android mobile devices, laptops, cameras, Xbox X|S, PS4, PS5, gaming console, and more
- On The Go: Lexar external solid state drive ES3's thin, stylish, and durable design, weighs 42g and is only 10.5mm thick, making it smaller than a card and easily fits in your pocket. It comes with a Type-C cable for plug-and-play convenience
- Data Safety First: Lexar SSD ES3 includes Lexar DataShieldTM 256-bit AES encryption software to protect files
| Decision axis | Questions to answer | Evidence to require in a test |
|---|---|---|
| Local resilience | Can acquisition, alarms and essential processing continue without WAN access? Is there a secondary local copy? | Observed local operation during a planned link interruption and a storage-failure test. |
| Recovery behavior | Can the system identify missing ranges, preserve event order and source times, and replay late data without duplicates? | A reconciliation report showing gaps, sequence checks and duplicate handling. |
| Interoperability | Which formats and interfaces cross operator, contractor and service-company boundaries? Who approves schema changes? | Documented mappings, version control and an owner for each interface. |
| Time integrity | Is there a shared time source, local fallback, offset monitoring and UTC-based source timestamp handling? | Clock-offset alarms and a post-disconnection timestamp comparison. |
| Security and governance | Are access, encryption, retention, escalation and ownership defined? | Access review, key-management procedure, incident contacts and retention evidence. |
| Operational dependency | Which decisions require live remote access, and what is the approved local fallback? | A signed responsibility matrix and an outage drill with decision handoffs. |
Baker Hughes describes its Kantori offering as centralized data management with edge and cloud deployment across wellsites, remote operations centers, enterprise systems and third-party applications. NOV describes WellData 4.0 as remote monitoring with surface and downhole time-series data plus rig context. These descriptions establish vendor-stated features, not a head-to-head test or proof of performance at a particular rig. Evaluate any platform against the recovery tests above.
Understand the bandwidth and telemetry limits
Downhole telemetry is not the same as rig-to-office connectivity. A US Department of Energy National Energy Technology Laboratory document associates mud-pulse telemetry with approximately 3 to 10 bits per second and describes the resulting limits on data resolution and real-time decisions. That figure applies to the downhole-to-surface telemetry method discussed in the document; it is not an internet-speed statistic for a remote rig.
Design decisions should therefore separate three paths: downhole-to-surface measurement, local rig network traffic and the WAN or satellite link to the office. Buffering and prioritization can protect critical alarms and acquisition, but neither creates information that the downhole channel never delivered.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Set governance, security and communications rules
Assign responsibilities across companies
Write a responsibility matrix covering collection, local retention, transfer, reconciliation, correction approval, access and regulatory submission. Include the operator, drilling contractor, mud logger, directional-drilling provider, measurement-while-drilling provider and any remote-center team. Standards such as WITSML and PRODML can ease exchange, but they do not decide who owns a gap or who may alter a record.
Define secure connectivity and change control
Use the site’s approved VPN, encryption, identity and least-privilege controls. Record which systems may be reached from the remote center, how credentials are rotated and how an emergency access request is approved. Baker Hughes’ infrastructure material describes VPN extension, encryption, risk assessment, change management, escalation and support as elements of its offering; treat those as a vendor example and verify that the deployed controls meet the operator’s security standard.
Best Value
- NONSTOP SPEED: Race through projects with our fastest SSD for creators; Load, edit and transfer with sustained read and write speeds of up to 2,000MB/s1; The T9 Portable SSD performs at high speeds even during longer processes
- DYNAMIC THERMAL GUARD: When you’re elbow-deep in a passion project, the T9 Portable SSD stays cool; Its advanced thermal solution withstands and controls heat to keep the SSD at ideal temperatures—even in heavy use2
- ADAPTS TO EVERY NEED: Whether you’re using a desktop, camera or a gaming console3, count on the T9 Portable SSD for extensive compatibility; It’s a true team player when it comes to heavy-duty application usage or file-saving
- STRONG. SOLID. STABLE: From concept to completion – the T9 Portable SSD gives you the longevity to last through heavy use with one convenient drive that dares to go the distance
- WORKS LIKE MAGIC: Your T9 Portable SSD performs like new with the always up-to-date Magician Software; With firmware updates, extra encryption and continual monitoring of your drive health, it works like a charm
Prepare communications fallbacks
Document primary, secondary and tertiary channels, the contact list, message format and check-in interval. A fallback channel should carry enough information to identify the well, current operation, safety status, outage start, affected systems and requested decision. Do not publish a universal switching threshold; establish one for the actual link, weather exposure, geography and risk assessment.
Regulatory reporting does not pause automatically
Reporting obligations vary by jurisdiction, well type and activity. Alberta’s Directive 059 release identifies August 11, 2025 as its release and effective date and sets out data-filing routes. That directive is an Alberta-specific example, not a universal rule. Before mobilization, identify the applicable current regulator requirements, required records, submission windows, accepted formats and portal or filing route. After reconciliation, compare the approved record with what was submitted and retain evidence of any correction or late filing.
Troubleshoot common failure patterns
The dashboard is blank, but local acquisition is healthy
- Confirm the last central receipt time and compare it with the local historian.
- Check the gateway queue, VPN state and application process separately; do not assume a green network icon means the data service is healthy.
- Keep local collection running and declare the outage interval.
The central system shows duplicate or out-of-order records after reconnection
- Stop automatic overwrite or reprocessing if it would destroy source evidence.
- Compare source sequence numbers and source timestamps with receipt times.
- Have the stream owner approve deduplication and document the rule used.
Rig and office events do not line up
- Compare each system’s clock, offset and time zone.
- Use the rigsite master and UTC source timestamps as the reference.
- Run the post-move or post-outage synchronization procedure before calculating derived events.
Storage fills during a long outage
- Follow the pre-approved retention and rollover policy; do not improvise deletion.
- Protect the secondary copy and verify that it is readable.
- Escalate before capacity is exhausted and record any stream that entered a degraded mode.
A practical outage runbook
- Detect: alert the rig and remote-center contacts and note the source-clock time.
- Classify: identify failed paths, streams and operating mode.
- Stabilize: keep approved local acquisition, alarms and controls active; suspend decisions that require unavailable authority.
- Communicate: use the fallback channel and send the well, status, outage start, safety condition and requested action.
- Preserve: protect local primary and secondary records, operator logs and source timestamps.
- Restore: bring services back in a controlled order and record restoration time for each stream.
- Reconcile: compare expected intervals with local and central records, checking duplicates, ordering and clock offsets.
- Approve: obtain data-owner sign-off, notify downstream users and complete any required regulatory correction.
What to measure in drills and reviews
- Time from link loss to declared outage.
- Percentage of required streams with verified local retention.
- Time to establish an approved fallback communication.
- Number and duration of unexplained intervals after reconciliation.
- Duplicate, reordered or manually reconstructed records detected.
- Clock offset at outage, restoration and final approval.
- Time from restoration to data-owner sign-off.
There is no representative cross-industry statistic establishing how often remote drilling WAN outages occur, how long they last or what percentage of data is lost. Use measurements from your own outage drills and operations rather than inserting a generic reliability number.
Recommended Free Tools
Bottom line for remote drilling teams
Connectivity resilience is an operating discipline, not a faster dashboard. Keep essential functions local, retain redundant source records, synchronize clocks with a fallback, define ownership across companies, and make reconciliation a required control after every interruption. When the network returns, trust only the intervals that have been checked against source data and approved by the responsible owner.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
