well data gap analysis project - pa - emarketplace well data gap analysis project gap analysis...

Well Data Gap Analysis Project

Gap Analysis Report Version 2.0

Prepared by:

November 5, 2010

Department of Conservation and Natural Resources Well Data Gap Analysis Project

Gap Analysis Report v 2.0

Well Data Gap Analysis Project

Gap Analysis Report Version 2.0

Prepared by:

The Gap Analysis Report is the overall deliverable of the Wells Data Gap Analysis Project.

Deliverable Approval

Margaret Hively, Department of Conservation and Natural Resources

Date Amy Malinoski, TreCom Systems Group

Date

George Love, Department of Conservation and Natural Resources

Date



Revision History

Document Version #

Revision Date Description of Change Initials

1.0 11/5/2010 Initial Creation ADM, MC

2.0 11/12/2010 Editing changes to Section 1 ADM

Editing changes to Section 1.1 ADM

Updates to Section 1.2 to clarify definitions, to remove several terms and to add new terms

ADM

Editing changes to Section 2 ADM

Editing changes to Section 3.1.1 ADM

Editing changes to Section 3.1.2, additional information about NAD 27 and NAD 83, additional information about permit numbers and the usage of the API

ADM

Added deficiencies to Section 3.1.4 including adding angle and course of deviation to data deficiencies, location information stored in multiple locations, system should allow management of users from interface; also some editing changes

ADM

Editing changes to Section 3.2.2, 3.2.3 and 3.2.4 ADM

Editing changes to Section 3.3.1 ADM

Changed Figure 44 ADM

Added deficiency to Section 3.3.4 for the Access files being incomplete

ADM

Editing changes to Section 3.4.1, added statement that accurate location information is a legal requirement

ADM

Editing changes to Section 3.4.2, updated information on the map available in WebDriller, changed information on well pluggings

ADM

Changed the first deficiency in Section 3.4.4 to state that the user should have to verify the coordinates on a map, updated the information on the well abandonments to include additional issues noted

ADM

Editing changes to Section 3.5.1 and 3.5.2 ADM

Section 4.2 updated with editing changes, bullets regarding well depth have been removed, additional bullets about location data have been added

ADM

Section 4.4 updated to note negative longitude is for the western hemisphere, to further explain the spreadsheet and what the columns represented, and editing changes

ADM

Section 5 updated with editing changes, clarifications on the need for images for water wells and the ability to map water wells

ADM

Editing changes to Section 6 ADM



Table of Contents 1. Introduction ........................................................................................................................ 5

1.1 Purpose ...................................................................................................................... 6 1.2 Terms and Acronyms .................................................................................................. 6 1.3 References ................................................................................................................10

2. Gap Analysis Process .......................................................................................................10 3. Functionality Analysis ........................................................................................................10

3.1 WIS ...........................................................................................................................10 3.1.1 Purpose .............................................................................................................10 3.1.2 Functionality .......................................................................................................11 3.1.3 Architecture ........................................................................................................37 3.1.4 Deficiencies .......................................................................................................37

3.2 PA*IRIS .....................................................................................................................39 3.2.1 Purpose .............................................................................................................39 3.2.2 Functionality .......................................................................................................40 3.2.3 Architecture ........................................................................................................46 3.2.4 Deficiencies .......................................................................................................48

3.3 PaGWIS ....................................................................................................................49 3.3.1 Purpose .............................................................................................................49 3.3.2 Functionality .......................................................................................................50 3.3.3 Architecture ........................................................................................................57 3.3.4 Deficiencies .......................................................................................................58

3.4 WebDriller ..................................................................................................................59 3.4.1 Purpose .............................................................................................................59 3.4.2 Functionality .......................................................................................................60 3.4.3 Architecture ........................................................................................................64 3.4.4 Deficiencies .......................................................................................................65

3.5 OGAPS > OGRE .......................................................................................................66 3.5.1 Purpose .............................................................................................................66 3.5.2 Functionality .......................................................................................................66 3.5.3 Architecture ........................................................................................................69 3.5.4 Deficiencies .......................................................................................................69

4. Data Analysis ....................................................................................................................69 4.1 Background ...............................................................................................................69 4.2 WIS ...........................................................................................................................70 4.3 PaGWIS ....................................................................................................................73 4.4 WebDriller ..................................................................................................................75

5. Overall Conclusion ............................................................................................................77 6. Stratigraphic Database Analysis ........................................................................................79 7. Technical Information ........................................................................................................79 Appendix A. Meeting Notes ......................................................................................................81 Appendix B. Database Models ............................................................................................... 103 Appendix C. Data Dictionary - WIS ........................................................................................ 104 Appendix D. Data Dictionary - PaGWIS ................................................................................. 137 Appendix E. Data Dictionary - WebDriller ............................................................................... 154



1. Introduction

The Well Data Gap Analysis Project was initiated by the Department of Conservation and Natural Resources (DCNR) Bureau of Information Technology (BIT) to have an independent resource inventory and evaluate all systems in use in DCNR that track and manage well related information. DCNR’s Bureau of Topographic and Geologic Survey (the Bureau) has a mission “to serve the citizens of Pennsylvania by collecting, preserving, and disseminating impartial information on the Commonwealth’s geology, geologic resources, and topography in order to contribute to the understanding, wise use, and conservation of its land and included resources.” In order to achieve this mission with respect to oil, gas and water wells in the Commonwealth, the Bureau utilizes several systems that record and track wells. These are disparate systems running on separate platforms using a variety of technologies. To better serve the constituency in Pennsylvania, the Bureau wishes to move all of these systems to the same platform using the same database schema. Prior to moving forward with this; however, the Bureau initiated the Gap Analysis Project to gather critical information on the structure and utilization of these systems.

The Commonwealth of Pennsylvania does not regulate water wells; however, according to PA Act 610 (the Water Well Drillers License Act), the Commonwealth does require that water well drillers be licensed in Pennsylvania, that all drilling rigs are permitted, and that a well completion report is submitted. The well completion report is a critical document providing information on the location of the well (address and latitude/longitude), the well depth, the specifics on the borehole, and the rock formations the well penetrated (driller’s log). PA Act 610 also requires that the information stored for all water wells in the Commonwealth be available and accessible to the public. To meet these requirements, DCNR has two different systems in place. WebDriller is the online application used by DCNR to allow drillers to renew their licenses, permit their rigs, and enter their completion reports. The Pennsylvania Groundwater Information System (PaGWIS) is the source of information for all water wells in the Commonwealth and is accessible to everyone using the DCNR website.

Oil/gas wells are treated much differently in the Commonwealth. They are strictly regulated by the Department of Environmental Protection (DEP) according to PA Act 223 (the Oil and Gas Act), which enumerates the regulations and requirements of drilling and operating oil/gas wells in the Commonwealth. In order to drill an oil/gas well in the Commonwealth, a permit application is required. This application requires information on the location of the well (location plat), the steps that must be taken in order to receive a permit, and a fee. The permit application is sent to DEP and entered into their eFACTS system, and DEP sends a copy of the location plat to DCNR. (The permit is not sent to DCNR). Once the permit is approved, the operator may proceed with drilling. With respect to oil/gas wells, the operator may not be the same as the driller. This is a fundamental difference between water wells and oil/gas wells. Once the well is drilled, the operator is required to complete a well completion report. This includes much of the same data as the well completion report completed for water wells; however, there is much greater specificity and detail with the well completion reports for oil/gas wells. The well completion report is submitted to DEP and approved after DEP has conducted an inspection. The well completion reports are then sent to DCNR so that the geologic information provided on the form can be analyzed and interpreted. Throughout the life of the well, the production of oil/gas and the waste generated in that production must be reported to the Commonwealth. At the end of the lifecycle of the well, it is required to be plugged, and a plugging certificate indicating when and how the well was plugged must be provided to DEP. This form is also sent to DCNR. In order to track, manage, and record the information



concerning the oil/gas wells in the Commonwealth, the Bureau utilizes several different systems. The Wells Information System (WIS) is the official source of information concerning the oil/gas wells. The Pennsylvania Internet Record Imaging System (PA*IRIS) provides online access to the data in WIS as well as to all imaged documents archived by the Bureau and stored in OnBase. And the Oil and Gas Annual Production System (OGAPS) has been used by operators to electronically submit their production reports.

The Bureau has offices located in Middletown and in Pittsburgh. The Middletown office is the central location for the Bureau and is where the hydrogeologists are located who support the water wells for DCNR. The Pittsburgh office is the location of the Bureau’s Carbon Sequestration (formerly Oil, Gas & Subsurface Geological Services) Section. This unit is staffed with administrative personnel as well as geologists who support the oil/gas wells for DCNR.

1.1 Purpose

The purpose of this Gap Analysis Report is to provide a document that captures all of the information gathered throughout the project concerning the functionality of WIS, PA*IRIS, PaGWIS, WebDriller, and OGAPS. The project involved analyzing and using the systems and interviewing the subject matter experts at the Bureau to discuss their workflow, the functionality in these systems, and their desired functionality of the new system. In addition, the databases used by these systems were analyzed. This included reviewing data models, developing data dictionaries, reviewing data quality and integrity, and noting important areas concerning data when moving to a new system.

The Bureau intends to use the information captured in this document to pursue the next steps in securing a vendor to complete the development and implementation of a solution that will provide the Bureau with a system that supports all wells in the Commonwealth on a single code base with a single database schema.

This document includes an explanation of the process taken by the team to complete the objectives of the project. It also includes background information on each system as well as a description of the functionality included in each system with screenshots. An accounting of the database and the data is provided for WIS, PaGWIS, and WebDriller as well as an explanation of the architecture. A section is devoted to the deficiencies identified by the team as well as those supplied by the subject matter experts during the interviews. The report appendices include meeting notes from the project, the data models, and the data dictionaries for WIS, PaGWIS, and WebDriller.

1.2 Terms and Acronyms

The section defines the terms used in the document as well as the definition of any acronyms used in this document.

Term/Acronym Definition

Acres Amount of land in the drilling unit; 1 acre = 43,560 ft2.

API Well Number Unique 14-digit American Petroleum Institute number assigned to a well when a permit is issued. The number format is SS-CCC-NNNNN-KKKK where S is the 2 digit state code, C is the 3 digit FIPS county code, N is the 5 digit unique sequential number, and K is the 4 digit number for each sidetrack.

Application for Permit to Drill Form required by DEP to be able to drill an oil or gas well.




Base Map Topographic map upon which oil/gas wells are plotted for locational reference.

BIT Bureau of Information Technology (DCNR)

Borehole Hole drilled in the act of drilling a well.

Bottom Hole Lowest or deepest part of a well.

Casing Material (usually steel or PVC) used in the borehole to prevent the wall of the hole from caving in and to prevent the movement of fluids from one formation to another. Casing is grouted to keep the casing in place and isolate desired geologic intervals.

Casing Record Type and amount of casing in the well; amount of cement/grout used to seal formations behind various types of casing.

CBM Coalbed Methane; a form of natural gas extracted from coalbeds.

Citrix Metaframe Application virtualization/delivery product or an application hosting solution. It allows remote access to a system and allows thin client access (no application software on the client machine).

CTC Commonwealth Technology Center

DBA Database Administrator; person responsible for the design, implementation, maintenance and repair of an organization’s database(s).

DCNR Department of Conservation and Natural Resources

DEP Department of Environmental Protection

Development well Drilled in proximity to other wells to access known resources in existing fields and pools.

Directional well Non-vertical well. Used to drill into reservoir where vertical access is not possible or not desired.

Driller Company responsible for the drilling of the well. For oil/gas wells, this is typically different than the operator.

eFACTS Environment, Facility, Application, Compliance Tracking System; publicly available system administered by DEP that provides a global view of the clients and sites that DEP regulates.

Exploratory well Drilled to discover new resources in untested areas and/or reservoirs. Typically this is in an area removed from documented production and in some cases, areas where field names haven’t been assigned.

Farm name Name assigned to the surface area that the leaseholder owns.

Field Group of pools related to a single stratigraphic or structural feature; in Pennsylvania, fields are not limited to this particular definition, in that we define fields based on geographic, political, or other types of boundaries to create seamless field boundaries across the state.

FIPS Federal Information Processing Standard

Geophysical log Physical measurements made by an electrical device that




is lowered down a well boring to gather information about the subsurface formations that were encountered during drilling.

GIS Geographic Information System

GL Ground level elevation of the well.

Horizontal well Well in which the lower part of the bore hole parallels the reservoir. A type of directional well.

Initial Rock Pressure Measured bottom hole pressure of the well.

Landowner Surface owner or mineral owner of the land where the well is located.

LAS files Log ASCII Standard (LAS) are digital versions of geophysical logs. These files digitize the curve values and can be easily imported and exported.

Location Plat Drawing of the well location prepared by a licensed surveyor; plots the location of the well on a topographic map.

Log types Kinds of wireline (geophysical) logs run on a well.

Logging Company Company which performs wireline logging of the well. Logging is the process of lowering devices on a wireline into the well to measure the properties of rocks and fluids penetrated by the borehole.

NAD 27 North American Datum 1927; regional geodetic reference system used to translate a location to a real position on Earth given that Earth is not a perfect sphere. Originates in a specific location (Meads Ranch, Kansas).

NAD 83 North American Datum 1983; the horizontal control datum for the United States, Canada, Mexico, and Central America, based on a geocentric origin and the Geodetic Reference System 1980.

NeuraScanner Specialty scanner used to scan geophysical logs. It is capable of scanning paper a mile in length and can accommodate all types of paper.

OCR Optical Character Recognition

OGAPS Oil and Gas Production System

OGO Oil and Gas Operator. This is a number given to all oil and gas operators by DEP.

OGRE Oil and Gas Reporting – Electronic

OnBase Enterprise Content Management software in use by DCNR to store all imaged documents for oil/gas wells.

Operator Person or company actually operating the oil/gas well. It is the company to whom the driller is engaged.

Oracle Discoverer Business intelligence tool that provides ad hoc query and reporting functionality.

PA*IRIS Pennsylvania Internet Record Imaging System

PaGWIS Pennsylvania Groundwater Information System

Perforation Hole punched in the casing or liner of a well to connect it to the reservoir. The number and depth of perforations in production casing and cement (if present) to allow




formation fluids to enter the well bore is to be supplied on the well completion report.

Petrophysical Study of the physical and chemical properties that describe the occurrence and behavior of rocks, soils and fluids.

Plugging Certificate Document that must be completed within 30 days of plugging a well. It must be completed by the well owner and approved by DEP.

Pool Specific area within a field where a single reservoir produces oil and/or gas from one or more formations.

Producing Formation Geologic formation(s) from which oil and/or gas is produced.

Quadrangle U.S. Geological Survey topographic map on which the well is located. This is the 7.5 minute quadrangle topographic map from the USGS.

RDBMS Relational Database Management System

Referential integrity Concept used to ensure parent/child relationships in a database are maintained.

Significant Well Subjective determination on some wells. In Pennsylvania each county has been assigned a depth and any wells that are greater than that depth are considered significant wells. This is typically Marcellus or intended Marcellus wells. CBM wells are also considered atypical wells but they are not considered significant wells.

SQL Server Relational Database Management System (RDBMS) developed by Microsoft and used for the storage and management of data.

Stimulation Well intervention performed on an oil or gas well to increase production by improving the flow of hydrocarbons from the drainage area into the well bore (hydraulic fracturing is one method of stimulation).

Stratigraphy Discipline within the field of geology that studies the arrangement of rock strata, especially as to geographic position and chronologic order of sequence.

Surface Hole Location on the surface where the drilling originates.

TD Formation Geologic formation at the total depth of the well.

TIFF Tagged Image File Format

Well Completion Report Report prepared when the well drilling has been completed. These are completed for oil, gas and water wells; however, the information varies depending on the type of well. For oil/gas wells, it records the perforation, stimulation, and initial production data.

Well Number For oil/gas wells, it is the lease number assigned to the well. For water wells, it is the unique number assigned by the well driller.

WIS Wells Information System



1.3 References

Reference that provides information on the Wells Data Gap Analysis project includes:

The TreCom Systems Group Statement of Work dated July 6, 2010.

2. Gap Analysis Process

The process used to complete the Gap Analysis project was iterative in nature. The team was tasked with learning about WIS, PA*IRIS, PaGWIS, WebDriller, and OGAPS in a relatively short period of time while also learning the oil, gas, and water drilling business and the geology associated with well drilling. As such the project began with the team learning the basics of well drilling by seeking resources internal and external to the Bureau. After having initial information gathering sessions with key resources, the Business Analyst scheduled interviews to conduct the in-depth discussions related to the systems. These interviews were segmented based on the type of wells involved. The geologists and staff of the Carbon Sequestration Section (Pittsburgh) were interviewed to discuss their usage of WIS and PA*IRIS. The hydrogeologists of DCNR (Middletown) were interviewed to discuss their usage of PaGWIS and WebDriller. The staff of DCNR’s BIT was interviewed to discuss the specifics of OGAPS. After conducting these interviews, each system was used by the Business Analyst and closely evaluated to ensure an understanding of how the system functioned and to identify any deficiencies not already noted during the interviews. During this inspection, the subject matter experts were consulted to answer specific questions and to clarify the processes and functionality.

Follow-on meetings were conducted with other members of the Bureau’s staff to discuss additional uses of the systems and to ensure the completeness and comprehensiveness of the information gathered. An Industry Focus Group meeting was conducted in Pittsburgh to meet with industry representatives and discuss their usage of WIS and PA*IRIS. Additional meetings were also conducted with the staff in Pittsburgh to answer any remaining questions.

While the Business Analyst was conducting interviews with the subject matter experts, the Data Analyst was reviewing the databases for each of the systems. The data models were reviewed and a data dictionary spreadsheet was assembled, which includes all of the tables with all of the fields and their data types and lengths, where applicable. This information was used as the basis for analyzing the data stored in the tables to identify data redundancies and other issues. A series of queries were executed on the databases to look at row counts, unique data values, etc. To supplement the data analysis activities, interviews with technical resources were conducted.

3. Functionality Analysis

3.1 WIS

3.1.1 Purpose

DEP is the regulatory agency in the Commonwealth responsible for monitoring and inspecting the activities of oil/gas well operators. On the other hand, DCNR is responsible for recording and tracking the geology and geologic resources in the Commonwealth. Therefore, the information provided to DEP on oil/gas wells is of the utmost importance to the Bureau because of the geologic information provided, but the Bureau is dependent on DEP to share the information. This encompasses providing hard copy documents to DCNR as well as data through an interface from DEP’s Environment, Facility, Application, Compliance Tracking



System (eFACTS) to the Wells Information System (WIS). WIS is the comprehensive tracking system developed by the Bureau for oil/gas well records.

The staff of the Carbon Sequestration Section is responsible for the input and maintenance of the data in WIS. They enter, revise, and interpret data received on Location Plats, Well Completion Reports, Geophysical Logs, and Plugging Certificates. Operators are required to provide location plats with their permit applications to DEP. The permit information is entered by DEP into eFACTS and the data interface sends the information to WIS. (DCNR does not receive the permit application). The location plat is sent from DEP to DCNR so that it can be scanned and stored in OnBase, the enterprise content management system in use by the Bureau. In addition the location information received in WIS from eFACTS is reviewed and the decimal latitude and longitude is computed. Upon completion of the well, the operator is responsible for submitting a Well Completion Report to DEP. DEP conducts an inspection and approves the Well Completion Report, after which the report is sent to DCNR for scanning into OnBase. Once the Well Completion Report is scanned, it is given to a geologist for identification of key geologic information. Using the information provided, the staff determines the rock formations involved in the well including the formations the well was drilled through (interpreted stratigraphy) as well as the total depth and producing formations. Well Completion Reports for significant wells (Marcellus shale or other deep wells) are given to the Section Chief for review. The rest of the wells are evenly distributed amongst the geologists on staff in Pittsburgh. Operators are responsible for supplying Geophysical Logs to DEP. These logs are supplied to DCNR in either paper or digital formats. If provided as paper logs, they are scanned using a NeuraScanner to create a .TIFF file that is uploaded to the Nrwis00 Server (for internal DCNR use) and an FTP site (for use by PA*IRIS subscribers). The file paths for the Logs themselves are recorded in WIS for accounting purposes and for quick access by Pittsburgh staff through the Inquire Wells screen of WIS. If provided as digital .TIFF and/or LAS files, no scanning is needed, so the logs can be immediately uploaded and entered into the system. During the life of the well, the operator must supply production information for the well which is stored in WIS, and the history of all production of the well is available in WIS. When a well has been plugged and abandoned, the operator must submit a Plugging Certificate to DEP that also must be approved. The Plugging Certificate is then sent to DCNR so that the document can be scanned and the plugging date can be entered into WIS.

WIS is an Oracle Forms application that was completed in 1995 and upgraded to Oracle Forms 6i in 2002. The database used to store the data for the application is an Oracle 9i database. The application, when originally built, was based on a pre-existing ENABLE database used by the Bureau.

3.1.2 Functionality

WIS is an application built using Oracle Forms 6i for the user interface and an Oracle database for data storage. As such the application is a series of forms that are connected together. As explained above, the data transfer from eFACTS provides permit application data to WIS as well as operator information. The hard copy documents are also provided to the Bureau’s office in Pittsburgh so that the information can be verified and the geologists can review and interpret the geological information available from these documents. Many of the forms that comprise WIS are equivalent to the documents provided to the Bureau. There are forms for Location Plat, Completion Report, Geophysical Log, and Plugging Certificate. In addition to these forms are forms used for production information, the Stratigraphic Interpretation form, and forms used to maintain the data stored in lookup tables.

For the staff in Pittsburgh, WIS is accessible directly via their workstations. For all other users including DCNR staff located in Middletown or Harrisburg, WIS is accessible via Citrix



Metaframe. Citrix Metaframe is an application virtualization/delivery product that allows applications to be used regardless of the hardware and software in use by the user. WIS does include role based security which affects the forms to which the user has access. This is covered in greater detail later in this section.

Regardless of the role the user has in the application, the menu and shortcut icons are consistent. Below is a screenshot of the menu options and shortcut icons available in WIS.

Figure 1. WIS menu bar

The menu includes: Action, Edit, Block, Field, Record, Query, Application, Window, and Help. The menu options available for Action are Clear All, Save, Print, and Exit. The menu options available for Edit are Cut, Copy, Paste, and Edit. The menu options available for Block are Previous, Next, and Clear. The menu options available for Field are Previous, Next, Clear, and Duplicate. The menu options for Record are Previous, Next, Scroll up, Scroll down, Clear, Remove, Insert, Duplicate, and Lock. The menu options for Query are Enter, Execute, Last Criteria, Cancel, Count hits, and Fetch next set. The menu options for Application are DEO, DRF, GEO, BOGM, IDU, SCO, Adm, Public, and Show Keys. These options vary depending on the role the user has in the system. The menu options for Window are Cascade, Tile and Arrange Icons. The menu options for Help are Help, Keys, List, Display error and Debug. During usage of the system, the Help option for Help did not function. In the interviews conducted with the user community, the Block, Field, and Record menus were identified as not being used. The key menu option used by the users is the Application menu which allows the user access to the forms available to that user based on the role assigned.

Oracle Forms utilizes a number of keyboard shortcuts. These shortcuts are displayed to the user when using the Show Keys option.

Figure 2. WIS Show Keys

The shortcut buttons in order of appearance are Save, Print, Clear Form, Find, Insert, Remove, Clear Record, List, Edit, Help, Enter Query, Execute Query, Count Query, Cancel Query, Next Record, Previous Record, and Exit Form. These shortcut icons are consistently used and it should be noted that Next Record and Previous Record are used because they allow the user to “scroll” through the results returned from a query. This interface does not return query results in a list fashion that would allow the user to open and view the record; therefore, the ability to go from one record to the next is required.

The key piece of data in WIS is the well permit number, which is an unique number assigned to a well by the DEP. The number in use by the DEP today is a form of the American Petroleum Institute’s (API) numbering scheme. The API started this global numeric system in 1967 and



asked the governing bodies to be in charge of assigning the numbers, but Pennsylvania chose not to and charged Petroleum Information with this task instead. Petroleum Information was acquired several times and is now part of IHS. By definition the API Number is a unique 14-digit number assigned to a well when a permit is issued. The format is SS-CCC-NNNNN-KKKK where S is the 2 digit state code, C is the 3 digit FIPS county code, N is the 5 digit unique sequential number, and K is the 4 digit number for each sidetrack. The well permit number used in the Commonwealth that is used in WIS is CCC-NNNNN where C is the 3 digit FIPS county code, and N is the 5 digit unique sequential number. Technically, the full API number is not being used.

The permit number in use today has a long history. Wells from 1956 – 1974 used a permit number that consisted of an abbreviation for the county and a sequential number. In 1974, it was decided to adopt the API numbering format. To do this, all of the wells from 1956 – 1974 retained the county abbreviation, but 20000 was added to the pre-existing unique sequential number. For example, permit IND-432 became IND-20432. The numbering of new wells as of 1974 started with the next number in sequence after all the existing numbers were converted to their 20000 series number. In 1984 a new oil and gas act was passed, and the county abbreviation was replaced with the FIPS county code. This is the format still in use today as described above.

For all of the historical wells prior to 1956, the records were tracked in a three-ring binder and the numbering was split for shallow and deep wells by quadrangle. When these wells were entered into the predecessor of WIS (an ENABLE database), the wells were assigned a 90000 series number because the system required a 5 digit permit number. These numbers were then converted to the permit numbers used in WIS and the 3 digit county code was added. Many of these historical wells are now being registered with DEP. The Well Registration Form is sent to the Bureau and the geologists must determine if the newly registered well is an historical well that may already have a record in WIS with a 90000 series number. If the well does already exist in WIS, then that data must be transferred to the newly registered well created in the system by the eFACTS data transfer with the new permit number.

Location Plats (WIS0420)

This form is the beginning point of the existence of a well in WIS. The well must have a location plat in order for any additional information to be entered. Much of the information on this form is populated with data provided by the operator on the Application Permit that is submitted to DEP. The data entered by DEP into eFACTS is then transferred to WIS on a nightly basis.

A location plat is completed by an operator and submitted along with their permit application. A well may have more than one location plat; a proposed and final location plat. It provides information about the location of the well including surface hole true latitude and longitude as well as offset information. Some location plats also include bottom hole true latitude and longitude; however, this information cannot presently be stored in WIS. The operator typically indicates the datum used for these latitude and longitude coordinates.

Until recently, the NAD 27 datum was the standard of the Commonwealth; however, DEP has migrated to the NAD 83 datum within the last several months. As of the writing of this document, the legacy (pre-March 2010) location data in WIS, which includes three types - reference latitude/longitude values and corresponding offset footages, true latitude/longitude values (degree, minute, second), and decimal latitude/longitude data, are stored in the NAD 27 datum. Data received since March of this year represent a combination of both NAD 27 and NAD 83 datums. As an example, the decimal latitude/longitude data, used by the Bureau for its digital mapping, remains in the NAD 27 datum, whereas true latitude/longitude values come into WIS from eFACTs in the NAD 83 datum. The archival and maintenance of three different types



of location data, as well as the lag time in migrating the WIS location data to the NAD 83 datum, have introduced much confusion and frustration on the part of Bureau staff as well as the PA*IRIS subscribers.

Figure 3. WIS Location Plat

Completion Report (WIS0450)

The Completion Report form is used to record the information submitted on the Well Completion Report by the driller/operator once a well has been completed. This Report must be submitted within 30 days of the completion of a well and is often referred to as the well record. Because of the subjective nature of the term “completed”, this report can be submitted at various times depending on the scheduling of the drilling and when the perforation/stimulation occurs. Some drillers/operators submit interim completion reports; therefore, a well can have multiple completion reports. The completion reports are submitted to DEP regional offices in Meadville, Pittsburgh, or Williamsport for approval. Once processed by DEP, these forms are sent to the Bureau’s Pittsburgh office, where they are scanned and given to a geologist for interpretation. This includes determining the total depth formation, the field, the pool, and the stratigraphic interpretation. Also, the well is spotted on a map.

Completion Reports are also completed for other drilling events including when a well is deepened or when a well is plugged back. All of these completion reports are recorded in WIS.



The Completion Report form in WIS is comprised of several screens. There is a screen that includes the information provided on the permit (Permit Details) from which the user navigates to the Completion Report form itself. Most of the information on these two screens comes from the eFACTS transfer; however, the data is verified and additional data is entered as necessary.

Figure 4. WIS Completion Report

Figure 5. WIS Completion Report, screen 2

The third screen of the Completion Report form is used by the geologists to record the producing formation data as well as the perforations and stimulations. The data stored with



respect to perforations and stimulations is the intervals at which these were conducted. No information regarding the sand and water used in the stimulation can be entered.

Figure 6. WIS Completion Report, screen 3

The last screen that comprises the Completion Report is the screen where the information from the driller’s log can be entered. The specificity of information on the driller’s log varies from well to well depending on whether or not a geologist was on site to provide the information. Regardless, this information is utilized by Bureau geologists to interpret the stratigraphy.

Figure 7. WIS Completion Report, Driller’s Log



Modify Wells (WIS0570)

Accessibility to this form depends on the user’s role, and depending on the role, the usage of this form will vary. It is a two-page form that is only accessible to a small user audience. Presently this form may be used by the geologists to edit the location information specific to the well as well as field and pool names, total depth formations, etc. If the location information is changed, the original location information is not changed. The new information is considered a second location. The depth can also change over the life of a well as the well may be deepened or plugged back. WIS allows the initial depth, the current depth, and the total depth to be maintained. The completion reports are necessary to be consulted as the various completion events change the depth of the well, and the information is recorded on that form.

Figure 8. WIS Modify Well Details

Figure 9. WIS Modify Well Details, screen 2



Stratigraphic Interpretations (WIS0020)

This form is used by the geologists to record the geological formations the well has penetrated. Upon receipt of the Well Completion Report by DCNR, it is scanned into OnBase, and the data is verified by the administrative staff to ensure the location information is correct and to enter the driller’s log. After this is complete, the Well Completion Reports are distributed to the geologists so that they can complete the geological analysis on the well. The distribution of the Well Completion Reports is a manual process; no system workflow is used. The Bureau geologists use the driller’s log, the known geology in the well’s location, geophysical logs (if any), and rock samples to complete the Stratigraphic Interpretations form.

The form records who completed the interpretation, when the interpretation was completed, and the intervals associated with each formation.

Figure 10. WIS Stratigraphic Interpretations

Note: The Driller’s Log is accessible from the Completion Report as well as the Stratigraphic Interpretations form.



Geophysical Log (WIS0490)

The Geophysical Log form is used to record information about the receipt of geophysical logs by DCNR. This includes information about the type of geophysical log, when it was received, and whether it is considered confidential. By mandate, geophysical logs are now to be submitted to DEP electronically, but even now, most geophysical logs have been submitted on paper. The Bureau has a NeuraScanner which is equipped to scan the geophysical logs and create electronic files so that these electronic files can be used in other systems. The geophysical logs themselves are available to external users through the FTP site that is part of PA*IRIS (Refer to Section 3.2.2 for further information). A file location is stored on this form; however, this location is for internal DCNR use only, to track which permits have geophysical logs associated with them, and to provide a quick link to Bureau staff for viewing these logs.

Figure 11. WIS Geophysical Log



Plugging Certificate (WIS0452)

The Plugging Certificate form captures information about any wells that have been plugged. The Plugging Certificate is submitted to DEP and the hard copy is then sent to DCNR. The completion event on the form is completed by the transfer of information from eFACTS; however, this causes an issue with scanning the plugging certificate. The scanning workflow software will not allow the plugging certificate to be scanned until the completion event is removed. To get around this issue, the administrative staff remove the completion event from the form, save the plugging certificate, scan the plugging certificate into OnBase, and then return to WIS to enter the completion event and the date of plugging.

Figure 12. WIS Plugging Certificate



Record Annual Production Reports – BOGM (YIS3010)

This form is used to record the production information submitted by the oil/gas well operators. Operators can submit their production information on paper forms or via an online application called the Oil and Gas Annual Production System (OGAPS). Refer to Section 3.5 of this document for further information on OGAPS. The Record Annual Production Reports form is accessible by the personnel at DEP so that when a paper production report is received, they have the ability to enter the information in WIS. The top of the form records the operator submitting the information, the middle of the form records all of the wells for which the operator is submitting production information (by permit number), and the bottom records the production data for each of the wells.

Figure 13. WIS Record Annual Production Reports

If the user enters a type of waste on the first screen that comprises the form, then the user will have to navigate to page 2 to provide additional information about the waste disposal. Note: The Page 2 navigation button appears on the first screen regardless, and if the user enters a non-waste product and clicks on the button, nothing happens.




This form is the data entry point for production data not supplied by OGAPS. As such it is temporary. The information is received “as is” and is stored in a separate location from the “final” production data. Once the data is entered on this form, it is checked for errors and a number of business rules are applied to the data prior to moving the data to its permanent storage location in the database. Some of these error checks include ensuring that the permit number is valid and that the same operator has not submitted production data for a well more than once. If there are errors encountered during this process, then an error code is checked and the Filter Production Data form is used to clean up the errors.

Filter Production Data (YIS3030)

This form allows the user to view the production records that generated errors in the export from the Record Annual Production Reports form to the permanent storage location in WIS and correct those errors. This form is used by the staff at the Bureau to quality control the production data and to research the errors in order to correct them. This form can be queried with the production year and/or the oil and gas operator. The information on this page displays the operator and well from the production report with that on the location plat. This is the reason for the two lines of data for each well displayed. Beside the permit number, farm name and serial number columns, there is a blank box. This box is used to record the error that has been found. If the box next to the permit number has a value in it, then the permit number is causing the error. If the box next to the farm name has a value in it, then the farm name is causing the error. And if the box next to the serial number has a value in it, then the serial number is causing the error. The values that display in these boxes correspond to the error types possible.

Permit Number value of 1: API not in proper format. This means that the permit number is not made up of the 3 digit county code and the 5 digit unique sequence number.

Permit Number value of 2: API not present in inventory. This means the permit number is not found in the location plats stored in the system.

Permit Number value of 3: Permit registration status not valid. Production has been reported for a well that has been cancelled, expired or is void.

Permit Number value of 4: Well not reported driller. This means the permit number was submitted on a location plat, but a well completion report does not exist in the system.

Farm Name or Serial Number value of 1: The information stored on the permit number submitted on the production report is compared to the information already stored in the system for that well. If the farm name doesn’t match, then the serial number is compared. If neither matches, then the well is flagged with this error.



At the bottom of the form are navigation buttons that provide easy access for the users to the various forms in the system that can be used to research what may be causing the error and to correct the errors. Once the corrections are made, the data is checked again and assuming it passes the error checks, it will be transferred to the permanent storage location in WIS.

Figure 15. WIS Filter Production Data

Export, Delete, or Set Error Flags on Production Data (YIS3050)

This form allows the users with access to it to execute the data export of the production data that was flagged with errors and has since been corrected.

Figure 16. Export, Delete, or Set Error Flags on Production Data



Record Annual Production Reports (WIS0520)

This form provides access to the production data that has been transferred to the permanent storage location for production information in WIS. This includes the production reports submitted through OGAPS. The data is associated with the operator, but once the operator is located, all of the wells for which that operator has submitted production data are displayed. The production data for each well is then listed at the bottom of the form, once the well is selected. During the export process, some production information is aggregated and a group is created. This is a common link between wells that produce into a common tank or through a common meter. The production can then be averaged across all wells in the group.




Pending Logs Request Letters (WIS0630)

This form is titled Log Requests in WIS and is used to track the letters that are sent requesting geophysical logs. The Oil and Gas Act requires that geophysical logs be requested within 90 days of the completion or recompletion of a well. This form is also used to track the confidentiality status of the geophysical logs. This functionality is no longer used. The most recent request date stored in the database is 09/22/1999.

Figure 18. WIS Pending Logs Request Letters

Rock Samples (WIS0550)

When working with WIS to complete this project, the functionality for Rock Samples was not able to be accessed. An error message is returned: “FRM-40911: Record not created due to sequence number generation error.” The table that this form accesses contains only one record which is the following:

ID NUMBER(6,0) 5 WELL_ID NUMBER(6,0) 29923 SAMPLE_TYPE VARCHAR2(1 BYTE) T COLLECTION_DATE DATE null NO_BOX NUMBER(2,0) Null FROM_RACK NUMBER(3,0) Null FROM_SHELF VARCHAR2(1 BYTE) Null TO_RACK NUMBER(3,0) Null TO_SHELF VARCHAR2(1 BYTE) Null TECHNICAL_REMARK VARCHAR2(100 BYTE) Null STORAGE_REMARK VARCHAR2(100 BYTE) Null

This record is populated with null values which would indicate that the need for this record and this functionality is nonexistent. DCNR has supplied our team with a spreadsheet that is used to track the rock samples received.

Inquire Well Details (WIS0670)

This form is available to all users of WIS. It allows the user to search for a well in the system, and any of the fields available on the form can be used in the search. Partial searches are possible by using the percentage sign wildcard (%). After searching for a well using the Inquire Well Details form, the form displays several buttons: Completion Reports, Plug Certificates,



Strats, Logs, Prods, and Samples. Beside each button is a number. This number corresponds to the number of records of each category that are available in the system. By clicking the Completion Reports button, the user sees the Completion Reports forms documented above, but they are read only. By clicking the Plug Certificates button, the user sees the Plugging Certificates form documented above, and the form is also read only. The Strats button navigates the user to the Stratigraphic Interpretations form, the Logs button navigates the user to the Geophysical Logs form, and the Samples button causes the same error noted above for Rock Samples. The Prods button navigates the user to the Inquire Production form which is documented in the next section.

Figure 19. WIS Inquire Well Details



Inquire Productions (WIS0675)

