ifference between revisions of "EMO:System Architecture"

From EMO Wiki
Jump to navigation Jump to search
Line 28: Line 28:
 
|
 
|
 
:''User Data Files''
 
:''User Data Files''
|:You can create your own Transmission System, Demand and Offers data files to upload into ''EMarketoffer''.
+
|
:----
+
:You can create your own Transmission System, Demand and Offers data files to upload into ''EMarketoffer''.
 +
----
 
: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.
 
: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.
:----
+
----
 
|-
 
|-

Revision as of 09:57, 18 December 2012

Technical Architecture

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.

Logical Architecture

The logical architecture of EMarketOffer is described in the figure and table below.

File:Logical Architecture.PNG
Figure 1: EMarketOffer Logical Architecture
Component Purpose
Online database(s)
EMarketOffer can access networked online databases containing market and transmission system data
EM6 Data Files
Transmission System data provided in standard format by the System Operator can be uploaded into EMarketOffer
COMIT Data Files
Offers and Demand data provided in standard format by the Market operator can be uploaded into EMarketOffer
User Data Files
You can create your own Transmission System, Demand and Offers data files to upload into EMarketoffer.

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.