June 11, 2019 | Real-Time Application (Client)

Known Issues

  • Channel count changing mid-stream can cause issues.
  • Batched data (FracPro) may cause gaps in data on Browser.

Updates & Improvements

  • Added “Refresh Stream List” button to the right of stream list dropdown.
  • The client will now attempt to reconnect on loss of connection to the data source.  This process runs for 30 seconds, after which users will need to manually restart the stream.
  • On loss of connection to the data source, the client will notify the user via an on-screen prompt and Windows notifications (Windows 7 and 10).
  • The client will now sync channel names and units between other clients and the server.
  • The client will now remove data that is synced with the server and over 30 days old from the local machine.
  • The client will now display an icon in the system tray.  
  • Closing the app via the X button will now minimize to the system tray. 
  • Improved process for syncing and reconciling data that was not transmitted due to a lost internet connection.
  • Events now require an Event Type, Well, and Stage to be entered.
  • Data received by the client at a rate higher than 1Hz will now be throttled to 1Hz.

Bug Fixes

  • Improved text of error messages when connection to data source is lost.
  • Fixed an issue that could cause the client to improperly report a failed connection.
  • Improved behavior on Serial (RS232) connections.

 

June 24, 2019 | Real-Time Application (Browser)

Known Issues

  • The “Favorite” icon on Stream List is not currently functional.
  • Y-Axis labels may not be visible depending on screen resolution.


Updates and Improvements

  • Added Real-Time Stage Comparison.  You can now compare your current stage against any previously flagged stages. 


Bug Fixes

  • The “Refresh Chart” button will now check stream status
  • Fixed an issue when editing the events grid where the time was not configuring properly

 

June 18, 2019 | Real-Time Application (Browser)

Known Issues

  • When flagging events with multiple streams enabled in the RT Viewer, the “Select event time” banner may not align properly with the screen.
  • The “Refresh Chart” option on RT Viewer does not reconnect to the stream if connection is lost.
  • The “Favorite” icon on Stream List is not currently functional.
  • Y-Axis labels may not be visible depending on screen resolution.

Updates and Improvements

  • SMS Alerts: Users can now configure alerts to send via SMS.  Please note that you need to have a phone number configured on your user to receive these alerts.
  • Event Flagging: Users can now flag events (Stage Start/End, Comments) on the RT Viewer, as well as via the Events screen in Stream View.
  • Demo Pads will no longer be visible in the WDL Real-Time client as an option to stream data to.

 

June 15, 2019 | Completions

What’s New

  • Proppant Loading on Treatment Data
    • In our latest attempt to give the people what they want, we’ve added a new field to the Treatment Data page called Proppant Loading. You can find it in between Frac Gradient and Horsepower in the Summary section.
    • We’ll calculate a value for it using depth features if we can, otherwise you can enter your own overrides.
  • Proppant Loading on Reports 
    • Jump straight into some analytical fun by visualizing this new field on Scatter Plot, Stage Variance, and Depth Variance. You’ll find it nested under the Proppants section on data selectors.

Updates & Improvements

  • Calculated Horsepower!
    • Turning dreams into realities once again, we’ll now calculate a value for horsepower from average treating pressure and average slurry rate. Don’t worry, you’ll still be able to enter your own override because less is never more when it comes to control over your own data.

Bug Fixes

  • A lot of things can happen that should result in a recalculation of Job Totals. So many, in fact, that we’re still finding them. We added another trigger around changes to metered data to recalculate those totals so that your data stays up-to-date.
  • For a few API endpoints, the ChangeUtc parameter was returning results in a way that was, put plainly, super confusing. We’ve tweaked it so that it’ll return results in a manner that is more consistent with the other endpoints.
  • Of course, it wouldn’t feel right if we didn’t have to do something with the Treatment Data Import sheet. Under some very specific circumstances the importer was improperly rejecting Breakdown and ISIP flags. It’ll stop being so difficult and only reject the bad ones now.