GeoFrame 4 Project & Data Management. One-Day Update Course

Transcription

1 GeoFrame 4 Project & Data Management One-Day Update Course

2 Copyright Notice 2001 Schlumberger. All rights reserved. No part of this manual may be reproduced, stored in a retrieval system, or translated in any form or by any means, electronic or mechanical, including photocopying and recording, without the prior written permission of GeoQuest, 5599 San Felipe, Suite 1700, Houston, TX Disclaimer Use of this product is governed by the License Agreement. Schlumberger makes no warranties, express, implied, or statutory, with respect to the product described herein and disclaims without limitation any warranties of merchantability or fitness for a particular purpose. Schlumberger reserves the right to revise the information in this manual at any time without notice. Trademark Information GeoFrame, StratLog WellPix, WellEdit, WellSketch, and CPS- 3 are trademarks of Schlumberger. All other products and product names are trademarks or registered trademarks of their respective companies or organizations. 2

3 AGENDA Morning Introduction A. Project Upgrade Strategies B. Project Management Changes Project Types and Data Sharing Exercise One Match and Merge Exercise Two Backup and Recover Log Curve Preference System Exercise Three Multi-User Server Options Rebuild Indexes Lunch Afternoon C. Project Data Management Changes/Additions Completed Intervals Data Manager Drillstem Tests Data Manager Exercise Four Horizon Patches Data Manager Interpretation Data Manager Exercise Five Interpretation Models Data Manager Exercise Six D. Loaders and Unloaders 3

4 Introduction This course is for users of GeoFrame 3.X and is intended to present new features and functionality in GeoFrame 4. Private data stores for CPS3, StratLog, IESX and Charisma have been reconciled in GeoFrame 4 into one common data store. Oracle tables now contain all Seismic interpretation headers (pointers) from both Charisma, IESX and Cross Section headers from Cross Section (the former StratLog) while the bulk data still remains in the assigned project disk storage locations (DSL s). New data types have been expanded, and GeoFrame 4 will accept a wider variety of seismic including 4-D & 4-C seismic, variance cubes and borehole images. GF4 supports technologies like stereo, wide-screen and all-round displays and can support 64 bit operating systems to better handle larger data sets. GeoFrame 4 remains an open software platform for 3rd party applications with open access layers for OpenSpirit, developer kit applications, Geoshare and Corporate databases such as Finder, Enterprise, GeoWeb, and in-house database systems. Although OpenSpirit is not yet commercial, GeoFrame 4 will integrate with standalone OpenSpirit enabled applications. 4

5 Presentation Topics A. Project Upgrade Strategies B. Project Management Changes 1. Project Types and Data Sharing 2. Match and Merge 3. Backup and Recover 4. Edit Project Parameters a. Log Curve Preference System b. Multi-User Server Options c. Rebuild Indexes C. Project Data Management Changes/Additions D. Loaders and UnLoaders Course Skills Development 5. Completed Intervals 6. Drillstem Tests 7. Horizon Patches 8. Interpretation Data 9. Interpretation Models Upon completion of this one-day course, you will learn new features and uses of GeoFrame 4 through a series of exercises, instructor led demonstrations, and PowerPoint presentations. In Project Upgrade Strategies, we will suggest methodologies to use when upgrading to GeoFrame 4. In Project Management Changes there will be presentations and exercises on the new project restructuring to show you what new project types exist and how to utilize new features such as Match and Merge customization, Backup, Recover, Rebuild Indexes and sharing well data. In Project Data Management Changes/Additions we will learn about new data types incorporated into the database and learn about five new Project Data Managers. We will explain a new interpretation management system called Model Centric Interpretation and you will have an opportunity to build an Interpretation Model and populate it with horizon and fault data. 5

