Elhub messages per process component

The business processes are described in separate Business Requirements Specifications (BRS) documents for market and metering value processes. Each process is described by a sequence diagram, in addition to a textual description, showing the parties involved in the process, the messages involved and the sequence of the messages.
Example:
The first message in the sequence diagram below regarding Change of Supplier is number 1 – Start of Supply.

The table below shows the "mapping" between the process components defined in the diagrams above and the Elhub messages used. Note that the same Elhub messages may be used by several process components.
The messages written with grey font color are acknowledgement (positive or negative) messages returned to the sender of the first message mapped to the process component. Ref. the sequence diagrams in chapter 5 below for a detailed description of the message flow between Elhub and the market parties for each process component.

Process comp.	Version	Name	Elhub Message
1	2.0	Start of supply – from Balance Supplier	1 – RequestStartOfSupply 2 – ConfirmStartOfSupply 3 – RejectStartOfSupply
2	2.0	Start of supply – to Balance Supplier	1 – RequestStartOfSupply
3	2.0	Update of masterdata – from Balance Supplier	24 – RequestUpdateCustomerInformation 37 – Acknowledgement
4	2.0	Meter reading – from Balance Supplier	14 – CollectedData 37 – Acknowledgement
5	2.0	Query – from Market parties	19 – RequestDataFromElhub 37 – Acknowledgement
6	2.0	Update of master data – to Balance Supplier - Grid Access Provider - Third Party	4- NotifyStartOfSupply 9 – NotifyMeteringPointCharacteristics 27 – NotifyCustomerInformation
7	2.0	Metering Values – to Market parties	20 – NotifyValidatedDataForBillingEnergy
8	2.0	Settlement – to Market parties	20 – NotifyValidatedDataForBillingEnergy
9	2.0	Reconciliation – to Balance Supplier	30 – PriceVolumeCombinationForReconcilation
10	2.0	End of supply – from Balance Supplier	5 – RequestEndOfSupply 6 – ConfirmEndOfSupply 7 – RejectEndOfSupply
11	2.0	End of supply – to Balance Supplier	8 – NotifyEndOfSupply
13	2.0	Start in metering point – from Grid Access Provider	1 – RequestStartOfSupply 2 – ConfirmStartOfSupply 3 – RejectStartOfSupply
14	2.0	Start in metering point – to Grid Access Provider	4 – NotifyStartOfSupply
15	2.0	Update of masterdata – from Grid Access Provider	21 - RequestUpdateMasterDataMeteringPoint 37 – Acknowledgement
16	2.0	Metering Values – from Metered Data Collector	14 – CollectedData 37 – Acknowledgement
19	2.0	Meter index_Estimated yearly consumption from Balance Supplier - to Metered Data Responsible and Grid Acces Provider	14 – CollectedData 37 – Acknowledgement
21	2.0	Reconcilation – to Grid Access Provider	30 – PriceVolumeCombinationForReconcilation
22	2.0	End in metering point – from Grid Access Provider	5 – RequestEndOfSupply 6 – ConfirmEndOfSupply 7 – RejectEndOfSupply
23	2.0	End in metering point – to Grid Access Provider	8 – NotifyEndOfSupply
24		Not in use
25	2.0	Request to Grid Access provider - from Balance Supplier	11 – RequestToGridAccessProvider 37 – Acknowledgement
26	2.0	Request to Grid Access Provider	11 – RequestToGridAccessProvider
27	2.0	Feedback from Grid Access Provider	12 – ResponseFromGridAccessProvider
28	2.0	Feedback from Grid Access Provider - to Balance Supplier	12 – ResponseFromGridAccessProvider
29		Not in use
30		Not in use
31	2.0	Verify Masterdata Metering Point from Balance Supplier	16 – RequestUpfrontMeteringPointCharacteristics 17 – ResponseUpfrontMeteringPointCharacteristics
32	2.0	Reminder to Metered Data Responsible / Grid Access Provider	13 – RequestCollectedData
34	2.0	Update of Third Party access	34 – UpdateThirdPartyAccess 37 – Acknowledgement
35	2.0	Report structure data to Settlement responsible	Message must be defined and specified by the NBS project
36	2.0	Report settlement basis per MGA to Balance Settlement Responsible	Message: 2.2 ebIX AggregatedData per MGA in NBS User Guide 1r2A
37	2.0	Report settlement basis per neighboring grid to Balance Settlement Responsible	Message: 2.3 ebIX AggregatedData per Neighboring Grid for Settlement Responsible in NBS User Guide 1r2A
38	2.0	Report prodused volume to NECS	Message is defined by the vendor of NECS, Grexel.
39	2.0	Report consumption to NECS	Message is defined by the vendor of NECS, Grexel.