Ref No. HFCL/GEC/GMRC-Surat/Tel-02/23/160 Date: 05.12.

2023

To,
The Project Director
GEC to GMRCL For Surat metro,
Consortium of SYSTRA AECOM-EGIS-CEG(Sub-Con)
SUDA Bhawan,Vesu
Surat- 395007,

Programme reference: Design, Manufacture, Supply, Installation, Testing, and

Commissioning of Telecommunication System for Surat Metro Rail Project Phase 1, Contract
/ Bid no. GMRC/S&T/TEL–02

Subject: Submission of FAT procedure of ACS system

Dear Sir,

We hereby submit for review by the Employer/ER/Engineer the documents or articles listed
below:

Sl.No Ref. Doc Name Doc. No

Telecommunication FAT procedure of ACS SUR-01/TEL-

1
works. system 02/TCP/CRS/010 (Rev-00)

I confirm that the material/ document submitted is in full compliance with the Contract.

Thanking you & assuring you of our best services.

Yours faithfully,
HFCL Limited
Puneet Digitally signed by
Puneet Saxena

Saxena Date: 2023.12.05

13:18:05 +05'30'
Authorized Representative
Mr. Puneet Saxena
Railways – Business Head

Encl: FAT procedure of ACS system

Cc: GMRCL GEC

1. CGM, Surat Metro (GMRC/S&T/Telecom) 1. Dy.Project Director System
 SURAT METRO
TEL-02
SURAT METRO- CORRIDOR-1 & 2

FACTORY ACCEPTANCE TEST DOCUMENT - ACCESS

CONTROL SYSTEM

Document No. –SUR-01/TEL-02/TCP/ACS/010 (Rev 00)

 Approval Prepared By Reviewed By Approved By

Name Saurabh Kumar Saxena Partha Sarathi Pal Jagmohan Vashisht

Function System Designer Design Manager Project Manager

Date 30-11-2023 02-12-2023 05-12-2023

Saurabh Digitally signed by

Partha Digitally signed by
Jagmoha Digitally signed by

Signature Saxena
Saurabh Saxena
Date: 2023.12.05
Sarathi Pal
Partha Sarathi Pal
Date: 2023.12.05
Jagmohan Vashisht

n Vashisht 13:25:44 +05'30'

Date: 2023.12.05
13:08:38 +05'30' 13:17:00 +05'30'

Revision History

Revision Number Revision Date Revision Description

00 05-12-2023 Initial Submission

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 2 of 43

 Distribution list

S. No Distribution in GMRC Distribution in GEC

Mr. Arvind Singh Rajput, GM- Mr. Sunil Jagdev, Project Director
1 Telecom/AFC, Surat Metro (GMRCL)

Mr. Rajesh Kumar Mehta, Dy. Project

2 Director-Systems

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 3 of 43

 Contents
1 Introduction 6

1.1 Project Introduction ..........................................................................................................6

1.2 Project Overview ..............................................................................................................6
1.2.1 Corridor – 1: SARTHANA TO DREAM CITY .............................................................7
1.2.2 Corridor – 2: BHESAN TO SAROLI ...........................................................................8
1.2.3 Chainage ..................................................................................................................9
1.3 Purpose..........................................................................................................................10
1.4 Scope .............................................................................................................................10
1.5 Abbreviations .................................................................................................................11
2 ACS Factory Acceptance Test Proposal 14

2.1 Factory Acceptance Test (FAT) Duration .......................................................................14

2.2 FAT Set Up Objective .....................................................................................................14
3 FAT Test Setup 15

3.1 List of ACS Equipment’s (IDCUBE Identification Systems (P) Ltd.) Used for FAT ..........15
3.2 List of Equipment (Other Than ACS OEM) Used for FAT ...............................................16
3.3 List of Tool and Test Equipment .....................................................................................16
4 General Conditions 17

5 FAT Test Procedures 18

5.1 ACS Test Procedures.....................................................................................................19

5.1.1 FAT Setup Verification ............................................................................................19
5.1.2 Hawk Eye Test (ACS) .............................................................................................20
5.1.3 Access Control Configuration Test ..........................................................................22
5.1.4 Smart Card Reader Configuration ...........................................................................23
5.1.5 Biometric Card Reader Configuration Test ..............................................................24
5.1.6 Access Card Configuration Test ..............................................................................25
5.1.7 Entry of Authorized Personnel at any Rooms ..........................................................26
5.1.8 Suspending Access Cards ......................................................................................27
5.1.9 Door Open / Closed Indications...............................................................................28

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 4 of 43

 5.1.10 Fingerprint Enrolment Test ................................................................................29
