The OEM asserted that a new BOP control system was necessary due to advances in technology and the operating system nearing its end-of-life cycle. During FAT and commissioning, Athens Group Services observed anomalies in the functionality of the control system while the OEM continued to try to iron out the bugs in the new software architecture.
We became increasingly aware that the control system problems would jeopardize the rig’s ability to go on contract. Recommendations to roll-back the operating system and software were noted but not acted on. When the system froze while preparing to drill a test well during rig acceptance tests, the OEM finally agreed to roll-back the software to an earlier version that is widely used in the industry.
Athens Group Services provided software configuration management and quality assurance during the roll-back, re-commissioning, and regression testing. That process took over 3 weeks of downtime, a lengthy and costly delay in getting on contract. Earlier action to roll-back the control system operating system and software would have avoided that downtime.
Why do you care?
This costs you money, time and potential degradation of safety. Functional, mission-critical software is not something that you test in production. OEMs must be held to a higher standard, and you, the customer, must do the “holding”.
What can you do about it?
When FAT and commissioning tests reveal problems in the OEM’s system, you need to quantify problems as early as possible and understand the timelines for corrective action. Add “software” to your contracts, document the processes, and HOLD the OEM responsible. It’s your and your crew’s safety at stake.