Appendix-II

STANDARD FACTORY ACCEPTANCE TEST (FAT) PROCEDURE

FOR SAS AND C&P of _____________S/S

LOA No :

PROJECT NAME :

DOCUMENT NAME : FACTORY ACCEPTANCE TEST (FAT)/ FACTORY SYSTEM TEST

(FST)/FUNCTIONAL PERFORMANCE TEST (FPT) PROCEDURE

DOCUMENT NO. : PG/CC/SAS/C&P/FAT, Rev0

ISSUE & DATE :

NAME DESIGNATION SIGNATURE

Prepared by :

Reviewed by :

Recommended by :

Approved by:

Page |1
Contents
General: 3
1 Test Configuration.................................................................................................................. 3
1.1 Equipment .............................................................................................................................. 3
1.2 Engineering documents.......................................................................................................... 4
1.3 Station level equipment: ........................................................................................................ 6
1.3.1 Hardware Component ........................................................................................................... 6
1.3.2 Software Components: .......................................................................................................... 7
1.3.2.1 Firmware Verification ............................................................................................................ 7
1.3 Test Equipment ...................................................................................................................... 9
1.4.1 Test Equipment Inspection .................................................................................................... 9
1.5 Power Checks ......................................................................................................................... 9
2. Functional testing ................................................................................................................. 10
2.1 Start-up and SAS system availability .................................................................................... 10
2.2 Monitoring and control ........................................................................................................ 11
2.2.1 BCU – displays and handling ................................................................................................ 11
2.2.2 HMI – modes of operation and user management .............................................................. 12
2.2.3 HMI – Displays and Handling ............................................................................................... 13
2.2.4 Inspections of HMI typical bay screens ................................................................................ 15
2.2.5 SCADA connection ............................................................................................................... 17
2.2.6 Control tests ......................................................................................................................... 18
2.2.7 Control method .................................................................................................................... 19
2.2.8 Control of dummy circuit breaker ........................................................................................ 19
2.2.9 Control of circuit breaker ..................................................................................................... 19
2.2.10 Synch-check ......................................................................................................................... 20
2.2.11 Control of isolator and earthing switch ............................................................................... 22
2.2.12 Interlocking (bay and station based).................................................................................... 23
2.2.13 Switching sequences for GIS ................................................................................................ 23
2.2.14 Digital RTCC Functions (if applicable)) ................................................................................. 23
2.2.15 Event processing .................................................................................................................. 24
2.2.16 Alarm processing.................................................................................................................. 25
2.2.17 Analogue measurement handling ........................................................................................ 26
2.2.18 Changing of alarm limits ...................................................................................................... 28
2.2.19 Redundancy/Availability and diagnostic function................................................................ 29
2.2.20 Additional Tests ................................................................................................................... 34
2.2.21 Remote Desktop .................................................................................................................. 35
2.2.22 Time synchronization ........................................................................................................... 35
2.3.1 Validation of OWS Memory and Disk Utilization ................................................................. 36
2.3 EWS TEST.............................................................................................................................. 36
2.4.1 Setting and Configuring of BCUs .......................................................................................... 36
2.5 Auto Reclose Test ................................................................................................................. 37
2.5.1 Test for Auto-Reclose Successful case:- ............................................................................... 37
2.5.2 Test for Auto-Reclose Failure case:- .................................................................................... 37
2.6 Setting of Protection Relays ................................................................................................. 37
2.6.1 Setting of Main-1 Protection Relays .................................................................................... 37
2.6.2 Setting of Main-2 Protection Relays ............................................................................ 38
2.7 DR Configuration : Check DR is configured as per TS as per following ............................ 38
2.8 Disturbance File Retrieval ........................................................................................... 38
3.2 BCU Input/output Data Retrieval ................................................................................ 39
3.3 Substation Controller Device Reporting ....................................................................... 40
3.3.1 IEC 60870-5-101 Data Retrieval................................................................................... 41
3.3.2 Master Digital Inputs Retrieval .................................................................................... 41
3.4 Master Analog Inputs Retrieval ................................................................................... 41
3.5 Statement of System Acceptance ................................................................................ 41
3.6 Duration of Factory Acceptance Test .......................................................................... 41

Page |2
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

General:
This document is used as a standard test protocol of all tests to be done at the Factory Acceptance
Test (FAT) for the typical Substation Automation System (SAS) and Control &Protection system of
every substation.
Aim of the Factory Acceptance Test (FAT) is to demonstrate equipment and functionality as well as
the approval of the system-parameterization by POWERGRID to reduce the change requests during
commissioning at site. The general philosophy shall be to deliver a system to site only after it has been
thoroughly tested and its specified performance has been verified, as far as site conditions can be
simulated in a test lab. During FAT the entire Sub-station Automation System including complete
control and protection system to be supplied shall be tested for complete functionality and
configuration in factory itself. The extensive testing shall be carried out during FAT. The purpose of
Factory Acceptance Testing is to ensure trouble free installation at site. No major configuration setting
of system is envisaged at site.
This document details the equipment and functions under test and the corresponding test methods as
well as the test documentation.
1 Test Configuration
1.1 Equipment
For the FAT configuration the following equipment will be present:
Computer type: Quantity (complete SW installed)
(Make e.g. Advantech) Engg./DR PC Server PC Client/HMI PC Gateway PC
(Model)

Network components: Quantity

Station Level Bay/Dia Level

Make/Model Nos. Make/Model Nos.

Ethernet Switch
GPS Time server
Router cum Firewall

Networking Panel
Auxiliary BCU Panel
Protection & Relay Panels NA NA

Peripheral Quantity
Make/Model Nos.
Event Printer
DR Printer (Color)
Logbook Printer
Auto-Changeover switch for
redundant UPS supply
UPS (5 kVA)

Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
Page3
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

Note: These equipment quantities shall be verified w.r.t. Engg. approved SAS Architecture and
BOM.

S.NO. IEDs Used For IED Make IED Model Quantity

Functions
1. Main-1 Distance Relay 21M1

2. Main-2 Distance Relay 21M2

3. Transformer Diff. Relay 87T

4. Transformer REF Relay 64

5. Reactor Differential 87R

Relay
6. Reactor REF Relay 64R

7. Bay Control Unit BCU

8. BB Diff. Relay 87CU/MCU

9. Peripheral Unit 87PU/ BU

10. LBB Relay 50BF

11. Backup Impedance 21R

Relay
12. Master Trip relay 86A/B

13. Auto-reclose Relay 79

14. Stand-alone DR 21DR

15. TEED Differential Relay

16. Over Flux Relay

17. Controlled Switching

Device
18. Transformer B/U O/C

19.

Notes:1) Typical units will be present which can be loaded with different configurations
For an overview drawing of the equipment installed for the FAT please refer to the Appendix.

1.2 Engineering documents

Purpose
This test verifies that the correct manufacturing drawings and documentation for the
equipment/system under test will be used during the Factory Acceptance Test.
Procedure
1. Verify that approved drawings (printed and soft copies) of all assembled equipment are present.
2. Verify that the detailed signal list for SCADA as per POWERGRID specimen signal list is available
with IEC 61850 addresses and display text as per the list.
3. Verify that the detailed GOOSE matrix with publisher and subscriber details are available.
4. Verify all required hardware and software manuals are present.

Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
Page4
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

5. Guaranteed Technical Particulars (GTPs) as approved by POWERGRID are included in Appendix A for
reference.
6. Copy of Customer Technical Specification for reference is made available in the FAT room.

Drawing Verification Log:

Cubicle Document Title Approved Drawing/ Doc. No. Checked
Overall System Architecture □
Standard General Technical Particulars for □
SAS
Functional Design Specification □
Signal List for SCADA
Matrix for GOOSE messages (with publisher
& subscriber details)
GA & Scheme of Networking Panel □
Bill of Quantity □
Server 1 □
Server 2 □
Gateway 1 □
Gateway 2 □
OPERATOR WORKSTATION 1 □
OPERATOR WORKSTATION 2 □
ENGINEERING/DR PC □
ICT Feeder □
Line Feeder □
Line Reactor Feeder □
Bus Reactor Feeder □
Tie Bay of all type □
Bus Coupler □
Bus Sectionalizer □
Bus-bar □
GPS □
UPS □
Other applicable drgs (not listed above) Attach the list as annexure □
Hardcopy & Softcopy Manuals Verification Log:
Cubicle Document Title Doc. No. Checked
Signal List for SCADA □
Matrix for GOOSE messages (with publisher & subscriber details) □
Operation and Technical Guide of BCU, GATEWAY, □
SERVER/CLIENT SOFTWARE
Relay Configuration Software for Main-1 □
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
Page5
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

