What is Beta?
In software, beta phase generally begins when a feature is complete and stable but could encounter unknown issues when applied in real-world situations. Beta reduces impact on users because it sets the expectation that there may be additional changes made to the feature. Additionally, it allows the software company to evaluate the performance of features in the real world and to verify all requirements are met before pushing it to production.
Why was it important for Drakewell Anti-Collision to be in beta?
Drakewell Anti-Collision was released in beta in 2019 for two reasons:
- At the time of Drakewell Anti-Collision feature deployment, ISCWSA (Industry Steering Committee on Wellbore Survey Accuracy) had not approved the release of version 5 of the error model, and
- It was not possible to know or to test every potential scenario during development. Due to the criticality of the results the anti-collision model produced, beta allowed the feature to be tested in the real world with the expectation of the possibility that issues could arise which would need to be addressed.
We stand by the reliability of our software and any modeling or calculations contained within. During development, we implement automated testing (code testing code) and user testing before we deploy new features to clients. Most features do not require a beta phase.
Drakewell Anti-Collision is now out of Beta
ISCWSA approved the release of version 5 of the ISCWSA error model in October 2019. See release notes here.
Drakewell’s clients have sufficiently used the feature and validated that, when inputs match, Drakewell anti-collision results are consistent with other anti-collision software solutions.