Idd part 1 Interfaces with bsc parties and their Agents




старонка68/82
Дата канвертавання24.04.2016
Памер4.34 Mb.
1   ...   64   65   66   67   68   69   70   71   ...   82

7.3 ECVAA-I003: (input) MVRNAA Data


Interface ID:

ECVAA-I003



User:

MVRNA, BSC Party



Title:

MVRNAA Data



BSC reference:

ECVAA SD: 7.1, 7.6, 7.7, A

ECVAA BPM: 3.2, 4.6, 4.10, 4.12

RETA SCH: 4, B, 3.4

CR 005, CP547, P110, CP888, P98


Mechanism:

Manual, by letter or fax, or can be sent as an electronic data file over the network



Frequency:

Ad hoc


Volumes:

Low

The ECVAA Service shall receive the following MVRNAA data on an ad hoc basis.
i. MVRNAA requests. Each request shall be submitted separately by the BM Unit Lead Party, BM Unit Subsidiary Party and either one or two MVRNAs, each providing identical details as shown below along with their individual password/signature.

ii. MVRNAA Termination requests. Each termination request shall be submitted by the BM Unit Lead Party, BM Unit Subsidiary Party or a MVRNA of the relevant MVRNAA.

iii. MVRNAA Key Change requests. Each request shall be submitted by a MVRNA for the relevant MVRNAA.

iv. MVRNAA Report Requirement Change requests. Each request shall be submitted by a MVRNA or BSC Party for the relevant MVRNAA.




The MVRNAA data shall comprise:


MVRNAA Requests:

MVRNA ID


MVRNA Name

BM Unit ID

Lead Party ID

Lead Party Name

Lead Party production/consumption flag

MVRNA ID 2 (optional)

MVRNA Name 2 (optional)

Subsidiary Party ID

Subsidiary Party Name

Subsidiary Party production/consumption flag

Effective From Date

Effective To Date

Report Requirements (optional - specific to submitter)


MVR Termination Requests:

MVRNAA ID

MVRNA ID

BM Unit ID

Lead Party ID

MVRNA ID 2 (optional)

Subsidiary Party ID

Associated VNNR Indicator


MVRNAA Key Change Requests (specific to submitter):

MVRNAA ID

MVRNA ID

BM Unit ID

Lead Party ID

MVRNA ID 2 (optional)

Subsidiary Party ID
MVRNAA Report Requirement Change Requests (specific to submitter):

MVRNAA ID

MVRNA ID

BM Unit ID

Lead Party ID

MVRNA ID 2 (optional)

Subsidiary Party ID

Report Requirement


Notes:

  • The MVRNAA Key is not included in the key change request since this is a manual interface. However standard authentication checks will ensure that the party submitting the request is the MVRNA for the relevant MVRNAA.

  • The Associated VNNR Indicator is used to inform the ECVAA that this MVRNAA Termination Request should be processed prior to processing the corresponding Volume Notification Nullification Request.

  • The Report Requirement will allow the following report variants to be selected for a given BSC Party or MVRNA and MVRNAA:

  • Receive AFR (with accepted data groups only) and RFR

  • Receive AFR (with accepted and matched data groups) and RFR

  • Receive no AFR and no RFR

Physical Interface Details: Physical flow details are defined for this manual interface because the registrant can send this information as an electronic data file over the network; the ECVAA operator enters the information via a screen-based interface however it is sent..


7.4 ECVAA-I004: (input) ECVN


Interface ID:

ECVAA-I004



User:

ECVNA


Title:

ECVNs


BSC reference:

ECVAA SD: 8.1, A

ECVAA BPM: 3.3, 4.18

RETA SCH: 4, B, 3.4

CR 008, CP527, P98


Mechanism:

Electronic Data File Transfer



Frequency:

Continuous



Volumes:

High


Interface Requirement:

i. The ECVAA Service shall receive the following ECVNs from ECVNAs continuously for every Settlement Period up until Gate Closure.


Note that ECVN Withdrawal is implemented by sending a notification containing a null ECV.


The ECVNs shall comprise:


Energy Contract Volume Notification:

ECVNA ID


ECVNAA ID

ECVNAA Key

ECVN ECVNAA ID

ECVN Reference Code

Effective From Date

Effective To Date (optional)

Settlement Period (1-50)

Energy Contract Volume (MWh) (volume sold by party 1 to party 2, may be negative))

Omitted Data: No Change (optional)9



Physical Interface Details:
The ECVNA Id is the From Participant Id in the AAA header record of the physical file and so is not included in the EDN record.

The ECVN ECVNAA Id should always be either

a) the ECVNAA Id of the Agent submitting the new/overwrite ECVN, or

b) an ECVNAA Id that has now expired (i.e. effective to date < todays date) but was for the same pair of trading Party Energy Accounts (specified in the same order in each ECVNAA);

An ECVN that does not follow these rules should be rejected in full.


See section 7.24 for more details.

1   ...   64   65   66   67   68   69   70   71   ...   82


База данных защищена авторским правом ©shkola.of.by 2016
звярнуцца да адміністрацыі

    Галоўная старонка