Topic:
10px Well Data Loading and Storage, what files hold what data items?
Description:
Solution:
Note: Loaded into IES - means loading took place in the IES Data Management option. Loaded into IESX - means loading took place in the DataManager/Wells option. Well Locations If loaded into IES or IESX they are stored in both data bases. In IES they are stored in the line_info*, maploc* and *.wel files. In IESX they are stored in the db_wellrep_key.* files. Logs Can only be loaded in IES, but entries are made in both data bases. All log data (log headers and log samples) are stored in the *.wel files in IES (one file/well). Entries are also made in the IESX data base in the db_logrep_key.* files (one file for all wells) but only the log headers are stored here. IESX can access the log data samples (bulk data) in the *.wel files. Markers (formation tops) If loaded into IES (tops) they are stored in the formation.tops file for all wells, IESX never sees this information unless you import the IES data through DataManager. If loaded into IESX (markers) they are stored in the db_intersect_key.* files, IES never sees this information unless you export it there through DataManager. Deviation surveys (paths) If loaded into IES or IESX they are stored in both data bases. In IES they are stored in the maploc* files, in IESX they are stored in the db_welldev_key.* files. If loaded into IES the path overwrites the current one in IES, but will not overwrite a path that preexists in the IESX data base. If loaded into IESX both data bases are always updated. DVT relationships (velocity surveys) DVTs cannot be loaded directly into IES. If a well path is input in time and depth in LPView then a DVT relationship will be created in the IESX data base for that well, but only if a DVT relationship for the given well does not already exist in IESX. If a DVT is loaded into IESX it is stored in the db_welldvt_key.* file in the IESX data base. The IES data base never sees this information.
Last Modified on: 06-OCT-98