ifference between revisions of "EMO:System Architecture"

From EMO Wiki
Jump to navigation Jump to search
Line 11: Line 11:
 
! Component !! Purpose
 
! Component !! Purpose
 
|-
 
|-
|
 
 
:''Online database(s)''
 
:''Online database(s)''
 
|
 
|
 
:''EMarketOffer'' can access networked online databases containing market and transmission system data
 
:''EMarketOffer'' can access networked online databases containing market and transmission system data
 
|-
 
|-

Revision as of 09:37, 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
Online database(s)
Component Purpose
EMarketOffer can access networked online databases containing market and transmission system data