5.1.11 Report Generation .............................................................................................30
5.1.12 Remote Opening and Locking Door ...................................................................31
5.1.13 View Live Events ...............................................................................................32
5.1.14 Viewing of Controller/Interface/Reader Online/Offline Status .............................33
5.1.15 ACS NMS ..........................................................................................................34
5.1.16 Door Control Test ..............................................................................................35
5.1.17 EM locks functioning in case of Power Supply Failure .......................................36
5.1.18 Override Key Test..............................................................................................37
5.1.19 Exit Switch Test .................................................................................................38
5.1.20 Card Reader Range with MIFARE .....................................................................39
5.1.21 Door Opening in case of Fire Alarm Input ..........................................................40
5.1.22 Device Online/Offline Status ..............................................................................41
5.1.23 Redundancy of ACS Central Servers.................................................................42
6 Authorized Representative Signatures 43

List of Tables
Table 1: Project Chainage ............................................................................................................ 9
Table 2 : Abbreviations ............................................................................................................... 11
Table 3: List of ACS Equipment for FAT test .............................................................................. 15
Table 4: List of ACS Equipment’s (Other than ACS OEM) for FAT test ....................................... 16
Table 5: List of Tool & Test Equipment ....................................................................................... 16

List of Figures

Figure 1: Surat Metro Phase I Route Map..................................................................................... 6

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 5 of 43

 1 INTRODUCTION

1.1 Project Introduction

For efficient Metro railway management and operation, it is essential to have a well-organized
Telecommunication network covering strategic locations like OCC, BCC, stations, depots and it is
equally essential to have reliable links between the strategic locations and moving trains or
working staff along the Metro railway track/Tunnel.
The Telecommunications System comprises of Subsystems including Fiber Optic Transmission
system (FOTS) and OAIT, Telephone system (IPABX & direct lines), Closed Circuit Television
system (CCTV), Passenger Information Display System (PIDS), Public Address system (PAS),
Master Clock System (MCS), Radio System (TETRA) and Access Control System (ACS),
Centralised Digital Recording System (CDRS) and Cyber Security System.

1.2 Project Overview

Figure 1: Surat Metro Phase I Route Map

The Telecommunications System covers the following two sections:
• Corridor-I: SARTHANA to DREAM CITY (Length – 21.61 Km)

• Corridor-2: BHESAN to SAROLI (Length: 18.74 km)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 6 of 43

 • Operation Control Centres (OCC) will be located at Dream City Depot and Backup
Control Centres (BCC) will be located at Bhesan Depot.

1.2.1 Corridor – 1: SARTHANA TO DREAM CITY

• Total Length – 21.61 Km

• Stations – 14 (Elevated)

• Stations – 6 (Underground)

• Receiving Sub Station (RSS) – 2 Nos.

• OCC – 1 No. (Dream City Depot)

• Depot – 1 No. (Dream City)

Section – CS1: Dream City to Kadarsha Ni Nal including Dream City Depot
1. Dream City Depot including OCC

2. Dream City

3. Convention Center

4. Bhimrad

5. Woman ITI

6. VIP Road

7. Althan Gam

8. Althan Tenament

9. Rupali Canal

10. Majura Gate

11. Kadarsha Ni Nal

Section – CS2:
1. Chowk Bazar

2. Maskati Hospital

3. Surat Railway Station

4. Central Warehouse

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 7 of 43

 5. Labheshwar Chowk

6. Kapodra

Section – CS3:
1. Shri Swaminarayan Mandir Kalakunj

2. Varachha Chopati Garden

3. Nature Park

4. Sarthana

1.2.2 Corridor – 2: BHESAN TO SAROLI

• Total Length – 18.74 Km

• Stations – 18 (Elevated)

• Receiving Sub Station (RSS) – 2 Nos.

• BCC – 1 No. (Bhesan Depot)

• Depot – 1 No. (Bhesan Depot)

Section – CS4:
1. Bhesan Depot including BCC

2. Bhesan

3. Botanical Garden

4. Ugat Vaarigruh

5. Palanpur Road

6. LP Savani school

7. Performing art Center

8. Adajan Gam

9. Aquerium

10. Badri Narayan Temple

11. Athwa Chopati

12. Majura Gate

Section – CS5:

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 8 of 43

 1. Udhna Darwaja

2. Kamela Darwaja

3. Anjana farm

4. Model Town

5. Magob

6. Bharat Cancer Hospital

7. Saroli

