NRIS DATA MANUAL 08/01/91

Transcription

1 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/91 08/01/ Data Element: Additional Information Record Aliases: ADDINFO When an operator files more than one completion report for a given well, the additional form(s) is reviewed to determine if significant new information is included on the new form. If so, it is added to the well file as a separate ADDINFO record. (Minor changes are updated to the original well record for records which are from the same source, i.e., OCC 1002A forms or Osage Tribal Council forms.) The text in the ADDINFO data element describes the basis for the additional submission. Record Type Well GIPSY Columns Written on the form during prescan, with the value text reflecting the reason that this additional form was filed by the operator. Any record with this data element has the same API number as the original (XREF) record for that well, or has the logical flag NOORIG coded. The original record for the well is updated with the XREF flag when an ADDINFO record is identified. Deepening Recompletion Workover Conversion Amended Reentry Plugback Osage Well deepened to a new producing zone Well recompleted Well worked over Well converted to injection or salt water disposal Well record amended (with significant changes) Well reentered Well plugged back to a different producing zone Osage Tribal Council Completion Report record with a corresponding 1002A on file

2 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/91 08/01/ Data Element: Additional Information Record (continued) Aliases: ADDINFO All values must be one of the valid values listed above. If ADDINFO is coded on a record, APINUM must be present, or the NOORIG logical flag must be present. For every ADDINFO record on file that does not have a NOORIG flag, one (and only one) XREF record with the same APINUM must also be on file. ADDINFO: RECOMPLETION This data element was developed to replace the logical flag WRKOVR for all newer areas of well file coverage; gradually, efforts will be completed to go back through those areas completed first, and convert all WRKOVR records to ADDINFO records. This data element is maintained on the GIPSY version of the well file only. The data values are consolidated with other data elements (XREF, WRKOVR) to form the Submission Type (SUBMTYP) data element on the WHFF file. With the addition of Osage Tribal Council Completion Reports, a new value ( Osage ) was added to the list of valid codes. This value is used when the Osage form is comparable to a 1002A form already on file. All Osage forms are added to the file regardless of how closely they may match a 1002A form. See data elements: XREF, NOORIG, APINUM, SUBMTYP.

3 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/ Data Element: API State Code Aliases: STATECO API State Code. Well A Computer-generated as a constant on all WHFF records. 35 Oklahoma API State Code Added to facilitate merging Oklahoma records with data from other states.

4 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/91 08/01/ Data Element: API Well Number Aliases: APINUM Well number assigned by the Oklahoma Corporation Commission according to standards set by the American Petroleum Institute. When more than one Well History record exists for a well (e.g., an original and a workover record), the API numbers on those records should be identical. Well A/GIPSY Eight-digit numeric (see exception below); no space or dash. The first three digits should equal the county code; STATE CODE is marked out, if given. A report of all API numbers on the Well History Subsystem is generated after each update cycle. The API numbers on new records are compared to those on this listing before adding them to the file. This keeps well record duplication to a minimum and helps identify workover or amended forms. First three digits must match COCODE. Must be eight-digit numeric, or first two bytes ZZ and six-digit numeric. A special program compares well records for identical API numbers, to verify that cross-reference information is accurate on the records. When duplicate API numbers are on file, the ADDINFO data element should be on all but the original form; the original form should be flagged with the XREF data element.

5 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/91 08/01/ Data Element: API Well Number (continued) Aliases: APINUM APINUM: is well number in county 063 Dummy API well numbers are assigned to interrelated forms when no real API number is available for the well. The dummy API number consists of ZZ and the six-digit unique ID (e.g., ZZ012345) of either the original (XREF) form for the well or the earliest ADDINFO record available. This data element is not requested on any of the Osage formats. It will be keyed if reported. When a relationship is determined between a 1002A and Osage form and the 1002A has an API number, it will be added to the Osage record. See data elements: XREF, ADDINFO.

6 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/ Data Element: Amount of Location Fee Paid Aliases: LFEEAMT The amount of money, in dollars, paid by an entity to lease the land around the well site. Well M/GIPSY The value is coded and keyed as a number with a decimal and two decimal places. LFEEAMT: This data element is only requested on the Osage Tribal Council Completion Report records. See data elements: LESSEE, LFEETO, LFEEDTE.

7 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/ Data Element: Amount of Water With Oil Aliases: WTROL01-30 The amount of water, represented as a percentage included with oil production. Well D/GIPSY The value is reported as a percent indicating a percentage of water droplets suspended in a volume of crude oil, each droplet encased in a film of oil. If any amount of water (BBLS etc.) is given, code as WBBLD. This data element (WTROL) reflects after treatment information. The data element occurrence number (01-30) must match the occurrence number of the PFNAM data element to which it refers. WTROL01: 80 This data element is only requested on the Osage Tribal Council Completion Report records. See data elements: WBBLD, FRAC, ACID, PFNAM, BWTROL.

8 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/ Data Element: Amount of Water With Oil Before Treatment Aliases: BWTROL1-2 The amount of water, represented as a percentage included with oil production before any acid or fracture treatment was applied. Well K/GIPSY The value is reported as a percent indicating a percentage of water droplets suspended in a volume of crude oil, each droplet encased in a film of oil. If any amount of water (BBLS etc.) is given, code as BWBBLD. This data element (BWTROL) reflects before treatment information. The data element occurrence number (1-2 on GIPSY file, on the WHFF) must match the occurrence number (01-02) of the PFNAM data element to which it refers. BWTROL1: 75 Before Treatment initial production test data elements are only requested on the Osage Tribal Council Completion Report records. See data elements: BWBBLD, WTROL, PFNAM.

