I want to thank the thousands of users that took a few minutes to take our poll, which asked the following two questions:
- “What is the likelihood, on a basis of 0-10, to recommend DI to a colleague”?
- “What one thing could we do that would raise the score you gave us”?
The results are very telling, and have really helped us allocated and prioritize our resources this year. This is exactly what we wanted in a poll. So, without further adieu, here are the results:
Our overall average score was 8.6. Our overall Net Promoter Score was 51% (Net Promoter Score is a score that helps determine customers satisfaction by taking the percentage of “promoters”, ie those that gave us 9s and 10s, and subtract the “demoters”, those that ranked is 6 or below, including takers with no response. For more information, visit https://www.theultimatequestion.com/theultimatequestion/measuring_netpromoter.asp?groupcode=2).
“User Experience”- The largest bucket, was what we broadly call “User Experience”, in other words, ideas on how to make the application more user friendly. Of the myriad of suggestions provided in this bucket, the following , in order, were most important.
- Mapping Interface, (Target Q2 2010, culminating in a much more functional and clean map interface),
- Search Wizard and Interface, (We have a beta design for this. We will roll it out as an optional feature to existing users and as our go forward to new users. Slotted following Mapping Interface, 2010),
- Fixed Table Column Header, (Not as easy as you might think. Researching best way to do it),
- Increase Truncation Limits and make 1000 items automatic, (Done, Released), and
- Cleaning up and flattening the Related Filings Page (bring more data up to the page, less click throughs), (Complex redesign, Probably 3rd Q, 2010).
- Faster Searches and data delivery (This is an important issue. We are delivering tens of times more data in our map layers with the introduction of our LandTracts and Unit Tracts. Also, certain searches we find really bog the system down. We are working on this with a multiprong approach. First, we are working consistently on mapping interface optimization; Second, we are creating what we call “roll up tables” for the more complex or database intensive queries that bog down our database; Third, we are doubling our “performance” capital budget in 2010 over very healthy 2009 levels to create a more scalable , much faster infrastructure that has root speed of 5 x existing hardware speed. I will keep you updated on our progress here).
“Enhancements”- The second largest bucket was what we broadly refer to as“Enhancements”, which is comprised of either migrating more Plus functionality/data to Basic Members, expanded Plus functionality/data, or new overall functionality/data. The five most popular requests were for the
- Well Report Generator to be migrated to Basic (AKA bulk printing of Well Files), (Done, Soon To Be Released),
- TX Water Production available to Basic on the lease level, (Done, Released),
- Pre-Regulatory cumulative production available to Basic rolled up to the lease level , (Done, Testing)
- Improved annotation and printing of maps, (In Beta Release as “PDF Download” on Map Tools. Necessary enhancements In Progress)
- Improved data download functionality, (Lat Long to Selectable Columns for Plus Done, Soon to Be Released. Investigating additional changes through 2010)
- Better charting and economics, (First iteration in testing, Soon to be Released),
- Better Multiwell Charting, (Scheduled for Q3 Release), and
- Lower Cost Well Logs, Free RRC Logs for BASIC. (OK, dang it. You got it. Soon to be Released)
“Deeper Data”- The third largest group of requests fell into what we call the “Deeper Data” bucket. These requests comprised:
- Adding more leasing details (this appears to be a real misunderstanding of what we already offer. We were asked to provide what we already offer in most cases, and full title information in others; a full explanation to clear up misunderstanding of what we have here will be published this week in the Wireline) (Done, we currently cover full Title data in Northern Louisiana where there are prescription laws, full Title data would be a much enhanced price. Let us know if you are interested),
- More old well scout file integration (will add much more during 2010),
- Completion information in those states where we don’t have it (Goal is to add 23 states of completion data during 2010. They will be online state by state as we finish them).
“State Expansion”– Given that we have just acquired HPDI and added 23 more states of production data and permit data, and that we are focusing, during 2010, on adding most or all of the 23 states for completion information, this is probably a failure on our part to educating our members effectively of what we had done, what they currently have available, and what we are working on so… (Done, Released).
“Data Accuracy”- The fifth bucket was “Data Accuracy”. The particular issues most mentioned were:
- Mapping of data to older well locations and cleaning up the API 0000 issue, (Ongoing),
- Clean up and finish reconciling old NM production data coverage, (currently, it is releases as separate data streams attached to wells, needs to be “stitched”), (In Progress),
- clean up KB’s in Louisiana,
- better reconcile Texas pre-completion production,
- better reconcile the non-unique Gas ID problems, (this results in a production stream being attached to the wrong API, and occurs as a 1 in 2,000 occurrence problem), (In Progress, Soon to be released and fixed on an ongoing basis),
- Well locations (we have a similar issue with locations that don’t have X,Y or Lat Long or where the X,Y/Lat Long does not correspond with Footage Calls or Plat, where a 1:1000 occurrence data entry mistake places a well in an adjacent Section or Abstract). (Instituting data entry process fix that should result in 1:10,000 occurrence or better. In Process, soon the be released and fixed on an ongoing basis, Released: Aerial Photography Layer for location QA/QC by user), and
- Design a better method to relate Preliminary Production to API’s prior to completion report being filed or Gas ID/Lease ID being assigned. 9% of new production, (this issue is more an intuitive user interface issue than a real data error, per se. We have the data, it is available via a search, but it won’t map, and the API is not assigned. We currently assign 80% of these by hand, but the bigger problem is cleaning up and reconciling the data after it appears on the well master), (In Process, soon to be released).
“Cost”- Believe it or not, the last major bucket was “cost”. Cost was much more an issue for small users than large, and, by adding many of the features above, we believe that many of you will hopefully appreciate the added value of the system. We are investigating ways of making some sort of Regulatory Data Only DI membership available for non corporate users.
In any case, I want to thank all of you for participating. For those that didn’t see their specific issue addressed, be assured we are aware and will incorporate those suggestions we can as we progress with this. Next year, same place and same time, you will be able to tell us if we have met your expectations. We recognize that we exist solely to make your job easier, more profitable, and more fun. We also have a couple of neat new things coming this year that percolate from the fevered minds of some of us here that constitute our Wildcat philosophy… something no one asked for because they think it can’t be done. Hope you like them!
Latest posts by Allen Gilmer (see all)
- Why Has Drillinginfo Expanded Into Oil and Natural Gas Marketing and Renewable Supply and Demand? - February 23, 2018
- The Price Of Oil: Looking Ahead Without All The Noise - January 21, 2016
- Drillinginfo’s US Oil Production Forecast - April 7, 2015