EMO:Data Storage Directory Structure

EMarketOffer creates two separate directory structures during installation:

• Program files
• Data files

Program Files

During the installation process you can choose where EMarketOffer places its program files (default C:\Program Files\Energy Link\EMO). This folder contains the EMarketOffer executable and the dlls (dynamic link libraries) required by the program.

Warning! You should not attempt to modify or move the location of any of these files after installation - doing so will cause the program to malfunction.

Data Files

During installation EMarketOffer creates a data directory structure containing these folders:

• Connection
• Forecast
• Inputs
• Licence
• Maps
• Positions
• Reports
• Settings

You can select the location for the data folders during the installation process. For performance reasons it is recommended that the data folder be located on the same computer as the EMarketOffer executable.

The Connection Folder

The information required to connect EMarketOffer to external databases is stored here.

File	Purpose	Comment
<Configuration_Name>.xml Where <Configuration_Name> is the name of a previously created Database Connectivity Configuration.	Stores database connectivity data referred to during program launch	Editing, deleting or moving this file may cause EMarketOffer to malfunction.

The Forecast Folder

This folder stores the definitions of Forecasts and Powerflow Cases (.xml format), and the results of Forecasts, Powerflow Cases and Scenarios (binary form).

Sub-Folder	File	Purpose	Comment
Forecasts	<My_Forecast>.ibn	Contains the output in binary form of the last run of the 'My_Forecast' Forecast Definition	One .ibn file will exist for each currently available Forecast Definition that has been run. NOTE: Deleting a Forecast Definition using the Main Window Data Source Manager will delete the associated .ibn file.
	Forecasts.xml	Contains the latest Definitions for all current Forecasts.	In editing or deleting this file you run the risk of losing all current Forecast Definitions and associated results data.
Powerflows	<My_Powerflow>.ibn	Contains the output in binary form of the last run of the 'My_Powerflow' Powerflow Case Definition	One .ibn file will exist for each currently available Powerflow Case Definition that has been run. NOTE: Deleting a Powerflow Case Definition using the Main Window Data Source Manager will delete the associated .ibn file.
	Powerflows.xml	Contains the latest Definitions for all current Powerflow Cases.	In editing or deleting this file you run the risk of losing all current Powerflow Case Definitions and associated results data.
Scenarios	<My_Scenario>.scn	Contains the output in binary form of the 'My_Scenario' Scenario	One .scn file will exist for each currently available Scenario
Library	<My_Component>.xml	Contains the definition for a saved Powerflow Case or Forecast Component.

The Inputs Folder

The Inputs folder contains several sub-folders:

File:Inputs Folder.PNG

Figure 2 - Inputs Folder Directory

Offers

EMarketOffer can load Offers from a database or from file. Offers files in the standard CSV format as provided by the COMIT system can be placed in the Offers folder, which can also be used as a library for user-defined/amended Offers data.

NOTE: This folder is created during installation for convenience; however EMarketOffer can read properly formatted files from any location.

Grid

EMarketOffer uses accurate Transmission System data for analysis of historical periods and as input into Forecast Definitions and Powerflow Cases. Transmission System configuration data downloaded from The EM6 and COMIT information services must be placed in respective sub-folders under this folder. EMarketOffer 'looks for' preferentially for system configuration data in these files during startup.

The Input Data section contains details on each file type.

The Licence Folder

Your customised license file is stored in the License folder.

Warning! This file contains important information about your installation. It is encrypted and you should not attempt to edit this file in any way. The program will fail to startup if the licence file is missing or altered.

The Maps Folder

Data required to support the Mapping function is stored here.

File:Maps Folder.PNG

Figure 3 - The Maps Data Directory

Folder	Purpose
NZ	Specifies a collection of maps (typically NZ) and contains the configuration data files (.config) for the full set of maps. Maps from only one collection can be displayed at a time.
Large Maps	Contains low level detail Map graphics in .emf format
Medium Maps	Contains medium level detail Map graphics in .emf format
Small	Contains high level detail Map graphics in .emf format

The Positions Folder

Map position details for Transmission System elements are stored here.

File	Purpose	Comment
NodePositions.csv	Contains Map positions of Market Nodes.	Updated automatically as Nodes are added and re-positioned through the Presentation Interface - should not be edited manually.
SubstationPositions.csv	Contains Map positions of Substations

The Reports Folder

This is the default folder for storing Report Output files, which are typically in .csv format and named according to their data content and date range.

The Settings Folder

User settings files are stored in here.

File	Purpose	Comment
EmbeddedUnits.xml	Contains the latest list of Embedded Generators	Updated automatically as Nodes are added and re-positioned through the Presentation Interface - should not be edited manually
WatchLists.xml	Contains the latest lists of Watched items
Regions.xml	Contains the latest Region set definitions
Views.xml	Contains the latest Main Map View specifications
Companies.xml	Contains the latest Company definition details
ExcludedEquations.xml	Contains the latest list of Equations Constraints to be excluded when loading Transmission System data into a Forecast Definition

Home - Back