9 NRIS INFORMATION SYSTEM Page: DATA MANUAL 08/01/91 08/01/ Data Element: Bottom-Hole-Plugs-Used Flag Aliases: BHPLUG Logical flag indicating that information was reported on the form regarding bottom hole plugs that were used, and/or other plugging information for the well. Well B/GIPSY 155 This logical flag is coded when an operator reports that bottom hole plugs were used, or reports other plugging information for the well. BHPLUG: Y Older 1002A formats explicitly asked for information regarding bottom hole plugs, but this question was dropped as of the A format. Bottom hole and other types of plugging information is sometimes volunteered by the operator on the 1002A forms, and so this flag was developed to alert the user about this information. The paper copy of the 1002A form must be consulted for more detailed information about the bottom hole plugs, or other plugging details that were volunteered by the operator. Two new data elements (PLGDEP and PLGTYP) were added to accommodate the A format which requests information on where plugs were set and what type. On the Osage 02 and 03 formats, plugging information was requested for dry holes and abandoned wells. The data element PLUGRMK was added to accommodate this information. BHPLUG will be added to other Osage formats when appropriate. See Appendix A for a copy of all format types. See data elements: PLGDEP, PLGTYP, PLUGRMK.

10 NRIS INFORMATION SYSTEM Page: DATA MANUAL 10/15/91 08/01/ Data Element: Casing Pressure Aliases: CPRES01-30 The casing pressure in PSI reported during the initial production test. This data element can occur up to 30 times per Well History record. Well D/GIPSY Data are recorded as a numeric value in units PSI. When the operator reports the pressure as FLOWING CASING PRESSURE (FCP), data are recorded under the FPRES data element. When the pressure is reported as SHUT IN CASING PRESSURE (SICP), the data are recorded under the ISIP data element. The data element occurrence number (01-30) must match the occurrence number of the PFNAM data element to which it refers. CPRES01: 320 This data element is not specifically requested on any Osage formats. See data structure (Section 3.4) for WHFF Record Type D for additional information. See data elements: ISIP, FPRES, BCPRES.

11 NRIS INFORMATION SYSTEM Page: DATA MANUAL 08/01/ Data Element: Casing Pressure Before Treatment Aliases: BCPRES1-2 The casing pressure in PSI reported during the initial production test before any acid or fracture treatment was applied. This data element can occur up to two times per Well History record. Well K/GIPSY Data are recorded as a numeric value in units PSI. When the operator reports the pressure as FLOWING CASING PRESSURE (FCP), data are recorded under the BFPRES data element. When the pressure is reported as SHUT IN CASING PRESSURE (SICP), the data are recorded under the BISIP data element. The data element occurrence number (1-2 on GIPSY file, on the WHFF) must match the occurrence number (01-02) of the PFNAM data element to which it refers. BCPRES1: 320 Before Treatment initial production test data elements are only requested on the Osage Tribal Council Completion Report records. However, this data element is not specifically requested on any Osage formats. See data structure (Section 3.4) for WHFF Record Type K for additional information. See data elements: BISIP, BFPRES, CPRES.

