ifference between revisions of "EMO:Powerflow Case Components"

From EMO Wiki
Jump to navigation Jump to search
(Created page with "{{#hidens}} === 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 ...")
 
Line 1: Line 1:
{{#hidens}}
+
{{#hidens:}}
 
=== Definition ===
 
=== 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.  
 
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.  

Revision as of 14:55, 28 January 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
Transmission System (Static with periodic changes)
EMS/COMIT text-based files or online database
Contains static Circuit and dynamic re-rating details that influence dispatch
Equations
Transmission System (periodic changes)
EMS/COMIT text-based files or online database
Contains dynamic Equation Constraint applications and re-ratings
Nodes
Market (Dynamic time series)
EMS
Nodal demand data
Units
Market (Dynamic time series)
COMIT
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 - Back