The Inquire Productions page allows the user to view the production history of a well. This form is accessible from the Inquire Well Details form by clicking the Prods button. It provides the production information for the well up to the most current year which is provided through the production functionality detailed above.

Figure 20. WIS Inquire Productions

The other forms used in WIS are used to maintain the lookup tables used throughout WIS. Some of these lookup tables are maintainable by the geologists and administrative staff at DCNR, but the majority of the lookup tables can only be updated by the System Administrator. This section provides screenshots of each of the forms used to update the lookup tables. For information about the construction of the tables themselves, refer to Section 4.1 regarding data.

General Classes (WIS0040): This value is used on the Completion Report form and is used to group large numbers of wells having general similarities (Producing, Non-Producing and Service).

Status (WIS0050): This value is used to report on the status of a well on the Location Plat form and can be used to search for a well on the Inquire Wells form.

The form could not be displayed in WIS. The following error message is returned: FRM-40911: Record not created due to sequence number generation error.



Well Types (WIS0060): This value is used on the Completion Report form and is dependent on the General Class value. This form allows the user to create the association between the General Class and the Well Type.

Special Classes and Exploratory Types (WIS0070): This value is used on the Completion Report Form and is also dependent on the General Class value. The Special Class allows the well to be identified as an exploratory or development well.

Well ID Types (WIS0090): This value is used to differentiate between permitted and non-permitted wells. Using this value, the user can quickly identify historical wells.

The form could not be displayed in WIS. The following error message is returned: FRM-40911: Record not created due to sequence number generation error.



Fields (WIS0100): This value corresponds to the geographic areas in the Commonwealth that produce oil or gas and is used on the Completion Report form. Fields and pools are related.

Pools (WIS0110): A pool is a reservoir within a field; therefore, this form requires the relationship between field and pool to be created. This value is used on the Completion Report form. It should be noted that the first pool discovered in a given field is identified as “Unnamed.”



Rock Units (WIS0120): This value is used to denote the sections of rock within a geologic record with a formal name. They could be individual beds, formations, or groups. The Type used on this form indicates the category: 1 – Supergroup, 2 – Group, 3 – Formation, 4 – Member, 5 – Bed.

Completion Event Types (WIS0130): This value is used on the Plugging Certificate form and the Completion Report form. It is used to denote the variety of events that can occur to a well.

Formation Aliases (WIS0140): This is a name that is not an official rock unit and could be used by a driller on the driller’s log. Prior to being able to enter the values on the driller’s log in WIS, the formation must exist here.



Clients (WIS0230): This is the lookup table that stores the information about the oil and gas operator including address and contact information.

Products (WIS0240): This is the lookup table that stores the types of products that can be produced by an oil/gas well.

US Counties (WIS0150): This table stores the counties that comprise the Commonwealth as well as the FIPS code for the county.



County Municipality Cross Reference (WIS0160): This form allows the user to maintain the relationship between the counties and the municipalities in those counties. The county and municipality must exist before creating the relationship.

US Municipalities (WIS0170): This form allows the user to maintain the municipalities in the Commonwealth.

Interpreters (WIS0180): This form access the lookup table that stores the names of the geologists that complete Stratigraphic Interpretations.



Log Types (WIS0190): This form allows the user to maintain the types of geophysical logs.

Elevation Types (WIS0200): This form allows the user to maintain the elevation types that can be used in WIS.

Units of Measure (WIS0210): This form allows the user to maintain the units of measure values that are used throughout WIS.



Quadrangle Maps (WIS0220): This form allows the user to maintain the quadrangle maps available for the Commonwealth. The Commonwealth uses 7.5 minute quadrangles.

Waste Disposal Methods (YIS3020): This form is used to maintain the values available to the user for waste disposal methods when entering production data.

Reports in WIS

There are several reports available within WIS. They are:

Error List (YIS3045)

Well Details (Oracle report number is unknown)

Exploratory versus Development Success (WIS0315)

Completion by Geologic Age (WIS0330)

Field Production Report (WIS0340)

Exploratory and Development Drilling (WIS0370)

New Wells (WIS0260)

These are all options that are available to the user in the Application menu sub-options depending on the role assigned to the user. In addition to these reports, there is also an option for Discoverer reports which does not work. Oracle Discoverer has been used as a custom



reporting engine to develop other types of reports. At one time the intent was to allow the user to navigate directly from WIS to Oracle Discoverer, but the thought is that this was never completed which is why the option doesn’t work. The Well Details report also does not work. After selecting the option in the menu, the system seems to attempt to complete the request, but nothing is displayed on the screen. In interviewing the subject matter experts, the only report that is being used is the Error List. This report generates a list of the errors identified in the production data. These are the errors that are identified when the production data that is submitted is error checked prior to being moved to the permanent storage location for production data.

Roles in WIS

The functionality available in WIS is dependent on the role the user has in the system. The roles include:

GEO – Geologist. This role is used by the geologists on staff with the Bureau.

DEO – Data Entry Operator. This role is used by the administrative staff and selected geologists with the Bureau.

DRF – Draftsmen. This role was used by the Geographic Information System (GIS) Specialist who was responsible for plotting the wells on the GIS map. This position has been phased out and the responsibility of plotting the wells on the maps is now undertaken by the geologists. Therefore, this role is no longer used in WIS.

BOGM – Bureau of Oil and Gas Management. This role is used by DEP users to enter production information into WIS when production reports are submitted on paper.

IDU – Interdepartmental users. The usage of this role by the staff at the Bureau is unknown.

CLN – Clients. This role is used for the external subscribers who have access to WIS through PA*IRIS.

SCO – Statistical Data Coordinator. The usage of this role by the staff at the Bureau is unknown.

ADM – Database Administrator. This role is used by the System Administrators who need access to the lookup tables and can edit the values in those tables through WIS. This role has broad-based access to WIS to provide the necessary support to the user community.

WIS uses role-based security where each role dictates the forms and reports the user may access. The following matrix provides the specifics on which role has access to which form. The options that are available to the user in the Application menu equate to the forms the users have access to given their role. The naming of these options is slightly different than some of the names used on the forms. Therefore, the matrix includes a column with the official form name as well as the menu option that appears. Each of the roles is listed at the top of the matrix.

Oracle Forms Menu option in WIS

DEO GEO DRF BOGM SCO ADM (codes)

ADM (misc)

Public IDU

Location Plats Location plat X X

Completion Reports

Completion rpts

X X X

Plugging Certificate

Plugging certif X X





ADM (misc)

Public IDU

Geophysical Logs

Geophysical log

X X

Log Requests Log requests X X

Filter Production Data

Filter prods X X X

Annual Production Report (BOGM)

Production bogm

X X

Record Annual Production Reports

Production btgs

X X

Rock Sample Storage Inventory

Rock samples X X X

Inquire Well Details

Inquire wells X X X X X X X

Modify Well Details

Modify location X

Stratigraphic Interpretations

Stratigraphy X X

Inquire Well Formations

Well formations

X X X

Modify Well Details

Modify wells X X

Fields Fields X X X disabled

Pools Pools X disabled X disabled

Rock Units Rock units X disabled X disabled X

Drillers Formation Alias

Formation alias

X disabled X disabled X

Clients Clients X X disabled X disabled

Unknown Set log dates error

Export, Delete, Set Flags

Export prods X

Products Products disabled X disabled

General Classes General classes

disabled X disabled

Special Class Special classes

disabled X disabled

Exploratory Types

Expl types disabled disabled

Well Types Well types disabled X disabled

Well ID Types Well id types disabled error disabled

Statuses Statuses disabled error disabled

Completion Event Types

Compl events disabled X disabled

Interpreters Interpreters disabled X disabled

US Counties Counties disabled X disabled

US Municipalities

Municipalities disabled X disabled

County Municipality Cross Reference

Countymunixrefs

disabled X disabled

Quadrangle Maps

Quadrangles disabled X disabled

Log Types Log types disabled X disabled





ADM (misc)

Public IDU

Elevation Types Elevation types disabled X disabled

Units of Measure Unit of measure

disabled X disabled

Disposal Methods

Waste disposal X

Note: Set Log Dates is an option in the menu for the user; however, this option causes an error. This form may not exist in the system.

Oracle Report Menu option in WIS


ADM (misc)

Public IDU

Error List Error list X X X

Unknown Well Details X X X X X

Not Applicable Discoverer Reports

X X X X X X

Development versus Exploratory Success

Exploratory vs Development Success

X X

Completion by Geologic Age

Completion by Age

X X

Field Production Report

Field Production

X X

Exploratory and Development Drilling

Exploratory and development drilling

X X

New Wells New wells X

In addition to the Oracle Forms application, WIS also includes mapping functionality which is referred to as Base Maps. The Base Maps functionality is supported by ArcGIS. These maps were used to electronically plot the wells on the quadrangle maps. Presently, this functionality is not working, and the wells must be plotted onto quadrangle maps by hand. The quadrangle maps being used are the 7.5 minute USGS quadrangle maps from 2005. If the well to be plotted is in a quadrangle in which no other wells are plotted, a USGS quadrangle map from 2005 must be printed. The fields and pools are plotted on Mylar®, which can then be overlaid onto the maps.

3.1.3 Architecture

Refer to Section 3.2.3 for the architecture information for WIS.

3.1.4 Deficiencies

This section identifies the results of the analysis conducted on the functionality available in WIS. This information is based on the results of the analysis conducted by the team as well as information provided to the team by the subject matter experts and the industry focus group.

There is additional information available for oil/gas wells that cannot be entered and stored in WIS. The following are the data elements that were identified during the course of the project as being needed in the new system: API number – this is the 14 digit number used for oil/gas wells. The permit number used

by the Commonwealth doesn’t include the last 4 digits of the API which provide a level of specificity when dealing with directional/horizontal wells.

The Commonwealth technically doesn’t use the API numbering system. This causes a conflict in the well numbers for many of the wells in WIS, particularly



the pre-1956 wells. In addition, IHS convention regarding re-entry wells (those that have been redrilled or drilled deeper) is to assign new numbers rather than using pre-existing numbers. Also, IHS often assigns new numbers for plugged wells instead of using the pre-existing number. Therefore, the likelihood of a well number in WIS matching the master well number retained by IHS using the formal API system is reduced. Also, there is a possibility that the same well has multiple API numbers assigned to it.

Target depth formation – this data is required on the permit application with DEP, but it cannot be stored in WIS. Although the data submitted by the operator may be suspect, this data should be included.

Angle and course of deviation – this is another data field on the location plat that cannot be stored in WIS. The type of data that may appear in this field varies, depending on operator and circumstance. Some indicate the direction of the deviated drilling in azimuth values (0 to 360 degrees), while others use quadrant method (e.g., N 30 degrees E). The length of the drilling “leg” is then generally provided in feet. Although final X-Y-Z coordinates (see below) for a completed deviated well would be preferable, the angle and course of deviation can be used to approximate the subsurface location of deviated well tracks in lieu of receiving a certified directional survey report.

Bottom hole location coordinates – presently the system allows the storage of surface hole coordinates. However, with the number of directional and horizontal wells being drilled in the Commonwealth, the location coordinates of the bottom hole are important.

X-Y-Z coordinates – with directional wells, these coordinates are included in a directional survey report provided by the operator at the completion of drilling activities, and provide a 3D location of the borehole. The expectation would be that the system should provide the ability to record multiple sets of X-Y-Z coordinates.

NAD 27 and NAD 83 coordinates – presently the legacy latitude and longitude information and all decimal latitude/longitude data stored in WIS uses the NAD 27 datum; newer data has been reported inconsistently in both datums. All of these data must be converted to the NAD 83 datum, and to avoid confusion moving forward, it would be preferable to use one particular type of location data in the system (whether offset-footage-based data, true latitude/longitude values, or decimal latitude/longitude values). Ideally, these latitude and longitude data should be available in both NAD 27 and NAD 83 datums.

True Vertical Depth – currently WIS stores a total depth (TD). At present, the total measured depth of the well is entered in this field. However, with directional and horizontal wells, the total measured depth is different from the true vertical depth. Therefore, an additional field is needed.

Stimulation engineering data – the information provided on the well completion report for the fluid and propping agent used for each interval and the average injection cannot be recorded in WIS.

Casing engineering data – the information provided on the well completion report for the casing used in the borehole cannot be stored in WIS.

Formation data for the perforation and stimulation intervals – presently the system allows the tops and bottoms of the perforation and stimulation intervals, but the formation names for those intervals cannot be recorded.

Deviated well flag – ideally those wells that are deviated wells should be flagged in the system for easy identification.

In WIS there is an Oracle Form for Rock Samples. Presently, this form is not used. Instead a spreadsheet is used to track the rock samples received by the Bureau. The usage of this



functionality should be evaluated to determine if it should or shouldn’t be included in the new application.

Presently the Base Maps functionality is not available. Therefore, there is no map functionality available within WIS to plot wells on a topographic quadrangle map. Moving forward, a mapping solution must be capable of layers because there are quadrangles with many wells, and the well labels may overlap or conflict.

For the historical wells that have been recorded in WIS with a permit number where the sequential number is 90000 or higher, and a subsequent well registration is received, DCNR requires functionality that will allow them to easily move the information stored for the record with the 90000 series permit number to the new permit number received in the system from eFACTS as a result of the registration.

The location information provided on the location plat provides the true latitude/longitude and the offset information. It doesn’t include the decimal latitude and longitude. WIS is supposed to execute this conversion automatically, but this often does not happen. In a new system, the decimal conversion should occur automatically.

Location information in WIS is presently tracked using three different values: true latitude/longitude, decimal latitude/longitude, and reference latitude/longitude values and corresponding offset footages. The system should be evaluated and possibly only one type of location data should be tracked.

The security model in use for WIS requires that a user be assigned a database account. The security model used in the new system should provide the ability to manage users from the system itself and should not require the Administrators to have access to the database.

The new system should take into consideration the reporting requirements for CBM wells. Presently, the information from WIS is extracted and imported into a separate Access database. Additional data is entered in the Access database and further manipulation of the data is undertaken.

Presently the field name for the well populates in multiple locations. At times this information is not accurate, and it is difficult to make the change and have all fields update appropriately.

The driller’s date is a required field, but this is not always known. A fictitious date (01/01/1901) is entered and a series of steps is required to change it when the correct date is learned.

WIS is a rigid system that requires execution for certain tasks to be in a certain order. It is often not intuitive and requires documentation detailing all of the steps to be taken. Instead of using dynamic screens that incorporate the business rules, the user must understand the business rules so that the system is executed in the proper order.

The Bureau uses IHS-PETRA ® to do petrophysical analysis of the data from WIS. This requires that the data be exported from WIS to Excel. Once in Excel the data is converted to a comma delimited file so that it can be imported using PETRA®’s import wizard.

3.2 PA*IRIS

3.2.1 Purpose

The Pennsylvania Internet Record Imaging System (PA*IRIS) was completed in 1999 by the Bureau to allow online access to scanned images of Location Plats, Completion Reports,



Geophysical Logs, and Plugging Certificates. Several years later, PA*IRIS was expanded to also allow access to WIS. Therefore, PA*IRIS serves two purposes. The first is as a gateway for external subscribers and users to the functionality available to them, and the second is as the interface that allows users to access the images stored by DCNR for a well.

PA*IRIS is available to external users who subscribe to the service by paying a one-time subscription fee and an annual maintenance fee which is applied to the general fund for DCNR. Subscribers include local governments, operators and drillers, other government agencies, academia, etc. The number of subscribers to the service is approaching 300. In return, the users are given an account which allows them to log-in to PA*IRIS. Once the users have accessed PA*IRIS, they then have the ability to view the images of the scanned documents created by DCNR, the ability to access WIS to view well information, and the ability to view WIS Reports using Oracle Discoverer.

3.2.2 Functionality

When logging into PA*IRIS, navigating to www.pairis.state.pa.us will take the user to the following web page. The user enters their User name and Password. This is supplied to the user once the subscription fee has been paid and the user’s account has been set up.

Figure 21. PA*IRIS log-in

Upon successful completion of the user name and password, the user will be successfully logged in and will see the following page:

Figure 22. PA*IRIS home page

This page allows the user to access OnBase (PA*IRIS), WIS (WIS2002), and Oracle Discoverer (WIS_Reports). Citrix Metaframe is used to serve the applications to the user’s computer, and installation files are necessary prior to Citrix functioning on the user’s machine. Citrix Metaframe is an application virtualization/delivery product that allows applications to be used regardless of the hardware and software in use by the user.

To many of the subscribers, PA*IRIS is the system that allows them to view the scanned images stored by DCNR. When these users refer to PA*IRIS, they are referring to the images stored in OnBase. DCNR uses OnBase to provide enterprise content management. The images stored in OnBase can be accessed using the PA*IRIS interface documented above. This is considered

http://www.pairis.state.pa.us/



the Citrix version and is used by most of the subscribers when viewing the images; however, most subscribers are not able to print from this version of OnBase.

Figure 23. Citrix OnBase

The document types in this list that are first received by DEP include Completion Reports, Location Plats, and Plugging Certificates. Copies of these documents are then shipped to the DCNR office in Pittsburgh for scanning.

Copies of the original hard copy versions of Location Plats, Completion Reports, and Plugging Certificates are received at the Pittsburgh office of DCNR from DEP on a regular basis. The administrative staff processes these documents by scanning them using a high speed scanner and AnyDoc OCR software (from a dedicated computer running an earlier Windows operating system than that used by other Bureau staff). Using AnyDoc, the user indicates the type of document being scanned and the template for the document is loaded. The template is then used to highlight the sections of the scanned document where the user may find the information to be entered as keywords. Those keywords are stored in the OnBase database so that when the user uses OnBase, the keywords can be used in the search and the information is available for display.

The Completed Base Map Quadrangles and Quadrangle Section Map images stored in OnBase are needed by those subscribers who may not have their own mapping applications. The Completed Base Map Quadrangles is a map of all of the 7.5 minute quadrangle maps for the Commonwealth of Pennsylvania. The Quadrangle Section Map allows the user to print the topographical map for a quadrangle. The Historical Records allows the user to view historical records that have been scanned into OnBase. The Users Guide for PA*IRIS is also available for reference on how to use PA*IRIS.

The images stored in OnBase are also accessible through the web interface for OnBase. This is accessible at www.pairis.state.pa.us/dcnr. The functionality available from this website is the same as the functionality available through Citrix; however, images can be printed from the web. In order to use the web version, there are installation files that must be installed on the computer that will be accessing OnBase through the website instead of through Citrix.

http://www.pairis.state.pa.us/dcnr



Once the user has navigated to www.pairis.state.pa.us/dcnr, the following log-in screen displays:

Figure 24. Web OnBase log-in

The user uses the same User Name and Password that is used to log into PA*IRIS. Upon successful log-in, the user sees the following:

Figure 25. Web OnBase

The web version of OnBase provides the same functionality as the Citrix version; however, the interface is slightly different and the user has the ability to print the images. The images can be printed to .pdf files, and the user has the option to select the pages of the image to be printed.

In addition to the functionality for OnBase, subscribers to PA*IRIS also have access to WIS and to WIS Reporting. The icon for WIS that displays for the user once logged into PA*IRIS will take the user to the same functionality described in Section 3.1.2 for WIS. Depending on the user’s role, the access in WIS will vary. For subscribers, the role will be the Public role which restricts the user to viewing the information in WIS only. For other users within DCNR, the role may vary. Refer to the role matrix in Section 3.1.2 for further information.

The icon for WIS Reports takes the user to Oracle Discoverer. Oracle Discoverer is a business intelligence tool that provides the ability to do ad hoc queries and reporting. Oracle Discoverer is based on the concept of a workbook. Each workbook should be built to combine data to accomplish specific tasks. From that workbook the user can assemble the data needed in a specific report. In WIS, Oracle Discoverer has a workbook for each individual report.

http://www.pairis.state.pa.us/dcnr



The user must log into Oracle Discoverer after clicking the icon from PA*IRIS using their PA*IRIS username and password.

Figure 26. Oracle Discoverer log-in

Once logged in, the user opens a workbook from the database. These workbooks will vary depending on the user logged in, but each of these workbooks has been built to meet the need for a specific report.

Figure 27. Oracle Discoverer Workbook list

During the analysis conducted for the project, it was noted that there appeared to be many redundancies in the workbooks available. During the industry focus group meeting, the



following workbooks were identified as those that were used: MonthlyLogs.DIS, Marcellus Producing Wells.DIS, PAIRIS_Monthly Logs.DIS, Pairis Monthly Completion Reports.DIS, Monthly Plats.DIS, and Pairis New Location Plats.DIS.

Once the user selects the workbook, it displays in spreadsheet form.

Figure 28. Workbook Results

The Bureau’s Pittsburgh staff members have the ability to edit the worksheet to add data elements to the view of the data. However, this capability is driven by the workbook and the query that is being used to generate the workbook. This may result in the needed data not being available to the user. When the user edits the sheet, the user has the option to select columns from the tables included in the workbook. These tables are represented with folder icons in the interface and the columns available in the table display to the right side. If the table containing the necessary data element isn’t included in the workbook, then the user cannot edit the sheet to include that data element.

Figure 29. Edit Sheet

WIS Reports is most often used by the subscribers to extract the data from WIS so that it can be loaded in their own systems. The Bureau receives many requests for custom reports because the subscribers do not have the ability to create their own reports. These requests consume much of the staff’s time. The request needs to be interpreted to ensure that the data is available and then the report needs to be built.



PA*IRIS also includes the capability to view Geophysical Logs. Geophysical Logs may be received on paper or electronically. Presently, DEP is requiring that all geophysical logs be submitted electronically; however, if paper copies are received, DCNR scans them using a NeuraScanner. Once the NeuraScanner completes the scan, the .tiff files are saved to the county folders that exist on the NRWIS00 server. This is because the geophysical logs are stored by county and accessible via the FTP site by county. The files are also saved to the hard drive of the user’s machine. To publish the logs and make them accessible via the FTP site, the user must log into the Citrix side of WIS/PA*IRIS as an Administrator and copy the files from the hard drive of the user’s machine to the “R” drive on the Citrix machine. The files cannot be copied directly within the server as this generates an error. The geophysical logs are available through the following website: www.pairis.state.pa.us/ftp. After providing the same log-in credentials (User Name and Password) as required for all other PA*IRIS functionality, the user sees the following web page:

Figure 30. FTP site

By clicking on the Geophysical Logs folder, the user sees all of the geophysical logs available through the FTP site which are stored by county.

Figure 31. Geophysical Logs

http://www.pairis.state.pa.us/ftp



After the user selects a county, the geophysical logs for all of the wells available for that county are listed. The file name of each of the log files includes the permit number and geophysical log type as displayed in the following screenshot.

Figure 32. Geophysical log files

The user can then click on the geophysical log to display the log or the user can save the log to their machine. Only one geophysical log can be downloaded at a time through this interface.

3.2.3 Architecture

The architecture in place to support WIS and PA*IRIS is intermingled as illustrated in the architecture diagram. The architecture diagram depicts the ability of external users to access PA*IRIS via the internet and gain access to WIS, OnBase, Oracle Discoverer, and the FTP site. This diagram also depicts the access internal users have. The public-facing servers that are accessible through the internet are housed at the Commonwealth Technology Center (CTC). The remaining servers are housed at DCNR with the database server located in Harrisburg and the other two servers located in Pittsburgh. All of the components of WIS and PA*IRIS are served to the user through Citrix Metaframe which is an application virtualization tool; therefore, Citrix is installed on a server at the CTC as well as a server at DCNR. The same is true of WIS. The servers on this diagram identified as having Oracle Forms are the servers that support WIS. The WIS database is stored on a server at DCNR (NRWIS01). Oracle Discoverer is also used internally and externally, and therefore, is installed on both a CTC and DCNR server.

OnBase is used through the external PA*IRIS interface; therefore, the instances of OnBase necessary to run the software are located only on a CTC server. OnBase uses a proprietary database schema in Oracle. The image files are not actually stored in the database, but the files locations are; however, the files are stored on the same server as the database. The instance of Oracle on PAIRIS2 is used by OnBase as well as Citrix.

ArcGIS 9.1 and Base Maps are on a server in Pittsburgh, and this functionality is accessed through Citrix by the personnel in Pittsburgh. Currently, the version of ArcGIS on the user’s desktops is 9.3 and the version on the server is 9.1, which is causing a problem and prevents



Base Maps from being used by the geologists to plot the wells. The FTP site is accessible to the user community through PA*IRIS; therefore, it is stored on a server at the CTC (PAIRIS1).

PAIRIS1

Citrix, Oracle Forms, Oracle

Discoverer, FTP

PAIRIS2

OnBase 3.7 Client, OnBase

4.3.7 Web, OnBase Workflow,

Images, Oracle 9i Database

PAIRIS3

Not currently used

INTERNET

Firewall

Firewall

DCNR BIT

Pa*IRIS Users

HTTP

CTC

PAIRIS2

Logins for

PaIRIS/OnBase

PAIRIS1

Database: WIS

Instance: WIS

NRWIS02

NRWIS00

Internal Users

Citrix

Logins

Server: NRWIS01

NRWIS00

Located in Pittsburgh,

Citrix, Oracle Forms 6i,

and Oracle Discoverer

NRWIS01

Located in Harrisburg,

Oracle 9i Database

NRWIS02

Located in Pittsburgh,

ArcGIS 9.1 and Base

Maps



3.2.4 Deficiencies This section identifies the results of the analysis conducted on the functionality available in PA*IRIS. This information is based on the results of the analysis conducted by the team as well as information provided to the team by the subject matter experts and the industry focus group.

The usage of Citrix in PA*IRIS causes frustration with the subscribers because of the number of times that the users must enter their log-in credentials. Not only do the users have to log into PA*IRIS, but each time they navigate to OnBase, WIS or WIS Reports, they must enter their log-in credentials again.

The original intent with the scanning capabilities in OnBase was to incorporate a workflow process. This was intended to allow scanned images to be sent via workflow to the appropriate individual for further processing. Alerts were to be sent to specific people regarding CBM and significant wells. Apparently, at one time this worked, but it no longer does. Currently, the workflow process is handled manually by providing the hard copy information to the appropriate individual. This causes problems because the staff members are not always sure who has what paperwork. Also, as mentioned with WIS, the images are not incorporated into WIS which would allow easy access for the user to view the imaged document. Instead the user must use WIS to look at the data for the well and separately use PA*IRIS to view the image.

Presently, there is no functionality within PA*IRIS or WIS that allows the subscribers to PA*IRIS to be stored and tracked. A spreadsheet is used to list all of the subscribers and to track the payment of their subscription and maintenance fees. There is also a separate Services application that is used by the administrative staff in Pittsburgh to record the services provided to external stakeholders that required a fee. With this information, the Bureau would be able to track metrics of usage in addition to creating a web interface that allows the subscribers to submit their subscription fees online.

The Oracle Discoverer tool is limited in its effectiveness. The staff indicated difficulty in creating the reports needed. In some instances this appeared to be caused by the database design. However, it also seems to be attributed to the lack of views in the database that allow the user to build reports easily from data that has already been assembled in the database and to the way workbooks have been constructed in Oracle Discoverer. If the workbook is broad enough in its design, it will include all of the tables that may be needed to accommodate the potential reporting requirements. It seems as though the workbooks built have been built to accommodate the needs of a specific report which provides limited flexibility when it comes to customizing the data to meet the needs of a specific report. There may also be permission issues that need to be addressed to ensure that the appropriate individuals have access to the correct information.

The ability to access the geophysical logs is very important to all PA*IRIS users. However, the FTP site only allows the download of one geophysical log at a time. This is satisfactory when the user is only attempting to view a geophysical log for a specific well. But more often than not, the user is attempting to gather information on a number of wells in proximity to each other to identify drilling locations, to complete stratigraphy, for use in a software application, etc. Therefore, geophysical logs should be associated with the well, but users should also be able to download geophysical logs in batches according to search criteria such as area, operator, county, quadrangle, section, township and lat/long.

PA*IRIS users have the ability to access OnBase within Citrix or via the web. The data is the same regardless of the interface used; however, the ability to print is not available for the Citrix version. Ideally, the imaging solution should provide the needed user interface and the ability to print.



PA*IRIS does not include any mapping capability. The ability to do interactive mapping or to see map layers is very desirable by the subscribers as well as the Bureau.

Directional surveys, which are submitted once a well has been completed, are important documents that are scanned and associated with the well’s completion report. Specifically identifying the existence of directional survey reports in PA*IRIS would be beneficial.

For many of the subscribers, they extract the data from WIS, review the data to verify its accuracy – particularly with respect to location data – and then load the data into their own application such as Geographix. Based on discussions with these subscribers, it seems that industry leans mostly toward the use of true latitude/longitude (degree/minute/second) data for their mapping projects. The Bureau is the official source of well data for the Commonwealth and as such the ability to extract the data is vital. However, the extraction can be difficult and doesn’t always provide the data needed. The ability to do ad hoc queries would be desirable, but it should be noted that this can cause training and support issues.

Additional options for querying the data in OnBase may be needed. For each type of image, certain keywords are recorded and searches can only be done for those keywords. Most often the permit number is used for the queries, but there may be other search criteria that would be helpful for subscribers.

3.3 PaGWIS

3.3.1 Purpose

Approximately 15,000 water wells are drilled in the Commonwealth each year. PA Act 610, the Driller’s Licensing Act of 1956, covers the regulations regarding water well drilling. According to PA Act 610, the driller must be licensed in the Commonwealth, must have permits for all drilling rigs, and must submit well completion reports to the Bureau. The licenses and permits require fees to the Commonwealth which are allocated to the DCNR General Fund and can be paid via WebDriller (refer to Section 3.4 for information on WebDriller) or directly with the Bureau. The well completion reports are to be submitted by the driller within 21 days of completion of the well, but as with oil/gas wells, this timeframe can be interpreted by the driller and is not strictly enforced. As of 2009 when the latest version of WebDriller was implemented, the requirement was changed where the drillers must now submit their well completion reports electronically; however, some drillers do still submit paper well completion reports. The Bureau has been collecting completion reports since 1966 and according to PA Act 610 must make the data available to the public.

In the 1980s, the Bureau used a system called Water Well Inventory to record and track the water wells drilled in the Commonwealth. This system used a legacy database platform, possibly ENABLE or dBase. This system was then converted to an Access database and renamed PaGWIS. In order to meet the requirement that water well data be available to the public, CD’s of the database were sold for a fee. The Access database was later converted to a SQL Server database, and the old version of the Access database was saved to CD for historical record.

PaGWIS is used by the Bureau to conduct groundwater studies, to study aquifers and their depths, to map bedrock, etc. It is also used by DEP as part of the permitting process for oil/gas wells that requires an inventory of all water wells within 200 feet of the proposed location. In addition, the Marcellus shale gas play has drawn significant attention to groundwater given allegations that private water well quality in the vicinity of such shale gas wells has been adversely impacted by dissolved constituents as well as stray methane gas.



PaGWIS provides the ability for anyone to view specific groundwater records or to download the data into an Access 2000 database. When viewing specific groundwater records, the user has the ability to search for the well based on location, well ID, date drilled, driller license. or driller name. The Access database downloads can be for a specific county or for the Commonwealth as a whole.

The data available in PaGWIS is stored in a SQL Server 2000 database. This database includes all of the legacy data stored in the various databases that have been used in the past to store water well records as well as the records received in WebDriller. PaGWIS does not have a user interface of its own. As of 2009, drillers have been entering their well completion reports in WebDriller and a weekly process is to export the data from WebDriller to PaGWIS. This interface has not been running for almost two years. To create the downloadable files accessible from the PaGWIS website, the data from the SQL Server database is exported to Access. An updated exportable file was created in June 2009, but no new exportable files have been generated since then.

There are approximately 150,000 records that are stored in PaGWIS with minimal data to date. These are mostly historical records that have been entered by interns in the past. In addition to entering skeletal data, the interns scanned the well completion reports, and the scanned images are available in PaGWIS. Some of the data associated with these records was entered at that time; however, there is data that is still missing for these records.

3.3.2 Functionality

PaGWIS is accessible from the Bureau’s web site. PaGWIS is located at http://www.dcnr.state.pa.us/topogeo/groundwater/PaGWIS/PaGWISMenu.asp?c=t. This web page provides general information about PaGWIS. Toward the bottom of the page are two different links: one that allows the ability to view specific groundwater records and the other to download PaGWIS data in Access 2000 format.

Figure 33. PaGWIS link to view specific records

Figure 34. PaGWIS link for Access database

View Groundwater Records Online

When viewing specific groundwater records, the user is prompted with several options to search for the record. These include “Multiple Criteria”, “Polygon Search Decimal Degree Format”,

http://www.dcnr.state.pa.us/topogeo/groundwater/PaGWIS/PaGWISMenu.asp?c=t



“Radial Search Decimal Degree Format”, Polygon Search Degrees Minutes Seconds Format”, and “Radial Search Degrees Minutes Seconds Format”. Once the user selects the option desired, the appropriate search screen displays.

Figure 35. PaGWIS search options

The Multiple Search option allows the user to search by county, by county and municipality, by driller well ID, by date drilled, by driller license, and by driller name. If a county is chosen, the municipality dropdown box should be filtered to only those municipalities in the county chosen. During use of the system, this did not happen automatically, and the user needed to click the Refresh Municipality List button for this to occur.

Figure 36. PaGWIS multiple search page



The results are returned based on the search criteria entered. The user has the ability to click on the well identification number to view the details of the record for that well.

Figure 37. PaGWIS search results



The details of the well record display on the page. The level of information provided on this page will vary by well. For some wells, this information is extensive whereas others are missing a lot of the data.

Figure 38. PaGWIS well record



For some of the older wells for which the records were scanned, the user has the ability to view the image. Once the user clicks on the View Image link, the scanned document displays.

Figure 39. PaGWIS well image

The user also has the ability to search for wells using polygon and radial searches. The polygon searches look for all wells within the latitude and longitude ranges provided by the user. These searches can be with decimal latitude and longitude or with true latitude and longitude (degree/minute/second format). The radial searches look for all wells in the user supplied radius around a supplied latitude and longitude for the central location of the radius. Like the polygon searches, these can use decimal latitude and longitude or true latitude and longitude. The results supplied by these searches are similar to the results displayed in Figure 37 shown above.

Figure 40. PaGWIS Polygon Search, decimal format



Figure 41. PaGWIS Radial Search, decimal format

Figure 42. PaGWIS Polygon Search, degree-minute-second format

Figure 43. PaGWIS Radial Search, degree-minute-second format



Download PaGWIS data in Microsoft Access 2000 format

The link provided on the PaGWIS webpage to download MS Access 2000 data takes the user to the following web page:

Figure 44. PaGWIS download page

This web page provides a link to the executable files created for each county and for the Commonwealth as a whole (pagwisall.exe). These executable files include all of the necessary data for the user to have a fully functioning Access database, along with the data for the county or if the all file is chosen, for the entire Commonwealth.



Below is a screenshot of the interface in Access after downloading the pagwisall.exe file. This file includes an interface to allow the user to view the data, but it also provides the user with access to all of the tables so that the user may create reports and queries as needed.

Figure 45. PaGWIS Access download

It should be noted that PaGWIS also contains data about springs in the Commonwealth. This data is only accessible via the Access downloads and is not accessible when viewing specific groundwater records in the current version of PaGWIS. Nonetheless, these data are necessary for the Bureau. When the Access version of PaGWIS was in use, this data was entered. Presently, there is no way to enter spring data because PaGWIS does not have an interface for it.

3.3.3 Architecture

The architecture of PaGWIS includes an internet accessible user interface as well as a SQL Server database that stores the water well data. The interface that provides access to the data in SQL Server is housed on load-balanced servers at the CTC. It should be noted that this interface is strictly a query tool that allows the user to search for and view information. Also, the user is not required to log into this interface. The SQL Server database used to store the data is housed at DCNR in Harrisburg.



INTERNET

Firewall

Firewall

DCNR BIT

PaGWIS Users

HTTP

CTC

NRINTS02

No Login

Required

NRINTS01

Database: PaGWIS

Instance: nrsqls02

Server: NRSQLS02

NRINTS01

.NET, PaGWIS Website,

Node 1 of 2, Load Balanced

NRINTS02

.NET, PaGWIS Website,

Node 2 of 2, Load Balanced

NRSQLS02


SQL Server 2000

3.3.4 Deficiencies

This section identifies the results of the analysis conducted on the functionality available in PaGWIS. This information is based on the results of the analysis conducted by the team as well as information provided to the team by the subject matter experts.



The key functionality deficiency in PaGWIS is the lack of an interface. Data presently cannot be entered directly into PaGWIS and the data transfer that should be occurring between WebDriller and PaGWIS isn’t functioning either. No new information has been provided in PaGWIS for almost two years. In addition information about springs in the Commonwealth cannot be entered nor can updated well information be added as a result of field surveys conducted.

The Access files are incomplete and are missing data. This is discussed in more detail in Section 4.3 of the document.

Mapping functionality would be desirable in PaGWIS to provide a visual representation of the location of the wells; however, the accuracy will be limited because of the quality of the location data in PaGWIS.

Approximately 15,000 water wells are drilled in the Commonwealth each year. There is no dedicated administrative staff for water wells in DCNR; therefore, data updates and data cleanup is difficult. PaGWIS issues and inquiries require hydrogeologists to take time away from their required geological tasks.

Because the water and oil/gas well information is not in one system, the Bureau does not have a clear picture of the proximity of oil/gas wells to water wells and the ability of the staff to conduct studies on the affect on groundwater of oil/gas wells is impaired.

Presently, PaGWIS provides the ability to extract data by county or for the whole Commonwealth in Access format. This data is used for further data manipulation and reporting. Ideally, when moving to a system with a single code base and database schema, the reporting tool should allow data extraction for both oil/gas and water wells to be executed similarly.