6 Project Upgrade Strategies Upgrade Strategies In this topic, we will look at Best Practice strategies for upgrading your current GeoFrame Project, Operating System and Oracle database to GeoFrame 4. Upgrading projects from GeoFrame 3.8 to GeoFrame 4 can be performed directly or in-place. Upgrading from GeoFrame projects will require a Project Backup and Restore to GeoFrame 4. If you are working on pre-geoframe 3.5 projects, you will need to perform an iterative project upgrade to GeoFrame 3.5, then backup and restore to GeoFrame 4. GeoFrame 4 requires the Sun operating system to be Solaris 8.0 and the SGI operating system to be IRIX and Oracle

7 Project Management Changes Project Types and Data Sharing Project Types There are three types of projects in GeoFrame 4: Standalone projects Shared projects Sub-projects Standalone projects are the traditional multi-user GeoFrame projects. New to GeoFrame 4 are Shared projects, which are read-only well data master projects and Sub-projects, which are user projects that are associated with a Shared project. Users must have privileges to create a Sub project. Before you can create a Charisma or IESX Sub-project, a Shared project has to be created first because of the association between a Sub and Shared project. A Sub-project (Charisma or IESX) can only be associated with one Shared project. This is a database architecture constraint. Data Sharing The purpose of the Shared project is to allow sharing of well data between multiple Sub-projects and a Shared project. You no longer have to load or data copy well data into each user project. Well sharing allows you to create limited subsets of well data from a larger Shared project by using an Area of Interest in the Sub-project to determine your well selection. An IESX Sub-project can share seismic data with multiple seismic master projects, however, a Charisma Sub-project can only share seismic with one seismic master project. Sharing is a one-way, one-time event. There is no way to un-share. When performing a Data load or Data copy to a Shared project filtering of un-shareable data items will occur. Once data is 7

8 shared it becomes un-editable. Not all data Types are sharable. Sharable data types include: Field, Well Borehole, Well deviation survey, azimuth reference, well check shot survey, well stratigraphic processing, well marker, array (log curves that are not stored under a collection), activity, position, elevation reference, coordinate system, tool run, service run, axis index, bulk, parameter, and data file. Not sharable data includes: composite, cross-sections, correlations, grids, zones, logs stored under collections, for example borehole dip and image data. Storage Settings Data storage for Standalone projects is the same as previous GeoFrame baselines. Sharable bulk data goes to the Shared DSL (Disk Storage Location). Data Storage in a Sub-project must include a shared DSL, otherwise there are no restrictions in DSL selection for other storage types such as CPS, Default, Interpretation, and so forth. Project Users The owner of the Shared project (or Database Administrator) can restrict user Login to the Shared project. There are two access lists shown below. The first list (left) will grant users direct access to the Shared project, authorization to create sub projects and data promotion from the sub-project to the Shared project. The second list (right) determines who can share data from the Shared project. Users in the Shared project automatically become pseudo-users in other Sub-projects connected to the Shared project. 8

9 Exercise One Create a Sub-project and Change the Well Area of Interest In this exercise, you will create a sub-project (Charisma & IESX), add users to your sub-project, and change the Well Area of Interest (AOI) of the shared well data in your sub-project. Open Project Manager - Create Sub projects. 1) After the Project Manager opens, click MB1 on the Project Management tab. It is not necessary to connect to the Shared project first. 2) Click MB1 on the blue Create a new project button. The Create a New Project dialog is displayed. 3) Type in the new project name and password. Use the Default Tablespaces. 4) Select the Sub Project option. It should be red. Click OK. 5) The Select Shared project dialog is displayed. Select a Shared project and click OK. The Confirm dialog is displayed. Click OK to proceed. It will take a few minutes for the Oracle Synonyms and Views to be set up. 6) The Storage Settings dialog is displayed. Use the DBA assigned disks; click OK to accept the storage settings. 7) You will be prompted to whether you are setting up a Charisma project. Make sure YES is selected on the Charisma dialog, and choose the Seismic Sub Project as the Charisma Project Type. Click OK. 8) You are prompted for the Seismic share project. Select the correct one (ask instructor) and click OK. The Charisma extensions for Oracle are then created and the project is ready for use. 9) The Edit Project Parameters dialog is displayed. Since this is a Sub Project, it will automatically pick up the Unit/Coordinate System from the Shared project you selected in step 5. Click OK. The sub projects are created. Add Users 10) In the Project Manager > Project Management click the Add/Remove Users button and choose two users to add to your project. Make the password the same as the project. Click OK. Set Area of Interest for the shared wells 11) In the Project Manager > Project Management area, select the Edit button. In the Well Area of Interest window, click the Compute Well Region button. 12) Open a GeoFrame basemap. After the basemap opens, make a supplemental readout window with XY coordinates. (User > Readouts). Using the XY readout, write down the XY coordinates for two diagonal corners in the basemap over the southern third of the posted wells in the basemap. You can zoom out (View > Zoom/Unzoom) to make this easier. If you 9

