GOVERNMENT OF THE PEOPLE’S
REPUBLIC OF BANGLADESH
Supply, Installation, Testing,
Commissioning, Implementation and
related services of Network Devices and
Software for Information Systems
[Package: BB(G)IT-5]
Single-Stage Bidding
Bangladesh Bank
Head Office, Motijheel, Dhaka
Bangladesh
08 December 2015
BIDDING DOCUMENT (SINGLE-STAGE)
Issued on: 08 December 2015
Supply, Installation, Testing, Commissioning,
Implementation and related services of
Network Devices and Software for
Information Systems
IFB No: BB(G)IT-5
Project: Financial Sector Support Project
Purchaser: Bangladesh Bank, Bangladesh
v
CONTENTS
Section I. Instructions to Bidders (ITB).................................................................................9
Table of Clauses ...................................................................................................................9
Section II. Bid Data Sheet (BDS) ..........................................................................................45
Section III. Eligible Countries for the Provision of Goods, Works, and Services in BankFinanced Procurement ..........................................................................................................53
Section IV. General Conditions of Contract........................................................................57
Notes on the General Conditions of Contract (GCC) ........................................................57
Table of Clauses .................................................................................................................58
Section V. Special Conditions of Contract (SCC) .............................................................133
Table of Clauses ...............................................................................................................135
Section VI. Technical Requirements (including Implementation Schedule) ..................151
Table of Contents: Technical Requirements ....................................................................153
Section VII. Sample Forms .................................................................................................307
Notes to Bidders on working with the Sample Forms .....................................................308
Table of Sample Forms ....................................................................................................311
7
Invitation for Bids (IFB)
08 December 2015
Bangladesh
Financial Sector Support Project
Supply, Installation, Testing, Commissioning, Implementation and related services of
Network Devices and Software
Credit Number: 56640
IFB Title: Supply, Installation, Testing, Commissioning, Implementation and related
services of Network Devices and Software for Information Systems
IFB Number: BB(G)IT-5
1.
This Invitation for Bids (IFB) follows the General Procurement Notice (GPN) for this
project that appeared in UNDB online on 09 July 2015.
2.
The Peoples Republic of Bangladesh has received a credit from the International
Development Association toward the cost of Financial Sector Support Project, and
it intends to apply part of the proceeds of this credit to payments under the
agreement(s) resulting from this IFB: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network Devices and Software for
Information Systems, IFB number: BB(G)IT-5.
3.
The Bangladesh Bank serves as the implementing agency for the project and now
invites sealed bids from eligible Bidders for Supply, Installation, Testing,
Commissioning, Implementation and related services of Network Devices and
Software for Information Systems.
4.
Bidding will be conducted using the International Competitive Bidding (ICB)
procedures specified in the World Bank’s Guidelines: Procurement under IBRD
Loans and IDA Credits, edition of Procurement of Goods, Works and nonconsulting services under IBRD Loans and IDA Credits and Grants by World Bank
Borrowers dated January 2011 (revised July 2014), and is open to all Bidders
eligible as defined in these Guidelines that meet the following minimum qualification
criteria:
(a) The Bidder and the agent/subcontractor must have been in business for the last
five (05) years;
(b) The Bidder must have completed minimum one successful contract involving
supply, installation, testing, commissioning, integration and related technical
support services of Network Devices for Information Systems involving data
center and disaster recovery sites in last five (05) years;
(c) The Bidder must demonstrate present minimum average annual turnover of
US$ Seven (07) Million equivalent calculated as total certified payments
received for contracts in progress or completed within the last five (05) years;
8
Section I. Instructions to Bidders
(d) The Bidder must demonstrate minimum US$ Five (05) Million equivalent
present liquid asset and/or line of credit, net of current commitments;
(e) The agent and the subcontractor of the bidder must have at least three years
proven experience in providing warranty support services. The local agent and
the subcontractor’s relationship with the Principal/manufacturer shall be at
least two (02) years.
5.
Interested eligible Bidders may obtain further information from Bangladesh Bank
and inspect the bidding documents at the address given below from 11:00AM to
5:00PM Bangladesh Standard Time (GMT+6:00) on all working days. A pre-bid
meeting which potential bidders may attend will be held on Tuesday 22 December
2015 at 11:00AM Bangladesh Standard Time (GMT+6:00).
6.
A complete set of bidding documents in English may be purchased by interested
Bidders on submission of a written application to the address below and upon
payment of a nonrefundable fee of Bangladesh Taka Twenty Thousand (BDT
20,000) or in US Dollar Two Hundred Sixty (US$ 260). The method of payment will
be pay order or bank draft in favor of the Advertiser. The document will be sent by
Courier Service or may be collected in person. No bidding documents would be sold
on the day of Bid opening.
7.
Bids must be delivered to Jahangir Alam Conference Hall, Fourth Floor, Main
Building, Bangladesh Bank, Head Office, Motijheel, Dhaka at or before 02:00PM
Bangladesh Standard Time on Tuesday 19 January 2016. Bids need to be secured
by a Bid Security. The amount of Bid Security required is: Bangladesh Taka Five
Million (BDT 5,000,000/=) or equivalent amount in a freely convertible currency.
Late bids will be rejected. Bids will be opened in the presence of Bidders’
representatives who choose to attend at Jahangir Alam Conference Hall at 02:10PM
Bangladesh Standard Time on Tuesday 19 January 2016.
8.
The attention of prospective Bidders is drawn to (i) the fact that they will be required
to certify in their bids that all software is either covered by a valid license or was
produced by the Bidder and (ii) that violations are considered fraud, which can result
in ineligibility to be awarded World Bank-financed contracts.
9.
The attention of prospective Bidders is also drawn to the fact that at the time of
receipt of the bidding documents, they carefully check that they have received all
sections and attachments of the bidding documents. The Bidder may note that this IFB
is a part of the Information Systems to be procured by the Purchaser.
Kazi Nasir Ahmed
Executive Director (ICT)
6th Floor, Main Building, Bangladesh Bank, Head Office, Motijheel, Dhaka
Telephone: +880-2-9566211, Fax: +880-2-9566212, Email: kazi.nasir@bb.org.bd
Section I. Instructions to Bidders
9
SECTION I. INSTRUCTIONS TO BIDDERS (ITB)
(Single-Stage Bidding)
Table of Clauses
A. General ...............................................................................................................................11
1.
2.
3.
4.
5.
6.
7.
8.
Scope of Bid and Bidding Process ............................................................................11
Source of Funds ........................................................................................................11
Fraud and Corruption ................................................................................................12
Eligible Bidders ........................................................................................................14
Eligible Goods and Services .....................................................................................15
Qualifications of the Bidder ......................................................................................16
Cost of Bidding .........................................................................................................19
Site Visit ...................................................................................................................19
B. The Bidding Documents ...................................................................................................19
9.
10.
11.
Content of Bidding Documents ................................................................................19
Clarification of Bidding Documents and Pre-bid Meeting .......................................20
Amendment of Bidding Documents .........................................................................21
C. Preparation of Bids ...........................................................................................................21
12.
13.
14.
15.
16.
17.
18.
19.
Language of Bid ........................................................................................................21
Documents Comprising the Bid ................................................................................21
Bid Prices ..................................................................................................................23
Bid Currencies ..........................................................................................................26
Documents Establishing the Conformity of the Information System to the Bidding
Documents ................................................................................................................26
Securing the Bid ........................................................................................................27
Period of Validity of Bids .........................................................................................29
Format and Signing of Bid ........................................................................................30
D. Submission of Bids ............................................................................................................31
20.
21.
22.
23.
Sealing and Marking of Bids ....................................................................................31
Deadline for Submission of Bids ..............................................................................31
Late Bids ...................................................................................................................31
Withdrawal, Substitution, and Modification of Bids ................................................31
E. Bid Opening and Evaluation ............................................................................................33
24.
25.
26.
27.
Opening of Bids by Purchaser...................................................................................33
Clarification of Bids ..................................................................................................34
Preliminary Examination of Bids ..............................................................................34
Conversion to Single Currency .................................................................................35
10
Section I. Instructions to Bidders
28. Evaluation and Comparison of Bids .........................................................................35
29. Domestic Preference .................................................................................................41
30. Contacting the Purchaser ..........................................................................................41
F. Postqualification and Award of Contract .......................................................................41
31.
32.
33.
34.
35.
36.
37.
38.
Postqualification .......................................................................................................41
Award Criteria ..........................................................................................................42
Purchaser’s Right to Vary Quantities at Time of Award ..........................................42
Purchaser’s Right to Accept Any Bid and to Reject Any or All Bids.......................42
Notification of Award ...............................................................................................42
Signing of Contract ...................................................................................................43
Performance Security ................................................................................................43
Adjudicator ...............................................................................................................43
Section I. Instructions to Bidders
11
Instructions to Bidders
A. GENERAL
1. Scope of Bid
and Bidding
Process
2. Source of
Funds
1.1
The Purchaser named in the BDS and the SCC for GCC Clause
1.1 (b) (i), or its duly authorized Purchasing Agent if so
specified in the BDS (interchangeably referred to as “the
Purchaser” in these Bidding Documents), invites bids for the
supply and installation of the Information System (IS), as briefly
described in the BDS and specified in greater detail in these
Bidding Documents.
1.2
The title and identification number of the Invitation for Bids
(IFB) and resulting Contract(s) are provided in the BDS.
1.3
Throughout the Bidding Documents, the term "in writing" means
communicated in written form (e.g. by mail, e-mail, fax, telex)
with proof of receipt, and the term "days" means calendar days
unless a different meaning is evident from the context.
1.4
If the BDS so provides, alternative procedures forming part or all
of what is commonly known as e-Tendering are available to the
extent specified in, or referred to by, the BDS.
2.1
The Borrower named in the BDS has applied for or received a
loan or credit (as identified in the BDS, and called a “loan” in
these Bidding Documents) from the International Bank for
Reconstruction and Development or the International
Development Association (called “the Bank” in these Bidding
Documents) equivalent to the amount indicated in the BDS
toward the cost of the Project specified in the BDS. The
Borrower intends to apply a portion of the proceeds of this loan
to eligible payments under the Contract for which these Bidding
Documents are issued.
2.2
Payment by the Bank will be made only at the request of the
Borrower, or the Borrower’s executing agency, and upon
approval by the Bank in accordance with the terms and
conditions of the Loan Agreement, and will be subject in all
respects to the terms and conditions of that agreement. The Loan
Agreement prohibits a withdrawal from the loan account for the
purpose of any payment to persons or entities, or for any import
of goods, if such payment or import, to the knowledge of the
Bank, is prohibited by a decision of the United Nations Security
Council taken under Chapter VII of the Charter of the United
Nations. No party other than the Borrower shall derive any rights
12
Section I. Instructions to Bidders
from the Loan Agreement or have any claim to the loan
proceeds.
3. Fraud and
Corruption
3.1
It is the Bank’s policy to require that Borrowers (including
beneficiaries of Bank loans), as well as bidders, suppliers, and
contractors and their subcontractors under Bank-financed
contracts, observe the highest standard of ethics during the
procurement and execution of such contracts.1 In pursuance of
this policy, the Bank:
(a)
defines, for the purposes of this provision, the terms set
forth below as follows:
(i)
“corrupt practice”2 is the offering, giving, receiving
or soliciting, directly or indirectly, of anything of
value to influence improperly the actions of another
party;
(ii)
“fraudulent practice”3 is any act or omission,
including a misrepresentation, that knowingly or
recklessly misleads, or attempts to mislead, a party
to obtain a financial or other benefit or to avoid an
obligation;
(iii) “collusive practice”4 is an arrangement between two
or more parties designed to achieve an improper
purpose, including to influence improperly the
actions of another party;
(iv) “coercive practice”5 is impairing or harming, or
threatening to impair or harm, directly or indirectly,
any party or the property of the party to influence
improperly the actions of a party;
(v)
“obstructive practice” is
(aa) deliberately destroying, falsifying, altering or
1
In this context, any action taken by a bidder, supplier, contractor, or a sub-contractor to influence the
procurement process or contract execution for undue advantage is improper.
2
“Another party” refers to a public official acting in relation to the procurement process or contract
execution]. In this context, “public official” includes World Bank staff and employees of other
organizations taking or reviewing procurement decisions.
3
A “party” refers to a public official; the terms “benefit” and “obligation” relate to the procurement process
or contract execution; and the “act or omission” is intended to influence the procurement process or contract
execution.
4
“Parties” refers to participants in the procurement process (including public officials) attempting to
establish bid prices at artificial, non competitive levels.
5
A “party” refers to a participant in the procurement process or contract execution.
Section I. Instructions to Bidders
13
concealing of evidence material to the
investigation or making false statements to
investigators in order to materially impede a
Bank investigation into allegations of a corrupt,
fraudulent, coercive or collusive practice;
and/or threatening, harassing or intimidating
any party to prevent it from disclosing its
knowledge of matters relevant to the
investigation
or
from
pursuing
the
investigation; or
(bb) acts intended to materially impede the exercise
of the Bank’s inspection and audit rights
provided for under sub-clause 3.1 (e) below.
3.2
(b)
will reject a proposal for award if it determines that the
bidder recommended for award has, directly or through an
agent, engaged in corrupt, fraudulent, collusive, coercive
or obstructive practices in competing for the contract in
question;
(c)
will cancel the portion of the loan allocated to a contract if
it determines at any time that representatives of the
Borrower or of a beneficiary of the loan engaged in
corrupt, fraudulent, collusive, or coercive practices during
the procurement or the execution of that contract, without
the Borrower having taken timely and appropriate action
satisfactory to the Bank to address such practices when
they occur;
(d)
will sanction a firm or individual, including declaring
ineligible, either indefinitely or for a stated period of time,
to be awarded a Bank-financed contract if it at any time
determines that the firm has, directly or through an agent,
engaged in corrupt, fraudulent, collusive, coercive or
obstructive practices in competing for, or in executing, a
Bank-financed contract; and
(e)
will have the right to require that a provision be included
in bidding documents and in contracts financed by a Bank
loan, requiring bidders, suppliers, and contractors and
their sub-contractors to permit the Bank to inspect their
accounts and records and other documents relating to the
bid submission and contract performance and to have
them audited by auditors appointed by the Bank.
Furthermore, Bidders shall be aware of the provision stated in
Clause 9.8 and Clause 41.2 of the General Conditions of Contract.
14
4. Eligible
Bidders
Section I. Instructions to Bidders
3.3
Any communications between the Bidder and the Purchaser
related to matters of alleged fraud or corruption must be made in
writing.
3.4
By signing the Bid Submission Form, the Bidder represents that
it either is the owner of the Intellectual Property Rights in the
hardware, software or materials offered, or that it has proper
authorization and/or license to offer them from the owner of
such rights. For the purpose of this Clause, Intellectual Property
Rights shall be as defined in GCC Clause 1.1 (c) (xvii). Willful
misrepresentation of these facts shall be considered a fraudulent
practice subject to the provisions of Clauses 3.1 through 3.4
above, without prejudice of other remedies that the Purchaser
may take.
4.1
A Bidder, and all parties constituting the Bidder, may have the
nationality of any country, subject to the restrictions specified in
Section III, Eligible Countries. A Bidder shall be deemed to have
the nationality of a country if the Bidder is a citizen or is
constituted, incorporated, or registered and operates in
conformity with the provisions of the laws of that country.
4.2
If a prequalification process has been undertaken for the
Contract(s) for which these Bidding Documents have been
issued, only those Bidders may participate that had been
prequalified and continue to meet the eligibility criteria of this
Clause. A prequalified Joint Venture may not change partners or
its structure when submitting a bid.
4.3
A firm may be excluded from bidding if:
4.4
(a)
it was engaged by the Purchaser to provide consulting
services for the preparation of the design, specifications, or
other documents to be used for the procurement of the
Information System described in these Bidding
Documents; or
(b)
it is a government-owned enterprise in the Borrower’s
country, unless it can establish that it (i) is legally and
financially autonomous and (ii) operates under commercial
law. No dependent agency of the Borrower or SubBorrower shall be permitted to bid.
A firm that has been determined to be ineligible by the Bank in
relation to the Bank Guidelines On Preventing and Combating
Fraud and Corruption in Projects Financed by IBRD Loans and IDA
Section I. Instructions to Bidders
15
Credits and Grants shall be not be eligible to be awarded a contract.
4.5
5. Eligible Goods
and Services
A firm or individual is or will be disqualified from participation
in this bidding if, at any time from advertisement of the bidding
until and including contract award, the firm or individual is
under:
(a)
a suspension by the Purchaser agreed by the Bank as a
result of execution of a Bid-Securing Declaration pursuant
to ITB Clause 17.6 in another Bank-financed procurement,
or under a suspension by the Purchaser for other reasons
that have been agreed by the Bank; or
(b)
a declaration of ineligibility by the Bank in accordance
with ITB Clause 3.1 (d). The list of individuals and firms
debarred from participating in World Bank projects is
available at http://www.worldbank.org/debarr/, or
(c)
a sanction imposed by the United Nations Security
Council, as mentioned in ITB Clause 2.2.
(d)
a suspension by the Government of Bangladesh or its
Department or Agency published in CPTU website
http://www.cptu.gov.bd/DebarmentList
4.6
A firm or other entity that is ineligible according to any of the
above provisions of this Clause, may also not participate as a
Joint Venture partner, or as Subcontractor for or supplier of
goods, works or services. If a bid becomes materially incomplete
after removing ineligible entities, the bid may be disqualified.
4.7
Bidders shall provide such evidence of their continued eligibility
satisfactory to the Purchaser, as the Purchaser shall reasonably
request.
5.1
For the purposes of these Bidding Documents, the Information
System means all:
(a)
the required information technologies, including all
information processing and communications-related
hardware, software, supplies, and consumable items that
the Supplier is required to supply and install under the
Contract, plus all associated documentation, and all other
materials and goods to be supplied, installed, integrated,
and made operational (collectively called “the Goods” in
some clauses of the ITB); and
(b)
the
related
software
development,
transportation,
16
Section I. Instructions to Bidders
insurance,
installation,
customization,
integration,
commissioning, training, technical support, maintenance,
repair, and other services necessary for proper operation of
the Information System to be provided by the selected
Bidder and as specified in the Contract.
6. Qualifications
of the Bidder
5.2
Funds from Bank loans are disbursed only for expenditures for
an Information System made up of goods and services provided
by nationals of, and produced in or supplied from, eligible
source countries as defined in Section III, Eligible Countries. An
Information System is deemed to be produced in a certain
country when, in the territory of that country, through software
development, manufacturing, or substantial and major assembly
or integration of components, a commercially recognized
product results that is substantially different in basic
characteristics or in purpose or utility from its components.
5.3
For purposes of this clause, the nationality of the Bidder is
distinct from the country in which the Information System and
its goods components are produced or from which the related
services are supplied.
6.1
By submission of documentary evidence in its bid, the Bidder
must establish to the Purchaser’s satisfaction:
(a)
that it has the financial, technical, and production
capability necessary to perform the Contract, meets the
qualification criteria specified in the BDS, and has a
successful performance history. If a prequalification
process has been undertaken for the Contract(s) for which
these Bidding Documents have been issued, the Bidder
shall, as part of its bid, update any information submitted
with its application for prequalification;
(For the purposes of establishing a Bidder’s qualifications,
and unless stated to the contrary in the BDS, the
experience and / or resources of any Subcontractor will
not contribute to the Bidder’s qualifications; only those of
a Joint Venture partner will be considered.)
(b)
that, in the case of a Bidder offering to supply key goods
components of the Information System, as identified in
the BDS, that the Bidder does not itself produce, the
Bidder is duly authorized by the producer to supply those
components in the Purchaser’s country under the
Contract(s) that may result from this bidding; (This will be
accomplished by including Manufacturer’s Authorizations
Section I. Instructions to Bidders
17
in the bid, based on the sample found in Section VII.)
6.2
(c)
that, if a Bidder proposes Subcontractors for key services
if and as identified in the BDS, these Subcontractors have
agreed in writing to serve for the Bidder under the
Contract(s) that may result from this bidding; and
(d)
that, in the case of a Bidder not doing business within the
Purchaser’s country, the Bidder is or will be (if awarded
the Contract) represented by an Agent in that country who
is equipped and able to carry out the Bidder’s
maintenance, technical support, training, and repair
obligations prescribed in the General and Special
Conditions of Contract, and/or Technical Requirements.
Bids submitted by a Joint Venture of two or more firms as
partners shall also comply with the following requirements:
(a)
the bid shall be signed so as to be legally binding on all
partners;
(b)
one of the partners shall be nominated as being in charge,
and this nomination shall be evidenced by submitting a
power of attorney signed by legally authorized signatories
of all the partners;
(c)
the partner in charge shall be authorized to incur liabilities
and receive instructions for and on behalf of any and all
partners of the Joint Venture, and the entire execution of
the Contract, including payment, shall be done exclusively
with the partner in charge;
(d)
the partner or combination of partners that is responsible
for a specific component of the Information System must
meet the relevant minimum qualification criteria for that
component;
(e)
a firm may submit bids either as a single Bidder on its
own, or as partner in one, and only one, Joint Venture. If,
as a result of the bid opening pursuant to ITB Clause 24,
this requirement is not met, all bids involving the firm as a
single Bidder or Joint Venture partner will be disqualified;
(f)
all partners of the Joint Venture shall be liable jointly and
severally for the execution of the Contract in accordance
with the Contract terms, and a statement to this effect shall
be included in the authorization mentioned under ITB
Clause 6.2 (b) above, in the bid as well as in the Contract
18
Section I. Instructions to Bidders
(in case of a successful bid).
6.3
If a Bidder intends to subcontract major items of supply or
services, it shall include in the bid details of the name and
nationality of the proposed Subcontractor for each of those items
and shall be responsible for ensuring that any Subcontractor
proposed complies with the requirements of ITB Clause 4, and
that any Goods or Services components of the Information
System to be provided by the Subcontractor comply with the
requirements of ITB Clause 5 and the related evidence required
by ITB Clause 13.1 (e) (iii) is submitted. Bidders are free to list
more than one Subcontractor against each item. Quoted rates and
prices will be deemed to apply, whichever Subcontractor is
appointed, and no adjustment of the rates or prices will be
permitted. The Purchaser reserves the right to delete any
proposed Subcontractor from the list. This shall be done prior to
Contract signature, by deleting such unacceptable Subcontractors
from Appendix 3 to the Contract Agreement, which shall list the
approved Subcontractors for each item prior to Contract
signature. Subsequent additions and deletions from the list of
approved Subcontractors shall be performed in accordance with
GCC Clause 20 (as revised in the SCC, if applicable) and
Appendix 3 to the Contract Agreement.
For the purposes of these Bidding Documents, a Subcontractor is
any vendor or service provider with whom the Bidder contracts
for the supply or execution of any part of the Information System
to be provided by the Bidder under the Contract (such as the
supply of major hardware, software, or other components of the
required Information Technologies specified, or the performance
of related Services, e.g., software development, transportation,
installation, customization, integration, commissioning, training,
technical support, maintenance, repair, etc.).
6.4
A firm which is a Bidder, whether as a single Bidder or as a
partner in a Joint Venture, cannot be a Subcontractor in other
bids, except for the supply of commercially available hardware
or software by the firm, as well as purely incidental services such
as installation/configuration, routine training, and ongoing
maintenance/support. If the BDS for ITB Clause 6.1 (a) allows
the qualification of Subcontractors nominated for certain
components to be taken into account in assessing the Bidder’s
overall qualifications, any Subcontractor so nominated by any
Bidder is automatically disqualified from being a Bidder itself or
a partner in a Joint Venture. The same will normally apply to
firms that have provided Subcontractor agreements for certain
Section I. Instructions to Bidders
19
services pursuant to ITB Clause 6.1 (c). Non-compliance may
result in the rejection of all bids in which the affected firm
participates as Bidder or as partner in a Joint Venture. As long as
in compliance with these provisions, or as long as unaffected by
them due to not participating as Bidder or as partner in a Joint
Venture, a firm may be proposed as a Subcontractor in any
number of bids. If the BDS for ITB 28.1 permits the submission
of bids for Subsystems, lots, or slices, then the provisions of this
Clause 6.4 apply only to bids for the same Subsystem(s), lot(s),
or slice(s);
7. Cost of
Bidding
7.1
The Bidder shall bear all costs associated with the preparation
and submission of its bid, and the Purchaser will in no case be
responsible or liable for those costs.
8. Site Visit
8.1
The Bidder may wish to visit and examine the site or sites of the
Information System and obtain for itself, at its own
responsibility and risk, all information that may be necessary for
preparing the bid and entering into the Contract. The costs of
visiting the site or sites shall be at the Bidder’s own expense.
8.2
The Purchaser will arrange for the Bidder and any of its
personnel or agents to gain access to the relevant site or sites,
provided that the Bidder gives the Purchaser adequate notice of a
proposed visit of at least fourteen (14) days. Alternatively, the
Purchaser may organize a site visit or visits concurrently with the
pre-bid meeting, as specified in the BDS for ITB Clause 10.2.
Failure of a Bidder to make a site visit will not be a cause for its
disqualification.
8.3
No site visits shall be arranged or scheduled after the deadline
for the submission of the Bids and prior to the award of
Contract.
B. THE BIDDING DOCUMENTS
9. Content of
Bidding
Documents
9.1
The contents of the Bidding Documents are listed below and
should be read in conjunction with any addenda issued in
accordance with ITB Clause 11:
Section I
Instructions to Bidders (ITB)
Section II
Bid Data Sheet (BDS)
Section III
Eligible Countries for the Provision of Goods,
Works, and Services in Bank-Financed
20
Section I. Instructions to Bidders
Procurement
Section IV
General Conditions of Contract (GCC)
Section V
Special Conditions of Contract (SCC)
Section VI
Technical Requirements (including
Implementation Schedule)
Section VII
Sample Forms
9.2
Bidders are expected to examine all instructions, forms, terms,
specifications, and other information in the Bidding Documents.
Failure to furnish all information required by the Bidding
Documents or to submit a bid not substantially responsive to the
Bidding Documents in every respect will be at the Bidder’s risk
and may result in the rejection of its bid.
9.3
The Invitation for Bids is not formally part of the Bidding
Documents and is included for reference only. In case of
inconsistencies, the actual Bidding Documents shall prevail.
10. Clarification of 10.1 A prospective Bidder requiring any clarification of the Bidding
Documents may notify the Purchaser in writing at the
Bidding
Documents
Purchaser’s address and by one of the means indicated in the
and Pre-bid
BDS. Similarly, if a Bidder feels that any important provision in
Meeting
the documents will be unacceptable, such an issue should be
raised as soon as possible. The Purchaser will respond in writing
to any request for clarification or modification of the Bidding
Documents that it receives no later than twenty-one (21) days
prior to the deadline for submission of bids prescribed by the
Purchaser. Copies of the Purchaser’s response (including an
explanation of the query but not identifying its source) will be
sent to all prospective Bidders that received the Bidding
Documents from the Purchaser.
10.2 When specified in the BDS, the Purchaser will organize and
Bidders are welcome to attend a pre-bid meeting at the time and
place indicated in the BDS. The purpose of the meeting will be
to clarify issues and answer questions on any matter that may be
raised at this stage, with particular attention to issues related to
the Technical Requirements. Bidders are requested to submit any
questions in writing to reach the Purchaser not later than one
week before the meeting. Questions and answers will be
transmitted in accordance with ITB Clause 10.1. Minutes of the
meeting, including the questions raised and responses given,
together with any responses prepared after the meeting, will be
transmitted without delay to all those that received the Bidding
Section I. Instructions to Bidders
21
Documents from the Purchaser. Any modification to the Bidding
Documents listed in ITB Clause 9.1, which may become
necessary as a result of the pre-bid meeting, shall be made by the
Purchaser exclusively by issuing an Addendum pursuant to ITB
Clause 11 and not through the minutes of the pre-bid meeting.
11. Amendment of
Bidding
Documents
11.1 At any time prior to the deadline for submission of bids, the
Purchaser may, for any reason, whether at its own initiative or in
response to a clarification requested by a prospective Bidder,
amend the Bidding Documents. Later amendments on the same
subject modify or replace earlier ones.
11.2 Amendments will be provided in the form of Addenda to the
Bidding Documents, which will be sent in writing to all
prospective Bidders that received the Bidding Documents from
the Purchaser. Addenda will be binding on Bidders. Bidders are
required to immediately acknowledge receipt of any such
Addenda. It will be assumed that the amendments contained in
such Addenda will have been taken into account by the Bidder in
its bid.
11.3 In order to afford prospective Bidders reasonable time in which
to take the amendment into account in preparing their bids, the
Purchaser may, at its discretion, extend the deadline for the
submission of bids, in which case, the Purchaser will notify all
Bidders in writing of the extended deadline.
C. PREPARATION OF BIDS
12. Language of
Bid
12.1 The bid prepared by the Bidder and all correspondence and
documents related to the bid exchanged by the Bidder and the
Purchaser shall be written in the language specified in the BDS,
or, if the BDS so provides, in either one of two languages
specified there. Any printed literature furnished by the Bidder as
part of its bid may be in a language not specified in the BDS, as
long as such literature is accompanied by a translation of its
pertinent passages into the language of the bid, in which case, for
purposes of interpretation of the bid, the translation shall govern.
13. Documents
Comprising
the Bid
13.1 The bid submitted by the Bidder shall comprise:
(a)
Bid Submission Form completed and signed by a person or
persons duly authorized to bind the Bidder to the Contract;
(b)
all Price Schedules duly completed in accordance with ITB
Clauses 14, 15, and 18 and signed by a person or persons
22
Section I. Instructions to Bidders
duly authorized to bind the Bidder to the Contract;
(c)
if required, Bid-securing Declaration or Bid Security
furnished in accordance with ITB Clause 17;
(d)
written confirmation authorizing the signatory of the bid to
commit the Bidder, in accordance with ITB Clause 19.2;
(e)
Attachments:
(i)
Attachment 1: Bidder’s Eligibility
In the absence of prequalification, documents
establishing to the Purchaser’s satisfaction the
Bidder’s eligibility to bid, including but not limited to
documentary evidence that the Bidder is legally
incorporated in a territory of an eligible source
country as defined under ITB Clause 4;
(ii)
Attachment 2: Bidder’s Qualifications
Documentary evidence establishing to the
Purchaser’s satisfaction, and in accordance with ITB
Clause 6, that the Bidder is qualified to perform the
Contract if its bid is accepted. In the case where
prequalification of Bidders has been undertaken, and
pursuant to ITB Clause 6.1 (a), the Bidder must
provide evidence on any changes in the information
submitted as the basis for prequalification or, if there
has been no change at all in said information, a
statement to this effect;
Any Manufacturer’s Authorizations and Subcontractor
agreements specified as required in the BDS for ITB
Clauses 6.1 (b) and 6.1 (c);
(iii) Attachment 3: Eligibility of Goods and Services
Documents establishing, to the Purchaser’s
satisfaction, that the Goods and Services components
of the Information System to be supplied, installed,
and/or performed by the Bidder are eligible Goods
and Services as defined under ITB Clause 5. If
awarded the Contract, the Bidder shall submit for
such components of the Information System evidence
of eligibility, which shall be confirmed by a
certificate of origin issued at the time of shipment;
(iv) Attachment 4: Conformity of the Information System
Section I. Instructions to Bidders
23
to the Bidding Documents
Documentary evidence establishing to the
Purchaser’s satisfaction, and in accordance with ITB
Clause 16, that the Goods and Services components
of the Information System to be supplied, installed,
and/or performed by the Bidder conform to the
Bidding Documents;
(v)
Attachment 5: Proposed Subcontractors
A list of all major items of Goods or Services that the
Bidder proposes to purchase or subcontract from
others, and the name and nationality of the proposed
Subcontractor, including vendors, for each of those
items;
(vi) Attachment 6: Intellectual Property
A list of:
(1)
all Software included in the Bidder’s bid,
assigning each item to one of the software
categories defined in GCC Clause 1.1 (c):
(A) System, General Purpose, and Application
Software; and
(B) Standard and Custom Software.
(2)
all Custom Materials, as defined in GCC Clause
1.1 (c), included in the Bidder’s bid.
All Materials not identified as Custom Materials shall
be deemed Standard Materials, as defined in GCC
Clause 1.1 (c).
Re-assignments among the Software and Materials
categories, if necessary, will be made during the
implementation of the Contract according to GCC
Clause 39 (Changes to the System).
14. Bid Prices
14.1 All Goods and Services identified in the Supply and Installation
Cost Sub-Table and the Recurrent Cost Sub-Table in Section VII
(Forms 2.5 and 2.6), and all other Goods and Services proposed
by the Bidder to fulfill the requirements of the Information
System, must be priced separately in the format of the same
tables and summarized in the corresponding Cost Summary
Tables in the same Section. Prices must be quoted in accordance
24
Section I. Instructions to Bidders
with the instructions provided in Section VII for the various cost
tables, in the manner specified below.
14.2 The price of items that the Bidder has left blank in the cost
tables provided in Section VII shall be assumed to be included
in the price of other items. Items omitted altogether from the
cost tables shall be assumed to be omitted from the bid and,
provided that the bid is substantially responsive, an adjustment
to the bid price will be made during evaluation in accordance
with ITB Clause 28.6 (c) (iii).
14.3 Unit prices must be quoted at a level of detail appropriate for
calculation of any partial deliveries or partial payments under the
contract, in accordance with the Implementation Schedule in
Section VI, and with GCC and SCC Clause 12 – Terms of
Payment. Bidders may be required to provide a breakdown of
any composite or lump-sum items included in the Cost Tables.
14.4 The prices for Goods components of the System are to be
expressed and shall be defined and governed in accordance with
the rules prescribed in the edition of Incoterms specified in the
BDS, and quoted in the appropriate columns of the cost tables of
Section VII as follows:
(a)
Goods supplied from outside the Purchaser’s country:
Unless otherwise specified in the BDS, the prices shall be
quoted on a CIP (named place of destination) basis,
exclusive of all taxes, stamps, duties, levies, and fees
imposed in the Purchaser’s country. The named place of
destination and special instructions for the contract of
carriage are as specified in the BDS. In quoting the price,
the Bidder shall be free to use transportation through
carriers registered in any eligible countries. Similarly, the
Bidder may obtain insurance services from any eligible
source country.
(b)
Locally supplied Goods:
Unit prices of Goods offered from within the Purchaser’s
Country, shall be quoted on an EXW (ex factory, ex works,
ex warehouse or off-the-shelf, as applicable) basis,
including all customs duties, levies, fees, sales and other
taxes incurred until delivery of the Goods, but excluding all
VAT or sales and other taxes and duties/fees incurred for
the Goods at the time of invoicing or sales transaction, if
the Contract is awarded.
Section I. Instructions to Bidders
25
(c)
Inland transportation:
Unless otherwise stated in the BDS, inland transportation,
insurance and related local costs incidental to the delivery
of the Goods to the designated Project Sites must be quoted
separately as a Service item in accordance with ITB Clause
14.5, whether the Goods are to be supplied locally or from
outside the Purchaser’s country, except when these costs
are already included in the price of the Goods, as is, e.g.,
the case, when ITB Clause 14.4 (a) specifies CIP, and the
named places of destination are the Project Sites.
14.5 The price of Services shall be quoted in total for each service
(where appropriate, broken down into unit prices), separated into
their local and foreign currency components. Prices must include
all taxes, duties, levies and fees whatsoever, except only VAT or
other indirect taxes, or stamp duties, that may be assessed and/or
apply in the Purchaser’s country on/to the price of the Services
invoiced to the Purchaser, if the Contract is awarded. Unless
otherwise specified in the BDS, the prices must include all costs
incidental to the performance of the Services, as incurred by the
Supplier, such as travel, subsistence, office support,
communications, translation, printing of materials, etc. Costs
incidental to the delivery of the Services but incurred by the
Purchaser or its staff, or by third parties, must be included in the
price only to the extent such obligations are made explicit in
these Bidding Documents (as, e.g., a requirement for the Bidder
to include the travel and subsistence costs of trainees).
14.6 Prices for Recurrent Costs beyond the scope of warranty services
to be incurred during the warranty Period, defined in SCC
Clause 29.4 and prices for Recurrent Costs to be incurred during
the Post- warranty Period, defined in SCC Clause 1.1. (e) (xii),
shall be quoted as Service prices in accordance with ITB Clause
14.5 on the Recurrent Cost Sub-Table in detail, and on the
Recurrent Cost Summary Table in currency totals. Recurrent
costs are all-inclusive of the costs of necessary Goods such as
spare parts, software license renewals, labor, etc., needed for the
continued and proper operation of the System and, if appropriate,
of the Bidder’s own allowance for price increases.
14.7 Unless otherwise specified in the BDS, prices quoted by the
Bidder shall be fixed during the Bidder’s performance of the
Contract and not subject to increases on any account. Bids
submitted that are subject to price adjustment will be rejected.
26
15. Bid Currencies
Section I. Instructions to Bidders
15.1 Prices shall be quoted in the following currencies:
(a)
The Bidder may quote its prices for all Information
Technologies, associated Goods, and Services to be
supplied from outside the Purchaser’s Country in the
currencies of countries eligible according to Section III. If
the Bidder wishes to be paid in a combination of different
currencies, it must quote unit prices accordingly, but no
more than three foreign currencies may be used.
(b)
Unless otherwise specified in the BDS, the Bidder shall
express its prices for such Information Technologies,
associated Goods, and Services to be supplied locally (i.e.,
from within the Purchaser’s Country) in the currency of the
Purchaser’s Country.
16.1 Pursuant to ITB Clause 13.1 (e) (iv), the Bidder shall furnish, as
16. Documents
part of its bid, documents establishing the conformity to the
Establishing
Bidding Documents of the Information System that the Bidder
the Conformity
proposes to supply and install under the Contract.
of the
Information
16.2 The documentary evidence of conformity of the Information
System to the
System to the Bidding Documents shall be in the form of written
Bidding
descriptions, literature, diagrams, certifications, and client
Documents
references, including:
(a)
the Bidder’s technical bid, i.e., a detailed description of the
Bidder’s proposed technical solution conforming in all
material aspects with the Technical Requirements (Section
VI) and other parts of these Bidding Documents, overall as
well as in regard to the essential technical and performance
characteristics of each component making up the proposed
Information System;
(b)
an item-by-item commentary on the Purchaser’s Technical
Requirements,
demonstrating
the
substantial
responsiveness of the Information System offered to those
requirements. In demonstrating responsiveness, the
commentary shall include explicit cross references to the
relevant pages in the supporting materials included in the
bid. Whenever a discrepancy arises between the item-byitem commentary and any catalogs, technical
specifications, or other preprinted materials submitted with
the bid, the item-by-item commentary shall prevail;
(c)
a Preliminary Project Plan describing, among other things,
the methods by which the Bidder will carry out its overall
Section I. Instructions to Bidders
27
management and coordination responsibilities if awarded
the Contract, and the human and other resources the Bidder
proposes to use. The Plan should include a detailed
Contract Implementation Schedule in bar chart form,
showing the estimated duration, sequence, and
interrelationship of all key activities needed to complete
the Contract. The Preliminary Project Plan must also
address any other topics specified in the BDS. In addition,
the Preliminary Project Plan should state the Bidder’s
assessment of what it expects the Purchaser and any other
party involved in the implementation of the Information
System to provide during implementation and how the
Bidder proposes to coordinate the activities of all involved
parties;
(d)
a written confirmation that the Bidder accepts
responsibility for the successful integration and interoperability of all components of the Information System as
required by the Bidding Documents.
16.3 For purposes of the commentary to be furnished pursuant to ITB
Clause 16.2 (b), the Bidder shall note that references to brand
names or model numbers or national or proprietary standards
designated by the Purchaser in its Technical Requirements are
intended to be descriptive and not restrictive. Except where
explicitly prohibited in the BDS for specific items or standards,
the Bidder may substitute alternative brand/model names or
standards in its bid, provided that it demonstrates to the
Purchaser’s satisfaction that the use of the substitute(s) will
result in the Information System being able to perform
substantially equivalent to or better than that specified in the
Technical Requirements.
17. Securing the
Bid
17.1 The BDS for this Clause specifies whether bids must be secured,
and if so, whether by a Bid-Securing Declaration or by a Bid
Security. If a Bid Security is required or optional, the BDS also
specifies the amount.
17.2 Securing the bids shall be substantially in accordance with the
related sample forms included in Section VII or other forms
approved by the Purchaser prior to bid submission. Bids must
remain secured for a period of 28 days beyond the validity period
of the bids, as extended, if applicable, in accordance with ITB
Clause 18.2. In case of a Bid Security, it shall also:
(a)
at the Bidder’s option, be in the form of either a certified
check, letter of credit, or a bank guarantee from a banking
28
Section I. Instructions to Bidders
institution, or a bond issued by a surety;
(b)
be issued by a reputable institution selected by the Bidder
and located in any eligible country; if the institution issuing
the security is located outside the Purchaser’s Country, it
shall have a correspondent financial institution located in
the Purchaser’s Country to make the security enforceable;
(c)
be payable promptly upon written demand by the Purchaser
in case any of the conditions listed in ITB Clause 17.6
is/are invoked;
(d)
be submitted in its original form; copies will not be
accepted.
17.3 The Bid-Securing Declaration or the Bid Security of a Joint
Venture shall be issued in the name of the Joint Venture
submitting the bid provided the Joint Venture has legally been
constituted, or else it shall be issued in the name of all partners
proposed for the Joint Venture in the bid. Sanctions due to a
breach of the terms of a Bid-Securing Declaration pursuant to
ITB Clause 17.6 will apply to all partners to the Joint Venture.
17.4 If a Bid-Securing Declaration or Bid Security is required in
accordance with ITB Clause 17.1, any bid not accompanied by a
substantially acceptable Bid-Securing Declaration or Bid
Security in accordance with ITB Clauses 17.2 and 17.3, shall be
rejected by the Purchaser as non-responsive.
17.5 Unless executed or forfeited pursuant to ITB Clause 17.6, BidSecuring Declarations, if any, will expire for, or Bid Securities,
if any, will be returned as promptly as possible to,
(a)
all Bidders upon annulment of the bidding pursuant to ITB
Clause 34;
(b)
Bidders refusing a request to extend the period of validity
of their bids pursuant to ITB Clause 18.2;
(c)
the successful Bidder once it has signed the Contract
Agreement and furnished a valid Performance Security as
required;
(d)
the unsuccessful Bidders at the same time as in (c), that is,
when they are informed about the successful establishment
of the contract with the successful Bidder.
Section I. Instructions to Bidders
29
17.6 The Bid-Securing Declaration, if any, may be executed, or the
Bid Security, if any, may be forfeited:
(a)
if a Bidder withdraws its bid during the period of bid
validity specified by the Bidder on the Bid Submission
Form or any extension of validity the Bidder has agreed to
pursuant to ITB Clause 18.2; or
(b)
in the case of the successful Bidder, if the Bidder fails to:
(i)
(ii)
sign the Contract Agreement in accordance with ITB
Clause 36; or
furnish the Performance Security in accordance with ITB Clause
37.
17.7 If a bid security is not required in the BDS, and
(a)
if a Bidder withdraws its bid during the period of bid
validity specified by the Bidder on the Letter of Bid Form,
except as provided in ITB 18.2, or
(b)
if the successful Bidder fails to: sign the Contract in
accordance with ITB 36; or furnish a performance security
in accordance with ITB 37;
the Borrower may, if provided for in the BDS, declare the
Bidder disqualified to be awarded a contract by the Employer
for a period of time as stated in the BDS.
18. Period of
Validity of
Bids
18.1 Bids shall remain valid, at a minimum, for the period specified
in the BDS after the deadline date for bid submission prescribed
by the Purchaser, pursuant to ITB Clause 21. A bid valid for a
shorter period shall be rejected by the Purchaser as nonresponsive. For the convenience of Bidders, the BDS spells out
the minimal original expiration dates for the validity of the bid
and, if applicable pursuant to ITB Clause 17.1, for securing the
bid. However, Bidders are responsible for adjusting the dates in
the BDS in accordance with any extensions to the deadline date
of bid submission pursuant to ITB Clause 21.2.
18.2 In exceptional circumstances, prior to expiry of the bid validity
period, the Purchaser may request that the Bidders extend the
period of validity for a specified additional period. The request
and the responses to the request shall be made in writing. A
Bidder may refuse the request without risking execution of the
Bid-Securing Declaration or forfeiting the Bid Security, but in
this case the bid will be out of the competition for the award.
30
Section I. Instructions to Bidders
Except as provided in ITB Clause 18.3, a Bidder agreeing to the
request will not be required or permitted to modify its bid, but
will be required to ensure that the bid remains secured for a
correspondingly longer period, pursuant to ITB Clause 17.2.
18.3 In the case of fixed price contracts, if the award is delayed by a
period exceeding fifty-six (56) days beyond the expiry of the
initial bid validity, the contract price will be adjusted as
specified in the request for extension. Bid evaluation will be
based on the bid prices without taking into consideration the
above correction.
19. Format and
Signing of Bid
19.1 The Bidder shall prepare an original and the number of
copies/sets of the bid specified in the BDS, clearly marking
each one as “ORIGINAL BID,” “COPY NO. 1,” “COPY
NO. 2,” etc., as appropriate. In the event of any discrepancy
between them, the original shall govern.
19.2 The original and all copies of the bid, each consisting of the
documents listed in ITB Clause 13.1, shall be typed or written in
indelible ink and shall be signed by a person or persons duly
authorized to sign on behalf of the Bidder. The authorization
must be in writing and included in the bid pursuant to ITB
Clause 13.1 (d). The name and position held by each person
signing the authorization must be typed or printed below the
signature. All pages of the bid, except for unamended printed
literature, shall be initialed by the person or persons signing the
bid.
19.3 The bid shall contain no interlineations, erasures, or overwriting,
except to correct errors made by the Bidder, in which case such
corrections shall be initialed by the person or persons signing the
bid.
19.4 The Bidder shall furnish in the Bid Submission Form (a sample
of which is provided in the Sample Forms Section of the Bidding
Documents) information regarding commissions or gratuities, if
any, paid or to be paid to agents relating to this procurement and
to the execution of the Contract should the Bidder be successful.
Section I. Instructions to Bidders
31
D. SUBMISSION OF BIDS
20. Sealing and
Marking of
Bids
20.1 The Bidder shall seal the original and each copy of the bid in
separate envelopes, duly marking the envelopes as “ORIGINAL
BID” and “COPY NO. [number].” The envelopes shall then be
sealed in an outer envelope.
20.2 The inner and outer envelopes shall
(a)
be addressed to the Purchaser at the address given in the
BDS, and
(b)
bear the loan/Project name indicated in the BDS for ITB
Clause 2.1, the Invitation for Bids title and number, and the
Contract name(s), as indicated in the BDS for ITB
Clause 1.2, and the statement “DO NOT OPEN BEFORE
[ time and date],” to be completed with the time and date
specified in the BDS for ITB Clause 24.1.
20.3 The inner envelopes shall also indicate the name and address of
the Bidder so that the bid can be returned unopened in case it is
declared “late.”
20.4 If the outer envelope is not sealed and marked as required by
ITB Clause 20.2 above, the Purchaser will assume no
responsibility for the bid’s misplacement or premature opening.
If the outer envelope discloses the Bidder’s identity, the
Purchaser will not guarantee the anonymity of the bid
submission, but this disclosure will not constitute grounds for
bid rejection.
21. Deadline for
Submission of
Bids
21.1 Bids must be received by the Purchaser at the address specified
in the BDS for ITB Clause 20.2 no later than the time and date
stated in the BDS.
21.2 The Purchaser may, at its discretion, extend this deadline for
submission of bids by amending the Bidding Documents in
accordance with ITB Clause 11.3, in which case all rights and
obligations of the Purchaser and Bidders will thereafter be
subject to the deadline as extended.
22. Late Bids
22.1 Any bid received by the Purchaser after the bid submission
deadline prescribed by the Purchaser in the BDS for ITB Clause
21, will be rejected and returned unopened to the Bidder.
23. Withdrawal,
Substitution,
and
23.1 The Bidder may withdraw, substitute, or modify its bid after
submission, provided that written notice of the withdrawal,
substitution, or modification is received by the Purchaser prior to
32
Section I. Instructions to Bidders
Modification of
Bids
the deadline prescribed for bid submission. All notices must be
duly signed by an authorized representative and shall include a
copy of the authorization (the power of attorney) in accordance
with ITB Sub-Clause 19.2.
23.2 All notices of withdrawal, substitution, or modification shall
(a)
be addressed to the Purchaser at the address named in the
BDS for ITB Clause 20.2 (a), and
(b)
bear the Contract name, the IFB Title and IFB Number,
and the words “BID WITHDRAWAL NOTICE”, BID
SUBSTITUTION NOTICE”, or “BID MODIFICATION NOTICE”.
23.3 A notice may also be sent by electronic means such as fax or email, but in this case must include a scan of the mailing receipt
showing both the sender's and receiver's addresses for the signed
hardcopy of the notice, and a scan of the power of attorney.
23.4 Bids requested to be withdrawn in accordance with ITB 23.1
shall be returned unopened to the Bidders. Bid withdrawal
notices received after the bid submission deadline will be
ignored, and the submitted bid will be deemed to be a validly
submitted bid.
23.5 The substitution or modification of the bid shall be prepared,
sealed, marked, and dispatched as follows:
(a)
The Bidders shall provide an original and the number of
copies specified in the BDS for ITB Clause 19.1 of any
substitution or modification to its bid, clearly identified as
such, in two inner envelopes duly marked “BID
SUBSTITUTION -- ORIGINAL” or “BID MODIFICATION -ORIGINAL” and “BID SUBSTITUTION -- COPIES” or “BID
MODIFICATION -- COPIES.” The inner envelopes shall be
sealed in an outer envelope, which shall be duly marked
“BID SUBSTITUTION” or “BID MODIFICATION”.
(b)
Other provisions concerning the marking and dispatch of a
bid substitution or modification shall be in accordance with
ITB Clauses 20.2, 20.3, and 20.4.
23.6 No bid may be withdrawn, substituted, or modified in the
interval between the bid submission deadline and the expiration
of the bid validity period specified by the Bidder in the Bid
Submission Form, or any extension thereof agreed to by the
Bidder. Withdrawal of a bid during this interval may result in the
execution of the Bid-Securing Declaration, if any, or forfeiture
Section I. Instructions to Bidders
33
of the Bid Security, if any, pursuant to ITB Clause 17.6.
E. BID OPENING AND EVALUATION
24. Opening of
Bids by
Purchaser
24.1 The Purchaser will open all bids, including withdrawals,
substitutions, and modifications, in public, in the presence of
Bidders’ representatives who choose to attend, at the time, on
the date and at the place specified in the BDS. Bidders’
representatives shall sign a register as proof of their attendance.
24.2 First, envelopes marked “BID WITHDRAWAL NOTICE” shall be
opened and read out and the envelope with the corresponding
bid shall not be opened, but returned to the Bidder. No bid
withdrawal shall be permitted unless the corresponding
withdrawal notice contains a valid authorization to request the
withdrawal and is read out at bid opening. Next, envelopes
marked “BID SUBSTITUTION NOTICE” shall be opened and read
out and exchanged with the corresponding bid being substituted,
and the substituted bid shall not be opened, but returned to the
Bidder. No bid substitution shall be permitted unless the
corresponding substitution notice contains a valid authorization
to request the substitution and is read out at bid opening.
Envelopes marked “BID MODIFICATION NOTICE” shall be opened
and read out with the corresponding bid. No bid modification
shall be permitted unless the corresponding modification notice
contains a valid authorization to request the modification and is
read out at bid opening. Only bids that are opened and read out
at bid opening shall be considered further.
24.3 Bids shall be opened one at a time, reading out: the name of the
Bidder and whether there is a modification; the total bid price
including any unconditional discounts, and, if applicable, the
prices and unconditional discounts for Subsystems, lots, or
slices; the presence or absence of a Bid-Securing Declaration or
a Bid Security if one was required; any conditional discounts
offered for the award of more than one Subsystem, lot, or slice,
if the BDS for ITB Clause 28.1 permits such discounts to be
considered in the bid evaluation; and any other such details as
the Purchaser may consider appropriate.
24.4 Bids and modifications that are not opened and read out at bid
opening shall not be considered for further evaluation,
irrespective of the circumstances. These bids, including any bids
validly withdrawn in accordance with ITB Clause 24.2, will
34
Section I. Instructions to Bidders
promptly be returned, unopened, to their Bidders.
24.5 The Purchaser will prepare minutes of the bid opening, including
the information disclosed to those present in accordance with
ITB Clause 24.3. The minutes will promptly be distributed to all
Bidders that met the deadline for submitting bids.
25. Clarification of 25.1 During the bid evaluation, the Purchaser may, at its discretion,
ask the Bidder for a clarification of its bid. The request for
Bids
clarification and the response shall be in writing, and no change
in the price or substance of the bid shall be sought, offered, or
permitted.
26. Preliminary
Examination
of Bids
26.1 The Purchaser will examine the bids to determine whether they
are complete, whether any computational errors have been made,
whether required sureties have been furnished, whether the
documents have been properly signed, and whether the bids are
generally in order. In the case where a prequalification process
has been undertaken for the Contract(s) for which these Bidding
Documents have been issued, the Purchaser will ensure that each
bid is from a prequalified Bidder, and in the case of a Joint
Venture, that partners and structure of the Joint Venture are
unchanged from those in the prequalification.
26.2 Arithmetical errors will be rectified on the following basis. 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 added or subtracted subtotals and totals, the unit or
subtotal price shall prevail and the total price shall be corrected,
unless in the opinion of the Purchaser there is an obvious
misplacement of the decimal point in the unit or subtotal prices,
in which case the line item total as quoted shall govern and the
unit price or sub-total shall be corrected. If there is a discrepancy
between words and figures, the amount in words will prevail,
unless the discrepancy is the result of a typo/error for which the
correction is self-evident to the Purchaser. If the Bidder with the
Lowest Evaluated Bid does not accept the correction of errors,
the bid shall be rejected.
26.3 The Purchaser may waive any minor informality, nonconformity,
or irregularity in a bid that does not constitute a material
deviation, provided such waiver does not prejudice or affect the
relative ranking of any Bidder.
26.4 Prior to the detailed evaluation, the Purchaser will determine
whether each bid is of acceptable quality, is complete, and is
substantially responsive to the Bidding Documents. For purposes
Section I. Instructions to Bidders
35
of this determination, a substantially responsive bid is one that
conforms to all the terms, conditions, and specifications of the
Bidding Documents without material deviations, exceptions,
objections, conditionalities, or reservations. A material
deviation, exception, objection, conditionality, or reservation is
one: (i) that limits in any substantial way the scope, quality, or
performance of the Information System; or (ii) that limits, in any
substantial way that is inconsistent with the Bidding Documents,
the Purchaser’s rights or the successful Bidder’s obligations
under the Contract; or (iii) the acceptance of which would
unfairly affect the competitive position of other Bidders who
have submitted substantially responsive bids.
26.5 If a bid is not substantially responsive, it will be rejected by the
Purchaser and may not subsequently be made responsive by the
Bidder by correction of the nonconformity. The Purchaser’s
determination of bid responsiveness will be based on the
contents of the bid itself.
27. Conversion to
Single
Currency
27.1 For evaluation and comparison purposes, the Purchaser shall
convert all bid prices expressed in various currencies and
amounts into a single currency specified in the BDS, using the
selling exchange rate established by the source and on the date
also specified in the BDS.
28. Evaluation
and
Comparison of
Bids
28.1 The Purchaser will evaluate and compare the bids that have been
determined to be substantially responsive, pursuant to ITB
Clause 26. The evaluation will be performed assuming either
that:
(a)
the Contract will be awarded to the lowest evaluated
Bidder for the entire Information System; or
(b)
if specified in the BDS, Contracts will be awarded to the
Bidders for each individual Subsystem, lot, or slice defined
in the Technical Requirements whose bids result in the
lowest combined evaluated price for the entire System.
In the latter case, discounts that are conditional on the award of
more than one Subsystem, lot, or slice may be offered in bids.
However, such discounts will only be considered in the price
evaluation if so confirmed in the BDS.
28.2 To be considered for Contract award, Bidders must have
submitted bids
(a)
for which detailed bid evaluation using the same standards
36
Section I. Instructions to Bidders
for compliance determination as listed in ITB Clauses 26.3
and 26.4 confirms that the bids are commercially and
technically responsive, and include the hardware,
Software, related equipment, products, Materials, and other
Goods and Services components of the Information System
in, substantially, the full required quantities for the entire
Information System or, if allowed in the BDS for ITB
Clause 28.1, the individual Subsystem, lot or slice bid on;
and
(b)
that offer Information Technologies that are proven to
perform up to the standards promised in the bid by having
successfully passed the performance, benchmark, and/or
functionality tests the Purchaser may require, pursuant to
ITB Clause 31.2.
28.3 The Purchaser’s evaluation of a bid will be made on the basis of
prices quoted in accordance with ITB Clause 14 (Bid Prices).
28.4 If indicated by the BDS, the Purchaser’s evaluation of
responsive bids will take into account technical factors, in
addition to cost factors. An Evaluated Bid Score (B) will be
calculated for each responsive bid using the following formula,
which permits a comprehensive assessment of the bid price and
the technical merits of each bid:
B
Clow
T
1  X 
X 
C
Thigh
where
C
= Evaluated Bid Price
C low = the lowest of all Evaluated Bid Prices among
responsive bids
T
= the total Technical Score awarded to the bid
Thigh = the Technical Score achieved by the bid that was
scored highest among all responsive bids
X
= weight for the Price as specified in the BDS
The bid with the highest Evaluated Bid Score (B) among
responsive bids shall be termed the Lowest Evaluated Bid and is
eligible for Contract award, provided the Bidder was
prequalified and/or it was found to be qualified to perform the
Contract in accordance with ITB Clause 31 (Postqualification).
Section I. Instructions to Bidders
37
28.5 If, in addition to the cost factors, the Purchaser has chosen to
give weight to important technical factors (i.e., the price weight,
X, is less than 1 in the evaluation), that cannot be reduced to
life-cycle costs or pass/fail criteria, the Total Technical Points
assigned to each bid in the Evaluated Bid Formula will be
determined by adding and weighting the scores assigned by an
evaluation committee to technical features of the bid in
accordance with the criteria set forth below.
(a)
The technical features to be evaluated are generally defined
below and specifically identified in the BDS:
(i)
Performance, capacity, or functionality features that
either exceed levels specified as mandatory in the
Technical Requirements; and/or influence the lifecycle cost and effectiveness of the Information
System.
(ii)
Usability features, such as ease of use, ease of
administration, or ease of expansion, which
influence the life-cycle cost and effectiveness of the
Information System.
(iii) The quality of the Bidder’s Preliminary Project Plan
as evidenced by the thoroughness, reasonableness,
and responsiveness of: (a) the task and resource
schedules, both general and specific, and (b) the
proposed arrangements for management and
coordination, training, quality assurance, technical
support, logistics, problem resolution, and transfer of
knowledge, and other such activities as specified by
the Purchaser in Section VI (Technical
Requirements) or proposed by the Bidder based on
the Bidder’s experience.
(b)
Feature scores will be grouped into a small number of
evaluation categories, generally defined below and
specifically identified in the BDS, namely:
(i)
The technical features that reflect how well the
Information System meets the Purchaser’s Business
Requirements (including quality assurance and riskcontainment measures associated with the
implementation of the Information System).
(ii)
The technical features that reflect how well the
Information System meets the System’s Functional
38
Section I. Instructions to Bidders
Performance Standards.
(iii) The technical features that reflect how well the
Information System meets the General Technical
Requirements
for
hardware,
network
and
communications, Software, and Services.
(c)
As specified in the BDS, each category will be given a
weight and within each category each feature may also be
given a weight.
(d)
During the evaluation process, the evaluation committee
will assign each desirable/preferred feature a whole
number score from 0 to 4, where 0 means that the feature
is absent, and 1 to 4 either represent predefined values for
desirable features amenable to an objective way of rating
(as is the case for, e.g., extra memory, or extra mass
storage capacity, etc., if these extras would be conducive
for the utility of the system), or if the feature represents a
desirable functionality (e.g., of a software package) or a
quality improving the prospects for a successful
implementation (such as the strengths of the proposed
project staff, the methodology, the elaboration of the
project plan, etc., in the bid), the scoring will be 1 for the
feature being present but showing deficiencies; 2 for
meeting the requirements; 3 for marginally exceeding the
requirements; and 4 for significantly exceeding the
requirements.
(e)
The score for each feature (i) within a category (j) will be
combined with the scores of features in the same category
as a weighted sum to form the Category Technical Score
using the following formula:
k
S j   t ji  w ji
i 1
where:
tji
= the technical score for feature “i” in category “j”
wji
= the weight of feature “i” in category “j”
k
= the number of scored features in category “j”
k
and
w
i 1
(f)
ji
1
The Category Technical Scores will be combined in a
Section I. Instructions to Bidders
39
weighted sum to form the total Technical Bid Score using
the following formula:
n
T   S j Wj
j 1
where:
Sj
= the Category Technical Score of category “j”
Wj
= the weight of category “j” as specified in the BDS
n
= the number of categories
n
and
W
j 1
j
1
28.6 The Evaluated Bid Price (C) for each responsive bid will be
determined as the sum of the Adjusted Supply and Installation
Costs (P) plus the Recurrent Costs (R);
where the Adjusted Supply and Installation Costs (P) are
determined as:
(a)
The price of the hardware, Software, related equipment,
products, Materials and other Goods offered from within or
from outside the Purchaser’s Country, in accordance with
ITB 14.4; plus
(b)
The total price for all software development,
transportation, insurance, installation, customization,
integration, Commissioning, testing, training, technical
support, repair, and other Services, in accordance with ITB
14.5;
(c)
with adjustments for:
(i)
Deviations proposed to the Implementation Schedule
in the Technical Requirements resulting in delayed
completion of the entire Information System, if
permitted in the BDS and provided they do not
exceed the maximum permissible delay period
specified in the BDS. For evaluation purposes, a pro
rata increase of the total Supply and Installation
Costs will be added using the percentage(s) specified
in the BDS for each week of delay. Bids offering
deliveries beyond the maximum permissible delay
specified may be rejected.
40
Section I. Instructions to Bidders
(ii)
Deviations taken to the Contract payment schedule
specified in the SCC. If deviations are permitted in
the BDS, for evaluation purposes the total Supply
and Installation Costs will be increased pro rata by
the amount of interest that could otherwise be earned
on the amount of any payments that would fall due
under the proposed schedule earlier than the schedule
stipulated in the SCC, at the interest rate specified in
the BDS.
(iii) Goods and Services that are required for the
Information System but have been left out or are
necessary to correct minor deviations of the bid will
be added to the total Supply and Installation Costs
using costs taken from the highest prices from other
responsive bids for the same Goods and Services, or
in the absence of such information, the cost will be
estimated at prevailing list prices. If the missing
Goods and Services are a scored technical feature, the
relevant score will be set at zero.
(iv) Corrections to errors in arithmetic, in accordance
with ITB Clause 26.2.
(v)
(d)
Any discounts offered for the award of more than one
Subsystem, lot, or slice, if the BDS for ITB Clause
28.1 permits the consideration of discounts in the
price evaluation.
The Recurrent Costs (R) are reduced to net present value
and determined using the following formula:
R
NM R
x

x
x  1 1  I 
where
N = number of years of the warranty Period, defined in
SCC Clause 29.4
M = number of years of the Post- warranty Services
Period, as defined in SCC Clause 1.1.(e) (xii)
x
= an index number 1, 2, 3, ... N + M representing
each year of the combined warranty Service and
Post- warranty Service Periods.
Rx = total Recurrent Costs for year “x,” as recorded in
Section I. Instructions to Bidders
41
the Recurrent Cost Sub-Table.
I
= discount rate to be used for the Net Present Value
calculation, as specified in the BDS.
29. Domestic
Preference
29.1 No margin of domestic preference will apply.
30. Contacting the
Purchaser
30.1 From the time of bid opening to the time of Contract award, if
any Bidder wishes to contact the Purchaser on any matter related
to the bid, it should do so in writing.
30.2 If a Bidder tries to directly influence the Purchaser or otherwise
interfere in the bid evaluation process and the Contract award
decision, its bid may be rejected.
F. POSTQUALIFICATION AND AWARD OF CONTRACT
31. Postqualification
31.1 The Purchaser will determine at its own cost and to its
satisfaction whether the Bidder (including Joint Venture
Partners, and any Subcontractors for which the BDS for ITB
Clause 6.1 (a) permits that their qualifications count towards the
required Bidder qualifications) that is selected as having
submitted the Lowest Evaluated Bid is qualified to perform the
Contract satisfactorily, in accordance with ITB Clause 6. If a
prequalification process was undertaken for the Contract(s) for
which these Bidding Documents were issued, the Purchaser will
determine in the manner described above that no material
changes have occurred after the prequalification that negatively
affect the ability of the Bidder that has submitted the Lowest
Evaluated Bid to perform the Contract.
31.2 Pursuant to ITB Clauses 6 and 16, and as additionally may be
specified in the BDS, the determination will evaluate the
Bidder’s financial, technical, design, integration, customization,
production, management, and support capabilities and will be
based on an examination of the documentary evidence of the
Bidder’s qualifications, as well as other information the
Purchaser deems necessary and appropriate. This determination
may include visits or interviews with the Bidder’s clients
referenced in its bid, site inspections, and any other measures. If
so specified in the BDS, at the time of postqualification the
Purchaser may also carry out tests to determine that the
performance or functionality of the Information System offered
meets those stated in the Technical Requirements.
42
Section I. Instructions to Bidders
31.3 An affirmative postqualification determination will be a
prerequisite for award of the Contract to the Lowest Evaluated
Bidder. A negative determination will result in rejection of the
Bidder’s bid, in which event the Purchaser will proceed to the
next lowest evaluated Bidder to make a similar determination of
that Bidder’s capabilities to perform satisfactorily.
32. Award
Criteria
32.1 Subject to ITB Clause 34, the Purchaser will award the Contract
to the Bidder whose bid has been determined to be substantially
responsive and the Lowest Evaluated Bid, provided further that
the Bidder has been determined to be qualified to perform the
Contract satisfactorily, pursuant to ITB Clause 31.
33. Purchaser’s
Right to Vary
Quantities at
Time of Award
33.1 The Purchaser reserves the right at the time of Contract award to
increase or decrease, by the percentage(s) indicated in the BDS,
any of the following:
(a)
the quantity of substantially identical Subsystems; or
(b)
the quantity of individual hardware, Software, related
equipment, Materials, products, and other Goods
components of the Information System; or
(c)
the quantity of Installation or other Services to be
performed,
from that originally specified in the Technical Requirements (as
amended by any Addenda issued pursuant to ITB Clause 11),
without any change in unit prices or other terms and conditions.
34. Purchaser’s
Right to
Accept Any
Bid and to
Reject Any or
All Bids
34.1 The Purchaser 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 thereby incurring any liability to the
Bidders.
35. Notification of
Award
35.1 Prior to the expiration of the period of bid validity, the Purchaser
shall notify the successful Bidder, in writing, that its bid has
been accepted.
35.2 Until a formal Contract is prepared and executed, the
notification of award shall constitute a binding Contract.
35.3 The Purchaser shall promptly publish in UNDB online and in
dgMarket the results, identifying the bid and lot numbers and the
following information: (i) name of each Bidder who submitted a
bid; (ii) bid prices as read out at bid opening; (iii) name,
Section I. Instructions to Bidders
43
evaluated price and, if the bidding conditions included scoring
for technical quality, the technical score of each bid that was
evaluated; (iv) name of Bidders whose bids were rejected and
the reasons for their rejection; and (v) name of the winning
Bidder, the price it offered, as well as the duration and summary
scope of the contract awarded. After publication of the award,
unsuccessful Bidders may make a request in writing to the
Purchaser for a debriefing seeking explanations on the grounds
on which their bids were not selected. The Purchaser shall
promptly respond in writing to any unsuccessful Bidder who,
after publication of contract award, requests a debriefing.
35.4 Upon the successful Bidder furnishing the signed Contract
Agreement and the Performance Security pursuant to ITB Clause
37, the Purchaser will promptly notify each unsuccessful Bidder,
and will discharge all remaining Bid Securities, if any, as
provided in ITB Clause 17.5 (c) and (d).
36. Signing of
Contract
36.1 At the same time as the Purchaser notifies the successful Bidder
that its bid has been accepted, the Purchaser will send the Bidder
the Contract Agreement provided in the Bidding Documents,
incorporating all agreements between the parties.
36.2 As soon as practically possible, but no more than twenty-eight
(28) days following receipt of the Contract Agreement, the
successful Bidder shall sign and date it, and return it to the
Purchaser.
37. Performance
Security
37.1 As soon as practically possible, but no more than twenty-eight
(28) days following receipt of notification of award from the
Purchaser, the successful Bidder shall furnish the Performance
Security in accordance with the GCC, using the Performance
Security form provided in the Bidding Documents or another
form acceptable to the Purchaser.
37.2 Failure of the successful Bidder to comply with the requirements
of ITB Clause 36 or ITB Clause 37.1 shall constitute sufficient
grounds for the annulment of the award and, if and as applicable,
execution of the Bid-Securing Declaration or forfeiture of the
Bid Security, in which event the Purchaser may make the award
to the next lowest evaluated bid submitted by a qualified Bidder
or call for new bids.
38. Adjudicator
38.1 Unless otherwise stated in the BDS, the Purchaser proposes that
the person named in the BDS be appointed as Adjudicator under
the Contract to assume the role of informal Contract dispute
mediator, as described in GCC Clause 6. In this case, a résumé
44
Section I. Instructions to Bidders
of the named person is attached to the BDS. The proposed
hourly fee for the Adjudicator is specified in the BDS. The
expenses that would be considered reimbursable to the
Adjudicator are also specified in the BDS. If a Bidder does not
accept the Adjudicator proposed by the Purchaser, it should state
its non-acceptance in its Bid Submission Form and make a
counterproposal of an Adjudicator and an hourly fee, attaching a
résumé of the alternative. If the successful Bidder and the
Adjudicator nominated in the BDS happen to be from the same
country, and this is not the country of the Purchaser too, the
Purchaser reserves the right to cancel the Adjudicator nominated
in the BDS and propose a new one. If by the day the Contract is
signed, the Purchaser and the successful Bidder have not agreed
on the appointment of the Adjudicator, the Adjudicator shall be
appointed, at the request of either party, by the Appointing
Authority specified in the SCC clause relating to GCC Clause
6.1.4, or if no Appointing Authority is specified there, the
Contract will be implemented without an Adjudicator.
45
SECTION II. BID DATA SHEET (BDS)
46
Section II. Bid Data Sheet
Bid Data Sheet
The following specific information relating to the System to be procured and the procurement
procedures that will be used shall complement, supplement, or amend the provisions in the
Instructions to Bidders (ITB). Whenever there is a conflict, the provisions in the Bid Data
Sheet (BDS) shall prevail over those in the ITB.
A. GENERAL
ITB 1.1
Name of Purchaser: Bangladesh Bank, represented by Executive
Director (ICT)
Name of authorized Purchasing Agent: none
Description of the System for which bids are invited: Supply,
Installation, Testing, Commissioning, Implementation and
related services of Network Devices and Software for
Information Systems.
ITB 1.2
Title of IFB: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network Devices
and Software for Information Systems
Number of IFB: BB(G)IT-5
Name of resulting Contract(s): Supply, Installation, Testing,
Commissioning, Implementation and related services of
Network Devices and Software for Information Systems
ITB 1.4
Alternative e-Tendering procedures are not available in this
procurement.
ITB 2.1
Name of the Borrower: The People’s Republic of Bangladesh
Credit number: 56640
Credit amount: SDR 213.4 Million
Name of Project: Financial Sector Support Project
ITB 6.1 (a)
Qualification requirements for Bidders are:
(a) The Bidder and the agent/subcontractor must have
been in business for the last five (05) years;
(b) The Bidder must have completed minimum one
successful contract involving supply, installation,
testing, commissioning, integration and related
technical support services of Network Devices for
Information Systems involving data center and disaster
recovery sites in last five (05) years;
Section II. Bid Data Sheet
47
(c) The Bidder must demonstrate present minimum
average annual turnover of US$ Seven (07) Million
equivalent calculated as total certified payments
received for contracts in progress or completed within
the last five (05) years;
(d) The Bidder must demonstrate minimum US$ Five (05)
Million equivalent present liquid asset and/or line of
credit, net of current commitments;
(e) The agent and the subcontractor of the bidder must
have at least three years proven experience in
providing warranty support services. The local agent
and the subcontractor’s relationship with the
Principal/ manufacturer shall be at least two (02)
years.
ITB 6.1 (b)
Manufacturer's Authorizations for Information Technologies - except
for those technologies which the Bidder itself manufactures are required for the following types/categories:
All active (i.e. powered) equipment such as Routers,
Switches, Firewalls, Content Filers, Load Balancers etc.
and all Software.
ITB 6.1 (c)
If the Bidder proposes to use Subcontractors for the provision of
certain key services, written agreements by the proposed
firms to provide these services in case of contract(s) resulting
from this bidding are required for the following
types/categories of services: all.
The Subcontractor must have adequate knowledge, experience and
resources to perform the assigned task/job successfully.
B. THE BIDDING DOCUMENTS
ITB 10.1
Purchaser’s / duly authorized Purchasing Agent’s address:
Executive Director (ICT)
Bangladesh Bank, 6th Floor, Main Building, Head Office,
Motijheel, Dhaka.
Telephone: +880-2-9566211, Fax: +880-2-9566212, Email:
kazi.nasir@bb.org.bd
Contact person or officer to whom bidder communications should be
addressed:
Systems Manager
IT
Operation
and
Communication
Department,
Bangladesh Bank, 29th Floor, Head Office, Motijheel,
48
ITB 10.2
Section II. Bid Data Sheet
Dhaka.
Telephone: +880-2-9530234, Fax: +880-2-9530481, Email:
sm.itocd@bb.org.bd; jalal.uddin@bb.org.bd
Dates, times, and places for the pre-bid meeting: 22 December 2015
at 11:00AM Bangladesh Standard Time at Jahangir Alam
Conference Hall, Fourth Floor, Main Building,
Bangladesh Bank, Head Office, Motijheel, Dhaka,
Bangladesh.
C. PREPARATION OF BIDS
ITB 12.1
The language of the bid and of all correspondence and documents
related to it is: English.
ITB 13.1 (e) (i)
The Bidder must submit the following evidences in support of their
eligibility:
A. Certificate of Incorporation and Trade License;
B. Work Order or Work Order Completion Certificate
mentioning contract value, time, work summary,
purchaser’s information etc.;
C. Audited Balance Sheet and Income Statement;
D. Bank Certificate mentioning undrawn balance in case of
credit line; and
E. Details of work experience
ITB 14.1
Recurrent cost items are not required.
ITB 14.4
The Incoterms edition is “Incoterms 2010 — ICC Official Rules
for the Interpretation of Trade Terms”.
ITB 14.4 (a)
For foreign goods priced on a CIP (named place of destination)
basis:
(i) The contract of carriage shall include the cost of
unloading the goods at destination, as well as payment
by the Supplier of the cost of custom formalities, duties,
taxes or other charges payable on the foreign Goods for
their transit through any country other than the
Purchaser's country.
(ii) The named place of destination shall be the following
Project Sites:
Sl
1
2
3
Site Code
R1.1
R1.2
R2
Project Site
Head Office, Motijheel, Dhaka
BBTA, Mirpur, Dhaka
Rajshahi Office
Section II. Bid Data Sheet
ITB 14.5
ITB 14.7
49
These costs shall be identified separately and these costs should
also include the cost of storing and guarding the equipment
at the Project Sites.
Related local costs mentioned in the sub-clause shall include
clearing, forwarding and other charges at the port of
destination.
Prices quoted by the Bidder shall be fixed.
ITB 15.1 (b)
The currency to be used for quoting prices of the Goods and
Services components of the System offered locally (i.e., from
within the Purchaser’s Country), as well as local currency
expenditures for local technical support, training,
maintenance, transportation, insurance, and other local
services incidental to delivery, installation and operation of
the System, is: Bangladesh Taka or in a freely convertible
currency.
ITB 16.2 (c)
In addition to the topics described in ITB Clause 16.2 (c), the
Preliminary Project Plan must address the following topics:
(a)
(b)
(c)
(d)
(e)
Project Organization and Management Plan;
Delivery and Installation Plan;
Knowledge Transfer Plan;
Training Plan;
Pre-commissioning and Operational Acceptance Testing
Plan;
(f) Warranty Service Plan;
(g) Detailed Site Survey Report;
(h) Task, Time and Resources schedule.
Further details regarding the required contents of each of the
above chapters are contained in the Technical
Requirements, Section VI.
ITB 16.3
ITB 17.1
In the interest of effective integration, cost-effective technical
support, and reduced re-training and staffing costs, Bidders
are required to offer specific brand names and models for the
following limited number of specific items: none.
Bids need to be secured by a Bid Security.
The amount of Bid Security required is: Bangladesh Taka Five
Million (BDT 5,000,000/=) or equivalent amount in a freely
convertible currency.
Any bid accompanied by a bid security of any smaller amount
specified above shall be rejected as non-responsive.
ITB 18.1
The bid validity period shall be One Hundred Nineteen (119) days
after the deadline for bid submission, as specified below in
50
Section II. Bid Data Sheet
reference to ITB Clause 21. Accordingly, each bid shall be
valid through Tuesday 17 May 2016.
Accordingly, a bid with a Bid Security that expires before Tuesday
14 June 2016 shall be rejected as non-responsive.
ITB 19.1
Required number of bid copies, besides the original: two (2) copies
and one (1) electronic copy in portable document format
(pdf) in Compact Disc.
D. SUBMISSION OF BIDS
ITB 20.2 (a)
ITB 21.1
The address for bid submission is:
Kazi Nasir Ahmed
Executive Director (ICT)
Jahangir Alam Conference Hall, Fourth Floor,
Bangladesh Bank, Main Building, Head Office, Motijheel,
Dhaka, Bangladesh,
Telephone: +880-2-9566211, Fax: +880-2-9566212, Email:
kazi.nasir@bb.org.bd.
Deadline for bid submission is: Tuesday 19 January 2016 at
02:00PM Bangladesh Standard Time.
E. BID OPENING AND EVALUATION
ITB 24.1
Time, date, and place for bid opening are: Tuesday 19 January 2016
at 02:10PM Bangladesh Standard Time at Jahangir Alam
Conference Hall, Fourth Floor, Main Building, Bangladesh
Bank, Head Office, Motijheel, Dhaka, Bangladesh.
ITB 27.1
The currency chosen for the purpose of converting to a common
currency is: Bangladesh Taka.
The source of exchange rate is: Sonali Bank, Dhaka and the rate
shall be the B.C. Selling exchange rate.
The date of exchange rate determination is: the date of Bid opening.
In case that no exchange rates are available on this date from
the source indicated above, the latest available exchange rates
from the same source prior to this date will be used.
ITB 28.1
This is a single lot package. The evaluation will be carried out on the
basis of total package and the contract will be awarded to the
lowest evaluated bidder for the entire package provided the
bidder fulfils the award criteria specified in ITB Clause 32.1
Section II. Bid Data Sheet
51
Bids for Subsystems, lots, or slices of the overall Information System
will not be accepted.
Discounts for the award of multiple Subsystems, lots, or slices will
not be considered in bid evaluation.
ITB 28.4
The bid evaluation will take into account technical factors in addition
to cost factors.
The weight of the Price (“X” multiplied by 100 in the Evaluated Bid
Score formula) = 0.80
ITB 28.5
(a),(b) The technical evaluation categories and the features to be
evaluated within each category are as follows:
1. Network Solution;
2. Technical Experience;
3. Network Device
(c),(e),(f) The evaluation weights for categories and technical features
within categories are:
Category
Network
Solution
Features
No single point of failure (High Availability)
Performance Consistency (Reliability)
Flexibility and scalability of Network
Management, Monitoring & error detection
Weight
50
30%
30%
20%
20%
Technical
Experience
20
Number of Certified professionals on offered
products
Number of deployment completion experience
using offered products or similar products
40%
60%
Network
Devices
30
Hardware Feature of Spine Switch
General Feature of Leaf Switch
Performances of other Switches
Scalability of Switches
Aggregation switch performance
Throughputs of Routers
Firewall performance
Features of Application Load Balancer
Functions of Bandwidth Manager
Functions of Content Filter
Total weight
10%
10%
10%
10%
10%
10%
10%
10%
10%
10%
100
Scores will be awarded only after the minimum requirement is met
and the relative technical scores will be based on the
qualities/performances/values of each technical criteria. If the
52
Section II. Bid Data Sheet
bidder provides highest or best products or services, the
maximum score will be given to the bidder and the remaining
bidder(s) will be given scores in proportion.
ITB 28.6 (c) (i)
The Purchaser will accept deviations in the schedule of installation
and commissioning specified in the Implementation Schedule.
The maximum advance period is nil and the maximum delay
period is twelve (12) weeks.
The percentage for adjustment of a bid offering to complete
installation and commissioning later than the specified date,
but earlier than the maximum delay, is one-half percent
(0.50%) of the bid price per week. Bids offering a delay of
more than 12 weeks shall be rejected.
ITB 28.6 (c) (ii)
The Purchaser will not accept deviations in the payment schedule in
the SCC.
F. POSTQUALIFICATION AND AWARD OF CONTRACT
ITB 31.2
As additional postqualification measures, Supply, Installation,
Testing, Commissioning, Implementation and related
services of Network Devices and Software for Information
Systems (or components/parts of it) offered by the Lowest
Evaluated Bidder may be subjected to the following tests and
performance benchmarks prior to Contract award:
The Purchaser will examine documentary evidence including visits
and interviews with the Bidder’s client referenced in its bid,
site inspection, witnessing performances and functionalities
of the installed systems and verification of other relevant
information that the purchaser deems necessary and
reasonable including load test, failover test, redundancy test,
reboot test.
ITB 33.1
Percentage for quantity increase or decrease: Twenty (20)
percentage of the total quantity of any item of the technical
requirements.
ITB 38.1
An adjudicator shall be agreed by the Purchaser and the Bidder
before the finalization of the contract.
The proposed hourly fee and the expenses that would be considered
reimbursable to the Adjudicator shall also be agreed by the
Purchaser and the Bidder before the finalization of the
contract.
53
SECTION III. ELIGIBLE COUNTRIES FOR THE PROVISION OF
GOODS, WORKS, AND SERVICES IN BANK-FINANCED
PROCUREMENT
54
Section III. Countries Eligible for Bank-Financed Procurement
Section III. Countries Eligible for Bank-Financed Procurement
55
Eligible Countries for the Provision of Goods, Works, and Services in
Bank-Financed Procurement
As of October 2015
1.
Eligible for this procurement are firms of, and goods manufactured in, all countries
except countries, if any, listed in the following restrictions.
2.
In accordance with paragraph 1.10 (a) of the Guidelines: Procurement of Goods,
Works and Non-consulting Services under IBRD Loans and IDA Credits and Grants by the
World Bank Borrowers, July 2014, firms of a Country or goods manufactured in a Country
may be excluded if
(i)
as a matter of law or official regulation, the Borrower’s Country prohibits
commercial relations with that Country, provided that the Bank is satisfied that
such exclusion does not preclude effective competition for the supply of the
goods or works required, or
(ii)
by an Act of Compliance with a Decision of the United Nations Security
Council taken under Chapter VII of the Charter of the United Nations, the
Borrower’s Country prohibits any import of goods from that Country or any
payments to persons or entities in that Country.
3.
For the information of borrowers and bidders, at the present time firms, goods and
services from the following countries are excluded from this bidding:
With reference to paragraph (i) above: Israel
With reference to paragraph (ii) above: None
57
SECTION IV. GENERAL CONDITIONS OF CONTRACT
Notes on the General Conditions of Contract (GCC)
The General Conditions of Contract (GCC) contained in this section are to be read in
conjunction with the Special Conditions of Contract (SCC) in Section V and the other
documents listed in the Contract Agreement. Together they form a complete document
expressing all the rights and obligations of the parties to the Contract.
The GCC must remain unaltered. Contract-specific information, deletions,
extensions, and modifications to the GCC shall be introduced only through the SCC.
58
Section IV. General Conditions of Contract
Table of Clauses
A. Contract and Interpretation ............................................................................................60
1.
2.
3.
4.
5.
6.
Definitions.................................................................................................................60
Contract Documents..................................................................................................68
Interpretation .............................................................................................................68
Notices ......................................................................................................................71
Governing Law .........................................................................................................72
Settlement of Disputes ..............................................................................................72
B. Subject Matter of Contract ..............................................................................................74
7.
8.
9.
10.
Scope of the System ..................................................................................................74
Time for Commencement and Operational Acceptance ...........................................75
Supplier’s Responsibilities .......................................................................................75
Purchaser’s Responsibilities .....................................................................................77
C. Payment..............................................................................................................................79
11.
12.
13.
14.
Contract Price............................................................................................................79
Terms of Payment .....................................................................................................79
Securities ...................................................................................................................80
Taxes and Duties .......................................................................................................81
D. Intellectual Property .........................................................................................................82
15. Copyright ..................................................................................................................82
16. Software License Agreements...................................................................................83
17. Confidential Information...........................................................................................85
E. Supply, Installation, Testing, Commissioning, and Acceptance of the System ...........87
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
Representatives .........................................................................................................87
Project Plan ...............................................................................................................89
Subcontracting ..........................................................................................................89
Design and Engineering ............................................................................................90
Procurement, Delivery, and Transport ......................................................................93
Product Upgrades ......................................................................................................96
Implementation, Installation, and Other Services .....................................................97
Inspections and Tests ................................................................................................97
Installation of the System ..........................................................................................98
Commissioning and Operational Acceptance ...........................................................99
F. Guarantees and Liabilities ..............................................................................................103
28.
29.
30.
31.
32.
Operational Acceptance Time Guarantee ...............................................................103
Defect Liability .......................................................................................................104
Functional Guarantees.............................................................................................107
Intellectual Property Rights warranty.....................................................................107
Intellectual Property Rights Indemnity ...................................................................108
Section IV. General Conditions of Contract
33.
59
Limitation of Liability .............................................................................................111
G. Risk Distribution .............................................................................................................111
34.
35.
36.
37.
38.
Transfer of Ownership ............................................................................................111
Care of the System ..................................................................................................111
Loss of or Damage to Property; Accident or Injury to Workers; Indemnification..113
Insurances................................................................................................................114
Force Majeure .........................................................................................................116
H. Change in Contract Elements ........................................................................................118
39.
40.
41.
42.
Changes to the System ............................................................................................118
Extension of Time for Achieving Operational Acceptance ....................................122
Termination .............................................................................................................123
Assignment .............................................................................................................132
60
Section IV. General Conditions of Contract
General Conditions of Contract
A. CONTRACT AND INTERPRETATION
1. Definitions
1.1
In this Contract, the following terms shall be interpreted as
indicated below.
(a)
contract elements
(i)
“Contract” means the Contract Agreement
entered into between the Purchaser and the
Supplier, together with the Contract Documents
referred to therein. The Contract Agreement and
the Contract Documents shall constitute the
Contract, and the term “the Contract” shall in all
such documents be construed accordingly.
(ii)
“Contract Documents” means the documents
specified in Article 1.1 (Contract Documents) of
the Contract Agreement (including any
amendments to these Documents).
(iii) “Contract Agreement” means the agreement
entered into between the Purchaser and the
Supplier using the form of Contract Agreement
contained in the Sample Forms Section of the
Bidding Documents and any modifications to
this form agreed to by the Purchaser and the
Supplier. The date of the Contract Agreement
shall be recorded in the signed form.
(iv) “GCC” means the General Conditions of
Contract.
(v)
“SCC” means the Special Conditions of
Contract.
(vi) “Technical Requirements” means the Technical
Requirements Section of the Bidding
Documents.
(vii) “Implementation
Schedule”
means
the
Implementation Schedule Sub-section of the
Technical Requirements.
viii) “Contract Price” means the price or prices
defined in Article 2 (Contract Price and Terms
Section IV. General Conditions of Contract
61
of Payment) of the Contract Agreement.
(ix) “Procurement Guidelines” refers to the edition
specified in the SCC of the World Bank
Guidelines: Procurement under IBRD Loans and
IDA Credits.
(x)
(b)
“Bidding Documents” refers to the collection of
documents issued by the Purchaser to instruct
and inform potential suppliers of the processes
for bidding, selection of the winning bid, and
Contract formation, as well as the contractual
conditions governing the relationship between
the Purchaser and the Supplier. The General and
Special Conditions of Contract, the Technical
Requirements, and all other documents included
in the Bidding Documents reflect the
Procurement Guidelines that the Purchaser is
obligated to follow during procurement and
administration of this Contract.
entities
(i)
“Purchaser” means the entity purchasing the
Information System, as specified in the SCC.
(ii)
“Project Manager” means the person named as
such in the SCC or otherwise appointed by the
Purchaser in the manner provided in GCC
Clause 18.1 (Project Manager) to perform the
duties delegated by the Purchaser.
(iii) “Supplier” means the firm or Joint Venture
whose bid to perform the Contract has been
accepted by the Purchaser and is named as such
in the Contract Agreement.
(iv) “Supplier’s Representative” means any person
nominated by the Supplier and named as such in
the Contract Agreement or otherwise approved
by the Purchaser in the manner provided in GCC
Clause 18.2 (Supplier’s Representative) to
perform the duties delegated by the Supplier.
(v)
“Subcontractor” means any firm to whom any of
the obligations of the Supplier, including
preparation of any design or supply of any
62
Section IV. General Conditions of Contract
Information Technologies or other Goods or
Services, is subcontracted directly or indirectly
by the Supplier.
(vi) “Adjudicator” means the person named in
Appendix 2 of the Contract Agreement,
appointed by agreement between the Purchaser
and the Supplier to make a decision on or to
settle any dispute between the Purchaser and the
Supplier referred to him or her by the parties,
pursuant to GCC Clause 6.1 (Adjudication).
(vii) “The World Bank” (also called “The Bank”)
means the International Bank for Reconstruction
and Development (IBRD) or the International
Development Association (IDA).
(c)
scope
(i)
“Information System,” also called “the System,”
means all the Information Technologies,
Materials, and other Goods to be supplied,
installed, integrated, and made operational
(exclusive of the Supplier’s Equipment),
together with the Services to be carried out by
the Supplier under the Contract.
(ii)
“Subsystem” means any subset of the System
identified as such in the Contract that may be
supplied, installed, tested, and commissioned
individually before Commissioning of the entire
System.
(iii)
“Information
Technologies”
means
all
information processing and communicationsrelated hardware, Software, supplies, and
consumable items that the Supplier is required
to supply and install under the Contract.
(iv)
“Goods” means all equipment, machinery,
furnishings, Materials, and other tangible items
that the Supplier is required to supply or supply
and install under the Contract, including,
without
limitation,
the
Information
Technologies and Materials, but excluding the
Supplier’s Equipment.
Section IV. General Conditions of Contract
63
(v)
“Services” means all technical, logistical,
management, and any other Services to be
provided by the Supplier under the Contract to
supply, install, customize, integrate, and make
operational the System. Such Services may
include, but are not restricted to, activity
management and quality assurance, design,
development, customization, documentation,
transportation,
insurance,
inspection,
expediting, site preparation, installation,
integration, training, data migration, Precommissioning, Commissioning, maintenance,
and technical support.
(vi)
“The Project Plan” means the document to be
developed by the Supplier and approved by the
Purchaser, pursuant to GCC Clause 19, based
on the requirements of the Contract and the
Preliminary Project Plan included in the
Supplier’s bid. The “Agreed and Finalized
Project Plan” is the version of the Project Plan
approved by the Purchaser, in accordance with
GCC Clause 19.2. Should the Project Plan
conflict with the Contract in any way, the
relevant provisions of the Contract, including
any amendments, shall prevail.
(vii) “Software” means that part of the System which
are instructions that cause information
processing Subsystems to perform in a specific
manner or execute specific operations.
(viii) “System Software” means Software that provides
the operating and management instructions for the
underlying hardware and other components, and is
identified as such in Appendix 4 of the Contract
Agreement and such other Software as the parties
may agree in writing to be Systems Software.
Such System Software includes, but is not
restricted to, micro-code embedded in hardware
(i.e.,
“firmware”),
operating
systems,
communications,
system
and
network
management, and utility software.
(ix)
“General-Purpose Software” means Software
that supports general-purpose office and
64
Section IV. General Conditions of Contract
software development activities and is
identified as such in Appendix 4 of the Contract
Agreement and such other Software as the
parties may agree in writing to be GeneralPurpose Software. Such General-Purpose
Software may include, but is not restricted to,
word processing, spreadsheet, generic database
management, and application development
software.
(x)
“Application Software” means Software
formulated to perform specific business or
technical functions and interface with the
business or technical users of the System and is
identified as such in Appendix 4 of the Contract
Agreement and such other Software as the
parties may agree in writing to be Application
Software.
(xi)
“Standard Software” means Software identified
as such in Appendix 4 of the Contract
Agreement and such other Software as the
parties may agree in writing to be Standard
Software.
(xii) “Custom Software” means Software identified as
such in Appendix 4 of the Contract Agreement
and such other Software as the parties may agree
in writing to be Custom Software.
(xiii) “Source Code” means the database structures,
dictionaries, definitions, program source files,
and any other symbolic representations
necessary for the compilation, execution, and
subsequent maintenance of the Software
(typically, but not exclusively, required for
Custom Software).
(xiv) “Materials” means all documentation in printed
or printable form and all instructional and
informational aides in any form (including
audio, video, and text) and on any medium,
provided to the Purchaser under the Contract.
(xv) “Standard Materials” means all Materials not
specified as Custom Materials.
Section IV. General Conditions of Contract
65
(xvi) “Custom Materials” means Materials developed
by the Supplier at the Purchaser’s expense under
the Contract and identified as such in Appendix 5
of the Contract Agreement and such other
Materials as the parties may agree in writing to be
Custom Materials. Custom Materials includes
Materials created from Standard Materials.
(xvii) “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.
(xviii) “Supplier’s Equipment” means all equipment,
tools, apparatus, or things of every kind
required in or for installation, completion and
maintenance of the System that are to be
provided by the Supplier, but excluding the
Information Technologies, or other items
forming part of the System.
(d)
activities
(i)
“Delivery” means the transfer of the Goods from
the Supplier to the Purchaser in accordance with
the current edition Incoterms specified in the
Contract.
(ii)
“Installation” means that the System or a
Subsystem as specified in the Contract is ready
for Commissioning as provided in GCC Clause
26 (Installation).
(iii) “Pre-commissioning” means the testing, checking,
and any other required activity that may be
66
Section IV. General Conditions of Contract
specified in the Technical Requirements that are to
be carried out by the Supplier in preparation for
Commissioning of the System as provided in GCC
Clause 26 (Installation).
(iv) “Commissioning” means operation of the
System or any Subsystem by the Supplier
following Installation, which operation is to be
carried out by the Supplier as provided in GCC
Clause 27.1 (Commissioning), for the purpose of
carrying out Operational Acceptance Test(s).
(v)
“Operational Acceptance Tests” means the tests
specified in the Technical Requirements and
Agreed and Finalized Project Plan to be carried
out to ascertain whether the System, or a
specified Subsystem, is able to attain the
functional and performance requirements
specified in the Technical Requirements and
Agreed and Finalized Project Plan, in
accordance with the provisions of GCC Clause
27.2 (Operational Acceptance Test).
(vi) “Operational Acceptance” means the acceptance
by the Purchaser of the System (or any
Subsystem(s) where the Contract provides for
acceptance of the System in parts), in accordance
with
GCC
Clause 27.3
(Operational
Acceptance).
(e)
place and time
(i)
“Purchaser’s Country” is the country named in
the SCC.
(ii)
“Supplier’s Country” is the country in which the
Supplier is legally organized, as named in the
Contract Agreement.
(iii)
“Project Site(s)” means the place(s) specified in
the SCC for the supply and installation of the
System.
(iv) “Eligible Country” means the countries and
territories eligible for participation in
procurements financed by the World Bank as
defined in the Procurement Guidelines. (Note:
Section IV. General Conditions of Contract
67
The World Bank maintains a list of countries
from which Bidders, Goods, and Services are not
eligible to participate in procurement financed
by the Bank. The list is regularly updated and
can be obtained from the Public Information
Center of the Bank or its web site on
procurement. A copy of the list is contained in
the Section of the Bidding Documents entitled
“Eligible Countries for the Provision of Goods,
Works, and Services in Bank-Financed
Procurement”).
(v)
“Day” means calendar day of the Gregorian
Calendar.
(vi) “Week” means seven (7) consecutive Days,
beginning the day of the week as is customary in
the Purchaser’s Country.
(vii) “Month” means calendar month of the Gregorian
Calendar.
(viii) “Year” means twelve (12) consecutive Months.
(ix) “Effective Date” means the date of fulfillment of
all conditions specified in Article 3 (Effective
Date for Determining Time for Achieving
Operational Acceptance) of the Contract
Agreement, for the purpose of determining the
Delivery,
Installation,
and
Operational
Acceptance dates for the System or
Subsystem(s).
(x)
“Contract Period” is the time period during
which this Contract governs the relations and
obligations of the Purchaser and Supplier in
relation to the System, as specified in the SCC.
(xi) “Defect Liability Period” (also referred to as the
“Warranty Period”) means the period of validity
of the warranties given by the Supplier
commencing at date of the Operational
Acceptance Certificate of the System or
Subsystem(s), during which the Supplier is
responsible for defects with respect to the
System (or the relevant Subsystem[s]) as
68
Section IV. General Conditions of Contract
provided in GCC Clause 29 (Defect Liability).
(xii) “The Post- warranty Services Period” means the
number of years defined in the SCC (if any),
following the expiration of the warranty Period
during which the Supplier may be obligated to
provide Software licenses, maintenance, and/or
technical support services for the System, either
under this Contract or under separate contract(s).
(xiii) “The Coverage Period” means the Days of the
Week and the hours of those Days during which
maintenance, operational, and/or technical
support services (if any) must be available.
2. Contract
Documents
2.1
Subject to Article 1.2 (Order of Precedence) of the Contract
Agreement, all documents forming part of the Contract (and
all parts of these documents) are intended to be correlative,
complementary, and mutually explanatory. The Contract
shall be read as a whole.
3. Interpretation
3.1
Governing Language
3.1.1 All Contract Documents and related correspondence
exchanged between Purchaser and Supplier shall be
written in the language specified in the SCC, and the
Contract shall be construed and interpreted in
accordance with that language.
3.1.2 If any of the Contract Documents or related
correspondence are prepared in a language other than
the governing language under GCC Clause 3.1.1
above, the translation of such documents into the
governing language shall prevail in matters of
interpretation. The originating party, with respect to
such documents shall bear the costs and risks of such
translation.
3.2
Singular and Plural
The singular shall include the plural and the plural the
singular, except where the context otherwise requires.
3.3
Headings
The headings and marginal notes in the GCC are included
for ease of reference and shall neither constitute a part of the
Section IV. General Conditions of Contract
69
Contract nor affect its interpretation.
3.4
Persons
Words importing persons or parties shall include firms,
corporations, and government entities.
3.5
Incoterms
Unless inconsistent with any provision of the Contract, the
meaning of any trade term and the rights and obligations of
parties thereunder shall be as prescribed by the current
Incoterms (“Incoterms 2000” or a more recent version if and
as published). Incoterms are the international rules for
interpreting trade terms published by the International
Chamber of Commerce, 38 Cours Albert 1er, 75008 Paris,
France.
3.6
Entire Agreement
The Contract constitutes the entire agreement between the
Purchaser and Supplier with respect to the subject matter of
Contract and supersedes all communications, negotiations,
and agreements (whether written or oral) of parties with
respect to the subject matter of the Contract made prior to
the date of Contract.
3.7
Amendment
No amendment or other variation of the Contract shall be
effective unless it is in writing, is dated, expressly refers to
the Contract, and is signed by a duly authorized
representative of each party to the Contract.
3.8
Independent Supplier
The Supplier shall be an independent contractor performing
the Contract. The Contract does not create any agency,
partnership, joint venture, or other joint relationship
between the parties to the Contract.
Subject to the provisions of the Contract, the Supplier shall
be solely responsible for the manner in which the Contract
is performed. All employees, representatives, or
Subcontractors engaged by the Supplier in connection with
the performance of the Contract shall be under the complete
control of the Supplier and shall not be deemed to be
employees of the Purchaser, and nothing contained in the
70
Section IV. General Conditions of Contract
Contract or in any subcontract awarded by the Supplier
shall be construed to create any contractual relationship
between any such employees, representatives, or
Subcontractors and the Purchaser.
3.9
Joint Venture
If the Supplier is a Joint Venture of two or more firms, all
such firms shall be jointly and severally bound to the
Purchaser for the fulfillment of the provisions of the
Contract and shall designate one of such firms to act as a
leader with authority to bind the Joint Venture. The
composition or constitution of the Joint Venture shall not be
altered without the prior consent of the Purchaser.
3.10 Nonwaiver
3.10.1 Subject to GCC Clause 3.10.2 below, no relaxation,
forbearance, delay, or indulgence by either party in
enforcing any of the terms and conditions of the
Contract or the granting of time by either party to
the other shall prejudice, affect, or restrict the rights
of that party under the Contract, nor shall any waiver
by either party of any breach of Contract operate as
waiver of any subsequent or continuing breach of
Contract.
3.10.2 Any waiver of a party’s rights, powers, or remedies
under the Contract must be in writing, must be dated
and signed by an authorized representative of the
party granting such waiver, and must specify the
right and the extent to which it is being waived.
3.11 Severability
If any provision or condition of the Contract is prohibited or
rendered invalid or unenforceable, such prohibition,
invalidity, or unenforceability shall not affect the validity or
enforceability of any other provisions and conditions of the
Contract.
3.12 Country of Origin
“Origin” means the place where the Information
Technologies, Materials, and other Goods for the System
were produced or from which the Services are supplied.
Goods are produced when, through manufacturing,
processing, Software development, or substantial and major
Section IV. General Conditions of Contract
71
assembly or integration of components, a commercially
recognized product results that is substantially different in
basic characteristics or in purpose or utility from its
components. The Origin of Goods and Services is distinct
from the nationality of the Supplier and may be different.
4. Notices
4.1
Unless otherwise stated in the Contract, all notices to be
given under the Contract shall be in writing and shall be
sent, pursuant to GCC Clause 4.3 below, by personal
delivery, airmail post, special courier, cable, telegraph,
telex, facsimile, electronic mail, or Electronic Data
Interchange (EDI), with the following provisions.
4.1.1 Any notice sent by cable, telegraph, telex, facsimile,
electronic mail, or EDI shall be confirmed within two
(2) days after dispatch by notice sent by airmail post
or special courier, except as otherwise specified in the
Contract.
4.1.2 Any notice sent by airmail post or special courier shall
be deemed (in the absence of evidence of earlier
receipt) to have been delivered ten (10) days after
dispatch. In proving the fact of dispatch, it shall be
sufficient to show that the envelope containing such
notice was properly addressed, stamped, and conveyed
to the postal authorities or courier service for
transmission by airmail or special courier.
4.1.3 Any notice delivered personally or sent by cable,
telegraph, telex, facsimile, electronic mail, or EDI
shall be deemed to have been delivered on the date of
its dispatch.
4.1.4 Either party may change its postal, cable, telex,
facsimile, electronic mail, or EDI addresses for receipt
of such notices by ten (10) days’ notice to the other
party in writing.
4.2
Notices shall be deemed to include any approvals, consents,
instructions, orders, certificates, information and other
communication to be given under the Contract.
4.3
Pursuant to GCC Clause 18, notices from/to the Purchaser
are normally given by, or addressed to, the Project Manager,
while notices from/to the Supplier are normally given by, or
addressed to, the Supplier's Representative, or in its absence
its deputy if any. If there is no appointed Project Manager or
72
Section IV. General Conditions of Contract
Supplier's Representative (or deputy), or if their related
authority is limited by the SCC for GCC Clauses 18.1 or
18.2.2, or for any other reason, the Purchaser or Supplier
may give and receive notices at their fallback addresses.
The address of the Project Manager and the fallback address
of the Purchaser are as specified in the SCC or as
subsequently established/amended. The address of the
Supplier's Representative and the fallback address of the
Supplier are as specified in Appendix 1 of the Contract
Agreement or as subsequently established/amended.
5. Governing Law
5.1
The Contract shall be governed by and interpreted in
accordance with the laws of the country specified in the
SCC.
6. Settlement of
Disputes
6.1
Adjudication
6.1.1 If any dispute of any kind whatsoever shall arise
between the Purchaser and the Supplier in connection
with or arising out of the Contract, including without
prejudice to the generality of the foregoing, any
question regarding its existence, validity, or
termination, or the operation of the System (whether
during the progress of implementation or after its
achieving Operational Acceptance and whether before
or after the termination, abandonment, or breach of
the Contract), the parties shall seek to resolve any
such dispute by mutual consultation. If the parties fail
to resolve such a dispute by mutual consultation
within fourteen (14) days after one party has notified
the other in writing of the dispute, then, if the Contract
Agreement in Appendix 2 includes and names an
Adjudicator, the dispute shall, within another fourteen
(14) days, be referred in writing by either party to the
Adjudicator, with a copy to the other party. If there is
no Adjudicator specified in the Contract Agreement,
the mutual consultation period stated above shall last
twenty-eight (28) days (instead of fourteen), upon
expiry of which either party may move to the
notification of arbitration pursuant to GCC Clause
6.2.1.
6.1.2 The Adjudicator shall give his or her decision in
writing to both parties within twenty-eight (28) days
of the dispute being referred to the Adjudicator. If the
Adjudicator has done so, and no notice of intention to
Section IV. General Conditions of Contract
73
commence arbitration has been given by either the
Purchaser or the Supplier within fifty-six (56) days of
such reference, the decision shall become final and
binding upon the Purchaser and the Supplier. Any
decision that has become final and binding shall be
implemented by the parties forthwith.
6.1.3 The Adjudicator shall be paid an hourly fee at the rate
specified in the Contract Agreement plus reasonable
expenditures incurred in the execution of duties as
Adjudicator, and these costs shall be divided equally
between the Purchaser and the Supplier.
6.1.4 Should the Adjudicator resign or die, or should the
Purchaser and the Supplier agree that the Adjudicator
is not fulfilling his or her functions in accordance with
the provisions of the Contract, a new Adjudicator
shall be jointly appointed by the Purchaser and the
Supplier. Failing agreement between the two within
twenty-eight (28) days, the new Adjudicator shall be
appointed at the request of either party by the
Appointing Authority specified in the SCC, or, if no
Appointing Authority is specified in SCC, the
Contract shall, from this point onward and until the
parties may otherwise agree on an Adjudicator or an
Appointing Authority, be implemented as if there is
no Adjudicator.
6.2
Arbitration
6.2.1 If
(a) the Purchaser or the Supplier is dissatisfied with
the Adjudicator’s decision and acts before this
decision has become final and binding pursuant
to GCC Clause 6.1.2, or
(b) the Adjudicator fails to give a decision within the
allotted time from referral of the dispute pursuant
to GCC Clause 6.1.2, and the Purchaser or the
Supplier acts within the following fourteen (14)
days, or
(c) in the absence of an Adjudicator from the
Contract Agreement, the mutual consultation
pursuant to GCC Clause 6.1.1 expires without
resolution of the dispute and the Purchaser or the
74
Section IV. General Conditions of Contract
Supplier acts within the following fourteen (14)
days,
then either the Purchaser or the Supplier may act to
give notice to the other party, with a copy for
information to the Adjudicator in case an Adjudicator
had been involved, of its intention to commence
arbitration, as provided below, as to the matter in
dispute, and no arbitration in respect of this matter
may be commenced unless such notice is given.
6.2.2 Any dispute in respect of which a notice of intention
to commence arbitration has been given, in
accordance with GCC Clause 6.2.1, shall be finally
settled by arbitration. Arbitration may be commenced
prior to or after Installation of the Information System.
6.2.3 Arbitration proceedings shall be conducted in
accordance with the rules of procedure specified in
the SCC.
6.3
Notwithstanding any reference to the Adjudicator or
arbitration in this clause,
(a)
the parties shall continue to perform their respective
obligations under the Contract unless they otherwise
agree;
(b)
the Purchaser shall pay the Supplier any monies due
the Supplier.
B. SUBJECT MATTER OF CONTRACT
7. Scope of the
System
7.1
Unless otherwise expressly limited in the SCC or Technical
Requirements, the Supplier’s obligations cover the provision
of all Information Technologies, Materials and other Goods
as well as the performance of all Services required for the
design, development, and implementation (including
procurement, quality assurance, assembly, associated site
preparation, Delivery, Pre-commissioning, Installation,
Testing, and Commissioning) of the System, in accordance
with the plans, procedures, specifications, drawings, codes,
and any other documents specified in the Contract and the
Agreed and Finalized Project Plan.
Section IV. General Conditions of Contract
8. Time for
Commencement
and Operational
Acceptance
9. Supplier’s
Responsibilities
75
7.2
The Supplier shall, unless specifically excluded in the
Contract, perform all such work and / or supply all such
items and Materials not specifically mentioned in the
Contract but that can be reasonably inferred from the
Contract as being required for attaining Operational
Acceptance of the System as if such work and / or items and
Materials were expressly mentioned in the Contract.
7.3
The Supplier’s obligations (if any) to provide Goods and
Services as implied by the Recurrent Cost tables of the
Supplier’s bid, such as consumables, spare parts, and
technical services (e.g., maintenance, technical assistance,
and operational support), are as specified in the SCC,
including the relevant terms, characteristics, and timings.
8.1
The Supplier shall commence work on the System within the
period specified in the SCC, and without prejudice to GCC
Clause 28.2, the Supplier shall thereafter proceed with the
System in accordance with the time schedule specified in the
Implementation Schedule in the Technical Requirements
Section and any refinements made in the Agreed and
Finalized Project Plan.
8.2
The Supplier shall achieve Operational Acceptance of the
System (or Subsystem(s) where a separate time for
Operational Acceptance of such Subsystem(s) is specified in
the Contract) within the time specified in the SCC and in
accordance with the time schedule specified in the
Implementation Schedule in the Technical Requirements
Section and any refinements made in the Agreed and
Finalized Project Plan, or within such extended time to
which the Supplier shall be entitled under GCC Clause 40
(Extension of Time for Achieving Operational Acceptance).
9.1
The Supplier shall conduct all activities with due care and
diligence, in accordance with the Contract and with the skill
and care expected of a competent provider of information
technologies, information systems, support, maintenance,
training, and other related services, or in accordance with
best industry practices. In particular, the Supplier shall
provide and employ only technical personnel who are skilled
and experienced in their respective callings and supervisory
staff who are competent to adequately supervise the work at
hand.
76
Section IV. General Conditions of Contract
9.2
The Supplier confirms that it has entered into this Contract
on the basis of a proper examination of the data relating to
the System provided by the Purchaser and on the basis of
information that the Supplier could have obtained from a
visual inspection of the site (if access to the site was
available) and of other data readily available to the Supplier
relating to the System as at the date twenty-eight (28) days
prior to bid submission. The Supplier acknowledges that any
failure to acquaint itself with all such data and information
shall not relieve its responsibility for properly estimating the
difficulty or cost of successfully performing the Contract.
9.3
The Supplier shall be responsible for timely provision of all
resources, information, and decision making under its control
that are necessary to reach a mutually Agreed and Finalized
Project Plan (pursuant to GCC Clause 19.2) within the time
schedule specified in the Implementation Schedule in the
Technical Requirements Section. Failure to provide such
resources, information, and decision making may constitute
grounds for termination pursuant to GCC Clause 41.2.
9.4
The Supplier shall acquire in its name all permits, approvals,
and/or licenses from all local, state, or national government
authorities or public service undertakings in the Purchaser’s
Country that are necessary for the performance of the
Contract, including, without limitation, visas for the
Supplier’s and Subcontractor’s personnel and entry permits
for all imported Supplier’s Equipment. The Supplier shall
acquire all other permits, approvals, and/or licenses that are
not the responsibility of the Purchaser under GCC
Clause 10.4 and that are necessary for the performance of the
Contract.
9.5
The Supplier shall comply with all laws in force in the
Purchaser’s Country. The laws will include all national,
provincial, municipal, or other laws that affect the
performance of the Contract and are binding upon the
Supplier. The Supplier shall indemnify and hold harmless the
Purchaser from and against any and all liabilities, damages,
claims, fines, penalties, and expenses of whatever nature
arising or resulting from the violation of such laws by the
Supplier or its personnel, including the Subcontractors and
their personnel, but without prejudice to GCC Clause 10.1.
The Supplier shall not indemnify the Purchaser to the extent
that such liability, damage, claims, fines, penalties, and
expenses were caused or contributed to by a fault of the
Section IV. General Conditions of Contract
77
Purchaser.
10. Purchaser’s
Responsibilities
9.6
The Supplier shall, in all dealings with its labor and the labor
of its Subcontractors currently employed on or connected
with the Contract, pay due regard to all recognized festivals,
official holidays, religious or other customs, and all local
laws and regulations pertaining to the employment of labor.
9.7
Any Information Technologies or other Goods and Services
that will be incorporated in or be required for the System and
other supplies shall have their Origin, as defined in GCC
Clause 3.12, in a country that shall be an Eligible Country, as
defined in GCC Clause 1.1 (e) (iv).
9.8
The Supplier shall permit the Bank and/or persons appointed
by the Bank to inspect the Supplier’s offices and/or the
accounts and records of the Supplier and its sub-contractors
relating to the performance of the Contract, and to have such
accounts and records audited by auditors appointed by the
Bank if required by the Bank. The Supplier’s attention is
drawn to Sub-Clause 41.2.1(c), which provides, inter alia,
that acts intended to materially impede the exercise of the
Bank’s inspection and audit rights provided for under SubClause 9.8 constitute a prohibited practice subject to contract
termination (as well as to a determination of ineligibility
under the Procurement Guidelines)
9.9
Other Supplier responsibilities, if any, are as stated in the
SCC.
10.1 The Purchaser shall ensure the accuracy of all information
and/or data to be supplied by the Purchaser to the Supplier,
except when otherwise expressly stated in the Contract.
10.2 The Purchaser shall be responsible for timely provision of all
resources, information, and decision making under its control
that are necessary to reach an Agreed and Finalized Project
Plan (pursuant to GCC Clause 19.2) within the time schedule
specified in the Implementation Schedule in the Technical
Requirements Section. Failure to provide such resources,
information, and decision making may constitute grounds for
Termination pursuant to GCC Clause 41.3.1 (b).
10.3 The Purchaser shall be responsible for acquiring and providing
legal and physical possession of the site and access to it, and for
providing possession of and access to all other areas reasonably
78
Section IV. General Conditions of Contract
required for the proper execution of the Contract.
10.4 If requested by the Supplier, the Purchaser shall use its best
endeavors to assist the Supplier in obtaining in a timely and
expeditious manner all permits, approvals, and/or licenses
necessary for the execution of the Contract from all local,
state, or national government authorities or public service
undertakings that such authorities or undertakings require the
Supplier or Subcontractors or the personnel of the Supplier
or Subcontractors, as the case may be, to obtain.
10.5 In such cases where the responsibilities of specifying and
acquiring or upgrading telecommunications and/or electric
power services falls to the Supplier, as specified in the
Technical Requirements, SCC, Agreed and Finalized Project
Plan, or other parts of the Contract, the Purchaser shall use
its best endeavors to assist the Supplier in obtaining such
services in a timely and expeditious manner.
10.6 The Purchaser shall be responsible for timely provision of all
resources, access, and information necessary for the
Installation and Operational Acceptance of the System
(including,
but
not
limited
to,
any required
telecommunications or electric power services), as identified
in the Agreed and Finalized Project Plan, except where
provision of such items is explicitly identified in the Contract
as being the responsibility of the Supplier. Delay by the
Purchaser may result in an appropriate extension of the Time
for Operational Acceptance, at the Supplier’s discretion.
10.7 Unless otherwise specified in the Contract or agreed upon by
the Purchaser and the Supplier, the Purchaser shall provide
sufficient, properly qualified operating and technical
personnel, as required by the Supplier to properly carry out
Delivery, Pre-commissioning, Installation, Commissioning,
and Operational Acceptance, at or before the time specified
in the Technical Requirements Section’s Implementation
Schedule and the Agreed and Finalized Project Plan.
10.8 The Purchaser will designate appropriate staff for the training
courses to be given by the Supplier and shall make all
appropriate logistical arrangements for such training as
specified in the Technical Requirements, SCC, the Agreed
and Finalized Project Plan, or other parts of the Contract.
10.9 The Purchaser assumes primary responsibility for the
Operational Acceptance Test(s) for the System, in
Section IV. General Conditions of Contract
79
accordance with GCC Clause 27.2, and shall be responsible
for the continued operation of the System after Operational
Acceptance. However, this shall not limit in any way the
Supplier’s responsibilities after the date of Operational
Acceptance otherwise specified in the Contract.
10.10 The Purchaser 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 the
Supplier elsewhere in the Contract.
10.11 All costs and expenses involved in the performance of the
obligations under this GCC Clause 10 shall be the
responsibility of the Purchaser, save those to be incurred by
the Supplier with respect to the performance of the
Operational Acceptance Test(s), in accordance with GCC
Clause 27.2.
10.12 Other Purchaser responsibilities, if any, are as stated in the
SCC.
C. PAYMENT
11. Contract Price
11.1 The Contract Price shall be as specified in Article 2
(Contract Price and Terms of Payment) of the Contract
Agreement.
11.2 The Contract Price shall be a firm lump sum not subject to
any alteration, except:
(a)
in the event of a Change in the System pursuant to
GCC Clause 39 or to other clauses in the Contract;
(b)
in accordance with the price adjustment formula (if
any) specified in the SCC.
11.3 The Supplier shall be deemed to have satisfied itself as to the
correctness and sufficiency of the Contract Price, which
shall, except as otherwise provided for in the Contract, cover
all its obligations under the Contract.
12. Terms of
Payment
12.1 The Supplier’s request for payment shall be made to the
Purchaser in writing, accompanied by an invoice describing,
as appropriate, the System or Subsystem(s), Delivered, Precommissioned, Installed, and Operationally Accepted, and by
documents submitted pursuant to GCC Clause 22.5 and upon
80
Section IV. General Conditions of Contract
fulfillment of other obligations stipulated in the Contract.
The Contract Price shall be paid as specified in the SCC.
12.2 No payment made by the Purchaser herein shall be deemed
to constitute acceptance by the Purchaser of the System or
any Subsystem(s).
12.3 Payments shall be made promptly by the Purchaser, but in no
case later than forty five (45) days after submission of a valid
invoice by the Supplier. In the event that the Purchaser fails
to make any payment by its respective due date or within the
period set forth in the Contract, the Purchaser shall pay to the
Supplier interest on the amount of such delayed payment at
the rate(s) specified in the SCC for the period of delay until
payment has been made in full, whether before or after
judgment or arbitration award.
12.4 All payments shall be made in the currency(ies) specified in
the Contract Agreement, pursuant to GCC Clause 11. For
Goods and Services supplied locally, payments shall be made
in the currency of the Purchaser’s Country, unless otherwise
specified in the SCC.
12.5 Unless otherwise specified in the SCC, payment of the
foreign currency portion of the Contract Price for Goods
supplied from outside the Purchaser’s Country shall be made
to the Supplier through an irrevocable letter of credit opened
by an authorized bank in the Supplier’s Country and will be
payable on presentation of the appropriate documents. It is
agreed that the letter of credit will be subject to Article 10 of
the latest revision of Uniform Customs and Practice for
Documentary Credits, published by the International
Chamber of Commerce, Paris.
13. Securities
13.1 Issuance of Securities
The Supplier shall provide the securities specified below in
favor of the Purchaser at the times and in the amount,
manner, and form specified below.
13.2 Advance Payment Security
13.2.1 As specified in the SCC, the Supplier shall provide a
security equal in amount and currency to the advance
payment, and valid until the System is Operationally
Accepted.
Section IV. General Conditions of Contract
81
13.2.2 The security shall be in the form provided in the
Bidding Documents or in another form acceptable to
the Purchaser. The amount of the security shall be
reduced in proportion to the value of the System
executed by and paid to the Supplier from time to time
and shall automatically become null and void when
the full amount of the advance payment has been
recovered by the Purchaser. The way the value of the
security is deemed to become reduced and, eventually,
voided is as specified in the SCC. The security shall
be returned to the Supplier immediately after its
expiration.
13.3 Performance Security
13.3.1 The Supplier shall, within twenty-eight (28) days of
the notification of Contract award, provide a security
for the due performance of the Contract in the amount
and currency specified in the SCC.
13.3.2 The security shall be a bank guarantee in the form
provided in the Sample Forms Section of the Bidding
Documents, or it shall be in another form acceptable to
the Purchaser.
13.3.3 The security shall automatically become null and void
once all the obligations of the Supplier under the
Contract have been fulfilled, including, but not limited
to, any obligations during the warranty Period and any
extensions to the period. The security shall be returned
to the Supplier no later than twenty-eight (28) days
after its expiration.
13.3.4 Upon Operational Acceptance of the entire System,
the security shall be reduced to the amount specified
in the SCC, on the date of such Operational
Acceptance, so that the reduced security would only
cover the remaining warranty obligations of the
Supplier.
14. Taxes and Duties
14.1 For Goods or Services supplied from outside the Purchaser’s
country, the Supplier shall be entirely responsible for all
taxes, stamp duties, license fees, and other such levies
imposed outside the Purchaser’s country. Any duties, such as
importation or customs duties, and taxes and other levies,
payable in the Purchaser’s country for the supply of Goods
and Services from outside the Purchaser’s country are the
82
Section IV. General Conditions of Contract
responsibility of the Purchaser unless these duties or taxes
have been made part of the Contract Price in Article 2 of the
Contract Agreement and the Price Schedule it refers to, in
which case the duties and taxes will be the Supplier’s
responsibility.
14.2 For Goods or Services supplied locally, the Supplier shall be
entirely responsible for all taxes, duties, license fees, etc.,
incurred until delivery of the contracted Goods or Services to
the Purchaser. The only exception are taxes or duties, such as
value-added or sales tax or stamp duty as apply to, or are
clearly identifiable, on the invoices and provided they apply
in the Purchaser’s country, and only if these taxes, levies
and/or duties are also excluded from the Contract Price in
Article 2 of the Contract Agreement and the Price Schedule
it refers to.
14.3 If any tax exemptions, reductions, allowances, or privileges
may be available to the Supplier in the Purchaser’s Country,
the Purchaser shall use its best efforts to enable the Supplier
to benefit from any such tax savings to the maximum
allowable extent.
14.4 For the purpose of the Contract, it is agreed that the Contract
Price specified in Article 2 (Contract Price and Terms of
Payment) of the Contract Agreement is based on the taxes,
duties, levies, and charges prevailing at the date twenty-eight
(28) days prior to the date of bid submission in the
Purchaser’s Country (also called “Tax” in this GCC Clause
14.4). If any Tax rates are increased or decreased, a new Tax
is introduced, an existing Tax is abolished, or any change in
interpretation or application of any Tax occurs in the course
of the performance of the Contract, which was or will be
assessed on the Supplier, its Subcontractors, or their
employees in connection with performance of the Contract,
an equitable adjustment to the Contract Price shall be made
to fully take into account any such change by addition to or
reduction from the Contract Price, as the case may be.
D. INTELLECTUAL PROPERTY
15. Copyright
15.1 The Intellectual Property Rights in all Standard Software and
Standard Materials shall remain vested in the owner of such
rights.
Section IV. General Conditions of Contract
83
15.2 The Purchaser agrees to restrict use, copying, or duplication
of the Standard Software and Standard Materials in
accordance with GCC Clause 16, except that additional
copies of Standard Materials may be made by the Purchaser
for use within the scope of the project of which the System is
a part, in the event that the Supplier does not deliver copies
within thirty (30) days from receipt of a request for such
Standard Materials.
15.3 The Purchaser’s contractual rights to use the Standard
Software or elements of the Standard Software may not be
assigned, licensed, or otherwise transferred voluntarily
except in accordance with the relevant license agreement or
as may be otherwise specified in the SCC.
15.4 As applicable, the Purchaser’s and Supplier’s rights and
obligations with respect to Custom Software or elements of
the Custom Software, including any license agreements, and
with respect to Custom Materials or elements of the Custom
Materials, are specified in the SCC. Subject to the SCC, the
Intellectual Property Rights in all Custom Software and
Custom Materials specified in Appendices 4 and 5 of the
Contract Agreement (if any) shall, at the date of this Contract
or on creation of the rights (if later than the date of this
Contract), vest in the Purchaser. The Supplier shall do and
execute or arrange for the doing and executing of each
necessary act, document, and thing that the Purchaser may
consider necessary or desirable to perfect the right, title, and
interest of the Purchaser in and to those rights. In respect of
such Custom Software and Custom Materials, the Supplier
shall ensure that the holder of a moral right in such an item
does not assert it, and the Supplier shall, if requested to do so
by the Purchaser and where permitted by applicable law,
ensure that the holder of such a moral right waives it.
15.5 The parties shall enter into such (if any) escrow arrangements
in relation to the Source Code to some or all of the Software
as are specified in the SCC and in accordance with the
SCC.
16. Software License
Agreements
16.1 Except to the extent that the Intellectual Property Rights in
the Software vest in the Purchaser, the Supplier hereby grants
to the Purchaser license to access and use the Software,
including all inventions, designs, and marks embodied in the
Software.
84
Section IV. General Conditions of Contract
Such license to access and use the Software shall:
(a)
be:
(i)
nonexclusive;
(ii)
fully paid up and irrevocable (except that it shall
terminate if the Contract terminates under GCC
Clauses 41.1 or 41.3);
(iii) valid throughout the territory of the Purchaser’s
Country (or such other territory as specified in
the SCC); and
(iv) subject to additional restrictions (if any) as
specified in the SCC.
(b)
permit the Software to be:
(i)
used or copied for use on or with the computer(s)
for which it was acquired (if specified in the
Technical Requirements and/or the Supplier’s
bid), plus a backup computer(s) of the same or
similar capacity, if the primary is(are) inoperative,
and during a reasonable transitional period when
use is being transferred between primary and
backup;
(ii)
as specified in the SCC, used or copied for use
on or transferred to a replacement computer(s),
(and use on the original and replacement
computer(s) may be simultaneous during a
reasonable transitional period) provided that, if
the Technical Requirements and/or the Supplier’s
bid specifies a class of computer to which the
license is restricted and unless the Supplier agrees
otherwise in writing, the replacement computer(s)
is(are) within that class;
(iii) if the nature of the System is such as to permit
such access, accessed from other computers
connected to the primary and/or backup
computer(s) by means of a local or wide-area
network or similar arrangement, and used on or
copied for use on those other computers to the
extent necessary to that access;
Section IV. General Conditions of Contract
85
(iv) reproduced for safekeeping or backup purposes;
(v)
customized, adapted, or combined with other
computer software for use by the Purchaser,
provided that derivative software incorporating
any substantial part of the delivered, restricted
Software shall be subject to same restrictions as
are set forth in this Contract;
(vi) as specified in the SCC, disclosed to, and
reproduced for use by, support service suppliers
and their subcontractors, (and the Purchaser may
sublicense such persons to use and copy for use
the Software) to the extent reasonably necessary
to the performance of their support service
contracts, subject to the same restrictions as are
set forth in this Contract; and
(vii) disclosed to, and reproduced for use by, the
Purchaser and by such other persons as are
specified in the SCC (and the Purchaser may
sublicense such persons to use and copy for use
the Software), subject to the same restrictions as
are set forth in this Contract.
16.2 The Standard Software may be subject to audit by the
Supplier, in accordance with the terms specified in the SCC,
to verify compliance with the above license agreements.
17. Confidential
Information
17.1 Except if otherwise specified in the SCC, the "Receiving
Party" (either the Purchaser or the Supplier) shall keep
confidential and shall not, without the written consent of the
other party to this Contract (“the Disclosing Party”), divulge
to any third party any documents, data, or other information
of a confidential nature (“Confidential Information”)
connected with this Contract, and furnished directly or
indirectly by the Disclosing Party prior to or during
performance, or following termination, of this Contract.
17.2 For the purposes of GCC Clause 17.1, the Supplier is also
deemed to be the Receiving Party of Confidential
Information generated by the Supplier itself in the course of
the performance of its obligations under the Contract and
relating to the businesses, finances, suppliers, employees, or
other contacts of the Purchaser or the Purchaser’s use of the
System.
86
Section IV. General Conditions of Contract
17.3 Notwithstanding GCC Clauses 17.1 and 17.2:
(a)
the Supplier may furnish to its Subcontractor
Confidential Information of the Purchaser to the extent
reasonably required for the Subcontractor to perform its
work under the Contract; and
(b)
the Purchaser may furnish Confidential Information of
the Supplier: (i) to its support service suppliers and
their subcontractors to the extent reasonably required
for them to perform their work under their support
service contracts; and (ii) to its affiliates and
subsidiaries,
in which event the Receiving Party shall ensure that the
person to whom it furnishes Confidential Information of the
Disclosing Party is aware of and abides by the Receiving
Party’s obligations under this GCC Clause 17 as if that
person were party to the Contract in place of the Receiving
Party.
17.4 The Purchaser shall not, without the Supplier’s prior written
consent, use any Confidential Information received from the
Supplier for any purpose other than the operation,
maintenance and further development of the System.
Similarly, the Supplier shall not, without the Purchaser’s
prior written consent, use any Confidential Information
received from the Purchaser for any purpose other than those
that are required for the performance of the Contract.
17.5 The obligation of a party under GCC Clauses 17.1 through
17.4 above, however, shall not apply to that information
which:
(a)
now or hereafter enters the public domain through no
fault of the Receiving Party;
(b)
can be proven to have been possessed by the Receiving
Party at the time of disclosure and that was not
previously obtained, directly or indirectly, from the
Disclosing Party;
(c)
otherwise lawfully becomes available to the Receiving
Party from a third party that has no obligation of
confidentiality.
17.6 The above provisions of this GCC Clause 17 shall not in any
way modify any undertaking of confidentiality given by
Section IV. General Conditions of Contract
87
either of the parties to this Contract prior to the date of the
Contract in respect of the System or any part thereof.
17.7 The provisions of this GCC Clause 17 shall survive the
termination, for whatever reason, of the Contract for three (3)
years or such longer period as may be specified in the SCC.
E. SUPPLY, INSTALLATION, TESTING,
COMMISSIONING, AND ACCEPTANCE OF THE SYSTEM
18.
Representatives
18.1 Project Manager
If the Project Manager is not named in the Contract, then
within fourteen (14) days of the Effective Date, the Purchaser
shall appoint and notify the Supplier in writing of the name
of the Project Manager. The Purchaser may 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 Supplier
without delay. No such appointment shall be made at such a
time or in such a manner as to impede the progress of work
on the System. Such appointment shall take effect only upon
receipt of such notice by the Supplier. Subject to the
extensions and/or limitations specified in the SCC (if any),
the Project Manager shall have the authority to represent the
Purchaser on all day-to-day matters relating to the System or
arising from the Contract, and shall normally be the person
giving or receiving notices on behalf of the Purchaser
pursuant to GCC Clause 4.
18.2 Supplier’s Representative
18.2.1 If the Supplier’s Representative is not named in the
Contract, then within fourteen (14) days of the
Effective Date, the Supplier shall appoint the
Supplier’s Representative and shall request the
Purchaser in writing to approve the person so
appointed. The request must be accompanied by a
detailed curriculum vitae for the nominee, as well as a
description of any other System or non-System
responsibilities the nominee would retain while
performing the duties of the Supplier’s Representative.
If the Purchaser does not object to the appointment
within fourteen (14) days, the Supplier’s
Representative shall be deemed to have been
88
Section IV. General Conditions of Contract
approved. If the Purchaser objects to the appointment
within fourteen (14) days giving the reason therefor,
then the Supplier shall appoint a replacement within
fourteen (14) days of such objection in accordance
with this GCC Clause 18.2.1.
18.2.2 Subject to the extensions and/or limitations specified
in the SCC (if any), the Supplier’s Representative
shall have the authority to represent the Supplier on all
day-to-day matters relating to the System or arising
from the Contract, and shall normally be the person
giving or receiving notices on behalf of the Supplier
pursuant to GCC Clause 4.
18.2.3 The Supplier shall not revoke the appointment of the
Supplier’s Representative without the Purchaser’s
prior written consent, which shall not be unreasonably
withheld. If the Purchaser consents to such an action,
the Supplier shall appoint another person of equal or
superior
qualifications
as
the
Supplier’s
Representative, pursuant to the procedure set out in
GCC Clause 18.2.1.
18.2.4 The Supplier’s Representative and staff are obliged to
work closely with the Purchaser’s Project Manager
and staff, act within their own authority, and abide by
directives issued by the Purchaser that are consistent
with the terms of the Contract. The Supplier’s
Representative is responsible for managing the
activities of its personnel and any subcontracted
personnel.
18.2.5 The Supplier’s Representative may, subject to the
approval of the Purchaser (which shall not be
unreasonably withheld), at any time delegate to any
person any of the powers, functions, and authorities
vested in him or her. Any such delegation may be
revoked at any time. Any such delegation or
revocation shall be subject to a prior notice signed by
the Supplier’s Representative and shall specify the
powers, functions, and authorities thereby delegated or
revoked. No such delegation or revocation shall take
effect unless and until the notice of it has been
delivered.
18.2.6 Any act or exercise by any person of powers, functions
Section IV. General Conditions of Contract
89
and authorities so delegated to him or her in
accordance with GCC Clause 18.2.5 shall be deemed
to be an act or exercise by the Supplier’s
Representative.
18.3 Objections and Removals
18.3.1 The Purchaser may by notice to the Supplier object to
any representative or person employed by the Supplier
in the execution of the Contract who, in the reasonable
opinion of the Purchaser, may have behaved
inappropriately, be incompetent, or be negligent. The
Purchaser shall provide evidence of the same,
whereupon the Supplier shall remove such person
from work on the System.
18.3.2 If any representative or person employed by the
Supplier is removed in accordance with GCC Clause
18.3.1, the Supplier shall, where required, promptly
appoint a replacement.
19. Project Plan
19.1 In close cooperation with the Purchaser and based on the
Preliminary Project Plan included in the Supplier’s bid, the
Supplier shall develop a Project Plan encompassing the
activities specified in the Contract. The contents of the
Project Plan shall be as specified in the SCC and/or
Technical Requirements.
19.2 The Supplier shall formally present to the Purchaser the
Project Plan in accordance with the procedure specified in
the SCC.
19.3 If required, the impact on the Implementation Schedule of
modifications agreed during finalization of the Agreed and
Finalized Project Plan shall be incorporated in the Contract
by amendment, in accordance with GCC Clauses 39 and 40.
19.4 The Supplier shall undertake to supply, install, test, and
commission the System in accordance with the Agreed and
Finalized Project Plan and the Contract.
19.5 The Progress and other reports specified in the SCC shall be
prepared by the Supplier and submitted to the Purchaser in
the format and frequency specified in the Technical
Requirements.
20. Subcontracting
20.1 Appendix 3 (List of Approved Subcontractors) to the
Contract Agreement specifies critical items of supply or
90
Section IV. General Conditions of Contract
services and a list of Subcontractors for each item that are
considered acceptable by the Purchaser. If no Subcontractors
are listed for an item, the Supplier shall prepare a list of
Subcontractors it considers qualified and wishes to be added
to the list for such items. The Supplier may from time to time
propose additions to or deletions from any such list. The
Supplier shall submit any such list or any modification to the
list to the Purchaser for its approval in sufficient time so as
not to impede the progress of work on the System. The
Purchaser shall not withhold such approval unreasonably.
Such approval by the Purchaser of a Subcontractor(s) shall
not relieve the Supplier from any of its obligations, duties, or
responsibilities under the Contract.
20.2 The Supplier may, at its discretion, select and employ
Subcontractors for such critical items from those
Subcontractors listed pursuant to GCC Clause 20.1. If the
Supplier wishes to employ a Subcontractor not so listed, or
subcontract an item not so listed, it must seek the Purchaser’s
prior approval under GCC Clause 20.3.
20.3 For items for which pre-approved Subcontractor lists have
not been specified in Appendix 3 to the Contract Agreement,
the Supplier may employ such Subcontractors as it may
select, provided: (i) the Supplier notifies the Purchaser in
writing at least twenty-eight (28) days prior to the proposed
mobilization date for such Subcontractor; and (ii) by the end
of this period either the Purchaser has granted its approval in
writing or fails to respond. The Supplier shall not engage any
Subcontractor to which the Purchaser has objected in writing
prior to the end of the notice period. The absence of a written
objection by the Purchaser during the above specified period
shall constitute formal acceptance of the proposed
Subcontractor. Except to the extent that it permits the
deemed approval of the Purchaser of Subcontractors not
listed in the Contract Agreement, nothing in this Clause,
however, shall limit the rights and obligations of either the
Purchaser or Supplier as they are specified in GCC
Clauses 20.1 and 20.2, in the SCC, or in Appendix 3 of the
Contract Agreement.
21. Design and
Engineering
21.1 Technical Specifications and Drawings
21.1.1 The Supplier shall execute the basic and detailed
design and the implementation activities necessary for
successful installation of the System in compliance
Section IV. General Conditions of Contract
91
with the provisions of the Contract or, where not so
specified, in accordance with good industry practice.
The Supplier shall be responsible for any
discrepancies, errors or omissions in the
specifications, drawings, 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 Supplier by or on behalf of the
Purchaser.
21.1.2 The Supplier shall be entitled to disclaim
responsibility for any design, data, drawing,
specification, or other document, or any modification
of such design, drawings, specification, or other
documents provided or designated by or on behalf of
the Purchaser, by giving a notice of such disclaimer to
the Project Manager.
21.2 Codes and Standards
Wherever references are made in the Contract to codes and
standards in accordance with which the Contract shall be
executed, the edition or the revised version of such codes and
standards current at the date twenty-eight (28) days prior to
date of bid submission shall apply unless otherwise specified
in the SCC. During Contract execution, any changes in such
codes and standards shall be applied after approval by the
Purchaser and shall be treated in accordance with GCC
Clause 39.3.
21.3 Approval/Review of Technical Documents by the Project
Manager
21.3.1 The Supplier shall prepare and furnish to the Project
Manager the documents as specified in the SCC for
the Project Manager’s approval or review.
Any part of the System covered by or related to the
documents to be approved by the Project Manager
shall be executed only after the Project Manager’s
approval of these documents.
GCC Clauses 21.3.2 through 21.3.7 shall apply to
92
Section IV. General Conditions of Contract
those documents requiring the Project Manager’s
approval, but not to those furnished to the Project
Manager for its review only.
21.3.2 Within fourteen (14) days after receipt by the Project
Manager of any document requiring the Project
Manager’s approval in accordance with GCC Clause
21.3.1, the Project Manager shall either return one
copy of the document to the Supplier with its approval
endorsed on the document or shall notify the Supplier
in writing of its disapproval of the document and the
reasons for disapproval and the modifications that the
Project Manager proposes. If the Project Manager fails
to take such action within the fourteen (14) days, then
the document shall be deemed to have been approved
by the Project Manager.
21.3.3 The Project Manager shall not disapprove any
document except on the grounds that the document
does not comply with some specified provision of the
Contract or that it is contrary to good industry practice.
21.3.4 If the Project Manager disapproves the document, the
Supplier shall modify the document and resubmit it for
the Project Manager’s approval in accordance with
GCC Clause 21.3.2. If the Project Manager approves
the document subject to modification(s), the Supplier
shall make the required modification(s), and the
document shall then be deemed to have been
approved, subject to GCC Clause 21.3.5. The
procedure set out in GCC Clauses 21.3.2 through
21.3.4 shall be repeated, as appropriate, until the
Project Manager approves such documents.
21.3.5 If any dispute occurs between the Purchaser and the
Supplier in connection with or arising out of the
disapproval by the Project Manager of any document
and/or any modification(s) to a document that cannot
be settled between the parties within a reasonable
period, then, in case the Contract Agreement includes
and names an Adjudicator, such dispute may be
referred to the Adjudicator for determination in
accordance with GCC Clause 6.1 (Adjudicator). If
such dispute is referred to an Adjudicator, the Project
Manager shall give instructions as to whether and if
so, how, performance of the Contract is to proceed.
Section IV. General Conditions of Contract
93
The Supplier shall proceed with the Contract in
accordance with the Project Manager’s instructions,
provided that if the Adjudicator upholds the Supplier’s
view on the dispute and if the Purchaser has not given
notice under GCC Clause 6.1.2, then the Supplier
shall be reimbursed by the Purchaser for any
additional costs incurred by reason of such
instructions and shall be relieved of such
responsibility or liability in connection with the
dispute and the execution of the instructions as the
Adjudicator shall decide, and the Time for Achieving
Operational
Acceptance
shall
be
extended
accordingly.
21.3.6 The Project Manager’s approval, with or without
modification of the document furnished by the
Supplier, shall not relieve the Supplier of any
responsibility or liability imposed upon it by any
provisions of the Contract except to the extent that any
subsequent failure results from modifications required
by the Project Manager or inaccurate information
furnished in writing to the Supplier by or on behalf of
the Purchaser.
21.3.7 The Supplier shall not depart from any approved
document unless the Supplier has first submitted to
the Project Manager an amended document and
obtained the Project Manager’s approval of the
document, pursuant to the provisions of this GCC
Clause 21.3. If the Project Manager requests any
change in any already approved document and/or in
any document based on such an approved document,
the provisions of GCC Clause 39 (Changes to the
System) shall apply to such request.
22. Procurement,
Delivery, and
Transport
22.1 Subject to related Purchaser's responsibilities pursuant to
GCC Clauses 10 and 14, the Supplier shall manufacture or
procure and transport all the Information Technologies,
Materials, and other Goods in an expeditious and orderly
manner to the Project Site.
22.2 Delivery of the Information Technologies, Materials, and
other Goods shall be made by the Supplier in accordance
with the Technical Requirements.
22.3 Early or partial deliveries require the explicit written consent
94
Section IV. General Conditions of Contract
of the Purchaser, which consent shall not be unreasonably
withheld.
22.4 Transportation
22.4.1 The Supplier shall provide such packing of the Goods
as is required to prevent their damage or deterioration
during shipment. The packing, marking, and
documentation within and outside the packages shall
comply strictly with the Purchaser’s instructions to the
Supplier.
22.4.2 The Supplier will bear responsibility for and cost of
transport to the Project Sites in accordance with the
terms and conditions used in the specification of
prices in the Price Schedules, including the terms and
conditions of the associated Incoterms.
22.4.3 Unless otherwise specified in the SCC, the Supplier
shall be free to use transportation through carriers
registered in any eligible country and to obtain
insurance from any eligible source country.
22.5 Unless otherwise specified in the SCC, the Supplier will
provide the Purchaser with shipping and other documents, as
specified below:
22.5.1 For Goods supplied from outside the Purchaser’s
Country:
Upon shipment, the Supplier shall notify the Purchaser
and the insurance company contracted by the Supplier
to provide cargo insurance by telex, cable, facsimile,
electronic mail, or EDI with the full details of the
shipment. The Supplier shall promptly send the
following documents to the Purchaser by mail or
courier, as appropriate, with a copy to the cargo
insurance company:
(a)
two copies of the Supplier’s invoice showing the
description of the Goods, quantity, unit price, and
total amount;
(b)
usual transportation documents;
(c)
insurance certificate;
(d)
certificate(s) of origin; and
Section IV. General Conditions of Contract
95
(e)
estimated time and point of arrival in the
Purchaser’s Country and at the site.
22.5.2 For Goods supplied locally (i.e., from within the
Purchaser’s country):
Upon shipment, the Supplier shall notify the Purchaser
by telex, cable, facsimile, electronic mail, or EDI with
the full details of the shipment. The Supplier shall
promptly send the following documents to the
Purchaser by mail or courier, as appropriate:
(a)
two copies of the Supplier’s invoice showing the
Goods’ description, quantity, unit price, and total
amount;
(b)
delivery note, railway receipt, or truck receipt;
(c)
certificate of insurance;
(d)
certificate(s) of origin; and
(e)
estimated time of arrival at the site.
22.6 Customs Clearance
(a)
The Purchaser will bear responsibility for, and cost of,
customs clearance into the Purchaser's country in
accordance the particular Incoterm(s) used for Goods
supplied from outside the Purchaser’s country in the
Price Schedules referred to by Article 2 of the Contract
Agreement.
(b)
At the request of the Purchaser, the Supplier will make
available a representative or agent during the process of
customs clearance in the Purchaser's country for goods
supplied from outside the Purchaser's country. In the
event of delays in customs clearance that are not the
fault of the Supplier:
(i)
the Supplier shall be entitled to an extension in
the Time for Achieving Operational Acceptance,
pursuant to GCC Clause 40;
(ii)
the Contract Price shall be adjusted to
compensate the Supplier for any additional
storage charges that the Supplier may incur as a
result of the delay.
96
23. Product
Upgrades
Section IV. General Conditions of Contract
23.1 At any point during performance of the Contract, should
technological advances be introduced by the Supplier for
Information Technologies originally offered by the Supplier
in its bid and still to be delivered, the Supplier shall be
obligated to offer to the Purchaser the latest versions of the
available Information Technologies having equal or better
performance or functionality at the same or lesser unit prices,
pursuant to GCC Clause 39 (Changes to the System).
23.2 At any point during performance of the Contract, for
Information Technologies still to be delivered, the Supplier
will also pass on to the Purchaser any cost reductions and
additional and/or improved support and facilities that it
offers to other clients of the Supplier in the Purchaser’s
Country, pursuant to GCC Clause 39 (Changes to the
System).
23.3 During performance of the Contract, the Supplier shall offer
to the Purchaser all new versions, releases, and updates of
Standard Software, as well as related documentation and
technical support services, within thirty (30) days of their
availability from the Supplier to other clients of the Supplier
in the Purchaser’s Country, and no later than twelve (12)
months after they are released in the country of origin. In no
case will the prices for these Software exceed those quoted
by the Supplier in the Recurrent Costs tables in its bid.
23.4 During the warranty Period, unless otherwise specified in
the SCC, the Supplier will provide at no additional cost to
the Purchaser all new versions, releases, and updates for all
Standard Software that are used in the System, within thirty
(30) days of their availability from the Supplier to other
clients of the Supplier in the Purchaser’s country, and no
later than twelve (12) months after they are released in the
country of origin of the Software.
23.5 The Purchaser shall introduce all new versions, releases or
updates of the Software within eighteen (18) months of
receipt of a production-ready copy of the new version,
release, or update, provided that the new version, release, or
update does not adversely affect System operation or
performance or require extensive reworking of the System. In
cases where the new version, release, or update adversely
affects System operation or performance, or requires
extensive reworking of the System, the Supplier shall
continue to support and maintain the version or release
Section IV. General Conditions of Contract
97
previously in operation for as long as necessary to allow
introduction of the new version, release, or update. In no case
shall the Supplier stop supporting or maintaining a version or
release of the Software less than twenty four (24) months
after the Purchaser receives a production-ready copy of a
subsequent version, release, or update. The Purchaser shall
use all reasonable endeavors to implement any new version,
release, or update as soon as practicable, subject to the
twenty-four-month-long stop date.
24. Implementation,
Installation, and
Other Services
24.1 The Supplier shall provide all Services specified in the
Contract and Agreed and Finalized Project Plan in
accordance with the highest standards of professional
competence and integrity.
24.2 Prices charged by the Supplier for Services, if not included in
the Contract, shall be agreed upon in advance by the parties
(including, but not restricted to, any prices submitted by the
Supplier in the Recurrent Cost Schedules of its Bid) and
shall not exceed the prevailing rates charged by the Supplier
to other purchasers in the Purchaser’s Country for similar
services.
25. Inspections and
Tests
25.1 The Purchaser or its representative shall have the right to
inspect and/or test any components of the System, as
specified in the Technical Requirements, to confirm their
good working order and/or conformity to the Contract at the
point of delivery and/or at the Project Site.
25.2 The Purchaser or its representative shall be entitled to attend
any such inspections and/or tests of the components,
provided that the Purchaser shall bear all costs and expenses
incurred in connection with such attendance, including but
not limited to all inspection agent fees, travel, and related
expenses.
25.3 Should the inspected or tested components fail to conform to
the Contract, the Purchaser may reject the component(s), and
the Supplier shall either replace the rejected component(s),
or make alterations as necessary so that it meets the Contract
requirements free of cost to the Purchaser.
25.4 The Project Manager may require the Supplier to carry out
any inspection and/or test not specified in the Contract,
provided that the Supplier’s reasonable costs and expenses
incurred in the carrying out of such inspection and/or test
shall be added to the Contract Price. Further, if such
98
Section IV. General Conditions of Contract
inspection and/or test impedes the progress of work on the
System and/or the Supplier’s performance of its other
obligations under the Contract, due allowance will be made
in respect of the Time for Achieving Operational Acceptance
and the other obligations so affected.
25.5 If any dispute shall arise between the parties in connection
with or caused by an inspection and/or with regard to any
component to be incorporated in the System that cannot be
settled amicably between the parties within a reasonable
period of time, either party may invoke the process pursuant
to GCC Clause 6 (Settlement of Disputes), starting with
referral of the matter to the Adjudicator in case an
Adjudicator is included and named in the Contract
Agreement.
26. Installation of the 26.1 As soon as the System, or any Subsystem, has, in the opinion
of the Supplier, been delivered, Pre-commissioned, and made
System
ready for Commissioning and Operational Acceptance
Testing in accordance with the Technical Requirements, the
SCC and the Agreed and Finalized Project Plan, the Supplier
shall so notify the Purchaser in writing.
26.2 The Project Manager shall, within fourteen (14) days after
receipt of the Supplier’s notice under GCC Clause 26.1,
either issue an Installation Certificate in the form specified in
the Sample Forms Section in the Bidding Documents, stating
that the System, or major component or Subsystem (if
Acceptance by major component or Subsystem is specified
pursuant to the SCC for GCC Clause 27.2.1), has achieved
Installation by the date of the Supplier’s notice under GCC
Clause 26.1, or notify the Supplier in writing of any defects
and/or deficiencies, including, but not limited to, defects or
deficiencies in the interoperability or integration of the
various components and/or Subsystems making up the
System. The Supplier shall use all reasonable endeavors to
promptly remedy any defect and/or deficiencies that the
Project Manager has notified the Supplier of. The Supplier
shall then promptly carry out retesting of the System or
Subsystem and, when in the Supplier’s opinion the System or
Subsystem is ready for Commissioning and Operational
Acceptance Testing, notify the Purchaser in writing, in
accordance with GCC Clause 26.1. The procedure set out in
this GCC Clause 26.2 shall be repeated, as necessary, until
an Installation Certificate is issued.
Section IV. General Conditions of Contract
99
26.3 If the Project Manager fails to issue the Installation
Certificate and fails to inform the Supplier of any defects
and/or deficiencies within fourteen (14) days after receipt of
the Supplier’s notice under GCC Clause 26.1, or if the
Purchaser puts the System or a Subsystem into production
operation, then the System (or Subsystem) shall be deemed
to have achieved successful Installation as of the date of the
Supplier’s notice or repeated notice, or when the Purchaser
put the System into production operation, as the case may be.
27. Commissioning
and Operational
Acceptance
27.1 Commissioning
27.1.1 Commissioning of the System (or Subsystem if
specified pursuant to the SCC for GCC Clause 27.2.1)
shall be commenced by the Supplier:
(a)
immediately after the Installation Certificate is
issued by the Project Manager, pursuant to GCC
Clause 26.2; or
(b)
as otherwise specified in the Technical
Requirement or the Agreed and Finalized
Project Plan; or
(c)
immediately after Installation is deemed to have
occurred, under GCC Clause 26.3.
27.1.2 The Purchaser shall supply the operating and technical
personnel and all materials and information reasonably
required to enable the Supplier to carry out its
obligations with respect to Commissioning.
Production use of the System or Subsystem(s) shall
not commence prior to the start of formal Operational
Acceptance Testing.
27.2 Operational Acceptance Tests
27.2.1 The Operational Acceptance Tests (and repeats of
such tests) shall be the primary responsibility of the
Purchaser (in accordance with GCC Clause 10.9), but
shall be conducted with the full cooperation of the
Supplier during Commissioning of the System (or
major components or Subsystem[s] if specified in the
SCC and supported by the Technical Requirements),
to ascertain whether the System (or major component
or Subsystem[s]) conforms to the Technical
Requirements and meets the standard of performance
100
Section IV. General Conditions of Contract
quoted in the Supplier’s bid, including, but not
restricted to, the functional and technical performance
requirements. The Operational Acceptance Tests
during Commissioning will be conducted as specified
in the SCC, the Technical Requirements and/or the
Agreed and Finalized Project Plan.
At the Purchaser’s discretion, Operational Acceptance
Tests may also be performed on replacement Goods,
upgrades and new version releases, and Goods that are
added or field-modified after Operational Acceptance
of the System.
27.2.2 If for reasons attributable to the Purchaser, the
Operational Acceptance Test of the System (or
Subsystem[s] or major components, pursuant to the
SCC for GCC Clause 27.2.1) cannot be successfully
completed within the period specified in the SCC,
from the date of Installation or any other period agreed
upon in writing by the Purchaser and the Supplier, the
Supplier shall be deemed to have fulfilled its
obligations with respect to the technical and functional
aspects of the Technical Specifications, SCC and/or
the Agreed and Finalized Project Plan, and GCC
Clause 28.2 and 28.3 shall not apply.
27.3 Operational Acceptance
27.3.1 Subject to GCC Clause 27.4 (Partial Acceptance)
below, Operational Acceptance shall occur in respect
of the System, when
(a) the Operational Acceptance Tests, as specified in
the Technical Requirements, and/or SCC and/or
the Agreed and Finalized Project Plan have been
successfully completed; or
(b) the Operational Acceptance Tests have not been
successfully completed or have not been carried
out for reasons that are attributable to the
Purchaser within the period from the date of
Installation or any other agreed-upon period as
specified in GCC Clause 27.2.2 above; or
(c) the Purchaser has put the System into production
or use for sixty (60) consecutive days. If the
System is put into production or use in this
Section IV. General Conditions of Contract
101
manner, the Supplier shall notify the Purchaser
and document such use.
27.3.2 At any time after any of the events set out in GCC
Clause 27.3.1 have occurred, the Supplier may give a
notice to the Project Manager requesting the issue of
an Operational Acceptance Certificate.
27.3.3 After consultation with the Purchaser, and within
fourteen (14) days after receipt of the Supplier’s
notice, the Project Manager shall:
(a)
issue an Operational Acceptance Certificate; or
(b)
notify the Supplier in writing of any defect or
deficiencies or other reason for the failure of the
Operational Acceptance Tests; or
(c)
issue the Operational Acceptance Certificate, if the
situation covered by GCC Clause 27.3.1 (b) arises.
27.3.4 The Supplier shall use all reasonable endeavors to
promptly remedy any defect and/or deficiencies and/or
other reasons for the failure of the Operational
Acceptance Test that the Project Manager has notified
the Supplier of. Once such remedies have been made
by the Supplier, the Supplier shall notify the
Purchaser, and the Purchaser, with the full cooperation
of the Supplier, shall use all reasonable endeavors to
promptly carry out retesting of the System or
Subsystem. Upon the successful conclusion of the
Operational Acceptance Tests, the Supplier shall
notify the Purchaser of its request for Operational
Acceptance Certification, in accordance with GCC
Clause 27.3.3. The Purchaser shall then issue to the
Supplier the Operational Acceptance Certification in
accordance with GCC Clause 27.3.3 (a), or shall notify
the Supplier of further defects, deficiencies, or other
reasons for the failure of the Operational Acceptance
Test. The procedure set out in this GCC Clause 27.3.4
shall be repeated, as necessary, until an Operational
Acceptance Certificate is issued.
27.3.5 If the System or Subsystem fails to pass the
Operational Acceptance Test(s) in accordance with
GCC Clause 27.2, then either:
102
Section IV. General Conditions of Contract
(a)
the Purchaser may consider terminating the
Contract, pursuant to GCC Clause 41.2.2;
or
(b)
if the failure to achieve Operational Acceptance
within the specified time period is a result of the
failure of the Purchaser to fulfill its obligations
under the Contract, then the Supplier shall be
deemed to have fulfilled its obligations with
respect to the relevant technical and functional
aspects of the Contract, and GCC Clauses 30.3
and 30.4 shall not apply.
27.3.6 If within fourteen (14) days after receipt of the
Supplier’s notice the Project Manager fails to issue the
Operational Acceptance Certificate or fails to inform
the Supplier in writing of the justifiable reasons why
the Project Manager has not issued the Operational
Acceptance Certificate, the System or Subsystem shall
be deemed to have been accepted as of the date of the
Supplier’s said notice.
27.4 Partial Acceptance
27.4.1 If so specified in the SCC for GCC Clause 27.2.1,
Installation and Commissioning shall be carried out
individually for each identified major component or
Subsystem(s) of the System. In this event, the provisions
in the Contract relating to Installation and
Commissioning, including the Operational Acceptance
Test, shall apply to each such major component or
Subsystem individually, and Operational Acceptance
Certificate(s) shall be issued accordingly for each such
major component or Subsystem of the System, subject to
the limitations contained in GCC Clause 27.4.2.
27.4.2 The issuance of Operational Acceptance Certificates for
individual major components or Subsystems pursuant to
GCC Clause 27.4.1 shall not relieve the Supplier of its
obligation to obtain an Operational Acceptance
Certificate for the System as an integrated whole (if so
specified in the SCC for GCC Clauses 12.1 and 27.2.1)
once all major components and Subsystems have been
supplied, installed, tested, and commissioned.
27.4.3 In the case of minor components for the System that
by their nature do not require Commissioning or an
Section IV. General Conditions of Contract
103
Operational Acceptance Test (e.g., minor fittings,
furnishings or site works, etc.), the Project Manager
shall issue an Operational Acceptance Certificate
within fourteen (14) days after the fittings and/or
furnishings have been delivered and/or installed or the
site works have been completed. The Supplier shall,
however, use all reasonable endeavors to promptly
remedy any defects or deficiencies in such minor
components detected by the Purchaser or Supplier.
F. GUARANTEES AND LIABILITIES
28. Operational
Acceptance Time
Guarantee
28.1 The Supplier guarantees that it shall complete the supply,
Installation, Commissioning, and achieve Operational
Acceptance of the System (or Subsystems, pursuant to the
SCC for GCC Clause 27.2.1) within the time periods
specified in the Implementation Schedule in the Technical
Requirements Section and/or the Agreed and Finalized
Project Plan pursuant to GCC Clause 8.2, or within such
extended time to which the Supplier shall be entitled under
GCC Clause 40 (Extension of Time for Achieving
Operational Acceptance).
28.2 If the Supplier fails to supply, install, commission, and achieve
Operational Acceptance of the System (or Subsystems pursuant
to the SCC for GCC Clause 27.2.1) within the time for
achieving Operational Acceptance specified in the
Implementation Schedule in the Technical Requirement or the
Agreed and Finalized Project Plan, or any extension of the time
for achieving Operational Acceptance previously granted under
GCC Clause 40 (Extension of Time for Achieving Operational
Acceptance), the Supplier shall pay to the Purchaser liquidated
damages at the rate specified in the SCC as a percentage of the
Contract Price, or the relevant part of the Contract Price if a
Subsystem has not achieved Operational Acceptance. The
aggregate amount of such liquidated damages shall in no event
exceed the amount specified in the SCC (“the Maximum”).
Once the Maximum is reached, the Purchaser may consider
termination of the Contract, pursuant to GCC Clause 41.2.2.
28.3 Unless otherwise specified in the SCC, liquidated damages
payable under GCC Clause 28.2 shall apply only to the
failure to achieve Operational Acceptance of the System (and
Subsystems) as specified in the Implementation Schedule in
the Technical Requirements and/or Agreed and Finalized
104
Section IV. General Conditions of Contract
Project Plan. This Clause 28.3 shall not limit, however, any
other rights or remedies the Purchaser may have under the
Contract for other delays.
28.4 If liquidated damages are claimed by the Purchaser for the
System (or Subsystem), the Supplier shall have no further
liability whatsoever to the Purchaser in respect to the
Operational Acceptance time guarantee for the System (or
Subsystem). However, the payment of liquidated damages
shall not in any way relieve the Supplier from any of its
obligations to complete the System or from any other of its
obligations and liabilities under the Contract.
29. Defect Liability
29.1 The Supplier warrants that the System, including all
Information Technologies, Materials, and other Goods
supplied and Services provided, shall be free from defects in
the design, engineering, Materials, and workmanship that
prevent the System and/or any of its components from
fulfilling the Technical Requirements or that limit in a
material fashion the performance, reliability, or extensibility
of the System and/or Subsystems. Exceptions and/or
limitations, if any, to this warranty with respect to Software
(or categories of Software), shall be as specified in the SCC.
Commercial warranty provisions of products supplied under
the Contract shall apply to the extent that they do not conflict
with the provisions of this Contract.
29.2 The Supplier also warrants that the Information
Technologies, Materials, and other Goods supplied under the
Contract are new, unused, and incorporate all recent
improvements in design that materially affect the System’s or
Subsystem’s ability to fulfill the Technical Requirements.
29.3 In addition, the Supplier warrants that: (i) all Goods
components to be incorporated into the System form part of
the Supplier’s and/or Subcontractor’s current product lines,
(ii) they have been previously released to the market, and
(iii) those specific items identified in the SCC (if any) have
been in the market for at least the minimum periods
specified in the SCC.
29.4 The warranty Period shall commence from the date of
Operational Acceptance of the System (or of any major
component or Subsystem for which separate Operational
Acceptance is provided for in the Contract) and shall extend
for the length of time specified in the SCC.
Section IV. General Conditions of Contract
105
29.5 If during the warranty Period any defect as described in
GCC Clause 29.1 should be found in the design, engineering,
Materials, and workmanship of the Information Technologies
and other Goods supplied or of the Services provided by the
Supplier, the Supplier shall promptly, in consultation and
agreement with the Purchaser regarding appropriate
remedying of the defects, and at its sole cost, repair, replace,
or otherwise make good (as the Supplier shall, at its
discretion, determine) such defect as well as any damage to
the System caused by such defect. Any defective Information
Technologies or other Goods that have been replaced by the
Supplier shall remain the property of the Supplier.
29.6 The Supplier shall not be responsible for the repair,
replacement, or making good of any defect or of any damage
to the System arising out of or resulting from any of the
following causes:
(a) improper operation or maintenance of the System by the
Purchaser;
(b) normal wear and tear;
(c) use of the System with items not supplied by the
Supplier, unless otherwise identified in the Technical
Requirements, or approved by the Supplier; or
(d) modifications made to the System by the Purchaser, or a
third party, not approved by the Supplier.
29.7 The Supplier’s obligations under this GCC Clause 29 shall
not apply to:
(a) any materials that are normally consumed in operation or
have a normal life shorter than the warranty Period; or
(b) any designs, specifications, or other data designed,
supplied, or specified by or on behalf of the Purchaser or
any matters for which the Supplier has disclaimed
responsibility, in accordance with GCC Clause 21.1.2.
29.8 The Purchaser shall give the Supplier a notice promptly
following the discovery of such defect, stating the nature of
any such defect together with all available evidence. The
Purchaser shall afford all reasonable opportunity for the
Supplier to inspect any such defect. The Purchaser shall
afford the Supplier all necessary access to the System and the
site to enable the Supplier to perform its obligations under
106
Section IV. General Conditions of Contract
this GCC Clause 29.
29.9 The Supplier may, with the consent of the Purchaser, remove
from the site any Information Technologies and other Goods
that are defective, if the nature of the defect, and/or any
damage to the System caused by the defect, is such that
repairs cannot be expeditiously carried out at the site. If the
repair, replacement, or making good is of such a character
that it may affect the efficiency of the System, the Purchaser
may give the Supplier notice requiring that tests of the
defective part be made by the Supplier immediately upon
completion of such remedial work, whereupon the Supplier
shall carry out such tests.
If such part fails the tests, the Supplier shall carry out further
repair, replacement, or making good (as the case may be)
until that part of the System passes such tests. The tests shall
be agreed upon by the Purchaser and the Supplier.
29.10
If the Supplier fails to commence the work necessary to
remedy such defect or any damage to the System caused by
such defect within the time period specified in the SCC, the
Purchaser may, following notice to the Supplier, proceed to
do such work or contract a third party (or parties) to do such
work, and the reasonable costs incurred by the Purchaser in
connection with such work shall be paid to the Purchaser by
the Supplier or may be deducted by the Purchaser from any
monies due the Supplier or claimed under the Performance
Security.
29.11 If the System or Subsystem cannot be used by reason of
such defect and/or making good of such defect, the warranty
Period for the System shall be extended by a period equal to
the period during which the System or Subsystem could not
be used by the Purchaser because of such defect and/or
making good of such defect.
29.12 Items substituted for defective parts of the System during
the warranty Period shall be covered by the Defect Liability
warranty for the remainder of the warranty Period applicable
for the part replaced or three (3) months, whichever is
greater.
29.13 At the request of the Purchaser and without prejudice to any
other rights and remedies that the Purchaser may have
against the Supplier under the Contract, the Supplier will
offer all possible assistance to the Purchaser to seek
Section IV. General Conditions of Contract
107
warranty services or remedial action from any subcontracted
third-party producers or licensor of Goods included in the
System, including without limitation assignment or transfer
in favor of the Purchaser of the benefit of any warranties
given by such producers or licensors to the Supplier.
30. Functional
Guarantees
30.1 The Supplier guarantees that, once the Operational
Acceptance Certificate(s) has been issued, the System
represents a complete, integrated solution to the Purchaser’s
requirements set forth in the Technical Requirements and it
conforms to all other aspects of the Contract. The Supplier
acknowledges that GCC Clause 27 regarding Commissioning
and Operational Acceptance governs how technical
conformance of the System to the Contract requirements will
be determined.
30.2 If, for reasons attributable to the Supplier, the System does
not conform to the Technical Requirements or does not
conform to all other aspects of the Contract, the Supplier
shall at its cost and expense make such changes,
modifications, and/or additions to the System as may be
necessary to conform to the Technical Requirements and
meet all functional and performance standards. The Supplier
shall notify the Purchaser upon completion of the necessary
changes, modifications, and/or additions and shall request
the Purchaser to repeat the Operational Acceptance Tests
until the System achieves Operational Acceptance.
30.3 If the System (or Subsystem[s]) fails to achieve Operational
Acceptance, the Purchaser may consider termination of the
Contract, pursuant to GCC Clause 41.2.2, and forfeiture of
the Supplier’s Performance Security in accordance with GCC
Clause 13.3 in compensation for the extra costs and delays
likely to result from this failure.
31. Intellectual
Property Rights
warranty
31.1 The Supplier hereby represents and warrants that:
(a)
the System as supplied, installed, tested, and accepted;
(b)
use of the System in accordance with the Contract; and
(c)
copying of the Software and Materials provided to the
Purchaser in accordance with the Contract
do not and will not infringe any Intellectual Property Rights
held by any third party and that it has all necessary rights or
at its sole expense shall have secured in writing all transfers
108
Section IV. General Conditions of Contract
of rights and other consents necessary to make the
assignments, licenses, and other transfers of Intellectual
Property Rights and the warranties set forth in the Contract,
and for the Purchaser to own or exercise all Intellectual
Property Rights as provided in the Contract. Without
limitation, the Supplier shall secure all necessary written
agreements, consents, and transfers of rights from its
employees and other persons or entities whose services are
used for development of the System.
32. Intellectual
Property Rights
Indemnity
32.1 The Supplier shall indemnify and hold harmless the
Purchaser and its employees and officers from and against
any and all losses, liabilities, and costs (including losses,
liabilities, and costs incurred in defending a claim alleging
such a liability), that the Purchaser or its employees or
officers may suffer as a result of any infringement or alleged
infringement of any Intellectual Property Rights by reason of:
(a)
installation of the System by the Supplier or the use of
the System, including the Materials, in the country
where the site is located;
(b)
copying of the Software and Materials provided the
Supplier in accordance with the Agreement; and
(c)
sale of the products produced by the System in any
country, except to the extent that such losses, liabilities,
and costs arise as a result of the Purchaser’s breach of
GCC Clause 32.2.
32.2 Such indemnity shall not cover any use of the System,
including the Materials, other than for the purpose indicated
by or to be reasonably inferred from the Contract, any
infringement resulting from the use of the System, or any
products of the System produced thereby in association or
combination with any other goods or services not supplied by
the Supplier, where the infringement arises because of such
association or combination and not because of use of the
System in its own right.
32.3 Such indemnities shall also not apply if any claim of
infringement:
(a)
is asserted by a parent, subsidiary, or affiliate of the
Purchaser’s organization;
(b)
is a direct result of a design mandated by the
Section IV. General Conditions of Contract
109
Purchaser’s Technical Requirements and the possibility
of such infringement was duly noted in the Supplier’s
Bid; or
(c)
results from the alteration of the System, including the
Materials, by the Purchaser or any persons other than
the Supplier or a person authorized by the Supplier.
32.4 If any proceedings are brought or any claim is made against
the Purchaser arising out of the matters referred to in GCC
Clause 32.1, the Purchaser shall promptly give the Supplier
notice of such proceedings or claims, and the Supplier may at
its own expense and in the Purchaser’s name conduct such
proceedings or claim and any negotiations for the settlement
of any such proceedings or claim.
If the Supplier fails to notify the Purchaser within twentyeight (28) days after receipt of such notice that it intends to
conduct any such proceedings or claim, then the Purchaser
shall be free to conduct the same on its own behalf. Unless
the Supplier has so failed to notify the Purchaser within the
twenty-eight (28) days, the Purchaser shall make no
admission that may be prejudicial to the defense of any such
proceedings or claim. The Purchaser shall, at the Supplier’s
request, afford all available assistance to the Supplier in
conducting such proceedings or claim and shall be
reimbursed by the Supplier for all reasonable expenses
incurred in so doing.
32.5 The Purchaser shall indemnify and hold harmless the
Supplier and its employees, officers, and Subcontractors
from and against any and all losses, liabilities, and costs
(including losses, liabilities, and costs incurred in defending
a claim alleging such a liability) that the Supplier or its
employees, officers, or Subcontractors may suffer as a result
of any infringement or alleged infringement of any
Intellectual Property Rights arising out of or in connection
with any design, data, drawing, specification, or other
documents or materials provided to the Supplier in
connection with this Contract by the Purchaser or any
persons (other than the Supplier) contracted by the
Purchaser, except to the extent that such losses, liabilities,
and costs arise as a result of the Supplier’s breach of GCC
Clause 32.8.
32.6 Such indemnity shall not cover
110
Section IV. General Conditions of Contract
(a)
any use of the design, data, drawing, specification, or
other documents or materials, other than for the
purpose indicated by or to be reasonably inferred from
the Contract;
(b)
any infringement resulting from the use of the design,
data, drawing, specification, or other documents or
materials, or any products produced thereby, in
association or combination with any other Goods or
Services not provided by the Purchaser or any other
person contracted by the Purchaser, where the
infringement arises because of such association or
combination and not because of the use of the design,
data, drawing, specification, or other documents or
materials in its own right.
32.7 Such indemnities shall also not apply:
(a)
if any claim of infringement is asserted by a parent,
subsidiary, or affiliate of the Supplier’s organization;
(b)
to the extent that any claim of infringement is caused
by the alteration, by the Supplier, or any persons
contracted by the Supplier, of the design, data,
drawing, specification, or other documents or materials
provided to the Supplier by the Purchaser or any
persons contracted by the Purchaser.
32.8 If any proceedings are brought or any claim is made against
the Supplier arising out of the matters referred to in GCC
Clause 32.5, the Supplier shall promptly give the Purchaser
notice of such proceedings or claims, and the Purchaser may
at its own expense and in the Supplier’s name conduct such
proceedings or claim and any negotiations for the settlement
of any such proceedings or claim. If the Purchaser fails to
notify the Supplier within twenty-eight (28) days after receipt
of such notice that it intends to conduct any such proceedings
or claim, then the Supplier shall be free to conduct the same
on its own behalf. Unless the Purchaser has so failed to
notify the Supplier within the twenty-eight (28) days, the
Supplier shall make no admission that may be prejudicial to
the defense of any such proceedings or claim. The Supplier
shall, at the Purchaser’s request, afford all available
assistance to the Purchaser in conducting such proceedings
or claim and shall be reimbursed by the Purchaser for all
reasonable expenses incurred in so doing.
Section IV. General Conditions of Contract
33. Limitation of
Liability
111
33.1 Provided the following does not exclude or limit any
liabilities of either party in ways not permitted by applicable
law:
(a)
the Supplier shall not be liable to the Purchaser,
whether in contract, tort, or otherwise, for any indirect
or consequential loss or damage, loss of use, loss of
production, or loss of profits or interest costs, provided
that this exclusion shall not apply to any obligation of
the Supplier to pay liquidated damages to the
Purchaser; and
(b)
the aggregate liability of the Supplier to the Purchaser,
whether under the Contract, in tort or otherwise, shall
not exceed the total Contract Price, provided that this
limitation shall not apply to any obligation of the
Supplier to indemnify the Purchaser with respect to
intellectual property rights infringement.
G. RISK DISTRIBUTION
34. Transfer of
Ownership
34.1 With the exception of Software and Materials, the ownership
of the Information Technologies and other Goods shall be
transferred to the Purchaser at the time of Delivery or
otherwise under terms that may be agreed upon and specified
in the Contract Agreement.
34.2 Ownership and the terms of usage of the Software and
Materials supplied under the Contract shall be governed by
GCC Clause 15 (Copyright) and any elaboration in the
Technical Requirements.
34.3 Ownership of the Supplier’s Equipment used by the Supplier
and its Subcontractors in connection with the Contract shall
remain with the Supplier or its Subcontractors.
35. Care of the
System
35.1 The Purchaser shall become responsible for the care and
custody of the System or Subsystems upon their Delivery.
The Purchaser shall make good at its own cost any loss or
damage that may occur to the System or Subsystems from
any cause from the date of Delivery until the date of
Operational Acceptance of the System or Subsystems,
pursuant to GCC Clause 27 (Commissioning and Operational
Acceptance), excepting such loss or damage arising from
acts or omissions of the Supplier, its employees, or
112
Section IV. General Conditions of Contract
subcontractors.
35.2 If any loss or damage occurs to the System or any part of the
System by reason of:
(a)
(insofar as they relate to the country where the Project
Site is located) nuclear reaction, nuclear radiation,
radioactive contamination, a pressure wave caused by
aircraft or other aerial objects, or any other occurrences
that an experienced contractor could not reasonably
foresee, or if reasonably foreseeable could not
reasonably make provision for or insure against, insofar
as such risks are not normally insurable on the
insurance market and are mentioned in the general
exclusions of the policy of insurance taken out under
GCC Clause 37;
(b)
any use not in accordance with the Contract, by the
Purchaser or any third party;
(c)
any use of or reliance upon any design, data, or
specification provided or designated by or on behalf of
the Purchaser, or any such matter for which the
Supplier has disclaimed responsibility in accordance
with GCC Clause 21.1.2,
the Purchaser shall pay to the Supplier all sums payable in
respect of the System or Subsystems that have achieved
Operational Acceptance, notwithstanding that the same be
lost, destroyed, or damaged. If the Purchaser requests the
Supplier in writing to make good any loss or damage to the
System thereby occasioned, the Supplier shall make good the
same at the cost of the Purchaser in accordance with GCC
Clause 39. If the Purchaser does not request the Supplier in
writing to make good any loss or damage to the System
thereby occasioned, the Purchaser shall either request a
change in accordance with GCC Clause 39, excluding the
performance of that part of the System thereby lost,
destroyed, or damaged, or, where the loss or damage affects a
substantial part of the System, the Purchaser shall terminate
the Contract pursuant to GCC Clause 41.1.
35.3 The Purchaser shall be liable for any loss of or damage to
any Supplier’s Equipment which the Purchaser has
authorized to locate within the Purchaser's premises for use
in fulfillment of Supplier's obligations under the Contract,
except where such loss or damage arises from acts or
Section IV. General Conditions of Contract
113
omissions of the Supplier, its employees, or subcontractors.
36. Loss of or
Damage to
Property;
Accident or
Injury to
Workers;
Indemnification
36.1 The Supplier and each and every Subcontractor shall abide
by the job safety, insurance, customs, and immigration
measures prevalent and laws in force in the Purchaser’s
Country.
36.2 Subject to GCC Clause 36.3, the Supplier shall indemnify
and hold harmless the Purchaser and its employees and
officers from and against any and all losses, liabilities and
costs (including losses, liabilities, and costs incurred in
defending a claim alleging such a liability) that the Purchaser
or its employees or officers may suffer as a result of the
death or injury of any person or loss of or damage to any
property (other than the System, whether accepted or not)
arising in connection with the supply, installation, testing,
and Commissioning of the System and by reason of the
negligence of the Supplier or its Subcontractors, or their
employees, officers or agents, except any injury, death, or
property damage caused by the negligence of the Purchaser,
its contractors, employees, officers, or agents.
36.3 If any proceedings are brought or any claim is made against
the Purchaser that might subject the Supplier to liability
under GCC Clause 36.2, the Purchaser shall promptly give
the Supplier notice of such proceedings or claims, and the
Supplier may at its own expense and in the Purchaser’s name
conduct such proceedings or claim and any negotiations for
the settlement of any such proceedings or claim. If the
Supplier fails to notify the Purchaser within twenty-eight
(28) days after receipt of such notice that it intends to
conduct any such proceedings or claim, then the Purchaser
shall be free to conduct the same on its own behalf. Unless
the Supplier has so failed to notify the Purchaser within the
twenty-eight (28) day period, the Purchaser shall make no
admission that may be prejudicial to the defense of any such
proceedings or claim. The Purchaser shall, at the Supplier’s
request, afford all available assistance to the Supplier in
conducting such proceedings or claim and shall be
reimbursed by the Supplier for all reasonable expenses
incurred in so doing.
36.4 The Purchaser shall indemnify and hold harmless the
Supplier and its employees, officers, and Subcontractors
from any and all losses, liabilities, and costs (including
losses, liabilities, and costs incurred in defending a claim
114
Section IV. General Conditions of Contract
alleging such a liability) that the Supplier or its employees,
officers, or Subcontractors may suffer as a result of the death
or personal injury of any person or loss of or damage to
property of the Purchaser, other than the System not yet
achieving Operational Acceptance, that is caused by fire,
explosion, or any other perils, in excess of the amount
recoverable from insurances procured under GCC Clause 37
(Insurances), provided that such fire, explosion, or other
perils were not caused by any act or failure of the Supplier.
36.5 If any proceedings are brought or any claim is made against
the Supplier that might subject the Purchaser to liability
under GCC Clause 36.4, the Supplier shall promptly give the
Purchaser notice of such proceedings or claims, and the
Purchaser may at its own expense and in the Supplier’s name
conduct such proceedings or claim and any negotiations for
the settlement of any such proceedings or claim. If the
Purchaser fails to notify the Supplier within twenty-eight
(28) days after receipt of such notice that it intends to
conduct any such proceedings or claim, then the Supplier
shall be free to conduct the same on its own behalf. Unless
the Purchaser has so failed to notify the Supplier within the
twenty-eight (28) days, the Supplier shall make no admission
that may be prejudicial to the defense of any such
proceedings or claim. The Supplier shall, at the Purchaser’s
request, afford all available assistance to the Purchaser in
conducting such proceedings or claim and shall be
reimbursed by the Purchaser for all reasonable expenses
incurred in so doing.
36.6 The party entitled to the benefit of an indemnity under this
GCC Clause 36 shall take all reasonable measures to
mitigate any loss or damage that has occurred. If the party
fails to take such measures, the other party’s liabilities shall
be correspondingly reduced.
37. Insurances
37.1 The Supplier shall at its expense take out and maintain in
effect, or cause to be taken out and maintained in effect,
during the performance of the Contract, the insurance set
forth below. The identity of the insurers and the form of the
policies shall be subject to the approval of the Purchaser,
who should not unreasonably withhold such approval.
(a)
Cargo Insurance During Transport
as applicable, 110 percent of the price of the
Section IV. General Conditions of Contract
115
Information Technologies and other Goods in a freely
convertible currency, covering the Goods from physical
loss or damage during shipment through receipt at the
Project Site.
(b)
Installation “All Risks” Insurance
as applicable, 110 percent of the price of the
Information Technologies and other Goods covering
the Goods at the site from all risks of physical loss or
damage (excluding only perils commonly excluded
under “all risks” insurance policies of this type by
reputable insurers) occurring prior to Operational
Acceptance of the System.
(c)
Third-Party Liability Insurance
On terms as specified in the SCC, covering bodily
injury or death suffered by third parties (including the
Purchaser’s personnel) and loss of or damage to
property (including the Purchaser’s property and any
Subsystems that have been accepted by the Purchaser)
occurring in connection with the supply and installation
of the Information System.
(d)
Automobile Liability Insurance
In accordance with the statutory requirements
prevailing in the Purchaser’s Country, covering use of
all vehicles used by the Supplier or its Subcontractors
(whether or not owned by them) in connection with the
execution of the Contract.
(e)
Other Insurance (if any), as specified in the SCC.
37.2 The Purchaser shall be named as co-insured under all
insurance policies taken out by the Supplier pursuant to GCC
Clause 37.1, except for the Third-Party Liability, and the
Supplier’s Subcontractors shall be named as co-insured
under all insurance policies taken out by the Supplier
pursuant to GCC Clause 37.1 except for Cargo Insurance
During Transport. All insurer’s rights of subrogation against
such co-insured for losses or claims arising out of the
performance of the Contract shall be waived under such
policies.
37.3 The Supplier shall deliver to the Purchaser certificates of
insurance (or copies of the insurance policies) as evidence
116
Section IV. General Conditions of Contract
that the required policies are in full force and effect.
37.4 The Supplier shall ensure that, where applicable, its
Subcontractor(s) shall take out and maintain in effect
adequate insurance policies for their personnel and vehicles
and for work executed by them under the Contract, unless
such Subcontractors are covered by the policies taken out by
the Supplier.
37.5 If the Supplier fails to take out and/or maintain in effect the
insurance referred to in GCC Clause 37.1, the Purchaser may
take out and maintain in effect any such insurance and may
from time to time deduct from any amount due the Supplier
under the Contract any premium that the Purchaser shall
have paid to the insurer or may otherwise recover such
amount as a debt due from the Supplier.
37.6 Unless otherwise provided in the Contract, the Supplier shall
prepare and conduct all and any claims made under the
policies effected by it pursuant to this GCC Clause 37, and
all monies payable by any insurers shall be paid to the
Supplier. The Purchaser shall give to the Supplier all such
reasonable assistance as may be required by the Supplier in
connection with any claim under the relevant insurance
policies. With respect to insurance claims in which the
Purchaser’s interest is involved, the Supplier shall not give
any release or make any compromise with the insurer without
the prior written consent of the Purchaser. With respect to
insurance claims in which the Supplier’s interest is involved,
the Purchaser shall not give any release or make any
compromise with the insurer without the prior written
consent of the Supplier.
38. Force Majeure
38.1 “Force Majeure” shall mean any event beyond the reasonable
control of the Purchaser or of the Supplier, as the case may
be, and which is unavoidable notwithstanding the reasonable
care of the party affected and shall include, without
limitation, the following:
(a)
war, hostilities, or warlike operations (whether a state
of war be declared or not), invasion, act of foreign
enemy, and civil war;
(b)
rebellion, revolution, insurrection, mutiny, usurpation
of civil or military government, conspiracy, riot, civil
commotion, and terrorist acts;
Section IV. General Conditions of Contract
117
(c)
confiscation,
nationalization,
mobilization,
commandeering or requisition by or under the order of
any government or de jure or de facto authority or ruler,
or any other act or failure to act of any local state or
national government authority;
(d)
strike, sabotage, lockout, embargo,
port congestion, lack of usual
transportation and communication,
shipwreck, shortage or restriction
epidemics, quarantine, and plague;
(e)
earthquake, landslide, volcanic activity, fire, flood or
inundation, tidal wave, typhoon or cyclone, hurricane,
storm, lightning, or other inclement weather condition,
nuclear and pressure waves, or other natural or physical
disaster;
(f)
failure, by the Supplier, to obtain the necessary export
permit(s) from the governments of the Country(s) of
Origin of the Information Technologies or other Goods,
or Supplier’s Equipment provided that the Supplier has
made all reasonable efforts to obtain the required
export permit(s), including the exercise of due
diligence in determining the eligibility of the System
and all of its components for receipt of the necessary
export permits.
import restriction,
means of public
industrial dispute,
of power supply,
38.2 If either party is prevented, hindered, or delayed from or in
performing any of its obligations under the Contract by an
event of Force Majeure, then it shall notify the other in
writing of the occurrence of such event and the
circumstances of the event of Force Majeure within fourteen
(14) days after the occurrence of such event.
38.3 The party who has given such notice shall be excused from
the performance or punctual performance of its obligations
under the Contract for so long as the relevant event of Force
Majeure continues and to the extent that such party’s
performance is prevented, hindered, or delayed. The Time
for Achieving Operational Acceptance shall be extended in
accordance with GCC Clause 40 (Extension of Time for
Achieving Operational Acceptance).
38.4 The party or parties affected by the event of Force Majeure
shall use reasonable efforts to mitigate the effect of the event
of Force Majeure upon its or their performance of the
118
Section IV. General Conditions of Contract
Contract and to fulfill its or their obligations under the
Contract, but without prejudice to either party’s right to
terminate the Contract under GCC Clause 38.6.
38.5 No delay or nonperformance by either party to this Contract
caused by the occurrence of any event of Force Majeure
shall:
(a)
constitute a default or breach of the Contract;
(b)
(subject to GCC Clauses 35.2, 38.3, and 38.4) give rise
to any claim for damages or additional cost or expense
occasioned by the delay or nonperformance,
if, and to the extent that, such delay or nonperformance is
caused by the occurrence of an event of Force Majeure.
38.6 If the performance of the Contract is substantially prevented,
hindered, or delayed for a single period of more than sixty
(60) days or an aggregate period of more than one hundred
and twenty (120) days on account of one or more events of
Force Majeure during the time period covered by the
Contract, the parties will attempt to develop a mutually
satisfactory solution, failing which, either party may
terminate the Contract by giving a notice to the other.
38.7 In the event of termination pursuant to GCC Clause 38.6, the
rights and obligations of the Purchaser and the Supplier shall
be as specified in GCC Clauses 41.1.2 and 41.1.3.
38.8 Notwithstanding GCC Clause 38.5, Force Majeure shall not
apply to any obligation of the Purchaser to make payments to
the Supplier under this Contract.
H. CHANGE IN CONTRACT ELEMENTS
39. Changes to the
System
39.1 Introducing a Change
39.1.1 Subject to GCC Clauses 39.2.5 and 39.2.7, the
Purchaser shall have the right to propose, and
subsequently require, the Project Manager to order
the Supplier from time to time during the
performance of the Contract to make any change,
modification, addition, or deletion to, in, or from the
System (interchangeably called “Change”), provided
that such Change falls within the general scope of
the System, does not constitute unrelated work, and
Section IV. General Conditions of Contract
119
is technically practicable, taking into account both
the state of advancement of the System and the
technical compatibility of the Change envisaged
with the nature of the System as originally specified
in the Contract.
A Change may involve, but is not restricted to, the
substitution of updated Information Technologies
and related Services in accordance with
GCC Clause 23 (Product Upgrades).
39.1.2 The Supplier may from time to time during its
performance of the Contract propose to the
Purchaser (with a copy to the Project Manager) any
Change that the Supplier considers necessary or
desirable to improve the quality or efficiency of the
System. The Purchaser may at its discretion approve
or reject any Change proposed by the Supplier.
39.1.3 Notwithstanding GCC Clauses 39.1.1 and 39.1.2, no
change made necessary because of any default of the
Supplier in the performance of its obligations under
the Contract shall be deemed to be a Change, and
such change shall not result in any adjustment of the
Contract Price or the Time for Achieving
Operational Acceptance.
39.1.4 The procedure on how to proceed with and execute
Changes is specified in GCC Clauses 39.2 and 39.3,
and further details and sample forms are provided in
the Sample Forms Section in the Bidding
Documents.
39.1.5 Moreover, the Purchaser and Supplier will agree,
during development of the Project Plan, to a date
prior to the scheduled date for Operational
Acceptance, after which the Technical Requirements
for the System shall be “frozen.” Any Change
initiated after this time will be dealt with after
Operational Acceptance.
39.2 Changes Originating from Purchaser
39.2.1 If the Purchaser proposes a Change pursuant to GCC
Clauses 39.1.1, it shall send to the Supplier a
“Request for Change Proposal,” requiring the
Supplier to prepare and furnish to the Project
120
Section IV. General Conditions of Contract
Manager as soon as reasonably practicable a
“Change Proposal,” which shall include the
following:
(a) brief description of the Change;
(b) impact on the Time for Achieving Operational
Acceptance;
(c) detailed estimated cost of the Change;
(d) effect on Functional Guarantees (if any);
(e) effect on any other provisions of the Contract.
39.2.2 Prior to preparing and submitting the “Change
Proposal,” the Supplier shall submit to the Project
Manager an “Change Estimate Proposal,” which
shall be an estimate of the cost of preparing the
Change Proposal, plus a first approximation of the
suggested approach and cost for implementing the
changes. Upon receipt of the Supplier’s Change
Estimate Proposal, the Purchaser shall do one of the
following:
(a) accept the Supplier’s estimate with instructions
to the Supplier to proceed with the preparation of
the Change Proposal;
(b) advise the Supplier of any part of its Change
Estimate Proposal that is unacceptable and
request the Supplier to review its estimate;
(c) advise the Supplier that the Purchaser does not
intend to proceed with the Change.
39.2.3 Upon receipt of the Purchaser’s instruction to
proceed under GCC Clause 39.2.2 (a), the Supplier
shall, with proper expedition, proceed with the
preparation of the Change Proposal, in accordance
with GCC Clause 39.2.1. The Supplier, at its
discretion, may specify a validity period for the
Change Proposal, after which if the Purchaser and
Supplier has not reached agreement in accordance
with GCC Clause 39.2.6, then GCC Clause 39.2.7
shall apply.
39.2.4 The pricing of any Change shall, as far as
Section IV. General Conditions of Contract
121
practicable, be calculated in accordance with the
rates and prices included in the Contract. If the
nature of the Change is such that the Contract rates
and prices are inequitable, the parties to the Contract
shall agree on other specific rates to be used for
valuing the Change.
39.2.5 If before or during the preparation of the Change
Proposal it becomes apparent that the aggregate
impact of compliance with the Request for Change
Proposal and with all other Change Orders that have
already become binding upon the Supplier under this
GCC Clause 39 would be to increase or decrease the
Contract Price as originally set forth in Article 2
(Contract Price) of the Contract Agreement by more
than fifteen (15) percent, the Supplier may give a
written notice of objection to this Request for
Change Proposal prior to furnishing the Change
Proposal. If the Purchaser accepts the Supplier’s
objection, the Purchaser shall withdraw the proposed
Change and shall notify the Supplier in writing of its
acceptance.
The Supplier’s failure to so object to a Request for
Change Proposal shall neither affect its right to
object to any subsequent requested Changes or
Change Orders, nor affect its right to take into
account, when making such subsequent objection,
the percentage increase or decrease in the Contract
Price that any Change not objected to by the
Supplier represents.
39.2.6 Upon receipt of the Change Proposal, the Purchaser
and the Supplier shall mutually agree upon all
matters contained in the Change Proposal. Within
fourteen (14) days after such agreement, the
Purchaser shall, if it intends to proceed with the
Change, issue the Supplier a Change Order. If the
Purchaser is unable to reach a decision within
fourteen (14) days, it shall notify the Supplier with
details of when the Supplier can expect a decision. If
the Purchaser decides not to proceed with the
Change for whatever reason, it shall, within the said
period of fourteen (14) days, notify the Supplier
accordingly. Under such circumstances, the Supplier
shall be entitled to reimbursement of all costs
122
Section IV. General Conditions of Contract
reasonably incurred by it in the preparation of the
Change Proposal, provided that these do not exceed
the amount given by the Supplier in its Change
Estimate Proposal submitted in accordance with
GCC Clause 39.2.2.
39.2.7 If the Purchaser and the Supplier cannot reach
agreement on the price for the Change, an equitable
adjustment to the Time for Achieving Operational
Acceptance, or any other matters identified in the
Change Proposal, the Change will not be
implemented. However, this provision does not limit
the rights of either party under GCC Clause 6
(Settlement of Disputes).
39.3 Changes Originating from Supplier
If the Supplier proposes a Change pursuant to GCC
Clause 39.1.2, the Supplier shall submit to the Project
Manager a written “Application for Change Proposal,”
giving reasons for the proposed Change and including the
information specified in GCC Clause 39.2.1. Upon receipt of
the Application for Change Proposal, the parties shall follow
the procedures outlined in GCC Clauses 39.2.6 and 39.2.7.
However, should the Purchaser choose not to proceed or the
Purchaser and the Supplier cannot come to agreement on the
change during any validity period that the Supplier may
specify in its Application for Change Proposal, the Supplier
shall not be entitled to recover the costs of preparing the
Application for Change Proposal, unless subject to an
agreement between the Purchaser and the Supplier to the
contrary.
40. Extension of
Time for
Achieving
Operational
Acceptance
40.1 The time(s) for achieving Operational Acceptance specified
in the Schedule of Implementation shall be extended if the
Supplier is delayed or impeded in the performance of any of
its obligations under the Contract by reason of any of the
following:
(a)
any Change in the System as provided in GCC
Clause 39 (Change in the Information System);
(b)
any occurrence of Force Majeure as provided in GCC
Clause 38 (Force Majeure);
(c)
default of the Purchaser; or
Section IV. General Conditions of Contract
(d)
123
any other matter specifically mentioned in the Contract;
by such period as shall be fair and reasonable in all the
circumstances and as shall fairly reflect the delay or
impediment sustained by the Supplier.
40.2 Except where otherwise specifically provided in the
Contract, the Supplier shall submit to the Project Manager a
notice of a claim for an extension of the time for achieving
Operational Acceptance, together with particulars of the
event or circumstance justifying such extension as soon as
reasonably practicable after the commencement of such event
or circumstance. As soon as reasonably practicable after
receipt of such notice and supporting particulars of the claim,
the Purchaser and the Supplier shall agree upon the period of
such extension. In the event that the Supplier does not accept
the Purchaser’s estimate of a fair and reasonable time
extension, the Supplier shall be entitled to refer the matter to
the provisions for the Settlement of Disputes pursuant to
GCC Clause 6.
40.3 The Supplier shall at all times use its reasonable efforts to
minimize any delay in the performance of its obligations
under the Contract.
41. Termination
41.1 Termination for Purchaser’s Convenience
41.1.1 The Purchaser may at any time terminate the
Contract for any reason by giving the Supplier a
notice of termination that refers to this GCC
Clause 41.1.
41.1.2 Upon receipt of the notice of termination under GCC
Clause 41.1.1, the Supplier shall either as soon as
reasonably practical or upon the date specified in the
notice of termination
(a) cease all further work, except for such work as
the Purchaser may specify in the notice of
termination for the sole purpose of protecting
that part of the System already executed, or any
work required to leave the site in a clean and safe
condition;
(b) terminate all subcontracts, except those to be
assigned to the Purchaser pursuant to GCC
Clause 41.1.2 (d) (ii) below;
124
Section IV. General Conditions of Contract
(c) remove all Supplier’s Equipment from the site,
repatriate the Supplier’s and its Subcontractors’
personnel from the site, remove from the site any
wreckage, rubbish, and debris of any kind;
(d) in addition, the Supplier, subject to the payment
specified in GCC Clause 41.1.3, shall
(i)
deliver to the Purchaser the parts of the
System executed by the Supplier up to the
date of termination;
(ii)
to the extent legally possible, assign to the
Purchaser all right, title, and benefit of the
Supplier to the System, or Subsystem, as at
the date of termination, and, as may be
required by the Purchaser, in any
subcontracts concluded between the
Supplier and its Subcontractors;
(iii) deliver to the Purchaser all nonproprietary
drawings, specifications, and other
documents prepared by the Supplier or its
Subcontractors as of the date of
termination in connection with the System.
41.1.3 In the event of termination of the Contract under
GCC Clause 41.1.1, the Purchaser shall pay to the
Supplier the following amounts:
(a) the Contract Price, properly attributable to the
parts of the System executed by the Supplier as
of the date of termination;
(b) the costs reasonably incurred by the Supplier in
the removal of the Supplier’s Equipment from
the site and in the repatriation of the Supplier’s
and its Subcontractors’ personnel;
(c) any amount to be paid by the Supplier to its
Subcontractors in connection with the
termination of any subcontracts, including any
cancellation charges;
(d) costs incurred by the Supplier in protecting the
System and leaving the site in a clean and safe
condition pursuant to GCC Clause 41.1.2 (a); and
Section IV. General Conditions of Contract
125
(e) the cost of satisfying all other obligations,
commitments, and claims that the Supplier may
in good faith have undertaken with third parties
in connection with the Contract and that are not
covered by GCC Clauses 41.1.3 (a) through (d)
above.
41.2 Termination for Supplier’s Default
41.2.1
The Purchaser, without prejudice to any other
rights or remedies it may possess, may terminate
the Contract forthwith in the following
circumstances by giving a notice of termination and
its reasons therefore to the Supplier, referring to
this GCC Clause 41.2:
(a) if the Supplier becomes bankrupt or insolvent,
has a receiving order issued against it,
compounds with its creditors, or, if the Supplier
is a corporation, a resolution is passed or order is
made for its winding up (other than a voluntary
liquidation for the purposes of amalgamation or
reconstruction), a receiver is appointed over any
part of its undertaking or assets, or if the
Supplier takes or suffers any other analogous
action in consequence of debt;
(b) if the Supplier assigns or transfers the Contract
or any right or interest therein in violation of the
provision of GCC Clause 42 (Assignment); or
(c) if the Supplier, in the judgment of the Purchaser,
has engaged in corrupt, fraudulent, collusive,
coercive or obstructive practices, in competing
for or in executing the Contract, including but
not limited to willful misrepresentation of facts
concerning ownership of Intellectual Property
Rights in, or proper authorization and/or licenses
from the owner to offer, the hardware, software,
or materials provided under this Contract.
For the purposes of this Clause:
126
Section IV. General Conditions of Contract
(i)
“corrupt practice”1 is the offering, giving,
receiving or soliciting, directly or
indirectly, of anything of value to
influence improperly the actions of
another party;
(ii)
“fraudulent practice”2 is any act or
omission, including a misrepresentation,
that knowingly or recklessly misleads, or
attempts to mislead, a party to obtain a
financial or other benefit or to avoid an
obligation;
(iii) “collusive practice”3 is an arrangement
between two or more parties designed to
achieve an improper purpose, including to
influence improperly the actions of
another party;
(iv) “coercive practice”4 is impairing or
harming, or threatening to impair or harm,
directly or indirectly, any party or the
property of the party to influence
improperly the actions of a party;
(v)
“obstructive practice” is
(aa) deliberately destroying, falsifying,
altering or concealing of evidence
material to the investigation or
making
false
statements
to
investigators in order to materially
impede a Bank investigation into
allegations of a corrupt, fraudulent,
coercive or collusive practice; and/or
threatening, harassing or intimidating
any party to prevent it from
1
“Another party” refers to a public official acting in relation to the procurement process or contract
execution]. In this context, “public official” includes World Bank staff and employees of other
organizations taking or reviewing procurement decisions.
2
A “party” refers to a public official; the terms “benefit” and “obligation” relate to the procurement process
or contract execution; and the “act or omission” is intended to influence the procurement process or contract
execution.
3
“Parties” refers to participants in the procurement process (including public officials) attempting to
establish bid prices at artificial, non competitive levels.
4
A “party” refers to a participant in the procurement process or contract execution.
Section IV. General Conditions of Contract
127
disclosing its knowledge of matters
relevant to the investigation or from
pursuing the investigation; or
(bb) acts intended to materially impede
the exercise of the Bank’s inspection
and audit rights provided for under
Sub-Clause 9.8.
41.2.2 If the Supplier:
(a) has abandoned or repudiated the Contract;
(b) has without valid reason failed to commence
work on the System promptly;
(c) persistently fails to execute the Contract in
accordance with the Contract or persistently
neglects to carry out its obligations under the
Contract without just cause;
(d) refuses or is unable to provide sufficient
Materials, Services, or labor to execute and
complete the System in the manner specified in
the Agreed and Finalized Project Plan furnished
under GCC Clause 19 at rates of progress that
give reasonable assurance to the Purchaser that
the Supplier can attain Operational Acceptance
of the System by the Time for Achieving
Operational Acceptance as extended;
then the Purchaser may, without prejudice to any
other rights it may possess under the Contract, give a
notice to the Supplier stating the nature of the
default and requiring the Supplier to remedy the
same. If the Supplier fails to remedy or to take steps
to remedy the same within fourteen (14) days of its
receipt of such notice, then the Purchaser may
terminate the Contract forthwith by giving a notice
of termination to the Supplier that refers to this GCC
Clause 41.2.
41.2.3 Upon receipt of the notice of termination under GCC
Clauses 41.2.1 or 41.2.2, the Supplier shall, either
immediately or upon such date as is specified in the
notice of termination:
(a) cease all further work, except for such work as
128
Section IV. General Conditions of Contract
the Purchaser may specify in the notice of
termination for the sole purpose of protecting
that part of the System already executed or any
work required to leave the site in a clean and safe
condition;
(b) terminate all subcontracts, except those to be
assigned to the Purchaser pursuant to GCC
Clause 41.2.3 (d) below;
(c) deliver to the Purchaser the parts of the System
executed by the Supplier up to the date of
termination;
(d) to the extent legally possible, assign to the
Purchaser all right, title and benefit of the
Supplier to the System or Subsystems as at the
date of termination, and, as may be required by
the Purchaser, in any subcontracts concluded
between the Supplier and its Subcontractors;
(e) deliver to the Purchaser all drawings,
specifications, and other documents prepared by
the Supplier or its Subcontractors as at the date
of termination in connection with the System.
41.2.4 The Purchaser may enter upon the site, expel the
Supplier, and complete the System itself or by
employing any third party. Upon completion of the
System or at such earlier date as the Purchaser thinks
appropriate, the Purchaser shall give notice to the
Supplier that such Supplier’s Equipment will be
returned to the Supplier at or near the site and shall
return such Supplier’s Equipment to the Supplier in
accordance with such notice. The Supplier shall
thereafter without delay and at its cost remove or
arrange removal of the same from the site.
41.2.5 Subject to GCC Clause 41.2.6, the Supplier shall be
entitled to be paid the Contract Price attributable to
the portion of the System executed as at the date of
termination and the costs, if any, incurred in
protecting the System and in leaving the site in a
clean and safe condition pursuant to GCC
Clause 41.2.3 (a). Any sums due the Purchaser from
the Supplier accruing prior to the date of termination
shall be deducted from the amount to be paid to the
Section IV. General Conditions of Contract
129
Supplier under this Contract.
41.2.6 If the Purchaser completes the System, the cost of
completing the System by the Purchaser shall be
determined. If the sum that the Supplier is entitled to
be paid, pursuant to GCC Clause 41.2.5, plus the
reasonable costs incurred by the Purchaser in
completing the System, exceeds the Contract Price,
the Supplier shall be liable for such excess. If such
excess is greater than the sums due the Supplier
under GCC Clause 41.2.5, the Supplier shall pay the
balance to the Purchaser, and if such excess is less
than the sums due the Supplier under GCC
Clause 41.2.5, the Purchaser shall pay the balance to
the Supplier. The Purchaser and the Supplier shall
agree, in writing, on the computation described
above and the manner in which any sums shall be
paid.
41.3 Termination by Supplier
41.3.1 If:
(a) the Purchaser has failed to pay the Supplier any
sum due under the Contract within the specified
period, has failed to approve any invoice or
supporting documents without just cause
pursuant to the SCC, or commits a substantial
breach of the Contract, the Supplier may give a
notice to the Purchaser that requires payment of
such sum, with interest on this sum as stipulated
in GCC Clause 12.3, requires approval of such
invoice or supporting documents, or specifies the
breach and requires the Purchaser to remedy the
same, as the case may be. If the Purchaser fails
to pay such sum together with such interest, fails
to approve such invoice or supporting documents
or give its reasons for withholding such
approval, fails to remedy the breach or take steps
to remedy the breach within fourteen (14) days
after receipt of the Supplier’s notice; or
(b) the Supplier is unable to carry out any of its
obligations under the Contract for any reason
attributable to the Purchaser, including but not
limited to the Purchaser’s failure to provide
130
Section IV. General Conditions of Contract
possession of or access to the site or other areas
or failure to obtain any governmental permit
necessary for the execution and/or completion of
the System;
then the Supplier may give a notice to the Purchaser
of such events, and if the Purchaser has failed to pay
the outstanding sum, to approve the invoice or
supporting documents, to give its reasons for
withholding such approval, or to remedy the breach
within twenty-eight (28) days of such notice, or if
the Supplier is still unable to carry out any of its
obligations under the Contract for any reason
attributable to the Purchaser within twenty-eight (28)
days of the said notice, the Supplier may by a further
notice to the Purchaser referring to this GCC
Clause 41.3.1, forthwith terminate the Contract.
41.3.2 The Supplier may terminate the Contract
immediately by giving a notice to the Purchaser to
that effect, referring to this GCC Clause 41.3.2, if
the Purchaser becomes bankrupt or insolvent, has a
receiving order issued against it, compounds with its
creditors, or, being a corporation, if a resolution is
passed or order is made for its winding up (other
than a voluntary liquidation for the purposes of
amalgamation or reconstruction), a receiver is
appointed over any part of its undertaking or assets,
or if the Purchaser takes or suffers any other
analogous action in consequence of debt.
41.3.3 If the Contract is terminated under GCC
Clauses 41.3.1 or 41.3.2, then the Supplier shall
immediately:
(a) cease all further work, except for such work as
may be necessary for the purpose of protecting
that part of the System already executed, or any
work required to leave the site in a clean and
safe condition;
(b) terminate all subcontracts, except those to be
assigned to the Purchaser pursuant to
Clause 41.3.3 (d) (ii);
(c) remove all Supplier’s Equipment from the site
and repatriate the Supplier’s and its
Section IV. General Conditions of Contract
131
Subcontractor’s personnel from the site.
(d) In addition, the Supplier, subject to the payment
specified in GCC Clause 41.3.4, shall:
(i)
deliver to the Purchaser the parts of the
System executed by the Supplier up to the
date of termination;
(ii)
to the extent legally possible, assign to the
Purchaser all right, title, and benefit of the
Supplier to the System, or Subsystems, as
of the date of termination, and, as may be
required by the Purchaser, in any
subcontracts concluded between the
Supplier and its Subcontractors;
(iii) to the extent legally possible, deliver to the
Purchaser all drawings, specifications, and
other documents prepared by the Supplier
or its Subcontractors as of the date of
termination in connection with the System.
41.3.4 If the Contract is terminated under GCC
Clauses 41.3.1 or 41.3.2, the Purchaser shall pay to
the Supplier all payments specified in GCC
Clause 41.1.3, and reasonable compensation for all
loss, except for loss of profit, or damage sustained
by the Supplier arising out of, in connection with, or
in consequence of such termination.
41.3.5 Termination by the Supplier pursuant to this GCC
Clause 41.3 is without prejudice to any other rights
or remedies of the Supplier that may be exercised in
lieu of or in addition to rights conferred by GCC
Clause 41.3.
41.4 In this GCC Clause 41, the expression “portion of the
System executed” shall include all work executed, Services
provided, and all Information Technologies, or other Goods
acquired (or subject to a legally binding obligation to
purchase) by the Supplier and used or intended to be used for
the purpose of the System, up to and including the date of
termination.
41.5 In this GCC Clause 41, in calculating any monies due from
the Purchaser to the Supplier, account shall be taken of any
132
Section IV. General Conditions of Contract
sum previously paid by the Purchaser to the Supplier under
the Contract, including any advance payment paid pursuant
to the SCC.
42. Assignment
42.l Neither the Purchaser nor the Supplier shall, without the
express prior written consent of the other, assign to any third
party the Contract or any part thereof, or any right, benefit,
obligation, or interest therein or thereunder, except that the
Supplier shall be entitled to assign either absolutely or by
way of charge any monies due and payable to it or that may
become due and payable to it under the Contract.
133
SECTION V. SPECIAL CONDITIONS OF CONTRACT (SCC)
135
Table of Clauses
A. Contract and Interpretation ..........................................................................................137
1.
2.
3.
4.
5.
6.
Definitions (GCC Clause 1) ....................................................................................137
Contract Documents (GCC Clause 2) .....................................................................137
Interpretation (GCC Clause 3) ................................................................................137
Notices (GCC Clause 4)..........................................................................................138
Governing Law (GCC Clause 5) .............................................................................138
Settlement of Disputes (GCC Clause 6) .................................................................138
B. Subject Matter of Contract ............................................................................................139
7.
8.
9.
10.
Scope of the System (GCC Clause 7) .....................................................................139
Time for Commencement and Operational Acceptance (GCC Clause 8) ..............139
Supplier’s Responsibilities (GCC Clause 9) ...........................................................139
Purchaser’s Responsibilities (GCC Clause 10).......................................................139
C. Payment............................................................................................................................139
11.
12.
13.
14.
Contract Price (GCC Clause 11) .............................................................................139
Terms of Payment (GCC Clause 12) ......................................................................140
Securities (GCC Clause 13) ....................................................................................141
Taxes and Duties (GCC Clause 14) ........................................................................142
D. Intellectual Property .......................................................................................................142
15.
16.
17.
Copyright (GCC Clause 15) ....................................................................................142
Software License Agreements (GCC Clause 16) ....................................................142
Confidential Information (GCC Clause 17) ............................................................143
E. Supply, Installation, Testing, Commissioning, and Acceptance of the System .........143
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
Representatives (GCC Clause 18) ..........................................................................143
Project Plan (GCC Clause 19) ................................................................................144
Subcontracting (GCC Clause 20)............................................................................145
Design and Engineering (GCC Clause 21) .............................................................145
Procurement, Delivery, and Transport (GCC Clause 22) .......................................145
Product Upgrades (GCC Clause 23) .......................................................................146
Implementation, Installation, and Other Services (GCC Clause 24) ......................146
Inspections and Tests (GCC Clause 25) .................................................................146
Installation of the System (GCC Clause 26) ...........................................................146
Commissioning and Operational Acceptance (GCC Clause 27) ............................146
F. Guarantees and Liabilities ..............................................................................................147
28.
29.
30.
31.
32.
Operational Acceptance Time Guarantee (GCC Clause 28)...................................147
Defect Liability (GCC Clause 29)...........................................................................147
Functional Guarantees (GCC Clause 30) ................................................................147
Intellectual Property Rights warranty (GCC Clause 31) ........................................148
Intellectual Property Rights Indemnity (GCC Clause 32).......................................148
136
Section V. Special Conditions of Contract
33. Limitation of Liability (GCC Clause 33) ................................................................148
G. Risk Distribution .............................................................................................................148
34. Transfer of Ownership (GCC Clause 34) ...............................................................148
35. Care of the System (GCC Clause 35) .....................................................................148
36. Loss of or Damage to Property; Accident or Injury to Workers; Indemnification
(GCC Clause 36) .....................................................................................................148
37. Insurances (GCC Clause 37) ...................................................................................148
38. Force Majeure (GCC Clause 38) ............................................................................149
H. Change in Contract Elements ........................................................................................149
39.
40.
41.
42.
Changes to the System (GCC Clause 39) ...............................................................149
Extension of Time for Achieving Operational Acceptance (GCC Clause 40) .......149
Termination (GCC Clause 41) ................................................................................149
Assignment (GCC Clause 42) .................................................................................149
Section V. Special Conditions of Contract
137
Special Conditions of Contract
The following Special Conditions of Contract (SCC) shall supplement or amend the General
Conditions of Contract (GCC). Whenever there is a conflict, the provisions of the SCC shall
prevail over those in the General Conditions of Contract. For the purposes of clarity, any
referenced GCC clause numbers are indicated in the left column of the SCC.
A. CONTRACT AND INTERPRETATION
1.
Definitions (GCC Clause 1)
GCC 1.1 (a) (ix)
The applicable edition of the Procurement Guidelines is dated:
Procurement of Goods, Works and non-consulting services
under IBRD Loans and IDA Credits and Grants by the World
Bank Borrowers dated January 2011 (revised July 2014).
GCC 1.1 (b) (i)
The Purchaser is: Bangladesh Bank, represented by the Executive
Director (ICT)
GCC 1.1 (b) (ii)
The Project Manager is:
Systems Manager
IT Operation and Communication Department, 29th Floor,
Bangladesh Bank, Annex-2 Building, Head Office, Motijheel,
Dhaka, Bangladesh.
Telephone: +880-2-9530234, Fax: +880-2-9530481, Email:
sm.itocd@bb.org.bd; jalal.uddin@bb.org.bd.
The Purchaser’s Country is: Bangladesh.
GCC 1.1 (e) (i)
GCC 1.1 (e) (iii)
The Project Site(s) is/are: as specified in the Implementation Schedule
in the Technical Requirements Section.
GCC 1.1 (e) (x)
The Contract shall continue in force until the Information System and
all the Services have been provided unless the Contract is
terminated earlier in accordance with the terms set out in the
Contract.
GCC 1.1. (e) (xii) The Post- warranty Services Period is nil starting with the completion of
the warranty Period.
2.
GCC 2
Contract Documents (GCC Clause 2)
There are no Special Conditions of Contract applicable to GCC Clause
2.
3.
GCC 3.1.1
Interpretation (GCC Clause 3)
The Contract's governing language is English.
138
Section V. Special Conditions of Contract
4.
GCC 4.3
Notices (GCC Clause 4)
Address of the Project Manager:
Systems Manager
IT Operation and Communication Department, 29th Floor,
Bangladesh Bank, Annex-2 Building, Head Office, Motijheel,
Dhaka, Bangladesh.
Telephone: +880-2-9530234, Facsimile: +880-2-9530481,
Email: sm.itocd@bb.org.bd; jalal.uddin@bb.org.bd.
No Electronic Data Interchange (EDI) will be used.
5.
GCC 5.1
The Contract shall be interpreted in accordance with the laws of:
Bangladesh.
6.
GCC 6.1.4
Governing Law (GCC Clause 5)
Settlement of Disputes (GCC Clause 6)
The Appointing Authority for the Adjudicator is:
(a) if the Supplier is foreign (including a Joint Venture when at
least one partner is foreign):
International Chamber of Commerce.
(b) if the Supplier is a national of the Purchaser’s country
BIAC or President of the Institution of Engineers in
consultation with the Executive Director of the Bangladesh
Computer Council or Any individual mutually agreed by both
the Purchaser and the Bidder.
GCC 6.2.3
The rules of procedure for arbitration proceedings are:
If the Supplier is foreign (including a Joint Venture when at least one
partner is foreign): Arbitration proceedings shall be conducted in
accordance with the rules of arbitration of UNCITRAL.
If the Supplier is a national of the Purchaser's country: Any dispute
between the Purchaser and a Supplier arising in connection with
the present Contract shall be referred to arbitration in accordance
with the Arbitration Act (Act Number: 1 of 2001) of Bangladesh
as at present in force. The place of Arbitration shall be in Dhaka,
Bangladesh.
Section V. Special Conditions of Contract
139
B. SUBJECT MATTER OF CONTRACT
7.
Scope of the System (GCC Clause 7)
The Supplier’s obligations under the Contract will include the following
recurrent cost items, as identified in the Recurrent Cost tables in
the Supplier’s Bid: Nil
GCC 7.3
The Supplier agrees to supply spare parts required for the operation and
maintenance of the System, as stated below, for the three (03)
years beginning with Operational Acceptance. Moreover, the
price of such spare parts shall be those specified in the spare parts
price schedule submitted by the Suppler as part of its bid. These
prices shall include the purchase price for such spare parts and
other costs and expenses (including the Supplier’s fees) relating
to the supply of spare parts.
8.
Time for Commencement and Operational Acceptance (GCC Clause 8)
GCC 8.1
The Supplier shall commence work on the System within: Twenty One
(21) of days from the Effective Date of the Contract.
GCC 8.2
Operational Acceptance will occur on or before: Operational Acceptance
date consistent with the Implementation Schedule in the
Technical Requirements Section.
9.
GCC 9.9
The Supplier shall have the following additional responsibilities: none.
10.
GCC 10.12
Supplier’s Responsibilities (GCC Clause 9)
Purchaser’s Responsibilities (GCC Clause 10)
The Purchaser shall have the following additional responsibilities: none.
C. PAYMENT
11.
GCC 11.2 (b)
Contract Price (GCC Clause 11)
Adjustments to the Contract Price shall be as follows: none.
140
Section V. Special Conditions of Contract
12.
GCC 12.1
Terms of Payment (GCC Clause 12)
Subject to the provisions of GCC Clause 12 (Terms of Payment), the
Purchaser shall pay the Contract Price to the Supplier according
to the categories and in the manner specified below. Only the
categories Advance Payment and Complete System Integration
relate to the entire Contract Price. In other payment categories,
the term "total Contract Price" means the total cost of goods or
services under the specific payment category. Within each such
category, the Contract Implementation Schedule may trigger prorata payments for the portion of the total Contract Price for the
category corresponding to the goods or services actually
Delivered, Installed, or Operationally Accepted, at unit prices
and in the currencies specified in the Price Schedules of the
Contract Agreement.
(a)
Advance Payment
ten percent (10%) of the entire Contract Price, exclusive of all
Recurrent Costs, shall be paid against receipt of a claim
accompanied by the Advance Payment Security specified in
GCC Clause 13.2.
The Advance Payment Security should be from any Scheduled
Bank of Bangladesh or from any other Bank duly endorsed by
a Scheduled Bank of Bangladesh and in the form provided
with these documents. The security should be in the Bid
Currency.
(b)
Information Technologies, Materials, and other Goods, with the
exception of Custom Software and Custom Materials:
sixty percent (60%) of the total or pro-rata Contract Price for this
category against Delivery
ten percent (10%) of the same price against Installation
ten percent (10%) of the same price against Operational
Acceptance.
(c)
Custom Software and Custom Materials:
sixty percent (60%) of the total or pro-rata Contract Price for this
category against Installation
twenty percent (20%) of the same price against Operational
Acceptance.
Section V. Special Conditions of Contract
(d)
141
Services other than Training:
eighty percent (80%) of the pro-rata Contract Price for services
performed will be paid monthly in arrears, on submission and
Purchaser’s approval of invoices.
(e)
Training
thirty percent (30%) of the total Contract Price for training
services at the start of the full training program
fifty percent (50%) of the pro-rata Contract Price for training
services performed will be paid after completion of each training
on submission and approval of appropriate invoices.
(f)
Complete System Integration
ten percent (10%) of the entire Contract Price, exclusive of all
Recurrent Costs, as final payment against Operational
Acceptance of the System as an integrated whole.
GCC 12.3
The Purchaser shall pay to the Supplier interest on the delayed payments
at a rate of: Five (05) percentage on the local currency and two (02)
percentage on the foreign exchange per annum.
GCC 12.4
For Goods and Services supplied locally, the Purchaser will pay the
Supplier in Bangladesh Taka.
GCC 12.5
Payment for Goods supplied from outside the Purchaser’s Country shall
be in the form of an irrevocable letter of credit.
13.
Securities (GCC Clause 13)
GCC 13.2.1
The Supplier shall provide within twenty-eight (28) days of the
notification of Contract award an Advance Payment Security in
the amount and currency of the Advance Payment specified in
SCC for GCC Clause 12.1 above.
GCC 13.2.2
The reduction in value and expiration of the Advance Payment Security
are calculated as follows:
Half of the value of the security would be deemed as recovered
when all items under the package (hardware and software)
have been delivered, and the other half, when all these items
have been installed and tested by the Purchaser.
GCC 13.3.1
The Performance Security shall be denominated in US Dollars or
equivalent amount in a freely convertible currency for an
142
Section V. Special Conditions of Contract
amount equal to ten (10) percent of the Contract Price, excluding
any Recurrent Costs.
GCC 13.3.4
During the Warranty Period (i.e., after Operational Acceptance of the
System), the Performance Security shall be reduced to Two and
a half (2.5) percent of the Contract Price, excluding any
Recurrent Costs.
14.
GCC 14
Taxes and Duties (GCC Clause 14)
The Taxes and Duties Table under the Price Schedule shall be filled in
as detailed as possible. The Taxes and Duties, however, shall
not be considered in the Bid Evaluation. Applicable Taxes and
Duties shall be paid by the Purchaser against actual payment
receipt of a claim.
D. INTELLECTUAL PROPERTY
15.
Copyright (GCC Clause 15)
GCC 15.3
The Purchaser may assign, license, or otherwise voluntarily transfer its
contractual rights to use the Standard Software or elements of the
Standard Software, without the Supplier’s prior written consent,
under the following circumstances: “Successor organization”.
GCC 15.4
The Purchaser’s and Supplier’s rights and obligations with respect to
Custom Software or elements of the Custom Software are as
follows:
The Supplier’s right in relation to custom software will be limited to
the use in order to support the Purchaser.
GCC 15.5
No software escrow contract is required for the execution of the
Contract.
16.
GCC 16.1 (a)
(iii)
Software License Agreements (GCC Clause 16)
The Standard Software license shall be valid throughout the territory of
the Purchaser’s Country. The supplied software licenses shall
be registered through Regional Headquarters, under which
Bangladesh falls, of the global software vendors for ensuring
convenient upgrade facility and renewal (as and when
necessary).
Section V. Special Conditions of Contract
143
GCC 16.1 (a) (iv) Use of the software shall be subject to the following additional
restrictions: None.
GCC 16.1 (b) (ii) The Software license shall permit the Software to be used or copied for
use or transferred to a replacement computer provided the
replacement computer falls within approximately the same class
of machine and maintains approximately the same number of
users, if a multi-user machine.
GCC 16.1 (b)
(vi)
The Software license shall permit the Software to be disclosed to and
reproduced for use (including a valid sublicense) by support
service suppliers or their subcontractors, exclusively for such
suppliers or subcontractors in the performance of their support
service contracts subject to the same restrictions set forth in this
Contract.
GCC 16.1 (b)
(vii)
In addition to the persons specified in GCC Clause 16.1 (b) (vi), the
Software may be disclosed to, and reproduced for use by,
Purchaser’s authorized staff subject to the same restrictions as
are set forth in this Contract.
GCC 16.2
The Supplier’s right to audit the Standard Software will be subject to the
following terms:
The Purchaser will make available to the Supplier within seven (07) days
of a written request accurate and up-to-date records of the
number and location of copies, the number of authorized users,
or any other relevant data required to demonstrate use of the
Standard Software as per the license agreement.
17.
Confidential Information (GCC Clause 17)
GCC 17.1
There are no modifications to the confidentiality terms expressed in
GCC Clause 17.1.
GCC 17.7
The provisions of this GCC Clause 17 shall survive the termination, for
whatever reason, of the Contract for three (03) years.
E. SUPPLY, INSTALLATION, TESTING, COMMISSIONING, AND
ACCEPTANCE OF THE SYSTEM
18.
GCC 18.1
Representatives (GCC Clause 18)
The Purchaser’s Project Manager shall have the following additional
powers and / or limitations to his or her authority to represent the
144
Section V. Special Conditions of Contract
Purchaser in matters relating to the Contract: No additional
powers or limitations.
GCC 18.2.2
The Supplier’s Representative shall have the following additional
powers and / or limitations to his or her authority to represent the
Supplier in matters relating to the Contract: No additional powers
or limitations.
19.
GCC 19.1
Project Plan (GCC Clause 19)
Chapters in the Project Plan shall address the following subject:
(a)
(b)
(c)
(d)
(d)
Project Organization and Management Plan;
Delivery and Installation Plan;
Knowledge Transfer Plan;
Training Plan;
Pre-commissioning and Operational Acceptance Testing
Plan;
(e) warranty Service Plan;
(f) Task, Time, and Resource Schedules;
(g) Technical Support Plan.
Further details regarding the required contents of each of the above
chapters are contained in the Technical Requirements, Section
VI.
GCC 19.2
Within twenty-one (21) days from the Effective Date of the Contract, the
Supplier shall present a Project Plan to the Purchaser. The
Purchaser shall, within fourteen (14) days of receipt of the
Project Plan, notify the Supplier of any respects in which it
considers that the Project Plan does not adequately ensure that the
proposed program of work, proposed methods, and/or proposed
Information Technologies will satisfy the Technical Requirements
and/or the SCC (in this Clause 19.2 called “non-conformities”
below). The Supplier shall, within seven (07) days of receipt of
such notification, correct the Project Plan and resubmit to the
Purchaser. The Purchaser shall, within seven (07) days of
resubmission of the Project Plan, notify the Supplier of any
remaining non-conformities. This procedure shall be repeated as
necessary until the Project Plan is free from non-conformities.
When the Project Plan is free from non-conformities, the
Purchaser shall provide confirmation in writing to the Supplier.
This approved Project Plan (“the Agreed and Finalized Project
Plan”) shall be contractually binding on the Purchaser and the
Section V. Special Conditions of Contract
145
Supplier.
GCC 19.5
The Supplier shall submit to the Purchaser Monthly progress reports,
summarizing:
(i)
(ii)
(iii)
(iv)
(v)
(vi)
(vii)
20.
GCC 20
results accomplished during the prior period;
cumulative deviations to date from schedule of progress
milestones as specified in the Agreed and Finalized Project
Plan;
corrective actions to be taken to return to planned schedule
of progress; proposed revisions to planned schedule;
resources that the Supplier expects to be provided by the
Purchaser and/or actions to be taken by the Purchaser in
the next reporting period;
training participants test results;
monthly log of service calls and problem resolutions;
other issues or potential problems the Supplier foresees that
could impact on project progress and/or effectiveness.
Subcontracting (GCC Clause 20)
There are no Special Conditions of Contract applicable to GCC Clause
20.
21.
GCC 21.3.1
Design and Engineering (GCC Clause 21)
The Supplier shall prepare and furnish to the Project Manager the
following documents for which the Supplier must obtain the
Project Manager’s approval before proceeding with work on the
System or any Subsystem covered by the documents.
(i)
(ii)
detailed site surveys;
final Subsystem configurations
Customization Plan;
(iii) Training Plan.
22.
based
on
System
Procurement, Delivery, and Transport (GCC Clause 22)
GCC 22.4.3
The Supplier shall be free to use transportation through carriers
registered in any eligible country and shall obtain insurance from
any eligible source country.
GCC 22.5
The Supplier shall provide the Purchaser with shipping and other
146
Section V. Special Conditions of Contract
documentation requirements as follows:
(a) Original plus five (05) copies of Bill of Lading
(b) Original plus five (05) copies of Supplier’s invoice showing
goods’ description, quantity, unit price, total amount;
(c) Original plus five (05) copies of the packing list identifying
the contents of each package
(d) Original plus five (05) copies of manufacturer’s/supplier’s
warranty certificate
(e) Original plus five (05) copies of certificate of origin.
23.
GCC 23.4
Product Upgrades (GCC Clause 23)
The Supplier shall provide the Purchaser: with all new versions, releases,
and updates to all Standard Software during the warranty
Period, for free, as specified in the GCC.
24.
GCC 24
Implementation, Installation, and Other Services (GCC Clause 24)
There are no Special Conditions of Contract applicable to GCC Clause
24.
25.
GCC 25
Inspections and Tests (GCC Clause 25)
Testing and Quality assurance requirements shall conform to the
Technical Requirements.
26.
GCC 26
Installation of the System (GCC Clause 26)
There are no Special Conditions of Contract applicable to GCC Clause
26.
27.
Commissioning and Operational Acceptance (GCC Clause 27)
GCC 27.2.1
Operational Acceptance Testing shall be conducted in accordance with
the Operational Acceptance Testing Plan as accepted by the
Purchaser.
GCC 27.2.2
If the Operational Acceptance Test of the System, or Subsystem(s),
cannot be successfully completed within no more than ninety
Section V. Special Conditions of Contract
147
one (91) days from the date of Installation or any other period
agreed upon by the Purchaser and the Supplier, then GCC
Clause 27.3.5 (a) or (b) shall apply, as the circumstances may
dictate.
F. GUARANTEES AND LIABILITIES
28.
Operational Acceptance Time Guarantee (GCC Clause 28)
GCC 28.2
Liquidated damages shall be assessed at one half of one (0.5) percent per
week. The maximum liquidated damages are ten (10) percent of
the Contract Price, or relevant part of the Contract Price if the
liquidated damages apply to a Subsystem.
GCC 28.3
Liquidated damages shall be assessed only with respect to achieving
Operational Acceptance.
29.
Defect Liability (GCC Clause 29)
GCC 29.1
For Software, exceptions or limitations to the Supplier’s warranty
obligations shall be as follows: None.
GCC 29.3 (iii)
The Supplier warrants that the following items have been released to the
market for the following specific minimum time periods: No specific
minimum time requirements are established for this Contract other
than that the Information Technologies must have been previously
released to the market for at least three months.
GCC 29.4
The warranty Period (N) shall begin from the date of Operational
Acceptance of the System or Subsystem and extend for thirty six
(36) month.
GCC 29.10
During the warranty Period, the Supplier must commence the work
necessary to remedy defects or damage within the time as
indicated in the Technical Specification and in Service Levels.
30.
GCC 30
Functional Guarantees (GCC Clause 30)
There are no Special Conditions of Contract applicable to GCC Clause
30.
148
Section V. Special Conditions of Contract
31.
GCC 31
There are no Special Conditions of Contract applicable to GCC Clause
31.
32.
GCC 32
Intellectual Property Rights warranty (GCC Clause 31)
Intellectual Property Rights Indemnity (GCC Clause 32)
There are no Special Conditions of Contract applicable to GCC Clause
32.
33.
GCC 33
Limitation of Liability (GCC Clause 33)
There are no Special Conditions of Contract applicable to GCC
Clause 33.
G. RISK DISTRIBUTION
34.
GCC 34
There are no Special Conditions of Contract applicable to GCC Clause
34.
35.
GCC 35
36.
Transfer of Ownership (GCC Clause 34)
Care of the System (GCC Clause 35)
There are no Special Conditions of Contract applicable to GCC Clause
35.
Loss of or Damage to Property; Accident or Injury to Workers; Indemnification
(GCC Clause 36)
GCC 36
There are no Special Conditions of Contract applicable to GCC Clause
36.
37.
Insurances (GCC Clause 37)
GCC 37.1 (c)
The Supplier shall obtain Third-Party Liability Insurance in accordance
with the statutory requirements in Bangladesh. The Insurance
shall cover the period six weeks after contract signing date until
complete system integration date (approximately six months).
GCC 37.1 (e)
The Supplier shall obtain Worker’s Compensation/Employer’s Liability
Section V. Special Conditions of Contract
149
Insurance in accordance with the statutory requirements in
Bangladesh. The Insurance shall cover the period six weeks after
contract signing date until complete system integration date
(approximately six months).
38.
GCC 38
Force Majeure (GCC Clause 38)
There are no Special Conditions of Contract applicable to GCC Clause
38.
H. CHANGE IN CONTRACT ELEMENTS
39.
GCC 39
40.
GCC 40
Changes to the System (GCC Clause 39)
There are no Special Conditions of Contract applicable to GCC Clause
39.
Extension of Time for Achieving Operational Acceptance (GCC Clause 40)
There are no Special Conditions of Contract applicable to GCC Clause
40.
41.
GCC 41
There are no Special Conditions of Contract applicable to GCC
Clause 41.
42.
GCC 42
Termination (GCC Clause 41)
Assignment (GCC Clause 42)
There are no Special Conditions of Contract applicable to GCC
Clause 42.
151
SECTION VI. TECHNICAL REQUIREMENTS (INCLUDING
IMPLEMENTATION SCHEDULE)
153
Table of Contents: Technical Requirements
A. Background .....................................................................................................................155
0.1
0.2
0.3
The Purchaser..........................................................................................................155
Business Objectives of the Purchaser .....................................................................156
Acronyms Used in These Technical Requirements ................................................157
B. Business Function and Performance Requirements ....................................................158
1.1
1.2
1.3
Business Requirements to Be Met by the System ...................................................158
Functional Performance Requirements of the System ............................................158
Related Information Technology Issues and Initiatives ..........................................158
C. Technical Specifications .................................................................................................161
2.0
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
General Technical Requirements ............................................................................161
Computing Hardware Specifications ......................................................................162
Network and Communications Specifications ........................................................216
Software Specifications ..........................................................................................216
System Management, Administration, and Security Specifications .......................217
Service Specifications .............................................................................................217
Documentation Requirements .................................................................................220
Consumables and Other Recurrent Cost Items .......................................................221
Other Non-IT Goods ...............................................................................................221
D. Testing and Quality Assurance Requirements .............................................................223
3.1
3.2
3.3
Inspections ..............................................................................................................223
Pre-commissioning Tests ........................................................................................223
Operational Acceptance Tests .................................................................................223
E. Implementation Schedule ...............................................................................................224
1.1.
1.2.
1.3.
1.4.
1.5.
Implementation Schedule Table..............................................................................225
System Inventory Table (Supply and Installation Cost Items) ................................226
System Inventory Table (Recurrent Cost Items) (Not Used) ..................................229
Site Table(s) ............................................................................................................230
Table of Holidays and Other Non-Working Days ..................................................231
F. Required Format of Technical Bids ...............................................................................232
5.1
5.2
5.3
5.4
5.5
Description of Information Technologies, Materials, Other Goods, and Services .232
Item-by-Item Commentary on the Technical Requirements ...................................232
Preliminary Project Plan .........................................................................................232
Confirmation of Responsibility for Integration and Interoperability of Information
Technologies ...........................................................................................................233
Knowledge Transfer Plan........................................................................................233
G. Technical Responsiveness Checklist..............................................................................234
Technical Responsiveness Checklist ...............................................................................235
154
Section VI. Technical Requirements
6.1. Documentation Checklist ..........................................................................................236
6.2. Details of Requirements:...........................................................................................236
6.3. Computing Hardware and Software Requirements ..................................................237
6.4. Network Spine Switch: ...........................................................................................237
6.5. Network Leaf Switch Type-A: ................................................................................241
6.6. Network Leaf Switch Type-B .................................................................................246
6.7. Network Aggregation Switch..................................................................................250
6.8. Campus Distribution Switch ...................................................................................252
6.9. Server Farm Firewall ..............................................................................................254
6.10. Extranet Firewall .....................................................................................................258
6.11. Internet Firewall ......................................................................................................264
6.12. Application Load Balancer .....................................................................................269
6.13. Bandwidth Manager ................................................................................................270
6.14. Content Filter ..........................................................................................................273
6.15. WAN Router ...........................................................................................................275
6.16. Extranet Router .......................................................................................................278
6.17. Internet Router ........................................................................................................280
6.18. iSCSI WAN Router.................................................................................................282
6.19. Extranet Switch .......................................................................................................283
6.20. SAN Director Switch ..............................................................................................285
6.21. Software Specifications ..........................................................................................291
6.22. Business Application Software: Not applicable......................................................291
6.23. System Management, Administration, and Security Specifications .......................291
6.24. Service Specifications .............................................................................................291
6.25. Technical Training Specifications ..........................................................................292
6.26. Technical Support: ..................................................................................................293
6.27. Maintenance Service: ..............................................................................................294
6.28. Documentation Requirements .................................................................................294
H. Attachments .....................................................................................................................297
Attachment 1: Existing Information Systems / Information Technologies......................299
Attachment 2: Site Drawings and Site Survey Information .............................................301
Attachment 3: Available Training Facilities ....................................................................303
Attachment 4: Project and Corporate Management Structure .........................................305
Section VI. Technical Requirements
155
Technical Requirements
A. BACKGROUND
0.1
The Purchaser
0.1.1
Bangladesh Bank, the Central bank of the country, was established as a body
corporate through the Bangladesh Bank Order, 1972 (Presidents Order No.
127 of 1972) with effect from 16 December 1971. It is responsible for the
supervision of the scheduled banks and financial institutions and for the full
range of functions normally associated with Central Banks. In addition to the
Head Office activities and Head Office Branch activities, BB carries out
business activities in nine further branches including one additional branch in
Dhaka area. There are eight branches outside of Dhaka, which are located in
principal districts across Bangladesh.
0.1.2
The broad goals and core objectives of the Bangladesh Bank are:









to carry out effective and comprehensive regulation and supervision of the
country’s banks and financial institutions
to regulate the issue of currency and manage the reserves
to preserve the value of the Bangladesh Taka
to provide an effective settlement and financial clearing system
to promote the developmental objectives of the country
to manage the country’s monetary and credit system to ensure stabilization
to promote the controlled development of the local financial markets
to provide meaningful economic analysis and research information
to act as the fiscal agent of the Government
0.1.3. Bangladesh Bank in consultation with the Ministry of Finance has undertaken
a project named as “Financial Sector Support Project” with the following
objectives:
(a) To strengthen the Bangladesh Bank to enable it to play its due role as the
country’s monetary authority and bank regulator and supervisor; and
(b) To enable Bangladesh Bank to lead the design and implementation of a
medium to long-term reform program for achieving a sound and efficient
financial system
0.1.4. The Financial Sector Support Project consists of the following three major
parts:



Supporting Financial Market Infrastructure;
Strengthening Regulatory Capacity and
Supporting Long Term Finance
156
Section VI. Technical Requirements
One of the major components of the Strengthening Financial Market
Infrastructure is capacity enhancement of the Bangladesh Bank. This
procurement is going to contribute to the capacity enhancement process.
0.1.5. Policy and overall coordination of the project rests on the Steering Committee
headed by the Governor of the Bank. The implementation of the project is
entrusted on the Project Director. Executive Director is the Project Director.
He is being assisted by the Financial Sector Support and Strategic Planning
Department, and a Program Office.
0.1.6. Procurement aspect against this project will be handled by the Bid/Tender
Evaluation Committee (TEC). The TEC will be assisted by the Technical SubCommittee headed by Executive Director (ICT). The contract shall be
awarded after obtaining approval of the Governor of Bangladesh Bank and the
Government of Bangladesh.
0.2
Business Objectives of the Purchaser
0.2.1
The goal of capacity enhancement is to increase the effectiveness of the user
and enable the user to produce more effective communications and reduce
dependencies on others for the completion of their assigned tasks.
0.2.2
This acquisition of network devices and related software will contribute to the
enhancement of existing automated systems. These will support the day to day
objectives and procedures of BB management. It will provide the Purchaser
personnel the tools, infrastructure and training to become skilled in the use of
modern technology.
0.2.3
This introduction of technology will start to enable the purchaser to build
technology skills that will enable the user to perform their work in a more
effective and efficient manner. The responsibilities of the affected personnel
will not change; however, the manner of working will be based on current
automated practices.
0.2.4
The main objective of this package is to install a completely new enterprise
network infrastructure for Bangladesh Bank on which existing Core Banking,
Treasury, Market Infrastructure, Enterprise Resource Planning, Enterprise
Data Warehouse, Online Credit Information Bureau, National Payment
Switch, Automated Clearing System, Integrated Supervision System, Foreign
Exchange Transaction Monitoring System, Emailing Service, Intranet based
services and other in-house application will run. There are Local Area
Network (LAN) in all departments of each BB buildings of Head Office. The
Head Office and all the branch offices are linked into a Wide Area Network
(WAN) using Fiber. Network devices will be deployed at data center (at
Motijheel, Dhaka), near data center (at Mirpur, Dhaka) and disaster recovery
site (at Rajshahi).
Section VI. Technical Requirements
0.3
157
Acronyms Used in These Technical Requirements
0.3.1
The following table provides a detailed listing with explanations of the
technical acronyms used in the course of this document.
Term
Explanation
bps
bits per second
cps
characters per second
DBMS
Database Management System
DOS
Disk Operating System
dpi
dots per inch
Ethernet
IEEE 802.3 Standard LAN protocol
GB
gigabyte
Hz
Hertz (cycles per second)
IEEE
Institute of Electrical and Electronics Engineers
ISO
International Standards Organization
KB
kilobyte
kVA
Kilovolt ampere
LAN
Local area network
lpi
lines per inch
lpm
lines per minute
MB
megabyte
MTBF
Mean time between failures
NIC
Network interface card
NOS
Network operating system
ODBC
Open Database Connectivity
OLE
Object Linking and Embedding
OS
Operating system
PCL
Printer Command Language
ppm
pages per minute
PS
PostScript -- Adobe page description language
158
Section VI. Technical Requirements
Term
Explanation
RAID
Redundant array of inexpensive disks
RAM
Random access memory
RISC
Reduced instruction-set computer
SCSI
Small Computer System Interface
SNMP
Simple Network Management Protocol
SQL
Structured Query Language
TCP/IP
Transmission Control Protocol / Internet Protocol
V
Volt
WLAN
Wireless LAN
B. BUSINESS FUNCTION AND PERFORMANCE REQUIREMENTS
1.1
1.2
Business Requirements to Be Met by the System
1.1.1
The business requirements that will be fulfilled by the introduction of new
standard hardware and software will be no different than that of the day to day
activities currently being performed by Bank personnel. The equipment will
enhance efficiency and effectiveness of the Information Systems.
1.1.2
There are no legal codes or regulatory issues that will be affected through the
use of these equipment.
Functional Performance Requirements of the System
1.2.1
1.3
The performance features of the equipment will be stated as part of the
detailed specification as this is an acquisition of technical equipment and
software.
Related Information Technology Issues and Initiatives
1.3.1
Bangladesh Bank has about 6,000 employees working in Head Office,
Motijheel, Bangladesh Bank Training Academy, Mirpur, Sadarghat Office,
Rajshashi Office, Bogra Office, Rangpur Office, Khulna Office, Barisal
Office, Chittagong Office, Sylhet Office and Mymensingh Office. Bangladesh
Bank has centralized ICT Infrastructure namely Data Canter (DC) and
Disaster Recovery Center (DRS) located in Dhaka to run centralized
Applications. All Branch Offices are connected from Branch Server Room
using WAN VPN Link having 2Mbps to 6Mbps bandwidth. Most of the
Servers for Office Automation are running on Windows 2003 and Windows
2008. BB Domain is using Windows 2008 based Active Directory solution
where branch Offices are in separate Organization Unit (OU) which are
Section VI. Technical Requirements
159
synchronizing in regular interval or trigger based. DNS and NTP service is
also running on Active Directory Servers which are also synchronizing.
Windows 2008 based Communicator are using for audio/video conferencing.
Microsoft Exchange 2007 based email solution (including OWA) connected
with Active Directory solution has Disaster recovery implementation at DRS.
Under centralized Application; Unix based Banking, ERP, Data Warehouse,
National Payment System, RTGS, Windows based Credit Information Bureau,
Automated Clearing House, Electronic Fund Transfer Network are running.
Also BB has Windows/Unix/Linux based desktop/web applications are
running. All users of Bangladesh Bank are using Windows XP/Windows 7
based Desktop/Laptop to use centralized Applications running from DC/DRS.
DHCP, File Server and Print Server are running on Windows 2008 based
Local Servers at DC, DRS and Branch Server rooms. All sort of Office
Automation and Related services need to migrate with the new Hardware and
latest Operating System and latest Application without any down-time and
data loss in three locations i.e., at Data Center, Near Data Center and Disaster
Recovery Site.
1.3.2
Bangladesh Bank intends to upgrade computing capacity and automate
remaining major business functionalities in phases. Accordingly Bangladesh
Bank is going to procure the following packages in addition to this package:
Package A
Three Data Center construction and renovation includes raised floor,
fire protection, Access Control, video surveillance, dehumidifier,
precision air-conditioner, data network, power system etc. to renovate
of existing two data centers and to construct one disaster recovery site.
Package B
Generator and Substation capacity expansion at Rajshahi and BBTA
includes Generator, Transformer, LT, PFI, AVR for Power House and
related electrical system for Rajshahi Office and BBTA located at
Mirpur, Dhaka
Package C
Server Solution includes servers, chassis etc. for three data centers.
Package D
Storage Solution includes storages, software and related items for three
data centers.
Package E
ePayment Gateway Solution includes payment gateway software and
related support.
Package F
Auditing Software includes software tool for audit team to audit
different application software of Bangladesh Bank.
Package G
Enterprise Service Bus includes software
1.3.3 Bangladesh Bank wishes to maintain internationally acceptable industry
standard interconnectivity between the application systems and existing all
available resources without any further major modification that incurs cost.
160
Section VI. Technical Requirements
Existing in-house application software will be interfaced or converted or
migrated to new systems considering optimum user friendliness.
1.3.4
The detailed specifications will reflect specific issues regarding compatibility.
Fulfillment of the specifications will ensure compatibility with information
technology systems that will be introduced in the latter stages of this project.
161
C. TECHNICAL SPECIFICATIONS
2.0
General Technical Requirements
2.0.1
Language Support: All information technologies must provide support for the
English language of the end-users. Specifically, all display technologies and
software must support the ISO character set and perform sorting accordingly.
2.0.2
DATES: All information technologies MUST properly display, calculate, and
transmit date data, including, but not restricted to 21st-Century date data.
Preferred date formats are:
DD/MM/YYYY
DD-MM-YYYY and
DD Month, YYYY
2.0.3
Electrical Power: All active (powered) equipment must operate on voltage
range: 220v +/- 20v, and frequency range: 50Hz +/- 2Hz. All active equipment
must include power plugs standard in Bangladesh.
2.0.4
Environmental: Unless otherwise specified, all equipment must operate in
environments of 10-45 degrees centigrade, 20-95 percent relative humidity,
and 0-40 grams per cubic meter of dust.
2.0.5
Safety:
2.0.5.1 Unless otherwise specified, all equipment must operate at noise levels
no greater than 55 decibels.
2.0.5.2 All electronic equipment that emits electromagnetic energy must be
certified as meeting US FCC class A or B or EN 55022 and EN 500821, or equivalent, emission standards.
2.0.6 The offered brand should be amongst the top ten (10), according to the most
recent assessment of a reputed global market analyst, such as ‘Gartner’.
2.0.7 Licensing for all software (where applicable) must be registered through
Regional Headquarters, under which Bangladesh falls, of the global software
vendors for ensuring convenient upgrade facility and renewal (as and when
necessary) by the time of operational acceptance test is completed. Service and
maintenance should be provided locally for the project period.
2.0.8 The Bidder should provide authorization letter(s) from the respective hardware
and software vendor(s).
162
Section VI. Technical Requirements
2.0.9. Table-A: Details of Requirements:
Component
Hardware
Software
Training
Installation
and
Implementation
Description
Routers, Switches, Firewalls, Content Filters etc.
As required as per Technical specification
Related training
As required as per Technical specification
Project Site(s)
All
All
All
All
The bidder must submit the bid for all the components with detailed specification as per
defined Technical, Financial, Legal & General requirements. In case of incomplete or
insufficient data the bid may be considered as non-responsive.
2.0.10. Table-B: Computing Hardware and Software Requirements
Description
Network Spine Switch (DC: 2 and NDC: 2)
Network Leaf Switch Type-A (DC: 2 and NDC: 2)
Network Leaf Switch Type-B (DC: 6 and NDC: 6)
Network Aggregation Switch (DC: 2 and NDC: 2)
Campus Distribution Switch for DC
Server Farm Firewall (DC: 2 and NDC: 2)
Extranet Firewall (DC: 2 and NDC: 2)
Internet Firewall (DC: 2 and NDC: 2)
Application Load Balancer (DC: 4 and NDC: 4)
Bandwidth Manager (DC: 2 and NDC: 2)
Content Filter (DC: 2 and NDC: 2)
WAN Router (DC: 2 and NDC: 2)
Extranet Router (DC: 2 and NDC: 2)
Internet Router (DC: 2 and NDC: 2)
iSCSI WAN Router (DC: 2 and NDC: 2)
Extranet Switch (DC: 2 and NDC: 2)
SAN Director Switch (DC: 2 and NDC: 2)
Email Security for Microsoft Exchange (DC: 2 and NDC: 2)
Notebook Computer
2.1
Minimum Quantity
4
4
12
4
2
4
4
4
8
4
4
4
4
4
4
4
4
30
Computing Hardware Specifications
2.1.1 Network Spine Switch:
Description
Quality
Certification
Brand
Model
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
To be mentioned by the bidder
Section VI. Technical Requirements
Description
Country of
Origin
Country of
Manufacture
163
Required Technical Specification
USA or EU
To be mentioned by the bidder
Proposed network device must be 19’’ rack mountable.
It is desirable that the network infrastructure is based on delivering front to back
airflow.
Offered device must have Redundant Power Supply Units (PSUs), Hot-swappable,
field-replaceable power supplies, 1:1 power redundancy.
Offered device must have N:1 fan module redundancy.
All components (including elements such as I/O modules, Expansion Module, power
supplies and fans) must be hot swappable with zero disruption to traffic forwarding
(Unicast or multicast).
In the event of a PSU failure, a single power supply must be able to support the
Hardware
network device.
features
Offered device must have minimum 34 x 40G QSFP ports with 24 QSFP Transceivers
which could extend up to 100 meters over Multi-mode Fiber. Bidders are allowed to
provide a solution to meet the requirement with two plus (2+) number of spine
switches at each Data Center.
Offered device must have Layer 2 hardware forwarding at minimum 2.7Tbps. Bidders
are allowed to meet the requirement by providing additional number of spine switches.
Offered switches should have the option to operate in single switch fabric Software
Driven Network Spine mode.
All the software and licenses required for the Single Fabric Software Driven Network
Mode should be included.
Offered device must have Line-rate traffic throughput on all ports at Layer 2.
Offered device must be able to act as a Spine switch on a Software Driven Network
Environment and can scale up to minimum 34 Leaf switches.
Single Fabric with multiple spine switches should be expandable to 10,000+ 10Gbps
Scalability
ports.
Offered device must allow building very large L2 domain using Multi-Path Ethernet
technologies scalable to minimum 10+ Tbps of switching capacity.
Offered device should be part of the SDN fabric and should support the following
features.
The switch fabric should support Layer 2 multipathing using ECMP
The SDN fabric should support Low and consistent latency through the whole Fabric
The solution consists of a spine-leaf architecture.
General
The Fabric downlinks from this switch to the Leaf switches should be based on 40GE
Feature
of links
Software
The solution must support Multi-Tenancy
Driven
The fabric architecture must be based on hardware VXLAN overlays to provide
Network
logical topologies that are abstracted from the physical infrastructure with no
performance penalty or similar solution with the same capability.
This Fabric must be highly programmable through open source APIs from a central
management point which exposes all the networking components, tenants and policies
via an object model to which the virtualization administrator can write REST calls.
The centralized management point can be integrated with major industry software
164
Description
Section VI. Technical Requirements
Required Technical Specification
management / cloud tools to automate end users’ service requests.
The Switch Fabric must support Auto-provisioning based on Application Requirement
and policy based forwarding networking.
All the fabric devices need to be auto-provisioned based on the application
requirement pushed down from the controller.
The proposed network solution must allow application architect (tenant) to define
policies, which control the network interaction between the different components of
his/her application, without any constraint imposed by routing/bridging boundaries.
Policies define which workload can work with which workload and through which
services (load balancing, firewalling).
With the proposed architecture the network infrastructure becomes a stateless element
whose behavior in interconnecting workloads is defined by the policies. The time to
deploy a new application is shortened because new policies can be applied and
removed in minutes instead of days.
The proposed integration solution between overlay and underlay must provide
granular visibility, and telemetry to shorten the time necessary for incident handling
and fault isolation or similar solution should be provided by using additional software
or hardware.
All workloads must be treated the same both virtual and physical, thus no bottleneck
(gateway) exists.
The whole Fabric (Virtual and Physical) must be managed as a single logical
component (single management point) while providing an option that requires
configuration of each node
Ability to implement Multi-Tenancy with totally separated policies between tenants.
Zero-touch installation and manage centralized at controller would be an advantage for
the bidders.
Traffic from hypervisors and from individual compute nodes is handled in the same
exact manner and benefits from the ability to completely virtualize the underlying
topology.
Offered device should support to connect any hypervisor like VMware, Microsoft,
RedHat to it without any different on design, solution and cost.
The fabric should support to decouple between End Point Location and Identity in
order for easy workload mobility.
The solution must have open API to integrate with 3rd party orchestrator or
management systems.
The controller must not directly involved in data plane forwarding, so a complete
failure or disconnection of all controllers elements in a cluster will not result in any
loss of existing datacenter functionality.
The policy inside the solution must be able to reuse the policy system-wide
Service device The solution should support to integrate with Layer 4-7 service devices like Firewall
Integration
Load balancers etc.; should have third party service device integration support.
The controller is the unified point of automation and management for the proposed
physical fabric, policy enforcement, and health monitoring.
The controller must be a single pane of glass to manage network policies for both
Controller
virtual, physical and cloud infrastructure based on application requirements.
Features
Automatic fabric discovery would be an advantage for the bidder.
The controller should be the unified GUI to do the image management and inventory
Section VI. Technical Requirements
Description
Fabric
Requirements
165
Required Technical Specification
for physical network fabric, if not please mention proposed solution.
The controller must run in the cluster mode with N+1 redundancy.
Controller integration with hypervisor management systems such as VMware,
Microsoft and Redhat.
The controller should support TACACS+, RADIUS, LDAP and/or Local
Authentication for integration into existing management system. Role-Based Access
Control is a must for the controller to be integrated into existing IT management
model.
The controller must have the Open NorthBound and SouthBound API.
The controller must support Standard OpenStack
The traffic flow and design for both physical and virtual workload must be consistent
and the same on logical point of view.
The proposed network physical fabric must support Spine/Leaf 2-tier topology, which
is the characteristic of hyper scale compute environments and is optimized for
east/west server-to-server traffic.
The proposed network physical fabric must support distributed default gateway on the
ToR/Leaf to optimize the traffic in DC.
The proposed network physical fabric must support decouple between endpoint id and
end point location. It will have the same ID when the end point moves between
ToR/Leaf.
No Flooding in IP control plane like ARP/GARP inside the tenants/Fabric would be an
advantage.
The proposed network physical fabric must support encapsulation normalization with
standard protocols like VXLAN
The proposed network physical fabric must support scale up and scale out without any
service interruption.
Offered device should support for visibility in hardware: can send the packet drops
and latency metrics to Controller to show to administrator would be an advantage.
The proposed network physical fabric must support prioritize the small packet inside
the fabric.
Hosts are required to connect to leaf nodes and the number of leaf switches depends
on the proposed hosts to be located at each data center.
All the connection to outside or existing network must be via leaf layer.
Hosts dual-attach to two leaf nodes via standard-based protocols would be an
advantage.
The proposed fabric must be able to support host communication to the fabric for
VLAN, VXLAN and NVGRE or similar protocols.
The proposed fabric must support direct connection to external network and/or WAN
as an option via static, OSPF or iBGP routing protocol, if not please mention the
solution.
The proposed fabric must support redistribute external/WAN routes via static, OSPF
or iBGP routing protocol into fabric if not please mention the solution.
The proposed fabric must support full host mobility such that any host can be moved
from any leaf node to any leaf node without any manual network configuration
involvement.
The proposed fabric should be able to support up to minimum 500 physical servers
(including hypervisor hosts) and scale to minimum 10,000 physical hosts, minimum
166
Description
Manufacturer
part number
Warranty
Section VI. Technical Requirements
Required Technical Specification
half a Million IP addresses and 50 tenants.
The proposed fabric must support variety of programmability: python, bash, netconf,
xml/json
The proposed fabric must support variety of programmability: python, bash, netconf,
xml/json or similar.
Bidder should submit BOQ of proposed device including the details of part numbers
and Manufacturer’s warranty.
Bidder should submit the required performance document for the proposed device.
Bidder should quote mentioning manufacturer’s warranty and part number and
minimum 3 (Three) years full replacement warranty should be provided for this unit
from the date of successful commissioning.
2.1.2 Network Leaf Switch Type-A:
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
General
Feature
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
It is desirable that the network infrastructure is based on delivering front to back
airflow.
Offered device must have Redundant Power Supply Units (PSUs), Hot-swappable,
field-replaceable power supplies, 1:1 power redundancy.
Offered device must have N:1 fan module redundancy.
All components (including elements such as I/O cards, Expansion Module, power
supplies and fans) must be hot swappable with zero disruption to traffic forwarding
(Unicast or multicast).
In the event of a PSU failure, a single (redundant) power supply must be able to
support the network device.
Offered device must have minimum 96 x 1/10GBase-T and 8 X 40 G QSFP ports.
Bidders are allowed to propose additional device to meet the requirement.
Offered device must include four QSFP Transceivers which could extend up to 100
meters over Multi-mode Fiber.
These switches should have the option to be deployed in standalone mode and also
single fabric Software Driven Network Leaf mode.
All the software and licenses for Single Fabric Software Driven Network Leaf mode
should be included.
Offered device must have Layer 2 hardware forwarding at minimum 2.5Tbps. Bidders
are allowed to provide additional device to meet the requirement.
Offered device must have Line-rate traffic throughput on all ports at Layer 2.
Offered device must have Line-rate traffic throughput on all ports at Layer 3
Section VI. Technical Requirements
Description
Scalability
Switch
features
Security
features
167
Required Technical Specification
Offered device must support minimum 80,000 MAC address table entries.
Offered device must allow building very large L2 domain using Multi-Path Ethernet
technologies scalable to 10+ Tbps of switching capacity.
Would be an advantage to support link aggregation across multi chassis for the servers
and other service devices.
Offered device must support Gigabit Ethernet (IEEE 802.3z, 802.3ab)
Offered device must support Ten Gigabit Ethernet (IEEE 802.3ae)
Offered device must support IEEE 802.1d - Spanning-Tree Protocol
Offered device must support IEEE 802.1w - Rapid Spanning Tree
Offered device must support IEEE 802.1s - Multiple Spanning Tree Protocol
Offered device must support IEEE 802.1q - VLAN encapsulation
Offered device must support IEEE 802.3ad - Link Aggregation Control Protocol
(LACP)
Offered device must support IEEE 802.1ab - Link Layer Discovery Protocol (LLDP)
Offered device must support auto-sensing and auto-negotiation (Link Speed/Duplex)
Offered device must support Static IP routing
Offered device must support Open Shortest Path First (OSPF) v2 (RFC 2328)
Offered device must support Protocol Independent Multicast Version 2 (PIMv2) sparse
mode, Source Specific Multicast (SSM), Multicast Source Discovery Protocol
(MSDP), and Internet Group Management Protocol Versions 2, and 3 (IGMP v2, and
v3)
Offered device must have Routed ports on platform interfaces, switch virtual interface
(SVI).
Offered device should support Virtual Route Forwarding (VRF): VRF-lite (IP VPN);
VRF-aware unicast; and BGP-, OSPF-, RIP-, and VRF-aware multicast
Offered device must support Jumbo Frame Size (9k)
Offered device must support IEEE 802.3ad Link Aggregation or equivalent capabilities
Ability to load balance across a logical bundle using the following algorithms would
be an advantage:
Source IP
Destination IP
Source and Destination IP
Source MAC
Destination MAC
Source and Destination MAC
TCP Port (destination and/or source)
UDP Port (destination and/or source)
Would be an advantage to support VXLAN (Bridging and Routing) as well as NVGRE
overlay encapsulation protocol in hardware to support multiple hypervisor deployment
in the Data Center
Offered device must support multiple privilege levels for remote access (e.g. console
or telnet access)
Offered device must support Remote Authentication Dial-In User Service (RADIUS)
and/or Terminal Access Controller Access Control System Plus (TACACS+) or
Equivalent.
Offered device must support AAA using RADIUS (RFC 2138 & 2139) and/or
TACACS+, enabling centralized control of the device and the ability to restrict
168
Description
QoS features
Management
features
General
Feature of
Software
Driven
Network
Section VI. Technical Requirements
Required Technical Specification
unauthorized users from altering the configuration or Equivalent.
Offered device must support Ingress ACLs (Standard & Extended) on Ethernet and
virtual Ethernet ports
Offered device must support Storm control (unicast, multicast, and broadcast)
Offered device must support IEEE 802.1p class-of-service (CoS) prioritization
Offered device must have Per-Port QoS configuration
Offered device must have CoS Trust
Offered device must have CoS-based egress queuing
Offered device must have Egress strict-priority queuing
Offered device must have per port virtual output queuing
Offered device must support Egress port-based scheduling: Weighted Round-Robin
(WRR)
Offered device must have ACL-based QoS classification (Layers 2, 3, and 4)
Offered device must provide management using 10/100/1000-Mbps management or
console ports
Offered device must have CLI-based console to provide detailed out-of-band
management
Offered device must have In-band switch management
Offered device must support Secure Shell Version 2 (SSHv2), Telnet & SNMPv1, v2,
and v3
Offered device must support AAA, AAA with RBAC, Radius, TACACS+ for user
authentication or Equivalent.
Offered device must have Switched Port Analyzer (SPAN) on physical, PortChannel,
VLAN, and Fiber Channel interfaces or equivalent.
Offered device should be part of the SDN fabric and should support the following
features.
The switch fabric should support Layer 2 multipathing using ECMP
The SDN fabric should support Low and consistent latency through the whole Fabric
The solution consists of spine-leaf architecture and this switch should act as a leaf.
The Fabric uplinks to the spine switches should be based on 40GE links. Minimum of
2 x 40G uplinks should be available. All the cables and accessories should be
provided.
The solution must support Multi-Tenancy
The fabric architecture must be based on hardware VXLAN overlays to provide logical
topologies that are abstracted from the physical infrastructure with no performance
penalty or similar solution with the same capability.
This Fabric must be highly programmable through open source APIs from a central
management point which exposes all the networking components, tenants and policies
via an object model to which the virtualization administrator can write REST calls.
The centralized management point can be integrated with major industry software
management / cloud tools to automate end users’ service requests.
The Switch Fabric supports Auto-provisioning based on Application Requirement and
policy based forwarding networking.
All the fabric devices need to be auto-provisioned based on the application
requirement pushed down from the controller.
The proposed network solution must allow application architect (tenant) to define
policies, which control the network interaction between the different components of
Section VI. Technical Requirements
Description
169
Required Technical Specification
his/her application, without any constraint imposed by routing/bridging boundaries.
Policies define which workload can work with which workload and through which
services (load balancing, firewalling).
With the proposed architecture the network infrastructure becomes a stateless element
whose behavior in interconnecting workloads is defined by the policies. The time to
deploy a new application is shortened because new policies can be applied and
removed in minutes instead of days.
The proposed integration solution between overlay and underlay must provide granular
visibility, and telemetry to shorten the time necessary for incident handling and fault
isolation or similar solution should be provided by using additional software or
hardware.
All workloads must be treated the same both virtual and physical, thus no bottleneck
(gateway) exists.
The whole Fabric (Virtual and Physical) must be managed as a single logical
component (single management point) while providing an option that requires
configuration of each node
Ability to implement Multi-Tenancy with totally separated policies between tenants.
Zero-touch installation and manage centralized at controller.
Traffic from hypervisors and from individual compute nodes is handled in the same
exact manner and benefits from the ability to completely virtualize the underlying
topology.
Offered device should support to connect any hypervisor like VMware, Microsoft,
Redhat to it without any different on design, solution and cost.
The fabric should support to decouple between End Point Location and Identity in
order for easy workload mobility.
The solution must have open API to integrate with 3rd party orchestrator or
management systems.
The controller must not directly involved in data plane forwarding, so a complete
failure or disconnection of all controllers elements in a cluster will not result in any
loss of existing datacenter functionality.
The policy inside the solution must be able to reuse the policy system-wide
Service
device
Integration
The solution should support to integrate with Layer 4-7 service devices like Firewall
Load balancers etc. should have 3rd party service device integration support.
Controller
Features
The controller is the unified point of automation and management for the proposed
physical fabric, policy enforcement, and health monitoring.
The controller must be a single pane of glass to manage network policies for both
virtual, physical and cloud infrastructure based on application requirements.
Automatic fabric discovery would be an advantage.
The controller should be the unified GUI to do the image management and inventory
for physical network fabric, if not please mention proposed solution.
The controller must run in the cluster mode with N+1 redundancy.
Controller integration with hypervisor management systems such as VMware,
Microsoft and Redhat would be an advantage.
The controller should support TACACS+, RADIUS, LDAP and/or Local
Authentication for integration into existing management system. Role-Based Access
Control is a must for the controller to be integrated into existing IT management
170
Description
Fabric
Requirements
Manufacturer
part number
Section VI. Technical Requirements
Required Technical Specification
model.
The controller must have the Open NorthBound and SouthBound API.
The controller must support Standard OpenStack
The traffic flow and design for both physical and virtual workload must be consistent
and the same on logical point of view.
The proposed network physical fabric must support Spine/Leaf 2-tier topology, which
is the characteristic of hyper scale compute environments and is optimized for
east/west server-to-server traffic.
The proposed network physical fabric must support distributed default gateway on the
ToR/Leaf to optimize the traffic in DC.
The proposed network physical fabric must support decouple between endpoint id and
end point location. It will have the same ID when the end point moves between
ToR/Leaf.
No Flooding in IP control plane like ARP/GARP inside the tenants/Fabric would be an
advantage.
The proposed network physical fabric must support encapsulation normalization with
standard protocols like VXLAN
The proposed network physical fabric must support scale up and scale out without any
service interruption.
Offered device should support for visibility in hardware: can send the packet drops and
latency metrics to Controller to show to administrator would be an advantage.
The proposed network physical fabric must support prioritize the small packet inside
the fabric.
Hosts are required to connect to leaf nodes and the number of leaf switches depends on
the proposed hosts to be located at each data center.
All the connection to outside or existing network must be via leaf layer.
Hosts dual-attach to two leaf nodes via standard-based protocols would be an
advantage.
The proposed fabric must be able to support host communication to the fabric for
VLAN, VXLAN and NVGRE or similar protocols.
The proposed fabric must support direct connection to external network and/or WAN
as an option via static, OSPF or iBGP routing protocol, if not please mention the
solution.
The proposed fabric must support redistribute external/WAN routes via static, OSPF or
iBGP routing protocol into fabric if not please mention the solution.
The proposed fabric must support full host mobility such that any host can be moved
from any leaf node to any leaf node without any manual network configuration
involvement.
The proposed fabric should be able to support up to minimum 500 physical servers
(including hypervisor hosts) and scale to minimum 10,000 physical hosts, minimum
half a Million IP addresses and 50 tenants.
The proposed fabric must support variety of programmability: python, bash, netconf,
xml/json
The proposed fabric must support variety of programmability: python, bash, netconf,
xml/json or similar.
Bidder should submit BOQ of proposed device including the details part numbers and
Manufacturer warranty.
Section VI. Technical Requirements
Description
Warranty
2.1.3
Required Technical Specification
Bidder should submit the required performance document for the proposed device.
Bidder should quote mentioning manufacturer’s warranty and part number and
minimum 3 (Three) years full replacement warranty should be provided for this unit
from the date of successful commissioning
Network Leaf Switch Type-B
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble/
Manufacture
General
Feature
Scalability
Switch
features
171
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
It is desirable that the network infrastructure is based on delivering front to back
airflow.
Offered device must have Redundant Power Supply Units (PSUs), Hot-swappable,
field-replaceable power supplies, 1:1 power redundancy.
Offered device must have N:1 fan module redundancy.
All components (including elements such as I/O cards, Expansion Module, power
supplies and fans) must be hot swappable with zero disruption to traffic forwarding
(Unicast or multicast).
In the event of a PSU failure, a single (redundant) power supply Must be able to
support the network device.
Offered device must have minimum 48 x 1/10 SFP+ and minimum 8 X 40 G QSFP
ports. Bidders can propose additional leaf switches to meet the requirement.
Offered device must Include four QSFP Transceivers which could extend up to 100
meters over Multi-mode Fiber.
These switches should have the option to be deployed in standalone mode and also
single fabric Software Driven Network Leaf mode.
All the software and licenses for Single Fabric Software Driven Network Mode should
be included.
Offered device must have Layer 2 hardware forwarding at minimum 1.6Tbps. Bidders
can propose additional leaf switches to meet the requirement.
Offered device must have Line-rate traffic throughput on all ports at Layer 2.
Offered device must have Line-rate traffic throughput on all ports at Layer 3
Offered device must support minimum 80,000 MAC address table entries.
Offered device must allow building very large L2 domain using Multi-Path Ethernet
technologies scalable to minimum 10+ Tbps of switching capacity.
Would be an advantage to support link aggregation across multi chassis for the servers
and other service devices.
Offered device must support Gigabit Ethernet (IEEE 802.3z, 802.3ab)
Offered device must support Ten Gigabit Ethernet (IEEE 802.3ae)
172
Description
Security
features
QoS features
Section VI. Technical Requirements
Required Technical Specification
Offered device must support IEEE 802.1d - Spanning-Tree Protocol
Offered device must support IEEE 802.1w - Rapid Spanning Tree
Offered device must support IEEE 802.1s - Multiple Spanning Tree Protocol
Offered device must support IEEE 802.1q - VLAN encapsulation
Offered device must support IEEE 802.3ad - Link Aggregation Control Protocol
(LACP)
Offered device must support IEEE 802.1ab - Link Layer Discovery Protocol (LLDP)
Offered device must support auto-sensing and auto-negotiation (Link Speed/Duplex)
Offered device must support Static IP routing
Offered device must support Open Shortest Path First (OSPF) v2 (RFC 2328)
Offered device must support Protocol Independent Multicast Version 2 (PIMv2)
sparse mode, Source Specific Multicast (SSM), Multicast Source Discovery Protocol
(MSDP), and Internet Group Management Protocol Versions 2, and 3 (IGMP v2, and
v3)
Offered device must have Routed ports on platform interfaces, switch virtual interface
(SVI).
Should support Virtual Route Forwarding (VRF): VRF-lite (IP VPN); VRF-aware
unicast; and BGP-, OSPF-, RIP-, and VRF-aware multicast
Offered device must support Jumbo Frame Size (9k)
Offered device must support IEEE 802.3ad Link Aggregation or equivalent
capabilities
Ability to load balance across a logical bundle using the following algorithms would
be an advantage:
Source IP
Destination IP
Source and Destination IP
Source MAC
Destination MAC
Source and Destination MAC
TCP Port (destination and/or source)
UDP Port (destination and/or source)
Would be an advantage to support VXLAN (Bridging and Routing) as well as
NVGRE overlay encapsulation protocol in hardware to support multiple hypervisor
deployment in the Data Center
Offered device must support multiple privilege levels for remote access (e.g. console
or telnet access)
Offered device must support Remote Authentication Dial-In User Service (RADIUS)
and/or Terminal Access Controller Access Control System Plus (TACACS+) or
Equivalent.
Offered device must support AAA using RADIUS (RFC 2138 & 2139) and/or
TACACS+, enabling centralized control of the device and the ability to restrict
unauthorized users from altering the configuration or Equivalent.
Offered device must support Ingress ACLs (Standard & Extended) on Ethernet and
virtual Ethernet ports
Offered device must support Storm control (unicast, multicast, and broadcast)
Offered device must support IEEE 802.1p class-of-service (CoS) prioritization
Offered device must have Per-Port QoS configuration
Section VI. Technical Requirements
Description
Management
features
General
Feature of
Software
Driven
Network
173
Required Technical Specification
Offered device must have CoS Trust
Offered device must have CoS-based egress queuing
Offered device must have Egress strict-priority queuing
Offered device must have per port virtual output queuing
Offered device must support Egress port-based scheduling: Weighted Round-Robin
(WRR)
Offered device must have ACL-based QoS classification (Layers 2, 3, and 4)
Offered device must provide management using 10/100/1000-Mbps management or
console ports
Offered device must have CLI-based console to provide detailed out-of-band
management
Offered device must have In-band switch management
Offered device must support Secure Shell Version 2 (SSHv2), Telnet & SNMPv1, v2,
and v3
Offered device must support AAA, AAA with RBAC, Radius, TACACS+ for user
authentication or Equivalent.
Offered device must have Switched Port Analyzer (SPAN) on physical, PortChannel,
VLAN, and Fiber Channel interfaces or equivalent.
This Device should be part of the SDN fabric and should support the following
features.
The switch fabric should support Layer 2 multipathing using ECMP
The SDN fabric should support Low and consistent latency through the whole Fabric
The solution consists of spine-leaf architecture and this switch should act as a leaf.
The Fabric uplinks to the spine switches should be based on minimum 40GE links.
Minimum of 2 x 40G uplinks should be available. All the cables and accessories
should be provided.
The solution MUST support Multi-Tenancy
The fabric architecture must be based on hardware VXLAN overlays to provide
logical topologies that are abstracted from the physical infrastructure with no
performance penalty or similar solution with the same capability.
This Fabric must be highly programmable through open source APIs from a central
management point which exposes all the networking components, tenants and policies
via an object model to which the virtualization administrator can write REST calls.
The centralized management point can be integrated with major industry software
management / cloud tools to automate end users’ service requests.
The Switch Fabric supports Auto-provisioning based on Application Requirement and
policy based forwarding networking.
All the fabric devices need to be auto-provisioned based on the application
requirement pushed down from the controller.
The proposed network solution must allow application architect (tenant) to define
policies, which control the network interaction between the different components of
his/her application, without any constraint imposed by routing/bridging boundaries.
Policies define which workload can work with which workload and through which
services (load balancing, firewalling).
With the proposed architecture the network infrastructure becomes a stateless element
whose behavior in interconnecting workloads is defined by the policies. The time to
deploy a new application is shortened because new policies can be applied and
174
Description
Section VI. Technical Requirements
Required Technical Specification
removed in minutes instead of days.
The proposed integration solution between overlay and underlay must provide
granular visibility, and telemetry to shorten the time necessary for incident handling
and fault isolation or similar solution should be provided by using additional software
or hardware.
All workloads must be treated the same both virtual and physical, thus no bottleneck
(gateway) exists.
The whole Fabric (Virtual and Physical) must be managed as a single logical
component (single management point) while providing an option that requires
configuration of each node
Ability to implement Multi-Tenancy with totally separated policies between tenants.
Zero-touch installation and manage centralized at controller would be an advantage for
the bidders.
Traffic from hypervisors and from individual compute nodes is handled in the same
exact manner and benefits from the ability to completely virtualize the underlying
topology.
Support to connect any hypervisor like VMware, Microsoft, Redhat to it without any
different on design, solution and cost would be an advantage for the bidders.
The fabric should support to decouple between End Point Location and Identity in
order for easy workload mobility.
The solution must have open API to integrate with 3rd party orchestrator or
management systems.
The controller must not directly involved in data plane forwarding, so a complete
failure or disconnection of all controllers elements in a cluster will not result in any
loss of existing datacenter functionality.
The policy inside the solution must be able to reuse the policy system-wide
Service device The solution should support to integrate with Layer 4-7 service devices like Firewall
Integration
Load balancers etc.; should have 3rd party service device integration support.
The controller is the unified point of automation and management for the proposed
physical fabric, policy enforcement, and health monitoring.
The controller must be a single pane of glass to manage network policies for both
virtual, physical and cloud infrastructure based on application requirements.
Automatic fabric discovery would be an advantage for the bidder.
The controller should be the unified GUI to do the image management and inventory
for physical network fabric, if not please mention proposed solution.
The controller must run in the cluster mode with N+1 redundancy.
Controller
Controller integration with hypervisor management systems such as VMware,
Features
Microsoft and Redhat would be an advantage for the bidder.
The controller should support TACACS+, RADIUS, LDAP and/or Local
Authentication for integration into existing management system. Role-Based Access
Control is a must for the controller to be integrated into existing IT management
model.
The controller must have the Open NorthBound and SouthBound API.
The controller must support Standard OpenStack
The traffic flow and design for both physical and virtual workload must be consistent
and the same on logical point of view.
Fabric
The proposed network physical fabric must support Spine/Leaf 2-tier topology, which
Section VI. Technical Requirements
Description
Requirements
Manufacturer
part number
Warranty
175
Required Technical Specification
is the characteristic of hyper scale compute environments and is optimized for
east/west server-to-server traffic.
The proposed network physical fabric must support distributed default gateway on the
ToR/Leaf to optimize the traffic in DC.
The proposed network physical fabric must support decouple between endpoint id and
end point location. It will have the same ID when the end point moves between
ToR/Leaf.
No Flooding in IP control plane like ARP/GARP inside the tenants/Fabric would be an
advantage.
The proposed network physical fabric must support encapsulation normalization with
standard protocols like VXLAN
The proposed network physical fabric must support scale up and scale out without any
service interruption.
Offered device should support for visibility in hardware: can send the packet drops
and latency metrics to Controller to show to administrator would be an advantage.
The proposed network physical fabric must support prioritize the small packet inside
the fabric.
Hosts are required to connect to leaf nodes and the number of leaf switches depends
on the proposed hosts to be located at each data center.
All the connection to outside or existing network must be via leaf layer.
Hosts dual-attach to two leaf nodes via standard-based protocols would be an
advantage.
The proposed fabric must be able to support host communication to the fabric for
VLAN, VXLAN and NVGRE or similar protocols.
The proposed fabric must support direct connection to external network and/or WAN
as an option via static, OSPF or iBGP routing protocol, if not please mention the
solution.
The proposed fabric must support redistribute external/WAN routes via static, OSPF
or iBGP routing protocol into fabric if not please mention the solution.
The proposed fabric must support full host mobility such that any host can be moved
from any leaf node to any leaf node without any manual network configuration
involvement.
The proposed fabric should be able to support up to minimum 500 physical servers
(including hypervisor hosts) and scale to minimum 10,000 physical hosts, minimum
half Million IP addresses and 50 tenants.
The proposed fabric must support variety of programmability: python, bash, netconf,
xml/json
The proposed fabric must support variety of programmability: python, bash, netconf,
xml/json or similar.
Bidder should submit BOQ of proposed device including the details part numbers and
Manufacturer warranty.
Bidder should submit the required performance document for the proposed device.
Bidder should quote mentioning manufacturer’s warranty and part number and
minimum 3 (Three) years full replacement warranty should be provided for this unit
from the date of successful commissioning
176
Section VI. Technical Requirements
2.1.4 Network Aggregation Switch
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Offered device should be highly performed fixed switch with wire rate Layer 2 and
Layer 3 throughput on all the ports on the chassis.
Offered device should have minimum of 24 x 10GE SFP/SFP+ transceiver based ports
Architecture and upgradeable to minimum 48 x 10GE ports on the same chassis.
Switch should include 2 Direct attach transceiver based 10G 7 meter cables, 15 multimode 10G transceivers. All the cables and accessories have to be provided.
Offered device should have dual redundant power source and redundant Fans
Switching capacity minimum 480 Gbps and upgradeable up to minimum 960 Gbps
Switching
Performance Forwarding Throughput minimum 360 Mpps and upgradeable up to minimum 720 Mpps
Layer 2 switch ports and VLAN trunks
IEEE 802.1Q VLAN encapsulation
Support for up to minimum 4096 VLANs
Rapid Spanning Tree (IEEE 802.1w compatible)
MSTP (IEEE 802.1s): 64 instances
Spanning Tree PortFast
Switch
Spanning Tree Root Guard
Layer 2
Spanning Tree Bridge Assurance
Services
Link Aggregation technology (up to 24 ports), If not please mention the provided
solution.
LACP: IEEE 802.3ad, IEEE 802.1ax
Advanced Link aggregation hashing based on Layer 2, 3, and 4 information
Jumbo frames on all ports (up to 9216 bytes)
Storm control (multicast and broadcast)
Layer 3 interfaces: Routed ports on interfaces, switch virtual interfaces (SVIs), Link
aggregation.
Minimum 24-way Equal-Cost Multipath (ECMP), if not please mention.
Switch
Minimum 4096 ACL entries
Layer
3
Routing protocols: Static, RIPv2, OSPF
Services
FHRP
ACL: Routed ACL with Layer 3 and 4 options to match ingress and egress ACLs
Jumbo frame support (up to 9216 bytes)
Ingress ACLs (standard and extended) on Ethernet
Security
Standard and extended Layer 3 to 4 ACLs include IPv4, Internet Control Message
features
Protocol (ICMP), TCP, and User Datagram Protocol (UDP)
VLAN-based ACLs (VACLs)
Section VI. Technical Requirements
Description
Management
features
Manufacture
r part
number
Warranty
177
Required Technical Specification
Port-based ACLs (PACLs)
Named ACLs
ACLs on virtual terminals (VTYs)
Dynamic Host Configuration Protocol ( DHCP) relay
Control Plane Policing (CoPP), if not please mention.
CLI-based console to provide detailed out-of-band management
In-band switch management
Switch management using 10/100/1000-Mbps management or console ports
SSHv2 and Telnet
SNMP agent - SNMPv1, SNMPv2, SNMPv3.
Bidder should submit BOQ of proposed device including the details part numbers and
Manufacturer warranty.
Bidder should submit the required performance document for the proposed device.
Bidder should quote mentioning manufacturer’s warranty and part number and
minimum 3 (Three) years full replacement warranty should be provided for this unit
from the date of successful commissioning.
2.1.5 Campus Distribution Switch
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
Enclosure Type
General
Features
Performance
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Rack-mountable Modular Chassis
The Switch should be modular at least 6 slots chassis switch
The Switch OS should be modular and open system/platform
The switch should support redundant switching engine for future requirement.
The switch OS can support third-party applications in parallel with Switch OS
Dual Hot-swappable power supplies
At least 96 x 1GE SFP ports available from day 1.
Minimum 96 number of 1G Optical Multi-Mode SFP modules should be included
with all the required cables and accessories.
At least 8 x 10 Gigabit SFP ports available from day 1.
Minimum 8 numbers of 10G Optical Multi-Mode SFP modules with all the required
cables and accessories.
Supervisor should support Minimum 550 Gbps Switching Capacity in single chassis.
Minimum 240 Mpps IPv4 forwarding capacity in single chassis.
Minimum 120 Mpps IPv6 forwarding capacity in single chassis.
Per-Slot Switching Capacity minimum 48 Gbps
IPv4 Routing Entries: Minimum 250,000
178
Description
Switch
Processor
Performance
Layer 2
Features
Layer 3
Features
Security
Features
HighAvailability
Management
Features
Manufacturer
part number
Section VI. Technical Requirements
Required Technical Specification
IPv6 Routing Entries: Minimum 125,000
Support IPv6 Unicast and Multicast in hardware with full line-rate forwarding
capacity
Multicast Routes Table/Entries: Minimum 31,000
MAC addresses: Minimum 54,000 entries
ARP: Minimum 45,000 Entries
Switch Virtual Interface: Minimum 4000
VLANs: Minimum 4000 active VLANs
Hardware-based multicast management
Minimum Centralized 550 Gbps switching capacity should be supported.
Should have full line rate forwarding for IPv6 packets
Advanced QoS support with up to 8 queues per port and security policies per port
Security and Qos services hardware based entries: Minimum 125,000
IEEE 802.1QVLAN encapsulation, IEEE 802.3ae, 802.3ad, 802.1p
Support for Automatic Negotiation of Trunking Protocol, to help minimize the
configuration & errors.
Support 4000 Switched Virtual Interfaces
Support for the Link Aggregation Protocol (LACP)
Support for Static IP routing, Routing Information Protocol (RIP),OSPF, BGP, VRF
for IPv4 and IPv6 protocol
Support for IP multicast routing protocols filtering on access and trunk ports.
Support for Quality of Service and Traffic Management
Support for 8 queues per port & priority queuing
Support Protocol Independent Multicast (PIM) and Source-Specific Multicast (SSM)
to support multimedia applications
Support Multicast Listener Discovery (MLD) snooping for IPv6
Standard and extended ACLs on all ports.
Support 802.1x user authentication
Support DHCP Snooping entries
Support IEEE 802.1X User Authentication
Support common policy for wired and wireless nodes
Support Port Security
The switch should support redundant power supply
Nonstop Forwarding/Stateful Switchover (NSF/SSO)
In-Service Software Upgrade (ISSU)
The switch should have Virtual Chassis or similar technology feature included to
create layer 2 loop free topology. Should have minimum 2 x 10G Virtual chassis
Data and Management plane connectivity.
Should have a console port and single IP address to manage all features of the system
Should have a Software-configuration management, including local and remote
storage
Should have a Manageability through a common network-management software
Should have support for Configuration Rollback for improved configuration
management
Bidder should submit BOQ of proposed device including the details part numbers
and Manufacturer warranty.
Bidder should submit the required performance document for the proposed device.
Section VI. Technical Requirements
Description
Warranty
179
Required Technical Specification
Bidder should quote mentioning manufacturer’s warranty and part number and
minimum 3 (Three) years full replacement warranty should be provided for this unit
from the date of successful commissioning.
2.1.6 Server Farm Firewall
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble
/Manufacture
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Offered Firewall should have minimum 12 x1GE integrated data ports, minimum 8 x
10G ports. Minimum 8 Multi-Mode 10G transceivers should be included. All the
cables and accessories should be included.
The appliance should be capable of providing Firewall, VPN Services and Next
Generation Firewall feature
Should have a 64Bit Multi-Core Processor or a similar technology.
The platform shall have dedicated interface for out-of-bound management
Offered Firewall should support CA functionality
Offered Firewall performance (Large packets) minimum 19Gbps with multiprotocol
performance of minimum 9.5Gbps
Offered Firewall + IPS + Application Visibility combine performance should be
5.8Gbps or more.
Hardware and
Offered Firewall should be capable configuring Policies using Command Line (CLI)
Performance
as a last resort in case of Emergency.
Offered Firewall should support minimum 4,000,000 concurrent connections
Offered Firewall should support minimum 200, 000 new connections per second (cps)
Offered Firewall should deliver VPN throughput of minimum 3 Gbps with 10,000
sessions.
Next Generation Firewall (FW+APPS Visiblity+IPS) concurrent sessions minimum
1,800,000 and minimum 120,000 connections/second
Offered Firewall should support up to 220 virtual context/firewall (Data Plane and
administratively separated Logical system)
Offered device should support grouping of physical interfaces within and across Fixed
and Expansion ports into one single physical or logical interface
Offered Firewall should have minimum 36 GB Memory for better performance.
The firewall shall be deployed in high availability mode (hot stand-by redundancy),
have fault tolerance and shall provide stateful failover
General
There shall be support for traffic-based and user based access control.
features
The broad default policy for the firewall for handling inbound traffic shall be to block
all packets and connections unless the traffic type and connections have been
specifically permitted
180
Description
Attack
protection
VPN Features
Section VI. Technical Requirements
Required Technical Specification
It shall support SNMP (Simple Network Management Protocol) v 2.0 and v 3.0.
Network address translation (NAT) shall be supported so that the private IP addresses
of hosts and the structure of an internal network can be concealed by the firewall.
Network Address Translation (NAT) shall be configurable as 1:1, 1: many, many: 1,
many:many shall be supported.
Dynamic Host Configuration Protocol (DHCP) over Virtual Private Network (VPN)
shall be supported for dynamic allocation of IP addresses.
Offered firewall shall support a number of routing options and configurations. Routing
protocol support shall include static routes, Open Shortest Path First (OSPF),
RIPv1/v2.
Virtual LAN (VLAN) support, high port density, WAN support and expandability of
interfaces over time are some important network integration features shall be
supported.
Offered firewall IP stack shall be IPv6 ready.
Offered firewall shall mask the internal network from the external world.
Offered firewall shall provide robust access control capability and be fast in making
access control decisions. Access Control shall be done based on criteria such as
source, destination IPs, port number, protocol, traffic type, application, date
information (day of week, time of day), etc.
Multi-layer, stateful, application-based filtering shall be supported
It shall provide network segmentation features with powerful capabilities that facilitate
deploying security for various internal, external and DMZ (Demilitarized Zone) subgroups on the network, to prevent unauthorized access.
There shall be support for detection of reconnaissance attempts such as IP address
sweep, port scanning etc.
Offered Firewall itself shall be resistant to attack and shall have protection against
firewall evasion techniques.
Some basic attack protection features listed below but not limited to :
a. Maximum no of protections against attacks that exploit weaknesses in the TCP/IP
protocol suite
b. It shall enable rapid detection of network attacks
c. TCP reassembly for fragmented packet protection
d. Brute force attack mitigation
e. SYN cookie protection , SYN Flood, Half Open Connections and NUL Packets
f. Protection against IP spoofing
g. Malformed packet protection
h. Java blocking, and real-time alerts
The firewall shall support Internet Protocol Security (IPSec) & SSL
Key exchange with latest Internet Key Exchange (IKE), IKEv2, Public Key
Infrastructure PKI (X.509) shall be catered to.
Site-to-site VPN tunnels: full-mesh / star topology shall be supported.
Should support Latest Encryption algorithms including AES 128/192/256 (Advanced
Encryption Standards), 3DES (Data Encryption Standard) etc.
Support Latest Authentication algorithms including SHA-1(Secure Hash Algorithm-1),
SHA-2(Secure Hash Algorithm-2) etc.,
IPSec NAT traversal shall be supported.
VPN supporting minimum 10,000 IPSec / SSL VPN peers
Section VI. Technical Requirements
Description
181
Required Technical Specification
Detection rules must be based on an extensible, open language (API) that enables
users to create their own rules, as well as to customize any vendor-provided rules.
Detection rules provided by the vendor must be documented, with full descriptions of
the identity, nature, and severity of the associated vulnerabilities and threats being
protected against.
The detection engine must be capable of detecting and preventing a wide variety of
threats (e.g., malware, network probes/reconnaissance, VoIP attacks, buffer overflows,
P2P attacks, zero-day threats, etc.).
The detection engine must incorporate multiple approaches for detecting threats,
including at a minimum exploit-based signatures, vulnerability-based rules, protocol
Next Gen FW
anomaly detection, and behavioral anomaly detection techniques. Identify and explain
feature
each type of detection mechanism supported.
The detection engine must inspect not only Network Layer details and information
resident in packet headers, but a broad range of protocols across all layers of the
computing stack and packet payloads as well.
The detection engine must be resistant to various URL obfuscation techniques
common to HTML-based attacks.
The solution must be capable of detecting and blocking IPv6 attack
The solution must provide IP reputation feed that comprised of several regularly
updated collections of IP addresses determined by the proposed security vendor to
have a poor reputation.
The solution must be capable of passively gathering information about network hosts
and their activities, such as operating system, services, open ports, client applications,
and vulnerabilities, to assist with multiple activities, such as intrusion event data
correlation, elimination of false positives, and policy compliance.
The solution must be capable of passively gathering information about session flows
for all monitored hosts, including start/end time, ports, services, and amount of data.
The solution must be capable of storing user-defined host attributes, such as host
criticality or administrator contact information, to assist with compliance monitoring.
The solution must be capable of passively gathering user identity information,
Real-Time
mapping IP addresses to username, and making this information available for event
Contextual
management purposes.
Awareness
The solution must be capable of passively gathering details unique to mobile devices
traffic to identify a wide variety of mobile operating systems, mobile applications and
associated mobile device hardware.
The solution must provide a detailed, interactive graphical summary that includes data
on applications, application statistics, connections, intrusions events, hosts, servers,
users, file-types, malwares and relevant URLs. These data should be presented in the
form of vivid line, bar, pie and donut graphs accompanied by detailed lists
(Administrator should easily create and apply custom filters to fine-tune the analysis).
Appliance have capacity to block source based on geo-location
The solution must be capable of employing an extensive set of contextual information
(e.g., pertaining to the composition, configuration, and behavior of the network and its
hosts) to improve the efficiency and accuracy of both manual and automatic analysis
Intelligent
of detected events.
Security
Automation
The solution must be capable of significantly reducing operator effort and accelerating
response to threats by automatically prioritizing alerts, ideally based on the potential
for correlated threats to successfully impact the specific hosts they are directed
182
Description
Advance
Malware
Protection
Network
Behavior
Analysis
(NBA)
NGFW
Management
and Usability
Section VI. Technical Requirements
Required Technical Specification
toward.
The solution must be capable of dynamically tuning IDS/IPS sensors (e.g., selecting
rules, configuring policies, updating policies, etc.) with minimal human intervention.
The solution should be capable of providing network-based detection of malware by
checking the disposition of known files in the cloud using the SHA-256 file-hash as
they transit the network (SHA-256 and target IP address should be given to aid
remediation efforts) with enabling just advance malware protection or similar solution
should be provided. Please add and mention if any additional device required.
The solution must provide a full-featured NBA capability to detect threats emerging
from inside the network This includes the ability to establish “normal” traffic
baselines through flow analysis techniques and the ability to detect deviations from
normal baselines
The NBA capability must provide visibility into how network bandwidth is consumed
to aid in troubleshooting network outages and performance degradations.
The NBA capability must provide the ability to link Active Directory and/or LDAP
usernames to IP addresses related to suspected security events.
The same network devices used for IPS must also be used as part of the NBA
capability. No NBA-only device should be required.
The same management platform used for IPS must also be used to manage the NBA
capability.
The management platform must be capable of centralized, life cycle management for
all NGFW services/devices, all required licenses for centralized management for Next
Generation FW IPS should be included.
The management platform must be capable of aggregating IDS/IPS events and
centralized, real-time monitoring and forensic analysis of detected events.
The management platform must be accessible via a web-based interface and ideally
with no need for additional client software.
The management platform must provide a highly customizable dashboard.
The management platform must be capable of integrating third party vulnerability
information into threat policy adjustment routines and automated tuning workflows.
The management platform must be capable of role-based administration, enabling
different sets of views and configuration capabilities for different administrators
subsequent to their authentication.
The management platform must include a scheduling subsystem to facilitate
automation of routine tasks, such as backups, upgrades, report creation, and policy
application.
The management platform must include one or more default (i.e., pre-defined)
detection policy configurations to help simplify initial deployment.
The management platform must provide the capability to easily view, enable, disable,
and modify individual rules, as well as groups or categories of rules.
The management platform must be capable of automatically receiving rule updates
published by the vendor and automatically distributing and applying those rule updates
to sensors.
The management platform must be capable of backup and rollback for sensor
configurations and the management platform itself.
The management platform must include flexible workflow capabilities for managing
the complete life cycle of an event, from initial notification through to any response
Section VI. Technical Requirements
183
Description
Required Technical Specification
and resolution activities that might be required.
The management platform must provide the ability to view the corresponding
detection rule for each detected event, along with the specific packet(s) that caused it
to be triggered.
The management platform must support both internal and external databases/systems
for storage of event data, logs, and other system-generated information.
The management platform must be capable of synchronizing time between all
components of the system via NTP.
The management platform must be capable of logging all administrator activities, both
locally and to a remote log server.
The solution must support LDAP for single sign-on to sensors and the management
console.
The management platform must provide robust reporting capabilities, including a
selection of pre-defined reports and the ability for complete customization and
generation of new reports.
The management platform must allow quick report customization by importing from
Reporting and
dashboards, workflows and statistics summaries.
Alerting
The management platform must provide multiple report output types or formats, such
as PDF, HTML, and CSV.
The management platform must support multiple mechanisms for issuing alerts (e.g.,
SNMP, e-mail, SYSLOG).
Bidder should submit BOQ of proposed device including the details part numbers and
Manufacturer
Manufacturer warranty.
part number
Bidder should submit the required performance document for the proposed device.
Bidder should quote mentioning manufacturer's warranty and subscription part number
Warranty
and minimum 3 (Three) years full replacement warranty and subscription should be
provided for this unit from the date of successful commissioning
2.1.7
Extranet Firewall
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
Enclosure
Type
Hardware and
Performance
Specs of
Firewall &
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Rack Mountable
The platform shall be supplied with at least 8 number of 10/100/1000Mbps interfaces.
The appliance should be capable of providing Firewall, VPN Services
The appliance should have a 64Bit Multi-Core Processor or similar technology.
The platform shall have dedicated interface for out-of-bound management
184
Description
VPN Services
General
features
Network
Address
Translation
Section VI. Technical Requirements
Required Technical Specification
The Firewall should support CA functionality
Firewall performance (Large packets) minimum 3.8 Gbps with multiprotocol
performance of minimum 1.8 Gbps
Firewall should be capable configuring Policies using Command Line (CLI) as a last
resort in case of Emergency.
The appliance should have hardware cryptographic module
The appliance should support concurrent connection up to minimum 950,000
New connection Per Second should be at least 48,000
Next generation Firewall (FW+IPS+AppsVisibilty) throughput Minimum 1.2 Gbps
Firewall should be capable of monitoring environmental temperature and generate
syslogs when exceeds normal temperature.
The appliance should support dual hot swappable redundant power supply
The appliance should deliver VPN throughput of minimum 680 mbps
Firewall should support up to minimum 95 virtual Firewalls (Data Plane and
Administratively separate logical system)
The appliance should support automatic creation of logs and generate a Technical
assistance case
The appliance should support grouping of physical interfaces within and across Fixed
and Expansion ports into one single physical or logical interface
The appliance should support for BOTNET protection, isolating malware
communication to the command control
The appliance should support for Multicast
The appliance should support Packet Tracer capabilities for troubleshooting purposes
Firewall should have minimum 16 GB Memory for better and faster processing.
The firewall shall be deployed in high availability mode (hot stand-by redundancy),
have fault tolerance and shall provide stateful failover
The firewall shall have a powerful OS that is hardened and is based upon minimal
feature sets.
Access control shall be provided for including specified as rules and policies or any
other comprehensive easy to maintain facility.
There shall be support for traffic-based and for user based access control.
The firewall shall allow configuration of policy that governs the rules according to
which the firewall handles the traffic.
The broad default policy for the firewall for handling inbound traffic shall be to block
all packets and connections unless the traffic type and connections have been
specifically permitted
It shall support SNMP (Simple Network Management Protocol) v 2.0 and v 3.0.
Network address translation (NAT) shall be supported so that the private IP addresses
of hosts and the structure of an internal network can be concealed by the firewall.
Network Address Translation (NAT) shall be configurable as 1:1, 1: many, many: 1,
many:many shall be supported.
Port address translation/Masquerading shall be provided.
Dynamic Host Configuration Protocol (DHCP) over Virtual Private Network (VPN)
shall be supported for dynamic allocation of IP addresses.
The firewall shall support a number of routing options and configurations. Routing
protocol support shall include static routes, Open Shortest Path First (OSPF),
RIPv1/v2.
Section VI. Technical Requirements
Description
185
Required Technical Specification
Virtual LAN (VLAN) shall be supported.
The firewall shall support LAN interfaces (10/100/1000) for high speed LAN traffic
with facility for future expansion.
The firewall shall be capable of integrating with other equipment and with adequate
optimization.
The firewall IP stack shall be IPv6 ready.
The firewall shall mask the internal network from the external world.
The firewall shall provide robust access control capability and be fast in making
access control decisions. Access Control shall be done based on criteria such as
source, destination IPs, port number, protocol, traffic type, application, date
information (day of week, time of day), etc.
Multi-layer, stateful, application -based filtering shall be done
It shall provide network segmentation features with powerful capabilities that facilitate
deploying security for various internal, external and DMZ (Demilitarized Zone) subgroups on the network, to prevent unauthorized access.
Ingress/egress filtering capability shall be provided.
There shall be support for detection of reconnaissance attempts such as IP address
sweep, port scanning etc.
Attack
Firewall itself shall be resistant to attack and shall have protection against firewall
protection
evasion techniques.
Some basic attack protection features listed below but not limited to :
a. Maximum number of protections against attacks that exploit weaknesses in the
TCP/IP protocol suite
b. It shall enable rapid detection of network attacks
c. TCP reassembly for fragmented packet protection
d. Brute force attack mitigation
e. SYN cookie protection , SYN Flood, Half Open Connections and NUL Packets
f. Protection against IP spoofing
g. Malformed packet protection
h. Java blocking, and real-time alerts
The firewall shall support Internet Protocol Security (IPSec) & SSL
Key exchange with latest Internet Key Exchange (IKE), IKEv2, Public Key
Infrastructure PKI (X.509) shall be catered to.
Site-to-site VPN tunnels: full-mesh / star topology shall be supported.
Layer Two Tunneling Protocol (L2TP) support shall be provided.
Support Latest Encryption algorithms including AES 128/192/256 (Advanced
VPN Features Encryption Standards), 3DES (Data Encryption Standard) etc.,
Support Latest Authentication algorithms including SHA-1 (Secure Hash Algorithm1), SHA-2 (Secure Hash Algorithm-2) etc.,
IPSec NAT traversal shall be supported.
Configuration of VPN shall be intuitive and user friendly.
VPN throughput should be at least 680 Mbps supporting minimum 4500 IPSec / SSL
VPN peers
Detection rules must be based on an extensible, open language that enables users to
Next Gen FW create their own rules, as well as to customize any vendor-provided rules.
feature
Detection rules provided by the vendor must be documented, with full descriptions of
the identity, nature, and severity of the associated vulnerabilities and threats being
186
Description
Advance
Malware
Protection
Protection
against
Advanced
Malware
Real-Time
Contextual
Awareness
Intelligent
Security
Section VI. Technical Requirements
Required Technical Specification
protected against.
The detection engine must be capable of detecting and preventing a wide variety of
threats (e.g., malware, network probes/reconnaissance, VoIP attacks, buffer overflows,
P2P attacks, zero-day threats, etc.).
The detection engine must incorporate multiple approaches for detecting threats,
including at a minimum exploit-based signatures, vulnerability-based rules, protocol
anomaly detection, and behavioral anomaly detection techniques. Identify and explain
each type of detection mechanism supported.
The detection engine must inspect not only Network Layer details and information
resident in packet headers, but a broad range of protocols across all layers of the
computing stack and packet payloads as well.
The detection engine must be resistant to various URL obfuscation techniques
common to HTML-based attacks.
The solution must be capable of detecting and blocking IPv6 attack
The solution must provide IP reputation feed that comprised of several regularly
updated collections of IP addresses determined by the proposed security vendor to
have a poor reputation.
The solution should be capable of providing network-based detection of malware by
checking the disposition of known files in the cloud using the SHA-256 file-hash as
they transit the network (SHA-256 and target IP address should be given to aid
remediation efforts) with enabling just advance malware protection or similar solution
should be provided. Please add and mention if any additional device required.
The solution should be capable of providing network-based detection of malware by
checking the disposition of known files in the cloud using the SHA-256 file-hash as
they transit the network (SHA-256 and target IP address should be given to aid
remediation efforts)
The solution must be capable of passively gathering information about network hosts
and their activities, such as operating system, services, open ports, client applications,
and vulnerabilities, to assist with multiple activities, such as intrusion event data
correlation, elimination of false positives, and policy compliance.
The solution must be capable of passively gathering information about session flows
for all monitored hosts, including start/end time, ports, services, and amount of data.
The solution must be capable of storing user-defined host attributes, such as host
criticality or administrator contact information, to assist with compliance monitoring.
The solution must be capable of passively gathering user identity information,
mapping IP addresses to username, and making this information available for event
management purposes.
The solution must be capable of passively gathering details unique to mobile devices
traffic to identify a wide variety of mobile operating systems, mobile applications and
associated mobile device hardware.
The solution must provide a detailed, interactive graphical summary that includes data
on applications, application statistics, connections, intrusions events, hosts, servers,
users, file-types, malwares and relevant URLs. These data should be presented in the
form of vivid line, bar, pie and donut graphs accompanied by detailed lists
(Administrator should easily create and apply custom filters to fine-tune the analysis).
Appliance have capacity to block source based on geo-location
The solution must be capable of employing an extensive set of contextual information
(e.g., pertaining to the composition, configuration, and behavior of the network and its
Section VI. Technical Requirements
Description
Automation
Application
control
Network
Behavior
Analysis
(NBA)
NGFW
Management
and Usability
187
Required Technical Specification
hosts) to improve the efficiency and accuracy of both manual and automatic analysis
of detected events.
The solution must be capable of significantly reducing operator effort and accelerating
response to threats by automatically prioritizing alerts, ideally based on the potential
for correlated threats to successfully impact the specific hosts they are directed
toward.
The solution must be capable of dynamically tuning IDS/IPS sensors (e.g., selecting
rules, configuring policies, updating policies, etc.) with minimal human intervention.
The solution must integrate application control to reduce risks associated with
applications usage and client-side attacks. It should provide a means of enforcing
acceptable use policies of up to minimum 1200 application detectors.
The solution must support creation of user-defined application protocol detectors.
The solution must have content awareness with comprehensive file detection policies
and blocking of files by types, protocols and directions.
The solution must provide capabilities for establishing and enforcing host compliance
policies and alerting on violations.
The solution must be capable of easily identifying all hosts that exhibit a specific
attribute or non-compliance condition.
The solution must provide a full-featured NBA capability to detect threats emerging
from inside the network (i.e., ones that have not passed through a perimeter IPS). This
includes the ability to establish “normal” traffic baselines through flow analysis
techniques (e.g., NetFlow) and the ability to detect deviations from normal baselines
The NBA capability must provide visibility into how network bandwidth is consumed
to aid in troubleshooting network outages and performance degradations.
The NBA capability must provide the ability to link Active Directory and/or LDAP
usernames to IP addresses related to suspected security events.
The NBA capability must provide the option of supplying endpoint intelligence to the
IPS for correlation against intrusion events to aid in event impact prioritization.
The same network devices used for IPS must also be used as part of the NBA
capability. No NBA-only device should be required.
The same management platform used for IPS must also be used to manage the NBA
capability. No NBA-only management components should be required.
The management platform must be capable of centralized, life cycle management for
all NGFW services/devices. The Central Management Platform for NGFW services
with all the required licenses has to be included.
The management platform must be delivered in virtual appliance form factor
(management system and UI must provide the same features and functions as in the
physical appliance).
The management platform must be capable of aggregating IDS/IPS events and
centralized, real-time monitoring and forensic analysis of detected events.
The management platform must be accessible via a web-based interface and ideally
with no need for additional client software.
The management platform must provide a highly customizable dashboard.
The management platform must be capable of integrating third party vulnerability
information into threat policy adjustment routines and automated tuning workflows.
The management platform must be capable of role-based administration, enabling
different sets of views and configuration capabilities for different administrators
188
Description
Section VI. Technical Requirements
Required Technical Specification
subsequent to their authentication.
The management platform must include a scheduling subsystem to facilitate
automation of routine tasks, such as backups, upgrades, report creation, and policy
application.
The management platform must include one or more default (i.e., pre-defined)
detection policy configurations to help simplify initial deployment.
The management platform must provide the capability to easily view, enable, disable,
and modify individual rules, as well as groups or categories of rules.
The management platform must be capable of automatically receiving rule updates
published by the vendor and automatically distributing and applying those rule updates
to sensors.
The management platform must be capable of backup and rollback for sensor
configurations and the management platform itself.
The management platform must include flexible workflow capabilities for managing
the complete life cycle of an event, from initial notification through to any response
and resolution activities that might be required.
The management platform must provide the ability to view the corresponding
detection rule for each detected event, along with the specific packet(s) that caused it
to be triggered.
The management platform must support both internal and external databases/systems
for storage of event data, logs, and other system-generated information.
The management platform must be capable of synchronizing time between all
components of the system via NTP.
The management platform must be capable of logging all administrator activities, both
locally and to a remote log server.
The solution must support LDAP for single sign-on to sensors and the management
console.
The management platform must provide robust reporting capabilities, including a
selection of pre-defined reports and the ability for complete customization and
generation of new reports.
The management platform must allow quick report customization by importing from
Reporting and
dashboards, workflows and statistics summaries.
Alerting
The management platform must provide multiple report output types or formats, such
as PDF, HTML, and CSV.
The management platform must support multiple mechanisms for issuing alerts (e.g.,
SNMP, e-mail, SYSLOG).
Bidder should submit BOQ of proposed device including the details part numbers and
Manufacturer
Manufacturer warranty.
part number
Bidder should submit the required performance document for the proposed device.
Bidder should quote mentioning manufacturer’s warranty and part number and
Warranty
minimum 3 (Three) years full replacement warranty should be provided for this unit
from the date of successful commissioning.
Section VI. Technical Requirements
2.1.8
189
Internet Firewall
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
Enclosure
Type
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Rack-mountable
The platform shall be supplied with at least 8 number of 10/100/1000Mbps interfaces.
The appliance should be capable of providing Firewall, VPN Services
The appliance should have a 64Bit Multi-Core Processor or similar technology.
The platform shall have dedicated interface for out-of-bound management
The Firewall should support CA functionality
Firewall performance (Large packets) minimum 2.8 Gbps with multiprotocol
performance of minimum 1.4 Gbps
Firewall should be capable configuring Policies using Command Line (CLI) as a last
resort in case of Emergency.
The appliance should have hardware cryptographic module
The appliance should support concurrent connection up to minimum 730,000
New connection Per Second should be at least 29,000
Firewall should be capable of monitoring environmental temperature and generate
Hardware and
syslog when exceeds normal temperature.
Performance
The appliance should Support dual hot swappable redundant power supply
of Firewall &
VPN Services The appliance should have Online Insertion and Removal (OIR) of external USB flash
drive
The appliance should deliver VPN throughput of minimum 380 mbps
Firewall should support up to minimum 45 virtual Firewalls (Data Plane and
Administratively separate logical system)
The appliance should support automatic creation of logs and generate a Technical
assistance case
The appliance should support grouping of physical interfaces within and across Fixed
and Expansion ports into one single physical or logical interface
The appliance should support for BOTNET protection, isolating malware
communication to the command control
The appliance should support for Multicast
Firewall should support memory up to minimum 12 GB Memory for better
performance.
The firewall shall be deployed in high availability mode (hot stand-by redundancy),
have fault tolerance and shall provide stateful failover
General
The firewall shall have a powerful OS that is hardened and is based upon minimal
features
feature sets.
Access control shall be provided for including specified as rules and policies or any
190
Description
Network
Address
Translation
Attack
protection
Section VI. Technical Requirements
Required Technical Specification
other comprehensive easy to maintain facility.
There shall be support for traffic-based and for user based access control.
The firewall shall allow configuration of policy that governs the rules according to
which the firewall handles the traffic.
The broad default policy for the firewall for handling inbound traffic shall be to block
all packets and connections unless the traffic type and connections have been
specifically permitted
It shall support SNMP (Simple Network Management Protocol) v 2.0 and v 3.0.
Network address translation (NAT) shall be supported so that the private IP addresses
of hosts and the structure of an internal network can be concealed by the firewall.
Network Address Translation (NAT) shall be configurable as 1:1, 1: many, many: 1,
many:many shall be supported.
Port address translation/Masquerading shall be provided.
Dynamic Host Configuration Protocol (DHCP) over Virtual Private Network (VPN)
shall be supported for dynamic allocation of IP addresses.
The firewall shall support a number of routing options and configurations. Routing
protocol support shall include static routes, Open Shortest Path First (OSPF),
RIPv1/v2.
Virtual LAN (VLAN) support
The firewall shall support LAN interfaces (10/100/1000) for high speed LAN traffic
with facility for future expansion.
The firewall shall be capable of integrating with other equipment and with adequate
optimization.
The firewall IP stack shall be IPv6 ready.
The firewall shall mask the internal network from the external world.
The firewall shall provide robust access control capability and be fast in making
access control decisions. Access Control shall be done based on criteria such as
source, destination IPs, port number, protocol, traffic type, application, date
information (day of week, time of day), etc.
Multi-layer, stateful, application-based filtering shall be done
It shall provide network segmentation features with powerful capabilities that facilitate
deploying security for various internal, external and DMZ (Demilitarized Zone) subgroups on the network, to prevent unauthorized access.
Ingress/egress filtering capability shall be provided.
There shall be support for detection of reconnaissance attempts such as IP address
sweep, port scanning etc.
Firewall itself shall be resistant to attack and shall have protection against firewall
evasion techniques.
Some basic attack protection features listed below but not limited to :
a. Maximum no of protections against attacks that exploit weaknesses in the TCP/IP
protocol suite
b. It shall enable rapid detection of network attacks
c. TCP reassembly for fragmented packet protection
d. Brute force attack mitigation
e. SYN cookie protection , SYN Flood, Half Open Connections and NUL Packets
f. Protection against IP spoofing
g. Malformed packet protection
Section VI. Technical Requirements
Description
191
Required Technical Specification
h. Java blocking, and real-time alerts
The firewall shall support Internet Protocol Security (IPSec) & SSL
Key exchange with latest Internet Key Exchange (IKE), IKEv2, Public Key
Infrastructure PKI (X.509) shall be catered to.
Site-to-site VPN tunnels: full-mesh / star topology shall be supported.
Layer Two Tunneling Protocol (L2TP) support shall be provided.
Support Latest Encryption algorithms including AES 128/192/256 (Advanced
VPN Features Encryption Standards), 3DES (Data Encryption Standard) etc.,
Support Latest Authentication algorithms including SHA-1(Secure Hash Algorithm-1),
SHA-2(Secure Hash Algorithm-2) etc.,
IPSec NAT traversal shall be supported.
Configuration of VPN shall be intuitive and user friendly.
VPN throughput should be at least 380 Mbps supporting minimum 2400 IPSec / SSL
VPN peers
Detection rules must be based on an extensible, open language that enables users to
create their own rules, as well as to customize any vendor-provided rules.
Detection rules provided by the vendor must be documented, with full descriptions of
the identity, nature, and severity of the associated vulnerabilities and threats being
protected against.
The detection engine must be capable of detecting and preventing a wide variety of
threats (e.g., malware, network probes/reconnaissance, VoIP attacks, buffer overflows,
P2P attacks, zero-day threats, etc.).
The detection engine must incorporate multiple approaches for detecting threats,
including at a minimum exploit-based signatures, vulnerability-based rules, protocol
Next Gen FW
anomaly detection, and behavioral anomaly detection techniques. Identify and explain
feature
each type of detection mechanism supported.
The detection engine must inspect not only Network Layer details and information
resident in packet headers, but a broad range of protocols across all layers of the
computing stack and packet payloads as well.
The detection engine must be resistant to various URL obfuscation techniques
common to HTML-based attacks.
The solution must be capable of detecting and blocking IPv6 attack
The solution must provide IP reputation feed that comprised of several regularly
updated collections of IP addresses determined by the proposed security vendor to
have a poor reputation.
The solution should be capable of providing network-based detection of malware by
Protection
checking the disposition of known files in the cloud using the SHA-256 file-hash as
against
they transit the network (SHA-256 and target IP address should be given to aid
Advanced
remediation efforts) with Advanced Malware Protection. Please add and mention if
Malware
any additional device required for this feature.
The solution must be capable of passively gathering information about network hosts
and their activities, such as operating system, services, open ports, client applications,
and vulnerabilities, to assist with multiple activities, such as intrusion event data
Real-Time
correlation, elimination of false positives, and policy compliance.
Contextual
Awareness
The solution must be capable of passively gathering information about session flows
for all monitored hosts, including start/end time, ports, services, and amount of data.
The solution must be capable of storing user-defined host attributes, such as host
192
Description
Section VI. Technical Requirements
Required Technical Specification
criticality or administrator contact information, to assist with compliance monitoring.
The solution must be capable of passively gathering user identity information,
mapping IP addresses to username, and making this information available for event
management purposes.
The solution must be capable of passively gathering details unique to mobile devices
traffic to identify a wide variety of mobile operating systems, mobile applications and
associated mobile device hardware.
The solution must provide a detailed, interactive graphical summary that includes data
on applications, application statistics, connections, intrusions events, hosts, servers,
users, file-types, malwares and relevant URLs. These data should be presented in the
form of vivid line, bar, pie and donut graphs accompanied by detailed lists
(Administrator should easily create and apply custom filters to fine-tune the analysis).
Appliance have capacity to block source based on geo-location
The solution must be capable of employing an extensive set of contextual information
(e.g., pertaining to the composition, configuration, and behavior of the network and its
hosts) to improve the efficiency and accuracy of both manual and automatic analysis
of detected events.
Intelligent
The solution must be capable of significantly reducing operator effort and accelerating
Security
response to threats by automatically prioritizing alerts, ideally based on the potential
Automation
for correlated threats to successfully impact the specific hosts they are directed
toward.
The solution must be capable of dynamically tuning IDS/IPS sensors (e.g., selecting
rules, configuring policies, updating policies, etc.) with minimal human intervention.
The solution must integrate application control to reduce risks associated with
applications usage and client-side attacks. It should provide a means of enforcing
acceptable use policies of up to minimum 1200 application detectors.
The solution must support creation of user-defined application protocol detectors.
The solution must have content awareness with comprehensive file detection policies
and blocking of files by types, protocols and directions.
The proposed solution should provide an option to include URL filtering for enforcing
Application
Internet content filtering so as to reduce web born threats and improve productivity.
and
URL
Each URL in the data set must has an associated category and reputation. URL
control
category is a general classification for the URL while URL reputation represents how
likely the URL is to be used for purposes that might be against the organization’s
security policy.
The solution must provide capabilities for establishing and enforcing host compliance
policies and alerting on violations.
The solution must be capable of easily identifying all hosts that exhibit a specific
attribute or non-compliance condition.
The solution must provide a full-featured NBA capability to detect threats emerging
from inside the network (i.e., ones that have not passed through a perimeter IPS). This
includes the ability to establish “normal” traffic baselines through flow analysis
Network
techniques (e.g., NetFlow) and the ability to detect deviations from normal baselines
Behavior
Analysis
The NBA capability must provide visibility into how network bandwidth is consumed
(NBA)
to aid in troubleshooting network outages and performance degradations.
The NBA capability must provide the ability to link Active Directory and/or LDAP
usernames to IP addresses related to suspected security events.
Section VI. Technical Requirements
Description
NGFW
Management
and Usability
193
Required Technical Specification
The NBA capability must provide the option of supplying endpoint intelligence to the
IPS for correlation against intrusion events to aid in event impact prioritization.
The same network devices used for IPS must also be used as part of the NBA
capability. No NBA-only device should be required.
The same management platform used for IPS must also be used to manage the NBA
capability. No NBA-only management components should be required.
The management platform must be capable of centralized, life cycle management for
all NGFW services/devices. The Central Management Platform for NGFW services
with all the required licenses has to be included.
The management platform must be delivered in virtual appliance form factor
(management system and UI must provide the same features and functions as in the
physical appliance).
The management platform must be capable of aggregating IDS/IPS events and
centralized, real-time monitoring and forensic analysis of detected events.
The management platform must be accessible via a web-based interface and ideally
with no need for additional client software.
The management platform must provide a highly customizable dashboard.
The management platform must be capable of integrating third party vulnerability
information into threat policy adjustment routines and automated tuning workflows.
The management platform must be capable of role-based administration, enabling
different sets of views and configuration capabilities for different administrators
subsequent to their authentication.
The management platform must include a scheduling subsystem to facilitate
automation of routine tasks, such as backups, upgrades, report creation, and policy
application.
The management platform must include one or more default (i.e., pre-defined)
detection policy configurations to help simplify initial deployment.
The management platform must provide the capability to easily view, enable, disable,
and modify individual rules, as well as groups or categories of rules.
The management platform must be capable of automatically receiving rule updates
published by the vendor and automatically distributing and applying those rule updates
to sensors.
The management platform must be capable of backup and rollback for sensor
configurations and the management platform itself.
The management platform must include flexible workflow capabilities for managing
the complete life cycle of an event, from initial notification through to any response
and resolution activities that might be required.
The management platform must provide the ability to view the corresponding
detection rule for each detected event, along with the specific packet(s) that caused it
to be triggered.
The management platform must support both internal and external databases/systems
for storage of event data, logs, and other system-generated information.
The management platform must be capable of synchronizing time between all
components of the system via NTP.
The management platform must be capable of logging all administrator activities, both
locally and to a remote log server.
The solution must support LDAP for single sign-on to sensors and the management
194
Section VI. Technical Requirements
Description
Required Technical Specification
console.
The management platform must provide robust reporting capabilities, including a
selection of pre-defined reports and the ability for complete customization and
generation of new reports.
The management platform must allow quick report customization by importing from
Reporting and
dashboards, workflows and statistics summaries.
Alerting
The management platform must provide multiple report output types or formats, such
as PDF, HTML, and CSV.
The management platform must support multiple mechanisms for issuing alerts (e.g.,
SNMP, e-mail, SYSLOG).
Bidder should submit BOQ of proposed device including the details part numbers and
Manufacturer
Manufacturer warranty.
part number
Bidder should submit the required performance document for the proposed device.
Bidder should quote mentioning manufacturer’s warranty and subscription part
Warranty
number and minimum 3 (Three) years full replacement warranty and subscription
should be provided for this unit from the date of successful commissioning.
2.1.9 Application Load Balancer
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
Features
Server/Applic
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Purpose built hardware architecture of multicore CPU based appliance
Should provide minimum 10 Gbps of layer 7 throughput
Should have minimum 16 GB of RAM
Should have minimum 2X10G ports and minimum 8X1G ports
Should have dedicated out of band 10/100/1000 copper management interface
Should support minimum 400,000 Layer 7 request per second and scalable to
minimum 700,000 Layer 7 request per second
Should support hardware assisted SSL offloading capability with minimum 4,500 SSL
Transactions per second at 2048 bit SSL and scalable to minimum 9,000 SSL
Transactions per second at 2048 bit
Should support hardware assisted minimum 8 Gbps SSL throughput in SSL offload
Should provide minimum 4 Gbps server side compression throughput scalable to
minimum 8 Gbps server side compression throughput
Should have a minimum DNS performance of minimum 400,000 QPS scalable up to
minimum 700,000 QPS
Should support minimum 10,000,000 concurrent connections
Should be able to provide layer 7 traffic management and application delivery features
Section VI. Technical Requirements
195
Description
Required Technical Specification
ation
Load using multicore processor architecture
Balancing
Should have application delivery features such as layer 7 load balancing, layer 7
content switch, caching, hardware based SSL offload and server side compression
Should be able to monitor the applications using intelligent application level monitors
which can be system defined, internal or external executable scripts
Should provide the capability to source address translation one arm deployment mode,
two arm routed mode and direct server return mode
Should provide static and dynamic load balancing algorithms such as round robin,
weighted round robin, fastest, predictive and observed
Should support 2048 and 4096 bit key for SSL traffic management
Should be application aware for protocols such as HTTP, HTTPS, FTP, SIP, DNS,
Diameter, RADIUS etc.
Should provide mechanism to bind multiple health checks, support for Application
specific VIP health check and next gateway health checks
Should be able to load balance traffic in environment where the request response path
is asymmetric
Should support inspection of SSL traffic for reverse proxy and forward proxy
deployment. Should also support ICAP interface for integration with external security
systems.
Should support SPDY gateway in environment where the client to load balancer traffic
is SYDP and from load balancer to server is normal HTTP providing SPDY proxy
Should provide HTTPS interface management for administering the device
Should provide SSH interface management for administering the device
Should provide troubleshooting and traffic analysis tool like tcpdump
Should support SNMP V1, V2c, V3
Should have a web dashboard that should provide the following information:
• Total concurrent sessions
Device
• Throughput
Administratio
• HTTP request per second
n
• CPU Usage
• Memory Usage
Graphs of the above data for the last 30 days should be available.
Should provide multiple config version option on the appliance
Should provide system, traffic logs on web GUI
Should support role based admin access with roles like No Access, Guest, Operator,
Application Editor, Resource Administrator and Administrator
Support both Active - Active and Active - Standby topology
High
Should support transparent failover between 2 devices, the failover should be
Availability
transparent to other networking devices
Should have dual power supply
Should be able to provide 24/7 support over phone/email
OEM Criteria
Preferable to be in Gartner’s Leaders quadrant for ADC's
Bidder should quote minimum 3 (Three) years manufacturer's full replacement
Warranty
warranty for this unit from the date of successful commissioning.
196
2.1.10
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
Hardware
Functions
Section VI. Technical Requirements
Bandwidth Manager
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
The equipment must provide at least 1 pair minimum 1Gbps and dedicated
Management port. The equipment must support expansion module up to at least 2
separate network segment.
Product should come with one power supply and should have option of second
redundant and hot swappable power supply
Equipment must support ‘fail-close’ in the event of power outrage, software or
hardware failure. The “fail-close” functionality of electronic interface must be
implemented internally。
(1) The equipment must support remote access to enable management and
operation via command line and GUI. It should provide the following access
interfaces:
 RS-232 DB9 serial port;
 HTTP/HTTPS
 Should support customized portal for different users
(2) SNMP V2/V3
(3) Telnet/ SSH
(4) The equipment must support high availability
(5) The equipment must support OSI L2 to L7 protocol auto-detection and classify
the traffic accordingly. It must be able to detect at least 700 commonly used
applications and protocols, including FTP, HTTP and other applications using
non-standard TCP port
(6) The equipment must support application flow classification based on MAC
address, 802.1p/q, ISL, MPLS tag;
(7) The equipment must support flow classification based on IP Precedence, DiffServ Code Point , IP address, multiple IP addresses ,IP subnet;
(8) The equipment must support flow classification based on both static and
dynamic TCP and UDP ports. Example of dynamic port applications are
Thunder,BitTorrent, FlashVideo,PPStream,PPlive,Skype,KaZaA
v1/v2, Gnutella, WinMx, eDonkey, Half-life, etc. The equipment must be able
to auto-detect, auto-classify and then enforce bandwidth control accordingly;
(9) The equipment must support customized application protocol detect, to
facilitate detection and control of homebrew application。
(10) The equipment must support flow classification based on DNS, URL,
attachment extension (e.g., “.exe, .zip, .com”), Mime-Type (e.g.
“application/octet-stream, video/x-flv, etc. browser type;
Section VI. Technical Requirements
Description
197
Required Technical Specification
(11) The equipment must support URL Category for HTTP traffic, category must
more than 80 kind, support cloud computing, process 8 billion request every
day so that can guarantee real time category and coverage;
(12) The equipment must support flow classification based on the server physical
location, traffic flow direction (in/out), host list, etc.;
(13) The equipment must support layer 7+ flow identification, and classify traffic
based on application level attribute, include the following applications:
- Video conference: Classify video, audio stream, ICMP in RTP/RTCP-I stream;
- Voice over IP (VOIP): Identify audio codec in RTP-I(dynamic, G729, GSM,
JPEG, PCMA, PCMU, endpoint type;
- Identify Individual application in Citrix traffic;
- Identify database in the Oracle traffic;
- Identify Individual database in PostrgreSQL traffic;
(14) The equipment must support flow classification based on the host system type
(TN3270,TN5250,FNA,5250p,TCPA,Attachmate, etc.);
(15) The equipment must make use of tree-based, multi-layers structure layout to
visualize the traffic flow;
(16) The equipment provide comprehensive application response time management,
by providing total delay, network delay, server delay and delay distribution
diagram;
(17) The equipment must provide detailed analysis on delay, jitter, packet loss of
VoIP traffic;
(18) The equipment must provide detailed analysis on a particular IP flow;
(19) The equipment must be able to identify the originator and receiver of a flow and
the associate ports;
(20) The equipment must provide TCP/IP based, worst client and worst server
analysis;
(21) The equipment must support bi-directional, precise flow control, only by
deploying one unit of proposed equipment on any traffic point along the flow;
(22) The equipment must support queue-based traffic control and TCP sliding
window, connection link delay control. The bandwidth adjustment must archive
down to 1kbps precision;
(23) The equipment must provide MTU management to control fragmentation and
jitter.
(24) The equipment must support, at the same time, per-session flow control and
enforce max/min bandwidth policy;
(25) The equipment must be able to seamless integrate into the WAN acceleration
solution of the same company. It must be able to identify applications in
individual acceleration tunnel and perform statistical analysis, bandwidth
control, to balance the resource among tunneled and non-tunneled traffic. It
must be able to perform bandwidth control on applications inside the
accelerated tunnels;
(26) The equipment must be able to automatically respond to network situation by
pre-defined policy (e.g. bandwidth adjustment, IP jail) and alert (e.g. SNMP
Trap, SysLog, Mail);
(27) The reporting and graphing function must be integrated in the equipment,
198
Description
Performance
requirement
Warranty
Section VI. Technical Requirements
Required Technical Specification
without any add-on or external device. The precision must be down to minute
level;
(28) Real-time analysis on the active flow (including single link and multi-inks realtime, end-to-end analysis) must be integrated into the equipment, without any
add-on or external device. The real-time precision and update interval must be
down to second and provide statistical figure for historical analysis. The UI
should be written in JAVA or Flash to facilitate browser access;
(29) At least 2 month of traffic data must be stored on the device itself, without any
add-on or external device;
(30) Should support centralized management and reporting;
(31) Should support data export via SNMP, XML, CSV, CGI, etc.;
(32) Should support integration with third party network management system
(33) Should support integration with Radius and TACACS+ for administrator
authentication and authorization
(34) Should support Active Directory Integration for user awareness
(35) Should support administrator operation audit
(1) Should support minimum 500,000 IP flows;
(2) Should Support minimum 5,000 traffic classification
(3) Should Support minimum 450,000 concurrent IP host statistic
(4) Should Support minimum 7,500 shaping policies
(5) Should Support minimum 15,000 dynamic partitions
(6) Should Support minimum 5,000 static partitions
Bidder should quote and provide minimum 3 (Three) years manufacturer's full
replacement warranty for this unit from the date of successful commissioning
2.1.11 Content Filter
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
General
malware
control and
filtering
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
The device should have minimum 1,000 licenses for web security control with
minimum of three years subscription.
The device should be capable of minimum 12,000 users capacity.
Spyware/Adware/Generic Web threat protection
Virus protection
Automatic update of all anti-malware signatures
Multiple anti-malware engines support
AS/AV engine(s)
Section VI. Technical Requirements
Description
199
Required Technical Specification
Phishing protection
Automatic update of phishing protection rules
URL filtering support
Number of URL categories
URL/web filtering database suppliers
Policies per identity / customer
Policies defined per time range
Policies defined per category
Policies defined per destination URL
Policies defined per destination IP address
Block possibility
Monitoring only possibility
Notification / logging
Custom URL categories
Sub-level domain categorization
Webmail filter
Web reputation based filtering
Customizable reputation filtering thresholds to block/allow/scan content
TCP-layer scanning to detect rogue activity and phone-home attempts
Monitoring and blocking of malware connection attempts on all 65535 TCP ports
Monitoring and blocking of malware connection attempts in both incoming and
outgoing direction
Cache storage capacity at least 4TB
Cache technology used
Implementation as transparent proxy
Proxy cache Implementation as transparent proxy using L4 switch
and
Implementation as explicit proxy
performance
Implementation as explicit proxy using PAC files and/or WPAD
PAC file hosting
Multiple upstream proxies support with conditional HTTP traffic routing
Multiple data ports for Web traffic scanning
HTTP
HTTPS
FTP over HTTP
FTP (native)
Web elements and browser filtering
Browser version filtering
Protocol
control
Java blocking
ActiveX blocking
Archive file types detected
Multiple archives detection
File type blocking
Block by defined maximum file size
User authorization by IP address
User
User authorization by Subnet
authentication
LDAP authentication
200
Section VI. Technical Requirements
Description
Required Technical Specification
Active directory authentication with NTLMSSP (Integrated Windows Authentication)
LDAP/Active directory groups support for policy assignment
HTTPS Management console
CLI access using SSH
RS232 serial console port
Centralized management possibility
Manage up to 100 separate devices from one single point
Administratio
Delegated, fully customizable, security policy administration down to user identity
n and
level
management
Administrative users authentication through LDAP
Administrative users authentication through RADIUS
Administrative users authentication through local passwords
Unlimited number of security policies
Unlimited number of custom (admin-specified) URL categories
Appliance-based solution with a proprietary hardened OS
Minimum 4 gigabit Ethernet interfaces supported by hardware platform for Web
security solution
Multiple hard-drives in RAID array
Total drive space available at least 4TB
Hardware and
Minimum 32 GB of RAM
support
Dual-core CPU with multicore software support
Rack mount chassis
Vendor support access through e-mail, telephone, website
Access to vendor support portal and knowledgebase
Full hardware warranty throughout the support contract period
Web interface for reporting solution
Fully customizable reports
Custom report scripting capability
Reporting
Possibility to drill down to each user's individual activity
Reports export and scheduling
Reporting implemented separately from main security appliances
Suspicious activity reporting per user
Bidder should submit BOQ of proposed device including the details part numbers and
Manufacturer
Manufacturer warranty.
part number
Bidder should submit the required performance document for the proposed device.
Bidder should quote mentioning manufacturer's warranty and part number and
Warranty
minimum 3 (Three) years full replacement warranty should be provided for this unit
from the date of successful commissioning.
2.1.12 WAN Router
Description
Quality
Certification
Brand
Model
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
To be mentioned by the bidder
Section VI. Technical Requirements
Description
Country of
Origin
Country of
Assemble /
Manufacture
Router
Processor
Service
Processor
RAM / DRAM
Power supply
Throughput
VPN
Interface
No of slots.
General
Features
201
Required Technical Specification
USA or EU
To be mentioned by the bidder
Dedicated Route processor module would be an advantage
Dedicated services processor module would be an advantage
Min 8 GB DRAM/Memory
Redundant Power supplies.
Minimum 2.5 (Full-Duplex) Gbps from day 1, Upgradable to minimum 18 Gbps or
more if required in future
Minimum 2 Mpps For the combination of the following commonly used features:
IPv4 forwarding, ACL and QoS. It can be scaled up to minimum 6 Mpps or more in
future if required
Would be an advantage to have on board VPN acceleration mechanism
Should have the capability to expand up to minimum 7,500 IPSec tunnels
Router must have encryption capabilities to scale up to 8GbpsIPSec/crypto
throughput
Should have at least 4 x 1GE SFP Port with minimum 4 GE copper transceivers with
all the cables and accessories.
Should have minimum 2 x 10 GE routing port with minimum 10 GE multi-mode SFP
transceivers with all the cables and accessories.
Minimum 1 module port adapter slot
Route Processors should have minimum 1GB of flash/internal memory to support
multiple software images for backup purposes and future scalability.
Would be an advantage to support dual Software for single-route-processor solutions
for a highly compact, fully redundant, high-availability solution. Otherwise dual
Route Processors have to be provided.
Route Processor should perform the following control processor functions:
 Build Layer 2 & Layer 3 forwarding information tables.
 Allow for centralized configuration of router including services like stateful
firewall, deep-packet inspection etc.
 Negotiating and maintaining IPSec authentication, encryption methods, and
encryption keys.
 Track the status of various system components like the software, services
processor, line cards, fan trays, PSU etc. & provide an out-of-band access
method to the router in case of a software crash
Dedicated Processor with following functions in hardware would be an advantage.
 MAC classification & Layer 2 and Layer 3 forwarding, QoS classification,
policing and shaping
 Multicast replication with low-jitter traffic paths
 Security access control lists (ACLs),
 VPNs and load balancing,
Dedicated processor would be an advantage and should additionally support the
following functions in hardware with additional licenses:
202
Description
Section VI. Technical Requirements
Required Technical Specification
Firewall feature
Network Based Application Recognition (NBAR) or similar technology
Network Address Translation (NAT)
Should have the scalability up to 3500 GRE tunnels or more
 Must have minimum 900,000 IPv4 or minimum 900,000 IPv6 routes and scaled
up higher than 3,350,000 IPv4 or 2,900,000 IPv6 routes.
QoS should support per interface/port:
 Two Low Latency Queuing (LLQ) queues per policy, with more than 500
policies
Router should have an integrated auxiliary and/or console & 10/100 management
interface, in addition it should support a standard USB interface to allow for
software image & configuration portability.
Should be capable of supporting 802.1q VLANs and VLAN trunking.
All modules, fan trays & Power supplies should be hot swappable without the need
of powering down the chassis during replacement.
Should support port aggregation for higher bandwidth and redundancy
The Gigabit Ethernet port should support multimode and single mode fiber
connectivity
The router should support wide variety of interfaces including E1, DS3 and STM-1
on SDH and Channelized E1, Fast Ethernet and Gigabit Ethernet, 10 Gigabit
Ethernet WAN Interface
Would be an advantage to support fast software patch upgrades while the router is in
service
Would be an advantage to provide Non-Stop Forwarding support to ensure data
forwarding during software switch-over or upgrade
Should have integrated diagnostics features
Should have modular software images, so that each software process runs
independent of the other thus allowing for higher stability.
Should support IPv6 from day 1.
The operating system should support a simple CLI interface for configuration
Should support the following WAN protocols : HDLC, PPP, and Frame Relay
Should support Multilink PPP as per RFC 1990.
Should support LFI (link fragmentation and Interleaving) for multiservice networks
Should have RIPv2, OSPF, IS-IS and BGP4 routing protocols, with support for all
the features like OSPF on demand etc. & IP multicast routing protocols: DVMRP,
PIM Version 2 (Sparse Mode & Dense Mode), IGMP v1,v2,v3
Should have Enterprise Services feature set with support for protocols like
Multiprotocol Label Switching (MPLS), Ethernet over MPLS (EoMPLS) & Virtual
Route Forwarding (VRF)
The router should support multiple level of privileges and authentication for user
access, along with SSH support for secured device access
Should support authentication protocol for AAA
The software should support Network Address Translation (NAT) and Port Address
Translation (PAT)
Should support source and destinations based ACLs, time based ACLs, VLAN /
Port-based ACLs & Dynamic reflexive ACLs and/or equivalent.
Should support MD5 authentication for routing protocols



Section VI. Technical Requirements
Description
Manufacturer
part number
Warranty
203
Required Technical Specification
The router must have IPsec encryption for data confidentiality, with support for
dedicated hardware modules to offload encryption processes from the CPU would be
an advantage.
The router should support 3DES and AES encryption standards
Should support protection against anti-replay attacks & perform Unicast Reverse
Path Forwarding in hardware, Policy based Routing
Must have IPSec Protocols: IPsec standards supported include Digital Encryption
Standard (DES), Triple DES (3DES), and Advanced Encryption Standard (AES;
128, 192, and 256) for encryption; Rivest, Shamir, Aldeman (RSA) algorithm
signatures and Diffie Hellman for authentication; and Secure Hash Algorithm 1
(SHA-1) or Message Digest Algorithm 5(MD5) hashing algorithms for data integrity
with the cryptographic engine in the router.
Support Detection of and response to distributed-denial-of-service (DDoS) attacks
Support source-based filtering which provide wire-rate, real-time defense against
DDoS attacks
Support routing peers validation, enhances routing stability, and overload protection
by using MD5 peer authentication and redistribution protection
Should support RSVP
The router should be able to support IP precedence
Bidder should submit BOQ of proposed device including the details part numbers
and Manufacturer warranty.
Bidder should submit the required performance document for the proposed device.
Bidder should quote mentioning manufacturer’s warranty and part number and
minimum 3 (Three) years full replacement warranty should be provided for this unit
from the date of successful commissioning.
2.1.13 Extranet Router
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
Enclosure Type
Architecture
Router
Processor
Service
Processor
RAM / DRAM
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Rack-mountable
The router should be modular in architecture with a services-based hardware
architecture
Dedicated Route processor would be an advantage
Dedicated services processor module would be an advantage.
Minimum 8 GB DRAM/Memory
204
Description
Power supply
Forwarding
throughput
VPN
Interface
No of slots.
General
Features
Section VI. Technical Requirements
Required Technical Specification
Redundant Power supplies.
Minimum 5 (Full-Duplex) Gbps from day 1, Upgradable through license to 33 Gbps
or more if required in future
Would be an advantage to have on board VPN acceleration mechanism
Should have the capability to expand up to minimum 7,500 IPSec tunnels
Minimum 4 Mpps For the combination of the following commonly used features:
IPv4 forwarding, IP Multicast, ACL, QoS. It can be scaled up to 18 Mpps or more in
future if required
Router should be scalable up to 4Gbps IPSec/crypto encryption throughput
Should have at least 6 x 1GE with 6x GE copper transceivers all the cables and
accessories should be included.
Minimum 3 module/shared port adapter slots
Route Processors should have minimum 1GB of flash/internal memory to support
multiple software images for backup purposes and future scalability.
Router should have Software sub-package/patch Upgrade Option without any
Downtime or reload requirement.
Router should support software redundancy, if not please provide Route processor
redundancy based on hardware.
Route Processor should perform the following control processor functions:
 Build Layer 2 & Layer 3 forwarding information tables.
 Allow for centralized configuration of router including services like stateful
firewall, deep-packet inspection etc.
 Negotiating and maintaining IPSec authentication, encryption methods, and
encryption keys.
 Track the status of various system components like the software, services
processor, line cards, fan trays, PSU etc. & provide an out-of-band access method
to the router in case of a software crash
Dedicated Processor would an advantage and should perform the following functions
in hardware
 MAC classification & Layer 2 and Layer 3 forwarding,
QoS classification, policing and shaping
 Multicast replication with low-jitter traffic paths
 Security access control lists (ACLs),
 VPNs and load balancing,
Services Processor supporting the following functions in hardware would be an
advantage.
 Firewall feature
 Network Based Application Recognition (NBAR) or similar technology
 Network Address Translation (NAT)
 More than 3,900 unique ACLs
 Minimum 900 GRE tunnels and scaled up to 3,900 GRE tunnels or more
 Must have minimum 490,000 IPv4 or minimum 123,500 IPv6 routes and scale
up higher than 3,350,000 IPv4 or 2,900,000 IPv6 routes without any hardware
install.
QoS should support per interface/port:
 Two Low Latency Queuing (LLQ) queues per policy, with more than 500
Section VI. Technical Requirements
Description
Manufacturer
part number
205
Required Technical Specification
policies
Router should have an integrated auxiliary and/or console & 10/100 management
interface, in addition it should support a standard USB interface to allow for
software image & configuration portability.
Should have status and health LEDs to diagnose system status on the front panel.
Should be capable of supporting 802.1q VLANs and VLAN trunking.
All modules, fan trays & Power supplies should be hot swappable without the need
of powering down the chassis during replacement.
Should support port aggregation for higher bandwidth and redundancy
The Gigabit Ethernet port should support multimode and single mode fiber
connectivity
The router should support wide variety of interfaces including E1, DS3 and STM-1
on SDH and Channelized E1, Fast Ethernet and Gigabit Ethernet, 10 Gigabit
Ethernet WAN Interface
Should support IPv6 from day 1.
The operating system should support a simple CLI interface for configuration
Should have RIPv2, OSPF, IS-IS and BGP4 routing protocols, with support for all
the features like OSPF on demand etc.& IP multicast routing protocols: DVMRP,
PIM Version 2 (Sparse Mode & Dense Mode), IGMP v1,v2,v3
Should have Enterprise Services feature set with support for protocols like
Multiprotocol Label Switching (MPLS), Ethernet over MPLS (EoMPLS) & Virtual
Route Forwarding (VRF)
The router should support multiple level of privileges and authentication for user
access, along with SSH support for secured device access
Should support authentication protocol for AAA
The software should support Network Address Translation (NAT) and Port Address
Translation (PAT)
Should support source and destinations based ACLs, time based ACLs, VLAN /
Port-based ACLs
Should support MD5 authentication for routing protocols
The router should support 3DES and AES encryption standards
Must have IPSec Protocols: IPsec standards supported include Digital Encryption
Standard (DES), Triple DES (3DES), and Advanced Encryption Standard (AES;
128, 192, and 256) for encryption; Rivest, Shamir, Aldeman (RSA) algorithm
signatures and Diffie Hellman for authentication; and Secure Hash Algorithm 1
(SHA-1) or Message Digest Algorithm 5(MD5) hashing algorithms for data integrity
with the cryptographic engine in the router.
Support Detection of and response to distributed-denial-of-service (DDoS) attacks
Support source-based filtering which provide wire-rate, real-time defense against
DDoS attacks
Support routing peers validation, enhances routing stability, and overload protection
by using MD5 peer authentication and redistribution protection
Should support RSVP
The router should be able to support IP precedence
Bidder should submit BOQ of proposed device including the details part numbers
and Manufacturer warranty.
Bidder should submit the required performance document for the proposed device.
206
Section VI. Technical Requirements
Description
Warranty
Required Technical Specification
Bidder should quote mentioning manufacturer's warranty and part number and
minimum 3 (Three) years full replacement warranty should be provided for this unit
from the date of successful commissioning
2.1.14 Internet Router
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
Enclosure Type
Router
Processor Type
Service Support
Routing
Performance:
DRAM
Flash Memory
Status
Indicators
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Rack-mountable - modular
High-performance multi-core processors
Device should support data, voice and video services
Minimum throughput of 1Gbps and upgradeable to 2 Gbps.
Module-to-Module communication without compromising router performance.
Minimum 2 GB (installed) and upgradeable to Minimum 4 GB
Minimum 512 MB (installed) and upgradeable to Minimum 4 GB
Link activity, power
Minimum 4 x 10/100/1000Base-T - RJ-45, Routing Ports
Minimum 8 x 10/100/1000Base-T- RJ-45 Switch ports
Management : 1 x console
Serial : 1 x auxiliary - RJ-45
USB : minimum 1 x USB 2.0 Type A
Minimum 2 x SFP (mini-GBIC) for optical interface provision in future if required
Should support inbuilt Stateful Firewall & Intrusion Prevention
Interfaces
Security:
Data
Protocol
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Link
Protocols
Encapsulations
Traffic
management
Expansion Slots
Ethernet, Fast Ethernet, Gigabit Ethernet.
IPv4, IPv6, static routes, Open Shortest Path First (OSPF), Border Gateway Protocol
(BGP), BGP Router Reflector, Intermediate System-to-Intermediate System (IS-IS),
Multicast Internet Group Management Protocol (IGMPv3), Protocol Independent
Multicast.
Generic routing encapsulation, Ethernet, 802.1q VLAN, Point-to-Point Protocol,
High-Level Data Link Control (HDLC), Serial (RS-232, RS-449, X.21, V.35)
QoS, Class-Based Weighted Fair Queuing, Weighted Random Early Detection,
Hierarchical QoS, Policy-Based Routing (PBR), Performance Routing, and Network
base Application inspection and treatment.
Minimum 3 WAN/LAN Interface Slots
Minimum 2 Service Module Slots
Section VI. Technical Requirements
Description
Monitoring
Power Device
Redundant
power supply
Rack-mount
Manufacturer
part number
Warranty
2.1.15
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
Architecture
Performance:
DRAM
Flash Memory
Interfaces
Requirements
Expansion Slots
Security
Data Link
Protocol
207
Required Technical Specification
Should have SNMP, RMON, Syslog,
GUI Management, Telnet and SSH
Should have capability to monitor events and take informational, corrective,
Should have Network Flow Statistic , IP Service Level feature
Power supply - internal
Should have redundant power supply
Standard 19 inch rack mountable
Bidder should submit BOQ of proposed device including the details part numbers
and Manufacturer warranty.
Bidder should submit the required performance document for the proposed device.
Bidder should quote mentioning manufacturer’s warranty and part number and
minimum 3 (Three) years full replacement warranty should be provided for this unit
from the date of successful commissioning.
iSCSI WAN Router
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Should be chassis based & modular architecture for scalability and should be a single
box configuration for ease of management.
Should have hardware based IPSEC VPN (3DES/AES) Encryption card. Should
support IPSEC VPN, Firewall & SSL VPN features.
Router should be quoted with AC power supply.
Should have a throughput of minimum 200 Mbps and upgradeable to 300 Mbps
Minimum 1 GB (installed) and upgradable to minimum 2 GB
Minimum 512 MB (installed) and upgradable to minimum 4 GB
Minimum 3 x 10/100/1000Base-T - RJ-45, Routing Port
Minimum 8 x 10/100/1000Base-T- RJ-45 Switch ports
Management : 1 x console
USB : Minimum 1 x USB 2.0 Type A
Minimum 3 WAN Interface Slots.
Minimum 1 Service/Network Module Slots
Embedded hardware-based cryptography acceleration (IPSec +Secure Sockets Layer)
Should have Dynamic VPN to connect remote VPN devices
Should support IPsec Stateful Failover
Ethernet, Fast Ethernet, Gigabit Ethernet.
208
Section VI. Technical Requirements
Description
Supported
Interfaces
Required Technical Specification
T1/E1, Channelized E1/T1, FXS, FXO, VDSL2/ADSL/2/2.
Up to 14 port L2 and L3 Switch module support
IPv4, IPv6, static routes, Open Shortest Path First (OSPF), Border Gateway Protocol
(BGP), BGP Router Reflector, Intermediate System-to-Intermediate System (IS-IS),
Multicast Internet Group Management Protocol (IGMPv3), Protocol Independent
Protocols
Multicast sparse mode (PIM SM), PIM Source Specific Multicast (SSM), Distance
Vector Multicast Routing Protocol (DVMRP), IPv4-to-IPv6 Multicast, MPLS, Layer
2 and Layer 3 VPN, IPSec, Layer 2 Tunneling Protocol Version 3 (L2TPv3).
Generic routing encapsulation, Ethernet, 802.1q VLAN, Point-to-Point Protocol,
Encapsulations
High-Level Data Link Control (HDLC), Serial (RS-232, RS-449, V.35).
QoS, Class-Based Weighted Fair Queuing, Weighted Random Early Detection,
QoS Features: Hierarchical QoS, Policy-Based Routing (PBR) or similar technology, Performance
Shall
support Routing, and Network base Application inspection and treatment.
the following
Shall support WAN traffic optimization feature with internal module / external
device
Monitoring
Should have Telnet, SSH, SNMP, Remote Monitoring (RMON).
Bidder should submit BOQ of proposed device including the details part numbers
Manufacturer
and Manufacturer warranty.
part number
Bidder should submit the required performance document for the proposed device.
Bidder should quote mentioning manufacturer’s warranty and part number and
Warranty
minimum 3 (Three) years full replacement warranty should be provided for this unit
from the date of successful commissioning.
2.1.16 Extranet Switch
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
Switch
Architecture
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
The Switch should have at least 16 x 1GE SFP port for downlink switches
Bidder should propose at least 10 x 1G Single-mode SFP modules for each switch
and minimum 6 x 1G Copper Module. All the cables and accessories should be
included.
The Switch should support Redundant Power Supplies
The Switch should be Stackable and all the required components for stacking should
be included.
The Switch Architecture should be able to Stack at least 4 Switches together.
The Switch stack should be based on Distributed forwarding Architecture, where in
each stack member forwards its own information on network.
The Switch Stack Architecture should have centralized control and Management
Section VI. Technical Requirements
Description
Switch
Performance
Layer 3
Features
Layer 2
Features
Network
Security
Features
Quality of
209
Required Technical Specification
plane with Active Switch and all the information should be Synchronized with
Standby Switch.
The Switch should support Stateful Switchover (SSO) when switching over from
Active to Standby switch in a Stack.
The Switch should have USB for OS Management (uploading, downloading &
booting of OS and Configuration)
The Switch should have at least 1x 10/100/1000 dedicated Ethernet Management
Port
The Switch should have at least redundant fans and incase of failure of any one of
those the other fan should automatically speed up. Fans should be field replaceable.
The Switch should have power savings mechanism wherein it should reduce the
power consumption on ports not being used.
The switch should be Rack Mountable and should not take space more than 1RU.
The Switch should have at least 60Gbps nonblocking switching bandwidth.
The switch should have at least 40Mpps of forwarding rate.
The Switch should have at least 80Gbps Stack Bandwidth.
The Switch should support at least 31,000 MAC Addresses
The Switch should support at least 4,000 VLAN ID's
The Switch should support 9198 bytes of Jumbo Frames
The switch should support routing protocol such OSPF.
The Switch should support IPv6 Routing capable protocols such as OSPFv3 in
hardware.
The Switch should support IP Multicast and PIM, PIM Sparse Mode, PIM Dense
Mode, PIM Sparse-dense Mode & Source-Specific Multicast.
The switch should support basic IP Unicast routing protocols (static, RIPv1 &
RIPv2) should be supported.
The switch should support IPv6 & IPv4 Policy Based Routing (PBR)
The switch should support 802.1d, 802.1s, 802.1w Spanning-Tree &its Enhancement
for fast convergence.
The switch should support 802.1q VLAN encapsulation.
The switch should support 802.3ad (LACP) to combine multiple network links for
increasing throughput and providing redundancy.
The switch should have Port security to secure the access to an access or trunk port
based on MAC address to limit the number of learned MAC addresses to deny MAC
address flooding.
The switch should support DHCP snooping to prevent malicious users from spoofing
a DHCP server and sending out rouge addresses.
The switch should support Secure Shell (SSH) Protocol, Kerberos, and Simple
Network Management Protocol Version 3 (SNMPv3) to provide network security by
encrypting administrator traffic during Telnet and SNMP sessions.
The switch should support Bridge protocol data unit (BPDU) Guard to shut down
Spanning Tree PortFast-enabled interfaces when BPDUs are received to avoid
accidental topology loops.
The switch should support Spanning Tree Root Guard to prevent edge devices not in
the network administrator’s control from becoming Spanning Tree Protocol root
nodes.
The Switch should support Advanced Modular QoS Policies
210
Description
Service (QoS)
& Control
Manufacturer
part number
Warranty
Section VI. Technical Requirements
Required Technical Specification
The Switch should be capable of Queuing, Policing, Shaping and marking Wired and
Wireless Traffic based on Class of Service (CoS) or DSCP.
The switch should support 802.1p CoS and DSCP Field classification using marking
and reclassification on a per-packet basis by source and destination IP address, MAC
address, or Layer 4 Transmission Control Protocol/User Datagram Protocol
(TCP/UDP) port number.
The Switch should support Rate limiting based on source and destination IP address,
source and destination MAC address.
Bidder should submit BOQ of proposed device including the details part numbers
and Manufacturer warranty.
Bidder should submit the required performance document for the proposed device.
Bidder should quote mentioning manufacturer's warranty and part number and
minimum 3 (Three) years full replacement warranty should be provided for this unit
from the date of successful commissioning
2.1.17 SAN Director Switch
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
Features
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
The fiber channel switch must be rack-mountable Thereafter, all reference to the
‘switch’ shall pertain to the ‘fiber channel switch’
The switch must be able to support port requirements from a minimum of 192 Fiber
Channel ports and scalable to 384 ports.
All ports must include 16/8 G FC transceivers.
Number of ports to be provided in the solution are the following:
i) 144 units of 16 Gbps port with transceivers (including 2 units minimum 70KM
Supported LW transceivers having maximum available speed) and required fiber
Cables.
ii) 48 units of 8 Gbps ports with transceivers and required fiber cables.
The switch must be able to provide 1024G of bandwidth per slot. The switch must
have non – blocking architecture.
The switch must support line rate minimum 16 Gig FC ports on all the slots.
The proposed director must have redundant hot swappable supervisor and Fabric
modules.
The switch must support the following modules types:
2/4/8/16 Gbps or 10 Gbps FC Module
10 Gbps FCoE Module
All FC ports for device connectivity should be 2/4/8/16 Gbps auto-sensing Fiber
Section VI. Technical Requirements
Description
211
Required Technical Specification
Channel ports.
The switch module must support local switching across the entire 48-ports on a
module as one local switched domain.
The switch must have hot-swappable redundant power supply & fan module without
resetting the switch, or affecting the operations of the switch.
The switch must be able to support non-disruptive software upgrade.
The switch must be able to support stateful process restart.
The switch must be capable of creating multiple hardware-based isolated Virtual
Fabric (ANSI T11) instances. Each Virtual Fabric instance within the switch should be
capable of being zoned like a typical SAN and maintains its own fabric services,
zoning database, Name Servers and FSPF processes etc. for added scalability and
resilience.
The switch must support graceful process restart and shutdown of a Virtual Fabric
instance without impacting the operations of other Virtual Fabric instances.
The switch must support Virtual Fabric instance 1 to 4094.
The switch shall support hot-swappable Small Form Factor Pluggable (SFP) LC typed
transceivers.
The switch must support hardware ACL-based Port Security, Virtual SANs (VSANs),
Port Zoning and LUN Zoning
Inter-switch links must support the transport of multiple Virtual Fabrics between
switches, whilst preserving the security between Virtual Fabrics.
The switch shall support FC-SP for host-to-switch and switch-to-switch
authentication.
The switch shall support the following Management Access Control
-SSHv2
-SNMPv3
-IP ACLs
The switch must support the following fabric services:
Name server
Internet Storage Name Server (iSNS)
Registered State Change Notification (RSCN)
Login services
Fabric Configuration Server (FCS)
Public loop
Broadcast
In-order delivery
The switch must support port mirroring for Fiber Channel, such that traffic going to a
specific port can be mirrored and forwarded to another port for analyzing.
The switch must be able to immediately recover in the event of a failed forwarding
path going via an alternative path.
The switch must also support load balancing across multiple paths through the fabric
via Fabric Shortest Path First (FSPF).
Using FSPF, the switch must be able to load balance up to 16 equal cost paths across
the SAN network.
The switch must support port aggregation of up to 16 physical Fiber Channel ports
into a single aggregated link. The aggregated ports must NOT be consecutive ports on
a line card.
212
Description
Section VI. Technical Requirements
Required Technical Specification
The switch must support the aggregation of any ports from any module.
Forwarding traffic must not be impacted when an individual ISL connection within an
aggregated link goes down.
FSPF must not re-converge when an individual ISL connection within an aggregated
link goes down.
The switch must be able to load balance traffic through an aggregated link with Source
ID and Destination ID. The support for load balancing utilizing the Exchange ID must
also be supported.
The switch must be equipped with congestion control mechanisms such that it is able
to throttle back traffic away from a congested link.
The switch must be capable of discovering neighboring switches and identify the
neighboring Fiber Channel switches.
The switch must support TACACS+ or RADIUS authentication when managing from
GUI, console or telnet to prevent unauthorized access
The switch must support Secure Shell Version 2 (SSHv2) with AES to provide
additional security for Telnet sessions to the switch.
The switch must support multilevel security on console access prevents unauthorized
users from altering the switch configuration.
The switch must support role-based administration by allowing different
administrators different access rights to the switch. Role-based access control will use
RADIUS or TACACS+ AAA functions.
The switch must support FICON CUP Management as an option with license.
The switch must support VRRP for management connections.
The switch must support SNMPv3 with AES for secured management access.
Switch must support Fiber Channel Traceroute and Fiber Channel Ping for ease of
troubleshooting and fault isolation. In addition, the switch must also support the
following diagnostics.
Power-on-self-test (POST) diagnostics
Online diagnostics
Internal loopbacks
Fabric Analyzer
SPAN
FC Debug
Syslog
Port level statistics
Real-Time Protocol (RTP) Debug
Switch must support out-band management protocols like SNMP, SNMPv3, SMI-S,
Telnet, FTP and SFTP.
The switch must support the use of an external port analyzer, which is able to convert
Fiber Channel frames to Ethernet frames so as to use a conventional Ethernet based
packet analyzer to capture the traffic and analyze it as Fiber Channel.
For switch management, the management software must support both Fabric wide and
Device level management without the additional purchase of software.
The switch must support SNMPv3—via Ethernet port and in-band IP-over-FC access
The Fabric Manager software must be able to perform
GUI based management, configuration and diagnostics.
Discovery and Topology Mapping
Section VI. Technical Requirements
Description
Warranty
213
Required Technical Specification
Fabric View
Summary View
-Physical View
-Monitoring and Alerts
-Network Diagnostics
-Configuration Wizards
Bidder should quote mentioning manufacturer's warranty and part number and
minimum 3 (Three) years full replacement warranty should be provided for this unit
from the date of successful commissioning
2.1.18 Email Security for Microsoft Exchange
Description
Quality
Certification
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
Model
To be mentioned by the bidder
Country of Origin USA or EU
Country of
To be mentioned by the bidder
Assemble /
Manufacture
The device should have 6000 licenses for Email security control with minimum
of 3 years subscription.
The device should be capable of 10000 or more users capacity.
OEM of solution provider should have broad visibility and a large footprint,
Global
threat including:
 50/More terabytes (TB) of security intelligence daily
intelligence
 1.5 million/More deployed security devices including firewalls, IPS sensors,
and web and email appliances
 100 million/More endpoints
 10/More billion web requests per day and zero-hour attacks
Email security appliance should support anti spam with multilayered defense
Should support inner and outer layer of filtering
Should be capable of working with the reputation of the sender
Should performs a deep analysis of the message
Spam Protection
Minimum 80 percent of spam should be blocked before it even hits network
Should support contextual analysis
Should be able to do auto classification
Should have capability to filters based on the sender or subject
Should filters defend against emerging threats and blended attacks
Should be able to issue rules on any combination of six parameters, including
file type, file name, file size and URLs in a message
Outbreak filters
Should have capability to modify rules and release messages from quarantine
accordingly
Should be capable to rewrite URLs linked in suspicious messages
Website content should be actively scanned
Brand
214
Section VI. Technical Requirements
Description
Required Technical Specification
Should detect graymail from sources like marketing, social networking, and bulk
messages
The safe unsubscribe solution provides:
 Protection against malicious threats masquerading as unsubscribe links
 A uniform interface for managing all subscriptions
 Better visibility for email administrators and end users into such emails
Appliances should be capable of supporting Advance Malware protection in
future in a same appliance
Should have future capability of file reputation scoring and blocking, static and
dynamic file analysis (sandboxing), and file retrospection for the continuous
analysis of threats, even after they have traversed the email gateway
Appliance-based solution with a proprietary hardened OS
4 gigabit Ethernet and 2 Ten gigabit fiber Ethernet interfaces for email security
solution. Ten Gigabit port should be populated with short range transceiver from
day one. Transceiver and appliance should be same OEM product.
Multiple hard-drives in RAID -10
Hardware
and Total drive space available at least 1.6TB/More
32 GB of RAM
support
2 x 6 (2 hexa cores)
Rack mount chassis
Vendor support access through e-mail, telephone, website
Access to vendor support portal and knowledgebase
Full hardware warranty throughout the support contract period
Should be able to Delivers high performance, comprehensive DLP helping
prevent leaks, enforce compliance, and protect brand and reputation. One or
more predefined policies (several options to choose from) to help prevent
confidential data from leaving the network. It should be able to use parts of those
DLP
predefined policies to create own custom policies. The built-in email DLP
Manufacturer
engine uses data structures along with own optional data points such as words,
part number
phrases, dictionaries, and regular expressions to quickly create accurate policies.
Bidder should submit BOQ of proposed device including the details part
numbers and Manufacturer Warranty.
Bidder should submit the required performance document for the proposed
device.
Bidder should quote mentioning manufacturer's warranty and part number and
Warranty
minimum 3 (Three) years full replacement warranty should be provided for this
unit from the date of successful commissioning
2.1.19 Notebook Computer
Description
Quality
Certification
Required Technical Specification
To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
Model
To be mentioned by the bidder
Country of Origin USA or EU
Brand
Section VI. Technical Requirements
Description
Country of
Assemble /
Manufacture
Display
Processor
Memory
Storage
Graphics and
Video Support
Camera
Connections and
Expansions
Wireless
Audio
Keyboard and
Trackpad
Battery and
Power
215
Required Technical Specification
To be mentioned by the bidder
Retina display: Minimum 13.3-inch (diagonal) LED-backlit display with IPS
technology. Minimum 2560-by-1600 resolution at 227 pixels per inch with
support for millions of colours
Native resolution: Minimum 2560 by 1600 pixels (Retina);
Minimum scaled resolutions: 1680 by 1050, 1440 by 900, and 1024 by 640
pixels
Minimum 3.1GHz dual-core Intel Core i7 (Turbo Boost up to 3.4GHz) with
4MB shared L3 cache.
Minimum 8GB of 1866MHz LPDDR3 onboard memory and configurable to
16GB
Minimum 512GB PCIe-based flash storage and configurable to 1TB flash
storage.
Intel Iris Graphics 6100 or better
Dual display and video mirroring: Simultaneously supports full native resolution
on the built-in display and up to 3840 by 2160 pixels on up to two external
displays, both in millions of colours
Thunderbolt digital video output
Native Mini DisplayPort output
DVI, VGA, dual-link DVI, and HDMI output supported using Mini DisplayPort
adapters
HDMI video output
Should support for 1080p resolution at up to 60Hz
Should support for 3840-by-2160 resolution at 30Hz
Should support for 4096-by-2160 resolution at 24Hz
Minimum 720p FaceTime HD camera
Minimum One MagSafe 2 power port
Minimum Two Thunderbolt 2 ports (up to 20Gb/s)
Minimum Two USB 3 ports (up to 5Gb/s)
Minimum One HDMI port
Minimum One Headphone port
802.11ac Wi-Fi wireless networking; IEEE 802.11a/b/g/n compatible
Bluetooth 4.0 wireless technology
Stereo speakers
Dual microphones
Headphone port
Support for Apple iPhone headset with remote and microphone
Support for audio line out (digital/analog)
Full-size backlit keyboard with 78 (US) or 79 (ISO) keys, including 12 function
keys and four arrow keys (inverted ‘T’ arrangement) with ambient light sensor
Force Touch trackpad for precise cursor control and pressure-sensing
capabilities; enables Force click, accelerators, pressure-sensitive drawing and
Multi-Touch gestures
Up to minimum 10 hours wireless web
Up to 12 hours iTunes movie playback
216
Section VI. Technical Requirements
Description
Required Technical Specification
Up to minimum 30 days of standby time
Built-in minimum 74.9-watt-hour lithium-polymer battery
Minimum 60W MagSafe 2 Power Adapter with cable management system;
MagSafe 2 power port
Line voltage: 100V to 240V AC
Electrical and
Operating Frequency: 50Hz to 60Hz
Operating
Operating temperature: 10° to 35° C (50° to 95° F)
Requirements
Storage temperature: –25° to 45° C (–13° to 113° F)
Relative humidity: 0% to 90% noncondensing
Operating System OS X El Captain.
OS Supported
Microsoft Windows 10
One MagSafe 2 Power Adapter
One set AC wall plug and Power cord
One Mini DisplayPort to VGA Adapter. Compatible with Mac computers with
Accessories
Mini DisplayPort and Thunderbolt ports
Requirements
One Thunderbolt to Gigabit Ethernet Adapter: Apple Thunderbolt to Gigabit
Ethernet Adapter with built-in Thunderbolt cable, compatible with OS X v10.7.4
or later
Brenthaven Collins Slim Brief Bag, Quantity: Thirty for thirty notebook
computers. Color: Blue (15 units) and Grey (15 units)
Quilted pockets for iPad and up to a 15-inch MacBook
Quick-access pocket for iPhone
Mobile battery compartment for easy charging
Removable shoulder strap
Soft, durable chambray exterior
Vegan leather trim (PVC free)
Carrying Case
A separate compartment holds a battery or charger for powering devices on the
go.
Part Number: UPC or EAN No.: 730791195400
Form Factor: Brief Case, Shoulder Bag, Shoulder Case
Material: Cotton, Synthetic, Vegan Leather
Height: 34.29 cm/13.5 in.
Width: 5.08 cm/2 in.
Length: 43.18 cm/17 in.
Bidder should quote mentioning manufacturer's warranty and part number and
Warranty
minimum One (01) year full replacement warranty should be provided for this
unit from the date of successful commissioning
2.2
Network and Communications Specifications
All branches of Bangladesh Bank have local area network (LAN) and are connected via Wide
Area Network (WAN). Users are using centrally managed internet facility.
2.3
Software Specifications
2.3.1 System Software and System-Management Utilities:
2.3.2 Networking and Communications Software: Not applicable
Section VI. Technical Requirements
217
2.3.3 General-Purpose Software:
2.3.4 Database Software and Development Tools: Not applicable
2.3.5 Business Application Software: Not applicable
2.4
System Management, Administration, and Security Specifications
2.4.0
General Requirements: In addition to the management, administration, and security
requirements specified in each sections covering the various hardware and software
components of the System, the System must also provide for the following
management, administration, and security features at the overall system level.
2.4.1
Technical management and troubleshooting: Supporting management software will
be capable to provide performance monitoring and diagnostic tools giving
immediate system information.
2.4.2
User and usage administration: Infrastructure as a service solution should be capable
to manage users and usage of delivered hardware.
2.4.3
Security: The system must have full security facilities to control access to data and
processing at each terminal meeting C-2 security standards. Security and encryption
means used by the system must comply with international standards.
2.5
2.5.1
Service Specifications
System Integration: Different application system will be deployed in the delivered
hardware. Proper functioning of the delivered hardware is the key to integrate
systems.
2.5.2 Training and Training Materials:
All training should be conducted by the certified trainers with prior approval from the
Purchaser. Necessary stationery required for the training shall be arranged by the Bidder, at
its own cost.
Training must be conducted by OEM authorized trainer only. Original Training materials
must be provided to all participants along with training completion certificate from OEM so
that participant can sit for certification.
For Local Training vendor must confirm the facility of high bandwidth internet for labs,
snacks for morning and evening along with standard lunch and dedicated classroom
environment during the training period.
For overseas/foreign training, the Bidder/vendor must include and confirm both way air
ticket, Hotel accommodation, Food, Training Fees, per diem (US$ 100/day/per participant),
both way airport to hotel transfer etc.
The Bidder/Vendor must take concern from contractor/customer while scheduling training
and there must be time gap between training modules.
218
Section VI. Technical Requirements
Training Course Description
Training on Offered Firewall, IPS, AVC, URL
Filter, Web security, Content Filter installation,
configuration, troubleshooting, maintenance etc.
Training on Load balancer, Bandwidth Manager
installation,
configuration,
troubleshooting,
maintenance etc.
Training on Router installation, configuration,
troubleshooting, maintenance etc.
Training on Application Centric Infrastructure
installation,
configuration,
troubleshooting,
maintenance etc.
Training on Data Center Networking
Number
of
Trainee
Minimum
Course Length
(6 hours/day)
Location
6
30 hours Malaysia/
Singapore
6
30 hours Malaysia/
Singapore
10
6
10
24 hours Local
30 hours Malaysia/
Singapore
72 hours Local
2.5.3 Technical Support:
2.5.3.1 Warranty Service:
All Hardware equipment and Software should have a warranty period that is in conformance
with the specifications supplied in the Technical Specification. During the warranty Period,
the Bidder will be responsible for the repair, replacement, support of all malfunctioning
equipment and software supplied under this Bid.
The Bidder shall provide on-site support for warranty Period. Repair and replacement of
equipment should be completed to the satisfaction of the Purchaser within the times specified
in Maintenance Service Level (section 2.5.3.2.)
a)
The Bidder should provide proper documentation from product manufacturer
that conforms 24x7x365 online support
b)
The Bidder should provide hot-line support.
c)
The Bidder will have to undertake immediate repair actions in the event of
software/hardware failure causing an interruption of operation of the DC,
NDC and DRS systems.
d)
The Bidder must notify about all the detected software errors and correct them
in a shortest possible time.
e)
The Bidder should offer the new versions/releases of software and supervise
their implementation in mutually agreed deadlines.
f)
The Bidder should enter into the obligation that in the event he releases a new
version of software, and the Purchaser is using one of the previous versions, he
will provide the full scope of services to the version used by the Purchaser for
the period of at least 5 years from the date it was purchased.
g)
The software service must be conducted in a manner not compromising the
security of Bank's data and not compromising the quality of operation of the
Bank, particularly the services rendered to customers (Banks).
Section VI. Technical Requirements
h)
i)
219
The Bidder should ensure maintenance support between the guaranteed
resolution times mentioned in the Service Levels. Failing of the resolution
time, a penalty of one half of one percent (0.5%) of the cost of the related units
shall be charged per day for nonconformance of the supplied Hardware,
Software and services.
The Bidder must submit as part of their proposal a detailed plan including
required manpower to support the supplied Hardware and Software.
Manpower can be changed with the advance approval of the Purchaser.
The bidder should maintain the following user support:
a. The Bidder must have service capability in Bangladesh Bank offices (Dhaka and
Rajshahi).
b. A suitable Helpdesk and Service Center must be established to ensure a high level
of service. Manpower requirements for Helpdesk and Service Centers shall be
specified by the Bidder. The Helpdesk shall be located at the Bangladesh Bank
Head Office premises. Necessary facilities (such as office accommodation,
telephone etc.) will be provided by the Purchaser.
c. The Bidder should provide trained, experienced and certified technical manpower
for onsite support in the Bangladesh Bank during all days.
d. Service records must be maintained at the Helpdesk for both hardware and
software warranty support. In addition, calls to the Helpdesk must be tracked
including the disposition and subsequent resolution of problem. These records are
to be reviewed monthly with the Purchaser.
e. A satisfactory stock of spare parts/ complete units (list of spare parts/complete
unit should be attached with proposal) must be maintained for support of all
items supplied in this tender. An inventory stock of spare parts status should be
maintained and reviewed by the Purchaser on a monthly basis.
f. Availability of all parts must be assured for a minimum of the same version or
compatible higher version for five (05) years from the date of system acceptance.
g. The Bidder is responsible for notification and installation/upgrade of new
versions/releases of software/firmware and patch within mutually agreed
timeframes.
2.5.3.2. Maintenance Service:
The Bidder must ensure (through evidences) that their respective Local Agents are capable of
maintaining Service Levels as described below:
A. Within Dhaka City:
Item
Routers, Switches, Firewalls, Content Filters etc.
Software
Spare replacement
warranty Period
Response Time Resolution Time
02 Hours
24 Hours
02 Hours
24 Hours
02 Hours
04 Hours
220
Section VI. Technical Requirements
B. Rajshahi City:
Item
warranty Period
Response Time Resolution Time
Routers, Switches, Firewalls, Content 02 Hours
48 Hours
Filters etc.
Software
02 Hours
48 Hours
Spare replacement
02 Hours
24 Hours
2.5.3.3 Technical Assistance: The Bidder should provide minimum one Graduate
Engineers having ICT related degree and a minimum of five (05) years of proven
experience in respective field (such as Firewall, Content Filter, Router, Spine
Switch, SAN Switch etc.) for Head Office in Dhaka.
2.5.3.4 Post- warranty maintenance services: Not required.
2.5.4
2.6
2.6.1
Network Migration: Existing network environment will be migrated to the proposed
network environment using IPv4 initially and IPv6 subsequently.
Documentation Requirements
The Bidder should provide detail information regarding the documentation that will
be supplied with the system. The following minimum documentation (hard copy and
soft copy) on the proposed systems must be made available in English:
A. Project Documentation
1. Project Management Controls
2. Project Plans
3. Implementation Controls
4. Quality Controls
5. Scope Management Controls
6. Progress Reports
B. System Documentation
1. Requirement Specifications
2. Technical Specifications
3. System Descriptions & Specifications
4. Installation Manuals
5. System Administration Guide
6. Maintenance Documentation
C. User Documentation
1. Training Requirements
2. Training Documentations
3. User Guides
4. Administrator Documentations
Section VI. Technical Requirements
5.
6.
7.
8.
221
Transaction Processing Guidelines
Operational Processing Guidelines
Operational Procedures
Error Correction Procedures
D. Testing Specifications
2.6.2. Updates:
1. The Bidder/Vendor must assure on-going documentation updates
2. The Bidder/Vendor must supply the documentation of the applications on optical
disks or other digital media together with the system for its updating as changes
are introduced
2.6.3. Technical Documents (Hard copy and Soft Copy):
1.
2.
3.
4.
Documentation should be consistent with international standards
Documentation should be user-friendly
Documentation should be indexed
Diagrams and schematics should be provided where possible to facilitate
practical understanding.
Technical documentation appropriate to the hardware and systems that are being
provided must be made available in both hard copy and soft copy (CD-ROM). A
commitment to providing updated versions must be given.
2.7
Consumables and Other Recurrent Cost Items
Consumables are not required.
2.8
Other Non-IT Goods
223
D. TESTING AND QUALITY ASSURANCE REQUIREMENTS
3.1
3.2
Inspections
3.1.1
Factory Inspections: No specific factory inspection visits are envisaged
involving the client. The bidder is responsible for ensuring that all items have
been properly inspected at the factory. The purchaser may arrange Preshipment Inspection through international inspection agent at his cost
3.1.2
Inspections following delivery: The Bidder is to confirm that all items are to
be fully tested following delivery on site. This is to include operational testing
of software and commissioning of hardware. The Purchaser may impose
physical inspection of all or any item(s) at its discretion.
Pre-commissioning Tests
3.2.1
In addition to the Supplier’s standard check-out and set-up tests, the Supplier
(with the assistance of the Purchaser) must perform a thorough tests on the
Software System before Installation will be deemed to have occurred and the
Bidder will be required to confirm that this has been successfully completed in
a certification letter. On receipt and on satisfactory review of the contents, the
Purchaser will issue the Installation Certificate(s) (pursuant to GCC Clause 26
and related SCC clauses).
3.2.2 The Entire System: Pre-commissioning Tests for the entire System are required
to ensure that the system is fully functioning in the way specified. The supplier
will use test data supplied by the Purchaser and will need to demonstrate to the
Purchaser that all functions are operational and functioning correctly.
3.2.3. The Supplier will be responsible for preparing and agreeing with the Purchaser
a comprehensive operational testing plan for this purpose.
3.3
Operational Acceptance Tests
3.3.0
Pursuant to GCC Clause 27 and related SCC clauses, the Purchaser (with the
assistance of the Supplier) will perform the following tests on the System and
its Subsystems following Installation to determine whether the System and the
Subsystems meet all the requirements mandated for Operational Acceptance.
The Bidder/Supplier will be responsible for preparing and agreeing with the
Purchaser a comprehensive operational testing plan for this purpose.
224
Section VI. Technical Requirements
E. IMPLEMENTATION SCHEDULE
Section VI. Technical Requirements
225
1.1.
Implementation Schedule Table
System, Subsystem, or lot number: Entire System procurement
Desired installation and acceptance dates for all items in Schedule below, modifying the sample line items and sample table entries as
needed. All periods are measured in weeks from the signing of Contract Award.
Line
Item
No.
1
1.1
2
2.1
2.2
3.0
3.1
4.0
4.1
5.0
Note:
Subsystem / Item
Contract Signing
Project Plan
Head Office Data Center, Motijheel,
Dhaka
Hardware
and
General-Purpose
Software
Training
BBTA Data Center (NDC), Mirpur,
Dhaka
Hardware
and
General-Purpose
Software
Rajshahi Disaster Recovery Site
Hardware
and
General-Purpose
Software
Operational Acceptance of the System as
an integrated whole
Configuration
Table No.
Site / Site
Code
--
--
1
R1.1
1
Delivery
(Bidder to
specify in the
Preliminary
Project Plan)
Installation
(weeks from
Effective Date)
Acceptance
(weeks from
Effective Date)
Liquidated
Damages
Milestone
---
W0
W6
--
No
Yes
--
“
W16
W20
Yes
1
2
“
R1.2
--
W26
No
2
“
W20
W22
Yes
3
“
R2.1
“
W24
W26
Yes
--
all sites
--
W28
Yes
W0
W2
Refer to the System Inventory Table(s) below for the specific items and components that constitute the Subsystems or item. Refer to the
Site Table(s) below for details regarding the site and the site code.
- - indicates not applicable. “ indicates repetition of table entry above.
226
Section VI. Technical Requirements
1.2.
System Inventory Table (Supply and Installation Cost Items)
System, Subsystem, or lot number: Entire System procurement
Line item number: Relevant line item number from the Implementation Schedule (e.g., 1.1)
The detailed components and quantities in the System Inventory Table below for the line item specified above, modifying the sample
components and sample table entries as needed.
Component
No.
1.
1.1
1.1.1
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7
1.1.8
1.1.9
1.1.10
1.1.11
1.1.12
1.1.13
1.1.14
1.1.15
1.1.16
Component
Hardware and Software
Head Office Data Center, Motijheel, Dhaka
Network Spine Switch
Network Leaf Switch Type-A
Network Leaf Switch Type-B
Network Aggregation Switch
Campus Distribution Switch for DC
Server Farm Firewall
Extranet Firewall
Internet Firewall
Application Load Balancer
Bandwidth Manager
Content Filter
WAN Router
Extranet Router
Internet Router
iSCSI WAN Router
Extranet Switch
Relevant Technical
Specifications
No.
2.1.1.
2.1.2.
2.1.3.
2.1.4.
2.1.5.
2.1.6.
2.1.7.
2.1.8.
2.1.9.
2.1.10.
2.1.11.
2.1.12.
2.1.13.
2.1.14.
2.1.15.
2.1.16.
Additional Site Information
(e.g., building, floor,
department, etc.)
Quantity
-Annex-2 Building
“
“
“
“
“
“
“
“
“
“
“
“
“
“
“
“
--2
2
6
2
2
2
2
2
4
2
2
2
2
2
2
2
Section VI. Technical Requirements
Component
No.
1.1.17
1.1.18
1.1.19
1.1.20
1.1.21
1.1.21.1
1.1.21.2
1.1.21.3
1.1.21.4
1.1.21.5
1.2
1.2.1
1.2.2
1.2.3
1.2.4
1.2.5
1.2.6
1.2.7
227
Component
SAN Director Switch
Email Security for Microsoft Exchange
Notebook Computer
Network Migration
Training
Training on Offered Firewall, IPS, AVC, URL Filter, Web
security, Content Filter installation, configuration,
troubleshooting, maintenance etc.
Training on Load balancer, Bandwidth Manager
installation, configuration, troubleshooting, maintenance
etc.
Training
on
Router
installation,
configuration,
troubleshooting, maintenance etc.
Training on Application Centric Infrastructure installation,
configuration, troubleshooting, maintenance etc.
Training on Data Center Networking
BBTA Data Center (NDC), Mirpur, Dhaka
Network Spine Switch
Network Leaf Switch Type-A
Network Leaf Switch Type-B
Network Aggregation Switch
Server Farm Firewall
Extranet Firewall
Internet Firewall
Relevant Technical
Specifications
No.
Additional Site Information
(e.g., building, floor,
department, etc.)
Quantity
“
“
“
2.5.4
2
2
30
As required
2.5.2
2.5.2
As specified
2.5.2
As specified
2.5.2
As specified
2.5.2
As specified
2.1.17.
2.1.18
2.1.19
2.5.2
2.1.1.
2.1.2.
2.1.3.
2.1.4.
2.1.6.
2.1.7.
2.1.8.
BBTA Building
“
“
“
“
“
“
“
As specified
-2
2
6
2
2
2
2
228
Component
No.
1.2.8
1.2.9
1.2.10
1.2.11
1.2.12
1.2.13
1.2.14
1.2.15
1.2.16
1.2.17
2.1
2.1.1
2.1.2
2.1.3
Note:
Section VI. Technical Requirements
Component
Relevant Technical
Specifications
No.
Application Load Balancer
Bandwidth Manager
Content Filter
WAN Router
Extranet Router
Internet Router
iSCSI WAN Router
Extranet Switch
SAN Director Switch
Email Security for Microsoft Exchange
Disaster Recovery Site, Rajshahi
- - indicates not applicable. “ indicates repetition of table entry above.
2.1.9.
2.1.10.
2.1.11.
2.1.12.
2.1.13.
2.1.14.
2.1.15.
2.1.16.
2.1.17.
2.1.18
Additional Site Information
(e.g., building, floor,
department, etc.)
Quantity
“
“
“
“
“
“
“
“
“
“
Main Building
4
2
2
2
2
2
2
2
2
2
--
Section VI. Technical Requirements
229
1.3.
System Inventory Table (Recurrent Cost Items) (Not Used)
System, Subsystem, or lot number: Entire System procurement
Line item number: Relevant line item number from the Implementation Schedule (e.g., z.1)
The detailed components and quantities in the System Inventory Table below for the line item specified above, modifying the sample
components and sample table entries as needed.
Cost must reflect prices and rates quoted in accordance with ITB Clause 14 and 15. Unit prices for the same item appearing several times in
the table must be identical in amount and currency.
Component
No.
1.
1.1
1.2
1.3
2.
2.1
2.2
3.
3.1
Note:
Component
Relevant
Technical
Specifications No.
Hardware Maintenance
Y1
Y2
Y3
Y4
Y5
Y6
Incl. in
warranty
Incl. in
warranty
Incl. in
warranty
none
none
none
all items,
all sites
Incl. in
warranty
all items,
all sites
Incl. in
warranty
none
none
none
none
none
none
2.1.1
2.1.2
2.1.3
Software Licenses and Updates:
System and General-Purpose
Incl. in
Software
warranty
Application, Standard, and Custom
Incl. in
Software
warranty
…
Technical Services
…
- - indicates not applicable. “ indicates repetition of table entry above.
230
Section VI. Technical Requirements
1.4.
Site Table(s)
System, Subsystem, or lot number: Entire System procurement
Site
Code
Site
R1.1
Head Office, Motijheel, Dhaka
R1.2
BBTA, Mirpur, Dhaka
R2
Rajshahi Office, Rajshahi
City / Town / Region
Primary Street Address
Drawing
Reference No.
(if any)
Section VI. Technical Requirements
231
1.5.
Table of Holidays and Other Non-Working Days
The days for each month for each year that are non-working days, due to Holidays or other business reasons (other than weekends).
Month
January
February
March
April
May
June
July
August
September
October
November
December
2015
26
16
2016
2017
2018
21
17, 26
14
1, 21
3
6-7
15
13-15
11
21
17, 26
14
1
21
17, 26
14
1
12, 25, 16
25, 16
15
16
2019
2020
2021
2022
232
Section VI. Technical Requirements
F. REQUIRED FORMAT OF TECHNICAL BIDS
5.1
5.2
5.3
Description of Information Technologies, Materials, Other Goods, and Services
5.1.0
The Bidder must provide detailed descriptions of the essential technical,
performance, or other relevant characteristics of all key Information
Technologies, Materials, other Goods, and Services offered in the bid (e.g.,
version, release, and model numbers). Without providing sufficient clear
detail, Bidders run the risk of their bids being declared non-responsive.
5.1.1
To assist in the bid evaluation, the detailed descriptions should be organized
and cross referenced in the same manner as the Bidder’s item-by-item
commentary on the Technical Requirements described in Section 5.2 below.
All information provided by cross reference must, at a minimum, include clear
titles and page numbers.
Item-by-Item Commentary on the Technical Requirements
5.2.0
The Bidder must provide an item-by-item commentary on the Purchaser’s
Technical Requirements, demonstrating the substantial responsiveness of the
overall design of the System and the individual Information Technologies,
Goods, and Services offered to those Requirements, see ITB Clause 16.2 (b).
5.2.1
In demonstrating the responsiveness of its bid, the Bidder is strongly urged to
use the Technical Responsiveness Checklist provided in Section G of the
Technical Requirements. Failure to do so, increases significantly the risk that
the Bidder’s Technical Bid will be declared technically non-responsive.
Among other things, the checklist should contain explicit cross references to
the relevant pages in the Bidder’s Technical Bid.
Preliminary Project Plan
5.3.0
The Bidder must prepare a Preliminary Project Plan describing, among other
things, the methods and human and material resources that the Bidder
proposes to employ in the design, management, coordination, and execution of
all its responsibilities, if awarded the Contract, as well as the estimated
duration and completion date for each major activity. The Preliminary Project
Plan must also address the topics and points of emphasis specified in
SCC Clause 19 including any additional items stated in the Bid Data Sheet
for ITB Clause 16.2 ©. The Preliminary Project Plan should also state the
Bidder’s assessment of the major responsibilities of the Purchaser and any
other involved third parties in System supply and installation, as well as the
Bidder’s proposed means for coordinating activities by each of the involved
parties to avoid delays or interference.
5.3.1
In addition to the topics and points of emphasis, the Preliminary Project Plan
MUST address what steps will be taken if there is a failure; how project
progress will be reported; etc.
Section VI. Technical Requirements
5.3.2
5.4
The Preliminary Project Plan must it be submitted in Microsoft Office
Document or Microsoft Project Document format in electronic copy in
addition to hard copy.
Confirmation of Responsibility for Integration and Interoperability of
Information Technologies
5.4.0
5.5
233
The Bidder must submit a written confirmation that, if awarded the Contract,
it shall accept responsibility for successful integration and interoperability of
all the proposed Information Technologies included in the System, as further
specified in the Bidding Document.
Knowledge Transfer Plan
5.5.0
The bidder must submit a Knowledge Transfer Plan (KTP) and its
implementation processes for effectively transferring the technical knowhow necessary for managing the respective or individual systems to the
Purchaser. The plans and their implementation processes must be evidenced
through courses of actions. For achieving the above, involvement of the local
agents and a maximum of fifteen (15) Bangladesh Bank IT Officials in the
entire implementation processes as follows should be ensured:
a.
b.
c.
d.
e.
f.
Project Plan
Configuration and Customization, where applicable
Testing
Implementation
Training (including “Train the Trainer”)
Maintenance
Execution of the above plans, processes and actions must be evidenced during and
after implementation.
234
Section VI. Technical Requirements
6.
TECHNICAL RESPONSIVENESS CHECKLIST
Section VI. Technical Requirements
235
Technical Responsiveness Checklist
Note to Bidders: The following Checklist is provided to help the Bidder organize and
consistently present its Technical Bid. For each of the following Technical Requirements, the
Bidder must describe how its Technical Bid responds to each Requirement. In addition, the
Bidder must provide cross references to the relevant supporting information, if any, included
in the bid. The cross reference should identify the relevant document(s), page number(s), and
paragraph(s). The Technical Responsiveness Checklist does not supersede the rest of the
Technical Requirements (or any other part of the Bidding Documents). If a requirement is not
mentioned in the Checklist that does not relieve the Bidder from the responsibility of
including supporting evidence of compliance with that other requirement in its Technical
Bid. One- or two-word responses (e.g. “Yes,” “No,” “Will comply,” etc.) are normally not
sufficient to confirm technical responsiveness with Technical Requirements.
M represents “Mandatory”;
P represents “Preferred”;
D represents “Desirable”
236
Section VI. Technical Requirements
6.1. Documentation Checklist
The Bidder should provide specific reference including page number, section number (if any)
to find the documents.
Level
Document
Reference
& Response
Description
Requirements
M
Offered brand
M
Business
experience
Job
experience
Amongst the top ten (10) according to the assessment of a reputed global
market analyst, such as ‘Gartner’
The Bidder and the agent/subcontractor must have been in business for the
last five (05) years.
The Bidder must have completed minimum one successful contract
involving supply, installation, testing, commissioning, integration and
related technical support services of Network Devices for Information
Systems involving data center and disaster recovery sites in last five (05)
years
The Bidder must demonstrate present minimum average annual turnover of
US$ Seven (07) Million equivalent calculated as total certified payments
received for contracts in progress or completed within the last five (05)
years
The Bidder must demonstrate minimum US$ Five (05) Million equivalent
present liquid asset and/or line of credit, net of current commitments
The agent and the subcontractor of the bidder must have at least three years
proven experience in providing warranty support services.
The local agent and the subcontractor’s relationship with the Principal/
manufacturer shall be at least two (02) years.
Licensing for all software (where applicable) must be registered through
Regional Headquarters, under which Bangladesh falls, of the global
software vendors for ensuring convenient upgrade facility and renewal (as
and when necessary) by the time of operational acceptance test is
completed. Service and maintenance should be provided locally for the
project period including post warranty support services.
The Bidder should provide authorization letter(s) from the respective
software vendor(s).
Preliminary Project Plan as per ITB 28.5 (a) (iii)
Project Organization and Management Plan
Delivery and Installation Plan
Knowledge Transfer Plan
Training Plan
Pre-commissioning and Operational Acceptance Testing Plan
Warranty Service Plan
Task, Time, and Resource Schedules
Technical Support Plan
Required features properly marked/highlighted in the Datasheet of the
products.
M
M
Annual
Turnover
M
Liquid Asset
M
Subcontractor
Relationship
Manufacturer
Relationship
Licensing
M
M
M
M
Authorization
Letter
Project Plan
M
6.2. Details of Requirements:
Component
Hardware
Software
Training
Description
Routers, Switches, Firewalls, Content Filters etc.
As required as per Technical specification
Related training
Project
Site(s)
All
All
All
Reference &
Response
Section VI. Technical Requirements
Component
Installation
and
Implementation
237
Description
Project
Site(s)
All
As required as per Technical specification
Reference &
Response
The bidder must submit the bid for all the components with detailed specification as per
defined Technical, Financial, Legal & General requirements. In case of incomplete or
insufficient data the bid may be considered as non-responsive.
6.3. Computing Hardware and Software Requirements
Description
Network Spine Switch (DC: 2 and NDC: 2)
Network Leaf Switch Type-A (DC: 2 and NDC: 2)
Network Leaf Switch Type-B (DC: 6 and NDC: 6)
Network Aggregation Switch (DC: 2 and NDC: 2)
Campus Distribution Switch for DC
Server Farm Firewall (DC: 2 and NDC: 2)
Extranet Firewall (DC: 2 and NDC: 2)
Internet Firewall (DC: 2 and NDC: 2)
Application Load Balancer (DC: 4 and NDC: 4)
Bandwidth Manager (DC: 2 and NDC: 2)
Content Filter (DC: 2 and NDC: 2)
WAN Router (DC: 2 and NDC: 2)
Extranet Router (DC: 2 and NDC: 2)
Internet Router (DC: 2 and NDC: 2)
iSCSI WAN Router (DC: 2 and NDC: 2)
Extranet Switch (DC: 2 and NDC: 2)
SAN Director Switch (DC: 2 and NDC: 2)
Email Security for Microsoft Exchange (Dc:2 and NDC: 2)
Notebook Computer (DC:30)
6.4.
Level
M
M
M
M
M
M
M
Minimum
Quantity
4
4
12
4
2
4
4
4
8
4
4
4
4
4
4
4
4
4
30
Bidders
Response
Network Spine Switch
Description
Required Technical Specification
Quality
Certification
ISO, FCC, UL, CE or To be mentioned by the bidder
Brand
Model
Country of
Origin
Country of
Manufacture
Hardware
features
Internationally reputed top ten (10) brand of Gartner Magic Quadrant
Report in 2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Proposed network device must be 19’’ rack mountable.
It is desirable that the network infrastructure is based on delivering front
to back airflow.
Reference
& Response
238
Level
Section VI. Technical Requirements
Description
M
M
M
M
M
M
M
M
M
M
M
Scalability
M
M
M
M
M
M
M
M
M
M
M
General
Feature of
Software
Driven
Network
Required Technical Specification
Offered device must have Redundant Power Supply Units (PSUs), Hotswappable, field-replaceable power supplies, 1:1 power redundancy.
Offered device must have N: 1 fan module redundancy.
All components (including elements such as I/O modules, Expansion
Module, power supplies and fans) must be hot swappable with zero
disruption to traffic forwarding (Unicast or multicast).
In the event of a PSU failure, a single power supply must be able to
support the network device.
Offered device must have minimum 34 x 40G QSFP ports with 24 QSFP
Transceivers which could extend up to 100 meters over Multi-mode Fiber.
Bidders are allowed to provide a solution to meet the requirement with
two plus (2+) number of spine switches at each Data Center.
Offered device must have Layer 2 hardware forwarding at minimum
2.7Tbps. Bidders are allowed to meet the requirement by providing
additional number of spine switches.
Offered switches should have the option to operate in single switch fabric
Software Driven Network Spine mode.
All the software and licenses required for the Single Fabric Software
Driven Network Mode should be included.
Offered device must have Line-rate traffic throughput on all ports at Layer
2.
Offered device must be able to act as a Spine switch on a Software Driven
Network Environment and can scale up to minimum 34 Leaf switches.
Single Fabric with multiple spine switches should be expandable to
10,000+ 10Gbps ports.
Offered device must allow building very large L2 domain using MultiPath Ethernet technologies scalable to minimum 10+ Tbps of switching
capacity.
Offered device should be part of the SDN fabric and should support the
following features.
The switch fabric should support Layer 2 multipathing using ECMP
The SDN fabric should support Low and consistent latency through the
whole Fabric
The solution consists of a spine-leaf architecture.
The Fabric downlinks from this switch to the Leaf switches should be
based on 40GE links
The solution must support Multi-Tenancy
The fabric architecture must be based on hardware VXLAN overlays to
provide logical topologies that are abstracted from the physical
infrastructure with no performance penalty or similar solution with the
same capability.
This Fabric must be highly programmable through open source APIs from
a central management point which exposes all the networking components,
tenants and policies via an object model to which the virtualization
administrator can write REST calls. The centralized management point
can be integrated with major industry software management / cloud tools
to automate end users’ service requests.
The Switch Fabric must support Auto-provisioning based on Application
Requirement and policy based forwarding networking.
All the fabric devices need to be auto-provisioned based on the application
requirement pushed down from the controller.
Reference
& Response
Section VI. Technical Requirements
Level
Description
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Service
device
Integration
M
M
M
M
M
M
Controller
Features
239
Required Technical Specification
The proposed network solution must allow application architect (tenant) to
define policies, which control the network interaction between the
different components of his/her application, without any constraint
imposed by routing/bridging boundaries.
Policies define which workload can work with which workload and
through which services (load balancing, firewalling).
With the proposed architecture the network infrastructure becomes a
stateless element whose behavior in interconnecting workloads is defined
by the policies. The time to deploy a new application is shortened because
new policies can be applied and removed in minutes instead of days.
The proposed integration solution between overlay and underlay must
provide granular visibility, and telemetry to shorten the time necessary for
incident handling and fault isolation or similar solution should be provided
by using additional software or hardware.
All workloads must be treated the same both virtual and physical, thus no
bottleneck (gateway) exists.
The whole Fabric (Virtual and Physical) must be managed as a single
logical component (single management point) while providing an option
that requires configuration of each node
Ability to implement Multi-Tenancy with totally separated policies
between tenants.
Zero-touch installation and manage centralized at controller would be an
advantage for the bidders.
Traffic from hypervisors and from individual compute nodes is handled in
the same exact manner and benefits from the ability to completely
virtualize the underlying topology.
Offered device should support to connect any hypervisor like VMware,
Microsoft, RedHat to it without any different on design, solution and cost.
The fabric should support to decouple between End Point Location and
Identity in order for easy workload mobility.
The solution must have open API to integrate with 3rd party orchestrator
or management systems.
The controller must not directly involved in data plane forwarding, so a
complete failure or disconnection of all controllers elements in a cluster
will not result in any loss of existing datacenter functionality.
The policy inside the solution must be able to reuse the policy systemwide
The solution should support to integrate with Layer 4-7 service devices
like Firewall Load balancers etc.; should have third party service device
integration support.
The controller is the unified point of automation and management for the
proposed physical fabric, policy enforcement, and health monitoring.
The controller must be a single pane of glass to manage network policies
for both virtual, physical and cloud infrastructure based on application
requirements.
Automatic fabric discovery would be an advantage for the bidder.
The controller should be the unified GUI to do the image management and
inventory for physical network fabric, if not please mention proposed
solution.
The controller must run in the cluster mode with N+1 redundancy.
Controller integration with hypervisor management systems such as
VMware, Microsoft and Redhat.
Reference
& Response
240
Level
Section VI. Technical Requirements
Description
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Fabric
Requirements
Required Technical Specification
The controller should support TACACS+, RADIUS, LDAP and/or Local
Authentication for integration into existing management system. RoleBased Access Control is a must for the controller to be integrated into
existing IT management model.
The controller must have the Open NorthBound and SouthBound API.
The controller must support Standard OpenStack
The traffic flow and design for both physical and virtual workload must be
consistent and the same on logical point of view.
The proposed network physical fabric must support Spine/Leaf 2-tier
topology, which is the characteristic of hyper scale compute environments
and is optimized for east/west server-to-server traffic.
The proposed network physical fabric must support distributed default
gateway on the ToR/Leaf to optimize the traffic in DC.
The proposed network physical fabric must support decouple between
endpoint id and end point location. It will have the same ID when the end
point moves between ToR/Leaf.
No Flooding in IP control plane like ARP/GARP inside the tenants/Fabric
would be an advantage.
The proposed network physical fabric must support encapsulation
normalization with standard protocols like VXLAN
The proposed network physical fabric must support scale up and scale out
without any service interruption.
Offered device should support for visibility in hardware: can send the
packet drops and latency metrics to Controller to show to administrator
would be an advantage.
The proposed network physical fabric must support prioritize the small
packet inside the fabric.
Hosts are required to connect to leaf nodes and the number of leaf
switches depends on the proposed hosts to be located at each data center.
All the connection to outside or existing network must be via leaf layer.
Hosts dual-attach to two leaf nodes via standard-based protocols would be
an advantage.
The proposed fabric must be able to support host communication to the
fabric for VLAN, VXLAN and NVGRE or similar protocols.
The proposed fabric must support direct connection to external network
and/or WAN as an option via static, OSPF or iBGP routing protocol, if
not please mention the solution.
The proposed fabric must support redistribute external/WAN routes via
static, OSPF or iBGP routing protocol into fabric if not please mention the
solution.
The proposed fabric must support full host mobility such that any host can
be moved from any leaf node to any leaf node without any manual
network configuration involvement.
The proposed fabric should be able to support up to minimum 500
physical servers (including hypervisor hosts) and scale to minimum
10,000 physical hosts, minimum half a Million IP addresses and 50
tenants.
The proposed fabric must support variety of programmability: python,
bash, netconf, xml/json
The proposed fabric must support variety of programmability: python,
bash, netconf, xml/json or similar.
Reference
& Response
Section VI. Technical Requirements
Level
Description
M
M
Manufacturer
part number
M
Warranty
6.5.
Level
M
M
M
M
M
Required Technical Specification
Reference
& Response
Bidder should submit BOQ of proposed device including the details of
part numbers and Manufacturer’s warranty.
Bidder should submit the required performance document for the
proposed device.
Bidder should quote mentioning manufacturer’s warranty and part number
and minimum 3 (Three) years full replacement warranty should be
provided for this unit from the date of successful commissioning.
Network Leaf Switch Type-A:
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
M
M
M
M
M
M
General Feature
M
M
M
M
M
M
M
M
Scalability
M
241
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report
in 2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
It is desirable that the network infrastructure is based on delivering front to
back airflow.
Offered device must have Redundant Power Supply Units (PSUs), Hotswappable, field-replaceable power supplies, 1:1 power redundancy.
Offered device must have N:1 fan module redundancy.
All components (including elements such as I/O cards, Expansion Module,
power supplies and fans) must be hot swappable with zero disruption to
traffic forwarding (Unicast or multicast).
In the event of a PSU failure, a single (redundant) power supply must be able
to support the network device.
Offered device must have minimum 96 x 1/10GBase-T and 8 X 40 G QSFP
ports. Bidders are allowed to propose additional device to meet the
requirement.
Offered device must include four QSFP Transceivers which could extend up
to 100 meters over Multi-mode Fiber.
These switches should have the option to be deployed in standalone mode
and also single fabric Software Driven Network Leaf mode.
All the software and licenses for Single Fabric Software Driven Network
Leaf mode should be included.
Offered device must have Layer 2 hardware forwarding at minimum
2.5Tbps. Bidders are allowed to provide additional device to meet the
requirement.
Offered device must have Line-rate traffic throughput on all ports at Layer 2.
Offered device must have Line-rate traffic throughput on all ports at Layer 3
Offered device must support minimum 80,000 MAC address table entries.
Offered device must allow building very large L2 domain using Multi-Path
Ethernet technologies scalable to 10+ Tbps of switching capacity.
Would be an advantage to support link aggregation across multi chassis for
the servers and other service devices.
Reference
& Response
242
Level
Section VI. Technical Requirements
Description
M
M
M
M
M
M
M
M
M
M
M
M
M
Switch features
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Security
features
Required Technical Specification
Offered device must support Gigabit Ethernet (IEEE 802.3z, 802.3ab)
Offered device must support Ten Gigabit Ethernet (IEEE 802.3ae)
Offered device must support IEEE 802.1d - Spanning-Tree Protocol
Offered device must support IEEE 802.1w - Rapid Spanning Tree
Offered device must support IEEE 802.1s - Multiple Spanning Tree Protocol
Offered device must support IEEE 802.1q - VLAN encapsulation
Offered device must support IEEE 802.3ad - Link Aggregation Control
Protocol (LACP)
Offered device must support IEEE 802.1ab - Link Layer Discovery Protocol
(LLDP)
Offered device must support auto-sensing and auto-negotiation (Link
Speed/Duplex)
Offered device must support Static IP routing
Offered device must support Open Shortest Path First (OSPF) v2 (RFC
2328)
Offered device must support Protocol Independent Multicast Version 2
(PIMv2) sparse mode, Source Specific Multicast (SSM), Multicast Source
Discovery Protocol (MSDP), and Internet Group Management Protocol
Versions 2, and 3 (IGMP v2, and v3)
Offered device must have Routed ports on platform interfaces, switch virtual
interface (SVI).
Offered device should support Virtual Route Forwarding (VRF): VRF-lite
(IP VPN); VRF-aware unicast; and BGP-, OSPF-, RIP-, and VRF-aware
multicast
Offered device must support Jumbo Frame Size (9k)
Offered device must support IEEE 802.3ad Link Aggregation or equivalent
capabilities
Ability to load balance across a logical bundle using the following
algorithms would be an advantage:
Source IP
Destination IP
Source and Destination IP
Source MAC
Destination MAC
Source and Destination MAC
TCP Port (destination and/or source)
UDP Port (destination and/or source)
Would be an advantage to support VXLAN (Bridging and Routing) as well
as NVGRE overlay encapsulation protocol in hardware to support multiple
hypervisor deployment in the Data Center
Offered device must support multiple privilege levels for remote access (e.g.
console or telnet access)
Offered device must support Remote Authentication Dial-In User Service
(RADIUS) and/or Terminal Access Controller Access Control System Plus
(TACACS+) or Equivalent.
Offered device must support AAA using RADIUS (RFC 2138 & 2139)
and/or TACACS+, enabling centralized control of the device and the ability
to restrict unauthorized users from altering the configuration or Equivalent.
Offered device must support Ingress ACLs (Standard & Extended) on
Ethernet and virtual Ethernet ports
Offered device must support Storm control (unicast, multicast, and
Reference
& Response
Section VI. Technical Requirements
Level
Description
M
M
M
M
M
M
M
QoS features
M
M
M
M
M
Management
features
M
M
M
M
M
M
M
M
M
M
M
M
M
M
General Feature
of Software
Driven Network
243
Required Technical Specification
broadcast)
Offered device must support IEEE 802.1p class-of-service (CoS)
prioritization
Offered device must have Per-Port QoS configuration
Offered device must have CoS Trust
Offered device must have CoS-based egress queuing
Offered device must have Egress strict-priority queuing
Offered device must have per port virtual output queuing
Offered device must support Egress port-based scheduling: Weighted
Round-Robin (WRR)
Offered device must have ACL-based QoS classification (Layers 2, 3, and 4)
Offered device must provide management using 10/100/1000-Mbps
management or console ports
Offered device must have CLI-based console to provide detailed out-of-band
management
Offered device must have In-band switch management
Offered device must support Secure Shell Version 2 (SSHv2), Telnet &
SNMPv1, v2, and v3
Offered device must support AAA, AAA with RBAC, Radius, TACACS+
for user authentication or Equivalent.
Offered device must have Switched Port Analyzer (SPAN) on physical,
PortChannel, VLAN, and Fiber Channel interfaces or equivalent.
Offered device should be part of the SDN fabric and should support the
following features.
The switch fabric should support Layer 2 multipathing using ECMP
The SDN fabric should support Low and consistent latency through the
whole Fabric
The solution consists of spine-leaf architecture and this switch should act as
a leaf.
The Fabric uplinks to the spine switches should be based on 40GE links.
Minimum of 2 x 40G uplinks should be available. All the cables and
accessories should be provided.
The solution must support Multi-Tenancy
The fabric architecture must be based on hardware VXLAN overlays to
provide logical topologies that are abstracted from the physical infrastructure
with no performance penalty or similar solution with the same capability.
This Fabric must be highly programmable through open source APIs from a
central management point which exposes all the networking components,
tenants and policies via an object model to which the virtualization
administrator can write REST calls. The centralized management point can
be integrated with major industry software management / cloud tools to
automate end users’ service requests.
The Switch Fabric supports Auto-provisioning based on Application
Requirement and policy based forwarding networking.
All the fabric devices need to be auto-provisioned based on the application
requirement pushed down from the controller.
The proposed network solution must allow application architect (tenant) to
define policies, which control the network interaction between the different
components of his/her application, without any constraint imposed by
routing/bridging boundaries.
Policies define which workload can work with which workload and through
Reference
& Response
244
Level
Section VI. Technical Requirements
Description
M
M
M
M
M
M
M
M
M
M
M
M
M
Service device
Integration
M
M
M
M
M
M
M
M
M
Controller
Features
Required Technical Specification
which services (load balancing, firewalling).
With the proposed architecture the network infrastructure becomes a
stateless element whose behavior in interconnecting workloads is defined by
the policies. The time to deploy a new application is shortened because new
policies can be applied and removed in minutes instead of days.
The proposed integration solution between overlay and underlay must
provide granular visibility, and telemetry to shorten the time necessary for
incident handling and fault isolation or similar solution should be provided
by using additional software or hardware.
All workloads must be treated the same both virtual and physical, thus no
bottleneck (gateway) exists.
The whole Fabric (Virtual and Physical) must be managed as a single logical
component (single management point) while providing an option that
requires configuration of each node
Ability to implement Multi-Tenancy with totally separated policies between
tenants.
Zero-touch installation and manage centralized at controller.
Traffic from hypervisors and from individual compute nodes is handled in
the same exact manner and benefits from the ability to completely virtualize
the underlying topology.
Offered device should support to connect any hypervisor like VMware,
Microsoft, Redhat to it without any different on design, solution and cost.
The fabric should support to decouple between End Point Location and
Identity in order for easy workload mobility.
The solution must have open API to integrate with 3rd party orchestrator or
management systems.
The controller must not directly involved in data plane forwarding, so a
complete failure or disconnection of all controllers elements in a cluster will
not result in any loss of existing datacenter functionality.
The policy inside the solution must be able to reuse the policy system-wide
The solution should support to integrate with Layer 4-7 service devices like
Firewall Load balancers etc. should have 3rd party service device integration
support.
The controller is the unified point of automation and management for the
proposed physical fabric, policy enforcement, and health monitoring.
The controller must be a single pane of glass to manage network policies for
both virtual, physical and cloud infrastructure based on application
requirements.
Automatic fabric discovery would be an advantage.
The controller should be the unified GUI to do the image management and
inventory for physical network fabric, if not please mention proposed
solution.
The controller must run in the cluster mode with N+1 redundancy.
Controller integration with hypervisor management systems such as
VMware, Microsoft and Redhat would be an advantage.
The controller should support TACACS+, RADIUS, LDAP and/or Local
Authentication for integration into existing management system. Role-Based
Access Control is a must for the controller to be integrated into existing IT
management model.
The controller must have the Open NorthBound and SouthBound API.
The controller must support Standard OpenStack
Reference
& Response
Section VI. Technical Requirements
Level
Description
M
M
M
M
M
M
M
M
M
M
M
M
Fabric
Requirements
M
M
M
M
M
M
M
M
M
Manufacturer
part number
M
Warranty
245
Required Technical Specification
The traffic flow and design for both physical and virtual workload must be
consistent and the same on logical point of view.
The proposed network physical fabric must support Spine/Leaf 2-tier
topology, which is the characteristic of hyper scale compute environments
and is optimized for east/west server-to-server traffic.
The proposed network physical fabric must support distributed default
gateway on the ToR/Leaf to optimize the traffic in DC.
The proposed network physical fabric must support decouple between
endpoint id and end point location. It will have the same ID when the end
point moves between ToR/Leaf.
No Flooding in IP control plane like ARP/GARP inside the tenants/Fabric
would be an advantage.
The proposed network physical fabric must support encapsulation
normalization with standard protocols like VXLAN
The proposed network physical fabric must support scale up and scale out
without any service interruption.
Offered device should support for visibility in hardware: can send the packet
drops and latency metrics to Controller to show to administrator would be an
advantage.
The proposed network physical fabric must support prioritize the small
packet inside the fabric.
Hosts are required to connect to leaf nodes and the number of leaf switches
depends on the proposed hosts to be located at each data center.
All the connection to outside or existing network must be via leaf layer.
Hosts dual-attach to two leaf nodes via standard-based protocols would be an
advantage.
The proposed fabric must be able to support host communication to the
fabric for VLAN, VXLAN and NVGRE or similar protocols.
The proposed fabric must support direct connection to external network
and/or WAN as an option via static, OSPF or iBGP routing protocol, if not
please mention the solution.
The proposed fabric must support redistribute external/WAN routes via
static, OSPF or iBGP routing protocol into fabric if not please mention the
solution.
The proposed fabric must support full host mobility such that any host can
be moved from any leaf node to any leaf node without any manual network
configuration involvement.
The proposed fabric should be able to support up to minimum 500 physical
servers (including hypervisor hosts) and scale to minimum 10,000 physical
hosts, minimum half a Million IP addresses and 50 tenants.
The proposed fabric must support variety of programmability: python, bash,
netconf, xml/json
The proposed fabric must support variety of programmability: python, bash,
netconf, xml/json or similar.
Bidder should submit BOQ of proposed device including the details part
numbers and Manufacturer warranty.
Bidder should submit the required performance document for the proposed
device.
Bidder should quote mentioning manufacturer’s warranty and part number
and minimum 3 (Three) years full replacement warranty should be provided
for this unit from the date of successful commissioning
Reference
& Response
246
6.6.
Level
M
M
M
M
M
Section VI. Technical Requirements
Network Leaf Switch Type-B
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
M
M
M
M
M
M
General
Feature
M
M
M
M
M
M
M
M
Scalability
M
M
M
M
M
M
M
M
M
Switch
features
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
It is desirable that the network infrastructure is based on delivering front to back
airflow.
Offered device must have Redundant Power Supply Units (PSUs), Hotswappable, field-replaceable power supplies, 1:1 power redundancy.
Offered device must have N:1 fan module redundancy.
All components (including elements such as I/O cards, Expansion Module,
power supplies and fans) must be hot swappable with zero disruption to traffic
forwarding (Unicast or multicast).
In the event of a PSU failure, a single (redundant) power supply Must be able to
support the network device.
Offered device must have minimum 48 x 1/10 SFP+ and minimum 8 X 40 G
QSFP ports. Bidders can propose additional leaf switches to meet the
requirement.
Offered device must Include four QSFP Transceivers which could extend up to
100 meters over Multi-mode Fiber.
These switches should have the option to be deployed in standalone mode and
also single fabric Software Driven Network Leaf mode.
All the software and licenses for Single Fabric Software Driven Network Mode
should be included.
Offered device must have Layer 2 hardware forwarding at minimum 1.6Tbps.
Bidders can propose additional leaf switches to meet the requirement.
Offered device must have Line-rate traffic throughput on all ports at Layer 2.
Offered device must have Line-rate traffic throughput on all ports at Layer 3
Offered device must support minimum 80,000 MAC address table entries.
Offered device must allow building very large L2 domain using Multi-Path
Ethernet technologies scalable to minimum 10+ Tbps of switching capacity.
Would be an advantage to support link aggregation across multi chassis for the
servers and other service devices.
Offered device must support Gigabit Ethernet (IEEE 802.3z, 802.3ab)
Offered device must support Ten Gigabit Ethernet (IEEE 802.3ae)
Offered device must support IEEE 802.1d - Spanning-Tree Protocol
Offered device must support IEEE 802.1w - Rapid Spanning Tree
Offered device must support IEEE 802.1s - Multiple Spanning Tree Protocol
Offered device must support IEEE 802.1q - VLAN encapsulation
Offered device must support IEEE 802.3ad - Link Aggregation Control Protocol
(LACP)
Offered device must support IEEE 802.1ab - Link Layer Discovery Protocol
Reference
& Response
Section VI. Technical Requirements
Level
Description
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Security
features
M
M
M
M
M
M
M
M
M
M
M
QoS features
Management
features
247
Required Technical Specification
(LLDP)
Offered device must support auto-sensing and auto-negotiation (Link
Speed/Duplex)
Offered device must support Static IP routing
Offered device must support Open Shortest Path First (OSPF) v2 (RFC 2328)
Offered device must support Protocol Independent Multicast Version 2 (PIMv2)
sparse mode, Source Specific Multicast (SSM), Multicast Source Discovery
Protocol (MSDP), and Internet Group Management Protocol Versions 2, and 3
(IGMP v2, and v3)
Offered device must have Routed ports on platform interfaces, switch virtual
interface (SVI).
Should support Virtual Route Forwarding (VRF): VRF-lite (IP VPN); VRFaware unicast; and BGP-, OSPF-, RIP-, and VRF-aware multicast
Offered device must support Jumbo Frame Size (9k)
Offered device must support IEEE 802.3ad Link Aggregation or equivalent
capabilities
Ability to load balance across a logical bundle using the following algorithms
would be an advantage:
Source IP
Destination IP
Source and Destination IP
Source MAC
Destination MAC
Source and Destination MAC
TCP Port (destination and/or source)
UDP Port (destination and/or source)
Would be an advantage to support VXLAN (Bridging and Routing) as well as
NVGRE overlay encapsulation protocol in hardware to support multiple
hypervisor deployment in the Data Center
Offered device must support multiple privilege levels for remote access (e.g.
console or telnet access)
Offered device must support Remote Authentication Dial-In User Service
(RADIUS) and/or Terminal Access Controller Access Control System Plus
(TACACS+) or Equivalent.
Offered device must support AAA using RADIUS (RFC 2138 & 2139) and/or
TACACS+, enabling centralized control of the device and the ability to restrict
unauthorized users from altering the configuration or Equivalent.
Offered device must support Ingress ACLs (Standard & Extended) on Ethernet
and virtual Ethernet ports
Offered device must support Storm control (unicast, multicast, and broadcast)
Offered device must support IEEE 802.1p class-of-service (CoS) prioritization
Offered device must have Per-Port QoS configuration
Offered device must have CoS Trust
Offered device must have CoS-based egress queuing
Offered device must have Egress strict-priority queuing
Offered device must have per port virtual output queuing
Offered device must support Egress port-based scheduling: Weighted RoundRobin (WRR)
Offered device must have ACL-based QoS classification (Layers 2, 3, and 4)
Offered device must provide management using 10/100/1000-Mbps
management or console ports
Reference
& Response
248
Level
Section VI. Technical Requirements
Description
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
General
Feature of
Software
Driven
Network
Required Technical Specification
Offered device must have CLI-based console to provide detailed out-of-band
management
Offered device must have In-band switch management
Offered device must support Secure Shell Version 2 (SSHv2), Telnet &
SNMPv1, v2, and v3
Offered device must support AAA, AAA with RBAC, Radius, TACACS+ for
user authentication or Equivalent.
Offered device must have Switched Port Analyzer (SPAN) on physical,
PortChannel, VLAN, and Fiber Channel interfaces or equivalent.
This Device should be part of the SDN fabric and should support the following
features.
The switch fabric should support Layer 2 multipathing using ECMP
The SDN fabric should support Low and consistent latency through the whole
Fabric
The solution consists of spine-leaf architecture and this switch should act as a
leaf.
The Fabric uplinks to the spine switches should be based on minimum 40GE
links. Minimum of 2 x 40G uplinks should be available. All the cables and
accessories should be provided.
The solution MUST support Multi-Tenancy
The fabric architecture must be based on hardware VXLAN overlays to provide
logical topologies that are abstracted from the physical infrastructure with no
performance penalty or similar solution with the same capability.
This Fabric must be highly programmable through open source APIs from a
central management point which exposes all the networking components, tenants
and policies via an object model to which the virtualization administrator can
write REST calls. The centralized management point can be integrated with
major industry software management / cloud tools to automate end users’
service requests.
The Switch Fabric supports Auto-provisioning based on Application
Requirement and policy based forwarding networking.
All the fabric devices need to be auto-provisioned based on the application
requirement pushed down from the controller.
The proposed network solution must allow application architect (tenant) to
define policies, which control the network interaction between the different
components of his/her application, without any constraint imposed by
routing/bridging boundaries.
Policies define which workload can work with which workload and through
which services (load balancing, firewalling).
With the proposed architecture the network infrastructure becomes a stateless
element whose behavior in interconnecting workloads is defined by the policies.
The time to deploy a new application is shortened because new policies can be
applied and removed in minutes instead of days.
The proposed integration solution between overlay and underlay must provide
granular visibility, and telemetry to shorten the time necessary for incident
handling and fault isolation or similar solution should be provided by using
additional software or hardware.
All workloads must be treated the same both virtual and physical, thus no
bottleneck (gateway) exists.
The whole Fabric (Virtual and Physical) must be managed as a single logical
component (single management point) while providing an option that requires
configuration of each node
Reference
& Response
Section VI. Technical Requirements
Level
Description
M
M
M
M
M
M
M
M
M
Service
device
Integration
M
M
M
M
M
M
Controller
Features
M
M
M
M
M
M
M
M
M
Fabric
Requirement
s
249
Required Technical Specification
Ability to implement Multi-Tenancy with totally separated policies between
tenants.
Zero-touch installation and manage centralized at controller would be an
advantage for the bidders.
Traffic from hypervisors and from individual compute nodes is handled in the
same exact manner and benefits from the ability to completely virtualize the
underlying topology.
Support to connect any hypervisor like Vmware, Microsoft, Redhat to it without
any different on design, solution and cost would be an advantage for the bidders.
The fabric should support to decouple between End Point Location and Identity
in order for easy workload mobility.
The solution must have open API to integrate with 3rd party orchestrator or
management systems.
The controller must not directly involved in data plane forwarding, so a
complete failure or disconnection of all controllers elements in a cluster will not
result in any loss of existing datacenter functionality.
The policy inside the solution must be able to reuse the policy system-wide
The solution should support to integrate with Layer 4-7 service devices like
Firewall Load balancers etc.; should have 3rd party service device integration
support.
The controller is the unified point of automation and management for the
proposed physical fabric, policy enforcement, and health monitoring.
The controller must be a single pane of glass to manage network policies for
both virtual, physical and cloud infrastructure based on application
requirements.
Automatic fabric discovery would be an advantage for the bidder.
The controller should be the unified GUI to do the image management and
inventory for physical network fabric, if not please mention proposed solution.
The controller must run in the cluster mode with N+1 redundancy.
Controller integration with hypervisor management systems such as VMware,
Microsoft and Redhat would be an advantage for the bidder.
The controller should support TACACS+, RADIUS, LDAP and/or Local
Authentication for integration into existing management system. Role-Based
Access Control is a must for the controller to be integrated into existing IT
management model.
The controller must have the Open NorthBound and SouthBound API.
The controller must support Standard OpenStack
The traffic flow and design for both physical and virtual workload must be
consistent and the same on logical point of view.
The proposed network physical fabric must support Spine/Leaf 2-tier topology,
which is the characteristic of hyper scale compute environments and is
optimized for east/west server-to-server traffic.
The proposed network physical fabric must support distributed default gateway
on the ToR/Leaf to optimize the traffic in DC.
The proposed network physical fabric must support decouple between endpoint
id and end point location. It will have the same ID when the end point moves
between ToR/Leaf.
No Flooding in IP control plane like ARP/GARP inside the tenants/Fabric
would be an advantage.
The proposed network physical fabric must support encapsulation normalization
with standard protocols like VXLAN
Reference
& Response
250
Level
Section VI. Technical Requirements
Description
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Manufacture
r part
number
M
Warranty
6.7.
Level
M
M
M
M
M
Required Technical Specification
Reference
& Response
The proposed network physical fabric must support scale up and scale out
without any service interruption.
Offered device should support for visibility in hardware: can send the packet
drops and latency metrics to Controller to show to administrator would be an
advantage.
The proposed network physical fabric must support prioritize the small packet
inside the fabric.
Hosts are required to connect to leaf nodes and the number of leaf switches
depends on the proposed hosts to be located at each data center.
All the connection to outside or existing network must be via leaf layer.
Hosts dual-attach to two leaf nodes via standard-based protocols would be an
advantage.
The proposed fabric must be able to support host communication to the fabric
for VLAN, VXLAN and NVGRE or similar protocols.
The proposed fabric must support direct connection to external network and/or
WAN as an option via static, OSPF or iBGP routing protocol, if not please
mention the solution.
The proposed fabric must support redistribute external/WAN routes via static,
OSPF or iBGP routing protocol into fabric if not please mention the solution.
The proposed fabric must support full host mobility such that any host can be
moved from any leaf node to any leaf node without any manual network
configuration involvement.
The proposed fabric should be able to support up to minimum 500 physical
servers (including hypervisor hosts) and scale to minimum 10,000 physical
hosts, minimum half Million IP addresses and 50 tenants.
The proposed fabric must support variety of programmability: python, bash,
netconf, xml/json
The proposed fabric must support variety of programmability: python, bash,
netconf, xml/json or similar.
Bidder should submit BOQ of proposed device including the details part
numbers and Manufacturer warranty.
Bidder should submit the required performance document for the proposed
device.
Bidder should quote mentioning manufacturer’s warranty and part number and
minimum 3 (Three) years full replacement warranty should be provided for this
unit from the date of successful commissioning
Network Aggregation Switch
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report
in 2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Reference
& Response
Section VI. Technical Requirements
Level
Description
M
M
M
Architecture
M
M
M
M
M
M
M
M
M
M
M
M
Switching
Performance
Switch Layer
2 Services
M
M
M
M
M
M
M
M
M
M
Switch Layer
3 Services
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Security
features
Management
features
251
Required Technical Specification
Offered device should be highly performed fixed switch with wire rate Layer
2 and Layer 3 throughput on all the ports on the chassis.
Offered device should have minimum of 24 x 10GE SFP/SFP+ transceiver
based ports and upgradeable to minimum 48 x 10GE ports on the same
chassis.
Switch should include 2 Direct attach transceiver based 10G 7 meter cables,
15 multi-mode 10G transceivers. All the cables and accessories have to be
provided.
Offered device should have dual redundant power source and redundant
Fans
Switching capacity minimum 480 Gbps and upgradeable up to minimum 960
Gbps
Forwarding Throughput minimum 360 Mpps and upgradeable up to
minimum 720 Mpps
Layer 2 switch ports and VLAN trunks
IEEE 802.1Q VLAN encapsulation
Support for up to minimum 4096 VLANs
Rapid Spanning Tree (IEEE 802.1w compatible)
MSTP (IEEE 802.1s): 64 instances
Spanning Tree PortFast
Spanning Tree Root Guard
Spanning Tree Bridge Assurance
Link Aggregation technology (up to 24 ports), If not please mention the
provided solution.
LACP: IEEE 802.3ad, IEEE 802.1ax
Advanced Link aggregation hashing based on Layer 2, 3, and 4 information
Jumbo frames on all ports (up to 9216 bytes)
Storm control (multicast and broadcast)
Layer 3 interfaces: Routed ports on interfaces, switch virtual interfaces
(SVIs), Link aggregation.
Minimum 24-way Equal-Cost Multipath (ECMP), if not please mention.
Minimum 4096 ACL entries
Routing protocols: Static, RIPv2, OSPF
FHRP
ACL: Routed ACL with Layer 3 and 4 options to match ingress and egress
ACLs
Jumbo frame support (up to 9216 bytes)
Ingress ACLs (standard and extended) on Ethernet
Standard and extended Layer 3 to 4 ACLs include IPv4, Internet Control
Message Protocol (ICMP), TCP, and User Datagram Protocol (UDP)
VLAN-based ACLs (VACLs)
Port-based ACLs (PACLs)
Named ACLs
ACLs on virtual terminals (VTYs)
Dynamic Host Configuration Protocol ( DHCP) relay
Control Plane Policing (CoPP), if not please mention.
CLI-based console to provide detailed out-of-band management
In-band switch management
Switch management using 10/100/1000-Mbps management or console ports
SSHv2 and Telnet
SNMP agent - SNMPv1, SNMPv2, SNMPv3.
Reference
& Response
252
Level
Section VI. Technical Requirements
Description
M
M
Manufacturer
part number
M
Warranty
6.8.
Level
M
M
M
M
M
M
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
Enclosure
Type
M
General
Features
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Reference
& Response
Bidder should submit BOQ of proposed device including the details part
numbers and Manufacturer warranty.
Bidder should submit the required performance document for the proposed
device.
Bidder should quote mentioning manufacturer’s warranty and part number
and minimum 3 (Three) years full replacement warranty should be provided
for this unit from the date of successful commissioning.
Campus Distribution Switch
M
M
M
M
M
M
Required Technical Specification
Performance
Required Technical Specification
ISO, FCC, UL, CE or to be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report
in 2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Rack-mountable Modular Chassis
The Switch should be modular at least 6 slots chassis switch
The Switch OS should be modular and open system/platform
The switch should support redundant switching engine for future
requirement.
The switch OS can support third-party applications in parallel with Switch
OS
Dual Hot-swappable power supplies
At least 96 x 1GE SFP ports available from day 1.
Minimum 96 number of 1G Optical Multi-Mode SFP modules should be
included with all the required cables and accessories.
At least 8 x 10 Gigabit SFP ports available from day 1.
Minimum 8 numbers of 10G Optical Multi-Mode SFP modules with all the
required cables and accessories.
Supervisor should support Minimum 550 Gbps Switching Capacity in single
chassis.
Minimum 240 Mpps IPv4 forwarding capacity in single chassis.
Minimum 120 Mpps IPv6 forwarding capacity in single chassis.
Per-Slot Switching Capacity minimum 48 Gbps
IPv4 Routing Entries: Minimum 250,000
IPv6 Routing Entries: Minimum 125,000
Support IPv6 Unicast and Multicast in hardware with full line-rate
forwarding capacity
Multicast Routes Table/Entries: Minimum 31,000
MAC addresses: Minimum 54,000 entries
ARP: Minimum 45,000 Entries
Switch Virtual Interface: Minimum 4000
VLANs: Minimum 4000 active VLANs
Reference
& Response
Section VI. Technical Requirements
Level
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Description
Switch
Processor
Performance
Layer 2
Features
Layer 3
Features
Security
Features
HighAvailability
M
M
M
Management
Features
M
M
M
Manufacturer
part number
M
Warranty
253
Required Technical Specification
Hardware-based multicast management
Minimum Centralized 550 Gbps switching capacity should be supported.
Should have full line rate forwarding for IPv6 packets
Advanced QoS support with up to 8 queues per port and security policies per
port
Security and Qos services hardware based entries: Minimum 125,000
IEEE 802.1QVLAN encapsulation, IEEE 802.3ae, 802.3ad, 802.1p
Support for Automatic Negotiation of Trunking Protocol, to help minimize
the configuration & errors.
Support 4000 Switched Virtual Interfaces
Support for the Link Aggregation Protocol (LACP)
Support for Static IP routing, Routing Information Protocol (RIP),OSPF,
BGP, VRF for IPv4 and IPv6 protocol
Support for IP multicast routing protocols filtering on access and trunk ports.
Support for Quality of Service and Traffic Management
Support for 8 queues per port & priority queuing
Support Protocol Independent Multicast (PIM) and Source-Specific
Multicast (SSM) to support multimedia applications
Support Multicast Listener Discovery (MLD) snooping for IPv6
Standard and extended ACLs on all ports.
Support 802.1x user authentication
Support DHCP Snooping entries
Support IEEE 802.1X User Authentication
Support common policy for wired and wireless nodes
Support Port Security
The switch should support redundant power supply
Nonstop Forwarding/Stateful Switchover (NSF/SSO)
In-Service Software Upgrade (ISSU)
The switch should have Virtual Chassis or similar technology feature
included to create layer 2 loop free topology. Should have minimum 2 x 10G
Virtual chassis Data and Management plane connectivity.
Should have a console port and single IP address to manage all features of
the system
Should have a Software-configuration management, including local and
remote storage
Should have a Manageability through a common network-management
software
Should have support for Configuration Rollback for improved configuration
management
Bidder should submit BOQ of proposed device including the details part
numbers and Manufacturer warranty.
Bidder should submit the required performance document for the proposed
device.
Bidder should quote mentioning manufacturer’s warranty and part number
and minimum 3 (Three) years full replacement warranty should be provided
for this unit from the date of successful commissioning.
Reference
& Response
254
6.9.
Level
M
M
M
M
M
Section VI. Technical Requirements
Server Farm Firewall
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble
/Manufacture
M
M
M
M
M
M
M
M
M
Hardware and
Performance
M
M
M
M
M
M
M
M
M
General
features
M
M
Required Technical Specification
ISO, FCC, UL, CE or to be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant
Report in 2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Offered Firewall should have minimum 12 x1GE integrated data ports,
minimum 8 x 10G ports. Minimum 8 Multi-Mode 10G transceivers should
be included. All the cables and accessories should be included.
The appliance should be capable of providing Firewall, VPN Services and
Next Generation Firewall feature
Should have a 64Bit Multi-Core Processor or a similar technology.
The platform shall have dedicated interface for out-of-bound management
Offered Firewall should support CA functionality
Offered Firewall performance (Large packets) minimum 19Gbps with
multiprotocol performance of minimum 9.5Gbps
Offered Firewall + IPS + Application Visibility combine performance
should be 5.8Gbps or more.
Offered Firewall should be capable configuring Policies using Command
Line (CLI) as a last resort in case of Emergency.
Offered Firewall should support minimum 4,000,000 concurrent
connections
Offered Firewall should support minimum 200, 000 new connections per
second (cps)
Offered Firewall should deliver VPN throughput of minimum 3 Gbps with
10,000 sessions.
Next Generation Firewall (FW+APPS Visiblity+IPS) concurrent sessions
minimum 1,800,000 and minimum 120,000 connections/second
Offered Firewall should support up to 220 virtual context/firewall (Data
Plane and administratively separated Logical system)
Offered device should support grouping of physical interfaces within and
across Fixed and Expansion ports into one single physical or logical
interface
Offered Firewall should have minimum 36 GB Memory for better
performance.
The firewall shall be deployed in high availability mode (hot stand-by
redundancy), have fault tolerance and shall provide stateful failover
There shall be support for traffic-based and user based access control.
The broad default policy for the firewall for handling inbound traffic shall
be to block all packets and connections unless the traffic type and
connections have been specifically permitted
It shall support SNMP (Simple Network Management Protocol) v 2.0 and
v 3.0.
Network address translation (NAT) shall be supported so that the private
IP addresses of hosts and the structure of an internal network can be
Reference
& Response
Section VI. Technical Requirements
Level
Description
M
M
M
M
M
M
M
M
M
M
M
Attack
protection
M
M
M
M
M
M
M
M
M
M
M
M
M
VPN Features
M
M
M
M
Next Gen FW
feature
M
255
Required Technical Specification
concealed by the firewall.
Network Address Translation (NAT) shall be configurable as 1:1, 1: many,
many: 1, many:many shall be supported.
Dynamic Host Configuration Protocol (DHCP) over Virtual Private
Network (VPN) shall be supported for dynamic allocation of IP addresses.
Offered firewall shall support a number of routing options and
configurations. Routing protocol support shall include static routes, Open
Shortest Path First (OSPF), RIPv1/v2.
Virtual LAN (VLAN) support, high port density, WAN support and
expandability of interfaces over time are some important network
integration features shall be supported.
Offered firewall IP stack shall be IPv6 ready.
Offered firewall shall mask the internal network from the external world.
Offered firewall shall provide robust access control capability and be fast
in making access control decisions. Access Control shall be done based on
criteria such as source, destination IPs, port number, protocol, traffic type,
application, date information (day of week, time of day), etc.
Multi-layer, stateful, application-based filtering shall be supported
It shall provide network segmentation features with powerful capabilities
that facilitate deploying security for various internal, external and DMZ
(Demilitarized Zone) sub-groups on the network, to prevent unauthorized
access.
There shall be support for detection of reconnaissance attempts such as IP
address sweep, port scanning etc.
Offered Firewall itself shall be resistant to attack and shall have protection
against firewall evasion techniques.
Some basic attack protection features listed below but not limited to :
a. Maximum no of protections against attacks that exploit weaknesses in
the TCP/IP protocol suite
b. It shall enable rapid detection of network attacks
c. TCP reassembly for fragmented packet protection
d. Brute force attack mitigation
e. SYN cookie protection , SYN Flood, Half Open Connections and NUL
Packets
f. Protection against IP spoofing
g. Malformed packet protection
h. Java blocking, and real-time alerts
The firewall shall support Internet Protocol Security (IPSec) & SSL
Key exchange with latest Internet Key Exchange (IKE), IKEv2, Public
Key Infrastructure PKI (X.509) shall be catered to.
Site-to-site VPN tunnels: full-mesh / star topology shall be supported.
Should support Latest Encryption algorithms including AES 128/192/256
(Advanced Encryption Standards), 3DES (Data Encryption Standard) etc.
Support Latest Authentication algorithms including SHA-1(Secure Hash
Algorithm-1), SHA-2(Secure Hash Algorithm-2) etc.,
IPSec NAT traversal shall be supported.
VPN supporting minimum 10,000 IPSec / SSL VPN peers
Detection rules must be based on an extensible, open language (API) that
enables users to create their own rules, as well as to customize any vendorprovided rules.
Detection rules provided by the vendor must be documented, with full
Reference
& Response
256
Level
Section VI. Technical Requirements
Description
M
M
M
M
M
M
M
M
M
M
Real-Time
Contextual
Awareness
M
M
M
M
M
M
Intelligent
Security
Automation
Required Technical Specification
descriptions of the identity, nature, and severity of the associated
vulnerabilities and threats being protected against.
The detection engine must be capable of detecting and preventing a wide
variety of threats (e.g., malware, network probes/reconnaissance, VoIP
attacks, buffer overflows, P2P attacks, zero-day threats, etc.).
The detection engine must incorporate multiple approaches for detecting
threats, including at a minimum exploit-based signatures, vulnerabilitybased rules, protocol anomaly detection, and behavioral anomaly detection
techniques. Identify and explain each type of detection mechanism
supported.
The detection engine must inspect not only Network Layer details and
information resident in packet headers, but a broad range of protocols
across all layers of the computing stack and packet payloads as well.
The detection engine must be resistant to various URL obfuscation
techniques common to HTML-based attacks.
The solution must be capable of detecting and blocking IPv6 attack
The solution must provide IP reputation feed that comprised of several
regularly updated collections of IP addresses determined by the proposed
security vendor to have a poor reputation.
The solution must be capable of passively gathering information about
network hosts and their activities, such as operating system, services, open
ports, client applications, and vulnerabilities, to assist with multiple
activities, such as intrusion event data correlation, elimination of false
positives, and policy compliance.
The solution must be capable of passively gathering information about
session flows for all monitored hosts, including start/end time, ports,
services, and amount of data.
The solution must be capable of storing user-defined host attributes, such
as host criticality or administrator contact information, to assist with
compliance monitoring.
The solution must be capable of passively gathering user identity
information, mapping IP addresses to username, and making this
information available for event management purposes.
The solution must be capable of passively gathering details unique to
mobile devices traffic to identify a wide variety of mobile operating
systems, mobile applications and associated mobile device hardware.
The solution must provide a detailed, interactive graphical summary that
includes data on applications, application statistics, connections, intrusions
events, hosts, servers, users, file-types, malwares and relevant URLs.
These data should be presented in the form of vivid line, bar, pie and donut
graphs accompanied by detailed lists (Administrator should easily create
and apply custom filters to fine-tune the analysis).
Appliance have capacity to block source based on geo-location
The solution must be capable of employing an extensive set of contextual
information (e.g., pertaining to the composition, configuration, and
behavior of the network and its hosts) to improve the efficiency and
accuracy of both manual and automatic analysis of detected events.
The solution must be capable of significantly reducing operator effort and
accelerating response to threats by automatically prioritizing alerts, ideally
based on the potential for correlated threats to successfully impact the
specific hosts they are directed toward.
The solution must be capable of dynamically tuning IDS/IPS sensors (e.g.,
Reference
& Response
Section VI. Technical Requirements
Level
Description
M
Advance
Malware
Protection
M
M
M
Network
Behavior
Analysis
(NBA)
M
M
M
M
M
M
M
M
M
M
M
M
M
M
NGFW
Management
and Usability
257
Required Technical Specification
selecting rules, configuring policies, updating policies, etc.) with minimal
human intervention.
The solution should be capable of providing network-based detection of
malware by checking the disposition of known files in the cloud using the
SHA-256 file-hash as they transit the network (SHA-256 and target IP
address should be given to aid remediation efforts) with enabling just
advance malware protection or similar solution should be provided. Please
add and mention if any additional device required.
The solution must provide a full-featured NBA capability to detect threats
emerging from inside the network This includes the ability to establish
“normal” traffic baselines through flow analysis techniques and the ability
to detect deviations from normal baselines
The NBA capability must provide visibility into how network bandwidth is
consumed to aid in troubleshooting network outages and performance
degradations.
The NBA capability must provide the ability to link Active Directory
and/or LDAP usernames to IP addresses related to suspected security
events.
The same network devices used for IPS must also be used as part of the
NBA capability. No NBA-only device should be required.
The same management platform used for IPS must also be used to manage
the NBA capability.
The management platform must be capable of centralized, life cycle
management for all NGFW services/devices, all required licenses for
centralized management for Next Generation FW IPS should be included.
The management platform must be capable of aggregating IDS/IPS events
and centralized, real-time monitoring and forensic analysis of detected
events.
The management platform must be accessible via a web-based interface
and ideally with no need for additional client software.
The management platform must provide a highly customizable dashboard.
The management platform must be capable of integrating third party
vulnerability information into threat policy adjustment routines and
automated tuning workflows.
The management platform must be capable of role-based administration,
enabling different sets of views and configuration capabilities for different
administrators subsequent to their authentication.
The management platform must include a scheduling subsystem to
facilitate automation of routine tasks, such as backups, upgrades, report
creation, and policy application.
The management platform must include one or more default (i.e., predefined) detection policy configurations to help simplify initial
deployment.
The management platform must provide the capability to easily view,
enable, disable, and modify individual rules, as well as groups or
categories of rules.
The management platform must be capable of automatically receiving rule
updates published by the vendor and automatically distributing and
applying those rule updates to sensors.
The management platform must be capable of backup and rollback for
sensor configurations and the management platform itself.
The management platform must include flexible workflow capabilities for
Reference
& Response
258
Level
Section VI. Technical Requirements
M
M
M
M
M
M
M
M
Reporting and
Alerting
M
M
M
Manufacturer
part number
M
Warranty
6.10.
Level
M
M
M
M
M
M
M
M
Required Technical Specification
Description
Reference
& Response
managing the complete life cycle of an event, from initial notification
through to any response and resolution activities that might be required.
The management platform must provide the ability to view the
corresponding detection rule for each detected event, along with the
specific packet(s) that caused it to be triggered.
The management platform must support both internal and external
databases/systems for storage of event data, logs, and other systemgenerated information.
The management platform must be capable of synchronizing time between
all components of the system via NTP.
The management platform must be capable of logging all administrator
activities, both locally and to a remote log server.
The solution must support LDAP for single sign-on to sensors and the
management console.
The management platform must provide robust reporting capabilities,
including a selection of pre-defined reports and the ability for complete
customization and generation of new reports.
The management platform must allow quick report customization by
importing from dashboards, workflows and statistics summaries.
The management platform must provide multiple report output types or
formats, such as PDF, HTML, and CSV.
The management platform must support multiple mechanisms for issuing
alerts (e.g., SNMP, e-mail, SYSLOG).
Bidder should submit BOQ of proposed device including the details part
numbers and Manufacturer warranty.
Bidder should submit the required performance document for the proposed
device.
Bidder should quote mentioning manufacturer's warranty and subscription
part number and minimum 3 (Three) years full replacement warranty and
subscription should be provided for this unit from the date of successful
commissioning
Extranet Firewall
Required Technical Specification
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
Enclosure
Type
Hardware
and
Performance
ISO, FCC, UL, CE or to be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report
in 2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Rack Mountable
The platform shall be supplied with at least 8 number of 10/100/1000Mbps
interfaces.
The appliance should be capable of providing Firewall, VPN Services
Reference
& Response
Section VI. Technical Requirements
Level
M
M
M
M
Description
Specs of
Firewall &
VPN
Services
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
General
features
M
M
M
M
M
M
Network
Address
Translation
259
Required Technical Specification
The appliance should have a 64Bit Multi-Core Processor or similar
technology.
The platform shall have dedicated interface for out-of-bound management
The Firewall should support CA functionality
Firewall performance (Large packets) minimum 3.8 Gbps with multiprotocol
performance of minimum 1.8 Gbps
Firewall should be capable configuring Policies using Command Line (CLI)
as a last resort in case of Emergency.
The appliance should have hardware cryptographic module
The appliance should support concurrent connection up to minimum 950,000
New connection Per Second should be at least 48,000
Next generation Firewall (FW+IPS+AppsVisibilty) throughput Minimum 1.2
Gbps
Firewall should be capable of monitoring environmental temperature and
generate syslogs when exceeds normal temperature.
The appliance should support dual hot swappable redundant power supply
The appliance should deliver VPN throughput of minimum 680 mbps
Firewall should support up to minimum 95 virtual Firewalls (Data Plane and
Administratively separate logical system)
The appliance should support automatic creation of logs and generate a
Technical assistance case
The appliance should support grouping of physical interfaces within and
across Fixed and Expansion ports into one single physical or logical interface
The appliance should support for BOTNET protection, isolating malware
communication to the command control
The appliance should support for Multicast
The appliance should support Packet Tracer capabilities for troubleshooting
purposes
Firewall should have minimum 16 GB Memory for better and faster
processing.
The firewall shall be deployed in high availability mode (hot stand-by
redundancy), have fault tolerance and shall provide stateful failover
The firewall shall have a powerful OS that is hardened and is based upon
minimal feature sets.
Access control shall be provided for including specified as rules and policies
or any other comprehensive easy to maintain facility.
There shall be support for traffic-based and for user based access control.
The firewall shall allow configuration of policy that governs the rules
according to which the firewall handles the traffic.
The broad default policy for the firewall for handling inbound traffic shall be
to block all packets and connections unless the traffic type and connections
have been specifically permitted
It shall support SNMP (Simple Network Management Protocol) v 2.0 and v
3.0.
Network address translation (NAT) shall be supported so that the private IP
addresses of hosts and the structure of an internal network can be concealed
by the firewall.
Network Address Translation (NAT) shall be configurable as 1:1, 1: many,
many: 1, many:many shall be supported.
Port address translation/Masquerading shall be provided.
Dynamic Host Configuration Protocol (DHCP) over Virtual Private Network
Reference
& Response
260
Level
Section VI. Technical Requirements
Description
M
M
M
M
M
M
M
M
M
M
M
M
Attack
protection
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
VPN
Features
M
M
M
M
Next
Gen
FW feature
Required Technical Specification
(VPN) shall be supported for dynamic allocation of IP addresses.
The firewall shall support a number of routing options and configurations.
Routing protocol support shall include static routes, Open Shortest Path First
(OSPF), RIPv1/v2.
Virtual LAN (VLAN) shall be supported.
The firewall shall support LAN interfaces (10/100/1000) for high speed LAN
traffic with facility for future expansion.
The firewall shall be capable of integrating with other equipment and with
adequate optimization.
The firewall IP stack shall be IPv6 ready.
The firewall shall mask the internal network from the external world.
The firewall shall provide robust access control capability and be fast in
making access control decisions. Access Control shall be done based on
criteria such as source, destination IPs, port number, protocol, traffic type,
application, date information (day of week, time of day), etc.
Multi-layer, stateful, application -based filtering shall be done
It shall provide network segmentation features with powerful capabilities that
facilitate deploying security for various internal, external and DMZ
(Demilitarized Zone) sub-groups on the network, to prevent unauthorized
access.
Ingress/egress filtering capability shall be provided.
There shall be support for detection of reconnaissance attempts such as IP
address sweep, port scanning etc.
Firewall itself shall be resistant to attack and shall have protection against
firewall evasion techniques.
Some basic attack protection features listed below but not limited to :
a. Maximum number of protections against attacks that exploit weaknesses in
the TCP/IP protocol suite
b. It shall enable rapid detection of network attacks
c. TCP reassembly for fragmented packet protection
d. Brute force attack mitigation
e. SYN cookie protection , SYN Flood, Half Open Connections and NUL
Packets
f. Protection against IP spoofing
g. Malformed packet protection
h. Java blocking, and real-time alerts
The firewall shall support Internet Protocol Security (IPSec) & SSL
Key exchange with latest Internet Key Exchange (IKE), IKEv2, Public Key
Infrastructure PKI (X.509) shall be catered to.
Site-to-site VPN tunnels: full-mesh / star topology shall be supported.
Layer Two Tunneling Protocol (L2TP) support shall be provided.
Support Latest Encryption algorithms including AES 128/192/256 (Advanced
Encryption Standards), 3DES (Data Encryption Standard) etc.,
Support Latest Authentication algorithms including SHA-1 (Secure Hash
Algorithm-1), SHA-2 (Secure Hash Algorithm-2) etc.,
IPSec NAT traversal shall be supported.
Configuration of VPN shall be intuitive and user friendly.
VPN throughput should be at least 680 Mbps supporting minimum 4500
IPSec / SSL VPN peers
Detection rules must be based on an extensible, open language that enables
users to create their own rules, as well as to customize any vendor-provided
Reference
& Response
Section VI. Technical Requirements
Level
Description
M
M
M
M
M
M
M
M
Advance
Malware
Protection
M
Protection
against
Advanced
Malware
M
M
M
M
M
M
Real-Time
Contextual
Awareness
261
Required Technical Specification
rules.
Detection rules provided by the vendor must be documented, with full
descriptions of the identity, nature, and severity of the associated
vulnerabilities and threats being protected against.
The detection engine must be capable of detecting and preventing a wide
variety of threats (e.g., malware, network probes/reconnaissance, VoIP
attacks, buffer overflows, P2P attacks, zero-day threats, etc.).
The detection engine must incorporate multiple approaches for detecting
threats, including at a minimum exploit-based signatures, vulnerability-based
rules, protocol anomaly detection, and behavioral anomaly detection
techniques. Identify and explain each type of detection mechanism supported.
The detection engine must inspect not only Network Layer details and
information resident in packet headers, but a broad range of protocols across
all layers of the computing stack and packet payloads as well.
The detection engine must be resistant to various URL obfuscation techniques
common to HTML-based attacks.
The solution must be capable of detecting and blocking IPv6 attack
The solution must provide IP reputation feed that comprised of several
regularly updated collections of IP addresses determined by the proposed
security vendor to have a poor reputation.
The solution should be capable of providing network-based detection of
malware by checking the disposition of known files in the cloud using the
SHA-256 file-hash as they transit the network (SHA-256 and target IP address
should be given to aid remediation efforts) with enabling just advance
malware protection or similar solution should be provided. Please add and
mention if any additional device required.
The solution should be capable of providing network-based detection of
malware by checking the disposition of known files in the cloud using the
SHA-256 file-hash as they transit the network (SHA-256 and target IP address
should be given to aid remediation efforts)
The solution must be capable of passively gathering information about
network hosts and their activities, such as operating system, services, open
ports, client applications, and vulnerabilities, to assist with multiple activities,
such as intrusion event data correlation, elimination of false positives, and
policy compliance.
The solution must be capable of passively gathering information about session
flows for all monitored hosts, including start/end time, ports, services, and
amount of data.
The solution must be capable of storing user-defined host attributes, such as
host criticality or administrator contact information, to assist with compliance
monitoring.
The solution must be capable of passively gathering user identity information,
mapping IP addresses to username, and making this information available for
event management purposes.
The solution must be capable of passively gathering details unique to mobile
devices traffic to identify a wide variety of mobile operating systems, mobile
applications and associated mobile device hardware.
The solution must provide a detailed, interactive graphical summary that
includes data on applications, application statistics, connections, intrusions
events, hosts, servers, users, file-types, malwares and relevant URLs. These
data should be presented in the form of vivid line, bar, pie and donut graphs
accompanied by detailed lists (Administrator should easily create and apply
Reference
& Response
262
Level
Section VI. Technical Requirements
Description
M
M
M
Intelligent
Security
Automation
M
M
M
M
Application
control
M
M
M
M
M
M
Network
Behavior
Analysis
(NBA)
M
M
M
M
M
M
NGFW
Management
and Usability
Required Technical Specification
custom filters to fine-tune the analysis).
Appliance have capacity to block source based on geo-location
The solution must be capable of employing an extensive set of contextual
information (e.g., pertaining to the composition, configuration, and behavior
of the network and its hosts) to improve the efficiency and accuracy of both
manual and automatic analysis of detected events.
The solution must be capable of significantly reducing operator effort and
accelerating response to threats by automatically prioritizing alerts, ideally
based on the potential for correlated threats to successfully impact the specific
hosts they are directed toward.
The solution must be capable of dynamically tuning IDS/IPS sensors (e.g.,
selecting rules, configuring policies, updating policies, etc.) with minimal
human intervention.
The solution must integrate application control to reduce risks associated with
applications usage and client-side attacks. It should provide a means of
enforcing acceptable use policies of up to minimum 1200 application
detectors.
The solution must support creation of user-defined application protocol
detectors.
The solution must have content awareness with comprehensive file detection
policies and blocking of files by types, protocols and directions.
The solution must provide capabilities for establishing and enforcing host
compliance policies and alerting on violations.
The solution must be capable of easily identifying all hosts that exhibit a
specific attribute or non-compliance condition.
The solution must provide a full-featured NBA capability to detect threats
emerging from inside the network (i.e., ones that have not passed through a
perimeter IPS). This includes the ability to establish “normal” traffic baselines
through flow analysis techniques (e.g., NetFlow) and the ability to detect
deviations from normal baselines
The NBA capability must provide visibility into how network bandwidth is
consumed to aid in troubleshooting network outages and performance
degradations.
The NBA capability must provide the ability to link Active Directory and/or
LDAP usernames to IP addresses related to suspected security events.
The NBA capability must provide the option of supplying endpoint
intelligence to the IPS for correlation against intrusion events to aid in event
impact prioritization.
The same network devices used for IPS must also be used as part of the NBA
capability. No NBA-only device should be required.
The same management platform used for IPS must also be used to manage the
NBA capability. No NBA-only management components should be required.
The management platform must be capable of centralized, life cycle
management for all NGFW services/devices. The Central Management
Platform for NGFW services with all the required licenses has to be included.
The management platform must be delivered in virtual appliance form factor
(management system and UI must provide the same features and functions as
in the physical appliance).
The management platform must be capable of aggregating IDS/IPS events and
centralized, real-time monitoring and forensic analysis of detected events.
The management platform must be accessible via a web-based interface and
ideally with no need for additional client software.
Reference
& Response
Section VI. Technical Requirements
Level
Description
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Reporting
and Alerting
M
M
M
Manufacture
r part
number
M
Warranty
263
Required Technical Specification
The management platform must provide a highly customizable dashboard.
The management platform must be capable of integrating third party
vulnerability information into threat policy adjustment routines and automated
tuning workflows.
The management platform must be capable of role-based administration,
enabling different sets of views and configuration capabilities for different
administrators subsequent to their authentication.
The management platform must include a scheduling subsystem to facilitate
automation of routine tasks, such as backups, upgrades, report creation, and
policy application.
The management platform must include one or more default (i.e., pre-defined)
detection policy configurations to help simplify initial deployment.
The management platform must provide the capability to easily view, enable,
disable, and modify individual rules, as well as groups or categories of rules.
The management platform must be capable of automatically receiving rule
updates published by the vendor and automatically distributing and applying
those rule updates to sensors.
The management platform must be capable of backup and rollback for sensor
configurations and the management platform itself.
The management platform must include flexible workflow capabilities for
managing the complete life cycle of an event, from initial notification through
to any response and resolution activities that might be required.
The management platform must provide the ability to view the corresponding
detection rule for each detected event, along with the specific packet(s) that
caused it to be triggered.
The management platform must support both internal and external
databases/systems for storage of event data, logs, and other system-generated
information.
The management platform must be capable of synchronizing time between all
components of the system via NTP.
The management platform must be capable of logging all administrator
activities, both locally and to a remote log server.
The solution must support LDAP for single sign-on to sensors and the
management console.
The management platform must provide robust reporting capabilities,
including a selection of pre-defined reports and the ability for complete
customization and generation of new reports.
The management platform must allow quick report customization by
importing from dashboards, workflows and statistics summaries.
The management platform must provide multiple report output types or
formats, such as PDF, HTML, and CSV.
The management platform must support multiple mechanisms for issuing
alerts (e.g., SNMP, e-mail, SYSLOG).
Bidder should submit BOQ of proposed device including the details part
numbers and Manufacturer warranty.
Bidder should submit the required performance document for the proposed
device.
Bidder should quote mentioning manufacturer’s warranty and part number and
minimum 3 (Three) years full replacement warranty should be provided for
this unit from the date of successful commissioning.
Reference
& Response
264
6.11.
Level
M
M
M
M
M
M
Section VI. Technical Requirements
Internet Firewall
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
Enclosure
Type
M
M
M
M
M
M
M
M
M
M
M
M
M
Hardware and
Performance
of Firewall &
VPN Services
M
M
M
M
M
M
M
M
M
M
Required Technical Specification
Description
General
features
ISO, FCC, UL, CE or to be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report
in 2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Rack-mountable
The platform shall be supplied with at least 8 number of 10/100/1000Mbps
interfaces.
The appliance should be capable of providing Firewall, VPN Services
The appliance should have a 64Bit Multi-Core Processor or similar
technology.
The platform shall have dedicated interface for out-of-bound management
The Firewall should support CA functionality
Firewall performance (Large packets) minimum 2.8 Gbps with multiprotocol
performance of minimum 1.4 Gbps
Firewall should be capable configuring Policies using Command Line (CLI) as
a last resort in case of Emergency.
The appliance should have hardware cryptographic module
The appliance should support concurrent connection up to minimum 730,000
New connection Per Second should be at least 29,000
Firewall should be capable of monitoring environmental temperature and
generate syslog when exceeds normal temperature.
The appliance should Support dual hot swappable redundant power supply
The appliance should have Online Insertion and Removal (OIR) of external
USB flash drive
The appliance should deliver VPN throughput of minimum 380 mbps
Firewall should support up to minimum 45 virtual Firewalls (Data Plane and
Administratively separate logical system)
The appliance should support automatic creation of logs and generate a
Technical assistance case
The appliance should support grouping of physical interfaces within and
across Fixed and Expansion ports into one single physical or logical interface
The appliance should support for BOTNET protection, isolating malware
communication to the command control
The appliance should support for Multicast
Firewall should support memory up to minimum 12 GB Memory for better
performance.
The firewall shall be deployed in high availability mode (hot stand-by
redundancy), have fault tolerance and shall provide stateful failover
The firewall shall have a powerful OS that is hardened and is based upon
minimal feature sets.
Access control shall be provided for including specified as rules and policies
or any other comprehensive easy to maintain facility.
Reference
& Response
Section VI. Technical Requirements
Level
Description
M
M
M
M
M
M
M
M
M
Network
Address
Translation
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Attack
protection
265
Required Technical Specification
There shall be support for traffic-based and for user based access control.
The firewall shall allow configuration of policy that governs the rules
according to which the firewall handles the traffic.
The broad default policy for the firewall for handling inbound traffic shall be
to block all packets and connections unless the traffic type and connections
have been specifically permitted
It shall support SNMP (Simple Network Management Protocol) v 2.0 and v
3.0.
Network address translation (NAT) shall be supported so that the private IP
addresses of hosts and the structure of an internal network can be concealed by
the firewall.
Network Address Translation (NAT) shall be configurable as 1:1, 1: many,
many: 1, many:many shall be supported.
Port address translation/Masquerading shall be provided.
Dynamic Host Configuration Protocol (DHCP) over Virtual Private Network
(VPN) shall be supported for dynamic allocation of IP addresses.
The firewall shall support a number of routing options and configurations.
Routing protocol support shall include static routes, Open Shortest Path First
(OSPF), RIPv1/v2.
Virtual LAN (VLAN) support
The firewall shall support LAN interfaces (10/100/1000) for high speed LAN
traffic with facility for future expansion.
The firewall shall be capable of integrating with other equipment and with
adequate optimization.
The firewall IP stack shall be IPv6 ready.
The firewall shall mask the internal network from the external world.
The firewall shall provide robust access control capability and be fast in
making access control decisions. Access Control shall be done based on
criteria such as source, destination IPs, port number, protocol, traffic type,
application, date information (day of week, time of day), etc.
Multi-layer, stateful, application-based filtering shall be done
It shall provide network segmentation features with powerful capabilities that
facilitate deploying security for various internal, external and DMZ
(Demilitarized Zone) sub-groups on the network, to prevent unauthorized
access.
Ingress/egress filtering capability shall be provided.
There shall be support for detection of reconnaissance attempts such as IP
address sweep, port scanning etc.
Firewall itself shall be resistant to attack and shall have protection against
firewall evasion techniques.
Some basic attack protection features listed below but not limited to :
a. Maximum no of protections against attacks that exploit weaknesses in the
TCP/IP protocol suite
b. It shall enable rapid detection of network attacks
c. TCP reassembly for fragmented packet protection
d. Brute force attack mitigation
e. SYN cookie protection , SYN Flood, Half Open Connections and NUL
Packets
f. Protection against IP spoofing
g. Malformed packet protection
h. Java blocking, and real-time alerts
Reference
& Response
266
Level
Section VI. Technical Requirements
Description
M
M
M
M
M
VPN Features
M
M
M
M
M
M
M
M
Next Gen FW
feature
M
M
M
M
M
Protection
against
Advanced
Malware
M
M
M
Real-Time
Contextual
Awareness
Required Technical Specification
The firewall shall support Internet Protocol Security (IPSec) & SSL
Key exchange with latest Internet Key Exchange (IKE), IKEv2, Public Key
Infrastructure PKI (X.509) shall be catered to.
Site-to-site VPN tunnels: full-mesh / star topology shall be supported.
Layer Two Tunneling Protocol (L2TP) support shall be provided.
Support Latest Encryption algorithms including AES 128/192/256 (Advanced
Encryption Standards), 3DES (Data Encryption Standard) etc.,
Support Latest Authentication algorithms including SHA-1(Secure Hash
Algorithm-1), SHA-2(Secure Hash Algorithm-2) etc.,
IPSec NAT traversal shall be supported.
Configuration of VPN shall be intuitive and user friendly.
VPN throughput should be at least 380 Mbps supporting minimum 2400 IPSec
/ SSL VPN peers
Detection rules must be based on an extensible, open language that enables
users to create their own rules, as well as to customize any vendor-provided
rules.
Detection rules provided by the vendor must be documented, with full
descriptions of the identity, nature, and severity of the associated
vulnerabilities and threats being protected against.
The detection engine must be capable of detecting and preventing a wide
variety of threats (e.g., malware, network probes/reconnaissance, VoIP
attacks, buffer overflows, P2P attacks, zero-day threats, etc.).
The detection engine must incorporate multiple approaches for detecting
threats, including at a minimum exploit-based signatures, vulnerability-based
rules, protocol anomaly detection, and behavioral anomaly detection
techniques. Identify and explain each type of detection mechanism supported.
The detection engine must inspect not only Network Layer details and
information resident in packet headers, but a broad range of protocols across
all layers of the computing stack and packet payloads as well.
The detection engine must be resistant to various URL obfuscation techniques
common to HTML-based attacks.
The solution must be capable of detecting and blocking IPv6 attack
The solution must provide IP reputation feed that comprised of several
regularly updated collections of IP addresses determined by the proposed
security vendor to have a poor reputation.
The solution should be capable of providing network-based detection of
malware by checking the disposition of known files in the cloud using the
SHA-256 file-hash as they transit the network (SHA-256 and target IP address
should be given to aid remediation efforts) with Advanced Malware
Protection. Please add and mention if any additional device required for this
feature.
The solution must be capable of passively gathering information about
network hosts and their activities, such as operating system, services, open
ports, client applications, and vulnerabilities, to assist with multiple activities,
such as intrusion event data correlation, elimination of false positives, and
policy compliance.
The solution must be capable of passively gathering information about session
flows for all monitored hosts, including start/end time, ports, services, and
amount of data.
The solution must be capable of storing user-defined host attributes, such as
host criticality or administrator contact information, to assist with compliance
monitoring.
Reference
& Response
Section VI. Technical Requirements
Level
Description
M
M
M
M
M
M
Intelligent
Security
Automation
M
M
M
M
M
Application
and URL
control
M
M
M
M
M
Network
Behavior
Analysis
(NBA)
267
Required Technical Specification
The solution must be capable of passively gathering user identity information,
mapping IP addresses to username, and making this information available for
event management purposes.
The solution must be capable of passively gathering details unique to mobile
devices traffic to identify a wide variety of mobile operating systems, mobile
applications and associated mobile device hardware.
The solution must provide a detailed, interactive graphical summary that
includes data on applications, application statistics, connections, intrusions
events, hosts, servers, users, file-types, malwares and relevant URLs. These
data should be presented in the form of vivid line, bar, pie and donut graphs
accompanied by detailed lists (Administrator should easily create and apply
custom filters to fine-tune the analysis).
Appliance have capacity to block source based on geo-location
The solution must be capable of employing an extensive set of contextual
information (e.g., pertaining to the composition, configuration, and behavior
of the network and its hosts) to improve the efficiency and accuracy of both
manual and automatic analysis of detected events.
The solution must be capable of significantly reducing operator effort and
accelerating response to threats by automatically prioritizing alerts, ideally
based on the potential for correlated threats to successfully impact the specific
hosts they are directed toward.
The solution must be capable of dynamically tuning IDS/IPS sensors (e.g.,
selecting rules, configuring policies, updating policies, etc.) with minimal
human intervention.
The solution must integrate application control to reduce risks associated with
applications usage and client-side attacks. It should provide a means of
enforcing acceptable use policies of up to minimum 1200 application
detectors.
The solution must support creation of user-defined application protocol
detectors.
The solution must have content awareness with comprehensive file detection
policies and blocking of files by types, protocols and directions.
The proposed solution should provide an option to include URL filtering for
enforcing Internet content filtering so as to reduce web born threats and
improve productivity. Each URL in the data set must has an associated
category and reputation. URL category is a general classification for the URL
while URL reputation represents how likely the URL is to be used for
purposes that might be against the organization’s security policy.
The solution must provide capabilities for establishing and enforcing host
compliance policies and alerting on violations.
The solution must be capable of easily identifying all hosts that exhibit a
specific attribute or non-compliance condition.
The solution must provide a full-featured NBA capability to detect threats
emerging from inside the network (i.e., ones that have not passed through a
perimeter IPS). This includes the ability to establish “normal” traffic baselines
through flow analysis techniques (e.g., NetFlow) and the ability to detect
deviations from normal baselines
The NBA capability must provide visibility into how network bandwidth is
consumed to aid in troubleshooting network outages and performance
degradations.
The NBA capability must provide the ability to link Active Directory and/or
LDAP usernames to IP addresses related to suspected security events.
Reference
& Response
268
Level
Section VI. Technical Requirements
Description
M
M
M
M
M
M
M
M
M
M
M
M
M
NGFW
Management
and Usability
M
M
M
M
M
M
M
M
M
Reporting and
Required Technical Specification
The NBA capability must provide the option of supplying endpoint
intelligence to the IPS for correlation against intrusion events to aid in event
impact prioritization.
The same network devices used for IPS must also be used as part of the NBA
capability. No NBA-only device should be required.
The same management platform used for IPS must also be used to manage the
NBA capability. No NBA-only management components should be required.
The management platform must be capable of centralized, life cycle
management for all NGFW services/devices. The Central Management
Platform for NGFW services with all the required licenses has to be included.
The management platform must be delivered in virtual appliance form factor
(management system and UI must provide the same features and functions as
in the physical appliance).
The management platform must be capable of aggregating IDS/IPS events and
centralized, real-time monitoring and forensic analysis of detected events.
The management platform must be accessible via a web-based interface and
ideally with no need for additional client software.
The management platform must provide a highly customizable dashboard.
The management platform must be capable of integrating third party
vulnerability information into threat policy adjustment routines and automated
tuning workflows.
The management platform must be capable of role-based administration,
enabling different sets of views and configuration capabilities for different
administrators subsequent to their authentication.
The management platform must include a scheduling subsystem to facilitate
automation of routine tasks, such as backups, upgrades, report creation, and
policy application.
The management platform must include one or more default (i.e., pre-defined)
detection policy configurations to help simplify initial deployment.
The management platform must provide the capability to easily view, enable,
disable, and modify individual rules, as well as groups or categories of rules.
The management platform must be capable of automatically receiving rule
updates published by the vendor and automatically distributing and applying
those rule updates to sensors.
The management platform must be capable of backup and rollback for sensor
configurations and the management platform itself.
The management platform must include flexible workflow capabilities for
managing the complete life cycle of an event, from initial notification through
to any response and resolution activities that might be required.
The management platform must provide the ability to view the corresponding
detection rule for each detected event, along with the specific packet(s) that
caused it to be triggered.
The management platform must support both internal and external
databases/systems for storage of event data, logs, and other system-generated
information.
The management platform must be capable of synchronizing time between all
components of the system via NTP.
The management platform must be capable of logging all administrator
activities, both locally and to a remote log server.
The solution must support LDAP for single sign-on to sensors and the
management console.
The management platform must provide robust reporting capabilities,
Reference
& Response
Section VI. Technical Requirements
Level
M
M
M
M
M
Manufacturer
part number
M
Warranty
6.12.
Lev
el
M
M
M
M
M
including a selection of pre-defined reports and the ability for complete
customization and generation of new reports.
The management platform must allow quick report customization by importing
from dashboards, workflows and statistics summaries.
The management platform must provide multiple report output types or
formats, such as PDF, HTML, and CSV.
The management platform must support multiple mechanisms for issuing alerts
(e.g., SNMP, e-mail, SYSLOG).
Bidder should submit BOQ of proposed device including the details part
numbers and Manufacturer warranty.
Bidder should submit the required performance document for the proposed
device.
Bidder should quote mentioning manufacturer’s warranty and subscription part
number and minimum 3 (Three) years full replacement warranty and
subscription should be provided for this unit from the date of successful
commissioning.
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
M
Features
M
M
M
M
Reference
& Response
Application Load Balancer
M
M
M
M
M
M
M
M
Required Technical Specification
Description
Alerting
269
Server/Applic
ation
Load
Balancing
Required Technical Specification
ISO, FCC, UL, CE or to be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report in
2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Purpose built hardware architecture of multicore CPU based appliance
Should provide minimum 10 Gbps of layer 7 throughput
Should have minimum 16 GB of RAM
Should have minimum 2X10G ports and minimum 8X1G ports
Should have dedicated out of band 10/100/1000 copper management interface
Should support minimum 400,000 Layer 7 request per second and scalable to
minimum 700,000 Layer 7 request per second
Should support hardware assisted SSL offloading capability with minimum
4,500 SSL Transactions per second at 2048 bit SSL and scalable to minimum
9,000 SSL Transactions per second at 2048 bit
Should support hardware assisted minimum 8 Gbps SSL throughput in SSL
offload
Should provide minimum 4 Gbps server side compression throughput scalable
to minimum 8 Gbps server side compression throughput
Should have a minimum DNS performance of minimum 400,000 QPS scalable
up to minimum 700,000 QPS
Should support minimum 10,000,000 concurrent connections
Should be able to provide layer 7 traffic management and application delivery
features using multicore processor architecture
Should have application delivery features such as layer 7 load balancing, layer 7
Reference
& Response
270
Lev
el
Section VI. Technical Requirements
Description
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Device
Administration
M
M
M
M
M
M
M
M
M
6.13.
Lev
el
M
High
Availability
OEM Criteria
Warranty
Required Technical Specification
Reference
& Response
content switch, caching, hardware based SSL offload and server side
compression
Should be able to monitor the applications using intelligent application level
monitors which can be system defined, internal or external executable scripts
Should provide the capability to source address translation one arm deployment
mode, two arm routed mode and direct server return mode
Should provide static and dynamic load balancing algorithms such as round
robin, weighted round robin, fastest, predictive and observed
Should support 2048 and 4096 bit key for SSL traffic management
Should be application aware for protocols such as HTTP, HTTPS, FTP, SIP,
DNS, Diameter, RADIUS etc.
Should provide mechanism to bind multiple health checks, support for
Application specific VIP health check and next gateway health checks
Should be able to load balance traffic in environment where the request
response path is asymmetric
Should support inspection of SSL traffic for reverse proxy and forward proxy
deployment. Should also support ICAP interface for integration with external
security systems.
Should support SPDY gateway in environment where the client to load balancer
traffic is SYDP and from load balancer to server is normal HTTP providing
SPDY proxy
Should provide HTTPS interface management for administering the device
Should provide SSH interface management for administering the device
Should provide troubleshooting and traffic analysis tool like tcpdump
Should support SNMP V1, V2c, V3
Should have a web dashboard that should provide the following information:
• Total concurrent sessions
• Throughput
• HTTP request per second
• CPU Usage
• Memory Usage
Graphs of the above data for the last 30 days should be available.
Should provide multiple config version option on the appliance
Should provide system, traffic logs on web GUI
Should support role based admin access with roles like No Access, Guest,
Operator, Application Editor, Resource Administrator and Administrator
Support both Active - Active and Active - Standby topology
Should support transparent failover between 2 devices, the failover should be
transparent to other networking devices
Should have dual power supply
Should be able to provide 24/7 support over phone/email
Preferable to be in Gartner’s Leaders quadrant for ADC's
Bidder should quote minimum 3 (Three) years manufacturer's full replacement
warranty for this unit from the date of successful commissioning.
Bandwidth Manager
Description
Quality
Certification
Required Technical Specification
ISO, FCC, UL, CE or to be mentioned by the bidder
Reference
& Response
Section VI. Technical Requirements
Lev
el
Description
M
Brand
M
M
Model
Country of
Origin
Country of
Assemble /
Manufacture
M
M
M
Hardware
M
M
Functions
271
Required Technical Specification
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report
in 2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
The equipment must provide at least 1 pair minimum 1Gbps and dedicated
Management port. The equipment must support expansion module up to at
least 2 separate network segment.
Product should come with one power supply and should have option of second
redundant and hot swappable power supply
Equipment must support ‘fail-close’ in the event of power outrage, software or
hardware failure. The “fail-close” functionality of electronic interface must be
implemented internally。
(1) The equipment must support remote access to enable management and
operation via command line and GUI. It should provide the following
access interfaces:
 RS-232 DB9 serial port;
 HTTP/HTTPS
 Should support customized portal for different users
(2) SNMP V2/V3
(3) Telnet/ SSH
(4) The equipment must support high availability
(5) The equipment must support OSI L2 to L7 protocol auto-detection and
classify the traffic accordingly. It must be able to detect at least 700
commonly used applications and protocols, including FTP, HTTP and
other applications using non-standard TCP port
(6) The equipment must support application flow classification based on
MAC address, 802.1p/q, ISL, MPLS tag;
(7) The equipment must support flow classification based on IP
Precedence, Diff-Serv Code Point , IP address, multiple IP addresses
,IP subnet;
(8) The equipment must support flow classification based on both static
and dynamic TCP and UDP ports. Example of dynamic port
applications are Thunder,BitTorrent, FlashVideo,PPStream,
PPlive,Skype,KaZaA v1/v2, Gnutella, WinMx, eDonkey, Half-life,
etc. The equipment must be able to auto-detect, auto-classify and then
enforce bandwidth control accordingly;
(9) The equipment must support customized application protocol detect, to
facilitate detection and control of homebrew application。
(10) The equipment must support flow classification based on DNS, URL,
attachment extension (e.g., “.exe, .zip, .com”), Mime-Type (e.g.
“application/octet-stream, video/x-flv, etc. browser type;
(11) The equipment must support URL Category for HTTP traffic, category
must more than 80 kind, support cloud computing, process 8 billion
request every day so that can guarantee real time category and
coverage;
(12) The equipment must support flow classification based on the server
physical location, traffic flow direction (in/out), host list, etc.;
Reference
& Response
272
Lev
el
Section VI. Technical Requirements
Description
Required Technical Specification
(13) The equipment must support layer 7+ flow identification, and classify
traffic based on application level attribute, include the following
applications:
- Video conference: Classify video, audio stream, ICMP in RTP/RTCP-I
stream;
- Voice over IP (VOIP): Identify audio codec in RTP-I (dynamic,
G729, GSM, JPEG, PCMA, PCMU, endpoint type;
- Identify Individual application in Citrix traffic;
- Identify database in the Oracle traffic;
- Identify Individual database in PostrgreSQL traffic;
(14) The equipment must support flow classification based on the host
system
type
(TN3270,TN5250,FNA,5250p,TCPA,Attachmate, etc.);
(15) The equipment must make use of tree-based, multi-layers structure
layout to visualize the traffic flow;
(16) The equipment provide comprehensive application response time
management, by providing total delay, network delay, server delay and
delay distribution diagram;
(17) The equipment must provide detailed analysis on delay, jitter, packet
loss of VoIP traffic;
(18) The equipment must provide detailed analysis on a particular IP flow;
(19) The equipment must be able to identify the originator and receiver of a
flow and the associate ports;
(20) The equipment must provide TCP/IP based, worst client and worst
server analysis;
(21) The equipment must support bi-directional, precise flow control, only
by deploying one unit of proposed equipment on any traffic point
along the flow;
(22) The equipment must support queue-based traffic control and TCP
sliding window, connection link delay control. The bandwidth
adjustment must archive down to 1kbps precision;
(23) The equipment must provide MTU management to control
fragmentation and jitter.
(24) The equipment must support, at the same time, per-session flow
control and enforce max/min bandwidth policy;
(25) The equipment must be able to seamless integrate into the WAN
acceleration solution of the same company. It must be able to identify
applications in individual acceleration tunnel and perform statistical
analysis, bandwidth control, to balance the resource among tunneled
and non-tunneled traffic. It must be able to perform bandwidth control
on applications inside the accelerated tunnels;
(26) The equipment must be able to automatically respond to network
situation by pre-defined policy (e.g. bandwidth adjustment, IP jail) and
alert (e.g. SNMP Trap, SysLog, Mail);
(27) The reporting and graphing function must be integrated in the
equipment, without any add-on or external device. The precision must
be down to minute level;
(28) Real-time analysis on the active flow (including single link and multiinks real-time, end-to-end analysis) must be integrated into the
equipment, without any add-on or external device. The real-time
precision and update interval must be down to second and provide
Reference
& Response
Section VI. Technical Requirements
Lev
el
Performance
requirement
M
6.14.
Lev
el
M
M
M
M
M
Required Technical Specification
Description
M
Warranty
Reference
& Response
statistical figure for historical analysis. The UI should be written in
JAVA or Flash to facilitate browser access;
(29) At least 2 month of traffic data must be stored on the device itself,
without any add-on or external device;
(30) Should support centralized management and reporting;
(31) Should support data export via SNMP, XML, CSV, CGI, etc.;
(32) Should support integration with third party network management
system
(33) Should support integration with Radius and TACACS+ for
administrator authentication and authorization
(34) Should support Active Directory Integration for user awareness
(35) Should support administrator operation audit
(1) Should support minimum 500,000 IP flows;
(2) Should Support minimum 5,000 traffic classification
(3) Should Support minimum 450,000 concurrent IP host statistic
(4) Should Support minimum 7,500 shaping policies
(5) Should Support minimum 15,000 dynamic partitions
(6) Should Support minimum 5,000 static partitions
Bidder should quote and provide minimum 3 (Three) years manufacturer's full
replacement warranty for this unit from the date of successful commissioning
Content Filter
Description
Quality
Certification
Brand
Model
Country of Origin
Country of
Assemble /
Manufacture
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
273
General malware
control
and
filtering
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report
in 2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
The device should have minimum 1,000 licenses for web security control
with minimum of three years subscription.
The device should be capable of minimum 12,000 users capacity.
Spyware/Adware/Generic Web threat protection
Virus protection
Automatic update of all anti-malware signatures
Multiple anti-malware engines support
AS/AV engine(s)
Phishing protection
Automatic update of phishing protection rules
URL filtering support
Number of URL categories
URL/web filtering database suppliers
Policies per identity / customer
Policies defined per time range
Policies defined per category
Reference
& Response
274
Lev
el
Section VI. Technical Requirements
Description
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Proxy cache and
performance
Protocol control
User
authentication
Administration
and management
Required Technical Specification
Policies defined per destination URL
Policies defined per destination IP address
Block possibility
Monitoring only possibility
Notification / logging
Custom URL categories
Sub-level domain categorization
Webmail filter
Web reputation based filtering
Customizable reputation filtering thresholds to block/allow/scan content
TCP-layer scanning to detect rogue activity and phone-home attempts
Monitoring and blocking of malware connection attempts on all 65535 TCP
ports
Monitoring and blocking of malware connection attempts in both incoming
and outgoing direction
Cache storage capacity at least 4TB
Cache technology used
Implementation as transparent proxy
Implementation as transparent proxy using L4 switch
Implementation as explicit proxy
Implementation as explicit proxy using PAC files and/or WPAD
PAC file hosting
Multiple upstream proxies support with conditional HTTP traffic routing
Multiple data ports for Web traffic scanning
HTTP
HTTPS
FTP over HTTP
FTP (native)
Web elements and browser filtering
Browser version filtering
Java blocking
ActiveX blocking
Archive file types detected
Multiple archives detection
File type blocking
Block by defined maximum file size
User authorization by IP address
User authorization by Subnet
LDAP authentication
Active directory authentication with NTLMSSP (Integrated Windows
Authentication)
LDAP/Active directory groups support for policy assignment
HTTPS Management console
CLI access using SSH
RS232 serial console port
Centralized management possibility
Manage up to 100 separate devices from one single point
Delegated, fully customizable, security policy administration down to user
identity level
Administrative users authentication through LDAP
Administrative users authentication through RADIUS
Reference
& Response
Section VI. Technical Requirements
Lev
el
Required Technical Specification
Description
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Hardware
support
and
Reporting
Manufacturer part
number
M
Warranty
6.15.
Lev
el
M
M
M
M
M
M
M
M
M
M
275
Reference
& Response
Administrative users authentication through local passwords
Unlimited number of security policies
Unlimited number of custom (admin-specified) URL categories
Appliance-based solution with a proprietary hardened OS
Minimum 4 gigabit Ethernet interfaces supported by hardware platform for
Web security solution
Multiple hard-drives in RAID array
Total drive space available at least 4TB
Minimum 32 GB of RAM
Dual-core CPU with multicore software support
Rack mount chassis
Vendor support access through e-mail, telephone, website
Access to vendor support portal and knowledgebase
Full hardware warranty throughout the support contract period
Web interface for reporting solution
Fully customizable reports
Custom report scripting capability
Possibility to drill down to each user's individual activity
Reports export and scheduling
Reporting implemented separately from main security appliances
Suspicious activity reporting per user
Bidder should submit BOQ of proposed device including the details part
numbers and Manufacturer warranty.
Bidder should submit the required performance document for the proposed
device.
Bidder should quote mentioning manufacturer's warranty and part number
and minimum 3 (Three) years full replacement warranty should be provided
for this unit from the date of successful commissioning.
WAN Router
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
Router
Processor
Service
Processor
RAM / DRAM
Power supply
Throughput
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant Report
in 2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Dedicated Route processor module would be an advantage
Dedicated services processor module would be an advantage
Min 8 GB DRAM/Memory
Redundant Power supplies.
Minimum 2.5 (Full-Duplex) Gbps from day 1, Upgradable to minimum 18
Gbps or more if required in future
Reference
& Response
276
Lev
el
Section VI. Technical Requirements
Description
M
M
M
M
VPN
M
M
M
M
Interface
No of slots.
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
General
Features
Required Technical Specification
Minimum 2 Mpps For the combination of the following commonly used
features: IPv4 forwarding, ACL and QoS. It can be scaled up to minimum 6
Mpps or more in future if required
Would be an advantage to have on board VPN acceleration mechanism
Should have the capability to expand up to minimum 7,500 IPSec tunnels
Router must have encryption capabilities to scale up to 8GbpsIPSec/crypto
throughput
Should have at least 4 x 1GE SFP Port with minimum 4 GE copper
transceivers with all the cables and accessories.
Should have minimum 2 x 10 GE routing port with minimum 10 GE multimode SFP transceivers with all the cables and accessories.
Minimum 1 module port adapter slot
Route Processors should have minimum 1GB of flash/internal memory to
support multiple software images for backup purposes and future scalability.
Would be an advantage to support dual Software for single-route-processor
solutions for a highly compact, fully redundant, high-availability solution.
Otherwise dual Route Processors have to be provided.
Route Processor should perform the following control processor functions:
 Build Layer 2 & Layer 3 forwarding information tables.
 Allow for centralized configuration of router including services like
stateful firewall, deep-packet inspection etc.
 Negotiating and maintaining IPSec authentication, encryption methods,
and encryption keys.
 Track the status of various system components like the software, services
processor, line cards, fan trays, PSU etc. & provide an out-of-band
access method to the router in case of a software crash
Dedicated Processor with following functions in hardware would be an
advantage.
 MAC classification & Layer 2 and Layer 3 forwarding, QoS
classification, policing and shaping
 Multicast replication with low-jitter traffic paths
 Security access control lists (ACLs),
 VPNs and load balancing,
Dedicated processor would be an advantage and should additionally support
the following functions in hardware with additional licenses:
 Firewall feature
 Network Based Application Recognition (NBAR) or similar technology
 Network Address Translation (NAT)
Should have the scalability up to 3500 GRE tunnels or more
 Must have minimum 900,000 IPv4 or minimum 900,000 IPv6 routes and
scaled up higher than 3,350,000 IPv4 or 2,900,000 IPv6 routes.
QoS should support per interface/port:
 Two Low Latency Queuing (LLQ) queues per policy, with more than
500 policies
Router should have an integrated auxiliary and/or console & 10/100
management interface, in addition it should support a standard USB interface
to allow for software image & configuration portability.
Should be capable of supporting 802.1q VLANs and VLAN trunking.
All modules, fan trays & Power supplies should be hot swappable without the
need of powering down the chassis during replacement.
Reference
& Response
Section VI. Technical Requirements
Lev
el
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Description
277
Required Technical Specification
Should support port aggregation for higher bandwidth and redundancy
The Gigabit Ethernet port should support multimode and single mode fiber
connectivity
The router should support wide variety of interfaces including E1, DS3 and
STM-1 on SDH and Channelized E1, Fast Ethernet and Gigabit Ethernet, 10
Gigabit Ethernet WAN Interface
Would be an advantage to support fast software patch upgrades while the
router is in service
Would be an advantage to provide Non-Stop Forwarding support to ensure
data forwarding during software switch-over or upgrade
Should have integrated diagnostics features
Should have modular software images, so that each software process runs
independent of the other thus allowing for higher stability.
Should support IPv6 from day 1.
The operating system should support a simple CLI interface for configuration
Should support the following WAN protocols : HDLC, PPP, and Frame Relay
Should support Multilink PPP as per RFC 1990.
Should support LFI (link fragmentation and Interleaving) for multiservice
networks
Should have RIPv2, OSPF, IS-IS and BGP4 routing protocols, with support
for all the features like OSPF on demand etc. & IP multicast routing protocols:
DVMRP, PIM Version 2 (Sparse Mode & Dense Mode), IGMP v1,v2,v3
Should have Enterprise Services feature set with support for protocols like
Multiprotocol Label Switching (MPLS), Ethernet over MPLS (EoMPLS) &
Virtual Route Forwarding (VRF)
The router should support multiple level of privileges and authentication for
user access, along with SSH support for secured device access
Should support authentication protocol for AAA
The software should support Network Address Translation (NAT) and Port
Address Translation (PAT)
Should support source and destinations based ACLs, time based ACLs, VLAN
/ Port-based ACLs & Dynamic reflexive ACLs and/or equivalent.
Should support MD5 authentication for routing protocols
The router must have IPsec encryption for data confidentiality, with support
for dedicated hardware modules to offload encryption processes from the CPU
would be an advantage.
The router should support 3DES and AES encryption standards
Should support protection against anti-replay attacks & perform Unicast
Reverse Path Forwarding in hardware, Policy based Routing
Must have IPSec Protocols: IPsec standards supported include Digital
Encryption Standard (DES), Triple DES (3DES), and Advanced Encryption
Standard (AES; 128, 192, and 256) for encryption; Rivest, Shamir, Aldeman
(RSA) algorithm signatures and Diffie Hellman for authentication; and Secure
Hash Algorithm 1 (SHA-1) or Message Digest Algorithm 5(MD5) hashing
algorithms for data integrity with the cryptographic engine in the router.
Support Detection of and response to distributed-denial-of-service (DDoS)
attacks
Support source-based filtering which provide wire-rate, real-time defense
against DDoS attacks
Support routing peers validation, enhances routing stability, and overload
protection by using MD5 peer authentication and redistribution protection
Reference
& Response
278
Lev
el
Section VI. Technical Requirements
Description
M
M
M
M
M
Manufacturer
part number
M
Warranty
6.16.
Lev
el
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
Enclosure Type
Architecture
Router Processor
Service
Processor
RAM / DRAM
Power supply
Forwarding
throughput
VPN
Interface
No of slots.
General Features
M
Reference
& Response
Should support RSVP
The router should be able to support IP precedence
Bidder should submit BOQ of proposed device including the details part
numbers and Manufacturer warranty.
Bidder should submit the required performance document for the proposed
device.
Bidder should quote mentioning manufacturer’s warranty and part number and
minimum 3 (Three) years full replacement warranty should be provided for
this unit from the date of successful commissioning.
Mentioning manufacturer's warranty and part number should be quoted,
minimum 3 (Three) years full replacement warranty should be provided for
this unit from the date of successful commissioning
Extranet Router
M
M
M
M
Required Technical Specification
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant
Report in 2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Rack-mountable
The router should be modular in architecture with a services-based
hardware architecture
Dedicated Route processor would be an advantage
Dedicated services processor module would be an advantage.
Minimum 8 GB DRAM/Memory
Redundant Power supplies.
Minimum 5 (Full-Duplex) Gbps from day 1, Upgradable through license to
33 Gbps or more if required in future
Would be an advantage to have on board VPN acceleration mechanism
Should have the capability to expand up to minimum 7,500 IPSec tunnels
Minimum 4 Mpps For the combination of the following commonly used
features: IPv4 forwarding, IP Multicast, ACL, QoS. It can be scaled up to
18 Mpps or more in future if required
Router should be scalable up to 4Gbps IPSec/crypto encryption throughput
Should have at least 6 x 1GE with 6x GE copper transceivers all the cables
and accessories should be included.
Minimum 3 module/shared port adapter slots
Route Processors should have minimum 1GB of flash/internal memory to
support multiple software images for backup purposes and future
scalability.
Router should have Software sub-package/patch Upgrade Option without
any Downtime or reload requirement.
Reference
& Response
Section VI. Technical Requirements
Lev
el
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Description
279
Required Technical Specification
Router should support software redundancy, if not please provide Route
processor redundancy based on hardware.
Route Processor should perform the following control processor functions:
 Build Layer 2 & Layer 3 forwarding information tables.
 Allow for centralized configuration of router including services like
stateful firewall, deep-packet inspection etc.
 Negotiating and maintaining IPSec authentication, encryption methods,
and encryption keys.
 Track the status of various system components like the software,
services processor, line cards, fan trays, PSU etc. & provide an out-ofband access method to the router in case of a software crash
Dedicated Processor would an advantage and should perform the following
functions in hardware
 MAC classification & Layer 2 and Layer 3 forwarding,
QoS classification, policing and shaping
 Multicast replication with low-jitter traffic paths
 Security access control lists (ACLs),
 VPNs and load balancing,
Services Processor supporting the following functions in hardware would
be an advantage.
 Firewall feature
 Network Based Application Recognition (NBAR) or similar
technology
 Network Address Translation (NAT)
 More than 3,900 unique ACLs
 Minimum 900 GRE tunnels and scaled up to 3,900 GRE tunnels or
more
 Must have minimum 490,000 IPv4 or minimum 123,500 IPv6 routes
and scale up higher than 3,350,000 IPv4 or 2,900,000 IPv6 routes
without any hardware install.
QoS should support per interface/port:
 Two Low Latency Queuing (LLQ) queues per policy, with more than
500 policies
Router should have an integrated auxiliary and/or console & 10/100
management interface, in addition it should support a standard USB
interface to allow for software image & configuration portability.
Should have status and health LEDs to diagnose system status on the front
panel.
Should be capable of supporting 802.1q VLANs and VLAN trunking.
All modules, fan trays & Power supplies should be hot swappable without
the need of powering down the chassis during replacement.
Should support port aggregation for higher bandwidth and redundancy
The Gigabit Ethernet port should support multimode and single mode fiber
connectivity
The router should support wide variety of interfaces including E1, DS3 and
STM-1 on SDH and Channelized E1, Fast Ethernet and Gigabit Ethernet,
10 Gigabit Ethernet WAN Interface
Should support IPv6 from day 1.
The operating system should support a simple CLI interface for
configuration
Reference
& Response
280
Lev
el
Section VI. Technical Requirements
Description
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Manufacturer
part number
M
Warranty
6.17.
Lev
el
M
M
M
M
M
Required Technical Specification
Reference
& Response
Should have RIPv2, OSPF, IS-IS and BGP4 routing protocols, with support
for all the features like OSPF on demand etc.& IP multicast routing
protocols: DVMRP, PIM Version 2 (Sparse Mode & Dense Mode), IGMP
v1,v2,v3
Should have Enterprise Services feature set with support for protocols like
Multiprotocol Label Switching (MPLS), Ethernet over MPLS (EoMPLS) &
Virtual Route Forwarding (VRF)
The router should support multiple level of privileges and authentication for
user access, along with SSH support for secured device access
Should support authentication protocol for AAA
The software should support Network Address Translation (NAT) and Port
Address Translation (PAT)
Should support source and destinations based ACLs, time based ACLs,
VLAN / Port-based ACLs
Should support MD5 authentication for routing protocols
The router should support 3DES and AES encryption standards
Must have IPSec Protocols: IPsec standards supported include Digital
Encryption Standard (DES), Triple DES (3DES), and Advanced Encryption
Standard (AES; 128, 192, and 256) for encryption; Rivest, Shamir,
Aldeman (RSA) algorithm signatures and Diffie Hellman for
authentication; and Secure Hash Algorithm 1 (SHA-1) or Message Digest
Algorithm 5(MD5) hashing algorithms for data integrity with the
cryptographic engine in the router.
Support Detection of and response to distributed-denial-of-service (DDoS)
attacks
Support source-based filtering which provide wire-rate, real-time defense
against DDoS attacks
Support routing peers validation, enhances routing stability, and overload
protection by using MD5 peer authentication and redistribution protection
Should support RSVP
The router should be able to support IP precedence
Bidder should submit BOQ of proposed device including the details part
numbers and Manufacturer warranty.
Bidder should submit the required performance document for the proposed
device.
Bidder should quote mentioning manufacturer's warranty and part number
and minimum 3 (Three) years full replacement warranty should be provided
for this unit from the date of successful commissioning
Internet Router
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant
Report in 2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Reference &
Response
Section VI. Technical Requirements
Lev
el
M
M
M
M
M
Description
Assemble /
Manufacture
Enclosure Type
Router
Processor Type
Service Support
Routing
Performance:
M
M
M
M
M
M
M
M
M
DRAM
Flash Memory
Status Indicators
M
M
Security:
Data
Protocol
Interfaces
Link
M
Protocols
M
Encapsulations
M
M
M
M
M
M
M
M
M
M
M
M
M
Traffic
management
Expansion Slots
Monitoring
Power Device
Redundant
power supply
Rack-mount
Manufacturer
part number
Warranty
281
Required Technical Specification
Rack-mountable - modular
High-performance multi-core processors
Device should support data, voice and video services
Minimum throughput of 1Gbps and upgradeable to 2 Gbps.
Module-to-Module communication without compromising router
performance.
Minimum 2 GB (installed) and upgradeable to Minimum 4 GB
Minimum 512 MB (installed) and upgradeable to Minimum 4 GB
Link activity, power
Minimum 4 x 10/100/1000Base-T - RJ-45, Routing Ports
Minimum 8 x 10/100/1000Base-T- RJ-45 Switch ports
Management : 1 x console
Serial : 1 x auxiliary - RJ-45
USB : minimum 1 x USB 2.0 Type A
Minimum 2 x SFP (mini-GBIC) for optical interface provision in future if
required
Should support inbuilt Stateful Firewall & Intrusion Prevention
Ethernet, Fast Ethernet, Gigabit Ethernet.
IPv4, IPv6, static routes, Open Shortest Path First (OSPF), Border Gateway
Protocol (BGP), BGP Router Reflector, Intermediate System-toIntermediate System (IS-IS), Multicast Internet Group Management
Protocol (IGMPv3), Protocol Independent Multicast.
Generic routing encapsulation, Ethernet, 802.1q VLAN, Point-to-Point
Protocol, High-Level Data Link Control (HDLC), Serial (RS-232, RS-449,
X.21, V.35)
QoS, Class-Based Weighted Fair Queuing, Weighted Random Early
Detection, Hierarchical QoS, Policy-Based Routing (PBR), Performance
Routing, and Network base Application inspection and treatment.
Minimum 3 WAN/LAN Interface Slots
Minimum 2 Service Module Slots
Should have SNMP, RMON, Syslog,
GUI Management, Telnet and SSH
Should have capability to monitor events and take informational, corrective,
Should have Network Flow Statistic , IP Service Level feature
Power supply - internal
Should have redundant power supply
Standard 19 inch rack mountable
Bidder should submit BOQ of proposed device including the details part
numbers and Manufacturer warranty.
Bidder should submit the required performance document for the proposed
device.
Bidder should quote mentioning manufacturer’s warranty and part number
and minimum 3 (Three) years full replacement warranty should be provided
for this unit from the date of successful commissioning.
Reference &
Response
282
6.18.
Lev
el
M
M
M
M
M
Section VI. Technical Requirements
iSCSI WAN Router
Description
Required Technical Specification
Quality
Certification
Brand
ISO, FCC, UL, CE or To be mentioned by the bidder
Model
Country of
Origin
Country of
Assemble /
Manufacture
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Architecture
Performance:
DRAM
Flash Memory
Interfaces
Requirements
Expansion
Slots
Security
Data Link
Protocol
Supported
Interfaces
Protocols
M
Encapsulation
s
M
M
QoS Features:
Shall support
the following
Internationally reputed top ten (10) brand of Gartner Magic Quadrant
Report in 2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Should be chassis based & modular architecture for scalability and
should be a single box configuration for ease of management.
Should have hardware based IPSEC VPN (3DES/AES) Encryption card.
Should support IPSEC VPN, Firewall & SSL VPN features.
Router should be quoted with AC power supply.
Should have a throughput of minimum 200 Mbps and upgradeable to 300
Mbps
Minimum 1 GB (installed) and upgradable to minimum 2 GB
Minimum 512 MB (installed) and upgradable to minimum 4 GB
Minimum 3 x 10/100/1000Base-T - RJ-45, Routing Port
Minimum 8 x 10/100/1000Base-T- RJ-45 Switch ports
Management : 1 x console
USB : Minimum 1 x USB 2.0 Type A
Minimum 3 WAN Interface Slots.
Minimum 1 Service/Network Module Slots
Embedded hardware-based cryptography acceleration (IPSec +Secure
Sockets Layer)
Should have Dynamic VPN to connect remote VPN devices
Should support IPsec Stateful Failover
Ethernet, Fast Ethernet, Gigabit Ethernet.
T1/E1, Channelized E1/T1, FXS, FXO, VDSL2/ADSL/2/2.
Up to 14 port L2 and L3 Switch module support
IPv4, IPv6, static routes, Open Shortest Path First (OSPF), Border
Gateway Protocol (BGP), BGP Router Reflector, Intermediate Systemto-Intermediate System (IS-IS), Multicast Internet Group Management
Protocol (IGMPv3), Protocol Independent Multicast sparse mode (PIM
SM), PIM Source Specific Multicast (SSM), Distance Vector Multicast
Routing Protocol (DVMRP), IPv4-to-IPv6 Multicast, MPLS, Layer 2
and Layer 3 VPN, IPSec, Layer 2 Tunneling Protocol Version 3
(L2TPv3).
Generic routing encapsulation, Ethernet, 802.1q VLAN, Point-to-Point
Protocol, High-Level Data Link Control (HDLC), Serial (RS-232, RS449, V.35).
QoS, Class-Based Weighted Fair Queuing, Weighted Random Early
Detection, Hierarchical QoS, Policy-Based Routing (PBR) or similar
technology, Performance Routing, and Network base Application
inspection and treatment.
Shall support WAN traffic optimization feature with internal module /
external device
Reference
& Response
Section VI. Technical Requirements
Lev
el
M
M
M
Description
Monitoring
Manufacturer
part number
M
warranty
6.19.
Lev
el
M
M
M
M
M
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
M
M
M
M
M
Switch
Architecture
M
M
M
M
M
M
Required Technical Specification
Reference
& Response
Should have Telnet, SSH, SNMP, Remote Monitoring (RMON).
Bidder should submit BOQ of proposed device including the details part
numbers and Manufacturer warranty.
Bidder should submit the required performance document for the
proposed device.
Bidder should quote mentioning manufacturer’s warranty and part
number and minimum 3 (Three) years full replacement warranty should
be provided for this unit from the date of successful commissioning.
Extranet Switch
M
M
M
283
Switch
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant
Report in 2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
The Switch should have at least 16 x 1GE SFP port for downlink switches
Bidder should propose at least 10 x 1G Single-mode SFP modules for
each switch and minimum 6 x 1G Copper Module. All the cables and
accessories should be included.
The Switch should support Redundant Power Supplies
The Switch should be Stackable and all the required components for
stacking should be included.
The Switch Architecture should be able to Stack at least 4 Switches
together.
The Switch stack should be based on Distributed forwarding Architecture,
where in each stack member forwards its own information on network.
The Switch Stack Architecture should have centralized control and
Management plane with Active Switch and all the information should be
Synchronized with Standby Switch.
The Switch should support Stateful Switchover (SSO) when switching
over from Active to Standby switch in a Stack.
The Switch should have USB for OS Management (uploading,
downloading & booting of OS and Configuration)
The Switch should have at least 1x 10/100/1000 dedicated Ethernet
Management Port
The Switch should have at least redundant fans and incase of failure of any
one of those the other fan should automatically speed up. Fans should be
field replaceable.
The Switch should have power savings mechanism wherein it should
reduce the power consumption on ports not being used.
The switch should be Rack Mountable and should not take space more
than 1RU.
The Switch should have at least 60Gbps nonblocking switching
Reference
& Response
284
Lev
el
Section VI. Technical Requirements
Description
Performance
M
M
M
M
M
M
M
M
Layer 3 Features
M
M
M
M
M
Layer 2 Features
M
M
M
Network
Security
Features
M
M
M
M
M
Quality
of
Service (QoS) &
Control
M
M
M
Manufacturer
part number
M
Warranty
Required Technical Specification
bandwidth.
The switch should have at least 40Mpps of forwarding rate.
The Switch should have at least 80Gbps Stack Bandwidth.
The Switch should support at least 31,000 MAC Addresses
The Switch should support at least 4,000 VLAN ID's
The Switch should support 9198 bytes of Jumbo Frames
The switch should support routing protocol such OSPF.
The Switch should support IPv6 Routing capable protocols such as
OSPFv3 in hardware.
The Switch should support IP Multicast and PIM, PIM Sparse Mode, PIM
Dense Mode, PIM Sparse-dense Mode & Source-Specific Multicast.
The switch should support basic IP Unicast routing protocols (static,
RIPv1 & RIPv2) should be supported.
The switch should support IPv6 & IPv4 Policy Based Routing (PBR)
The switch should support 802.1d, 802.1s, 802.1w Spanning-Tree &its
Enhancement for fast convergence.
The switch should support 802.1q VLAN encapsulation.
The switch should support 802.3ad (LACP) to combine multiple network
links for increasing throughput and providing redundancy.
The switch should have Port security to secure the access to an access or
trunk port based on MAC address to limit the number of learned MAC
addresses to deny MAC address flooding.
The switch should support DHCP snooping to prevent malicious users
from spoofing a DHCP server and sending out rouge addresses.
The switch should support Secure Shell (SSH) Protocol, Kerberos, and
Simple Network Management Protocol Version 3 (SNMPv3) to provide
network security by encrypting administrator traffic during Telnet and
SNMP sessions.
The switch should support Bridge protocol data unit (BPDU) Guard to
shut down Spanning Tree PortFast-enabled interfaces when BPDUs are
received to avoid accidental topology loops.
The switch should support Spanning Tree Root Guard to prevent edge
devices not in the network administrator’s control from becoming
Spanning Tree Protocol root nodes.
The Switch should support Advanced Modular QoS Policies
The Switch should be capable of Queuing, Policing, Shaping and marking
Wired and Wireless Traffic based on Class of Service (CoS) or DSCP.
The switch should support 802.1p CoS and DSCP Field classification
using marking and reclassification on a per-packet basis by source and
destination IP address, MAC address, or Layer 4 Transmission Control
Protocol/User Datagram Protocol (TCP/UDP) port number.
The Switch should support Rate limiting based on source and destination
IP address, source and destination MAC address.
Bidder should submit BOQ of proposed device including the details part
numbers and Manufacturer warranty.
Bidder should submit the required performance document for the proposed
device.
Bidder should quote mentioning manufacturer's warranty and part number
and minimum 3 (Three) years full replacement warranty should be
provided for this unit from the date of successful commissioning
Reference
& Response
Section VI. Technical Requirements
6.20.
Level
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
285
SAN Director Switch
Description
Quality
Certification
Brand
Model
Country of
Origin
Country of
Assemble /
Manufacture
Features
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant
Report in 2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
The fiber channel switch must be rack-mountable Thereafter, all
reference to the ‘switch’ shall pertain to the ‘fiber channel switch’
The switch must be able to support port requirements from a minimum
of 192 Fiber Channel ports and scalable to 384 ports.
All ports must include 16/8 G FC transceivers.
Number of ports to be provided in the solution are the following:
i) 144 units of 16 Gbps port with transceivers (including 2 units
minimum 70KM Supported LW transceivers having maximum
available speed) and required fiber Cables.
ii) 48 units of 8 Gbps ports with transceivers and required fiber
cables.
The switch must be able to provide 1024G of bandwidth per slot. The
switch must have non – blocking architecture.
The switch must support line rate minimum 16 Gig FC ports on all the
slots.
The proposed director must have redundant hot swappable supervisor
and Fabric modules.
The switch must support the following modules types:
2/4/8/16 Gbps or 10 Gbps FC Module
10 Gbps FCoE Module
All FC ports for device connectivity should be 2/4/8/16 Gbps autosensing Fiber Channel ports.
The switch module must support local switching across the entire 48ports on a module as one local switched domain.
The switch must have hot-swappable redundant power supply & fan
module without resetting the switch, or affecting the operations of the
switch.
The switch must be able to support non-disruptive software upgrade.
The switch must be able to support stateful process restart.
The switch must be capable of creating multiple hardware-based
isolated Virtual Fabric (ANSI T11) instances. Each Virtual Fabric
instance within the switch should be capable of being zoned like a
typical SAN and maintains its own fabric services, zoning database,
Name Servers and FSPF processes etc. for added scalability and
resilience.
The switch must support graceful process restart and shutdown of a
Virtual Fabric instance without impacting the operations of other
Virtual Fabric instances.
The switch must support Virtual Fabric instance 1 to 4094.
The switch shall support hot-swappable Small Form Factor Pluggable
Reference &
Response
286
Level
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Section VI. Technical Requirements
Description
Required Technical Specification
(SFP) LC typed transceivers.
The switch must support hardware ACL-based Port Security, Virtual
SANs (VSANs), Port Zoning and LUN Zoning
Inter-switch links must support the transport of multiple Virtual Fabrics
between switches, whilst preserving the security between Virtual
Fabrics.
The switch shall support FC-SP for host-to-switch and switch-to-switch
authentication.
The switch shall support the following Management Access Control
-SSHv2
-SNMPv3
-IP ACLs
The switch must support the following fabric services:
Name server
Internet Storage Name Server (iSNS)
Registered State Change Notification (RSCN)
Login services
Fabric Configuration Server (FCS)
Public loop
Broadcast
In-order delivery
The switch must support port mirroring for Fiber Channel, such that
traffic going to a specific port can be mirrored and forwarded to
another port for analyzing.
The switch must be able to immediately recover in the event of a failed
forwarding path going via an alternative path.
The switch must also support load balancing across multiple paths
through the fabric via Fabric Shortest Path First (FSPF).
Using FSPF, the switch must be able to load balance up to 16 equal
cost paths across the SAN network.
The switch must support port aggregation of up to 16 physical Fiber
Channel ports into a single aggregated link. The aggregated ports must
NOT be consecutive ports on a line card.
The switch must support the aggregation of any ports from any module.
Forwarding traffic must not be impacted when an individual ISL
connection within an aggregated link goes down.
FSPF must not re-converge when an individual ISL connection within
an aggregated link goes down.
The switch must be able to load balance traffic through an aggregated
link with Source ID and Destination ID. The support for load balancing
utilizing the Exchange ID must also be supported.
The switch must be equipped with congestion control mechanisms such
that it is able to throttle back traffic away from a congested link.
The switch must be capable of discovering neighboring switches and
identify the neighboring Fiber Channel switches.
The switch must support TACACS+ or RADIUS authentication when
managing from GUI, console or telnet to prevent unauthorized access
The switch must support Secure Shell Version 2 (SSHv2) with AES to
provide additional security for Telnet sessions to the switch.
The switch must support multilevel security on console access prevents
unauthorized users from altering the switch configuration.
Reference &
Response
Section VI. Technical Requirements
Level
Description
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
6.21.
Warranty
287
Required Technical Specification
Reference &
Response
The switch must support role-based administration by allowing
different administrators different access rights to the switch. Role-based
access control will use RADIUS or TACACS+ AAA functions.
The switch must support FICON CUP Management as an option with
license.
The switch must support VRRP for management connections.
The switch must support SNMPv3 with AES for secured management
access.
Switch must support Fiber Channel Traceroute and Fiber Channel Ping
for ease of troubleshooting and fault isolation. In addition, the switch
must also support the following diagnostics.
Power-on-self-test (POST) diagnostics
Online diagnostics
Internal loopbacks
Fabric Analyzer
SPAN
FC Debug
Syslog
Port level statistics
Real-Time Protocol (RTP) Debug
Switch must support out-band management protocols like SNMP,
SNMPv3, SMI-S, Telnet, FTP and SFTP.
The switch must support the use of an external port analyzer, which is
able to convert Fiber Channel frames to Ethernet frames so as to use a
conventional Ethernet based packet analyzer to capture the traffic and
analyze it as Fiber Channel.
For switch management, the management software must support both
Fabric wide and Device level management without the additional
purchase of software.
The switch must support SNMPv3—via Ethernet port and in-band IPover-FC access
The Fabric Manager software must be able to perform
GUI based management, configuration and diagnostics.
Discovery and Topology Mapping
Fabric View
Summary View
-Physical View
-Monitoring and Alerts
-Network Diagnostics
-Configuration Wizards
Bidder should quote mentioning manufacturer's warranty and part
number and minimum 3 (Three) years full replacement warranty should
be provided for this unit from the date of successful commissioning
Email Security for Microsoft Exchange
Level
Description
M
Quality
Certification
Required Technical Specification
ISO, FCC, UL, CE or To be mentioned by the bidder
Reference
& Response
288
Level
M
M
M
M
Section VI. Technical Requirements
Description
Required Technical Specification
Brand
Model
Country of Origin
Country of
Assemble /
Manufacture
M
M
M
Global
threat
intelligence
M
M
M
M
M
Spam Protection
M
M
M
M
M
M
M
M
M
M
Outbreak filters
M
M
M
M
Hardware
support
and
Internationally reputed top ten (10) brand of Gartner Magic Quadrant
Report in 2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
The device should have 6000 licenses for Email security control with
minimum of 3 years subscription.
The device should be capable of 10000 or more users capacity.
OEM of solution provider should have broad visibility and a large
footprint, including:
 50/More terabytes (TB) of security intelligence daily
 1.5 million/More deployed security devices including firewalls,
IPS sensors, and web and email appliances
 100 million/More endpoints
 10/More billion web requests per day and zero-hour attacks
Email security appliance should support antispam with multilayered
defense
Should support inner and outer layer of filtering
Should be capable of working with the reputation of the sender
Should performs a deep analysis of the message
Minimum 80 percent of spam should be blocked before it even hits
network
Should support contextual analysis
Should be able to do auto classification
Should have capability to filters based on the sender or subject
Should filters defend against emerging threats and blended attacks
Should be able to issue rules on any combination of six parameters,
including file type, file name, file size and URLs in a message
Should have capability to modify rules and release messages from
quarantine accordingly
Should be capable to rewrite URLs linked in suspicious messages
Website content should be actively scanned
Should detect graymail from sources like marketing, social networking,
and bulk messages
The safe unsubscribe solution provides:
 Protection against malicious threats masquerading as unsubscribe
links
 A uniform interface for managing all subscriptions
 Better visibility for email administrators and end users into such
emails
Appliances should be capable of supporting Advance Malware
protection in future in a same appliance
Should have future capability of file reputation scoring and blocking,
static and dynamic file analysis (sandboxing), and file retrospection for
the continuous analysis of threats, even after they have traversed the
email gateway
Appliance-based solution with a proprietary hardened OS
4 gigabit Ethernet and 2 Ten gigabit fiber Ethernet interfaces for email
security solution. Ten Gigabit port should be populated with short
Reference
& Response
Section VI. Technical Requirements
Level
Description
M
M
M
M
M
M
M
M
M
DLP
M
M
Manufacturer part
number
M
Warranty
6.22.
Level
Required Technical Specification
Reference
& Response
range transceiver from day one. Transceiver and appliance should be
same OEM product.
Multiple hard-drives in RAID -10
Total drive space available at least 1.6TB/More
32 GB of RAM
2 x 6 (2 hexa cores)
Rack mount chassis
Vendor support access through e-mail, telephone, website
Access to vendor support portal and knowledgebase
Full hardware warranty throughout the support contract period
Should be able to Delivers high performance, comprehensive DLP
helping prevent leaks, enforce compliance, and protect brand and
reputation. One or more predefined policies (several options to choose
from) to help prevent confidential data from leaving the network. It
should be able to use parts of those predefined policies to create own
custom policies. The built-in email DLP engine uses data structures
along with own optional data points such as words, phrases,
dictionaries, and regular expressions to quickly create accurate policies.
Bidder should submit BOQ of proposed device including the details
part numbers and Manufacturer Warranty.
Bidder should submit the required performance document for the
proposed device.
Bidder should quote mentioning manufacturer's warranty and part
number and minimum 3 (Three) years full replacement warranty should
be provided for this unit from the date of successful commissioning
Notebook Computer
Description
M
Quality
Certification
M
Brand
M
M
Model
Country of Origin
Country of
Assemble /
Manufacture
M
289
M
Display
M
M
Processor
M
Memory
M
Storage
Required Technical Specification
To be mentioned by the bidder
Internationally reputed top ten (10) brand of Gartner Magic Quadrant
Report in 2014/2015
To be mentioned by the bidder
USA or EU
To be mentioned by the bidder
Retina display: Minimum 13.3-inch (diagonal) LED-backlit display
with IPS technology. Minimum 2560-by-1600 resolution at 227 pixels
per inch with support for millions of colours
Native resolution: Minimum 2560 by 1600 pixels (Retina);
Minimum scaled resolutions: 1680 by 1050, 1440 by 900, and 1024 by
640 pixels
Minimum 3.1GHz dual-core Intel Core i7 (Turbo Boost up to 3.4GHz)
with 4MB shared L3 cache.
Minimum 8GB of 1866MHz LPDDR3 onboard memory and
configurable to 16GB
Minimum 512GB PCIe-based flash storage and configurable to 1TB
flash storage.
Reference &
Response
290
Level
Section VI. Technical Requirements
Description
M
M
M
M
M
Graphics and
Video Support
M
M
M
Camera
M
Connections and
Expansions
M
M
Wireless
M
Audio
M
Keyboard and
Trackpad
M
M
M
Battery and Power
M
M
Electrical and
Operating
Requirements
M
M
M
M
Operating System
OS Supported
M
Accessories
Requirements
M
Required Technical Specification
Intel Iris Graphics 6100 or better
Dual display and video mirroring: Simultaneously supports full native
resolution on the built-in display and up to 3840 by 2160 pixels on up
to two external displays, both in millions of colours
Thunderbolt digital video output
Native Mini DisplayPort output
DVI, VGA, dual-link DVI, and HDMI output supported using Mini
DisplayPort adapters
HDMI video output
Should support for 1080p resolution at up to 60Hz
Should support for 3840-by-2160 resolution at 30Hz
Should support for 4096-by-2160 resolution at 24Hz
Minimum 720p FaceTime HD camera
Minimum One MagSafe 2 power port
Minimum Two Thunderbolt 2 ports (up to 20Gb/s)
Minimum Two USB 3 ports (up to 5Gb/s)
Minimum One HDMI port
Minimum One Headphone port
802.11ac Wi-Fi wireless networking; IEEE 802.11a/b/g/n compatible
Bluetooth 4.0 wireless technology
Stereo speakers
Dual microphones
Headphone port
Support for Apple iPhone headset with remote and microphone
Support for audio line out (digital/analog)
Full-size backlit keyboard with 78 (US) or 79 (ISO) keys, including 12
function keys and four arrow keys (inverted ‘T’ arrangement) with
ambient light sensor
Force Touch trackpad for precise cursor control and pressure-sensing
capabilities; enables Force click, accelerators, pressure-sensitive
drawing and Multi-Touch gestures
Up to minimum 10 hours wireless web
Up to 12 hours iTunes movie playback
Up to minimum 30 days of standby time
Built-in minimum 74.9-watt-hour lithium-polymer battery
Minimum 60W MagSafe 2 Power Adapter with cable management
system; MagSafe 2 power port
Line voltage: 100V to 240V AC
Operating Frequency: 50Hz to 60Hz
Operating temperature: 10° to 35° C (50° to 95° F)
Storage temperature: –25° to 45° C (–13° to 113° F)
Relative humidity: 0% to 90% noncondensing
OS X El Captain.
Microsoft Windows 10
One MagSafe 2 Power Adapter
One set AC wall plug and Power cord
One Mini DisplayPort to VGA Adapter. Compatible with Mac
computers with Mini DisplayPort and Thunderbolt ports
One Thunderbolt to Gigabit Ethernet Adapter: Apple Thunderbolt to
Gigabit Ethernet Adapter with built-in Thunderbolt cable, compatible
with OS X v10.7.4 or later
Reference &
Response
Section VI. Technical Requirements
Level
Description
M
Carrying Case
M
M
Warranty
291
Brenthaven Collins Slim Brief Bag, Quantity: Thirty for thirty
notebook computers. Color: Blue (15 units) and Grey (15 units)
Quilted pockets for iPad and up to a 15-inch MacBook
Quick-access pocket for iPhone
Mobile battery compartment for easy charging
Removable shoulder strap
Soft, durable chambray exterior
Vegan leather trim (PVC free)
A separate compartment holds a battery or charger for powering
devices on the go.
Part Number: UPC or EAN No.: 730791195400
Form Factor: Brief Case, Shoulder Bag, Shoulder Case
Material: Cotton, Synthetic, Vegan Leather
Height: 34.29 cm/13.5 in.
Width: 5.08 cm/2 in.
Length: 43.18 cm/17 in.
Bidder should quote mentioning manufacturer's warranty and part
number and minimum One (01) year full replacement warranty should
be provided for this unit from the date of successful commissioning
6.23.
Software Specifications
6.24.
Business Application Software: Not applicable.
6.25.
System Management, Administration, and Security Specifications
Level
M
M
M
M
6.26.
Level
M
Reference &
Response
Required Technical Specification
Description
Reference &
Response
General Requirements: In addition to the management,
administration, and security requirements specified in each sections
covering the various hardware and software components of the
System, the System must also provide for the following management,
administration, and security features at the overall system level.
Technical management and troubleshooting: Supporting management
software will be capable to provide performance monitoring and
diagnostic tools giving immediate system information.
User and usage administration: Infrastructure as a service solution
should be capable to manage users and usage of delivered hardware
Security: The system must have full security facilities to control
access to data and processing at each terminal meeting C-2 security
standards. Security and encryption means used by the system must
comply with international standards.
Service Specifications
Description
System Integration: Different application system will be deployed in the
delivered hardware. Proper functioning of the delivered hardware is the
Reference &
Response
292
Section VI. Technical Requirements
Level
M
M
M
Reference &
Response
Description
key to integrate systems.
Training and Training Materials:
All training should be conducted by the certified trainers with prior
approval from the Purchaser. Necessary stationery required for the training
shall be arranged by the Bidder, at its own cost.
Training must be conducted by OEM authorized trainer only. Original
Training materials must be provided to all participants along with training
completion certificate from OEM so that participant can sit for
certification.
For Local Training vendor must confirm the facility of high bandwidth
internet for labs, snacks for morning and evening along with standard
lunch and dedicated classroom environment during the training period.
M
For overseas/foreign training, the Bidder/vendor must include and confirm
both way air ticket, Hotel accommodation, Food, Training Fees, Per diem
(US$ 100/day/per participant), both way airport to hotel transfer etc.
M
The Bidder/Vendor must take concern from contractor/customer while
scheduling training and there must be time gap between training modules.
6.27.
Level
Technical Training Specifications
Training Course Description
Number
of
Trainee
Minimum
Course Length
(6 hours/day)
Location
M
Training on Offered Firewall, IPS, AVC,
URL Filter, Web security, Content Filter
installation, configuration, troubleshooting,
maintenance etc.
6
30 hours Malaysia/
Singapore
M
Training on Load balancer, Bandwidth
Manager installation, configuration,
troubleshooting, maintenance etc.
Training on Router installation,
configuration, troubleshooting, maintenance
etc.
Training on Application Centric
Infrastructure installation, configuration,
troubleshooting, maintenance etc.
Training on Data Center Networking
6
30 hours Malaysia/
Singapore
M
M
M
10
6
10
24 hours Local
30 hours Malaysia/
Singapore
72 hours Local
Reference
& Response
Section VI. Technical Requirements
293
6.28. Technical Support:
Level
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
Description
Warranty Service
All Hardware equipment and Software should have a warranty period that is in conformance
with the specifications supplied in the Technical Specification. During the warranty Period,
the Bidder will be responsible for the repair, replacement, support of all malfunctioning
equipment and software supplied under this Bid.
The Bidder shall provide on-site support for warranty Period. Repair and replacement of
equipment should be completed to the satisfaction of the Purchaser within the times specified
in Maintenance Service Level
The Bidder should provide proper documentation from product manufacturer that conforms
24x7x365 online support
The Bidder should provide hot-line support.
The Bidder will have to undertake immediate repair actions in the event of
software/hardware failure causing an interruption of operation of the DC, NDC and DRS
systems.
The Bidder must notify about all the detected software errors and correct them in a shortest
possible time.
The Bidder should offer the new versions/releases of software and supervise their
implementation in mutually agreed deadlines.
The Bidder should enter into the obligation that in the event he releases a new version of
software, and the Purchaser is using one of the previous versions, he will provide the full
scope of services to the version used by the Purchaser for the period of at least 5 years from
the date it was purchased.
The software service must be conducted in a manner not compromising the security of Bank's
data and not compromising the quality of operation of the Bank, particularly the services
rendered to customers (Banks).
The Bidder should ensure maintenance support between the guaranteed resolution times
mentioned in the Service Levels. Failing of the resolution time, a penalty of one half of one
percent (0.5%) of the cost of the related units shall be charged per day for nonconformance
of the supplied Hardware, Software and services.
The Bidder must submit as part of their proposal a detailed plan including required
manpower to support the supplied Hardware and Software. Manpower can be changed with
the advance approval of the Purchaser.
The bidder should maintain the following user support:
The Bidder must have service capability in Bangladesh Bank offices (Dhaka and Rajshahi).
A suitable Helpdesk and Service Center must be established to ensure a high level of service.
Manpower requirements for Helpdesk and Service Centers shall be specified by the Bidder.
The Helpdesk shall be located at the Bangladesh Bank Head Office premises. Necessary
facilities (such as office accommodation, telephone etc.) will be provided by the
Purchaser.
The Bidder should provide trained, experienced and certified technical manpower for onsite
support in the Bangladesh Bank during all days.
Service records must be maintained at the Helpdesk for both hardware and software warranty
support. In addition, calls to the Helpdesk must be tracked including the disposition and
subsequent resolution of problem. These records are to be reviewed monthly with the
Purchaser.
A satisfactory stock of spare parts/ complete units (list of spare parts/complete unit should
be attached with proposal) must be maintained for support of all items supplied in this
tender. An inventory stock of spare parts status should be maintained and reviewed by the
Purchaser on a monthly basis.
Availability of all parts must be assured for a minimum of the same version or compatible
Reference &
Response
294
Section VI. Technical Requirements
Level
Reference &
Response
Description
higher version for five (05) years from the date of system acceptance.
The Bidder is responsible for notification and installation/upgrade of new versions/releases
of software/firmware and patch within mutually agreed timeframes.
M
6.29. Maintenance Service:
The Bidder must ensure (through evidences) that their respective Local Agents are capable of
maintaining Service Levels as described below:
A. Within Dhaka City:
Level
M
Item
Routers, Switches,
Content Filters etc.
Software
Spare replacement
M
M
Firewalls,
warranty Period
Response Time
Resolution Time
02 Hours
24 Hours
02 Hours
02 Hours
Response
24 Hours
04 Hours
B. Rajshahi City:
Level
Item
M
warranty Period
Response Time
Resolution Time
02 Hours
48 Hours
Routers, Switches, Firewalls,
Content Filters etc.
Software
Spare replacement
M
M
02 Hours
02 Hours
Level
M
Response
48 Hours
24 Hours
Reference &
Response
Description
Technical Assistance: The Bidder should provide minimum one Graduate Engineers having ICT
related degree and a minimum of five (05) years of proven experience in respective field (such as
Firewall, Content Filter, Router, Spine Switch, SAN Switch etc.) for Head Office in Dhaka.
Network Migration: Existing network environment will be migrated to the proposed network
solution using IPv4 initially and IPv6 subsequently.
M
6.30.
Documentation Requirements
The Bidder should provide detail information regarding the documentation that will be
supplied with the system. The following minimum documentation (hard copy and soft copy)
on the proposed systems must be made available in English:
Level
M
M
M
M
Description
Project Documentation
Project Management Controls
Project Plans
Implementation Controls
Quality Controls
Reference &
Response
Section VI. Technical Requirements
Level
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
M
295
Description
Scope Management Controls
Progress Reports
System Documentation
Requirement Specifications
Technical Specifications
System Descriptions & Specifications
Installation Manuals
System Administration Guide
Maintenance Documentation
User Documentation
Training Requirements
Training Documentations
User Guides
Administrator Documentations
Transaction Processing Guidelines
Operational Processing Guidelines
Operational Procedures
Error Correction Procedures
Testing Specifications
Updates:
The Bidder/Vendor must assure on-going documentation updates
The Bidder/Vendor must supply the documentation of the
applications on optical disks or other digital media together with
the system for its updating as changes are introduced
Technical Documents (Hard copy and Soft Copy):
Documentation should be consistent with international standards
Documentation should be user-friendly
Documentation should be indexed
Diagrams and schematics should be provided where possible to
facilitate practical understanding.
Technical documentation appropriate to the hardware and systems
that are being provided must be made available in both hard copy
and soft copy (CD-ROM). A commitment to providing updated
versions must be given.
Reference &
Response
Section VI. Technical Requirements
297
H. ATTACHMENTS
Section VI. Technical Requirements
Attachment 1: Existing Information Systems / Information Technologies
299
300
Section VI. Technical Requirements
Existing Information Systems
Bangladesh Bank has Data Center and Disaster Recovery Site in Dhaka. All Branch offices
has server rooms. Most of the critical business processes are automated.
Section VI. Technical Requirements
Attachment 2: Site Drawings and Site Survey Information
301
302
Section VI. Technical Requirements
Section VI. Technical Requirements
Attachment 3: Available Training Facilities
303
304
Section VI. Technical Requirements
In-house Training Facilities at Bangladesh Bank
Bangladesh Bank Training Academy (BBTA)
The BBTA is situated at Mirpur-2 area in Dhaka city. The BBTA has training rooms for
standard class instruction fitted with white boards. Each classroom can cater for a maximum
of thirty (30) students.
In addition, there is a computer training facility that has sufficient number of PCs each
operating in a stand-alone mode. The BBTA has a permanent training staff of trainers who
are supplemented, when required, from a pool of an additional senior staff within BB who
have particular skills and experience to bring to the training courses. BBTA also offers IT
related training courses. BBTA also have access to other specialists within Dhaka who
provide specific topic experience and training in their areas of expertise.
Section VI. Technical Requirements
Attachment 4: Project and Corporate Management Structure
305
306
Section VI. Technical Requirements
Project and Corporate Management Structure
The IT implementation process will be organised for maximum effectiveness with full senior
management involvement. Structures will be in place for decision-making, communication,
and management.
Steering Committee
The top level in the IT Project Management organisation structure is the Steering Committee.
The functions of the Steering Committee are to:





Take overall ownership for the IT Project & other project components
Be responsible for major project decisions
Operate as the Project oversight committee
Determine policy issues concerning the IT project
Review the key progress reports of the IT Project
The Steering Committee is headed by Chairman (Governor) with members from senior BB
personnel, Ministry of Finance (MOF) and other GOB representatives. The Steering
Committee will meet at regular fixed intervals.
The Supplier shall engage a Project Manager (PM) for successful implementation of the
project. The PM’s role is to provide Project Management services for the IT implementation
and s/he will report to the Systems Manager or his delegated representatives on project status,
progress, risks identified, and issues.
Project Manager and Sub-Project Managers
The BB will designate a Project Manager who shall assist the Executive Director (ICT) in the
implementation of the contract with the supplier. The Project manager will also coordinate
the activities of all sub-projects teams. Each sub-project within this IT Project will have a BB
appointed Sub-Project Manager (Team leader) and sub-project team. The Sub-Project
Manager will report to the Project Manager as and when required.
307
SECTION VII. SAMPLE FORMS
308
Section VII. Sample Forms
Notes to Bidders on working with the Sample Forms
The Purchaser has prepared the forms in this section of the Bidding Documents to suit
the specific requirements of the System being procured. They are derived from the forms
contained in the World Bank’s Standard Bidding Documents for the Supply and Installation
of Information Systems. In its bid, the Bidder must use these forms (or forms that present in
the same sequence substantially the same information). Bidders should not introduce changes
without the Purchaser’s prior written consent (which may also require the clearance of the
World Bank). If the Bidder has a question regarding the meaning or appropriateness of the
contents or format of the forms and/or the instructions contained in them, these questions
should be brought to the Purchaser’s attention as soon as possible during the bid clarification
process, either at the pre-bid meeting or by addressing them to the Purchaser in writing
pursuant to ITB Clause 10.
The Purchaser has tried to provide explanatory text and instructions to help the Bidder
prepare the forms accurately and completely. The instructions that appear directly on the
forms themselves are indicated by use of typographical aides such as italicized text within
square brackets as is shown in the following example taken from the Bid Submission Form:
Duly authorized to sign this bid for and on behalf of [ insert: name of Bidder ]
In preparing its bid, the Bidder must ensure all such information is provided and that
the typographical aides are removed.
The sample forms provide a standard set of documents that support the procurement
process as it moves forward from the stage of bidding, through Contract formation and onto
Contract performance. The first set of forms must be completed and submitted as part of the
bid prior to the deadline for bid submission. These include: (i) the Bid Submission Form; (ii)
the Price Schedules; (iii) the Manufacturer’s Authorizations and key Subcontractor
agreements; (iv) the List of Proposed Subcontractors; (v) the form(s) for securing the bid (if
and as required); and other forms as found in sub-sections 1 through 4 of this Section VII of
the Bidding Documents.

Bid Submission Form: In addition to being the place where official confirmation of
the bid price, the currency breakdown, the completion date(s), and other important
Contract details are expressed, the Bid Submission Form is also used by the Bidder to
confirm - in case adjudication applies in this Contract - its acceptance of the
Purchaser’s proposed Adjudicator, or to propose an alternative. If the bid is being
submitted on behalf of a Joint Venture, it is essential that the Bid Submission Form be
signed by the partner in charge and that it be supported by the authorizations and
power of attorney required pursuant to ITB Clause 6.2. Given widespread concern
about illegal use of licensed software, Bidders will be asked to certify in the Bid
Submission Form that either the Software included in the bid was developed and is
owned by the Bidder, or, if not, the Software is covered by valid licenses with the
proprietor of the Software.
Section VII. Sample Forms

309
Price Schedules: The prices quoted in the Price Schedules should constitute full and
fair compensation for supply, installation, and achieving Operational Acceptance of
the System as described in the Technical Requirements based on the Implementation
Schedule, and the terms and conditions of the proposed Contract as set forth in the
Bidding Documents. Prices should be given for each line item provided in the
Schedules, with costs carefully aggregated first at the Subsystem level and then for
the entire System. If the Price Schedules provide only a summary breakdown of items
and components, or do not cover some items unique to the Bidder’s specific technical
solution, the Bidder may extend the Schedules to capture those items or components.
If supporting price and cost tables are needed for a full understanding of the bid, they
should be included.
Arithmetical errors should be avoided. If they occur, the Purchaser will correct them
according to ITB Clause 26.2 (ITB Clause 38.2 in the two-stage SBD) without
consulting the Bidder. Major omissions, inconsistencies, or lack of substantiating
detail can lead to rejection of a bid for commercial non-responsiveness. Presenting
prices according to the breakdown prescribed in the Price Schedules is also essential
for another reason. If a bid does not separate prices in the prescribed way, and, as a
result, the Purchaser cannot apply the domestic preference provision described in ITB
Clause 29 (ITB Clause 41 in the two-stage SBD), if they are applicable in this
bidding, the Bidder will lose the benefit of the preference. Once bids are opened, none
of these problems can be rectified. At that stage, Bidders are not permitted to change
their bid prices to overcome errors or omissions.

Manufacturer’s Authorizations and written agreements by key Subcontractors: In
accordance with ITB Clauses 6.1 (b) and (c), a Bidder may be required to submit, as
part of its bid, Manufacturer’s Authorizations in the format provided in the Bidding
Documents, and agreements by Subcontractors proposed for key services, for all items
specified in the Bid Data Sheet. There is no particular format (or sample form) for
Subcontractor agreements.

List of Proposed Subcontractors: In accordance with ITB Clause 6.3, a Bidder must
submit, as part of its bid, a list of proposed subcontracts for major items of
Technologies, Goods, and/or Services. The list should also include the names and
places of registration of the Subcontractors proposed for each item and a summary of
their qualifications.

List of Software and Materials: In accordance with ITB Clause 13.1 (e) (vi) (ITB
Clauses 13.1 (c) (vi) and 25.1 (e) (vi) in the two-stage SBD), Bidders must submit, as
part of their bids, lists of all the Software included in the bid assigned to one of the
following categories: (A) System, General-Purpose, or Application Software; or
(B) Standard or Custom Software. Bidders must also submit a list of all Custom
Materials. If provided for in the Bid Data Sheet, the Purchaser may reserve the right to
reassign certain key Software to a different category.

Qualification information forms: In accordance with ITB Clause 6, the Purchaser will
determine whether the Bidder is qualified to undertake the Contract. This entails
financial, technical as well as performance history criteria which are specified in the
310
Section VII. Sample Forms
BDS for ITB Clause 6. The Bidder must provide the necessary information for the
Purchaser to make this assessment through the forms in this sub-section. The forms
contain additional detailed instructions which the Bidder must follow.

Securing the bid: If the BDS for ITB Clause 17 (ITB Clause 29 in the two-stage SBD)
requires that bids be secured, the Bidder shall do so in accordance with the type and
details specified in the same ITB/BDS Clause, either using the form(s) included in
these Sample Forms or using another form acceptable to the Purchaser. If a Bidder
wishes to use an alternative form, it should ensure that the revised format provides
substantially the same protection as the standard format; failing that, the Bidder runs
the risk of rejection for commercial non-responsiveness.
Bidders need not provide the Performance Security and Advance Payment Security
with their bids. Only the Bidder selected for award by the Purchaser will be required to
provide these securities.
The following forms are to be completed and submitted by the successful Bidder
following notification of award: (i) Contract Agreement, with all Appendices;
(ii) Performance Security; and (iii) Advance Payment Security.

Contract Agreement: In addition to specifying the parties and the Contract Price, the
Contract Agreement is where the: (i) Supplier Representative; (ii) if applicable,
agreed Adjudicator and his/her compensation; and (iii) the List of Approved
Subcontractors are specified. In addition, modifications to the successful Bidder’s Bid
Price Schedules are attached to the Agreement. These contain corrections and
adjustments to the Supplier’s bid prices to correct errors, adjust the Contract Price to
reflect – if applicable - any extensions to bid validity beyond the last day of original
bid validity plus 56 days, etc.

Performance Security: Pursuant to GCC Clause 13.3, the successful Bidder is required
to provide the Performance Security in the form contained in this section of these
Bidding Documents and in the amount specified in accordance with the SCC.

Advance Payment Security: Pursuant to GCC Clause 13.2, the successful Bidder is
required to provide a bank guarantee for the full amount of the Advance Payment - if
an Advance Payment is specified in the SCC for GCC 12.1 - in the form contained in
this section of these Bidding Documents or another form acceptable to the Purchaser.
If a Bidder wishes to propose a different Advance Payment Security form, it should
submit a copy to the Purchaser promptly for review and confirmation of acceptability
before the bid submission deadline.
The Purchaser and Supplier will use the following additional forms during Contract
implementation to formalize or certify important Contract events: (i) the Installation and
Operational Acceptance Certificates; and (ii) the various Change Order forms. These and the
procedures for their use during performance of the Contract are included in the Bidding
Documents for the information of Bidders.
Section VII. Sample Forms
311
Table of Sample Forms
1. Bid Submission Form (Single-Stage Bidding) ...............................................................313
2. Price Schedule Forms ......................................................................................................317
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
2.9
2.10
Preamble .................................................................................................................318
Grand Summary Cost Table ....................................................................................320
Supply Cost Summary Table ..................................................................................321
Installation Cost Summary Table ............................................................................322
Training Cost Summary Table ................................................................................323
Supply Cost Sub-Table [ insert: identifying number ] ...........................................324
Installation Cost Sub-Table [ insert: identifying number ].....................................326
Training Services Cost Sub Table...........................................................................329
Taxes and Duties Cost Table ..................................................................................330
Country of Origin Code Table ................................................................................331
3. Other Bid Forms and Lists..............................................................................................332
3.1 Manufacturer’s Authorization .................................................................................333
3.2 List of Proposed Subcontractors .............................................................................334
3.3 Software List ...........................................................................................................335
3.4 List of Custom Materials ........................................................................................336
3.5.1 General Information Form ......................................................................................337
3.5.2 General Information Systems Experience Record ..................................................338
3.5.2a Joint Venture Summary.........................................................................................339
3.5.3 Particular Information Systems Experience Record ...............................................340
3.5.3a Details of Contracts of Similar Nature and Complexity .......................................341
3.5.4 Summary Sheet: Current Contract Commitments / Work in Progress ...................342
3.5.5 Financial Capabilities..............................................................................................343
3.5.6 Personnel Capabilities .............................................................................................345
3.5.6a Candidate Summary ..............................................................................................346
3.5.7 Technical Capabilities .............................................................................................347
3.5.8 Litigation History ....................................................................................................348
4. Bid-Securing Declaration ................................................................................................349
4A. Bid Security (Bank Guarantee) ...................................................................................350
4B. Bid Security (Bid Bond) ................................................................................................351
5. Contract Agreement ........................................................................................................352
Appendix 1. Supplier’s Representative............................................................................356
Appendix 2. Adjudicator ..................................................................................................357
Appendix 3. List of Approved Subcontractors ................................................................358
Appendix 4. Categories of Software ................................................................................359
312
Section VII. Sample Forms
Appendix 5. Custom Materials ........................................................................................360
Appendix 6. Revised Price Schedules .............................................................................361
Appendix 7. Minutes of Contract Finalization Discussions and Agreed-to Contract
Amendments ...........................................................................................................362
6. Performance and Advance Payment Security Forms ...................................................363
6.1 Performance Security Form (Bank Guarantee) .......................................................364
6.2 Advance Payment Security Form (Bank Guarantee) ..............................................365
7. Installation and Acceptance Certificates .......................................................................366
7.1 Installation Certificate .............................................................................................367
7.2 Operational Acceptance Certificate ........................................................................368
8. Change Order Procedures and Forms ...........................................................................369
8.1
8.2
8.3
8.4
8.5
8.6
Request for Change Proposal Form ........................................................................370
Change Estimate Proposal Form .............................................................................372
Estimate Acceptance Form .....................................................................................373
Change Proposal Form ............................................................................................374
Change Order Form ................................................................................................376
Application for Change Proposal Form ..................................................................378
Section VII. Sample Forms
313
1. BID SUBMISSION FORM (SINGLE-STAGE BIDDING)
Date:
Credit No.:
IFB Title:
IFB Number:
Contract:
56640
Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems
BB(G)IT-5
Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems
To: Executive Director (ICT), 6th Floor, Main Building, Bangladesh Bank, Head Office,
Dhaka
Dear Sir or Madam:
Having examined the Bidding Documents, including Addenda Nos. [ insert
numbers ], the receipt of which is hereby acknowledged, we, the undersigned, offer to
supply, install, achieve Operational Acceptance of, and support the Information System under
the above-named Contract in full conformity with the said Bidding Documents for the sum
of:
plus
[ insert: amount of local
currency in words ]
([ insert: amount of local currency in
figures from corresponding Grand
Total entry of the Grand Summary
Cost Table ])
[ insert: amount of foreign
currency A in words ]
([ insert: amount of foreign currency
A in figures from corresponding
Grand Total entry of the Grand
Summary Cost Table ])
[ as appropriate, add the following ]
plus
[ insert: amount of foreign
currency B in words ]
([ insert: amount of foreign currency
B in figures from corresponding
Grand Total entry of the Grand
Summary Cost Table ])
plus
[ insert: amount of foreign
currency C in words ]
([ insert: amount of foreign currency
C in figures from corresponding
Grand Total entry of the Grand
Summary Cost Table ])
314
Section VII. Sample Forms
or such other sums as may be determined in accordance with the terms and conditions of the
Contract. The above amounts are in accordance with the Price Schedules attached herewith
and made part of this bid.
We undertake, if our bid is accepted, to commence work on the Information System
and to achieve Installation and Operational Acceptance within the respective times stated in
the Bidding Documents.
If our bid is accepted, and if these Bidding Documents so require, we undertake to
provide an advance payment security and a performance security in the form, in the amounts,
and within the times specified in the Bidding Documents.
“We accept the appointment of the Adjudicator as indicated in the Bid Data Sheet.”
Or
“We do not accept the appointment of the Adjudicator as indicated in the Bid Data
Sheet ] as the Adjudicator, and we propose instead that [ insert: name ] be appointed as
Adjudicator, whose résumé and hourly fees are attached.”
We hereby certify that the Software offered in this bid and to be supplied under the
Contract (i) either is owned by us, or (ii) if not owned by us, is covered by a valid license
from the proprietor of the Software.
We agree to abide by this bid, which, in accordance with ITB Clauses 13 and 16,
consists of this letter (Bid Submission Form) and the enclosures listed below, for a period of
119 days from the date fixed for submission of bids as stipulated in the Bidding Documents,
and it shall remain binding upon us and may be accepted by you at any time before the
expiration of that period.
Commissions or gratuities, if any, paid or to be paid by us to agents relating to this
Bid, and to Contract execution if we are awarded the Contract, are listed below:
Name and Address
of Agent
Etc.
Amount and
Currency
Purpose of
Commission or
Gratuity
[if none, state: “none”]
Until the formal final Contract is prepared and executed between us, this bid, together
with your written acceptance of the bid and your notification of award, shall constitute a
binding contract between us. We understand that you are not bound to accept the lowest or
any bid you may receive.
Section VII. Sample Forms
315
Dated this [ insert: ordinal ] day of [ insert: month ], [ insert: year ].
Signed:
Date:
In the capacity of [ insert: title or position ]
Duly authorized to sign this bid for and on behalf of [ insert: name of Bidder ]
ENCLOSURES:
Price Schedules
Bid-Securing Declaration or Bid-Security (if and as required)
Signature Authorization [plus, in the case of a Joint Venture Bidder, list all other
authorizations pursuant to ITB Clause 6.2]
Attachment 1. Bidder’s Eligibility
Attachment 2. Bidder’s Qualifications (including Manufacturer’s Authorizations and
Subcontractor agreements if and as required)
Attachment 3. Eligibility of Goods and Services
Attachment 4. Conformity of the Information System to the Bidding Documents
Attachment 5. Proposed Subcontractors
Attachment 6. Intellectual Property (Software and Materials Lists)
[if appropriate, specify further attachments or other enclosures]
316
Section VII. Sample Forms
Bid Table of Contents and Checklist
Note: Bidders should expand and (if appropriate) modify and complete the following table.
The purpose of the table is to provide the Bidder with a summary checklist of items that must
be included in the bid as described in ITB Clauses 13.1 and 16, in order for the bid to be
considered for Contract award. The table also provides a summary page reference scheme to
ease and speed the Purchaser’s bid evaluation process.
Item
Bid Submission Form......................................................
Price Schedules ...............................................................
Bid-Securing Declaration / Bid-Security (if and as
required) ..........................................................................
Signature Authorization (for Joint Ventures additionally
including the authorizations listed in ITB Clause 6.2) ....
Attachment 1 ...................................................................
Attachment 2 ...................................................................
Manufacturer’s Authorizations .................................
Subcontractor agreements .........................................
Attachment 3 ...................................................................
Attachment 4 ...................................................................
Attachment 5 ...................................................................
Attachment 6 ...................................................................
.........................................................................................
present: y/n
page no.
Section VII. Sample Forms
317
2. PRICE SCHEDULE FORMS
Note: in information systems procurement, the Contract Price (and payment schedule)
should be linked as much as possible to achievement of operational capabilities, not just to
the physical delivery of technology.
318
Section VII. Sample Forms
2.1
Preamble
General
1.
The Price Schedules are divided into separate Schedules as follows:
2.2
Grand Summary Cost Table
2.3
Supply Cost Summary Table
2.4
Installation Services Cost Table
2.5
Training Services Cost Table
2.6
Supply Cost Sub-Table(s)
2.7
Installation Cost Sub-Table
2.8
Training Services Cost Sub-Table
2.9
Taxes and Duties Cost Table
2.10
Country of Origin Code Table
2.
The Schedules do not generally give a full description of the information technologies
to be supplied, installed, and operationally accepted, or the Services to be performed
under each item. However, it is assumed that Bidders shall have read the Technical
Requirements and other sections of these Bidding Documents to ascertain the full scope
of the requirements associated with each item prior to filling in the rates and prices. The
quoted rates and prices shall be deemed to cover the full scope of these Technical
Requirements, as well as overhead and profit.
3.
If Bidders are unclear or uncertain as to the scope of any item, they shall seek
clarification in accordance with the Instructions to Bidders in the Bidding Documents
prior to submitting their bid.
Pricing
4.
Prices shall be filled in indelible ink, and any alterations necessary due to errors, etc.,
shall be initialed by the Bidder. As specified in the Bid Data Sheet, prices shall be fixed
and firm for the duration of the Contract.
5.
Bid prices shall be quoted in the manner indicated and in the currencies specified in
ITB Clauses 14 and 15. Prices must correspond to items of the scope and quality
defined in the Technical Requirements or elsewhere in these Bidding Documents.
6.
The Bidder must exercise great care in preparing its calculations, since there is no
opportunity to correct errors once the deadline for submission of bids has passed. A
single error in specifying a unit price can therefore change a Bidder’s overall total bid
price substantially, make the bid noncompetitive, or subject the Bidder to possible loss.
The Purchaser will correct any arithmetic error in accordance with the provisions of
ITB Clause 26.2.
Section VII. Sample Forms
7.
319
Payments will be made to the Supplier in the currency or currencies indicated under
each respective item. As specified in ITB Clause 15.1, no more than three foreign
currencies may be used. The price of an item should be unique regardless of installation
site.
320
Section VII. Sample Forms
2.2
Grand Summary Cost Table
[ insert: Local
Currency ]
Price
1.
Supply Costs (from
Summary Table 2.3)
2.
Installation Costs (from Installation Cost
Summary Table 2.4)
3.
Training Services Costs (from Training
Services Cost Summary Table 2.5)
4.
Grand Totals (to Bid Submission Form)
5
Supply
Cost
Taxes and Duties (from Taxes and
Duties Table 2.9)
Name of Bidder:
Authorized Signature of Bidder:
[ insert: Foreign
Currency A ]
Price
[ insert: Foreign
Currency B ]
Price
[ insert: Foreign
Currency C ]
Price
Section VII. Sample Forms
321
2.3
Supply Cost Summary Table
System or Subsystem number: Entire System procurement [ as necessary for supply, installation, and achieving Operational
Acceptance of the System, specify items in the Table below, modifying, deleting, or expanding the sample line items and sample table
entries as needed. ]
Costs MUST reflect prices and rates quoted in accordance with ITB Clauses 14 and 15.
Line
Item
No.
1
1.1
1.2
2
2.1
2.2
3
3.1
3.2
Note:
Subsystem / Item
Supply
Cost SubTable No.
Locally
supplied items
BDT
Price
Supply Prices
Items supplied from outside the Purchaser’s Country
BDT
Price
[ insert:
Foreign
Currency A]
Price
[ insert:
Foreign
Currency B]
Price
[ insert:
Foreign
Currency C]
Price
Motijheel Data Center
1
Hardware
1
Software
1
….
Mirpur Data Center (NDC)
2
Hardware
2
Software
2
Rajshahi Disaster Recovery Site
Hardware
Software
SUBTOTALS
TOTAL (To Grand Summary Table)
- - indicates not applicable. “indicates repetition of table entry above. Refer to the relevant Supply Cost Sub-Table for the specific
components that constitute each Subsystem or line item in this summary table
Name of Bidder:
Authorized Signature of Bidder:
322
Section VII. Sample Forms
2.4
Installation Cost Summary Table
System or Subsystem number: Entire System procurement [ as necessary for supply, installation, and achieving Operational
Acceptance of the System, specify items in the Table below, modifying, deleting, or expanding the sample line items and sample table
entries as needed. ]
Costs MUST reflect prices and rates quoted in accordance with ITB Clauses 14 and 15.
Installation Prices
Line
Item
No.
1
1.1
1.2
2
2.1
2.2
3
3.1
3.2
Note:
Subsystem / Item
Supply Cost
Sub-Table
No.
Locally supplied
items
BDT
Price
Items supplied from outside the Purchaser’s Country
BDT
Price
[ insert:
Foreign
Currency A]
Price
[ insert:
Foreign
Currency B]
Price
[ insert:
Foreign
Currency C]
Price
Motijheel Data Center
1
Hardware
1
Software
1
Mirpur Data Center (NDC)
2
Hardware
2
Software
2
Rajshahi Disaster Recovery Site
Hardware
Software
SUBTOTALS
TOTAL (To Grand Summary Table)
- - indicates not applicable. “ indicates repetition of table entry above. Refer to the relevant Installation Cost Sub-Table for the
specific components that constitute each Subsystem or line item in this summary table
Name of Bidder:
Authorized Signature of Bidder:
Section VII. Sample Forms
323
2.5
Training Cost Summary Table
System or Subsystem number: Entire System procurement [ as necessary for supply, installation, and achieving Operational
Acceptance of the System, specify items in the Table below, modifying, deleting, or expanding the sample line items and sample table
entries as needed. ]
Costs MUST reflect prices and rates quoted in accordance with ITB Clauses 14 and 15.
Item
No.
Training Cost
Sub-Table No.
Description
1
2
3
4
5
6
Note:
Training on Offered Firewall, IPS, AVC, URL
Filter, Web security, Content Filter installation,
configuration, troubleshooting, maintenance etc.
Training on Load balancer, Bandwidth Manager
installation,
configuration,
troubleshooting,
maintenance etc.
Training on Router installation, configuration,
troubleshooting, maintenance etc.
Training on Application Centric Infrastructure
installation,
configuration,
troubleshooting,
maintenance etc.
Training on Data Center Networking
BDT
Price
Items supplied from outside the Purchaser’s Country
[ insert: Foreign
[ insert: Foreign
[ insert: Foreign
Currency A] Price Currency B] Price
Currency C]
Price
1
2
3
4
5
SUBTOTALS
TOTAL (To Grand Summary Table)
- - indicates not applicable. “ indicates repetition of table entry above. Refer to the relevant Installation Cost Sub-Table for the
specific components that constitute each Subsystem or line item in this summary table
Name of Bidder:
Authorized Signature of Bidder:
324
Section VII. Sample Forms
2.6
Supply Cost Sub-Table [ insert: identifying number ]
System or Subsystem number: Entire System procurement
Line item number: [ specify: relevant line item number from the Supply Cost Summary Table (e.g., 1.1) ]
The detailed components and quantities in the Sub-Table below for the line item specified above, modifying the sample
components and sample table entries as needed. Repeat the Sub-Table as needed to cover each and every line item in the Supply Cost
Summary Table that requires elaboration.
Prices, rates, and subtotals MUST be quoted in accordance with ITB Clauses 14 and 15. Unit prices for the same item appearing
several times in the table must be identical in amount and currency.
Compo
nent
No.
1
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
1.9
1.10
1.11
1.12
1.13
1.14
1.15
Component Description
Motijheel Data Center
Network Spine Switch
Network Leaf Switch Type-A
Network Leaf Switch Type-B
Network Aggregation Switch
Campus Distribution Switch for
DC
Server Farm Firewall
Extranet Firewall
Internet Firewall
Application Load Balancer
Bandwidth Manager
Content Filter
WAN Router
Extranet Router
Internet Router
iSCSI WAN Router
Country Quanof
tity
Origin
Code
Supplied
Locally
BDT
Unit Prices / Rates
Supplied from outside the Purchaser’s
Country
BDT [ insert:
[ insert
[ insert:
foreign
foreign
foreign
currency currency currency
A]
B]
C]
Supplied
Locally
BDT
Total Prices
Supplied from outside the Purchaser’s
Country
BDT
[ insert:
[ insert:
[ insert:
foreign
foreign
foreign
currency currency
currency
A]
B]
C]
Section VII. Sample Forms
Compo
nent
No.
2
3
Component Description
325
Country Quanof
tity
Origin
Code
Supplied
Locally
BDT
Unit Prices / Rates
Supplied from outside the Purchaser’s
Country
BDT [ insert:
[ insert
[ insert:
foreign
foreign
foreign
currency currency currency
A]
B]
C]
Extranet Switch
SAN Director Switch
Notebook Computer
Mirpur Data Center
Network Spine Switch
Network Leaf Switch Type-A
Network Leaf Switch Type-B
Network Aggregation Switch
Server Farm Firewall
Extranet Firewall
Internet Firewall
Application Load Balancer
Bandwidth Manager
Content Filter
WAN Router
Extranet Router
Internet Router
iSCSI WAN Router
Extranet Switch
SAN Director Switch
Disaster Recovery Site,
Rajshahi
Subtotals (to [ insert: line item ] of Supply Cost Summary Table)
Note: - - indicates not applicable.
Name of Bidder:
Authorized Signature of Bidder:
Supplied
Locally
BDT
Total Prices
Supplied from outside the Purchaser’s
Country
BDT
[ insert:
[ insert:
[ insert:
foreign
foreign
foreign
currency currency
currency
A]
B]
C]
326
Section VII. Sample Forms
2.7
Installation Cost Sub-Table [ insert: identifying number ]
System or Subsystem number: Entire System procurement
Line item number: [ specify: relevant line item number from the Installation Cost Summary Table (e.g., 1.1) ]
The detailed components and quantities in the Sub-Table below for the line item specified above, modifying the sample
components and sample table entries as needed. Repeat the Sub-Table as needed to cover each and every line item in the Installation
Cost Summary Table that requires elaboration.
Prices, rates, and subtotals MUST be quoted in accordance with ITB Clauses 14 and 15. Unit prices for the same item appearing
several times in the table must be identical in amount and currency.
Supplied
Locally
Component
No.
Component Description
1.
Motijheel Data Center
Network Spine Switch
Network Leaf Switch
Type-A
Network Leaf Switch
Type-B
Network Aggregation
Switch
Campus Distribution
Switch for DC
Server Farm Firewall
Extranet Firewall
Internet Firewall
Application Load
Balancer
Bandwidth Manager
Content Filter
Country
of Origin
Code
Quantity
BDT
Unit Prices / Rates
Supplied from outside the
Purchaser’s Country
BDT
[ insert:
foreign
currency
A]
[ insert
foreign
currency
B]
[ insert:
foreign
currency
C]
Supplied
Locally
BDT
Total Prices
Supplied from outside the Purchaser’s
Country
BDT
[ insert:
foreign
currency
A]
[ insert:
foreign
currency
B]
[ insert:
foreign
currency
C]
Section VII. Sample Forms
327
Supplied
Locally
Component
No.
2
3
Component Description
WAN Router
Extranet Router
Internet Router
iSCSI WAN Router
Extranet Switch
SAN Director Switch
Mirpur Data Center
Network Spine Switch
Network Leaf Switch
Type-A
Network Leaf Switch
Type-B
Network Aggregation
Switch
Server Farm Firewall
Extranet Firewall
Internet Firewall
Application Load
Balancer
Bandwidth Manager
Content Filter
WAN Router
Extranet Router
Internet Router
iSCSI WAN Router
Extranet Switch
SAN Director Switch
Disaster Recovery
Site, Rajshahi
Country
of Origin
Code
Quantity
BDT
Unit Prices / Rates
Supplied from outside the
Purchaser’s Country
BDT
[ insert:
foreign
currency
A]
[ insert
foreign
currency
B]
[ insert:
foreign
currency
C]
Supplied
Locally
BDT
Total Prices
Supplied from outside the Purchaser’s
Country
BDT
[ insert:
foreign
currency
A]
[ insert:
foreign
currency
B]
[ insert:
foreign
currency
C]
328
Section VII. Sample Forms
Unit Prices / Rates
Supplied from outside the
Purchaser’s Country
Supplied
Locally
Component
No.
Component Description
Country
of Origin
Code
Quantity
BDT
BDT
[ insert:
foreign
currency
A]
Subtotals (to [ insert: line item ] of Installation Cost Summary Table)
Note: - - indicates not applicable.
Name of Bidder:
Authorized Signature of Bidder:
[ insert
foreign
currency
B]
[ insert:
foreign
currency
C]
Supplied
Locally
BDT
Total Prices
Supplied from outside the Purchaser’s
Country
BDT
[ insert:
foreign
currency
A]
[ insert:
foreign
currency
B]
[ insert:
foreign
currency
C]
Section VII. Sample Forms
329
2.8
Training Services Cost Sub Table
System or Subsystem number: Entire System procurement [ as necessary for supply, installation, and achieving Operational
Acceptance of the System, specify items in the Table below, modifying, deleting, or expanding the sample line items and sample table
entries as needed. ]
Costs MUST reflect prices and rates quoted in accordance with ITB Clauses 14 and 15.
Item
No.
Course
1
Number of
Trainee
Duration
BDT
Price
[ insert: Foreign
Currency A] Price
[ insert: Foreign
Currency B] Price
[ insert: Foreign
Currency C] Price
1
2
3
SUBTOTALS
TOTAL (To Grand Summary Table)
Note:
- - indicates not applicable. “ indicates repetition of table entry above. Refer to the relevant Installation Cost Sub-Table for the
specific components that constitute each Subsystem or line item in this summary table
Name of Bidder:
Authorized Signature of Bidder:
330
Section VII. Sample Forms
2.9
Taxes and Duties Cost Table
Cost for each and every item (Component and Sub-component wise) of Hardware, Software and other goods and services proposed
by the Bidder shall be separately made.
Component
No.
1
Total
Quantity
Component
VAT if goods manufactured/ Customs Duty and other Taxes and dues at the port
supplied locally
for goods supplied from abroad
Remarks
Hardware
:
2
Software
:
…
3
:
Training Services
…
Total Taxes and Duties
Note:
- - indicates not applicable. “ indicates repetition of table entry above. Refer to the relevant Installation Cost Sub-Table for the
specific components that constitute each Subsystem or line item in this summary table
Name of Bidder:
Authorized Signature of Bidder:
Section VII. Sample Forms
331
2.10 Country of Origin Code Table
Country of Origin
Country
Code
United States of America
USA
United Kingdom
UK
Japan
JPN
Country of Origin
Country Code
Country of Origin
Country
Code
332
Section VII. Sample Forms
3. OTHER BID FORMS AND LISTS
Section VII. Sample Forms
333
3.1
Manufacturer’s Authorization
Invitation for Bids Title and No.:
[If applicable:] Lot, Slice, Subsystem No(s).:
To: ________________________________
WHEREAS _______________________________________ who are official producers of
_______________________________________________ and having production facilities at
__________________________________________________________ do hereby authorize
__________________________________________________________________ located at
_____________________________________________________ (hereinafter, the “Bidder”)
to submit a bid and subsequently negotiate and sign a Contract with you for resale of the
following Products produced by us:
.
We hereby confirm that, in case the bidding results in a Contract between you and the Bidder,
the above-listed products will come with our full standard warranty.
Name
In the capacity of
Signed
Duly authorized to sign the authorization for and on behalf of : ________________________
Dated on _______________________________ day of ______________________, ______.
Note: This authorization should be written on the letterhead of the Manufacturer and be
signed by a person with the proper authority to sign documents that are binding on the
Manufacturer.
334
Section VII. Sample Forms
3.2
Item
List of Proposed Subcontractors
Proposed Subcontractor
Place of Registration &
Qualifications
Section VII. Sample Forms
335
3.3
Software List
(select one per item)
Software Item
System
Software
GeneralPurpose
Software
Application
Software
(select one per item)
Standard
Software
Custom
Software
336
Section VII. Sample Forms
3.4
List of Custom Materials
Custom Materials
Section VII. Sample Forms
337
3.5.1 General Information Form
All individual firms and each partner of a Joint Venture that are bidding must complete the
information in this form. Nationality information should be provided for all owners or
Bidders that are partnerships or individually owned firms.
Where the Bidder proposes to use named Subcontractors for highly specialized components
of the Information System, the following information should also be supplied for the
Subcontractor(s), together with the information in Forms 3.5.2, 3.5.3, 3.5.3a, 3.5.4, and 3.5.5.
Joint Ventures must also fill out Form 3.5.2a.
1.
Name of firm
2.
Head office address
3.
Telephone
Contact
4.
Fax
Telex
5.
Place of incorporation / registration
Year of incorporation / registration
Nationality of owners¹
Name
Nationality
1.
2.
3.
4.
5.
¹/
To be completed by all owners of partnerships or individually owned firms.
338
Section VII. Sample Forms
3.5.2 General Information Systems Experience Record
Name of Bidder or partner of a Joint Venture
All individual firms and all partners of a Joint Venture must complete the information in this
form with regard to the management of Information Systems contracts generally. The
information supplied should be the annual turnover of the Bidder (or each member of a Joint
Venture), in terms of the amounts billed to clients for each year for work in progress or
completed, converted to U.S. dollars at the rate of exchange at the end of the period reported.
The annual periods should be calendar years, with partial accounting for the year up to the
date of submission of applications. This form may be included for Subcontractors only if the
Bid Data Sheet for ITB Clause 6.1 (a) explicitly permits experience and resources of (certain)
Subcontractors to contribute to the Bidder’s qualifications.
A brief note on each contract should be appended, describing the nature of the Information
System, duration and amount of contract, managerial arrangements, purchaser, and other
relevant details.
Use a separate page for each partner of a Joint Venture, and number these pages.
Bidders should not enclose testimonials, certificates, and publicity material with their
applications; they will not be taken into account in the evaluation of qualifications.
Annual turnover data (applicable activities only)
Year¹
Turnover
US$ equivalent
1.
2.
3.
4.
5.
¹/
Commencing with the partial year up to the date of submission of bids
Section VII. Sample Forms
339
3.5.2a Joint Venture Summary
Names of all partners of a Joint Venture
1. Partner in charge
2. Partner
3. Partner
4. Partner
5. Partner
6. etc.
Total value of annual turnover, in terms of Information System billed to clients, in US$
equivalent, converted at the rate of exchange at the end of the period reported:
Annual turnover data (applicable activities only; US$ equivalent)
Partner
1. Partner
in charge
2. Partner
3. Partner
4. Partner
5. Partner
6. Etc.
Totals
Form
Year 1
3.5.2
page no.
Year 2
Year 3
Year 4
Year 5
340
Section VII. Sample Forms
3.5.3 Particular Information Systems Experience Record
Name of Bidder or partner of a Joint Venture
On separate pages, using the format of Form 3.5.3a, the Bidder is requested to list contracts
of a similar nature, complexity, and requiring similar information technology and
methodologies to the contract or contracts for which these Bidding Documents are issued,
and which the Bidder has undertaken during the period, and of the number, specified in the
BDS for ITB Clause 6.1 (a). Each partner of a Joint Venture should separately provide details
of its own relevant contracts. The contract value should be based on the payment currencies
of the contracts converted into U.S. dollars, at the date of substantial completion, or for
ongoing contracts at the time of award.
Section VII. Sample Forms
341
3.5.3a Details of Contracts of Similar Nature and Complexity
Name of Bidder or partner of a Joint Venture
Use a separate sheet for each contract.
1.
Number of contract
Name of contract
Country
2.
Name of Purchaser
3.
Purchaser address
4.
Nature of Information Systems and special features relevant to the contract for which the
Bidding Documents are issued
5.
Contract role (check one)
Prime Supplier  Management Contractor  Subcontractor  Partner in a Joint Venture
6.
Amount of the total contract/subcontract/partner share (in specified currencies at
completion, or at date of award for current contracts)
Currency
7.
Currency
Currency
Subcontract: $_______;
Partner share: $_______;
Equivalent amount US$
Total contract: $_______;
8.
Date of award/completion
9.
Contract was completed _____ months ahead/behind original schedule (if behind, provide
explanation).
10.
Contract was completed US$ _________ equivalent under/over original contract amount (if
over, provide explanation).
11.
Special contractual/technical requirements.
12.
Indicate the approximate percent of total contract value (and US$ amount) of Information
System undertaken by subcontract, if any, and the nature of such Information System.
342
Section VII. Sample Forms
3.5.4 Summary Sheet: Current Contract Commitments / Work in
Progress
Name of Bidder or partner of a Joint Venture
Bidders and each partner to an Joint Venture bid should provide information on their current
commitments on all contracts that have been awarded, or for which a letter of intent or
acceptance has been received, or for contracts approaching completion, but for which an
unqualified, full completion certificate has yet to be issued.
Name of contract
1.
2.
3.
4.
5.
etc.
Purchaser,
contact
address/tel./fax
Value of
outstanding
Information
System (current
US$ equivalent)
Estimated
completion date
Average monthly
invoicing over last
six months
(US$/month)
Section VII. Sample Forms
343
3.5.5 Financial Capabilities
Name of Bidder or partner of a Joint Venture
Bidders, including each partner of a Joint Venture, shall provide financial information to
demonstrate that they meet the requirements stated in the BDS for ITB Clause 6.1 (a). Each
Bidder or partner of a Joint Venture shall complete this form. If necessary, separate sheets
shall be used to provide complete banker information. A copy of the audited balance sheets
shall be attached.
Autonomous subdivisions of parent conglomerate businesses shall submit financial
information related only to the particular activities of the subdivision.
Banker
Name of banker
Address of banker
Telephone
Contact name and title
Fax
Telex
Summarize actual assets and liabilities in U.S. dollar equivalent (at the rates of exchange
current at the end of each year) for the previous five calendar years. Based upon known
commitments, summarize projected assets and liabilities in U.S. dollar equivalent for the next
two calendar years, unless the withholding of such information by stock market listed public
companies can be substantiated by the Bidder.
Financial
information in
US$ equivalent
Actual:
Projected:
Previous five years
Next two years
5
1. Total assets
2. Current assets
3. Total
liabilities
4. Current
liabilities
5. Profits before
taxes
6. Profits after
taxes
4
3
2
1
1
2
344
Section VII. Sample Forms
Specify proposed sources of financing, such as liquid assets, unencumbered real assets, lines
of credit, and other financial means, net of current commitments, available to meet the total
construction cash flow demands of the subject contract or contracts as indicated in the BDS
for ITB Clause 6.1 (a).
Source of financing
Amount (US$ equivalent)
1.
2.
3.
4.
Attach audited financial statements—including, as a minimum, profit and loss account,
balance sheet, and explanatory notes—for the period stated in the BDS for ITB Clause 6.1 (a)
(for the individual Bidder or each partner of a Joint Venture).
If audits are not required by the laws of Bidders' countries of origin, partnerships and firms
owned by individuals may submit their balance sheets certified by a registered accountant,
and supported by copies of tax returns,
Section VII. Sample Forms
345
3.5.6 Personnel Capabilities
Name of Bidder
For specific positions essential to contract management and implementation (and/or those
specified in the Bidding Documents, if any), Bidders should provide the names of at least two
candidates qualified to meet the specified requirements stated for each position. The data on
their experience should be supplied on separate sheets using one Form 3.5.6a for each
candidate.
Bidders may propose alternative management and implementation arrangements requiring
different key personnel, whose experience records should be provided.
1.
Title of position
Name of prime candidate
Name of alternate candidate
2.
Title of position
Name of prime candidate
Name of alternate candidate
3.
Title of position
Name of prime candidate
Name of alternate candidate
4.
Title of position
Name of prime candidate
Name of alternate candidate
346
Section VII. Sample Forms
3.5.6a Candidate Summary
Name of Bidder
Position
Candidate

Candidate
information
Name of candidate
Prime

Alternate
Date of birth
Professional qualifications
Present
employment
Name of Employer
Address of Employer
Telephone
Contact (manager / personnel officer)
Fax
Telex
Job title of candidate
Years with present Employer
Summarize professional experience over the last twenty years, in reverse chronological order.
Indicate particular technical and managerial experience relevant to the project.
From
To
Company/Project/ Position/Relevant technical and management experience
Section VII. Sample Forms
347
3.5.7 Technical Capabilities
Name of Bidder
The Bidder shall provide adequate information to demonstrate clearly that it has the technical
capability to meet the requirements for the Information System. With this form, the Bidder
should summarize important certifications, proprietary methodologies, and/or specialized
technologies which the Bidder proposes to utilize in the execution of the Contract or
Contracts.
348
Section VII. Sample Forms
3.5.8 Litigation History
Name of Bidder or partner of a Joint Venture
Bidders, including each of the partners of a Joint Venture, shall provide information on any
history of litigation or arbitration resulting from contracts executed in the last five years or
currently under execution. A separate sheet should be used for each partner of a Joint
Venture.
Year
Award FOR Name of client, cause of litigation, and matter in Disputed
amount
or AGAINST dispute
(current value, US$
Bidder
equivalent)
Section VII. Sample Forms
349
4. BID-SECURING DECLARATION
IFB: Supply, Installation, Testing, Commissioning, Implementation and related services of
Network Devices and Software for Information Systems and number of IFB
Number: BB(G)IT-5]
To: [insert: name and address of Purchaser]
We, the undersigned, declare that:
We understand that, according to your conditions, bids must be supported by a Bid-Securing
Declaration.
We accept that we, and in the case of a Joint Venture all partners to it, will automatically be
suspended from being eligible for participating in bidding for any contract with you for the
period of time of [Purchaser insert: number of months or years], in case of, and starting
from the date of, breaching our obligation(s) under the bidding conditions due to:
(a)
withdrawing our bid, or any part of our bid, during the period of bid validity specified
in the Bid Submission Form or any extension of the period of bid validity which we
subsequently agreed to; or
(b)
having been notified of the acceptance of our bid by you during the period of bid
validity, (i) failing or refusing to execute the Contract Agreement, or (ii) failing or
refusing to furnish the performance security, if required, in accordance with the
Instructions to Bidders.
We understand this Bid-Securing Declaration shall expire if we are not the successful Bidder,
upon the earlier of (i) our receipt of your notification to us of the name of the successful
Bidder; or (ii) twenty-eight days after the expiration of the period of bid validity.
If the submission of alternative bids was permitted, and in case we did submit one or more
alternative bids, this Bid-Securing Declaration applies to these parts of our bid as well.
Signed: [insert: signature of person whose name and capacity are shown below]
Name: [insert: name of person signing the Bid-Securing Declaration], in the capacity of
[insert: legal capacity of person signing the Bid-Securing Declaration]
Duly authorized to sign the bid for and on behalf of: [insert: name of Bidder]
Dated on ____________ day of __________________, 20__
[add Corporate Seal (where appropriate)]
[Note to Bidders: Joint Ventures need to ensure that, their Bid-Securing Declaration meets the requirements for
Joint Ventures as stated in the ITB Clause on "Securing the Bid".]
350
Section VII. Sample Forms
4A. BID SECURITY (BANK GUARANTEE)
________________________________
[insert: Bank’s Name, and Address of Issuing Branch or Office]
Beneficiary: [insert: Name and Address of Purchaser]
Date: [insert: date]
BID GUARANTEE No.: [insert: Bid Guarantee Number]
We have been informed that [insert: name of the Bidder] (hereinafter called "the Bidder")
has submitted to you its bid dated [insert: bid date] (hereinafter called "the Bid") for the
execution of [insert: name of contract] under Invitation for Bids No.: BB(G)IT-5.
Furthermore, we understand that, according to your conditions, bids must be supported by a
bid guarantee, and that the bid guarantee automatically covers any alternative bids included in
the Bid, if the Bidder is permitted to offer alternatives and does so.
At the request of the Bidder, we [insert: name of Bank] hereby irrevocably undertake to pay
you any sum or sums not exceeding in total an amount of [insert: amount in figures]
([insert: amount in words]) upon receipt by us of your first demand in writing accompanied
by a written statement stating that the Bidder is in breach of its obligation(s) under the bid
conditions, because the Bidder:
(a)
has withdrawn the Bid (or any parts of it) during the period of bid validity specified
by the Bidder in the Bid Submission Form or any extension of the period of bid
validity which the Bidder subsequently agreed to; or
(b)
having been notified of the acceptance of the Bid by you during the period of bid
validity, (i) failed or refused to execute the Contract Agreement, or (ii) failed or
refused to furnish the performance security, if required, in accordance with the
Instructions to Bidders.
This guarantee will expire: (a) if the Bidder is the successful bidder, upon our receipt of
copies of the contract signed by the Bidder and the performance security issued to you upon
the instruction of the Bidder; or (b) if the Bidder is not the successful bidder, upon the earlier
of (i) our receipt of a copy of your notification to the Bidder of the name of the successful
bidder; or (ii) twenty-eight days after the expiration of the Bid's validity.
Consequently, any demand for payment under this guarantee must be received by us at the
office on or before that date.
This guarantee is subject to the Uniform Rules for Demand Guarantees, ICC Publication No.
458.
_____________________________
[Signature(s)]
[Note to Bidders: Instructions on amount and currency can be found in the ITB Clause and BDS for "Securing
the Bid." Joint Ventures need to also ensure that their Bank Guarantee meets the requirements for Joint
Ventures as provided in the same Clause.]
Section VII. Sample Forms
351
4B. BID SECURITY (BID BOND)
BOND NO.: ______________________
BY THIS BOND, [insert: name of Bidder] as Principal (hereinafter called “the Principal”),
and [insert: name, legal title, and address of surety], authorized to transact business in
[insert: name of Purchaser's country], as Surety (hereinafter called “the Surety”), are held
and firmly bound unto [insert name of Purchaser] as Obligee (hereinafter called “the
Purchaser”) in the sum of [insert amount of Bond in currency, figures and words], for the
payment of which sum, well and truly to be made, we, the said Principal and Surety, bind
ourselves, our successors and assigns, jointly and severally, firmly by these presents.
WHEREAS the Principal has submitted a written bid to the Purchaser dated the ___ day of
______, 20__, for the execution of [insert: name of contract] (hereinafter called "the Bid”).
If the Principal was permitted by the bidding conditions to submit alternative bid(s) and did
so, then these are deemed part of the Bid and thus covered by this Bond.
NOW, THEREFORE, THE CONDITION OF THIS OBLIGATION is such that if the
Principal:
(a)
withdraws the Bid (or any parts of it) during the period of the Bid's validity specified
in the Bid Submission Form, or any extension of the period of the Bid's validity the
Principal subsequently agreed to, notice of which to the Surety is hereby waived; or
(b)
having been notified of the acceptance of the Bid by the Purchaser during the period
of the Bid's validity, (i) fails or refuses to execute the Contract Agreement, or (ii) fails
or refuses to furnish the performance security, if required, in accordance with the
Instructions to Bidders;
then the Surety undertakes to immediately pay to the Purchaser up to the above amount upon
receipt of the Purchaser's first written demand, without the Purchaser having to substantiate
its demand, provided that in its demand the Purchaser shall state that the demand arises from
the occurrence of any of the above events, specifying which event(s) has/have occurred.
The Surety hereby agrees that its obligation will remain in full force and effect up to and
including the date 28 days after the date of expiration of the Bid's validity.
IN TESTIMONY WHEREOF, the Principal and the Surety have caused these presents to be
executed in their respective names this ____ day of ____________ 20__.
Principal: _______________________
Surety: ______________________________
[add Corporate Seal(s) (where appropriate)]
_______________________________
____________________________________
[Signature]
[Signature]
_______________________________
____________________________________
[state: printed name and title]
[state: printed name and title]
[Note to Bidders: Instructions on amount and currency can be found in the ITB Clause and BDS for "Securing
the Bid." Joint Ventures need to also ensure that their Bid Bond meets the requirements for Joint Ventures as
provided in the same Clause.]
352
Section VII. Sample Forms
5. CONTRACT AGREEMENT
THIS CONTRACT AGREEMENT is made
the [ insert: ordinal ] day of [ insert: month ], [ insert: year ].
BETWEEN
(1)
[ insert: Name of Purchaser ], a [ insert: description of type of legal entity,
for example, an agency of the Ministry of . . . ] of the Government of
[ insert: country of Purchaser ], or corporation incorporated under the laws
of [ insert: country of Purchaser ] and having its principal place of business
at [ insert: address of Purchaser ] (hereinafter called “the Purchaser”), and
(2)
[ insert: name of Supplier], a corporation incorporated under the laws of
[ insert: country of Supplier] and having its principal place of business at
[ insert: address of Supplier ] (hereinafter called “the Supplier”).
WHEREAS the Purchaser desires to engage the Supplier to supply, install, achieve
Operational Acceptance of, and support the following Information System [ insert: brief
description of the Information System ] (“the System”), and the Supplier has agreed to such
engagement upon and subject to the terms and conditions appearing below in this Contract
Agreement.
NOW IT IS HEREBY AGREED as follows:
Article 1.
Contract
Documents
1.1
Contract Documents (Reference GCC Clause 1.1 (a) (ii))
The following documents shall constitute the Contract between
the Purchaser and the Supplier, and each shall be read and
construed as an integral part of the Contract:
(a)
This Contract Agreement and the Appendices attached to
the Contract Agreement
(b)
Special Conditions of Contract
(c)
General Conditions of Contract
(d)
Technical Requirements (including Implementation
Schedule)
(e)
The Supplier’s bid and original Price Schedules
(f)
[ Add here: any other documents ]
Section VII. Sample Forms
1.2
353
Order of Precedence (Reference GCC Clause 2)
In the event of any ambiguity or conflict between the Contract
Documents listed above, the order of precedence shall be the
order in which the Contract Documents are listed in Article 1.1
(Contract Documents) above, provided that Appendix 7 shall
prevail over all provisions of the Contract Agreement and the
other Appendices attached to the Contract Agreement and all the
other Contract Documents listed in Article 1.1 above.
1.3
Definitions (Reference GCC Clause 1)
Capitalized words and phrases used in this Contract Agreement
shall have the same meanings as are ascribed to them in the
General Conditions of Contract.
Article 2.
2.1
Contract Price
and Terms of
Payment
Contract Price (Reference GCC Clause 1.1(a)(viii) and GCC
Clause 11)
The Purchaser hereby agrees to pay to the Supplier the Contract
Price in consideration of the performance by the Supplier of its
obligations under the Contract. The Contract Price shall be the
aggregate of: [ insert: amount of foreign currency A in words ],
[insert: amount in figures ], plus [ insert: amount of foreign
currency B in words ], [insert: amount in figures ], plus
[ insert: amount of foreign currency C in words ], [insert:
amount in figures ], [ insert: amount of local currency in
words ], [ insert: amount in figures ], as specified in the Grand
Summary Price Schedule.
The Contract Price shall be understood to reflect the terms and
conditions used in the specification of prices in the detailed price
schedules, including the terms and conditions of the associated
Incoterms, and the taxes, duties and related levies if and as
identified.
Article 3.
Effective Date
for
Determining
Time for
Operational
Acceptance
3.1
Effective Date (Reference GCC Clause 1.1 (e) (ix))
The time allowed for supply, installation, and achieving
Operational Acceptance of the System shall be determined from
the date when all of the following conditions have been fulfilled:
(a)
This Contract Agreement has been duly executed for and
on behalf of the Purchaser and the Supplier;
(b)
The Supplier has submitted to the Purchaser the
performance security and the advance payment security, in
accordance with GCC Clause 13.2 and GCC Clause 13.3;
(c)
The Purchaser has paid the Supplier the advance payment,
354
Section VII. Sample Forms
in accordance with GCC Clause 12;
(d)
[ specify here: any other conditions, for example,
opening/confirmation of letter of credit ].
Each party shall use its best efforts to fulfill the above conditions
for which it is responsible as soon as practicable.
Article 4.
3.2
If the conditions listed under 3.1 are not fulfilled within two (2)
months from the date of this Contract Agreement because of
reasons not attributable to the Supplier, the parties shall discuss
and agree on an equitable adjustment to the Contract Price and
the Time for Achieving Operational Acceptance and/or other
relevant conditions of the Contract.
4.1
The Appendixes listed below shall be deemed to form an integral
part of this Contract Agreement.
4.2
Reference in the Contract to any Appendix shall mean the
Appendixes listed below and attached to this Contract
Agreement, and the Contract shall be read and construed
accordingly.
Appendixes
APPENDIXES
Appendix 1.
Appendix 2.
Appendix 3.
Appendix 4.
Appendix 5.
Appendix 6.
Appendix 7.
Supplier’s Representative
Adjudicator [if there is no Adjudicator, state “not applicable”]
List of Approved Subcontractors
Categories of Software
Custom Materials
Revised Price Schedules (if any)
Minutes of Contract Finalization Discussions and Agreed-to Contract
Amendments
Section VII. Sample Forms
355
IN WITNESS WHEREOF the Purchaser and the Supplier have caused this Agreement to be
duly executed by their duly authorized representatives the day and year first above written.
For and on behalf of the Purchaser
Signed:
in the capacity of [ insert: title or other appropriate designation ]
in the presence of
For and on behalf of the Supplier
Signed:
in the capacity of [ insert: title or other appropriate designation ]
in the presence of
CONTRACT AGREEMENT
dated the [ insert: number ] day of [ insert: month ], [ insert: year ]
BETWEEN
[ insert: name of Purchaser ], “the Purchaser”
and
[ insert: name of Supplier ], “the Supplier”
356
Section VII. Sample Forms
Appendix 1. Supplier’s Representative
In accordance with GCC Clause 1.1 (b) (iv), the Supplier’s Representative is:
Name:
[ insert: name and provide title and address further below, or state “to be
nominated within fourteen (14) days of the Effective Date” ]
Title:
[ if appropriate, insert: title ]
In accordance with GCC Clause 4.3, the Supplier's addresses for notices under the Contract
are:
Address of the Supplier's Representative: [ as appropriate, insert: personal delivery,
postal, cable, telegraph, telex, facsimile, electronic mail, and/or EDI addresses. ]
Fallback address of the Supplier: [ as appropriate, insert: personal delivery, postal,
cable, telegraph, telex, facsimile, electronic mail, and/or EDI addresses. ]
Section VII. Sample Forms
357
Appendix 2. Adjudicator
In accordance with GCC Clause 1.1 (b) (vi), the agreed-upon Adjudicator is:
Name: [ insert: name ]
Title: [ insert: title ]
Address: [ insert: postal address ]
Telephone: [ insert: telephone ]
In accordance with GCC Clause 6.1.3, the agreed-upon fees and reimbursable expenses are:
Hourly Fees: [ insert: hourly fees ]
Reimbursable Expenses: [ list: reimbursables ]
Pursuant to GCC Clause 6.1.4, if at the time of Contract signing, agreement has not been
reached between the Purchaser and the Supplier, an Adjudicator will be appointed by the
Appointing Authority named in the SCC.
358
Section VII. Sample Forms
Appendix 3. List of Approved Subcontractors
The Purchaser has approved use of the following Subcontractors nominated by the Supplier
for carrying out the item or component of the System indicated. Where more than one
Subcontractor is listed, the Supplier is free to choose between them, but it must notify the
Purchaser of its choice sufficiently in advance of the time when the subcontracted work needs
to commence to give the Purchaser reasonable time for review. In accordance with GCC
Clause 20.1, the Supplier is free to submit proposals for Subcontractors for additional items
from time to time. No subcontracts shall be placed with any such Subcontractors for
additional items until the Subcontractors have been approved in writing by the Purchaser and
their names have been added to this list of Approved Subcontractors, subject to GCC
Clause 20.3.
[ specify: item, approved Subcontractors, and their place of registration that the Supplier
proposed in the corresponding attachment to its bid and that the Purchaser approves that
the Supplier engage during the performance of the Contract. Add additional pages as
necessary. ]
Item
Approved Subcontractors
Place of Registration
Section VII. Sample Forms
359
Appendix 4. Categories of Software
The following table assigns each item of Software supplied and installed under the Contract
to one of the three categories: (i) System Software, (ii) General-Purpose Software, or
(iii) Application Software; and to one of the two categories: (i) Standard Software or
(ii) Custom Software.
(select one per item)
Software Item
System
Software
GeneralPurpose
Software
Application
Software
(select one per item)
Standard
Software
Custom
Software
360
Section VII. Sample Forms
Appendix 5. Custom Materials
The follow table specifies the Custom Materials the Supplier will provide under the Contract.
Custom Materials
Section VII. Sample Forms
361
Appendix 6. Revised Price Schedules
The attached Revised Price Schedules (if any) shall form part of this Contract Agreement
and, where differences exist, shall supersede the Price Schedules contained in the Supplier’s
Bid. These Revised Price Schedules reflect any corrections or adjustments to the Supplier’s
bid price, pursuant to the ITB Clauses 18.3, 26.2, and 33.1 (ITB Clauses 30.3, 38.2, and 45.1
in the two-stage SBD).
362
Section VII. Sample Forms
Appendix 7. Minutes of Contract Finalization Discussions and Agreed-to
Contract Amendments
The attached Contract amendments (if any) shall form part of this Contract Agreement and,
where differences exist, shall supersede the relevant clauses in the GCC, SCC, Technical
Requirements, or other parts of this Contract as defined in GCC Clause 1.1 (a) (ii).
Section VII. Sample Forms
6. PERFORMANCE AND ADVANCE PAYMENT SECURITY FORMS
363
364
Section VII. Sample Forms
6.1
Performance Security Form (Bank Guarantee)
________________________________
[insert: Bank’s Name, and Address of Issuing Branch or Office]
Beneficiary: [insert: Name and Address of Purchaser]
Date: [insert: date]
PERFORMANCE GUARANTEE No.: [insert: Performance Guarantee Number]
We have been informed that on [insert: date of award] you awarded Contract No. [insert:
Contract number] for [insert: title and/or brief description of the Contract] (hereinafter
called "the Contract") to [insert: complete name of Supplier] (hereinafter called "the
Supplier"). Furthermore, we understand that, according to the conditions of the Contract, a
performance guarantee is required.
At the request of the Supplier, we hereby irrevocably undertake to pay you any sum(s) not
exceeding [insert: amount(s)1 in figures and words] upon receipt by us of your first demand
in writing declaring the Supplier to be in default under the Contract, without cavil or
argument, or your needing to prove or to show grounds or reasons for your demand or the
sum specified therein.
On the date of your issuing, to the Supplier, the Operational Acceptance Certificate for the
System, the value of this guarantee will be reduced to any sum(s) not exceeding [insert:
amount(s)1 in figures and words]. This remaining guarantee shall expire no later than
[insert: number and select: of months/of years (of the warranty Period that needs to be
covered by the remaining guarantee)] from the date of the Operational Acceptance
Certificate for the System,2 and any demand for payment under it must be received by us at
this office on or before that date.
This guarantee is subject to the Uniform Rules for Demand Guarantees, ICC Publication No.
458, except that subparagraph (ii) of Sub-article 20 (a) is hereby excluded.
_______________________
[Signature(s)]
1
The bank shall insert the amount(s) specified and denominated in the SCC for GCC Clauses
13.3.1 and 13.3.4 respectively, either in the currency(ies) of the Contract or a freely convertible
currency acceptable to the Purchaser.
2
In this sample form, the formulation of this paragraph reflects the usual SCC provisions for GCC
Clause 13.3. However, if the SCC for GCC Clauses 13.3.1 and 13.3.4 varies from the usual
provisions, the paragraph, and possibly the previous paragraph, need to be adjusted to precisely
reflect the provisions specified in the SCC.
Section VII. Sample Forms
6.2
365
Advance Payment Security Form (Bank Guarantee)
________________________________
[insert: Bank’s Name, and Address of Issuing Branch or Office]
Beneficiary: [insert: Name and Address of Purchaser]
Date: [insert: date]
ADVANCE PAYMENT GUARANTEE No.: [insert: Advance Payment Guarantee
Number]
We have been informed that on [insert: date of award] you awarded Contract No. [insert:
Contract number] for [insert: title and/or brief description of the Contract] (hereinafter
called "the Contract") to [insert: complete name of Supplier] (hereinafter called "the
Supplier"). Furthermore, we understand that, according to the conditions of the Contract, an
advance payment in the sum of [insert: amount in numbers and words, for each currency of
the advance payment] is to be made to the Supplier against an advance payment guarantee.
At the request of the Supplier, we hereby irrevocably undertake to pay you any sum or sums
not exceeding in total the amount of the advance payment referred to above, upon receipt by
us of your first demand in writing declaring that the Supplier is in breach of its obligations
under the Contract because the Supplier used the advance payment for purposes other than
toward the proper execution of the Contract.
It is a condition for any claim and payment to be made under this guarantee that the advance
payment referred to above must have been received by the Supplier on its account [insert:
number and domicile of the account].
For each payment after the advance payment, which you will make to the Supplier under this
Contract, the maximum amount of this guarantee shall be reduced by the ninth part of such
payment.1 At the time at which the amount guaranteed becomes nil, this guarantee shall
become null and void, whether the original is returned to us or not.
This guarantee is subject to the Uniform Rules for Demand Guarantees, ICC Publication No.
458.
______________________
[Signature(s)]
1
This sample formulation assumes an Advance Payment of 10% of the Contract Price excluding
Recurrent Costs, and implementation of the main option proposed by this SBD in the SCC for
GCC Clause 13.2.2 for gradually reducing the value of the Advance Payment Security. If the
Advance Payment is other than 10%, or if the reduction in amount of the security follows a
different approach, this paragraph would need to be adjusted and edited accordingly.
366
Section VII. Sample Forms
7. INSTALLATION AND ACCEPTANCE CERTIFICATES
Section VII. Sample Forms
367
7.1
Installation Certificate
Date:
Credit Number: 56640
IFB Title: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems.
IFB Number: BB(G)IT-5
Contract: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems.
To: [ insert: name and address of Supplier ]
Dear Sir or Madam:
Pursuant to GCC Clause 26 (Installation of the System) of the Contract entered into
between yourselves and the [ insert: name of Purchaser ] (hereinafter the “Purchaser”) dated
[ insert: date of Contract ], relating to the [ insert: brief description of the Information
System ], we hereby notify you that the System (or a Subsystem or major component thereof)
was deemed to have been correctly installed on the date specified below.
1.
Description of the System (or relevant Subsystem or major component: [ insert:
description ]
2.
Date of Installation: [ insert: date ]
Notwithstanding the above, you are required to complete the outstanding items listed
in the attachment to this certificate as soon as practicable. This letter shall not relieve you of
your obligation to achieve Operational Acceptance of the System in accordance with the
Contract nor of your obligations during the warranty Period.
For and on behalf of the Purchaser
Signed:
Date:
in the capacity of: [ state: “Project Manager” or state the title of a higher level authority in
the Purchaser’s organization ]
368
Section VII. Sample Forms
7.2
Operational Acceptance Certificate
Date:
Credit Number: 56640
IFB Title: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems.
IFB Number: BB(G)IT-5
Contract: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems.
To: [ insert: name and address of Supplier ]
Dear Sir or Madam:
Pursuant to GCC Clause 27 (Commissioning and Operational Acceptance) of the
Contract entered into between yourselves and the [ insert: name of Purchaser ] (hereinafter
the “Purchaser”) dated [ insert: date of Contract ], relating to the [ insert: brief description
of the Information System ], we hereby notify you the System (or the Subsystem or major
component identified below) successfully completed the Operational Acceptance Tests
specified in the Contract. In accordance with the terms of the Contract, the Purchaser hereby
takes over the System (or the Subsystem or major component identified below), together with
the responsibility for care and custody and the risk of loss thereof on the date mentioned
below.
1.
Description of the System (or Subsystem or major component): [ insert: description ]
2.
Date of Operational Acceptance: [ insert: date ]
This letter shall not relieve you of your remaining performance obligations under the
Contract nor of your obligations during the warranty Period.
For and on behalf of the Purchaser
Signed:
Date:
in the capacity of: [ state: “Project Manager” or higher level authority in the Purchaser’s
organization ]
Section VII. Sample Forms
369
8. CHANGE ORDER PROCEDURES AND FORMS
Date:
Credit Number: 56640
IFB Title: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems.
IFB Number: BB(G)IT-5
Contract: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems.
General
This section provides samples of procedures and forms for carrying out changes to the
System during the performance of the Contract in accordance with GCC Clause 39
(Changes to the System) of the Contract.
Change Order Log
The Supplier shall keep an up-to-date Change Order Log to show the current status of
Requests for Change and Change Orders authorized or pending. Changes shall be
entered regularly in the Change Order Log to ensure that the log is kept up-to-date. The
Supplier shall attach a copy of the current Change Order Log in the monthly progress
report to be submitted to the Purchaser.
References to Changes
(1)
(2)
(3)
(4)
(5)
Request for Change Proposals (including Application for Change Proposals) shall
be serially numbered CR-nnn.
Change Estimate Proposals shall be numbered CN-nnn.
Estimate Acceptances shall be numbered CA-nnn.
Change Proposals shall be numbered CP-nnn.
Change Orders shall be numbered CO-nnn.
On all forms, the numbering shall be determined by the original CR-nnn.
Annexes
8.1
8.2
8.3
8.4
8.5
8.6
Request for Change Proposal Form
Change Estimate Proposal Form
Estimate Acceptance Form
Change Proposal Form
Change Order Form
Application for Change Proposal Form
370
Section VII. Sample Forms
8.1
Request for Change Proposal Form
(Purchaser’s Letterhead)
Date:
Credit Number: 56640
IFB Title: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems.
IFB Number: BB(G)IT-5
Contract: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems.
To: [ insert: name of Supplier and address ]
Attention: [ insert: name and title ]
Dear Sir or Madam:
With reference to the above-referenced Contract, you are requested to prepare and
submit a Change Proposal for the Change noted below in accordance with the following
instructions within [ insert: number ] days of the date of this letter.
1.
Title of Change: [ insert: title ]
2.
Request for Change No./Rev.: [ insert: number ]
3.
Originator of Change: [ select Purchaser / Supplier (by Application for Change
Proposal), and add: name of originator ]
4.
Brief Description of Change: [ insert: description ]
5.
System (or Subsystem or major component affected by requested Change): [ insert:
description ]
6.
Technical documents and/or drawings for the request of Change:
Document or Drawing No.
7.
Description
Detailed conditions or special requirements of the requested Change: [ insert:
description ]
Section VII. Sample Forms
8.
9.
371
Procedures to be followed:
(a)
Your Change Proposal will have to show what effect the requested Change will
have on the Contract Price.
(b)
Your Change Proposal shall explain the time it will take to complete the requested
Change and the impact, if any, it will have on the date when Operational
Acceptance of the entire System agreed in the Contract.
(c)
If you believe implementation of the requested Change will have a negative
impact on the quality, operability, or integrity of the System, please provide a
detailed explanation, including other approaches that might achieve the same
impact as the requested Change.
(d)
You should also indicate what impact the Change will have on the number and
mix of staff needed by the Supplier to perform the Contract.
(e)
You shall not proceed with the execution of work related to the requested Change
until we have accepted and confirmed the impact it will have on the Contract
Price and the Implementation Schedule in writing.
As next step, please respond using the Change Estimate Proposal form, indicating how
much it will cost you to prepare a concrete Change Proposal that will describe the
proposed approach for implementing the Change, all its elements, and will also address
the points in paragraph 8 above pursuant to GCC Clause 39.2.1. Your Change Estimate
Proposal should contain a first approximation of the proposed approach, and
implications for schedule and cost, of the Change.
For and on behalf of the Purchaser
Signed:
Date:
in the capacity of: [ state: “Project Manager” or higher level authority in the Purchaser’s
organization ]
372
Section VII. Sample Forms
8.2
Change Estimate Proposal Form
(Supplier’s Letterhead)
Date:
Credit Number: 56640
IFB Title: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems.
IFB Number: BB(G)IT-5
Contract: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems.
To: [ insert: name of Purchaser and address ]
Attention: [ insert: name and title ]
Dear Sir or Madam:
With reference to your Request for Change Proposal, we are pleased to notify you of
the approximate cost of preparing the below-referenced Change in accordance with GCC
Clause 39.2.1 of the Contract. We acknowledge that your agreement to the cost of preparing
the Change Proposal, in accordance with GCC Clause 39.2.2, is required before we proceed
to prepare the actual Change Proposal including a detailed estimate of the cost of
implementing the Change itself.
1.
Title of Change: [ insert: title ]
2.
Request for Change No./Rev.: [ insert: number ]
3.
Brief Description of Change (including proposed implementation approach): [ insert:
description ]
4.
Schedule Impact of Change (initial estimate): [ insert: description ]
5.
Initial Cost Estimate for Implementing the Change: [insert: initial cost estimate]
6.
Cost for Preparation of Change Proposal: [ insert: cost in the currencies of the
Contract ], as detailed below in the breakdown of prices, rates, and quantities.
For and on behalf of the Supplier
Signed:
Date:
in the capacity of: [ state: “Supplier’s Representative” or other higher level authority in the
Supplier’s organization ]
Section VII. Sample Forms
373
8.3
Estimate Acceptance Form
(Purchaser’s Letterhead)
Date:
Credit Number: 56640
IFB Title: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems.
IFB Number: BB(G)IT-5]
Contract: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems.
To: [ insert: name of Supplier and address ]
Attention: [ insert: name and title ]
Dear Sir or Madam:
We hereby accept your Change Estimate and agree that you should proceed with the
preparation of a formal Change Proposal.
1.
Title of Change: [ insert: title ]
2.
Request for Change No./Rev.: [ insert: request number / revision ]
3.
Change Estimate Proposal No./Rev.: [ insert: proposal number / revision ]
4.
Estimate Acceptance No./Rev.: [ insert: estimate number / revision ]
5.
Brief Description of Change: [ insert: description ]
6.
Other Terms and Conditions:
In the event that we decide not to order the Change referenced above, you shall be
entitled to compensation for the cost of preparing the Change Proposal up to the amount
estimated for this purpose in the Change Estimate Proposal, in accordance with GCC
Clause 39 of the General Conditions of Contract.
For and on behalf of the Purchaser
Signed:
Date:
in the capacity of: [ state: “Project Manager” or higher level authority in the Purchaser’s
organization ]
374
Section VII. Sample Forms
8.4
Change Proposal Form
(Supplier’s Letterhead)
Date: [ insert: date ]
Credit Number: 56640
IFB: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems
and IFB Number: BB(G)IT-5]
Contract: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems
To: [ insert: name of Purchaser and address ]
Attention: [ insert: name and title ]
Dear Sir or Madam:
In response to your Request for Change Proposal No. [ insert: number ], we hereby
submit our proposal as follows:
1.
Title of Change: [ insert: name ]
2.
Change Proposal No./Rev.: [ insert: proposal number/revision ]
3.
Originator of Change: [ select: Purchaser / Supplier; and add: name]
4.
Brief Description of Change: [ insert: description ]
5.
Reasons for Change: [ insert: reason ]
6.
The System Subsystem, major component, or equipment that will be affected by the
requested Change: [ insert: description ]
7.
Technical documents and/or drawings for the requested Change:
Document or Drawing No.
8.
Description
Estimate of the increase/decrease to the Contract Price resulting from the proposed
Change: [ insert: amount in currencies of Contract ], as detailed below in the
breakdown of prices, rates, and quantities.
Total lump sum cost of the Change:
Cost to prepare this Change Proposal (i.e., the amount payable if the Change is not
accepted, limited as provided by GCC Clause 39.2.6):
Section VII. Sample Forms
9.
375
Additional Time for Achieving Operational Acceptance required due to the Change:
[ insert: amount in days / weeks ]
10. Effect on the Functional Guarantees: [ insert: description ]
11. Effect on the other terms and conditions of the Contract: [ insert: description ]
12. Validity of this Proposal: for a period of [ insert: number ] days after receipt of this
Proposal by the Purchaser
13. Procedures to be followed:
(a)
You are requested to notify us of your acceptance, comments, or rejection of this
detailed Change Proposal within [ insert: number ] days from your receipt of this
Proposal.
(b)
The amount of any increase and/or decrease shall be taken into account in the
adjustment of the Contract Price.
For and on behalf of the Supplier
Signed:
Date:
in the capacity of: [ state: “Supplier’s Representative” or other higher level authority in the
Supplier’s organization ]
376
Section VII. Sample Forms
8.5
Change Order Form
(Purchaser’s Letterhead)
Date: [ insert: date ]
Credit Number: 56640
IFB: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems
and IFB Number: BB(G)IT-5
Contract: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems
To: [ insert: name of Supplier and address ]
Attention: [ insert: name and title ]
Dear Sir or Madam:
We hereby approve the Change Order for the work specified in Change Proposal No.
[ insert: number ], and agree to adjust the Contract Price, Time for Completion, and/or other
conditions of the Contract in accordance with GCC Clause 39 of the Contract.
1.
Title of Change: [ insert: name ]
2.
Request for Change No./Rev.: [ insert: request number / revision ]
3.
Change Order No./Rev.: [ insert: order number / revision ]
4.
Originator of Change: [ select: Purchaser / Supplier; and add: name ]
5.
Authorized Price for the Change:
Ref. No.: [ insert: number ]
Date: [ insert: date ]
[ insert: amount in foreign currency A ] plus [ insert: amount in foreign currency
B ] plus [ insert: amount in foreign currency C ] plus [ insert: amount in local
currency ]
6.
Adjustment of Time for Achieving Operational Acceptance: [ insert: amount and
description of adjustment ]
Section VII. Sample Forms
7.
377
Other effects, if any: [ state: “none” or insert description ]
For and on behalf of the Purchaser
Signed:
Date:
in the capacity of: [ state: “Project Manager” or higher level authority in the Purchaser’s
organization ]
For and on behalf of the Supplier
Signed:
Date:
in the capacity of: [ state “Supplier’s Representative” or higher level authority in the
Supplier’s organization ]
378
Section VII. Sample Forms
8.6
Application for Change Proposal Form
(Supplier’s Letterhead)
Date: [ insert: date ]
Credit Number: 56640
IFB: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems
and number of IFB Number: BB(G)IT-5
Contract: Supply, Installation, Testing, Commissioning,
Implementation and related services of Network
Devices and Software for Information Systems
To: [ insert: name of Purchaser and address ]
Attention: [ insert: name and title ]
Dear Sir or Madam:
We hereby propose that the below-mentioned work be treated as a Change to the
System.
1.
Title of Change: [ insert: name ]
2.
Application for Change Proposal No./Rev.: [ insert: number / revision] dated: [ insert:
date ]
3.
Brief Description of Change: [ insert: description ]
4.
Reasons for Change: [ insert: description ]
5.
Order of Magnitude Estimation: [ insert: amount in currencies of the Contract ]
6.
Schedule Impact of Change: [ insert: description ]
7.
Effect on Functional Guarantees, if any: [ insert: description ]
8.
Appendix: [ insert: titles (if any); otherwise state “none” ]
For and on behalf of the Supplier
Signed:
Date:
in the capacity of: [ state: “Supplier’s Representative” or higher level authority in the
Supplier’s organization ]
Download PDF
Similar pages