9.3.1.1.1 Preparing for Data Exchange

When working in the context of an asset team and the full life cycle of an earth model, and before beginning to exchange data in the workflow, we must give some thought to how to organize data for iterative exchanges throughout the life cycle. This organization is important so that in the future, we can retrieve the hypothesis used during the successive modeling steps.

The first recommended action is to create an earth model feature in Software A: an organization feature of kind earth model with the title: MY_EARTHMODEL_Feature (UUID_EMF, Citation_EMF) ( Figure 9.1.3-1 , Figure 9.1.3-1 ). This example does not yet use the earth model feature (because we have not yet created any earth model interpretations). However, in support of long-term organization for full life cycle and iterative workflows, the earth model was created first.

Then, because the team has created features, each with a UUID (for this example: HORIZON_1_UUID, HORIZON_2_UUID, FAULT_1_UUID), the team can attach one or more corresponding interpretations to each feature, using a data object reference to indicate the UUID of the feature that is being interpreted. (For more information, about features and interpretations see 5 Knowledge Hierarchy : Features, Interpretations, Representations , and Properties .)

This reference mechanism allows enrichment of the model, step by step. For example, because of this referencing ability, at a given time stamp, we can export Peter's interpretations. In a few weeks, after more work has been done, Paul's interpretation can also be exported and are associated with the same features by UUID.

So we have a prospect with three individual features: (Horizon_1, Horizon_2 and Fault_1). Each of these features has two interpretations (one by Peter and one by Paul), and for each interpretation, we can attach one or more representations. The representations that can be exported from Software A are:

• For each horizon interpretation, one 2D grid based on a point lattice of 2 dimensions (4 2D grids, all together with only one point lattice 2D).
• For each fault Interpretation, one polyline sets.