10 include surface locations of any deviated boreholes in the new AOI then those boreholes will be included in the new AOI even though the bottom hole locations may fall outside of the new AOI. 13) Click Project Manager > Project Management > Edit, and input the new AOI corners. Click on the XY tab and enter the corner coordinates you wrote down. Click OK. 14) Close the current basemap. Open a new basemap and observe the results. Share Seismic for the IESX sub project 1. Open the IESX Session Manager (Application Manager > Seismic > IESX) 2. Open the IESX Data Manager (Session Manager > Applications > Data Manager > Share). Select the project with the IESX seismic volume and share the 3d volume. (Ask instructor for what data to use) End of Exercise 1 10

11 Match and Merge Match rules define what data attribute must be identical to identify data being loaded and data already loaded in the project, as being duplicates. Merge rules are instructions on what to do with any duplicate or new data being loaded. Match and Merge rules in GeoFrame 4 have been removed from individual loading applications. You now have the ability of customizing the Match and Merge rules. Match rules are now defined at the System level, which means that changes made will affect all users. Match rules are set when the project is created. Your GeoFrame DBA (Database Administrator) can set Match rules. Merge rules are defined at the project level and can be changed anytime you load data. The default Match and Merge rules should behave similarly to previous releases. In GeoFrame 4 the data being loaded is stored in a staged area prior to merge. NOTE: An issue exists should you abort the load. If the load is aborted, then data can be left unmerged and will require clean up using the Quality Control Tool and General Tests to clean the staged area. See the procedure below for more details. Aborted Data Load Procedure 1. Open Quality Control Tool from the General Data Manager 2. Open the General tests folder and select Staged data test. Click Start. 3. In the resulting Report Panel, select the Auto-repair option. This will remove the incomplete data created by the Merge Run from the project, clearing the staged area. 11

12 Match Match rules define what data attribute must be identical to identify data being loaded (and data already loaded) in the project as being duplicates. Match rules are defined at the System level and affect all users. To set the Match rules you will need DBA access to the GeoFrame 4 catalog. Set Match Rules Procedure 1. From within Project Manager > Project Management, change to DBA mode. 2. Switch to the Login tab and connect to a catalog account. 3. Click the Project Management tab, and click on the Match Rule Editor button. This will open the Match Rule System Editor. Merge Merge rules are instructions on what to do with any duplicate or new data being loaded. From the Application Manager > Data > Tools > Merge Preference Setting Tool or from the Project Manager > Project Management > Merge you can open the Merge Rule Template Editor to set Merge Operation options. These options will let you set actions to skip, update, replace or delete incoming data with Match rules, or set actions to insert or ignore incoming data without Match rules. 12

13 Skip Update Replace Delete No changes for matched data items Change attributes of matched data items unless specific exception is set as Skip Replace existing matched data items unless specific exception is set as Skip Delete existing matched data items Merge Operation Options Actions with regard to existing and incoming data with a Match: Actions with regard to incoming data without a Match: Insert Ignore Add data items without Match Skip data without Match and its children 13