Relay Configuration Software for Main-2 □

NMS Software □
Ethernet Switch □
Time Synchronizing Equipment □
Router cum Firewall □
UPS □
1.3 Station level equipment:
Soft- and hardware components are checked to ensure required functionalities. Versions are recorded
for later support purposes.

1.3.1 Hardware Component

The following hardware equipments are to be present during FAT:
• All Bay Control Units as per approved BOQ.
• All Protection Relays as per approved BOQ.
• HMI/Redundant HMI system consisting of redundant servers.
• Time Synchronizing Equipment consisting of GPS Receiver Unit, Antenna, Time Display Unit.
• Substation Controller/Gateway Subsystem
• Color Printer
• LAN switch equipment
• Auxiliary Panel
• UPS
The above equipment are to be as per approved standard GTP
Purpose
To verify that all hardware equipment required in the contract are available in the FAT room for testing.
Procedure
1. Visually inspect units and individual modules for cleanliness and ensure that they are free from
damage.
2. Visually inspect the units for correct wiring practices and ensure that they are free from insulation
damage.
3. Ensure the equipment is configured for proper point capacity as per approved drawings.
4. Ensure all modules, terminations and cables have the proper location labels as per approved
drawings.
5. Ensure that all earth ground and shield connections are correctly bonded in the panels.
6. Ensure all equipment is free from all foreign material (Dust, Solder, droppings etc.)
Hardware Visual Inspections Log:
S.NO. Equipment Hardware Specification Serial No. Checked
(CPU/RAM/HDD)
1 Server Workstation-1 □
2 Server Workstation-2 □
3 Operator Workstation-1 □
4 Operator Workstation-2 □
5 Gateway #1 □

Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
Page6
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

6 Gateway #2 □
7 Disturbance Recorder PC □
8 Color Laser JET Printer NA □
9 Dot Matrix printer NA □
10 GPS Receiver Unit NA □
Panel Visual Inspections Log:
S.NO. Equipment Serial No. Circuit Name Quality of Wiring Checked

1. Networking Networking Panel □

Panel
2. Aux. Panel Aux. Panel □
3. Inverter □
4. Modem □
5. ---- □
6. ---- □

1.3.2 Software Components:

The Software to be used will include the following applications:
• The BCU/IED with IEC 61850 (Server/Client) capability.
• HMI & Server with latest Version with IEC 61850 (Client) capability.
• Gateway with latest Version with IEC 60870-5-101 & 104 capability.
Configuration files shall be downloaded prior to commencement of tests and shall be the actual
configuration files for individual S/S.
1.3.2.1 Firmware Verification
Purpose
To verify and record that the Equipment Firmware used in the FAT.
Procedure
Using Device Display verify all BCU/IED equipment firmware version.
Firmware Verification Log.
S.NO. Equipment Model Operating System/Firmware Checked

1 HMI-1 □
2 HMI-2 □
3 DR PC □
4 Color Laser JET Printer □
5 Dot Matrix Printer □
6 Gateway-1&2 □
7 Ethernet Switches □

Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
Page7
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

8 Voltage Level_BCU_BAY No. □

9 Voltage Level IED’s □
(IEC61850 Compliant) for
Dia

SCADA Devices - IP Addresses

Will be checked at each device user interface.
System Devices

Designation N/W Name GOOSE ID IP Address Checked

SERVER 1 172 16 55 1 □
SERVER 2 □
OWS1 □
OWS2 □
EWS/DR PC □
SDC1 □
SDC2 □
GATEWAY1 □
GATEWAY2 □
GPS Time Server 1 □
GPS Time Server 2 □
Ethernet Switch 1 □
Ethernet Switch 2 □
Event Printer □
Color Laserjet Printer □
Router cum Firewall 1 □
Router cum Firewall 2 □
19 Port Managed LAN □
Switch

RELAY’S NAME N/W NAME GOOSE ID IP Address Checked

Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
Page8
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

172 16 55 101 □
P444 _____ LINE #01_21M1
□

1.3 Test Equipment

The following equipment are required to conduct the test.

• EWS/DR PC to be used for Configuration Applications for different IEDs.

• Hand-held Digital Multi-meter suitable for AC/DC with peak-hold and continuity tester.
• Digital Clamp-on Meter suitable range for secondary current measurement.
• Three phase injection KIT (Relay Test Kit) for supplying 3 phase current and voltage.
• 4-20 mA Injection Kit.
• Protocol Analyser as applicable.

1.4.1 Test Equipment Inspection

Purpose
To ensure that the Test Equipment to be used is operational and have valid calibration.
Procedure
Visual inspection of calibration stickers and certificates. Power up and verification that units are
operational.
Test Equipment Inspection Log:

S.NO. Equipment Calibration Check Device Power On Checked

1 3 Phase Injection Kit □

2 Precision Hand-held Digital □
Multi Meters
3 Digital Clamp-on meter □
3 Insulation Resistance □
Tester
4 220V DC Source for □
powering up all SAS Panels
5 4-20 ma Injection Kit □
1.5 Power Checks
Purpose
To ensure that the SAS equipments installed in the panels & control rooms are operating when
connected to the nominal specified power supply (220 V AC/DC).
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
Page9
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

Setup/Program
Perform the steps below to confirm correct operation of all equipment connected to the power
supplies.
Procedure
1. Verify that all 220V AC/DC equipments are powered at the nominal AC/DC supply voltage input.
Using a Digital Multimeter verify that the nominal AC/DC supply voltage is present.
2. Verify that there are no abnormalities seen when the equipment are turned ON.

Power Checks Log:

S.NO. Panel Equipment Device Power ON Checked

1 NA Server-1 □
2 NA Server-2 □
3 NA HMI-1 □
4 NA HMI-2 □
5 NA DR PC □
6 Gateway-1 □
7 Gateway-2 □
8 NA Laser JET Printer □
9 NA Dot Matrix Printer □
10 Networking Panel Auxiliaries (Lighting etc), LAN □
Switches, Gateway

11 Relay Panel Relays and Wiring diagram □

2. Functional testing
General Substation Automation System (SAS) is a combination of different bay control units and
protection devices with a central operator placed as Human-Machine-Interface (HMI) and central data
storage and acquisition. These components and its connections are shown in the System Architecture.
For SAS-FAT a configuration is selected to check the basic system functions and the co-operation
between the different components. The test procedure will show the proper function of the system in
general. All of decentralized I/O devices (bay control units and protection devices) is provided for this
test. A complete test of all I/O signals (see SAS signal list) is objective of this test. All modules are
tested by type tests in general and by test routines during manufacturing.

2.1 Start-up and SAS system availability

For following equipment the start – up times are measured to check the performance. The timing of
the station controllers starts with switching on the power supply and finishes after reaching the
working condition “RUN”. The timing of the Operator Workstation starts with switching on the power
supply. The computer will then start - up automatically without registering to Windows or manual start
of any software. The timing finishes after reaching the start picture of the application software where
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 10
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

the user has to register with his password. The timing of the Engineering PC and Protection Interface
PC starts with switching on the power supply and finishes after successful achievement of the working
condition.

System Start-up checked Time Comments see

log sheet no.
Server-1 □
Server-2 □
Operator Workstation 1 □
Operator Workstation 2 □
Engineering/DR PC □
Gateway 1 □ Data Transmission to RCC/RLDC
should resume automatically
Gateway 2 □ Data Transmission to RCC/RLDC
should resume automatically
Complete system start up □ Black Start

After start-up of all devices the error free operation, communication and time synchronization of
components is checked on the SCADA displays.
S.NO. System Start-up Checked

1. Time synchronization of Substation controllers / PCs □

2. Time synchronization of connected IEDs □
3. Communication to Bay Control Unit □
4. Communication to Protection Devices □
5. Event list printer □
6. Hardcopy color/ Logbook printer □
7. Communication with remote control centres □
2.2 Monitoring and control

2.2.1 BCU – displays and handling

General layout, handling and control of typical feeder BCUs is demonstrated and checked under this
chapter. The displayed SLD is cross checked against the approved SLD/ Mimic SLD.
BCUs for _____kV Level checked Comments see
log sheet no.

Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 11
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

Basic/control display for OHL □

