ifference between revisions of "EMO:Powerflow Case Components"

From EMO Wiki
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 14: Line 14:
 
:Transmission System ('''''Static''''' with periodic changes)
 
:Transmission System ('''''Static''''' with periodic changes)
 
|
 
|
:Grid data files or online database
+
:Grid data files or database
 
|
 
|
:Contains static Circuit and dynamic re-rating details that influence dispatch
+
:Contains static circuit data that influence power flow
|-
 
! Equations
 
|
 
:Transmission System (periodic changes)
 
|
 
:Grid data files or online database
 
|
 
:Contains dynamic Equation Constraint applications and re-ratings
 
 
|-
 
|-
 
! Nodes
 
! Nodes
Line 30: Line 22:
 
:Market ('''''Dynamic time series)
 
:Market ('''''Dynamic time series)
 
|
 
|
:EMS
+
:In-house database or profile files
 
|
 
|
 
:Nodal demand data
 
:Nodal demand data
Line 38: Line 30:
 
:Market (Dynamic time series)
 
:Market (Dynamic time series)
 
|
 
|
:In-house database
+
:In-house database or profile files
 
|
 
|
 
:Generation
 
:Generation
Line 53: Line 45:
  
  
[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Powerflow Analysis|Back]]
+
[[Main Page|Home]]

Latest revision as of 09:38, 13 February 2014

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
Transmission System (Static with periodic changes)
Grid data files or database
Contains static circuit data that influence power flow
Nodes
Market (Dynamic time series)
In-house database or profile files
Nodal demand data
Units
Market (Dynamic time series)
In-house database or profile files
Generation


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:

  1. The whole Definition
  2. A whole class (e.g. Demand for all Nodes)
  3. Individual items within a class (e.g. selected Circuits within the circuit class)


Home