3.4 WebDriller

3.4.1 Purpose

As explained in Section 3.3.1, WebDriller is the online application used for driller licensing, drilling rig permitting, and well completion reporting. WebDriller was originally built in 1998 using a SQL Server database with an interface written in ASP which was later converted to .NET 1.1. WebDriller was updated in 2009 to a SQL Server 2005 database with a .NET 3.5 application written in VB.NET.

WebDriller provides online functionality for the drillers to renew their licenses including paying for the license and to permit all of their rigging equipment. This reduces the administrative requirement of the Bureau to support this process; however, several drillers complete their licenses and permits manually. With the implementation of the new WebDriller application in 2009, all drillers are now required to submit their well completion reports electronically; however, there are a few drillers who continue to submit paper well completion reports. Drillers must supply the county and the decimal latitude and longitude coordinates for the well drilled as part of the completion report. It is a legal requirement that drillers submit an accurate location of the water well. This is critical information to know the location of the well particularly when compared with the location of oil/gas wells. It is a requirement that oil/gas well operators identify all water wells within 200 feet of the location of the intended oil/gas well.

The completion report data in WebDriller is the critical data needed in PaGWIS. WebDriller is supposed to transfer data to PaGWIS with a transfer process that is to execute once a week. However, as indicated in Section 3.3.1, this transfer has not occurred for almost two years.



Therefore, the most recent well record information is not available in PaGWIS because there is no other way for the data to be entered in PaGWIS.

WebDriller includes an administrative interface available to Bureau personnel via the intranet that allows the Bureau to manage driller information and accounts, to process funds received, and to perform other necessary administrative tasks.

3.4.2 Functionality

WebDriller is accessible through the following link: https://www.webdrillersecure.dcnr.state.pa.us/Login.aspx. Once the website is accessed, the driller must log-in using their driller number and their assigned password.

Figure 46. WebDriller log-in

From the Home Page in the application, the user has the ability to renew their license, complete a new rig permit, and manage their well completion reports. The application uses icons, almost like a desktop, to represent the different areas of functionality available in the application.

Figure 47. WebDriller home page

When the driller chooses the icon to enter a new well completion report, the application first requires the driller to supply the county in which the well was drilled. After this is completed, the page as illustrated below displays. The web pages in WebDriller utilize the tab navigation

https://www.webdrillersecure.dcnr.state.pa.us/Login.aspx



concept. This groups similar material onto tabs so that the user is not presented with an overwhelming web page with many fields to complete. The tab displayed below is the Location tab, which provides information on the latitude and longitude of the well as well as the well depth, well address, unique well ID, and drilling method. The application verifies that the longitude and latitude coordinates fall within the boundaries of the county supplied. If the user also supplied a municipality or a municipality and quadrangle, the application will verify that the coordinates fall within that municipality or quadrangle. The application also provides the ability for the user to view the well location on a map or to use the map to identify the location of the well and the coordinates will populate the latitude and longitude fields after closing the map. This is not a topographical map and is not associated with a GIS.

Figure 48. WebDriller Location tab

The driller must also complete the Driller’s Log tab. This tab requires at least one entry and allows the user to provide the intervals of each rock formation encountered during drilling. The driller provides the top and bottom of the formation and a description of the formation. The description is a text field that allows the entry of any text value. WebDriller does not use the concept of rock formations or units like WIS does.

Figure 49. WebDriller Driller's Log tab



The driller must complete the Borehole tab. A borehole can have different sections that are different diameters. This tab is used to record the borehole sections and the diameter for each section.

Figure 50. WebDriller Borehole tab

There are additional tabs in WebDriller that allow the driller to record Casing, Screen/Slot, Well Liner, Packer, and Water Bearing Zone data. These are all optional tabs.

Figure 51. WebDriller Casing tab

Figure 52. WebDriller Screen/Slot tab

Figure 53. WebDriller Well Liner tab



Figure 54. WebDrillerPacker tab

Figure 55. WebDrillerWater Bearing Zone tab

The last tab in WebDriller, the Summary tab, summarizes the accuracy and completeness of the well completion report. This includes ensuring that all required fields have been completed, but this also involves ensuring the business rules have been successfully passed. For example, the application ensures that the decimal latitude and longitude coordinates are inside the confines of the geography chosen. At a minimum, the coordinates must be within the range of coordinates that are acceptable for the county where the well was drilled.

Figure 56. WebDriller Summary tab

Once the report has been completed, the driller has the ability to review the report. This displays the report in the format that it will be printed in allowing the driller to ensure the information is accurate and complete. The driller must then print the report for the owner; however, once this is done, the report cannot be edited. Therefore, it is imperative for the driller to review the report prior to printing it to verify its accuracy.



WebDriller is also used to record the plugging/abandoning, deepening, or reworking (“cleaning out”) of wells. The Commonwealth must be notified of the plugging/abandoning of a well and a well abandonment report must be submitted. All of these options are controlled on the Location tab by selecting the Type of Activity. Depending on the selection, the data entry fields are dynamic to reflect the business rules associated with the activity.

WebDriller does not include any imaging capability or GIS mapping capability.

3.4.3 Architecture

The architecture of WebDriller includes an internet accessible user interface as well as a SQL Server database that stores the data. The interface is housed on a server at the CTC, and the user connects via the internet using a secure connection. The SQL Server database used to store the data is housed at DCNR in Harrisburg.

The user must access WebDriller using a username and password as well as an intrusion protection code. The application is accessible using a web browser (preferably Internet Explorer), and it does not require any additional specific software.



INTERNET

Firewall

Firewall

DCNR BIT

Driller Users

HTTPS

CTC

NRECOMMS02

WebDriller

Login

Database: Driller

Instance: nrsqlprd02\inter

Server: NRSQLS07

NRECOMMS02

.NET, WebDriller Website

NRSQLS07


SQL Server 2005

3.4.4 Deficiencies

This section identifies the results of the analysis conducted on the functionality available in WebDriller. This information is based on the results of the analysis conducted by the team as well as information provided to the team by the subject matter experts.

The WebDriller interface is a new interface, and enhancements are identified from time to time. Many of those enhancements have been made, but there are a few remaining changes desired in the functionality. Presently, WebDriller requires the decimal latitude and longitude when the well completion report is entered. For many drillers the decimal latitude and longitude that will satisfy the business rule check that verifies the latitude/longitude



within the boundaries of the county, quadrangle or municipality is not known. It would be helpful if WebDriller provided a feature that verified the coordinates the user entered on a map.

When entering a completion report in WebDriller, the driller must complete all required fields and pass the business rule checks. Ideally, WebDriller should allow the user to save a completion report without completing all fields.

The WebDriller interface is not particularly intuitive for well abandonments or for ground source heat pump borings or wells. Some of the fields seem not to apply for these types of activities, which generates a number of inquiries to the Bureau. Casing and backfilling data entry is confusing, and the drillers are unsure where to enter the information. Some of the data entry fields that are required for an abandonment do not appear to be applicable, e.g., Drilling Method, and Well Depth.

3.5 OGAPS > OGRE

3.5.1 Purpose

The Pennsylvania Oil and Gas Annual Production System (OGAPS) has been used by oil/gas well operators to report their annual production. According to the Oil and Gas Act, annual production data for oil/gas wells must be submitted to the Commonwealth and the production data is confidential for 5 years. OGAPS was implemented in 2007 to allow operators to submit their production data via an online system. Some operators continued to submit their production data on paper, and this data was entered directly into WIS by DEP. Refer to Section 3.1.2 for information regarding the processing of production data entered into WIS. OGAPS was originally built by DCNR, and was supported and maintained by DCNR until earlier this year.

In the beginning of 2010, Senate Bill 297 was passed and PA Act 15 of 2010 was signed into law. This changed the Oil and Gas Act to require the reporting of production data for wells producing from the Marcellus shale formation to semiannually (due February 15th and August 15th each year). For wells producing from all other formations, the reporting remains annual; however, for all types of wells, the confidentiality period of 5 years no longer applies. With the passage of PA Act 15, the DEP assumed responsibility and control for the production system. PA Act 15 required production data for Marcellus producing wells for July 1, 2009 through June 30, 2010 to be reported by August 15, 2010. To support the operators, the DEP took over OGAPS, renamed it Oil and Gas Reporting – Electronic (OGRE), and made it available to the operators to report their Marcellus production in accordance with the August 15, 2010 deadline. Operators were told that they should continue to submit their non-Marcellus production using OGAPS. This legislation also includes a provision whereby the Marcellus production data shall be made available to the public via the internet. This took effect on November 1, 2010, and the system is referred to as OGRE Reporting. The intention at the time of writing this document is to fully decommission OGAPS by 12/31/2010, and OGRE will be used for reporting of all oil and gas production in the Commonwealth.

3.5.2 Functionality

Because OGAPS will no longer be used in the near future, this document does not include in-depth detail on the OGAPS functionality. In the simplest of terms, the OGAPS application was based on the operator’s unique Oil and Gas Operator Number (OGO).



Figure 57. OGAPS log-in page

Once logged into the application, the operator entered the year for which they were reporting production data. It should be noted that the functionality available in OGAPS mirrors the data collection of the Report Annual Production Data (BOGM) form used in WIS.

Figure 58. OGAPS production year page

Once this was entered, the operator would indicate all of the wells for which production data was being reported. This was based on permit number.

Figure 59. OGAPS well page

Once the well information was entered, the production for that well could be entered by choosing the production hyperlink. This new page provided the ability to record oil, gas, and waste production.

Figure 60. OGAPS production entry page



If the operator supplied waste production data, then the operator would be prompted to provide waste disposal information.

Figure 61. OGAPS waste entry page

Once this information was entered for all wells for that operator for the year, the operator could then generate the full production report.

Figure 62. OGAPS Production Report page

At this point, the production information is stored in the temporary tables used for production data in WIS. Just as if the data was entered in WIS, the information entered in OGAPS will go through the error-checking process prior to the production data being transferred to the permanent storage for production data in the WIS database. If errors are found, the information will be available through the Filter Production Data form in WIS.

With the transfer of OGAPS to OGRE, responsibility for the production system has shifted from DCNR to DEP. OGRE was built based on the functionality available in OGAPS, and the data from OGAPS has been moved to OGRE. Therefore, when registering for an account, the operator will be prompted to provide their OGAPS password.



Figure 63. OGRE log-in page

As previously mentioned, the complete transition of all production data entry to OGRE form OGAPS will occur by the end of the year. At this time, OGRE is receiving its data from OGAPS, which is receiving its data from WIS. Moving forward, when the transition is complete from OGAPS to OGRE, the data in OGRE will come directly from eFACTS. At the time of the writing of this document, this interface was in the process of being built. The key component of the production data for DCNR is that the production data is shared with DCNR and recorded in WIS. WIS is the only system that provides an historical record of all production for a given well during its lifetime. This transfer may occur via an interface that provides a process of getting the data from OGRE to WIS or this could be done by DEP providing the tables to DCNR with the necessary data for DCNR to load into WIS. The exact design of the data transfer is not presently known.

3.5.3 Architecture

The data needed to support the OGAPS functionality and the processing of annual production reports is stored in the WIS database. As explained in Section 3.2.3, the NRWIS01 server located at DCNR BIT in Harrisburg stores the WIS Oracle 9i database. Because the front end functionality of OGAPS is being decommissioned, a full architecture diagram was not developed for this document. Upon the conclusion of the design of the data transfer of data from OGRE to WIS, a diagram should be completed.

3.5.4 Deficiencies

Because OGAPS is being decommissioned, documenting functionality deficiencies is moot.

4. Data Analysis

4.1 Background

The Data Analyst reviewed existing documentation for the WIS, WebDriller, and PaGWIS databases, which primarily consisted of the data model. However, for WIS, there were multiple versions of the data model and no apparent way to determine which one was current or the most accurate. Most of the analysis was conducted using Oracle SQL Developer with connections to the respective systems. The system catalogs and tables were used to cross reference the data models with the actual system inventory for each system. A data dictionary spreadsheet was assembled which includes all of the tables and data elements with their associated data types and lengths. These data dictionaries are included in the Appendices.



A series of queries were developed and executed to gather table-specific (row counts, indexes, etc) and data-specific (missing, incomplete, uniqueness, etc) information. Informal question and answer sessions were held with the WIS Database Administration and the developers supporting WebDriller and PaGWIS to gain the perspective of technology “use” of the systems. Basic system information including database platform and year-over-year database growth was also captured.

A complete database design evaluation was not done and would normally take into account data relationships, database access paths and execution times, end-user query usage and various other factors. However, during the analysis, any obvious database design concerns were documented.

The primary focus of this task was the data. Data quality needed to be determined before the expectation of creating a single database schema could be addressed. The quality of data has many dimensions; accuracy and completeness are two of the most important.

Accuracy: Data Accuracy is the most important as it represents all business activities, entities and events. Two important requirements should be met for a data to be accurate. First, it has to be the right value. Second, it has to precisely represent the value in consistent form.

Completeness: Refers to whether or not all the data necessary to meet the current and future business information demands are available in the data resource.

After the individual systems were analyzed and documented, the scope was expanded to determine the feasibility, and document the challenges of combining the WIS, WebDriller, and PaGWIS systems along with the information contained in the Stratigraphic Database Systems Requirements Specification document to create a single database schema. This level of focus identified items that during the individual systems analysis were not concerns, but when considering the merger of data structures, storage methods, database platforms and unique business, were now identified as potential challenges.

4.2 WIS

Overview

The WIS system went live in 1995. The data is stored in a Relational Database Management System (RDBMS) using Oracle 9i. The current (at the time of analysis) WIS database schema consists of approximately 110 tables with primary keys identified, both system generated and data defined. Additional indexes are defined throughout the database schema. The current storage utilization is 6,750 MB.

The database analysis to determine “active” tables was based upon several differing database diagrams, end-user documentation, feedback from the Oracle Database Administrator (DBA) and examination of the actual Oracle system. There were a number of tables (30+) defined in the Oracle system that were determined to be not used. This determination was made by comparing the varying data models, end-user notes, DBA expertise, and Business Analyst systems evaluations. A thorough code review would need to be completed in order to validate that the remaining tables are all being used.

Data Growth

The following table represents the number of new wells added to the WIS system year over year. 26,639 entries did not have a corresponding creation date.



Year*

New Wells Total Wells

Prior to 1995 29267 29267

1995 98688 127955

1996 3853 131808

1997 3724 135532

1998 4085 139617

1999 1668 141285

2000 3498 144783

2001 3434 148217

2002 4389 152606

2003 1340 153946

2004 968 154914

2005 600 155514

2006 748 156262

2007 841 157103

2008 417 157520

2009 893 158413

2010 264 158677

none identified 26639 185316

*based upon Well Creation Date

Database Design

As mentioned above, a complete database design evaluation was not done. However, as part of the data analysis, several design issues were readily identified.

1. No industry accepted naming conventions were used when this structure was originally created.

2. Commonwealth OA OIT and DCNR IT standards are lacking.

3. There is inconsistent naming of data elements.

example: Long_True (Loc_Plat table) v. True_Longitude (Wells table)

4. Review of the data model(s) showed a recurring theme of a group of tables that were orphans, meaning that this group of tables had no documented relationship to other tables within the model. This situation can legitimately occur in a data model. Without conducting a comprehensive code audit in conjunction with reviewing established business rules in effect; however, the true reason can not be determined. Even so, these types of situations raise a number of questions that should be asked.

Do these tables have valid relationships to others and the model just needs updated?

Are these tables used for verification or lookup?

Does the application control referential integrity within the code or with the database by use of Foreign keys?

Are these tables totally unrelated in the current structure? …implying either the data is not needed or the original design is flawed or outdated

5. Data normalization seems to be an issue.



The logical database model and design should be driven by the implicit data relationships, with the end result of having data stored in one place only.

The physical database design should use the logical design as a starting point and apply database techniques (ie. Denormalization) to increase efficiency and support common queries identified by the application and end-users.

A database design that supports this practice typically has several main transactional tables that are supported by smaller “supporting operational data” tables, with relationships enforced by the use of primary and foreign keys, and look-up tables are used to ensure standard and consistent data values. The current design does not represent this structure very accurately.

6. The referential integrity and primary key definitions are not consistent.

For some of the tables the foreign keys are ID’s while for others, the foreign keys are specific data elements.

7. Data redundancy exists, particularly between the Wells and Loc Plats tables. Location information is stored in both tables as well as well depth. This information should only be stored in one table. True latitude and longitude and offset data are stored in both tables. Decimal latitude and longitude values are only stored in the Wells table.

Data Quality

The data quality analysis effort was concentrated against the tables containing the primary system information: Wells, Location Plats, Drillers, and Drillers Logs.

The information and associated counts presented below were accurate at the time the analysis was conducted and queries executed. Due to the ever-changing dynamics of a database system, these numbers will not exactly match the current database composition, but will provide an accurate representation.

1. Wells table– 185,316 rows

There are over 20 fields in the Wells table that store some sort of location information. Several of these fields do not seem to have been used over the life of the system.

o All rows have null Slat / Slong and null Tlat / Tlong degree, minute, second, and millisecond data elements.

Several of these fields have been sporadically used.

o 43,939 rows do not have true latitude and true longitude or decimal latitude and longitude values.

o 37,687 rows do not have west offset and south offset values. There are records that have one or the other, but not both.

True latitude and longitude values stored in the table could be according to NAD 27 or NAD 83. As of March 1, 2010, DEP is storing true latitude/longitude in NAD 83. Of the 310 rows with a creation date of 3/1/10 or more recent, 53 rows have true latitude and longitude values. The remaining 257 have null true latitude and longitude values.

Missing or sporadically used fields (data elements)

o 26,702 rows do not have a Creation Date



o 45,849 rows do not have a Completion Date o 19 of 59 fields have no data on any row within the table

2. Loc_Plats table– 245,039 rows

There are 14 fields in the Loc_Plats table that store some sort of location information. Several of these fields do not seem to have been used over the life of the system.

o All but 5 of the rows have null lat and long degree, minute, and second data elements.

Several of these fields have been sporadically used.

o 75,354 rows have null true latitude and longitude data elements. o 55,888 rows have null lat offset and long offset data elements.

There are 112,240 records in the Wells and Loc_Plats tables that have identical true latitude and longitude values. (ID vs Well ID)

True latitude and longitude values stored in the table could be according to NAD 27 or NAD 83. As of March 1, 2010, DEP is storing true latitude/longitude in NAD 83. Of the 4,392 rows with a creation date of 3/1/10 or more recent, 4,346 have true latitude and longitude values. The remaining 46 have null true latitude and longitude values.


o 26 of 72 fields have no data on any row within the table

3. Clients (Operators) table – 10,718 rows


o 756 rows do not have a street address o 724 rows do not have a city o 726 rows are missing state information o 800 rows are missing a zip code o 12 of 30 fields have no data on any row within the table

4. Driller’s Logs table – 751,849 rows

4 rows with an entry greater than the depth specified as “bottom”

1 row with and entry less than the depth specified as “top”

5. Geophysical Logs table – 49,166 rows

Location of the tiff Log is stored in the database

4.3 PaGWIS

Overview

PaGWIS data is stored in MS SQL Server 2000. The current (at the time of analysis) PaGWIS database schema consists of approximately 93 tables with primary keys identified, both system generated and data defined. Additional indexes are defined throughout the database schema. The current storage utilization is 1,611 MB.

The database used for PaGWIS is very similar to the one for WebDriller, except that PaGWIS includes tables for Springs. There is no interface to enter data into the PaGWIS database.



WebDriller is the source data for the well information contained within PaGWIS; however, the interface that transferred data from WebDriller to PaGWIS currently is non-functional.

Data Growth

There is no database growth to report for the PaGWIS system. There are scripts that mapped and migrated completed Well Reports from WebDriller. However, these scripts have not been functional for over two years.

Database Design

As mentioned above, a complete database design evaluation was not done. Since there is no interface to this data and the source of most of the data is another system (WebDriller), it would be more practical to focus on any issues relating to the source data. The only exception is if there is a need to migrate the Spring data from PaGWIS. At that time, a more comprehensive analysis of the impacted tables and data would need to be done in order to provide an accurate data mapping and migration strategy.

Data Quality

The data quality analysis effort was concentrated against the tables containing the primary system information: Wells, Drillers, Driller’s Log and Well Reports.

The information and associated counts presented below were accurate at the time the analysis was conducted and queries executed. Due to the ever changing dynamics of a database system, these numbers will not exactly match the current database composition, but will provide an accurate representation.

1. tbGenSiteInfo (Wells) table– 388,852 rows

Location coordinates are stored in decimal degrees

194,292 rows are missing Latitude coordinates

194,275 rows are missing Longitude coordinates

All wells have completion reports

o Only completed wells were populated from WebDriller

Some rows have missing municipalities

There are missing and/or incomplete addresses

2. tblSpringGenInfo (Springs) table – 1,538 rows

Location coordinates are stored in decimal degrees

3. tblDrillersLogInfo table – 77,069 rows

Inconsistent terms used for the description

o example: Dk Gr Shale v. Gr Shale v. Gry Sh

Similar (or same) descriptions but UPPER CASE versus Mixed case

4. tblConstructionInfo table – 388,501 rows

14,694 rows have an invalid or missing Driller License number

o This could be a result of not using a lookup table and/or not using database Referential Integrity (RI).



5. There are approximately 300,000 wells that have not been stored in PaGWIS. This includes wells from 2005 to 2009 because of the broken interface between WebDriller and PaGWIS and the nonfunctioning data extraction tool for the Access database. This is a problem particularly when oil/gas well operators work through the permitting process for their wells and search for the water wells within 200 feet of the proposed location.

The data for PaGWIS is somewhat complicated by the various sources of data. The PaGWIS data that was analyzed was the data stored in the SQL Server database. This database is used to create an Access database that can be downloaded through the PaGWIS website. However, there can be some confusion in viewing the data in these two sources because of the use of ID’s and well numbers. There is also an historical database in Access. This database contains data that seems to have not been converted to the SQL Server database. It was noted in the data that the records in tblGenSiteInfo after 2000 contain much less data than those prior to 2000. This is about when the conversion was made to SQL Server. Prior to doing a data conversion onto a single database schema, the water well data would need to be evaluated in detail to determine the best source of data. The best source may actually be a combination of data from the historical Access database with the SQL Server data.

4.4 WebDriller

Overview

The WebDriller system went live on June 1, 2009. The system consisted of a new interface using the existing database structure and data. No conversion or cleansing of the data was done as part of the project.

The data is stored in MS SQL Server 2005. The current (at the time of analysis) WebDriller database schema consists of approximately 63 tables with primary keys identified, both system-generated and data-defined. Additional indexes are defined through-out the database schema. The current storage utilization is 120 MB.

Data Growth

The following table represents the number of Drillers and Well Reports added to the WebDriller system year over year. The totals are based upon Date Drilled.

Year Licensed Drillers*

Well Reports Completed#

Well Reports Incomplete

Total Well Reports

prior to 2000 629 16576 2677 19253

2001 512 4341 307 4648

2002 509 4268 171 4439

2003 503 4251 212 4463

2004 491 4099 212 4311

2005 483 3206 403 3609

2006 468 73 1687 1760

2007 480 172 1898 2070

2008 449 1675 1979 3654

2009 437 6624 2161 8785

2010 284 4936 1216 6152

*Licensed Drillers indicates the number of drillers who registered for and paid for a license in the license year.

#Well Reports Completed indicates well reports that have been printed for owner and are locked.



Database Design

As mentioned above, a complete database design evaluation was not done. A cursory review of the design did not show any obvious concerns.

Data Quality

The data quality analysis effort was concentrated against the tables containing the primary system information: Wells, Drillers, Driller’s Log and Well Reports.

The information and associated counts presented below were accurate at the time the analysis was conducted and queries executed. Due to the ever changing dynamics of a database system, these numbers will not exactly match the current database composition, but will provide an accurate representation.

1. tblWell table– 67,408 rows

Location coordinates can be stored in three types of formats.

o UTM Northing / UTM Easting o Longitude / Latitude (degrees/minutes/seconds) o Longitude / Latitude (decimal degrees). Some errors occurred during the

conversion from the corresponding degrees/minutes/seconds value.

Location coordinates contain missing or invalid values.

o Some coordinates represent locations outside of Pennsylvania o Longitude – degrees/minutes/seconds

41,559 have invalid (positive) values. Western Hemisphere coordinates are negative.

7,632 have non-unique coordinates o Longitude – decimal degrees

16 have invalid (positive) values. Western Hemisphere coordinates are negative.

7,882 have non-unique coordinates o Latitude – degrees/minutes/seconds

12 have invalid (negative) values. Northern Hemisphere coordinates are positive.

6,798 have non-unique coordinates o Latitude – decimal degrees

6,796 have non-unique coordinates


o 11,346 rows are missing location information o 60,408 rows are missing Quadrangle data

2. tblDriller– 3,048 rows

534 rows do not have a street address

153 rows have no city information

8 rows are missing state information

91 rows contain an invalid state code

1,468 rows have no zip code



3. tblDrillerLog table – 205,738 rows

Inconsistent terms used in the description

o example: Dk Gr Shale v. Gr Shale v. Gry Sh

Similar (or same) descriptions but UPPER CASE versus Mixed case

Invalid descriptions (null, space, ?)

Some rows contain multiple “layers” in the description

o example:

0-20 hardpan 20-80 grayrock 80-120 brown shale 120-180 grayrock o There should be an entry with top/base (start/stop) depth of each layer

encountered, instead of one row with the description providing the breakdown.

4. tblDrill table (Well reports) – 67,048 rows

Not all wells have reports. 63,144 Well Reports are in the database

12,923 Well Reports have not been completed

In addition to these data quality issues, there is no ability for data extracts to be done from WebDriller except by DCNR BIT staff. This becomes cumbersome because WebDriller is the only up-to-date source of data for the current wells.

5. Overall Conclusion

The Bureau intends to move the water and oil/gas well systems onto the same code base and database schema. While this effort is possible, there are fundamental differences between the business processes, functionality, and data that need to be accounted for when moving forward. From a business perspective, oil/gas wells are the responsibility of operators and water wells are the responsibility of drillers. Oil/gas well operators hire the drillers. Water wells are drilled, and the wells are turned over to the owners for their use. Oil/gas wells are drilled and are monitored by the operators for their production. Water well drillers are typically less sophisticated than oil/gas well operators; therefore, they have less capability to provide correct location information and detailed drilling log information. Many of the oil/gas well operators have a field geologist available to provide accurate formation information on their driller’s logs.

Both oil/gas wells and water wells require a completion report to be submitted. There are some similarities between the two, but the level of detail and amount of data is significantly greater for oil/gas wells. For water wells the completion report is the only document required; whereas oil/gas wells have a permit application which includes a location plat, geophysical logs, and a plugging certificate in addition to a completion report. It should be noted that water well drillers are to submit a completion report for the abandonment of a water well whereas oil/gas wells require a plugging certificate. Oil/gas well completion reports are submitted to DEP, whereas water well completion reports are submitted to DCNR online using WebDriller.

There are similarities between the two from a functionality perspective as well. Both require a public-facing service that allows the access and use of data. However, the levels of access are different. All of the water well data is available to anyone needing it, but the oil/gas well data have variations in that the public shouldn’t have the same level of access as PA*IRIS subscribers. Both systems require data extraction capabilities.

The functionality required for supporting oil/gas wells is more extensive and comprehensive. The system supporting oil/gas wells would benefit from a fully integrated workflow that included



imaging capabilities. Water wells require imaging capabilities; however, there is no requirement for a workflow process for those images. Integration with GIS mapping capabilities would be needed for oil/gas wells, and although this would be a desired functionality for water wells, it may be limited due to problems with the quality of the location data.

With respect to building a database schema common to oil/gas wells and water wells, several high-level items should be considered when planning and executing the data portion of this effort. This list does not represent all the tasks that will be required to do create a single database schema, but are some key considerations to ensure that current requirements are met while allowing for growth and flexibility.

1. Development of the data model must be driven by the actual relationships of the data, not by business rules, application programming requests, or any other external factors.

A truly normalized data model will provide the purest representation of the data.

This type of model can then support application development to enforce existing business rules and flows as well as future ones with minimal impact.

A normalized logical data model can easily be transformed into a physical database design that fully utilizes and enforces RDBMS referential integrity.

2. The Data Model must be developed as “least common denominator” of all current systems sources

Resolution of data elements across systems

Consensus of element name, definition, and characteristics

Mapping of source elements, include conversion requirements

It should be noted that the data elements in common between oil/gas and water wells are location information, some completion information, and the driller’s log.

3. Current system business rules may be contradictory and will need resolution.

Mandatory fields and editing requirements may vary across existing systems.

4. Current DCNR and Commonwealth standards will need to be followed, which may introduce constraints when developing a single model.

External vs. internal customer needs may have an impact on server (storage) location and limitations.

Security policies and/or business rules will have an impact.

Performance for internal and external access will need to be considered.

5. Data clean-up and verification

All data should be verified for completeness, accuracy and reasonableness.

Data cleansing will be necessary for some elements.

Mapping of data source to destination with any conversion requirements will be needed. Migration scripts and dependencies will be required.

6. Stored procedure usage for standardization and control

Stored procedures should be created and used for any kind of repetitive calculations instead of being contained within the application code.



o For example: well location could be stored as decimal degrees (NAD83). But a stored procedure could be created to translate those values into numerous other formats (South/West Offsets, UTM, NAD27, etc) needed by internal and/or external stakeholders.

6. Stratigraphic Database Analysis

The Stratigraphic Information Data Management System Systems Requirements Specification (SRS) document was reviewed as part of the project. The goal was to evaluate the requirements identified in this document with respect to the information and knowledge gained about well data. The stratigraphic database, as referred to herein, is intended to provide an enterprise view of the geological data for the Commonwealth.

In reviewing the document, it was not immediately apparent where the oil, gas, and water well data would be incorporated into the Stratigraphic database. The well data identified during the course of this project did not seem to easily integrate into the concepts and terms upon which this database is based. For example, the concepts of a station and a project are not directly equivalent to the concepts and terms used with oil, gas, and water wells. The stratigraphic database uses linear stations to represent the multiple points along a borehole that has X-Y-Z coordinates. While this concept is similar to the desired functionality of directionally drilled oil/gas wells, this terminology is not equivalent to the terminology used in WIS or by the oil and gas industry at large. Therefore, the definition of project would need to be evaluated against the concepts used with oil, gas, and water wells.

The intentions with respect to location data are similar between what is desired in the new wells system and the stratigraphic database. Once again, terminology differs between the two and possibly the kinds of data available. Length value, thickness value and planar value are not terms used in WIS, PA*IRIS, PaGWIS, or WebDriller, but are concepts used for location information in the stratigraphic database.

The team was able to identify information that seemed equivalent to the information gathered during this project with respect to the CBM Well Stations section of the document. This section identified data elements that are similar to those that were discussed during this project. In fact, WIS is cited in this section. However, the document was specific to CBM wells and not wells in general. Therefore, several of the data elements that would be needed for oil, gas, and water wells are still lacking in the CBM Wells Stations section.

Many of the data elements in this document are not data elements that would be available from the well data. The level of detail desired in the stratigraphic database is not equivalent to the level of detail needed to track and manage wells. The geological data stored with respect to oil/gas wells is limited to stratigraphic interpretation data and the data supplied on geophysical logs for individual wells. The geological data stored with respect to water wells is limited to the driller’s logs supplied by the drillers. There is no stratigraphic interpretation prepared for water wells. Data like lithologic data, rock description data, lithic clasts, etc. would not be readily available in the new well data system. The data that may integrate the best with the stratigraphic database is the interpreted data generated in PETRA® using the raw well data from the new well system.

7. Technical Information

During the course of executing this project, the subject matter experts repeatedly indicated the need for the “new” system to be developed as a web application. Ideally, the web application would have role-based security that would provide a single point of entry to the system, but



allow for access to the data to vary depending on the user’s objectives. This would eliminate the need for Citrix and would eliminate the redundant log-ins required in WIS and PA*IRIS.

In addition to the need for a web application, a mapping solution should be integrated into the system. Ideally, the map would have layers to it which could be role-based and would provide varying types of data at different levels of detail. The mapping solution would allow the user to select the layers to display on the map. Ideally, the mapping solution should be connected to the data so that the user can navigate from the map to the detailed information for the chosen item on the map. Again, this capability would be role-based and the layers and access to data would be driven by the role of the user.

At this time in the industry, the usage of web applications is standard. This allows the implementation of a thin client application that does not require any software to be loaded on the user’s machine other than an Internet browser. As web applications have matured, new architectures and approaches to development have evolved. Currently use of a service-oriented architecture is the latest and greatest development. This means that the application uses an architecture where the business layer is decoupled from the physical architecture. This allows for the application to be enabled in a variety of ways and does not restrict presentation. In development of applications, the agile approach to development is also widely used. This is an improvement over the waterfall approach because it allows for iterative development to ensure that all requirements are addressed adequately without major rework. The agile approach is similar to a set of rings. The center ring is the functionality that is absolutely required. That ring is fully analyzed, developed and implemented before moving onto the next set of functionality, or the next ring. Within each ring it is recommended to use an interactive prototyping approach which allows the team to verify the requirements and features with the user community as the project progresses.

The Bureau may want to consider the usage of web services, which would provide a direct way to serve up the data to the subscribers for use in their systems. If designed correctly, this would allow the subscribers to directly extract only the data that is needed in their application.



Appendix A. Meeting Notes The interview meeting notes for the meetings conducted are included in this Appendix. Pittsburgh Meetings – Day 1 Group Meeting Met with Pittsburgh staff for 1.45 hours commencing at 0800 at the Pittsburgh office at 400 Waterfront Drive. In attendance: John Harper, Manager Kristin Carter, Section Chief Katie Schmid, Geologist Jaime Kostelnik, Geologist Lynn Levino, Clerk Typist II Joe Kunz, Clerk Typist III Pedro Forero, ITContractor replacing Kyle Imbrogno while he is on military leave Meeting was kicked off by Amy providing information on her background and involvement in doing analytical work for the Commonwealth and for the EPA. She also explained what she has done to this point in the project. A meeting was conducted on 8/26 with George Love, Margaret Hively, Sandip Patel, Earl Stoltzfus, Seth Greiner, Bryan Hoffman, and Amy. This was an introductory meeting providing information on the background of the project and the overall goals of the project. Amy officially started the project on 9/20/10. Sandip provided a demonstration of PA*IRIS, WIS, WIS Reporting, and the FTP site. Sandip also provided initial information about OGAPS and the transition of the production reporting from DCNR to DEP as a result of PA Act 15. Amy also explained that she has met with Earl, Margaret and Craig concerning OGAPS and the transition to DEP. Amy does not yet have access to WIS and PA*IRIS to view the system. Each member in attendance then explained their role, their usage of WIS and their issues with WIS and PA*IRIS. John Harper - Manager Data cruncher, concerned with statistics and reporting. John was involved with the development and implementation of WIS and PA*IRIS. Explained the piecemeal implementation of the wells information systems – PA WIS first, then GIS, then production (OGAPS), then PA*IRIS. John’s wish list:

One log-in for everything – WIS, WIS Reports, IRIS, GIS, etc.

Usage of the API number – this would include the 2 digit state code, 3 digit county code, 5 digit number and the additional 4 digit code used for different kicks of the same well (horizontal drills, lost holes or directional drills). Situations where there are different kicks mean there is one well, but because there are multiple bottom locations, the well would have multiple APIs. The full API hasn’t been needed in the past, but is needed now. DEP would have to mandate the usage of this number.

Reporting is a problem because of the data structure. The ability to do joins is severely restricted because of the data structure and the inability to relate the data between



tables. For instance, some tables have the permit number while others have a well number. Therefore a join by one or the other has limited functionality.

Eliminate the usage of Citrix. Currently, Citrix doesn’t allow printing. Using the OnBase web interface does allow printing.

Katie Schmid – Geologist Katie is a new hire to DCNR (July) who previously worked in the oil and gas industry. She is responsible for processing completion reports including the total depth (TD) and producing formations as well as verifying the location data/offsets. This is entered on the Completion Reports screen in WIS. She also uses the Stratigraphy screen in WIS and records the stratigraphy, but she currently does not have access to this screen. She uses the modify wells and pools screens as well. Jaime Kostelnik – Geologist Jaime typically does a lot of work with the Base Maps (ArcGIS). However, Base Maps is not functioning. It hasn’t functioned for some time. Base Maps is supposed to be linked directly to WIS and displays the wells on the GIS map. They used to have the ability to publish the map to share it digitally with a push of a button. Presently they cannot offer any maps digitally. They provide the lat/long data in Excel. The operators can then use that information in their own mapping software. If an operator drills in a quadrant that has not previously been drilled in, then they need to print out a map. These maps are from 2005 from the USGS, but sometimes the maps do not correctly print to scale. Note: DCNR uses the 7.5 minute quadrangle topographic maps. Because of the large numbers of wells within certain areas, it is difficult to display all of the wells and their labels. The conversion to decimal lat/long has also been an issue. It is not always executed in the system. Kris Carter – Section Chief (reports to John) Responsibilities:

Run interference with DEP

Process Completion Reports

Field/pool naming

Geophysical log processing – geophysical logs are available through the quasi FTP site Definition of significant well County by county a depth was determined that would classify wells below that depth as significant. For some counties that depth can be 0. Typically these wells are deep and are Marcellus or intended Marcellus shale wells. CBM wells are treated separately, but are considered atypical wells. Operators have 30 days to file a Completion Report after the completion of a well. In 2008, DEP required the operators to provide the target formation on the permit applications. This information cannot be recorded in WIS. However, it is important to note that the information provided by the operators for the target formation is not always accurate.



