1. shopping
2. auctions

RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Request for Proposal (RFP) Document for
The implementation of
Anti Corruption Bureau Management System (ACBMS)
for
Anti Corruption Bureau, Government of Rajasthan
Reference No.: F4.2(183)/RISL/Tech/2012/2192
Mode of Bid Submission
Online
Dated: 06/07/2012
though
eProcurement/
eTendering
system at http://eproc.rajasthan.gov.in
Tendering Authority/ Purchaser
Managing Director,
RajCOMP Info Services Limited (RISL), First
Floor, Yojana Bhawan, Tilak Marg, C-Scheme,
Jaipur (Rajasthan)
Date & Time of Pre-bid meeting
30/07/2012 at 04:00PM
Last Date & Time of Submission of eBid
27/08/2012 at 05:00PM
Date & Time of Opening of Technical Bid
28/08/2012 at 05:00PM
Cost of Tender Document: Rs. 1000/- Only (Rupees One Thousand Only)
Name of the Bidding Company/ Firm:
Contact Person(Authorised Bid Signatory):
Correspondence Address:
Telephone &
Mobile No.
Fax Nos.:
Website & E-Mail:
RajCOMP Info Services Limited (RISL)
1st Floor, Yojana Bhawan, Tilak Marg, C-Scheme, Jaipur (Rajasthan), India
Phone: 91(141) 2229394, 5103902
Fax: 0141-2228701
Web: http://risl.rajasthan.gov.in, Email: [email protected]
Seal & Signature of the Auth. Sign.
Page 1 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
TABLE OF CONTENTS
CONTENTS
ABBREVIATIONS & DEFINITIONS .............................................................................................................................5
1.
INVITATION FOR BIDS (IFB) AND NOTICE INVITING TENDER
7
2.
BACKGROUND INFORMATION
10
2.1. PROJECT PROFILE .....................................................................................................................................................10
2.1.1. THEMATIC FOCUS/ P ROJECT OBJECTIVES ..............................................................................................................10
2.1.2. NEED AND BENEFITS ..................................................................................................................................................10
2.1.3. BRIEF TECHNICAL SOLUTION REQUIREMENTS .......................................................................................................11
2.1.4. BRIEF SCOPE OF W ORK ............................................................................................................................................11
2.1.5. IMPLEMENTING AND PARTICIPATING AGENCIES (STAKEHOLDERS) ......................................................................12
2.1.6. TARGET GROUP (AUDIENCE/ BENEFICIARIES) ........................................................................................................12
2.1.7. EXPECTED PROJECT O UTCOMES .............................................................................................................................13
2.2. ABOUT ANTI CORRUPTION B UREAU.........................................................................................................................13
2.2.1. GEOGRAPHICAL COVERAGE OF ANTI C ORRUPTION BUREAU ...............................................................................14
2.2.2. KEY FUNCTIONS OF ANTI C ORRUPTION BUREAU ...................................................................................................14
3.
ELIGIBILITY CRITERIA
16
4.
SCOPE OF WORK, DELIVERABLES AND TIMELINES
19
4.1. CONCEPTUAL TECHNICAL DESIGN OF THE ACBMS ..............................................................................................19
4.2. THE W EB APPLICATION..............................................................................................................................................19
4.2.1. PROPOSED DEPLOYMENT ARCHITECTURE .............................................................................................................19
4.2.2. PROPOSED SECURITY ARCHITECTURE ....................................................................................................................20
4.2.3. APPROACH AND METHODOLOGY TO BE FOLLOWED ...............................................................................................20
4.3. SCOPE OF W ORK .......................................................................................................................................................20
4.3.1. W EB BASED APPLICATION SOFTWARE DEVELOPMENT ...........................................................................................21
4.3.2. SUPPLY, INSTALLATION AND COMMISSIONING OF IT AND NON-IT HARDWARE.....................................................25
4.3.3. DATA DIGITIZATION ....................................................................................................................................................26
4.3.4. TRAINING & CAPACITY BUILDING .............................................................................................................................27
4.3.5. SYSTEM I NTEGRATION AND C OMMISSIONING OF THE P ROJECT ( G O LIVE )........................................................28
4.3.6. OPERATION AND MAINTENANCE / FACILITY MAINTENANCE SERVICES (FMS)....................................................29
4.3.6.1.
ACCEPTANCE FOR SUCCESSFULL R OLL OUT ................................................................................................29
4.3.6.2.
DEPLOYMENT OF MANPOWER FOR FACILITY MANAGEMENT SERVICES ......................................................30
4.3.6.3.
SUPPORT SERVICES FOR W EB BASED APPLICATION S/W ............................................................................31
4.3.6.4.
MIS REPORTS: .......................................................................................................................................................32
4.3.7. CHANGE REQUEST MANAGEMENT SERVICES .........................................................................................................32
4.3.8. THIRD PARTY AUDIT (TPA) ......................................................................................................................................33
Seal & Signature of the Auth. Sign.
Page 2 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
4.4. PROJECT DURATION ..................................................................................................................................................34
4.5. ROLES & RESPONSIBILITIES (STAKEHOLDER-W ISE)..............................................................................................34
4.6. PROJECT DELIVERABLES, MILESTONES & TIME SCHEDULE .................................................................................37
5.
INSTRUCTION TO BIDDER (ITB) & BIDDING PROCESS
41
6.
TERMS AND CONDITIONS, OF TENDER & CONTRACT
58
A)General Conditions of the Bid
59
1) Income Tax and VAT Registration and VAT Clearance Certificate
59
2) Contract Documents
59
3) Interpretation
59
4) Language
60
5) Eligible Goods and Related Services
60
6) Notices
60
7) Governing Law
61
8) Scope of Supply
61
9) Delivery & Installation
61
10)
Supplier’s/ Selected Bidder’s Responsibilities
62
11)
Purchaser’s Responsibilities
62
12)
Contract Price
62
13)
Recoveries from Supplier/ Selected Bidder
62
14)
Taxes & Duties
62
15)
Performance Security Deposit (PSD)
63
16)
Copyright
64
17)
Confidential Information
64
18)
Sub-contracting
65
19)
Specifications and Standards
65
20)
Packing and Documents
66
21)
Insurance
67
22)
Transportation
67
23)
Inspection
67
24)
Samples
67
25)
Drawl of Samples
68
26)
Testing charges
68
27)
Rejection
69
28)
Extension in Delivery Period and Liquidated Damages (LD)
69
29)
Authenticity of Equipments
72
30)
Warranty
72
31)
Patent Indemnity
73
Seal & Signature of the Auth. Sign.
Page 3 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.
32)
Limitation of Liability
74
33)
Change in Laws & Regulations
74
34)
Force Majeure
75
35)
Change Orders and Contract Amendments
75
36)
Termination
76
37)
Settlement of Disputes
77
B)Payment Terms and Schedule
78
38)
Terms of Payment
78
C)
Special Conditions of the Bid
81
39)
Service Level Standards/ Requirements/ Agreement
83
40)
Change Requests/ Management
83
D)
Exit Management
85
90
ANNEXURES
7.1. ANNEXURE 1 – FUNCTIONAL REQUIREMENT SPECIFICATIONS ........................................................90
7.2
ANNEXURE 2 –BILL OF MATERIAL (BOM)................................................................................................... 127
7.3
ANNEXURE-3 – SUGGESTED TECHNICAL SPECIFICATIONS............................................................. 130
7.4
ANNEXURE-4 - COVERING LETTER OF THE BID..................................................................................... 140
7.5
ANNEXURE-5 - PRE- BID QUERIES FORMAT............................................................................................ 142
7.6
ANNEXURE-6 - TENDER FORM...................................................................................................................... 143
7.7
ANNEXURE-7- BIDDER’S AUTHORIZATION CERTIFICATE .................................................................. 144
7.8
ANNEXURE-8 - SELF-DECLARATION – NO BLACKLISTING ................................................................. 145
7.9
ANNEXURE-9 - CERTIFICATE OF CONFORMITY/ NO DEVIATION ..................................................... 146
7.10 ANNEXURE-10 - MANUFACTURER’S AUTHORIZATION FORM (MAF) .............................................. 147
7.11 ANNEXURE-11 - UNDERTAKING ON AUTHENTICITY OF COMPUTER EQUIPMENTS................. 148
7.12 ANNEXURE-12- FORMAT FOR STATEMENT OF DEVIATIONS ............................................................ 149
7.13 ANNEXURE-13 - FINANCIAL BID FORMAT ................................................................................................. 151
7.14 ANNEXURE-14 - PERFORMANCE BANK GUARANTEE .......................................................................... 159
7.15 ANNEXURE-15 - DRAFT AGREEMENT FORMAT...................................................................................... 161
7.16 ANNEXURE-16 - FORMAT FOR SUBMISSION OF PROJECT REFERENCES FOR
ELIGIBILITY CRITERIA ................................................................................................................................................. 164
7.17 ANNEXURE 17- SERVICE LEVEL AGREMENT .......................................................................................... 165
7.18 ANNEXURE-18 - LIST OF INFRASTRUCTURE TO BE PROVIDED BY RSDC.................................... 170
7.19 ANNEXURE-19 - INDICATIVE PROJECT PLAN.......................................................................................... 171
7.20 ANNEXURE-20 - EXPECTED QUALIFICATION OF MANPOWER RESOURCES .............................. 172
7.21 ANNEXURE-21 – LIST OF OFFICES, ACB ................................................................................................... 173
Seal & Signature of the Auth. Sign.
Page 4 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
ABBREVIATIONS & DEFINITIONS
ACBMS
Anti Corruption Bureau Management System
Agreement
The Agreement to be signed between the successful bidder and RajCOMP Info
Services Ltd.
Authorised
Signatory
The bidder’s representative/ officer vested (explicitly, implicitly, or
through conduct) with the powers to commit the authorizing organization
to a binding agreement (also called signing officer/ authority having the
Power of Attorney (PoA) from the competent authority of the respective
Bidding firm).
"Bidder" means any firm/ agency/ company/ contractor/ supplier/
vendor/ service provider/ quoter responding to Invitation for Bids (IFB)
and who is participating in the Bidding process.
“The Contract” means a legally enforceable agreement entered into
between RISL and the selected bidder(s) with mutual obligations.
Bidder
Contract
Contract/ Project
Period
COTS
CP
Day
The “Contract” means a legally enforceable agreement entered into
between RajCOMP Info Services Limited (RISL) and the selected
bidder(s) with mutual obligations.
GoR
Commercial Off-The-Shelf
Capex Payment
“Day” means a calendar day.
Department of Information Technology, Govt. of India
Department of Information Technology and Communications,
Government of Rajasthan.
Anti Corruption Bureau, Govt. of Rajasthan
Earnest Money Deposit.
Government of India.
“Goods” means a tangible physical product that can be contrasted with
a service which is intangible i.e. all the products which the bidder is
required to supply to Purchaser under the Contract.
Government of Rajasthan.
ICT
Information and Communication Technology.
IT/ ITeS
LCBS
LoI
Information Technology/ Information Technology Enabled Services
Least Cost Based Selection Method (L1).
Letter of Intent
NeGP
National e-Governance Plan of Government of India, Department of
Information Technology (DIT), Ministry of Communications and
Information Technology (MCIT), New Delhi.
NIT
OEM
OP
Notice Inviting Tender.
PAN
PBG
Permanent Account Number
Performance Bank Guarantee
PC
Project Site
Procurement Committee (as per RISL procurement manual).
“The Project Site”, wherever applicable, means the designated project
DeITY
DoIT&C
ACB
EMD
GoI
Goods
Original Equipment Manufacturer
Opex Payment
Seal & Signature of the Auth. Sign.
Page 5 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
location or locations as per the details mentioned in bidding document.
Performance Security Deposit (also called as SD)
Submission of the 5% amount of the Total Quoted/ Order Value by the
PSD/ SD
Bidder and is retained till the successful completion of the project (as
long as the bidder fulfils the contractual agreement).
Person or entity that is a recipient of a goods and/ or services provided
Purchaser/
by a seller (bidder) under a purchase order or contract of sale (also
Tendering Authority called buyer), RajCOMP Info Services Limited (RISL) in this bidding/
RFP document.
RFP
Request for Proposal (Bidding document), an early stage in
procurement process, issuing an invitation for suppliers/ vendors/
service provider, through a competitive bidding process, to submit a
proposal (bid) on a specific commodity or service.
RISL
RajCOMP Info Services Ltd.
RSDC
Services
SLA
SoW
State Government
TPA
UAT
VAT
WO/PO
Rajasthan State Data Centre at IT Building, Tilak Marg, C-Scheme,
Jaipur, Rajasthan
“Services” means the services to be delivered by the selected bidder
and as required to run the project successfully as per the Contract. A
service is the intangible equivalent of an economic good.
Service Level Agreement is a negotiated agreement between two
parties wherein one is RISL and the other is the selected bidder (service
provider). It is a service contract where the level and quality of service
required is formally defined. In practice, the term SLA is sometimes
used to refer to the contracted delivery time (of the service) or
performance.
Scope of Work
Government of Rajasthan (GoR).
Third Party Audit
User Acceptance Testing
Value Added Tax
Work Order/ Purchase Order
Seal & Signature of the Auth. Sign.
Page 6 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
1.
INVITATION FOR BIDS (IFB) AND NOTICE INVITING TENDER
1) RajCOMP Info Services Ltd. (RISL), on behalf of Anti Corruption Bureau (ACB), Govt. of
Rajasthan (GoR), invites electronic bid proposal (eBid) from competent and professional
Information Technology (IT) Firms, who meet the minimum eligibility criteria as specified in
this bidding document, for the design, development, implementation of Anti Corruption
Bureau Management System (ACBMS), as detailed in the section titled “Scope of Work” of
this RFP document.
2) The ACBMS will be based upon open standards & state-of-art technologies designed in 3tier architecture with the flexibility to expand/ upgrade and integrate with other existing/
proposed NeGP/ GoR projects as per the requirements of ACB, GoR.
3) The
complete
bidding
document
has
been
published
on
the
websites
http://eproc.rajasthan.gov.in, http://risl.rajasthan.gov.in, and http://www.acb.rajasthan.gov.in
for the purpose of downloading. The downloaded bidding document shall be considered
valid for participation in the electronic bidding process (eProcurement/ eTendering) subject
to the submission of required tender/ bidding document fee and RISL Processing Fee in
Cash/ Demand Draft and in favour of “Managing Director, RajCOMP Info Services Limited
(RISL)” payable at “Jaipur”. A copy of the tender/ bidding document fee receipt and RISL
Processing Fee must be enclosed along with the Technical bid/ proposal failing which the
bid will be summarily rejected.
4) Bidders
who
wish
to
participate
in
this
bidding
process
must
register
on
http://eproc.rajasthan.gov.in (bidders already registered on http://eproc.rajasthan.gov.in
before 30-09-2011 must register again).
5) To participate in online bidding process, Bidders must procure a Digital Signature Certificate
(Type III) as per Information Technology Act-2000 using which they can digitally sign their
electronic bids. Bidders can procure the same from any CCA approved certifying agency,
i.e. TCS, safecrypt, Ncode etc. Bidders who already have a valid Digital Signature
Certificate (DSC) need not procure a new DSC.
6) A “single stage-two envelope” selection procedure shall be adopted.
7) Bidder (authorised signatory) shall submit their offer on-line in Electronic formats both for
technical and financial proposal. However, Demand Draft (DD) for Tender document fees,
RISL Processing Fees and EMD should be submitted physicaly at the office of Tendering
Authority as prescribed in NIT and scanned copy of same should also be uploaded along
with the technical bid/ cover.
8) RISL will not be responsible for delay in online submission due to any reason. For this,
bidders are requested to upload the complete bid well advance in time so as to avoid 11th
Seal & Signature of the Auth. Sign.
Page 7 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
hour issues like slow speed; choking of web site due to heavy load or any other unforeseen
problems.
9) Bidders are also advised to refer “Bidders Manual Kit” available at eProc website for further
details about the e-tendering process.
10) Training for the bidders on the usage of e-Tendering System (eProcurement) is also being
arranged by RISL on regular basis. Bidders interested for training may contact eProcurement Cell, RISL for booking the training slot.
Contact No: 0141-4022688 (Help desk 10 am to 6 pm on all working days)
e-mail: [email protected]
Address : e-Procurement Cell, RISL, Yojana Bhawan, Tilak Marg, C-Scheme, Jaipur
11) Please note that a Pre-Bid meeting of the prospective bidders, who have purchased the
tender/ bidding document, is scheduled as per the details specified in Notice Inviting Tender
(NIT) below. The objective of this meeting is to address the queries of the prospective
bidders related to the Project/Bidding document.
12) No contractual obligation whatsoever shall arise from the RFP/ bidding process unless and
until a formal contract is signed and executed between the tendering authority and the
successful bidder(s).
13) RISL disclaims any factual/ or any other errors in this document (the onus is purely on the
individual bidders to verify such information) and the information provided herein are
intended only to help the bidders to prepare a logical bid-proposal.
Seal & Signature of the Auth. Sign.
Page 8 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
NOTICE INVITING TENDER-NIT
Reference No: F4.2(183)/RISL/Tech/2012/2192
Dated: 06/07/2012
RajCOMP Info Services Limited (RISL), on behalf of Anti Corruption Bureau (ACB), Govt. of
Rajasthan (GoR), invites Technical & Financial eBids/ proposals from the eligible Information
Technology (IT) firms for the selection of a System Integrator (SI)/ Service Provider for the
implementation of Anti Corruption Bureau Management System (ACBMS) project for ACB,
GoR. The proposals shall only be submitted through eTendering system at
www.eproc.rajasthan.gov.in .The bidding schedule is as follows:
Nature of the Project
Cost of Tender Document
(non-refundable)
RISL Processing Fee (non-refundable)
Estimated Project Cost
Earnest Money Deposit (EMD)
Publishing Date/ Time
RFP Download Start Date/ Time
Date, Time& Venue of Pre-Bid Meeting
Bid submission Start Date/ Time
RFP Download End Date/ Time
Bid submission End Date/ Time
Submission of Banker’s Cheque/ Demand
Draft for Tender Fee, EMD, and Processing
Fee
Technical Bid Opening Date/ Time
Selection of a System Integrator/ Service Provider for
the implementation of Anti Corruption Bureau
Management System (ACBMS) Project for Anti
Corruption Bureau, Govt. of Rajasthan.
Rs. 1000/- (Rupees One Thousand Only)
Rs. 1000/- (Rupees One Thousand Only)
Rs. 3 Crores (Rupees Three Crores Only)
Rs. 6 Lacs (Rupees Six Lacs Only)
20/07/2012 at 05:00PM
20/07/2012 at 05:00PM onwards
30/07/2012 at 04:00PM
Board Room,
RajCOMP Info Services Limited (RISL),
First Floor, Yojana Bhawan,
Tilak Marg, C-Scheme,
Jaipur (Rajasthan)
06/08/2012 at 05:00PM onwards
27/08/2012 at 04:00PM
27/08/2012 at 05:00PM
From 05:00PM onwards on 27/08/2012 and up to
02:00PM on 28/08/2012
28/08/2012 at 05:00PM
Will be intimated later to the Technically qualified
Financial Bid Opening Date/ Time
bidders
http://eproc.rajasthan.gov.in
Websites
for
downloading
Tender
http://risl.rajasthan.gov.in
Document, Corrigendum’s, Addendums etc.
http://www.acb.rajasthan.gov.in /
Bid Validity
120 Days from the date of bid submission
* In case, any of the bidders fails to physically submit the Banker’s Cheque/ Demand Draft for Tender
Fee, RISL Processing Fee and EMD up to 02:00PM on 28/08/2012, the Bid of the bidder shall not be
accepted. The Banker’s Cheque/ Demand Draft should be drawn in favour of “Managing Director,
RajCOMP Info Services Limited” payable at “Jaipur” from any Scheduled Commercial Bank.
Date:06/07/2012
Seal & Signature of the Auth. Sign.
Managing Director
RajCOMP Info Services Limited (RISL)
Jaipur (Rajasthan)
Page 9 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
2. BACKGROUND INFORMATION
2.1. Project Profile
2.1.1. Thematic Focus/ Project Objectives
The key objectives that the Anti Corruption Bureau (ACB) intends to achieve through the
implementation of Anti Corruption Bureau Management System (ACBMS) is to put in place
a web based management and monitoring mechanism for improving the ease of accessing
the information about different cases and tracking status of various case and also to provide
an online interface to the citizens for registering a complaint. The Bureau identifies
computerization and automation of processes under the ACBMS project for achieving the
goal. The Bureau has taken a four pronged approach:
a) Citizen Centric Service Delivery
b) IT Infrastructure Creation
c) Back end computerization
d) Human Resource Development
2.1.2. Need and benefits
Strategic objective of the project is to improve the efficiency of the Bureau operations and
pass on the benefits of an efficient and well managed operating system to all
stakeholders. The broad objectives include:
a) Transparency and Accountability:
Building trust between Government and citizen is
fundamental to good governance. In order to achieve this e-governance is increasingly
becoming a tool to address issues of accountability, transparency, and efficiency.
Greater people participation should be encouraged in planning process, promoting open
and accountable government processes etc.
b) Improved decision making: The e- governance project would help bureau to create,
generate and own integrated databases relating to vigilance complaint, tracking of
existing cases, employees vigilance verifications, cases /complaints filed and court
cases etc. Access to such data repository would facilitate the Officials in making better
decisions and planning for their work would be improved. This decision making would be
more representative of the people’s needs as their needs and grievances would be
tracked and monitored while planning.
c) Internal process movement: In order to strengthen the bureau it is important that their
internal process is optimized. While the trust on improving quality of services &
effectiveness of information decimation is rightly placed, it is equally important to focus
on improving internal functioning of bureau it will be difficult to achieve any substantial
Seal & Signature of the Auth. Sign.
Page 10 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
improvements vis-à-vis service delivery and information dissemination without building
internal capacity. ICT would also strengthen linkages between the various departments
ensuring seamless information sharing.
d) Improved service delivery to citizens: The vision consists of making all the government
services accessible to the common man in his locality, through common service delivery
outlets. This ensures efficiency, transparency and reliability of such services through
bilingual portal. It will eliminate the communication barrier between the bureau and the
citizen. The services/information should be delivered to the citizens in a timely and cost
effective manner. Massive amount of time and money is spent in commuting between
different offices to obtain information and to avail the required services. Keeping such
challenges in mind, this project aims to offer not only the mandated services but also
those that are highly demanded by citizens.
2.1.3. Brief Technical Solution Requirements
a) The bidder is responsible to provide the best of class technical solutions as per the
requirements in the Scope of Work provided in Chapter 4 of the RFP document.
b) The web based application software is conceptualised as a centralized web based
application to be accessed by all the users (Bureu Users, Citizen, and registred users of
Government department/Board ) across the state.
c) The application s/w development work shall comply with the respective guidelines
issued by DoIT&C, Government of Rajasthan and Department of Electronics and
Information Technology (DeitY), Government of India (GoI). For detailed technical
solution requirements, bidders may refer to subsequent chapters/ sections of this
bidding document.
2.1.4. Brief Scope of Work
a) The scope involves study, design, development, integration, testing and implementation
of ACBMS application software for ACB, GoR. The Functional Requirements
Specifications (FRS) included in this document at Annexure-11 to be considered as an
integral part of the scope of work and the bidder should take it into account for effort
estimation and financials.
b) Site Preparation and installation and commissioning of IT and non-IT hardware at, Head
Quarter (HQ) of ACB at Jaipur, 8 Range Offices and 35 Outpost offices across
Rajasthan. List of range office and 35 outposts is attached as per annexure 21.
c) Supply, install, configure, operate and maintain all the genuine licensed software with
requisite user licenses (as applicable), media and manuals required at various project
locations along with OEM support, updates, patches, and errata for the period of 3 years
and as per the bill of material/ technical specifications specified in this bid document.
Seal & Signature of the Auth. Sign.
Page 11 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
d) Data digitisation and migration of legacy data (available in electronic form) into the
proposed database.
e) The bidder shall be responsible to provide necessary IT skills training, sensitization
training covering basics of eGovernance, Project Management etc. and handholding
training to ACB staff.
f) After successful commissioning of the project, providing 3 year of Facility Management
& Operations Maintenance (O&M) services as per the agreed SLA.
g) The ACB expects the successful bidder to provide quality & timely services. All the
activities performed during different phases of the project shall be closely monitored by
RISL/ ACB/ GoR.
h) For detailed SoW, bidders may refer to subsequent chapters/ sections of this bidding
document and specially section 4 Scope of work deliverable and timelines.
2.1.5. Implementing and Participating Agencies (Stakeholders)
a) Anti Corruption Bureau, GoR
b) RajCOMP Info Services Ltd. (RISL)
c) Department of Information Technology & Communications (DoIT&C), GoR
2.1.6. Target group (Audience/ Beneficiaries)
a) ACB internal Users
o Registered complaint
o Process a complaint
o Pre enquiry
o Regular enquiry
o Legal prosecution and proceeding
o Generation of various type of MIS reports
o Case tracking
o Follow up with other complainant departments, board and other organisation
o Forward case to enforcement agencies for legal and technical opinion
b) Users of other departments for
Uploading documents related to a complaint.
Providing response to clarifications initiated by ACB.
To view and download final findings related to a complaint/case as authorized by
ACB.
o Track status of submitted complaints/cases as authorized by ACB.
c) External public users for
o
o
o
o
o
o
o
Registering a complaint
Uploading documents related to a complaint.
To view and download final findings related to a complaint/case as authorized
by ACB.
To track status of submitted complaints.
Seal & Signature of the Auth. Sign.
Page 12 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
2.1.7. Expected Project Outcomes
The expected outcomes to be achieved from the project are as follows:
o Creation of an automated Management Information System
o Improvement in the quality of service and information to all the stakeholders
o Centralized storage of data for gathering information on real time basis
o Ease of administration and reduction in manual work
2.2. About Anti Corruption Bureau
In order to investigate the offences under the Prevention of Corruption Act and to enquire
into the complaints relating to corruption against government servants, a separate "AntiCorruption Cell" was created in the year 1949 in the Rajasthan Police under a
Superintendent of Police, as a part of the Crime Branch of the Criminal Investigation
Department (CID). Later in the year 1957, a separate Anti-Corruption Branch of the
Rajasthan Police was established, headed by the Special Inspector General of Police,
under the administrative control of the Department of Home, Government of Rajasthan.
The Anti Corruption Bureau is primarily responsible for the detection, investigation and
prosecution of cases of corruption among public servants and facilitating government
departments to provide an honest, transparent and clean administration. Anti Corruption
Bureau conducts enquiries into complaints of corruption and investigates cases registered
under Prevention of Corruption Act. Anti Corruption Bureau deals with three types of cases
viz. Trap Cases, Disproportionate Assets Cases, and Misuse of Position/Office Cases. The
activities of the Anti Corruption Bureau are carried out through the Head Quarters, Range
office, Out Posts, mails and website. All the activities however are initiated, coordinated and
monitored by the head quarters.
The ACB Head Quarter has three sections - Crime, Complaint & PE and Intelligence
through which detection, investigation and prosecution of cases regarding corruption is
undertaken. Each of the above mentioned sections work independently and performs
specific functions towards solving the case. Apart from the above mentioned sections there
are three special units located at the head quarters - Special Investigating Unit (SIU),
Special Unit (SU) and Special Investigating Wing (SIW). All these units are headed by
Officer In charge of the rank of Addl. SP. All these above mentioned units are designed for
undertaking special jobs such as investigating those cases which have a large canvass to
operate and are of a greater magnitude. The jurisdiction of these special units is entire
Rajasthan.
The territorial jurisdiction of the ACB is throughout the territory of the State of Rajasthan and
is authorized to deal with the following types of cases:
Seal & Signature of the Auth. Sign.
Page 13 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
3.
ELIGIBILITY CRITERIA
S.
No.
1
Basic
Requiremen
t
Legal Entity
2
Turnover
from IT/ITeS
3
Net Worth
4
Technical
Capability
Specific Requirements
Documents Required
The Bidder can be an individual company
or firm. The Bidder should be a company
registered under Indian Companies Act,
1956 or a partnership firm registered
under Indian Partnership Act, 1932 or a
proprietorship firm registered under shop
act and VAT registration.
Annual Turnover of the bidder from IT/
ITeS during each of the last three
financial years (2009-10, 2010-11 and
2011-12)as per the last published audited
balance sheets), should be at least Rs.
30 Crores.
The net worth of the bidder in the last
financial year, i.e. 2011-12, should be
positive.
Copy of the Certificate of
Incorporation
and
registration certificates
CA Certificate with CA’s
Registration
Number/ Seal
CA Certificate with CA’s
Registration
Number/ Seal
The bidder must have successfully · Project reference format
as per Annexure – 16
completed at least One eGovernance
· Work
Completion
project of including services like supply
Certificates from the
and installation of hardware and web
client; OR Work Order +
Self
Certificate
of
based application software development
Completion (Certified by
and O&M to any state/ central
the Statutory Auditor);
government
organization/
PSU’s
OR Work Order + Phase
Completion Certificate
(excluding Banks) only in India not less
from the client
than the amount Rs. 3 Crores during the
last three financial Years (2009-10, 201011 and 2011-12)
OR
The
bidder
must
have
successfully
completed at least One eGovernance
project of including services like web
based application software development
and deployment & O&M to any state/
central government organization/ PSU’s
(excluding Banks) only in India not less
than the amount Rs. 3 Crores during the
last three financial Years (2009-10, 2010Seal & Signature of the Auth. Sign.
Page 16 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
S.
No.
Basic
Requiremen
t
Specific Requirements
Documents Required
11 and 2011-12).
OR
The
bidder
must
have
successfully
completed at least TWO eGovernance
project of including services like supply
and installation of hardware, web based
application software development and
O&M to any state/ central government
organization/ PSU’s (excluding Banks)
only in India not less than the amount Rs.
1.5 Crores during the last three financial
Years (2009-10, 2010-11 and 2011-12)
OR
The
bidder
must
have
successfully
completed at least TWO eGovernance
project of including services like web
based application software development
and deployment & O&M to any state/
central government organization/ PSU’s
(excluding Banks) only in India not less
than the amount Rs. 1.5 Crores during
the last three financial Years (2009-10,
2010-11 and 2011-12)
5
Tax
registration
and
clearance
6
Certifications
The bidder should have a registered
number of
i. VAT/Sales Tax where his business is
located
ii. Service Tax
iii. Income Tax / Pan number.
The bidder should have cleared his VAT
dues to the State Government of
Rajasthan.
The bidder must possess at the time of
bidding, a valid below certifications:
· ISO 9001:2008 (For Quality
Management System) certification
· CMMi
Level
3
(Software
Development & Customization)
certification
Seal & Signature of the Auth. Sign.
Copies of relevant
certificates of
Registration
VAT clearance certificate
from the Commercial Taxes
Officer of the Circle
concerned
Copy of a valid certificate
Page 17 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
S.
No.
7
Basic
Requiremen
t
Blacklisting
8
Manpower
Strength
9
Local
Presence
10
OEM
Authorization
Specific Requirements
Documents Required
The Bidder is not eligible to participate in
this project while under sanction by RISL.
Similarly, at the time of bidding, the firms
black-listed/ debarred in participating in
any procurement activities by any State
or Central Government or UT in India are
not allowed to bid
The bidder must have a minimum
strength of 60 ICT professionals /domain
experts on their permanent rolls.
A Self Certified letter
Undertaking to this effect
shall be submitted by the
bidder on a letter head as
per the format given in
Annexure – 8.
Self Certification by the
authorized signatory with
clear declaration of staff –
year wise, level/designation
wise.
The Bidder should have their own office Declaration as a part of the
located at Jaipur. If the bidder, at the time cover letter as per the
of bidding, does not have a local support format given at Annexure –
office at Jaipur an undertaking on the
4
bidders’ letter head (as a part of the
cover letter at Annexure - 4) that an office
will be opened by the bidder (if selected
for the award of the contract) within 2
months from the date of issue of LoI,
should be submitted by the bidder.
The bidder should have been authorized As per Annexure-10
by
respective
OEM
for
distribution/channel partner/ Retailer of
the equipments covered under the RFP.
The bidder must attach Manufactures
Authorization certificate & Back-to-back
support for all the active items to be
covered through this tender except for
the items which are declared End of
Support from respective OEM.
Note: The bidder/ firm are requested to kindly adhere to the order of documents as mentioned above.
Also, all the required documents should be properly annexed as indicated above along with an Index
Page.
Seal & Signature of the Auth. Sign.
Page 18 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
4. SCOPE OF WORK, DELIVERABLES AND TIMELINES
4.1. Conceptual Technical Design of the ACBMS
4.2. The Web application
ACBMS is conceptualised as a centralized web based application to be accessed by all
the users (Bureau’s User, Citizen and Government Department User) across the state.
Internal users (Bureau User) can access portal and application modules of ACBMS
through an enterprise wide secured interface/portal. However common citizen and
registered users for other department, technical experts and legal experts (not belonging
to ACB) can access portal through internet.
ACBMS application will consist of four modules and shall have 3-Tier architecture
comprising of presentation layer delivery through web based application software, email
and SMS Gateway. Middleware will facilitate communication between user interfaces
and application layer through pre defined business rules of application modules,
document management system, user base dash board, user access rule. Database
layer shall be use to store and retrieval of records.
The web based application software & application s/w shall be designed using Unicode
5.1.0 character encoding standard and available in bilingual i.e. English & Hindi. The
application shall be designed as per the technical standards for Interoperability
framework for E-Governance, DeiTY, GoR.
Application shall have integration with CCTNS and shall have the capability for
integration with UIDAI’s Aadhaar number (as and when available) through external
connectors. All applications shall be secured through a role based user access.
4.2.1.
Proposed Deployment Architecture
The centralized application shall be deployed at RSDC. Application server and database
cluster along with load balancing will be provided by RSDC to maintain high availability,
of application and database. To host application DNS server, authentication server,
syslog log, backup server, Mail Server, SMS server, antivirus server shall be provided
by the RSDC. A different zone for each authentication method will be used web server,
application server and database server.
The GoR has provided connectivity at ACB HQ, through SecLAN. A dedicated 2 Mbps
connectivity has already been provided to ACB HQ.
Seal & Signature of the Auth. Sign.
For connectivity at all Range
Page 19 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
offices and Outpost offices 1 Mbps connectivity through Virtual Private Network (VPN)
on Broadband, a secure networking connectivity will be provided by ACB GoR, Thus, all
intranet users can access application through secured network connection. However, all
public users and business community can connect through internet only.
GoR has also envisaged connecting all range offices (situated at district HQ) and
outpost office (situated at District HQ) with 2 Mbps connectivity under RSWAN. As and
when RSWAN will be operational, these locations will get connected with2 Mbps line.
4.2.2.
Proposed Security Architecture
Security standards shall be eSAFE: eGovernance Security Assurance Framework
Guidelines for Implementation of Security Controls issued by the Department of
Electronics and Information Technology (DeitY), Ministry of Communications & IT
(MCIT), Government of India”. Envisaged security architecture for the ACBMS solution
is as provided below:
a) User Level Security: Restricted areas of the application should only be accessible
through pre-defined user access rights. Since it will comprise critical information
related to crime and security, so biometric based user auhernication shall be done
as second layer of user security. SI should supply relevant SDK (Software
Development Kit) as per the biometric machines.
b) Application Level Security: Role based access, encryption of user credentials and
storing of user credentials for external and internal users in separate repositories.
Audit trail shall be maintained for each session of user.
4.2.3.
Approach and Methodology to be followed
The bidder is expected to adopt any of the following approaches or combination of
following approaches:
a)
Bespoke development of the application OR
b)
Configuration / Customization of an existing application
OR
c)
4.3.
Combination of (a) and (b) above.
Scope of Work
The broad scope of work for the successful bidder during the period of contract/
engagement would include (but not limited to): ·
Web based application software development (for CUG and Public interface)
·
Site Survey and Site Preparation and installation and commissioning of IT and nonIT hardware
·
Data Digitization and Migration
Seal & Signature of the Auth. Sign.
Page 20 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
·
Training and Capacity Building
·
System Integration and Commissioning (Go-Live)
·
Handholding support after Go-Live
·
Operation & Maintenance (O&M)/ Facility Management Services (FMS)
4.3.1. Web based application software development
a) Broad scope of activities to be computerised
i.
The core applications envisaged to be developed and to be rolled out in ACB HQ, 8
Range Offices and 35 Outposts Offices in the State of Rajasthan are as below:
ii.
o
Complaint Submission System
o
Preliminary Enquiry System
o
Regular Enquiry System
o
Legal and Prosecution System
The application will be integrated with following third party applications
· SMS gateway (available with RSDC)
· Integration with Email Solution (available with GoR)
iii.
Annexure 1 provides detailed FRS for the proposed application.
b) System Requirement Study
i.
Although the FRS has been provided for the application, the bidder is responsible to
carry out an independent system study at ACB HQ, at least 2 Range office and 3
Outposts to thoroughly understand the function and operational process of bureau
by a. Interacting with concerned bureau officials
b. Reviewing the existing systems, applications, and the Bureau website
c. Detailed study of requirements of ACBMS components and solutions
d. Detailing various use cases scenario
e. Understanding / assessing
data migration / digitization requirement and
strategy
f.
Understanding / assessing data inputs and outputs requirements
g. Collecting all input forms, registers and reports formats of bureau
ii.
The bidder shall be responsible for preparation of Software Requirement
Specifications (SRS) based on an independent assessment of the requirements of
the ACBMS and the functional requirements as specified in this RFP document. The
System Requirement Specifications (SRS) should be prepared as per the latest
version of the IEEE Standard 830 & 1233
iii.
c)
The bidder shall obtain sign-off of SRS from the designated authority.
Development of the web based application software
Seal & Signature of the Auth. Sign.
Page 21 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
i.
The bidder shall prepare & submit System Design Document (SDD) based on
principles of enterprise and service oriented architecture to provide for secure and
scalable application software. The design should be modular. SI shall submit the
SDD including
ii.
a.
Solution Architecture
b.
Application Architecture
c.
Deployment Architecture
d.
Database Design
An industry standard methodology should be adopted for Software Engineering,
covering the entire SDLC (Software Development Life Cycle).
iii.
The bidder shall be responsible for the development of dynamic content and
feature rich web based application software for the department and as per the
guidelines issued by the Govt. of India and Govt. of Rajasthan for the development
of the government websites/ portal like GIGW etc. The web based application
software should be of dynamic nature.
iv.
The departmental web based application software solution should support at least
Unicode 5.1/ 6.0 standard based Bi-lingual versions for user interface. It is
expected to be in Hindi and English (India) languages. The users should see the
labels and captions on selected language and additionally be able to feed-in their
data in the language of their own choice i.e. Hindi or English. Also, the SI must
translate, at its own, the equivalent Hindi captions for the English version (without
altering the meaning) of the web based application software and the same must
be submitted to the ACB, GoR for approval before implementation/ uploading or
vice-versa.
v.
To maintain information security during transaction the developed application
should support both HTTP and HTTPS
All internal data communication shall be
done through encrypted mode using SSL 3.0 (128 bit SSL certificate to be
deployed by the bidder on the Web/ Application Server for the entire project
duration).
SI shall follow the eSAFE: eGovernance Security Assurance
Framework Guidelines for Implementation of Security Controls issued by the
Department of Electronics
and Information Technology (DeitY), Ministry of
Communications & IT (MCIT), Government of India” which can be downloadable
at given below address
http://egovstandards.gov.in/guidelines/guidelines-for-information-security/eSAFEGD210.pdf/view
vi.
The development should be based open standards, 64-bit architecture and should
have in built system based application as per indicative FRS.
Seal & Signature of the Auth. Sign.
Page 22 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
vii.
The Application must have integrated security/ monitoring features with the
following: o
Definition of Roles and Users
o
Define Role-wise add/ edit/ view/ delete rights for each Entry Form/
Report in all modules
o
viii.
Digital Time and User Stamping of each transaction
Audit trail should be maintained, all deleted & edited records should be traceable
and copy of all editions/ deletions should be available with MIS reporting of the
same. The audit trail should be preserve in securely and No user other than
authorise should be allowed to modify audit record.
ix.
The information and forms collected from various sources and the development of
the web portal and application will have to be converted into appropriate electronic
open standard format(s) as mentioned in “Interoperability Framework for EGovernance in India- Document No IFEG;01 Version 1.0 May 2012 issued by
Department of Electronics
and Information Technology (DeitY), Ministry of
Communications & IT (MCIT), Government of India” which can be downloadable
at given below address
http://egovstandards.gov.in/standardsandFramework/IFEG/view
x.
The successful bidder will develop application with built-in feature or provide
software integration of third party application involving all services and software
functionalities as described below:
xi.
o
User Access Control
o
User Dash Board
o
Integration with Document Management System
o
Integration with existing Mailing Solution
o
Integration with existing SMS solution
o
Single sign on for all module including DMS
To maintain business continuty of RSDC, the selected bidder shall make use of
the existing DMS software (MS-Sharepoint or Omnidocs) available at RSDC for
integrating all the required DMS features in the web based application software.
Additional MS-Sharepoint or Omnidocs licenses, if any and as applicable, shall be
provided by the bidder. Expected number of name users licenses for DMS shall
be 70 only.
xii.
The Web based Application developed should be compatible with all the common
web browsers i.e. web based application software so developed should be
browser independent.
Seal & Signature of the Auth. Sign.
Page 23 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
xiii.
To maintain business continuity the SI shall make use of existing database cluster
(Postgre SQL Server v9.x and My SQL) available at the RSDC is considered.
d) Software Testing of web based application software
i.
The costs of testing (other than third party auditing) shall be borne by the bidder
ii.
The selected bidder shall be responsible for the following –
§
Conducting testing of various components/ modules of the software
developed, as per the latest version of the IEEE 730 standards.
§
Designing the Testing strategy, Test Cases
§
Submit test cases and test result to the RISL/ACB
§
Obtaining sign-off on testing approach and plan.
e) Deployment & Configuration of Web based Application Software
i.
The selected bidder shall be provided with required infrastructure at RSDC to
host application. The list of Infrastructure hardware and software to be provided
by RSDC is attached as Annexure 18 of this RFP document.
ii.
The bidder shall be responsible to coordinate with RSDC operator to host, install
and web based application software at RSDC Jaipur. SI shall adhere with the
rules and regulation of RSDC.
iii.
Configuration with RSDC infrastructure: The selected bidder shall be responsible
to configure the web based application software with existing infrastructure at
RSDC like DNS Server, backup server, EMS server, application load balancer
etc.
iv.
The bidder should provide server and client edition usage licenses (Perpetual
Licence, if any) in the name of
ACB for the various tools and third party
components used by the bidder to run the application. These tools would
typically include Application Framework / Environment,
integration with
Document Management System to manage document repository,
reporting
tools, database connector, Database Schema Designer, Help authoring tool etc.,
if used.
v.
All tool/software supplied should be with comprehensive OEM support though
online/phone line, along with upgrade option for period of 3 years from data of
installation.
f) Integration with SMS server and Email Server
Seal & Signature of the Auth. Sign.
Page 24 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
i.
Integration with SMS Gateway: The web based application software must
facilitate, from the day one, existing SMS gateway (MSDG) for automatically
sending the required details/ information through SMS to the designated officers of
the department and other stakeholders. The selected bidder would be responsible
for integrating the existing SMS Gateway (MSDG), provided by GoI, with the
proposed web based application software. The recurring SMS charges, if any,
shall be borne by RISL/ GoR.
ii.
Integration with email Server: The web based application software must facilitate
email / alerts to notify the designated officers of the department and other
stakeholders. The selected bidder would be responsible for integrating the existing
email solution of GoR with the proposed web based application software.
g) User Acceptance Testing (UAT)
The selected bidder would be responsible for:
o
Preparation and submission of detailed FAT/ UAT plans/ schedules/ procedures/
formats.
o
Prepare various use cases and scenarios
o
Performing Hardware and Software Testing: Conducting testing of various
components/ modules of the software developed (ACBMS application), as per the
latest version of the IEEE 730 standards. The bidder shall be required to share the
testing documents and standards with the designated S/w testing team, wherever
applicable/ required.
o
System Test Cases with Results
o
UAT Cases and Results
o
Rectifying the Hardware and Software (including the bureau website and ACBMS
application software) issues/ bugs reported during the testing to the satisfaction of
RISL/ ACB.
o
Final approval/user acceptance of the software and system shall be given by ACB /
RISL after successful implementation and testing. This is the responsibility of the
bidder to obtain the UAT approval from the ACB / RISL.
4.3.2. Supply, Installation and commissioning of IT and non-IT hardware
a) ACB shall provide the requisite space to the SI for the deployment of the requisite IT/
Non-IT infrastructure in the existing office premises at all the designated project
locations. However, the requisite infrastructure for hosting of web based application
software shall be provided by RISL to SI at RSDC, Jaipur. The selected bidder shall not
Seal & Signature of the Auth. Sign.
Page 25 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
be liable for any delay arising out of RISL/ ACB’s failure to provide the sites within the
stipulated period.
b) The entire hardware and software supplied under the project should be as per the
technical specifications specified in this RFP and IPv6 ready from the day one.
c) The bidder supply all the media and manuals, OEM support, updates, patches, and
errata for the project duration.
d) Bidder should ensure that none of the components and sub-components is declared
end-of-sale or end-of-support by the respective OEM at the time of submission of bid. If,
the OEM declares any of the products / solutions end-of-sale subsequently, bidder
should ensure that the same is supported by the respective OEM from its date of
installation till the end of the 3 years.
e) The bidder shall be responsible for supply, installation and commissioning of all
equipment as per finalised quantities of items mentioned in the BOM. However quantity
provided for passive work (structure cabling) is indicative and SI will carry out
independent exercise to finalise quantity as per location requirement in consultation with
ACB.
f) Bidder should ensure that all the software, hardware, peripherals, accessories, subcomponents required for the functionality and completeness of the solution, including
but not limited to devices, equipment, accessories, patch cords (copper / fibre), cables,
software, licenses, development / testing kits, tools, etc. should also be provisioned
according to the requirements of the solution.
g) SI will be responsible for supplying and installing all allied accessories, consumables
and fitting assembly and complete all related work for installation and commissioning
including but not limited to the following a. For installation of LAN, the bidder is expected to also carry out structured
cabling. Any equipment (like Screws, clamps, fasteners, ties, anchors, supports,
grounding strips, wires, fibre termination kits etc.) required for completing
installation of LAN will be supplied/provided by the bidder.
b. For installing and commission UPS at all the required locations, the bidder will
also be required to undertake any work related to electrical wiring for UPS only.
h) The bidder shall provide OEM documentation with every unit of the equipment supplied.
4.3.3. Data Digitization
a) Selected SI shall provide manpower for the data digitization & migration; this includes
creation of master database, Master of case file, entry of transactional data, scanning of
supporting documents of complaints/cases, attachment of scan documents tag with the
relevant case/compliant file.
Seal & Signature of the Auth. Sign.
Page 26 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
b) Quoted man-month rate by SI shall be used for cost estimation, efforts of all technical
resources- data entry operator, data entry supervisor responsible for data validation, any
managerial staff use by SI shall be taken into account for total man-month estimation to
carry out data digitization. For all technical resources irrespective of their experience
and specialization, the quoted man-month rate shall be used. Efforts of support staff
shall not be taken into consideration for this purpose
c) SI will develop a migration strategy for migration of digitized data of existing cases to
proposed system.
d) SI should ensure proper validations, data authenticity, tracking and reporting and
correction procedures for data creation for ACBMS from details shared by the ACB.
e) The SI is required to get acceptance of data from ACB
Indicative list of master records and transaction record need to be digitized is as under:
SNo.
Record Description
Number of
Approximate QTY
pages/forms
1
Data entry of cases e.g. complaint 6000 cases
@10 per case =
detail,
60,000
evidence
details, FIR
detail,
witness
, Finding reports,
Inspection report, etc.
2
4.3.4.
Data to be scanned and tagged 6000 cases
@100 per case =
with case files
6,00,000
Training & Capacity Building
a) Training of staff is essential for ensuring that the software developed is actually put
to use. Hence, the selected bidder shall also ensure a proper hands-on training to
the designated end-users on the Website and ACBMS application developed by him
so as to make them well conversant with the functionalities, features and processes
built in the ACBMS.
b)
Training could have multiple sessions as per the need and requirement of the
project/ application. Hence, SI shall conduct Training Needs Analysis of all the
concerned staff and drawing up a systematic training plan. The training duration
should be sufficiently long for effecting meaningful assimilation of training content by
an average user. There should be sufficient number of trainers in every training
session for conducting the training program.
c)
The content of the training plan and schedule shall be mutually decided by RISL /
ACB and the selected bidder later at an appropriate time period.
d)
Retraining the above staffs whenever significant changes are made in the
Seal & Signature of the Auth. Sign.
Page 27 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
application and/or personnel.
e)
The bidder shall take training feedback from the trainees.
f)
In case more than 30% of the respondents suggest that the training provided to
them was unsatisfactory or less than satisfactory, then SI would re-conduct the
same training at no extra cost.
g)
The space for training will be provided by the RISL/ACB, GoR.
h)
The requisite training infrastructure like computers, projector with screen shall be
provided by the RISL/ACB.
i)
Training should be of 8hrs/ session and all the trainees should be offered Morning
Tea and Evening Tea. Hence, the bidder is advised to quote accordingly.
j)
The SI shall provide training manual (role base), the language of training manual
shall be in Hindi and English.
k)
The SI shall ensure that all the training handouts are provided in Hardcopy to the
participants.
l)
Indicative Training needs identified for ACB are:
Sl.No.
Description
Training
of
No
of
employees
to
be
trained
approx
Batch
Size
No of
Batch
No. of
Session/Batch
Total No
of
Session
1
Basic
Skills/Office
Suite/Internet Skills
Including
Basic
Hardware
&
Networking
Concepts
60
20
3
2
6
2
Sensitization
Training
covering
basics
of
eGovernance,
Project Management
etc
20
10
2
1
2
3
Application Training
(Role Base)
120
20
6
2
12
o
Duration of each training session should be of 8 Hours per day,
o
Expected number of participants for the training session will be
15-20
participants except sensitization training to top management which expected to
be 5-10 persons only.
4.3.5.
System Integration and Commissioning of the Project ( Go live )
a) Facilitation for network connectivity: The bidder shall provide the following facilitation
and integration –
I. ACB will be responsible for providing the network connectivity (VPN over
Seal & Signature of the Auth. Sign.
Page 28 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
broadband) to the selected bidder for running ACBMS solution till RSWAN is
operational.
II. Dedicated 2 Mbps connectivity has been provided to the ACB HQ, through
SecLAN and further 1 Mbps broadband connectivity will be provided by ACB,
GoR. at range offices and outposts. However, SI will be responsible for the
LAN connectivity within the bureau offices.
b) The bidder shall integrate the hardware including the LAN, system software and
application software and commission the whole project. The purchaser shall conduct
Final Acceptance Testing on receipt of intimation of commission of the whole project
from the bidder. Only after the acceptance of FAT reports by RISL, the entire
infrastructure (including ACBMS application) would be deemed to have been
commissioned. After the successful commissioning of the project, the system would
be declared as Go-Live and enter into O&M/ FMS phase and the selected bidder
would also be issued a commissioning certificate by RISL/ GoR.
c) SI should provide following documents to the purchaser
·
Installation Manuals
·
User manual (Role wise)
·
Access Control Policy
·
Incident Management Policy
·
Change management plan development
d) Transferring the ownership of all software developed/ customized/ configured/
procured. All licenses & support related documents should be in the name of ACB,
GoR.
4.3.6.
Operation and Maintenance / Facility Maintenance Services (FMS)
Bidder would be responsible of operations and maintenance for the entire ACBMS
solution at ACB HQ, 8 Range Offices and 35 Outposts Offices for 3 years after the Golive (as certified and accepted by ACB/RISL)
4.3.6.1. Acceptance for Successfull Roll Out
a) Post Go- live, SI shall be responsible to provide 3 month implementation support.
b) During implementation period SI shall be responsible to create a separate register
for all telephone call/online calls received from all project locations regard, SI shall
also keep a tracker of call resolve and pending. SI will provide a monthly compliance
report after resolving of such calls to RISL/ACB. These calls / complaint will be
resolved by SI within the 3 month implementation period only.
c) After successful performance of the web based application software, a separate
sign-off/acceptance shall be issued to the SI by RISL/ ACB. The sign off shall be
Seal & Signature of the Auth. Sign.
Page 29 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
given only after successful resolution of the issues/ complaint.
4.3.6.2.
Deployment of Manpower for Facility Management
Services
i.
Bidder shall depute the following resources at the below project locations for
three years, from
starting day of commissioning of hardware and system
software, to trouble shoot, manage, replace and repair the hardware/ system
software onsite (if possible) and also lodge complaints of the local support team
at 8 Range Offices for repairing the items as per SLA.
S.
Resource at ACB HQ
1st Year
2nd Year
3rd Year
Project Manager
1
-
-
NOC
2
2
IT help Desk
1
1
Local support engineer
7
1
No
1.
2.
3.
4.
ii.
2
1
1
The minimum required technical qualifications and experience details for the
aforementioned manpower are provided in annexure 20 of this RFP document
iii.
Also, it would be the responsibility of the SI to retain the deployed manpower for
the entire Contract/ Project duration or in the event of a resource leaving the
employment with SI, the same shall be immediately replaced with another
resource of equivalent minimum qualifications and experience. All such events
should be notified prior to RISL.
iv.
As Hindi is Official Language of the Government of Rajasthan, the SI has to
appoint personnel having proficiency with Hindi language.
v.
The staff provided by the SI will perform their duties in accordance with the
instructions given by the designated officers of RISL/ ACB from time to time.
RISL/ ACB will examine the qualification, experience etc. of the personnel
provided before they are put on positions. The SI has to take approval from
RISL/ ACB for the proposed staff before their deployment. RISL/ ACB has every
right to reject the personnel, if the same is not acceptable, before or after
commencement of the awarded work/ project.
vi.
At no time, the provided manpower should be on leave or absent from the duty
without prior permission from the designated nodal officer of ACB. In case of long
term absence due to sickness, leave etc the SI shall ensure replacements and
manning of all manpower posts by without any additional liabilities to RISL/ ACB.
Substitute will have to be provided by the SI against the staff proceeding on
Seal & Signature of the Auth. Sign.
Page 30 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
leave/ or remaining absent and should be of equal or higher qualifications/
experience.
vii.
The proposed services shall be normally manned from 9:30 AM to 6:30 PM but
may vary as per the requirement throughout the project period or as decided by
RISL/ ACB
viii.
The operational support will have to be provided through a suitable helpdesk
system, to ensure that the solution is functioning as intended and that all
problems associated with operation are resolved satisfactorily.
·
The Helpdesk persons should be accessible to all the project locations and
their end-users on telephone/ e-mail.
·
The SI shall have to maintain an call log register with all the necessary
details/ references and submit the report from same to the nodal officer as
and when required. The format of the report would be mutually decided later
at appropriate time.
·
The end-users should be able to register complaint and obtain a complaint
no. from the helpdesk and same should be closed after the resolution of the
problem.
·
Helpdesk staff shall escalate the problem to the Project Manager and
maintain the log/ status of the complaint.
a) Asset Management Services
i. The SI shall be required to create database of all IT assets like hardware, software,
peripherals, etc., by recording information like configuration details, serial numbers,
licensing agreements, warranty and AMC details, etc. Create Software inventory with
information such as Licenses, Version Numbers and Registration Details
ii. The SI shall register all software procured by RISL / ACB in this bid document with
respective OEMs.
iii. The SI shall perform software license management and arrange for licensing contract
renewal for RISL / ACB for period of 3 years from the date of installation at no cost to
RISL / ACB and notify RISL/ACB on licensing contract renewal.
4.3.6.3. Support Services for Web Based Application S/w
i.
Overall administration, operations, monitoring, maintenance of the deployed web
based application software and the Database to ensure the desired uptime.
ii.
During O&M period ACB/RISL may request SI, to make necessary changes in
the layout, colour schema, MIS reports format, input forms layout. However,
these changes shall be suggested keeping in view that it should not transform in
Seal & Signature of the Auth. Sign.
Page 31 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
database schema. The SI shall be responsible to make these changes at No
extra cost to purchaser.
4.3.6.4.
MIS Reports:
The SI shall have to submit certain key deliverables which are mentioned hereunder.
However, in addition to the reports/ deliverables as indicated below, SI shall prepare
and submit all other required information in the desirable format as notified by the
purchaser related to project.
The formats for all the reports shall be prepared by the SI
and submitted to the
purchaser for approval. The reports submitted by the SI should strictly be in the
approved format only which, if required, may be revised from time to time.
Sr
1.
Activity
Deliverable
Asset
Management
Services
2.
Software
license
management
3.
Software Inventory
Frequency
Time Frame
Details of Hardware Equipments Once
with serial no., configuration
details,
Software
Details,
Policies implemented
During
Details of software licences with Once
renewal due date
During
Details of software licence with Bi-Annual
renewal due date
Within 1 Week
handholding
handholding
of end of each
Quarter
4.
SLA
FMS
Support
(User)
Log reports of help desk, Call
resolved,
unresolved
Daily
Monthly
Quarterly
Within 1 Week
and
escalated issues
List of stand by equipments
Incident Reporting
of end of each
Quarter
User
complaint
resolve time
redressal Quarterly
Within 1 Week
of end of each
Quarter
5.
SLA Manpower Report
Attendance
deployed
of
Manpower
Quarterly
Within 1 Week
of end of each
Quarter
6.
SLA for Application up
time
Application up time report
Quarterly
Within 1 Week
of end of each
Quarter
4.3.7.
Change Request Management Services
i.
ACB envisaged that ACBMS should have integration with exiting application. The
Seal & Signature of the Auth. Sign.
Page 32 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
requirement for integration shall be finalise in consultation with ACB/ DoIT&C/NIC as
and when these projects will be operational. The required integration shall be done
through change request management system. Following are envisaged existing
application but not limited to these to be considered for change request.
ii.
·
Integration with UIDAI
·
Integration with SUGAM
·
Integration with CCTNS
RISL/ ACB may at any time, by a written order given to the selected bidder, make
changes within the general scope of the Agreement in any one or more of the
following: ·
Designs, specifications, requirements which software or service to be
provided under the Agreement are to be specifically developed and rendered
for the ACB
·
The method of deployment, shipping or packing.
·
Schedule for Installation Acceptance.
·
The place of delivery and/or the services to be provided by the selected
bidder.
iii.
The steps to be followed in change request/ management procedure has been
described in Chapter for Change Management of this RFP.
4.3.8. Third Party Audit (TPA)
o A third party audit may be got done by RISL/ ACB, GoR at its own cost. The TPA would
be selected separately by RISL/ GoR.
o
The audit will study execution of the project by SI and verify the executed work against
entire scope envisaged in the RFP. If TPA report suggests any modification / alteration
to meet RFP requirement / adherence then SI shall be required to do the needful without
any financial implication to the purchaser.
o
The TPA activity will be one time and will be initiated after start of the FMS phase.
o
The bidder shall be required to share the testing documents and standards with the
designated third party wherever applicable/ required.
o
Based on the audit reports submitted by the TPA, the selected bidder shall make the
required changes to the solution deployed (as per RFP) and incorporate the suggestions
of the auditor at no extra cost. The purchaser may recover costs from the pending
payments or performance security on failure of the bidder to make the required
changes.
Seal & Signature of the Auth. Sign.
Page 33 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
4.4. Project Duration
As per RFP, the ACBMS project will likely to achieve Go Live status within 52 weeks of
award of contract. This will be followed by 3 years of operations and maintenance
phase post successful commissioning of the project.
4.5. Roles & Responsibilities (Stakeholder-Wise)
A contract monitoring committee will be constituted for overall monitoring of the progress of
ACBMS project. The contract monitoring committee will be appraised on the periodic
developments by the bidder. The contract monitoring committee shall consist of the
members of RISL and ACB
a) Responsibilities of RISL
The role of RISL in the successful implementation of the solution includes discharging the
following responsibilities:
·
To ensure active participation from the Bureau users
·
To coordinate with other government agencies and Bureau
·
To provide acceptance and Sign off SRS document
·
Review the solution design document, submitted by the selected bidder.
·
To conduct review meetings at defined regular intervals to monitor the overall
progress of the project.
·
Provide feedback on changes to be in the solution to improve usability of the
application software.
·
Report problems/ bugs in solution to the selected bidder for immediate action/
rectification.
·
Prioritize the change requests as per project objectives.
·
Provide required infrastructure to conduct training at Jaipur
·
Co-ordination with the RSDC Operator and other stakeholders of the project.
·
To coordinate with the ACB for prividing schedule for hardware installation &
commissioning at ACB Ho, Range offices, ACB Outposts.
·
To coordinate with the ACB for prividing schedule for data digitisation& training
·
To approve testing aproch methdology and test cases submitted by SI
·
To provide sign off/ acceptance of SRS, approval of testing approch & test
cases, User Acceptance testing (UAT), Final Acceptance Testing (FAT),
Commissioning Certificate, Acceptance
of
successful performance
after
completion of 3 Months
·
Facilitate UAT, security audit and performance audit
·
Appoint agency for third party audit of web based application software if needed
·
To ensure timely project milestones sign offs.
Seal & Signature of the Auth. Sign.
Page 34 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
·
To approve and oversee the proposed training plan
·
Set up and administration of escalation mechanism
·
Review and approval of payment against CAPEX as per payment schedule as
mentioned in section of this RFP
·
Review and approve the payments to the bidder as per SLA
·
Approval and disapproval of change requested including the finalisation of efforts
estimation, cost estimation, milestone and payment
·
Any other help/ assisperiodic report submitted by SI, and acceptance/ coordination required for the successful implementation and operations of the work/
project
b) Responsibilities of ACB, GoR
The roles and responsibilities of the ACB, GoR shall be as follows: ·
To formulate a nodal team for the project responsible for end to end coordination
and execution of the ACBMS project.
·
To identify the Range Office and outposts for conducting detailed SRS study
·
To provide necessary support during requirement gathering, sharing of sample
reports and other IT infrastructure requirements
·
To identify and appoint nodal officer for facilitating the project execution
·
Explain the functional requirements in detail to the selected bidder
·
To approve schedules for Hardware deployment , training ,data digitization etc
proposed by the bidder .
·
Provide space and infrastructure for purpose of training in case training is
required at a location outside Jaipur
·
ACB
will
be
responsible
for
providing
the
network
connectivity
(MPLS/broadband) to the SI for running ACBMS solution till RSWAN is
operational.
·
To ensure active participation from the bureau users
·
To provide data required to be digitized
·
To conduct review meetings at defined regular intervals to monitor the overall
progress of the project.
·
Provide feedback on changes to be in the solution to improve usability of the
application software.
·
Prioritize the change requests as per project objectives.
·
To ensure timely project milestones sign offs
·
to provide readiness report from all project location after commissioning of
infrastructure
Seal & Signature of the Auth. Sign.
Page 35 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
·
To approve and oversee the proposed training plan
·
To ensure close coordination of all the participants and the external agencies
involved in the project.
·
To review the installation, commissioning and maintenance of the software
·
To take steps to mitigate any potential risks that might surface during the course
of the project
·
Set up and administration of an issue and escalation management process.
·
To identify the staff at various levels who need to undergo user training
·
To identify employees who needs to be trained by SI for learning the technical
aspects of the ACBMS application.
·
Upload monthly arrival and price report on the central web based application
software by the Range office and outposts.
·
ACB will provide dedicated telephone line at ACB HQ for managing help desk
·
Handle change management
·
To monitor the overall progress of the project
·
Review of software requirement specifications, system design, hardware
sizing/Scrutiny of deliverables for their compliance with RFP specifications
·
Review content, methodology and pedagogy for user training
·
Review data migration plans and their implementation.
·
Review the documentation provided by the Bidder and verifies that it conforms to
the requirements.
·
To facilitate RISL in providing sign-off /acceptance UAT of web based application
software
·
To facilitate RISL in providing sign-off/acceptance final
FAT of web based
application software and its integration with hardware and network components
·
To facilitate RISL in providing acceptance of successful performance of web
based application software (post implementation)
·
Periodic SLA monitoring of the system deployed by the successful bidder
·
To ensure timely release of the payments as per agreed schedule
c) DoIT&C GOR
Rajasthan State Data Centre (RSDC)
·
The core software application infrastructure and web based application software
are expected to be hosted at the RSDC. The data collected from all 8 Range
Offices and 35 Outposts will be centrally stored at the RSDC.
·
All services, applications and infrastructure to provide efficient delivery of G2G
and G2C services will be consolidated on RSDC.
Seal & Signature of the Auth. Sign.
Page 36 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
·
The SI will be provided with the requires hardware infrastructure for hosting web
ACBMS software applications. The list of infrastructure to be provide by RSDC
has been attached as Annexure18 of this RFP.
·
RSDC will be responsible to manage all servers and infrastructure to be use for
deployment of web based application software.
·
RSDC will provide infrastructure such as firewall service, directory service,
management and data storage services, SMS and payment gateway which
could be a shared infrastructure to all the applications /departments in the
RSDC.
·
Some of the key functionalities of RSDC are Central Data Repository of the
State, Secure Data Storage, Disaster Recovery, Remote Management and
Service Integration.
·
RSDC will provide access and share middleware application software available
at RSDC (MS share point and omni docs) to build DMS and other applications.
·
RSDC will provide database cluster along with database admin access rights to
SI for manage database.
·
RSDC will provide SAN Storage, high speed (Fibre Channel)
·
RSDC will provide SAN SATA and Tap liberary usable for archived data storage.
·
RSDC will provide required number of Internal and external IP at data centre for
the ACBMS application.
d) Responsibilities of System Integrator (SI)
The detailed role & responsibilities of SI has already been described in the scope of work
section 4 of this RFP.
4.6. Project Deliverables, Milestones & Time Schedule
In view of the volume and complexity of the ACBMS, bidder is expected to carry out all
ground work for implementation including documentation, coordination with GoR and other
stakeholders of the project, site survey etc. These reports or deliverables are to be
submitted timely by bidder to the RISL / ACB to ensure the timely and smooth execution of
ACBMS project. Certain key deliverables are identified for each of the parts/stages, which
are mentioned hereunder. However, bidder has to prepare and submit any required
information in form of Reports / excel sheet / document desired by RISL related to ACBMS
other than defined hereunder in the table.
The milestones and deliverables for the implementation of ACBMS project would be as
follows:T= Date of work order
Seal & Signature of the Auth. Sign.
Page 37 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Scope of Work
Milestone
Deliverable
(Reports/ Documents & Infra)
Project Kick off
Study, Design,
Development &
Deployment of
ACB
Supply and
Installation of
IT and Non IT
Infrastructure
and all project
location
Time of
completion
·
Detailed Project Plan with
Timelines (.MPP/ .XLS or any
other format chosen by the
bidder)
·
Service Level Agreement (SLA)
·
Performance Security Deposit
Perform System Study
& Prepare SRS
·
Approved Software
Requirement Specifications
(SRS)
T2=T1+12 weeks
(includes 2 weeks
for approving
SRS by
purchaser)
Development &
Deployment of Web
ACBMS Application S/w
·
System Design Document
(SDD) / Process Design
Report
·
Testing Methodology including
test cases and test plan and
Test Results
T3=T2+28 weeks
(Including 3
weeks for time
taken for UAT
acceptance)
·
Development and deployment
of web based application
software
·
Electronic conversion of master
records
·
Data digitization of 500 cases
·
UAT Acceptance
·
Hardware deployment plan ,
testing plan & methodology
·
Item
Delivery
Report, T5= T4+4 weeks
inspection reports with detailed
specifications
·
Site Completion/redlines
Project Plan
Installation &
commissioning at ACB
HQ
Procurement, Installation
and commissioning of IT
& Non IT infrastructure at
T1=T+2 Weeks
T4= T2+8 weeks
Report
ACB HQ as per BoM
annexure -2 (A)
Installation &
commissioning at 8
Range Offices
·
Item
Delivery
Report, T6= T4+8
inspection reports with detailed
Weeks
specifications
Procurement, Installation
and commissioning of IT
& Non IT infrastructure at
8 Range Offices as per
BoM annexure -2 (A) and
(Para 4.3.2 of SoW)
·
Site Completion/ Readiness
report from each project
location
Seal & Signature of the Auth. Sign.
Page 38 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Scope of Work
Milestone
Deliverable
(Reports/ Documents & Infra)
Time of
completion
Installation &
commissioning at 35
Outposts Offices
·
Item
Delivery
Report, T7= T4+12
inspection reports with detailed
Weeks
specifications
Procurement, Installation
and commissioning of IT
& Non IT infrastructure at
35 Outposts Offices as
per BoM annexure -2 (A)
and (Para 4.3.2 of SoW)
·
Site
Completion/Readiness
report from each project
location
Data
Digitization
Perform activities as per
the scope defined in SoW
·
Data Digitization of
remaining case details (as
provided by ACB)
T8= T3+6 Weeks
Training
Perform activities as per
the scope defined in SoW
·
Training Plan
T9= T3+6
·
Training manual
Weeks
·
Trainees Feedback
Rollout of
ACBMS Go
Live
GO-Live
·
Final Acceptance (FAT)
T10= T9+4
·
·
Installation Manuals
Weeks
·
User manual (Role wise)
·
Change management plan
development
·
Operation and
Maintenance
for a Period of
three year
post
Publish web based
application software
for internal and public
Use
Obtaining required
approvals and
procedural formalities
for hosting
Successfully Roll out
Acceptance
·
Implementation
support for period of
3 months as per
SOW
acceptance of
FMS During O&M
the solution
Perform all activities
defined in SoW for 3
years from Go-Live for all
IT Infrastructure provided
at ACB HQ, Range
Offices and Outposts
Support for
web based
application
software
Support for web based
application software
Perform activities related
to maintenance of web
based application
software, defined in SoW
section (Para 4.2.7.4)
Operation & Maintenance
Seal & Signature of the Auth. Sign.
·
Acceptance of successfully
performance of web based
application software
·
Monthly compliance report on
incident reporting and bugs
fixing
Post –Go live
+12 Weeks
Report from defined in para (Para
4.3.6.2),
Operation
&
management/ facility management
section of this RFP
Go-Live + 3 Years
Report from defined in (Para
4.3.6.3), Operation &
management/facility management
section of this RFP
Go-Live + 3 Years
Page 39 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Scope of Work
Milestone
Deliverable
(Reports/ Documents & Infra)
Time of
completion
/Facility Maintenance
services for a period of 3
years from Go-Live
The entire activity should be completed within 12 months of signing of contract. This will be followed by
operations & maintenance phase for 3 years post successful commissioning of the project.
·
Deliverables/ Reports, if any, mentioned elsewhere in this RFP document would also be
accounted for while ascertaining the successful completion of the respective Phase of the project
and SI would submit the same as per the requirement of RISL/ ACB.
·
It may be also be noted that the time schedule for each milestone shown in the table above
would be enforced independently, even though some of them are inter-dependent. This would
have a cascading effect of penalties for delays in all other milestones dependent on the
precedent milestone.. Any delay in the approval of the deliverable(s) submitted by the SI to RISL/
ACB shall not account for the delay on SI’s part.
·
The Purcchaser may schedule data digitization and training in phase manner, the SI will adhere
with time lines of the schedule
Seal & Signature of the Auth. Sign.
Page 40 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
5. INSTRUCTION TO BIDDER (ITB) & BIDDING PROCESS
1. Sale of Tender/ Bidding Document
The complete bidding document would be available on the websites for the period as
specified in the NIT. The prospective bidders are permitted to download the bidding
document from any of the specified websites but must pay the cost of tender /bidding
document while submitting the ebids.
2. Clarifications to the Bidding / Bid Document
a) If the prospective bidder has any doubts as to the meaning of any portion of the
bidding document, then he is allowed to refer the same to the tendering authority
and get clarifications. He may do so by contacting the tendering authority in writing
at the tendering authority’s address indicated in the NIT.
b) The Tendering authority/ Procurement Committee will respond, either in writing or
will upload the details on the websites mentioned in the NIT, to any request for
clarification, provided that such request is received no later than 3 days after the
Pre-bid Meeting. All the prospective bidders must submit the prescribed Tender
Fee before submitting any such requests to the Tendering authority.
c) The Tendering authority shall forward copies of its response to all Bidders who
have purchased the Bidding Document directly from it and shall also place it on
the eProc website, including a description of the inquiry but without identifying its
source.
d) Should the Tendering authority deem it necessary to amend the Bidding
Document as a result of a clarification or otherwise, it shall do so by issuing a
revised bidding document and/ or Addendum/ Corrigendum. If need be, the
deadline for submission of Bids may also be extended in order to give reasonable
time to the prospective Bidders to take into account the amendment.
e) Post-bid clarifications, if any, will be sought only once. Hence, bidders are advised
to prepare and submit the bid accordingly and ensure that all the required
documents are in place. Also, clarifications shall be sought only for the bid/
documents submitted and no new documents shall be accepted.
3. Pre-bid Conference/ Meeting
a) The bidder or its official representative (not more than two representatives per
bidder) is invited to attend the pre-bid meeting as per the details specified in NIT.
The objective of this meeting is to address the generic queries of the prospective
bidders related to the Project/ bidding document.
Seal & Signature of the Auth. Sign.
Page 41 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
b) Only the bidders/ firms, who have purchased the bidding document from the office
of the RISL or have deposited the prescribed tender fee, are allowed to attend the
pre-bid conference/ meeting and submit their pre-bid queries in the specified
format as provided in Annexure 5. Bidders having purchased the bidding
document are welcome to attend the pre-bid meeting, even if they do not have any
specific queries. Tendering authority shall respond to the queries of only those
bidders who have purchased the bidding document till the day of pre-bid meeting
or within 2 Days after the Pre-bid meeting.
c) As a result of discussions in the pre-bid conference, if modifications in the bidding
document, specifications of services and/ or goods are considered necessary, they
may be done by issuing an addendum/ corrigendum and its copies shall be sent
through Email/ post to all the bidders having purchased the bidding document. The
corrigendum/ addendum and the Final bidding document will be placed on the
websites as specified in the NIT.
d) The tendering authority reserves the right not to respond to any/ all queries raised
or clarifications sought if, in their opinion and at their sole discretion, they consider
that it would be inappropriate to do so or do not find any merit in it.
4. Amendment of Bidding Document
a) At any time prior to the deadline for submission of the Bids, the tendering authority
may amend the Bidding document by issuing Corrigendum/ Addendum.
b) Any Corrigendum/ Addendum issued shall be a part of the Bidding document and
shall be communicated to all, either in writing or by uploading the details on the
websites mentioned in the NIT, who have purchased the Bidding document and on
the websites specified in NIT.
c) To give prospective Bidders reasonable time in which to take a Corrigendum/
Addendum into account in preparing their Bids, the tendering authority may, at its
discretion, extend the deadline for the submission of the Bids.
d) Any change in date of submission and opening of bids would be published in
appropriate manner including the websites mentioned in the NIT.
5. Documents comprising the Bid
a) A single-stage two-envelope/ cover system shall be followed for the e-bid: a. Technical Bid (including the pre-qualification & technical Documents)
b. Commercial Bid
b) Technical Bid shall include the following documents: S. No. Documents Type
1. Covering Letter – Technical Bid
Seal & Signature of the Auth. Sign.
Document Format
On bidder’s letter head duly
Page 42 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
signed by authorized signatory
(as per Annexure - 4)
Bidder’s Authorization Certificate
As per Format given at
Annexure – 7
Copy of board resolution/ Power of Power of Attorney/ Copy of
Attorney in favor of person signing the board resolution
Letter of Authority at 2 above
Fee Details
Tender Fee
Scanned copy of Fee Receipt
RISL Processing Fee
Scanned copy of Fee Receipt
EMD
Scanned copy of DD/ Banker’s
Cheque/ Bank Guarantee
Pre-Qualification Documents
Tender Form
As per Annexure-6
Self-Declaration – No Blacklisting
As per Annexure-8
All the documents mentioned in the As per the format mentioned
“Eligibility Criteria”, in support of the against the respective eligibility
eligibility
criteria clause
Technical Documents
Certificate of Conformity/ No-Deviation
As per Annexure-9
Manufacturer’s Authorisation Form (MAF)
As per Annexure-10
Undertaking of Authenticity of Computer As per Annexure-11
Equipments
Statement of Deviations
As per Annexure-12
Compliance
Report
of
Technical As per Annexure 3, along with
Specifications
datasheet
c) Commercial bid shall include the following documents: S. No. Documents Type
1. Covering Letter – Financial Bid
2.
Price Bid
Document Format
On bidder’s letter head duly
signed by authorized signatory
As per Annexure-13, As per
BoQ (.XLS) on eProc website
d) The bidder should ensure that all the required documents, as mentioned in this
RFP/bidding document, are submitted along with the bid and in the prescribed
format only. Non-submission of the required documents or submission of the
documents in a different format/ contents may lead to the rejections of the bid
proposal submitted by the bidder. Post-bid clarifications, if any, will be sought only
once. Hence, bidders are advised to prepare and submit the bid accordingly and
ensure that all the required documents are in place. Also, clarifications shall be
sought only for the bid/ documents submitted and no new documents shall be
accepted.
Seal & Signature of the Auth. Sign.
Page 43 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
6. Cost of Bidding
The Bidder shall bear all costs associated with the preparation and submission of its
eBids, and the tendering authority shall not be responsible or liable for those costs,
regardless of the conduct or outcome of the bidding process.
7. Language of Bids
The eBid, as well as all correspondence and documents relating to the Bid exchanged
by the bidder and the tendering authority, shall be written only in English Language.
Supporting documents and printed literature that are part of the bid may be in another
language provided they are accompanied by an accurate translation of the relevant
passages in English/ Hindi language, in which case, for purposes of interpretation of
the Bid, such translation shall govern.
8. Bid Prices
a) The price/financial bid must be specidfied in the BoQ file available at eProc and
without changing its form and type.
b) Prices quoted in the bid must be firm and final and shall not be subject to any
modifications, on any account whatsoever. The price quoted shall include all costs,
taxes and duties applicable to the bidder as per law of the Central/ State
Government/ Local Authorities, As the taxes are asked separately, the revision in
taxes/ duties including VAT and Service Tax shall be on account of the tendering
authority if they have been asked for separately in the financial bid and are not
taken into account for the purpose of comparison of bids. If, however, they have
not been asked for separately, any benefit or additional cost will be on account of
the bidder.
c) All the prices should be quoted only in Indian Rupees (INR) Currency.
d) Prices/ Rates shall be written both in words and figures. There should not be
errors and/ or over-writings. Corrections/ alterations, if any, should be made clearly
and initialled with dates by the authorized signatory.
e) All rates quoted must be FOR destination/ site where the IT/ Computer systems
and allied items are to be installed, and should include all incidental charges
except Central/ Rajasthan VAT, which should be shown separately in the
Financial/ Commercial bid format only. In case of local supplies the rates should
include all taxes, etc., and RISL will not pay any cartage or transportation charges.
f) Prices quoted in the bid must be firm and final and shall not be subject to any
modifications, on any account whatsoever.
Seal & Signature of the Auth. Sign.
Page 44 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
g) The prices quoted by the Bidder in the Financial/Commercial bid shall conform to
the requirements specified therein.
h) All the required items must be listed and priced separately in the financial bid. If a
financial bid shows items listed but not priced, their prices shall be assumed to be
included in the prices of other items. Items not listed in the financial bid shall be
assumed not to be included in the bid, and provided that the bid is substantially
responsive, the corresponding adjustment shall be applied in accordance with the
provisions of bidding document.
i)
The price to be quoted in the financial bid shall be the total price of the bid.
Discount, if any should be included in the quoted price. Discounts of any type,
indicated separately, will not be taken into account for evaluation purposes.
j)
The disaggregation of price components is required solely for the purpose of
facilitating the comparison of bids by the tendering authority. This shall not in any
way limit the tendering authority’s right to contract on any of the terms offered: i. For Goods offered from within/ outside the country.
ii. For Related Services whenever such Related Services are specified in the
bidding document.
9. Period of Validity of Bids
a) Bids shall remain valid for the period of 120 days, as specified in NIT, after the bid
submission deadline date prescribed by the tendering authority. A bid valid for a
shorter period shall be rejected by the tendering authority as nonresponsive bid.
b) In exceptional circumstances, prior to the expiration of the bid validity period, the
tendering authority may request bidders to extend the period of validity of their
Bids. The request and the responses shall be made in writing. If EMD is
requested, it shall also be extended for a corresponding period. A bidder may
refuse the request without forfeiting its bid security i.e. EMD. A bidder granting the
request shall not be required or permitted to modify its bid.
c) If the validity of the EMD instrument expires before the bid validity period, the
bidder will ensure renewal / resubmission of EMD as and when asked for.
10. Earnest Money Deposit (EMD)
a) Every bidder, if not exempted, participating in the bidding process must furnish the
required earnest money deposit as specified in the Notice Inviting Tender (NIT).
b) Government of Rajasthan and Union Government undertakings, corporations,
companies; autonomous bodies managed or controlled by Government are not
required to submit the EMD. Receipt of EMD or Registration certificate or Certificate
Seal & Signature of the Auth. Sign.
Page 45 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
that the bidder is a Government undertaking/ Corporation/ Company/ autonomous
body as mentioned above shall necessarily accompany the sealed bid without which
the bid shall be rejected forthwith.
c) For the S.S.I. units of Rajasthan, a 75% discount shall be given in EMD, i.e., they will
have to pay only 25% of the prescribed EMD. Similarly, Performance Security Deposit
shall be @ 1% of the total agreed/ ordered project cost. They will have to furnish
original or certified copy of the registration of SSI unit issued by the Director of
Industries in respect of stores for which they are registered.
d) Earnest money deposit of a bidder lying with RISL in respect of other bids awaiting
decision will not be adjusted towards earnest money deposit for the fresh bids. The
earnest money originally deposited may, however, should be taken into consideration
in case bids are re-invited.
e) Form of EMD: The EMD may be deposited in the form of a banker’s cheque or
demand draft or bank guarantee (only if it exceeds Rs 10 lacs) in favour of “Managing
Director, RajCOMP Info Services Limited” payable at “Jaipur”. The EMD shall be valid
for the period of Bid Validity as mentioned in the NIT. The same shall be payable at
par at “Jaipur”.
f) Refund of EMD: The earnest money deposit of unsuccessful bidders shall be refunded
soon after final acceptance of bid and award of contract. In case of best/ successful
bidder, the EMD, if feasible, may also be adjusted in arriving at the amount of the
Performance Security Deposit.
g) Forfeiture of EMD: The EMD taken from the bidder shall be forfeited in the following
cases:i. When the bidder withdraws or modifies his bid proposal after opening of bids.
ii. When the bidder does not execute the agreement after placement of order
within the specified time.
iii. When the bidder fails to commence the supply of the goods and service as per
purchase / work order within the time prescribed.
iv. When the bidder does not deposit the security money after the purchase/ work
order is placed.
v. To adjust any dues against the firm from any other contract with RISL.
Seal & Signature of the Auth. Sign.
Page 46 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
11. Deadline for the submission of Bids
a) Bids must be submitted by the bidders online at eProc website as indicated in the NIT
of subsequent corrigendums, if any.
b) Normally, the date of submission and opening of bids would not be extended.
However, in exceptional circumstances or when the bidding document is required to
be substantially modified as a result of discussions in pre-bid conference and the
time with the prospective bidders for preparation of bids appears insufficient, the date
may be extended by Managing Director, RISL and due publicity to such change in
date of submission of bids would be given. In such cases, it would be ensured that
after issue of corrigendum, reasonable time is available to the bidders to prepare and
submit their bids. Any change in date of submission and opening of bids would also
be placed on the respective websites immediately. However, if the modifications in
bidding document, specifications of goods and service are substantial, fresh
publication of original bid inquiry may also be issued.
c) The tendering authority may, at its discretion, extend the deadline for the submission
of bids by amending the RFP/bidding document, in which case all rights and
obligations of the tendering authority and bidders previously subject to the deadline
shall thereafter would be subject to the deadline as extended.
12. Format and Signing of Bid
a) The bid forms/ templates/ annexures etc., whereever applicable, shall be typed or
written in indelible ink and shall be signed (all the pages) by a person duly
authorized to sign, in token of acceptance of all the terms and conditions of the
bidding document. This authorization shall consist of a written letter of
Authorization from the authorised person, accompanied with a board resolution, in
case of a company/ power of attorney as per Annexure 7.
b) Any amendments such as interlineations, erasures, or overwriting shall be valid
only if they are signed or initialled by the authorized person signing the bid.
c) The bid, duly signed (digitally) by Authorized Signatory, should be uploaded on
the eproc portal in respective file/ format.
d) Bidders must submit their bids online at eproc portal. Bids received by another
other means shall not be accepted.
e) If bids are not submitted as per the details mentioned in this bidding document and
eProc website, the tendering authority shall reject the bid.
13. Withdrawal and Resubmission ( Substitution) of Bids
Seal & Signature of the Auth. Sign.
Page 47 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
a) If permitted by the tendering authority, a Bidder may withdraw its bid or re-submit
its bid (technical and/ or financial cover) as per the instructions/ procedure
mentioned at eProc website under the section “Bidder’s Manual Kit”.
b) Bids withdrawn shall not be opened and processed further.
14. Bid Opening/ Opening of Tenders
a) The designated Procurement Committee will perform the bid opening, which is a
critical event in the bidding process.
b) The tendering authority shall conduct the bid opening at the address, date and
time specified in the NIT.
c) All the bids received up to the specified time and date in response to all the bid
inquiries shall be opened by the members of the designated Procurement
Committee at the specified place, date and time in the presence of bidders or their
authorized representatives who may choose to be present. Alternatively, the
bidders may also view the bid openeing status/ process online at eProc website.
d) All the documents comprising of technical bid/ cover shall be opened &
downloaded from the eProc website (only for the bidder’s who have submitted the
prescribed fee(s) to RISL).
e) All the technical bid covers, except the Commercial/ Financial cover, shall be
opened one at a time, and the following read out and recorded: the name of the
bidder; the presence of the RISL processing fee, tender fee, EMD and any other
details as the tendering authority may consider appropriate.
f) The Tendering authority shall prepare a record of the bid opening that shall
include, at a minimum: the name of the bidder and the presence or absence of
processing fee, Tender fee, and EMD. The bidder’s representatives who are
present shall be required to sign the attendance sheet.
g) The Commercial/ Financial cover shall be kept unopened and shall be opened
later on the date and time intimated to the bidders who qualify in the evaluation of
technical bids.
15. Selection Method
a) A bidder would be selected on the basis of Least Cost Based Selection Method
(LCBS) i.e. L1 method wherein an eligible bidder with adequate technical
competence and the most competitive (lowest) rates/ quote would be selected for
the implementation of the project.
16. Guiding Principles for evaluation of bids
a) The tendering authority shall strictly apply only and all of the evaluation and qualification
criteria specified in the bidding document.
Seal & Signature of the Auth. Sign.
Page 48 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
b) The determination shall be based upon an examination of the documentary evidence of
the bidder’s qualifications and proposed solution submitted by the bidder.
17. Determination of Eligibility and Responsiveness
a) A bidder shall be considered to be eligible if it meets the eligibility and technical
evaluation criteria mentioned in the RFP document.
b) A responsive bid would be the one that meets the requirements of the bidding document
without material deviation, reservation, or omission where: i.
“Deviation” is a departure from the requirements specified in the bidding
document;
ii.
“Reservation” is the setting of limiting conditions or withholding from
complete acceptance of the requirements specified in the bidding
document; and
iii.
“Omission” is the failure to submit part or all of the information or
documentation required in the bidding document.
c) A material deviation, reservation, or omission is one that,
i. if accepted, would: a. affect in any substantial way the scope, quality, or performance of the
Goods and Related Services specified in the bidding document; or
b. limits in any substantial way, inconsistent with the bidding document, the
tendering authority’s rights or the bidder’s obligations under the proposed
Contract; or
ii. if rectified, would unfairly affect the competitive position of other bidders
presenting responsive bids.
d) The tendering authority shall examine the technical bid including the pre-qualification
documents.
e) Provided that a bid is substantially responsive, the tendering authority ·
may waive any nonconformity in the bid that does not constitute a material
deviation, reservation or omission.
·
may request that the bidder submit the necessary information or documentation,
within a reasonable period of time, to rectify nonmaterial nonconformities or
omissions in the bid related to documentation requirements. Requesting
information or documentation on such nonconformities shall not be related to any
aspect of the price of the bid. Failure of the bidder to comply with the request may
result in the rejection of its bid.
·
shall rectify nonmaterial nonconformities or omissions. To this effect, the bid price
shall be adjusted, for comparison purposes only, to reflect the price of the missing
Seal & Signature of the Auth. Sign.
Page 49 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
or non-conforming item or component. The adjustment shall be made using the
method indicated in pre-qualification and Evaluation Criteria of this bidding
document.
f) The eligible bidders whose bid is determined to be substantially responsive shall be
considered to be qualified in the technical evaluation, unless disqualified pursuant to
clause 18 or 31, and shall be informed, either in writing or by uploading the details on
the websites mentioned in the NIT, about the date, time and place of opening of their
financial bids.
g) The firms which could not qualify in technical evaluation will be informed about this
fact. Their financial bid will be returned unopened and EMD refunded after completion
of the bid process i.e. award of the contract to the best/ successful bidder.
18. Conflict of Interest
a) RISL considers a conflict of interest to be a situation in which a party has interests that
could improperly influence that party’s performance of official duties or responsibilities,
contractual obligations, or compliance with applicable laws and regulations. In
pursuance of RISL's Procurement Ethics requirement that bidders, suppliers, and
contractors under contracts, observe the highest standard of ethics, RISL will take
appropriate actions against the bidder, if it determines that a conflict of interest has
flawed the integrity of any procurement process. Consequently all bidders found to
have a conflict of interest shall be disqualified.
b) A bidder may be considered to be in a conflict of interest if the bidder or any of its
affiliates participated as a consultant in the preparation of the solicitation
documents/RFP for the procurement of the goods and services that are the subject
matter of the bid.
c) It may be considered to be in a conflict of interest with one or more parties in the
bidding process if
i. they have controlling shareholders in common; or
ii. it receives or have received any direct or indirect subsidy from any of them; or
iii. they have the same legal representative for purposes of the Bid; or
iv. they have a relationship with each other, directly or through common third parties,
that puts them in a position to have access to information about or influence on the
Bid of another Bidder, or influence the decisions of the tendering authority
regarding this bidding process.
19. Confidentiality
a) Information relating to the examination, evaluation, comparison, and post qualification of
bids, and recommendation of contract award, shall not be disclosed to bidders or any
Seal & Signature of the Auth. Sign.
Page 50 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
other persons not officially concerned with such process until publication of the Contract
award.
b) Any attempt by a bidder to influence the tendering authority or other officials in the
examination, evaluation, comparison, and post qualification of the bids or Contract
award decisions may result in the rejection of his bid.
c) From the time of bid opening to the time of Contract award, if any bidder wishes to
contact the tendering authority on any matter related to the bidding process, he is
allowed to do so in writing.
20. Clarification of Bids
a) To assist in the examination, evaluation, comparison and post qualification of the bids,
the tendering authority may, at its discretion, ask any bidder for a clarification of his bid.
The tendering authority’s request for clarification and the response shall be either in
writing or by uploading the details on the websites mentioned in the NIT.
b) Any clarification submitted by a bidder with regard to his bid that is not in response to a
request by the tendering authority shall not be considered.
c) No change in the prices or substance of the bid shall be sought, offered, or permitted,
except to confirm the correction of arithmetic errors discovered by the tendering
authority in the evaluation of the Commercial/ Financial Bids.
21. Evaluation of Technical Bids
a) The technical evaluation shall be completed by the designated Procurement Committee
as early as possible after opening of technical bids.
b) After approval of the technical evaluation by tendering authority, the firms which
qualified in the technical evaluation shall be informed in writing or by uploading the
details on the websites mentioned in the NIT about the date, time and place of opening
of their financial bids.
c) The firms who could not qualify in technical evaluation will be informed about this fact
and their EMD will be refunded after completion of the tender process i.e. award of the
contract to the best/ successful bidder.
22. Evaluation of Financial Bids
a) The financial bids/ cover of bidders who qualify in technical evaluation shall be opened
online at the notified time, date and place by the members of the designated
Procurement Committee in the presence of the bidders or their representatives who
choose to be present. Alternatively, the bidders may also view the financial bid opening
status/ process online at eProc website.
b) The Process of opening of financial bids/covers shall be similar to that of technical bids.
Seal & Signature of the Auth. Sign.
Page 51 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
c) The names of the firms, the rates given by them, shall be read out and recorded in
tender opening register.
d) To evaluate a bid, the tendering authority shall consider the following: i.
the bid price as quoted in accordance with bidding document.
ii. price adjustment for correction of arithmetic errors in accordance with bidding
document.
e) The tendering authority’s evaluation of a bid will exclude and not take into account i.
in the case of goods, Rajasthan VAT but Central Sales Tax shall be
considered for purposes of comparison; and
f) The evaluation shall include all costs and all taxes and duties applicable to the bidder as
per law of the Central/ State Government/ Local Authorities. Treatment of CenVAT/ VAT
etc. would, however, be as per Clause “ Comparison of Rates of firms outside and those
in Rajasthan “ below.
23. Clarification of Bids
a) To assist in the examination, evaluation, comparison and post qualification of the bids,
the tendering authority may, at its discretion, ask any bidder for a clarification of his bid.
The tendering authority’s request for clarification and the response shall be either in
writing or by uploading the details on the websites mentioned in the NIT.
b) Any clarification submitted by a bidder with regard to his bid that is not in response to a
request by the tendering authority shall not be considered.
c) No change in the prices or substance of the bid shall be sought, offered, or permitted,
except to confirm the correction of arithmetic errors discovered by the tendering
authority in the evaluation of the Commercial/ Financial Bids.
24. Correction of Arithmetic Errors
Provided that the Bid is substantially responsive, the competent Procurement Committee
shall correct arithmetical errors on the following basis: i. if there is a discrepancy between the unit price and the total price that is obtained
by multiplying the unit price and quantity, the unit price shall prevail and the total
price shall be corrected, unless in the opinion of the tendering authority there is an
obvious misplacement of the decimal point in the unit price, in which case the total
price as quoted shall govern and the unit price shall be corrected;
ii. if there is an error in a total corresponding to the addition or subtraction of
subtotals, the subtotals shall prevail and the total shall be corrected; and
Seal & Signature of the Auth. Sign.
Page 52 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
iii. if there is a discrepancy between words and figures, the amount in words shall
prevail, unless the amount expressed in words is related to an arithmetic error, in
which case the amount in figures shall prevail subject to (i) and (ii) above.
25. Comparison of Rates of firms outside and those in Rajasthan
While tabulating the bids of those firms which are not entitled to price preference, the
element of Rajasthan VAT shall be excluded from the rates quoted by the firms of
Rajasthan and the element of Central VAT shall be included in the rates of firms outside
Rajasthan. In such case, if the price of any commodity being offered for sale by firms in
Rajasthan is the same or lower (excluding element of Rajasthan Sales Tax) than the price
of firm outside Rajasthan (including element of Central Sales Tax), the commodity shall
be purchased from the firm in Rajasthan.
26. Margin of Preference/ Price Preference
No margin of preference/ price preference shall be given to the goods produced or
manufactured by Industries of Rajasthan over goods produced or manufactured by
Industries outside Rajasthan.
27. Negotiations
a) As a general rule, negotiations after opening of financial bids would be discouraged.
However, negotiations may be undertaken in exceptional circumstances, such as: i. when ring prices have been quoted.
ii. When the quoted rates have wide variations and are much higher than the market
rates prevailing at the time of opening of bids.
b) Negotiations shall not make original offer of the bidder ineffective.
c) Negotiations shall be conducted with the best value bidder only and by information given
in writing with a minimum period of 3 days (in case of a local bidder) and 7 days (in case
of an outstation bidder) shall be given for response in writing and in sealed cover. In
case of urgency, the tender sanctioning authority may reduce the notice period for
negotiations provided the bidder receives the information regarding holding negotiations.
d) In case the best value bidder does not reduce his rates in response to negotiations or
the rates so reduced are still considered to be higher, the tender sanctioning PC may
decide to make a written counter offer to the best value bidder. If the best value bidder
does not accept the counter offer given by the PC, the PC may recommend rejecting the
bid or may repeat the process to make the same counter offer to second best value
bidder and so on to third, fourth best value bidder, etc. till a bidder accepts it.
28. Comparison of bids and determination of the best value bid
Seal & Signature of the Auth. Sign.
Page 53 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
The tendering authority shall compare responsive bids of all eligible bidders to determine
the best value bid, in accordance with the evaluation criteria given in this RFP.
29. Tendering authority’s Right to Accept/ Reject any or all of the Bids
The tendering authority reserves the right to accept or reject any Bid, and to annul the
bidding process and reject all Bids at any time prior to Contract award, without thereby
incurring any liability to the Bidders.
30. Right to vary Quantities
a) At the time the Contract is awarded, the quantity of Goods and Related Services
originally specified in the bidding document may be increased or decreased, provided
this change does not exceed the limits/ ceilings of minimum and maximum quantity, if
any, indicated in the bidding document, and without any change in the unit prices or
other terms and conditions of the bid and the bidding document.
b) The tendering authority reserves the right to increase the quantity of goods and scope of
services originally specified in the bidding document by 25% and without any change in
the unit prices or other terms and conditions of the bid and the bidding document.
c) Repeat orders may also be placed with the consent of the contractor/ supplier on the
rates and conditions given in the bidding document provided that the repeat orders are
up to 50% of the quantity originally purchased and the period is not more than one
month from the date of expiry of last supply (i.e., delivery) and that the original order
was given after inviting open tenders/ bids. The delivery/ completion period will also be
proportionately increased.
d) If the tendering authority does not purchase any of the tendered articles or purchases
less than the quantity/ indicated in the tender form, the bidder shall not be entitled to
claim any compensation.
31. Disqualification
Tendering authority may at its sole discretion and at any time during the processing of
bids, disqualify any bidder if the bidder: a) Has not submitted the bid in accordance with the bidding document.
b) Has submitted bid without submitting the prescribed Tender Fee, RISL Processing
Fee, EMD or the Bidder's authorisation certificate/ Power of Attorney.
c) Has imposed conditions in his bid.
d) During validity of the bid or its extended period, if any, increases his quoted prices.
e) Has made misleading or false representations in the forms, statements and
attachments submitted in proof of the eligibility requirements.
f) Has failed to provide clarifications related thereto, when sought.
Seal & Signature of the Auth. Sign.
Page 54 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
g) Has submitted more than one bid. This will cause disqualification of all bids
submitted by such bidders including forfeiture of the EMD.
h) Is found to canvass, influence or attempt to influence in any manner for the
qualification or selection process, including without limitation, by offering bribes or
other illegal gratification.
32. Acceptance of the Tender / Bid and Notification of Award
a) Prior to the expiration of the period of bid validity, the tendering authority shall notify the
successful Bidder, in writing, that its bid has been accepted.
b) The tendering authority shall award the Contract to the Bidder whose proposal/ bid has
been determined to be the best value bid.
c) Decision on bids shall be taken within original validity period of offers. If the decision on
acceptance or rejection of a bid cannot be taken within the original bid validity period
due to unavoidable circumstances, all the bidders shall be requested to extend validity
period of their bids up to a specified date.
d) As soon as a bid is accepted by the tendering authority, its written intimation would be
sent to the concerned bidder. If the issuance of formal Work Order is likely to take time,
a Letter of Intent (LOI) may be sent in the meanwhile. In the same intimation the bidder
may be asked to execute an agreement in prescribed format on a non-judicial stamp of
prescribed value and deposit the amount of prescribed performance security deposit
within 15 days from the date of issue of acceptance.
e) The acceptance of an offer is complete as soon as the letter of communication is posted
to the correct address of the bidder.
f) The acceptance of the bid shall also be placed on website of ACB and RISL for general
information to all.
g) The EMD of the bidders whose bids could not be accepted shall be refunded soon after
the agreement with the successful bidder is executed and his performance security
deposit is obtained. Until a formal Contract is prepared and executed, the notification of
award shall constitute a binding Contract.
33. Signing of Contract
a) Promptly after notification of award, the tendering authority shall send to the successful
Bidders the Contract Agreement including “Special Conditions of Contract.
b) Within fifteen (15) days of receipt of the Letter of Intent from the tendering authority, the
successful Bidders shall sign, date, and return the Contract Agreement to the tendering
authority.
34. Performance Security Deposit (PSD)
Seal & Signature of the Auth. Sign.
Page 55 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
a) Within fifteen (15) days of the receipt of notification of award from the tendering
authority, the successful Bidder shall furnish the Performance Security Deposit (PSD)
@5% of the total agreed/ordered project value.
b) Failure of the successful bidder to submit the aforementioned PSD or sign the Contract
Agreement shall constitute sufficient grounds for the annulment (cancellation/
termination) of the award and forfeiture of the EMD. In that event the tendering authority
may award the Contract to the next best value bidder whose offer is valid and
substantially responsive and is determined by the tendering authority to be qualified to
perform the Contract satisfactorily.
35. Reservation of Rights
To take care of unexpected circumstances, RISL reserves the rights for the following: a) Extend the Closing Date for submission of the bid proposals.
b) Amend the bidding requirements at any time prior to the closing date, with the
amendment being notified to prospective bidders and on the respective websites.
c) Allow a bidder to change its technical proposal if the same opportunity is given to all
bidders but before the opening of financial bids.
d) To accept any bid not necessarily the lowest, reject any bid without assigning any
reasons and accept bid for all or anyone or more of the articles/services for which bid
has been invited or distribute items of stores/services to more than one bidder.
e) Terminate or abandon the bidding procedure or the entire project whether before or after
the receipt of bid proposals.
f) Seek the advice of external consultants to assist RISL in the evaluation or review of
proposals.
g) Make enquiries of any person, company or organization to ascertain information
regarding the bidder and its proposal.
h) Reproduce for the purposes of the procedure the whole or any portion of the proposal
despite any copyright or other intellectual property right that may subsist in the proposal.
36. Monitoring of Contract
a) An officer or a committee of officers named Contract Monitoring Committee (CMC) may
be nominated by tendering authority to monitor the progress of the contract during its
delivery period.
b) During the delivery period the CMC shall keep a watch on the progress of the contract
and shall ensure that quantity of goods and service delivery is in proportion to the total
delivery period given, if it is a severable contract, in which the delivery of the goods and
service is to be obtained continuously or is batched. If the entire quantity of goods and
Seal & Signature of the Auth. Sign.
Page 56 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
service is to be delivered in the form of completed work or entire quantity of goods and
service is to be delivered in the form of completed work or entire contract like fabrication
work, the process of completion of work may be watched and inspections of the
selected bidders premises where the work is being completed, may be inspected.
c) If delay in delivery of goods and service is observed a performance notice would be
given to the selected bidder to speed up the delivery.
d) Any change in the constitution of the firm, etc. shall be notified forth with by the
contractor in writing to the tendering authority and such change shall not relieve any
former member of the firm, etc., from any liability under the contract.
e) No new partner/ partners shall be accepted in the firm by the selected bidder in respect
of the contract unless he/ they agree to abide by all its terms, conditions and deposits
with the tendering authority through a written agreement to this effect. The bidder’s
receipt for acknowledgement or that of any partners subsequently accepted as above
shall bind all of them and will be sufficient discharge for any of the purpose of the
contract.
f) The selected bidder shall not assign or sub-let his contract or any substantial part
thereof to any other agency without the permission of tendering authority.
Seal & Signature of the Auth. Sign.
Page 57 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
6.
TERMS AND CONDITIONS, OF TENDER & CONTRACT
Definitions
For the purpose of clarity, the following words and expressions shall have the meanings hereby
assigned to them: a) “Contract” means the Agreement entered into between the Purchaser and the successful/
selected bidder, together with the Contract Documents referred to therein, including all
attachments, appendices, and all documents incorporated by reference therein.
b) “Contract Documents” means the documents listed in the Agreement, including any
amendments thereto.
c) “Contract Price” means the price payable to the successful/ selected bidder as specified in
the Agreement, subject to such additions and adjustments thereto or deductions there from,
as may be made pursuant to the Contract.
d) “Day” means a calendar day.
e) “Delivery” means the transfer of the Goods from the successful/ selected bidder to the
Purchaser in accordance with the terms and conditions set forth in the Contract.
f)
“Completion” means the fulfilment of the related services by the successful/ selected bidder
in accordance with the terms and conditions set forth in the Contract.
g) “Goods” means all of the commodities, raw material, machinery and equipment, and/or
other materials that the successful/ selected bidder is required to supply to the Purchaser
under the Contract.
h) “Purchaser” means the entity purchasing the Goods and related services, as specified in the
bidding document.
i)
“Related Services” means the services incidental to the supply of the goods, such as
insurance, installation, training and initial maintenance and other similar obligations of the
successful/ selected bidder under the Contract.
j)
“Subcontractor” means any natural person, private or government entity, or a combination
of the above, including its legal successors or permitted assigns, to whom any part of the
Goods to be supplied or execution of any part of the related services is subcontracted by
the successful/ selected bidder.
k) “Supplier/ Successful or Selected bidder” means the natural person, private or government
entity, or a combination of the above, whose bid to perform the Contract has been accepted
by the Purchaser and is named as such in the Agreement, and includes the legal
successors or permitted assigns of the successful/ selected bidder.
l)
“The Site,” where applicable, means the designated project place(s) named in the bidding
document.
Seal & Signature of the Auth. Sign.
Page 58 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
A) General Conditions of the Bid
1) Income Tax and VAT Registration and VAT Clearance Certificate
No Dealer who does not hold a valid Permanent Account Number (PAN)/ Tax Indentification
Number (TIN) from Income Tax department, GoI and who is not registered under the Sales
Tax Act prevalent in the State where his business is located shall bid. The VAT Registration
Number should be quoted and a VAT clearance certificate from the Commercial Taxes
Officer of the Circle concerned valid on the date of submission of bid shall be submitted
without which the bid is liable to rejection. The bidder quoting Rajasthan VAT should have
valid VAT registration in the state of Rajasthan and he should mention the same VAT
registration number in the bid document.
2) Contract Documents
Subject to the order of precedence set forth in the Agreement, all documents forming the
Contract (and all parts thereof) are intended to be correlative, complementary, and mutually
explanatory.
3) Interpretation
a) If the context so requires it, singular means plural and vice versa.
b) Entire Agreement: The Contract constitutes the entire agreement between the
Purchaser and the Supplier/ selected bidder and supersedes all communications,
negotiations and agreements (whether written or oral) of parties with respect thereto
made prior to the date of Contract.
c) Amendment: No amendment or other variation of the Contract shall be valid unless it is
in writing, is dated, expressly refers to the Contract, and is signed by a duly authorized
representative of each party thereto.
d) Non-waiver: Subject to the condition (f) 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, neither shall any waiver by either party of any
breach of Contract operate as waiver of any subsequent or continuing breach of
Contract.
e) Any waiver of a party’s rights, powers, or remedies under the Contract must be in
writing, 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.
f) 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.
Seal & Signature of the Auth. Sign.
Page 59 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
4) Language
a) The Contract as well as all correspondence and documents relating to the Contract
exchanged by the successful/ selected bidder and the Purchaser, shall be written in
English language only or as specified in the special conditions of the contract. .
Supporting documents and printed literature that are part of the Contract may be in
another language provided they are accompanied by an accurate translation of the
relevant passages in the language specified in the special conditions of the contract, in
which case, for purposes of interpretation of the Contract, this translation shall govern.
b) The successful/ selected bidder shall bear all costs of translation to the governing
language and all risks of the accuracy of such translation.
5) Eligible Goods and Related Services
a) For purposes of this Clause, the term “goods” includes commodities, raw material,
machinery, equipment, and industrial plants; and “related services” includes services
such
as
insurance,
transportation,
supply,
installation,
integration,
testing,
commissioning, training, and initial maintenance.
b) Bids for articles/ goods marked in the bill of material should be the ones which are
produced in volume and are used by a large number of users in India/ abroad should be
encouraged. All products quoted by the successful/ selected bidder must be associated
with specific make and model numbers, item code and names and with printed literature
describing configuration and functionality. Any deviation from the printed specifications
should be clearly mentioned in the offer document by the bidder/ supplier.
c) The OEM/ Vendor of the quoted product must have its own registered spares depot in
India having adequate inventory of the equipment being quoted for providing the
necessary spares within next business day or maximum 30 hours.
d) The OEM/ Vendor of the quoted product should also have its direct representation in
India in terms of registered office for at least past 3 years. The presence through any
Distribution/ System Integration partner agreement will not be accepted.
e) Bidder must quote products in accordance with above clause “Eligible goods and related
services”.
f) The OEM/ Vendor of the quoted product whose equipments are being quoted shall have
Technical Support/ Assistance Center to provide 24x7 support over Toll Free numbers
as well as web-based support.
6) Notices
a) Any Notice given by one party to the other pursuant to the Contract shall be in writing to
the address specified in the contract. The term “in writing” means communicated in
written form with proof of dispatch and receipt.
Seal & Signature of the Auth. Sign.
Page 60 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
b) A Notice shall be effective when delivered or on the Notice’s effective date, whichever is
later.
7) Governing Law
The Contract shall be governed by and interpreted in accordance with the laws of the
Rajasthan State/ the Country (India), unless otherwise specified in the contract.
8) Scope of Supply
a) Subject to the provisions in the bidding document and contract, the goods and related
services to be supplied shall be as specified in the bidding document.
b) Unless otherwise stipulated in the Contract, the scope of supply shall include all such
items not specifically mentioned in the Contract but that can be reasonably inferred from
the Contract as being required for attaining delivery and completion of the goods and
related services as if such items were expressly mentioned in the Contract.
c) The bidder shall not quote and supply and hardware/ software that is likely to be
declared as End of Sale in next 6 months and End of Service/ Support for a period of
3 Years from the last date of bid submission. OEMs are required to mention this in
the MAF for all the quoted hardware/ software. If any of the hardware/ software is
found to be declared as End of Sale/ Service/ Support, then the bidder shall replace
all such hardware/ software with the latest ones having equivalent or higher
specifications without any financial obligation to the purchaser.
9) Delivery & Installation
a) Subject to the conditions of the contract, the delivery of the goods and completion of the
related services shall be in accordance with the delivery and completion schedule
specified in the bidding document. The details of supply/ shipping and other documents
to be furnished by the successful/ selected bidder are specified in the bidding document
and/ or contract.
b) The Contract for the supply can be repudiated at any time by the Purchase Officer, if the
supplies are not made to his satisfaction after giving an opportunity to the bidder of
being heard and recording the reasons for repudiation.
c) The supplier / selected bidder shall arrange to supply, install and commission the
ordered materials/ system as per specifications within the specified delivery/ completion
period at various departments and/ or their offices/ locations mentioned in the PO/WO .
d) Shifting the place of Installation: The user will be free to shift the place of installation
within the same city /town/ district/ division. The successful/ selected bidder shall
provide all assistance, except transportation, in shifting of the equipment. However, if
the city/ town is changed, additional charges of assistance in shifting and providing
maintenance services for remaining period would be decided mutually.
Seal & Signature of the Auth. Sign.
Page 61 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
10) Supplier’s/ Selected Bidder’s Responsibilities
The Supplier/ Selected Bidder shall supply all the goods and related services included in the
scope of supply in accordance with the provisions of bidding document and/ or contract.
11) Purchaser’s Responsibilities
a) Whenever the supply of goods and related services requires that the Supplier/ selected
Bidder obtain permits, approvals, and import and other licenses from local public
authorities, the Purchaser shall, if so required by the Supplier/ Selected Bidder, make its
best effort to assist the Supplier/ Selected Bidder in complying with such requirements in
a timely and expeditious manner.
b) The Purchaser shall pay all costs involved in the performance of its responsibilities, in
accordance with the general and special conditions of the contract.
12) Contract Price
a) The Contract Price shall be paid as specified in the contract subject to any additions and
adjustments thereto, or deductions there from, as may be made pursuant to the
Contract.
b) Prices charged by the Supplier/ Selected Bidder for the Goods delivered and the
Related Services performed under the Contract shall not vary from the prices quoted by
the Supplier/ Selected Bidder in its bid, with the exception of any price adjustments
authorized in the special conditions of the contract.
13) Recoveries from Supplier/ Selected Bidder
a) Recovery of liquidated damages, short supply, breakage, rejected articles shall be made
ordinarily from bills.
b) The Purchase Officer shall withhold amount to the extent of short supply, broken/
damaged or for rejected articles unless these are replaced satisfactorily. In case of
failure to withhold the amount, it shall be recovered from his dues and performance
security deposit available with RISL.
c) The balance, if any, shall be demanded from the Supplier/ Selected Bidder and when
recovery is not possible, the Purchase Officer shall take recourse to law in force.
14) Taxes & Duties
a) The income tax, service tax, value added tax, etc., if applicable, shall be deducted at
source from the payment to the Supplier/ Selected Bidder as per the law in force at the
time of execution of contract.
b) The entry tax, if applicable shall be deducted at source and deposited in the government
treasury in proper revenue receipt head of account.
Seal & Signature of the Auth. Sign.
Page 62 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
c) For goods supplied from outside India, the successful / selected bidder shall be entirely
responsible for all taxes, stamp duties, license fees, and other such levies imposed
outside the country.
d) For goods supplied from within India, the successful/ selected bidder shall be entirely
responsible for all taxes, duties, license fees, etc., incurred until delivery of the
contracted Goods to the Purchaser.
e) Revision in VAT and Service Tax shall be on account of the tendering authority if it has
been asked for separately in the financial bid and is not taken into account for the
purpose of comparison of bids. If, however, they have not been asked for separately,
any benefit or additional cost will be on account of the bidder. Revision of any other tax
or duty shall be on account of the bidder.
f) If any tax exemptions, reductions, allowances or privileges may be available to the
successful/ selected bidder in India, the Purchaser shall use its best efforts to enable the
successful /selcted bidder to benefit from any such tax savings to the maximum
allowable extent.
15) Performance Security Deposit (PSD)
a) In case of successful/ selected bidder, the EMD will be adjusted in arriving at the
amount of the PSD.
b) The successful / selected bidder shall, within fifteen (15) days of the notification of
Contract award, provide a PSD 5% of th etotal agreed / ordered project value for the
due performance of the Contract in the amounts and currencies specified in the work
order. .
c) The proceeds of the PSD shall be payable to the Purchaser as compensation for any
loss resulting from the successful / selected bidder failure to complete its obligations
under the Contract.
d) Form of PSD: PSD in the form of cash will not be accepted. It may be deposited in the
form of Bank Draft or Banker’s Cheque/ Bank Guarantee (Unconditional & Irrevocable)
in favour of “Managing Director, RajCOMP Info Services Limited” payable at “Jaipur”.
The concerned Procurement Committee may also permit to accept full amount or part of
PSD in the form of a Bank Guarantee ( Unconditional & Irrevocable) in case the amount
of PSD exceeds Ruppees 10 Lacs. The other form of security money shall be Postoffice Savings Bank Pass Book duly pledged or National Savings Certificates, Defence
Savings Certificates. Kisan Vikas Patras, or any other script/ instrument under National
Savings Schemes for promotion of small savings, if the same can be pledged. These
certificates shall be accepted at surrender value. The competent Purchase Committee
Seal & Signature of the Auth. Sign.
Page 63 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
may permit to deposit Bank Guarantee in part or full if the amount of PSD exceeds
Rupees 10 Lacs.
e) Refund of PSD: The PSD shall be refunded within one month from the successful
completion of the assignment as per the work order and/ or expiry of the term of the
contract.
f) Forfeiture of PSD: PSD shall be forfeited in the following cases: i. When any terms and condition of the contract is breached.
ii. When the Supplier/ selected Bidder fail to commence supply or stops making the
supplies or fail to provide deliverables after partially executing the purchase/ work
order.
iii. To adjust any dues against the firm from any other contract with RISL.
g) No interest will be paid by RISL on the amount of EMD and PSD.
h) Proper notice will be given to the Supplier/ selected Bidder with reasonable time before
EMD/ PSD is forfeited.
i)
Forfeiture of EMD/ PSD shall be without prejudice to any other right of RISL to claim any
damages as admissible under the law as well as to take such action against the
Supplier/ Selected Bidder such as severing future business relation or black listing, etc.
16) Copyright
a) The copyright in all drawings, source code design documents, and other materials
containing data and information furnished to the Purchaser by the Selected Bidder
herein shall remain vested in the Purchaser, or, if they are furnished to the Purchaser
directly or through the Selected Bidder by any third party, including suppliers of
materials, the copyright in such materials shall remain vested in such third party.
17) Confidential Information
a) The Purchaser and the Supplier/ Selected Bidder shall keep confidential and shall not,
without the written consent of the other party hereto, divulge to any third party any
drawings, documents, data, or other information furnished directly or indirectly by the
other party hereto in connection with the Contract, whether such information has been
furnished prior to, during or following completion or termination of the Contract.
Seal & Signature of the Auth. Sign.
Page 64 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
b) The Supplier/ Selected Bidder may furnish to its Subcontractor, if permitted, such
documents, data, and other information it receives from the Purchaser to the extent
required for the Subcontractor to perform its work under the Contract, in which event the
Supplier/ Selected Bidder shall obtain from such Subcontractor an undertaking of
confidentiality similar to that imposed on the Supplier/ Selected Bidder.
c) The Purchaser shall not use such documents, data, and other information received from
the Supplier/ Selected Bidder for any purposes unrelated to the Contract. Similarly, the
Supplier/ Bidder shall not use such documents, data, and other information received
from the Purchaser for any purpose other than the design, procurement, or other work
and services required for the performance of the Contract.
d) The obligation of a party under sub-clauses above, however, shall not apply to
information that: i. the Purchaser or Supplier/ Selected Bidder need to share with other institutions
participating in the Contract;
ii. now or hereafter enters the public domain through no fault of that party;
iii. can be proven to have been possessed by that party at the time of disclosure and
which was not previously obtained, directly or indirectly, from the other party; or
iv. otherwise lawfully becomes available to that party from a third party that has no
obligation of confidentiality.
e) The above provisions shall not in any way modify any undertaking of confidentiality
given by either of the parties hereto prior to the date of the Contract in respect of the
supply or any part thereof.
f) The provisions of this clause shall survive completion or termination, for whatever
reason, of the Contract.
18) Sub-contracting
a) Unless otherwise specified in the Contract, the bidder shall not assign or sub-let his
contract or any substantial part thereof to any other agency without the permission of
Purchaser/ Tendering Authority
b) If permitted, the selected bidder shall notify the Purchaser, in writing, of all subcontracts
awarded under the Contract, if not already specified in the Bid. Subcontracting shall in
no event relieve the Supplier/ Selected Bidder from any of its obligations, duties,
responsibilities, or liability under the Contract.
c) Subcontracts shall comply with the provisions of bidding document and/ or contract.
19) Specifications and Standards
a) All articles supplied shall strictly conform to the specifications, trademark laid down in
the tender form and wherever articles have been required according to ISI/ ISO/ other
Seal & Signature of the Auth. Sign.
Page 65 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
applicable specifications/ certifications/ standards, those articles should conform strictly
to those specifications/ certifications/ standards. The supply shall be of best quality and
description. The decision of the competent authority/ purchase committee whether the
articles supplied conforms to the specifications shall be final and binding on the supplier/
selected bidder.
b) Technical Specifications and Drawings
i. The Supplier/ Selected Bidder shall ensure that the goods and related services
comply with the technical specifications and other provisions of the Contract.
ii. The Supplier/ Selected Bidder shall be entitled to disclaim responsibility for any
design, data, drawing, specification or other document, or any modification thereof
provided or designed by or on behalf of the Purchaser, by giving a notice of such
disclaimer to the Purchaser.
iii. The goods and related services supplied under this Contract shall conform to the
standards mentioned in bidding document and, when no applicable standard is
mentioned, the standard shall be equivalent or superior to the official standards
whose application is appropriate to the country of origin of the Goods.
c) Wherever references are made in the Contract to codes and standards in accordance
with which it shall be executed, the edition or the revised version of such codes and
standards shall be those specified in the bidding document. During Contract execution,
any changes in any such codes and standards shall be applied only after approval by
the Purchaser and shall be treated in accordance with the general conditions of the
contract.
20) Packing and Documents
a) The Supplier/ Selected Bidder shall provide such packing of the Goods as is required to
prevent their damage or deterioration during transit to their final destination, as indicated
in the Contract. During transit, the packing shall be sufficient to withstand, without
limitation, rough handling and exposure to extreme temperatures, salt and precipitation,
and open storage. Packing case size and weights shall take into consideration, where
appropriate, the remoteness of the final destination of the Goods and the absence of
heavy handling facilities at all points in transit.
b) The packing, marking, and documentation within and outside the packages shall comply
strictly with such special requirements as shall be expressly provided for in the Contract,
including additional requirements, if any, specified in the contract, and in any other
instructions ordered by the Purchaser.
Seal & Signature of the Auth. Sign.
Page 66 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
21) Insurance
a) The Goods supplied under the Contract shall be fully insured against loss by theft,
destruction or damage incidental to manufacture or acquisition, transportation, storage,
fire, flood, under exposure to weather and delivery at the designated project locations, in
accordance with the applicable terms. The insurance charges will be borne by the
supplier and Purchaser will not be required to pay such charges if incurred.
b) The goods will be delivered at the FOR destination in perfect condition.
22) Transportation
a) The supplier/ selected bidder shall be responsible for the proper packing so as to avoid
damage under normal conditions of transport by sea, rail and road or air and delivery of
the material in the good condition to the consignee at destination. In the event of any
loss, damage, breakage or leakage or any shortage the bidder shall be liable to make
good such loss and shortage found at the checking/ inspection of the material by the
consignee. No extra cost on such account shall be admissible.
b) All goods must be sent freight paid through Railways or goods transport. If goods are
sent freight to pay, the freight together with departmental charge @5% of the freight will
be recovered from the supplier’s/ selected bidder’s bill.
23) Inspection
a) The Purchase Officer or his duly authorized representative shall at all reasonable time
have access to the supplier’s/ selected bidder’s premises and shall have the power at all
reasonable time to inspect and examine the materials and workmanship of the goods/
equipment/ machineries during manufacturing process or afterwards as may be
decided.
b) The supplier/ selected bidder shall furnish complete address of the premises of his
factory, office, go-down and workshop where inspection can be made together with
name and address of the person who is to be contacted for the purpose. In case of
those dealers who have newly entered in business, a letter of introduction from their
bankers will be necessary.
c) After successful inspection, it will be supplier’s/ selected bidder’s responsibility to
dispatch and install the equipment at respective locations without any financial liability to
the Purchaser. However, supplies when received at respective locations shall be subject
to inspection to ensure whether they conform to the specification.
24) Samples
a) When notified by the Purchaser to the supplier/ bidder/ selected bidder, Bids for articles/
goods mentioned in the BoM shall be accompanied by four sets of samples of the articles
quoted properly packed. Such samples if submitted personally will be received in the office.
Seal & Signature of the Auth. Sign.
Page 67 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
A receipt will be given for each sample by the officer receiving the samples. Samples if sent
by train, etc., should be despatched freight paid and the R/R or G.R. should be sent under a
separate registered cover. Samples for catering/ food items should be given in a plastic box
or in polythene bags at the cost of the bidder.
b) Each sample shall be marked suitably either by written on the sample or on a slip of
durable paper securely fastened to the sample, the name of the bidder and serial number of
the item, of which it is a sample in the schedule.
c) Approved samples would be retained free of cost upto the period of six months after the
expiry of the contract. RISL shall not be responsible for any damage, wear and tear or loss
during testing, examination, etc., during the period these samples are retained.
The Samples shall be collected by the supplier/ bidder/ selected bidder on the expiry of
stipulated period. RISL shall in no way make arrangements to return the samples. The
samples uncollected within 9 months after expiry of contract shall be forfeited by RISL and
no claim for their cost, etc., shall be entertained.
d) Samples not approved shall be collected by the unsuccessful bidder. RISL will not be
responsible for any damage, wear and tear, or loss during testing, examination, etc., during
the period these samples are retained. The uncollected samples shall be forfeited and no
claim for their cost, etc., shall be entertained.
e) Supplies when received may be subject to inspection to ensure whether they conform to
the specifications or with the approved samples. Where necessary or prescribed or
practical, tests may be carried out in Government laboratories, reputed testing house like
STQC (ETDC) and the like and the supplies will be accepted only when the articles conform
to the standard of prescribed specifications as a result of such tests.
f) The selected bidder shall at its own expense and at no cost to the Purchaser carry out
all such tests and/ or inspections of the Goods and Related Services as are specified in the
bidding document.
25) Drawl of Samples
In case of tests, wherever feasible, samples shall be drawn in four sets in the presence of
selected bidder or his authorised representative and properly sealed in their presence.
Once such set shall be given to them, one or two will be sent to the laboratories and/ or
testing house and the third or fourth will be retained in the office for reference and record.
26) Testing charges
Testing charges shall be borne by the RISL/ACB. In case, urgent testing is desired to be
arranged by the bidder or in case of test results showing that supplies are not upto the
prescribed standards or specifications, the testing charges shall be payable by the bidder.
Seal & Signature of the Auth. Sign.
Page 68 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
27) Rejection
a) Articles not approved during inspection or testing shall be rejected and will have to be
replaced by the selected
bidder at his own cost within the time fixed by the Purchase
Officer.
b) If, however, due to exigencies of RISL/ACB’s work, such replacement either in whole or
in part, is not considered feasible, the Purchase Officer after giving an opportunity to the
selected bidder of being heard shall for reasons to be recorded, deduct a suitable
amount from the approved rates. The deduction so made shall be final.
c) The rejected articles shall be removed by the selected bidder within 15 days of
intimation of rejection, after which Purchase Officer shall not be responsible for any loss,
shortage or damage and shall have the right to dispose of such articles as he thinks fit,
at the selected bidder’s risk and on his account.
28) Extension in Delivery Period and Liquidated Damages (LD)
a) Except as provided under clause “Force Majeure”, if the Supplier/ selected Bidder fails
to deliver any or all of the Goods or perform the Related Services within the period
specified in the Contract, the Purchaser may without prejudice to all its other remedies
under the Contract, deduct from the Contract Price, as liquidated damages, a sum
equivalent to the percentage specified in the conditions of the Contract Price for each
week or part thereof of delay until actual delivery or performance, up to a maximum
deduction of the percentage specified in the bidding document and/ or contract. Once
the maximum is reached, the Purchaser may terminate the Contract pursuant to clause
“Termination”.
b) The time specified for delivery in the tender form shall be deemed to be the essence of
the contract and the supplier/ selected bidder shall arrange goods supply and related
services within the specified period.
c) Delivery and installation/ completion period may be extended with or without liquidated
damages if the delay in the supply of goods or service is on account of hindrances
beyond the control of the supplier/ selected bidder.
i. The supplier/ selected bidder shall request in writing to the purchaser giving reasons
for extending the delivery period of service if he finds himself unable to complete the
supply of goods or service within the stipulated delivery period or is unable to
maintain prorate progress in the supply of goods or service delivery. This request
shall be submitted as soon as a hindrance in delivery of goods and service occurs or
within 15 days from such occurrence but before expiry of stipulated period of
completion of delivery of goods and service after which such request shall not be
entertained.
Seal & Signature of the Auth. Sign.
Page 69 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
ii. The purchaser shall examine the justification of causes of hindrance in the delivery
of goods and service and the period of delay occurred due to that and recommend
the competent authority on the period of extension which should be granted with or
without liquidated damages.
iii. Normally, extension in delivery period of goods and service in following
circumstances may be considered without liquidated damages:
a. When delay has occurred due to delay in supply of drawings, designs, plans etc.
if the RISL / ACB was required to supply them to the supplier of goods or service
provider as per terms of the contract.
b. When delay has occurred in supply of materials etc. if these were required to be
supplied to the supplier or service provider by the ACB/ RISL as per terms of the
contract.
iv. If the competent authority agrees to extend the delivery period/ schedule, an
amendment to the contract with suitable denial clauses and with or without
liquidated damages, as the case may be, shall be issued. The amendment letter
shall mention that no extra price or additional cost for any reason, what so ever
beyond the contracted cost shall be paid for the delayed supply of goods and
service.
v. It shall be at the discretion of the concerned authority to accept or not to accept the
supply of goods and/ or services rendered by the contractor after the expiry of the
stipulated delivery period, if no formal extension in delivery period has been applied
and granted. The competent authority shall have right to cancel the contract with
respect to undelivered goods and/ or service.
vi. If RISL / ACB are in need of the good and/ or service rendered after expiry of the
stipulated delivery period, it may accept the services and issue a letter of extension
in delivery period with usual liquidated damages and denial clauses to regularize the
transaction.
d) In case of extension in the delivery and/ or installation/ completion/ commissioning
period is granted with full liquidated damages, the recovery shall be made on the basis
of following percentages of value of goods and/ or service which the bidder has failed to
supply or complete : No.
Condition
a.
Delay up to one fourth period of the prescribed period of delivery,
successful installation and completion of work
2.5 %
b.
Delay exceeding one fourth but not exceeding half of the prescribed
5.0 %
Seal & Signature of the Auth. Sign.
LD %*
Page 70 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
period of delivery, successful installation and completion of work
c.
Delay exceeding half but not exceeding three fourth of the prescribed
period of delivery, successful installation and completion of work
7.5 %
d.
Delay exceeding three fourth of the prescribed period of delivery,
successful installation and completion of work
10.0 %
i. Fraction of a day in reckoning period of delay in supplies, successful installation and
completion of work shall be eliminated if it is less than half a day.
ii. The maximum amount of liquidated damages shall be 10%.
iii. The percentage refers to the payment due for the associated milestone.
iv. The goods and services mentioned in the clause along with the associated
deliverables and applicable cost reference for the LD calculations shall be in
accordance to the following table:
S.No
1.
2.
3.
4.
5.
Goods/Service
Deliverable
Cost reference in
Financial Bid for
calculation
of
LD %
System Study & Prepare SRS
Submission of SRS
Capex
respective
component
Table A4
of
Item
delivery
/
Commissioning
reports as applicable
(Component wise )
Capex
respective
component
Table A1
of
Item
delivery
/
Commissioning
of IT & Non IT infrastructure at
reports as applicable
8 Range offices
(Component wise )
Capex
respective
component
Table A2
of
Installation and Commissioning
Capex
respective
component
Table A3
of
Successful Installation and
Commissioning of IT & Non IT
infrastructure at ACB HQ
Installation and Commissioning
Item
delivery
/
Commissioning
of IT & Non IT infrastructure at
reports as applicable
35 Outpost Offices
(Component wise )
Application
software
deployment at RSDC
6.
System Integration & Go-Live
Seal & Signature of the Auth. Sign.
Deployment,
integration
RSDC and
acceptance
in
in
in
in
Capex
as
and mentioned in S1
UAT of Table A4
FAT Acceptance
Go- Live
& Capex
as
mentioned in S1
of Table A4
Page 71 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
29) Authenticity of Equipments
a) The selected bidder shall certify (as per Annexure-10) that the supplied goods are brand
new, genuine/ authentic, not refurbished, conform to the description and quality as
specified in this bidding document and are free from defects in material, workmanship
and service.
b) If during the contract period, the said goods be discovered counterfeit/ unauthentic or
not to conform to the description and quality aforesaid or have determined (and the
decision of the Purchase Officer in that behalf will be final and conclusive),
notwithstanding the fact that the purchaser may have inspected and/ or approved the
said goods, the purchaser will be entitled to reject the said goods or such portion thereof
as may be discovered not to conform to the said description and quality, on such
rejection the goods will be at the selected bidder’s risk and all the provisions relating to
rejection of goods etc., shall apply. The selected bidder shall, if so called upon to do,
replace the goods etc., or such portion thereof as is rejected by Purchase Officer,
otherwise the selected bidder shall pay such damage as may arise by the reason of the
breach of the condition herein contained. Nothing herein contained shall prejudice any
other right of the Purchase Officer in that behalf under this contract or otherwise.
c) Goods accepted by the purchaser in terms of the contract shall in no way dilute
purchaser’s right to reject the same later, if found deficient in terms of the this clause of
the contract.
30) Warranty
a) The bidder must supply all items with comprehensive on-site warranty valid for three
years after the goods, or any portion thereof as the case may be, have been delivered
to, installed and accepted at the final destination(s) indicated in the bidding document.
However, if delay of installation is more than a month’s time due to the reasons ascribed
to the bidder, the warranty shall start from the date of last successful installation of the
items covered under the PO.
b) The bidder shall submit a certificate/ undertaking from all the respective OEMs
mentioning the fact that the goods supplied are covered under comprehensive warranty
& support for the prescribed period.
c) The purchaser shall give a written notice to the selected bidder stating the nature of any
defect together with all available evidence thereof, promptly following the discovery
thereof. The purchaser shall afford all reasonable opportunity for the selected bidder to
inspect such defects. Upon receipt of such notice, the selected bidder shall
expeditiously cause to repair the defective goods or parts thereof or replace the
defective goods or parts thereof with brand new genuine/ authentic ones having similar
Seal & Signature of the Auth. Sign.
Page 72 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
or higher specifications from the respective OEM, at no cost to the Purchaser. Any
goods repaired or replaced by the selected bidder shall be delivered at the respective
location without any additional costs to the purchaser.
d) If having been notified, the selected bidder fails to remedy the defect within the period
specified, the purchaser may proceed to take within a reasonable period such remedial
action as may be necessary, in addition to other recourses available in terms and
conditions of the contract and bidding document.
e) During the warranty period, the bidder shall also be responsible to ensure adequate and
timely availability of spare parts needed for repairing the supplied goods.
f) The warranty on supplied software media, if any, should be at least 3 months.
31) Patent Indemnity
a) The supplier/ selected bidder shall, subject to the Purchaser’s compliance with subclause (b) below, indemnify and hold harmless the Purchaser and its employees and
officers from and against any and all suits, actions or administrative proceedings,
claims, demands, losses, damages, costs, and expenses of any nature, including
attorney’s fees and expenses, which the Purchaser may suffer as a result of any
infringement or alleged infringement of any patent, utility model, registered design,
trademark, copyright, or other intellectual property right registered or otherwise existing
at the date of the Contract by reason of: i. the installation of the Goods by the supplier/ selected bidder or the use of the Goods
in the country where the Site is located; and
ii. the sale in any country of the products produced by the Goods.
Such indemnity shall not cover any use of the Goods or any part thereof other than for
the purpose indicated by or to be reasonably inferred from the Contract, neither any
infringement resulting from the use of the Goods or any part thereof, or any products
produced thereby in association or combination with any other equipment, plant, or
materials not supplied by the supplier/ selected bidder, pursuant to the Contract.
b) If any proceedings are brought or any claim is made against the Purchaser arising out of
the matters referred to above, the Purchaser shall promptly give the supplier/ selected
bidder a notice thereof, and the supplier/ selected bidder 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.
c) If the supplier/ selected bidder fails to notify the Purchaser within thirty (30) 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.
Seal & Signature of the Auth. Sign.
Page 73 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
d) The Purchaser shall, at the supplier’s/ selected bidder’s request, afford all available
assistance to the supplier/ selected bidder in conducting such proceedings or claim, and
shall be reimbursed by the supplier/ selected bidder for all reasonable expenses
incurred in so doing.
e) The Purchaser shall indemnify and hold harmless the supplier/ selected bidder and its
employees, officers, and Subcontractors (if any) from and against any and all suits,
actions or administrative proceedings, claims, demands, losses, damages, costs, and
expenses of any nature, including attorney’s fees and expenses, which the supplier/
selected bidder may suffer as a result of any infringement or alleged infringement of any
patent, utility model, registered design, trademark, copyright, or other intellectual
property right registered or otherwise existing at the date of the Contract arising out of or
in connection with any design, data, drawing, specification, or other documents or
materials provided or designed by or on behalf of the Purchaser.
32) Limitation of Liability
Except in cases of gross negligence or wilful misconduct: a) neither party shall be liable to the other party 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/ selected bidder to pay
liquidated damages to the Purchaser; and
b) the aggregate liability of the supplier/ selected bidder to the Purchaser, whether under
the Contract, in tort, or otherwise, shall not exceed the amount specified in the Contract,
provided that this limitation shall not apply to the cost of repairing or replacing defective
equipment, or to any obligation of the supplier/ selected bidder to indemnify the
Purchaser with respect to patent infringement.
33) Change in Laws & Regulations
Unless otherwise specified in the Contract, if after the date of the Invitation for Bids, any
law, regulation, ordinance, order or bylaw having the force of law is enacted, promulgated,
abrogated, or changed in Rajasthan/ India, where the Site is located (which shall be
deemed to include (i) any change in interpretation or application by the competent
authorities, (ii) changes in taxes and levies) that subsequently affects the Delivery Date and/
or the Contract Price, then such Delivery Date and/ or Contract Price shall be
correspondingly increased or decreased, to the extent that the supplier/ selected bidder has
thereby been affected in the performance of any of its obligations under the Contract.
Notwithstanding the foregoing, such additional or reduced cost shall not be separately paid
or credited, if the same has already been accounted for in the price adjustment provisions
where applicable.
Seal & Signature of the Auth. Sign.
Page 74 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
34) Force Majeure
a) The supplier/ selected bidder shall not be liable for forfeiture of its PSD, LD, or
termination for default, if and to the extent that its delay in performance or other failure
to perform its obligations under the Contract is the result of an event of Force Majeure.
b) For purposes of this Clause, “Force Majeure” means an event or situation beyond the
control of the supplier/ selected bidder that is not foreseeable, is unavoidable, and its
origin is not due to negligence or lack of care on the part of the supplier/ selected bidder.
Such events may include, but not be limited to, acts of the Purchaser in its sovereign
capacity, wars or revolutions, fires, floods, epidemics, quarantine restrictions, and freight
embargoes.
c) If a Force Majeure situation arises, the supplier/ selected bidder shall promptly notify the
department in writing of such conditions and cause thereof within 15 days of occurrence
of such event. Unless otherwise directed by RISL, the supplier/ selected bidder shall
continue to perform its obligations under the contract as far as reasonably practical.
d) If the performance in whole or part or any obligation under the contract is prevented or
delayed by any reason of Force Majeure for a period exceeding 60 days, either party at
its option may terminate the contract without any financial repercussion on either side.
e) In case a Force Majeure situation occurs with the RISL, the RISL may take the case
with the supplier/ selected bidder on similar lines.
35) Change Orders and Contract Amendments
a) The Purchaser may at any time order the Supplier/ Bidder through Notice in
accordance with clause “Notices” above, to make changes within the general
scope of the Contract in any one or more of the following: i. drawings, designs, or specifications, where Goods to be furnished under the
Contract are to be specifically manufactured for the Purchaser;
ii. the method of shipment or packing;
iii. the place of delivery; and
iv. the Related Services to be provided by the Supplier.
b) If any such change causes an increase or decrease in the cost of, or the time
required for, the Supplier’s/ Bidder’s performance of any provisions under the
Contract, an equitable adjustment shall be made in the Contract Price or in the
Delivery and Completion Schedule, or both, and the Contract shall accordingly
should be amended. Any claims by the Supplier/ Bidder for adjustment under this
clause must be asserted within thirty (30) days from the date of the Supplier’s/
Bidder’s receipt of the Purchaser’s change order.
Seal & Signature of the Auth. Sign.
Page 75 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
c) Prices to be charged by the Supplier/ Bidder for any Related Services that might
be needed but which were not included in the Contract shall be agreed upon in
advance by the parties and shall not exceed the prevailing rates charged to other
parties by the Supplier/ Bidder for similar services.
36) Termination
a) Termination for Default
i. The tender sanctioning authority of RISL may, without prejudice to any other remedy
for breach of contract, by written notice of default sent to the supplier/ selected
bidder, terminate the contract in whole or in part: a. If the supplier/ selected bidder fails to deliver any or all quantities of the service
within the time period specified in the contract, or any extension thereof granted
by RISL; or
b. If the supplier/ selected bidder fails to perform any other obligation under the
contract within the specified period of delivery of service or any extension
granted thereof; or
c. If the supplier/ selected bidder, in the judgement of the Purchaser, is found to be
engaged in corrupt, fraudulent, collusive, or coercive practices in competing for
or in executing the contract.
d. If the supplier/ selected bidder commits breach of any condition of the contract.
ii. If RISL terminates the contract in whole or in part, amount of PSD may be forfeited.
iii. Before cancelling a contract and taking further action, advice of senior most finance
person available in the office and of legal adviser or legal assistant posted in the
office, if there is one, may be obtained.
b) Termination for Insolvency
RISL may at any time terminate the Contract by giving Notice to the supplier/ bidder, if
the supplier/ bidder become bankrupt or otherwise insolvent. In such event, termination
will be without compensation to the supplier/ bidder, provided that such termination will
not prejudice or affect any right of action or remedy that has accrued or will accrue
thereafter to RISL.
c) Termination for Convenience
i. RISL, by a Notice sent to the supplier/ selected bidder, may terminate the Contract,
in whole or in part, at any time for its convenience. The Notice of termination shall
specify that termination is for the Purchaser’s convenience, the extent to which
Seal & Signature of the Auth. Sign.
Page 76 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
performance of the supplier/ bidder under the Contract is terminated, and the date
upon which such termination becomes effective.
ii. Depending on merits of the case the supplier/ bidder may be appropriately
compensated on mutually agreed terms for the loss incurred by the contract if any
due to such termination.
iii. The Goods that are complete and ready for shipment within twenty-eight (28) days
after the supplier’s/ selected bidder’s receipt of the Notice of termination shall be
accepted by the Purchaser at the Contract terms and prices. For the remaining
Goods, the Purchaser may elect:
a. To have any portion completed and delivered at the Contract terms and prices;
and/or
b. To cancel the remainder and pay to the supplier/ selected bidder an agreed
amount for partially completed Goods and related services and for materials and
parts previously procured by the supplier/ selected bidder.
37) Settlement of Disputes
a) General: If any dispute arises between the supplier/ selected bidder and RISL during the
execution of a contract that should be amicably settled by mutual discussions. However,
if the dispute is not settled by mutual discussions, a written representation will be
obtained from the supplier/ selected bidder on the points of dispute. The representation
so received shall be examined by the concerned Procurement Committee which
sanctioned the tender. The Procurement Committee may take legal advice of a counsel
and then examine the representation. The supplier/ selected bidder will also be given an
opportunity of being heard. The Committee will take a decision on the representation
and convey it in writing to the supplier/ selected bidder.
b) Standing Committee for Settlement of Disputes: If a question, difference or objection
arises in connection with or out of the contract/ agreement or the meaning of operation
of any part, thereof or the rights, duties or liabilities of either party have not been settled
by mutual discussions or the decision of tender sanctioning Procurement Committee, it
shall be referred to the empowered standing committee for decision, if the amount of the
claim is more than Rs. 50,000/-. The standing committee shall consist of following
members of RISL and ACB.
c) Procedure for reference to the Standing Committee: The supplier/ selected bidder shall
present his representation to the Managing Director, RISL along with a fee equal to two
percent of the amount of dispute, not exceeding Rupees One Lac, within one month
from the date of communication of decision of the tender sanctioning Procurement
Committee. The officer-in-charge of the project who was responsible for taking delivery
Seal & Signature of the Auth. Sign.
Page 77 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
of the goods and/ or service from the supplier/ selected bidder shall prepare a reply of
representation and shall represent the RISL’s stand before the standing committee.
From the side of the supplier/ selected bidder, the claim case may be presented by
himself or through a lawyer. After hearing both the parties, the standing committee shall
announce its decision which shall be final and binding both on the supplier/ selected
bidder and RISL. The standing committee, if it so decides, may refer the matter to the
Board of Directors of RISL for further decision.
d) Legal Jurisdiction: All legal proceedings arising out of any dispute between both the
parties regarding a contract shall be settled by a competent court having jurisdiction
over the place, where agreement has been executed and by no other court, after
decision of the standing committee for settlement of disputes.
B) Payment Terms and Schedule
38) Terms of Payment
a) The supplier’s/ selected bidder’s request for payment shall be made to the ACB, GoR in
writing, accompanied by invoices describing, as appropriate, the goods delivered and
related services performed, and by the required documents submitted pursuant to
general conditions of the contract and upon fulfilment of all the obligations stipulated in
the Contract.
b) Subject to the performance as per SLA, Payments shall be made promptly by the ACB,
GoR, generally within sixty (60) days after submission of an invoice or request for
payment by the supplier/ bidder, and the Purchaser has accepted it.
c) The currency or currencies in which payments shall be made to the supplier/ selected
bidder under this Contract shall be Indian Rupees (INR) only.
d) All remittance charges will be borne by the supplier/ selected bidder.
e) In case of disputed items, the disputed amount shall be withheld and will be paid only
after settlement of the dispute.
f) Payment in case of those goods which need testing shall be made only when such tests
have been carried out, test results received conforming to the prescribed specification.
g) Advance Payments will not be made.
h) Payments to the selected bidder, after successful completion of the target milestones
(including specified project deliverables), would be made as under: -
Milestone
Deliverable (Reports/
Documents & Infra)
Payment Terms
Payment Schedule
Perform System
Study & SRS (Para
4.3.1 b)
·
(Acceptance of the
SRS )
10 % of CAPEX for
ACBMS Application
S/w (S.No. 1 of Table
Software Requirement
Specifications (SRS)
Seal & Signature of the Auth. Sign.
Page 78 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Milestone
Deliverable (Reports/
Documents & Infra)
Payment Terms
Payment Schedule
A4 of Fin. Bid)
·
System Design
Document (SDD)
·
Testing Methodology
including test cases and
test plan and Test
Results
·
Development and
deployment of web
based application
software
·
Electronic conversion of
master records
·
Data digitization of 500
cases
·
UAT Acceptance
Supply, Installation
and commissioning
of IT & Non IT
Infrastructure at
ACB HQ as per BoM
annexure -2 (A) and
(Para 4.3.2 of SoW)
·
Item Delivery, installation (Successful
Report,
inspection commissioning of IT
&
Non
IT
reports
Infrastructure at ACB
HQ
60% of the total
CAPEX (Table A1 of
Fin. Bid) for ACB HQ
infrastructure
Supply, Installation
and commissioning
of IT & Non IT
infrastructure at 8
Range Offices as per
BoM annexure -2 (B)
and (Para 4.3.2 of
SoW)
·
Item Delivery, installation Successful
Report,
inspection commissioning of IT
&
Non
IT
reports
Infrastructure at all
regional offices
60% of the total
CAPEX (Table A2 of
Fin. Bid) for 8 Range
Office infrastructure
Supply, Installation
and commissioning
of IT & Non IT
infrastructure at 35
Outposts Office as
per BoM annexure -2
(c) and (Para 4.3.2 of
SoW)
·
Item Delivery Report, Successful
inspection reports with commissioning of IT
&
Non
IT
detailed specifications
Infrastructure at all
the
respective
locations
60% of the total
CAPEX (Table A3 of
Fin. Bid) for 35
Outposts Offices
Training
·
Training manual
(Para 4.3.4 of SoW)
·
Training to all Nominated
employees of ACB as
per SoW
·
Trainees Feedback and
attendance sheet
Development and
deployment of Web
Portal & ACBMS
Application S/w
(Para 4.3.1)
Seal & Signature of the Auth. Sign.
(Sign off- Final user
acceptance of Web
portal & ACBMS
application S/W)
Successful
completion of the
Training to all the
designated officers/
employees on the
basis of training
feedback report
50 % of CAPEX for
Web portal & ACBMS
Application S/w (S.No.
1 of Table A4 of Fin.
Bid)
Payment shall be paid
based on no. of
session successfully
completed
(unitary
price SNo. 2 of table
A6 of Fin Bid)
Page 79 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Milestone
Deliverable (Reports/
Documents & Infra)
GO-Live
Data Digitization
·
(Para 4.3.3 of SoW)
·
User
manual
of
Application Software
·
Access
Policy
·
Incident
Management Policy
·
Change
management plan
development
Control
Perform activities as per
the scope defined in
SoW
Payment Terms
Payment Schedule
Final FAT of
ACBMS Application
S/w (Go-Live)
25% of CAPEX for
ACBMS Application
S/w (S.No. 1 of Table
A4 of Fin. Bid)
75% (Table A5 of Fin.
Bid, DMS Lic.)
Attendance of man
power approved by
RISL/ACB
Quarterly payment
shall be paid on the
basis of Man month
efforts put in by SI
(unitary price of S No
1 Table A6 of Fin Bid)
Successfully rollout
of Web portal &
ACBMS application
S/W for period of
minimum 3 months
after Go-Live
(Acceptance for
successful
performance from
ACB/RISL)
Remaining 15%
CAPEX for Web portal
& ACBMS Application
S/w (S N 1 of A4 of
Fin. Bid) shall be paid
after successful go live
(Minimum 3 months).
Successful
completion of O&M
Activities
and
maintenance of web
based
application
software
12 Equal quarterly
instalment of the total
OPEX (Table B1 of
Financial Bid)
Operation & Management (Post Go-Live)
Implementation
Support
·
Post –Go live for
period of 3
months
FMS During O&M
i)
·
Monthly compliance
report on compliant
registers and bugs fixing
Manpower Supply for
period of 3 years at as
per requirement
mentioned in SoW
(operation &
maintenance) to manage
services
·
Helpdesk for the
technical & functional
scope
·
MIS reports as per SOW
(Para 4.3.6) Operation &
maintenance sub section
of this RFP
And
25% of the total
CAPEX (Table A5 of
Fin. Bid,DMS Lic.)
and
Remaining 40%
CAPEX of (Table A1,
A2, A3 of Fin. Bid)
shall be paid in 12
equal quarterly
instalments during the
O&M phase of the
project
Any penalties/ liquidated damages, as applicable, for delay and non-performance, as
per the criterion mentioned in this bidding document, will be deducted from the
payments for the respective milestones.
Seal & Signature of the Auth. Sign.
Page 80 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
j)
The selected bidder must obtain an NOC for all the kind of deliverables as mentioned in
this bidding document from the designated nodal officer/ authority before raising the Bill/
Invoice for the successful completion of the respective milestone.
k) All work contract tax, service tax and income tax, etc., as applicable, will be deducted at
source as per the prevalent rules & regulations at the time of making payments to the
selected bidder.
C) Special Conditions of the Bid
a) Acceptance Testing and Certification The primary goal of Acceptance Testing and
Certification is to ensure that the Project (including all the project components as discussed
in the scope of work) meets requirements, standards, specifications and performance, by
ensuring that the following are associated with clear, quantifiable metrics for accountability:
·
Functional requirements
·
Infrastructure Compliance Review
·
Availability of the project Services in the defined locations
·
Performance
·
Security
·
Manageability
·
SLA Reporting System
·
Project Documentation (Design, development, configuration, training and administration
manuals etc)
·
Data Quality Review
b) As part of Acceptance testing, performed through a third party agency, the procurement
agency shall review all aspects of project development and implementation covering
software, hardware and networking including the processes relating to the design of solution
architecture, design of systems and sub-systems, coding, testing, business process
description, documentation, change management, security, performance in relation to
defined requirements, interoperability, scalability, availability and compliance with all the
technical and functional requirements of the RFP and the agreement.
c) The procedures and parameters for testing will be laid down by the Third Party Agency after
approval from procurement agency; the solution deployed by the vendor has to satisfy third
party acceptance testing.
d) The procurement agency will establish appropriate processes for notifying the selected
vendor of any shortcomings from defined requirements at the earliest instance after noticing
the same to enable the selected vendor to take corrective action. All gaps identified shall be
Seal & Signature of the Auth. Sign.
Page 81 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
addressed by the vendor immediately prior to Go-live of the solution. It is the responsibility
of the selected Bidder to take any corrective action required to remove all shortcomings,
before the roll out of the project.
e) It is to be noted that the if their is involvement of the third party for acceptance testing and
certification, does not absolve the vendor of his responsibilities to meet all SLAs as laid out
in this RFP document.
f)
It is to be noted that the procurement agency may get the solution audited through a Third
Party periodically after Go-Live in order to ensure the success of the project. Such thirdparty agency for carrying out the acceptance testing and certification of the entire solution
will be nominated by the RISL.
g) Following discusses the acceptance criteria to be adopted for the project as mentioned
above. The list below is indicative and the activities will include but not be limited to the
following:
·
Functional Requirements Review: The solution developed/customized by selected
Bidder shall be reviewed and verified by the agency against the Functional
Requirements signed-off between the procurement agency and the selected Bidder. All
gaps, identified shall be addressed by the vendor immediately prior to Go-live of the
solution.
·
Security Review: The software developed/customized shall be audited by the agency
from a security and controls perspective. Such audit shall also include the IT
infrastructure and network deployed for the project. Following are the broad activities to
be performed by the Agency as part of Security Review. The security review shall
subject the solution to the following activities.
o
Application security mechanisms
o
Assessment
of
authentication
mechanism
provided
in
the
application
/components/modules
o
Assessment of data encryption mechanisms implemented for the solution
o
Assessment of data access privileges, retention periods and archival mechanisms
protected.
o
Application Security mechanisms should be accessed in compliance with the IT Act
2000,2008 Amendment and IT rules 2011, such that it maintains data/information
Integrity, Confidentiality, Non-repudiation.
o
Audit of Security mechanisms so that they are in compliance with the latest
Guidelines by Controller of Certifying authority (CCA), IT Act, ISO27001.
Seal & Signature of the Auth. Sign.
Page 82 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
·
Performance: Performance is another key requirement for the project and the agency
shall review the performance of the deployed solution against certain key parameters
defined in SLA. Such parameters include request-response time, work-flow processing
time, concurrent sessions supported by the system etc. The performance review also
includes verification of scalability provisioned in the solution for catering to the project
requirements.
·
Availability: The solution should be designed to remove all single point failures.
Appropriate redundancy shall be built into all the critical components to provide the
ability to recover from failures. The agency shall perform various tests including security
tests to verify the availability of the services in case of component/location failures. The
agency shall also verify the availability of the project services to all the users in the
defined locations.
·
Project Documentation: The Agency shall review the project documents developed by
the selected Bidder including requirements, design, source code, installation, training
and administration manuals etc.
·
Any issues/gaps identified by the Agency, in any of the above areas, shall be addressed
to the complete satisfaction of the Department.
·
Data Quality: The Agency shall perform the Data Quality Assessment for the Data
digitized by selected Bidder and the data migrated by the vendor to the new system.
The errors/gaps identified during the Data Quality Assessment shall be addressed by
the vendor before moving the data into production environment, which is a key mile
stone for Go-live of the solution.
39) Service Level Standards/ Requirements/ Agreement
Service level Agreement - SLA defines the terms of the successful bidder’s responsibility in
ensuring the performance of the hardware, software & other equipments supplied for ACBMS
project based on the agreed performance indicators as detailed in the agreement. This defines
various Service Levels for various components of the project, which shall be considered in the
Service Level Agreement with SI. The service level agreement has been given at
Annexure – 17.
40) Change Requests/ Management
i.
RISL/ ACB may at any time, by a written order given to the selected bidder, make
changes within the general scope of the Agreement in any one or more of the
following: -
Seal & Signature of the Auth. Sign.
Page 83 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
·
Designs, specifications, requirements which software or service to be
provided under the Agreement are to be specifically developed and rendered
for the ACB.
·
The method of deployment, shipping or packing.
·
Schedule for Installation Acceptance.
·
The place of delivery and/or the services to be provided by the selected
bidder.
ii.
The change request/ management procedure will follow the following steps: ·
Identification and documentation of the need for the change - The
information related to initiator, initiation date and details of change required
and priority of the change will be documented by ACB/ RISL.
·
Analysis and evaluation of the Change Request - Impact of the change in
terms of the estimated effort, changed schedule, cost and the items impacted
will be analyzed and documented by the selected bidder.
·
Approval or disapproval of the change request – ACB/ RISL will approve or
disapprove the change requested including the additional payments for
software development, quoted man-month rate shall be used for cost
estimation, efforts of all technical resources- project manager, analyst,
software developer, testing engineer, database architecture etc shall be
taken into account for total man-month estimation to carry out the s/w
development resulting from the change request. For all technical resources
irrespective of their experience and specialisation, the quoted man-month
rate shall be used. Efforts of support staff shall not be taken into
consideration for this purpose.
·
Implementation of the change – The change will be implemented in
accordance to the agreed cost, effort, and schedule by the selected bidder.
·
Verification of the change - The change will be verified by the ACB/ RISL on
implementation of the change request.
iii.
All changes outside the scope of supplies agreed to herein which may have likely
financial implications in terms of the overall cost/ time of the project shall be
undertaken by SI only after securing the express consent of the ACB/ RISL. In the
event that the consent of ACB/ RISL is not received then the change will not be
carried out.
iv.
While approving any change request, if required, RISL/ GoR may ask the selected
bidder to deploy the required resources on-site.
Seal & Signature of the Auth. Sign.
Page 84 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
v.
If any such change outside the scope of supplies agreed to herein causes an
increase or decrease in cost of, or the time required for, firm’s performance of any
provisions under the Agreement, equitable adjustments shall be made in the
Agreement Price or Delivery Schedule, or both, and the Agreement shall accordingly
be amended. Any claims by firm for adjustment under this must be asserted within
30 (thirty) days from the date of SI receiving the RISL change order which shall not
be unreasonably withheld or delayed.
D) Exit Management
a)Preamble
I.
II.
The word ‘parties’ include the tendering authority and the selected bidder.
This Schedule sets out the provisions, which will apply on expiry or termination
of the Project Implementation and Operations and Management of SLA.
III.
In the case of termination of the Project Implementation and/ or Operation and
Management SLA due to illegality, the Parties shall agree at that time whether,
and if so during what period, the provisions of this Schedule shall apply.
IV.
The Parties shall ensure that their respective associated entities carry out their
respective obligations set out in this Exit Management Schedule.
b)Transfer of Assets
I.
The selected bidder may continue work on the assets for the duration of the exit
management period which may be a six months period from the date of expiry or
termination of the agreement, if required by RISL / ACB to do so. During this
period the selected bidder will transfer all the assets in good working condition
and as per the specifications of the bid document including the ones being
upgraded to the bureau/ designated agency. The security deposit/ performance
security submitted by selected bidder will only be returned after the successful
transfer of the entire project including its infrastructure.
II.
The selected bidder will transfer all the Software Licenses under the name of the
bureau as desired by the tendering authority during the exit management period.
III.
ACB / RISL during the project implementation phase and the operation and
management phase shall be entitled to serve notice in writing to the selected
bidder at any time during the exit management period requiring the selected
bidder to provide ACB / RISL or its nominated agencies with a complete and upto-date list of the assets within 30 days of such notice.
IV.
Upon service of a notice, as mentioned above, the following provisions shall
apply:
Seal & Signature of the Auth. Sign.
Page 85 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
a. In the event, if the assets which to be transferred to ACB / RISL mortgaged to
any financial institutions by the selected bidder, the selected bidder shall ensure
that all such liens and liabilities have been cleared beyond any doubt, prior to
such transfer. All documents regarding the discharge of such lien and liabilities
shall be furnished to ACB / RISL or its nominated agencies.
b. All title of the assets to be transferred to ACB / RISL or its nominated agencies
pursuant to clause(s) above shall be transferred on the last day of the exit
management period. All expenses occurred during transfer of assets shall be
borne by the selected bidder.
c. That on the expiry of this clause, the selected bidder and any individual assigned
for the performance of the services under this clause shall handover or cause to
be handed over all confidential information and all other related material in its
possession, including the entire established infrastructure supplied by selected
bidder to RISL / ACB.
d. That the products and technology delivered to RISL /ACB during the contract
term or on expiry of the contract duration should not be sold or re-used or copied
or transferred by selected bidder to other locations apart from the locations
mentioned in the this bid document without prior written notice and approval of
ACB and RISL. Supplied hardware, software & documents etc., used by selected
bidder for ACB / RISL shall be the legal properties of ACB / RISL.
c)Cooperation and Provision of Information
I.
During the exit management period
a. The selected bidder will allow RISL / ACB or its nominated agencies access to
the information reasonably required to define the current mode of operation
associated with the provision of the services to enable ACB / RISL or its
nominated agencies to assess the existing services being delivered.
b. The selected bidder shall provide access to copies of all information held or
controlled by them which they have prepared or maintained in accordance with
the Project Implementation, the Operation and Management SLA and SOWs
relating to any material aspect of the services provided by the selected bidder.
RISL / ACB or its nominated agencies shall be entitled to copy all such
information comprising of details pertaining to the services rendered and other
performance data. The selected bidder shall permit RISL / ACB or its nominated
agencies and/ or any Replacement Operator to have reasonable access to its
employees and facilities as reasonably required by RISL / ACB or its nominated
agencies to understand the methods of delivery of the services employed by the
Seal & Signature of the Auth. Sign.
Page 86 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
selected bidder and to assist appropriate knowledge transfer.
d)Confidential Information, Security and Data
I.
The selected bidder will promptly on the commencement of the exit management
period supply to RISL / ACB or its nominated agencies the following:
a. Documentation relating to Intellectual Property Rights;
b. Project related data and confidential information;
c. All current and updated data as is reasonably required for purposes of RISL /
ACB or its nominated agencies transitioning the services to its replacement
selected bidder in a readily available format nominated by RISL / ACB or its
nominated agencies; and
d. All other information (including but not limited to documents, records and
agreements) relating to the services reasonably necessary to enable RISL / ACB
or its nominated agencies, or its replacement operator to carry out due diligence
in order to transition the provision of the services to RISL / ACB or its nominated
agencies, or its replacement operator (as the case may be).
e. Before the expiry of the exit management period, the selected bidder shall
deliver to RISL / ACB or its nominated agencies all new or up-dated materials
from the categories set out above and shall not retain any copies thereof, except
that the selected bidder shall be permitted to retain one copy of such materials
for archival purposes only.
e)Transfer of certain agreements
I.
On request by Tendering Authority or its nominated agencies, the selected
bidder shall effect such assignments, transfers, innovations, licenses and sublicenses as Tendering authority or its nominated agencies may require in favour
of tendering authority or its nominated agencies, or its Replacement Operator in
relation to any equipment lease, maintenance or service provision agreement
between selected bidder and third party leasers, operators, or Operator, and
which are related to the services and reasonably necessary for carrying out of
the replacement services by RISL / ACB or its nominated agencies, or its
replacement Operator.
II.
Right of Access to Premises: At any time during the exit management period
and for such period of time following termination or expiry of the SLA, where
assets are located at the selected bidder’s premises, the selected bidder will be
obliged to give reasonable rights of access to (or, in the case of assets located
on a third party's premises, procure reasonable rights of access to RISL / ACB or
Seal & Signature of the Auth. Sign.
Page 87 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
its nominated agencies, and/ or any replacement operator in order to inventory
the assets.
f) General Obligations of the selected bidder
I.
The selected bidder shall provide all such information as may reasonably be
necessary to effect as seamless during handover as practicable in the
circumstances to RISL / ACB or its nominated agencies or its replacement
operator and which the operator has in its possession or control at any time
during the exit management period.
II.
The selected bidder shall commit adequate resources to comply with its
obligations under this Exit Management Clause.
g)Exit Management Plan
I.
The selected bidder shall provide RISL / ACB or its nominated agencies with a
recommended exit management plan ("Exit Management Plan") which shall deal
with at least the following aspects of exit management in relation to the SLA as a
whole and in relation to the Project Implementation, the Operation and
Management SLA and SOWs.
II.
A detailed program of the transfer process that could be used in conjunction with
a replacement operator including details of the means to be used to ensure
continuing provision of the services throughout the transfer process or until the
cessation of the services and of the management structure to be used during the
transfer; and
III.
Plans for the communication with such of the selected bidder's, staff, suppliers,
customers and any related third party as are necessary to avoid any material
detrimental impact on RISL / ACB operations as a result of undertaking the
transfer; and
IV.
If applicable, proposed arrangements and Plans for provision of contingent
support in terms of business continuance and hand holding during the transition
period, to RISL / ACB or its nominated agencies, and Replacement Operator for
a reasonable period, so that the services provided continue and do not come to
a halt.
V.
The Bidder shall re-draft the Exit Management Plan annually after signing of
contract to ensure that it is kept relevant and up to date.
VI.
Each Exit Management Plan shall be presented by the selected bidder to and
approved by ACB / RISL or its nominated agencies.
Seal & Signature of the Auth. Sign.
Page 88 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
VII.
In the event of termination or expiry of SLA, Project Implementation, Operation
and Management SLA or SOWs each party shall comply with the Exit
Management Plan.
VIII.
During the exit management period, the selected bidder shall use its best efforts
to deliver the services.
IX.
Payments during the Exit Management period shall be made in accordance with
the Terms of Payment Clause.
X.
It would be the responsibility of the selected bidder to support new operator
during the transition period.
Seal & Signature of the Auth. Sign.
Page 89 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.
ANNEXURES
7.1. ANNEXURE 1 – FUNCTIONAL REQUIREMENT SPECIFICATIONS
The functional requirement specifications stated below are the minimum indicative features that
the solution suggested for Anti Corruption Bureau should have. This indicative functional
requirement has been provided here to be used by the SI for the effort estimation. The System
Integrator/ Implementation Agency (SI/IA) shall develop the final detailed Functional
Requirement Specifications (FRS) and System Requirement Specifications (SRS) documents
after a detailed design phase where all the processes, procedures and existing templates
should be studied in detail by the SI/IA. SI/IA should independently design the solutions as may
be required to support the business operations. The SI/IA shall be required to coordinate with
the department for the detailed system study and interact with the different users of the
department for preparation of final FRS, SRS and related design documents.
The scope of work for the project will cover core ACBMS application development, bilingual
(English and Hindi) integrated web based application software for ACB Head Quarter, 8 Range
Office and 35 Outposts offices.
7.1.1.
Core Modules
Based on the requirements of automation under current scope of project, following are the core
functional modules that are envisaged:
a.
b.
c.
d.
Complaint Submission System
Preliminary Enquiry System
Regular Enquiry System
Legal and Prosecution System
a) Complaint Submission System
This module will take care of
o
o
o
Submission of complaints to ACB
Categorization of submitted complaints
Review of submitted complaints by authorized reviewing authority (ADG or as
designated by ADG)
Requirement Id
Description
System Login
ACB_CMM_1.
The System shall be accessible to following users
·
Internal Bureau users as per the user roles specified by the ACB for various
components of ACBMS
Seal & Signature of the Auth. Sign.
Page 90 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
·
·
ACB_CMM_2.
Other departmental users for
o Uploading documents related to a complaint.
o Providing response to clarifications initiated by ACB.
o To view and download final findings related to a complaint/case as
authorized by ACB.
o Track status of submitted complaints/cases as authorized by ACB.
External public users for
o Uploading documents related to a complaint.
o To view and download final findings related to a complaint/case as
authorized by ACB.
o To track status of submitted complaints.
The system should allow authorized users to access various functions, forms,
screens, sub modules, information etc. as per the authorizations and user roles
permissible as per guidelines and policies of the Bureau.
ACB_CMM_3.
The system should, as a part of registration, establish challenge and response
mechanisms for session validation for future online sessions. Details such as
username and password, challenge question and response answer should be asked
if login details are forgotten etc.
ACB_CMM_4.
The system should apply spam control measures like ‘captcha’ images during
registration to avoid spurious details being automatically submitted and ensure that
data is not submitted by non-humans.
ACB_CMM_5.
The system shall maintain non editable audit trail of all activities carried out by any
user in ACBMS.
Access
ACB_CMM_6.
The module should be accessible through centralized web application only for
following roles and indicative privileges:
·
·
·
Internal Bureau user as per the user role specified by the ACB for various
components of ACBMS over Intranet
o Deciding Authority
o Verification Authority
o Duty Office
o Bureau User
Other government departments users over Internet for
o Department Administrator
o Department User
External public users over Internet for
o Registered Public user
Submission of Complaint
ACB_CMM_7.
The following mentioned fields are indicatively expected be captured:
·
·
·
Source of Complaint
Complainant’s name
Complainant’s Address
Seal & Signature of the Auth. Sign.
Page 91 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
·
·
·
·
·
·
·
·
·
·
·
·
·
Email ID
Contact number
Category of complainant (individual person / department/NGO/
society/Union) etc
UID Number of Complainant (in case of Individual)
Identification proof (in case of Individual)
Complaint Description
Name/information of entity against whom complaint is to be filed
Details about suspects
Charges in brief
Address of the person against whom complaint is to be filed
Location of incident
Jurisdiction /Range /Outpost (optional)
Available evidences
These shall be finalized in discussions with the Bureau. SI may be required to
provide different forms for different kind of complaints and accordingly different
information fields may be captured. e.g. system should allow capturing of details of
news clippings in case of complaints relating to media or for complaints arising from
MLAs/MPs, constituency details may be captured etc.
ACB_CMM_8.
Through centralized web based electronic form, a complainant should be able to
Register himself based on certain mandatory information provided for registration.
Indicative list for fields to be captured is provided in ‘Fields to be Captured’
subsection. However details to be captured shall be finalized in consultation with the
Bureau.
ACB_CMM_9.
The system should also allow an authorized user from Bureau to submit a complaint
on behalf of someone else e.g. on behalf of public request, other departments, MLA,
MP, public representative, other government departments or on recommendation of
internal staff.
ACB_CMM_10.
The system should allow the complainant to attach various documents/supporting
documents/evidences along with the complaint. Following should be the allowed
documents for upload:
·
·
·
·
·
·
Scanned documents
Images
RTFs
PDFs
Video files
Audio files
The system shall support all other formats as specified by ACB for above
mentioned types of documents.
Seal & Signature of the Auth. Sign.
Page 92 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
ACB_CMM_11.
All types of documents submitted along with the complaint should be preserved
securely in the system and its quality must be maintained. All documents should be
in read only mode and non editable.
ACB_CMM_12.
On submission of the complaint, a unique complaint number should be generated by
the system for future reference. This complaint number should be saved in
encrypted form in the system.
ACB_CMM_13.
All types of documents submitted along with the complaint should be tagged with the
unique complaint number and should be retrievable only by an authorized user of the
Bureau of the role of verification authority.
ACB_CMM_14.
The system should have mandatory fields marked out clearly for online complaint
filling. The system should not allow submission of the complaint without completing
the mandatory fields. Mandatory/Non Mandatory fields shall be finalized in
discussion with the Bureau.
Review of complaints
ACB_CMM_15.
All submitted complaints should be notified to the reviewer through email and
dashboard. This role shall be preconfigured in the system as part of system
configured for review of complaints.
ACB_CMM_16.
The system should allow reviewer after successful login, to review the charges made
in the complaint, to establish identity of complainant and to categorize the submitted
complaints/cases.
Following is the initial categorization of complaints that system should allow
(indicative):
Categorization of Persons (entity against whom complaint is to be filed)
·
·
·
·
·
Complaints against person with the rank of Gazetted officer and
above
Complaints against subordinate officer
Complaint against person other than government staff/officer like
PSU
Government/Minister related cases
Head of Department related Cases
Charges Framed in Complaint
·
·
·
Charges regarding misuse of position/office
Charges of disproportionate assets
Charges of corruption
Seal & Signature of the Auth. Sign.
Page 93 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Complaint Source
·
·
·
·
·
·
Anonymous complaints
Complaint forwarded by MPs/MLAs
Cases forwarded by other departments
Public complaint
News & Media
Complaint initiated by ACB officials etc.
Action Required
·
·
·
·
·
·
ACB_CMM_17.
Pseudo complaints
Complaints requiring preliminary enquiries
Complaints that can be directly submitted for regular enquiries
Complaints against with case can be filed
Trap is Required
Verification of complainant
The System should allow authorized user to configure the system for all the
designated authorized users as per the guidelines of Bureau for handling complaint
according to:
·
·
·
·
Category of person (entity against whom complaint is to be filed);
Charges;
Source of complaint; and
Action required
The designated authority should be allowed to modify the system anytime during the
proceedings. However all audit trails shall be maintained in the system and
mandatory approvals should be required to be uploaded in the system if required for
the change.
ACB_CMM_18.
Based on pre-registration investigation and review of complaints, the reviewer
should be able to mark the case as secret in which case special restrictive access
shall be given to the case/complaint.
ACB_CMM_19.
Based on complaint review and investigation, in case the Bureau envisages that
further investigations are required, the complaint is put under system for preliminary
enquiry. Alternatively he may choose to reject the complaint based on special
approvals by deciding authority. Optionally, he may forward the case for regular
enquiry in case sufficient evidence exists and there is an approval by the deciding
authority.
ACB_CMM_20.
In case the complaint is not considered for further processing/action, system should
allow authorized user to reject the complaint. Accordingly, based on the functional
requirements listed at ACB_CMM_18, ACB_CMM_19 and ACB_CMM_20, the status
Seal & Signature of the Auth. Sign.
Page 94 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
of submitted complaint may change in the system to any of the following:
·
·
·
·
·
·
·
ACB_CMM_21.
Submitted
Reviewed
Rejected
Under Preliminary Enquiry
Under Regular Enquiry
Final decision taken
Reopened etc.
Authorized users should be allowed to view the status of a complaint and associated
proceedings and documents as per rights and privileges assigned as per guidelines
and policies of Bureau.
ACB_CMM_22.
A notesheet in line with format used by the Bureau should be attached with each
complaint which shall record all proceedings/meetings/decisions related to the
complaint and will exist throughout the lifecycle of the complaint. Authorized users
should only be allowed to provide inputs to notesheet. No user should be allowed to
modify any already existing content in the notesheet.
b) Preliminary Enquiry
Based on the nature of complaint, the reviewing officer may decide to carry out further investigations on
the charges reported in the complaint before registering a complaint/case.
Requirement Id
Description
System Login
ACB_PEM_1
It shall be accessible to following users
·
·
·
ACB_PEM_2
Internal Bureau users as per the user role specified by the ACB for various
components of ACBMS.
Other government departments users
o Uploading documents related to a complaint.
o To provide response to clarifications initiated by ACB.
o To view and download final findings related to a complaint/case as
authorized by ACB.
o To track status of submitted complaints/cases as authorized by
ACB.
External public users for
o To track status of submitted complaints/cases as authorized by
ACB.
For certain sensitive information, the system shall enable biometric based
authentication to access information/forms/other components e.g. to complaints
Seal & Signature of the Auth. Sign.
Page 95 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
marked as secret/highly sensitive video files etc.
Access
ACB_PEM_3
The module should be accessible through centralized web application only for
following roles and indicative privileges:
·
·
·
Internal Bureau user as per the user role specified by the ACB for various
components of ACBMS over Intranet
o Deciding Authority.
o Verification Authority.
o Enquiry Officer.
o Investigator.
Other state government departments users over Internet for
o Department Administrator.
External public users over Internet for
o Public registered user.
Fields to be captured
ACB_PEM_4
For various reports to be generated the formats and fields shall be discussed and
finalized with the Bureau.
Investigations
ACB_PEM_5
The System should allow authorized user to configure the system for all the
designated authorized users as per the guidelines of Bureau for handling PE in case
of
·
·
·
·
·
·
·
·
·
·
·
Anonymous complaints
Pseudo complaints
Trap Cases
Cases regarding misuse of position/office
Disproportionate assets cases
Complaints against person with the rank of Gazetted officer and
above
Complaints against subordinate officer
Government/Minister related cases
Head of Department Related Cases
Complaint forwarded by MPs/MLAs
Cases forwarded by other departments
Designated authority should be allowed to modify the system anytime during the
proceedings. However all audit trails shall be maintained in the system and
mandatory approvals should be required to be uploaded in the system if the system
is required to be changed.
ACB_PEM_6
All submitted complaints under trap cases should be notified to the respective
range/enquiry officer through SMS. The system should allow to escalate complaints
require trap action as per the configured system,
Seal & Signature of the Auth. Sign.
it should provide interface to
Page 96 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
capture
·
·
·
·
ACB_PEM_7
Team appointment by the designated officer
Take recommended action
Proceedings of trap team
Findings of trap team
The System should allow authorized user to appoint special teams in the system for
handling various activities of case/complaint handling. It should capture details like
Complaint No, assigned date, team member name, target date, task assigned etc. In
case the team members belong to ACB then it should also allow to capturing of
employee id and related details.
ACB_PEM_8
The system should allow authorized and designated officer for a complaint to be
assigned to next level user to take action on the processing of complaints. He should
have the flexibility in the system to provide only requisite information to the next level
designated officer for taking action.
ACB_PEM_9
The system should be able to configure timelines for action to be taken by other
designated users.
ACB_PEM_10
The system should allow authorized users to configure sending reminders for
defined periodicity based on defined action timelines or custom timelines. Authorized
user may be allowed to extend/revise the timelines based on the guidelines provided
in the charter of the Bureau.
ACB_PEM_10
The system should allow authorised authority to record instructions and take action
while assigning a case e.g. verification of complainants, collection of evidence,
record statement of witness and complainants etc.
ACB_PEM_11
System should allow providing interface for legal cell authorized users, technical
team users to provide inputs/opinions on areas where their inputs are sought.
In case their inputs are received through systems like email/post, authorized user
should be able to attach those communications/documents in the system and tag it
to
the
complaint
number.
Suitable
integration
with
underlying
document
management system, email solution, sms gateway and other support systems
should be enabled.
ACB_PEM_12
System should provide interface to designated authority to appoint external legal
expert and technical expert, and shall allow him to send formal office memo along
with case description to provide inputs/opinions on areas where their inputs are
sought.
The system should provide interface for office user to capture inputs provided by the
external experts. In case their inputs are received through systems like email/post,
Seal & Signature of the Auth. Sign.
Page 97 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
authorized user should be able to attach those communications/documents in the
system and tag it to the complaint number. Suitable integration with underlying
document management system, email solution should be enabled.
ACB_PEM_13
Based on the task configured in the system by authorized user, the tasks should
reflect in the email of the user and in the dashboard along with activity status
ACB_PEM_14
Customized dashboard should allow authorized user to take action on activities
pending with him/her in a secured manner in a system seamlessly integrated with
other modules like portal, document management and other modules of the
application. Submission of every activity in the system should suitably update
required tables/databases at the backend. There should be no/minimum data
redundancy.
ACB_PEM_15
The configured system should allow each designated authorized user for a particular
activity to provide his comments/ prepare and attach reports (in line with formats
being used by the Bureau) /attach documents relevant to the case, allow
communication through email/sms to relevant registered department users or to the
complainant, or the people associated with the complaint through registered
email/mobile number or composing an email/sms. From a master of Anti Corruption
Acts and sections, he may choose to provide relevant references for the reviewers.
ACB_PEM_16
System should provision designated user to prepare and attach Plan of Action,
Factual Report, Source Information Report, Verification Report etc. as per formats of
the Bureau.
ACB_PEM_17
Once the tasks of the officer assigned by higher authority are completed, further
actions about the processing of complaint/enquiry may not be notified to the
assigned officer. Only the highest level authorized and designated officer (or
assigned by him/her) should have access to all the details of the case. (ADG in case
of ACB).He/she should be able to configure access rights to each component of
information about the complaint.
ACB_PEM_18
All communications, remarks, reviews, recommendations, approvals, rejections,
disposals
should
be
recorded
in
the
system
and
available
for
preparer/approver/reviewer or any other designated officer as per assigned authority
for viewing and providing comments.
ACB_PEM_19
Each communication, notification, comments should be referenced uniquely under a
complaint number and should be retrievable based on combinations like date,
complaint number, comment number or user id, user name etc.
ACB_PEM_20
System should allow search of activities, comments, notifications, documents etc.
related to a complaint based on multiple search parameters.
ACB_PEM_21
System should allow inter referencing of complaints.
Seal & Signature of the Auth. Sign.
Page 98 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
ACB_PEM_22
System should allow marking complaints as repeat complaints based on various
parameters such as repeat complaint against someone or repeated complaint by
same complainant etc.
ACB_PEM_23
System should allow authorized user to search complaints based on various
parameters such as complainant/ name of the person against whom complaint is
filed etc.
ACB_PEM_24
The system should allow designated officer to capture final decision related details.
The System shall allow user to record the final decision taken by the Bureau, and
proceed further to Regular Enquiry module if required.
ACB_PEM_25
In case decision requires departmental action to be carried out, system should allow
preparation of suitable communication in standard office order format for
communication to the department administrator. This shall be integrated with the
email solution.
MIS
ACB_PEM_26
System should provide suitable MIS to designated officer at predefined periodicity.
These MIS should have parameters to configure option to be delivered through
email, or dashboard, or access by the designated user. Indicative but not
comprehensive list of MIS include:
·
·
·
·
·
·
·
·
·
·
Complaint categorization related reports
Repeat compliant related reports
Complaint rejection reason related reports
Complaints pending for verification
Complaint against Class One Officer
Complaint forwarded by MLA/MP
Department wise complaints logged
Complaint forwarded for Preliminary Enquiry
Complaint Registered with Mollified Intention
Monthly Progress Report etc.
These are indicative only. Final list shall be developed in consultation
with the Bureau.
ACB_PEM_27
The System should provide a screen to designated authorized user to extract and
export data related to complaints based on various parameters into word/excel/pdf
format for analysis or further reporting.
Archival
ACB_PEM_28
The system should have the provision that once a complaint is closed/rejected, after
a predefined periodicity, such complaints may be archived for better performance of
Seal & Signature of the Auth. Sign.
Page 99 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
the system.
ACB_PEM_29
Archived complaints/enquiries should be easily retrievable, if required, by the
designated and authorized officer and allow read only view of all the activities,
documents, communication, notifications, audit trails pertaining to the case.
ACB_PEM_30
The system may allow designated authorized user to open a closed case for further
action after providing necessary and mandatory reasoning and attaching required
approval documents from authorized signatory (ies).
ACB_PEM_31
At anytime during the processing of the complaints, designated authorized user may
be
authorized
to
change
the
categorization
of
the
case
based
on
circumstances/proceedings of the case. In such cases all past history, activities
should be accessible/ available for further processing as well.
Integration
ACB_PEM_32
The system shall allow the user to search the existing repository of previous
Complaints pending against same person before acting on the complaint. In case of
duplication of complaint under similar offence it should allow user to club the
evidence of both complaints.
ACB_PEM_33
The system should allow authorized designated user to cross reference
complaints/FIRs/PEs in case they are related. Seamless integration in terms of all
records/documents is made available to the reviewer/designated officer.
ACB_PEM_34
The system should allow seamless integration for system activities of Legal cell and
for prosecution of cases.
ACB_PEM_35
The system should allow attaching references to a complaint/Case/FIR/PE from a
centralized repository of applicable and relevant rules/regulations if required or from
other cases.
ACB_PEM_36
The
system
shall
maintain
documents/policies/rules/regulations
a
centralized
etc.
(Please
repository
refer
to
of
all
such
requirements
of
“management of documents” for details)
c) Regular Enquiry System
Based on the nature of complaint, findings of preliminary investigations/enquiry or availability of sufficient
evidences, the reviewing officer may register the complaint and generate FIR. Such complaints/
preliminary enquiries shall be handled through Regular Enquiry module till sufficient facts/evidences are
collected for supporting the charges made in the complaint to initiate legal prosecution/action
Requirement Id
Description
Seal & Signature of the Auth. Sign.
Page 100 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
System Login
ACB_REM_1.
The system shall be accessible to following users
·
·
·
ACB_REM_2.
Internal Bureau users as per the user’s role specified by the ACB for various
components of ACBMS.
Other state government departments users for
o To Upload documents related to a complaint
o To provide response to clarifications initiated by ACB
o To view and download final findings related to a complaint/case as
authorized by ACB
o To track status of submitted complaints/cases
External public users for
o To track status of submitted complaints
For certain sensitive information, the system shall enable biometric / digital signature
based authentication to access information/forms/other components e.g. to
complaints market secret/highly sensitive video files etc.
Access
ACB_REM_3.
The system shall be accessible to the following users
·
·
·
Internal Bureau user as per the user role specified by the ACB for various
components of ACBMS
o Deciding Authority
o Verification Authority
o Enquiry Officer
o Investigator
o Legal Officer
o Duty Officer
o Bureau Officer
Other state government departments users for
o Department administrator
o Department User
External public users for
o Registered Public User
Fields to be captured
ACB_REM_4.
For various reports to be generated by the Bureau, formats and fields shall be
discussed and finalized with the Bureau.
Processing of complaint
ACB_REM_5.
No complaint shall be registered unless permission is granted through the system by
the deciding authority
ACB_REM_6.
The system should allow filing of FIR for the cases forwarded for Regular Enquiry in
the format defined by the Department. Unique FIR number shall be generated and
this FIR number shall be used for further references pertaining to complaint.
Seal & Signature of the Auth. Sign.
Page 101 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
ACB_REM_7.
The system should allow designated user to associate relevant Anti Corruption Acts
to the FIR from a master available for all relevant sections of applicable acts and
their details.
ACB_REM_8.
The system should allow authorized user to input details about complaint, action
taken during preliminary enquiry for collection of facts and evidences, findings of
preliminary enquiry, in case the same is not available in the system, and attach/
upload suitable documents/evidences.
ACB_REM_9.
The system should provide work flow to enable different reviewer level before final
approval of FIR content before final submission in system.
Association of Other Suspects
ACB_REM_10.
The system should allow authorized user to prepare a suspect database for
registered FIR. It should allow authorized user to capture details such as:
ACB_REM_11.
·
·
·
·
·
Name
Contact details
Identification number
UID number
Biometric details
·
Employee’s department
·
Designation
·
Identification Mark
·
·
·
Government ID Card number
PAN no of accused etc.
Reference to complaint numbers/FIR/cases
The system should maintain history of all cases where the individual might have
been associated with any complaint/case/FIR and should be accessible on search
by UID/Name/Contact details/Case number etc. This data may be used at the time of
“Vigilance Verification” requests raised to the Bureau.
ACB_REM_12.
The system should allow capturing of proceedings against the suspect & tag to
specific FIR.
ACB_REM_13.
The system should allow authorized user to search FIRs based on various
parameters and prioritize the same.
ACB_REM_14.
In case the complaint is not considered for further processing/action, system should
allow authorized user to reject/close the complaint. Accordingly the status of
submitted complaint may change in the system to any of the following
·
Submitted
Seal & Signature of the Auth. Sign.
Page 102 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
·
·
·
·
·
·
Reviewed
Rejected
Registered
Under Preliminary Enquiry
Under Regular Enquiry
Reopened etc.
The Closing of the case should be allowed only to ADG.
ACB_REM_15.
Authorized users should be allowed to view the status of a complaint and associated
proceedings and documents only as per rights and privileges assigned as per
guidelines and policies of Bureau.
ACB_REM_16.
A Notesheet in line with format used by the Bureau should be attached with each
complaint which shall record all proceedings/meetings/decisions related to the case
and will exist throughout the lifecycle of the case. Authorized users should only be
allowed to provide inputs to notesheet. No user should be allowed to modify any
already existing content in the notesheet.
Investigations
ACB_REM_17.
The system should allow authorized user to forward the FIR for investigations as per
preconfigured system as per the guidelines of Bureau.
ACB_REM_18.
The system should allow designated authority to modify the system anytime
during the proceedings where he/she should be allowed to change enquiry office,
investigator or change member of special team. However all audit trails shall be
maintained in the system and mandatory approvals should be required to be
uploaded in the system if required for the change.
ACB_REM_19.
The system should allow authorized user to appoint special teams in the system
for handling various activities of case/complaint handling. It should capture details
like assigned date, team member name, target date, task assigned etc. in case
the members belongs to ACB then it should also allow to capturing of employee
id and related details.
ACB_REM_20.
The system should allow authorized and designated officer for a case/complaint to
assign next level user to take action on the processing of complaints. He should
have flexibility in the system to provide only requisite information to the next level
designated officer for taking action instead of complete information about the
case/complaint.
S/He should be able to configure timelines for actions to be taken by other
designated users. System should allow him to configure sending reminders for
defined periodicity based on defined action timelines or custom timelines.
Authorized user may be allowed to extend/revise the timelines based on the
Seal & Signature of the Auth. Sign.
Page 103 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
guidelines provided in the Charter of the Bureau.
ACB_REM_21.
Based on the task configured in the system by authorized user, the tasks should
reflect in the email of the user and in the dashboard.
ACB_REM_22.
The system should allow each designated authorized user for a particular activity to
provide his comments/ prepare and attach reports (in line with formats being used by
the Bureau) /attach documents relevant to the case. The Indicative list of activities
may include:
·
·
·
·
·
·
·
·
ACB_REM_23.
The system should allow designated authority to issue
·
·
ACB_REM_24.
Record statement of accused
Record statements of suspects
Statements of witnesses
Evidences collected
Reports of search warrants
Assessment report of property of accused in case of
disproportionate assets cases
Results of search of official records for department related cases
Results of financial transactions related monitoring of suspects
etc.
Summons
Search warrants
The system should allow designated authority to generate office orders for initiation
and issuance of
·
·
ACB_REM_25.
Arrest warrants
Non-bail able warrants etc.
Once the tasks of the officer assigned by higher authority are completed, further
actions about the processing of complaint/enquiry may not be notified to the
assigned officer. Only the highest level authorized and designated officer (or
assigned by him/her) should have access to all the details of the case. (ADG in case
of ACB).He/she should be able to configure access rights to each component of
information of the complaint.
ACB_REM_26.
All communications, remarks, reviews, recommendations, approvals, rejections,
disposals should be recorded in the system and be made available for
preparer/approver/reviewer or any other designated officer as per assigned authority
for view and providing comments.
ACB_REM_27.
Each communication, notification, comments should be referenced uniquely under a
complaint number and should be retrievable based on combinations like date,
complaint number, comment number or user id, user name etc.
ACB_REM_28.
The system should allow search on multiple search parameters.
Seal & Signature of the Auth. Sign.
Page 104 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
ACB_REM_29.
The system should allow inter referencing of complaints/PEs/FIRs.
ACB_REM_30.
The system should allow marking complaints as repeat complaints based on various
parameters such as repeat complaint against someone or repeated complaint by
same complainant etc.
ACB_REM_31.
The system should allow authorized user to search complaints based on various
parameters such as complainant/ name of the person against whom complaint is
filed etc.
Legal & Technical Advice
ACB_REM_32.
The system should provide interface for legal cell authorized users, technical team
users and other departments to provide inputs/opinions on areas where their inputs
are sought. In case their inputs are received through systems like email/post,
authorized user should be able to attach those communications/documents in the
system and tag it to the complaint number. Suitable integration with underlying
document management system, email solution and other support systems should be
enabled.
ACB_REM_33.
The system should provide interface to designated authority to appoint external legal
expert(s) and technical expert(s), and allow him to send formal office memo along
with case description to provide inputs/opinions on areas where their inputs are
sought.
The system should provide interface for office user to capture input being provided
by the external experts. In case their inputs are received through systems like
email/post,
authorized
user
should
be
able
to
attach
those
communications/documents in the system and tag it to the complaint number.
Suitable integration with underlying document management system, email solution
should be enabled.
Correspondence with other department
ACB_REM_34.
The system should allow designated authorities to develop a case brief in the system
in specific office order format that may be shared with other departments and
agencies while soliciting information e.g. Income Tax Department, FERA, Revenue
Department, Concerned Department of accused etc. for providing information.
ACB_REM_35.
The system should allow authorized users to update the communication/clarifications
received from the other departments and agencies. Alternatively system should also
allow authorized users to design and provide a web based interface to the
department respondent to provide clarifications/inputs/information.
Decision
ACB_REM_36.
The system should allow designated officer to capture final decision related details.
Seal & Signature of the Auth. Sign.
Page 105 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
The System shall allow user to record the final decision taken by the Bureau, and
proceed further to Legal and Prosecution module if legal suit is required to be filed.
In case FIR decision requires departmental action to be carried out, system should
allow preparation of suitable communication in standard format for communication to
the department. This shall be integrated with the email solution.
ACB_REM_37.
In line with the final decision the “suspect” information should be updated in “Suspect
Database” e.g. If as per final decision, suspect/accused is not proved guilty then
system should allow designated authority to update suspect status to “released of all
charges” in database etc.
MIS
ACB_REM_38.
The system should provide suitable MIS to designated officer at predefined
periodicity. These MIS should have parameters to configure option to be delivered
through email, or dashboard, or access by the designated user. Indicative but not
comprehensive list of MIS include:
·
·
·
·
·
·
·
·
·
·
·
·
·
Complaint categorization related reports
Repeat compliant related reports
Complaint rejection reason related reports
Complaints pending for verification
Complaint against Class One Officer
Complaint forwarded by MLA/MP
Department wise complaint logged
Complaints forwarded for Preliminary Enquiry
Complaints Registered with Mollified Intention
Monthly Progress Report
FIRs where Prosecution is recommended
Section of Anticorruption Act wise FIR reports
Warrant/summon related FIRs.
These are indicative only. Final list shall be developed in consultation with the
Bureau.
ACB_REM_39.
The System should provide a screen to designated authorized user to extract and
export data related to complaints based on various parameters into word/excel/pdf
format for analysis or further reporting.
Archival
ACB_REM_40.
The system should have the provision that once a case is closed, after a predefined
periodicity, such cases may be archived for better performance of the system.
ACB_REM_41.
Archived cases should be easily retrievable if required by the designated and
authorized officer and allow read only/review of all the activities, documents,
communication, notifications, audit trails pertaining to the case.
Seal & Signature of the Auth. Sign.
Page 106 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
ACB_REM_42.
The system may allow designated authorized user to open a closed case for further
action after providing necessary and mandatory reasoning and attaching required
approval documents from authorized signatory (ies).
ACB_REM_43.
At anytime during the processing of the complaints, designated authorized user may
be
authorized
to
change
the
categorization
of
the
case
based
on
circumstances/proceedings of the case. In such cases all past history, activities
should be accessible/ available for further processing as well.
Integration
ACB_REM_44.
The system shall allow the user to search the existing repository of previous
Complaints pending against same person before acting on the complaint. In case of
duplication of complaint under similar offence then it should allow user to club the
evidence of both complaints.
ACB_REM_45.
The system should allow authorized designated user to cross reference
complaints/FIRs/PEs in case they are related. Seamless integration in terms of all
records/documents is made available to the reviewer/designated officer.
ACB_REM_46.
The system should allow seamless integration for system activities of Legal cell and
for prosecution of cases.
ACB_REM_47.
The system should allow attaching references to a complaint/Case/FIR/PE from a
centralized repository of applicable and relevant rules/regulations if required or from
other cases.
ACB_REM_48.
The
system
shall
maintain
documents/policies/rules/regulations
a
centralized
etc.
(Please
repository
refer
to
of
all
such
requirements
of
“management of documents” for details)
d) Legal and Prosecution System Module
Legal and prosecution module is required to
·
·
·
·
Maintain details of all cases filed by ACB
Record all proceedings pertaining to each case
Maintain records of expenditures incurred by ACB for various cases
Send email alerts to associated stakeholders for various activities related to proceedings of the
cases.
Requirement Id
Requirement Description
System Login & Access
ACB_LEG_1.
The system shall be accessible to the internal user, as per access roles suggested
by ACB for Legal and Prosecution.
Seal & Signature of the Auth. Sign.
Page 107 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Requirement Id
Requirement Description
Access
ACB_LEG_2
Internal Bureau user as per the user role specified by the ACB for various
components of ACBMS
·
·
·
·
Deciding Authority
Verification Authority
Enquiry Officer
Legal Officer
Case Details
ACB_LEG_3.
The Indicative Case details related fields include:
·
·
·
·
·
·
·
·
ACB_LEG_4.
Date
Case Type
Court Case No
Court Details
Petitioner Details and contact number
Respondent
Endorsement of anticorruption Act details
Petition details etc.
The system should authorize designated user to associate relevant section of Indian
Panel Code Act, Crime Procedure Code Act, and Indian Civil Code
Act, to the FIR
from a master available for all relevant sections of applicable acts and their details.
ACB_LEG_5.
The system should provide work flow to enable different review levels before
finalization of case petition.
ACB_LEG_6.
A Note sheet in line with format used by the Bureau should be attached with each
case which shall record all proceedings/meetings/decisions related to the case and
will exist throughout the lifecycle of the case. Authorized users should only be
allowed to provide inputs to note sheet. No user should be allowed to modify any
already existing content in the note sheet.
ACB_LEG_7.
The system shall allow ACB to raise case filing requests to Legal cell and provide
relevant information like complaint number, complainant details, case in charge
details, petitioner details , FIR details, PE details etc. in the format used by ACB and
Legal.
ACB_LEG_8.
Through centralized web based electronic form, an authorized user should be able to
provide/modify/update case details in the system.
Indicative list for fields to be
captured is provided in ‘Fields to be captured’ subsection. However details to be
captured shall be finalized in consultation with the Bureau.
Association of counselor
Seal & Signature of the Auth. Sign.
Page 108 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Requirement Id
Requirement Description
ACB_LEG_9.
The system should allow authorized user to centrally capture and access details of
counselors empanelled with ACB.
ACB_LEG_10.
Indicative details to be captured regarding empanelled counselors:
·
·
·
·
·
·
·
ACB_LEG_11.
Name
Contact Details
Address
Email id
Areas of specialization
Key cases handled
Empanelment number etc.
The system should allow authorized user to associate various counselors/change
counselor to the case.
ACB_LEG_12.
The system should allow authorized user to record professional fee of the counselor
for each case.
ACB_LEG_13.
The system should generate unique case identity number for each case submitted in
the system.
ACB_LEG_14.
The system should allow authorized user to create links/references to relevant
documents, complaint number, and FIR number to be attached to the case.
ACB_LEG_15.
The system should allow authorized user to configure system for uploading/
processing/closing/ archival of the case in the system.
ACB_LEG_16.
The system should allow authorized user to record each update/ proceeding/
decision/ comment on the case in the system.
ACB_LEG_17.
All communications, remarks, reviews, recommendations, approvals, rejections,
disposals should be recorded in the system and available for preparer/ approver/
reviewer or any other designated officer as per assigned authority for view and
providing comments.
ACB_LEG_18.
Each communication, notification, comments should be referenced uniquely under a
complaint number and should be retrievable based on combinations like date,
complaint number, comment number or user id, user name etc.
ACB_LEG_19.
The system should allow search of activities, comments, notifications, documents etc
related to a case based on multiple search parameters.
ACB_LEG_20.
The system should allow inter referencing of cases.
ACB_LEG_21.
The system should allow marking cases as repeat cases based on various
parameters such as repeat case against someone or repeated case by same
complainant etc.
ACB_LEG_22.
The system should allow authorized user to search cases based on various
parameters such as complainant/ name of the person against whom case is filed etc.
ACB_LEG_23.
The system should allow system enabled system to change the counsel during any
time during processing of the case on submission of mandatory approvals required
by various senior stakeholders.
Seal & Signature of the Auth. Sign.
Page 109 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Requirement Id
Requirement Description
Case Proceeding
ACB_LEG_24.
The system should allow authorized user to record different stages of cases e.g.
petition filed, evidence, personal hearing, closed, appeal file etc.
ACB_LEG_25.
The system should allow authorized user to record next case hearing date and
further allow association of internal staff to the case who shall be designated to
attend the hearing.
ACB_LEG_26.
The system should automatically generate SMS/email notification to the councilor
and other staff associated with the case, X days in advance to inform/remind about
hearing date. Periodicity and frequency of communication shall be finalized in
discussion with the Bureau.
ACB_LEG_27.
The system should allow authorized user to record and update proceeding of all
legal cases according to hearing date proceedings and maintain a non editable
chronological order of the same.
ACB_LEG_28.
The system should provide document management for attachment of evidence,
statement, affidavit, reply of opponent, and other documentary proof related to the
case. Allowable type of documents shall be as stated in Complaint Registration
Module.
ACB_LEG_29.
The system should allow authorized user to maintain a list of court cases pending in
the different courts.
ACB_LEG_30.
The system should allow authorized user to record the interim orders passed by the
court in each case.
ACB_LEG_31.
The system should allow authorized user to record the final judgment in a case and
the report on compliance of the order of the Court.
ACB_LEG_32.
The system should allow authorized user to record whether opinion is required from
counsel for moving a superior court for appeal. If yes, he should be able to generate
a communication/generate a system activity for the same.
ACB_LEG_33.
In line with the final decision the “suspect” information should be updated in “Suspect
Database” e.g. If as per final decision, suspect/accused is not proved guilty then
system should allow designated authority to update suspect status to “released of all
charges” in database etc.
MIS
ACB_LEG_34.
The System should provide suitable MIS to designated officer at predefined
periodicity. These MIS should have parameters to configure option to be delivered
through email, or dashboard, or access by the designated user. Indicative but not
Seal & Signature of the Auth. Sign.
Page 110 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Requirement Id
Requirement Description
comprehensive list of MIS include:
·
·
·
·
·
·
·
·
·
·
7.1.2.
Pending case related reports
Court wise cases
Hearing date wise cases
Closed case related reports
Cases pending with court
Status/Stage wise reports
Councilor wise reports
Expenditure reports
Reopened case related reports
Petitioner related reports etc.
Other functional and non-functional requirements
a) System login and access control
Requirement
Requirement Description
Id
REQ_GEN_1
Through the web portal the system should have a provision for creating unique login ID
for users on provision of certain mandatory details such as Name, Bureau, Employee
code, Designation, Location, Office Address, Residential Address, Contact Details, Email
id etc. as finalized in discussions with the Bureau.
REQ_GEN_2
The system should provide access rights and privileges according to login ID and
password. The rights and privileges allowed to that user should be as per Bureau
guidelines and policies.
REQ_GEN_3
The system should allow authorized users to access various functions, forms, screens,
sub modules, information etc. as per the authorizations and user roles permissible by the
Bureau as per guidelines and policies of the Bureau.
REQ_GEN_4
The system should allow single sign on to all components as per rights and privileges of
the user.
REQ_GEN_5
The system should have a mechanism for resetting and emailing the new password to
the user’s registered email ID, in case one forgets his password.
REQ_GEN_6
The system must prompt the user to change the password on the first login.
REQ_GEN_7
The system shall as a part of registration establish challenge and responses
mechanisms for session validation for future online sessions. Details such as a
username and password, challenge question and response answer should be asked if
login details are forgotten etc.
Seal & Signature of the Auth. Sign.
Page 111 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Requirement
Requirement Description
Id
REQ_GEN_8
The system shall apply spam control measures like ‘captcha’ images during registration
to avoid spurious details being automatically submitted and ensure that data is not
submitted by non-humans.
REQ_GEN_9
The system shall maintain non editable audit trail of all activities carried out by any user
in ACBMS.
b)User Dashboard
Requirement
Requirement Description
Id
REQ_GEN_1
Each user of ACBMS (Bureau user or Applicant/Registered User) should have a
customized dashboard view on logging into Solution. Key sections should include:
·
·
·
·
·
·
REQ_GEN_2
Activities pending
Activities assigned
Key MIS
Email
Notifications
Link to allowable modules/activities for particular user etc.
The interface shall give flexibility to toggle between graphical and tabular view and tile
different windows in the same interface.
REQ_GEN_3
Customized dashboard should allow authorized user to take action on activities pending
with him in a secured manner in a system seamlessly integrated with other relevant
modules like portal, document management and other modules of the application.
Submission of every activity in the system should suitably update required
tables/databases at the backend. There should be no/minimum data redundancy.
c) Web Portal
Requirement
Requirement Description
Id
REQ_GEN_1
SI shall be required to develop a web portal for ACB which shall be user friendly,
informative, interactive and easily accessible. It should have following sections
(indicative):
·
·
·
Overview about the ACB
Brief statistics about the Bureau
Administrative setup of the ACB
Seal & Signature of the Auth. Sign.
Page 112 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Requirement
Requirement Description
Id
· Access to various literature related to rules and regulations
· Feedback centre
· Contact us
· News section
· Notification section
· Access for users to register themselves and file online complaint
· Link for bureau users to access various modules of ACBMS
· Link for administrators for various modules/components of ACBMS including
components for security, database, user administration etc.
· Information related to Rights to Information Act that may be required to be made
public.
· Information about various acts and sections relevant to ACB related services.
· Citizen charter
· MIS reports for citizen, Bureau and identified stakeholders.
REQ_GEN_2
All the sections of the web portal should be of dynamic nature and must be supported
with easy content management and administration of the same.
Solution Login
REQ_GEN_3
The system should be accessible to following roles:
·
·
Bureau user: For carrying out bureau related activities in ACBMS solution.
Public user: For viewing content on bureau website which shall made available
public viewing.
Registered user: A public user becomes a registered user on applying through
available link for registration on website.
Complainant: A registered user becomes a complainant once he/she chooses to
submit a complaint.
Admin user: To carry out administration related activities in Solution for various
components and modules of ACBMS.
·
·
·
Access
REQ_GEN_4
The web portal should be made accessible to Public user/Registered user over Internet
and to Bureau users and various other entities related to Bureau/ Admin through
intranet/internet. Except Public user with rights to view public content available on the
website of the Bureau, rest all types of users shall enter solution through secured User Id
and Password. Wherever biometric/digital signature needs to be integrated to the
solution for sensitive information access, it shall be suitably provisioned.
User Registration
REQ_GEN_5
For Bureau user registration following indicative fields should be captured:
· Name
· Contact Details
· Email id
Seal & Signature of the Auth. Sign.
Page 113 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Requirement
Requirement Description
Id
·
·
·
·
REQ_GEN_6
Phone Number
Department
Designation
Employee number etc.
For registration of public user following indicative fields should be captured:
· Name
· Contact Details
· Email id
· Phone Number
REQ_GEN_7
For registration of other department user following indicative fields should be captured:
· Name
·
·
·
·
·
·
Contact Details
Email id
Phone Number
Department
Designation
Employee number etc.
REQ_GEN_8
The system should allow each user to create only a unique user name.
REQ_GEN_9
The system should provide a feature to the authorized user to search a valid user based
on various parameters.
REQ_GEN_10
The system should provide a facility to block or unblock any user.
REQ_GEN_11
The system shall display the date and time of last login when the user logs in.
REQ_GEN_12
The system should allow admin user to create/modify a user’s roles and privileges as per
requirements of the ACBMS including capturing information like
· Offices (HQ/ Range Office/ Outpost Office)
· User roles
· Default rights
As far as possible, information captured in Solution should be parameterized.
REQ_GEN_13
The system should allow a user to access various functions, forms, screens, sub
modules, information etc as per the authorization and user role permitted by the bureau
as per guidelines and policies of the bureau.
REQ_GEN_14
The system should provide access rights and privileges according to rights and
privileges allowed to that user as per bureau guidelines and policies.
REQ_GEN_15
The system should have a mechanism for resetting and emailing the new password to
the user’s registered email ID, in case one forgets his password.
Seal & Signature of the Auth. Sign.
Page 114 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Requirement
Requirement Description
Id
REQ_GEN_16
They system must prompt the user to change the password on the first login.
REQ_GEN_17
The system should give a warning if user with similar email id is already exist
REQ_GEN_18
The system should provide facility to block or unblock any user access
REQ_GEN_19
The system shall as a part of registration establish challenge and responsive
mechanisms for session validation for future online sessions. Details such as a
username and password, challenge question and response answer should be asked if
login details are forgotten etc
REQ_GEN_20
The system shall apply spam control measures like ‘captcha’ images during registration
to avoid spurious details being automatically submitted and ensure that data is not
submitted by non-humans
REQ_GEN_21
The Portal should provide access to following common information to all users
·
·
·
·
·
·
·
·
·
·
·
·
·
·
·
REQ_GEN_22
Overview about the ACB
Brief statistics about the bureau.
Administrative setup of the ACB
Access to various types of forms/applications
Access to various rules and regulations related literature
Feedback centre
Contact us
News section
Notification Section
Access for users to register themselves and apply for various
schemes
Link for bureau users to access various modules of ACBMS
Link for administrators for various modules/components of ACBMS
including components for security, database, user administration etc.
Information related to Rights to Information Act that may be required
to be made public.
Citizens charter
MIS reports for citizen, bureau and identified stakeholders.
Privilege access should be given to users other than public/citizen for
·
·
·
·
Content Management
Central repository management
ACBMS modules management
Management of other components of ACBMS.
REQ_GEN_23
The system should publish policies, procedure and Anti Corruption Act
REQ_GEN_24
The System should publish standard template being used by the Bureau for Factual
Seal & Signature of the Auth. Sign.
Page 115 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Requirement
Requirement Description
Id
Report, Source Information Report, Verification Report, finding report, office order, inter
office communication etc. as per formats of the Bureau.
REQ_GEN_25
The system should allow authorized user to create site navigation index through a
dynamic menu option. A common navigation bar should be included on all pages.
REQ_GEN_26
The system should allow users to discuss issues within the community as well as sharing
of information within a common platform.
Web Content management
REQ_GEN_27
The system should allow authorized user, through a user friendly GUI, to manage/edit
the content of the various web pages. It shall allow authorized user to manage and
maintain content of website in an efficient manner. User should be able to perform
advanced update maintenance jobs on website content with minimal technical
knowledge on website development.
REQ_GEN_28
The front end user interface must be integrated with content management solution for
easy management and change of theme design.
REQ_GEN_29
The system should allow authorized user, through a user friendly GUI, to design and
create a web page dynamically and publish it through an approval system. WCMS
should provide feature to define the position of the web page like centre frame, left frame
or right frame etc.
REQ_GEN_30
The system should allow authorized user, through a user friendly GUI, to access web
pages directory with facility to publish or block a web page
REQ_GEN_31
The system should allow authorized user, through a user friendly GUI, to create meta tag
search of each web page.
REQ_GEN_32
WCMS should allow authorized user to upload any image on the page and further allow
him to define position of the image on web page
REQ_GEN_33
The system should allow authorized user, through a user friendly GUI, to publish content
both in Hindi and English.
Hindi content may include
·
·
·
·
Static content
Labels/Headings etc in Hindi
Entering translated text in Hindi for data provided in English e.g. name may be
entered both in English as well as Hindi by the applicant if he may choose to.
However entry of name in English shall be mandatory. The language for
transactions shall primarily be English. However search / filter options etc may
be provided for Hindi as well.
Generating reports/letters etc in Hindi.
Seal & Signature of the Auth. Sign.
Page 116 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Requirement
Requirement Description
Id
REQ_GEN_34
The system should allow the user for meta tag basis search option. The search result
should show path of the web page with brief description of the page or else first 20-30
words of the page. Solution should further allow drill down to the page.
REQ_GEN_35
The system should allow authorized user to publish bureau news, office circulars etc.
The news should comprises minimum following details:
· News Heading
· Date of publication
· News source
· Reported by
· News room
· News search key word
· News main content
REQ_GEN_36
The system should provide facility to attach image related to news
Event Calendar
REQ_GEN_37
The web portal should provide facility to upload event details being organized by bureau
including details such as:
· Event name
· Event type
· Date of event
· Start time- end time
· Event description
· Reported by
· Detail event program schedule
· Event organized by
· Target group
· Registration process
· Fee if any
REQ_GEN_38
The system should provide facility to a registered user for online registration for event.
REQ_GEN_39
The system should allow authorized user to be able to design custom look and feel of the
portal with minimal change in software code.
REQ_GEN_40
The system should adhere to standard programming practices that can help authorized
user to easily extend the functionality of the portal.
REQ_GEN_41
The system shall provide compatible interfaces, metadata and indexing support for
exchange of electronic documents with Scanner APIs, digital imaging programs and
document management.
Seal & Signature of the Auth. Sign.
Page 117 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Requirement
Requirement Description
Id
REQ_GEN_42
All forms made available in the solution shall be created on standard A4 paper (as
defined by standard ISO 216: 2007)
REQ_GEN_43
All kinds of notifications whether internal or external through channels such as email,
letter shall be recorded by the system.
REQ_GEN_44
All kinds of notifications shall be assigned a designated user to whom response will be
communicated. The response shall be automatically routed to the designated user.
REQ_GEN_45
All notifications / alerts / reminders shall be as per as a standard format/ template that is
configurable by a user.
REQ_GEN_46
The system shall have a fail-proof online modification/submission process.
REQ_GEN_47
The system shall ensure virus check for all files that are uploaded in Solution e.g. detect
malicious executables.
REQ_GEN_48
Where ever documents are involved, the system shall allow the user to assign a
note/annotation to a document image.
REQ_GEN_49
Where ever system solutions are involved, System shall be designed in such a manner
that introduction of additional system requirements or changes to existing system can be
implemented without underlying architectural or programming changes to Solution.
REQ_GEN_50
The system shall provide consistent look & feel to the users and the standards defined
for content, structure and presentation of the portal shall be applied and followed
throughout the portal.
REQ_GEN_51
The system shall provide Metadata directories or indexes of data related to the data
available within the application to facilitate search.
d)Integration with SMS and Email Solution
Requirement
Requirement Description
Id
REQ_GEN_1
Wherever required, modules of ACBMS should have integration with a SMS solution for
sms based communication to users/applicants.
REQ_GEN_2
Wherever required, modules of ACBMS should have integration with a Email solution for
email based communication to users/applicants
7.1.3.
Additional Requirements
S No.
Business Requirement Description
Solution Wide Functionalities
REQ_GEN_1
The system shall support consistent, globally unique naming and addressing scheme
for data made centrally and automatically/systemically.
Seal & Signature of the Auth. Sign.
Page 118 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
REQ_GEN_2
The system shall allow user to manage data independently of the processes that
create or use that data.
REQ_GEN_3
The system shall allow user to format output to support HTML, XML, text and any
other format required for data exchange/integration with various entities involved in the
process.
REQ_GEN_4
The system shall allow user to scale up or scale out solution with easy to use GUI.
REQ_GEN_5
Application shall be designed to permit user for easy insertion of new modules and
new enhancements.
REQ_GEN_6
Application shall have the capability to complete all requests (e.g. store, retrieve,
update, etc.) without any data loss.
REQ_GEN_7
Application shall have a system of record for legal purposes and shall maintain an
audit file in chronological sequence of each transaction and all corresponding
corrections made during the transaction by clients or their facilitators.
REQ_GEN_8
Application shall be made possible to distribute the elements between different
premises.(only if required)
REQ_GEN_9
Distributed elements shall operate as a single integrated and cohesive solution.
REQ_GEN_10
The system shall have the capability to organize and store all data for aggregation and
analysis.
REQ_GEN_11
The system shall accommodate usage growth with minimal disruptions.
REQ_GEN_12
Application shall be designed to accommodate growth in data rates and volumes for
communications, networks, hardware and storage.
REQ_GEN_13
Application shall have the capability to remotely maintain and upgrade.
REQ_GEN_14
Application shall use open systems/ standard-based architecture to meet functional
requirements and to inter-operate with existing/envisaged solutions.
REQ_GEN_15
Application shall facilitate the development of applications; application platform’s
enabling services shall consist of well-defined Applications Program Interface (API).
Solution Management Requirements
REQ_GEN_16
The system shall incorporate interfaces for authorized users for management
capabilities, which shall include: Configuration Management, Testing & Validation,
Fault Detection, Fault Isolation, Fault Recovery, Data collection, Data Analysis.
REQ_GEN_17
The system shall provide reports and MIS to authorized user for end-to-end
performance monitoring and control.
REQ_GEN_18
The system shall maintain knowledge of current operational status of all elements for
Seal & Signature of the Auth. Sign.
Page 119 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
retrieval/use by authorized user.
REQ_GEN_19
The system shall establish and maintain accounting information on communications
used.
REQ_GEN_20
The system shall support end-to-end Solution fault isolation of all provided services,
including the capability to identify a failing node, element, and/or service, to the level
necessary to correct the fault.
REQ_GEN_21
The system shall provide capability to manage fault isolation functions.
REQ_GEN_22
The system shall provide data quality determination and analysis, error correction,
recovery processing, and related quality control procedures and processes.
REQ_GEN_23
The system shall provide for support of coordinated management of elements
distributed between different premises.
REQ_GEN_24
Application shall implement applications and infrastructure components to permit
management to monitor and measure the effectiveness.
REQ_GEN_25
Application shall permit inclusion of new or modified requirements during the life of
application with appropriate established change control procedures.
Operational Requirements
REQ_GEN_26
Application shall be accessible to users 24 hours per day, 7 days per week on a
continuous basis.
REQ_GEN_27
Data inputs to the application shall be validated prior to being processed
REQ_GEN_28
Input data shall be validated for out of range values.
REQ_GEN_29
Input data shall be validated for missing or incomplete data.
REQ_GEN_30
Input data shall be validated for unauthorized or inconsistent control data.
REQ_GEN_31
Input data shall be validated for values or volumes that are exceptional to the norm.
REQ_GEN_32
Invalid input data shall be rejected and security incident shall be initiated.
REQ_GEN_33
Integrity checks functionality on any data generated by solution shall be provided.
REQ_GEN_34
Functionality necessary for scheduling of Application to certain days, dates or time of
day, shall be provided.
REQ_GEN_35
Functionality necessary for 'roll back' or recovery routines if applicable fails to operate
as planned shall be provided
Human Engineering Requirements
REQ_GEN_36
The system shall provide a menu driven screen interface permitting a user to navigate
easily through the different functions of Solution.
Seal & Signature of the Auth. Sign.
Page 120 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
REQ_GEN_37
The system shall provide users with access to information management services at
their premises.
REQ_GEN_38
The user interface shall be tailored to functions, which are authorized for the user.
Logs
The following operations shall be logged by means of automatic (machine generated)
logs:
REQ_GEN_39
Logs shall include process start and finish times.
REQ_GEN_40
Logs shall include Application faults, errors and recovery processes.
REQ_GEN_41
Logs shall include the use of any privileged passwords.
REQ_GEN_42
Logs shall include the use of any privileged utilities.
REQ_GEN_43
Logs shall include automatically generated data necessary to assess the application
performance.
REQ_GEN_44
The frequency of logs generation shall be mutually agreed upon, in order to be
consistent with the ability to trace appropriate actions of the application.
REQ_GEN_45
Logs shall include all log-ones and log-outs as well as all attempts (whether
successful or not) to log-on
REQ_GEN_46
Logs shall have appropriate mutually agreed upon retention period.
REQ_GEN_47
The log generating software shall prohibit amendment of log details and disabling of
the recording of events.
REQ_GEN_48
The log generating software shall include review of log-on patterns to determine
potentially abnormal Solution use.
REQ_GEN_49
Files of logged events shall be protected from amendment or deletion.
REQ_GEN_50
Logging process shall always be enabled except when explicitly disabled by a
supervisor role. Controls shall be in place to prevent the logging process from being
disabled.
Security Requirements
REQ_GEN_51
Application shall prevent unauthorized users from accessing Solution.
ACB_SYS_1.
The system should have facility to restrict user access to:
·
Module Menus
·
Sub- menus
·
Screens
·
Fields
Seal & Signature of the Auth. Sign.
Page 121 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
·
Reports
·
Combination of the above
·
Search
ACB_SYS_2.
For login for internal user application shall provide biometric authentication system,
ACB_SYS_3.
The system should support terminal based logins I.e. a user cannot log on to the system
from any terminal apart from what is specified in the parameter for him / her.
REQ_GEN_52
Application shall make data available to the authorized users in an expedient and
secure environment
ACB_SYS_4.
If access is denied following repeated unsuccessful logon attempts, this shall be treated
by the application as a security incident and handled accordingly.
ACB_SYS_5.
The System to define Maximum Inactive Time after which a user should be
automatically logged out of the system.
REQ_GEN_53
Application shall provide access monitoring to compile and report security violations
and attempted security violations.
REQ_GEN_54
Application shall have the thorough capability to a log record of an unauthorized
attempt.
REQ_GEN_55
Application shall provide physical and remote access control to components.
REQ_GEN_56
Application shall implement controls to ensure the privacy of information, individuals,
and corporations are not compromised.
REQ_GEN_57
Application shall use audit controls, electronic signatures, data encryption and other
methods to assure the authenticity of transaction and other relevant data.
REQ_GEN_58
Application database management security services shall include access control (e.g.,
Discretionary Access Control (DAC), Mandatory Access Control (MAC), contentdependent and context dependent access control), individual user identification and
authentication (I&A), data confidentiality, data integrity (e.g., entity integrity, referential
integrity, and label integrity), security audit, object reuse, availability of service and
data, and other security services.
REQ_GEN_59
Application shall implement controls to ensure the authenticity of data is preserved.
REQ_GEN_60
Application shall integrate seamlessly with Digital Signature solution wherever
required.
REQ_GEN_61
Application shall comply with the Application Security Plan and security guidelines of
each of the stakeholder involved.
REQ_GEN_62
Application shall adhere to guidelines for physical, personnel, computer,
communications, and internal data security.
Seal & Signature of the Auth. Sign.
Page 122 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
REQ_GEN_63
Application shall be foreseen of user registration Solution allowing: distinguishing
different user roles; authorization of users;
REQ_GEN_64
Application shall be foreseen with an access control policy functionality allowing
access of users in different roles to different functionalities of Application. At least the
following roles shall be introduced for Application: Supervisor, Operator, Solution
support, User
REQ_GEN_65
Only registered users shall be allowed to log-in to the application.
REQ_GEN_66
Registered users shall be allowed to log-on only to those Application functions which
they are authorized to access and use.
REQ_GEN_67
Registration of users in their respective roles shall be valid only for a limited period of
time, where after their authorization shall be re-confirmed and prolonged.
REQ_GEN_68
The logon processes shall display only the minimum amount of information to assist
users.
REQ_GEN_69
The logon processes shall prohibit the display of help screens.
REQ_GEN_70
The logon processes shall minimize the opportunities for unauthorized connections to
application.
REQ_GEN_71
The logon processes shall prohibit the display of the solution or the application details
until the process has been successfully completed.
REQ_GEN_72
The logon process shall deny access if either the username or password is invalid
without identifying the specific erroneous element.
REQ_GEN_73
The logon process shall allow only a fixed number of logon attempts before disabling
the terminal.
REQ_GEN_74
If access is denied following repeated unsuccessful logon attempts, this shall be
treated by the application as a security incident and handled accordingly.
REQ_GEN_75
The logoff procedure shall clear any screen displays prior to terminating the
application.
REQ_GEN_76
Application shall disallow simultaneous logon by the same user.
REQ_GEN_77
Passwords to log-on to Application (and additional access control devices) shall have
at least the length of 8 characters. The password management solution shall require
the enforcement of a minimum password length.
REQ_GEN_78
The password management solution shall require the use of quality (i.e. difficult to
guess) passwords.
REQ_GEN_79
The password management solution shall require the enforcement of a password
change after a 3 months’ period.
Seal & Signature of the Auth. Sign.
Page 123 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
REQ_GEN_80
The password management solution shall include non-display of the password when
being entered.
REQ_GEN_81
The password management solution shall require the storage of passwords in
encrypted form.
REQ_GEN_82
For all security incidents alarm functionality shall be implemented, which immediately
informs the supervisor role of these incidents.
REQ_GEN_83
Application shall treat the following events as security incidents: unsuccessful log-on,
intrusion detection, malfunctioning of encryption facility
Legal and Regulatory Requirements
REQ_GEN_84
Application shall provide flexibility to easily modify Solution to handle changes in trade
laws, regulations, and license & permit requirements.
REQ_GEN_85
Application shall have the capability to search and analyze payment transactions.
Interface Requirements
REQ_GEN_86
Seam less integration / interfacing with existing/proposed applications.
Testing Requirements
REQ_GEN_87
Application shall support operations and testing concurrently.
REQ_GEN_88
Application shall provide tools and metrics to support testing, solution performance
monitoring, fault isolation, verification and validation of the end-to-end solution.
Common Technical Requirements
REQ_GEN_89
The system shall have ability to customize user menus and screens based on user
access authority.
REQ_GEN_90
The system shall be able to archive transactional database records to prevent long
term speed concerns. Solution must also feature functionality for efficient retrieval of
archived data.
REQ_GEN_91
The system shall be capable of generating event notifications and interfacing with Email Solution and must support e-mail triggers as part of system.
REQ_GEN_92
The system shall provide a report-writing tool, which can be used to generate
customized reports at any level.
Enquiries and Grievance Redressal Services
REQ_GEN_93
The system shall be able to provide a list of "Frequently Asked Questions" to the user
REQ_GEN_94
The system should allow users to log enquiries and grievances through an online web
Seal & Signature of the Auth. Sign.
Page 124 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
application / allow help desk personnel to take relevant actions.
REQ_GEN_95
The system shall be able to capture enquiries and grievances through an electronic
form.
REQ_GEN_96
The system shall be able to associate an enquiry or a grievance with a past request
similar request.
REQ_GEN_97
The system shall generate a unique case number for the grievance which can be used
for tracking purposes.
7.1.4.
Integration Requirements
ACB has envisaged certain systems that shall be developed in near future. SI should provide suitable
connectors/interfaces of APIs for integration with the existing and envisaged IT systems. List of these
systems is as follows:
Application
Status
Personal
Envisaged
Integration
Data
Requirements
methodology
Integration
may
required
Management System
consolidated
certain
exchange
be
Flat
for
services
or
exchange
MIS
files/
for
Web
Data
parameters
required for Employee
master/Designation
Master
Integration
with
Envisaged
CCTNS
System should provision
Flat
for
State
files/
integration
with
services
CCTNS
and
exchange
Nation
for
Web
Data
CCTNS
database for uploading
of content related to
FIR,
and
subsequent
update on case status
Integration with UIDAI
Envisaged
System should provision
for
integration
with
UIDAI system in terms
of
·
files/
services
for
Web
Data
exchange
Using Aadhaar and
demographic/biom
etric authentication
for identification
Complying
Seal & Signature of the Auth. Sign.
Flat
to
various
Page 125 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
standards
and
compliance
requirements of various
components in line with
guidelines
issued
by
UIDAI
Integration
with
Envisaged
SUGAM
Seal & Signature of the Auth. Sign.
System should provision
for
integration with
State
SUGAM
application as citizens/
departments also file
complaints which are
then forwarded to the
bureau for it to proceed
Flat
files/
services
for
Web
Data
exchange
Page 126 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.2 ANNEXURE 2 –BILL OF MATERIAL (BoM)
1
Following are minimum and indicative requirements. The bidder is expected to provide
complete list of Bill of Materials proposed to fulfil the stated requirements in the RFP.
2
The bidder should propose the bill of material such that the same technology, make,
model, family of products are implemented at all sites. The bidder should ensure
standardization at unit building blocks. The entire architecture is minimized in order to
improve the management of the overall solution and scope of future expandability.
3
The bidder should offer latest and proven technologies that are available for items. All
hardware and software provided by the bidder should be new and not purchased more
than two months prior to the supply to ACB/RISL.
4
The power supplies, cables/connectors for all equipments should be for Indian power
specifications of voltage, frequency and phasing.
5
The bidder has to propose hardware to meet all the minimum performance and SLA
requirements and accordingly propose the solution.
Seal & Signature of the Auth. Sign.
Page 127 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
INDICATIVE BILL OF MATERIALS
A) RSDC, Jaipur
S.No Name of item
Document Management System client user licence
1. (in case of share point /Omni doc) based on
number of users
B) Head Quarter (HQ), ACB, Jaipur
S.No Name of item
1.
Desktop Computer ( incl. OS + AV + MS Office
Standard Indic Latest edition ( with media))
Qty
Technical
Specification
Ref
---
70
Qty
5
Technical
Specification
Ref
Item No 1(a)
2. Tablet Devices
8
Item No 2
3. MFD Printer (B/W) A4 Size
5
Item No 3
4. 800 VA UPS
5
Item No 4
5. L2 Manageable Switch -24 Port
3
Item No 5
6. Passive work – structure cable –UTP (indicative)
7. Passive work- Panel along with 19U Rack
8.
PVC Conduits and Laying of PVC conduits/UTP
cable
9. Biometric Authentication Device
300
Mtr
Item No 6/1
3
Item No 6/2
100
Mtr
Item No 6/3
10
Item No 7
C) Range Office
S.No
Name of item
Qty
1.
Desktop Computer ( incl. OS + AV + Open Office)
18
2.
MFD printer (B/W) A4 Size
8
Item No 3
3.
800 VA UPS
18
Item No 4
4.
L2 Manageable Switch – 24 Port
8
Item No 5
Seal & Signature of the Auth. Sign.
Technical
Specificatio
n Ref
Item No 1
(b)
Page 128 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Passive work – structure cable –UTP (indicative)
600
Mtr
6.
Panel along with 19U Rack
8
7.
Passive work –I/O (Information outlet)
50
Item No 6/3
8.
Passive work –patch cord (Average 7 ft )
50
Item No 6/4
9.
PVC Conduits and Laying of PVC conduits/UTP 200
cable
5.
Item No 6/1
Item
No
6/2
Item No 6/5
The above is the requirement for all the Range Offices
D) Outpost Offices
S.No Name of item
Qty
1. Desktop Computer ( incl. OS + AV + Open Office)
36
Technical
Specification
Ref
Item No 1 (b)
2. MFD printer (B/W) A4 Size
35
Item No 2
3. 800 VA UPS
36
Item No 4
4. L2 Manageable Switch – 24 Port
35
Item No 5
6. Panel along with 19U Rack
1700 Item No 6/1
Mtr
Item No 6/2
35
7. Passive work –I/O (Information outlet)
110
Item No 6/3
8. Passive work –patch cord (Average 7 ft )
110
Item No 6/4
9. PVC Conduits and Laying of PVC conduits/UTP
cable
500
Item No 6/4
5. Passive work – structure cable –UTP (indicative)
The above is the requirement for all the Outposts Offices
Seal & Signature of the Auth. Sign.
Page 129 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.3
1
ANNEXURE-3 – SUGGESTED TECHNICAL SPECIFICATIONS
All specifications are minimum and indicative required and have been provided for
immediate reference. Any alternative (make/model) suggested by Bidder must either meet
or exceed the specifications stated in terms of capacity, performance etc and must be
supported by suitable evidences depicting equivalence to stated specifications.
2
Bidder should ensure that none of the listed parameters are modified, deleted and no
additional parameter is added. (Remarks, if any, should be indicated separately in the
Remarks column)
3
In case the software proposed by the Bidder has multiple modules/components that are
priced and sold separately, the Bidder should use additional sheets for each such
module/component and include the licensing policy and number of licenses proposed for
the same in the respective sheets.
4
While there are no marks for compliance with specifications, any deviations shall be
evaluated by Purchaser and if found significant, Purchaser may reject the bid on the
grounds on technical non-compliance.
5
The contents in this document do not indicate an exhaustive 'Bill-of-Material' for the
requirements of purchaser. Bidders may add/ modify the components based on suggested
design as long as minimum requirements are met or exceeded.
1. (a) Desktops Computer
Sl.N
Parameter
Minimum Specifications Suggested
1.
Model
Offered
To be provided by bidder
2.
Make
Offered
To be provided by bidder
3.
Mandatory
Certification
s
4.
Processor
5.
Chipset
6.
Memory
7.
HDD
8.
Monitor
OEM – ISO 9001 Manufacturer,
Certified on supplied OS, DMI 2.0
compliance and support, Energy
Star 5, UL certification,
Intel Core i5-2400, 3.1 GHz, 6 MB
L3 Cache or higher
Intel H61 or better on Intel/OEM
Motherboard
4 GB 1333 MHz DDR3 RAM with 8
GB Expandability
500 GB 7200 Serial ATA HDD or
higher
47 cm (18.5 inch) or larger
TFT/LED Digital Color Monitor
TCO-05 certified.
o.
Seal & Signature of the Auth. Sign.
Specification Proposed
by Bidder
Compliance Y/N
Page 130 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Sl.N
o.
9.
Parameter
Minimum Specifications Suggested
Bays
3 Nos. or above.
10. Keyboard
11. Mouse
OEM Mechanical Keyboard with
104 keys
Optical with USB interface.
12. Optical
DVD RW (Min. 16x) or higher
Device
13. Cabinet
14. Ports
15. Network
Features
16. Multimedia
17. Power
Manageme
Operating
18. nt
System
19. MS Office
20. Antivirus
21. Warranty
Period
Specification Proposed
by Bidder
Compliance Y/N
Specification Proposed
by Bidder
Compliance Y/N
Micro ATX
6 USB Ports (with at least 2 in
front), 1 Serial audio port for
microphone and headphone in
front.
10/100/1000 on board integrated
Network Port with remote booting
facility, remote system installation,
remote wake up.
Integrated Audio and Graphic
Controller
ACPI (Advanced Configuration and
Power Management Interface)
Genuine latest Windows 7
professional SP1 (64 Bits)
preloaded with Media and
Documentation and Certificate of
Authenticity
Standard Indic Latest edition ( with
media)
Pre-installed & Norton/McAfee/
Kaspersky/trend micro /quick heal,,
Internet security and Antivirus
Software latest Version with 3
years subscription
Minimum 3 Years (Comprehensive
Onsite)
(b) Desktops Computer (for Range and Outpost)
Sl.N
Parameter
Minimum Specifications Suggested
1.
Model
Offered
To be provided by bidder
2.
Make
Offered
To be provided by bidder
3.
Mandatory
Certification
s
4.
Processor
OEM – ISO 9001 Manufacturer,
Certified on supplied OS, DMI 2.0
compliance and support, Energy
Star 5, UL certification,
Intel Core i3-2120, 3.3 GHz, 3 MB
Cache and 1066 MHz FSB or
higher.
o.
Seal & Signature of the Auth. Sign.
Page 131 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Sl.N
Parameter
Minimum Specifications Suggested
5.
Chipset
6.
Memory
7.
HDD
8.
Monitor
9.
Bays
Intel H61 or better on Intel/OEM
Motherboard
4 GB 1066 MHz DDR3 RAM with 8
GB Expandability
500 GB 7200 Serial ATA HDD or
higher
47 cm (18.5 inch)or larger
TFT/LED Digital Color Monitor
TCO-05
3
Nos. orcertified.
above.
o.
10. Keyboard
11. Mouse
OEM Mechanical Keyboard with
104 keys
Optical with USB interface.
12. Optical
DVD RW (Min. 16x) or higher
Device
13. Cabinet
14. Ports
15. Network
Features
16. Multimedia
17. Power
Manageme
Operating
18. nt
System
19. Office Suite
20. Antivirus
21. Warranty
Period
Specification Proposed
by Bidder
Compliance Y/N
Micro ATX
6 USB Ports (with at least 2 in
front), 1 Serial audio port for
microphone and headphone in
front.
10/100/1000 on board integrated
Network Port with remote booting
facility remote system installation,
remote wake up.
Integrated Audio and Graphic
Controller
ACPI (Advanced Configuration and
Power Management Interface)
Genuine latest Windows 7
professional SP1 (64 Bits)
preloaded with Media and
Documentation and Certificate of
Authenticity
Open office (With media)
Pre-installed & Norton/McAfee/
Kaspersky/trend micro /quick heal,,
Internet security and Antivirus
Software latest Version with 3
years subscription
Minimum 3 Years (Comprehensive
Onsite)
2. Tablet Device with GPRS
S.
Parameter
Minimum Specifications Suggested
1.
Make
To be provided by bidder
2.
Model
To be provided by bidder
No.
Seal & Signature of the Auth. Sign.
Specifications
proposed by
the Bidder
Remarks/
Deviations
Page 132 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
S.
Parameter
No.
Minimum Specifications Suggested
Specifications
proposed by
the Bidder
Remarks/
Deviations
2G GSM 850/900/1800 and 3G
HSDPA 850/900
TFT capacitive touch screen, 16M or
higher colors
3.
Network
4.
Display
5.
Body Size
6.
Display
7.
Memory
8.
Memory
9.
Data
10.
Bluetooth
v2.1 with A2DP
11.
WLAN
Should have Wi-Fi 802.11 a/b/g/n,
12.
CPU
13.
Messaging
Dual-core 1 GHz Cortex-A9
SMS ( threaded view), MMS, Email,
Push Email
241.2 X 185.7 X 8.8 mm or higher
768 x 1024 pixels, 9.7 inches or
higher
Card slot – microSD, upto 16 GB or
higher
Should have internal memory of –
16/32/64 GB storage, 512MB RAM
Should be GPRS and EDGE
compatible
3. Multi Functional Device Printer A4 Size
S.
Parameter
No.
Minimum Specifications
Suggested
1.
Model
Offered
To be provided by bidder
2.
Make
Offered
To be provided by bidder
Print speed
Up to 25 ppm (A4)
Print
Resolution
Up to 600 x 600 dpi
Duty cycle
Up to 8000 pages
Duplex print
option (A4)
Yes
Features
Print, Copy, Scan & Fax
Network
Enabled
Yes (min 10/100 mbps)
Energy Star
Yes
Standard
memory
Min. 128 MB
3.
4.
5.
6.
7.
8.
9.
10.
Seal & Signature of the Auth. Sign.
Specification
Proposed By Bidder
Compliance Y/N
Page 133 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
S.
Parameter
No.
11.
12.
13.
Minimum Specifications
Suggested
Processor
Speed
500 MHz or higher
Compatible
operating
systems
Accessories
All Windows Operating System
Specification
Proposed By Bidder
Compliance Y/N
USB & power cable
4. 800 VA UPS
S.
Features
Minimum Specifications
Suggested
1.
Model Offered
To be provided by Bidder
2.
Make Offered
To be provided by Bidder
3.
Mandatory
Certification
- ISO 9001 Series Manufacturer,
- Valid Test Certificate from any
Govt. Approved Test/ Certifying
Agency on Tendered Specs.
4.
Capacity
800 VA
5.
No. of Sockets
6.
Battery Make
7.
Battery backup
8
Cables
Min. 3 sockets for connecting
devices. (3 pin only)
2* 7AH, Battery should be
branded - ISO 9001 and 14001
certified
Minimum 30 minutes or more on
full load with Internal batteries
(both battry should be inside of
casing)
With necessary cable and plug
9
Warranty
Period
Minimum 3 Years
(Comprehensive Onsite)
No.
Specifications
Proposed by Bidder
Compliance Y/N
5. L2 24 Port Manageable Switch
S. No
Parameter
Minimum Specifications
Suggested
To be provided by Bidder
1.
Model
Offered
2.
Make
Offered
To be provided by Bidder
3.
Interface
10/100/1000 BASE-TX Ports : 16
Combo 10/100/1000 BASE-T/SFP
:2
RS 232 Console Port/RJ45 serial
Seal & Signature of the Auth. Sign.
Specification
Proposed by Bidder
Compliance Y/N
Page 134 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
S. No
Parameter
4.
Performance
5.
Layer-2
Features
6.
VLAN
7.
Quality of
Services
8.
Access
Control List
(Max 256
Profiles/Rule
s)
Minimum Specifications
Suggested
console port
Specification
Proposed by Bidder
Compliance Y/N
Switch Capacity : 48 Gbps or
more with non blocking
architecture
64-Byte Packet Forwarding Rate:
33.6 Mpps or more
MAC Address Table Size : 8k
IGMP Snooping v1,v2 (Up to 256
groups),IGMPV3
IGMP Snooping Fast leave
802.1D Spanning Tree
802.1w Rapid Spanning Tree
802.1s Multiple Spanning Trees
802.3x & Back-Pressure
802.3ad Link Aggregation (8Ports
per group/6
groups per device)
Should support Spanning Tree
Fast Forward | BPDU Filtering |
BPDU Guard | BPDU Forward |
BPDU Transparent | Loopback
Detection | Auto Edge Port
Port mirroring ( One to One, Many
to One )
Standard : 802.1Q
VLAN IDs: 4K
Dynamic VLAN groups : 128 or
higher
GVRP/MVRP/Equivalent
802.1p Priority Queues standard
Number of 802.1p priority
Queues: 4 Queues
Support WRR/Strict mode
Packet classification based on
Switch Port
VLAN ID
TCP/UPD Port number
MAC address
IPv4 +IPV6
802.1p Priority
TOS
DSCP
User defined Packet Content
Multi-Layer ACL based on :
Switch Port
VLAN ID
802.1p Priority
MAC address
IPv4
DSCP
Protocol type
TCP/UPD Port number
User defined Packet Content
Seal & Signature of the Auth. Sign.
Page 135 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
S. No
9.
Parameter
Network
Access/Secu
rity
10. Management
11. MIB Support
12. Physical &
Minimum Specifications
Suggested
RADIUS/TACACS+
Authentication for
Management Access
RADIUS Accounting for
Management Access
Port security (max.16MAC entries
per port)
802.1X Port-based Access
Control
802.1X MAC-based Access
Control
802.1X Guest VLAN
SSH v1, v2/ SSL v3
Traffic Segmentation
Broadcast Storm Control
Web-based GUI
CLI ( Command Line Interface )
Telnet client
TFTP client
SNMP v1,v2c, v3
Support for RMON 1/2 group as
and when required BOOTP/DHCP
Client
SNTP or NTP
SYSLOG
Dual image or fireware upgrade
through TFTP
/FTP server
Port description
Web GUI traffic/CPU Monitoring
SNMP trap on MAC notification
DHCP Auto Configuration
DHCP relay option 82
SMTP client ( e-mail notification
)externally/
Internally
MIBII ( RFC 1213 )
Bridge MIB ( RFC 1493 )
RFC 2011 SNMPv2 MIB for
IP,RFC 2013 SNMPv2MIB
for UDP
RMON MIB ( RFC 1757, 2819 )
802.1p MIB ( RFC 2674 )
IF MIB ( RFC 2233, 2863 )
RADIUS Authentication client
MIB(RFC 2620)
RADIUS Accounting client MIB
(RFC 2925)Private MIB
Internal/External Power supply
Specification
Proposed by Bidder
Compliance Y/N
Environment
al
6. Passive Work Components
Seal & Signature of the Auth. Sign.
Page 136 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
S.
Features
No.
1.
2.
3.
4.
Structure
Cable
(UTP cable)
Minimum Specifications
Suggested
Specifications
Proposed by Bidder
Compliance
Y/N
The UTP Cable Shall
meet the requirement w.r.t
maximum d.c resistance,
balance and unbalance,
maximum PR to GND
Capacitance and
attenuation losses as
applicable to the category
6,unshielded UTP Cable
and corresponding ASTM
Standards as mentioned
there in.
Cable shall have Standard
marking and designation
as applicable in line with
the international standard
such as CSA/UL. This
item shall be accepted
based on OEM certificate.
All specifications for
components & cabling to
be tested up to 250 MHz ,
UL *R listed & verified
24 port Patch
Panel
110 wiring block at rear
end & RJ 45 jack on front
panel, 19” rack mountable,
should confirm or
deviance exceed the
EIA/TIA 568 B standards
for CAT 6, Metallic /steel
high strength & 1U height,
confirm EIA/TIA 568 B
wiring pattern, should
have routing rings & ties
and labeling strips for
identification, UL *R Listed
& verified.
Information
outlets
Surface mount box with
single RJ 45 socket,
should confirm or exceed
the EIA/TIA 568 B
standards for CAT 6,
provision for dust cover,
labeling icons & strips,
anchors for stain relief
cable entry, UL *R listed &
verified
Patch Cord
Should confirm or exceed
the EIA/TIA 568 B
Seal & Signature of the Auth. Sign.
Page 137 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
S.
Features
No.
Minimum Specifications
Suggested
Specifications
Proposed by Bidder
Compliance
Y/N
Specifications
Proposed by Bidder
Compliance
Y/N
standards for CAT 6,
Factory molded boots on
RJ 45 plugs at both ends,
UL *R listed & verified,
Option for color – Grey,
Blue, Red & Green &
cross over cable
Length - 3 feet
Length – 10 feet
Length – 7 feet
5.
6.
PVC Conduits
OEM should be ISO 9001
certified
Laying of PVC
conduits/UTP
cable
Conduiting and channeling
of PVC conduits, casing
capping on the walls, I/O
fixing and termination at
both ends, cable laying of
UTP
7. Biometric Authentication Device
S.
Features
No.
1.
2.
3.
4.
5.
6.
7.
8.
Minimum Specifications
Suggested
Model Offered
To be provided by Bidder
Make Offered
To be provided by Bidder
Cable Length
Certification
Sensor
Image
Resolution
Image Size
Image
Grayscale
Min 1800 mm
FCC, CE
Optical
500 DPI
260 X 300 pixels
256 shades
Seal & Signature of the Auth. Sign.
Page 138 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
S.
Features
No.
9.
Light Source
Minimum Specifications
Suggested
Lifetime
(typical)
Min 50,000 hours
11.
Operating
Voltage
5 V from USB Port
12.
Supporting
Operating
System
Windows 98/Me/
NT4/2000/XP/Vista/7
Interface
Compliance
Y/N
Red LED
10.
13.
Specifications
Proposed by Bidder
USB 2.0
14.
Communicatio
n Speed (max)
12 Mbps
15.
Verification
Time
Less than 1 Sec.
16.
Auto On
Function
Yes
17.
Hardened
contact area
Yes
Seal & Signature of the Auth. Sign.
Page 139 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.4
ANNEXURE-4 - COVERING LETTER OF THE BID
(To be submitted on the Company Letter head of the Tenderer, sealed and signed)
To,
Managing Director,
RajCOMP Info Services Limited (RISL),
First Floor, Yojana Bhawan, Tilak Marg,
C-Scheme, Jaipur (Rajasthan)
Dear Sir,
Ref: Request for Proposal (RFP) Notification dated............... No..........
1.
I/We, the undersigned bidder, Having read & examined in detail, the Bid Document, the receipt of
which is hereby duly acknowledged, I/ we, the undersigned, offer to supply/ work as mentioned in
the Scope of the work, Technical specifications, Service Level Standards & in conformity with the
said bidding document for the same.
2.
I/ We hereby declare that our bid is made in good faith, without collusion or fraud and the
information contained in the bid is true and correct to the best of our knowledge and belief.
3.
I/ we hereby submit our token of acceptance to all the tender terms & conditions without any
deviations. Hence, we are hereby submitting our Bid and offer to provide services to Purchaser
for carrying out the project in accordance with your RFP.
4.
Until a formal contract is prepared and executed, this bid, together with your written acceptance
thereof and your notification of award shall constitute a binding Contract between us.
5.
I/We agree to abide by this RFP for a period of 180 days from the closing date fixed for
submission of bid as stipulated in the RFP document.
6.
I/We undertake that, in competing for (and, if the award is made to us, in executing) the above
contract, we will strictly observe the laws against fraud and corruption in force in India namely
“Prevention of Corruption Act, 1988”.
7.
I/ We undertake, for timely establishment of a local office in Jaipur (if the award is made to us)
and within 2 months from the date of issue of LoI.
Or (strike out whichever is not applicable)
We have an existing office at Jaipur at the following address:
..........................................................................................................................
8.
I/We understand that the Purchaser is not bound to accept any bid received in response to this
RFP.
9.
In case we are engaged by the Purchaser, we shall provide any assistance/cooperation required
by Purchaser, appointed auditing agencies (if any), state government officials and Other
Seal & Signature of the Auth. Sign.
Page 140 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Stakeholders of the project for performing their duties with respect to this project. We understand
that our non-cooperation for the same shall be grounds for termination of service.
Signature…………………
In the capacity of………………………
Duly authorised to sign Proposal for And on behalf of………………………..
Date…………………..
Seal & Signature of the Auth. Sign.
Place………………….
Page 141 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.5
ANNEXURE-5 - PRE- BID QUERIES FORMAT
Name of the Company/Firm:
Name of Person(s) Representing the Company/ Firm:
Name of Person
Designation
Email-ID(s)
Tel. Nos. & Fax Nos.
Company/Firm Contacts:
Contact Person(s)
Address
Correspondence
for Email-ID(s)
Tel. Nos. & Fax Nos.
Query / Clarification Sought:
Sl.No.
RFP Page
No.
RFP clause
No.
Clause Details
Query/
Clarification
Suggestion/
Note: - Queries must be strictly submitted only in the prescribed format (.XLS/ .XLSX/ .ODF/.doc/.docx).
Queries not submitted in the prescribed format will not be considered/ responded at all by the tendering
authority
Seal & Signature of the Auth. Sign.
Page 142 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.6
ANNEXURE-6 - TENDER FORM
1) Addressed to:
Name of the Tendering Authority
Address
Telephone
Tele Fax
Email
Managing Director, RajCOMP Info Services Limited
(RISL),
First Floor, Yojana Bhawan, Tilak Marg, C-Scheme, Jaipur
(Rajasthan)
0141-2226055, 5103902
0141-2228701
[email protected]
(clearly mention the NIT no. in the subject of the mail)
2) Firm Details:
Name of Firm
Name of Contact Person with Designation
Registered Office Address
Address of the Firm
Year of Establishment
Type of Firm
Put Tick( Ö ) mark
Telephone Number(s)
Email Address/ Web Site
Fax No.
Mobile Number
Certification/Accreditation/Affiliation, if Any
3)
Public Limited
Email:
Private
Limited
Partnership
Proprietary
Web-Site:
Mobile:
The requisite tender fee amounting to Rs. ________/- (Rupees <in words>) has been deposited vide receipt no.
_______ dated ___________.
4)
The requisite tender processing fee amounting to Rs. ________/- (Rupees <in words>) has been deposited vide
receipt no. _______ dated ___________.
5)
The requisite EMD amounting to Rs. ________/- (Rupees <in words>) has been deposited vide Banker’s
Cheque/ DD No. ___________ dated ___________.
6)
We agree to abide by all the terms and conditions mentioned in this form issued by the Empanelment Authority
and also the further conditions of the said notice given in the attached sheets (all the pages of which have been
signed by us in token of acceptance of the terms mentioned therein along with stamp of the firm).
Date:
Name & Seal of the firm: ________________________
Authorized Signatory: ___________________________
Seal & Signature of the Auth. Sign.
Page 143 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.7
ANNEXURE-7- BIDDER’S AUTHORIZATION CERTIFICATE
To,
Managing Director,
RajCOMP Info Services Limited (RISL),
First Floor, Yojana Bhawan, Tilak Marg,
C-Scheme, Jaipur (Rajasthan)
I/ We <Name/ Designation> hereby declare/ certify that <Name/ Designation> is hereby authorized to
sign relevant documents on behalf of the company/ firm in dealing with Tender/ NIT reference No.
______________________ dated _________. He/ She are also authorized to attend meetings & submit
technical & commercial information/ clarifications as may be required by you in the course of processing
the Bid. For the purpose of validation, his/ her verified signatures are as under.
Thanking you,
Name of the Bidder: -
Verified Signature:
Authorised Signatory: Seal of the Organization: Date:
Place:
Please attach the board resolution / valid power of attorney in favour of person signing this
authorizing
Seal & Signature of the Auth. Sign.
letter.
Page 144 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.8
ANNEXURE-8 - SELF-DECLARATION – NO BLACKLISTING
To,
Managing Director,
RajCOMP Info Services Limited (RISL),
First Floor, Yojana Bhawan, Tilak Marg,
C-Scheme, Jaipur (Rajasthan)
In response to the Tender/ NIT Ref. No. _____________________________ dated ___________ for
<Project Title>, as an Owner/ Partner/ Director of ________________________________________, I/
We hereby declare that presently our Company/ firm ___________________, at the time of bidding, is
having unblemished record and is not declared ineligible for corrupt & fraudulent practices either
indefinitely or for a particular period of time by any Central Government / State / Semi Government / or
other Government subsidiaries including autonomous bodies in India
If this declaration is found to be incorrect then without prejudice to any other action that may be taken,
my/ our security may be forfeited in full and our bid, to the extent accepted, may be cancelled.
Thanking you,
Name of the Bidder: Authorised Signatory: Seal of the Organization: Date:
Place:
Seal & Signature of the Auth. Sign.
Page 145 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.9
ANNEXURE-9 - CERTIFICATE OF CONFORMITY/ NO DEVIATION
To,
Managing Director,
RajCOMP Info Services Limited (RISL),
First Floor, Yojana Bhawan, Tilak Marg,
C-Scheme, Jaipur (Rajasthan)
CERTIFICATE
This is to certify that, the specifications of Hardware & Software which I/ We have mentioned in the
Technical bid, and which I/ We shall supply if I/ We am/ are awarded with the work, are in conformity with
the minimum specifications of the Tender/ bidding document and that there are no deviations of any kind
from the requirement specifications.
Also, I/ we have thoroughly read the tender/ bidding document and by signing this certificate, we hereby
submit our token of acceptance to all the tender terms & conditions without any deviations.
I/ We also certify that the price I/ we have quoted is inclusive of all the cost factors involved in the end-toend implementation and execution of the project, to meet the desired Standards set out in the Tender/
bidding Document.
Thanking you,
Name of the Bidder: Authorised Signatory: Seal of the Organization: Date:
Place:
Seal & Signature of the Auth. Sign.
Page 146 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.10
ANNEXURE-10 - MANUFACTURER’S AUTHORIZATION FORM (MAF)
To,
Managing Director,
RajCOMP Info Services Limited (RISL),
First Floor, Yojana Bhawan, Tilak Marg,
C-Scheme, Jaipur (Rajasthan)
Subject: Issue of the Manufacturer’s Authorisation Form (MAF)
Reference: NIT/ RFP Ref. No. _____________________ dated ________
Sir,
We <name and address of the OEM> who are established and reputed original equipment
manufacturers (OEMs) having factories at <addresses of manufacturing location> do hereby
authorize <M/s __________________________> who is our <Distributor/ Channel Partner/ Retailer/
Others <please specify> to bid, negotiate and conclude the contract with you against the
aforementioned tender reference for the following Hardware/ Software manufactured by us: <OEM will mention the details of all the proposed product(s) with their make/ model.
This should be in sync with the overall proposed technical solution. Also, OEM shall
provide to the bidder, the Compliance Sheets (duly supported by the datasheets) for all
the products as per Technical Specifications mentioned in this bid document at
Annexure-3>
We undertake that offered Hardware/ Software, as mentioned above, by the bidder for back to back
service, support, spares, updates and patches for the entire period of contract as mentioned in the
bid document.
Yours faithfully,
For and on behalf of M/s (Name of the manufacturer)
(Authorized Signatory) – Please attach proof
Name, Designation & Contact No.:
Address: ___________________________________
Seal:
Seal & Signature of the Auth. Sign.
Page 147 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.11
ANNEXURE-11 - UNDERTAKING ON AUTHENTICITY OF COMPUTER
EQUIPMENTS
(On Rs. 100/- Non-judicial stamp paper)
To,
Managing Director,
RajCOMP Info Services Limited (RISL),
First Floor, Yojana Bhawan, Tilak Marg,
C-Scheme, Jaipur (Rajasthan)
Reference: NIT No. :___________________________________ Dated:__________
This has reference to the items being supplied/ quoted to you vide our bid enquiry no. ___________
dated ___________.
We hereby undertake that all the components/ parts/ assembly/ software used in the equipment shall be
genuine, original and new components /parts/ assembly/ software from respective OEMs of the products
and that no refurbished/ duplicate/ second hand components/ parts/ assembly/ software are being used
or shall be used. In respect of licensed operating system, we undertake that the same shall be supplied
along with the authorized license certificate with our name/logo. Also, that it shall be sourced from the
authorized source for use in India.
In case, we are found not complying with above at the time of delivery or during installation, for the
equipment already billed, we agree to take back the equipment already supplied at our cost and return
any amount paid to us by you in this regard and that you will have the right to forfeit our EMD/ SD/ PSD
for this bid or debar/ black list us or take suitable action against us.
Authorized Signatory
Name:
Designation:
Seal & Signature of the Auth. Sign.
Page 148 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.12
ANNEXURE-12- FORMAT FOR STATEMENT OF DEVIATIONS
7.12.1 Statement of deviations from Schedule of Requirements
To
Managing Director,
RajCOMP Info Services Limited (RISL),
First Floor, Yojana Bhawan, Tilak Marg,
C-Scheme, Jaipur (Rajasthan)
Following are the Technical deviations and variations from the requirements and documents proposal
submitted against Tender document No. <TENDER REFERNECE NUMBER> Dated <DATE>. These
deviations and variations are exhaustive. Except these deviations and variations, all other Terms and
Conditions of the Tender are acceptable to us.
S. No.
Section No.
Clause No.
Page No.
Statement
of
deviations
and
Remarks
variations.
Note: Bidders may please note that compliance to a clause and a sub-clause would mean complete
compliance to all the other sections within those clauses and sub-clauses.
Witness:
Bidder:
Signature
------------------------
Signature
------------------------
Name
------------------------
Name
------------------------
Address
------------------------
Designation
------------------------
Company
------------------------
Date
-------------------------
Date
-------------------------
Seal & Signature of the Auth. Sign.
Page 149 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.12.2 Statement of Deviations from Tender Terms & Conditions
To
The Managing Director,
RajCOMP Info Services Limited (RISL),
First Floor, Yojana Bhawan, Tilak Marg,
C-Scheme, Jaipur-302016 (Raj.)
Following are the Technical deviations and variations from the requirements and documents proposal
submitted against Tender document No. <TENDER REFERNECE NUMBER> Dated <DATE>. These
deviations and variations are exhaustive. Except these deviations and variations, all other Terms and
Conditions of the Tender are acceptable to us.
S. No.
Section No.
Clause No.
Page No.
Statement
of
deviations
and
Remarks
variations.
Note: Bidders may please note that compliance to a clause and a sub-clause would mean complete
compliance to all the other sections within those clauses and sub-clauses.
Witness:
Bidder:
Signature
------------------------
Signature
------------------------
Name
------------------------
Name
------------------------
Address
------------------------
Designation
------------------------
Company
------------------------
Date
-------------------------
Date
-------------------------
Seal & Signature of the Auth. Sign.
Page 150 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.13
ANNEXURE-13 - FINANCIAL BID FORMAT
To,
The Managing Director,
RajCOMP Info Services Limited (RISL),
First Floor, Yojana Bhawan, Tilak Marg,
C-Scheme, Jaipur-302016 (Raj.)
Sir,
Having examined the Bidding Document, the receipt of which is hereby duly acknowledged, I/ we, the
undersigned, offer to work as “System Integrator/ Implementing Agency” as per the defined Scope of the
work & in conformity with the said bidding document for the same. We hereby offer our best price as per
the details below and would be valid as per the details mentioned in the NIT.
1) I/ We undertake that the prices are in conformity with the specifications/ requirements prescribed.
The price quoted is inclusive of all cost likely to be incurred for executing this work. The prices are
inclusive of all type of govt. taxes/ duties.
2) I/ We undertake, if our bid is accepted, to deliver the services in accordance with the requirements of
RISL/ designated department.
3) If our bid is accepted, we will give the Performance Security of Rs. ___________for the due
performance of the Contract, in the form prescribed by RISL.
4) I/ We agree to abide by this bid for a period of 180 (One Hundred Eighty only) days after the last date
fixed for bid submission and it shall remain binding upon us and may be accepted at any time before
the expiry of that period.
5) Until a formal contract is prepared and executed, this bid, together with your written acceptance
thereof and your notification of award shall constitute a binding Contract between us.
6) We understand that you are not bound to accept the lowest or any bid you may receive.
7) We agree to the terms & conditions mentioned in the Tender document.
Seal & Signature of the Auth. Sign.
Page 151 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
A) CAPEX
A1) CAPEX: Head Quarter, ACB, Jaipur
S.No.
Item No. and
Description
Unit
Total Qty Base Unit Cost in Rajasthan Total Cost in
INR (incl. all
VAT on Base INR (excl.
incidental charges Unit Cost as Rajasthan
and all Taxes
mentioned in
VAT)
(CST, Excise duty
B in INR
etc) but excl. Raj.
VAT)
A
1.
Desktop Computer (Incl.
OS + AV + MS Office)
Nos.
5
2.
Tablets Devices
Nos.
8
3.
MFD Printer (B/W) A4
Nos.
5
4.
UPS 0.8 KVA
Nos.
5
5.
L 2 Switch - 24 Port
Nos.
3
6.
Passive work -structure
cable (UTP)
Mtr
300
7.
Passive
work-Panel
along with 19U rack
Nos
3
8.
PVC
Conduits
and
Laying
of
PVC
conduits/UTP cable
Nos
100
Nos
10
Size
Biometric authentication
device
9.
B
C
E=A*B
The
rates
shall be filled
up separately
in
given
format on eprocurement
portal
with
financial bid.
Total A1 (In Figures) – Rs
Total A1 (In Words) – Rupees
* Aforesaid Quantity mentioned for item no 7 (structure cable) are Indicative, in case of any deviation in quantity
unitary price of each item shall be applicable.
Seal & Signature of the Auth. Sign.
Page 152 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
A2) CAPEX: Range Offices
S.No. Item No. and Description
1.
Desktop (Incl. OS + AV +
Open Office) for Range
Office
Unit
Total
Qty
Base Unit Cost in
INR (incl. all
incidental charges
and all Taxes
(CST, Excise duty
etc) but excl. Raj.
VAT)
A
B
Nos.
18
Nos.
8
2.
MFD Printer (B/W) A4
3.
UPS 0.8 KVA
Nos.
18
4.
L 2 Switch - 24 Port
Nos.
8
5.
Passive work – structure
cable –UTP (indicative)
Mtr
600
6.
Panel along with 19U Rack
Nos
8
Passive
work
–I/O
(Information outlet)
Passive work –patch cord
(Average 7 ft )
Nos
50
Nos
50
7.
8.
Size
Nos
9.
PVC Conduits and Laying
of PVC conduits/UTP cable
200
Rajasthan Total Cost in
VAT on
INR (excl.
Base Unit
Rajasthan
Cost as
VAT)
mentioned
in B in INR
C
E=A*B
The
rates
shall be filled
up separately
in
given
format on eprocurement
portal
with
financial bid.
Total A2 (In Figures) – Rs
Total A2 (In Words) – Rupees
* Aforesaid Quantity mentioned for item no 6 (structure cable) are Indicative, in case of any deviation in
quantity unitary price of each item shall be applicable.
Seal & Signature of the Auth. Sign.
Page 153 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
A3) CAPEX: Outpost Offices
S.No.
Item No. and
Description
Unit
Total Qty Base Unit Cost in
INR (incl. all
incidental charges
and all Taxes
(CST, Excise duty
etc) but excl. Raj.
VAT)
A
Desktop (Incl. OS + AV
+ Open Office)
Nos.
36
2.
MFD Printer (B/W) A4
Nos.
35
3.
UPS (0.8KVA)
Nos.
36
4.
L 2 Switch - 24 Port
Nos.
35
Mtr
1700
Nos
35
Nos
110
Nos
110
Nos
500
1.
5.
6.
7.
8.
Size
Passive work – structure
cable –UTP (indicative)
Panel along with 19U
Rack
Passive
work
–I/O
(Information outlet)
Passive work –patch
cord (Average 7 ft )
PVC
Conduits
and
Laying
of
PVC
conduits/UTP cable
9.
B
Rajasthan Total Cost in
VAT on
INR (excl.
Base Unit
Rajasthan
Cost as
VAT)
mentioned
in B in INR
C
E=A*B
The
rates
shall be filled
up separately
in
given
format on eprocurement
portal
with
financial bid.
Total A3 (In Figures) – Rs
Total A3 (In Words) – Rupees
* Aforesaid Quantity mentioned for item no 5 (structure cable) are Indicative, in case of any deviation in
quantity unitary price of each item shall be applicable.
Seal & Signature of the Auth. Sign.
Page 154 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
A4) CAPEX: Web Based Application Software Development
S.No.
Item No. and
Description
Unit
Total Qty
Rate (R) in INR Service Tax Total Cost
(incl. all incidental
(Excl.
in INR
charges and all
Taxes but excl.
Service Tax)
Service Tax)
in INR
R (in Rs.)= Unit
Rate * Quantity
(given in Col A)
A
1.
Web base application
software along with 3
Nos
1
years OEM support
B
C
E=A*(B+C)
The rates shall be filled up
separately in given format on eprocurement portal with financial
bid.
Total A4 (In Figures) – Rs
Total A4 (In Words) – Rupees
A5) CAPEX: RSDC Document Management System
S.No.
Item No. and
Description
Unit
Total Qty
A
1.
Document
Management System
client user licence
User
70
Base Unit Cost in Rajasthan Total Cost in
INR (incl. all
VAT on Base INR (excl.
incidental charges Unit Cost as Rajasthan
and all Taxes
mentioned in
VAT)
(CST, Excise duty
B in INR
etc) but excl. Raj.
VAT)
B
C
D
E=A*B
The rates shall be filled up
separately in given format on eprocurement portal with financial
bid.
Total A5 (In Figures) – Rs
Total A5 (In Words) – Rupees
Seal & Signature of the Auth. Sign.
Page 155 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
A6) CAPEX: Miscellaneous One-Time Activities
S.No.
Item No. and
Description
Unit
Qty
Rate (R) in INR Service Tax Total Cost
(incl. all incidental
(Excl.
in INR
charges and all
Taxes but excl.
Service Tax)
Service Tax)
in INR
R (in Rs.)= Unit
Rate * Quantity
(given in Col A)
A
1.
Man-Month Rate for
undertaking Data
Digitization with an effort
estimate of 92 manmonths
2.
Initial Training to all
Officers/ Emp. as per
SoW
Man
B
C
E=A*B
The rates shall be
filled up separately in
given format on eportal
20 procurement
with financial bid.
92
Month
Sessions
Total A5 (In Figures) – Rs
Total A5 (In Words) – Rupees
* Aforesaid Quantity mentioned for item no 1 (data digitization) are Indicative, in case of any deviation in
quantity unitary price of each item shall be applicable.
B) OPEX for 3 YEARS
S.No.
1.
Item No. and Description
FMS for web based application
software (ACBMS) and all IT
infrastructure deployed at various
locations(HQ,
Range
Office,
Outpost Offices and RSDC)
QTY
Units
A
B
1
Nos.
Rate (R) in INR Service Tax Total Cost
(incl. all
(Excl.
in INR
incidental
charges and all
Service
Taxes but excl.
Tax)
Service Tax)
R (in Rs.)= Unit
in INR
Rate * Quantity
(given in Col A)
C
D
E=A*(C+D)
The rates shall be filled up
separately in given format on
e-procurement portal with
financial bid.
Total B for 3 Year (In Figures) – Rs.
Total B for 3 Year (In Words) – Rupees
Seal & Signature of the Auth. Sign.
Page 156 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
C) Man-Month Rate for Application Change Requests
S.No.
Item No. and Description
QTY
Units
A
B
Man-Month Rate for undertaking
1. change request work with an effort
estimate of 24 man-months
24
Rate (R) in INR Service Tax Total Cost
(incl. all
(Excl.
in INR
incidental
charges and all
Service
Taxes but excl.
Tax)
Service Tax)
R (in Rs.)= Unit
in INR
Rate * Quantity
(given in Col A)
C
Man
Months
D
E=A*(C+D)
The rates shall be filled up
separately in given format on eprocurement
portal
with
financial bid.
Total C (In Figures) – Rs.
Total C (In Words) – Rupees
D) COMMERCIAL BID SUMMARY – TOTAL CAPEX and TOTAL OPEX
D1) TOTAL CAPEX
Sl.No.
Item No. and Description
CAPEX Cost in INR
A
1. Total Cost of A1
2. Total Cost of A2
3. Total Cost of A3
4. Total Cost of A4
5. Total Cost of A5
6. Total Cost of A6
Total D1 (In Figures) – Rs.
Total D1 (In Words) – Rupees
Seal & Signature of the Auth. Sign.
Page 157 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
D2) TOTAL OPEX
Sl.No. Item No. and Description
Total OPEX
Cost in INR
1. Total Cost of B1
Total D2 (In Figures) – Rs.
Total D2 (In Words) – Rupees
E) COMMERCIAL BID SUMMARY – TOTAL PROJECT COST
S.No. Item No. and Description
Total Cost in
INR
1. Total CAPEX (D1)
2. Total OPEX (D2)
3.
Total Rate for undertaking change request work with an effort estimate of 24
man-months (C)
Total E (In Figures) – Rs.
Total E (In Words) – Rupees
Date: ________________
Place: ________________
Authorized Signatory: ___________________________
Seal of the Company/Firm: ______________________
Seal & Signature of the Auth. Sign.
Page 158 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.14
ANNEXURE-14 - PERFORMANCE BANK GUARANTEE
(To be stamped in accordance with Stamp Act and on a Stamp Paper purchased from Rajasthan State
only and to be issued by a Nationalised/ Scheduled bank having its branch at Jaipur)
To,
Managing Director,
RajCOMP Info Services Ltd. (RISL),
Jaipur.
1. In consideration of the RajCOMP Info Services Ltd. (RISL) (hereinafter called "RISL") having agreed
to exempt M/s ..........................(hereinafter called "the said Contractor(s)" from the demand, under
the terms and conditions of an Agreement No..................................dated .....................made between
the RISL through Director (T) and .......................(Contractor) for the work .................(hereinafter
called "the said Agreement") of Security Deposit for the due fulfillment by the said Contractor (s) of
the terms and conditions contained in the said Agreement, on production of a Bank Guarantee for
Rs...................(rupees ........................................only), we ...................(indicate the name of the
Bank), (hereinafter referred to as "the Bank") at the request of ..................Contractor(s) do hereby
undertake
to
pay
to
the
RISL
an
amount
not
exceeding
Rs...................(Rupees..................................only) on demand.
2. We................. (Indicate the name of Bank), do hereby undertake to pay Rs....................
(Rupees............................only), the amounts due and payable under this guarantee without any
demur or delay, merely on a demand from the RISL. Any such demand made on the bank by the
RISL shall be conclusive as regards the amount due and payable by the Bank under this guarantee.
The Bank Guarantee shall be completely at the disposal of the RISL and We....................... (Indicate
the name of Bank), bound ourselves with all directions given by RISL regarding this Bank Guarantee.
However, our liability under this guarantee shall be restricted to an amount not exceeding
Rs...................... (Rupees....................only).
3. We.......................(indicate the name of Bank), undertake to pay to the RISL any money so
demanded notwithstanding any dispute or disputes raised by the contractor(s) in any suit or
proceeding pending before any Court or Tribunal or Arbitrator etc. relating thereto, our liability under
these presents being absolute, unequivocal and unconditional.
4. We.....................(indicate the name of Bank) further agree that the performance guarantee herein
contained shall remain in full force and effective up to <DATE> and that it shall continue to be
enforceable for above specified period till all the dues of RISL under or by virtue of the said
Agreement have been fully paid and its claims satisfied or discharged or till the RISL certifies that the
terms and conditions of the said Agreement have been fully and properly carried out by the said
Contractor(s) and accordingly discharges this guarantee.
5. We ...........................(indicate the name of Bank) further agree with the RISL that the RISL shall have
the fullest liberty without our consent and without affecting in any manner our obligations hereunder
to vary any of the terms and conditions of the said Agreement or to extend time of performance by
the said Contractor(s) from time to time or to postpone for any time or from time to time any of the
powers exercisable by the RISL against the said Contractor(s) and to forbear or enforce any of the
terms and conditions relating to the said Agreement and we shall not be relieved from our liability by
reason of any such variation, or extension being granted to the said Contractor(s) or for any
forbearance, act or omission on the part of the RISL or any indulgence by the RISL to the said
Contractor(s) or by any such matter or thing whatsoever which would but for this provision, have
effect of so relieving us.
6. The liability of us ............................. (indicate the name of Bank), under this guarantee will not be
discharged due to the change in the constitution of the Bank or the contractor(s).
7. We .............................. (indicate the name of Bank), lastly undertake not to revoke this guarantee
except with the previous consent of the RISL in writing.
Seal & Signature of the Auth. Sign.
Page 159 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
8. This performance Guarantee shall remain valid and in full effect, until it is decided to be discharged
by the RISL. Notwithstanding anything mentioned above, our liability against this guarantee is
restricted to Rs........................... (Rupees..............................only).
9. It shall not be necessary for the RISL to proceed against the contractor before proceeding against
the Bank and the guarantee herein contained shall be enforceable against the Bank notwithstanding
any security which the RISL may have obtained or obtain from the contractor.
10. We .............................. (indicate the name of Bank) verify that we have a branch at Jaipur. We
undertake that this Bank Guarantee shall be payable at any of its branch at Jaipur. If the last day of
expiry of Bank Guarantee happens to be a holiday of the Bank, the Bank Guarantee shall expire on
the close of the next working day.
11. We hereby confirm that we have the power(s) to issue this guarantee in your favor under the
memorandum and articles of Association/constitution of our bank and the undersigned is/are the
recipient of authority by express delegation of power(s) and has/have full power(s) to execute this
guarantee for the power of attorney issued by the bank.
Dated..........................day of....................For and on behalf of the <Bank> (indicate the Bank)
Signature
(Name & Designation)
Bank's Seal
The above performance Guarantee is accepted by the RISL
For and on behalf of the RISL
Signature
(Name & Designation)
Seal & Signature of the Auth. Sign.
Page 160 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.15
ANNEXURE-15 - DRAFT AGREEMENT FORMAT
1) An agreement made this__ (enter date of Agreement)__between__(enter your firm’s name
& address)__(hereinafter called "the approved supplier", which expression shall, where the
context so admits, be deemed to include his heirs, successors, executors and
administrators of the one part and the "RISL" which expression shall, where the context so
admits, be deemed to include his successors in office and assigns of the other part.
2) Whereas the approved supplier has agreed with the RISL to supply to the Managing
Director, RISL, Yojana Bhawan, Jaipur on behalf of (enter name of client organisation) to its
various Offices as well as at its branch offices throughout Rajasthan, all those articles set
forth in Our Order No ._________ Dated __________ appended hereto in the manner set
forth in the conditions of the tender and contract appended herewith and at the rates set
forth in the said order.
3) And whereas the approved supplier has deposited a sum of Rs._____________ in the form
of: a) Cash/ Bank Draft No./ Banker Cheque No.____________________ dated._________
valid upto _____________.
b) Post Officer Savings Bank Pass Book duly hypothecated to the Departmental authority.
c) National Savings Certificates / Defence Savings Certificates / Kisan Vikas Patras or any
other script / instrument under National Saving Schemes for promotion of Small
Savings, if the same can be pledged under the relevant rule. (The certificates being
accepted at surrender value) as security for the due performance of the aforesaid
agreement which has been formally transferred to RISL.
4) Now these Presents witness:
a) In consideration of the payment to be made by the RISL through cheque/DD at the rates
set forth in the Supply Order hereto appended the approved supplier will duly
the
said
articles
set
forth
supply
in Our Order No.___________ dated ___/___/20___
thereof in the manner set forth in the NIT, Tender Form, Instructions to Bidders, Terms
of Reference, General and Special Conditions of the Tender and Contract, Technical
Bid and Financial Bid along with their enclosures.
b) The NIT, Tender Form, Scope of Work, General and Special Terms and Conditions of
the Tender and Contract, Technical Bid and Financial Bid along with their enclosures
enclosed with the Tender Notice No._____ dated.___/___/20___ and also appended to
this agreement will be deemed to be taken as part of this agreement and are binding on
the parties executing this agreement
Seal & Signature of the Auth. Sign.
Page 161 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
c) Letter Nos._______________ dated __________ received from bidder and letter
number _____________dated____________ issued by the RISL and appended to this
agreement shall also form part of this agreement.
d) (i) The RISL do hereby agree that if the approved supplier shall duly supply the said
articles in the manner aforesaid observe and keep the said terms and conditions,
the RISL will through Cheque/ DD pay or cause to be paid to the approved supplier at
the time and the manner set forth in the said conditions, the amount payable for each
and every consignment.
(ii) The mode of Payment will be as specified in the bid document/ work order.
5) The prescribed scope of work/ requirement of services and deployment of technical
resources shall be effected and completed within the period as specified in the work order.
6) In case of extension in the delivery and/ or installation period/ completion period with
liquidated damages, the recovery shall be made on the basis of following percentages of
value of stores/ works which the bidder has failed to supply or complete the work: 2.5%
a) Delay up to one fourth period of the prescribed delivery period, successful
installation & completion of work
b) Delay exceeding one fourth but not exceeding half of the prescribed delivery
period, successful installation & completion of work.
c) Delay exceeding half but not exceeding three fourth of the prescribed delivery
period, successful installation & completion of work.
d) Delay exceeding three fourth of the prescribed delivery period, successful
installation & completion of work.
5.0%
7.5%
10.0%
Note:
a) Fraction of a day in reckoning period of delay in supplies/ maintenance services shall be
eliminated if it is less than half a day.
b) The maximum amount of agreed liquidated damages shall be 10%.
c) If the supplier requires an extension of time in completion of contractual supply on
account of occurrence of any hindrances, he shall apply in writing to the authority which
had placed the supply order, for the same immediately on occurrence of the hindrance
but not after the stipulated date of completion of supply.
Delivery period may be extended with or without liquidated damages if the delay in the supply of
goods in on account of hindrances beyond the control of the bidder.
7) Warranty/ Services shall be provided by the bidder as per Conditions of Contract.
8) All disputes arising out of this agreement and all questions relating to the interpretation of
this agreement shall be decided by the RISL and the decision of the RISL shall be final.
In witness whereof the parties hereto have set their hands on the _____ day of _____ (Year).
Seal & Signature of the Auth. Sign.
Page 162 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Signature
of
the
Approved
supplier
Signature for and on behalf of
MD, RISL
Designation:
Date:
Date:
Witness No.1
Witness No.1
Witness No.2
Witness No.2
Seal & Signature of the Auth. Sign.
Page 163 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.16 ANNEXURE-16 - FORMAT FOR SUBMISSION OF PROJECT REFERENCES
FOR ELIGIBILITY CRITERIA
Project Name:
Value of Contract/Work Order (In INR):
Country:
Location within country:
Name of Customer:
Project Duration:
Contact person with address, phone,
fax and e-mail:
Start date (month/year):
Completion date (month/year):
Name of associated Bidders, if any:
Approx. value of the services provided by your company under the
contract (in INR):
Total No. of staff-months of the assignment:
Narrative description of Project:
List of Services provided by your firm/company
Please attach a copy of the work order/completion certificate/purchase order/ letter from the customer for each
project reference
Seal & Signature of the Auth. Sign.
Page 164 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.17
ANNEXURE 17- SERVICE LEVEL AGREMENT
a) Purpose & Duration of SLA: The SLA purpose is to enforce a contract between the bidder
and Purchaser. The SLA would come into effect from the date of commissioning and until
the successful completion of the operations & maintenance period of 3 years.
b) Escalation Procedure: The SLA provides Levels of support to be provided by the selected
bidder, incident handling process based on criticality of incident reported, incident
escalation, responsible offices and expected time to resolve the incident. The following
characteristics are used to identify the severity of an incident.
• Business
and financial exposure
• Work outage
• Number of end-users affected
• Workaround
• Acceptable resolution time
A given problem must be judged against each of the characteristics to make an overall
assessment of which severity level best describes the incident. The designated officer
and selected bidder’s helpdesk staff may jointly determine the initial severity rating for
the report.
Escalation Level
Severity Codes
Responsible Officer
Level 1
High
Medium
Low
1) Bidder’s Helpdesk Executive at NOC/ HQ
of ACB, GoR
2) Designated Nodal Officer, RISL
3) Designated Nodal Officer, ACB, GoR
Level 2
High
Medium
Low
1) Bidder’s Project Manager at NOC/ HQ of
ACB, GoR
2) Director (Technical), RISL
3) IG, ACB, GoR
Level 3
High
Medium
Low
2) Bidder’s Project Manager at NOC/ HQ of
ACB, GoR
3) ADG, ACB, GoR
4) Managing Director, RISL
5) Additional Director, DoIT&C, GoR
a) Service Window:
1
Prime Business Hours (PBH)
2
Non-Prime
Business
08:00AM to 06:00PM, 10 Hours (On all days)
Hours 06:00PM to 08:00AM, 14 Hours (On all days)
(NPBH)
Seal & Signature of the Auth. Sign.
Page 165 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
b) Hours of Operation (Help Desk): The problems encountered during the usage of the
application would be reported at the Help Desk established by the selected bidder at the
Head Quarter of ACB in Jaipur. This would enable the Helpdesk staff to log complaints
and take action as per the severity of the reported problem. Also, the hours of Helpdesk
operation would be from 9.30AM to 6.30PM and on all the working days. If required,
under exceptional circumstances, the Helpdesk would also be operational on nonworking days.
c) Dependencies: The dependencies on the performance of services beyond the control of
either party and where default is due to reasons beyond the control of the selected
bidder or due to reasons attributable to RISL or third parties, the selected bidder would
not be penalized. For example, if uptime of a particular equipment/ application is desired
and this is due to non-availability of power (which is out of scope of work of the selected
bidder), then the time period during which a service was unavailable due to nonavailability of power would be removed while calculating the uptime.
d) Monitoring & Evaluation: The selected bidder shall provide and make use of following
system for monitoring and evaluation
Sr No
SLA Report
Reporting System
1
Down time of IT & Non-IT Through a web base/phone line Incident
Infrastructure deployed at all reporting log available at IT help desk
project locations
Down Time
2
web
portal & Through EMS application available at RSDC
Application software
(reports to made available by the DCO)
3
Non Availability of Manpower
Attendance Register at each project location
4
Delay in performing software Through a web base/phone line call log
support like upload content/ available at IT help desk
bugs
fixing/
minor
change
request
e) Review Committee and Review Mechanism: The designated review committee/
members, on a quarterly basis, shall review and discuss the services delivery and
performance standard compliance of the selected bidder. The review would include but
not limited to: ·
Service provided during the review period
·
Major incidents during the review period
Seal & Signature of the Auth. Sign.
Page 166 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
·
Problems that remains outstanding
·
Review of Change requests/Variation and progress for enhancements
·
Future events or business developments that will affect the Service
·
Review any potential changes required to the SLA
·
Agree items for submission to the executive decision making
·
Review schedules for Services provided.
f) Penalty for downtime
If the selected bidder fails to deliver the required services due to reasons attributable to
him like non-functioning of the hardware/ system, non-accessibility of the web based
application software, non-availability of the technical personnel/ manpower, etc. the
cumulative penalty, as applicable, would be imposed as mentioned bellow while
processing the payment for respective milestone.
i. Penalty for Downtime of IT & Non IT Infrastructure deployed at various project
locations.
The below mentioned table describes item wise schedule of expected time allowed
to SI to maintain items in Up & running condition it further describes the schedule for
escalation of complaints.
The penalty shall imposed in case SI fails to resolve complaint in expected time (as
defined in No penalty column)
Items
No Penalty
Escalation Schedule
Low
Medium
High
Network Switch
No Delay
30 Min
120 Min
240 Min
Desktop
20 Min
60 Min
8 Hour
2 days
Tablet PC
20 Min
60 Min
8 Hour
2 days
MFD
40Min
120 Min
8 Hour
3 days
UPS
40Min
120 Min
8 Hour
3 days
The penalties defined below shall be applicable per location e.g if downtime is
reported at particular location (Range Office/ Outpost office) then penalty shall be
attributed for quarterly payment of particular Range/ Outpost Office only.
Seal & Signature of the Auth. Sign.
Page 167 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Location
Uptime in a Quarter
>=98%
>=97% and <98%
>=96% and <97%
>=95% and <96%
All Project <95%
Locations
Penalty in % of the quarterly payable amount
attributed to per location
PBH
NPBH
No Penalty
No Penalty
1%
No Penalty
2%
1%
3%
2%
2%
upto
95%
and
3% upto 95% and additional
additional
2%
per
5% per additional downtime
additional downtime of 5%
of 5% (subject to a max.
(subject to a max. penalty
penalty of 50%).
of 50%).
Note: Consolidated Down-time of 90% (average of all locations) for consecutive 2 months
may be treated as breach of contract.
ii. Penalty for Downtime of web based application software
The penalty defined below table is applicable for web based application software not
functional/ accessible. If the website/ application is up and running in RSDC then
penalty defined below will not be applicable.
Overall Non-Availability of the Website/
Application in a Quarter
Upto 60 mins. (upto 1 Hr)
61-120 mins. (upto 2 Hrs)
121-180 mins. (upto 3 Hrs)
181-240 mins. (upto 4 Hrs)
241-300 mins. (upto 5 Hrs)
301-360 mins. (upto 6 Hrs)
361-420 mins. (upto 7 Hrs)
421-480 mins. (upto 8 Hrs)
481-540 mins. (upto 9 Hrs)
541-600 mins. (upto 10 Hrs)
601-660 mins. (upto 11 Hrs)
661-720 mins. (upto 12 Hrs/ 1 Day)
Penalty in % of the quarterly payable
PBH
NPBH
No Penalty
No Penalty
0.5%
No Penalty
1%
0.5%
2%
1%
3%
2%
4%
3%
5%
4%
6%
5%
7%
6%
8%
7%
9%
8%
10%
9%
9% per day and
10% and additional
additional 9% per
10% per additional 12
> 720 mins. (> 12 Hrs/ 1 Day)
additional 12 Hrs/ 1 Day
Hrs/ 1 Day downtime
downtime (subject to
(subject to max 50%)
max 50%)
Note: Down-time of 5 days in a month for consecutive 2 months may be treated as breach of
contract. Also, the penalty defined in this section shall be used only when the website/
application are not accessible/ functional/ active but the hardware is functional at RSDC,
Jaipur.
iii. Penalty for Non-Availability of deployed Personnel/ Resources/ Manpower
Seal & Signature of the Auth. Sign.
Page 168 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
Resource Type
Project Manager/ NOC
Helpdesk Executive (Helpdesk)
Local Support Engineer
Penalty Per Day of Non-Availability
(to be deducted from the total quarterly
payable amount during the O&M Phase)
Rs. 2500/- per day.
Rs. 1200/- per day.
Rs. 750/- per day.
iv. Penalty for non-timely performing software support
service like Update on web
based application software / Incident reporting of Bugs fixing/ Change Management
(Application Software) i.e. Minor Change Requests
Delay (in days)
Penalty Per Day
(to be deducted from the total quarterly
payable amount during the O&M Phase)
Upto 1 Day
No Penalty
2nd Day
Rs. 2,000/- per day.
rd
3 Day
Rs. 3,000/- per day.
4th Day
Rs. 4,000/- per day.
5th Day
Rs. 5,000/- per day.
Note: Non-timely updates/ Bugs fixing / Change Management for 5 or more days for
consecutive 2 months may be treated as breach of contract.
v. Penalty for improper/ missing Data Backup: If the selected bidder fails to take the
backup (as per the RSDC Backup Policy) then a penalty of Rs. 2,000 per day will be
imposed (to be deducted from the total quarterly payable amount during the O&M
Phase).
vi. Note: Any delay/ non-performance, not attributable to the selected bidder, shall not
be taken into account while computing adherence to service levels but the selected
bidder shall submit sufficient records/ documents that the delay/ non-performance is
not on his part.
Seal & Signature of the Auth. Sign.
Page 169 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.18
S. No.
ANNEXURE-18 - LIST OF INFRASTRUCTURE TO BE PROVIDED BY RSDC
Item Description
Shared/Dedicated
Type/ Specification
Servers
1
Web Servers
Virtual Dedicated
1+1 HP DL580 G7, (4 x hex core) available in DMZ zone with
32 GB dedicated Ram, including OS Linux/windows
2
Application
Virtual Dedicated
1+1 HP DL580 G7, (4 x hex core) available in MZ zone with 32
GB dedicated RAM including OS Linux/windows
3
Database
Shared
1+1 HP DL580 G7, (4x 8core) available in MZ zone with Post
grey SQL server ver 9
4
Back Up Server
shared
IBM Tivoli Storage manager client licence shall be provided
by RSDC
5
EMS Server
shared
6
SMS Server / Payment Gateway
shared
CA NMS, e health & spectrum, DPM wily, willy-cer, service
desk &ITCM on windows (additional NMS licenses shall be
provided by SI)
Red Chilly on windows / As provided by GoI
7
Anti virus
shared
Symantec Endpoint protection 11.0 on windows 2008 R2
client licence as applicable shall be provided by RSDC
8
Authentication Server
Shared
DC,ADC ON WINDOWS 2008 R2, client license shall be
provided by RSDC
9
Audit Log Server
Shared
Centralized syslog server on RHE15
10
Mailing Server
shared
Open Source
Storage
11
SAN Storage
shared
IBM SAN & HP 3PAR
12
Tape Library
shared
IBM
Network
13
Core Switch
shared
CISCO 6513
14
Application Access Switch
shared `
CISCO 3750
15
Network Load balancer
shared
Link Proof & array
16
Bandwidth to be provide by RSDC
dedicated
4X2 Mbps
17
Data transfer inter connectivity
shared
1 Gbps , HBA 4Gbps for SAN
18
Middle ware application server
shared
MS Sharepoint, Jboss AS, Tomcat (client & user licenses shall
be provide by SI)
Seal & Signature of the Auth. Sign.
Page 170 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.19
ANNEXURE-19 - INDICATIVE PROJECT PLAN
PROJECT IMPLEMENTATION TIMELINES
S.
No.
Activities
Timeli
ne
(in
weeks)
A
Project Inception Phase
1
Project Kick off
T+1
2
Detailed Project Plan
T+2
B
Application
Development
Implementation
3
Completion of requirement study and
designing of the SRS document
T+12
4
T+15
5
Designing Detailed Architecture design &
Approval
Application Development
6
Partial User Acceptance Testing (UAT)
T+36
C
Infrastructure (IT& Non IT)
7
Deployment of RSDC Infrastructure &
Commissioning
Completion of Supply, Installation and
Commissioning of the infrastructure
8
M
1
M
2
M
3
M
4
M
5
M
6
M
7
M
8
M
9
M1
0
M1
1
M1
2
M3
6
and
D
Training
E
Final User Acceptance Testing (UAT)
F
Application Audit
G
Project Sign-off
H
Support and Maintenance of three years
post implementation
T+32
T+20
T+30
T+36
T+44
T+32
T+48
M12-M36
# T – is the Date of Signing of the
Contract with SI
Seal & Signature of the Auth. Sign.
Page 171 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.20
ANNEXURE-20 - EXPECTED QUALIFICATION OF MANPOWER
RESOURCES
S. No.
1
Role
Project Manager
Desirable Qualification and Experience
· B.E/ B.Tech + MBA and preferably PMP certified
· Having at least 5 years of post-qualification relevant
work experience in design and development of
customized IT applications
· Experience working through the design, development,
release (SDLC) cycle delivering software application
projects
· Experience in managing a team size of more than 15
developers in the capacity of Team Leader / Project
Manager
· Must have good understanding of Government
Processes and IT automation initiatives in eGovernance
Domain
2
NOC
(at HQ, ACB)
· B.E/ B.Tech/ MCA/ M.Sc (CS/ IT)/ MCA/ M.Tech
· Certification (Microsoft/ Redhat Platform)
· Fluency in English/ Hindi
· 3+ years of post-qualification and relevant work
experience as System administrator
6
Local Support Engineer
and IT help desk
· Graduation + Diploma in Computers
· Certification (Microsoft/ Redhat/ Cisco or Equivalent)
· Fluency in English/ Hindi
· 2+ years of post-qualification and relevant work
experience as Support Executive/ Engineer
Seal & Signature of the Auth. Sign.
Page 172 of 173
RISL: RFP – Implementation of ACBMS for ACB, GoR (After Pre Bid)
7.21
ANNEXURE-21 – LIST OF OFFICES, ACB
S.No
1
·
Range Office
Jaipur – I
2
Jaipur – II
3
Udaipur
4
Bikaner
5
Jodhpur
6
Bharatpur
7
Kota
8
Ajmer
Outposts Office
Jaipur – I
Jaipur - II
Jaipur
Alwar
Sikar
Jhunjhunu
Dausa
Udaipur
Banswara
Chittorgarh
Rajsamand
Pratapgarh
Dungarpur
Bikaner
Ganganagar
Hanumangarh
Churu
Jodhpur
Pali
Sirohi
Barmer
Jaisalmer
Jalore
Bharatpur
Dholpur
Madhopur
Karauli
Kota
Bundi
Jhalawar
Baren
Ajmer
Bhilwara
Nagaur
Tonk
Exact address shall be provided at the time of the work order.
Seal & Signature of the Auth. Sign.
Page 173 of 173