SFT Implementation Project
Project Update
23 Jul 10 Update: Due to the need for further testing of the synchronisation and comparison tools, ensuring the test and production environments have identical inputs (outages, bids and offers), the target parallel operations start date is now 16 August 2010.
Once the inputs are aligned with production we will extend the period of monitoring SFT outputs until March 2011. SFT will now be switched on in the Coordination Centre on 28 March 2011. Outage Planners will begin using SFT constraints for checking outages from 14 February 2011 for outages that occur after 28 March.
In the meantime, we welcome your comments, feedback, and any questions. Further updates to the project timeline will be notified as they are available.
Thank you for your patience.
4 Jul 10 Update: The SFT Implementation Issues Register has been updated.
Background
Security Constraints are applied to the SPD market clearing engine to ensure the power system is securely dispatched.
The System Operator is automating the way thermal security constraints are calculated using an application called Simultaneous Feasibility Testing (SFT), which was delivered as part of the System Operator’s Market Systems replacement programme (MSP). When implemented, SFT will allow the System Operator to determine and implement thermal security constraints dynamically.
Constraints built through this process will:
- use up-to-date and accurate network and injection data for developing constraints, therefore providing optimal application of security constraints
- automatically consider all realistic contingencies
- remove the current considerable manual process with attendant risks of error and conservative assumptions
- allow for efficient and more cost effective use of grid capabilities by market participants.
The use of SFT will therefore allow the System Operator to provide better management of constraints in real-time operation in a secure and efficient manner.
The proposed project timeline is as follows:
These timeframes are approximate and will be subject to change depending on any issues that arise during the operational testing.
Feedback on the content of this page can be sent by email to system.operator@transpower.co.nz for attention Fiona Abbott.
Methodology
The methodology that we intend to use to implement SFT is best illustrated in a number of flowcharts. These show what input information about the power system stability limits and transmission capability limits are used to define the parameters in the market model that are used to formulate the security constraints and when such information can be published.
| Name/Link to Diagram |
Description |
Process Overview [77kB]
|
This diagram shows the SFT Security Constraint development process used by the SFT application. Additional information about inputs/parameters/ outputs can been seen by hovering the cursor over the boxes with yellow icons in them. |
Security Contraint creation process with SFT [44kB]
|
Page 1 of this diagram shows the process used by the SFT Constraint Builder to create Security Constraints, page 2 is the same diagram with additional details added. |
Industry Involvement
As part of the overall test phase for SFT implementation, the System Operator is building a test environment to enable selected participants to conduct their own due diligence on the effects of enabling SFT automated constraint generation on the operation of the market. This will allow participants to:
- view the SFT outcomes from schedules and compare them with the existing production system outcomes
- select scenarios for the System Operator to run to test the SFT outcomes against previous outcomes
- test compatibility and integrate the SFT outcomes with their own tools
The participants involved in the testing are those who are most directly affected by such outcomes. Others are welcome to join in the testing, or to use the published testing results.
Related Infomation