FEEDER
Basic/control display for □
TRANSFORMER FEEDER
Basic/control display for LINE □
REACTOR FEEDER
Basic/control display for BUS □
REACTOR FEEDER
Basic/control display for TIE □
BAY/TBC
Basic/control display for
AUXILIARY System
Basic/control display for BUS □
COUPLER
Basic/control display for BUS □
SECTION
Event list □
Alarm list □
Analogue measurement list □
Metering list □
Alarm limits □
Handling of displays, control □
and menu
Changing V,I,f – limits:
- current >limit 1
- current >limit 2
- voltage >limit 1 □
- voltage <limit 1
- frequency >limit 1
- frequency <limit 1
BCUs for _____kV Level □

2.2.2 HMI – modes of operation and user management

A multi-level login is implemented in SCADA. There are 4 different levels of access. Without login,
there is no possibility to open any display. The different access levels are implemented as shown in
following table:

Purpose
To verify that the OWS/HMI system has Security Classes, that are enabled and configured properly.
Setup
1. Ensure that the HMI Servers are running.
Procedure
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 12
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

1. Start Client, by default the user will be logged in as blank.

2. Verify that this user class has proper access level as per HMI Security Classification.
3. Go to any bay detail screen. Verify if access to tool bar and object controls are according to that
allowed in the access level logged in.
4. Repeat steps 1 to 3 for the other HMI Usernames (Operator, Protection, Administrator)
5. Repeat steps 1 to 4 for the other Workstations
6. Function is tested by clicking on the corresponding buttons or switching devices and checking of
SCADA “No permission” – notifications.
HMI Access Level:
Access Level Monitor Operator Engineer Administrator Checked Comments
see log
sheet no.
Display System Status & Yes Yes Yes Yes □
View Screens
Controls – CB, Isolators No Yes Yes Yes □
Acknowledge/Clear No Yes Yes Yes □
Alarms
Change HMI Config. No No No Yes □
Create/Disable/Delete No No No Yes □
User Account

Change User No No No Yes □

Profile/Access Level
Maintenance mode No No Yes Yes □
Reset lockout relay No Yes Yes Yes □
Interlocking bypass No No Yes Yes □
Sync. Check Bypass No No Yes Yes □
Auto-reclosure No No Yes Yes □
Auto sequence No No No Yes □
Shut down the system No No Yes Yes □
2.2.3 HMI – Displays and Handling
Check that the displays are in accordance with POWERGRID requirements. General layout and handling
is demonstrated and checked. Overview and control pictures are cross-checked against the approved
substation SLD.
Purpose
To verify that the Single Line Diagram and Bay Detail Screens on the OWS system are configured
properly and are in correct operating condition.
Setup
1. Ensure that the HMI Servers are running.
2. Log in as an “Operator”.
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 13
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

Procedure
1. Verify the layout of each SLD on the OWS.
2. Verify the device number, device description and device symbol for each device.
3. Verify all displayed analog and digital values on the detailed bay view screens.
4. Click on each device object and confirm that the respective popup screen or bay/view detail screen
is displayed.
5. Repeat steps 1 to 4 for each SLD / Detailed Bay View.

Checked Comments see log sheet no.

Handling of screen/picture selection □
Display for Station overall SLD □
Display for ______kV overview: □
- ______kV substation overview □
- ______kV single line diagram view □
Display for _____kV overview: □
- ______kV substation overview □
- ______kV single line diagram view □
Display of Measurement Trends (Real-time and □
Historical)
Display of maintenance mode □
Display of safety tagging □
Display of Operations counter for PLCC & CB □
Display of Network/LAN overview □
Display of typical bay communication (Ring) □
Display for Auxiliary System views □
Display of event list □
Display of alarm list □
Handling of screen/picture selection □
Basic/ Control display for Kiosk Air Conditioning □
System
Basic Control display for Online Monitoring □
System for Transformers & Reactors
Basic /Control display for Control Switching □
Device
Display of Counter for LA & PLCC □
CVT/CT Monitoring □
Visual Monitoring System □
Transformer Bank with Tap changer Operation □
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 14
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

(In case of extension packages, the existing make SCADA system of the substation where extension
is proposed shall be used to carry out the validation of extension bays signals, control commands,
etc., with the extension bays configured as the only bays that exist in the substation. For this
purpose, the existing SCADA system can be installed in a laptop. Further after completion of FAT, the
verified SCADA configuration shall be used for addition into the existing SCADA at site.)

2.2.4 Inspections of HMI typical bay screens

Validation of electrical views

Purpose
To verify that the Single Line Diagram and Bay Detail Screens on the OWS system are configured
properly and are in correct operating condition.
Setup
1. Ensure that the HMI Servers are running.
2. Log in as an “Operator”.
Procedure
1. Verify the layout of each SLD on the OWS.
2. Verify the device number and device description for each device.
3. Verify all displayed analog and digital values on the detailed bay view screens.
4. Click on each device object and confirm that the respective popup screen or bay/view detail screen
is displayed.
5. Repeat steps 1 to 4 for each SLD / Detailed Bay View.

Bay screens ________kV Checked Comments see log sheet no.

Naming, SCADA numbers, status indications,
measurement items to be checked
_______kV LINE FEEDER □
_______kV TRANSFORMER FEEDER □
_______kV BUS REACTOR □
_______kV LINE REACTOR □
------
--------
Bay screens ________kV
Naming, SCADA numbers, status indications,
Measurement to be checked
_______kV LINE FEEDER □
_______kV TRANSFORMER FEEDER □
_______kV SHUNT REACTOR □
_______kV BUS REACTOR □

Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 15
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

_______kV LINE REACTOR □

------ □
--------

Validation & Verification of Signals on SCADA HMI

Purpose
To verify that the signals as per the specimen signal list provided by POWERGRID has been
correctly configured and are appearing on SCADA HMI as desired.
Setup
The Detailed signal list based on which the SCADA configuration has been prepared shall be taken and
each signal shall first be validated (e.g appearance of “Valid”, Reset/ Set/operated/Healthy, etc status
as per the appearance of on screen validity shall be checked). Any signal appearing as “unknown” /
“invalid” shall be flagged and configuration shall be modified for proper validation.
After validation of signals under SCADA configuration, various protection functions and appearance of
the desired signals on SCADA HMI shall be verified.
For certain signals (having Integer type attribute), the on-screen display of text displayed depends on
the value fetched from IED, (e.g. Auto-reclose status from function RREC wherein the value of
AutoRecSt 1 denotes ready, 2 denotes Auto-reclosure in-progress, etc). All types of text displays with
different inputs shall be verified by simulation of the state.
For all the IEDs subscribing to GOOSE messages from other IEDs ( e.g. BCUs), which are used to
perform logical actions, the appearance of GOOSE fail / GOOSE trouble alarm shall be configured and
verified by making one of the GOOSE message absent, to which the IED subscribes.
The Voltage selection logics for ICTs & Rector feeders, utilizing GOOSE messages shall also be verified
by simulating various switchgear status, which change the selected voltage.

Validation of Historical Trend

Purpose
To verify that the Trending in the OWS system are configured properly and are in correct operating
condition.
Setup
Ensure that the HMI servers are running.
Go to Trend Screen.

Validation of Historical Trend on OWS

S.No. Activity Checked

1 Verify the all Analog signals on trend screen. □

3 Verify that the trend curve on HMI screen for different analog □
signal has different colors.

Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 16
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

4 Verify that the Time Scale for trend curves are user settable. □
5 Verify that EHV Lines have Predefined trend of active and reactive □
power, ICT have Predefined trend of current, active and reactive
power. Bus have Predefined trend of voltage and frequency.

6 Data archive retrieval is to be checked for proper display of old □

records

Validation of Reports Function

Purpose
To verify that the Reports Functions (Historical Report) in the OWS/HMI system are configured
properly and are in correct operating condition.
Setup
1. Ensure that the Client & Server is running.
Procedure
Historical Event Report
1. Generate some Digital / Analog events in the BCU.
2. Click on the Reports button present on the HMI Screen.
3. Select the Range of date by selecting the Start Date and End Date.
4. Verify whether the same generated events have been produced in the Historical Report.
Daily Report (Hourly Instantaneous Value of Analog Data Points)
1. Inject Voltage & Current through 3 Phase Injection Kit to any BCU.
2. Verify the values on the detailed view of the selected BCU.
3. Select the daily Report Button of line BCU.
4. Verify the daily Report have produced Hourly instantaneous Value of the selected BCU. The
Maximum and minimum instantaneous value of each selected parameter (with time) shall also
be included in the report. This time-tagged max and min data shall be generated from the
Trend data of the BCU.
5. Data archive retrieval is to be checked for proper display of old records
Operation Reports:
Apart from Historical and trend reports of analog values, reports in specified formats as per the
requirement of POWERGRID system operation is also to be generated in the standard format provided
by POWERGRID. The reports will be periodic logging ( 01 hourly/ 04 hourly/ 08 hourly etc) of analog/
digital values and mainly cover the EHV feeder , Transformer & Reactors temperatures, AC & DC
Auxiliary supply system, Battery chargers, CB operation counter readings, PLCC counter readings etc.
2.2.5 SCADA connection
In this chapter the communication to SCADA via IEC101/IEC104/IEC 61850 will be checked. Detailed
information test (control authority, command and indication) will be done in the chapter followed to
this. SCADA-interface is simulated with test program IEC-Test running on two laptops. With the test
program the protocols IEC-101/IEC-104 as well as IEC-61850 can be simulated. Detailed redundancy
tests will be performed under chapter 2.2.20.4/3.2.20.5.
Checked Comments see log sheet no.
Communication check for □
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 17
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

