B10_RFQ_Solicitation_Q&A_FBO.pdf

RFQ Solicitation # 140M0118Q0032 Questions and Answers

1. Is there a requirement for log data for RFQ Solicitation No. 140M0118Q0032

This is not a requirement of the RFQ.

2. Does the offeror need to develop separate applications for O&G Well and Production data services? (OR) they can be built part of the same web application?

The RFQ doesn’t specify separate or combined applications, this is left to the discretion of the offeror.

3. Does the offeror need to build services to access data from the cloud? Or the services exist and sufficient to access the required well data and production data attributes.

BOEM is seeking a service that provides user access only to a cloud-based oil and gas well data and production database service for State of Alaska and OCS Alaska areas that is already established, not developed.

4. Does the software application being developed need to integrate and work with the

Petrel E&P software? If Yes, what is the scope of integration work to be done?

This is not a requirement of the RFQ.

5. Are we addressing only the Current datasets of Oil and Gas or Historic datasets also needs be addressed as part of this project? We assume Historic datasets need further research.

See Section 2.3.1.

6. Are the Mapping capabilities limited to Production data only?

The extent of mapping capabilities are not specified by the RFQ and is left to the discretion of the offeror.

7. Does information that is available in Alaska (http://doa.alaska.gov) website as scanned documents need to be converted to digital data along with the available information in digital/HTML?

8. Should the Web interface be able to load the future digital data directly into database and need to integrate with existing Geological, Geophysical and Engineering Software applications?

This is not a requirement of the RFQ.

9. Do we need to manually convert ALL scanned copies existing data into Digital format?

Or only specific datasets as mentioned in Statement of work?

This is not a requirement of the RFQ.

10. What is the data model standard that needs to be followed? Is that a standard one or customized based on the present requirements?

This is not a requirement of the RFQ.

11. There could be possible gaps in the available information which may need further research / Analysis from the existing data. Is data analysis required on the stated attributes or required AS IS values from existing scanned copies?

The RFQ doesn’t address how the offeror will handle missing or incomplete well history and production data from their data sources. This is decision left to the discretion of the offeror.

12. We assume that converting the scanned log image to digital file is not part of the scope.

Do we have to index the available digital log file to the captured record? Please confirm.

This is not a requirement of the RFQ.

13. Do we need to index all of the scanned images to the records?

This is not a requirement of the RFQ.

14. What data is referred to part of digital data for AOCS wells? We understand well attribute data and historical data.

See Section 2.3.1 and 2.3.2.

15. What data model does the Alaska OG historical data exists in? Does it support PPDM or does it have a proprietary data model?

This is not a requirement of the RFQ.

16. Does Alaska OG have GIS data that can be used to provide mapping capabilities? If yes, is it compatible with ESRI/shape files or it exists in a different format? Does the offeror need to analyze seismic data while providing GIS mapping capabilities?

17. Does the offeror need to build GIS data (part of building mapping capabilities) using software like ESRI?

This is not a requirement of the RFQ.

18. Does the dynamic query building require a Textual or Visual interface?

The RFQ does not specify a textual or visual interface. The type of query is left to the discretion of offeror.

19. The background statement alludes to multiple data formats, web applications, and sources used for accessing and synthesizing well and production data. In addition to the

AOGCC public datasets, please list all datasets and sources that BOEM would like to have incorporated into their solution.

The RFQ doesn’t specify datasets and sources incorporated into this application. This decision is left to the discretion of the offeror.

20. Has AOSCR RE documented best practices for collecting and synthesizing the AOGCC data for use in desktop applications? If so, can this documentation be provided at award?

This is not a requirement of the RFQ.

21. To confirm, BOEM is looking to have this solution hosted in the cloud and does not want an on premise solution?

See Section 2.3.1 and 2.3.2.

22. What, if any, GIS infrastructure or platforms are preferred for BOEM users? E.g. ESRI, QGIS.

This is not a requirement of the RFQ.

23. What way, if any, does the BOEM wish to integrate their existing GIS infrastructure into the proposed solution? For example, does BOEM wish to consume or update data services in desktop GIS applications or just through the web application?

24. Does BOEM users have ESRI ArcGIS Online (AGOL) organizational and/or user accounts?

25. Confirm that the web application solution must comply with Section 508 accessibility standards?

See section 3.9 of the RFQ.

26. Does this “history” extend beyond the source data provided by AOGCC? Please clarify this statement with a more defined objective, are any interpretations of the data history required outside of the source data?

See answer to question 19.

27. How is the app to present this history? For example: time aware features can be visualized through the use of a time slider contral. Reports can generated using date range queries.

The RFQ doesn’t specify how to present this well history. This decision is left to the discretion of the offeror.

28. Is there a preference for how historical data should be handled during the update process… zipped to a location for downloads, pushed to a historic table, archived internally etc?

This is not a requirement of the RFQ.

29. Upon review of the AOGCC data extracts, it appears that 69 wells lack latitude and longitude coordinate values, to comply with the DOI Scientific Integrity Policy, what is the BOEM policy for incomplete source data (e.g. wells missing coordinate and footage information are either ignored, position interpolated or centered on PLSS centroids)?

See answer to question 11.

30. Upon reviewing the AOGCC data extracts we found these datasets to be incomplete, does BOEM expect the contract to acquire this data using alternative methods or as is?

See answer to question 29.

31. Does BOEM have a schema for their expected data format or is the schema to be developed?

32. Does BOEM expect these data to all be accessible in a web map, REST endpoints, or do they expect some other interface such as a “downloads” page or an interface for the

State of Alaska’s data portal?

The RFQ doesn’t specify how the offeror will provide the required well history data. This decision is left to the discretion of the offeror.

33. Please identify all dataset features that will require an ETL process to create Petrel E&P consumable formats? Are there other applications, such as GIS software that need format conversion support or direct access to REST APIs?

See Section 2.3.1 and 2.3.2.

34. What is the BOEM vision for this requirement (Capability to perform summaries and user-defined calculations on numeric data fields, includes analysis tool for production decline analysis.), purely within a cloud interface or would BOEM users download a spreadsheet to perform these calculations locally? Can BOEM provide a high-level overview of the expected business processes associated to generate these summaries and analysis?

See answer to question 11.

35. This requirement seems unrealistic for a project with this scope (Delivery date is within

10 days of award). Is this a hard requirement or will the BOEM extend flexibility to the successful vendor based on agreed upon schedules presented in the respondents proposal?

The BOEM is seeking a service that provides user access only that is already established, not developed. BOEM has a time critical need for well history data and well production data in support of their mission for ensuring receipt of FMV during federal lease sales and for our ongoing efforts to assess undiscovered oil and gas potential of the Alaskan OCS.