On February 2nd 2017 we launched the first beta of Oliasoft Wellplan and we will be adding users that have indicated an interest in participating gradually going forward.
Currently we are beta testing our casing design module. Beta testers will have access to an early version of our trajectory module which is currently fairly limited, allowing for import and modelling of simple well trajectories. The casing design module is complete, but we will keep adding new features during the beta test and later, based on feedback from current and future customers and partners.
Typically a test of Wellplan today involves the following steps:
- Import or model a well trajectory
- Enter overall well and location parameters (depths, pressures)
- Enter geological input tables (pore- and fracture pressure)
- Add any number of casing sections with any number different pipes
- Add any number of relevant load cases (burst, collapse, axial), with any combination of external gradients and temperature models
- Visual inspection in 3D (verify trajectory and casing sections)
- Visual inspection of load case simulation results (differential pressures, weights, triaxial effects, both as charts and tables)
- Iterate by modifying designs, going as far back as point 4.
- Generate final reports and summaries
Platform and Equipment
Wellplan is delivered on a software-as-a-service platform. This means the primary user interface (for humans) is a web browser. For computers (using our APIs) we speak REST+JSON. Internet access is required while beta testing. We are considering adding support for private clouds and/or hosting later (and is not part of this beta test).
Most modern web browsers are supported. Our developers mostly use Chrome while developing, but we test and verify on other browsers regularly. Wellplan should already work well on the following platforms:
- Chrome (Windows, macOS, Linux, Android)
- Microsoft Edge (Windows)
- Safari (macOS, iOS)
- Opera (Windows, macOS, Linux)
- Vivaldi (Windows, macOS, Linux)
Effectively this means Wellplan runs on most kinds of computers, including touch devices like iPads and tablets, and even mobile phones. Our user interface even supports advanced features like touch gestures and more. Please note however that standardisation around touch and gesture interfaces is an ongoing process and very much a moving target, so expect some issues from time to time until things settles down.
If you find any issues in Wellplan that keep you from continuing testing, the first thing you should always do is to try it in Chrome. If it works in Chrome, it means it is a platform issue. We still want to know about it, but at least you can keep working.
While we've already mentioned Wellplan runs on mobile phones, it's typically not a platform that is well suited for actual work. Compared to actual computers, mobiles are still pretty slow. And all touch devices are not good devices for inputting lots of textual/numeric data.
Which brings me over to another point, related to speed. On modern computers (e.g. less than four years old) with sufficient RAM Wellplan should be more than fast enough. It will get even faster, but we will balance our effort with speed with the need for improving other parts of the system. Feel free to use this as an excuse to buy a modern computer .
Wellplan makes use of interactive 3D models for visualisations. The technology used for this is named WebGL and was launched in 2011. Long story short, it allows programs running in the web browser to access the powerful 3D graphics cards that can be found in virtually any kind of computer or device with a screen the last 10-15 years. Which means that we still get pretty surprised when large computer vendors still manage to ship computers where a basic install of Chrome manage to run with WebGL disabled by default. It's usually very easy to fix; when/if we get reports of 3D views not working we share the necessary workarounds here. Having said that, most computers and browser should run with WebGL enabled by default now.
Crashes and Instabilities
As an early beta tester, expect this. Fortunately a "crash" in a browser mostly means the software running in it hit some unexpected error. The "crash" mostly manifests itself by some output missing (empty graphs) or some button not working (being non-responsive).
The first "standard" test is simply to reload the dataset you were working on. You have saved your work regularily, right? If you did and a reload works, great, keep testing. If it doesn't, please tell us when/how and why if you have a theory. Share with us the URL to the screen where you hit the bug.
With your help we should be able to get such errors fixed very rapidly. We're already deploying new releases multiple times a day, so best case, if you identify a showstopper bug we should have you up and running again in a very short while.