maersk-drilling-inspirer-1-156
Wells & HSEQ
bredford dolphin 1180
Decommissioning
topstrip 0014 ps forside-bilde
Reservoir
1dbdce62-2444-11e4-b51c-12313d026081-medium
AGR Consultancy
agr energy web and ppt copy2
Software
816 thumb
Facilities Solutions
agr-tracs-training3
TRACS Training
AGR%27s P1 time and cost modelling software enables team collaboration
11.04.2017

AGR's P1 time and cost modelling software enables team collaboration

Collaboration is a vital part of preparing any operation. We will look at how P1™ can aid in the collaborative process.
Preparing any procedure has many challenges and requires a different approach to identifying risks during the operation. Using a multidiscipline team that has implicit knowledge of operations complements whatever explicit information may be available for the operation being looked at. The mixed discipline team helps to avoid blinkered views of how operations should be carried out although it will not overcome the challenge of “Group Think” should it arise.

The fact that all the information is stored in one file ensures that each member of a team can access and understand what process is being followed.

An example of this is the Well Description section of P1™. This allows specific depths to be predefined in the system - the video below shows eight predefined depths. As can be seen in the 20" Casing shoe depth, the depth has been set at 1,350 metres, it also allows the entry of a range of depths if the exact depth is not known accurately, and this range will be taken into account when the software is run. 

More importantly, this is a central section where, if a depth is changed, it will be changed throughout the model. As can be seen from the example, the 20" Casing shoe depth is referred to in 18 places, therefore if this information was not centralised and a change was made, the engineer would need to search through the entire programme to ensure all references were correctly changed.

This obviously benefits team collaboration as it ensures that any changes are communicated throughout the team.
 

As the well Phases are built up, the information from the Well Descriptions are used in the Events. The example below shows how the Well Details information is used in the Event “SW26 - Run 20" Casing”.
 

Another important part of the process is the ability to add information to the Comments box. Often in projects, especially ones that have been a long time in planning, the reasons for making a specific decision have been lost as people have left the project. One method of overcoming this is to have a formal decision log, however these are often not thought about until it is too late in the process. The comments box in all of the inputs allows an explanation about why the information is there.

For example, in the predefined event for "FE08 - Open hole logging", the depth may have been changed once new information became available. By entering the reason each item, the team no longer has to rely on the memory for that decision being within the project team.
 

By using a disciplined approach to building a well model all of the assumptions may be captured, and if they are changed the reason for the change is also captured and communicated to the team.

P1™ is cloud based which allows simple collaboration not only within a single office but also around the world. This means that if there is a Subject Matter Expert in a different location, they can access the P1™ Project and conduct a peer review or monitor how the project is being developed and maintained.

Collaboration within the company is obviously important, but there are other external stakeholders that may also have to be informed and involved. Being external, they will not have access to the Project files to understand what assumptions have been made during the process. This is where the P1™ Reporting function becomes most useful.

Once a project is ready, a simulation is run, using the Monte Carlo engine. This gives an output report as would be expected, however it also generates an Input Report as an Excel Spreadsheet.

The Input report details:
 
  • Project Information
  • Currency Information
  • Well Description
  • Pre-defined Events
  • Phase Model
  • Event Model
  • Cost Information
  • Project Risk Information

input

This report may be used with the customer or the rest of the team to define all the assumptions that have been made, and provided that the team follow the correct discipline mentioned earlier of explaining the rational for each event as they would in a decision log - there is now a detailed record that may be used in the End of Well Report or even if in later years detailing why the decision as made.

If you would like to find out more about benefits of P1™, please click here.

Latest news

2017-08-03 — AGR celebrates success of reservoir modelling book with second edition
Read More
2017-07-19 — Dana Gas to use AGR software for deep water exploration in Egypt
Read More
© AGR. All rights reserved 2017. Norway l UK l Americas l Asia Pacific l Middle East l Africa