ifference between revisions of "EMO:Powerflow Case Components"
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
:Transmission System ('''''Static''''' with periodic changes) | :Transmission System ('''''Static''''' with periodic changes) | ||
| | | | ||
| − | :Grid data files or | + | :Grid data files or database |
| | | | ||
:Contains static Circuit and dynamic re-rating details that influence dispatch | :Contains static Circuit and dynamic re-rating details that influence dispatch | ||
| Line 22: | Line 22: | ||
:Transmission System (periodic changes) | :Transmission System (periodic changes) | ||
| | | | ||
| − | :Grid data files or | + | :Grid data files or database |
| | | | ||
:Contains dynamic Equation Constraint applications and re-ratings | :Contains dynamic Equation Constraint applications and re-ratings | ||
| Line 30: | Line 30: | ||
:Market ('''''Dynamic time series) | :Market ('''''Dynamic time series) | ||
| | | | ||
| − | : | + | :Grid data files or database |
| | | | ||
:Nodal demand data | :Nodal demand data | ||
Revision as of 18:22, 3 May 2013
Definition
A Powerflow Case Component is all or part of a Powerflow Case Definition stored separately as an .xml file. Components are created by exporting all or selected parts of a Powerflow Case Definition to the Component Library.
Purpose
Components can be directly imported into new Case Definitions at any time. Components can also be made available to other users of EMarketOffer and incorporated into their Case Definitions.
Component Classes
| Class | Type | Source | Description |
|---|---|---|---|
| Circuits |
|
|
|
| Equations |
|
|
|
| Nodes |
|
|
|
| Units |
|
|
|
NOTE: It is possible to create data for any of these classes yourself without using the listed data sources.
A Powerflow Case Component can contain data from any one of three levels:
- The whole Definition
- A whole class (e.g. Demand for all Nodes)
- Individual items within a class (e.g. selected Circuits within the circuit class)