RFT for Provision of a White Label Booking Engine for Shannon Airport under the trading name 'Fly Shannon.ie'

AI-generated analysis of the documents. Check the official notice and any amendments for current submission details.

1. At a glance

2. Scope of Work

Shannon Airport Authority DAC ran this procurement for “RFT for Provision of a White Label Booking Engine for Shannon Airport under the trading name "Fly Shannon.ie”.” as an operational contract requiring implementation and sustained service execution. The extracted pack showed qualification-stage material with references to later ITT technical depth; practical activity therefore centred on building, integrating, and operating the specified service stack with compliant reporting and handover obligations where stated. Constituent activities and named work elements in the supplied extracts:

• Appendix 6: Draft Service Contract Required? Type of insurance Minimum cover for any one claim Period Yes Public liability for death, personal injury, loss of and damage to property €6,500,000 From date of Agreement until completio
• Within 7 days of service of the notice, the contract
• 1.1 The Contracting Authority invites responses (“Tenders”) to this Request for Tenders (“RFT”) from economic operators (“Tenderers”) for the provision of the services as described in Appendix 1 to this RFT, “Requirements and Specifications”, (“the Services”). Shannon Airport Authority DAC. is the Contracting Authority for this procurement competition (“the Contracting Authority”).
• 2.1.9 Any restraints, covenants, writs, claims or other action current or pending in respect of any item or the Tenderer itself proposed must be declared by the Tenderer. Failure to do so will result in the proposal being disqualified or the Tenderer being held accountable for all losses incurred. Included in this heading are restrictions imposed by foreign governments, government agencies and intergovernmental agencies on the supply, use and subsequent disposal of items of equipment or software.
• 2.1.13 In issuing this RFT, there are no implied obligations for the Contracting Authority to procure any of the services described
• 2.1.13 In issuing this RFT, there are no implied obligations for the Contracting Authority to procure any of the services described in the RFT.
• 2.1.14 The Contracting Authority reserves the right to proceed with the whole or part of the Contract and to amend quantities or descriptions as deemed appropriate to meet their requirements. The Contracting Authority also reserves the right to award sections of the services to different Tenderers depending on final selection.
• 2.3.1 The Contracting Authority will, subject to the right of cancellation of this procurement competition (as set out at paragraph 2.1.3 above and at paragraph 3.2 below), select the successful Tenderer(s) to provide the Services sought under this RFT.
• 2.3.2 The successful Tenderer(s) shall provide the Services in accordance with and on the terms and conditions of the contract as set out at Appendix 6 to this RFT (“the Services Contract”). The successful Tenderer(s) shall be required to enter into the Services Contract with the Contracting Authority. Tenderers should take account of the provisions of the Services Contract in the preparation of their Tenders. Tenderers are required to confirm their acceptance of the Services Contract in the Tenderers’ Statement / Form of Tender at Appendix 3. Tenderers may not amend the Services Contract.
• 2.5.1 Where a group of undertakings submit a Tender in response to this RFT the Contracting Authority will deal with all matters relating to this procurement competition through the entity who will carry overall responsibility for the performance of the Services Contract only (“Prime Service provider”), irrespective of whether or not tasks are to be performed by a subcontractor and/or consortium members. The Tenderer must clearly set out:
• The full legal name of the Prime Service provider together with its registered business address (where applicable), registered business name (where applicable), company registration number (where applicable), telephone and e-mail contact details.
• The names of all subcontractors and/or consortium members who will be involved in the provision of the Services. Non-binding monetary references in the source were treated as context only and were not used as qualification thresholds.

3. Background & buyer context

The buyer context reflected a formal Irish public-procurement route, with pre-qualification used to control entry into the tender stage.