Pedro Forero– IT Specialist Supports the office with computer issues and receives the notifications from PA*IRIS that would ordinarily be sent to Kyle. He handles service requests for reports, establishes new accounts for new subscribers, assists the members of the office with IT issues, etc. Lynn – Clerk Typist She was involved in the testing and implementation of WIS and PA*IRIS. She does the scanning, has a high speed scanner. She gets location plats 2-3 times a day. Location plats are scanned and the information in WIS is verified based on what is on the location plats. The information in WIS is coming from eFACTS. She handles plugging certificates, completion reports, and location plats. She provides quality control support of annual production data on the WIS side of the database (OGAPS is used to gather the production data from operators; this system is being transitioned to DEP’s responsibility, and may be called OGRE going forward). Even with the shift in responsibility taken on by DEP, Lynn will remain the Survey’s point of contact for production data, and depending on how things play out with the reporting requirements from PA Act 15, may continue to do quality control work. Discussed NAD 27 versus NAD 83. DEP has decided to move to 83. Data in WIS is 27 but a conversion to 83 will be made. Data received from operators could be in one or the other. Typically, notes have been added in WIS to indicate the NAD used according to the information provided by the operator. Joe Kunz – Clerk Typist His main responsibility with respect to WIS and PA*IRIS is data entry. He enters the driller’s log which is included with the completion report. The driller’s log provides information on the rock formations the driller noted when drilling the well. Issues:

Rigidity and structure of system make it difficult to use

Formation names on driller’s logs can be incorrect – using incorrect formation names for PA, making up names, etc.

Field name stamping. The field name will populate in multiple locations and it isn’t accurate.

Discussed 90000 records. These permit numbers were issued for old wells. Many old wells are now being registered which requires a Well Registration from DEP. DCNR must verify if the well registration is for a well that may have a 90000 record. Then the data from the 90000 record must be transferred to the new well record created as a result of the well registration. Discussed the access within WIS and that there are different roles. There is a GEO role for the geologists which is different from the role for data entry operators (DEO) which is different from the role for Administrators. One on One Meetings



One on One meeting with Kris Conducted interview with Kris at 10:00, 9/29/2010 Marcellus started in earnest in 2003. Data needed:

Target formation from permit applications

Need XYZ coordinates for deviated wells – these can be multiples Also referred to as directional survey data

TVD – ture vertical depth versus TMD - total measured depth. Currently TD is captured in WIS. The value entered in this field represents the TMD. Therefore, a field for TVD would be needed.

Process:

1. Well is permitted by DEP. DCNR does not get permit application 2. Location plats are sent to DCNR from DEP – can get proposed location plats and final

location plat (once the well is set up) 3. Then get completion report within 30 days of completion of the well (the term completion

is interpreted which is why some completion reports take awhile to receive) Sometimes operators send interim completion reports. The completion report can also be referred to as the well record.

Objectives with new system:

Web based with a single log on – essentially so that all pieces are under one umbrella

Some piece of the application should be accessible to the lay public as well as the subscription service for the partners. The personnel in the office spend a significant amount of time doing customer service for industry and the public which would be alleviated by providing data on the web, particularly maps.

Additional information: There is a price list for services – payment for subscriptions and services is processed by Lynn and sent to Middletown. These payments are processed through SAP. The fees received for PA*IRIS (subscription and maintenance) are income to the Bureau as a whole (the General Fund) and are not earmarked as income generated by the Geological Survey. Wells can have more than one producing formation. There are requests for custom reports – these take time to interpret to design the report. A NeuraScanner is used to scan the geophysical logs. The geophysical logs are available on the FTP site and can be downloaded one at a time. The FTP site is separate from PA*IRIS and requires its own navigation and log-in. DCNR has 2 NeuraScanners with a third on the way. This includes the scanner as well as the software to do the interpretation and the “squiggles”. System downtime is a concern. In addition to NeuraScanner, they also use PETRA® to perform data and geologic interpretation. Industry uses GeoGraphix which is very expensive and difficult to learn to use.



To get data from WIS into PETRA®, the data has to be exported from WIS to Excel and converted to a csv file and then the import wizard in PETRA® is used to import the data. Permits are good for one year. One on one meeting with Lynn Conducted interview with Lynn at 1:00 on 9/29/10 Location Plat received from DEP – usually a record exists in WIS from link with eFACTS. Sometimes record needs to be created. AnyDOC OCR connected to OnBase. This is what provides the workflow capability. Indicate to system which kind of document is being scanned. This indicates the template so that AnyDOC can highlight the keywords that need to be entered. The template provides the data entry fields where the keywords can be entered. These keywords are then data that can be used in OnBase on querying the images and the keywords populate the necessary information in WIS. (DEP copies documents and sends copies to DCNR. Once documents are scanned, they are discarded.) There is a process in AnyDOC to commit the batch and a dip process that loads the data into PA*IRIS and WIS. After scanning the location plat, Lynn goes to the Location Plat screen in WIS and the Inquire Wells screen to check the latitude and longitude information to make sure the data is there. If not, there is a Convert button so the system computes the lat and long on the Inquire wells screen. Additional information on 90000 records: ENABLE database needed a 5 digit permit number. For old wells before permitting, there is no permit number, but each well had to have one in the system. Therefore, they were assigned a permit number starting with 9. Thus these are referred to as 90000 records. They were assigned a permit number in the 90000 series because it is by county and that level of numbering wasn’t used in any county. (Note: This may become an issue as one county, (McKean) is in the 50000 range.) For these records, well registration forms may be submitted to DEP. With the registration, the well has a new permit number rather than the 90000 number. The information stored for the 90000 record needs to be transferred to the new permit number which is cumbersome and difficult. The deletion of the 90000 record requires that all of the information related to the original well must first be removed. The system won’t execute the child deletions – these must be done manually. The attachments in OnBase are moved – click and drag. Lynn scans Completion Reports and gives them to the geologists. Geologists interpret the data. They determine TD formations, fields and pools, and spot the well on the maps (by hand). Geologists enter information in WIS and then give completion reports back to Lynn who then enters the necessary information in the keywords for OnBase. There used to be a report to update the keywords in OnBase instead of doing it manually. WIS brings in production data from OGAPS. Error flags may be set when data is brought in. Lynn investigates the error codes. Production data is needed in WIS because a history is



maintained. WIS is the only place where there is a history of production data. DEP doesn’t verify permit numbers which causes many of the error codes. Numbers can be transposed or there can be letters in the permit numbers. Plugging certificates cannot be scanned into OCR because the well is flagged as plugged. The Plugging certificates are received by DEP and the information is entered into eFACTS. In WIS the well is updated to plugged and abandoned, but the plugging date is not entered, and the plugging certificate needs to be scanned. Because the well has been updated to plugged and abandoned, that status must first be removed before the system will allow the scan to take place. Once the scan is done, then it is set to plugged and abandoned and the plugging date is entered. The plugging certificates are scanned directly into OnBase. One on One meeting with Jaime Conducted interview with Jaime at 2:00 on 9/29/10 Discussed the mapping situation. Base Maps doesn’t function. Jaime brought up ArcGIS – it starts, but it cannot be used. It appears as though links have been broken. Several months ago the ArcGIS server was upgraded, and since then Base Maps has not functioned. Base Maps is available as WIS GIS in the Citrix set of applications available for the geologists. Starting in 2005, the wells did not always plot on the map (the symbols) and sometimes the labels did not appear either. Also in 2005, the ability to publish the maps stopped functioning. The lack of maps has been a significant issue. She fields many calls asking about location information and if the maps were available particularly on the web, then the calls would decrease and people could do their research via the website. Jaime also has the ability to add new pools. A field must exist to have a pool. Fields are related to counties. She often receives error messages when trying to create a new pool because of the field. In addition to the mapping issue, she also indicated the need for XYZ coordinates for deviated wells, good location data (NAD 27 vs. NAD 83 issue), and the target formation information. Pittsburgh Meetings – Day 2 One on One Meeting with John Conducted interview with John at 8:30 on 9/30/2010 Data needed: Engineering data including stimulation data including the amount of sand and water, and casing and cementing data (this information is available on the completion report). Essentially all data that is on the completion report should be captured in WIS. Latitude and longitude: The operator provides the true latitude and longitude. Today, these are usually provided by a GPS. The operator also provides the corner coordinates (offsets). The base for the corner coordinates are the quadrant and the section. This gives a base latitude and longitude and the operator provides the location data for where the well is located south and west of those. The true latitude/longitude is then used to calculate the decimal latitude and longitude. NAD 27 and NAD 83 will affect all of this data. Ideally both sets of data should be captured.



API: Industry is using the full 14 digit number. The Commonwealth is using the 10 digit number. For many wells the last 4 digits will be 0’s, but for those wells with kicks or side tracks, the 4 digits are used. Workflow: The vision was for the workflow to be much more sophisticated than what was delivered. The contractor did not complete the work. Significant well and CBM alerts were to be sent by the system. This used to work, but apparently, it no longer does. Ideally, the completion reports were also supposed to be workflowed. Vision for the new system: To have the system accessible on the web and provide interactive maps of PA. Ideally, the system would be available to everyone including the lay public, but access to the information and the functionality of the system would be dictated by user roles in the system. The system should also provide download and print functionality. Discussed unnamed pools. If production is occurring from only one reservoir in a field, then the pool is not named. This is how records in WIS have “Unnamed” as a pool value. One on One Meeting with Katie Conducted interview at 9:30 on 9/30/2010 Discussed information from an industry perspective:

Plugged wells – when they were plugged, how they were plugged and where they are. This causes a problem with safety. If they don’t know the wells are there and they dig new wells, blowouts and other problems can occur. Operators have also run into problems with the leases because of location issues.

The multiple log-ins are confusing.

Industry downloads the geophysical logs and uses the reporting heavily. Discussed well registrations for old wells. These are plotted just as the completion reports are plotted. There is a fee to register an old well ($15), but many of the registrations are initiated by DEP. Some registrations are completed by operators. In addition to plotting these, the TD (total depth) formation is also entered into WIS as well as completing as much of the completion report form in WIS as possible. One on One Meeting with Joe Conducted interview at 10:30 on 9/30/2010 Data entry is his primary responsibility. He enters the driller’s log that accompanies the completion report for approved wells. The driller’s log is not included in the imaged documents in PA*IRIS. He also enters the driller’s log for pending significant wells. He has an issue with the field name populating in multiple places and the value is incorrect. It is difficult to correct this situation because the incorrect value displays on a number of screens. He also has an issue with updating the driller’s date. This date is required and is sometimes not known (i.e. pending/incomplete wells). A fictitious date is entered and it cannot be corrected. Likewise, sometimes the date is incorrect.



On Lynn’s off days, Joe scans using her scanner. There is only one scanner. Because there is no workflow, it is difficult to know who has what paperwork. This can cause a problem if an inquiry is received regarding a well that hasn’t been entered yet. The completion reports are distributed randomly to the geologists for review and interpretation. He is unable to print production for a specific well. One on One Meeting with Pedro Conducted interview at 11:30 on 9/30/2010 Pedro fields PA*IRIS calls and assists with service requests. These service requests include the custom reports that are often requested because the subscribers don’t have the ability to query the data except using the canned reports provided in PA*IRIS. He also handles networking issues and networking management (adding/deleting users, etc.). He also creates PA*IRIS accounts once the payment is received by Lynn. Some subscribers may have Apple computers. This causes problems with Citrix, but also needs to be taken into consideration with a new system. The subscribers may need to access the functionality through Safari. The FTP site is used for downloading geophysical logs, but he also uses it to expedite the set up for subscribers because the Citrix client and OnBase software are available on the FTP site. Follow-up Questions Amy asked a few follow-up questions to the appropriate individuals. Those questions and answers are below: How are the partners/subscribers kept track of? There is no registration piece within WIS or IRIS. This is handled manually and is tracked in an Excel spreadsheet that Lynn Levino has. Lynn processes the payments in SAP and mails them to the Department of Revenue. Who scans the geophysical logs? Kris scans these using the NEURA scanner. Does Kris receive automatic notifications for the significant wells? No, she receives the paperwork from Lynn when a significant well is received. Definition of field – a geographic area in which a pool may be located Definition of pool – reservoir where oil/gas is found Landowner versus farm name? Farm name is usually the lease owner which would be different than the landowner. Do they record plug backs? Yes, this is a type of completion. Conclusion Meeting Conducted at 1:45 on 9/30/10 At the conclusion of the two days of meetings, the group was reassembled to wrap things up. Amy asked a few additional questions during the wrap up session, but the focus of the meeting



was to thank everyone for their time and assistance. An abundance of information was gathered and everyone was extremely helpful. The second purpose of the meeting was for Amy to identify the take away items she has. They are:

Crosswalk of reports in WIS to those available through IRIS in WIS Reporting

Review eFACTS process to better understand the data transfers between WIS and eFACTS and to understand problems that have occurred.

Investigate how the production data will be provided in WIS going forward with the usage of OGRE. It is vital to WIS that the production data be available.

Investigate what, if anything, can be done to remedy the situation with Base Maps.

Investigate the different levels of access in WIS for the different roles. We need to do a full accounting of the system and all of its functionality. It appears that there is a fair amount of functionality that is not being used. Therefore, we will need the different roles to further investigate this.

Gather an understanding of the FTP site and its history.

Develop an architecture diagram. The third was to explain what happens next. Further analysis will be conducted and the data analysis will be pursued. The expectation is to conduct elaboration meetings in Pittsburgh later in October (the week of 10/19 most likely) and to conduct an industry focus group during that time. The elaboration meetings will be focused on issues that require further information and to review any data questions that have arisen during the data analysis effort. Industry Focus Group Meeting Notes

TITLE: Discussion of PA*IRIS and WIS from an industry perspective DATE: October 19, 2010 TIME: 1:00 – 3:30 pm LOCATION: TopoGeo Pittsburgh Office INVITEES:

NAME AFFILIATION PRESENT

Carla Blocksom Texas Keystone, Inc. X

Dennis Carulli DC Energy Consultants X

Susan Carulli EOG Resources X

Chuck Devlin XTO Energy

Kathy J. Flaherty ABARTA Oil & Gas Company

Josh Hickman Cabot Oil & Gas Corporation

Patrick Imbrogno Sylvan Energy

Cathy Mathias EXCO Resources X

Tom Metarko XTO Energy X

Jim Wigal ABARTA Oil & Gas Company

Greg Wrightstone Texas Keystone, Inc. X

Kristin Carter DCNR X

Amy Malinoski TreCom Systems Group X

SCHEDULE:

1. Introductions



The meeting was opened by Amy Malinoski introducing herself and the Gap Analysis Project. Amy works for TreCom Systems Group based out of Philadelphia with an office outside of Harrisburg which works on various projects with the Commonwealth. Her background with information technology projects includes analysis, testing, training, documentation, design, etc. The Gap Analysis Project has been undertaken by DCNR to evaluate all of the well systems in place at DCNR and to determine the gaps with those systems and the ultimate goal of all of these systems being on the same database schema and same code base. Several meetings have been conducted to this point regarding the systems included and those meetings have included a lot of information on WIS and PA*IRIS and suggestions for the new system. The purpose of this meeting is to hear from industry representative directly regarding their usage of the system and their suggestions for the new system. Cat Mathias introduced herself. She is responsible for supporting the geologists and geophysicists and uses PA*IRIS everyday. Her company uses the state’s data in their database. She also is responsible for supporting other employees with their use of PA*IRIS and WIS. Tom Metarko is a District Geologist. He has used PA*IRIS to pull up geophysical logs and completion reports. He is also interested in production data. Carla Blocksum is a Geoscience Technician. She uses PA*IRIS for completion reports and location plats. The true latitude/longitude data from Location Plats in PA*IRIS is used in WellBase which is a Geographix product. She also reviews the geophysical logs. Sue Carulli is a Geologist. She uses WIS more than PA*IRIS. She double checks all of the data in WIS prior to loading it into the company’s systems. She would like the target formation and bottom hole coordinates to be available in WIS. The reports are used to supply data to their system. Dennis Carulli is an independent Geologist consultant. He uses PA*IRIS often, but not everyday. His main focus is on data extraction to use the data in spreadsheets to conduct various analysis activities. He doesn’t have a mapping program. Greg Wrightstone supervises the data input for his company. He would like more information on horizontal wells and would like directional wells to be flagged. As an example, Greg noted that they want to see both total measured depth (TMD) and true vertical depth (TVD) for directional wells. Kristin Carter is the Section Chief for DCNR. She oversees the group responsible for the scanning of documents and entering of data that is available through PA*IRIS and WIS. She reviews Completion Reports, interprets stratigraphy, etc. 2. Overview of the usage of PA*IRIS by industry representatives The consensus of the group was that everyone uses PA*IRIS. They use both the version that is available through Citrix as well as the web version. (The Citrix version allows direct access to PA*IRIS where the web version requires navigation to another website.) With the web version they have the ability to print. A few are able to print using the version through Citrix, but not many. PA*IRIS provides the following document types: Completed Base Map Quadrangles, Completion Report, Historical Records, Location Plat, Plugging Certificate, and Quadrangle Section Map. The maps are not needed if the operator has a mapping application. The maps



are 5 years old. Completion Reports and Location Plats are used heavily. Plugging Certificates are also used, but not to the extent of Completion Reports and Location Plats. Historical Records can be used to lookup data available on older wells. There was a question regarding the directional surveys that are submitted as part of the completion report. If a directional survey is included as part of a completion report, it is scanned and included in PA*IRIS, but there is no way to look specifically for directional surveys in PA*IRIS. An issue was noted where PA*IRIS doesn’t allow the user to indicate which pages to be printed. When using PA*IRIS on the web (web version of OnBase), the user is able to indicate the pages to print as illustrated in the following screenshot in the print range portion of the dialog box:

It should also be noted, that if the user’s computer has Adobe PDF, that the documents can be printed to PDF documents. 3. Overview of the usage of WIS by industry representatives The functionality/search capability available on the Inquire Well Details screen is satisfactory. The fields that allow for searching are adequate. The need to do a partial name search on the Farm Name was discussed. This is possible in WIS using the “%” before and after the search criteria. For instance if the user is searching for all Farms with Smith in the name, the search would be %Smith%. The data on the Inquire Well Details screen would be the kind of header information desired for the well in a new system. One of the main topics discussed with respect to WIS was the API number. The usage of the 14 digit API is highly desired by industry. It was discussed that DEP is presently issuing new permits for sidetracks. Amy explained that the need for the 4 digit suffix on the API number has been discussed, but without mandate from DEP, it may be difficult to implement.



The location data in WIS was also discussed and the Datum being used. The decimal lat/long data in WIS is presently in NAD 27. It has not yet been converted to NAD 83. Some industry representatives indicated that they thought the conversion had been done. It would be nice if the system did the NAD 27 / NAD 83 conversions on the fly, and/or stored all of the values. Also desired is location data for the bottom hole. The concept of a “project” with respect to oil/gas wells does apply to those situations where the production of the wells is pooled. It would be nice if WIS included information on the formation names of the intervals on the perforation and stimulation data. (It was mentioned that John Harper has suggested that the perforation and stimulation data include the amount of water and sand and the injection information.) The geologists in Pittsburgh are responsible for interpreting the formations for the well, so it might be possible to use that information to provide the system with the information for it to determine the formations in the perforation and stimulation intervals. It would be nice if the documents were integrated with the associated well. This includes integrating the geophysical logs rather than having them on the FTP site. The information on the Geophysical Log screen is not used external to DCNR. The file name stored on this page is to be used internally by DCNR staff. The production data was discussed briefly. Apparently, production data from January 2009 to June 2009 cannot be found on the DEP site. It was verified that condensate is to be included in the production data as a result of the PA Act 15 and the usage of OGRE. The production data screen in WIS is not used. The industry representatives indicated that they dump this data and use it in their own systems without using the screen in WIS. Wells plugged after 1956 but drilled prior to 1956 do not have permit numbers. The old permit numbers are not cataloged. Only API’s are cataloged. The question was asked regarding whether or not DEP cancels permits. This requires further investigation. 4. Overview of the usage of WIS Reports by industry representatives A list of WIS reports was supplied along with the agenda for the meeting. The reports available to a user vary by user. The following reports were indicated as being used: MonthlyLogs.DIS, Marcellus Producing Wells.DIS, PAIRIS_Monthly Logs.DIS, and Pairis Monthly Completion Reports.DIS. There was also discussion about Monthly Plats.DIS and Pairis New Location Plats.DIS and uncertainty as to whether or not these reports were redundant. Expired Plats and PAIRIS_Expired Location Plats also may be the same report. Further investigation is needed to determine the necessary reports. Often times the reports needed by industry require custom development. This is done with Oracle Discoverer. Some of the reports requested by industry cannot be created. Often this involves combining the information from several of the canned reports together. An example is a report that combined the Well Summary Report, Well Header information, and perforation and stimulation data. A report with all of this data cannot be built in Oracle Discoverer. The other report needed incorporates the geophysical logs into an existing report which cannot be done presently with the design of the database.



The key need for the industry operators is to be able to extract the data from WIS to then be loaded in the system used by the operator. This could be PETRA®, WellBase, other Geographix products, etc. The data extracted is typically reviewed and corrected if errors are found prior to it being loaded. There is also a need for ad hoc queries for those partners that use the data directly to perform analysis. It was mentioned that this need usually needs to be evaluated for user training issues as well as system performance issues. The need for industry to extract the data will require much further analysis in the development of the new system to ensure that the needs are met. 5. Overview of the usage of the FTP site The geophysical logs are very important to the industry operators. It would be preferable if the geophysical logs were connected to the well in WIS rather than having to use the FTP site (which permits downloads of only one log at a time). This includes having all logs available for the well in WIS if the well has multiple geophysical logs. Industry operators would also like the ability to download geophysical logs in batches according to search criteria such as area, operator, county, quadrangle, section, township and lat/long. The geophysical logs are to be submitted electronically (DEP mandate). The color tiff logs take a long time to download. LAS files are much faster to download. 6. Requirements of a new system Many of the requirements of a new system were identified throughout the discussion. At the conclusion of the meeting, the following were also reiterated – the need for a flag for deviated wells and the bottom hole coordinates. Additional items that have been identified previously that were mentioned with the group include recording the target formation information, recording the engineering data (casing, stimulation and perforation specifics), and providing dynamic GIS mapping. Follow-up Meetings in Pittsburgh on October 20, 2010 Met with Lynn Levino Discussed the eFACTS transfer. She indicated that there was a problem with the eFACTS transfer lately that was causing some problems, but that has been fixed. There are instances where the information isn’t in WIS yet and that is most often caused when the paperwork is received by DEP in Pittsburgh. The DEP office in Pittsburgh is across the street from DCNR and the paperwork can be received faster than the data transfer. To see each of the completion reports for a well that has more than one, the down arrow can be used. On the user interface if the “Prods” value is greater than 0, that means that the well has more than one year of production information. Log requests are no longer used in WIS. This used to track the requests for geophysical logs from operators. The administrative accounting and billing is handled external to WIS. The subscribers are maintained in an Excel spreadsheet along with their payment information. There is also a



Services database that is an application that stores information on the services provided to various external stakeholders along with the fees for those services. Met with Pedro Forero Pedro demonstrated for me how he sets up roles in the system. He has a special icon available in PA*IRIS to configure user accounts. Met with Kristin Carter Briefly discussed the Carbon Sequestration Database. The Carbon Sequestration Database Design Report documents the potential design of a database that would incorporate all of the information gathered by DCNR during the carbon sequestration project. An abundance of information was collected during the project that could be useful moving forward. This database design is conceptual in nature and inventories all of the data products available as a result of the carbon sequestration project. There is a significant amount of analysis data and interpretations of logs available. This is something that could potentially be integrated into the eventual well information system. Completion reports are not completed by DEP. DEP is to inspect the well upon its completion prior to approving the completion report. The operators complete the completion report and submit it to DEP. The delay in the submission of this paperwork is often caused by the interpretation of “completion” by the operator. This term is not specifically defined, and therefore, the operators may delay submitting the information until the stimulation is complete even if there is a significant delay from the time the well drilling is completed. Some operators will submit interim completion reports and then update with an amended completion report. In the Industry Focus Group meeting, there was some discussion about IHS’s data not being accurate. Kristin explained that IHS is a partner with PA*IRIS and gets the data from WIS that is then used in their software application. WIS is considered the official source of well data within the Commonwealth. Apparently there have been some issues with IHS manipulating the data and in the process the location information is adversely affected. The interpreters in WIS refers to the geologists that interpret the stratigraphy based on the information for the well. Discussed the custom reports in Oracle Discoverer. The users have mentioned on several occasions that creating custom reports is difficult because of the design of the database. We discussed specifically what the users are attempting to do. In Oracle Discoverer a canned report is opened and the desire is to add information to the report. However, the additional data to be added to the report is grayed out and the data fields cannot be added. Discussed the needs of the department with respect to well data as compared to using a package already available (e.g., PETRA® or Geographix). This was brought up because most of the industry representatives mentioned that they take the data from WIS and load it into their application and many of them use WellBase (a Geographix product). These products are expensive and require subscriptions. Also, if the Commonwealth were to use one of these products, industry would still want to dump the data from the Commonwealth and review it prior to using it in their own application. These products also include more functionality than is needed by the Commonwealth for recording the data from location plats, completion reports, plugging certificates, production reports, and geophysical logs.



The desire is to have a vendor onsite by the end of the year to begin development of the new solution. Met with the staff from the Pittsburgh office together (Kristin, Lynn, Katie, Jaime, Joe, and Pedro) Discussed the functionality available via the menu in WIS. This includes the menu options for Block, Field, and Record. These are not used. Discussed the Previous and Next options. These are used to navigate to the previous and next records when more than one record is returned in the search results. The reports available in WIS (not WIS Reports) include the following:

Well Details

Error List

Discoverer Reports

Exploratory vs Development Success

Completion by Age

Field Production

Exploratory and development drilling

New Wells Of these reports, the Well Details and Discoverer Reports don’t work. Lynn indicated that she thought the Discoverer Reports were supposed to be implemented within WIS, but this was never completed. The Error List is the only report that anyone indicated as being used. In addition to reviewing the reports in WIS, the various forms that are accessible for the roles (menu options under Applications) were also reviewed. The following are used:

Location Plats

Completion Reports

Plugging Certificates

Geophysical Logs

Filter prods

Inquire Wells

Modify Location

Stratigraphy

Modify Wells The following forms (menu options under Applications) are not used:

Log Requests

Rock Samples

Well Formations

Rock Units

Formation Alias The DRF role in WIS was used by the Draftsperson. This person was responsible for spotting the wells on the map. No one presently on staff does only this, and the geologists have picked up this task during their completion report processing; therefore, this role is no longer used.



No one in Pittsburgh was familiar with the SCO role. This is the Statistical Data Coordinator role. The thought was that this was Cheryl’s role when the system was built. No one in Pittsburgh was familiar with the IDU (Interdepartmental Users) role either. I updated the group on the actions items I had from the last meeting in Pittsburgh.

Crosswalk of reports in WIS to those available through IRIS in WIS Reporting o I just received access to the reports in WIS for all roles on 10/15; however, based

on my initial inspection, the reports in WIS Reporting are different from those available in WIS.

Review eFACTS process to better understand the data transfers between WIS and eFACTS and to understand problems that have occurred.

o I have reviewed the eFACTS process and understand that an issue was encountered last week and it has been fixed. Also learned that there can be a delay in receiving the data in WIS because the paperwork comes from across the street at DEP in Pittsburgh.

Investigate how the production data will be provided in WIS going forward with the usage of OGRE. It is vital to WIS that the production data be available.

o Explained that I have had follow-up meetings to discuss WIS, OGAPS and OGRE. At this point in time the exact process to get data from WIS to OGRE has not been identified, but it is being addressed. Either DEP will provide the whole OGRE database to WIS or a process will be used to supply the data needed by WIS.

Investigate what, if anything, can be done to remedy the situation with Base Maps. o The issue with Base Maps has to do with an upgrade to ArcGIS 9.3 on the

desktops, but the version published to Citrix is ArcGIS 9.1. This is causing the problem. Those who need to be aware of the problem are.

Investigate the different levels of access in WIS for the different roles. We need to do a full accounting of the system and all of its functionality. It appears that there is a fair amount of functionality that is not being used. Therefore, we will need the different roles to further investigate this.

o As of 10/15, I now have all roles and have been able to account for all functionality in WIS. I have followed up with some questions to which the answers have been supplied in this document.

Gather an understanding of the FTP site and its history. o I spoke with Sandip briefly about the FTP site, but further information is needed.

Develop an architecture diagram. o A draft architecture diagram has been developed and supplied to DCNR staff.

Input is needed to complete the diagram. At the conclusion of the meeting, I reviewed binders with information kept about the development of WIS. I learned that WIS was converted in 2002 to Oracle Forms 6i. A vendor was responsible for this conversion. I also located a list of all of the forms in WIS so that I am able to cross check the functionality to the forms. I found a data model of the original database built for WIS and an architecture diagram for WIS. Interview Notes for PaGWIS and WebDriller Interview conducted with Al Smith on 10/4/2010 at 1:30 WebDriller is used for the licensing and permitting of equipment.



Completion reports for each well drilled are also entered and stored in WebDriller. Location data:

Critical information to have

County is required

Municipality and quadrangle are optional

User supplies decimal latitude and longitude

Once latitude and longitude is entered, the coordinates are checked to ensure that they are in the county supplied. If the municipality and quadrangle are also supplied, then the coordinates are checked for those as well.

There is no mapping associated with WebDriller; however, the application does provide the ability to view a map to see the location on a map (a Microsoft Mapping API).

Total depth is also required information. This is considered the well depth. The borehole can be deeper than the well depth. WebDriller incorporates a driller’s log. The data stored includes the top and bottom depths and a text field to describe the rock in that interval. Because the description is a textbox, a variety of values can be entered in this field. Borehole information must also be entered (at least one entry). A borehole can have different sections because of the varying diameters of the borehole. Casing information can also be entered; must first have a borehole record. Water bearing zone data is another tab where data can be entered. There can be multiple water-bearing zones. The well yield from the water bearing zone is different from the well yield for the well in general. The report can be printed so that it can be provided to the owner. Once it is printed for the owner, it cannot be edited. WebDriller and PaGWIS use two different databases. PaGWIS is a SQL Server 2000 database. WebDriller is a SQL Server 2005 database. The schemas between the two are not the same. There is an interface between WebDriller and PaGWIS that is supposed to run once a week on Sunday nights. However, this interface has not been functioning for some time. PaGWIS does not have a user interface; therefore, the only way to populate data in PaGWIS is through the WebDriller interface which is not presently functioning. PaGWIS is available on the DCNR website. It includes the ability to view an individual well record from the data stored in SQL Server. It also includes the ability to export data in an Access database. The data is dumped from SQL Server to Access by county and for the entire state, is zipped up and the file is provided on the website. This process stopped working several years ago so although the modified date on the website indicates 2009, the data is actually from 2005. Therefore, there is no data available via PaGWIS for 2005 on. Abandoned wells can be entered into WebDriller.



Drillers can also deepen wells or clean them out. These are all options in the Type of Activity field. Date drilled is missing for many of the records in PaGWIS. Auditing is not used. No imaging is used at this point in time. Another item to consider is underground stream data. This is to be discussed with Gary Fleeger and Stuart Reese. Interview conducted with Gary Fleeger and Stuart Reese on 10/5/2010 at 1:00 WebDriller replaces the use of paper records. There are a few drillers that still supply paper records. With the new WebDriller, all drillers must supply decimal lat and long. They do not record offsets and they do not use true lat/long (degrees, minutes, seconds). However, some drillers don’t know the decimal lat/long so there have been issues with the entry of data. Extractions from WebDriller cannot be done from the new WebDriller – they must ask Al Smith or John Clucker for the data. They do not have any need for XYZ coordinates for wells. The Commonwealth of PA does not regulate private water drilling. One of only 2 states where that is the case. There is no dedicated staff for water wells. Therefore, data entry has been a problem. Because of the time needed to answer questions, they do not have as much time as they would like for research work. There are approximately 389,000 well records in PaGWIS. 150,000 of those do not have lat/long information. The geologic, hydrologic and well construction data are also missing for these wells. The other 150,000 have no well address or driller’s (lithologic) log. The coordinates for these are unreliable. The remainder of records are good. There are approximately 300,000 records that are missing from PaGWIS. This includes the paper records received from 2005 – 2009. (There are approximately 15,000 wells drilled per year in the Commonwealth.) Act 610 governs water well drilling. This Act indicates that the driller must be licensed and the drill rig must be licensed. There are fees involved for both. The Act also indicates that completed well records are to be submitted within 21 days of completion of the well. This doesn’t typically occur because the drillers tend to do completion reports in batches. Licensing and permitting fees go to the General Fund. Act 610 also requires that water well data be publicly available and accessible. Well abandonments are entered in WebDriller; however, the data entry is awkward. There are no regulations on plugging wells. PaGWIS data usage:



DCNR uses the data to map bedrock, to conduct groundwater studies, to study aquifers and their depths, etc. (Aquifers are not the same as fields or pools.) Data is also used by DEP. Permitting process for DEP may require inventory of all wells within a certain area and with the current state of PaGWIS, this cannot be provided completely. Timeline for these systems: In the 80’s they used a system called Water Well Inventory which used one of the legacy database platforms (possibly ENABLE or dBase). The well records were submitted on paper. The Water Well Inventory system was later moved to Access and a CD of the data was sold. This was the start of PaGWIS. PaGWIS was eventually migrated to SQL Server. In 1998 they introduced the original WebDriller so that drillers could voluntarily complete their reports online. In 2009 WebDriller was moved to the new WebDriller application and it was mandated that all completion reports be submitted through WebDriller; although, there are drillers who still submit the paper copies. The data was transferred from WebDriller to PaGWIS through the interface. Data doesn’t always match between what is retrieved from PaGWIS when viewing records online and using the Access extraction. This seems to be tied to record keys and ID’s. Also, in the Access data extraction there are records missing data, particularly the water level. The water level is missing for approximately 70,000 records. It seems as though the data was corrupted somewhere along the line. However, there is a CD of the Access database prior to the conversion to SQL Server that does have complete records. Because PaGWIS doesn’t have an interface there is no way to update location information if it is improved upon. Also, if old wells are found when doing field surveys, they cannot be entered. Functionality desired for PaGWIS:

The interface between PaGWIS and WebDriller should be repaired. However, with the desire to move to a single database schema, this functionality becomes moot. With a single database schema, an interface is not needed.

Provide an interface to the PaGWIS data to allow updates to the information.

Mapping would be desirable at some point, but presently the location data for most wells is unreliable.

Additional search capabilities for the users of PaGWIS are desired, particularly the ability to search by well address.

Data cleansing so that the data is complete and accurate. This mostly entails cleaning up the 300,000 records that are in PaGWIS for which the data is incomplete.

Functionality desired for WebDriller:

Providing the name of the county, municipality or quadrangle where the coordinates entered may be found if it differs from the county, municipality or quadrangle entered.

Allowing the user to save the record even if errors exist.

Allowing entry of Decimal values in all numeric fields.

Ability to print a well record by Topo/Geo personnel. At present only drillers can print the well record.

Gary and Stuart did not indicate a need to capture any data specific to underground streams. Interview Notes for additional interviews concerning WIS and PA*IRIS Conducted interview with Toni regarding CBM (CBM) wells at 3:00 on 10/6/2010



Production data is critical to Toni’s work. eFACTS has a flag for CBM wells. When these wells populate in WIS, the Well Type field is set to CBM. This isn’t always the case, but Toni is able to identify certain wells as CBM wells. Often wells less than 2000 feet depending on the county are CBM wells. Toni doesn’t manipulate the data. She is using the data from the well record and building a database with the production data so that she is able to manipulate the data in Access – subtotals, etc. She is also supplementing the data from WIS with additional data. With the Access database she will have the ability to meet her reporting requirements. Toni responds to service requests that are specific to CBM wells. Often these are requests that she receives directly, but in some instances, the requestors contact Pittsburgh first. Toni uses the well record (completion report) and location plat images stored in PA*IRIS to cross-check the information in WIS. She also uses the geophysical logs stored on the FTP site. Conducted interview with Cliff at 3:40 Cliff conducts a number of shallow geologic projects and uses the data stored in PA*IRIS (the images) heavily. He is particularly interested in the geophysical logs and the location plats. He has a direct link to the FTP site which he uses heavily. (The FTP is the location where the geophysical logs are accessible.) He has noticed scale problems with some of the scanned location plats. He also is not able to print from PA*IRIS. This is an issue that was raised while in Pittsburgh. The web version of OnBase must be used to be able to print from it. Cliff rarely uses WIS reports. Notes from other meetings Meeting with Sue Coia on 10/6/2010 eFACTS Weekly batch on Sunday nights to provide permit data and driller information. When the well is completed, DEP is to inspect the well and a completion report is completed. OGAPS There are two points of entry for production information. The usage of OGAPS to enter production data is available for operators only. Using their OGO number, the operator can log into OGAPS and report their production information. The second point of entry is for the operator to submit a paper report to DEP. DEP then enters the information into WIS. There is a holding area in WIS where the production data is stored. A number of validations and business rules are applied to the data stored prior to it being moved to the final tables in WIS. Meeting with Seth Greiner on 10/12/2010



