Idd part 1 Interfaces with bsc parties and their Agents




старонка64/82
Дата канвертавання24.04.2016
Памер4.34 Mb.
1   ...   60   61   62   63   64   65   66   67   ...   82

6.7 CRA-I007: (input/output) Boundary Point and System Connection Point Data


Interface ID:

CRA-I007


Source:-
System Operator, Distribution Business

Destination:


BSCCo Ltd

Title:

Boundary Point and System Connection Point Data



BSC reference:

CRA SD 6.4, CRA BPM 3.3, ERM, CRA BPM 4.9, RETA SCH 4,B, 2.4.2, CP615, CP756



Mechanism:

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



Frequency:

As Necessary



Volumes:

Low

The CRA shall receive information concerning the initial registration, decommissioning and changes to registered data for Boundary Points and System Connection Points. The information shall include the following:
Action Description
Authentication Details

Name


Password
Point Details

Boundary Point or System Connection Point Identifier

Boundary Point or System Connection Point Type

Effective From Date

Effective To Date
Where the information concerns a new registration, or the permanent decommissioning of an existing point, then CRA shall forward a copy of the information to BSCCo Ltd. The forwarded copy will include any additional information provided.


Physical Interface Details:

A physical structure is defined for this manual interface because the registrant can send this information as an electronic data file over the network; the CRA operator enters the information via a screen-based interface however it is sent.




6.8 CRA-I008: (input) Interconnector Registration Details


Interface ID:

CRA-I008


Source:

System Operator or Distribution Business



Title:

Interconnector Registration Details



BSC reference:

CRA SD 6.3, CRA BPM 3.5, ERM, CP756



Mechanism:

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



Frequency:

As Necessary



Volumes:

Low


Interface Requirement:

The CRA shall receive new registrations and changes to the registration details of Interconnectors. Changes to the administration of the Interconnector are considered within the requirements of the Interconnector Administrator requirements:


Action Description
Authentication Details

Name


Password
Interconnector Details

Name


Additional Details (including GSP Group Id where appropriate)

Interconnector ID

Effective From Date

Effective To Date




Physical Interface Details:

A physical structure is defined for this manual interface because the registrant can send this information as an electronic data file over the network; the CRA operator enters the information via a screen-based interface however it is sent.




6.9 CRA-I012: (output) CRA Encryption Key


Interface ID:

CRA-I012


User:

BSC Party,

BSC Party Agent, MIDP


Title:

CRA Encryption Key



BSC reference:

CRA SD 4.1.7, P78



Mechanism:

Manual


Frequency:

As necessary



Volumes:

Low

See [COMMS] for details of the encryption key.
The CRA system shall issue a report containing the authentication details for a BSC Party, Market Index Data Provider and other agents where necessary. The Authentication details shall consist of:
Encryption details

CRA public Key

Effective Start Date



Physical Interface Details:


6.10 CRA-I014: (output) Registration Report


Interface ID:

CRA-I014


User:

BSC Party,

BSC Party Agent,

BSC Service Agent,

System Operator,

BSCCo Ltd



Title:

Registration Report



BSC reference:

CRA SD 4, CRA BPM 3.5, CRA BPM 3.1, CRA BPM 4.16, ERM, CP546/CP726, P78, P100, CP962, P215



Mechanism:

Electronic data file transfer

(except Manual to BSC Service Agents and BSCCo Ltd)


Frequency:

As necessary



Volumes:

Low

The CRA system shall issue a report detailing changes and new registration data once it has been input into the CRA system. The report will be issued to the interested parties in the registration:
In most cases, the update only directly affects the registrant (i.e. the participant that submitted the registration request), but in a few particular cases, additional participants must be informed.
The report is issued to the relevant participants according to the following rules, dependent on the entity updated:

1. If the entity is a BSC Party then the report will be issued to that BSC Party;

2. If the entity is a BSC Party Agent then the report is issued to that BSC Party Agent;

3. If the entity is a BSC Service Agent then the report is issued to that BSC Service Agent;

4. If the entity is a BM Unit then the owning BSC Party of that unit is issued with the report;

5. If the entity is a Joint BM Unit Group then all BSC Parties having BM Units in the Group(s) concerned are issued with the report, as well as the owner of the Joint BM Unit Group;

