5.5 Transfer and Tanker Lifting
Topic Version | 1 | Published | 12/09/2016 | |
For Standard | PRODML v2.0 |
Volumes associate with transfers and tanker liftings can be transferred as part of the Simple Product Volume capability. Again, both these types of transfer are designed to be transferred upon events happening, rather than periodically as for asset production volumes. For this reason, they are available as standalone objects (see Figure 5.1-2 , purple box). However, unlike the production well test object and the well production parameters objects, they can also be transferred embedded within an asset production volumes data object. The reason for this is an operator may wish to do an end-of-period (typically end-of-month) report showing all production and all dispositions of production, including all transfers and tanker liftings. When used within asset production volumes in this way, transfers and tanker liftings are to be identified as specific types of disposition.
The transfer object and tanker lifting object both use the same data object reference described above (and shown in Figure 5.1-2 ). However, they differ in that they refer to multiple reporting entities.
Transfer: 2 Reporting Entities:
- source facility
- destination facility
Tanker Lifting: 3 Reporting Entities:
- loading terminal
- destination terminal
- tanker
For facility and terminal entities, the reporting entity should be some kind of facility. For oil tanker and tanker trucks, the reporting entity is expected to be tanker. As noted above, the behavior of reporting entities and kind is not enforced by the schema, so it needs to be validated by the software (that the data objects are implemented in).
Both the Transfer object and Tanker Lifting object use the same reference to fluid components in a fluid component catalog as does the Asset Production Volumes (described in Section 5.3.1 Fluid Component Catalog ). Each instance of transfer and tanker lifting has its own fluid component catalog so that it can behave as a standalone data object. However, where they are used within Asset Production Volumes (see above), then they share the fluid component catalog of the parent asset production volumes.