• 2.1.1 While every effort has been made to provide comprehensive and accurate background information and requirements and specifications, Tenderers must form their own conclusions about the solution needed to meet the requirements set out in this RFT. Tenderers and recipients of this RFT may wish to consult their own legal advisers in relation to this RFT or the subject matter thereof.
• 2.1.11 It will be the responsibility of the Tenderer/s to take account of any deficiencies with regard to the information provided and to stipulate any assumptions that impact on this policy when replying to this RFT.
• 2.11.3 The requirement of the Acquired Rights Directive as implemented into Irish law by Statutory Instrument S.I. No. 131 of 2003 European Communities (Protection of Employees on Transfer of Undertakings) Regulations 2003 (“SI 131/2003”), does not apply to staff currently employed by the incumbent provider of the Service sought under this RFT.
• It is the responsibility of all Tenderers to ensure their Tender includes for all costs associated with compliance with the Acquired Rights Directive and SI 131/2003. The Contracting Authority will not, under any circumstances, accept any liability or responsibility whatsoever for any of the content/information provided by the incumbents or for the consequences of any reliance upon or actions taken, by the Tenderer or any third party, on the basis of any of the content/information provided by the incumbents.

4. Eligibility & selection criteria

• Turnover requirement — — use these verbatim for insurance / turnover. If a category (insurance, turnover) has no entry here, treat it as 'not specified' for THIS tender.
• Insurance — — use these verbatim for insurance / turnover. If a category (insurance, turnover) has no entry here, treat it as 'not specified' for THIS tender.; Processor Agreement Page 50 Page 53 Part 1 : Introduction Part 2: Instructions to Tenderers Type of Insurance Indemnity Limit Employer’s Liability €12.7m Public/Product Liability €6; 5m Part 3 – Award Page 53 Part 1 : Introduction Part 2: Instructions to Tenderers Type of Insurance Indemnity Limit Employer’s Liability €12.7m Public/Product Liability €6
• Certifications — not specified for this tender
• Past experience — not specified for this tender
• Personnel — not specified for this tender
• Geographic / facility constraints — not specified for this tender Additional binding lines surfaced in the deterministic extract:
• — use these verbatim for insurance / turnover. If a category (insurance, turnover) has no entry here, treat it as 'not specified' for THIS tender.
• Processor Agreement Page 50 Page 53 Part 1 : Introduction Part 2: Instructions to Tenderers Type of Insurance Indemnity Limit Employer’s Liability €12.7m Public/Product Liability €6
• 5m Part 3 – Award Page 53 Part 1 : Introduction Part 2: Instructions to Tenderers Type of Insurance Indemnity Limit Employer’s Liability €12.7m Public/Product Liability €6
• Appendix 6: Draft Service Contract Required? Type of insurance Minimum cover for any one claim Period Yes Public liability for death, personal injury, loss of and damage to property €6,500,000 From date of Agreement until completio
• Yes Product liability €6,500,000 From date of Agreement until completio
• Yes Employer’s liability for sickness, injury and death of employees €12,700,000 From date of Agreement until completio

5. Award criteria & scoring

6. Submission requirements

• Method statement / response document (template/page limits) — Appendix 1 questionnaire/PQQ response was required.
• CVs (page count, named roles) — not specified in extract.
• Pricing schedule (format/template) — expected at ITT stage.
• Case studies (number/value range) — client references/comparable project evidence was referenced.
• Declarations (ESPD/Bona Fides/Tax/COI) — ESPD/declaration/statement-of-confirmation language was present.
• Mandatory site visit — not specified in extract.
• Submission portal and formatting — eTenders portal and PDF electronic copies were referenced. Submission-related source lines:
• Value: not disclosed (eTenders placeholder)
• Appendix 6: Draft Service Contract Required? Type of insurance Minimum cover for any one claim Period Yes Public liability for death, personal injury, loss of and damage to property €6,500,000 From date of Agreement until completio
• 1.1 The Contracting Authority invites responses (“Tenders”) to this Request for Tenders (“RFT”) from economic operators (“Tenderers”) for the provision of the services as described in Appendix 1 to this RFT, “Requirements and Specifications”, (“the Services”). Shannon Airport Authority DAC. is the Contracting Authority for this procurement competition (“the Contracting Authority”).
• 2.1.4 This RFT supersedes and replaces all previous documentation, communications and correspondence between the Contracting Authority and Tenderers, and Tenderers should place no reliance on such previous documentation and correspondence. Tenderers to this RFT should study the contents of this RFT , including the information and documents contained in the Appendices. The Tenderers attention is drawn to the Tenderers’ aide-memoire at Appendix 4.
• Include a statement confirming whether any of the excluding circumstances listed in Article 57 of EU Council Directive 2014/24/EU as implemented into Irish law by the European Communities (Award of Contracts by Public Sector Undertakings) Regulations 2016 (Statutory Instrument 284 of 2016), apply to the Tenderer. Tenderers from Ireland must include with the Tender the declaration at Appendix 5 to this R
• [RFT for Provision of a White Label Booking Engine for Shannon Airport under the trading name Fly Shannon.ie.docx] U as implemented into Irish law by the European Communities (Award of Contracts by Public Sector Undertakings) Regulations 2016 (Statutory Instrument 284 of 2016), apply to the Tenderer. Tenderers from Ireland must include with the Tender the declaration at Appendix 5 to this RFT (“Declaration”). For all Tenderers outside Ireland the statement must be evidenced, as required.

