Requirements to M7 - System approval

This page describes the requirements for approval of systems to be used by the Market parties against Elhub as part of the M7 milestone. The attached document below lists all test cases that are part of the total scope for approval. Each System vendor must define which test cases that are relevant for them and that will be their specific scope for approval.
Status per system must be reported using the Test log. As soon as a system is approved, the “System approved (godkjent)” column in the “Aktørstatus (Market party status)” on Elhub.no.will be set to green.
All Market parties must have their systems approved before they can perform Market party approval (Aktørgodkjenning).

Date for M7 is 22.December 2017.

Known bugs and limitations to certain BRS’es are describe below.

Acceptance criterias:

  • All relevant test cases set to green in internal verification are executed minimum 1 time either in Systest3 or Exatest2
  • If requested, defined test cases are retested by the System vendor due to major changes in Elhub
  • All messages described in the test case are processed correctly
  • There are no open critical defects

BRS’es in scope for M7:

Description of test cases:

Calculations test

Calculations test for systems supporting the role Grid owner will be agreed separatly.
For Balance supplier/Balance responsible roles we have created a MGA where we are running calculations in Systest3. Elhub is set as Grid owner and are sending in metering values on a regular basis.
To test reception of PPC/FPC as well as imbalance settlement results, you as Balance Suppliers (and Balance Responsible Parties) must join this MGA by sending in a Move in back in time (BRS-NO-103) in a defined Metering point. We will provide you with a list of MPID’s to use.
Later on you will also receive aggregated values in BRS-NO-503 when this functionality is implemented in Elhub.

Please contact us, and we will provide you with MPIDs so you can perform a Move in back in time and thereafter start receiving meter values.

You will find description of the Calculations test and test cases here.

Known bugs and limitations.

BRS-NO-315:

If a BRS-NO-315 is called for a period (e.g. 01.03.2017-14.06.2017) and there is a period volume that ends on the requested end date (e.g. 01.04.2017-14.06.2017). Then the period volume ending on the requested end date will not be returned.
This is happening due to that the emeter interface that is returning period volumes from EIP is not retrieving period volumes where the end date is the same as the requested end date. We expect that this should be returned as the other emeter interfaces are end date inclusive.

Work around:
The requesting market party should request a period that is one day longer. I.e. instead of retrieving 01.04.2017-14.06.2017, use 01.04.2017-15.06.2017. This will retrieve the period volume ending on the 14.06.2017. Note that this will not work if the market party do not have access to see data on the 15.06.2017, e.g. the market party is a third party and the move out/in was made on the 14.06.2017 and thus his contract was ended on the 14.06.2017. Note that this should only be a problem with third parties and balance suppliers.
Note that this is only the case with period volumes. Interval volumes are not affected by the current bug.

BRS-NO-321 and BRS-NO-502:

• No messages received for D+3 and D+4
• No messages received for SLR (at all)

Business types that are green, meaning that there are no issues detected yet:
• SE02 – Sum infeed per MGA
• SE06 – Sum pumped consumption per MGA
• SE12 – Sum consumption for Balance Supplier for profiled metering points per MGA (Pumped consumption types excluded)
• SE13 – Sum consumption for Balance Supplier for non-profiled metering points per MGA (Pumped consumption types excluded)
• SE15 – Sum pumped consumption per Balance Supplier per MGA
• SE16 – Sum pumped storage consumption per Balance Supplier per MGA
• SE19 – MGA exchange in
• SE20 – MGA exchange out
• SE23 – Sum production per MGA
• LS01 – Grid loss

Business types with issues found, although some are erroneous only for certain scenarios:
• SE04 – Sum exchange
• SE05 – Sum supply of last resort consumption per MGA
• SE07 – Adjusted Load Profile per MGA
• SE08 – Sum consumption for Balance Responsible Party per MGA (Pumped consumption types excluded)
• SE09 – Sum production for Balance Responsible Party per MGA
• SE10 – Sum consumption for Balance Supplier per MGA (Pumped consumption types excluded)
• SE11 – Sum production for Balance Supplier per MGA
• SE14 – Sum pumped storage consumption per MGA
• SE17 – Sum pumped consumption per Balance Responsible Party per MGA
• SE18 – Sum pumped storage consumption per Balance Responsible Party per MGA
• SE21 – Sum consumption for Balance Responsible Party for profiled metering points per MGA (Pumped consumption types excluded)
• SE22 – Sum consumption for Balance Responsible Party for non-profiled metering points per MGA (Pumped consumption types excluded)
• SE24 – Sum consumption for non-profiled metering points per MGA (Pumped consumption types excluded)