Skip to main content

We've saved some files called cookies on your device. These cookies are:

  • essential for the site to work
  • to help improve our website by collecting and reporting information on how you use it

We would also like to save some cookies to help tailor communications.

BETA
You're viewing an updated version of this service - your feedback will help us to improve it.

Contract Notice

23-CO-048 - IS - New ESB

  • First published: 31 January 2023
  • Last modified: 31 January 2023
  • Version: N/A
  • This file may not be fully accessible.

  •  

Information icon

The buyer is not using this website to administer the notice.

To record your interest or obtain additional information or documents please find instructions within the Full Notice Text. (NOTE: Contract Award Notices and Prior Information Notices do not normally require a response)

Information icon
You are viewing an expired notice.

Contents

Summary

OCID:
ocds-h6vhtk-03a10e
Published by:
University of Portsmouth
Authority ID:
AA21030
Publication date:
31 January 2023
Deadline date:
16 February 2023
Notice type:
Contract Notice
Has documents:
No
Has SPD:
No
Has Carbon Reduction Plan:
N/A

Abstract

OverviewThe University of Portsmouth is seeking to engage the market with regards the refinement of its requirements to procure an Enterprise Service Bus (ESB). We are seeking assistance to help shape and enhance our current requirements before tendering the solution to the market in the next stage of the procurement process.An Enterprise Service Bus (ESB) is traditionally used to orchestrate all integrations and consists of a few tools that consolidate bespoke developments into a single solution that is both flexible and easy to monitor. These tools considerably reduce the work required to maintain communications between different applications.At the time the University purchased the current ESB, most systems were hosted on site and very few of them communicated in a ‘standard’ way, instead of using bespoke integrations between systems. The ESB purchased was intended to handle all these requirements with the flexibility to adapt to future requirements.The University's approach to integrations has since changed; many on-site systems have been replaced with cloud hosted alternatives, and are becoming more standardised in the way they communicate, with a drive towards a publish and subscribe methodology.The way the University pays for these systems is also changing - rather than buying licences, new solutions are typically based on pay per usage. In the past we did not have to consider the amount of data we moved between systems; with cloud based systems we have to be careful because there is often a charge associated with moving data.

Full notice text

Contract notice

Section I: Contracting authority

I.1) Name and addresses

University of Portsmouth

Winston Churchill avenue

Portsmouth

PO1 2UP

UK

E-mail: procurement@port.ac.uk

NUTS: UKJ31

Internet address(es)

Main address: https://in-tendhost.co.uk/port/aspx/Tenders/Current

I.3) Communication

The procurement documents are available for unrestricted and full direct access, free of charge at:

https://in-tendhost.co.uk/port/aspx/Tenders/Current


Additional information can be obtained from the abovementioned address


Tenders or requests to participate must be sent electronically to:

https://in-tendhost.co.uk/port/aspx/Tenders/Current


Tenders or requests to participate must be sent to the abovementioned address


I.4) Type of the contracting authority

Body governed by public law

I.5) Main activity

Education

Section II: Object

II.1) Scope of the procurement

II.1.1) Title

23-CO-048 - IS - New ESB

Reference number: 23-CO-048 - IS - New ESB

II.1.2) Main CPV code

72000000

 

II.1.3) Type of contract

Services

II.1.4) Short description

OverviewThe University of Portsmouth is seeking to engage the market with regards the refinement of its requirements to procure an Enterprise Service Bus (ESB). We are seeking assistance to help shape and enhance our current requirements before tendering the solution to the market in the next stage of the procurement process.An Enterprise Service Bus (ESB) is traditionally used to orchestrate all integrations and consists of a few tools that consolidate bespoke developments into a single solution that is both flexible and easy to monitor. These tools considerably reduce the work required to maintain communications between different applications.At the time the University purchased the current ESB, most systems were hosted on site and very few of them communicated in a ‘standard’ way, instead of using bespoke integrations between systems. The ESB purchased was intended to handle all these requirements with the flexibility to adapt to future requirements.The University's approach

II.1.6) Information about lots

This contract is divided into lots: No