OnBase has a proprietary schema. Physcially, the database is in Oracle, but the schema is not accessible. The database doesn’t hold the scanned images; it holds the file structure of the scanned images. There is a server at BIT for the WIS database that is at DCNR on the 4th floor. This database also has the schema for the Stratigraphic database as well as an OnBase schema. The external servers are at CTC. PA IRIS 1 has Citrix, Oracle Forms and Oracle Discoverer. PA IRIS 2 has the OnBase schema. PA IRIS 3 is not presently used. It was initially to be used as a backup, but it is not being used in that capacity at this time. NRWIS01 – internal DCNR server that has the WIS database schema NRWIS00 and NRWIS02 are both located in Pittsburgh. One is used for BaseMaps (ArcGIS) and the other is used for Citrix, Oracle Forms, and Oracle Discoverer. The issue with BaseMaps is related to the upgrade of the client side of ArcGIS to 9.3 and the version published to Citrix has not been upgraded. With respect to the eFACTS transmission process – this is a nightly process which is fairly complicated. The process includes a number of Oracle packages that run. These packages create some tables on the fly and will use some tables that already exist in the schema used. These tables are prefixed with “EFACTS”. There are three tables in particular that are affected by the transfer – Loc Plats, Wells and Clients. User maintenance is done within Oracle. There are no user tables within the database schema. Instead, for each user a database account is created and the appropriate role is assigned. We reviewed the possible roles and there are many. Roles exist for each of the forms in the application. Discussion with Dave Barner (TreCom Systems Group) on 10/13/10 There are two pieces to OGRE – OGRE which allows for data entry and OGRE Reporting which will be the publicly available reporting site (it has not been deployed as of yet). Currently, OGRE is being used for only Marcellus Shale reporting. However, there have been some issues with operators providing production data on non-Marcellus Shale wells. The data that is entered into OGRE is fed to OGRE Reporting to generate the reports for the general public. OGAPS is still being used and will be until sometime in November/December. At that time OGAPS will be shut down and OGRE will be used for all production reporting. The interface for OGRE is very similar to that of OGAPS. The operators have to register for an account, and when they do so, they have to provide their OGAPS password because the information has been brought over from OGAPS. In OGRE Reporting, the information can be searched by county, by operator and by waste management facility.



Presently DEP is focused on building the interface of data between eFACTS and OGRE because presently the data is coming from OGAPS. When OGAPS is turned off, that feed will no longer function. (Note: OGAPS gets its data from WIS which gets its data from eFACTS) Sally Fiscus is the liaison between DCNR and DEP. Additional information from Sandip Only the users in Pittsburgh use the internal version of Citrix. Everyone else accesses WIS via PA*IRIS including DCNR staff in Middletown and Harrisburg and DEP users.



Appendix B. Database Models The database models have been stored on the Sharepoint site in a folder titled “Data Models”. The following link will take you to the folder from which you can access each of the data models. There is a data model for PaGWIS, WebDriller, and WIS. http://nrshrpnts02/wdgap/Project%20Documentation/Forms/AllItems.aspx?RootFolder=%2fwdgap%2fProject%20Documentation%2fGap%20Analysis%20Report%2fData%20Models&FolderCTID=&View=%7b027CD669%2d3ED8%2d4F3F%2d8A0F%2d173352F44B6A%7d

http://nrshrpnts02/wdgap/Project%20Documentation/Forms/AllItems.aspx?RootFolder=%2fwdgap%2fProject%20Documentation%2fGap%20Analysis%20Report%2fData%20Models&FolderCTID=&View=%7b027CD669%2d3ED8%2d4F3F%2d8A0F%2d173352F44B6A%7d





Appendix C. Data Dictionary - WIS table name column

ID column name data type nullable

AD_FUNTREE 1 EL_ID NUMBER Yes

AD_FUNTREE 2 PARENT NUMBER Yes

AD_FUNTREE 3 ELEMENTARY VARCHAR2(1 BYTE) Yes

AD_FUNTREE 4 COMMON VARCHAR2(1 BYTE) Yes

AD_MENU 1 MOD_ID NUMBER Yes

AD_MENU 2 MODTITLE VARCHAR2(240 BYTE) Yes

AD_MENU 3 MODTYPE VARCHAR2(20 BYTE) Yes

AD_MENU 4 MOD_SHORT_NAME VARCHAR2(20 BYTE) Yes

AD_MENU 5 MOD_NAME VARCHAR2(40 BYTE) Yes

AD_MENU 6 MOD_LANGUAGE_ID NUMBER Yes

AD_MENU 7 BUN_NAME VARCHAR2(100 BYTE) Yes

AD_MENU 8 BUN_ID NUMBER Yes

AD_MENU 9 PARENT_NAME VARCHAR2(100 BYTE) Yes

AD_MENU 10 PARENT_ID NUMBER Yes

AD_MENU 11 PARENT_LEVEL NUMBER Yes

AD_MENU 12 SEQ_NO NUMBER Yes

AD_MOD 1 MOD_ID NUMBER Yes

AD_MOD 2 FUN_ID NUMBER Yes

AD_MOD 3 ELEM_FLAG VARCHAR2(10 BYTE) Yes

AD_MOD 4 RESPONSE VARCHAR2(20 BYTE) Yes

AD_MOD 5 COMMON_LIST VARCHAR2(240 BYTE) Yes

AD_MOD 6 INPUT_PARAMS VARCHAR2(240 BYTE) Yes

AD_MOD 7 OUTPUT_PARAMS VARCHAR2(240 BYTE) Yes

AD_MOD 8 BUNS VARCHAR2(240 BYTE) Yes

AD_MOD 9 ENT_USAGE_LIST VARCHAR2(240 BYTE) Yes

AD_MOD 10 ATT_USAGE_LIST VARCHAR2(240 BYTE) Yes

AD_MOD 11 ENTS_AS_TABLES VARCHAR2(240 BYTE) Yes

AD_MOD 12 ENTITIES VARCHAR2(240 BYTE) Yes

AD_MOD 13 ATTRIBUTES VARCHAR2(240 BYTE) Yes

AD_MOD 14 CHILDREN NUMBER Yes

AD_MOD 15 DESCENDANTS NUMBER Yes



table name column ID

column name data type nullable

AD_MOD 16 ELEM_DESCENDANTS NUMBER Yes

AD_MOD 17 COMM_DESCENDANTS NUMBER Yes

AD_MOD 18 PARENTS NUMBER Yes

AD_MOD 19 ANCESTORS NUMBER Yes

AD_MOD 20 ELEM_ANCESTORS NUMBER Yes

AD_MOD 21 COMM_ANCESTORS NUMBER Yes

AD_MOD 22 MOD_TMP NUMBER Yes

AD_MOD 23 OLD_MOD_ID NUMBER Yes

AD_MOD 24 NEW_MOD_ID NUMBER Yes

AD_MOD 25 MOD_SHORT_NAME VARCHAR2(20 BYTE) Yes

AD_MOD 26 MOD_NAME VARCHAR2(40 BYTE) Yes

AD_MOD 27 MOD_PURPOSE VARCHAR2(70 BYTE) Yes

AD_MOD 28 MOD_TYPE VARCHAR2(10 BYTE) Yes

AD_MOD 29 MOD_LANGUAGE_ID NUMBER Yes

AD_MODFUN 1 MOD_ID NUMBER Yes

AD_MODFUN 2 FUN_ID NUMBER Yes

AD_MODNOTES 1 MOD_ID NUMBER Yes

AD_MODNOTES 2 SEQ NUMBER Yes

AD_MODNOTES 3 NOTE_DESC VARCHAR2(1 BYTE) Yes

AD_MODNOTES 4 TEXT VARCHAR2(240 BYTE) Yes

AD_MODPARAMS 1 MOD_ID NUMBER Yes

AD_MODPARAMS 2 PARAM_ID NUMBER Yes

AD_MODPARAMS 3 INPUT_OUTPUT VARCHAR2(10 BYTE) Yes

ANNUAL_PRODUCTION_REPORTS 1 ID NUMBER(9,0) No

ANNUAL_PRODUCTION_REPORTS 2 CLIENT_ID NUMBER(9,0) No

ANNUAL_PRODUCTION_REPORTS 3 PROD_YEAR NUMBER(4,0) No

ANNUAL_PRODUCTION_REPORTS 4 OPERATOR_REMARK VARCHAR2(100 BYTE) Yes

ANNUAL_PRODUCTION_REPORTS 5 OG_REMARK VARCHAR2(100 BYTE) Yes

ANNUAL_PRODUCTION_REPORTS 6 DATE_OF_RCPT DATE Yes

ANNUAL_PRODUCTION_REPORTS 7 BTGS_REMARK VARCHAR2(100 BYTE) Yes

ANNUAL_PRODUCTION_REPORTS 8 TYPE_OF_CREATION VARCHAR2(2 BYTE) Yes

ANNUAL_PRODUCTION_REPORTS 9 DATE_OF_CREATION DATE Yes

ANNUAL_WELL_PRODUCTIONS 1 ID NUMBER(9,0) No





ANNUAL_WELL_PRODUCTIONS 2 APRW_ID NUMBER(9,0) No

ANNUAL_WELL_PRODUCTIONS 3 PRODUCT_ID NUMBER(4,0) No

ANNUAL_WELL_PRODUCTIONS 4 QUANTITY NUMBER(10,2) Yes

ANNUAL_WELL_PRODUCTIONS 5 OPERATING_DAYS NUMBER(3,0) Yes

APR_WELLS 1 ID NUMBER(9,0) No

APR_WELLS 2 APR_ID NUMBER(9,0) No

APR_WELLS 3 WELL_ID NUMBER(6,0) No

APR_WELLS 4 WELL_POOL_ID NUMBER(4,0) Yes

APR_WELLS 5 WTYPE_ID NUMBER(2,0) Yes

APR_WELLS 6 STATUS_ID NUMBER(1,0) Yes

APR_WELLS 7 TANK_METER_NO VARCHAR2(15 BYTE) Yes

APR_WELLS 8 PROD_GRP_NO NUMBER(6,0) Yes

APR_WELLS 9 HW_TYPE VARCHAR2(1 BYTE) Yes

APR_WELLS 10 CLIENT_MATCH NUMBER(1,0) Yes

APR_WELLS 11 NO_DUPLICATE NUMBER(1,0) Yes

APR_WELLS 12 WTYPE_MATCH NUMBER(1,0) Yes

ARC_WELLSX_TT 1 REJECTED NUMBER Yes

ARC_WELLS_ERR 1 PERMIT_NUMBER VARCHAR2(15 BYTE) Yes

ARC_WELLS_ERR 2 AUTH_ID NUMBER(10,0) Yes

ARC_WELLS_ERR 3 PROJECT_NO VARCHAR2(10 BYTE) Yes

ARC_WELLS_ERR 4 REG_STATUS VARCHAR2(2 BYTE) Yes

ARC_WELLS_ERR 5 COUNTY VARCHAR2(25 BYTE) Yes

ARC_WELLS_ERR 6 MUNICIPALITY VARCHAR2(60 BYTE) Yes

ARC_WELLS_ERR 7 SLOC_ID NUMBER(9,0) Yes

ARC_WELLS_ERR 8 ELEVATION NUMBER(4,0) Yes

ARC_WELLS_ERR 9 FARM_NAME VARCHAR2(40 BYTE) Yes

ARC_WELLS_ERR 10 FARM_WELL_NO VARCHAR2(10 BYTE) Yes

ARC_WELLS_ERR 11 CO_SRL_NO VARCHAR2(10 BYTE) Yes

ARC_WELLS_ERR 12 CLIENT_ORGANIZATION VARCHAR2(60 BYTE) Yes

ARC_WELLS_ERR 13 CLIENT_ID NUMBER(9,0) Yes

ARC_WELLS_LOCPLAT_TT 1 PROCEDURE_NAME VARCHAR2(20 BYTE) Yes

ARC_WELLS_LOCPLAT_TT 2 COMMIT_RATE NUMBER(9,0) Yes

ARC_WELLS_LOCPLAT_TT 3 LOW_BOUND NUMBER(9,0) Yes





ARC_WELLS_LOCPLAT_TT 4 HIGH_BOUND NUMBER(9,0) Yes

ARC_WELLS_LOCPLAT_TT 5 LOAD_DATE DATE Yes

ARC_WELLS_STATUS_TT 1 PROCEDURE_NAME VARCHAR2(20 BYTE) Yes

ARC_WELLS_STATUS_TT 2 COMMIT_RATE NUMBER(9,0) Yes

ARC_WELLS_STATUS_TT 3 LOW_BOUND NUMBER(9,0) Yes

ARC_WELLS_STATUS_TT 4 HIGH_BOUND NUMBER(9,0) Yes

ARC_WELLS_STATUS_TT 5 LOAD_DATE DATE Yes

AUTH_REQ_SITES_OLD 1 AUTHREQ_ID NUMBER(10,0) No

AUTH_REQ_SITES_OLD 2 SITE_ID NUMBER(9,0) No

BOGM_ANNUAL_PRODUCTION_REPORTS 1 ID NUMBER(9,0) No

BOGM_ANNUAL_PRODUCTION_REPORTS 2 BAPR_ID NUMBER(9,0) No

BOGM_ANNUAL_PRODUCTION_REPORTS 3 PERMIT_NUMBER VARCHAR2(9 BYTE) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 4 FARM_NAME VARCHAR2(40 BYTE) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 5 FARM_WELL_NO VARCHAR2(10 BYTE) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 6 CO_SRL_NO VARCHAR2(10 BYTE) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 7 TANK_METER_NUMBER VARCHAR2(15 BYTE) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 8 HW_TYPE VARCHAR2(1 BYTE) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 9 STATUS_ID NUMBER(1,0) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 10 PROD_GRP_NO NUMBER(4,0) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 11 API_MISMATCH NUMBER(1,0) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 12 FARM_MISMATCH NUMBER(1,0) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 13 CLIENT_MISMATCH NUMBER(1,0) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 14 DUPLICATE_REPORTING NUMBER(1,0) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 15 STATUS_MISMATCH NUMBER(1,0) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 16 WTYPE_MISMATCH NUMBER(1,0) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 17 PROD_MISSING NUMBER(1,0) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 18 PROD_INVALID NUMBER(1,0) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 19 PROD_ZERO NUMBER(1,0) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 20 DAYS_MISSING NUMBER(1,0) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 21 DAYS_INVALID NUMBER(1,0) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 22 SRL_NO_MISMATCH NUMBER(1,0) Yes

BOGM_ANNUAL_PRODUCTION_REPORTS 23 EXPORT_TO_BTGS DATE Yes

BOGM_ANNUAL_PROD_WELLS 1 ID NUMBER(9,0) No





BOGM_ANNUAL_PROD_WELLS 2 DATE_OF_RCPT DATE Yes

BOGM_ANNUAL_PROD_WELLS 3 PROD_YEAR NUMBER(4,0) No

BOGM_ANNUAL_PROD_WELLS 4 CLIENT_ID NUMBER(9,0) Yes

BOGM_ANNUAL_PROD_WELLS 5 OPERATOR_REMARK VARCHAR2(100 BYTE) Yes

BOGM_ANNUAL_PROD_WELLS 6 OG_REMARK VARCHAR2(100 BYTE) Yes

BOGM_ANNUAL_PROD_WELLS 7 BTGS_REMARK VARCHAR2(100 BYTE) Yes

BOGM_ANNUAL_PROD_WELLS 8 TYPE_OF_CREATION VARCHAR2(2 BYTE) Yes

BOGM_ANNUAL_PROD_WELLS 9 CREATED_BY VARCHAR2(30 BYTE) Yes

BOGM_ANNUAL_PROD_WELLS 10 CREATION_DATE DATE Yes

BOGM_ANNUAL_PROD_WELLS 11 MODIFIED_BY VARCHAR2(30 BYTE) Yes

BOGM_ANNUAL_PROD_WELLS 12 MODIFICATION_DATE DATE Yes

BOGM_ANNUAL_WASTE_FACILITIES 1 ID NUMBER(9,0) No

BOGM_ANNUAL_WASTE_FACILITIES 2 BAWP_ID NUMBER(9,0) No

BOGM_ANNUAL_WASTE_FACILITIES 3 FACILITY_NAME VARCHAR2(40 BYTE) No

BOGM_ANNUAL_WASTE_FACILITIES 4 FACILITY_PERMIT_NUMBER VARCHAR2(15 BYTE) Yes

BOGM_ANNUAL_WASTE_METHODS 1 ID NUMBER(9,0) No

BOGM_ANNUAL_WASTE_METHODS 2 BAWF_ID NUMBER(9,0) No

BOGM_ANNUAL_WASTE_METHODS 3 BWDM_ID NUMBER(2,0) No

BOGM_ANNUAL_WASTE_METHODS 4 QUANTITY NUMBER(10,2) Yes

BOGM_ANNUAL_WELL_PRODUCTIONS 1 ID NUMBER(9,0) No

BOGM_ANNUAL_WELL_PRODUCTIONS 2 BAPW_ID NUMBER(9,0) No

BOGM_ANNUAL_WELL_PRODUCTIONS 3 PRODUCT_ID NUMBER(4,0) No

BOGM_ANNUAL_WELL_PRODUCTIONS 4 QUANTITY NUMBER(10,2) Yes

BOGM_ANNUAL_WELL_PRODUCTIONS 5 OPERATING_DAYS NUMBER(3,0) Yes

BOGM_WASTE_DISPOSAL_METHODS 1 ID NUMBER(2,0) No

BOGM_WASTE_DISPOSAL_METHODS 2 NAME VARCHAR2(40 BYTE) No

CG_CODE_CONTROLS 1 CC_DOMAIN VARCHAR2(30 BYTE) No

CG_CODE_CONTROLS 2 CC_COMMENT VARCHAR2(240 BYTE) Yes

CG_CODE_CONTROLS 3 CC_NEXT_VALUE NUMBER(15,0) No

CG_FORM_HELP 1 HLP_APPLN VARCHAR2(30 BYTE) No

CG_FORM_HELP 2 HLP_INDEX VARCHAR2(100 BYTE) No

CG_FORM_HELP 3 HLP_MODTAB_NAME VARCHAR2(30 BYTE) Yes

CG_FORM_HELP 4 HLP_GENERATED VARCHAR2(1 BYTE) Yes





CG_FORM_HELP 5 HLP_SEQ NUMBER(5,0) No

CG_FORM_HELP 6 HLP_TEXT VARCHAR2(70 BYTE) Yes

CG_FORM_HELP 7 HLP_TYPE VARCHAR2(1 BYTE) No

CG_REF_CODES 1 RV_LOW_VALUE VARCHAR2(240 BYTE) No

CG_REF_CODES 2 RV_HIGH_VALUE VARCHAR2(240 BYTE) Yes

CG_REF_CODES 3 RV_ABBREVIATION VARCHAR2(240 BYTE) Yes

CG_REF_CODES 4 RV_DOMAIN VARCHAR2(100 BYTE) No

CG_REF_CODES 5 RV_MEANING VARCHAR2(240 BYTE) Yes

CG_REF_CODES 6 RV_TYPE VARCHAR2(10 BYTE) Yes

CLIENTS 1 ID NUMBER(9,0) No

CLIENTS 2 ORG_NAME VARCHAR2(60 BYTE) No

CLIENTS 3 MAIL_ADDRESS_1 VARCHAR2(45 BYTE) Yes

CLIENTS 4 MAIL_ADDRESS_2 VARCHAR2(45 BYTE) Yes

CLIENTS 5 MAIL_CITY VARCHAR2(30 BYTE) Yes

CLIENTS 6 STATE_CODE_FOR_MAIL VARCHAR2(2 BYTE) Yes

CLIENTS 7 ZIP_CODE_FOR_MAIL VARCHAR2(10 BYTE) Yes

CLIENTS 8 MAIL_COUNTRY VARCHAR2(3 BYTE) Yes

CLIENTS 9 PHONE_NUM NUMBER(15,0) Yes

CLIENTS 10 PHONE_EXT NUMBER(4,0) Yes

CLIENTS 11 FAX_NUM NUMBER(15,0) Yes

CLIENTS 12 SUFFIX VARCHAR2(4 BYTE) Yes

CLIENTS 13 TITLE VARCHAR2(30 BYTE) Yes

CLIENTS 14 FIRST_NAME VARCHAR2(20 BYTE) Yes

CLIENTS 15 MIDDLE_INITIAL VARCHAR2(1 BYTE) Yes

CLIENTS 16 LAST_NAME VARCHAR2(26 BYTE) Yes

CLIENTS 17 SSN VARCHAR2(11 BYTE) Yes

CLIENTS 18 FED_TAX_ID VARCHAR2(9 BYTE) Yes

CLIENTS 19 LOC_ADDRESS_1 VARCHAR2(45 BYTE) Yes

CLIENTS 20 LOC_ADDRESS_2 VARCHAR2(45 BYTE) Yes

CLIENTS 21 LOC_CITY VARCHAR2(30 BYTE) Yes

CLIENTS 22 STATE_CODE_FOR_LOCATE VARCHAR2(2 BYTE) Yes

CLIENTS 23 ZIP_CODE_FOR_LOCATE VARCHAR2(10 BYTE) Yes

CLIENTS 24 BEGIN_DATE DATE Yes





CLIENTS 25 END_DATE DATE Yes

CLIENTS 26 VERIFY_DATE DATE Yes

CLIENTS 27 VERIFY_STATUS_FLAG VARCHAR2(1 BYTE) Yes

CLIENTS 28 CLITYP_CODE VARCHAR2(4 BYTE) Yes

CLIENTS 29 CLISTAT_CODE VARCHAR2(5 BYTE) Yes

CLIENTS 30 EMP_ID NUMBER(6,0) Yes

CLIENTS 31 EMPLOYEE_FLAG VARCHAR2(1 BYTE) Yes

CLIENTS 32 SALUTATION VARCHAR2(4 BYTE) Yes

COLOR 1 SNO NUMBER(5,0) Yes

COLOR 2 BACKGROUND_COLOR VARCHAR2(100 BYTE) Yes

COLOR 3 FOREGROUND_COLOR VARCHAR2(100 BYTE) Yes

COLOR 4 NORMALMODE_COLOR VARCHAR2(100 BYTE) Yes

COLOR 5 QRYMODE_COLOR VARCHAR2(100 BYTE) Yes

COLOR 6 STATUS VARCHAR2(1 BYTE) Yes

COMPLETION_EVENT_TYPES 1 ID NUMBER(4,0) No

COMPLETION_EVENT_TYPES 2 NAME VARCHAR2(40 BYTE) No

COMPLETION_EVENT_TYPES 3 SHORT_NAME VARCHAR2(5 BYTE) Yes

COMPLETION_REPORTS 1 ID NUMBER(9,0) No

COMPLETION_REPORTS 2 WELL_ID NUMBER(6,0) No

COMPLETION_REPORTS 3 CEVTYPE_ID NUMBER(4,0) No

COMPLETION_REPORTS 4 RCPT_DATE DATE No

COMPLETION_REPORTS 5 DC_DATE DATE Yes

COMPLETION_REPORTS 6 PC_DATE DATE Yes

COMPLETION_REPORTS 7 SC_DATE DATE Yes

COMPLETION_REPORTS 8 FROM_DEPTH NUMBER(5,0) Yes

COMPLETION_REPORTS 9 TO_DEPTH NUMBER(5,0) Yes

COMPLETION_REPORTS 10 DEEPEST_RUNIT_CODE NUMBER(4,0) Yes

COMPLETION_REPORTS 11 PRODUCING_DEPTH NUMBER(5,0) Yes

COMPLETION_REPORTS 12 NGF_QUANTITY NUMBER(7,2) Yes

COMPLETION_REPORTS 13 NOF_QUANTITY NUMBER(7,2) Yes

COMPLETION_REPORTS 14 NRP_QUANTITY NUMBER(4,0) Yes

COMPLETION_REPORTS 15 NRP_DURATION NUMBER(4,0) Yes

COMPLETION_REPORTS 16 ATGF_QUANTITY NUMBER(7,2) Yes





COMPLETION_REPORTS 17 ATOF_QUANTITY NUMBER(7,2) Yes

COMPLETION_REPORTS 18 ATRP_QUANTITY NUMBER(4,0) Yes

COMPLETION_REPORTS 19 ATRP_DURATION NUMBER(4,0) Yes

COMPLETION_REPORTS 20 GENCLSS_ID NUMBER(1,0) Yes

COMPLETION_REPORTS 21 SPLCLSS_ID NUMBER(1,0) Yes

COMPLETION_REPORTS 22 EXPTYPE_ID NUMBER(2,0) Yes

COMPLETION_REPORTS 23 WELL_TYPE NUMBER(2,0) Yes

COMPLETION_REPORTS 24 POOL_ID NUMBER(4,0) Yes

COMPLETION_REPORTS 25 OPERATOR_REMARK VARCHAR2(100 BYTE) Yes

COMPLETION_REPORTS 26 OG_REMARK VARCHAR2(100 BYTE) Yes

COMPLETION_REPORTS 27 DRF_REMARK VARCHAR2(100 BYTE) Yes

COMPLETION_REPORTS 28 GEO_REMARK VARCHAR2(100 BYTE) Yes

COMPLETION_REPORTS 29 CREATION_DATE DATE Yes

COMPLETION_REPORTS 30 CREATED_BY VARCHAR2(30 BYTE) Yes

COMPLETION_REPORTS 31 MODIFICATION_DATE DATE Yes

COMPLETION_REPORTS 32 MODIFIED_BY VARCHAR2(30 BYTE) Yes

COUNTY_MUNICIPALITY_XREFS 1 COUNTY_ID NUMBER(4,0) No

COUNTY_MUNICIPALITY_XREFS 2 MUNICIPALITY_ID NUMBER(6,0) No

COUNTY_MUNICIPALITY_XREFS 3 PA_MUNICIPALITY_CODE VARCHAR2(5 BYTE) Yes

COUNTY_MUNICIPALITY_XREFS 4 PERCENT_LAND_AREA NUMBER(3,0) Yes

CR_RESERVOIRS_TT 1 CR_ID NUMBER(9,0) Yes

CR_RESERVOIRS_TT 2 RUNIT_DESCRIPTION VARCHAR2(255 BYTE) Yes

DENGLISH_EXTRACT 1 PERMIT_NUMBER VARCHAR2(15 BYTE) No

DENGLISH_EXTRACT 2 PERMIT_STATUS VARCHAR2(2 BYTE) Yes

DENGLISH_EXTRACT 3 WELL_STATUS VARCHAR2(40 BYTE) Yes

DENGLISH_EXTRACT 4 OPER_NUM VARCHAR2(9 BYTE) Yes

DENGLISH_EXTRACT 5 OPER_NAME VARCHAR2(60 BYTE) No

DENGLISH_EXTRACT 6 OPER_ADDR1 VARCHAR2(45 BYTE) Yes

DENGLISH_EXTRACT 7 OPER_ADDR2 VARCHAR2(45 BYTE) Yes

DENGLISH_EXTRACT 8 OPER_CITY VARCHAR2(30 BYTE) Yes

DENGLISH_EXTRACT 9 OPER_STATE VARCHAR2(2 BYTE) Yes

DENGLISH_EXTRACT 10 OPER_ZIP VARCHAR2(10 BYTE) Yes

DRILLERS_FORMATION_ALIASES 1 ID NUMBER(4,0) No





DRILLERS_FORMATION_ALIASES 2 NAME VARCHAR2(40 BYTE) No

DRILLERS_FORMATION_ALIASES 3 SHORT_NAME VARCHAR2(5 BYTE) Yes

DRILLERS_FORMATION_ALIASES 4 RUNIT_CODE NUMBER(4,0) Yes

DRILLERS_FORMATION_ALIASES 5 RUNIT_TYPE_CODE VARCHAR2(2 BYTE) Yes

DRILLERS_FORMATION_ALIASES 6 FORMATION_TYPE VARCHAR2(2 BYTE) No

DRILLERS_LOGS 1 ID NUMBER(9,0) No

DRILLERS_LOGS 2 WELL_ID NUMBER(6,0) No

DRILLERS_LOGS 3 TOP NUMBER(5,0) No

DRILLERS_LOGS 4 RUNI_CODE_DFOR_ID NUMBER(4,0) Yes

DRILLERS_LOGS 5 FORMATION_TYPE VARCHAR2(2 BYTE) Yes

DRILLERS_LOGS 6 BOTTOM NUMBER(5,0) Yes

DRILLERS_LOGS 7 DEPTH_GAS NUMBER(5,0) Yes

DRILLERS_LOGS 8 DEPTH_OIL NUMBER(5,0) Yes

DRILLERS_LOGS 9 DEPTH_BRINE NUMBER(5,0) Yes

DRILLERS_LOGS 10 DEPTH_FWATER NUMBER(5,0) Yes

DUP_AUTH_REQ_SITES_TT 1 PERMIT_NUMBER VARCHAR2(15 BYTE) Yes

DUP_AUTH_REQ_SITES_TT 2 AUTH_ID NUMBER(10,0) Yes

DUP_CLIENTS_TT 1 PERMIT_NUMBER VARCHAR2(15 BYTE) Yes

DUP_CLIENTS_TT 2 AUTH_ID NUMBER(10,0) Yes

DUP_ERIC_TT 1 SITE_ID NUMBER(9,0) Yes

DUP_OG_WELL_TT 1 ID NUMBER(9,0) Yes

DUP_OG_WELL_TT 2 SITE_ID NUMBER(9,0) Yes

ECR 1 PERMIT_NUMBER VARCHAR2(9 BYTE) Yes

ECR 2 EVENTTYPE VARCHAR2(1 BYTE) Yes

ECR 3 DCYEAR NUMBER(4,0) Yes

ECR 4 TD_DD NUMBER(5,0) Yes

ECR 5 PROD_DEPTH NUMBER(5,0) Yes

ECR 6 ATGF_QUANTITY NUMBER(7,2) Yes

ECR 7 ATOF_QUANTITY NUMBER(7,2) Yes

ECR 8 ATRP_QUANTITY NUMBER(4,0) Yes

ECR 9 ATRP_DURATION NUMBER(4,0) Yes

ECR 10 RESERVOIRS VARCHAR2(23 BYTE) Yes

ECR 11 CEVTYPE_ID NUMBER(1,0) Yes





ECR 12 COMPLETION_DATE DATE Yes

ECR 13 FROM_DEPTH NUMBER(5,0) Yes

ECR 14 TO_DEPTH NUMBER(5,0) Yes

ECR 15 RUNIT_CODE1 NUMBER(4,0) Yes

ECR 16 RUNIT_TYPE_CODE1 VARCHAR2(2 BYTE) Yes







ECR 23 GENCLSS_ID NUMBER(1,0) Yes

ECR 24 SPLCLSS_ID NUMBER(1,0) Yes

ECR 25 EXPTYPE_ID NUMBER(2,0) Yes

ECR 26 WTYPE_ID NUMBER(2,0) Yes

ECR 27 FIELD_ID NUMBER(4,0) Yes

ECR 28 POOL_ID NUMBER(4,0) Yes

ECR 29 DATA_SOURCE VARCHAR2(6 BYTE) Yes

ECR 30 CREATION_DATE DATE Yes

ECR 31 ERROR_CODE NUMBER(9,0) Yes

ECR 32 ERROR_MSG VARCHAR2(255 BYTE) Yes

ECR 33 WELL_ID NUMBER(6,0) Yes

ECR 34 DC_DATE DATE Yes

ECR 35 OPERATOR_REMARK VARCHAR2(100 BYTE) Yes

EDLOG 1 PERMIT_NUMBER VARCHAR2(9 BYTE) Yes

EDLOG 2 TOP NUMBER(5,0) Yes

EDLOG 3 WELL_ID NUMBER(6,0) Yes

EDLOG 4 RUNIT_CODE NUMBER(4,0) Yes

EDLOG 5 RUNIT_TYPE_CODE VARCHAR2(2 BYTE) Yes

EDLOG 6 DATA_SOURCE VARCHAR2(6 BYTE) Yes

EDLOG 7 CREATION_DATE DATE Yes

EDLOG 8 ERROR_CODE NUMBER(9,0) Yes

EDLOG 9 ERROR_MSG VARCHAR2(255 BYTE) Yes





EGEOLOG 1 PERMIT_NUMBER VARCHAR2(9 BYTE) Yes

EGEOLOG 2 TYPE1 VARCHAR2(9 BYTE) Yes




EGEOLOG 6 INTERVAL1 VARCHAR2(11 BYTE) Yes




EGEOLOG 10 AUTHREQ_ID NUMBER(10,0) Yes

EGEOLOG 11 WELL_ID NUMBER(6,0) Yes

EGEOLOG 12 OIL_AND_GAS_CODE1 VARCHAR2(10 BYTE) Yes









EGEOLOG 21 OIL_AND_GAS_COD10 VARCHAR2(10 BYTE) Yes



EGEOLOG 24 TOP1 NUMBER(5,0) Yes

EGEOLOG 25 BOTTOM1 NUMBER(5,0) Yes







EGEOLOG 32 DATA_SOURCE VARCHAR2(6 BYTE) Yes

EGEOLOG 33 ERROR_CODE NUMBER(10,0) Yes





EGEOLOG 34 ERROR_MSG VARCHAR2(255 BYTE) Yes

EGEOLOG 35 LOGTYPE_DER_CODE1 VARCHAR2(2 BYTE) Yes








EGEOLOG_DTL 1 AUTHREQ_ID NUMBER Yes

EGEOLOG_DTL 2 WELL_ID NUMBER Yes

EGEOLOG_DTL 3 LOGTYPE_DER_CODE VARCHAR2(2 BYTE) Yes

EGEOLOG_DTL 4 TOP_INTERVAL NUMBER Yes

EGEOLOG_DTL 5 BOTTOM_INTERVAL NUMBER Yes

EGEOLOG_MISSING 1 OIL_AND_GAS_CODE VARCHAR2(10 BYTE) Yes

EINTSTRAT 1 PERMIT_NUMBER VARCHAR2(9 BYTE) Yes

EINTSTRAT 2 TOP NUMBER(5,0) Yes

EINTSTRAT 3 WELL_ID NUMBER(6,0) Yes

EINTSTRAT 4 RUNIT_CODE NUMBER(4,0) Yes

EINTSTRAT 5 RUNIT_TYPE_CODE VARCHAR2(2 BYTE) Yes

EINTSTRAT 6 DATA_SOURCE VARCHAR2(6 BYTE) Yes

EINTSTRAT 7 CREATION_DATE DATE Yes

EINTSTRAT 8 ERROR_CODE NUMBER(6,0) Yes

EINTSTRAT 9 ERROR_MSG VARCHAR2(255 BYTE) Yes

ELEVATION_TYPES 1 ID NUMBER(4,0) No

ELEVATION_TYPES 2 NAME VARCHAR2(40 BYTE) No

ELEVATION_TYPES 3 SHORT_NAME VARCHAR2(5 BYTE) Yes

EPROD 1 PROD_YEAR NUMBER(4,0) No

EPROD 2 CLIENT_ID NUMBER(5,0) No

EPROD 3 PERMIT_NUMBER VARCHAR2(9 BYTE) No

EPROD 4 FARM_NAME VARCHAR2(20 BYTE) Yes

EPROD 5 CO_SRL_NO VARCHAR2(7 BYTE) Yes

EPROD 6 TANK_METER_NO VARCHAR2(10 BYTE) Yes





EPROD 7 ACTIVE VARCHAR2(1 BYTE) Yes

EPROD 8 INACTIVE VARCHAR2(1 BYTE) Yes

EPROD 9 ABANDONED VARCHAR2(1 BYTE) Yes

EPROD 10 ABANDONEDYEAR NUMBER(4,0) Yes

EPROD 11 STATUS_ID NUMBER(1,0) Yes

EPROD 12 HW_TYPE VARCHAR2(1 BYTE) Yes

EPROD 13 GAS_PRODUCTION NUMBER(10,2) Yes

EPROD 14 GAS_DAYS NUMBER(3,0) Yes

EPROD 15 OIL_PRODUCTION NUMBER(10,2) Yes

EPROD 16 OIL_DAYS NUMBER(3,0) Yes

EPROD 17 WATER_PRODUCTION NUMBER(10,2) Yes

EPROD 18 PROD_GRP_NO NUMBER(3,0) Yes

EPROD 19 ERROR_CODE NUMBER Yes

EPROD 20 ERROR_MSG VARCHAR2(255 BYTE) Yes

EPROD 21 FARM_WELL_NO VARCHAR2(10 BYTE) Yes

ERR_TABLE 1 ERR_NUM NUMBER Yes

ERR_TABLE 2 ERR_MSG VARCHAR2(100 BYTE) Yes

EWELL 1 PERMIT_NUMBER VARCHAR2(9 BYTE) Yes

EWELL 2 COMPLETION_DATE DATE Yes

EWELL 3 TOTAL_DEPTH VARCHAR2(6 BYTE) Yes

EWELL 4 SPLCLSSSHORTNAME VARCHAR2(3 BYTE) Yes

EWELL 5 GENCLSS_ID NUMBER(1,0) Yes

EWELL 6 SPLCLSS_ID NUMBER(1,0) Yes

EWELL 7 EXPTYPESHORTNAME VARCHAR2(3 BYTE) Yes

EWELL 8 EXPTYPE_ID NUMBER(2,0) Yes

EWELL 9 WTYPESHORTNAME VARCHAR2(5 BYTE) Yes

EWELL 10 WTYPE_ID NUMBER(2,0) Yes

EWELL 11 FIELDNAME VARCHAR2(40 BYTE) Yes

EWELL 12 FIELD_ID NUMBER(4,0) Yes

EWELL 13 POOLNAME VARCHAR2(40 BYTE) Yes

EWELL 14 POOL_ID NUMBER(4,0) Yes

EWELL 15 DS_INDICATOR VARCHAR2(1 BYTE) Yes

EWELL 16 DATA_REMARK VARCHAR2(40 BYTE) Yes





EWELL 17 QUAD_SECTION_NUMBER NUMBER(1,0) Yes

EWELL 18 SOUTH_OFFSET VARCHAR2(6 BYTE) Yes

EWELL 19 WEST_OFFSET VARCHAR2(6 BYTE) Yes

EWELL 20 TDRUNITSTRATCODE VARCHAR2(5 BYTE) Yes