1.2.3 Chainage

Table 1: Project Chainage

Sr. Corridor-I: SARTHANA TO DREAM Corridor-2: BHESAN TO SAROLI

No. CITY (Length: 21.61 km) (Length: 18.74 km)

Chainage Chainage
Station Name Station Name
(m) (m)

1 Sarthana 0 Bhesan 0

2 Nature Park 1238.1 Botanical Garden 950.6

3 Varachha Chopati Garden 2108.5 Ugat Vaarigruh 1617.5

Shri Swaminarayan
4 3196.6 Palanpur Road 2738.9
Mandir Kalakunj

5 Kapodra 4237 L.P. Savani school 3831.6

6 Labheshwar Chowk 5506.6 Performing Art Centre 4421.8

7 Central Warehouse 6668.9 Adajan Gam 5155

8 Surat Railway Station 7255.6 Aquerium 5770.1

9 Maskati Hospital 8487 Badri Narayan Temple 6891.5

10 Chowk Bazar 10289.8 Athwa Chopati 7863.5

11 Kadarsha Ni Nal 11721.7 Majura Gate 9019.2

12 Majura Gate 12313.8 Udhna Darwaja 10646.2

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 9 of 43

 Sr. Corridor-I: SARTHANA TO DREAM Corridor-2: BHESAN TO SAROLI
No. CITY (Length: 21.61 km) (Length: 18.74 km)

Chainage Chainage
Station Name Station Name
(m) (m)

13 Rupali Canal 13611.5 Kamela Darwaja 11247.2

14 AlthanTenament 14696.2 Anjana Farm 12593.9

15 Althan Gam 15843.5 Model Town 13636.3

16 VIP Road 16699.1 Magob 14763.1

17 Women ITI 17808.4 Bharat Cancer Hospital 15899.4

18 Bhimrad 18659.5 Saroli 17341.8

19 Convention Centre 19829.4

20 Dream City 20710.3

DEAD END 21160.3 DEAD END 17791.9

Total 21160.3 Total 18741.53

1.3 Purpose
The purpose of this document is to provide Factory Acceptance Test (FAT) procedures that will
be conducted to verify and validate the testing of the Access Control System during the Factory
Testing phase for Surat Metro Rail Project Phase – I.

1.4 Scope
The scope of this document is to explain Factory Test Procedures of ACS System and other
connected components in following sequence:
• Abbreviations
• Manufacturer Details
• Factory Acceptance Test proposal
• Intended Audience
• FAT Test setup
• FAT Test procedures

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 10 of 43

 1.5 Abbreviations
Table 2 : Abbreviations

Abbreviation Meaning / Full Form

AC Alternating Current

ACS Access Control System

AFC Automatic Fare Collection

BCC Backup Control Center

BOQ Bill Of Quantity

CCTV Closed Circuit Television

CDRS Centralised Digital Recording System

CER Communication Equipment Room in OCC & BCC building or any other
suitable location.

CPU Central Processing Unit

CSS Communication System Supervisor

DAS Distributed Antenna System

DCC Depot Control Centre

DTER Depot Telecom Equipment Room

DVD Digital Video Disk

DVI Digital Visual Interface

E&M Electrical & Mechanical

EMI Electro-Magnetic Interference

FAT Factory Acceptance Test

FOTS Fibre Optic Transmission System

GE Gigabit Ethernet

GHz Gigahertz

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 11 of 43

 Abbreviation Meaning / Full Form

GoS Grade of Service

GPS Global Positioning System

GUI Graphical User Interface

H.264 Video Compression Format

HDD Hard Disk Drive

HMI Human Machine Interface

HTTP HyperText Transfer Protocol

IEC International Electro-Technical Commission

IEEE Institute of Electrical and Electronics Engineers

ITU-T International Telecommunication Union Telecommunication Standardization

Sector

LAN Local Area Network

MMI Man Machine Interface

MPEG-4 Moving Picture Experts Group (Audio/Video Data Compression)

MTBF Mean Time Between Failures

MTTR Mean Time to Repair

NMS Network Management System

NTP Network Time Protocol

OCC Operations Control Center

ODF Optical Distribution Frame

PA Public Address

PAS Public Address System

PIDS Passenger Information Display System

PoE Power-Over-Ethernet

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 12 of 43

 Abbreviation Meaning / Full Form

PPIO Planning and Investigation Office

PS Particular Specification

QoS Quality of Service

RSS Receiving Substation

SCR Station Control Room

TER Telecom Equipment Room

TETRA Terrestrial Trunked Radio

