ifference between revisions of "EMO:System Architecture"
Jump to navigation
Jump to search
| (13 intermediate revisions by 2 users not shown) | |||
| 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. | ''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==== | ====Logical Architecture==== | ||
| − | The logical architecture of ''EMarketOffer'' is described in the | + | The logical architecture of ''EMarketOffer'' is described in the table below. |
| − | + | ||
{|class="wikitable" | {|class="wikitable" | ||
! Component !! Purpose | ! Component !! Purpose | ||
|- | |- | ||
| | | | ||
| − | :''Online | + | :''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 |
|- | |- | ||
| | | | ||
| − | :'' | + | :''Data Files'' |
| | | | ||
| − | :Transmission System data provided in standard format by | + | :Transmission System and Reserves data provided in standard format by Energy Link and uploaded into ''EMarketOffer'' |
|- | |- | ||
| | | | ||
| − | :'' | + | :''WITS Data Files'' |
| | | | ||
:Offers and Demand data provided in standard format by the Market operator can be uploaded into ''EMarketOffer'' | :Offers and Demand data provided in standard format by the Market operator can be uploaded into ''EMarketOffer'' | ||
| 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 | + | ---- |
| − | : | + | :'''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. |
| + | |- | ||
| + | | | ||
| + | :''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]]''''', '''''[[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]]'''''. | ||
|- | |- | ||
| + | | | ||
| + | :''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. | ||
| + | |- | ||
| + | | | ||
| + | :''Auto-SFT Engine'' | ||
| + | | | ||
| + | :The Auto-SFT engine calculates constraints equations that protects circuits during an N - 1 loss of another circuit for a specified network and dispatch solve or powerflow. | ||
| + | |- | ||
| + | | | ||
| + | :''Reports and Export Files'' | ||
| + | | | ||
| + | :Reports and Export Files are produced by ''EMarketOffer's'' reporting capabilities. | ||
| + | |} | ||
| + | |||
| + | |||
| + | [[Main Page|Home]] | ||
Latest revision as of 10:05, 10 February 2014
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 table below.
| Component | Purpose |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|