EWELL 21 TD_RUNIT_CODE NUMBER(4,0) Yes

EWELL 22 TD_RUNIT_TYPE_CODE VARCHAR2(2 BYTE) Yes

EWELL 23 STATUSSHORTNAME VARCHAR2(2 BYTE) Yes

EWELL 24 STSTUS_ID NUMBER(1,0) Yes

EWELL 25 PLUG_FLAG VARCHAR2(1 BYTE) Yes

EWELL 26 DATA_SOURCE VARCHAR2(6 BYTE) Yes

EWELL 27 CREATION_DATE DATE Yes

EWELL 28 ERROR_CODE NUMBER(6,0) Yes

EWELL 29 ERROR_MSG VARCHAR2(255 BYTE) Yes

EWELL 30 REG_STATUS VARCHAR2(2 BYTE) Yes

EWELL 31 WIDTYPE_ID NUMBER(1,0) Yes

EWELLUPD 1 PERMIT_NUMBER VARCHAR2(9 BYTE) Yes

EWELLUPD 2 QM_DER_CODE VARCHAR2(4 BYTE) Yes

EWELLUPD 3 QUAD_SECTION_NUMBER NUMBER(1,0) Yes

EWELLUPD 4 ERROR_CODE NUMBER Yes

EWELLUPD 5 ERROR_MSG VARCHAR2(225 BYTE) Yes

EXPLORATORY_TYPES 1 ID NUMBER(2,0) No

EXPLORATORY_TYPES 2 SPLCLSS_ID NUMBER(1,0) No

EXPLORATORY_TYPES 3 NAME VARCHAR2(40 BYTE) No

EXPLORATORY_TYPES 4 SHORT_NAME VARCHAR2(5 BYTE) Yes

FACILITY 1 FACILITY_ID NUMBER(10,0) No

FACILITY 2 FACILITY_PERMIT_NUMBER VARCHAR2(15 BYTE) Yes

FACILITY 3 FACILITY_NAME VARCHAR2(50 BYTE) Yes

FACILITY 4 BWDM_ID NUMBER(2,0) No

FIELD_COUNTIES_TT 1 FIELD_ID NUMBER(4,0) Yes

FIELD_COUNTIES_TT 2 COUNTY_NAME VARCHAR2(255 BYTE) Yes

FIELD_COUNTY_XREFS 1 ID NUMBER(5,0) No

FIELD_COUNTY_XREFS 2 FIELD_ID NUMBER(4,0) No

FIELD_COUNTY_XREFS 3 COUNTY_ID NUMBER(4,0) No





FIELDS 1 ID NUMBER(4,0) No

FIELDS 2 NAME VARCHAR2(40 BYTE) No

FIELDS 3 SHORT_NAME VARCHAR2(5 BYTE) Yes

GENERAL_CLASSES 1 ID NUMBER(1,0) No

GENERAL_CLASSES 2 NAME VARCHAR2(40 BYTE) No

GENERAL_CLASSES 3 SHORT_NAME VARCHAR2(5 BYTE) Yes

GEOPHYSICAL_LOGS 1 ID NUMBER(9,0) No

GEOPHYSICAL_LOGS 2 LOGREQ_ID NUMBER(10,0) No

GEOPHYSICAL_LOGS 3 WELL_ID NUMBER(6,0) Yes

GEOPHYSICAL_LOGS 4 LOGTYPE_DER_CODE VARCHAR2(2 BYTE) No

GEOPHYSICAL_LOGS 5 RUN_DATE DATE Yes

GEOPHYSICAL_LOGS 6 ELVTYPE_ID NUMBER(4,0) Yes

GEOPHYSICAL_LOGS 7 ELEVATION NUMBER(4,0) Yes

GEOPHYSICAL_LOGS 8 TOP_INTERVAL NUMBER(5,0) Yes

GEOPHYSICAL_LOGS 9 BOTTOM_INTERVAL NUMBER(5,0) Yes

GEOPHYSICAL_LOGS 10 TOTAL_DEPTH NUMBER(5,0) Yes

IAPXTB 1 XTB$XNM VARCHAR2(10 BYTE) No

IAPXTB 2 XTB$XTY VARCHAR2(3 BYTE) No

IAPXTB 3 XTB$REM VARCHAR2(40 BYTE) Yes

IAPXTB 4 XTB$CRE DATE No

IAPXTB 5 XTB$MOD DATE Yes

INTERPRETED_STRATIGRAPHIES 1 WELL_ID NUMBER(6,0) No

INTERPRETED_STRATIGRAPHIES 2 LINE_NO NUMBER(6,0) No

INTERPRETED_STRATIGRAPHIES 3 RUNIT_CODE NUMBER(4,0) No

INTERPRETED_STRATIGRAPHIES 4 RUNIT_TYPE_CODE VARCHAR2(2 BYTE) No

INTERPRETED_STRATIGRAPHIES 5 TOP NUMBER(5,0) No

INTERPRETED_STRATIGRAPHIES 6 BOTTOM NUMBER(5,0) Yes

INTERPRETED_STRATIGRAPHIES 7 DEPTH_GAS NUMBER(5,0) Yes

INTERPRETED_STRATIGRAPHIES 8 DEPTH_OIL NUMBER(5,0) Yes

INTERPRETED_STRATIGRAPHIES 9 DEPTH_BRINE NUMBER(5,0) Yes

INTERPRETED_STRATIGRAPHIES 10 DEPTH_FWATER NUMBER(5,0) Yes

INTERPRETERS 1 ID NUMBER(4,0) No

INTERPRETERS 2 NAME VARCHAR2(40 BYTE) No





INTERPRETERS 3 SHORT_NAME VARCHAR2(5 BYTE) Yes

LLP 1 AUTH_OTHER_ID VARCHAR2(9 BYTE) Yes

LLP 2 AUTH_REG_STATUS VARCHAR2(2 BYTE) Yes

LLP 3 SITE_CNTM_COUNTY_ID NUMBER(6,0) Yes

LLP 4 COUNTYMUNICIPALITY NUMBER(5,0) Yes

LLP 5 MUNICIPALITY_NAME VARCHAR2(20 BYTE) Yes

LLP 6 SITE_CNTM_MUNICIPALITY_ID NUMBER(6,0) Yes

LLP 7 SLOC_QM_DER_CODE VARCHAR2(4 BYTE) Yes

LLP 8 SLOC_QUAD_SECTION_NUMBER NUMBER(1,0) Yes

LLP 9 SLOC_LAT_OFFSET_DISTANCE VARCHAR2(6 BYTE) Yes

LLP 10 SLOC_LONG_OFFSET_DISTANCE VARCHAR2(6 BYTE) Yes

LLP 11 SLOC_ELEVATION NUMBER(4,0) Yes

LLP 12 OGWS_CO_SRL_NO VARCHAR2(7 BYTE) Yes

LLP 13 OGWS_PROJECT_NO VARCHAR2(12 BYTE) Yes

LLP 14 OGWS_FARM_WELL_NO VARCHAR2(6 BYTE) Yes

LLP 15 OGWS_FARM_NAME VARCHAR2(36 BYTE) Yes

LLP 16 CLIR_CLIENT_ID NUMBER(5,0) Yes

LLP 17 TIME_STAMP DATE Yes

LLP 18 DATA_SOURCE VARCHAR2(6 BYTE) Yes

LLP 19 ERROR_CODE NUMBER Yes

LLP 20 ERROR_MSG VARCHAR2(525 BYTE) Yes

LLP 21 ROW_ID ROWID Yes

LLPREJ 1 AUTH_OTHER_ID VARCHAR2(9 BYTE) Yes

LLPREJ 2 AUTH_REG_STATUS VARCHAR2(2 BYTE) Yes

LLPREJ 3 SITE_CNTM_COUNTY_ID NUMBER(6,0) Yes

LLPREJ 4 COUNTYMUNICIPALITY NUMBER(5,0) Yes

LLPREJ 5 MUNICIPALITY_NAME VARCHAR2(20 BYTE) Yes

LLPREJ 6 SITE_CNTM_MUNICIPALITY_ID NUMBER(6,0) Yes

LLPREJ 7 SLOC_QM_DER_CODE VARCHAR2(4 BYTE) Yes

LLPREJ 8 SLOC_QUAD_SECTION_NUMBER NUMBER(1,0) Yes

LLPREJ 9 SLOC_LAT_OFFSET_DISTANCE VARCHAR2(6 BYTE) Yes

LLPREJ 10 SLOC_LONG_OFFSET_DISTANCE VARCHAR2(6 BYTE) Yes

LLPREJ 11 SLOC_ELEVATION NUMBER(4,0) Yes





LLPREJ 12 OGWS_CO_SRL_NO VARCHAR2(7 BYTE) Yes

LLPREJ 13 OGWS_PROJECT_NO VARCHAR2(12 BYTE) Yes

LLPREJ 14 OGWS_FARM_WELL_NO VARCHAR2(6 BYTE) Yes

LLPREJ 15 OGWS_FARM_NAME VARCHAR2(36 BYTE) Yes

LLPREJ 16 CLIR_CLIENT_ID NUMBER(5,0) Yes

LLPREJ 17 TIME_STAMP DATE Yes

LLPREJ 18 DATA_SOURCE VARCHAR2(6 BYTE) Yes

LLPREJ 19 ERROR_CODE NUMBER Yes

LLPREJ 20 ERROR_MSG VARCHAR2(512 BYTE) Yes

LLPREJ 21 ROW_ID ROWID Yes

LOC_PLATS 1 AUTHREQ_ID NUMBER(10,0) No

LOC_PLATS 2 AUTHTYP_CODE VARCHAR2(6 BYTE) No

LOC_PLATS 3 OTHER_ID VARCHAR2(15 BYTE) No

LOC_PLATS 4 WELL_ID NUMBER(6,0) Yes

LOC_PLATS 5 UPDATE_DTE DATE Yes

LOC_PLATS 6 UPDATE_BY_ID VARCHAR2(30 BYTE) Yes

LOC_PLATS 7 COUNTY_ID NUMBER(4,0) Yes

LOC_PLATS 8 BOND_SET VARCHAR2(80 BYTE) Yes

LOC_PLATS 9 RECEIVED_DTE DATE Yes

LOC_PLATS 10 PRIORITY_TEXT VARCHAR2(255 BYTE) Yes

LOC_PLATS 11 ORDER_NUM NUMBER(3,0) Yes

LOC_PLATS 12 AUTH_DESCRIPTION VARCHAR2(2000 BYTE)

Yes

LOC_PLATS 13 DISPOSITION_DTE DATE Yes

LOC_PLATS 14 EXPIRE_DTE DATE Yes

LOC_PLATS 15 FEE_SET VARCHAR2(80 BYTE) Yes

LOC_PLATS 16 DER_DESCRIPTION VARCHAR2(255 BYTE) Yes

LOC_PLATS 17 REG_STATUS VARCHAR2(2 BYTE) Yes

LOC_PLATS 18 SITE_ID NUMBER(9,0) No

LOC_PLATS 19 CNTM_COUNTY_ID NUMBER(4,0) No

LOC_PLATS 20 CNTM_MUNICIPALITY_ID NUMBER(6,0) No

LOC_PLATS 21 SITE_DESCRIPTION VARCHAR2(255 BYTE) Yes

LOC_PLATS 22 LOC_ADDRESS_1 VARCHAR2(45 BYTE) Yes





LOC_PLATS 23 LOC_ADDRESS_2 VARCHAR2(45 BYTE) Yes

LOC_PLATS 24 MAIL_ADDRESS_1 VARCHAR2(45 BYTE) Yes

LOC_PLATS 25 MAIL_CITY VARCHAR2(30 BYTE) Yes

LOC_PLATS 26 OTHER_LOC_DESCRIPTION VARCHAR2(255 BYTE) Yes

LOC_PLATS 27 PHONE_NUM NUMBER(10,0) Yes

LOC_PLATS 28 PHONE_EXT NUMBER(4,0) Yes

LOC_PLATS 29 NAME VARCHAR2(60 BYTE) Yes

LOC_PLATS 30 MAIL_ADDRESS_2 VARCHAR2(45 BYTE) Yes

LOC_PLATS 31 LOC_CITY VARCHAR2(30 BYTE) Yes

LOC_PLATS 32 FAX_NUM NUMBER(10,0) Yes

LOC_PLATS 33 SITELOC_ID NUMBER(9,0) Yes

LOC_PLATS 34 QM_DER_CODE VARCHAR2(4 BYTE) Yes

LOC_PLATS 35 QUAD_SECTION_NUMBER NUMBER(3,0) Yes

LOC_PLATS 36 LAT_DEGREE NUMBER(3,0) Yes

LOC_PLATS 37 LAT_MINUTE NUMBER(2,0) Yes

LOC_PLATS 38 LAT_SECOND NUMBER(2,0) Yes

LOC_PLATS 39 LONG_DEGREE NUMBER(3,0) Yes

LOC_PLATS 40 LONG_MINUTE NUMBER(2,0) Yes

LOC_PLATS 41 LONG_SECOND NUMBER(2,0) Yes

LOC_PLATS 42 REFERENCE_CORNER VARCHAR2(6 BYTE) Yes

LOC_PLATS 43 LAT_OFFSET_DIRECTION VARCHAR2(2 BYTE) Yes

LOC_PLATS 44 LAT_OFFSET_DISTANCE NUMBER(6,0) Yes

LOC_PLATS 45 LAT_OFFSET_UNITS VARCHAR2(6 BYTE) Yes

LOC_PLATS 46 LONG_OFFSET_DIRECTION VARCHAR2(2 BYTE) Yes

LOC_PLATS 47 LONG_OFFSET_DISTANCE NUMBER(6,0) Yes

LOC_PLATS 48 LONG_OFFSET_UNITS VARCHAR2(6 BYTE) Yes

LOC_PLATS 49 ELEVATION NUMBER(4,0) Yes

LOC_PLATS 50 ELEVATION_UNITS VARCHAR2(6 BYTE) Yes

LOC_PLATS 51 VERIFIED_FLAG VARCHAR2(1 BYTE) Yes

LOC_PLATS 52 STATE_PLANE_ZONE VARCHAR2(6 BYTE) Yes

LOC_PLATS 53 REFERENCE_DATUM_CODE VARCHAR2(6 BYTE) Yes

LOC_PLATS 54 MAP_SCALE_CODE VARCHAR2(10 BYTE) Yes

LOC_PLATS 55 DATE_OF_COLLECTION DATE Yes





LOC_PLATS 56 LOCATION_METHOD_CODE VARCHAR2(6 BYTE) Yes

LOC_PLATS 57 CLIENT_ID NUMBER(9,0) Yes

LOC_PLATS 58 CLIENT_NAME VARCHAR2(60 BYTE) Yes

LOC_PLATS 59 AFFELIATION_TYPE VARCHAR2(1 BYTE) Yes

LOC_PLATS 60 OGWELL_ID NUMBER(9,0) No

LOC_PLATS 61 CO_SRL_NO VARCHAR2(10 BYTE) Yes

LOC_PLATS 62 PROJECT_NO VARCHAR2(10 BYTE) Yes

LOC_PLATS 63 FARM_NAME VARCHAR2(40 BYTE) Yes

LOC_PLATS 64 FARM_WELL_NO VARCHAR2(10 BYTE) Yes

LOC_PLATS 65 CURRENT_AREA NUMBER(6,0) Yes

LOC_PLATS 66 PROJECT_KEY_WELL VARCHAR2(1 BYTE) Yes

LOC_PLATS 67 LAT_TRUE NUMBER Yes

LOC_PLATS 68 LONG_TRUE NUMBER Yes

LOC_PLATS 69 DEP_ID NUMBER(10,0) Yes

LOC_PLATS 70 TOTAL_DEPTH NUMBER(6,0) Yes

LOC_PLATS 71 PAIRIS_SCAN_FLAG NUMBER(1,0) No

LOC_PLATS 72 DOCUMENT_SYS_DATE DATE Yes

LOG_REQUESTS 1 ID NUMBER(10,0) No

LOG_REQUESTS 2 AUTHREQ_ID NUMBER(10,0) No

LOG_REQUESTS 3 CREATION_DATE DATE Yes

LOG_REQUESTS 4 REQUEST_DATE DATE Yes

LOG_REQUESTS 5 RESPONSE_DATE DATE Yes

LOG_REQUESTS 6 CONFIDENTIALITY NUMBER(1,0) Yes

LOG_REQUESTS 7 REMINDER_DATE DATE Yes

LOG_REQUESTS 8 RECEIPT_DATE DATE Yes

LOG_REQUESTS 9 RELEASE_FLAG NUMBER(1,0) Yes

LOG_TYPES 1 DER_CODE VARCHAR2(2 BYTE) No

LOG_TYPES 2 DESCRIPTION VARCHAR2(60 BYTE) No

LOG_TYPES 3 OIL_AND_GAS_CODE VARCHAR2(10 BYTE) Yes

LOG_TYPES 4 WATER_CODE VARCHAR2(1 BYTE) Yes

LP_PERMIT_SCANNED 1 PERMIT_NUMBER VARCHAR2(15 BYTE) Yes

LPC 1 PERMIT_NUMBER VARCHAR2(9 BYTE) Yes

LPC 2 WELL_ID NUMBER(6,0) Yes





LPC 3 DC_DATE DATE Yes

LPC 4 DATA_SOURCE VARCHAR2(6 BYTE) Yes

LPC 5 ERROR_CODE NUMBER(6,0) Yes

LPC 6 ERROR_MSG VARCHAR2(255 BYTE) Yes

LWELL 1 PERMIT_NUMBER VARCHAR2(9 BYTE) Yes

LWELL 2 COMPLETION_DATE DATE Yes

LWELL 3 TOTAL_DEPTH VARCHAR2(6 BYTE) Yes

LWELL 4 SPLCLSSSHORTNAME VARCHAR2(3 BYTE) Yes

LWELL 5 GENCLSS_ID NUMBER(1,0) Yes

LWELL 6 SPLCLSS_ID NUMBER(1,0) Yes

LWELL 7 EXPTYPESHORTNAME VARCHAR2(3 BYTE) Yes

LWELL 8 EXPTYPE_ID NUMBER(2,0) Yes

LWELL 9 WTYPESHORTNAME VARCHAR2(5 BYTE) Yes

LWELL 10 WTYPE_ID NUMBER(2,0) Yes

LWELL 11 FIELDNAME VARCHAR2(40 BYTE) Yes

LWELL 12 FIELD_ID NUMBER(4,0) Yes

LWELL 13 POOLNAME VARCHAR2(40 BYTE) Yes

LWELL 14 POOL_ID NUMBER(4,0) Yes

LWELL 15 DS_INDICATOR VARCHAR2(1 BYTE) Yes

LWELL 16 DATA_REMARK VARCHAR2(40 BYTE) Yes

LWELL 17 QUAD_SECTION_NUMBER NUMBER(1,0) Yes

LWELL 18 SOUTH_OFFSET VARCHAR2(6 BYTE) Yes

LWELL 19 WEST_OFFSET VARCHAR2(6 BYTE) Yes

LWELL 20 TDRUNITSTRATCODE VARCHAR2(5 BYTE) Yes

LWELL 21 TD_RUNIT_CODE NUMBER(4,0) Yes

LWELL 22 TD_RUNIT_TYPE_CODE VARCHAR2(2 BYTE) Yes

LWELL 23 STATUSSHORTNAME VARCHAR2(2 BYTE) Yes

LWELL 24 STSTUS_ID NUMBER(1,0) Yes

LWELL 25 PLUG_FLAG VARCHAR2(1 BYTE) Yes

LWELL 26 DATA_SOURCE VARCHAR2(6 BYTE) Yes

LWELL 27 CREATION_DATE DATE Yes

LWELL 28 ERROR_CODE NUMBER(6,0) Yes

LWELLREJ 1 PERMIT_NUMBER VARCHAR2(9 BYTE) Yes





LWELLREJ 2 COMPLETION_DATE DATE Yes

LWELLREJ 3 TOTAL_DEPTH VARCHAR2(6 BYTE) Yes

LWELLREJ 4 SPLCLSSSHORTNAME VARCHAR2(3 BYTE) Yes

LWELLREJ 5 GENCLSS_ID NUMBER(1,0) Yes

LWELLREJ 6 SPLCLSS_ID NUMBER(1,0) Yes

LWELLREJ 7 EXPTYPESHORTNAME VARCHAR2(3 BYTE) Yes

LWELLREJ 8 EXPTYPE_ID NUMBER(2,0) Yes

LWELLREJ 9 WTYPESHORTNAME VARCHAR2(5 BYTE) Yes

LWELLREJ 10 WTYPE_ID NUMBER(2,0) Yes

LWELLREJ 11 FIELDNAME VARCHAR2(20 BYTE) Yes

LWELLREJ 12 FIELD_ID NUMBER(4,0) Yes

LWELLREJ 13 POOLNAME VARCHAR2(20 BYTE) Yes

LWELLREJ 14 POOL_ID NUMBER(4,0) Yes

LWELLREJ 15 DS_INDICATOR VARCHAR2(1 BYTE) Yes

LWELLREJ 16 DATA_REMARK VARCHAR2(40 BYTE) Yes

LWELLREJ 17 QUAD_SECTION_NUMBER NUMBER(1,0) Yes

LWELLREJ 18 SOUTH_OFFSET VARCHAR2(6 BYTE) Yes

LWELLREJ 19 WEST_OFFSET VARCHAR2(6 BYTE) Yes

LWELLREJ 20 TDRUNITSTRATCODE VARCHAR2(5 BYTE) Yes

LWELLREJ 21 TD_RUNIT_CODE NUMBER(4,0) Yes

LWELLREJ 22 TD_RUNIT_TYPE_CODE VARCHAR2(2 BYTE) Yes

LWELLREJ 23 STATUSSHORTNAME VARCHAR2(2 BYTE) Yes

LWELLREJ 24 STSTUS_ID NUMBER(1,0) Yes

LWELLREJ 25 PLUG_FLAG VARCHAR2(1 BYTE) Yes

LWELLREJ 26 DATA_SOURCE VARCHAR2(6 BYTE) Yes

LWELLREJ 27 CREATION_DATE DATE Yes

LWELLREJ 28 ERROR_CODE NUMBER(6,0) Yes

LWELLREJ 29 ERROR_MSG VARCHAR2(255 BYTE) Yes

LWELLREJ 30 REG_STATUS VARCHAR2(2 BYTE) Yes

MERGE_NOT_FOUND_TT 1 PERMIT_NUMBER VARCHAR2(15 BYTE) Yes

MERGE_NOT_FOUND_TT 2 WELL_ID NUMBER(6,0) Yes

MERGE_NOT_FOUND_TT 3 DATE_OF_NOT_MERGED DATE Yes

MICROSOFTDTPROPERTIES 1 ID NUMBER No





MICROSOFTDTPROPERTIES 2 OBJECTID NUMBER Yes

MICROSOFTDTPROPERTIES 3 PROPERTY VARCHAR2(64 BYTE) No

MICROSOFTDTPROPERTIES 4 VALUE VARCHAR2(255 BYTE) Yes

MICROSOFTDTPROPERTIES 5 LVALUE LONG RAW Yes

MICROSOFTDTPROPERTIES 6 VERSION NUMBER No

NO_AUTH_CLIENTS_TT 1 AUTHREQ_ID NUMBER(10,0) Yes

NO_AUTH_CLIENTS_TT 2 PERMIT_NUMBER VARCHAR2(15 BYTE) Yes

NO_AUTH_REQ_SITES_TT 1 PERMIT_NUMBER VARCHAR2(15 BYTE) Yes

NO_AUTH_REQ_SITES_TT 2 AUTH_ID NUMBER(10,0) Yes

NO_CLIENT_REQUESTS_TT 1 AUTHREQ_ID NUMBER(10,0) Yes

NO_OG_WELLS_TT 1 SITE_ID NUMBER(9,0) Yes

NO_SITES_TT 1 SITE_ID NUMBER(9,0) Yes

OG_KEY_WELLS 1 PROJECT_NO VARCHAR2(10 BYTE) No

OG_KEY_WELLS 2 WELL_ID VARCHAR2(6 BYTE) Yes

OG_KEY_WELLS 3 PERMIT_NUMBER VARCHAR2(15 BYTE) Yes

OG_KEY_WELLS 4 DATE_CREATED DATE Yes

OG_WELL_SITES_OLD 1 ID NUMBER(9,0) No

OG_WELL_SITES_OLD 2 SITE_ID NUMBER(9,0) No

OG_WELL_SITES_OLD 3 CO_SRL_NO VARCHAR2(10 BYTE) Yes

OG_WELL_SITES_OLD 4 PROJECT_NO VARCHAR2(10 BYTE) Yes

OG_WELL_SITES_OLD 5 FARM_NAME VARCHAR2(40 BYTE) Yes

OG_WELL_SITES_OLD 6 FARM_WELL_NO VARCHAR2(10 BYTE) Yes

OG_WELL_SITES_OLD 7 CURRENT_AREA NUMBER(6,0) Yes

OG_WELL_SITES_OLD 8 PROJECT_KEY_WELL VARCHAR2(1 BYTE) Yes

OGAPS_CODES 1 ID NUMBER(12,0) No

OGAPS_CODES 2 TYPE_CODE VARCHAR2(60 BYTE) No

OGAPS_CODES 3 CODE_VALUE VARCHAR2(100 BYTE) Yes

OGAPS_EXCEPTIONS 1 EXP_DATE DATE No

OGAPS_EXCEPTIONS 2 SOURCE VARCHAR2(255 BYTE) No

OGAPS_EXCEPTIONS 3 BAPRID NUMBER(9,0) No

OGAPS_EXCEPTIONS 4 CLIENTID NUMBER(9,0) No

OGAPS_EXCEPTIONS 5 PRODYEAR NUMBER(4,0) No

OGAPS_EXCEPTIONS 6 SQLERRM VARCHAR2(2000 Yes





BYTE)

OGAPS_EXCEPTIONS 7 REPORTED VARCHAR2(1 BYTE) Yes

OGPXFER_EXP_PROD_REPORTS 1 BAPRID NUMBER(9,0) Yes

OGPXFER_EXP_PROD_REPORTS 2 DATEOFRCPT DATE Yes

OGPXFER_EXP_PROD_REPORTS 3 PRODYEAR NUMBER(4,0) Yes

OGPXFER_EXP_PROD_REPORTS 4 CLIENTID NUMBER(9,0) Yes

OGPXFER_EXP_PROD_REPORTS 5 OPERATORREMARK VARCHAR2(100 BYTE) Yes

OGPXFER_EXP_PROD_REPORTS 6 OGREMARK VARCHAR2(100 BYTE) Yes

OGPXFER_EXP_PROD_REPORTS 7 BTGSREMARK VARCHAR2(100 BYTE) Yes

OGPXFER_EXP_PROD_REPORTS 8 TYPEOFCREATION VARCHAR2(2 BYTE) Yes

OGPXFER_EXP_PROD_REPORTS 9 CREATEDBY VARCHAR2(30 BYTE) Yes

OGPXFER_EXP_PROD_REPORTS 10 CREATIONDATE DATE Yes

OGPXFER_EXP_PROD_REPORTS 11 MODIFIEDBY VARCHAR2(30 BYTE) Yes

OGPXFER_EXP_PROD_REPORTS 12 MODIFICATIONDATE DATE Yes

OGPXFER_EXP_PROD_WELLS 1 BAPWID NUMBER(9,0) Yes

OGPXFER_EXP_PROD_WELLS 2 BAPRID NUMBER(9,0) Yes

OGPXFER_EXP_PROD_WELLS 3 PERMITNUMBER VARCHAR2(9 BYTE) Yes

OGPXFER_EXP_PROD_WELLS 4 FARMNAME VARCHAR2(40 BYTE) Yes

OGPXFER_EXP_PROD_WELLS 5 FARMWELLNUMBER VARCHAR2(10 BYTE) Yes

OGPXFER_EXP_PROD_WELLS 6 COSRLNO VARCHAR2(10 BYTE) Yes

OGPXFER_EXP_PROD_WELLS 7 TANKMETERNUMBER VARCHAR2(15 BYTE) Yes

OGPXFER_EXP_PROD_WELLS 8 HWTYPE VARCHAR2(1 BYTE) Yes

OGPXFER_EXP_PROD_WELLS 9 STATUSID NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 10 PRODGRPNO NUMBER(4,0) Yes

OGPXFER_EXP_PROD_WELLS 11 APIMISMATCH NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 12 FARMMISMATCH NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 13 CLIENTMISMATCH NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 14 DUPLICATEREPORTING NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 15 STATUSMISMATCH NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 16 WTYPEMISMATCH NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 17 PRODMISSING NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 18 PRODINVALID NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 19 PRODZERO NUMBER(1,0) Yes





OGPXFER_EXP_PROD_WELLS 20 DAYSMISSING NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 21 DAYSINVALID NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 22 SRLNOMISMATCH NUMBER(1,0) Yes

OGPXFER_EXP_PROD_REPORTS 1 BAPRID NUMBER(9,0) Yes

OGPXFER_EXP_PROD_REPORTS 2 DATEOFRCPT DATE Yes

OGPXFER_EXP_PROD_REPORTS 3 PRODYEAR NUMBER(4,0) Yes

OGPXFER_EXP_PROD_REPORTS 4 CLIENTID NUMBER(9,0) Yes

OGPXFER_EXP_PROD_REPORTS 5 OPERATORREMARK VARCHAR2(100 BYTE) Yes

OGPXFER_EXP_PROD_REPORTS 6 OGREMARK VARCHAR2(100 BYTE) Yes

OGPXFER_EXP_PROD_REPORTS 7 BTGSREMARK VARCHAR2(100 BYTE) Yes

OGPXFER_EXP_PROD_REPORTS 8 TYPEOFCREATION VARCHAR2(2 BYTE) Yes

OGPXFER_EXP_PROD_REPORTS 9 CREATEDBY VARCHAR2(30 BYTE) Yes

OGPXFER_EXP_PROD_REPORTS 10 CREATIONDATE DATE Yes

OGPXFER_EXP_PROD_REPORTS 11 MODIFIEDBY VARCHAR2(30 BYTE) Yes

OGPXFER_EXP_PROD_REPORTS 12 MODIFICATIONDATE DATE Yes

OGPXFER_EXP_PROD_WELLS 1 BAPWID NUMBER(9,0) Yes

OGPXFER_EXP_PROD_WELLS 2 BAPRID NUMBER(9,0) Yes

OGPXFER_EXP_PROD_WELLS 3 PERMITNUMBER VARCHAR2(9 BYTE) Yes

OGPXFER_EXP_PROD_WELLS 4 FARMNAME VARCHAR2(40 BYTE) Yes

OGPXFER_EXP_PROD_WELLS 5 FARMWELLNUMBER VARCHAR2(10 BYTE) Yes

OGPXFER_EXP_PROD_WELLS 6 COSRLNO VARCHAR2(10 BYTE) Yes

OGPXFER_EXP_PROD_WELLS 7 TANKMETERNUMBER VARCHAR2(15 BYTE) Yes

OGPXFER_EXP_PROD_WELLS 8 HWTYPE VARCHAR2(1 BYTE) Yes

OGPXFER_EXP_PROD_WELLS 9 STATUSID NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 10 PRODGRPNO NUMBER(4,0) Yes

OGPXFER_EXP_PROD_WELLS 11 APIMISMATCH NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 12 FARMMISMATCH NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 13 CLIENTMISMATCH NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 14 DUPLICATEREPORTING NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 15 STATUSMISMATCH NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 16 WTYPEMISMATCH NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 17 PRODMISSING NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 18 PRODINVALID NUMBER(1,0) Yes





OGPXFER_EXP_PROD_WELLS 19 PRODZERO NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 20 DAYSMISSING NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 21 DAYSINVALID NUMBER(1,0) Yes

OGPXFER_EXP_PROD_WELLS 22 SRLNOMISMATCH NUMBER(1,0) Yes

OGPXFER_EXP_WASTE_FACILITIES 1 ID NUMBER(9,0) Yes

OGPXFER_EXP_WASTE_FACILITIES 2 BAWP_ID NUMBER(9,0) Yes

OGPXFER_EXP_WASTE_FACILITIES 3 FACILITY_NAME VARCHAR2(40 BYTE) Yes

OGPXFER_EXP_WASTE_FACILITIES 4 FACILITY_PERMIT_NUMBER VARCHAR2(15 BYTE) Yes

OGPXFER_EXP_WASTE_METHODS 1 ID NUMBER(9,0) Yes

OGPXFER_EXP_WASTE_METHODS 2 BAWF_ID NUMBER(9,0) Yes

OGPXFER_EXP_WASTE_METHODS 3 BWDM_ID NUMBER(2,0) Yes

OGPXFER_EXP_WASTE_METHODS 4 QUANTITY NUMBER(10,2) Yes

OGPXFER_EXP_WELL_PRODUCTIONS 1 BAWPID NUMBER(9,0) Yes

OGPXFER_EXP_WELL_PRODUCTIONS 2 BAPWID NUMBER(9,0) Yes

OGPXFER_EXP_WELL_PRODUCTIONS 3 PRODUCTID NUMBER(4,0) Yes

OGPXFER_EXP_WELL_PRODUCTIONS 4 QUANTITY NUMBER(10,2) Yes

OGPXFER_EXP_WELL_PRODUCTIONS 5 OPERATINGDAYS NUMBER(3,0) Yes

PERFORATIONS 1 ID NUMBER(9,0) No

PERFORATIONS 2 CR_ID NUMBER(9,0) No

PERFORATIONS 3 TOP NUMBER(5,0) No

PERFORATIONS 4 BOTTOM NUMBER(5,0) Yes

POOL_RESERVOIRS_TT 1 POOL_ID NUMBER(9,0) Yes

POOL_RESERVOIRS_TT 2 RESERVOIR_NAME VARCHAR2(255 BYTE) Yes

POOL_ROCK_UNITS 1 ID NUMBER(4,0) No

POOL_ROCK_UNITS 2 POOL_ID NUMBER(4,0) No

POOL_ROCK_UNITS 3 RUNIT_CODE NUMBER(4,0) No

POOL_ROCK_UNITS 4 RUNIT_TYPE_CODE VARCHAR2(2 BYTE) No

POOLS 1 ID NUMBER(4,0) No

POOLS 2 FIELD_ID NUMBER(4,0) No

POOLS 3 NAME VARCHAR2(40 BYTE) No

POOLS 4 SHORT_NAME VARCHAR2(5 BYTE) Yes

POOLS 5 DISCOVERY_DATE DATE Yes

POOLS 6 CUM_GAS_1974 NUMBER(12,2) Yes





POOLS 7 CUM_GAS NUMBER(12,2) Yes

POOLS 8 CUM_OIL NUMBER(12,2) Yes

POOLS 9 DISCOVERY_WELL_ID NUMBER(6,0) Yes

POOLS_HAYDENVILLE 1 ID NUMBER(4,0) No

POOLS_HAYDENVILLE 2 FIELD_ID NUMBER(4,0) No

POOLS_HAYDENVILLE 3 NAME VARCHAR2(40 BYTE) No

POOLS_HAYDENVILLE 4 SHORT_NAME VARCHAR2(5 BYTE) Yes

POOLS_HAYDENVILLE 5 DISCOVERY_DATE DATE Yes

POOLS_HAYDENVILLE 6 CUM_GAS_1974 NUMBER(12,2) Yes

POOLS_HAYDENVILLE 7 CUM_GAS NUMBER(12,2) Yes

POOLS_HAYDENVILLE 8 CUM_OIL NUMBER(12,2) Yes

POOLS_HAYDENVILLE 9 DISCOVERY_WELL_ID NUMBER(6,0) Yes

PRODUCTS 1 ID NUMBER(4,0) No

PRODUCTS 2 NAME VARCHAR2(40 BYTE) No

PRODUCTS 3 SHORT_NAME VARCHAR2(5 BYTE) Yes

PRODUCTS 4 UOM_CODE NUMBER(5,0) No

PRODUCTS 5 CONVERSION_TO_TONS NUMBER(5,3) Yes

QUADRANGLE_MAPS 1 DER_CODE VARCHAR2(4 BYTE) No

QUADRANGLE_MAPS 2 BWQM_CODE VARCHAR2(5 BYTE) No

QUADRANGLE_MAPS 3 NAME VARCHAR2(60 BYTE) No

QUADRANGLE_MAPS 4 SW_LATITUDE NUMBER(12,4) Yes

QUADRANGLE_MAPS 5 SW_LONGITUDE NUMBER(13,4) Yes

QUADRANGLE_MAPS 6 NE_LATITUDE NUMBER(12,4) Yes

QUADRANGLE_MAPS 7 NE_LONGITUDE NUMBER(13,4) Yes

RESERVOIRS 1 ID NUMBER(9,0) No

RESERVOIRS 2 CR_ID NUMBER(9,0) No

RESERVOIRS 3 RUNIT_CODE NUMBER(4,0) No

RESERVOIRS 4 RUNIT_TYPE_CODE VARCHAR2(2 BYTE) No

RF_OBJECTS_TO_RETROFIT 1 OBJ_NAME VARCHAR2(30 BYTE) Yes

RF_OBJECTS_TO_RETROFIT 2 OBJ_TYPE VARCHAR2(30 BYTE) Yes

RF_RETROFITTED_OBJECTS 1 NAME VARCHAR2(30 BYTE) Yes

RF_RETROFITTED_OBJECTS 2 TYPE VARCHAR2(20 BYTE) Yes

RF_RETROFITTED_OBJECTS 3 PARENT_NAME VARCHAR2(30 BYTE) Yes





RF_RETROFITTED_OBJECTS 4 PARENT_TYPE VARCHAR2(20 BYTE) Yes

RF_RETROFITTED_OBJECTS 5 COMMENTS VARCHAR2(240 BYTE) Yes

