UC2-5
State Estimation
1. Description of the Use Case
1.1. Name of the Use Case
| ID | Area /Domain(s)/Zone(s) | Name of the Use Case |
|---|
| 1 | Energy, | UC2-5 |
1.2. Version Management
| Version No. | Date | Name of author(s) | Changes | Approval status |
|---|
| 1 | 2021-11-05T00:00:00 | ICCS, | First version | Final |
1.3. Scope and Objectives of Use Case
| |
|---|
| Scope | GRIDFLEX, X-FLEX platform |
| Objective(s) | None |
| Related business case(s) | None |
1.4. Narrative of Use Case
Short description
State Estimation
Complete description
State estimation consists in the solution of an optimization problem that processes the measurements together with the network model in order to determine the optimal estimate of the system state. The output of state estimation is typically the voltage magnitude and phase (phase-to-ground voltage phasors) at all the network buses.
| ID | Name | Description | Reference to mentioned use case objectives |
|---|
1.6. Use case conditions
| Relation to other use cases |
|---|
|
| Level of depth |
| Prioritisation |
| High |
| Generic, regional or national relation |
|
| Nature of the use cases |
|
| Further keywords for classification |
|
2. Diagrams of Use Case
3. Technical Details
3.1. Actors
| Actor Name | Actor Type | Actor Description | Further information specific to this Use Case |
|---|
3.2. References
| No. | References Type | Reference | Status | Impact on Use Case | Organistaor / Organisation | Link |
|---|
4. Step by Step Analysis of Use Case
4.1. Overview of Scenarios
| No. | Scenario Name | Scenario Description | Primary Actor | Triggering Event | Pre-Condition | Post-Condition |
|---|
| 1 | Main path | None | | Main path | | |
| 2 | Exception path | None | | Exception path | | |
Notes
4.2. Steps – Scenarios
| Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
|---|
| 1 | Acquisition of data | None | The measurements devices send data | None | | | | |
| 2 | State estimation calculation | None | With the received measurements the state estimation algorithm produces optimal power system data | None | | | | |
| 3 | Trigger the bad data detector | None | The verification of the accuracy and reliability of the estimated state is conducted by interacting with the bad data detector | None | | | | |
| 4 | Coupling with real-time applications | None | The state estimator forwards its outcome to various real-time applications (UC 2.7) | None | | | | |
| Scenario Name: |
|---|
| Exception path |
| Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
|---|
| 1 | Bad data are detected | None | Based on accuracy bad data are removed and system state is recalculated | None | | | | |
| Information exchanged ID | Name of Information | Description of Information Exchanged | Requirement |
|---|
6. Requirements (optional)
| Category Identifier | Name | Description | mRID |
|---|
| Req_ID | Req_Name | ‘State Estimation’ | |
| Identifier | Name | Description | mRID |
|---|
7. Common Terms and Definitions
| Key | Value | Refers to Section |
|---|