Testing and Documentation of SCADA-DMS System
Testing and Documentation of SCADA-DMS System
Testing and Documentation of SCADA-DMS System
Section 2, Chapter 7
TESTING & DOCUMENTATION
7.0
General
This section describes the specific requirements for testing and documentation of
the SCADA/DMS system. The general requirements of testing and documentation
are covered in Section 7.
7.1
Type testing
Equipments wherever mentioned in the specification for type testing shall conform to
the type tests listed in the relevant chapters. Type test reports of tests conducted in
NABL accredited Labs or internationally accredited labs with in last 5 years from the
date of bid opening may be submitted. In case, the submitted reports are not as per
specification, the type tests shall be conducted without any cost implication to
employer.
7.2
7.2.1
7.2.2
Page 1 of 9
After completion of hardware integration test, the SCADA/DMS system shall be built
from the backup software on electronic media (CDs/Magnetic Tapes) to check the
completeness of backup media for restoration of system in case of its
crashing/failure. The software deliverables shall include one copy of backup
software on electronic media.
7.2.3
(b)
(c)
(d)
(e)
(f)
(g)
(h)
(i)
(j)
(k)
(l)
Page 2 of 9
(m)
(g)
(h)
(i)
(j)
(k)
(l)
(n)
(o)
(p)
(q)
(r)
(s)
(s)
Page 3 of 9
7.3
The SCADA/DMS system shall be tested at the site. All hardware and software
associated with the SCADA/DMS system along with all RTUs/FRTUs/FPIs along
with all field devices including MFTs connected shall be tested under the field tests.
7.3.2
End-to-End Test
After the field installation tests, the Contractor shall carry out end-to-end test to
verify:
(a) the communication of RTUs/FRTUS/FPIs/MFTs with SCADA/DMS system
(b) the RTU /FRTU/FPI communication channel monitoring in the SCADA/DMS
system
(c) the mapping of SCADA database with RTU /FRTU/FPI database for all RTU
/FRTU/FPI points
(d) the mapping of SCADA database with displays and reports
The Contractor shall provide the details of all the variances observed and
corrections carried out during end to end test.
7.3.3
Page 4 of 9
Contractor shall provide & approve theoretical and practical figures used for this
calculation at the time of detailed engineering. The calculation shall entail reliability
of each individual unit of the System in terms of Mean Time Between Failures
(MTBF and a Mean time to Repair (MTTR) as stated by OEM. Reliability figures of
existing equipment shall be supported by evidence from operational experience at
similar types of installation / figure given by OEM.
From those data, the unavailability of each sub-system shall be calculated taking in
account each item redundancy. The global availability shall then be calculated from
those different unavailability data. This calculation shall lead to the failure probability
and equivalent global MTBF data for the control center system.
The overall assessment of System availability shall be provided in the form of an
overall System block diagram with each main item shown, complete with its
reliability data. The calculation of overall availability shall be provided with this
diagram.
System availability tests shall be conducted after completion of the field tests. The
system availability test shall apply to the SCADA/DMS system (hardware and
software) integrated with its RTUs/FRTU/FPIs and R-APDRP IT SYSTEM .
However, the non-availability of RTUs/Data Concentrators/ FRTU/FPI , R-APDRP
SECTION-2, CHAPTER-7 : Testing & Documentation
Page 5 of 9
IT system etc & Communication System shall not be considered for calculating
system availability. However , RTU/FRTU, communication equipments , Auxiliary
power supply shall be tested as per the provisions given in their chapters.
The SCADA/DMS system (hardware and software systems) shall be available for
99.5% of the time during the 360hours (15 days) test period. However, there shall
not be any outage /down time during last 85 Hours of the test duration. In case the
system availability falls short of 99.5%, the contractor shall be allowed to repeat the
system availability test after fixing the problem, failing which the system shall be
upgraded by the contractor to meet the availability criteria without any additional
cost implication to the owner.
Availability tests of RTUs/FRTUs shall be conducted along with System availability
test for 360 hours. Each RTU/FRTUs shall exhibit minimum availability of 98%. In
case the RTU/FRTU availability falls short of 98%, the contractor shall be allowed to
repeat the RTU/FRTU availability test (for failed RTU/FRTU only) after fixing the
problem, failing which the equipment shall be upgraded by the contractor to meet
the availability criteria without any additional cost implication to the owner.
In the event of unsuccessful reruns of the availability test, employer may invoke the
default provisions described in the General Conditions of Contract.
The system availability tests will be performed by the owner by using the
SCADA/DMS system and RTUs/FRTU/FPI for operation, control and monitoring of
distribution system and using Contractor supplied documentation. The owner will
also be required to generate daily, weekly and monthly reports. The supplied system
shall be operated round the clock.
The SCADA/DMS system shall be considered as available if
a) one of the redundant hardware is available so that all the SCADA/DMS
applications are functional to ensure the design & performance requirement
as envisaged in the specification
b) atleast one of the operator console is available
c) atleast one of the printers is available (off-lining of printers for change of
ribbon, cartridge, loading of paper, paper jam shall not be considered as
downtime)
d) All SCADA applications are available
e) All DMS applications are available
f) All SCADA/DMS functions described in the specification are executed at
periodicities specified in the specification. without degradation in the
response times
g) Requests from available Operator Consoles & VPS are processed
h) Information Storage and Retrieval applications are available
i) Data exchange with other system is available
However each device, including servers, shall individually exhibit a minimum
availability of 98%.
Page 6 of 9
During the availability test period, employer reserves the right to modify the
databases, displays, reports, and application software. Such modifications will be
described to the Contractor at least 48 hours in advance of implementation to allow
their impact on the availability test to be assessed, except where such changes are
necessary to maintain control of the power system.
The successful completion of system availability test at site shall be considered as
operational acceptance of the system.
7.4.1
Downtime
Downtime occurs whenever the criteria for successful operation are not satisfied.
During the test period , owner shall inform the Contractor for any failure observed.
For attending the problem the contractor shall be given a reasonable travel time of 8
hours. This service response time shall be treated as hold time and the test duration
shall be extended by such hold time. The downtime shall be measured from the
instant, the contractor starts the investigation into the system and shall continue till
the problem is fixed. In the event of multiple failures, the total elapsed time for repair
of all problems (regardless of the number of maintenance personnel available) shall
be counted as downtime. Contractor shall be allowed to use mandatory spares (on
replenishment basis) during commissioning & availability test period. However it is
the contractors responsibility to maintain any additional spares as may be required
to maintain the required system availability individual device/ equipment availability.
All outage time will first be counted but if it is proven to be caused by hardware or
software not of Contractors scope, it will then be deducted.
7.4.2
Holdtime
During the availability test, certain contingencies may occur that are beyond the
control of either employer or the Contractor. These contingencies may prevent
successful operation of the system, but are not necessarily valid for the purpose of
measuring SCADA/DMS availability. Such periods of unsuccessful operation may be
declared "holdtime" by mutual agreement of employer and the Contractor. Specific
instances of holdtime contingencies could be Scheduled shutdown of an equipment,
Power failure to the equipment, Communication link failure.
7.5
Documentation
Page 7 of 9
Page 8 of 9
Page 9 of 9