EMK Wiki - User contributions [en]

Main Page

2014-04-04T01:10:43Z

Greg:

; Current Release Version of EMarket: ''EMarket 5.4.1''

''[[EMK:EMarket 5 Release Notes|EMarket 5 Release Notes]]''

'''[[EMK:EMarket User Manual | EMarket User Manual]]'''

'''[[EMK:EMarket 5 Notes | EMarket 5 Release Commentary]]'''

'''[[EMK:EMarket Development | EMarket Development Path and Requests]]'''

Main Page

2014-04-04T01:08:13Z

Greg:

; Current Release Version of EMarket: ''EMarket 5.4.1''

''[[Release Notes | EMarket_5_Release_Notes]]''

'''[[EMK:EMarket User Manual | EMarket User Manual]]'''

'''[[EMK:EMarket 5 Notes | EMarket 5 Release Commentary]]'''

'''[[EMK:EMarket Development | EMarket Development Path and Requests]]'''

EMK:Main Page

2014-04-04T01:07:56Z

Greg: moved EMK:Main Page to Main Page

#REDIRECT [[Main Page]]

Main Page

2014-04-04T01:07:56Z

Greg: moved EMK:Main Page to Main Page

{{#hidens:}}

; Current Release Version of EMarket: ''EMarket 5.4.1''

''[[Release Notes | EMarket_5_Release_Notes]]''

'''[[EMK:EMarket User Manual | EMarket User Manual]]'''

'''[[EMK:EMarket 5 Notes | EMarket 5 Release Commentary]]'''

'''[[EMK:EMarket Development | EMarket Development Path and Requests]]'''

Special:Badtitle/NS106:The Data Grid

2013-08-11T21:30:38Z

Greg: /* Copying to Clipboard */

{{#hidens:}}
All text-format data appearing in the '''''Presentation Interface''''' appears in a Data Grid. The Data Grid can appear as:
*A single data entry field (a single cell grid)
*A column of data entry fields
*A row of data entry fields
*A table ("grid") of data entry fields

===Editing a Data Grid Field===

'''>> To enter text in a field:'''

1. Make the field current and enter field 'edit mode' by:
*Right mouse click inside the field box (a grey border will appear around the cell)
*Use the Arrow (Up, Down, Left and Right) keys to move to the required field and pressing the <SPACE> bar

2. Type the text you want to enter - this will replace all text currently in the field


{|class="wikitable"
! Keys !! Function
|-
|
:''<F2>''
|
:Highlights the Field contents and makes it available for editing
|-
|
:''<Esc>''
|
:Discards any changes you have made the field in the current edit
|-
|
:''<Home>''
|
:Positions the text cursor before the first character in the field
|-
|
:''<End>''
|
:Positions the text cursor after the last character in the field
|}

----
NOTE: Standard text editing features such as highlighting, cutting and pasting are supported in Data Grid fields.
----

== Advanced Data Grid Features ==

===Selecting Fields===

{|class="wikitable"
! Selection !! Method !! Result
|-
|
:''Single Field''
|
:Click on field with the Mouse
|
:Field border is highlighted in grey
|-
|
:''Multiple Fields''
|
:Click and drag with mouse to describe a rectangle containing the required fields
|
:Selected fields are bordered in grey and appear highlighted in a pale purple (except for upper left field)
|-
|
:''Single Row''
|
:Click on row label
|
:Row border is highlighted in grey and row fields are highlighted in pale purple
|-
|
:''Single Column''
|
:Click on column header
|
:Column border is highlighted in grey and row fields are highlighted in pale purple
|-
|
:''Multiple Rows''
|
:Click and drag mouse across adjacent row labels
|
:The border of the selected rows is highlighted in grey and row fields are highlighted in pale purple
|-
|
:''Multiple Columns''
|
:Click and drag mouse across adjacent column headers
|
:The border of selected columns is highlighted in grey and column fields are highlighted in pale purple
|-
|
:''Whole Table''
|
:Click on the top left table corner (not the top left field)
|
:The whole table is highlighted in pale purple
|}

===Copying to Clipboard===


'''>> To copy all or part of a Data Grid to the Windows clip board:'''


#Highlighting the fields to be copied with a click and drag operation. Highlighted fields appear light purple except for the first field in the selection which remains uncoloured (but will appear within the grey border around all selected cells)
#Using ''<CTRL><C>'' or "<Ctrl><Shift><C>" to copy to the clip board. "<Ctrl><Shift><C>" copies the column headers as well as the data.

Data copied to the clipboard can be copied directly to Excel retaining the columns and rows of the original grid.

===Pasting from Clipboard===


'''>> Use <CTRL><V> to paste data from the clipboard into a Data Grid.'''

To be noted when pasting:
*Original row and column structure of a cutting from an Excel spreadsheet will be retained
*In cases where the data grid can only accept data for a fixed number of fields, surplus clipboard data will be discarded
*Where an unlimited number of repeating fields can be accepted in the Grid (e.g. Nodes defining a Transmission System) new rows will be created when the number of pasted rows exceeds the number of displayed rows

----
'''WARNING!''' The Data Grid attempts to paste directly in any area you have highlighted within the Grid. If the clipboard holds more fields than the highlighted area, extra clipboard fields are pasted over the top of non-highlighted fields replacing their contents.
----

===Creating New Rows in a Table===


'''>> To create a new row in a table Data Grid:'''
#Make the Data Grid the current object by clicking in any cell in the Grid (if a Grid contains no rows use one of the Column Headers)
#Press <INSERT>: a new blank row of fields will appear

===Sorting Fields by Column===
Some Data Grid Tables support data sorting.


'''>> To sort the whole table by the contents of a column alphanumerically:'''
#Double-click on the Header of the Column you want to sort by (sorts in ascending order)
#Double-clicking again will re-sort the table by column contents in descending order

----
NOTE: Where a Data Grid supports data sorting, the header for the column currently sorting the table will contain an arrow head facing upwards or downwards depending on whether the data has been sorted in ascending or descending order.
----

[[EMO:EMarketOffer User Manual |Home]] - [[EMO:The Presentation Interface|Back]]

Special:Badtitle/NS106:Using the Wiki

2013-05-06T22:12:10Z

Greg:

{{#hidens:}}
This manual is divided into seven sections and some additional information is provided in the Glossary.

To view a section of the manual simply click on the required link in the '''''[[EMO:EMarketOffer User Manual|EMarketOffer User Manual Main Page]].'''''

Where a word is highlighted in blue as above, there is a link to another page or section of a page. Rolling over the link with the mouse will bring up a popup text saying where clicking the link will take you.

=Searching the Wiki=
Generally the easiest way to find the information which you are searching for is to use the search function in the top right corner of the page. Type the keyword(s) which you are after and then press search. This won't return any results, but brings up a box with many tick boxes, allowing you to search in certain wiki namespaces. Select the "'''EMO'''" namespace by clicking on it, and then the Search button which appears just above the tick boxes. This will return all results with the namespace of "'''EMO'''".

=Navigation Side Bar=
If you click on any of the links in the Navigation side bar at the left of this screen, you will move out of the EMO namespace, so avoid doing this. TO get back to the EMO Home page, click on the '''Home''' link at the bottom of each page.

[[EMO:EMarketOffer User Manual|Home]]

Special:Badtitle/NS106:EMarketOffer User Manual

2013-05-06T22:08:52Z

Greg:

{{#hidens:}}
[[EMO:Release Notes|Release Notes]]

[[EMO:Using the Wiki|READ THIS FIRST: Using and Searching the Wiki]]

[[EMO:Getting Started|Getting Started]]

[[EMO:System Overview|System Overview]]

[[EMO:The Main Window|The Main Window]]

[[EMO:Forecasting|Forecasting]]

[[EMO:Powerflow Analysis|Powerflow Analysis]]

[[EMO:Scenarios|Scenarios]]

[[EMO:Data File Formats|Data File Formats]]

[[EMO:Glossary|Glossary]]

[[EMO:Main Page|Back to Main Page]]

Special:Badtitle/NS106:Release Notes

2013-05-05T22:06:11Z

Greg:

{{#hidens:}}
=Latest Release=
;EMO 4.11.2 Released 2-May-13
*Bug fixed in demand profile import for Powerflow mode
*Bug fixed in generation profile import for Powerflow mode
*EMO now automatically checks for new grid and reserves data when you start the program (if you leave EMO running overnight then you need to check manually when you come back to it)
*The File Inputs window EMO now shows the date to which input data is believed to be valid
*If you select a day in Market view for which EMO believes there is incomplete data, then "Incomplete Data" will show in read near the top left corner of the Main window. Hover over this and it shows the date to which inputs are available. Click on this and it opens the File Inputs window.
*EMO Help will now take you to this new wiki on the web. The wiki replaces the old online help and the user manual. It is easier and cheaper to maintain than the old manual and help material.
*We advise you check that the excluded items (see the Edit menu) include the following 8 wind farms: MAH, NZW, TAP, TUK, TWC, TWF, WHL, WWD
*Also check that the constraints DCSA_BenP1Aout, DCSA_BenP1Bout, DCSA_HayP1Aout, DCSA_HayP1Bout are excluded.
*EMO 4.11.2 is available at http://www.ellsoft.co.nz/downloads/emo/installemo4.11.2.zip
*The password is available for licensed users from Matt.Woods@energylink.co.nz ddi 03 474 9379.

=Previous Releases=
;EMO 4.10.4 Released 30-Oct-12
:There was a bug in EMO 4.10.3 when loading demand data into a Forecast from a file. EMO would halt with an exception notice from which clicking Continue would not recover. The bug was caused by an array which overflowed when reading the demand from the csv file.

;EMO 4.10.3 Released 31-Jul-12
:Quote of the year from Matt Woods, our Development Manager: “it’s like wading through mud” as he referred to the difficulties he experienced interpreting the data in the SPD daily case data files from which we now extract reserves, grid and constraint data. A long process, but we’re pretty much there now and Matt has even developed a nice developer’s utility for analysing the daily case data.

:The result is that EMO 4.10.3 is now ready for release in beta version (which means that our users need to perform their own testing before it can be confirmed as a final version before it can be confirmed as a final release).

;Previous Release (EMO 4.8.2) will not be Supported Much Longer
:The previous version release in Dec-11 uses a slightly different update mechanism for updating the grid and reserves inputs data files, which won’t be supported once all users on the latest version EMO 4.10.3. For that reason, we want to get all users onto 4.10.3 as quickly as possible.

:Changes in the new version are listed below.

:Input Data
1. Full grid data is available back to 22 July 2009 using the new data from the SPD daily case files (and prior to that using the old grid format data, although we are no longer supporting this older data).

2. Full reserves data is also available back to January 2010 (but not prior to that date).

3. Additional constraints associated with frequency keeping generators (constraining them up or down so that they operate within their FK range) are now captured and available in the constraints files.

4. Additional constraints associated with line outages are now captured and included in the constraints files.

5. The grid and reserves files will be updated most business days.

6. Items 1 – 5 above mean that EMO will be ready to solve the market without any manual input of reserves data or additional constraints.
:To get the latest data files, use File>File Inputs

:Go to the Download tab and click on the button labelled Check for New Files. If you have any problems with this, please contact Matt.

:Really Useful Changes to the User Interface

7. When you create a Scenario EMO will remember whether you last solved with or without reserves, and offer this as the default.

8. You can now add items to Watch Lists from all windows (not just from the map), e.g. right click on a row of offers in the Units window, or on an equation constraint in the Constraints window, and add it to a watch list.

9. The Data Sources window (lower right hand corner, where you see Market, Forecasts, Powerflows and Scenarios in a folder structure) has the ability to filter what you see in this window down to a particular day or trading period. This makes it easier to work with Scenarios and Forecasts.

10. Use Ctrl-Shift-C to copy data and column headings onto the Clipboard.

Other Improvements

11. We’ve started on making improvements to the way the HVDC link is modelled. We had hoped to get all of the changes in this release, but some more subtle changes are required and will be released later.

12. The performance of the solver was improved to handle the many additional constraints now included in the grid, constraints and reserves files.

13. A few bugs were found and fixed including handling of constraints on the HVDC link.

;Important Information About Solves (Forecasts and Scenarios)

:Where there are differences between solves produced by EMO and SPD, these are now likely to be caused by:

1. your input data being wrong or incomplete: this is the single biggest cause of problems with EMO’s solves, and if you have any doubts about your inputs, or which inputs to use, please feel free to call us to discuss;

2. your input data being wrong or incomplete (just repeating this for emphasis);

3. the handling of the HVDC link in EMO is slightly different to the handling in SPD;

4. there is a known issue with EMO’s pricing (but not dispatch) in some cases when a constraint creates a very large price difference across some parts of the grid;

5. EMO is a non-linear model (and hence models losses as quadratic losses) whereas SPD is a linear model and has to approximate quadratic losses with linear losses.

;EMO 4.8.2 Released 23-Dec-11
:This version is no longer supported as it is superseded by EMO 4.10.4.

;Grid Data

*There is a new file for VLRs which, during the VLR trial, will be created manually. When we know what format they will be delivered in on a permanent basis, then the new formatted will be handled in EMO and data capture automated. There is a limitation with the VLRs in this EMO version:
**note that DST changes are not handled exactly using these trial ratings;
*There is a new window for grid data, accessed from File Menu>Grid Data:
**this used to be accessed from File>Data Sources;
**this is the window where you now go to download new grid files;
**this window shows when the default ratings are valid and whether they ratings follow a SSW (summer shoulder winter) or VLR (variable line rating) scheme;
**click on the Download EMO Grid Files button to check for and load new grid files;
**the Use File Sourced Grid button is currently disabled, but files are used anyway;
**the table shows the dates and trading periods (Valid from and Valid to) between which the latest default ratings apply.
*Double click on any line in the table to see the default ratings that apply.
**For VLR lines:
***the table shows 6 MW capacity values and 5 TP (trading periods)
***the MW capacity in the first column applies from TP 1 to the 1 TP before the TP shown in the first TP column, and so on, e.g. “400 15 367 19” would mean 400 MW from TP 1 to 14, 367 MW from TP 15 to 18, and so on;
**For SSW lines the shows the summer, shoulder and winter ratings that apply;
**The Reratings tab shows a limited history of re-ratings that reflect outages or partial outages on the line, as represented in the new grid data files;
**The Dec row may not display correctly (known bug) but nevertheless the VLR ratings are applied correctly in EMO.
*Re-ratings changes:
**EMO now distinguishes changes in the default ratings (SSW or VLR) from other re-ratings, which will make the new re-ratings file smaller;
**even with the new grid files, there is no way of knowing if an outage present in the last few tradings periods in the file will persist, e.g. the permanent split between FHL and WPW. As a solution, any line in an outage (capacity = zero) for the last 48 trading periods in the grid files is assumed to be in outage into the future;
*Delays in getting grid data: users have noted delays of up to 10 days in getting the raw SPD final pricing case data posted on the EA’s web site, which apparently occurred due to the need to handle files manually. But the EA advised us that the process would be automated and the data available from an FTP server: this has now happened. We are working through re-automating the capture process at our end, and this will be completed early next year;
*refreshing grid files: if you think your grid files are corrupt (perhaps you opened one in Excel, modified it and then saved it again), the easiest solution is to delete the file(s) and then get EMO to check for new files from the File Menu>Grid Data window (click the Download EMO Grid Files button).

;Demand Data
:Our '''recommendation''' for demand data continues to be to use the SPD demand data from WITS. Find this by logging onto WITS and selecting '''GXP Demand''' from the '''Market Data''' menu. To get accurate solves in EMO which mirror final prices, you must select Final as the Price Type. You will also need to do a multiple selection to get all nodes.

:'''BE WARNED''' - this data appears to be provisional in many cases and is often updated when final prices are published, so you need to make sure that you have the latest data that is consistent with final prices.

:'''BE WARNED AGAIN''' - if you use any other data set, then you may not get accurate solves with EMO. In many cases, small changes in demand make a big difference to the solve.

This data is what is used in SPD for solving final prices. It is gross demand with some important exceptions:
#wind farm output is netted off GXP/GIP demand. At grid-connected wind farm GIPs, therefore, you will find either negative or zero values. At GXPs with embedded wind farms you will find positive and sometimes also negative values, depending on whether or not the wind farms cause export to the grid;
#generation under 10 MW has a blanket exemption from offering so is netted off GXP demand, in the same way as embedded wind farms.

There are two key aspects to getting the demand right: one is to use the correct demand data, as described above, but the second is ensure that you are not double counting any generators. Whereas generation under 10 MW is not offered and therefore won’t have offers appear in the daily offer data, wind farms over 10 MW do offer and their offers do appear in the daily offer data. If you don’t remove the wind farm offers then you will double count their output in your solves. Solution: make sure you use the demand data described above, and then also exclude all wind farms by going to Edit>Excluded Items. As of this date, the excluded items should include the following:

Embedded Generators Excluded Equations

NZW DCSA_BenP1Aout

TAP DCSA_BenP1Bout

TUK DCSA_HayP1Aout

TWF DCSA_HayP1Bout

WHL

WWD

The wind farms above are NZ Windfarms Te Rere Hau, Te Apiti, te Uku, Tararua Windfarm, White Hill and West Wind. The excluded equations above relate to the HVDC link and are not required by EMO.

'''Enhancements'''

*The offers that you can change in a Scenario are shaded in a much brighter yellow which makes them easier to see on a laptop screen.
Bug fixes:
*the offers graph Edit>Supply & Demand>Offer Graph now loads much quicker
*detection of an infeasible solution was improved to reduce the occurrence of false infeasibilities.

[[EMO:EMarketOffer User Manual|Home]]

Special:Badtitle/NS106:Release Notes

2013-05-05T22:05:58Z

Greg:

{{#hidens:}}
=Latest Releases=
;EMO 4.11.2 Released 2-May-13
*Bug fixed in demand profile import for Powerflow mode
*Bug fixed in generation profile import for Powerflow mode
*EMO now automatically checks for new grid and reserves data when you start the program (if you leave EMO running overnight then you need to check manually when you come back to it)
*The File Inputs window EMO now shows the date to which input data is believed to be valid
*If you select a day in Market view for which EMO believes there is incomplete data, then "Incomplete Data" will show in read near the top left corner of the Main window. Hover over this and it shows the date to which inputs are available. Click on this and it opens the File Inputs window.
*EMO Help will now take you to this new wiki on the web. The wiki replaces the old online help and the user manual. It is easier and cheaper to maintain than the old manual and help material.
*We advise you check that the excluded items (see the Edit menu) include the following 8 wind farms: MAH, NZW, TAP, TUK, TWC, TWF, WHL, WWD
*Also check that the constraints DCSA_BenP1Aout, DCSA_BenP1Bout, DCSA_HayP1Aout, DCSA_HayP1Bout are excluded.
*EMO 4.11.2 is available at http://www.ellsoft.co.nz/downloads/emo/installemo4.11.2.zip
*The password is available for licensed users from Matt.Woods@energylink.co.nz ddi 03 474 9379.

=Previous Releases=
;EMO 4.10.4 Released 30-Oct-12
:There was a bug in EMO 4.10.3 when loading demand data into a Forecast from a file. EMO would halt with an exception notice from which clicking Continue would not recover. The bug was caused by an array which overflowed when reading the demand from the csv file.

;EMO 4.10.3 Released 31-Jul-12
:Quote of the year from Matt Woods, our Development Manager: “it’s like wading through mud” as he referred to the difficulties he experienced interpreting the data in the SPD daily case data files from which we now extract reserves, grid and constraint data. A long process, but we’re pretty much there now and Matt has even developed a nice developer’s utility for analysing the daily case data.

:The result is that EMO 4.10.3 is now ready for release in beta version (which means that our users need to perform their own testing before it can be confirmed as a final version before it can be confirmed as a final release).

;Previous Release (EMO 4.8.2) will not be Supported Much Longer
:The previous version release in Dec-11 uses a slightly different update mechanism for updating the grid and reserves inputs data files, which won’t be supported once all users on the latest version EMO 4.10.3. For that reason, we want to get all users onto 4.10.3 as quickly as possible.

:Changes in the new version are listed below.

:Input Data
1. Full grid data is available back to 22 July 2009 using the new data from the SPD daily case files (and prior to that using the old grid format data, although we are no longer supporting this older data).

2. Full reserves data is also available back to January 2010 (but not prior to that date).

3. Additional constraints associated with frequency keeping generators (constraining them up or down so that they operate within their FK range) are now captured and available in the constraints files.

4. Additional constraints associated with line outages are now captured and included in the constraints files.

5. The grid and reserves files will be updated most business days.

6. Items 1 – 5 above mean that EMO will be ready to solve the market without any manual input of reserves data or additional constraints.
:To get the latest data files, use File>File Inputs

:Go to the Download tab and click on the button labelled Check for New Files. If you have any problems with this, please contact Matt.

:Really Useful Changes to the User Interface

7. When you create a Scenario EMO will remember whether you last solved with or without reserves, and offer this as the default.

8. You can now add items to Watch Lists from all windows (not just from the map), e.g. right click on a row of offers in the Units window, or on an equation constraint in the Constraints window, and add it to a watch list.

9. The Data Sources window (lower right hand corner, where you see Market, Forecasts, Powerflows and Scenarios in a folder structure) has the ability to filter what you see in this window down to a particular day or trading period. This makes it easier to work with Scenarios and Forecasts.

10. Use Ctrl-Shift-C to copy data and column headings onto the Clipboard.

Other Improvements

11. We’ve started on making improvements to the way the HVDC link is modelled. We had hoped to get all of the changes in this release, but some more subtle changes are required and will be released later.

12. The performance of the solver was improved to handle the many additional constraints now included in the grid, constraints and reserves files.

13. A few bugs were found and fixed including handling of constraints on the HVDC link.

;Important Information About Solves (Forecasts and Scenarios)

:Where there are differences between solves produced by EMO and SPD, these are now likely to be caused by:

1. your input data being wrong or incomplete: this is the single biggest cause of problems with EMO’s solves, and if you have any doubts about your inputs, or which inputs to use, please feel free to call us to discuss;

2. your input data being wrong or incomplete (just repeating this for emphasis);

3. the handling of the HVDC link in EMO is slightly different to the handling in SPD;

4. there is a known issue with EMO’s pricing (but not dispatch) in some cases when a constraint creates a very large price difference across some parts of the grid;

5. EMO is a non-linear model (and hence models losses as quadratic losses) whereas SPD is a linear model and has to approximate quadratic losses with linear losses.

;EMO 4.8.2 Released 23-Dec-11
:This version is no longer supported as it is superseded by EMO 4.10.4.

;Grid Data

*There is a new file for VLRs which, during the VLR trial, will be created manually. When we know what format they will be delivered in on a permanent basis, then the new formatted will be handled in EMO and data capture automated. There is a limitation with the VLRs in this EMO version:
**note that DST changes are not handled exactly using these trial ratings;
*There is a new window for grid data, accessed from File Menu>Grid Data:
**this used to be accessed from File>Data Sources;
**this is the window where you now go to download new grid files;
**this window shows when the default ratings are valid and whether they ratings follow a SSW (summer shoulder winter) or VLR (variable line rating) scheme;
**click on the Download EMO Grid Files button to check for and load new grid files;
**the Use File Sourced Grid button is currently disabled, but files are used anyway;
**the table shows the dates and trading periods (Valid from and Valid to) between which the latest default ratings apply.
*Double click on any line in the table to see the default ratings that apply.
**For VLR lines:
***the table shows 6 MW capacity values and 5 TP (trading periods)
***the MW capacity in the first column applies from TP 1 to the 1 TP before the TP shown in the first TP column, and so on, e.g. “400 15 367 19” would mean 400 MW from TP 1 to 14, 367 MW from TP 15 to 18, and so on;
**For SSW lines the shows the summer, shoulder and winter ratings that apply;
**The Reratings tab shows a limited history of re-ratings that reflect outages or partial outages on the line, as represented in the new grid data files;
**The Dec row may not display correctly (known bug) but nevertheless the VLR ratings are applied correctly in EMO.
*Re-ratings changes:
**EMO now distinguishes changes in the default ratings (SSW or VLR) from other re-ratings, which will make the new re-ratings file smaller;
**even with the new grid files, there is no way of knowing if an outage present in the last few tradings periods in the file will persist, e.g. the permanent split between FHL and WPW. As a solution, any line in an outage (capacity = zero) for the last 48 trading periods in the grid files is assumed to be in outage into the future;
*Delays in getting grid data: users have noted delays of up to 10 days in getting the raw SPD final pricing case data posted on the EA’s web site, which apparently occurred due to the need to handle files manually. But the EA advised us that the process would be automated and the data available from an FTP server: this has now happened. We are working through re-automating the capture process at our end, and this will be completed early next year;
*refreshing grid files: if you think your grid files are corrupt (perhaps you opened one in Excel, modified it and then saved it again), the easiest solution is to delete the file(s) and then get EMO to check for new files from the File Menu>Grid Data window (click the Download EMO Grid Files button).

;Demand Data
:Our '''recommendation''' for demand data continues to be to use the SPD demand data from WITS. Find this by logging onto WITS and selecting '''GXP Demand''' from the '''Market Data''' menu. To get accurate solves in EMO which mirror final prices, you must select Final as the Price Type. You will also need to do a multiple selection to get all nodes.

:'''BE WARNED''' - this data appears to be provisional in many cases and is often updated when final prices are published, so you need to make sure that you have the latest data that is consistent with final prices.

:'''BE WARNED AGAIN''' - if you use any other data set, then you may not get accurate solves with EMO. In many cases, small changes in demand make a big difference to the solve.

This data is what is used in SPD for solving final prices. It is gross demand with some important exceptions:
#wind farm output is netted off GXP/GIP demand. At grid-connected wind farm GIPs, therefore, you will find either negative or zero values. At GXPs with embedded wind farms you will find positive and sometimes also negative values, depending on whether or not the wind farms cause export to the grid;
#generation under 10 MW has a blanket exemption from offering so is netted off GXP demand, in the same way as embedded wind farms.

There are two key aspects to getting the demand right: one is to use the correct demand data, as described above, but the second is ensure that you are not double counting any generators. Whereas generation under 10 MW is not offered and therefore won’t have offers appear in the daily offer data, wind farms over 10 MW do offer and their offers do appear in the daily offer data. If you don’t remove the wind farm offers then you will double count their output in your solves. Solution: make sure you use the demand data described above, and then also exclude all wind farms by going to Edit>Excluded Items. As of this date, the excluded items should include the following:

Embedded Generators Excluded Equations

NZW DCSA_BenP1Aout

TAP DCSA_BenP1Bout

TUK DCSA_HayP1Aout

TWF DCSA_HayP1Bout

WHL

WWD

The wind farms above are NZ Windfarms Te Rere Hau, Te Apiti, te Uku, Tararua Windfarm, White Hill and West Wind. The excluded equations above relate to the HVDC link and are not required by EMO.

'''Enhancements'''

*The offers that you can change in a Scenario are shaded in a much brighter yellow which makes them easier to see on a laptop screen.
Bug fixes:
*the offers graph Edit>Supply & Demand>Offer Graph now loads much quicker
*detection of an infeasible solution was improved to reduce the occurrence of false infeasibilities.

[[EMO:EMarketOffer User Manual|Home]]

Special:Badtitle/NS106:Release Notes

2013-05-05T22:05:21Z

Greg:

{{#hidens:}}
;EMO 4.11.2 Released 2-May-13
*Bug fixed in demand profile import for Powerflow mode
*Bug fixed in generation profile import for Powerflow mode
*EMO now automatically checks for new grid and reserves data when you start the program (if you leave EMO running overnight then you need to check manually when you come back to it)
*The File Inputs window EMO now shows the date to which input data is believed to be valid
*If you select a day in Market view for which EMO believes there is incomplete data, then "Incomplete Data" will show in read near the top left corner of the Main window. Hover over this and it shows the date to which inputs are available. Click on this and it opens the File Inputs window.
*EMO Help will now take you to this new wiki on the web. The wiki replaces the old online help and the user manual. It is easier and cheaper to maintain than the old manual and help material.
*We advise you check that the excluded items (see the Edit menu) include the following 8 wind farms: MAH, NZW, TAP, TUK, TWC, TWF, WHL, WWD
*Also check that the constraints DCSA_BenP1Aout, DCSA_BenP1Bout, DCSA_HayP1Aout, DCSA_HayP1Bout are excluded.
*EMO 4.11.2 is available at http://www.ellsoft.co.nz/downloads/emo/installemo4.11.2.zip
*The password is available for licensed users from Matt.Woods@energylink.co.nz ddi 03 474 9379.

;EMO 4.10.4 Released 30-Oct-12
:There was a bug in EMO 4.10.3 when loading demand data into a Forecast from a file. EMO would halt with an exception notice from which clicking Continue would not recover. The bug was caused by an array which overflowed when reading the demand from the csv file.

;EMO 4.10.3 Released 31-Jul-12
:Quote of the year from Matt Woods, our Development Manager: “it’s like wading through mud” as he referred to the difficulties he experienced interpreting the data in the SPD daily case data files from which we now extract reserves, grid and constraint data. A long process, but we’re pretty much there now and Matt has even developed a nice developer’s utility for analysing the daily case data.

:The result is that EMO 4.10.3 is now ready for release in beta version (which means that our users need to perform their own testing before it can be confirmed as a final version before it can be confirmed as a final release).

;Previous Release (EMO 4.8.2) will not be Supported Much Longer
:The previous version release in Dec-11 uses a slightly different update mechanism for updating the grid and reserves inputs data files, which won’t be supported once all users on the latest version EMO 4.10.3. For that reason, we want to get all users onto 4.10.3 as quickly as possible.

:Changes in the new version are listed below.

:Input Data
1. Full grid data is available back to 22 July 2009 using the new data from the SPD daily case files (and prior to that using the old grid format data, although we are no longer supporting this older data).

2. Full reserves data is also available back to January 2010 (but not prior to that date).

3. Additional constraints associated with frequency keeping generators (constraining them up or down so that they operate within their FK range) are now captured and available in the constraints files.

4. Additional constraints associated with line outages are now captured and included in the constraints files.

5. The grid and reserves files will be updated most business days.

6. Items 1 – 5 above mean that EMO will be ready to solve the market without any manual input of reserves data or additional constraints.
:To get the latest data files, use File>File Inputs

:Go to the Download tab and click on the button labelled Check for New Files. If you have any problems with this, please contact Matt.

:Really Useful Changes to the User Interface

7. When you create a Scenario EMO will remember whether you last solved with or without reserves, and offer this as the default.

8. You can now add items to Watch Lists from all windows (not just from the map), e.g. right click on a row of offers in the Units window, or on an equation constraint in the Constraints window, and add it to a watch list.

9. The Data Sources window (lower right hand corner, where you see Market, Forecasts, Powerflows and Scenarios in a folder structure) has the ability to filter what you see in this window down to a particular day or trading period. This makes it easier to work with Scenarios and Forecasts.

10. Use Ctrl-Shift-C to copy data and column headings onto the Clipboard.

Other Improvements

11. We’ve started on making improvements to the way the HVDC link is modelled. We had hoped to get all of the changes in this release, but some more subtle changes are required and will be released later.

12. The performance of the solver was improved to handle the many additional constraints now included in the grid, constraints and reserves files.

13. A few bugs were found and fixed including handling of constraints on the HVDC link.

;Important Information About Solves (Forecasts and Scenarios)

:Where there are differences between solves produced by EMO and SPD, these are now likely to be caused by:

1. your input data being wrong or incomplete: this is the single biggest cause of problems with EMO’s solves, and if you have any doubts about your inputs, or which inputs to use, please feel free to call us to discuss;

2. your input data being wrong or incomplete (just repeating this for emphasis);

3. the handling of the HVDC link in EMO is slightly different to the handling in SPD;

4. there is a known issue with EMO’s pricing (but not dispatch) in some cases when a constraint creates a very large price difference across some parts of the grid;

5. EMO is a non-linear model (and hence models losses as quadratic losses) whereas SPD is a linear model and has to approximate quadratic losses with linear losses.

;EMO 4.8.2 Released 23-Dec-11
:This version is no longer supported as it is superseded by EMO 4.10.4.

;Grid Data

*There is a new file for VLRs which, during the VLR trial, will be created manually. When we know what format they will be delivered in on a permanent basis, then the new formatted will be handled in EMO and data capture automated. There is a limitation with the VLRs in this EMO version:
**note that DST changes are not handled exactly using these trial ratings;
*There is a new window for grid data, accessed from File Menu>Grid Data:
**this used to be accessed from File>Data Sources;
**this is the window where you now go to download new grid files;
**this window shows when the default ratings are valid and whether they ratings follow a SSW (summer shoulder winter) or VLR (variable line rating) scheme;
**click on the Download EMO Grid Files button to check for and load new grid files;
**the Use File Sourced Grid button is currently disabled, but files are used anyway;
**the table shows the dates and trading periods (Valid from and Valid to) between which the latest default ratings apply.
*Double click on any line in the table to see the default ratings that apply.
**For VLR lines:
***the table shows 6 MW capacity values and 5 TP (trading periods)
***the MW capacity in the first column applies from TP 1 to the 1 TP before the TP shown in the first TP column, and so on, e.g. “400 15 367 19” would mean 400 MW from TP 1 to 14, 367 MW from TP 15 to 18, and so on;
**For SSW lines the shows the summer, shoulder and winter ratings that apply;
**The Reratings tab shows a limited history of re-ratings that reflect outages or partial outages on the line, as represented in the new grid data files;
**The Dec row may not display correctly (known bug) but nevertheless the VLR ratings are applied correctly in EMO.
*Re-ratings changes:
**EMO now distinguishes changes in the default ratings (SSW or VLR) from other re-ratings, which will make the new re-ratings file smaller;
**even with the new grid files, there is no way of knowing if an outage present in the last few tradings periods in the file will persist, e.g. the permanent split between FHL and WPW. As a solution, any line in an outage (capacity = zero) for the last 48 trading periods in the grid files is assumed to be in outage into the future;
*Delays in getting grid data: users have noted delays of up to 10 days in getting the raw SPD final pricing case data posted on the EA’s web site, which apparently occurred due to the need to handle files manually. But the EA advised us that the process would be automated and the data available from an FTP server: this has now happened. We are working through re-automating the capture process at our end, and this will be completed early next year;
*refreshing grid files: if you think your grid files are corrupt (perhaps you opened one in Excel, modified it and then saved it again), the easiest solution is to delete the file(s) and then get EMO to check for new files from the File Menu>Grid Data window (click the Download EMO Grid Files button).

;Demand Data
:Our '''recommendation''' for demand data continues to be to use the SPD demand data from WITS. Find this by logging onto WITS and selecting '''GXP Demand''' from the '''Market Data''' menu. To get accurate solves in EMO which mirror final prices, you must select Final as the Price Type. You will also need to do a multiple selection to get all nodes.

:'''BE WARNED''' - this data appears to be provisional in many cases and is often updated when final prices are published, so you need to make sure that you have the latest data that is consistent with final prices.

:'''BE WARNED AGAIN''' - if you use any other data set, then you may not get accurate solves with EMO. In many cases, small changes in demand make a big difference to the solve.

This data is what is used in SPD for solving final prices. It is gross demand with some important exceptions:
#wind farm output is netted off GXP/GIP demand. At grid-connected wind farm GIPs, therefore, you will find either negative or zero values. At GXPs with embedded wind farms you will find positive and sometimes also negative values, depending on whether or not the wind farms cause export to the grid;
#generation under 10 MW has a blanket exemption from offering so is netted off GXP demand, in the same way as embedded wind farms.

There are two key aspects to getting the demand right: one is to use the correct demand data, as described above, but the second is ensure that you are not double counting any generators. Whereas generation under 10 MW is not offered and therefore won’t have offers appear in the daily offer data, wind farms over 10 MW do offer and their offers do appear in the daily offer data. If you don’t remove the wind farm offers then you will double count their output in your solves. Solution: make sure you use the demand data described above, and then also exclude all wind farms by going to Edit>Excluded Items. As of this date, the excluded items should include the following:

Embedded Generators Excluded Equations

NZW DCSA_BenP1Aout

TAP DCSA_BenP1Bout

TUK DCSA_HayP1Aout

TWF DCSA_HayP1Bout

WHL

WWD

The wind farms above are NZ Windfarms Te Rere Hau, Te Apiti, te Uku, Tararua Windfarm, White Hill and West Wind. The excluded equations above relate to the HVDC link and are not required by EMO.

'''Enhancements'''

*The offers that you can change in a Scenario are shaded in a much brighter yellow which makes them easier to see on a laptop screen.
Bug fixes:
*the offers graph Edit>Supply & Demand>Offer Graph now loads much quicker
*detection of an infeasible solution was improved to reduce the occurrence of false infeasibilities.

[[EMO:EMarketOffer User Manual|Home]]

Special:Badtitle/NS106:Control Panel Components

2013-05-05T22:04:15Z

Greg: /* Features */

{{#hidens:}}
The appearance of the Control Panel changes with the context of the [[EMO:The Main Window|Main Window]] so not all of the following features will be visible in each different Control Panel view.
== The Current Data Source Panel ==

=== Purpose ===
To provide information about the Current Data Source and allow you select periods to view using the '''''Date and Time Selector''''' (where appropriate).

==== Market Data Source ====
When Market is selected as the Current Data Source, the text "''Data Source: Market''" is shown in the top left hand corner. Below this is an area for selection of
Date, time and time period within the Market Data Source.

==== Forecast Data Source ====
[[File:Forecast Data Source.PNG|400px|thumb|right|Figure 1 - Current Data Source Panel for Forecast Data Sources]]
When Forecast is selected as the Current Data Source, the text "''Data Source: Forecast''" is shown in the top left hand corner.

'''Components'''
{|class="wikitable"
! Component !! Purpose
|-
|
:''Forecast Parameters''
|
:Used to indicate the Forecast name and the Effective Date Range
|-
|
:''Function Buttons''
|
:Used to:
*Edit the underlying '''''[[EMO:The Forecast Definition Window|Forecast Definition]]'''''
*Cause the first Trading Period in the Effective Date Range to be displayed in the Presentation Interface
*Enter '''''Forecast Summary Mode'''''
|-
|
:''Date and Time Selector''
|
:Selection of Current Data Set within the Forecast Data Source
|}

===== Summary Mode =====
In Forecast Summary mode the Current Data Source Panel contains only the Data Source Divider - indicating the Current Data Set is drawn from a Forecast.

==== Scenario Data Source ====
When Scenario is selected as the Current Data Source, the text "''Data Source: Scenario''" is shown in the top left hand corner. Below this the Scenario name and version number is listed in a Grid. Located under the grid are buttons which can be used to:
*Enter Marginal Analysis Mode. In Scenario Marginal Analysis mode the Current Data Source Panel contains only the top line of text (i.e. "''Data Source: Scenario''") - indicating the Current Data Set is drawn from a Scenario.
*Redispatch the Scenario (after changing one or more '''''Dispatch Factors''''')
*Save the amended Scenario as new Version

=== Date and Time Selector ===

==== Purpose ====
To select the date and period of the Current Data Set for Market, Powerflow Case and Forecast Data Sources. This period is referred to as the 'Current Period'.


'''>> To Set the Current Date:'''
#Open the Calendar by clicking on the down-pointing arrow head in the '''Date Selector'''.
#Use the Calendar navigation features to select the day to become 'Current'

===== Calendar Features =====
*The current Month and Year is displayed in the blue header
*The current Month can be changed using the 'Previous' and 'Next' arrow keys in the blue header
*The current Day is highlighted with a blue ellipse
*A new current Day can be selected by clicking on the required date with the mouse
*The current day can be changed using the arrow keys on your keyboard. Using ''<page up/down>'' skips forward/back a whole month and ''<Ctrl><Page Up/Down>'' skips forward/back a whole year
*Clicking on the actual date (today's date) displayed at the foot of the calendar, causes the current day marker to move to this date.
*Clicking on the year displayed in the blue header area reveals an up and down arrow - clicking and holding on these arrows causes the current year to scroll backwards or forwards in time until the mouse button is released.
*Clicking on the month name in the blue header area reveals a drop-down list of months which can be used to select the current month

----
NOTE: It is also possible to alter the current date without invoking the Calendar, by highlighting the Day, Month and Year fields in the Date Selector and either typing the text you want or using the up/down arrow keys

===== Period Selection =====
The Current Period may be selected by:
*Clicking the required Trading Period number in the horizontal Period Selection Bar (the blue highlight indicates the currently selected Trading Period)
*Using the arrow keys in the Period Selection Roller
*Typing into the Trading Period text box in the Roller

== The View Manager ==
The View Manager is located directly beneath the '''''Current Data Source Panel'''''.

=== Purpose ===
A View is a pre-defined area of the Main Map which can be recalled to fit into the Main or a secondary Map Window. The View Manager allows you to create certain views of the Map and quickly return to these views simply by clicking on the required tab. Views can only be created through the Main Window View manager which is visible in the Main Window for all Data Sources (Market, Forecast, Powerflow Case and Scenario).


'''>> To create a new View:'''
#Use the [[EMO:The_Map#Map_Navigation|Map Navigation Features]] to position a section of the Main Map that you want to be able to recall in the Main Window Map Panel
#Click on a View name in the View Manager and press the <INSERT> Key to open the Add View dialogue
#Enter the name you wish to call the view and click 'OK' (The view name will now appear in the Views List in the View Manager)


'''>> To recall a previously created View in the Main Window Map Panel:'''
#Double-click a View name in the Views List


'''>> To recall a previously created View in a Secondary Map Window:'''
#Expand the Secondary Map View Selector (double arrow head in the top left corner)
#Select the required View from the second drop down box
#The selected View will now be displayed in the Secondary Map Window


'''>> To Delete a View:'''
#Highlight the View to be deleted in the Views list and press the <DELETE> Key
#Confirm the delete in the pop dialogue box
#The View will be removed from all View lists

== Trading Period Summary ==
[[File:Trading Period Summary.PNG|300px|thumb|right|Figure 2 - Example Trading Period Summary]]
=== Purpose ===
To display key indicator totals for the Current Data Source.

=== Items ===
{|class="wikitable"
! Data Item !! Unit !! Description (for the Current Period)
|-
|
:''Ave. Price''
|
:$/MWh
|
:Average of all Nodal Prices (the average is not load weighted) - always zero for Powerflow Case Data Sources
|-
|
:''Load''
|
:MW
|
:Total system demand
|-
|
:''Generation''
|
:MW
|
:Total system injection
|-
|
:''Losses''
|
:MW
|
:Difference between total injection and off-take
|-
|
:''Imbalance''
|
:MW
|
:The difference between load and generation (visible only for the Market Data Source to assist in identifying inconsistencies in input data)
|}

NOTE: When in Summary Mode the Current Trading Period Summary displays average values for the whole Forecast or Powerflow Case.

== The Data Source Manager ==
The '''''Data Source Manager''''' is located at the bottom of the Control Panel.

=== Definition ===
A '''''Data Source''''' determines the context for viewing Maps, Reports, Charts and Information Windows. There are four Data Source types:
#Data from the '''''Market'''''
#Data from a '''''Forecast'''''
#Data from a '''''Powerflow Case'''''
#Data from a created '''''Scenarios'''''

Access to Data Sources is handled through the Main Window Data Source Manager.

==== Features ====
{|class ="wikitable"
! Feature !! Description
|-
|
:''Browser''
|
:Tree type browser used to browse available Data Sources
|-
|
:''Function Panel''
|
:Panel of buttons which provide access to Data Source management functionality
|}

=== Managing the Market Data Source ===

==== Purpose ====
To provide historical Market data for viewing in the '''''[[EMO:The Presentation Interface|Presentation Interface]]''''' and '''''[[EMO:The_Edit_Menu#The_Reports_and_Graphs_Option|Reports]]'''''.

==== Usage ====

'''>> To place the Presentation Interface into Market Data Source mode and view Market Data:'''
#highlight "Market" in the Main Window Data Source Manager
#Click the View button or double-click on the highlighted "Market" text

Notes:
#Simply placing the Presentation Interface into Market Data Source Mode will not replace the Current Data Set with Market data
#''EMarketOffer'' launches with a Market Data Source using the actual calendar date and time.
#When switching to Market Data Source mode ''EMarketOffer'' takes the 'Current Date' from the previously loaded Data Source. For example if you were looking at a Forecast with an Effective Date Range some time in the future, switching to Market Data Source Mode and loading data will cause displays to go blank as EMarketOffer fails to find any historical data. Alternatively if you are in Scenario Data Source Mode and looking at a Scenario based on a historical period, switching to Market Data Source Mode will cause actual (historical) data for the date and period of the Scenario to be loaded.

=== Managing the Forecast Data Source ===

==== Purpose ====
To provide data from Forecast Runs for viewing in the '''''[[EMO:The Presentation Interface|Presentation Interface]]''''' and '''''[[EMO:The_Edit_Menu#The_Reports_and_Graphs_Option|Reports]]'''''.

==== Usage ====

'''>> To place the Presentation Interface into Forecast Data Source mode:'''
#highlight "Forecast" in the '''''[[EMO:Control_Panel_Components#The_Data_Source_Manager|Main Window Data Source Manager]]'''''

Unlike the Market Data Source which has only one discrete set of data for any given Trading Period, the Forecast Data Source provides access to the many discontinuous, discrete and potentially overlapping data sets produced by Forecast Runs.


'''>> To access the output of individual Forecast Runs:'''
#Place the Presentation Interface into Forecast Data Source Mode
#Click the expander box next to the Forecast Data Source header (marked '+' )
#Highlight the desired Forecast output from the expanded list
#Click the '''View button''' or Double-click the Forecast Definition name in the Data Source Manager

==== Features ====
{|class="wikitable"
! Feature !! Purpose
|-
|
:''Data Source Indicator''
|
:Shows the currently operative mode (Forecast) in the top left corner of the control panel
|-
|
:''View Button''
|
:Causes the Forecast data to be loaded into the Presentation Interface
|-
|
:''Create Button''
|
:Allows you to create a new Forecast Definition by opening a blank Forecast Definition Window
|}

When the Forecast Data Source browser is expanded and a single Forecast highlighted the following additional features are displayed in the control panel:
{|class="wikitable"
! Feature !! Purpose
|-
|
:''Data Source Indicator''
|
:Now shows both the Data Source mode and the name of the currently selected Forecast
|-
|
:''Delete Button''
|
:Allows you to delete the highlighted Forecast (this deletes the Forecast Definition and all associated output). You are required to confirm the delete through a dialogue box.
|-
|
:''Edit Button''
|
:Allows you to edit the highlighted Forecast Definition through the Forecast Definition Window
|}

NOTE: Simply placing the Presentation Interface into Forecast Data Source mode will not replace the currently loaded data with Forecast data.

=== Managing the Powerflow Data Source ===

==== Purpose ====
To provide data from Powerflow Case Analyses for viewing in the '''''[[EMO:The Presentation Interface|Presentation Interface]]''''' and '''''[[EMO:The_Edit_Menu#The_Reports_and_Graphs_Option|Reports]]'''''.

==== Usage ====

'''>> To place the Presentation Interface into Powerflow Case Data Source Mode:'''
#highlight "Powerflow" in the Main Window Data Source Manager

The Powerflow Case Data Source provides access to the many discontinuous, discrete and potentially overlapping data sets produced by Powerflow Case analysis.


'''>> To access the output of an individual Powerflow Case Analysis:'''
#Place the Presentation Interface into Powerflow Case Data Source Mode
#Click the expander box next to the Powerflow Case Data Source header (this is marked with a '+' sign)
#Highlight the desired Powerflow Case output from the expanded list
#Click the view button or double-click the highlighted Powerflow Case name

==== Features ====
{|class="wikitable"
! Feature !! Purpose
|-
|
:''Data Source Indicator''
|
:Shows the currently operative mode (Powerflow) in the top left corner of the control panel.
|-
|
:''View Button''
|
:Causes Powerflow data to be loaded into the Presentation Interface
|-
|
:''Create Button''
|
:Allows you to create a new Powerflow Case Definition by opening a blank Powerflow Case Definition Window
|}

When the Powerflow Case Data Source browser is expanded and a single Powerflow Case highlighted the following additional features are displayed in the control panel

{|class="wikitable"
! Feature !! Purpose
|-
|
:''Data Source Indicator''
|
:Now shows both the Data Source mode and the name of the currently selected Powerflow Case
|-
|
:''Delete Button''
|
:Allows you to delete the highlighted Powerflow Case (this deletes the Powerflow Case Definition and all associated output). You are required to confirm the delete through a dialogue box.
|-
|
:''Edit Button''
|
:Allows you to edit the highlighted Powerflow Case Definition through the Powerflow Case Definition Window
|}

NOTE: Simply placing the Presentation Interface into Powerflow Case Data Source mode will not replace the currently loaded data with Powerflow Case data.

=== Managing the Scenario Data Source ===

==== Purpose ====
To provide data from previously saved Scenarios for viewing in the '''''[[EMO:The Presentation Interface|Presentation Interface]]''''' and '''''[[EMO:The_Edit_Menu#The_Reports_and_Graphs_Option|Reports]]'''''.

==== Definition ====
A Scenario is a snapshot for a single Trading Period created from either a Forecast or Market Data Source.

==== Usage ====

'''>> To place the Presentation Interface into Scenario Data Source mode highlight "Scenario" in the Main Window Data Source Manager'''

The Scenario Data Source provides access to the many discrete, single-period Scenarios.


'''>> To access a Scenario:'''
#Place the Presentation Interface into Scenario Data Source Mode
#Click the expander box next to the Scenario Data Source header (this is marked with a '+' sign)
#Highlight the desired Scenario from the expanded list
#Click the '''View button''' or double-click the highlighted Scenario name

==== Features ====
{|class="wikitable"
! Feature !! Purpose
|-
|
:''Data Source Indicator''
|
:Shows the currently operative mode (Scenario) in the top left corner of the control panel
|-
|
:''View Button''
|
:Causes Scenario data to be loaded into the Presentation Interface
|-
|
:''Create Button''
|
:Allows you to create a new Scenario using the dispatch data for the currently displayed period
|}

When the Scenario Data Source browser is expanded and a single Scenario highlighted the following additional features are displayed in the control panel

{|class="wikitable"
! Feature !! Purpose
|-
|
:''Data Source Indicator''
|
:Now shows both the Data Source mode and the name of the currently selected Scenario
|-
|
:''Delete Button''
|
:Allows you to delete the highlighted Scenario. You are required to confirm the delete through a dialogue box.
|}

NOTES:
#Simply placing the Presentation Interface into Scenario Data Source mode will not replace the currently loaded data with Scenario data
#Because Scenarios apply to only one period on one date, the Current Date and Periods is set to match those of the Scenarios.
#Scenarios can be created from the following Data Sources:
##The Market Data Source providing historical offers exist for the Scenario period
##Any Forecast output
##Any Scenario that has been amended during an analysis session

== The Circuit Colouring Panel ==
The Cicuit Colouring Panel can, when applicable, be found beneath the View Manager in the Main Window Control Panel.

=== Purpose ===
To modify the use of coloured Circuits on any Main, Secondary or Inset map to help rapidly identify situations of interest in the Transmission System.

=== Loading View Mode ===
In Loading View mode circuits are colour-graded according to their loading. Lines with low loading percentages are coloured according to the colour selected in the '''''Map Settings''''' function. Typically the closer a Circuit's loading approaches its capacity the 'hotter' its colouring becomes (100% loaded circuits are typically coloured bright red).

NOTE: For the Market Data Source loading cannot be calculated with 100% certainty and therefore the circuit colouring is based on probable rather than actual loadings.

=== Constraint View Mode ===
In Constraint View Mode Circuits are coloured as selected in the '''''Map Settings''''' function, except for those that are constraining (100% of Capacity). These circuits are coloured bright red (also changeable through the Map Settings function).

NOTE: Accurate Identification of Constraints only occurs with the Forecast, Powerflow Case and Scenario Data Source in periods with a feasible dispatch.

=== Price Difference View Mode ===
In Price Difference View mode Circuits are colour graded according nodal price difference between From and To Nodes. The greater the price difference in the direction of flow (most likely due to a binding constraint) the warmer the colour will be relative to the standard circuit colour (large differences being displayed in bright red). In cases where a price difference is in the opposite direction to flow (most likely to occur with the spring washer effect) the cooler the circuit colour will be relative to the standard circuit colour (largest difference displayed in deep blue).

== The Infeasibilities Panel ==
The Infeasibilities Panel appears in the Control panel whenever the Current Data Set contains an infeasibility. The Panel contains a simple text string alerting you to the existence of an infeasibility. However, in Forecast/Powerflow Case Summary Mode the Panel will list all the periods in the summary date range in which an infeasibility occurs. For further discussion on interpretation of the messages in the Infeasibilities Panel see the section on '''''[[EMO:Infeasibilities|Infeasibilities]]'''''.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:The Control Panel|Back]]

Special:Badtitle/NS106:Creating a Powerflow Case Definition

2013-05-05T22:02:22Z

Greg: /* Editing Loaded Equation Constraint Data */

{{#hidens:}}

'''>> To create a Powerflow Case Definition:'''
#Place the '''''[[EMO:Control_Panel_Components#The_Data_Source_Manager|Data Sources Manager]]''''' in the Main Window into Powerflow Mode by highlighting the 'Powerflow' data source option
#Click the '''Create button''' at the foot of the Panel which opens the the '''''Powerflow Case Definition Window'''''

IMPORTANT: Equation Constraints are allowed in Powerflows, but they do not impact on the power flow in any way at all.
'''Equation Constraints are allowed in Powerflows so that you can see if their right hand side value is exceeded, and by how much, but they do not impact on the power flows. Power flows are determined only by the generation, demand, line impedances and swing nodes you choose.'''

=== Powerflow Case Steps ===
#Naming The Powerflow Case
#Selecting the data range for the Powerflow Case
#Loading and editing Demand and Generation data
#Loading and editing Transmission System data
#Selecting the Swing Node/s
#Running the Powerflow Case

== Naming a Powerflow Case ==
By default new Powerflow Cases are created with the name: '''_New_'''. If a Case of this name already exists a version number in parentheses is appended to the name.


'''>> To add or change the name of the Powerflow Case:'''
#Click on the '''Powerflow Name button''' on the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Rename Powerflow Window
#Type the new Powerflow Case name and click the '''OK button'''

== Selecting a Powerflow Case Date Range ==
Each Powerflow Case must be associated with an Effective Date Range. The Powerflow output will contain data for each Trading Period specified in the Effective Date Range.

NOTE: It is possible to create Powerflow Cases for historical as well as future dates.


'''>> To specify the Effective Date Range:'''
#Use the Date Selector to specify the date on which the Powerflow Case will start
#Use the Trading Period Selector to specify the starting Trading Period for the Powerflow Case
#Specify how many Trading Periods (from and include the starting period) you would like the Powerflow Case to cover

NOTES:
#''EMarketOffer'' uses the Effective Date Range as a default when loading input data into the Powerflow Case from database or file.
#The Powerflow Case works with a single week (seven-days) of input data, Powerflow Cases covering more that 336 periods (seVen-days) will re-cycle Demand and Generation data.

== Loading and Editing Demand and Generation Data ==

'''>> To load Demand and Generation data in to your Powerflow Case:'''
#Use the '''Data > Load Data''' option in the Menu bar of the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Load Data Window
#Use the '''Demand and Generation Data Panel''' to specify the details of the Demand and Generations data you wish to use.

NOTES:
#When loading Demand or Generation data from file ''EMarketOffer'' uses the date in the file name to establish the day of the week the data will be used for in the profile. Loading two files for a Wednesday means an average of the two days will be made for the weekly profile.
#It is possible to load partial files for a limited number of Trading Periods and/or Nodes. Data for the Trading Periods and Nodes in the partial file will overwrite existing data but leave other data in tact.

You can also load Demand and Generation data from previously prepared Demand or Generation Profile files using the '''Profiles > Demand''' or '''Profiles > Generation''' options in the menu of the Powerflow Case Definition Window.

Finally, you can:
*Load Demand data into the Definition one Node at a time through the Edit Node Data Grid accessed through the loaded data panel on the Powerflow Case Definition Window. Such loading can be achieved either manually or by cutting and pasting from another application such as Excel.
*Load Generation data on Units at a time through the Edit Unit Data Grid in the Powerflow Case Definition Window

=== Editing Loaded Demand and Generation Data ===
Demand data can be edited individually by Node using the '''''Edit Node Window''''' accessed through the loaded data panel on the Powerflow Case Definition Window (similar functionality can be used to edit loaded Generation data using the Edit Unit Data Grid).

Individual Demand figures can be edited manually or multiple cells can be changed by pasting into a highlighted section of the grid from the clipboard. You can:
*Replace all of the existing profile by re-loading from the database
*Use edited demand files to replace all or part of the existing Demand profile.

NOTE: Data pasted into the Demand Grid overwrites existing data as soon as it is pasted.

TIP: You can use the Graph Nodal Demand profile feature (Graph Button on the Edit Node Data Grid) to make a quick visual check on changes you are making to the Nodal Demand profile).

== Loading and Editing Transmission System Data ==

=== Loading Transmission Data ===

'''>> To load Transmission data into your Powerflow Case Definition:'''
#Use the '''Data > Load Data''' option in the Menu bar of the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Load Data Window
#Use the '''Load Transmission Data Panel''' to specify the details of the Transmission data you wish to use

Tip: Remember to select a data range for the Transmission System data that fully covers the Powerflow Case Definition Effective Date Range.

Finally you can load Circuit and Equation Constraint data into the Powerflow Case Definition one Circuit and Equation at a time through the '''''Edit Circuits '''''and '''''Edit Equations Information Windows''''' accessed through the loaded data panel on the Powerflow Case Definition Window. This can be achieved either manually or by cutting and pasting from another application such as Excel.

=== Editing Loaded Circuit Data ===
Data for individual Circuits can be edited using the '''''Edit Circuit Information Window''''' accessed by double-clicking a circuit in the loaded circuit data panel on the Powerflow Case Definition Window.

=== Editing Loaded Equation Constraint Data ===

IMPORTANT: Equation Constraints are allowed in Powerflows, but they do not impact on the power flow in any way at all.
'''Equation Constraints are allowed in Powerflows so that you can see if their right hand side value is exceeded, and by how much, but they do not impact on the power flows. Power flows are determined only by the generation, demand, line impedances and swing nodes you choose.'''

Equation Constraint data can be edited using the '''''Edit Equation Constraint Information Window''''' accessed by double-clicking an equation in the loaded equations data panel on the Powerflow Case Definition Window.

== Selecting Swing Nodes ==
The final step before running the Powerflow Analysis is to select one or more Swing Nodes to be used by the Powerflow model for allocating unmatched Demand.

Swing Nodes are selected through the '''''Swing Node Data Grid''''' in the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]].'''''

NOTE: it is possible to run a Powerflow Case without specifying a Swing Node, however the Infeasibilities Sub-Panel in the Control Panel of the Main Window will display the following message when viewing the results: '''"Unable to find Swing Node(s)"'''

== Running a Powerflow Case ==

'''>> To run the definition to produce Powerflow outputs:'''
#Click on the '''Run Powerflow button''' in the '''''Powerflow Case Definition Window.'''''

Initiating a Run opens the Run Progress Pop-up Window, which shows how many Powerflow Case periods have so far been analysed. You can use the '''Cancel button''' to halt the Powerflow Run at any time. Output calculated by the Run up until the time of cancellation can be viewed via the various output viewers.

NOTE: On completion the '''''[[EMO:The Main Window|Main Window]]''''' is immediately set to Powerflow '''''Data Source''''' mode and shows data from the first period in the Powerflow Case.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Powerflow Analysis|Back]]

Special:Badtitle/NS106:Creating a Powerflow Case Definition

2013-05-05T22:01:54Z

Greg:

{{#hidens:}}

'''>> To create a Powerflow Case Definition:'''
#Place the '''''[[EMO:Control_Panel_Components#The_Data_Source_Manager|Data Sources Manager]]''''' in the Main Window into Powerflow Mode by highlighting the 'Powerflow' data source option
#Click the '''Create button''' at the foot of the Panel which opens the the '''''Powerflow Case Definition Window'''''

IMPORTANT: Equation Constraints are allowed in Powerflows, but they do not impact on the power flow in any way at all.
'''Equation Constraints are allowed in Powerflows so that you can see if their right hand side value is exceeded, and by how much, but they do not impact on the power flows. Power flows are determined only by the generation, demand, line impedances and swing nodes you choose.'''

=== Powerflow Case Steps ===
#Naming The Powerflow Case
#Selecting the data range for the Powerflow Case
#Loading and editing Demand and Generation data
#Loading and editing Transmission System data
#Selecting the Swing Node/s
#Running the Powerflow Case

== Naming a Powerflow Case ==
By default new Powerflow Cases are created with the name: '''_New_'''. If a Case of this name already exists a version number in parentheses is appended to the name.


'''>> To add or change the name of the Powerflow Case:'''
#Click on the '''Powerflow Name button''' on the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Rename Powerflow Window
#Type the new Powerflow Case name and click the '''OK button'''

== Selecting a Powerflow Case Date Range ==
Each Powerflow Case must be associated with an Effective Date Range. The Powerflow output will contain data for each Trading Period specified in the Effective Date Range.

NOTE: It is possible to create Powerflow Cases for historical as well as future dates.


'''>> To specify the Effective Date Range:'''
#Use the Date Selector to specify the date on which the Powerflow Case will start
#Use the Trading Period Selector to specify the starting Trading Period for the Powerflow Case
#Specify how many Trading Periods (from and include the starting period) you would like the Powerflow Case to cover

NOTES:
#''EMarketOffer'' uses the Effective Date Range as a default when loading input data into the Powerflow Case from database or file.
#The Powerflow Case works with a single week (seven-days) of input data, Powerflow Cases covering more that 336 periods (seVen-days) will re-cycle Demand and Generation data.

== Loading and Editing Demand and Generation Data ==

'''>> To load Demand and Generation data in to your Powerflow Case:'''
#Use the '''Data > Load Data''' option in the Menu bar of the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Load Data Window
#Use the '''Demand and Generation Data Panel''' to specify the details of the Demand and Generations data you wish to use.

NOTES:
#When loading Demand or Generation data from file ''EMarketOffer'' uses the date in the file name to establish the day of the week the data will be used for in the profile. Loading two files for a Wednesday means an average of the two days will be made for the weekly profile.
#It is possible to load partial files for a limited number of Trading Periods and/or Nodes. Data for the Trading Periods and Nodes in the partial file will overwrite existing data but leave other data in tact.

You can also load Demand and Generation data from previously prepared Demand or Generation Profile files using the '''Profiles > Demand''' or '''Profiles > Generation''' options in the menu of the Powerflow Case Definition Window.

Finally, you can:
*Load Demand data into the Definition one Node at a time through the Edit Node Data Grid accessed through the loaded data panel on the Powerflow Case Definition Window. Such loading can be achieved either manually or by cutting and pasting from another application such as Excel.
*Load Generation data on Units at a time through the Edit Unit Data Grid in the Powerflow Case Definition Window

=== Editing Loaded Demand and Generation Data ===
Demand data can be edited individually by Node using the '''''Edit Node Window''''' accessed through the loaded data panel on the Powerflow Case Definition Window (similar functionality can be used to edit loaded Generation data using the Edit Unit Data Grid).

Individual Demand figures can be edited manually or multiple cells can be changed by pasting into a highlighted section of the grid from the clipboard. You can:
*Replace all of the existing profile by re-loading from the database
*Use edited demand files to replace all or part of the existing Demand profile.

NOTE: Data pasted into the Demand Grid overwrites existing data as soon as it is pasted.

TIP: You can use the Graph Nodal Demand profile feature (Graph Button on the Edit Node Data Grid) to make a quick visual check on changes you are making to the Nodal Demand profile).

== Loading and Editing Transmission System Data ==

=== Loading Transmission Data ===

'''>> To load Transmission data into your Powerflow Case Definition:'''
#Use the '''Data > Load Data''' option in the Menu bar of the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Load Data Window
#Use the '''Load Transmission Data Panel''' to specify the details of the Transmission data you wish to use

Tip: Remember to select a data range for the Transmission System data that fully covers the Powerflow Case Definition Effective Date Range.

Finally you can load Circuit and Equation Constraint data into the Powerflow Case Definition one Circuit and Equation at a time through the '''''Edit Circuits '''''and '''''Edit Equations Information Windows''''' accessed through the loaded data panel on the Powerflow Case Definition Window. This can be achieved either manually or by cutting and pasting from another application such as Excel.

=== Editing Loaded Circuit Data ===
Data for individual Circuits can be edited using the '''''Edit Circuit Information Window''''' accessed by double-clicking a circuit in the loaded circuit data panel on the Powerflow Case Definition Window.

=== Editing Loaded Equation Constraint Data ===
Equation Constraint data can be edited using the '''''Edit Equation Constraint Information Window''''' accessed by double-clicking an equation in the loaded equations data panel on the Powerflow Case Definition Window.

== Selecting Swing Nodes ==
The final step before running the Powerflow Analysis is to select one or more Swing Nodes to be used by the Powerflow model for allocating unmatched Demand.

Swing Nodes are selected through the '''''Swing Node Data Grid''''' in the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]].'''''

NOTE: it is possible to run a Powerflow Case without specifying a Swing Node, however the Infeasibilities Sub-Panel in the Control Panel of the Main Window will display the following message when viewing the results: '''"Unable to find Swing Node(s)"'''

== Running a Powerflow Case ==

'''>> To run the definition to produce Powerflow outputs:'''
#Click on the '''Run Powerflow button''' in the '''''Powerflow Case Definition Window.'''''

Initiating a Run opens the Run Progress Pop-up Window, which shows how many Powerflow Case periods have so far been analysed. You can use the '''Cancel button''' to halt the Powerflow Run at any time. Output calculated by the Run up until the time of cancellation can be viewed via the various output viewers.

NOTE: On completion the '''''[[EMO:The Main Window|Main Window]]''''' is immediately set to Powerflow '''''Data Source''''' mode and shows data from the first period in the Powerflow Case.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Powerflow Analysis|Back]]

Special:Badtitle/NS106:Creating a Powerflow Case Definition

2013-05-05T22:01:23Z

Greg:

{{#hidens:}}

'''>> To create a Powerflow Case Definition:'''
#Place the '''''[[EMO:Control_Panel_Components#The_Data_Source_Manager|Data Sources Manager]]''''' in the Main Window into Powerflow Mode by highlighting the 'Powerflow' data source option
#Click the '''Create button''' at the foot of the Panel which opens the the '''''Powerflow Case Definition Window'''''

IMPORTANT: Equation Constraints are allowed in Powerflows, but they do not impact on the power flow in any way at all.
'''Equation COnstraints are allowed in Powerflows so that you can see if their right hand side value is exceeded, and by how much, but they do not impact on the power flows. Power flows are determined only by the generation, demand, line impedances and swing nodes you choose.'''

=== Powerflow Case Steps ===
#Naming The Powerflow Case
#Selecting the data range for the Powerflow Case
#Loading and editing Demand and Generation data
#Loading and editing Transmission System data
#Selecting the Swing Node/s
#Running the Powerflow Case

== Naming a Powerflow Case ==
By default new Powerflow Cases are created with the name: '''_New_'''. If a Case of this name already exists a version number in parentheses is appended to the name.


'''>> To add or change the name of the Powerflow Case:'''
#Click on the '''Powerflow Name button''' on the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Rename Powerflow Window
#Type the new Powerflow Case name and click the '''OK button'''

== Selecting a Powerflow Case Date Range ==
Each Powerflow Case must be associated with an Effective Date Range. The Powerflow output will contain data for each Trading Period specified in the Effective Date Range.

NOTE: It is possible to create Powerflow Cases for historical as well as future dates.


'''>> To specify the Effective Date Range:'''
#Use the Date Selector to specify the date on which the Powerflow Case will start
#Use the Trading Period Selector to specify the starting Trading Period for the Powerflow Case
#Specify how many Trading Periods (from and include the starting period) you would like the Powerflow Case to cover

NOTES:
#''EMarketOffer'' uses the Effective Date Range as a default when loading input data into the Powerflow Case from database or file.
#The Powerflow Case works with a single week (seven-days) of input data, Powerflow Cases covering more that 336 periods (seVen-days) will re-cycle Demand and Generation data.

== Loading and Editing Demand and Generation Data ==

'''>> To load Demand and Generation data in to your Powerflow Case:'''
#Use the '''Data > Load Data''' option in the Menu bar of the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Load Data Window
#Use the '''Demand and Generation Data Panel''' to specify the details of the Demand and Generations data you wish to use.

NOTES:
#When loading Demand or Generation data from file ''EMarketOffer'' uses the date in the file name to establish the day of the week the data will be used for in the profile. Loading two files for a Wednesday means an average of the two days will be made for the weekly profile.
#It is possible to load partial files for a limited number of Trading Periods and/or Nodes. Data for the Trading Periods and Nodes in the partial file will overwrite existing data but leave other data in tact.

You can also load Demand and Generation data from previously prepared Demand or Generation Profile files using the '''Profiles > Demand''' or '''Profiles > Generation''' options in the menu of the Powerflow Case Definition Window.

Finally, you can:
*Load Demand data into the Definition one Node at a time through the Edit Node Data Grid accessed through the loaded data panel on the Powerflow Case Definition Window. Such loading can be achieved either manually or by cutting and pasting from another application such as Excel.
*Load Generation data on Units at a time through the Edit Unit Data Grid in the Powerflow Case Definition Window

=== Editing Loaded Demand and Generation Data ===
Demand data can be edited individually by Node using the '''''Edit Node Window''''' accessed through the loaded data panel on the Powerflow Case Definition Window (similar functionality can be used to edit loaded Generation data using the Edit Unit Data Grid).

Individual Demand figures can be edited manually or multiple cells can be changed by pasting into a highlighted section of the grid from the clipboard. You can:
*Replace all of the existing profile by re-loading from the database
*Use edited demand files to replace all or part of the existing Demand profile.

NOTE: Data pasted into the Demand Grid overwrites existing data as soon as it is pasted.

TIP: You can use the Graph Nodal Demand profile feature (Graph Button on the Edit Node Data Grid) to make a quick visual check on changes you are making to the Nodal Demand profile).

== Loading and Editing Transmission System Data ==

=== Loading Transmission Data ===

'''>> To load Transmission data into your Powerflow Case Definition:'''
#Use the '''Data > Load Data''' option in the Menu bar of the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Load Data Window
#Use the '''Load Transmission Data Panel''' to specify the details of the Transmission data you wish to use

Tip: Remember to select a data range for the Transmission System data that fully covers the Powerflow Case Definition Effective Date Range.

Finally you can load Circuit and Equation Constraint data into the Powerflow Case Definition one Circuit and Equation at a time through the '''''Edit Circuits '''''and '''''Edit Equations Information Windows''''' accessed through the loaded data panel on the Powerflow Case Definition Window. This can be achieved either manually or by cutting and pasting from another application such as Excel.

=== Editing Loaded Circuit Data ===
Data for individual Circuits can be edited using the '''''Edit Circuit Information Window''''' accessed by double-clicking a circuit in the loaded circuit data panel on the Powerflow Case Definition Window.

=== Editing Loaded Equation Constraint Data ===
Equation Constraint data can be edited using the '''''Edit Equation Constraint Information Window''''' accessed by double-clicking an equation in the loaded equations data panel on the Powerflow Case Definition Window.

== Selecting Swing Nodes ==
The final step before running the Powerflow Analysis is to select one or more Swing Nodes to be used by the Powerflow model for allocating unmatched Demand.

Swing Nodes are selected through the '''''Swing Node Data Grid''''' in the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]].'''''

NOTE: it is possible to run a Powerflow Case without specifying a Swing Node, however the Infeasibilities Sub-Panel in the Control Panel of the Main Window will display the following message when viewing the results: '''"Unable to find Swing Node(s)"'''

== Running a Powerflow Case ==

'''>> To run the definition to produce Powerflow outputs:'''
#Click on the '''Run Powerflow button''' in the '''''Powerflow Case Definition Window.'''''

Initiating a Run opens the Run Progress Pop-up Window, which shows how many Powerflow Case periods have so far been analysed. You can use the '''Cancel button''' to halt the Powerflow Run at any time. Output calculated by the Run up until the time of cancellation can be viewed via the various output viewers.

NOTE: On completion the '''''[[EMO:The Main Window|Main Window]]''''' is immediately set to Powerflow '''''Data Source''''' mode and shows data from the first period in the Powerflow Case.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Powerflow Analysis|Back]]

Special:Badtitle/NS106:Creating a Powerflow Case Definition

2013-05-05T21:59:58Z

Greg:

{{#hidens:}}

'''>> To create a Powerflow Case Definition:'''
#Place the '''''[[EMO:Control_Panel_Components#The_Data_Source_Manager|Data Sources Manager]]''''' in the Main Window into Powerflow Mode by highlighting the 'Powerflow' data source option
#Click the '''Create button''' at the foot of the Panel which opens the the '''''Powerflow Case Definition Window'''''

IMPORTANT: Equation Constraints are allowed in Powerflows, but they do not impact on the power flow in any way at all.

=== Powerflow Case Steps ===
#Naming The Powerflow Case
#Selecting the data range for the Powerflow Case
#Loading and editing Demand and Generation data
#Loading and editing Transmission System data
#Selecting the Swing Node/s
#Running the Powerflow Case

== Naming a Powerflow Case ==
By default new Powerflow Cases are created with the name: '''_New_'''. If a Case of this name already exists a version number in parentheses is appended to the name.


'''>> To add or change the name of the Powerflow Case:'''
#Click on the '''Powerflow Name button''' on the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Rename Powerflow Window
#Type the new Powerflow Case name and click the '''OK button'''

== Selecting a Powerflow Case Date Range ==
Each Powerflow Case must be associated with an Effective Date Range. The Powerflow output will contain data for each Trading Period specified in the Effective Date Range.

NOTE: It is possible to create Powerflow Cases for historical as well as future dates.


'''>> To specify the Effective Date Range:'''
#Use the Date Selector to specify the date on which the Powerflow Case will start
#Use the Trading Period Selector to specify the starting Trading Period for the Powerflow Case
#Specify how many Trading Periods (from and include the starting period) you would like the Powerflow Case to cover

NOTES:
#''EMarketOffer'' uses the Effective Date Range as a default when loading input data into the Powerflow Case from database or file.
#The Powerflow Case works with a single week (seven-days) of input data, Powerflow Cases covering more that 336 periods (seVen-days) will re-cycle Demand and Generation data.

== Loading and Editing Demand and Generation Data ==

'''>> To load Demand and Generation data in to your Powerflow Case:'''
#Use the '''Data > Load Data''' option in the Menu bar of the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Load Data Window
#Use the '''Demand and Generation Data Panel''' to specify the details of the Demand and Generations data you wish to use.

NOTES:
#When loading Demand or Generation data from file ''EMarketOffer'' uses the date in the file name to establish the day of the week the data will be used for in the profile. Loading two files for a Wednesday means an average of the two days will be made for the weekly profile.
#It is possible to load partial files for a limited number of Trading Periods and/or Nodes. Data for the Trading Periods and Nodes in the partial file will overwrite existing data but leave other data in tact.

You can also load Demand and Generation data from previously prepared Demand or Generation Profile files using the '''Profiles > Demand''' or '''Profiles > Generation''' options in the menu of the Powerflow Case Definition Window.

Finally, you can:
*Load Demand data into the Definition one Node at a time through the Edit Node Data Grid accessed through the loaded data panel on the Powerflow Case Definition Window. Such loading can be achieved either manually or by cutting and pasting from another application such as Excel.
*Load Generation data on Units at a time through the Edit Unit Data Grid in the Powerflow Case Definition Window

=== Editing Loaded Demand and Generation Data ===
Demand data can be edited individually by Node using the '''''Edit Node Window''''' accessed through the loaded data panel on the Powerflow Case Definition Window (similar functionality can be used to edit loaded Generation data using the Edit Unit Data Grid).

Individual Demand figures can be edited manually or multiple cells can be changed by pasting into a highlighted section of the grid from the clipboard. You can:
*Replace all of the existing profile by re-loading from the database
*Use edited demand files to replace all or part of the existing Demand profile.

NOTE: Data pasted into the Demand Grid overwrites existing data as soon as it is pasted.

TIP: You can use the Graph Nodal Demand profile feature (Graph Button on the Edit Node Data Grid) to make a quick visual check on changes you are making to the Nodal Demand profile).

== Loading and Editing Transmission System Data ==

=== Loading Transmission Data ===

'''>> To load Transmission data into your Powerflow Case Definition:'''
#Use the '''Data > Load Data''' option in the Menu bar of the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Load Data Window
#Use the '''Load Transmission Data Panel''' to specify the details of the Transmission data you wish to use

Tip: Remember to select a data range for the Transmission System data that fully covers the Powerflow Case Definition Effective Date Range.

Finally you can load Circuit and Equation Constraint data into the Powerflow Case Definition one Circuit and Equation at a time through the '''''Edit Circuits '''''and '''''Edit Equations Information Windows''''' accessed through the loaded data panel on the Powerflow Case Definition Window. This can be achieved either manually or by cutting and pasting from another application such as Excel.

=== Editing Loaded Circuit Data ===
Data for individual Circuits can be edited using the '''''Edit Circuit Information Window''''' accessed by double-clicking a circuit in the loaded circuit data panel on the Powerflow Case Definition Window.

=== Editing Loaded Equation Constraint Data ===
Equation Constraint data can be edited using the '''''Edit Equation Constraint Information Window''''' accessed by double-clicking an equation in the loaded equations data panel on the Powerflow Case Definition Window.

== Selecting Swing Nodes ==
The final step before running the Powerflow Analysis is to select one or more Swing Nodes to be used by the Powerflow model for allocating unmatched Demand.

Swing Nodes are selected through the '''''Swing Node Data Grid''''' in the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]].'''''

NOTE: it is possible to run a Powerflow Case without specifying a Swing Node, however the Infeasibilities Sub-Panel in the Control Panel of the Main Window will display the following message when viewing the results: '''"Unable to find Swing Node(s)"'''

== Running a Powerflow Case ==

'''>> To run the definition to produce Powerflow outputs:'''
#Click on the '''Run Powerflow button''' in the '''''Powerflow Case Definition Window.'''''

Initiating a Run opens the Run Progress Pop-up Window, which shows how many Powerflow Case periods have so far been analysed. You can use the '''Cancel button''' to halt the Powerflow Run at any time. Output calculated by the Run up until the time of cancellation can be viewed via the various output viewers.

NOTE: On completion the '''''[[EMO:The Main Window|Main Window]]''''' is immediately set to Powerflow '''''Data Source''''' mode and shows data from the first period in the Powerflow Case.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Powerflow Analysis|Back]]

Special:Badtitle/NS106:Creating a Powerflow Case Definition

2013-05-05T21:58:27Z

Greg:

{{#hidens:}}

'''>> To create a Powerflow Case Definition:'''
#Place the '''''[[EMO:Control_Panel_Components#The_Data_Source_Manager|Data Sources Manager]]''''' in the Main Window into Powerflow Mode by highlighting the 'Powerflow' data source option
#Click the '''Create button''' at the foot of the Panel which opens the the '''''Powerflow Case Definition Window'''''

IMPORTANT: To avoid confusion, please note that you can load and edit Equation Constraints in Powerflows,
but they do not impact on the power flow in any way at all. Equation Constraints are shown only so you can see if they are exceeded and by how much.

=== Powerflow Case Steps ===
#Naming The Powerflow Case
#Selecting the data range for the Powerflow Case
#Loading and editing Demand and Generation data
#Loading and editing Transmission System data
#Selecting the Swing Node/s
#Running the Powerflow Case

== Naming a Powerflow Case ==
By default new Powerflow Cases are created with the name: '''_New_'''. If a Case of this name already exists a version number in parentheses is appended to the name.


'''>> To add or change the name of the Powerflow Case:'''
#Click on the '''Powerflow Name button''' on the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Rename Powerflow Window
#Type the new Powerflow Case name and click the '''OK button'''

== Selecting a Powerflow Case Date Range ==
Each Powerflow Case must be associated with an Effective Date Range. The Powerflow output will contain data for each Trading Period specified in the Effective Date Range.

NOTE: It is possible to create Powerflow Cases for historical as well as future dates.


'''>> To specify the Effective Date Range:'''
#Use the Date Selector to specify the date on which the Powerflow Case will start
#Use the Trading Period Selector to specify the starting Trading Period for the Powerflow Case
#Specify how many Trading Periods (from and include the starting period) you would like the Powerflow Case to cover

NOTES:
#''EMarketOffer'' uses the Effective Date Range as a default when loading input data into the Powerflow Case from database or file.
#The Powerflow Case works with a single week (seven-days) of input data, Powerflow Cases covering more that 336 periods (seVen-days) will re-cycle Demand and Generation data.

== Loading and Editing Demand and Generation Data ==

'''>> To load Demand and Generation data in to your Powerflow Case:'''
#Use the '''Data > Load Data''' option in the Menu bar of the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Load Data Window
#Use the '''Demand and Generation Data Panel''' to specify the details of the Demand and Generations data you wish to use.

NOTES:
#When loading Demand or Generation data from file ''EMarketOffer'' uses the date in the file name to establish the day of the week the data will be used for in the profile. Loading two files for a Wednesday means an average of the two days will be made for the weekly profile.
#It is possible to load partial files for a limited number of Trading Periods and/or Nodes. Data for the Trading Periods and Nodes in the partial file will overwrite existing data but leave other data in tact.

You can also load Demand and Generation data from previously prepared Demand or Generation Profile files using the '''Profiles > Demand''' or '''Profiles > Generation''' options in the menu of the Powerflow Case Definition Window.

Finally, you can:
*Load Demand data into the Definition one Node at a time through the Edit Node Data Grid accessed through the loaded data panel on the Powerflow Case Definition Window. Such loading can be achieved either manually or by cutting and pasting from another application such as Excel.
*Load Generation data on Units at a time through the Edit Unit Data Grid in the Powerflow Case Definition Window

=== Editing Loaded Demand and Generation Data ===
Demand data can be edited individually by Node using the '''''Edit Node Window''''' accessed through the loaded data panel on the Powerflow Case Definition Window (similar functionality can be used to edit loaded Generation data using the Edit Unit Data Grid).

Individual Demand figures can be edited manually or multiple cells can be changed by pasting into a highlighted section of the grid from the clipboard. You can:
*Replace all of the existing profile by re-loading from the database
*Use edited demand files to replace all or part of the existing Demand profile.

NOTE: Data pasted into the Demand Grid overwrites existing data as soon as it is pasted.

TIP: You can use the Graph Nodal Demand profile feature (Graph Button on the Edit Node Data Grid) to make a quick visual check on changes you are making to the Nodal Demand profile).

== Loading and Editing Transmission System Data ==

=== Loading Transmission Data ===

'''>> To load Transmission data into your Powerflow Case Definition:'''
#Use the '''Data > Load Data''' option in the Menu bar of the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Load Data Window
#Use the '''Load Transmission Data Panel''' to specify the details of the Transmission data you wish to use

Tip: Remember to select a data range for the Transmission System data that fully covers the Powerflow Case Definition Effective Date Range.

Finally you can load Circuit and Equation Constraint data into the Powerflow Case Definition one Circuit and Equation at a time through the '''''Edit Circuits '''''and '''''Edit Equations Information Windows''''' accessed through the loaded data panel on the Powerflow Case Definition Window. This can be achieved either manually or by cutting and pasting from another application such as Excel.

=== Editing Loaded Circuit Data ===
Data for individual Circuits can be edited using the '''''Edit Circuit Information Window''''' accessed by double-clicking a circuit in the loaded circuit data panel on the Powerflow Case Definition Window.

=== Editing Loaded Equation Constraint Data ===
Equation Constraint data can be edited using the '''''Edit Equation Constraint Information Window''''' accessed by double-clicking an equation in the loaded equations data panel on the Powerflow Case Definition Window.

== Selecting Swing Nodes ==
The final step before running the Powerflow Analysis is to select one or more Swing Nodes to be used by the Powerflow model for allocating unmatched Demand.

Swing Nodes are selected through the '''''Swing Node Data Grid''''' in the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]].'''''

NOTE: it is possible to run a Powerflow Case without specifying a Swing Node, however the Infeasibilities Sub-Panel in the Control Panel of the Main Window will display the following message when viewing the results: '''"Unable to find Swing Node(s)"'''

== Running a Powerflow Case ==

'''>> To run the definition to produce Powerflow outputs:'''
#Click on the '''Run Powerflow button''' in the '''''Powerflow Case Definition Window.'''''

Initiating a Run opens the Run Progress Pop-up Window, which shows how many Powerflow Case periods have so far been analysed. You can use the '''Cancel button''' to halt the Powerflow Run at any time. Output calculated by the Run up until the time of cancellation can be viewed via the various output viewers.

NOTE: On completion the '''''[[EMO:The Main Window|Main Window]]''''' is immediately set to Powerflow '''''Data Source''''' mode and shows data from the first period in the Powerflow Case.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Powerflow Analysis|Back]]

Special:Badtitle/NS106:Creating a Powerflow Case Definition

2013-05-05T21:58:12Z

Greg: /* Powerflow Case Steps */

{{#hidens:}}

'''>> To create a Powerflow Case Definition:'''
#Place the '''''[[EMO:Control_Panel_Components#The_Data_Source_Manager|Data Sources Manager]]''''' in the Main Window into Powerflow Mode by highlighting the 'Powerflow' data source option
#Click the '''Create button''' at the foot of the Panel which opens the the '''''Powerflow Case Definition Window'''''

=== Powerflow Case Steps ===
#Naming The Powerflow Case
#Selecting the data range for the Powerflow Case
#Loading and editing Demand and Generation data
#Loading and editing Transmission System data
#Selecting the Swing Node/s
#Running the Powerflow Case

== Naming a Powerflow Case ==
By default new Powerflow Cases are created with the name: '''_New_'''. If a Case of this name already exists a version number in parentheses is appended to the name.


'''>> To add or change the name of the Powerflow Case:'''
#Click on the '''Powerflow Name button''' on the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Rename Powerflow Window
#Type the new Powerflow Case name and click the '''OK button'''

== Selecting a Powerflow Case Date Range ==
Each Powerflow Case must be associated with an Effective Date Range. The Powerflow output will contain data for each Trading Period specified in the Effective Date Range.

NOTE: It is possible to create Powerflow Cases for historical as well as future dates.


'''>> To specify the Effective Date Range:'''
#Use the Date Selector to specify the date on which the Powerflow Case will start
#Use the Trading Period Selector to specify the starting Trading Period for the Powerflow Case
#Specify how many Trading Periods (from and include the starting period) you would like the Powerflow Case to cover

NOTES:
#''EMarketOffer'' uses the Effective Date Range as a default when loading input data into the Powerflow Case from database or file.
#The Powerflow Case works with a single week (seven-days) of input data, Powerflow Cases covering more that 336 periods (seVen-days) will re-cycle Demand and Generation data.

== Loading and Editing Demand and Generation Data ==

'''>> To load Demand and Generation data in to your Powerflow Case:'''
#Use the '''Data > Load Data''' option in the Menu bar of the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Load Data Window
#Use the '''Demand and Generation Data Panel''' to specify the details of the Demand and Generations data you wish to use.

NOTES:
#When loading Demand or Generation data from file ''EMarketOffer'' uses the date in the file name to establish the day of the week the data will be used for in the profile. Loading two files for a Wednesday means an average of the two days will be made for the weekly profile.
#It is possible to load partial files for a limited number of Trading Periods and/or Nodes. Data for the Trading Periods and Nodes in the partial file will overwrite existing data but leave other data in tact.

You can also load Demand and Generation data from previously prepared Demand or Generation Profile files using the '''Profiles > Demand''' or '''Profiles > Generation''' options in the menu of the Powerflow Case Definition Window.

Finally, you can:
*Load Demand data into the Definition one Node at a time through the Edit Node Data Grid accessed through the loaded data panel on the Powerflow Case Definition Window. Such loading can be achieved either manually or by cutting and pasting from another application such as Excel.
*Load Generation data on Units at a time through the Edit Unit Data Grid in the Powerflow Case Definition Window

=== Editing Loaded Demand and Generation Data ===
Demand data can be edited individually by Node using the '''''Edit Node Window''''' accessed through the loaded data panel on the Powerflow Case Definition Window (similar functionality can be used to edit loaded Generation data using the Edit Unit Data Grid).

Individual Demand figures can be edited manually or multiple cells can be changed by pasting into a highlighted section of the grid from the clipboard. You can:
*Replace all of the existing profile by re-loading from the database
*Use edited demand files to replace all or part of the existing Demand profile.

NOTE: Data pasted into the Demand Grid overwrites existing data as soon as it is pasted.

TIP: You can use the Graph Nodal Demand profile feature (Graph Button on the Edit Node Data Grid) to make a quick visual check on changes you are making to the Nodal Demand profile).

== Loading and Editing Transmission System Data ==

=== Loading Transmission Data ===

'''>> To load Transmission data into your Powerflow Case Definition:'''
#Use the '''Data > Load Data''' option in the Menu bar of the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Load Data Window
#Use the '''Load Transmission Data Panel''' to specify the details of the Transmission data you wish to use

Tip: Remember to select a data range for the Transmission System data that fully covers the Powerflow Case Definition Effective Date Range.

Finally you can load Circuit and Equation Constraint data into the Powerflow Case Definition one Circuit and Equation at a time through the '''''Edit Circuits '''''and '''''Edit Equations Information Windows''''' accessed through the loaded data panel on the Powerflow Case Definition Window. This can be achieved either manually or by cutting and pasting from another application such as Excel.

=== Editing Loaded Circuit Data ===
Data for individual Circuits can be edited using the '''''Edit Circuit Information Window''''' accessed by double-clicking a circuit in the loaded circuit data panel on the Powerflow Case Definition Window.

=== Editing Loaded Equation Constraint Data ===
Equation Constraint data can be edited using the '''''Edit Equation Constraint Information Window''''' accessed by double-clicking an equation in the loaded equations data panel on the Powerflow Case Definition Window.

== Selecting Swing Nodes ==
The final step before running the Powerflow Analysis is to select one or more Swing Nodes to be used by the Powerflow model for allocating unmatched Demand.

Swing Nodes are selected through the '''''Swing Node Data Grid''''' in the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]].'''''

NOTE: it is possible to run a Powerflow Case without specifying a Swing Node, however the Infeasibilities Sub-Panel in the Control Panel of the Main Window will display the following message when viewing the results: '''"Unable to find Swing Node(s)"'''

== Running a Powerflow Case ==

'''>> To run the definition to produce Powerflow outputs:'''
#Click on the '''Run Powerflow button''' in the '''''Powerflow Case Definition Window.'''''

Initiating a Run opens the Run Progress Pop-up Window, which shows how many Powerflow Case periods have so far been analysed. You can use the '''Cancel button''' to halt the Powerflow Run at any time. Output calculated by the Run up until the time of cancellation can be viewed via the various output viewers.

NOTE: On completion the '''''[[EMO:The Main Window|Main Window]]''''' is immediately set to Powerflow '''''Data Source''''' mode and shows data from the first period in the Powerflow Case.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Powerflow Analysis|Back]]

Special:Badtitle/NS106:Creating a Powerflow Case Definition

2013-05-05T21:57:52Z

Greg: /* Powerflow Case Steps */

{{#hidens:}}

'''>> To create a Powerflow Case Definition:'''
#Place the '''''[[EMO:Control_Panel_Components#The_Data_Source_Manager|Data Sources Manager]]''''' in the Main Window into Powerflow Mode by highlighting the 'Powerflow' data source option
#Click the '''Create button''' at the foot of the Panel which opens the the '''''Powerflow Case Definition Window'''''

=== Powerflow Case Steps ===
#Naming The Powerflow Case
#Selecting the data range for the Powerflow Case
#Loading and editing Demand and Generation data
#Loading and editing Transmission System data
#Selecting the Swing Node/s
#Running the Powerflow Case

IMPORTANT: To avoid confusion, please note that you can load and edit Equation Constraints in Powerflows, but they do not impact on the power flow in any way at all. Equation Constraints are shown only so you can see if they are exceeded and by how much.

== Naming a Powerflow Case ==
By default new Powerflow Cases are created with the name: '''_New_'''. If a Case of this name already exists a version number in parentheses is appended to the name.


'''>> To add or change the name of the Powerflow Case:'''
#Click on the '''Powerflow Name button''' on the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Rename Powerflow Window
#Type the new Powerflow Case name and click the '''OK button'''

== Selecting a Powerflow Case Date Range ==
Each Powerflow Case must be associated with an Effective Date Range. The Powerflow output will contain data for each Trading Period specified in the Effective Date Range.

NOTE: It is possible to create Powerflow Cases for historical as well as future dates.


'''>> To specify the Effective Date Range:'''
#Use the Date Selector to specify the date on which the Powerflow Case will start
#Use the Trading Period Selector to specify the starting Trading Period for the Powerflow Case
#Specify how many Trading Periods (from and include the starting period) you would like the Powerflow Case to cover

NOTES:
#''EMarketOffer'' uses the Effective Date Range as a default when loading input data into the Powerflow Case from database or file.
#The Powerflow Case works with a single week (seven-days) of input data, Powerflow Cases covering more that 336 periods (seVen-days) will re-cycle Demand and Generation data.

== Loading and Editing Demand and Generation Data ==

'''>> To load Demand and Generation data in to your Powerflow Case:'''
#Use the '''Data > Load Data''' option in the Menu bar of the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Load Data Window
#Use the '''Demand and Generation Data Panel''' to specify the details of the Demand and Generations data you wish to use.

NOTES:
#When loading Demand or Generation data from file ''EMarketOffer'' uses the date in the file name to establish the day of the week the data will be used for in the profile. Loading two files for a Wednesday means an average of the two days will be made for the weekly profile.
#It is possible to load partial files for a limited number of Trading Periods and/or Nodes. Data for the Trading Periods and Nodes in the partial file will overwrite existing data but leave other data in tact.

You can also load Demand and Generation data from previously prepared Demand or Generation Profile files using the '''Profiles > Demand''' or '''Profiles > Generation''' options in the menu of the Powerflow Case Definition Window.

Finally, you can:
*Load Demand data into the Definition one Node at a time through the Edit Node Data Grid accessed through the loaded data panel on the Powerflow Case Definition Window. Such loading can be achieved either manually or by cutting and pasting from another application such as Excel.
*Load Generation data on Units at a time through the Edit Unit Data Grid in the Powerflow Case Definition Window

=== Editing Loaded Demand and Generation Data ===
Demand data can be edited individually by Node using the '''''Edit Node Window''''' accessed through the loaded data panel on the Powerflow Case Definition Window (similar functionality can be used to edit loaded Generation data using the Edit Unit Data Grid).

Individual Demand figures can be edited manually or multiple cells can be changed by pasting into a highlighted section of the grid from the clipboard. You can:
*Replace all of the existing profile by re-loading from the database
*Use edited demand files to replace all or part of the existing Demand profile.

NOTE: Data pasted into the Demand Grid overwrites existing data as soon as it is pasted.

TIP: You can use the Graph Nodal Demand profile feature (Graph Button on the Edit Node Data Grid) to make a quick visual check on changes you are making to the Nodal Demand profile).

== Loading and Editing Transmission System Data ==

=== Loading Transmission Data ===

'''>> To load Transmission data into your Powerflow Case Definition:'''
#Use the '''Data > Load Data''' option in the Menu bar of the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Load Data Window
#Use the '''Load Transmission Data Panel''' to specify the details of the Transmission data you wish to use

Tip: Remember to select a data range for the Transmission System data that fully covers the Powerflow Case Definition Effective Date Range.

Finally you can load Circuit and Equation Constraint data into the Powerflow Case Definition one Circuit and Equation at a time through the '''''Edit Circuits '''''and '''''Edit Equations Information Windows''''' accessed through the loaded data panel on the Powerflow Case Definition Window. This can be achieved either manually or by cutting and pasting from another application such as Excel.

=== Editing Loaded Circuit Data ===
Data for individual Circuits can be edited using the '''''Edit Circuit Information Window''''' accessed by double-clicking a circuit in the loaded circuit data panel on the Powerflow Case Definition Window.

=== Editing Loaded Equation Constraint Data ===
Equation Constraint data can be edited using the '''''Edit Equation Constraint Information Window''''' accessed by double-clicking an equation in the loaded equations data panel on the Powerflow Case Definition Window.

== Selecting Swing Nodes ==
The final step before running the Powerflow Analysis is to select one or more Swing Nodes to be used by the Powerflow model for allocating unmatched Demand.

Swing Nodes are selected through the '''''Swing Node Data Grid''''' in the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]].'''''

NOTE: it is possible to run a Powerflow Case without specifying a Swing Node, however the Infeasibilities Sub-Panel in the Control Panel of the Main Window will display the following message when viewing the results: '''"Unable to find Swing Node(s)"'''

== Running a Powerflow Case ==

'''>> To run the definition to produce Powerflow outputs:'''
#Click on the '''Run Powerflow button''' in the '''''Powerflow Case Definition Window.'''''

Initiating a Run opens the Run Progress Pop-up Window, which shows how many Powerflow Case periods have so far been analysed. You can use the '''Cancel button''' to halt the Powerflow Run at any time. Output calculated by the Run up until the time of cancellation can be viewed via the various output viewers.

NOTE: On completion the '''''[[EMO:The Main Window|Main Window]]''''' is immediately set to Powerflow '''''Data Source''''' mode and shows data from the first period in the Powerflow Case.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Powerflow Analysis|Back]]

Special:Badtitle/NS106:Creating a Powerflow Case Definition

2013-05-05T21:52:10Z

Greg: /* Editing Loaded Equation Constraint Data */

{{#hidens:}}

'''>> To create a Powerflow Case Definition:'''
#Place the '''''[[EMO:Control_Panel_Components#The_Data_Source_Manager|Data Sources Manager]]''''' in the Main Window into Powerflow Mode by highlighting the 'Powerflow' data source option
#Click the '''Create button''' at the foot of the Panel which opens the the '''''Powerflow Case Definition Window'''''

=== Powerflow Case Steps ===
#Naming The Powerflow Case
#Selecting the data range for the Powerflow Case
#Loading and editing Demand and Generation data
#Loading and editing Transmission System data
#Selecting the Swing Node/s
#Running the Powerflow Case

== Naming a Powerflow Case ==
By default new Powerflow Cases are created with the name: '''_New_'''. If a Case of this name already exists a version number in parentheses is appended to the name.


'''>> To add or change the name of the Powerflow Case:'''
#Click on the '''Powerflow Name button''' on the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Rename Powerflow Window
#Type the new Powerflow Case name and click the '''OK button'''

== Selecting a Powerflow Case Date Range ==
Each Powerflow Case must be associated with an Effective Date Range. The Powerflow output will contain data for each Trading Period specified in the Effective Date Range.

NOTE: It is possible to create Powerflow Cases for historical as well as future dates.


'''>> To specify the Effective Date Range:'''
#Use the Date Selector to specify the date on which the Powerflow Case will start
#Use the Trading Period Selector to specify the starting Trading Period for the Powerflow Case
#Specify how many Trading Periods (from and include the starting period) you would like the Powerflow Case to cover

NOTES:
#''EMarketOffer'' uses the Effective Date Range as a default when loading input data into the Powerflow Case from database or file.
#The Powerflow Case works with a single week (seven-days) of input data, Powerflow Cases covering more that 336 periods (seVen-days) will re-cycle Demand and Generation data.

== Loading and Editing Demand and Generation Data ==

'''>> To load Demand and Generation data in to your Powerflow Case:'''
#Use the '''Data > Load Data''' option in the Menu bar of the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Load Data Window
#Use the '''Demand and Generation Data Panel''' to specify the details of the Demand and Generations data you wish to use.

NOTES:
#When loading Demand or Generation data from file ''EMarketOffer'' uses the date in the file name to establish the day of the week the data will be used for in the profile. Loading two files for a Wednesday means an average of the two days will be made for the weekly profile.
#It is possible to load partial files for a limited number of Trading Periods and/or Nodes. Data for the Trading Periods and Nodes in the partial file will overwrite existing data but leave other data in tact.

You can also load Demand and Generation data from previously prepared Demand or Generation Profile files using the '''Profiles > Demand''' or '''Profiles > Generation''' options in the menu of the Powerflow Case Definition Window.

Finally, you can:
*Load Demand data into the Definition one Node at a time through the Edit Node Data Grid accessed through the loaded data panel on the Powerflow Case Definition Window. Such loading can be achieved either manually or by cutting and pasting from another application such as Excel.
*Load Generation data on Units at a time through the Edit Unit Data Grid in the Powerflow Case Definition Window

=== Editing Loaded Demand and Generation Data ===
Demand data can be edited individually by Node using the '''''Edit Node Window''''' accessed through the loaded data panel on the Powerflow Case Definition Window (similar functionality can be used to edit loaded Generation data using the Edit Unit Data Grid).

Individual Demand figures can be edited manually or multiple cells can be changed by pasting into a highlighted section of the grid from the clipboard. You can:
*Replace all of the existing profile by re-loading from the database
*Use edited demand files to replace all or part of the existing Demand profile.

NOTE: Data pasted into the Demand Grid overwrites existing data as soon as it is pasted.

TIP: You can use the Graph Nodal Demand profile feature (Graph Button on the Edit Node Data Grid) to make a quick visual check on changes you are making to the Nodal Demand profile).

== Loading and Editing Transmission System Data ==

=== Loading Transmission Data ===

'''>> To load Transmission data into your Powerflow Case Definition:'''
#Use the '''Data > Load Data''' option in the Menu bar of the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]''''' to open the Load Data Window
#Use the '''Load Transmission Data Panel''' to specify the details of the Transmission data you wish to use

Tip: Remember to select a data range for the Transmission System data that fully covers the Powerflow Case Definition Effective Date Range.

Finally you can load Circuit and Equation Constraint data into the Powerflow Case Definition one Circuit and Equation at a time through the '''''Edit Circuits '''''and '''''Edit Equations Information Windows''''' accessed through the loaded data panel on the Powerflow Case Definition Window. This can be achieved either manually or by cutting and pasting from another application such as Excel.

=== Editing Loaded Circuit Data ===
Data for individual Circuits can be edited using the '''''Edit Circuit Information Window''''' accessed by double-clicking a circuit in the loaded circuit data panel on the Powerflow Case Definition Window.

=== Editing Loaded Equation Constraint Data ===
Equation Constraint data can be edited using the '''''Edit Equation Constraint Information Window''''' accessed by double-clicking an equation in the loaded equations data panel on the Powerflow Case Definition Window.

== Selecting Swing Nodes ==
The final step before running the Powerflow Analysis is to select one or more Swing Nodes to be used by the Powerflow model for allocating unmatched Demand.

Swing Nodes are selected through the '''''Swing Node Data Grid''''' in the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]].'''''

NOTE: it is possible to run a Powerflow Case without specifying a Swing Node, however the Infeasibilities Sub-Panel in the Control Panel of the Main Window will display the following message when viewing the results: '''"Unable to find Swing Node(s)"'''

== Running a Powerflow Case ==

'''>> To run the definition to produce Powerflow outputs:'''
#Click on the '''Run Powerflow button''' in the '''''Powerflow Case Definition Window.'''''

Initiating a Run opens the Run Progress Pop-up Window, which shows how many Powerflow Case periods have so far been analysed. You can use the '''Cancel button''' to halt the Powerflow Run at any time. Output calculated by the Run up until the time of cancellation can be viewed via the various output viewers.

NOTE: On completion the '''''[[EMO:The Main Window|Main Window]]''''' is immediately set to Powerflow '''''Data Source''''' mode and shows data from the first period in the Powerflow Case.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Powerflow Analysis|Back]]

Special:Badtitle/NS106:Loading and editing Transmission System Data

2013-05-05T21:51:47Z

Greg: /* Editing Loaded Group Constraint Data */

{{#hidens:}}
=== Loading Transmission Data ===

'''>> To load Transmission data in to your forecast Definition:'''
#Use the '''Data > Load Data''' option in the Menu bar of the '''''Forecast Definition Window''''' to open the '''''Load Data Window'''''
#Use the '''Load Transmission Data Dialogue''' to specify the details of the Transmission data you wish to use

Tip: Remember to select a data range for the Transmission data that fully covers the Forecast Definition Effective Date Range.

=== Editing Loaded Circuit Data ===
Data for individual Circuits can be edited using the '''''Edit Circuit Information Window''''' accessed by double-clicking a circuit in the loaded circuit data panel on the Forecast Definition Window.

=== Editing Loaded Equation Constraint Data ===
Equation Constraint data can be edited using the '''''Edit Equation Constraint Information''''' Window accessed by double-clicking an equation in the loaded equations data panel on the Forecast Definition Window.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Creating a Forecast Definition|Back]]

Special:Badtitle/NS106:Equation Constraints Schedule

2013-05-05T21:51:21Z

Greg: /* Usage */

{{#hidens:}}
=== Purpose ===
To display all circuit Re-ratings in the Forecast or Powerflow Case Definition individually.

=== Items ===
{|class="wikitable"
! Data Item !! Description
|-
|
:''Name''
|
:Identifies an Equation Constraint used in the Definition. (Typically the same names as used by the System Operator.)
|-
|
:''Date From''
|
:Date on which Constraint becomes effective
|-
|
:''TP From''
|
:Trading Period in which Constraint becomes effective
|-
|
:''Date To''
|
:Date on which Constraint ceases to be effective
|-
|
:''TP To''
|
:Trading Period in which Constraint ceases to be effective
|-
|
:''Equation''
|
:The Formula to be applied in working out the Constraint value for any given Trading Period (typically a matter of summing the products of powerflow and a load sharing distribution factor for each circuit in the Group)
|-
|
:''Limit''
|
:The maximum permitted Value before the Constraint becomes binding
|}

NOTE: The values of all fields in the Grid can be edited except for the Equation Constraint Name which can only be changed using the '''''Edit Equation Constraint Window.'''''

=== Usage ===

'''>> Double click a row to open the associated '''''Edit Equation Constraint Window''''', where Constraint details can be edited.