- spontaneous information □
- general interrogation
- time stamping of indications □
2.2.6 Control tests
Control is possible from Relay Panel/MIMIC Board, BCU, Operator Workstation (1 or 2) and
NTAMC/Backup NTAMC/RTAMC. During the test all check back indications from switchgear devices
will be simulated by an I/O simulation box. Preconditions for controls are correct switching conditions
(synch-check and interlocking). Switching the relevant local/remote switch will be displayed in event
list.

Checked Comments see log sheet no.

A. Control from mimic board □

The mimic board is implemented in the cubicle
B. Control from BCU □
Changing status of local/remote switch on BCU
raises an event on event list. Control from BCU is
only possible if local/remote switch on
BCU is in local position and local/remote switch on
mimic board is in remote position. In this position
no control from Operator
Workstation and SCADA is possible.
C. Control from Operator Workstation □
Changing status of local (SCADA) / remote
(SCC/ECC) button on Software screen raises an
event on event list. Control from Operator
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 18
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

Workstation is only possible if control is switched

to local position and local/remote switch on BCU
and mimic board is in remote position. In this
position no control from SCADA is possible.
D. Control from SCADA □
Control from SCADA is only possible if all
local/remote switches per bay (on bay- and station
level) are in remote position. SCADA interface is
simulated with test program IEC Test.

2.2.7 Control method

Control of switchgear shall be done from the detailed bay display diagrams in OWS. The method of
man machine dialogue shall be a multi-stage procedure with verification to ensure security of control.

Checked Comments see log sheet no.

- Selection of switching device □
- Appearance of selected device control window □
- Selection of switching direction (open/close) □
Change of the selected device symbol(flashing □
in selected control direction)
- Execution of the control □
- Possibility of cancellation at any time □
- Time out of control mode if operator fails to □
respond
- Source of control appearance in event list □
- Double object control blocking function for □
control from HMI/ SCADA level

2.2.8 Control of dummy circuit breaker

Checked Comments see log sheet no.
- Check of dummy circuit breaker function □
2.2.9 Control of circuit breaker
“CLOSE” and “OPEN” operation of 765/400kV typical circuit breaker is tested by giving a command from BCU or
HMI and checking of the command execution. At the same time, the respective check back indication of
switching position is checked at the BCU and HMI. The correct registration in the event list will also be tested. All
the bays for each voltage level will be checked. Furthermore some faults will be simulated (e. g. control authority,
CMD interlocked, CMD monitoring time). SCADA-interface is simulated with test program IEC-Test.

Command Checked typical Comments see log

701-52 702-52 703-52 704-52 sheet no.
765kV Circuit breaker
Control/Display BCU
Control/Display HMI □ □ □ □
Control/Display □ □ □ □
SCADA
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 19
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

HMI/SCADA Display □ □ □ □
event list
□ □ □ □
400kV Circuit breaker
Control/Display BCU
Control/Display HMI □ □ □ □
Control/Display □ □ □ □
SCADA
HMI/SCADA Display □ □ □ □
event list □ □ □ □

2.2.10 Synch-check
Synchro check-function is parameterized in the BCU. Therefore control is demonstrated from bay
control unit for functionality-check. Positions of bus bar voltage transformer disconnecting switch are
simulated by an I/O simulation box and bus bar voltage by a test set (e.g., Relay Test Kit).
Purpose
To verify that Incoming and Running (Reference) voltages are within the synchronizing range before
the circuit breaker can close. The circuit breaker will not close if any of the limiting parameters is not
within the check synchronizing range. For practical reasons this FAT will not include the testing of
Running Voltage selection for the Synchronization.
Setup
1. Set up the BCU to check synchronizing ranges as follows:
• Phase Differences Specification requirement states Phase Difference shall not exceed 30° (1º
Hysterisis).
• Voltage Difference Specification requirement states Voltage Difference shall not exceed 10%
(2% Hysterisis).
• Frequency difference 0.1 Hz (Connected System).
2. Set up the 3 Phase Injection Kit to supply the Running Voltage & Selected Voltage to BCU TMU card
(CT/VT card).
3. Set up the 3 Phase Injection Kit to the following test cases:

Check Synchronization Test Settings

Test Case Voltage Difference Phase Y Difference Expected Sync Checked
in pu in Degrees Close Results

1 0.20 40.0 No □
2 0.12 40.0 No □
3 0.10 20.0 No □
4 0.09 20.0 No □
5 0.09 17.0 No □
6 0.10 16.0 No □
7 0.10 15.0 Yes □
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 20
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

8 0.05 10.0 Yes □

Procedure
1. Select a BCU and corresponding Circuit Breaker to Test.
2. Using the 3 Phase Injection kit, inject the Running & Selected Voltage to the BCU and apply the
differences as shown in the above table.
3. Open the Detailed view of the selected Bay on the HMI and verify the voltage references.
4. Initiate the CB Close Request.
5. Verify that the Circuit Breaker closes only when the configured settings are satisfied.

CB CB Condition Checked
765KV Circuit Breakers
□
□
□
400KV Circuit Breakers
□
□
□
The above check sync verification is to be carried out for all possible voltage selection logics for
synchronization (e.g, for main bay breaker connected to Bus 1 in one and half scheme, Bus 1 Voltage-
Bus 2 Voltage, Bus 1 Voltage - Feeder 1 Voltage, Bus 1 Voltage – Feeder 2 voltage, as may be required
in the scheme). These possible voltage selection conditions are required to be simulated either by
simulated switchgear or by simulating GOOSE messages published by other BCUs, which are required
in the selection logic.

Dead Source Condition

Purpose
To verify that when the following conditions are met, the Synchrocheck logic permits the Immediate
closure of the Circuit Breaker.
• Dead Line-Dead Bus
• Dead Line-Live Bus
• Live Line-Dead Bus
Setup
1. Set up the BCU to check synchronizing settings as follows:
• Presence of Line Voltage (Param1) – 70%
• Absence of Line Voltage (Param2)– 20%
• Presence of Bus Voltage (Param3)– 70%
• Absence of Bus Voltage (Param4)– 20%
Procedure
The absolute values of the two voltages (Vline and Vbusbar) must be above or below settable
thresholds, to permit the circuit breaker closing. The following voltage controls are available:
• not (Vline) and not(Vbusbar) – (Dead Line-Dead Bus)
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 21
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

• not (Vline) and Vbusbar – (Dead Line-Live Bus)

• Vline and not (Vbusbar) – (Live Line-Dead Bus)
• Vline and Vbusbar – (Live Line-Live Bus)
With Vline and Vbusbar TRUE if the measured voltage is above the threshold V> (param 1 and param
3), and not(Vline) and not(Vbusbar) TRUE if the measured voltage is below the threshold V< (param 2
and param 4). These threshold are given in % of the nominal voltage value, updated at TMU220 board
level
The selection of the voltage control is made during the configuration phase.

Test Case Description Expected Sync Checked

Close Results

DL-DB In case of the absence of both voltages i.e. Yes □

not(Vline) or not(Vbusbar)

DL-LB In case of the absence of one of the two Yes □

voltages i.e. not(Vline) and Vbusbar

LL-DB In case of the absence of one of the two Yes □

voltages i.e. Vline and not(Vbusbar)

LL-LB In Case of the presence of both voltages i.e. No □

Vline and Vbusbar, Set beyond ranges

LL-LB In Case of the presence of both voltages Vline Yes □

and Vbusbar, Set good ranges

Checked Comments see log sheet no.

Displaying and handling - BCU □
- HMI
□
Checked Comments see log sheet no.
Live line – dead bus □
Dead line – live bus □
Dead line – dead bus □
Live line – live bus with fulfilled sync □
conditions (Vdiff, fdiff, angle) □

