Data Acquisition & Management Improving Work Flow Efficiency Master Class

1. Data Acquisition & ManagementImproving Work Flow EfficiencyMaster Class Sam Simonian Eclipse Petroleum Technology Limited IQPC London – Precise Production Forecasting for Improved Portfolio Management April 2005

2. Agenda • INFORMAL… • Design • How do we go about designing an efficient workflow • What are the key questions? • Who do we need to target within the asset • What can we do to help ‘smooth’ the process of change management • Implementation • How to phase the project • How to project manage implementation • Learning's • Capturing the learning's and applying elsewhere • What went well / what did not go so well • People – Their feedback is key! • Outcome • To produce workflow diagrams for stakeholders and well site personnel.

3. Design • Site Assessment: • Objective: Visit asset and spend 4 to 5 days understanding the current workflows • Identify key stakeholders: RE’s, PT’s, PE’s, IT • Well site visit – • What are the workflows, • How are production reports generated • How are well test reports generated (how often) • How long does it take to produce a report – Is it automated? Manual data entry? • What technologies are in place (e.g. P&T gauges, MPFM’s, instrumented separators…) • What computing infrastructure is in place (DCS/Scada/Standalone systems) • Any connectivity issues between well site & office?

4. Design • Site Assessment: • Office – • How is ‘production data’ gathered in the office • What are the key data requirements from the stake holders • What do the stake holders do with the data – any manipulations required • How long does it take for them to find the relevant information • Who are the partners – what are their requirements • What are the corporate and commercial requirements (reserve accounting) • Outcome  Site Assessment report

5. Design • Create an Implementation Plan: • Create a project plan • How to phase a project • What can be done to realise ‘quick value’ • Create simple solutions based on existing software and infrastructure • Roll-out and train well site and office personnel • Create ‘generic data management system’ • Carry out evaluation of vendor products • Talk to other operators – what are their experiences • What are the ‘building blocks’ that are required for an effective data management system?

6. Design • Create a Business Case: • Why do we need a business case – Isn’t it obvious? • 9 time out 10 we require a business case • To show benefits that can be derived from a data management system • Asset level: • Reducing non-productive time • Halving manipulation time • Better allocation procedures • Standard reporting for internal and partners • Lower opex • Corporate level: • Reserve allocation/accounting • Loss accounting • Corporate standard reporting • Increase enterprise efficiency

7. ONSHORE OFFSHORE/ WELL SITE DCS Automated Daily Production reporting Scheduled Daily Download Automated Download & QA/QC of well test data Download on demand THP’s DHG’s Separator Flow Offshore System System flexibility to add new data streams

8. Daily Production monitoring Daily production data and report File Server Well test data analysis (QA/QC), Flow factors Well test data Automated update of flow factors in daily production reporting software Onshore System

9. Implementation • Use the implementation plan to: • Present scope of work to • Onshore engineers • WellSite personnel • Explain project phasing • Implement • Train users

10. Sensors and process data e.g. Platform process, Separator sensors DCS Wellsite Historian to capture and store all data Wellsite OPC Require a good link between wellsite and office Minimum download rate – every 15mins If comms fail, wellsite Historinan to continue to try to send data Communication Office Historian to capture and store all well site data Serves as Real-Time feed Minute by minute real-time data stream Web interface Office Historian client applications e.g. Excel add-in Application Server Daily/weekly data analysis Data Base applications e.g. QA/QC, Production allocation Production Data Base Monthly yearly data analysis Data Base applications e.g. Eclipse HQ Corporate Data Base Next Steps… WHY ?

11. Learning's • Capture the lesson’s learnt during implementation phase: • Did project go well / not so well • What was good / what was not so good • Peoples reactions • Was implementation/system embraced with open arms or not? • Follow-up

12. Learning's • Start simple • Complex and costly solutions are not necessarily the best…. Try and use what you have and what your staff are comfortable with… Utilise existing and known tools • Systems have to be usable by the available resources • Importance here is to focus on work flow and change management • Fully understand the work & data flow – don’t assume anything! • Understand the day to day challenges • Spend time with offshore & onshore personnel • Explain the concept of efficient workflow • Ensure good quality data • No production data management system will have value without proper validity and QC processes

13. More learning's • What went well • Positive engagment by both offshore and onshore personnel • Understanding of the problems and suggesting solutions was a team effort • Change management • Discussing issues with the real players (offshore and offshore) • Getting buy in and ownership • Effective communication across different disciplines (RE,PE, WS, IT)