CALL FOR TENDERS FOR THE PROVISION OF CLOUD COMPUTING SERVICES FOR ST JAMES’S HOSPITAL

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

St James's Hospital ran this procurement for “CALL FOR TENDERS FOR THE PROVISION OF CLOUD COMPUTING SERVICES FOR ST JAMES’S HOSPITAL” 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:

• Title: CALL FOR TENDERS FOR THE PROVISION OF CLOUD COMPUTING SERVICES FOR ST JAMES’S HOSPITAL
• 005 Specification and Minimum Requirements for Cloud Computing Services
• Service Level Agreement, which has not been rectified after 30 days from the Employer serving written notic
• [001 Call for to Tenders for Cloud Computing Services.docx] OSPIDÉAL SAN SÉAMAS
• Re: Formal Call for Tenders for the Provision of Cloud Computing Services for St James’s Hospital.
• I enclose herewith the Formal Call for Tenders documentation for the Provision of Cloud Computing Services for St James’s Hospital.
• Tender submissions will be reviewed and evaluated by the IMS (Information Management Services) Steering Group, whose members, have been tasked by the CA with overseeing the tender process, in line with the award criteria as stated herein.
• [001 Call for to Tenders for Cloud Computing Services.docx] instructions contained in this Call for Tenders (CfT) document and that all information requested is returned.
• Interested Parties are advised to read all the tender documentation and to ensure that their submission complies with the instructions contained in this CfT and that all information requested is returned in the 002 Tender Response Document for the Provision of Cloud Computing Services (Economic, Financial and Technical Capacity), 003 Compulsory Pricing Schedule for the Provision of Cloud Computing Services and 005 Software Requirements Specification (SRS) for the Provision of Cloud Computing Services.
• Call for Tenders for the Provision of Cloud Computing Services for St James’s Hospital, known as the Contracting Authority (CA)
• [001 Call for to Tenders for Cloud Computing Services.docx] the CA Terms and Conditions and any additional terms detailed in the Call for Tenders document and pertinent to the above competition.
• This Call for Tenders (CfT) has been prepared for the purpose of requesting tenders in the Open Procedure (OJEU) procurement process in relation to the Provision of Cloud Computing Services for St James’s Hospital (the Contract). 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.

• idence from an objective source confirming that they are in a sound financial position and that they have a turnover of €1,358,090 per annum over the past three years
• HSE hospitals and HSE funded hospitals including section 38 hospitals may utilise the result of this tender,
• The CA undertakes to hold any information provided to it by Tenderers on a confidential basis, subject to the CA’s obligations under law, including the Freedom of Information Act 2014. If, for any reason it is intended that information provided to the CA should not be disclosed because of its sensitive nature, then it is incumbent upon the person or body when supplying the information, to make clear this intention, and to specify the reason for the information’s sensitivity. The CA will endeavour to consult with any Tenderer supplying sensitive information before making a decision on any Freedom of Information request received.
• HSE hospitals and HSE funded hospitals including section 38 hospitals may utilise the result of this tender, where this occurs they must write to St James’s Hospital for permission to use the tender result.

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.; Rule: Tenderer(s) are required to provide current insurance certificates or a broker’s letter confirming the following types and levels of insurance: Employers Liability €13m, Public Liability €6.5m, Products Liability €6; Insurance Type Required Insurance Level Employers Liability €13m Public Liability €6.5m Product Liability €6
• Certifications — Rule: Tenderer(s) are required to provide current insurance certificates or a broker’s letter confirming the following types and levels of insurance: Employers Liability €13m, Public Liability €6.5m, Products Liability €6
• 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.
• Rule: Tenderer(s) are required to provide current insurance certificates or a broker’s letter confirming the following types and levels of insurance: Employers Liability €13m, Public Liability €6.5m, Products Liability €6
• Insurance Type Required Insurance Level Employers Liability €13m Public Liability €6.5m Product Liability €6
• Insurance Type Required Insurance Level Employer Liability €13m Public Liability €6.5m Professional Liability €6

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:
• Value: not disclosed (eTenders placeholder)
• Tenderers are advised that any contract(s) resulting from this CfT process will incorporate the CA’s Terms and Conditions herein (document 004) and that by submitting a tender, tenderers agree with these terms and conditions.
• Interested Parties are advised to read all the tender documentation and to ensure that their submission complies with the instructions contained in this CfT and that all information requested is returned in the 002 Tender Response Document for the Provision of Cloud Computing Services (Economic, Financial and Technical Capacity), 003 Compulsory Pricing Schedule for the Provision of Cloud Computing Services and 005 Software Requirements Specification (SRS) for the Provision of Cloud Computing Services.
• Valid applications must be submitted using www.etenders.gov.ie
• The Closing date for receipt of valid tenders, exclusively by electronic means on www.etenders.gov.ie is:
• If you have any queries on this tender please forward them on www.etenders.gov.ie

7. Key dates & process

8. Contract terms that matter

Contract duration in the extract: 12 months. 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)
• There are three extension periods of 12 months (3 x 12 months)
• erm of the Agreement shall rollover for a further period of 12 months (the ‘Second Term’) unless SJH has noti
• fied the Supplier in writing not less than 3 months prior to the end of the Initial Term th
• erm of the Agreement shall rollover for a further period of 12 months (the ‘Third Term’) unless SJH has notif
• ied the Supplier in writing not less than 3 months prior to the end of the Second Term tha
• rty may, if the Force Majeure event continues for more than 8 weeks terminate this Agreement forthwith on g
• which is capable of remedy, fails to remedy the same within 30 days after receipt of a written notice givin

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: 001 Call for to Tenders for Cloud Computing Services.docx, 004 SJH Terms and Conditions.docx, Schedule for the Provision of Cloud Computing Services and 005 Software Requirements Spe.
• eTenders CFT / notice reference: OJEU) procurement process in relation to the Provision of Cloud.
• Clarification contact / portal: [email protected].
• Key attachments to prioritise: appendixes, by electronic means and through e-Tenders only., Schedule 2.1 b) in Document 002 Tender Response Document for the Provision of Cloud Comp, Schedule 2.1 (D) in Document 002 Tender Response Document for the Provision of Cloud Com.