Skip to main content

Transfers

The Transfer element type is unique in that it is defined within a time context, and is not related to any specific model, analysis, or case. Since transfers are used to monitor the movement of material from one point to another over a specific time interval, transfers are stored in a dedicated section of the Sigmafine Database and referenced by Sigmafine Cases using the "Collect Transfer" action; in other words, transfers become part, as references, of the Sigmafine Case only after they are collected.

From a system perspective, transfers can be created, modified or deleted regardless of the state of the case that eventually references them. Therefore a transfer, referenced in a case, can be deleted even if the case is locked or checked out by another user. To better understand the potential implications, here are some simple scenarios:

Deleting a transfer referenced by a Case

The transfer can be deleted. The case, regardless of its status (Locked, Checked out), loses the reference, results related to the transfer are marked as 'Unknown', and the case dataset becomes inconsistent as the transfer no longer exists.

Adding a transfer that overlaps a Case

The transfer is added. The case in unaware of the action. Depending on your business process, this may not be a problem, or it could generate inconsistencies in the system as:

  • The locked cases Dataset does not contain the transfer information.
  • Open cases may already have performed the "collect transfer" prior to the transfer creation; a new "collect transfers" should be performed.

Modifying properties of a transfer that overlaps a case

The transfer is modified. The case in unaware of the action. Depending on your business process, this may not be a problem, or it can generate inconsistencies in the system such as:

  • The locked cases Dataset will contain inconsistent information,
  • Open cases may have already performed the "collect transfer" prior to the transfer creation, a new "collect transfer" should be performed.

Modifying transfer attributes in the event-frame data base

Changes to transfer attribute value, although performed in the event-frame data base, may affect all cases referencing the transfer. This happens if the changed attribute contributes to the calculation of one of transfer INPUT attributes. In such a case, the applied change will impact all cases that have already performed a Collect Input. Locked cases will also be affected, as the transfer INPUT attribute has changed.

Note

The Above scenarios are mainly related to manual operative performed through an application such as PI System Explorer, ProcessBook, etc. If you are using Sigmafine products such as IMM, or if your business process is structured to properly handle such situations, you are not impacted.