OPGC ERP Implementation

Confidential Page 1
ORISSA POWER GENERATION CORPORATION LIMITED

IB THERMAL POWER STATION
AT/PO : BANHARPALLI
DIST: JHARSUGUDA 768 234 (ORISSA)
TELE: 06645-222224
FAX: 06645-222249

Bid Document for

Implementation of SAP ERP, Non-SAP Applications and related IT Infrastructure
along with Post-Implementation support with Facility Management at OPGC.

Bid Document Number: ITPS/CC-22/2008/68
Date of Issue: 03.09.2008

Confidential Page 2

TABLE OF CONTENTS

Bid Data Sheet ...................................................................................................................................................... 4
Disclaimer .............................................................................................................................................................. 5
Section 1: Project Introduction ........................................................................................................ 6
1.1 About OPGC ................................................................................................................................................. 7
1.2 Future Business Plan ................................................................................................................................... 8
1.3 ERP Project Background Note .................................................................................................................. 8
Section 2: Scope Of Work ................................................................................................................. 9
2.1 Supply of Hardware and Non-SAP Software .............................................................................................. 10
2.2 Design, installation & commissioning of Infrastructure ............................................................................... 10
2.3 Implementation of the SAP applications ..................................................................................................... 10
2.4 Implementation of Non-SAP applications ................................................................................................... 10
2.5 Project Management in different phases, Change Management and Training. ......................................... 11
2.6 Post Implementation support services for running the SAP Application, Non-SAP applications and
Infrastructure Facility Management services....................................................................................................... 11
Section 3: Bidding Procedure ........................................................................................................ 12
3.1 Formal Invitation to Bid ............................................................................................................................... 13
3.2 Bidding Procedure ...................................................................................................................................... 15
3.3 Structure of Bid Document ......................................................................................................................... 19
3.4 Submission Of Bid ...................................................................................................................................... 19
3.5 Instruction to Bidder .................................................................................................................................... 21
Section 4: Evaluation of Bids ......................................................................................................... 26
4.1 Opening Of Bids ......................................................................................................................................... 27
4.2 Evaluation & Comparison of Bids ............................................................................................................... 27
4.3 Signing Of Agreement ................................................................................................................................ 28

Appendix-A: Bidding Reference .......................................................................................................... 30
Appendix-A1: Current IT Infrastructure details .................................................................................. 31
Appendix-A2: Business Processes Requirement-Overview ............................................................ 35

Appendix-B: Bid Support Documents ................................................................................................ 48
Appendix-B1: Letter of Undertaking by the Bidder ........................................................................... 49
Appendix-B2: Form for Price Bid ........................................................................................................ 51
Appendix-B4: Proforma for Bank Guarantee for Bid Security (Earnest Money Deposit) .............. 57
Appendix-B5: Consortium MOU .......................................................................................................... 59
Appendix-B6: Profile of Implementation Partner ............................................................................... 61
Appendix-B7: Profile of Hardware Partner ......................................................................................... 67

Appendix-C: Contract Document ........................................................................................................ 68
1 Definitions & Interpretations ................................................................................................................... 70
2 Scope of Agreement............................................................................................................................... 72
3 Obligation of Vendor ............................................................................................................................... 72
4 Obligation of Owner ................................................................................................................................ 76
5 Implementation Plan ............................................................................................................................... 78
6 Scope Change ........................................................................................................................................ 80

Confidential Page 3

7 Product Upgrades .................................................................................................................................. 80
8 Assignment and Subcontracting ............................................................................................................ 80
9 Tests ....................................................................................................................................................... 80
10 Performance Guarantee / Warranty ....................................................................................................... 84
11 Waiver .................................................................................................................................................... 86
12 Price and Payment ................................................................................................................................. 86
13 Liquidated Damages .............................................................................................................................. 90
14 Insurance ................................................................................................................................................ 91
15 Indemnity ................................................................................................................................................ 92
16 Patent Infringement ................................................................................................................................ 92
17 Settlement of Disputes ........................................................................................................................... 92
18 Term and Termination ............................................................................................................................ 93
19 Force Majeure ........................................................................................................................................ 94
20 Ownership .............................................................................................................................................. 95
21 Limitation of Liability ............................................................................................................................... 95
22 Time of the Essence ............................................................................................................................... 95
23 Confidential Information ......................................................................................................................... 95
24 Miscellaneous ......................................................................................................................................... 96
Annexure-1: Detailed Scope of Work .................................................................................................. 98
T Ta ab bl le e- -0 01 1: : Techno-Functional Requirement Specifications ............................................................................... 119
Table-02: Broad Specifications for Hardware and Devices .............................................................................. 126
Table-03: Broad Specifications for Data Center ............................................................................................... 157
Table-4: Broad Specifications for Network Layout ............................................................................................ 172
Table-05 Broad Specifications for Video Conferencing Equipment & Software ............................................... 175
Table-06: Broad Specifications for IP Telephony Equipments & Software ....................................................... 178
Table-07: Broad Specifications for Email Solution ............................................................................................ 186
Table-08: Broad Specifications Antivirus/ Anti-Spam ....................................................................................... 200
Table-09: Broad Specifications EMS/ NMS ...................................................................................................... 204
Table-10: Broad Specifications of Building Management System .................................................................... 221
Annexure-2: Deliverables & Performance Parameters .................................................................... 227
Annexure-3: Preliminary Implementation Plan ................................................................................ 240
Annexure-4: Price Schedule .............................................................................................................. 241
Annexure-5: Payment Milestone ....................................................................................................... 245
Annexure-6: Proforma for Performance Bank Guarantee (PBG) ................................................... 250
Annexure-7: Owner Safety Rules ...................................................................................................... 253

Confidential Page 4

Bi d Dat a Sheet
Bid Document No- ITPS/CC-22/2008/68, Date 03.09.2008

Date of Issue Bid Document 03
rd
Sep 2008
Address for Communication
Contract Cell,
Orissa Power Generation Company Limited
IB Thermal Power Station
AT/PO : Banharpalli,
Dist: J harsuguda
Orissa -768234
Tele: 06645-222224
Fax : 06645 222249
contractcell@opgc.co.in
Bid Document
Bid Document shall be available on the website
(http://www.opgc.co.in) for download from 03
rd
Sept 2008
to 15
th
Sep 2008
Pre-Bid Clarification
The queries on the Bid Document if any shall only be
received on 16
th
& 17
Th
of Sep 2008. All queries should be
addressed to contractcell@opgc.co.in. The Bidders shall
be invited for a pre-bid meeting at OPGC Head Office
Fortune Towers, Chandrasekharpur, Bhubaneswar on
22
nd
& 23
rd
of Sep 2008 in which all the received queries
shall be discussed and confirmed to all the bidders.
Last Date, Time and Place for submission
of Bids
By 10:00 Hrs on 14
th
Oct 2008at
Contract Cell, OPGC
IB Thermal Power Station, Banharpali,
District: J harsuguda, Orissa
EMD to be submitted as part of bid
Amount: Rs 6,00,000 (Rupees SIX LAKHS ONLY)
Mode : DD/ Bank Guarantee
Bank : In case of DD, one of the authorized banks as per
Bid Invitation details. In case of BG any schedule Bank
(except co-operative Banks).
Period of Bid validity
180 days from the last date of submission of Bids or any
extension thereof.
Date & Time of Opening of Techno-
Commercial Bid
15.00 Hrs of 14
th
Oct 2008
Demonstration and Bidder Interactions
Exact dates of visit to OPGC Head Office, Bhubaneswar will be
communicated individually to each Techno Commercially
qualified Bidders.
Date and Time of Opening Price bids To be intimated to the Techno commercially Qualified Bidders.
Negotiation Only qualified bidder will be invited for this activity.
Agreement Signing Will be intimated.

Confidential Page 5

Di scl ai mer
The purpose of this document is to give the bidders information to help them understand the scope of the IT
Solution required for OPGC. In addition, OPGC encourages bidders to provide alternate innovative and proven
approaches to the Solution that will minimize cost, time and risk and will maximize the potential success of the
project. The information on existing IT infrastructure and business processes of OPGC as detailed under
Appendix A, are indicative only and the Bidder shall be fully responsible for carrying out due diligence and
queries at his level to satisfy his requirement with respect to participating in the bid. OPGC reserves the right to
provide additional information at its sole discretion.

The information contained in this document is confidential in nature. The bidders shall not share this information
with any other party not connected with responding to this Bid document.

OPGC makes no representation or warranty and shall incur no liability under any law, statute, rules or regulations
on any claim, the potential bidder may make in case of failure to understand the requirement and respond to the
Bid document. OPGC may, in its absolute discretion, but without being under any obligation to do so, update,
amend or supplement the information in this Bid Document.

Contract Cell,
Orissa Power Generation Company Limited
IB Thermal Power Station
AT/PO : Banharpalli,
Dist: Jharsuguda
Orissa -768234
Tele: 06645-222224
Fax : 06645-222249
e-mail: contractcell@opgc.co.in

Confidential Page 6

Section 1: Project Introduction

Confidential Page 7

1. 1 About OPGC
Orissa Power Generation Corporation Limited (OPGC) was incorporated on November 14, 1984. OPGC
started as a wholly owned Government Company of the State of Orissa with the main objective of establishing,
operating & maintaining large Thermal power generating stations. In the pursuit of its objective, OPGC
established IB Thermal Power Station (ITPS) having two units of 210 MW each in the Ib valley area of
J harsuguda District in the State of Orissa. The plant went into commercial operation from 1996. The entire
generation from these units are committed to Gridco the state owned Trading Company on the basis of a long-
term power purchase agreement.
As a part of the reforms process in the energy sector, the State Govt. divested 49% of the equity in favour of a
Private investor i.e. AES Corporation of USA in early 1999 through International Competitive Bidding (ICB)
process. OPGC with its present Ownership structure is unique of its kind in the country and has excellent track
record of plant performance and earnings. The Company has earned many state as well as national level awards
and recognitions. Today OPGC has firmly established its credentials as a successful power generating company
both technically & commercially by providing safe, clean & reliable power.
ITPS has a good Town Ship with all modern amenities. The township along with the plant is surrounded and well
protected with a boundary wall of 12 KM length. The township comprises of quarters for 672 Employees. It
contains Training Hostel, Erector's Hostel (Guest House), English Medium DAV school, Oriya Medium High
School, Officers Club, Community Center, Shopping Complex, Hospital, Banks, Post Office, Bust stand, temple &
Helipad.

OPGC's stated vision, mission and core values are:
a) To be one of the best and reliable power utilities of India
b) To make every work place a safe work place
c) To keep the environment clean
d) To be socially responsible for employees and society

Strength of OPGC
a) This is a Pithead Thermal Power plant with coal field located nearby & a Merry-Go-Round (MGR) system
for Coal transportation.
b) There is adequate water availability from the nearby Hirakud Reservoir with an Intake Channel connected
to Reservoir.
c) Long term PPA with the State Power Transmission utility i.e. GRIDCO for 100% off-take.
d) Payment security mechanism comprising Escrow Account and revolving Letter of Credit with Gridco.
e) Infrastructure like land and common facilities are already available for further expansion.
f) A Dedicated workforce of Young Engineers & support staff.
g) Long term Fuel Linkage Agreement with Mahanadi Coalfield Limited (MCL) for supply of coal.

Confidential Page 8

1. 2 Fut ur e Busi ness Pl an
OPGC is in the process of further capacity addition of another 1200 MW at the same location. Requisite land is
already in physical possession. Water linkage & required infrastructure are in place. The Capital Investment for
the expansion project will be Rs. 5700 crores (approx.). OPGC has been allotted two Coal Blocks namely
Manoharpur and Dip Side of Manoharpur, having indicated reserves of 531 million tones, from the Ministry of
Coal, GOI through Govt. Dispensation Route and is in the process of entering into mining development activities
for its own captive use..The initial capital Investment for mining activities is estimated to be Rs. 800 crores. OPGC
is also planning to enter into Power Trading business in near future and may also extend its business to multi-
locations in India.

1. 3 ERP Pr oj ect Backgr ound Not e
It is envisaged that OPGC's business transformation will result in new business processes through extensive
process change as it seeks improved efficiency, expansion into new markets and partnerships. OPGC's IT
strategy has been developed based on aligning OPGC to become an efficient organization, both for its existing
operations and keeping in view future growth. OPGC is seeking to replace the current in-house developed
systems in the corporate centre and Plant with a centralised, ERP solution. The key reason for seeking a
centralised, ERP Solution is that the existing in-house applications are disparate, lack seamless integration and
have become very complex to extend to new business processes. Therefore, it is desired to establish integrated
business applications architecture based on SAP ERP backbone that will support OPGC's IT strategy and will in
turn move its larger objectives of attaining higher efficiency and growth. OPGC, accordingly, intends to seek
proposals from prospective bidders and shortlist the most eligible bidder to become the Implementation Partner
OPGCs goal and objective for ERP implementation is to enhance performance through
a) Improving Operational Efficiency
b) Driving Revenue Growth
c) Increasing Compliance

Confidential Page 9

Section 2: Scope Of Work

Confidential Page 10

2. 1 Suppl y of Har dwar e and Non-SAP Sof t war e
2.1.1 Supply of Hardware Data Center Equipments
2.1.2 Supply of Hardware Servers, Storage, Backup Devices, Racks & Other Hardware (PCs/Printers) etc.
2.1.3 Supply of Hardware Networking Equipments
2.1.4 Supply of Hardware Video conferencing Equipments
2.1.5 Supply of Hardware IP Telephony Equipments
2.1.6 Supply of Non-SAP Software Messaging & Collaboration System.
2.1.7 Supply of Non-SAP Software Anti Virus / Anti Spam /Content Filtering
2.1.8 Supply of Non-SAP Software EMS/NMS and Service Desk tools.
2.1.9 Supply of Non-SAP Software Building Management System(BMS)
2.1.10 Supply of Non-SAP Software Video conferencing system
2.1.11 Supply of Non-SAP Software IP Telephony System
2.1.12 Supply of Non-SAP Software Other Software
2. 2 Desi gn, I nst al l at i on & commi ssi oni ng of I nf r as t r uct ur e
2.2.1 Design, installation & commissioning of Data Centre including civil constructions work (OPGC will provide
bare floor space along with provision of power supply).
2.2.2 Installation & commissioning of Hardware.
2.2.3 Installation & commissioning of Networking Components.
2.2.4 Installation & commissioning of Video Conferencing System
2.2.5 Installation & commissioning of IP Telephony System
2. 3 I mpl ement at i on of t he SAP appl i cat i ons
2.3.1 Conducting Business Process Study.
2.3.2 Mapping of Business processes as per Business Blueprinting.
2.3.3 Conceptualizing, Developing, Configuring and Testing the Solution.
2.3.4 SAP Application installation on development, quality and production instances.
2.3.5 Data migration to SAP system.
2.3.6 Go-live and Stabilization Support.
2. 4 I mpl ement at i on of Non-SAP appl i cat i ons
2.4.1 Active Directory implementation with Single Sign On (SSO).
2.4.2 Messaging and Collaboration solution with Black Berry integration.
2.4.3 Anti-Virus, Anti-Spam solution & Content Filtering.
2.4.4 Enterprise Management System (EMS) / Network Management System (NMS) & Service Desk
2.4.5 Building Management System (BMS) for Data Center.
2.4.6 Video Conferencing Application
2.4.7 IP Telephony Application
2.4.8 Implementation Stabilization Support.


2. 5 Pr oj ec t Management i n di f f er ent phases, Change Management and Tr ai ni ng.
The work covering all the above elements put together will be completed by the Bidder on a Turnkey
basis.
2. 6 Post I mpl ement at i on suppor t ser vi ces f or r unni ng t he SAP Appl i c at i on, Non-
SAP appl i cat i ons and I nf r ast r uct ur e Faci l i t y Management ser vi ces.
2.6.1 SAP Application Support
2.6.2 Non-SAP Application Support
2.6.3 Infrastructure Facility Management Support
2.6.4 Hardware & Network Equipment maintenance


Section 3: Bidding Procedure


3. 1 For mal I nvi t at i on t o Bi d

NOTICE INVITING TENDER

1. Bids in two Parts (Techno-Commercial & Price Bid) are invited from financially sound & authorised SAP
Implementation Partners having PF Code, IT PAN & VAT/Sales Tax Registration Certificates, Service Tax
Registration Certificate, Professional Tax Registration Certificate, on behalf of the OPGC Ltd. for the work of
Implementation of SAP ERP, Non-SAP Applications and related IT Infrastructure along with Post-
Implementation support with Facility Management at OPGC.
2. OPGC reserves the right to directly invite any organisation to bid for the project and evaluate them on a
competitive basis along with other bidders.
3. The Bid & Rates shall be in the prescribed form provided in the Bid Document.
4. The Contract Period is for 12 (Twelve) Months for the Project Implementation from the date of Signing of
Agreement and 48 (Forty Eight) Months for providing Post Implementation Support with Facility Management
from the date of Final Acceptance of the Project. The Project shall be implemented within 6 (Six) Months form
the date of sign of Agreement and subsequent 6 (Six) Months shall be for Post Go-live Stabilization Support.
5. The queries on the Bid Document if any shall only be received on 16
th
& 17
Th
of Sep 2008. The Bidders will
be invited for a pre-bid meeting at OPGC Head Office Fortune Towers, Chandrashekarpur, Bhubaneswar
on 22
nd
& 23
rd
of Sep 2008 in which all the clarifications of the received queries will be discussed and be
confirmed. The queries should be addressed to contractcell@opgc.co.in.
6. Bidders should familiarise themselves with the site conditions before submitting the Bids.
7. Any Bidder for the works shall not be the witness in the Bid of any other Bidder, for the same works. Failure to
observe this condition shall render the Bid of the Bidder tendering as well as of those witnessing the Bid,
liable for rejection.
8. Bids will be received up to 10.00Hrs of 14
th
of Oct 2008 and Techno-Commercial Bid shall be opened at 15.00
Hrs of 14
th
of Oct 2008 in presence of the Bidders or their duly authorized representatives.
9. The Bid shall be accompanied by Earnest Money (EMD) of Rs. 6,00,000.00(Rupees Six Lacs only). The
Earnest Money offered shall be in shape of Demand Draft drawn in favour of Orissa Power Generation
Corporation Ltd. and payable at State Bank of India (Code-9510) / Andhra Bank (Code-0662) / Central Bank
of India (Code-Belpah) or Bank Guarantee issued by a scheduled Bank( excluding Co-operative Banks) in the
enclosed proforma (Appendix-B4) in the bid document. The EMD submitted in the form of BG should be valid
for 6(Six) months from the date of opening of the Techno Commercial Bid. Any Bid not accompanied with
Earnest Money in accordance with aforesaid provisions shall be rejected by the Owner as non-responsive Bid.
No interest will be payable by the Owner on the said amount covered under Earnest Money / other security
deposits. The Earnest Money of all unsuccessful Bidders will be returned within thirty (30) days after the
award of the Agreement.
10. The Bid shall be accompanied with letter of undertaking on non- judicial stamp paper of appropriate value in
the prescribed proforma (Appendix-B1) in the Bid document.
11. In consideration of the Owner opening and considering the Bid for purpose of award of Agreement, Bidder
shall keep his Bid valid for a period of 180 days(One Hundred Eighty) from the last date for submission of
Bids or any extension thereof. During this period the Bidder agrees not to vary, alter or revoke his offer either
in whole or in part. If the Bidder however, fails to keep his offer valid for 180(One Hundred Eighty) days or
varies its terms and conditions during the said period then the Owner shall be entitled to forfeit the Earnest
Money amount without any notice or proof of damages etc.


12. On finalization of Bid, the successful Bidder will submit a security deposit @10% of the Contract value
towards the head of Project in the form of Performance Bank Guarantee (PBG) at Annexure-6 of Appendix-C:
Contract Document, on signing of the Agreement. The EMD of all the Bidders shall be returned on award of
the contract.
13. A Bidder shall submit the offer which satisfies each and every condition laid down in this notice and other Bid
documents, failing which the Bid will be liable to be rejected.
14. The Orissa Power Generation Corporation Ltd. do not bind them to accept the lowest or any Bid or to give any
reasons for their decision. The Orissa Power Generation Corporation Ltd. reserves the right of accepting the
whole or any part of the Bid or split the total scope of work among eligible Bidders and Bidder (s) shall be
bound to perform the same at his/their quoted rates.

For and on behalf of Orissa Power Generation Corporation Ltd.

SignatureSd/-

Senior Manager (PSM), Contract Cell, ITPS.


3. 2 Bi ddi ng Pr ocedur e
The Bidder shall bear all costs associated with understanding the scope of work, bid preparation and bid
submission. OPGC will in no case be responsible or liable for these costs, regardless of the conduct or outcome
of the bidding process.
3.2.1 Qualification to bid
The bidding process will be open to any Authorised SAP Implementation Partner, who shall be able to supply,
design, install and commission all of the components as described in the Broad Scope of work at Section- 2 and
Detail Scope of Work at Annexure-1 of Appendix-C and be able to provide Post implementation support services
with Facility management, either on their own or by forming a consortium

The only exclusion is SAP Product and related software licenses which will be procured from SAP
directly.

The bidders must also meet the following mandatory qualification criteria with respect to the above.

Mandatory Qualification Criteria for Bidding

SN Parameter Description
Supporting
Documents
Bidder
Response
Reference
1 Implementation
capabilities in
Power
Generation
The Bidder should have done end-to-end
SAP implementation in at least 2 Power
Generation Companies.
Documentary
evidence in form of
Purchase Order or
Completion
Certificate or any
other document
from customer

2 Global SAP
Implementation
Experience

The Bidder should be Authorised SAP
Implementation Partner and must have
done 10 SAP Implementations as the
Lead vendor.

Out of these 10 implementations, there
has to be a minimum of 5 end-to-end
implementations containing at least Five
of the following modules and all the five
implementation should have a user base
of 500 or more.

1. Finance & Controlling / Costing
2. Material Management
3. Asset Management
4. Project systems
5. EH&S
6. HR and Payroll
7. Maintenance Management
8. Quality Management
9. Employee Self Service
10. Business Intelligence.
Documentary
evidence in form of
Purchase Order or
Completion
Certificate or any
other supporting
document from
customer

As per
Appendix-
B6: Profile
of
Implement
ation
Partner
Number of
customer
acquisition

Stage of
Implementation

Scope of
Implementation

Testimonial


Supporting
Documents
Bidder
Response
Reference
3 Indian SAP
Implementation
Experience

The Bidder should have done at least 3
successful end-to-end SAP
implementations as a Lead Vendor of
which at least one implementation in an
Indian PSU.
All the implementations should have been
done for at least five of the following
modules, with a user base of 500 or more.

1. Finance & Controlling / Costing
2. Material Management
3. Asset Management
4. Project systems
5. EH&S
6. HR and India Payroll
7. Maintenance Management
8. Quality Management
9. Employee Self Service
10. Business Intelligence
Documentary
evidence in form of
Purchase Order or
Completion
Certificate or any
other supporting
document from
customer

As per
Appendix-
B6: Profile
of
Implement
ation
Partner
Number of
customer
acquisition

Stage of
Implementation

Scope of
Implementation

Testimonial
Note: The Indian and global experiences are mutually exclusive and all the customers should have unique names.
3 SAP Experience
in Power
industries
Experience in computerising all or most
of associated business functions typical of
a thermal power plant such as Plant
Maintenance, Materials, Plant
Performance, Efficiency measurements,
Mining & Coal handling and Environment
Health and Safety etc.
Valid documentary
evidence in form of
Major processes
covered.
As per
Appendix-
B6: Profile
of
Implement
ation
Partner
Scope of
Implementation

Customer
feedback

Presentation
4 Systems
Integration
Capability
The Implementation Partner should have
executed and completed at least One
turnkey projects, in India, involving ERP
implementation, Hardware & Networking
installation and integration, Data Center
set-up and / or facilities management. The
turnkey project value in one or more
projects should not be less than INR 10
crores in last three years.
Documentary
evidence in form of
Purchase Order or
Completion
Certificate stating
the value or any
other Customer
Testimonials
As per
Appendix-
B6: Profile
of
Implement
ation
Partner
Customer
acquisition

Stage of
implementation

6 Implementation
Team
The Implementation Partner has to
provide the details of the Senior Project
Team Members who must fulfil all the
requirements of the Role mentioned in the
RFP
Brief Resume As per
Appendix-
B6: Profile
of
Implement
ation
Partner
Qualitative
7 Financial
Stability,
Manpower &
Quality
a) The companys turnover from IT
Application Implementation and
Systems Integration services for the
last three financial years (2005, 06
and 07) should be at least INR 500
crores for each of the three years and
should have a positive net worth in
each of the last three years.

b) The Implementation Partner should
have its Delivery Centre / R& D / CoE
in India with overall employee
strength of not less than 5000
employees on its payroll as on 31
st

March 2008. The Implementation
Audited Financial
Statements for the
each of three
years.

Self certificate from
companys
authorised
signatory

As per
Appendix-
B6: Profile
of
Implement
ation
Partner
Financials

Manpower

SAP Focus

Accreditations


Supporting
Documents
Bidder
Response
Reference
Partner shall have a trained Delivery
staff strength of at least 500
personnel on its payroll, of the offered
SAP product, as on 31st March 2008.

c) The Implementation Partner should
have a CMMI Level V Certification

Copy / details of
certificate
8 Alliance with
Vendors /
Vendor
Accreditation
The Implementation Partner (IP) needs to
be an authorized partner of SAP.

The Implementation Partner should have
the Partner Certification from the offered
SAP product and other Hardware &
Software vendors respectively.

Valid documentary
evidence.

Please provide the
Vendor
Accreditation
Certificate
As per
Appendix-
B6: Profile
of
Implement
ation
Partner
Partnership
certificate

Vendor
accreditation
certificate

Note: The Bidder has to provide responses to the above failing which it will not be considered for
Technical Scoring. Please use additional sheets wherever required.

Hardware and Network Manufacturer Partner Capability
Supporting
Documents
Bidder
Response
Reference
1 Implementation
in large
organisations

The Hardware platform suggested should
have been successfully implemented in at
least five organizations, in SAP
environment with a user base of 500 or
more
Documentary
evidence in form of
Customer
Testimonials
As per
Appendix-
B7: Profile
of
Implement
ation
Partner
Customer
Testimonials
2 Hardware
configuration
The hardware platform configuration
should be RISC / EPIC.
Details of Hardware
configuration.
Scope of H/W
installation
3 Guarantee
Support
Guarantee support for the provided
hardware for minimum 5 years after
completion of warranty with regard to
service and spares and must be willing to
undertake Annual Maintenance Contract
(AMC) for all the supplied equipment in
the Bid for minimum 5 years after
completion of warranty with manpower
stationed at OPGC.
Submit self
certificate to this
effect from the
companys
authorized
signatory.
Self
authenticated
certificate
4 Authorized
Partner
Must be an OEM or authorized partner of
the OEM for minimum 6 months.
Please submit
certificate from the
OEM to this effect.
Partnership
certificate
5 Hardware
Supply and
installation
Experience
The Hardware partner should have
executed a single order of minimum value
of Rs. 5 crores for supply and installation
of Hardware in India during the last 2
years.
submit the order
copy

Copy of order
6 Local
presence

The Hardware manufacturer must have
offices in India and the hardware
manufacturer should have support centre
for the quoted hardware in India.
Details of offices
and activities
performed to be
submitted
Offices
Manpower
Brief Financials
7 Support
services

The Hardware manufacturer must be
capable of providing 24 X 7 support
services on technical issues, upgrades,
bug fixes etc related to hardware.
Self certificate
From companys
Authorized
Signatory
Customer
testimonials


Note: The Bidder has to provide responses to the above failing which it will not be considered for
Technical Scoring. Please use additional sheets wherever required.

Note:
The following are expressly barred from bidding for this project either individually or as a member of any
consortium
a) Any business unit of PricewaterhouseCoopers Private Limited (PwC) even if not involved in current
engagement being executed.
b) Any subsidiary or affiliate of PwC
3.2.2 Consortium Guidelines
In case, the Bidder bids by forming consortium then the following guidelines shall be followed.

The consortium should consist of Authorised SAP Implementation Partner, Hardware manufacturer and Network
component manufacturer, Non SAP Software license provider & Service providers. The Implementation Partner
must be an Authorised SAP Implementation Partner and should be the leader of consortium, responsible for
providing the total solution to OPGC. While this is acceptable to OPGC in principle, it expects certain
requirements to be fulfilled by each of the consortium member. These include the following preconditions

Sl.
no
Preconditions
1 The Implementation Partner should be the Lead Partner of the consortium.
2
The response to the Bid has to be submitted only by the Implementation Partner & will be designated as the Bidder
for the purpose of this Bid.
3
The response to the Bid must contain a written declaration by the competent authority of all the consortium
members that :
a) They have collectively agreed to respond to the Bid.
b) They have nominated the named entity (name of Implementation Partner) as the leader of the consortium and his
nomination shall be evidenced by submitting a letter of authorization signed by legally authorized signatories of
all the members of the consortium.
c) The consortium leader is authorized to receive instruction / communications from OPGC, authorized to incur
liabilities and shall deliver all the provisions of the contract on behalf of consortium members.
d) All members of the Consortium shall be responsible and liable jointly and severally for the execution of the Scope
of Work under Agreement in accordance with the terms and conditions of the Agreement. However, the Leader
of the Consortium shall be solely responsible for the integration, interface, coordination and completeness of the
entire Scope of Work including establishment of Performance Guarantees under the Agreement. A format in
which such a declaration may be submitted is given in Appendix-B5: Consortium MOU.
4
The Implementation Partner cannot submit different bids by forming consortium with different Hardware
Manufacturer and Network Hardware & Network Service Provider.
5 It will be Implementation partners responsibility to certify the work completed by the other consortium members.
6 Payments shall only be released to the Implementation Partner against his Invoices as per the Price schedule.
7
The bidder should provide a declaration from all the consortium members that they have full property right or
requisite right to use all intellectual property / tool they propose to supply or use in course of this project.
8
The Implementation Partner must provide in writing the mechanism for decision making and dispute resolution
among the Consortium members.
9
The offer shall include all the information required for a Bid as described in Bid Document including the eligible
criteria, for each Consortium member.


10 The offer shall be signed only by the Implementation Partner.
12 The offer submitted by one bidder shall not be permitted to be transferred to another bidder.
3. 3 St r uct ur e of Bi d Document
The Bid Document is structured into four Sections and three Appendices.
Section-1 to Section-4 describes the Project Introduction, Broad Scope of Work, Bidding Procedure and
Evaluation of bids.
Appendix-A provides indicative details of the existing IT infrastructure & Facilities in OPGC, a brief overview of the
business processes.
Appendix-B outlines the supporting documents/inputs which are to be submitted as a part of the bid.
Appendix-C outlines the Agreement along with supporting Annexures.
3. 4 Submi s si on Of Bi d
3.4.1 Complete Bid
Both the Techno-commercial & Price Bid in shape of soft copy (PDF Format), in password protected / encrypted
CDs or DVDs, shall be submitted in separate and sealed covers, super scribed as Techno-commercial and price
Bid. The passwords / decryption key need to be typed and put into a separate envelope. All these envelopes
shall be put in to a third envelope. All the envelopes must be sealed & superscripted with Name of the Work, NIT
No., and due date of opening. The full name, postal address, telegraphic address and Telex / telephone / fax / E-
Mail of the Bidder shall be written on the bottom left corner of the envelope. Completed Bid shall be submitted
within due date and during office hours only. The bids can be sent by speed post /registered post or submitted in
person so as to reach the accepting authority before the date & time fixed for submission of the bid. Bids sent by
any other mode(s) will be rejected.
The Bidder will be required to return the original Bid Document (in soft copy) as a part of the response to the Bid.
It shall be expressly agreed therein by the Bidder that he has read and understood the complete Bid Document
and shall comply with the same. All pages of the original Bid Document, Techno-Commercial Bid and Price Bid
must be signed (scanned signature) by the person or persons of the Implementation Partner, duly authorized to
sign such a Bid. Any changes, erasing, alterations, additions or overwriting made in the Bid will be valid only if the
person or persons signing the bid have authenticated the same with their signature.
Deviation, if any, from the Bid specifications and other parts of the Bid Document, shall be listed out separately
and clearly by the Bidder as per the format of Exclusion /Deviation Statement attached as Appendix-B3. If
deviations are not clearly listed as such, they will not be considered by OPGC later.
3.4.2 Bid Submission Format
The Bidders are requested to submit the proposals written only in English language. Each proposal shall have
three parts containing the following:

Part - A: Certificate of Acceptance of Important Conditions and EMD
a) Covering letter.
b) Crossed Demand Draft / BG for requisite amount drawn in favour of Orissa Power Generation
Corporation Ltd. in the manner prescribed in NIT enclosed herewith towards the Earnest Money.
c) Letter of undertaking in judicial stamp paper of worth Rs. 10.00 in the format enclosed at Appendix-B1.
d) Consortium MOU, as per Appendix - B5
e) Documents in support of authentication of the person who signed the Bid. Only proprietor, partner,
directors or permanent employee with due power of attorney is recognized for such signature.


Part - B: Techno-Commercial Proposal
a) Statement of work.
b) Project Charter.
c) Details of work of similar nature and magnitude executed by the Bidder during last three years
d) Details of present commitments of the Bidder.
e) Scanned copy of valid VAT/Sales Tax Registration Certificate and IT PAN.
f) Scanned copy of Provident Fund Registration No. and Service Tax Registration No. of appropriate
category issued by competent authority.
g) Scanned copy of the Registration of Firm / Company.
h) Present & permanent Address for correspondence along with Telephone No./Fax No./E-mail address
etc.
i) Any other technical information, Bidder wishes to furnish.
j) Resumes of personnel who will be working on the Project.
k) Formal proposal and response to Functional and Technical requirements.
l) The Bidder shall submit a detailed Service Level Agreement (SLA) covering severity levels, expected
service windows, expected service levels, performance measurement matrix, escalation matrix etc. for
the post implementation support along with the bid document.
m) Exclusion /Deviation Statement in the proforma at Appendix-B3.
n) Unpriced Schedule of BPS and Bill of Quantity, being proposed by Bidder. Techno-Commercial
Proposal shall not contain any price.
o) Scanned copy of supporting documents for Important Conditions as specified in clause 3.2.1:
Qualification to bid
p) Profile of Implementation Partner and Hardware Partner as per Appendix- B6 and B7.
Part - C: Price Proposal
Price bid shall include -
1. Original price bid / schedule of quantity duly filled in, signed & stamped on each page as token of
unconditional acceptance. The Bidder shall take utmost care in filling the Bid documents corresponding to
instruction to Bidder and relevant information elsewhere in Bid document.
Price Bid shall be completed in all respects with all their attachments / enclosures, if any.


The submission of various documents constituting the bid shall be submitted in the manner as detailed below.
Part of Proposal Submission Type
Part A Hard Copy ONLY. All documents need to be submitted in original.
Part B & C Soft Copy in CD / DVD
- For security purpose all CDs and DVDs will be password protected or
encrypted.
- All passwords or decryption information must be provided in a sealed
envelop and shall be opened in front of the bidders as per the bid sheet
schedule.
- All signatures needed for this part can be digital or scanned in nature.
- This authorization in favour of person/persons signing the bid must be
duly supported by a stamped Power-of-Attorney from the Implementation
Partner (backed up by board of directors resolution) which must be
submitted in HARD COPY along with the Bid. In addition, the
authorization letter of all the members of the Consortium indicating their
mandate to the leader of the Consortium for submitting the Bid must also
be submitted along with the bid.
3.4.3 Sealing the Bid
All the envelopes containing the Bid documents must be put in a tamper proof packet and sealed preferably with
lacquer. Appropriate care should be taken to protect the DVDs from damage.
3.4.4 Rejection of Bid
The Bid Document must be submitted in the form of printed document or soft copy as specifically mentioned in
3.4.2 above. Bids submitted by fax or email will not be treated as valid and rejected outright.

Once the deviations as submitted along with the original Bid documents are sorted out at mutually agreed terms
and conditions with all the participating Bidders, no further deviations are acceptable and any bids submitted with
any deviations shall be liable for rejection. Bids not containing all the parts will be rejected.
3. 5 I nst r uct i on t o Bi dder
3.5.1 Bidder to obtain their own Information
a) Bidder shall for all purposes and whatsoever reason may be, deemed to have independently obtained all
necessary information for the purpose of preparing his Bid. The correctness of the details given in the Bid
Document is for guideline/ information only, to help the Bidder to prepare his Bid.
b) Bidder shall be deemed to have examined the Bid documents and to have obtained his own information
in all matters whatsoever that might influence carrying out the implementation of the Project at the
scheduled rates and satisfied himself to the sufficiency of his Bid. Any error in description or quantity or
omission there from shall not vitiate the Agreement or release the Implementation Partner from executing
the work comprised in the Agreement according to the scope of work and specifications at scheduled
rates. He is deemed to know the scope, nature and magnitude of implementing the Project.


c) Bidder shall be deemed to have visited the sites, offices and surrounding areas, to have satisfied itself to
the nature of all existing Business processes and also as to the nature and the conditions of available
facilities and communications and possible interruptions there to the access and egress from site and to
have made enquiries, examined satisfied himself of the sites in respect to requirements for implementing
Project and to have made local independent enquiries on all matters affecting the Agreement. He is
deemed to have acquainted himself his liability for payment of Government Taxes, Customs and Duties
and other charges.
d) Any neglect or failure on part of the Bidder in obtaining necessary and reliable information on issues
stated in the above clause or any other matters affecting the Agreement shall not relieve him from any
risks or liabilities or the entire responsibility for implementing the SAP Solution at the scheduled rates and
time in strict accordance with the contract documents.
e) Any change in site conditions or technological requirement shall be binding on the Implementation
Partner and no extra claim on this account shall be entertained.
f) The oral agreement or inference from conversation with any officer or employee of the Owner either
before, during or after the execution of the Agreement shall not in any way affect or modify the terms and
obligations herein contained.
3.5.2 Addenda / Corrigenda / Amendments issued to this Tender
a) OPGC reserves the right to issue any addenda or corrigenda to the Bid document without assigning any
reason thereto. In response to such addenda / corrigenda, the Bidders shall submit their Bid in a fresh
schedule. However, if the Bidder has already submitted his Bid prior to issue of such addenda /
corrigenda, they shall resubmit a fresh offer marked on the envelope as Amended Offer. The original
offer submitted by such party shall be destroyed in presence of the Bidder on the date of opening.
b) At any time prior to the deadline of submission of Bids, OPGC may, for any reason, whether at its own
initiatives or in response to a clarification by a prospective bidder, modify the bid document through
Amendment(s)
c) The Amendment(s) will be notified to all prospective bidders through the website and such Amendment(s)
will be binding on them.
d) OPGC may extend the deadline for the submission of bids, in order to allow the prospective bidders a
reasonable time in which to take the amendment(s) into account in preparing their Bids.

3.5.3 Extension of Bid Opening Date
OPGC may, at its sole discretion, decide to extend this Bid Opening Date and / or date for submission of Bids. In
such a case, all rights and obligations of OPGC and that of Bidders previously subject to the Bid Opening Date
will thereafter be subject to the new Bid Opening Date.
3.5.4 Bids Received Late
Any bid received by OPGC after the expiry of the specified date and time for submission of bids will be rejected
outright and returned to the Bidder. The Bidders must take all responsibility of submitting the Bids within the
prescribed date of submission of Bids. OPGC will not accept as valid reason or be responsible for any postal
delay or non-receipt / non-delivery of the Bids.
3.5.5 Modification and Withdrawal of Bids
3.5.5.1 Modification Request by Bidder
The Bidder will not be allowed to modify its Bid after its submission,
3.5.5.2 Withdrawal of Bid by Bidder
No bid shall be withdrawn during the period between the Bid Opening Date and the expiration of the bid validity


period as specified in Notice Inviting Tender. Withdrawal of a bid during this interval period may result in the
forfeiture of the Bidders Bid Security (EMD).
3.5.6 Acceptance of Important Conditions
Bidders may note that no deviations whatsoever to certain important conditions as per the RFP is permitted by
the Owner and therefore, the Bidders are advised that while developing their proposals and prices, these
conditions may appropriately be taken into consideration especially with respect to their effect, wherever
applicable, on the cash flow projections during the execution of the Agreement. Bidders are required to furnish
certificates to support the requirements furnished under clause 3.2.1 and Appendix- B6 and B7. Any Bid not
accompanied by such certificate shall be rejected by the Owner and shall not be opened.
3.5.7 Bid Validity Period
All bids, not rejected for any other reason, will remain valid for a period of 180 (One Hundred Eighty) days from
the last date for submission of Bids or any extension thereof. Each Proposal shall indicate that it is a firm and
irrevocable offer. Non-adherence to this requirement may form ground for declaring the proposal as non-
responsive. In case of the bidder revoking or withdrawing / cancelling his Bid, varying any term in regard thereof
during the validity period of the Tender without the written consent of OPGC, the Bid submitted shall be liable for
rejection and will entail forfeiture of the Earnest Money paid along with the Bid. On completion of the validity
period 180 (One Hundred Eight) days, unless the bidder withdraws its bid in writing, it will be deemed to be valid
until such time that the bidder formally (in writing) withdraws its bid.
3.5.7.1 Extension of Period of Bid Validity
In exceptional circumstances, OPGC may request all the Bidders consent to an extension of the period of validity
of their respective bid. The request and the response thereto will be made in writing. Extension of validity period
by the Bidder must be unconditional. The bid EMD provided in the form of BG will also have to be accordingly
extended. A Bidder will not be permitted to modify his bid.
3.5.8 EMD
Bids not accompanied by the requisite EMD, or bids accompanied by EMD of inadequate value shall not be
entertained and in such a case bids shall be returned to the Bidders without being opened.
The EMD may be forfeited,
a) If the Bidder withdraws its bid during the period of bid validity.
b) In the case of a successful Bidder, if the Bidder fails within the specified time limit to furnish the
acceptance of Letter of Award and / or fails to submit Performance Guarantee of requisite amount.
c) If, during evaluation of bids, OPGC ascertains that there is discrepancy in the bid price due to arithmetical
error, and on communicating such error to the Bidder, the Bidder does not accept the proposed correction
of errors.
3.5.9 Price Basis, Taxes and Duties
Complete details of Commercial Bid are to be provided in specified schedules in Bid Proposal Sheets (BPS). All
prices are to exclude central and local taxes and duties which shall be indicated separately. All items and services
are to be quoted in Indian Rupees. No adjustment of the contract price shall be made on account of variation of
costs of labour and materials or any other cost component affecting the total cost in fulfilling the obligations under
the Agreement. The prices once offered must remain firm and shall not be subject to escalation due to fluctuation
in foreign currency or for any reason; however Taxes, Duties, Levies etc prevailing during the contract period as
per payment milestones shall be paid. All the Bidders are requested to familiarise themselves with the laws, rules
and regulations prevailing in India and consider the same while developing and submitting their Proposal.

The Bidder has to consider all taxes, duties, levies, cess etc., applicable for executing this Contract and
accordingly, shall indicate the excise duties, customs duties and all other taxes, levies, cess etc. considered on


supplies and services either imported or locally sourced included in his offer. Non inclusion or omission either
declared or not declared on the part of the Bidder shall be construed as inclusive of such duties or taxes in his
quoted price as may be applicable as of 7 (seven) days prior to the Date of opening of Techno-Commercial bids.
3.5.10 Rates To Be In Figures & Words
The Bidder shall quote both in figures and in words for the rates and amount Bided by him in the Schedule of
quantities / Price schedule forming part of the Bid document, in such a way that interpolation is not possible. The
amount of each item shall be worked out and entered and requisite total given for all items. The Bided amount for
the work shall be entered in the Bid and duly signed by the Bidder. If any ambiguities are observed in the rates &
amount given in words & figures the following procedure shall be followed:
When there is difference between the rates in figures and words, rate which corresponds to the amount worked
out by the Bidder, shall be taken as correct.
When the rate quoted by the Bidder in figures and words tally but the amount is incorrect, the rate quoted by the
Bidder shall be taken as correct but not the amount.
When it is not possible to ascertain the correct rate by either of above methods, the rate quoted in words shall be
taken as correct.
3.5.11 Abnormal Rates
The Bidder is expected to quote the rate for each item after careful analysis of cost involved for the satisfactory
performance and completion of item work considering all specifications and conditions of Agreement. This will
avoid loss of profit or gain in case of curtailment or change in specification for any other item. In case the rates
quoted by the Bidder for any item are unusually high or unusually low it will be sufficient cause for the rejection of
the Bid unless the Owner is convinced about the reasonableness of the analysis for rate furnished by the Bidder
(on demand) after scrutiny.
3.5.12 Corrections & Erases
No erases or over writings are permissible. All corrections and alterations in the entries of Bid papers shall be
signed by the Bidder with date.
3.5.13 Details & Signature Of Bidder
The Bid shall contain the name, residence and place of business of person or persons making the Bid and shall
be signed by the Bidder with his usual signature. Partnership firms shall furnish the full names of the partners in
the Bid. It should be signed in the partnerships name by all the partners or by duly authorized representative
followed by the name and designation of the person signing. Bid by a Corporation shall be signed by an
authorized representative and a power of attorney / authorization on its behalf shall accompany the Bid. A copy of
constitution of the firm with names of all partners shall be furnished. In case of cooperative society, the authorized
representative of the society will sign the Bid. Similar principle shall be followed in case of any Trust and Hindu
Undivided Family business. The signature should be attested, at least by one witness.
3.5.14 False or Misleading Claims
OPGC may in its absolute discretion exclude or reject any proposal that in the reasonable opinion only of OPGC
contains any false or misleading claims or statements. OPGC has no liability to any person for excluding or
rejecting any such proposal.
3.5.15 Fraud and Corruption
Bidders are expected to observe the highest standard of ethics during the procurement stage and execution of this Agreement.
In pursuit of this policy, OPGC defines, for the purposes of this provision, the terms set forth below as follows:
corrupt practice means the offering, giving, receiving, or soliciting of anything of value to influence the action in
the procurement process or in Contract execution; and


"fraudulent practice means a misrepresentation of facts in order to influence a procurement process or the
execution of a Contract to the detriment of OPGC and includes collusive practices among Bidders (prior to or after
bid submission) designed to establish bid prices at artificial, non-competitive levels and to deprive OPGC of the
benefits of competition;
3.5.16 Contacting The Owner
From the time of bid opening to the time of Contract award, if any Bidder wishes to contact the Owner on any
matter related to the bid, he shall do so in e-mail.

All Technical queries, if any, shall be referred to the Head of IT, OPGC by the Bidder.
All Commercial queries, if any, shall be referred to Contract Cell, OPGC by the Bidder.
3.5.17 Conflict of Interest
Bidders must state in their submission any circumstances, arrangements, understandings or relationships that
constitute, or may reasonably be considered to constitute, an actual or potential conflict of interest with the
Bidders (or their consortium partners) obligations under this RFP (including but not limited to these conditions of
proposal) or under any contract which may be negotiated or executed between the Bidder and OPGC. Bidders
and their employees, agents, advisers and any other person associated with the Bidder must not place
themselves in a position which may, or does, give rise to a conflict of interest (or a potential conflict of interest)
between the interests of OPGC or any other interests during the bidding process.
3.5.18 Ownership of Responses
Without affecting any intellectual property rights, which may exist in a response to this RFP document, all
responses submitted will become the property of OPGC. Without limiting this section, OPGC reserves the right to
copy and reproduce responses for the purposes of evaluation, clarification, negotiation and/or contract execution
and anything else related to these purposes. In addition, OPGC will retain (soft and hard) copies of all responses,
evaluation, negotiation or such other materials as are required for the discharge of its legal obligations and in
order to efficiently and effectively manage any contract entered into with a Bidder.
3.5.19 Owners Right to Accept Any Bid and to Reject any or all Bids
OPGC reserves the right to accept or reject any bid or to annul the bidding process and reject all bids at any time
prior to Contract award, without assigning any reasons thereof and OPGC shall not entertain any claim
whatsoever on this account.
3.5.20 Clarification on Bids
During the bid evaluation, OPGC may, at its discretion, ask the Bidder for clarifications on its Proposal.
3.5.21 Language
English shall be the binding and controlling language for all matters relating to the meaning or interpretation of this
Contract.
3.5.22 Caution to Bidder
The person who submit the Bid or participate in the opening of the Bid must abide by the safety rule of OPGC
right from the plant gate. Some of the checkpoints are, the vehicle must have valid insurance & tax paid road
permit, valid driving license of the driver / Owner as the case may be. Persons with full shoes shall be allowed to
enter the plant & our plant gate shall provide other items such as hardhat, safety glass & visitor pass. Not more
than 2(two) persons for one Bid shall be allowed to participate in Bid opening.


Section 4: Evaluation of Bids


4. 1 Openi ng Of Bi ds
The Techno-Commercial bid shall be opened at a predetermined time, venue & date in presence of the Bidder(s)
or their authorized representative(s) who may like to be present. Partner, Director or permanent employee of the
firm duly authorized only can be the authorized representative. Price bid shall be opened at a future date under
intimation to all technically qualified Bidders and in presence of them or their authorized representatives who shall
participate.
4.1.1 Preliminary Examination of Proposals
OPGC will examine the Proposals to determine whether they are complete, whether required EMD have been
furnished, whether the documents have been properly signed, and whether the Proposals are generally in order.
If a Proposal is not substantially responsive, it shall be liable for rejection by OPGC. OPGCs determination of
Proposals responsiveness will be based on the contents of the Proposal itself and any written clarifications, if
sought for by OPGC and submitted by the Bidder.
4. 2 Eval uat i on & Compar i son of Bi ds
4.2.1 Basis for Technical Evaluation
OPGC will carry out a detailed evaluation of the bids previously determined to be substantially responsive, in
order to ascertain whether the technical aspects are in accordance with the requirements set forth in the Bid
Document. OPGC will examine and compare the technical aspects of the bids on the basis of the information
supplied by the bidders, taking into account the following factors:
a) Technical and Functional requirements
b) Bidders project approach
c) Capability of the Implementation Partner
i. Organization Strength and Business Focus
ii. Experience as a System Integrator
iii. Experience in providing IT support & Facility Management Services.
4.2.2 Basis for Price Evaluation:
4.2.2.1 OPGC will examine the Price Proposals to determine whether any arithmetical errors have been made,
whether the documents have been signed, and whether the Proposals are generally in order.
Arithmetical errors will be rectified on the following basis.
a) If there is a discrepancy between the unit price and the total price, which is obtained by multiplying
the unit price and quantity, or between subtotals and the total price, the unit or subtotal price shall
prevail, and the total price shall be corrected.
b) If there is a discrepancy between words and figures, the amount in words will prevail. If a Bidder
does not accept the correction of errors, its Proposal will be rejected and its bid security may be
forfeited.
4.2.2.2 The evaluation shall be based on the evaluated cost of completing the contract in compliance with all
commercial, contractual and technical obligations under this Bid including taxes, duties & levies etc. The
rates of taxes, duties and levies as applicable on seven (7) days prior to the date of Techno-commercial
bid opening shall be considered for the purpose of evaluation.
4.2.3 Techno Commercial evaluation:
The Techno Commercial Evaluation of bids shall be done in two stages as detailed below.


4.2.3.1 Stage I: Response to Mandatory Requirements
The evaluation committee, appointed by OPGC as a whole, evaluates the proposals on the basis of
their responsiveness to the Mandatory Requirement criteria (3.2.1 Qualification to bid). Proposal shall
be rejected at this stage if it does not respond to mandatory requirements criteria. Only those bidders,
who meet all the mandatory requirements, shall be considered for stage II evaluation.
4.2.3.2 Stage II: Response to Techno-Functional Qualification Criteria
The Techno-functional requirements are broadly categorized in two sections
(A) Capability of Implementation Partner (as in Appendix-B6 & B7)
(B) Technical-functional requirement specifications (as in Table-01 of Annexure-1 in Appendix-C,
Techno-functional Requirement Specifications).
There would be certain cut-off marks or criteria for each of the above sections. A proposal shall be
rejected at this stage if it fails to meet the minimum qualifying marks or cut-off points. The evaluation
committee, appointed by the OPGC as a whole, evaluates the proposals on the basis of the response of
the bidder to criterion set forth by OPGC.

OPGC shall notify the bidders that have secured the minimum qualifying mark, indicating the date and
time set for opening the Financial Proposals.
4.2.4 Award Criteria
OPGC will award the contract to the successful bidder whose bid has been determined to be substantially
responsive and to be economically advantageous, which will be established by weighing Tehno-Commercial
quality against price on a 70:30 basis.
The selected Bidder for OPGC shall be the bidder with the highest cumulative points.
4.2.5 Negotiation
The selected bidder will be notified in writing by OPGC inviting him for further Negotiations. Negotiations will be
held only at OPGCs corporate office.
4. 3 Si gni ng Of Agr eement
On finalization of negotiation, to the mutual satisfaction of both the parties, OPGC shall invite the selected bidder
through Letter of Acceptance (LOA) for the signing of the Agreement. The selected bidder shall execute the
Agreement within a period of Fourteen (14) days of receiving LOA from OPGC. The Agreement is to be signed in
English language in two originals, one each for OPGC and the Bidder
Within 14 days of signing of the Agreement, the Bidder shall submit 6 photocopies of the entire contract document
duly bound to OPGC.
The Bidder shall submit the following documents for signing of the formal Agreement:
a) Copy of detailed LOA duly signed on all pages as a token of acknowledgement of receipt.
b) Security Deposit as in the form of Bank Guarantee as per proforma Bank Guarantee for security
deposit in the contract document.
c) Non-J udicial Stamp Paper of value Rs.100/- purchased in Orissa, India for the signing of Agreement.
d) Permanent Account Number of all consortium partners allotted by Income Tax Department.
e) Self-attested Photostat copy of Notarized Power of Attorney by the Competent Authority or Board of
Directors resolution authorizing the individual(s), to sign the Agreement.


f) Self-attested Photostat copy of the Registration under Orissa State VAT, Service Tax, as applicable.
4.3.1 Failure to Sign Agreement / Commence The Work
Failure to sign the agreement and / or commence the Work within the date to be agreed upon after issue of LOA,
the LOA will be terminated and the Bidder will be liable to be debarred from participation in the Owners Tenders
for a period of two (2) years, besides forfeiture of EMD.


Appendix-A: Bidding Reference


Appendix-A1: Current IT Infrastructure details
A. Current IT Organization set-up
In line with OPGCs IT strategy, the efforts are to ensure that the IT imperatives of the organization are in line with
the business objectives. The IT department is headed by the Director (Operations). A steering committee under
chairmanship of Managing Director has already been constituted to monitor and ensure successful
implementation of SAP in the organization. This committee comprises of Director Finance, Director Operations,
Senior GM Head Finance/ P&A, DGM Projects and Support Services. Manager(El)-Head IT, who will be
responsible for all IT related technical support for SAP implementation, is also a member of this Steering
Committee.
B. Brief Description of existing Applications
1. Ramco e-Application 3.1 Enterprise Asset Management Systems. The modules are Maintenance, Inventory,
Purchase and HRIS. Operating System - WIN NT 4.0 & Database - MS SQL 7.0.
2. Locally developed Finance & Payroll package. Operating System - Win-2000 & Database - Oracle 8.0.
3. Locally developed Automatic Attendance Recording Software. Operating System WIN 2000 & Database -
Oracle 8.0.
4. Locally developed Generation MIS software. Operating System Win2000 & Database MS SQL 2000.
5. Knowledge Sharing A Document Server is deployed to share common documents for knowledge sharing.
Operating System Win2003
6. The Intranet Mailing Facility is extended to the users through the use of Microsoft Exchange Server 5.5 for 30
users & Red Hat Linux Send Mail for rest of the users at ITPS.
7. Client Operating System Windows Vista, Windows XP, Windows 98
8. Other client software MS Office 2000/2003/2007, MS Project 2000/2003/2007
C. Existing IT Infrastructure at OPGC Plant (Ib Thermal Power Station)
The bidder shall indicate in their proposal if the hardware, devices out of the following list can be used with
adequate details.
1. Hardware & Network
a) No of PCs - For details of No PC & Laptops please refer Appendix-A2: Business Processes
Requirement-Overview- Expected Number of Users
b) Local Area Network Layer-3 Fiber Optic Backbone Fast Ethernet Networking.
c) No of Backbone Switch -1, No of Workgroup Switches 6, No of Ethernet Switches 8 (All the
switches are D-Link/ Cabletron make)
d) Total No of Servers 6 (Intel Xeon, PIV & PIII Compaq, IBM & HCL make)
e) Backup Solution. Daily Backups are taken in Tape & stored in a Data Safe. No standard Backup
solution.
f) Remote connectivity to LAN Broad Band DIAS system. Please refer the Network Diagram in
figure-5


g) Existing Fiber Optic cable length 2.8 Km shall be used in the proposed solution.
h) Existing internal network (access layer) within Service Building, Control room shall be used in the
proposed solution.
i) Attendance Punching System 8 No of Keltron make Integrated Data Capture Units.

Figure 05: Network layout across plant (existing)


MS Exchange Mail
Server
Ramco e-Application
server
Attendance &MIS
Server
Document Server
Internet &Mail
Gateway
Proxy Server &Mail
(Sendmail) Server
Broad Band Direct
Internet Access System
Internet
Router(CISCO 2600)
VSAT Terminal
Controll Room
Time Office for Central Store
3rd Floor
2
nd
Floor
4
th
Floor
Switch
To Remote Locations
Ramco Backup Server
VSAT Antenna at Roof Top
Testing Terminal
UTP Link
Fiber Link
Telephone Line
Fiber
Converter
Fiber
Converter
Coaxial Cable
(A)
(B)
(C)
(D)
(E)
(F)
Reliance Antena &ODU
Reliance IDU
Reliance Router
Reliance Connectivity(1 MBPS Internet &512Kbps MPLS VPN
connectivity to HO ) under implementation

Figure 06: Network layout within Server Room (existing)

2. Internet Connecti vity
a) Through 64 Kbps VSAT Connectivity. Recently installed 1Mbps Direct Internet Access from
Reliance.
b) Connectivity to Corporate Office. Recently installed 512Kbps MPLS VPN connectivity to connect
ITPS with Corporate Office.


D. Existing IT Infrastructure at Head Office (HO)
1. Hardware
a) For details of No PC & Laptops please refer Appendix A2: Business Processes Requirement-
Overview- Expected Number of Users
b) Local Area Network Cat-5 Ethernet Networking.
c) No of Ethernet Switches 2. (D-Link)
d) Total No of Servers 1 (Intel PIII Compaq make used as Internet Proxy Server)
e) Fortuna make employee ID proximity reader for attendance recording.
2. Software
a) Client Operating System Windows Vista, Windows XP, Windows 98
b) Other client software MS Office 2000, MS Project 2003
3. Internet Connecti vity
a) 1 Mbps BSNL Broadband Connectivity.
E. OPGC Web Site
Official website www.opgc.co.in was hosted by M/S Alloy Soft Solutions, Bhubaneswar. It has all information
regarding the location, Monthly/Yearly performance, achievements, Tender notices, financial information etc. The
Website is actively used for Tender (Work/Purchase) publication.


Appendix-A2: Business Processes Requirement-Overview
A. Business process overview
OPGC is engaged in the business of generating power from coal. It was incorporated as a fully owned subsidiary
of Govt. of Orissa in 1984, registered under the Companies Act 1956 and went into commercial operation with
2x210 MW generation units (Units 1&2) in 1996. 49% of OPGC was divested in 1999 in favour AES Corporation,
USA, with a mandated to take over the day-to-day management of the company. OPGC has been in operation
since commissioning and has been improving on its performance consistently. OPGC has been a profit making
company and has been consistently paying dividends to its share holders.
1. Business locations
OPGC has two primary business locations. The head office is at Bhubaneshwar, the capital city of the State of
Orissa. Bhubaneshwar is connected to most of the major cities in India through roads, railway and air. The plant is
located at Ib Valley, in J harsuguda District, which is over 400 kms from Bhubaneshwar. J harsuguda is well
connected to Bhubaneshwar through roads and railways.
As part of the expansion plans of OPGC, it has acquired captive coal mines located at a distance of @ 55 kms
from the plant site. In the process of developing and operating the mines, OPGC shall also be creating office and
other infrastructure set up close to the mine location, which is expected in a span of next two to three years.
OPGC also has seven mini-micro hydel projects spread out at various locations, with a total generation capacity
of 5.4 MW. In the instant case, OPGC is not considering extending the IT solutions to these areas.
2. Functional areas of the company
Head office
The head office has @ 150 employees. The primary functions managed at the head office comprise of HR,
Finance, projects and corporate affairs.
HR at head office mostly looks at managing the payroll of the employees at head office and other employee
related information. At organization level, it maintains the employee data base, looks at transfers, issues policy
guidelines and manages new initiatives for employee development.
FINANCE function deals with cash bank, investment of surplus funds, insurance, accounts receivable, managing
head office expenses, audits, taxation, treasury and preparation of financial statements and budgets.
PROJ ECTS looks after business development initiatives and co-ordinates all aspects of the expansion projects,
mostly looking at permits and clearances and appointment and management of consultants.
CORPORATE AFFAIRS looks after the corporate communication, managing media and brand imaging of OPGC
through advertisements, sponsorships and events. This functionality is also responsible for handling reporting to
various Govt. departments and responding to the queries of State and Central Govt. bodies.
Ib Thermal Power Station (ITPS), Banharpalli, Jharsuguda
The plant site has @ 400 employees. The functional departments operational within ITPS comprise of,
Coal transportation: OPGC has a coal requirement of slightly over eight (8) tons per day. It gets coal from
Lakhanpur mines of Mahanadi Coal Fields Ltd.(MCL), a subsidiary of Coal India Ltd. (CIL). The coal supply is
effected through a long term coal linkage agreement. The coal mine is 11 km from the plant and is connected


through railway Merry-go-Round system (MGR) from a railway siding at Ubuda. Both the Railway siding and the
rail network, along with the diesel engines and wagons are owned, operated and maintained by OPGC. Coal from
the mines is transported upto railway siding by MCL tippers, from where they are transported through OPGC
MGR.
Coal Handling Plant (CHP): Coal transported through the MGR are unloaded on to a track hopper from where
they are transferred through belt conveyors to the Transfer House. From the transfer house the coal is either
transferred to the crusher house or stacking yard based on whether coal needs to be fed directly to the plant or
stored.
Water Treatment Plant (WTP): Water for the plant is drawn from the Hirakud Reservoir, through an intake
channel. Water is then processed in the WTP to make it usable in the boiler and other areas within the plant.
Operations and Efficiency: The plant operations looks after control and monitoring of the power block through
the Control Room which is situated in the generator building. Their primary function is to monitor key operating
parameters through a Distributed Control System.
Efficiency department assists Operations in collating key operational parameters, analyzing, providing corrective
inputs, monitoring equipment performance to optimize overall plant performance and generating MIS.
Maintenance & Maintenance Planning: The maintenance function is segregated into different departments
based on core area of work. These departments are Mechanical, Electrical, Control & Instrumentation and Civil.
These departments handle preventive, predictive and break down maintenance of various plant and equipment
falling within their purview.
Maintenance planning department plans and schedules all maintenance activities within the plant which are
inclusive of preventive, predictive and break down maintenance. This is done through a process of receiving work
requests and issue of work orders to respective maintenance functions. Apart from the above all annual shut
down or major overhauling schedules are planned by this department.
Ash Management: On an average around 3200 tons of ash is generated and handled every day. The bottom
ash is transferred to the ash dykes. 20% of the fly ash generated is collected through a silo and supplied to
cement manufacturing plant. Balance fly ash is transferred to the ash dyke.
Finance and accounting: This function looks after all the raising invoice for energy supplied, accounts payable,
bank and cash, payroll of employees, capital expenditure and budgeting.
Purchase and warehouse: This department caters to the requirements of the maintenance departments and are
responsible for purchase of spares, consumables, bulk non-stock items, office stationary, capital assets, storage
and inventory management.
HR and administration: This function manages the employee administration, maintenance of land records,
Rehabilitation and Relocation of land oustees, CSR, training and employee development.
Contracts: This department sources and finalises outsourced jobs like job contracts, maintenance contracts,
major civil works, consultancy etc.
Environment Health and Safety: This function prepares the EHS policies and procedures, maintains and
monitors the integrated E,H & S management system consisting of the following standards ISO 14001, OHSAS
18001 and other statutory requirements.


B. Indicative List of Non SAP Interface Requirements
Sr.
Legacy
System
Name
Purpose and High
Level Data
Description
Legacy System
Information
Direction
Frequency of Data
Transfer
1
Attendance
System at
IBTPS
Attendance Punching
data(In / Out timing)
Keltron make
WINCDCU software
with Access
database
From
IDCU(Integrated Data
Capture Units)
Every 5 minutes
2
Attendance
System at
HO
Attendance Punching
data(In / Out timing)
Fortuna make ID
Proximity System
From Proximity
Device
Every 5 minutes
3 CHP
Gross wt & Tare wt of
wagon
In excel From Weigh Bridge
As and when rake
comes
4
Energy
Management
System
Energy Consumption
by Equipments
Conzerv e-LAN
EMS system
From electrical
equipments
Continuous
5
ABB Advant
System
Displaying Field
process parameters
(generation,
Frequency etc.)
ABB Advant System
From Field
Equipments
Continuous
6
RCM
Software
Operationl
RiAssessment
through Reliability
Centered
Maintenance
Reliability Centered
Maintenance
Business Stream
Optimization Tool
from RCM Business
Stream, USA
User Data input As & when required
7 ABT System Will be implemented soon and require interface to SAP later on

C. List of Indicative Reports
1. Operation
Sr No Report Name Frequency Recipient Purpose of Report
1 Daily Morning Report Daily All TLs, Advisors and DO Plant status
2 Parameter Excursion Daily All TLs ,Advisors & DO Equipment Status.

2. Efficiency
1 Daily Generation report Daily
MD,D(O),D(F),AES
Advisor, F.M., Head
(E&E), Head(Opr)
Daily Generation, PLF, Loss of
Generation, Fuel oil status &
consumption
2 Ash utilization report Daily
MD,D(O),D(F),AES
Advisor, F.M., Head
(E&E),Head(Opr)
Quantity of Fly ash & bottom ash
used for manufacturing ash brick,
filling in low lying area & taken by
M/s Ultra tech
3
Day ahead availability
schedule
Daily SLDC
Prediction of day ahead generation
schedule
4 Coal report Daily CEA Coal consumption, received & stock


5 Coal report Daily MCL
PLF, Sp. Coal cons., No. of rake
received, % of direct feeding &
reclaiming
6 EMS report Daily Internal
Daily monitoring of equipment wise
aux consumption
7 Monthly Generation report Monthly Grid Co.
Monthly gen, PLF, Peak load,
Deemed PLF
8 Performance report Monthly
M.D.,D(O),D(F),Sr.
Manager (F)
Month wise gen, PLF, availability,
Deemed PLF, sp coal & oil cons.,
loss of generation, tripping no. &
hrs, running hrs
9 Monthly Operating report Monthly CEA
Monthly generation, export, peak
load, gen loss details & tripping
details
10
Data for incentive awards for
economic & efficient
Operation of Thermal Power
stations for the year 2008
Monthly CEA
Month wise generation, PLF, % aux
consumption (Calendar year)
11
Monthly operational data of
Thermal power stations for
Evaluating performance,
Efficiency & HR
Monthly CEA
Month wise generation, PLF, Aux
cons. Sp coal cons., GCV & heat
rate (fin year)
12
Half hourly peak generation
report
Monthly CEA,ERPC
Daily peak load (MW) & energy
meter reading (MWH)
13
Monthly operation data of
TPS for Performance award
Scheme
Monthly CEA
Month wise generation, PLF, Aux
cons. Sp coal cons., sp. Oil cons.,
coal & oil stock GCV & heat rate (fin
year)
14
Monthly secondary Fuel oil
Consumption
Monthly CEA
Monthly coal & oil consumption,
received, stock & cost of fuel
15 Efficiency report Monthly Internal
Coal pipe velocity test, fineness
test, loss on ignition test, condenser
& cooling tower, HP Heater, BFP
performance test, APH duct in-
leakage test
16 Coal analysis report Monthly Internal
Proximate analysis of coal with
station HR
17 Ash Generation data Monthly Internal
Monthly ash generation, avg ash
content & GCV
18 KPI report Monthly AES
Equivalent forced outage rate,
Equivalent availability factor, Net
plant Heat rate, Safety information,
Manpower, SPM, Sox, NOx
19 Micro GADS reporting Monthly AES
Derating & outage detail, gross
generation, net generation, GCV &
heat rate
20 Running hour report Monthly Internal Equipment wise running hour
21 Coal linkage report Quarterly CEA
Generation, Sp coal consumption,
stock building per month &
requirement
22 Trip analysis report
As & when
trip occurs
Internal
Down time, generation loss & oil
consumption per tripping & detail
analysis (dept. wise)

3. HR - Training & Development


1
Employee wise qualification
report
As and
when
required
D (O), Head (P&A), Sr.
GM (P&A), MD, All TLs
Manpower planning, record of
qualifications of human inventory
2
Employee wise skill /
competency/ potential report

Once a year
D (O), Head (P&A), Sr.
GM (P&A), MD, All TLs
Manpower planning
3
Employee wise training report
e.g. in-house trg. programmes
attended, institutional training
attended, seminar/ conf.
Attended, no. of mandays
training attended ( current
year, previous years)
Any time as
& when
required
All employees, top
management
Preparation of training calendar,
planning for imparting training to the
employees, record purpose
4
Area wise training programmes
attended by the employees
e.g. no. of persons who have
attended trg. On leadership,
positive attitude,
communication skill etc.
Any time as
& when
required
All employees, top
management
do
5
Level or grade wise (team
leaders, managers, Dy.
Managers, executives,
Supervisors, W1, W2, W3, W4,
S2, S1, SG) training
programmes attended by the
employees
Any time as
and when
required
All employees, top
management
do
6
Report with regard to training
feedback submitted e.g.
feedback submitted by the
employee who have
undergone training, by
immediate superior, by team
leader
Any time as
& when
required
D (O), All TLs, Head
(P&A), Manager (Pers)
Evaluation of effectiveness of
training programmes, planning for
training & retraining
7
Report with regard to training
need of employees received
from TLs through Performance
Appraisal System
Once a year
Preparing training calendar &
training plan
8
Report w.r.t. training budget
vs. utilization, investment on
training (current year, previous
year, as on date etc)
Any time as
& when
required
Tracking of training budget
9
Report w.r.t. training calendar
(planned vs. actual), trg.
Programmes conducted and
programmes to be conducted
As & when
required
Tracking of training programmes
10
Week wise, month wise, year
wise report on training
programmes (in-house,
institutional, seminars etc.,
Induction training on transfer,
plant visit etc.)
As & when
required
do do

4. HR - Performance Management
1
Employee wise / year wise
appraisal reports i.e. marks
Once a year
(P&A), Sr. GM (P&A)
Evaluation for promotion


2
Report showing how many
employees performance are
outstanding, very good, good,
average, below average
Once a year do
Tracking of performance of
employees and for counselling
3
Report showing areas of
improvement
As & when
required
do
Counselling and planning for
imparting training
4
Report showing the
performance target vs.
achieved of each executive
Each
quarter
do
Improving the performance of
executive in other quarters
5
Report showing performance
target of each executive
As & when
required
All executives
Making the targets transparent to
each executive
6
Report showing the names of
employees whose
performance appraisal has not
been submitted and the name
of TL who has not submitted
the Appraisal format
As & when
required
P&A Department
Tracking of receipt of Appraisal
formats
7
Report showing the difference
of opinion between Appraiser
& Appraise and remarks of
Counselor
Once a year P&A Department
Strengthening the counseling
system

5. Environment, Health & Safety
1
Inspection Test & Maintenance
report of active fire protection &
suppression system
Daily/ Monthly Fire Officer
Healthiness of Fire
Fighting system
2 J ob Safety Analysis
As & when
required
Safety Officer, Fire Officer,
Factory Manager,
Concerned Departments
Accident Prevention
3
Monitoring healthiness of Tools &
Tackles
Annually
Safety Officer, Fire Officer,
Factory Manager,
Concerned Departments
Accident Prevention
4

Environment monitoring report Monthly by 10th
State Pollution control
board
Statutory
5 Environment monitoring report Monthly
board
Statutory
6 Ash utilization report Monthly by 10th
board
Statutory
7 Ash utilization report Monthly by 10th Central electricity authority Statutory
8 Water Cess report Monthly by 5th
board
Statutory
9 Environment status report
Half yearly (by
J uly & J an)
Ministry of Environment &
Forests(MoEF)
Statutory
10 Environmental audit Statement Annually by Sept
board
Statutory
11 Ash utilization statement Annually by April
board
Statutory
12 Ash utilization statement
Half yearly by
October
Central electricity authority Statutory
13 Ash utilization statement Yearly by April Central electricity authority Statutory
13 Ash utilization compliance report Yearly by April
Forests (MoEF)
Statutory


14
Ash utilization compliance, High
Court Order
Yearly by April
Forests (MoEF)
Statutory
15 Annual Ash utilization plan Yearly by April
Forests (MoEF), Central
electricity authority, State
Pollution control board
Statutory
16 Compliance to CREP guideline Yearly by April
board
Statutory
17 Hazardous waste return Yearly by J anuary
board
Statutory
18
Return statement on used/waste
batteries
Half yearly (by
J une & Dec)
board
Statutory
19 Biomedical waste return Yearly by J anuary
board
Statutory
20 EHS News letter Monthly Internal Internal
21
AES Environmental survey report
related to EHS
Quarterly AES Other requirement
22 AES annual EHS report Yearly by J anuary AES Other requirement
23 Monthly EHS report Monthly by 5 th AES Other requirement

6. Finance
1 Trial Balance Monthly
Internal(ITPS/HO-
Finance),External-
Auditors
For preparation of accounts
2 Bank reconciliation statement Monthly
Internal-
Finance/Auditors
Reconciliation of account/audit
3 Fund requisition Weekly HO Finance Fund requisition
4 Fund utilization Weekly/Fortnightly HO Finance Fund management
5 Cash/bank position Daily Internal-Finance Monitoring
6 Budget variance-AES Monthly AES
Analysis,monitoring&controlling
expenditure
7 Budget variance-OPGC Monthly OPGC
Analysis,monitoring&controlling
expenditure
8
Pending bills status-
contractors/suppliers/others
Weekly Director (O) Monitoring/timely payment
9
Contractors bills/payment
details
As required Internal-Finance Record/accounting
10
Bank payment /DD abstract-
Contractors/suppliers
Daily Banks Payment/DD making
11

Cash /bank books Daily
Internal(ITPS/HO-
Finance),External-
Auditors ,Tax
authorities & others
For recording day to day
transactions
12 General ledger Daily
Internal(ITPS/HO-
Finance),External-
Auditors ,Tax
transactions


13 Sub-ledgers Daily
Internal(ITPS/HO-
Finance),External-
Auditors ,Tax
transactions
14 J ournal book Daily
Internal(ITPS/HO-
Finance),External-
Auditors ,Tax
transactions
15
Schedules of
receivables/payables
Monthly/Annual
Internal(ITPS/HO-
Finance),External-
Auditors ,Tax
Accounting
16 C Form utilization statement Monthly/Quarterly
Sales Tax Officer-II
Circle,Bhubaneswar(th
rough HO Finance)
Statutory
17 Entry tax statement Monthly
Sales Tax
Officer,Sambalpur-III
Circle,J harsuguda
Statutory
18 VAT statement Fortnightly
Sales Tax
Officer,Sambalpur-III
Circle,J harsuguda
Statutory
19
ITDS statement-
contractors/others
Fortnightly ITO,J harsuguda Statutory
20 Royalty statement Monthly Tehsildar,Lakhanpur Statutory
21 e_TDS returns-salary Quarterly/Annual
Income tax
deptt.(through NSDL)
Statutory
22
e_TDS returns-
contractors/others
Quarterly/Annual
Income tax
Statutory
23
e_TCS returns-
contractors/others
Quarterly/Annual
Income tax
Statutory
24 FBT statement Quarterly/Annual HO Finance Statutory
25 TDS certificate-salary Annual/as required Employees Statutory
26
TDS certificate-
contractors/others
Annual Contractors/others Statutory
27 VAT/Sales tax certificate Annual Contractors/others Statutory
28 Cost center wise salary data Monthly/Annual Internal-Finance Preparation of cost records
29
Cost center wise employee
benefits
Monthly/Annual Internal-Finance Preparation of cost records
30
Cost center wise
stores/spares consumed
31
Cost center wise
repairs/maintenance-land &
building
32
Cost center wise
repairs/maintenance-plant &
machineries
33
Cost center wise
repairs/maintenance-others
34 Coal stock register Monthly/Annual Internal-Finance Preparation of cost records
35
Chemical consumption
statement


36 Fuel consumption report Monthly/Annual Internal-Finance Preparation of cost records
37
Quantitative record of raw
material processed
38
Cost center wise issue of raw
material
39 Fixed asset addition list Monthly/Annual HO-Finance
Preparation of Fixed asset
register
40
Fixed asset/depreciation
statement-cost center wise
41
Labour utilization record-cost
center wise
42
Machine utilization record-
cost center wise
43
Quantitative statement on
power generation
44 Salary bills Monthly Internal-Finance Salary payment/accounting
45 Pay slips Monthly Employees Salary payment
46 Allowances bills Monthly Internal-Finance Payment/accounting
47 Arrear/other bills As required Internal-Finance Payment/accounting
48 Abstract/J V Monthly Internal-Finance Accounting
49 Pay bill register Monthly Internal-Finance Record purpose
50
Credit notes-PF,bank loan
recovery, others
Monthly
OPGC EPF
Trust,banks,OPGC
Ltd.
Accounting&payment
51 Debit notes-PF,others Monthly
OPGC EPF
Trust,OPGC Ltd.
Accounting&payment
52 Bank payment advices-salary Monthly
SBI/CBI/AB
Banharpali
Payment to employees
53
Bank payment advices-
allowances
Monthly
SBI/CBI/AB
Banharpali
54
Bank payment advices-
arrear/other bills
Monthly
SBI/CBI/AB
Banharpali
55
Bank payment advices-staff
claims/re-imbursements
Monthly
SBI/CBI/AB
Banharpali
56
Deduction /recovery
statements
Monthly
Banks,LIC,PLI,Union,
Association,Clubs,Ma
ndir,Cable TV, School
and others
Payment/record
57 Annual salary details Annual Employees Employee information/record
58 Other MIS reports As required Internal/External
Compliance to
management/external agencies


7. Plant Maintenance
Sr.
No.
Report Name Frequency Recipient Purpose of Report
1
Equivalent Planning Factor =
(Planned Hours worked / Total
Hours worked) * 100
As and when
required.
Maint. Planning &
Maint. Teams
Planning
2
PM : BM Ratio =[(Total PM +
PdM work orders
executed)/(Total work orders
executed) * 100] : [(Total
breakdown work orders
executed) / (Total work orders
executed) * 100]
As and when
required.
Maint. Planning &
Maint. Teams
Overall effectiveness of PM & PdM -
Result focus
3
Planned Maintenance Cost
Effectiveness: [(Total Rs. spent
on PM, PdM) / (Total Rs. spent
on routine maintenance)] * 100
As and when
required.
Maint. Planning &
Maint. Teams
Overall cost effectiveness - Result
[Planned maintenance cost
considered an investment]
This cost is inclusive of contractor
cost
4
Backlog PM work order index =
Total PM work orders that
became backlog in current
month / Total PM backlog work
orders
As and when
required.
Maint. Planning &
Maint. Teams
Planning ineffectiveness - Lagging
5
Planning Effectiveness =(PM
work orders completed as
scheduled / Total PM work
orders scheduled) * 100
As and when
required.
Maint. Planning &
Maint. Teams

6
Schedule compliance index =
Total man-hours on all
scheduled jobs / Scheduled
man-hours on all scheduled
jobs
As and when
required.
Maint. Planning &
Maint. Teams

7
Total backlog work order index
=Total work orders that
became backlog in current
month / Total backlog work
orders
As and when
required.
Maint. Planning &
Maint. Teams

8
Repeat work order rate? (To
measure any repeat work being
performed that is an indirect
indicator of quality of work
performed or engineering flaw).
As and when
required.
Maint. Planning &
Maint. Teams
To know the workmanship quality.
9
Number of schedule break in =
Number of scheduled jobs
those were rescheduled to
another day
As and when
required.
Maint. Planning &
Maint. Teams

10
Maintenance cost % =(Total
maintenance cost / Total
revenue) * 100
As and when
required.
Maint. Planning &
Maint. Teams
Maintenance Cost analysis.


8. Material & Inventory Management
Sr.
no
Report Name Frequency Recipient Purpose of Report
1
Consumption Of Consumable
Item
MIS
2 Gate Pass MIS
3 Material Transfer Note MIS
4
Min-Max Lavel Report Of
Stock Control Item
MIS
5 Owner Ship Of Material MIS
6 Return Report MIS
7
Team Wise Budget Wise
Consumption Report
MIS
8
Team Wise Consumption
Report
MIS
9
Vehicle Master Report For
(HSD,LUBRICANT)
MIS
10 Spl-Monthly Spl MIS
11 Detail Item A/C Wise Spl MIS
12 Detail Location Spl With OB MIS
13 Transaction Report-Receive MIS
14 Transaction Report-Issue MIS
15 Transaction Report-Return MIS
16
Transaction Report-
Adjustment
MIS
17
As On Stock Report Like
Physical Verification Report.
MIS
18 Detail Spl Any Date Any Time MIS
19 Non-Moving Report MIS
20 Freight Bill Detail Report MIS
21 Gate Pass Report MIS
22 Grn Check Report MIS
23 Issue Details MIS
24 No Of Grn MIS
25 No Of Receive MIS
26 Pending Inspection MIS
27
Physical Verification BY
ZONE AND WH
MIS
28
Physical Verification BY
LOCATION
MIS
29
Up Loadded Data For
Codification
MIS
30 Balance Of Po Details. MIS
31 Reject Register MIS
32 Goods Receive Note MIS
33 Item Purchase History MIS
34 Vendor Want Of Document MIS
35 Unloading Inspection Report MIS
36 Material Not Yet Inspected MIS
37 Unloading Insurance Report MIS
38
Oil Receipt Report(Unpland
Receipt)
MIS


39
Stationery Receipt&Issue
Report
MIS
40 Vendor Details MIS
41 Po Details MIS
42 Pr Details MIS
43 Inventory Details MIS
44 Pr Pending Details MIS
45 PO Receipt Details MIS
46 Tender Details MIS
47 Pr-Pr Coverage Details MIS
48 Itemwise Specification Details MIS
49 Goods Receipt Details MIS
50 PO Payment Details MIS
51 Vat Details MIS
52 Oet Details MIS
53 Mateiral Unloading Details MIS
54
Budget Code /Cost Centre
Details
MIS
55 Material Not Received Details MIS
56
Itemwise PO Long Description
Details
MIS
57 Category Wise Item Details MIS
58 Way Bill Details MIS
59 In Transit Material Details MIS
60 Insurance Coverage Details MIS
61
Reminder For Due Of
Material Against Order Details
MIS
62
Order Balance Material
Details
MIS
63 Rejection Details MIS
64 Advance Outstanding Details MIS
65 Last Price Of Item Details MIS
66 Itemwise Vendor Details MIS
67 Comparative Statement MIS

B. Expected Number of Users
1. SAP Users
The SAP Users number information is provided to facilitate planning and implementation. Following licenses will
be separately arranged by OPGC.

SAP ERP Licenses
Sr No Description of Item Unit Quantity
1 SAP ERP- Development License License 1 License
2 SAP ERP- Professional User License License 150 License
3 SAP ERP- ESS User License 400 License
4 Payroll Engine for Employees India License 550 Employees
5 RDBMS Runtime Licenses to run SAP ERP License For the above


The SAP ERP Professional User License (total 150 no) can be categorized as 124 LAN users and 26
WAN/Internet users. Similarly the SAP ERP Employee Self Service (400 nos excluding Professional Users
License). Users can be categorized as 343 LAN users and 57 WAN/ Internet users. Provision of increase in
number of users should be considered during planning, implementation. Quality Assurance (QA) Infrastructure will
be needed for conducting tests and trainings during and post implementation approximately for 30 users at any
point of time.
2. Email Users
High availability email solution and collaboration tools shall be provided for the following no of users.
Sl No Description
IB Thermal Power
Plant (ITPS)
Head Office
1 Named email account 190 60
1.1 Access from Web 190 60
1.2 Access mail from Black Berry 25 10
2 Email Quota for each named account (Avg) 200 Mb 200 Mb
3. PC/ Laptop Users
All the PCs/Laptops will be controlled by Domain Controller, DHCP and DNS. The break up would be as follows

System Users

IB Thermal Power Plant (ITPS) Head Office (HO)
PC Laptop PC Laptop
Old 144 21 26 17
New 50 Nil 10 Nil

The New PCs mentioned above has to be supplied by the bidders. The final schedule for supply of PCs shall be
given by OPGC.
4. Network Printers
Old
IB Thermal Power Plant (ITPS) Head Office (HO)
Laser Line Laser Line
1 2 1 2 1

The printers mentioned above have to be supplied by the bidders.
5. Anti virus/ Anti-Spam
Antivirus and Anti-Spam software license for the Gateways, Servers and Antivirus software license for all the new
and old PCs and Laptops
6. VPN Users
30 VPN Clients for OPGC
7. Video Conferencing
Conference room at ITPS
Conference room at HO.


Appendix-B: Bid Support Documents


Appendix-B1: Letter of Undertaking by the Bidder
PROFORMA OF LETTER OF UNDERTAKING TO BE SUBMITTED BY THE BIDDER ALONG WITH HIS
BID.
(To be executed on non-judicial stamp paper of requisite value)

Ref: Date:

To
Orissa Power Generation Corporation Ltd.,
IB Thermal Power Station,
Banharpali.

(Hereinafter referred to as the Owner)

I/We have read and examined the Bid documents relating to Implementation of SAP ERP, Non-SAP
Applications and related IT Infrastructure along with Post-Implementation support with Facility Management at
OPGC.
I/We hereby tender for execution of the works referred to in the aforesaid documents upon the terms and
conditions contained or referred to therein and in accordance in all respects with the specifications, designs,
drawings and other relevant details contained in Schedule of Quantities / Price schedule attached with the Bid
documents and the period (s) of completion as stipulated in the Contract.
In consideration of I/We being invited to Bid, I/We agree to keep the Bid open for acceptance for 180 days
from the due date of opening of bid there of and not to make any modifications in its terms and conditions which
are not acceptable to the Owner.
A sum of Rs is hereby forwarded in shape of Demand Draft drawn in favour of Orissa
Power Generation Corporation Ltd. and payable at State Bank of India (Code-9510) / Andhra Bank (Code-0662) /
Central Bank of India (Code-Belpah) or Bank Guarantee issued by a ______________Bank as Earnest Money in
the manner prescribed in NIT enclosed. If I/We fail to keep the Bid open as aforesaid or make any modifications in
the terms and conditions of the Bid, which are not acceptable to the Owner, I/We agree that the Owner shall,
without prejudice to any other remedy, be at liberty to forfeit the said earnest money absolutely. Should this Bid be
accepted, I/We hereby agree to abide by and fulfil all the terms, conditions and provisions of the aforesaid
documents.
If, after the Bid is accepted, I/We fail to commence the execution of the works as provided in the
conditions, I/We agree that the Owner shall without prejudice to any other right or remedy be at liberty to forfeit
the said earnest money absolutely.


Signature of Bidder

Duly authorized to sign the Bid on behalf
of the (in block capitals)..
..
Dated
Postal Address.
Telegraphic Address
Telephone No..
Fax No.
E-mail address

Witness..

Date..

Address


Appendix-B2: Form for Price Bid
Having examined the Bid Document Number ... dated , the receipt of
which is hereby acknowledged, we, the undersigned, offer to supply, implement, commission, integrate and put
into operation the Solution under the above-named Bid in full conformity with the Bidding Documents for the sum
quoted in price schedule. The following is the total bid price for the scope of work described in our response to
your Bid Document.

i) In figures __________________________________________

ii) In words __________________________________________

(Please quote the price in Indian Rupees only)

The break-up of the above lump sum price is given in the Price schedule attached herewith and is made part of
this bid.

Thanking you,
Yours faithfully,

<Seal and Signature of Authorized Signatory>
<Name of Authorized Signatory>
<Title of Authorized Signatory>

Note: In case of bid by a consortium, this form has to be signed by authorised signatories of all the
members of the consortium.


A. Price Schedule for Project

2.1 Supply of Hardware & Non-SAP Software

SN Description UOM Qty.
FOR Unit
Rate in
INR
exclusi ve
of Taxes
& Duties
Amount
in INR
Taxes &
Duties
in INR
Taxes &
Duties in
INR
Taxes &
Duties
in INR
Total
Amount
in INR
1 UPS
2 Precision Air Conditioning System (PAC)
3 Fire Suppression Systems
4 Access Control Equipments
5 Water Leak & Rodent Control Systems
6 Civil work components (give break-up)
7 Electrical Components
8 Security system including CCTV, LCD,
Biometric reader, proximity control.

9 EMS / BMS Equipments
10 Data Safe
11 Any other
1 Servers
2 Rack with KVM
3 SAN Storage
4 Backup Devices
5
Other Hardware (PCs with OS / Printers
etc.)

6 Any Other
2.1.3 Supply Hardware - Networking Components
1 Switches
2 Routers
3 Firewall / IPS
4 Modem
5 Fiber Optic Cable
6 UTP cable
7 Connectors
8 NMS
9 Network bandwidth cost
10 Any other item (give detailed break-up)
2.1.4 Supply Hardware - Video Conferencing Equipments
1 Video Conferencing Equipments(give


detailed break-up)
2.1.5 Supply Hardware IP Telephony Equipments
1
IP Telephony Equipments (give detailed
break-up)

2.1.6 Supply of Non-SAP Software Messaging & Collaboration System
1 Mailing Software
2 Blackberry enterprise software
2.1.7 Supply of Non-SAP Software Anti virus / AntiSpam / Content Filtering
1 Antivirus / Anti Spam / Content Filtering
(give detailed break-up)

2.1.8 Supply of Non-SAP Software NMS/EMS/Service Desk Tools
1 NMS/EMS Software & Service Desk Tools

2 Backup Software
2.1.9 Supply of Non-SAP Software BMS
1 BMS Software
2.1.10 Supply of Non-SAP Software Video conferencing System
1 Video Conferencing Software
1 IP telephony Software
1 Server Operating System
2 PC Operating System
3 Any Other Software (give detailed break-
up)

2.2 Design, installation & commissioning of Infrastructure

FOR Unit
Rate in
INR
exclusi ve
of Taxes
& Duties
Amount
in INR
Taxes &
Duties in
INR
Taxes &
Duties
in INR
Taxes &
Duties
in INR
Total
Amount
in INR
2.2.1 Design, installation & commissioning of Data Center
1 Design and Engineering Charges
2 Installation and commissioning charges
(including Civil & Electrical works)

2.2.2 installation & commissioning of Hardware
1 Installation and commissioning of
Hardware

2.2.3 installation & commissioning of Networking Components
2 Installation, commissioning of Network
services

3 Establish Connectivity
2.2.4 installation & commissioning of Video Conferencing System
1 Installation, commissioning of Video


Conferencing System (give detailed break-
up)
2.2.5 installation & commissioning of IP Telephony System
1 Installation, commissioning of IP Telephony
System (give detailed break-up)

2.3 Implementation of SAP Application
FOR Unit
Rate in
INR
exclusi ve
of Taxes
& Duties
Amount
in INR
Taxes &
Duties in
INR
Taxes &
Duties
in INR
Taxes &
Duties
in INR
Total
Amount
in INR
1 SAP Implementation as per scope
including 6 months post go live stabilization
support

2.4 Implementation of Non-SAP Applications
FOR Unit
Rate in
INR
exclusi ve
of Taxes
& Duties
Amount
in INR
Taxes &
Duties in
INR
Taxes &
Duties
in INR
Taxes &
Duties
in INR
Total
Amount
in INR
2.4.1 Active Directory Implementation with SOS
2.4.2 Messaging & Collaboration Solution with
Black Berry Integration

2.4.3 Anti Virus/Anti Spam/Content Filtering
2.4.4 EMS/NMS
2.4.5 BMS for Data Center
2.5 Project Management in different phases, Change Management & Training
FOR Unit
Rate in
INR
exclusi ve
of Taxes
& Duties
Amount
in INR
Taxes &
Duties in
INR
Taxes &
Duties
in INR
Taxes &
Duties
in INR
Total
Amount
in INR
1 Project Management
2 Change management & Training on all the
above services (with breakup)


B. Price schedule for Post Implementation Support Services
2.6 Post Implementation support services for running all the SAP Application, Non-SAP
applications and Infrastructure Facility Management Services.

FOR Unit
Rate in
INR
exclusi ve
of Taxes
& Duties
Amount
in INR
Taxes &
Duties in
INR
Taxes &
Duties
in INR
Taxes &
Duties
in INR
Total
Amount
in INR
2.6.1 SAP application support
1 SAP Application Support
1 Active Directory administration
2 Messaging & collaboration, Blackberry apps
administration

3 Security Solution(Antivirus/Firewall IPS/Anti
Spam / Content Filtering application
administration

4 Video Conferencing & IP Telephony solution
administration

5 EMS/NMS/BMS application administration
2.6.3 Infrastructure and facility management
1 Help Desk
2 Desktop/Laptop
3 SAP App, database Servers
4 Non SAP and other servers
5 Router
6 Switch - L3
7 Firewall and other security equipments
8 Database
9 Leased Line and MPLS Links
2.6.4 Hardware and Network Equipment Maintenance
1 Maintenance Support within warranty
2 Maintenance Support after warranty
including parts


Appendix-B3: Exclusions / Deviations Statement

DEVIATION / EXCLUSION / VARIATION STATEMENT

We confirm that the following are the only deviations / exclusions / variations to the requirements described in
your Bid Document Number ..dated .and as responded in our proposal / bid Number .
dated . Except for these deviations / exclusions / variations, we confirm to all the other requirements of the
said Bid Document.

Sr.
No.
Page no.
of Bid
Document
Serial no.
of Bid
Document
Subject Deviation / Exclusion / Variation

We declare that any other deviations noted in other places in the bid documents / correspondences shall be
ignored and construed as our unconditional acceptance of the respective tender terms, unless mutually agreed
under seal and signature from both sides.

Thanking you,
Yours faithfully

Name and Designation of Signatory:
Name of Firm:
Address

Notes:
a) This form has to be signed by authorised signatories of the Bidder.
b) Please use separate sheets in case the deviation / exclusion / variation that cannot be adequately described
in the table above clearly mentioning the reasons).
c) The Bidders must comply with all requirements of this Bid Document. However, where the Bidder is unable to
comply with specific requirements listed out in this document, he must specifically indicate these in the format
given above. Anything contained in this Bid Document, which has not been specifically excluded, or for which
deviations have not been indicated, will be regarded as being agreed to by the Bidder.


Appendix-B4: Proforma for Bank Guarantee for Bid Security
(Earnest Money Deposit)

PROFORMA BANK GUARANTEE IN LIEU OF DD FOR EARNEST MONEY
(on Non Judicial stamp paper of appropriate value)
(Applicable to Bid value more than Rs. 25 lakh only)

Ref: Date:
Bank Guarantee No.

To
Ib Thermal Power Station,
At/Po- Banharpali,
Dist-Jharsuguda-768234.

Dear Sir,

In consideration of Orissa Power Generation Corporation having its Registered office at 7th.Floor, Zone A,
Fortune Towers, Chandrasekharpur, Bhubaneswar-751 023 (hereinafter called the Owner which expression
shall unless repugnant to the subject or context include its successors and assigns) having issued Bid
Specification Against NIT No_________________________________________ dt.________________ to
M/s________________________________________ having its Registered / Head office
at_________________________________________ (hereinafter called the Bidder) who wishes to participate in
the said tender for and you, as a special favour, have agreed to accept an irrevocable and unconditional Bank Bid
Guarantee for an amount of Rs.________________________________ valid up to ___________________ On
behalf of the Bidder, as a condition for participation in the said tender.

We, the _____________________ Bank incorporated under ________________ law and having one of our
branches at _________________ and having our Registered office/Head office at _________________ do here
by unconditionally and irrevocably guarantee and under take to pay to the Owner immediately on demand
without any demur reservation, protest, contest and recourse to the extent of the said sum of Rs._____________
(Rupees _______________________ only). Any such claim/demand made by the said Owner on us shall be
conclusive and binding on us irrespective of any dispute or differences raised by the Bidder.


This guarantee shall be irrevocable and shall remain valid up to _________________. If any further extension of
this guarantee is required, the same shall be extended to such required period on receiving instructions from M/s
____________________ on whose behalf this guarantee is issued.

We, the said Bank lastly undertake not to revoke this guarantee during its currency except with the previous
consent of the Owner in writing and agree that any change in the constitution of the said tenderer or the said Bank
shall not discharge our liability. In witness where of the Bank, through its authorised officer, has set its hand and
stamp on this ___________________________ day of _______________________20______

Witness:

(Signature) (Signature)

____________________ __________________
Name Name

_____________________ (Designation with Bank stamp)
Official Address

Attorney as per Power of Attorney

No.___________________

Date__________________


Appendix-B5: Consortium MOU

Date:

To
--------------------------------------
--------------------------------------
--------------------------------------

Dear Sir,

Sub: Notice of Intent to Respond to Bid Document
(Bid Document Number ; dated ..)

We are a consortium with the following members:
a) Company Name & Address
b) Company Name & Address
c) Company Name & Address

Having examined the Bid Document we, hereby confirm our intention to collectively respond to the described Bid
Document floated by your company as members of the above consortium. by submitting a consolidated Bid
number .. dated .. offering to supply, install, test, pre-commission, commission, demonstrate and
establish performance guarantee parameters of the solution in full conformity with the said bidding documents.

<Company Name> will be the Lead Bidder of our consortium. They are authorized to sign all contract documents,
receive instructions and incur liabilities on behalf of the consortium. A notarized copy of the duly executed
Consortium Agreement to this effect is enclosed.

We hereby confirm that <Company Name>, the Lead Bidder, will responsible for execution of the contract in such
a manner that the Solution delivered meets the performance requirements as described in the Bid.

We hereby confirm that information provided in this Bid is true and correct to the best of our knowledge and belief
and nothing has been concealed, misrepresented, manipulated or exaggerated there from.


Details of primary and secondary contact persons for each consortium member are as follows:

We undertake, if our bid is accepted, to commence execution of work of the Solution and to achieve completion
within the respective times stated in the bidding documents / quoted by us in our bid.

We understand that you are not bound to accept the lowest or any bid you may receive and in-turn we will not
have any rights to raise any claim, whatsoever it may be, due to or arising out of rejection of our bids.

Thanking you,

Yours faithfully,

<Seal and Signature of Authorized Signatory>
<Name of Authorized Signatory>
<Title of Authorized Signatory>

Note: This form has to be signed by authorised signatories of all the members of the consortium
<Company Name & Address>
<Brief Description of Companys Key Role on the Project>
Primary Secondary
Name
Designation
Company Name
Address
Phone
Fax
Email id


Appendix-B6: Profile of Implementation Partner
A. Organisation details
A. Background Information
Name of the Implementation Partner
Registered Office Address
Contact Person with contact details
B. Financials
Financial Year ( 1
st
April 31
st
March ) Turnover
(INR Crores)
Profit
( INR Crores)
ERP Business
(INR Crores)
2007-2008
2006-2007
2005-2006
C. Employee Strength
Total No of Employees
Total No of Employees in SAP Practice
Total No of Employees in Infrastructure Practice
Total No of SAP Functional Consultant
Total No of SAP Technical Consultant
Total No of SAP Certified Consultants in the area:
a) Materials Management
b) Finance and Controlling
c) Human Resource
d) Project Systems
e) Plant Maintainence
f) XI & Netweaver
g) BASIS
h) ABAP
i) XMII
j) EH&S
List the Quality Certification like CMM Level V, ISO
etc

Provide details on SAP CoE established
Provide details on SAP Helpdesk

Note: Please use additional sheets wherever required. Please ensure proper reference between the table
row and the additional sheet used.


B. Global SAP Delivery Experience
Customer No 1
Name of the Customer

(For reference only)

Brief about the Organisation

SAP Modules Implemented
Industry Vertical
Name of the Project Manager from IP
Type of Engagement with the Customer New Implementation / Upgrade / Support / Custom Development
Present Implementation Stage Business Blueprint/ Realisation /Go-live / Support
No of SAP Users
Please provide a brief remarks on the below mentioned questionnaire
Sl Question Remark
1 What was the role in the implementation Prime Bidder/ Partner / staff Augmentation/ Training
2 Does the Implementation involve SAP
Integration with other products like Outlook,
Lotus Notes etc.

3 Does the Implementation involve usage of
New Dimension products Like XMII, CPM,
SEM, GRC etc

4 Does the Implementation also involve Post Go
live support by your organization

5 Was the project delivered on time agreed upon
initially? If No, Please state the reasons for the
same.

6 What was the Value of the Contract?
7 Does the Contract also include the creation of
infrastructure and Training?

8 Date of Contract Signature and Go Live dates
9 What is the Hardware Platform used in the
Project?

10 Did the customer involve SAP Consulting or
any third Party Organisation for Audit of the
implementation?



C. Indian SAP Delivery Experience
Customer No 1


Industry Vertical
Type of Engagement with the Customer New Implementation / Upgrade / Support / Custom Development
Present Implementation Stage Business Blueprint/ Realisation /Go-live / Support
No of SAP Users
Sl Question Remark
1 What was the role in the implementation Prime Bidder/ Partner / staff Augmentation/ Training
2 Does the Implementation involve SAP
Integration with other products like Outlook,
Lotus Notes etc.

3 Does the Implementation involve usage of
New Dimension products Like XMII, CPM,
SEM, GRC etc


same.

7 Does the Contract also include the creation of
infrastructure and Training?

Project?

10 Did the customer involve SAP Consulting or
any third Party Organisation for Audit of the
implementation?



D. SAP Delivery Experience in Utilities
Customer No 1



Utilities value Chain Generation /Distribution /Transmission /Trading

Modules implemented
Please include couple of workflow diagram for
Power Generation Business

Sl Question Remark
1 What was the total timeframe for the
implementation at the Power Plant?

2 Was the power Plant Thermal/Hydel/Nuclear?
3 Did the implementation also include machine
Level integration with MES, SCADA etc.

4 Please provide any ROI case study for the
Customer with relationship to SAP
Implementation

5 Can we contact your customer over
phone/email or any other means of
communication for reference and understand
the finer elements of the implementation?


E. System Integration Capability
Customer No 1


Industry Vertical
Scope of Implementation LAN / WAN/ Hybrid
OEM Suppliers
No of Users
Sl Question Remark
Project?


same.

F. Implementation Team
Employee No 1
Name of the Employee
Designation of the Employee
Contact details
Industry Vertical
Educational Background
Proposed Role in the OPGC Project team
Certifications

The Implementation Partner has to deploy a specialized and trained team for the successful and timely
completion of the Project. It is therefore desirable that the key personnel in the team have the following minimum
work experience.


a) Project Manager: Two (2) SAP implementation cycle experiences which includes Implementation experience
in an integrated Utility plant
b) Change Management Lead: One (1) project experience in SAP led Change management.
c) Functional Integration Lead: One (1) SAP implementation cycle experience on different modules of the
offered product suite which includes implementation experience in an Integrated Utility Plant.
d) Functional Leads: One (1) SAP implementation cycle experience on the offered product suite which includes
India localization experience in the relevant modules.
e) Technical Leads Interfaces: Minimum One(1) SAP implementation cycle experience for the offered
product which includes experience with implementing interfaces to Oracle based legacy applications.
f) Technical Leads Database Management: Minimum One (1) full cycle experience with the same SAP
product suite and localization requirements.
G. IT Support & Facility Management Services Capability
Customer No 1


Scope of IT service support / Facility Management
service offered

Industry Vertical
Name of the Vendor representative
Period of Service & value of FMS Contract
No of Users
Sl Question Remark
1 The Bidder should be certified for IT service
management system standard BS 15000 / ISO
20000.

2 The Bidder should be certified for Information
Security Management System Standard BS
7799 part 2 Or ISO/IEC 27001

3 ISO 9001:2000 standard/certified process
framework and FMS division

4 The Bidder should have an ITIL framework or
any other globally recognised framework for
delivery of services.


Appendix-B7: Profile of Hardware Partner

A. Background Information
Name
Head Office Address
Contact Person
Countries with offices
Net worth as at the end of last three Financial Years
internationally for Hardware business (Please attach certified
annual reports)

Annual revenue in the last three Financial Years internationally
for Hardware business (Please attach certified annual reports)

Countries where SAP has been installed on the hardware
B. Indian Operations
Head of Indian Operations
Indian Head Office Address
Contact Person
Contact Number
Email id
Number of offices
Net worth as at the end of last three Financial Years in India
for Hardware business (Please attach certified annual reports)

Annual revenue in the last three Financial Years in India for
Hardware business (Please attach certified annual reports)

Number of employees
a) Support Related
b) Others
Details of Accreditations such as ISO 9001, etc.
Alliances
C. Proposed Infrastructure
Infrastructure Elements e.g. Hardware (server, storage, SAN,
backup), UPS, Generator, Precision Air Conditioning System,
Access Control System, Fire Detection and Suppression
System, etc.

Configuration in brief
Other Details in brief
(Please give above information for each Infrastructure
element)



Appendix-C: Contract Document


AGREEMENT FOR IMPLEMENTATION OF SAP ERP, NON-SAP APPLICATIONS AND RELATED IT
INFRASTRUCTURE ALONG WITH POST IMPLEMENTATION SUPPORT WITH FACILITY MANAGEMENT.

Agreement No:

Made on this day of

Between

M/s Orissa Power Generation Corporation Limited, a company incorporated under Companies Act. 1956 having
its registered office at Zone-A, 7
th
Floor, Fortune Towers, Gangadhar Meher Marg, Chandrasekharpur,
Bhubaneswar- 751023, hereinafter referred to as the Owner (which expression shall unless repugnant to the
context or meaning thereof include its administrators, successors, executors and assigns)

On the one part

And

M/s

hereinafter referred to as the Vendor ( which expression shall unless repugnant to the context or meaning
thereof include its administrators, successors, executors and assigns)

On the other part

WHEREAS the Owner is desirous of executing the work comprising of supply of hardware and non-SAP software,
design, installation & commissioning of infrastructure, implementation of SAP application, implementation of non-
SAP applications, project management, change management and training (hereinafter referred to as the
Project ).

AND WHEREAS the Owner is desirous of availing the post implementation support services for running the SAP
application, non-SAP applications, the infrastructure facility management services (hereinafter referred to as the
FMS)

AND WHEREAS the Owner has invited two part bids through open tender vide NIT No -ITPS/CC-22/2008/68
Dated - 03.09.2008 for both the Project and FMS (hereinafter referred to as the IT Solution)

AND WHEREAS the Vendor has submitted his offer vide No________dated______.

AND WHEREAS the Owner after evaluating the said offer and negotiating with the Vendor entered into this
agreement on terms and conditions more specifically contained in this agreement and the documents &
correspondences referred to therein which have been unequivocally accepted by the Vendor resulting into a
concluding agreement, hereinafter referred to as the Agreement.

Witnesseth that


1 Definitions & Interpretations

1.1 Definitions

The following words and expressions shall have the meanings hereby assigned to them except where the context
otherwise requires.

Agreement shall have the same meaning as ascribed to it in the cover page of the Agreement.

Approval of the Owner shall mean the written approval to a document, a drawing or other particulars of matters
in relation to the Agreement by the Owner or his authorized representative.

Contract Price means the price payable to the Vendor under the Agreement as per Annexure-4 for the full and
proper performance of its contractual obligations.

Core SAP Product means the standard features provided by the modules of the SAP ERP application.

Delivery shall have the same meaning as ascribed to it in the Annexure-1 & Annexure-2 of Appendix-C.

Day means calendar day of the Gregorian calendar consisting of 24 hours from midnight to midnight irrespective
of the number of hours worked in that day.

Effective date shall mean the date of signing the Agreement.

FMS shall have the same meaning as ascribed to it in the cover page of the Agreement.

Final Acceptance shall have the same meaning as ascribed to it in the clause-9.6.

Go-live shall have the same meaning as ascribed to it in the clause-9.5.1(a).

Go-live Acceptance shall have the same meaning as ascribed to it in the clause-9.5.1.

Hardware Manufacturer means the original manufacturer of hardware based in India or its Indian office in case
the manufacturer is located outside INDIA.

IT Solution shall have the same meaning as ascribed to it in the cover page of the Agreement.

Intellectual Property Rights means any and all copyright, moral rights, trademark, patent, and other intellectual
and proprietary rights, title and interests worldwide, whether vested, contingent or future including without
limitation all economic rights and all exclusive rights to reproduce, fix, adapt, modify, translate, create derivative
works from, extract or re-utilize data from, manufacture, introduce into circulation, publish, distribute, sell, license,
sublicense, transfer, rent, lease, transmit or provide access electronically, broadcast, display, enter into computer
memory, or otherwise use any portion or copy, in whole or in part, in any form, directly or indirectly, or to authorize
or assign others to do so.

Infrastructure shall have the same meaning as ascribed to it in the clause-9.2

Materials means all the deliverables to be provided to Owner under the Agreement.

Month means calendar month of the Gregorian calendar.

Owner shall have the same meaning as ascribed to it in the cover page of the Agreement.


Offices shall mean corporate office, regional offices, branch offices and locations wherever business activities are
conducted by the Owner.

Project shall have the same meaning as ascribed to it in the cover page of the Agreement.

Project Manager shall have the same meaning as ascribed to it in clause-4.1.1.

Project Plan shall have the same meaning as ascribed to it in clause-5.1.1

Project Site shall mean Ib Thermal Power Station, Banharpalli, J harsuguda.

Scope shall have the same meaning as ascribed in clause 2 of the Agreement.

Services means all technical, logistics, management, and any other services to be provided by the Vendor under
the Agreement to develop, install, implement, customize, integrate, and make operational the IT Solution. Such
services may include, but are not restricted to installation, commissioning, Go-live, testing, stabilization and
Training.

Stabilization Acceptance shall have the same meaning as ascribed to it in clause-9.5.2.

System means any hardware component, software component, application component, developed application or
module of the SAP proposed to meet the technical requirements that may be supplied, installed, tested, and
commissioned individually.

Sub-contractor shall have the same meaning as ascribed to it in clause-8.2.

Tests shall have the same meaning as ascribed to it in clause-9.

Test Plan shall have the same meaning as ascribed to it in clause-9.1

Term of Agreement shall have the same meaning as ascribed to it in clause-18.1

Vendor shall have the same meaning as ascribed to it in the cover page of the Agreement.

Week means seven (7) consecutive Days, beginning the said day of the week

Year means a period of twelve (12) consecutive Months.

1.2 Interpretation

1.2.1 Language: The Agreement shall be construed and interpreted in accordance with the English language.

1.2.2 Headings: The headings are included for ease of reference and shall neither constitute a part of the
Agreement nor affect its interpretation.

1.2.3 Party or Parties: The Owner and the Vendor shall be individually referred to as Party and collectively
as Parties.

1.2.4 Persons: Words importing persons shall include firms, companies, corporations, associations or body of
individuals whether incorporated or not. Words importing masculine gender or singular number shall also
include the feminine gender and plural number and vice-versa where the Agreement so requires or
permits.


1.2.5 Entire Agreement: The Agreement constitutes the entire Agreement between Owner and Vendor with
respect to the IT Solution and supersedes all communications, negotiations, and Agreements (whether
written or oral) between the Parties with respect to the IT Solution made prior to the date of Agreement.

2 Scope of Agreement
The Scope of Agreement covers work to be executed as indicated in the detail scope of work at Annexure -1
along with the supporting information provided under Annexure 2 to Annexure 7.

a) Unless otherwise expressly limited, the Vendors obligations involve supply of necessary software, requisite
hardware, network hardware and services, product, implementation, integration, testing, acceptance,
achieving go-live, training, change management, stabilization of the Project, provision of all the Project
components and materials as well as performance of all Services, as tendered in this document & in
accordance with the plans, procedures, specifications, and any other documents specified in the Agreement
and the Project Plan, at no additional cost.
b) The Vendor shall, unless specifically excluded in the Agreement, perform all such work and / or supply all
such items, service materials not specifically mentioned in the Agreement but that can be reasonably inferred
from the Agreement as being required for attaining Go-live Acceptance and stabilization acceptance of the
Project as if such work and / or items and Materials were expressly mentioned in the Agreement, at no
additional cost.
3 Obligation of Vendor
3.1 Obligation of Vendor towards the Project
3.1.1 The Vendor has the overall responsibility of implementing, conducting Tests, successful running and
stabilization of the Project.
3.1.2 The Vendor shall be responsible for timely provision of all resources, information, and decision making
under its control that are necessary to reach a mutually accepted Project Plan as per Annexure-3 and the
detailed Scope of work at Annexure 1.
3.1.3 The Vendor shall appoint its representative within fourteen (14) days of signing of the Agreement after
mutual discussions and written approval of Owner. The request must be accompanied by a detailed CV
for the nominee, as well as a description of any responsibility other than Project responsibilities the
nominee would retain while performing the duties as the Vendors representative. The Vendors
representative shall have the authority to represent the Vendor on all day-to-day matters relating to the
Project.
3.1.4 The Vendor shall provide the key personnel namely the project leader, module leaders, quality assurance
personnel any specialist / analysts required as appropriate, and having sufficient experience in terms of
relevance and number of years required to implement the Project. Should the profile of any personnel not
be acceptable to Owner, Owner will require the Vendor to suitably replace such personnel. The key
personnel are to be assigned to the project on full time basis and to the satisfaction of Owner. If for any
reason beyond the control of the Vendor, there arises a need to replace any personnel, the Vendor shall
provide a replacement person of equivalent or better qualification and experience, subject to the written
approval of Owner. Further, at any time in the opinion of the Project Manager, any additional, qualified,
experienced engineer is considered necessary; they shall be deployed by the Vendor without any
additional charge. The Vendor shall ensure to the satisfaction of the Project Manager competent and
efficient supervision in the Implementation of the Project.
3.1.5 In case project gets delayed due to any reason attributed to Vendor, the annual technical support /
maintenance up to the stabilization acceptance of the project shall remain in the scope of the Vendor with
no financial implication on Owner.
3.2 Obligation of Vendor towards the FMS


3.2.1 The vendor has overall responsibility of providing post implementation support services for the successful
running of the System(s) as per the scope outlined in this Agreement and any further terms and
conditions as may be stipulated at the time of execution of the contract for FMS.
3.2.2 The vendor shall appoint a new representative after mutual discussion and written approval of the Owner
or may keep the representative of the Project as a single point contact for the FMS. For new
representative Vendor shall make the request which must be accompanied by a detailed CV for the
nominee, as well as a description of any responsibility other than FMS responsibilities. The vendors
representative shall have the authority to represent the vendor on all day-to-day matters relating to the
FMS.
3.2.3 The Vendor shall ensure that the faulty network devices, servers, PCs and peripherals etc are repaired /
brought back to service within specified resolution time. Vendors representative posted during the FMS
period will ensure that the down time for individual node does not exceed the time of failure reporting as
detailed in Annexure - 2.
3.2.4 The Vendor shall provide all the personnel required as appropriate, and having sufficient experience in
terms of relevance and number of years in providing FMS. Should the profile of any personnel be not
acceptable to Owner, the vendor is to suitably replace such personnel.
3.2.5 The Vendor shall provide the Services to meet or exceed the service levels specified in Annexure-2. The
Vendors obligation to perform the Services to meet or exceed the service levels continues despite any
increase or other variation in any Service volumes. The Vendor in consultation with the Owner shall
review the Service Levels once each year and will adjust the service levels in accordance with the change
control procedure to meet the continuous improvement objective.
3.2.6 Where the Vendor anticipates that there will be a significant delay to the performance of any of its
services for which it considers an extension of time is required, then it must immediately notify Owner of
its request, the reasons for an extension and steps taken or to be taken to minimize the delay and as
soon as practicable, notify the Owner promptly in writing of the period of the delay caused and give
details of the extension of time which it reasonably considers will be required.
3.2.7 The Vendor must, at its own cost obtain the relevant network connections (including redundant network
connections) that are required to connect from the Vendors sites to Owners.
3.2.8 The Vendor shall ensure that all technology and equipment used to perform and deliver the Services is
not obsolete and is kept in good working order at all times.
3.3 Obligation of Vendor towards the IT Solution


3.3.1 The Vendors representative and staff are obliged to work closely with Project Manager / Owners
representative and act within their own authority, and abide by directives issued by Owner that are
consistent with the terms of the Agreement. The Vendors representative is responsible for managing the
activities of its personnel.
3.3.2 In the event if any discrepancy with respect to the qualifications of the employees of the Vendor is
detected by Owner then the Vendor shall appoint a replacement to such objection immediately in
accordance with this clause.
3.3.3 The Vendors representative may, subject to the written approval of Owner (which shall not be
unreasonably withheld), at any time delegate to any person any of the powers, functions, and authorities
vested in him. Any such delegation may be revoked at any time with prior notice signed by the Vendors
representative and shall specify the powers, functions, and authorities thereby delegated or revoked. No
such delegation or revocation shall take effect unless and until a copy of such a notice has been delivered
to the Project Manager / Owners representative. Any act or exercise by any person of powers, functions
and authorities so delegated to him or her shall be deemed to be an act or exercise by the Vendors
representative.
3.3.4 The Vendor shall acquire in its name all permits, approvals, and/or licenses from all local, state, or
national government and other statutory authorities and/or public service undertakings that are necessary
for the performance of the Agreement.
3.3.5 Neither the Vendor nor its personnel shall during the term of this Agreement, engage in any business or
professional activities in India/abroad which would conflict with the activities assigned to them under this
Agreement
3.3.6 The Vendor is responsible for performing and safely storing, timely and regular backups of its data and
Software in accordance with accepted data management principles, except where such responsibility is
clearly assigned to Owner elsewhere in the Agreement.
3.3.7 Vendors Staff and their Conduct

a) If any of the Vendors employee, in the opinion of Project Manager / Owners representative, be found
guilty of any misconduct or be incompetent or insufficiently qualified or negligent in the performance
of their duties or that in the opinion of the Project Manager / Owners representative, undesirable for
administrative or any other reasons, for such person(s) to be employed for providing desired services,
then at the directions of the Project Manager / Owners representative, the Vendor shall at once
remove such person (s). Vacancy so created shall be immediately filled at the expense of the Vendor
by a qualified and competent substitute. Should the Vendor be requested to repatriate any person or
removed from this Agreement, he shall do so and shall bear all costs in connection therewith.
b) The Vendor shall be solely responsible for the proper behaviour of his employees and staff employed
by him/deputed by him to provide IT Solution. The Vendor shall exercise proper degree of control
over them and in particular without prejudice to the said generality the Vendor shall be bound to
prohibit/prevent any of his employees (as stipulated above) from trespassing or acting in anyway
detrimental or prejudicial to the interest of the community or the properties or occupiers of land or
properties in the neighbourhood. In the event of such trespassing, the Vendor shall be responsible for
all consequent claims or actions for damages or injury or any other grounds whatsoever. The decision
of the Project Manager / Owners representative upon any matter arising under this clause shall be
final.
c) If the Vendor or their employees damage, break, deface the property belonging to the Owner or
others during the execution of the Agreement, the same shall be made good by the Vendor at his own
expense and in default thereof, the Project Manager may cause the same to be made good by other
agencies and recover expenses from the Vendor for which the certificate of the Project Manager shall
be final.
d) All Vendors personnel entering Owners premises shall be properly identified by badges of a type
issued by Owner as per prevailing rules and must be worn at all times on Owners premises.
e) It is made clear that no relationship of Owner and employee is created between Owner and the
Vendors resident engineers, employees and no claim for employment of any such personnel shall be
tenable or entertained.

3.3.8 Security, Statutory and Safety Regulations


a) The Vendor shall abide by all the safety and security regulations of Owner in force and promulgated
from time to time and other statutory requirements. The Vendor shall be responsible for the safety of
all employees and/or workmen employed or engaged by them on and in connection with the work and
shall report to Owner and other local authorities concerned all cases of accidents howsoever caused
and wherever occurring on the works and shall make adequate arrangements for rendering
immediately all possible aid to the victims of the accidents. Owners safety rules & regulations, are
detailed in Annexure-7.
b) Owner shall not be in any way held responsible for any accident or damages incurred and claims
arising there from during the period of installation, testing, commissioning and stabilizing IT solution.
The Vendor shall be responsible for following the provisions of all safety laws and rules made there-
under and other statutory requirements at his own cost.
c) The Vendor shall arrange to obtain from Owner the required gate pass for entry and exit to Owners
plant site and other protected areas for each one of its engineers/specialists, representatives/ agents,
supervisors, workmen and staff as per Owners prescribed procedure and format. Each entry and exit
gate pass shall contain the photograph of the person concerned. In the event of loss and/or damage
to the gate passes, the Vendor shall pay to Owner the prescribed penalty before a new entry and exit
gate pass can be issued. Owners security department and the concerned officer/ engineer shall have
the right to refuse the entry and exit gate passes to any worker or representatives of the Vendor
without assigning any reason.
d) The Vendor shall register all equipment that may be taken inside the plant area in order to facilitate
the issue of exit gate permits for such items to be taken out after the completion of work.
e) The Vendor shall not employ for the purpose of the Work, any person below the age of 18 years.
Owner shall have the right to decide whether any person employed by the Vendor is below the age
limit, and to refuse to allow any person, whom he considers to be under-aged to be employed by the
Vendor.
f) Factories Act, 1948: The Vendor shall follow the provisions of Indian Factories Act, Contract Labour
(R&A) act 1970, workman Compensation Act 1923 and other Acts and rules made there under from
time to time as applicable, and shall indemnify Owner against all claims of compensations under the
provisions of the Act in respect of workmen employed by the Vendor in carrying out the works and
against all costs and expenses or penalties that may be incurred by Owner in connection therewith.
g) The Vendor shall submit labour license (if required).
h) The Vendor shall ensure that no explosive or inflammable material are used or stored at the Project
Site. In the event such material are essential as part of execution of the Project work, written
permission shall be sought from the Project Manager / Owners representative and it shall be the sole
responsibility of the vendor to ensure acquisition of necessary statutory permits and clearances and
proper storage and handling of such material.

3.3.9 Environmental, Health & Safety clause
The following environment, safety & health points are to be adhered:
a) The Vendor must adhere to all the applicable statutory laws pertaining to safety, health and
environment.
b) The Vendor must ensure that there is no wastage of water and power at the work site
c) All the motor vehicles of the Vendor used for transporting materials/machinery etc should have
pollution control certificates and the same should be submitted at the time of obtaining gate passes. A
copy of the same must be exhibited/pasted on the vehicle also
d) The Vendor must ensure proper house keeping at work station / site by keeping the work-areas free
from unwanted material.
e) The Vendor must ensure that any debris generated during the work is transported safely to dump
yard such that there is no spillage of debris on the road during transportation (by covering with a
plastic sheet/tarpaulin)
f) All the material which may be recycled / reused should be transported to the designated place for
reuse/recycling.


g) All supervisors/ workers of Vendor must take safety and environmental induction training and comply
with the instructions given therein.
h) The Vendor shall engage its human resources who are proven to be of good conduct and clean
antecedents.
i) Generally, it shall be the responsibility of the Vendor to complete with all the statutory enactments,
regulations, directions, notifications etc. issued by the Central and State Governments or any other
Pollution Control Authorities from time to time.
3.3.10 Employees Provident Funds and Miscellaneous Provisions Act 1952 & Employees State Insurance Act
1948
a) The Vendor shall ensure strict compliance of provisions of the Employees Provident Funds and
Miscellaneous Provisions Act 1952 and the schemes framed there under so far as they are applicable
to their establishments and agencies engaged by them. The Vendor is also required indemnifying
Owner against any loss or claims or penal damages whatsoever resulting out of non-compliance on
the part of the Vendor with the provisions of the aforesaid Act and the schemes framed there under.

b) The Vendor agrees to maintain all statutory records as required under various labour laws in respect
of employees and payments. Any expenses incurred for the contributions, making contribution or
maintaining records shall be to the Vendors account.
3.3.11 Vendor Responsibility with Other Agencies
a) Without repugnance to any other condition, it shall be the responsibility of the Vendor not to divert or
withdraw the people working for IT solution for any other service contract with Owner. No claim shall
be entertained on account of above.
b) The Vendor shall conform in all respects with the provisions of any statutory regulations, ordinances
or byelaws of any local or duly constituted authorities or public bodies which may be applicable from
time to time to the consulting services work.
3.3.12 All notices, instructions, information, and other communications given by the Vendor to Owner under the
Agreement shall be given to the Project Manager / Owners representative, except as otherwise provided
for in this Agreement.
3.3.13 The Vendor shall make its own arrangements for movement of personnel and equipment, within and
outside the sites / units / offices at the various locations covered by the Agreement.
4 Obligation of Owner
4.1 Obligation of Owner towards Project
4.1.1 Owner shall appoint a Project Manager and notify the Vendor in writing the name of the Project Manager
within fourteen (14) days of signing of the Agreement. Owner may also from time to time appoint some
other person as the Project Manager in place of the person previously so appointed and shall give a
notice of the name of such other person to the Vendor without delay. The Project Manager shall have the
authority to represent Owner on all day-to-day matters relating to the Project or arising from the
Agreement. All notices, instructions, orders, certificates, approvals, and all other communications under
the Agreement shall be given by the Project Manager, except as otherwise provided for in this
Agreement.
4.1.2 Owner shall be responsible for timely constitution of core team and provision of resources, necessary
access, and information for the installation, commissioning and Go-live of the Project as identified in the
Project Plan, except where provision of such items is explicitly identified in the Agreement as being the
responsibility of the Vendor.
4.1.3 Unless otherwise specified in the Agreement or agreed upon by the Parties, Owner shall provide
personnel, to properly carry out commissioning, Go-live (including successful running and stabilization of
the system), at or before the time specified in the Project Plan.
4.1.4 Owner will designate its appropriate staff for the training courses to be given by the Vendor and shall
endeavour to make all appropriate logistical arrangements for such training as specified in the Project
Plan.

4.2 Obligation of Owner towards FMS


4.2.1 Owner shall designate its representative responsible for the FMS. The representative so designated shall
have the authority to represent Owner on all day-to-day matters relating to the FMS.
4.2.2 Owners shall provide updated contact listing as a one-time activity for use by help desk personnel in
contacting Owners appropriate personnel for assistance/notification and shall provide an adequate level
of system authority for all hardware, software and resources for which the Vendor has problem resolution
responsibility and communications access
4.2.3 Owner shall assist the Vendor in the development of help desk operational procedures by providing input
to, and review and approval of such procedures and shall allow the Vendor to utilize remote access
capability to remotely diagnose problems if required.
4.2.4 Owner shall allow access by vendor maintenance personnel to Owners designated locations for
purposes of problem diagnosis and repair and shall provide secured storage area for Vendors spare
parts inventory.
4.3 Obligation of Owner towards IT Solution
4.3.1 Owner shall ensure the availability of all information and/or data to be supplied by Owner to the Vendor.
4.3.2 The Project Manager / Owners representative may at any time delegate/revoke to any person any of the
powers, functions, and authorities vested in him or her of which due notice in writing will be given. Failure
of the Project Manager to reject any part of the IT Solution viz., software modules, equipment, Materials,
workmanship etc., or to disapprove any service or materials shall not prejudice the Owner to reject such
software module, equipment, Materials, workmanship etc., or to disapprove such work or materials and to
order re-supply of such software module, equipment & Materials or to pull down, remove or break up such
disapproved service at the cost of the Vendor, provided the Vendor fails to comply with the direction and
requirement of the Owner there off. The decision, opinion, certificates or valuation of the Owner in respect
of any matter under this clause shall be final, binding and conclusive. If the Vendor is dissatisfied by
reason of any decision, opinion, direction, certificate or valuation of the Project Manager / Owners
representative, they shall be entitled to refer the matters to the Owner who shall thereupon confirm,
reverse or vary such matters.
4.3.3 Owner by notice to the Vendor may object to any representative or person employed by the Vendor in the
execution of the Agreement who, in the reasonable opinion of Owner, may have behaved inappropriately,
be incompetent, or be negligent. Where upon the Vendor shall remove such person from work on the
Project. If any representative or person employed by the Vendor is removed, the Vendor shall, where
required, promptly appoint a replacement.
4.3.4 Workplace/Facilities for Vendors Site Office
a) Owner shall provide the office space and other essential work facilities within its premises for the
Vendors team.
b) Suitable workspace in the respective sites/offices may be provided to the Vendor subject to the
availability, free of charge. However, providing such space and store is for the smooth execution of
Agreement and non provision of such space does not bind Owner and make Owner liable to the
Vendor in any manner except as specifically provided in the Agreement terms. Owner is not liable for
any loss or damage to the Vendors equipment/material as a result of variation in voltage or frequency
or interruption in power supply or other loss to the Vendor arising there from.
c) Owner will supply electric power 220/440V, 3 phase/single phase, 50 cycles from the nearest
established substation free of cost, for the site works and approved site offices. Only one outlet will be
provided from the point of supply.
d) Though efforts will be made by Owner to maintain regular power supply, Owner shall not be
responsible for any failure in power supply and any consequences arising there from. The Vendor
shall obtain the approval of the Project Manager / Owners representative for installation of machinery
and electric power supply connection to them. The Vendor shall be responsible for any defect therein.
Any defects pointed out by the Owner in the distribution system shall be rectified forthwith to the
satisfaction of Project Manager / Owners representative by the Vendor, failing which the power
supply may be cut off by the Owner.
4.3.5 Accommodation and Transportation
Residential accommodation will be provided by Owner to the staff of Vendor on chargeable basis.


5 Implementation Plan
5.1 Implementation Plan for Project
5.1.1 Project Plan
a) In close cooperation with Owner and based on the preliminary Project Plan included in the Vendors
bid, the Vendor shall develop a project plan hereinafter referred to as Project Plan encompassing
the activities specified in the Agreement.
b) The Vendor shall formally present to the Owner the Project Plan in accordance with the technical
requirements. The Vendor has to specify the strategy and methodology with time frame and the
synchronization of various phases of the Project to ensure completion of the Project in time. The
Project Plan shall also include a PERT chart describing the activities, resources required on the time
for completion. The Project Plan shall also bring out the critical areas needing continuous attention of
Owner.
c) The Vendor shall undertake to supply, install, implement, integrate, commission and ensure the go-
live and stabilization of the System in accordance with the Project Plant.
d) The progress and other reports specified shall be prepared by the Vendor and submitted to Owner in
the format and frequency specified in the Project Plan.
e) Changes to the Project Plan, if required, shall be made with the mutual consent of Owner and the
Vendor.
5.1.2 Design and Development
Vendor shall execute the basic and detailed design and the implementation activities necessary for
successful implementation of the Project in compliance with the provisions of the Agreement or where not
so specified, in accordance with best industry practice.
The Vendor shall be responsible for any discrepancies, errors or omissions in the specifications, and
other technical documents that it has prepared, whether such specifications, drawings, and other
documents have been approved by the Project Manager or not, provided that such discrepancies, errors,
or omissions are not because of inaccurate information furnished in writing to the Vendor by or on behalf
of Owner.
5.1.3 Approval/review of technical documents by Project Manager
a) The Vendor shall prepare and furnish to the Project Manager the documents as specified in the
technical requirements for the Project Managers approval or review.
b) Within twenty one (21) days after receipt by the Project Manager of any document requiring the
Project Managers approval, the Project Manager shall either return one copy of the document to the
Vendor with its approval endorsed on the document or shall notify the Vendor in writing of its
disapproval of the document and the reasons for disapproval and the modifications that the Project
Manager proposes.
c) If the Project Manager disapproves the document, the Vendor shall modify the document and
resubmit it for the Project Managers approval. If the Project Manager approves the document subject
to modification(s), the Vendor shall make the required modification(s), and the document shall then
be deemed to have been approved. The procedure set out above shall be repeated, as appropriate,
until the Project Manager approves such documents.
d) The Vendor shall not depart from any approved document unless the Vendor has first submitted to
the Project Manager an amended document and obtained the Project Managers approval of the
document.
e) The Project Managers approval, with or without modification of the document furnished by the
Vendor, shall not relieve the Vendor of any responsibility or liability imposed upon it by any provisions


of the Agreement except to the extent that any subsequent failure results from inaccurate information
furnished in writing to the Vendor by or on behalf of Owner.
5.1.4 Packing, Protective Painting and Marking of hardware and other equipment or material
a) The Vendor shall include and provide for securely protecting and packing the equipment in
accordance with the best established practices so as to protect the contents from damage during
transit from point of manufacture until after arrival at Project Site under conditions which may involve
multiple handling, transport by ship, rail and road, reshipment, storage, exposure to heat, moisture,
rain etc. and possibility of pilferage. All packing shall allow for easy removal and checking at Project
Site. The Vendor shall stick/paste list of its contents on top of the Package. The Vendor shall ensure
packing of all items as listed in the packing list before finally dispatching the Package.
b) Fragile items shall be wrapped in crepe cellulose wadding or some equally efficient cushioning
materials and floated in excelsior and packed in substantial wooden covers with special precaution
against risk or breakage.
c) Wherever necessary the packages shall be marked with special markings such as TOP, BOTTOM,
DO NOT OVERTURN, FRAGILE, HANDLE WITH CARE, KEEP DRY, etc. as well as a special
symbol indicating the top.
d) Packing lists: Each package shall have inside it a detailed packing list quoting specifically the name of
the Vendor member, number and date of the Agreement, the name of the Owner and the detailed list
of contents packed within the package indicating the nomenclature of the Stores and a schedule of
parts of each complete Equipment, giving the part numbers with reference to the assembly drawings
and the quantity of each part, drawing numbers and tag numbers. A duplicate copy of the packing list
shall be put in a water proof envelope and fastened securely to the outside of the package as well as
to unpacked pieces or bundles.
e) Notwithstanding anything stated in the clause, the Vendor shall be entirely responsible for missing,
shortage, damage, loss or depreciation to the Materials occasioned by faulty, defective or insecure
packing or due to improper or insufficient protective system.
5.1.5 Record Maintenance: The Vendor shall maintain accurate records of works executed as per the scope of
the Agreement in a format that will permit audit.
5.1.6 Review of Progress: The work shall be executed strictly as per the time Schedule, indicated in the Bid
documents. Monthly / weekly work programme will be drawn up by the Vendor before commencement of
work & submitted to Project Manager for approval. The programme & progress will be reviewed from time
to time and if required, the programme may be re-scheduled by Project Manager. The Vendor shall also
be responsible to provide materials within his scope in time to achieve the programme. In all matters
concerning the extent of programme set out weekly and monthly, the decision of the Project Manager will
be final and binding on the Vendor. Both Parties shall agree to a planned review of the progress of the
works executed under the scope of the Agreement, in a periodic interval with a view to,
a. Review the progress
b. Resolve pending issues
c. Plan for resources required for ongoing and future works.
d. Evaluate all escalated issues and address mechanisms to remedy them.
During the term of this Agreement Owner reserves the right to formally audit and evaluate the
performance of the Vendor upon reasonable notice and at reasonable times.
5.2 Implementation Plan for FMS
a. The Vendor shall prepare a transition plan that sets out the steps to assume the provision of the
relevant Services and ensure an effective and orderly transfer of responsibility for the
management and provision of the Services to the Vendor.


b. The Vendor shall prepare a detailed Schedule for preventive maintenance of all the systems of
the Project.
6 Scope Change
Intentionally kept blank.
7 Product Upgrades
7.1 At any point during performance of the Agreement, if any technological advances be introduced by the
Vendor for Systems originally offered by the Vendor in its bid and which are still to be delivered, the
Vendor shall be obligated to offer to Owner the latest versions of the available System having equal or
better performance or functionality at additional cost if applicable and as mutually agreed.
7.2 Owner may at its discretion introduce all new versions, releases or updates of the software provided that
the new version, release, or update does not adversely affect the operation or performance or require
extensive reworking of the System. In cases where the new version, release, or update adversely affects
the System operation or performance, or requires extensive reworking of the System, the Vendor shall
continue to support and maintain the version or release previously in operation for as long as necessary
to allow introduction of the new version, release, or update. In no case shall the Vendor stop supporting
or maintaining the version or release of the software in operation for a period not less than that mentioned
in clause 10.
7.3 The Vendor shall not supply any software that Owner is not licensed to use, unless the product is
activated by a required license key. The Vendor shall also certify that all their products and updates as
supplied to Owner shall be free from viruses, worms, Trojans, spy-ware etc.
8 Assignment and Subcontracting
8.1 Assignment
The Vendor shall not transfer or assign the Agreement or any part thereof or any benefit or interest
therein or there under without the written consent of the Owner. In the event of the Vendor contravening
this condition, the Owner shall be entitled to place the Agreement else where on the Vendor's account
and at his risk and cost, then the Vendor shall be liable for any loss or damage which the Owner may
sustain in consequence or arising out of such replacing of Agreement. This shall not relieve the Vendor of
any responsibility under this Agreement.

8.2 Subcontracting
The Vendor shall not sub-contract the whole or any part of the Project to any person or firm or company
hereinafter referred as Sub-Contractor, without the prior approval of the Owner and such approval if
given shall not establish any contractual relationship between the Sub-Contractor and the Owner and
shall not relieve the Vendor of any responsibility, liability or obligation under the Agreement and the
Vendor shall be responsible for the acts, defaults and neglects of any Sub-Contractor or Sub-Contractors
agents, servants or workmen as fully as if they were the acts, defaults or neglects of the Vendor or his
agents, servants or workmen.

Notwithstanding any approval given by the Owner for sub-contract, it shall continue to be obligatory on
the part of the Vendor to provide to the Owner all the details viz., drawings, specifications, technical data,
detailed design, performance characteristics etc. from his Sub- Contractors.
9 Tests
9.1 After mutual consultation with the Owner, the vendor shall prepare and submit a detail plan containing
test schedule, test procedures & the various performance parameters for testing as per industry
standards & best practices for conducting various tests, hereinafter referred to as the Test Plan.
Necessary instruments, automated testing tools, consumables, personnel and other facilities required for
conducting the tests shall be arranged by the Vendor. All acceptance parameters as agreed between


Owner and the Vendor will be demonstrated during the tests. Some of the important performance
parameters are mentioned in Annexure-2. The Tests to be carried out shall include but not be limited to
the following.
9.2 Acceptance tests for installation & commissioning of infrastructure
Acceptance tests shall be carried out for the following infrastructure components in line with the cl.no -
9.2.1 & 9.2.2.
i. Data Center equipments.
ii. Hardware equipments
iii. Networking components
iv. Video conferencing system
v. IP telephony system.

The above infrastructure components shall be collectively referred to as Infrastructure.

9.2.1 Preliminary acceptance tests for Infrastructure components.
a) Preliminary acceptance test shall be conducted individually for the Infrastructure components.
b) As soon as the installation of individual components with all its auxiliary facilities including its final
connections is completed, Owner, jointly with the Vendor, shall proceed with preliminary tests to check
and ensure that all the units have been properly installed and are fit to be operated. The Vendor shall
be responsible for any defective functioning/ workmanship, if any and the resulting damages while
conducting the test. Defects found during the testing due to faulty installation shall be rectified by the
Vendor at his own cost and to the satisfaction of Owner.
c) All Infrastructure components will be tested for 72 hours of continuous working in confirmation to
specifications of the systems. The Vendor shall conduct commissioning test and establish 100%
satisfactory performance of the system supplied by him during this period. If the test is interrupted due
to any reason attributable to the Vendor, the system has to be started again for 72 hours continuous
testing. Any defect/malfunctioning found during this period shall be rectified and defective part if any,
shall be replaced immediately without any extra cost to Owner. In such case, the commissioning test
of the system shall be demonstrated again for the next 72 hours on a continuous basis.
d) Should the tested Infrastructure component or its system fail to conform to the specification, Owner
may reject the System, and the Vendor shall within a period of 14 (fourteen) days either replace the
rejected System, or make alterations as necessary so that it meets the required performance, without
any additional cost to the Owner.
e) As soon as the preliminary acceptance tests have been carried out individually and the results are
found to be satisfactory, Owner shall issue the preliminary acceptance certificate for the individual
Infrastructure components. Such certificate however shall be deemed to be on account and shall in no
way relieve the Vendor from the liabilities in respect of the work as a whole.
9.2.2 Final acceptance test for Infrastructure
a) After the issue of the preliminary acceptance certificate of all the individual Infrastructure components,
the Infrastructure shall be ready for the final acceptance test to ensure the integrated operation. The
final acceptance test for the Infrastructure shall be carried out during the Go-live acceptance test at full
load on the Infrastructure components with all the applications running so as to meet the standard of
performance parameters as per Annexure-2.
b) The Vendor shall use all reasonable endeavours to promptly remedy any defect and/or deficiencies
and/or other reasons for the failure of the final acceptance test of Infrastructure as notified by the
Owner. Once the Vendor has made such remedies, it shall notify the Owner, and shall use all
reasonable endeavours to promptly carry out retesting of the System.


9.3 Upon the successful final acceptance test of the Infrastructure, the Owner shall issue the final acceptance
certificate for the Infrastructure.
9.4 Acceptance Tests for SAP & non-SAP application implementation
9.4.1 Conference room pilot Tests for SAP application
a) Conference room pilot tests of SAP implementation shall be carried out through solution prototype to
check the fulfilment of functional requirements configured as per accepted business blue print. The
prototype validation will go through multiple iterations. The feedback provided to the Vendor after each
round of validation / conference room pilot must be documented and signed off by the Owner
nominated users. Changes to the solution must be presented to the users in next round of solution
validation or conference room pilot. This will be an iterative process till the solution prototype is signed
off as acceptable by the Owner.
b) Conference room pilot test certificate shall be issued on successful demonstration of all critical
functional requirements and at least 80 % of essential functional requirements as per agreed blue print.
9.4.2 User acceptance Tests for SAP & non-SAP applications
a) User acceptance Tests of the SAP and non-SAP application implementation shall be completed by the
Vendor as specified in the Test Plan.
b) Owner shall deploy the operating and technical personnel and all materials and information reasonably
required to enable the Vendor to carry out its obligations with respect to commissioning. Production
use shall not commence prior to the formal User acceptance testing.
c) The User acceptance tests (and repeats of such tests) shall be the primary responsibility of the Vendor,
but shall be conducted with the cooperation of Owner before the roll out of the implementation of the
SAP & non-SAP applications in production environment, to ascertain whether the System(s) conforms
to the Technical Requirements and meets the standard of performance parameters as specified in the
Annexure-2, including, but not restricted to, the functional and technical performance requirements.
The User acceptance Tests shall be conducted in accordance with the test scenarios provided by
Owner. At Owners discretion, user acceptance Tests may also be performed on upgrades and new
version releases that are added or modified after user acceptance of the System.
9.4.3 User acceptance for SAP & non-SAP applications
a) Subject to clause 9.4.4 below, user acceptance shall occur in respect of the implementation of SAP
and non-SAP applications, when the user acceptance Tests have been successfully completed.
b) At any time after any of the events set out in clause 9.4.2 have occurred, the Vendor may give a notice
to the Project Manager requesting the issue of an user acceptance certificate.
c) After receipt of the Vendors notice, the Project Manager shall within a reasonable period of time:
I. Issue a user acceptance certificate or
II. Notify the Vendor in writing of any defect for deficiencies or other reason for the failure of the
user acceptance Tests.
d) The Vendor shall use all reasonable endeavours to promptly remedy any defect and/or deficiencies
and/or other reasons for the failure of the user acceptance Test that the Project Manager has notified
the Vendor of. Once the Vendor has made such remedies, it shall notify Owner and shall use all
reasonable endeavours to promptly carry out retesting of the System. Upon the successful user
acceptance Tests, the Vendor shall notify Owner of its request for user acceptance certification, in
accordance with clause 9.4.3(b). Owner shall then issue to the Vendor the user acceptance
certification or notify the Vendor of further defects, deficiencies, or other reasons for the failure of the
user acceptance test in accordance with clause 9.4.3(c).


e) The procedure set out in this clause shall be repeated, as necessary, until a user acceptance
certificate is issued.
f) If the System fails to pass the user acceptance Test, then Owner may consider terminating the
Agreement, pursuant to clause 18.
9.4.4 Partial User Acceptance
a) User acceptance shall be carried out individually for each identified System of the SAP and non-SAP
application. In this event, the provisions in the Agreement relating to the user acceptance Test, shall
apply to each such System individually, and user acceptance certificate(s) shall be issued accordingly
for each such System of the SAP and non-SAP application, subject to the limitations contained in
clause 9.4.4(b)
b) The issuance of user acceptance certificates for individual Systems pursuant to clause 9.4.4(a) shall
not relieve the Vendor of its obligation to obtain a user acceptance certificate for the SAP and non-
SAP application as a whole once all Systems have been implemented.
9.5 Go-live and Stabilization Acceptance of Project
9.5.1 Go-live Acceptance
a) After the issue of the user acceptance certificates the Vendor will ensure that the Project is rolled out
for production environment, hereafter referred to as Go-live, in accordance with the timelines
specified in the Project Plan.
b) Owner shall deploy the operating and technical personnel and all materials and information reasonably
required to enable the Vendor to carry out its obligations under Go- Live as specified in the Project
Plan.
c) Different modules rolled out for Go-live will be operated in an integrated environment as per the
Project Plan. Upon successful operation of the Project in the production environment, Go-live
acceptance certificate will be issued.
d) After issue of Go-live Acceptance certificate Owner shall take over the Project implemented. However,
taking over by Owner shall relieve the Vendor of its obligations under this Agreement. Taking over
means taking over physical possession and the Project shall be operated under the supervision and
guidance of the Vendor till the Stabilization Acceptance Tests are carried out and the Stabilization
Acceptance Certificate is issued as per clause No. 9.5.2 here in below.
9.5.2 Stabilization Acceptance
a) During the stabilization period, the Vendor shall provide hand holding services (post Go-live support)
to Owner for optimum utilization of the Project.
b) The Stabilization Acceptance Tests (and repeats of such tests) shall be the primary responsibility of
the Vendor, but shall be conducted with the cooperation of Owner after stabilization period of the
Project, to ascertain whether the Project meets the standard of performance as specified in Annexure-
2 and functional requirements as desired by Owner. The Stabilization Acceptance Tests shall be
conducted as per the Test Plan in consultation with Owner. At Owners discretion, Stabilization
Acceptance Tests may also be performed on upgrades and new version, releases that are added or
modified. Stabilization Acceptance Test shall be of 21 days. The Stabilization Acceptance certificate
shall be issued by the Owner after achieving defined performance levels during Stabilization
Acceptance Tests.
c) If, for reasons entirely attributable to the Vendor, the Project does not conform to the Scope of
Agreement or does not conform to all /any other aspects of the Agreement, the Vendor shall at its cost
and expense make such changes, modifications, and/or additions to the Project as may be necessary


to conform to the Scope of the Agreement and meet all functional and performance standards. The
Vendor shall notify the Owner upon completion of the necessary changes, modifications, and/or
additions and shall request the Owner to repeat the Stabilization Acceptance Tests until the Project
achieves Stabilization Acceptance.
d) If the Project or its System(s) fails to achieve Stabilization Acceptance, due to reasons entirely
attributable to the Vendor, then Owner may consider termination of the Agreement, pursuant to clause
18, and forfeiture of the Vendors security deposit for the project in accordance with clause 12.5.2 in
compensation for the extra costs and delays likely to result from this failure without prejudice to other
rights of Owner available under the Agreement.
9.6 Final Acceptance of the Project
Once the Owner issues the Stabilization Acceptance Certificate, the Project represents a complete
solution to the Owners requirements set forth in the Scope of Agreement and it conforms to all other
aspects of the Agreement and stands finally accepted by the Owner, hereinafter referred to as Final
Acceptance.
10 Performance Guarantee / Warranty
10.1 The Vendor will provide the following Performance Guarantee / Warranty:
a) Performance Guarantee (PG) for the implementation of SAP and non-SAP applications shall be for the
period of 1 (One) Year from the date of Final Acceptance. During the performance guarantee period,
the Vendor shall extend all services required including but not limited to the details given in clause
10.4.
b) For Data center components including civil & electrical installations, the period of performance
guarantee / warranty shall be for a period of 1 (One) Year from the date of Final Acceptance.
c) For hardware, including Video Conference & IP Telephony, the period of performance guarantee /
warranty shall be for a period of three years from the date of Final Acceptance. The services required
are including but not limited to scope as given at clause 10.4.
d) For Network hardware & installations, the period of performance guarantee / warranty will be for 3
(Three) Years from the date of Final Acceptance. The services required are including but not limited to
scope as given at clause 10.4.
10.2 The Vendor will guarantee to Owner the performance of the Project for a period as stated above. This
Performance Guarantee (PG) will be applicable to all components of the solution including hardware,
network and implementation services. For the performance guarantee / warranty, Vendor shall provide
security deposit as per clause 12.4.1.
10.3 Owner will measure the performance of the Project against the technical parameters and performance
levels as indicated at Annexure -1 and Annexure-2. The Vendor should provide performance levels at
normal and peak load and Owners decision in this respect shall be final and binding on Vendor.
10.4 Detailed scope of Performance Guarantee/Warranty
The details provided below as part of the services to be covered under the performance guarantee /
warranty, shall not be limiting in the sense that the Vendor shall endeavor to provide such services in
conformation with industry best practices, which may be equal to or better than the level of services
provided herein. Further, the Vendor should ensure that such services shall be exclusive of the services
to be provided under FMS.
10.4.1 Annual Technical Support (ATS):
The ATS should cover the services which the Vendor provides normally under technical support and shall
include minimally the following support for RDBMS, EAI products and all other standard third party
software wherever applicable:


a) All product upgrades
b) User & Technical support on a 24x7 basis.
c) Technical Support for integration or installation of any patch or product upgrade for any third party
software.
d) Periodic site visit.
e) Database software.
10.4.2 Performance Guarantee/Warranty for hardware and Network hardware:
10.4.2.1 Performance guarantee and warranty support shall be delivered directly by the OEM through Vendor.
Certificate from OEM should be attached stating that the OEM will provide support directly during the
warranty period and subsequent AMC including replacement of spares. The OEM supplier/vendor
should undertake to
a) Provide comprehensive warranty for the supplied systems/subsystems for a period of 3 years from
the date of Final Acceptance.
b) Warrant the tapes, Diskettes, CDs or the media to be free of defects in material and workmanship
under normal case for 90 days from the date of Final Acceptance. During this period, Owner may
return defective media to the Vendor and it will be replaced free of cost.
c) If any document/manual supplied by the Vendor is found to be inadequate/ incomplete within the
period of the Agreement, the Vendor shall replace/complete such document/manual at their cost
within 15 days time.
d) Warranty shall cover the following:
i. Repair / replacement of hardware and other supplier items inclusive of all types of spare parts
including batteries, plastic parts, sprockets, glass items, picture tubes, print heads, etc. Only
consumables like printer ribbons, Ink cartridge, etc. are excluded.
ii. installation / re-installation / maintenance of OS, system software and other supplied software.
iii. installation of system software, patches, upgrades, service packs etc.
iv. Supply of all system software upgrades and patches.
v. Supply of future release of all OS and related system software
vi. Supply and install security patches and bug fixes
vii. 24 x 7 x 365 national telephonic support
viii. Access to raise technical assistance request at hardware vendors /supplier website.
10.4.2.2 The Vendor shall be required to provide the following services based on standards and the best
practices to meet or exceed the uptime/performance requirements:
a) 24 x 7 x 365 Support at IBTPS, Banharaplai, J harsuguda & HO, Bhubaneswar
b) Manpower at on-Site: Adequate number of competent hardware engineers to manage of all the
components of the supplied hardware (for server, storage & storage Nntwork, network hardware viz.,
routers, switches, firewalls etc.) and software, should be available on site to provide Warranty on 24
x 7 x 365 basis. The Manpower should be always available on site during office hours 9 AM to 6 PM
seven days a week. For rest of the period of the day, the manpower can either be available on site
or contacted on telephone. During non-office hours the manpower should reach site within one hour.
The concerned service engineers should be associated with the project from installation stage.
c) Must have service to support the following:
i. Maximum Two (2) hours response time for any reported fault.


ii. Maximum Twelve (12) hours resolution time to all hardware and OS related issues on High
Availability Clusters, SAN storage, Backup System, network hardware viz., routers, switches,
firewalls etc.
Maximum twenty four (24) hours resolution time to all hardware and OS related issues on all
stand alone systems
10.5 Defect Liability
10.5.1 The Vendor warrants that the Project, including all the System(s) and other Services provided, shall be
free from any defect or deficiency in the material, design, engineering, and performance/workmanship
that prevent the Project and/or any of its Systems(s) from fulfilling the technical requirements or that limit
in a material fashion the performance, reliability, or extensibility of the Project and/or any of its System(s)
as per the performance guarantee / warranty period defined at clause 10.1.
10.5.2 If during the warranty period any defect or deficiency is found in the material, design and
performance/workmanship of the Project and other Services provided by the Vendor, the Vendor shall
promptly, in consultation and agreement with Owner, and at the Vendors sole cost repair, replace, or
otherwise make good (as the Vendor shall, at its discretion, determine) such default, defect or deficiency
as well as any damage to the Project caused by such default, defect or deficiency. Any defective System
that has been replaced by the Vendor shall remain the property of the Vendor.
10.5.3 If the Project or any of its System cannot be used by reason of such default, defect or deficiency and/or
making good of such default, defect or deficiency, the warranty period for the Project shall be extended by
a period equal to the period during which the Project or any of its System could not be used by the Owner
because of such defect and/or making good of such default, defect or deficiency.
10.5.4 The warranties provided herein are in lieu of all other warranties, both express and implied, and all other
warranties, including without limitation that of merchantability or fitness for intended purpose is specifically
disclaimed.
11 Waiver
Failure of Owner to insist upon strict performance of any terms and conditions of the Agreement will not be
deemed a waiver of any rights or remedies that Owner may have and will not be deemed a waiver of any
subsequent default under the terms and conditions of the Agreement. No right or remedy of Owner will be
exclusive of any other right or remedy and Owner will have all the rights and remedies given under the
Agreement and now or hereafter, existing in law or by statute. The shipping or delivery by the Vendor or
receiving of payment by Vendor for the work under this Agreement will not be deemed a waiver of any rights
for any prior failure by the Vendor to comply with any of the provisions of the Agreement.
12 Price and Payment
For the performance of the IT Solution, the Owner shall pay to the vendor the price as stipulated in
Annexure-4 and as per the Payment Milestone given at Annexure-5.
12.1 Price
12.1.1 The FOR unit rates accepted by the Vendor as per the price schedule under Annexure-4 shall remain firm
and binding during the Term of Agreement subject to the variations stipulated hereinafter. The Vendor
shall perform all his works as envisaged in the Agreement.
12.1.2 Should the actual physical supplies and services are found more than those indicated by the Vendor in
the price schedule, the Vendor shall not be entitled for any additional amount from Owner. However in the
event of decrease in actual supplies/services/installation & commissioning, the Contract Price shall be
proportionately adjusted for the decreased supplies/services/installation & commissioning based on the
break-up furnished by the Vendor as annexure in the price schedule.
12.1.3 The prices are intended to provide for all the Scope duly and properly completed in accordance with the
terms and conditions of Agreement. Any additional items that are essential for execution and satisfactory
implementation of IT Solution shall be deemed to be included and covered but not limited to inter-alia, the
following:
a. The Prices shall include cost of delivery of all items for successful implementation of IT solution.
Items / Materials delivered by the Vendor for which payment was made by Owner shall remain the
property of Owner whether those are used or not.


b. The delivery terms for all supplies/services shall be on F.O.R. at Owners site. Payment against
supplies shall be released only on receipt and acceptance of material as per payment terms referred
under this clause.
c. The prices shall be inclusive of all Taxes, duties, levies etc. as detailed under clause 12.2.10 below.
12.1.4 The cost of all superintendence of labour, materials, tools, equipments, mobilizing and demobilizing
equipment, fixtures, transport charges, insurance charges, bank guarantee charges, temporary and
permanent works, testing, handling of materials, stocking and removal charges of any rejected materials,
power arrangement and satisfactory maintenance of the same for the full and satisfactory completion of
the works intended are all inclusive in the price.
12.1.5 All fees, duties, royalties, rent and compensation to Owner for surface damage or taxes and impositions
payable to local authorities in respect of all materials supplied for the work or other duties or expenses for
which the Vendor may become liable or may be put to under any provision of the law for the purpose of or
in connection with the execution of the Agreement including levies payable on all transactions are all
inclusive in the price.
12.2 Taxes & Duties
12.2.1 The price shall be inclusive of all taxes, duties, service tax and education cess thereon, imposed by
State/Central/Local governments and includes CENVAT (Excise Duty). Service tax and education cess
shall be paid subject to the Vendor complying with all the statutory requirements and furnishing the
relevant documents, to facilitate Owner to claim the CENVAT credit which inter-alia include copy of
Registration certificate from their jurisdiction of Superintendent of Service tax and Cenvatable invoices
containing the following details:

i. Name, address and the registration number and service tax range of each Vendor member.
ii. Name and address of the person receiving taxable service (Owner).
iii. Description, classification and the value of taxable service provided.
iv. Service tax and education cess payable thereon.

However the payment of service tax and education cess thereon shall be restricted to the total amount as
indicated in the price schedule


12.2.2 The Vendor has to indicate the amount of Orissa VAT and service tax for which they shall provide
relevant documents for enabling Owner to claim Input Tax Credit on Orissa VAT and CENVAT credit on
account of service tax.
12.2.3 Introduction/upward variation in taxes, duties, cess and levies, if any applicable shall be paid by Owner
subject to production of necessary documents by the Vendor. Similarly withdrawal/downward revision in
variation in taxes shall be adjusted in the price and benefit shall be passed to Owner. Fresh taxes &
levies, if any, as may be applicable on this Agreement, shall be reimbursable against documentary proof
to be submitted by the Vendor. The Vendor has to consider all taxes & duties applicable on this
Agreement. Any omission, or non-inclusion, either declared or not declared, of any taxes and duties that
are applicable at the time of submission of price bid/revised price bid /revision in prices shall not be
considered as a reason for reimbursement of such taxes and duties at a later date.
12.2.4 If the work is delayed for the reasons attributable to Owner and extension of the time for completion is
granted, variation in taxes and duties enacted during Contractual completion/execution period, the
adjustment in contract price shall be allowed within the extended period of the Agreement. Similarly, if the
work is delayed for the reasons attributable to the Vendor, variations in taxes and duties will not be paid.
12.2.5 The Vendor shall bear and pay all the liabilities in respect of non-observance of all legal requirements as
per various statutory provisions.
12.2.6 VATable invoice shall be submitted by the Vendor members duly complying with the procedure and
conditions stipulated by tax authorities to facilitate Owner to claim ITC on VAT for all supplies made from
within the State of Orissa. Payment of Orissa VAT shall be restricted to the value of Orissa VAT in
VATable invoices or the amount of Orissa VAT shown against ITC, whichever is lower. For this purpose
the amount of Orissa VAT indicated against different rates in the table shall be treated separately but total
amount of Orissa VAT on various items will be taken as one within the same rate category.
12.2.7 In case of bought-out items outside the state of Orissa, the Vendor shall make Sale in Transit as per
Section 6(2) of Central Sales Tax Act 1956 and all formalities required shall have to be observed by the
Vendor.
12.2.8 The adjustment in the Contract Price towards imposition of new taxes or abrogation of existing taxes shall
be applicable only if the new tax is enacted or existing tax is abrogated within Contractual
delivery/execution period. For any variation due to enactment of new tax or abrogation of existing tax after
Contractual delivery / execution period, adjustment in the Contract Price shall not apply.
12.2.9 All formalities required under statutes, for availing any concessions under relevant tax laws shall be
adhered to by the Vendor.

12.2.10 Deduction of Taxes At Source

12.2.10.1 Recovery at source towards income tax calculated at the rate prescribed from time to time under the
Income Tax Act 1961 and other relevant sections of Income Tax Act shall be made from the bills of the
Vendor and the amount so recovered shall be deposited with the Income Tax Department. Necessary
TDS certificate to this effect will be issued to the Vendor in the prescribed pro-forma.
12.2.10.2 If any other taxes / duties / cess etc are to be recovered at source as per government regulations /
Legislation from time to time, the same shall be recovered from the bills payable to the Vendor.
Necessary receipt to this effect will be issued to the Vendor in this regard as per the applicable
legislation.
12.3 Billing and Payment Terms
Billing and Payments shall be carried out from IB Thermal Power Station, Banharpali, J harsuguda office
of Owner. All interactions regarding the execution of the Agreement, submission of bills and
correspondence on any matter shall be done with the Project Manager / Owners representative.
12.3.1 Billing

12.3.1.1 Vendor shall submit running account bills as per the payment milestone with supporting documents for
having achieved the designated milestone activities.
12.3.1.2 All bills/invoices must be raised in INR only taking into account the prevailing taxes & duties with
reference to the Payment milestone.


12.3.2 Payment

12.3.2.1 Owner shalll release payments based on the Payment Milestones as indicated in the Annexure-5.
Payment shall be released on submission of the bill with supporting documents duly certified by the
Project Manager / Owners representative after deducting taxes at source as prescribed by the
legislative authorities, penalty and other recoverable if any. If such payment release day falls on a
holiday of Owner, payment will be released on the next working day. Against deduction of statutory
taxes, tax deduction certificates where ever applicable shall be issued as per the applicable provisions
of the statute. The Project Manager may recover any amount wrongly paid in excess in any previous
bills certified by him.
12.3.2.2 All payments shall be made direct to the Vendor or his authorized representative in the shape of
crossed A/c payee Cheque / Demand Draft less Bank Charges on certification of the Project
Manager/Owners representative and on compliance of contractual terms & conditions.
12.3.2.3 In case of shortage/missing/damage/ failure of any material identified at any point of time within the
period specified by the Agreement including guarantee period, the agency shall supply/replace the
same without any financial implication to Owner. The taxes, duties, clearing & forwarding and other
charges incurred by Owner in this regard shall be recovered from the Vendors pending bills and in
case no bills are pending the same shall be made good by the Vendor. The Vendor shall accordingly
submit the subsequent invoices.
12.4 Security Deposit
12.4.1 Security Deposit for Project
12.4.1.1 The Vendor shall stand guarantee for the overall performance as per clause 10 including the supplies
made and work to be done by the Vendor.
12.4.1.2 The Vendor shall furnish a Performance Bank Guarantee Bond from any scheduled bank (other than
cooperative Bank) in India as per the enclosed proforma at Annexure-6 before the signing of the
Agreement, for an amount equivalent to 10% of the of the Contract Price towards the Project, valid for
Ninety Days beyond the performance guarantee period. The issuing bank should be advised to send
a direct confirmation of issue of bank guarantee to Owner. Performance Guarantee Bond will be
released phase wise after satisfactory completion of respective components guarantee as defined in
clause 10 -performance guarantee / warranty. The Vendor shall have to submit a fresh Performance
Guarantee Bond of reduced amount proportionate to the remaining components as defined in clause
10-Performance Guarantee / Warranty in lieu of the released Performance Guarantee Bond. Owner
shall not be liable to the Vendor for any matter or thing arising out of or in connection with the
Agreement or the implementation of the Project unless the Vendor shall have made a claim in writing
in respect there of before issue of the Stabilisation Acceptance Certificate.
12.4.1.3 The Bank Guarantee for security deposit shall be for the due and faithful performance of the
Agreement and shall remain binding notwithstanding such variations, alterations or extensions of time
as may be made, given, conceded or agreed to between the Vendor and Owner.
12.4.1.4 Should the extent or the object of the Agreement be altered during the execution of the Agreement in
such a way as to effect an increase or decrease on the Contract Price by more than 10%, the amount
in the Bank Guarantee shall be increased or decreased correspondingly.
12.4.1.5 The bank guarantee and any amendment thereto shall be executed on a non-judicial stamp paper of
requisite money value as prescribed by the Statute.
a) All Bank Guarantees for security deposit, interest free recoverable advance and other
payments and extensions of Bank Guarantees shall be sent in a sealed envelope directly by
the Bank through Registered Post to Sr.Manager(PSM), Purchase & Contracts, IB Thermal
PS, Banharpali, J harsuguda.
b) Bank Guarantees / extensions of Bank Guarantees submitted by the Vendor directly will not
be admitted.
12.4.1.6 The Non-judicial stamp paper for the Bank Guarantee should be purchased in the name of executing
Bank only.


12.4.2 Security Deposit for FMS
12.4.2.1 An amount of 10% shall be retained as Security Deposit for FMS from each bill raised for FMS as per
the payment milestone. This security deposit shall be refunded to the Vendor after Six months of
completion of FMS.
12.5 Forfeiture Of Security Deposit
12.5.1 Whenever any claim against the Vendor for the payment of a sum of money arises out of or under the
Agreement, Owner shall be entitled to recover such sum by in part or whole from the security deposits. In
the event of the security deposit being insufficient or if no other security has been taken from the Vendor,
then the balance or the total sum recoverable as the case may be, shall be deducted from any sum then
due or which at any time thereafter may become due to the Vendor. The Vendor shall pay to Owner on
demand any balance remaining due.
12.5.2 In the event of any material breach by the Vendor or any loss or damage suffered by Owner which in the
opinion of Owner that the loss or damage has arisen due to reasons attributable to Vendor or in the event
of the termination of the Agreement for any such breach, the security deposit is liable to be forfeited. The
decision of forfeiture by Owner shall be final and binding on the Vendor.
13 Liquidated Damages
13.1 Liquidated Damages for the Project
13.1.1 Liquidated damages for failure by Vendor to meet critical techno-functional requirement specification of
the Project
The Vendor shall meet each functional and technical requirement specification of the Project. During the
implementation phase, if the Project is found not to be meeting the requirement specifications, the
liquidated damage structure as detailed below shall be applicable. The Parties hereby agree that the
Liquidated damages structure herein below is a genuine pre-estimate of the damages likely to be suffered
and not by way of penalty. The Liquidated damages shall be imposed without prejudice to the right of the
owner to make any other recoveries/levies mentioned else where in this Agreement or in Law.
a) Vendor shall meet all critical requirement specifications in the scope, in the event of any delay by
Vendor in meeting the critical requirements/ specifications beyond one month from the User
Acceptance Test of the Project and for not meeting 20 or more such critical requirement
specifications Parties agree that maximum of 5% of Contract Price towards the head of Project will
be levied as Liquidated damages. If it is less than 20 critical requirement specifications, the liquidated
damages shall be levied 1/20th of 5% of Contract Price towards the head of Project multiplied by
actual number of critical requirement specifications not met by the vendor.
b) Vendor shall meet all non-critical requirement specifications, in the event of any delay in meeting the
non-critical requirement specifications beyond three months from Go-live of the Project and for not
meeting 20 or more such non-critical requirement specifications a maximum of 2% of Contract Price
towards the head of Project will be levied as liquidated damages. If it is less than 20 non-critical
requirement specifications, Liquidated damages shall be levied 1/20th of 2% of Contract Price
towards the head of Project multiplied by actual number of non-critical requirement specifications not
met by the Vendor.
c) The above liquidated damages payable by the Vendor are only for delay in providing solution to the
functional and technical requirement specifications in time as per schedule given in the Agreement.
Even after completion of the time given as above, if the requirements are still not met by the Vendor,
the requirements of Owner will be carried out by another alternative party at risk and cost of the
Vendor. In such an event the entire additional cost/amount incurred by Owner in addition to the
liquidated damages levied above will be recovered from the pending bills of the Vendor and if the
same is not sufficient, the performance Bank Guarantee given by the Vendor shall also be
invoked/used to recover the costs incurred by Owner. If the amount is still not sufficient to meet the
costs incurred by Owner, the same is to be made good by the Vendor upon notification by Owner in
writing to the Vendor.


d) During validity of the performance guarantee, for non-performance against any of the technical
parameters as per clause 10.3, Owner reserves the right to levy liquidated damages of 2.5% of
Contract Price towards the head of Project for not meeting the response time and further liquidated
damages of 2.5% of Contract Price towards the head of Project for not meeting the uptime
requirements of technical parameters and will notify the Vendor accordingly. The decision of Owner in
imposing the liquidated damages as above will be final, but in any case, the liquidated damages for
13.1.1(a) to (d) shall not exceed 5% of Contract Price towards the head of Project.
13.1.2 Liquidated Damages for failure to adhere to the timelines of the Project
a) The Vendor shall stand guarantee for the performance and output as envisaged in the Agreement.
b) If the Vendor fails in the due performance of the Project within the timelines fixed by the Agreement or
any extension thereof and/or to fulfil its obligations in time under the Agreement or any extension
thereof, Vendor shall be liable to pay Liquidated damages to the extent of a sum of 1% of Contract
Price towards the head of Project per week or part thereof for which the delay has occurred, subject
to a maximum of 10% of Contract Price towards the head of Project. In assessing such delays, the
Project Managers decision is final and binding on the Vendor. Parties agree that this is a genuine
pre-estimate of the damages and not by way of penalty.
c) The recovery of Liquidated damages shall not relieve the Vendor from its obligations to complete the
work or from any of its obligations and liabilities under the Agreement.
d) The decision of Owner with respect to this clause is final and binding on the Vendor.
13.2 Liquidated Damages for FMS
The Vendor shall ensure that the faulty network devices, servers, PCs and peripherals etc are repaired /
brought back to service within specified resolution time of service level of FMS. The resolution time shall
not exceed the stipulated time for mission critical networking (Criticality-I) equipment, units and
components, as mentioned in the service level of FMS. Criticality-I items/calls are to be closed within the
service level, irrespective of time the call is registered. In case the Vendor fails to meet the Service levels
in time, an amount equal to 0.5 % of Contract Price towards the head of FMS per week of default in such
services subject to a maximum of 10 % of the Contract Price towards the head of FMS shall be recovered
as liquidated damages. Parties agree that this is a genuine pre-estimate of the damages and not by way
of penalty.
13.3 Notwithstanding anything to the contrary in the Agreement, the overall cap of cumulative of penalty and
liquidated damages shall not exceed 15% of the Contract Price.
14 Insurance
a) The comprehensive insurance and safety of all men and material of the Vendor shall be the responsibility of
the Vendor. The comprehensive insurance should cover for full value against loss, damage or destruction by
fire, lightning, earth quake, theft, pilferage, non-delivery of package/packages and all other risks including
strikes, riots and civil commotions during transit, storage, testing & commissioning and guarantee tests to
protect Owner and the Vendor from any loss arising out of such condition.
b) The insurance policy shall be tripartite, Owner being the beneficiary. The insurance cover shall remain in full
force up to the time the Project is accepted and Stabilization Acceptance Certificate is issued by the Owner.
The Vendor shall produce the insurance policy and receipts for the premium at the appropriate time. All
money received under any such policy shall be applied in or towards the cost incurred for the
damage/deficiency but this provision shall not affect the Vendor liabilities under the Agreement.
c) The Vendor shall maintain in full force and affect all such insurances as above and required by the law for the
purpose of the Agreement at the cost of the Vendor.
d) The Vendor shall furnish to the Project Manager/Owners representative with evidence of such insurance a
copy of the issued policy and any cancellation or termination thereof. Should the Vendor default in paying any
premium when due, Owner, without prejudice to other remedies set forth in this Agreement shall be at liberty
to pay such premium and recover the same from Vendor.
e) The provisions contained within this clause are not intended to and do not impair or in any manner limit the
liabilities or obligation assumed by Vendor as may be set forth more fully elsewhere in the Agreement.


f) The Vendors services shall include the filing and pursuance of all insurance claims on behalf of Owner and
the entire Work incidental thereto till realization of Claim.
g) Owner shall be the principal holder of the policy along with the Vendor. Owner reserves the exclusive right to
assign the policy.
h) The Vendor shall be responsible for effecting insurance under the Indian Workmens Compensation Act and
any other insurance in accordance with the Indian laws and regulations at his own cost.
i) If any Agreement Scope including supplies and services perishes or becomes unserviceable due to any
cause whatsoever, including missing, shortage, loss or damage and/or various destructions and risks as
mentioned above, the Vendor shall on demand by Owner make replacement at his own cost and in such a
way as to avoid disturbances in the general progress of IT Solution. This shall apply irrespective of the
question whether or not the risk has passed to Owner or who shall be responsible for such unserviceable
condition as aforesaid.
j) Upon arrival at Project Site, all equipment, Materials, commissioning spares, special tools & tackles, all
consumables, etc., the Vendor shall assume custody thereof and remain responsible therefore, until the
physical possession taken by the Owner.
k) The Vendor shall, as custodian, be responsible for communicating to the project manager / Owners
representative any shortages, missing, breakages, damages, etc. as soon as they come to his notice without
prejudice to his obligation under Agreement.
l) The insurance policy obtained by the Vendor shall also cover liability for accidents resulting in death, injury,
damage to property of Owner or any third party including employees of third parties and / or Owner
employees within the premises and precincts of Owner.
15 Indemnity
The Vendor assumes responsibility for and shall indemnify and save harmless the Owner, from all liability, claims,
costs, expenses, taxes and assessments including penalties, punitive damages, attorney's fees and court cost
which are, or may be required with respect to any breach of the Vendors obligations under the Agreement, or in
respect of all salaries, wages or statutory dues or any other compensation or dues of whatsoever, nature of all
persons employed by the Vendor in connection with performance of the Scope of this Agreement. Owner shall the
vendor to take sole control of the defence of such claims. The vendor shall execute and deliver such other further
instruments as may be necessary to comply with all the requirements of such laws and regulations as may be
necessary there under to confirm and effectuate the Agreement and to fully protect and indemnify the Owner. The
Vendor shall not indemnify Owner to the extent that such liability, damage, claims, fines, penalties, and expenses
were caused or contributed to by the sole fault of the Owner. The Owner shall not be in any way held responsible
for any accident or damages incurred or claims arising there from during discharge of the obligations by Vendor
under this Agreement.
16 Patent Infringement
The Vendor shall protect, indemnify and save harmless the Owner, his customers and users of his products,
against all liability, including cost, expenses, claims, suits or proceedings at law in equity or otherwise, growing
out of or in connection with any actual or alleged patent infringement (including process patents, if any) or
violation of any license and will defend or settle at the Vendors own expense any such claims, suits or
proceedings.

The Owner will notify the Vendor in writing of any such claim, suit, action or proceeding coming to his attention,
giving authority and all available information and assistance for the Vendors defence of the same. The Vendor
shall appoint a counsel at his own expenses in consultation with the Owner to collaborate in the defence of any
such claim, suit, action or proceeding.
17 Settlement of Disputes
The Agreement shall in all respects be construed and carried into effect and rights and liabilities of the Parties
hereto shall be regulated according to the laws of India.


17.1 Mutual Settlement of Disputes
Except where otherwise provided for in the Agreement, other than excepted matters all questions and
dispute relating to any matter directly or indirectly connected with this Agreement shall in the first place be
resolved through mutual discussions, negotiations, deliberation and consultations between both the
Parties.
17.2 Conciliation
If the effort to resolve all or any of the disputes other than excepted matters through mutual settlement
fails, such disputes shall be referred to the conciliator to be appointed by the mutual agreement of both
Owner and the Vendor. The conciliator shall make the settlement agreement after the Parties reach
agreement and shall give an authenticated copy thereof to each of the Parties. The settlement agreement
shall be final and binding on the Parties. The settlement agreement shall have the same status and effect
of an arbitration award. The venue of Conciliation shall be Owners Corporate Office, Bhubaneswar.
17.3 Arbitration
In the event, the dispute can not be settled amicably, the same shall be resolved through the provisions
contained in the Arbitration and Conciliation Act 1996, or any statutory modification or re-enactment
thereof and the rules made there under for the time being in force. The arbitration award shall be final and
binding for the Parties without appeal and shall be in writing and set forth the findings of fact and
conclusion of law. The number of arbitrators shall be three, with each side of the dispute being entitled to
appoint one arbitrator. The two arbitrators appointed by the Parties shall appoint a third arbitrator who
shall act as chairman of the proceeding. All proceedings shall be conducted, including all documents
presented in such proceedings, in the english language. The venue of arbitration shall be at
Bhubaneswar only and jurisdiction for any proceedings arising out of or concerning or connected with
such arbitration shall be of appropriate court at Bhubaneswar under the jurisdiction of Orissa High Court.
For all disputes, appropriate court at Bhubaneswar under the jurisdiction of Orissa High Court alone shall
have exclusive jurisdiction in all matters arising under this Agreement.
18 Term and Termination
18.1 Term of Agreement
a) The Effective Date of the Agreement shall commence from the signing of Agreement. Time period for
implementing the Project is 12 months (6 Months till Go-live and 6 months of stabilization including
the 14 days of initial mobilization).
b) The Time period for the FMS is 48 months from the date of Final Acceptance of the Project. The
Owner has the right to extend the service term by additional periods, on at least 30 days notice
before the expiry of the current service term.
c) The Vendor should bear in mind that the stipulated time for completing the scope as per the
Agreement is the essence of the Agreement, unless such time is extended pursuant to the provisions
of this Agreement.
d) The Vendor shall complete the entire work inline with this Agreement within the stipulated time frame.
No extra time or extension of Agreement period is allowed unless specifically agreed to in writing by
the Owner.
18.2 Extension of Time
If, for any special circumstances, an extension of time is required, then the Vendor shall inform to the
Project Manager/Owners representative, within 15 days from the date of occurrence of such
circumstances, request with full particulars for extension of time for which it may consider itself entitled in
order that such request may be examined. The decision of the Project Manager / Owners representative,
shall be final and binding in this aspect and no additional remuneration shall be payable for the extended
period for the scope of work covered under this Agreement.


18.3 Termination of the Agreement
18.3.1 Termination of Agreement on Vendor's Default

The Owner, without prejudice to any other remedy for material breach of Agreement, by written notice of
default sent to the Vendor, may terminate this Agreement in whole or in part:
a) If the Vendor materially fails to complete any part of all the work or all of the goods within the
period(s) specified in the Agreement, or within any extension thereof granted by the Owner.
b) If the Vendor fails to perform any other obligation(s) under the Agreement.
c) If the Vendor, in the judgment of the Owner has engaged in Corrupt Practices or Fraudulent
Practices in competing for or in executing the Agreement.
For the purpose of this clause:
"Corrupt Practices" means the offering, giving, receiving or soliciting of any thing of value to
influence the action of a any official, be it from the Owners organisation or any other Govt. or
non-govt. body, in the procurement process or in Agreement execution. "Fraudulent Practices"
means a misrepresentation of facts in order to influence a procurement process or the execution
of a Agreement to the detriment of the Owner and includes collusive practice among bidders
(prior to or after bid submission) designed to establish bid prices at artificial non-competitive
levels and to deprive the Owner of the benefits of free and open competition".
In the event the Owner terminates the Agreement in whole or in part, the Owner may procure / get
repaired, upon such terms and in such manner as it deems appropriate, Goods or Services similar to
those undelivered / un-repaired, and the Vendor shall be liable to the Owner for any excess costs for such
similar Goods or Services. However, the Vendor shall continue performance of the Agreement to the
extent not terminated.

18.3.2 Termination for Insolvency of the Vendor

The Owner may at any time terminate the Agreement by giving written notice to the Vendor if the Vendor
becomes bankrupt or otherwise insolvent. In this event, termination will be without compensation to the
Vendor, provided that such termination will not prejudice or affect any right of action or remedy which has
accrued or will accrue thereafter to the Owner.

18.3.3 Termination of Agreement on Owner's Initiative

The Owner reserves the right to terminate the Agreement either in part or in full due to reasons other than
those mentioned under clause entitled "Vendor's Default" or due to the outbreak of war. The Owner shall
in such an event give thirty (30) days notice in writing to the Vendor of his decision to do so.

The Vendor upon receipt of such notice shall discontinue the work on the date and to the extent specified
in the notice, make all reasonable efforts to obtain cancellation of all orders and Agreement to the Owner,
stop all further sub-contracting or purchasing activity related to the work terminated, and assist the Owner
in storage, maintenance, protection, and disposition of the works acquired under the Agreement by the
Owner.

18.3.4 In the event of termination for whatsoever reason, the Vendor shall be paid equitable and reasonable
compensation, as dictated by the circumstances prevalent at the time of termination.
19 Force Majeure
If at any time during the continuance of the Agreement, the performance in whole or in part by either party or any
obligations under the Agreement shall be prevented or delayed by reason beyond reasonable control of the party
including without limitation such as any war, hostilities, act of public enemy, civil commotion, sabotage, fire,
floods, earthquake, explosions, epidemics, quarantine restrictions and acts of God (hereinafter referred to as
'Events') and provided notice of the happening of any of the above mentioned Event is given by either party to
the other within 21 days from the date of occurrence thereof, the agreed timelines shall be extended by the Owner
on receipt of application from the Vendor without imposition of penalty and the services under the Agreement


shall be resumed after such event has come to end/ceases to exist. Should one or both the Parties be prevented
from fulfilling their contractual obligations by a state of force majeure lasting continuously for a period of at least 3
months and the Owner not having terminated the Agreement by that time, the two Parties shall consult each other
regarding the further implementation of the Agreement with the provision that if no mutually satisfactory
arrangement is arrived at within a period of 2 months from the expiry of 3 months referred to above, the
Agreement shall be deemed to have expired at the end of the 2 months referred to above. The above mentioned
expiry of the Agreement will imply that both the Parties have obligations to reach an agreement regarding the
winding up and financial settlement of the Agreement.
20 Ownership
20.1 Ownership of Documents and Copy Rights
All study documents, data and specification prepared by the Vendor subject to the Scope of Agreement
shall be the property of Owner. As and when required or upon termination of the Agreement, the
aforesaid documents of all versions shall be handed over to Owner. Vendor shall take all necessary steps
to ensure confidentiality in handling of all the matters pertaining to business process studies, data,
specifications, methods and other information developed or acquired or furnished by Owner by means of
this Agreement or in the performance thereof.
Ownership and the terms of usage of the software and Materials supplied under the Agreement shall be
governed by this clause. The vendor shall grant Owner a perpetual license to use the software without
any additional payment or obligations to enter into a contact for maintenance or support.
20.2 Transfer of Ownership
The Project and its System(s) shall be deemed to have passed onto the Owner when the Project is tested
for its performance, validation and acceptance by Owner. However the Licensing rights with regard to
Core SAP Product and the third party software shall be governed by the End User License Agreement
(EULA) of respective OEM.
21 Limitation of Liability
21.1 Notwithstanding anything to the Contrary in the Agreement or any other document, the aggregate liability
of the vendor for actual direct damage shall be limited to the Contract Price provided that this limit shall
not apply to the patent infringement, bodily injury (including death) and damage to the real property and
tangible personal property caused by Vendors negligence.
21.2 In no event, neither party shall be liable to the other party for any indirect, special, punitive, consequential
or incidental damages including without limitation, loss of revenue, profits, business, goodwill, anticipated
savings or data or third party claims.
21.3 No Director or official or employee of Owner or Vendor shall in any way be personally bound or liable for
the acts or obligations of the Owner or Vendor under the Agreement or answerable for any default or
omission in the observance or performance of the acts, matters or things which are herein contained.
21.4 The Vendor shall not be entitled to any increase on the scheduled rates or any other rights or claims
whatsoever by reason of any representation, explanation, statement or alleged understanding, promise or
guarantees given or to have been given to him by any person.
22 Time of the Essence
Time is of the essence of this Agreement. The acceptance of a late performance with or without objection or
reservation by Owner shall not waive any rights of Owner or constitute a waiver of the requirement of timely
performance, of any obligations remaining to be performed.
23 Confidential Information
In the performance of its obligations under this Agreement or in the contemplation thereof, the Vendor and its
employees may have access to private or confidential information, including but not limited to information
concerning costs, charges, operating procedures and technical information, which may be owned or controlled by


Owner or its parent or affiliates. With respect to any such information so accessed or acquired, the Vendor and
Owner, mutually agree as follows:

a) all information provided by Owner shall be and shall remain the exclusive property of Owner or its parent
or affiliates;
b) the Vendor shall limit access to such information to its employees who have a need to know, consistent
with the Vendor's authorized use of such information;
c) the Vendor shall keep, and have its employees having access keep, all such information confidential;
d) the Vendor shall not copy, publish or disclose to others, or permit its employees or anyone else to copy,
publish or disclose to others, any such information;
e) the Vendor shall return such information to Owner at its request;
f) the Vendor shall use such information only for the purpose of performing its obligations hereunder;

The Vendor at all times shall maintain appropriate internal policies and procedures reasonably sufficient to satisfy
its obligations under this provision.

If the Vendor is required to disclose any confidential information of Owner or its parent or affiliates pursuant to any
governmental or legal proceedings, the Vendor shall not be liable for such disclosure provided that it gives Owner
written notice of the proceeding and seeks an appropriate protective order at least ten (10) business days prior to
its disclosure of the aforementioned confidential information.
24 Miscellaneous
24.1 The Vendor represents and warrants to the Owner that as of the effective date of this Agreement,(a) it is
a corporation duly organized, validly existing and in good standing under the laws of Country of India, (b)
it has all requisite power and authority to enter into and perform its obligations under this Agreement, and
(c) there are no actions, suits or proceedings pending, or to the best of its knowledge threatened, which
may have a material adverse effect on its ability to fulfill its obligations under this Agreement or on its
operations, business, properties, assets or condition.
24.2 The Vendor shall comply with all laws in force in India. The laws will include all national, provincial,
municipal, or other laws that affect the performance of the Agreement and are binding upon the Vendor.
The Vendor & the Owner agree that the Courts of Orissa shall have the exclusive jurisdiction for any and
all disputes, differences and claims arising out of, regarding or in relation to this Agreement or any work
issued hereunder.
24.3 If any provision of this Agreement is found to be illegal or unenforceable then, notwithstanding such
illegality or unenforceability, this Agreement shall remain in full force and effect and there shall be
substitution for such illegal or unenforceable provision a like but legal and enforceable provision which
most nearly effects the intention of the Parties. In the event a like but legal and enforceable provision
cannot be substituted, the illegal or unenforceable provision shall be deemed to be deleted and the
remaining provisions shall continue in full force and effect, provided that the performance, rights and
obligations of the Parties under this Agreement are not materially adversely affected by such deletion.
24.4 Notwithstanding any provisions in the contrary which may be contained elsewhere herein, any
stenographic, typographic or clerical errors found in this Agreement shall be deemed as automatically
corrected without necessity of written amendment.
24.5 No amendment or other variation of the Agreement shall be effective unless it is in writing, is dated,
expressly refers to the Agreement, and is signed by a duly authorized representative of each party to the
Agreement.
24.6 Neither party shall, during the term of this Agreement and for a period of three (3) months thereafter
directly or indirectly, solicit or hire the personal of the other party.
24.7 If at any time should there be any evidence or any lien, claim for which Owner might become liable, which
is chargeable to the Vendor, and then the Owner may pay and discharge the same and deduct the
amount so paid from any amount which may be or may become due and payable to the Vendor. If any
lien or claim remains unsettled after all payments are made, the Vendor shall refund or pay to Owner the


cost of such lien or claim including all payments and reasonable expenses. Owner reserves the right to
the same.
24.8 This Agreement shall inure to the benefit of and be binding upon the respective successors and permitted
assigns, if any, of the Parties, provided that this provision shall not be construed to permit any assignment
which would be unauthorized or void pursuant to any other provision contained herein.
24.9 If a work is transferred from the jurisdiction of Owner to any Successor, while the Agreement is in
subsistence, the Agreement shall be binding on the Vendor and the Successor in the same manner and
take effect in all respects as if the Vendor and the Successor were parties there-to from the inception and
then corresponding office of the competent authority of the Successor will exercise the same powers and
enjoy the same authority as conferred to Owner under the original Agreement entered into and the
Project Manager so appointed shall have the same powers as envisaged in the Agreement.
24.10 Any notice to be given to the Vendor under the terms of the Agreement shall be considered as duly
served if the same shall have been delivered to, left for, or posted by registered post to the address of the
Vendor at their registered office. Similarly, any notice to be given to the Owner shall be considered as
duly served, if the same shall have been delivered to, left for, or posted by registered post to the Owners
office. All notices shall be delivered or sent to the other party at the address(s) shown below or at any
other address(s) as the party may designate subsequent to signing of this Agreement.

If to Owner: If to Vendor:
______________________ ________________________
24.11 Changes of location of site/offices do not invalidate the Agreement and Vendor shall have no claim for
any compensation for such changes.

IN WITNESS WHERE OFF, both the Owner and the Vendor through their duly authorised representatives, have
executed these presents (execution thereof has been approved by the competent authority by both the Owner
and Vendor) on the day, month and year mentioned herein.

For & on behalf of For & on behalf of

Orissa Power Generation Corporation Ltd. ___________________________________

In presence of In presence of


Annexure-1: Detailed Scope of Work
The proposed project implementation will be carried out in the following geographical locations
a) ITPS Plant / Works Banharpalli, J harsuguda (Orissa)
b) Head Office Bhubaneshwar
Further, any other offices may be established based on the requirement and expansion of the plant activities
during the execution of project.
1. Supply of Hardware and Non-SAP Software
1.1. Supply of Hardware Data Center Equipments
The vendor shall supply all the items necessary for the erection & commissioning of the Data Center including but
not limited to the following
a) Civil construction items such as partition, tiled floor, false floor, false ceiling etc.
b) Electrical items such as LT Panels, Power Cables, PVC Copper cables, PVC conduict, Power Distribution
board, Lighting Distribution Boards, MCCB, Earthing System for electrical installations, RF earthing for UPS &
Servers.
c) Dual redundant UPS system along with independent Battery Bank, UPS Distribution Boards.
d) Illumination system and its accessories.
e) Precision Air-conditioning System, Water Leak Detection System complete with its electrical.
f) Access Control System, Rodent Repellent System, CCTV System.
g) Items for Fire Detection & Protection system and VESDA system.
h) Items for building management system with sensors, direct digital controllers, communication controllers etc.
The number of controllers shall be based on the input / output summary given in the BMS specifications.
Generic specifications for the above are provided in Table-03 & Table - 10 of Annexure-1. All bought out items
shall be as per the acceptable make list given at Table-03 & Table - 10 of Annexure-1. Any other materials
proposed, other than preferred makes, will require approval from Owner.
1.2. Supply of Hardware Servers, Storage, Backup Devices, Racks & Other hardware (PCs/Printers) etc.
The vendor shall supply al the hardware infrastructure including but not limited to the following.
a) Servers
b) Racks with KVM
c) SAN storage with SAN switch
d) Backup Devices
e) other required items
1.3. Supply of hardware Networking Equipments
The vendor shall supply all the networking Equipments required for the infrastructure including but not limited to
the following.
a) Switches Core Switch, Distribution Switch, Access Switch, Server-firm switch etc.
b) Routers
c) Firewall & IPS
d) Modem
e) Fiber Optic Cable
f) UTP cable
g) Fiber & UTP Connectors & IO


h) NMS equipments
i) Internet Connectivity and WAN connectivity Bandwidth
j) other required items

Generic specifications of key hardware and Network Equipments are provided in Table-2 of Annexure-1. All
bought out items shall be as per the acceptable make list given at Table-2 of Annexure-1. Any other materials
proposed, other than preferred makes, will require approval from Owner. The OEM should provide service, spares
support to Owner during Warranty period and subsequent AMC period. The necessary certificate should be
provided by the Vendor from the OEM as part of the bid.
1.4. Supply of Hardware Video conferencing Equipments
The Vendor shall supply all the items necessary for Video Conferencing. Generic Specification of Video
Conferencing equipments & software is provided in Table-5 of Annexure-1
1.5. Supply of Hardware IP Telephony Equipments
The Vendor shall supply all the items necessary for IP Telephony. Generic Specification of Video Conferencing
equipments & software is provided in Table-6 of Annexure-1
1.6. Supply of Non-SAP Software
The Vendor shall provide Licenses for all Non-SAP application software including Operating Systems and other
related software on all servers / storage broadly covering but not limited to the following.
a) Supply of Non-SAP software Messaging & Collaboration System.
b) Supply of Non-SAP software Anti Virus / Anti Spam /Content Filtering
c) Supply of Non-SAP software EMS/NMS and Service Desk tools.
d) Supply of Non-SAP software Building Management System (BMS)
e) Supply of Non-SAP software Video conferencing & IP Telephony
f) Supply of Non-SAP software Other software
The Vendor shall provide media for the software/ applications as well as hard copy of the licences. Time to time
patches, updates shall also be provided by the Vendor.
2. Design, installation and commissioning of Infrastructure
The Vendors will be responsible for design, installation and commissioning of necessary infrastructure required
for running the intended applications and their management.
2.1. Design, installation and commissioning of Data Center
The Vendor shall design, install and commission the interior work and infrastructure for Data Center including but
not limited to the following required services. The Vendor shall submit the design and drawing documents for
validation of Owner before commencing the installation and commissioning work.
a) Civil construction including walls, partition, tiled floor, false floor, false ceiling etc. The Vendor shall make
temporary arrangements to secure the site from the regular working office area. In case the work requires
demolition of part of existing structure such as walls, false ceiling, and re-routing/ dismantling of existing
communication, electrical wiring, fixtures & fittings, the same shall be in the Vendors scope.
b) Erection, testing and commissioning of Power Distribution board, Lighting Distribution Boards, UPS Distribution
Boards.
c) Laying, terminations, testing and commissioning of power cabling. This includes making of Raceways for
power as well as networking cables. Design and installation of LT Panel, termination of incoming cables
brought up to the Panel room, testing and commissioning.
d) installation, testing and commissioning of Dual redundant UPS and independent battery bank at the Data
Center. The scope includes installation of two nos. of MCCB of appropriate rating, 415 V, three phase and ly,
laying, termination of FRLS, PVC copper cables in PVC conduit from UPS DB at Data Center.


e) installation, testing and commissioning of Illumination system.
f) Erection, testing and commissioning of Earthing System for electrical installations, RF earthing for UPS. The
earthing of servers is also included in this package; along with grid for RF earthing shall be in the scope.
g) installation & commissioning of Precision Air-conditioning System, Water Leak Detection System complete with
its electrical for Data Center.
h) installation & commissioning of Access Control System, Rodent Repellent System, CCTV System.
i) installation & commissioning of Fire Detection & Protection system and VESDA system.
j) installation & commissioning of Building Management System.
Generic specifications for the above are provided in Table-03 & Table - 10 of Annexure-1 of this document. On
completion of work, the Vendor should furnish 6 sets of hard and soft copy of complete technical documents
along with as-built drawings for all the systems. The Vendor should submit all the following design & drawing
documents for scrutiny of Owner.

Architectural Drawings
a) Plan of Data Center indicating the proposed equipment layout.
b) Sections of Data Center indicating all proposed partitions, panelling, false ceiling/ flooring etc.
c) Details of ceiling and flooring.
d) Material specifications.

Electrical: Drawings and Documents
a) Power calculations and Single line diagrams of L.T Panel and DB.
b) Make and Model of all equipment and components used along with their ratings and type.

Air conditioning: Drawings and Documents
a) Make and Model of all equipment and components used along with their ratings and type.
b) Single line diagram.
c) Calculation for estimation of cooling load and dehumidified air quantity.
d) Details of individual items like compressors, condensers, fans, air filters, controls, accessories, interlocks,
insulations, ducting etc.

Associated systems
a) Technical Specifications of components proposed for all the systems like Access Control and Surveillance,
Fire Detection and Suppression, Rodent repellent system, Water leak Detection system, VESDA, CCTV etc.,
networking for the same along with catalogues.
b) Write up on remote monitoring and views/ reports generation.
2.2. installation & commissioning of Hardware
For running the intended applications as mentioned in the scope of Agreement, the Vendor shall design, install
and commission the hardware infrastructure including but not limited to the following. The hardware shall be
designed to meet the user workload and performance requirements
a) Servers for SAP and Non-SAP Applications
b) SAN storage, SAN switch and required cabling
c) Administrative Tools
d) Tape Library
e) Racks with KVM and Peripherals

The Vendor shall submit the designed solution architecture of the hardware infrastructure, hardware sizing
documents for validation of the owner before commencing installation and commissioning.
Hardware sizing for SAP Production, Development and QA / training environment designed by Vendor
shall be validated by SAP.


Hardware sizing for messaging and Collaboration system should be certified for the performance requirements by
the OEM of Messaging software Application.

The factors/ considerations required for solution architecture and hardware sizing are as under

a) All servers shall be optimally sized in such a manner that they are able to meet the performance and
availability criteria of the offered SAPs ( minuimum SAPs is mentioned bellow) and other solutions like
Messaging & Collaboration with stated concurrent users at maximum 70% of installed capacity. Design
provision shall be kept to double the capacity with out physically adding up boxes.

Instances SAPs
Database Server 10000
Production Server 10000
Development 5000
Quality Server 5000

b) The Solution Architecture should be depicted in text and schematic to explain high availability configuration
Architecture i.e. failure of any component should not fail or degrade any service. No dual port adaptor should
be used in the solution architecture.
c) Development infrastructure needed to support ongoing development/ upgrade needs during and post
implementation.
d) Quality Assurance (QA) / Training Infrastructure will be needed for conducting tests and trainings during and
post implementation.
e) The Disaster Recovery site will be set in future course of time. However, the recovery strategy against failure
of Servers and SAN, based on RTO (Recovery Time Objective) of 2 hours and RPO (Recovery Point
Objective) Zero for Synchronous and RTO (Recovery Time Objective) of 4 hours and RPO (Recovery Point
Objective) 30 minutes for Asynchronous shall be given by the Vendors and the provisions shall be kept
accordingly.

The Vendor will offer the development infrastructure framework, QA infrastructure framework in details.

The concept of server architecture is depicted in the diagram below (for guidance only). The Architecture should
be planned keeping in mind the following design criteria
a) Scalability
b) Solution flexibility
c) Performance
d) Redundancy
e) Business Continuity
f) Investment protection


Figure 1: Schematic representation of Server Architecture (for reference purpose only)

All arrangements for loading/ unloading, movement of the equipment etc. shall be done by the Vendor. All
equipment shall be designed and constructed to the highest standards as well as utilise the most recent and
proven technology regarding reliability, ease of maintenance, safety of personnel and ergonomic considerations.
Each module of the equipment shall be clearly labelled in English, according to its function. Each module shall
include a serial number for identification purposes. All plugs, sockets and cabling shall be labelled in such a way
that it eliminates any ambiguity in locating the matching connectors. All equipment shall operate on 230 volts, 50
Hz using the standard three-prong plug defined in British Standard 546.


2.3. installation & commissioning of Networking Components
For running the intended application as mentioned in the scope, the Vendor shall design, install and commission
the network infrastructure including but not limited to the following. The network shall be designed to meet the
user workload and performance requirements without single point of failure. The Vendor shall submit the
designed network architecture and network drawings to the Owner for validation, before commencing installation
and commissioning.

Local Area Network
a) Network cabling comprising of but not limited to UTP & Fiber Optic.
b) Data Center sites Gbps UTP connectivity between various components like core switch, firewall etc.
c) Total Fibre Optic cable layout of approximately 7.5 km. There is existing FO Cabling of approx 3 km from
Service Building to Warehouse through Time Office, Service Building to Control Room and Service Building
floors. Of this Service Building to Warehouse shall be used as redundant path between the distribution
switches. Additional Fiber Optic cable layout for approximately 4.5 Kms is required from Data Center to
Service Building, Data Center to Ware House, Service Building to CHP & WTP, and Warehouse to MGR.While
considering the above, use of existing FO cabling should be considered to the extent it is technically
compatible..
d) Total network of UTP connectivity is approximately 5.5 kms. There is existing internal network of UTP
connectivity of approx. 3.5 kms of Service Building, Control room and Head Office (Bhubaneswar). Additional
UTP connectivity for approximately 2 Kms is required from access/ distribution switches to nodes at Coal
Handling Plant (CHP), Merry Go Round (MGR), Water Treatment Plant, and Warehouse Sheds shall be
required. While considering the above, use of existing UTP connectivity should be considered to the extent it is
technically compatible.
e) Design & installation of high availability Core switches.
f) installation of Two Nos of Distribution switches at Service Building & Warehouse of IBTPS and One no of
Distribution Switch at Head office Bhubaneswar. The old core switch at IBTPS shall be configured in Active
Active mode as fall back arrangement with one of the distribution switch.
g) installation of access switches ( No of Access Switches required shall be suggested as per detailed design
proposed by Vendor)
h) Termination and connectorisation of all fibre and UTP connections.
Wide Area Network
a) The Vendor shall procure and implement WAN connectivity at Owner.
b) The Head Office at Bhubaneswar shall be connected with the primary site at IB Thermal Power Station (ITPS)
through two separate 1 Mbps links in load sharing mode.
c) All the links shall be from separate service providers on separate network backbone.

Internet connectivity requirements
a) The Vendor shall procure and establish internet connectivity at Owner.
b) Internet link should be a 2 Mbps (Upgradeable to 10 Mbps) lease line with 2 Mbps online backup link.
c) Internet connectivity should be from two different service providers. One link should act as online backup.
Quality of Service should be configured to prioritize traffic for optimization and efficient utilization of links.

Storage Area Network (SAN)
a) The storage area network should be designed and implemented keeping in mind Owners requirement of high
availability and based on high availability architecture.
b) The entire SAN solution needs to be implemented comprising but not limited to components for SAN
connectivity and SAN storage. Vendors should ensure availability of the following
I. Details of Fiber channel SAN connectivity with appropriate topology (point to point, arbitrated loop
etc.) for connection keeping in mind Owners needs.
II. Documentation on topology used, ports used, backup policy, maintenance guide.
III. Details of proposed login mechanism for FC login (port, process, fabric etc).
IV. Routing mechanism for the fiber channel along with necessary algorithms name.


V. Details of Layout and commissioning of entire cabling for SAN.
VI. Details of the regular backup devices to be configured and deployed.

Network Management System (NMS)
a) NMS as a part of Enterprise Management System (EMS) should be capable of providing network management
services for all integrated network elements (existing as well as new).
b) The major services to be provided by NMS should be fault management, configuration management,
performance management, accounting Management and security management.
c) The monitoring of the NMS shall be located in the Network Operations Center in the Data Center.
d) LCD monitors 42 shall be installed on the IT floor for monitoring the WAN & LAN network status.
Security
a) Appropriate security architecture is to be recommended considering authentication and authorization services,
appropriate connectivity e.g. VPN / Dialup / Internet, proxy / firewall services, etc
b) Provide an intermediary between an external end-user/system on an external network and the Owner internal
systems on the Owner internal networks.
c) Allow only certain ports and/or protocols and block internet access to specific sites/systems.
d) Firewalls in Data centre shall be configured with failover for high availability. External networks shall be
connected to Owner network through a firewall. The entire traffic at interface points needs to be monitored and
a traffic log needs to be maintained.
e) Intrusion Protection System (IPS) including Denial of Service (DOS) detection should be used to monitor and
control any malicious traffic to and from internet, Data Center, DMZ etc.
f) Proxy servers should be used to distribute and log internet usage and block access to prohibited sites.
g) The Vendor should conduct a Vulnerability Assessment (VA) & Penetration Testing (PT) exercise form an
independent agency for all the Servers and critical network equipments and submit the report to Owner.
Vendor would take appropriate counter measures to close the reported issues and submit a detailed report.
On successful installation of the equipment and configuration of individual components and the solution as a
whole, the Vendor shall submit the following as part of the commissioning:
h) Configuration details for each server name, IP address, OS version, details of disk partitioning.
i) Network diagrams/ cabling scheme.
j) Cluster details.
k) Details of SAN access, snapshot copy, etc.
l) Details of Tape Backup systems.
m) Administrators Manual for Servers, SAN, back-up solution and network.
n) Line Diagram, details of various LANs, VLANs, and SANs etc.
o) IP addressing scheme

The OEM should provide service, spares support to Owner or Owner designated agency during Warranty period
and subsequent AMC period. Generic Specification of the network layout is provided in Table-04 of Annexure-1.
The concept network is depicted in the diagram below (for guidance only). The Network Architecture should be
planned keeping in mind the following design criteria
a) Scalability
b) Solution flexibility
c) Performance
d) Redundancy
e) Business Continuity
f) Investment protection


Figure 2: Proposed Network Architecture (Schematic) for reference purpose only
2.4. installation and commissioning of Video Conferencing & IP Telephony
The Vendor shall design and implement suitable video conferencing solution that shall connect the conference
rooms at Head Office, Bhubaneswar and IB Thermal Power Station (ITPS) with other national and international
offices. The solution should have the ability to participate in conferences originating from outside the county via an
IP or ISDN gateway connection. The details requirement is given in Table-05 of Annexure-1.


The Vendor shall design and implement suitable IP Telephony solution for Owner. The solution should be
designed to dial up or receive call from international offices across the globe. The details requirement is given in
Table-06 of Annexure-1.
3. Implementation of the SAP applications
3.1. Conducting Business Process Study
The Vendor will be required to study the business processes, which would be covered by the implementation.
Owner will validate this list and suggest suitable changes as may be necessary. Based on the agreed business
process coverage of the implementation, the Vendor will:
a) Conduct a detailed Business Process Study and propose process changes/improvements that would be
facilitated by / necessitated in the solution.
b) Identify the workaround solutions / customizations / interfaces to be developed as part of the implementation.
c) Identify information / Reports requirements for each business process.
d) Identify data conversion elements for each business process.
e) Identify the legacy systems that may be retained.
The Business Process study will enable the project team of the Vendor to get first hand understanding of the
business processes at Owner. It would also help them understand the specific role played by each module /
system and identify systems, which would be retained or scrapped, post implementation of the solution. It would
also enable the Project Team to see the system in operation, collect sample transactions / reports and get a
better understanding of the business process.
3.2. Mapping of Business Processes as per Business Blueprinting
Vendor has to design the relevant business processes with all details. This effort shall have the following
important tasks:
a) AS-IS process mapping to activity/ task level and current state analysis to identify areas of improvement and
opportunities for standardization.
b) Review the AS-IS processes and define TO-BE processes that are based on business requirements, GAP
Analysis and SAP enabled best practices processes.
c) Designing of the specific screens and data formats along with the process and method for entering the details.
Process Improvement will be done to enable Owner to adopt some of the best practices embedded in the SAP
systems. The areas that can bring maximum benefits will be identified by Vendor in close coordination with Owner
process Owners. In order to do this, Vendor will also bring in knowledge of the best practices adopted by other
world-class organization to the Owner implementation. Vendor shall associate in identifying KPIs for Owner and
share benchmark data with Owner team so that their relevance in terms of best practices in the industry can also
be ascertained. This in turn will help the implementation team to set up these KPIs in the system. The KPIs
relevant to Owner will thus be identified and made to report through BW of the SAP system. Owner envisages
that the proposed process improvement and process re-engineering is SAP-enabled. This will enable early
completion of the implementation and will also avoid any major re-work. Accordingly process improvement
exercise will be an integral part of implementation and the Project Plan for the same will be detailed as part of the
overall SAP implementation plan.
3.3. Conceptualizing, Developing, Configuration and Testing the Solution
The design proposed by Vendor, shall be realistic, simple, flexible enough to take care of future changes in the
organizational structure and easy maintainability. The Vendor will be responsible for the following;
a) Conceptualizing and developing the solution based on the business blueprint


b) Identification of the fields that need to be captured for the Masters and mapping of the information with the
legacy systems
c) Configuring the SAP system according to the processes as well as configuring the solution including
development of necessary interfaces, bolt-on / third party applications etc.
d) Integration of the detailed design across modules.
e) Developing the Reports requirements as identified in the Business Process Study for each business process.
f) Conducting Conference Room Pilot Test & User Acceptance Test and making necessary changes to
configuration / setup based on the test results.
g) The SAP implementation at Owner is to be audited/ monitored in continuous basis by SAP India for ensuring
smooth and timely implementation as per the requirement of Owner.
While developing and configuring the system, the following features essentially, but not limited to should be
considered.

User Interface
The end user interfaces should be both web interface (wherever applicable) and Graphic User Interface (GUI)
based. Wherever possible, data should be available for entry from a drop-down list. There should be field level
validation of the data being entered. In case of an error in data type, the error message should be customized to
Owner specification. It should be possible for the system administrator to restrict certain values for entry to
specific users (e.g. account codes). It should also be possible for the users to retrieve data entered incorrectly
and change the same subject to defined security procedure.

Single Point Data Entry avoiding Duplicate Data Entry
The system should be capable of reusing the data once captured in the computer, so as to ensure integrity of
data. The system should be able to automatically capture data from other legacy / process control systems
through integration .There should be a single set of data which once created should be available for use by all
users, thereby eliminating the need for multiple data entry and ensuring data consistency across the system. This
applies not only to the transaction level data but also to all master data, which may be shared across functions.
The system should support capture and storage of statutory documents like invoices, LR/ RR, etc. as part of
transaction for avoiding duplicate copies of such documents and access by all concerned from a single source.

Centralized / Common Master Data
The solution envisaged by Owner assumes a centralized master data repository to be shared by all the units
based on their requirements. These master data would include but not be limited to the following:
a) Chart of Account values
b) Item / Service Master
c) Vendor Master
d) Customer Master
e) Fixed Assets Category Master
f) Employee Master
g) Equipment master

Accounting Architecture
There should be only one instance of the financial module of the SAP and all units should work on the same.
System should be capable of generating consolidated as well as unit wise cost/financial accounts/reports with
sub-ledger option. This should not, in anyway, compromise the operational flexibility, security and data access
that each unit currently enjoys. Since Owner expects that all units will work on the same instance of the SAP,
consolidation of accounts should be a system driven process with minimal human intervention. It should be
possible to maintain multiple instances of accounts for supporting its subsidiary units, employee provident fund
trust, cooperative societies, etc. from the same and single instance of the application. The system should give
flexibility for maintaining the dictionary of old chart of accounts and map it with the new scheme supporting
merger and/or splitting of old accounts.

Enabling Centralized Procurement


Owner expects the SAP to facilitate system driven consolidation of purchase requisitions raised across units into
centralized purchase orders. In other words, different units could raise purchase requisition for the same item or
on the same vendor which should get consolidated into a single Purchase Order. The SAP should also enable
recording of rate contracts with specific vendors for specific items such that as and when purchase orders are
raised on those vendors for those items, the rate will default automatically. E-Procurement (comprising of e-
Tendering and e-auction) application will be a part of the procurement solution in future as per the IT Strategy.

Data Access and Security
Owner believes that ensuring security of data in SAP environment is critical. This assumes greater significance in
an organization like Owner where the number of users will be very high and access will be across a wide area
network. Owner expects that there will be 150 named users, 1 development users and 400 self service users. The
system must have proper security and maintenance facility which limit access to the system and its various
functions to the users delegated with appropriate authority. It should provide log in, both by user and by terminal.
The System should record date and time stamp of all transaction with details of creation, read, update, delete or
print. Access should be restricted at different levels of data file, program, module, screen, record, field database
table, row or column. Suitable firewall against unauthorized use, interceptions shall be provided. IT security policy
shall be given by the Vendor to safeguard information against unauthorized use, disclosure or modification,
damage or loss.

Data Archival
In order to meet statutory requirements, archiving and easy retrieval of data is important for Owner. The Vendor
must ensure that the proposed SAP Solution provides a user driven data archiving capability, with support for
flexible archiving periods and select Tables. The system should also be able to restore archived data for on-line
inquiry and reporting as and when required. The Vendor will also provide a data archiving procedure based on
best practices.

Audit Trail
The Vendors must ensure that the SAP Solution implemented by them has extensive facility with respect to
maintaining audit trail. The system should be able to define audit trails, audit logs and transaction log-in
requirements. It should enable audit trails on-line, tailor audit requirements by modules, call audit records to an
archive based data or other recorded audit details. Any addition, deletion or modification to an existing record,
whether master or transaction, must bear the date and time stamp, the name of the log-in user who made the
change and the terminal from which the change was made. It should also be possible to maintain details of the
original record and subsequent changes to the same. Standard audit related reports should also be available.

On Line Help Facility
The SAP Solution should provide context based online help capability for every form /process. This on-line help
text / facility should be customizable to make it Owner processes specific. The Vendor must indicate how he
proposes to make the online help tailored to Owner requirement.

Availability of Interface Points
The SAP Solution should have well defined standard interface points to facilitate integration with satellite
applications to interface transaction and master data. This is crucial in Owner context as some of the Owner
specific satellite/legacy applications might have to be retained.

Workflow Based Applications
Owner expects the proposed SAP Solution to provide workflow-based functional capabilities. SAP Solution should
be capable of replacing the current physical flow of documents across business team with the flow of electronic
data. For instance, if purchase requisitions require approval based on the item or service being procured, then the
workflow in the SAP Solution should forward the link of a purchase requisition electronically to a user/approver
based on the criteria defined by Owner.

Modularity
Owner expects the proposed SAP Solution to be modular in nature. The system will initially be required to cover a
range of business process modules as mentioned above but it should allow addition of more modules as and
when required, which should seamlessly integrate into the core system without encountering any technical issues.


Integration between such modules and the modules already implemented should be seamless and should not
require any development effort.

Scalability
The SAP Solution being implemented by the Vendors must be scalable both in terms of the business rules,
volume of transaction and master data but also in terms of defining new entities and organization structure.
Solution scalability is particularly important given the expansion projects underway which would increase
production capacity of Owner. The system should be scalable to handle up to four times the number of users and
volume of data load without compromising response time or efficiency of operations.

Localization
Given that the taxes and other statutory requirements change from year to year, Owner expects the SAP Product
vendor to provide updates / patches to cater to these changed India specific statutory requirements within an
acceptable time-frame. The system should have adequate localization to handle specific requirements of
Companys Act and Cost Accounting guidelines as per ICWAI, Regulatory Indian Laws (Central and State), tax
and duty legislation and other regulations.

Enhancements, Upgrades and Bug Fixes
Owner expects the Vendor to arrange for providing support for all future enhancements, upgrades and bug fixes.
All Vendors are expected to provide description of the mechanism proposed for provision of the same. If these
require additional costs, then this must be clearly indicated along with the Time and Material rates.

System Architecture
The Vendor shall be entirely responsible for the architecture of the system implemented to satisfy all features,
functions and performance as described in this document. The System architecture shall be developed as per
following guidelines:
a) The system architecture should be based on open industry standards and protocols.
b) The system will be centrally deployed and globally accessed. Access should not be restricted locally.
c) The application design should be Service Oriented Architecture (SOA) based for all environments.
d) Client applications, if any, should be J ava/XML/HTML based thin client architecture with centralized
deployment capability.
e) All production application must have high availability.
f) All systems must take into account appropriate security, performance, efficiency and maintainability issues.
g) The system must be designed in such a way that it supports load balancing of the application, presentation
and data layers of the system.
h) Integration services should address requirements of integration for application to application and data
integration.
3.4. SAP Application installation
It is proposed to implement following modules of SAP ERP package for Owner at its plant site and Head office as
a uniform Business IT solution. The application shall be installed for development, quality and production
environment. The production instance shall be independent and shall not share resources from any other
instances.
a) SAP Financials & Costing(FICO)
b) SAP Human Capital Management(HCM)
c) SAP Materials Management(MM)
d) SAP Plant Maintenance(PM)
e) SAP Asset Management(AM)
f) SAP Project Systems(PS)
g) SAP Environmental Health & Safety(EH&S)
h) SAP Quality Management(QM)


i) SAP Analytics (BI)
SAP Strategic Enterprise Management (SEM)
Financial Analytics
Operational Analytics
Workforce Analytics
j) Employee Self Service(ESS)
k) India Payroll(PAYROLL)
l) Country India Version(CIN)
In order to support the prime functions, the SAP system shall also cover the following. However during the study
of the SAP modules to be implemented, if the need for any other module is felt, the same shall be considered for
implementation.
m) Contracts Management
n) Dashboard for Senior Management
o) Document Management (DMS)
p) Workflow Management
q) Knowledge Management(KM)
r) Content Management(CMS)
s) Web portals
3.5. Data Migration
All specifications that are needed to populate the data into the new SAP system need to be defined. Vendor, with
the assistance of Owners Core Team, shall develop the templates and facilitate the migration of legacy and new
data elements to the SAP system. This shall include the following tasks:
a) Formal data migration training and facilitating the Owner core team
b) Assistance in Checking data quality and Integrity
c) Identification & development of the data upload/download programs
d) Guidance for creating data extraction programs in the legacy systems to convert into the format as required by
SAP
e) Providing data migration tools to Owner
f) Integration testing of the configured system using the populated master and transaction data
g) Assist Owner team in Master Data management.
The Vendor is expected to prepare and submit a high level Data Conversion and migration Strategy Document
during the process study stage of the project describing the broad data elements to be converted, cleaned,
enriched, identify source for the same, the target SAP module and the detailed form in which the same will be
converted (i.e., whether at transaction level or at balance level and the coverage period). A tentative time-frame
for developing the necessary scripts, testing and validating the same and eventual execution on the Production
environment should also be indicated. Vendors responsibility shall be to ensure that data migration is complete in
all respects, within time so that the requirements of the implementation are fulfilled. Owner shall cleanse and
rationalize the data in the required format provided by the Vendor with their assistance. Vendor shall prepare and
provide detailed system for Master Data management.

Owner expects Vendor to commence activity on the data conversion from the early stage of the project to prevent
any kind of delay in implementation of overall project. Owner will extract and provide data required from identified


existing applications at Owner .Owner acknowledges that the responsibility of efficient data conversion lies with
the both, the Vendor and Owner. In this regard, Owner expects the Vendor to:
a) Identifying data elements- Masters and Transactional to be converted and migrated
b) Extraction of existing data from the identified legacy systems with Owner assistance
c) Collection of data from other identified sources with Owner assistance
d) Owner will provide assistance in cleansing, enriching and formatting of data extracted from the legacy systems
e) Formatting of data collected from other sources
f) Preparing and validating data mapping structure
g) Preparing data migration scripts
h) Running successful trial data migration
i) Uploading of data to the new test and production system
j) Reconciliation and validation of migrated data and status of transactional data
k) Creation of new/additional data mandatory in the new system

Figure 4: Data Conversion Process Steps

The following data need to be migrated (the list may not be exhaustive and could enlist few more data types
depending on requirements)

a) Opening & Closing balances for the last five years.
b) Specified Transaction data of the last five years.
c) All open transactions and all transactions from the start of financial year of Go-live.
d) Standing or master data such as vendors/Suppliers, customers, material, work breakdown structures,
equipment, preventive maintenance, work specification, defect codes, cost data, etc.
e) Production Statistical Data
f) Further to past 5 years Legacy data migration, important production statistics since inception such as
production of main items, performance parameters are required to be migrated to meet requirements of audit
and other queries.
Legacy
Applications
ERP
Production
Environment
Data
extracted
Data
Cleansed /
formatted
Data added Data
Signed off
Data
Conversion
Tested
Data
Conversion
executed
ERP Test
Environment


3.6. Go-live and Stabilization Support
Vendor is required to undertake the following for final preparation and Go-live at the Owner premise:
a) Review readiness for cut over
b) Facilitate in setting up central help desk for any queries
c) Resolve Technical & functional related issues
d) Define the requirements towards the phasing out of the legacy systems
e) Documentation of the issues/ problems that come up and solutions thereof.
f) Final configuration/ integration, volume and stress testing
g) Switch over to production environment
h) The Vendor should obtain a certificate / validation from SAP Product Vendor mentioning that the Solution is fit
for go-live.
Vendor shall be responsible for Project implementation and correct & satisfactory functioning of the SAP system.
Vendor shall provide post implementation support to the Owner to ensure the efficient day-to-day functioning of
the system for a period of six (6) months from Go-live. The full implementation team should be there on site
during stabilization period. In addition, Vendor shall extend their support during the First quarterly, half yearly,
nine monthly and annual closing (7 days for each). Vendor shall also review the health, usage and performance of
the SAP system till it stabilizes.
Vendor shall provide guidelines in setting up and managing a SAP Helpdesk including the processes to be
followed in logging request for assistance, assigning requests to specific helpdesk individuals, recording
resolution and tracking overall time frame from logging a call to its resolution. The help desk support to users shall
be provided on 24 x 7 bases. Vendor response time will be the basis for end-user support response time in
Owners service level agreements with the Vendor. The Vendor will follow response time as detailed below:

Support
Category
Criteria Maximum
Response
Time
Resolution
Critical The system is unable to be used for normal business
activities. There is certainty of financial loss to Owner.
30 Minutes 90 Minutes
Urgent There is a problem with part of the system, which
impacts on Owners decision making. No viable
workaround is available. There is a likelihood of financial
loss.
1 Hour 4 Hours
High The efficiency of users is being impacted, but has a
viable workaround.
4 Hours Next Release based on
SAP Confirmation
Medium A low impact problem that affects the efficiency of users
but has a simple workaround.
SAP Confirmation
Low A fault, which has no particular impact on processing of
normal business activities.
SAP Confirmation

4. Implementation of the Non-SAP applications
The following non SAP applications & software shall be implemented by the Vendor
4.1. Acti ve Directory Implementation with SSO
Vendor shall design and implement Active Directory Structure in the organisation with Single Sign On (SSO).
Active Directory (AD) Management shall provide master operations, replication, DNS, monitoring/ mapping


capabilities for all sites of Owner. AD Management shall inform the operator of Active Directory-related conditions
occurring across the network on the following:
a) Data is consistent across all Domain Controllers
b) Replication is successfully completing in a timely manner
c) Systems are able to cope with outages
d) Active Directory is not experiencing capacity and fault-tolerance issues
e) Active Directory global catalogue is replicating in a timely manner.
f) It shall include policies for service monitoring, a tool for mapping replication connections among domain
controllers, and reports and graphs for consolidating and charting the collected data.
g) It shall provide policies to control the monitoring schedule and receipt of collected information in the form of
service problem alerts and messages.
h) AD topology viewer shall be provided for viewing the content and topology of AD domains and sites.
i) AD topology viewer shall generate a tree showing the AD components as well as graphical map that shows the
DC replication connections.
j) Active directory set up shall be done to the policies uniformly and regular patch updates.
k) Support of Lightweight Directory Access Protocol (LDAP) to allow systems access to the directory.
l) Support single sign-on.
4.2. Messaging and collaboration solution
The Vendor shall design and implement a high availability mailing solution for Owner users at Head Office and
ITPS site. The details requirement is given in Table-07 of Annexure-1. The e-mail solution must be compatible to
SAP environment and should be integrated with SAP for sending notification/ alerts etc. The mails system should
be integrated with Black Berry Enterprise Servers.
4.3. Anti-Virus / Anti-SPAM / Content Filtering Solution
The Vendor shall design and implement a comprehensive security solution for the entire system including suitable
Antivirus and Anti-Spam solution for all PC and Laptop users as mentioned in Table-08 of Annexure-1. All the
system and servers should be configured with Antivirus software to detect malicious software like Viruses, Worms,
and Trojans etc and protect the system.
4.4. EMS/ NMS and Service Desk
The Vendor shall design and implement suitable Enterprise Management System (EMS)/ Network Management
System solution to be deployed at the Data Center for centralized monitoring of Servers and Network as
mentioned in Table-09 of Annexure-1. The Vendor shall provide suitable service desk application at Owner. The
application shall be ITIL compliant and support the following function and processes.
a) Help Desk
b) Incident Management
c) Service Level Management
d) Problem Management with Known Error Database (KEDB)
e) Configuration Management with Configuration Management Database (CMDB)
f) Change Management
4.5. BMS for Data Center
The Vendor shall design and implement suitable Building Management (BMS) solution for centralized monitoring
of the Data Center mentioned in Table-10 of Annexure-1.

Important features desired from BMS are:
g) SMS Alerts for Alarm on GSM Mobile Network
h) E-mails in the event of Alarm
i) Atleast 20% Spare Capacity shall be kept while designing the configuration for Direct Digital Controllers for the
scope mentioned. The 20% spares shall be applicable all types of inputs & outputs.
All equipments and the interface points of Data Center should be covered in BMS based on the design approved
by Owner.


4.6. Video conferencing and IP Telephony
The Vendor shall implement video conferencing and IP telephony software applications in the installed video
conferencing and IP telephony systems as per the specifications provided in Table 05 and Table 06 of Annexure
1.
4.7. Implementation Stabilization Support
Vendor shall be responsible for correct & satisfactory functioning of the Non SAP systems implemented. Vendor
shall provide post implementation stabilization support to the Owner to ensure the efficient day-to-day
functioning of systems till the end of stabilization support. The full implementation team should be there on site
during stabilization period. Vendor shall also review the health, usage and performance of the systems till it
stabilize.

5. Project Management in different Phases, Change Management and Training
5.1. Project Management
Design and develop the Project Plan
The detailed Project Plan for the implementation is to be prepared at the commencement of the project. The
implementation of the Project as per the scope will require a strong program management activity integrating the
core product implementation with software application. This ensures complete acceptability of the solution within
the organization. Program management services shall aim at constantly improving the business processes,
leveraging technology solutions, incorporating best-of-breed industry practices to maximize opportunities for
Owners business operations and at the same time addressing growth and development of the employees.

Project Organisation
To build up an effective project team, Owner suggests that an initial formal project organisation structure be
created as part of the Planning Phase of the SAP implementation project. This must be so designed as to ensure
that the project runs to plan and delivers Owner's project objectives. The specific project organisational structure
and team roles and responsibilities will be defined by the Vendor to provide the optimal outcome to Owner. The
Project implementation team shall comprise of members from Vendor. Owner shall make available its
implementation team which shall work in association with the above team for assisting and to ensure proper skill
transfer. Owner requires Vendor as the Lead Member to exhibit how they will effectively manage, control and
contribute to the project. As a minimum criterion set up by us, Owner Vendor has to fulfil the following roles in its
project team vide its own manpower:
a) Project Director cum Program Manager.
b) Project Manager.
c) Functional and Technical Leads.
d) Functional and Technical Team.
e) Power utility Industry expert(s).
f) Other project roles such as process improvement, change management, training etc.

Project Office
The Project will be executed from a suitable location (Project Office) within Owner premises, from where the
Vendors project team will operate. All activities of the project including Process documentation, development,
configuration, testing etc. will be carried out from the Project Office. Visits to various departments / locations
within Owner will be made as and when required.

Project Reporting
The Vendors should describe the proposed project reporting methodology. At minimum, the Vendor should submit
to Owner a written progress report every week. The frequency may be increased during critical phases of the


project. In addition, the Vendor shall report on a continuous basis exceptions and issues that require immediate
attention of Owner.
The Vendor will be responsible for appraising the Steering Committee about progress of the project during
Steering Committee Meetings to be held at interval of around one month. The date and time of the meetings will
be finalized from time to time.

Documentation
Vendor shall ensure preparation of complete documentation of all configuration settings, other activities, steps /
stages involved in the implementation with the support of the Core team. Vendor in close coordination with
Owners core team shall prepare the business process document, end-user manuals and training documents in
the jointly agreed templates.
5.2. Organization Change Management and Training
The purpose of Organization Change Management is to ensure that Owner achieves the expected results from its
investment in SAP technology in a short span of time. As part of this service, Vendor will work closely with
Owners SAP core team in introducing the change-processes, stressing the importance of organizational
alignment, and introducing the necessary tools and techniques needed to address issues in the Organization. The
Vendor will suggest to the Owner Project Management Team issues anticipated in the change management
process and proposed solution to overcome the same. The Vendor is expected to conduct the change
management programs on one-on-one individual basis or in groups and at different locations.

Vendor shall conduct a training need assessment of Owners SAP core team members as well as power users/
end-users as a component of the process improvement and change management process. Training needs should
be continuously refined and frequently reconfirmed with the end-user community & the core team as the project
progresses. Additionally, the Vendor will do the followings,
a) Provide a description of the approach and tentative plan for training Owners core team members and end
users along with the tentative time frame;
b) Separate training programs will have to be organized for separate categories of users (e.g. core team
members, senior management, middle management, junior management, non-executives, system (IT) team,
etc) and for separate geographic locations.
c) The Vendor will be responsible for the preparation of the training material and end user manuals. End user
manuals should cover how to use concepts for all SAP modules to be implemented.
Use of recommended SAP training tools / software(s) for providing various training is essential. Adequate training
material which includes training manuals, quick reference cards etc should be provided during the training
sessions. The recommended training material should be in paper & electronic media with courses on SAP
fundamentals, business process overview, job activity training, and delivery options being on-line, CBTs,
instructor led class rooms, etc.
The following is a brief description of the training needs of the important (but not exhaustive) categories of users:
Core Team Training
Owner Core Team will comprise of representatives from different functions at Owner. This Core Team will
comprise of members from all the Business Functions and IT. This training should enable the SAP core team of
Owner for setting up of SAP Competency Centre and to involve in SAP implementations which are within the
scope, building and managing SAP related skills and maintain the SAP system in Banharapalli.

Technical Core Team
Owner Technical Core team will comprise of team having expertise in performing roles for the Application portfolio
of Owner, Database Administrator, System Administrator, Report Writers, Interface Developer, Data Conversion
Script Writers, any Customization development, security management etc. These representatives will bring with
them knowledge of existing applications, interfaces, constraints, information requirements etc. The SAP training
needs of Technical Core team members will be in areas such as BASIS, ABAP, database administration, system
configuration, report customization, operating system, security management etc.


End User Training
Owner End Users will be the users from different functions, which are covered by SAP implementation or are
likely to be impacted by the SAP implementation. These users will need to be trained before going live on SAP.
Comprehensive guidelines on how to accomplish tasks in Owner specific SAP solution must be provided to these
users. Sign-off by the end users about their comfort level will be a key parameter to be considered by the
Management in giving the go-ahead for cut-over.

Training for Non SAP applications and infrastructure
Vendor shall provide the following trainings for all the applications, tools, Data Center Management, hardware and
Network management implemented as per scope.
a) Extensive administrative training to core technical team
b) Systems training for Non SAP applications and tools, information security etc.
c) Service Desk related processes aligned with ITIL for Help Desk.
d) The Vendor shall provide training materials, system manual both in hardcopy and soft copy
6. Post implementation Support Services for running SAP Applications, Non-SAP
Applications and Infrastructure Facility Management Services.
Considering Owners strategy of outsourcing the IT Operations, the vendor shall provide extended post
implementation support for running the SAP Applications, Non-SAP Applications & Infrastructure and providing
facility management services to Owner for a period of 48 (Forty eight) Months from the date of Final Acceptance
of the Project. During this period, the Vendor shall ensure trouble free running of the entire system implemented
as per the scope of work, broadly covering the following areas. While considering the scope outlined below, the
Vendor shall ensure that there is no overlapping of services as covered under detailed scope of services under
performance guarantee / warranty as per clause 10.4 of the Agreement.

1. SAP Application Support which includes but not limited to the following
a) System Administration
b) Database Administration
c) User Management
d) Backup & Restore
e) Development Support

2. Support of Non SAP Applications.
a) System Administration
b) Database Administration
c) User Management
d) Backup & Restore
e) Development Support

3. Infrastructure Support and Facility Management which includes but not limited to the following
a) User Helpdesk
b) Data Center Management
c) Servers Administration
d) Network Administration
e) Information Security Administration
f) Asset Management
g) Change Management
h) Configuration Management
i) Service Level Management
j) Capacity Mangement
k) installation and maintenance support on applications, hardware and network.

4. AMC of hardware & Network Components
a) Periodic preventive maintenance as per the recommended schedules.


b) Repair / Replacement of hardware and other supplier items inclusive of all types of spare parts
including batteries, plastic parts, sprockets, glass items, Picture tubes, Print Heads, etc. Only
consumables like printer ribbons, Ink cartridge, etc. are excluded.
c) installation / Re-installation / Maintenance of OS, System software and other supplied software.
installation of system software, patches, upgrades, service packs etc.

The post implementation support services should include but not limited to the following
a) System Management:
i. Monitoring, logging and reporting of the equipment operation on 24 x 7 x 365 basis.
ii. Periodic health checks of the systems and implementing proactive rectification measures.
iii. Troubleshooting Servers, OS, SAN and backup related issues.
iv. Analyzing and reporting all system related issues.
v. Managing user, roles and passwords of all the relevant subsystems, including, but not limited
to servers, OS, storage, applications etc.
vi. Liaison with various vendors, OEMs, agencies and service providers for equipment
maintenance & related work.
b) Server Administration: Server Administration Functions include following activities.
i. Operating System administration and tuning.
ii. OS and software re-installation in the event of system crash/failures
iii. Configuring file systems, volumes and apportioning disk space.
iv. Ensure proper configuration of server parameters.
v. Periodic system performance tuning.
vi. Addition, deletion, re-configuration of devices, additional users and printers etc.
vii. Implementing security patches on servers at all levels.
viii. Orderly start-up and shutdown of servers as per laid down procedures.
ix. Security management Configuring account policy, access rights, password control as per
Owners security policy.
x. Ensure all critical services are running properly on the servers. Schedule and optimize these
services.
xi. Maintain lists of all system files, root directories and volumes.
xii. Resolving all server related problems.
xiii. Escalating unresolved problems to ensure resolution as per the agreed uptime and
performance requirements.
c) Performance Monitoring and Reporting
i. Ensure regular monitoring and maintain a log of the performance monitoring of servers
including but not limited to monitoring CPU, disk space, memory utilization, I/O utilization,
Central Storage etc.
ii. Ensure regular analysis of events and logs generated in the entire sub systems including but
not limited to servers, operating systems, databases, applications etc. The system
administrators shall also ensure that the logs are backed up and truncated at regular intervals.


iii. Undertake appropriate actions in accordance with the results of the log analysis to ensure
optimal performance.
d) Storage Administration
i. Management of storage environment to maintain performance at optimum levels on a 24 x 7
basis.
ii. To ensure that Owner is able to take regular and proper backups of all Servers & Storage to
protect against data losses.
iii. Management of the storage solution including, but not limited to, management of space,
volume, RAID configuration, configuration and management of disk array, SAN fabric /
switches, tape library etc. as per mutually agreed storage management policy.
e) Backup and Restore
i. 24 x 7 support for file and volume restoration requests.
ii. To help Owner in regular Backup of operating system, database and application as per
stipulated policies and time schedule.
iii. Help Owner in conducting periodic restore operations on backed up data.
iv. Assist in backups of volumes, files and database applications whenever required.
v. Real-time monitoring, log maintenance and reporting of backup status on a regular basis. Shall
ensure prompt problem resolution in case of failures in the backup processes.
vi. Regular maintenance of all the media and the backup/storage devices.
vii. Provide MIS reports such as weekly reports on backup and restoration (failed reasons),
monthly report on planned backup & backups actually taken and Quarterly report on number of
restoration drill performed and percentage of success, health status of media and drive.
f) Network administration, Security & monitoring
i. 24 X 7 support for all the network and security related infrastructure
ii. Configuration of routers, switches and other security appliances ensuring backup of
configuration of all network devices.
iii. Trouble shooting routers, switches and security devices viz. firewalls etc.
iv. Analyzing and reporting all network related issues.
v. Real time monitoring, and reporting of status on regular basis. Shall ensure prompt problem
resolution in case of failure of hardware.
vi. Online updates of virus definitions, signature database etc.
vii. Regular update of software patches provided by OEMs.
viii. Monitoring of VPN, measurement of internet and VPN bandwidths on regular basis.
ix. Uptime measurement of different outstation VPN circuits.
x. Tuning of network parameters to ensure response times.
xi. Responding/resolving the network related problems as recorded/monitored through Enterprise
Management System/Network Management System.
xii. Trouble shooting and resolving all passive component related problems including OFC system.


T Ta ab b l l e e- - 0 01 1: : Techno-Funct i onal Requi r ement Spec i f i c at i ons
Sr.
No.
Requirement specification
Priority
C-Critical
NC-Non-
critical
Vendors Response
Yes /
No Remarks
Data Center Architecture

1
Ability to develop the Data Center architecture following N-Tier
Architecture considering the following components. (Submit detailed
architecture documentation)

1.01 Web Tier C

1.02 DMZ C

1.03 Application Tier C

1.04 Database Tier C
1.05 Database Cluster C

1.06 Data Storage C

1.07 Stoarage Area Network (SAN) C

1.08 Backup Server & Tape Drive C

1.09 Configuration of Private VLAN for different component of Datacenter C

2
Ability to integrate the following applications in the data center
architecture (In the architecture documents please elaborate the
integration)

2.01 ERP C

2.02 Mailing Solution C

2.03 Antivirus & Anti-Spam Solution C

2.04 Active Directory Services C

2.05 Enterprise Management System (including NMS, Service Desk etc.) C

2.06 Building Management System C

2.07 VPN Client Access C

2.08 Video Conferencing & IP Telephony C

3
Separate environment for Production, Development and QA for all
applications. (In the architecture documents please elaborate these
environments)
C

4
Ability to provisions for flexibility, scalability and investment protection
(Please also refer the scalability requirement in Data Center Design)
by adding physical boxes
C

5
Provision to accommodate Phase2 ERP Modules and other
applications that will be implemented in future. (Submit the plan to
accommodate such expansion)
C

6
Ability to provision for Disaster Recovery of IT applications aligned
with future business need. (See the Disaster Recovery below for
further details)
C

Data Center Design

7
Ability to design the Data Center Layout considering UPS, Gas Bank,
Management Console, EMS, BMS area. (Please provide the data
center layout proposed)
C

8
The detailed Data Center design the following components with
justification

8.01 Server C


8.02 Network Equipments C

8.03 Power Distribution, Cabling, Earthing C

8.04 Illumination C

8.05 UPS & Battery Bank C
8.06 Fire Detection & Suppression System C

8.07 Access Control C

8.08 CCTVs C

8.09 Rodent Control C

8.10 Leak Detection System C

8.11 Data Safes C
9
Integration with available Owner DG Set with Building Management
System
C

10
Designed provisions for High Availability/ Redundancy for different
hardware & devices shall be provided
C

11 Ability of the Vendor to design scalability in the following levels

11.01
The initial configuration recommended should be optimally sized to
ensure the system, at full load, operates at maximum 70% of its
installed capacity.
C

11.02
All servers shall be planned in such a manner that they have
scalability to deliver additional 100% increase in performance over and
above the installed capacity. (Any expansion required by adding
physical boxes shall be addressed at architecture level.)
C

12
The Vendor should propose servers with latest CPU architecture
offered by the hardware provider
C

13
The solution should support software RAID and hardware RAID
Controller
C

14
The consolidated storage should meet all requirements of all solution
areas. The same storage area will be used by all servers in all
environment
C

15
The solution shall be supported on client with Mobile Devices (palm-
Top, Mobile Phones, PDA)
C

16 Built-in hardware service processor for support and diagnostics NC

17
The solution shall support client machine with Pentium IV CPU and
512 MB RAM
NC

18
The solution shall be supported on client with Windows Vista,
Windows XP and Windows 98 SE Operating System
NC

19 The solution shall be supported on client with Linux Operating System C

20 Ability of client to run the entire ERP functions through browser NC

21
The solution shall run on native browser with additional plug-in's that
should be downloaded automatically
NC

22 The solution shall support IE browser and Netscape browser NC

23 Ability to support Thin clients C

Sizing and Scalability
24
The initial configuration recommended should be optimally sized to
ensure the system, at full load, operates at maximum 70% of its
installed capacity.
C

25
The Vendor should design the solution to meet scalability
requirements stated below:


25.01
SAP Production Infrastructure:
- Support current work load of 550 users which should be scalable to
1100 in the next three years.
These users can be categorized as follows:
LAN users - 550
WAN/Internet users - 40
- Support 550 self service users
Messaging System - Support current workload of 250 users which
should increase to 1000 in the next three years.
C

26
The sizing report given by the Vendor should be vetted by the ERP
vendor for the hardware specification.
C

Sr.
No.
Requirement specification
Priority
C-Critical
NC-Non-
critical
Vendors Response
Yes /
No Remarks
Development Infrastructure:
27
Development infrastructure will be needed to initiate and support
ongoing development/ upgrade needs during and post
implementation. The Vendor will recommend and mobilize/arrange the
development hardware/infrastructure framework and details.
C

Quality / Training Infrastructure

28
Quality Assurance infrastructure will be needed for conducting tests
and trainings during and post implementation. The Vendor should
recommend and mobilize/arrange for appropriate QA
hardware/infrastructure framework and details for approximately 30
users.
C

29
Training and Demonstration infrastructure will be needed for
conducting trainings and demonstrations during and post
implementation. The Vendor should recommend and mobilize/arrange
for appropriate training hardware/infrastructure framework and details.
C

Response Time Performance Criteria

30
Ability to provide Response Time Performance Criteria as prescribed
in the Annexure-2 Deliverables and Performance Parameters .
C

Availability Performance Criteria (Uptime Requirement)

100% 100% 100%
100% 100%
200%
0%
100%
200%
300%
400%
70% PL +30%
SC
Expansion1 Expansion2
Architecture level
scalability
Box level scalability
Installed Capacity


31
The System shall have an availability of at least 99.90%. The
availability will be calculated based on the following formula:
C

A =[ { tsh - ( tud - tepd ) } / tsh ] * 100

A: Availability (percent)
tsh: Total Service Hours

tud: Total Unscheduled Downtime (hours)

tepd: Total Excused Performance Downtime (hours)

Total Service Hours are the total available service hours of 24
hours, 7 days a week minus Total Scheduled Downtime

tsh = tah tsd

tah: Total Available Hours

tsd: Total Scheduled Downtime

Total Service Hours are all the Service Hours in the calendar month

Unscheduled Downtimes are where the Production Infrastructure are
unavailable during Service Hours and outside the Scheduled
Downtime.

Total Scheduled Downtime is
(a) planned maintenance, with all such planned maintenance to be
agreed in advance by the Service Provider and Owner.
and
(b) the scheduled back-up windows specified in the operational
procedures manual or as otherwise agreed.

Excused Performance Downtime means the elapsed time for any
outage that is the result of an excused performance problem.

32
The networking and infrastructure requirements to meet the
performance criteria should be specified by the Vendor.
NC

33
Support 100% addition to transaction volume over next three years
based on expansion plans of Owner
NC

34
The Enterprise Management System should be able to measure the
availability of at individual component level and consolidated individual
availability from service availability perspective.
NC

Batch Programs

35
Number of failures while running batch requests should not be more
than 2 per month, with 100% success rate for batch re-run after failure
NC

User Access and Security

36
Appropriate security architecture is to be recommended considering
authentication and authorization services, appropriate connectivity e.g.
VPN/ Dialup/ Internet, proxy/ firewall services, disaster recovery etc.
(Refer Network Architecture sheet)
C

37
Implementing directory services as per Owner enterprise wide
directory services strategy
C

38
Ability to integrate with directory services for authentication and
authorization and support the following features
C

39
Support of LDAP (Lightweight Directory Access Protocol) to allow
systems access to the directory.
C


40
Ability to allow definition of rules for password composition and
password encryption
C

41 Ability to define rules for password's as per Owner passsword policy C

42 Ability to configure the number of permissible log-in attempts. C

43
Ability to handle data updation/ deletion/ creation only through
application layer.
C

44 Users should not be allowed to access the database directly. C

45
Ability to provide a complete audit trail of transactions with time stamp
and user ID stamp.
C

46 Ability to support role based access control C

47
The Solution shall be compliant with the Indian Information
Technology Act.
C

48
Ability to provide access level security for Entry forms at Field level -
allow, Read only, Hide
C

49
Ability providing access level security for Entry forms at Transaction
level - allow / deny
C

50
Allow providing access level security for reports at Field level - show /
hide
C

51
Allow providing access level security for reports at Transaction level -
allow / deny
C

52 Ability to provide authorization by transaction type NC

53 Ability to provide authorization by user name C

54 Ability to provide automatic time out for entry transaction C
55 Ability to encrypt password while passing on wire C

56 Ability to provide automatic time out (log out) for user C

57 Ability to provide terminal soft locking facility NC

58
Ability to support 2 factor authentication for users connecting to ERP
from internet
NC

59 Centralized repository of all identification and access control data NC

60 Single Sign-on Support C
61 Support access control to individual or groups of applications. NC

62
Network Intrusion Prevention System (IPS) should be used to monitor
any malicious traffic to and from internet, ERP center, WAN, DMZ etc.
C

63
Any external connectivity to Owner network applications and any other
external networks should be connected to Owner through a firewall.
NC

64
VLAN's shall be configured aligned with data center architecture,
network architecture and Owner's information security requirements.
NC

65
All the desktops running ERP GUI should be configured with personal
firewall, Antivirus software and a spyware removal.
NC

66 Ability to provide multiple roles for one user NC
67 The Solution should be able to cater to ISO 27001 requirements C

68 Ability to support remote operation of Security Management NC

69 Ability to support remote operation of Diagnostic and Fine tuning tools C

70 Ability to provide time restriction on transactions NC

71 Ability to provide user login with time restriction NC


Back up and Restore

72
The Vendor should provide both on-line and off-line data backup and
restoration capabilities
C

73 The on line back up facility should be possible with all clients working C

74 The Vendor will design and implement appropriate archival policy C

75
The Vendor will recommend and implement appropriate storage
solution
C

76
The solution shall have in built source / application code control
program
C

77 Ability to allow fresh login to ERP during online data back up NC
78 The backup should be completed within 6 hours/night shift NC

79
The solution shall have a built in software to manage typical data
centre like database back ups and restore
NC

80
The solution shall have a built in software to manage application
software back ups and restore Source Control
NC

Disaster Recovery

81
The Vendor should recommend a DR strategy based the recovery
strategy against failure of Servers and SAN, based on RTO (Recovery
Time Objective) of 2 hours and RPO (Recovery Point Objective) Zero
for Synchronous and RTO (Recovery Time Objective) of 4 hours and
RPO (Recovery Point Objective) 30 minutes for Asynchronous.
C

82 The solution shall support DR with asynchronous replication of data NC

83
The solution should support connectivity to the DRS from the end user
system, in case of disaster at the Data Center.
C

84
The DR strategy-infrastructure-processes-organization structure
design should be provided by the Vendor for future implementation
C

85
Please provide detailed recommendations describing the software and
technical architecture of the Recovery mechanism supported by the
Solution.
NC

86
There should not be a single point of failure at the production
infrastructure
C

Network Connecti vity and Internet Service

87
The solution shall have 1 Mbps / 2Mbps connectivity from Site office to
the Corporate office of Owner
C

88 The solution shall have a minimum 512 Kbps backup connectivity . C

89
Internet connectivity should be from two different Service Providers.
One link should act as a backup. QoS should be configured to
prioritize traffic for optimization and efficient utilization of links
C

90
Internet Gateway Security including Content filtering should be done
for web content.
C

EMS/NMS

91
The Enterprise Management System/ Network Management System
should be capable of providing network management services for all
integrated network elements
C

92
The major services to be provided by NMS should be fault
management, configuration management, performance management,
accounting Management and security management
C


93
The monitoring of the EMS/ NMS shall be centrally located in the
Network Operations Centre in the Owner Data Center.
NC

Other Application

94
The mailing solution should be integrated with SAP application for
seamlessly sending the alerts, notifications
C

95 The mailing application should be accessible through web-mail. C

96 The mailing solution should provide the platform for collaboration. NC

97
Videoconferencing solution should be able to dial up other
Videoconferencing facility of the organization across the globe.
C

98
Tool should be able to monitor and manage bandwidth during
videoconferencing without affecting network users of the critical
applications like SAP, Email etc.
C

Training

99 The Vendor should provide ERP Vendor certified training C

100 The Vendor shall provide online help and a Solution Tutorial. NC
101
The Vendor shall provide the training material documentation with the
implemented solution
C

102 The Vendor shall provide CBT (Computer Based Training) software. NC

103
The Vendor shall provide a demo / test solution with dummy data for
user training.
C

104
The Vendor shall provide details of duration of training normally
required (Number of days for Users, Administrators, Technical Support
Staff, etc).
C

Documentation

105 The Vendor shall provide configuration documentation. C
106
The Vendor shall provide Technical Manual suitable for developers
describing the Source Program, Entity Relationship Diagrams,
Requirement Specs, Data Dictionary, etc. for all customized
components
C

107
The Vendor shall provide User Manual describing the necessary
procedure to correctly operate the software solution
C

108
The Vendor shall provide a System Manuals and operating
procedures for the System Administrator.
C

109
The documentation shall be written in English using accepted
technical terms and nomenclature currently in use within the industry.
C

110
The Vendor shall maintain the Versions of each Documentation set
released.
C

111
The Vendor shall provide appropriate documentation of Backup,
Disaster Recovery policy
C

112
The server shall be hardened and all the unnecessary ports shall be
closed and the services should be stopped. Documentation shall be
provided for the open ports and services with detailed explanations.
C


Tabl e-02: Br oad Speci f i cat i ons f or Har dwar e and Devi ces
Vendor shall provide the specifications of the offered solution as detailed below with product literature and other
supporting documents. Mere reference to internet site for downloading product literature is not sufficient.
A. Broad Specification for Servers
a) CPUs should be of RISC / EPIC for all SAP Production, QA, Development, Log shipping, and Back up
offered.
b) All offered servers for SAP Production, QA, Development, Log shipping, and Back up should be on UNIX
unless mandated.
c) Production Database Servers should be 100% vertically scalable with respect to the number of CPUs,
memory and disks configured. Clustering to be provided for Database & Central Instance (CI) Servers
only.
d) Application Servers should meet the required SAPs for the present requirements. The solution
Architecture should support horizontal scalability for Application Servers and 100% Application Load
failover without degradation of performance.
e) Mail server should have more than 100% vertical scalability and the proposed system should be certified
as meeting the performance requirements by the OEM Mail application provider.
f) All Servers except SAP Production Database Servers & Mail Servers should be consolidated in a Blade.
The offered Blade can be of X86 architecture. All CPUs quoted provided for the blade should be of Server
Class architecture.
g) The proposed OS should be certified to run the latest versions of the offered application/ solutions and
database.
h) Roadmap for the Processors of the quoted servers should be presented.
i) In case any upgrades need to be conducted by Owner at a later point of time for reasons attributed to
load increase due to increase in user levels then the OEM should provide the same for the period of at
least Six years from the date of supply.
j) The servers to be supplied along with OEM racks (same as server make).
Detailed technical specification shall be supplied by the Vendors in the specified format given below. Separate
sheets shall be given for all the devices if specification differs.


B. Technical Specifications for UNIX Servers

Sr.
No.
Item Specifications
Offered
Yes/No/
Value
Deviation/
Enhancement
1 Make and Model HP/ IBM/ SUN <specify>
2 Purpose of server Quantity & Use
3 Processor
Should be of Current generation & will have
support for at least 6 years.
Yes/No
3.1 64 bit SMP capability Yes/No
4 CPUs <Value>
4.1 Offered
Specify with justification/Application OEM
Certification

4.2 Max CPUs Specify
5 TPC rating offered
<Attach
relevant
document>
<Value>

6 CPU Cache offered Specify <Value>
7 ECC DDR2 Memory
Memory shall be provided at 6GB
/1000SAPs for Database and Application
server, and minimum 4GB RAM per
processor core for all others.
<Value>

7.1 RAM offered Specify
7.2 Max RAM To be at least twice of that offered
8 System disk
Minimum capacity of 140 (+/- 10%) GB or
higher, 15000 rpm internal disks in mirrored
configuration (2 disks) connected through a
SCSI/SAS/ Fibre Channel controller.

Suitable disk management software shall
be supplied including Volume Manager to
dynamically manage the logical volumes.
Yes/No

8.1 In RAID 1 Specify
8.2 Without RAID Specify
8.3 SWAP space At least 4 times the size of RAM
9 DVD <Capacity>
Shared/
Discrete

10 DAT72 Drive <Capacity>
Shared/
Discrete

11 Adapter slots <Value>


Sr.
No.
Item Specifications
Offered
Yes/No/
Value
Deviation/
Enhancement
PCIX/PCIE
12 Adapters
10/100/1000Mbps Ethernet Network ports
(all adaptors should have single Ethernet
port except the ports on the mother board)
autosensing, in automatic fail-over/
redundant/ trunking / link aggregation and
auto-switching mode. Ports for Dedicated
LAN and Management LAN should be
extra as per requirement.

12.1
Fibre Channel SAN adapters for SAN
storage Cluster Heartbeat Adapters.

FC ports of 4 Gbps speed (for SAN
connectivity) with multi-path I/o/ trunking
and automatic load balancing should be
provided for each server/ partition. All the
compatible required hardware and software
and licenses for this should be provided.

12.2 Display/ Keyboard/ Mouse
13 Partitioning Whether offered as a Partition Yes/No
14 (RAS) features - ECC in memory Yes/No

14.1 - Hot swappable disk bays
14.2 - Redundant cooling fans
14.3 - Redundant power supply
15 OS/ Compiler/ Sw Provide Details
16 Form factor Rack Model with rack mount kit
17 Documentation Yes/No
18
Whether Part of
Cluster
Yes/No
18.1 Cluster Heart Beat
OS Cluster/ Heartbeats ports (using dual
path). Vendor has to submit the detail
scheme.

19 software
Partition management software having
dynamic configuration feature with GUI
interface.
Yes/No
19.1
Latest version of 64-bit OEM UNIX
Operating System for each partition with
unlimited user.
Yes/No
19.2
The OS license shall be provided to
support all servers/ partitions with separate
independent instances of the OS in each
server/ partition.
Yes/No


Sr.
No.
Item Specifications
Offered
Yes/No/
Value
Deviation/
Enhancement
19.3 Clustering software for DB servers Cluster. Yes/No
20 Power requirement Specify
21
Heat generated by the
server
Specify
22 Other features
If the server is part of a Partition, specify in
a separate table the details of partitions in
the box.

22.1
Provide Technical Specifications for UNIX
Server Box, offered as Partition with details
like current and maximum configuration
possible in each box.

C. Technical Specifications for Windows Servers
To be offered only if a particular SAP module or other Application mandates a platform other than UNIX,
(Separate sheets if specification differs between servers).

Sr.
No.
Item Specification
Offered
Yes/No
Deviation/
Enhancement
1 Make and Model HP/ IBM/ SUN Specify
2 Purpose of server Quantity & Use
3 Processor
Should be of current generation & will have
support for at least 6 years.

3.1 No of Processors Specify

3.2 Max processors To be at least twice of that offered
4 Cache Specify <Value>
5 TPC rating Specify
6 ECC DDR2 SDRAM
Memory shall be provided at 6GB/1000SAPs
for database and Application server, and
minimum 4GB RAM per processor core for
all others
<Value>

7 Max RAM To be at least twice of that offered
8 Chipset Intel Chipset or equivalent
9 Hard drives
Minimum capacity of 140 (+/- 10%) GB or
higher, 15000 rpm, internal disks in mirrored
configuration (2 disks) connected through a
SCSI/SAS/ Fibre Channel controller.

Suitable disk management software shall be
supplied including Volume Manager to
dynamically manage the logical volumes.


Sr.
No.
Item Specification
Offered
Yes/No
Deviation/
Enhancement
10 Adapters
I/O Adapters Ethernet Network Adapters
with RJ 45 port

10.
1

Ultra320 SCSI adapters with external port - 1
No

10.
2

Fibre Channel SAN adapters for SAN
storage. FC ports of 4 Gbps speed (for SAN
connectivity) with multi-path I/o/ trunking and
automatic load balancing should be provided
for each server/ partition. All the compatible
required hardware and software and
licenses for this should be provided.

10.
3
Adapter Slots
PCIX/PCIE
Specify
11 Network Adapters
10/100/1000Mbps Ethernet Network ports
(all adaptors should have single Ethernet
port except the ports on the mother board)
autosensing, in automatic fail-over/
redundant/ trunking / link aggregation and
auto-switching mode. Ports for Dedicated
LAN and Management LAN should be extra
as per requirement.

12 DVD DVD +R/+RW 1 no per server
13 Form Factor Rack model with 19" rack mounting kit
14 (RAS) features - ECC in memory

14.
1
- Hot swappable disk bays
14.
2
- Redundant cooling fans
14.
3
- Redundant power supply
15 Operating System
MicrosoftWindows2003 Server
Enterprise Edition

15.
1

Edition 64 bit (licensed copy) with latest
Service Pack and patches on CD Media with
manuals (OEM version).

15.
2

Should provide integration with Enterprise
Management software offered.


Sr.
No.
Item Specification
Offered
Yes/No
Deviation/
Enhancement
16
System manageability
and diagnostics
The system should have following hardware/
software capabilities :

16.
1

Pre-installed OEMs diagnostic tool for
hardware diagnostics.

16.
2
System hardware Management Tool.
16.
3
Rescue and Recovery with Rapid Restore.
18
Heat generated by the
server
Specify
D. Technical Specifications for Windows Blade Servers

Sr.
No.
Item Specification
Offered
Yes/No
Deviation/Enha
ncement
1 Make/Model HP/ IBM/SUN
1.1 Purpose of server Quantity & Use
2 Processor
Latest Intel Xeon or AMD Opteron. CPU must
be of the latest generation, highest speed
available for that model.

2.1 Max Processors To be at least twice of that offered
3 Memory 4 GB RAM per core . Specify.
3.1 Max Memory To be at least twice of that offered
4 Storage
2x 146GB hot plug SAS hard drive at 10K RPM
speed internal to the server.

5 I/O
The blade server should internally support at
least 2 PCI Express I/O slot (either x4 or x8)

6 RAID Controller
Integrated Raid Controller (capable of doing
RAID 0, 1 )

7 NIC Dual Gigabit Ethernet NIC port
8 OS support
Windows server 2003 Enterprise Edition, Red
Hat Linux, SUSE Linux etc.

9 Spare blade Server
One global spare, preferably hot standby, per
enclosure matching highest blade configuration
within the enclosure, to be offered. Windows
and UNIX blades shall be in separate
enclosures.

10 SAN Connectivity
The blade servers should support 2 Nos.
4Gbps Fiber Channel ports for connectivity to
SAN. Two ports required for redundancy.

11 DVD/CD RW External CD/DVD RW drive for software


Sr.
No.
Item Specification
Offered
Yes/No
Deviation/Enha
ncement
installation.
12 Enclosure
Plugs in Blade Enclosure backplane for both
data and power transmission.

12.1
Industry standard suitable for housing in
Standard Server Racks.

12.2
The blade chassis should support at least 8
blade servers with Interconnect devices.

12.3
Same enclosure should support Dual CPU and
Four CPU blade servers.

12.4
Should support Hot Pluggable and Redundant
Management Module.

12.5
Support simultaneous remote access for
different servers in the enclosure.

12.6
Should support a visual display of hardware on
blade enclosure to indicate health of enclosure.

13
Blade Server
Interconnect to LAN/
Network
Network interconnect module for routing all
network cards to switch - provision for FC
connectivity to SAN.

14 Power
Multiple Hot Pluggable Power supplies to be
provided as per Vendors Power Requirement
Calculation. Power supplies should support
redundancy.

15 Cooling
Each blade enclosure should have each own
set of hot pluggable redundant fans/blowers to
ensure cooling.

16 System software System software has to be from the OEM itself.
16.1
Deployment - GUI, console-based deployment
server to set up multiple OS and application
configurations. Grouping of blade servers in
the console by physical location of
rack/enclosure/bay should be possible.

16.2
Management - Comprehensive web enabled
system management tool that monitors the
system health, environment, critical action etc.

17 Remote Management
Complete hardware based Remote
Administration from a standard web-browser
with Event logging, detailed server status,
Logs, Alert Forwarding, virtual control, remote
graphical console, Remote Power Control/
Shutdown, Virtual Floppy and CD for Remote
boot and configuration, Virtual Text and
Graphical Control, Automatic IP configuration
via DHCP/ DNS/ WINS, with 128 bit SSL
Encryption Security. The blade system should
have the capability of managing all the blades
in the enclosure simultaneously.

18
FC and Ethernet connectivity should have
redundant connectivity to the backplane.


Sr.
No.
Item Specification
Offered
Yes/No
Deviation/Enha
ncement
20
Heat generated by
storage system
Specify

E. Technical Specifications for Unix Blade Servers

Sr.
No.
Item Specification
Offered
Yes/No
Deviation/
Enhancement
1 Make/Model HP/ IBM/ SUN
1.1 Purpose of server Quantity & Use
2 Processor
64 bit processor. CPU must be of the latest
generation, highest speed available for that
model.

2.1
Max Processors
Expandability
To be at least twice of that offered
3 Memory 4 GB RAM per core. Specify.
3.1 Max Memory To be at least twice of that offered
4 Storage
2 x 73GB hot plug SCSI hard drive or Blade
Server booting from SAN

5 RAID Controller
Integrated Raid Controller (capable of doing
RAID 0, 1)

6 NIC Dual Gigabit Ethernet NIC port
7 OS support 64 bit SMP UNIX.
8 Spare blade Server
One global spare, preferably hot standby, per
enclosure matching highest blade configuration
within the enclosure, to be offered. Windows
and UNIX blades shall be in separate
enclosures.

9 SAN Connectivity
The blade servers should support Two Nos.
4Gbps Fiber Channel ports for connectivity to
SAN. Two ports required for redundancy.

10 DVD/CD RW
External CD/DVD RW drive for software
installation.

11 Enclosure
Plugs in Blade Enclosure backplane for both
data and power transmission.

11.1
Industry standard suitable for housing in
Standard Server Racks.

11.2
The blade chassis should support atleast 8
blade servers with Interconnect devices.

11.3
Same enclosure should support
RISC/EPIC/Intel/AMD blade servers.

11.4
Same enclosure should support Dual CPU and
Four CPU blade servers.


Sr.
No.
Item Specification
Offered
Yes/No
Deviation/
Enhancement
11.5
Should support Hot Pluggable and Redundant
Management Module.

11.6
Support simultaneous remote access for
different servers in the enclosure.

11.7
Should support a visual display of hardware on
blade enclosure to indicate health of enclosure

12
Blade Server
Interconnect to LAN/
Network
Network interconnect module for routing all
network cards to switch - provision for FC
connectivity to SAN

13 Power
Multiple Hot Pluggable Power supplies to be
provided as per Vendors Power Requirement
Calculation. Power supplies should support
redundancy.

14 Cooling
Each blade enclosure should have each own
set of hot pluggable redundant fans/blowers to
ensure cooling.

15 System software System software has to be from the OEM itself.
15.1
Deployment - GUI, console-based deployment
server to set up multiple OS and application
configurations Grouping of blade servers in the
console by physical location of
rack/enclosure/bay should be possible.

15.2
Management - Comprehensive web enabled
system management tool that monitors the
system health, environment, critical action etc.

16 Remote Management
Complete hardware based Remote
Administration from a standard web-browser
with Event logging, detailed server status,
Logs, Alert Forwarding, virtual control, remote
graphical console, Remote Power Control/
Shutdown, Virtual CD for Remote boot and
configuration, Virtual Text and Graphical
Control, with 128 bit SSL Encryption Security.
The blade system should have the capability of
managing all the blades in the enclosure
simultaneously.

17
FC and Ethernet connectivity should have
redundant connectivity to the backplane.

19
Heat generated by
storage system
Specify


F. Technical Specifications for Administrators Console

Sr.
No.
Item Specification
Offered
Yes/No
Deviation/
Enhancement
1 Make and Model HP/ IBM/ SUN
1.1 Purpose Quantity & Use
2 Processor Latest Dual Core Intel/ AMD processor
2.1 No of Processors/
Specify
2.2 Max Processors
3 DDR2 SDRAM 1 GB minimum

3.1 Max RAM Specify
4 Chipset Specify
5 Display
17 TFT flat panel colour monitor.
Resolution:1024x768

6 Hard drives 120GB SATA
7 I/O Adapters Specify
8 Adapter Slots 4 nos. PCI-X slots free
9 LAN connectivity 10/100/1000 BaseTx , RJ 45
10 DVD 48X CD-RW-DVD-ROM combo
11 I/O Interfaces 1 Serial; 1 parallel; PS/2 port; 4 USB 2.0 ports
12 Mouse Optical scroll Mouse
13 Keyboard 107 keys
14 Operating System
MicrosoftWindowsXP professional/ Vista
(licensed copy) with latest Service Pack and
patches on CD Media with manuals (OEM
version).

15
System manageability
and diagnostics
The system should have following hardware/
software capabilities :

15.1
Pre-installed OEMs diagnostic tool for
hardware diagnostics+C41
15.2 System hardware Management Tool.
15.3 Rescue and Recovery software.


G. Technical Specifications for SAN Storage system

Sr.
No.
Item/Feature
Offered
Yes/No
Deviation/
Enhancement
1 Make/ Model : EMC/ HP/ IBM/ SUN Specify
1.1 Purpose (Quantity & Use)
2
The storage solution must have intelligent hardware based RAID
support for the proposed solution.

3
The solution shall be offered in Heavy Duty OEM racks (Same as
storage make).

4
The Central Storage System must support multi path and automatic
load balancing with no single point-of-failure between Servers, Central
Storage System and SAN. The required licenses (multi path etc) shall
be provided and configured.

5
The DB Servers and Application Servers where clustering is indicated,
will have access to the common single database on an external storage
through a switched Fibre Channel Storage Area Network (SAN).

6 The offered solution shall have Hot-Plug feature enabled disks.
7
Shall have support for multiple Operating Systems. License
requirements if any for OS access for the following operating systems
shall be provided for the entire storage:

Offered Unix, Windows and Linux with support for clustering
8 Architecture
8.1
The storage array shall be an all-fibre channel technology and shall
have architecture and be configured for no single point of failure.

8.2
The storage system shall be configured with minimum 4GB usable data
cache per controller.

8.3 The SAN system shall provide minimum 120000 IOPS.
8.4
System shall have Intelligent hardware RAID controllers to implement
hardware mirroring at storage controller level.

8.5
Shall have support for RAID levels 1, 1+0 & 5. RAID implementation
shall be hardware based.

8.6
System shall have redundant hot swappable power supplies and
cooling fans with no single point of failure

9 Storage Capacity
9.1
The storage system shall be configured for each server for usable
storage capacities and required RAID (1, 1+0, 5) configuration.

9.2
Space under RAID 1 using 146 GB FC disks.
Space under RAID 5 using 146 GB FC disks. Minimum disk speed shall
be 15000 rpm for FC drives. Capacities are mentioned bellow.

9.3
The system shall be configured to make and maintain snapshot local
backup, of designed capacity (of full scale usage by 150 unrestricted-
full-license SAP users, 550 SAP ELSS users and other application
users mentioned in the RFP) under Raid 1. The amount of Disk space
required for each server for both local and SAN disks, after formatting


Sr.
No.
Item/Feature
Offered
Yes/No
Deviation/
Enhancement
(Storage Overhead +Operating System Overhead +File System
Overhead) visible to the OS shall be computed considering the master
and transaction volume, requirement for online data availability of 2
years (Current and previous financial year) on SAP database and 7
years on the Business Warehouse Database. Beyond this period, data
will be vaulted and depending on requirement to be selectively loaded
on Business Warehouse database. All employee data will be
permanent. An annual transaction growth rate of 5% can be considered.
10 SAN Host Ports
10.1 The SAN box should have 4Gbps host side ports.
11 Availability And Data Protection Features
11.1
System should support non-disruptive hot replacement of modules /
components for the following:

1. Interfaces
2. Disk Controllers
3. Disk Drives
4. Cache memory cards
5. Cache memory boards
6. Power supplies & battery systems
7. Cooling Fans
11.2 The system shall have:
1. Automatic detection of errors, error logging and notification.

2. Pro-active maintenance self monitoring, self diagnosing and
wherever possible, self repairing features

12 Management

GUI based Management software for total configuration & performance
management of the SAN.

13
SAN license should not limit the number of servers to be connected to
the SAN

14 Power requirement
15 Heat generated by storage system
The minimum acceptable Storage for 250 users shall be
Production Database 1.5TB
Development 500GB
Test 1.5TB


Business Copy 1.5TB
BW Production 1TB
BW Development 500GB
For copies in ATA drives 4.5TB
30% additional space for each disk type should be configured for storage performance.
All the software provided with the storage systems should have licensing for a period of Five Years.


H. Technical Specification for Rack Mountable Fiber Channel SAN Switch

Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
1 Make/ Model : Brocade/CISCO/McData/OEM
1.2
Two numbers of fibre channel switches, shall be provided and
configured. The switches shall be rack mountable.

2
The switch shall be guaranteed to be fully compatible for HBAs,
Clustering solutions and OS offered with the servers.

3
Nos. fiber channel ports of 4Gbps (1/2/4 auto sensing) full-duplex to be
configured. Sufficient ports to be available for redundant connectivity
between proposed servers and the two switches with 100% scalability.
Each SAN port on the switch should be 4Gbps. Breakup of port as
mentioned:
Mention
No, of
ports on
each
switch

Total
configure
d

Free
3.1 For Servers , as per SAN Network scheme
3.2 For SAN Storage, as per SAN network scheme and free ports.
3.3
The FC connects between Servers and the SAN Switch as well as the
FC Connects between SAN Switches and SAN storage shall be of
minimum 4 Gbps bandwidth

4.0 Shall support Error detection and fault isolation

I. Technical Specification for Tape Library (Back-up Device) Drive and Backup software

Sr.
No.
Item Specification
Offered
Yes/ No
Deviation/
Enhancement
A. Tape Library(Back-up device)
Library Specifications
The production data should get backed up in a
window of 6 hours max on LTO-4 drives.
Proposed Library should have cartridge slots
for at least 2 sets of Production data copy &
Cartridges to backup 4 copies of Production
data.

Make/Model: EMC/
HP/IBM/SUN

1 Tape Drive Ultrium 4

2 Type and Nos. Specify
3 Number of drives Adequate Nos.
4 Interface 1 for each drive

4.1 Controllers 2/4 Gbps
5 PCI card slots Nos.


Sr.
No.
Item Specification
Offered
Yes/ No
Deviation/
Enhancement
6
Number of cartridges/
slots
Specify
7 Maximum capacity Specify
8 Maximum throughput In TB/hr
9 RAS Features
10 Scalability
11 Interface GUI
12 Supported platforms
Windows2000; Windows Server 2003; IBM
AIX; Sun Solaris; HP-UX, Ent. Linux

13 Management via GUI software and command line interface
14 software Supplied Specify
15 Power consumption
15.1 Power requirement
16
Heat generated by
backup system

17 Drive Specifications:
17.1
Capacity Per
cartridge
1600 GB (with 2:1 compression)
17.2
Recording
Technology

17.3
Sustained Data
Transfer rate

17.4
Aggregate sustained
data rate

17.5 Number of tracks
17.6 Media Type
17.7
Backward
compatibility

17.8 Interface
17.9 Rewind speed
17.10 Operating Speed
17.11
The tape drives
should be sharable
across all
servers/partitions.

B. Back-up software
18
Backup software
shall have the
following features:

18.1
Back-up software
should be a single
solution for
supporting multiple
operating systems
and application using
a single product
which would take


Sr.
No.
Item Specification
Offered
Yes/ No
Deviation/
Enhancement
care of Growth in
future.
18.2
Should have built-in
centralized, policy
driven management
feature.

18.3
software should
provide extensive
device supports for
various device types
and device
manufactures.

18.4
software should have
full command line as
well as GUI support
on above mention
OSs.

18.5
Should support
backups for clustered
servers and support
industry popular
clusters like HP
service guard, Legato
cluster, HACMP and
GNU Linux. i.e.
should have the
ability to backup data
from clustered
servers from the
virtual client, backing
up data only once
and giving consistent
bcakup in case of
failure of nodes.

18.6
The software should
able to take online
backup for multiple
instances of
messaging or
database running on
single system without
requiring multiple
licenses for every
instance.

18.7
software should
support cross
platform Tape Device
& Media sharing with
multiple clients and
backup servers in
SAN environment to
increase the return of


Sr.
No.
Item Specification
Offered
Yes/ No
Deviation/
Enhancement
investment.
18.8
Software should have
true Disk Staging,
wherein the backup
continues to take
place even when the
disk space allocated
is full. The backup
software must be
intelligent enough to
flush out the data
from the disk and
migrate the same to
the tape
automatically.

18.9
Software should have
the capability to
virtualize the disk
resources for disk
staging and should
have the ability to
keep a copy of the
active backups on the
staging disks to
provide quick
restoration.

18.10
Should support
policy-based
automated migration
that moves managed
data from one type of
media to another
based on user
defined thresholds.
e.g automated
backup from disk
units to tape media or
tape to worm.

18.11
Backup software
shall support
Synthetic backup so
that Full backup can
be constructed
directly from the disk
based incremental
backups.

18.12
The Backup software
must also be capable
of automatically
reorganizing the data
from partially filled
tapes to one or more
tapes within the same


Sr.
No.
Item Specification
Offered
Yes/ No
Deviation/
Enhancement
library to increase
space utilization. The
thresholds for
defining the data
reorganizing can be
user defined.
18.13
The software must
have the capability of
monitoring and
controlling the tape
sent offsite, or data
sent across by WAN
through Electronic
Vaulting.

18.14
The software must
also provide for
creating a Disaster
Recovery Plan or
DRP in case of the
Backup server and all
other servers in the
backup network
being destroyed in a
possible disaster.
This should be a
scheduled and
Automated activity on
the backup server.

18.15
LAN free backups to
tapes and disk
devices on most
popular OS
platforms.

18.16
The Backup software
must have an open
API to enable
integration with other
enterprise
applications such as
EMS.

18.17
Should have the
ability to store data in
a hierarchy of storage
that provides users
with the ability to
automatically move
managed data from
one type of media to
another, including to
new technology.

18.18
Should have well
differentiated
Archiving and DR


Sr.
No.
Item Specification
Offered
Yes/ No
Deviation/
Enhancement
mechanisms.
Archived Data should
be tracked for a
policy-determined
time before deleting
them. Should also
have the ability to
delete data from the
primary system after
archiving the data.
18.19
Should provide
details logs on both
the Clients as well as
the Server to support
in advanced
troubleshooting
without any
performance
implications.

18.20
Ability to perform
Hot-Online backup
for different type of
Databases such as
Oracle, MS SQL,
DB2 etc. on various
platforms.

18.21
Should be licensed to
support multiple disk
and tape
drives/libraries with
SAN attachments.
There should be no
additional licensing if
the number of tape
drives is increased in
order to reduce
backup window.

18.21
The licensing for the
Backup software
must be done in such
a way that the
migration of operating
systems and/or
databases/mail
servers of
servers/clients must
not warrant a change
in license. The
licensing must be
independent of the
server processor.

19 Backup licenses are


Sr.
No.
Item Specification
Offered
Yes/ No
Deviation/
Enhancement
to be provided for
following:
19.1
Base License All
Servers

19.2
SAN (LAN free
backup) for DB

19.3 ERP online for DB
19.4
ERP from Snapshot
for DB

19.5
Any other ERP
Component Backup

19.6
Legacy server and
common service
server agents for
online backup

J. Technical Specifications for Core Switch
Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
1 Make/ Model : CISCO/Nortel
1.2
Two Nos of Switches shall be provided and configured. The switches
shall be rack mounted in 19 Rack.

2
Chassis based with minimum 7 payload slots including two spare slots
for future needs

3 Should be loaded with 8 nos of 10 Gb ports including transceivers
4 Should be loaded with 16 nos of 1000 base FX ports.
5 Should be housed in a standard network rack with all accessories
6 Suitable uplinking and downlinking fiber patch cords are to be supplied
7 Should be loaded with redundant supervisor engine
8 Console cable to be supplied
9
Chassis with Redundant Power supply with support for hot swappable
modules

10
Should be as per Indian power supply design and shall operate
between 180-240 AC

11 Should provide a minimum of 720 Gbps backplane capacity.
12 Should support forwarding rate of upto 400mpps
13
Support management module redundancy in active passive mode and
should be loaded with dual management modules. Failure of one
supervisor should not affect throughput of the supervisor and hence
reduce the performance of the switch.

14 Should support stateful failover and hitless software upgrades.
15
Switch should provide the ability to monitor events and take corrective,
or any desired action when the monitored events occur or when a
threshold is reached.

16 Should provide a mechanism to manage the traffic flow of control plane


Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
packets to protect the control plane against reconnaissance and Denial
of Service (DoS) attacks.
17
Switch should provide a mechanism to detect connectivity issues with
both fiber and copper cabling. Ensures that a partially failed link is shut
down on both sides, to avoid L2/L3 protocol convergence issues

18
Should support a mechanism to provide security and isolation between
switch ports, helping ensure that users cannot snoop on other users'
traffic.

19
Should support remote port mirroring ie mirror ports from and to any
other switch in the network

20
The Security features should support port filtering, enabling of individual
ports to access only selected nodes, IP permit lists to prevent
unauthorized access to the switch, Access Control Lists (ACL) to secure
networks from unauthorized users, strong authentication and secure
communications over un-secure channels for access to the network.

21
Switch should provide mechanism to prevent unauthorized switch from
taking over as the Root bridge or causing the Spanning Tree to re-
converge

22
Switch should provide a mechanism to prevent unauthorized switch
from affecting core spanning tree topology, by auto-disabling access
port

23 Should support VRRP for high availability.
24
Should support IPv6 in hardware, L2, L3 and L4 access control filters,
L3/L4 frame classification,

25
Should support Ethernet, Fast Ethernet, Gigabit Ethernet and 10G
Ethernet protocols

26 Should support for RMON, SNMP management, RIP2 etc.

K. Technical Specifications for Distribution Switch

Sr.
No.
Specification
Offered
Yes/No
Deviation/
Enhancement
1 Make/ Model : CISCO/ Nortel
1.2
Two numbers of switches shall be provided and configured. The switches
shall be rack mountable and configured in 19 racks.

2
The switch shall work as the distribution layer shall be connected with
Core Switch and Access Switch.

2.1
The Management LAN switch shall be provided and configured. The
switches shall be rack mountable.

2.2
The switch shall be connected to Database servers, SAN, Backup,
Backup server, Legacy SAN, Legacy Backup etc. and the Administrator
consoles.

3 At least 24 port 10/100/1000 Mbps ports
4 16 GBPS switching fabric
5 Advanced QoS and resiliency
6 Integrated security including network admission control


Sr.
No.
Specification
Offered
Yes/No
Deviation/
Enhancement
7 Minimum 6.5 Mbps using 64 byte packets
8
Chassis based with minimum 5 payload slots including two spare slots for
future needs

9 Should be loaded with 4 nos of 10 Gb ports including transceivers
10 Should be loaded with 16 nos of 100 base FX ports
11 Should be housed in a standard network rack with all accessories
12 Suitable uplinking and downlinking fiber patch cords are to be supplied
13 Should be loaded with redundant supervisor engine
14 Console cable to be supplied
15
Chassis with Redundant Power supply with support for hot swappable
modules

16
Should be as per Indian power supply design and shall operate between
180-240 AC

17 Should provide a minimum of 100 Gbps backplane capacity.
18 Should support forwarding rate of upto 80mpps
19
Support management module redundancy in active passive mode and
should be loaded with dual management modules. Failure of one
supervisor should not affect throughput of the supervisor and hence
reduce the performance of the switch.

20 Should support stateful failover and hitless software upgrades.
21
Switch should provide the ability to monitor events and take corrective, or
any desired action when the monitored events occur or when a threshold
is reached.

22
Should provide a mechanism to manage the traffic flow of control plane
packets to protect the control plane against reconnaissance and Denial
of Service (DoS) attacks.

23
Switch should provide a mechanism to detect connectivity issues with
both fiber and copper cabling. Ensures that a partially failed link is shut
down on both sides, to avoid L2/L3 protocol convergence issues

24
Should support a mechanism to provide security and isolation between
switch ports, helping ensure that users cannot snoop on other users'
traffic.

25
Should support remote port mirroring ie mirror ports from and to any
other switch in the network

26
The Security features should support port filtering, enabling of individual
ports to access only selected nodes, IP permit lists to prevent
unauthorized access to the switch, Access Control Lists (ACL) to secure
networks from unauthorized users, strong authentication and secure
communications over un-secure channels for access to the network.

27
Switch should provide mechanism to prevent unauthorized switch from
taking over as the Root bridge or causing the Spanning Tree to re-
converge

28
Switch should provide a mechanism to prevent unauthorized switch from
affecting core spanning tree topology, by auto-disabling access port

29 Should support VRRP for high availability.
30
Should support IPv6 in hardware, L2, L3 and L4 access control filters,
L3/L4 frame classification,

31
Should support Ethernet, Fast Ethernet, Gigabit Ethernet and 10G
Ethernet protocols

32 Should support for RMON, SNMP management, RIP2 etc.


L. Technical Specification for Management LAN Switch
Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
1 Make/ Model : CISCO/Nortel
1.2
The Management LAN switch shall be provided and configured. The
switches shall be rack mountable.

2
The switch shall be connected to Database servers, SAN, Backup,
Backup server, Legacy SAN, Legacy Backup etc. and the Administrator
consoles.

3 At least 24 port 10/100/1000 Mbps ports
4 16 GBPS switching fabric
5 Advanced QoS and resiliency
6 Integrated security including network admission control
7 Minimum 6.5 Mbps using 64 byte packets

M. Heavy Duty Racks for Servers/ SAN/ Storage/ Backup/ LAN switch/ Structured cabling
The Vendor should provide the no of racks with details of equipment in each rack.
Sr.
No.
Item Specifications
Offered
Yes/No
Deviation/
Enhancement
1 Make/ Model:
VeroPresident (Rack), Valrack, OEM Make,
KVM switch (Avocent, Minicom, Raritan or
OEM make KVM to be offered if needed to
manage multiple servers. If KVM is not offered
vendors should mention how multiple servers
will be managed)

1.1 Purpose Quantity & Use
2 Rack
Heavy duty 42Ux600x1000 Integrated Server
Rack Frame, with Power and Air Management;
Depth Optimised for Multi-vendor Server
Support

2.1 Recessed 19" Verticles for Server Support
2.2 Single Front glass Door with Handle and Lock
2.3
Single Back Perforated Door with Handle and
Lock

2.4
Side Panels with Slam Latches - Easily
Removable

Accessories
2.5 Fixed Tray
2.6 Keyboard Tray
2.7 12 Socket Power Strip, 5/15 AMP
2.8 4" Fans


Sr.
No.
Item Specifications
Offered
Yes/No
Deviation/
Enhancement
2.9 Castors (2 Locking; 2 Non Locking)
3 Monitor
15 TFT flat panel colour monitor with
necessary cable per rack. Resolution: SXGA

4 Keyboard
Unix OS/ Windows compatible, per rack with
drawer.

5 Mouse Optical USB Scroll Mouse, per rack
6 KVM switch
Digital KVM switch per rack with minimum ports
to connect all Unix/Windows based servers in
the rack to a single TFT monitor, keyboard and
mouse to carry out administrative functions of
all the connected servers using the common
monitor.

N. Broad Specifications for Internet/Intranet Routers

Sr. No. Specification
Offered
Yes/ No
Deviation/
Enhancement
1 Architecture
1.1
Should be chassis based & modular architecture for scalability and
should be a single box configuration for ease of management.

1.2
Shall support at least 5 interface slots to accommodate the current
requirement as well as for the future expansion. Should have
minimum 2 slots free for future expansion

1.3
Should have hardware based IPSEC VPN (3DES/AES) Encryption
card. Should have integrated/ integration capability with complete
Firewall, IPS & SSL VPN features.

1.4
Should have minimum of 256MB of RAM and 64 MB of Flash
Memory and should be upgradeable to 1GB and 256MB respectively.

2 Interface Requirements
2.1 2 x V.35 Serial (2 Mbps) Interfaces
2.2 2 x 10/100/1000 Interfaces
2.3 Cache engine with at least 120 GB hard disk
3 Performance
3.1 Shall support high performance traffic forwarding with concurrent
features like security & voice enabled

3.2 Shall support variety of interfaces like:
3.2.1 V.35 Sync Serial (2 Mbps), Async Serial, E1 G.703, Ch-E1 for
Horizontal office aggregation

3.2.2 GE as per IEEE 802.3z and 802.3ab, FE as per IEEE 802.3u,
Chassis support for 802.3af.

3.2.3 ISDN BRI, PRI
3.2.4 Shall support DSL connectivity using ADSL, G.SHDSL for Horizontal
office connectivity using Dead copper from Service Provider.

3.2.5 Support for 802.11a/b/g Wireless Cards for Wireless LAN or Wireless
Bridging functionality.


Offered
Yes/ No
Deviation/
Enhancement
3.2.6 Should have support for high density Voice interfaces like E &M,
Voice E1 for connecting Analog phones & integration to PBX / PSTN.

3.2.7 Support for high density Ethernet switch cards (8 port / 16 port) for
remote offices to avoid additional switches.

3.2.8 Should have USB ports for storing OS images & secure token
3.3
Shall have support performance enhancement through hardware
based encryption / compression module

3.4 Shall support other IP Services like GRE tunneling, ACLs, IPSEC
VPNs, Firewalling, SSL VPN, NAT services.

3.5
Shall support MLPPP for link aggregation
3.6 Shall support Voice traffic optimization with features like LFI, cRTP
3.7 Shall support at least 160 Kpps forwarding performance
4 High Availability
High Availability with NSPOF Should support Active/Active and
Active/Standby failover, when two identical appliances are
implemented in fail safe mode. Should have support for redundant
power supply & cooling fan.

4.1 Shall support redundant connection to LAN
4.2 Shall support Non-Stop forwarding for fast re-convergence of routing
protocols

4.3 Shall support boot options like booting from TFTP server, Network
node

4.4 Shall support multiple storage of multiple images and configurations
4.5 Shall support link aggregation using LACP as per IEEE 802.3ad
4.6 Shall support VRRP or equivalent
5 Protocol Availability
5.1 Shall support Routing protocols like RIP ver1 (RFC1058)&2 (RFC
1722 and 1723), OSPF ver2 & ver3 (RFC2328), OSPF on demand
(RFC1793), BGP4 (RFC1771), IS-IS (RFC1195). OSPF Fast hellos
for faster convergence. OSPF Flooding Reduction

5.2 Support for Non-Stop Forwarding on the routing protocols NSF
Awareness (BGP, OSPF, IS-IS

5.3 Multicast routing protocols support : IGMPv1,v2 (RFC 2236), PIM-
SM (RFC2362) and PIM-DM, DVMRP, M-BGP

5.4 Shall support IPv6 features: DHCPv6, IPv6 QoS, IPv6 Multicast
support, BiDirectional PIM, Multicast VPN, PIM SSM (Source
Specific Multicast), IPv6 PIMv2 Sparse Mode, IPv6 PIMv2 Source-
Specific Multicast,

5.5 Shall support RIPng and OSPFv3 for IPv6.
5.6 MPLS Features: MPLS VPN, MPLS (mVPN (Multicast VPN), VRF-
Aware Services (NAT, FW, IPsec), Carrier Supporting Carrier
(CsC), DiffServ Tunnel Modes, MPLS TE, DiffServ-Aware TE, Inter-
AS VPNs)

5.7 Should have support for Integrated IP Telephony support to function
as local IP PBX and as redundant IP PBX

5.8 Support for URL filtering & Caching of applications & videos
5.9 Support for Load balancing Protocol for better use of resources
5.10 Support unequal cost link load sharing to better utilize the alternate
paths


Offered
Yes/ No
Deviation/
Enhancement
5.11 Support for TCP Acceleration mechanisms to enhance the TCP
performance over the WAN links. The TCP Acceleration mechanisms
should be supported over end-to-end encrypted tunnels

5.12 Support for Circuit Emulation over IP to carry PBX traffic or legacy
protocols in their native form

5.13 Configuration Roll Back to recover the mis-configured router to last
good configuration.

6 QoS Features (following features should be supported)
6. Classification and Marking: Policy based routing, IP Precedence,
DSCP, MPLS exp bits

6.1 Congestion Management: WRED, Priority queuing, Class based
weighted fair queuing

6.2 Traffic Conditioning: Committed Access Rate/Rate limiting
6.3 Signalling: RSVP
6.4 Link efficiency mechanisms: cRTP, LFI, MLPPP (necessary
hardware modules to be quoted)

6.5 Per VLAN QoS. Time Based Shaping and Policing for QoS
6.6 Shall support Classifiers for Intelligent Application Identification
7 Security Features
7.1 Should have GRE Tunneling, NAT, L2TP tunneling, without any
major performance impact. (necessary hardware modules to be
quoted)

7.2 IPSEC Site-to-Site and Remote Access VPNs. hardware based
encryption. Any Office to Any other office, dynamic establishment of
VPNs so that the configuration & management of IPSEC VPNs
becomes easier. IPSEC VPNs should be able to carry data, voice,
video multicast traffic. Support for IPSEC Site-to-Site and Remote
Access VPNs.

7.3 Firewall, IPS & SSL VPN features. Support for customized IPS
signatures.
Support for tunnel less VPNs for very high scalability with support for
routing protocols and multicast traffic.

7.4 MD-5 route authentication for RIP, OSPF, IS-IS and BGP
7.5 Shall support multi-level of access
7.6 SNMPv3 authentication, SSHv2
7.7 AAA support using Radius and/or TACACS
7.8 PAP and CHAP authentication for P-to-P links
7.9 DoS prevention through TCP Intercept & DDoS protection
7.10 IP Access list to limit Telnet and SNMP access to router
7.11 Multiple privilege level authentications for console and telnet access
through Local database or through an external AAA Server.

7.12 IEEE 802.1x support for MAC address authentication
7.13 Should have features to limit the spread of viruses & worms on the
desktops / workstations.

8 Multi-media support

Shall support Voice capabilities
- Voice pass-through
- Codec support for G.711 and G.729

Shall support H.323, SIP, MGCP


Offered
Yes/ No
Deviation/
Enhancement
Shall support Voice call processing in the event of WAN link failure
to Central call processing Engine

Shall support bandwidth optimization features like Voice Activity
Detection, Silence Suppression, Echo cancellation

Should not consume more than 14-15Kbps of bandwidth (including
overheads) for a single voice over IP call

9 Management
9.1 Shall have support for Web based management, CLI, Telnet and
SNMPv3

9.2 Shall support Secure Shell for secure connectivity.
9.3 Shall support Out of band management through Console and
external modem for remote management

10 Debug, alarms & Diagnostics:
10.1 Display of input and output error statistics on all interfaces
10.2 Display of Dynamic Arp table
10.3 Display of physical layer line status signals like DCD, DSR, DTR,
RTS, CTS on all serial interfaces

10.4 Trace-route, Ping and extended Ping
10.5 Should have extensive support for SLA monitoring for metrics like
delay, latency, jitter, packet loss, and MOS

O. Broad Specifications for Firewall cum VPN Concentrator
Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
1 The device should match or exceed the following specifications:
1.1 Firewall Throughput at least 400 Mbps from day 1
1.2 3DES/ AES VPN Throughput at least 300 Mbps from day 1
1.3 Concurrent Sessions - at least 250,000 from day 1
1.4 IPSec VPN Peers - at least 700 from day 1
1.5 SSL VPN Peers - at least 50 required from day 1, support up to at least
700 through license enhancement only

1.6 Security Contexts support up to 20
1.7 Interfaces Should have 4 Gigabit Ethernet ports and 1 Fast Ethernet
port

1.8 VLAN Support as per IEEE 802.1q at least 125
1.9 Scalability should support VPN clustering and load balancing
1.10 High Availability with NSPOF Should support Active/Active and
Active/Standby failover, when two identical appliances are implemented
in fail safe mode.

2 Application Security Services Support
2.1 The Firewall should have Integrated specialized inspection engines for
protocols like HTTP, FTP, ESMTP, DNS, SNMP, ICMP, SQL*Net, NFS,
H.323 Versions 1-4, SIP, MGCP, RTSP, TAPI and J TAPI over CTIQBE
protocol, GTP, LDAP, ILS, RPC

2.2 Advanced H.323 inspection services that support versions 1-4 of the
protocol along with Direct Call Signaling (DCS) and Gatekeeper Router
Control Signaling (GKRCS) to provide flexible security integration in


Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
a variety of H.323-driven voice-over-IP (VoIP) environments
2.3 NAT and PAT support for H.323 services, including advanced features
such as fax over IP (FoIP) using the T.38 protocol, an ITU standard that
defines how to transmit FoIP in real time

2.4 Fortified SIP inspection engine that secures both, UDP and TCP based
SIP environments

2.5 NAT- and PAT-based address translation support for SIP-based IP
phones and applications such as Microsoft Windows Messenger, while
delivering advanced services such as call forwarding, call transfers, and
more

2.6 Secure integration of IP telephony services while successfully
connecting calls over multiprotocol VoIP environments across NAT and
PAT boundaries

2.7 Rich MGCP security services and NAT- and PAT-based address
translation services for MGCP-based connections between media
gateways and call agents or media gateway controllers

2.8 Support multisite IP Telephony and Video Conferencing solutions
3 Support for Secure Connecti vity Services
3.1 IPSec remote-access VPN concentrator services for up to hundreds of
simultaneous remote software- or hardware-based VPN clients

3.2 Should be able to Push VPN policy dynamically to Easy VPN Remote-
enabled solutions upon connection, eliminating the need to manage
each client separately and therefore helping ensure enforcement of the
latest corporate VPN security policies

3.3 Perform VPN client security posture checks when a VPN connection
attempt is received, including enforcing usage of authorized host-based
security products

3.4 Should support SSL VPN-based remote-access connectivity from
almost any Internet-enabled location, using only a Web browser and its
native SSL encryption

3.5 Support for hundreds of simultaneous SSL VPN connections
4 Support for High-Availability Services
4.1 Support for bidirectional state sharing between Active/Active failover
pair members for support of advanced network environments with
asymmetric routing topologies, allowing flows to enter through one
Firewall appliance and exit through the other, if required

4.2 Maximizing VPN connection uptime with Active/Standby stateful failover
for VPN connections

4.3 Support for Synchronizing all security association state information and
session key material between failover pair members, providing a highly
resilient VPN solution

4.4 Enable geographic separation of Security appliances in a failover pair
by allowing failover information to be shared over a dedicated LAN
connection between failover pair members

4.5 Access control and deep inspection firewall services for native IPv6
network environments and mixed IPv4 and IPv6 network environments
through dual-stack support

4.6 IPv6-enabled inspection services for applications based on HTTP, FTP,
SMTP, ICMP, TCP, and UDP

4.7 Support for SSHv2, Telnet, HTTP and HTTPS, and ICMP, SNMPv3,
OSPF with md5 authentication -based management over IPv6


Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
4.8 DHCP server services on one or more interfaces, allowing devices to
obtain IP addresses dynamically

4.9 Support for NTPv3 to provide convenient method for synchronizing the
clock on the firewall appliance with other devices on a network

5 Support for Flexible Management Solutions
5.1 Support for Built-in Management software for simple, secure remote
management of the security appliances through integrated, Web-based
GUI

5.2 Support for out-of-band management through a dedicated Fast
Ethernet 10/100 management interface

5.3 Packet Capturing for powerful troubleshooting capabilities by providing
robust packet-capturing facilities on each interface. Support for several
methods of accessing captured packets, including through the console,
secure Web access, or a file exported to a TFTP server

P. Technical Specification for Structured Cabling Components
S No. Item Make/Model Specifications
Offered
Yes/ No
Deviation/
Enhancement
1 Fiber Cable Specify 6 Core/ 12 Core
2 CAT6 UTP Cable Specify CAT6
3
19" Fibre Admin/
Termination Kit
Specify
4 19" Patch/ J ack Panel Specify 24 Port
5
Factory fitted fibre patch
chord
Specify
6
Factory fitted UTP patch
chord
Specify 4FT/7FT
7 Information Outlet Specify Surface mount
8
All connections to be
ferruled/ labeled
Specify
9 Cabling Certification Specify
10 Network cabinet Specify


Q. Technical Specification for PCs
S
No.
Specification
Offered
Yes/No
Deviation/
Enhancement
1
CPU: Intel Core 2 Duo , 2 GHz, 2 MB L2 Cache and 800 MHz FSB or
more

2 Memory: 2 GB DDR2 RAM minimum
3 Hard Disk: 160 GB 7200 rpm SATA HDD
4 Monitor: 17 TFT
5 Keyboard: 104 Keys
6 Mouse: Optical
7 Cabinet: Mini Tower (Black)
8 Networking: 10/100/1000 MBPS Ethernet
9 Operating System: Windows Vista OEM
10 Office: Ms Office 2007 Standard with license

R. Technical Specification for Network Printers
S
No.
Specification
Offered
Yes/No
Deviation/
Enhancement
1 Printing Speed minimum 25ppm
2 No of paper trays: 2
3 Print quality 1200 X 1200dpi
4 Duplex Printing
5 Media size: A4, Letter, Legal, Envelop
6 10/100 Fast Ethernet

S. Technical Specification for Line Printers
S
No.
Specification
Offered
Yes/No
Deviation/
Enhancement
1 Prining Speed minimum 600LPM
2 Minimum 2 tractors
3 Print quality 240 X 288dpi
4 Media Size: 132 Column
5 10/100 Fast Ethernet
T. Acceptable Makes for Hardware Devices
S No. Material Preferred Makes
1 High end servers HP/ IBM/ SUN/ Dell
2 Windows Servers HP/ IBM/ SUN/ Dell
3 Blade Servers HP/ IBM/ SUN/ Dell
4 SAN Storage HP/ IBM/ SUN/ EMC
5 SAN Switch Brocade/ Cisco/ Mcdata
6 Structured Cabling components Tyco/ Molex/ Systimax
7 Network Switch, firewalls, routers, IPS Cisco/ Nortel


8 Backup EMC/ HP/ IBM / SUN
9 Network Rack Vero President/ Valrack /Hardware OEM Make
10 KVM Switch Avocent/ Raritan/ Minicom
11 Administrator Console/ Rack PCs HP/ IBM/ SUN
12 PC Lenovo/ Dell/ HP
13 Network Laser Printer HP
14 Network Line Printer Wipro/ Lipi


Tabl e-03: Br oad Speci f i cat i ons f or Dat a Cent er
A. Specification of Architectural & Interior works of Data Center
These specifications are for work to be done, items to be supplied and materials to be used in the works for Data
Center. The proposed location for Data center is at ITPS. Approximately 900 sq ft area is available for the Data
Center, Management Console, BMS, Gas Bank and UPS room. The indicative design is given for
conceptualization.

1. Specific Requirements in interiors
The interiors shall include finishes on all walls, tiled floors, false floor, ceiling, partition, signage, displays, etc. All
major finishes shall have a fire rating of 2 hrs and shall be of non-combustible, self- extinguishing or fire-retardant
type.
2. Walls/Partitions
For the Server-room, walls in separating zones shall be of floor to ceiling height, perimeter walls/ partitions shall
have 2-hour fire-rating. The frame work of partly glazed Aluminium (Main and Cross) partitions in Data Center
areas shall be from base floor to RCC roof with Fire Rating of 2 Hours. The partitions/ cladding shall be of Fire
Retardant Glass and Aluminium or equivalent material.
3. Specifications for False Flooring
The height of cavity floor is proposed to be 300mm in Data Center. The bottom of the proposed cavity floor shall
be in line and level. The base floor of cavity floor shall be treated with epoxy paint. The base floor in Data Center
needs to be thermally insulated with Armaflex or equivalent insulation. The junctions between the insulator and
fixtures are to be watertight and airtight. The permissible Uniform Distributed Load (UDL) of the Data Center
concrete floor is 350 -400 kg/m
2
. of live load. The Data Center false flooring, equipment, servers & storage on
racks should be provided such the total live load is well with the permissible UDL stated above.


4. False flooring panels
a) The floor should be designed for standard load confirming to BIS 875-1987.
b) Panels should be made up of 18-gauge steel of 600mm x 600mm size treated for corrosion and
coated with epoxy conductive paint (minimum thickness 50 Micron). False flooring covering shall be
antistatic high pressure laminate 2 mm. thick in approved shade and colour with PVC TRIM edge.
c) Perforated floor panels are to be provided on the designated floor for air delivery. The placement of
perforated panels shall be decided after consulting the equipment vendor. The perforated panels
shall have provision for dampers.
d) The interior of the panels shall be filled with non-combustible cementitious compound.
e) The false floor should withstand the load of the racks with 50% safety margin.
f) No obstructions of pipes, conduits, detectors shall be permitted in space immediately under
equipment line-ups. The under floor space under line-ups is required for equipment frame securing,
cable management and power access.
g) Ramps and steps are to be provided for transitioning to elevated floor area at entrance of Data
Center. Ramps are to be designed and installed to building code requirements.
h) Special tools and tackles required for operation of false flooring shall be supplied in two sets.
5. Under Structure
Pedestal Assembly: Pedestal assembly shall be of snap lock type consisting of base assembly 100 x 100 x 2 mm.
with full bead weld to steel base plate with embossing and four numbers holes which shall be fixed to the floor
with screws. Anti vibration rubber pad shall be provided below base plate. Steel pipe riveted to base plate shall
engage the pedestal head assembly. Head shall be formed steel and full bead weld to stud, with four flange
having shape and size as per standard approved manufacturers specifications. Pedestal head flanges shall be
provided with holes for screws for fastening the G.I. Stringers. No sharp edges or corners shall be exposed from
pedestal head when floor panel is removed. G.I. rod, fully threaded shall be locked to pedestal head. The entire
head assembly is engaged in the base assembly by means of nut and check nut.
6. Stringer
Stringer system is hot dipped galvanized sheet, construction having channel, with pre-punched counter and holes
at both ends of the top face for securing the stringers on to the pedestal head to be fixed with screw ensuring
maximum lateral stability in all directions. The grid formed by the pedestal and stringer assembly shall receive the
floor panel. The stringer system would be earthed properly by using copper wire. This is required for some of the
servers for transient grounding.
7. False ceiling, Mineral Fiber Board (Modular ceiling Tile)
Providing and fixing of Mineral Fibre Ceiling tiles in true horizontal level. The ceiling in Data Center needs to be
thermally insulated with Armaflex or equivalent insulation. False ceiling grid shall be of specified make of
Armstrong/ Aerolite or equivalent. Using hot dipped galvanized steel section, exposed surface chemically cleaned
capping pre-finished in baked polyester powder paint, Main tee of size 15 x 35 x 0.33 mm at every 1200 mm G/C
max and rotary stitched cross tee of size 15 x 30 x 0.33mm at every 600 mm CIC 0.457 mm wall angle around the
wall to form a grid of 600 mm x 600 mm and suspending the grid using 2 mm GI rod and 6 mm raw plug at every
1200 mm intervals at the main tee and laying the Ceiling tiles of size 595 mm x 595 mm x 15 mm over the formed
grid having fire rating of 60 minutes as per BS 476/23 of 1987; Noise reduction Coefficient (NRG) of 0.50-0.60, to
resist temperature and humidity conditions up to 40degree (104 deg. F) and humidity of 95% RH, weight of tile
3.5Kgs/SQ.M. The ceiling tile shall be of easy remove and install type for the access of utilities in the ceiling void.
Non-combustible and dust-free plates shall be considered. The false ceiling shall serve as a plenum for lighting
fixtures, fire detection and protection system.
8. Doors


All doors in Data Center shall be of 2 hour fire-rating, with secure bolted hinge. Provision for remote door release
is made for the electric door locks. The Data Centers are to be provided as per indicative diagram with door of
size 1500 mm x 2100mm atleast for equipment movement ingress and egress for installation in and maintenance
out. This would be used during the setup of the proposed Data Center facility and to move in any equipment like
PAC units, electrical panels etc. into the Data Center. The doors will be kept closed and will not be used for
regular access of Data Center facility. This shall also serve as Emergency exit door way with panic bar to be
provided for egress from Data Center area in case of fire exigency. Suitable incline ramp for movement of the
Server hardware, PAC, UPS in Data Center shall be made by supplier. The list for the same may be submitted for
approval/ documentation.
B. Guidelines for Electrical Work
All electrical installation shall conform to the relevant Indian Standard Specifications and Indian Electricity Rules.
Safety : OHSAS 18001, ISO14000 related risk and aspect mitigation system has been established especially for
electrical and fire safety.
1. Source of power
Power will be made available by Owner at the incoming side of existing L.T.Panel at 415v, 3 Phase and N, 50Hz
from the distribution feeder. The distance between the Data Center and the distribution feeder is 50mts. Further
distribution of power to different loads like A/C panels, UPS power supply to Servers through DBs, shall be
designed, supplied, tested and commissioned by the supplier. Proper Incoming cable entries shall be planned
with special attention to plugging of conduits. The L.T. Panel shall have AUTO CHANGE OVER facility between
the generator and mains with proper interlocking. Incoming and outgoing electrical lines should have Transient
Voltage Surge Suppressors (TVSS) installed, primary TVSS just after the main LT switchboard and secondary
TVSS just before the UPS. The primary should take care of heavy transients (kilovolt range) caused by lightning
surges or HT surges and the secondary should take care of whatever manages to pass through (several hundred
volts in range) the main TVSS.
2. Power distribution
All Distribution Boards shall be aesthetically built, single front, non draw out. Main L.T. Panel shall have MCCBs
as incomer and outgoings with S/C withstand capacity of 35KA. L.T.Panel and all DBs shall have Digital
Ammeters and volt meters, one for each source. ON, OFF and TRIPPED indications shall be provided for all
incomers. For outgoings, ON indication shall be provided. All components shall be chosen from List of Preferred
makes. Power distribution network for Air-conditioning and illumination shall be in the scope of the supplier which
includes sub-distribution boards, concealed wiring, switch boards etc. Adequate redundancy shall be provided
while designing the distribution system. Spare power distribution boards for atleast 5 Nos. Racks at Data Center
should be provided. There shall be two redundant circuits from the UPS to the server racks.
3. Illumination
The level of illumination, type of fixtures and wiring shall be designed/ selected, supplied and erected,
commissioned and tested. However, the basis and selection of equipments shall be approved by Owner before
manufacturing/ procurement. IS 1913 General and Safety requirements for luminaries. IS 3646 Code of Practice
for Interior Illumination shall be followed. Illumination design shall include type of fixtures easily maintainable and
available of approved makes. The level of illumination in Data Center shall be 400 Lux. The luminaries shall be
glare free with optical mirror work. All ballasts for fluorescent fittings shall be high P.F. electronic ballasts. Normal
lighting system shall be fed from Raw power DBs whereas 10% of lights shall be fed from emergency power. The
emergency lights shall be located at Data Center, electrical panel room, including passage and emergency exit.
All switchboards shall be aesthetically built, concealed and of modular design. Lighting SDB & Raw power DB
shall be aesthetically built with recessed mounting consisting of MCB as incomer and ELCB as outgoing. Service
power outlets of 6/16 A with 16 A switch shall be provided at skirting level for maintenance purposes.
4. Cabling


Raceway design shall be adopted for electrical wiring and network wiring. Both the raceways with power cables
and data cables shall be separated by a distance of 400mm. To ensure unrestricted airflow of PAC crossing of
cabling raceway is not permitted on the under structure. All electrical cabling shall be done with 1100V grade
FRLS, PVC cable with stranded Copper Conductor. The sizing shall be based on current requirements, voltage
drop and short circuit withstand. Point wiring shall be done with 1100V grade CU. Cable FRLS, PVC/PVC of size
1 X 2.5mm2. All wiring shall be concealed. Cable installation shall be as per IS:1225.
5. Earthing
Earthing of electrical installation shall be done in accordance with IS:3043. There shall be three separate buses
for earthing system i.e. dedicated UPS Neutral Grounding, Technical earth (Low impedance) for Equipment and
Raised floor grids & panel body earthing. All the earths shall be kept equi-potential and shorted at ground level
only. Earthing station, with pipe electrode, necessary Civil/ Electrical work, CI cover, alternate layers of salt and
charcoal, etc. as per IS:3043 shall be provided in required numbers. Galvanized M.S. saddles shall be used for
clamping earth conductor. Flats shall be supported at interval not exceeding 1000mm and stranded wires at
intervals of 500mm Logic/RF earthing, grid shall be provided. All components, panels, cables, conduits shall be
chosen from list of approved make. The distance between LT panel and earth pit is 100 mts. Approval of Owner
shall be sought in case of any deviation from the list of preferred makes. The supplier is required to indicate the
following in their offer:
6. UPS Systems
It is proposed to have two UPS systems working in dual redundant mode, capable of feeding the power required
for equipments at Data Center. The dual redundant UPS shall provide power to servers, SAN, network equipment,
backup, other devices, Access Control System, CCTV, Smoke detection System, fire protection system, rodent
repellent system, water leakage detection system, emergency lighting etc.

These systems shall have three phase incoming and three phases out going. Redundancy shall be provided up to
the Server rack end by using Dual distribution system. The UPS System must operate under environmental
conditions. The UPS parameters shall be monitored remotely from the Systems Department.

The power requirement for all servers, storage, backup, network solution and common services such as access
control, CCTV, fire detection and suppression, emergency lighting except Precision A/C is to be estimated and
provision of the total UPS power requirements to be made. Break-up of power requirement for servers, storage,
backup and network devices shall be provided by Vendors for verification by Owner.
7. UPS Modes of Operation
The UPS shall be designed to operate as an ON LINE reverse transfer system in the following modes:
Normal
The critical AC load is continuously supplied by the UPS Inverter. The rectifier/ charger derives power from AC
Input source and supplies DC power to the Inverter while simultaneously load charging power reserve battery.
Emergency
Upon failure of AC Input power, the critical AC load is supplied by the Inverter, which without any switching
obtains power from the battery. There shall be no interruption in power to the critical load upon failure or
restoration of the AC input source. In case of AC power outage, the diesel generator would automatically be
started to provide power to the UPS. In the event of the DG set unable to start within reasonable time, the UPS
shall automatically shut down the SAP servers.

Automatic Mains Failure (AMF) control panel provided by Owner shall start up the DG set and transfer the loads
on to the DG sets on mains failure after a configurable delay time without requiring any human intervention.
Similarly on restoration of mains supply it shall be able to transfer the load to mains supply after a configurable
delay time and switch off the DG set automatically.


Recharge
Upon restoration of AC input power during the emergency mode of operation, the rectifier/ charger shall
automatically restart, walk-in and gradually assume the inverter and battery recharge loads.
Bypass
If the UPS be taken out of service for maintenance or repair or should the inverter overload capacity be exceeded,
static transfer switch shall perform reverse transfer of the load from the inverter to bypass source with no
interruption in the power to the critical AC load.

Both the UPS modules should be operated in parallel mode with equal load sharing. However each UPS will be
adequately sized to feed rated load. In case of trouble in one of the UPS section, the other UPS will continue to
feed the load while the faulty section will be isolated without interruption in the output. If both the UPS fails, the
load should be transferred to bypass with no interruption in power to the critical AC load. There should not be any
common parts in parallel circuit, which will lead to single point failure. If parallel circuit is removed both the UPSs
should be able to work independently without any modification. There should be independent battery bank
connected to each UPS with facility to connect both battery banks and rectifiers in parallel and if one of the battery
bank or rectifier fails, then other battery bank or rectifier should support both Inverters without interrupting the load.
The UPS shall be monitored from the Administration Room.
8. UPS Specification
Technical Specification
A Input
1 Input voltage 415V, 3 phase, 4 wires
2 Input voltage tolerance +15%, -20 %
3 Input frequency 50 Hz
4 Input frequency tolerance +/- 5 %
5 Nominal Input current during Normal running condition
6 Input circuit IGBT based PWM rectifier
7 Input Circuit harmonic distortion <5%
B Output
1 Module full load rating KVA/ KW
2 Rated voltage 415 V, 3 Ph, 4 wire
3 Rated current
4
Phase Voltage asymmetry
a] Balance load
b] 100% unbalanced load

1 %
2 %
5
Phase displacement
a] Balance load
b] 100% unbalanced load

120 deg. +/- 1 deg
120 deg. +/- 1 deg
6 Output power factor support capability
0.6 lag to unity

7 Internal oscillator stability +/- 0.1 %
8 Mains synchronization tracking +/- 1 Hz (settable to +/-2)
9 Max. rate of change of frequency 1 Hz. Per second
10
Output voltage harmonics
a] Linear load
b] Non-linear load (Crest factor of 3:1)

<2 %
<5 %
11 Crest Factor 3:1 or better
12 Overload rating
110% for 60 minutes,
125% for 10 minutes,
150% for 60 seconds


13 Overall Efficiency at 100 % load >90 %
14 Transient recovery time
Recovery to +/- 5 % in <4
msec.
C DC Characteristics
1 DC Bus voltage ripple <1 RMS
D Controls
1 Charger input MCCB
2 Inverter output MCCB
3 Standard controls to be specified
E Measuring Instruments
1
LCD panel for Measuring Input voltage per phase, frequency Output voltages,
Output currents and Frequency, Battery Voltage and Charging/ Discharging current.
Load in KVA, Load in KW, and percentage of load.
2
LCD panel should display status of the Battery capacity and backup Time in
minutes.
F Protections
1
RC surge suppressor, Sustained under voltage on input side, Phase loss on input
side, Negative sequence on input side, Semiconductor fuses in the lines for
thyristor, Snubber circuit for device dv/ dt protection, Charger input current limit,
HRC fuses for filter capacitors, Battery current limit, DC over voltage, Low battery,
Semiconductor fuses at inverter output, Overload, Over temperature for the inverter,
HRC fuses in the control circuit.
G Indications (Alarms)
1
Inverter Failure, Overload (if load exceeds 100%), Overload shutdown, Emergency
shutdown, Equipment over temperature, Maintenance Bypass ON, DC over voltage,
Low battery, Battery circuit breaker open, Battery on load, Mains failure, Rectifier
Failed or Off, Inverter Unsynchronized, Load on bypass, Output voltage error
Special features:
a) UPS shall be provided with SNMP hardware and software for remote diagnostics.
b) Microprocessor based digital control and redundant control power supply.
c) PC based monitoring, control and reporting unit.
i. Monitoring system performance with automatic generation of daily, weekly reports.
ii. RS. 485 communication port.
iii. Fan redundancy
d) Battery management system with battery diagnostics
Environnemental conditions:
Temp : Max. 50C
Humidity : 95% Rh
(Max temp. and Humidity do not occur simultaneously).

Acoustic noise : <60dBA at 1 meter from panel front
Cable Entry : From bottom
Ventilation : Forced air cooling with integral fans.
Battery details
Battery type : Lead Acid Plante / Sealed maintenance free (SMF)
Battery back up time : 30 minute with 100% load
Battery Make : As mentioned in Table-03 of Annexure-1
No of batteries : To specify


Expected battery life : 5 Year
Tests : As per IEC
Documents to be provided:
a) Operational and maintenance manual including card wise component details and PCB
b) Drawings
c) All acceptance and routine tests as per the specification and relevant standards shall be carried out.
Charges for these shall be deemed to be included in the equipment price.
C. Guide Lines for Air Conditioning Works
This part of specification provides technical parameters for design, manufacture, supply, installation testing and
commissioning of Air-conditioning system for the proposed Data Center. All items of equipment supplied shall be
complete in all respects and any item/accessory not covered in this specification but essential for proper design
and operation of equipment shall be included by the supplier.
i. The equipments shall be designed, assembled and tested in accordance with the latest relevant Indian
Standards Institution wherever applicable. In case where suitable Indian Standards are not available, the
equipments shall conform to generally accepted codes and practices and copies of the relevant standards
and regulations shall be submitted along with the quotation.
ii. All electrical equipments shall conform to the latest IS, Indian Electricity Regulations and earthing and
other provisions specified therein for installation and operation of electrical equipment. All equipments
shall conform to the provision of statutory and other regulations in force, such as Indian Explosives Act
and Factories Act, etc.
iii. All equipment shall be of reputed make. The material used and equipments supplied shall be new and
best of their respective kinds. Type and constructional features of individual equipments shall be such as
to ensure long life with minimum maintenance.
iv. All the name plates of the machinery as well as operating instructions shall be in English language.
Calibration of all instruments, dimensions and weights shall be in metric units.
v. All the equipments shall be suitably cleaned, painted and protected against corrosion and damage. Final
coats of paints of appropriate colour shall be applied after erection, before handing over the plant and
equipment.
vi. Layout of equipment shall be such as to facilitate easy and safe operation and maintenance, at the same
time ensuring maximum efficiency of the system. Suitable interlocking wherever necessary shall be done.
vii. All moving assemblies like compressor, fan etc. shall be mounted on vibration proof base.
1. Proposed Air Conditioning System
Following Air Conditioning Systems are proposed to be installed. As Data Centers require round the clock air
conditioning to maintain a temperature of 21 C 1C and relative humidity 50 % 5 %, Precision Air conditioning
units are proposed to be installed.
Design Data
Climate condition related data

Ambient conditions shall be assumed as follows:-
a) Summer
i. Dry Bulb Temperature : 44C to 19C
ii. Relative Humidity : 21% to 98%

b) Monsoon


ii. Relative Humidity : 55 to 98%

c) Winter
ii. Relative Humidity : 97% to 28%

d) Heat dissipation by the servers and other common services such as access control, CCTV, fire
detection and suppression, lightening shall be considered for design of Precision A/C.
2. Precision Air Conditioners
Data Center requires round the clock 365 days precision cooling to maintain temperature of 21C 1C and
relative humidity 50% 5%. The room air-conditioning system shall be a floor discharge unit designed specifically
for high sensible heat ratio applications such as Server and Computer rooms. The solution should be scalable to
address future load of servers.

For effective and uniform distribution of cooling, proper equipment layout planning with high CFM units to be
considered. Each precision air-conditioning system shall have the following features:
a) No. of units - N +1 (N working +1 standby).
The standby will be set in automatic rotation. (Where N stands for no. of units required based on heat
load calculation)
b) Flow direction - Downward flow
c) Filters efficiency - 95% down to 5 microns.
d) Type of load - High sensible heat load.
The system shall contain Scroll compressors, Evaporator, Humidifier, Condenser, and Thermostatic expansion
valve which shall be contained within the cabinet of the unit.
01 Cabinet Construction
The frame and panels shall be constructed of heavy gauge Zinc-anneal
corrosion resistant sheet steel. The fan section shall be insulated with
minimum 25 mm thick fire rated insulation. The cabinet shall be powder
coated and have a textured finish
02
Evaporator coil

The units shall be fitted with large surface area cooling coil with split coil
mechanism for dehumidification. The evaporator coil shall be constructed of
copper tubes and slit aluminium fins with frame and drip tray fabricated
from heavy gauge aluminium.
03
Compressor

Each air-conditioner shall be provided with Hermetic Scroll compressors.
Compressor shall have inbuilt overloads, and shall be mounted on anti-
vibration mountings.
04
Refrigeration circuit

The refrigeration circuit shall be direct expansion type and incorporate
hermetic scroll compressor. The system shall include a manual reset HP
and an auto reset LP switch, filter drier and charging port. A thermal
expansion valve, sight glass and filter drier shall be provided for each
circuit.
05
Blower

The blower shall be centrifugal type, double inlet, double width, statically
and dynamically balanced. Blower shall be driven by a high efficiency motor
with a self tensioning belt drive arrangement. The blower-motor assembly
shall be mounted on anti vibration mountings. Each unit to be provided with
multiple blowers.
06 Humidifier
The unit shall be in-built with Humidifier. Humidifier shall be provided by
boiling water in a high temperature polypropylene steam generator. The
humidifier shall be fully serviceable with replaceable electrodes.


07
Electrical heating

The electrical heating elements shall be of low watt finned tubular
construction. The heating circuit shall include dual safety protection through
loss of air and high temperature controls.
08
Air cooled
condenser

Condenser shall be the low profile, weather-proof type incorporating high
efficiency direct drive, external rotor motors with axial blade fans. The heat
rejection coil shall be constructed from copper tubes and aluminium fins.
The fan shall be selected for quiet operation and shall be suitable for 24
hours operation.
09
Controls

The standard controls shall be microprocessor based programmable PID
(Proportional, Integral and Derivative) logic controller that monitors, displays
and operates the precision cooling units, so that the environment is held
within desired specifications. The controller shall have a LCD display
screen, which shall be visible from the front of the unit without removing any
covers/external panels. The controls shall have separate indications for
a) Various modes of operation (cooling, heating, humidifying and
dehumidifying)
b) Alarm conditions (temperature high, wet floor and loss of air)
temperature and humidity.
c) Graphical displays of set temperature and humidity and achieved
temperature and humidity.
d) No airflow
e) Low humidifier water
f) Service intervals
g) Low battery
The system shall have a menu driven interface with supporting help screens
and shall use multi-protocol data communications. Access to the controller
settings shall be protected with passwords to prevent against unauthorized
access. Necessary interfaces shall be provided for remote monitoring of
temperature, RH and other parameters of the Air Conditioning systems from
the Admin Room in Systems Department.
The controls shall be integrated with the Building Management System and
capable of sending notifications to concerned person.
10
Safety precautions

a) High pressure trip - Manual reset for each compressor
b) Low pressure trip - Manual reset for each compressor
c) Single phasing preventers
d) Reverse phasing
e) Phase imbalancing
f) Phase failure
g) Overload tripping (MPCB) of all components
Air cooled condenser shall be installed by the side of the Data Center on
steel frame. Condenser and air-conditioner shall be suitably connected with
insulated refrigerant pipings. Condenser shall have heat rejection coil block,
fan-motor assembly with all necessary automation/interlocking
The PAC units shall auto start the redundant unit in case there is failure of any running PAC. The standby unit
shall continue to work till the failed unit is serviced and repaired. The unit shall be serviceable with a maximum
space of 1000mm from front.
3. Air Conditioning System Scope of Work / Supply


The scope of work covers design, engineering, manufacture/procurement, fabrication, factory testing, assembly,
and supply, storage at site, erection, testing, trial run and commissioning of air conditioning systems for proposed
Data Center of Owner. Briefly scope of work shall include but not limited to the following:
a) The supply, erection, testing & commissioning of precision air-conditioning units for Data Center. The
precision air-conditioning units shall be complete with Scroll compressors, Evaporator, Humidifier,
Condenser and Thermostatic expansion valve.
b) All civil and structural work required for above installation.
c) All insulation work for refrigerant piping, ducting etc.
d) All electrical works.
e) Supply and installation of minimum two numbers of digital humidity and temperature meters with data
logger at the Data Centers with display provision in the Control Cabin at Systems Department.
f) Any other job, not specified but required for the successful completion of air-conditioning job shall be in
the scope of work of successful supplier.
D. Fire Detection and Suppression
This specification outlines the requirements for a "Total Flood" Clean Agent - non Oxygen Depletion System
(ODS) & Zero Global Warming Potential (GWP), Fire Suppression System with automatic detection and control
for protection of Data Center, UPS, Management Console/ BMS/ EMS area. The work described in this
specification includes all engineering, labour, materials, equipment and service necessary, and required, to
complete and test the suppression system.
1. Applicable Standards
The design, equipment, installation, testing and maintenance of the Clean Agent Suppression System shall be in
accordance with the applicable requirements set forth in the latest edition of the following codes and standards:
National Fire Protection Association (NFPA) Standards:
a) NFPA 2001 Clean Agent Fire Extinguishing Systems
b) NFPA 70 National Electric Codes
c) NFPA 72 National Fire Alarm Code

The standards listed, as well as all other applicable codes, standards, and good engineering practices, shall be
used as minimum" design standards.
2. Requirements
The Suppression System installation shall be made in accordance with the drawings, specifications, and
applicable standards. Should a conflict occur between the drawings and specifications, the specifications shall
prevail.
3. Quality Assurance
The manufacturer of the suppression system hardware and detection components shall be ISO 9001 registered.
a) The name of the manufacturer shall appear on all major components.
b) All devices, components, and equipment shall be the products of the same manufacturer, or supplied by the
same manufacturer.
c) All devices, components, and equipment shall be new, standard products of the manufacturer's latest design
and suitable to perform the functions intended.
d) All devices and equipment shall be UL listed and/or FM approved.
e) Locks for all cabinets shall be keyed alike.
4. Installer


a) The installing contractor shall be trained by the supplier to design, install, test, and maintain fire suppression
systems.
b) When possible, the installing contractor shall employ a professional having more than 5 years of in line
experience, who will be responsible for this project.
c) The installing contractor shall be an experienced firm engaged in the installation of automatic clean agent, or
similar, fire suppression systems, in strict accordance with all applicable codes and standards.
d) The installing contractor must have a minimum of five (5) years experience in the design, installation, and
testing, of clean agent, or similar fire suppression systems.
5. Submittals
a) The installing contractor shall submit the following design information and drawings for approval prior to
starting work on this project:
i. Field installation layout drawings having a scale of not less than 1/8 in. =1 ft.- 0 in. or 1:100 detailing the
location of all agent storage tanks, nozzles, pipe runs, including pipe sizes and lengths, control panel(s),
detectors, manual pull stations, abort stations, audible and visual alarms, etc.
ii. Auxiliary details and information such as maintenance panels, door holders, special sealing requirements,
and equipment shutdown.
iii. Separate layouts, or drawings, shall be provided for each level, (i.e.; room, sub floor, and above ceiling)
and for mechanical and electrical work.
iv. Electrical layout drawings shall show the location of all devices and include point-to-point conduit runs
and a description of the method(s) used for detector mounting.
v. Provide an internal control panel wiring diagram which shall include power supply requirements and field
wiring termination points.
vi. A complete sequence of operation shall be submitted detailing all alarm devices, shutdown functions,
remote signaling, damper operation, time delay, and agent discharge for each zone or system.
b) Submit drawings, calculations and system component sheets to the Owner for approval & record.
6. System Requirements
System Description and Operation
a) The system shall be a Total Flood non ODS & Zero GWP Fire Suppression clean agent preferably Novec
1230 Fire Protection Fluid (Sapphire).
b) The system shall provide a Novec 1230 minimum design concentration of 4.2% by volume for Class A
hazards and a minimum of 5.85% by volume for Class B hazards in all areas and/or protected spaces, at the
minimum anticipated temperature within the protected area. System design shall not exceed 10% for normally
occupied spaces, adjusted for maximum space temperature anticipated, with provisions for room evacuation
before agent release.
c) The system shall be complete in all ways. It shall include a mechanical and electrical installation, all detection
and control equipment, agent storage containers, Novec 1230 agent, discharge nozzles, pipe and fittings,
manual release and abort stations, audible and visual alarm devices, auxiliary devices and controls,
shutdowns, alarm interface, advisory signs, functional checkout and testing, training and any other operations
necessary for a functional UL listed Sapphire Clean Agent suppression system.
d) Provide two (2) inspections during the first year of service: Inspections shall be made at 6-month intervals
commencing when the system is first placed into normal service.
e) The general contractor shall be responsible for sealing and securing the protected spaces against agent loss
and/or leakage during the 10-minute "hold" period.
f) The Very Early Smoke Detection and Alarm (VESDA) system for Data Center and cavity floor shall provide
the highest sensitivity appropriate for detecting a complete range of smoke particles produced in incipient
stage and real fires involving natural or synthetic materials. It comprises of an air sampling system, filter
assembly, aspiration system, detector and control system. The VESDA panels shall be located in the
respective protection areas.
g) The system(s) shall be actuated by a combination of ionization and photoelectric detectors installed for
maximum area coverage of 250 sq. ft. (23.2 sq. m) per detector, in both the room, under floor and above
ceiling protected spaces. If the airflow is one air change per minute, photoelectric detectors only shall be
installed for maximum area coverage of 125 sq. ft. (11.6 m) per detector. (Ref. NFPA No. 72.)


h) Detectors shall be Cross-Zoned detection requiring two detectors to be in alarm before release.

Automatic operation of each protected area shall be as follows:
a) Actuation of one (1) detector, within the system, shall:
i. Illuminate the "Alarm" lamp on the control panel face.
ii. Energize an alarm bell.
iii. Transfer auxiliary contacts, which can perform auxiliary system functions such as: Operate door
holder/closures on access doors; Transmit a signal to a fire alarm system; Shutdown PAC equipment.
b) Actuation of a 2nd detector, within the system, shall:
i. Illuminate the "Pre-Discharge lamp on the control panel face.
ii. Energize a pre-discharge horn/strobe device.
iii. Shut down the PAC system and/or close dampers.
iv. Start time-delay sequence (not to exceed 20 seconds).
v. System abort sequence is enabled at this time.
c) After completion of the time-delay sequence, the Sapphire Clean Agent system shall discharge and the
following shall occur:
i. Illuminate a "System Fire Red" lamp on the control panel face.
ii. Shutdown of all power to high-voltage equipment if any.
iii. Energize a visual indicator(s) outside the hazard in which the discharge occurred.
d) The system shall be capable of being actuated by manual discharge devices located at each hazard exit.
Operation of a manual device shall duplicate the sequence description above except that the time delays and
abort functions shall be bypassed. The manual discharge station shall be of the electrical actuation type and
shall be supervised at the main control panel.

7. General Requirements of material and equipment
a. The Sapphire Clean Agent system materials and equipment shall be standard products of the
supplier's latest design and suitable to perform all functions intended. When one or more pieces of
equipment must perform the same function(s), they shall be duplicates produced by one
manufacturer.
b. All devices and equipment shall be Underwriter Laboratories (U.L.) Listed and/or FM approved.
c. Each system shall have its own supply of clean agent.
d. The system design shall be modular type.
e. The areas below the false ceiling only shall be protected and there are no sub floors.
f. Systems shall be designed in accordance with the manufacturer's guidelines.
g. Each supply shall be located within the hazard area, or as near as possible, to reduce the amount of
pipe and fittings required to install the system. There shall be no reserve cylinders installed on to the
system. However, spare cylinders of suitable quantities shall be supplied and kept ready at Owners
stores for all the times.
h. The clean agent shall be stored in Sapphire Clean Agent storage tanks. Tanks shall be super-
pressurized with dry nitrogen to an operating pressure of 360 psi @ 70 F (24.8 bar at 21 C). Tanks
shall be of high-strength low alloy steel construction and conforming to NFPA 2001.
i. Tanks (master) shall be actuated by either a resetable electric actuator or by pneumatic means from
a nitrogen cartridge located in the releasing device. Explosive devices shall not be permitted.
j. Each tank shall have a pressure gauge and low pressure switch (optional) to provide visual and
electrical supervision of the container pressure. The low-pressure switch shall be wired to the control
panel to provide audible and visual "Trouble" alarms in the event the container pressure drops below
290 psi (20 bar). The pressure gauge shall be color coded to provide an easy, visual indication of
container pressure.
k. Tanks shall have a pressure relief provision that automatically operates before the internal nominal
pressure exceeds 730 psi (50 bar).
l. Engineered discharge nozzles shall be provided within the manufacturer's guidelines to distribute the
Novec 1230 agent throughout the protected spaces. The nozzles shall be designed to provide proper
agent quantity and distribution. Nozzles shall be available in 1/2 in. through 2 in. pipe sizes. Each size
shall be available in 180 and 360 distribution patterns.


m. Distribution piping and fittings shall be installed in accordance with the manufacturer's requirements,
NFPA 2001, and approved piping standards and guidelines. All distribution piping shall be installed by
qualified individuals using accepted practices and quality procedures. All piping shall be adequately
supported and anchored at all directional changes and nozzle locations.
i. All piping shall be reamed, blown clear and swabbed with suitable solvents to remove burrs, mill
varnish and cutting oils before assembly.
ii. All pipe joints should have grooved lock fittings for easy assembly and dismounting.
8. Agent
Agent shall not contain any Hydro fluorocarbons (HFC).
9. Control Panel
a) The control panel shall be an Autopulse releasing panel.
b) The detection control system and its components shall be UL listed and FM approved for use as a
local fire alarm system with releasing device service.
c) The control system shall perform all functions necessary to operate the system detection, actuation,
and auxiliary functions.
d) The control system shall include battery standby power to support 24 hours in standby and 5 minutes
in alarm.
e) The control system shall be microprocessor based, utilizing a distributed processing concept. A single
microprocessor failure shall not impact operation of additional modules in the system.
f) The control system shall be capable of supporting Cross Zoned Detection.
g) The control system shall supply integrated 2.0 amp (minimum) power supply circuitry.
h) Each control system shall contain four (4) initiating circuits:
i. Each circuit shall be capable of Class A (Style D) or Class B (Style A) operation.
ii. Each circuit shall be capable of operating up to fifteen (15) approved detectors or thirty (30)
detectors per system.
iii. Each circuit shall be capable of monitoring contact devices configured for manual release,
manual alarm, system abort, trouble input or auxiliary (non-fire) input.
i) Each control system shall contain release circuits for activation of a fire suppression system(s):
i. Each circuit shall be capable of Class B (Style Y) operation.
ii. Each circuit shall be rated for a minimum of 1.5 amp @ 24 VDC.
j) Each control system shall contain two (2) indicating appliance circuits for annunciation:
i. Each circuit shall be capable of Class A (Style B) or Class B (Style Y) operation.
ii. Each circuit shall be rated for a minimum of 1.5 amp @ 24 VDC.
k) Each control system shall provide an auxiliary power supply rated for 2 amps @ 24 VDC.
l) Each control system shall provide two (2) SPST relays: one for common alarm and one for common
trouble. Four (4) additional programmable relays can be added to each control system by adding a
relay module.
10. Detectors
a) The detectors shall be spaced and installed in accordance with the manufacturer's specifications and
the guidelines of NFPA 72.
b) The ionization detector and photoelectric smoke detector must be compatible with the control panel.
11. Manual Release (Electric)
a) The electric manual release shall be a dual action device which provides a means of manually
discharging the suppression system when used in conjunction with the detection system.
b) The manual release or manual pull station shall be a dual action device requiring two distinct
operations to initiate a system actuation.
c) Manual actuation shall bypass the time delay and abort functions and shall cause all release and
shutdown devices to operate in the same manner as if the system had operated automatically.
d) Manual release shall be located at each exit from the protected hazard.


E. Access Control
The Access Control System shall be used to serve the objective of allowing entry and exit to and from the
premises/ restricted areas within the facility to authorized personnel only. The system employed shall be based on
Biometric Technology for the Data Center, Management Console area. The readers shall be both side of each
door and shall be connected to Door Controller dedicated to that door. The components inclusive of (but not
limited to) the system are as follows:
a) Network Server
b) Card issue terminal PC
c) Application software
d) Controller
e) Finger print reader
f) Cables
The scope of work involves supply, installation, testing and commissioning of Access Control system for Data
Center with requisite GUI software, PC and database for monitoring the entry/exit by authorized persons.
Monitoring of system/ logs shall be done from the Systems Department.
F. Closed Circuit Television (CCTV) System
a) Closed Circuit Television (CCTV) System shall be provided for surveillance and record for post event
analysis. Products with UL listing and proven installation worldwide only shall be supplied.
b) The video output from individual camera locations shall be available on high resolution monitor via
Digital Video Recorder (DVR). Twisted pair telemetry shall be employed to control pan/tilt/zoom
functions. Viewing/Monitoring would be done from the Systems Department.
c) The Controls shall be based on Digital Video Recorders (DVR). The DVR shall combine the functions
of duplex multiplexing, video storage, control of cameras, alarm/ event detection, etc. The DVRs shall
be connected to the PC provided with user friendly GUI for remote monitoring. The DVR shall be
capable for multiple camera displays for live viewing or play back while recording, continuous motion
detection, alarm, pre alarm handling and schedule recording modes. Recording up to min. of 30
images per second, high speed searching shall be capable of backup management with external
storage device. The recorder shall provide programmable motion detection. Each camera shall be
customized for specific motion triggered recording with digital zoom.
d) The CCTV cameras shall be located in Data Center, entry passage and battery room.
e) The external DVD writer shall be used to archive the video image. PC shall be used for the
management of the system.
f) The scope includes provision of monitoring software, server with adequate disk space for storing
video data for 30 days, DVD writer, 21 inch LCD monitor (the monitor shall be used for BMS),
graphics card etc.
G. Pest/Rodent repellent system
Appropriate system of solution to keep away rodent/ cockroach/ pests from Data Center shall be provided by
Vendor.
H. Water Leak Detection System
Water leak detection cable shall be provisioned in the water prone areas of Data Center. Water leak detection
System shall be designed to protect the air-conditioned premises and to provide alert at the Systems Dept about


the leak in the AC systems. The system shall also be designed to trip the AC when the sensor is activated. Events
should be clearly reported on LCD/ LED display with full English language description of the nature of the fault in
the panel. The Water leak detection system shall comprise of Tape Sensors, Water Leak detection modules,
Condensation detectors, I/O modules and sounders all connected to a Control Panel.
I. Data Safes
Two sets of safes shall be used to keep the magnetic media, DAT drives, licenses and software media etc. The
safes should be completely fire-proof, dust proof, Pilferage proof, humidity proof, Magnetic and electrostatic proof.
The safes shall have facility to store the data tape backups for five years. Separate safes shall have facility to
store all licenses and software. The safe should be designed to withstand temperatures of around 1000 deg C for
60 min. One set of safes shall be kept in Systems Department and the other at a separate location. The safes
should have adequate capacity to store the data cartridges for the SAP System and Legacy backup for 5 years.
J. Acceptable Makes-Interior/Electrical Work/AC
S No. Material Preferred Makes
1 Aluminium sections Indal/ J indal/ Hindalco
2 Float Glass (Toughend) Saint Gobain/ Indo-Asahi/ Modifloat
3 Raised Access flooring United Insulations/Microtac
4 Under deck Insulation Armaduct/ Armaflex
5 Vitrified Ceramic tiles Nitco/ J ohnson/ Bell/ Asian
6 Fire Rated Door Shakthi Met door/ Godrej
7 Steel door Shakthi Met door/ Godrej
8 Fire rated glass Promat/ Schott
9 Aluminium Composite panel Alustrong/ Alucobond/ Alcopla/ Alstone
10 Panic Bar Assa abloy, Dorma, Honeywell, Europlex
11 Fire Proof Data Safe Godrej/ Methodex
12 Electrical Switches [modular] MK/ Crabtree/ Legrand/ Roma/Anchor/ Cona
13 Electrical Fittings Philips/ Bajaj/ Crompton
14 MCCB L&T/Siemens/ Legrand/ Havells
15 MCB Schneider/ Legrand/ Seimens/ Havells
16 MDS/STD Havells/ CGL/ Indokopp/ Schneider/ Legrand/ Seimens
17 HRC fuse Siemens/ L&T/ Alstom
18 Voltmeter/Ammeter [digital] AE/Meco/ IMP
19 Aux. Contactor L&T/ Siemens/ Telemechaniqe
20 Power Contactor L&T/ Siemens/Telemechaniqe
21 Push Button L&T/ Siemens/ Telemechaniqe
22 Signaling Lamp [LED type] Siemens/ L&T /Binay
23 Overload Relay L&T/Siemens/Telemechaniqe
24 Control/selector switches Siemens/ L&T/ Kaycee Industries
25 Terminal blocks Elmex Controls/ Connect Well /Phoenix
26 Control Transformers Siemens/ Indcoil Manufacturing Co/ National Engg. Corporation/ AE
27 UPS Siemens/ Emerson/ APC/ MGE/ILK/ Fuji
28 Maintenance Free Battery Excide
29 Precision Air-conditioning Emerson/ Stulz
30
VESDA and FM200 Based
Fire suppression System
Chemetron/ Hygood/ Siemens/ KIDDE/ Vision Systems
31 Access Control System Bosch/ Cardax/ HID/ Ramsdec/ Europlex
32 CCTV Bosch/ Europlex/ Baxal/ Panasonic
33 Digital Controllers Honeywell/ Tridium/ J ohnson Controls/ Seimens


Tabl e-4: Br oad Speci f i cat i ons f or Net wor k Layout
A. General
a) In office buildings, cable should be laid through GI Pipe for Fiber Optic (FO) Cable and PVC casing
and capping for UTP Cable.
b) installation work shall be carried out in a neatly manner by skilled, experienced and competent
workmen with experience in jointing and termination of data communication cables.
c) Cable runs shall be uniformly placed, properly supported and protected in an approved manner. All
bends in runs shall be well defined and made with due consideration to avoid sharp bending and
kinking of cables.
d) Cable installation shall be properly left at both the ends for proper termination without any tension and
to allow future expansion.
e) No joint shall be made at any intermediate point through runs of cables. In case of any damage
during the laying of the cables, the Vendor shall replace the complete segment of the cable without
any cost implication to Owner.
f) Holes in walls, ceiling etc. made during cable layout shall be plugged after drawing the cable.
g) Each equipment, panel and outgoing cable from the patch panels shall be ferruled and labeled.
Proper labeling and numbering shall also be provided on the outlets.
h) All UTP cabling within the false ceiling space or under raised flooring shall be encased inside PVC
pipe of minimum 25 mm dia and suitably supported. The layout shall be designed such a way that
cable does not cross.
i) Flexible GI pipe of suitable size should to be used for bending.
j) GI pipes carrying FO cable shall be colour coded at regular intervals of 2 Mtr. throughout the cable
run for over ground cable laying.
B. Surface /Concealed Fiber Optic Cable Laying
a) Backbone cables shall be installed separately from horizontal distribution cables.
b) Fiber slack shall be neatly coiled within the fiber termination panel. No slack loop shall be allowed
external to the fiber panel(s).
c) Each cable shall be individually attached to the respective termination panel by mechanical means.
d) Each fiber cable shall be stripped upon entering the termination panel and individual fiber routed in
the termination panel. All fiber should be terminated properly.
e) Each cable shall be clearly ferruled and labeled at the entrance to the termination point. Cables
labeled within the bundle shall not be acceptable.
f) Dust caps shall be installed on the connectors and couplings at all times unless physically connected.
g) GI pipe shall be used for routing cables embedded through concrete foundation/floor generally in
plant buildings. These shall be medium gauge, hot dip galvanized electric resistance welded (ERW)
screw type conforming to IS: 1239 (Part -I). All pipe fittings shall conform to IS: 1239 (Part -II).
h) G.I pipe shall generally be used for exposed cabling along building wall/surface, etc. in both plant and
non-plant buildings. Pipes shall be of galvanized steel, screwed type conforming to IS: 1650. The size
of pipe shall be a minimum of 25 mm dia and 2 mm thickness.
i) All pipe fittings, e.g. sockets, elbows, tees, bends, saddlers, locknuts, etc. as required for pipe cabling
with minimum of 25 mm dia steel pipe shall be made of hot dip galvanized steel and conforming to IS:
2667 and IS: 3887.
j) All GI pipe/conduits shall be provided with pull wires to facilitate cable pulling.
k) GI pipes shall be firmly supported in position by means of heavy gauge saddles either screwed in
concrete/brick walls using suitable plugs or screwed to MS brackets/cleats welded on to building
structure. The spacing between the supports for both horizontal and vertical runs shall not be more
than 1000 mm for straight runs. At bends or termination to junction/pull boxes, the nearest support
shall be 300 mm from such fittings.
l) Exposed GI pipes shall run parallel or perpendicular to column/building lines to match the existing
architectural arrangement. Embedded GI pipes, shall, however, run in direct lines with minimum
bends.


C. Surface /Concealed UTP Cable Laying
Cables shall be coiled in the surface-mount boxes if adequate space is present to house the cable coil without
exceeding the manufacturers bend radius. No more than 12 of slack shall be stored.Each cable type shall be
terminated as indicated below:
a) Cables shall be dressed and terminated in accordance with the recommendations made in the
TIA/EIA -568-B document, manufacturers recommendations and/or best industry practices.
b) Bend radius of the cable in the termination area shall not be less than 4 times the outside diameter of
the cable.
c) The cable jacket shall be maintained as close as possible to the termination point.
d) Cables shall be neatly bundled and dressed to their respective panels or blocks. Each panel or block
shall be fed by an individual bundle separated and dressed back to the point of cable entrance into
the rack or frame.
e) Each cable shall be clearly labeled on the cable jacket behind the patch panel at a location that can
be viewed without removing the bundle support ties. Cables labeled within the bundle, where the
label is obscured from view shall not be acceptable.
f) Cables shall be installed in continuous lengths from origin to destination (no splices) and the length
shall not exceed 80 meters.
g) Minimum of 150 mm axial spacing shall be maintained at all time between power and network cable.
h) Cables shall not be attached to ceiling grid or lighting support wires.
i) Any cable damaged or exceeding recommended installation parameters during installation should be
replaced by the contractor prior to final acceptance at no cost to the Owner.
j) A self-adhesive label or PVC marker ferules shall identify the Cables. A cable label shall be applied to
the cable behind the faceplate on a section of cable that can be accessed by removing the cover
plate. Similar label or marker ferrules shall also be placed on a section of the cable near to the patch
panel termination.
k) Pulling tension on 4-pair UTP cables shall not exceed 25-pounds for a single cable or cable bundle.
The pathway shall be adequately sized so as not to exceed the 80% cross-section fill of cables. The
pathway shall be securely installed in the facility.
l) For surface (Indoor) cable laying, good quality PVC Casing/Capping of minimum 25 mm width and 10
mm height shall be used. Rest of the specifications shall be same as B.
m) For surface (outdoor) cable laying, it is to be inserted in GI pipes and clamps on walls.
n) For shop floor cable laying, good quality GI pipe shall be used for insertion of cable in it and laid along
the structural columns, trusses, girders etc. with clamps fixed to the supports at all heights.
D. Laying of Underground Cable (All Types)
a) Underground cable shall be laid generally about 1.0 meter below finished ground level and shall be
provided with atleast 75 mm and cushioning both at top and bottom with brick top cover (min. 12
bricks per meter) and sand filing for mechanical protection, where power and network cable trenches
are run side by side, the axial spacing between power and network cables shall not be less than 300
mm.
b) The excavation of trenches shall be executed with vertical sides and the trenches shall be kept as
straight as possible. Width of trench shall be in accordance with the number of cables to be laid but in
any case shall not be less than 300 mm.
c) After cable laying, the trenches shall be back filled in layers with each layer being well rammed,
consolidated and sufficient allowance made for settlement. In case of road crossings, if the road has
to be dug for cable laying, the Vendor shall make good the damages of the road thus done. For
crossing of road, railway track and other services, cables in GI pipe shall be taken through GI pipe.
d) In each cable run some extra length shall be kept at a suitable point to enable one or two straight
through joints to be made in case the cable develops faults at a later date. Also when numbers of
cables are laid together, the cable length shall be adjusted to stagger the straight through joints.
e) Underground cables shall be generally laid in the utility alley along the road and cable shall follow
road layout. Where backbone cables and distribution cables are installed in a cable tray, backbone
cables shall be installed first and bundled separately from the horizontal distribution cables.


f) All cable crossings across railway tracks shall be done in a GI pipe that shall pass through another
pipe of suitable specification and diameter and the depth of the trench will be minimum 150 Cms from
ground.
g) For cable laying in areas having corrosion effect, like Cold Rolling Mill (Pickling Line), Silicon Steel
Mill (Pickling Line) and Coal Chemical, suitable PVC / Rubber coated GI pipe shall be used.
h) Suitable cable route markers shall be provided at the distance of every 200 meters on the cable route
and also at places or corners wherever the route of the cable changes.


Tabl e-05 Br oad Speci f i cat i ons f or Vi deo Conf er enci ng Equi pment & sof t war e

S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
1 Equipment
42 Wall-Mounted Plasma Screens
State-of-the Art Videoconferencing System Processor

Digital Mixer, Echo Canceller and Far End Feedback Reduction
Device

Wireless Touchpad Control Panel
Connection Device for PC Image Share

The E-Board system could be either a full electronic whiteboard or
a system that allows conversion of a normal whiteboard into an
electronic board.

Integration of Bandwidth Controller-Packet Shaper with Network
Management System

2 Interoperability Standard for IP, ISDN
H.323 (Multisite support enabled)
H.320 (ISDN Support provision)
SIP
3 Video standards
H.261
H.263 +
H.263 ++
H.264
4 Frame Rates (Point to point )
Minimum 30 frames per second
5 Video Inputs:
Integrated Main camera
Additional auxiliary camera(s)
Document Camera
DVDR port

PC/Laptop (SXGA) connection provision for PowerPoint
presentations etc

6 Video output:
DVD RW for recording
For Primary Display:
Plasma
Multimedia Projector
For Secondary Display:
Plasma
Multimedia Projector
7 Video format
PAL, NTSC
Graphics : XGA, SVGA, VGA, SXGA

Video Bandwidth (capable of operating at 256kbps onwards
bandwidth)


8
Integrated Main camera
Ultra quite , Ultra fast action pan /tilt / zoom
60 Field view or better
Tilt Range : +/- 15 (UP/ Down) or better
Pan Range : +/- 90 (left /right) or better
Total Field view : 180 or better
10 x zoom or better
Auto focus
Automatic white balance
Camera Preset local and far end
Standard based far end camera control (FECC)
Remotely operated snap shot
9 Video Resolution
Interlaced video (60 /50 field full screen video for NTSC / PAL )
NTSC: 4 SIF (704 x 480)
NTSC: SIF (352 x 240)
PAL: 4 CIF (704 x 576)
PAL: CIF (352 x 288)
Advanced Screen Layouts to display multiple locations
Picture-in-picture
10 Dual Video Support/Resolution

Dual Video Support to transmit PC/VCR/External camera and
presenter

XGA (1024 x 768) ,SVGA (800 x 480) for graphic display
People Video support for 4 CIF and SIF on second VGA display
11 Audio protocols
G.711, G.722.1, G.722, G.728 on IP or ISDN or Mixed calls
G.711, G.728 on IP/ ISDN
12 Audio Feature
Full duplex audio
Stereo
Mono
CD Quality
Instant Adaptation Echo Cancellation
Automatic Gain Control (AGC)
Voice Activated Camera Tracking
Automatic Noise Suppression (ANS)
Audio Mixer Mic, VCR, Telephone , Line in
Ability to connect Audio calls
13 Audio input
1 x Microphone
1 x RCA inputs for stereo or mono input DVD RW
1 x RCA for mixer
Support for Audio Conferencing minimum 3 mics
14 Audio output
Primary Audio output
Secondary Audio output
DVDR (mono & stereo)
15 Digital Tabletop/Ceiling Microphone Array


360 degree voice pick up ; 4.8 dB less reverberant than omni
microphone

Integrated mute button (local and far end)
16 Network interface support
Ethernet port : (10/100Mbps)
17 Network Features
Automatic IP/ISDN calling
Down speeding over IP and ISDN
Auto SPID detection and configuration
SNMP for enterprise management
Audio and video Error Concealment over IP ,ISDN and mixed call
Maximum call length digital timer
IP Address Conflict Warning
18 System Management / Directory Services
Software Up-gradation via ISDN, PC, LAN
Downloading CDR
Directory Services
19 H.323 Quality of Service Features
IP DiffServ
IP Precedence
TOS
RSVP
IP Packet Loss Recovery and J itter Control
20 Security
Secure password authentication
Administrative password
Management via HTTP, Telnet
SNMP security alerts
21 Encryption on IP/ISDN/Serial Ports
Software encryption on ISDN ,IP and serial / V.35
22 User Interface
User friendly graphical interface
23 Firewall Support
System is able to operate behind Firewall
24 Electrical
Auto sensing power supply
Operating voltage/power 110-240 VAC
50-60 Hz
25 Documentation

The system must come with complete documentation set involving
user guides, technical specifications, operation and maintenance
manuals etc.

Acceptable Makes for Video Conferencing System Polycom / Tandberg/LifeSize


Tabl e-06: Br oad Speci f i cat i ons f or I P Tel ephony Equi pment s & sof t war e
Offered
Yes/ No
Deviation/
Enhancement
1 User Features
1.1 Abbreviated Dial
1.2 Answer and answer release
1.3 Autoanswer and intercom
1.4 Barge
1.5 Callback busy, no reply to station
1.6 Call connection
1.7 Call coverage
1.8 Call forwardall (off net and on net)
1.9 Call forwardbusy
1.10 Call forwardno answer
1.11 Call hold and retrieve
1.12 Call J oin
1.13 Call park and pickup
1.14 Call pickup group-universal
1.15 Call status per line (state, duration, number)
1.16
Call waiting and retrieve (with configurable audible
alerting)

1.17 Calling Line Identification (CLID)
1.18
Calling Line Identification Restriction call by call
(CLIR)

1.19 Calling party name identification (CNID)
1.20 Conference Barge
1.21
Conference List and Drop any party (ad-hoc
conference)

1.22 Direct inward dial (DID)
1.23 Direct outward dial (DOD)
1.24 Directory dial from phonecorporate, personal

Directoriesmissed, placed, received calls list stored
on selected IP phones

1.25 Distinctive ring (on net vs. off net)
1.26 Distinctive ring per line appearance
1.27 Distinctive ring per phone
1.28 Drop last conference party (ad-hoc conferences)
1.29 Extension mobility support
1.30 Hands-free, full-duplex speakerphone
1.31
Hypertext Markup Language (HTML) help access
from phone

1.32 Immediate Divert to voicemail
1.33 Last number redial (off net and on net)
1.34 Malicious Call ID and Trace
1.35 Manager-assistant service (IPMA application)
- Proxy line support
1.36
Manager features: Immediate divert or transfer, do not
disturb, divert all calls, call intercept, call filtering on
CLID, intercom, speed dials.


Offered
Yes/ No
Deviation/
Enhancement
1.37
Assistant features: Intercom, immediate divert or
transfer, divert all calls, manager call handling through
assistant console application

- Shared Line support
1.38
Manager features: Immediate divert or transfer, do not
disturb, intercom, speed dials, barge, direct transfer,
join.

1.39
Assistant features: Handle calls for their managers;
View manager status and calls; Create speed dials for
frequently used numbers; Search for people in the
Corporate/Call Manager directory, handle calls on
their own lines, immediate divert or transfer, intercom,
barge, privacy, multiple calls per line, direct transfer,
join, send DTMF digits from console, MWI status of
managers phone.

- System capabilities: Multiple managers per
assistant, redundant service

1.40 Message waiting indication
1.41
Multiparty conferenceAd hoc with add-on, meet-me
features

1.42 Multiple calls per line appearance
1.43 Multiple line appearances per phone
1.44 Music-on-hold
1.45 Mute capability from speakerphone and handset
1.46 On-hook dialing
1.47 Operator attendantAttendant Console
- Call Queuing
- Broadcast Hunting
- Shared line support
1.48 Privacy
1.49
Real-time QoS statistics through HTTP browser to
phone

1.50
Recent dial listCalls to phone, calls from phone,
autodial, and edit dial

1.51
Service URLsingle button access to IP Phone
Service

1.52
Single-button data collaboration on softphonechat,
whiteboard, and application sharing

1.53
Single directory number, multiple phonesBridged
line appearances

1.54 Speed dialMultiple speed dials per phone
1.55 Station volume controls (audio, ringer)
1.56 Transfer
- Blind
- Consultative
- Direct Transfer of two parties on a line.
1.57
User-configured speed dial and call forward through
Web access

1.58 Video (SCCP and H.323)


Offered
Yes/ No
Deviation/
Enhancement
1.59 Web services access from phone
2 Summary of Administrative Features
2.1
Application discovery and registration to SNMP
manager

2.2
AVVID XML Layer (AXL) Simple Object Access
Protocol (SOAP) Application Programming Interface
with performance and real-time information.

2.3 Bulk Admin Tool (BAT)
2.4 Call detail records (CDRs)
2.5 CDR Analysis and Reporting Tool (CAR)
2.6 Call forward reason code delivery
2.7
Centralized, replicated configuration database,
distributed Web-based management viewers

2.8 Configurable and default ringer WAV files per phone
2.9 Configurable Call Forward Display
2.10 Database automated change notification
2.11 Date and time display format configurable per phone
2.12 Debug information to common syslog file
2.13 Device addition through wizards
2.14
Device-downloadable feature upgradesPhones,
hardware transcoder resource, hardware conference
bridge resource, VoIP gateway resource

2.15
Device groups and pools for large system
management

2.16
Device mapping toolIP address to Media Access
Control (MAC) address

2.17
Dynamic Host Configuration Protocol (DHCP) block IP
assignmentPhones and gateways

2.18 Dialed Number Analyzer (DNA)
2.19
Dialed number translation table (inbound and
outbound translation)

2.20 Dialed number identification service (DNIS)
2.21 Enhanced 911 service
2.22
H.323-compliant interface to H.323 clients, gateways,
and gatekeepers

2.23 J TAPI 2.0 computer telephony interface
2.24
Lightweight Directory Access Protocol (LDAP) Version
3 directory interface to selected vendor's LDAP
directories

- Active directory
2.25 Multilevel Administration Access (MLA)
2.26
MGCP signaling and control to selected VoIP
gateways

2.27
Native supplementary services support to H.323
gateways

2.28
Paperless phone DNISDisplay-driven button labels
on phones

2.29
Performance-monitoring SNMP statistics from
applications to SNMP manager or to operating system
performance monitor


Offered
Yes/ No
Deviation/
Enhancement
2.30 QoS statistics recorded per call
2.31
Redirected DNIS (RDNIS), inbound, outbound (to
H.323 devices)

2.32 Select specified line appearance to ring
2.33 Select specified phone to ring
2.34 Single CDR per cluster
2.35 Single point system and device configuration
2.36
Sortable component inventory list by device, user, or
line

2.37
System event reportingto common syslog or
operating system event viewer

2.38 TAPI 2.1 computer telephony interface
2.39 Time-zone configurable per phone
2.40 Tool for Auto-Registered Phones Support (TAPS)
2.41
Extended Markup Language (XML) API into IP
phones (IP Phone 794x/796X)

2.42 Zero-cost automated phone moves
2.43 Zero-cost phone adds
3 IP Phones
3.1 Should have an LCD display
3.2 Multiple ring tones
3.3 A hearing-aid-compatible handset
3.4 G.711 and G.729a audio compression
3.5
H.323 compatible and Microsoft NetMeeting
compatibility

3.6
An IP address assignmentDHCP client or statically
configured

3.7
Comfort noise generation and voice activity detection
(VAD) programming on a system basis

3.8 The phone should also includes the following settings:
3.9 Display contrast
3.10 Ring type
3.11 Network configuration
3.12 Call status
4 Calling Features
4.1 The phone should also include the followings:
4.2 Multi-line appearance
4.3 Calling name and number display
4.4 Call waiting
4.5 Call forward
4.6 Call transfer
4.7 Three-way calling (conference)
4.8 Pre-dialing before sending
4.9 Redial
4.10 Call hold / resume
4.11 Call mute
4.12 Call park


Offered
Yes/ No
Deviation/
Enhancement
4.13 Call pick-up / group pick-up
4.14 "You Have Voice Mail" message on display
4.15 Hotkey for keypad lock
4.16 Hotkey for voice-mail access
4.17 Nine speed dials configurable in the set
4.18 Programmable speed-dial hotkeys 2-9
4.19
Comfort noise generation (CNG), voice activity
detection (VAD), adaptive jitter buffer, and echo
cancellation

4.20
Language support: English, French, German in the
first release

4.21 Local phone book
4.22 Time / date display
4.23 Keypad lock / vibration icon indicators
4.24 Idle / call state-based soft-keys
5 Network Features
5.1
Automatic IEEE 802.1q (virtual LAN [VLAN])
configuration

5.2
G.711a, G.711u, and G.729ab audiocompression
coders-decoders (codecs)

5.3 Integrated Ethernet switch
5.4
10/100BASE-T Ethernet connection through an RJ -45
interface for LAN connectivity

5.5
software upgrade supported using a Trivial File
Transfer Protocol (TFTP) server

5.6
Provisioning of network parameters through Dynamic
Host Configuration Protocol (DHCP)

5.7
Voice activity detection, silence suppression, comfort-
noise generation, and error concealment

6 Protocols Supported
6.1 Terminal Control Protocol
6.2 SIP (RFC 2543)
7 Power Supply
7.1 Inline power
7.2
Power can also be supplied locally using an optional
AC to 48-VDC power adapter (CP-PWR-CUBE)

8 Reports
8.1 Administrative Access Activity Report
8.2 AMIS Out Traffic Report
8.3 AMIS In Traffic Report
8.4 Call Handler Traffic Report
8.5 Distribution Lists Report
8.6 Event Log Report
8.7 Failed Login Report
8.8 Outcall Billing Report
8.9 Port Usage Report
8.10 Subscribers Report
8.11 Subscriber Message Activity Report


Offered
Yes/ No
Deviation/
Enhancement
8.12 System Configuration Report
8.13 Transfer Billing Report
8.14 Unresolved References Report
9 IP Based Voice / Video / Web Conferencing Bridge
9.1
Appliance based solution with necessary hardware
and software

9.2 Client software Compatibility
9.2.1
Operating Systems : Windows 2000 Pro (SP2 or
later), Windows 2000(SP2 or later), Windows 2000
Advanced Server (SP2 or later), Windows XP (SP1 or
later), or Windows Vista (Business or Enterprise),
Red Hat 9 or Red Hat Enterprise Linux 3 or later, Sun
Solaris9 or 10

9.2.2
Browser: Internet Explorer 5.5 or later; Netscape 7.1
or later, Mozilla 1.6 or later; or Firefox 1.0.3 or later

9.2.3 Adobe Flash Player: 8 or later
9.3 Protocol Support
9.3.1 H.323 v4
9.3.2 SIP (RFC 3261)
9.3.3 G.711 and G.729a
9.3.4 Real-Time Transport Protocol (RTP; RFC 3550)
9.3.5
RTP Payload for Dual Tone Multifrequency (DTMF])
Digits (RFC 2833)

9.3.6 Session Description Protocol (SDP; RFC 2327)
9.3.7 IPv4
9.3.8 LDAPv3
9.3.9 SMTP (RFC 2821)
9.3.10 SNMP Versions 1, 2c, and 3
9.3.11 HTTPv1.1
9.3.12
SSL Versions 2 and 3 (optional; customer provides
certificates obtained from a broadly trusted certificate
authority)

9.3.13 Network Time Protocol (NTP) Versions 3 and 4
9.4 Network connectivity and bandwidth
9.4.1
Two 100-Mbps or faster Ethernet connections for
server

9.4.2 For voice only, up to 84 Kbps in each direction
9.4.3
For Video Conference: 64 to 768 kbps (quality
increases with bit rate)

9.4.4 Web conference: At least a 56-kbps or faster
9.5 Management
9.5.1
Monitoring and alarming are supported through the
Simple Network Management Protocol (SNMP)

9.5.2
The appliance should be accessible through CLI /
HTTP or HTTPS for configuration and management
purpose

10 IP Based Voice Mail Solution
10.1 System Capability
10.1.1 Should provide intelligent voice messaging system for


Offered
Yes/ No
Deviation/
Enhancement
minimum of 300 users & 16 voicemail ports,
10.1.2
Should allow comfortable & convenient way for users
to interact with the system, selectable telephone user
interface , support for desktop interface with visual
access to voice messages using IMAP or a dedicated
Web browser,

10.1.3
Should support Session Initiation Protocol (SIP) proxy
servers, designated SIP phones and clients and SIP-
enabled access gateways,

10.1.4
Should leverage communications infrastructure
investment by integrating with IP PBX and traditional
telephone systems. Should support Intuitive browser-
based system administration console and tools to
simplify installation, maintenance, and daily use and
enable maintenance from any PC on the network

10.1.5
Should support Innovative use of streaming media
providing efficient audio delivery, Should support
Fault-tolerant system tools including robust security,
file replication, event logging

10.2 Message Access
10.2.1
Play and process messages (repeat, reply, forward,
delete, save, mark as new, hear day or time stamp, or
skip to the next message)

10.2.2
Reverse, pause, or fast-forward messages during
playback

10.2.3 Control volume and speed during message playback
10.2.4 Pause or resume during message recording
10.2.5 Address messages to multiple recipients
10.2.6
Support for searching for messages by caller ID,
name, or extension in saved messages

10.2.7
Record messages and mark them as regular, urgent,
private, or secure/request a return receipt

10.2.8
Switch between spelling name and extension when
addressing a message

10.2.9 Define rules to route incoming calls by caller
10.2.10 Define rules to route incoming calls by time of day
10.3 End User Features
10.3.1 Support for customizable message notification options
10.3.2
Support for different personal greetings (alternate,
busy, internal, off-hours, standard)

10.3.3 Passwords protection for listening the message
10.3.4
Support for specifying the order in which messages
are presented over the phone by message type
(voice, fax, e-mail), urgency, or LIFO/FIFO

10.3.5
Create private distribution lists and address messages
to them via TUI or GUI

10.3.6
Support for setting expiration date for any personal
greeting

10.3.7
Support for message notification for new messages
via SMTP text, pagers, and SMS text messaging for
mobile users. Should Support SMPP 3.4 protocol for


Offered
Yes/ No
Deviation/
Enhancement
interoperability with all major SMS center providers
10.3.8 Support for sending additional notification types if a
message is not retrieved.

10.3.9 The system should have message-waiting indicator
(MWI)

10.3.10 Should support Music on Hold
10.4 System Administration Features
10.4.1
Should be able to integrate with industry standard IP
PBX system

10.4.2 Should be able to provides native support for SIP
proxy servers, designated SIP phones and clients,
and SIP-enabled access gateways

10.4.3 Should have browser based system administration
console and tools to simplify installation, maintenance,
and daily use and allow maintenance from any PC on
the network.

10.4.4 Should have option to enable end users to manage
more of their own accounts, and thus decentralizing
routine administration.

10.4.5 Should have support for Event Logging
10.4.6 Should support automatic and manual failover
10.4.7 Should provide warning when mailbox is full
10.4.8 Should support day and time stamps for messages
10.4.9 Should provide directory search facility by spelling
user name

10.4.10 Once integrated with the proposed IP PBX, the
system should support encrypted Skinny Client
Control Protocol (SCCP) and Secure Real-Time
Transport Protocol (SRTP).

10.5 The system should provide the following Reports
10.5.1 Administrative Access Activity Report
10.5.2 Call Handler Traffic Report
10.5.3 Distribution Lists Report
10.5.4 Event Log Report
10.5.5 Outcall Billing Report
10.5.6 Port Usage Report
10.5.7 Users Failed Login Report
10.5.8 User Message Activity Report
10.5.9 System Configuration Report
10.5.10 Transfer Call Billing Report
10.5.11 User Access Activity Report
10.5.12 User Lockout Report

Acceptable Makes for IP Telephony System Cisco/Nortel/Avaya


Tabl e-07: Br oad Speci f i cat i ons f or Emai l Sol ut i on
Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
1 Messaging server
1.1
Should be able to support and enable users to connect using the
desktop/ thick mail clients like MS Outlook, Lotus Notes, Mozilla
Thunder Bird, Evolution, Netscape Communicator and Outlook
Express using industry standard protocols like
POP3/IMAP/HTTP/SMT

1.2 Should support multiple domains on a single system
1.3
Should support recovery or restoration of single mailbox without
impacting/ downtime for other users in online and offline mode

1.4
Should support storage of any file format and should allow users to
upload and download content from the messaging system.

1.5
Should support full-text search on each message store database
including scheduled indexing for faster search capabilities from the
messaging client (browser and rich client)

1.6 The messaging store should support Server and Client side rules.
1.7
Should be capable of scheduling message delivery by date and time
both by user and administrator

1.8
Should be capable of limiting message storage space for each user
by message store database

1.9 Should be able to prioritize a message sent by the user
1.10
Should support online addition of additional storage in to the System
as and when required

1.11
Should support message archival and journaling on the Server to
comply with security and auditing requirements

1.12
Should support shared message stores like Notice Board or Bulletin
Board. Also these stores should support access control with variety
of permission set.

1.13
Should support access of all mailbox folders (Inbox, Calendar,
Shared Folders, etc) through the browser by providing user friendly
URLs.

1.14
Should support online maintenance of message store databases
which can be scheduled. Should also support restoration of
mailboxes to active messaging store without the need of additional
steps or servers

1.15 Should support cumulative and non-cumulative transaction logging
1.16
Should support virtual partitioning of the messaging system protocols
(including POP/SMTP/IMAP/HTTP protocols) for higher scalability

1.17
Should support hosting messaging sub-systems by role (like
protocol, message storage, directory database, message routing,
etc.) on more than one physical server or on the same server using
partitioning

1.18
Should support high availability and clustering like active-passive,
active-active.

1.19 Should be able to specify data which needs to be clustered
1.20
Should support Load Balancing for the web servers that render web
pages to browser based messaging client.

2 Groups/Mailing Lists
2.1
Mailing Lists application is part of (or built in to) the core messaging
application being proposed


Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
2.2 The solution should be able to populate lists from Directory Server.
2.3
Automatic updates of the mail list, when a user is added to a group
where the mail list has been defined for the same group.

2.4 Web based list administration for nearly all tasks.
2.5
Privacy features such as moderation, open and closed list
subscription policies, private membership rosters and sender-based
filters.

2.6
Automatic web based archiving built-in with support for private and
public archives and hooks for external archivers.

2.7 Integrated auto-replies
2.8 Integrated bounce detection within an extensible framework.
2.9 Integrated spam detection, and MIME-based content filtering
3 Features of Message Transfer Agent (MTA)
3.1 The MTA should allow relaying mails from the authenticated users.
3.2
The MTA should allow relaying of the mails from the clients in the
trusted network or to the domains that are configured as authorized
relay destination.

3.3
MTA should allow a user account to have more than one email
address associated with it. i.e., should have aliasing feature.

3.4
MTA should have Delivery Status Notification providing an e-mail
sender ability to specify success, failure, delay or none of the
message.

3.5
The MTA should have option to define the maximum message size
on a global/group/user level basis.

3.6
MTA should be capable of handling bulk mailing, limiting number of
recipients and message size.

3.7
The MTA should do the segregation of queues into inbound and
outbound on the same server and also across servers.

3.8
MTA should be able set the parameters for controlling the queue
such as concurrency delivery, queue lifetime, response timeout,
connect timeout and bounce mail lifetime.

3.9
MTA should provide queue handling such as delete, redirect,
flushing.

3.10 The MTA should provide scheduling of mails queue based on priority.
3.11 The MTA should be able to define the maximum recipients per mail
3.12
The MTA should support for sending mails in graphics, audio, video
files and text in multilingual.

3.13
The MTA and other components proposed in the solution should be
protected from the virus and spam attacks using the Anti-Virus and
Anti-Spam solution proposed.

3.14
The MTA should be capable of providing SSL/TLS and S/MIME
support for encrypted communication.

3.15
The MTA should be able to validate sender domain in DNS (Sender
Policy Framework, Domain-Keys and RDNS look ups).

3.16
The MTA should be able to verify the local domain users exist in
directory server or not.

3.17
The messaging system should provide an option to block, discard,
bounced and route SPAM mails to an alternate mailbox at the server
level.

3.18
The messaging system should be capable to define blacklist/ white
list senders, domains at the global level to reduce SPAM and virus


Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
mails.
3.19
The messaging system should provide an option of subject rewriting,
header appending in case of detection of virus or SPAM mail.

3.20
The messaging system should provide proactive blocking of SPAM
by referring to Real Time Block Lists (RBLs) at the MTA level.

3.21
The messaging system should provide a facility to take action on a
SPAM mail to quarantine, delete, reject or bounce.

4 Disclaimer Facility
4.1
Every outgoing mail should be appended with a Disclaimer statement
preset by the Administrator at the global level.

4.2 The system administrator should be able to change the disclaimer.
4.3
Should support server side out-of-office reply capabilities. Users can
customize response and select filters that determine which message
senders are to receive the notification

5 Storage format
5.1
Storage Format should implement an indexing feature for quick
retrieval of the mails.

5.2 Support for unlimited mailbox size.
6 Quota System
6.1 The system administrator should be able to set the quota
6.2
There should be a facility for defining the quota by the administrator
at global, group and user level by the administrator for all the users.

6.3
The system administrator should have an option to define the
threshold level limits for the user mailbox quota.

6.4
An email message needs to be send to user with the Quota warning
on reaching defined threshold value.

6.5
Visual display of the actual usage of allocated quota for the users
over the web interface.

6.6
There should be a GUI interface (Web / Console) for quota
administration for the administrator.

6.7
Message De-duping: The System should not duplicate the message
addressed to multiple recipients in to each mailbox in the system.

7 Desktop/Thick Mail Client
7.1
When composing message in thick mail client, addresses auto-
complete as they are being typed, including a dynamically updated
selection dialog when multiple addresses match.

7.2
The application should support composing of messages in major
International Languages.

7.3
The Desktop mail client should be able to set priority of the
messages like high, normal and low.

7.4
The desktop mail client should be able to schedule the delivery of the
messages and also the expiry of the messages.

7.5 Desktop/Thick Mail Client should have following indicative features:

Support for SMTP, IMAP and POP mail protocols, as well as HTML
mail formatting.

Easily import your existing email accounts and messages.
Flagging Option for mails.

Powerful quick search based on senders, recipients, message,
subject, data, status etc.

Spell check facility as you type.


Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
Advanced message filtering rules.
J unk Mail Filters and Anti-Phishing Protection.

Enterprise and Government grade security features including
S/MIME, digital signing, message encryption, support for certificates
and security devices.

Attachments are never run without the express permission of the
user, protecting the users system from worms and viruses.

It should have an option to get updates from the central server.
Personal and global Address Book.
Support for LDAP/Directory Services.
Display of Quota limits.
Calendar, Group Scheduling, Personal Task Management.
Mail Archiving to local disk and server side.
7.6
Welcome Page should be customizable and allow users to display
information they need in the way that they want.

7.7
Data sent over the network can be compressed for more efficient
network utilization.

7.8
Allow multiple people to share a single PC. The thick mail client
software should have features for creating multiple-user profiles on a
single PC with separate message stores, allowing users to access
their personal data securely while sharing common resources.

7.9
Should support multiple archive policies and destinations. Save
valuable contents and retrieve them whenever they are needed.

7.10 Viewing, creating, and scheduling calendar entries and meetings.
7.11
Off-line support for all Personal Information Management (PIM)
functionality.

7.12
Should allow the user to bring a copy of the servers directory catalog
off-line.

7.13
Group Calendaring Allow users to manage another users calendar.
Can compose and accept/decline meeting invitations. Auto
Accept/Decline of invitations.

7.14 Should support Task Assignment.
7.15 Should provide for support for J ournal Entries.
7.16 Support for Drag and Drop Attachments.
7.17 Should support for Mail Box Delegation.
7.18 Should be able to tentatively accept/draft meetings.
7.19 Should provide for Calendar Preferences like Default Appointment
7.20 Duration, Calendar Entry Type, Auto processing invitations.
7.21
Should Print multiple Calendar formats:
Daily
Weekly
Monthly
Calendar List
To-do List
Trifold

8 Web Interface
8.1
All Web mail functionality should be accessible through all major
browsers like: Internet Explorer, Mozilla Firefox and Netscape; It
should be compliant to HTTP-1.0 and HTTP-1.1

8.2 Rich, interactive, web-based interface for end user functions (access


Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
via HTTP or HTTPS)
8.3
The Server should sense the available bandwidth and provide or
disable the rich feature functionalities in the web interface.

8.4
The Web interface automatically updates to display messages and
other updates (without refreshing the browser or users intervention).

8.5
The Web mail session idle time should be configurable by the
administrator at the global level

8.6
Secure logout from Web mail client to prevent unauthorized access
to mail pages after sign out.

8.7 Online end user help accessible directly from the end user interface.
8.8
Ability to customize look and feel, logo, colour themes, behaviour,
etc.

8.9
Ability to use custom logos in the web interface. Customisable look
and feel of the Webmail client. (This will be approved by Owner
before deployment.)

8.10
Ability to display Banner Ads in the Web Mail interface in the
Browser; Administrators should be able to select the Ads and display
selectively to a group of users or users individually.

8.11 Users can search from within the Web Client.
8.12
Web interface should provide the capability for dragging and
dropping attachments and an ability to check the size of the attached
documents.

8.13
Addresses auto-complete as they are being typed, including a
dynamically updated selection dialog when multiple addresses
match.

8.14
Ability to assign tags/categories to To Do, Contacts, Calendar
entries. Ability to assign tags to mail messages and configure alarms.

8.15
Ability to render and create messages, appointments, and web
documents in HTML format and Text format.

8.16
Built-in Rich text editor for composing messages with support for
colour, fonts, attributes, font size, hyperlinks, etc.

8.18
Option to check and correct spelling while composing a mail
message, calendar appointment, or web Document using an
interactive spell check session

8.19
Ability to delegate access to mail files and allow users to decide level
of access needs to be provided.

8.20
Ability to choose from users in personal Address Books, shared
Address Books, or the Global Address List.

8.21 Ability to view attachments in HTML format.
8.22 Should have support for folder nesting (folders within folders).
8.23 The user should be able to append a text signature.
8.24
Should show Public Folders/discussion databases to all users who
have been granted rights to view them.

8.25 User definable Personal folders to organize mail.
8.26
Global address book for wide list of contacts, group mailing feature
etc.

8.27
Built-in support for displaying complete web interface in Hindi and
other major Indian languages (specify languages) with Unicode
support.

8.28
Facility for automated installation of the required font and other
resources on the client machine from the mail server itself or


Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
dynamic font support.
8.29
Ability to take the recipients digital certificate from a central server or
from the users personal address book in case the mail is to be
encrypted.

8.30 Feature to send and receive files as attachments.
8.31
Multiple POP accounts-Universal Inbox to collect mail from various
dispersed POP accounts into one account.

8.32 Send multiple attachments of any file type.
8.33 Selection of multiple files as attachments in a single click.
8.34
Read receipt request - while composing a message, user can mark
the message to request for a read receipt notification from the
recipient and delivery status notification.

8.35
Message Priority feature to set priority of messages while composing
them.

8.36
Delete (mark for deletion), Undelete (recover from errors) and Purge
(permanently delete) messages.

8.37 Filtering of incoming mails based on user definable filtering rules.
8.38
Webmail user should be able to send and receive files as MIME
attachments.

8.39
User of the Webmail interface should be able to see full message
headers and able to expanding or collapse the Header Info view.

8.40 Webmail interface should have features for notification of new mails.
8.41
Organization wide Address lookup for Web email interface should be
there.

8.42
Webmail address book should support auto completion of email
address.

8.43
Webmail interface should have support for spell check at the time of
composing the mail.

8.44
Webmail interface should support for composing the mail in HTML
and plain text format.

8.45
User should be able to define the rules for sorting mails and moving
mails to folders.

8.46
Webmail interface should have an integrated calender providing the
following features: shared calendar, to-do lists, event scheduler and
reminders.

8.47
The user should be able to change the password through web
interface.

8.48
Forgot Password functionality should provide facility for the user to
reset the password.

8.49
User should be able to login to proposed mail server, by entering
user name and password one time only without entering the domain
name.

8.50
User should be able to customize the look and feel of the webmail
interface.

8.51
User should be able to mark mails as read or unread and maintain
flags for follow ups.

8.52
Mail sorting based on fields: unread, attachments, from, subject,
message, date and size.

8.53
The Webmail interface should provide feature to search messages
based on: From, To ,Cc, Bcc, Subject and body but not limited to
these, search in the folders and also advance search capabilities.


Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
8.54 User should able to maintain his own sender block list.
8.55
Runtime scanning of attachment for virus while composing the
message.

8.56
Webmail should provide feature of auto saving of message while
composing.

8.57
Should provide option to check mails during low bandwidth
connection using Basic Mail client functionality.

8.58
Should provide ability to categorize the calendar based on user
defined categories and colour coding.

8.59
Should provide ability to auto complete the recipient address for
recent recipients.

8.60
Should provide an embedded player to play attached media files
without requiring to open the attachment with a separate application.

8.61
Should provide ability to preview commonly used file attachments
without requiring separate application & downloading the attachment.

8.62
Should provide ability to access delegated mailbox from the logged
on Webmail client.

8.63
Should provide ability to view organizational hierarchy of the recipient
from the company address book.

8.64
Should provide ability to add sender to - Blocked Sender list or Safe
sender list.

8.65
Should provide ability to view Calendar details for selected dates
apart from default day, week, and monthly view.

8.66
Should provide flexibility to Drag drop calendar items between
different days and send the meeting updates to the recipients
automatically.

8.67
Should provide ability to create Tasks & categorize them based on
colour/text.

8.68
Should provide ability to import/export addresses from
Global/Personal address book from/to a standard format (e.g., CSV
format).

8.69
User should be able to select the priority of the follow-up (low,
normal, urgent), indicated by a flag in the inbox. Additionally, user
should be capable of setting an alarm as a reminder of a follow-up
action, like marking an e-mail for follow-up on the

8.70
The follow-up feature should allow sorting so that all mail flagged for
follow-up will appear grouped together and use the follow-up view to
sort messages by priority, by due date or by date.

8.71
Should allow copying the body of a received message into a new to-
do item or calendar entry with a single click.

8.72
Should specify a preference to view only unread mail in their
inboxesallowing them to focus on the mail they have yet to act
upon.

8.73
Should allow the user to open any major functional areawelcome,
mail, calendar, to-do list, contact list or notebookin a new window.

8.74
Should allow the user to move to the next or previous message
without having to return to the inbox view.

8.75
Should allow the user to open and act upon invitations directly from
the calendar viewbecause new invitations automatically appear on
the calendar view at the appropriate time. This function offers a
visual snapshot of the new calendar entry in relation

8.76 User should be given an option to view dual time zones on the


Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
calendar view, allowing users to easily understand calendar
commitments for meetings with colleagues around the world. User
should be able to select a separate time zone for start and end time
8.77
User should be given the option to pencil in a meeting invitation,
appointment, anniversary, event, reminder and to-do items to provide
the appropriate visual reminder.

8.78
Should allow the user to delegate the scheduling and response to
meeting invitations to another user, especially helpful for
administrative assistants and busy executives.

8.79
Should provide the user the ability to copy a person listed in the
Enterprise Directory to his/her personal contact lists from within the
dialog box for addressing new e-mail messages. The browser based
email software should automatically populate a record

8.80
Should allow the user to create to-do items that can be assigned to
another user or group of users.

8.81
Should take advantage of advanced printing functions, like selecting
and printing multiple documents in a view, adding a time stamp to
calendar printouts, printing a selected view and printing contact
records.

8.82
Should provide feature for printing of the message displayed in the
web interface as it appears (printer friendly version).

8.83
Should support basic authentication, session authentication, secure
logoff, Secure Sockets Layer encryption and active content filtering.

8.84
Should be able to send encrypted messages, signed messages and
also capable of verifying the digital signaturesdirectly from the
browser interface.

8.85
Users should be able to access web mail using a common URL
published for the email site.

8.86
Users should be capable of viewing the total size and available
space of their mail boxes.

8.87
Should provide archiving based on enterprise policies and
requirements and thereby make administration more manageable.

8.88
Users should be able to import/export personal address book entries
maintained on the server, through web interface.

9 Mobile Client
9.1
The EMS services should be accessible using GPRS (EDGE),
CDMA, WAP enabled mobile devices for limited set of users.

9.2
Vendor should provide the list of the devices supporting the mobile
client (if any).

9.3
The Mobile Access should have support for accessing mails from
Blackberry, Windows Mobile Enabled Devices.

9.4
Vendor should provide the list of PDAs that can be used with the
proposed messaging solution.

9.5 The solution should provide Push/Pull technology.
9.6
Should support synchronization of calendar items, contact items, and
mail items between pocket pc devices and the messaging server and
client over GPRS network over the Internet

9.7
Should support secured access of Mail, Calendar and Contacts from
a WAP phone

9.8
Should support text based notifications of Mail & Calendar Reminder
onto a Cell Phone directly from the mail server

9.9 The users should be able to synchronize tasks between their mobile


Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
devices and the messaging solution
9.10
The users should have the functionality to search through their entire
mailbox from their mobile devices.

9.11
The user should be able to access internal corporate files through
Mobile devices.

9.12
The user should be able to configure Out of office messages from
their mobile devices.

9.13 Users should be able to reset their passwords from mobile devices.
9.14
The Mobile component of the messaging solution should support the
functionality to remotely wipe all data from devices.

9.15
Details of any other feature that is not mentioned or listed in above
category may please be provided. These will have added weightage.

10 Disaster Recovery
10.1
The proposed replication should be able to replicate data residing on
any storage subsystems in synchronous, asynchronous modes
without any distance limitations.

10.2
The proposed replication should replicate at block level or/and file
level

10.3
The proposed replication should have feature to operate in
synchronous and asynchronous modes and should assure 100%
data consistency. Allow the administrator to schedule the data
replication between the primary and the DR site.

10.4
The proposed replication should have option to integrate with High
Availability clustering software.

10.5
The proposed replication should provide various methods to initialize
the secondary including over the wire and via backup and restore.
Both the options should be able to perform while the application is
completely online.

10.6
The proposed replication should be storage independent which
means that it has capability to replicate between different storage
from same vendor or from different vendors. It should work on
storage like DAS(J BOD) and SAN

10.7
The proposed replication should be able to replicate between any
hosts connected by an IP network without requiring additional
network hardware or dedicated fibre connections.

10.8 The proposed replication should support Zero RPO.
11 Reporting
11.1
Mail delivery reports generated automatically and archived for pre-
defined (configurable) number of days and available to the
Messaging Administrator and to the End user. Samples (not limited
to only these).

General statistics about the mail delivery (total messages, rejections,
bytes transferred, etc.).

List of domains with which mail was transacted.
User wise successful message sends and receipts.
Rejection details due to RBL, ill-formed mails etc.
Rejection due to viruses (quarantined messages).
Rejection due to mail policy controls.
Data transferred by each user via POP.
Messages fetched by each user from configured POP accounts.


Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
Count of mail marked as spam
11.2
Controls for number of days to retain the report archives, whether to
show the reports to the end user, etc.

11.3
Health Monitor to generate periodic reports about the health of the
system, security status, services, etc.

11.4
Set up report jobs for custom MIS reports (What to report on, where
to send it, when to send it)

11.5
The items that must be logged such as identifying information about
each email message that passes through the email service, including

Envelope from,
Envelope recipient,
Time of transaction,
IP address of host sending message
Size of message

Facility of displaying the extracted reports in the form of
charts/graphs/tables.

12
The messaging software should provide feature for compliance
to corporate policy

13 Directory services
13.1 Directory System Specifications

A centralized directory service based on LDAPv3 for user, application
servers and their profiles.

System should provide support for integration / synchronization with
other directory servers based on LDAPv3.

The system should support auto-tuning of data like indexing and
caching.

13.2 Management & Replication Features

The Directory system should provide for replication in master-master,
master-slave modes across the LAN or WAN.

The Directory system should be able to define different attributes,
indexes to optimize the performance of the over all services.

The Directory system should support differential replication.
13.3 Directory Security Features

The Directory system should provide the following authentication
methods Encrypted passwords, Certificates.

The Directory system should have support for implementing policy
based access control for access of the directory data for every user
and also should replicate the same.

The Directory system should have password policy management like
retry attempts, lockout, min/ max length and password history.

The Directory system should also provide for policies which allow
granular control of the Mail Client on the desktop.

Changes to an object made during business hours must be
replicated to all other directory servers within defined SLA.

13.4 Directory Administration

The Directory system should support online administrative operation
on the directory data such as backups, schema updates, and
configuration.

Ability to support and delegate the administrative rights at different
levels depending upon the server, users and task level.


Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement

The Directory system should have a GUI console and Web Based
console for performing the administrative tasks.

The Directory system should allow for registration of users using the
Web Based console.

The Directory system should have support for defining dynamically
extensible schema and custom attributes.

The Directory system should permit monitoring of directory server in
real time using the Simple Network Management Protocol (SNMP).

The Directory system should provide support for different log levels,
log rotation policies and log analysis tools.

The Directory system should be capable for on line import, export,
backup and restore of data.

13.5 LDAP Compliance

A LDAP search facility for filtering users including equality, sub-
string, approximate (sounds like) and the boolean operators and
(&), or (|) and not (!) should be available.

The Directory system should support for making a query on other
directory servers over LDAP v3.

13.6 Personal and Global Address Book

LDAP support to provide access to the Global Address Book and
Personal Address Book from Webmail client and any desktop email
client program like Outlook, Outlook Express, Notes etc.

Search for addresses using fuzzy search logic

Integrated with the Webmail client by allowing address insertions,
and use while sending messages

Sort the addresses on various fields like nickname, name, email
address etc.

The user should have an option of maintaining personal address
book on the server accessible through the web based clients.

There should be an option for Address book Import / Export to a
personal address book on the server.

The global address book should be accessible from webmail &
desktop / thick mail clients for all users.

Support for X.500 naming standards

Support for LDAPv2 and v3 as the directory access protocol for fast
queries and directory updates

PKI based support for logon and authentication

Support for DNS as the locator service (service records & dynamic
updates)

14 Address Book & Search
Support for Multiple Address Books
Search capability to query all directory objects

Search capability to query Resources by attributes (meeting room
seating capacity, meeting room computing resources etc.)

Should provide Offline Address Book Support as follows:

The Directory Services should provide an interface for messaging
clients to download the address book to their local machine and work
offline.

The client should also offer the functionality of partial or full download
of the address book locally.

The synchronization should download only the new information and


Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
not re-download the old information already present on the client
end.

Should support server-side and client-side contact management
including integration of contacts with word processing applications.

Should support personal directory apart from the offline address book
and should support the following object types: Users, Distribution
Lists.

Also, these object types should be supported in a thick messaging
client as well as a browser client.

Should support vCard standard.

Users can add addresses from other organizations or individuals to
their private address book.

Users should be able to import/export Contacts in .csv format (from
Global/ Personal Address Book).

15 Administrative Features for Messaging Solution
15.1
The system administrator should be able to start, stop, and restart
software components without the shutdown of underlying hardware
component.

15.2
The messaging solution should have a detailed reporting and system
usage analyzing tools.

15.3
System administrator should be able to create, delete user accounts
by dedicated administrator.

15.4
System administrator should have the ability to allow/restrict
users/groups to access all the services/part of services provided
through the messaging system at a global level.

15.5
System Administrator should be able to control the following user
related features (essential):

Configuring mail forwarding
Configuring email filtering.
Defining the quota limits.
Resetting User Passwords
Activating / Inactivating
15.6
System administrator should be able to delegate administration on
the basis of users.

15.7
The messaging solution should have support for system alerts for
alarms and usage statistics and administrator should be also able to
set threshold values for the same.

15.8
The system administrator should be able to customize the error
messages displayed or logged by the messaging system.

15.9
The System should be able to send automated message/alert to the
users whose mailbox has reached the quota or to the users who are
receiving/sending mails more than the threshold set or on any other
parameter.

16 Collaboration Services & Features
16.1 Calendaring and Group Meeting

Calendar interface should allow end users to view one or more
person's agenda, choose a meeting time.

Calendar Service must provide ability to set access control list that
restrict calendar sharing.

"Should natively support server-side and client-side calendaring and
scheduling, including:


Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
Checking the online availability of intended attendees for a meeting
Sending of request for meetings
Accept or reject meeting requests
Provide conflict man"

Calendar interface should provide an option to delegate commonly
used tasks like manage schedule, Accept/Reject appointment
calendar on users behalf.

User should be able to View, create, and schedule calendar entries
and meetings.

Calendar should support different views like Daily, Weekly, Monthly,
Calendar List, To do List.

Should support sharing of calendar between users (with access
control features).

Should support booking of meeting rooms and other company
resources using shared calendar.

Should support tracking of responses from the meeting invitees with
information on the number of accepted and rejected responses.

Should support marking appointments as private, so it will not appear
when others view ones calendar.

Should support access to multiple calendars side by side to make
scheduling meetings fast and more convenient.

Should support accessing a group calendar to view simultaneously
the free time schedules of 2 or more users or resources

User should be able to view selected days or series of days apart
from default views like Daily, Weekly, Monthly, Calendar List, to do
List.

Users should be able to share their calendar information with others,
enabling users to view multiple calendars simultaneously in a side-
by-side view.

User Should be able to customize a work week by Days and hours.

The users should be able to view the presence information of the
other users

The solution should provide support for group collaboration,
Calendaring, Scheduling

16.2 Collaboration

The Messaging solution should support the ability to create shared
team Calendar and tasks.

The Messaging solution should provide the ability to synchronize
Shared calendar/Documents

The Messaging solution should provide the ability to send automatic
alerts based on pre-defined criteria

The messaging solution should provide information gathering
mechanism such as surveys and feedbacks.

The solution should provide for workflow based approval mechanism
and versioning capabilities.

The solution should support streaming of web based content to be
used for capabilities such as e-learning.

16.3 Instant Messaging / Chatting

The user authentication should be from the same Directory Services
used with the messaging solution.

Instant messaging service should provide an ability to chat with
contacts with a click of a button.


Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement

Instant messaging service must provide one-to-one, one-to-many
and many-to-many chat and chat conference.

Instant messaging service must provide support for archiving chats.
Instant messaging service should publish and notify the user status.

The Instant Messaging Service should provide an ability for Instant
messaging (chat)

Users should be able to change their status (online, away, etc).

Users should be able to chat irrespective of whether they are using
the full client or the web access to mails.

The chat interface should offer the facility of buddy lists on Mail and
Web Mail Client

IM client should have the capability of installing separately on the
client machines, integrated with the Desktop/Thick Mail client and
integrated into the Web Interface

Instant messaging should support rich text, emoticons, in-line spell
checking, and content filtering.


Tabl e-08: Br oad Speci f i cat i ons Ant i vi r us/ Ant i -Spam
Specification for SMTP gateway level antivirus and anti spam
S No. Specification
Offered Yes/
No
Deviation/
Enhancement
1 General Features
1.1
The solution should be a single product integrated solution to
provide SMTP AntiVirus,

1.2 Content Filtering and Heuristics based Anti Spam Solution.
1.3 The product should be software based solution
1.4
The solution should work on Windows, Linux, Solaris and/or any
other Unix OS

2 Anti virus Features
2.1 The solution must support mass mailing virus detection
2.2 The solution must support mail attachment virus detection
2.3 The solution must support Malformed Mail format detection
2.4 The solution must have a built in Safe Stamp feature
2.5
The solution must have its own Updated Recommended Virus
Extensions

2.6 The solution must support Compression algorithms
3 AntiSpam Features
3.1
The solution must support Heuristics-based mail header detection
for Spam

3.2
The solution must support Heuristics-based scanning of the mail
body for Spam

3.3
The solution must support administrator defined Anti-Spam
exception list

3.4
The solution must support administrator-defined non-approved list
of known spammers.

3.5
The solution should be able to detect Spam based on multiple
categories (such as general, commercial email, Get rich quick,
pornography, Racially insensitive content).

3.6
The solution should be able to take action based on the category
in which Spam is detected.

3.7
The solution must be able to take different action based on the
different sensitivity level of Spam detection.

3.8
The solution must provide alerts based on action taken on the
Spam mail

4 Content Filtering Features
4.1 The solution must support Content Filtering
4.2 The solution must support Keyword search in message body
4.3
The solution must support Intelligent Keyword Search (NEAR,
NOT, WILD, OCCUR N times operators)

4.4 The solution must support Attachment scanning for MS Office
4.5
The solution must be able to scan by message subject, header,
body, and attachment objects

4.6 The solution must support Attachment Filtering
4.7
The solution must be able to block attachment by file name and
extension

4.8 The solution must be able to block attachment by real file type (file


S No. Specification
Offered Yes/
No
Deviation/
Enhancement
header based checking)
4.9 The solution must be able to block attachment by number

Specification for centralized AV management console
S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
1
Shall manage the anti-virus programs on the network from a single
web-based console.

2 Shall provide network wide virus statistics and analysis.
3
Shall allow automatic, single point updates of virus pattern files for
all the antivirus products from the same vendor.

4
Must be able to do centralized update to all anti-virus programs on
the network.

5
Shall support Microsoft Internet Explorer browser, using Active X
and J ava.

6
It shall be able to monitor remote locations over WAN links for anti
virus activity.

7
Shall provide Incident monitoring and notification System reporting
shall provide Information collected throughout network for analysis
of activity; graphical report generation (templates provided)

8
Shall eliminate the need for platform-specific computer skills when
administering the variety of anti-virus programs often found on the
network.

9
Shall install on an NT/2000 add/or any Unix server then deploy
Agent that register every anti-virus product detected on the
network.

10
Shall be interactive and event-driven communication minimizes
network traffic.

11
Shall allow administrators to enforce an enterprise-wide virus
protection policy from one GUI monitor.

12
Shall support 3 tier deployment architecture to have better
bandwidth management.

13
Example, Parent Management console ->Child Management
Console ->Managed

14 AntiVirus Products
15
Shall provide proactive attack process management, focused on
getting attack specific information and policy file to IT
administrators before new pattern file available

16
Shall be able to perform all necessary outbreak related tasks from
a single interface

17
Shall Offer a hierarchical structure for job delegation so
administrators can determine access control. The management
system's users shall be classified into Administrator, Power User
or Operator roles.

18
It should support central deployment of Outbreak Prevention
Policies to all the managed anti virus products


19
Shall be able to have Different operator assigned separate access
to individual location for job delegation and separation of task and
responsibility

20
Shall utilize Secure communications between Management Server
and managed product(s)

21 Shall be able to Customize software update deployment plans

Specification for server / desk side antivirus solution
S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
1
Should be able to run a clean-up scan (damage-cleanup) on all
the clients from a single console without user intervention.

2
Should be able to deploy the updates manually to all the clients
with an Update now option.

3
Should provide SORT and search function on the client tree in the
management console to sort the clients in the required order and
search for a specific client.

4
Outbreak Prevention option to block specific shared folders, ports,
and to deny write access to specified files and folders on selected
clients from the central console during a virus outbreak.

5
Control Client access to the antivirus program installed by giving
restricted access to the program folder and registry files thereby
preventing the user from deleting and altering the files necessary
for the client program to run properly.

6
Client installation - Should be able to deploy the Client software
using the following mechanisms:
Support MSI in Client Packager tool
Notify Clients to install via E-Mail
Client Packager tool for client local install
Web Install via Active X control
NT Remote Install
Via Login Script
Through disk imaging
Support MS Systems Management Server (SMS)

7 Update
7.1
The server component should automatically update itself from the
Internet or through a Central management server with an option to
do a manual and a scheduled update.

7.2
The update component should download all components required
including the pattern file, scan engine, program files, damage
cleanup template/engine, spyware pattern and firewall engine
instead of downloading every component separately.

7.3
Clients should automatically get updated from the Antivirus Server
without user intervention.

7.4
Clients should get virus updates and personal firewall updates
from a single server. Antivirus server.

7.5
Should have an option to roll-back the pattern file and scan engine
separately.

8 Manageability.
8.1
Should provide with Web-based centralized management through
which all the clients can be centrally managed/ configured for


S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
antivirus and firewall policies.
8.2 Secure remote access via Web browser (SSL-enabled)
8.3 Should support multiple remote installation
8.4 Notification/Logging
8.5 Customizable client alert message for virus detection
8.6 Customizable client alert message for Personal firewall
8.7
Notification through E-mail, Pager, SNMP trap or through
Windows Event Log.

8.8
Should generate Virus activity log, update log, Personal
firewall/intrusion detection log,

8.9 Client connection status log and Server system event log.
8.10 Notify the administrator in case of License Violation.
8.11 Notification to be sent to the infection source.
9 Platform Support
9.1
Protect the following Operating Systems.
Windows Server 2007
Windows Server 2003
Windows 2000 Server
Windows NT Server
MS Small Business Server 2000/2003
Windows Vista
Windows 2000 Professional
Windows NT Workstation
Windows XP
Windows ME
Windows 98
Windows 95


Tabl e-09: Br oad Speci f i cat i ons EMS/ NMS
S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
1 General Specification
1.1
EMS must provide a centralized point of control of all events
happening across the IT systems, creating a "mission control"
centre for the distributed environment.

1.2
EMS must filter, correlate, process, and respond to the
thousands of events that are created daily from network
devices, systems, databases, and applications.

1.3
The EMS product family must address the challenges related
to providing true application quality of service to the business:

1.4
EMS technology must map the complex dependencies
between managed elements. EMS must be able to
immediately determine the impact of a component failure on
the overall application service, because not every problem in
the infrastructure impacts the business or the end user. This
information must allow IT staff to prioritize problem-solving
efforts.

1.5
EMS must consolidate into one management capabilities, that
allow IT organization to consistently manage the various layers
of an application service infrastructure, including network,
systems, databases, applications.

1.6
EMS Solution must provide secure and reliable communication
mechanisms, advanced local filtering, and corrective action for
truly proactive management. Flexible management must allow
the definition of sophisticated management hierarchies, and a
powerful role-based user concept that permits the
management application to scale any size. EMS must be able
to manage mission-critical environments with tens of
thousands of elements.

1.7
EMS must manage industry-leading applications and
databases. It must also manage every major UNIXoperating
system, plus MicrosoftWindows NTlegacy systems.

1.8
EMS must include very powerful event management and
correlation services technology, providing correlation
capabilities on the intelligent agents in addition to the central
manager preferably in a graphical manner.

1.9
EMS must provide a web based user interface across the
managed components.

1.10
EMS must provide an extensive set of open interfaces
available for instrumentation of application, and for tight
integration into existing management applications.

1.11
The EMS must provide the ability to enable hierarchical
management that provides maximum scalability of the
management system.

1.12
EMS must allow IT management staff to manage business-
critical application services from the end-user perspective, and
to be immediately aware of the business impact of lower level
component failures or performance degradations.

1.13 Complex dependencies between managed elements must be


S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
captured, allowing IT management staff to interpret lower level
data in terms of its importance to the higher-level service.
1.14
Simple point-and-click navigation to faulty components for
further diagnostic or problem resolution must be provided in
order to significantly reduces mean time to recovery (MTTR)
and, therefore, system downtime.

1.15
The EMS must provide a graphical services view of the
elements composing Customers complex end-to-end
application services, including network elements, computer
systems, databases, and the application itself are captured
together with their dependencies in graphical application
service views.

2 Monitoring Critical Servers and Operating Systems
2.1 Monitoring
2.1.1
The Monitoring system should use industry best practices to
provide monitoring for essential system resources, detect
bottlenecks and potential problems, and automatically recover
from critical situations.

2.1.2
The Monitoring tool should be able to help manage large,
heterogeneous implementations by continuously monitoring
essential systems resources, automatically detecting
bottlenecks and potential problems while proactively
responding to events.

2.1.3
It should provide the underlying technology to identify
application problem signatures, which can help prevent failures
before they occur. Problem signatures (Situations) are key
metrics and thresholds that, when combined, trigger an
automated action that prevents system failure. The product
should provide out-of-the-box ready to use monitors
minimizing time-consuming configuration and setup. It should
be possible to easily adjust the settings to reflect their unique
systems.

2.1.4
It should be built on the highly scalable distributed architecture
and provide efficient, centralized management of distributed
and Web-based systems. It should also facilitate to proactively
and automatically detect, correct and alert problems before
they affect

2.1.5
It should offer an easy, consistent way to monitor and manage
key distributed resources through a centralized management
interface. Monitoring parameters should be able set and
updated for an entire group and applied to distributed
resources in a single action. Changes to hundreds of related
remote systems should take place in minuteshelping provide
consistency across targeted systems.

2.1.6
It should provide decision-tree logic to apply several rules to
verify system health and decide whether to trigger an event.
By using built-in intelligence it should relieve the administrator
from having to perform mundane tasks and provide valuable
information for troubleshooting critical situations.

2.1.7
The agents for monitoring should independent of the operating
system they are monitoring.

2.1.8 It should provide an easy to use situation editor to


S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
modify/create custom Situations without any programming
knowledge
2.1.9
It should provide a Wed based health console to view both
near real time and historical data for the systems you are
monitoring. It should enable to check the health rating and
status of your critical resources and resource models deployed
in your environment. It should provide drill down to view
specific problems affecting the system or can view historical
data using Netscape or Internet Explorer Web browsers. It
should also provide selection of key indicators and graphing
them by choosing a large variety of graph types, which allows
the administrator to quickly identify trends and potential trouble
spots.

2.1.10
Drag N Drop Reporting - Should provide an Enterprise
Portal/Dashboard as part of the product, which can be
customized to have views for individual administrators. It
should be possible to create bar charts/tables/Pie
charts/Online Plot charts etc using drag n drop options. Each
administrator should be able to create his own custom portal
view as part of the monitoring environment.

2.1.11
It should be possible to present the Portal information in any of
the following views below:
- Table view
- Chart(Bar, Plot) view
- Needle gauge view
- Thermometer gauge view
- Event console view
- Take action view
- Browser view

2.1.12
The Portal should also provide facility to create custom
resource views, which can be mapped and provided to
Admins. It should be easy to add area specific maps, custom
network diagrams or .jpgs in the portal resource views.

2.1.13
It Should provide an inbuilt Data warehouse for storing historic
data, which can be used for generating capacity planning
reports. The historical data collection function should permit to
specify the attribute group or groups for which data is to be
collected, the interval at which data is to be collected or the
interval at which data is to be warehoused and the location at
which the collected data is to be stored

2.1.14
It should support all standard platforms for server monitoring
including Windows, Unix (HP-UX, Solaris, AIX), Linux, AS/400
and Database like DB2, Oracle, MS-SQL, and Sybase.

2.1.15
Situation based events should be generated and same should
be forwarded to the event management tool.

2.1.16
Monitoring solution should provide Workflow automation
capability which allows administrators to automate detailed
system process using which they can design policies to
perform actions, schedule work to be done by users or
automate manual task.

2.2 Windows Monitoring
2.2.1 The tool should provide detailed information about many


S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
critical Windows areas, including:
- Enhanced event log monitoring
- Virtual and physical memory statistics
- Disk space and I/O statistics
- Paging information and swap statistics
- Network information
- Multiple nodes and platforms from a single view
- Historical data for trend analysis and capacity planning
2.2.2
It should be possible to use this data for alerts derived from
situation analysis of Windows NT performance and availability
metrics.

2.2.3
It should be possible to view/start/stop the Services running on
all windows servers centrally.

2.2.4
It should provide performance statistics for various Windows
parameters such as memory, logical disk, Physical Disk,
Process, services, paging file, TCP statistics, UDP statistics,
HTTP statistics, Active server pages, Network interface etc.

2.2.5
Apart from this it should also have an option to integrate the
Windows NT Event log and Microsoft Active Directory
Monitoring.

2.3 UNIX Monitoring
2.3.1
It should provide the following key performance statistics for
Unix environment monitoring:

2.3.2
System identification and activity Configuration of systems
and checks their current activity levels. Attributes include
system name, type and version.

2.3.3
CPU Percentages of processor activity taking place on each
monitored UNIX system; use this report to check for problems
such as imbalances between user and system CPU, and long
CPU waits caused by I/O bottlenecks. Attributes include
system name, user and system CPU, idle CPU and wait I/O

2.3.4
System virtual memory Includes swapping and paging
activity to help determine if system performance problems are
caused by memory shortages; attributes include total virtual
memory, processes in run queue, processes waiting, page
faults and page reclaims, and pages in and pages out

2.3.4
Load average Overall picture of system activity; attributes
include system name, up-time and load average

2.3.5
Disk use Includes file system location and disk space usage
to identify system performance problems caused by disk space
shortages and poor distribution of space usage

2.3.6 Disk inodes Monitors inode usage on each file system
2.3.7
Networks Helps identify network interfaces, determine
whether they are operational and see the amount of data traffic
for each

2.3.8
Processes Detailed data on each currently expanding
process, including identification, priority, command and size
data

2.3.9 File File attributes, paths and time information
2.3.10
UNIX disk performance Helps clearly see I/O efficiency,
identify disk performance problems, get information about file


S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
system location, distribution and disk space storage, and
monitor inode usage on file systems; attributes include
transfer rate, busy percent and transferred bytes
2.3.11
It should also provide Unix System Log integration for alerting
critical events centrally.

2.4 Database Monitoring
2.4.1
Administrators can quickly view the performance of each
database through a navigational tree.

2.4.2 Automate routine administrative tasks.
2.4.3
Efficiently survey the health of databases from any browser on
the network

2.4.4
The Monitoring tool should support monitoring of standard
RDBMs like Oracle, MS-SQL, Sybase and DB2

2.4.5
The Database monitoring should seamlessly integrate with the
same Dashboard/Portal as that of Server Monitoring and
provide integration with the central event console.

2.4.6
The tool should provide you the ability to easily collect and
analyze specific information, including information on:
a) Buffer pools
b) Databases
c) Locks and other details about lock resources
d) Server key events
e) Tablespaces
f) Database Usage
g) Database State
h) Errors.

3 Configuration Management

The Vendor should provide tools to perform Desktop
Management functions that include software Delivery, Asset
Management, Compliance, OS Management, Patch
Management. This may also include Remote Desktop Capture
for remote problem solving. The tool should have out of box
support for Discovery based on range of IP addresses or IP
subnets and Remote deployment of agents from GUI console

3.1 software Distribution
3.1.1
The software distribution function should provide flexible and
scalable delivery, installation, and configuration of software
both shrink-wrapped and in-house across heterogeneous
environments. Pre-and post-installation steps should also be
specifiable to tailor the process to the specific needs of the
organization

3.1.2
The software distribution should support customisable
distribution schedules and alternate fan-out methods.

3.1.3
It should support diverse operating systems such as Windows
XP, 2000/2003, Unix (Linux, SUN, AIX, HP) out of box, without
using any third party products

3.1.4
Support of fan-out and local servers should enable to deliver
software to hundreds of systems, in a controlled and secured
manner.

3.1.5
It should be independent of the Windows Domain Environment
and not have multiple implementations for every Windows
Domain.


S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
3.1.6
The software distribution function should leverage the
information stored in asset database for intelligent software
distribution (Should seamlessly integrate with the Inventory
Module). For example, it should identify which systems satisfy
certain hardware and software prerequisites, ensuring delivery
of the right version of software to the right system. Also the
software distribution module should automatically update the
inventory database.

3.1.7
The system should support uninstall of the software installed
in the system with the help of software distribution.

3.1.8
It should provide Bandwidth management, Checkpoint and
restart capabilities, Control of the server resources and Wake-
On-LAN feature which simplifies software installation

3.1.9
The software distribution module should provide a monitoring
interface (GUI) with complete status of the softwares
distributed e.g. successful, failed, pending etc.

3.1.10
It should provide retry or resubmit options for failed
distributions

3.1.11
It should support dependency checking and package version
control while distributing a new version of the software
package.

3.1.12
Should have interoperability in Firewall scenarios. It should be
able to support distribution of softwares across Firewalls with
minimum port configuration

3.1.13
Should support software packaging options like MSI, PDF
Importer, and Install Shield

3.1.14 Should support complete Automated Patch management
3.2 Inventory & Asset management
3.2.1
The Asset Management module is necessary to maintain and
keep track of the IT-Resources in the organization. There is a
need for tight integration of inventory information with the
software Distribution function so that conditional delivery can
be performed. It should have the following features:

3.2.2
Identify software and hardware configurations from a central
location. Provide complete hardware and software information
from all the desktops and servers.

3.2.3
It should provide full integration with the software Distribution
module to perform policy based software distribution.

3.2.4
It should provide reports on total install count of software
products in the enterprise, in addition to the software and
hardware inventory on individual systems.

3.2.5 Provide History capability for trouble shooting purposes
3.2.6
Provide ability to integrate third-party query and reporting tools
through ODBC interfaces.

3.2.7
Should support standard RDBMSs like Oracle, SQL, Informix,
and DB2 for inventory repository.

3.2.8
Should provide Scheduler to determine when the inventory
scans are executed

3.2.9 Ability to return only the differences during the scan
3.2.10
Should provide out-of-the-box signatures for thousands of
softwares. Should provide a graphical user interface for adding
additional custom signature.


S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
3.3 Server, Desktop Compliance management:
3.3.1
The software should have Compliance management Solution
to check servers and desktop for software installed as per
companys policies

3.3.2
The software shall have feature to check compliance of Screen
Saver, Password, Network, organization policies for Server
and Desktop etc.

3.3.3
The software should be able to send email to administrator
/managers on finding non-compliance.

3.3.4
It Shall provide reports and should store the compliance data
in a RDBMS database to query on the compliance as and
when required besides this the software should be able to give
out of the box reports and shall be customizable with reporting
tools like crystal reports.

3.3.5
The software beside having out of the box policies and
collectors for checking compliance of default policies should be
customizable to create new collectors for checking compliance
of Servers, desktops, Network and Applications.

3.3.6
The software should be able to check for compliance of
version levels of Patch of applications, antivirus, hot-fixes ,
password policies etc and have provisions to remediate
desktops and servers automatically with required
patch/software levels to comply to company policies.

3.4 OS Management
3.4.1 Ability to capture, install and restore disk images
3.4.2
Should provide Operating system imaging and bare metal
provisioning

3.5 Automated Patch Management
3.5.1 Provide Multiplatform Patch Management
3.5.2
Provide tools and predefined automation for patch
management with Microsoft software Update Services,
Microsoft Windows Server Update Services, Red Hat Network,
SUMA, and Sun Update Connection Proxy as well as support
for customized automation using other software update
sources.

3.5.3 Provide integrated compliance & remediation functions
3.5.4
Accurate patch recommendations for each system based on
vendor scan technology

3.6 Remote Control
3.6.1
This module is expected to take complete control of Remote
Windows 2000, Windows 2003, Windows XP and Linux based
desktops from a central location.

3.6.2
Roles should be used to restrict the level of operations an
administrator can perform.

3.6.3
The enterprise-scale remote control solution must enable rapid
connection to the right target with the help of an automatically
updated searchable list of target system names, enabling the
administrator to establish a remote control session by simply
clicking the target.

3.6.4
Web Browser Interface - The Remote control module should
provide authorization based Web Interface for Administrators


S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
to facilitate Remote control using a Internet Explorer or
Netscape Browser. It should support all the functions i.e.
Remote Control, Chat, Files Transfer etc through the Web
Browser Interface.
3.6.5
It should provide automatic session logoffs due to
administrative inactivity.

3.6.6
It should provide facilitates collaboration and escalation
process for improved problem resolution.

3.6.7
Help desk agents/person taking the remote control should be
able to give control of a problem to another agent, or revoke
control as necessary. This hand-over should be done without
re-opening the session, expediting problem resolution.

3.6.8
It should allow multiple help desk agents to use built-in
collaboration capabilities to resolve complex problems that
require input from multiple sources, providing the user with a
seamless problem resolution experience.

3.6.9
It is important that sensitive data has not been compromised
that unauthorized help desk personnel or the person taking the
remote control have not had access to restricted data during a
support session where the remote control feature was used to
access a users computer. Remote Control software should
support compliance efforts and helps keep access to sensitive
data secure.

4 Alert/Event Management with Event Correlation
4.1
The solution should include a powerful event management and
automation application. The event console should be able to
process and correlate common management events from
many different system and network components and
automatically initiate corrective actions. Grouping and filtering
capabilities should be available to reduce the number of
events displayed to operations staff, enabling them to manage
even the largest, most complex environments. The Event
Console should be cable of: event integration, event
processing, event response and notification, and automation
capabilities.
Key functions of the Event Console should include:

4.2
Comprehensive Event Integration provides a complete
mission-control view of the health of the entire distributed
environment from a single administrator desktop. It should also
provide specialized views of events to different administrators
displaying only those events important to their jobs, thereby
optimizing the staff resources.

4.3
Cross-domain Event Correlation Should have sophisticated
rules-based engine correlates event information across any
resource in any management domain to determine the true
cause of the problem. This ability is critical when problems
within one management domain, such as the network, have
ramifications across other domains, such as systems,
databases, and applications.

4.4
Automated Event Notification and Response The Event
Console should act on events using either automatic or
operator-initiated responses.


S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
4.5
It should offer a unique solution to the problem of managing
exception events. It should correlate and filter events from all
different types of IT resources, and pinpoint the root cause of a
problem. In addition, it should be possible to define rules and
task in a centralized database which would be activated on
reporting of the exception by the intelligent agents.

4.6
Event management in the EMS should also closely integrate
with the service desk function. It should automatically
forwards exceptions that require human intervention to the
help desk function, open a problem ticket and assigns it to the
right support personnel.

4.7
This event manager should also permit integrating in-house
applications with the EMS. It should be used to integrate not
only management applications, but also general business
applications to make them easier to manage.

4.8
With event filtering and correlation, multi-level managers and
agents, automatic corrective measures, and integration with
the service desk, the EMS should provide comprehensive
event management capabilities. It should eliminate the clutter
of spurious alarms and simplify the management of complex IT
infrastructures.

4.9
It should help to notify through GSM Mobile Phone, e-mail, etc
of various/selective events occurring in the enterprise.

4.10
The event management shall provide a sophisticated rules
engine that can:

Correlate events
Discard the event
Prevent duplicate events from being displayed
Execute an application or a script
Generate a new event
Modify the event's attributes
Modify the attributes of other events
Forward an event to another event server
Provide event filtering and buffering at the source

Facility for developing custom events and custom event
engines

Support for heterogeneous platforms and protocols

Should support standard RDBMSs like Oracle, SQL, DB2 for
event repository.

5 Service Desk
5.1 The Service Desk should be based on ITIL.
5.2
The Service Desk software should provide pre-defined
templates based on industry best practices for easy and quick
deployment of the service desk.

5.3
It should be possible to make on-line changes to the defined
processes / business rules without having to bring down or
restart the service desk application.

5.5 Shall support tight integration with NMS incidents.
5.6
Shall support monitoring of the operating status of current
asset inventory so that future asset needs can be effectively


S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
planned and budgeted for.
5.7
The helpdesk shall provide a graphical wizard or rule manager
to create escalation, assignment, and database field update
rules, without any need for programming.

5.8
Should be able to generate various customized Service Level
Reports e.g. Open Call Reports, Closed Call Reports, Problem
Area specific Reports.

5.9 Escalations will happen with help of E-mail Notification.
5.10
A process for creating the Knowledge Base should be
provided. This knowledge base shall be having search
capability.

5.11
The Service Desk should include Change Management
module which should link the processes of initiating,
scheduling, assessing, implementing and evaluating changes
to the IT infrastructure. The Change Management module
should provide complete work order management and tracking
to ensure work is completed as quickly and smoothly as
possible.

5.14
Release Management - The object of Release Management is
to take a holistic view of a Change to an IT service and ensure
that all aspects of a Release, both technical and non-technical,
are considered together.

5.15
Problem Management - The object of Problem Management is
to minimize the adverse effect on the business of Incidents
and Problems caused by errors in the infrastructure, and to
proactively prevent the occurrence of Incidents, Problems and
errors.

5.16
The Service Desk should include an integrated Service Level
Management.

5.17
The Service Desk should include Configuration Management
Database.

5.18 Provide Self-Service Requests module to allow users to submit
and view service requests. Service requests could be created
automatically from sources such as email, system monitoring
tools.

5.19 Ability to assign ownership via workflow or an escalation
process.

5.20 Ability to automatically assign one or more SLAs via Workflow
or Escalation process based on SLAs criteria

5.21 Incident could be created automatically from sources such as
email, system monitoring tools.

5.22 Ability to identify a global incident which is the root cause of
many other issues or that is something affecting many users.

5.23 Ability to relate a Problem to a Global record. A global record
captures information about an issue affecting many people.
The record might be a created for a shared asset i.e. the root
cause of many other issues, such as a failed network server.
Ability to relate existing service requests, incidents and
problems to a global record and manage them via the global
record.

5.24 Ability to apply a template to a Problem. The template contains
common data such Priority, Owner or Owner Group, Service


S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
Group or Service, Classification, Vendor, and Organization.
The Problem template also can contain Problem activity
common data such as, Sequence number, J ob Plan, Site,
Organization, Description, Owner or Owner Group, Priority,
Vendor, and Classification.
5.25
Ability to create follow-up work orders. It will copy the asset,
location, and GL account from the originating work order to the
follow-up work order. A follow-up work order is for when you
complete a job but notice that additional work is needed on the
same asset or location.

5.26
It should have a Service Catalog component that allows users
to select services directly from a catalog, helping to lower the
cost of providing services.

5.27
Ability to define the SLAs such as Customer (SLA), Internal
(OLA) and Vendor (Underpinning contract) and define SLAs at
the System, Organization, or Site level. Ability to relate an SLA
to another SLAs, for example if an SLA has supporting SLAs.
Ability to associate specific assets, asset types, and locations
to a service level agreement (SLA). Once an SLA and its
associated escalation are activated, it shall apply the SLA to
any listed assets, asset types, and locations.

5.28
It should provide out of the box real-time dashboards that
provides insight into multiple levels of service desk operations
so that support staff, managers and executives can monitor
role-based key performance indicators using an intuitive,
graphical display from any Web-based client.

5.29
It should have built-in remote diagnostics capabilities enabling
service desk personnel to remotely take over control of the end
users machine for troubleshooting, updating a file, changing a
users configuration, and looking at settings. It should provide
the facility to record these sessions for auditing and recordings
should be available for review at a later date.

5.30
It should provide instant messenger support that provides an
alternative multi-threaded mode of communication with end
users.

5.31
It should have built-in survey management capabilities that
allows service desk personnel to author and distribute
customer surveys related to Service Desk and Service
Catalog. It should enable automatic distribution of a survey via
e-mail to a specific user or to all users in the system over a
cyclical time period.

6 Network Management System
6.1
Network management software shall be scalable for a
comprehensive, distributed networking solution and have
flexibility to manage mission-critical systems and provide rapid
problem solution.

6.2
It shall discover TCP/IP networks, display and build network
topologies maps as soon as it is installed. Correlate and
manage events and SNMP traps, monitor network health and
gather performance data.

6.3
It shall be able to support all standard SNMP.v1 and
SNMP.v2.And Support SNMP.v3 once it become available.


S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
6.4
It shall have Web console facility to provide network
management for a broader range of people in varied location.

6.5
The Web interface/Console for the network management shall
authorization based on Web Console User, Role, and Scope.
Security shall be used to validate access to the critical action
like Sub-Map exploration, Object properties, Diagnostics,
Event Browser and the MIB Browser. Action and areas of
visibility shall be regulated for Web viewing by Roles and
Scoping, which is assigned to a User. Using combination of
roles and scoping, action a viewer can perform and limit the
view that the user has of the network shall be fine-tuned.

6.6
It shall have support for the following Switch Management
Capabilities:
Switch Management: for Port View, Switch Status and MAC
View.
Inactive Ports: for Port Number, IP Status, and Spanning Tree
Status.

6.7
The Network Monitoring tool should extend the following Web-
based GUIs:
Network Topology Visualization: GUI for visualizing the
network topology
Device Structure Browser: Drill down to see a particular
device's configuration
MIB Browser: GUI for viewing SNMP MIB variable values
associated with devices in the topology
Network Discovery GUI: For configuring and tracking the
status of discoveries
Monitor Configuration GUI: For configuring the active
monitoring and SNMP polling functionality.

6.8 The Network monitoring tool should be designed to provide
real-time network discovery, topology visualization, and root
cause analysis for layer 2 and 3 networks, including IP,
Ethernet, and multi protocol label switching (MPLS).

6.9 The Network monitoring tool should provide event
management and monitoring for the discovered network.

6.10 The Network monitoring tool should have been designed to
provide the user with the capability to automatically discover
network devices and their connectivity.

6.11 It should extend its discovery engine can be configured
through a Web-based graphical wizard, providing the network
operator with full control of the discovery process and how the
discovered data should be presented to the user.

6.12 It should support the following network technologies: IP,
Ethernet, Cisco Discovery Protocol (CDP),Hot Standby Router
Protocol (HSRP), Virtual Local Area Network (VLAN), and
static Network Address Translation (NAT).

6.13 The network monitoring tool should support actively polling
network devices to help proactively identify problems in the
network.

6.14 The network visualization GUI should use the network
topology and event information from the tool (and, if
applicable, your event management tool) to generate graphical


S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
maps of the network topology around particular devices and
send these maps to Web clients on demand.
6.15 Network operators should be able to drill down on specific
problems in the event list to locate the alarmed device in the
network topology view, or show a list of all outstanding alarms
on a selected device in the network topology view.

6.16 It shall develop report on network trends and analysis.
6.17 It shall maintain object inventory in internal database as well
as external database.

6.18 It shall quickly identify and focus on the root cause of the
network error.

6.19 It shall allow users to view network information from any
supported Web browser.

6.20 It shall also dynamically group resources by type, location,
vendor, service offering, or other common characteristics.

6.21 It shall correct problem at the source before users are affected,
enhanced facility of automated problem detection and
response at local level.

6.22 It shall be capable of using rules and manage events locally,
centrally or by propagating events to the enterprise event
management and correlation application and diagnose root
cause problems without reporting all symptomatic events.

6.23
It shall handle variety of actions when reporting events and
exceeded thresholds, including GSM Mobile phone, e-mail,
and problem responses to specific failure.

6.24 It shall in the event of a network problem or router failure mark
affected network regions as unreachable. And in response to
this the network management software shall reduce polling of
the affected networks thereby reducing overall event traffic.

6.25 It shall have the facility to perform Hot Backup of network
management database without stopping or restarting the
production network management server or the user interface.

6.26 It shall be capable of providing with insight of network, as well
as ability to perform thoughtful data analysis.

6.27 It shall be capable to proactively manage network by providing
trend data and quick answering question.

6.28 The information shall be present in the multi dimensional
graphical format and can be viewed interactively or posted as
a snapshot through URL.

6.29 It shall provide a detailed view of overall health and behaviour
of networks individual elements, such as routers, servers, end
system, SNMP data, MIB expressions collected from MIB II
agents.

6.30 It shall provide an overall view of network, event flow and
event traffic. It shall analyze events over time, distinguishing
device class and event severity.

6.31 It shall provide a view of network segment behaviour primarily
determined by using RMON characteristic on network. This
network analysis shall be focused on the health of the specific
sections of the network rather than individual network
elements.

6.32 It shall be able to monitor any MIB parameter dynamically and


S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
plot an online graph of the same using built-in utilities for any
device in the network.
6.33
It shall have capability to store the network event data in the
standard RDBMS for performance and historical analysis.

6.34 The Network Management function must monitor performance
across heterogeneous networks from one end of the enterprise
to the other

6.35 It must proactively analyze problems to improve network
performance.

6.36 Identify, isolate, and helps to resolve response time problems
on LANs, remote links, and servers.

6.37 The Network Management function must collect usage data.
Once collected, it should automatically store data gathered by
the NMS System in a database. This enterprise-wide data
should be easily accessed from a central location and used to
help with capacity planning, reporting, and analysis.

6.38 The Network Management function must also provide
information on performance of Ethernet segments, including
capacity utilization and error statistics for the segment and the
top-contributing nodes, WAN links and routers.

6.39 Alerts should be shown on the Event Management map when
thresholds are exceeded and should subsequently be able to
inform help desk and notify concerned authority using different
methods such as GSM Mobile Phone, E-mails etc..

6.40 LCD monitors 42 on the IT floor for monitoring the WAN &
LAN network status.

6.41
The fault management module of NMS shall provide various
functionalities such as device fault management, link fault
management, network service fault management, systems and
application fault management.

6.42
The Fault Management module shall raise alarms, co-relate
alarms, analyze alarm and shall help in taking corrective
action.

6.43 The Faults displayed shall have a mechanism whereby a link
down or an interface down alarm contains information about all
the affected links and associated customers/sites.

6.44 The NMS shall support SNMP Traps which trigger alarms,
alarm suppression, alarm threshold setting, escalation, alarm
logging, alarm email notification, alarm correlation of element
level alarms to network-level alarms, correlation of network-
level alarms to service-level alarms.

6.45 The Fault Management module of NMS shall support event co-
relation where the correlation logic can be configured by
operator.

6.46 False / transient alarms should be able to be suppressed and
threshold alarm correlation needs to be supported by the NMS.

6.47 The NMS shall keep a list of all active faults of the managed
Network Elements and based upon certain filter conditions,
appropriate messages/command can be sent to alarm notifier,
which in turn could send notification to appropriate destination
defined in the escalation policy.

6.48 The operator should be able to define filtered views of alarms.


S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
6.49 The NMS shall support acknowledgement of faults and clear
the alarms in active alarm list automatically and manually and
same should be notified by alarm notification module.

6.50 The Fault Manager shall provide statistics on number of
alarms generated per element, number of alarms attended by
operator, number of alarms cleared, number of critical alarms
generated and escalated as a minimum requirement.

NMS reporting Specifications
6.51 Provides Web-based secure reporting tool anytime anywhere
access.

6.51 Provides reports for network administrators and business
managers from engineering and management perspective
respectively.

6.52 Provides Near time and historical reports on the availability of
devices and links.

6.53 Daily, weekly, monthly and custom period reporting for both
regular and business hours.

6.54 Near time and historical reports on the performance
parameters of devices and links such as reliability, utilization,
input, output traffic, and CRC errors etc.

6.55 Option to receive configured reports through e-mail on daily,
weekly, and monthly basis.

6.56 Auto-emailing of reports at defined intervals.
6.57 Consolidation of daily performance data into weekly and
monthly performances, to facilitate performance analysis over
a longer time frame.

6.58 The following device availability reports should be provided as
part of the best practice / standards:
Summary reports on discovered assets.
Bandwidth utilization, Real time MIB graphing, Top N
reports.
Availability reports showing current status of devices and
their ports and interfaces.
Availability reports showing devices with root cause
problems sorted by age.

7 Application Transaction Monitoring & Management
7.1
Support simulation of the different types of transactions that
are currently being deployed.

7.2
Provide page and component breakdowns of user transaction
monitored.

7.3
It should track transactions from end to end across multiple
systems to quickly isolate and resolve the cause of bottlenecks
or other issues.

7.4
It should provide response time tracking for Web and Microsoft
Windows environments using real-time techniques.

7.5
It should track Web services transactions to help isolate
problems in service oriented architecture (SOA) applications.

7.6
It should help save administrator time with an easy-to-use
portal that unites key performance and availability metrics and
presents contextual, resource-based views and diagnostic
tools.

7.7 It should allow drilling down each step that the transaction


S No. Specification
Offered
Yes/ No
Deviation/
Enhancement
takes as it travels across multiple enterprise systems and
should allows to measure how each component of a
transaction contributes to the overall response time regardless
of geographic locations and without requiring customers to
install software on their workstations or modify application
code.
7.8
It should perform the discovery process dynamically rather
than relying on static definitions. The starting point can be a
particular URL, a J 2EE component, a synthetic transaction or
a Web services request. It should automatically set baselines
for transaction response times as the system learns
transaction flows and analyzes the response time characteris-
tics of unique environment.

7.9
It should provide or integrate with a portal-based interface to
observe multiple response time metrics and resource-based
views to speed analysis of performance issues.

7.10
It should provide a graphical user interface (GUI) transaction
simulation capability to reproduce end-user behavior and
monitor a transactions health.

7.11 It should provide response times of real end users at the client
to help isolate the root cause of a problem, breaking down
information into overall response time, server time and network
time.

7.11 Provide reports for location analysis & transaction analysis.
7.12 Provide reports to view raw data collected for deeper analysis
of individual transactions.

7.13 Provide triage diagnostics starting from end user process,
breaking down time spent between backend components,
application components and methods to pin-point the areas at
fault.

7.14 Provide capability to identify the top performance hotspots in
the applications.

7.15 Provide capability to perform server request breakdown to
identify where time and CPU is spent in an application.

7.16 Provide capability to identify the slowest server request or
application entry points for non-Web-fronted applications.

7.17 Provide capability to view individual requests and selective
arguments to help diagnose intermittent problems.

7.18 Provide capability to perform SQL diagnostics to identify
slowest SQL query and report query information.

7.19 Provide capability to pinpoint latency for consumer and
providers of web services.

7.20 Offers application programming interfaces (APIs) to export
data.

7.21 Provides an easy way to generate HTML reports for cross-
teams.

Suitable solution should be proposed by the Vendor to support the following in addition to the EMS/NMS.

8 Compliance
8.1
Should determine if the installed software and security settings
match desired policies.


8.2 Compliance reporting and remediation
8.3
Generate reports of the noncompliant issues and recommend
corrective actions. Should provide the following compliance
reports:

8.4 Security Compliance Check
Antivirus
Endpoint Agent
Hard Disk Password
Linux System Logging
Operating System Patches and Updates
Power-On Password
Remote Root Login
Restrict Other software
Screen Saver
UNIX File Permissions
UNIX Services
Unauthorized Guest Access
User Defined Check
User Password
Windows Event Logging
Windows File Permissions
Windows Firewall
Windows Services
Windows System Audit
8.5 Software Compliance Checks
Check individual software products
Required installation
Prohibited installation
Optional installation
Check software groups
Minimum of one member of the group is required
All other members are considered optional


Tabl e-10: Br oad Speci f i cat i ons of Bui l di ng Management Syst em

Building Management System (BMS) shall be a Data Center automation system for monitoring, total integration
and managing devices and systems, including Precision AC, UPS, Diesel Generator, Fire Detection &
suppression, Access Control Systems, Water Leak Detection System etc.

A Sample schematic of the BMS is shown below

General Requirements
Sr.
No.
Specification
Offered
Yes/ No
Deviation/
Enhancement
1 General Specification
1.1
The Supervisory/Direct Digital Controllers in BMS shall be with
minimum 32 bit microprocessor & real time clock.

1.2
Integration with a diverse range of devices, enterprise systems,
Internet and intranet sources allowing intelligent management of
key facility information

1.3
Shall be available on industry-standard hardware and Windows
XP, 2000 and 2003 operating systems

1.4
Shall support the leading open standards: BACnet, LonMark,
Modbus , ODBC, OPC, etc


1.5
UL Listed to Standards UL864 (Fire), UL2017 (Signaling
Systems), UL916 (Energy Management Systems), UL1017,
UL1076 (Security), UL1610 (Central Station) and UL294 (Access
Control)

1.6
Shall provide Easy-to-use Web-based user interface with unified
system with centralized database storage, data logging &
archiving, and alarm reporting.

1.7
The BMS System shall meet Precision AC control needs by
providing interfaces to Precision AC devices. The PAC units shall
be integrated with BMS unit for time sequential operations and
also auto start the redundant unit in case there is failure of any
running PAC. The standby unit shall continue to work till the
failed unit is serviced & repaired.

1.8
The BMS System shall collect information from security, access
control and surveillance devices, ensuring protection of people
and assets.

1.9
The BMS System shall perform monitoring and control of fire
alarm systems for fire protection and smoke control. Fire
Suppression by FM-200 automatic gas suppression

1.10
The BMS System shall facilitate surveillance of facility using
cameras for enabling flexible event based recording and viewing.

1.11
The BMS System shall perform monitoring of the UPS and DG
set.

1.12
BMS shall have facility to enable remote support over dial-up
links.

2 System Architecture
2.1
The BMS System shall support client/server and distributed
system architecture.
The BMS System shall support open system architecture which
combines a variety of controllers, standard hardware devices,
and communications interfaces. The BMS System shall integrate
with the following subsystems:

- Access controllers
- Precision AC monitoring and control
- Water Leak Detection System
- UPS Monitoring & Control
- Interfacing with the Building DG Set
- Life safety monitoring and control
- Digital CCTV systems
- Digital Video Manager
- Mobile Phone and SNMP notification systems
3 Open Systems Support
3.1 The BMS shall support open systems Standards such as

MODBUS: Support general-purpose interface and de facto
standard communications protocol that can be used to integrate
different controllers.

LonWorks: LonWorks Interface is based on Echelons LNS
Database to provide compatibility with third-party LON tools and
shall support the latest version of LNS (3.2) available from
Echelon.

BACnet: Supports ASHRAE Standard for the BACnet Protocol,
implementing both BACnet Operator Workstation and BACnet


Gateway functionality. It supports BACnet over Ethernet and IP
communications. A BACnet PICS document is available on
request which details It support for BACnet Standard Objects and
Application Services.

OPC: Supports OLE for Process Control (OPC) 2.0 Data Access.
This interface allows reading and writing to an OPC Data Server
as an OPC client. This capability provides access to a wide
range of third-party OPC Data Servers.

ODBC: Support read-only ODBC access to its real-time
database , card holder database etc

4 Supervisor/ Operator Interface
4.1
The operator/supervisor interface shall enable two concurrent
administrators to perform the following tasks:

- Display and control field equipment
- Acknowledge alarms on a priority basis
- Display point status and history information
- Status / parameter display on Data Center system mimic
- Initiate printing of reports
- View, archive and retrieve event logs
- Monitor data communications channels
- Configure system parameters
- Select and control CCTV cameras
- Create colour graphic displays
- Record and play back digital video
4.2
Operator Security and Levels: Shall offer sophisticated methods
for controlling access to sensitive data. It shall restrict and control
activities to be performed by operators by giving them different
security levels.

5 Video Integration
5.1
Video surveillance is essential for monitoring activity in Data
Center vicinity enabling one operator to view many parts of the
Data Center from a central location. Video may be integrated
from CCTV systems or from Digital Video Manager product.

6 Web Enabled System
6.1
Remote monitoring of equipment, performance analysis,
adjustment of control parameters, response to alarms using PC
based web browser.

7 Alarm Management
7.1
The comprehensive alarm management facilities shall ensure
that operators are immediately notified of any attempted security
violations. This action will automatically be recorded in the
system event file.

7.2 It shall offer alarms as follows:
- Audible Tone. The audible tone on each Station.

- Alarm Indicator. An alarm indicator to appear on all displays
and to flash when there are any unacknowledged alarms.

- Alarm Summary Display. An alarm summary display to show all
alarms in the system with colour-codes to indicate priority and
severity.

7.3
Alarms to drive external communicator such as a hooter locally
as well as in Systems Department. Alarms shall be associated
with different point states for digital points or special conditions
such as high or low values or rates of change for analog points.


7.4
An Alarm Broadcaster shall be provided to route alarms to mobile
phones and email.

8 Event Management
8.1
Events include alarms, point changes of state, cardholder
movements, changes in system status and all operator actions.
As system events occur, a journal of the events to be created in
an event file. J ournalized event entries include a description,
condition, message, time of occurrence, and responsible
operator. The system event file shall store event data in an on-
line buffer. It shall be possible to store as many events as
necessarysubject only to disk space on the server. When the
on-line buffer becomes full, the event data shall be transferred to
an archived buffer and notify the operator to save the file to
external media. The on-line buffer shall continue to store events
without interruption. An operator shall retrieve current or archived
system event data for use on-line or in the reports.

9 Historical Data
9.1
Shall provide continuous history about behaviour of points in the
system over time.

9.2 Shall support a range of different history collection rates.
9.3
Ability to collect both snapshots and averages, allowing operator
to view activity data on the system at any instant in time or over a
longer period. This historical data shall be viewed as graphical
trends (such as line or bar charts) and as lists of numeric values.
Historical data can also be used in reports, exported to Microsoft
Excel and archived to offline media for long term storage.

10 Reporting
10.1
Shall provide comprehensive reporting facilities including a range
of standard reports. Standard reports shall be provided, which
shall be operator selectable to appear on the operator station.
Point summary reports shall include the value/status and
condition for any defined period such as

- Point Report
- Alarm Report
- Analog Limits Report
- Hardware fault Report
- Equipment failure report
- Analogue trend report
- Historical event report
- System wise scheduling report

10.2 Some examples of reporting are as follows:
- All points in alarm over a configurable time period
- All activities by a certain operator
- All activities for a certain group of points
- All movements of cardholders through certain doors
- All movements through any doors by a specified cardholder
- All information pertaining to access configuration information
- Temperature and Humidity figures over a period of time.

- Number and duration of mains power failure over a configurable
time period


I/O Summary for Data Center
POINT FUNCTION
SNo Description QTY AI DI AO DO Monitor Control Alarm By BMS Vendor

1 Precision ACs

Temperature x x x
Humidity x x x
On/Off Control x
On/Off Status x x
Alarm Status x
Trip Status x

2
Environment
Monitoring:

Monitoring of
Temp in Data
Center
x x

Monitoring of
Humidity in
Data Center
x x

3 UPS

Incoming
Voltage
x

Outgoing
Voltage
x
Battery on load x
Frequency x
Phase Current x

UPS ON/OFF
Status
x

UPS ON/OFF
Command
x
Power Factor x

4
Multifunction
Meters

LT R, Y, B
phase voltage
Monitoring

Through Modbus
Output of Energy
Meters
x x

LT R, Y, B
phase Current
Monitoring
x x

LT Frequency
Monitoring
x x

LT Kilowatt
Monitoring
x x

LT kWH
Monitoring
x x


POINT FUNCTION
SNo Description QTY AI DI AO DO Monitor Control Alarm By BMS Vendor
5
Diesel
Generator
x x x

6
Fire Alarm
System
x x x

7
Water Leakage
System

Zone wise
alarm Alarm
x x

8
Safety &
Security
Systems

a
Access Control
System -
Opening of all
doors in case
of fire
x x x
b CCTV System x x x


Annexure-2: Deliverables & Performance Parameters

A. Deliverables & Technical Response Parameter for the Project

A1. Deliverables

Vendor shall be required to follow milestone based deliverables for the Project. The methodology, detailed project
activities, deliverables and responsibilities, which are to be followed during implementation should be based on
ASAP Methodology.

The following table lists out the deliverables in pertaining to individual phases of the project

Sr No Acti vity Deli verable Deli verable
Schedule
2.1 Supply of Hardware & Non-SAP software
1. Supply of hardware- Data center equipments
Physical delivery of
equipments and
accessories at Project
Site.
Vendor to suggest
suitable time line
considering the
dependency of
Application
implementations.
2.
Supply of hardware- servers, storage, backup device, racks &
other hardware.
3. Supply of hardware- Networking components
4. Supply of video conferencing equipments
5. Supply of IP telephony equipments
6.
Supply of Non-SAP software Messaging & Collaboration
System.
Physical delivery of
application software,
tools, media and
necessary user
licenses etc. at
Project Site.
7.
Supply of Non-SAP software Anti Virus / Anti Spam /Content
Filtering.
8.
Supply of Non-SAP software EMS/NMS and Service Desk
tools.
9.
Supply of Non-SAP software Building Management
System(BMS)
10. Supply of Non-SAP software Video conferencing system.
11. Supply of Non-SAP software IP Telephony System.
12. Supply of Non-SAP software Other software.
2. 2 Design, installation and commissioning of Infrastructure
1.
The Vendor shall design the data center architecture, civil
construction, date center equipments layout, electrical system
including power supply distribution with earthing system, UPS
system, cable layout, illumination system, air conditioning
system, fire protection system, access control system, building
management system etc . as per the detail scope and techno-
functional requirement specification
.
Design document
including architectural
drawing, electrical
drawing, air
conditioning drawing,
equipment layout
drawing, BMS
drawing etc.
Vendor to suggest
suitable time line
considering the
dependency of
Application
implementations.
2.
Services covering installation & commissioning of Data Center
after validation of design document as above by owner.
Completed Data
center as per the
design. The Vendor
shall submit 6 sets of
hard & soft copy of
complete technical
documents & as
building drawing of all
the systems of data
center.


Schedule
3. Preliminary acceptance test
Preliminary
acceptance test
report

2.2.2 Installation & commissioning of Hardware
1.
The Vendor shall design the solution architecture for the
hardware infrastructure of the Project and perform the Server
Sizing for SAP application & non-SAP applications.
solution architecture
& hardware sizing
document Vendor to suggest
suitable time line
considering the
dependency of
Application
implementations.
2.
Services covering installation & commissioning of various
hardware components after the validation of solution architecture
by the owner and hardware sizing by OEM.
Completed hardware
infrastructure setup
as per the solution
architecture
3. Preliminary acceptance Test.
Preliminary
acceptance test
report
2.2.3 Installation & commissioning of Networking components
1.
The Vendor shall prepare the Network design i.e. identification of
network equipment requirements and other parameter e.g. QoS,
IP addressing etc for different environments
Network architecture
and design
document.
Vendor to suggest
suitable time line
considering the
dependency of
Application
implementations.
2.
Services covering installation and commissioning of local area
network, wide area network, internet connectivity, storage area
network & security after the validation of the network architecture
& design document as above by the Owner.
Completed network
infrastructure
3. Preliminary acceptance Test.
Preliminary
acceptance test
report
2.2.4 Installation & commissioning of video conferencing system
1.
Design, installation & commissioning of video conferencing
system
Completed Video
conferencing
infrastructure
Vendor to suggest
suitable time line
considering the
dependency of
Application
implementations
2. Preliminary acceptance Test
Preliminary
acceptance test
report
2.2.5 Installation & commissioning of IP Telephony system
1. Design, installation & commissioning of IP Telephony system
Completed IP
telephony
infrastructure
Vendor to suggest
suitable time line
considering the
dependency of
Application
implementations
2. Preliminary acceptance Test
Preliminary
acceptance test
report
2.3 Implementation of SAP Applications
2.3.1 Conducting Business Process Study
1.
The Vendor shall conduct As-is business process & information
requirement study
As-is business
process & information
requirement
document

2.
Once the As-is business process information requirement study
is complete, the Vendor will prepare a To-be business process
document. This document will describe how existing processes
will be executed post going live with the SAP Application. The
changes in the To-be processes from the As-is
process will be highlighted.
Where an existing process cannot be mapped directly to any
SAP functionality (i.e. there is a gap), the Vendor must propose
solutions, in terms of process changes, workarounds, custom
To-be process with
gap analysis &
resolution document
Vendor to suggest
suitable time line
based on the Project
Plan and
Methodology.


Schedule
development, interface with legacy systems, etc. This document
must be prepared in a format which allows easy reference to the
As-Is Process Document. The To-Be Processes along with the
Gap Analysis and resolution must be vetted by the Project
Management Team.
3.
Once the To-Be Process and the Gap Analysis & Resolution
Document is finalized and the custom
developments/enhancements identified, the Vendor will prepare
a customization strategy report for approval of project
Management Team
Customization
strategy report
4.
The interfaces to be developed between the SAP System and
the legacy applications or satellite application based on the To-
Be Process document must be documented by the Vendor and
signed off by the project management team.
Interface strategy
document
5.
Based on the revised information requirements in the context of
To-be business processes and standard reports available in the
SAP System, the specific information / reporting requirements
(including the form, parameters, access and content) will be
documented by the Vendor and signed off by the Project
Management Team.
Custom Report
requirements
document
2.3.2 Mapping of business processes as per Business Blueprinting
6.
Development & approval of business blueprint document
mapping all the To-be processes.
The business
blueprint document
Vendor to suggest
suitable time line
based on the SAP
Solution, Project Plan
and Methodology
2.3.3 Conceptualizing, Developing, Configuration and Testing the Solution
7.
Based on the approved business blueprint, the Vendor shall
prepare a prototype of the solution (including all customization,
interfaces etc).
Solution prototype
with necessary
documentation
Vendor to suggest
suitable time line
Plan and
Methodology.
8.
The solution prototype should be made available for validation by
the Owner nominated users and the project management team.
The prototype validation will go through multiple iterations. The
prototype validation must be conducted in a formal set up with
proper test scripts prepared by the Vendor and approved by the
Owner.
Solution Prototype /
validation of
Conference room
pilot scripts
9.
The feedback provided to the Vendor after each round of
validation / conference room pilot must be documented and
signed off by the Owner nominated users.
Conference room
pilot Test report
10.
Changes to the solution must be presented to the users in next
round of solution validation or conference room pilot. This will be
an iterative process till the solution prototype is signed off as
acceptable by the project management team.
11.
The Vendor must deliver all custom development as has been
described in the business blueprint.
Custom development
12.
The Vendor must provide relevant documentation about the
business case for the custom development, description of the
code etc
Relevant
documentation
13.
The Vendor must integrate the SAP system with certain retained
legacy applications or new bolt-on applications. The detailed is
only an indicative list and the complete list will depend on the
final solution proposed by the Vendor and accepted by Owner.
Integration document
between ERP
Systems and other
satellite systems
14.
Process and methodology adopted for Quality Assurance must
be documented and periodic reports submitted to the project
management team.
Quality assurance
process document
15. User acceptance test.
User acceptance
certificate


Schedule
16.
Submit the Access control matrix template to Owner, after the
template is filled up, Configure the access control matrix in the
application.
Access control matrix
Template and the
configured application
print of the user
access.
17.
Based on the report and the feedback received from the users,
project management team may recommend additional tests to be
conducted in specific areas. Conduct of such additional tests and
the result must be documented by the Vendor.
Additional tests
conducted in specific
areas and test results
documented
2.3.4 SAP Application installation
18.
SAP will be installed in development, test and production
instances
Three instances up
and running
Vendor to suggest
suitable time line
Plan and
Methodology.
2.3.5 Data migration to SAP system
19.
The Vendor will provide the template in which each data element
to be converted must be provided by Owner.
Template for data to
be converted
Vendor to suggest
suitable time line
Plan and
Methodology.
20. The Vendor must validate the data provided in terms of format.
Validate data
provided in terms of
format
21.
The Vendor will prepare the necessary data conversion scripts
and document the same. He will also identify/provide necessary
reports to facilitate verification of data converted.
Data conversion
scripts & necessary
documentation
22.
The Vendor will execute complete / sample data conversion on
test instance for each data element and get sign off from users in
terms of adequacy and correctness.
Data conversion test
results for each data
element
23.
The data conversion test will also be conducted and signed off
by the users with assistance of the Vendor in terms of format,
completeness and correctness.
Data conversion Test
Certificate
24.
The Vendor will execute data conversion on production instance
and obtain signoff.
Data conversion
executed on
production instance
25.
The Vendor will provide a scheme for archival of old data
required to be maintained for statutory and other reporting
purposes and retrieval of the same in the new ERP environment.
Archival and retrieval
document
2.3.6 Go-live and Stabilization Support
26.
The Vendor will configure production instance of the SAP
solution with assistance from the Owners core team.
Fully configured
Production Instance
Vendor to suggest
suitable time line
Plan and
Methodology.
27.
The Vendor will present a cut-over strategy to the Project
Management Team for their validation and approval.
Cut-over strategy
28.
Executing the cut-over from the legacy applications to the ERP
solution in accordance with the approved cut-over strategy.
Executing cut-over
29.
In case the cut over does not synchronize with the accounting
period (such as beginning of the financial year etc), the Vendor
will suggest and provide the required strategy for building data
for the prior period.
Strategy for prior
period data build-up
30.
The Vendor will provide stabilization support for six months
(including six month-end closing and one quarter closing) after
go-live.
Post go-live
stabilisation support
for six months.
After going live
31.
The Vendor is expected to transfer knowledge to Owner and
provide guidelines in setting up and managing an SAP Helpdesk.
The knowledge and guidelines will encompass all aspects of the
help desk such as configuration, report writing, database
administration, system administration etc.
Knowledge transfer During Stabilisation
Support
32.
The Vendor will be responsible for providing detailed back-up
policy to the Owner.
Back-up Policy
During Stabilisation
Support


Schedule
33.
The Vendor will also provide a disaster recovery plan including
remote DR site for Owner keeping in mind the specific
operational requirements.
Disaster recovery
plan
34.
The Vendor will be responsible for providing a detailed upgrade
policy for the upgrade (minor as well as major) of all applications
being implemented as a part of this Project implementation.
Application upgrade
policy During Stabilisation
Support
35.
The Vendor will also provide a patch application guideline based
on the best practices in this regard
Patch application
guidelines
2.4. IMPLEMENTATION OF NON SAP APPLICATIONS
2.4.1 Acti ve Directory Control with SSO
1. Implementation of Active Directory with single sign on
All machines of
Owners network on
Active Directory
At least two month
prior to go-live date

2.
All the machines on active directory must be configured in such a
way that software maintenance, patch updating, maintenance
and monitoring are done from remote/ centralized location.
Centralized patch
updating, monitoring
and management of
the machines on
Active Directory
3. User acceptance Test
User acceptance test
report
2.4.2 Messaging and collaboration solution
1.
Implementation of messaging solution along with the web
interface
Integrated messaging
backbone
As soon as
possible. Expected
within two months
after starting the
project.
2. Implementation of the other collaboration tools for Collaboration tools
3. Integration of messaging solution with Black Berry.
Availability of
messaging services
on Black Berry
4.
Centralized back up and restoration process for the messaging
solution
High reliability and
zero data loss
report
2.4.3 Anti virus/Anti-spam/Content Filtering
1.
Configuration of Antivirus solution in all the users desktop, and
Windows servers
Protected PC,
Laptops and servers
from potential Virus,
Malware, Trojan etc.
At least two month
2.
Configuration of the anti-spam & content filtering solution in all
the relevant servers/ equipments.
Messaging solution
protected with anti
spam
3.
Configuring auto update for the servers, clients. Special
configuration for the mobile users for auto update from internet.
Regular automatic
update of the
patterns, engines etc
report
2.4.4 Enterprise Management System/ Network Management System & Service Desk
5.
Installation, configuration and testing of GSM based alert
system. EMS will send alarms and status through email/ GSM
based Alert system to at least ten designated mobile phones.
GSM Alert System
with installation and
configuration
document. At least one month
6.
installation and configuration of the EMS software with setting up
of major policies, monitoring parameters on Central Server
EMS Server
installation and
configuration
document.


Schedule
7.
Installation of necessary agents on monitored servers and
desktops
EMS Agent
installation and
configuration
document.
8.
Documentation and installation of the EMS on central server,
activation of user licenses etc. The documentation will cover:
a) Features of the EMS application, database, related software
and necessary licenses being supplied;
b) The process to be followed in installation of the EMS
application , database and the related software; at Central
server and monitored Servers, Desktops etc
Installation of the
EMS Application,
database, related
software and tools,
activation of user
licenses etc. and
submitting
documentation
9.
Detailed patch/upgrade procedure for the modules being
implemented at central server and monitored servers, desktops
etc
EMS patch/ upgrade
procedure
10.
Implementation of service desk tool with the associated
processes
a) Help Desk
b) Incident Management
c) Service Level Management
d) Problem Management with Known Error Database (KEDB)
e) Configuration Management with Configuration Management
Database (CMDB)
f) Change Management
Tool integrated with
function and
processes.
report
2.4.5 Building Management System for data center
12.
Supply, installation, configuration and testing of GSM based alert
system. BMS will send alarms and status through email/ GSM
based Alert system to atleast ten designated mobile phones.
GSM Alert System
with installation and
configuration
document.
At least one month
13. RF earthing for BMS. RF Earthing
14.
Installation and configuration of the BMS software with setting up
of major policies, monitoring parameters on Central Server. The
BMS system shall be concurrently monitored by two
administrators.
BMS Server
installation and
configuration
document.
15.
Documentation and installation of the BMS on central server,
activation of user licenses etc. The documentation will cover:
a) Features of the BMS Application, database, related software
and necessary licenses being supplied;
b) The process to be followed in installation of the BMS
Application , database and the related software; at Central
server
c) Network diagram of the BMS
d) Schematic Electrical diagrams indicating interlocks and
interface with BMS.
installation of the
BMS System,
database, related
software and tools,
activation of user
licenses etc. and
submitting
documentation

16.
Detailed patch/upgrade procedure for the modules being
implemented at Central server
BMS patch/ upgrade
procedure
report
2.4.6 Video Conferencing and IP Telephony
18. Implementation of Video conferencing applications
Video conferencing
capability among the
Owner and other
facilities
By go-live date
19. Implementation of IP Telephony applications
IP Telephony
communication


Schedule
among the Owner
and other facilities
report
1.
The Vendor will study the scope of the Agreement with respect
to existing processes, requirements, legacy applications, data
availability, integration, customization etc. He will present his
conclusions in the form of a Report and a presentation to the
Project management team
Project initiation
report & presentation
Vendor to suggest
suitable time line
based on Project Plan
and Methodology

2.
Once the above has been discussed and changes, if any,
incorporated, the Vendor will prepare the Project Plan in MS
Project and indicate the proposed approach towards key phases
/ activities of the project such as process study, legacy
applications integration, data conversion, change management,
training etc. The Project Plan and the high-level approach will be
discussed with / presented to the Project management team,
which may suggest changes if necessary.
Project Plan
3.
The Vendor will carry out a detailed study to fine tune the
specific requirements with respect to the hardware & networking
components. This will be spelt out in the hardware requirement
report
Hardware & network
requirement report
1.
The Vendor will give a report /presentation to the Project
management team on anticipated change management related
issues and proposed solution to overcome them.
Change management
approach report /
presentation
Vendor to suggest
suitable time line
based Project Plan
and Methodology

2.
The Vendor will provide guidelines in setting up an SAP
helpdesk including development of Service level agreements
(SLA).
SAP helpdesk
guidelines
3.
The Vendor will conduct change management programs on one-
on-one individual basis or in groups and at different locations.
Tentative schedule
and approach
document
4.
The Vendor will propose effectiveness measurement criteria on
change management and its monitoring.
Effectiveness
measurement
document
5.
Identify training requirements for Owner s core / system team
members and end-users.
Training requirement
Report
Vendor to suggest
suitable time line
based on Project Plan
and Methodology
6.
A detailed Training Plan giving details of content, duration and
training material to be provided to different categories of
participants as identified by the Owner Project Management
Team.
Training Plan for
Owner Users
7.
Specific training to Owner core team from product Vendor
followed by the Vendor and project management team to
prepare them for testing and accepting fully configured solution
prototype.
Training plan for
solution prototype
Validation
8.
Hands-on training to Owner s core team member on SAP
configurations, the processes and other applications.
SAP Training for
Owners core team
members
9.
Hands-on training to Owners technical team member on SAP
and other applications, including training to Owner database
administrators, system administrators including backup &
restoration, system executives for development including reports
and maintenance of package. .
SAP training for
Owner s system
team members
10.
Training to IT team on administration of servers, storage, SAN
and backup systems
Hardware training to
Owners system team
members
11.
A fully configured solution prototype for training Owner end-
users.
Configured solution
prototype for training
12. Extensive system administrative training to IT team for all the


Schedule
Non SAP applications and tools, information security, Data
center management, hardware and network management,
service desk related processes aligned with ITIL for help desk.
13.
Hands-on training to Owner end-users on SAP and Non-SAP
Applications.
SAP training for
Owners end-users.
14.
Preparation of Owners ERP solution training manual and end
user manuals keeping in mind the specific requirements of
processes and users at Owner.
Owners ERP solution
training and end user
manuals along with
online documentation
15.
Preparation of Owner ERP systems management manual
keeping in mind the specific configuration of solution
implemented at Owner.
Owner ERP systems
management manual


A2. Performance Parameters

Response Time for Tests:

User Activity to be guaranteed by the vendor All ERP Users
Direct
Connect
Remote
Connect
Menu Navigation Displaying the appropriate menu as per defined user role
and profile
<1 sec

<2 sec

Screen Opening Display of the selected data entry screen from the menu <2 sec <5 sec
Field Navigation Navigation between different data entry fields in the Screen <1 sec

<3 sec

Look up response Display of items from a List of Values <1 sec <10 sec
Look up response To display items from table <5 sec <15 sec
Screen Navigation Navigation between different data entry screens (from one
to another)
<1 sec <13 sec

Transaction Commit Transaction saving after completing the data entry <2 sec <20 sec

Query retrieval Online query entered by the user
Simple query
Medium Complexity query
High Complexity query

<5 sec
<8 sec
<15 sec

<12 sec
<15 sec
<20 sec
Reports response Report fired by the user from the Report Generator
Simple Report
Medium Complexity report
High Complexity report

<5 sec
<30 sec
<1 min

<12 sec
<25 sec
<3 min

The Response time mentioned above should be measured by using standard automated testing tools. The
Vendor should provide the details of tools & methodology to be used in measuring the response time mentioned
above. The response time will be tested for all users consisting 100% concurrent user.

Uptime Requirement:

The System shall have an availability of at least 99.90%. The formula for arriving at uptime figures is given in
Table-01 of Annexure-1. The Uptime includes the following infrastructural / System uptime collectively:
a) Database uptime,
b) Local area/Intranet network Uptime
c) SAP & Non SAP server uptime,
d) Portal Uptime,
e) VPN network uptime,
f) Branch offices application uptime
g) SAP and Non SAP software uptime
h) Other systems effecting SAP uptime.

Performance parameters of the Data Center

Performance parameters of the Data Centers shall be judged against the following major parameters:
a) Average illumination of the Data Center shall be 400 Lux.
b) UPS output shall be as follows, tested over a period of 72 Hours


i. Output Phase asymmetry for 100% imbalance load - <1%
ii. Output voltage harmonics for Non-linear load -<5%
iii. Battery backup duration testing for half an hour with load.
c) Automatic failover to DG set upon interruption of power and automatic shutdown of DG upon resumption of
power will be tested.
d) The Precision Air Conditioning system shall be tested at peak load conditions for a period of 72 hours. The
temperature shall be maintained at 21C 1C. The relative humidity shall be maintained 50% 5%.
e) The Fire Detection and suppression system shall tested by simulating various test scenarios proposed by
Owner.
f) Other tests as may be appropriate will also be conducted for the various components of the Data Center.


B. Deliverables & Service Level for the FMS
B1. Deliverables
Sr No Acti vity Deli verable Deli verable Schedule
7. POST IMPLEMENTATION SUPPORT / AMC of hardware & Network Component
1.
The Vendor will provide SAP application support which
would include but not limited to monitoring, incident,
problem, custom development, change, release,
configuration management, system setup/ rebuild, data,
backup, print management, coordination with SAP support
team.
Complete SAP
application support
by the Vendor
For 4 years from the
date of Final
Acceptance of the
Project.
2.
The vendor will provide Non-SAP application support
which would include but not limited to monitoring, incident,
problem, custom development, change, release,
configuration management, system setup/ rebuild, data,
backup, print management, coordination with Non-SAP
support team.
Complete Non-
SAP application
support by the
Vendor
date of Final
Acceptance of the
Project.
3.
The vendor will provide Infrastructure and Facility
Management which would include but not limited to help
desk support, user management, data center
management, server, storage administration, network
administration.
Complete
infrastructure and
facility
management by
the vendor
date of Final
Acceptance of the
Project.
4.
The bidder would coordinate with the hardware and
Network equipment manufacturer for any warranty related
issues and provide equipment maintenance including
spare parts required after post warranty period.
Complete
Maintenance
Support for
hardware &
Network
equipments within
& after Warranty
by the Vendor
date of Final
Acceptance of the
Project.

B2. Service Level of FMS

1. Criticality of Services:
Criticality level-1 Any server related issues like hardware failure, OS failure etc.
A critical problem, which affects large number of users / prioritised users /
networks / servers e.g. Server UPS, Gateway Routers, Layer-3 and Layer-2
core switches, networked printers, messaging servers, domain servers and
other mission critical server, including their power supplies for servers, routers
and L-3 and L-2 core switches etc.
A critical problem, affecting any segment of the LAN / WAN network or
connectivity between any two segments including security breach.
Criticality level-2 A major problem, which affects the individual user, e.g. PCs, desktop printers,
UPS, Access switches, hubs etc.
Criticality level-3 Other problems not covered in criticality-1 and criticality-2 items.


2. Criticality Level Classification

Component affected Criticality Level-1, which
affects large number of
users/prioritized
users/Network/ server
Criticality Level-2,
which affects the
individual user
Criticality Level-3
Server Server not booting up, Cannot
login to server, Database has
stopped
. Server upgrades, Bug
fixes, patch installations
Preventive maintenance.
Desktop PCs and
laptops
Desktops and Laptops of
prioritized users.
Slowing down of
PC, No display, Not
able to boot , Not
able to login,
Keyboard / mouse
not working, Virus
problem , Local
printing problems
Windows and MS
Office problems.
Hardware software
installation and upgrades,
New software installation,
Moves, adds, changes,
profile maintenance etc.
Network Failure of core switches, L-3
switches, routers.
distribution switches, Access
Switches,
Hubs Configuration change of
router
Software OS problem on Server, OS
corruption
Performance
tuning/response
time
New software installation
UPS Failure of Server, Core
switches, router, Centralised
UPS, Failure of UPS
connected to Access switches,
Hubs, network printers

Failure of UPS connected
to end users

IT Peripherals and
other activities
Any call of prioritized users,
Networked printers, L-3 and
L-2 switches, Centralized
printers
Desktop printers,
UPS
Problems in scanners,
peripherals and devices
etc. not covered in
criticality II, installation
of Desktops,
reconfiguration, creation
of profiles and movement
of equipment etc.
A list of other prioritized users shall be given to the Vendor at the time of commencement of the Agreement by the
Owner.

3. RESOLUTION / RESPONSE TIME:

Resolution time is the total time taken by the Vendor between registering the complaint at help desk of the site
and rectifying the fault. This time includes time taken to, diagnose, repair / replace the faulty
component/module/device and network equipment.


Criticality Levels
I II III
Desk side support SLA for remote resolution calls
Response Time Within 15 minutes Within 30 minutes Within 60 minutes
Resolution Time Within 30 minutes Within 60 minutes Within 90 minutes
Desk side support SLA for On-site call resolution
Data Centre equipment support SLA

4. SAP & Non-SAP Application Helpdesk Support

The help desk support to users shall be provided on 24 x 7 bases. The Vendor will follow response time as
detailed below:

Support
Category
Criteria Maximum
Response
Time
Resolution
Critical The system is unable to be used for normal business
activities.
30 Minutes 90 Minutes
Urgent There is a problem with part of the system, which
impacts on Owners decision making. No viable
workaround is available. There is a likelihood of financial
loss.
1 Hour 4 Hours
High The efficiency of users is being impacted, but has a
viable workaround.
4 Hours 8 Hours
Medium A low impact problem that affects the efficiency of users
but has a simple workaround.
8 Hours Based on OEM
confirmation
Low A fault, which has no particular impact on processing of
normal business activities.
8 Hours Based on OEM
confirmation


Annexure-3: Preliminary Implementation Plan
Implementation Plan
Vendor shall provide detailed time schedule for all items as per scope of work matching with the preliminary
implementation plan. Vendors shall have to submit a detailed Project Plan (which should be updated regularly)
indicating the key phases / activities of the project and the expected time lines for each phase / activity. The
Vendor shall further detail the Project Plan in early stages of the project and get the same validated from Owner.
Owners Project management team may suggest changes to the plan where necessary. The Project Plan should
include the following at minimum:
a) The project broken up into logical phases and sub-phases;
b) Activities making up the sub-phases and phases;
c) Key milestones and deliverables along with their dates;
d) Start date and end date for each activity;
e) The dependencies among activities;
f) Resources / consultants to be assigned to each activity;
g) Resources (core team, business team and process Owners) expected from Owner for each activity.

Implementation plan for the Project

Acti vities M0 M1 M2 M3 M4 M6 M7 M8 M9 10 11 12
Order release
Infrastructure Design
Data Center Setup
Hardware Setup
Network Setup
SAP Analyze Phase
SAP Design Phase
SAP Build Phase
SAP Integrate Phase
Deploy or Go-live phase
Stabilization Support
Active Directory (SSO)
Messaging Solution
Antivirus, Anti-Spam
Video Conf, IP Telephone
EMS/NMS,BMS
** M denotes calendar month.


Annexure-4: Price Schedule

A. Price Schedule for Project

2.1 Supply of Hardware & Non- SAP Software

FOR Unit
Rate in
INR
exclusi ve
of Taxes
& Duties
Amount
in INR
Taxes &
Duties
in INR
Taxes &
Duties in
INR
Taxes &
Duties
in INR
Total
Amount
in INR
1 UPS
2 Precision Air Conditioning System (PAC)
3 Fire Suppression Systems
4 Access Control Equipments
5 Water Leak & Rodent Control Systems
6 Civil work components (give break-up)
7 Electrical Components
8 Security system including CCTV, LCD,
Biometric reader, proximity control.

9 EMS / BMS Equipments
10 Data Safe
11 Any other
1 Servers
2 Rack with KVM
3 SAN Storage
4 Backup Devices
5
Other hardware (PCs with OS / Printers
etc.)

6 Any Other
2.1.3 Supply Hardware - Networking Components
1 Switches
2 Routers
3 Firewall / IPS
4 Modem
5 Fiber Optic Cable
6 UTP cable
7 Connectors
8 NMS
9 Network bandwidth cost


10 Any other item (give detailed break-up)
2.1.4 Supply Hardware - Video Conferencing Equipments
1
Video Conferencing Equipments(give
detailed break-up)

2.1.5 Supply Hardware IP Telephony Equipments
1
IP Telephony Equipments (give detailed
break-up)

2.1.6 Supply of Non-SAP Software Messaging & Collaboration System
1 Mailing Software
2 Blackberry enterprise software
2.1.7 Supply of Non-SAP Software Anti virus / AntiSpam / Content Filtering
1 Antivirus / Anti Spam / Content Filtering

2.1.8 Supply of Non-SAP Software NMS/EMS/Service Desk Tools
1 NMS/EMS Software & Service Desk Tools

2 Backup Software
2.1.9 Supply of Non-SAP Software BMS
1 BMS Software
2.1.10 Supply of Non-SAP Software Video conferencing System
1 Video Conferencing Software
1 IP telephony Software
1 Server Operating System
2 PC Operating System
3 Any Other Software (give detailed break-
up)


FOR Unit
Rate in
INR
exclusi ve
of Taxes
& Duties
Amount
in INR
Taxes &
Duties in
INR
Taxes &
Duties
in INR
Taxes &
Duties
in INR
Total
Amount
in INR
2 Installation and commissioning charges
(including Civil & Electrical works)

2.2.2 installation & commissioning of Hardware
1 Installation and commissioning of
Hardware

2.2.3 installation & commissioning of Networking Components
2 Installation, commissioning of Network
services


3 Establish Connectivity
2.2.4 installation & commissioning of Video Conferencing System
1 Installation, commissioning of Video
Conferencing System (give detailed break-
up)

2.2.5 installation & commissioning of IP Telephony System
1 Installation, commissioning of IP Telephony
System (give detailed break-up)

FOR Unit
Rate in
INR
exclusi ve
of Taxes
& Duties
Amount
in INR
Taxes &
Duties in
INR
Taxes &
Duties
in INR
Taxes &
Duties
in INR
Total
Amount
in INR
1 SAP Implementation as per scope
including 6 months post go live stabilization
support

2.4 Implementation of Non-SAP Applications
FOR Unit
Rate in
INR
exclusi ve
of Taxes
& Duties
Amount
in INR
Taxes &
Duties in
INR
Taxes &
Duties
in INR
Taxes &
Duties
in INR
Total
Amount
in INR
2.4.1 Active Directory Implementation with SOS
2.4.2 Messaging & Collaboration Solution with
Black Berry Integration

2.4.3 Anti Virus/Anti Spam/Content Filtering
2.4.4 EMS/NMS
FOR Unit
Rate in
INR
exclusi ve
of Taxes
& Duties
Amount
in INR
Taxes &
Duties in
INR
Taxes &
Duties
in INR
Taxes &
Duties
in INR
Total
Amount
in INR
1 Project Management
2 Change management & Training on all the
above services (with breakup)


B. Price Schedule for FMS
2.6 Post Implementation support services for running SAP Application, Non-SAP
Applications and Infrastructure Facility Management Services.

FOR Unit
Rate in
INR
exclusi ve
of Taxes
& Duties
Amount
in INR
Taxes &
Duties in
INR
Taxes &
Duties
in INR
Taxes &
Duties
in INR
Total
Amount
in INR
2.6.1 SAP application support
1 SAP Application Support
1 Active Directory administration
2 Messaging & collaboration, Blackberry apps
administration

3 Security Solution(Antivirus/Firewall IPS/Anti
Spam / Content Filtering application
administration

4 Video Conferencing & IP Telephony solution
administration

5 EMS/NMS/BMS application administration
2.6.3 Infrastructure and facility management
1 Help Desk
2 Desktop/Laptop
3 SAP App, database Servers
4 Non SAP and other servers
5 Router
6 Switch - L3
7 Firewall and other security equipments
8 Database
9 Leased Line and MPLS Links
2.6.4 Hardware and Network Equipment Maintenance
1 Maintenance Support within warranty
2 Maintenance Support after warranty
including parts


Annexure-5: Payment Milestone
A. Payment Milestone for Project
Item
Ref.
Item Description Payment Milestone Payment %
2.1 Supply of Hardware and non-SAP Software
2.1.1 Supply of Hardware - Data Center
Equipments
On supply of all Data center equipments and
physical verification by Owner at Project Site.
50% of
Total Cost
under 2.1.1 of
price schedule
On completion of installation, commissioning
& issue of final acceptance certificate for
Infrastructure
40% of
Total Cost
under 2.1.1 of
price schedule
On issue of Stabilization Acceptance
Certificate.
10% of
Total Cost
under 2.1.1 of
price schedule
2.1.2 Supply of Hardware - Servers, Storage,
Backup device, racks & other hardware
(PC/Printers) etc.
On supply of all hardware equipments and
physical verification by Owner at Project Site
50% of
Total Cost
under 2.1.2 of
price schedule
Infrastructure
40% of
Total Cost
under 2.1.2 of
price schedule
Certificate.
10% of
Total Cost
under 2.1.2 of
price schedule
2.1.3 Supply of Hardware Network Components On supply of all networking components and
50% of
Total Cost
under 2.1.3 of
price schedule
Infrastructure
40% of
Total Cost
under 2.1.3 of
price schedule
Certificate.
10% of
Total Cost
under 2.1.3 of
price schedule
2.1.4 Supply of Hardware Video Conferencing
System
On supply of all video conferencing
equipments and physical verification by
Owner at Project Site
50% of
Total Cost
under 2.1.4 of
price schedule
Infrastructure
40% of
Total Cost
under 2.1.4 of
price schedule
Certificate.
10% of
Total Cost
under 2.1.4 of
price schedule
2.1.5 Supply of Hardware IP Telephony System On supply of all IP telephony equipments and
50% of
Total Cost
under 2.1.5 of
price schedule
On completion of installation, commissioning 40% of


Infrastructure
Total Cost
under 2.1.5 of
price schedule
Certificate.
10% of
Total Cost
under 2.1.5 of
price schedule
2.1.6 Supply of Non-SAP Software Messaging &
Collaboration System
On supply of software license and physical
verification by Owner at Project Site
50% of
Total Cost
under 2.1.6 of
price schedule
On issue of Go-live Acceptance Certificate 40% of
Total Cost
under 2.1.6 of
price schedule
Certificate
10% of
Total Cost
under 2.1.6 of
price schedule
2.1.7 Supply of Non-SAP Software Anti Virus /
Anti Spam/ Content Filtering
On Supply of software license and physical
50% of
Total Cost
under 2.1.7 of
price schedule
Total Cost
under 2.1.7 of
price schedule
Certificate
10% of
Total Cost
under 2.1.7 of
price schedule
2.1.8 Supply of Non-SAP Software
EMS/NMS/Service Desk Tool
50% of
Total Cost
under 2.1.8 of
price schedule
Total Cost
under 2.1.8 of
price schedule
Certificate
10% of
Total Cost
under 2.1.8 of
price schedule
2.1.9 Supply of Non-SAP Software
BMS Software
50% of
Total Cost
under 2.1.9 of
price schedule
Total Cost
under 2.1.9 of
price schedule
Certificate
10% of
Total Cost
under 2.1.9 of
price schedule
2.1.10 Supply of Non-SAP Software Video
Conferencing & IP telephony Software
50% of
Total Cost
under 2.1.10 of
price schedule
Total Cost


under 2.1.10 of
price schedule
Certificate
10% of
Total Cost
under 2.1.10 of
price schedule
2.1.11 Supply of Non-SAP Software IP telephony
Software
50% of
Total Cost
under 2.1.11 of
price schedule
Total Cost
under 2.1.11 of
price schedule
Certificate
10% of
Total Cost
under 2.1.11 of
price schedule
2.1.12 Supply of Non-SAP Software Other
Software
50% of
Total Cost
under 2.1.12 of
price schedule
Total Cost
under 2.1.12 of
price schedule
Certificate
10% of
Total Cost
under 2.1.12 of
price schedule
2.2.1 Design, installation & commissioning of Data
Center
Infrastructure
80% of
Total Cost
under 2.2.1 of
price schedule
Certificate
20% of
Total Cost
under 2.2.1 of
price schedule
2.2.2 Installation & commissioning of Hardware On completion of installation, commissioning
Infrastructure
80% of
Total Cost
under 2.2.2 of
price schedule
Certificate
20% of
Total Cost
under 2.2.2 of
price schedule
2.2.3 Installation & commissioning of Networking
Component
Infrastructure
80% of
Total Cost
under 2.2.3 of
price schedule
Certificate
20% of
Total Cost
under 2.2.3 of
price schedule
Providing network services
As per charges
levied by
Network
Bandwidth
provider.
2.2.4 Installation & commissioning of On completion of installation, commissioning 80% of


Video Conferencing System & issue of final acceptance certificate for
Infrastructure
Total Cost
under 2.2.4 of
price schedule
Certificate
20% of
Total Cost
under 2.2.4 of
price schedule
2.2.5 Installation & commissioning of
IP Telephony System
Infrastructure
80% of
Total Cost
under 2.2.5 of
price schedule
Certificate
20% of
Total Cost
under 2.2.5 of
price schedule
2.3.1
2.3.2

2.3.3

2.3.4

2.3.5
2.3.6
Conducting Business Process Study
Mapping Businesses Process as per
Business Blueprinting
Conceptualising, developing, Configuration
and Testing of Solution
SAP Application installation on development,
quality and production instances.
Data Migration to SAP System
Go-live and Stabilization Support
Completion of business process study &
business blueprinting and respective sign-
offs
15% of Total
Cost under 2.3 of
price schedule
After issue of conference room pilot Test
certificate.
15% of Total
Cost under 2.3 of
price schedule
After user acceptance certification.
15% of Total
Cost under 2.3 of
price schedule
Data migration, data conversion executed on
production instance and signoff by Owner.
20% of Total
Cost under 2.3 of
price schedule
After Go-live Acceptance certification
20% of Total
Cost under 2.3 of
price schedule
Certificate
15% of Total
Cost under 2.3 of
price schedule
2.4 Implementation of Non-SAP Application
2.4.1
Active Directory Implementation with Single
Sign On(SOS)
75% of
Total Cost
Under 2.4.1 of
price schedule
Certificate
25% of
Total Cost
Under 2.4.1 of
price schedule
2.4.2
Messaging and Collaboration Solution with
Black Berry integration
75% of
Total Cost
Under 2.4.2 of
price schedule
Certificate
25% of
Total Cost
Under 2.4.2 of
price schedule
2.4.3
Anti Virus/Anti Spam/content Filtering
Solution
75% of
Total Cost
Under 2.4.3 of
price schedule
Certificate
25% of
Total Cost
Under 2.4.3 of
price schedule
2.4.4 EMS/NMS and service Desk Tools
After Go-live Acceptance Certification
75% of
Total Cost


Under 2.4.4
Certificate
25% of
Total Cost
Under 2.4.4 of
price schedule
75% of
Total Cost
Under 2.4.5 of
price schedule
Certificate
25% of
Total Cost
Under 2.4.5 of
price schedule
75% of
Total Cost
Under 2.4.6 of
price schedule
Certificate
25% of
Total Cost
Under 2.4.6 of
price schedule
2.4.7 IP telephony Application
75% of
Total Cost
Under 2.4.7 of
price schedule
Certificate
25% of
Total Cost
Under 2.4.7 of
price schedule
2.5 Project Management in different phases, Change Management and Training
2.5.1

Project management in different Phases
Change Management & Training
Resource mobilisation, kick-off, core team
finalisation, and detailed Project Plan and
Test Plan.
15% of the total
cost under 2.5 of
price schedule
Completion of business process study &
business blueprinting and respective sign-
offs
15% of the total
cost under 2.5 of
price schedule
After User Acceptance Certification
15 % of the total
cost under 2.5 of
price schedule
40% of the total
cost under 2.5 of
price schedule
Certificate
15% of the total
cost under 2.5 of
price schedule

B. Payment Milestone for FMS
Item
Ref.
Item Description Payment Milestone Payment %
2.6 Post Implementation Support Services for running SAP Application, Non SAP Applications and
Infrastructure Facility Management Services
2.6.1
2.6.2
2.6.3
2.6.4
SAP Application Support
Non-SAP Application Support
Infrastructure Facility Management
Hardware & network Equipment
Maintenance
On completion of each quarter of Service Pro-rata
quarterly basis
of 85% of the
Total Cost
under 2.6 of the
price schedule
On completion of the FMS. 15% of the
Total Cost
under 2.6


Annexure-6: Proforma for Performance Bank Guarantee (PBG)

PERFORMANCE BANK GUARANTEE IN LIEU OF SECURITY DEPOSIT
(On Non-Judicial Stamp Paper)

To
Ib Thermal Power Station,
At/Po-Banharpali,
Dist-Jharsuguda-768 234.

In consideration of the Orissa Power Generation Corporation Ltd. (Ib Thermal Power Station) having
registered office at 7
th.
Floor, Zone A, Fortune Towers, Chandrasekharpur, Bhubaneswar-751 023 (hereinafter
called the Owner which expression shall unless repugnant to the subject or context include its administrators
successors and assigns) having agreed to the price, terms and conditions of Tender and Letter of Intent bearing
no._____________ dated _____________ issued which has been unequivocally accepted by the Vendor ***M/s
____________________________ for the work of ______________________________ (hereinafter called the
said contract) to accept a performance Guarantee as herein provided for Rs. __________(Rupees
____________________________ only ) from a Nationalized bank in lieu of the security deposit to be made by
the Vendor or in lieu of the deduction to be made from the Vendors bills, for the due fulfillment of the terms and
conditions contained in the said Agreement by the said Vendor, We the _______________________ Bank
(hereinafter referred to as the said Bank and having our registered office at __________________________ do
hereby undertake and agree to indemnify and keep indemnified Owner from time to time to the extent of
Rs.________ (Rupees __________________________ only) against any loss or damage, costs, charges and
expenses caused to or suffered by or that may be caused to or suffered by Owner by reason of any breach or
breaches by the said Vendor of any of the terms and conditions contained in the said Agreement and to
unconditionally pay the amount claimed by Owner on demand and without demur to the extent aforesaid.
2. We______________________ Bank, further agree that Owner shall be the sole judge of and as to whether the
said Vendor has committed any breach or breaches of any of the terms and conditions of the said Agreement and
the extent of loss, damage, costs, charges and expenses caused to or suffered by or that may be caused to or
suffered by Owner on account thereof and the decision of Owner that the said Vendor has Committed such
breach or breaches and as to the amount or


amount of loss, damage, costs charges and expenses caused to or suffered by or that may be caused to or
suffered by Owner from time to time shall be final and binding on us.
3. We the said Bank further agree that the Guarantee herein contained shall remain in full force and effect during
the period that would be taken for the performance of the said Agreement and till all the dues of Owner under the
said Agreement or by virtue of any of the terms and conditions governing the said Agreement have been fully and
properly carried out by the said Vendor and accordingly discharges this Guarantee, subject, however, that Owner
shall have no claim under the Guarantee after 90 (Ninety) days from the date of expiry of the Defects Liability
period as provided in the said Agreement i.e. (Date) or from the date of cancellation of the said
Agreement, as the case may be, unless a notice of the claim under this Guarantee has been served on the Bank
before the expiry of the said period in which case the same shall be enforceable against the Bank not with
standing the fact, that the same is enforced after the expiry of the said period.
4. Owner shall have the full liberty without affecting in any way the liability of the Bank under this Guarantee or
indemnity, from time to time to vary any of the terms and conditions of the said Agreement or to extend time of
performance by the said Vendor or to postpone for any time and from time to time any of the powers exercisable
by it against the said Vendor and either to enforce or forbear from enforcing any of the terms and conditions
governing the said Agreement and either securities available to Owner and the said Bank shall not be released
from its liability under these presents by any exercise by Owner or of the liberty with reference to the matters
aforesaid or by reason of time being given to the said Vendor or any other forbearance, act or omission on the
part of Owner or any indulgence by Owner to the said Vendor or any other matter or thing whatsoever which
under the law relating to sureties would but for this provision have effect of so releasing the Bank from its such
liability
5. It shall not be necessary for Owner to proceed against the Vendor before proceeding against the Bank and the
Guarantee herein contained shall be enforceable against the Bank notwithstanding any security, which Owner
may have retained or obtained from the Vendor shall at the time when proceedings are taken against the Bank
hereunder be outstanding or unrealized.
6. We, the said Bank, lastly undertake not to revoke this Guarantee during its currency except with the prior
consent of Owner in writing and agree that any change in the Constitution of the said Vendor or the said Bank
shall not discharge our liability hereunder. If any further extension of this Guarantee is required the same shall be
extended to such required periods on receiving instructions from
M/s_________________________________________ on whose behalf this guarantee is issued.

In presence of


WITNESS For and on behalf of (Bank)
1. Signature____________________
2. Name & Designation___________
Authorisation No._____________
Date and Place ________________
Banks Seal__________________

*** NOTES:
FOR PROPRIETARY CONCERNS:
Shri___________________________ S/o_______________________________ resident of
______________________________ carrying on business under the name and style of
_________________________ at __________________________________ (hereinafter called the said
Vendor which expression shall unless the context requires otherwise include his heirs, executors, administrators
and legal representatives).
FOR PARTNERSHIP CONCERNS:
M/s ______________________________ a partnership firm with its office at _______________ __________
(hereinafter called the said Vendor which expression shall unless the context requires otherwise include their
heirs, executors, administrators and legal representatives); the names of their partners being (I) Shri
___________________________ S/o ________________________________________ (II) Shri
____________________ S/o ________________________________________ etc.
FOR COMPANIES
M/s _______________________ a company registered under the Companies Act, 1956 and having its
registered office in the state of __________________ (hereinafter called the said Vendor which expression shall
unless the context requires otherwise include its administrators, successors and assigns).


Annexure-7: Owner Safety Rules

The Vendor shall provide Personal Protective Equipments (like helmet, shoes, safety glass, nose mask and
earplug etc.) as many as required to all his workmen & ensure safety policy of Owner strictly otherwise they will
not be allowed to work. Standard of personal protective equipments to be provided by the Vendor to their
employees are indicated below.

1. Industrial safety helmet conforming IS: 2925
2. Safety shoes conforming IS: 9473-1993
3. Dust mask conforming IS: 9473-1983
4. Full body Harness along with Lifeline with fall arrestor
5. Safety glasses for dust protection (Lightweight safety glasses with side shield to protect against wind &
ultraviolet ray with adjustable side arms for personalized fit).
6. (i) Ear muff conforming IS:6229
(ii) Ear plug or Ear seal
Unique closed cell polyester from smooth tapered surface similar to ear canal, swells slowly to fit individual Ear
canal.
(Any one item out of three types of ear protection device should be issued)
7. Flame-Water-Oil-Acids & alkali resistant work wear (made of 100% cotton fabric)
8. Safety gloves of Kevlar or equivalent (high temp. resistance)
9. Face shield (conforming IS: 8521 part I type-I)
10. Electrical hand gloves 440v & 33 KV conforming IS: 4770
11. Hand gloves for chemical laboratory made from pure latex Acid and Alkali proof
12. Hand gloves for concentrated chemicals made from superior PVC inside cotton reinforce for better grip
13. Split chrome leather hand gloves for handling rough object.
14. Canvas hand gloves for handling smooth object & doing light work with it.
15. Flip up goggles with stationery frame fitted with ophthalmic grade zero power toughened lens and fitting
frame, Blue lens for furnace, Green shade No.4 for gas cutting, dark green No.11 for glasses for ARC
welding whenever is required.
16. Panoramic type safety goggles for acid & alkali whenever is required. Vendor shall ensure proper use of
personal protective equipment by their workmen and supervisor on duty.

Before issue of the above PPEs depending on the need of the area of work the sample of the same must be
provided to Owner Safety Officer for inspection & approval.

The Vendor shall be issued entry pass for their employees after due verification of the quality of the standard
PPEs and imparting necessary training well in advance (i.e. before 7 days of commencement of work) by Project
Manager / Safety Officer.

a) None of the Vendors employees shall be allowed inside the plant premises without valid gate pass,
safety shoes, helmet & safety glasses.
b) Vendor shall ensure that all his employees use proper PPEs inside the plant premises as per the work &
site requirement.
c) During the course of execution of the work the Vendor must ensure use of appropriate tested tools by
their workmen. Safe working practice must strictly be followed, e.g. use of proper plug & socket for
electrical connections, right size & standard spanner, right capacity and tested lifting & pulling equipment
etc.
d) The Vendor must ensure tidiness of the work place during & after completion of the work.
e) In case of any doubt relating to safety guidelines, the Vendor should seek advice of Project Manager /
Safety Officer immediately for clarification.
f) The Vendor must provide adequate first aid boxes at different locations and maintain a register to this
effect.
g) The Vendor should follow proper fire fighting procedure while executing the work.


h) The Vendor must provide proper barricades for excavations & other hazardous areas with proper marking
even during nighttime.
i) The Vendor should use proper & safe scaffoldings wherever required.
j) The Vendor should take utmost care & precaution while handling inflammable gases, compressed gases
& explosives.
k) The Vendor should use proper fall protection equipments while working at height and guard the bottom
area.
l) The Vendor should not use any metallic ladders inside ITPS premises.
m) The Vendor should use proper electrical & lifting tools having periodic testing & .
n) The Vendor should follow Owner policy for PTW, Hot work permit & confined space. Before starting any
work the Vendor should obtain the required clearance from the concerned authority.
o) The Vendor should follow all safety standards, codes, rules, regulations & acts as in force.
p) The Vendor must engage only experienced and qualified manpower to prevent any safety lapses during
execution of the work.

ANY DEFICIENCY IN SAFETY ASPECTS SHALL BE VIEWED SERIOUSLY BY OWNER. THE VENDOR WILL
BE PENALISED UP TO THE EXTENT OF Rs.10, 000/- (RUPEES TEN THOUSAND ONLY) PER EACH LAPSE
AS DETERMINED BY THE PROJ ECT MANAGER. OWNER RESERVES THE RIGHT TO TERMINATE THE
AGREEMENT AND DEBAR THE VENDOR TO PARTICIPATE ANY FUTURE BIDDING IN CASE OF
CONTINUED FLOUTING OF THE SAFETY NORMS PRESCRIBED BY OWNER.

OPGC ERP Implementation

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

OPGC ERP Implementation

Загружено:

Авторское право:

Доступные форматы

Confidential Page 1

ORISSA POWER GENERATION CORPORATION LIMITED

Вам также может понравиться