12 NRIS INFORMATION SYSTEM Page: DATA MANUAL 10/15/91 08/01/ Data Element: Casing Test PSI Aliases: CSGTST1-9 The pressure, in PSI, reported during a casing-burst-strength test for a section of casing. This data element can occur up to nine times per Well History record. Well F/GIPSY Data are coded as numeric values in units PSI. Commas, pound signs (#) and units are not included. The data element occurrence number (1-9) must match the occurrence number of the CASSIZ data element to which it refers. CSGTST1: 1000 CSGTST2: 3500 This data element is only specifically requested on the 1970, 1979, and A formats but is sometimes volunteered on earlier 1002A formats and Osage formats. See data structure (Section 3.4) for WHFF Record Type F for additional information.

13 NRIS INFORMATION SYSTEM Page: DATA MANUAL 10/15/91 08/01/ Data Element: Casing-Pulled Length Aliases: CASPLL1-9 The length, in feet, of a section of casing pulled from the well. This data element can occur up to nine times per Well History record. Well F/GIPSY Data are coded as numeric values. On the 1910 format, the reported value is commonly the value for the amount of casing left in the hole. In such cases, the reported value is subtracted from the value that was reported under CASFT to arrive at a value for CASPLL. The Osage formats request the amount of casing left in the hole. The reported value is subtracted from the value reported under CASFT to arrive at a value for CASPLL. The data element occurrence number (1-9) must match the occurrence number of the CASSIZ data element to which it refers. CASPLL1: 1580 See data structure (Section 3.4) for WHFF Record Type F for additional information. In 1993, a data comparison was conducted between Casing-Set Size (CASSIZ) and Casing-Pulled Size (CASPLS). Records with the same occurrence number but differing sizes were reconciled so that the sizes were equal. The CASPLS label is no longer used or maintained on the GIPSY file or the WHFF. See data elements: CASFT, CASPLS, CASSIZ.

14 NRIS INFORMATION SYSTEM Page: DATA MANUAL 10/15/91 08/01/ Data Element: Casing-Pulled Size Aliases: CASPLS1-9 The diameter, in inches, of a section of casing pulled from the well. Record Type Well NA Columns This data element is no longer coded or keyed on the Well History Subsystem. The work of reconciling CASPLS and CASSIZ was completed in CASPLS has been eliminated from both the GIPSY file and the WHFF. See data elements: CASSIZ, CASPLL.

15 INFORMATION SYSTEM Page: NRIS DATA MANUAL 10/15/ Data Element: Casing-Set at Depth Aliases: CASDEP1-9 The drilling depth, in feet, at which the section of casing was set in the well. This data element can occur up to nine times per Well History record. Well F/GIPSY Data are coded as numeric values, and are rounded to the nearest foot when inches or decimals are reported. Commas and footage symbols are not coded. Data are normally reported as at, where, landing, or casing pt.. Care is taken to ensure that the value is for the depth at which the casing was set, and not the length of that casing (CASFT). The data element occurrence number (1-9) must match the occurrence number of the CASSIZ data element to which it refers. CASDEP1: 4950 See data structure (Section 3.4) for WHFF Record Type F for additional information. See data element: CASFT.

16 INFORMATION SYSTEM Page: NRIS DATA MANUAL 10/15/ Data Element: Casing-Set Feet Aliases: CASFT1-9 The length, in feet, of a section of casing that was set in the well. This data element can occur up to nine times per Well History record. Well F/GIPSY Data are coded as numeric values, and are rounded to the nearest foot when inches or decimals are also reported. Commas and footage symbols are not coded. Care is taken to ensure that the value reported is the length of the casing and not the depth of the casing (CASDEP). When the value reported includes JTS (# of joints), it is also coded with a numeric value, followed by JTS. The data element occurrence number (1-9) must match the occurrence number of the CASSIZ data element to which it refers. CASFT1: JTS See data structure (Section 3.4) for WHFF Record Type F for additional information. See data element: CASDEP.

17 NRIS INFORMATION SYSTEM Page: DATA MANUAL 10/15/91 08/01/ Data Element: Casing-Set Grade Aliases: CASGRD1-9 Grade number or brand name of a section of casing that was set in the well. This data element can occur up to nine times per Well History record. Well F/GIPSY Data are alpha/numeric. When more than one grade is reported for a particular section of casing, the values are not separated by commas. Some commonly reported grades are: J-55, K, H-90, L.W., LTD. SVC., NEW, USED, SMLS, SEAM., YOUNGSTOWN, PITTSBURG, BETHLEHEM, and NATIONAL. The data element occurrence number (1-9) must match the occurrence number of the CASSIZ data element to which it refers. CASGRD1: J-55 CASGRD2: YOUNGSTOWN For the Osage formats, this data element was only specifically requested on the 05 format. See data structure (Section 3.4) for WHFF Record Type F for additional information.

18 NRIS INFORMATION SYSTEM Page: DATA MANUAL 10/15/91 08/01/ Data Element: Casing-Set Size Aliases: CASSIZ1-9 The diameter, in inches, of a section of casing that was set in the well. The casing size serves as the unique identifier for a section of casing in a well, and all other data elements which describe that section of casing are linked to the casing size via the data element occurrence number. This data element can occur up to nine times per Well History record. Well F/GIPSY Data are normally reported as numeric values with fractions (e.g., 8 5/8, 5 1/2). If stage collar, casing shoe or DV tool information was reported for wells added to the file prior to 1994, it was coded under the FORMREM data element in the format CASSIZn: comment. With the implementation of the Osage formats in 1994, data elements were added for casing shoe information (SHOEFT and SHOEMK). Care is taken to ensure that all casing and cementing data elements that are related to the section of casing, as identified by the casing size, are assigned the appropriate data element occurrence numbers. CASSIZ1: 15 1/2 A section of casing for a well is uniquely identified by its size, therefore this data element determines the data element number for all WHFF Type F data elements. The exception is on the 1979 and A formats and the 04 and 05 Osage formats where packer data is reported in a separate area on the form with no reference to casing size. For these formats, the data element number is sequentially assigned for the PACMAK and PACDEP data elements. See data structure (Section 3.4) for WHFF Record Type F for additional information. See data elements: FORMREM, PACMAK, PACDEP.

19 NRIS INFORMATION SYSTEM Page: DATA MANUAL 10/15/91 08/01/ Data Element: Casing-Set Type Aliases: CASTYP1-9 The type of a section of casing that was set in the well. This data element can occur up to nine times per Well History record. Well F/GIPSY Types of casing usually reported include Conductor, Surface, Intermediate, Production, Liner, Tubing, Tieback, Perforated Liner, and Slotted Liner. The data element occurrence number (1-9) must match the occurrence number of the CASSIZ data element to which it refers. CASTYP1: SURFACE CASTYP2: PRODUCTION This data element is only specifically requested on the A format but is sometimes volunteered on earlier 1002A and Osage formats. See data structure (Section 3.4) for WHFF Record Type F for additional information.

20 INFORMATION SYSTEM Page: NRIS DATA MANUAL 10/15/ Data Element: Casing-Set Weight Aliases: CASWGT1-9 The weight of a section of casing that was set in the well. This data element can occur up to nine times per Well History record. Well F/GIPSY Data are coded as numeric values. The data element occurrence number (1-9) must match the occurrence number of the CASSIZ data element to which it refers. CASWGT1: 70 CASWGT2: 32 See data structure (Section 3.4) for WHFF Record Type F for additional information.

21 NRIS INFORMATION SYSTEM Page: DATA MANUAL 10/15/91 08/01/ Data Element: Cement Fillup Aliases: CEMFIL1-9 The length, in feet, of the portion of the section of casing that was filled with cement. Sometimes this data element is expressed as a percentage of the total section of casing. This data element can occur up to nine times per Well History record. Well F/GIPSY Data are usually coded as numeric values, but can be alpha. If CIRC TO TOP is reported as well as CEMSAX data, the value of CASFT is coded. If CIRC is reported without the word top, CIRC is coded. When there is no value reported for CEMFIL and values are reported for CEMTOP, CASFT, and CEMSAX, the CEMTOP value is subtracted from the CASFT value and the difference is used as the value for CEMFIL unless the difference results in a negative value. In such cases, no value is reported for CEMFIL. The data element occurrence number (1-9) must match the occurrence number of the CASSIZ data element to which it refers. CEMFIL1: 2980 CEMFIL2: 100% This data element is not specifically requested on any Osage formats. See data structure (Section 3.4) for WHFF Record Type F for additional information. See data elements: CASFT, CEMTOP, CEMSAX.

22 NRIS INFORMATION SYSTEM Page: DATA MANUAL 10/15/91 08/01/ Data Element: Cement Sacks Aliases: CEMSAX1-9 The number of sacks of cement used for a specified section of casing during the drilling of the well. This data element can occur up to nine times per Well History record. Well F/GIPSY Data are normally coded as numeric values representing the number of sacks. If the data are in a unit of measurement other than sacks, the numeric value is followed by the reported units. The data element occurrence number (1-9) must match the occurrence number of the CASSIZ data element to which it refers. CEMSAX1: 250 CEMSAX1: 10 YDS CEMSAX1: 150 CUFT For Osage format records, this data element is only specifically requested on the 01 and 05 formats. See data structure (Section 3.4) for WHFF Record Type F for additional information.

23 NRIS INFORMATION SYSTEM Page: DATA MANUAL 10/15/91 08/01/ Data Element: Cement Top Aliases: CEMTOP1-9 The drilling depth, in feet, of the top of the cement in a section of casing in the well. This data element can occur up to nine times per Well History record. Well F/GIPSY Data are normally coded as numeric values. If CIRC TO TOP, SURFACE, GROUND, or GL are reported, the value is coded as 0. When the data reported as the cement top is also identified as a liner or casing top, it is recorded under this data element in the format nnnn (LINER TOP). The data element occurrence number (1-9) must match the occurrence number of the CASSIZ data element to which it refers. CEMTOP1: 0 CEMTOP2: 2300 CEMTOP1: 2400 (LINER TOP) CEMTOP2: 2800 (CASING TOP) This data element is not specifically requested on any Osage formats. See data structure (Section 3.4) for WHFF Record Type F for additional information.

24 NRIS INFORMATION SYSTEM Page: DATA MANUAL 10/15/91 08/01/ Data Element: Cementing Chemicals (Make) Aliases: CEMCHM1-9 Data element describing the types of chemicals used in the cementing of a section of casing. This data element can occur up to nine times per Well History record. Well F/GIPSY Data are coded as textual descriptions of the chemicals used in the cement, including percents, ratios, sacks, and barrels of various materials. Care is taken to ensure that all relevant reported data are clearly coded for keying. The data element occurrence number (1-9) must match the occurrence number of the CASSIZ data element to which it refers. CEMCHM1: POZ W/2% GEL 1% CFR2 This data element was only specifically requested on the 1952 and A and the 04 and 05 Osage formats but is sometimes volunteered on other formats. See data structure (Section 3.4) for WHFF Record Type F for additional information.

25 NRIS INFORMATION SYSTEM Page: DATA MANUAL 08/01/91 _08/01/95_ 3.3 Data Element: Character of Well Aliases: CHARWEL Data element used to describe the overall character of the well, considering the classes (CLASS01, CLASS02, etc.) reported for the reported producing formations. Well A/GIPSY 194 Computer-generated based on the CLASS data items, or coded on the form during prescan when CLASS is not reported or does not reflect the overall character of the well. If a show of a hydrocarbon is reported but it is not produced, it is not considered in determining the character of the well. G GAS - If gas production is reported O OIL - If oil production is reported B GAS and OIL - If oil and gas production are reported S Service Well - Gas injection, water injection, air injection, salt water disposal, water supply for injection, or observation well T Temporarily Abandoned - If the well is temporarily abandoned J Junked and Abandoned - If the hole was lost and abandoned D Dry - If no production and no other status are reported U Unknown - only used when there is not enough information reported to determine the overall character of the well All codes in CHARWEL must be from the list of valid codes. CHARWEL: O See data element: CLASS.

26 INFORMATION SYSTEM Page: NRIS DATA MANUAL 10/15/91 08/01/ Data Element: Choke Size Aliases: CHOKE01-30 The size of the choke used during the initial production test. This data element can occur up to 30 times per Well History record. Well D/GIPSY Data can be alpha or numeric and are usually reported as a fraction. The words OPEN or FULL are included along with the numeric value when reported. VARIOUS is acceptable text. The data element occurrence number (01-30) must match the occurrence number of the PFNAM data element to which it refers. CHOKE01: 20/64 For the Osage formats, this data element was only requested on the 01 and 04 formats. See data structure (Section 3.4) for WHFF Record Type D for additional information. See data element: BCHOKE.

27 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/ Data Element: Choke Size Before Treatment Aliases: BCHOKE1-2 The size of the choke used during the initial production test before any acid or fracture treatment was applied. This data element can occur up to two times per Well History record. Well K/GIPSY Data can be alpha or numeric and are usually reported as a fraction. The words OPEN or FULL are included along with the numeric value when reported. VARIOUS is acceptable text. The data element occurrence number (1-2 on GIPSY file, on the WHFF) must match the occurrence number (01-02) of the PFNAM data element to which it refers. BCHOKE1: 20/64 Before Treatment initial production test data elements are only requested on the Osage Tribal Council Completion Report records. Choke data are only requested on the 01 and 04 Osage formats. See data structure (Section 3.4) for WHFF Record Type K for additional information. See data element: CHOKE.

28 NRIS INFORMATION SYSTEM Page: DATA MANUAL 10/15/91 08/01/ Data Element: Classification Aliases: CLASS01-30 Classification as reported by the operator for the producing formation tested for oil and/or gas production. This data element can occur up to 30 times per Well History record. Well C/GIPSY Data are reviewed to ensure the classification is one of the valid values and reflects the initial production test results (i.e., if Class = OIL, then oil production is reported). If DUAL is reported, the data element MULTIZ is coded if not already reported. If the operator has commented that volumes measured during the IP test were not commercially producible, that information is included under the FORMREM data element. For all 1002A formats except the 1910 format, if all classes are dry, PLGDATE is coded on the form using the reported completion or drill-end date, and CMPDATE is not recorded. This does not apply to Osage format records. The data element occurrence number (01-30) must match the occurrence number of the PFNAM data element to which is refers.

29 NRIS INFORMATION SYSTEM Page: DATA MANUAL 10/15/91 08/01/ Data Element: Classification (continued) Aliases: CLASS01-30 ASD Abandoned-Salvage Deferred Well CORE HOLE Core Hole CORE TEST Core Test DISPOSAL Disposal Well DRY Dry Well GAS Gas Well GAS, INJ Gas & Injection Well GAS INJ Gas Injection Well GAS OIL Gas & Oil Well GAS STORAGE Gas Storage Well INJ Injection Well INJ, WSW Injection & Water Storage Well JA Junked & Abandoned Well OBSERVATION Observation Well OIL Oil Well OIL, INJ Oil & Injection Well OIL, WSW Oil & Water Storage Well PA Plugged & Abandoned Well RELIEF Relief Well SWD Salt Water Disposal Well SWS Salt Water Storage Well TA Temporarily Abandoned Well WDW Water Disposal Well WIW Water Injection Well WSW Water Storage Well All values must be one of the valid values listed above. If all CLASSes are dry, PLGDATE must be reported. For completion reports filed on the 1910, 1952 and A and all Osage formats, these data usually reflect an overall classification of the well and are comparable to the CHARWEL data element. For 1979, 1985 and 1992 formats, these data reflect the classification for the producing formation tested with the same data element number (01-30). See data structure (Section 3.4) for WHFF Record Type C for additional information. See data elements: PLGDATE, MULTIZ, FORMREM, CHARWEL.

30 NRIS INFORMATION SYSTEM Page: DATA MANUAL 10/15/91 08/01/ Data Element: CO2-Encountered Flag Aliases: CO2PRES Logical flag indicating that carbon dioxide was encountered during the drilling of the well. Well H/GIPSY 19 This logical flag is coded when the operator reports information indicating that carbon dioxide was encountered during drilling. blank Y No carbon dioxide was reported Carbon dioxide was encountered CO2PRES: Y This data element only appears on the 1985 and A formats but is sometimes volunteered on other formats. See data element: CO2DPTH.

31 NRIS INFORMATION SYSTEM Page: DATA MANUAL 08/01/91 08/01/ Data Element: Coder Remarks Regarding Form Aliases: FORMREM Information relevant to the well, which has not been captured in any of the standard well data elements, is recorded under this data element. Well G/GIPSY This data element is used for information which is not covered by any of the standard data elements, or for special comments that refer to a standard data element. When the remark refers to a specific data element, the alias for that data element is recorded first, followed by the remark. If the remark refers to the well in general, ALL: is used in place of a specific alias. FORMREM: CASSIZ4: 2ND STAGE - DV Data commonly included under FORMREM are: asphalt; coal; H2S; DV tools; casing shoes; stage collars; squeezed or notched perforations; bottom-hole pressure; second 24 hour production; or production information that, according to coding instructions, should not be recorded under IPROD, OBBLD, or GMCFD. When an operator reports more than nine oil/gas zones, the additional zones are recorded here. For the WHFF, data are truncated after 1145 bytes. The GIPSY master file must be consulted for more information. With the implementation in 1994 of the 1992 and Osage formats, data elements for casing shoes and bottom-hole location data were added to the file and are no longer being coded under FORMREM. See the data structures for Record Types F and J for more information on these new data elements. See data structure (Section 3.4) for WHFF Record Type G for additional information.

32 NRIS INFORMATION SYSTEM Page: DATA MANUAL 08/01/91 08/01/ Data Element: Commingled-Completion Flag Aliases: COMMING Logical flag indicating that the well has been completed for joint production out of two or more producing intervals. Record Type Well GIPSY Columns The completion report form is reviewed for reported production commingling. When present, the logical flag COMMING is added to the record. COMMING: Y This flag is maintained on the GIPSY file only. The data are included as part of the completion type data element on the WHFF file. This data element is not specifically requested on any Osage formats. See data elements: COMMORD, CMPTYPE.

33 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/91 08/01/ Data Element: Commingled-Completion Order Number Aliases: COMMORD Order number assigned by the Oklahoma Corporation Commission that allowed a well to be completed for joint production out of two or more producing intervals. Record Type Well GIPSY Columns This data element is coded when it has been determined that the well is a commingled completion and an order number is reported by the operator. Data are alpha/numeric. This data element does not apply to Osage Tribal Council records since it is an OCC order number. COMMORD: This data element is maintained on the GIPSY file only. The data are included as part of the completion-type order number data element on the WHFF file. See data elements: COMMING, CMPORD.

34 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/ Data Element: Company Name Which Drilled Well Aliases: DRILLBY Name of the company responsible for the drilling of the well. Well L/GIPSY Information reported reflects company s name which drilled the well and may be a subcontractor for the well. DRILLBY: LEE DRILLING COMPANY This data element is only requested on the Osage Tribal Council Completion Report records.

35 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/ Data Element: Completion Type Aliases: CMPTYPE Data element indicating the type of completion for the well, and qualifying the type of order number that is designated in CMPORD. Well B 106 Computer-generated for the WHFF from the GIPSY logical flags SINGLEZ, MULTIZ, AND COMMING. S M C Single zone completion Multizone completion Commingled completion See data elements: SINGLEZ, MULTIZ, COMMING, CMPORD.

36 NRIS INFORMATION SYSTEM Page: DATA MANUAL 08/01/91 08/01/ Data Element: Completion-Type Order Number Aliases: CMPORD Data element indicating the order number(s) assigned by the Oklahoma Corporation Commission that allowed the type of completion for the well. Well B Data for this data element are computer-generated from the GIPSY data elements SINGORD, MULTORD and COMMORD as appropriate for the type of well completion. Refer to the completion type data element (CMPTYPE) to determine if this order is for a single zone, multizone, or commingled completion. This data element does not apply to Osage Tribal Council records since it is an OCC order number. See data elements: SINGORD, MULTORD, COMMORD, CMPTYPE.

37 NRIS INFORMATION SYSTEM Page: DATA MANUAL 10/15/91 08/01/ Data Element: Condensate in Barrels per Day Aliases: CBBLD01-30 The amount of condensate produced during the initial production test, in barrels per day (BBLD). This data element can occur up to 30 times per Well History record. Well D/GIPSY These data are sometimes reported on the 1002A form where oil data are requested. Data are recorded as a numeric value, with decimals when reported. BBLD is not coded. When fractions are reported they are converted to decimal values. TRACE, UNTESTED, NOT MEASURED, and TSTM (too small to measure) are acceptable text. When it is unclear that the initial test duration was 24 hours, the data are recorded under the IPROD data element with BC following the value. The data element occurrence number (01-30) must match the occurrence number of the PFNAM data element to which it refers. Data must be numeric or TRACE, NOT MEASURED, TSTM, or UNTESTED. CBBLD01: 50 These data are not requested on the 1002A or Osage forms but are sometimes volunteered by the operator. See data structure (Section 3.4) for WHFF Record Type D for additional information. See data elements: OBBLD, CBBLM, IPROD, BCBBLD.

38 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/ Data Element: Condensate in Barrels per Day Before Treatment Aliases: BCBBLD1-2 The amount of condensate produced during the initial production test, before any acid or fracture treatment was applied, in barrels per day (BBLD). This data element can occur up to two times per Well History record. Well K/GIPSY These data are sometimes reported on the completion form where oil data are requested. Data are recorded as a numeric value, with decimals when reported. BBLD is not coded. When fractions are reported they are converted to decimal values. TRACE, UNTESTED, NOT MEASURED, and TSTM (too small to measure) are acceptable text. When it is unclear that the initial test duration was 24 hours, the data are recorded under the IPROD data element with BC following the value. The data element occurrence number (1-2 on GIPSY file, on the WHFF) must match the occurrence number (01-02) of the PFNAM data element to which it refers. Data must be numeric or TRACE, NOT MEASURED, TSTM, or UNTESTED. CBBLD01: 50 Before Treatment initial production test data elements are only requested on the Osage Tribal Council Completion Report records. These data are not specifically requested on the Osage formats but are sometimes volunteered by the operator. See data structure (Section 3.4) for WHFF Record Type K for additional information. See data elements: BOBBLD, BCBBLM, BIPROD, CBBLD.

39 NRIS INFORMATION SYSTEM Page: DATA MANUAL 10/15/91 08/01/ Data Element: Condensate in Barrels per MCF Aliases: CBBLM01-30 The amount of condensate produced during the initial production test, in barrels per MCF. This data element can occur up to 30 times per Well History record. Well D/GIPSY This data element is used when condensate production is reported as barrels per MCF of gas instead of barrels per day. Data are usually a numeric value, with decimals when reported. BBLM is not coded. If fractions are reported, they are converted to decimal values. TRACE, UNTESTED, NOT MEASURED, and TSTM (too small to measure) are acceptable text. If the volume is reported in units other than barrels per MCF, it is converted appropriately (e.g., 10 bbl/mmcf =.01 bbl/mcf). The data element occurrence number (01-30) must match the occurrence number of the PFNAM data element to which it refers. Data must be numeric or TRACE, NOT MEASURED, TSTM, or UNTESTED. CBBLM01: 2.5 CBBLM02:.02 These data are not requested on the 1002A or the Osage formats but are sometimes volunteered by the operator. See data structure (Section 3.4) for WHFF Record Type D for additional information. See data elements: CBBLD, BCBBLM.

40 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/ Data Element: Condensate in Barrels per MCF Before Treatment Aliases: BCBBLM1-2 The amount of condensate produced during the initial production test before any acid or fracture treatment was applied, in barrels per MCF. This data element can occur up to two times per Well History record. Well K/GIPSY This data element is used when condensate production is reported as barrels per MCF of gas instead of barrels per day. Data are usually a numeric value, with decimals when reported. BBLM is not coded. If fractions are reported, they are converted to decimal values. TRACE, UNTESTED, NOT MEASURED, and TSTM (too small to measure) are acceptable text. If the volume is reported in units other than barrels per MCF, it is converted appropriately (e.g., 10 bbl/mmcf =.01 bbl/mcf). The data element occurrence number (1-2 on GIPSY file, on the WHFF) must match the occurrence number (01-02) of the PFNAM data element to which it refers. Data must be numeric or TRACE, NOT MEASURED, TSTM, or UNTESTED. BCBBLM1: 2.5 BCBBLM2:.02 Before Treatment initial production test data elements are only requested on the Osage Tribal Council Completion Report records. These data are not specifically requested on the Osage formats but are sometimes volunteered by the operator. See data structure (Section 3.4) for WHFF Record Type K for additional information. See data elements: BCBBLD, CBBLM.

41 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/91 09/15/ Data Element: County Code (FIPS) Aliases: COCODE County Code as established by FIPS (Federal Information Processing Standard). Equal to API county codes. On the Lease Master File, the county code is one of four components in the Oklahoma Tax Commission's Production Unit Number (PUN), the data structure which is used as the key identifier on the Lease Master File. Well A/GIPSY Lease All 8-10 Field All 8-25 (up to 6 occurrences) County Three-digit numeric, computer-generated for the Well History Subsystem based on the reported county name. (see list in Appendix B) 000 County Unknown Code must be one of 77 valid codes for Oklahoma, or 000 (county unknown). Numeric/odd number code for Latimer County County codes for a field in Latimer, Leflore, and Pittsburg counties (Field Master File only) See data element: COUNTY. See OGP data structure: PUN.

42 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/ Data Element: County Code (FIPS) of Bottom Hole Location Aliases: BHCOCD1-9 Bottom hole location county code as established by FIPS (Federal Information Processing Standard). Equal to API county codes. This data element can occur up to nine times per well history record. Well J/GIPSY Three-digit numeric, computer-generated for the Well History Subsystem based on the reported county name of the bottom hole location. (see list in Appendix B) 000 County Unknown Code must be one of 77 valid codes for Oklahoma, or 000 (county unknown). Numeric/odd number code for Latimer County This data element only appears on the A format but may be volunteered on other formats. See data structure (Section 3.4) for WHFF Record Type J for additional information. See data element: BHCNTY.

43 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/91 09/15/ Data Element: County Name Aliases: COUNTY (Well History); CNTYNAM (OGP) Name of county where the well is located (Well History), or county for which production is reported (County Master File). Well A/GIPSY County Spelling checked; no abbreviations. Must be present. One of Oklahoma's 77 counties (see list in Appendix B), or Unknown Present and valid Oklahoma county. The county name must correspond with the FIPS county code (COCODE). COUNTY: POTTAWATOMIE On a well record, if COUNTY is updated based on something other than a subsequent 1002A form, the change is noted under the FORMREM data element. (E.g., FORMREM: COUNTY changed from Okmulgee.) This is done to aid in the reconciliation of missing well records. See data element: COCODE.

44 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/ Data Element: County Name of Bottom Hole Location Aliases: BHCNTY1-9 Name of county where the bottom hole of the well is located This data element can occur up to nine times per Well History Record. Well J/GIPSY Spelling checked; no abbreviations. Must be present. One of Oklahoma's 77 counties (see list in Appendix B), or Unknown Present and valid Oklahoma county. The county name must correspond with the FIPS county code (COCODE). COUNTY: POTTAWATOMIE On a well record, if BHCNTY is updated based on something other than a subsequent 1002A form, the change is noted under the FORMREM data element. (E.g., FORMREM: BHCNTY1 changed from Okmulgee.) This is done to aid in the reconciliation of missing well records. This data element only appears on the A format but may be volunteered on other formats. See data structure (Section 3.4) for WHFF Record Type J for additional information. See data element: BHCOCD.

45 NRIS INFORMATION SYSTEM Page: DATA MANUAL 08/01/91 08/01/ Data Element: Cross-Reference-Record Flag Aliases: XREF Logical flag to identify that a well record is an original submission, and has one or more related records on file which have additional information for that well. Record Type Well GIPSY Columns Logical flag, written on the original form during prescan, or updated to a pre-existing well record when a new completion report is received for that well. Any record with this flag must have a related record (with the same API number) on file that reports additional information (ADDINFO). If XREF is assigned to a form, APINUM must be present. For every XREF record on file, one or more ADDINFO records with the same APINUM must also be on file. For every ADDINFO record on file, one (and only one) XREF record with the same APINUM must also be on file, or the ADDINFO record must have a NOORIG flag. This logical flag is maintained on the GIPSY version of the Well History Subsystem only. The data are consolidated with other data elements (ADDINFO, WRKOVR) to form the Submission Type (SUBMTYP) data element on the WHFF file. All records with the XREF GIPSY flag have a WHFF Submission Type of XREF. See data elements: ADDINFO, APINUM, NOORIG, SUBMTYP.

46 NRIS INFORMATION SYSTEM Page: DATA MANUAL 10/15/91 08/01/ Data Element: Data Type Aliases: DATATYP This data element is used as a key identifier to distinguish between types of data contained on a WHFF record type. It is only used on record types which contain more than one type of data (currently WHFF types E & G). Well E&G 10 Computer-generated during the conversion from the GIPSY master file to the WHFF, based on the content of the data in the record. D F G O W Drill Stem Test Zones Data, Record Type E Formation Record Data, Record Type E Gas Initial Open Flow Sand Zones Data, Record Type E Oil/Gas Zones Data, Record Type E Water Zones Data, Record Type E C G P R U W Coder Remarks, Record Type G Plugging Remarks, Record Type G Protection Methods for Sands, Record Type G Remarks by the Operator, Record Type G Unusual Drilling Circumstances, Record Type G Work Detail Remarks, Record type G The value/codes for this data element were expanded beginning with the January 1994 data release. See data structures (Section 3.4) for WHFF Record Types E and G for additional information. See data elements: FBOT, FNAM, FORMREM, FTOP, GIOFFR, GIOFMC, GIOFNM, GIOFRP, GIOFTO, OGZNAM, OGZNFR, OGZNTO, PLUGRMK, PROTECT, REMARKS, SFNAM, STBOT, STTOP, UNUSUAL, WRKDETL, WTRZFR, WTRZNM, WTRZTO.

47 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/ Data Element: Date Deepening Finished Aliases: DEEPEND The date that drilling to deepen the well ended. Well B/GIPSY Coded for the GIPSY File in the format YYYY MM DD. For records with incomplete dates, 99 is used for month and/or day and 9999 is used for year to indicate unknown. Must be a valid date format; valid date ( current date); and a date that is later than the deepening started date (DEEPSTR). DEEPEND: This data element is only specifically requested on Osage format records but may be used when appropriate for 1002A records. See data element: DEEPSTR.

48 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/ Data Element: Date Deepening Started Aliases: DEEPSTR The date that drilling to deepen the well started. Well B/GIPSY Coded for the GIPSY File in the format YYYY MM DD. For records with incomplete dates, 99 is used for month and/or day and 9999 is used for year to indicate unknown. Must be a valid date format and valid date ( current date). DEEPSTR: This data element is only specifically requested on Osage format records but will be used when appropriate for 1002A records. See data element: DEEPEND.

49 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/91 10/15/ Data Element: Date Drilling Ended Aliases: DRILEND The date that drilling ended for the well. Well B/GIPSY Coded for the GIPSY file in the format YYYY MM DD. If the well is dry and no other date is available, this date is coded for plugging date (PLGDATE) as well as the DRILEND data element. For records with incomplete dates, 99 is used for month and/or day and 9999 is used for year to indicate unknown. Must be valid date format; valid date ( current date); and a date that is later than the drilling-started date (DRILSTR). DRILEND: For the WHFF, the format is YYYYMMDD (spaces are eliminated). See data elements: PLGDATE, DRILSTR.

50 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/91 10/15/ Data Element: Date Drilling Started Aliases: DRILSTR The date that drilling was started for the well. Well B/GIPSY Coded for the GIPSY file in the format YYYY MM DD. For records with incomplete dates, 99 is used for month and/or day and 9999 is used for year to indicate unknown. Must be present; valid date ( current date); and valid date format. DRILSTR: For the WHFF, the format is YYYYMMDD (spaces are eliminated).

51 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/ Data Element: Date Location Fee Was Paid Aliases: LFEEDTE The date that the location fee was paid. Well M/GIPSY Coded for the GIPSY file in the format YYYY MM DD. For records with incomplete dates, 99 is used for month and/or day and 9999 is used for year to indicate unknown. Must be present; valid date ( current date); and valid date format. LFEEDTE: This data element is only specifically requested on Osage format records. For the WHFF, the format is YYYYMMDD (spaces are eliminated).

52 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/91 08/01/ Data Element: Date of Completion Aliases: CMPDATE Date the well was completed. Well B/GIPSY Coded for the GIPSY file in the format YYYY MM DD. If the well is dry and the operator has reported a completion date, that date is coded under the plugging date (PLGDATE) data element instead of the CMPDATE data element. (This does not include the A or Osage formats.) For records with incomplete dates, 99 is used for month and/or day and 9999 is used for year to indicate unknown. Valid date ( current date); valid date format; a date that is later than the drill-start date (DRILSTR), and later than or equal to the drilling-finished date (DRILEND). CMPDATE: This data element is not requested on any of the Osage formats. For the WHFF, the format is YYYYMMDD (spaces are eliminated). See data elements: PLGDATE, DRILSTR, DRILEND.

53 INFORMATION SYSTEM Page: NRIS DATA MANUAL 08/01/91 10/15/ Data Element: Date of First Production Aliases: FRSTPRD Date the well first produced oil or gas. Well B/GIPSY Coded for the GIPSY file in the format YYYY MM DD. Operators sometimes report shutin information in this blank on the 1002A formats, which is converted to the SHUTIN data element. For records with incomplete dates, 99 is used for month and/or day and 9999 is used for year to indicate unknown. Must be valid date ( current date); valid date format; and a date that is after the drill-start (DRILSTR) and drill-end (DRILEND) dates. FRSTPRD: This data element is not requested on any Osage formats. For the WHFF, the format is YYYYMMDD (spaces are eliminated). See data elements: SHUTIN, DRILSTR, DRILEND.