Background:

The DCNR Bureau of Information Technology Services (BITS) was interested in upgrading and re-writing the oil and gas Well Information System. It was written in 1994-1995 and was state-of-the-art at the time, but is now out dated. At the same time, BITS was performing maintenance work on the WebDriller application, and saw that while the business needs for the two applications differed, a few similarities existed as well between the two systems. Also a few years ago, the Bureau of Topographic and Geologic Survey (TopoGeo) was interested in creating a central repository for the stratigraphic data. Both of the wells systems collect and maintain stratigraphic data, so a decision was made to look at how all these system might work together. A Gap Analysis was conducted, and that Gap Analysis is included within this RFQ. This repository is being built to accommodate all stratigraphic data collected by the bureau, and the wells data

TopoGeo has two offices. (1) Their central office is located in Middletown, PA. The director and operational support is housed at this location. The knowledge experts concerning the water systems are also housed at this location. (2) The Petroleum and Subsurface Geology Section is located in the Pittsburgh Office. This is the primary knowledge base for the oil and gas systems. BITSis located in the DCNR central office (the Rachel Carson State Office Building) in Harrisburg, PA.

To date, managing these various types of wells has been handled in disparate systems with no overlap of information. While all the functions shown in the current systems are still relevant, they do not represent how we wish to do business in the future. In other words, DCNR does not want to lose functionality, but is very interested in improving efficiency - better technology, better information flow, better reuse of data, etc. DCNR BITS is looking for far better data normalization, which will allow for better reporting and make it easier to mine and share these data.

This RFQ does not scope out a solution, only the current conditions of our systems. We are looking for proposing vendors to look at the functions of these systems and the skills sets within DCNR and propose a new approach that is supportable by in-house staff. The only caveat DCNR has concerning the solution is the consolidation and conformance to a new methodology in maintaining stratigraphic data. This concept was provided pictorially with the following diagram:

2

(Uniform Records Reporting System?) (External Users Looking for Any Well Record Spatially)

External Users

(External Users Looking for Oil & Gas Records and Associated Data (both scan and digital formats))

(Enterprise Interactive Map) (External Users Looking for Groundwater Records) (External Users Submitting for Drilling License)

(PaGWIS)

(PA*IRIS and WIS Data) (WebDriller)

Internal Users

(PaGWIS) (PA*IRIS and WIS)

Oil & Gas Specific Data

(TopoGeo Bureau-Wide Stratigraphic Data)

Water Specific Data

Overlapping Data Elements (Company, Location, Casing, product, etc.)

Stratigraphic Data

NOTES: At end of effort, there will still be unique access points for business specific users. If within budget, create a uniform reporting entry for wells in general as well. Also, the PA*IRIS/WIS interface will require a more efficient design. WebDriller keep familiar to minimize re-training. It is recommended that entry forms for overlapping data be consistent between internal systems. Leverage Stratigraphic Design in areas covered by that RFQ. Leverage the RockIT methodology for areas outside of that RFQ (such as groundwater).

At the completion of this effort, DCNR is to see streamlined technologies employed for a cohesive wells system. The successful vendor is to look at the existing systems and see where efficiencies of scale can be realized, leveraging current industry technologies for multiple uses. Even the incorporation of the Stratigraphic database is to be done in a way that the end users only know they are working with a Wells system. While the user will see changes, such as now looking at O&G geologic data in a three dimensional perspective, overall functionality is to remain familiar to the user. Keep interfaces as clean and simple as feasible. To clarify this is to be a complete re-vamp, not simply an upgrade. Rather, the finished product is to accommodate the functions of the past, incorporate new business needs for todays geologic needs, and do so leveraging new approaches for information management.

Questions and Answers

RFQ #DCNR-38-11-04, Wells Information System

1. Did any vendor help DCNR in the preparation of the RFQ? If Yes, is the vendor allowed to bid on the RFQ?

