TAMIL NADU ELECTRICITY BOARD

SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

INDEX-G2: Technical Specification requirement of Application packages

Sub-Section Sl No. Description Page No.

1 Introduction 3
G2: Part-A – Essentially Required by
most Utilities for setting up an IT 2 System Functionality 6
backbone for collection of baseline
3 Module : Meter Data Acquisition 11
data, Energy Accounting / Auditing
and establishment of Customer care 4 Module : Energy Audit 31
centers
5 Module : New Connection 34
6 Module : Disconnection & Dismantling 39
7 Module : GIS based customer Indexing 42
and asset mapping
8 Module : GIS based integrated 84
network analysis module
9 Module: Centralized Customer Care 103
Services
10 Module: Management Information 132
System (MIS)
11 Module : Web Self Service 141
12 Module : Identity and Access 144
Management system
13 Module : System Security Requirement 158
14 Development of Commercial Database 164
G2: Part-B – Requirement based
implementation of Commercial of Consumers
Processes like M,B,C for Utilities, 15 Module: Metering 166
who do not have such IT enabled
systems 16 Module : Billing 172
17 Module: Collections 182
18 Module: Asset Management 186
19 Module: Maintenance Management 192

Page 1 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

SECTION – G2: PART-A

APPLICATION PACKAGES REQUIRED

ESSENTIALLY FOR TNEB

Page 2 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

[Link] -

Traditionally Indian distribution utility’s business processes are supported by the use of paper documents
and folders passed from table to table and function to function. A few of utilities have IT enabled part of
business processes, but they continue to run on existing business rules and systems.

GOI under APDRP has proposed to leverage strength of information technology for creation of authentic
base line data and support utilities in IT enablement of their business processes. Energy Audit and
Accounting would base on integrated IT solution by use of GIS indexing and asset mapping along with
network analysis software. Single window customer care centers would be available at front end to interact
with consumers, which will run through linking of back end business processes. The creation of IT
infrastructure under System requirement specification template will enable utilities to integrate other
business processes such as ERP, SCADA etc., at a later date as per the requirement of the utility, which are
presently not in the scope of the SRS document. The proposed solution in the SRS document will create the
building block of Enterprise Application integration. Therefore, proposed business process softwares should
be process oriented and support workflow management.

Though it is preferable that utility should carry out Business Process Re-engineering, to assess, analysis,
model, define and subsequent operational implementation of the core business processes of the utility. The
solution provider should study the business process of the utility with or without BPR to provide procedural
automation of business process.

Under competitive fast changing business environment coupled with reforms initiated in the sector, the
proposed solution under the scope of this specification must be agile and adaptable to change to tackle
corporatisation, competition, merger, demerger etc. The workflow system should be able to handle routing
of documents, structured information handling, complex event processing, programmatic manipulation of
information, and the ability to exchange information with web services and other external information
sources.

The entire system specified in the document should be able to provide procedural automation of the
existing business processes i.e work flow activities, invocation of appropriate human and/or IT resources

Page 3 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

associated with the various activity steps. The proposed solution should be able to respond to changes of
user’s need.

The document has been divided in different modules for purpose of specifying different kind of business
activities for ease of understanding but each of the module is a part of one business i.e. the distribution of
power by the utility. The workflow system should be able to interact between different processes and data
base to carry out required task. For example, to carry out DT wise energy accounting and audit it is
necessary for energy account module to extract information from GIS database for the no. of consumers
connected to that DT and their identification no. The MBC module will provide the energy consumption of
that given set of consumers for defined billing period and Data acquisition module will provide the energy
consumption of that DT for said period. The difference between these two sets of input will generate DT
wise energy loss.

Similarly the network analysis module will calculate technical loss for any given section of the network
based on GIS based network information and load flow details in Data acquisition module to segregate
technical and commercial losses.

The effort had been made to specify all such inter process interactions, however study of business process
of the utility is required by the implementing agency to complete the understanding. However, Service
oriented architecture would be preferred solution for work flow implementation.

SOA with its loosely coupled nature shall provide better flexibility in building applications and allow
enterprise to plug in new services or upgrade existing services in a granular fashion to address the new and
changing business requirements, shall bring better reusability of existing assets or investments and allow to
create applications that can be built on top on new and existing applications without completely rewriting
an application.

Service Oriented Architecture shall be implemented using standard set of technical specifications of Web
Services to achieve a platform-neutral approach for accessing services and better interoperability.

SOA should be approached based on business process as the driver and it should not be driven
Purely from an IT perspective (i.e. reuse only).

Page 4 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

The business process and its re-engineering would drive the abstraction of business process which in
turn would drive the identification of catalog of business services i.e., services at high granularity.
Also the variables in business rules embedded in these services should be configurable and not hard-
coded.
The scope of integration includes establishment of Business Services following SOA principles.
The solution should have a catalog of business services that are at a high level of granularity
(illustrated below in example, however an indicative list of service catalogue shall be provided which
can be customized by the concerned IT consultant) to facilitate flexibility in business process.
e.g.: New connection module could have the following set of services, some of which could be
common with other modules:
o Request for New connection
o Establish Customer (add/update; common with customer care module and web self-service)
o Establish Service Contract (add / update)
o Start Service Connection etc.

In addition, the solution could also have lower level granularity of services to facilitate re-use of
business functionality for the technical/IT Team. This is not mandatory but desirable.
The Solution would ensure that the above is achieved in one of these ways:
o The solution provides for all of the above “out-of-the –box”
o Additional business services are created, say using wrappers around existing services, to
create higher granularity of services

For Baseline data creation, IT enabling of distribution business will be required and the following
applications as add on modules will be integrated on GIS platform. The BPA software should be modular in
nature. The rate for each module should be quoted separately. Utility may implement in full or in parting
phases the BPA software. The requirement of different modules for Business Process automation is detailed
below.
Response Guide
Response Definition
Compliant (C) Functionality is included in the base product. No
customisation1 is required. Provide an explanation – refer
to comment field.
Explanation Required (ER) Functionality is included with some limitations, provisions

Page 5 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

or dependencies that require further explanation – refer

to comment field.
Future (F) Functionality is not currently included but will be
available within the next 12 months (from date of
submission of this proposal).
Customisation Required Functionality is not included in the base product but can
(CR) be provided by a customisation1 to the base product.
Non Compliant (NC) Functionality is not currently included and will not be
available within the next 12 months.
Comment Comments to explain or qualify the response.

Descriptive Style Responses

Responses are required in a written form, providing a descriptive or informational response. Depending on
the size and format of the desired response, respondents may choose to provide written responses in the
comments column of make reference to attached documents. Attached documents must be in Microsoft
Word, Microsoft PowerPoint, Microsoft Excel, Microsoft Project or Adobe Acrobat formats.
Customization - to alter the base product to meet the specifications of an individual organization, such that
it becomes unique and can no longer can be treated as a commercial-off-the-shelf product.

[Link] functionalities:-
Requir
Criticalit Respons Comme
ement Feature Functionality
y e nts
ID
Applications, systems and infrastructure are to
be characterized as service-oriented,
C/
Modular component-based & reusable. The system will be
Sf.1 Vital ER/F/
Design modular in design, operations and
CR/ NC
implementation.

The supplier is to balance the adoption of

standards used by market leading vendors and
products, and adherence to industry standards
and open architectures. Systems are to be
Sf.2 System acquired, developed, or enhanced in such a way Vital
Architecture that business processes; application and
infrastructure services and data can be shared
and integrated across the Utility and with
potential business partners.

Page 6 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Application architectures must be

highly granular and loosely coupled.
This is focused on loosely coupling systems
compliant to Service Oriented Architecture to
Application facilitate application recovery. This is to ensure
Sf.3 Vital
architecture that the failure of one component does not
cascade to others. A tier can also be scaled to
run separate applications to optimize
performance.

All the application designed for this

purpose shall be web based and the
Purchaser at workstation shall be able
to access through the latest available version of
Web based the web browser such
Sf.4 Vital
design as Internet Explorer, FireFox etc Any add-on
required must be integrated with latest version
released by the developer at the time of Bid
opening

Application requirements will be

based on Utility’s business processes
Business and the functional requirements that
Sf.5 Process derive from them. The application system should Essential
Requirement empower the Business Users in defining the
business processes by process modeling.

The applications must be capable of

running in a clustered environment
Sf.6 Data base as high availability configuration of database Essential
server server that will run multiple workloads.

The applications system should have the built

upon WS* specifications using open industry
standards of web services using XML, SOAP, WSDL
Basic System and UDDI and should have the unified access
architecture framework compliant to W3C portal
Sf.7 and Unified Vital
specifications for people, process and
Access information by integrating the backend
framework applications with single sign-on feature, role
based, request based and hybrid user type
access, searching and collaborative environment.

Common enterprise wide directory services shall

Directory be leveraged by all access systems and services
Sf.8 Vital
service used by all the enterprise users and adhere to
commonly accepted standards such as LDAP.

Page 7 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

As per the requirement, Interfaces between

Message based separate systems (both internal and external
Sf.9 Essential
interface systems) will be messaged based compliant to
W3C XML standard/OPC/DDE/ODBC interface.
Integration technologies must be
industry proven standards. They must be scalable
in capacity and provide for extensive
functionality.
WS* based Web Services integration
specifications shall be used from integrating
disparate systems, such as :
Web Services Messaging
Specification including SOAP
Sf.10 Application Web Services Reliable Messaging Essential
Integration Web Services metadata Specifications
including WSDL
Web Services XML Specifications
Web Services Business Process
Specifications including BPEL4WS
Web Services Management Specifications
EDIFACT and ANSI

Data is considered to be an utility wide asset and

is to be shared across the utility. Data stores for
Sf.11 Data Storage Vital
transaction processing shall be kept separate
from data stores for decision support.
The applications will access data through
business rules i.e. the applications must not
access data directly without going through APIs
Sf.12 Data access Vital
managed by business rules/ validation/workflow.
Data should be collected once and used many
times.
Data shall be stored at central data center. The
Central data Data acquisition server located at Central Data
Sf.13 Centre will acquire the meter data at periodic Vital
storage
interval as agreed between owner and bidder
during implementation stage.
The application should be capable in
running in a hybrid network connectivity
Sf.14 Network
environment i.e. Dialup, PSTN, Wireless, Leased Vital
environment
Line, WAN environment etc. including MPLS/VPN
based secured tunnel.
The application portfolio and the IT
infrastructure are to be vertically and
horizontally scalable in size, on demand with
Sf.15 Application
virtualization capacity, and functionality to meet Vital
scalability
changing business and technical requirements,
thereby enabling the utility to be adaptable to
change.

Page 8 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Applications need to be designed for

manageability using Enterprise Management
System.
Application
Sf.16 This needs to encompass: scheduling, backup and Essential
manageability
recovery, application, database and network
infrastructure monitoring, tuning and remote
diagnostic management.
The network will use standard, open, vendor
neutral communication protocols. Considering
Network the scale of implementation envisaged, the
Sf.17 system will provide for various networking Vital
option
options between different entities. Such options
would include Leased Lines, VSAT Links,
Telephone Modems, through Internet , VPN etc.

It will be possible to set various options and logic

Central of the system (for example -Calculation Logic of
Sf.18 Vital
Administration payable amount by consumer) centrally. This will
ease the system administration work.

Irrespective of the Operation/

Outsourcing option adopted for
operation of the system, the
Data ownership and physical possession of
Sf.19 the data will always remain with the Vital
Ownership
Discoms. The application should provide the
flexibility of system disintegration/aggregation
of information and application in case of
outsourcing, acquisition, and merger of Discoms.
The system will be able to grant
specific access rights to each login or group of
logins, as per the business
requirement and policy of the
Login wise
Sf.20 DISCOMs with unique identify across the Essential
rights, groups
enterprise system.
System shall also permit temporary transfer of
access rights within his group to officers for
employees reporting to him.
System will be required to maintain daily
Sf.21 Data Backup backups of the database on reliable backup Vital
media like DAT drives, CDs, tape etc.
The System will maintain only five years of
Sf.22 operations data online. Operations data more
Data Archiving Essential
than five years old would be archived and the
archives maintained at the various locations.
As per the requirement, system will exist in
Interface with conjunction with several other systems. It would
Sf.23 Vital
other system therefore be required to interface with
other systems for seamless flow of

Page 9 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

business information in Web Services or W3C XML

industry format/ OPC/ DDE /ODBC Interface.
To make the operations more efficient, the
Embedded system will have the facility of incorporating
Sf.24 embedded controls, which would force the Essential
control
organization to carry required tasks in the time
frame specified.
The system will provide a report generating tool,
which can be used to generate customized
Report reports at any level. The reports generated
Sf.25 Essential
Generation should be stored in various user configurable
“bins”. The access to bins should be configurable
by having security roles in the system.

The system will have the capability to

interface with the mailing system (e.g.
Lotus Notes, Microsoft Exchange etc),
if available, to deliver the Alerts and
Sf.26 Mail interface Service Orders. In the absence of Essential
such a system, the Alerts and Service
Orders will be served on portal with user login.
The system should also be capable of interfacing
with other applications (ERPs, MS Office etc).

The system will have in built priorities defined,

Prioritizing which will be used to process the prioritized
Sf.27 Desirable
workflow tasks first in case of system constraints (e.g.
network unavailability, time constraints etc).

The system should have provision for network,

Performance application, and database monitoring for
Sf.28 monitoring of performance management, tuning, remote Essential
system control configuration management features with
facility for SLA report generation.

The system should allow for a graphical interface

to view the summary data in MIS reports. This
Sf.29 MIS Reports Essential
would include trend graphs, graphs indicating
how much of the target has been met etc.

Client End: The solution should be able to

support a variety of client end Operating Systems
like Windows, Linux with X-Windows or MAC OS.
Multiple OS
support/
Sf.30 Server End: The solution should be built on open Essential
Inter-
standards and interoperable platform of WS*
operability.
based open specification and shall be able to
interoperate with multiple operating systems like
Windows, Unix and Linux.
Multiple The solution should be able to interoperate with
Sf.31 database multiple industry standard RDBMS platforms like essential
support Oracle, MS SQL, MY SQL, DB2, Informix, Sybase or

Page 10 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

any other RDBMS confirming to ANSI/ISO SQL-

200n standards and should be built on WS* based
open specifications.

1.0 Module : Meter data acquisition system

Objective :
The main objective is to acquire meter data from System and Select consumer meters automatically from
remote avoiding any human intervention, Monitor important distribution parameters, use meter data for
accurate billing purposes and generate exceptions and MIS reports for proper planning, monitoring, decisions
and taking corrective actions on the business activities by the management.

The above objective under this specification is achieved by providing an Automatic Meter Reading (AMR)
based Data Logging System using any of the available Communication Technologies available like GPRS,
EDGE, covering all the Feeder Meter, DT Meters and All HT and LT consumers above 25 KW in the entire
Utility area.

The module describes the broad functionalities and requirements of AMR based Data Logging System at
Substations, Sub division and other offices in the entire utility area, as described in the following sections to
acquire & store data of Energy Meters of various makes installed at 33/11 KV Feeders, Distribution
Transformers, HT Consumer and select LT consumer ends.

The sub station data concentrator unit will acquire data from feeder meters and will transmit the same to
central data centre server(s) through GPRS/EDGE. The meter data from all distribution transformers as well
as HT/select LT consumers will be transmitted to the central data centre server(s) through GPRS/EDGE. A PC
will be installed at each substation with a purpose for local viewing and monitoring of feeders by substation
staff.

The sub station meters are fitted with RS 485 ports, whereas meters at DT & select consumer locations fitted
with RS 232 ports. The supply and installation of the meters are excluded from the scope of this contract

The meters provided are modbus compliant. However, the solution provided shall be compatible with future
meters also, which may be introduced in Indian market complying with DLMS/COSEM/IEC-62056/ANSI C-12
19/IEEE P 1377 Standards. For solving the interoperability issue of different make / model of Meters
installed presently in different utilities, Utility is responsible for providing meter protocol and memory map
of the meters installed in their area.

As most of the meters provided presently are Modbus compliant, Modbus/TCP shall be the preferred mode of
communication.

The proposed Data Logging system is expected to provide continuous on line monitoring and logging of
essentially, though not limited to, the following parameters in respect of all incoming and outgoing feeders,
Distribution Transformers and consumers on real time basis : -
i. Voltage, Phase to Phase and Phase to Neutral
ii. Current on each phase
iii. Power factor

Page 11 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

iv. Frequency
v. Power - Active / reactive / Apparent
vi. Energy – Active, Reactive and Apparent

The proposed system is expected to provide continuous on line monitoring and logging of above mentioned
parameters and capability to generate Spread Sheets and MIS report as below :
i. System outage / downtime feeder wise.
ii. Energy balancing at sub stations .
iii. Daily peak loads feeder / transformer wise.
iv. Peak Load of the Station.
v. Bus bar profile.
vi. Daily Log sheets & any other forms / reports as required by the Utility

The detailed scope for each of the activities is detailed hereunder. The tentative quantities of Assets to be captured
under the said scope of work is being mentioned in Annexure-A of Section: G6.

Requirem Comm
Functionality Description Criticality Response
ent ID ents
Das.1.0 System features :-
A system that collects and
comprehensively manages meter data
from system (utility network) meters and
select customer meters using
Provision to
MODBUS/DLMS/COSEM/IEC/ANSI/EEE
collect and C/ ER/F/
Das1.1 compliant protocol. Vital
manage meter CR/ NC
data As most of the meters provided presently
are Modbus complaint, Modbus / TCP
shall be the preferred mode of
communication
A system that captures the meter data
remotely from all the meters at 33 KV,
22 KV & 11 KV Feeders, Ring fencing
Remote meters, Distribution Transformers and
capturing of HT/select LT Consumers for sending it
meter data automatically to the remote collection
Das1.2 Vital
from system & center i.e. Central data center.
select consumer The system should have a provision of
meters capturing data from captive generators,
third party sales, wind energy generators
etc if a provision of AMR is provided at
these meters.
The system provides for GPRS/ EDGE
Communication technology between
Provision of
Meters located at Distribution
Das1.3 communication Vital
transformer/HT/LT consumers substation
media
DCUs ring fencing Meters and Central
Data Center .

Page 12 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Optimal A system that optimally utilizes meter

Das1.4 utilization of data for distribution management and Essential
meter data billing.
A decision-support system for distribution
operations, asset management and
planning actions, e.g. Peak load
monitoring shall help in finalizing the
requirements for creation of additional
electrical network element or up-
gradation of existing electrical network
element to meet the increased demand /
Provision of a
load growth, Power factor monitoring
Das1.5 decision support Essential
shall help in capacitor placement
system
requirement, voltage monitoring shall
help in identifying low voltage areas for
network up-gradation, data captured on
imbalance between phases for DT,
substation and 3 phase consumer meters
can be used to increase reliability/plan
load balancing jobs / advise customer to
transfer loads between phases etc.
A system that pinpoints poorly performing
areas in the sub-transmission /
distribution network, based upon the
Identification of
technical parameters, such as area wise
Das1.6 poorly Vital
distribution losses, theft, outages,
performing areas
overloaded circuits/equipment, voltage
imbalance, reliability indices, power
quality etc.
A system that aids decision-making on
network upgrade actions by leveraging of
Helping in historical meter data to calculate area-
Das1.7 network upgrade wise load growth, equipment wise, Essential
actions downtime/outage statistics, seasonal
effects and usage pattern for long term
and short term planning.

Enabling health A system that enables ‘health’ and

and performance performance-monitoring and management
Das1.8 Essential
monitoring of of important system assets (feeders/
assets transformers).
A system that enables quicker, ‘event-
Detection of driven’ detection of HV/DTR outages
Das1.9 Essential
HV/DTR outages thereby improving reliability indices and
customer satisfaction.
A system that enables monitoring of
customer “performance”, e.g. contract
Monitoring of demand violation, peak load violation,
Das1.10 customer tamper counts, average power factor etc. Essential
performances The system should also have provisions to
cover usage patterns to solve high
consumption complaints, facilitate

Page 13 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

calculation of assessed readings for

stopped meter cases, detect low
consumption cases by comparing average
historical consumption with actual
consumption.
Enabling A system that enables dispatching of
dispatch of event notifications to targeted recipients
Das1.11 Essential
event for faster field response and decision
notifications making.
Das.2.0 Scope of deliverables :
Supply and installation of Server, Work
Supply
station with Printer and all other
Das2.1 /installation of Vital
hardware system for data acquisition
Hardware
system at Central Data Centre
Web based Application software for
Application
capturing, validating and analyzing the
software for
Meter data for the given size of Utility
capturing,
Das2.2 network defined in Annexure-A of Section: Vital
validating and
G6. (Sub Station feeders, ring fencing
analyzing the
meters DTs, HT Consumers and select LT
Meter data
Consumers)
Application software for acquiring
Application incremental meter data from all metering
software at data points under the utility area for
Das2.3 Vital
center aggregation, analysis and generation of
various MIS report through appending of
the Metering module.
Supply and installation of data
Supply/
concentrator unit and connect all
installation of
substation meters through Daisy chaining
Das2.4 data Vital
along with field wiring / cabling from
concentrator at
feeder meters to Data concentrator unit
sub stations
Supply and installation of suitable (
Supply/ GPRS/ EDGE) Modem at sub stations
installation of for communication between Data
Das2.5 Vital
Modems at sub Concentrator Unit located at sub station
stations and data acquisition server at Data
Centre.
Supply and installation of suitable Modem
(/GPRS/ EDGE/) at meter ends for
Supply/
communication between Meters located
installation of
at Distribution transformer, ring fencing
Das2.6 Modems at DTs Vital
meters and HT/select LT consumers and
and HT/ Select
Data Acquisition Server at Central data
LT consumers
Centre. Modem may be retrofitted on
optical port of the meter.
Supply/
installation of
Any other equipments or accessories
Das2.7 any other Essential
required for operation of the system.
equipments or
accessories

Page 14 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Das.3.0 System Architecture : General Notes

An integrated software system should be
provided to meet the following Functional
requirements spanning Automated Meter
Reading :-
 Real Time data acquisition from
Meters
 Historical data acquisition from
Meters
Provision of an  Supervisory function i.e. process-
integrated ing, monitoring, analysis and
software system diagnostics
Das3.1 Vital
to meet the  Data exchange
functionality of  Storage of data
AMR  Report generation and reporting
 Facility for user defined forms and
reports e.g. calculation of Feeder/
DT performance statistics
 Facility for time synchronizing
 Alarm list
 Event list
 Limit value violations

Flexible The software system

deployment / deployment/implementation should be
Das3.2 implementation flexible. The deployment should be web Vital
of software based and there should be no need for
system any installation / licensing at client end.
The software shall be web based system
Web based
Das3.3 for automatic data display and reporting Essential
software system
capturing, etc.
The software shall have option for data
Provision for
collection from meters connected locally
Das3.4 local / remote Vital
or that are located in remote locations,
data collection
through modem communication.
Facility for Web
Das3.5 Software shall have web based front end. Essential
based front end
The software shall ensure data validation
at Central Data Centre after reception to
Provision for eliminate possibility of garbage data. The
Das3.6 Vital
data validation. system at Central Data Centre should
apply comprehensive data validation
before accepting and using meter data.
Provision for The software system shall be flexible in
flexibility, user terms of System & Application software,
Das3.7 Essential
friendly and user friendly and scalable upwards and
scalability downwards.
Software system The software should be based on a robust
with robust architecture model / framework that is
Das3.8 architecture, highly scalable/available/reliable, gives Essential
high availability good performance, and offers distributed
and reliability computing.

Page 15 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

The software would be designed with

multi-tier (N-tier) design methodology. It
N-tier design should have distinct tiers representing the
Das3.9 Vital
methodology data acquisition/ data processing/ time-
series database/ rule based MDM/ web-
interface/ reporting layers etc.
The client tier will be the interface of the
software with the utility’s operations/
dashboard user. The client tier will
Das3.10 Client tier provide all the user interfaces for the Vital
operational and supervisory activities
involved in meter data acquisition,
processing and analysis.
The business logic tier would service the
requests made by the client tier. These
Business logic
Das3.11 requests could be automated, based on Vital
tier
user-defined schedules or on-demand
from the user.
Automatic Normal workflow processes from meter
workflow data acquisition to analysis would be as
Das3.12 process from automated as possible; for example user Essential
data acquisition intervention would be sought only for
to analysis data editing or verification decisions.
The database tier should comprise an
RDBMS that should be designed to be able
to maintain the relationships between
Das3.13 Database tier Vital
meter and network assets, network
topology, user privileges, service points,
customer accounts and other entities.
The database should also maintain a time-
series repository that stores the data
collected and processed from meters,
Maintenance of including interval usage data, event logs
Das3.14 time stamped and outage history, as well as derived Vital
database data such as aggregations and asset
performance indicators like load factor
and load duration curves.

Optimal The database tier should be optimally

Das3.15 designing of designed to exploit both normalized as Desirable
database well as multidimensional data models.
Both OLTP (Online Transaction Processing)
Provision of
and OLAP (Online Analytical Processing)
Das3.16 OLTP and OLAP Essential
models should be exploited for ensuring
models
performance and scalability.
Features for Data logging system at Sub
Das.4.0
station:-
Software shall be capable of collecting
Data collection data on a common data structure /
Das4.1 on a common format from Feeder meters of various Vital
data structure manufacturers installed in the Sub
station. The data logging software

Page 16 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

package should be able to integrate,

extract and analyze data of different
make of Meters.

Das4.2

The software will in general collect the

following data from the meter -
 Billing Data
Main areas of  Load survey profiles
Das4.3 Vital
data collection  Tamper data
 Date and time of collection of data
 Instantaneous parameters at the time
of collection
A typical list of data acquisition from the
Meters has been mentioned below :
 Acquire real time instantaneous data
like voltage, current frequency, power
factor, active power, reactive power
etc. at the specified regular intervals
( 15 minutes as per meter
specification) for online monitoring
Typical list of anywhere across Utility using web
Das4.4 data acquisition browser. Essential
from the Meters  Acquire stored historical values of data
at regular interval with power
consumptions, accumulated energy,
accumulated power, maximum
demand and other parameters.
 Acquire real values of specified
parameters on demand.
 Synchronize date and time of all
meters.
Software shall be able to provide details
Provision of of critical events (e.g. No communication
Das4.5 generating with Meter,, Power failure etc.) and Essential
critical events necessary provision should exists to report
the correct event to user.
Software shall have facility to enter
Provision of
manual readings & associated data for
manual entry of
Das4.6 taking care of meter change on feeder, Essential
data in case of
but only with appropriate user
meter change
identification, security and audit trail.
Seamless Software shall show and transfer data
transfer of data seamlessly even in case of meter change.
Das4.7 Essential
even in case of An indication of meter change shall be
meter change available.
Sub-station data concentrator unit will
Storage of meter
acquire and store the Meter data in it’s
Das4.8 data at sub Essential
memory and push the data to the central
station
data center at pre defined intervals..
Das4.9 Mode of data Normally the data transfer from Essential

Page 17 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

transfer from Substation to data center will be over

sub station to /GPRS/ EDGE/The data should be sent
Central Data automatically on pre-defined interval (15
Centre mins).
Facility for back
Facility for taking backup & restore of
up and
Das4.10 data collected at Data centre shall be Essential
restoration of
provided in software.
data
The software at the data center shall
provide administrator facility to decide
the storage of data for at least three
Administrator
Das4.11 [Link], the data concentrator Essential
facility
unit at the sub station shall have a
storage capacity of Meter data of at least
24 hours
Features of Data Logging system for
Das.5.0 Central Data Centre:-

System shall be capable of collecting data

from all the HT consumers at least every
One Hour and from all the Distribution
Transformers at least once in 24Hour.
The meter data from the substation data
concentrator units shall also be captured
at least once in 24 Hours.
The data transfer from field to data
center should be automatic without the
need for any dialing or scheduling at the
data center.

The number of HT consumers and number

Periodicity of
Das5.1 of DTs have been furnished in the Vital
data collection
enclosed Annexure-A of Section: G6.
However, the bidder may visit the area
and collect the exact details about the
number of HT consumers and number of
DTs at site and design and supply the
system as per actual availability at site.
Further, the system shall be designed and
shall have provisions for inclusion of new
Consumers and Assets in future and shall
provide additional spare capacity to cater
7.5% per annum growth over and above
the actual requirement at site on account
of the future provisions.
The Data acquisition software at central
data centre must have the following
functions :
Functionality of
a) Data Collection : It shall receive data
Das5.2 Data acquisition Vital
from the remote Data concentrator
software
unit installed at the substations DTs
and HT consumers through
GPRS/EDGE Modems and store in the

Page 18 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

database.
b) Data Processing : It shall use data
from the database to create reports,
charts and spread sheets.
c) Data transfer to data center : All the
modems should be able to transmit
the meter data to central data centre
which shall reside in the Metering
module for further aggregation,
analysis and MIS generation as per
request from various utility offices
d) Messaging : Via GPRS/EDGE
e) Program Generator: It shall have
editors and configuration software.
f) Facility to communicate with multiple
clients simultaneously through
multiple communication lines.

The system shall have sufficient memory

capacity for storing every Analog, Digital
Availability of and Accumulator data of all connected
Das5.3 sufficient remote Data concentrator units as well as Vital
storage capacity all Ring fencing meters, DTs and
Consumer data for a period of at least
three year at Central Data Center.
Generation of The software shall provide DT wise,
DT wise, Feeder Feeder wise and Substation wise data
Das5.4 wise and for generating summary reports, Essential
Substation wise statistical data, performance indices etc.
data base in user defined forms.
Ability of
Software shall be capable of collecting
software to
data on a common data structure /
integrate,
format from DT meters and HT/select LT
extract and
Das5.5 consumers of various manufacturers. The Vital
analyze data of
data logging software package should be
different make
able to integrate, extract and analyze
of Meters
data of different make of Meters.
The modems (remote devices) should
Manual/
automatically send the data at pre
automatic mode
Das5.6 configured interval of time. There should Essential
of data
be option for changing the frequency of
transmission
data transfer from the central server.
The collected data can be viewed in the
Viewing / form of customized reports. User can take
Das5.7 exporting of print outs of these reports, export the Essential
collected data data into spreadsheets, or convert the
data in the form of flat file.
The data will be transferred from various
AMR devices/data concentrator unit to
Mode of transfer
Das5.8 the data centre server in one of the Vital
of Meter data
following possible methods :-

Page 19 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

By default data shall be automatically

sent in push mode by the AMR
Automatic Data
a) devices/data concentrator units to the Vital
Transfer
Data Centre at preconfigured time
interval.
Under special circumstances there should
Manual Request also be a provision to get the data on
b) Vital
for Data manual request from AMR devices/data
concentrator units
Facility for
Facility for archiving, deletion and taking
archiving,
backup & restore of entire or part of the
Das5.9 deletion, backup Essential
data collected at Central server office
& restoration of
shall be provided in Software.
the data
Meter Data Acquisition : software
Das.6.0 requirements

The Data collection engine of the Data

Configurable
logging software shall be configurable for
data collection
Meter of different make and shall have
Das6.1 engine for Vital
the ability to perform remote data
meters of
acquisition from system and customer
different make
meters.
Enabling of data The software will enable data acquisition
acquisition from from different AMR configuration schemes
Das6.2 Vital
different AMR (based on location and selection of
configuration system/consumer nodes)
Enabling of data
The software will enable data acquisition
acquisition over
over any of the locally and reliably
Das6.3 any Vital
available communication media : GPRS,
communication
EDGE, etc.
media
Provision to
configure and
The software will be able to configure and
manage
manage technical parameters for the
Das6.4 technical Vital
communication media used in the project.
parameters for
communication
media
Provision of
Remote reading collection will be possible
remote reading
in data push from the field devices
& collection in
Das6.5 automated mode. as well as in the on- Vital
both automated
demand (real-time) mode.
and
manualmode.
Data from remote AMR devices will be
acquired [Link] will
allow reading cycle to be configured
Features of data either for individual meters or groups of
Das6.6 Vital
collection [Link] time windows for
data collection from different meters at
preconfigured interval of time to the Data
collection server at the DC can be [Link]

Page 20 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

data collection could be at any one of the

pre-defined monthly, daily, hourly or
quarter-hourly frequencies or at any user-
defined frequency greater than 15
minutes.
The software will support both inbound
Support for both
and outbound communication, i.e. data
inbound and
Das6.7 transfer could be initiated by either the Vital
outbound
remote meter in general or the central
communication
software in case of special requirements.
At minimum, inbound communication will
include event notification calls for power
Type of Inbound outage and restoration events.
Das6.8 Essential
communication The event driven polling of meters shall
enable pinpointing of faults during
outages, defective or stopped meter.
In outbound communication, the number
of retries made by the software for failed
meter readings will be configurable. If the
Type of
meter cannot be read even after the
Das6.9 outbound Essential
specified number of retries, the system
communication
will raise an alarm and generate meter
reading exceptions to enable tagging of
cases for site verification.
Ability to The software will have the ability to
retrieve both retrieve both instantaneous and logged
Das6.10 Essential
instantaneous data from the meter.
and logged data
The software will support import of meter
data from external sources in industry-
standard formats like ASCII, CSV or XML. It
Support for will also allow manual entry of meter data
Das6.11 import of meter in exceptional cases only with appropriate Essential
data user identification, security and audit
trail. The input sources of meter data
could be CMRIs (Common Meter Reading
Instruments), substation log books etc.
The software will be able to synchronize
the date and time of all remote devices to
a common fixed reference of the server
Synchronization
clock.
of all meters to
Das6.12 Essential
a common fixed
All the raw meter data entering the
reference
system via AMR or any external means is
time-stamped and stored for audit and
further analysis.
Network Topology Management
Das.7.0
Ability to The software will be able to capture and
capture and maintain the geographic / administrative
Das7.1 Essential
maintain the / regional hierarchy of a utility’s control
geographic / area, i.e., the tree hierarchy of zones,

Page 21 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

administrative / circles, divisions, subdivisions, sections

regional and substations constituting a utility.
hierarchy
Ability to
The software will be able to capture and
capture and
maintain the electrical network topology,
maintain the
Das7.2 i.e. ring fencing meters, substations, Essential
electrical
feeders, transformers and HT consumers
network
and select LT consumers.
topology
Flexible and Both the regional hierarchy and topology
Indian context would be specific to the Indian context
oriented and flexible enough to account for
Das7.3 Essential
regional different voltage levels in Indian sub-
hierarchy and transmission and distribution networks
topology e.g. 66/33/22/11/ 0.4 KV.
Provision to
The software will be able to capture and
capture and
maintain associations between various
maintain
Das7.4 metering nodes (both system and Essential
associations
consumer meters) and the regional
between various
hierarchy / network topology.
metering nodes
System metering nodes could include
AMR-enabled meters located at these
network points, among others: (i)
Outgoing feeders from grid substations (at
33kV/ 22kV / 11kV etc), (ii) Incomers
Typical list of (33kV etc) at the power/secondary
Das7.5 System metering substations, (iii) Outgoing feeders Vital
nodes (22kV/11kV/ 6.6kV etc) from the
power/secondary substations, (iv) inter-
region power import / export tie-points
on sub-transmission/ distribution feeders,
(v) Distribution transformers (DTR)
primary/secondary.
Consumer metering nodes could include
Typical list of AMR-enabled meters located at the
Das7.6 Consumer service points of selected H.T./L.T. Vital
metering nodes consumers (e.g. those with load above
25kW)
Provision for
modification in The software will allow modification of
Das7.7 Essential
existing existing metering node parameters.
metering nodes
The software will allow addition of virtual
Provision to add
metering nodes and associate the same to
Das7.8 virtual metering Essential
the regional hierarchy / network
nodes
topology.
Provision to
Navigation to any level of the regional
Navigate to any
hierarchy / network topology would be
level of the
Das7.9 simple and intuitive via drill-down Essential
regional
mechanism.
hierarchy/
network

Page 22 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

topology
Provision to Software will be able to display SLD
Das7.10 Essential
display SLD schematics for important network areas.
Software shall have facility for creating
Provision to data base and display of single line
Das7.11 depict Single diagram of entire electrical network and Essential
line diagram embedding of acquired data (both analog
& digital) of each feeder in real time.
Data Validation, Editing and Estimation
Das.8.0
(VEE)
Supporting of Software will support automated rule-
Das8.1 automated rule- based validation and estimation of raw Essential
based validation metered data.
The software would support multiple data
Supporting of states for metered data through its
Das8.2 multiple data transition from acquisition to analysis e.g. Essential
states invalid, estimated, edited, verified,
validated etc.
The software will allow configurable
validation rules that may be selectively
Configuration of
Das8.3 applied to an individual metering node or Essential
validation rules
groups of metering nodes or to channels
common to different metering nodes.
Logging of
Validation failures would be logged for
Das8.4 validation Essential
audit purposes.
failures
Backing up of Raw data would be backed up for audit
Das8.5 Essential
raw data purposes.
Provision of
The software will have a meter data
meter data
Das8.6 estimation routine that will be triggered Essential
estimation
on occurrence of validation failures.
routine
Enabling of
The estimation routine can be selectively
Das8.7 estimation Essential
enabled/disabled.
routine
Provision of The software allows manual editing of
Das8.8 Essential
manual editing metering data with audit trail.
Provision for All data state transitions would be logged
Das8.9 Essential
audit trail for audit trail.
Das.9.0 Data Analysis & Charting
The software will enable processing of
validated meter reading data for
Processing of
generation and storage of different time
Das9.1 validated meter Essential
series channels. A channel would hold
data
data pertaining to one particular
parameter.
Support for The software will support multiple
multiple channels for multi-parameter such as
Das9.2 channels for Voltage, Current, Frequency, Energy, Essential
multi Energy demand, performance indicator
parameters and event related data.

Page 23 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Support for
The software will support channels of
channels of
Das9.3 different time granularities, i.e. hourly, Essential
different time
daily, monthly etc.
series
Support for
different The channels could hold direct measured
Das9.4 channels for data, derived (calculated) data, or data Essential
different type of imported from external sources.
data
Viewing of time
series data in User will be able to view time series data
Das9.5 Essential
tabular / in tabular as well as graphical format.
graphical form
Ability to show The software will be able to highlight the
status of time state of a particular time series data
Das9.6 Essential
series data element, e.g. if it is absent, edited,
element estimated etc.
The software will enable user to compare
Comparison of
multiple time series together. The data
Das9.7 multiple time Essential
series could pertain to the same channel
series data
or different channels.
Automated filling up of certain derived
Facility for
time series channels based on data in one
automated
or more other channels will be enabled;
filling up of
e.g. data for the power factor channel of
certain derived
a particular metering node can be
Das9.8 time series Essential
calculated using the data in the active
channels based
power and reactive power channels of the
on data in one or
same node. The latter two may have been
more other
directly filled with measured data from
channels
the meter.
Provision of The software will allow setting / editing
setting/editing of the conversion formulae for the derived
Das9.9 of the channels. The conversion formulae can be Essential
conversion based on simple arithmetic /
formulae trigonometric / aggregation functions.
The software should allow aggregation of
Provision of
time series data based on parameters like
Das9.10 aggregation of Essential
geography (regional hierarchy), network
time series data
topology, time and customer category
Das.10.0 0 Executive Dashboard
Various utility offices, such as Circle,
Division, Sub division, sections, sub-
Provision of
stations etc., can interact with master
Executive
Metering (AMR as well as non AMR
Das10.1 dashboard at
enabled) / Billing database at data
various utility
center to provide the below mentioned
offices
features.

Provision of The software would support selective

Das10.2 selective monitoring of important summarized data Essential
monitoring of at user-defined intervals that would aid in

Page 24 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

summarized data decision-making for distribution

operations and planning actions.
Key performance indicators, like AT&C
Highlighting of
losses, SAIFI, SAIDI, CAIDI (but not limited
Das10.3 key performance Essential
to) will be highlighted for every level of
indicators
the network hierarchy.
Energy balance at different network
levels will be captured and displayed. This
Energy balance
enables monitoring losses by region
Das10.4 at different Essential
(section/subdivision/division /circle etc)
network levels
and by network asset
(transformer/feeder).
Monitoring of
losses at Monitoring of losses at different voltage
Das10.5 Essential
different voltage levels will be enabled.
levels
The software will enable capture and
display of data from multi-parameter load
Display of load
Das10.6 survey analysis. Monitoring of Essential
survey analysis
usage/demand patterns would thus be
enabled.
Monitoring of Peak load at different network levels
Das10.7 Essential
peak load could be monitored.
Monitoring of Performance factors like load factor,
Das10.8 performance power factor, utilization factor, load Essential
factors duration curves etc would be monitored.
The dashboard will enable transformer
load management. User will be able to
Provision of
monitor overloading/ under loading,
Das10.9 transformer load Essential
phase imbalance, load factor, utilization
management
factor, load duration curves of
transformers.
The dashboard will enable feeder load
management. User will be able to
Provision of
monitor overloading / under loading,
Das10.10 Feeder load Essential
phase imbalance, load factor, utilization
management
factor, load duration curves of feeders
etc.
Personalization
The software would support
as per the user’s
Das10.11 personalization of the dashboard displays Essential
preferences.
as per the user’s preferences.
Navigation from
one level of Navigation from one level of network
Das10.12 network hierarchy to another will be intuitive and Essential
hierarchy to drilldown will be possible
another
Das.11.0 1 Reports
Generation of The software will be able to generate and
Das11.1 reports based on display reports based on the results of Essential
the results of data analysis. The reports module will be

Page 25 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

data analysis used as a more data-heavy alternative to

the Executive Dashboard.
The software will be able to display
Reporting on
reports on all energy, demand,
energy flow,
Das11.2 performance factor and event related Essential
performance
data available for different metering
factor etc.
nodes.
Generation of Each report will allow user to specify
Das11.3 reports with parameters like date range, end points for Essential
date range which reports need to be generated.
Type of The reports could be either Windows or
Das11.4 Essential
reporting Web based.
The software will enable the user to
Exporting of
export reports into other application
Das11.5 reports to other Essential
software like ERP, Microsoft Excel etc. for
applications
further processing.
Reports for Sub stations :
Das11.6
Finalization of Few typical reporting requirements are
reporting mentioned below, exact formats &
Das11.6.1 Essential
requirement as requirement may be finalized as per the
per utility requirement of the Utility.
Facility to
configure & view Software at substation level shall provide
Das11.6.2 parameters in facility to configure & view parameters Essential
tabular/graphic captured in tabular & graphical format.
form
Software shall have facility to query data
Facility to query based on dates & parameter name.
data based on Software shall be able to show trend for
Das11.6.3 Essential
date & single parameter & comparative trend for
parameter name multiple parameters based on the
selection.
Das11.7 Reports for Sub division office
Software shall provide comprehensive
Provision for
reporting & MIS facility and it should
comprehensive
Das11.7.1 provide fixed format as well as query Essential
reporting and
based reports in tabular & graphic format
MIS facility
as required by user.
The user should have option for viewing
selective data like Instantaneous
parameters, Cumulative Energy Readings,
Tamper information's, Tariff-wise Billing
Option to view
Data for each reset backup, Load Survey
data selectively
Das11.7.2 data, Meter Programming records. Option Essential
in numerical /
should be provided to view the Load
Graphical form
Survey data in both numerical as well as
In Graphical format with selective or
composite view of parameters and in
different styles viz. bar, pie and line.
Generation of The software should scan through each
Das11.7.3 Essential
summary report meter data and generate a summary

Page 26 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

of meter data report of billing data, contract demand

for any load violation / peak load violation/ off days
violation and violation along with tamper counts for
tamper counts that particular meter.

Menu option shall be given for viewing

each data reports. The options will be
enabled based on the availability of the
Provision of data for the meter selected for data
menu option for viewing. Each report header should give
Das11.7.4 Essential
viewing each the information regarding the Meter serial
data report Number, RTC, Date and Time of data
collection, Type of collection, CT/PT
details and other important consumer
details.
Reports should provide detailed
information on Billing data, Load
Survey data, Profiles, Tamper
information, Programming mode
records and other system irregularities.
Following is a representative list of
Typical list of reports for different levels of the
Das11.7.5 reports to be network hierarchy and for different Essential
generated timeframes.
Energy balance report
Consumption trends report
Load factor report
Reliability analysis Report
Asset utilization report
Electrical network monitoring report
User should have extensive Search option
for search using Meter number, Consumer
Number, Consumer Name, Location, Date
Availability of of Reading of meter. An explore option
Das11.7.6 extensive search should also be given for listing out all the Essential
options meter data available in the system. This
menu option will provide the list of data
files sorted in the order of serial numbers,
consumer account number and location.
Few typical reporting, requirements are
mentioned below, exact formats &
requirement may be finalized as per the
requirement of the Utility.
 Display of Electrical Parameters (Load
List of a few current in Amp, power factor,
Das11.7.7 typical reporting frequency, voltage, active, reactive Essential
requirements and apparent power etc.) in Tabular
Formats and as Trends (Graphs) Over
Periods (e.g. for a week or month)
 Comparative tabular & graphical
reports for more than one meter &
more than one parameters (comparison

Page 27 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

of pure values as well as Min, Max,

Sum, Average)
 Min, Max, Sum, Average electrical
parameters values, its time of
occurrence and duration of maximum
and minimum values
 Graphical Display of Maximum Power
Demand Analysis
 Software shall have facility to query
data based on dates & parameter
name
 Software shall be able to show trend
for single parameter & comparative
trend for multiple parameters based
on the selection.
 Support for sending report using Email
or Alerts
 User Configurable Reports using MS
Excel
 Detailed Error Reporting and diagnosis
through Log Files and online display of
Error Status
 Printing and Exporting of Reports to MS
office.
 % availability factor of feeder (i.e. %
of time for which power was available
for feeders to know the reliability
index of the feeder)
Reports for various Utility offices, such
Das11.8
as Division, Circle, Head Quarter etc. :
Web based Reporting Software shall be
available through web browser to Various
utility offices, which can interact with
Metering/ Billing database at Data center
Reporting to provide extensive analysis & reporting
facility at facility. It shall also have extensive search
Das11.8.1 Essential
various utility options and should provide fixed format
offices as well as query based reports in tabular
& graphic format as per the requirement
of the utility and described in detail at
para Das.11.7 above (i.e. Reports at Sub
division offices).
The various offices of the utility e.g.
Geographic/
zones, circles, divisions etc. can login to
administrative/
the system for generating and viewing
Das11.8.2 regional Essential
various MIS reports, statistical data,
hierarchy wise
performance indices etc. as per their
reporting facility
requirement.

Das.12.0 Event and Alarm Notification

Das12.1 Monitoring of The event list shall contain events, which Essential

Page 28 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

important events are important for monitoring. The date

and time has to be displayed for each
event.
The events shall be registered in a
chronological event list, in which the type
Chronological of event and its time of occurrence are
Das12.2 registration of indicated. It shall be possible to store all Essential
events events in the computer. The information
shall be obtainable also from printed
Event log.
Faults, errors and limit value violation
of all values occurring shall be listed in an
Listing of faults,
alarm list. Audible annunciation must be
errors and limit
Das12.3 provided on receiving alarm. It shall Essential
value violation
contain unacknowledged alarms and
in alarm list
persisting faults. Date and time of
occurrence shall be indicated.
The alarm list shall consists of a summary
display of the present alarm situation.
Each alarm shall be reported on line that
Summary display
contains :
Das12.4 of alarm Essential
 Alarm date and time
situation
 Name of the alarming object
 A descriptive text
 Acknowledgement state
The operator shall be able to
Acknowledgeme
Das12.5 acknowledge alarms. Acknowledged Essential
nt of alarms
alarms shall be marked at the list.
The system will analyze time-series /
meter data and generate
alarms/notifications. Following is the
representative list of items on which
system may generate alarms :
Typical list of  Alarms based on consumption
items on which patterns
Das12.6 Essential
system can  Alarms based on loading conditions
generate alarms  Alarms based on tamper detection
 Alarms based on outage detection
 Alarm based on violation of limit
values
 Ability to configure criticality /
priority of the events
The system will have framework that
Framework to allows user to configure thresholds for
configure generating alarms at each end-point. (e.g.
thresholds for one set of end points, user should be
Das12.7 Essential
generating notified if daily consumption exceeds Y
alarms at each kWh and for some other end points alarms
end-point should be generated only if the daily
consumption exceeds X kWh).
Alarm on failure The system will also generate alarms
Das12.8 in based on any failure in communication, Essential
communication, missing/loss of data.

Page 29 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

loss of data etc.

Supporting of
The system will support dispatching
alarm/
alarms/notification using various
Das12.9 notification Essential
communication media like SMS, E-Mail,
dispatch via
Desktop Application etc.
comm. media
Ability to deliver The system will allow each alarm /
alarm/ notification to be delivered to multiple
Das12.10 notification to recipients. (e.g. alarms corresponding to Essential
multiple outage at DTR level should be sent to a
recipients J.E. and an S.E.)
The system will allow turning on/off
Provision for certain type of alarms generation (at
turning certain system wide level or for particular end
Das12.11 alarm generation point) based on user preferences. (e.g. if Essential
on/off as per one does not want any Communication
user preferences Failure alarms, he/she can turn off the
alarm generation for this criterion)
The system will allow turning on/off
Provision for
dispatching alarm notifications to
turning certain
required recipients. e.g. if Chief
Das12.12 alarm dispatch Essential
Engineer, does not want to receive any
on/off as per
alarms for some reasons, system should
user preferences
be able to turn-off the same)
The system will allow user to
Provision to
acknowledge or ignore events/alarms.
acknowledge or
Das12.13 System will also allow user to log the Essential
ignore events /
actions taken, if any, for any particular
alarms
event.
Setting of
The system will support different priority
different priority
levels for different types of events/
Das12.14 levels for Essential
alarms.
different events
/alarms
Provision of The system will support different dispatch
different schedules for different types of events/
dispatch alarms. (e.g. Outage Alarms to be
Das12.15 schedules for dispatched within 5 minutes of receipt Essential
different types and Contact Demand violation alarms
of events/ should be dispatched before every billing
alarms cycle start)
Das.13.0 1

Page 30 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

2.0 Module: Energy Audit

Objective : Monitor important distribution parameters, capture hierarchical view of energy accounting,
Network assets of power distribution utilities, intelligent analysis tools for plugging loop holes and
identifying revenue leakage, adding into perform network planning and management activities,
calculate / identify technical and commercial losses at any point in the network.

Specification Energy Audit

Require Respon Comme

Functionality Description Criticality
ment ID se nts
The system must collect energy flow
data from the metering module. The
Collection of manual entry of data should not be
C/
energy flow data allowed except in the exceptional
Ea.1 Vital ER/F/
from metering circumstances. The same can be
CR/ NC
module allowed only by system administrator
after approval of CEO or persons
authorized for this purpose.
The module should have a graphical
network diagram indicating schematics
of each substation, all connected
transformers, outgoing feeders, DTs,
all switches and connected meters.
Based on the input from field, operator
should be able to modify the switch
Provision of position to represent reconfigured
graphical network network. The time of carrying out such
Ea.2 diagram and operation shall be informed by field Essential
network staff.
reconfiguration
If the SCADA is in place the input for
switch position should come from
SCADA automatically. From the
condition of switches, the system
should be able to understand the
power flow logic at any given point of
time

With the help of Integration with

System Meter data acquisition module,
Calculation of Bus the system should be able to check
bar and energy balance between HV side and
Ea.3 transformation Vital
LV side of any Sub station to ensure all
losses in the sub the meters are working properly and
station can calculate bus bar losses and
transformation losses in the substation.

Page 31 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

The system should be able to balance

11 KV feeder flow against consumption
Calculation of HT of HT consumers and DTs in the feeder
Ea.4 Vital
losses through integration with System Meter
data acquisition module, thereby
finding HT losses and DT losses.

The system should be able to add

consumptions of all the consumers
connected to a particular DT and the
Ea.5 Calculation of DT consumptions of all the DTs in an 11 KV
Vital
losses feeder. The necessary data for this
regard will be available from the
Customer indexing and asset coding
database and billing data base.
In case of change in power flow logic
due to network reconfiguration the
system should be able to regroup the
DTs / 11KV Feeders based on changed
Provision of network configuration. The energy
Network consumption data at the time of
Ea.6 reconfiguration in network reconfiguration should be Vital
case of change in recorded by system for energy
power flow logic accounting. In case meters are not
recording on line data the consumption
data of the meters recorded closest to
the reconfiguration time should be
taken for consideration.

With the help of Integration with

Network Analysis module, the system
Calculation of
Ea.7 should have be able to calculate the
technical losses in Essential
technical losses in the system from
the system
the power flow data and network data
available in the system.

The system should be able to calculate

the estimated technical losses and
Calculation of
segregate the commercial losses in
estimated
Ea.8 every part of the network via
technical and Vital
integration with Network analysis
commercial losses
module, GIS based indexing and asset
in the system
mapping and computerized Billing
System.

Page 32 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

It should store the energy audit data of

each month for a period of 5 years.
The system should able to generate
Generation of report of energy accounting indicating
Ea.9 report of energy areas where high technical losses and
Essential
accounting and high commercial losses are taking
graphical analysis place.
The system should be able to generate
graphical analysis of losses over a
period.

The system should have intelligent

Features of
Ea.10 data analysis feature to detect possible
intelligent data Essential
malpractices by comparing previous
analysis
statistics of consumption.

Page 33 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

3.0 Module New Connection

Objective: The proposed system would aim at enhancing the convenience of the customer, when an application for
new connection is received. It would enable the customer to collect and submit applications through a host of delivery
channels, allow application status tracking etc. The system would help reduce the time taken for the new connection
process. The system would enable updating customer data to be captured in the GIS based customer indexing database
in a reliable way. The data entered at this stage would form the basis of the customer's record in the system. The
system would ensure, through validation and checks, that the integrity of this data is maintained.

System Boundary From : Issue of Application To : New Connection confirmation, Temporary Connection, Load
Extension/Reduction, Name Change and Meter Shifting etc.

Specification New Connection

Requirement Criticality Response Comments

Functionality Description
ID
The system should be able to generate
and issue different application forms for
New connection, Temporary connection,
Standardized Load extension/reduction, Name change,
C/ ER/F/
NC1. formats and issue meter shifting etc. for different categories Vital Standard
CR/ NC
of form of users, and the same forms should be
available across all delivery channels
(Section/ division/ circle/ corporate office/
customer service center, over the web
etc).
The system should be able to accept the
form over the web and the system should
trigger the CRM module to generate a bill
inclusive of the registration fee and
request the customer to make a payment at
one of the Utility’s collection centers before C/ ER/F/
Accepting Vital Standard
NC2. a specified date. The system should also be CR/ NC
application form
able to accept forms at customer care center
and manual / automatic input (through
scanner and OCR software) of customer data
from application forms. System should check
before accepting a form that all mandatory
details as mentioned in the forms are filled.

The system should be able to record the

registration fee payment details and issue a
receipt to the customer. The payments of
Accepting registration fees may also be accepted C/ ER/F/
NC3. registration fee through secure on line payment gateways Desirable Standard
CR/ NC
details over the web using latest version of SSL and
in such cases receipt and application no will
be displayed on the customer browser and
the same will be emailed to customer.

Page 34 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Generation of The system should generate a unique C/ ER/F/

NC4. unique application application number for every application Vital Standard
CR/ NC
no form received and registered.

All registration fee details captured should

Reconciliation of be reconciled with the collections for the C/ ER/F/
NC5. Essential Standard
collection day via integration with MBC system. CR/ NC

The system should be capable of capturing C/ ER/F/

Accepting Vital Standard
NC6. the details of the customer from the CR/ NC
customer details
Application form.

The system should accept the customer

details and then check the applicant's
particulars against the set of existing
customers, defaulted customers,
disconnected and rejected applications. In
Checking customer
NC7. case of a match in records, an exception Essential
details
should be raised. This exception should be
flagged off to the relevant approving
authority. After clearance from approving
authority, the application will be processed
further or the same will be rejected.

The system should, based on a minimum set

of data requirements and approvals specified
Handle special by the utility, accept applications fulfilling
NC8. Desirable
drives the new connections or load enhancement
need posed by special connection/
regularization drives.

The system should be able to assess the load

for each applicant based on the predefined
standards and validate the customer's self-
assessment of load. The system should also
have provision to accept installation test
report of Licensed electrical contractor and
to consider the load mentioned as the
Checking system sanctioned load as per SERC regulations.
NC9. capability for During the verification process, the Vital
issuing connection system shall also validate the current load
on the relevant transformer, whether
additional capacity is available. This
information is maintained in a separate
server (GIS based customer index and
asset coding data base) The system
should be able to provide a list of
exceptions where the self-assessment

Page 35 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

The system should provide the

functionality of generating an intimation
Inspection report letter to the customer informing him of the
NC10. Desirable
generation customer premise inspection. The
corresponding section office would also
be informed of the premise inspection.
The system should be able to define area-
wise standards based on the customer
database for the area and a predefined logic.
For instance, based on the applicant's
NC11. Generate Standard Desirable
locality, category and applicant details
(premise floor area). The system should
provide the flexibility of modifying the
business logic that drives the standards.

The system should have the flexibility of

Waiver of bypassing the premise inspection
NC12. Essential
inspection requirements for customer below a
particular connected load.

The system should accept the customer load

details, the category assigned etc. from the
section officer, once the field test has been
Accept inspection performed and add these to the customer
NC13. report and capture database. It should also facilitate to capture Essential
all details the information regarding customer’s
planning to provide the service line himself
etc, so that the development charges can be
adjusted to reflect the same.

The system should be able to prepare an

estimate for new connection, temporary
connection, load extension/reduction,
shifting of meter and / or service line with
details as per utility defined criteria which
may change from time to time. The system
Estimate should be able to estimate the development
NC14. Desirable
preparation cost after field inspection and the cost data
provided by the utility. This database will be
modified by the utility from time to time. In
case of availability of on line stores and
materials management module, system
should be able to check materials availability
and generate exceptions accordingly.

The system should update the applicant log

Updating
NC15. with his status (Accepted / Rejected / under Essential
application status
process).

Page 36 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

In case the application is rejected, the

Generating system should generate a dues settlement
NC16. Desirable
rejection letter statement, and print a cheque for dispatch
to the applicant.

When the Service Order for the' New

Connection Approval, Temporary
Generation of bill connection, Load extension/reduction,
NC17. for issuing new Name change, meter shifting etc. is Vital
connection generated, the system should trigger the
billing module to generate a bill inclusive
of the development charges and security
deposit.
The system will generate an intimation letter
informing him the bill amount etc. and last
date of payment and will be sent to
Generation of consumer by post, through email wherever
NC18. Essential
intimation letter available or any other information channels.
E-mails should be sent automatically by the
system and printed bills shall be dispatched
by the Utility's staff.

The system should also have the flexibility of

Multiple contract storing multiple contract formats (between
NC19. Essential
formats the utility and the customer) catering to the
different customer categories.
The system should have the facility for the
Case by Case
user to specify a standard contract and make
NC20. modifications to Desirable
modifications to the same on a case to case
the contract
basis.
In response to the Service Order for new
Accepting testing connection installation, the test report
NC21. details should be entered into the system as Desirable
details
a confirmation of the connection
installation.
The system should have the provision of
accepting the number of meters available (of
predefined types) through interface with
online store management module (if
Interfacing with
NC22. implemented in future) and the business Desirable
stores for meters
logic to allocate them. Based on this, the
system can allocate meters to customers. In
case of non availability, system should be
able to generate exception.
Based on the allocation and the service
Route plan and levels defined, the system should be able to
NC23. monitoring of provide meter installation route plan. System Desirable
Meter installation should also monitor installation report of the
meters.

Page 37 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

System should monitor generation of first bill

Generation of first
NC24. of the consumer and raise exceptions after Vital
bill
pre determined period.

After approval of the application form for

new connection / temporary connection, the
system should generate a unique Service
Connection Number ("SCN") for the customer.
The logic for generating SCN shall be
provided by the utility. The system may has
to interface with GIS based consumer index
Generation of database for generating SCN. This number
unique service would form the basis of all transactions by
NC25. vital
connection the customer under his account with the
number Utility. The service connection no. and the
entire customer detail shall be first updated
in GIS based indexing database before issue
of service order for new connection /
temporary connection. Similar updation of
GIS database shall be done for other cases
like load extension/reduction, name change
etc.

This module shall be integrated with GIS

database and GIS based network
analysis module for allowing a new
connection for the purpose of checking
the network capability for adding
additional load, the necessity for capacity
augmentation and for generating work
order with material requirement. At the
Integration with time of adding a new customer the
NC26. GIS and updation updation of GIS data base is mandatory. Vital
of database The system should have the provision for
tagging connections to the property i.e.
identifying all connections in the same
building/ plot/premises, along with
indication of their share of built up area. The
tagging of connection with property should
be superimposed on GIS maps to facilitate
accurate dues transfer and facilitate site
survey.

Page 38 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

4.0 Module : Disconnection & Dismantling

Objective: Recovery improvement and improvement in collection efficiency. The system should aim at
improving recovery through a disciplined disconnection and dismantling mechanism that would serve as
a deterrent for defaulters. This shall also provide updated information to CRM.

Specification : Disconnection, Dismantling & Details of Revenue related matters.

Requir
Criticalit Commen
ement Functionality Description Response
y ts
ID

System should be capable of generating

the list of defaulting consumers i.e. the
consumers who do not make payment of
their bills by the due date or the date on
Generation of which list is generated, which ever is later. C/ ER/F/
Dis.1 defaulting Vital
System should be capable to accept report CR/ NC
consumer list
of action taken on such consumers and
remind further action required to be taken
during specified period as decided by
Utility.

System should have the provision of

generating automatically list of
disconnection notices as per utility defined
criteria in utility defined template. After
expiry of due date of disconnection notice,
it should print disconnection advise for
disconnection by field staff. The utility
defined criteria may :
Exclude cases with open complaints in
customer care module
Generation of Classify live and disconnected cases in
Dis.2 disconnection separate buckets Vital
list Prioritize cases based on default
amount, aging of debt, tariff category,
category of consumer etc.
On receiving the disconnection notice, if
any customer approaches and requests for
help like getting some more time for
payment, then the system should have
provision for payment extensions or
accepting payment in installments.

Process of The system shall have provision of

Dis.3
dispatching dispatching the disconnection notices to

Page 39 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

disconnection the consumers by post, through email

notices wherever available or any other
information channels. E-mails should be
sent automatically by the system and
printed notices shall be dispatched by the
utility’s staff.
The system should capture the reason for
non disconnection from amongst the
Capturing of reasons predefined by the Utility from
Non time to time.
Dis.4 Essential
disconnection System should also have provisions for
reasons maintaining (Adding/ Updating/Deleting)
non-disconnection reasons to designated
persons.
The system should recognize payment
received on real time basis and shall be
able to raise exceptions accordingly, so
that the field staff can be informed on
payments made after the disconnection list
has been generated, to avoid unnecessary
Creation of trips to the customer premises.
exception Desirabl
Dis.5
report on e
disconnection System should also have provision for such
cases, where the field staff receives the
payment (Cash/ Cheque) from the
customer while visiting customer premise
for disconnection and update the
disconnection status or call the designated
person to update the same.
Updation of The system should be able to provide
Dis.6 customer updates on the customer status – Vital
status disconnected / dismantled / live.
Updation of
dismantlemen The system should be able to update the
t status for dismantlement status, triggering an
Dis.7 Vital
deduction automatic deduction from the security
from SD on deposit of the customer.
auto

The dismantlement information should be

Linkage with
available to the new connection approval
New
Dis.8 process, so that dismantled customers are Essential
Connection
not provided new connections till the dues
module
have been cleared.

Tracking and The system should be able to track reasons

escalation of for failure of disconnection/dismantlement
Dis.9 Vital
disconnection and escalate the case to a user-defined
failures higher authority.
Generation of The system should be able to generate the Desirabl
Dis.10
optimal route optimal route and plan for dismantlement, e

Page 40 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

and plan such that the people, transport asset

(vehicles) and meters utilization are
optimized. The system should be capable
of accepting business logic to take care of
such optimization.
In case a customer requests for
termination of connection, the system
Termination
Dis.11 should accept the terminating meter Essential
of connection
reading (which will be out of cycle in most
cases) for generating the last bill.

The system should be able to provide

Integration information to the materials management
Desirabl
Dis.12 with MM function, on the meters that have been
e
system rendered available because of
dismantlement.

This module shall be integrated with GIS

Integration
database and updating of GIS database is
Dis.13 with GIS Vital
mandatory in case of dismantling of
database
existing customer.

Exception
The module shall generate exception, if
reports on
the disconnected consumers not paying the
Dis.14 payment by Essential
dues after disconnection within a period
disconnected
specified by utility.
consumers

Transfer of The system shall have provisions to

dues from one transfer dues from one connection to other
Desirabl
Dis.15 connection to connection(s) including transfer of dues of
e
other disconnected connections to other live
connection(s) connections of same owner.

The disconnection notice would be sent to

consumers in all the specified channels and
Dis. Notice Desirabl
must also be sent through SMS (text
16 through SMS messaging) in case the mobile number of e
the consumer is registered.

Page 41 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

5.0 Module: GIS based customer indexing and asset mapping

Requirem Resp Comme
Functionality Description Criticality
ent ID onse nts
G.1.0 INTRODUCTION

Geographic Information System solution consists

of a system for capturing, storing, checking,
integrating, manipulating, analyzing and
displaying geo data related to positions on the
Earth's surface and data related to attributes of
the entities/Customers in an utility area. It
pertains to both vector and raster GIS. The use
of capabilities includes hardware, software and
data, provided by a Geographic Information C/
System specific to a set of user requirements. ER/F
G1.1 GIS Solution Vital /
This is achieved through GIS mapping to pre- CR/
defined scale, generation of intelligence NC
electrical network maps and super imposing
them on the land base GIS maps and through
customization and / or development of
application software.
The electical network should include the entire
network from SUBSTATIONS, HT line,
Distribution transformers, LT line pillars and
consumers wherever implied.

G.2.0 System Software supply & Installation

Supply and installation of all the software such

as GIS software system, Internet mapping
G.2.1 GIS Software software, drawing software etc and necessary Vital
customization. The RDBMS procured for data
centre may be used for GIS system.
The GIS application package shall work in
OGC LAN/WAN/Internet/Intranet
Compliance environment. Any standard software of GIS of
G.2.2 Vital
Of GIS international repute, registered with OGC
software (Open Geospatial Consortium) as compliant
products shall be used.
Versioning
G.2.3 Capability of Software must have capability of versioning. Vital
Software
Relationship
Software must have dynamic capability to
G.2.4 establishing Essential
establish relationship between the entities.
capability

Page 42 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Non-fatal errors or warnings : This would

include incorrect phasing assigned by users,
incorrect new line connectivity or incorrect
conductor assignment. When new facilities are
added, validation tables should exist to check
G.2.5 Data Validation the data entry against predefined parameters Vital
unique to the item being added, resulting in
correct and consistent data entry. Additionally
warnings should be generated when new facilities
are placed in conflict with pre-established rules
of connectivity as part of user customization.

The application should capture errors with

respect to connectivity and database integrity.
G.2.6 Error Listing Essential
Additionally the application should allow users to
view a listing of the errors that have occurred.

It shall be the responsibility of the bidder for

integration/interfacing with the existing
applications. Also the single window interface
for GIS software and the existing applications
Integration (requiring interface/ interaction / data
Capability of exchange
G.2.7 GIS software with the GIS software) shall be provided with Vital
with existing proper security levels. The desired
modules modifications in the underlying database of
existing system software / GIS software should
be possible through this single window
interface. The bidder shall make necessary
arrangements to provide such kind of interface.

Data model for data conversion : GIS

Application Architecture should provide a
framework and the necessary programming
interfaces to enable complex GIS applications
GIS
to be developed and integrated with
Application
G.2.8 applications that already exist within the Vital
Architecture-
utility. GIS Application Architecture should
Features
support the distribution of the functionality of
GIS application across no. of components which
interacts as separate process via process
communication and control mechanism.

Page 43 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Create Single Line Diagram(SLDs) of electrical

sub transmission network starting from 66
kV/33 KV bus of EHV sub station including 66
kV/33 KV feeders, 66/33/11 KV sub stations
GIS-Software- (with internals), 11 KV feeders up to 11/ 0.4 KV
G.2.9 SLD creation DT, LT feeders and LT poles. It should be Vital
feature possible to print/view the SLD of all or selected
voltage level for desired distribution centers/
division/ circle. The electical network should
include Substations , HT line, Distribution
transformers, LT line pillars and consumers.

FEATURES AND CAPABILITIES OF SOFTWARE

G.3.0
SYSTEM

G.3.1 Generic Specifications

Open Architecture and COM Compliant :
The application supports a fully extensible
GIS Software- Component Object Model (COM) or Enterprise
G.3.1.1 Architecture Entity Bean (EJB) or any other open standards Vital
Type architecture - compliant programming
environment for customization and to have an
open architecture system.
GIS Engine-
Capability to
work in all The GIS Spatial Data Engine should work on all
G.3.1.2 industry industry standard Cross-Platform support such as Vital
standard Windows/Unix/Linux.
cross-
platforms
Proven Imaging Software System Platform :
The GIS Imaging software package with
latest version, and spatial data base engine
with reputed developers such as Oracle/MS
Compliance of
SQL/MY SQL/DB2/Informix/Sybase or any other
G.3.1.3 GIS Imaging Vital
RDBMS confirming to ANSI/ISO SQL-200n
Software
standards with latest version supplied shall
have to be Open GIS consortium (OGC)
registered compliant product time tested,
widely deployed at multiple utilities worldwide
Custom
The application supports an integrated
Functionality
G.3.1.4 customization environment to change the Ul and Essential
addition to
to add custom functionality, programmatically.
application
Software
The system shall provide support in the form of a
based
documented interface specification (API) to
G.3.1.5 functionality Vital
allow software based functionality extensions, or
extensions to
integration with other products to be achieved.
application

Page 44 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

G.3.2 Database Management

Unique no. Customer Identification Number : The system

Allocation shall be capable of allocating a unique
G.3.2.1 Essential
capability of identification number known as Customer
Software Identification Number (CIN) to each Customer.
Functionality The system should have functionality to PAN the
G.3.2.2 Desirable
to PAN display display across the screen.
Provision for linking and maintaining records :
Provision for Provision shall be made for linking and
linking maintaining records (in Registers/ Ledgers) of
customer data the Utility Customer number as parameter,
to ledgers existing before implementation/adoption of
G.3.2.3 Vital
maintained the Customer indexing work under this
prior to specification. This shall be one of the
Customer relational data from archive of UTILITY
Indexing record, to be listed by the system.

Customer Database edit : The database shall

be flexible for making changes in the Customer
Customer
profile as required. The changes may be
Database
G.3.2.4 Customer name, location, connected load, Vital
editing
category of connection, maximum demand,
flexibility
type of connection (HT/LT), and tariff related
information.
Sorting &
Sorting and viewing electrical area or
viewing
G.3.2.5 feeder/administrative area wise Customer Vital
capability of
details should be possible on request.
any area
Creating changes in the Customer and
network entity attributes in relation to
Database addition/ deletion of network entities, record
G.3.2.6 editing of new Customer connections/ disconnections Vital
flexibility in response to other business process like
billing and revenue system in geo database of
GIS system.
Color graphic displays and Color Coding :
The database shall generate color graphic
displays of the system network which can be
Color Graphic zoomed in / out. This shall represent each of
Display of the elements in the electrical system with
G.3.2.7 Vital
System suitable differing colors for the elements. The
Network colour coding will be based on the rated
voltage, Percentage of voltage at each bus,
Percentage of loading of section, Symbols or
any other chosen parameters by user.

Page 45 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Geographical attributes query : It shall be

Geographic possible to query the geographical attributes
Attributes of a specified location, preferably clicking on
G.3.2.8 Vital
Query in GIS to the location or objects of interest and
software examining the contents of the database for
the location of object.

Dynamic Dynamic selection of attributes : User should

Attribute be able to dynamically select one or more of
G.3.2.9 query of any the attributes of an object, to be displayed Vital
object in GIS as label of the object. This can be for
software viewing, plotting and printing purposes.

Representatio Colors based attributes : System should

n of objects in support representation of the Entities/
G.3.2.10 Vital
different Objects/Elements in different colors based on
colors the attribute criterion.
Dimensioning The system should have Dimensioning
G.3.2.11 Vital
Capabilities Capabilities
Moving,
System should be able to perform move, copy,
G.3.2.12 copying Essential
rotate, mirror and offset.
capabilities
Real length
System should specify the real time
G.3.2.13 specifying Essential
measurement / length while drawing the lines.
capability
capability to Restoration of views / workspace / layouts :
G.3.2.14 save & restore System should be able to save and restore Essential
views/layouts views / workspace / layouts.
Entry / editing configuration on specific
workstation : The graphical and textual data
capability to entry/editing shall be configured on specific
G.3.2.15 edit graphical workstation. The system shall allow facility to Essential
& textual data allow configuration of levels of security,
whereby access and modification rights are
appropriately assigned.
capability to Details of Customers : It shall be possible to
provide get a view of the details of the Customer or
G.3.2.16 customer Customers connected to particular distribution Essential
details DT transformer in a list form using a pointing
wise device.
Menu driven Customers query : It shall be
capability to
possible to zoom in / out on a particular
provide query
Customer to obtain the desired degree of
regarding
G.3.2.17 information. Menus shall be provided for
customers in Essential
viewing various combination of information
relation to
related to any group of Customers. For
power supply
example, it shall be possible to view only the
network
list of commercial Customers fed from a

Page 46 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

particular feeder. Similarly electrical

equipment parameters shall also be possible to
be viewed.
Dynamic configuration : The graphic user
Dynamic
interface shall have a modular structure with
Configuration
G.3.2.18 main menus and sub-menus that allow users Essential
capability of
to dynamically configure their own user
system
interface to required level.
Dynamic switching over from one mode of
view to the other : It shall be possible to
view the system elements such as Customer
Dynamic mode
location etc on, mapping and indexing work.
changeover
G.3.2.19 It shall be dynamically possible to switch Essential
capability of
from one mode of view to the other by use of
system
a pointing device. It shall be possible to view
the physical system details in the background
of the area maps created.
Application Administration : Database
Security : The data management system
incorporates mechanisms to ensure data
Database integrity, security and distribution as well as
security to retain historical information. The
G.3.2.20 Vital
provisions in databases shall have password protections
system with varying degree of access definable
by the administrator. The security shall
be adequate considering web-enabled
usage.
Provision of
Version Management of the data - Changes /
version
G.3.2.21 updates made to the base line drawing should Essential
management
be tracked as different versions.
of Data
Managing conflicts :
 Be able to see the latest drawing on the
system which should be union of all the
Provision of
changes made by all of the users/multiple
G.3.2.22 multi-tiered Essential
users at same time on single work order
architecture
and manage conflicts arising due to the
merge / post of different versions.
 Have multi-Tiered Architecture.

System to support the Enterprise wise

System central database and remote users over the
capability of WAN : System should be able to support the
G.3.2.23 being Enterprise wise/Circle wise central database Vital
operated and remote users over the WAN even for the
through WAN creation and editing operations without
degrading the performance over the net.

Page 47 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

System Support seamless data access between

capability of appllications, which allow information in
G.3.2.24 supporting existing systems to be used without a need for Essential
seamless data migration or translation, ensuring a maximum
access return on existing investment.

Facility of representing technical data of the

internals of system entity : The proposed
system should have facility of representing
technical data of the internals of system entity.
System
For example, with a click of mouse on the
capability of
substation user should be able to see internals
representing
of the sub station and on taking the pointing
G.3.2.25 technical data Essential
device to a Power Transformer, a 'pull down'
of internals of
menu to show user options such as Tech. data,
any system
connectivity data or maintenance record data
entity
to be displayed on request. The internals
visible on clicking on the substation should be
dynamic in nature and not merely static snap-
shots.

The application should provide a data model

specific for electric utilities. Bidder is
requested to provide, along with
Electric Utility
documentation as part of their proposed
G.3.2.26 specific data Essential
system, a database schema that facilitates data
model
access via queries and new applications. A
utility data model is an advantage and would
help realize the data warehouse concept.

The data model should also be customizable to

Electric Utility incorporate the user specific needs. UTILITY
G.3.2.27 user specific should also provide the final data model to Essential
data model other parties for the purpose of interface
development or building new applications.

Import / Export of data : The software should

Data
have the capability to import/export both data
import/Export
G.3.2.28 and graphical information in wide variety of Essential
capability of
formats (e.g. Access, Excel, DXF, DWG, MID,
GIS software
Geo-Tiff, Jpeg, MIF, TAB, E000, and DGN )

Data export
The system must support export of data into
G.3.2.29 capability into Essential
XML format.
XML format

Ability to
System should support Customer master data,
G.3.2.30 support Vital
Customer billing data, DGPS data to create
Customer Data
network.

Page 48 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Capability to
import Import of satellite imagery in different
G.3.2.31 Vital
Satellite formats like Geo Tiff, JPEG etc.
Imagery Data
The software should have the ability to
import and display both color and multiple
capability for gray scale raster images. Transparency of the
importing & image should be user controllable to allow for
G.3.2.32 Vital
displaying color viewing items regardless of drawing
raster images priorities. The importable raster files formats
should be of the same types listed in the
previous requirement.
Capability for Opening / attachment of standard format
opening / files for schematic representation without
attaching importing into the mapping system : Should be
standard able to open / attach all standard format
G.3.2.33 format files files like Visio, Power Point, Excel, DWG etc. Vital
without for Schematic representation without
importing to importing into the mapping system. All existing
mapping manual/cad drawings for all sub-stations to be
system attached as soft copy.
Supporting multiple / complex SQL queries :
Capability to
G.3.2.34 System should provide query builder and
provide query Essential
support multiple / complex SQL queries.
builder
capability to
support Should support Sorting, Filtering and
G.3.2.35
sorting display records in Tabular/ Browser formats. Essential
/filtering of
records
capability to Should be able to save the queries as well as the
G.3.2.36 save queries in output in text format. Essential
text format
Highlighting
On Query, the system should be able to highlight
capability of
G.3.2.37 the objects based on the user specified boundary Essential
user specified
or attributes for visualization.
attributes
capability to System should support the easy web enabling of
G.3.2.38 support web the application. Essential
enablement
capability to Store and manage CAD and GIS data in a single
G.3.2.39 store CAD & repository. Essential
GIS data
capability to Support automated spatial and attribute data
G.3.2.40 support data entry validation. Essential
validation
Capability to
Translate vector and raster geospatial data sets
translate
G.3.2.41 from a variety of standard and nonstandard Essential
geospatial
projections and datums.
data sets

Page 49 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Updation of
RDBMS Automatically or manually update RDBMS
G.3.2.42 attribute data attribute data when spatial changes are made. Essential
on spatial
changes
Capability to Support for distributed databases within
support flexible, scalable, multi-tiered, partitionable
G.3.2.43 Essential
distributed architecture.
databases
The system shall be able to be configured to
add additional asset types and to modify
existing definitions of assets, such as the
Capability to
addition of additional attributes, without the
G.3.2.44 modify asset Essential
need to involve the software vendor. Such
data
configuration is to be achieved using Data
Dictionary style tools and not require re-
compilation of the software.
System
availability Report runs and any other batch jobs should not
G.3.2.45 Essential
due to report affect system availability.
run
G.3.3 Spatial database features
Database support : All Industry standard
capability to
RDBMS should be supported viz. Oracle/MS
support all
G.3.3.1 SQL/MY SQL/DB2/Informix/Sybase or any other Essential
industry std.
RDBMS confirming to ANSI/ISO SQL-200n
RDBMS
standards.
Database portability : Each Table or layer
Database
G.3.3.2 should be independently exported to a file and Essential
portability
restored into supplied database.
Schema portability : In an enterprise-wide
GIS, there may be different groups working on
the same datasets at remote locations. To
Multipoint
enable them to work on this dataset, one
G.3.3.3 editing Essential
should be able to port the owner's schema to
permissibility
the remote database, let them edit the
dataset and then bring back the changes after
some time interval.
capability to
store Additional data types : User should be able
G.3.3.4 Essential
additional data to store custom objects, dimensions.
type
Published API’s Published APIs : Software must have published
for interface free java and C APIs and development tools
G.3.3.5 Essential
to master for custom development and interface to
database master database.
capability to Support for direct editing of spatial data in the
G.3.3.6 support direct DBMS including multiple user editing with long Essential
editing of transactions and advanced rule-based editing

Page 50 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

spatial data with GIS Client.

capability to
serve Serving the Database directly to the
database Internet Mapping Server and desktops should
directly to be possible without any conversion. Map server
G.3.3.7 Essential
internet can upload a configurable amount of data to the
mapping users workstation based on different pre-
server & defined situations / network load.
desktops
Capability to
Should support network topology,
support
G.3.3.8 versioning, long transactions. It should also Essential
network
handle version conflicts.
topology
Capability to Should support raster images and other
support raster raster operations (mosaic, catalog, editing)
G.3.3.9 Essential
images & support for – Rasters, Native Cad entities,
operations Annotations, Database & Versioning.
Capability to
The ability to view and browse for maps in the
enable map
G.3.3.10 contents of folders and databases is supported. Essential
browsing in
folders & DB
Capability to
Map data and table data can be previewed.
G.3.3.11 preview map & Essential
table data
Capability to Object Linking and Embedding database (OLE
G.3.3.12 Essential
support OLE DB DB) providers is supported.
Capability to
The application provides the ability to manage
G.3.3.13 manage data Essential
data sources and database connections.
sources
Capability to
manage The application supports the ability to define
G.3.3.14 Essential
coordinate and manage coordinate systems.
systems
Ability to
create & The application provides the ability to create
G.3.3.15 Essential
maintain and maintain metadata and store as XML data.
metadata
The data management system provides spatial-
Capability of
indexing (i.e. a method of breaking down the
DMS to provide
G.3.3.16 master file by allocating each map an index in Essential
spatial-
order to decrease the screen refresh and data
indexing
access times.
Capability of
The data management system allows users to
DMS to permit
choose between managing features on an
G.3.3.17 users to Desirable
individual feature basis (user-specified features)
manage
or grouped by a logical selection.
features

Page 51 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Capability to
CASE tools are supported.
G.3.3.18 support CASE Desirable
tools
Ability to
The application provides the ability to generate
generate
schemas for objects in UML using the CASE tools
G.3.3.19 schemes for Desirable
subsystem.
objects in UML
using CASE
G.3.4 CORE GIS FUNCTIONALITIES
Core GIS Engine : The Electric Utility GIS
Desktop software should be built on top
Core GIS
G.3.4.1 industry standard core GIS Engine having Vital
Engine specs.
the following
functionalities :
Create layers from all supported data sources
Layer Creation including coverage feature classes; shape files;
G.3.4.2 capability of computer-aided design, TIN, raster, and geo Vital
GIS software database feature classes; or tables containing
x,y coordinates.
Group Layer Create group layers from multiple data sources
G.3.4.3
creation including vector overlays on top of raster data/ Vital
capability images.
Layer storage The application should allow users to define and
G.3.4.4 capability of save various user specified views, for example Vital
GIS software by storing collections of layers.
Preset Layer
The system should allow preset layer
G.3.4.5 configuration Essential
configurations for specific plotting applications.
permissibility
Intelligent Intelligent layering capabilities. Ability to show
G.3.4.6 layering only certain layers at a given scale and for a Essential
capabilities given condition (i.e. type of service call).
Manual
Manual Layering capabilities. Ability for the
G.3.4.7 layering Essential
operator to turn Layers on and off at will.
capabilities
Data Data Preview : Should provide facility to
G.3.4.8 previewing preview the data before Loading. Drag & Drop Essential
capability layer from the preview window to the map.
Report Generation : The software should
have inbuilt industry standard Reports
Generation tool both at Server and Desktops.
Report  Facility to display Aerial, Projection and
Surface distances.
G.3.4.9 Generation Essential
 Feature Labeling : Should have the
capability facility to label features based upon
fields or expression of two or more fields.
 Registration, rectification & storage of
Raster and Vector data in a single

Page 52 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

database must be possible.

 Must support Topological-editing
capabilities.
 Defining rules for Topology like rules to
make sure that no polygon overlaps another
polygon in the same data, polygons should
form a continuous surface with no voids or
gaps, lines in a data should connect to one
another, dangling and pseudo nodes
removal
Create Bookmarks: Facility to Create, Edit
Bookmark
and Move To Bookmarks. Bookmarks will be
G.3.4.10 creating Essential
created to store the information of the display
capability
Extents of the map.
Spatial Spatial querying engine that can retrieve
G.3.4.11 querying specific features based upon a user determined Vital
engine facility buffer zone around a point, line, or polygon.
The amount of data that initially appears on the
Configurability screen should be configurable. This includes the
G.3.4.12 Essential
of screen data geographic extent as well as the richness of the
data.
Transparenc
When user workstation requests additional
y of data to
G.3.4.13 data from the server, this should be Essential
user when
transparent to the user.
queried
Availability
of out of box Out of the box tool for geo-positioning based
G.3.4.14 tool for on software operator initialized address Essential
addressing queries.
queries.
Software
ability to Point and Click access to data (static objects as
G.3.4.15 enable point & well as moving objects). Essential
click access to
data
Clients :
This can be proposed from a wide variety of
capability to
clients from out-of-the-box browser-based
adopt to
G.3.4.16 clients to full-featured ArcGIS clients, or can be Essential
variety of
customized or built using HTML, DHTML, ASP,
clients
JSP, Java, Cold Fusion, or other standard web
development tools.
System
Cluttering and decluttering - The application
ability to
should have facility of cluttering and
perform
decluttering The process of showing more
G.3.4.17 cluttering & Essential
details as users zooms in is called cluttering
decluttering
and process of hiding details as user zooms out
of data
is called decluttering
details

Page 53 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Edge matching - This system shall have the

edge matching facility since edges may not
Image Edge match, whenever two images or two networks
matching are joined together. For E.g.: If two maps of
G.3.4.18 Essential
facility in network are scanned and a line running is
GIS software across two images, the ends of line cannot
exactly match. Edge mapping is achieved by a
snap of two ends or joining of two ends.
The software must :
 Support full connectivity of all electrical
capability to
circuit elements and devices.
provide logical
 Provide logical circuit connectivity
circuit
G.3.4.19 techniques that insure proper hierarchy of Essential
connectivity to
line section and device connectivity. This
ensure
should ensure that incompatible line types
compatibility
or devices cannot be directly connected in a
circuit.
Authorization Software should allow an authorized user to
to modify switch the position of a device, thus modifying Essential
G.3.4.20
directional the directional connectivity of the affected
connectivity conductor.

The electric utility geo database can contain 50

or more feature classes, each of which is
represented as a layer. Users will have a number
Software of standard views or displays, a display being a
capability to distinct combination of map layers and layer
create & store rendering properties. Individually changing
Essential
G.3.4.21 standard properties of each of the 50 layers to configure a
displays at new display could be tedious and error-prone.
system & user Hence the software should store these standard
level displays in the RDBMS so that any user who logs
in the system can choose the most suitable
display. It should be possible to create and store
these displays at system and user level.

G.3.5 NETWORK MANAGEMENT

This module shall have the following
G.3.5.1 Functionalities Vital
functionalities -
a) Create a new network
b) Open an existing network
c) Merging of two networks
d) Cut and paste part of the network
Display a partial network of the area of the
e)
interest
f) Delete a network

Page 54 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

The application provides the ability to create,

Abilities of maintain and save a geometric network using
G.3.5.2 Vital
Network Mgmt. designated features or by adding features to an
empty geometric network.
The application can create and maintain flow
Abilities of
G.3.5.3 direction in a geometric network based on the Vital
Network Mgmt.
current configuration of sources and sinks.
The application supports tracing operations to
Abilities of
G.3.5.4 perform complex network analysis functions Vital
Network Mgmt.
within a utility network.
Abilities of The application can create, maintain and save
G.3.5.5 Vital
Network Mgmt. flags or starting points for trace operations.
Abilities of The application can create, maintain and save
G.3.5.6 Vital
Network Mgmt. barriers for use in trace operations.
The ability to disable features and layers to
Abilities of
G.3.5.7 create a more permanent barrier for tracing at Vital
Network Mgmt.
a particular location shall be supported.
Abilities of Customized trace results can be created,
G.3.5.8 Vital
Network Mgmt. maintained, and saved.
Network
The ability to perform network analysis along
G.3.5.9 analysis Vital
with the display of its result shall be supported.
functionality
User capability
to connect/ The user should be able to disconnect and
G.3.5.10 disconnect a reconnect a network feature. Essential
network
feature
Network The system defines different network
G.3.5.11 impedance impedance criteria to support analysis at Essential
criterion different times of the day.
The system allows for the tracing of networks to
Tracing of
G.3.5.12 identify land parcels or customer information Essential
network
affected by network interruptions.
Export of
The system allows the export of network
network
G.3.5.13 analysis product to third party modeling Essential
analysis
packages.
product
Network topology processor : The module
Capability of shall have the facility to identify the objects
network in a feeder and the feeders of a substation for
G.3.5.14 Essential
mgmt. purpose of color coding etc The module shall
module have capability of displaying hanging sections
and loops in distribution networks.
Handling network problems : GIS must be
Capability of
capable to handle network problems, such as
GIS to handle
G.3.5.15 road network analysis, which facilitate Essential
network
evaluation of the shortest path between two
problems
points.

Page 55 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

G.3.5.16 Tracking Changes -

Proper relationships shall be established in the

database between the various entities. Further,
hierarchical relationships should be established
between various elements to link and group them
at any voltage level. It should be possible to change
System the hierarchical parent of any element i.e. any
G.[Link] capability to element along with all its children in a hierarchical Essential
track changes relationship can be made child of any other
element. Such shifting should be possible only
where voltage levels match. The time of making
such changes shall be tracked. This arrangement
should enable rearrange entity relationships with
time stamping.

The energy accounting software supported by the

Customer indexed database shall be able to
recognize the transfer of any group of Customers
fed by any particular line to any other
neighborhood / alternate line by switching of
System isolators or modification of jumpers during the
capability to operation, for the purpose of improving the
provide availability of supply. To facilitate the above, all
information switching devices in the system shall be properly
G.[Link] Vital
regarding identified in the database. Such changes may also
manual or be effected due to system modifications such as
automatic addition of a new distribution transformer or
switching additional line or a new substation etc. The
software system shall provide user-friendly screens
for inputting the information for all manual
switching operation carried out. The software shall
also be capable of recognizing any automatic
switching wherever provided at a later date.

System ability
The database shall keep track of all such changes
to keep track of
in any of the Customer attributes such as change
G.3.5.17 changes in Vital
in name, connected load, tariff category,
customer
connection status, meter changes etc.
attributes

Affected Customers/ Areas : Software should

System ability have standard tools to find out affected customers
to provide in case of an outage. This must allow finding
information affected Customers/ areas in case of an outage or
regarding as a result of switching operation. The user shall
G.3.5.18 Vital
outage get the affected Customers / areas by placing a
affected flag at the point of outage.
customers/ Outage data to be obtained from scada load centre
areas wherever there is an existing provision for SCADA
else else meter data acquisition system and other
applications.

Page 56 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Software
Switching & Looped Network: The software must
capability to
support switching operations and recognize the
support
G.3.5.19 status of the downstream network based on the Essential
switching opns.
switch position, on or off. The software must also
& looped
support looped network in GIS.
network
System ability QA/QC of GIS Data: The application should have
to perform tools to perform QA/QC on the data created. The
G.3.5.20 Essential
QA/QC on data software must be rule based. These rules should be
created configurable to suit UTILITY requirements.

The QA/QC tool must perform QA/QC for all sub

G.3.5.21
sections based on the following :

Attribute level QA/QC as per the domains defined

Attribute level
a) for the particular attribute: e.g. user cannot enter Essential
QA/QC
an incorrect voltage level and chooses from a drop
down list of voltages
Connectivity Connectivity rules e.g. a 3 phase tap cannot
b) Essential
rule-QA/QC be taken from a single phase line.
Relationship Relationship rules e.g. a PMT transformer can
c) Essential
rule-QA/QC be placed on top of a pole only.
Contingent
Contingent validity rules : A set of valid values
d) Validity Rule- Essential
that depend on the value of another attribute.
QA/QC

User's custom validation rules

Customer The QA/QC functions shall have the feature to
e) Validation save the report/ result of the QA/QC and the Essential
Rule-QA/QC tools should also provide with the error
messages information to help user correct the
errors.

Locator Tool : The application must have a

locator tool to find specific entities and
Availability of
automatically zoom to the same. It must also be
G.3.5.22 locator tool in Essential
able to find all specified entities within a
GIS System
certain radius by inputting the radius and the
X, Y coordinates. It must also be able to
locate tie devices in a specified feeder.
Location
Location Display : Facility to display a given
G.3.5.23 Display Essential
location when the location code or object code
facility in GIS
or latitude/longitude are specified.

Location Tracking : The system shall keep

Location
track of the location in the network from
G.3.5.24 Tracking Essential
where a particular Customer is fed. This shall
facility in GIS
be achieved in conjunction with the network
data created for the utility area.

Page 57 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Allow modeling of composite objects :

Placement of multiple objects at a single click
is enabled by composite objects. An example
System ability
of the same can be a switch box / LT panel
to permit
containing internal bus bars, switches, fuses etc.
G.3.5.25 composite Essential
Once the composite object is modeled with all
object
its constituent entities, it can be placed on the
modeling
map by a single click whenever required. This
saves the effort of placing every entity all the
time.
Allow defining Templates : These are models
that define the behavior of the software to be
controlled while editing the network. Say a
template for LT service can be defined to in
such a manner that it places a Tap on the main
System line and places a service line on the first click,
G.3.5.26 permissibility places a fuse on the second click on the Essential
for templates service line, a meter on the service line on
the third click and ends the service line on the
meter. This also helps save time and effort of
the utility officials by eliminating the need of
picking each entity and keying in the attributes
of the same.
Creation of Favorites & Mass attribute
G.3.5.27
updates :

System The system should allow creation of Favorites.

permissibility These would be entities that are created from
G.[Link] Essential
for creation of the complete generic library of models having
favorites predefined attributes.
System ability
The system must allow saving of Favorites
to save
organize and save attribute values of
Favorites &
G.[Link] often-used features. The system must also Essential
allow mass
allow mass attribute updates. This would help
attributes
user in speeding up data creation.
update
Display : System must allow storing
predefined display of layout and symbology.
The symbology should be as per UTILITY
System
standards. For the purpose of day to day work
permissibility
and display/query, it must be possible for
G.3.5.28 of storing Essential
users to change symbology of elements on the
predefined
fly without changing the database. E.g. to
layout display
display 50KVA transformers due for oil
change in the next three months in a different
colour/ symbol etc.

Page 58 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Digitization of
DIGITIZATION OF ELECTRICAL AND LAND BASE
G.3.6 electrical Vital
SYMBOLS
symbols
The digitization module shall have the following
functionalities :
Desktop
G.3.6.1 Desktop functionalities Vital
functionalities
The application requires that information
a)
(metadata) be stored about a map.
The application supports a customizable
b)
graphical user interface.
The user will be able to create hyperlinks to any
c) document or URL and store the hyperlinks with
data in an attribute field.
The application can save a map in a thumbnail
d)
image.
The application can store data using different
e)
paths.
The application can create, store and maintain
f)
map templates.
The system can store true 3-D features (X, Y & Z
g)
coordinates).
Display
G.3.6.2 Display Properties Vital
properties
The application requires the use of specified
a)
projections.
b) A variety of data sources can be displayed.
The application supports the ability to set
c)
background and symbols.
The application supports the manipulation of
d)
symbols.
The application supports the ability to label
e)
layers.
The application supports the display of TIN
f)
datasets.
Interaction
G.3.6.3 Interaction Tools Vital
tools
Provide a list of map interaction tool supported
a)
by the application.
b) Describe the application's hot linking capabilities.
The application supports the ability to locate
c)
features.
The user should be able to create and save spatial
d)
bookmarks.
The application provides the ability to control
e)
map drawing.
f) The application should provide a magnifier

Page 59 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

window that can be changed to any desired

percentage and represent the magnified view as a
snapshot.
The application can create an overview window
g) which can be resized and moved such that it
affects the active data frame.
The GIS software displays the results of attribute
queries in graphic format. This may include
h)
graphics for a single record or an entire query
result. Zoom to selected features.
Vector data
G.3.6.4 Vector Data Vital
display
The application supports the ability to label
a)
definition and position
The application provides a display threshold for
b)
vector layers
c) Allows user to focus on an area of interest.
d) Tool tips can be created for toolbar buttons.
e) Selections can be customized.
The application provides the ability to manipulate
f)
map features.
A definition filter based on an SQL expression can
g)
be set up.
Raster data
G.3.6.5 Raster Data Vital
display
a) The extent of raster image can be set.
Image brightness, contrast, and transparency can
b)
be changed.
The application provides for re-sampling for
c) geometric transformations and for converting
grids to other resolutions.
Data query
G.3.6.6 Data Query Vital
properties
The application can query data using a number of
a)
different expressions.
The application allows query expressions to be
b)
saved and loaded.
The query language supports querying against a
c) set of features, which are the result of executing
a previous query.
The system allows features be selected for data
editing in the following ways : Geographic
d)
window; Selection by mouse; Selection by SQL
query.
The NOT qualifier can be applied to any spatial
e)
operator.
Query results are displayed or plotted in user-
f)
defined symbology.
g) Query results can be easily formatted in a

Page 60 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

report. The report writer has a forms-driven user

interface for the interactive definition and
formatting of the report.
Symbol related
G.3.6.7 Symbology Vital
properties

a) The user can assign values to attributes (scaling).

b) The application supports symbol classification.
c) The application supports color ramps for symbols.
d) The application supports label text.
The application supports the ability to perform
e)
statistics.
Interactive map symbol display capabilities are
f)
provided.
The application supports transparency function of
g)
attributes.
The application provides capabilities for symbol
h)
management.
i) The application supports symbol stretches.
The application provides ability to adjust
j)
brightness, contrast and transparency.
The user can predefine feature characteristics,
such as line style, weight, color, symbol and
k)
angle, for features and text for the system to use
as a default when displaying features.

l) Display attribute-based symbology.

Symbol Editing
G.3.6.8 & management Symbol Editing and Management Vital
prop
a) The user can create templates and map series.
The application provides TrueType font support.
b)

c) The application supports EMF and BMP formats.

d) The application provides symbol-editing support.
The application provides the ability to create and
e)
edit symbols.
f) The application supports gradient fills.
The map production system generates point
symbols based on any attribute associated with a
g) point. The software supports a variety of point
symbols, including both system default and user-
specified symbols.
The map production system generates line
h) symbols based on any attribute associated with a
line. The software supports a variety of line

Page 61 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

symbols, including more complex line symbols

and the custom creation of user-defined line
styles (including color, pattern and width).
The map production system generates polygon
shade symbols based on any attribute associated
with a polygon. The software supports a variety
i)
of shade characteristics for each polygon shade
symbol, such as shade line colors, angles,
patterns, line widths and separations.
Labeling
G.3.6.9 Automatic Labeling Vital
properties
a) Conflict detection is provided.
The application supports labeling of multiple
b)
layers.
c) Interactive text can be placed on a map.
The application supports annotation stored with
d) a map as a group or stored separately in a file
or database.
The application supports feature linked
e)
annotation.
The application allows users to position and
f) orient labels and graphics in a data frame or
position map elements on the layout.
g) Supports transparency layers.
h) The application supports predefined label styles.
Support is provided for label display of a subset
i)
of features.
j) The application supports symbols as labels.
k) Labels can be stored in a graphic layer.
l) Manual placement of feature labels is supported.
The system shall allow for scaleable fonts that
m) allow changes to font type, height, width, color,
etc.
The system shall support multiple lines of text
with full justification options available.
Justification options include, top left, top
n)
center, top right, center left center, center
right, bottom left, bottom center, and bottom
right.
Graphic
G.3.6.10 Graphics Vital
properties
a) The application supports text as graphics.
b) Different graphic shapes are supported.
c) Graphic editing is supported.
The application supports graphic placement and
d)
manipulation.
Moving, rotating, and ordering graphics is
e)
supported.

Page 62 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Feature Editing
G.3.6.11 Feature Editing Vital
properties
a) The application supports feature editing.
b) New features can be created.
The creation of features at an x, y coordinate
c)
location is supported.
Features at a specified length or angle can be
d)
created.
The application supports the creation of
e)
segments using angles from existing segments.
f) True curves can be created.
The application supports copying a line at a
g)
specified interval.
The application supports creation of a buffer
h)
around a specific feature.
Mirror images can be created from existing
i)
features.
Merging features from the same layer into one
j)
feature are supported.
The application supports combining features from
k)
different layers into one feature.
The application supports the creation of a feature
l)
from features with common areas.
m) A new polygon with shared parts can be created.
The application supports the ability to modify
n)
existing shapes.
o) Splitting a line or polygon is supported.
The application supports trimming a line, line
p)
extensions, flipping a line.
The application supports the modification of
q)
existing features.
The application provides support of topological
r)
editing capabilities.
A comprehensive snapping environment is
s)
supported.
t) Copying and pasting attributes are supported.
Relationships between features and attributes
u)
can be created.
v) Validation rules are supported.
w) The application provides digitizer support.
x) Undo/Redo framework is supported.
The application supports a fully customizable
y)
editing environment.
When entering new data, the system displays a
listing of features types to be selected, while
z)
automatically setting layer, attribution and
symbology.
The system allows attribute data to be
aa) interactively entered or edited using default
field values (such as ownership) or user-defined

Page 63 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

values at the time of entry (such as by equipment

identification number).
The system provides domains (pre-defined listings
bb) of valid values for a particular attribute) for
graphic/ attribute integrity checking.
The system can automatically update attribute
values based upon changes to a feature's
cc) geometry, changes to other attributes, or the
creation of a new feature, thus ensuring
database integrity.
The system supports the manipulation of sets of
dd) features, such as deleting, moving, querying and
updating attributes.
The system supports the interactive merging of
ee) two identified lines with and without an attribute
comparison
Checking for geometric connectivity :
The system supports the interactive editing of
topological edges and nodes, allowing vertices to
ff)
be added, deleted, or moved on an edge (an
edge, shared by two features, that is modified
allows both features to share the modification).
The system provides "heads-up" digitizing
capabilities, including the ability to load raster
gg) and vector data as a background on the screen
over which vector graphics can be traced using the
cursor.
The digitizing process includes interactive rubber
hh) sheeting, as well as the ability to snap to points
during placement and editing.
Digitizing allows for key-in by coordinate
ii)
geometry
The system allows the user to place construction
jj)
points / lines when placing elements.
The system supports "on-the-fly" digitizing
kk) techniques, such as line following and attribution
during digitizing.
The system allows for the automatic generation
of points :
- At the midpoint of a feature;
- At the endpoint of a feature;
- Projected (and vertex-inserted) onto a
ll) feature;
- Perpendicular to and from a feature;
- At a distance along a feature;
- At a distance from a given point in a given
direction;
- At the centroid of an area feature
The system supports the development of
mm)
specialized feature placement methods (e.g. pole

Page 64 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

bisecting a corner and street offset from a kerb

line)
Data
G.3.6.12 formatting Data Formats Vital
properties
Bidder should list the vector formats supported
a)
and editable by the proposed solution.
Bidder should list the raster formats supported by
b)
the proposed solution.
Bidder should list the formats in which the
c)
product can export data.
The proposed GIS allows data to be input from the
following sources : Hardcopy maps; Digital
d)
coordinate ASCII files; Batch processing (to load
attribute data).
The system allows ASCII data (both coordinate
and attribute information) to be loaded as
e) features, which are optionally linked to attribute
records. An interface for ASCII format definition,
modification and loading is provided.
Table
G.3.6.13 Management Table Management Vital
properties
The application provides the ability to view data
a)
in a table.
The application supports table data selection and
b)
editing.
Aliases can be defined in tables.
c)
d) Field values can be calculated.
The application provides the ability to find and
e)
replace functions in tables.
The application provides the ability to freeze
f)
columns during display.
Chart
G.3.6.14 Charts Vital
properties
Bidder should list the different chart formats the
a)
application supports.
b) Graphics and charts should be editable
Buffer Analysis
G.3.6.15 Buffer Analysis Essential
Properties
The application provides the ability to create
a)
buffers.
b) The ability to output buffers is supported.
Spatial Analysis
G.3.6.16 Spatial Analysis Vital
properties
a) Data can be merged and joined.

Page 65 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Data mgmt.
G.3.6.17 /compilation Data Management/ Compilation tools Vital
tool
Data compilation tools for using data that is
a)
obtained in multiple formats
Projection Management Tools to standardize data
b)
from multiple projections.
Boundary creation tool. Need the ability to
clump areas together from different layers (I.e.
c) counties, zip codes) and create one area/polygon
on a new layer with its own attributes. Also
require manual boundary modification tools.
Geocoding Tool for objects based on street
d)
addresses.

Page Templates define and store standard map

page elements to retrieve later. A page template
defines the size, orientation, and map elements
capability to for a standard map. Similar to a template for a
support Page word processing document that defines the styles
G.3.6.18 Essential
Template and format, a template saves time and repetition
properties by storing elements used on every map. These
then can be used for printing.
The application should support creation of above-
mentioned feature at system as well as user level.
The software should have utility tools to navigate
large map documents quickly by finding,
highlighting, and moving features. It should
support tools like:
Utility tools for
a) Locator tool
G.3.6.19 navigating Essential
b) Copy
large maps
c) Quick Attribute viewer
d) Delete
e) Highlight
f) Pan Zoom to Etc
Feeder Manager : The application must have a
feeder manager to manage and trace specific
feeders and must have the following capabilities
:
 Help generate circuit map for a desired
Feeder Manager feeder
G.3.6.20 properties in  Help locate all features or tie devices Essential
software associated with a feeder
 Select features belonging to a particular
feeder or group
 Show feeder information graphically in a
map display (loops, islands, and double
feeds or extra feeds)

Page 66 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

 To assign energized phase information to

each feature in a circuit indicating by
name (R, Y, or B) the phases of electric
power that can reach the feature from
the power source(s) for the circuit.
Work flow manager : to manage the work flow
Work Flow related to the complete design process / cycle
G.3.6.21 Manager (from design, approved, released for Essential
properties construction, construction complete to
commissioned).
capability for Schematic Lay out of compound objects –The
Schematic module shall have capability to blow up
G.3.6.22 layout of compound objects like substation, DT, feeder Essential
compound pole, LT pole etc showing single line diagram of
objects arrangement.

Pole Code Generation -This module shall have

the capability to generate code for poles on a
feeder as per user-defined format. The typical
examples are 11 kV pole coding comprising
Pole Code substation code / substation name, feeder code,
G.3.6.23 Generation serial no of pole which can be continuous or Essential
facility varying on basis of laterals and sub laterals. –
e.g. The 33kV cables are laid at 3 ft depth, 11 kV
at 2 ft depth and LV cables are laid at 1 ft depth.
It should be possible the no of cables at each
depth and configuration of the trench etc.
New symbol/ The user should be able to create any new
G.3.6.24 Essential
attribute symbol and also specify its attributes.
There shall not be any limitation on the
number of symbols or the number of
attributes for a symbol. Attributes
Symbol/attrib associated to each of the entity/object
G.3.6.25 Essential
ute limitation /element should be user definable like Data
type, Lengths as per record of SEB, Access
restriction, Pull down list and Mandatory /
Optional.
customized Customized representation of
representation entities/objects/elements: System should
G.3.6.26 of entities/ allow the user to customize the Essential
objects/ representation for each of entities/objects/
elements elements.
a) Point
b) Line
c) Polygon
d) Text
e) Color
f) Hash pattern
g) Line style (Dashed, Dotted...)

Page 67 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

h) Font
Point shape (Round, square, user defined...)
i)
The attributes can be text; Number;
Type Of
G.3.6.27 reference of AutoCAD Drawing, Raster image, Essential
attributes
Photograph, etc.
The software shall be customized to provide the
electrical symbols given in Annexure-D of
Section: G6 and land based features given in
Software
Annexure-E of Section: G6. The attributes to
customization
be shown are also listed in the Annexure-E. As
G.3.6.28 for electrical Essential
already stated, whenever user wants, he can
symbols & land
add any number of attributes to a symbol
based features
and also create any number of new
symbols. This capability should be
demonstrated at the time of demo.
Capture of all Capability to capture all the attributes,
attributes while digitizing each symbol as specified by
G.3.6.29 Essential
while data dictionary, through a user friendly dialog
digitizing box.
The system should support automatic scaling of
Support of graphics. Based on defaults and parameters set
automatic by the user, the software should have the ability
G.3.6.30 Essential
scaling of to manage inserted symbol size, so that it is
graphics displayed at a consistent size throughout any
level of zoom scale.
Creation of As and when each symbol is digitized the
G.3.6.31 spatial attribute database, the spatial database Essential
database should get created instantaneously.
Layer
G.3.6.32 specifying Capability to specify layers, while digitizing. Essential
ability
System On completion of digitization, the system
G.3.6.33 readiness after should be ready for studies without any further Essential
digitiztion interventions.
Support raster
G.3.6.34 Support raster Images / scanned photographs. Essential
images
Multi Circuit Representation
On a pole or a tower, more than one OH line
may be running. These lines may be
Multi circuit different voltages or same voltages. The
G.3.6.35 Essential
Representation application program should provide for
digitizing and display of these multi circuit
lines. On clicking of multi circuit line, the
configuration of Line shall be displayed.
Multi cable representation
Number of cables running in the same duct
Multi-cable or footpath is more common compared to
G.3.6.36 Essential
representation OH lines. The application shall have the
facility to display these cables and show also
the configuration how these cable are laid.

Page 68 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

On clicking, cross section of trench shall be

shown showing arrangements of cable.
Land Base Representation : The land base
shall be made intelligent. Various queries
shall be made available for different entities in
a land base area of UTILITY power network
Land base premises. Each entity will contain a minimum
G.3.6.37 representatio of five to six attributes to carry the basic Essential
n information like Name, Address,
Circle/Div/Sub-div/DC, Service Number,
Telephone Number, etc. The software shall be
able to build the topology on its own to ease
this query process through the intelligence.
Substation Representation : Substation is a
building or out-door area location where
Representatio various electrical accessories are connected
n of Sub- together to
G.3.6.38 station serve the load centers. Following are the Essential
Electrical electrical equipment in a substation, which
Components are normally installed and electrically
connected :
a) High Voltage Cables/ Conductors
b) Circuit Breaker
c) Isolators
d) Transformers
e) Protective Relays
f) Feeder Energy meters
g) Fuse section pillars, LT Boards
h) LV Cable feeders
i) Bus couplers / Bus-Section
Aux. Systems (DG Set, Battery, Charger, UPS
j)
etc)
Display of The land base information shall be displayed
s/stn. on demand by just clicking on the substation
G.3.6.39 Essential
Information on diagram and the complete database of
demand substation shall be displayed.
There shall be user-friendly methods
Acceptance of
available in the software to define and
G.3.6.40 new network Essential
integrate any new network symbols into symbol
symbols
library.
The substation's database should contain the
details like equipment data (Make/Type
/Model/rating plate information, History,
Sub-station
G.3.6.41 Maintenance and Remark etc. These details Essential
Database
shall also have to associate the electrical
accessories details installed in the same
premises.
check of inter The electrical connectivity shall be
G.3.6.42 Essential
connectivity established at all times between substations

Page 69 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

between or from any nodes. It shall be linked so that

substations the connectivity shall be checked at all times
through the logical checks, which is being
performed by the software internally.
It shall be possible to edit the associated text for
Text Editing
G.3.6.43 its presentation. This shall be achieved for the Essential
Ability
users with the proper security rights.
Placement of During the placement of equipment, it shall
new be possible of being rotated, scaled and
G.3.6.44 equipment in moved about its insertion point. The Essential
geographic placement shall be assisted by a "rubber
maps band" to assure a proper position.
All of the electrical entities and accessories
Identification shall be identified by their name information
G.3.6.45 of electrical of the substation in addition to their Essential
entities in GIS alphanumerical database information of
interest, which is associated with each item.
An interactive tool like icons in a toolbar,
GUI
graphical user interface (GUI) shall be
availability to
available to enable the users to perform their
G.3.6.46 perform Essential
graphics handling operations such as zooming,
graphic
panning, highlighting, selection, clicking an
operations
item for its alphanumerical details etc.
The following information shall be queried
System ability using the user-friendly GUI by just selecting
to provide the category of the query. The results
G.3.6.47 Essential
information shall be made available in the graphics by
using GUI highlighting them and/or in the non-graphical
text report forms.
Connected load information, which is fed from
a)
the substation.
b) List of Customers based on the connected load
History information of load readings of the
c) transformer and outgoing LV distributor cables
etc.
The selection criteria and query of a
substation / transformers / cables / pillars/
G.3.6.48 Query Type joints / ducts/ sleeves / manholes/ AD Essential
pillars/ Capacitors/ Switch Gear etc. may
follow the patterns listed below :
Name of the substation. This will enable to
a)
highlight the selected elements
b) Name of the area of the substation
Display of service numbers of the Customer fed
c)
from the substation
The entities located in the downstream of the
d)
substation

Page 70 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Through a polygon retrieval i.e. selecting a

window area from the overview map, the
e)
software shall highlight and retrieve all the
substation
The software shall highlight the respective
substation by query i.e. substation located
f)
in a particular zone, substations located in a
particular area.
The software shall be able to attach and
retrieve any scanned image, video clips,
g)
sound files or any multi-media clippings to the
substation.
Report
availability on Following reports shall be made available after
G.3.6.49 Essential
non-graphic the non-graphics query :
query
List of substation connected on a particular
a)
Feeder
List of substation based on capacity of
b)
switchgears/ transformers
List of substation based on make of electrical
c)
entities
d) List of substation based on breakdowns
List of substation commissioned during the
e)
specified period.
The software shall be able to compose the
various types of cables with its technical
information like type, material of the
Cable
conductor, cross-section in the network cable
technical
symbol library. The list of cable type shall be
G.3.6.50 information Essential
available in the cable symbol library for
on GIS
selection in advance and for laying purpose in
software
the field. The chosen cable type shall be
displayed always in the geo-client's toolbar
space until the selection is replaced.
Cables and Other Electrical Components
G.3.7
Representation :
During the selection process, there shall be a
provision to set the runtime environment
settings i.e. the geometry of the cable
Cable location e.g. Line, Arc, Tangential Arc, Tangential
G.3.7.1 Essential
information Line and also the type of connection like
'Begin' and 'End'. The distance information
shall be made available to enter in case of
different cable laying path.
G.3.7.2 Availability of All of the functions shall be available in terms Essential

Page 71 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

all functions of menu and/or toolbar icons.

on menu
There shall be a provision to click on the
Accepting existing laid cable in the field by a mouse
G.3.7.3 cable type as button and to accept that cable type as the Essential
current one current one. This enables wherever the
existing cable may be extended or continued.
There shall be some facilities to consider the
Software
cable laying procedures through the rounding
capability to
lines tangentially or by specifying a radius.
G.3.7.4 exhibit cable Essential
Icons shall enable the same. This facility will
paths through
be used wherever the cable-laying route has
obstructions
any obstructions or restricted area.
The software shall have the mechanism to
Facility to
incorporate Loop-In-Loop-Out (LILO) facility in
G.3.7.5 exhibit LILO in Essential
the existing cables. The network node symbol
exiting cables
will be chosen earlier to use the same in LILO.
The software shall include the facility to
compose different types of cable for laying
the multiple feeders at a stretch. The GUI can
GUI facility of be used to make the composition of the type
exhibiting & for multiple feeder cables. The GUI shall
G.3.7.6 editing contain the facility to add, delete the cable Essential
multiple type selection for multiple feeders along with
feeder cables the parameter of line spacing distance and
cable alignment. In addition to this, editing
facility of the individual cable line type shall
be made available.
The software shall carry out the multiple
feeder cable laying procedure through simple
Multiple cable icon clicks. It shall also have the facility to
laying continue existing multiple feeder cables to
G.3.7.7 Essential
procedure on another location. Similarly connecting two
software different multiple lines with proper selection
of individual cables in the multiple feeders
through a rounding way or by an arc.
Edition facility There must be very simple methods available
for cables/ Tr. to establish the edition of a transmission lines
G.3.7.8 Essential
lines in and / or distribution cables. The edition
software could be achieved as listed below :ll
Drawing the two different end points of the
G.[Link] feeder together by just clicking on to the end
points of the feeder
Connecting two different lines at an
G.[Link] intersection point project from the same angle
and direction
G.[Link] Extending a single line by intersecting it with

Page 72 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

another line
Unlinking the positions of the feeder from the
G.[Link]
cable
Linking the positions of the feeder into the
G.[Link]
cable
Moving the line points from a selected position
G.[Link] to a new position through a dragging
mechanism.
Deleting the entire line/multiple line by just
G.[Link] clicking on to the line / multiple line to be
deleted.
Deleting the portion of the line segment
G.[Link] through the identification of the start and end
positions.
Replacing the line designation by selecting a
G.[Link] new line designation. This is nothing but the
"changing the line type" method.
Updating the cable's non-graphical data through
a)
an interactive GUI mask.
Displaying the cable's non-graphical data on to
b)
the graphical space
Software
capability to The software shall be able to check the
G.3.7.9 check electrical network line continuity for the power
Essential
electrical flow through graphical and non-graphical data
continuity for as listed below :
power flow
The electrical line tracing till the end of the
line by considering the switch positions on the
a)
line. The line will have to be highlighted after
the tracing.

By ignoring the switch position conditions, the

b) line shall be traced for its continuity and same
shall be highlighted

By selecting the text attributes attached to a

c)
line, the tracing shall be possible.

d) Through a non-graphical data.

Addition of It shall be possible to insert an electrical
electrical element in to an existing cable. This will split
element in the existing cable into two sections and each
G.3.7.10 Essential
cable followed section's alpha data will be displayed in a mask
by updating of for update. Accordingly the graphical and non-
data graphical data will be updated.
Addition of It shall be possible to insert any of the chosen
G.3.7.11 electrical electrical devices on a multiple feeder cables. Essential
element in For instance, the electrical device will be

Page 73 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

cables connected with all of the lines in the multiple

followed by cables. Similarly, there shall be a provision to
updating of insert the electrical device net point on to
data individual cables in the multiple cable lines.
The other functions shall be made available as
listed below through a simple clicks by mouse
button:
a) Deleting a electrical net point
Replacing a net point. The existing electrical
b) net point will be replaced with the new
electrical net point.
Switching a net point from open to close or vice
c)
versa positions
d) Moving and rotating the net point
e) Scaling up or down of the net point
It shall be possible to update or change the non-
graphic master data of the net point. Any of the
endpoint can be selected by simple mouse clicks
Updating of
and the respective net point's master data
G.3.7.12 non-graphic Essential
should appear in the mask for the new values.
master data
Similarly, there shall be a provision to display
the data based on the selection of the net
points.
The bus bar shall be able to accommodate the
increase in no. of feeder points. It shall be
Graphic possible to redefine the no. of feeder
alteration for entry/exit points in the bus bar to a higher
G.3.7.13 addition of number as per the requirement. The software Essential
feeder points shall internally replace the bus bar with more
in bus bar no. of feeder entry/exit points by retaining the
technical information associated with the bus
bar.
Electrical item
It shall be possible to perform the following
G.3.7.14 editing Essential
tasks in the software.
abilities
Inserting a cable into a station/bus
a)
bar/distribution box
b) Laying a protective pipes on the cable route
c) Laying protective pipes with dimension defined
d) Creating a manhole
Creating a cross section for Trench, Man-hole,
e)
Protective Pipes
f) Defining the cable route
g) Labeling
Electrical item
It shall be possible to insert " cable beneath
G.3.7.15 editing Essential
cable"
abilities
During the insertion of cable, if there is change
Electrical item
between any segment, e.g. if there is change in
G.3.7.16 editing Essential
type of cable between joint J2 and J3, the
abilities
software shall allow the user to edit the same.

Page 74 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Software
capability to After inserting the cable/joint, the software
check shall carry out on-line electrical connectivity
G.3.7.17
electrical establishment checks internally and all related Essential
continuity for databases tables shall be updated
power flow automatically.
after editing
The software shall have facility so that cable of
Error same voltage levels can only be connected with
generation each other, i.e. if by mistake, user connects LV
G.3.7.18 Essential
capability in cable / equipment with HV/EHV
software cable/equipment, the software shall generate
error message.
Software If parts of the cable are running across more
ability to than one sheet, the software shall be able to
G.3.7.19
display carry out merging of the two cables into one Essential
merging of cable. The cable may be redesigned
cables accordingly.
Software
ability to It shall be possible to represent
G.3.7.20 represent cables/switchgears/HV-EHV cables under Essential
cables / existing scenario.
switchgears
Calculation of
length of It shall be possible to calculate the length of
G.3.7.21 upstream or downstream or upstream from the selected Essential
downstream element.
cable
Retrieval of
electrical It shall be possible to retrieve / query the Essential
G.3.7.22
elements elements like cable within the polygon.
within polygon
It shall be possible to split the existing
Splitting of
G.3.7.23 cable/LC for the insertion of new Customer Essential
existing cable
cable / LC.
Tracing of It shall be possible to trace electrical
customer’s connectivity of a Customer. By default, the
G.3.7.24 Essential
electrical connectivity should be traced up to its feeding
connectivity substation/Pole Mounted Transformer (PMT).
Ability to
It shall be possible to attach scanned image of
G.3.7.25 attach scanned Essential
service SKETCH to a particular service number.
drawing
It shall be possible to search and zoom into the
Software
user-defined distance around that service
G.3.7.26 capability to
without any drawing sheet boundaries. The Essential
search & zoom
default distance shall be 100 meter around the
in any drawing
service point.
Project The software shall include the Project
G.3.7.27 Administration Administration features. The software shall Essential
features in enable the facility to address multi-project

Page 75 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

software environment.
The software shall include the Layer
Management features. This function shall
Layer Mgmt. enable to assign descriptions to the layer. The
G.3.7.28 Essential
Features composition of various objects shall be
allocated in unique layers, depending on the
user requirements.
The software shall include the features of Task
Management, by which the geographical data
Task access will be controlled and monitored. This
G.3.7.29 Management feature utilizes the security features Essential
features administered by Data, Project and User
administrators. It should also administer the
interim backup storage, mechanism internally.
Different Different accessing modes of area/ locality
G.3.7.30 accessing shall be possible in the software. Some of Essential
modes of area the modes are listed below :
a) Co-ordinate
b) User specific
c) Area
Map sheet number (Index for the map sheet shall
d)
be created).
e) Polygon or any shape of interest
Automatic creation of relationship between
the network components while creating them.
Creation of Besides that, the system is necessary to have
relationship facilities to generate, store, retrieve,
G.3.7.31 between edit, delete and display information on Essential
network infrastructure assets, Customers through
components proposed system. The system should provide
the facility to plot or print the base map or
facility map to plotter or printer as well.
The application should provide users with the
capability to add multiple features with a
single mouse click i.e. without picking each
Capability to
entity separately. This would help in speeding
create
G.3.7.32 creation of network. For example adding a Essential
multiple
new service to a customer, the application
features easily
should automatically know the set of facilities
to be placed as per the category of the
customer industrial, residential etc)
A stencil with relevant shapes for drawing a
Provision of Single Line Diagram (SLD) will be provided
G.3.7.33 stencil to which will enable the user to create Essential
create SLD a schematic representation of the basic
electrical network.

Page 76 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Zoom in/Zoom out : The user will have option

Zooming to view an area with about 2000 objects
G.3.7.34 facility in (Customers, DTs, Cables, Poles, Junction Essential
drawing Boxes, Etc.) represented on a Visio Interface
and zoom in to sections of the drawing.
The user should be able to define the number
Zoom sensitive
G.3.7.35 of objects displayed at any zoom scale (zoom- Essential
layer control
sensitive layer control).
Connectivity to ODBC data sources : The
Connectivity
objects shown on the interface would be
G.3.7.36 to ODBC data Essential
connected to an ODBC Data source in the back
sources
end.
Drawing schematic electrical network of a
selected area automatically from the database.
System ability
It will be possible for the user to plot the
to draw
G.3.7.37 schematic electrical Essential
automatically
network of a selected area on a blank page in
from database
the interface based upon a selection query on
the database.
Intelligent objects on the diagram showing
data from back-end database on double click.
The objects shown on the interface would be
Software connected to an ODBC Data source in the back
G.3.7.38 ability to end. On double clicking an object in the Essential
exhibit data interface a form would be shown with most
relevant data, there would be options on the
form to drill down and retrieve data in greater
detail.
Pictographic
Pictographically representing assets in the
G.3.7.39 representation Essential
distribution network.
of assets
The stencil provided in the Interface would
have icons to represent constituents of the
electrical network like feeders, Sub Stations,
DTs, Junction Boxes, Cables, Poles and
Stencil
G.3.7.40 Customer Connections etc. These can further Essential
Features
be colour coded to easily identify objects of
similar rating. E.g. User would have an option
to draw all 11 KV feeders in Blue objects on
the Visio drawing can be text labeled.
Showing Equipment status : The interface
would have options to show equipment status.
Equipment e.g. Open and close status of circuit breakers
G.3.7.41 Status Display would be shown in different colours. Switch Essential
facility on GUI position / status to be shown in different
colours in real time based on manual input by
user or through SCADA interface which shall be

Page 77 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

established by the owner at the later stage.

Query on the database and representation of
result data on the schematic diagram. The
GUI ability to
interface would have a query through which
accept query
the user would be able to select information
G.3.7.42 & provide Essential
from the database based upon specified
result data on
parameters. The result set can then be either
diagram
highlighted on the existing network or plotted
on a separate page.
Data Entry by dragging objects onto the map
Data entry
for what-if analysis : The user would have
provision after
options to drag objects from the stencil into
G.3.7.43 dragging Essential
the drawing area and enter data for the object
objects to
in the form and save the data into the
map
backend database.
Printing Printing: Object property data shown in forms
G.3.7.44 capability of should be printed from Visio with the Essential
object data reporting tools.
Ability to find Finding an element on the drawing: It should
G.3.7.45 element on be possible to find and highlight elements on Essential
drawing the drawing through query.
Drawing in parts: It should possible to
Ability to
draw a section of the complete network
G.3.7.46 draw a section Essential
in a separate page from the seamless database
of drawing
and maintaining connectivity between pages.
Software
Representing Internals : The software shall
facility to
G.3.7.47 have facility of representing the internals of Essential
represent
objects like a sub-station.
internals
The software should have industry standard
report creation tools which would allow end
Report users to create new reports with desired
G.3.7.48 Essential
Creation Tools formatting functionalities such as sorting,
filtering & display records in Tabular/
Browser format.
User Friendly interface Network Symbol
Library - The software should accept the user
defined symbology applicable at the UTILITY.
It should be possible to view the same network
Software
with different symbology in different views
ability to
without changing the database, by storing the
G.3.7.49 accept Utility Essential
new display configuration. For example feeder
defined
view where different feeders of voltage level
symbols
shown in different colors, outage view where
live and energized line
segments are displayed in different colors etc.
all without changing the back end database.

Page 78 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

This would allow the users to view the

network as desired by them.
The system should provide an extensive library
Provision of
of utility oriented symbols, allowing possibility
extensive
G.3.7.50 of modification, if required. The system should Essential
library of
also have the facility to create new symbols as
symbols
per client requirements.
G.3.8 Modes Of digitization: The digitization
module shall have the following Capabilities :
Capability to digitize either a single line
Ability to
diagram not to scale or geographical
G.3.8.1 digitize SLD’s Essential
network to scale in user given coordinates
or Global coordinates.
Ability for on Capability for on screen Digitization i.e., to
G.3.8.2
screen digitize freely using a mouse or Essential
digitization a scanned image or satellite imagery.
Multi-user
Capability for multiple users to digitize a single
G.3.8.3 digitization in Essential
network
single network
G.3.9 Validations of Digitization
The application shall provide library of
Provision of validations and facility for user to choose the
G.3.9.1 Library of validations for any symbol existing or added to Essential
validations package. The validations shall be stored in
database as stored procedures.
Typical validations are : Voltage of two
objects / buses to be connected shall be the
Typical same; Voltage of any bus shall be one of
G.3.9.2 Essential
Validations standard voltages defined; the ratings of
equipment shall confirm to standard ratings
defined;
The bidder shall prepare a list of validations
List of
G.3.9.3 proposed for each symbol and take approval of Essential
validations
utility.
G.3.10 LINKAGES AND INTERFACES
Integration with other systems : For
ensuring high level of
Integration interoperability of GIS software with the
Capability of various business process software, open
GIS software GIS standards and OGC
G.3.10.1 Vital
to other Compliant/implemented software shall be
modules in adhered by the bidders. Software should
utility have a ready provision / facility so that the
proposed system can be easily integrated to
the following systems :

Page 79 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

a) SCADA
b) Energy Management System
c) Customer Call Centre
d) Customer Information and Billing System (CIBS)
e) Project management
IEC 61968-1, which is based on an integration
bus approach focusing on integration of major
utility applications relating to distribution
Interface
management.
G.3.10.2 package for Vital
The bidder is responsible to provide the
integration
interface software to Customer Billing
package, SCADA package etc., if existing in the
utility.
Ability to Interface with Analysis Software : The
interface with application shall have the ability to easily
G.3.10.3 Vital
industry std. integrate to industry standard analysis tools
Analysis tools like SynerGEE, CYME etc. using XML.
Specifications for the internet mapping
G.3.11 server to enable the web enabling of the
spatial data -
Cross Platform Cross-platform support : It Should work on all
support of industry standard cross platforms with latest
G.3.11.1 internet versions at the time of bidding, such Windows/ Vital
mapping Unix/Linux.
software
Web server support : Several Web servers
Web Server should be fully supported including Microsoft
support of Internet Information Server, Netscape
G.3.11.2 internet Enterprise Server, Java Server, Apache, SunOne Vital
mapping - Sun Solaris, IBM HTTP Server, WebLogic, etc
software with support of all industry standard servlet
engines : - ServletExec, Tomcat, Jrun, etc.
Scalability &
Easier to install: - Scalable, reliable, more
reliability of
configurable (services across multiple
G.3.11.3 Internet Vital
machines (multi-tier) - in order to achieve
Mapping
faster response and load balancing),
software
Advanced
Advanced cartographic Capability
G.3.11.4 cartographic Vital
Capability
Advanced Advanced client side functionality :
Client side Should support streaming vector data to a
functionalities client Web browser. More functions, such as
G.3.11.5 Vital
of Internet map rendering, spatial selection, and querying,
Mapping should be done in the client Web browser
software without sending requests back to the server.

Page 80 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Integration of
G.3.11.6 local & Should integrate Local and Internet Data. Vital
internet data
Highly Scalable Server Architecture: IMS
Server
should publish GIS services from a single
architecture
G.3.11.7 server or distributes services across multiple Vital
to be highly
servers, which provides for a highly efficient
scaleable
and scalable environment.
IMS capacity The IMS should be specifically designed so
to function that the site will continue to function while
even if new servers and services are added or removed. A
G.3.11.8 Essential
servers are site configuration should be able to save so that
added or it will automatically restart the same
removed configuration.
Printing &
G.3.12 PRINTING & PLOTTING Essential
Plotting
Printing Printing Properties : This module shall have the
G.3.12.1 Essential
Properties following printing facilities :
Print network vector map alone, raster
G.[Link] map alone and network superimposed over
raster.
The user should have the facility to print the
G.[Link]
features required by him.
The user shall have the capability to print the
G.[Link] complete network or a part of the network in a
given size of paper.
The user should be able to print complete or
G.[Link] part of the network on given scale in multiple
sheets of specified size.
The application should support print preview
G.[Link]
feature as well as various drivers.
G.[Link] The application supports PostScript.
The user should have the option for labeling
G.[Link] specific or all the devices or objects of the
network.
Plotting/Printi
Plotting and Printing of graphical areas : The
ng of
G.3.12.2 system should support WYSIWYG Plotting and Essential
graphical
Printing of graphical areas.
areas
Legend, Texts styles in plotting template :
G.[Link] Placement of Own Legend, various Texts styles
in plotting template.
G.[Link] List the supported Plotters and Printers
The system must support : Map insets that
G.[Link]
allow the user to designate a portion of the

Page 81 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

map in a source frame and show a zoomed

version of the source in a destination frame to
enable printing and plotting cluttered areas.
The system should allow Generation of user
defined Map grids, coordinate systems and
preparation of Map-books automatically.
G.[Link]
System should also allow scheduling of plotting
activity. A map grid is a set of map sheets that
can be plotted.
The application should provide users with the
G.[Link] capability to store a map layout for consistent
look and feel during map production.
The system shall support Map Production tools
that allow users to create map books and map
G.[Link]
sets. It shall be possible to schedule the plot /
print of the map books.
The map production system may automatically
G.[Link] orient text (i.e. along the axis as opposed to
horizontally).
The map production system plots labels for point,
line and polygon features using any attribute
G.[Link]
(alpha or numeric). Labels are plotted in a
variety of text fonts, sizes, colors and angles.
The system provides the functionality to
automatically create titles, legends and other
G.[Link]
margin data and store them in templates that are
transportable.
The map production system needs to be able to
G.[Link] create markers and line sizes that vary
automatically by the scale of the map.
The map production system allows the saving of
G.[Link]
layouts and or templates.
The Map production system includes the optional
G.[Link] application of standard drawing frames and
editable title blocks.
G.[Link] Storage of predefined templates for plotting
The system shall support Inset Frame tool that
allows user to display specific features within
current view individually in separate windows.
G.[Link]
For example, user can depict each switching
facility in the Switching Facility layer in its own
inset frame. These are to be plottable.
Report
G.3.13 REPORT GENERATION Essential
generation
This module shall have the facility to print
G.3.13.1
and display the following reports :
Report of assets of complete network or a
G.3.13.2 part of the network say Sub station, Feeder,
Area etc.

Page 82 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Report showing number of objects for a

G.3.13.3 particular symbol with different attribute
data on the basis of selected attribute.
The system should support ability to create
G.3.13.4
reports and report templates.
Bidder should list the report tools available with
G.3.13.5
the proposed solution.
The system is capable of generating reports from
G.3.13.6
the results of batch query sets.
The reports are user-format table and full-page
G.3.13.7
when output to a printer.
Graphic reports can be generated from within the
G.3.13.8
GIS applications software.
Wizard production of charts and reports in all
G.3.13.9
user applications.
Sessions Manager : The application must
provide a Session Manager to
establish and enforce a specific version
structure and user roles. Session Manager
System should create an edit session in which an
capability to editor may make changes. After the changes
G.3.14 provide are complete, the user forwards the session Essential
sessions through an approval process. A session (and its
manager associated version) may travel through the
process several times before receiving
approval and being posted to the geodatabase.
Session Manager allows creating and editing
sessions.
Online help &
G.3.15 online ONLINE HELP & ONLINE TUTORIAL Essential
tutorials
The system should have the facility for online
G.3.15.1
help context based and also on line tutorials.
A query builder to generate adhoc queries by
G.3.15.2 user, who have no skills on SQL Commands,
shall be provided.
Context based and user-friendly help should be
G.3.15.3
available.
Help should be available at different levels :
G.3.15.4
novice, expert etc.

Page 83 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

6.0 Module : GIS based integrated network analysis module

Com
Require Respo
Functionality Description Criticality ment
ment ID nse
s
Na.1.0 General features

The module shall be able to perform several types

of analyses on balanced or unbalanced three-phase,
two-phase and single-phase systems that are C/
Module operated in radial, looped, meshed or mixed ER/F/
Na.1.1 Vital
capability configurations. The system shall be able to create CR/
"what-if" studies and performing simulations to NC
evaluate the impact of modifications to existing
network.

The system shall have functionality for editing,

querying and viewing the electrical system on a GIS
base. Background maps showing city, streets, land
Module
Na.1.2 parcels or annotations can be used to give context Vital
features
to the electrical network. It shall also be possible to
trace and query the electrical connectivity of the
system.

The module should have the capability to perform

the following broad functions related to distribution
system design, analysis and optimization :
i) Creation and editing of network,
ii) Load flow and voltage drop analysis,
iii) Optimization studies like capacitor placement,
network reconfiguration, conductor up-
Broad gradation, express feeder, load balancing and
Na.1.3 Vital
functionality load allocation etc.
iv) Creating extensive “what-if” studies.
v) Fault analysis and protection coordination,
vi) Network design reports, cost estimates,
financial analysis,
vii) Integration with New connection module for
checking the network capability,
augmentation requirement, if any

It shall be possible to do any number of studies

Comprehensive
either sequentially or at random. The package
package and
Na.1.4 should be comprehensive, cover all aspects of Vital
integration
analysis, optimization & designing and should be
with GIS
integrated with GIS package via XML.
Sharing of GIS The package should share the database of the GIS
Na.1.5 Vital
database and should not require a separate database.

Page 84 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

There should be separate modes to maintain

Actual Mode &
Na.1.6 organization precious data - Actual Mode or Real Vital
Analysis Mode
Mode and Analysis mode for any study.

Actual Mode or Real Mode must be the simulation of

the network under subdivision. This type of study is
Na.1.7 Actual Mode Vital
useful for maintaining the real asset data and to
view real network for planning purpose.

In “actual mode” the network must be connected

with subdivision working and updated regularly with
Network in the associated module. Any changes made to the
Na.1.8 Vital
Actual Mode system are recorded and can be further traced.
Since its information is precious to organization and
must be updated through proper channel (i.e.
subdivision or office working).

Editing in In “actual mode” Cut, Paste, Save and Consumer

Na.1.9 Vital
Actual Mode shifting should be allowed but with proper check on
user authenticity.

An analysis mode of network will be such that

whatever ad-hoc changes made to the network for
Na.1.10 Analysis Mode Vital
analysis will not affect the actual
“network/subdivision data”, which represents
actual network propriety of the organization.

In “Analysis mode” Cut, Paste and all editing

Editing in
Na.1.11 options shall be allowed so that user can analyze Vital
Analysis mode
the network with different configurations and
modifications.
System ability
A network / study can be opened (Loaded) either
to analyze with
Na.1.12 whole or in part i.e. user can specify the feeders or Essential
part load on
transformers to be loaded on network.
any feeder
The software should provide for online graphical
Graphical
creation and editing of network topology and data.
representation
Na.1.13 Mosaicing features for large networks shall be Vital
and Mosaicing
provided.
features
Software
The software should be capable of presenting a tree
ability to
view structure of the network-representing root at
Na.1.14 present tree Essential
Sub-division/GSS and successive feeders/
view structure
transformers and LT circuits.
of network
There should be provision to make different backup
Backup copy
Na.1.15 copy for the network. Essential
for network
Password
The software should provide a password protection
protection for
Na.1.16 on important issues like on deleting a study. Vital
important
editions

Page 85 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Merging of two There should be facility to merge two studies in

Na.1.17 Essential
studies order to work in distributed environment.
Up gradation There should be facility for up gradation and
Na.1.18 and expansion expansion without disrupting the earlier studies. Essential
facility
System ability
to export full User can export whole or part of a network to a new
Na.1.19 Essential
or in part study via selecting transformers and feeders.
network
Na.2.0 Modeling capabilities of Network equipments:

Software
capability of The software should be capable of representing
modeling (Modeling) an ‘Electric Distribution Network’, which
Na.2.1 Vital
Electric comprises of various electric equipment, connected
Distribution from each other to generate a distribution system.
Network

The software should be modular in design and

Modular design
should be combined with powerful tools, templates
with powerful
Na.2.2 and libraries for easy input, updation and retrieval / Vital
tools and
sharing of data. The common database shall be
libraries
available to all the users.

The software should provide tools for creation of

Network 3/2/1 phase networks with different voltage levels
creation with with all its entities e.g., generator, bus, substation
Na.2.3 different with different voltage grades, feeder, transformer, Vital
voltage levels motor, capacitor, protective devices, lines with
and all entities different size conductors and cables, loads,
switches etc, with symbols and their technical data.
The information in the system should be available
as single line diagram of the network, schematic
Na.2.4 SLD of network diagram of the substations with facility to access Vital
any or all of the information about equipment or
network with zoom and pan facility.
Any limitation regarding the number of nodes,
Indication of buses, substations, feeders, number of balanced
Na.2.5 Vital
limitations and unbalanced loads, branching on a circuit shall
be clearly indicated.

It should be possible to model the loads as constant

Modeling of
Na.2.6 power loads, constant impedance loads and Essential
loads
constant current loads.
It should provide facility for expanding the standard
library and also creating user specific library of
Creation of symbols, design data, equipment data, operating
Na.2.7 user specific limits and standards, cost data for equipment / Vital
library of data material, cost data for power and energy losses and
necessary data for carrying out economic analysis
for the operating life time of the system.

Page 86 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

The module should allow network modeling for

all types of network elements or assets of
TNEB distribution network [Link]
Buses
Network Feeder as node
modeling of
Section
Na.2.8 various Essential
Tap.
electrical
Circuit Breakers
components
Switches
Capacitors
Series Reactors
Boosters

Network
It should allow modeling the system for
modeling with - Various Conductors (R, X & Amp. Capacity )
various - Various Distribution Transformer
Na.2.9 Essential
electrical - Energy (kWh)
components & - Various Loads (kW & KVAR )
- Demand (kW & KVAR)
parameters

Module
validation The module automatically checks and validates
Na.2.10 Essential
capability network topology and data for errors.

Modeling with The module should provide for accurate modeling of

Power & Substation as well as Distribution transformers. The
Na.2.11 Essential
Distribution software provides a separate canvas for drawing GSS
transformers equipment.

Modeling with Cable & lines can be modeled for Overhead lines,
Na.2.12 cables & overhead, duct or underground cables, Cable joints Essential
overhead lines etc.

Section A section is represented in the network with a line

Na.2.13 representation from a possible parent node plus its physical Essential
in network structure.
The software provides different shapes for different
type of sections like -
Cut-Point
Representation Double-Pole structure
of various Composite line
Na.2.14 Composite double circuit Essential
types of
Double Supply
sections
Four Pole Structure
Six-pole structure
Shapes of each component of network will be
furnished by TNEB during implementation.

Page 87 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Checks while
installing new There should be proper checks provided for all
Na.2.15 sections on types of phase connections while installing a Essential
single/two section.
phase lines
Module ability
to analyze There should be a facility for utility to add and
Na.2.16 Essential
‘spot load’ on analyze “Spot load” onany network asset..
pole
Module to
The point from where the feeder starts has a visible
Na.2.17 display ‘feeder Essential
interface i.e. the ‘Feeder node’.
node’
Feeder There should be restrictions that the feeder can be
Na.2.18 installation installed at either on a load bus of a grid substation Essential
restrictions or on the distribution transformer.
Na.3.0 Analysis features -

The module should have following Analytical

Capability-
Balanced/Unbalanced load flow and voltage
Analytical
Na.3.1 drop Analysis Essential
Modules
Fault Analysis (Symmetrical/ Unsymmetrical)
Optimization of losses
Capacitor Placement
The following analysis results are to be available
Analysis
through graphical interface by “Point and Click”
available
method.
Na.3.2 through Essential
T & D Losses Analysis
graphical
Balanced Analysis
interface
By-phase AnalysisFault Analysis
Na.4.0 Load Flow Analysis and voltage regulation -
The module must have balanced/Unbalanced
Load Flow
Na.4.1 voltage drops and load flow analysis. Essential
Analysis
Ability to
perform
technical User can perform various technical actions on
Na.4.2 Essential
actions on network to have the changed statistics of load flow.
network &
analyze
It should be possible to define / evaluate annual
Defining of LF, load factor and loss load factor from the load
Na.4.3 Essential
LLF duration details obtained from data acquisition
system

Page 88 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

It should be possible to calculate the system and

operating parameters from the data e.g.,
Calculation of calculation of resistance, impedances, susceptances
system and of the lines and cable at different temperatures and
Na.4.4 Essential
operating equivalent impedance of the transformers in case of
parameters parallel operation in a substation. It should be
possible to define the spacing, configuration,
temperature etc.
Provision of The program should provide for at least one slack
Na.4.5 Essential
slack bus bus.
Modeling of
It should be possible to model bulk loads as well as
Na.4.6 bulk and UD Essential
uniformly distributed loads
loads
It should be possible to carry out load flow analysis
of radial, meshed, looped or mixed configuration,
Load flow
3/2/1 phase balanced and unbalanced networks.
capability on
Na.4.7 Provision shall be there for 3 phase 4 wire and 3 Vital
various type of
phase 5 wire system operating at user defined
networks
voltage and parallel operation with different sizes
of conductors / cables
Load flow calculations should give power flows in
Deliverables in
Na.4.8 MW & MVAR, current in each section, load at each Vital
load flow
node, voltage and % voltage regulation at each node
It should give the peak power loss and the energy
Peak power
loss in each line section and the transformation loss
loss and energy
in each transformer. The iron losses and the copper
Na.4.9 loss in each Essential
losses (load losses) should be indicated separately.
section of
It should be possible to use the iron and copper loss
Network
values defined in user created library for the same
Voltage and
component It should also be possible to segregate and get a
Na.4.10 wise summary of the losses voltage level wise and Essential
segregation of component wise for the entire network under study
losses
It should be possible to conduct load flow analysis
Load flow at
for nominal voltages or user defined voltage. It
Na.4.11 varied tap & Vital
should also be possible to conduct load flow analysis
voltage levels
for different tap positions of the transformers
Indication of
The load flow analysis should indicate violation of
Na.4.12 limit of Vital
loading voltage and current limits
violation

Page 89 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

The calculation can be further filtered according to

parameterss like mentioned below and it should be
possible for all distribution assets of TNEB- -
a) Consumers category
Calculations
b) Diversity Factor of individual feeder.
according to
Na.4.13 c) Inclusion of only 3 Phase load (exclusion of Essential
various
single phase load)
parameters
d) Set load according to each LT Feeder, Peak
loading, average loading
e) Set Load according to the DTC full load, part
load, average loading
Considering
The software must include seasonal effects like
Na.4.14 Seasonal Essential
temperature, skin and corona effect.
Effects
The module should allow Allocation of Load by
substation demand by -
Load
Na.4.15 Dividing load in proportion to connected kVA Essential
calculations
Dividing load in proportion to KWH
Include spot loads
The module can calculate and allocate the
Substation Demand among the feeders based on-
KVA and PF
KW and PF
Demand
Na.4.16 KVAR and PF Essential
calculations
KWH, Load Factor and PF
Amps, KVA and PF
KW and KVAR
Diversity factor
The module must provide facilities for Allocation of
Load by Feeder Demand, DT demand, pf etc from
the meter database.
- Divide Load in proportion to KWH / connected
Na.4.17 Load Allocation KW Essential
- KWH parameter shall be updated regularly by
subdivision working.
- New load (consumer) added in the subdivision
is automatically taken into account in load
flow calculations.
Na.5.0 Optimization Studies -
Ability to
support sub- Software shall support Power / Distribution
Na.5.1 Vital
station substation proposal
proposal

Page 90 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Design of
It should be possible to evaluate the design of
support
Na.5.2 distribution feeders to check adequacy of support Vital
strength, strength and statutory clearances.
clearances etc.
It should be possible to evaluate the design of earth
Na.5.3 Earthing design Vital
mats and earth electrodes.
It should be possible to compute, positive sequence,
Computation of
Na.5.4 negative sequence and zero sequence impedances Vital
impedances with and without mutual impedances.
Ability to
It should be possible to determine the number,
support power
Na.5.5 location and size of primary substations required to Vital
transformer meet the growing demand at minimum total cost.
proposal
Ability to
support It shall be possible to generate optimum distribution
Na.5.6 Distribution transformer proposal, new or augmentation over a Vital
transformer selected regions or nodes.
proposal
It should be possible to determine the optimum
Solutions for network configuration for formation of new links to
Na.5.7 line nodes on a existing feeder, tie points for changing Vital
overloading etc feed area from one substation to another to balance
load among substations.
It should propose an express feeder in order to
Creation of overcome irregular overloading of a feeder, to
Na.5.8 Essential
express feeder remove or reduce the Low Voltage Area and to
minimize line losses.
Economic and
It should be possible to determine the economic and
Na.5.9 break-even Vital
break-even loading limits of conductors and cables.
loading limits
The software can propose a new conductor over the
Solutions for
over loaded regions on a feeder to
Na.5.10 conductor Essential
remove/minimize the over loaded region by
problems
suggesting better conductor on the network.
User defining The conductor can be user-defined i.e. user can
of Express force suggest the conductor for express feeder
Na.5.11 Essential
feeder proposal, feeder bifurcation, feeder re-
conductor conductoring etc.
Software alert
The software must warn if poor conductor is chosen
for incorrect
Na.5.12 which is poorer from the existing one in case of re- Essential
conductor
conductoring.
selection
The software must propose optimum reactive
compensation along with sizing, location and
Capacitor
Na.5.13 switching time of capacitor to be installed for Essential
proposal
improvement of voltage profile, minimizing losses
and maximizing the net economic benefits.
User ability to
The unit of each individual capacitor bank installed
Na.5.14 vary capacitor Essential
can be adjusted.
size

Page 91 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Load Balancing The software should provide load-balancing analysis

Na.5.15 Essential
Analysis to minimize losses.
Phase change
The system suggests consumers re-phasing for
Na.5.16 proposal for Essential
minimum losses.
loads
The software must suggest repositioning of a switch
between two feeders to achieve the optimal feeder
Proposal to
configuration, which will minimize losses, improve
reposition
the voltage profile and balance the load between
Na.5.17 switch Essential
feeders. The module can determine the optimal
between two
location of the tie points by suggesting new location
feeders
(addition of switching devices) or recommending
new switching schemes to achieve the objective.
Technical and Software should provide the technical and
commercial feasibility of any technical modification
commercial
Na.5.18 done by user. Such feasibility report shall include Essential
feasibility due the following details. New proposal will be reflected
to any change with different line color and style.
- The feeder statistics like length, power losses,
max voltage drop, power factor, max current
etc. as per the requirement before and after
the proposal.
- List, location, and details of equipment installed
Feasibility and actions performed.
Na.5.19 Report - List of equipment uninstalled due to Essential
Contents replacement
- Approximate cost of equipment installed and
depreciated cost of equipment uninstalled.
- Technical feasibility of the proposal.
- Commercial feasibility of the proposal.
- Pay back period of the proposal
Such summarized analysis can be made more
practical further by putting following constraints -
a) Fixing minimum limit for new transformer
proposed.
Network
analysis based b) Available conductor.
Na.5.20 on certain c) To select only those feeders where VR is above Essential
practical some specified limit.
constraints d) To select only those transformers, where
overloading is above some specified limit.
e) Limit can be fixed for minimum payback period
of each unit of proposals
Connection
The consumer applications for new connections,
feasibility for
Na.5.21 load extension etc. shall be processed to generate Essential
new
connection feasibility report.
application

Page 92 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

The Connection feasibility report shall include

mainly the following details –
a) The Feeder/Transformer statistics like max
voltage drop, max current etc before and after
Contents of the proposal.
connection b) Suggested phase and technical details from tail
Na.5.22 Essential
feasibility end to source end of the feeder subjected .
sheet c) List of equipment to be installed/uninstalled and
technical actions to be taken before release of
new connection or load extension.
d) Final suggestion for new connection like
connection can be released or not.
Check for non
bypass of This application processing is bound to further
Na.5.23 processes of processing. For example, if user tries to bypass the Essential
new process then he can’t generate the SCO or RCO etc.
connections
Network
updating on The actual network updating can be bound to job
Na.5.24 the basis of order process in order to update the original Essential
actual jobs changes to network.
done
The network analysis module shall be able to
calculate the allowable as well as actual technical
losses based upon the power flow data in any part
Calculation of
of the network by linking with the meter data
Technical
Na.5.25 acquisition system and asset mapping database. The Essential
losses in the
result of technical loss analysis shall be used by
network
Energy Audit module to generate detail Energy
accounting and Audit reports as described in detail
in separate module of “Energy Audit”.
Boundary
Condition
The package provides proper mechanism to solve
Conflict
Na.5.26 boundary conditions conflicts of subdivisions and Essential
resolution
work area concept.
through
module
Na.6.0 Fault Analysis -

The software should provide following short circuit

Short circuit analysis.
Na.6.1 analysis - LL Essential
- LLG
feature - SLG
- 3 phase

Page 93 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

The short circuit module shall provide values for

fault currents for different types of fault and also
gives the fault voltage and impedance analysis
Short circuit throughout the network taking into account pre-
Na.6.2 module fault loading condition . A user shall specify any Essential
capability point in the system and the analysis will return fault
values for all points downstream. This helps to
determine fault values for entire feeders if
required.
The analysis algorithm shall take into account any
Short circuit
closed loops in the distribution system and also for
Na.6.3 analysis Essential
the fault infeeds from embedded generation and
algorithm
large motors throughout the system.
Na.7.0 “What if “ studies -

The software should provide extensive “what if”

‘What If’ scenario on all TNEB distribution assets parameters
scenario on eg. --
Na.7.1 - Connected load Essential
certain
- Line Configuration
parameters - Distance
- Conductor/Cable
The module should provide for system study
and analysis of alternate network scenarios
involving cost implications considering the
following options :
System study a)Capacitor placement and sizing
and analysis b)Selective re-conductoring
Na.7.2 Essential
under different c)Selective reconfiguration
scenarios d)Selective rerouting
e)Substation sizing and location
f)Network addition / augmentation by feeders /
new transformers
g) Selective and across the network load variation
There must be a facility to implement “what if”
changes in bulk with following criterion.
- Changes Downward selected node : - This
Software option will change the selected parameter,
facility for downward the selected node (i.e. the change
network will affect all the nodes supplied from this
Na.7.3 node.) Essential
analysis on
“what if” - Downward on 11 kV sections only: - This will
changes in bulk change the parameter for all 11KV section
downward the selected node.
- Upstream from selected section to section no:
- This option enables user to change parameter
for all nodes between two connected nodes.

Page 94 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Making “what These “what if” changes mentioned above can be

Na.7.4 if” changes as made permanent, if required. Essential
permanent
Na.8.0 Protective device co-ordination -

The software shall be able to verify the

coordination of protective devices, the maximum
permitted operating time and the maximum
Protection co- permitted continuous load current.
Na.8.1 Essential
ordination
Its coordination wizard shall be able to suggest
protective device settings / adjustments and
ratings.
The software shall be equipped with an extensive
Protective
database of protective devices and device settings
Na.8.2 device Essential
reports.
database

Na.9.0 User level customization features

Line parameter User can customize the line color, width, style for
Na.9.1 Desirable
customization voltage levels according to his requirements.
Equipment
User can customize the equipment color according
Na.9.2 Color Desirable
to his requirements.
customization
Background
User can customize the background color, display of
Na.9.3 Color Desirable
analysis results and input data information.
customization
User-defined text and other labels can be changed
for following properties :-
Text - Font Name
Na.9.4 Desirable
customization - Font Size
- Font Color
- Font Style
Color assigning One can assign a circuit/ feeder a distinguishable
Na.9.5 Essential
for a circuit color permanently.
Color Editing of The standard color for a feeder can be attained
Na.9.6 Essential
feeder again if required.
Overloaded
User can see the overloaded equipment as blinking
Na.9.7 equipment Essential
with overloaded color.
representation
Complaint
The user must have a facility to view complaints
Na.9.8 Affected node Essential
affected nodes with different color.
representation
Labels loaded on the network can be made invisible
Na.9.9 Label Hiding Desirable
if required.

Page 95 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Change of
parameters Important parameters like tariff of energy (in
Na.9.10 Essential
like tariff of Rupees per unit) can be changed.
energy
The unit system for various parameters envisaged
Na.9.11 Unit system shall be in SI (Metric) units and cost in Indian Essential
Rupees.
User can fix the limit of Over Volt and Under Volt
Fixing voltage
Na.9.12 conditions (Voltage Regulation) according to the Essential
limits
organization regulations.
Storage of Load User can store load flow statistics with different
Na.9.13 Essential
Flow Statistics name and reload them when required further.
Unit Allocation
User can fix the unit of capacitance with which the
Na.9.14 for capacitance Essential
system gives the capacitor proposal.
value
User can fix the unit of section installed by the
Section Unit
Na.9.15 system according to different voltage levels and Essential
allocation
pole type like cut point, double circuit etc.
Na.10.0 Help/Search/Display Features
The software should contain varied range of tool tip
‘Help’ features
Na.10.1 help, with important parameters/ attributes can be Vital
in software
seen with balloon help.
Specifically it should provide following attributes on
balloon help on proper node :
- No of Consumers on a node
Attributes on - Distance of this node from source.
Na.10.2 Essential
balloon help - Load at the pole of different phases R, B, Y.
- Current :- Individual and all 3 phases
- Voltage regulation : Individual and all 3 phases
current
Balloon help to The balloon help must be specific to the type of
Na.10.3 be node node. Essential
specific
Source trace
A source can be traced from the node selected
Na.10.4 ability through Essential
showing it with a different line color.
node
It should provide following views and prints.
View/Print - Remove all nodes upwards.
Na.10.5 Option wrt - Remove all nodes downwards. Essential
nodes - Show All Nodes downward
- Show All Nodes
Node inclusion
These “view changes” must not exclude the nodes
Na.10.6 in ‘View Essential
from calculations.
Changes’

Page 96 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Easy Interface
The network traversing is provided with easy
Na.10.7 for network Essential
interface like “dragging the canvas”.
traversing
Network The network can also be traversed by keyboard
Na.10.8 Traversing by from the selected node in upward and downward Essential
Keyboard directions.
Provision for
Toolbar The toolbars can be removed from screen when not
Na.10.9 Essential
removal when required.
not required
Filtered search
The node searching should be provided with
Na.10.10 for node Essential
systematically filtered search.
tracing
The node search support global as well as Feeder
Node Search
Na.10.11 ID/Feeder Name/Transformer ID/Transformer Essential
Support Logic
Name/ Absolute ID oriented search.
Node search on
A node can be searched for a consumer if consumer
basis of
Na.10.12 information is provided like Essential
customer
Service No. / Account No. etc
information
System ability
A particular or whole network can be set to show
to show
Na.10.13 only junction and terminal nodes while excluding Essential
particular type
carry nodes.
of nodes only
Drawing
Na.10.14 formats in Supports shp, dwg etc. drawing formats. Essential
system
Insertion of GIS Number of GIS Layers can be inserted in the
Na.10.15 layers in network with electrical layer superimposing rest all Essential
network the layer.
Representation
The application shall facilitate a network to be
of different
entered in several different layers. User can have
Na.10.16 voltage levels Essential
different view of Layers like 33KV, 11KV, LT layers
in different
etc.
layers
Identification of area on the map based on the
Area results of data analysis shall be done on various
Na.10.17 identification functions such as commercial functions, billing Essential
on map demand, defaulter concentrations, no of new
connections, load & energy balance etc.

Page 97 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

System allows the user to customize and insert the

graphical elements in the network to represent for
System each of entities/objects/elements.
permissibility Point
for Line
customization Polygon
Na.10.18 Essential
of graphical Text
representation Color
for each Hash pattern
entities Line style
Font
Point shape (Round, square, user defined..)
User can dynamically select one or more of the
attributes of an object, to be displayed as label or
Tool Tip of the object. This can be for viewing,
plotting and printing purposes.
- System supports representation of the
User ability to
structure/object/elements in different colors
dynamically
Na.10.19 based on the certain attribute criterion Essential
select object
- User can display the different layers with
attributes
different scales.
- The software should have dimensioning
capabilities.
- The system gives the real time measurement /
length, while drawing the sections.
System
The system improvement proposals generated by
improvement
the application are not only on cost effective
Na.10.20 proposals Essential
aspects but also involves GIS enabled logic like
generated by
shortest route technically feasible.
system
Feature to tag
The program should provide for feature to
as existing,
Na.10.21 tag/identify/code the equipment / network Essential
new or
component as existing, new , proposed etc.
proposed
Shall control the display of the data on the screen
Pan/zoom
Na.10.22 and allow the user to refresh, pan, zoom in, zoom Essential
features
out, zoom to preset scales etc.
Na.11.0 Editing Features
Controlled It should provide restrictions on all edits
Na.11.1 Editing of modifications on the network including Vital
network adding/editing equipment on the network.
Locking facility It must provide a facility for a super user to lock
Na.11.2 for system some particular studies or backup safe from others Essential
studies via password protection.
Moving/Shifting Users can move/shift a complete circuit downward
Na.11.3 of complete by moving source equipment with proper Essential
circuit validations.
Entry of
For ease of data entry, every probable or default
Na.11.4 probable/ Essential
value should be entered implicitly.
default value

Page 98 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

User
User can change the supply shifting/change in the
Na.11.5 permission to Essential
network.
change supply
The supply change is supported with proper
validation like mismatch in voltages, ring
Validation of
Na.11.6 generation, logical constraints, shunt equipment Essential
Supply Change
,alternate sources of supply and their load
indicationsetc.
Mapping It can properly map composite nodes as one node
Na.11.7 composite same time treating them with different lines Essential
nodes equipment as well as maintaining the inventory.
Software
facility for
The software has facility to put geographical labels
Na.11.8 geographic & Essential
as well as equipment attribute labels on study.
equipment
attribute labels
Label
Na.11.9 These labels can be dedicated to a feeder alone. Essential
Dedication
The software shall allow multiple nodes selection.
Multiple Node
Na.11.10 and alternate sources of supply and their load to be Essential
Selection
indicated.
Node insertion
A node can be inserted between two already
Na.11.11 permissibility Essential
existing nodes irrespective of their order.
by software
Equipment The software shall provide facility to rotate
rotation asymmetric equipment like series equipment like
Na.11.12 Essential
permissibility transformer,
in drawing
Recording of Any significant action performed by user like Supply
Na.11.13 significant change, Switch On/OFF, move, rotate etc. should Essential
actions be recorded.
Retrieval of These actions can be retrieved with repeat history
Na.11.14 Essential
records (Undo).
Saving of The record history (undo record) should persist even
Na.11.15 Essential
Record History after closing a session.
Circuit
A circuit can be rotated from its source with any
Na.11.16 Rotation ability Essential
degree of rotation.
of software
Closure of new
The new nodes, which are added by software at the
nodes on
Na.11.17 time of new proposals/ augmentation should Essential
closing of
automatically vanish on closing of the network.
network
Mapping of The nodes added at the time of proposals or
new nodes with estimate should be mapped with dash or different
Na.11.18 Essential
different lines/ line color/node-id to distinguish them from
colors persistent nodes.
Provision to
remove There must be provisions to remove such temporary
Na.11.19 Essential
temporary equipment automatically as well as forced.
equipment

Page 99 of 212
 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Provision to
To expand any study on further high level there are
supply source
Na.11.20 provisions to supply the source bus with some other Essential
bus with
source.
another source

Selecting/ Any node selected can be deselected deliberately.

Na.11.21 Essential
Deselecting of
node
Querying & Querying and Reporting facility : Other than
Na.12.0 Reporting analyses, software should provide following
facility querying and reporting facility.
Querying & Section -
Na.12.1 Reporting on a) Section parameters individual. Essential
‘Sections’ b) Section consumer detailed/Individual.
Feeder -
a) Feeder parameters individual.
b) Feeder parameter detailed.
c) Feeder parameter summery
Querying &
Na.12.2 Reporting on d) Circuit parameters Graph. Essential
‘Feeders’ - Distance V/s Pole
- Current V/s Load
- Power losses
e) Consumers reports
f) Consumer service lines losses detailed
Transformer -
Querying &
a) Transformer parameters individual Static.
Na.12.3 Reporting on Essential
‘Transformers’ b) Transformer parameters individual (dynamic )
c) Consumers reports (User filtered/customized)
Substation -
Querying & a) Substation design print schematic
Na.12.4 Reporting on b) Substation inventory summery Essential
‘Sub-stations’ c) Subdivision level consumers report (User
filtered/customized
Na.13.0 Printing and Plotting

It should provide facility to view and print Network

directly from tree view of the network without
actually loading the study as :-
Network
a) LT Maps only
Na.13.1 Printout from Essential
b) LT Maps with 11 KV
tree view
c) 11 KV Map with LT
d) 11 KV Map
e) Whole study Map

Page 100 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Generation of
various There should be facility for generation of various
summary / summary / individual reports for example feeder
Na.13.2 Essential
individual wise, transformer wise, voltage level wise,
reports zone/area wise, consumer category wise etc.

Abnormal
condition Abnormal condition reports for sections with voltage
Na.13.3 Vital
reports violations and / or over loads.

Identification
of equipment There should be facility for identification of
through colors network element / equipment through colors code
Na.13.4 code on SLD in Vital
on a single line diagram in case of abnormal
abnormal operating condition.
condition.

Saving of The user can save reports, information

Na.13.5 reports (Tabular/Graphical /non-graphical) to file/printer/ Essential
terminal.
User Text
printing along The comments/user text can be printed along with
Na.13.6 with selected Essential
the selected graphs and network diagrams.
network
Saving in There should be facility for importing Single line
Na.13.7 different diagrams and reports to industry standard packages Essential
formats like Microsoft Word, Microsoft Excel etc.

Na.14.0 Cost Estimating -

Preparation of
The module should be capable of preparing cost
cost estimates
Na.14.1 estimates of lines, substations etc. based on the Vital
as per cost
cost data.
data
There should be provision for users to input
customized costs for special structures like river
Provisions to
crossings, railway crossings. There should also be
input special
Na.14.2 provision to input the cost data of storing the Essential
and customized
material and associated equipment, erection
cost data
charges, other standard and non-standard estimate
components.
Estimated for
The module should be capable of preparing project
several lines
Na.14.3 estimates consisting of several lines and Essential
and sub
substations.
stations
Storage of cost
data of several There should be facility to store the cost data of
Na.14.4 areas and several areas and more than one version of the Vital
multiple project report.
versions

Page 101 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Automatic The module should be capable of capturing the

capturing of works proposed under various studies and creating
Na.14.5 works proposed the estimates of the studies performed by Vital
and creation of transferring the initial works proposed in the
cost estimates studies without again entering those details.
When the user picks up the study, the cost estimate
Automatic
should get created automatically interactively by
Na.14.6 creation of Vital
selecting the complete details of the lines and
cost estimates
equipment proposed.
Na.15.0 Financial Analysis

For providing the commercial feasibility of any

Module for cost
technical modification proposed, the software
Na.15.1 benefit Vital
should have module for cost benefit analysis of any
analysis
network under various proposed alternatives.

Provision for The proposal shall also include the depreciation of

Na.15.2 cost “Item recovered” Essential
depreciation
Cost The module should provide for evaluation of project
Na.15.3 calculations for and cost calculations for various system Essential
various options improvement options proposed.
Calculation of It should be able to calculate the financial
various parameters such as internal rate of return, pay back
Na.15.4 Vital
financial period, sensitivity analysis etc. so as to optimize
parameters the investment for an electrical distribution system.
Module should also give the optimal solution for any
Provision of given network and shall have provisions for
Na.15.5 optimal minimization of losses so as to maximize the net Vital
solution benefit i.e., the present worth of loss reduction is
more than the annual cost of capital investment.

Page 102 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

7.0 Module: Customer Care Services

Objective: The system should improve the customer service by processing and resolving customer
requests/queries/complaints in minimum possible time by taking up it at appropriate place and level.

Module domain
From : Receipt of customer requests / queries/ complaints
To : Closure of complaints and intimation of the same to the customer

Specification Customer Services

The CRS will provide customer care using all subdivision’s latest consumer and network data using latest
technologies. The prime data input for the CRS will be as follows -

a Consumer related all sub-division Via Each sub-division’s daily working

information
b Latest Network information Via Each sub-division latest Network data
C Feeder Shutdown, Breakdown, Faults, Via CRS operator or SCADA
Alerts
D Complaint/Grievances registering, Via CRS operator
logging and assigning
E Attending the complaint Via Line party/Gang
F Attending of Grievances Via Concerned subdivision officials/modules
G Feedback or receiving the solved Via CRS operator
information

Type of Complaints that shall be received include -

S. No. Type of Complaint / Grievances Nature of Complaint

Voltage related Voltage High

Voltage Low
1.
Dim Supply
Voltage Fluctuation
Supply Failure related Supply failed – Individual
2. Supply failed – Total Area
Supply failed – One Phase
Transformer related Transformer – Cable / Lugs burnt
Transformer – Oil Leakage
3.
Transformer – Sparking at Pole
Transformer – Smoke /Flames

Page 103 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Line related Line Snapped

4. Line – Tree branches touching
Line – Bunched / Twisted
Pole related Pole – Rusted / Damaged
Pole – Fell Down
5.
Pole – Leaning
Pole – Current leakage in pole
Services connection related Service connection–Wire Damaged
Services Connection – Wire Broken
6.
Services Connection – Wire Loose
Connection
Billing related Excess billing, wrong meter reading
7
etc.
8 Meter related Defective or damaged meter
9 New connection Getting new service connection,
Disconnection / not in use Disconnection of supply / not in
10
use for long period
Attribute change Attribute changes i.e. location,
11
name, floor, load etc.

The various other services in addition to technical complaints as mentioned above that shall be extended by the
customer care center to the customer of DISCOM are mentioned below. The list is just indicative.
1) Customer Information -
Providing information to customer queries relating to metering and billing data. Information about how to avail various
customer services offered by DISCOM, etc.
2) New Services Connection -
Provide status and information for new service connection.
3) Handle Metering & Billing related and other Complaints -
Receive and register all complaints relating to metering, billing, disconnection, dismantlement etc., forward the
registered complaints to the respective office of DISCOM for timely redressal. Follow up until the complaint is
successfully resolved.
4) Handle Service Request -
Accept and register various service request relating to status of title transfer, change of consumer data, change of
contracted load, energy theft enumeration, line shifting, etc. Forward the registered complaints to the respective
offices of DISCOM for timely redressal. Follow up until the complaint is successfully resolved.

Page 104 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

“ System Logical Block Diagram showing different components and Interfaces of the Centralized
Customer Care Center “

Page 105 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Module: Centralized Customer Care Services

Com
Require Functionality Description Critic Respon
ment
ment ID ality se
s
CC1.0 General Features -

The specification is for establishment of an centralized

and computerized customer care center with single
window operation equipped with latest technology &
multi skilled customer service representatives. The one
Establishmen
point contact service relieves the customer from the
t of single
inconvenience of visiting or contacting different utility C/
window
CC1.1 offices. In addition to Complaints received online Vital ER/F/
computerize
through Telephone, email, fax, letters and IVR system, CR/ NC
d customer
many customers may choose a personal visit and
care center
therefore the Customer care Centre set up to address
their grievances, must be equipped with basic
amenities, clean environment and manned by trained
personnel, who should be sensitive to customer needs.

Easy to remember and easy to access Telephone

number like 1912 with multiple lines
Available 24-hours a day, 365 days a year.
Multi-lingual if required (Hindi, English, any
CC1.2 Main features regional language) Vital
Multi-Skilled Customer Service Representatives
Single touch-point for no supply, billing
complaints, fire & shock complaints, all other
queries and assistance etc.
The Customer care centre should be linked
through mobile SMS in a “closed user group” to
Link of CC breakdown staff / mobile maintenance vans.
Centre to Immediately upon receipt of a no-supply complaint,
CC1.3 Vital
maintenanc an SMS will be sent by CC centre to the
e staff breakdown staff/van for fault restoration. After
restoration of the fault, the breakdown staff will
close the complaint at the CC centre.

Initially the centralized CC centre may be established

Seating Desira
CC1.4 with 30 seats, but should be further expandable as per
capacity ble
the requirement of utility.

Page 106 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

The CRM infrastructure shall make use of the existing

applications in such a way that the required
functionalities are available on the agent desktop in
the following fashion :-
Availability 1. The existing screens, features & functionalities of
of required the Billing, Consumer Indexing and Asset Mapping
functionalitie & Customer Care Solution shall be popped up
s like billing, appropriately. The system shall have the
CC1.5 Vital
consumer scalability so that any change, if required can be
indexing etc. done free of charge in 48 hrs time.
on agent 2. For the data, which is generated & maintained in
desktop the CC Centre itself such as call center
performance, voice recording etc., the local
database will be accessed. All other information
like billing, collection, other customer service
functions will reside over central server.

Provision of
The utility shall provide read access to various
read access
database tables related with Computerized Billing,
to CC centre
Consumer indexing and Asset mapping (if any). The Essent
CC1.6 staff for
agency shall be responsible for designing, procuring ial
various
and installing necessary software and hardware for
database
accessing the same.
tables

The bidder shall design different CRM application for

meeting the requirements of its agents in consultation
with utility. This application should be fast, flexible
Design of
and efficient enough to meet all the requirements of
CRM
customers’ queries. Typically such an application shall
application Essent
CC1.7 display customer’s personal profile, product / facility
by bidder to ial
profile, billing and payment profile besides the
suit utility’s
answers for their queries. The bidder shall further add
requirement
new features to be installed at CRM application, if so
desired by utility free of charge within 7 days of the
request.
Use of The CC centre will provide facility not only for
incoming as receiving calls, but also outbound calls. The Agents
Essent
CC1.8 well as would be asked to make outbound calls for informing
ial
outgoing customers about the various power supply positions,
calls payment reminders etc.
CC2.0 Infrastructure
The workstation for each agent should meet minimum
requirement of 36”x24” table size with partition. The
Workstation agent seats should be placed at sufficient distance so Desira
CC2.1
dimensions that conversations are not overheard. Each agent ble
should be provided with a standard and convenient
seating arrangement / chair.
PC & Each workstation should be provided with Work station
Essent
CC2.2 communicati PC along with Telephone Instrument with good quality
ial
on facilities handsets of reputed brands with options like voice

Page 107 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

at switch, background noise cancellation etc. Option of

workstation using headsets should also be available.
The CC centre environment should be pleasant and
Public
refreshing. The lighting should be soothing and air- Essent
CC2.3 conveniences
conditioning up to human comfort level. Call center ial
& ambience
should have its own pantry and clean and tidy toilet.
Sound The work atmosphere should be noise proof to avoid Essent
CC2.4
proofing disturbances from external sources. ial
Fire fighting The infrastructure should be provided with fire fighting Essent
CC2.5
equipment equipments to avoid any disasters. ial
Inter-
connectivity The workstations will be connected to each other Essent
CC2.6
of through a LAN (Local Area Network) connection. ial
workstations
Space to
There should be separate and adequate space to host
accommodat Essent
CC2.7 technology equipments, which must be safe, secure
e Technology ial
and accessible to administrative use only.
Equipments
CC3.0 Technology -

It should be Voice logger driven, CTI Server based

Customer care Center with real time data update. It
will act as an interface between the customer and the
Utility operations in the entire supply related
complaint handling processes. It should use a wide
Voice logger Essent
CC3.1 variety of latest technologies to allow them to manage
& CTI server ial
the large volumes of work that need to be managed by
the customer care centre. These technologies will
ensure that agents are kept as productive as possible,
and that calls are queued and processed as quickly as
possible according to the desired levels of service.

The centralized Customer Care Center consists of the

following components. The components shown are
logical blocks, these components can reside on single
server or span across multiple servers.
1. Call Switching Equipment (Private Branch
Exchange) – Soft PBX / switch based PBX
2. IVRS ( Interactive Voice Response System) / Fax on
Demand
High-Tech 3. CTI (Computer telephony Integration) - Screen
CC3.2 Vital
facilities pop-up
4. Automatic Call Distributor
5. Dialer
6. Voice Logger
7. Reporting
8. Call Monitoring and recording
9. CTI Remote monitoring capabilities and remote
logging facility
10. Customer Relationship Module (CRM)
CC4.0 Call switching Equipment / PBX :
CC4.1 PBX features The PBX system on the incoming trunk side should Vital

Page 108 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

support both Analog and Digital lines (ISDN PRI). The

capacity on the trunks and extensions shall be as per
the size of the call center. The PBX should have all
features of an advanced PABX System and should be
CTI and IP enabled. The PBX should have the following
features :-
Call Transfer, Conference, Call Pickup, Call Monitoring,
Call Recording, Call Hunt Groups, Direct Inward System
Access (DID), Extension Dialing, Voice Messaging, and
ACD (Automatic Call Distribution).
The ISDN-PRI interface must support the following
features -
Call-by-Call Service Selection
Channel Negotiation
Calling party number (ANI)
Called party number(DNIS)
Billing Number (BN)
Non-Facility Associated Signaling (NFAS)
D-Channel Backup
Administration Connections with Automatic
Restoration Temporary Signaling Connections
Ability to
Call Switching System should also support standard
support DNIS, Essent
CC4.2 features like DNIS, ANI and CLI.
ANI & CLI ial
features

Server or The PBX system can be either switch based or server

Essent
CC4.3 switch based based system.
ial
PBX system

CC5.0 Automatic Call Distributor (ACD) :

Automatic Call Distributor (ACD) distributes incoming
calls to a specific group of terminals used by agents.
ACD is a feature used to route calls in a call center Essent
CC5.1 ACD features
environment to the appropriate agents, based on ial
factors such as time available, skill sets and priority
levels.
Handling incoming calls is the task of the ACD system
that consists of hardware for the terminals, switches,
Telephone lines and software for the routing strategy.
The routing strategy is a rule based set of instructions
that tells the ACD how calls are handled inside the
system. Most of the time this will be a set that Essent
CC5.2 ACD feature
determines the best available agent for a certain ial
incoming call. To help make this match, extra
variables are taken into account, most often to find
out the reason why the customer is calling. Sometimes
the caller's caller ID or ANI is used, more often a
simple IVR is used to just ask for the reason.

Page 109 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Call Detail Recording. The system must be able to

generate Call Detail Records (CDRs). CDRs must be
generated for both incoming and outgoing calls on
trunk facilities, The Bidder must describe :
The information provided in a CDR.
System
The methods for outputting CDR data. Buffering
capacity to
must be provided in the event that the external Essent
CC5.3 generate Call
call accounting system, or storage device, is ial
Detail
unable to accept the CDRs for any period of time.
Records
How many CDRs can be buffered ?
If the system has the capability to provide a
printed listing of CDRs as they are output.
The Bidder must provide samples of Call Detail
Records.
System Management Security. Access to the system
for management purposes must be logging password-
protected. The system should have the ability to
restrict the capabilities of the users based on the login
Password IDs.
CC5.4 protection of The system must support the setting of an attempts Vital
system threshold (number of attempts within a specific time
period) for access to system management ports. If this
threshold is exceeded, the system must automatically
disable the login. The Bidder must describe his
proposed system's ability to meet this requirement.
Call Handling. Calls must be delivered to CSRs in First
Call Delivery In / First Out order (order of arrival queuing). Calls
Essent
CC5.5 to CSR’s by must be distributed to the "most-idle" CSR. The Bidder
ial
ACD must describe the algorithm for selecting the "most
idle" CSR.
Priority Queuing. It is desirable that calls to certain
Priority
trunk groups or to certain dialed numbers be assigned
Queuing Essent
CC5.6 a higher priority than other calls and that calls which
facility in ial
overflow from another split be queued ahead of other
ACD
calls. The Bidder must describe this process.
Call Queuing
ACD systems place calls into a queue, where they are Essent
CC5.7 facility in
typically handled in the order received. ial
ACD
ACD systems may handle routing of inbound or
Handling of Essent
CC5.8 outbound calls, or in some cases a combination of the
calls by ACD ial
two.
ACD ability
ACD system should support skill base routing, multiple
to support Essent
CC5.9 group support, priority handling and Queue status
priority ial
indicator.
handling etc.
Monitoring in Essent
CC5.10 It should provide supervisor assistance and monitoring
ACD ial
Real time remote monitoring of ACD queue, agent
Real time MIS Essent
CC5.11 status, and no call answered, abandoned etc. by
of ACD status ial
Supervisor.
ACD system’s Queue Specific Delay Announcement / Music. For Essent
CC5.12
ability to basic ACD applications, the customers must be ial

Page 110 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

announce provided a queue specific (different for each queue)

average wait delay announcement if a CSR is not immediately
time & music available to answer a call. If a CSR is not available to
to customer handle a call, the call must queue for the next
during hold available CSR. The system must be able to announce
up the average wait time to the caller. The system must
offer the caller the option of opting out to automated
information (i.e. IVR) or call back facility
The system must be able to provide music and
announcements on hold until the call is answered. The
Bidder must describe how the proposed system meets
these basic announcement requirements.
Tracking CSR Activities by Reason Codes / Automatic
Availability / Wrap Up Work. In order to give call
center managers detailed information about how CSRs
spend their time and to develop precise staffing
forecasting models, CSRs must enter a numeric code
that describes their reason for entering non-available
work modes or for logging out of the system. At least 9
codes must be supported.
Monitoring of
CSR sets must have the ability to be automatically
CSR’s
available to take the next call upon disconnecting from Essent
CC5.13 availability/
the current call. CSR sets must have the ability ial
non
automatically to go into a wrap-up, unavailable work
availability
state at the completion of a call. CSRs must also be
able to temporarily remove themselves from the call
queue to perform call related tasks.
Time spent in this work state (e.g., wrap up, lunch,
restroom, etc.) must be included in the individual CSR
and group statistics. In addition, the supervisor must
be provided with a visual real time indication of CSRs
spending time in this state.
Emergency Notification. The system must allow CSR
System positions to activate an alarm notifying a supervisor of
ability to an emergency condition. The system must also have
permit CSR the ability to automatically record the trunk number Essent
CC5.14
to activate and/or calling number if provided, the CSR position ial
alarm in case involved in the emergency, and to activate a recording
of emergency of the conversation with recording equipment
provided.
CSR Request for Assistance. The CSR set will have the
System ability to directly signal the supervisor when the CSR
capability to requires assistance handling an active call. Answering
permit CSR of CSR requests for supervisor assistance must be
to take help provided on the supervisor's set with special audible Essent
CC5.15
from and visual notification; so that the supervisor may ial
supervisor to readily identify that a CSR requires support. The LCD
deal with an or alphanumeric display must provide identification of
active call the calling CSR to the supervisor without referring to
the supervisor terminal.
Supervisors
Supervisors As CSRs. Supervisors must have the Essent
CC5.16 as CSR’s
capability to receive ACD calls during busy periods. ial
during busy

Page 111 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

periods
Supervisor Logout of CSRs by Supervisor. Supervisors must be
ability to able to logout CSRs from their own "soft phone" or
Essent
CC5.17 logout CSR’s supervisor terminal without having to go to the CSR's
ial
from its desk. They must also be able to log a CSR out from a
terminal remote location.
Monitoring CSR Conversations The supervisor must be
able to monitor a CSR's conversation for training or
administrative purposes from the supervisor set,
without plugging in to the CSR's "soft phone" set. The
proposed system must also meet the
System following requirements :
ability to Both silent monitoring and tone indication to the
enable CSR during monitoring must be available. Essent
CC5.18
monitoring a The system must offer a "soft phone" or supervisor ial
CSR’s terminal capability for monitoring directly at the
conversation CSR's "soft phone" or supervisor terminal for "ride
along" CSR training.
The "soft phone" or supervisor terminal must be
equipped with two jacks in order to permit a
supervisor to plug into the "soft phone" set for
training purposes.
Access to Real Time ACD Statistics. Each CSR set must
have the ability to view a customizable list of Call
Center MIS information on the digital display of the
CSR "soft phone". This information shall be individually
configured or selected from a pre-defined list of MIS
templates such as current split/skill performance,
application performance, and individual performance
status. CSRs and supervisors must be notified via the
"soft phone" or supervisor terminal indicators when
thresholds are reached for individuals and groups. The
capability must also exist to notify via email. CSRs
CSR set must be able to receive continual real-time display
ability to updates of ACD statistics via their display including
view call such information as a comparison of individual
center MIS performance to group averages or objectives. Essent
CC5.19 The display of ACD statistics on the "soft phone" or
regarding ial
ACD statistics supervisor terminal must include, but is not limited to,
on real time the following items:
basis ACD calls
calls abandoned
calls waiting
oldest call waiting
average speed of answer
average time to abandon
percent in service level
CSRs staffed
CSRs available
CSRs on ACD calls
CSRs on extension calls
calls handled by CSR

Page 112 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

calls completed by CSR

Real Time Monitoring Reports. The system must
support real time monitoring of CSRs, split/skill
groups, trunk groups, and applications. Reports must
be available in both text based and full color,
graphical formats.
The supervisor must be able to see at a minimum (in
plain language and color graphical formats)
information including but not limited to each of the
following items:
the active CSRs and the current individual CSR
status (whether on an active ACD call, in after-call
work, waiting for an ACD call, or in an inactive or
idle state).
the number of CSRs currently in various work
states such as available, on ACD calls, in
unavailable modes.
drill down capability to see individual
System
performance data for a given CSR.
ability to
the current queue status including calls waiting,
provide real
oldest call waiting, number of calls handled, Essent
CC5.20 time
number of calls abandoned, service level, etc. ial
monitoring of
CSR’s to a display of how CSR time is spent based upon
supervisor assigned reason codes for unavailable non call
associated work modes. For example: how much
time CSRs spent on breaks, in group meetings,
training, etc. At least nine different reason codes
are required for reporting time spent unavailable.
These must be reported individually on each
individual CSR report.
a call handling time profile which displays the
number of calls answered and abandoned
according to increasing service intervals. For
example, how many calls were answered and
abandoned from 0-5 seconds, 5-30 seconds, 30-60
seconds, 60-90 seconds, etc.
the number of times during the current interval
that a CSR reported a call event. This will assist
Utility in keeping count of specific customer
requests or types of calls. At least nine different
call events must be tracked.
System Call overflow : The system should support call
ability to overflow routing e.g. if there is a queue in particular
Essent
CC5.21 support call ACD group and another group is sitting idle, system
ial
overflow should be able to transfer the calls to another group
rerouting based on the settings defined by the administrator.
Skill Assignment and Preference Levels. The
System
proposed system must be able to assign individual skills
ability to
to each CSR (i.e. bilingual, training or experience Essent
CC5.22 rate CSR’s on
level, product knowledge, customer knowledge, etc.). ial
various
Individually assigned skills must be able to be ranked
parameters
and rated in terms of priority, proficiency or

Page 113 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

preference -
the maximum number of simultaneous skills
queries and routing requests that can be executed
at a time
how call processing is affected with a server or
link failure
backup and recovery options
Skills-based Routing - The proposed system must be
able to match the requirements of the caller to a CSR
with the skills to handle the call. The Bidder must
System explain how this is accomplished. The system must
ability to assure that the CSR will receive a waiting call for
Essent
CC5.23 route calls his/her primary assignments even if a secondary skill
ial
depending on assignment call has been waiting longer. Alternatively,
skills of CSR on a CSR by CSR basis, the system must provide that a
CSR always receives the highest priority, oldest call
waiting for any of the CSR's skill competencies on a
"greatest need" basis.
System Changing CSR Skill Assignments-The ability must be
ability to provided to add or remove CSR skills dynamically while
Essent
CC5.24 modify CSR CSRs are on calls. The system must provide the
ial
skills capability for CSRs to be logged into one or more
dynamically splits/skills when being moved between CSR groups.
Virtual Seating or Free Seating - The proposed system
must support the concept of virtual seating. CSRs can
log-on from any "soft phone" instrument within the
system. CSRs on the proposed system will be logically
defined, rather than requiring a "soft phone" extension
CSR ability to
and termination. Each CSR and supervisor on the Essent
CC5.25 login on any
system must have an individually assigned log-on ial
soft phone
identification number which permits individual
statistics to be collected by the ACD management
information system. Multiple log-on events by the same
individual during a work period at different terminals
must be tracked individually as one "shift".
Integrated Auto-Attendant - The system must provide
integrated auto-attendant routing
System to functionality such as "If you know the extension of the
have party you wish to speak with, you may dial it now". The
integrated system must have the capability to prompt customers Essent
CC5.26
auto- for the type of service they desire, i.e. "Press 1..., ial
attendant Press 2..." The proposed system should support these
routing capabilities internally within the proposed
Switching/ACD system even without requiring an
external IVR.
System
ability to Announcement Hardware / Capacities - The system
provide must provide customers in queue with a variety of
Essent
CC5.27 announceme announcements. This capability must be inherent
ial
nt to within the ACD architecture avoiding the need for
customers in external announcement devices and/or IVR servers.
queue
CC5.28 Flexible General Announcement Features - The system must Essent

Page 114 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

announceme be able to force customers to listen to an entire ial

nt features in announcement before being connected to a CSR.
system Alternatively, the system must be able to immediately
connect a call to the CSR if a CSR becomes available
before an announcement is completed. The supervisor
must have the capability to control which method is
being used.
Unique Call Identification Tag - A unique tag must be
Call
associated with each call when it originates and remain Essent
CC5.29 Identification
with the call throughout a multi-site network to ial
Tag facility
facilitate cradle to grave call tracking.
Call Routing Commands/ Capacity. The system must
Call Routing
promote an autopilot approach to call routing by Essent
CC5.30 capacity of
providing routing tables of selectable commands and ial
ACD
conditions and using Standard English commands.
Integrated Routing Database Tables - A database must
Database
be maintained in the system for specialized routing
maintenance Essent
CC5.31 purposes (e.g., a table of priority customers which
for call ial
would receive priority routing and possibly queue to a
routing
dedicated CSR).
Call Routing
Call Routing Comparators - Comparison operators such
Comparator Essent
CC5.32 as "less than", "greater than", etc., must be available
facility in ial
for constructing vector routing commands.
ACD
Wildcard Digit Matching for Call Routing - The system
Wildcard
must be able to match ANI or other
Digit
digits in routing tables using wild card sequences that Essent
CC5.33 matching
would identify and route specific calls to a specified ial
capability in
destination. Bidder must describe type of wild card
Call Router
digit.
CC6.0 CSR AND SUPERVISOR TERMINALS
General Functionality - The CSR and supervisor
General terminals must use open architecture state-of the art
functionality technology and be widely used, generally available and
of CSR & standard equipment. Bidder will provide the desktop
CC6.1 Vital
supervisor PCs/ workstations and headsets to interface with the
functionalitie proposed solution. The Bidder must offer ACD "soft
s phone" and supervisor terminal functionality that is
controlled by a PC-based CSR interface.
CSR Station - Bidders must propose "soft phone"
technology for the CSR station. The proposed solution
CSR station must integrate with PCs provided by Bidder. PC
CC6.2 Vital
technology specifications are specified in hardware [Link] an
option, the Bidder must describe available touch
screen operation for CSRs.
CSR Headset / Handset Operation - The CSR "soft
CSR ‘soft
phone" set must be able to support both a CSR headset
phone’
CC6.3 and a CSR handset. There must be volume controls for Vital
support
each. The Bidder has to provide soft phone with
abilities
amplifier and head set.

Page 115 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Incoming Call Announcement - The system must

provide audible and visual whisper indication prior to
Incoming call the automatic connection of an ACD call to the CSR.
announceme For CSRs that handle calls for multiple applications, a
CC6.4 Vital
nt capability whisper must indicate what type of call is arriving so
of system that the CSR can greet the caller appropriately. The
"soft phone" must also display this information to the
CSR before delivery of the call.
Call Hold, Hold, Transfer & Conference Features - A dedicated,
Transfer & fixed feature button, for each function, must be
Conference provided on the CSR and supervisor "soft phone" set.
CC6.5 features of The system must have the capability for CSRs and Vital
CSR & supervisors to set up conference calls for a minimum of
Supervisor 4 parties (including the CSR supervisor) without
soft phone requiring attendant assistance.
Personalized
Greeting CSR Personalized Greeting - The system must offer
recording the capability for CSRs to record Essent
CC6.6 personalized greetings that can be played to the caller
capability of ial
CSR soft prior to connection to the CSR.
phone
CSR phone Entering Event Codes (Wrap Up) - CSRs must be able
system to enter codes to identify events that occurred during
ability to a call and to enter wrap up codes before becoming Essent
CC6.7 have & ial
available for another call.
accept event
codes
CSR phone
system
Entering Call Identification Codes - CSRs must be able
ability to
to associate other types of identifying information, Essent
CC6.8 have &
such as consumer code, to particular calls. The system ial
accept call
must support up to sixteen digits per code.
identification
codes
Audio fault
Audio Difficulty Trace - When a CSR experiences static
reporting & Essent
CC6.9 or a noisy trunk, the audio difficulty must be easily
tracing ial
reported and traced.
ability
System
ability to Routing Based on DNIS - The system must be able to
Essent
CC6.10 route calls route calls based on Dialed Number Identification
ial
based on Service (DNIS).
DNIS
System
Routing Based on ANI - The system must be able to
ability to Essent
CC6.11 route calls based on Automatic Number Identification
route calls ial
(ANI).
based on ANI
System Support for Network Provided CINFO Digits (Caller Essent
CC6.12 support for Information Forwarding) - The system must have the ial
network ability to collect caller entered digits (CED) and

Page 116 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

provided customer database provided digits (CDPD) supplied by

customer the network in an incoming call’s ISDN PRI setup
information message and provide routing based upon these digits.
digits
System Overflow Destinations - Calls must have the capability
ability to to be automatically overflowed to a voice response Essent
CC6.13 divert calls system based upon conditions in the call center ial
to IVRS based including call volume and time of day.
on conditions
Ability of Route by Caller Prompted Information - The ACD
ACD system system must be able to request and collect
to request & information, such as a consumer no, and then route
the call based upon that information. The system must Essent
CC6.14 collect
have the ability to prompt a caller for up to 12 fields ial
customer
information containing up to 16 alpha/numeric characters of
& route call information.

CC7.0 MANAGEMENT INFORMATION SYSTEM

Basic Internal Reporting - The system must provide
System basic low-cost, integrated reporting that does not
ability to require administration, external processors or external
provide real storage. Both real time reports and historical reports
CC7.1 Vital
time & are required. Historical reports must be available for
historical hourly or half hourly intervals. The proposed system
reports must be capable of displaying reports on a video
display terminal in real time or emailing them.
Custom Reporting - Fast, easy creation of custom
System reports from scratch is required as is
ability for modification of existing reports to customize them for Essent
CC7.2 creation of reporting purposes. Report customization must include ial
custom the ability to create custom data items and define
reports custom calculations.
ODBC
Open Data Base Connectivity - The database must be Essent
CC7.3 compliance
ODBC compliant. ial
of database
System
ability to Exporting Data - It is desirable that call center data be
transfer call exported to file or directly to other Essent
CC7.4 applications (e.g., other database systems, web
center data ial
for other servers).
applications
System
Remote Access - Supervisors must be able to access
ability to
the management information system and monitor and
CC7.5 provide Vital
administer the call center from a PC at remote
access to MIS
locations.
from remote
Cradle to Grave Reporting - The system must support
‘Cradle to Essent
"cradle to grave" reporting which would reveal exactly
CC7.6 Grave’ ial
what happened to a caller from the time they entered
reporting by
the system until the time they hung up, and

Page 117 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

system everything in between.

System
ability to Web Browser Interface - The system must support
support call customized queries of detailed call records via an Essent
CC7.7 record industry-standard Web browser or graphical user ial
queries via interface.
web browser
Long term Long Term Storage of Detailed Call Records - The
Essent
CC7.8 record system must provide for long-term storage of detailed
ial
storage call history records.
Comprehensive Historical Reporting - Historical
reports must be available for CSRs, split/skills, trunk
groups, and applications in interval, daily, weekly, and
Comprehensi monthly formats. Both graphical and text based
formats are required. It is required that reports be Essent
CC7.9 ve Historical
printed on demand and on a scheduled basis. Historical ial
Reporting
data must be stored. Real Time reports must update
automatically approximately every 3 seconds or less.

Basic Graphical PC based Reporting - The system must

provide real-time graphical reporting (bar-chart, pie-
chart, time trace, wallboard, or text report display
formats) to multiple supervisors, such as :
support of multiple external PC-based wallboards
for display of real-time data to various ACD groups
Graphical PC text messages created by supervisors displayed on
PC-based wallboards Essent
CC7.10 based
set thresholds on data items that alert supervisors ial
reporting
both visually and audibly when thresholds are
reached and be able to send beeper/text
messaging device
Supervisor ability to customize views for real time
monitoring of items and resources of interest in
the call center.
LAN
Local Area Network Connectivity - Supervisors must
connectivity
have access to the management information system via Essent
CC7.11 of CSR PC’s
a PC connected to a local area network using TCP/IP ial
for remote
protocol.
MIS access
Exceptions and Thresholds - The following reports
capabilities are required :
Real time reports displaying color threshold
Exceptions & indications for items that are exceeding desired
threshold levels such as number of calls in queue or oldest Essent
CC7.12
reporting by call waiting time. ial
system Definable exception categories and thresholds.
Bidder must fully explain if thresholds can vary
between different splits and applications or are
they set for the entire system.

Page 118 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Supervisors receive notification of all defined

exceptions.
Recent exceptions be displayed on demand.

Backup Backup Process - Backups must be performed

Essent
CC7.13 process scheduled or on demand.
ial
performance
Online Help - The system must provide Browser/GUI-
Essent
CC7.14 Online Help based online Help.
ial
Alarm in Alarms and Error Conditions -The system must
event of generate an alarm and notify service personnel in the Essent
CC7.15
problem or event of system problems or errors. ial
error
INTEGRATED FORECASTING CAPABILITIES - The
Management Information System must offer integrated
Forecasting capabilities based on AHT (average Handle
time) and no of CSR etc. It is desirable the proposed
solution has a call center simulator or the ability to
provide "what if" forecasting scenarios considering the
Integrated
factor such as holidays, special campaigns, season
Forecasting Essent
CC7.16 trends, billing cycles, and other date of month
Capabilities ial
influences are taken into consideration. Assignment of
of MIS
work shifts to employees. Generate an optimal
schedule for CSRs for each hour that meets the
forecasted call volume taking into consideration CSR
availability, calendar management, and our desired
service objectives.

CC8.0 Interactive voice response system (IVRS) :

Interactive voice response system, or IVRS, is a
computerized system that should allow a telephone
caller, to select an option from a voice menu. The
system should play a pre-recorded voice prompts to
which the person presses a number on a telephone
keypad to select the option chosen, or speaks simple
answers such as "yes", "no", or numbers in answer to
the voice prompts.
IVRS with Advanced Speech Processing (ASP). The multiple
ASP features advanced speech processing technologies (large
with text to vocabulary recognition, natural language
CC8.1 Vital
speech & understanding, speaker verification, speech-to-text)
text to fax may be required as features. The ASP technology
capabilities should be provided with software that runs on an open,
industry standard subsystem platform, under Unix or
Windows. The platform must permit qualified third
party developers to integrate additional ASP
technology and functions.
ASP shall support English and local language.
The latest system of natural language speech
recognition shall be used to interpret the questions
that the person wants answered. Latest innovations of

Page 119 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

its ability to speak complex and dynamic information

such as an e-mail or any other information using Text-
To-Speech (TTS), which is computer generated
synthesized speech, shall be used. Real voices are
used to create the speech in tiny fragments that are
glued together before being played to the caller.
Text to FAX capabilities. The IVR Bidder must support
this functionality consistent with the languages
supported by the Text to Speech, ASP. IVR will provide
multiple options to callers for self- retrieval of
information by fax.

IVR systems shall generally be used at the front end of

call centers to identify what service the caller wants
and to extract numeric information such as electricity
payment dues, bill payment status as well as provide
IVRS system answers to simple questions such as completion of fuse Essent
CC8.2
features off calls or allow pre-recorded information to be ial
heard. The IVR Systems should be properly designed so
as to connect callers to their desired service promptly
and with a minimum of fuss.

The IVR System should be scalable as per the locations

of consumer base. All the calls received at the call
center shall first land on the IVRS, the system shall
welcome the user and present a voice menu to select
Scalability of the service he requires and also key in and retrieve
CC8.3 Vital
IVRS information from the system. The IVRS shall be CTI
supported so that all the information entered by the
caller on the IVRS is to be passed to the customer
service representative screen as popup.

IVRS
The average call duration is 2 minutes; The IVR system
capability to
must be able to accommodate fluctuations in call Essent
CC8.4 handle
volume. ial
variable call
volume
Response Time / Performance / Availability - The
response time must be no more than 2.0 seconds. The
worst-case IVR response time (not the average) must
be measured with all phone ports simultaneously
speaking different messages (different or the same).
The response time must be measured using the
following two scenarios:
Response
CC8.5 The time the user completes input until the start Vital
Time of IVRS
of voice output is heard; and
From the time a host message is received until the
start of voice output is heard.
The requirement is for the IVR system to be
available in a 24 X 7 X 365 for general narrative
information and customer billing information.

CC8.6 General General Architectural Requirements - Although the Vital

Page 120 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Architectural Bidder will propose the general

Requirement architecture of the system, there are certain overall
s of IVRS aspects of the system that the Utility considers
important to include. These are :
For effective use of memory capacity, the system
must permit multiple applications to use common
speech files to handle items unique to an
application along with common items.
The IVR system must be built employing open
industry standards and widely-used and generally
available components and software.
The system must be a client–server architecture
that is scaleable.
The proposed IVR system must interface with the
Customer care systems and database.

Redundancy / Alternate Call Routing - The IVR system

must have redundant connections to both the
telecommunications network and the Local Area
Network (LAN) interfaces. These connections must
have failover capability to support both voice and data
traffic. These failover connections are to ensure
redundancy in the event of failure within the network
Redundancy servicing the IVR, and for the LAN providing the data
of from the back-end systems. Each of the links must be
connections capable of supporting the emulation of multiple
CC8.7 for tele- terminals. Recovery from power interruptions and Vital
communicati system problems must occur automatically. The system
on & LAN must include provisions to monitor all centers 24 hours
network per day, 7 days per week and the capability to conduct
online, on-demand and routine diagnostics to
determine general status of the IVR and its
applications without interfering with service. The
telephone connections required for this purpose has to
be arranged by the bidder and cost of the same shall
be reimbursed by the utility in actual.

To ensure that the proposed IVR platform can support

growing and changing needs, the bidder shall provide a
platform based on an industry standard processor and
Processor & operating system utilizing a Unix or Windows platform.
system The kernel of the operating system must not be
CC8.8 Vital
standards for modified or use proprietary drivers.
IVRS system The system must be a modular design to support
expansion and enhancement to major components
of the IVR system.

IVR Menu Tree Complexity - Based on the business

Menu tree process requirement the bidder has to design menu
complexity tree structure. The menu structure should not be more Essent
CC8.9
of IVRS than 4 levels with 4 to 5 options per level. Each of ial
system the IVR system's menu options will need to be reviewed
with the utility prior to IVR development to ensure

Page 121 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

that all business functions are implemented as needed.

The Bidder must make recommendations on the best
way to implement the required functionality of the
menu trees.

IVR Data Base Interfaces - The required method of

connectivity is to integrate the proposed IVR to
Integration
networks located at CC centre with the master
of IVRS with
CC8.10 database of the utility This connectivity should be Vital
Call centre
through a single point, with redundancy provided
networks
through 2 connections at the single point.

General Functionality -The IVR must be designed with

the following parameters to manage / limit the
following call transaction and duration characteristics :
General
total transaction (call length)
Functionality Essent
CC8.11 individual message input (response to a prompt)
of IVRS ial
The parameters must be configurable by the Bidder
system
and Utility with no interruption of production
applications running on the system.

INTELLIGENT CALL ROUTING REQUIREMENTS -

If it becomes necessary to shut down an IVR
application, the system must be capable of providing
an announcement to the caller. Utility must be able to
take all lines out of service after the completion of the
call in progress on each line. This must be initiated by
console command or host command.
The IVR system must be able to automatically restart
following a power failure.
When the host systems are unavailable, the IVR must
be capable of responding to incoming calls in various
different ways. First, it must offer the capability to
answer incoming calls and announce either
"Information not available at this time" or "System
unavailable" (as examples). Secondly, the system must
IVRS have the ability to make all ports appear busy. It is
CC8.12 Vital
functionality desirable to have the system’s response to this
condition be controlled by the application software,
rather than defined at the system level.
The following additional functionality is required when
a host or IVR application is unavailable to the caller:
Ability to directly route all incoming calls to the
CSRs for complaints handling
Ability to route incoming calls to a CSR when the
Customer has difficulty in accurately inputting
their customer no.
Ability to route incoming calls to CSR when the
data server or an IVR application is down during
business hours and the Customer can not access
specific information during an Information Inquiry.

CC8.13 Graphical Monitoring, Statistics and Reporting - Each system Essent

Page 122 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

tool for must provide a graphical tool for ial

monitoring & supervisors, managers and system administrators for
Reporting on real-time monitoring of the system. Utility requires ad
real time / hoc reporting, upon demand.
on demand The system must include an administration or
basis management tool for local and remote monitoring and
management of every component of the IVR system.
The monitoring tool must allow for immediate or
progressive shutdowns and for shut down of single or
multiple telephone lines, host connections, processors,
applications of the entire system. The management
tool must be secure from unauthorized users and
available to one or more administrators concurrently.
The management tool must be accessible via remote
access. At minimum, reporting features must capture
all of the following criteria and be available on-line, in
real time:
Ability to generate traffic and performance
reports online on a daily, weekly, monthly and
quarterly basis.
Application statistics must be provided on an
event basis and accumulated by specific
applications in the IVR and by Customer ID.
Application statistics must be provided showing
the number of times a Customer is transferred to
a CSR during a Information Inquiry transaction.
Report information to include downtime, system
usage by event script application, calls aborted,
average length of call, busy hours, average call
hold time by script application accessed.
Cumulative data to the previous hour must be
available at the half-hour.
System capability to permit automatic scheduling
of certain routine tasks at specific intervals. This
would include report generation, data collection,
and transfer or scripts for administration. A log
file provided to review activities.
The reporting system must track historical and
real-time information. The reporting system must
be capable of creating, saving and printing both
standard and customized reports. The real time
monitoring and reporting must be accomplished in
a windowing environment. Monitoring and
reporting must include security features to ensure
access only by authorized personnel.
Common monitoring statistics across all systems
include call volumes, IVR uptime, utilization,
billing, max/min call usage, average length of
call, average queue depth, average hold time and
logging (for legal traceability).

CC8.14 IVRS The bidder shall keep provision for making changes in Essent

Page 123 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

announceme the IVRS announcement as per the request of utility ial

nt changes within two days.

IVR will be responsible to answer each and every call

IVRS ability
and multilingual / multilevel option to be provided to Essent
CC8.15 to respond to
the caller based on the dialed number (DNIS). ial
each call
IVRS ability IVR should provide user defined rule based routing e.g.
to provide IVR can automatically play payment balance, energy
Essent
CC8.16 user defined used etc. in the current month based on the data
ial
rule based captured (CLI) or entered by the subscriber.
information
IVRS ability IVR will route the call to the appropriate ACD group
to route call e.g. billing enquiry, fuse off complaints, new payment Essent
CC8.17
to requisite schemes, technical support etc. ial
ACD group
IVRS ability IVR should also capture customer’s dialing details and
to present presenting them to ACD or CTI directly to make routing
customer of calls easier by identifying the calls i.e. by Essent
CC8.18
dialing identifying the customers from DNIS, CLI, ANI or ial
details to internal calls etc.
ACD
Integration
Other voice related technologies shall also be
of other Desira
CC8.19 integrated to IVR system.
voice related ble
technologies
a) Performance Testing. Because the Bidder will be
delivering hardware and software across all
applications, the Bidder must provide performance
testing for each application before full acceptance of a
system by Purchaser.
b) Testing, Diagnostics, and Monitoring. The Bidder
must develop, implement and install the new IVR
systems. The hardware, software and developed
application must be tested prior to full production
implementation. The Bidder’s must complete the
installation and provide pre-installation site
IVRS (all preparation to ensure proper environments and
applications) adequate space is available for the IVR. The Bidder
CC8.20 performance must ensure that the system is fully integrated with Vital
testing by existing database server and equipment.
bidder The Bidder is required to perform extensive testing,
based upon the requirements for each application,
including but not limited to Bidder testing, and
acceptance testing. These tests will include load
testing, and verification that the application works at
each location. Testing must include hardware,
software and application full integration and systems
testing, stress testing, post implementation testing and
parallel testing, where appropriate. The Bidder is
responsible to establish the testing environment. The
Bidder must coordinate with Purchaser for transition
from the existing systems if any to the new systems

Page 124 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

without interference with production systems.

Adequate reporting must be available to allow both the
Bidder and Purchaser to measure the system’s
performance accurately under defined test conditions
and in defined environments. The Bidder must develop
and submit a Test Plan, including resource
requirements and schedules, for complete testing of
each of the applications, with test criteria to support
all hardware and software performance requirements,
IVR system features, interfaces, and architectural,
communications and security requirements. The Bidder
must include a disaster recovery procedure to insure
that the systems are always available. The Test Plan
must include the intended plan and justification for
the chosen testing environment(s) throughout the
entire testing lifecycle. Contingency plans must be
defined in the event the Test Plan cannot be carried
out, as initially planned. Purchaser must approve
each segment of the Test Plan before testing begins

TRAINING AND DOCUMENTATION -

a) Common Initial Training Requirements. The Bidder
must provide SOCC site training for Purchaser staff at
the time of installation. Initial training must include
training on the overall functionality and monitoring
capabilities of the Call Center, statistical monitoring
and generation of ad hoc reporting capabilities.
The Bidder must provide train-the-trainer training and
documentation to the CSRs and supervisors. They must
also provide training for any administrator or
programmer.
Purchaser requires the Bidder to develop a training
Documentati
document (pamphlet, binder, or manual) for each IVR
on &
CC8.21 application, outlining the Customer interfaces of each Vital
Training to
application for distribution among Customers who will
Customer
use the applications.
The Bidder must provide PURCHASER with copies of all
documentation regarding the IVR applications and Call
Center application, including a User Manual.
The Bidder must provide basic maintenance training
and support training to Purchaser’s staff.
b) Unique Training and Documentation
Requirements. The Bidder will provide Purchaser’s
staff with training, documentation and tools to allow
the PURCHASER staff to make ACD and IVR system
script or vocabulary changes

CC9.0 Voice Messaging :

It is used for recording, storing, playing and
Voice Mail distributing phone messages to agents and / or group.
CC9.1 Vital
facility The voice messages could be attached as e-mail
messages and routed to agents.

Page 125 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Voice Mail provides the customers the choice to leave

their requests e.g. call back requests in times of long
time queuing etc.

Voice mail requests can be retrieved and played back

Retrieving of at any time from agent’s voice mailboxes or via their Essent
CC9.2
voicemail desktops. ial

System The system should keep a log of all voice messages,

ability to senders, receivers date & time etc. for reporting Essent
CC9.3
keep log of purpose. ial
all messages
The no. of IVR ports should be equivalent to the
No. of IVR incoming voice channels to provide non-blocking Essent
CC9.4
ports facility. ial

CC10.0 0 Computer telephony integration (CTI)

CTI (Computer telephony integration) is the
technology that allows interactions on a telephone and
a computer to be integrated or co-ordinated. The
following functions are implemented using CTI –
 Calling Line Information Display (Caller’s Number,
Number Called, IVR Options)
CC10.1 CTI system  Screen Population on answer, with or without Vital
using calling line data
 On Screen Dialling (Fast dial, preview and
predictive dial)
 On Screen Phone Control (Ringing, Answer, Hang-
up, Hold, Conference etc.)

Forms of CTI – Generally there are two forms of CTI –

a) First-party Call control – Here, only the
computer associated with the phone can control
all the fuctions of the phone at the computer
user’s directions.
b) Third-party Call control – It requires a dedicated
telephony Server to interface between the
Telephone network and Computer network. Any
CC10.2 CTI forms Vital
computer in the Network has the potential to
control any Telephone in the telephone system.
The phone does not need to be built into the
computer and may only need to have a
microphone and Headset in the circuit.
For the proposed Call centre, the agency should
provide CTI with Third party call control.

CTI ability to The CTI (Computer Telephony Integration) component

transfer shall be required for passing all the information from
information the PBX and IVR, such as the caller identification, Essent
CC10.3
from PBX & Dialed number information, Language option service ial
IVR to CSR’s opted by the caller etc., to the CSR’s CRM screens.
CRM screen

Page 126 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

The system should provide an agent application

Integration
integrated with CRM application. It should pop-up
of agent
along with the caller information, when the call comes
CC10.4 application Vital
to the agent. The CLI should have the capability to
to CRM
popup all the vital customer data on screen.
application
CTI system The Agent should be able to control the telephony
ability to features from this GUI application like login, logout,
enable away, pick-up, hold, hang-up, conference, and transfer
control of to another agent along with the screen (voice and Essent
CC10.5
telephony data). Screen pop-ups should be multi-colored. CRM ial
features components, queries or call priorities should be
from GUI recognizable by the color of the pop-up.
application
CTI system
The system should support virtual login e.g. an agent
support for
can sit anywhere and login by putting his login id and Essent
CC10.6 login from
that becomes his workstation. ial
any
workstation
Report
Entire login, logout, away, total call handled, data of
generation Essent
CC10.7 the agent should be captured and produced as reports.
capability of ial
CTI system
Online The Agent application should also have the online
Essent
CC10.8 display of monitoring display of the ACD queue(s).
ial
ACD queue
Integration The CTI application should also record a ticket on each
of CTI call for reporting purpose. The docket shall be opened
application by the CC centre and should be closed only after the
CC10.9 to billing & customer is satisfied. The system shall have the Vital
consumer capability to integrate with the utility’s billing and
indexing consumer indexing database.
database
CC11.0 0 DIALER :
The dialer system should be capable of interfacing with
the CRM for automatically dialing out to the consumers
to deliver information like power supply position,
Automatic
payment reminders, payment acknowledgement and Essent
CC11.1 Dialing
other information. The dialer should also be capable of ial
System
working in both predictive and progressive modes
depending on the requirement.

CC12.0 0 Remote monitoring capabilities

The system should support remote monitoring of real
Remote time ACD statistics, queue, and number of agents,
monitoring abandoned, answered calls from their office using the
ability of application provided by the system. Essent
CC12.1
ACD status, The application software shall have the facility for ial
no. of agents fault escalation to various administrative levels of
etc. utility depending upon the delay in clearance.

Page 127 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

CC13.0 Database Integration: -

System
integration The System should support retrieval of data from
with billing Utility’s computerized billing, Consumer indexing and
module & asset mapping systems residing at different server e.g.
Esse
CC13.1 Consumer if a caller wants to check his billing status, the IVR
should retrieve the data in real time from the database ntial
indexing &
asset residing at these servers.
mapping
module
System
integration Certain database access, like Billing and consumer
with billing & indexing, should be integrated with CTI for screen Essent
CC13.2
consumer pop-up, CRM and priority handling etc. ial
indexing
modules
CC14.0 0 CRM CRM: - Some of the main features of the CRM are : Essent
features ial
Multiple Application should support multiple host
Essent
CC14.1 host connectivity- local as well as remote. ial
connectivity
Single
Single interface for consistent customer interactions
Interface for Essent
CC14.2 through multiple touch points.
customer ial
interactions
Consolidated view of the customer to ensure that each
Customer agent has complete knowledge of every interaction Desira
CC14.3
Feedback regardless of the channel of communication. ble

The Agent should be able to rapidly create, assign,

track, and resolve a complete range of service
requests, cases, and trouble calls. They should also be
Essent
CC14.4 Agent ability able to generate confidence by successfully resolving
ial
inquiries. Brief description of all queries should be
recorded.

Should support standard features for e.g. subscribers

Standard Essent
CC14.5 call history, booking of complaints etc.
features ial
System The system should allow agents to capture and display
ability to contact information, problem descriptions, problem
permit categorization, severity classification, prioritisation, Essent
CC14.6 agents to and complete status tracking with open and closed ial
extract dates and times.
information
from system
System Should provide Customer service professionals with
ability to comprehensive defect tracking capabilities, enabling Essent
CC14.7
provide CSR to categorize, prioritise, and assign product defects for ial
with defect resolution based on input from incoming customer

Page 128 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

management service requests to proactively correct product quality

data issues.

Should provide option to view billing details of the

Billing details customer (last six months records) on CTI pop up along Essent
CC14.8 for six with vital information of customer. ial
months
Option to Should provide option to send the billing record (last
send billing six months) of the customer through e-mail / fax. Essent
CC14.9
details by e- ial
mail/ fax
Should be able to view details of the customer with an
Ability to authentic ID e.g. Consumer number, Name, Telephone
view number, Address and with an option to change the Essent
CC14.10
customer required parameters. ial
details
Should build a FAQ database for commonly asked
Ability to query. In case of any changes in tariff, the FAQ should Essent
CC14.11 build FAQ be updated within 1 day. ial
database
Search Search option to find the most similar answer to the
option for queries in the FAQ section with an option to e-mail Desir
CC14.12 most similar the same to the customer also. able
answer to
FAQ
Report generation module e.g. billing reports,
Report customer details report etc. - CRM application will
record the language preference of a customer and his Essen
CC14.13 Generation
next call will be routed according to his preference. tial
module

CC15.0 COMPLAINTS ESCALATION SYSTEM

In case the issues are not resolved within the defined
service levels, it shall be possible to escalate to pre-
specified higher authorities. The escalation hierarchy
would consist of three or more levels for escalation of
Escalation
CC15.1 complaints to expedite the complaint resolution Vital
policy
process. The choice of escalation authorities would be
made based on the criticality of the situation, which
could include the AE/EE or even the SE of the Circle.

The call centre software shall have a facility for

Automatic diversion of message from the Call Centre
Supervisor’s desk to the utility hierarchy as given
above, if the complaints are not closed within 2 Hours.
Escalation
CC15.2 However, it shall be possible to escalate all the critical Vital
policy
complaints like death / accident immediately to the
respective Circle CEO as well as Town in-charge of the
utility.

Page 129 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

CC16.0 OTHER SERVICES

Status Enquiry - Consumers should be able to know the
Complaint status of their complaint anytime by calling the CC
CC16.1 status center and providing the unique registration number / Vital
enquiry token number to CSR.

Payment Reminders – It shall be possible for the CSRs

in the CC center to follow-up with the consumers
regarding payments. The appropriate details of such
overdue consumers would be provided by the Utility to
the call center Supervisor. Billing software shall
generate weekly reports of such consumers, who have
Payment outstanding payments and should be forwarded to call Essen
CC16.2
reminders center every week through automatic messaging tial
services for further follow up with consumers.
Concerned utility may also decide a cutoff point for
consumers with such overdue payments, for whom call
center will refuse to lodge any complaint till all the
previous dues are cleared.

New Connection and other activities – As this Call

Centre will be a Single window option type, consumer
will be approaching for providing new connection. Call
center will provide the Application form to consumers
for New Connection and will also collect, scrutinize
and forward the same to utility official concerned. The
back end operation will be done by the utility staff,
but will keep the status updated in the system.
Similarly, there are other activities for which the
required application along with the required document
if any will be collected by the call center and
forwarded to utility official for sanctioning, changing
New
the tariff category etc, such as –
connection Essen
CC16.3 - Extension / Reduction of Load
and other tial
- Change/Transfer of Name
facilities
- Address correction
- Change of Category
- Disconnection and re-connection of power
- Any adhoc scheme etc.

All the status should be available with the Call center

at any point of time from the point consumer submits
his application till the job is completed and the
consumer shall get complete status of his application
at any point of time from call center itself through
Phone or in person.

Lead Lead generation and marketing of services - The

generation above shall be possible through the CSR personnel e.g.
Desir
CC16.4 and new payment modalities like direct debit facilities,
able
marketing of ATP Machines, Bill payment through Credit Card,
services Cheque Drop boxes etc. could be explained to the

Page 130 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

consumers. The CSR should inform the consumers

regarding tariff or any new service provided by the
utility.

Group Messaging System - The CC software should

have facility to sent group messages to those
consumers having Mobile phones as per the call centre
database, such as -
Common message transmittal/warning in case of
Group group faults (DT/Feeder failure etc) or any other
Essen
CC16.5 messaging information common for all consumers on power
tial
system situation
Advance intimation to consumers regarding load
shedding or planned shutdown or preventive
maintenance schedule
Date of bills generated and due date of payments

Closing of issues/requests - Once the issue is resolved

or the fault has been attended, the concerned
Electrical maintenance staff in the field will inform the
status to the CSR through his CUG Mobile phone. The
Closing of Essen
CC16.6 CSR personnel will update the status of the complaint
complaints tial
as closed and will also intimate the customer of the
same and take a feedback regarding service provided
by his personnel.

Page 131 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

8.0 Module: Management Information System (MIS)

Require Functionality Description Criticalit Response Commen
ment ID y ts

Mis.1 Generation The specification covers maintenance and Vital C/ ER/F/

and generation of various management information CR/ NC
maintenance reports required for top management, middle
level management and respective unit offices.
of various MIS
These are generally based on the data
reports generated under different other packages
covered in this section.
The MIS Module should include
 Information capturing
 Information processing
 Information management
 Information based decision-making &
reporting.
Mis.2 Study of Before finalization of MIS requirement and formats, Vital
existing a through study of the existing business process
business shall be carried out along with the utility. Based on
process to the organization structure and requirement of
finalize MIS decision support system at organization level, a
formats comprehensive MIS requirement document shall be
prepared. The actual MIS requirement shall be
finalized at implementation Stage.

Mis.3 Provision to The system should able to generate reports on Essential

generate MIS regular basis. Utility will finalize the periodicity
on regular and the format of report.
basis
Mis.4 Creation of The format for same report prepared for different Essential
different levels will be different, e.g. Monthly collection
formats for report for SDO, SE & CEO will be different.
different
level
Mis.5 Elimination of Data acquisition for MIS should preferably be Essential
human without human intervention as far as possible. The
intervention data should be collected only at the lowest level
in data and from the same source and in the standard
acquisition formats.

Page 132 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Mis.6 Provision to MIS reports are also to be generated for external Essential
generate MIS agencies such as regulatory Commission. The
reports for Formats for such reports are different based on the
external specific requirement of SERC. The formats and the
agencies periodicity of the same will be finalized with the
utility.
Mis.7 Type and Type of report and periodicity of such reports given Essential
periodicity of below are indicative only and final requirement will
reports be spelt out by utility as per requirement :

Type : Lower Middle Top level

level level
Financial Daily Daily / Monthly /
weekly quarterly / yearly
/
monthl
y
Operational Daily Daily / Monthly /
Efficiency / weekly quarterly / yearly
weekl /
y monthl
y
Customer weekl Weekly Monthly /
Satisfaction y / quarterly / yearly
monthl
y
Mis.8 Provision of This module should also provide monitoring system Essential
monitoring for -
system Revenue monitoring and Reconciliation
monitoring (based on billing backup data &
bank reconciliation and cash collection data)
Grievances & Public representation
Legal Cases
Vigilance, Theft & embezzlement cases
Reconciliation of consumer wise opening &
closing balances QTR & Year wise will also be
required

Page 133 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Mis.9 Provision of This module should provide Business Intelligence Essential

Business Tools for data mining, analysis, trending,
Intelligence simulation, manage reporting, OLAP analysis, Ad-
Tools Hoc querying, dashboarding, score carding,
business activity monitoring, Office Integration.

Mis.10 Provision to The system shall generate reports for all the Essential
generate modules in user-defined formats.
reports for all The system will have a graphical user interface
modules in with a capability for generating customized
user defined reports, apart from the regular ones mentioned
formats above, as per the requirement of management and
operations staff. Display of statistical data shall be
presented additionally in graphical formats such as
bar-graph/pie diagram etc. for convenience of
analysis.

Mis.11 Single All BI solutions mentioned above need to be Vital

Platform provided from a single BI platform.

Mis.12 Web Client The application should be web based and there Vital
should be no requirement to install any component
on client machine.
Mis.13 Access of Common service oriented architecture and data Vital
Services access services should be used by all BI features.
Mis.14 Security All BI solutions should have Common Security model Essential
& Support cube level, table level, row and column
level as well as cell level security

An indicative chart for MIS requirement is given below.

Page 134 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Page 135 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Document Management Solution:

Document management solution is a computer system used to track and store electronic documents and/or
images of paper documents; provide storage, versioning, metadata, security, as well as indexing and
retrieval capabilities. It's also termed as document management software or document management tool.
Operating efficiency in utility companies is necessary to decrease liability, maximize capacity, minimize
operating costs, and boost productivity. Companies require integration across suppliers, partners and
customer. The information in the form of documents is required to be shared across the stakeholders for
smooth functioning and maintaining high service levels.
Utilities providers must find ways to: optimize their document workflow, manage multiple technology assets
and, maintain full process integrity and security for invoices and statements. In addition they also need to
implement strategies for customer-centric initiatives and unify disparate systems to offer value-added
services.

Customer Service
Commercial Management

Metering, Billing, Collection Reliability, Quality of Supply

New Connection Billing Accuracy
Payment Mechanisms
Dismantling, disconnection
Loss Reduction Complaint Handling

Information

Network Management Internal Management

Network Planning Finance

Network Construction Human Resources
Network Operations Procurement, tenders, stores
Maintenance and Outages Regulatory

Page 136 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Requirement of Document management solution -

Storage : Every user should have approx 1 GB of storage space so that user can add documents as per their
requirement.
Easy Additions: Adding a new Document should be easy and trouble free so that user can upload the document
file at ease.
Managed Filing: Document filing system can be maintained hierarchy like normal disk based file systems and
also associate multiple taxonomies with the same document or set of documents.
Fast Retrieval: User should be able to search for any document that has been uploaded by name with Full
Text Search of inside any kind of document. Automated Retrieval should also available by popular XML formats
like RSS for every Tag.
Security: Each document must be protected by a granular security system, All Documents must be protected
against theft, loss and tampering. Also should support for archival storage of tier storage, HSM, WORM etc.
devices.
Distribution: The documents must be available in utility’s internal and external portal depending upon utility’s
policy to any user who has access right to it. It should also be possible easily click-to-distribute documents to
select users, user group or even the whole Web Space.
Archival: Automatic Revision control system must be in place that maintains versions automatically, every
time a document is updated. All prior revisions should also be always available.
Retention: The facility of purging prior revisions and permanently deleting stored documents should also be
available to user to protect security of sensitive documents.
File Collaboration: It should be possible to collaborate on any kind of document that is stored within using Ad-
Hoc Workflows of Collaboration.

Benefits of document Management:

Scanning customer documents and other back office files (including meter books, ledgers etc) to save office
space and retrieval time.
Enabling auto storage of documents submitted through website.
Enabling information sharing between different offices, departments and customers
Automating document filing
Scanning of tender documents and automating tendering process.
Automating paper or form based business processes
Implementation of enterprise wide Electronic Data Management (EDM) solutions
Enabling Document security from manipulation, compliance & regulatory norms.
Reuse of content without adding any cost to the organization

Page 137 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Enabling the delivery of content through multiple channel like web, email even mobile devices.
Ensure single & consistent view of documents for various applications
Enabling Information Life Cycle Management of document from generation to archival.
Easy search & access of content using index & full text search based retrieval

Data warehousing and Business Intelligence:

BI applications should include the activities of decision support systems, query and reporting, online
analytical processing (OLAP), statistical analysis, forecasting, and data mining.

Essentially, a BI solution is normally implemented with following components

- An Extraction, transformation and loading (ETL) component which extracts data from OLTP
systems, transforms it and load it to the data warehouse
- A data warehouse component which will host the data.
- A reporting component which will allow on-the-fly reporting on the data from data warehouse.
The MIS should utilise the BI solution and data ware house for management information, data analysis,
reporting and estimating what if scenario

Specific areas which BI should include:

 Customer credit analysis.
 Daily, weekly and monthly report generation to access the performance of sub
divisions/division and circles.
 Load forecasting
 Customer segmentation and analysis for SLAs
 Customer complaint analysis
 Network planning
 Capacity expansion planning
 Accurate manpower planning
 Material Planning

Page 138 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Suggested Technical Architecture of BI -

Reporting
O Data
L Warehouse
T R
P Master Data E
Warehouse P
S
O Users
Y R
S T
T S
E
M
S

The above figure depicts the data flow vis-à-vis the system. As depicted, there are various sources of data
(OLTP systems) from where the data flows to the Master Data Warehouse.
Before loading to master data warehouse, the data goes through cleansing and transformation to maintain
data integrity. Loading process also does simple data aggregation. Once data is loaded to master DW, then it
is again aggregated and loaded to reporting DW. The reports requiring only aggregate data refers only to
report DW but the reports requiring data at most granular level will fetch data from master DW.

Page 139 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Suggested Logical Architecture Diagram

Fig : Logical Architecture Diagram

The logical architecture Diagram can be represented as shown above in figure. It is a graphical
representation of how Webi reports are generated as and when requested by an end user using a
Web Browser.

Page 140 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

9.0 Module: Web Self Service

Objective :
The goal is to provide a high quality experience for the customers and business associates that will provide
them a user friendly portal that will make it easy for them to communicate with the utility though the web
instead of direct phone calls or visits. This portal will also act as a source of information for the customers
regarding policies and procedures. This in turn will improve customer satisfaction and reduce work load on
the employees.

Require Functional Criticalit Respo Comment

Description y nse s
ment ID ity
This page provides a brief description about the site, the
various functionalities it provides and promotional
features or any kind of advertisement for special
C/
programs can be placed in this page. Login Component is
ER/F/
wss.1 Home provided and registered users may login using their Vital
CR/
username and password. New Users can also register by
NC
clicking on the First Time Users Register link. The Forgot
Password link helps the user to retrieve their password.

The Log In page asks the registered users for their

wss.2 Log In username and password while the new members can also Vital
register through this page.
The user is asked for personal, security and account
Registratio
wss.3 information in this page before registering. Vital
n
The user is asked for his first name, last name, zip code,
Forgot birthday and his primary email address before being
wss.4 Vital
Password provided with the security question.

The new password is sent to the user by email (his

Security
primary email address as in his profile) on answering the
wss.5 Question Vital
question correctly.
Answer
Once the user has logged in, he can change his
Change credentials i.e. Username and Password by clicking on
wss.6 Vital
Password the Change Credentials link

This is the landing page for the users with multiple

accounts. The screen contains a brief summary of all the
My
wss.7 accounts such as the account name, address, balance, Vital
Accounts
due date and the account status.

This is the landing page for the customers. The screen

contains a description of the account. Any status
Single
wss.8 messages pertaining to the account involving immediate Vital
Account
user action is also presented here.

Page 141 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

The page provides an account of the usage for the last 12

months graphically. A more detailed analysis is provided
Consumpti
wss.9 in a tabular format listing the meter reading date, the Vital
on History
reading, consumption, number of days, charges etc.

Consumpti The consumption calculator popup is provided to help the

wss.10 on user calculate the usage between any two given dates. Vital
Calculator

The Bill Summary page gives a record of the Billing

Bill
wss.11 amounts and Payments made by the customer over the Vital
Summary
last few months.

Online
The user is provided with the options of registering in
Billing
wss.12 Online Billing and also continues with paper bills. Vital
Registratio
n

The View and Pay Bill page presents a short summary of

View and
wss.13 the bill. The user can also view the bill in PDF format by Vital
Pay Bill
clicking on the link ‘View Bill as PDF’.

The user is provided with 2 modes of payment

namely Credit Card and Debit card On providing the
wss.14 Pay Bill valid credentials payment can be made directly from Vital
the site. The online payment shall be processed
through secured payment gateways

Payments for all the accounts can be directly made from

this page. For each of the account the user is provided
Multiple
wss.15 with 2 modes of payment namely Credit Card and Debit Vital
Pay Bill
card. On providing the valid credentials payment can be
made from the site directly.

Manage The page lists all the accounts for the user and the
wss.16 Essential
Accounts preferences for the accounts.

This page allows customer to lodge request for services

such as new connection, disconnection, load change,
Service
wss.17 name change, category change, meter shifting etc. Vital
Requests
Depending on the regulatory/utility requirements user is
required to submit the documents.

Page 142 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

This is a read only screen which the user can view. Status
Service
of various pending requests for the customer such as load
wss.18 Request Vital
change, name change, category change, meter shifting
Status
etc are listed here.

Under this page user can log his complaint using a drop
wss.19 Complain Vital
down menu and also enter some text.

This is a read only screen in which user can view the

Complaint
wss.20 complaint status. Vital
Status

This screen contains static data related to the power

Report failure. The contact number is mentioned in case any
wss.21 Power power failure occurs. The user calls up the number and Vital
Failure reports the power failure and necessary action is taken to
restore the power connection.

Report This screen allows the user to report any street light
Street outage incident. The user has to fill up the specific
wss.22 Vital
Light information provided in the screen in order to locate the
Outage street light and then report it.

This screen enables the user to update his/her profile

Update information. The user can edit the personal information
wss.23 Vital
Profile and click on Update Changes button to save those
changes.

Commercia
This screen displays the applicable policies, acts and
l
wss.24 rules prescribed by the utility, regulator and the law, Essential
Informatio
which are helpful for customers.
n

Associated This screen provides the link to all the associated sites
wss.25 Essential
Sites such as SERC. CERC, Ministry of Power etc.

This screen displays the information of the contact

Contact Us
wss.26 persons, who should be contacted for any information or Vital
for providing any feedback.

This screen shows the different privacy policies to which

Privacy the web site adheres. This screen displays only static
wss.27 Vital
Policy content. The user can navigate to other pages by clicking
on the bread crumb or the left navigation.

Page 143 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

This screen enables business associates (contractors) to

Business
wss.28 register online, view tenders, purchase tenders, submit Essential
Associate
tenders, etc.

12.0 Module: Identity and Access Management System

Requirem Criticali Respons Comme

Feature Functionality
ent ID ty e nts
Idm.1 Adapter/ connector Support
The proposed solution should be compatible on all
the operating systems offered by the bidder in the C/
Solution
Idm.1.1 proposed solution including client machines which Vital ER/F/
Compatible
are most likely window based system. CR/ NC

Identity management for user provisioning should

have out of the box workflow for automating
approvals for user access management, self
Out of box
Idm.1.2 registration and self-care functionality for Vital
workflow
reducing the administrative load and manual
intervention.

The solution should provide an IDE to design the

IDE to design Desirabl
Idm.1.3 workflows.
Work - Flow e
The proposed solution should support "Workflow
Standard for
Management Consortium (WfMC) TC-1003
Workflow Desirabl
Idm.1.4 Workflow Reference Model standard for workflow
implementati e
implementation".
on
Connector Identity Management Solution should have
availability Connector availability for all target systems that Essentia
Idm.1.5
for target need to be managed. l
systems
The proposed solution Should provide
Connector
resource kit or an SDK to add new Resource Essentia
Idm.1.6 development
adapters. l
tool
Identity Management solution should be Agent-
Agent-less less Architecture and use gateways where agent is Essentia
Idm.1.7
Architecture required. l

The Proposed solution should be certified as

“Liberty Interoperable?” And Should be
Desirabl
Idm.1.8 Certification interoperable with other products / solution
e
based on SAML 2.0 specification. A few typical
profiles given below:

Page 144 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Identity Provider
Identity Provider Extended
Service Provider
Service Provider Complete
Service Provider Extended
ECP
Attribute Authority Requester
Attribute Authority Responder
Authorization Decision Authority Requester
Authorization Decision Authority Responder
Authentication Authority Requester
Authentication Authority Responder
POST Binding
GSA Profile
The solution should leverage an intelligent
indexing system to manage user identities and
access privileges, leaving account information
Essentia
Idm.1.9 Indexing with the information owner and thus avoiding the
l
time-consuming effort of building and maintaining
another user repository.

The Proposed solution should provide an

Discovery and automated way to discover and correlate all
Essentia
Idm.1.10 Correlation of accounts associated with an individual to speed
l
user Account the account mapping process.

The solution should use separate repository for

User Essentia
Idm.1.11 user data and audit log information.
Repository l
Open
The solution should support open provisioning Desirabl
Idm.1.12 Provisioning
standard like SPML. e
Standard

The solution should allow enterprise applications

Authenticatio
and platforms to integrate into the centralized
n/authorizati
Idm.1.13 authentication/ authorization framework Vital
on
seamlessly. The solution should support both thick
framework
client as well as web based applications.

The Access Management solution should be

Access capable of running on web servers as well as Essentia
Idm.1.14
Management application servers. l

The proposed solution should provide the ability

Pluggable for pluggable authentication module, and new
Essentia
Idm.1.15 authenticatio auth modules should be able to be added via an
l
n module SDK.

Idm.2 Access Rights Capabilities and Access Control

Sensitive customers' data must be protected in
Data
Idm.2.1 accordance with guidelines that will be agreed Vital
protection
with the Purchaser.

Page 145 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

On completion of successful logon, the

following information shall be displayed :
a) Date and time of previous successful logon.
b) Details of any unsuccessful logon attempts desirabl
Idm.2.2 Entry screens
since the previous successful logon. e
Reminder of the onus of the user to bring to
notice any aberration observed.

After predefined number of consecutive

Unsuccessful unsuccessful attempts to logon to a user Id, that
Essentia
Idm.2.3 logon user id shall be disabled against further use until
l
attempts the same is enabled by System Administrator.

Terminal / User Id time-out shall occur if a

terminal / user ID remains logged onto a system/
application but remains inactive for a predefined
Application time. If the terminal is dedicated to one
Idm.2.4 Vital
time out application then timeout shall occur after
predefined time inactivity. The screen shall be
cleared of any information when time out occurs.

Software which can be used to modify existing

Limited programs on systems / applications, e.g. editors
application and compilers, shall have access restricted to desirabl
Idm.2.5
software on authorized staff only. Any such software which is e
key systems not needed for operational reasons shall be
removed after the modifications have been made.
Clear segregation of duties between user groups is
necessary to minimize the risk of negligent or
deliberate system misuse. In particular
segregation must be implemented between :
1. Business use.
2. Computer operations.
3. Network management.
4. System administration.
[Link] development & maintenance.
Segregation Essentia
Idm.2.6 6. Change management.
of duties l
7. Security administration.
8. Security audit.
Where it is operationally not possible to adhere to
this policy advice shall be sought from the
Purchaser on security. As a minimum, the above
segregation shall be enforced at the User Id level
i.e. the above functions shall not be allowed from
the same User Id.

A prescribed warning screen shall be displayed

Communicati
immediately after a user successfully completes desirabl
Idm.2.7 ng usage
the logon sequence to any multi user system, e
restrictions
server or database. This does not apply when

Page 146 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

logging onto a PC, which cannot be accessed via

any other means, or when logging onto a network
where no information is available without further
logon (note: the screen should be presented after
this further logon). This screen will emphasize the
requirement to comply with requirements on
usage of computer as laid down by the Purchaser.
The screen will require confirmation that the user
has understood these requirements prior to
proceeding.

The system shall provide a mechanism to

authorize users to access the system, revoke users
from accessing the system, and modify the
Controlling security information associated with users.
Idm.2.8 Vital
User’s access The system shall also be able to automatically
suspend or roll back a reconfigured account that
violates policy.

The system / resources shall provide a mechanism

Restricted to allow or deny specified user IDs to access the Essentia
Idm.2.9 access to system during specified ranges of time based on l
resources time-of-day, day-of-week, and calendar date.

Console
The system shall provide a mechanism to allow
operations Essentia
Idm.2.10 or deny specified user IDs to access the system
for privileged l
based on means of access or port of entry.
users
For each resource, the system shall provide a
mechanism to specify a list of user IDs or groups
Resource, with their specific access rights to that resource
Essentia
Idm.2.11 access (i.e. an access control list).
l
control list Solution Shall provide for grouping of users and
assigning ACL to the group.

Group ACL vs Group ACL should be aggregated to individual

Desirabl
Idm.2.12 individual user’s ACL and in case of conflict, user’s ACL shall
e
ACL govern.

Grant and System shall provide both Grant and Deny to a Essentia
Idm.2.13
deny access resource. l

The system shall have ability to assign users

Individual
individual access rights and to define access rights
Idm.2.14 access rights Vital
available to users in a role upon their request and
to users
approval.

Job based The system shall have ability for different

Idm.2.15 Vital
access to personnel to view different levels of information

Page 147 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

information based on their job duties.

Modifications The system shall provide a mechanism to modify
Essentia
Idm.2.16 to the access the contents of a resource's access control list.
l
list
The System shall have ability to associate access-
rights definition with a role within the
organization and dynamically and automatically
change access rights based on changes in user
Change in
Idm.2.17 roles. Vital
Access rights
The system shall also have ability to set
designated times for changes in access rights or
policies.

System should also use defined rules/ information

Rules for
specific to utility to determine routing of
Idm.2.18 routing Vital
approvals.
approvals
The system shall be able to compare local
administrator changes against a system-of-record
of account states to determine if changes comply
Access rights
with approved authorities and policies and shall
Idm.2.19 change Vital
be able to notify designated personnel of access-
notification
rights changes made outside the provisioning
solution, if any.

Audits on The solution should provide the capability to do

Idm.2.20 user half yearly audits on the lines of ISO Vital
accounts 17799/BS7799 for user accounts.
The system shall provide a mechanism to identify
all resources in the system that are owned by a
Resource Essentia
Idm.2.21 specified user ID, the resources to which that user
ownership l
ID is allowed access and the specific access rights
for each resource.
User’s System shall also be able to detect, evaluate and
Essentia
Idm.2.22 authority respond to user authority changes made directly
l
changes to a resource.
Each resource delivered with the system shall
Restrictive have the most restrictive access rights possible to Essentia
Idm.2.23
access permit the intended use of that resource. l

Restricted
The system shall protect all information used for
access to
resource access control decisions (e.g., access Essentia
Idm.2.24 access
control lists, groups lists, system date and time) l
control
information
The system shall provide policy simulation and
‘what-if’ modeling of changes, i.e. simulation of
Policy effects of policy changes before they are enacted, Desirabl
Idm.2.25
simulation reporting errors, or potential problems, and e
ability to resolve before live operations.

Page 148 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

The system shall monitor the followings :-

Successful logins and login attempts e.g.
Wrong user ID / Password, and login
patterns
Rejected access attempts because of
insufficient authority
Monitoring of
All usage by privilege users e.g. Powerful Essentia
Idm.2.26 access
access to system utilities or applications l
controls
Use of sensitive resources e.g. Access to
highly sensitive data
Change to access rights of resources
Changes to the system security configuration
Modification of the package software
Changes to user privileges.
Reporting on The system shall have ability to report on roles,
Desirabl
Idm.2.27 user roles rights associated with roles and users associated
e
and rights with roles.
Flexible
The system shall have flexible mechanisms to
connection Essentia
Idm.2.28 connect to multiple data stores containing
to multiple l
accurate information on valid users.
data stores
The system shall have ability to load identity
Identity store
store information on a scheduled bulk basis and to Essentia
Idm.2.29 information
detect and respond to identity store changes in l
in real time
near real time.
The system shall have ability to retrieve account
Retrieval of
information from target managed resources on a Essentia
Idm.2.30 account
scheduled basis, both in bulk or in filtered subsets l
information
to preserve network bandwidth.
Real-time
The system shall have ability to detect and report
local
in near real-time local administrator account Essentia
Idm.2.31 administrator
maintenance (creation, deletion, changes) made l
account
directly on local resources natively.
maintenance
The system shall define services that must be
granted prior to creation of the access rights. For
example, Microsoft ® Windows NT ® rights must
Support for be granted prior to granting rights to Exchange
Essentia
Idm.2.32 prerequisite Support for entitlement defaults and constraints
l
services (each characteristic of an entitlement may be set
to a default value, or its range can be
constrained, depending on the capabilities of the
entitlement to be granted)
Idm.3 User Administration
A mechanism must exist to allow a range of User
Creation of Ids to be built with a standard user profiles of
Idm.3.1 standard multiple categories, e.g. Data entry user, data Vital
User Profile modify user at the section office, division office
etc
Dormant Where a user Id remains unused for a pre- Essentia
Idm.3.2
User specified number of consecutive days, it shall be l

Page 149 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

disabled. If no authorized request for

reinstatement is received within a further
predefined time period, the user Id shall be
deleted. The user would be informed before this
happens.
All user Ids shall be set up with privileges that
limit the use of the user Id to designated areas
only and to ensure that other functions cannot be
performed by the user ID for which they are not
authorized. Some user IDs have powerful
Segregating
privileges associated with them and these shall
Idm.3.3 user access Vital
only be provided and maintained by the system
to system
administrator. To prevent the provision of user IDs
with privileges associated to them, when these
are not required by the user, any templates used
to set up user IDs shall have no default privileges
associated with them.
System shall be able to create unique user IDs
using a set of consistent algorithms and defined
policies of the owner and not in current use or
Unique User previous use by the organization and not shared
Idm.3.4 Vital
ID with others.
The system shall provide a mechanism to
associate specified information (e.g., user name
and affiliation) with each user ID.
Procedures for user account management should
ID define the naming convention for user IDs and the Essentia
Idm.3.5
conventions operations practices for provisioning and removing l
these user Ids.
Differentiatin User Ids shall not consist of less than a predefined
g normal and number of characters. The number of characters
Idm.3.6 Vital
privileged would be different for normal users and privileged
users users;
Single
The system shall have ability to create a single
account with Essentia
Idm.3.7 account with multiple authorities governed by
multiple l
different policies.
authorities
The system shall provide a mechanism to
administratively disable user IDs and a mechanism
Temporarily Desirabl
Idm.3.8 for re-enabling or deleting a disabled user ID after
Disabling e
a specified period of time. The use of this
mechanism shall be privileged.
The system shall internally maintain the identity Essentia
Idm.3.9 Active Users
of all active users. l
Tracking User The system shall provide a mechanism to obtain Desirabl
Idm.3.10
IDs the status of any user ID. e
The system shall provide a mechanism that allows
Grouping Essentia
Idm.3.11 a collection of user IDs to be referenced together
User IDs l
as a group.
For those systems that have the architecture to
Limiting
support multiple logons per user ID, the system Desirabl
Idm.3.12 multiple log
shall provide a mechanism that limits the number e
on
of multiple logon sessions for the same user ID.

Page 150 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

The mechanism shall allow limits for user IDs and

groups to be specified. The system default shall
limit each user ID to one simultaneous logon
session. As per business process requirement,
particular machine ID’s to permit login by
selected users only.
The system shall provide a mechanism by which
Associating
the user ID associated with a process can change Desirabl
Idm.3.13 IDs to
to a user ID that would provide any additional e
processes
privileges.
Assignment
The system shall be able to assign users to one or
of one or Essentia
Idm.3.14 more roles and can implicitly define subsets of
more roles to l
access to be unavailable to a role.
users
Idm.4 Self Regulation User Administration capabilities
Adherence to
The system shall adhere to open standards.
Idm.4.1 open Vital
standards
Secure The system shall have secure environment for
Idm.4.2 Vital
environment transmitting access changes across the Internet.
Protection of
Protection of private user information through
Idm.4.3 private user Vital
secure facilities and sound processes.
information
Reports of user rights into external systems,
Reporting of Desirabl
Idm.4.4 sponsors of users and audit trails of access rights
user rights e
changes.
Idm.5 Authentication
Authenticatio The system shall provide a mechanism to
Idm.5.1 n authenticate the claimed identity of a user. Vital
mechanism
The system shall perform the entire user
Single authentication procedure even if the user ID that
Essentia
Idm.5.2 authenticatio was entered was not valid. Error feedback shall
l
n procedure contain no information regarding which part of
the authentication information is incorrect
Modification
The system shall provide a mechanism to support
Ability to Essentia
Idm.5.3 the initial entry or modification of authentication
authenticatio l
information.
n information
Privileged
The system shall require a privilege to access any
access to
Idm.5.4 internal storage of authentication data Vital
authenticatio
n data
2-Factor
System should support two factor authentication
Idm.5.5 Authenticatio
(Biometrics, tokens etc.)
n
Password Management
Idm.6

Password System shall be able to securely deliver User Ids

Idm.6.1 Vital
confidentialit and passwords to new users electronically.

Page 151 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

y User Ids and passwords, when conveyed

electronically shall only be visible to the person
for whom they are intended e.g. after the user
has logged on to the appropriate electronic
system.

All electronic information systems and

applications shall have a password management
system which meets the following requirements
:
a) Enforces change of initial password at
first logon.
b) Allows users to select and change their
own passwords at any time subsequently.
c) Have ability to implement password
formation rules to enforce password
strength across the organization, e.g.
minimum character length of password,
password as a combination of numeric,
alphabets & special characters
d) Have validation routines built in which, as
far as possible, check that the password
selected is a quality password as defined
in a Policy Document to be handed over to
the Purchaser at the time of
implementation.
e) have a confirmation process on changing
passwords to cater for typing errors,
Password Essentia
Idm.6.2 f) have ability to deliver password-change
protection l
success/ failure status to requestor
electronically
g) have the ability to enforce password
change after every n days. if the password
is not changed in the pre specified
number of logins then the ID should be
disabled requiring re-enabling by System
Administrator.
h) prevents reuse of passwords within a
specified period.
i) does not echo passwords to screen or
paper.
j) Stores passwords in a one-way encrypted
form away from the system/ application
data files in a protected password file that
is access controlled such that no users can
read or copy the encrypted contents.
k) Prohibit use of null passwords
l) Have ability to synchronize passwords for
multiple systems to the same value to
reduce the number of different passwords
to be remembered by the user

Page 152 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

m) Have a challenge-response system to

authenticate a user with a forgotten
password by using shared secrets
The system shall provide no mechanism whereby
multiple user IDs explicitly shares a single stored
Unique
Idm.6.3 password entry. The system shall provide no Vital
passwords
means to facilitate the sharing of passwords by
multiple users.
The system shall allow a user to choose a
password that is already associated with another
Clearing Essentia
Idm.6.4 user ID. The system shall provide no indication
passwords l
that a password is already associated with
another user ID.
Directory Services Requirement for Enterprise
Idm.7
 The Directory Server should be LDAP v3
Compliant.
LDAP and  LDAP server should be able to replicate data
Essentia
Idm.7.1 Open between servers and support cascading
l
Standards replication.
 Should have support for open standards (LDAP
v.3, XML)
 The directory service should provide support
for Group policies and software restriction
policies.
 The group policies should have settings to
configure various desktop or user related
Group
settings via centralized control. These
Idm.7.2 Policies Vital
settings will include items like Browser
Management
setting, desktop restrictions, program
restrictions, admin controls, software
deployment etc. It should allow for almost all
manual functions to be automated using group
policies.
 Should have support for integrated
authentication mechanism across operating
system, messaging services.
 The Directory server should have out of the
box integration with the e-mail server.
 Should provide enhanced authentication like
Essentia
Idm.7.3 Integration Kerberos which support authentication across
l
multiple Operating system like Windows and
Unix/ Linux.
 Should be able to integrate with other
standards based Directory system for
synchronizing user accounts and passwords.

 SNMP support for flexible network monitoring

and management.
 Should support directory services integrated Desirabl
Idm.7.4 Management
DNS zones for ease of management and e
administration/ replication.
 The directory service should support features

Page 153 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

for health monitoring and verifying

replication.
 The directory service shall provide support for
modifiable and extensible schema.

 Support for Access Control Lists (ACLs).

 Support for controlling access to the
directory, a subtree, entries, attributes by
Access setting permissions for users, groups, roles Essentia
Idm.7.5
Control and location information like IP addresses. l
 Should provide facility to provide Rights
Management Service for documents like Word,
Excel etc on the built on standards like XRML.
 Support for user authentication through user
ID/ password, X.509v3 public-key certificates,
Multi Factor
or Anonymous authentication
Idm.7.6 Authenticatio Vital
 Should support security features such as
n
support for Kerberos, smart cards, public key
infrastructure (PKI), and x.509 certificates
 Should support participating into multiple
LDAP Repository architectures for scalability
High  Should support LDAP servers in multi master Essentia
Idm.7.7
Availability configuration l
 Ability to keep Replicas in Synch and to
enforce Replication updates.
 The solution should provide a comprehensive
single window Admin tool locally or over
internet to administer the directory services.
 The Directory Services should have APIs to
Administratio Essentia
Idm.7.8 programmatically manage each component of
n l
Directory Service.
 The directory service shall provide support for
modifiable and extensible schema both
manually and programmatically
Idm.8 Audit Trails & Reports
The system must maintain-
Time-stamped records of every access change
Time-
request, approval/denial, justification and
Idm.8.1 stamped Vital
change to a managed resource
records
Time-stamped record of every administrative
and policy-driven change to access rights
The system must provide reports on audit trails
for users, systems, administrators and time
periods, including workflow approvals,
Audit Trail Essentia
Idm.8.2 rejections, request statistics, policy compliance
reporting l
and Audit reports, User account reports, Access
reports and Service reports and also any
customized reports based on specific need.
Audit trail records shall be retained in a tamper
Maintaining proof environment in accordance with the
Idm.8.3 Vital
audit trails Purchaser’s policy for a reasonable amount of
time to allow for accountability and evidential

Page 154 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

purposes. Backup copies shall also be maintained

to protect against any accidental or deliberate
erasure of data.
Idm.9 Distributed Administration
Defining of Ability to define organizational structures based
Desirabl
Idm.9.1 organizationa on the access-granting authority
e
l structures
Ability to delegate each administrative task with
Delegation of fine-grained control at Organizational Unit Level
Essenti
Idm.9.2 administrativ so that the team or Dept Admins can completely
e tasks perform the Administrative tasks for their al
Organization Unit.
Access to Ability to access all delegated capabilities over
delegated the Web via Web Browser with a zero-footprint Essentia
Idm.9.3
capabilities client. l
over web
Ability to incorporate Web access control with
Web access single sign-on environment and to distribute
control with provisioning components securely over WAN and
Idm.9.4 Vital
single sign-on Internet environments, including crossing
environment firewalls.

Ability to incorporate Enterprise Single Sign On

Enterprise products to include the provisioning solution
Idm.9.5 Single Sign within the Thick client single sign-on Vital
On products environment.

Ability to incorporate custom user authentication

Custom user approaches commensurate with internal security
Essentia
Idm.9.6 authenticatio policies and to create private, filtered views of
l
n approach information about users and available resources.

Ability to
Ability to import and export configurations to
import and
enable migrations between Development, Staging Desirabl
Idm.9.7 export
and Production environment without delays. e
configuration
s
Idm.10 System Operations
interaction Ability to interact with target resources without
Essentia
Idm.10.1 with target interfering with their performance.
l
resources
Operation for
Ability to continue to operate without
temp Essentia
Idm.10.2 degradation when the managed system is
inaccessible l
temporarily inaccessible.
system
Function if
Ability for the managed resources to remain fully
provisioning Essentia
Idm.10.3 functional if the provisioning solution is
solution l
unavailable
unavailable
Users Responsiveness to users interacting with the
Desirabl
Idm.10.4 interaction provisioning solution features for searches,
e
with reporting, approvals, self-service and auditing.

Page 155 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

provisioning
solution
Ability to load and maintain synchronization with
synchronizati
user information from existing human resources Desirabl
Idm.10.5 on with user
and other identity systems, both statically and e
information
dynamically.
account and
Ability to load account and authorization
authorization
information from existing operational systems Essentia
Idm.10.6 information
without data entry l
from existing
systems
Reconcile Ability to detect and reconcile accounts created
accounts by, and/or changed by, other administrative
Essentia
Idm.10.7 created by systems (e.g., the local administration console
l
other adm. provided with the managed resource)
systems
Support for
Support for configuration and scalability
configuration
requirements for large environments and high- Essentia
Idm.10.8 and
availability operations utilizing shared l
scalability
communication capacity on corporate WANs.
requirements
End-to-end End-to-end security over account changes.
Idm.10.9 Vital
security
Web-based Entirely Web-based functionality to allow easy Essentia
Idm.10.10
functionality distributed administration on an unlimited scale. l
Integrated
Integrated functionality that does not require
functionality
duplicate data entry or manual synchronization of Essentia
Idm.10.11 w/o
information shared for multiple functions. l
duplicate
data entry
Server
configuration Ability for servers to be inexpensively configured
Idm.10.12 for high for high-availability operation, including disaster Vital
availability recovery.
opn.
Utilized data
store
Ability for utilized data stores to be configured
configuration
Idm.10.13 for high-availability operation. Vital
for high
availability
opn.
Accuracy in Ability for provisioning solution to maintain
Idm.10.14 provisioning accuracy when local administrators maintain Vital
solution privileges to make changes to target resources.
Resilient Resilient communications design between
Desirabl
Idm.10.15 communicati distributed components to withstand network or
e
ons design target resource outages.
Multilayered security architecture for operation in
Multi-layered a “demilitarized zone ” ((DMZ) and for
Idm.10.16 security management of users and systems in untrusted Vital
architecture environments.

Page 156 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

interaction XML-based extensibility and interaction with

Desirabl
Idm.10.17 with external external systems
e
systems
common and Use of common and de facto standards for
Desirabl
Idm.10.18 de facto interfaces that are internal and external to the
e
standards provisioning solution.
Integration Integration of LDAP directory services as identity
of LDAP stores, access control system authorization stores Essentia
Idm.10.19
directory and internal user account and policy stores. l
services
audit trails
Inclusion of a persistent data store or repository
Idm.10.20 and system Vital
for audit trails and system recovery.
recovery
Quick Ability to respond quickly to user interactions
response to including report requests, access change requests, Essentia
Idm.10.21
user policy changes and password self-service. l
interactions

Page 157 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

11.0 Module: System Security Requirement

Require Critica Respon Comme

Functionality Description lity se
ment ID nts
Ss.1 Audit Trails and Reports

Ss.1.1 Tracking key The system must be capable of generating Essenti C/

system accesses log trails, which contain details about any al ER/F/
read / write access to sensitive data. Details CR/ NC
must relate activity to an identifiable person.
They must be configurable, so that filters
and switches can be used to lower
performance overheads and focus on areas
of concern. It is important that the audit trail
that is generated contain enough
information to support after-the-fact
investigation of loss or impropriety.
Ss.1.2 Time-stamp Where equipment uses a real-time clock to Essenti
based auditing timestamp audit and other time related events, al
method the clock should be regularly checked for
synchronization with both connected systems
and reference clock outside of the system, in
this case the Indian Standard time. For daily
reporting, this would ensure that the reports
generated have some sanity given continuous
data input

Ss.1.3 Exception Where the security audit trail becomes Vital

reporting unavailable for any reason, the system shall
continue to operate but will trigger an alarm.
Action shall be taken as soon as possible to
rectify the situation

Ss.1.4 Detailed system System and application use and attempted use Essenti
access tracking will be monitored to ensure that the integrity al
and security of the client and customer data is
maintained. The documented process shall
include details of: who will monitor what event
and how, the frequency of monitoring, what to
do when suspicious activity is noted, when to
escalate and the escalation path. All events
logged in the audit data shall be taken into
account when deciding what to audit and the
appropriate actions to take. The log must
record the user or process responsible for the
event, terminal ID where available, and the
date and time of the event The following shall
be monitored :-
Enabling and disabling of the audit process
Any changes to the type of events logged

Page 158 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

by the audit trail

Any changes to the audit trail itself
Start up parameters and any changes to
them
System or application start-up and shut-
down
Use of selected transactions
Changes to any of the data base or
records
Ss.1.5 Audit records and journals shall be retained in a Vital
Maintaining audit tamper proof environment in accordance with
trails the Purchaser’s policy for a reasonable amount
of time to allow for accountability and
evidential purposes. Backup copies shall also be
maintained to protect against any accidental or
deliberate erasure of data.

Ss.1.6 A recovery options analysis shall be carried out Vital

to produce the practical options for those
Disaster systems and networks, which are deemed to
recovery require recovery in the event of a disaster. The
most effective option shall be chosen, taking
into account the cost of recovery and the cost
to the business of unavailability of the
application.

Ss.2 System Integrity

Ss.2.1 User process The system should be able to protect the user Essentia
protection process and local data from other user. l

Ss.2.2 Version Mechanisms should be in place to ensure that Essentia

consistency the currently installed software has remained l
checks consistent with the delivered product.

Ss.2.3 Versioning Software used on systems/ applications shall be Essentia

subject to version and change control to ensure l
that only the current authorized software is
used at all user location.
Ss.2.4 Modification of Modification or replacement of the software Desirabl
the system provided with the system would require special e
privileges
Ss.2.5 System Execution of system maintenance and repair Essentia
maintenance software would require special privileges l

Page 159 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Ss.2.6 Basic checks on Data input to an application shall be validated Vital

data input by the application to ensure that the data is
correct and appropriate. As a minimum, an
application shall check input data is complete.
within the required ranges, and contains no
invalid characters. Procedures shall be
established to deal with any input data
violations.
Ss.2.7 Time stamping The system should be able to track the date Essentia
modifications and time at which a resource was last modified. l
Ss.2.8 Integrity of data The system should have in-built mechanisms Vital
passed over a e.g. checksums to verify the integrity of data
communication passed over a communication channel.
channel

Ss.2.9 Data transfer lock Where an encryption process used for data Essentia
transfer fails and cannot be automatically l
corrected, then the transfer should not be
completed.

Ss.3 Confidentiality
Ss.3.1 Use of The system should have the flexibility of Essentia
encryption encrypting the data stored online. l
Ss.3.2 Approval for Any cryptographic techniques or encryption Essentia
cryptographic systems used to safeguard information shall l
techniques have been approved by relevant authority on
data security prior to their use.

Ss.3.3 Approval for Only security components which have been Essentia
security approved by the Purchaser shall be used to l
components protect the Purchaser's sensitive information
and processes.
Ss.3.4 Documentation of The procedures used to maintain confidentiality Essentia
encryption should be documented and access to them l
procedures restricted.

Networking and Data Transfer

Ss.4

Ss.4.1 Authorized data All data transfers must be documented and Vital
transfer authorized by the owner of the donor system.
They must only be authorized where the
receiving system has the capability to protect
the data, i.e. it has an acceptable security
rating.
Ss.4.2 Inter system data Data which is to be passed between systems Essentia
Transfers shall be labeled to indicate the type and l
sensitivity of that data. The security policy for
a system will state what data may be sent to,
or received from, another system and will state
the translation, if any, between the labeling of

Page 160 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

the two systems.

Interfaces that have been built - i.e. the data
migration systems should have defined access
rights.
The interfaces should have a fixed enabling
procedure - including the frequency with which
the migration happens to and from the system,
the data flow that would happen and the data
items that would be frozen during such a
migration.
Customer needs
Ss.5

Ss.5.1 Documentation of System developers responsible for Essentia

risks and its customization should consider and document l
mitigation the risks and associated mitigation in the
strategy design.

Ss.5.2 Installation and Developers will document instructions on how Essentia

configuration the system is to be delivered, installed and l
configured in a secure manner.

Ss.5.3 Startup Developers will document instructions for the Vital

documentation secure start-up, re-start and operation of the
system.

Ss.5.4 Interface Interface designs must include the capability to Essentia

designing selectively deny access to certain types of data. l
Ss.5.5 Scope control Vendor supplied software packages must not be Essentia
modified outside of the scope recommended by l
the Purchaser.

Ss.5.6 Software change A mechanism for controlling software changes Essentia

control during development shall be implemented. This l
mechanism shall as a minimum ensure that :
a) The change is reviewed by appropriate
groups prior to authorization,
b) Changes are properly authorized prior to
implementation,
c) All change requests are logged.
d) All associated documentation is altered
along with the software change.
e) Version control records are maintained.

Ss.5.7 Internal data All applications shall be designed to minimize Essentia

the risk of corruption by processing errors by l
building in validation checks, reconciliation
checks etc. , where necessary.

Page 161 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Ss.5.8 Module and All new and modified software to be used on Essentia
product testing system/application shall first be tested by l
expert personnel to ensure that the software
have been subjected to the rigor of test and
thereby -
a) Does not introduce added security risks
b) Functions according to design
specifications
c) Does not adversely affect the operation of
the system
d) Introduces no unauthorized system
changes.
Ss.6 Security of web services

Ss. 6.1 XML based Web As web services have certain limitations with
security schemas SSL type of security scheme, the web service
technology shall be used with different XML-
based security schemes. Some of the XML-based
securities include the following: -
 WS-Security
 XML digital signature
 XKMS (XML key Management
Specifications)
 SAML (Secure Assertion Markup
Language)
 ebXML Message Service
The bidder shall ensure content security,
message level security and secure message
delivery, meter data security policy, trust
management and secure public key
infrastructure while implementing web services
using appropriate web security mechanism,
which must be W3C/ OASIS compliant.

Page 162 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

SECTION – G2 : PART-B

APPLICATION PACKAGES FOR COMMERCIAL

OPERATION, viz. M, B, C

Page 163 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

12.0 Module: Development of Commercial Database of Consumers

The Commercial Database of Consumer is to be developed based on the Consumers Billing Database available with the
Utility and the GIS based consumer and asset data base developed/being developed. The system to be developed and
installed under this specification shall be capable of accepting the data as will be made available and capable of
appending any necessary attribute etc. and performing the entire intended task. After the first installation, the
database shall be updated online and taken into the system for routine functioning.

a) The commercial data base development shall cover the following activities-
- Development of Master File of consumer comprising of consumer’s details including Energy meter history
as per Annexure-G of Section-G6 of this specification ,
- meter reading,
- energy consumption,
- assessment,
- payments and
- other relevant data from the initial record and other relevant records to be provided by Utility.
 Data model should support complex billing operations such as single bill for a customer having
more than 1 connection and other such operations which require customer information at various
layers.
 In case of consumers on computerized billing system, data shall be provided in the form of soft
copy as far as possible.
 In case of consumers billed manually or new connection, data will be provided in the form of
manuscript as per standard card code system.
b) Development of well-designed layout / formats for Master Information Data in soft copy for easy reference
and access, to be approved by Utility. The layout / formats will be properly defined and documented for
reference to facilitate Data Management and print out as and when required.
c) Updating of consumers’ master file on the basis of the transaction advice from respective source from time
to time in respect of energy consumption, payment made and any other changes to affect required
modification in the Master Data.
d) Undertaking consumers’ master file listing in the prescribed format, compilation of corrected master file
at the initial exercise of master file creation as detailed against ‘a’, ‘b’ and ‘c’ above, incorporating such
corrections to consumers’ master file on subsequent repetitive processing as detailed against item ‘c’
above, so that at any time master file of consumers and listing of such corrections / additions represents
the correct status of consumers file record for reference.

Page 164 of 212

 Edited by Foxit Reader
Copyright(C) by Foxit Corporation,2005-2010
For Evaluation
TAMIL NADU ELECTRICITY BOARD Only.
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

e) Utility shall be providing the existing customer related information as available on records for starting the
billing activity. In the Commercial Database available with Utility each consumer is allotted a Service
Connection Number and Book Number. While developing database care is to be taken that each consumer
is allotted unique identity number (generated during consumer indexing) so that with the help of that
identity number it should be possible to identify the Consumer, Feeder, Distribution Transformer and the
Substation feeding the consumer. Application should have the provision of bifurcation of one section into
many and vice versa while maintaining the relationship between the old and the new consumer details.
f) All data related to a consumer must be captured in database v.i.z. Consumer S.C Number, premise
number, e-mail ID, Name, Meter number and make, CT/PT ratio, date of installation, date of testing, name
of personnel employed for checking and sealing, billing address, supply address, phone number, customers
tariff category, contracted load, special consumer status (like hospital, water works, govt. offices etc.)
etc.
g) GIS based index database has structured customer information on GIS based map with electrical system on
the fore ground and all the Consumers are being coded and segregated 11 kV feeder wise and Distribution
Transformer wise. In the Commercial Database to be developed, care has to be taken that Consumers are
segregated Distribution Transformer wise, 11kV Feeder wise and 33/11 kV Substation wise so that there is
no problem in Energy Accounting. More over any change taken place in customer information related to
electrical network equipment due to addition/ modification of network in the base GIS system, the
commercial database shall be automatically updated.
h) The agency developing the system software shall provide with easy and convenient platform to integrate
his software system with indexed Geographical and Electrical Database. The two systems (i.e. Customer
indexing cum asset mapping system and billing system software) have to work in total unison such that
any revision of data in one of the system should automatically update into related information in the other
without any conflict. Wherever there is limitation on account of any cross system interaction, it has to be
resolved and debugged by the supplier to the complete satisfaction of Utility.
i) System must be able to support operations for variety of consumer like residential, industrial, commercial
government, agriculture etc. History of consumption and payment for every consumer must be maintained
even after account is closed or interrupted for a period of 10 years or as may be mutually decided with
UTILITY.
j) Complete data of the entire system for the past 2 years must be available on server. Data of prior period
must be available on external media, which can be loaded on server as and when needed.
k) The Commercial Database to be developed should be capable to interface with the Geographical and
Electrical Database with the S.C. No. of the consumer being the link key between the two databases.
Provision should be there that interfacing of the database should be possible with any other system that
may be developed at a later stage.

Page 165 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

13.0 Module: Metering

Objective: An Effective meter reading system would enhance the effectiveness of the measurement
process. This would include accurate metering for all customers and tapping revenue loss through the
identification and handing of exceptions.

System Boundary: From: Consumption detail capturing To: Providing final reading
Specification Metering
Requir
Functionalit Critical Respons Comment
ement Explanation
y ity e s
ID

All the input points to the circle and feeders &

related distribution transformers are having
Collecting
electronic meters. The data of all such meters
meter
will normally be downloaded on a central
readings in
server located at data centre. The system C/
the
M1 should also be capable of interfacing with Spot Vital ER/F/
metering
billing devices and MRI data for uploading such CR/ NC
database
meter readings including consumer meter
from remote
readings. The detail specification of system
meters
meter data acquisition is in separate chapter
as ‘data logger’

System should provide data validation checks

to minimize data entry errors. It should
incorporate user supplied logics to check
variations in consumption and generate
exceptions. After data entry, the system
should generate an Exception Report for non
reading of meters due to any reason. A typical
list of such exceptions has been listed at
Annexure-F of Section G-6. It shall also
Data highlight possible inconsistencies in the
M2 Vital -do- -do-
Validation metering data. After handling of exceptions
by the respective officials, the system should
be updated with the result of exception
handling. While validating if the meter reading
found low / unacceptable based on earlier
readings/trends the system should issue a work
order for checking and replacement of meter.
If the work orders are not closed with valid
reason system should escalate the issue till the
same is resolved

Essenti
M3 Data Review The system should provide the facility for the -do- -do-
al
designated officials to review the metering

Page 166 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

data as per utility defined criteria. In case any

discrepancy is found, the system will allow the
data to be edited, with proper access rights
and audit trails.

The system should be able to interface with

Automatic online Meter Reading devices.
System should be capable to schedule and
AMR collect automatically readings from online
Essenti
M4 Compatibilit connected consumer meters / Distribution
al
y Transformers meters through automatic meter
reading system. The system should generate
exception in case meter reading found
unacceptable after validation check

The system should be capable of capturing

meter reading data from a Meter Reading
Book, handheld computers/CMRI used for spot
metering & billing for uploading and
downloading the data.
Capturing System should be capable to upload and
Meter download the data for a given set or group of
M5 Vital
reading consumers to CMRI/HHC automatically. System
Data should also keep log of CMRI Device/HHC
assigned to meter reader.
The system should have provision for storing
check readings which can be used for
assessment and analysis purposes, however this
would not be utilized for the billing/utilized
case to case basis.

The system should be able to transfer or

Validations update the meter reading validation logic to
for the MRI and spot billing machines. The system
the spot should have the flexibility of validating the
Essenti
M6 metering data uploaded from the meter reading
al
and billing instruments. The validation would include
data restricting the customer data uploads to those
updated that were indicated in the meter reader's
schedule.

The system shall also have provision for

Prohibiting
prompting the Meter Reader at the time of Essenti
M7 the wrong
entering wrong meter reading values in the al
entry
spot billing machine.

Page 167 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

System should generate meter-reading plan for

day / week / fortnight by meter readers and
provide it to the respective authorities. For
generating meter reading plan system should
take care of no of meter readers available with
the customer and their productivity for
coverage of all meters before due date. The
business logic shall be provided by owner and
owner should have a flexibility to modify the
same. After generation of plan the same shall
be sent to respective offices by e-mail/other
mode, so that the meter reader can download
the site/premise addresses of the meters to be
read on that day.

The system should be capable of-

i) Assigning individual MRIs to individual
Readers to track their performance.
Meter
ii) Generation of optimum route plan using Essenti
M8 reading plan
the capabilities of the GIS and based on al
generation
reading jobs (including re-reads if any) to
be read in a given cycle in a given
area/route to maximize the productivity of
meter readers.
iii) Optimization of meter plans whenever a
new connection is "inserted" in a route, or
an existing connection is disconnected and
"deleted" from the route.
iv) Reading plan should include disconnected
connections also based on logic, and should
exclude the same based on instruction
from authorized user; reader should not be
able to know from MRI whether a
particular connection on his reading plan is
supposed to be live or disconnected, for
the purpose of tracing the connections
wrongly marked disconnected where meter
may still be at site.

The system should make it necessary for the

meter readers to upload all the meter readings
according to the itinerary generated within the
timeframe stipulated by the utility. Otherwise
exceptions should be generated and further
Monitoring meter reading can be entered only after
Essenti
M9 meter clearance from specified authority. The system
al
reading plan should track and generate the exception
reports, for each meter reader to establish
performance measures and determine
deviations if any. It may include No. of meters
planned, no. of meters actually read per day,
no. of wrong readings, unread meters by
reason etc.

Page 168 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

The system should be able to track customer

Monitoring
behavior in terms of exceptions. For example: Essenti
M10 Customer
The number of times a customer figures in the al
exception
list of exceptions.

The system should also have the facility if

desired by utility to enter the meter reading as
specified by the customer by telephone/ fax/
Supporting web portal and record that the same is
meter customer-specified. All customers who provide Essenti
M11
reading on a reading on trust, should be inspected after a al
trust Utility specified time period. This would mean
that a customer providing a reading on trust
would be inspected once every 6/12 months
for instance.

In case a meter reading becomes overdue

Overdue
M12 (Utility specified criteria), the system would Vital
alert
generate the necessary exceptions and alerts.

Accepting
The system should be in a position to cater to
change in Essenti
M13 changes in the metering cycle. Metering in
metering al
certain cases maybe TOD, hourly, daily,
cycle
fortnightly etc.

Capability
to store The system should keep past metering data
M14 data for a online for a period specified by the Utility & Vital
specified SERC guidelines from time to time.
period

The system will support data downloading to

and uploading from handheld devices used for
Interfacing Spot metering & billing and MRI. The devices
with spot would provide information about the meter
M15 billing and number, customer code, meter reader's Vital
MRI employee no, meter reading with date and
instruments time stamping, billing amount, collection mode
and collection amount in case the collection is
made at the consumer premise itself.

Meter
The System should be capable of accepting
reading for Essenti
M16 opening, closing and intermediate meter
temporary al
readings for temporary connections for
connections
generation of bills for such connection.
M17 Essenti

Page 169 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

Final meter For all kinds of disconnections (whether a al

reading for customer requests for termination of
closure of connection or utility disconnects due to non
connection payment), the system should accept the
terminating meter reading (which will be out
of cycle in most cases) for generating the last
bill.

System must be capable of capturing complete

meter history throughout meter’s lifecycle,
starting from arrival in stores to type, Make.
Model, Batch, Catalogue Number of meter, its
place of installation, cycle and record of
Lifecycle calibration/testing till it is being scrapped or
monitoring destroyed. System must be capable of
Essenti
M18 and testing capturing data like ordinary meter, electronic
al
plan for meter etc. System must be able to identify the
meters meters, which are due for mass replacement or
scheduled testing/calibrations and generate a
work order for action by field staff. It is
desirable that system should be able to
interact with meter testing devices for
obtaining test report

System should be capable to monitor and track

the following :
MIS
M19 Meter reader’s performance, Vital
generation
Comparison of input versus expected
consumption, variance in consumption for
consumers etc.

Current location of meter must be tracked i.e.

Tracking
in stores, under testing, at consumer premise, Essenti
M20 meter
under overhauling etc. Data must be captured al
location
at appropriate locations and point of time to
track the meter.

The system will track the current status of the

Tracking
meter. Various options would include Correct
M21 meter Vital
Meter, Stuck-Up Meter, Sluggish Meter, Door
status
Lock etc.

Tracking
Tracking & reconciliation of meter seals i.e.
meter/mete Essenti
M22 date, type no. of seals, sealed by condition of
r boxes al
meter etc. including meter boxes.
Seals
The system shall be capable to prepare the
Vigilance
M23 vigilance report at site. Format will be Vital
Report
finalized during implementation.

Page 170 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

The system shall be capable to track the

Tracking the Essenti
M24 consumer who has been found to frequently
consumer al
indulge in theft and malpractices.
Tag the The system shall be capable to tag the
M25 consumer consumers / non-consumers / location / site on Vital
on GIS map GIS map who was found to commit the theft.

Page 171 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

14.0 Module: Billing

Objective: A comprehensive billing system will ensure that the utility efficiently bill their customers for
the services rendered. It should support the continuous billing to reduce the outstanding. Ensure the
timely and accurate billing. The system will support the complaints handling functionally by providing
short turnaround times for billing related customer queries.

System Boundary: From: Accepting Consumption data To: Providing reminder letters
System Functionality: This system should broadly cover functions relating to generation, printing and
issue of bills to the consumers. Specifications for various billing types, tracking of reasons for deviations
from normal billing, billing logic flexibility etc. are some of the features that the system should address.

Specification Billing
Require Functionality Description Criticality Response Comment
ment ID s
B1. Unique Bill No All bills generated by the system should be Vital C/ ER/F/
given a unique number CR/ NC
B2. Format of bill The logic for defining the bill number would Vital C/ ER/F/
number be flexible and provided by the client. For CR/ NC
example the system should be capable of
generating bill numbers that are reflective of
the Section Office, Subdivision, Division etc
that the customer falls under. It should also
capture the customer category and the billing
month.
B3. Bill Calculation The Utility would provide the billing logic for Vital C/ ER/F/
-Billing Logic generation of bills. This calculation logic will CR/ NC
flexibility be flexible and the utility should be able to
revise the billing logic from time to time
depending upon the modifications in
regulations, tariffs, etc. It should be possible
to make these changes from a central
location. It should be possible to manually
modify the billing logic on a case to case
basis, with alerts and within specified limits.
The system should follow the same for
computing the final bill amount and should
generate bill in soft and hard forms for the
all type of requisite customers with certain
pre-defined periodicity. The periodicity may
also vary from generating continuous bills for
spot billing to bills once a year for particular
type of customers like agricultural customers.
The system should have the flexibility of
defining the periodicity in bill processing.
The system should have the capability to
generate the bills either in batches or
individually.
System should also accept billing logic for

Page 172 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

consumer purchased meters. Suitable rebate

as per rule be provided for consumer
purchased meters.
System should have provision of -
i) Auto-credit of penalty specified by SERC
for Utility in case of deficiency of service
to the consumer
ii) Putting a certain bill amount under
deferral due to stay order from court till
the matter is decided.

B4. Transfer in System should also support prepaid metering Essential C/ ER/F/
billing logic and billing system, if implemented by utility CR/ NC
later on and should permit seamless transfer
of existing customers from -
i) post-paid to prepaid regime and back
ii) Unmetered to metered regime
iii) kWh based billing to KWh & kVArh based
billing regime and back

B5. Meter data The system shall be capable of identifying Vital

validation meter tampering data as per utility defined
criteria and generate flags for operator
intimation and further investigation. The
billing system shall be capable of identifying
faulty meters and preparation of bills
considering a defined algorithm for
estimation of consumption during such
periods of meter faults. The bills shall
indicate the estimated consumption
separately.
System shall also incorporate multiple meter
changes in a single billing cycle, properly
accounting old meter final consumption
based on final reading (or assessment if
functional reading is not available)

B6. Bar code System should be capable of automatic Vital

generation generation of bar code and printing on the
consumer's bill Using Code-39 or any other
Universal standard; capable of generating
Alphanumeric and all the special characters
available on 'Microsoft-Word', Additional
Capability to generate output in 'local
language' script will be preferred.

B7. Billing logic System should be capable to download the Vital

download billing logic to CMRI/HHC to facilitate spot
billing at consumer premises using HHC/CMRI
as and when required.

Page 173 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

B8. Bill printing System must be able to automatically select Essential

based on and print those bills together in a desirable
dispatch sequence for ease of distribution, which are
sequence under same reading cycle/group, convenient
for walking order of meter readers/bill
distributors.
B9. Group billing System should allow for generation of Essential
common bill for a set of consumers with same
or different due dates.
The system should also have provision for
generation of bill of multiple premises on a
single bill for a single customer, if the
customer has opted for the same.
In case of advance payments the system
should have a logic for adjusting such
payments with the bill amounts of the same
set of consumers with same or different due
dates.
B10. Bill printing System must support bill processing and Essential
flexibility printing either at workstation location or at
the base billing center.
B11. Use of pre System must be able to print the bills either Vital
printed on pre-printed stationary or plain paper in
stationary Hindi/English/Local language as per
directions of Utility.
B12. Interfacing with The system should have the flexibility of Vital
manual billing capturing inputs manually to update the
customer database on bills that have been
manually generated, with a reason for the
same. Such updates should be limited to
specific logins.
B13. Bill on demand The system should be capable of generating Essential
bills on demand by the customers. The
system should have the provision of
generating duplicate bills on demand from
the customer - and have the provision for
accepting payment details for the same.
The system shall have provision to print
duplicate bill of any past bill up to last 3
years (applicable after the software is rolled
out)
B14. Bill correction/ The system should have provision for Bill Essential
amendment correction/amendment manually to update/
provisions modify the customer billing database, with a
reason for the same. Such bill amendments
should be limited to specific logins.
The system shall employ separate accounting
process for bill amendments, which results in
reversal of sales (Unit and Rs) booked (bill
raised) in past financial years, i.e. prior to

Page 174 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

start of current year.

B15. Change of The system will have the capability to change Essential
billing cycle billing cycle of a consumer. The changes
would include - shifting to another cycle and
increasing or decreasing the frequency of
billing.
B16. Interfacing with If there is some special scheme for payments Essential
special drives (e.g. Installments), then the system will
generate the bills taking into account the
special scheme provisions. Also, there would
be codes for all the Schemes, so that the
system can track their usage. There would be
codes for all the Schemes so that the system
can track their usage. The system will keep a
record, as to who authorized the scheme
(e.g. installment) and capture the details of
the scheme.
B17. options for System should have options for level Desirable
level payments payments where in the customer can pay a
fixed amount per month. In such a scheme,
system should also provide for balancing the
charges at the end of the year for any
variations between the calculated amount
(Fixed amount) Vs the actual charges the
customer has incurred.
B18. Penal Billing for System should have provision to compute Vital
unauthorized penal billing for unauthorized use of
use of electricity, as per Electricity Act, and based
electricity
on parameters defined by SERC
a) Assessment based on sanctioned load /
connected load / MDI
b) Assessment based on error in meter
accuracy due to tampering
c) Penal tariff for theft / misuse.

B19. Linking The system should link the customer to the Vital
consumer to rate applicable to his category. The rate
appropriate applicable is calculated on the basis of fixed
tariff charges, consumed energy, capacity (power
consumption limit), taxes applicable, subsidy
or support from the government, etc.
System shall also have provision to account
for retrospective changes in tariff / discount
/ subsidy announced by Govt. with effect
from back date. In case of subsidized
customer the system should calculate
amount of subsidy payable against each bill
and if utility want the subsidy amount can be
printed on the bill for information of

Page 175 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

customer.
B20. Inclusion of The system should calculate other dues for Vital
past dues and the customer (e.g. late payment charge,
surcharge electricity duty surcharge, assessed amount,
etc) and add them to the regular bill amount.
If there are past dues, the system should
calculate both the past dues and the fines on
past dues as applicable. The system should
allow flexibility to define and modify the
logic for fine/ penalty calculation for
different types of arrears as per the
prevailing norms of the utility. If past dues
are there the generated bill should include
past dues.
In case of any post facto extension of due
date, system to have provisions to
automatically waive late payment surcharge.
B21. Management of The system should have provision of Managing Essential
Security Deposit Security Deposit (SD) like :
(SD): i.) Refund of SD by adjustment in final Bill
ii.) Interest payout on SD through auto-
debit in bills or lump sum payout
separately
iii.) Adjustment of SD in prepaid charges for
any consumer shifting from post-paid to
prepaid regime
iv.) Caution money deposits in case of New
Connections should be treated as a
Security Deposit.
B22. Billing with pre If there is any credit on account of Vital
payment credit prepayment, adjustment etc., the system
should be able to adjust the credit against
the amount payable for the month and
generate a zero or a negative bill.
B23. Estimate billing As and when the metering data is validated in Vital
the system, it should be capable to generate
bill under the normal billing cycle. In case
of meter data is not available the system
should generate an estimate bill based on the
past consumption pattern of the customer. It
shall also be possible to generate Estimate
Bill for theft/enforcement cases. The system
should also provide for change in the
estimation logic that may happen from time
to time. The system should incorporate the
estimate for consumption from the metering
module.

B24. Reasons for The system will have a list of all standard Vital

Page 176 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

estimate billing reasons for estimate billing. The list will be

compiled based upon the utility and SERC
guidelines, which may change from time to
time. The system should be capable of
generating bills for all instances of
exceptional readings. The scenarios under
which exceptional readings are taken are
temporary connections, voluntary
termination, forced termination etc. The
system will allow the bill amount to be
modified by the designate authorities through
their login ids only. All such changes along
with the corresponding login ids will be
tracked by the system.

B25. Electronic The system should be capable to dispatch the Vital

dispatch of bill/ generated bill electronically to customer/
availability of payment portals to which customer is
bills on internet registered if desired by customer. The bill in
portal of utility actual format must also be available on
utility’s internet portal for customers. System
must be able to inform customer regarding
new bill along with due date & amount via
SMS automatically. The system should allow
generation of reminder letters at predefined
intervals before the due date - over the web/
mobile phones/ paper formats.

B26. Discontinuing The system should have the provision of Desirabl

billing after stopping the generation of bills and taking e
dismantling the arrears as bad debts, after a Purchaser
specified period of time, say 6-12 months
after dismantlement.
B27. Billing for The system should have the provision of Vital
temporary preparation of Temporary Connection
connections. Energy Bill, with DISCOM defined Category
and Charges. Provision for -
 Final Bill Proportion
 Fixed amount calculation (In case of
first bill)
 Amount Shifted to next bill (if next
bill is prepared in same month)
 Debit/Credit Adjustment (Unit or
Amount)
The system should have provision for
automatic job creation for disconnection
and final billing of temporary connections
one day prior to the expiry of the duration
for which the temporary connection was
granted.
The system should also have option to
extend such temporary connections based

Page 177 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

on utility defined authorization.

B28. Creation of The system should provide the monthly Vital

monthly ledger of the assessment and realization.
ledger
B29. Ledger The system should have the provision for Essentia
adjustment Debit/Credit Adjustment in ledger. l

B30. Final The system should have the provision for Essentia
reconciliation Final Bill Reconciliation, in case of l
permanent disconnection and provision for
final amount adjustment.

B31. Monthly Module can close Ledger monthly and Vital

report generate assessment and realization report.
generation
B32. Last bill In case a customer requests for Vital
generation termination of connection, the system
should accept the terminating meter
reading (which will be out of cycle in
most cases) for generating the last bill.
B33. Provision for System should have the provision of not Vital
holding bill allowing to print any bill of a cycle unless
printing till cleared by bill quality check group.
checked System shall have post billing filters to
outsort abnormal bills based on logic, so
that such bills are not printed/sent to
consumer by any mode.
B34. Bill The system should have provision to Desirabl
distribution generate optimal bill distributor route plan e
route plan based on bill distribution jobs in a given
generation area in a given cycle.
B35. Enforcement System shall have provision to log leads of Desirabl
and Legal theft / misuse by : e
Module :
- Creating automatic leads based on
Logging of
leads consumption analysis and tamper
analysis
- Accepting lead through mail, website,
phone calls, call centre or any other
mode
- Capturing the details of the lead
contributor person, whether
employee/outsider
B36. Enforcement The system shall have provision of lead Desirabl
and Legal processing - workflow and life cycle e
Module : Lead tracking for :
processing - Assessment billing
- Public Hearing and bill revision
- Payment and Settlement
- Escalation & Legal proceedings

Page 178 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

- Recovery of installments
- Case closure

B37. Detect The system should be able to detect the Essentia

doubtful doubtful consumer by comparing l
consumer consumption data of similar consumers
category / consumption / amount / trend /
previous consumption etc
B38. Analyze System should be able to analyze consumer Essentia
consumer consumptions for a particular period and l
consumption present the same graphically.

B39. Generate System should be able to generate Essentia

Disconnection disconnection notice to the consumer, when l
Notice theft or any other malpractice is detected.

B40. Notice to System should generate the notice to Essentia

consumer consumer / non- consumer and also be l
mailed or SMS

B41. Penalty System should be able to track penalty Essentia

realization realization l

B42. Log court System should be able to log court cases Essentia
cases and proceedings l

B43. Spot Billing System -

B46.1 Downloading The Spot Billing system shall enable meter Vital
of data in reading activities by transferring relevant
spot billing consumer information data base from Billing
system system, like service numbers, address, area
code, meter number, phase, load, MF, old
meter reading, old status, category, arrears
if any etc.

B46.2 Uploading of At the end of data collection and billing Vital

data in spot operation in the field, the information
billing system recorded in the spot billing machine should
be uploaded into the Base Billing system for
updating master database in the system.
The information would contain the service
number, present meter reading, present
status of the meter, billed date and time,
units consumed, average units, billed
amount, due date, disconnection date,
collections mode, collection amount in case
the collection is done at the consumer

Page 179 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

primise itself, etc.

B46.3 Billing logic in The Spot Billing software to be resident in Vital

spot billing the HHE shall be based on the existing
system billing logic and algorithms of the utility.

B46.4 Tariff revision The HHE should be able to calculate the Vital
cases tariff rates accordingly with the previous
and present rates during the assessment
period, so as to issue the on date calculated
demand to consumers under tariff revision
period including number of days, slab rates
etc.

B46.5 Skipping of The HHE should prompt for entry of present Vital
meter reading meter reading. If meter reading is skipped,
entry average/units consumed for previous month
from the master shall be
calculated/retrieved and units for billing
shall be displayed.

B46.6 Entry of meter The HHE should prompt for entry of meter Essentia
status status and display of calculated units/Avg. l
Units (Avg. units is to be retrieved from the
master data) depending upon the meter
status.
B46.7 Billing with The HHE shall prompt for any other Essentia
charges / adjustments/charges depending on the l
adjustments category of the consumer. Net bill is to be
calculated after adjustment of above
charges and should be displayed and prompt
for printout shall be given.

B46.8 Error checking Extensive error checking shall be provided Vital

to assure data integrity during
communications between the HHE and the
PC.

B46.9 Validation of Field validation for meter reading shall be Vital

meter reading ensured if the readings are beyond a
data predefined range and software will have
provisions to enter remarks in such cases of
abnormality.
B46.10 Printing of Spot Billing system would print the summary Desirabl
summary report with HHC serial number, which e
report contains the consumer file downloaded to
the unit, total number of services, services
billed / unbilled, total amount, collection
etc.
B46.11 Password HHE shall have two levels of Password Essentia
protection Protection - Supervisory level for functions l
of upload, download, time setting and other
supervisory functions and Meter Reader

Page 180 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

level for starting and closing the meter

reading.
B46.12 Event logging All events should be recorded in the event Essentia
file in HHE. The event details should be l
downloadable for analysis.
B46.13 Menu driven The spot billing software shall be user Vital
modular friendly, menu driven, structured and
format modular format for flexibility (Easy changes
/ Up gradation etc.)
B46.14 Time stamping Data Logging in the spot billing machine Vital
of logged data shall be date and time stamped.
B46.15 Provision for There should be a provision for enhancing Essentia
enhancing the the functionality of the software by adding l
functionality additional features.
B46.16 Time setting The HHE shall have the facility to get its Essentia
of HHE time set from Billing system only with l
proper security and password
authentication.

Page 181 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

15.0 Module: Collections

Objective : The system should provide different payment and information channels to customers and own
staff to improve customer convenience for payments and enable collections for the energy billed, and a
shorter metering-bill billing-collections (MBC) trade cycle
System Boundary: From: Capturing payment details To: Generation of disconnection and dismantlement
lists
Specification: Collection
Require Functionality Description Criticality Respons Comm
ment ID e ents
C1 Decentralized System must be capable of handling centralized or Vital C/
payment decentralized payment processing. ER/F/
processing & And System must be capable of centralized CR/ NC
centralized reconciliation of the collection.
reconciliation
C2 Linking The system should capture all the customer and Vital
payment to payment details as specified by the Utility time to
logging id time. All payments should be associated with the
login-id of the personal receiving them and the
collection center codes at which they were
received. All collections should be made against
specific bills/ forms to enable reconciliation at a
later stage.
C3 Mandatory In all Instances of collections without bill/ form Essential
reason code the system should make it mandatory for the user
to specify a reason from the predefined reason
codes embedded in the system, and defined by
the Utility time to time.
C4 Code based All collections will be classified against standard Vital
Classification of codes of payments that would be specified by the
collection Utility from time to time.
C5 Receipt The system should generate a receipt whenever Vital
generation money is collected. Each receipt should have a
unique receipt number. The system will allow
payments to be collected under the payment
categories indicated by Utility.
C6 Adaptability to System shall be capable to receive payments made Vital
different mode by the consumer in either of the following modes:
of collection -
Cash/ Cheque/ Bank Draft/ Credit Cards/ Debit
Cards/ Internet Payment Gateway/spot collection
or Payment made by direct debit from bank
accounts on authorization by the consumer (ECS).
Any other mode as may be specified by Utility
from time to time. In certain cases (e.g. Advance
Payments) collections can be accepted without
the bill as well. System should have support of
accepting payment through a single cheque
against multiple bills and keep proper track
against respective bills.
Further, the system shall also allow the consumer

Page 182 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

to pay one single bill through multiple modes i.e.

through multiple cheques of different banks, by
cash & cheque etc.

The payments made by the consumers are to be

acknowledged and accounted for in the respective
databases. For payment made by the consumers at
Collection Counter through Cheque/ Bank Draft
computerized acknowledgement shall be issued to
the consumers. System must be able to generate
& send SMS automatically to customer for every
payment received.
C7 Handling of The system should have following functionalities : Essential
cheque a) Holding recovery proceedings based on cheque
payments submission, but recognition of payment on
cheque clearance only.
b) In case of cheque dishonour -
i) Reversal of any payment recognized by the
system
ii) Levy of handling charges
iii) Generation of Notice under Negotiable
Instruments Act
iv) Blocking of further payment by cheque till a
defined timeframe/logic with appropriate
message on bill for same.

C8 Daily The system should generate a daily total for the Vital
reconciliationreceipts issued for the day. This would enable the
of cash and daily reconciliation of the cash collected with the
bank amount entered in the system as 'payment
received'. The system should also capture all bank
remittance details. At the end of a period, the
system should reconcile them with the bank
statements.
C9 Acceptance of The system should have the flexibility to accept Essential
part/ advance full, partial or advance payments. The system
payment should also have the facility to centrally change
these settings from time to time (e.g. - not
accepting partial payments during the last few
months of a financial year).

C10 Interfacing with In certain cases (eg during special collection Vital
special drives drives, collection by spot billing agent etc)
collections are made in the field and receipts
issued there. The system will have the provision
for accepting the collections and receipt details
for such field collections.

C11 Generation of The system should allow generation of reminders Essential

reminders/ by SMS/ letters at specified dates - before the
disconnection payment due date, and notices for disconnection,

Page 183 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

notice dismantlement.

C12 System ability System shall be capable to cancel receipt at cash Essential
to keep track of counters due to wrong punching etc. The details
cancelled of cancelled receipt to be kept in the system and
receipt the same may be printed on the new receipt also.

System should also provide to reverse the payment

applied to a particular account in case errors are
detected at a later stage, e.g. payment getting
applied to a wrong customer.

C13 Finance & The system should have provision for - Essential
Accounting i) Automatic creation of books of accounts
based on :
- Balance Sheet and Profit & Loss Statement
as per GAAP and Indian Companies Act 1956
- Annual Revenue Requirement, based on
Electricity Act 2003 read in conjunction with
SERC regulations
ii) Meter to be treated as asset in ARR (may be
treated as consumable material in other books
of accounts)
iii) Different payment settlement logic for various
components of payment received from the
consumer:
- Energy Revenue
(a) Revenue as per tariff :
i. Subsidy/Discount outside normal tariff
structure
ii. Penal tariff in case of
theft / misuse
(b) Electricity Tax
- Non-energy revenue
(a) Charges for various services : Service Tax
(b) Late Payment Surcharge
(c ) Penalty payout to
consumer in case of
deficiency of service
(d) Interest payout to
consumer on:
i. Security Deposit
ii. Advance Payment
- FIFO/LIFO settlement logic specific to Utility's
requirements, on the following buckets :
(a) Arrears :
i. Prior to certain period,
inherited by Discom from

Page 184 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

SEB as legacy
ii. After the certain timeline,
as accumulated by Discom
(b) Current Demand

iv) Payment settlement logic should take care of

the following scenarios:
- Part payment
- Late payment
- Surplus payment
- Advance payment
- Bill amendment after payment of bill

Page 185 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

16.0 Module: Asset Management

Require Functionality Description Critic Response Comment
ment ID ality s
AM.1 Identification The system shall have the ability to identify a Vital C/ ER/F/
of business business entity/district to which the CR/ NC
entity equipment/assets belongs and also should be able
to reorganize divisions, office codes, etc. in the
case of organizational changes.
The system shall have the ability to track from
fixed assets to movable assets, line assets (cables,
conduits) to underground assets, which run across
business entities.
AM.2 Creation of The system should able to create and define Vital
multiple asset multiple asset grouping for each type of asset e.g.
grouping poles in a group of LT pole, 11 KV pole etc and
again PCC Pole, Rail pole etc. The user should
able to classify the asset as per the defined asset
groups.
AM.3 Electronic The system shall allow electronic certification of Vital
certification physical inventory for locations including, but not
of physical limited to:
inventory Circles
Division
Sub division
AM.4 Creation of The system shall have the ability to initiate the Vital
asset master creation of asset master records from the process
records of creating and processing store issue documents.
The system shall have the ability to identify
potential fixed assets through Store transaction
details.
AM.5 Recording of The system shall be able to record information Vital
purchase and such as the supplier, purchase dates, serial
all other number against each individual piece of
historical equipment.
information Equipment / Asset identification number,
about asset Description
Serial number - Manufacturer - Model number
Year of manufacturing
Maintenance history for the equipment
Cost centre
Bill of Materials
Status (e.g. installed, repaired, in store)
Supplier,
Warrant period
Location etc

Page 186 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

AM.6 Analytical The system shall be capable to record condition Vital

features assessment calculation (condition analysis) as well
as root cause analysis of failures (FMEA studies).
Along with the risk factor (probability of failure),
the consequence factor (criticality of the failure)
should also be captured for each asset.

The system shall also be able to analyze the stress

levels on the assets (accelerated ageing) from the
data of AMR/SCADA/ DMS.
AM.7 Tracking of The system shall have the ability to track Vital
insurance insurance values (e.g., replacement value).
values
AM.8 Capability to The system shall have the ability for the user to Essen
update/ make subsequent updates to grouped or tial
regroup component assets. (e.g., the user may acquire,
individual retire or transfer one component of a group of
asset record assets). The system shall provide the capability to
update the individual asset record and to re-group
into an existing group or component structure.

AM.9 Review and The system shall allow the incoming and (or) Vital
approval of outgoing Business Unit head to review and
assets approve assets assigned to his Business Unit
assigned to his whenever transfer of personnel takes place. The
unit on system shall support this function with reports of
transfer of assets under BUH’s control.
BUH
AM.10 Maintaining The system should be able to maintain the list of Essen
the list of spares along with their part no for each tial
spares with equipment. The system should also be able to
their part no. group equipments of same make and rating for
the purpose of assessment of spares requirement.

To avoid stock out situations and ensure minimum

inventory carrying costs, the system should be
able to prompt for replenishing of spares, optimal
re-order levels for major assets and also for re-
ordering of daily consumables.
AM.11 Capability to The system shall provide the capability to scan Essen
scan bar code their own bar code tags and automatically upload tial
tags and the physical inventory for review, reconciliation,
upload the and approval.
inventory
AM.12 Furnishing of The system shall allow utilities to provide a Vital
condition of 'condition of the asset' at the date of physical
the asset on inventory. Examples include:
the date of New
physical Good
inventory Poor
Broken
AM.13 Recording of a The system shall allow utilities to record a 'date Essen

Page 187 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

date of of physical inventory' when inventory counts of tial

physical physical assets take place.
inventory
AM.14 Provision for The system shall allow utilities to provide mass Essen
mass updates updates to a physical inventory date field. This tial
to a physical would be required for agencies that complete
inventory date their inventory at one time and wish to update all
field of their assets with one transaction.
AM.15 Capability to The system shall allow utilities to provide the Essen
identify capability to identify all assets that have been tial
missed or non missed and not updated by the physical inventory
updated process, or to identify all assets in the following
assets categories :
Missing or lost
Stolen
Destroyed
Under disposal review
AM.16 Capability to The system shall provide the capability to identify Essen
identify vehicles and other assets that have been tial
vehicles and purchased or leased via various methods.
other assets
AM.17 Provision of The system shall provide workflow to identify and Essen
workflow to route possible lease renewals to the appropriate tial
identify and user.
route lease
renewals
AM.18 Insurance The system shall allow asset tracking and Essen
claims related reporting related to insurance claims and tial
asset tracking insurance recoveries.
AM.19 Provision for The system shall provide an asset transfer Essen
asset transfer transaction for collaborative data entry. This shall tial
transaction include the capability to enter and save partially
completed asset transfers. This could include
allowing the transferring agency to complete their
portion of a transfer and to allow the document
to be saved. At a later date, the receiving agency
could access the transaction for completion and
posting of the final transfer.
AM.20 Generation of The system shall generate reports detailing the Vital
reports on cost of new assets acquired to replace an asset
cost of new lost, missing, stolen, or destroyed.
assets
AM.21 Provision to The system shall provide the ability to deactivate Vital
deactivate an an asset when removed for maintenance and
asset allow reactivation based on proper authorization.

AM.22 Allowing and The system shall allow and track adjustments to Essen
tracking of historical cost (e.g., An isolator which was tial
adjustments captured as part of the original cost of the
to historical substation is transferred, requiring the original
cost cost of the Sub station to reflect the adjusted
cost base).

Page 188 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

AM.23 Online The system shall have the ability to allow agency Essen
viewing and asset managers to view and search official fixed tial
search of asset policy and procedures online or via web
fixed asset browser.
policy and
procedures
AM.24 Creation of The system shall contain a population table for Vital
population the purpose of identifying ownership and
table for maintenance responsibility for equipments.
identifying
ownership and
maintenance
responsibility
AM.25 Provision for The system shall allow different depreciation Vital
different schedules and methods for different assets within
depreciation an asset group.
schedules and
methods
AM.26 Classification The system shall allow for major asset class (e.g., Vital
of assets personal property (including vehicles), buildings
(new, improvements, renovations), land, land
improvements, infrastructure, leasehold
improvements, and construction in progress)
dependent features for tracking and reporting
data elements.
The system shall also be able to identify and
classify the assets as per its criticality in
improving the system reliability indices (SAIDI,
SAIFI etc).
For reliability based asset management, the
system should also be able to perform reliability
analysis (N-1 criteria) or other applicable criteria.

AM.27 Tracking of an The system shall be capable of tracking an Essen

alternate alternate replacement date besides useful life tial
replacement expiration date.
date
AM.28 Ability to link The system shall have the ability to link asset Desir
asset master master records to other asset master records for able
records to grouping (Custodian) Assignment. The system
other asset shall have the ability to flexibly track assets
master (parent to child relationships), to effectively have
records asset structures record component and 'complex'
assets, essentially allowing a 'roll up' feature
(e.g., the individual asset values for routers will
roll up to the asset value for the network rack,
which is the asset master record).

AM.29 Creation and The system shall have the capability to create and Essen
maintenance maintain both central and agency dependent tial
of coding coding tables for all tracking fields (e.g., location,
table sub divisions, etc.).

Page 189 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

AM.30 Uniform The system shall have uniform naming Essen

naming conventions for coding employees, integrated tial
conventions with the HR employee number, name, or other
unique identifier when assigning an asset to an
employee or custodian.

AM.31 Provision of The system shall allow mass adjustment Essen

mass functionality (e.g., useful life for building changes tial
adjustment from 25 to 30 years) to update all assets in that
facility category.
AM.32 Provision to The system shall have the ability to track multiple Essen
track multiple location codes. These codes would provide tial
location codes Utilities with the ability to identify where the
assets are located, including but not limited to :
Sub station
Feeder
Buildings
AM.33 Provision of The system shall provide agencies with multiple Essen
multiple responsibility codes. These codes would provide tial
responsibility agencies with the ability to identify who is
codes. responsible for the asset, including but not
limited to :
Department assignment
Organization assignment
Group assignment
Individual assigned responsibility
Program responsible
District responsible
Supervisor responsible
AM.34 Identification The system shall allow for the identification of Essen
of maintenance or capital costs performed. tial
maintenance
or capital cost
AM.35 Generation of Shall have the ability to establish an asset record Essen
an asset status based on a 'level of completeness’ and tial
record status update that status and master record.
AM.36 Integration The system shall allow integration of web-based Vital
with web- GIS (geographic information system) information,
based GIS such as X, Y coordinates.
information
AM.37 Provision of The system shall provide flexible selection criteria Essen
flexible in asset management reporting (e.g., site tial
selection locations and vehicles).
criteria.
AM.38 Tracking and The system shall have the ability to track and Vital
reporting of report statistical information.
statistical
information
AM.39 Provision of The system shall have insurance reporting for risk Essen
insurance management. tial
reporting

Page 190 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

AM.40 Life cycle cost The system shall calculate replacement costs by Essen
analysis and tracking current or forecasted values. tial
calculation of The system shall also be capable of performing
replacement life cycle cost analysis to maintain a balance
costs of asset between system reliability and cost incurred over
the assets life cycle and to facilitate decision to
continue with maintenance of the asset or replace
the same.
AM.41 Generation of The system shall have the ability to produce Essen
capital asset capital asset activity reports by agency, asset tial
activity report class and fund source.

Page 191 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

17.0 Module: Maintenance Management

Objective : For better planning and co-ordination of various maintenance activities, reduce breakdowns by
inculcating the culture of preventive and predictive maintenance, to maintain maintenance history, to review
and control maintenance costs and providing a feedback to management for timely decision making.

Specification: Maintenance Management System

Require Functionality Description Criticalit Respon Comm

ment ID y se ents
MM.1.0 General Features and Scope of Work: -
MM.1.1 Co-ordination Ability to provide a means to co-ordinate various Vital C/
between maintenance work being planned (e.g. ER/F/
various corrective, preventive, breakdown and predictive CR/ NC
Maintenance maintenance related work).
works
MM.1.2 Printing of Ability to print shutdown notices for potentially Vital
shutdown affected customers and integrate with Customer
notices Care System, which can send SMS to such
customers automatically.

System shall also have ability to print excavation

permits for underground works for the purpose of
attending cable faults and related maintenance
activities.
MM.1.3 Review of Ability to review any outages/ overhaul / Desirable
planned shutdowns being planned, and the maintenance
maintenance work planned to be performed during that
works period.

MM.1.4 Support for Ability to support Predictive Maintenance, where Vital

predictive specific equipment data (e.g. noise level, meter
maintenance reading, abnormal temperature at line joints etc.)
can be recorded and monitored for automatic
creation of maintenance work order, in case
certain event occur (e.g. meter reading is at
danger level).

MM.1.5 Forecasting of Ability to support the forecasting of future Essential

future corrective work for next 12 months (user-
corrective definable period). An analysis of historical work
works will be used to forecast future corrective work.
Such an exercise would likely include an analysis
of the incidence of certain classes of failures,
analysis of causes of failure etc.

MM.1.6 Automatic Ability to automatically trigger the creation of Vital

creation of Work Orders for single equipment or group of
work orders equipments based on equipment condition
monitoring results, maintenance strategies and
associated criteria. These Work Orders should in

Page 192 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

turn be based on a Standard Job capable of storing

all job requirement information.
MM.1.7 Flagging of Ability to flag work units created for statutory or Essential
statutory works regulatory reasons.

MM.1.8 Automatic Ability to generate work orders automatically when Vital

generation of a particular asset's warranty is soon to expire. This
WO after would be used to trigger maintenance checks /
expiry of inspections prior to the warranty expiring.
warranty
MM.1.9 Forecasting of Forecast Maintenance Activities - Vital
planned Ability to forecast planned / preventive
maintenance maintenance for next 12 months (user-definable
jobs period) based on maintenance strategies /
triggers. The forecast should apply both time and
operational / conditional triggers to predict,
'when' maintenance activities will be required.
MM.1.10 Automatic Ability to schedule maintenance plan for Vital
creation of WO automatic creation of work order, based on :
as per - Time (calendar date or fixed time interval)
maintenance - Activity (counter based)
schedule - Time and activity based on which ever is
earlier basis.
MM.1.11 Time based Ability to maintain time based criteria for the Vital
creation of WO creation of work units. This refers to maintenance
strategies based on time (e.g. Perform statutory
inspection every twelve months).
MM.1.12 Usage based Ability to Maintain Usage Based Criteria for the Vital
creation of WO creation of work units. This refers to maintenance
strategies based on equipment usage (e.g. Perform
circuit breaker maintenance every 500 operations).
MM.1.13 User defined Ability to maintain user defined maintenance Vital
creation of WO criteria for the creation of work units. Any special
maintenance strategies defined by users.
MM.1.14 Automatic Ability to automatically generate a recommended Vital
generation of schedule / shift pattern based on work order due
schedule, dates, work order priorities / criticality, resource
priority etc. availability, Feeder / location / geography. Also,
ability to automatically schedule down to work
crew level triggered preventive maintenance
work orders and priority jobs.
MM.1.15 Identification Ability to identify opportunity maintenance. Vital
of opportunity Opportunities arise through:
maintenance - Review of outstanding work orders on
jobs specific items of equipment
- Examination of the work 'mode' that
identifies the outage requirements for the
work and consequently the down-stream
activities that can be performed.
- Review of condition monitoring data for the
equipment and 'related' equipment.
- Review of future preventive maintenance

Page 193 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

tasks.
- Review of location of work and identification
of work, which may be performed within a
geographical area.
MM.1.16 Creation of The short to medium term maintenance planning Vital
short/medium horizon is on a monthly basis and should be
term planning approximately at least 12 months long. Ability to
support the update of the plan on a regular basis.
MM.1.17 Resource Ability to review resources available compared Vital
planning and with resources required to undertake the work.
review Resources may be either individual skills or work
groups (e.g. teams / crews) or special tools &
tackle. Also, ability to identify resource shortfalls
in suggested schedule.
MM.1.18 Search inquiry Ability to inquire on Work Request and Work Order Vital
on Work through inbuilt system searches.
request and
WO
MM.1.19 Location of WO Ability to use a customer reference to locate a Vital
on customer Work Request or Work Order and ascertain
reference progress.

MM.1.20 Graphical Ability to graphically depict and manipulate Essential

depiction of online schedules in the form of GANTT charts by
online multiple variables including:
schedule - Period - Date (Between two dates)
- Time (Days/Hours/Weeks/Months/Years)
- Work Group/Branch - individual
- Work Order Type (preventive, corrective,
fault type)
- Work Order Relationship (Parent, Child, Peer
to Peer)
- Skill or Resource - Location - Tools -
Equipment/Plant
MM.1.21 Creation of Ability to take a 'snap-shot' of the schedule for Essential
snap shot of the purpose of forwarding the schedule to the
schedule appropriate person (supervisor) to review and
approve via workflow.

MM.1.22 Creation of Ability to schedule work for customer Essential

customer appointments (generally for new connections)
appointment allowing for several appointments per day by
schedule either an individual or crew. Such calls will
initially be recorded in the Utility’s Call Centre.
MM.1.23 Rescheduling It should also be possible to change the planned Vital
of planned execution date for the maintenance work while
works providing a means to co-ordinate all related
works at a particular location and time.
MM.1.24 Creation of Ability to bulk schedule and bulk approve. Essential
bulk schedule
MM.1.25 Creation of Ability to bulk reschedule and slip schedule (i.e. Essential
bulk schedule Remove work from the schedule and move to open
and slip periods), e.g. cater for storms and other high

Page 194 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

schedule priority events. This should be able to be

performed graphically by dragging and dropping
GANTT chart objects.
Scheduling should be allowed across districts,
and/or divisions, sub divisions, work groups,
types or grouping of assets.
MM.1.26 Creation of Inspection work will be sub-divided into Vital
Inspection manageable parcels using the asset relationships
work parcels held within the GIS system (either by polygon or
network). Work parcels will be prepared by
nominating the inspection activities to be applied
to the asset. Inspection tasks will be required to
be held as standard jobs in the maintenance
management system.
MM.1.27 Downloading Ability to download inspection work parcels into Vital
of inspection a format readable by work crew, who perform
work parcels the inspections.
MM.1.28 Generation of Ability to generate work parcels by nominating a Essential
work parcels network activity to be applied to the asset. The
based on subsequent work will be required to be held as
network standard jobs in the maintenance management
activity system.
MM.1.29 Forecasting and Ability to forecast labor requirements and support Vital
planning for labour planning in terms of both quantities and
labour skills based on work forecasts. Labour planning
requirements would include structure and size of work crews,
individual skills and involve analysis of worker leave
patterns.
MM.1.30 Forecasting and Ability to forecast contractor requirements and Vital
planning for support contractor planning based on work
contractor forecasts.
requirements
MM.1.31 Forecasting and Ability to forecast maintenance plant / tool Vital
planning for requirements and support maintenance plant / tool
T&P planning based on work forecasts.
requirements
MM.1.32 Forecasting and Ability to forecast materials requirements and Vital
planning for support materials planning based on work
material forecasts.
requirements
MM.1.33 Work plan as a Ability to hold the work plan as a series of work Essential
series of work parcels tied to specific time period - i.e. Months,
parcels Weeks etc.

MM.1.34 Updation of Ability to update the long-term plan for a business Essential
long term plans division or department.

MM.1.35 Tracing of Ability to trace movement and usage. History of Desirable

movement and the movement of traced components will be
usage performed largely automatically. The allowing
details will be maintained / available: - Acquisition
details (order no, date and price); - Issue details
(requisition no and date); - Installation details

Page 195 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

(equipment identifier, date installed and

removed); - Repair details (technical description,
costs, dates, operating statistic e.g. hours); -
Operational and condition statistics of installed
equipment (e.g. failure rates, outputs, vibration
results, oil samples etc)
MM.1.36 Integration Ability to integrate with the Materials, HR and Vital
with Materials, Finance management system in future.
HR and
Finance
MM.2.0 Work Requests
MM.2.1 Creation, Ability to create, maintain and review work Vital
review and requests and delete them if they are not
deletion of required.
work requests
MM.2.2 Creation of Ability to raise maintenance Work Requests after Vital
Work requests receiving notification from operations about a
breakdown. The Work Request should then be
capable of actioning / triggering electronic
notification to the maintenance supervisor.
MM.2.3 Capturing of all Ability to capture maintenance job requests from a Essential
job requests variety of groups and systems in addition to
Operations, Maintenance personnel of the utility,
which includes external customers via the Internet,
Fax, letter Telephone or Modem through the
utility’s interfacing Systems/Call centres.
MM.2.4 Search Ability to easily review / search for equipment Essential
capability for related Work Request and/or any other Work
all work Request problem e.g. graphical, Colloquial
requests searches for equipment IDs, drop down menus for
selectable fields and sizeable descriptive fields for
recording job/fault information.
MM.2.5 Classification Ability to classify Work Request/Work Order by Essential
of work user defined variables. For example safety,
requests modification, new work, rework, breakdown,
preventive etc.. It should be possible to report by
each of these classifications.
MM.2.6 Prioritization of Ability to assign a priority to a Work Request. Vital
work requests
MM.2.7 Ability to view Ability to view details of any outstanding Work Vital
any work Requests on a specific job or related piece of
request equipment in order to avoid duplicating work
requests. Also, ability to link / reference a Work
Request against a customer reference or location.

MM.2.8 Status of a Ability to record the status of a Work Request via Vital
work request user defined variables eg. Awaiting approval etc.

MM.2.9 Feedback to Ability to inform requestor via e-mail or otherwise Vital

requestor upon approval / rejection of Work Request.

MM.2.10 Automatic Ability to automatically and manually create / link Vital

Page 196 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

creation/ Work Orders to a Work request.

linking of WO
to a work
request
MM.2.11 Transfer of Ability to transfer (manually or automatically) Vital
information information captured within a Work Request
from work directly into a Work Order fields e.g. Job Type.
request to WO Once entered in the Work Order, it should be
possible to alter this information e.g. fault
description.

MM.2.12 Establishment Ability to establish Service Level targets against a Desirable

of Service level Work Request. These targets could be time,
targets financial and/or quality based. The ability to
report on these targets should also exist.

MM.2.13 Defining of Ability to clearly define work, in terms of attributes Desirable

work (nature, type, driver etc), by populating fields and
allowing user to enter a suitable long/short text
description.

MM.2.14 Defining of Ability to define critical dates against a Work Vital

critical dates Request. e.g. Required By date.

MM.2.15 Approval to Ability to approve, maintain, complete and close Vital

closure of Work Request online.
request online
MM.3.0 Work Orders
MM.3.1 Creation, Ability to create, maintain and delete Work Orders. Vital
review and
deletion of WO
MM.3.2 Creation of Ability to create a work order for all types of Vital
Work orders work by estimating the job duration, resource
requirements, material requirements, contractor
requirements and allocate a work priority and
mode to the request. The mode refers to the
requirement for and type of 'outage'. The work
order shall also identify the labor type and/or
crew (s) allocated to the work, description of the
work and the duration of the work. It is likely that
for Emergency work, the Work Order details could
be provided in via an electronic interface.
MM.3.3 Generation of The Work Order reference number should Essential
WO number accommodate existing numbering and naming
conventions used by the utility.
MM.3.4 Linkage of WO Ability to link a Work Order to a financial account Essential
with account code.
code
MM.3.5 Defining of Ability to define critical dates against a Work Essential
critical dates Order e.g. Required By date, planned start date,
for a WO planned end date, job duration etc.
MM.3.6 Format of a The Work Order details should include but not be Essential

Page 197 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

WO limited to:
 Work Order type (e.g. corrective, preventive,
breakdown etc.)
 Sub categories within a Work Order type
 Detailed description
 Work Order tasks
 Planned start/end date and duration for work
 Asset object requiring attention (e.g.
equipment, function, location)
 Work instructions/tasks
 Any safety procedures
 Material (spare parts, stock and non stock
items) required
 Estimation of manpower (internal and
external labor) requirement
 Labor skill level
 Work permit
 Planned cost
 Cost centre/project code etc.
MM.3.7 Linking of WO Ability to link/reference a Work Order against a Essential
piece or group of equipment, customer reference
or location.

MM.3.8 Creation of Ability to create multiple Work Order tasks against Essential
multi WO tasks a Work Order.

MM.3.9 Defining of Ability to define work requirements (plan/ labour/ Essential

work equipment/ other) against the Work Order.
requirements
MM.3.10 Review of WO Ability to assign and review Work Order priorities. Essential
priorities
MM.3.11 Postponement Ability to postpone Work Orders to a certain date or Vital
of WO to a specific shutdown period.

MM.3.12 Ability to Ability to make changes to a Work Order (e.g. Essential

change a WO change maintenance steps, change material
requirements, change labour requirements).

MM.3.13 Ability to view Ability to view details of any outstanding Work Essential
details of a WO Orders on specific or related pieces of equipment.

MM.3.14 Recording the Ability to record the status of a Work Order via user Essential
status of a WO defined variables e.g. on stand-by awaiting
materials, partially closed, closed etc.

MM.3.15 Generation of Ability to generate Work Orders based on Essential

WO based on maintenance triggers. Work Orders for Preventative
maintenance Maintenance tasks may be generated in the
triggers following ways :
 Automatically
 Automatically requiring approval /
authorization
 Manually

Page 198 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

MM.3.16 Automatic Ability to automatically identify and waive a Work Essential

waival of a WO Order, if a previous activity has already taken
place that satisfied the work requirement.
MM.3.17 Online The ability to approve work orders on-line via Essential
approval of workflow is required. This could be performed by
WO different incumbents within the organization,
depending on work order size/cost, priority,
mode and Delegated Financial Authority levels
etc. If a work order is not approved within a
specified time it should be forwarded to the next
appropriate person.
MM.3.18 Closure of WO Ability to maintain, complete and close Work Essential
online Orders online.
MM.3.19 Adjustment in Ability to adjust all elements of the Work Order Essential
WO including :
 Materials
 Resources
 Tools
 Timings
MM.3.20 Creation of an Ability to create and issue an emergency Work Vital
emergency WO Order that does not require approval. An audit trail
will record the user who authorized the Work
Order.
MM.3.21 Review of Ability to review maintenance history for a specific Desirable
maintenance item of equipment and/or on a particular
history manufacturer based on Work Order history.
MM.3.22 Attachment of Ability to attach documents to a Work Order Desirable
documents to a including detailed work instructions, safety
WO requirements and checklists, drawings etc. Upon
issue of a Work Order, it should be optional as to
whether attachments are printed automatically or
at the discretion of the user.
MM.3.23 Review and Ability to review and print any technical Desirable
printing of tech information associated with the work parcel.
information
MM.3.24 Status on Ability to check whether there are any current Desirable
warranty warranties on the equipment, or 'related'
equipment. This will require a link to the
equipment database where all warranty
information will be kept.
MM.3.25 Bulk creation Ability to create Work Orders in bulk using a pre- Essential
of WO selected set of fields.
MM.3.26 Bulk updation Ability to bulk update information for a number of Essential
of WO Work Orders.
MM.3.27 Search criteria Ability to specifically target a group of Work Orders Desirable
on group of WO during a search - based on Work Order fields
populated by the user.
MM.3.28 Viewing of bulk Ability to view bulk Work Order information and Essential
WO information manipulate this information based on user
requirements. These modifications should include
filed/code updates and/or generic description/
information input into the Work Orders description

Page 199 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

/ extended description.
MM.3.29 Issue of Ability to notify relevant personnel or issue a Essential
warning / warning/alarm, if a Work Order has not been
alarm in case completed after certain period of time.
of non
completion
MM.3.30 Generation of Ability to generate a requisition of permit in Vital
work permit order to isolate equipments for maintenance.
requisition
MM.3.31 Status of Ability to identify all permits issued/outstanding Vital
permits in relation to a particular piece of equipment or
groups of equipment.

MM.3.32 Automatic Once work has been scheduled requisitions are Essential
creation of automatically raised for materials and
resource contractors. These requisitions should not require
requisition additional approval i.e. Once the work order is
approved all related business objects that require
approval should be approved.

MM.3.33 Automatic Ability to dispatch work to crews automatically Vital

dispatch of (Manually function should be able to overwrite the
work to crews automatic function.) based on user defined criteria.

MM.3.34 Integration Ability to integrate with Mobile messaging and/or Vital

with mobile Internet systems for electronic dispatch of work to
messaging and work groups or crews via Utility’s Customer care
CC system system.

MM.3.35 Modification in Ability to create, review and modify the structure Desirable
work crew / and make-up of the work teams / crews including
teams skills and competency requirements.
MM.4.0 Standard Jobs
MM.4.1 Creation of Ability to create, retain and use standard jobs Essential
standard jobs including specification of tasks, materials
requirements, labour, hours and skills and
contractor hours and skills, in-house and
outsourced tools / plant requirements, outage
requirements, priorities, accounting information
etc.
MM.4.2 Creation of Ability to create standard maintenance jobs for Essential
standard jobs activities involving specific equipment, specific
for specific 'classes' or 'groups' of equipment or some 'general'
equipments jobs.
MM.4.3 Creation of Ability to use standard jobs to create Work Orders Essential
standard jobs resulting from condition results.
for specific
conditions
MM.4.4 Creation of Ability to use standard jobs to create Work Orders Essential
standard jobs for work originated from Maintenance Scheduled
for scheduled Tasks.
tasks

Page 200 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

MM.4.5 Classification Ability to classify standard job. Due to the Essential

of standard anticipated number of standard jobs, an easy-to-
jobs use classification system for standard jobs/Work
Orders is required. For example this system may be
dependent on the equipment hierarchy, equipment
class, location etc.
MM.4.6 Isolation Ability to link a standard job to any isolation Essential
requirement procedures required (e.g. need to shutdown certain
for a standard part of a plant).
job
MM.4.7 Linkage of Ability to link to a standard job(s) any required Essential
documents to a documents including technical information, safety
standard job instructions, method sheets, checklists etc.
MM.4.8 Tasks during a Ability to specify the type of tasks that will be Essential
standard job performed during a standard job.
MM.4.9 Linkage of Ability to link to a standard job any required safety Essential
safety instructions. Linkage is also required to be
documents to a maintained to Safety procedures within externally
standard job maintained documentation.
MM.4.10 Linkage of Ability to link a standard job to any inspection Essential
inspection checklists.
checklists to a
standard job
MM.5.0 Backlogs
MM.5.1 Viewing of Ability to view all work, review the backlog, and Essential
backlogs availability of resources to see which of the jobs
can be absorbed into the current or next
schedulable period(s). All work, including backlog,
should be able to be reviewed by user-defined
codes e.g. Fault type.
MM.5.2 Graphical Ability to graphically indicate all backlog work. Desirable
representation
of backlogs
MM.5.3 Actioning on Ability to bulk re-schedule, cancel, close or Desirable
backlog work postpone backlog work.
MM.6.0 Work Flow Functionality

MM.6.1 Workflow Ability to perform work flow and job tracking Essential
tracking functionalities.
function
MM.6.2 Structuring of The Work flow functionality should be able to be Essential
workflow as structured according to utility’s business processes.
per utility BP
MM.6.3 Graphical Ability to provide a graphical representation of a Desirable
representation process in terms of :
of a process - Roles
- Tasks
- Tools
- Processes
MM.6.4 Definition of The work flow functionality should be able to Essential
process rules define process rules with help options from drop
with help down lists.

Page 201 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

options
MM.6.5 Creation of Based on certain process options and actions, the Desirable
work units & work flow function should be able to create work
linking with units and link them to appropriate equipment
equipment information.
MM.6.6 Creation of Ability to utilize standard jobs and job estimates in Essential
work flow the creation of Work Flow related jobs/work
related jobs parcels.

MM.6.7 Automatic alert The work flow should be able to automatically alert Desirable
options in a or notify on :
work flow - Tasks completion
- Approval
- Exceed Service Levels
MM.6.8 Prioritization Ability to priorities work - automatically and Desirable
manually.

MM.6.9 Conductance of Ability to conduct statistical analysis such as: Vital

statistical average time to complete, average workload (by
analysis individual and work groups) etc.

MM.6.10 Providing Ability to support work steps and control elements Desirable
support in work such as:
steps and - Sending & editing messages
control - Scheduling
elements - Creating text documents & notes
- Setting & monitoring deadlines
- Escalation of overdue activities etc.
MM.6.11 Interface with Ability to interface with fax-on-demand systems. Desirable
fax-on-demand
MM.6.12 Ability to Ability to support electronic signature for document Vital
support approval
electronic
signature
MM.7.0 Work Sign Off
MM.7.1 Mandatory Ability to record the maintenance history data Vital
recording of against a component/equipment that has had a
maintenance work order raised against it. It should be possible
history data to make this field mandatory i.e. A job cannot be
closed unless this field has been entered.

MM.7.2 Capturing of all Ability to capture all information relating to Essential

information for completed maintenance work against a work order
a completed as part of the maintenance history database.
work Retain the information as part of the maintenance
history unless it is physically removed from the
system (e.g. through archiving exercise).
MM.7.3 Recording the Ability to record the return of materials that were Desirable
return of issued against the work order, but they were then
unused not used.
materials
MM.7.4 Recording the Ability to record the fact that the work has been Essential

Page 202 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

delayed delayed due to the materials not being available in

completion on time. This will be used to evaluate the material
a/c of planning procedures.
materials
MM.7.5 Recording the Ability to record the fact that the work has been Essential
delayed delayed due to insufficient labor resources. This
completion on will be used to evaluate the scheduling
a/c of labour procedures.

MM.7.6 Recording the Ability to record the fact that the work has been Essential
delayed delayed due to Lack of permit issue or any other
completion on user definable fields.
a/c of permit
to work
MM.7.7 Bulk closure of Ability to bulk close Work Orders meeting a user Essential
WO defined time, cost, resource, status or other
criteria.
MM.7.8 Automatic Ability to close Work Orders automatically once the Essential
closure of WO last Work Order Task has been completed.
MM.7.9 Authorization Ability to allow authorized employees to enter text Essential
to enter in a free format against the Work Order. These
comments comments should be able to be forwarded to
against WO maintainer's supervisor.
MM.7.10 Flagging WO Ability to flag/warning work orders where the work Essential
for cost order cost exceeds the work estimate / budget for
escalation the month/year or user defined approval limit.

MM.7.11 Automatic Ability to automatically flag outstanding Essential

flagging of orders/costs when attempting to close a Work
outstanding Order.
orders
MM.7.12 Attachment of Ability to attach user defined codes to work orders Essential
user defined upon closure e.g. fault type.
codes
MM.7.13 Complete Ability to completely close off work order. System Essential
closure of WO should inform user that all outstanding
commitments and invoices have been met. After
this step, no more costs can be charged to the
order.

MM.7.14 Archiving of Ability to archive Work Orders after a defined Desirable

WO period of time. It should be possible to easily
retrieve archived Work Orders within few hours.

MM.7.15 Resetting of Any associated time based or usage-based triggers Desirable

any time based should be reset, if the related work has been
or usage based completed. "Completion" should be user defined
triggers e.g. Partially closed Work Order. The system will
then begin to schedule the next predictive or
preventative maintenance Work Order.
MM.8.0 Maintain Bill of Materials
MM.8.1 Maintaining Ability to maintain the parts list contained in the Essential

Page 203 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

parts list equipment. The list should also include the

quantities of parts involved. Ideally a graphical
parts book Referenced to the catalogue would
support this.
MM.8.2 Maintaining Ability to maintain history of changes to Part List. Essential
history of From time to time equipment is reconfigured with
changes in alternative parts. History of such changes is
parts list required to be kept.
MM.8.3 Maintaining Ability to maintain reference to catalogue. For Essential
reference to each part in the equipment parts list, there is a
catalogue requirement to include a cross-reference to the
catalogue, to enable material identification and
reservations.
MM.8.4 Maintaining Ability to maintain the document identification and Essential
document document contents in the document register.
identification Ability to maintain any links between documents
and contents and any Equipment/ Component items.
MM.8.5 Maintaining Ability to maintain the drawing identification and Essential
drawing drawing contents in the drawing register. Ability to
identification maintain any links between drawings and any
and contents Equipment/ Component items. It also desirable to
have the ability to mark up/red line drawings on
the users screen and email the changes to an
officer responsible for updating the document.
MM.8.6 Creation of When an equipment item / component is created, Essential
asset it is required to reference the item / component to
an asset in the fixed assets register. Where a
relevant asset hasn't been set up, it is expected
that the system would require the creation of an
appropriate asset.
MM.9.0 Maintain Vendor Supplied Information
MM.9.1 Recording of Ability to record the vendor recommended skills Essential
vendor required to maintain the equipment/ component.
recommendatio
n skill
requirement
MM.9.2 Recording of Ability to record against the equipment/component Essential
vendor vendor recommendations for how it will perform.
recommendatio
n performance
MM.9.3 Recording of Ability to record against the Essential
vendor equipment/component vendor recommendations
recommendatio for the conditions under which it should be
n operating operated.
conditions
MM.9.4 Maintaining Ability to hold history of changes to recommended Essential
history of performance / operational specifications.
changes to
above recom-
mendations
MM.9.5 Maintaining the Ability to record the warranty duration, the Essential
warranty warranty period end date, the warranty number
details and any warranty notes. If a WO is raised on an

Page 204 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

asset under warranty, the system should flag that

the vendor is responsible for repairs and that
maintenance is required to be performed in
accordance with warranty supply and contract
conditions.
MM.9.6 Recording of Ability to record the maintenance frequency, type Essential
vendor and procedure recommended by the vendor.
recommendatio
n maint. freq,
type,
procedure etc.
MM.9.7 Maintaining Ability to hold history of changes to the Desirable
history of recommended maintenance frequency, type and
changes to procedure.
above recom-
mendations
MM.9.8 Recording of Ability to record any environmental issues or Desirable
environmental regulations required in the operation of the
issues equipment / asset.
MM.9.9 Maintaining the For the purpose of repair / replacement decisions, Essential
useful life it is required that the individual items useful life be
details maintained.
MM.10.0 Analyze and Report
MM.10.1 Reporting of Ability to report the total costs and quantities for a Essential
total cost and particular job. Ability to drill down into the Work
quantity Order for a more detailed breakdown including an
analysis of internal and external labour, materials
and other costs.
MM.10.2 Performance of Ability to analyze the performance of standard Essential
standard job jobs against the estimates contained within it. The
against job costs and quantities should be able to be
estimate broken down by work crew.
MM.10.3 Analysis of Ability to list the amount of time taken to Essential
time taken to complete a Work Order for making comparison
complete against the planned / estimated duration. This
against time analysis should be able to be classified by
estimated work type or Work Order classification and be
duration broken down by work crew.
MM.10.4 Listing of total Ability to list the total costs incurred due to issue Essential
cost due to of material to Work Orders. The material could
issue of either be store issue or direct purchase issue. This
materials report could be against a specific equipment or
against a cost centre.
MM.10.5 Listing of total Ability to list the total costs incurred due to Essential
cost due to contractor work charged to Work Orders. This
contractor cost would include any contractor overheads. This
report could be against an item of equipment, a
cost center, a contractor, an equipment ID etc.
MM.10.6 Graphical Ability to measure and report on resource and Desirable
display of utilization factors. This should include graphical
resource and displays and/or tabulated data.
utilization
factor

Page 205 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

MM.10.7 Ability to One component of the planning performance is to Vital

review backlog keep the backlog of jobs to a minimum, therefore
WO the ability to review backlog Work Orders is
crucial.
MM.10.8 Listing of Ability to list the outstanding Work Orders that Essential
outstanding & have not been completed by their estimated due
incomplete WO date.

MM.10.9 Reporting on Ability to report on all Preventive maintenance Essential

status of work that has been missed rescheduled or
Preventive postponed.
works
MM.10.10 Listing of WO Ability to list all Work Orders completed by a work Essential
completed group during the shutdown period. It should be
during a shut able to compare this summary with the total
down period number of Work Orders scheduled for completion
during this period.
MM.10.11 Listing of Ability to report on Work Orders that have been Essential
delayed WO delayed due to:
- Materials not being available in time for the
maintenance work;
- Insufficient internal / external labour
resources;
- Lack of permit being issued;
- Other user defined fields.
MM.10.12 Comparison Ability to compare the amount of planned work Essential
between (Preventative) to the amount of unplanned work
planned and (breakdown or corrective) over a set time period.
unplanned
works
MM.10.13 Comparison of Ability to compare the costs of preventative work Essential
cost between to corrective and modification work incurred over
preventive and a set time period.
other work
MM.10.14 Analysis of Ability to support the analysis of historical work to Essential
historical work assist in the estimation of future work and
resource requirements.
MM.10.15 Ability to Ability to record status of a Work Order such as Essential
record status approved, not-approved, wait on materials, wait
of a WO on contractors, wait on labour, held etc.

MM.10.16 Capturing of Ability to capture work progress including : Essential

Work progress - Internal labour hours performed on each task
of a WO and resultant charges
- Hourly hire contractor hours performed on
each task and resultant charges
- Material charges based on issue
- Contractor charges from invoice entry
- Plant charges
- Completion of tasks and closure of Work
Orders
- Manually derived % complete for each task or
Work Order

Page 206 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

MM.10.17 Reporting on Ability to report on an asset's maintenance history Essential

asset based on Work Orders raised against it.
maintenance
history
MM.11.0 Analyze and Report asset performance

MM.11.1 Viewing of Ability to display the maintenance costs for a range Essential
maintenance of equipment/ components. This will enable the
cost user to review all costs incurred during the life of
an asset including labor, materials, contractors
costs etc.
MM.11.2 Reporting of Ability to report common equipment failures and Essential
common repair times based on fault codes.
failures &
repair times
MM.11.3 Review of any Ability to review any notes about the particular Essential
notes on equipment/ component, which have been entered
equipment by maintenance experts. The notes should be
accessed from the particular equipment/
component record.
MM.11.4 Analysis and Ability to analyze and report the mean time Essential
report on MTBF between failure (MTBF) or an item of equipment. It
should be able to be summarized for any
particular equipment or a group of equipment. In
addition, the 'time between failure' should be able
to be replaced by usage statistics between failure.
MM.11.5 Analysis and Ability to analyze and report the mean time to Essential
report on MTTR repair (MTTR) for an item of equipment. This
involves calculating the average of the work order
duration's for an item of equipment. Alternatively,
it could be an average of the recorded downtimes.
MM.11.6 Reporting on Ability to report how many times an item of Essential
frequency of equipment has failed within nominated time
failure. periods (Frequency of Failure).
MM.11.7 Assessment of Ability to determine from the historical data the Essential
failure probability of failure over a set time period.
probability.
MM.11.8 Assessment on Ability to display what affects the failure of an Essential
affect of equipment/ component. This will then help to
failure determine how critical it is that this equipment/
component does not fail.
MM.11.9 Statistics on Ability to produce statistics linking the cause of Essential
cause of failure failure and the effects of the failure.
and its effects

MM.11.10 Graphical Ability to map (graphically) how the rate of failure Desirable
mapping of changes with different work load, by
rate of failure equipment/group of equipment. It would be used
to assist in determining the optimal workload.
MM.11.11 Graphical Ability to report equipment / group of equipment Desirable
analysis of downtimes over a particular period of time
fault including analysis of fault (Graphically).

Page 207 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

MM.11.12 Review of age, Ability to assist in the reviewing Essential

maintenance equipment/component age, maintenance history,
history & and recommended working life to determine if it
working life of will be able to meet the requirements of the
equipment operations/ maintenance departments.
MM.11.13 Assisting in Ability to assist in the decision to retain an item in Essential
making its current state, replace the item, or modify it
replacement based on future usage, estimated maintenance
decision costs, average downtime etc.
MM.11.14 Review of Ability to review maintenance work performed on Vital
maintenance equipment and highlight regularly occurring
work and defects in specific types/designs of equipment.
highlighting The report should be able to be run based on user
any defects of defined parameters such as equipment ID, make /
recurring model, defect code etc.
nature
MM.11.15 Simulation of Ability to simulate the life cycle maintenance costs Vital
life cycle for an item of equipment, when different
maintenance operational conditions and maintenance strategies
costs are entered as parameters.
MM.12.0 Reporting and On-line Inquiry
MM.12.1 Defining Able to define criteria for extraction of data. Essential
criteria for
data extraction
MM.12.2 Defining Able to define security rules for data extraction. Essential
security rules
for data
extraction
MM.12.3 Comparison of Able to compare historical data to actual data Essential
historical and based on user defined period (e.g. monthly,
actual data quarterly, yearly).

MM.12.4 Comparison of Able to compare actual data to Target / budget Essential

target and data based on user defined period (e.g. monthly,
actual data quarterly, yearly).

MM.12.5 Defining Able to define formula for formatting data i.e. Essential
formula for metric conversion, quantity count, percentage
data formatting calculation and arithmetic calculation.

MM.12.6 Tracing of Able to provide drill down functionality to trace Essential

summarized summarized information to source
information data/transaction.

MM.12.7 Performing of Able to perform "what if" or scenario analysis on Essential

scenario report data.
analysis

MM.12.8 Selection of Able to select the level of details and volume of Essential
level and data for reporting
volume of data
MM.12.9 Defining Able to define criteria for filtering data subject to Essential

Page 208 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

criteria for security rules.

filtering data
MM.12.10 Generation of Able to generate reports : Essential
reports-1 - One at a time,
- Multiple reports at a time
- Ad hoc and regular reports together

MM.12.11 Generation of Able to generate reports at : Essential

reports-2 - Real time / on line basis.
- In background (when evaluation is time-
consuming).
- Via overnight batch
- Specific date
- Regular time interval

MM.12.12 Creation of Allow creation of user-defined reports without the Essential

user defined need for technical skills.
reports
MM.12.13 Defining report Able to provide flexible reporting tools for defining Essential
layout and report layout and type of graphical representation.
graphical
representation
MM.12.14 defining Able to define personalized report menu. Essential
personalized
report menu.

MM.12.15 Restriction in Able to restrict report selection based on security Essential

report of database, organization structure, group.
selection
MM.12.16 Provision of Provide flexible Report Writer with the following Essential
flexible report minimum features :
writer  Specify the format and layout of reports;
 Summaries and total the information to be
reported;
 Select records to be included in the report;
 Select details from each record to be
included;
 Sort the information to be reported as one
level within another;
 Perform arithmetic calculation on the
information selected or totals thereof;
 Ability to add narrative comments to reports
 Store the report format for later use; and
 Produce reports in graphical form for
presentation purposes.

MM.12.17 Downloading of Able to allow downloading of reports to standard Vital

reports PC applications (e.g. MS Excel spreadsheet, MS
Project, MS Word, MSWorks etc)

MM.12.18 Outputting of Able to output reports in various media: - screen - Vital

reports printer - electronic media

Page 209 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

MM.12.19 Prioritization of Able to prioritize reports for processing. Essential

reports
MM.12.20 Defining Able to define distribution list for each report. Essential
distribution list
MM.12.21 Electronic Able to distribute reports electronically to other Essential
distribution of users :
reports - Automatically upon completion
- At preset time

MM.13.0 Cost Control

MM.13.1 Costing of Ability to cost internal maintenance work hours to Essential
internal the work parcel. The value should be a multiple of
maintenance the hours and a predefined standard charge rate.
work hours
MM.13.2 Costing of Ability to cost contractor hours to the work parcel. Essential
contractor The charge rate should be contained in an
work hours established agreement with the contractor. It shall
also have ability to record other contractor
charges, such as overheads, costs of using
contractor owned equipment, or costs of using
contractor materials etc.

MM.13.3 Reconciliation Upon receipt of contractors invoice it should be Essential

of Work hours possible to reconcile hours against those appearing
on the W/O.

MM.13.4 Recording of all Ability to record all costs towards materials/spares Essential
costs towards etc. against a work Order
materials/
spares
MM.13.5 Costing of T&P Ability to cost equipment, plant and tools to Work Essential
based on work Orders based on hourly rates.
hours
MM.13.6 Recording of Ability to allow the recording of actual worked Essential
actual work hours on an on-line timesheet. It should be
hours on an on- possible to enter the timesheet data by individual
line time sheet employee, work group, work crew or by Work
Order.

MM.13.7 Interfacing Ability to interface with financial system via the Vital
with Financial referencing/linking of the Work Order to an
system account code. There should be an option to link all
transactions booked to the Work Order to a
transaction file for examinations of costs and dates
of incurrence.

MM.13.8 Validation of Ability to validate entered timesheet data Essential

timesheet data including :
 Employees (validate against crews and
individuals scheduled to the work);
 Work Order no (validate against Work Order
no and status e.g. closed for actual)

Page 210 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

MM.13.9 Forwarding of Ability to forward, through Work Flow, the input Essential
input timesheet to the appropriate approving officer for
timesheet via certification.
workflow
MM.13.10 Ability to Ability to allow for manual keying in of Work Order Essential
manually key in expenses.
WO expenses
MM.13.11 Allocation of Ability to allocate (manually and/or automatic; Essential
cost to individually and/or in bulk) cost to different Work
different WO Orders and asset types (e.g. contractor fees).

MM.13.12 Costing of Ability to drill down from Work Order or job to Desirable
individual individual cost transactions.
transaction in a
Work order
MM.13.13 Comparison of Ability to show Work Order actual costs versus Desirable
WO actual cost budget and forecast.
vs budget cost
MM.13.14 Generation of Ability to generate an alarm when Work Order Vital
alarm on cost expenses reach a user defined limit.
escalation
MM.13.15 Online viewing Ability to view (on-line) cost information for the Essential
of cost purpose of checking and monitoring progress.

MM.13.16 Checks on cost Capable of performing checks to ensure that cost Essential
transfer can only be transferred based on approved criteria
(e.g. that the job to which the cost is to be
transferred to is a valid job).

MM.13.17 Prevention of Ability to prevent cost transfers against closed Essential

cost transfer jobs.
against closed
jobs
MM.13.18 Security Checks Ability to establish security measures to control the Essential
on cost transfer transfer of costs.

MM.14.0 Data Capturing and Extraction

MM.14.1 Capturing of Able to capture statistical data from Essential
statistical data  Manual entry
 External electronic media
 Interfacing with external databases

MM.14.2 Integration with Other Systems

MM.14.2.1 Integration Integrated to GIS System to identify the nearest Vital
with GIS substation and to perform load analysis.

MM.14.2.2 Integration Integrated to Customer Care System to use CCS Vital

with Customer functionalities and information
care system
MM.14.2.3 Integration Integrated to DMS-SCADA System to use SCADA Vital
with DMS- functionalities, if available.
SCADA system

Page 211 of 212

 TAMIL NADU ELECTRICITY BOARD
SRS DOCUMENT (SECTION G2) FOR APPOINTMENT OF IT IMPLEMENTATION AGENCY

MM.14.2.4 Integration Integrated to Asset Database to use Asset Database Vital

with Asset functionalities and information.
database
MM.14.2.5 Database The system should support multiple databases. Essential
Support

Page 212 of 212