TSS Traction Substation

UPS Uninterruptible Power Supply

USB Universal Serial Bus

VLAN Virtual Local Area Network

WAN Wide Area Network

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 13 of 43

 2 ACS FACTORY ACCEPTANCE TEST PROPOSAL
The ACS equipment are manufactured & supplied by IDCUBE Identification Systems (P) Ltd. The
legal references of the factory, manufacturing of the equipment & location of FAT:
IDCUBE FZE,
Techno Hub 1 – Office G 042
Dubai Silicon Oasis
Dubai, UAE

IDCUBE’s Quality Assurance System is certified in accordance with ISO 9001:2015 Standards.
The certificate for the same will be provided during FAT execution.

2.1 Factory Acceptance Test (FAT) Duration

Factory Acceptance Test (FAT) duration will be of 01 day(s).

2.2 FAT Set Up Objective

The objective of this document is to provide an overview of Testing Methodology to carry out test
on project requirements. It describes the test schedule, equipment, test procedures, acceptance
criteria in accordance with our proposed Final Detailed Design. The FAT will be conducted in a
simulated environment (with OCC and BCC Servers) along with ACS equipment.

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 14 of 43

 3 FAT TEST SETUP
3.1 List of ACS Equipment’s (IDCUBE Identification Systems (P) Ltd.) Used for
FAT
The following equipment will be configured for Factory Acceptance Test for ACS system. The
basic key system functions will be tested to verify that the proposed solution is fully functional.
The equipment’s involved in the tests are mentioned in the below table:

Table 3: List of ACS Equipment for FAT test

S. Quantity
Description Model Number Serial Number
No. (Nos.)

ACS Main Controller

1 (ICMLP1502) 1
with Enclosure

2 ACS Slave Controller (ICMMR52) 1

3 Smart Card Reader (AXS+) 1

Biometric Fingerprint
4 Readers for T&A (Sigma Lite+) 1
purpose

Electro Magnetic Lock

5 (AAIEMAGA4SSHSAL) 1
for Single Door (600 lbs)

Electro Magnetic Lock

6 for Single Door (600 (AAEMAGA4SSHSALW) 1
lbs)- weatherproof

Electro Magnetic Lock

7 for Double Door (AAIEMAGA4DSHSAL) 1
(600+600 lbs)

8 Push Button KT-300-SD-SPDT-EM 1

Emergency Break Glass

9 KT-MCP-100 1
for the exit Side of Door

Override Key Switch at

10 KT-300 1
Entry Side of Door

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 15 of 43

 3.2 List of Equipment (Other Than ACS OEM) Used for FAT
Table 4: List of ACS Equipment’s (Other than ACS OEM) for FAT test

S. No. Description Model Number Quantity (Nos.)

11 ID Card Printer ZC300 1

12 ACS Central Server at OCC and 1

Central Server
BCC

13 Workstation, Keyboard & Mouse Workstation 1

14 NMS Workstation with 1

NMS Workstation
Application

15 KVM Extender Set (Tx & Rx) KVM Tx & Rx 1

16 ACS Maintenance Laptop Laptop 1

17 Access 360 Base License Access 360 Application 1

Application

18 Access 360 Reader License Access 360 reader 1

Module

38 ACS Smartcards Smartcards 1

3.3 List of Tool and Test Equipment

Table 5: List of Tool & Test Equipment

S. No. Description Model Number Quantity (Nos.)

1 LAN cables Any reputed Make / Model Approx(10)

2 Multimeter Any reputed Make / Model 1

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 16 of 43

 4 GENERAL CONDITIONS
During the Factory Acceptance Test the following procedure will be executed:
• Representatives of ACS OEM (IDCUBE) will execute the test cases described in this
document.
• Prior to the commencement of each test, the demonstrator will explain to the Witness:
o The number of the test.
o What the test will demonstrate.
o How the test will be carried out.
o What result is expected?
• All test equipment shall be in good working order and within its calibration period, where
equipment requires calibration; the calibration date will be recorded.
• If a test case is completed successfully, then this is indicated in the check box with a
check mark ‘’’ by a representative of witness.
• If a test case is not completed successfully, then this is indicated in the check box with a
check mark ‘X’.
• After finishing the Factory Acceptance Test, a Factory Acceptance Test Certificate for
ACS (IDCUBE) will be generated and under-signed.
• The conclusion, being one of the following alternatives:
a) Factory Test Accepted.
b) Factory Test Accepted with remarks.
c) Factory Test not accepted indicating the reasons.

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 17 of 43

 5 FAT TEST PROCEDURES