7. Key dates & process

8. Contract terms that matter

Contract duration in the extract: 3 years. Payment cycle, SLA/KPI schedule, and penalty regime were not fully disclosed in the snippets unless listed below.

• VERIFIED PHRASES (deterministic regex extract from the documents — treat as authoritative for numerical claims)
• NOW IT IS HEREBY AGREED in consideration of the sum of €5 (the receipt of which is hereby acknowledged by the Contractor) as follows:
• ocurement competition will be issued for a term of 3 years (36 months) (“the Term”) from the date of notifica
• the right to extend the Term for a period or periods of up 12 months with 2 such extensions on the same term
• he information contained in this document at any time up to 10 days before the final date for receipt of te
• Payment shall be made within 30 days of receipt of a correct and valid invoi
• breach(es) (if the breach(es) are capable of remedy) within 30 days after receipt of a request in writing f
• For the Term and for a period of 12 months thereafter (and save in respect of publ

9. Risks, red flags & unusuals

• Qualification gate: the deterministic extract included a turnover threshold line (— use these verbatim for insurance / turnover. If a category (insurance, turnover) has no entry here, treat it as 'not specified' for THIS tender.), which can materially narrow bidder pool composition.
• Contract value was not disclosed in metadata, creating uncertainty on margin, resourcing, and financing assumptions.
• The two-step process (PQQ then ITT) shifted effort to compliance evidence early, with competitive scoring detail potentially deferred.
• Technical and contractual granularity appeared ITT-dependent, increasing ambiguity at qualification stage for non-incumbent bidders.

10. SME fit assessment

This competition looked most accessible to firms with established public-sector tender capability, documented financial capacity, and direct operational experience in the relevant service category.

• Credible bidder profile — mid-sized to large specialist with formal QA/compliance process.
• Consortium / sub-contracting — allowed or addressed in the extracts (Appendix references and reliance provisions).
• Indicative bid-prep effort — 6 to 12 working days for evidence collation, form completion, and review cycles at PQQ level.
• Pwin signal — strongest for bidders with reusable qualification artefacts, comparable references, and low-friction mobilisation capability.

11. Where to dig deeper

• Source RFT/PQQ filenames: RFT for Provision of a White Label Booking Engine for Shannon Airport under the trading name Fly Shannon.ie.docx, RFT for Provision of a White Label Booking Engine for Shannon Airport under the tra, Appendix 6: Draft Service Contract Required? Type of insurance Minimum cover for.
• eTenders CFT / notice reference: not specified in extract.
• Clarification contact / portal: [email protected].
• Key attachments to prioritise: RFT”) from economic operators (“Tenderers”) for the provision of the services as de, Appendix 1 to this RFT, “Requirements and Specifications”, (“the Services”). Shannon Ai, RFT is Request for Tender for the Provision of a White Label Booking Engine for Sha.