26-003 Greater Dublin Drainage (GDD) – Main Works Contracts

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

Uisce Éireann ran this procurement for “26-003 Greater Dublin Drainage (GDD) – Main Works Contracts” 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:

• Core service configuration, integration, and ongoing support obligations were referenced but not numerically defined in the extract.
• ITT-stage documents were expected to carry the granular technical schedules, acceptance tests, and phased rollout details.
• The bidder had to evidence ability to mobilise, operate, and maintain the contracted service profile for the full term. 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.

• Example: Health &Safery Policy Sep 2025.doc becomes H_S_Policy_25
• Example: Health &Safery Policy Sep 2025.doc becomes H_S_Policy_25.doc

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.
• 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.
• gn & Build (DB) Main Works 2 Design & Build (DB) Main Works 3 DBO Form of Contract NEC4 ECC Target Cost NEC4 ECC Target Cost FIDIC Gold/NEC4 DBO Turnover Requirement €100m* €100m* €175m* Indexation Provision Yes Yes Yes Expe

5. Award criteria & scoring

6. Submission requirements

• Method statement / response document (template/page limits) — not specified in extract.
• 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:
• APPENDIX 9: Minimum REQUIREMENTS: Relevant Experience (D2) 55
• they intend to rely on the financial capacity of another entity to satisfy this Minimum Requirement they must submit all of the following: 1
• D2 Relevant Experience (Pass/ Fail) The minimum requirements relevant to each Lot are outlined in Appendix 9 with respect to Previous Project Experience
• o tender (provided four Applicants submit compliant PQQ Responses that meet the minimum requirements)
• These minimum requirements may be met collectively across the submitted reference projects
• according to the relevant section, the relevant appendix number and a descriptive name

7. Key dates & process

8. Contract terms that matter

Contract duration in the extract: 2 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)
• according to the relevant section, the relevant appendix number and a descriptive name
• relevant section, the relevant appendix number and a descriptive name
• [26-003 Tender Pack - PQQ.zip] [ZIP containing 3 files]

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.
• 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 — not clearly specified in extract.
• 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: Notes_for_submission.pdf, APPENDIX 9: Minimum REQUIREMENTS: Relevant Experience (D2) 55](#_Toc222815772), Appendix 9 with respect to Previous Project Experience.
• eTenders CFT / notice reference: not specified in extract.
• Clarification contact / portal: eTenders message portal (email not surfaced in extract).
• Key attachments to prioritise: PQQ Responses that meet the minimum requirements), PQQ Response, appendix number and a descriptive name.