The various Factory Acceptance test procedures to be conducted under ACS system are listed
below:
• FAT Setup Verification / Physical Verification
• Hawk eye test (ACS)
• Access control configuration test
• Smart Card Reader configuration test
• Biometric card reader configuration test
• Access Card configuration test
• Entry of authorized personnel at any rooms
• Suspending Access Cards
• Door-open / closed indication of door
• Fingerprint Enrolment Test
• Report Generation
• Remote open and locking Smart Card reader door
• View live events
• Viewing of Controller/interface/reader online/offline status
• ACS NMS
• Door Control Test
• EM Locks Functioning in case of power supply failure.
• Override key Test
• Exit Switch Test
• Card reader range with MIFARE.
• Door opening in case of fire alarm input.
• Device online/offline status
• Redundancy of ACS Central Servers (Simulated Environment)

The ACS Test procedures listed above are given in detail in the following section.

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 18 of 43

 5.1 ACS Test Procedures

5.1.1 FAT Setup Verification

Test Procedure
FAT Setup Verification
Name:
Test Case: FAT Setup Verification
1.1.2: Functions of Access Control System (ACS) shall be access
management and alarm management. The system shall include, but not
Clause limited to, the Main Controllers, detection sensors, electromagnetic locks
Reference: (EMLs), control switches (Emergency & Key), access cards, access card
readers, interface controllers, central ACS servers, display HMI, interface
with common printers, card issue workstation cum NMS etc.
Start Date End Date
Procedures Description:
 Check all the devices are present or not.
 Check all the devices are powered up or not.
 Check GUI is working properly or not.
Expected Result:
 All devices are present and powered on.
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 19 of 43

 5.1.2 Hawk Eye Test (ACS)

Test Procedure
HAWK EYE TEST
Name:
The Contractor shall design the ACS Graphical User Interface (GUI) for the
ACS workstations using multiple screens showing ACS equipment locations
on representations of architectural station layouts and depot area layouts.
The purpose of the GUI is to provide the workstation operator with
a. Location of each access control entry
Test Case: b. Indication of each access control status - in service/disabled/malfunction
c. Selection of each access control entry point by pointing device for
additional information
d. Selection of other ACS screens
e. Menu of selectable access control data for log printing and selection of
printer
5.9.7.1: Interactive GUI map display for operator interaction showing plan
Clause and elevation layouts views of the site, which shall identify each building,
Reference: room, corridor together with relevant doors, access control devices, device
status and intruder detection at depot periphery
Start Date End Date
Procedures Description:
1. Open ACS360 application and go to monitor > Events.
2. Go to Hawkeye tab and we can see various ACS/IDS devices layer wise and their
online/offline/fault status.
3. ACS entry points can be mouse hovered for additional information.
4. ACS360 is a menu driven web based application providing seamless navigation to other
ACS screens
5. Go to event history and the event log data can be exported and printed.
Expected Result:
 ACS Graphical User Interface (GUI) layout.
PASS FAIL

Comments:

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 20 of 43

 Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 21 of 43

 5.1.3 Access Control Configuration Test

Test Procedure
Access control configuration test
Name:
Test Case: To configure Access Control Controllers
5.3.1 (d): The access card reader shall have suitable internal memory for
Clause
data storage for fast access and operation of system in fall back mode.
Reference:
Storage at controller level is also acceptable.
Start Date End Date
Procedures Description:
1. Check the Server & Workstation LAN connectivity.
2. Configure the IP in the controller webpage & Connect the controller with LAN.
2. Open Security View Application & Scan the available controller.
5. Provide the name of the controller.
6. Check the controller is added in system database & see online status in Access360 web
interface.
7. Check the Internal parameters like memory of Controller
Expected Result:
 Controller should come online.
 Last message received should get updated.
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 22 of 43

 5.1.4 Smart Card Reader Configuration

Test Procedure
Smart Card Reader configuration
Name:
Test Case: Configuration of Smart Card Reader
1.2.2: The system in-charge of the management of staff identity cards shall
Clause be able to support all necessary features as for example: to create new
Reference: cards, store, retrieve, photograph and print out cardholder details, including
programming and cancelling details of people, cards and access rights
Start Date End Date
Procedures Description:
1. Open the Application GUI and Configure the Smart Card Reader with name.
2. Check the reader has been added in system application successfully.
3. Show the card reader to reader and check the status of the reader in system.
4. If user is valid access will be granted and lock should be unlocked within 10seconds.
5. From the exit side, swipe a card or press the exit button and door shall be unlocked.
Expected Result:
 Reader should show as connected in Reader Status
 Reader should read the card and beep/LED change should happen.
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 23 of 43

 5.1.5 Biometric Card Reader Configuration Test

