PMACS Software Test Plan

1
PMACS Software Test Plan

• NEPTUNE Preliminary Design Review
• 4-5 December 2003
• Chen-Ching Liu, Ting Chan, Kevin Schneider

2
PMACS Software Test Plan

• Software test plan for PMACS
• General Operations
• State Estimation and Topology Error
  Identification
• Load Management and Emergency Control
• Fault Location

3
General Operations

• The testing of PMACS is to ensure the capability
  of PMACS in failover, alarm handling,
  communications, and availability
• Switching between main and backup systems
• Switching between primary and back up computer
  system
• Switching between primary Master station and
  secondary Master station
• Alarms and alert messages
• Multiple number of system constraint violations
• Current constraint violations at multiple
  locations
• Voltage constraint violation at multiple nodes

4
General Operations

• Availability Test
• A uptime/(uptime downtime)
• Communications Test
• Data transfer between the science nodes and the
  Master stations
• Data consistency between primary and secondary
  Master stations
• Communications and data transfer between the
  Master stations

5
State Estimation

• The testing of State Estimation algorithm in
  handling missing data and error of system data
• Failure of all measurements at a single science
  node
• Failure of a string of measurements
• Failure of multiple measurements not in a string
• Error in the assumed value of the link resistance

6
Topology Error Identification

• Evaluation of the topology processor for
  different topologies and load configurations
• Low system loads
• High system loads
• Regions of simultaneously high and low system
  loads

7
Load Management and Emergency Control

• To verify proper operation of the software,
  communications and load shedding functions are
  tested
• Check interface with the science node instruments
• Check interface with Data Management and
  Archiving System (DMAS)

8
Load Management and Emergency Control

• Load shedding to prevent voltage collapse
• Monitor voltage profile at individual nodes to
  prevent under voltage at science nodes
• Load shedding to reduce backbone line currents
• Estimating backbone current based on results of
  State Estimation to prevent over current
• Load is shed according to the schedule of power
  selected by the end users in accordance with the
  user contract.

9
Fault Location

• Divide system into 3 areas and perform test cases
  within each
• Radial branches connected directly from the shore
  station
• Fault current from each end of the link equal to
  the current outputs at the shore stations
• Network area with T connections
• Fault current from neither end of the link is
  known.
• Radial branches coming out of the network
• Fault current is the sum of shore stations output
  currents

10
Fault Location

• The following abnormal conditions will be tested
• Multiple measurements not available at one or
  both shore stations
• Voltage and current measurements are only
  available at one shore station
• Significant error associated with cable
  resistances
• Significant error associated with voltage drops