REQUEST FOR PROPOSAL (RFP) For Selection of Agency for ... · REQUEST FOR PROPOSAL (RFP) For...
95
Ref No.: KIAL/IT/RFP/2/2019 Amount: Rs. 50000/- (Fifty Thousand Only) + 18% GST REQUEST FOR PROPOSAL (RFP) For Selection of Agency for Procurement, Design, Development, Testing, Implementation, Integration and Operation & Maintenance of an Airport Operational Database (AODB), Resource Management System (RMS) and Master Systems Integration (MSI) for Kannur International Airport Limited.
Transcript of REQUEST FOR PROPOSAL (RFP) For Selection of Agency for ... · REQUEST FOR PROPOSAL (RFP) For...
Ref No.: KIAL/IT/RFP/2/2019 Amount: Rs. 50000/- (Fifty Thousand Only) + 18% GST
REQUEST FOR PROPOSAL (RFP)
For
Selection of Agency for Procurement, Design, Development, Testing, Implementation, Integration and
Operation & Maintenance of an Airport Operational Database (AODB), Resource Management System (RMS)
and Master Systems Integration (MSI) for Kannur International Airport Limited.
1
1. Table of Contents
1. Table of Contents ....................................................................................... 1
1. Invitation for Proposal .............................................................................. 4
2. Instruction to Bidders ................................................................................ 6
I. Definition of Terms and Interpretations ................................................. 6
II. Tendering guidelines to the Bidders ........................................................ 8
A. Tendering Process ...................................................................................... 8
PART- I: Technical Bid ........................................................................................... 9
PART - II: Financial Bid ....................................................................................... 10
B. Guidelines to bidders ............................................................................... 12
C. Tender document fees and Earnest Money Deposit (EMD) / Security
Deposit....................................................................................................... 12
III. Critical dates and time ............................................................................ 12
IV. Clarifications on tenders ......................................................................... 12
V. Late Tenders ............................................................................................. 13
VI. Modification and withdrawal of tenders ............................................... 13
2.1. Introduction of Kannur International Airport Limited ...................... 14
2.2. Purpose ..................................................................................................... 14
2.3. Cost of RFP............................................................................................... 14
2.4. Transfer of RFP ....................................................................................... 14
2.5. Consortium ............................................................................................... 14
2.6. Involvement of Sub-Contractor (s) ........................................................ 14
2.7. Completeness of Response....................................................................... 15
2.8. Proposal Preparation Costs .................................................................... 16
2.9. Bidder Inquiries ....................................................................................... 16
2.10. Amendment of RFP Document ............................................................... 16
2.11. Supplemental Information to the RFP................................................... 16
2.12. Right to terminate the process ................................................................ 16
2.13. Earnest Money Deposit (EMD) / Security Deposit ............................... 16
2.14. Authentication of Bid............................................................................... 17
2.15. Language of Bids ...................................................................................... 17
2.16. Bid Submission Format ........................................................................... 17
2.17. Submission of Bids ................................................................................... 17
2.18. Bid Validity Period .................................................................................. 18
2.19. Bid Opening .............................................................................................. 18
2.20. Evaluation Process ................................................................................... 18
2.20.1. Bid Evaluation Committee ...................................................................... 18
2
2.20.2. Eligibility Criteria .................................................................................... 18
2.20.3. Process of Evaluation............................................................................... 19
2.20.4. Technical Eligibility Criteria .................................................................. 20
2.20.5. Financial Bid Evaluation ......................................................................... 22
2.21. Performance Bank Guarantee (PBG) .................................................... 23
2.22. Payment Terms and Schedule ................................................................ 24
2.23. Service Level Agreement (SLA) and Penalty during Operation and
Maintenance ............................................................................................. 24
2.24. Design, Development, Testing, Implementation and Integration ........ 25
2.25. Letter of Acceptance ................................................................................ 25
2.26. Force Majeure .......................................................................................... 25
2.27. Non-Disclosure Agreement (NDA) ......................................................... 25
2.28. Liability Clause ........................................................................................ 26
2.29. Warranty .................................................................................................. 26
2.30. Confidentiality .......................................................................................... 26
2.31. Contract Termination.............................................................................. 26
3. Scope of Work .......................................................................................... 27
4. Project Milestones .................................................................................... 30
5. Deliverables .............................................................................................. 31
5.1. Technical Architecture ............................................................................ 32
5.2. System Architecture ................................................................................ 33
5.3. Admin and User Management ................................................................ 34
5.4. Training Services ..................................................................................... 34
5.5. Resource Management, Monitoring & Compliance Services .............. 35
5.6. Application Software Development/Customization Methodology ...... 36
5.7. Security ..................................................................................................... 38
6. Airport Operation Database (AODB), Resources Management System
(RMS) & Master Systems Integration (MSI) Functional requirements
................................................................................................................... 39
7. Airport Operational Database (AODB), Resource Management
System (RMS) and Master Systems Integration (MSI) Non-functional
requirements............................................................................................. 55
Annexure 1: Compliance Statement ......................................................................... 65
Annexure 2: Unconditional Acceptance Letter ....................................................... 66
Annexure 3: Technical Bid Qualification Compliance Statement ......................... 68
Annexure 4: Proposal Covering Letter in response to RFP Notice ....................... 69
Annexure 5: Power of Attorney ................................................................................ 71
Annexure 6: Undertaking for not been Blacklisted ................................................ 72
Annexure 7: Affidavit ................................................................................................ 73
3
Annexure 8: SLA Computation ................................................................................ 74
Annexure 9: Non-Disclosure Agreement .................................................................. 75
Annexure 10: Network Schematic Diagram ............................................................ 80
Annexure 11: Guidelines for Technical Proposal .................................................... 81
Annexure 12: Guidelines for Financial Proposal .................................................... 83
Form 1: Financial Proposal Submission Form ........................................................ 84
Form 2: Details of responding firm .......................................................................... 85
Form 3: Format of Performance Bank Guarantee ................................................. 86
Form 4: Details for Financial Proposal Consolidated Cost Summary .................. 89
Form 5: Format of providing citations ..................................................................... 91
Form 6: Team Member Profile ................................................................................. 92
Form 7: Resource Deployment Plan ......................................................................... 93
4
I. NOTICE INVITING TENDER
1. Invitation for Proposal
Tenders are invited by the Managing Director on behalf of the Kannur International Airport Limited, for
Selection of Agency for Procurement, Design, Development, Testing, Implementation, Integration and
Operation & Maintenance of Airport Operational Database (AODB), Resource Management System
(RMS) & Master Systems Integration (MSI) at Kannur International Airport.
S. No Information Details
1 Name of Work:
Selection of Agency for Procurement, Design, Development,
Testing, Implementation, Integration and Operation &
Maintenance of Airport Operational Database (AODB),
Resource Management System (RMS) & Master Systems
Integration(MSI) for Kannur International Airport.
2 Tender Number KIAL/IT/RFP/2/2019
3 Completion Period 270 days from the date of issue of the work order
4 Bid Validity Period 120 days from the date of opening of Financial Bid
5 Earnest Money Deposit
(EMD) / Security Deposit
INR 1,00,00,000/- (Rupees One Crore Only)
6 Cost of Tender Document INR 50,000/- (Rupees Fifty Thousand Only) exclusive of GST
7 Publishing Date 15 January 2020
8 Document Download sale
Start Date:
15 January 2020
End Date:
2 February 2020
9 Clarification
Start Date:
16 January 2020
End Date:
22 January 2020
All queries shall be addressed to
10 Bid Submission
Start Date:
28 January 2020
End Date:
3 February 2020, 1700 hours
Indian Standard Time
11
Technical Bid Opening
Date& Time
4 February 2020 at 1100 hrs.
Product features
demonstration
Will be notified after the Technical Bid opening process
12 Financial Bid Opening
Date
Will be notified after the Technical Bid opening Process
13
Last date for furnishing
Performance Security to
Kannur International
PBG Part I
Within Thirty (30) days of the date of the Letter
of Acceptance/Letter of Award issued by
Kannur International Airport Limited
5
Airport Limited (By
successful bidders) PBG Part II
On commencement of O&M contract
14
Performance Security
(Performance Bank
Guarantee)
PBG Part I 15% of contract value excluding the O&M
support contract amount
PBG Part II 15% of O&M contract value for 5 years
15 Performance Security
validity period
PBG part I 18 Months from the date of successful warranty
completion with zero outstanding defects
PBG part II 60 Months from the date of commencement of
O&M service contract.
Bidders are advised to study this RFP document carefully before submitting their proposals in response
to the RFP Notice. Submission of a proposal in response to this notice shall be deemed to have been done
after careful study and examination of this document with full understanding of its terms, conditions and
implications.
Prospective bidders are advised to check the eligibility criteria before purchase of bid document. This
RFP document is not transferable and name of purchaser and bidder who submits shall be the same.
6
2. Instruction to Bidders
I. Definition of Terms and Interpretations
Singular & Plural
Where the context so requires, words importing the singular only also include the plural and vice-
versa.
A) AUTHORITY: means the “KANNUR AIRPORT BOARD”.
B) KANNUR AIRPORT: means the “Kannur International Airport Ltd” (Kannur Airport).
C) CLIENT /KANNUR AIRPORT: Means “Kannur International Airport Limited” which invites
tender through the Managing Director, on behalf of Kannur Airport Board.
D)"The Bidder/Tenderer/Vendor/Agency", means the individual/Sole proprietorship/
Partnership Firm/Company who participates in this tender and submits its bid.
E) “The Contractor” means the Individual / Sole proprietorship / Partnership Firm / Company
taking up the work as defined under the Notice Inviting Tender”.
F) “The Works Order/ Purchase order/ Supply order/Award letter" means the order placed
for the Procurement, Design, Development, Testing, Implementation, Integration and Operation
& Maintenance of Airport Operational Database (AODB), Resource Management System (RMS)
& Master Systems Integration (MSI) at Kannur International Airport. issued by the Kannur
Airport including all attachments and appendices there to and all documents incorporated by
reference therein.
G) “The Contract Price” means the price payable to the Contractor under the Works Order
/Purchase Order for the full and proper performance of its contractual obligations.
H) “Non‐responsive Bid” means a bid, which is not submitted as per the instructions to the bidder
or Earnest Money Deposit / Security Deposit has not been attached or the required data has not
been provided with the Bid or intentional errors have been committed in the Bid.
I) CONSIGNEE: Consignee means where the stores are required by the purchaser on
agreement/acceptance of tender to be dispatched by rail, road, air or steamer, the portion specified
in the agreement/ acceptance of tender to whom these are to be delivered at the destination, were
the stores are required by the agreement/ acceptance of tender to be delivered to a person as an
interim consignee for the purpose of dispatch to another person such other person and in any other
case, the person to whom the stores are required by the agreement/acceptance of tender to be
delivered in the manner therein specified.
J) CONTRACT: Contract means the documents containing invitation to tender, instructions to
tenderer, agreement/acceptance of tender, particular, general and special conditions, specified
technical specifications, mutually agreed terms and conditions in the acceptance of tender and
7
includes a repeat order, which has been accepted or acted upon by the contractor.
K) CODES: Codes shall mean applicable codes of the country of origin of equipment international
codes applicable for product and applicable codes in India.
L) DELIVERY: Delivery shall mean stores to be supplied in finished and completely ready for use
condition. The delivery shall be deemed to take place on delivery of the stores in accordance with
the terms of the contract after approval by the Managing Director., to:
(i) The consignee at his premises or,
(ii) Where so provided the interim consignee at his premises or,
(iii) A carrier or other person named in the contract as an interim Consignee for the purpose of
transmission to the consignee.
(iv) The consignee at the destination station in case of contracts stipulating for delivery of stores
at destination station.
M) COMPLETION: Completion of work i.e. Procurement, Design, Development, Testing and
Implementation and Integration of system as specified, their testing and all pre-commissioning
checks and commissioning the installation for safe operation of the equipment/ system and handing
over the same to Kannur International Airport Limited.
N) MATERIAL/EQUIPMENT: Material means anything used by the manufacturer for
fabrication of the stores and installation of the work.
O) PURCHASER: Purchaser shall mean the owner that is KANNUR INTERNATIONAL
AIRPORT LTD which term also includes its successors and permitted Assigns.
P) CONTRACTOR: Contractor shall mean the individual or firm or company, undertaking the
works and shall include the legal personal representatives of such individual or the persons
composing such firms or company or the successor of such firm or company and the permitted
assigns of such individual or firm or company. The words tenderer, contractor, bidder, company
and firm shall also mean the contractor.
Q) ACCREDITED AGENT: A person appointed by the prospective bidder/tenderer who will
collect the correspondence and deliver the same (if required by the bidder). Appointment of
accredited agent is sole responsibility of the tenderer.
R) AODB: Airport Operational Database, a centralized system that maintains and distributes flights
and airports resources information.
S) WORK: The expression ‘Works’ shall unless be something either in the subject or content
repugnant to such construction, be construed and taken to mean the works or by virtue of the
contract contracted to be executed whether temporary or permanent, and whether original, altered,
substituted or additional.
T) SITE: The site shall mean the building/ land or other place on, into or through which work is
to be executed under the contract or any adjacent land, path or street through which work is to be
executed under the contract or other place approved by the purchaser under the Contract.
8
U) TEST: Test shall mean such test or tests as are prescribed by the purchaser or considered
necessary by the Engineer in-Charge or any agency acting under the directions of the Engineer In-
Charge. The tests shall mean the tests to be conducted at contractor’s works and at site by the
purchaser, or his nominee, after the installation is completed.
V) PERFORMANCE OF WORK: The work shall be performed at the place or places named in
the contract or at such other place and places as may be approved by the purchaser.
W) STORES: Stores means the goods specified in the schedule, which the Contractor has agreed
to supply at any place approved by the purchaser under the Contract.
X) WRITING: ‘Writing’ shall, include any manuscript, type written or printed statement
under/over signature or seal of either of the parties as the case may be.
Y) HAND HOLDING shall mean after completion of supply, installation, testing and
commissioning of the goods/equipment by the contractor to the purchaser after satisfactory
compliance of with all conditions for acceptance and taking over.
Z) Government: Shall mean Indian Government Authorities/ Government of Kerala as the case
may be.
AA) Force majeure shall mean an event of effect that cannot reasonably be anticipated such as
acts of God (like earthquakes, floods, storms etc.), acts of States, the direct and indirect ties, national
emergencies, civil commotions and strikes (only those which exceed a duration of ten continuous
days).
AB) GST: Goods and Services Tax
AC) Cess: The word cess means educational cess and higher educational cess etc.
AD) Development: Shall mean customization of the Commercial-off-the-shelf (COTS) software
to cater for the Airport Operational Database (AODB), Resource Management System (RMS) &
Master Systems Integration(MSI) requirements as detailed in this RFP.
II. Tendering guidelines to the Bidders
A. Tendering Process
All documents of the bid shall be signed by the Partner/ Director/ Authorized Person having valid
authorization letter at the time of bid submission. Any consequences resulting due to such signing
shall be binding on the Bidder. The Bidder shall submit Technical &Financial Bid in two parts as
per details below:
PART - I: Technical Bid
PART - II: Financial Bid
9
PART- I: Technical Bid
a. Technical Bid shall be submitted in physical mode only.
The envelope (Cover – I) containing the Technical Bid shall be super scribed with "Technical
Bid-Tender for Selection of Agency for Procurement, Design, Development, Testing,
Implementation, Integration and Operation & Maintenance of an Airport Operational Database
(AODB), Resource Management System (RMS) & Master Systems Integration (MSI) for
Kannur International Airport Limited". The bid shall be addressed to Managing Director
mentioning of reference number of Tender. If the envelope is not properly sealed and marked,
Kannur Airport will assume no responsibility for the misplacement or premature opening of
the bid.
b. Bid documents containing the following must be bound, indexed, completely page numbered
and arranged in the order:
i. Covering letter of Bid on Bidder's letter head as per Annexure 4.
ii. Consultant’s Background and Experience as per Form 2
iii. Detailed CVs of Key Personnel as per Form 6
iv. Resource deployment plan as per Form 7
v. Tender document fee of INR 50,000/- (Rupees Fifty Thousand only) + 18% GST in
the form of or Demand Draft (DD) in favor of Kannur International Airport
Limited, payable at Kannur. Tender not accompanied by Tender Document Fee will
not be entertained.
vi. Chartered Accountant Certificate for the turnover for the last three financial years
ending on 31.3.2019
vii. Earnest Money Deposit / Security Deposit of INR 1,00,00,000/- (Rupees. One Crore
only) in the form of Demand Draft (DD) in favor of Kannur International Airport
Limited, payable at Kannur. Tender not accompanied by EMD/Security Deposit
submitted in any form other than stated above will not be accepted.
viii. Copy of abridged balance sheet along with Profit and Loss Account statement of the
firm shall be submitted for last 5 five financial years.
ix. Undertaking for not having been blacklisted as per Annexure 6.
x. The tenderer must submit PAN & PF Account Numbers & GST Registration
Certificate.
xi. Any other information required in the Bidding Documents or considered relevant by
the bidder.
xii. All documents furnished by the Bidder as per the requirement of Technical Bid
Evaluation Criteria shall be signed and stamped by the bidder or authorized signatory
of bidder. A board resolution / Registered/ Non-revocable Power of Attorney
(Annexure 5) executed by the Bidder in favor of the bidder’s authorized
representative to sign/ execute the proposal as a contract document and execute all
relevant agreements forming part of RFP.
xiii. Client list and successful completion certificate from the current authorized signatory
of the client on their letter head shall be furnished.
xiv. Affidavit as per Annexure 7format.
xv. Technical Document should include:
▪ Understanding of Scope of Work
10
▪ Solution Deployment Architecture including systems integration
▪ Approach, Methodology & Project Plan
▪ Functional and non-functional requirements compliancy matrix
▪ Recommended IT infrastructure (software hosting requirements, operating
system,
▪ Database, 3rd party tools and software, client workstations specifications)
▪ Quality and Security Assurance Plan
▪ Innovation & New Ideas
▪ Project Experience
▪ Training Plan
▪ Adherence to SLA, Go-live support, post cutover warranty and maintenance
support
▪ Monitoring & Review Framework
▪ Understanding of Industry Department Functions, Services and Processes
xvi. Signed and stamped copy of the RFP document along with its annexures/
corrigendum/ documents etc.
xvii. Any other document to support the Bid.
xviii. Technical bids that does not comply with the above specifications will be summarily
disqualified at the time of Technical Bid opening
PART - II: Financial Bid
a. Financial Bid shall be submitted in physical mode only.
b. The envelope (Cover – II) containing the Price Bid shall be super scribed with "Financial Bid-
Tender for selection of agency for Procurement, Design, Development, Testing,
Implementation, Integration and Operation & Maintenance of an Airport Operational Database
(AODB), Resource Management System (RMS) and Master Systems Integration (MSI) for
Kannur International Airport Limited"
c. The Financial Bid should be submitted as per the format specified in Annexure 4on the
letterhead of the Bidder.
d. The bid shall be addressed to Managing Director mentioning Reference Number of Tender. If
the envelope is not properly sealed and marked, Kannur Airport will assume no responsibility
for the misplacement or premature opening of the bid.
e. Other Terms of Financial Bid:
i. No stipulation, deviation, terms & conditions, presumption, basis etc. shall be
stipulated in the price bid. Any conditions, if stipulated, shall be treated as null and
void and shall render the bid liable for rejection.
ii. Bidder shall quote the lump sum price, including applicable taxes and expenses after
careful analysis of cost involved for the performance of the complete work considering
all parts of the Bidding Document.
iii. The quoted Price shall be deemed to be all inclusive till the completion of the work. It
is clearly understood that Kannur Airport will not have any additional liability to wards
payment of any Taxes & Duties over and above total quoted price.
iv. Alternative bids shall not be considered.
v. Prices quoted by the Bidder, shall remain firm and fixed and valid until completion of
the Contract and will not be subject to variation on any account.
11
vi. Price shall be quoted in figures as well as in words. If some discrepancies are found
between the price given in words and figures, the price quoted in words shall be taken
as correct.
vii. Fixed Price: Prices quoted by the Bidder shall be fixed during the bidder`s performance
of the contract and not subject to variation on any account. A bid submitted with an
adjustable / variable price quotation will be treated as non-responsive and rejected.
f. Components of BOQ
i. Design, Development, Testing, Implementation and Integration of all the required
Packages. This line item includes the design of all the modules as listed in this RFP,
integration with Kannur Airport applications (Existing & New), Testing,
Implementation and post cutover maintenance support.
ii. Software and Licenses. This line item envisages the procurement of all the required
software licenses for the successful completion of the project as per the scope
mentioned in this RFP and its annual maintenance. It also includes the procurement of
Airport Operational Database & Resource Management System licenses to
support<<number of licenses to be included>>. Bidder should advise the required
quantity of licenses to support business operations at Kannur Airport.
iii. Operation & Maintenance (5 Years). This include the Operation and Maintenance of
entire system for a period of 5 Years Including the AMC for requisite licenses.
iv. Man-Hour Cost. This line item asks for the man hour cost for 1,440hrs. required for
development against the Change Order/ additional development as contingency,
outside the scope of this RFP.
v. Cloud hosting charges, if Kannur Airport decides to host the software and database on
cloud.
vi. Additional O&M (2 Years). This line item will be required for entering into an optional
contact for O&M support after the expiry of initial 5 Years O&M period. This line item
will not be considered for financial bid evaluation.
General Conditions:
a. Bidders must submit their documents pertaining to the Pre-Qualification Criteria / Technical
Criteria and Financial Quote as per the guidelines stipulated in this RFP.
b. Submission of a Tender by a Tenderer implies that he has read this notice and all other contract
documents and has made himself aware of the eligibility criteria, scope and specifications of
the works to be done, local conditions, local material rates and other factors bearing on the
execution of the works.
c. Notification of Award of contract will be made in writing to the successful Tenderer by the
Accepting Authority or his representative. The contract will normally be awarded to the
qualified and responsive Tenderer offering lowest evaluated bid in conformity with the
requirements of the specifications and contract documents and the Accepting Authority shall
be the sole judge in this regard. The Accepting Authority does not bind himself to accept the
lowest or, any tender or to give any reason for his decision.
d. A responsive tenderer is one who submits priced tender and accepts all terms and conditions of
the specifications and contract documents.
e. Bidders shall demonstrate the functional, non-functional, integration requirements compliancy
at Kannur Airport premises using a prototype model.
12
f. Financial Bid: Only the Financial Bid of the Bidders who have qualified in the Technical Bid
as per the tender conditions and accepted by Kannur Airport will be opened on a later date,
with prior notification.
g. Publishing of Corrigendum: All corrigendum shall be published on
https://www.kannurairport.aero/tenderand shall not be available elsewhere.
B. Guidelines to bidders
Tender documents can be downloaded from the Web site https://www.kannurairport.aero/tender
C. Tender document fees and Earnest Money Deposit (EMD) / Security
Deposit
The bidder shall pay, a tender document fees of INR 50,000 /- (Rupees Fifty Thousand Only) +
18% GST and Earnest Money Deposit / Security Deposit of Bid security of INR 1,00,00,000/-
(Rupees One crore only). The Security Deposit /EMD is required to protect the tenderer against
risk of Bidder`s conduct, which would warrant the forfeiture of security.
III. Critical dates and time
# Event Date and Time
1 Document Download
sale Start Date: 15 January 2020 End Date: 2 February 2020
2 Clarification Start Date: 16 January 2020 End Date: 22 January 2020
3 Bid Submission Start Date: 28 January 2020
End Date: 3 February 2020,
1700 hours Indian Standard
Time
4
Technical Bid Opening
Date 4 February 2020 At 1100 Hrs
Product features
demonstration Will be notified after the Technical Bid opening process
5 Financial Bid Opening
Date Will be notified after the Technical Bid opening Process
NOTE:
Kannur Airport may at its discretion extend / change the schedule of any activity by intimating the
bidders through a notification.
IV. Clarifications on tenders
13
i. All enquiries/clarifications in connection with this tender should be addressed to
ii. To assist in the examination, evaluation and comparison of Tenders, the Purchaser may, at
its discretion, ask the Tenderer for a clarification.
iii. The tenderer, at its discretion, extend the deadline for the submission of Tender by
amending the Tender Documents in accordance with Section III Critical Dates and Time
of this RFP, in which case all rights and obligations of the Purchaser and Tenderers
previously subject to the deadline will thereafter be subject to the deadline as extended.
iv. The queries may be restricted to that are essential for further clarification on any aspect of
the tender, if required. Queries requesting for extension of submission date and other terms
will not be entertained.
V. Late Tenders
Any tender submitted by the Bidder after the deadline for submission of Tenders will not be
accepted in the e-Portal.
VI. Modification and withdrawal of tenders
i. No Tender shall be modified subsequent to the deadline for submission of Tenders.
ii. No Tender shall be withdrawn in the interval between the deadline for submission of
Tenders and the expiration of the period of Tender validity specified.
iii. If the tenderer modifies the tender condition at any stage even after submitting the
unconditional acceptance letter, then the bid submitted by the tenderer are liable to be
rejected and the EMD / Security Deposit shall be forfeited.
MANAGING DIRECTOR
14
2.1. Introduction of Kannur International Airport Limited
Kannur International Airport Limited (Kannur Airport) is an unlisted public limited company
incorporated under the Companies Act,1956 to establish a Greenfield international Airport at Mattannur
in Kannur District. The airport is operational since December 2018.
2.2. Purpose
The purpose of this Request for Proposal (RFP) is to seek the services of a reputed IT Company, to
Procure, Design, Develop, Test and Implement Airport Operational Database (AODB), Resource
Management System (RMS) and Master Systems Integration (MSI) (as specified under clauses 3 to 8)
for Kannur Airport and to provide support for a minimum period of 5 years, commencing from the date
when the entire system goes “live” and the free Post Implementation Warranty Support of six (6) months
is completed. The bidder shall be required to give a lumpsum quote separately for the additional two
years as per the BOQ. This document provides information to enable the bidders to understand the broad
requirements to submit their "Bids". The detailed scope of work is provided in RFP document.
2.3. Cost of RFP
The cost of the document is INR 50,000/- (Rupees Fifty Thousand Only) + 18% GST and the same shall
be paid online.
2.4. Transfer of RFP
The RFP document is not transferable to any other bidder. The bidder who purchases the document and
submit shall be the same and only one tender document shall be sold to a single party either a firm or an
individual.
2.5. Consortium
Consortium Bidding shall be allowed but restricted to two partners. However, the prime bidder will hold
the Sole responsibility of the contract and its execution as a single point of contact to Kannur Airport.
2.6. Involvement of Sub-Contractor (s)
2.6.1. Where the Contractor expects to sub-contract a part of the specified Scope of Work, the
same must be clearly stated in the Bid, describing the work to be sub-contracted, the
reasons for sub-contracting and the details of the Sub-Implementing Agency, including
previous work done by the Sub-Implementing Agency in similar area. If the Contractor
had not envisaged involvement of any Sub-contractor while bidding, but desires to do so
during project execution, the Bidder must first get this approved by the Purchaser in
writing, giving necessary details.
2.6.2. The Overall responsibility lies with the Contractor and the Contractor shall submit an
undertaking on behalf of Sub-contractor for the fulfillment of the services for the entire
contract period.
2.6.2.1. Except as provided, the Contractor shall not be permitted to sub-contract any part
15
of its obligations under the Contract.
2.6.2.2. If the contractor selects the sub-contractors, the names and roles of the same shall
be clearly mentioned in the proposal/bid.
2.6.2.3. The Contractor shall ensure that the sub-contractor appointed has sufficient
capacity to undertake the execution of the tasks they will perform under this contract.
2.6.2.4. The Contractor indemnifies and shall keep indemnified Purchaser against any
losses, damages, claims or such other implications arising from or out of the acts and
omissions of such subcontractor. The Contractor shall be responsible for making all
payments to the subcontractor as may be necessary, in respect of any Services
performed or task executed, and the Purchaser shall not be responsible for any part or
full payment which is to due to such subcontractor.
2.6.2.5. All rights of use of any process, product, service or facility developed or any
other task performed by the subcontractor for the Supplier, under this contract would
lie exclusively with the Purchaser in perpetuity free from all liens, encumbrances and
other third party rights and the Supplier shall, wherever required, take all steps that
may be necessary to ensure the transfer of such ownership in favor of the Purchaser.
2.6.2.6. Nothing in the clause of the RFP shall relieve the Contractor from any of its
liabilities or obligations under this Contract. The Purchaser reserves the right to hold
Supplier liable for any act/omission of any subcontractor.
2.6.2.7. Where the Purchaser deems necessary, it shall have the right to require
replacement of any subcontractor with another subcontractor and the Contractor shall
in such case terminate forthwith all agreements/contracts other arrangements with
such subcontractor and find suitable replacement for such subcontractor to the
satisfaction of the Purchaser at no additional charge. Failure to terminate all
agreements/contracts with such sub-contractors, shall amount to a breach of the terms
hereof.
2.6.2.8. The Contractor shall be responsible for ensuring that the Subcontractor shall
comply with all relevant and applicable provisions of the Contract. In default on the
part of the sub-contractor to comply with the terms and conditions of the Contract
wherever applicable, shall amount to breach on the part of the Contractor, and the
Purchaser in addition to all other rights, have the right to claim damages add recover
from the Contractor all losses/ or other damages that may have resulted from such
failure.
2.7. Completeness of Response
Bidders are advised to study all instructions, forms, terms, requirements and other information in the RFP
documents carefully. Submission of bid shall be deemed to have been done after careful study and
examination of the RFP document and Existing Site conditions/facilities at Kannur Airport with full
understanding of its implications.
16
The response to this RFP should be full and complete in all respects. Failure to furnish all information
required by the RFP documents or submission of a proposal not substantially responsive to the RFP
documents in every respect will be at the Bidder's risk and may result in rejection of its Proposal and
forfeiture of the EMD / Security Deposit. However, Kannur Airport Reserves the right/ Discretion of
Accepting/ rejecting the proposal.
2.8. Proposal Preparation Costs
The bidder shall submit bid at its cost and, Kannur International Airport Limited shall not be held
responsible for any cost incurred by the bidder. Submission of bid and demonstration of the proposed
product does not entitle the bidder to claim any cost and rights over Kannur International Airport Limited
and Kannur International Airport Limited shall be at liberty to cancel any or all bids without giving any
notice. All materials submitted by the bidder shall be the absolute property of Kannur International
Airport Limited and no copyright/patent etc. shall be entertained by Kannur International Airport Limited.
2.9. Bidder Inquiries
Bidder shall send their email queries as prescribed into the contact at which the bids are to be submitted.
There is no limitation to number of questions posted. The last date for receiving the questions is 22 January
2020. Questions received from all respondents would be consolidated and clarification to each question
would be sent to all the respondents latest by 27 January 2020. No telephonic queries will be entertained,
this response of Kannur International Airport Limited shall become integral part of RFP document.
2.10. Amendment of RFP Document
All the amendments made in the document would be published at https://www.kannurairport.aero/tender
and shall be a part of RFP.
The bidders are advised to visit the aforementioned website on regular basis for checking necessary
updates. The Kannur International Airport Limited also reserves the rights to amend the dates mentioned
in this RFP for bid process.
2.11. Supplemental Information to the RFP
If Kannur International Airport Limited deems it appropriate to revise any part of this RFP or to issue
additional data to clarify an interpretation of provisions of this RFP, it may issue supplements to this RFP.
Any such corrigendum shall be deemed to be incorporated by this reference into this RFP.
2.12. Right to terminate the process
Kannur International Airport Limited may terminate the RFP process at any time and without assigning
any reason. Kannur International Airport Limited reserves the right to amend/ edit / add/ delete any clause
of this Bid document and will become part of Bid/ RFP.
2.13. Earnest Money Deposit (EMD) / Security Deposit
i. Earnest Money Deposit (EMD) / Security Deposit of INR 1,00,00,000/- shall be paid as
detailed in the Tendering guidelines to the bidders.
17
ii. The EMD / Security Deposit shall be denominated in Indian Rupees only. No interest will be
payable to the Bidder on the amount of the EMD.
iii. Unsuccessful Bidder’s EMD / Security Deposit will be returned to the unsuccessful bidder
15 days after the award of work to the successful bidder. In case of successful bidder,
EMD / Security Deposit will be returned, without interest on submission of Performance
Bank Guarantee.
iv. The EMD / Security Deposit may be forfeited
a. If a Bidder withdraws the bid or amends the bid in anyway or increases the quoted prices
during the period of bid validity or its extended period, if any;
b. In case of a successful bidder, fails to sign the Contract or to furnish Performance Bank
Guarantee within specified time i.e. 30 (Thirty) days from the date of issue of award of
work in accordance with the format given in the RFP.
c. During the bid process, if a Bidder indulges in any such deliberate act as would
jeopardize or unnecessarily delay the process of bid evaluation and finalization. The
decision of the Kannur International Airport Limited regarding forfeiture of the Bid
Security shall be final & and binding upon bidders.
d. During the bid process, if any information is found false/ fraudulent then Kannur
International Airport Limited shall reject the bid and if necessary, initiate action.
2.14. Authentication of Bid
The bid documents should be signed (all pages) and submitted along with the bid. Authorized person of
the bidder who signs the bid shall have a board resolution / Registered/ Non-revocable Power of Attorney
executed by the bidder which shall also be submitted with the Bid. All pages of the bid and its annexures,
etc. shall be signed and stamped by the person or persons signing the bid. The person accountable for the
bid shall be the employee of the bidder till the end of contract period.
2.15. Language of Bids
This bid should be submitted in English language only. Any supporting document produced in language
other than English shall be translated and notarized.
2.16. Bid Submission Format
The entire proposal shall be submitted strictly as per the format specified in this RFP. Bids with deviation
from this format shall be rejected.
2.17. Submission of Bids
The bids submitted by the Bidder shall comprise of the following two covers: (a) Cover-I (b) Cover –II.
18
2.18. Bid Validity Period
The validity of the bids submitted in time shall be till 120 days from the date of opening of the Financial
Bid. No liability will be borne by Kannur International Airport Limited on the rejected bids for the cost
in preparation of bids etc.
2.19. Bid Opening
Refer Tendering guidelines. (2. II)
2.20. Evaluation Process
2.20.1. Bid Evaluation Committee
a. The Bid Evaluation Committee constituted by the Kannur International Airport
Limited shall evaluate the bids.
b. The Bid Evaluation Committee shall evaluate the Technical and Financial bids and
submit its recommendation to Competent Authority whose decision shall be final.
2.20.2. Eligibility Criteria
The bidder shall fulfil all the following eligibility criteria:
# Eligibility Criteria Supporting Document to be
furnished
Compliance
Status
(Yes/No)
1
The Bidder should be partnership firm registered
under the Partnership Act / .limited Liabiliy
Partnership Act or Companies Act,1956/ 2013,
should have registered office in India and should
be in existence in India for at least the last five (5)
years as on date of submission of the bid.
Certificate of Incorporation/
Registration
2
The bidder shall have minimum average annual
turnover of INR 500 Crore (Globally) for the last
five years for Software Development and System
Integration Services
As a proof of financial
turnover, copy of abridged
Balance Sheet along with Profit
& Loss account of the firm
(bidder) for last five years
ending 31 March 2019 should
be submitted. A Certificate
from Statutory Auditor / CA
stating shall also be accepted as
a proof of financial Turnover,
net worth and profitability.
19
Note: The Bidder needs to submit the Eligibility Criteria form in Cover-I mentioning the Compliance
Status in respect of eligibility criteria in the above-mentioned format along with the bid documents.
The Technical & Commercial proposals of only such bidders will be opened, who fulfil Eligibility Criteria
as mentioned above.
2.20.3. Process of Evaluation
i. Bidder shall be evaluated as per eligibility criteria mentioned at 2.20.2. The bidders
who fulfil all the eligibility criteria will qualify for further Technical Evaluation.
ii. Bidders scoring 70 marks or above in technical evaluation will be considered to be
eligible for financial evaluation.
iii. The financial evaluation will be based on a QCBS system with 70:30 weightage to
(Technical Requirements & The Quoted Price). The bidder with the highest score on
the merit-based system as above will be deemed to be the L1 bidder.
3
The bidder or the consortium Experience of having
successfully completed similar works as indicated
below at an International Airports in India or
abroad, during the last 05 years prior to date of
issue of this tender: -
At least two similar works involving Airport
Operational Database (AODB) implementation,
Resource Management System (RMS)
implementation and Master Systems Integration
(MSI),in an international airport in India or abroad
of value of 15 crore and above.
Attach copy of Letter of Awards/PO along with
successful completion certificate. “Similar works”
shall mean Procurement, Design, Development,
Testing and Implementation of an Airport
Operational Database (AODB)& Resource
Management System (RMS) software and Master
Systems Integration (MSI).
Copy of Purchase Order from
Client. Copy of certificate of
completion of the projects
done.
Shall submit substantial
completion certificate in case
the contract is still live (A
completion certificate shall be
obtained from the client for
the completion of
development and testing of
core modules)
4
Bidder or one of the Bidders in case of consortium,
should possess CMMi Level 5 and any the below
valid Certifications which are valid at the time of
bid submission:
• ISO 20000:2011/20000-1:2011for IT
Service Management
• ISO27001:2005forInformationSecurity
Management System
Copies of valid certificates in
the name of bidder.
20
iv. The Bid Evaluation Committee reserves the right to accept or reject any or all bids
without giving any reasons thereof.
v. To facilitate evaluation of Technical proposals, the Kannur International Airport may,
at its sole discretion, seek clarifications or additional information / document(s) in
writing from any bidder regarding its proposal. Such clarifications or additional
information/document(s) shall be provided within the time specified by Kannur
International Airport for the purpose. Any request and response thereto shall be in
writing. If the bidder does not furnish the clarification(s) or additional
information/document(s) within the prescribed time, the proposal shall be liable to be
rejected. In the case the proposal is not rejected, Authority may proceed to evaluate the
proposal by construing the particulars requiring clarification to the best of its
understanding, and the bidder shall be barred from subsequently questioning such
interpretation of the Authority.
2.20.4. Technical Eligibility Criteria
Each Proposal which qualifies in Cover-I shall be scrutinized further and evaluated accordingly to the
following criteria and granted a score. If the score is 70 or above, the bidder will qualify for further
evaluation (cover-I financial bid). The proposal with score less than 70 shall be disqualified and bidder
will not be eligible for further evaluation.
# Evaluation Criteria Points
A Relevant Experience Max 10
The Bidder should have Designed, Developed, Tested and Commissioned and
maintained Airport Operational Database (AODB), Resource Management
System (RMS) and Master Systems Integration (MSI)works as given in 2.20.2
Table Item No 3. The marks shall be awarded based on the following: -
(i)
Designed, Developed, Tested and Commissioned and maintained Airport
Operational Database (AODB), Resource Management System (RMS) and
Master Systems Integration (MSI) works at an airport of value 25 Crore and
above
10
(ii)
Designed, Developed, Tested and Commissioned and maintained Airport
Operational Database (AODB), Resource Management System (RMS) and
Master Systems Integration (MSI) works at an airport of value 20 Crore and
above
8
(iii)
Designed, Developed, Tested and Commissioned and maintained Airport
Operational Database (AODB), Resource Management System (RMS) and
Master Systems Integration (MSI)works at an airport of value 15 Crore and
above
5
(iv)
Designed, Developed, Tested and Commissioned and maintained Airport
Operational Database (AODB), Resource Management System (RMS) and
Master Systems Integration (MSI)works at an airport of value 10 Crore and
above
2.5
B Company Profile Total 45
21
1
The Bidder should be registered under the Partnership Act or Companies Act,
2013, should have registered offices in India and should be in existence in India
for at least the last 5 years as on date of submission of the bid.
Max 5
(i) More than 15 years 5
(ii) 10 - 15 years 3
(iii) 5 Years or above, but less than 10 Years 1
2
Bidder or one of the Bidder in case of consortium, should possess CMMi Level
5 and any one of the below valid Certifications which are valid at the time of
bid submission:
• ISO 20000:2011 for IT Service Management
ISO 27001:2005 for Information Security Management System
Max 5
(i) More than 10 Years 5
(ii) 5-10 Years 3
(iii) 3 Years or above but less than 5 Years 1
3 The bidder must have an aviation SME with technology background, involved
with minimum 10 years of experience in aviation technology projects Max 5
(i) 20 years 5
(ii) 15 years 3
(iii) 10 years 2
4 The bidder must demonstrate the product capabilities to establish requirements
compliance Max 20
(i) 100% 20
(ii) 85% compliance 10
(iii) 75% compliance 5
5 Compliance Certifications Max 5
(i) ISO27001:2013 or ISO27017:2015 or ISO27018:2014, 5
6 Willingness to assist in preparing Standard Operating Procedures and workflow
management Max 3
(i) Willingness to assist in preparing Standard Operating Procedures and workflow
management 3
7 The bidder’s willingness to invest in Kannur Airport’s Innovation lab Max 2
(i)
Willing to showcase innovative solutions at innovation lab and take part in
Corporate Social Responsibility activities that will be conducted by Kannur
Airport
2
C Proposed Team Leader Total 13
1 Certification Max 5
(i) Information Technology Certifications 2.5
22
2.20.5. Financial Bid Evaluation
Kannur International Airport Limited shall evaluate Financial Proposals of eligible bidders. If
there is a discrepancy between words and figures, the amount in words shall prevail. For any other
calculation/ summation error etc. the bid may be rejected.
a) The evaluation will be conducted on a QCBS based evaluation system with a 70:30 weightage
(Technical/Financial). The contract will be awarded to the vendor, arriving as L1 on a merit-
based evaluation in the above QCBS process.
b) In the Bill of Quantities (Financial Bid), Only Sl. No.i to iv will be considered for financial
bid evaluation.
(ii) Project Management Certifications i.e., PMP or Prince 2 2.5
2 Qualification Max 4
(i) Post Graduate Qualifications (MSc IT / M.Tech / MCA / M.E) 4
(ii) Graduate Qualifications (BSc IT / B.Tech / BCA / B.E) 2
3 Past Experience (quality & relevance of experience) Max 4
(i) 10 + years 4
(ii) 5 - 10 years 2
(iii) Less than 5 Years 1
D. Technical Presentation Total 27
(i) Project Experience for the Previous Projects Done 7
(ii) Understanding of Scope of Work 5
(iii) Solution Deployment Architecture including integration 2
(iv) Approach, Methodology & Project Plan 2
(v) Quality and Security Assurance Plan 2
(vi) Innovation & New Ideas 5
(vii) Training Plan 1
(viii) Adherence to SLA, Monitoring & Review Framework 2
(ix) Understanding of Industry Department Functions, Services and Processes 1
E. Project Management Office 5
(i) Clearly defined PMO structure, change management approach &
implementation plan and governance 5
(ii) Basic PMO structure, change management and governance 2
Total 100
23
c) In BOQ, Sl.No. v will be required for entering into a contract for O&M support after the
expiry of 5 years O&M contract stipulated in this RFP. However, quoted price for the 6th and
the 7th year shall not exceed by 10% or Consumer Price Index (CPI) whichever is lower ,
based on the average annual O&M support cost for the initial 5 years.
d) In the event, the quotes so obtained are ‘tied’, the bidder with the highest technical score will
be adjudicated as the Best Value Bidder for award of the Project.
2.21. Performance Bank Guarantee (PBG)
a) The Bidder shall at his own expense, deposit with Kannur International Airport Limited,
within 30 (Thirty days) of the date of issue of Letter of Award or prior to signing of the
contract, whichever is earlier, an unconditional and irrevocable Performance Bank Guarantee
(PBG) from a Nationalized Bank or any Scheduled Bank acceptable to Kannur International
Airport Limited as per Form 3, payable on demand, for the due performance and fulfilment
of the contract by the bidder.
b) This Performance Bank Guarantee will be for an amount equivalent to 10% of the contract
value, in two parts as mentioned below. All charges whatsoever such as premium,
commission, etc. with respect to the Performance Bank Guarantee shall be borne by the
bidder. First part of the PBG for an amount of 10% of the Implementation and
License/Software cost excluding the O&M contract cost, need to be submitted within 30 days
of awarding the contract. The EMD received in respect of the successful bidder will be
returned to the bidder, only after the receipt of the PBG. The PBG should be valid for a term
of one and a half years from the date of work order or till the completion of Go-Live and
submission of the second part of the PBG for the O&M period. Second part of the PBG for
an amount of 10% of the O&M contract cost spreading over a period of five years, post Go-
Live and the six months warranty period, need to be submitted prior to the commencement
of the O&M period. The first part of the PBG received from the bidder will be returned only
after the receipt of the second part against the O&M. The second PBG should be valid for a
term of five year from the date of commencement of the O&M period.
c) The first part of the Performance Bank Guarantee towards the Installation/License should be
valid for a period of 18 months from the date of work order and should be in the format
prescribed in the tender. The second part of the PBG towards the O& M support should be
valid for a period of 5 years from the date of the commencement of the O&M period.
d) The Performance Bank Guarantee may be discharged/ returned by Kannur International
Airport Limited upon being satisfied that there has been due performance of the obligations
of the Bidder under the contract. However, no interest shall be payable on the Performance
Bank Guarantee.
e) Kannur International Airport Limited shall also be entitled to make recoveries from the
Bidder’s bills, performance bank guarantee, or from any other amount due to him, the
equivalent value of any payment made to him due to inadvertence, error, collusion,
misconstruction or misstatement.
f) PBG submitted by bidder need to be revised/ extended, in case of delay/default on the part of
agency as may be required by Kannur International Airport Limited.
24
g) PBG should be en-cashable on demand; Bank should have no right to question the claim of
Kannur International Airport Limited.
2.22. Payment Terms and Schedule
Refer to annexure 12, Form 4 for details
(a) Operation and Maintenance
The total quoted amount for O& M shall be paid in 20 Equal Quarterly installments (Every three months
in arears) during the initial 5 years of paid maintenance period. If Kannur Airport opts for the additional
two years of O&M Support, the lumpsum quote for the additional two years shall be paid in eight equal
quarterly instalments.
10% payment under para 2.21(a) and 2.21(b) will be paid to the vendor only against a Bank Guarantee
for equal amount, valid for a period of one and half year. This Bank Guarantee will be returned to the
vendor, along with the second part of the payment (i.e. on delivery of software / licenses &Design Sign
off).
2.23. Service Level Agreement (SLA) and Penalty during Operation and
Maintenance
The Service Level Agreement (SLA) will be based on the stipulated minimum uptime to be guaranteed
for various category of modules after Go-live and during the entire O&M period. The stipulated minimum
uptime and the penalty for not adhering to the SLA shall be as per table below:
*Note:(1) SLA for response time, resolution time and relevant penalties shall be applicable per
incident
The penalty will be capped to a maximum limit of 10% of the contract value excluding the O&M cost,
during the warranty support period and 25% of the Quarterly O&M amount for each quarter during the
O&M period. The Contractor shall deploy suitable tools to monitor the module wise serviceability of the
Airport Operational Database (AODB)& Resource Management System (RMS) software.
The SLA Computation and Other details are attached as Annexure8.
Description Uptime
Percentage Penalty (INR)
Highly Critical Modules 99.99* 25,000 for each .01 % point of downtime
Critical Modules 99.9* 20,000 for each .01 % point of downtime
Other Modules 99* 15,000 for each .01 % point of downtime
25
2.24. Design, Development, Testing, Implementation and Integration
i. Implementation plan should detail complete implementation of Airport Operational Database
(AODB), Resource Management System (RMS) & Master Systems Integration (MSI)
including the data migration that are essential for the implemented systems to perform as
required, without any hindrance or restriction.
ii. Penalties: In case of delay in Design, Development and going LIVE of Whole Package
(Excluding O&M) within six (6) months of the issue of the work order, then a sum equivalent
to one (1) % of the total contract value shall be deducted from the payment for each week of
delay or part thereof.
(a) Delay in excess of 4 weeks will be sufficient to cause for termination of the contract.
In that case the Performance Bank Guarantee of the bidder will be forfeited.
(b) In case, the selected bidder does not supply the ordered items/services for any reason,
the bidder will be liable to pay the difference amount to the purchaser, over and above
the performance guarantee, which indenter Kannur International Airport Limited
must pay to the next or other selected bidder for purpose of the said items.
2.25. Letter of Acceptance
The Bidder whose bid has been accepted shall be notified of the award by the Kannur International Airport
Limited prior to the expiration of the period of validity of the proposal, by registered letter or by fax. The
Bidder shall acknowledge in writing, the receipt of the Letter of Acceptance and shall send his acceptance
to enter into the Contract within 15 (fifteen) days from the receipt of the Letter of Acceptance.
2.26. Force Majeure
The Bidder shall not be liable for forfeiture of its Performance Security, liquidated damages, 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. For purposes of this Clause,
“Force Majeure” means an event or situation beyond the control of the Bidder that is not foreseeable, is
unavoidable, and its origin is not due to negligence or lack of care on the part of the Bidder. Such events
may include, but not be limited to, acts of Kannur International Airport Limited in its sovereign capacity,
wars or revolutions, fires, floods, epidemics, quarantine restrictions, and freight embargoes. If a Force
Majeure situation arises, the Bidder shall promptly notify Kannur International Airport Limited in writing
of such condition and the cause thereof. Unless otherwise directed by Kannur International Airport
Limited in writing, the Bidder shall continue to perform its obligations under the Contract as far as is
reasonably practical and shall seek all reasonable alternative means for performance not prevented by the
Force Majeure event.
2.27. Non-Disclosure Agreement (NDA)
Successful bidder must sign the Non- Disclosure Agreement (Annexure 9) with Kannur International
Airport Limited.
26
2.28. Liability Clause
A. Any fine imposed by agencies including legal agencies against the contractor’s personnel
directly or indirectly involved in the implementation and O&M support, should be fully borne
by the contractor.
B. If a third-party claim that deliverables the contractor provided to Kannur Airport infringe that
third party’s copy right or intellectual proprietary, the contractor should be responsible to
defend Kannur Airport against that claim at its expense and pay all costs, damages, court
charges etc. that a court finally awards or the amount included in a settlement of the claim, as
applicable.
C. In the event that Bidder is delayed or prevented from performing its obligations due to failure
by the Kannur Airport or its employees or agents or delay on the part of or on behalf of
Kannur Airport, then Bidder shall be allowed an additional period of time to perform its
obligations and unless otherwise agreed the additional period shall be equal to the amount of
time for which Bidder is delayed or prevented from performing its obligations due to such
failure or delay on the part of or on behalf of the Kannur Airport.
2.29. Warranty
Bidder shall warrant that the delivered software meets the requirements as specified in the detailed
Specifications of the Application Software. This warranty shall remain valid for six (6) months after the
system Go Live at Kannur Airport. Kannur Airport shall promptly notify Bidder in writing of any ‘defect’
in the software arising due to the reasons solely and entirely attributable to Bidder under this warranty.
Upon receipt of such notification, Bidder shall remove the ‘defect’ in the application software. Warranty
shall also include changes or modifications that becomes essential for giving the intended performance of
the system, as specified in the approved Specifications. In case of breach of this warranty, Kannur
Airport’s exclusive remedy will be to obtain (1) the re-performance of the service or the correction or
replacement of any service deliverable that provides substantially similar functionality or (2) if both
parties mutually determines that such remedies are not practicable, a refund of the fees allocable to that
part of the deliverable will be due to Kannur Airport if already paid by the Kannur Airport.
2.30. Confidentiality
Both parties agree that they may, in the course of their business relationship with the other, acquire or be
exposed to information that is proprietary or confidential to the other party, its affiliates or its or their
respective clients. Both parties undertake, to hold all such information in strictest confidence and not to
disclose such information to third parties nor to use such information for any purpose whatsoever save as
may be strictly necessary for the performance of the assignment as mentioned in this proposal.
2.31. Contract Termination
The Kannur Airport may, for its convenience and with 30 days prior written notice to the Contractor,
terminate this contract in whole or in part and without payment of any penalty or incurring any further
obligation to the Contractor. The Contractor shall be entitled to compensation upon submission of
invoices and proof of claim for supplies and services provided in compliance with this contract up to and
including the date of termination.
27
3. Scope of Work
Through this tender Kannur Airport plan to implement an Airport Operational Database (AODB),
Resource Management System (RMS) and Master Systems Integration (MSI), accommodating various
operational, administrative and integration requirements of the Kannur Airport as follows:
The detailed scope of work is as given below:
I. Conduct ‘As-is’ Study to finalize the Functional and non-functional requirement for all the
Stakeholders.
a) As part of this exercise, the Contractor will have to:
i. Study the existing network architecture and end user hardware and propose the
required ‘Bill of Material’ for Cloud and on-premise instance to manage the servers,
storage, virtualization and networking.
ii. Submit the ‘As-is’ report and the recommended ‘To-Be’ report along with the gap
analysis.
iii. Detailed Functional Requirement document after conducting a detailed study in
Kannur Airport.
iv. Recommend the required network sizing to support the expected performance of
Airport Operational Database (AODB)& Resource Management System (RMS):
a. Minimum specifications for end user computing devices such as laptops,
workstations
b. Minimum specifications of servers, operating system, database and other required 3rd
party tools to host an instance on-premises at Kannur airport
b) Host Airport Operational Database (AODB) & Resource Management System (RMS)
applications on the primary and secondary data centers, one on premise and another on cloud
environment. Kannur Airport will decide which one will be the primary.
c) Data cleansing and migration (including master and transaction data).
d) Integration with other existing application Software.
e) Providing Helpdesk support and annual operations and maintenance support
f) There should be guaranteed uptime for Airport Operational Database and Master Systems
Integration cloud of 99.9%. The planned downtime should occur once a month and should
not last no longer than eight hours.
g) Providing training covering all the functional users, technical users and end users over a
minimum of five (5) training sessions.
h) Provide two (2) hardcopies of and a soft copy of the training documentation.
i) Implementation of approved Change Requests.
28
II. Supply, Installation, configuration, Data Migration, Documentation, Testing, Training and
commissioning of the chosen Airport Operational Database (AODB) and Resource Management
System (RMS)solution along necessary licenses for Integration and support <<number of licenses
to be included>>for the chosen Airport Operational Database (AODB), Resource Management
System (RMS) and Master System Integration. The Contractor shall ensure the licenses are valid
and available to the Kannur Airport users for the entire duration of the contract from Go-Live
including the warranty period and O&M contract period. Contractor may use his discretion to
procure the licenses at an early date as required for the development and implementation, but this
shall not hinder the availability of licenses to Kannur Airport users after Go-Live as indicated
above. The contractor is should also be the Master System Integrator (MSI) for the project.
III. Kannur Airport may at its own discretion opt to purchase the Airport Operational Database
(AODB) and Resource Management System (RMS)licenses directly from the OEM. In the event
of a decision to allow the Contractor to purchase the licenses, the Contractor shall, at its own cost,
shall transfer the licenses to Kannur Airport during the termination or expiry of the O&M contract.
IV. The design must address the requirements such as high availability, scalability, modularity,
manageability, future development and integration feasibility and low operating and maintenance
costs. Applying international standards where applicable further underpins the flexibility and
viability of the design.
V. The developed software shall have comprehensive warranty for six (6) months after
commissioning of the entire system from the date of Go-live. Any changes that would be
warranted for ensuring the intended functionality, which might not have been apparent during the
UAT, and within the scope of the RFP, would have to be undertaken by the Contractor during
this period. Incase, such requirement if outside the scope of this RFP, shall be implemented by
the Contractor at an additional cost, based on the quoted man month cost by the Contractor. The
reasonable manhours required for completing such changes would be decided on a mutually
agreeable terms between Kannur Airport and the Contractor.
VI. The Contractor must associate with Kannur Airport till the completion of the O&M period of five
years, post completion of the warranty period. The Contractor may have to provide this service
for another two years at the discretion of Kannur Airport, if Kannur Airport is satisfied and
decides to extend the contract with the Contractor.
a. During this period of O&M, the Contractor must assist Kannur Airport in identifying
additional software/hardware required for enhancing the functionality and should also make
necessary changes in the operational database and other modules for integrating third party
software systems on mutually agreed terms. This does not bind Kannur Airport to buy the
future requirements from the Contractor. Kannur Airport would be the sole judge in selecting
software. The Contractor should suggest packages which are proven and acceptable in the
airport operations.
b. The AMC/renewal charges for the licenses for the specified users licenses to support
<<number of licenses to be included>> for the chosen Airport Operational Database (AODB)
and Resource Management System (RMS) platform during the entire O&M period should
also be part of the O&M contract.
29
VII. The Contractor should have very good knowledge in software used in airports across the globe
and the technical details used in civil aviation.
VIII. Requirements defined here are conceptual, but not exhaustive. However, within the framework
set herein there can be variations, depending upon the system study by the Contractor and his
interaction with the users, after which development and customization would be carried out.
IX. If any works, services, functions or responsibilities not specifically described in this RFP, are an
inherent, necessary or customary part of the services or are essential for the proper performance
or provision of the intended services, they shall be deemed to be included within the scope of
work and is to be delivered as part of the contract without any additional cost.
X. At any point of time before the end of System Design if Airport Operational Database (AODB)
and Resource Management System(RMS) OEM introduces technological advance (including
new version) for System Design if Airport Operational Database (AODB) and Resource
Management System(RMS)product originally proposed in the Bid, the Contractor shall be
obligated to supply, configure and implement the latest version of the available sub-system(s)
having equal or better performance or functionality at the same or lesser unit price as compared
to that contained in this Bid.
30
4. Project Milestones
Supply, Installation, data migration, training, testing and commissioning of the system shall be completed
within nine (9) from the order date. A detailed Project plan needs to be submitted by the contractor before
commencement of the project. An indicative timeline is tabulated below.
# Milestone Timelines
1 Contract Award to Contractor D0*
2 Business process analysis and documentation D0 + 30
3 Functional Requirements Specifications document D0 + 45
4 System design D0 + 65
5 Data Migration Strategy/Plan D0+75
6 System customization and interfaces development D0 + 95
7 Conference Room Pilot 1 D0+125
8 Conference Room Pilot 2 D0 + 155
9 Test Plan and scenarios documentation D0 + 170
10 Business rules and related configuration setup
(Departments and user IDs with access rights) D0 + 180
11 Data Migration D0 + 200
12 Business administrator training D0 + 220
13 IT administrator training D0 + 220
14 Integration Testing D0 + 230
15 Performance testing D0 + 245
16 Endurance testing D0 +255
17 Training - End users D0 + 265
18 System readiness for user acceptance testing D0 + 270
19 User Acceptance testing D0 + 270
20 Soft cutover D0 + 280
21 Full cutover D0 + 290
* D0 is the date of contract award plus 7 days
31
5. Deliverables
The following need to be ensured during the project.
a. Airport Operational Database (AODB), Resource Management System (RMS) and Master
Systems Integration architecture
b. Detailed design of Airport Operational Database (AODB) & Resource Management System
(RMS)including integration with Kannur Airport systems
c. Detailed specifications and requirement of hardware/networking equipment for the proposed
solution.
d. Project Plan along with manpower deployment plan
e. Functional and Non-functional requirements Specification of Airport Operational Database and
Master Systems Integration
f. Flow charts and detailed design of the software
g. License copies of the software, Database along with license certificates
h. Airport Operational Database (AODB), Resource Management System (RMS) software,
Database implementation, middleware, third party software as per the requirement of the project
i. Service Oriented Architecture (SOA) based integration with Kannur Airport’s Airport
Operational Database (AODB)& Resource Management System (RMS), non-aeronautical
concessionaires’ systems for required for aeronautical and non-aeronautical billing. Refer to
Section 6, point 21 for detailed list of interfaces.
j. Service Oriented Architecture (SOA) based integration with Kannur Airport data platform to
publish the required data for necessary analysis and insights.
k. Detailed SOPs for all Airport Operational Database (AODB), Resource Management System
(RMS) and Master Systems Integration business process flows along with workflow
management
l. Intuitive dashboards that covers operational, regulatory and statutory reports requirements
m. User Manuals, Technical Manual, System Admin Manual and Troubleshooting Manuals
n. Source code of all the software developed as part of customization specific to Kannur Airport and
all packages with detailed comments and descriptions as per the practices in vogue in the industry.
o. In the case of Airport Operational Database (AODB), Resource Management System (RMS) and
third party off the shelf products, the details of customization and developments from the core
package with detailed comments and description also should be provided.
p. In case of open source software, if used for any reason, the Contractor should provide a certificate
for the software support from a relevant tech support firm or should certify themselves as a
guarantee for the software support for a period not less than five years from the date of acceptance
by Kannur Airport.
q. Provide maintenance and support services in coordination with Kannur Airport’s IT Help desk
team or any other as nominated by Kannur airport.
Wherever applicable, the Contractor shall provide advanced proven products in service at several other
locations that do not require any further research and development and are in current production of the
OEM. A certificate from OEM assuring product support for a minimum period of five years commencing
the date of acceptance by Kannur Airport should be provided to Kannur Airport by the Contractor.
32
5.1. Technical Architecture
The system comprising of the transaction modules for each wing shall enable the Kannur Airport
Managers to transact, access and capture different information across different wings through a single
portal interface.
The Bidder shall clearly define the technical architecture proposed to meet the functionality and
the same shall be based on the state-of-the-art solution having the following features.
The architecture should have the following features:
5.1.1 Scalability
The system shall be scalable in respect of the Modules and Functionality both in respect of downsizing
and upsizing facilitating its installation at larger or smaller airports, as the case may be. The scalability of
the systems described shall be substantiated as application server capacity based on transactions per
minute tpm = no of flights x frequency of update x no. of users. During the detailed design phase, the
figures shall be substantiated to support Kannur airport’s resource management, flight movements and
other business operations to deal with 2.5 million passengers per year (and up to 8 million passengers
over 5 years) based on:
(a) Users at the airport operations centre accessing the applications
(b) Other users accessing the applications
(c) Number of flights per day
(d) Number of information updates per day
(e) Figures for the traffic estimates extrapolated by the bidder based on ICAO forecasts
5.1.2 User friendly
The software in question should be such that Screens are user friendly. It should have Intuitive interface
based on internet portal styles to significantly reduce end-user training.
5.1.3 Multi-user Multi-tasking
Complete System shall be multi-user and Multi-tasking.
5.1.4 Open Data Structure
The software package shall have data structures on open architecture and as per accepted international
standards such that it facilitated easy integration with other applications on the Network.
5.1.5 Standard Communication Mechanism
Standard Intranet and Non-Intranet Communication Mechanism shall be used for inter-Application
Communication.
5.1.6 Security
Security to ensure information access to the right users while restricting sensitive material from
33
unauthorized users. Only approved content can be kept in the portal/ Kannur Airport’srepository. The
system shall not permit storage of data on the local hard disks. The administrator(s) must be able to create
workgroups of users. Security should be inbuilt in to the system. Proposed system should not be vulnerable
for virus attacks or hacking. Tightening of the security aspects of the systems, in order to safeguard against
accidental or intentional damage to information and equipment should be provided.
5.1.7 Integration Architecture
Please refer to section 7 (Non-functional requirements) point no 18 for the indicative Integration
architecture. The bidder is expected to come-up with a detailed integration architecture based on their
study in Kannur Airport once selected for the project.
5.2. System Architecture
a. The system shall utilize a multi-tier architecture. End devices shall be clients to the applications
servers. Application servers in turn shall communicate with the database servers. All information
shall be communicated between the server(s) and clients using the Kannur Airport Local Area
Network using a dedicated VLAN and/or dedicated secured tunnel.
b. Network communications shall utilize TCP/IP network communications protocol. The Contractor
shall identify the network bandwidth required to support the Airport Operational Database
(AODB), Resource Management System (RMS) and Master System Integration (MSI).
c. The system architecture shall be resilient and redundant with automatic fail-over to ensure that
performance and high-availability objectives are met without manual intervention. All major
system components shall be designed so there is not any single point of failure causing disruptions
to operations.
d. All Data interfaces between Airport Operational Database (AODB), Resource Management
System (RMS)and other systems shall be coordinated with other contractors and shall utilize
Kannur Airport’s Integration platform.
5.2.1 Production environment
The production instances in cluster mode is the live server in which day to day operations
are carried out. The production instances will be constantly monitored for utilization and
uptime. It may be on-premise or on-cloud.
5.2.2 DR environment
The DR server needs to be planned on the cloud. The Contractor should work out the
specifications of the cloud resource during the initial phase and assist Kannur Airport in
procuring and implementing the same.
5.2.3 Test Environment
All the preliminary testing should be done in the test server. The data should be periodically moved from
productive environment to test server. The module testing and integration testing are done in test server
along with data sets.
5.2.4 Purging
There should be a facility to purge the previous year’s data as well as unwanted data as per Kannur
34
Airport’s data retention policy.
5.2.5 Back up
There should be provision for easy backing up of the entire system and restoring the data in the event of
a failure. The Contractor should suggest suitable back up devices and methodology.
5.2.6 Help Facility
The software should have an in-built help module. A tip provider, error warning signals etc. are required.
5.2.7 Audit Trail
There should be a facility to track the activities performed by individual user. This should enable the
system administrator to find out the person who had performed activities like deletion of files,
modification of critical data, etc.
5.3. Admin and User Management
The system has several modules dedicated to overall administration of the system. These are described in
more detail in the following sub-sections:
5.3.1 Access Management
The management of access to the data and applications will be coordinated by the central system.
Authorities for applications, function in the application and authorities for the individual functions will
be organized there. The authorities to access the various applications and thus the data can be processed
using the particular application will be checked with respect to the user ID and password. Applications
for which the user has no authority will not be displayed. Functions within an application for which user
has no authority will be shown as inactive on the Windows dialog.
To protect certain production data from prohibited access, a “carrier” can be specified for certain users so
that they only have access to data.
5.3.2 User logging
The log-in, log-out and other actions of all the users will be automatically recorded in the audit files. A
tool to evaluate these logs can be provided.
5.3.3 Alerter
The Alerter is a tool that displays the alert messages that result from erroneous states in interface
connections. The ‘alert’ tool is an independent client module that contains the functionality of an error-
reporting tool. The purpose is to indicate errors to supervisory employees regarding interface connections.
Based on the information provided in the message, the supervisor can then act to resolve the problem.
After clarifying the error, the status can be changed directly from the user interface of the Alerter.
5.4. Training Services
35
The Contractor is responsible to ensure that the nominated resources by Kannur Airport are trained on the
intended task to be performed on the system. He should ensure the following: -
a) User training to different user groups based on the nature of usage.
b) Training of power users.
c) Training the technical team on configuration and customization.
d) Onsite support to resolve post installation issues.
e) Provision of comprehensive documents for the above stages including training documents,
User Manuals and Technical Literature.
f) Any other relevant services or documents
5.5. Resource Management, Monitoring & Compliance Services
5.5.1 Cloud / On-premise Resource Monitoring
Capability to monitor cloud / On-premise environment centrally, custom monitoring metrics, monitor and
store logs, view graphs & statistics, set alarms, monitor and react to resource changes. Support monitoring
of custom metrics generated by your applications and services and any log files your applications
generate. Gain system-wide visibility into resource utilization, application performance, and operational
health, using these insights to react intelligently and keep applications running smoothly.
5.5.2 Personal Health Dashboard
Provide alerts and remediation guidance when CSP is experiencing events that may impact the customer.
Personalized view into the performance and availability of the Cloud / On-premise services underlying
your Cloud / On-premise resources.
5.5.3 Audit Trail
Logs of all user activity within a CSP account including actions taken through the CSP's Management
Console, CSP's SDKs, command line tools, and other CSP services. The recorded information includes
the identity of the API caller, the time of the API call, the source IP address of the API caller, the request
parameters, and the response elements returned by the Cloud / On-premise service.
5.5.4 Encryption requirement
Capability to encrypt data at rest and data in motion in between Kannur Airports systems and ERP.
5.5.5 Governance & Compliance
Capability to discover all of cloud resources and view the configuration of each. Continuously monitor
and record your Cloud / On-premise resource configurations and allows you to automate the evaluation
of recorded configurations against desired configurations. Receive notifications each time a configuration
changes, as well as dig into the configuration history to perform incident analysis. Capability to obtain
details of what a resource’s configuration looked like at any point in the past. Capability to notify every
configuration change so customers can process these notifications programmatically.
5.5.6 Cloud Advisor
36
Analyses Cloud environment and provides best practice recommendations (or checks) in five categories:
cost optimization, security, fault tolerance, performance, and service limits.
Kannur Airport reserves the right to facilitate the cloud hosting services as per the recommended specs
by the Contractor.
5.6. Application Software Development/Customization Methodology
Application Software Customization shall be carried out in following steps in agile methodology:
• Requirement Study
• Design
• Development
• Testing
• Integration
• Release
5.6.1 Requirement Study
The software development team shall carry out the study of the existing systems and shall discuss with
the Kannur Airports IT Division and respective user department to validate the requirements defined in
the Qualitative Requirements. The requirements of the comprehensive system shall be frozen in the form
of Software Requirement Specifications (SRS)/ Preliminary design keeping the time schedule defined in
the Contract.
5.6.2 Design
It is essential for the Kannur Airport to be provided with state-of-the-art IT, networking and equipment
solutions to support operational, administrative and business requirements. The overall concept is to
service all members of the Kannur Airport Community (airlines, governmental agencies, concessionaires,
handlers, passengers and visitors) with the most recent, applicable and sustainable technological solutions.
The existing IT network and infrastructure as shown in Annexure 10, shall be used as the backbone for
the communication. Any additional requirement for the IT infrastructure should be designed to address
Kannur Airport operational needs for the next 10 years.
Key criteria for the IT design shall be:
• Redundancy and minimal convergence time
• Limited congestion
• Appropriate modularity
• Sufficient and scalable bandwidth
• Highest possible availability
• Ease of management
• Energy efficiency
• Future proof design
• Minimal running costs
37
As far as possible Only proven, tested, standard based commercially available systems shall be
implemented. The technology implemented shall promote safety, efficiency, affordability, service
integration, innovation and commercialization.
The software team shall then translate the SRS/ Preliminary design into a design document. Functional
Specifications shall be prepared for the system, as per the quality standards defined in the document.
Database design for the system shall also be undertaken during this phase. This task shall be carried out
in the following steps:
• Preparation of Functional Specifications
• Design of User Interfaces, Portals/ JSPs
• Development of User Interfaces without underlying business logic
• User Interface Design reviews
• Detail Design — Database
• Physical Database Design
• Database Design reviews
The design must address issues such as high availability, scalability of bandwidth, modularity,
manageability, future development potential and low operating and maintenance costs. Applying
international standards where applicable further underpins the flexibility and viability of the design.
Robustness, stability, scalability and ease of maintenance are key considerations. As the operations are
near 24 x 7 x 365, the hardware, tools and backup management shall be correctly planned and provided
(for later operation and maintenance).
The design service life time of all equipment within each IT System shall be at least 10 years in the
prevailing environmental conditions.
5.6.3 Integration
In order to ensure a perfectly operational system, a well-planned and structured systems integration
process shall be used. This is always important in systems development work, but the need is extra
highlighted when it comes to integration of complex, large-scale systems, built-up from many systems
and sub-systems as is the case in an airport environment. Integration is the key to improving safety,
security and efficiency and helps improve data access.
5.6.4 Testing
The testing methodology advocates complete and comprehensive testing of the system to ensure that all
specified features and performance criteria are met. The site acceptance testing should consist of the
following phases.
(a) Conference Room Pilot
(b) Integration testing
(c) Performance testing
(d) Endurance Testing
(e) User Accepting Testing
This is the phase when Acceptance Testing plan based on the Acceptance Testing procedures shall be
taken up in consultation with the IT Division. Development of User Manuals shall also be taken up and
38
get approved by the Kannur Airport.
Acceptance Testing shall be carried out using the finalized Acceptance Testing Plan. The user will devise
the acceptance-testing plan. For acceptance tests a plan including the test cases will be produced by the
Contractor that contains the procedures and responsibilities for delivery acceptance.
5.6.5 Implementation
The system should be implemented without affecting the operation of the Kannur Airport functions
including duty free. The porting and migration of data would be the responsibility of the Contractor.
Necessary temporary arrangements should be made by the Contractor at his cost for smooth changeover
of the existing system to new system without affecting the operation.
5.6.6 Operation & Maintenance Support
Bidder shall adequately plan the O&M on-site support team during the entire period of warranty and
operation & maintenance support, with adequate teams to ensure the SLA conditions as stipulated under
clause 2.23, from 0700 hrs. to 1900 hrs. Monday to Saturday. The Contractor may plan for offsite support
for modules, wherever feasible, subject to the SLA conditions.
5.7. Security
a. Authorized users shall log into the system using a unique user name and password. Depending
on assigned user access privileges, the user shall be either granted or denied access to individual
applications, forms, fields or data.
b. A System Administrator shall be able to add, delete, set, and change user privileges and access
authorization via a GUI built into the general operations of the applications and servers. All
system security parameters shall be configurable by the System Administrator.
c. The system shall have a configurable "inactivity timeout period" such that if any workstation is
determined to be inactive by having no input/output performed at that workstation for the defined
timeout period, that workstation shall be automatically logged out of the system. The timeout
period shall be configurable by the System Administrator. NOTE: This requirement applies only
to interactive users, not to automated interfaces which are expected to be inactive during certain
periods where no data is transmitted.
d. The inactivity timeout described above shall be recorded in the fault log, showing date, time,
workstation identifier, and the user name logged in when the inactivity timeout occurred.
e. The system shall provide an audit trail of all transactions. The audit trail shall track on a per-user
basis. The audit trail file shall indicate any changes that occurred to applications configuration,
data structure, or database fields/records, and shall contain the date and time of the change, the
identification of the user or the subsystem that made the change, and the details of the change.
f. The system shall provide automated tracking of the audit trail database and alert the System
Administrator when the file has exceeded pre-determined size restrictions. The operator shall then
have the ability to archive this database, along with the ability to restore it for reporting purposes.
The system shall also include the option of a “rolling window”. In this case, the audit trail database
shall use a rolling window with a System Administrator configurable window (i.e., after defined
period of time oldest records are automatically dumped).
g. The system shall assign a specific user authorization for each user as per Kannur Airport policies.
The system shall provide the following four access levels as a minimum:
39
h. Read-only: This access level allows only read capabilities for authorized database fields and
screens.
i. Privileged User: This access level allows read capabilities and write capabilities for specific
database fields.
j. System Administrator: This access level allows unlimited read and write capabilities in addition
to system maintenance.
6. Airport Operation Database (AODB), Resources Management System
(RMS)&Master Systems Integration (MSI) Functional requirements
The below listed Functional requirement are just indicative and not exhaustive. The bidder is expected
to conduct a detailed requirement gathering session with Kannur Airport once selected for the project.
# Business Functional
Area Description
1 General
a) The (Airport Operation Database) AODB should act as the central data
repository and foundation for operational applications. It should be resource
planning and operations knowledge base, schedule and flight information
server, and communications hub.
b) It must contain comprehensive, accurate, and consistent information about
schedules, plans, operations, and human and physical resources. Acting as a
knowledge repository, it should contain flexible, user-specified business rules
that control the decision-making logic for the creation of resource-allocation
plans and scenarios, models of future operations, operational schedules, and
real-time responses to irregular operations and other unplanned events.
Acting as an archive of valuable historical data, it maintains an accurate and
secure record of the schedules, plans, and day-of-operation activities it
manages, providing the data needed to produce reports, to generate invoices,
and to perform analyses. Importantly, the AODB stores the information in a
well-engineered relational database model that uses English-language column
and table names and that enables all information to be shared.
c) The AODB should increase collaborative decision-making and overall
organizational effectiveness by ensuring access to all staff members to
identical and accurate schedule, plan, and day-of-operation information,
including all stakeholders covering ATC, landside and airside.
d) The AODB should maintain business intelligence data for the entire
enterprise, whether the enterprise consists of many terminals or airports. For
example, it should support:
i. An airport operator managing a single airport / terminal
ii. An airport operator managing multiple airports / terminals
e) Users throughout the entire enterprise should be able to work collaboratively
and make better decisions, by sharing and accessing valuable information
stored in the AODB.
2 General
a) In a customer hosted environment, the AODB will include a single,
centralized, real-time relational database, running on database system, in
which all data describing the operating policies, procedures, and preferences
of the airport, the planned parking positions, and the real-time operations are
collected and stored. It should provide high availability.
40
# Business Functional
Area Description
b) All data stored in the AODB can be exported to a reporting database for ad-
hoc queries or reports using SQL or other reporting tools.
c) All table names and table column names in the AODB will be in the English
language to simplify information retrieval and report generation.
d) Except for passwords, all data stored in the AODB will be stored unencrypted
to allow access to that data by third-party reporting tools and to simplify
building interfaces to external systems.
e) The AODB will store all operational data in historical data archives for a
minimum of one year.
f) The AODB will store information in the database automatically as soon as
the user enters it.
g) The AODB will be able to be configured to be fault tolerant, thus surviving a
server failure.
h) Except for backups, no information or data will be kept or stored outside of
the Oracle database.
i) It should be possible to store multiple versions of the business rules and
airport configurations in a single database.
j) The user should be able to store information in the AODB that allows the
applications to select a given airport configuration on a specific day
automatically.
k) It should be possible to indicate dynamically that a new airport configuration
(used for analysis, for example) is identical to another airport configuration
except for specific changes that the new configuration contains. Changes
made to the original airport configuration will flow automatically to the new
airport configuration regardless of when they are made if the user elects to
configure the system that way.
l) It should be possible to copy an entire airport configuration and no longer
have it linked to the original configuration.
m) It should be possible to export an entire airport configuration and load it
elsewhere.
n) It should be possible to export a schedule from one AODB and load it in
another AODB.
o) Intuitive User experience and User Interface (CX & UI), the application user
interface shall be user friendly featuring the following:
i. Displays the standard GUI techniques such as Scroll bars, variety of
fonts, colors, different selection options, text boxes.
ii. The GUI shall be user-friendly. The Contractor shall describe
precisely the look and feel of the GUI.
iii. All GUI shall be web-based.
iv. The AODB System Administrator or Supervisor to be able to
configure GUI’s to meet a group or individual user need.
p) Where reference data contains both ICAO and IATA codes, the use of IATA
codes only for primary keys shall not be permitted.
q) Where there are relationships between ICAO and IATA data, and conversion
tables shall support-one-to many and many-to-one relationships without loss
41
# Business Functional
Area Description
of data integrity (e.g. ICAO B742 may refer to IATA 74F, 747 or 74C).
r) Any descriptions or free text elements should support English and Malayalam
text.
s) Terminal topology: such as Check in desks, Gates, Bus Gates, Carousels,
Boarding lounge, Aircraft contact & remote stands, Boarding bridges,
Terminal and Baggage belts to be stored using the names/codes defined for
the physical locations.
t) Messages help files and some references will need to be stored in English,
Hindi and Malayalam for display purposes.
u) Alerts are to be raised as soon as interfaces go offline. Alerts can be
propagated to SMS/Email/Mobile tool
3
Basic Airport Data
System shall support all the basic airport data, including the following list:
a) Airports
i. IATA Code.
ii. ICAO Code.
iii. Name.
iv. Airport name.
v. Country (ICAO Code).
vi. Customs Type.
vii. Time zone.
b) Airlines
i. ICAO Code.
ii. Name.
iii. IATA Code.
iv. Country (ICAO Code).
v. Commercial information:
i. Reservation phone numbers.
ii. Website.
iii. Operational phone numbers in (e.g. baggage claim, ops, or
VIP lounge).
iv. Accepted modes of payment.
v. Check-in policies.
c) Aircraft Type
The reference data includes the aircraft resources. This covers the types of
aircraft, as well as all details required for each individual airframe. This data is
important both for safety, choosing suitable parking stands, but also used for
planning and is used when collecting data for invoicing and statistics. Minimum
data elements are:
i. Name.
ii. ICAO Code
iii. IATA Code.
iv. Engine type (e.g. jet, turboprop, piston).
v. Configuration (Cargo, passengers mixed).
vi. Size using ICAO dimension groups(A-G).
vii. Physical dimensions as overall length and overall wing span in meters
42
# Business Functional
Area Description
viii. Maximum take–off weight.
ix. Maximum number of passengers.
x. Average speed.
xi. Acoustic category.
xii. Hold size.
d) Aircraft
i. Registration number (allowing formats for military and private aircraft).
ii. Aircraft type stored as ICAO and IATA.
iii. Owner airline.
iv. Operating airline.
v. Maximum take –off weight.
vi. Size using ICAO dimension groups (A-G).
vii. Physical dimensions as overall length and overall wingspan in meters
viii. Comment.
e) Terminal topology
i. Check-in desks:
i. Name.
ii. Terminal.
iii. Zone
iv. Customs Type.
v. Oversize bag (y/n)
ii. Gates:
i. Name.
ii. Terminal.
iii. Customs Type.
iv. Arrival/departure.
v. Bus access.
iii. Baggage Carousels:
i. Name.
ii. Terminal.
iii. Customs Types
iv. Passenger capacity.
iv. Boarding lounges:
i. Name.
ii. Terminal.
iii. Customs Type
iv. Passenger capacity.
v. Aircraft stands:
i. Name.
ii. Name apron / bay
iii. Type: contact or remote.
iv. Nature: e.g. commercial, freight maintenance, hangar.
v. Services: e.g. water, pca, 400 Hz.
vi. Dimensions maximum allowable ICAO group (A-G).
vii. Physical dimensions as maximum length and maximum
43
# Business Functional
Area Description
wingspan in meters
viii. Associated Boarding Lounges if appropriate
vi. Passenger Boarding Bridges:
i. Name.
ii. Terminal
iii. Dimensions.
iv. Associated Aircraft Stands
4 User’s features
Users should be able to:
a) Enter flight schedules, resource, planning, and operations data in one
application and share it with all other applications on real time basis
b) Access a comprehensive, integrated, up-to-the-minute view of airport
scheduling, planning, and operations information throughout the enterprise
c) Exchange information stored in the AODB with external systems
d) Maintain an accurate and consistent business-intelligence data repository and
historical data archive
e) Build multiple scenarios of the business rules for planning purposes and to
accommodate changes over time.
f) Support operational critical systems such as:
i. Airport Collaborative Decision-Making System (ACDM),
ii. Airport Operational Control Center (AOCC)
iii. Airport Community App
iv. Passenger App
v. Other concessionaire application
vi. Other initiatives like DigiYatra
vii. Airport’s information platform such as Data lake
5 Schedule
Management
a) The schedule management module should create, manage, and communicate
the seasonal flight schedule and day-of-operation flight-status information
that drives almost all airport decisions. The schedule manager should provide
user interface panels to maintain data, such as:
i. Handling seasonal flight schedules, that is, the schedule information,
in IATA SSIM Chapter 7 format, that is related to sets of flights that
operate between specific start and end dates
ii. Handling operational flight information, that is, information related
to a specific flight on a specific date
iii. Controlling the generation of flight legs automatically by unrolling
seasonal flight schedules to create individual flight records.
b) There should not be any limit to the number of schedules that can be
managed. Future schedules created by the schedule manager should be
ableto be analyzed in real time to forecast capacity. The schedule
management module should provide consistent schedule and real-time flight
information to all AODB connected applications manually or with automated
airline data feeds.
c) The schedule management module should enable the user to:
i. Create, view, update, edit, and analyze seasonal flight schedule and
operational flight data using manual data entry
44
# Business Functional
Area Description
ii. Load IATA SSIM (Chapter 7) schedules into the AODB and
automatically infer and link data connecting arrivals with departures
iii. Ensure the consistency of flight schedule and flight data, preventing
errors that could become costly mistakes
iv. Disseminate consistent up-to-date flight-schedule and flight-status
information throughout the enterprise
v. Increase collaborative decision-making and overall organizational
effectiveness by ensuring all staff members have access to identical,
accurate flight schedule and day-of-operation flight information.
d) Planners should be able to use the schedule manager to manage current and
future airport-specific flight schedules, to print reports and to search for new
airline service offerings. The schedule manager should automatically roll out
the flights for the next few days from the seasonal schedule and makes the
data available to the day-of-operation decision-support products and to flight
information display systems. If turn data were not available when the
schedule file was loaded, the schedule manager should have the ability to link
day-of-operation arrivals with departures based on an intelligent turn-
forecasting module.
e) Users in the operational control center must have the ability to manually enter
flight-related data that is not received in real time.
f) There should be no limit to the number of schedule manager users. They may
all view flight status and, if authorized, update flight information. There
should be airline filters so that users may see only their authorized flights.
The schedule management module can be used to pass updated estimated
times of arrival to FIDS.
g) There should be limits on what users may view and update. Users should be
allowed to view and modify information for only the flights for which they
are responsible. When an airport supplies the schedule management module
to an airline, the airline users should be allowed to view and modify
information only for the airline’s flights.
6 Gate Management
System
a) The gate-management system should provide a flexible, easy-to-manage,
automated tool to support long-term planning, short-term planning, and real-
time allocation of aircraft parking positions.
b) The gate-management system should be a commercial off-the-shelf product
that can be configured by airport staff to reflect the specific needs of the
airport.
c) The gate-management system should operate seamlessly with an integrated
central airport database that can receive flight information from multiple
airlines, national air control centers, and data providers, such as Flight Stats,
and that can provide information to external systems such as FIDS, billing
systems, and accounting systems. Changes made to information processed in
the gate-management system will update the database in real time; changes
will not be updated by means of a batch update process based on a timer or a
manually-invoked save command.
d) The gate-management system should work seamlessly with other airport
45
# Business Functional
Area Description
automated resource-planning and resource-allocation systems, such as a gate-
planning system, a capacity-analysis system, a check-in-counter allocation
system, a baggage-belt allocation system, a landing-slot allocation system,
and a workforce-management system, as well as with accounting, human
resources, and time and attendance systems. All systems will operate with the
same central database; no system will operate with a separate database.
e) The gate-management system should be flexible so that it can support future
expansion of the airport and changes in the number, location, and physical
configuration of parking positions under management, as the airport’s needs
change. The system will not be limited in the capacity of the number of
parking-position resources it can handle.
f) The gate-management system should be able to support a distributed
architecture, where the central airport database is operated in a central
location and is connected via a network to other locations at the airport where
only the planning functionality operates or only the real-time allocation
functionality operates.
g) The gate-management system should support the activities of multiple
simultaneous users, who may manage the same gates, synchronized in real
time.
h) The gate-management system should support applications that provide
viewing and editing of flight information through an application that can be
accessed from a URL in a web browser.
i) The gate-management system should support a real-time bar chart display
that provides flight times, such as ON, IN, OFF, OUT, scheduled IN, and
scheduled OUT, in graphical form so the user does not have to enter or select
the flight to view the information.
j) The gate-management system should be able to support distributed
operations, where a central workstation at the primary airport controls the
planning and real-time allocation of parking positions at secondary airports.
k) The gate-management system should operate on a non-proprietary
architecture that will support the development of interfaces with other
systems installed at the airport.
l) The gate-management system should operate on personal computers running
the latest versions Microsoft Windows as an operating system.
m) The display of the bar chart should be made available to multiple users from
a URL in a web browser. The chart will not require manual refresh and will
not redraw an entire page when a flight status has changed. HTTP refresh is
not acceptable.
n) The bar chart display should support the definition of user profiles, such as
preferred graphical settings and the gate (stands) a user view.
o) The bar chart display should provide a history window that shows all recent
changes.
p) The gate-management system should support as many as three screens from
a single workstation to display gates and times.
q) The gate-management system vendor will provide remote web-based user-
46
# Business Functional
Area Description
support services and remote software error monitoring and repair 24
hours/day, 7 days/week, and 365 days/year.
7
Gate Management
System (Resources
to be managed)
a) The gate-management system will be able to manage these resources when
developing plans for future allocations and when operating in real time:
i. Gates
ii. Stands
iii. Remote stands
iv. Bus lounges
v. Stand hierarchies (A=B+C) and (B=D+E)
vi. Flexible parking locations based on dynamic passenger flow using
doors and moveable barriers
vii. Maintenance positions
viii. Cargo positions.
b) The gate-management system will enable the user to specify the following
information for each resource under management:
i. Inoperative due to scheduled preventive maintenance for a specific
period
ii. Inoperative due to recurring scheduled preventive maintenance for a
specific period
iii. Inoperative due to unscheduled maintenance during a specific period
iv. Reduction in the level of service due to unscheduled maintenance
during a specific period
v. Reduction in the use of a resource due to security considerations
vi. Physical limitations due to overlapping parking positions
vii. Physical limitations due to unusual and/or complicated traffic and
parking patterns.
c) The gate-management system will not limit the quantity of parking position
resources that can be managed.
d) The gate-management system will automatically select the proper airport
configuration and business rules for any given operational day and will
automatically handle airport changes that may occur at specific dates.
e) The gate-management system will store multiple time-varying configurations
of the airport in the database.
8
Gate Management
System (Flight
handling in planning
and in real-time
operations)
a) The gate-management system will be able to handle the flight movements
when developing plans for future allocations and when operating in real time,
with situational awareness of all the required resources and their status.
b) The gate-management system will link flight arrivals and departures and
identify turns automatically using aircraft registration information. When
aircraft registration data is not available, an intelligent linking process will
link arrivals with the most likely departures and publish the updated
information on real time basis to all the subscribers of the information.
c) The gate-management system will be able to handle the following flight types
when developing plans for future allocations and in real-time operations:
i. Charter
ii. Cargo
47
# Business Functional
Area Description
iii. Mixed use
iv. Trainer.
d) The gate-management system will support the IATA code suffix.
e) The gate-management system will enable the user to add textual remarks to
flights and aircraft.
f) The gate-management system will enable multiple users to access the system
simultaneously, ensuring that data entered by one user is displayed
automatically and in near real time to all other users.
g) The gate-management system will support irregular operations such as
cancellations, diversions, and multiple returns of the same flight without
losing flight history.
h) The gate management system will support the airline’s flight date concept,
thus providing unique identification of the flights on the screen even if a
flight is delayed more than 12 hours.
9
Gate Management
System (Business
Rules)
a) The gate-management system should make its recommendations based on
business rules, which can be customized to reflect the unique operating
conditions at the airport, and which can vary with time.
b) The gate-management system should operate with the same business rules
when performing long-term planning and when operating in real time.
c) The gate-management system should enable the user to adjust rule
parameters without any programming.
d) The gate-management system should contain hard rules, which must be
obeyed, and soft rules, which should, but will not always, be obeyed.
e) The gate-management system must support rules that indicate if an airline has
priority for a gate or parking position.
f) The gate-management system must support rules that cluster the flights of
one airline together or the flights handled by one handling agent together.
g) The gate-management system must provide automatic email notification to
system managers when changes are made to the business rules.
h) The gate-management system must generate the parking-position scheme
automatically, based on schedule information and the business-rule
mechanism, without reliance on manual adjustment.
i) The gate-management system should operate 24 hours/day and 7 days/week.
It will not require restart or exit at specific times. It will handle aircraft that
arrive one day and depart the next without breaking any links. It will keep
track of aircraft that stay at the airport for multiple days and reflect the
position of such aircraft accurately on the bar chart.
j) The gate-management system must be able to provide complete aircraft
movement history from arrival to departure regardless of the number of tows
or the amount of time spent on the ground
48
# Business Functional
Area Description
10
Gate Management
System (Planning
parking-position
schedules)
a) The gate-management system should support long-term planning of parking-
position schedules. It should assign parking positions automatically based on
pre-defined and stored business rules when seasonal schedules, including
exceptions, are loaded. Planning should take into account each day in the
schedule period, rather than a single typical day during the schedule period.
b) In cases where the airport configuration changes during the schedule period,
the planning system should take all different airport configurations into
account when generating the plan.
c) The planning system should operate independently from the system that
performs real-time allocation.
d) The planning system should enable the user to analyze the following what-if
scenarios:
e) The consequence of accommodating new airlines
f) The consequence of introducing changes in flight schedules
g) The consequences of the closure of parking positions.
h) The system should provide an interactive planning tool to enable the user to
create multiple airport scenarios, for example, to allow for planned expansion
or changes in business rules, and to analyze and compare a variety of what-if
scenarios. The planning tool should enable the user to modify an existing
scenario by changing business rules while ensuring synchronization with the
master planning scenario.
i) The planning system should operate with a seasonal flight schedule that
contains the following information:
i. Days of operation in standard OAG format
ii. Arrival time and departure time in local time
iii. Aircraft type
iv. Airline code in the form of a prefix
v. IATA suffix for each flight
vi. International flight identification
vii. Domestic flight identification.
j) The planning system should use the following information about parking
positions when preparing schedules. The information should be in the form of
a hard rule, or one that must not be violated.
i. Size constraints related to aircraft types allowed at each parking
position
ii. Size constraints related to aircraft types allowed at adjacent parking
positions
iii. Time-dependent constraints related to aircraft types allowed at
adjacent parking positions
iv. Security constraints related to aircraft allowed at adjacent parking
positions
v. Constraints related to international vs. domestic flights allowed at
adjacent parking positions
49
# Business Functional
Area Description
vi. Constraints related to buffer time between two aircraft at the same
parking position
vii. Distance of parking position from main terminal area
viii. Constraints related to service level or repair condition of parking
position
ix. Constraints related to customs and immigration areas
x. Constraints related to parking positions reserved for special use, such
as VIP and mixed flight
xi. Constraints related to transborder or international in-transit areas.
k) The planning system should use the following information about parking
positions when preparing schedules. The information should be in the form of
a soft rule, or a preference which may be violated if there are no other
solutions.
i. Marketing constraints
ii. Proximity between high-connection flights
iii. Minimize resource under-utilization
iv. Preferred airline stands
v. Minimum time on gate or hard stand for handling, by aircraft type
vi. Maximum times on gate or hard stand before towing, by aircraft type.
11
Gate Management
System (Operating
in real time)
a) The real-time gate-management system should support day-of-operation
planning and real-time allocation of parking positions. It should
automatically assign parking positions based on the pre-planned schedule and
on pre-defined and stored business rules.
b) The real-time gate-management system should operate with the following
flight information:
i. Days of Operation, in standard OAG format
ii. Departure Time
iii. Aircraft type
iv. Airline code in form of 2- or 3-character prefix
v. IATA suffix for each flight
vi. Ramp handling agent identification
vii. Arrival flight number
viii. Departure flight number
ix. Aircraft registration number
x. Estimated time of arrival
xi. Estimated time of departure
xii. Tow on time
xiii. Tow off time
xiv. Passenger load on arriving flight
xv. Passenger load on departing flight
xvi. Assigned parking position for arriving flight
xvii. Assigned parking position for departing flight
xviii. Assigned holding room for departing flight
xix. Flight sector indicator (Transborder pre-cleared, Transborder post-
cleared, International, Domestic)
xx. Flight type indicator (Charter, Scheduled Flight, Military, Cargo)
50
# Business Functional
Area Description
xxi. Remarks.
c) The real time gate-management system should use the following information
about parking positions when operating in real time. The information should
be in the form of a hard rule, or one that must not be violated.
i. Size constraints related to aircraft types allowed at each parking
position
ii. Size constraints related to aircraft types allowed at adjacent parking
positions
iii. Time-dependent constraints related to aircraft types allowed at
adjacent parking positions
iv. Security constraints related to aircraft allowed at adjacent parking
positions
v. Constraints related to international vs. domestic flights allowed at
adjacent parking positions
vi. Constraints related to buffer time between two aircraft at the same
parking position
vii. Distance of parking position from main terminal area
viii. Constraints related to service level or repair condition of parking
position
ix. Constraints related to customs and immigration areas
x. Constraints related to parking positions reserved for special use, such
as VIP and mixed flight
xi. Constraints related to trans-border or international in-transit areas.
d) The gate-management system should display operations in a window without
a hard start- and end-of-day boundary. It should be possible to consider that
the typical operational day does not go from midnight to midnight.
e) The gate-management system should automatically size the information
displayed in the bar chart window to ensure that information is displayed
consistently and that flight numbers are never cut off at the edge of the chart.
f) The gate-management system should allow the user to reassign parking
positions and to override recommendations made by the system.
g) The gate-management system should provide automatic visual alerts when
assignments violate rules and other scheduling conflicts occur.
h) The gate-management system should provide a conflict table where all
recognized conflicts are specified.
i) The gate-management system should provide different options for conflict
resolution.
j) The gate-management system should provide a multi-stage process for
conflict resolution, where several flights may be moved to other parking
positions.
k) The gate-management system should introduce and track all aircraft tows.
l) The gate-management system should display details about conflicts.
m) The gate-management system should handle the return of a flight as well as
multiple returns of a flight to the airport.
n) The gate-management system should link flights automatically in real-time
51
# Business Functional
Area Description
when registration changes and should plan tows automatically.
o) The gate-management system should generate turns automatically for
unlinked schedules.
p) The gate-management system should provide an audit log that stores the
details of actions that change data, including the user ID of the person
making the entry and a time stamp. The system should support central
logging from all workstations to a single server.
12
Gate Management
System (Check-in
counter
management)
a) The gate-management system should operate seamlessly with a check-in
counter management system that plans allocations in advance and manages
check-in counter allocations on the day of operation in response to flight
schedule changes The check-in counter management system should
determine the number of check-in counters needed to handle passengers
based on flight schedules, aircraft sizes, passenger load, type of flight, class
of service, and passenger-arrival patterns.
b) The check-in counter management system should be capable of assigning
contiguous check-in counters that vary in number over time as handling
needs change.
c) The check-in counter management system should handle code shares and
alliances.
d) The check-in counter management system should update check-in counter
displays automatically.
e) The check-in counter management system should generate reports of counter
use for billing.
13
Gate Management
System (Baggage-
belt management)
a) The gate-management system should operate seamlessly with a baggage
make-up and reclaim belt management system that plans belt allocations in
advance and manages belt allocations on the day of operation in response to
flight schedule changes and other unanticipated events.
b) The baggage-belt management system should determine belt allocations
automatically based on flight schedule, aircraft size, passenger load,
passenger count, type of flight, and class of service.
c) The baggage-belt management system should handle code shares and
alliances.
d) The baggage-belt management system shouldbe able to balance allocations
based on the expected and actual numbers of passengers on flights.
e) The baggage-belt management system should update baggage belt displays
automatically.
14 Gate Management
System (Reports)
a) The gate-management system should produce reports about its schedule
planning and real-time operations.
b) The gate-management system should print bar charts for user-defined time
ranges.
c) The gate-management system should enable users to generate some reports
by accessing a web page. The web reports should be generated in PDF form
from a central report server.
d) Data may be exported through ETL to customer hosted reporting systems.
52
# Business Functional
Area Description
15
Gate Management
System (User
Documentation)
a) The gate-management system should include comprehensive documentation
that describes how to use the system. The documentation should be online, in
a form that users can access and print.
b) The user documentation should contain a detailed index that lists key words
alphabetically with appropriate page references.
c) The user documentation should describe the layout and use of the data-entry
and data-display fields of the user interface screens.
d) The user documentation should describe how to use each of the commands
contained in the gate-management system.
e) The user reference documentation should describe what the user should do to
obtain customer support.
16
Gate Management
System (User and
System administrator
training)
a) The vendor of the gate-management system should provide hands-on training
courses for users and system administrators.
b) The vendor of the gate-management system should provide on-site
operational training to users during the first seven days in which the gate-
management system is in operation at the airport.
c) The vendor of the gate-management system should provide refresher training
courses to users and system administrators as needed.
d) It should be possible for a system administrator to create, edit, and add
system users and new type of resources without contractors involment, thus
controlling access to the web-based components of the system.
17
Gate Management
System
(Maintenance &User
Support)
a) The vendor of the gate-management system should provide remote software
maintenance and technical user support services 24 hours/day, 7 days/week
on an annual contract basis.
b) The vendor of the gate-management system should provide a web-based help
desk that will enable the user to report problems and track the resolution of
problems.
c) The gate-management system should generate complete logs of all user-
initiated commands for each session.
d) The gate-management system should generate a history in the database of all
changes made to key flight information such as gate assignments, changes in
flight status and times.
18 Mobile
Compatibility
a) The mobile tool should be able to show an airport map with the current status
of resources, arrival and departure schedule with the latest status as well as
being able to show turnaround timelines for each flight.
b) Mobile tool should comply with the concept of "Mobile Airport Control
Centre" and being configurable to use by different airport stakeholders.
c) Search features should be available to support users to retrieve information
quickly and effectively. User features like sorting, partial search, filtering of
information, etc. that improve user interface would be preferred.
53
# Business Functional
Area Description
19 Operations
Planning
a) System shall allow Airport to schedule blockage for maintenance or
renovation of various air side resources (Taxiway, Gates, Apron, etc.) and
accordingly have intelligence to reflect on impacted resources (e.g. Gates,
GSE Area, Route access, etc.)
b) System shall have the capability to present scenario-based analysis as per
chosen KPI of importance, to present options and accordingly decide on most
optimum SOP incorporation in case of any disruptions.
20
Computational
Environment
(AODB&RMS)
a) The gate-management system should operate on commercially-available
industry-standard hardware, such as Intel or AMD-based PCs running
Windows 7 or newer versions, or as an alternative a vendor provided hosted
offering through a service such as Amazon Web Services.
b) The web-enabled viewer should operate off an industry-standard web server,
such as Apache, and support hundreds of users simultaneously.
c) The gate-management system should provide a secure, configurable, open-
standards-based architecture for data exchange between the gate-management
system and external systems such as flight-display systems, finance systems,
and human resources systems. It should support both a table-to-table
interface to transfer information from the gate-management system central
database to another system that contains a SQL-compliant database and a
web-enabled messaging interface that requires no database access to the gate-
management system central database.
d) The server should be configured as a cluster to allow no more than five
minutes of database downtime should one of the servers in the cluster fail. No
data should be lost in the transfer (except, possibly, the last transaction)
during the switchover.
e) The server cluster should be Intel or AMD processor units running either
Microsoft Server or Linux.
f) The server cluster should include a RAID-5 disk unit accessible by both
servers in the cluster.
54
# Business Functional
Area Description
21
Detailed list of
interfaces
55
7. Airport Operational Database (AODB), Resource Management System
(RMS) and Master Systems Integration (MSI) Non-functional
requirements
# Item Requirement
1 Application and access control Requirements The system should provide a single sign-on solution
across all modules
2 Application and access control Requirements The system should ensure no session data persists
when a session is closed.
3 Application and access control Requirements
The system should assign the ability to set
prescribed and configurable session time-out limits.
5 Application and access control Requirements
The system should display an advisory warning
message to the user before initiating the system
logon procedure regarding unauthorized use of the
system and the possible consequences of failure to
heed this warning
7 Application and access control Requirements
The system should provide an access control and
authentication solution that is to be capable of
enforcing a specified password policy
8 Application and access control Requirements
The system should facilitate the copy of the user
roles defined in the production/pre-production
environment to be used across multiple
environments as follows:
- The ability to define and maintain roles in multiple
environments (e.g. development, training, UAT,
production/pre-production);
- The ability to change roles and access rights in one
environment without impacting on the other
environments;
- The ability to modify the underlying user directory
in one environment without impacting on the other
environments; and
- The ability to export and import (or copy) a user's
access profile attributes within the same system and
between systems environments.
9 Application and access control Requirements The system should track changes to user access and
logs them in an audit trail
10 Application and access control Requirements
The system should ensure authentication data is
encrypted such that it is not susceptible to
interception
11 Application and access control Requirements System access should be role and permission based.
56
# Item Requirement
12 Application and access control Requirements The system logs users out after a specified period of
inactivity.
13 Application Audit Requirements
The system should capture audit trail records in a
form that facilitates ease of use, analysis and
reporting. Data includes:
- identification of the user;
- event description;
- event source (e.g. application module name);
- the actions performed by the user;
- the data involved (tracking prior and subsequent to
a change being made);
- success or failure of the event;
- the date and time of the interaction; and
- a session or transaction identifier.
14 Application Audit Requirements The system should provide the ability to track all
log-ins and log-in failures.
15 Application Audit Requirements
The system should provide transaction logs to
record executed functions to facilitate diagnosis and
reconciliation of system errors
16 Architecture standards
The system should provide the ability to make
changes to the Relational Database Structure and
business rules without requiring a change to the
source code
17 Architecture standards
• The system should be able to deploy
changes in a modular format.
Architecture permits modular release of
functionality.
• Specify Artificial Intelligence (BI)
extensibility supported by the proposed
application
• Specify the Business Intelligence (BI)
capability
• The environments (Production, Test, Dev
and UAT) should have capability to deploy
on cloud as well.
18 Architecture standards
The standard architecture offers the ability to
change Solution functionality and data structures in
an efficient and effective way without
compromising the Solution architecture and whilst
maintaining data integrity. Data is to be stored and
managed in a manner that allows efficient and
effective recovery from data loss, corruption,
disaster or any other event that renders it
unavailable or unusable.
19 Architecture standards Specify Artificial Intelligence (BI) extensibility
supported by the proposed application
20 Architecture standards Specify the Business Intelligence (BI) capability
57
# Item Requirement
21 Architecture standards The environments (Production, Test, Dev and UAT)
should have capability to deploy on cloud as well.
22 Availability Requirements
The system should follow a standard in terms of
how failover and redundancy of core systems is
handled within Kannur Airport
23 Availability Requirements
The system should effectively facilitate the seamless
failover of production access between the primary
and secondary site
24 Availability Requirements
The system should provide for a configuration that
optimally employs two physically separate sites; a
primary site and a secondary site
25 Availability Requirements The system should support remote access for
service/maintenance monitoring
26 Backup and restore Requirements
The system should facilitate recovery testing and
incident simulation to the non-production
environment
27 Backup and restore Requirements
The system should facilitate configurable backup
processes to be set up and tested without impacting
production, availability or performance
28 Backup and restore Requirements
The system should facilitate the following backups:
- multi level backups
- adhoc whole system to transaction backup of
group of transactions.
29 Backup and restore Requirements System to allow patches / Upgrades for the system
to be made available through vendor portal.
30 Backup and restore Requirements The system should perform full, differential and/ or
incremental Disk2Disk backup retention daily
31 Data storage Requirements
The system should be capable of generating and
storing sanitized copies of the production data for
use in the UAT and development environments
whilst maintaining controls that ensure the process
of creating the copies does not interfere, corrupt or
modify the production data
32 Data storage Requirements
The system should provide a database management
system that is query-able using industry standard
languages such as SQL and XMLA
33 Data storage Requirements System to provide functionality to allow database to
be compressed.
58
# Item Requirement
34 Fault Management Requirements
The system should support the automatic detection
and logging of all application failures, with
supporting diagnostic information transmitted.
35 Fault Management Requirements
The system should support automated application
failure recovery and data rebuild from central to
distributed environment.
36 Fault Management Requirements
The system should produce transaction-based error
and trace logs. The error logs are in a clear and
concise format, and in a form that facilitates the
easy removal of sensitive aspects of data.
37 Fault Management Requirements
The system is capable of producing notification of
various levels of error based on a defined
notification list.
38 General Data Management Requirements
The system should maintain the integrity of the data
irrespective of any changes to solution functionality
or data structures.
39 General Requirements
System should provide the ability to provide an
open architecture for user and system interfaces
based on current and industry-accepted standards,
methods, and protocols such as HTTP, XML,
SOAP, FTP, etc.
40 General Requirements
The system should provide the ability to integrate
with standard Microsoft Office products, including
MS Word, MS Excel, MS Access and MS Outlook.
41 Generic Interface Requirements
System to ensure that secure integration policies are
adhered to when integration occurs between internal
and/or external systems and the AODB & RMS
solution
AODB system should be able to interface with ERP
& Enterprise Integration and messaging systems.
System should have the ability to integrate using
API / Webservices with out of the box features.
42 Internal Interface Requirements
The system should facilitate data transfers to and
from the system via the Kannur Airport network to
take place via SFTP or SSH File Transfer Protocol
for file access, file transfer, and file management
functionality over any reliable data stream
59
# Item Requirement
43 Network and data security Requirements The system should ensure that encryption does not
prohibit the Solution performance requirements
44 Network and data security Requirements
The system should have the ability to check on web-
based access in order to verify user session and
authentication status, (e.g. session state session ID)
or some type of verification of user connections into
and within the application
45 Network and data security Requirements
The system should address all known security
vulnerabilities arising from the application level
protocols used by the Solution and ensure that they
are effectively mitigated
46 Network and data security Requirements
The system should protect database files from
access that bypasses the database's normal access
controls.
47 Network and data security Requirements
The system must ensure that it employs strong
methods for data communication security (i.e.
TLS/SSL and Share File Staging through secured
environments)
48 Report Requirements (non-functional)
The system should be able schedule management
reports (as opposed to transactional artefacts /
reports – i.e. an invoice, statement) to be run based
on current resource availabilities. If two reports are
currently being requested, they should be scheduled
to run one after the other to ensure resource
optimization.
49 Report Requirements (non-functional)
System to provide the ability to generate data sets
using appropriate open standards (i.e. text, excel,
CSV, MS-Word, XML etc.) with adequate security.
50 Solution Capacity Requirements The system will support at least expected business
volumes of Kannur Airport
51 Solution Capacity Requirements The system should be able to flexibly accommodate
multiple database updates per second.
52 Solution Capacity Requirements
The combined application and Infrastructure
architecture and configuration can flexibly
accommodate up to 1000 user generated database
updates per second.
53 Structured Data Management Requirements
The system should provide for a customizable data
dictionary that defines the names and definitions of
business data elements.
60
# Item Requirement
54 Structured Data Management Requirements
The system will maintain the integrity of data
regardless of the number of users concurrently
updating the database.
55 Structured Data Management Requirements
Subject to necessary Infrastructure, the system is to
be able to recover from transaction failures with the
data remaining in a consistent state and no loss of
committed data.
56 Structured Data Management Requirements
The system should have the ability to prevent
update or deletion of certain records based on
business rules or status flags.
57 System Management Requirements
The system event logs can be maintained such that:
- they are protected from modification and
unauthorized access;
- they can be archived and retained for future
access; and
- they are protected from whole or partial loss
within the defined retention period.
58 System Management Requirements
The system should have the ability to manage and
control the overall runtime environment. At a
minimum, this should include:
- the ability to start and stop individual components;
and
- the ability to schedule starting and stopping of
individual components.
59 System Management Requirements
The system should allow a system administrator to
monitor and control system usage (e.g... the system
administrator is to be able to disable a user session
that is overloading the system).
60 System Performance Requirements
The system should be configured in such that when
running complex reports, control of processing is
returned to the user and processing is completed in
the background, as well as providing an estimated
completion time, and visible indication of progress.
61 System Performance Requirements The menu navigation should take less than 1 second
to complete
62 System Performance Requirements The screen-opening should take less than 3 seconds
to complete
63 System Performance Requirements The field navigation should take less than 1 second
to complete
64 System Performance Requirements The transaction commit should take less than 10
seconds to complete
65 System Performance Requirements Query retrieval should take less than 3 seconds to
complete
61
# Item Requirement
66 System Performance Requirements Online report generation should take between 5 and
60 seconds to complete
67 System Performance Requirements Reports that are run in the background should not
take more than 20 minutes.
68 System Performance Requirements
The system should not exceed:
- 75% of CPU capacity
- 75% of RAM utilization
- 75% of database capacity
69 Unstructured Data Management
Requirements
The system should have the ability to store
unstructured data (e.g... MS Office and PDF
documents) and link them to relational database
records.
70 Unstructured Data Management
Requirements
The system should have the ability to archive and
restore unstructured data.
71 Usability Requirements
— The system exhibits the controls to ensure all
graphical user interfaces have a consistent look
and feel, menu layout, functional behavior and
navigation styles.
— Navigation crumb trails should show users
where they are within the application.
— The various locations in the path should be
clickable, allowing users to navigate to any
location in the path.
72 Usability Requirements The UI should adapt to differing screen sizes, e.g.
phone / tablet screens etc.
73 Usability Requirements
The system should facilitate the ability to perform
keyword and text searches across on-line end-user
documentation.
74 Usability Requirements Users can enter and submit a simple search query,
easily accessible from any screens.
75 Usability Requirements
The system should provide user help menu’s and
on-screen context sensitive help, wherever possible
i.e.
When users click the help menu item or press the
“F1” key while within a view, the help facility
opens and displays help for that specific view.
The help menu should contain a glossary of terms.
76 Usability Requirements
The system should provide standard keyboard
alternatives for all actions that can be performed by
any point and mouse-click action
77 Usability Requirements
The system should provide hover help tooltips with
the configurable option to switch them on/off edit:
When users place the cursor over a user interface
object such as field or button, a tooltip appears
explaining the purpose of that object and offers brief
help in how to use it
62
# Item Requirement
78 Usability Requirements The system should progressively save data in a
temporary location until the data set is committed
79 Usability Requirements
The UI that is used should be flexible enough to
facilitate the display, navigation and update of very
large grid like data sets, including the ability to
‘freeze panes’ so that headings and data groupings
remain visible when moving around the screen
80 Usability Requirements
The system should provide a real time alert
mechanism on erroneous input and/or calculations.
Warning / error messages must be in plain English
and not technical in nature.
81 Usability Requirements
The system should provide defined field formatting
/ mandatory fields to ensure that users make fewer
mistakes when capturing information.
82 Usability Requirements
The system should provide on screen feedback
proposed by the vendor during waiting periods. The
system should make use of a progress bars with a
percentage and or time metric to indicate the
progress on a transaction.
83 Usability Requirements
System to allow scalability in terms of languages
offered on the UI, allowing additional languages to
be added in the future as and when the requirement
arises.
84 Usability Requirements
The solution (wherever capability exists without
modification of the source code) should support
HTML format.
85 Usability Requirements
System to perform validation on data that is entered
into the system at field and form level. This should
ensure that at a minimum all mandatory fields
within system are entered by user in the correct
format.
86 Usability Requirements
System to limit free text entry where possible to
limit potential data errors. Preference should be
given to selectable fields.
87 Usability Requirements
System to provide functionality that allows data
fields to be pre-populated from the existing
information within the form or within the workflow.
88 User Interface Requirements
The system should at least support the following
browsers:
- Internet Explorer v9
- Google Chrome v35
- Firefox v30
63
# Item Requirement
89 User Interface Requirements
The system should employ a file export/upload
capability that can be accessed via the user’s
interfaces identified in the requirements described
above
90 User Interface Requirements
All error messages generated by the Solution and
presented to an end-user should be meaningful,
actionable and in 'plain English'
91 Infrastructure Requirements
Specify the typical / preferred server environments
design i.e. Production, Development, Test
environments etc.
92 Infrastructure Requirements Specify the typical middleware requirements as part
of the solution implementation.
93 Infrastructure Requirements Specify the minimum database requirements,
including sizing.
94 Infrastructure Requirements Specify the operating system requirements as per
your preferred solution architecture.
95 Infrastructure Requirements Specify the development software typically required
in order to develop customizations.
96 Infrastructure Requirements Specify the hardware sizing required to support the
solution implementation and operations.
97 Interoperability
- Ability to migrate into/out of the cloud to
Cloud/On-premise
- Ability to integrate into on-premise IT
- Portability between providers
a. Service portability
b. Data portability
98 Instance Requirements
- One instance shall be on the cloud
- One instance should be on premise
- Real time synchronization to be enabled
between instances
- Near zero time to shift between instances
99 General Requirement The system must use web technologies for easy
deployment
100 General Requirement
The system shall have a capability of active and
passive dynamic monitoring of all system
components, services, resources and interfaces
101 Integration Requirement
The system shall support event driven and efficient
data and message formats, as well as real-time data
propagation
102 Integration Requirement The system must come with RESTful API and
standard SOA services
103 Integration Requirement
System shall be able to integrate with 3rd-parties
using various mechanisms (AIDX, API or
Webservices)
64
# Item Requirement
104 Integration Requirement
The system shall come with an extensive library of
integration services for support of varied business
operational and maintenance processes
105 Integration Requirement
Modular service architecture to allow low risk, easy
deployment of new services onto an operational
integration platform
106 Mobile Compatibility The system must come with a mobile application
accessible on mobile devices (phones, tablets)
107 Mobile Compatibility The system must be able to provide KPI dashboards
with analytics via mobile device.
41 Integration with Enterprise Messaging
System
Notifications / alerts should be sent via SMS / Email
/ automated call using Enterprise Messaging
Systems
65
Annexure1: Compliance Statement
Tender Cost& EMD Submission:
(This Compliance statement duly filled, along with the scanned copies of the documents to be submitted
in Cover-1: Fee)
AUTHORIZED SIGNATURE :
NAME OF THE SIGNATORY :
NAME & ADDRESS OF THE TENDERER :
OFFICIAL SEAL & Date :
# Documents “YES “for Complied
“NO” for not Complied
01 Online submission of Tender Cost / Fee:
INR50,000/- (Rupees Fifty Thousand Only) + 18% GST
02
Online submission of EMD (Earnest Money Deposit) / Security
Deposit:
INR 1,00,00,000/- (Rupees One Crore Only)
66
Annexure 2:Unconditional Acceptance Letter
ACCEPTANCE LETTER
The Managing Director,
Kannur International Airport,
Mattannur,
Kannur - 670702.
ACCEPTANCE OF TERMS AND CONDITIONS OF TENDER
Name of work: Selection of Agency for Procurement, Design, Development, Testing,
Implementation, Integration and Operation & Maintenance of an Airport Operational
Database (AODB), Resource Management System (RMS) and Master Systems Integration
(MSI) for Kannur International Airport Limited.
Tender no: KIAL/IT/RFP/2/2019
Dear Sir,
1. The tender documents for the works mentioned above have been sold to me/us by Kannur
International Airport Ltd and I/we hereby certify that I/we have inspected the site and read the
entire terms and conditions of the tender documents made available in the website
https://www.kannurairport.aero/tender, which shall form part of the contract agreement and I/We
shall abide by the conditions/clauses contained therein.
2. I/We hereby unconditionally accepts the general tender conditions of KANNUR
INTERNATIONAL AIRPORT LIMITED’s tender documents in its entirety for the above works
and in case we have put forth any conditions same may be treated as withdrawn.
3. I/we hereby accepts that all the technical specifications as brought out in the tender are
acceptable and where ever, it is not meeting the listed technical specifications in the RFP, a
deviation has been indicated in the Technical Specification Compliance Sheet (Annexure 3),
without affecting the intended purpose or the overall software functionality. I/We hereby fully
understand and accept, that if such deviation is not acceptable to KANNUR AIRPORT, the tender
submitted by us is liable to be rejected, without any further notice/clarification.
4. That, I/We declare that I/We have not paid and will not pay any bribe to any officer of
KANNUR INTERNATIONAL AIRPORT LIMITED for awarding this contract at any stage during
its execution or at the time of payment of bills, and further if any officer of KANNUR
INTERNATIONAL AIRPORT LIMITED asks for bribe/gratification, I will immediately report it
to the Appropriate Authority in KANNUR INTERNATIONAL AIRPORT LIMITED’.
5. The required earnest money as specified in for this work has also been submitted and is attached
herewith.
67
Yours faithfully,
AUTHORIZED SIGNATURE
NAME OF THE SIGNATORY :
NAME & ADDRESS OF THE TENDERER :
OFFICIAL SEAL & DATE :
68
Annexure 3: Technical Bid Qualification Compliance Statement
#
Critical Functional
Requirements of Kannur
Airport
Requirement met by
Deviation Standard
AODB &
RMS Product
Third
Party
tool
Requires
Development
1.
<Individual line item wise
compliance for the requirements
listed in Section 6 of the main
RFP shall be provisioned by
Contractor>
69
Annexure4: Proposal Covering Letter in response to RFP Notice
(To be submitted on the Letterhead of the bidder)
{Place}
{Date}
To,
The Managing Director,
Kannur International Airport,
Mattannur,
Kannur - 670702.
Ref: RFP Notification no: KIAL/IT/TDR/2018-19/2
Subject: Selection of Agency for Procurement, Design, Development, Testing, Implementation,
Integration and Operation & Maintenance of an Airport Operational Database (AODB), Resource
Management System (RMS) and Master Systems Integration (MSI) for Kannur International Airport
Limited.
Dear Sir,
1. Having examined the RFP document, I/we, the undersigned, herewith submit our proposal in
response to your RFP Notification no KIAL/IT/RFP/2/2019 for “Selection of Agency for
Procurement, Design, Development, Testing, Implementation, Integration and Operation &
Maintenance of an Airport Operational Database (AODB), Resource Management System (RMS)
and Master Systems Integration (MSI) for Kannur International Airport Limited.” in full
conformity with the said RFP document.
2. I/We have read the provisions of the RFP document and confirm that these are acceptable to us.
I/We further declare that additional conditions, variations, deviations, if any, found in our
proposal shall not be given effect to.
3. I/We agree to abide by this proposal, consisting of this letter, the detailed response to the RFP and
all attachments, for a period of 120 days from the date of opening of financial proposals.
4. I/We hereby declare that I/we am/are not involved in any major litigation that may have an impact
of affecting or compromising the delivery of services as required under this assignment and I/we
am/are not under a declaration of ineligibility for corrupt or fraudulent practices.
5. I/We hereby declare that there is no conflict of interest in the services that we will be providing
under the terms and conditions of this RFP.
6. I/We hereby declare that all the information and statements made in this proposal are true and
accept that any misrepresentation contained in it may lead to my/our disqualification.
7. I/We understand you are not bound to shortlist / accept any or all proposal you receive.
70
8. I/We hereby declare that information provided by me/us in respect of the eligibility criteria
mentioned at clause 2.20.2 is correct as per our record.
Our correspondence details with regards to this proposal are:
# Information Details
1 Name of responding firm:
2 Address of responding firm:
3
Name, Designation and Address of the
contact person to whom all references
shall be made regarding this RFP:
4 Telephone no. of contact person:
5 Mobile no. of contact person:
6 Fax no. of contact person:
7 E-mail address of contact person:
I/We am/are enclosing details of my/our company in the format as given in Form 2.
I/We hereby declare that our proposal submitted in response to this RFP is made in good faith and
the information contained is true and correct to the best of my/our knowledge and belief.
Sincerely, [FIRM’S NAME]
Name
Title
Signature
Date
Stamp of the Signatory
71
Annexure 5: Power of Attorney
POWER OF ATTORNEY FOR SIGNING OF TENDER DOCUMENTS
(Duly Filled, scanned copy to be submitted in Cover - I: Technical Bid)
Know all men by these presents, We ____________________________________________ (name of the
Principal/firm and address of the registered office) do hereby irrevocably constitute, nominate, appoint
and authorize Mr./ Ms. (name), _______________________________________ son/daughter/wife of
_____________________________________________________ and presently residing at
____________________________, who is presently employed with us holding the position of
__________________________________________________, as our true and lawful attorney
(hereinafter referred to as the "Attorney") to do in our name and on our behalf, all such acts, deeds and
things as are necessary or required in connection with or incidental to submission of our bid for “Selection
of Agency for Procurement, Design, Development, Testing, Implementation, Integration and Operation
& Maintenance of an Airport Operational Database (AODB), Resource Management System (RMS) and
Master Systems Integration (MSI) for Kannur International Airport, Kerala, India under the Kannur
International Airport Limited (the "Authority") including but not limited to signing and submission of all
applications, bids and other documents and writings, participate in Pre-Applications and other conferences
and providing information/ responses to the Authority, representing us in all matters before the Authority,
signing and execution of all contracts, and generally dealing with the Authority in all matters in connection
with or relating to or arising out of our bid for the said Project and/ or upon award thereof to us and/or till
the entering into of the Agreement with the Authority and we hereby agree to ratify and confirm and do
hereby ratify and confirm all acts, deeds and things done or caused to be done by our said Attorney
pursuant to and in exercise of the powers conferred by this Power of Attorney and that all acts, deeds and
things done by our said Attorney in exercise of the powers hereby conferred shall and shall always be
deemed to have been done by us.
IN WITNESS WHEREOF WE, _____________________________________________________, THE
ABOVE NAMED PRINCIPAL HAVE EXECUTED THIS POWER OF ATTORNEY ON THIS
__________________________________DAY OF _________________ 20…
For____________________________ (Signature, name, designation and address) \
Witnesses: 1.
2.
(Notarized)Accepted
___________________________ (Signature)
(Name, Title and Address of the Attorney)
72
Annexure 6: Undertaking for not been Blacklisted
UNDERTAKING FOR NOT BEEN BLACKLISTED
(Duly filled in the letter head of the tenderer, scanned copy to be submitted in Cover-1)
We do hereby undertake that our firm or its partners or Directors have not been blacklisted or any case is
pending or any complaint regarding irregularities is pending, in India or abroad, by any Global
International body like World Bank/International Monetary Fund/World Health Organization etc. or any
Indian State/Central Governments Departments or Public Sector undertaking of India
Date: Signature of tenderer with seal
73
Annexure 7: Affidavit
AFFIDAVIT
(To be submitted on non-judicial stamp paper (Rs.500/-),
Scanned copy to be submitted in Cover-1: Technical Bid)
1. The undersigned do hereby certify that all the statements made in the attachments are true and correct.
2. The undersigned hereby authorizes and requests any Bank person, Firm or Corporation to furnish
pertinent information deemed necessary and requested by Kannur International Airport Limited.
3. The undersigned understands and agrees that further qualifying information may be requested and
agrees to furnish any such information at the request of Kannur International Airport Limited.
4. The undersigned also hereby certifies that neither our firms/companies have abandoned any work in
India, nor any contract awarded to us for such work has been rescinded in the past five years.
5. The undersigned also hereby authorizes Kannur International Airport Limited and their authorized
representative to conduct any enquiries or investigation to verify the statements, documents and
information submitted in connection with this application, and to seek clarification from our bankers
and clients regarding any financial and technical capability. This will also serve as authorization to
Kannur International Airport Limited representative to contact in person or otherwise, any individual
or authorized representative of any institution referred to in the supporting information and obtain
such information as may be required by him to verify statements and information provided in this
application, or with regard to the resources, experience and competence of the Applicant.
6. The undersigned understands that furnishing of false information could result in disqualification.
(Signed by Authorized signatory of the bidder)
…………………………..
……………………………
Title of Officer
Name of bidder
……………………………………….
Date ……………………………….
Encl: Requisite Power of Attorney
74
Annexure 8: SLA Computation
Modules Categorization*
Severity 1
(HIGHLY CRITICAL) AODB, RMS Real Time modules and interfaces
Severity 2
(CRITICAL) RMS Planning Modules
Severity 3
(OTHERS) Remaining modules
SLA Highly Critical Critical Others
Response Time from
the time of problem
report
30 minutes (On Call) 30 minutes 2 hours
Resolution/Workaround
from the time of
problem report
2 hours 4 hours 2 days
The purpose of this SLA is to clearly define the levels of service to be provided by the Contractor for the
duration of this contract or until this SLA has been amended. Key principles driving this SLA are:
a) SLA is between the Contractor and Kannur Airport.
b) Make explicit the performance related expectations from the Contractor.
c) Trigger a process that facilitates Kannur Airport and the Contractor’s management attention to in
the event the performance drops below the set expectations.
Severity Level Severity Level definition
Severity 1
(Highly Critical)
A critical function is not available or very seriously impaired:
The impact on business is severe; a large number of end users are unable to
perform their normal work; and/or no readily available alternative exists.
Severity 2
(Critical)
A critical service is seriously impacted by a problem:
There is no realistic workaround available and financial, customer-related, or
safety related impacts could occur.
Severity 3
(Others)
A non-critical service is unavailable or impaired by a problem:
There is no direct immediate impact on business. Work can continue with
minor disruptions or loss of Efficiency. Alternative ways of performing
normal work are available.
75
Annexure 9: Non-Disclosure Agreement
This Non-Disclosure Agreement ("Non-Disc") is made and entered into day of
month year (effective date) by and between
Kannur International Airport Limited ("Kannur Airport") and ("Company").
Whereas, Kannur Airport and Company have entered into an Agreement ("Agreement")
Effective for ………………; and
Whereas, each party desires to disclose to the other party certain information in oral or written form which
is proprietary and confidential to the disclosing party, ("CONFIDENTIAL INFORMATION").
NOW, THEREFORE, in consideration of the foregoing and the covenants and agreements contained
herein, the parties agree as follows:
1 Definition
As used herein:
a. The term “Confidential Information” shall include, without limitation, all information and
materials, furnished by either Party to the other in connection with citizen/users/persons/customers
data, products and/or services, including information transmitted in writing, orally, visually, (e.g.
video terminal display) or on magnetic or optical media, and including all proprietary information,
customer & prospect lists, trade secrets, trade names or proposed trade names, methods and
procedures of operation, commercial or marketing plans, licensed document know-how, ideas,
concepts, designs, drawings, flow charts, diagrams, quality manuals, checklists, guidelines,
processes, formulae, source code materials, specifications, programs, software packages, codes
and other intellectual property relating to the disclosing party’s data, computer database, products
and/or services. Results of any tests, sample surveys, analytics, data mining exercises or usages
etc. carried out by the receiving party in connection with the Airport’s Information including
citizen/users/persons/customers personal or sensitive personal information as defined under any
law for the time being in force shall also be considered Confidential Information.
b. The term, “Airport” shall include the officers, employees, agents, consultants, contractors and
representatives of Kannur Airport.
c. The term, “Company” shall include the directors, officers, employees, agents, consultants,
contractors and representatives of Company, including its applicable affiliates and subsidiary
companies.
2 Protection of confidential information
With respect to any Confidential Information disclosed to it or to which it has access, Company affirms
that it shall:
a. Use the Confidential Information as necessary only in connection with Project and in accordance
with the terms and conditions contained herein;
b. Maintain the Confidential Information in strict confidence and take all reasonable steps to enforce
76
the confidentiality obligations imposed hereunder, but in no event take less care with the
Confidential Information that the parties take to protect the confidentiality of its own proprietary
and confidential information and that of Kannur Airport;
c. Not to make or retain copy of any commercial or marketing plans,
citizen/users/persons/customers database, Proposals developed by or originating from Kannur
Airport or any of the prospective clients of Kannur Airport except as necessary, under prior
written intimation from Kannur Airport, in connection with the Project, and ensure that any such
copy is immediately returned to Kannur Airport even without express demand from Kannur
Airport to do so;
d. Not disclose or in any way assist or permit the disclosure of any Confidential Information to any
other person or entity without the express written consent of the other party; and
e. Return to the other party, or destroy, at Kannur Airport’s discretion, any and all Confidential
Information disclosed in a printed form or other permanent record, or in any other tangible form
(including without limitation, all copies, notes, extracts, analyses, studies, summaries, records
and reproductions thereof) immediately upon the earlier to occur of (i) expiration or termination
of either party’s engagement in the Project, or (ii) the request of the other party therefore.
f. Not to discuss with any member of public, media, press, any or any other person about the nature
of arrangement entered between Kannur Airport and Company or the nature of services to be
provided by the Company to the Kannur Airport.
3 Onus
Company shall have the burden of proving that any disclosure or use inconsistent with the terms and
conditions hereof falls within any of the foregoing exceptions.
4 Exceptions
These restrictions as enumerated in section 1 of this Agreement shall not apply to any
Confidential Information:
a. Which is independently developed by Company or lawfully received from another source free of
restriction and without breach of this Agreement; or
b. After it has become generally available to the public without breach of this Agreement by
Company; or
c. Which at the time of disclosure to Company was known to such party free of restriction and
evidenced by documentation in such party’s possession; or
d. Which Kannur Airport agrees in writing is free of such restrictions.
e. Which is received from a third party not subject to the obligation of confidentiality with respect
to such Information.
5 Remedies
Company acknowledges that (a) any actual or threatened disclosure or use of the Confidential Information
by Company would be a breach of this agreement and may cause immediate and irreparable harm to
Kannur Airport; (b) Company affirms that damages from such disclosure or use by it may be impossible
to measure accurately; and (c) injury sustained by Kannur Airport may be impossible to calculate and
remedy fully. Therefore, Company acknowledges that in the event of such a breach, Kannur Airport shall
77
be entitled to specific performance by Company of Company’s obligations contained in this Agreement.
In addition, Company shall indemnify Kannur Airport of the actual and liquidated damages which may
be demanded by Kannur Airport. Moreover, Kannur Airport shall be entitled to recover all costs
(including reasonable attorneys’ fees) which it or they may incur in connection with defending its interests
and enforcement of legal rights arising due to a breach of this agreement by Company.
6 Need to Know
Company shall restrict disclosure of such Confidential Information to its employees and/or consultants
with a need to know (and advise such employees of the obligations assumed herein), shall use the
Confidential Information only for the purposes set forth in the Agreement, and shall not disclose such
Confidential Information to any affiliates, subsidiaries, associates and/or third party without prior written
approval of the disclosing party.
7 Intellectual Property Rights Protection
No license to a party, under any trademark, patent, copyright, design right, mask work protection right, or
any other intellectual property right is either granted or implied by the conveying of Confidential
Information to such party.
8 No Conflict
The parties represent and warrant that the performance of its obligations hereunder do not and shall not
conflict with any other agreement or obligation of the respective parties to which they are a party or by
which the respective parties are bound.
9 Authority
The parties represent and warrant that they have all necessary authority and power to enter into this
Agreement and perform their obligations hereunder.
10 Dispute Resolution
If any difference or dispute arises between the Kannur Airport and the Company in connection with the
validity, interpretation, implementation or alleged breach of any provision of this Agreement, any such
dispute shall be referred to the Managing Director, Kannur Airport. If either Party objects to any action
or inaction of the other Party, the objecting Party may file a written Notice of Dispute to the other Party
providing in detail the basis of the dispute. The Party receiving the Notice of Dispute will consider it and
respond in writing within fourteen (14) days after receipt. If that Party fails to respond within fourteen
(14) days, or the dispute cannot be amicably settled within fourteen (14) days following the response of
that Party, the dispute may be referred to by either Party to the Court of Law for which the jurisdiction of
the Court shall be at Thiruvananthapuram.
11 Governing Law
78
This Agreement shall be interpreted in accordance with and governed by the substantive and procedural
laws of India and the parties hereby consent to the exclusive jurisdiction of Courts and/or Forums situated
at Thiruvananthapuram, Kerala, India only.
12 Entire Agreement
This Agreement constitutes the entire understanding and agreement of the parties, and supersedes all
previous or contemporaneous agreement or communications, both oral and written, representations and
under standings among the parties with respect to the subject matter hereof.
13 Amendments
No amendment, modification and/or discharge of this Agreement shall be valid or binding on the parties
unless made in writing and signed on behalf of each of the parties by their respective duly authorized
officers or representatives.
14 Binding Agreement
This Agreement shall be binding upon and inure to the benefit of the parties hereto and their respective
successors and permitted assigns.
15 Severability
It is the intent of the parties that in case any one or more of the provisions contained in this Agreement
shall be held to be invalid or unenforceable in any respect, such provision shall be modified to the extent
necessary to render it, as modified, valid and enforceable under applicable laws, and such invalidity or
unenforceability shall not affect the other provisions of this Agreement.
16 Waiver
If either party should waive any breach of any provision of this Agreement, it shall not thereby be deemed
to have waived any preceding or succeeding breach of the same or any other provision hereof.
17 Survival
Both parties agree that all their obligations undertaken herein with respect to Confidential Information
received pursuant to this Agreement shall survive till perpetuity even after any expiration or termination
of this Agreement.
18 Non-solicitation
During the term of this Agreement and thereafter for a further period of two (2) years Company shall not
solicit or attempt to solicit Kannur Airport’s employees and/or consultants, for the purpose of
79
hiring/contract or to proceed to conduct operations/business similar to Airport with any employee and/or
consultant of the Airport who has knowledge of the Confidential Information, without the prior written
consent of Kannur Airport. This section will survive irrespective of the fact whether there exists a
commercial relationship between Company and Kannur Airport.
19 Term
Subject to aforesaid section 17, this Agreement shall remain valid up to 48 (Forty-Eight) months from the
“effective date”.
IN WITNESS HEREOF, and intending to be legally bound, the parties have executed
this Agreement to make it effective from the date and year first written above.
For Kannur Airport, For Company
Name: Name:
Title: Title:
WITNESSES: WITNESSES:
1. 1.
2. 2.
80
Annexure 10: Network Schematic Diagram
A) Schematic Network Layout (Main Network)
B) Schematic Network Layout (CCTV)
Figure 2: Schematic Network Layout (CCTV)
Figure 1: Schematic Network Layout (Main Network)
81
Annexure 11: Guidelines for Technical Proposal
Technical Proposal should comprise of the following:
1. A covering letter, on the bidding organization's letterhead with all required information and authorized
representative's initials shall be submitted along with the technical proposal. Do not, otherwise, edit
the content of the proposal cover letter.
2. The technical proposal must not contain any pricing information. In submitting additional
information, please mark it as supplemental to the required response.
3. The technical proposal should contain a detailed description of how the bidder will provide the
required services of AODB & RMS outlined in this RFP. It should articulate in detail, as to how the
bidder's Technical Solution meets the requirements specified in the RFP.
4. Proposals must be direct, concise, and complete. All information not directly relevant to this RFP
should be omitted. Kannur International Airport Limited will evaluate bidder's proposal based upon
its clarity and the directness of its response to the requirements of the project as outlined in this RFP.
5. The bidder is expected to provide deliverables for the proposed solution as part of technical proposal
without price quote. The deliverables as given in the technical solution should be in consonance with
the financial proposal. Any deviations in the final deliverables between technical and financial
proposals shall make the proposal as being unresponsive and may lead to disqualification of the
proposal. Kannur International Airport Limited reserves the right to take appropriate action in this
regard.
6. The bidder must address the following in their project implementation strategy:
a. A detailed Project schedule along with a milestone chart.
b. Approach and Methodology of design, development and management of the AODB &
RMSSystems
c. Project Management tools proposed to be used for project.
d. Bidder's plan to address the key challenges of the project.
7. The technical proposal should address the following minimum requirements:
a. The proposal should have information specific to Kannur International Airport Limited’s
System
b. Describe how the functional requirements will be translated into technical
implementations, that is, it should map with the Functional Requirements Specifications.
c. Propose how availability and performance for the system will be measured and maintained.
d. Project Management Plan including:
i. Team composition and Tasks assigned
ii. Implementation Methodology and Plan to include
• Key implementation objectives, key deliverables and an implementation
82
schedule for the same
• Roll-out Plan
• Indication of Time Frame
• Acceptance Testing Plan
• Escalation Process during implementation
iii. Hosting Plan
iv. Quality and Security Assurance Plan
v. Training Plan
vi. Hand holding, Operation and Maintenance Plan
vii. Licensing details of software
viii. Responsibility Matrix
ix. Post Implementation Plan
• Proposed Operation & Maintenance Plan for the O&M Period.
• Resource deployment plan during the O&M Period
• Issue escalation matrix plan.
• Exit Plan
8. The bidder should also include an indicative proposal for hardware/network requirements, that needs
to be procured by Kannur Airport for project implementation.
83
Annexure12: Guidelines for Financial Proposal
1. Unless expressly indicated, bidder shall not include any technical information regarding the services
in the financial proposal.
2. Prices shall be quoted entirely in Indian Rupees.
3. No adjustment of the contract price shall be made on account of any variations in costs of labor and
materials or any other cost component affecting the total cost in fulfilling the obligations under the
contract. The contract price shall be the only payment payable to the bidder for completion of the
contractual obligations by the Bidder under the Contract, subject to the terms of payment specified in
the contract. The price quoted would be exclusive of GST. Prices quoted shall be inclusive of supply
at site, installation and commissioning. No extra payment on any account shall be admissible.
4. The prices, once offered, must remain fixed and must not be subject to escalation for any reason
whatsoever within the period of project. A proposal submitted with an adjustable price quotation or
conditional proposal may be rejected as non-responsive.
84
Form1: Financial Proposal Submission Form
(To be submitted on the Letterhead of the bidder)
[Location, Date]
To,
The Managing Director,
Kannur International Airport,
Mattannur,
Kannur - 670702
Ref: RFP Notification no KIAL/IT/TDR/2018-19/2
Subject: Submission of Financial proposal in response to the RFP for “Selection of Agency for
Procurement, Design, Development, Testing, Implementation, Integration and Operation &
Maintenance of an Airport Operational Database (AODB), Resource Management System (RMS) and
Master Systems Integration (MSI) for Kannur International Airport Limited.”
Dear Sir,
I/We, the undersigned, offer to provide the services for “Selection of Agency for Procurement, Design,
Development, Testing, Implementation, Integration and Operation & Maintenance of an Airport
Operational Database (AODB), Resource Management System (RMS) and Master Systems
Integration (MSI) for Kannur International Airport Limited.” in accordance with your Request for
Proposal dated [Insert Date] and our Technical Proposal. Our attached Financial Proposal is for the
sum of [Insert amount(s) in words and figures]. We are aware that any conditional financial offer will
be outright rejected by Kannur International Airport Limited. This amount is exclusive of taxes as
listed at Form 5 (Consolidated Cost Summary) attached.
Our Financial Proposal shall be binding upon us subject to the modifications resulting from Contract
negotiations, up to expiration of the validity period of the Proposal i.e. 120 days from the date of
opening of financial bid.
We are aware that Kannur International Airport Limited reserves the right to accept or reject any or
all bids without assigning any reasons thereof.
I/We remain,
Yours sincerely,
Authorized Signature [In full and initials]:
Name and Title of Signatory:
Name of Firm:
Stamp of the Signatory:
85
Form 2: Details of responding firm [In support of 2.20.2]
Sr. No. Particulars Details to be Furnished
1 Details of Responding Firm
Name
Address
Telephone Fax
Email Website
2 Information about Responding Firm
Status of Firm/ Company (Public Ltd., Pvt. Ltd., etc.)
Details of Registration (Ref e.g., ROC Ref #) Date
Ref #
Number of professionals (on the rolls of the firm) providing managed services (excluding temporary
staff)
Locations and addresses of offices (in India and overseas)
Certificates (Please attach copy) as required in the Eligibility and Technical Evaluation Criteria
86
Form 3: Format of Performance Bank Guarantee ( See clause 2.21 )
ANNEXURE d
Format
In consideration of Kannur International Airport Limited, having its office at Kara-Peravoor
Road, Mattannur, Kannur, Kerala, India (hereinafter referred to as the "Kannur Airport", which
expression shall unless it be repugnant to the subject or context thereof include its, successors and
assigns) having agreed to receive the Bid of _________ {●} and having its registered office at --------
------------------- (hereinafter referred to as the "Bidder" which expression shall unless it be repugnant
to the subject or context thereof include its/their executors administrators, successors and assigns), for
Procurement, Design, Development, Testing, Implementation, Integration and Operation &
Maintenance of an Airport Operational Database (AODB), Resource Management System (RMS) and
Master Systems Integration (MSI) for Kannur International Airport in Mattanur, Kannur, Kerala
(hereinafter referred to as the "Services") pursuant to the RfP Document dated .................................
issued in respect of the Services and other related documents (hereinafter collectively referred to as
"Bidding Documents"), we [Name of the Bank] having our registered office at _____ and one of its
branches at ________ (hereinafter referred to as the "Bank"), at the request of the Bidder, do
irrevocably, unconditionally and without reservation guarantee the due and faithful fulfilment and
compliance of the terms and conditions of the Bidding Documents (including the RfP) by the said
Bidder and unconditionally and irrevocably undertake to pay forthwith to Kannur Airport an amount
of [INR ..................... as performance Security (hereinafter referred to as the " Performance
Security") as our primary obligation without any demur, reservation, recourse, contest or protest and
without reference to the Bidder if the Bidder shall fail to fulfil or comply with all or any of the terms
and conditions contained in the said Bidding Documents.
(a)Any such written demand made by Kannur Airport stating that the Bidder is in default of the due
and faithful fulfilment and compliance with the terms and conditions contained in the Bidding
Documents shall be final, conclusive and binding on the Bank.
(b) We, the Bank, do hereby unconditionally undertake to pay the amounts due and payable under
this Guarantee without any demur, reservation, recourse, contest or protest and without any
reference to the Bidder or any other person and irrespective of whether the claim of Kannur
Airport is disputed by the Bidder or not merely on the first demand from Kannur Airport
stating that the amount claimed is due to Kannur Airport by reason of failure of the Bidder to
fulfil and comply with the terms and conditions contained in the Bidding Documents
including failure of the said Bidder to keep its Bid open during the Bid validity period as set
forth in the said Bidding Documents for any reason whatsoever. Any such demand made on
the Bank shall be conclusive as regards amount due and payable by the Bank under this
Guarantee. However, our liability under this Guarantee shall be restricted to an amount not
exceeding [amount].
(c) This Guarantee shall be irrevocable and remain in full force for a period of
.......................inclusive of a claim period of 60 (sixty) days or for such extended period as
may be mutually agreed between Kannur Airport and the Bidder, and agreed to by the Bank,
87
and shall continue to be enforceable till all amounts under this Guarantee have been paid.
(d) We, the Bank, further agree that Kannur Airport shall be the sole judge to decide as to
whether the Bidder is in default of due and faithful fulfilment and compliance with the terms
and conditions contained in the Bidding Documents including, inter alia, the failure of the
Bidder to keep its Bid open during the Bid validity period set forth in the said Bidding
Documents, and the decision of Kannur Airport that the Bidder is in default as aforesaid shall
be final and binding on us, notwithstanding any differences between Kannur Airport and the
Bidder or any dispute pending before any court, tribunal, arbitrator or any other Kannur
Airport.
(e) The Guarantee shall not be affected by any change in the constitution or winding up of the
Bidder or the Bank or any absorption, merger or amalgamation of the Bidder or the Bank
with any other person.
(f) In order to give full effect to this Guarantee, Kannur Airport shall be entitled to treat the
Bank as the principal debtor. Kannur Airport shall have the fullest liberty without affecting
in any way the liability of the Bank under this Guarantee from time to time to vary any of
the terms and conditions contained in the said Bidding Documents or to extend time for
submission of the Bids or the Bid validity period or the period for conveying acceptance of
Letter of Award by the Bidder or the period for fulfilment and compliance with all or any of
the terms and conditions contained in the said Bidding Documents by the said Bidder or to
postpone for any time and from time to time any of the powers exercisable by it against the
said Bidder and either to enforce or forbear from enforcing any of the terms and conditions
contained in the said Bidding Documents or the securities available to Kannur Airport, and
the Bank shall not be released from its liability under these presents by any exercise by
Kannur Airport of the liberty with reference to the matters aforesaid or by reason of time
being given to the said Bidder or any other forbearance, act or omission on the part of Kannur
Airport or any indulgence by Kannur Airport to the said Bidder or by any change in the
constitution of Kannur Airport or its absorption, merger or amalgamation with any other
person or any other matter or thing whatsoever which under the law relating to sureties would
but for this provision have the effect of releasing the Bank from its such liability.
(g) Any notice by way of request, demand or otherwise shall be sufficiently given or made if
addressed to the Bank and sent by courier or by registered mail to the Bank at the address
set forth herein.
(h) We undertake to make the payment on receipt of your notice of claim on us addressed to
[name of Bank along with branch address] and delivered at our above branch which shall be
deemed to have been duly authorised to receive the said notice of claim.
(i) It shall not be necessary for Kannur Airport to proceed against the said Bidder before
proceeding against the Bank and the guarantee herein contained shall be enforceable against
the Bank, notwithstanding any other security which Kannur Airport may have obtained from
the said Bidder or any other person and which shall, at the time when proceedings are taken
against the Bank hereunder, be outstanding or unrealised.
(j) We, the Bank, further undertake not to revoke this Guarantee during its currency except with
88
the previous express consent of Kannur Airport in writing.
(k) The Bank declares that it has power to issue this Guarantee and discharge the obligations
contemplated herein, and the undersigned is duly authorised and has full power to execute
this Guarantee for and on behalf of the Bank.
Signed and Delivered by _______ Bank
By the hand of Mr./Ms. ___ _____, its ________ and authorised official.
(Signature of the Authorised Signatory)
(Official Seal).
(Signature of the Authorised Signatory)
(Official Seal)
89
Form 4: Details for Financial Proposal Consolidated Cost Summary
# Item Description Qty Units Rate in
figures
Total
Amount
without
Tax
Total
Amount in
words
1.0
Design, Development, Testing,
Implementation and Master
System Integration (MSI)of
Airport Operational Database
(AODB) and Resource
Management System(RMS)
comprising for Kannur
International Airport Limited
with all the required packages.
1.00 LS
2.0 Procurement of software and
licenses 1.00 LS
3.0
Operation and Maintenance of the
entire system for a period of 5
Years including the AMC for the
requisite licenses
1.00 LS
3.01 1st year 1.00 LS
3.02 2nd Year 1.00 LS
3.03 3rd Year 1.00 LS
3.04 4th Year 1.00 LS
3.05 5th Year 1.00 LS
4.0
Man Hour Cost for additional
development against change
orders (For 1440 Hours)
1.00 LS
5.0 Cloud Hosting Charges 1.00 LS
6.0
Additional optional period of
Operation & maintenance
including AMC for the requisite
licenses
6.01 6th Year 1.00 LS
6.02 7th Year 1.00 LS
Note 1: Payment shall be made as per the clause Payment Terms and Schedule 2.22
Bidders are to quote without Taxes. However, the GST shall be paid at the prevailing rate at the time
of effecting payment.
Note 2: # 1.0 to 5.0 will be considered for financial bid evaluation.
Note 3: # 6.0 will be required for entering into a contract for O&M support after the expiry of 5 years
O&M contract stipulated in this RFP. However, quoted price for the 6th and the 7th year shall adhere
90
to the terms set in section 2.20.4 under Financial Bid Evaluation.
Note 4: Contractor shall not front load the cost with capital expenditure and shall propose the cost in
operational expenditure model paid on a quarterly basis over a period of 6 years for both the license,
implementation and maintenance costs.
Note 5: The license cost shall be based on the actual licenses utilized.
91
Form 5: Format of providing citations
# Item Guidelines Attachment
Ref. No for details
1 Name of the Project
2 Date of Work Order
3 Client Details Name: Contact person’s Name & No.
4 Scope of Work Provide Scope of Work: Highlight Key
Result Areas expected and achieved
5 Contract Value
Provide particulars on Contract value
assigned to each major phase and
milestone
6 Complete Project
Duration
Provide particulars on the total time taken
on completion of the project including
time details on various activities
92
Form 6: Team Member Profile
S.No. Item Details
1 Name
2 Specify role to be
played
3 Current Job Title
4 Experience in yrs. (Provide details regarding name of organizations worked for,
Designation, responsibilities, tenure etc.)
5 Name of Organization From To Designation/Responsib
ilities
6 Number of Years with
Current Organization
7 Current Job
Responsibilities
8 Skill Sets
9 Relevant Project Details
10 Project Name Project Duration
(Start to End date) Project Details and Role of Resource
11 Educational Background, Certification, %age of Marks
12
Degree including
stream/subject/Certificat
ion
Year of Award Institution/Uni
versity %age of Marks
93
Form 7: Resource Deployment Plan
The Bidder also needs to fill the below Resource Deployment which it plans to deploy during the
implementation phase of the project.
1. Implementation Phase:
Resource
Name Role
M
1
M
2
M
3
M
4
M
5
M
6
M
7
M
8
M
9
M
10
M
11
M
12
M
…
Project
Manager
F/P
Quality
Manager
Delivery
Manager
Functional
AODB &
RMS Lead
Functional
Bespoke
Lead
Functional
AODB &
RMS
Consultants
Functional
Bespoke
Consultants
Technical
Consultants
Others(Insert
separate line
items for
other roles
proposed)
Note:
• F – Full Time
• P – Part Time
94
2. Resource Deployment Plan during Support Phase
S.
No. Services
Resourc
e Level
(L1/L2/
L3)
Resource
Type
(Onsite
/Remote)
No. of
Resourc
es Year
1
No. of
Resourc
es Year
2
No. of
Resourc
es Year
3
No. of
Resourc
es Year
4
No. of
Resourc
es Year
5
1 Program
Manger
2 Helpdesk
3 Application
Management
4
Others(Insert
separate line
items for
other roles
proposed)
Note:
• Resource Deployment sheet shall be as per the support model proposed.
• The proposed model shall fulfil minimum requirements outlined in the RFP and as per the Service
Window
Bidder should ensure that support model should meet SLA requirements and Industry best practices
