EACL-PL-04

Balancing Service Provider (BSP) on the Flexibility Platform

1. Description of the Use Case

1.1. Name of the Use Case

IDArea /Domain(s)/Zone(s)Name of the Use Case
1Poland,EACL-PL-04

1.2. Version Management

Version No.DateName of author(s)ChangesApproval status
0.72021-07-26T00:00:00Wojciech Lubczyński and Grzegorz Sawicki (PSE),NoneNone

1.3. Scope and Objectives of Use Case

ScopeIntroduction of BSP, linking it with FSP or FSPA, creation of a scheduling unit and its prequalification for the Balancing Market
Objective(s)Enable pre-qualified FSP and FSPA resources to provide balancing services in the balancing market via BSP
Related business case(s)EACL-PL-01 Prequalification

1.4. Narrative of Use Case

Short description

BSP registration on the flexibility platform BSP verification of the technical capabilities of FSP and FSPA Creation of a scheduling unit by the BSP based on selected FSP and FSPA resources Testing the scheduling unit and confirming that the BSP and this scheduling unit meet the conditions set out in the Terms and Condition Related to Balancing Confirmation by TSO of BSP’s ability to provide balancing services based on a scheduling unit made up of FSP and FSPA resources

Complete description

Registration of BSP on Flexibility Platform

Scenario 1 BSP already has a contract with TSO for the provision of balancing services

The BSP registers on the flexibility platform.

1.5. Key Performance Indicatiors (KPI)

IDNameDescriptionReference to mentioned use case objectives

1.6. Use case conditions

Assumptions
EACL-PL-04
Prerequisites
EACL-PL-04

1.7. Further information to the use case for classification/mapping

Relation to other use cases
Level of depth
Prioritisation
Generic, regional or national relation
National Polish Flexibility Market
Nature of the use cases
Business Use Case
Further keywords for classification

1.8. General remarks

General remarks

2. Diagrams of Use Case

EACL-PL-04 BSP on Platform_Use case diagram EACL-PL-04 BSP on Platform_BUC overview EACL-PL-04 Scenario 1 EACL-PL-04 Scenario 2 EACL-PL-04 Scenario 3a EACL-PL-04 Scenario 3b EACL-PL-04 Scenario 4 EACL-PL-04 Scenario 5

3. Technical Details

3.1. Actors

Actor NameActor TypeActor DescriptionFurther information specific to this Use Case
Transmission System Operator (TSO)BusinessA natural or legal person who is responsible for operating, ensuring the maintenance of and, if necessary, developing the transmission system in a given area and, where applicable, its interconnections with other systems, and for ensuring the long-term ability of the system to meet reasonable demands for the transmission of electricity
Distribution System Operator (DSO)BusinessA natural or legal person who is responsible for operating, ensuring the maintenance of and, if necessary, developing the distribution system in a given area and, where applicable, its interconnections with other systems, and for ensuring the long-term ability of the system to meet reasonable demands for the distribution of electricity
Flexibility Service Provider (FSP)BusinessA natural or legal person who is a market participant providing flexibility services to any electricity market that represents and aggregates the capacity of the entities that own a distributed energy resources (DER).
Market Operator (MO) or Flexibility Platform Operator (FPO)BusinessA natural or legal person who organizes auctions (continuous auction, discrete auctions, call for tenders) between buyers and sellers of electricity-related products in the markets. Manage/operate the platform for trading (where bids and offers are collected). Clear the market and communicate results.
Balancing Service ProviderBusinessA market participant with reserve-providing units or reserve-providing groups able to provide balancing services to TSO or a market participant providing either or both balancing energy and balancing capacity to transmission system operators

3.2. References

No.References TypeReferenceStatusImpact on Use CaseOrganistaor / OrganisationLink

4. Step by Step Analysis of Use Case

4.1. Overview of Scenarios

No.Scenario NameScenario DescriptionPrimary ActorTriggering EventPre-ConditionPost-Condition
1Registration of new BSPNoneRegistration of new BSP
2Registration of existing BSPNoneRegistration of existing BSP
3Assignment of resourcesNoneAssignment of resources
4VerificationNoneVerification
5RegistrationNoneRegistration
6Change within the scheduling unitNoneChange within the scheduling unit
7Request for recertification demanded by TSONoneRequest for recertification demanded by TSO

Notes

4.2. Steps – Scenarios

Scenario Name:
Registration of new BSP
Step No.Event.Name of Process/ ActivityDescription of Process/ Activity.ServiceInformation Producer (Actor)Information Receiver (Actor)Information ExchangedRequirements, R-ID
Scenario Name:
Registration of existing BSP
Step No.Event.Name of Process/ ActivityDescription of Process/ Activity.ServiceInformation Producer (Actor)Information Receiver (Actor)Information ExchangedRequirements, R-ID
Scenario Name:
Assignment of resources
Step No.Event.Name of Process/ ActivityDescription of Process/ Activity.ServiceInformation Producer (Actor)Information Receiver (Actor)Information ExchangedRequirements, R-ID
Scenario Name:
Verification
Step No.Event.Name of Process/ ActivityDescription of Process/ Activity.ServiceInformation Producer (Actor)Information Receiver (Actor)Information ExchangedRequirements, R-ID
Scenario Name:
Registration
Step No.Event.Name of Process/ ActivityDescription of Process/ Activity.ServiceInformation Producer (Actor)Information Receiver (Actor)Information ExchangedRequirements, R-ID
Scenario Name:
Change within the scheduling unit
Step No.Event.Name of Process/ ActivityDescription of Process/ Activity.ServiceInformation Producer (Actor)Information Receiver (Actor)Information ExchangedRequirements, R-ID
Scenario Name:
Request for recertification demanded by TSO
Step No.Event.Name of Process/ ActivityDescription of Process/ Activity.ServiceInformation Producer (Actor)Information Receiver (Actor)Information ExchangedRequirements, R-ID

5. Information Exchanged

Information exchanged IDName of InformationDescription of Information ExchangedRequirement

6. Requirements (optional)

Category IdentifierNameDescriptionmRID
Req_IDReq_Name‘Balancing Service Provider (BSP) on the Flexibility Platform’
IdentifierNameDescriptionmRID

7. Common Terms and Definitions

8. Custom Information (optional)

KeyValueRefers to Section