New edition – OREDA 2015 handbook
One of the main reliability data sources for the oil and gas industry now has a new edition – OREDA 2015 handbook.
Before using the database, it is useful to know how the handbook has evolved over the years. Oreda project was initiated in 1981 and the primary aim was to collect reliability data for safety equipment. As the project became an important source of data, in 1983 it was decided that oil and gas companies should be in charge of the project. To give us some context with our tools, this was also the year where the focus was to collect data from the operation of offshore oil and gas production facilities to improve the basic data. Currently, the Oreda project is run in phases normally lasting for 2 – 3 years.
You can see more about Oreda’s history here: http://www.oreda.com/history/
The new edition comes with a new name: Offshore and Onshore Reliability Database. The topside and subsea handbooks are both divided into two parts: Part I describes the OREDA project, the different phases of data collection; Part II, the estimation procedures used to generate the generic reliability data tables.
There are some additional classes in the Oreda database which I believe are going to be extremely helpful. We can highlight some of the new classes involving subsea items:
- Subsea power cables
- Subsea control system
- Subsea pumps
- Subsea vessels
- Common components
In order to obtain a reasonable population for presenting reliability data for topside equipment in the 2015 edition, some data from phases VI and VII already issued in the previous 2009 handbook (5th edition) have also been included.
It is important to notice that the topside data typically doesn’t cover the entire life of the system/equipment. Generally, infant mortality is not collected thus the data collected are for the useful life of the bathtub curve in normal operating environment.
Utilising Oreda requires experience. Reliability data are collected over a number of installations so the first thing to check is the population size. Rule of thumb is: if the population size isn’t big enough, be careful. Another important point is the boundary of the dataset. Check if a component or auxiliary equipment/component is within the boundaries to avoid miscounting an item.
You have to convert data from millions of hours to years. This is easily done in Maros at the convert field:
More information here: http://www.oreda.com/