2.2.11 Control of isolator and earthing switch

“CLOSE” and “OPEN” operation of high voltage switching devices are tested by giving a command from
BCU or HMI and checking of the command execution. At the same time, the respective check back
indication of switching position is checked at the BCU and HMI. The correct registration in the event

Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 22
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

list will also be tested. One bay for each voltage level will be checked (400kV-station: “C03” and for
132kV-station: “E05”). Furthermore some faults will be simulated (e.g. control authority, CMD
interlocked, CMD monitoring time).
SCADA-interface is simulated with test program IEC-Test.

2.2.12 Interlocking (bay and station based)

Control of switchgear devices is only possible if all interlocking conditions are fulfilled. Interlocking
conditions are shown in circuit manuals of local control cubicles (For drawing nos. see chapter 1.2).
Generally for demonstration of interlocking the control can be done from bay control unit. As the
complete feeder interlocking is checked during SAT of BCU together with primary switchgear, only
some selected general functions are shown. Positions of relevant breakers/isolators are simulated by a
hardwired I/O simulation box. The interlocking logic and status for each switchgear should be visible
to the operator on operator HMI beforehand while going to operate the respective switchgear. The
validation of interlock condition shall be performed based on the interlock logic visible on the screen.

Checked Comments see log sheet no.

Maintenance mode □
Switchgear interlocking □
HMI – display of interlocking conditions along with □
signals for each switchgear device

2.2.13 Switching sequences for GIS

Switching sequences are initiated and controlled from Station Controller. The preconditions for
switching sequences are parameterized in BCU. The interruption of the switching sequence can occur
due to missing of one of the preconditions, either synch-check or interlocking. Correct switching and
the corresponding feedback indications will be checked. Randomly, some interlocking conditions will
be done in such a way that the switching sequence will be interrupted. The effect will be that the
system will wait for the command running time to terminate. In the event list a negative feedback will
be recorded indicating the reason for not executing the command.

CONNECT OHL FEEDER TO BB1:

closing of Isolators & CB
CONNECT OHL FEEDER TO BB2:
closing of Isolators &CB
DISCONNECT OHL FEEDER (Bay):
opening of
CHANGE BUSBAR:
closing/opening of Isolators
CLOSE BUS COUPLER :
closing of Isolators & CB
OPEN BUS COUPLER :

2.2.14 Digital RTCC Functions (if applicable))

The Digital RTCC Functions view shows information about the transformer feeder (ICT1-ICTn) of the
station. Information about: the tap position. Using the control button a tap position control window
will appear. It can be chosen between the automatic and manual mode. The tap position of each

Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 23
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

transformer feeder can be changed with the top/down slider by using the manual mode. The exit
button closes the window.

Properties of Digital RTCC Checked Comments see log sheet no.

- Selection of transformer feeder □
- Appearance of selected window □
- Selection of control mode (auto/manual) □
- Send TAP rise/ lower command in manual □
-Checking of Master-Follower/ independent mode □
-Checking of Other RTCC Functions □
2.2.15 Event processing
Events are displayed in chronological order in event list. All events have date and time tag. Selection of
event list on Operator Workstation will show the latest page with the newest event on top. Event list
shows all events including the alarms. Events are coloured in white. The creation of a reduced list is
possible by filter function. Transient conditions (i.e.00/11) will not generate an event, unless a time
delay is exceeded.
Purpose
To verify that the Events Points are configured properly and in correct operating condition.
Setup
1. Ensure that the HMI Servers are running.
2. Display the Event Screen.
Procedure

1. Select a Digital Input Point from one of the BCUs configured as an Event.
2. Change the state of the Selected Input
3. Verify that an Event is displayed in the Event Screen with proper description and Time Stamp.
4. Acknowledge this alarm.
5. Go to Event Screen and verify that this alarm is displayed in the list.
6. Verify that the same has been printed on the Dot Matrix Printer.
7. Repeat Steps 1 to 6 for the several Digital Input

Validation of the Events and Alarm Management on OWS

S.No. Activity Checked

1 Verify that separate logs are available for alarm and events □
2 Verify that suitable filters (sorting by date, time etc) are provided □
for both alarms and events
3 Verify that an Alarm and Event is displayed in the Alarm and Event □
Screen with proper description and Time Stamp
4 Verify the alarm acknowledgement facility and verify that their □
display changes in alarm viewer according to the alarm status
(active/inactive; acknowledged/not acknowledged)
Checked Comments see log sheet no.
Event processing - BCU □
- HMI
□
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 24
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

□
Time tagging - BCU
- HMI □
Filter function - date/time □
- message group □
- message text □
- alarm group □
Check naming convention of one typical feeder
according signal list □
- hierarchical name
- signal name
□

2.2.16 Alarm processing

Alarms are displayed in chronological order in alarm list. Selection of alarm list on Operator
Workstation will show the latest page with the newest alarm on top of the line. Coloring depends on
alarms status (raised, cleared and acknowledged). Acknowledgement of alarms dependents on
permissions level (see 2.2.2 “HMI – modes of operation and use)
Purpose
To verify that the Alarms are configured properly and in correct operating condition.
Setup
1. Ensure that the HMI Servers are running.
2. Display the Alarm Screen.
Procedure
1. Select a Digital Input Point from one of the BCUs configured as an Alarm.
2. Change the state of the Selected Input
3. Verify that an Alarm is displayed in the Alarm Screen with proper description and Time Stamp.
4. Acknowledge this alarm.
5. Verify that the same has been printed on the log Printer.
6. Repeat Steps 1 to 6 for the several Digital Input

Checked Comments see log sheet no.

Alarm processing - BCU □
- HMI
□
Time tagging - BCU □
- HMI
- Time stamp quality field □
Filter function - date/time □
- message group
- message text □
- alarm group □
□
Permission of acknowledgement □

Alarm raised: YELLOW FLASHING □

Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 25
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

Alarm cleared: GREEN □

Alarm acknowledged: YELLOW □
Alarm list filtering function (Date & Time, Bay □
No.)

2.2.17 Analogue measurement handling

Correct displaying of analogue values is checked on the screens of BCU and HMI. A change of analogue
quantity is reported to the SCADA master system. Correct displaying of power flow convention is
defined and checked. Measurements will be tested from BCU (in feed by a relay test set) as well as
from BCU :

Checked Comments see log sheet no.

Displaying of analogue values - BCU □
- HMI
□
Power flow convention □
Real time trends □
Measurement of each Bay: For e.g. Checked
CT Ratio: 3000A/1A * □
VT Ratio: 400KV/110V * □
Current Measurement:
Injected Expected Dead Indicated Value
second. measured band
Current value
R Y B
BCU HMI BCU HMI BCU HMI
0.0A
0.05A
0.5A
1.0A
1.1A

Voltage Measurement:
Injected Expected Dead Indicated Value
second. measured band
Voltage value
R Y B
BCU HMI BCU HMI BCU HMI
6.35V
31.75V
63.5V
70V
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 26
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

110V

Frequency Measurement:
Injected Dead band 48Hz 50Hz 52Hz
Frequency
BCU HMI BCU HMI BCU HMI

Indicated Value

Comments see log sheet no.

*CT & PT Ratio as per approved drawing

Injected Phase
Value Angle
Active Reactive Power Factor
Power Power
V with Calculat BCU HMI Err. Expecte BCU HMI Err. ( %) Calculat BCU HMI Err.(%)
ref. to I ed (%) d Value ed
Value Value

I= 0° 1
U=
60° 0.5
90° 0
120° -0.5
-120° 0.5
-60° -0.5

Transformer Measurement Values

Injected Measured Checked
Simulator HMI Error (%) Remote Control
Center
Oil Temperature ................................. °C

Winding Temperature HV .................. °C

Winding Temperature IV ................... °C

Winding Temperature LV ................... °C

Oil Temperature ................................. °C

Winding Temperature HV .................. °C

Winding Temperature IV ................... °C

Winding Temperature LV ................... °C

........................................................... °C

Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 27
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

........................................................... °C

General Station Analogue Values

Injected HMI Measured Checked Comme
SUPERVISORY nts see
log
sheet
no.
Simulator Display Error (%) Transmitted
Outside Temp………. ...°C □
Outside Humidity…….. ...% □
SCADA Room Temp……. ...°C □
Telecom Room Temp…. ...°C □
Battery Room Temp….. ...°C
SPR… Temp…… ...°C
SPR… Temp…… ...°C

Injected HMI Measured Checked Comment