II.2) Description

II.2.2) Additional CPV code(s)

72000000

II.2.3) Place of performance

NUTS code:

UKJ31


Main site or place of performance:

II.2.4) Description of the procurement

OverviewThe University of Portsmouth is seeking to engage the market with regards the refinement of its requirements to procure an Enterprise Service Bus (ESB). We are seeking assistance to help shape and enhance our current requirements before tendering the solution to the market in the next stage of the procurement process.An Enterprise Service Bus (ESB) is traditionally used to orchestrate all integrations and consists of a few tools that consolidate bespoke developments into a single solution that is both flexible and easy to monitor. These tools considerably reduce the work required to maintain communications between different applications.At the time the University purchased the current ESB, most systems were hosted on site and very few of them communicated in a ‘standard’ way, instead of using bespoke integrations between systems. The ESB purchased was intended to handle all these requirements with the flexibility to adapt to future requirements.The University's approach to integrations has since changed; many on-site systems have been replaced with cloud hosted alternatives, and are becoming more standardised in the way they communicate, with a drive towards a publish and subscribe methodology.The way the University pays for these systems is also changing - rather than buying licences, new solutions are typically based on pay per usage. In the past we did not have to consider the amount of data we moved between systems; with cloud based systems we have to be careful because there is often a charge associated with moving data.

II.2.5) Award criteria

Price is not the only award criterion and all criteria are stated only in the procurement documents

II.2.7) Duration of the contract, framework agreement or dynamic purchasing system

Duration in months: 60

This contract is subject to renewal: No

II.2.9) Information about the limits on the number of candidates to be invited

II.2.10) Information about variants

Variants will be accepted: Yes

II.2.11) Information about options

Options: No

II.2.13) Information about European Union funds

The procurement is related to a project and/or programme financed by European Union funds: No

II.2.14) Additional information

Section III: Legal, economic, financial and technical information

III.1) Conditions for participation

III.1.1) Suitability to pursue the professional activity, including requirements relating to enrolment on professional or trade registers

List and brief description of conditions:

An SQ (Suppiler questionnaire) will be used as a suitablilty assessment. Suppliers must meet all mandatory requirements listed in the specification

III.1.2) Economic and financial standing

Selection criteria as stated in the procurement documents


III.1.3) Technical and professional ability

Selection criteria as stated in the procurement documents


III.2) Conditions related to the contract

Section IV: Procedure

IV.1) Description

IV.1.1) Type of procedure

Open procedure

IV.1.8) Information about Government Procurement Agreement (GPA)

The procurement is covered by the Government Procurement Agreement: No

IV.2) Administrative information

IV.2.2) Time limit for receipt of tenders or requests to participate

Date: 16/02/2023

Local time: 17:00

IV.2.4) Languages in which tenders or requests to participate may be submitted

EN

IV.2.7) Conditions for opening of tenders

Date: 16/02/2023

Local time: 17:00

Place:

Section VI: Complementary information

VI.1) Information about recurrence

This is a recurrent procurement: No

VI.4) Procedures for review

VI.4.1) Review body

University of Portsmouth

Winston Churchill Avenue Portsmouth Hampshire PO1 2UP

Portsmouth

PO1 2UP

UK

E-mail: procurement@port.ac.uk

VI.4.3) Review procedure

Precise information on deadline(s) for review procedures:

VI.5) Date of dispatch of this notice

30/01/2023

Coding

Commodity categories

ID Title Parent category
72000000 IT services: consulting, software development, Internet and support Computer and Related Services

Delivery locations

ID Description
100 UK - All

Alert region restrictions

The buyer has restricted the alert for this notice to suppliers based in the following regions.

ID Description
There are no alert restrictions for this notice.

About the buyer

Main contact:
procurement@port.ac.uk
Admin contact:
N/a
Technical contact:
N/a
Other contact:
N/a

Further information

Date Details
No further information has been uploaded.

0800 222 9004

Lines are open 8:30am to 5pm Monday to Friday.

Rydym yn croesawu galwadau'n Gymraeg.

We welcome calls in Welsh.