ALL Consulting
[ RBDMS Home ] [ HelpDesk ] [ TechFacts ] [ Custom Services ] [ Toolbox ] [ State Updates ]

 
 

This area of the site includes information regarding the status of RBDMS is a select number of users.  This is NOT a complete list.

Alaska Oil & Gas Conservation Commission
Alabama Department of Natural Resources
California Division of Oil, Gas, and Geothermal Resources
Colorado Oil & Gas Conservation Commission
Florida Geological Survey
Kansas Corporation Commission
Michigan Department of Environmental Quality
Mississippi State Oil & Gas
Montana Board of Oil & Gas Conservation
Nebraska Oil & Gas Conservation Commission
New Mexico Oil Conservation Division
New York Division of Mineral Resources
Ohio Department of Natural Resources
Oklahoma Department of Environmental Quality
United States Environmental Protection Agency
Texas Railroad Commission
Osage Indian Tribe
Indiana Department of Natural Resources
Kentucky Division of Oil & Gas
Pennsylvania Bureau of Oil & Gas Management
Other Miscellaneous 

 

Alaska Oil & Gas Conservation Commission (AOGCC): ALL is currently assisting the AOGCC migrate from existing systems to a Access2000 version of RBDMS.  The alpha version of Alaska's custom RBDMS program was initiated through a compilation of RBDMS custom objects from various RBDMS implementations, including Montana, Michigan, Arkansas, Nebraska, and Oklahoma.  This compilation effort is a demonstration of the effectiveness that can be reached from leveraging efforts among state agencies!

Arkansas Oil & Gas Commission (AOGC): The AOGC is currently implementing a new Client/Server custom version of RBDMS as well as several other integrated software components/tools. This includes a Data Entry System (DES), various GIS systems that utilize Sylvan Ascent's SylvanMaps and ESRI's ArcView and ArcExplorer, a Production Forecasting and Economic Evaluation Tool (PFEET), and others.

Arkansas Department of Environmental Quality (ADEQ):  The ADEQ has initiated a custom installation of RBDMS. To achieve the ADEQ's functional requirements, the RBDMS development team will leverage off previous development work performed for the Oklahoma Department of Environmental Quality (ODEQ). One key consideration in ADEQ's implementation effort will be data sharing between the ADEQ and AOGC. Implementation will include custom development to meet functional requirements, incorporation of select ODEQ custom RBDMS components, setup and installation of RBDMS, training, and other general assistance tasks.

Alabama Oil & Gas Board (AOGB): The GWPC recently provided funding to assist the AOGB migrate data from four (4) existing data systems into the 32-bit general version of RBDMS. The data migration process including migrating approximately 600,000 oil & gas production records, several hundred Class II injection well related records, over 10,000 well and well completion records, as well as other information. The AOGB is currently in the process of evaluating the RBDMS program and delineating customization issues that need to be addressed for full implementation of the RBDMS program.

California Department of Oil, Gas, and Geothermal Resources (CDOGGR): The CDOGGR pursued implementation of RBDMS as part of their original AOR grant from the DOE's NPTO. This initial pursuit resulted in a focused data entry effort by BDM Oklahoma using the 16-bit version of RBDMS. The CDOGGR has since pursued an alternate development effort that aligns more closely with their in-house resources. The CDOGGR's decision to pursue an alternative to RBDMS was partially related to decreases in their AOR grant from DOE.

Although the CDOGGR has pursued an alternative approach to the standard implementation of RBDMS, they have utilized the RBDMS data model in the development of their own custom software. Therefore, it is important to recognize that the RBDMS project has indirectly provided benefits even though it appears that the CDOGGR will develop a stand-alone system.

Colorado Oil & Gas Conservation Commission (COGCC): The COGCC has undertaken a significant oil & gas information system development effort. They have decided that due to their distinct needs that a internally developed custom system is required to best meet their unique functional requirements.

Florida Geological Survey (FGS): ALL-LLC staff and the GWPC have assisted the FGS pursue Primacy over their Class II Underground Injection Control (UIC) program.  The program is currently being implemented directly by the EPA in Region IV.  As part of this effort, data for all oil & gas producing wells and related Class II injection wells were loaded onto RBDMS.   FGS is in the beginning stages of implementing RBDMS.

 

Indiana Department of Natural Resources (IDNR): The IDNR has been implementing a internally developed system in MS Access. 

Kansas Corporation Commission (KCC): The KCC is perhaps the largest installation of RBDMS being implemented by a state oil & gas regulatory agency. The KCC currently maintains approximately 335,000 records in RBDMS. This includes records for approximately 30,000 injection wells, 5,000 pits/ponds, and approximately 300,000 other wells that may include producers, abandoned wells, plugged wells, and orphan wells. The KCC's system is also deployed in a Client/Server platform using MS Access97 as a client to MS SQL Server.