14 Exercise Two - Match and Merge Example Workflows We will look at two examples of how to modify Merge Rules. You will protect Well Names from being replaced by the borehole UWI. You will protect well position data from being updated from a LAS load in your project. You will see a demonstration of how to change Match rules. You will create new markers in your project and promote them to the Shared project using the default Match and Merge rules. DLIS Load Well Name Protection Loading a DLIS file can result in the Well Name being replaced with the Borehole UWI. 1. To prevent this from occurring open the Merge Template Editor (Project Manager > Project Management > Merge button > Template Editor button) 2. Use File > Save As and save a copy of the Default Merge Rule Template as User_DLIS_Well_Name_Skip. 3. In the Exceptions window (The following images show the exceptions to the default merge rule) set the following; 4. After you click the Edit button, toggle on skip for Well Name. Click OK. 5. Save the modified template (File > Save) and use it for all loading of DLIS files. 14

15 Position Value Protection Currently when loading LAS files using the default merge rule you will have to check each file to verify position data because the default merge rule template does not have an exception for position, so all position data would be updated. To avoid this condition, open the Template Editor and use File > Save As to save a copy of the Default Merge rule template as: User_Skip_LAS_Position. In the Template Editor, click on the Add Data Type button. This will open a list of data items. In the list, select Position by highlighting it and click OK. This will add Position to the Exceptions window. Change to the following: Save the new template with File > Save. 15

16 Instructor Demo Match Rule Change of Multiple Markers Modification Remember that when you change Match Rules you will affect all users in all projects in the GeoFrame baseline, because this requires a connection to the GeoFrame 4 catalog account you will need DBA access. The System Well Marker Match Rule will identify multiple markers with the same name and same value as duplicates, and the duplicates will be merged into one marker. Markers with the same name but with different values will not be merged into one marker but will be added as separate markers with the same name per borehole. Create Markers and promote them to the Shared project. To demonstrate the default Match and Merge Rules all participates will use the same Shared borehole. 1. In your Sub-project open the Application Manager > Markers Manager. 2. Select the borehole. 3. In the top row of the spreadsheet add a row. Create a new marker and call it MATCH, give it a measured depth that is not the same as your neighbor s depth. Click Apply. 4. In the top row, add another. Create a new marker and call it MATCH2, give it a measured depth that is the same as your neighbor. Click Apply. 5. Open the General Data Manager. Run a Query for your project; Find all Well Marker with Attribute Name = MATCH*. 6. In the Markers Manager highlight Match and click the activated Share button (lower right corner). What happens to the marker in General Data Manager after you re-run the above query? In the Marker Manager? Once you promote your marker to the Shared project it becomes read-only. It can only be deleted or edited in the Shared project. 16

17 Backup and Recover Backup and Recover contain a user interface in the Project Manager > Project Management window. These features are used for quick and light nightly backups as well as for disaster and user error recovery. Backup requires that the data be restored to a project that contains the same version and same site. Backup and Recover use the RP66 format, which is a description on how to save data. Backup will wrap the bulk data and Oracle export files in a RP66 container to allow for spanning multiple tapes on a large backup. Edit Project Parameters Two additional project parameters have been added to Project Management > Edit. Log Curve Preference System Multi-User Server Options Log Curve Preference System (LCPS) The LCPS is a group of log curve specifications that you can create and modify, which can be used to set precedence when working with applications that use lgp templates. You can choose to use - or not to use - the LCPS. The default is set to not use the LCPS; therefore, log curve query behavior is the same as previous versions of GeoFrame. If you elect to use the LCPS and if a log curve is absent then the LCPS will select the next curve in the precedence you set. If a curve does not post in the track then be sure to check the log curve unit values and/or confirm that there is a curve in the database for the substitution. To use the LCPS, first open the LCPS preference window from the Project Manager > Project Management > Edit; second click on the Log Curve Preference system button; Third toggle on Yes and select a LCPS system. If you use the LCPS, then log curve queries will first look for log curves using the specified search criteria. 17