Test Procedure
Biometric card reader configuration test
Name:
Test Case: Configuration of Biometric card reader
1.2.2: The system in-charge of the management of staff identity cards shall
Clause be able to support all necessary features as for example: to create new
Reference: cards, store, retrieve, photograph and print out cardholder details, including
programming and cancelling details of people, cards and access rights
Start Date End Date
Procedures Description:
1. Configure the IP of Biometric reader.
2. Show the card/finger to reader and check the status of the reader in system with LED
indication.
3. On getting access user will see ‘Valid’ flashed on biometric reader screen and invalid in case
of vice versa.
Expected Result:
 Reader should show as connected in Reader Status
 Reader should read the card/finger and beep/LED change should happen showing
access valid/invalid.
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 24 of 43

 5.1.6 Access Card Configuration Test

Test Procedure
Access Card Configuration test
Name:
Test Case: Issuing staff access cards
Clause
1.1.11, 1.1.12.2, 1.2.2, 4.13,
Reference
Start Date End Date

Procedures Description:
1. Open the Application GUI and issue credential to an existing user.
2. Give access to the credential and check whether tasks are successful.
3. User will get access on swiping the card on reader if the tasks are successful.

Expected Result:
 User will get access on successful card addition.
 Photo will be printed on the same.
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 25 of 43

 5.1.7 Entry of Authorized Personnel at any Rooms

Test Procedure
Entry of authorized personnel at any rooms
Name:
Test Case: Test to restrict entry of authorized personnel at any rooms
Clause
1.1.11, 1.1.12.2, 5.2.2 (b), 5.2.2 (c)
Reference:
Start Date End Date
Procedures Description:
1. Configure the card in the system and assign to the user.
2. Allow the entry of card user.
3. Show the card to the reader. If access is granted, then it proves the authorization level for
that particular user & access card.
4. Restrict the same card & again try to get the access.
5. Access should be denied which proves authorization level.
6. Check the logs with IN/OUT time and access denied alarm in events.
Expected Result:
 User should get access on only that door where he has permission as per access group.
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 26 of 43

 5.1.8 Suspending Access Cards

Test Procedure
Suspending Access Cards
Name:
Test Case: Test to suspending access cards
1.2.2: The system in-charge of the management of staff identity cards shall
Clause be able to support all necessary features as for example: to create new
Reference: cards, store, retrieve, photograph and print out cardholder details, including
programming and cancelling details of people, cards and access rights.
Start Date End Date

Procedures Description:
1. Search the user with name or card number & Blacklist/Suspend the card for access.
2. Show the card to the reader.
3. Access should be denied to the blacklisted user.

Expected Result:
 Suspended user should not get access
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 27 of 43

 5.1.9 Door Open / Closed Indications

Test Procedure
Door-open / Door-closed indication
Name:
Test Case: Test to check door-open / closed indications
Clause 5.8. (vii): A forced entry shall be detected by the sensor and trigger alarm of
Reference: the Access Control system.
Start Date End Date

Procedures Description:
1.Check the status and simulate opening of door.
2.Check the notification must be appear door is open.
3.Operator can acknowledge the alarm and same can be viewed in event logs.

Expected Result:
 The user should get alarm on door opening of door.
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 28 of 43

 5.1.10 Fingerprint Enrolment Test

Test Procedure
Fingerprint Enrolment Test
Name:
Test Case: Enrolment of user with photo and thumb impression (fingerprint)
1.2.2: The system in-charge of the management of staff identity cards shall
Clause be able to support all necessary features as for example: to create new
Reference: cards, store, retrieve, photograph and print out cardholder details, including
programming and cancelling details of people, cards and access rights.
Start Date End Date
Procedures Description:
1.Open the web application.
2.Search the user and click on enrol.
3.Enroll the fingerprint when alerted and click on save.
4.Swipe the finger and it should give grant access subjected to permissions given.
Expected Result:
 The user should get access on successful enrollment.
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 29 of 43

 5.1.11 Report Generation

Test Procedure
Report Generation
Name:
Test Case: Test to produce reports
Clause
3.7: All alarms for events and faults shall be reported in real time.
Reference:
Start Date End Date

Procedures Description:
1. Login to web application and go to reports tab in menu
2. Go to access/attendance reports based on choice
3. Click on any report based on choice and click on view/csv/pdf as per desired format.