The current data set was merged from more than a dozen different legacy databases. The subject legacy systems incorporated a wide variety of formats, varied in data quality, and generally did not include unique well identifiers. As a result, a significant effort was undertaken by the RBDMS project team in data translation, conversion, merging, and migration. One significant result of this process has been the fact that KCC staff have now been provided the first opportunity ever to analyze the combined dataset for all of the known wells in Kansas - which had previously not been possible.

In addition to data merging, a significant effort was undertaken with regard to system performance and optimization. The large number of wells residing on the KCC system required that significant queries could be performed in short period of times. One benchmark that was performed during testing was to filter the total dataset down to approximately 10,000 select records. Using approximately 20 approaches, system data querying was accomplished in timeframes of between 15 to 20 seconds (i.e., querying 335,000 well records to get a resultant dataset of 10,000 well records). This performance demonstrates the ability of the RBDMS program to handle very large datasets.

Project implementation in Kansas also included, but is not limited to, the following:
 
Zone of Endangering Influence (ZOEI): The KCC had a need to evaluate injection well projects using multiple "What If" scenarios. To address this need, the project team modified CH2M HILL's ZOEI program to fit the needs of the KCC. The program was written in Visual Basic 5.0 and distributed to the KCC for use in evaluating Class II UIC permits;
Area of Review Variance (AorVarQ): To address AOR Variance issues, a custom program was developed in Visual Basic 5.0 to assist in evaluating AOR Variances in the state;
RBDMS Procedural Manual: One of the priorities of the KCC was to provide written procedures for performing select workflow tasks. Therefore, a procedural analysis and subsequent manual was prepared. To effectively distribute the manual it was published to the RBDMS web site and, therefore, made available to all RBDMS users.
Custom Data Entry Forms: Several custom data entry forms were developed for the KCC to provide meet specific functional requirements of the Conservation Division. Some of the custom data entry forms that were developed include a UIC entry form, annual monitoring data entry, docket and hearing tracking systems, pits/ponds tracking system, and other custom data entry forms.

Kentucky Division of Oil & Gas (KDOG): The KDOG has obtained and are evaluating the 32-bit general version of RBDMS currently.

Michigan Department of Environmental Quality (MDEQ)

Mississippi State Oil & Gas Board (MSOGB): The MSOGB participated in the initial development of the RBDMS program. Activities undertaken by the state over the last year have included importing a total of approximately 27,000 well records into their 16-bit version of RBDMS. In addition, a number of custom data entry forms were prepared for the MSOGB, including a injection well monitoring data entry form (specific to Mississippi), well permitting system, and a new module to track submittals pertaining to NORM reporting.

Montana Board of Oil & Gas Conservation (MBOGC): The MBOGC participated in the initial design and development of the RBDMS program. The MBOGC has general 32-bit version of RBDMS was beta tested by both the MBOGC and Kansas Corporation Commission (KCC). The general 32-bit version of RBDMS has been under active implementation by the MBOGC since mid-1997. The MBOGC's data set includes the following data records (approximately):

 
nearly 1,000,000 oil & gas production records;
35,000 well and well completion records;
9,000 Mechanical Integrity Test Records;
10,000 well inspection records;
1,500 UIC permit and AOR tracking records;
12,000 core and sample records;
70,000 well history records;
over 100,000 formation tops; and
a variety of other data types.

The MBOGC is somewhat unique as a great deal of the UIC related information in the current installation of RBDMS was provided by the U.S. Environmental Protection Agency in Region VIII (EPA). Data was provided by EPA as part of the Class II UIC program transition from EPA to the MBOGC. The combination of data sources from both existing state agency systems and the EPA's system has demonstrated the utility and direct benefits of a combined data management system compared to maintaining multiple unrelated data systems.

Also during the last year, the MBOGC has participated in the development of a project with the New Mexico Petroleum Recovery Research Center (NMPRRC) and the GWPC in an effort to investigate the feasibility of providing an Internet Interface to the RBDMS program. The NMPRRC and MBOGC decided to pursue this effort as a team approach based on the distinct similarities in how data is collected and utilized (especially oil & gas production related data and information).

The MBOGC uses RBDMS for a number of agency activities, including (but not limited to) the following:
 

Scheduling field activities such as well and incident inspections, ownership transfer inspections, field compliance and enforcement activities, mechanical integrity testing, on-site confirmation of well construction and plugging, and other field activities;