RF_RETROFITTED_OBJECTS 6 TEXT VARCHAR2(240 BYTE) Yes

RF_RETROFITTED_OBJECTS 7 REASON_NO_RETRO VARCHAR2(100 BYTE) Yes

RF_RETROFITTED_OBJECTS 8 CHAR1 VARCHAR2(30 BYTE) Yes





RF_RETROFITTED_OBJECTS 13 NUMB1 NUMBER Yes









ROCK_SAMPLES 1 ID NUMBER(6,0) No

ROCK_SAMPLES 2 WELL_ID NUMBER(6,0) No

ROCK_SAMPLES 3 SAMPLE_TYPE VARCHAR2(1 BYTE) No

ROCK_SAMPLES 4 COLLECTION_DATE DATE Yes

ROCK_SAMPLES 5 NO_BOX NUMBER(2,0) Yes

ROCK_SAMPLES 6 FROM_RACK NUMBER(3,0) Yes

ROCK_SAMPLES 7 FROM_SHELF VARCHAR2(1 BYTE) Yes

ROCK_SAMPLES 8 TO_RACK NUMBER(3,0) Yes

ROCK_SAMPLES 9 TO_SHELF VARCHAR2(1 BYTE) Yes

ROCK_SAMPLES 10 TECHNICAL_REMARK VARCHAR2(100 BYTE) Yes

ROCK_SAMPLES 11 STORAGE_REMARK VARCHAR2(100 BYTE) Yes

ROCK_UNITS 1 CODE NUMBER(4,0) No

ROCK_UNITS 7 TYPE_CODE VARCHAR2(2 BYTE) No

ROCK_UNITS 2 DESCRIPTION VARCHAR2(60 BYTE) No

ROCK_UNITS 3 DATE_CREATED DATE Yes





ROCK_UNITS 4 CREATED_BY VARCHAR2(30 BYTE) Yes

ROCK_UNITS 5 DATE_LAST_MODIFIED DATE Yes

ROCK_UNITS 6 LAST_MODIFIED_BY VARCHAR2(30 BYTE) Yes

ROCK_UNITS 8 PARENT_ROCK_UNIT_CODE NUMBER(4,0) Yes

ROCK_UNITS 9 PARENT_ROCK_UNIT_TYPE_CODE

VARCHAR2(2 BYTE) Yes

ROCK_UNITS 10 STRATIGRAPHIC_CODE VARCHAR2(5 BYTE) Yes

ROCK_UNITS 11 SHORT_NAME VARCHAR2(5 BYTE) Yes

SAMPLE_RANGES 1 RSMP_ID NUMBER(6,0) No

SAMPLE_RANGES 2 LINE_NO NUMBER(6,0) No

SAMPLE_RANGES 3 DEPTH_FROM NUMBER(5,0) No

SAMPLE_RANGES 4 DEPTH_TO NUMBER(5,0) No

SAMPLE_RANGES 5 RUNIT_CODE NUMBER(4,0) Yes

SAMPLE_RANGES 6 RUNIT_TYPE_CODE VARCHAR2(2 BYTE) Yes

SITE_LOCATIONS_OLD 1 ID NUMBER(9,0) No

SITE_LOCATIONS_OLD 2 SITE_ID NUMBER(9,0) No

SITE_LOCATIONS_OLD 3 QM_DER_CODE VARCHAR2(4 BYTE) Yes

SITE_LOCATIONS_OLD 4 QUAD_SECTION_NUMBER NUMBER(3,0) Yes

SITE_LOCATIONS_OLD 5 LAT_DEGREE NUMBER(3,0) Yes

SITE_LOCATIONS_OLD 6 LAT_MINUTE NUMBER(2,0) Yes

SITE_LOCATIONS_OLD 7 LAT_SECOND NUMBER(2,0) Yes

SITE_LOCATIONS_OLD 8 LONG_DEGREE NUMBER(3,0) Yes

SITE_LOCATIONS_OLD 9 LONG_MINUTE NUMBER(2,0) Yes

SITE_LOCATIONS_OLD 10 LONG_SECOND NUMBER(2,0) Yes

SITE_LOCATIONS_OLD 11 REFERENCE_CORNER VARCHAR2(6 BYTE) Yes

SITE_LOCATIONS_OLD 12 LAT_OFFSET_DIRECTION VARCHAR2(2 BYTE) Yes

SITE_LOCATIONS_OLD 13 LAT_OFFSET_DISTANCE NUMBER(6,0) Yes

SITE_LOCATIONS_OLD 14 LAT_OFFSET_UNITS VARCHAR2(6 BYTE) Yes

SITE_LOCATIONS_OLD 15 LONG_OFFSET_DIRECTION VARCHAR2(2 BYTE) Yes

SITE_LOCATIONS_OLD 16 LONG_OFFSET_DISTANCE NUMBER(6,0) Yes

SITE_LOCATIONS_OLD 17 LONG_OFFSET_UNITS VARCHAR2(6 BYTE) Yes

SITE_LOCATIONS_OLD 18 ELEVATION NUMBER(4,0) Yes

SITE_LOCATIONS_OLD 19 ELEVATION_UNITS VARCHAR2(6 BYTE) Yes





SITE_LOCATIONS_OLD 20 VERIFIED_FLAG VARCHAR2(1 BYTE) Yes

SITE_LOCATIONS_OLD 21 STATE_PLANE_ZONE VARCHAR2(6 BYTE) Yes

SITE_LOCATIONS_OLD 22 REFERENCE_DATUM_CODE VARCHAR2(6 BYTE) Yes

SITE_LOCATIONS_OLD 23 MAP_SCALE_CODE VARCHAR2(10 BYTE) Yes

SITE_LOCATIONS_OLD 24 CLIENT_ID NUMBER(9,0) Yes

SITE_LOCATIONS_OLD 25 DATE_OF_COLLECTION DATE Yes

SITE_LOCATIONS_OLD 26 LOCATION_METHOD_CODE VARCHAR2(6 BYTE) Yes

SITES_OLD 1 ID NUMBER(9,0) No

SITES_OLD 2 CNTM_COUNTY_ID NUMBER(4,0) No

SITES_OLD 3 CNTM_MUNICIPALITY_ID NUMBER(6,0) Yes

SITES_OLD 4 DESCRIPTION VARCHAR2(255 BYTE) Yes

SITES_OLD 5 LOC_ADDRESS_1 VARCHAR2(45 BYTE) Yes

SITES_OLD 6 LOC_ADDRESS_2 VARCHAR2(45 BYTE) Yes

SITES_OLD 7 MAIL_ADDRESS_1 VARCHAR2(45 BYTE) Yes

SITES_OLD 8 MAIL_CITY VARCHAR2(30 BYTE) Yes

SITES_OLD 9 OTHER_LOC_DESCRIPTION VARCHAR2(255 BYTE) Yes

SITES_OLD 10 PHONE_NUM NUMBER(10,0) Yes

SITES_OLD 11 PHONE_EXT NUMBER(4,0) Yes

SITES_OLD 12 NAME VARCHAR2(60 BYTE) Yes

SITES_OLD 13 MAIL_ADDRESS_2 VARCHAR2(45 BYTE) Yes

SITES_OLD 14 LOC_CITY VARCHAR2(30 BYTE) Yes

SITES_OLD 15 FAX_NUM NUMBER(10,0) Yes

SPECIAL_CLASSES 1 ID NUMBER(1,0) No

SPECIAL_CLASSES 2 GENCLSS_ID NUMBER(1,0) No

SPECIAL_CLASSES 3 NAME VARCHAR2(40 BYTE) No

SPECIAL_CLASSES 4 SHORT_NAME VARCHAR2(5 BYTE) Yes

ST 1 O VARCHAR2(30 BYTE) Yes

ST 2 V VARCHAR2(100 BYTE) Yes

ST 3 T VARCHAR2(2000 BYTE)

Yes

STATUSES 1 ID NUMBER(1,0) No

STATUSES 2 NAME VARCHAR2(40 BYTE) No

STATUSES 3 SHORT_NAME VARCHAR2(5 BYTE) Yes





STIMULATIONS 1 ID NUMBER(9,0) No

STIMULATIONS 2 CR_ID NUMBER(9,0) No

STIMULATIONS 3 TOP NUMBER(5,0) No

STIMULATIONS 4 BOTTOM NUMBER(5,0) Yes

STRATIGRAPHIC_INTERPRETATIONS 1 WELL_ID NUMBER(6,0) No

STRATIGRAPHIC_INTERPRETATIONS 2 IDATE DATE No

STRATIGRAPHIC_INTERPRETATIONS 3 IBASIS VARCHAR2(1 BYTE) No

STRATIGRAPHIC_INTERPRETATIONS 4 INT_ID NUMBER(4,0) No

STRATIGRAPHIC_INTERPRETATIONS 5 IREMARK VARCHAR2(100 BYTE) Yes

UNITS_OF_MEASURE 1 CODE NUMBER(5,0) No

UNITS_OF_MEASURE 2 DESCRIPTION VARCHAR2(60 BYTE) No

UNITS_OF_MEASURE 3 ABBREVIATION VARCHAR2(8 BYTE) No

UNITS_OF_MEASURE 4 EPA_STORET_CODE VARCHAR2(1 BYTE) Yes

UNITS_OF_MEASURE 5 TYPE_CODE NUMBER(2,0) No

UNITS_OF_MEASURE 6 USGS_CODE VARCHAR2(1 BYTE) Yes

US_COUNTIES 1 COUNTY_ID NUMBER(4,0) No

US_COUNTIES 2 COUNTY_FIPS_CODE VARCHAR2(3 BYTE) No

US_COUNTIES 3 COUNTY_NAME VARCHAR2(25 BYTE) No

US_COUNTIES 4 STATE_CODE VARCHAR2(2 BYTE) No

US_COUNTIES 5 PA_COUNTY_CODE VARCHAR2(2 BYTE) Yes

US_COUNTIES 6 COUNTY_ABBREVIATION VARCHAR2(2 BYTE) Yes

US_MUNICIPALITIES 1 MUNICIPALITY_ID NUMBER(6,0) No

US_MUNICIPALITIES 2 MUNICIPALITY_FIPS_CODE VARCHAR2(5 BYTE) Yes

US_MUNICIPALITIES 3 MUNICIPALITY_NAME VARCHAR2(60 BYTE) No

US_MUNICIPALITIES 4 TYPE_CODE VARCHAR2(1 BYTE) Yes

US_MUNICIPALITIES 5 MUNICIPALITY_CENSUS_CODE VARCHAR2(6 BYTE) Yes

US_MUNICIPALITIES 6 ACTIVE VARCHAR2(1 BYTE) Yes

WELL_ID_TYPES 1 ID NUMBER(1,0) No

WELL_ID_TYPES 2 NAME VARCHAR2(40 BYTE) No

WELL_ID_TYPES 3 SHORT_NAME VARCHAR2(5 BYTE) Yes

WELL_LOGS_IT 1 WELL_ID NUMBER(6,0) Yes

WELL_LOGS_IT 2 LOG_DESCRIPTION VARCHAR2(255 BYTE) Yes

WELL_TYPES 1 ID NUMBER(2,0) No





WELL_TYPES 2 GENCLSS_ID NUMBER(1,0) No

WELL_TYPES 3 NAME VARCHAR2(40 BYTE) No

WELL_TYPES 4 SHORT_NAME VARCHAR2(5 BYTE) Yes

WELLS 1 ID NUMBER(6,0) No

WELLS 2 PERMIT_NUMBER VARCHAR2(15 BYTE) No

WELLS 3 TANK_METER_NUMBER VARCHAR2(15 BYTE) Yes

WELLS 4 QUAD_SECTION_NUMBER NUMBER(1,0) Yes

WELLS 5 SLAT_DEGREE NUMBER(2,0) Yes

WELLS 6 SLAT_MINUTE NUMBER(2,0) Yes

WELLS 7 SLAT_SECOND NUMBER(2,0) Yes

WELLS 8 SLAT_MILSEC NUMBER(4,0) Yes

WELLS 9 SLONG_DEGREE NUMBER(3,0) Yes

WELLS 10 SLONG_MINUTE NUMBER(2,0) Yes

WELLS 11 SLONG_SECOND NUMBER(2,0) Yes

WELLS 12 SLONG_MILSEC NUMBER(4,0) Yes

WELLS 13 SOUTH_OFFSET NUMBER(6,0) Yes

WELLS 14 WEST_OFFSET NUMBER(6,0) Yes

WELLS 15 TLAT_DEGREE NUMBER(2,0) Yes

WELLS 16 TLAT_MINUTE NUMBER(2,0) Yes

WELLS 17 TLAT_SECOND NUMBER(2,0) Yes

WELLS 18 TLAT_MILSEC NUMBER(4,0) Yes

WELLS 19 TLONG_DEGREE NUMBER(3,0) Yes

WELLS 20 TLONG_MINUTE NUMBER(2,0) Yes

WELLS 21 TLONG_SECOND NUMBER(2,0) Yes

WELLS 22 TLONG_MILSEC NUMBER(4,0) Yes

WELLS 23 COMPLETION_DATE DATE Yes

WELLS 24 INIT_GENCLSS_ID NUMBER(1,0) Yes

WELLS 25 INIT_SPLCLSS_ID NUMBER(1,0) Yes

WELLS 26 INIT_EXPTYPE_ID NUMBER(2,0) Yes

WELLS 27 INIT_DEPTH NUMBER(5,0) Yes

WELLS 28 TOTAL_DEPTH NUMBER(5,0) Yes

WELLS 29 TD_RUNIT_CODE NUMBER(4,0) Yes

WELLS 30 TD_RUNIT_TYPE_CODE VARCHAR2(2 BYTE) Yes





WELLS 31 CURRENT_DEPTH NUMBER(5,0) Yes

WELLS 32 GENCLSS_ID NUMBER(1,0) Yes

WELLS 33 SPLCLSS_ID NUMBER(1,0) Yes

WELLS 34 EXPTYPE_ID NUMBER(2,0) Yes

WELLS 35 WTYPE_ID NUMBER(2,0) Yes

WELLS 36 WIDTYPE_ID NUMBER(1,0) No

WELLS 37 STATUS_ID NUMBER(1,0) Yes

WELLS 38 FIELD_ID NUMBER(4,0) Yes

WELLS 39 POOL_ID NUMBER(4,0) Yes

WELLS 40 DS_INDICATOR VARCHAR2(1 BYTE) Yes

WELLS 41 DATA_REMARK VARCHAR2(100 BYTE) Yes

WELLS 42 GEOLOGIST_REMARK VARCHAR2(100 BYTE) Yes

WELLS 43 CREATION_SOURCE VARCHAR2(6 BYTE) Yes

WELLS 44 CREATION_DATE DATE Yes

WELLS 45 CREATED_BY VARCHAR2(30 BYTE) Yes

WELLS 46 MODIFY_DATE DATE Yes

WELLS 47 MODIFIED_BY VARCHAR2(30 BYTE) Yes

WELLS 48 EFFECTIVE_ATTRIB_UPD_DATE DATE Yes

WELLS 49 FILE_RELEASE_DATE DATE Yes

WELLS 50 PLUG_FLAG VARCHAR2(1 BYTE) Yes

WELLS 51 PERMIT_REG_STATUS VARCHAR2(2 BYTE) Yes

WELLS 52 DATA_SOURCE VARCHAR2(6 BYTE) Yes

WELLS 53 TRUE_LATITUDE NUMBER Yes

WELLS 54 TRUE_LONGITUDE NUMBER Yes

WELLS 55 CHANGE_IN_LOCATION VARCHAR2(1 BYTE) Yes

WELLS 56 QM_DER_CODE VARCHAR2(4 BYTE) Yes

WELLS 57 HW_TYPE VARCHAR2(1 BYTE) Yes

WELLS 58 DECIMAL_LATITUDE NUMBER(10,8) Yes

WELLS 59 DECIMAL_LONGITUDE NUMBER(10,8) Yes

WIS_CONFIGURATION 1 ID_CONFIG NUMBER(12,0) No

WIS_CONFIGURATION 2 CODE_DESC VARCHAR2(60 BYTE) No

WIS_CONFIGURATION 3 CODE_VALUE VARCHAR2(100 BYTE) Yes

WIS_CONFIGURATION 4 CREATED_BY VARCHAR2(30 BYTE) No





WIS_CONFIGURATION 5 CREATED_DATE DATE No

WIS_CONFIGURATION 6 UPDATED_BY VARCHAR2(30 BYTE) Yes

WIS_CONFIGURATION 7 UPDATED_DATE DATE Yes



Appendix D. Data Dictionary - PaGWIS table name column

ID column name data type nullable numeric

precision numeric

scale datetime precision

tblAbandonmentReasonLU 1 AbandonmentReasonCode smallint No 5 0

tblAbandonmentReasonLU 2 AbandonmentReason varchar YES

tblAgencyCodeLU 1 AgencyCode smallint No 5 0

tblAgencyCodeLU 2 AgencyTxt varchar YES

tblAgencyUseInfo 1 CounterLink int YES 10 0

tblAgencyUseInfo 2 TransactionCounter int YES 10 0

tblAgencyUseInfo 3 AgencyUseOfSiteCode varchar YES

tblAgencyUseInfo 4 AgencyUseDate datetime YES 23 3 3

tblAgencyUseInfo 5 ID int No 10 0

tblAgencyUseOfSiteCodeLU 1 AgencyUseOfSiteCode varchar No

tblAgencyUseOfSiteCodeLU 2 AgencyUseOfSiteTxt varchar YES

tblAquiferCodeLU 1 AAPGCode varchar No

tblAquiferCodeLU 2 FormationName varchar YES

tblAquiferCodeLU 3 _1980MapCode varchar YES

tblAquiferCodeLU 4 _1980MapName varchar YES

tblCasingInfo 1 TransactionCounter int YES 10 0

tblCasingInfo 2 ParentSeqNumConsSubrec smallint YES 5 0

tblCasingInfo 3 RecNumCasing smallint YES 5 0

tblCasingInfo 4 TopOfCasing real YES 24

tblCasingInfo 5 BottomOfCasing real YES 24

tblCasingInfo 6 CasingDiameter real YES 24

tblCasingInfo 7 CasingCode varchar YES

tblCasingInfo 8 CasingWallThickness real YES 24

tblCasingInfo 9 ConsLink int YES 10 0

tblCasingInfo 10 CasingCounter int No 10 0

tblCasingInfo 11 upsize_ts timestamp YES

tblCasingInfo 12 TempCasingID int YES 10 0

tblCasingMaterialLU 1 CasingCode varchar No

tblCasingMaterialLU 2 Description varchar YES

tblCasingPackingInfo 1 PackingCode varchar No




column name data type nullable numeric precision

numeric scale

datetime precision

tblCasingPackingInfo 2 TopOfPacking real YES 24

tblCasingPackingInfo 3 BottomOfPacking real YES 24

tblCasingPackingInfo 4 PackingPlacementCode varchar YES

tblCasingPackingInfo 5 MethodEmplacedCode varchar YES

tblCasingPackingInfo 6 CasingLink int YES 10 0

tblCasingPackingInfo 7 ID int No 10 0

tblCasingSealInfo 1 TransactionCounter int YES 10 0

tblCasingSealInfo 2 SealantCode varchar YES

tblCasingSealInfo 3 TopOfSealant real YES 24

tblCasingSealInfo 4 BottomOfSealant real YES 24

tblCasingSealInfo 5 SealPlacementCode varchar YES

tblCasingSealInfo 6 MethodEmplacedCode varchar YES

tblCasingSealInfo 7 CasingLink int No 10 0

tblConstructionInfo 1 RecNumFlag varchar YES

tblConstructionInfo 2 CounterLink int YES 10 0

tblConstructionInfo 3 ConsCounter int No 10 0

tblConstructionInfo 4 TransactionCounter int YES 10 0

tblConstructionInfo 5 RecNumConSubrec smallint YES 5 0

tblConstructionInfo 6 ParentSeqNumConsSubrec smallint YES 5 0

tblConstructionInfo 7 ConstructionDate datetime YES 23 3 3

tblConstructionInfo 8 Driller varchar YES

tblConstructionInfo 9 SourceConsDataCode varchar YES

tblConstructionInfo 10 MethodConsCode varchar YES

tblConstructionInfo 11 FinishCode varchar YES

tblConstructionInfo 12 Drillers_well_id varchar YES

tblConstructionInfo 13 InterimWell_ID int YES 10 0

tblConstructionInfo 14 AbandonmentReasonCode smallint YES 5 0

tblConstructionInfo 15 ConstructionCode int YES 10 0

tblConstructionInfo 16 OriginalDriller smallint YES 5 0

tblConstructionInfo 17 OriginalDrillerName varchar YES

tblConstructionInfo 18 Licensee varchar YES

tblConstructionInfo 19 TempDrillID int YES 10 0

tblConstructionTypeLU 1 ConstructionCode int No 10 0





numeric scale

datetime precision

tblConstructionTypeLU 2 ConstructionType varchar YES

tblContributingUnitCodeLU 1 ContributingUnitCode varchar No

tblContributingUnitCodeLU 2 ContributingUnitTxt varchar YES

tblContributingUnitCodeLU 3 ContributingUnitRank smallint YES 5 0

tblCoordMethodLU 1 CoordCode int No 10 0

tblCoordMethodLU 2 Description varchar YES

tblCountyCodeLU 1 CountyNum varchar No

tblCountyCodeLU 2 AlphNum varchar YES

tblCountyCodeLU 3 County varchar YES

tblCountyCodeLU 4 Last_WWI varchar YES

tblDatabaseDownload 1 DatabaseID int No 10 0

tblDatabaseDownload 2 DatabaseName varchar No

tblDatabaseDownload 3 DatabaseFile image No

tblDatabaseDownload 4 DatabaseSize int No 10 0

tblDatabaseDownload 5 ModifyDate smalldatetime No 16 0 3

tblDataReliabilityLU 1 DataReliabilityCode varchar No

tblDataReliabilityLU 2 DataReliabilityTxt varchar YES

tblDischargeMeasMethodCodeLU 1 DischargeCode varchar No

tblDischargeMeasMethodCodeLU 2 DischargeMeasMethod varchar YES

tblDischargeTypeLU 1 DischargeTypeCode varchar No

tblDischargeTypeLU 2 DischargeTypeTxt varchar YES

tblDrillerLU 1 LicenseNumber varchar No

tblDrillerLU 2 Licensee varchar YES

tblDrillersLogInfo 1 ConsLink int YES 10 0

tblDrillersLogInfo 2 TopOfInterval real YES 24

tblDrillersLogInfo 3 BottomOfInterval real YES 24

tblDrillersLogInfo 4 Description varchar YES

tblDrillersLogInfo 5 ID int No 10 0

tblElevMethodLU 1 ElevMethodCode varchar No

tblElevMethodLU 2 ElevMethodTxt varchar YES

tblFieldQWCodeLU 1 QWCode varchar No

tblFieldQWCodeLU 2 QWParameter varchar YES

tblFieldQWInfo 1 TransactionCounter int YES 10 0





numeric scale

datetime precision

tblFieldQWInfo 2 SeqNumQualSubrec smallint YES 5 0

tblFieldQWInfo 3 AAPGCode varchar YES

tblFieldQWInfo 4 QWCode varchar YES

tblFieldQWInfo 5 QWValue real YES 24

tblFieldQWInfo 6 VisitLink int YES 10 0

tblFieldQWInfo 7 DateQWMeas datetime YES 23 3 3

tblFieldQWInfo 8 id int No 10 0

tblFinishCodeLU 1 FinishCode varchar No

tblFinishCodeLU 2 FinishMethod varchar YES

tblFinishCodeLU 3 FinishExplanation varchar YES

tblGenSiteInfo 1 GeneralCounter int No 10 0

tblGenSiteInfo 2 DEPCounter int YES 10 0

tblGenSiteInfo 3 SiteID varchar YES

tblGenSiteInfo 4 TransactionCounter int YES 10 0

tblGenSiteInfo 5 LocalWellNumber varchar YES

tblGenSiteInfo 6 CountyCode varchar YES

tblGenSiteInfo 7 AAPGCode varchar YES

tblGenSiteInfo 8 TopographyCode varchar YES

tblGenSiteInfo 9 WellDepth real YES 24

tblGenSiteInfo 10 Elevation real YES 24

tblGenSiteInfo 11 ElevMethodCode varchar YES

tblGenSiteInfo 12 AccuracyOfElevation varchar YES

tblGenSiteInfo 13 HydrologicUnit varchar YES

tblGenSiteInfo 14 LatLongAccuracyCode varchar YES

tblGenSiteInfo 15 QuadCode smallint YES 5 0

tblGenSiteInfo 16 TypeOfSiteCode varchar YES

tblGenSiteInfo 17 DateCreated datetime YES 23 3 3

tblGenSiteInfo 18 DateUpdated datetime YES 23 3 3

tblGenSiteInfo 19 DataReliabilityCode varchar YES

tblGenSiteInfo 20 SourceDepthDataCode varchar YES

tblGenSiteInfo 21 MunicipalityCode varchar YES

tblGenSiteInfo 22 LatitudeDD float YES 53

tblGenSiteInfo 23 LongitudeDD float YES 53





numeric scale

datetime precision

tblGenSiteInfo 24 WellAddress varchar YES

tblGenSiteInfo 25 WellZipCode varchar YES

tblGenSiteInfo 26 DepthToBedrock real YES 24

tblGenSiteInfo 27 BedrockNotReached bit YES 1 0

tblGenSiteInfo 28 SaltwaterZone real YES 24

tblGenSiteInfo 29 DateDrilled datetime YES 23 3 3

tblGenSiteInfo 30 PaGWIS_ID int YES 10 0

tblGenSiteInfo 31 SourceSiteDataCode smallint YES 5 0

tblGenSiteInfo 32 LocalPermit varchar YES

tblGenSiteInfo 33 LatestOwner int YES 10 0

tblGenSiteInfo 34 DrillersCoordMethod int YES 10 0

tblGenSiteInfo 35 LatestProduction int YES 10 0

tblGenSiteInfo 36 LatestWellUse int YES 10 0

tblGenSiteInfo 37 upsize_ts timestamp YES

tblGenSiteInfo 38 TempWellID int YES 10 0

tblGenSiteInfo_Fixes 1 GeneralCounter nvarchar YES

tblGenSiteInfo_Fixes 2 LocalWellNumber nvarchar YES

tblGenSiteInfo_Fixes 3 AAPGCode nvarchar YES

tblGenSiteInfo_Fixes 4 Correction nvarchar YES

tblGenSiteInfo_Fixes 5 Comment nvarchar YES

tblGenSiteInfo_Fixes 6 LatitudeDD nvarchar YES

tblGenSiteInfo_Fixes 7 LongitudeDD nvarchar YES

tblGenSiteInfo_Fixes 8 PaGWIS_ID nvarchar YES

tblGenSiteInfoImage 1 ImageID int No 10 0

tblGenSiteInfoImage 2 CounterLink int No 10 0

tblGenSiteInfoImage 3 ImageName varchar No

tblGenSiteInfoImage 4 DateEntered datetime No 23 3 3

tblGeohydrologicInfo 1 CounterLink int YES 10 0

tblGeohydrologicInfo 2 TransactionCounter int YES 10 0

tblGeohydrologicInfo 3 SeqNumGEOHSubrec smallint YES 5 0

tblGeohydrologicInfo 4 ParentSeqNumAQFRSubrec smallint YES 5 0

tblGeohydrologicInfo 5 AAPGCode varchar YES

tblGeohydrologicInfo 6 LithologyCode varchar YES





numeric scale

datetime precision

tblGeohydrologicInfo 7 ContributingUnitCode varchar YES

tblGeohydrologicInfo 8 TopOfInterval real YES 24

tblGeohydrologicInfo 9 BottomOfInterval real YES 24

tblGeohydrologicInfo 10 ID int No 10 0

tblHoleInfo 1 TransactionCounter int YES 10 0

tblHoleInfo 2 ParentSeqNumConsSubrec smallint YES 5 0

tblHoleInfo 3 RecNumHoleSubrec smallint YES 5 0

tblHoleInfo 4 TopOfHole real YES 24

tblHoleInfo 5 BottomOfHole real YES 24

tblHoleInfo 6 HoleDiameter real YES 24

tblHoleInfo 7 Remarks varchar YES

tblHoleInfo 8 ConsLink int YES 10 0

tblHoleInfo 9 HoleCounter int No 10 0

tblHoleInfo 10 upsize_ts timestamp YES

tblHolePackingInfo 1 TopOfPacking real YES 24

tblHolePackingInfo 2 BottomOfPacking real YES 24

tblHolePackingInfo 3 PackingCode varchar YES

tblHolePackingInfo 4 MethodEmplacedCode varchar YES

tblHolePackingInfo 5 Remarks varchar YES

tblHolePackingInfo 6 HoleLink int No 10 0

tblHoleSealInfo 1 TopOfSealant real YES 24

tblHoleSealInfo 2 BottomOfSealant real YES 24

tblHoleSealInfo 3 SealantCode varchar YES

tblHoleSealInfo 4 MethodEmplacedCode varchar YES

tblHoleSealInfo 5 Remarks varchar YES

tblHoleSealInfo 6 HoleLink int No 10 0

tblLatLongAccuracyCodeLU 1 LatLongAccuracyCode varchar No

tblLatLongAccuracyCodeLU 2 LatLongAccuracyTxt varchar YES

tblLinerInfo 1 ConsLink int YES 10 0

tblLinerInfo 2 LinerTop real YES 24

tblLinerInfo 3 LinerBottom real YES 24

tblLinerInfo 4 LinerDiameter real YES 24

tblLinerInfo 5 PVCLinerType int YES 10 0





numeric scale

datetime precision

tblLinerInfo 6 upsize_ts timestamp YES

tblLinerInfo 7 LinerID int No 10 0

tblLithologyCodeLU 1 LithologyCode varchar No

tblLithologyCodeLU 2 LithologyTxt varchar YES

tblLithologyCodeLU 3 DERLithCode smallint YES 5 0

tblMemo 1 Date datetime YES 23 3 3

tblMemo 2 Note text YES

tblMemo 3 id int No 10 0

tblMethodConsCodeLU 1 ConsCode varchar No

tblMethodConsCodeLU 2 MethodCons varchar YES

tblMethodEmplacedLU 1 MethodEmplacedCode varchar No

tblMethodEmplacedLU 2 MethodTxt varchar YES

tblMethodEmplacedLU 3 Explanation varchar YES

tblMunicipalityCodeLU 1 MunicipalityCode varchar No

tblMunicipalityCodeLU 2 Municipality varchar YES

tblMunicipalityCodeLU 3 County varchar YES

tblOpeningTypeCodeLU 1 OpeningCode varchar No

tblOpeningTypeCodeLU 2 TypeOfOpening varchar YES

tblOpenIntervalMaterialLU 1 OpenIntervalMaterialCode varchar No

tblOpenIntervalMaterialLU 2 OpenIntervalMaterialTxt varchar YES

tblOtherIDInfo 1 CounterLink int YES 10 0

tblOtherIDInfo 2 TransactionCounter int YES 10 0

tblOtherIDInfo 3 SeqNumOtherIDSubrec smallint YES 5 0

tblOtherIDInfo 4 OtherIdentifier varchar YES

tblOtherIDInfo 5 OtherIDAssignor varchar YES

tblOtherIDInfo 6 ID int No 10 0

tblOwnerInfo 1 CounterLink int YES 10 0

tblOwnerInfo 2 TransactionCounter int YES 10 0

tblOwnerInfo 3 SeqNumOwnerSubrec smallint YES 5 0

tblOwnerInfo 4 Owner varchar YES

tblOwnerInfo 5 ZIPCode varchar YES

tblOwnerInfo 6 OwnerFirstName varchar YES

tblOwnerInfo 7 DateOwnership datetime YES 23 3 3





numeric scale

datetime precision

tblOwnerInfo 8 ConsLink int YES 10 0

tblOwnerInfo 9 OwnerID int No 10 0

tblPackerInfo 1 PackerID int No 10 0

tblPackerInfo 2 ConsLink int YES 10 0

tblPackerInfo 3 PackerTop real YES 24

tblPackerInfo 4 PackerBottom real YES 24

tblPackerInfo 5 PackerSealant bit YES 1 0

tblPackerInfo 6 upsize_ts timestamp YES

tblPackingCodeLU 1 PackingCode varchar No

tblPackingCodeLU 2 PackingType varchar YES

tblPackingCodeLU 3 Explanation varchar YES

tblPaGWIS_ID_Creator 1 Well_GenSiteCounter int YES 10 0

tblPaGWIS_ID_Creator 2 PaGWIS_ID int No 10 0

tblPaGWIS_ID_Creator 3 Spring_GenSiteCounter int YES 10 0

tblPlacementCodeLU 1 PlacementCode varchar No

tblPlacementCodeLU 2 Placement varchar YES

tblPlacementCodeLU 3 Explanation varchar YES

tblProductionInfo 1 CounterLink int YES 10 0

tblProductionInfo 2 TransactionCounter int YES 10 0

tblProductionInfo 3 ProdSeqNum varchar YES

tblProductionInfo 4 DischargeTypeCode varchar YES

tblProductionInfo 5 DataSourceCode varchar YES

tblProductionInfo 6 DischargeMeasMethodCode varchar YES

tblProductionInfo 7 Discharge real YES 24

tblProductionInfo 8 SWL real YES 24

tblProductionInfo 9 WLDataSourceCode varchar YES

tblProductionInfo 10 WLMeasMethodCode varchar YES

tblProductionInfo 11 ProdWL real YES 24

tblProductionInfo 12 Drawdown real YES 24

tblProductionInfo 13 SpecCap real YES 24

tblProductionInfo 14 TestLength real YES 24

tblProductionInfo 15 SiteStatusWLMeasCode varchar YES

tblProductionInfo 16 DateDischarged datetime YES 23 3 3





numeric scale

datetime precision

tblProductionInfo 17 ConsLink int YES 10 0

tblProductionInfo 18 ProductionID int No 10 0

tblPumpIntakeInfo 1 CounterLink int YES 10 0

tblPumpIntakeInfo 2 TransactionCounter int YES 10 0

tblPumpIntakeInfo 3 RecNumLiftSubrec smallint YES 5 0

tblPumpIntakeInfo 4 DepthOfIntake real YES 24

tblPumpIntakeInfo 5 ID int No 10 0

tblPVCLinerTypeLU 1 LinerCode int No 10 0

tblPVCLinerTypeLU 2 Description varchar YES

tblQuadLU 1 DERCode smallint No 5 0

tblQuadLU 2 QuadName varchar YES

tblQuadLU 3 UTMZone smallint YES 5 0

tblQWCounterCodeValueInfo 1 QWTableCounter int No 10 0

tblQWCounterCodeValueInfo 2 QWDateCounter int YES 10 0

tblQWCounterCodeValueInfo 3 QWCode varchar YES

tblQWCounterCodeValueInfo 4 QWValue float YES 53

tblQWCounterCodeValueInfo 5 QWRemarkCode varchar YES

tblQWCounterCodeValueInfo 6 QWQACode varchar YES

tblQWCounterCodeValueInfo 7 QWMethodCode varchar YES

tblQWCounterCodeValueInfo 8 QWSignificantDigits varchar YES

tblQWCounterCodeValueInfo 9 upsize_ts timestamp YES

tblQWCounterCodeValueInfo 10 ID int No 10 0

tblQWDate&TimeInfo 1 QWDateCounter int No 10 0

tblQWDate&TimeInfo 2 LinkWithWells int YES 10 0

tblQWDate&TimeInfo 3 LinkWithSprings int YES 10 0

tblQWDate&TimeInfo 4 SiteID varchar YES

tblQWDate&TimeInfo 5 Date datetime YES 23 3 3

tblQWDate&TimeInfo 6 Time varchar YES

tblQWDate_TimeInfo 1 QWDateCounter int No 10 0

tblQWDate_TimeInfo 2 LinkWithWells int YES 10 0

tblQWDate_TimeInfo 3 LinkWithSprings int YES 10 0

tblQWDate_TimeInfo 4 SiteID nvarchar YES

tblQWDate_TimeInfo 5 Date smalldatetime YES 16 0 3





numeric scale

datetime precision

tblQWDate_TimeInfo 6 Time nvarchar YES

tblQWMemo 1 MemoCounter int No 10 0

tblQWMemo 2 Date datetime YES 23 3 3

tblQWMemo 3 Memo text YES

tblQWMemo 4 upsize_ts timestamp YES

tblQWMethodCodeLU 1 ParameterCode varchar YES

tblQWMethodCodeLU 2 MethodCode varchar YES

tblQWMethodCodeLU 3 LongName varchar YES

tblQWMethodCodeLU 4 ShortName varchar YES

tblQWMethodCodeLU 5 LabCode varchar YES

tblQWMethodCodeLU 6 TWRIMethod varchar YES

tblQWMethodCodeLU 7 MinimumReport varchar YES

tblQWMethodCodeLU 8 A varchar YES

tblQWMethodCodeLU 9 B varchar YES

tblQWMethodCodeLU 10 C varchar YES

tblQWMethodCodeLU 11 D varchar YES

tblQWMethodCodeLU 12 E varchar YES

tblQWMethodCodeLU 13 F varchar YES

tblQWMethodCodeLU 14 G varchar YES

tblQWMethodCodeLU 15 ID int No 10 0

tblQWQACodeLU 1 QWQACode varchar No

tblQWQACodeLU 2 Description varchar YES

tblQWQACodeLU 3 ID int No 10 0

tblQWRemarkCodeLU 1 QWRemarkCode varchar No

tblQWRemarkCodeLU 2 Description varchar YES

tblQWRemarkCodeLU 3 ID int No 10 0

tblRemarksInfo 1 CounterLink int YES 10 0

