Practical Well Log Standards
Organizational Meeting
November 12, 1999
Shell, Rijswijk, The Netherlands

Meeting Minutes

Objective of project:

Objective of the meeting:

References:

• View attendance list.
• Download the slides from Alain Citerne’s presentation. (Alain used the slides from Ted Spalding's Houston presentation.)
• Download slides from Dave Camden's overview of the project

Agenda

Shell’s vision of what this project should ultimately achieve is:

• A POSC registry for names of log curves in years to come
• The data generators submit new names to POSC for registration
• Application developers include lastest version in release
• Oil companies NOT in this loop

Dave presented strawman for a curve type classification.
Dave presented part 1 of his presentation pack (slides 1 – 16).

Recommendation from Alain to solve the long term usuability problem are:

• Reinforce DLIS, especially for data acquisition (tool trade names, unit symbols)
• Provide tools to produce data sets from original, other formats and reduced data sets.
• Have centralised dictionary control at the data producer level
• Organise and classify data to improve clarity and facility filtering
• Improve documentation

Business Issues - Dave Camden

Dave presented part 2 of his presentation pack (slides 17 – 28)

Lunch

Project Infrastructure - Cary Purdy

Cary discussed his strawman of a the project structure as shown on the POSC website.

• Collaborative project
• Project steering group
• One representative per sponsor plus project leaders
• Set major milestones, decide deliverable, finances
• PSG do no technical work
• Meet say every 6 weeks (teleconferences?)
• POSC infrastructure for dynamically support
• Phase 1 get something out of the door quickly. Prove the value.
• More details are on the POSC website.

Comments/Issues

Definition of "raw data" depends on who you are; e.g., oil company vs. service company.

API codes were very good – but there was no method for maintenance. A similar agreement/effort for this project but with provision for long-term maintenance would be a very good accomplishment.

Similarly, people generally recognize the robustness and completeness of Schlumberger’s OSDD, but it is also recognized that the "standard for logs" can’t be developed or maintained by any one service company.

Sharing of information for the project needs to be done through a public accessible web site; e.g., the POSC web site.

How do you classify groups of curves – service vs. tool categorization.

Additional project benefits (from Chris Hamley): increases the ‘plug and play’ percentage of success; would improve data flow between disparate systems.

---

Should the results be available as an ‘early release’ to the project sponsors.

---

Summations

Shell is committed and has approval to contribute $10k US funds.

SAGA believes the project is very worthwhile, but funding is unknown because of the pending merger. The NPD and Diskos have a similar effort and funding may be available through that group.

Jan Rafdal, Statoil, gave an overview of the proposed well data flow with Petrobank.

• Acquistion and QC goes from well site to Petrobank.
• From there, data are available for Operator QC and analysis applications. In other words, project databases could be populated from the Petrobank data source.
• NPD would approve the data sent to Petrobank.
• Partners in the well would also have access to Petrobank so they could retrieve the well data from Petrobank to their project database.

Statoil and Nork Hydro said they support the project from a technical perspective, but could not commit on a commercial basis at this time. If Statoil and Norsk Hydro do decide to sponsor the project, it will most probably be in the form of cash.

Schlumberger strongly supports the project. It was Alain’s guess that they would probably commit in-kind resources to the project. However, he was quick to point out that he didn’t have authority to commit Schlumberger at this time.

PGS supported the initiative. However, they couldn’t comment on their participation in the project. They volunteered that if they did participate in the project, it would be an in-kind contribution. The PDS and MBS databases need the deliverables from the project. This will probably be a strong factor in PGS’ decision to participate.

Baker-Atlas (Z and S) can’t commit at this time but have been an initial, strong supporter of this type of effort. They funded Dave Camden in his early work. Comments received from their user groups indicate that many of them (their users) would fund such an effort. Chris suggested that additional funding for the project could come from the users that have previously commented that they would fund such an effort. He suggested that this user list be made available to POSC so that they could be solicited for sponsorship.

PetroData (who takes care of the Norwegian National Data Set on behalf of the Diskos group, using PetroBank software) commented they are definitely interested in participating in the effort. They believe the project’s deliverables could contribute significantly to Petrobank software. PetroData will solicit the Diskos members for comments and suggestions. They couldn’t commit at this time, but believe they will participate either as a separate company and/or on behalf of the Diskos group.

Action Items

1. All participants agreed to respond via email by December 1, with: whether or not they intend to participate in the project; whether they will participate with cash, in-kind contribution or a combination of the two; whether or not they would serve on the Project Steering Group (PSG).
2. Formal email will be sent out by POSC to potential participants outlining proposed scope of project, project deliverables, and any milestones. It will also be important to outline how many additional phases there will be and what funding is expected/needed for each of the subsequent phases. Should emphasize where funding for maintenance will come from.
3. Cary Purdy and Dave Camden Need to specifically address the intent to handle just raw, acquisition data or if we will include process data.
4. POSC Will update web site to show companies who have committed to the project.
5. Cary Purdy Need to put an electronic version of the contract on the web site with the other documentation.
6. Cary Purdy Need to supply a link to examples of what the final product (project deliverable) might look like. Dave Camden will send example to Cary to post to the web site.
7. Chris Hamley will send list of potential project participants.
8. POSC Set up email discussion group for project.
9. Cary Purdy Correct project deliverables to say that we will develop business rules for how you sort the traces into the various trace classifications.

3:30 Adjourn