SUPERVISORY s see log
sheet no.
Simulator Display Error (%) Transmitted
Current 220V DC 1 O/P .................
....A □
Voltage 220V DC 1 O/P ................
... V □
Current 220V DC 2 O/P .................
....A □
Voltage 220V DC 2 O/P ................
... V □
Current 48V DC 1 O/P ...................
....A
Voltage 48V DC 1 O/P ..................
... V
Current 48V DC 2 O/P ...................
....A
Voltage 48V DC 2 O/P ..................
... V

Diesel Generator Voltage ..............

... V
Diesel Generator Current ...............
..A

2.2.18 Changing of alarm limits

For supervising the analogue values each measured value shall have high and low alarm limits available.
It shall be possible to set each limit independently at the BCU stage. When an alarm limit is detected as
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 28
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

having been transgressed an alarm shall be generated and the value displayed on the VDU shall be
identified as in alarm status by use of color or other means to the approval of engineer.

Set point Checked Comments see

log sheet no.
Voltage - upper limit: □
107% of nominal value
- lower limit: □
95% of nominal value
- processing of alarm □
limits (color)
- hysteresis □
- alarm dead band □
Current - first upper limit: □
1000A for 400&765kV level
- second upper limit: □
1500A for 400&765kV Level
- processing of alarm □
limits (color)
- hysteresis □
Frequency - upper limit: □
105% of nominal value
- lower limit: □
95% of nominal value
- processing of alarm □
limits (color)
- hysteresis □

2.2.19 Redundancy/Availability and diagnostic function

The SAS system is designed for a hot/hot configuration. In order to fulfil this functionality following
test will be performed:

2.2.19.1 SAS – SERVER Redundancy

Purpose
In case of server failure the connected HMI operator workstations must switch to the healthy server.

Setup
Ensure setup as per approved SAS Architecture Drawing.
Procedure
1. With both Servers operational, verify that Clients are connected with their respective servers &
can perform normal function i.e. open different screens, alarm & trend screen.
2. On OWS-1 (Server1), Close the Server1 Application.
3. Check that Alarm appear on the client.
4. Observe that Client1 are now connected with the Server2

Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 29
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

5. Start the Server1 application on OWS1, Observe that Client1 are now connected with the OWS1
after some defined period of interval.
6. On OWS-2 (Server2), Close the Server2 Application.
7. Observe that Client2 are now connected with the Server1.
8. Check that Alarm appear on the client.
9. Start the Server2 application on OWS2, Observe that Client2 are now connected with the OWS2
after some defined period of interval.

Shutdown & Startup of Servers

Purpose
To verify that the HMI Redundancy is operational during the shutdown of the active server.
Setup
Ensure setup as per approved SAS Architecture Drawing.
Procedure
1. With both Servers operational, verify that Clients are connected with OWS-1.
2. Shutdown OWS-1. Observe that Client is now connected with the OWS-2 and receives
communications from the remote devices.
3. Startup OWS-1 . Observe that there is no interruption to the Bay Level Devices. Restart the Client.
4. Observe that Client is now connected with the OWS-1 (Primary Server) and receives
communications from the remote devices.
5. Shutdown OWS-2. Observe that Client is still connected with OWS-1.
6. Startup OWS-2. Observe that there is no interruption to the Bay Level Devices.

Voltage Level substation controller/Servers Checked Switch over Comments see log
time sheet no.
Server1 faulty:
Disconnect Server1 from LAN and generate
new inputs (events and alarms) on BCU.
Initiate control of any switching device.
• Check switchover of connected HMIs to SC 2
• Check updating of information □
event/alarm/analogue appearance on HMI 1 □
&2
• Check execution of command □
• Check event/alarm appearance on dot □
printer
• Check fault indication of SC 1
□
Server2 faulty: (Server1 healthy again)
Disconnect Server2 from LAN and generate □
new inputs (events and alarms) on BCU.
Initiate control of any switching device. □
• Check switchover of connected HMIs to □
Server 1
• Check updating of information □
event/alarm/analogue appearance on HMI 1 □
&2

Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 30
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

• Check execution of command

• Check appearance on dot printer
• Check fault indication of Server 2

2.2.19.2 SAS– HMI Operator workstation redundancy

Each HMI operator workstation is independent of the other operator workstation and in case of failure
the second workstation remains operational
Comments see Comments see log sheet no.
log sheet no.
HMI 1 faulty
Disconnect HMI1 from LAN and generate new
inputs (events and alarms) on BCU. Initiate □
control of any switching device. □
• Check updating of information on HMI 2
• Check execution of command □
• Check appearance on dot printer □
• Check fault indication of HMI 1
□
HMI 2 faulty (HMI 1 healthy again)
Disconnect HMI2 from LAN and generate new □
inputs (events and alarms) on BCU. Initiate
control of any switching device. □
• Check updating of information on HMI 2 □
• Check execution of command
• Check appearance on dot printer □
• Check fault indication of HMI 1 □
HMI 1 and HMI 2 healthy again □
Check database synchronizing

2.2.19.3 SAS – Network redundancy

Reliability and security of the redundant LAN configuration will be checked.
Purpose
To verify that
• Ethernet connections in the Substation Automation System are functional and running.
• LAN Switch Redundancy is functional.
To establish that in the event of a loss in communications, the SAS device are OFFLINE. When
communications link is restored, the SAS device are automatically back to ON-LINE.
Typical Procedure:
ETHERNET LAN REDUNDANCY CHECK

1. Choose a Switch in the LAN. Let it be Switch B in below fig having switches A & B adjacent to it.
There are two ports, 3 & 4 of switch B connected to two ports, 1 & 2 of switch A. Similarly
there are 2 other ports in switch B, 5 & 6 connected to ports 7 & 8 of switch C (as shown in
figure).
1 3 5 7
Switch A Switch B Switch C
2 4 6 8

Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 31
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

2. On switch B Disconnect port 3 LAN cable. Verify that no device in the entire system fails to
communicate.
3. On switch B Disconnect port 4 LAN cable. Verify that no device in the entire system fails to
communicate.
4. On switch B Disconnect port 5 LAN cable. Verify that no device in the entire system fails to
communicate.
5. On switch B Disconnect port 6 LAN cable. Verify that only those devices, which are connected
to switch B, fail to communicate.
6. Restore the LAN cables in reverse order and check that communication of the devices above
gets restored.
7. Repeat the above for all other switches in the Redundant RING LAN.

LAN Communication Functional Check test Results Log

S.NO. Panel Equipment Communication Redundancy check

check

1 ____KV BCU (Bay

01/02/03---)

2 ____KV BCU (Bay

01/02/03---)

3 Networking Panel

Comments see Comments see log sheet no.

log sheet no.
Checking Station Ethernet ring
Checking functionality in case of disconnecting
and connecting the ring at several points.
Initiate control of any switching device. □
• Check redundancy
• Check fault indication from adjacent units □
• Check appearance on HMI 1 & 2 □
• Check execution of command
• Check dynamic animation of SCADA pictures □
(Communication ports status etc.) □
Checking Bay Ethernet ring
Checking functionality in case of disconnecting
and connecting the ring at several points.
Initiate control of any switching device. □
• Check redundancy □
• Check fault indication from adjacent units
□
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 32
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

• Check appearance on HMI 1 & 2 □

• Check execution of command
• Check dynamic animation of SCADA pictures □
(communication ports status etc.)
Checking the communication of switches
Checking functionality in case of disconnecting
and connecting the Ethernet switches and
router at several points. Initiate control of any
switching device.
(1x optical, 1x electrical, 1x 1GB port) □
• Check redundancy □
• Check fault indication from adjacent units
• Check appearance on HMI 1 & 2 □
• Check execution of command □
• Check dynamic animation of SCADA pictures
(communication ports status etc.)
□

2.2.19.4 Gateway redundancy (IEC 104 & IEC101 Ports)

The redundancy of the IEC 101 communication interface from the Gateways will be checked. As the
real SCADA system is not available 2 Laptops with the IEC TEST – Software are used to simulate the
RCC& RSCC.

2.2.19.5 Time synchronization redundancy

Redundancy of GPS time synchronization is tested. One clock will be disconnected from the network. It
is checked that the various devices are still time synchronized (i.e. by changing the time manually for a
device and check that it gets synchronized again).

Time synchronization redundancy Checked Comments see log sheet no.

Disconnect GPS time server 1 from the network □
Check availability of correct time synchronization
Reconnect GPS time server 1 and disconnect time
server 2 (any one of the IED/OWS internal clock)
from the network Check availability of correct time
synchronization

2.2.19.6 Safety tag facility