6. If the entity is a Trading Unit then all BSC Parties having BM Units in the Trading Unit concerned are issued with the report, as well as the owner of the Trading Unit;

7. If the entity is a Metering System, the owning BSC Party and the BSC Party Agent appointed as Meter Operator Agent are issued with the report;

8. If the entity is a Boundary Point, then the owning BSC Party of that Boundary Point is issued with the report;

9. If the entity is a GSP Group, GSP or Distribution Systems Connection Point (DSCP) then the owning BSC Party is issued with the report;

10. If the entity is an Interconnector or an Interconnector Administration appointment then all BSC Parties owning Interconnector-usage BM Units on that Interconnector are issued with the report, as well as the Parties acting as Administrator and Error Administrator, and the owner of the Interconnector.

11. If the entity is a Market Index Data Provider then BSCCo Ltd will be issued with the report.


For Market Index Data Provider Registration a full refresh of the MIDP’s current registration details will be sent as a manual flow, back to BSCCo Ltd. This manual flow will include:
Market Index Data Provider ID

Market Index Data Provider Name



Registration Details

Registration Effective From

Registration Effective To

Name


Address

Telephone No

Fax No

e-mail address


For all other Registration types an automatic flow will be generated, which will meet the following requirements:
The interface may be used to either send updated details (received over the course of a day), or a full refresh of all the BSC Party’s current registration details.
The report shall contain the details of the registration along with the success / failure / pending nature and where appropriate, the reasons for failure / pending status.
The report shall contain a header detailing the status of the registration attempt / change, along with the structure and content of the input data flow for which this is a report. The structure of the individual response shall correspond to that contained on the incoming flow (CRA-I0018, CRA-I002, CRA-I003, CRA-I004, CRA-I005, CRA-I006, CRA-I007, CRA-I008, CRA-I027, CRA-I031).
The content of the report corresponding to incoming flow CRA-I005 shall be extended to include the following data items, in addition to the details contained in the incoming flow:

  • CALF (as received in interface CRA-I011)

  • TLF (as received in interface CRA-I029)

  • Exempt Export Flag (as received in interface CRA-I043)

  • Manual Credit Qualifying Flag (as received in interface CRA-I009)

  • Credit Qualifying Status (derived value)

  • BMCAIC (derived value)

  • BMCAEC (derived value)

  • Production / Consumption Status (derived value)

Updates shall be reported in response to incoming flow CRA-I005 or where any of the data items above have changed. A report may also be issued following changes to the composition of a Trading Unit, or changes to any of the component BM Units belonging to a Trading Unit, that result in re-computation of Production / Consumption Status even though that re-computation may derive the same Status as before.


The header details shall contain the following information:
Registration Details

Requesting Registrant,

Registration Type (Party, Party Agent, Service Agent, BM Unit etc.)

Registration Status (success, failure, pending)

Additional Details
The requesting registrant field will normally contain the Id of the registrant; but for the report sent in response to CRA-I003, it will always be the Id of the Party Agent being registered.
The registration status details the result of the registration request. This may be:


  1. Success : The registration request was successful

  2. Failure : The request failed validation and was rejected

  3. Pending : The request relied upon corroborative material and is thus pending the arrival of this information.

Where BSC Parties, BSC Party Agents and BSC Service Agents have registered multiple roles, the report includes a separate registration status for each role.


Followed by the individual registration details, omitting authentication details, but including any additional details (such as identifiers and BM Units automatically assigned).
Each record of the report contains an Action Code, indicating whether the record has a) been added or changed; b) been deleted or c) not changed. When the report is sent as a full refresh, the action code is omitted for each record.
Note that there is no data item “Energy Account ID” since each party has a Production and a Consumption account which are identified by the Party ID and the P/C Indicator.

Physical Interface Details:

In the physical report, Registration Status can only be success or pending. Reporting that a registration has failed is a manual process. Accordingly, the physical report does not contain “Additional Details”.


For the response to CRA-I005, where a BM Unit's Production / Consumption Status changes on a date where no other BM Unit attributes change (for example as a result of another BM Unit being added or removed from the Trading Unit to which the BM Unit belongs), the BM Unit information will be reported as separate date ranges in order to accurately report the changing Status.



1   ...   60   61   62   63   64   65   66   67   ...   82


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

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