'''>> To add a new Equation Constraint to the Schedule:'''
#Select a row containing the name of the Equation Constraint to be entered and press the <INSERT> key
#This opens the '''''Activate Equation Constraint Window''''' with the "current" Equation Constraint selected

NOTE: The Equation Constraint Dialogue lists only those named Equation Constraints that have been loaded into the Forecast Definition


'''>> To Edit details of an existing Equation Constraint in the Schedule:'''
#Highlight the Grid Cell you wish to alter (you can alter all fields except for the Equation Constraint Name)
#Type the new value in the Cell, or press ''<F2>'' to edit the current contents


'''>> To Delete an existing Equation Constraint from the Schedule:'''
#Press the ''<Delete>'' key. You will be asked to confirm the deletion before it takes place.

NOTE: The Equation Constraints Schedule Grid can be sorted by any column by double-clicking on the column header.

'''WARNING!''' It is possible to create overlapping Equation Constraints using the Equation Constraint Schedule. ''EMarketOffer'' sorts the Equation Constraints by start and end dates and applies each one sequentially. This means that for any one period the last Constraint applied will be effective in the dispatch calculation. To see the actual order in which Equation Constraints will be applied refer to the '''''Edit Equation Constraint Window.'''''

=== The Activate Equation Constraint(s) Window ===

