EMO:System Architecture - Revision history

Greg: /* Logical Architecture */

2014-02-09T21:05:10Z

Logical Architecture

Greg: /* Logical Architecture */

2014-02-09T20:43:44Z

Logical Architecture

Greg: /* Logical Architecture */

2013-05-05T21:43:36Z

Logical Architecture

Greg: /* Logical Architecture */

2013-05-03T04:55:09Z

Logical Architecture

Sisep: /* Logical Architecture */

2013-02-08T01:08:03Z

Logical Architecture

Sisep: /* Logical Architecture */

2013-02-08T01:05:47Z

Logical Architecture

Sisep: /* Technical Architecture */

2013-02-08T01:04:46Z

Technical Architecture

Sisep: /* Logical Architecture */

2013-01-13T22:17:41Z

Logical Architecture

Sisep: /* Logical Architecture */

2013-01-13T22:17:22Z

Logical Architecture

Sisep: /* Logical Architecture */

2012-12-17T21:04:20Z

Logical Architecture

@@ Line 52: / Line 52: @@
+|
 :The Powerflow engine calculates the powerflows for a specified network using given nodal injection and off-take.  The engine provides essential support for historical (market) data analysis and powerflow case analysis.
 |-
+|

← Older revision		Revision as of 20:43, 9 February 2014
Line 60:		Line 60:


−	[[~~EMO:EMarketOffer User Manual~~\|Home~~]] - [[EMO:System Overview\|Back~~]]	+	[[Main Page\|Home]]

@@ Line 12: / Line 12: @@
 |-
+|
-:''Online database(s)''
+:''Online databases''
+|
-:''EMarketOffer'' can access networked online databases containing market and transmission system data
+:''EMarketOffer'' can access networked online (in-house) databases containing market and transmission system data
 |-
+|
-:''EM6 Data Files''
+:''Data Files''
+|
-:Transmission System data provided in standard format by the System Operator can be uploaded into ''EMarketOffer''
+:Transmission System and Reserves data provided in standard format by Energy Link and uploaded into ''EMarketOffer''
 |-
+|

@@ Line 22: / Line 22: @@
 |-
+|
-:''COMIT Data Files''
+:''WITS Data Files''
+|
 :Offers and Demand data provided in standard format by the Market operator can be uploaded into ''EMarketOffer''

@@ Line 36: / Line 36: @@
 :''Presentation Interface''
+|
-:The collection of information presentation features that allow you to visualise the '''''Current Data Set'''''.  These include the '''''[[EMO:The Map|Map]]''''', '''''[[EMO:Charts|Charts]]''''', '''''Information Windows, Watch Windows''''' and '''''[[EMO:Reports|Reports]]'''''.
+:The collection of information presentation features that allow you to visualise the '''''Current Data Set'''''.  These include the '''''[[EMO:The Map|Map]]''''', '''''[[EMO:Charts|Charts]]''''', '''''[[EMO:The_Display_Area_Information_Grids#Information_Windows|Information Windows]]''''', '''''[[EMO:The_Edit_Menu#Watch_Window|Watch Windows]]''''' and '''''[[EMO:The_Edit_Menu#The_Reports_and_Graphs_Option|Reports]]'''''.
 |-
+|

@@ Line 3: / Line 3: @@
 ''EMarketOffer'' is provided as a single executable program developed in C# using Microsoft's .net environment.  It is designed to operate as a desktop application and can be configured to operate as a client of networked online databases.  To support mobile users the system can also operate when disconnected from the corporate network using data uploaded from corporate databases or appropriately formatted files.  Offline data must be stored in the local machine in relational database schema implemented in either Microsoft Access or SQL server.
-'''''Forecast Definitions''''' and forecast results are stored in binary or XML file formats and can be exported for use in applications such as Excel and other ''EMarketOffer'' implementations.  Forecast results files can be stored either on the client PC's local drive or on a mapped network drive.  Energy Link recommends Forecast output is stored on the local drive by default to minimise the effects of network latency on Forecast Run speed.  Forecast files can subsequently exported to networked locations either in native XML format or translated into csv format.
+'''''[[EMO:The Forecast Definition Window|Forecast Definitions]]''''' and forecast results are stored in binary or XML file formats and can be exported for use in applications such as Excel and other ''EMarketOffer'' implementations.  Forecast results files can be stored either on the client PC's local drive or on a mapped network drive.  Energy Link recommends Forecast output is stored on the local drive by default to minimise the effects of network latency on Forecast Run speed.  Forecast files can subsequently exported to networked locations either in native XML format or translated into csv format.
 ====Logical Architecture====

@@ Line 32: / Line 32: @@
 ----
 :'''TIP:''' To avoid the time consuming task of creating of large, customised time-series data files from scratch, use ''EMarketOffer'' to create output files of Offer and Demand data from database downloads, and store them in the Library. These can be edited in Excel as required and uploaded into new Forecast Definitions.
 |-
+|

@@ Line 6: / Line 6: @@
 ====Logical Architecture====
-The logical architecture of ''EMarketOffer'' is described in the figure and table below.
+The logical architecture of ''EMarketOffer'' is described in the table below.
-[[File:Logical Architecture.PNG|600px|thumb|Figure 1: EMarketOffer Logical Architecture]]
 {|class="wikitable"
 ! Component !! Purpose

← Older revision		Revision as of 21:04, 17 December 2012
Line 38:		Line 38:
	\|		\|
	:The collection of information presentation features that allow you to visualise the '''''Current Data Set'''''. These include the '''''Map''''', '''''Charts''''', '''''Information Windows, Watch Windows''''' and '''''Reports'''''.		:The collection of information presentation features that allow you to visualise the '''''Current Data Set'''''. These include the '''''Map''''', '''''Charts''''', '''''Information Windows, Watch Windows''''' and '''''Reports'''''.
		+	\|-
		+	\|
		+	:''Data Source Manager''
		+	\|
		+	:Manages the run-time data displayed through the Presentation Interface
		+	\|-
		+	\|
		+	:''Forecaster''
		+	\|
		+	:Forecasts a range of Market-related variables for a specific period of time, based on a user-defined Definition which can be constructed using a mix of real (historical) data and user-created data. A special forecasting feature (Scenario mode) allows immediate, multiple re-forecasts for a selected single period using interactively modified Scenario details.
		+	\|-
		+	\|
		+	:''Powerflow Engine''
		+	\|
		+	:The Powerflow engine calculates the powerflows for a specified network using given nodal injection and off-take. The engine provides essential support for historical (market) data analysis and powerflow case analysis.
		+	\|-
		+	\|
		+	:''Reports and Export Files''
		+	\|
		+	:Reports and Export Files are produced by ''EMarketOffer's'' reporting capabilities.
		+	\|}
		+
		+
		+	[[EMO:EMarketOffer User Manual\|Home]] - [[EMO:System Overview\|Back]]