It is checked that safety tag facility is realized in SCADA. A triangle with exclamation mark is set on the
respective switching device.

Checked Comments see log sheet no.

Processing of safety tag facility □
Properties of safety tagging □
- 3 different types of safety tags
- notebook facility (date, time, user, ...)
- prevent of SCADA control
Display on the - overview picture □
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 33
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

- individual bay display

Check appearance on redundant server/operator □
2.2.19.7 Maintenance mode
It is checked that individual feeders can be set into maintenance mode. No control is possible and no
alarms/events can come up during the feeder is in maintenance mode, which is indicated by
annunciation “MAINTENANCE MODE.”
Checked Comments see log sheet no.
Feeder is in “Maintenance Mode” □
Check appearance on HMI Display □
Check control blocking □
Check suppression of data transmission □

2.2.19.8 Import and export of archived process data

The backup/ archiving function will be checked under this chapter. Data, which was outsourced as
backup files will be imported into the runtime and displayed in the event list in conjunction with the
filter function. During import mode no changes of any other archive type or date is possible. The
“Archive” button starts blinking when an import succeeded. Afterwards the imported messages can be
saved into a readable format (as *.csv or *.txt). The export button function will remove the backup
database from the eventlist and the “Archive” button stops blinking.

Checked Comments see log sheet no.

Import from archive □
Export data to readable format to Excel □
(*.csv or *.txt)
Export to archive □

2.2.20 Additional Tests

In this chapter the remote access to bay control unit and protection relays will be checked. In addition
some protection tests will be simulated for checking information recording in SAS-system.

Checked Comments see log sheet no.

Remote access to IED devices via DR PC: □
- Password security
- Access/Load function with ability to □
change relay settings □
- Download of fault records
- Automatic download of DR (Built-in & Stand- □
alone) fault record with necessary S/w □
- Evaluation of Fault records with evaluation S/w
- Connection to 3rd party relays □
Remote access to BCUs and via DR PC: □
- Password security
- Access/Load function with ability to □
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 34
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

change relay settings □

Information recording in SAS-system □
- Reset of trip lockout relay
- Autoreclosing ON/OFF selection □
- Reporting of fault location
- Hardcopy print (to paper and file) □

2.2.21 Remote Desktop

The remote desktop function is a feature of Windows. It is shown as an icon on the desktop of all PCs
of this station. Press this button and a window will appear. Choose the desired PC by selecting its IP
address; the remote desktop function opens the desktop of the desired PC. It is mainly used for
configuring the station controllers and HMI servers from the Engineering PC.

Remote desktop Checked Comments see log sheet no.

Remote desktop functionality □

2.2.22 Time synchronization

The time synchronization is checked under this chapter. The antenna of the GPS clock is disconnected.
An alarm should be generated. Then the times of the devices is changed by hand for a few minutes
only. Connect the antenna again. The devices have to synchronize again by themselves after some
minutes and the alarm has to disappear. The time synchronization test shall be performed by making
GPS as the master clock for synchronizing all IED’s present on ring network.
Procedure
1. Disconnect the GPS Receiver Antenna. Set the GPS Receiver to send Local Time.
2. Confirm that the External Time Display Unit displays this local time.
3. Confirm that IEDs Operator Workstations and Substation Gateway Times match this local time.
This confirms that the SNTP packets are broadcasted by the GPS receiver.
4. Confirm that GPS Receiver unsynchronized alarm is received in the workstations.
5. Power off the GPS receiver.
6. Verify that all IEDs are synchronized with any of the IED/OWS designated as redundant Time
server.
7. Power on the GPS receiver.
8. Connect the GPS receiver Antenna. Verify that the GPS receiver is locked with satellite and GPS
is updated to satellite time.
9. Confirm that the External Time Display Unit, The IEDs, Operator Workstations and the
Substation Gateway are updated to the correct time of GPS.

Time synchronization Checked Comments see log sheet no.

OWS-1 & Server-1 □
OWS-2 & Server-2 □
DR PC □
Auxiliary System □
Time synchronization of connected IEDs □
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 35
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

Bay Control Unit □

Event list printer/ Hardcopy/ Logbook printer □
2.3.1 Validation of OWS Memory and Disk Utilization
Purpose
To verify that the OWS have Memory and Disk Usage and allocation those are within the specification
requirements.
Setup
Ensure that the Servers are running and functioning properly.
Validation of OWS Memory and Disk Utilization
Computer Physical Memory Hard Drive Free Space PASS/FAIL

SERVER-1

SERVER-2

OWS-1

OWS-2

DR/EWS PC

GATEWAY-1

GATEWAY-2

2.3 EWS TEST

2.4.1 Setting and Configuring of BCUs
Purpose
To verify that the BCU database is configured in necessary software and download is possible. Settings
of BCU like Change of IP Address etc are possible.
Setup
1. Ensure that DR PC is running.
Procedure
1. Change some parameters in S/W for the BCU to test. Compile the Database for which parameters
have been changed.
2. Run S/w on the DR and select the compiled Database. Connect the BCU for which the parameters
have been changed.
3. Upload the database.
4. Verify that the download is successful and check the DB version on the BCU.
2.4.2 Network Monitoring System
Purpose
To verify that the Network Monitoring System (NMS) application software can perform the following
functions on the LAN devices:

Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 36
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

• Configuration Management
• Fault Management
• Performance Monitoring
Note that the Network Management System is based on Simple Network Monitoring Protocol (SNMP).
Some background on this protocol is needed to understand how the application software works.
Procedure
1. Verify that NMS software used monitors LAN devices statistics and present these using displays.
2. Verify that it maintains connectivity and device status, issues alarms on errors conditions. This can
be verified in the OI client screens.
3. Verify that it has tools for maintenance of addressed and links.

2.5 Auto Reclose Test

2.5.1 Test for Auto-Reclose Successful case:-
1. Select the Circuit Breakers of Main & Tie on which Auto reclose has to be tested.
2. Ensure that the Circuit Breakers are in closed condition and Auto-recloser is in ON state and all
interlock conditions for closing the breaker are satisfied.
3. Simulate 1-Phase trip, ensure that the corresponding phase of the Main & tie breakers open.
4. Ensure that the Main Circuit Breaker Auto recloses first with predefined dead time (1sec) and Tie
breaker auto recloses once the main breaker reclose cycle is completed. (2sec)
5. Ensure that once Auto-recloser is successful for main, the respective reclaim timer starts and Auto-
reclose State goes back to Normal once the reclaim time is over and the same is applicable for Tie
bay.
6. Put Auto-recloser of main CB in off position. Repeat steps 1 to 3. In this case ensure that Main CB
does not go for Auto-reclose and tie CB Auto-reclosers without priority.(1 sec)
7. Check that Auto-reclose does not take place for CB which are already in open condition. Check this
for both main & tie CB.
8. Check that A/R does not take place for CB having A/R lockout condition ( SF6 gas pressure/Oil
pressure/spring discharge). The healthy CB associated with the feeder shall A/R successfully.

2.5.2 Test for Auto-Reclose Failure case:-

1. Repeat steps 1to 5 of successful case, Once the reclaim time starts, simulate another 1-Phase trip.
2. Ensure that the Auto-reclose enters Locking State and a 3-Ph tripping is issued to the both Main
and Tie Breaker and all the 3-phases of the breaker open.
3. Repeat steps 1to 3 of successful case, Once the Auto-recloser cycle starts, before the dead time is
over and close command is issued to the Main and Tie Breaker, Simulate another 1-ph trip. In this
case also Auto-recloser enters Locking State and a 3-Ph tripping is issued to the both Main and Tie
Breaker and all the 3-phases of the breaker open.
4. Repeat steps 1to 3 of successful case, Once the Auto-recloser cycle starts, before the dead time is
over and close command is issued to the breaker, simulate the AR blocking signal, Ensure that the
Auto-reclose does not take place and Auto-recloser goes back to its Initial state.
2.6 Setting of Protection Relays

2.6.1 Setting of Main-1 Protection Relays

Purpose
To verify that the Setting of Main-1 Protection Relays can be changed via the Rear Port of Protection
Relays.
Setup
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 37
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

1. Ensure that DR PC is running.

2. Relay Configuration software is properly installed on DR PC.
Procedure
4. Verify that Protection relay rear Port for which test to be performed are connected via rear port.
5. Run Relay Software on DR PC and open the Protection relay file. Verify that the connection is
successful.
6. Extract the settings from the connected Protection Relay. After extracting, select the parameter
needs to be modified. Upload the changes to the connected relay.
7. Verify that the parameter is changed again by opening the setting file of Protection Relay from DR
PC.

