Attachment_1_-_Contractor_Questions_3.pdf
PDF 140 KB Posted
- Attached to
- Geological Interpretive Tools (GIT) Technology
- Solicitation number
- DOIMFBO240003
About this file
This document contains questions from the government to potential contractors regarding the draft Request for Proposal (RFP) for the Geological Interpretive Tools (GIT) Technology procurement. The questions cover technical requirements such as software capabilities, data management solutions, and integration with other systems. The document also includes acquisition-related questions about subcontracting and the proposal preparation and evaluation process. The purpose of this market research is to gather information from industry to help refine the requirements for the upcoming RFP. The related federal contract opportunity is a pre-solicitation for the GIT Technology requirement, to be issued by the Department of the Interior Bureau of Ocean Energy Management.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Pre-Solicitation_Notice_3.pdf | ||
| Attachement_2_-_Draft_Solicitation_3.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
ATTACHMENT 1 - QUESTIONS FOR CONTRACTORS REGARDING THE DRAFT
RFP AND BOEM’S GIT TECHNOLOGY REQUIREMENTS
For Market Research Purposes Only:
Technical Questions:
1. What license configuration do you allow for users to perform the workflows described in the RFP?
2. What levels of customer Service Level Agreements (SLA) do you provide? Please provide a copy of your SLA.
3. How have you performed a transition from a client’s current GIT solution to your proposed solution? List software environments and software that you have assisted migrating from, provide examples of migration plans and estimate of how long migration may take, the amount of support you provide(d), and the exact tools required to facilitate or ease the transition from the current environment to the new environment.
4. How are work projects stored and shared? Are these flat files on a shared drive? Is there an external database in the background? If so, describe the database and relationship types within the database.
5. Is the software able to accept fluid/gas contacts and allow for both 2-D (map based) and 3-D (geocellular grid based) volume calculations?
6. Is the software able to be able to create geocellular 3-D volume grids/models and allow for continuous data population (well data and/or facies models) in order to model reservoir properties (perm, Bo, porosity, water saturation, and N/G)?
7. Does the software allow for mapping of faults and integration of faults into geocellular models? Once integrated into the geomodel, are faults able to be delineated as sealing or leaking faults?
8. Is the software able to create flow simulation grids/models that can be exported for use with external reservoir (oil, gas, carbon dioxide) simulation software?
9. Does the software allow for both deterministic and stochastic modeling?
10. Does the software have the ability to perform multi mineral solver analysis?
11. Is the software able to perform Geomechanical workflows for a 1D model that allow for the creation of a Mechanical Earth Model?
12. Can the software perform borehole image analysis for facies analysis, dip analysis and fracture analysis?
13. Is the software able to utilize both python scripts and machine learning to be utilized in petrophysical workflows to generate supporting log curves?
14. Does the software have the ability to generate and edit zonation’s in a graphical and tabular view? Is the software able to generate multi well workflow evaluations, cross-sections, and plots?
15. Is the software able to incorporate various other well data types including mudlogs, MDT, core analysis, NMR, etc...?
16. Can software perform Thin Bed analysis with the Thomas Steiber method or some other methods?
17. Can the software perform depth shifting, filtering and data smoothing?
18. Does your data management solution connect directly to your proposed software and perform direct data transfers into projects?
19. Is your data management solution integrated within a Fed-Ramped DOI Cloud-compliant environment?
20. Is your data management solution able to manage petabytes of data?
21. Does your data management solution manage boreholes, directionals, checkshots, well logs, seismic, velocity surveys, pointsets, polygons, raster images, shapefiles, interpretation, and binary and ascii formatted data types?
22. Is the data management solution MFA compliant?
23. Can your data management solution be integrated with an ESRI Portal?
24. Does your data solution follow Oil and Gas Industry standards for data management?
25. Can a single data management tool be used to import, delete, review, and edit data?
Acquisition-Related Questions
26. Can any of the work included in this IDIQ be subcontracted? If so, what type of work can be subcontracted? If not, an explanation would help the Government determine if a subcontracting plan is required.
27. Are the RFP proposal preparation instructions in Section 4 and proposal evaluation criteria in Section 5, clear and understandable?
28. The purpose of the down-selection process is to save contractors some proposal preparation costs if BOEM does not anticipate that the proposed GIT solutions will meet BOEMs needs. Do you see value in this down-selection approach?
File details come from the government source that posted it. Updated .