Since we created our cloud service in 2009, one of the first in oil and gas and still the leader, we have built and managed our own infrastructure in multiple data centres in the UK. After a year of work, in the next week we’ll be moving our platform to infrastructure provided by Amazon Web Services, and I wanted to explain why.Details
EnergySys is pleased to announce the US version of our Production Allocation Standard app is available for all US Onshore producers.
The US Onshore oil and gas market has several unique characteristics that can often make out-of-the-box solutions harder to implement, creating costly and time consuming projects. With this in mind, we saw an opportunity to develop a new version to cater specifically for the US onshore marketDetails
EnergySys Inc is delighted to announce that ZaZa Energy Corporation has joined the growing number of oil and gas companies using the market-leading Production Allocation Standard (PAS) App. The agreement between EnergySys and ZaZa Energy was completed on 5 May 2014, and the system was configured and fully operational within 6 weeks. EnergySys is the first cloud-based platform…Details
People often ask me how our cloud service for production data management, production reporting and production allocation is different from traditional solutions. This is a hard question to answer, as I want to describe the distinct values of my product and company without seeming to denigrate the competition.
In addition, it’s really hard to provide quantitative information. We think an EnergySys solution is hands-down the fastest, most cost-effective and most configurable choice for customers, but this is largely based on anecdotal evidence. It’s rare for two companies to have delivered systems for the same assets under the same conditions, though we do have a fair amount of experience of replacing competitor systems, so an exact comparison is difficult.
However, during the course of a discussion with a company looking to replace a competitor system I realised that part of the answer lay in the conversation we were having. This user kept talking about projects. Projects to implement new assets. Projects to add new fields or wells. Projects to upgrade the basic software. Everything was a project. And projects required substantial time, money and resources, even just to get a basic upgrade of the software done. In fact, for this user an upgrade cost almost as much as the original project implementation! EnergySys isn’t like that.Details
Register now for the latest EnergySys webinar: The Only Production Dashboard You Need.
On the 16th of July at 2pm BST (8am CST) James Robertson (Global Sales Consultant, EnergySys) will deliver a 20 minute demonstration of our mobile dashboard functionality followed by an interactive Q&A session.Details
As many of you know, we have recently refreshed large parts of our production service infrastructure. Parts of the existing hardware, while still running well, had reached three years of age, which represents the point where we deem the ROI on renewal to be about right. In a cloud based service the ROI is made immediately more attractive because the cost is shared between all the consumers of the service.
Also, there have also been a lot of advances in three years for hardware.Details
I’ve spoken at several conferences about the failures in standards efforts in oil and gas, and I’ve commented on the reasons for these failures. I’ve also highlighted the key characteristics of successful standards efforts in other industries. In the short version, this boils down to my well-worn aphorism “adoption beats perfection”. The longer version is contained in the seminal paper by Hanseth and Lyytinen (“Theorizing about the Design of Information Infrastructures: Design Kernel Theories and Principles”, 2004) which, despite its title, contains material that is relevant for all standards efforts. They identify five design principles:
- Design initially for usefulness
- Draw upon existing installed base
- Expand installed base by persuasive tactics to gain momentum
- Make it simple
- Modularize by building separately key functions of each infrastructure, use layering, and gateways
This has led me to consider the goals of standardisation in oil and gas, and what might help with their adoption.
I can see three obvious scenarios where standards could be useful. There are probably more, but let’s start with these three.Details