Transcript system-operator-Testing EPER Workshop 2

Extended Reserve
Testing Requirements
Presenter:
Jamie Jordan, System Operator
System Operator role
Develop
technical
requirements
report
TRR
SERO
Issue
statement of
extended
reserve
obligations
IMP.
PLANS
Coordinate
implementation
plans
SYSTEM
REQUIREMENTS
Create
technical
requirements
schedule
TRS
Workshop overview
Overview
Testing of
AUFLS Systems
Implementation
Guidelines
Workshop 1
Workshop 2
Workshop 3
Background
• Review of the technical requirements for
extended reserve providers
• Publish the technical requirement report
• Develop draft technical requirement
schedule
Why test?
• To prove reliability of AUFLS by
demonstrating offered systems meet the
technical requirements
What do you test?
• Functional tests
– frequency
– hold delay
– voltage
• Operational tests
– harmonic
– end to end
– application
Functional Test: Frequency
• Action
– ramp the frequency through band
• Outcome
– confirm pick up (no hold times)
– confirm rate of change if applicable
– compare calculated versus expected
– determine any inherent delays
Functional Test: Hold delay
• Action
– ramp frequency through band
• Outcome
– test appropriate test points with time delay
– test drop out times
– compare with expected
– determine any addition inherent delays
Functional Test: Voltage
• Action
– vary voltage input from 1.15pu to 0.4pu
• Output
– compare this with the expected
– confirm device is reliable above 0.5pu
– if unreliable notify the system operator
Operational Test: Harmonic
• Action
– repeat frequency with hold delay tests
– apply a combination of harmonic distortion
– the most common are: 5th; 7th; 11th; and 13th
– compare calculated frequency
• Outcome
– if reliability is impacted by harmonics notify
the system operator
Operational Test: End to End
• Action
– test the complete system with as-left settings
– monitor trip coil and relevant contacts
• Outcome
– verify total operating time
Operational Test: Application
• Action
– additional tests may need to be carried out if
there are known system or hardware
limitations which could be identified by the
provider or system operator
• Outcome
• verify AUFLS operation
When do you test?
• Testing is required when
– a new system is installed
– an existing system selected with untested
settings
– the test period has elapsed [4 or 10 yearly]
– maintenance may have affected settings
Testing obligation
• Selected extended reserve providers must
– complete implementation plan including
developing test plans
– carry out testing
– complete and keep compliance reports,
copies of which may be requested to confirm
compliance
Companion Guide for Testing
• Details typical testing methods, objectives,
required results, relevant standards and
codes
• Is not intended to replace knowledge and
understanding of obligations
Compliance Report
• Clearly summarise compliance as per
technical requirements
• Display relevant testing in a fit-for-purpose
manner such as
– system design diagrams (R & I, DC)
– system settings and trip equations
– trends of injected and monitored values
Summary
• AUFLS systems must be tested both
initially and routinely
• Companion Guide for testing has been
developed by the system operator
• Test requirements are set out fully in the
technical requirement schedule
Questions