==== Purpose ====
To activate one or more Equation Constraints in a Forecast or Powerflow Case Definition.

==== Features ====
{|class="wikitable"
! Feature !! Purpose
|-
|
:''Date Range Selector''
|
:Allows you to select the date and time period range for which the Equation Constraint will be effective. Note that "To" dates are inclusive, so include the final day and time period selected
|-
|
:''Constraint Selector Type Toggle Buttons''
|
:Toggles the Constraint Selector from a drop down list (only selected Equation Constraints are displayed) to a Check List (all available Circuits are displayed)
|-
|
:''Drop Down Constraint Selection List (drop down mode)''
|
:Provides a list of available Equation Constraint from a drop down list

:It is possible to activate a whole category of Constraints at once by selecting Constraint Sets. Constraint sets appear in angled brackets at the top of the drop down list and provides all permutations of the following criteria:
*Season (Summer and Winter)
*Constraint type (Permanent, Temporary, Outage)
:Constraint Watch Lists also allow multiple selection in the drop down lists.
|-
|
:''Drop Down Constraint Selection List (check list mode)''
|
:Provides a list of available Equation Constraint from a check list. Multiple selection using Constraint Sets and Watch Lists is available by clicking on the "+/- Sets" row at the head of the check list.
|}

==== Usage ====
Please refer to '''''[[EMO:Circuit_Outage_Schedule#The_Insert_Re-ratings_Window|Insert Re-rating Window]]''''' which has very similar functionality.

