Composite processes

Processes with interdependencies have been unified into composite processes in the Datahub system. Composite processes allow us to create predefined entities in which all processes in a process chain must be executed to complete the chain. Controlled lead times can also be assigned to composite processes. Individual processes related to composite processes may also be events reported only by a specific reason code. The processes in the composite processes always have a connecting factor, the same accounting point ID, agreement ID or customer ID and/or associated message ID.

An example of a composite process is the creation of a new sales agreement when a customer is moving in, and the confirmation of the related grid agreement. When a supplier reports a new sales agreement to Datahub, Datahub determines the reason code for this new agreement. If it is a move-in, Datahub creates an open transaction for the DSO awaiting the confirmation of the grid agreement. When Datahub has received the confirmation, the open transaction can be closed. The time limit for confirming the grid agreement is set to a minimum of two working days from the receipt of the information about the new grid agreement. This open transaction can be seen in the DSO’s information. Two working days is set as the lead time of this composite process. The Datahub operator can monitor the DSOs’ response to these within the set time limits. There is a specific view in the Datahub UI for these open transactions.

Some events can only be sent to Datahub as part of composite processes. For example, the confirmation of a grid agreement is always a part of this kind of process chain. It can only be reported when the supplier has first reported a new sales agreement. Based on this a new grid agreement is needed, and a new open transaction for the DSO is created.

Composite processes in Datahub are listed in the table below. The process in brackets is a conditional part of the composite process. For example, DH-312 follows DH-311 only when a new grid agreement is required for the accounting point.

Composite process	Name	Initiating party	Continuing party	Processes	Description

Composite process	Name	Initiating party	Continuing party	Processes	Description
DH-112 → DH-111	Customer information update request	DSO	Supplier	DH-112 + DH-111	The update request is forwarded to the supplier.
DH-113 → DH-11	Customer information update request	Third party	Supplier	DH-113 + DH-111	The update request is forwarded to the supplier.
DH-113 → DH-112	Customer information update request	Third party	DSO	DH-113 + DH-112	The update request is forwarded to the DSO, if the customer does not have a valid sales agreement.
DH-113 → DH-112 → DH-111	Customer information update request	Third party	DSO/Supplier	DH-113 + DH-112 + DH-111	The update request is forwarded to the DSO, if the customer does not have a valid sales agreement. The DSO’s update is forwarded to the supplier as an update request if a sales agreement has been reported for the customer before the DSO’s update.
DH-124 → DH-122	Accounting point data update request	Supplier/Third party	DSO	DH-124 + DH-122	The update request is always forwarded to the DSO.
DH-311 → DH-312	Supplier starts sales agreement process	Supplier	DSO	DH-311 + (DH-312)	If a new grid agreement is required by the sales agreement, the DSO should confirm the grid agreement.
DH-331 → DH-333	Supplier terminates sales agreement	Supplier	DSO	DH-331 + (DH-333)	If the supplier ends the sales agreement with reason move-out, the grid agreement needs to be terminated as well. If a separate termination is reported for a sales agreement that was terminated due to a new agreement, a separate termination must also be reported for the corresponding grid agreement that was terminated due to a new agreement. If the grid agreement corresponding to the sales agreement is unconfirmed, the DSO is notified about the termination, but a composite process is not formed. In this case, the DSO must first confirm the grid agreement, after which the DSO can report the termination of the grid agreement as a separate event.
DH-333 → DH-331	DSO terminates grid agreement	DSO	Supplier	DH-333 + DH-331	When the grid agreement is terminated, the supplier needs to end the sales agreement accordingly. If a separate termination is reported for a grid agreement that was terminated due to a new agreement, a separate termination must also be reported for the corresponding sales agreement that was terminated due to a new agreement.
DH-341 → DH-342	Supplier cancels sales agreement	Supplier	DSO	DH-341 + (DH-342)	The DSO should cancel the grid agreement that corresponds to the cancelled sales agreement. If the cancellation is reported with reason code ‘Cancellation due to a supplier related reason’, the grid agreement is not cancelled, and no composite process is formed. If the grid agreement corresponding to the sales agreement is unconfirmed, the DSO is notified about the cancellation, but Datahub cancels the grid agreement automatically, and no composite process is formed. If the cancellation is reported with reason code ‘Cancellation due to a supplier related reason’, the possible unconfirmed grid agreement is not cancelled, and no composite process is formed.
DH-341 → DH-343	Refusal of sales agreement restoration	Supplier	(Edeltävä) Supplier	DH-341 + (DH-343)	Refusal of sales agreement restoration is possible only if the cancelled sales agreement caused a previous sales agreement to be restored.
DH-342 → DH-341	DSO cancels grid agreement	DSO	Supplier	DH-342 + (DH-341)	The supplier should cancel the sales agreement if the corresponding grid agreement is cancelled.
DH-351 → DH-352	Supplier cancels sales agreement termination	Supplier	DSO	DH-351 + (DH-352)	If a sales agreement is terminated with reason move-out and this termination is then cancelled, the corresponding grid agreement termination must also be cancelled, if the DSO has already ended the grid agreement.
DH-411 → DH-412	Supply connection request	Supplier	DSO	DH-411 + (DH-413) + DH-412	The supply connection request is forwarded to the DSO. The DSO’s notification of connection delay (DH-413) is optional.
DH-421 → DH-422	Supply disconnection request	Supplier	DSO	DH-421 + (DH-423) + DH-422	The supply disconnection request is forwarded to the DSO. The DSO’s notification of connection delay (DH-423) is optional.
DH-711 → DH-713	Creating a product	Supplier	Supplier	DH-711 + (DH-713)	A composite process is formed if a price is reported for the product (not a price time series).
DH-712 → DH-714	Creating a product	DSO	DSO	DH-712 + (DH-714)	A composite process is formed if a price is reported for the product (not a price time series).