Tracking of Class II UIC permits, including wells on each permit (i.e., both individual and area permits), AOR data and statistics for each AOR evaluation; and permit histories for subject wells;
Tracking of UIC technical activities, including Area of Reviews, Mechanical Integrity Tests, Permit File Reviews, drilling and completion details, borehole geophysical logs information, etc.;
Tracking of all wells in the state, including the tracking of data such as general well information, well surface and bottom hole location data; drilling and completion information, core/sample data, log data, well histories, lease and unit information, well permit information, well type/status details, etc.
Oil & gas production information, tracked on a by-well and distinct producing horizon basis. Including the ability to analyze data numerically and graphically. Data from RBDMS is also used to prepare the MBOGC's annual report;
Reference information on all operators in the state, including contacts; and
Subsurface geology related information on geologic formations, oil & gas fields and related field rules, pool and reservoir information in the state, production test information for wells in the state, core/sample data for wells in the state.

The MBOGC has also performed a good deal of personal customization to the system which it has shared with other state regulatory agencies, mostly involving reports generated by RBDMS.

Nebraska Oil & Gas Conservation Commission (NOGCC): The NOGCC participated in the initial design and development of the original RBDMS program. The NOGCC implemented the 16-bit version of RBDMS for its Class II UIC program and is now in the process of migrating both UIC and production data to the general 32-bit version of RBDMS.

Of significance to the NOGCC is the fact that the current implementation effort includes a custom production module developed to meet the NOGCC's specific needs. This new production module allows the tracking of detailed information for leases and units that report production in the state. It also provides for tracking of oil & gas production in accordance with NOGCC's specific requirements (i.e., monthly production reported by lease/unit).

Data migration programs were developed by the RBDMS project support team to facilitate the migration of historical oil & gas production records from an existing WANG system to RBDMS. The actual data migration process is being performed by NOGCC staff with minor assistance from the RBDMS project support team.

New Mexico Oil Conservation Division (NMOCD): The NMOCD has been working with RBDMS for some time. The have chosen to continue implementation of the 16-bit version of RBDMS because deployment of the 32-bit version of RBDMS did not coincide with their timing limitation for project funding. The NMOCD performed a good deal of customization to the 16-bit version of RBDMS, including adding the ability to allow remote data reporting of field activities. The RBDMS project team provided technical support services to the customization and implementation effort. Development and modifications of the program were generally performed by NMOCD staff.

New Mexico Petroleum Recovery Research Center (NMPRRC): The NMPRRC met with representatives of the RBDMS project team and DOE's NPTO office in Tulsa, Oklahoma in 1997. Following that meeting, the research center obtained a copy of the 32-bit general version of RBDMS for evaluation and testing. The NMPRRC currently serves as the data archive to the NMOCD's ONGARD system. As such, they require a comprehensive system to store petroleum information incoming from the NMOCD as well as other sources. 

Ohio Department of Natural Resources (ODNR): The ODNR was among the first two (2) states to implement a 32-bit version of RBDMS. Further, ODNR was the first state to pursue a development effort coordinated by both the state's oil & gas regulatory group and the state's geological survey. This combined development effort provided significant benefits to the RBDMS project and capabilities of the RBDMS program. Some of the specific improvement developed and deployed as a result of the ODNR's development effort are listed below:
 