ANSWER: The DCNR made a determination that it would be beneficial for the five systems covered under this RFQ to be consolidated. To verify the areas of overall and conflicts, BITS contracted with a vendor to inventory the data sets in play, and some of the higher-level business processes. This study was completed a year and a half ago. The gaps and overlaps that were uncovered during that study have been incorporated into this RFQ. However, no vendor aided in the preparation of the RFQ.

2. What is the work location for the project?

ANSWER: For requirements and UI design, vendor will be at Middletown for the water, will be in Pittsburgh for the oil and gas wells portion. Architecture and build will be at the Harrisburg location. Test will be as appropriate.

3. Will travel be required to the Pittsburgh office location?

ANSWER: See question 2.

4. Can you please explain the following sentence on Page 35 Last paragraph? 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).

ANSWER: As the regulatory agency, DEP handles the review and approval of oil and gas permits, and none of this paperwork is forwarded to DCNR. However, once DEP has issued a valid permit and a location plat is received for that permit by DEP, DEP forwards a copy of the plat and all subsequent well-related paperwork to DCNR for inclusion in PA*IRIS/WIS.

5. After an oil/gas well has been drilled, the operator is required to complete a well completion report. Is the report submitted to DCNR and then forwarded to DEP for approval or is it submitted to DEP?

ANSWER: As the regulatory agency, DEP is the agency that receives ALL paperwork related to oil and gas well permits; it then reviews and approves such documentation as needed. Copies of such paperwork is forwarded to DCNR for inclusion in PA*IRIS/WIS and never the other way around.

6. What is the timeline for the project?

ANSWER: As noted in the RFQ, we estimated for the effort to take around 18 months.

7. Is the payment based on the deliverables identified in section IV-4 of the RFQ?

ANSWER: Yes. Refer to format of Cost Matrix.

8. Who will be responsible for the cleanup of the data in the existing systems prior to data conversion? Referring Page 89 of the RFQ.

ANSWER: The vendor would be responsible for data mapping, ETL processes, clarifying best practices and recommendations for data cleanup actual clean-up would be conducted by DCNR resources.

9. Does DCNR currently use any credential management system?

ANSWER: No we do not. We only leverage active directory.

10. Has DCNR determined to implement all of the recommendations from the Gap analysis or some of them? If only some have been selected, please identify the ones selected?

ANSWER: The RFQ identifies the areas of the Gap Analysis that DCNR determined are to be implemented.

11. Did a vendor complete the Gap Analysis? Is the vendor with in depth knowledge of WIS allowed to bid on this RFQ?

ANSWER: Note question 1 Yes, a vendor conducted the Gap Analysis, and the analyst that performed that study is no longer with the company. Because no decisions were made via that Gap Analysis, that vendor is entitled to bid. Also remember, DCNR is not simply interested in an up-to-date WIS application, but rather in a new way of doing business. DCNR provided the functional areas of WIS which contain the business functions we wish to maintain within the RFQ. DCNR will be looking for vendor who understands this area of business and who can bring to the table an efficient solution for this area of business.

12. Which RDBMS should be used for the final system Oracle or SQL Server?

ANSWER: Oracle 11G or later.

13. Has DCNR documented all the requirements for the unified system?

ANSWER: The Gap analysis provided the As Is, but did not go into the To Be. The Requirements will need to be determined a part of this effort.

14. Please provide a breakdown of the number of users of each of the five systems to be transitioned broken out by whether they are employees or citizens. We are seeking to understand how many users will be accessing the new integrated system.

ANSWER: This is somewhat difficult for obvious reasons, but we would estimate that for external, several hundred users access the system daily. There are around 100 users of the internal systems.

15. Can you please confirm that 11 users require training and 3 technical staff require technical training and knowledge transfer for the new system? (This is referenced on RFP page 96 Section 6. D Phase 4). Will other users require training?

ANSWER: Yes, those numbers are correct for the users. However, we would modify the technical training to include 1 developer, 1 dba, and 4 system support (& he