9.1.1 How the Solution Supports this Use Case

Topic Version1Published12/09/2016
For StandardPRODML v2.0

The sample acquisition data object helps to answer questions like these:

  • Which reservoir did this sample flow from?
  • Which conditions was the sample acquired under? Where? When?
  • What method was used to acquire it? Which particular tool was used?
  • How much actual and usable sample volumes were collected?
  • Were multiple samples taken from same location?
  • What are the intended uses of the samples?
  • Who handled the sample? What did they do? When?

This information is needed to assess the sample’s representativeness, its potential for contamination, and its susceptibility for the removal of trace components (e.g., by adsorption onto surfaces of the sampling tool). This information is also needed when designing the laboratory analyses and selecting the best samples for characterization. The ability to describe the physical configuration and conditions of the flow stream being sampled—either at the surface or downhole— was recognized as a very important part of this use case. For this reason, the sample acquisition data object contains specific references to other available data objects, such as WITSML’s Well, Wellbore and Well Completion; and PRODML’s Product Network port, Welltest, and WFT Run, allowing the context of the sampling event to be derived, when available, from their data. Additional context is preserved by enabling field notes and other relevant documents to be referenced from and “bundled” with the sample acquisition data object.