A well permit application system was developed from scratch. This new component of RBDMS was developed to meet the specific needs of the Division of Oil & Gas (DOG) and tracks fees, application information, proposed well location and completion information, and incorporates the ability to automatically generate a new API well number. In addition, this new component includes the ability to automatically generate well permits in accordance with specific requirements. Incorporated in the process where permits are generated is the automatic preparation of well completion forms and well plugging forms to be completed by owners;
A detailed location system was added to the RBDMS suite to address the 13+ land-grid systems present in Ohio. This was perhaps one of the most challenging aspects of the project due to the variation in individual land-grid systems, including more than 3 types of section-township-range systems;
Expanded field activity tracking systems: existing field activity tracking components from the original 16-bit version of RBDMS were expanded to include information on spills, site reclamation, and violation tracking in accordance with Ohio State Statutes and Rules;
To address the state's Division of Geological Survey's (DGS's) needs, a "Well Card" module was also developed for the ODNR. This new component was designed to facilitate data entry of well data not currently in electronic form. Data sources will include well and core cards maintained at the state's geologic library. The Well Card component allows data to be entered from a single data entry form into approximately 15 database tables within the RBDMS program (a relational and normalized database). As part of this effort, a new method of handling the entry of formation tops recorded for wells was also developed. An alternate method was required due to the fact that many formation tops submitted by industry (especially on older wells) do not conform to current standards. Therefore, a method to allow either a standard formation name or a non-standard formation name was developed and deployed;
In an effort to benefit industry, a geologic stratigraphy component was developed. This component was desired due to the volume of requests pertaining to localized stratigraphy by the DGS. This component allows DGS staff to record local stratigraphy throughout the state and make that information available to industry representatives upon request;
The RBDMS geologic formations module was expanded to better address the functional requirements of both the DOG and DGS. Additional formation codes were added as well as alias formation names. Furthermore, image files used by the DGS's GIS efforts were incorporated into the system to allow dynamic mapping using the appropriate symbology;
A basic well stimulation component was designed and developed to track information on well stimulations and treatments performed on wells in the state;
The RBDMS borehole geophysical log module was modified to incorporate the needs of the DGS. This customization included modifying the 16-bit version of RBDMS to allow more detailed tracking of borehole geophysical log information;
The RBDMS bonds module was modified to coordinate more closely with the related functional requirements of the DOG. A new "Bond Holds" component was added to allow the state to track those operators that had a hold placed on a particular bond. The "bond holds" concept allow the state to preclude the issuance of permits to permittees;
Approximately 20 new reports were developed for the ODNR as part of the RBDMS implementation effort in Ohio. These reports included a utility to generate letters to send to injection well operators, well permits, statistical and tracking reports, as well as others;

The following new RBDMS components were designed and developed by ODNR staff following the contracted RBDMS implementation project:
 
The DOG developed a production accounting module to handle production data reported to the state in-house. The DOG requires the submission of oil & gas production data on an annual basis. DOG decided to develop this component in-house because the existing RBDMS production module did not fit Ohio's data model for production. Further, the state's database administrator for the RBDMS program gained significant knowledge about the RBDMS program during the main implementation effort, thus providing that person with the skills to develop and deploy addition components without the need to contract further services through the GWPC;
The DOG expanded the RBDMS compliance module to fit their particular needs;
Of particular interest is the fact that the DOG developed a utility that allows industry users of RBDMS to maintain an up-to-date dataset. In Ohio's instance, they publish weekly data updates to their FTP server. Industry users can then download that data and append it to existing data electronically. This utility will likely also be used by the ODNR to maintain updated dataset in the state's regional offices;
In addition to development of program components, the ODNR took the lead in migrating data from their existing legacy systems into RBDMS.

The ODNR has a very comprehensive set of data now included in the their version 32-bit custom version of RBDMS. This includes approximately 100,000 well records, 200,000 permit application records, and a wide variety of other additional data and information.

Oklahoma Department of Environmental Quality (ODEQ): ODEQ has been using RBDMS since September 1996 for tracking Class I, III, and V type injection wells. Custom components of the ODEQ 32-bit version of RBDMS include a graphical data analysis module, Class I inspection module, injection well monitoring data reports, and a data transfer system. The ODEQ is currently considering migrating from MS Access95 to MS Access97. ODEQ is the first state to use RBDMS for tracking Class I, III, and V type well activities.

Osage Indian Tribe: The Osage Indians implement some aspects of the Class II UIC program in Osage County, Oklahoma. Further, the tribe works closely with the Bureau of Indian Affairs and EPA for various oil & gas and environmental activities. The tribe is currently considering and evaluating the possibility of using RBDMS to maintain data and information specific to both injectors and producers in Osage County.

Pennsylvania Bureau of Oil & Gas Management (PBOGM): In 1997, the RBDMS project team visited the PBOGM to discuss possible implementation of RBDMS in Pennsylvania. Initial evaluation of RBDMS by the PBOGM was very positive. However, the PBOGM was already involved with a information system development effort for their entire agency. The ongoing develop for the "FIX" program is planned to address all of the environmental programs regulated by the state at the cost of several million dollars. This broad ongoing effort did not easily provide for the integration of another information system. Therefore, the PBOGM has decided to forego further consideration of RBDMS at the current time. 

Texas Railroad Commission (RRC): The RRC has been active in developing information systems for themselves for some time. Recently, the GWPC has been discussing options whereby the RRC could use some parts of the RBDMS program to compliment existing systems they implement.

U.S. Environmental Protection Agency: Several EPA regional offices are in the process of evaluating the RBDMS program. Both Region VIII and IV have downloaded the system. Detailed discussions have been held with Region IV, but a specific determination has yet to be finalized by EPA.

Others: There are certainly other states and industry groups evaluating RBDMS. The summary above is limited to those agencies expressing the greatest interest in RBDMS or having the greatest activity over the last year.