2.6.2 Setting of Main-2 Protection Relays

Purpose
To verify that the Setting of Main-2 Protection Relay can be changed via the Ethernet Port of
Protection Relays.
Setup
1. Ensure that DR PC is running.
2. Relay software is properly installed on DR PC.
Procedure
1. Connect the Ethernet cable between Ethernet switch and Protection relay for which test to be
performed.
2. Run software and connect with the Protection relay. Verify that the connection is successful.
3. Extract the settings from the connected Protection Relay. After extracting, select the parameter
needs to be modified. Upload the changes to the connected relay.
4. Verify that the parameter is changed by using the front display of Protection Relay.

2.7 DR Configuration : Check DR is configured as per TS as per following

i. Analog triggering level
ii. Signal name and order
iii. Pre-& Post fault time (Pre-fault time: min 500ms)
iv. Triggering Channel
v. Re-trigger option etc.

2.8 Disturbance File Retrieval

Purpose
To verify that the automatic disturbance file is uploaded to DR PC when the disturbance is created.
Setup
1. Ensure that DR PC is running.
2. System Software should be running on the DR PC.
Procedure
1. Create the Disturbance on Main-1 &2, Verify that the disturbance has been created in the relay.
2. Observe that the Disturbance File (.cfg/.dat etc.) is automatically created in the DR PC.
3. Open the Disturbance file with DR software.

Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 38
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

Testing of Typical Relays & BCU (One number of each type and function) is to be verified in Factory
Acceptance Test.

3.2 BCU Input/output Data Retrieval

The following are the procedures in the BCU I/O Data retrieval. The individual BCU Test result logs are
to be filled up in the following sections.

Digital Input Retrieval

Purpose
To verify that the change of state of Digital Input points are updated in the BCU MMI, the Operator
Workstations and Master Station Simulator.
To verify that the Digital Inputs are mapped correctly as per the approved drawing.
Setup/Program
1. Connect the test jig to the BCU under test.
2. Go to the BCU MMI Digital Inputs Display screen.
3. On the OWS-1 go to relevant HMI screen.
4. On the OWS-2 go to Alarm/Event list.
Procedure
1. Select a Digital Input point on the BCU under test.
2. Change its state from ‘OFF’ to ‘ON’ (single points) or from ‘OPEN’ to ‘CLOSED’ (double points) by
toggling the corresponding jig.
3. Verify that the state of this point in the BCU MMI and HMI is changed correctly.
4. Verify that the state of this point in the OWS-2 event list screen is changed correctly.
5. For points configured with alarm, verify that alarms are displayed in the Alarm Screen of the OWS-
2 with correct time stamp.
6. For points considered in the IEC 60870-101 List, verify that the state of this point in the Master
Station Simulator is changed correctly with correct time stamp.
7. Change its state from ‘ON’ to ‘OFF’ (single points) or from ‘CLOSED’ to ‘OPEN’ (double points) by
toggling the corresponding jig.
8. Repeats step 3 to 6
9. Repeat 1 to 8 for all Digital Input points to be tested on this BCU.
10. Repeat steps 1 to 9 for all BCU’s.

Digital Output
Purpose
To verify that digital output operations are successfully executed.
To verify that the Digital Output points are mapped correctly according to the approved drawings &
Data List.
Setup/Program
1. Connect the test jig to the BCU under test.
2. Go to the BCU MMI Digital Outputs Display screen.
3. On the OWS-1 go to relevant HMI screen.
4. On the OWS-2 go to Alarm/Event list.
Procedure
1. Choose a BCU to test. From the HMI workstation initiate digital output requests.
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 39
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

2. Verify that the corresponding output activated.

Software Interlock Logic

Purpose
To verify that software interlock logic for CBs and Isolators are operational based on simulated
conditions.
Note: Since not all interlock conditions can be tested during FAT, other interlock inputs shall be
simulated by shorting auxiliary contacts at the terminal blocks of the panels.
Setup
1. Set up the test jig to simulate software interlock positive and negative test conditions.
2. Set up shorting links to simulate other auxiliary contacts.
3. Refer approved drawings.
Procedure
1. Select a BCU to test.
2. Refer to the interlock conditions for testing. First set up a negative condition. Attempt to operate
controls related to the interlock logic being tested. Verify that the interlock is successful.
3. Set up for a positive test condition. Verify that interlock is successful when control operation is
performed on related to the interlock logic being tested.

CB/ CB/Isolators CB/Isolators CB/Isolator Checked

Interlock Interlock
Isolators Condition
Negative Test Positive Test
Result Result

Interlock involving GOOSE signal shall also be checked. It shall be ensured that absence of required GOOSE signal does not
enable any interlocking condition.
Spare switching arrangement for Single phase reactor and transformer banks shall be verified by simulation and software
interlocks to be verified.

3.3 Substation Controller Device Reporting

Purpose
To verify that the Substation Controller (Server/Client) is successfully communicating with the bay level
devices using IEC 61850 protocol.
Setup
1. Ensure that the Server/Clients are running.
2. Go to the System Architecture Screen on Client.
Procedure
1. On the System Architecture screen, verify that the bay device status is Normal.

Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 40
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

2. Go to a remote device and disconnect the LAN cable, verify that the System Architecture screen
shows the bay device is Failed.
3. Connect the LAN cable. Monitor the communication between Server and remote device and verify
that the IEC 61850 packets between the two TCP/IP addresses are passing through.
4. Verify that the System Architecture Screen shows that the device is Normal.
5. Repeat the above procedures for other devices.

3.3.1 IEC 60870-5-101 Data Retrieval

Purpose
To perform preliminary verification that the IEC 60870-5-101 Communication Ports are functional.
Setup/Program
• Ensure that the test equipment is in FAT room.
• Use a Protocol Analyzer Test set to simulate an IEC 60870-5-101 Master Station polling with
General Interrogation and data changes. Use the Protocol Analyzer Test set to Monitor IEC 60870-
5-101 datagram on the redundant serial communications links.
Procedure
1. Verify that communication is established with the simulator Protocol Analyzer Test set.
2. Verify that the simulator is sending request on the primary channel and that the SAS Gateways is
responding on both the primary (Main) and the secondary (Standby) channels.
3. Disconnect the simulator from the primary channel and connect it to the secondary channel; verify
that the SAS Gateway will respond on both channels to requests received on the secondary
channel.
4. Verify that data present at HMI should be same at Protocol Analyzer Test also.
5. Verify that all the configured required data points are sent by the gateway to the simulator.

3.3.2 Master Digital Inputs Retrieval

Purpose
To verify that the Substation Gateway is polled for Digital Input data correctly by the Master Simulator.
Procedure
1. Inject digital input changes to single point and double point inputs.
2. Verify change of the state in the Gateway Machine and Protocol Analyzer.

3.4 Master Analog Inputs Retrieval

Purpose
To verify that substation gateway is polled for Analog Input data correctly by the Master Simulator.
Procedure
Inject Analog Inputs and verify that the Analog data are correctly received by the Master Simulator.

3.5 Statement of System Acceptance

Upon satisfactory completion of all applicable tests specified in this document and the proper
disposition of all properly documented and witnessed discrepancies resulting from tests specified in
the procedure, the system, tested and witnessed by the POWERGRID is functionally accepted by
POWERGRID.

3.6 Duration of Factory Acceptance Test

The duration of Factory Acceptance Testing will be mutually agreed depending upon the size of the
substation (normally one to two weeks).
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 41
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc
 Doc. No. : PG/CC/AM/STD/SAS/FAT Rev0

4. Comments
Any comments should be added in “log sheets”; a pattern is attached on next page.

SAS-FAT LOG SHEET

No. Reference Author Date

Description

5. Glossary:
BCU: Bay Control Unit
DR: Disturbance Recorder
EWS: Engineering Work Station
FAT: Factory Acceptance Test
FPT: Functional Performance Test
FST: Factory Simulation Test
GTW: Gateway
GPS : Global Positioning System
IED: Intelligent Electronic Device
NMS: Network Management (Monitoring) System
OWS: Operator Workstation
RCC: Remote Control Centre
RSCC: Regional System Co-ordination Centre
SAS: Sub-station Automation System
SAT: Site Acceptance Test
SCADA: System Control & Monitoring System
Verify by:
POWERGRID Representative Manufacturer Representative
Signature : Signature :
Name : Name :
Date : Date :
P a g e 42
Factory Simulation Test (FST) /Factory Acceptance Test (FAT) Procedure Rev0.doc