18 The LCPS is created in the LCPS Editor (Application Manager > Data > Tools > Log Curve Preference System Editor.) Multi-User Server Options The multi user server (commonly called the super server) is used to maintain data consistency among several applications sharing the same project. The server is started by the first application that connects to the project. You can run on a remote host just type in the paths to the host and the startup script. If you select to run persistently, the server would not be shut down when its last client exits, so the next application you open will not need a new instance of the server. 18

19 Rebuild Indexes For all types of projects that have been used for a relatively long time or have experienced data changes, use the Rebuild Indexes option to improve data access performance. Rebuild Indexes is launched from the Project Manager > Project Management window. 19

20 Exercise Four - Log Curve Preference System (LCPS) 1. Open WellComposite Plus (Application Manager > Geology > WellComposite Plus). 2. Set Data Focus and Presentation File as shown above. 3. Click Run. Leave presentation open. 4. Launch the LCPS from the Application Manager > Data > Tools > Log Curve Preference System Editor. 5. Toggle on Create New. 6. Click in the row, first cell and remove NEW_0 using the delete key on your keyboard, then type Resistivity. 7. Tab over and type ILD under the Select column. 8. Tab over and type ILM, RT under the Or Select columns. 9. Click the i icon for a description of the log curve preference. 20

21 10. Toggle on (Yes) the LCPS that you saved. (Project Manager > Project Management > Edit > Log Curve Preference System.) 11. Re-run WellCompositePlus with a new Run over the same borehole and lgp template. 12. Compare the two presentations. What is the result? 13. Have the instructor remove the ILD curve from the borehole you are using in the Shared Master then re-run WellCompositePlus keeping the LCPS ON. What is the result? 21

22 Data Management Changes Five new Project Data Managers have been added to GeoFrame 4. They are: Completed Intervals Drillstem Tests Horizon Patches Interpretation Data Interpretation Models Data Managers Graphical displays of the Deviation Survey and Checkshot Survey for a borehole can be seen in the Borehole Editor as a quick quality control check. The Borehole Editor can be launched by double-clicking on a posted borehole, in either Basemap or in Seis%DV. The steps to use this functionality are outlined below. Project Completed Intervals Data Manager Production data can now be input in the database. This data can be loaded from the General ASCII loader or input manually in the Project Completed Interval Data Manager spreadsheet. The graphic below shows all available attributes that can be input. Production data can be displayed on the Basemap as bubble plots. 22

23 23

24 Exercise Completed Interval Here you have the opportunity to load some production data and post the data on basemap. Load production data 1. Open the Layer Data Manager (Application Manager > Data > Data Managers > Layers) and create layers for the production data you are going to load. If you are using the Gullfaks dataset then create the Bunnkritt and Etive layers. For the Bunnkritt set the Top Surface as Bunnkritt and Bottom Surface as Etive. For the Etive layer use Etive and Drake as the Top and Bottom Surface respectively. 2. In your project open the Application Manager > Data > Loaders and Unloaders > ASCII Load. 3. Select the input file(s). Ask instructor for path to the data files. 4. Click the Control file; name the file: completed_intervals.ctl. 5. Select completed Interval Data and click the Create Control file button. 6. Set the Start Row and toggle off the Column Delimiter selection. Toggle on MultiBorehole UWI and set Position and Length. 7. Add the following Attributes; Bottom Depth, Cumulative_Gas_Volume, Cumulative_Oil_Volume, Cumulative_Water_Volume, LayerName, Name Top_Depth. 8. Set the row and column counts. Click OK. Ask for help if you need it. 9. Set the Target Field, Click OK. 10. Run the load. Completed Interval Data Manager 1. From the Application Manager open the Completed Interval Data Manager. 24

