Productioneer has an extensive paginated report library for our customers to utilize. We have everything from simple data exports to paginated reports that highlight variances and trends.
One of the reports we have had in our library for quite a while, is the Tank Stock report. The user selects a day and the report returns the tank stock and tank production for each tank in the organization for the selected day. It aggregates the stock and production at the tank, battery, field, and organization level and provides the tank strappings (feet and inches) for each tank. It is a standard and widely used report and I know it has not had any significant changes requested to it for at least 3 years.
Disclaimer: Mi4 is not affiliated with Enverus. Mi4 does not endorse or recommend any particular data subscription service.
Mi4 has helped many of our clients integrate data from data subscription services into their own projects and data initiatives. One of the many subscription services we have implemented solutions around is Enverus Drillinginfo’s Direct Access API. The Direct Access API allows Enverus customers with DI Plus subscriptions to access Enverus’ extensive collection of public data and bring it in-house.
TL/DR: Check out our C# Classes and SQL scripts for the Enverus Drillinginfo Direct Access API on our GitHub.
As an end-user of a Power BI report, a chart that looked great at first might look not so great once you start applying filters or using slicers. Very large values in the data might throw off the scales and now your line chart might be suddenly all squeezed at the top or the bottom. Does any of the above sound familiar?
Usually it’s the report designer who has all the power, this article is about giving more power to Power BI end users…
End users’ ability to change the scale, appearance or formatting of that chart is limited. That’s why I started creating the Mi4 Line Chart Power BI custom visual that lets you switch scales on the fly, and eventually have more overall control of the visual without having to edit the report.
As we wrote about earlier this month, the Texas Railroad Commission (RRC) released a treasure trove of data freely available to the public on their site. It was like Christmas in the Mi4 office. After we sang some carols and drank some hot chocolate, we realized that there was so much data. We didn’t know where to start.
Christmas in September
As my colleague @Talal wrote last week, we decided to get Lat/Long coordinates for every Texas well. In his post, he explained, there are many use cases for this data, so it seemed like an excellent place to start.
Last week I wrote a blog post talking about the TX RRC publishing data to the public that previously was only available via a paid subscription.
After downloading the different data sets and examining the various types of data and formats, I decided to take a closer look at the data that might prove to be useful to us and to our Productioneer clients.
It is not uncommon for location and depth data, as well as other well-header and meta data to be incomplete or non-existent during a software migration, after all this data might not be considered crucial for the daily gauge sheets. Especially in the case of Excel gauge sheets, where additional columns are a waste of “prime real estate” and might be considered as cluttering that particular production report.
It would be nice if we have a quick way to pull the Lat Long data in bulk to speed up the on-boarding process.
The accounting team at TPIC was spending too much time doing manual and repetitive tasks to close out the month and generate regular reporting packets for management. Having worked with us in the past, they asked us to streamline the process.
We promised them we’d make the process as fast and as simple as possible, joking that it would be as easy as pressing a button, and now it is!
A process that used to take days now only takes a few minutes, and all the manual labor has been reduced to a single button press, literally.