9.5 Use Case 5: Data Storage

Topic Version1Published12/09/2016
For StandardPRODML v2.0

Data storage (Figure 9.5-1) addresses the storage, search, and retrieval of information in systems of record for the lifecycle of the fluid sample data (i.e., from acquisition to utilization to disposal).

Figure 9.5-1 Data storage use case.

This use case is specifically intended to support the requirements from laboratories and operators for loading, searching, and exporting fluid analysis and characterization datasets from systems of records, such as in corporate databases.

The two general requirements for the data storage use case are:

  • Accurate capture and organization of data to meet the needs of future workflows
  • Preservation of context for data items that are used in multiple workflows.

These requirements significantly influenced the structure and behavior of the data objects that make up this standard—such as the separation of the fluid sample from distinct sample acquisition and laboratory analysis objects—so that implementers of the standard are not burdened with the need to “make up” data not otherwise available. For example, the distinction between fluid analysis data and fluid characterization data more clearly defines the difference between measured and calculated data while better supporting the description of user-defined data because it can be handled without having to fake “laboratory tests”.

Another product of these requirements was the assignment of identifiers within each data object and allowing all data objects to reference other data objects by these identifiers. For example, this enables the data in the sample acquisition data object to remain connected to the fluid samples it produces and vice versa. These schemas are also designed to incorporate the operator’s system of record’s identification (e.g., completion, well, or facility identifiers) within the initially created data objects, which are then carried forward through the workflow, making it easier to load them into a system of record.

Because of the expanded scope of these specifications over earlier ones (Aydelotte et al. 2003), the scope of the corporate repositories needing to store these datasets may need to be expanded. Specifically, additional tables for sample acquisition, laboratory analysis tests, and fluid characterization may be needed unless these data are de-normalized into existing tables, which could potentially limit the system’s ability to export the original data. Also, a capability to managing the document attachments (field notes and laboratory reports, etc.) may be required. Definition of the scope or details of these potential changes are beyond the scope of any transfer standard and are the province of the owner of the relevant databases