25 2. Click the Intervals button and select All. 3. Click OK. This will give you an overview of the data you loaded. Basemap 1. Open Basemap (Application Manager > Visualization > Basemap). 2. Post boreholes (Post > Boreholes Sets) 3. Post production (Post > Production Data) 4. Change the Post Data Type to Completed Interval Production. 5. Select a Layer and click and drag the Cumulative Oil volume into Property Click and drag the Cumulative Gas volume into Property Click OK. Composite (Geology Office Suite) 1. In Basemap select Send > Borehole and click MB1 on one of the boreholes with posted production to select the borehole. Once selected click MB3 > Composite. This will send the borehole as context to Geology Office so we can create a production track in Composite. 25

26 2. Click the star icon (as shown above) and enter a name for the composite. 3. When Composite opens, again click on the star icon to open the Track Create window (below). 4. In the Track Create window, set the Track Type to Production Data and click Apply. 5. After the track has been added, Double-click MB1 in the production track to open the editor window. Set the display parameters and click OK. 26

27 27

28 Project Drillstem Test Data Manager Drillstem test data can be loaded from the General ASCII loader or input manually in the Project Drillstem Test Data Manager spreadsheet. The graphic below is a list of Attributes that can be entered into the database. 28

29 Project Horizon Patches Data Manager Horizon Patch is a new feature, which allows you to store individual parts of the same horizon, called horizon patches, in an Interpretation Model under a single horizon name. The Project Horizon Patch Data Manager assists you in filtering horizon patches that may be present in your project and provides editing tools for other data associated with Interpretation models. To facilitate data selection, you can filter horizon patches by choosing a specific Interpretation Model, Horizons, and Patches. Horizons contain horizon patches, while Interpretation Models contain horizons and horizon patches. The Reorder button lets you change the sequence of the horizon patches. You have flexibility to order the patches based on their logical geological sequence in the strata rather than being limited to the order in which you originally picked them. Order is important when viewing maps in overlapping horizon patch areas. 29

30 30

31 Project Interpretation Data Manager (IDM) Use the Interpretation Data Manager to conveniently view lists of surface interpretation in your project. You can filter interpretation by Type, Containment, or by customizing the selection parameters. The list of interpretation is updated dynamically to reflect changes in the database. Additionally, you can use the IDM as a stand-alone browser of surface data, promote data to other projects, delete data from the database, and create HTML reports of data in the project. Charisma users can take advantage of drag & drop functionality to select data from the IDM spreadsheet, and using MB2 to drag & drop the selected surface into the Charisma basemap. 31

32 Project Interpretation Model Manager (IMM) and Model Centric Interpretation The Interpretation Model Manager is the primary window interface to set up Model Centric Interpretation. The Model Centric concept allows multiple users to work in an IESX project concurrently. Each user can create an interpretation model within a project. An Interpretation Model is a collection of horizon grids, 2D line interpretation, fault cuts, contact points, and fault boundaries. Horizon interpretation data, such as Grids and 2D line data, is contained in Horizon Versions. Fault interpretation data, including fault segments, contact sets, and fault boundaries is contained in Fault Cut Sets. Interpretation model data can be Shared or Cloned. Shared data is made available to other users in other models in the same project. Cloned data is private to a specific model and is not seen by other users in the project. Cloned data can be made sharable later, and can be promoted to other projects. IMM can be launched from the IESX Session Manager or from the Application Manager (Application Manager > Data > Data Management Catalog.) 32

33 Borehole Editor Steps to use quick quality control of deviation and checkshot surverys. Once you open the Borehole Editor you can access the Deviation or Checkshot data windows by clicking on the blue Deviations or Checkshots buttons as shown below. Select the deviation or checkshot survey you want to look at then click the blue i icon to open the survey editor windows displayed below. Access data windows 33

34 To quality check the surveys graphically, click the graphic output icon. You can zoom using <Shift> + MB1 and drag, or select data with <Ctrl> + MB1. 34