Expected Result:
 The user should get reports in desired format.
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 30 of 43

 5.1.12 Remote Opening and Locking Door

Test Procedure
Remote Opening and Locking of door
Name:
Test Case: Test Remote Opening and Locking of door feature
5.8 (vii): A forced entry shall be detected by the sensor and trigger alarm of
the Access Control system.
Clause
Reference: 5.8 (viii): A local alarm sound shall be activated at the operator’s HMI and
locally at the door, gate to alert security personnel to the location of the
forced entry. Reset of the forced entry shall be security protected.
Start Date End Date
Procedures Description:
1. After login to client, click on door status.
2. Navigate to the door, which should be opened manually.
3. Select the door and click on lock/permanent lock/disable lock/unlock etc. to see desired
change.
4. Check the physical door status.
5. Show the card to a reader and keep the door open. Door held alarm should come.
6. Disconnect power of Door Lock, Door forced should come.
Expected Result:
 The physical door status should change based on the command executed.
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 31 of 43

 5.1.13 View Live Events

Test Procedure
View Live Events
Name:
Test Case: Test to view live events
Clause
3.7.2: All alarms for events and faults shall be reported in real time.
Reference:
Start Date End Date
Procedures Description:
1. After login to client, click on monitor.
2. Navigate to events.
3. Check the latest event and see if it is real time
Expected Result:
 Live events should Come
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 32 of 43

 5.1.14 Viewing of Controller/Interface/Reader Online/Offline Status

Test Procedure
Viewing of controller/interface/reader online/offline status
Name:
Test Case: Test to control controller/interface/reader online/offline status
5.15.4: The ACS NMS workstations shall have a Graphical User Interface
Clause
using pull down menus and icons for user friendly manipulation of the NMS
Reference:
functions.
Clause
Reference:
Start Date End Date
Procedures Description:
1. After login to client, click on reader/controller/interface status based on which status you
want to see.
2. The devices with proper connectivity to the system will show online and rest unhealthy
ones will be offline.

Expected Result: Controller/interface/reader online/offline status

PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 33 of 43

 5.1.15 ACS NMS

Test Procedure
ACS NMS
Name:
Test Case: Checking Communication link failure of ACS system in NMS
5.15.4: The ACS NMS workstations shall have a Graphical User Interface
Clause using pull down menus and icons for user friendly manipulation of the NMS
Reference: functions.
5.15.7: The NMS shall have self-diagnostic feature.
Start Date End Date
Procedures Description:
1. Check the ACS system server connectivity from LAN.
2. Disconnect the power supply or shutdown the ACS server.
3. Login to ACS NMS application on another server.
4. Verify the server failure alarm is available on the NMS Application.
5. Restore the ACID server & recheck restoration status on the NMS application.
Expected Result:
 The communication failure should reflect in NMS alarms.
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 34 of 43

 5.1.16 Door Control Test

Test Procedure
Door Control Test
Name:
Test the demonstration of each access control card reader with EM lock
Test Case:
opening and reclosing.
1.2.6: All doors controlled by the ACS shall also be monitored by the
Clause system for their unlock and lock status and lock/unlock feedback status.
Reference:
5.8. (iv): If access is granted, the electrical locks shall automatically release.
Start Date End Date
Procedures Description:
1. Check the connectivity status of EM lock with access controller.
2. Green LED should glow in EML which indicates door close condition.
3. Check the status of the door in security view.
4. Display the valid card to the Smart Card or biometric card reader with thumb impression on
the sensor.
5. On valid transaction access will be granted and EML power will disconnect and open the
door.
6. Close the door and wait till EML LED become green again.
Expected Result:
 The door should open on showing valid card and de-energize the EM lock
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 35 of 43

 5.1.17 EM locks functioning in case of Power Supply Failure

Test Procedure
EM locks functioning in case of power supply failure
Name:
Simulation of proper functioning of electric EM locks in case of power
Test Case:
supply failure.
5.3.2 (c): The electrical locks may be configured as either ‘fail unlock or ‘fail
Clause lock, as appropriate to the access point location, on lock failure, power
Reference:
failure, fire alarm or emergency site evacuation.
Start Date End Date
Procedures Description:
1. Green LED should glow in EML, which indicates door close condition.
2. Check the status of the door in security view.
3. Disconnect the power to the controller powering the EM lock and check whether door can be
open or not.
Expected Result:
 In case of power supply failure of EML it will remain powered via battery and AC Fail
alarm will be generate in event tab.
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 36 of 43

 5.1.18 Override Key Test