NOTE: New Equation Constraints cannot be added here, you must use the Equation Constraints Data Grid instead. Constraints added using the Data Grid will automatically appear in the Constraint selection lists.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Loaded Data Summary Panel|Back]]

Special:Badtitle/NS106:Equation Constraints Schedule

2013-05-05T21:51:08Z

Greg: /* Features */

{{#hidens:}}
=== Purpose ===
To display all circuit Re-ratings in the Forecast or Powerflow Case Definition individually.

=== Items ===
{|class="wikitable"
! Data Item !! Description
|-
|
:''Name''
|
:Identifies an Equation Constraint used in the Definition. (Typically the same names as used by the System Operator.)
|-
|
:''Date From''
|
:Date on which Constraint becomes effective
|-
|
:''TP From''
|
:Trading Period in which Constraint becomes effective
|-
|
:''Date To''
|
:Date on which Constraint ceases to be effective
|-
|
:''TP To''
|
:Trading Period in which Constraint ceases to be effective
|-
|
:''Equation''
|
:The Formula to be applied in working out the Constraint value for any given Trading Period (typically a matter of summing the products of powerflow and a load sharing distribution factor for each circuit in the Group)
|-
|
:''Limit''
|
:The maximum permitted Value before the Constraint becomes binding
|}

NOTE: The values of all fields in the Grid can be edited except for the Equation Constraint Name which can only be changed using the '''''Edit Equation Constraint Window.'''''

=== Usage ===

'''>> Double click a row to open the associated '''''Edit Equation Constraint Window''''', where Constraint details can be edited.


'''>> To add a new Equation Constraint to the Schedule:'''
#Select a row containing the name of the Equation Constraint to be entered and press the <INSERT> key
#This opens the '''''Activate Equation Constraint Window''''' with the "current" Equation Constraint selected

NOTE: The Equation Constraint Dialogue lists only those named Equation Constraints that have been loaded into the Forecast Definition


'''>> To Edit details of an existing Equation Constraint in the Schedule:'''
#Highlight the Grid Cell you wish to alter (you can alter all fields except for the Equation Constraint Name)
#Type the new value in the Cell, or press ''<F2>'' to edit the current contents


'''>> To Delete an existing Equation Constraint from the Schedule:'''
#Press the ''<Delete>'' key. You will be asked to confirm the deletion before it takes place.

NOTE: The Equation Constraints Schedule Grid can be sorted by any column by double-clicking on the column header.

'''WARNING!''' It is possible to create overlapping Equation Constraints using the Equation Constraint Schedule. ''EMarketOffer'' sorts the Equation Constraints by start and end dates and applies each one sequentially. This means that for any one period the last Constraint applied will be effective in the dispatch calculation. To see the actual order in which Equation Constraints will be applied refer to the '''''Edit Equation Constraint Window.'''''

=== The Activate Equation Constraint(s) Window ===

==== Purpose ====
To activate one or more Equation Constraints in a Forecast or Powerflow Case Definition.

==== Features ====
{|class="wikitable"
! Feature !! Purpose
|-
|
:''Date Range Selector''
|
:Allows you to select the date and time period range for which the Equation Constraint will be effective. Note that "To" dates are inclusive, so include the final day and time period selected
|-
|
:''Constraint Selector Type Toggle Buttons''
|
:Toggles the Constraint Selector from a drop down list (only selected Equation Constraints are displayed) to a Check List (all available Circuits are displayed)
|-
|
:''Drop Down Constraint Selection List (drop down mode)''
|
:Provides a list of available Equation Constraint from a drop down list

:It is possible to activate a whole category of Constraints at once by selecting Constraint Sets. Constraint sets appear in angled brackets at the top of the drop down list and provides all permutations of the following criteria:
*Season (Summer and Winter)
*Constraint type (Permanent, Temporary, Outage)
:Constraint Watch Lists also allow multiple selection in the drop down lists.
|-
|
:''Drop Down Constraint Selection List (check list mode)''
|
:Provides a list of available Equation Constraint from a check list. Multiple selection using Constraint Sets and Watch Lists is available by clicking on the "+/- Sets" row at the head of the check list.
|}

==== Usage ====
Please refer to '''''[[EMO:Circuit_Outage_Schedule#The_Insert_Re-ratings_Window|Insert Re-rating Window]]''''' which has very similar functionality.

NOTE: New Group Constraints cannot be added here, you must use the Equation Constraints Data Grid instead. Constraints added using the Data Grid will automatically appear in the Constraint selection lists.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Loaded Data Summary Panel|Back]]

Special:Badtitle/NS106:Equation Constraints Schedule

2013-05-05T21:50:44Z

Greg: /* Purpose */

{{#hidens:}}
=== Purpose ===
To display all circuit Re-ratings in the Forecast or Powerflow Case Definition individually.

=== Items ===
{|class="wikitable"
! Data Item !! Description
|-
|
:''Name''
|
:Identifies an Equation Constraint used in the Definition. (Typically the same names as used by the System Operator.)
|-
|
:''Date From''
|
:Date on which Constraint becomes effective
|-
|
:''TP From''
|
:Trading Period in which Constraint becomes effective
|-
|
:''Date To''
|
:Date on which Constraint ceases to be effective
|-
|
:''TP To''
|
:Trading Period in which Constraint ceases to be effective
|-
|
:''Equation''
|
:The Formula to be applied in working out the Constraint value for any given Trading Period (typically a matter of summing the products of powerflow and a load sharing distribution factor for each circuit in the Group)
|-
|
:''Limit''
|
:The maximum permitted Value before the Constraint becomes binding
|}

NOTE: The values of all fields in the Grid can be edited except for the Equation Constraint Name which can only be changed using the '''''Edit Equation Constraint Window.'''''

=== Usage ===

'''>> Double click a row to open the associated '''''Edit Equation Constraint Window''''', where Constraint details can be edited.


'''>> To add a new Equation Constraint to the Schedule:'''
#Select a row containing the name of the Equation Constraint to be entered and press the <INSERT> key
#This opens the '''''Activate Equation Constraint Window''''' with the "current" Equation Constraint selected

NOTE: The Equation Constraint Dialogue lists only those named Equation Constraints that have been loaded into the Forecast Definition


'''>> To Edit details of an existing Equation Constraint in the Schedule:'''
#Highlight the Grid Cell you wish to alter (you can alter all fields except for the Equation Constraint Name)
#Type the new value in the Cell, or press ''<F2>'' to edit the current contents


'''>> To Delete an existing Equation Constraint from the Schedule:'''
#Press the ''<Delete>'' key. You will be asked to confirm the deletion before it takes place.

NOTE: The Equation Constraints Schedule Grid can be sorted by any column by double-clicking on the column header.

'''WARNING!''' It is possible to create overlapping Equation Constraints using the Equation Constraint Schedule. ''EMarketOffer'' sorts the Equation Constraints by start and end dates and applies each one sequentially. This means that for any one period the last Constraint applied will be effective in the dispatch calculation. To see the actual order in which Equation Constraints will be applied refer to the '''''Edit Equation Constraint Window.'''''

=== The Activate Equation Constraint(s) Window ===

==== Purpose ====
To activate one or more Equation Constraints in a Forecast or Powerflow Case Definition.

==== Features ====
{|class="wikitable"
! Feature !! Purpose
|-
|
:''Date Range Selector''
|
:Allows you to select the date and time period range for which the Group Constraint will be effective. Note that "To" dates are inclusive, so include the final day and time period selected
|-
|
:''Constraint Selector Type Toggle Buttons''
|
:Toggles the Constraint Selector from a drop down list (only selected Group Constraints are displayed) to a Check List (all available Circuits are displayed)
|-
|
:''Drop Down Constraint Selection List (drop down mode)''
|
:Provides a list of available Group Constraint from a drop down list

:It is possible to activate a whole category of Constraints at once by selecting Constraint Sets. Constraint sets appear in angled brackets at the top of the drop down list and provides all permutations of the following criteria:
*Season (Summer and Winter)
*Constraint type (Permanent, Temporary, Outage)
:Constraint Watch Lists also allow multiple selection in the drop down lists.
|-
|
:''Drop Down Constraint Selection List (check list mode)''
|
:Provides a list of available Group Constraint from a check list. Multiple selection using Constraint Sets and Watch Lists is available by clicking on the "+/- Sets" row at the head of the check list.
|}

==== Usage ====
Please refer to '''''[[EMO:Circuit_Outage_Schedule#The_Insert_Re-ratings_Window|Insert Re-rating Window]]''''' which has very similar functionality.

NOTE: New Group Constraints cannot be added here, you must use the Equation Constraints Data Grid instead. Constraints added using the Data Grid will automatically appear in the Constraint selection lists.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Loaded Data Summary Panel|Back]]

Special:Badtitle/NS106:Equation Constraints Schedule

2013-05-05T21:50:36Z

Greg: /* Usage */

{{#hidens:}}
=== Purpose ===
To display all circuit Re-ratings in the Forecast or Powerflow Case Definition individually.

=== Items ===
{|class="wikitable"
! Data Item !! Description
|-
|
:''Name''
|
:Identifies an Equation Constraint used in the Definition. (Typically the same names as used by the System Operator.)
|-
|
:''Date From''
|
:Date on which Constraint becomes effective
|-
|
:''TP From''
|
:Trading Period in which Constraint becomes effective
|-
|
:''Date To''
|
:Date on which Constraint ceases to be effective
|-
|
:''TP To''
|
:Trading Period in which Constraint ceases to be effective
|-
|
:''Equation''
|
:The Formula to be applied in working out the Constraint value for any given Trading Period (typically a matter of summing the products of powerflow and a load sharing distribution factor for each circuit in the Group)
|-
|
:''Limit''
|
:The maximum permitted Value before the Constraint becomes binding
|}

NOTE: The values of all fields in the Grid can be edited except for the Equation Constraint Name which can only be changed using the '''''Edit Equation Constraint Window.'''''

=== Usage ===

'''>> Double click a row to open the associated '''''Edit Equation Constraint Window''''', where Constraint details can be edited.


'''>> To add a new Equation Constraint to the Schedule:'''
#Select a row containing the name of the Equation Constraint to be entered and press the <INSERT> key
#This opens the '''''Activate Equation Constraint Window''''' with the "current" Equation Constraint selected

NOTE: The Equation Constraint Dialogue lists only those named Equation Constraints that have been loaded into the Forecast Definition


'''>> To Edit details of an existing Equation Constraint in the Schedule:'''
#Highlight the Grid Cell you wish to alter (you can alter all fields except for the Equation Constraint Name)
#Type the new value in the Cell, or press ''<F2>'' to edit the current contents


'''>> To Delete an existing Equation Constraint from the Schedule:'''
#Press the ''<Delete>'' key. You will be asked to confirm the deletion before it takes place.

NOTE: The Equation Constraints Schedule Grid can be sorted by any column by double-clicking on the column header.

'''WARNING!''' It is possible to create overlapping Equation Constraints using the Equation Constraint Schedule. ''EMarketOffer'' sorts the Equation Constraints by start and end dates and applies each one sequentially. This means that for any one period the last Constraint applied will be effective in the dispatch calculation. To see the actual order in which Equation Constraints will be applied refer to the '''''Edit Equation Constraint Window.'''''

=== The Activate Equation Constraint(s) Window ===

==== Purpose ====
To activate one or more Group Constraints in a Forecast or Powerflow Case Definition.

==== Features ====
{|class="wikitable"
! Feature !! Purpose
|-
|
:''Date Range Selector''
|
:Allows you to select the date and time period range for which the Group Constraint will be effective. Note that "To" dates are inclusive, so include the final day and time period selected
|-
|
:''Constraint Selector Type Toggle Buttons''
|
:Toggles the Constraint Selector from a drop down list (only selected Group Constraints are displayed) to a Check List (all available Circuits are displayed)
|-
|
:''Drop Down Constraint Selection List (drop down mode)''
|
:Provides a list of available Group Constraint from a drop down list

:It is possible to activate a whole category of Constraints at once by selecting Constraint Sets. Constraint sets appear in angled brackets at the top of the drop down list and provides all permutations of the following criteria:
*Season (Summer and Winter)
*Constraint type (Permanent, Temporary, Outage)
:Constraint Watch Lists also allow multiple selection in the drop down lists.
|-
|
:''Drop Down Constraint Selection List (check list mode)''
|
:Provides a list of available Group Constraint from a check list. Multiple selection using Constraint Sets and Watch Lists is available by clicking on the "+/- Sets" row at the head of the check list.
|}

==== Usage ====
Please refer to '''''[[EMO:Circuit_Outage_Schedule#The_Insert_Re-ratings_Window|Insert Re-rating Window]]''''' which has very similar functionality.

NOTE: New Group Constraints cannot be added here, you must use the Equation Constraints Data Grid instead. Constraints added using the Data Grid will automatically appear in the Constraint selection lists.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Loaded Data Summary Panel|Back]]

Special:Badtitle/NS106:Equation Constraints Schedule

2013-05-05T21:50:23Z

Greg: /* Usage */

{{#hidens:}}
=== Purpose ===
To display all circuit Re-ratings in the Forecast or Powerflow Case Definition individually.

=== Items ===
{|class="wikitable"
! Data Item !! Description
|-
|
:''Name''
|
:Identifies an Equation Constraint used in the Definition. (Typically the same names as used by the System Operator.)
|-
|
:''Date From''
|
:Date on which Constraint becomes effective
|-
|
:''TP From''
|
:Trading Period in which Constraint becomes effective
|-
|
:''Date To''
|
:Date on which Constraint ceases to be effective
|-
|
:''TP To''
|
:Trading Period in which Constraint ceases to be effective
|-
|
:''Equation''
|
:The Formula to be applied in working out the Constraint value for any given Trading Period (typically a matter of summing the products of powerflow and a load sharing distribution factor for each circuit in the Group)
|-
|
:''Limit''
|
:The maximum permitted Value before the Constraint becomes binding
|}

NOTE: The values of all fields in the Grid can be edited except for the Equation Constraint Name which can only be changed using the '''''Edit Equation Constraint Window.'''''

=== Usage ===

'''>> Double click a row to open the associated '''''Edit Equation Constraint Window''''', where Constraint details can be edited.


'''>> To add a new Equation Constraint to the Schedule:'''
#Select a row containing the name of the Equation Constraint to be entered and press the <INSERT> key
#This opens the '''''Activate Equation Constraint Window''''' with the "current" Equation Constraint selected

NOTE: The Equation Constraint Dialogue lists only those named Equation Constraints that have been loaded into the Forecast Definition


'''>> To Edit details of an existing Equation Constraint in the Schedule:'''
#Highlight the Grid Cell you wish to alter (you can alter all fields except for the Equation Constraint Name)
#Type the new value in the Cell, or press ''<F2>'' to edit the current contents


'''>> To Delete an existing Equation Constraint from the Schedule:'''
#Press the ''<Delete>'' key. You will be asked to confirm the deletion before it takes place.

NOTE: The Equation Constraints Schedule Grid can be sorted by any column by double-clicking on the column header.

'''WARNING!''' It is possible to create overlapping Group Constraints using the Equation Constraint Schedule. ''EMarketOffer'' sorts the Equation Constraints by start and end dates and applies each one sequentially. This means that for any one period the last Constraint applied will be effective in the dispatch calculation. To see the actual order in which Equation Constraints will be applied refer to the '''''Edit Equation Constraint Window.'''''

=== The Activate Equation Constraint(s) Window ===

==== Purpose ====
To activate one or more Group Constraints in a Forecast or Powerflow Case Definition.

==== Features ====
{|class="wikitable"
! Feature !! Purpose
|-
|
:''Date Range Selector''
|
:Allows you to select the date and time period range for which the Group Constraint will be effective. Note that "To" dates are inclusive, so include the final day and time period selected
|-
|
:''Constraint Selector Type Toggle Buttons''
|
:Toggles the Constraint Selector from a drop down list (only selected Group Constraints are displayed) to a Check List (all available Circuits are displayed)
|-
|
:''Drop Down Constraint Selection List (drop down mode)''
|
:Provides a list of available Group Constraint from a drop down list

:It is possible to activate a whole category of Constraints at once by selecting Constraint Sets. Constraint sets appear in angled brackets at the top of the drop down list and provides all permutations of the following criteria:
*Season (Summer and Winter)
*Constraint type (Permanent, Temporary, Outage)
:Constraint Watch Lists also allow multiple selection in the drop down lists.
|-
|
:''Drop Down Constraint Selection List (check list mode)''
|
:Provides a list of available Group Constraint from a check list. Multiple selection using Constraint Sets and Watch Lists is available by clicking on the "+/- Sets" row at the head of the check list.
|}

==== Usage ====
Please refer to '''''[[EMO:Circuit_Outage_Schedule#The_Insert_Re-ratings_Window|Insert Re-rating Window]]''''' which has very similar functionality.

NOTE: New Group Constraints cannot be added here, you must use the Equation Constraints Data Grid instead. Constraints added using the Data Grid will automatically appear in the Constraint selection lists.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Loaded Data Summary Panel|Back]]

Special:Badtitle/NS106:Equation Constraints Schedule

2013-05-05T21:49:49Z

Greg: /* Items */

{{#hidens:}}
=== Purpose ===
To display all circuit Re-ratings in the Forecast or Powerflow Case Definition individually.

=== Items ===
{|class="wikitable"
! Data Item !! Description
|-
|
:''Name''
|
:Identifies an Equation Constraint used in the Definition. (Typically the same names as used by the System Operator.)
|-
|
:''Date From''
|
:Date on which Constraint becomes effective
|-
|
:''TP From''
|
:Trading Period in which Constraint becomes effective
|-
|
:''Date To''
|
:Date on which Constraint ceases to be effective
|-
|
:''TP To''
|
:Trading Period in which Constraint ceases to be effective
|-
|
:''Equation''
|
:The Formula to be applied in working out the Constraint value for any given Trading Period (typically a matter of summing the products of powerflow and a load sharing distribution factor for each circuit in the Group)
|-
|
:''Limit''
|
:The maximum permitted Value before the Constraint becomes binding
|}

NOTE: The values of all fields in the Grid can be edited except for the Equation Constraint Name which can only be changed using the '''''Edit Equation Constraint Window.'''''

=== Usage ===

'''>> Double click a row to open the associated '''''Edit Equation Constraint Window''''', where Constraint details can be edited.


'''>> To add a new Group Constraint to the Schedule:'''
#Select a row containing the name of the Group Constraint to be entered and press the <INSERT> key
#This opens the '''''Activate Equation Constraint Window''''' with the "current" Equation Constraint selected

NOTE: The Equation Constraint Dialogue lists only those named Equation Constraints that have been loaded into the Forecast Definition


'''>> To Edit details of an existing Group Constraint in the Schedule:'''
#Highlight the Grid Cell you wish to alter (you can alter all fields except for the Equation Constraint Name)
#Type the new value in the Cell, or press ''<F2>'' to edit the current contents


'''>> To Delete an existing Group Constraint from the Schedule:'''
#Press the ''<Delete>'' key. You will be asked to confirm the deletion before it takes place.

NOTE: The Equation Constraints Schedule Grid can be sorted by any column by double-clicking on the column header.

'''WARNING!''' It is possible to create overlapping Group Constraints using the Equation Constraint Schedule. ''EMarketOffer'' sorts the Group Constraints by start and end dates and applies each one sequentially. This means that for any one period the last Constraint applied will be effective in the dispatch calculation. To see the actual order in which Group Constraints will be applied refer to the '''''Edit Equation Constraint Window.'''''

=== The Activate Equation Constraint(s) Window ===

==== Purpose ====
To activate one or more Group Constraints in a Forecast or Powerflow Case Definition.

==== Features ====
{|class="wikitable"
! Feature !! Purpose
|-
|
:''Date Range Selector''
|
:Allows you to select the date and time period range for which the Group Constraint will be effective. Note that "To" dates are inclusive, so include the final day and time period selected
|-
|
:''Constraint Selector Type Toggle Buttons''
|
:Toggles the Constraint Selector from a drop down list (only selected Group Constraints are displayed) to a Check List (all available Circuits are displayed)
|-
|
:''Drop Down Constraint Selection List (drop down mode)''
|
:Provides a list of available Group Constraint from a drop down list

:It is possible to activate a whole category of Constraints at once by selecting Constraint Sets. Constraint sets appear in angled brackets at the top of the drop down list and provides all permutations of the following criteria:
*Season (Summer and Winter)
*Constraint type (Permanent, Temporary, Outage)
:Constraint Watch Lists also allow multiple selection in the drop down lists.
|-
|
:''Drop Down Constraint Selection List (check list mode)''
|
:Provides a list of available Group Constraint from a check list. Multiple selection using Constraint Sets and Watch Lists is available by clicking on the "+/- Sets" row at the head of the check list.
|}

==== Usage ====
Please refer to '''''[[EMO:Circuit_Outage_Schedule#The_Insert_Re-ratings_Window|Insert Re-rating Window]]''''' which has very similar functionality.

NOTE: New Group Constraints cannot be added here, you must use the Equation Constraints Data Grid instead. Constraints added using the Data Grid will automatically appear in the Constraint selection lists.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Loaded Data Summary Panel|Back]]

Special:Badtitle/NS106:Equation Constraints Schedule

2013-05-05T21:49:35Z

Greg: /* Items */

{{#hidens:}}
=== Purpose ===
To display all circuit Re-ratings in the Forecast or Powerflow Case Definition individually.

=== Items ===
{|class="wikitable"
! Data Item !! Description
|-
|
:''Name''
|
:Identifies an Equation Constraint used in the Definition. (Typically the same names as used by the System Operator.)
|-
|
:''Date From''
|
:Date on which Constraint becomes effective
|-
|
:''TP From''
|
:Trading Period in which Constraint becomes effective
|-
|
:''Date To''
|
:Date on which Constraint ceases to be effective
|-
|
:''TP To''
|
:Trading Period in which Constraint ceases to be effective
|-
|
:''Equation''
|
:The Formula to be applied in working out the Constraint value for any given Trading Period (typically a matter of summing the products of powerflow and a load sharing distribution factor for each circuit in the Group)
|-
|
:''Limit''
|
:The maximum permitted Value before the Constraint becomes binding
|}

NOTE: The values of all fields in the Grid can be edited except for the Group Constraint Name which can only be changed using the '''''Edit Equation Constraint Window.'''''

=== Usage ===

'''>> Double click a row to open the associated '''''Edit Equation Constraint Window''''', where Constraint details can be edited.


'''>> To add a new Group Constraint to the Schedule:'''
#Select a row containing the name of the Group Constraint to be entered and press the <INSERT> key
#This opens the '''''Activate Equation Constraint Window''''' with the "current" Equation Constraint selected

NOTE: The Equation Constraint Dialogue lists only those named Equation Constraints that have been loaded into the Forecast Definition


'''>> To Edit details of an existing Group Constraint in the Schedule:'''
#Highlight the Grid Cell you wish to alter (you can alter all fields except for the Equation Constraint Name)
#Type the new value in the Cell, or press ''<F2>'' to edit the current contents


'''>> To Delete an existing Group Constraint from the Schedule:'''
#Press the ''<Delete>'' key. You will be asked to confirm the deletion before it takes place.

NOTE: The Equation Constraints Schedule Grid can be sorted by any column by double-clicking on the column header.

'''WARNING!''' It is possible to create overlapping Group Constraints using the Equation Constraint Schedule. ''EMarketOffer'' sorts the Group Constraints by start and end dates and applies each one sequentially. This means that for any one period the last Constraint applied will be effective in the dispatch calculation. To see the actual order in which Group Constraints will be applied refer to the '''''Edit Equation Constraint Window.'''''

=== The Activate Equation Constraint(s) Window ===

==== Purpose ====
To activate one or more Group Constraints in a Forecast or Powerflow Case Definition.

==== Features ====
{|class="wikitable"
! Feature !! Purpose
|-
|
:''Date Range Selector''
|
:Allows you to select the date and time period range for which the Group Constraint will be effective. Note that "To" dates are inclusive, so include the final day and time period selected
|-
|
:''Constraint Selector Type Toggle Buttons''
|
:Toggles the Constraint Selector from a drop down list (only selected Group Constraints are displayed) to a Check List (all available Circuits are displayed)
|-
|
:''Drop Down Constraint Selection List (drop down mode)''
|
:Provides a list of available Group Constraint from a drop down list

:It is possible to activate a whole category of Constraints at once by selecting Constraint Sets. Constraint sets appear in angled brackets at the top of the drop down list and provides all permutations of the following criteria:
*Season (Summer and Winter)
*Constraint type (Permanent, Temporary, Outage)
:Constraint Watch Lists also allow multiple selection in the drop down lists.
|-
|
:''Drop Down Constraint Selection List (check list mode)''
|
:Provides a list of available Group Constraint from a check list. Multiple selection using Constraint Sets and Watch Lists is available by clicking on the "+/- Sets" row at the head of the check list.
|}

==== Usage ====
Please refer to '''''[[EMO:Circuit_Outage_Schedule#The_Insert_Re-ratings_Window|Insert Re-rating Window]]''''' which has very similar functionality.

NOTE: New Group Constraints cannot be added here, you must use the Equation Constraints Data Grid instead. Constraints added using the Data Grid will automatically appear in the Constraint selection lists.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Loaded Data Summary Panel|Back]]

Special:Badtitle/NS106:Loaded Equation Constraints

2013-05-05T21:49:14Z

Greg: /* Purpose */

{{#hidens:}}
=== Items ===
{|class="wikitable"
! Item !! Purpose
|-
|
:''Name''
|
:Name of Constraint
|-
|
:''Included''
|
:Included Status (checked when Constraint will be included in dispatch)
|-
|
:''Constraint Type''
|
:Can be
*Permanent
*Temporary
*Outage
|-
|
:''Season''
|
:Can be
*Summer
*Winter
*Both
|-
|
:''Default Formula''
|
:Used as the default formula when applied in the Forecast
|-
|
:''Default Limit''
|
:Used as the default limit value when applied in the Forecast
|}

NOTE: ''EMarketOffer'' flags an Equation Constraint as Active if the grid data files contains a constraint starting before or during the Forecast Effective Date Range and ending during or after the Effective Date Range.

=== Usage ===

'''>> Double-click on a row to open the ''Edit Equation Constraint Window'' where Constraint details can be edited'''


'''>> To add a new Equation Constraint:'''
#Click on any row in the Equation Constraints Data Grid and press the ''<Insert>'' key. This creates an empty row at the top of the Grid labelled " _ new _ ". Details of the Constraint can be entered by bringing up the Edit Equation Constraint Window by double-clicking the empty row.


'''>> To delete an existing Circuit:'''
#Click on the row in the Circuit Data Grid containing the Circuit you want to delete and press the <DELETE> key. A dialogue box asking you to confirm the delete operation will appear.

NOTE: Deleting a Constraint also deletes any re-ratings data associated with the Constraint at the time of deletion.

=== The Edit Equation Constraints Window ===

==== Access ====
Double-clicking an Equation Constraint name in the '''''Loaded Data Summary Panel''''' of either the '''''Forecast Definition''''' or '''''Powerflow Case Definition''''' Windows.

==== Purpose ====
To manually add, delete and modify the applications of a specific Equation Constraint throughout the Effective Date Range.

==== Components ====
{|class="wikitable"
! Component !! Description
|-
|
:''Name''
|
:Name of Constraint
|-
|
:''Active''
|
:Checked when Constraint will be included in dispatch
|-
|
:''Type''
|
:Constraint type
|-
|
:''Season''
|
:Season constraint is applicable to
|-
|
:''Default Formula''
|
:Default formula for Constraint as published by System Operator
|-
|
:''Default Limit''
|
:Default limit for Constraint as published by System Operator
|-
|
:''Equation Constraints Grid''
|
*Time From - Date from which Constraint will be effective within the Forecast Effective Date Range
*TP From - Trading Period from which the Constraint will be effective
*Time To - Date until and including which the Constraint will be effective
*TP To - Trading Period until and including which the constraint will be effective
*Limit - The Constraining value of the Equation
*Equation - The Equation used to calculate the value
|}

NOTE: When uploading historic Transmission System data from grid data files ''EMarketOffer'' automatically applies and Transpower notified re-ratings.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Loaded Data Summary Panel|Back]]

Special:Badtitle/NS106:Loaded Equation Constraints

2013-05-05T21:48:54Z

Greg: /* Access */

{{#hidens:}}
=== Items ===
{|class="wikitable"
! Item !! Purpose
|-
|
:''Name''
|
:Name of Constraint
|-
|
:''Included''
|
:Included Status (checked when Constraint will be included in dispatch)
|-
|
:''Constraint Type''
|
:Can be
*Permanent
*Temporary
*Outage
|-
|
:''Season''
|
:Can be
*Summer
*Winter
*Both
|-
|
:''Default Formula''
|
:Used as the default formula when applied in the Forecast
|-
|
:''Default Limit''
|
:Used as the default limit value when applied in the Forecast
|}

NOTE: ''EMarketOffer'' flags an Equation Constraint as Active if the grid data files contains a constraint starting before or during the Forecast Effective Date Range and ending during or after the Effective Date Range.

=== Usage ===

'''>> Double-click on a row to open the ''Edit Equation Constraint Window'' where Constraint details can be edited'''


'''>> To add a new Equation Constraint:'''
#Click on any row in the Equation Constraints Data Grid and press the ''<Insert>'' key. This creates an empty row at the top of the Grid labelled " _ new _ ". Details of the Constraint can be entered by bringing up the Edit Equation Constraint Window by double-clicking the empty row.


'''>> To delete an existing Circuit:'''
#Click on the row in the Circuit Data Grid containing the Circuit you want to delete and press the <DELETE> key. A dialogue box asking you to confirm the delete operation will appear.

NOTE: Deleting a Constraint also deletes any re-ratings data associated with the Constraint at the time of deletion.

=== The Edit Equation Constraints Window ===

==== Access ====
Double-clicking an Equation Constraint name in the '''''Loaded Data Summary Panel''''' of either the '''''Forecast Definition''''' or '''''Powerflow Case Definition''''' Windows.

==== Purpose ====
To manually add, delete and modify the applications of a specific Group Constraint throughout the Effective Date Range.

==== Components ====
{|class="wikitable"
! Component !! Description
|-
|
:''Name''
|
:Name of Constraint
|-
|
:''Active''
|
:Checked when Constraint will be included in dispatch
|-
|
:''Type''
|
:Constraint type
|-
|
:''Season''
|
:Season constraint is applicable to
|-
|
:''Default Formula''
|
:Default formula for Constraint as published by System Operator
|-
|
:''Default Limit''
|
:Default limit for Constraint as published by System Operator
|-
|
:''Equation Constraints Grid''
|
*Time From - Date from which Constraint will be effective within the Forecast Effective Date Range
*TP From - Trading Period from which the Constraint will be effective
*Time To - Date until and including which the Constraint will be effective
*TP To - Trading Period until and including which the constraint will be effective
*Limit - The Constraining value of the Equation
*Equation - The Equation used to calculate the value
|}

NOTE: When uploading historic Transmission System data from grid data files ''EMarketOffer'' automatically applies and Transpower notified re-ratings.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Loaded Data Summary Panel|Back]]

Special:Badtitle/NS106:Equation Constraints Information Grid

2013-05-05T21:48:35Z

Greg: /* Data Types */

{{#hidens:}}
=== Access ===
The '''Equations Tab''' in the '''''[[EMO:Main Window Display Panel|Main Window Display Panel]]'''''.

=== Purpose ===
To display '''''Dynamic Information''''' related to all Group Constraints for the '''''Current Data Set'''''.

=== Data Types ===
{|class="wikitable"
! Column !! Description (for the Current Period)
|-
|
:''Name''
|
:Equation Constraint Name (as provided by Transpower or user-named)
|-
|
:''Formula''
|
:The Equation specifying how the value of the Constraint is to be calculated
|-
|
:''Active''
|
:When checked indicates ''EMarketOffer'' included the Equation Constraint in the dispatch
|-
|
:''Limit''
|
:The value which the Equation's solution must not exceed (in MW)
|-
|
:''Value''
|
:The Value of the Equation solution (in MW)
|-
|
:''Freedom''
|
:How close (in MW) the current value is to the constraining value
|}

NOTE: Double-clicking on any row will open a separate '''''[[EMO:Equation Constraints Information Window|Equation Constraint Information Window]]''''' for the associated Equation Constraint.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:The Display Area Information Grids|Back]]

Special:Badtitle/NS106:Equation Constraints Information Window

2013-05-05T21:48:10Z

Greg: /* Features */

{{#hidens:}}
=== Access ===
Double-clicking any row in the [[EMO:Equation Constraints Information Grid|Equation Constraints Information Grid]] of the '''''Main Window''''', or a '''''Secondary Window''''' displaying Circuits.

=== Purpose ===
To display read-only information relating to an Equation Constraint for the '''''Current Data Set'''''.

=== Features ===
{|class="wikitable"
! Feature !! Description (for the Current Period)
|-
|
:''Title Bar''
|
:Contains the following information:
*Modelled Item Type ("Equation")
*Node Name: (e.g. "ROX_T10_S_P_z")
*Data Source Type (e.g. "Forecast")
*Data Source Name (e.g. "21 Aug 2004")
*Date of Current Data Set (e.g. Sat, 21 Dec 2007")
*Current Trading Period (e.g. ":1")
*Scenario Version (e.g. ";1") - Scenarios only
|-
|
:''Name''
|
:Equation Constraint Name. Double-clicking on this field opens a '''''Equation Constraints Watch Window''''' based on the default Equation Constraint Watch List with the Equation Constraint added
|-
|
:''Formula''
|
:Formula (LHS) of the Equation Constraint
|-
|
:''Active''
|
:When checked indicates the Equation Constraint was included in the dispatch
|-
|
:''Limit''
|
:Limit (RHS) of the Equation Constraint
|-
|
:''Value''
|
:Value of the Equation Constraint
|-
|
:''Freedom''
|
:Freedom of the Equation Constraint
|-
|
:''Associated Circuits Panel''
|
*Name - Circuit Name. Double-clicking on this field opens the related [[EMO:Circuits Information Window|Circuit Information Window]]
*Powerflow - Powerflow on the Circuit
*P.S. - Price separation across the Circuit (always zero for Powerflow Cases)
|}

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:The Display Area Information Grids|Back]]

Special:Badtitle/NS106:Equation Constraints Information Window

2013-05-05T21:47:54Z

Greg: /* Features */

{{#hidens:}}
=== Access ===
Double-clicking any row in the [[EMO:Equation Constraints Information Grid|Equation Constraints Information Grid]] of the '''''Main Window''''', or a '''''Secondary Window''''' displaying Circuits.

=== Purpose ===
To display read-only information relating to an Equation Constraint for the '''''Current Data Set'''''.

=== Features ===
{|class="wikitable"
! Feature !! Description (for the Current Period)
|-
|
:''Title Bar''
|
:Contains the following information:
*Modelled Item Type ("Equation")
*Node Name: (e.g. "ROX_T10_S_P_z")
*Data Source Type (e.g. "Forecast")
*Data Source Name (e.g. "21 Aug 2004")
*Date of Current Data Set (e.g. Sat, 21 Dec 2007")
*Current Trading Period (e.g. ":1")
*Scenario Version (e.g. ";1") - Scenarios only
|-
|
:''Name''
|
:Equation Constraint Name. Double-clicking on this field opens a '''''Equation Constraints Watch Window''''' based on the default Equation Constraint Watch List with the Equation Constraint added
|-
|
:''Formula''
|
:Formula (LHS) of the Group Constraint
|-
|
:''Active''
|
:When checked indicates the Equation Constraint was included in the dispatch
|-
|
:''Limit''
|
:Limit (RHS) of the Group Constraint
|-
|
:''Value''
|
:Value of the Equation Constraint
|-
|
:''Freedom''
|
:Freedom of the Equation Constraint
|-
|
:''Associated Circuits Panel''
|
*Name - Circuit Name. Double-clicking on this field opens the related [[EMO:Circuits Information Window|Circuit Information Window]]
*Powerflow - Powerflow on the Circuit
*P.S. - Price separation across the Circuit (always zero for Powerflow Cases)
|}

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:The Display Area Information Grids|Back]]

Special:Badtitle/NS106:Equation Constraints Information Window

2013-05-05T21:47:20Z

Greg: /* Purpose */

{{#hidens:}}
=== Access ===
Double-clicking any row in the [[EMO:Equation Constraints Information Grid|Equation Constraints Information Grid]] of the '''''Main Window''''', or a '''''Secondary Window''''' displaying Circuits.

=== Purpose ===
To display read-only information relating to an Equation Constraint for the '''''Current Data Set'''''.

=== Features ===
{|class="wikitable"
! Feature !! Description (for the Current Period)
|-
|
:''Title Bar''
|
:Contains the following information:
*Modelled Item Type ("Equation")
*Node Name: (e.g. "ROX_T10_S_P_z")
*Data Source Type (e.g. "Forecast")
*Data Source Name (e.g. "21 Aug 2004")
*Date of Current Data Set (e.g. Sat, 21 Dec 2007")
*Current Trading Period (e.g. ":1")
*Scenario Version (e.g. ";1") - Scenarios only
|-
|
:''Name''
|
:Group Constraint Name. Double-clicking on this field opens a '''''Equation Constraints Watch Window''''' based on the default Equation Constraint Watch List with the Equation Constraint added
|-
|
:''Formula''
|
:Formula (LHS) of the Group Constraint
|-
|
:''Active''
|
:When checked indicates the Group Constraint was included in the dispatch
|-
|
:''Limit''
|
:Limit (RHS) of the Group Constraint
|-
|
:''Value''
|
:Value of the Group Constraint
|-
|
:''Freedom''
|
:Freedom of the Group Constraint
|-
|
:''Associated Circuits Panel''
|
*Name - Circuit Name. Double-clicking on this field opens the related [[EMO:Circuits Information Window|Circuit Information Window]]
*Powerflow - Powerflow on the Circuit
*P.S. - Price separation across the Circuit (always zero for Powerflow Cases)
|}

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:The Display Area Information Grids|Back]]

Special:Badtitle/NS106:Equation Constraints Information Grid

2013-05-05T21:46:20Z

Greg: /* Data Types */

{{#hidens:}}
=== Access ===
The '''Equations Tab''' in the '''''[[EMO:Main Window Display Panel|Main Window Display Panel]]'''''.

=== Purpose ===
To display '''''Dynamic Information''''' related to all Group Constraints for the '''''Current Data Set'''''.

=== Data Types ===
{|class="wikitable"
! Column !! Description (for the Current Period)
|-
|
:''Name''
|
:Equation Constraint Name (as provided by Transpower or user-named)
|-
|
:''Formula''
|
:The Equation specifying how the value of the Constraint is to be calculated
|-
|
:''Active''
|
:When checked indicates ''EMarketOffer'' included the Equation Constraint in the dispatch
|-
|
:''Limit''
|
:The value which the Equation's solution must not exceed (in MW)
|-
|
:''Value''
|
:The Value of the Equation solution (in MW)
|-
|
:''Freedom''
|
:How close (in MW) the current value is to the constraining value
|}

NOTE: Double-clicking on any row will open a separate '''''[[EMO:Equation Constraints Information Window|Equation Constraint Information Window]]''''' for the associated Group Constraint.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:The Display Area Information Grids|Back]]

Special:Badtitle/NS106:Installation Package

2013-05-05T21:45:47Z

Greg:

{{#hidens:}}
Your ''EMarketOffer'' contains the following items:

1. An installation program setup.exe, that installs the ''EMarketOffer'' executable and associated dynamic link libraries

2. In most instances the following data files are also provided:
:*NodePositions.csv containing the position of Market Nodes on the Main Map
:*A set of Map data files contained in a 'Maps' directory
:*SubStationPositions.csv containing the position of Substations on the Main Map

[[EMO:Getting Started|Back]] - [[EMO:EMarketOffer User Manual|Home]]

Special:Badtitle/NS106:System Architecture

2013-05-05T21:43:36Z

Greg: /* Logical Architecture */

{{#hidens:}}
===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.

'''''[[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====
The logical architecture of ''EMarketOffer'' is described in the table below.

{|class="wikitable"
! Component !! Purpose
|-
|
:''Online databases''
|
:''EMarketOffer'' can access networked online (in-house) databases containing market and transmission system data
|-
|
:''Data Files''
|
: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''
|-
|
:''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.
|-
|
:''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.
|-
|
:''Reports and Export Files''
|
:Reports and Export Files are produced by ''EMarketOffer's'' reporting capabilities.
|}

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:System Overview|Back]]

Special:Badtitle/NS106:Release Notes

2013-05-05T21:41:36Z

Greg:

{{#hidens:}}
;EMO 4.11.2 Released 2-May-13
:Bug fixed in demand profile import for Power Flow mode
:Bug fixed in generation profile import for Power Flow mode
:EMO now automatically checks for new grid and reserves data when you start the program (if you leave EMO running overnight then you need to check manually when you come back to it)
:The File Inputs window EMO now shows the date to which input data is believed to be valid
:If you select a day in Market view for which EMO believes there is incomplete data, then "Incomplete Data" will show in read near the top left corner of the Main window. Hover over this and it shows the date to which inputs are available. Click on this and it opens the File Inputs window.
:EMO Help will now take you to this new wiki on the web. The wiki replaces the old online help and the user manual. It is easier and cheaper to maintain than the old manual and help material.
:We advise you check that the excluded items (see the Edit menu) include the following 8 wind farms: MAH, NZW, TAP, TUK, TWC, TWF, WHL, WWD
:Also check that the constraints DCSA_BenP1Aout, DCSA_BenP1Bout, DCSA_HayP1Aout, DCSA_HayP1Bout are excluded.
:EMO 4.11.2 is available at http://www.ellsoft.co.nz/downloads/emo/installemo4.11.2.zip
:The password is available for licensed users from Matt.Woods@energylink.co.nz ddi 03 474 9379.

;EMO 4.10.4 Released 30-Oct-12
:There was a bug in EMO 4.10.3 when loading demand data into a Forecast from a file. EMO would halt with an exception notice from which clicking Continue would not recover. The bug was caused by an array which overflowed when reading the demand from the csv file.

;EMO 4.10.3 Released 31-Jul-12
:Quote of the year from Matt Woods, our Development Manager: “it’s like wading through mud” as he referred to the difficulties he experienced interpreting the data in the SPD daily case data files from which we now extract reserves, grid and constraint data. A long process, but we’re pretty much there now and Matt has even developed a nice developer’s utility for analysing the daily case data.

:The result is that EMO 4.10.3 is now ready for release in beta version (which means that our users need to perform their own testing before it can be confirmed as a final version before it can be confirmed as a final release).

;Previous Release (EMO 4.8.2) will not be Supported Much Longer
:The previous version release in Dec-11 uses a slightly different update mechanism for updating the grid and reserves inputs data files, which won’t be supported once all users on the latest version EMO 4.10.3. For that reason, we want to get all users onto 4.10.3 as quickly as possible.

:Changes in the new version are listed below.

:Input Data
1. Full grid data is available back to 22 July 2009 using the new data from the SPD daily case files (and prior to that using the old grid format data, although we are no longer supporting this older data).

2. Full reserves data is also available back to January 2010 (but not prior to that date).

3. Additional constraints associated with frequency keeping generators (constraining them up or down so that they operate within their FK range) are now captured and available in the constraints files.

4. Additional constraints associated with line outages are now captured and included in the constraints files.

5. The grid and reserves files will be updated most business days.

6. Items 1 – 5 above mean that EMO will be ready to solve the market without any manual input of reserves data or additional constraints.
:To get the latest data files, use File>File Inputs

:Go to the Download tab and click on the button labelled Check for New Files. If you have any problems with this, please contact Matt.

:Really Useful Changes to the User Interface

7. When you create a Scenario EMO will remember whether you last solved with or without reserves, and offer this as the default.

8. You can now add items to Watch Lists from all windows (not just from the map), e.g. right click on a row of offers in the Units window, or on an equation constraint in the Constraints window, and add it to a watch list.

9. The Data Sources window (lower right hand corner, where you see Market, Forecasts, Powerflows and Scenarios in a folder structure) has the ability to filter what you see in this window down to a particular day or trading period. This makes it easier to work with Scenarios and Forecasts.

10. Use Ctrl-Shift-C to copy data and column headings onto the Clipboard.

Other Improvements

11. We’ve started on making improvements to the way the HVDC link is modelled. We had hoped to get all of the changes in this release, but some more subtle changes are required and will be released later.

12. The performance of the solver was improved to handle the many additional constraints now included in the grid, constraints and reserves files.

13. A few bugs were found and fixed including handling of constraints on the HVDC link.

;Important Information About Solves (Forecasts and Scenarios)

:Where there are differences between solves produced by EMO and SPD, these are now likely to be caused by:

1. your input data being wrong or incomplete: this is the single biggest cause of problems with EMO’s solves, and if you have any doubts about your inputs, or which inputs to use, please feel free to call us to discuss;

2. your input data being wrong or incomplete (just repeating this for emphasis);

3. the handling of the HVDC link in EMO is slightly different to the handling in SPD;

4. there is a known issue with EMO’s pricing (but not dispatch) in some cases when a constraint creates a very large price difference across some parts of the grid;

5. EMO is a non-linear model (and hence models losses as quadratic losses) whereas SPD is a linear model and has to approximate quadratic losses with linear losses.

;EMO 4.8.2 Released 23-Dec-11
:This version is no longer supported as it is superseded by EMO 4.10.4.

;Grid Data

*There is a new file for VLRs which, during the VLR trial, will be created manually. When we know what format they will be delivered in on a permanent basis, then the new formatted will be handled in EMO and data capture automated. There is a limitation with the VLRs in this EMO version:
**note that DST changes are not handled exactly using these trial ratings;
*There is a new window for grid data, accessed from File Menu>Grid Data:
**this used to be accessed from File>Data Sources;
**this is the window where you now go to download new grid files;
**this window shows when the default ratings are valid and whether they ratings follow a SSW (summer shoulder winter) or VLR (variable line rating) scheme;
**click on the Download EMO Grid Files button to check for and load new grid files;
**the Use File Sourced Grid button is currently disabled, but files are used anyway;
**the table shows the dates and trading periods (Valid from and Valid to) between which the latest default ratings apply.
*Double click on any line in the table to see the default ratings that apply.
**For VLR lines:
***the table shows 6 MW capacity values and 5 TP (trading periods)
***the MW capacity in the first column applies from TP 1 to the 1 TP before the TP shown in the first TP column, and so on, e.g. “400 15 367 19” would mean 400 MW from TP 1 to 14, 367 MW from TP 15 to 18, and so on;
**For SSW lines the shows the summer, shoulder and winter ratings that apply;
**The Reratings tab shows a limited history of re-ratings that reflect outages or partial outages on the line, as represented in the new grid data files;
**The Dec row may not display correctly (known bug) but nevertheless the VLR ratings are applied correctly in EMO.
*Re-ratings changes:
**EMO now distinguishes changes in the default ratings (SSW or VLR) from other re-ratings, which will make the new re-ratings file smaller;
**even with the new grid files, there is no way of knowing if an outage present in the last few tradings periods in the file will persist, e.g. the permanent split between FHL and WPW. As a solution, any line in an outage (capacity = zero) for the last 48 trading periods in the grid files is assumed to be in outage into the future;
*Delays in getting grid data: users have noted delays of up to 10 days in getting the raw SPD final pricing case data posted on the EA’s web site, which apparently occurred due to the need to handle files manually. But the EA advised us that the process would be automated and the data available from an FTP server: this has now happened. We are working through re-automating the capture process at our end, and this will be completed early next year;
*refreshing grid files: if you think your grid files are corrupt (perhaps you opened one in Excel, modified it and then saved it again), the easiest solution is to delete the file(s) and then get EMO to check for new files from the File Menu>Grid Data window (click the Download EMO Grid Files button).

;Demand Data
:Our '''recommendation''' for demand data continues to be to use the SPD demand data from WITS. Find this by logging onto WITS and selecting '''GXP Demand''' from the '''Market Data''' menu. To get accurate solves in EMO which mirror final prices, you must select Final as the Price Type. You will also need to do a multiple selection to get all nodes.

:'''BE WARNED''' - this data appears to be provisional in many cases and is often updated when final prices are published, so you need to make sure that you have the latest data that is consistent with final prices.

:'''BE WARNED AGAIN''' - if you use any other data set, then you may not get accurate solves with EMO. In many cases, small changes in demand make a big difference to the solve.

This data is what is used in SPD for solving final prices. It is gross demand with some important exceptions:
#wind farm output is netted off GXP/GIP demand. At grid-connected wind farm GIPs, therefore, you will find either negative or zero values. At GXPs with embedded wind farms you will find positive and sometimes also negative values, depending on whether or not the wind farms cause export to the grid;
#generation under 10 MW has a blanket exemption from offering so is netted off GXP demand, in the same way as embedded wind farms.

There are two key aspects to getting the demand right: one is to use the correct demand data, as described above, but the second is ensure that you are not double counting any generators. Whereas generation under 10 MW is not offered and therefore won’t have offers appear in the daily offer data, wind farms over 10 MW do offer and their offers do appear in the daily offer data. If you don’t remove the wind farm offers then you will double count their output in your solves. Solution: make sure you use the demand data described above, and then also exclude all wind farms by going to Edit>Excluded Items. As of this date, the excluded items should include the following:

Embedded Generators Excluded Equations

NZW DCSA_BenP1Aout

TAP DCSA_BenP1Bout

TUK DCSA_HayP1Aout

TWF DCSA_HayP1Bout

WHL

WWD

The wind farms above are NZ Windfarms Te Rere Hau, Te Apiti, te Uku, Tararua Windfarm, White Hill and West Wind. The excluded equations above relate to the HVDC link and are not required by EMO.

'''Enhancements'''

*The offers that you can change in a Scenario are shaded in a much brighter yellow which makes them easier to see on a laptop screen.
Bug fixes:
*the offers graph Edit>Supply & Demand>Offer Graph now loads much quicker
*detection of an infeasible solution was improved to reduce the occurrence of false infeasibilities.

[[EMO:EMarketOffer User Manual|Home]]

Special:Badtitle/NS106:Data Storage Directory Structure

2013-05-05T21:40:00Z

Greg: /* The Inputs Folder */

{{#hidens:}}
''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.

{|class="wikitable"
! 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).

{|class="wikitable"
! Sub-Folder !! File !! Purpose !! Comment
|-
! rowspan="2" | 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 '''''[[EMO:Control_Panel_Components#The_Data_Source_Manager|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.
|-
! rowspan="2" | 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 '''''[[EMO:Control_Panel_Components#The_Data_Source_Manager|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 folders and sub-folders as shown below:
*Demand
*Grid
**Grid\Ellsoft
**Grid\EM6
***Grid\EM6\BaseGrid
***Grid\EM6\Constraints
***Grid\EM6\Equations
***Grid\EM6\Reratings
**Grid\EMO
*Offers
*Reserves

The Grid\EMO and Reserves folders contain the data which is updated on Energy Link's web site each day, and is the grid and reserves data that we continue to support (includes all grid data from 22-Jul-09 and reserves from January 2010). The Grid\Ellsoft and Grid\EM6 folders contain grid data that we no longer support.

== Offers ==
''EMarketOffer'' can load Offers from a database or from file. Offers files in the standard CSV format as provided on http://www.electricityinfo.co.nz 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'''''.

The '''''[[EMO:Input Data|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|300px|thumb|right|Figure 3 - The Maps Data Directory]]

{|class="wikitable"
! 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.

{|class="wikitable"
! File !! Purpose !! Comment
|-
|
:''NodePositions.csv''
|
:Contains Map positions of Market Nodes.
|
:Updated automatically as Nodes are added and re-positioned through the '''''[[EMO:The Presentation Interface|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.

{|class="wikitable"
! 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'''''
|
|}

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Data Management|Back]]

Special:Badtitle/NS106:The File Menu

2013-05-05T21:38:50Z

Greg: /* Purpose */

{{#hidens:}}
The File Menu provides access to the following ''EMarketOffer'' features:
*'''''Database Connections''''' - ''set up and test connections to your local databases''
*'''''File Inputs''''' - ''set up and check the status of grid and reserves data files''
*'''''Map Settings''''' - ''customise the EMO map''
*'''''Save All Settings'''''
*'''''Open EMO Data Directory'''''
*'''''Exit'''''

== The Database Connections Option ==
Please read in conjunction with the section on '''''[[EMO:Connecting to a Database Server|Connecting to a Database Server]]'''''.

=== Input Data Concepts ===
Input data is sourced from databases and from files (see '''[[EMO:Data_Storage_Directory_Structure#Data_Files|Data Files]]'''), or from online database servers.

==== The Database Connection Configuration ====
''EMarketOffer'' supports multiple connections to multiple database servers. Database connectivity is managed through the Database Connection Configuration (DCC). A DCC contains a number of queries which obtain data from one or more databases. While a DCC's queries can access data in more than one database on more than one database server, it is not possible to have more than one query handling data of the same type (e.g. only one query can return Price data, and only one query can return Demand data). To overcome this limitation it is possible to define multiple DCCs. Each configuration will define a different, but complete set of data access queries. ''EMarketOffer'' can use only one DCC at a time, which together with the data files loaded from the '''''Inputs files directory''''', fully determine ''EMarketOffer's'' run-time data environment.

==== The Database Connection ====
A Database Connection is a set of data that describes the addressing, technical and security details required to a specific database on a specific database server. The details are combined in to a specific string format and used to access the required data. A DCC must contain one connection string for every database to be addressed in the configuration.

----
NOTE: Only one Connection per server is required in DCC. Therefore if all your data is stored in the same database then all queries required to access data can use the same Connection.

=== Source Data Administration Window ===

==== Access ====

The '''Database Connections''' option in the '''Main Window File Menu'''.

==== Purpose ====
To manage '''''Database Connection Configurations''''' (DCC).

==== Features ====
{|class="wikitable"
! Feature !! Purpose
|-
!Database Connections Configuration Selector
|
:To set the Current DCC from a drop down box of all currently available DCCs.
|-
!Open configuration Button
|
:Opens the DCC Window for the selected configuration
|-
!New Configuration Button
|
:Opens the New DCC Window Dialogue
|-
!Refresh All Cached Data Button
|
:Reloads all cached data (from file and database)
|}

=== Database Connection Settings Window ===

==== Access ====
Either through the '''Open Configuration Button''' or the '''New Configuration Button''', both on the '''''Source Data Administration Window'''''.

==== Purpose ====
Specification of the database connection and query details used by a Database Connectivity Configuration (DCC).

==== Components and Features ====
{|class="wikitable"
! Component !! Feature !! Purpose
|-
! rowspan="5" | Function Panel
|
:''Test Button''
|
:Tests the validity of the DCC. Test results are displayed in the Status Box (see below)
|-
|
:''Save Button''
|
:Saves the current set of configuration data to file.
----
:NOTE: Connection details changed through the interface will only remain effective for the current session. Unless saved using this button, future sessions will revert to the previously saved details.
|-
|
:''Done Button''
|
:Closes the Data Connections Window retaining any unsaved changes for the current session only.
|-
|
:''Date and Period Selector''
|
:Selects the Date and Trading Period for the data connectivity test.
|-
|
:''Status Box''
|
:Shows the results of the last connectivity test
|-
! rowspan="8" |Database Panel
|
:''Add Button''
|
:Creates a new Database Connection
|-
|
:''Delete Button''
|
:Delete an existing Database Connection
|-
|
:''Name Field''
|
:Contains the name of the Database Connection used to reference the connection in the Query Panel
|-
|
:''Connection Type Field''
|
:Determines the type of connection ''EMarketOffer'' will use for a specific connection. Currently supported connections are:
*OleDB
*ODBC
*Oracle
*SQL
:OleDB and ODBS are generic types and operate with most SQL compliant databases. The Oracle and SQL connection types are specific .net variants for the Oracle and Microsoft SQL server database type. They provide performance superior to the generic connection types and should be used by preference where possible.
|-
|
:''Connection String Field''
|
:Contains the Connection String required to access a database server
|-
|
:''Date Brackets Field''
|
:Contains the symbol used by database server to identify dates within query strings (varies by server type)
|-
|
:''Date Format Field''
|
:Defines how the database server interprets date formats
|-
|
:''Error Field''
|
:Displays results from the last test operation that are specific to this Database Connection
|-
! rowspan="9" | Query Panel
|
:''Entity Type Field''
|
:Informs ''EMarketOffer'' which entity type a query will return data for (either 'Node' or 'Unit')
|-
|
:''Connection Field''
|
:Defines the Connection String, named through the Database Panel which is used by the query
|-
|
:''Query Field''
|
:Contains the text of the query used to access data
|-
|
:''Date Field Field''
|
:Links the column containing the date in the query to ''EMarketOffer's'' date/time handler (allows you to use in-house column names)
|-
|
:''TP Field Field''
|
:Links the Trading Period column in the query to ''EMarketOffer's'' date/time handler (allows you to use in-house column names)
|-
|
:''Entity Field Field''
|
:Links the Entity column (defined in the Entity Type Field) in the query to ''EMarketOffer's'' Entity data handler (allows you to use column names from your in-house databases from queries)
|-
|
:''Other Fields Field''
|
:Links additional columns in the query to ''EMarketOffer's'' Entity.trait data handler
|-
|
:''Error Field''
|
:Displays the results of the last test operation specific to the query
|-
|
:''Sent Query Field''
|
:Displays the actual text of the last query sent to test the database connection (provided as a feature to assist with trouble shooting during setup)
|}

=== Creating A New Database Connection Configuration ===

==== Usage ====
The ability to define multiple Database Connection Configurations allows you to create different data environments for different requirements and easily switch between these environments as needed. Examples of different data environments include:
*The standard (historical) market data in the corporate market database
*A short-term model of a specific market scenario (suitable for business development projects)
*An alternate data source for one or more data streams (e.g. Demand data from SCADA vs SPD Daily Demand)
*A database on a portable computer (suitable for away trips and business presentations)
*A training database of illustrative scenarios


'''>> To create a new Database Connection Configuration'''
#Open the '''''External Data Administration Window''''' from the Data Source option of the '''''Main Window''''' File Menu
#Open the New Connection Configuration Dialogue using the '''New Configuration Button'''
#Enter the name for the new configuration in the '''Connection Configuration Name''' field
#Chose whether to start the new configuration with a copy of the Current Configuration (saves much data re-rentry) or with a blank screen by selecting 'Yes' or 'No' in the ''Copy Current Connection Configuration'' field
#Click '''OK Button''' to accept your entries and open the Database Connection Settings Window or the '''Cancel Button''' to reject entry and return to the '''''External Data Administration Window'''''

== The File Inputs Window ==

==== Access ====
The '''File Inputs''' option in the '''Main Window File Menu.'''

==== Purpose ====
Shows the status of grid and reserves data downloaded in csv files from the Energy Link web site. Since 22-Jul-09 grid and reserves data has been sourced from the "SPD daily case final pricing solve" data files that are made available each day on the Electricity Authority's web site (reserves data is available from January 2010). Each business day, Energy Link downloads the SPD daily case final pricing solves and extracts data that defines the grid, lince capacities, line re-ratings (which are typically line outages), equation constraints, variable line ratings and reserves parameters, by half hour for the entire day. Sometimes provisional data is available but which is subsequently updated with final data.

Whenever you start EMO it automatically chceks for the latest data files on the Energy Link web site, but if you leave EMO running overnight then each subsequent day you need to check the File Inputs window for new data: on the Download tab, click '''Check For New Files'''.

==== Tabs and Features ====
{|class="wikitable"
! Tab !! Feature !! Purpose
|-
! rowspan="3" |Download Tab
|
:''Check For New Files button''
|
:Click on this button to check for new data files
|-
|
:''Web Site Configuration''
|
:The fields in the table under the Check For New Files button are used to configure access to the Energy Link web site: these are set up for the default, but you may need to contact Energy Link for help with more complex configurations required in a corporate environment
|-
|
:''Messages''
|
:The tree structure in this area shows what data is loaded: expand the tree to view the messages. Messages can also be copied to the clipboard by clicking the Copy Messages button.
|-
! rowspan="6" | Grid Tab
|
:''Open Grid Files Directory Button''
|
:Opens the folder which stores grid. You'll most likely see folders for 'EMO', 'EM6' and 'Ellsoft'. The EMO folder holds the grid files which are used from 22-Jul-09. The other two folders hold older grid data.
|-
|
:''Reload Grid Inputs button''
|
:Relaods the grid data from the files in the relevant data folder
|-
|
:''Date and TP boxes''
|
:These show the date and trading period on the Main Window
|-
|
:''Base Grid Source Table''
|
:This table shows the range of dates from the data file from which the displayed date's grid data is drawn from
|-
|
:''Circuits Table''
|
:This table displays the data relating to lines for the displayed date. Double click on any line to get more information including name, dates for which the displayed data is valid, the type of rating (SSW = summer, shoulder, winter; VLR = variable line rating), and the value of the default ratings (click the Annual Ratings button) and any re-ratings that apply (click the Reratings button).
|-
|
:''Messages''
|
:Messages in a tree structure.
|-
! Reserves
|
|
:This window provides access to the reserves data folder and shows the valid date range based on the data files available to EMO.
|}

== The Map Settings Menu Option ==

=== Access ===
The Map settings option from the file Menu on the Main Window.

=== Purpose ===
To configure the appearance of items appearing on the Map.

The Map Settings Window contains two panels accessed through tabs. The panels are:
*Main Map Settings
*Inset Map Settings

Both panels contain exactly the same setting types and options.

=== Editing ===

{|class="wikitable"
|-
|
:''Numeric Field''
|
:Click on the required field and then type the required new number
|-
|
:''Colour''
|
:Place mouse pointer over field to be edited and click on the "..." tab at the right of the cell to open the colour selector
|-
|
:''Font''
|
:Place mouse pointer over field to be edited and click on the "..." tab at the right of the cell to open the font selector
|-
|
:''Check Box''
|
:Simply click on the box to check/un-check
|}

----
NOTE: The reset button restores the Map Settings for the Main or Inset map types back to the default settings.

== The Save All Settings Option ==
''EMarketOffer'' saves changes to Forecast and Powerflow Case Definitions to file on closing. The '''Save All Settings''' option saves any unsaved changes to file without shutting ''EMarketOffer'' down. This feature should be used as a precaution in situations where extensive changes to Forecast and Powerflow Case Definitions are being made.

== The Open EMO Data Directory Option ==
This opens a standard Windows directory window containing the '''''EMO Data Directory''''' (location selected during the installation process). The window provides easy access to important ''EMarketOffer'' data such as Forecast files and the Component Library.

== The Exit Option ==
Selecting this option closes down ''EMarketOffer.'' In doing so the program will save all unsaved data and close all internal files. Output files created and opened through ''EMarketOffer'' (e.g. output csv files) will remain open.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Menu Bar|Back]]

Special:Badtitle/NS106:The File Menu

2013-05-05T21:38:33Z

Greg: /* Purpose */

{{#hidens:}}
The File Menu provides access to the following ''EMarketOffer'' features:
*'''''Database Connections''''' - ''set up and test connections to your local databases''
*'''''File Inputs''''' - ''set up and check the status of grid and reserves data files''
*'''''Map Settings''''' - ''customise the EMO map''
*'''''Save All Settings'''''
*'''''Open EMO Data Directory'''''
*'''''Exit'''''

== The Database Connections Option ==
Please read in conjunction with the section on '''''[[EMO:Connecting to a Database Server|Connecting to a Database Server]]'''''.

=== Input Data Concepts ===
Input data is sourced from databases and from files (see '''[[EMO:Data_Storage_Directory_Structure#Data_Files|Data Files]]'''), or from online database servers.

==== The Database Connection Configuration ====
''EMarketOffer'' supports multiple connections to multiple database servers. Database connectivity is managed through the Database Connection Configuration (DCC). A DCC contains a number of queries which obtain data from one or more databases. While a DCC's queries can access data in more than one database on more than one database server, it is not possible to have more than one query handling data of the same type (e.g. only one query can return Price data, and only one query can return Demand data). To overcome this limitation it is possible to define multiple DCCs. Each configuration will define a different, but complete set of data access queries. ''EMarketOffer'' can use only one DCC at a time, which together with the data files loaded from the '''''Inputs files directory''''', fully determine ''EMarketOffer's'' run-time data environment.

==== The Database Connection ====
A Database Connection is a set of data that describes the addressing, technical and security details required to a specific database on a specific database server. The details are combined in to a specific string format and used to access the required data. A DCC must contain one connection string for every database to be addressed in the configuration.

----
NOTE: Only one Connection per server is required in DCC. Therefore if all your data is stored in the same database then all queries required to access data can use the same Connection.

=== Source Data Administration Window ===

==== Access ====

The '''Database Connections''' option in the '''Main Window File Menu'''.

==== Purpose ====
To manage '''''Database Connection Configurations''''' (DCC).

==== Features ====
{|class="wikitable"
! Feature !! Purpose
|-
!Database Connections Configuration Selector
|
:To set the Current DCC from a drop down box of all currently available DCCs.
|-
!Open configuration Button
|
:Opens the DCC Window for the selected configuration
|-
!New Configuration Button
|
:Opens the New DCC Window Dialogue
|-
!Refresh All Cached Data Button
|
:Reloads all cached data (from file and database)
|}

=== Database Connection Settings Window ===

==== Access ====
Either through the '''Open Configuration Button''' or the '''New Configuration Button''', both on the '''''Source Data Administration Window'''''.

==== Purpose ====
Specification of the database connection and query details used by a Database Connectivity Configuration (DCC).

==== Components and Features ====
{|class="wikitable"
! Component !! Feature !! Purpose
|-
! rowspan="5" | Function Panel
|
:''Test Button''
|
:Tests the validity of the DCC. Test results are displayed in the Status Box (see below)
|-
|
:''Save Button''
|
:Saves the current set of configuration data to file.
----
:NOTE: Connection details changed through the interface will only remain effective for the current session. Unless saved using this button, future sessions will revert to the previously saved details.
|-
|
:''Done Button''
|
:Closes the Data Connections Window retaining any unsaved changes for the current session only.
|-
|
:''Date and Period Selector''
|
:Selects the Date and Trading Period for the data connectivity test.
|-
|
:''Status Box''
|
:Shows the results of the last connectivity test
|-
! rowspan="8" |Database Panel
|
:''Add Button''
|
:Creates a new Database Connection
|-
|
:''Delete Button''
|
:Delete an existing Database Connection
|-
|
:''Name Field''
|
:Contains the name of the Database Connection used to reference the connection in the Query Panel
|-
|
:''Connection Type Field''
|
:Determines the type of connection ''EMarketOffer'' will use for a specific connection. Currently supported connections are:
*OleDB
*ODBC
*Oracle
*SQL
:OleDB and ODBS are generic types and operate with most SQL compliant databases. The Oracle and SQL connection types are specific .net variants for the Oracle and Microsoft SQL server database type. They provide performance superior to the generic connection types and should be used by preference where possible.
|-
|
:''Connection String Field''
|
:Contains the Connection String required to access a database server
|-
|
:''Date Brackets Field''
|
:Contains the symbol used by database server to identify dates within query strings (varies by server type)
|-
|
:''Date Format Field''
|
:Defines how the database server interprets date formats
|-
|
:''Error Field''
|
:Displays results from the last test operation that are specific to this Database Connection
|-
! rowspan="9" | Query Panel
|
:''Entity Type Field''
|
:Informs ''EMarketOffer'' which entity type a query will return data for (either 'Node' or 'Unit')
|-
|
:''Connection Field''
|
:Defines the Connection String, named through the Database Panel which is used by the query
|-
|
:''Query Field''
|
:Contains the text of the query used to access data
|-
|
:''Date Field Field''
|
:Links the column containing the date in the query to ''EMarketOffer's'' date/time handler (allows you to use in-house column names)
|-
|
:''TP Field Field''
|
:Links the Trading Period column in the query to ''EMarketOffer's'' date/time handler (allows you to use in-house column names)
|-
|
:''Entity Field Field''
|
:Links the Entity column (defined in the Entity Type Field) in the query to ''EMarketOffer's'' Entity data handler (allows you to use column names from your in-house databases from queries)
|-
|
:''Other Fields Field''
|
:Links additional columns in the query to ''EMarketOffer's'' Entity.trait data handler
|-
|
:''Error Field''
|
:Displays the results of the last test operation specific to the query
|-
|
:''Sent Query Field''
|
:Displays the actual text of the last query sent to test the database connection (provided as a feature to assist with trouble shooting during setup)
|}

=== Creating A New Database Connection Configuration ===

==== Usage ====
The ability to define multiple Database Connection Configurations allows you to create different data environments for different requirements and easily switch between these environments as needed. Examples of different data environments include:
*The standard (historical) market data in the corporate market database
*A short-term model of a specific market scenario (suitable for business development projects)
*An alternate data source for one or more data streams (e.g. Demand data from SCADA vs SPD Daily Demand)
*A database on a portable computer (suitable for away trips and business presentations)
*A training database of illustrative scenarios


'''>> To create a new Database Connection Configuration'''
#Open the '''''External Data Administration Window''''' from the Data Source option of the '''''Main Window''''' File Menu
#Open the New Connection Configuration Dialogue using the '''New Configuration Button'''
#Enter the name for the new configuration in the '''Connection Configuration Name''' field
#Chose whether to start the new configuration with a copy of the Current Configuration (saves much data re-rentry) or with a blank screen by selecting 'Yes' or 'No' in the ''Copy Current Connection Configuration'' field
#Click '''OK Button''' to accept your entries and open the Database Connection Settings Window or the '''Cancel Button''' to reject entry and return to the '''''External Data Administration Window'''''

== The File Inputs Window ==

==== Access ====
The '''File Inputs''' option in the '''Main Window File Menu.'''

==== Purpose ====
Shows the status of grid and reserves data downloaded in csv files from the Energy Link web site. Since 22-Jul-09 grid and reserves data has been sourced from the "SPD daily case final pricing solve" data files that are made available each day on the Electricity Authority's web site (reserves data is availabel from January 2010). Each business day, Energy Link downloads the SPD daily case final pricing solves and extracts data that defines the grid, lince capacities, line re-ratings (which are typically line outages), equation constraints, variable line ratings and reserves parameters, by half hour for the entire day. Sometimes provisional data is available but which is subsequently updated with final data.

Whenever you start EMO it automatically chceks for the latest data files on the Energy Link web site, but if you leave EMO running overnight then each subsequent day you need to check the File Inputs window for new data: on the Download tab, click '''Check For New Files'''.

==== Tabs and Features ====
{|class="wikitable"
! Tab !! Feature !! Purpose
|-
! rowspan="3" |Download Tab
|
:''Check For New Files button''
|
:Click on this button to check for new data files
|-
|
:''Web Site Configuration''
|
:The fields in the table under the Check For New Files button are used to configure access to the Energy Link web site: these are set up for the default, but you may need to contact Energy Link for help with more complex configurations required in a corporate environment
|-
|
:''Messages''
|
:The tree structure in this area shows what data is loaded: expand the tree to view the messages. Messages can also be copied to the clipboard by clicking the Copy Messages button.
|-
! rowspan="6" | Grid Tab
|
:''Open Grid Files Directory Button''
|
:Opens the folder which stores grid. You'll most likely see folders for 'EMO', 'EM6' and 'Ellsoft'. The EMO folder holds the grid files which are used from 22-Jul-09. The other two folders hold older grid data.
|-
|
:''Reload Grid Inputs button''
|
:Relaods the grid data from the files in the relevant data folder
|-
|
:''Date and TP boxes''
|
:These show the date and trading period on the Main Window
|-
|
:''Base Grid Source Table''
|
:This table shows the range of dates from the data file from which the displayed date's grid data is drawn from
|-
|
:''Circuits Table''
|
:This table displays the data relating to lines for the displayed date. Double click on any line to get more information including name, dates for which the displayed data is valid, the type of rating (SSW = summer, shoulder, winter; VLR = variable line rating), and the value of the default ratings (click the Annual Ratings button) and any re-ratings that apply (click the Reratings button).
|-
|
:''Messages''
|
:Messages in a tree structure.
|-
! Reserves
|
|
:This window provides access to the reserves data folder and shows the valid date range based on the data files available to EMO.
|}

== The Map Settings Menu Option ==

=== Access ===
The Map settings option from the file Menu on the Main Window.

=== Purpose ===
To configure the appearance of items appearing on the Map.

The Map Settings Window contains two panels accessed through tabs. The panels are:
*Main Map Settings
*Inset Map Settings

Both panels contain exactly the same setting types and options.

=== Editing ===

{|class="wikitable"
|-
|
:''Numeric Field''
|
:Click on the required field and then type the required new number
|-
|
:''Colour''
|
:Place mouse pointer over field to be edited and click on the "..." tab at the right of the cell to open the colour selector
|-
|
:''Font''
|
:Place mouse pointer over field to be edited and click on the "..." tab at the right of the cell to open the font selector
|-
|
:''Check Box''
|
:Simply click on the box to check/un-check
|}

----
NOTE: The reset button restores the Map Settings for the Main or Inset map types back to the default settings.

== The Save All Settings Option ==
''EMarketOffer'' saves changes to Forecast and Powerflow Case Definitions to file on closing. The '''Save All Settings''' option saves any unsaved changes to file without shutting ''EMarketOffer'' down. This feature should be used as a precaution in situations where extensive changes to Forecast and Powerflow Case Definitions are being made.

== The Open EMO Data Directory Option ==
This opens a standard Windows directory window containing the '''''EMO Data Directory''''' (location selected during the installation process). The window provides easy access to important ''EMarketOffer'' data such as Forecast files and the Component Library.

== The Exit Option ==
Selecting this option closes down ''EMarketOffer.'' In doing so the program will save all unsaved data and close all internal files. Output files created and opened through ''EMarketOffer'' (e.g. output csv files) will remain open.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Menu Bar|Back]]

Special:Badtitle/NS106:Release Notes

2013-05-05T21:36:33Z

Greg:

{{#hidens:}}
;EMO 4.11.2 Released 2-May-13
:Bug fixed in demand profile import for Power Flow mode
:Bug fixed in generation profile import for Power Flow mode
:EMO now automatically checks for new grid and reserves data when you start the program (if you leave EMO running overnight then you need to check manually when you come back to it)
:The File Inputs window EMO now shows the date to which input data is believed to be valid
:If you select a day in Market view for which EMO believes there is incomplete data, then "Incomplete Data" will show in read near the top left corner of the Main window. Hover over this and it shows the date to which inputs are available. Click on this and it opens the File Inputs window.
:EMO Help will now take you to this new wiki on the web. The wiki replaces the old online help and the user manual. It is easier and cheaper to maintain than the old manual and help material.
:We advise you check that the excluded items (see the Edit menu) include the following 8 wind farms: MAH, NZW, TAP, TUK, TWC, TWF, WHL, WWD
:Also check that the constraints DCSA_BenP1Aout, DCSA_BenP1Bout, DCSA_HayP1Aout, DCSA_HayP1Bout are excluded.
:EMO 4.11.2 is available at http://www.ellsoft.co.nz/downloads/emo/installemo4.11.2.zip
:The password is available for licensed users from Matt.Woods@energylink.co.nz ddi 03 474 9379.

;EMO 4.10.4 Released 30-Oct-12
:There was a bug in EMO 4.10.3 when loading demand data into a Forecast from a file. EMO would halt with an exception notice from which clicking Continue would not recover. The bug was caused by an array which overflowed when reading the demand from the csv file.

;EMO 4.10.3 Released 31-Jul-12
:Quote of the year from Matt Woods, our Development Manager: “it’s like wading through mud” as he referred to the difficulties he experienced interpreting the data in the SPD daily case data files from which we now extract reserves, grid and constraint data. A long process, but we’re pretty much there now and Matt has even developed a nice developer’s utility for analysing the daily case data.

:The result is that EMO 4.10.3 is now ready for release in beta version (which means that our users need to perform their own testing before it can be confirmed as a final version before it can be confirmed as a final release).

;Previous Release (EMO 4.8.2) will not be Supported Much Longer
:The previous version release in Dec-11 uses a slightly different update mechanism for updating the grid and reserves inputs data files, which won’t be supported once all users on the latest version EMO 4.10.3. For that reason, we want to get all users onto 4.10.3 as quickly as possible.

:Changes in the new version are listed below.

:Input Data
1. Full grid data is available back to 22 July 2009 using the new data from the SPD daily case files (and prior to that using the old grid format data).

2. Full reserves data is also available back to January 2010 (but not prior to that date).

3. Additional constraints associated with frequency keeping generators (constraining them up or down so that they operate within their FK range) are now captured and available in the constraints files.

4. Additional constraints associated with line outages are now captured and included in the constraints files.

5. The grid and reserves files will be updated most business days.

6. Items 1 – 5 above mean that EMO will be ready to solve the market without any manual input of reserves data or additional constraints.
:To get the latest data files, use File>File Inputs

:Go to the Download tab and click on the button labelled Check for New Files. If you have any problems with this, please contact Matt.

:Really Useful Changes to the User Interface

7. When you create a Scenario EMO will remember whether you last solved with or without reserves, and offer this as the default.

8. You can now add items to Watch Lists from all windows (not just from the map), e.g. right click on a row of offers in the Units window, or on an equation constraint in the Constraints window, and add it to a watch list.

9. The Data Sources window (lower right hand corner, where you see Market, Forecasts, Powerflows and Scenarios in a folder structure) has the ability to filter what you see in this window down to a particular day or trading period. This makes it easier to work with Scenarios and Forecasts.

10. Use Ctrl-Shift-C to copy data and column headings onto the Clipboard.

Other Improvements

11. We’ve started on making improvements to the way the HVDC link is modelled. We had hoped to get all of the changes in this release, but some more subtle changes are required and will be released later.

12. The performance of the solver was improved to handle the many additional constraints now included in the grid, constraints and reserves files.

13. A few bugs were found and fixed including handling of constraints on the HVDC link.

;Important Information About Solves (Forecasts and Scenarios)

:Where there are differences between solves produced by EMO and SPD, these are now likely to be caused by:

1. your input data being wrong or incomplete: this is the single biggest cause of problems with EMO’s solves, and if you have any doubts about your inputs, or which inputs to use, please feel free to call us to discuss;

2. your input data being wrong or incomplete (just repeating this for emphasis);

3. the handling of the HVDC link in EMO is slightly different to the handling in SPD;

4. there is a known issue with EMO’s pricing (but not dispatch) in some cases when a constraint creates a very large price difference across some parts of the grid;

5. EMO is a non-linear model (and hence models losses as quadratic losses) whereas SPD is a linear model and has to approximate quadratic losses with linear losses.

;EMO 4.8.2 Released 23-Dec-11
:This version is no longer supported as it is superseded by EMO 4.10.4.

;Grid Data

*There is a new file for VLRs which, during the VLR trial, will be created manually. When we know what format they will be delivered in on a permanent basis, then the new formatted will be handled in EMO and data capture automated. There is a limitation with the VLRs in this EMO version:
**note that DST changes are not handled exactly using these trial ratings;
*There is a new window for grid data, accessed from File Menu>Grid Data:
**this used to be accessed from File>Data Sources;
**this is the window where you now go to download new grid files;
**this window shows when the default ratings are valid and whether they ratings follow a SSW (summer shoulder winter) or VLR (variable line rating) scheme;
**click on the Download EMO Grid Files button to check for and load new grid files;
**the Use File Sourced Grid button is currently disabled, but files are used anyway;
**the table shows the dates and trading periods (Valid from and Valid to) between which the latest default ratings apply.
*Double click on any line in the table to see the default ratings that apply.
**For VLR lines:
***the table shows 6 MW capacity values and 5 TP (trading periods)
***the MW capacity in the first column applies from TP 1 to the 1 TP before the TP shown in the first TP column, and so on, e.g. “400 15 367 19” would mean 400 MW from TP 1 to 14, 367 MW from TP 15 to 18, and so on;
**For SSW lines the shows the summer, shoulder and winter ratings that apply;
**The Reratings tab shows a limited history of re-ratings that reflect outages or partial outages on the line, as represented in the new grid data files;
**The Dec row may not display correctly (known bug) but nevertheless the VLR ratings are applied correctly in EMO.
*Re-ratings changes:
**EMO now distinguishes changes in the default ratings (SSW or VLR) from other re-ratings, which will make the new re-ratings file smaller;
**even with the new grid files, there is no way of knowing if an outage present in the last few tradings periods in the file will persist, e.g. the permanent split between FHL and WPW. As a solution, any line in an outage (capacity = zero) for the last 48 trading periods in the grid files is assumed to be in outage into the future;
*Delays in getting grid data: users have noted delays of up to 10 days in getting the raw SPD final pricing case data posted on the EA’s web site, which apparently occurred due to the need to handle files manually. But the EA advised us that the process would be automated and the data available from an FTP server: this has now happened. We are working through re-automating the capture process at our end, and this will be completed early next year;
*refreshing grid files: if you think your grid files are corrupt (perhaps you opened one in Excel, modified it and then saved it again), the easiest solution is to delete the file(s) and then get EMO to check for new files from the File Menu>Grid Data window (click the Download EMO Grid Files button).

;Demand Data
:Our '''recommendation''' for demand data continues to be to use the SPD demand data from WITS. Find this by logging onto WITS and selecting '''GXP Demand''' from the '''Market Data''' menu. To get accurate solves in EMO which mirror final prices, you must select Final as the Price Type. You will also need to do a multiple selection to get all nodes.

:'''BE WARNED''' - this data appears to be provisional in many cases and is often updated when final prices are published, so you need to make sure that you have the latest data that is consistent with final prices.

:'''BE WARNED AGAIN''' - if you use any other data set, then you may not get accurate solves with EMO. In many cases, small changes in demand make a big difference to the solve.

This data is what is used in SPD for solving final prices. It is gross demand with some important exceptions:
#wind farm output is netted off GXP/GIP demand. At grid-connected wind farm GIPs, therefore, you will find either negative or zero values. At GXPs with embedded wind farms you will find positive and sometimes also negative values, depending on whether or not the wind farms cause export to the grid;
#generation under 10 MW has a blanket exemption from offering so is netted off GXP demand, in the same way as embedded wind farms.

There are two key aspects to getting the demand right: one is to use the correct demand data, as described above, but the second is ensure that you are not double counting any generators. Whereas generation under 10 MW is not offered and therefore won’t have offers appear in the daily offer data, wind farms over 10 MW do offer and their offers do appear in the daily offer data. If you don’t remove the wind farm offers then you will double count their output in your solves. Solution: make sure you use the demand data described above, and then also exclude all wind farms by going to Edit>Excluded Items. As of this date, the excluded items should include the following:

Embedded Generators Excluded Equations

NZW DCSA_BenP1Aout

TAP DCSA_BenP1Bout

TUK DCSA_HayP1Aout

TWF DCSA_HayP1Bout

WHL

WWD

The wind farms above are NZ Windfarms Te Rere Hau, Te Apiti, te Uku, Tararua Windfarm, White Hill and West Wind. The excluded equations above relate to the HVDC link and are not required by EMO.

'''Enhancements'''

*The offers that you can change in a Scenario are shaded in a much brighter yellow which makes them easier to see on a laptop screen.
Bug fixes:
*the offers graph Edit>Supply & Demand>Offer Graph now loads much quicker
*detection of an infeasible solution was improved to reduce the occurrence of false infeasibilities.

[[EMO:EMarketOffer User Manual|Home]]

Special:Badtitle/NS106:Release Notes

2013-05-05T21:35:09Z

Greg:

{{#hidens:}}
;EMO 4.11.2 Released 2-May-13
:Bug fixed in demand profile import for Power Flow mode
:Bug fixed in generation profile import for Power Flow mode
:EMO now automatically checks for new grid and reserves data when you start the program (if you leave EMO running overnight then you need to check manually when you come back to it)
:The File Inputs window EMO now shows the date to which input data is believed to be valid
:If you select a day in Market view for which EMO believes there is incomplete data, then "Incomplete Data" will show in read near the top left corner of the Main window. Hover over this and it shows the date to which inputs are available. Click on this and it opens the File Inputs window.
:EMO Help will now take you to this new wiki on the web. The wiki replaces the old online help and the user manual. It is easier and cheaper to maintain than the old manual and help material.
:We advise you check that the excluded items (see the Edit menu) include the following 8 wind farms: MAH, NZW, TAP, TUK, TWC, TWF, WHL, WWD
:Also check that the constraints DCSA_BenP1Aout, DCSA_BenP1Bout, DCSA_HayP1Aout, DCSA_HayP1Bout are excluded.
:EMO 4.11.2 is available at http://www.ellsoft.co.nz/downloads/emo/installemo4.11.2.zip
:The password is available for licensed users from Matt.Woods@energylink.co.nz ddi 03 474 9379.

;EMO 4.10.4 Released 30-Oct-12
:There was a bug in EMO 4.10.3 when loading demand data into a Forecast from a file. EMO would halt with an exception notice from which clicking Continue would not recover. The bug was caused by an array which overflowed when reading the demand from the csv file.

;EMO 4.10.3 Released 31-Jul-12
:Quote of the year from Matt Woods, our Development Manager: “it’s like wading through mud” as he referred to the difficulties he experienced interpreting the data in the SPD daily case data files from which we now extract reserves, grid and constraint data. A long process, but we’re pretty much there now and Matt has even developed a nice developer’s utility for analysing the daily case data.

:The result is that EMO 4.10.3 is now ready for release in beta version (which means that our users need to perform their own testing before it can be confirmed as a final version before it can be confirmed as a final release).

;Previous Release (EMO 4.8.2) will not be Supported Much Longer
:The previous version release in Dec-11 uses a slightly different update mechanism for updating the grid and reserves inputs data files, which won’t be supported once all users on the latest version EMO 4.10 .3. For that reason, we want to get all users onto 4.10.3 as quickly as possible.

:Changes in the new version are listed below.

:Input Data
1. Full grid data is available back to 16 July 2009 using the new data from the SPD daily case files (and prior to that using the old grid format data).

2. Full reserves data is also available back to 22 July 2009 (but not prior to that date).

3. Additional constraints associated with frequency keeping generators (constraining them up or down so that they operate within their FK range) are now captured and available in the constraints files.

4. Additional constraints associated with line outages are now captured and included in the constraints files.

5. The grid and reserves files will be updated most business days.

6. Items 1 – 5 above mean that EMO will be ready to solve the market without any manual input of reserves data or additional constraints.
:To get the latest data files, use File>File Inputs

:Go to the Download tab and click on the button labelled Check for New Files. If you have any problems with this, please contact Matt.

:Really Useful Changes to the User Interface

7. When you create a Scenario EMO will remember whether you last solved with or without reserves, and offer this as the default.

8. You can now add items to Watch Lists from all windows (not just from the map), e.g. right click on a row of offers in the Units window, or on an equation constraint in the Constraints window, and add it to a watch list.

9. The Data Sources window (lower right hand corner, where you see Market, Forecasts, Powerflows and Scenarios in a folder structure) has the ability to filter what you see in this window down to a particular day or trading period. This makes it easier to work with Scenarios and Forecasts.

10. Use Ctrl-Shift-C to copy data and column headings onto the Clipboard.

Other Improvements

11. We’ve started on making improvements to the way the HVDC link is modelled. We had hoped to get all of the changes in this release, but some more subtle changes are required and will be released later.

12. The performance of the solver was improved to handle the many additional constraints now included in the grid, constraints and reserves files.

13. A few bugs were found and fixed including handling of constraints on the HVDC link.

;Important Information About Solves (Forecasts and Scenarios)

:Where there are differences between solves produced by EMO and SPD, these are now likely to be caused by:

1. your input data being wrong or incomplete: this is the single biggest cause of problems with EMO’s solves, and if you have any doubts about your inputs, or which inputs to use, please feel free to call us to discuss;

2. your input data being wrong or incomplete (just repeating this for emphasis);

3. the handling of the HVDC link in EMO is slightly different to the handling in SPD;

4. there is a known issue with EMO’s pricing (but not dispatch) in some cases when a constraint creates a very large price difference across some parts of the grid;

5. EMO is a non-linear model (and hence models losses as quadratic losses) whereas SPD is a linear model and has to approximate quadratic losses with linear losses.

;EMO 4.8.2 Released 23-Dec-11
:This version is no longer supported as it is superseded by EMO 4.10.4.

;Grid Data

*There is a new file for VLRs which, during the VLR trial, will be created manually. When we know what format they will be delivered in on a permanent basis, then the new formatted will be handled in EMO and data capture automated. There is a limitation with the VLRs in this EMO version:
**note that DST changes are not handled exactly using these trial ratings;
*There is a new window for grid data, accessed from File Menu>Grid Data:
**this used to be accessed from File>Data Sources;
**this is the window where you now go to download new grid files;
**this window shows when the default ratings are valid and whether they ratings follow a SSW (summer shoulder winter) or VLR (variable line rating) scheme;
**click on the Download EMO Grid Files button to check for and load new grid files;
**the Use File Sourced Grid button is currently disabled, but files are used anyway;
**the table shows the dates and trading periods (Valid from and Valid to) between which the latest default ratings apply.
*Double click on any line in the table to see the default ratings that apply.
**For VLR lines:
***the table shows 6 MW capacity values and 5 TP (trading periods)
***the MW capacity in the first column applies from TP 1 to the 1 TP before the TP shown in the first TP column, and so on, e.g. “400 15 367 19” would mean 400 MW from TP 1 to 14, 367 MW from TP 15 to 18, and so on;
**For SSW lines the shows the summer, shoulder and winter ratings that apply;
**The Reratings tab shows a limited history of re-ratings that reflect outages or partial outages on the line, as represented in the new grid data files;
**The Dec row may not display correctly (known bug) but nevertheless the VLR ratings are applied correctly in EMO.
*Re-ratings changes:
**EMO now distinguishes changes in the default ratings (SSW or VLR) from other re-ratings, which will make the new re-ratings file smaller;
**even with the new grid files, there is no way of knowing if an outage present in the last few tradings periods in the file will persist, e.g. the permanent split between FHL and WPW. As a solution, any line in an outage (capacity = zero) for the last 48 trading periods in the grid files is assumed to be in outage into the future;
*Delays in getting grid data: users have noted delays of up to 10 days in getting the raw SPD final pricing case data posted on the EA’s web site, which apparently occurred due to the need to handle files manually. But the EA advised us that the process would be automated and the data available from an FTP server: this has now happened. We are working through re-automating the capture process at our end, and this will be completed early next year;
*refreshing grid files: if you think your grid files are corrupt (perhaps you opened one in Excel, modified it and then saved it again), the easiest solution is to delete the file(s) and then get EMO to check for new files from the File Menu>Grid Data window (click the Download EMO Grid Files button).

;Demand Data
:Our '''recommendation''' for demand data continues to be to use the SPD demand data from WITS. Find this by logging onto WITS and selecting '''GXP Demand''' from the '''Market Data''' menu. To get accurate solves in EMO which mirror final prices, you must select Final as the Price Type. You will also need to do a multiple selection to get all nodes.

:'''BE WARNED''' - this data appears to be provisional in many cases and is often updated when final prices are published, so you need to make sure that you have the latest data that is consistent with final prices.

:'''BE WARNED AGAIN''' - if you use any other data set, then you may not get accurate solves with EMO. In many cases, small changes in demand make a big difference to the solve.

This data is what is used in SPD for solving final prices. It is gross demand with some important exceptions:
#wind farm output is netted off GXP/GIP demand. At grid-connected wind farm GIPs, therefore, you will find either negative or zero values. At GXPs with embedded wind farms you will find positive and sometimes also negative values, depending on whether or not the wind farms cause export to the grid;
#generation under 10 MW has a blanket exemption from offering so is netted off GXP demand, in the same way as embedded wind farms.

There are two key aspects to getting the demand right: one is to use the correct demand data, as described above, but the second is ensure that you are not double counting any generators. Whereas generation under 10 MW is not offered and therefore won’t have offers appear in the daily offer data, wind farms over 10 MW do offer and their offers do appear in the daily offer data. If you don’t remove the wind farm offers then you will double count their output in your solves. Solution: make sure you use the demand data described above, and then also exclude all wind farms by going to Edit>Excluded Items. As of this date, the excluded items should include the following:

Embedded Generators Excluded Equations

NZW DCSA_BenP1Aout

TAP DCSA_BenP1Bout

TUK DCSA_HayP1Aout

TWF DCSA_HayP1Bout

WHL

WWD

The wind farms above are NZ Windfarms Te Rere Hau, Te Apiti, te Uku, Tararua Windfarm, White Hill and West Wind. The excluded equations above relate to the HVDC link and are not required by EMO.

'''Enhancements'''

*The offers that you can change in a Scenario are shaded in a much brighter yellow which makes them easier to see on a laptop screen.
Bug fixes:
*the offers graph Edit>Supply & Demand>Offer Graph now loads much quicker
*detection of an infeasible solution was improved to reduce the occurrence of false infeasibilities.

[[EMO:EMarketOffer User Manual|Home]]

Special:Badtitle/NS106:The File Menu

2013-05-05T21:28:12Z

Greg: /* Purpose */

{{#hidens:}}
The File Menu provides access to the following ''EMarketOffer'' features:
*'''''Database Connections''''' - ''set up and test connections to your local databases''
*'''''File Inputs''''' - ''set up and check the status of grid and reserves data files''
*'''''Map Settings''''' - ''customise the EMO map''
*'''''Save All Settings'''''
*'''''Open EMO Data Directory'''''
*'''''Exit'''''

== The Database Connections Option ==
Please read in conjunction with the section on '''''[[EMO:Connecting to a Database Server|Connecting to a Database Server]]'''''.

=== Input Data Concepts ===
Input data is sourced from databases and from files (see '''[[EMO:Data_Storage_Directory_Structure#Data_Files|Data Files]]'''), or from online database servers.

==== The Database Connection Configuration ====
''EMarketOffer'' supports multiple connections to multiple database servers. Database connectivity is managed through the Database Connection Configuration (DCC). A DCC contains a number of queries which obtain data from one or more databases. While a DCC's queries can access data in more than one database on more than one database server, it is not possible to have more than one query handling data of the same type (e.g. only one query can return Price data, and only one query can return Demand data). To overcome this limitation it is possible to define multiple DCCs. Each configuration will define a different, but complete set of data access queries. ''EMarketOffer'' can use only one DCC at a time, which together with the data files loaded from the '''''Inputs files directory''''', fully determine ''EMarketOffer's'' run-time data environment.

==== The Database Connection ====
A Database Connection is a set of data that describes the addressing, technical and security details required to a specific database on a specific database server. The details are combined in to a specific string format and used to access the required data. A DCC must contain one connection string for every database to be addressed in the configuration.

----
NOTE: Only one Connection per server is required in DCC. Therefore if all your data is stored in the same database then all queries required to access data can use the same Connection.

=== Source Data Administration Window ===

==== Access ====

The '''Database Connections''' option in the '''Main Window File Menu'''.

==== Purpose ====
To manage '''''Database Connection Configurations''''' (DCC).

==== Features ====
{|class="wikitable"
! Feature !! Purpose
|-
!Database Connections Configuration Selector
|
:To set the Current DCC from a drop down box of all currently available DCCs.
|-
!Open configuration Button
|
:Opens the DCC Window for the selected configuration
|-
!New Configuration Button
|
:Opens the New DCC Window Dialogue
|-
!Refresh All Cached Data Button
|
:Reloads all cached data (from file and database)
|}

=== Database Connection Settings Window ===

==== Access ====
Either through the '''Open Configuration Button''' or the '''New Configuration Button''', both on the '''''Source Data Administration Window'''''.

==== Purpose ====
Specification of the database connection and query details used by a Database Connectivity Configuration (DCC).

==== Components and Features ====
{|class="wikitable"
! Component !! Feature !! Purpose
|-
! rowspan="5" | Function Panel
|
:''Test Button''
|
:Tests the validity of the DCC. Test results are displayed in the Status Box (see below)
|-
|
:''Save Button''
|
:Saves the current set of configuration data to file.
----
:NOTE: Connection details changed through the interface will only remain effective for the current session. Unless saved using this button, future sessions will revert to the previously saved details.
|-
|
:''Done Button''
|
:Closes the Data Connections Window retaining any unsaved changes for the current session only.
|-
|
:''Date and Period Selector''
|
:Selects the Date and Trading Period for the data connectivity test.
|-
|
:''Status Box''
|
:Shows the results of the last connectivity test
|-
! rowspan="8" |Database Panel
|
:''Add Button''
|
:Creates a new Database Connection
|-
|
:''Delete Button''
|
:Delete an existing Database Connection
|-
|
:''Name Field''
|
:Contains the name of the Database Connection used to reference the connection in the Query Panel
|-
|
:''Connection Type Field''
|
:Determines the type of connection ''EMarketOffer'' will use for a specific connection. Currently supported connections are:
*OleDB
*ODBC
*Oracle
*SQL
:OleDB and ODBS are generic types and operate with most SQL compliant databases. The Oracle and SQL connection types are specific .net variants for the Oracle and Microsoft SQL server database type. They provide performance superior to the generic connection types and should be used by preference where possible.
|-
|
:''Connection String Field''
|
:Contains the Connection String required to access a database server
|-
|
:''Date Brackets Field''
|
:Contains the symbol used by database server to identify dates within query strings (varies by server type)
|-
|
:''Date Format Field''
|
:Defines how the database server interprets date formats
|-
|
:''Error Field''
|
:Displays results from the last test operation that are specific to this Database Connection
|-
! rowspan="9" | Query Panel
|
:''Entity Type Field''
|
:Informs ''EMarketOffer'' which entity type a query will return data for (either 'Node' or 'Unit')
|-
|
:''Connection Field''
|
:Defines the Connection String, named through the Database Panel which is used by the query
|-
|
:''Query Field''
|
:Contains the text of the query used to access data
|-
|
:''Date Field Field''
|
:Links the column containing the date in the query to ''EMarketOffer's'' date/time handler (allows you to use in-house column names)
|-
|
:''TP Field Field''
|
:Links the Trading Period column in the query to ''EMarketOffer's'' date/time handler (allows you to use in-house column names)
|-
|
:''Entity Field Field''
|
:Links the Entity column (defined in the Entity Type Field) in the query to ''EMarketOffer's'' Entity data handler (allows you to use column names from your in-house databases from queries)
|-
|
:''Other Fields Field''
|
:Links additional columns in the query to ''EMarketOffer's'' Entity.trait data handler
|-
|
:''Error Field''
|
:Displays the results of the last test operation specific to the query
|-
|
:''Sent Query Field''
|
:Displays the actual text of the last query sent to test the database connection (provided as a feature to assist with trouble shooting during setup)
|}

=== Creating A New Database Connection Configuration ===

==== Usage ====
The ability to define multiple Database Connection Configurations allows you to create different data environments for different requirements and easily switch between these environments as needed. Examples of different data environments include:
*The standard (historical) market data in the corporate market database
*A short-term model of a specific market scenario (suitable for business development projects)
*An alternate data source for one or more data streams (e.g. Demand data from SCADA vs SPD Daily Demand)
*A database on a portable computer (suitable for away trips and business presentations)
*A training database of illustrative scenarios


'''>> To create a new Database Connection Configuration'''
#Open the '''''External Data Administration Window''''' from the Data Source option of the '''''Main Window''''' File Menu
#Open the New Connection Configuration Dialogue using the '''New Configuration Button'''
#Enter the name for the new configuration in the '''Connection Configuration Name''' field
#Chose whether to start the new configuration with a copy of the Current Configuration (saves much data re-rentry) or with a blank screen by selecting 'Yes' or 'No' in the ''Copy Current Connection Configuration'' field
#Click '''OK Button''' to accept your entries and open the Database Connection Settings Window or the '''Cancel Button''' to reject entry and return to the '''''External Data Administration Window'''''

== The File Inputs Window ==

==== Access ====
The '''File Inputs''' option in the '''Main Window File Menu.'''

==== Purpose ====
Shows the status of grid and reserves data downloaded in csv files from the Energy Link web site. Since 22-Jul-09 grid and reserves data has been sourced from the "SPD daily case final pricing solve" data files that are made available each day on the Electricity Authority's web site. Each business day, Energy Link downloads the SPD daily case final pricing solves and extracts data that defines the grid, lince capacities, line re-ratings (which are typically line outages), equation constraints, variable line ratings and reserves parameters, by half hour for the entire day. Sometimes provisional data is available but which is subsequently updated with final data.

Whenever you start EMO it automatically chceks for the latest data files on the Energy Link web site, but if you leave EMO running overnight then each subsequent day you need to check the File Inputs window for new data: on the Download tab, click '''Check For New Files'''.

==== Tabs and Features ====
{|class="wikitable"
! Tab !! Feature !! Purpose
|-
! rowspan="3" |Download Tab
|
:''Check For New Files button''
|
:Click on this button to check for new data files
|-
|
:''Web Site Configuration''
|
:The fields in the table under the Check For New Files button are used to configure access to the Energy Link web site: these are set up for the default, but you may need to contact Energy Link for help with more complex configurations required in a corporate environment
|-
|
:''Messages''
|
:The tree structure in this area shows what data is loaded: expand the tree to view the messages. Messages can also be copied to the clipboard by clicking the Copy Messages button.
|-
! rowspan="6" | Grid Tab
|
:''Open Grid Files Directory Button''
|
:Opens the folder which stores grid. You'll most likely see folders for 'EMO', 'EM6' and 'Ellsoft'. The EMO folder holds the grid files which are used from 22-Jul-09. The other two folders hold older grid data.
|-
|
:''Reload Grid Inputs button''
|
:Relaods the grid data from the files in the relevant data folder
|-
|
:''Date and TP boxes''
|
:These show the date and trading period on the Main Window
|-
|
:''Base Grid Source Table''
|
:This table shows the range of dates from the data file from which the displayed date's grid data is drawn from
|-
|
:''Circuits Table''
|
:This table displays the data relating to lines for the displayed date. Double click on any line to get more information including name, dates for which the displayed data is valid, the type of rating (SSW = summer, shoulder, winter; VLR = variable line rating), and the value of the default ratings (click the Annual Ratings button) and any re-ratings that apply (click the Reratings button).
|-
|
:''Messages''
|
:Messages in a tree structure.
|-
! Reserves
|
|
:This window provides access to the reserves data folder and shows the valid date range based on the data files available to EMO.
|}

== The Map Settings Menu Option ==

=== Access ===
The Map settings option from the file Menu on the Main Window.

=== Purpose ===
To configure the appearance of items appearing on the Map.

The Map Settings Window contains two panels accessed through tabs. The panels are:
*Main Map Settings
*Inset Map Settings

Both panels contain exactly the same setting types and options.

=== Editing ===

{|class="wikitable"
|-
|
:''Numeric Field''
|
:Click on the required field and then type the required new number
|-
|
:''Colour''
|
:Place mouse pointer over field to be edited and click on the "..." tab at the right of the cell to open the colour selector
|-
|
:''Font''
|
:Place mouse pointer over field to be edited and click on the "..." tab at the right of the cell to open the font selector
|-
|
:''Check Box''
|
:Simply click on the box to check/un-check
|}

----
NOTE: The reset button restores the Map Settings for the Main or Inset map types back to the default settings.

== The Save All Settings Option ==
''EMarketOffer'' saves changes to Forecast and Powerflow Case Definitions to file on closing. The '''Save All Settings''' option saves any unsaved changes to file without shutting ''EMarketOffer'' down. This feature should be used as a precaution in situations where extensive changes to Forecast and Powerflow Case Definitions are being made.

== The Open EMO Data Directory Option ==
This opens a standard Windows directory window containing the '''''EMO Data Directory''''' (location selected during the installation process). The window provides easy access to important ''EMarketOffer'' data such as Forecast files and the Component Library.

== The Exit Option ==
Selecting this option closes down ''EMarketOffer.'' In doing so the program will save all unsaved data and close all internal files. Output files created and opened through ''EMarketOffer'' (e.g. output csv files) will remain open.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Menu Bar|Back]]

Special:Badtitle/NS106:Input Data

2013-05-05T21:27:37Z

Greg: /* Transmission System Data */

{{#hidens:}}
The input data types processed by ''EMarketOffer:''
*'''''Generation Data'''''
*'''''Price data
*'''''Offers data
*'''''Demand data
*'''''Transmission data
*'''''Reserves data
*'''''Static (user-defined) data'''''

==Generation Data==
Generation data is used:
*As information-only in the'''''Units Information Grid''''' for the '''''Market Data Source'''''
*To calculate Powerflows for the Market Data Source
*To calculate Powerflows for the Powerflow Case Data Source

=== Loading Generation Data ===
Historical Generation data can be loaded from an online database (see '''''[[EMO:Connecting_to_a_Database_Server|Connecting to a Networked Database]]'''''). Historical or user-created Generation data can be loaded into '''''Powerflow Case Definitions''''' from file as a '''''generation profile'''''.

==Price Data==
Historical Price data is used as information-only in the '''''Units Information Grid''''' for the '''''Market Data Source'''''

=== Loading Historical Price Data ===
Historical Price data can only be loaded into ''EMarketOffer'' through direct connection to an online database (see '''''[[EMO:Connecting_to_a_Database_Server|Connecting to a Networked Database]]''''').

== Offers Data ==
Historical Offers data is used:
*As information-only in the '''''[[EMO:Units Information Grid|Units Information Grid]]''''' for the '''''Market Data Source'''''
*As input into the seven-day '''''Offers Profile''''' in '''''forecast Definitions'''''
*As input into '''''Scenario Data Sources''''' based on historical Trading Periods (when available)

----
NOTE: ''EMarketOffer'' does NOT use Offers to calculate Powerflows for historical Trading Periods.
----

===Loading Historical Offers Data===
Historical Offers can be loaded either through:
*'''''direct connection to an online database'''''
*from pre-formatted '''''Offers files'''''
*Offers profile files (Forecast Definitions only)

Pre-formatted Offers files must use the same formatting used by the market for providing Offers data and be named in the following manner:

:'''Offersyyyymmdd.csv

Where:
:''''Offers'''' is the text 'Offers'
:''''yyyy'''' is the numerical 4 digit year (e.g. 2012)
:''''mm'''' is the numerical 2 digit month (e.g. 06)
:''''dd'''' is the numerical 2 digit day (e.g. 08)

You can download Offers files directly from http://www.electricityinfo.co.nz and use them without further editing (once renamed).

----
NOTE: Date format is important - the date in the file name is used to allocate offers data to specific week days. One Offers files cannot contain data for periods from two different calendar days.
----

Offers files are processed row by row without regard to overall integrity. This allows you to edit the raw Offers files prior to loading to:
*Alter Offer Prices and Quantities
*Restrict the number of offered periods to less than a full day
*Restrict the number of offering Generation Units to less than those actually offering on the day

The formatting for the Offers files can be found in '''''[[EMO:Offers File Format|Offers File Format]].'''''

Offers profile files can also be used. An Offers profile file uses a proprietary format designed to capture a complete seven-day profile suitable for importing into a Forecast Definition. The format of this file can be found in '''''[[EMO:Offers Profile File Format|Offers Profile File Format]].'''''

===Using Offers with Forecast Definitions===
''EMarketOffer's'' Forecast Definitions are based on a weekly Offers Profile, organised by day of week (as opposed to date). Offers for no more than seven consecutive days can be loaded into a Forecast Definition.

The following points should be noted:
*Where a '''''Forecast Effective Date Range''''' extends beyond seven days, Offers from the loaded profile will be re-used (by corresponding day of the week) from day eight onward
*Where Offers for fewer than seven days are loaded into a Forecast Definition , any periods in the Effective Date Range not covered by the loaded Offers will fail to dispatch
*New Offers can be loaded over the top of existing Offers. examples of how this might be useful include:
**producing modified historical offers by loading a week profile from the database and then loading an edited and/or partial Offers file containing different data
**Modifying a single generator's offering behaviour by loading an edited file containing Offers for only the Generation Unit and specific Trading Periods of interest leaving all previously loaded Offers (for this or any other generator) unchanged.
*Offers files are loaded consecutively by date from earliest to latest. Loading more than seven-days of Offers data from file will cause over-writing of the weekly Offer profile. for example if ten days of offers are loaded from file the first three days will be lost.

== Demand Data ==
Historical Demand data is used:
*As input into calculating the Powerflows in the '''''[[EMO:Data_Sources#Market_Mode|Market Data Source]]'''''
*As input into the seven-day Demand profile for '''''[[EMO:The Forecast Definition Window|Forecast Definitions]]''''' and '''''[[EMO:Powerflow_Analysis|Powerflow Cases]]'''''

===Which Demand data to use with ''EMarketOffer?''===
For best results ''EMarketOffer's'' database connection should be configured to use reconciled SPD Daily Demand data (available to subscribed WITS users) as this most closely matches the historical Offers used in final dispatch. However, ''EMarketOffer'' can be configured to work with SCADA or other Demand data. Where SCADA data is used the net final Load at each Market Node should also be used.

===Loading Historical Demand Data===
Historical Demand can be loaded into ''EMarketOffer'' either through:
*'''''direct connection to an online database''''',
*from pre-formatted '''''Demand files'''''
*from demand profile files

===Pre-formatted files===
Pre-formatted Demand files must comply with ''EMarketOffer's'' Demand file format (see '''''[[EMO:Demand File Format|Demand File Format]]''''') and named in the following manner:

:'''Loadyyyymmdd.csv'''

Where:
:''''Load'''' is the text 'Load'
:''''yyyy'''' is the numerical 4 digit year (e.g. 2012)
:''''mm'''' is the numerical 2 digit month (e.g. 06)
:''''dd'''' is the numerical 2 digit day (e.g. 08)

----
NOTE: The date format is important. ''EMarketOffer'' uses the date in the file name to allocate the Demand data to specific days. One demand file cannot contain data for periods from more than one calendar day.
----

''EMarketOffer'' processes the Demand files row by row and does not check overall integrity. This allows you to edit the raw files prior to loading into ''EMarketOffer'' to:
*Alter Demand Quantities
*Restrict the number of Demand periods to less than a full day
*Restrict the number of Demand Nodes to less than those actually drawing down power on the day

The formatting for the Demand files can be found in '''''[[EMO:Demand File Format|Demand File Formats]]'''''.

===Demand Profile Files===
A Demand profile file uses a proprietary format designed to capture a complete seven-day profile suitable for importing into a Forecast Definition or Powerflow Case. The format of this file can be found in '''''[[EMO:Demand Profile File Format|Demand Profile File Formats]]'''''.

===Using Demand with Forecast Definitions and Powerflow Cases===
''EMarketOffer's'' Forecast and Powerflow Case Definitions are based on a weekly Demand profile, by day of week. Demand figures for no more than seven consecutive days can be loaded into a Definition.

The following points should be noted:
*Where a Forecast or Powerflow Case '''''Effective Date Range''''' extends beyond seven days ''EMarketOffer'' will re-use the loaded Demand by day of the week from the profile for all weeks in the Effective Date Range.
*Where Demand for fewer than seven days is loaded into a Definition, any periods in the Effective Date Range not covered by the loaded Demand will fail to dispatch
*New Demand data can be loaded over the top of existing data. For example it is possible to load a full week profile from the database and then load a partial Demand file that has been edited to contain Demand for a single Node for a specific number of periods on a specific day. In this case only those periods for the selected Node will be overwritten with new data, all other Demand figures will remain unchanged.
*Demand files are loaded consecutively by date from earliest to latest. '''''Loading more than seven days of data from file''''' will cause over-writing of the weekly Demand profile. For example if ten days of Demand figures are loaded from file the first three days will be lost.
*When '''''loading Demand data from database''''' it is possible to specify a date range covering several weeks of Demand data. In this case an averaged Demand profile is created by day-of-the-week and Trading Period. It is not possible to create averaged Demand profiles by loading from file.

== Transmission System Data ==
''EMarketOffer'' can create a set of grid data (circuit details, line re-ratings and constraints) at run time from one of four sources:
#Historical transmission system data files provided by Energy Link
#Transmission system files sourced through the EM6 web site operated by Transpower division EMS
#In-house databases
#The files available each business day from the Energy Link web site (for grids from 22-Jul-09 onward)

'''Of the sources above, 1 - 3 are legacy data sources and we have stopped supporting them as the data available from EM6 is incomplete for the purposes required in ''EMarketOffer'', and because we have gone to great effort to provide daily grid and reserves files that include all data reuired to solve the market by half hour. Only the daily updated grid files from 22-Jul-09 are now supported (though the other types of existing grid data can still be used in the meantime). The daily updated files also include full reserves data.'''

On startup ''EMarketOffer'' checks the Energy Link web site for the new grid and reserves data and automatically downloads files if you are not up to date.

The '''Connect Grid Data Tables''' check box in the '''''Database Connection Settings''''' window can be checked if you wish to use grid data from your own database, subject to the following:
----
'''WARNING!''' ''EMarketOffer'' will ignore any database links for grid data if grid data can be obtained from files. To use grid data from your own database you must delete any grid data files that are downloaded by ''EMarketOffer'' on startup.
----

----
'''DISCLAIMER''': Energy Link takes a great deal of care in extracting grid and reserves data from the SPD daily final pricing case data files provided on the Electricity Authority's web site. However, we are totally unsupported in this endeavour and cannot in anyway guarantee the accuracy of the data we provide to ''EMarketOffer'' users. We provide the data in good faith and will not be held liable for the use of the data in ''EMarketOffer'' or in any other application, for the accuracy of the data, or for any special or consequential damages or losses resulting in any way whatsoever from the use of the data.
----

The following descriptions of grid data relate only to the data which is updated on Energy Link's web site each business day. For assistance with earlier versions of grid data (for all periods up to and including 15-Jul-09) you need to contact Energy Link or refer to an earlier ''EmarketOffer'' User Manual.

The SPD daily final pricing case data files are parsed by Energy Link each bussiness day to extract grid and reserves data. Grid data is stored in files with names:
*BaseGrid_yyyymmdd_yyyymmdd.csv contain the base data for circuits, transformers and other key grid elements by half hour
*Equations_yyyymmdd_yyyymmdd.csv contain the equation constraints by half hour
*Reratings_yyyymmdd_yyyymmdd.csv contain circuit and transformer outages and reratings by half hour

In each case, the two dates show the range of dates covered by each file (from date first, to date second). The files are added to day by day but do not contain more than one year of data each.

In the same folder as the files above, you will also find VLRs_yyyymmdd_yyyymmdd.csv files which contain the VLR ratings for a small number of circuits which are currently being trialled: this data comes from Transpower's web site and are checked periodically.

== Reserves Data ==
Reserves data is collected from the same source as the grid data, and is stored in two sets of files:
*Reserves_yyyymmdd_yyyymmdd.csv
*RiskSetters_yyyymmdd_yyyymmdd.csv

In this case the files store reserves data for up to one month at a time.

== Static (User-Defined) Data ==
''EMarketOffer'' uses static data to calculate or organise the dynamic data produced by the Run (see the Circuit Item example below). Static data tends to remain unchanged between the Trading Periods contained in a Run,

{|class="wikitable"
! Item !! Description !! Static Data !! Dynamic Data
|-
! Circuit
|
:A branch (Circuit) conducting power on the NZ Transmission System
|
*Name
*From Node
*To Node
*Contributes to HVDC (Yes/No)
*Resistance
*Reactance
*Capacity (Summer/Winter)
|
*Powerflow
*Price Separation
*Losses
*Loading
|}

Modelled Items are defined by static data. Some Items are global, i.e. common for all Definitions, and their associated static data must be pre-defined (e.g. '''''Companies''''' and '''''Regions''''') Most Modelled Items, and their static data, are created for each new Definition (e.g. Generators or Nodes).

----
NOTE: To avoid time-consuming effort re-creating data in Definitions, Modelled Items, with their static data descriptions, can be imported into a Definition using ''EMarketOffer's'', '''''data loading functions''''', once loaded these Items can be modified, added to or removed with the Definition editor.
----

Functionality to maintain global static data can be accessed through the '''''[[EMO:The Edit Menu|Edit Menu]]''''' in the Main Window.

Static data in Definitions can be accessed through the '''''[[EMO:The Forecast Definition Window|Forecast Definition Window]]''''' or the '''''[[EMO:The Powerflow Case Definition Window|Powerflow Case Definition Window]]'''''.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Data Management|Back]]

Special:Badtitle/NS106:Data Storage Directory Structure

2013-05-05T21:27:00Z

Greg: /* The Inputs Folder */

{{#hidens:}}
''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.

{|class="wikitable"
! 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).

{|class="wikitable"
! Sub-Folder !! File !! Purpose !! Comment
|-
! rowspan="2" | 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 '''''[[EMO:Control_Panel_Components#The_Data_Source_Manager|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.
|-
! rowspan="2" | 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 '''''[[EMO:Control_Panel_Components#The_Data_Source_Manager|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 fodlers and sub-folders as shown below:
*Demand
*Grid
**Grid\Ellsoft
**Grid\EM6
***Grid\EM6\BaseGrid
***Grid\EM6\Constraints
***Grid\EM6\Equations
***Grid\EM6\Reratings
**Grid\EMO
*Offers
*Reserves

The Grid\EMO and Reserves folders contain the data which is updated on Energy Link's web site each day, and is the grid and reserves data that we continue to support (includes all data from 22-Jul-09). The Grid\Ellsoft and Grid\EM6 folders contain grid data that we no longer support.

== Offers ==
''EMarketOffer'' can load Offers from a database or from file. Offers files in the standard CSV format as provided on http://www.electricityinfo.co.nz 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'''''.

The '''''[[EMO:Input Data|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|300px|thumb|right|Figure 3 - The Maps Data Directory]]

{|class="wikitable"
! 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.

{|class="wikitable"
! File !! Purpose !! Comment
|-
|
:''NodePositions.csv''
|
:Contains Map positions of Market Nodes.
|
:Updated automatically as Nodes are added and re-positioned through the '''''[[EMO:The Presentation Interface|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.

{|class="wikitable"
! 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'''''
|
|}

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Data Management|Back]]

Special:Badtitle/NS106:Data Initialisation

2013-05-05T21:26:09Z

Greg: /* Market Data */

{{#hidens:}}
''EMarketOffer'' requires three types of externally sourced '''''input data:'''''
*Transmission System (grid) data
*Reserves data
*Market data

===Grid and Reserves Data===
''EMarketOffer'' can create a set of grid data (circuit details, line re-ratings and constraints) at run time from one of four sources:
#Historical transmission system data files provided by Energy Link
#Transmission system files sourced through the EM6 web site operated by Transpower division EMS
#In-house databases
#The files available each business day from the Energy Link web site (for grids from 22-Jul-09 onward)

'''Of the sources above, 1 - 3 are legacy data sources and we have stopped supporting them as the data available from EM6 is incomplete for the purposes required in ''EMarketOffer'', and because we have gone to great effort to provide daily grid and reserves files that include all data reuired to solve the market by half hour. Only the daily updated grid files from 22-Jul-09 are now supported (though the other types of existing grid data can still be used in the meantime). The daily updated files also include full reserves data.'''

On startup ''EMarketOffer'' checks the Energy Link web site for the new grid and reserves data and automatically downloads files if you are not up to date.

The '''Connect Grid Data Tables''' check box in the '''''Database Connection Settings''''' window can be checked if you wish to use grid data from your own database, subject to the following:
----
'''WARNING!''' ''EMarketOffer'' will ignore any database links for grid data if grid data can be obtained from files. To use grid data from your own database you must delete any grid data files that are downloaded by ''EMarketOffer'' on startup.
----

----
'''DISCLAIMER''': Energy Link takes a great deal of care in extracting grid and reserves data from the SPD daily final pricing case data files provided on the Electricity Authority's web site. However, we are totally unsupported in this endeavour and cannot in anyway guarantee the accuracy of the data we provide to ''EMarketOffer'' users. We provide the data in good faith and will not be held liable for the use of the data in ''EMarketOffer'' or in any other application, for the accuracy of the data, or for any special or consequential damages or losses resulting in any way whatsoever from the use of the data.
----

===Market Data===
Dynamic market data can be loaded into ''EMarketOffer'' directly from in-house databases. Care should be taken when constructing database queries to ensure the data that best suits your needs is returned. In particular, think through the following issues before finalising your queries:
*Demand and Generation figures can be obtained from SCADA, WITS Daily Demand, reconciled GXP demand data or by processing arcflow and generation data. Which of these best suits your needs?
*Offers files contain offers from Embedded Generators. How do you wish to deal with embedded generators? Is your demand data consistent with your treatment of embedded generators?

Generation and price data must be loaded from database in Market View. Offer and Demand data can be loaded from database or, in Forecasts, it can also be loaded from files. In Power Flows, demand and generation can be loaded from database or from files. Offer files are published on http://www.electricityinfo.co.nz the business day after the day the Offers relate to. If your database does not contain Offers data you can update the Offers folder with the latest files from this web site as required.

If your database does not store Demand data you will need to create Demand files manually using a third party program such as Excel. All files should be formatted in accordance with the templates provided in '''''[[EMO:Data File Formats|Data File Formats]]'''''.

----
IMPORTANT: When you first install EMO you should consult with Energy Link to ensure that your database connections are set up correctly. We will also ensure that you are able to access and download the daily updated grid and reserves files which include data back to 22-Jul-09. Earlier grid data may be be available on a limited basis only, and will not be supported in future.

[[EMO:Getting Started|Back]] - [[EMO:EMarketOffer User Manual|Home]]

Special:Badtitle/NS106:Data Initialisation

2013-05-05T21:25:52Z

Greg: /* Grid and Reserves Data */

{{#hidens:}}
''EMarketOffer'' requires three types of externally sourced '''''input data:'''''
*Transmission System (grid) data
*Reserves data
*Market data

===Grid and Reserves Data===
''EMarketOffer'' can create a set of grid data (circuit details, line re-ratings and constraints) at run time from one of four sources:
#Historical transmission system data files provided by Energy Link
#Transmission system files sourced through the EM6 web site operated by Transpower division EMS
#In-house databases
#The files available each business day from the Energy Link web site (for grids from 22-Jul-09 onward)

'''Of the sources above, 1 - 3 are legacy data sources and we have stopped supporting them as the data available from EM6 is incomplete for the purposes required in ''EMarketOffer'', and because we have gone to great effort to provide daily grid and reserves files that include all data reuired to solve the market by half hour. Only the daily updated grid files from 22-Jul-09 are now supported (though the other types of existing grid data can still be used in the meantime). The daily updated files also include full reserves data.'''

On startup ''EMarketOffer'' checks the Energy Link web site for the new grid and reserves data and automatically downloads files if you are not up to date.

The '''Connect Grid Data Tables''' check box in the '''''Database Connection Settings''''' window can be checked if you wish to use grid data from your own database, subject to the following:
----
'''WARNING!''' ''EMarketOffer'' will ignore any database links for grid data if grid data can be obtained from files. To use grid data from your own database you must delete any grid data files that are downloaded by ''EMarketOffer'' on startup.
----

----
'''DISCLAIMER''': Energy Link takes a great deal of care in extracting grid and reserves data from the SPD daily final pricing case data files provided on the Electricity Authority's web site. However, we are totally unsupported in this endeavour and cannot in anyway guarantee the accuracy of the data we provide to ''EMarketOffer'' users. We provide the data in good faith and will not be held liable for the use of the data in ''EMarketOffer'' or in any other application, for the accuracy of the data, or for any special or consequential damages or losses resulting in any way whatsoever from the use of the data.
----

===Market Data===
Dynamic market data can be loaded into ''EMarketOffer'' directly from in-house databases. Care should be taken when constructing database queries to ensure the data that best suits your needs is returned. In particular, think through the following issues before finalising your queries:
*Demand and Generation figures can be obtained from SCADA, WITS Daily Demand, reconciled GXP demand data or by processing arcflow and generation data. Which of these best suits your needs?
*Offers files contain offers from Embedded Generators. How do you wish to deal with embedded generators? Is your demand data consistent with your treatment of embedded generators?

Generation and price data must be loaded from database in Market View. Offer and Demand data can be loaded from database or, in Forecasts, it can also be loaded from files. In Power Flows, demand and generation can be loaded from database or from files. Offer files are published on http://www.electricityinfo.co.nz the business day after the day the Offers relate to. If your database does not contain Offers data you can update the Offers folder with the latest files from this web site as required.

If your database does not store Demand data you will need to create Demand files manually using a third party program such as Excel. All files should be formatted in accordance with the templates provided in '''''[[EMO:Data File Formats|Data File Formats]]'''''.

----
IMPORTANT: When you first install EMO you should consult with Energy Link to ensure that your database connections are set up correctly. We will also ensure that you are able to access and download the daily updated grid and reserves files which include data back to 16-Jul-09. Earlier grid data may be be available on a limited basis only, and will not be supported in future.

[[EMO:Getting Started|Back]] - [[EMO:EMarketOffer User Manual|Home]]

Special:Badtitle/NS106:The File Menu

2013-05-05T21:24:16Z

Greg: /* Tabs and Features */

{{#hidens:}}
The File Menu provides access to the following ''EMarketOffer'' features:
*'''''Database Connections''''' - ''set up and test connections to your local databases''
*'''''File Inputs''''' - ''set up and check the status of grid and reserves data files''
*'''''Map Settings''''' - ''customise the EMO map''
*'''''Save All Settings'''''
*'''''Open EMO Data Directory'''''
*'''''Exit'''''

== The Database Connections Option ==
Please read in conjunction with the section on '''''[[EMO:Connecting to a Database Server|Connecting to a Database Server]]'''''.

=== Input Data Concepts ===
Input data is sourced from databases and from files (see '''[[EMO:Data_Storage_Directory_Structure#Data_Files|Data Files]]'''), or from online database servers.

==== The Database Connection Configuration ====
''EMarketOffer'' supports multiple connections to multiple database servers. Database connectivity is managed through the Database Connection Configuration (DCC). A DCC contains a number of queries which obtain data from one or more databases. While a DCC's queries can access data in more than one database on more than one database server, it is not possible to have more than one query handling data of the same type (e.g. only one query can return Price data, and only one query can return Demand data). To overcome this limitation it is possible to define multiple DCCs. Each configuration will define a different, but complete set of data access queries. ''EMarketOffer'' can use only one DCC at a time, which together with the data files loaded from the '''''Inputs files directory''''', fully determine ''EMarketOffer's'' run-time data environment.

==== The Database Connection ====
A Database Connection is a set of data that describes the addressing, technical and security details required to a specific database on a specific database server. The details are combined in to a specific string format and used to access the required data. A DCC must contain one connection string for every database to be addressed in the configuration.

----
NOTE: Only one Connection per server is required in DCC. Therefore if all your data is stored in the same database then all queries required to access data can use the same Connection.

=== Source Data Administration Window ===

==== Access ====

The '''Database Connections''' option in the '''Main Window File Menu'''.

==== Purpose ====
To manage '''''Database Connection Configurations''''' (DCC).

==== Features ====
{|class="wikitable"
! Feature !! Purpose
|-
!Database Connections Configuration Selector
|
:To set the Current DCC from a drop down box of all currently available DCCs.
|-
!Open configuration Button
|
:Opens the DCC Window for the selected configuration
|-
!New Configuration Button
|
:Opens the New DCC Window Dialogue
|-
!Refresh All Cached Data Button
|
:Reloads all cached data (from file and database)
|}

=== Database Connection Settings Window ===

==== Access ====
Either through the '''Open Configuration Button''' or the '''New Configuration Button''', both on the '''''Source Data Administration Window'''''.

==== Purpose ====
Specification of the database connection and query details used by a Database Connectivity Configuration (DCC).

==== Components and Features ====
{|class="wikitable"
! Component !! Feature !! Purpose
|-
! rowspan="5" | Function Panel
|
:''Test Button''
|
:Tests the validity of the DCC. Test results are displayed in the Status Box (see below)
|-
|
:''Save Button''
|
:Saves the current set of configuration data to file.
----
:NOTE: Connection details changed through the interface will only remain effective for the current session. Unless saved using this button, future sessions will revert to the previously saved details.
|-
|
:''Done Button''
|
:Closes the Data Connections Window retaining any unsaved changes for the current session only.
|-
|
:''Date and Period Selector''
|
:Selects the Date and Trading Period for the data connectivity test.
|-
|
:''Status Box''
|
:Shows the results of the last connectivity test
|-
! rowspan="8" |Database Panel
|
:''Add Button''
|
:Creates a new Database Connection
|-
|
:''Delete Button''
|
:Delete an existing Database Connection
|-
|
:''Name Field''
|
:Contains the name of the Database Connection used to reference the connection in the Query Panel
|-
|
:''Connection Type Field''
|
:Determines the type of connection ''EMarketOffer'' will use for a specific connection. Currently supported connections are:
*OleDB
*ODBC
*Oracle
*SQL
:OleDB and ODBS are generic types and operate with most SQL compliant databases. The Oracle and SQL connection types are specific .net variants for the Oracle and Microsoft SQL server database type. They provide performance superior to the generic connection types and should be used by preference where possible.
|-
|
:''Connection String Field''
|
:Contains the Connection String required to access a database server
|-
|
:''Date Brackets Field''
|
:Contains the symbol used by database server to identify dates within query strings (varies by server type)
|-
|
:''Date Format Field''
|
:Defines how the database server interprets date formats
|-
|
:''Error Field''
|
:Displays results from the last test operation that are specific to this Database Connection
|-
! rowspan="9" | Query Panel
|
:''Entity Type Field''
|
:Informs ''EMarketOffer'' which entity type a query will return data for (either 'Node' or 'Unit')
|-
|
:''Connection Field''
|
:Defines the Connection String, named through the Database Panel which is used by the query
|-
|
:''Query Field''
|
:Contains the text of the query used to access data
|-
|
:''Date Field Field''
|
:Links the column containing the date in the query to ''EMarketOffer's'' date/time handler (allows you to use in-house column names)
|-
|
:''TP Field Field''
|
:Links the Trading Period column in the query to ''EMarketOffer's'' date/time handler (allows you to use in-house column names)
|-
|
:''Entity Field Field''
|
:Links the Entity column (defined in the Entity Type Field) in the query to ''EMarketOffer's'' Entity data handler (allows you to use column names from your in-house databases from queries)
|-
|
:''Other Fields Field''
|
:Links additional columns in the query to ''EMarketOffer's'' Entity.trait data handler
|-
|
:''Error Field''
|
:Displays the results of the last test operation specific to the query
|-
|
:''Sent Query Field''
|
:Displays the actual text of the last query sent to test the database connection (provided as a feature to assist with trouble shooting during setup)
|}

=== Creating A New Database Connection Configuration ===

==== Usage ====
The ability to define multiple Database Connection Configurations allows you to create different data environments for different requirements and easily switch between these environments as needed. Examples of different data environments include:
*The standard (historical) market data in the corporate market database
*A short-term model of a specific market scenario (suitable for business development projects)
*An alternate data source for one or more data streams (e.g. Demand data from SCADA vs SPD Daily Demand)
*A database on a portable computer (suitable for away trips and business presentations)
*A training database of illustrative scenarios


'''>> To create a new Database Connection Configuration'''
#Open the '''''External Data Administration Window''''' from the Data Source option of the '''''Main Window''''' File Menu
#Open the New Connection Configuration Dialogue using the '''New Configuration Button'''
#Enter the name for the new configuration in the '''Connection Configuration Name''' field
#Chose whether to start the new configuration with a copy of the Current Configuration (saves much data re-rentry) or with a blank screen by selecting 'Yes' or 'No' in the ''Copy Current Connection Configuration'' field
#Click '''OK Button''' to accept your entries and open the Database Connection Settings Window or the '''Cancel Button''' to reject entry and return to the '''''External Data Administration Window'''''

== The File Inputs Window ==

==== Access ====
The '''File Inputs''' option in the '''Main Window File Menu.'''

==== Purpose ====
Shows the status of grid and reserves data downloaded in csv files from the Energy Link web site. Since 16-Jul-09 grid and reserves data has been sourced from the "SPD daily case final pricing solve" data files that are made available each day on the Electricity Authority's web site. Each business day, Energy Link downloads the SPD daily case final pricing solves and extracts data that defines the grid, lince capacities, line re-ratings (which are typically line outages), equation constraints, variable line ratings and reserves parameters, by half hour for the entire day. Sometimes provisional data is available but which is subsequently updated with final data.

Whenever you start EMO it automatically chceks for the latest data files on the Energy Link web site, but if you leave EMO running overnight then each subsequent day you need to check the File Inputs window for new data: on the Download tab, click '''Check For New Files'''.

==== Tabs and Features ====
{|class="wikitable"
! Tab !! Feature !! Purpose
|-
! rowspan="3" |Download Tab
|
:''Check For New Files button''
|
:Click on this button to check for new data files
|-
|
:''Web Site Configuration''
|
:The fields in the table under the Check For New Files button are used to configure access to the Energy Link web site: these are set up for the default, but you may need to contact Energy Link for help with more complex configurations required in a corporate environment
|-
|
:''Messages''
|
:The tree structure in this area shows what data is loaded: expand the tree to view the messages. Messages can also be copied to the clipboard by clicking the Copy Messages button.
|-
! rowspan="6" | Grid Tab
|
:''Open Grid Files Directory Button''
|
:Opens the folder which stores grid. You'll most likely see folders for 'EMO', 'EM6' and 'Ellsoft'. The EMO folder holds the grid files which are used from 22-Jul-09. The other two folders hold older grid data.
|-
|
:''Reload Grid Inputs button''
|
:Relaods the grid data from the files in the relevant data folder
|-
|
:''Date and TP boxes''
|
:These show the date and trading period on the Main Window
|-
|
:''Base Grid Source Table''
|
:This table shows the range of dates from the data file from which the displayed date's grid data is drawn from
|-
|
:''Circuits Table''
|
:This table displays the data relating to lines for the displayed date. Double click on any line to get more information including name, dates for which the displayed data is valid, the type of rating (SSW = summer, shoulder, winter; VLR = variable line rating), and the value of the default ratings (click the Annual Ratings button) and any re-ratings that apply (click the Reratings button).
|-
|
:''Messages''
|
:Messages in a tree structure.
|-
! Reserves
|
|
:This window provides access to the reserves data folder and shows the valid date range based on the data files available to EMO.
|}

== The Map Settings Menu Option ==

=== Access ===
The Map settings option from the file Menu on the Main Window.

=== Purpose ===
To configure the appearance of items appearing on the Map.

The Map Settings Window contains two panels accessed through tabs. The panels are:
*Main Map Settings
*Inset Map Settings

Both panels contain exactly the same setting types and options.

=== Editing ===

{|class="wikitable"
|-
|
:''Numeric Field''
|
:Click on the required field and then type the required new number
|-
|
:''Colour''
|
:Place mouse pointer over field to be edited and click on the "..." tab at the right of the cell to open the colour selector
|-
|
:''Font''
|
:Place mouse pointer over field to be edited and click on the "..." tab at the right of the cell to open the font selector
|-
|
:''Check Box''
|
:Simply click on the box to check/un-check
|}

----
NOTE: The reset button restores the Map Settings for the Main or Inset map types back to the default settings.

== The Save All Settings Option ==
''EMarketOffer'' saves changes to Forecast and Powerflow Case Definitions to file on closing. The '''Save All Settings''' option saves any unsaved changes to file without shutting ''EMarketOffer'' down. This feature should be used as a precaution in situations where extensive changes to Forecast and Powerflow Case Definitions are being made.

== The Open EMO Data Directory Option ==
This opens a standard Windows directory window containing the '''''EMO Data Directory''''' (location selected during the installation process). The window provides easy access to important ''EMarketOffer'' data such as Forecast files and the Component Library.

== The Exit Option ==
Selecting this option closes down ''EMarketOffer.'' In doing so the program will save all unsaved data and close all internal files. Output files created and opened through ''EMarketOffer'' (e.g. output csv files) will remain open.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Menu Bar|Back]]

Special:Badtitle/NS106:Software Installation

2013-05-05T21:22:47Z

Greg:

{{#hidens:}}
For optimal performance ''EMarketOffer'' should be installed on a dedicated workstation.

----
'''Before you start:''' The process for implementing ''EMarketOffer'' includes configuring connectivity to your online databases and providing important Transmission System configuration data, consultation with your system administrator or the Energy Link helpdesk is recommended before proceeding to installation.
----

'''''To install EMarketOffer on your workstation:'''''
#Ensure you have administrative permission rights if you are installing on a Windows work station
#Unpack the zipped installation package into a temporary folder on your workstation using the password provided by Energy Link. (Skip this step if your system administrator has setup a directory containing the installation data on a network drive.)
#Read any release notes or any file called "Readme.txt" - these notes will contain important installation information which may modify the instructions given here
#Run the program called 'Setup.exe' in the temporary folder (if the package has been sent to you by e-mail the setup program will be called 'Setup.ex_', and should be renamed to 'Setup.exe' before running).
#Enter a location for the program's executable when prompted by the setup program (default. 'C:\Program Files\Energy Link\EMO')
#Enter a location for the program's data files when prompted by the setup program (e.g. 'C:\Data\EMO')
#The setup program will then:
##Install the ''EMarketOffer'' executable in your specified program folder
##Create a '''''Directory Structure''''' under your specified data folder
##Create an 'EMO' globe icon on your desktop

'''''If this is the first time the software has been installed on your computer you will need to:'''''
#Copy the license file (provided separately) to the '''''License Folder''''' in the '''''[[EMO:Data_Storage_Directory_Structure|Data Directory Structure]]'''''
#Copy the Nodes and Substations Positions files to the '''''Positions folder''''' in the Data Directory Structure
#Copy the contents of the 'Maps' folder to the '''''Maps Folder''''' in the Data Directory Structure (please take care to ensure all New Zealand Maps are placed in the 'NZ' sub-folder)
#Copy the contents of the remaining EMS files to the 'EMS' Sub-folder (in the '''''Inputs Folder''''' in the Data Directory Structure)

You can now launch ''EMarketOffer'' from the desktop icon, however for first time installations the program stills needs to be configured to link to your '''''internal databases'''''.

----
'''Warning!''' ''EMarketOffer'' is computationally intense and operates with high volumes of both input and output data. Operating the program across a network or in a shared application environment may result in unsatisfactory performance.
----

[[EMO:Getting Started|Back]] - [[EMO:EMarketOffer User Manual|Home]]

Special:Badtitle/NS106:The Powerflow Case Definition Window

2013-05-05T21:21:48Z

Greg: /* Purpose */

{{#hidens:}}
[[File:Powerflow case Definition Window.PNG|600px|thumb|right|Figure 1 - The Powerflow Case Definition Window]]
=== Purpose ===
To create, edit, run and re-run Powerflow Case Definitions.

=== Components ===
*Title Bar
*Menu Bar
*Details Panel
*Effective Date Range Panel
*Run Powerflow Button
*Loaded Data Summary Panel

== Title Bar ==
The Powerflow Case Definition Window Title Bar contains the Powerflow Case Definition name (e.g. 'Final test PFC 1').

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Powerflow Analysis|Back]]

== Menu Bar ==
{|class="wikitable"
! Menu !! Option !! Purpose !! Action
|-
! rowspan="4" | Data
|
:''Load Data''
|
:To load historical or externally sourced data into the Powerflow Case Definition
|
:Opens the '''''Load Powerflow Window'''''
|-
|
:''Copy Powerflow''
|
:To make a copy of the current Powerflow Case Defintion
|
:Opens a new case Definition Window containing the same input data as the current Definition
|-
|
:''Import''
|
:To import prepared Powerflow Case Components from the Resource Library
|
:Opens the Component Library Import Window
|-
|
:''Export''
|
:To export Components of the current Forecast Definition to the resource Library
|
:Opens the Component Library Export Window
|-
! Graphs
|
:''Demand Generation Graph''
|
:To provide access to a Chart of the Demand and Generation profiles loaded into the Case Definition
|
:Opens the Demand, Generation Graph
|-
! rowspan="2" | Profiles
|
:''Demand''
|
:Allows access to the Demand Profile for all Nodes (Demand profiles can be imported and exported from here)
|
:Opens the Demand Profile Window
|-
|
:''Generation''
|
:Allows access to the Generation Profile for all Nodes (generation profiles can be imported and exported from here)
|
:Opens the Generation Profile Window
|}

=== Load Powerflow Data Window ===

==== Access ====
The '''Data > Load Data''' Option in the Powerflow Case Definition Window Menu Bar.

==== Purpose ====
To:
*Control the loading of all Definition input data in a single operation
*Record the details of the last load operation for a specific Definition

==== Components ====
{|class="wikitable"
! Component !! Purpose
|-
|
:''Load Profile Panel (under the yellow heading of "Demand and Generation"''
|
:Controls the loading of Demand and Generation Profile Data
|-
|
:''Load Transmission Data Panel (under yellow heading of "Transmission"''
|
:Controls the loading of Transmission data
|-
|
:''Load/Close buttons''
|
:Initiates or cancels the loading operation specified in the template
|}

=== Load Profile Panel ===

==== Access ====
The '''Data > Load Data''' menu option in the Powerflow Case Definition Window.

==== Purpose ====
To load seven day Demand and Generation profile data into a Powerflow Case from an online database.

==== Components ====
{|class="wikitable"
! Component !! Purpose
|-
|
:''Date From Field''
|
:Uses a date selector to specify the inclusive date (day) to start loading Demand data into the Powerflow Case Definition
|-
|
:''Number of Weeks Button''
|
:Specifies the number of weeks of Demand and Generation data (starting at the specified Load Start Date) to use when creating an averaged profile for each Node
|-
|
:''Date To Display''
|
:Shows the last date for which profile data will be loaded or included into an averaged profile
|-
|
:''Clear and Load Check box''
|
:Clears all existing Profile data before loading new profile data (toggles with the Keep and Overwrite Check box)
|-
|
:''Keep and Overwrite Check box''
|
:Keeps existing profile data and overwrites with new data averaged with existing data, allowing averaged Demand profiles to be created using Demand data from discontinuous time periods (toggles with the Clear and Load Check box)
|-
|
:''Last Load Operation Details''
|
:Records when Demand and Generation profile data was last loaded and if the load operation was succesful
|-
|
:''Load Demand Data and Generation Check box''
|
:To include or exclude profile data from the next Load Operation
|-
|
:''Reset Button''
|
:Restores the Profile Load Panel to its default settings
|}

=== Load Transmission Data Panel ===

==== Access ====
The '''Data > Load Data''' menu option in the Powerflow Case Definition Window.

==== Purpose ====
To specify the date range of Transmission data you want to load into a Powerflow Case Definition from you default Transmission System data source.

==== The default ''EMarketOffer'' data source for Transmission System data ====
When uploading Transmission System data into a Powerflow Case ''EMarketOffer'' first checks the Inputs sub-folders for valid grid files, and uses these in preference to data from an online database, even when a connection to obtain Transmission System data has been defined.

=== Transmission System Data Loading Modes ===
Transmission System data can be loaded into a Powerflow Case Definition in one of two modes:
*Date Range Mode
*Period Mode

==== Date Range Mode ====
Accessed by clicking on the "Date Range" tab under the "Transmission" heading.

===== Purpose =====
To select a date range for loading a Powerflow Case Definition with Transmission System data.

A Definition loaded through the Date Range Mode will contain the following:
*Base Grid Configuration
*All Re-ratings applied during the date range
*All Equation Constraints applied during the date range

===== Components =====
{|class="wikitable"
! Component !! Purpose
|-
|
:''Date Selectors''
|
:Allows you to specify the inclusive dates to start/end loading Transmission data into the Definition
|-
|
:''Clear and Load Check box''
|
:Clears all existing Transmission data before loading new data (toggles with the Keep and Overwrite Check Box)
|-
|
:''Keep and Overwrite Check box''
|
:Keeps existing Transmission data and overwrites with new data from the database
|-
|
:''Last Load Operation Details''
|
:Records when Transmission data was last loaded into the Definition
|-
|
:''Include Transmission Data in Load Check box''
|
:To include or exclude Transmission data from the next Load Operation
|-
|
:''Reset Button''
|
:Restores the entire Transmission Load Panel (file and database) to its default settings:
*Start Date = First date of the Effective Date Range
*End Date = Last date of the Effective Date Range
*Clear and Load = Checked
*Include Transmission System data in next load operation
|}

==== Period Mode ====
Accessed by clicking on the "Period" tab under the "Transmission" heading.

===== Purpose =====
To select a specific period which will provide the basic Transmission System data for all periods in your Powerflow Case Effective Date Range.

NOTE: When using Period Mode ''EMarketOffer'' applies the basic grid and re-ratings to obtain the System Configuration for the Period and applies this to all periods in the Powerflow Case Effective Date Range. It does not keep specific records of Circuit re-ratings or Equation Constraints, which are kept when loading in Date Range Mode.

Control of the Transmission data takes place through the Load Transmission Data Panel in Period Mode.

===== Components =====
{|class="wikitable"
! Component !! Purpose
|-
|
:''Date Selector''
|
:Specifies the inclusive date of the period to load Transmission data into the Powerflow Case Definition
|-
|
:''Period Selection Bar''
|
:Used with the mouse to select the loading Period
|-
|
:''Period Selection Roller''
|
:Used with the mouse or by text entry to select the loading Period
|-
|
:''Clear and Load Check box''
|
:Clears all existing Transmission data before loading new data (toggles with the Keep and Overwrite check box)
|-
|
:''Keep and Overwrite Check box''
|
:Keeps existing Transmission data and overwrites with new data from the database
|-
|
:''Last Load Operation Details''
|
:Records when Transmission data was last loaded
|-
|
:''Load Transmission Data Check box''
|
:To include or exclude Transmission data from the next Load Operation
|-
|
:''Reset Button''
|
:Restores the entire Transmission Load Panel (file and database) to its default settings:
*Start Date = First date of the Effective Date Range
*End Date = Last date of the Effective Date Range
*Clear and Load = Checked
*Include Transmission System data in next load operation
|}

=== The Export Powerflow Components Window ===
The function and operation of this window are similar to that of the '''''[[EMO:Menu#The_Export_Forecast_Components_Window|Export Forecast Components Window]]'''''.

=== The Import Powerflow Components Window ===
The function and operation of this window are similar to that of the '''''[[EMO:Menu#The_Import_Forecast_Component_Window|Import Forecast Components Window]]'''''.

=== The Demand Profile Option ===

==== Access ====
The '''Profiles > Demand''' option of the '''''Powerflow Case Definition Window''''' Menu.

==== Purpose ====
To:
#Import and export Demand Profile files
#Edit Demand figures for groups or individual Trading Periods and Nodes.

NOTE: The format of Demand Profile files is covered in '''''[[EMO:Demand Profile File Format|Demand Profile File Format]]'''''.

The Window displays the seven-day Demand Profile in a Data Grid with a column for each Node and a row for each Trading Period. Data in a cell can be edited manually. Cutting and pasting to and from single or multiple cells is supported.

The ''File'' menu provides access to the ''Export'' and ''Import'' functions for the Profile.

=== The Demand Generation Graph ===

==== Access ====
The '''Graphs > Demand Generation Graph''' menu option in the '''''Powerflow Case Definition Window.'''''

==== Purpose ====
To show the Demand and Generation Profile for the current Powerflow Case Definition in graphical form.

==== Features ====
{|class="wikitable"
! Feature !! Purpose
|-
|
:''Title Bar''
|
:Shows the type of Graph being displayed
|-
|
:''Date Range Selectors''
|
:Displays how the loaded profile will appear on any specific day (and for how many days)
|-
|
:''Chart Options Link''
|
:Opens the Chart Options Window where you can control some aspects of the chart's appearance
|-
|
:''Chart Area''
|
:Contains the Chart's graphical contents
|-
|
:''Quantity Axis''
|
:Linear scale of Demand/Generation quantity (MW)
|-
|
:''Time Axis''
|
:Profile days
|-
|
:''Demand Line''
|
:Profile Demand displayed as a single line
|-
|
:''Generation Area''
|
:Profile Generation displayed as a shaded area
|-
|
:''Period Roll Over''
|
:A mouse-activated feature showing (for the point under the cursor):
*Day, Date and Period (e.g. "Tue, 23 Aug 200 : 37")
*Demand Quantity
*Generation Quantity
|}

NOTE: The Demand Generation Graph Window is sizable. The chart area expands and compresses to fill the available space.


'''>> To change the colours used on the graph:'''
#Click on the blue ''Options...'' link in the top right hand corner of the Graph window
#Choose the required colours using the options in the pop-up window.

=== The Export Powerflow Components Window ===
The function and operation of this window are similar to that of the '''''[[EMO:Menu#The_Export_Forecast_Components_Window|Export Forecast Components Window]]'''''.

=== The Import Powerflow Components Window ===
The function and operation of this window are similar to that of the '''''[[EMO:Menu#The_Import_Forecast_Component_Window|Import Forecast Components Window]]'''''.

=== The Demand Profile Option ===

==== Access ====
The '''Profiles > Demand''' option of the '''''Powerflow Case Definition Window''''' Menu.

==== Purpose ====
To:
#Import and Export Demand Profile files
#Edit Demand figures for groups or individual Trading Periods and Nodes.

NOTE: The format of Demand Profile files is covered in the '''''[[EMO:Demand Profile File Format|Demand Profile File Format]]'''''.

The Window displays the seven-day Demand Profile in a Data Grid with a column for each Node and a row for each Trading Period. Data in a cell can be edited manually. Cutting and pasting to and from single or multiple cells is supported.

The ''File'' menu provides access to the ''Export'' and ''Import'' functions for the Profile.

==== Exporting from the Profile ====
Selecting the '''File > Export''' option open the Export Node Profile Options Window.

===== Components =====
{|class="wikitable"
! Component !! Purpose
|-
|
:''Select All Nodes check box''
|
:When checked will include in the exported data, Demand for all Nodes in the loaded Profile. When not checked the Node Selection Drop Down List is displayed
|-
|
:''Node Selection Drop Down List''
|
:To select the individual Nodes to be included in the export
|-
|
:''Output Format Type Toggle''
|
:To select if the data will be exported with Nodes as columns or rows
|-
|
:''Included Day Selector''
|
:To select which Profile days will be exported.
|-
|
:''Output Location Toggle''
|
:To select if the data will be output to CSV file or to the Windows Clipboard
|-
|
:''On Completion Action''
|
:When checked will cause the created CSV file to be opened automatically when the export is complete.
|-
|
:''OK Button''
|
:Executes the data export operation. When saving to .csv file this button will open the Standard Windows 'Save As' dialogue to select a name and location for the exported profile.
|-
|
:''Cancel Button''
|
:Cancel the export operation and closes the Options Window.
|}

==== Importing Into the Profile ====
Demand data can be imported into the Powerflow Case Profile from any properly formatted file. Selecting the '''File > Import''' menu option opens the Standard Windows file browsing window to locate the import file.

An imported Profile File may contain data for:
*One or many Nodes
*One or many profile days
*One or many Trading Periods

NOTE: Demand for Nodes absent from the Profile's Transmission System data will be loaded, but will not play any role in the Powerflow analysis unless the new Node is manually connected with one or more user-defined Circuits.

=== The Generation Profile Option ===

==== Access ====
The '''Profiles > Generation''' option of the '''''Powerflow Case Definition Window''''' Menu.

==== Purpose ====
To:
#Import and export Generation Profile files
#Edit Generation figures for individual period and Nodes.

NOTE: The format of Generation Profile files is covered in '''''[[EMO:Generation Profile File Format|Generation Profile File Format]]'''''.

The Window displays the seven-day Generation Profile in a Data Grid with a column for each Unit and a row for each Trading Period. Data in a cell can be edited manually. Cutting and pasting to and from single or multiple cells is supported.

The ''File'' menu provides access to the ''Export'' and ''Import'' functions for the Profile.

==== Exporting from the Profile ====
Selecting the '''File > Export''' option opens the Export Unit Profile Options Window.

===== Components =====
{|class="wikitable"
! Component !! Purpose
|-
|
:''Select All Units check box''
|
:When checked will include in the exported data Generation for all Units in the loaded Profile. When not checked the Unit Selection Drop Down List is displayed
|-
|
:''Unit Selection Drop Down List''
|
:To select individual Units to be included in the export.
|-
|
:''Output Format Type Toggle''
|
:To select if data will be exported with Units as columns or rows
|-
|
:''Included Day Selector''
|
:To select which Profile days will be exported
|-
|
:''Output Location Toggle''
|
:To select if the data will be output to CSV file or to the Windows Clipboard
|-
|
:''Open CSV on creation check box''
|
:When checked will cause the created CSV file to be opened automatically when the export is complete
|-
|
:''OK Button''
|
:Executes the data export operation. When saving to .csv file this button will open the Standard Windows 'Save As' dialogue for you to select a name and location for the exported profile.
|-
|
:''Cancel Button''
|
:Cancels the export operation and closes the Options Window
|}

==== Importing Into the Profile ====
Generation data can be imported into the Profile from any properly formatted file. Selecting the '''File > Import''' menu option opens the Standard Windows file browsing window to locate the import file.

An imported Profile File may contain data for:
*One or many Units
*One or many profile days
*One or many Trading Periods

NOTE: Generation for Units not currently connected in the Profile's Transmission System data will be loaded, but will not play any role in the Powerflow analysis unless the new Unit is manually connected to a specific injection Node.

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Powerflow Analysis|Back]]

== The Powerflow Case Details Panel ==

=== Components ===
{|class="wikitable"
! Item !! Purpose
|-
|
:''Powerflow Case Name Button''
|
:Enables the Powerflow Case to be named by opening the Renaming Window
|-
|
:''Powerflow Case Name Field''
|
:Displays the Powerflow Case name
|-
|
:''Powerflow Case Comments Field''
|
:Enables important information about the Powerflow Case to be saved (e.g. creator, creation date, reason for creation etc). Information entered in this field is free text only and cannot be used in searches etc.
|}

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Powerflow Analysis|Back]]

== Effective Date Range Selector ==

=== Components ===
{|class="wikitable"
! Item !! Purpose
|-
|
:''Start''
|
:Selects Start Date for the Effective Date Range
|-
|
:''Start TP Selector''
|
:Selects the Start Period for the Effective Date Range. Can be altered by direct text entry from the keyboard or by operating the up and down arrow head buttons.
|-
|
:''Number of Periods Selector''
|
:Selects the number of discrete Trading Periods included in the Effective Date Range
|-
|
:''Run Powerflow Button''
|
:Runs a Powerflow Case Definition to produce output
|}

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Powerflow Analysis|Back]]

== Powerflow Case Loaded Data Summary Panel ==

=== Purpose ===
To display a summary of the data currently loaded into the Powerflow Case Definition.

=== Features ===
{|class="wikitable"
! Feature !! Purpose
|-
|
:''Data grid Toggle Buttons''
|
:Select the type of information to be displayed in the Panel's '''''Data Grid'''''
|-
|
:''Data Grid Panel''
|
:Displays summarised '''''Powerflow Case''''' data
|-
|
:''Data Grid Header Row''
|
:Contains the column headings for the displayed data columns
|-
|
:''Data Grid Information Row''
|
:Each Data Grid row contains information relevant to a single instance of a modelled item. Most data values displayed in the Panel can be edited directly; also double-clicking on a row opens a window for editing the instance's details.
|-
|
:''Create/Delete Instance Buttons''
|
:To add new, or delete instances of the '''''Modeled Item''''' currently displayed in the Data Grid Panel. The behaviour of the create/delete operation varies by Modelled Item type
|}

The following Data Grids can be displayed:
*Loaded Nodes
*Loaded Units
*Loaded Circuits
*Loaded Equation Constraints
*Circuit Re-rating Schedule
*Equation Constraint Schedule
*Swing Nodes

=== The Powerflow Node Data Grid ===

==== Purpose ====
To display the Node name and Associated Sub-Station for each Node loaded into the Definition.

NOTE: The value of the Substation field can be edited but not the Node Name which can only be changed using the '''''Edit Node Window.'''''

==== Usage ====

'''>> Double-click on row to open the associated ''Edit Node Window'' where Nodal Demand can be edited'''


'''>> To add a new Node:'''
#Click on any row in the Nodes Data Grid and press the <INSERT> key. This creates an empty row at the top of the Grid. Details of the Node can be entered by bringing up the Edit Node Window for the empty row.


'''>> To delete an existing Node:'''
#Click on the Nodes Data Grid row containing the Node to be deleted
#Press the ''<Delete>'' key - a dialogue box asking you to confirm the delete operation will appear.

=== The Powerflow Case Unit Data Grid ===

==== Purpose ====
To display the following items for each Unit loaded into the Powerflow Case Definition:
*Unit name
*Active Status (checked when Generation for the Unit is included in the Powerflow analysis)
*Associated Generation Station
*Injection Node

NOTE: The values of all fields in the Grid can be edited except for the Unit Name which can only be changed using the Edit Unit Window.

=== Usage ===

'''>> Double-click a row to open the ''Edit Unit Window'' where Unit Offers can be edited'''


'''>> To add a new Unit:'''
#Click on any row in the Units Data Grid and press the ''<Insert>'' key. This creates an empty row at the top of the Grid labelled " _ new _ ". Details of the Unit can be entered by bringing up the Edit Unit Offers Window for the empty row.


'''>> To delete an existing Unit:'''
#Click on any row in the Units Data Grid and press the <DELETE>key. A dialogue box asking you to confirm the delete operation will appear.

NOTE: Deleting the Unit also deletes any Offers data associated with the Unit at the time of deletion

==== Components ====
{|class="wikitable"
! Component !! Purpose
|-
|
:''Unit Details Panel''
|
:Editable display of Unit details:
*Unit Name
*Injecting Node
*Included in Powerflow analysis indicator
*Associated Generator
|-
|
:''Generation Data Grid''
|
:Displays Generation by period for each day in the seven-day generation profile
|-
|
:''Display Toggle Buttons''
|
:Toggles between Grid and Graph display modes.
|}

==== The Unit Generation Graph ====

===== Access =====
Double-clicking the '''Graph Button''' in the Edit Unit Generation Window.

===== Purpose =====
To display the Powerflow Case Generation Profile for a specific Unit.

===== Features =====
{|class="wikitable"
! Component !! Purpose
|-
|
:''Unit Details Panel''
|
:Editable display of Unit details:
*Unit Name
*Injecting Node
*Included in Powerflow analysis indicator
*Associated Generator
|-
|
:''Generation Graph''
|
:Displays Generation in MW by period as a vertical red line
|-
|
:''Display Toggle Buttons''
|
:To toggle between Grid and Graph display modes
|-
|
:''Day of the Week Selector''
|
:Switches the time axis for the Generation Graph to one of the seven profile days or to the whole seven-day profile
|}

=== The Powerflow Case Circuit Data Grid ===

==== Items ====
{|class="wikitable"
! Item !! Purpose
|-
|
:''Circuit Name''
|
:Name of Circuit
|-
|
:''FromNode''
|
:Circuit 'From' Node
|-
|
:''ToNode''
|
:Circuit 'To' Node
|-
|
:''isHVDC''
|
:Component of HVDC indicator (checked when circuit contributes to the HVDC link)
|-
|
:''Resistance''
|
:Circuit Resistance value
|-
|
:''Reactance''
|
:Circuit Reactance value
|-
|
:''Summer Capacity''
|
:Circuit Summer Capacity
|-
|
:''Winter Capacity''
|
:Circuit Winter Capacity
|-
|
:''Re-Rated''
|
:Checked when circuit is re-rated at any time during the Forecast Effective Date Range
|}

NOTES:
#The values of all fields in the Grid can be edited except for the Re-Rating indicator which is read-only and the Circuit Name which can only be changed using the Edit Circuit Window.
#''EMarketOffer'' flags a Circuit as re-rated if the Branch Constraint data file contains a rating change for the Circuit that starts before or during the Forecast Effective Date Range and that ends during or after the Effective Date Range. Many of the re-ratings in the grid data files are for prolonged durations. It is therefore quite likely you will see a Circuit flagged as re-rated while the rating throughout the chosen Powerflow Case Effective Date Range remains constant.

==== Usage ====
Double-click on a row to open the associated '''''Edit Circuit Window''''' where Circuit details can be edited.


'''>> To add a new Circuit:'''
#Click on any row in the Circuits Data Grid and press the ''<Insert>'' key. This creates an empty row at the top of the Grid labelled " _ new _ ". Details of the Circuit can be entered by bringing up the '''''Edit Circuit Window''''' by double-clicking the empty row.


'''>> To delete an existing Circuit:'''
#Click on the row in the Circuit Data Grid containing the Circuit you want to delete and press the ''<Delete>'' key. A dialogue box asking you to confirm the delete operation will appear.

NOTE: Deleting a Circuit also deletes any re-ratings data associated with the Circuit at the time of deletion

=== The Powerflow Case Equation Constraints Data Grid ===

==== Purpose ====
To display the following items for each Equation Constraint loaded into the Powerflow Case Definition:
*Constraint Name
*Included Status (checked when Constraint will be included in dispatch)
*Type (can be 'Permanent', 'Temporary' or 'Outage')
*Season (can be 'Summer' or 'Winter')
*Default Limit (used as the default limit value when applied in the Forecast)

NOTE: ''EMarketOffer'' flags Equation Constraints as Active if the grid data files contain a Constraint starting before or during the Powerflow Case Effective Date Range and ending during or after the Effective Date Range.

==== Usage ====

'''>> Double-click on a row to open the ''Edit Equation Constraint Window'' where Constraint details can be edited'''


'''>> To add a new Equation Constraint:'''
#Click on any row in the Equation Constraints Data Grid and press the ''<Insert>'' key. This creates an empty row at the top of the Grid labelled " _ new _ ". Details of the Constraint can be entered by bringing up the Edit Equation Constraint Window by double-clicking the empty row.


'''>> To delete an existing Circuit:'''
#Click on the row in the Circuit Data Grid containing the Circuit you want to delete and press the <DELETE> key. A dialogue box asking you to confirm the delete operation will appear.

NOTE: Deleting a Constraint also deletes any re-ratings data associated with the Constraint at the time of deletion.

=== The Powerflow Circuits Re-ratings Schedule Grid ===
Please refer to the section, the '''''[[EMO:Circuit_Outage_Schedule|Circuit Re-ratings Schedule Grid]]''''' which has identical functionality.

=== The Powerflow Equation Constraints Schedule Grid ===
Please refer to the section, the '''''[[EMO:Equation_Constraints_Schedule|Equation Constraints Schedule Data Grid ]]''''' which has identical functionality.

=== The Powerflow Swing Node Data Grid ===

==== Purpose ====
To select one or more Swing Nodes to which unmatched demand in the Powerflow Analysis can be allocated.

==== Usage ====
Swing Nodes can be selected using a check list or drop down box (selected using the buttons in the top right hand corner of the Data Grid).

[[EMO:EMarketOffer User Manual|Home]] - [[EMO:Powerflow Analysis|Back]]