35 Exercise Six - Project Data Management In this exercise you will populate your empty sub-project (Charisma & IESX), create an interpretation model with horizon and fault data, assign the horizon and fault to be sharable or cloned, modify a horizon by adding a patch and generate an html report of interpretation data in your model. Populate your empty sub-project using IMM 1. Ask your instructor for a master project and log into it from the Project Manager. 2. Connect to the master project and Launch the Application Manager > Data > Data Managers > Interpretation Models Manager. 3. In the IMM, select the Default model. 4. Click the Create button and type a new model name in the window. Click OK. 5. Click the blue Populate button and in the Populate Model window that opens click the black arrow and highlight the Default model. 6. Under the Filter box, toggle on Apply Horizon Filter and click the small icon. Select three horizons. Toggle on Apply Fault Filter and click the small icon, select three faults. Click OK. 7. Click on the Export button and export the selected model to your sub-project. The interpretation will be put into your project Default model. 8. When export is complete, exit from the IMM and Application Manager. 9. You can now launch either your Charisma or IESX Sub project. Select the new Interpretation Model and begin using the horizon and fault data. Change Horizon Version Assignment. 1. Open the IMM (Application Manager > Data > Data Manager > Interpretation Model Manager) 2. Select a model. And toggle on the Horizon Tab. 3. Highlight one of the horizons you want to change an assignment for, and click the Assign button. 4. In the pop-up window click OK. In the Confirm Model Assignment window choose either; Assign the selected Horizon Version to the model Clone the selected Horizon Version, and assign the copy to the model. 35

36 5. When finished making a selection click OK. The selected horizon assignment is changed. Modify a horizon by adding a patch You can create a horizon patch in the Project Horizon Patches Data Manager. 1. Open the Project Horizon Patch Data Manager (Application Manager > Data > Data Managers > Horizon Patches.) 2. In the Horizon Patch Data Manager, click on the blue Interpretation Model button and select the model that you created. You should have some horizons posted in the spreadsheet under the Horizon Patch Information window. 3. In the Horizon Patch Information window, highlight a horizon and click the blue Add button under New Horizon Patches. Add a new row below the current row. Click OK. 4. In the new row under Name, type the number 2 in the blank cell. 5. In the new row, double-click the gray cell under Horizon Name, or highlight the row and click the Target Horizon button. In the selection window that opens, select the horizon you have chosen to add the patch. Click OK. 6. Now click Apply to create the patch. Use the Drag and Drop Selection with Interpretation Data Manager and your Charisma sub project Launch Imain. (Application Manger > Seismic > Charisma Interpretation > Imain). When the Imain Preference Editor opens, select your new Interpretation Time Model. Open the Interpretation Data Manager. (Application Manager > Data > Data Managers > Interpretation Data Manager). Be sure to open the IDM in the same window as the Charisma Grids Map. In the IDM, select a grid with MB1 and hold down MB2, dragging the cursor over the Imain Grid map. Release MB2 to drop and display. Try selecting IESX, CPS3 and Imain sources to display. Generate an html report of interpretation data in your model. 1. Open the Project Interpretation Data Manager (Application Manager > Data > Project Managers > Interpretation Data Manager.) 2. In the IDM window, toggle on Filters. 3. Toggle on Type = Grid 4. Toggle on Containment = Interpretation Model. Click on the black arrow in the containment row and select your Interpretation Model. 36

37 5. Click the Configure table icon to open the Table Configuration window. 6. Select several available columns and use the up/down arrows to rearrange the order of Visible Columns. When finished click OK. 7. To make the report, first select a grid. 8. Second, click the Generate HTML icon. End of exercise 3 37

38 Loaders and Un-loaders Several new data types that can be loaded into the database have been added to the Generic ASCII Loader. These include zone interval and production data, such as drill stem tests, pressures, cumulative oil and gas, and initial potential rates. You can select a Merge Rule Template before a data load. A Quality Control interface has been added to check the consistency of the loaded data with the database hierarchy. The well loader in the IESX > Session Manager > Data Manager has been retired. An IESX well loading control file has been added to the GAL as a replacement. Click on black arrow across from the Control File button. 38