Test Procedure
Override key test
Name:
Test the access control system with a proprietary override key in or near the
Test Case: Smart Card Reader that will allow room entry in event of complete failure of
the access control system.
1.2.3: Additional override physical key switches shall be provided as an
alternative means of access to the locations, wherever ACS controllers,
Clause ACDB are installed at station and depots. Override physical key shall also
Reference:
be provided at the intermediate doors through which above mentioned ACS
controllers, ACDB locations are being accessed.
Start Date End Date
Procedures Description:
1. Simulate the failure by disconnecting the connectivity of the reader to the ACS controller.
2. Use the Override key switch at the door to open the doors in case of failure.
3. Check the door can be open via accessing override key switch.
Expected Result:
 Door should open in case of key override switch pressed
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 37 of 43

 5.1.19 Exit Switch Test

Test Procedure
Exit Switch Test
Name:
Test Case: To test Exit Switch Functionality
5.8. (v): When the lock release button is operated on the exit side of doors
Clause the electrical locks shall release automatically for a pre-set duration. The
Reference:
pre-set time shall be adjustable.
Start Date End Date
Procedures Description:
1. Stimulate the closing of the Door
2. Use the Exit switch at the door to open the doors in case of failure.
3. Check the door can be open via accessing Exit switch.
Expected Result:
 Door will open when Exit Switch is pressed
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 38 of 43

 5.1.20 Card Reader Range with MIFARE

Test Procedure Card Reader Range with MIFARE

Name:
Test Case: To test card reader range with MIFARE card
Clause NA
Reference:
Start Date End Date
Procedures Description:
1. Display Mifare card to the reader from 50cm.
2. If card is not read by reader reduce the distance between card & reader and check the point
where reader will be able to detect the card.
3. Note down the card reader detection range for both type of cards.
Expected Result:
 Card reader detection rang
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 39 of 43

 5.1.21 Door Opening in case of Fire Alarm Input

Test Procedure
Door opening in case of fire alarm
Name:
Test Case: To test all door opening in case of fire alarm
5.3.2 (c): The electrical locks may be configured as either ‘fail unlock or ‘fail
Clause lock, as appropriate to the access point location, on lock failure, power
Reference:
failure, fire alarm or emergency site evacuation.
Start Date End Date
Procedures Description:
1. Configure fire alarm in software and select correct doors.
2. Simulate fire alarm trigger and check all selected doors are open or not.
Expected Result:
 All doors should open in case of fire alarm.
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 40 of 43

 5.1.22 Device Online/Offline Status

Test Procedure
Device Online/Offline Status
Name:
Test Case: To check the status of ACS devices.
Clause 5.15.7: The NMS shall have self-diagnostic feature.
Reference:

Procedures Description:
1. Go to Controller status/Interface status to check

Expected Result:
 Status will be visible
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 41 of 43

 5.1.23 Redundancy of ACS Central Servers

Test Procedure
Redundancy of ACS Central Servers
Name:
Test the failover (redundancy) scenarios (simulated) for the Central ACS
Servers and check ACS servers database(s) at the OCC are continually
Test Case: updated at the BCC during OCC operations.
Note: Servers will not be of the same make/model that is being planned for
Surat Metro Project.
Clause NA
Reference:
Procedures Description:
1. Check the connectivity of ACS system with central servers.
2. Ping the IP of both physical servers at OCC & BCC and the floating IP of database.
3. The database should be syncing regularly at BCC and status synchronized will be
shown.
4. Remove Primary server from LAN and ACS will shift to Secondary server.
5. Once the primary server is recovered up ACS need to be manually shifted back to it.
6. If the BCC fails it will not impact the ACS working and whenever it will be recovered up
data will start syncing.
Expected Result:
 The server will switch seamlessly
PASS FAIL

Comments:

Authorized Representative Initials

Executed by Witnessed by
Engineer
IDCUBE
(GC)
Employer
HFCL
(GMRCL)

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 42 of 43

 6 AUTHORIZED REPRESENTATIVE SIGNATURES

Authorized Representative Signatures: -

OEM
Name:

Designation:

Signature:

Date:

HFCL
Name:

Designation:

Signature:

Date:

ENGINEER(GC)
Name:

Designation:

Signature:

Date:

EMPLOYER(GMRC)
Name:

Designation:

Signature:

Date:

-End of Document-

Doc No. – SUR-01/TEL-02/TCP/ACS/010 FAT DOCUMENT – ACS

Ref: TEL- 02 Rev - 00 05th December 2023 Page 43 of 43