tblRemarksInfo 2 TransactionCounter int YES 10 0

tblRemarksInfo 3 SeqNum int YES 10 0

tblRemarksInfo 4 Remark varchar YES

tblRemarksInfo 5 RemarkDate datetime YES 23 3 3

tblRemarksInfo 6 ID int No 10 0

tblScreenAndOpeningInfo 1 ScreenSlotOpenCounter int No 10 0





numeric scale

datetime precision

tblScreenAndOpeningInfo 2 TransactionCounter int YES 10 0

tblScreenAndOpeningInfo 3 ParentSeqNumConsSubrec smallint YES 5 0

tblScreenAndOpeningInfo 4 RecNumOpeningSubrec smallint YES 5 0

tblScreenAndOpeningInfo 5 TopOpenInterval real YES 24

tblScreenAndOpeningInfo 6 BottomOpenInterval real YES 24

tblScreenAndOpeningInfo 7 DiameterOpenInterval real YES 24

tblScreenAndOpeningInfo 8 OpenIntervalMaterialCode varchar YES

tblScreenAndOpeningInfo 9 OpeningCode varchar YES

tblScreenAndOpeningInfo 10 YieldOfInterval real YES 24

tblScreenAndOpeningInfo 11 SlotSize real YES 24

tblScreenAndOpeningInfo 12 ConsLink int YES 10 0

tblScreenAndOpeningInfo 13 upsize_ts timestamp YES

tblScreenAndOpeningInfo 14 TempOpeningID int YES 10 0

tblScreenPackingInfo 1 PackingCode varchar No

tblScreenPackingInfo 2 TopOfPacking real YES 24

tblScreenPackingInfo 3 BottomOfPacking real YES 24

tblScreenPackingInfo 4 PackingPlacementCode varchar YES

tblScreenPackingInfo 5 MethodEmplacedCode varchar YES

tblScreenPackingInfo 6 ScreenSlotOpenLink int YES 10 0

tblScreenPackingInfo 7 ID int No 10 0

tblScreenSealInfo 1 SealantCode varchar No

tblScreenSealInfo 2 TopOfSealant real YES 24

tblScreenSealInfo 3 BottomOfSealant real YES 24

tblScreenSealInfo 4 ScreenPlacementCode varchar YES

tblScreenSealInfo 5 MethodEmplacedCode varchar YES

tblScreenSealInfo 6 ScreenSlotOpenLink int No 10 0

tblSealantCodeLU 1 SealantCode varchar No

tblSealantCodeLU 2 SealantName varchar YES

tblSealantCodeLU 3 Explanation varchar YES

tblSiteAndWaterUseInfo 1 CounterLink int YES 10 0

tblSiteAndWaterUseInfo 2 TransactionCounter int YES 10 0

tblSiteAndWaterUseInfo 3 SiteUseCode varchar YES

tblSiteAndWaterUseInfo 4 DateOfUse datetime YES 23 3 3





numeric scale

datetime precision

tblSiteAndWaterUseInfo 5 Note varchar YES

tblSiteAndWaterUseInfo 6 WaterUseCode varchar YES

tblSiteAndWaterUseInfo 7 SiteWaterID int No 10 0

tblSiteStatusWLMeasurementLU 1 SiteStatusWLMeasCode varchar No

tblSiteStatusWLMeasurementLU 2 SiteStatusWLMeasTxt varchar YES

tblSourceOfDataLU 1 SourceCode varchar No

tblSourceOfDataLU 2 SourceOfData varchar YES

tblSourceOfSiteRecordLU 1 SourceOfSiteCode smallint No 5 0

tblSourceOfSiteRecordLU 2 SourceOfSiteRecordTxt varchar YES

tblSourceOfSiteRecordLU 3 ExplanationOfSource varchar YES

tblSphereOfDischargeLU 1 Sphere_Code varchar No

tblSphereOfDischargeLU 2 SphereOfDischarge varchar YES

tblSphereOfDischargeLU 3 ID int No 10 0

tblSpringAgencyUseInfo 1 CounterLink int YES 10 0

tblSpringAgencyUseInfo 2 AgencyUseCounter int No 10 0

tblSpringAgencyUseInfo 3 TransactionCounter int YES 10 0

tblSpringAgencyUseInfo 4 AgencyUseOfSite varchar YES

tblSpringAgencyUseInfo 5 DateOfAgencyUse datetime YES 23 3 3

tblSpringFieldQWInfo 1 CounterLink int YES 10 0

tblSpringFieldQWInfo 2 TransactionCounter int YES 10 0

tblSpringFieldQWInfo 3 SeqNumQualSubrec smallint YES 5 0

tblSpringFieldQWInfo 4 FormationSampled varchar YES

tblSpringFieldQWInfo 5 QWCode varchar YES

tblSpringFieldQWInfo 6 QWValue real YES 24

tblSpringFieldQWInfo 7 DateQWMeasured datetime YES 23 3 3

tblSpringFieldQWInfo 8 ID int No 10 0

tblSpringGenInfo 1 SpringGenCounter int No 10 0

tblSpringGenInfo 2 SiteID varchar YES

tblSpringGenInfo 3 TransactionCounter int YES 10 0

tblSpringGenInfo 4 LocalWellNumber varchar YES

tblSpringGenInfo 5 CountyCode varchar YES

tblSpringGenInfo 6 Quad varchar YES

tblSpringGenInfo 7 QuadCode smallint YES 5 0





numeric scale

datetime precision

tblSpringGenInfo 8 Topography varchar YES

tblSpringGenInfo 9 Elevation float YES 53

tblSpringGenInfo 10 ElevMethod varchar YES

tblSpringGenInfo 11 ElevAccuracy varchar YES

tblSpringGenInfo 12 HydrologicUnit varchar YES

tblSpringGenInfo 13 LatLongAccuracyCode varchar YES

tblSpringGenInfo 14 TypeOfSite varchar YES

tblSpringGenInfo 15 Formation varchar YES

tblSpringGenInfo 16 DataReliability varchar YES

tblSpringGenInfo 17 SpringName varchar YES

tblSpringGenInfo 18 SpringType varchar YES

tblSpringGenInfo 19 PermanenceOfSpring varchar YES

tblSpringGenInfo 20 SphereOfDischarge varchar YES

tblSpringGenInfo 21 Improvements varchar YES

tblSpringGenInfo 22 NumOfOpenings varchar YES

tblSpringGenInfo 23 FlowVariability varchar YES

tblSpringGenInfo 24 AccuracyOfFlowVariability varchar YES

tblSpringGenInfo 25 MunicipalityCode varchar YES

tblSpringGenInfo 26 DateCreated datetime YES 23 3 3

tblSpringGenInfo 27 DateUpdated datetime YES 23 3 3

tblSpringGenInfo 28 LatitudeDD float YES 53

tblSpringGenInfo 29 LongitudeDD float YES 53

tblSpringGenInfo 30 SourceSiteDataCode smallint YES 5 0

tblSpringGenInfo 31 PaGWIS_ID int YES 10 0

tblSpringGenInfo 32 upsize_ts timestamp YES

tblSpringGEOHInfo 1 CounterLink int YES 10 0

tblSpringGEOHInfo 2 TransactionCounter int YES 10 0

tblSpringGEOHInfo 3 SeqNumGEOHSubrec smallint YES 5 0

tblSpringGEOHInfo 4 ParentSeqNumAQFRSubrec smallint YES 5 0

tblSpringGEOHInfo 5 FormationCode varchar YES

tblSpringGEOHInfo 6 LithologyCode varchar YES

tblSpringGEOHInfo 7 ContributingUnit varchar YES

tblSpringGEOHInfo 8 ID int No 10 0





numeric scale

datetime precision

tblSpringMemo 1 MemoCounter int No 10 0

tblSpringMemo 2 Date datetime YES 23 3 3

tblSpringMemo 3 Memo text YES

tblSpringMemo 4 upsize_ts timestamp YES

tblSpringOtherIDInfo 1 CounterLink int YES 10 0

tblSpringOtherIDInfo 2 TransactionCounter int YES 10 0

tblSpringOtherIDInfo 3 SeqNumOtherIDSubrec smallint YES 5 0

tblSpringOtherIDInfo 4 OtherIdentifier varchar YES

tblSpringOtherIDInfo 5 OtherIDAssignor varchar YES

tblSpringOtherIDInfo 6 ID int No 10 0

tblSpringOwnerInfo 1 CounterLink int YES 10 0

tblSpringOwnerInfo 2 TransactionCounter int YES 10 0

tblSpringOwnerInfo 3 SeqNumOwnerSubrec smallint YES 5 0

tblSpringOwnerInfo 4 Owner varchar YES

tblSpringOwnerInfo 5 DateOwned datetime YES 23 3 3

tblSpringOwnerInfo 6 ID int No 10 0

tblSpringPermanenceLU 1 Permanence_Code varchar No

tblSpringPermanenceLU 2 Permanence varchar YES

tblSpringPermanenceLU 3 ID int No 10 0

tblSpringProdInfo 1 CounterLink int YES 10 0

tblSpringProdInfo 2 TransactionCounter int YES 10 0

tblSpringProdInfo 3 ProdSeqNum smallint YES 5 0

tblSpringProdInfo 4 DischargeType varchar YES

tblSpringProdInfo 5 DataSource varchar YES

tblSpringProdInfo 6 MeasuredMethod varchar YES

tblSpringProdInfo 7 Discharge real YES 24

tblSpringProdInfo 8 SWL real YES 24

tblSpringProdInfo 9 WL_DataSource varchar YES

tblSpringProdInfo 10 WLMeasuredMethod varchar YES

tblSpringProdInfo 11 DateDischarged datetime YES 23 3 3

tblSpringProdInfo 12 ID int No 10 0

tblSpringRemarkInfo 1 CounterLink int YES 10 0

tblSpringRemarkInfo 2 TransactionCounter int YES 10 0





numeric scale

datetime precision

tblSpringRemarkInfo 3 Remark varchar YES

tblSpringRemarkInfo 4 RemarkDate datetime YES 23 3 3

tblSpringTypeLU 1 Sp_Type_Code varchar No

tblSpringTypeLU 2 Spring_Type varchar YES

tblSpringTypeLU 3 ID int No 10 0

tblSpringUseOfSiteInfo 1 CounterLink int No 10 0

tblSpringUseOfSiteInfo 2 TransactionCounter int YES 10 0

tblSpringUseOfSiteInfo 3 UseOfSiteCode varchar YES

tblSpringUseOfSiteInfo 4 DateOfSiteUse datetime YES 23 3 3

tblSpringUseOfSiteInfo 5 Note varchar YES

tblSpringVisitInfo 1 CounterLink int YES 10 0

tblSpringVisitInfo 2 TransactionCounter int YES 10 0

tblSpringVisitInfo 3 SeqNumVisitSubrec smallint YES 5 0

tblSpringVisitInfo 4 VisitorName varchar YES

tblSpringVisitInfo 5 VisitDate datetime YES 23 3 3

tblSpringWaterLevelInfo 1 CounterLink int No 10 0

tblSpringWaterLevelInfo 2 TransactionCounter int YES 10 0

tblSpringWaterLevelInfo 3 TimeWLMeasured varchar YES

tblSpringWaterLevelInfo 4 WaterLevel real YES 24

tblSpringWaterLevelInfo 5 WaterLevelStatus varchar YES

tblSpringWaterLevelInfo 6 WaterLevelMethod varchar YES

tblSpringWaterLevelInfo 7 SourceWLData varchar YES

tblSpringWaterLevelInfo 8 AccuracyCode varchar YES

tblSpringWaterLevelInfo 9 DateMeasured datetime YES 23 3 3

tblSpringWaterUseInfo 1 CounterLink int YES 10 0

tblSpringWaterUseInfo 2 TransactionCounter int YES 10 0

tblSpringWaterUseInfo 3 WaterUseCode varchar YES

tblSpringWaterUseInfo 4 DateOfWaterUse datetime YES 23 3 3

tblSpringWaterUseInfo 5 Note varchar YES

tblTopoCodeLU 1 TopoCode varchar No

tblTopoCodeLU 2 Topography varchar YES

tblTransaction 1 TransactionCounter int No 10 0

tblTransaction 2 UserCurrent smallint YES 5 0





numeric scale

datetime precision

tblTransaction 3 Agency smallint YES 5 0

tblTransaction 4 DateCurrent datetime YES 23 3 3

tblTransaction 5 TransactionType varchar YES

tblTypeOfSiteCodeLU 1 TypeOfSiteCode varchar No

tblTypeOfSiteCodeLU 2 TypeOfSiteTxt varchar YES

tblUseOfSiteCodeLU 1 UseOfSiteCode varchar No

tblUseOfSiteCodeLU 2 UseOfSiteTxt varchar YES

tblUseOfSiteCodeLU 3 ID int No 10 0

tblVisitInfo 1 CounterLink int YES 10 0

tblVisitInfo 2 TransactionCounter int YES 10 0

tblVisitInfo 3 SeqNumVisitSubrec smallint YES 5 0

tblVisitInfo 4 VisitorName varchar YES

tblVisitInfo 5 VisitCounter int No 10 0

tblVisitInfo 6 VisitDate datetime YES 23 3 3

tblVisitInfo 7 TempVisitID int YES 10 0

tblWaterQualityCodeLU 1 QWCode varchar No

tblWaterQualityCodeLU 2 ShortName varchar YES

tblWaterQualityCodeLU 3 LongName text YES

tblWaterQualityCodeLU 4 upsize_ts timestamp YES

tblWaterUseCodeLU 1 WaterUseCode varchar No

tblWaterUseCodeLU 2 WaterUse varchar YES

tblWaterUseCodeLU 3 ID int No 10 0

tblWBZInfo 1 TransactionCounter int YES 10 0

tblWBZInfo 2 ParentSeqNumConsSubrec smallint YES 5 0

tblWBZInfo 3 RecNumOpeningSubrec smallint YES 5 0

tblWBZInfo 4 TopOpenInterval real YES 24

tblWBZInfo 5 BottomOpenInterval real YES 24

tblWBZInfo 6 YieldOfInterval real YES 24

tblWBZInfo 7 ConsLink int YES 10 0

tblWBZInfo 8 OpeningCode varchar YES

tblWBZInfo 9 ID int No 10 0

tblWhatsNew 1 ItemID int No 10 0

tblWhatsNew 2 EffectiveDate smalldatetime YES 16 0 3





numeric scale

datetime precision

tblWhatsNew 3 AppliesTo varchar YES

tblWhatsNew 4 Description varchar YES

tblWhatsNew 5 CreatedDate datetime YES 23 3 3

tblWLMeasMethodCodeLU 1 WLMeasMethodCode varchar No

tblWLMeasMethodCodeLU 2 WLMeasMethod varchar YES



Appendix E. Data Dictionary - WebDriller table name column

ID column name data type nullable numeric

precision numeric

scale datetime precision

tblAbandonmentReason 1 Code int NO 10 0

tblAbandonmentReason 2 Description varchar YES

tblAbandonmentReason 3 msrepl_synctran_ts timestamp NO

tblActivity 1 Code int NO 10 0

tblActivity 2 Description varchar YES

tblActivity 3 msrepl_synctran_ts timestamp NO

tblAdminDataEntryPersonnel 1 NameID int NO 10 0

tblAdminDataEntryPersonnel 2 FName varchar YES

tblAdminDataEntryPersonnel 3 LName varchar YES

tblAdminDataEntryPersonnel 4 TempDrillID char YES

tblAdminDataEntryPersonnel 5 Active bit YES

tblAdminDataEntryPersonnel 6 msrepl_synctran_ts timestamp NO

tblAuditLogin 1 AuditLoginID bigint NO 19 0

tblAuditLogin 2 AuditUserName varchar NO

tblAuditLogin 3 AuditPasswordEntered varchar NO

tblAuditLogin 4 AuditTimestamp datetime NO 3

tblAuditLogin 5 AuditSuccessfulLogin bit NO

tblCasing 1 CasingID int NO 10 0

tblCasing 2 DrillID int YES 10 0

tblCasing 3 CasingTop real YES 24

tblCasing 4 CasingBottom real YES 24

tblCasing 5 CasingDiameter real YES 24

tblCasing 6 CasingMaterial varchar YES

tblCasing 7 SealTop real YES 24

tblCasing 8 SealBottom real YES 24

tblCasing 9 SealType varchar YES

tblCasing 10 upsize_ts timestamp YES

tblCasingMaterial 1 Code varchar NO

tblCasingMaterial 2 Description varchar YES

tblCasingMaterial 3 msrepl_synctran_ts timestamp NO





numeric scale

datetime precision

tblContactInfo 1 PhoneNumber varchar YES

tblContactInfo 2 EmailAddress varchar YES

tblCoordMethod 1 Code int NO 10 0

tblCoordMethod 2 Description varchar YES

tblCoordMethod 3 msrepl_synctran_ts timestamp NO

tblCounty 1 Code varchar NO

tblCounty 2 Name varchar YES

tblCounty 3 CountyNumber varchar YES

tblCounty 4 UTMZone smallint NO 5 0

tblCounty 5 State char YES

tblCounty 6 msrepl_synctran_ts timestamp NO

tblCounty 7 LongitudeMin float YES 53

tblCounty 8 LongitudeMax float YES 53

tblCounty 9 LatitudeMin float YES 53

tblCounty 10 LatitudeMax float YES 53

tblDrill 1 DrillID int NO 10 0

tblDrill 2 WellID int YES 10 0

tblDrill 3 DrillerWellReference varchar YES

tblDrill 4 OriginalDriller smallint YES 5 0

tblDrill 5 TypeOfActivity int YES 10 0

tblDrill 6 ReasonForAbandonment int YES 10 0

tblDrill 7 OwnerFirstName varchar YES

tblDrill 8 OwnerLastNameOrCompany

varchar YES

tblDrill 9 WellAddress varchar YES

tblDrill 10 WellZipCode varchar YES

tblDrill 11 DrillerID int YES 10 0

tblDrill 12 DateDrilled datetime YES 3

tblDrill 13 WellUse varchar YES

tblDrill 14 WaterUse varchar YES

tblDrill 15 DrillingMethod varchar YES

tblDrill 16 WellDepth real YES 24

tblDrill 17 YieldMeasurementMethod varchar YES





numeric scale

datetime precision

tblDrill 18 WellYield real YES 24

tblDrill 19 StaticWaterLevel real YES 24

tblDrill 20 WaterLevelAfterPumping real YES 24

tblDrill 21 DepthToBedrock real YES 24

tblDrill 22 BedrockNotReached bit YES

tblDrill 23 WellFinish varchar YES

tblDrill 24 Description varchar YES

tblDrill 25 SaltwaterZone real YES 24

tblDrill 26 LengthOfTest real YES 24

tblDrill 27 Printout bit YES

tblDrill 28 Downloaded bit YES

tblDrill 29 Completed bit YES

tblDrill 30 OriginalDrillerName varchar YES

tblDrill 31 LocalPermit varchar YES

tblDrill 32 upsize_ts timestamp YES

tblDrill 33 DateEntered datetime YES 3

tblDrill 34 ErrorState smallint YES 5 0

tblDrill 35 PaGWIS bit YES

tblDrill 36 EnteredBy int YES 10 0

tblDrill 37 InternalEntry bit YES

tblDriller 1 DrillerID int NO 10 0

tblDriller 2 LicenseNumber varchar YES

tblDriller 3 FirstName varchar YES

tblDriller 4 LastNameOrCompany varchar YES

tblDriller 5 Email varchar YES

tblDriller 6 Password varchar YES

tblDriller 7 MI char YES

tblDriller 8 TypeOfBusiness int YES 10 0

tblDriller 9 Address1 varchar YES

tblDriller 10 Address2 varchar YES

tblDriller 11 City varchar YES

tblDriller 12 CountyCode char YES

tblDriller 13 State char YES





numeric scale

datetime precision

tblDriller 14 Zip char YES

tblDriller 15 ZipPlusFour char YES

tblDriller 16 Phone char YES

tblDriller 17 DateFirstLicensed smalldatetime

YES 3

tblDriller 18 LicensePassword varchar YES

tblDriller 19 ModifiedBy varchar YES

tblDriller 20 ModifyDate smalldatetime

YES 3

tblDriller 21 msrepl_synctran_ts timestamp NO

tblDrillerLog 1 DrillerLogID int NO 10 0

tblDrillerLog 2 DrillID int YES 10 0

tblDrillerLog 3 LogTop real YES 24

tblDrillerLog 4 LogBase real YES 24

tblDrillerLog 5 Description varchar YES

tblDrillerLog 6 upsize_ts timestamp YES

tblDrillingMethod 1 Code varchar NO

tblDrillingMethod 2 Description varchar YES

tblDrillingMethod 3 msrepl_synctran_ts timestamp NO

tblHelp 1 HelpIndex bigint NO 19 0

tblHelp 2 ScreenCode varchar NO

tblHelp 3 HelpText varchar YES

tblHole 4 HoleID int NO 10 0

tblHole 5 DrillID int YES 10 0

tblHole 6 HoleTop real YES 24

tblHole 7 HoleBottom real YES 24

tblHole 8 HoleDiameter real YES 24

tblHole 9 upsize_ts timestamp YES

tblLicenseAdministration 1 PhoneNumber nvarchar YES

tblLicenseAdministration 2 EmailAddress varchar YES

tblLicenseAdministration 3 LicenseCost smallmoney YES 10 4

tblLicenseAdministration 4 RigPermitCost smallmoney YES 10 4

tblLicenseAdministration 5 TempLicenseInterval smallint YES 5 0





numeric scale

datetime precision

tblLicenseAdministration 6 DateDeleted smalldatetime

YES 3

tblLicenseAdministration 7 ContactPerson varchar YES

tblLicenseApplication 1 ApplicationID int NO 10 0

tblLicenseApplication 2 DrillerID int NO 10 0

tblLicenseApplication 3 LicenseYear int NO 10 0

tblLicenseApplication 4 ApplicationDate smalldatetime

NO 3

tblLicenseApplication 5 PaymentID int YES 10 0

tblLicenseApplication 6 PaymentAmount smallmoney YES 10 4

tblLicenseApplication 7 LicenseSent smalldatetime

YES 3

tblLicenseApplication 8 EnteredBy varchar YES

tblLicenseApplication 9 msrepl_synctran_ts timestamp NO

tblLicenseComment 1 CommentID int NO 10 0

tblLicenseComment 2 DrillerID int NO 10 0

tblLicenseComment 3 Comment varchar YES

tblLicenseComment 4 CommentDate smalldatetime

YES 3

tblLicenseComment 5 Commentor varchar YES

tblLicenseComment 6 msrepl_synctran_ts timestamp NO

tblLicenseCompletionReport 1 ReportID int NO 10 0

tblLicenseCompletionReport 2 DrillerID int NO 10 0

tblLicenseCompletionReport 3 ReportsSubmitted int YES 10 0

tblLicenseCompletionReport 4 ReportsReturned int YES 10 0

tblLicenseCompletionReport 5 DateReceived datetime YES 3

tblLicenseCompletionReport 6 LicenseYear int YES 10 0

tblLicenseCompletionReport 7 Notes text YES

tblLicenseCompletionReport 8 ReportType int YES 10 0

tblLicenseCompletionReport 9 msrepl_synctran_ts timestamp NO

tblLicenseContact 1 ContactID int NO 10 0

tblLicenseContact 2 DrillerID int NO 10 0

tblLicenseContact 3 FirstName varchar NO

tblLicenseContact 4 MI char YES





numeric scale

datetime precision

tblLicenseContact 5 LastName varchar NO

tblLicenseContact 6 Phone char YES

tblLicenseContact 7 Email varchar YES

tblLicenseContact 8 msrepl_synctran_ts timestamp NO

tblLicenseDeposit 1 DepositID int NO 10 0

tblLicenseDeposit 2 DepositDate datetime YES 3

tblLicenseDeposit 3 ProcessedBy varchar YES

tblLicenseDeposit 4 msrepl_synctran_ts timestamp NO

tblLicenseOfficeHeld 1 OfficeHeldID int NO 10 0

tblLicenseOfficeHeld 2 OfficerID int YES 10 0

tblLicenseOfficeHeld 3 OfficeID int YES 10 0

tblLicenseOfficeHeld 4 OtherDescription varchar YES

tblLicenseOfficeHeld 5 msrepl_synctran_ts timestamp NO

tblLicenseOfficer 1 OfficerID int NO 10 0

tblLicenseOfficer 2 DrillerID int NO 10 0

tblLicenseOfficer 3 FirstName varchar YES

tblLicenseOfficer 4 MI char YES

tblLicenseOfficer 5 LastName varchar YES

tblLicenseOfficer 6 msrepl_synctran_ts timestamp NO

tblLicensePayment 1 PaymentID int NO 10 0

tblLicensePayment 2 PayerDrillerID int NO 10 0

tblLicensePayment 3 PaymentAmount money YES 19 4

tblLicensePayment 4 PaymentType int YES 10 0

tblLicensePayment 5 AuthorizationCode varchar YES

tblLicensePayment 6 PaymentDate smalldatetime

YES 3

tblLicensePayment 7 PaymentYear smallint YES 5 0

tblLicensePayment 8 Note varchar YES

tblLicensePayment 9 DepositID int YES 10 0

tblLicensePayment 10 msrepl_synctran_ts timestamp NO

tblLicenseRig 1 RigID int NO 10 0

tblLicenseRig 2 DrillerID int NO 10 0

tblLicenseRig 3 RigType int YES 10 0





numeric scale

datetime precision

tblLicenseRig 4 ManufacturerID int YES 10 0

tblLicenseRig 5 Manufacturer varchar YES

tblLicenseRig 6 Model varchar YES

tblLicenseRig 7 SerialNumber varchar YES

tblLicenseRig 8 EngineSerialNumber varchar YES

tblLicenseRig 9 VehiclePlateNumber varchar YES

tblLicenseRig 10 State char YES

tblLicenseRig 11 Active bit YES

tblLicenseRig 12 LicenseNumber char YES

tblLicenseRig 13 SequenceNumber int YES 10 0

tblLicenseRig 14 PlateNotRequired bit YES

tblLicenseRig 15 OriginDate smalldatetime

YES 3

tblLicenseRig 16 msrepl_synctran_ts timestamp NO

tblLicenseRigPermit 1 RigID int NO 10 0

tblLicenseRigPermit 2 PermitYear smallint NO 5 0

tblLicenseRigPermit 3 DrillerID int NO 10 0

tblLicenseRigPermit 4 PaymentID int NO 10 0

tblLicenseRigPermit 5 PaymentAmount smallmoney YES 10 4

tblLicenseRigPermit 6 SequenceNumber tinyint YES 3 0

tblLicenseRigPermit 7 PermitSent smalldatetime

YES 3

tblLicenseRigPermit 8 msrepl_synctran_ts timestamp NO

tblLicenseService 1 DrillerID int NO 10 0

tblLicenseService 2 ServiceID int NO 10 0

tblLicenseService 3 msrepl_synctran_ts timestamp NO

tblLicenseSignature 1 ApplicationID int NO 10 0

tblLicenseSignature 2 OfficeID int NO 10 0

tblLicenseSignature 3 FirstName varchar NO

tblLicenseSignature 4 MI char YES

tblLicenseSignature 5 LastName varchar NO

tblLicenseSignature 6 OtherDescription varchar YES

tblLicenseSignature 7 Signed bit NO





numeric scale

datetime precision

tblLicenseSignature 8 SignatureID int NO 10 0

tblLicenseSignature 9 msrepl_synctran_ts timestamp NO

tblLicenseStatus 1 DrillerID int NO 10 0

tblLicenseStatus 2 EffectiveYear smallint NO 5 0

tblLicenseStatus 3 Code int NO 10 0

tblLicenseStatus 4 Comment varchar YES

tblLicenseStatus 5 EnteredBy varchar YES

tblLicenseStatus 6 EnterDate smalldatetime

YES 3

tblLicenseStatus 7 msrepl_synctran_ts timestamp NO

tblLicenseTempAppList 1 TempID int NO 10 0

tblLicenseTempAppList 2 PayerID int NO 10 0

tblLicenseTempAppList 3 DrillerID int NO 10 0

tblLicenseTempAppList 4 AppDate smalldatetime

NO 3

tblLicenseTempAppList 5 msrepl_synctran_ts timestamp NO

tblLicenseTypeBusiness 1 TypeID int NO 10 0

tblLicenseTypeBusiness 2 Description varchar NO

tblLicenseTypeBusiness 3 msrepl_synctran_ts timestamp NO

tblLicenseTypeCreditCard 1 TypeID int NO 10 0

tblLicenseTypeCreditCard 2 Description varchar YES

tblLicenseTypeCreditCard 3 msrepl_synctran_ts timestamp NO

tblLicenseTypeManufacturer 1 TypeID int NO 10 0

tblLicenseTypeManufacturer 2 Description varchar NO

tblLicenseTypeManufacturer 3 msrepl_synctran_ts timestamp NO

tblLicenseTypeOfficer 1 TypeID int NO 10 0

tblLicenseTypeOfficer 2 Description varchar YES

tblLicenseTypeOfficer 3 BusinessTypeID int YES 10 0

tblLicenseTypeOfficer 4 msrepl_synctran_ts timestamp NO

tblLicenseTypePayment 1 TypeID int NO 10 0

tblLicenseTypePayment 2 Description varchar YES

tblLicenseTypePayment 3 msrepl_synctran_ts timestamp NO

tblLicenseTypeRig 1 TypeID int NO 10 0





numeric scale

datetime precision

tblLicenseTypeRig 2 Description varchar NO

tblLicenseTypeRig 3 msrepl_synctran_ts timestamp NO

tblLicenseTypeService 1 ServiceID int NO 10 0

tblLicenseTypeService 2 Description varchar NO

tblLicenseTypeService 3 msrepl_synctran_ts timestamp NO

tblLicenseTypeStatus 1 TypeID int NO 10 0

tblLicenseTypeStatus 2 Description varchar NO

tblLicenseTypeStatus 3 msrepl_synctran_ts timestamp NO

tblLicenseTypeWell 1 Code char NO

tblLicenseTypeWell 2 Description varchar YES

tblLicenseTypeWell 3 msrepl_synctran_ts timestamp NO

tblLicenseWellReport 1 ReportType char NO

tblLicenseWellReport 2 DrillerID int NO 10 0

tblLicenseWellReport 3 DrillYear smallint NO 5 0

tblLicenseWellReport 4 WellsReported smallint YES 5 0

tblLicenseWellReport 5 msrepl_synctran_ts timestamp NO

tblLiner 1 LinerID int NO 10 0

tblLiner 2 DrillID int YES 10 0

tblLiner 3 LinerTop real YES 24

tblLiner 4 LinerBottom real YES 24

tblLiner 5 LinerDiameter real YES 24

tblLiner 6 PVCLinerType int YES 10 0

tblLiner 7 upsize_ts timestamp YES

tblListTable 1 TableName varchar NO

tblListTable 2 Description varchar NO

tblListTable 3 TableUse char YES

tblListTable 4 msrepl_synctran_ts timestamp NO

tblMunicipality 1 Code varchar NO

tblMunicipality 2 Name varchar YES

tblMunicipality 3 Type varchar YES

tblMunicipality 4 County varchar YES

tblMunicipality 5 msrepl_synctran_ts timestamp NO

tblMunicipality 6 MunicipalityNumber varchar YES





numeric scale

datetime precision

tblMunicipality 7 LongitudeMin float YES 53

tblMunicipality 8 LongitudeMax float YES 53

tblMunicipality 9 LatitudeMin float YES 53

tblMunicipality 10 LatitudeMax float YES 53

tblMunicipalityORA 1 OBJECTID decimal NO 38 0

tblMunicipalityORA 2 COUNTY varchar YES

tblMunicipalityORA 3 MUNICIPAL_ varchar YES

tblMunicipalityORA 4 MUNICIPAL1 varchar YES

tblMunicipalityORA 5 FIPS_MUN_C varchar YES

tblMunicipalityORA 6 FED_AID_UR varchar YES

tblMunicipalityORA 7 FIPS_COUNT varchar YES

tblMunicipalityORA 8 FIPS_AREA_ varchar YES

tblMunicipalityORA 9 FIPS_NAME varchar YES

tblMunicipalityORA 10 FIPS_SQ_MI decimal YES 23 5

tblMunicipalityORA 11 FIPS_MUN_P decimal YES 11 0

tblMunicipalityORA 12 FED_ID_NUM varchar YES

tblMunicipalityORA 13 CLASS_OF_M varchar YES

tblMunicipalityORA 14 SHAPE decimal YES 38 0

tblOpening 1 OpeningID int NO 10 0

tblOpening 2 DrillID int YES 10 0

tblOpening 3 OpeningTop real YES 24

tblOpening 4 OpeningBottom real YES 24

tblOpening 5 OpeningYield real YES 24

tblOpening 6 OpeningDiameter real YES 24

tblOpening 7 SlotSize real YES 24

tblOpening 8 Type varchar YES

tblOpening 9 Material varchar YES

tblOpening 10 Packing varchar YES

tblOpening 11 upsize_ts timestamp YES

tblOpeningMaterial 1 Code varchar NO

tblOpeningMaterial 2 Description varchar YES

tblOpeningMaterial 3 msrepl_synctran_ts timestamp NO

tblOpeningType 1 Code varchar NO





numeric scale

datetime precision

tblOpeningType 2 Description varchar YES

tblOpeningType 3 msrepl_synctran_ts timestamp NO

tblOrderNumber 1 OrderNumberID int YES 10 0

tblPacker 1 PackerID int NO 10 0

tblPacker 2 DrillID int YES 10 0

tblPacker 3 PackerTop real YES 24

tblPacker 4 PackerBottom real YES 24

tblPacker 5 Sealant bit YES

tblPacker 6 upsize_ts timestamp YES

tblPacking 1 Code varchar NO

tblPacking 2 Description varchar YES

tblPacking 3 msrepl_synctran_ts timestamp NO

tblPostalBoundaryORA 1 ZIP varchar YES

tblPostalBoundaryORA 2 PO_NAME varchar YES

tblPostalBoundaryORA 3 STATE varchar YES

tblPostalBoundaryORA 4 COUNTY varchar YES

tblPostalBoundaryORA 5 ST_FIPS varchar YES

tblPostalBoundaryORA 6 CTY_FIPS varchar YES

tblPostalBoundaryORA 7 FID decimal NO 38 0

tblPostalBoundaryORA 8 SHAPE decimal YES 38 0

tblPVCLinerType 1 Code int NO 10 0

tblPVCLinerType 2 Description varchar YES

tblPVCLinerType 3 msrepl_synctran_ts timestamp NO

tblQuadCountyXRef 1 QuadCode smallint YES 5 0

tblQuadCountyXRef 2 CountyCode varchar YES

tblQuadCountyXRef 3 QuadName varchar YES

tblQuadCountyXRef 4 XrefID int NO 10 0

tblQuadCountyXRef 5 msrepl_synctran_ts timestamp NO

tblQuadrangle 1 DERCode smallint NO 5 0

tblQuadrangle 2 QuadName varchar YES

tblQuadrangle 3 UTMZone smallint YES 5 0

tblQuadrangle 4 msrepl_synctran_ts timestamp NO

tblQuadrangle 5 LongitudeMin float YES 53





numeric scale

datetime precision

tblQuadrangle 6 LongitudeMax float YES 53

tblQuadrangle 7 LatitudeMin float YES 53

tblQuadrangle 8 LatitudeMax float YES 53

tblSealType 1 Code varchar NO

tblSealType 2 Description varchar YES

tblSealType 3 msrepl_synctran_ts timestamp NO

tblWaterUse 1 Code varchar NO

tblWaterUse 2 Description varchar YES

tblWaterUse 3 msrepl_synctran_ts timestamp NO

tblWell 1 WellID int NO 10 0

tblWell 2 County varchar YES

tblWell 3 Municipality varchar YES

tblWell 4 Quadrangle smallint YES 5 0

tblWell 5 UTMNorthing int YES 10 0

tblWell 6 UTMEasting int YES 10 0

tblWell 7 Latitude float YES 53

tblWell 8 Longitude float YES 53

tblWell 9 CoordMethod int YES 10 0

tblWell 10 upsize_ts timestamp YES

tblWell 11 LatitudeDD float YES 53

tblWell 12 LongitudeDD float YES 53

tblWellError 1 ErrorCode int NO 10 0

tblWellError 2 DrillID int NO 10 0

tblWellError 3 msrepl_synctran_ts timestamp NO

tblWellErrorList 1 WellErrorID int NO 10 0

tblWellErrorList 2 Description varchar NO

tblWellErrorList 3 TableName varchar YES

tblWellErrorList 4 DataBaseName varchar YES

tblWellErrorList 5 DataBaseType varchar YES

tblWellErrorList 6 DataBasePath varchar YES

tblWellErrorList 7 msrepl_synctran_ts timestamp NO

tblWellFinish 1 Code varchar NO

tblWellFinish 2 Description varchar YES





numeric scale

datetime precision

tblWellFinish 3 msrepl_synctran_ts timestamp NO

tblWellUse 1 Code varchar NO

tblWellUse 2 Description varchar YES

tblWellUse 3 msrepl_synctran_ts timestamp NO

tblWhatsNew 1 ItemID int NO 10 0

tblWhatsNew 2 EffectiveDate datetime YES 3

tblWhatsNew 3 AppliesTo varchar YES

tblWhatsNew 4 Description varchar YES

tblWhatsNew 5 msrepl_synctran_ts timestamp NO

tblWhatsNew 6 CreatedDate datetime YES 3

tblYieldMethod 1 Code varchar NO

tblYieldMethod 2 Description varchar YES

tblYieldMethod 3 msrepl_synctran_ts timestamp NO

well data gap analysis project - pa - emarketplace well data gap analysis project gap analysis...

Documents